Database Develop

flash recovery issue

I am having a weird issue that I have not been able to fix it. The only custom recovery that works with my device is twrp 2.6.3.3.
I flashed the newer versions of twrp and the latest version of cwm for m7 - it flashes successfully (no error during flashing), but when trying to enter recovery, it gets stuck at "entering recovery" screen (restart recovery-->shows up the "entering recovery" screen-->for one secong the screen goes black --> goes back to htc splash with "entering recovery" message)
also, the factory recovery WORKS.
I tried:
- fastboot erase cache - reflash recovery
- factory reset - fastboot erase cache - flashed recovery
- I even downgraded the software version: wiped all the phone, including internal storage; flashed twrp 2.6.3.3 - adb loaded 4.19.401.11 stock - flashed factory recovery - updated the official OTAs back to 6.09.401.5
nothing helped.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__304
(bootloader) battery-status: good
(bootloader) battery-voltage: 4048mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.113s
If anyone has some idea why this happens or can give me some new ideas to try, please let me know

Not sure why but I'd stick with 2.6.3.3. It is nice and stable. Newer isn't always better

did you try out the latest Unofficial TWRP 2.7.1.2? im using it and havent looked back, works execelent (at least for me)

nateboi81 said:
Not sure why but I'd stick with 2.6.3.3. It is nice and stable. Newer isn't always better
Click to expand...
Click to collapse
true
the thing is that i need ver. 2.7.0.0 or newer in order to flash for ex slimkat or other roms

seqas said:
did you try out the latest Unofficial TWRP 2.7.1.2? im using it and havent looked back, works execelent (at least for me)
Click to expand...
Click to collapse
is it the version from June or something?
if it's newer version, could you please send me a link for it? i can't seem to find it
Thx

floxrin3 said:
is it the version from June or something?
if it's newer version, could you please send me a link for it? i can't seem to find it
Thx
Click to expand...
Click to collapse
its from 12th Jul
yes, here http://mdmower.cmphys.com/twrp-m7/

seqas said:
its from 12th Jul
yes, here http://mdmower.cmphys.com/twrp-m7/
Click to expand...
Click to collapse
yes, I tried that - no luck :/
thanks though

it has to do something with not wiping the cache after flashing the recovery ... I think
after every failed twrp2.7xx or latest cwm flash , I need to flash the 2.6.3.3 version that works flawlessly.
what i notice right away, is that whatever i try to do in there, i m getting E:Unable to mount '/cache'
wipe--advanced--select cache--wipe works though and after that everything is ok in 2.6.3.3
i tried fastboot erase cache, did`t make any difference
i´m pretty much out of ideas...

You will always get unable to mount cache in recovery after you do a fastboot erase cache. Have you been using that command after you flash the recovery? I just noticed you've been doing that before you flash it. You should flash the recovery. Then erase cache

nateboi81 said:
You will always get unable to mount cache in recovery after you do a fastboot erase cache. Have you been using that command after you flash the recovery? I just noticed you've been doing that before you flash it. You should flash the recovery. Then erase cache
Click to expand...
Click to collapse
thanks a lot for the info.
I will give it another go. I tried via flashify as well - same outcome
Sent from my HTC One using Tapatalk

still no success. I even ruu-ed it til the ver. 1.19.xx.xx and gradually used the official ota to update to 6.09.401.5. same issue, it says that flashed successfully, but doesn't enter recovery ; staying stucj at the htc splash page with ^entering recovery ^ text. I'm out of ideas, using sense roms anyway. it's just that it drives me kookoo not knowing why this is happening ??
Sent from my HTC One using Tapatalk

deleted

deleted
Sent from my HTC One using Tapatalk

Have you tried 2.8.0.1?
---------- Post added at 01:49 PM ---------- Previous post was at 01:47 PM ----------
Also: You may have to take everything back to factory. Turn s on if off. Relock bootloader. Run RUU. Enter factory recovery and perform factory reset. Unlock bootloader, Flash TWRP, and root.

[Q] HTC M7 can not get to start recovery

Hi,
I did searched the forums first to look for similar problems, but couldn't find exact problems, hence I started this thread. If by any chance I have missed it then I do apologise.
Here goes...
I have a HTC ONE M7 running 4.4.2 viper one rom, bootloader 1.54.0000 S-OFF
Problem:
I can boot the phone into bootloader menu, but I can not start the recovery. It gives an red triangle error logo stays there for a while and then reboots normally.
I have downloaded TWRP, and used fast boot command to erase cache and flashed twrp-2.6.3.3. Tried to get into recovery again, it said Entering Recovery on top of the screen and then went into a restarting loop.
what I would like to do here is to successfully flash a custom rom but for that as far as I can understand I have to enter recovery which I am failing.
In TWRP app it says recovery has been installed but I still couldn't enter the recovery mode.
Please suggest if there is any way that I can just erase the current rom and flash it with a custom rom or a NAND backup of another htc one m7 vanilla rom.
Thanks in advance hope to have a solution soon.

windyborough said:
Hi,
I did searched the forums first to look for similar problems, but couldn't find exact problems, hence I started this thread. If by any chance I have missed it then I do apologise.
Here goes...
I have a HTC ONE M7 running 4.4.2 viper one rom, bootloader 1.54.0000 S-OFF
Problem:
I can boot the phone into bootloader menu, but I can not start the recovery. It gives an red triangle error logo stays there for a while and then reboots normally.
I have downloaded TWRP, and used fast boot command to erase cache and flashed twrp-2.6.3.3. Tried to get into recovery again, it said Entering Recovery on top of the screen and then went into a restarting loop.
what I would like to do here is to successfully flash a custom rom but for that as far as I can understand I have to enter recovery which I am failing.
In TWRP app it says recovery has been installed but I still couldn't enter the recovery mode.
Please suggest if there is any way that I can just erase the current rom and flash it with a custom rom or a NAND backup of another htc one m7 vanilla rom.
Thanks in advance hope to have a solution soon.
Click to expand...
Click to collapse
Give us the output of "fastboot getvar all"
Thanks

mb_guy said:
Give us the output of "fastboot getvar all"
Thanks
Click to expand...
Click to collapse
Thanks for the reply, here is the output
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 2.03.30.0109
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.03.651.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4106mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.094s

windyborough said:
Thanks for the reply, here is the output
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 2.03.30.0109
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.03.651.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4106mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.094s
Click to expand...
Click to collapse
You have the sprint variant m7wls. You can only use roms and recovery that are specifically made for that variant.

alray said:
You have the sprint variant m7wls. You can only use roms and recovery that are specifically made for that variant.
Click to expand...
Click to collapse
Thanks for the quick reply, I am downloading this file please correct me if I am wrong.
ruu-zip-m7_wls_jb_50_sprint_1-29-651-10_ruu_decrypted-zip
Once its downloaded unzip it and then what to do? Kindly let me know.

windyborough said:
Thanks for the quick reply, I am downloading this file please correct me if I am wrong.
ruu-zip-m7_wls_jb_50_sprint_1-29-651-10_ruu_decrypted-zip
Once its downloaded unzip it and then what to do? Kindly let me know.
Click to expand...
Click to collapse
If you really want to flash RUU, you MUST NOT unzip it. You can also download TWRP for Sprint and flash it via recovery. After that choose your ROM, download it, transfer the ROM.zip to your phone using MTP option in custom recovery, and flash away

windyborough said:
Thanks for the quick reply, I am downloading this file please correct me if I am wrong.
ruu-zip-m7_wls_jb_50_sprint_1-29-651-10_ruu_decrypted-zip
Once its downloaded unzip it and then what to do? Kindly let me know.
Click to expand...
Click to collapse
well if your goal is to flash a custom recovery and then a custom rom, this file won't help. Download latest twrp for sprint variant then flash it to your phone:
Code:
fastboot flash recovery twrp-2.8.7.0-m7wls.img
fastboot erase cache
fastboot reboot-bootloader
Then boot in TWRP and flash the custom your youd like (must be a sprint rom from the sprint section)
Also remove your IMEI, MEID and SN from post #3. You want to keep these 3 numbers for yourself.

Then boot in TWRP and flash the custom your youd like (must be a sprint rom from the sprint section)
Also remove your IMEI, MEID and SN from post #3. You want to keep these 3 numbers for yourself.[/QUOTE]
Thanks a lot mate, for the answer and removing those numbers from the post. Cheers for that.
I will follow the instructions and update you with the result

O.k. I rebooted into TWRP successfully, downloaded this file from the link Guru_Reset_M7_Sprint_1.31.651.2
copied it to the root directory of the phone, flashed it, everything went well with no errors whatsoever, rebooted the phone it started fine showed me the home screen wallpaper but the screen was locked and the touch was not working, so I rebooted the phone, this time its only showing me the notification bar on top and the rest of the screen is blank, and the phone restarts on its own. Any advise please.

windyborough said:
O.k. I rebooted into TWRP successfully, downloaded this file from the link Guru_Reset_M7_Sprint_1.31.651.2
copied it to the root directory of the phone, flashed it, everything went well with no errors whatsoever, rebooted the phone it started fine showed me the home screen wallpaper but the screen was locked and the touch was not working, so I rebooted the phone, this time its only showing me the notification bar on top and the rest of the screen is blank, and the phone restarts on its own. Any advise please.
Click to expand...
Click to collapse
And why did you flashed this rom? You were telling us at post 1 that you want a custom rom/vanilla rom so why using an old stock rom? This rom is only for resetting your phone to the 1.31.651.2 software version which is not the right version for your phone (look at your getvar)
So what is your goal? You want to flash a custom rom or you want to go back to stock rom??

So what is your goal? You want to flash a custom rom or you want to go back to stock rom??[/QUOTE]
ok maybe I failed to explained myself but if you see I did said that in my very first post that its either custom rom or stock rom I just want to make it fully work.
If you can please point me to the correct rom link do not mind if its custom or stock as long as it fully works I will appreciate it. Because its a long list I got confused and made this mess, sorry about that.

windyborough said:
ok maybe I failed to explained myself but if you see I did said that in my very first post that its either custom rom or stock rom I just want to make it fully work.
If you can please point me to the correct rom link do not mind if its custom or stock as long as it fully works I will appreciate it. Because its a long list I got confused and made this mess, sorry about that.
Click to expand...
Click to collapse
ok no problem then if you want you could use the latest RUU for sprint which will update your phone to the latest stock version
http://dl3.htc.com/application/RUU_M7_WL_L50_SENSE60_SPCS_MR_Sprint_WWE_6.23.651.10.exe
Its an .exe file, launch it and follow instructions, it should take 10-15 min to flash

alray said:
ok no problem then if you want you could use the latest RUU for sprint which will update your phone to the latest stock version
Its an .exe file, launch it and follow instructions, it should take 10-15 min to flash
Click to expand...
Click to collapse
Thanks for your reply. I really appreciate your help. I will give it a go in the morning and will update you how it goes.

alray said:
ok no problem then if you want you could use the latest RUU for sprint which will update your phone to the latest stock version
Its an .exe file, launch it and follow instructions, it should take 10-15 min to flash
Click to expand...
Click to collapse
Thanks a million mate, it worked like a charm. Thank you for all your help. :good:

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!

Fastboot - write protected

Today my cell phone got stuck on the android one logo.
I was using the cell phone when it suddenly fired, so I forced a restart with the power button and from that moment on it never turned on again.
I have the bootloader unlocked and I was running the Paranoid Quartz 4 rom about 3 months ago without any problem.
The first thing I did was try to enter recovery mode (twrp) and it was not possible. The only thing I can do with the cell phone is enter fastboot mode. So I decided to flash the stock rom using MiFlash (I tried with android 9 and android 10), but the error is always the same: "remote: Error flashing partition: Write Protected".
I have been trying to find a solution for several hours, I watched a lot of videos, I read a lot of threads, but there is no case: no solution has worked so far.
In the MiA2 forums the only thread I found is the following:
https://forum.xda-developers.com/mi-a2/help/help-xiaomi-mi-a2-write-protected-t4153629
I followed all the steps you left in the comments but nothing worked.
I wanted to know if this is happening to anyone else, and if anyone can try to help me fix it.
Thank you very much, I appreciate any kind of help.

try running :
fastboot flashing unlock_critical
*if that doesn't work then try to run
fastboot getvar all
***post the output here so we can see what's going on
have you checked the basics ? are you CERTAIN you didn't lock bootloader ..
when you went back to stock from the custom rom did you remember to go into dev settings afterwards & to check that oem unlock and adb debug were toggled to on position
lastly if trying to restore stock using miflash try it in edl mode :
fastboot oem edl
then flash latest stock in miflash
the write protect error sounds strange to me .. what happens while trying to enter twrp ? what error do you get ? did you hold power and volume up until entering recovery ..are you sure you don't have ARB triggered ?

KevMetal said:
try running :
fastboot flashing unlock_critical
*if that doesn't work then try to run
fastboot getvar all
***post the output here so we can see what's going on
have you checked the basics ? are you CERTAIN you didn't lock bootloader ..
when you went back to stock from the custom rom did you remember to go into dev settings afterwards & to check that oem unlock and adb debug were toggled to on position
lastly if trying to restore stock using miflash try it in edl mode :
fastboot oem edl
then flash latest stock in miflash
the write protect error sounds strange to me .. what happens while trying to enter twrp ? what error do you get ? did you hold power and volume up until entering recovery ..are you sure you don't have ARB triggered ?
Click to expand...
Click to collapse
Thanks for the reply.
This is the output when i put "fastboot getvar all"
(bootloader) crc:1
(bootloader) anti:1
(bootloader) token:/+VhxhMzqIjkRrCKNtCRXkCZccE=
(bootloader) parallel-download-flash:yes
(bootloader) hw-revision:10000
(bootloader) unlocked:yes
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4346
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) erase-block-size: 0x200
(bootloader) logical-block-size: 0x200
(bootloader) variant:SDM EMMC
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xBB77F7E00
(bootloader) partition-type:vendor_b:raw
(bootloader) partition-size:vendor_b: 0x80000000
(bootloader) partition-type:vendor_a:raw
(bootloader) partition-size:vendor_a: 0x80000000
(bootloader) partition-type:system_b:ext4
(bootloader) partition-size:system_b: 0xC0000000
(bootloader) partition-type:system_a:ext4
(bootloader) partition-size:system_a: 0xC0000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x10000000
(bootloader) partition-type:boot_b:raw
(bootloader) partition-size:boot_b: 0x4000000
(bootloader) partition-type:boot_a:raw
(bootloader) partition-size:boot_a: 0x4000000
(bootloader) partition-type:minidump:raw
(bootloader) partition-size:minidump: 0x8000000
(bootloader) partition-type:rawdump:raw
(bootloader) partition-size:rawdump: 0x8000000
(bootloader) partition-type:modem_b:raw
(bootloader) partition-size:modem_b: 0xC000000
(bootloader) partition-type:modem_a:raw
(bootloader) partition-size:modem_a: 0xC000000
(bootloader) partition-type:logdump:raw
(bootloader) partition-size:logdump: 0x4000000
(bootloader) partition-typeersistbak:raw
(bootloader) partition-sizeersistbak: 0x2000000
(bootloader) partition-typeersist:raw
(bootloader) partition-sizeersist: 0x2000000
(bootloader) partition-type:splash:raw
(bootloader) partition-size:splash: 0x4000000
(bootloader) partition-type:mdtp_b:raw
(bootloader) partition-size:mdtp_b: 0x2000000
(bootloader) partition-type:mdtp_a:raw
(bootloader) partition-size:mdtp_a: 0x2000000
(bootloader) partition-type:bk1:raw
(bootloader) partition-size:bk1: 0x700000
(bootloader) partition-type:bluetooth_b:raw
(bootloader) partition-size:bluetooth_b: 0x100000
(bootloader) partition-type:dsp_b:raw
(bootloader) partition-size:dsp_b: 0x1000000
(bootloader) partition-type:dsp_a:raw
(bootloader) partition-size:dsp_a: 0x1000000
(bootloader) partition-type:modemst2:raw
(bootloader) partition-size:modemst2: 0x800000
(bootloader) partition-type:modemst1:raw
(bootloader) partition-size:modemst1: 0x800000
(bootloader) partition-type:fsg:raw
(bootloader) partition-size:fsg: 0x800000
(bootloader) partition-type:logfs:raw
(bootloader) partition-size:logfs: 0x800000
(bootloader) partition-type:devinfo:raw
(bootloader) partition-size:devinfo: 0x800000
(bootloader) partition-type:misc:raw
(bootloader) partition-size:misc: 0x400000
(bootloader) partition-type:xbl_b:raw
(bootloader) partition-size:xbl_b: 0x380000
(bootloader) partition-type:xbl_a:raw
(bootloader) partition-size:xbl_a: 0x380000
(bootloader) partition-type:sti:raw
(bootloader) partition-size:sti: 0x200000
(bootloader) partition-type:bluetooth_a:raw
(bootloader) partition-size:bluetooth_a: 0x100000
(bootloader) partition-type:keymaster_b:raw
(bootloader) partition-size:keymaster_b: 0x100000
(bootloader) partition-type:keymaster_a:raw
(bootloader) partition-size:keymaster_a: 0x100000
(bootloader) partition-type:mdtpsecapp_b:raw
(bootloader) partition-size:mdtpsecapp_b: 0x400000
(bootloader) partition-type:mdtpsecapp_a:raw
(bootloader) partition-size:mdtpsecapp_a: 0x400000
(bootloader) partition-type:tz_b:raw
(bootloader) partition-size:tz_b: 0x400000
(bootloader) partition-type:tz_a:raw
(bootloader) partition-size:tz_a: 0x400000
(bootloader) partition-type:devcfg_b:raw
(bootloader) partition-size:devcfg_b: 0x100000
(bootloader) partition-type:devcfg_a:raw
(bootloader) partition-size:devcfg_a: 0x100000
(bootloader) partition-type:toolsfv:raw
(bootloader) partition-size:toolsfv: 0x100000
(bootloader) partition-type:ddr:raw
(bootloader) partition-size:ddr: 0x100000
(bootloader) partition-type:dip:raw
(bootloader) partition-size:dip: 0x100000
(bootloader) partition-type:abl_b:raw
(bootloader) partition-size:abl_b: 0x100000
(bootloader) partition-type:abl_a:raw
(bootloader) partition-size:abl_a: 0x100000
(bootloader) partition-type:cmnlib64_b:raw
(bootloader) partition-size:cmnlib64_b: 0x100000
(bootloader) partition-type:cmnlib_b:raw
(bootloader) partition-size:cmnlib_b: 0x100000
(bootloader) partition-type:cmnlib64_a:raw
(bootloader) partition-size:cmnlib64_a: 0x100000
(bootloader) partition-type:cmnlib_a:raw
(bootloader) partition-size:cmnlib_a: 0x100000
(bootloader) partition-typemic_b:raw
(bootloader) partition-sizemic_b: 0x80000
(bootloader) partition-typemic_a:raw
(bootloader) partition-sizemic_a: 0x80000
(bootloader) partition-type:hyp_b:raw
(bootloader) partition-size:hyp_b: 0x80000
(bootloader) partition-type:hyp_a:raw
(bootloader) partition-size:hyp_a: 0x80000
(bootloader) partition-type:rpm_b:raw
(bootloader) partition-size:rpm_b: 0x80000
(bootloader) partition-type:rpm_a:raw
(bootloader) partition-size:rpm_a: 0x80000
(bootloader) partition-type:frp:raw
(bootloader) partition-size:frp: 0x80000
(bootloader) partition-type:keystore:raw
(bootloader) partition-size:keystore: 0x80000
(bootloader) partition-type:msadp:raw
(bootloader) partition-size:msadp: 0x40000
(bootloader) partition-type:apdp:raw
(bootloader) partition-size:apdp: 0x40000
(bootloader) partition-typeraw
(bootloader) partition-size 0x20000
(bootloader) partition-type:storsec:raw
(bootloader) partition-size:storsec: 0x20000
(bootloader) partition-type:vbmeta_b:raw
(bootloader) partition-size:vbmeta_b: 0x10000
(bootloader) partition-type:vbmeta_a:raw
(bootloader) partition-size:vbmeta_a: 0x10000
(bootloader) partition-type:sec:raw
(bootloader) partition-size:sec: 0x5000
(bootloader) partition-type:ssd:raw
(bootloader) partition-size:ssd: 0x8000
(bootloader) partition-type:limits:raw
(bootloader) partition-size:limits: 0x8000
(bootloader) partition-type:fsc:raw
(bootloader) partition-size:fsc: 0x2000
(bootloader) partition-type:dpo:raw
(bootloader) partition-size:dpo: 0x2000
(bootloader) partition-type:switch:raw
(bootloader) partition-size:switch: 0x2000
(bootloader) has-slot:modem:yes
(bootloader) has-slot:system:yes
(bootloader) current-slot:b
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:6
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:yes
(bootloader) slot-retry-count:a:7
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:no
(bootloader) slot-count:2
(bootloader) secure:yes
(bootloader) serialno:ca5094d9
(bootloader) product:jasmine
(bootloader) max-download-size:805306368
(bootloader) kernel:uefi
all:
finished. total time: 0.570s
Click to expand...
Click to collapse
And when I put fastboot flashing unlock_critical
FAILED (remote: Device already : unlocked!)
finished. total time: 0.004s
The problem is that I never thought to go back to the stock rom, I am trying to do it because my cell is dead. But the usb debugging was activated (I remember, whenever I connected the cell phone to the car, the notification would appear).
I already tried flashing the stock rom in EDL. I tried different versions but they all end in the same error. At this moment I am again downloading the last stable that they uploaded (V11.0.14.0.QDIMIXM) to try, but without hope hahaha
Finally, it doesn't let me enter TWRP, the only way is with a boot from fastboot (because flashing does not allow me, just like the roms). When I boot the twrp it starts up but gets stuck at the boot logo, it never enters recovery. And I don't know what you mean by "ARB triggered"
This MiA2 literally looks like a stone, I don't know what else to do. In a forum they told me that I have to have an "authorized EDL account" or contact one in order to unbrick the terminal.
Thanks again for the reply, I appreciate it.

ivan.lxc.10 said:
Thanks for the reply.
This is the output when i put "fastboot getvar all"
And when I put fastboot flashing unlock_critical
FAILED (remote: Device already : unlocked!)
finished. total time: 0.004s
The problem is that I never thought to go back to the stock rom, I am trying to do it because my cell is dead. But the usb debugging was activated (I remember, whenever I connected the cell phone to the car, the notification would appear).
I already tried flashing the stock rom in EDL. I tried different versions but they all end in the same error. At this moment I am again downloading the last stable that they uploaded (V11.0.14.0.QDIMIXM) to try, but without hope hahaha
Finally, it doesn't let me enter TWRP, the only way is with a boot from fastboot (because flashing does not allow me, just like the roms). When I boot the twrp it starts up but gets stuck at the boot logo, it never enters recovery. And I don't know what you mean by "ARB triggered"
This MiA2 literally looks like a stone, I don't know what else to do. In a forum they told me that I have to have an "authorized EDL account" or contact one in order to unbrick the terminal.
Thanks again for the reply, I appreciate it.
Click to expand...
Click to collapse
it will work by flashing the stock rom in edl
1. install Qualcomm 9008 drivers
2. run : fastboot oem edl
3.open miflash and refresh and flash rom
make sure you are using THE LATEST miflash ( use it to install drivers)
you can also try just changing to your other slot ...stock android 1 might still be there :
fastboot set_active b
or if you are b just put :
fastboot set_active a

KevMetal said:
it will work by flashing the stock rom in edl
1. install Qualcomm 9008 drivers
2. run : fastboot oem edl
3.open miflash and refresh and flash rom
make sure you are using THE LATEST miflash ( use it to install drivers)
you can also try just changing to your other slot ...stock android 1 might still be there :
fastboot set_active b
or if you are b just put :
fastboot set_active a
Click to expand...
Click to collapse
it didn't work. I'll leave you the log so you can see if you see something that I don't
"ACK count don't match!"
http://www.mediafire.com/file/z746700jxil5d6e/COM8%4020201019114123.txt/file (1st)
http://www.mediafire.com/file/5ba9u2yb0rnzqg9/COM8%402020101911540.txt/file (2nd)

ivan.lxc.10 said:
it didn't work. I'll leave you the log so you can see if you see something that I don't
"ACK count don't match!"
http://www.mediafire.com/file/z746700jxil5d6e/COM8%4020201019114123.txt/file (1st)
http://www.mediafire.com/file/5ba9u2yb0rnzqg9/COM8%402020101911540.txt/file (2nd)
Click to expand...
Click to collapse
I will take a look when i can
were you able to enter EDL correctly ?
did you try changing slots using the commands specified ?

KevMetal said:
I will take a look when i can
were you able to enter EDL correctly ?
did you try changing slots using the commands specified ?
Click to expand...
Click to collapse
Yes, every time I try to flash (so far without success) I try in fastboot mode and in EDL mode. Each mode has a different error: in fastboot mode the error is "remote: Error flashing partition: Write Protected". In EDL mode the error is: "ACK count don't match!".

ivan.lxc.10 said:
Yes, every time I try to flash (so far without success) I try in fastboot mode and in EDL mode. Each mode has a different error: in fastboot mode the error is "remote: Error flashing partition: Write Protected". In EDL mode the error is: "ACK count don't match!".
Click to expand...
Click to collapse
ACK count doesn't match error is because you didn't listen to me ..USE THE LATEST BETA MI FLASH ... uninstall old ones first ... send a photo to show you are using latest
---------- Post added at 11:47 PM ---------- Previous post was at 11:33 PM ----------
I looked at the logs.. you also seem to be using patched programmer files ..STOP ..use only the stock rom ..without copying or replacing files ...
send me a summary of exactly which version of miflash you are using ..which stock rom and explain what you are trying to do correctly

KevMetal said:
ACK count doesn't match error is because you didn't listen to me ..USE THE LATEST BETA MI FLASH ... uninstall old ones first ... send a photo to show you are using latest
---------- Post added at 11:47 PM ---------- Previous post was at 11:33 PM ----------
I looked at the logs.. you also seem to be using patched programmer files ..STOP ..use only the stock rom ..without copying or replacing files ...
send me a summary of exactly which version of miflash you are using ..which stock rom and explain what you are trying to do correctly
Click to expand...
Click to collapse
Sorry but you said to use the latest version of my flash .. not the BETA of my flash.
Anyway I just downloaded the beta version of miflash and it didn't work either, I'm starting to go crazy lol
What do you mean by "patched programmer files"? I am using the latest fastboot rom from 09/28/2020, I did not touch or replace anything (neither now nor in the previous times I tried to flash)
Now the step by step is as follows:
I am using the beta version of my flash that I downloaded from here https://drive.google.com/file/d/12Gy2RP1eWBBKS6R2S2G9qzt-UQRIxpAM/view
and the fastboot rom I downloaded it from here https://xiaomifirmwareupdater.com/archive/miui/jasmine/
(from the xiaomi page the links for the roms do not work)
So what I do is:
- Open cmd and MiFlash
- I put in MiFlash the option "clean all"
- I select the path where the rom is located (I have it in c: \ rom)
- fastboot oem edl
- refresh and flash in MiFlash

ivan.lxc.10 said:
Sorry but you said to use the latest version of my flash .. not the BETA of my flash.
Anyway I just downloaded the beta version of miflash and it didn't work either, I'm starting to go crazy lol
What do you mean by "patched programmer files"? I am using the latest fastboot rom from 09/28/2020, I did not touch or replace anything (neither now nor in the previous times I tried to flash)
Now the step by step is as follows:
I am using the beta version of my flash that I downloaded from here https://drive.google.com/file/d/12Gy2RP1eWBBKS6R2S2G9qzt-UQRIxpAM/view
and the fastboot rom I downloaded it from here https://xiaomifirmwareupdater.com/archive/miui/jasmine/
(from the xiaomi page the links for the roms do not work)
So what I do is:
- Open cmd and MiFlash
- I put in MiFlash the option "clean all"
- I select the path where the rom is located (I have it in c: \ rom)
- fastboot oem edl
- refresh and flash in MiFlash
Click to expand...
Click to collapse
well if that the case you need to consider a hardware failure...
please try the command to change slots and send me a photo of what is says in fastboot
also when you try to edl flash did you check that your phone appears as qualcomm 9008 device in device manager * just to make sure your 9008 drivers were installed correctly.
anyway try another thing .... download the fastboot version aosip-derp from their official page ...then flash all the image files one by one from fastboot ..but before starting first do :
fastboot -w
send me photo of what happens

KevMetal said:
well if that the case you need to consider a hardware failure...
please try the command to change slots and send me a photo of what is says in fastboot
also when you try to edl flash did you check that your phone appears as qualcomm 9008 device in device manager * just to make sure your 9008 drivers were installed correctly.
anyway try another thing .... download the fastboot version aosip-derp from their official page ...then flash all the image files one by one from fastboot ..but before starting first do :
fastboot -w
send me photo of what happens
Click to expand...
Click to collapse
I spoke with a person from the xiaomi forum and checking the log he told me that apparently the device has memory damaged, so it could not be solved with the firmware flashing. After that, he consulted another person and gave him the same diagnosis: the memory is damaged so it does not allow me to write in various sectors. So effectively, my problem is hardware.
I will send it to the technical service and then I will make an update on this thread to tell my experience.
Thank you very much for the answer, I appreciate it.

ivan.lxc.10 said:
I spoke with a person from the xiaomi forum and checking the log he told me that apparently the device has memory damaged, so it could not be solved with the firmware flashing. After that, he consulted another person and gave him the same diagnosis: the memory is damaged so it does not allow me to write in various sectors. So effectively, my problem is hardware.
I will send it to the technical service and then I will make an update on this thread to tell my experience.
Thank you very much for the answer, I appreciate it.
Click to expand...
Click to collapse
yeah hardware failure makes sense

KevMetal said:
yeah hardware failure makes sense
Click to expand...
Click to collapse
Hi there
having a similar issue with regards to flashing a rom over to an Asus Zenfone 5 ZC600KL X017DA has a Qualcomm Chipset 630
the issue i have is the phone is stuck on Asus logo and all i can get from the device using the power and volume Keys is CSC fastboot mode no recovery or anything
downloaded a couple firmwares details are
Asus_Zenfone_5_Lite_ZC600KL_630_14.0400_1808.057_20180903_CMD
And
[firmware27]CSC__ZC600KL(630)_14.0400.1801.006_20191023_Phone_PtoN
both firmwares in fastboot mode will fail and one thing to note is write protected keeps appearing and the interesting thing is the first firmware i listed seems to not do very much it will show several lines and then fail but the second firmware had more activity it seemed to be pushing something but then several points it kept saying write protected
i am to assume the device bootloader is locked
i keep seeing everywhere to try unlock bootloader i need to be able to disable the OEM within the phone settings ( obviously i cannot due to it not booting ) as well as debugging mode being enabled again i cant enable
i have a third firmware that is meant to be used with QPTS / Qfil and that throws up a couple of errors also
really could use some help with this it would be super appreciated and would owe an virtual beer haha
any solutions

nighthawk658 said:
Hi there
having a similar issue with regards to flashing a rom over to an Asus Zenfone 5 ZC600KL X017DA has a Qualcomm Chipset 630
the issue i have is the phone is stuck on Asus logo and all i can get from the device using the power and volume Keys is CSC fastboot mode no recovery or anything
downloaded a couple firmwares details are
Asus_Zenfone_5_Lite_ZC600KL_630_14.0400_1808.057_20180903_CMD
And
[firmware27]CSC__ZC600KL(630)_14.0400.1801.006_20191023_Phone_PtoN
both firmwares in fastboot mode will fail and one thing to note is write protected keeps appearing and the interesting thing is the first firmware i listed seems to not do very much it will show several lines and then fail but the second firmware had more activity it seemed to be pushing something but then several points it kept saying write protected
i am to assume the device bootloader is locked
i keep seeing everywhere to try unlock bootloader i need to be able to disable the OEM within the phone settings ( obviously i cannot due to it not booting ) as well as debugging mode being enabled again i cant enable
i have a third firmware that is meant to be used with QPTS / Qfil and that throws up a couple of errors also
really could use some help with this it would be super appreciated and would owe an virtual beer haha
any solutions
Click to expand...
Click to collapse
Good day, I would like to ask did you resolve the problem we have exactly same problem.

KevMetal said:
try running :
fastboot flashing unlock_critical
*if that doesn't work then try to run
fastboot getvar all
***post the output here so we can see what's going on
have you checked the basics ? are you CERTAIN you didn't lock bootloader ..
when you went back to stock from the custom rom did you remember to go into dev settings afterwards & to check that oem unlock and adb debug were toggled to on position
lastly if trying to restore stock using miflash try it in edl mode :
fastboot oem edl
then flash latest stock in miflash
the write protect error sounds strange to me .. what happens while trying to enter twrp ? what error do you get ? did you hold power and volume up until entering recovery ..are you sure you don't have ARB triggered ?
Click to expand...
Click to collapse
Bro i have the same problem with my redmi note 5 pro .one day it running smoothly but suddenly it stuck.when i restarted the device it stuck on logo. Recovery also got stucked.fastboot logo not showing only black screen but computer detected fastboot.i tried many things .but it says that the device is write protected