Database Develop

[Q] Help! No radios installed at all

I mistakenly wiped the htc one m7 trying to install a rom based off kit kat I believe. Well, now I have no radios listed at all on the boot screen. I followed the tutorial on the forum for using fast boot to reflash the boot I believe. Process involved an older boot, which didn't flash with an error. I successfully flashed the latest 4.06 version of boot which was successful.
The thread went on to say I should start with the stock rom. Couldn't get it to load with adb side loader or fast boot flash zip name.zip. I have been able to successfully side load viper one, the latest version, and I have the latest version of terp as the recovery.
My problem is the phone will stay on no more than 15 sec. Before it reboots. I cannot see it in my computer although it shows up in device manager. I installed the latest driver from a thread on here.
Seems my options are fast boot and side loader, but I get a signed verification fail when I try to fast boot the radio , also taken from a radio thread here. I'm pretty sure I need s off which is the only thing left. Would this cause the phone to reboot continuously?
I'm tired of messing with it is it time to trash it or is this fixable? Thanks in advance and I'll give any info you guys need to help.

Latest Sprint Radio

from fastboot getvar
C:\Users\Tai\Desktop\HTC One Backup\Restore Data\Others>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA3C4S903734
(bootloader) imei: 990004288501756
(bootloader) meid: 99000428850175
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3796mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.040s
C:\Users\Tai\Desktop\HTC One Backup\Restore Data\Others>
I dont know if this helps or not.

This is what I get from fastboot when I try to load the radio...
C:\Users\Tai\Desktop\HTC One Backup\Restore Data\Others>fastboot flash radio Rad
io_HTC.zip
sending 'radio' (18554 KB)...
OKAY [ 2.250s]
writing 'radio'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 5.500s
C:\Users\Tai\Desktop\HTC One Backup\Restore Data\Others>
This is where I was last night. After searching on the threads, it seems that flashing hboot is ok, but the radios cannot be flashed without S-OFF. At this point what are my options as far as getting this radio in.
It did this auto reboot every 10-15 sec. the minute i flashed the improper rom. Again I've tried fixing with thread guidance on here for softbricking a Sprint device by flashing an ATT, etc. device.
Please help. Are there people you can call to undo damage like this or are you stuck fixing yourself?
Thanks

tpan1983 said:
This is what I get from fastboot when I try to load the radio...
C:\Users\Tai\Desktop\HTC One Backup\Restore Data\Others>fastboot flash radio Rad
io_HTC.zip
sending 'radio' (18554 KB)...
OKAY [ 2.250s]
writing 'radio'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 5.500s
C:\Users\Tai\Desktop\HTC One Backup\Restore Data\Others>
This is where I was last night. After searching on the threads, it seems that flashing hboot is ok, but the radios cannot be flashed without S-OFF. At this point what are my options as far as getting this radio in.
It did this auto reboot every 10-15 sec. the minute i flashed the improper rom. Again I've tried fixing with thread guidance on here for softbricking a Sprint device by flashing an ATT, etc. device.
Please help. Are there people you can call to undo damage like this or are you stuck fixing yourself?
Thanks
Click to expand...
Click to collapse
if you are using fastboot the radio has to be an image file, not a zip, or a boot.img, or get a radio zip file and flash from recovery.

54594563 3255
Aldo101t said:
if you are using fastboot the radio has to be an image file, not a zip, or a boot.img, or get a radio zip file and flash from recovery.
Click to expand...
Click to collapse
Woops typo. So, what I was doing was opening the .zip, and there are two files. A .inf I believe, and the image file (which Windows recognizes as such). I'm copying and pasting this file in the folder with the tools and fastbooting the .img with the command
fastboot devices
I see the phone serial and fastboot
fastboot flash radio radio.img
I get the error I posted before...
I would like to explore flashing from recovery. Given my situation is this possible? Also, do the stock ROMs, the RUU I believe, does it have the radio installed?

The link BD Posted here are flashable zips for recovery install
Sent from my HTCONE using Tapatalk

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

Managed to soft-brick my HTC One m7, need help to recover

Hi everyone, I inherited a used HTC One m7 from my son after my iPhone 4 died. This is my first android device. The phone worked perfect with the stock OS, except the green tint issue after a factory pink tint camera fix. My son never had the time to address the issue, but I decided to try to fix the problem by replacing the awb_cal file. I'm not a Linux guy, so I started from scratch.
Unlocked, installed TWRP, rooted. Because of my inexperience with not only TWRP, but Linux, during the process I managed to wipe clean my HTC. I read lots of instructions to get back in business, but some of them caused more trouble than help. Now, I ended up with a nonfunctioning beautiful piece of technology.
This is where I'm now:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.17.661.52
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT34RW911052
(bootloader) imei: 354439053805232
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: TELUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4330mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-eff4f609
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.137s
Using Windows 7 Pro, have installed the fastboot/ADB drivers, installed HTC Sync Manager.
TWRP 3.0.2-0 installed, but not working, can't get into twrp recovery from fastboot-usb mode, it returns to fastboot-usb. In this mode fastboot recognizes the device in cmd. The only way to get ADB recognize my device is to go through the Unlock_code routine. The phone boots right into TWRP, but stops responding at the Running OpenRecoveryScript screen, "Updating partition details... done - Full SELinux support is present. - Running Recovery Commands - Formatting Cache using make_ext4fs... - Wiping data without wiping /data/media ... - Done. - Done processing script file". It hangs here, but now ADB recognizes my device. After rebooting manually into fastboot, it shows Tampered - Relocked, so the unlocking not finishing.
I tried to flash the PN07IMG_M7_UL_L50_SENSE60_MR_TELUS_WWE_7.17.661.7_Radio_4T.35.3218.16_10.33Q.1718.01L_release_420202_signed.zip file in Relocked, with htc_fastboot in rebootRUU mode, but after the first writing I cannot start the second flashing, because it doen't stop but starts sending 'zip' ... (43286 KB) by itself and gets unresponsive at that line:
sending 'zip'... (43286 KB) OKAY
sending time = 3.097 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) signature checking...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAIL90 hboot pre-update! please flush image again immediately
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
For "hboot-preupdate" response, restart the same procedure for device HT34RW9110
52...
sending 'zip'... (43286 KB)
Since that in the Bootloader it says in red: OS-7.17.661.52 (7.17.661.7)
I tried to give as much detail as I can, and now I need help please, what should I do. Thanks

vik919 said:
After rebooting manually into fastboot, it shows Tampered - Relocked, so the unlocking not finishing.
Click to expand...
Click to collapse
Unlocking the bootloader requires the stock recovery, not a custom recovery because when unlocking the bootloader, the phone must first make a factory reset using the stock recovery before the bootloader can be unlocked (this is to prevent unauthorized access to your data). If you don't have the stock recovery, your phone will try to boot it, custom recovery will boot instead of the stock one, unlock process will fail because the script is made for the stock recovery, phone will reboot to bootloader mode with the phone still in the locked/relocked state. Unfortunately, you can not boot custom software (recovery/rom/kernel) if the bootloader is locked/relocked. Flashing the recovery partition also requires an unlocked bootloader. You're kinda stock in an endless loop... You need to unlock the bootloader, bootloader unlock requires stock recovery, flashing back the stock recovery requires an unlocked bootloader... Long story short, never relock if custom software is installed.
When the phone is S-ON and (re)Locked, you can only flash signed files (official HTC files) that are same or newer version than what is already on your phone. You'll need to find either the 7.17.661.52 RUU or a 7.17.661.52 firmware.zip. (firmware.zip can be extracted from an ota update.zip so the 7.17.661.52 update file would be ok).

alray said:
Unlocking the bootloader requires the stock recovery, not a custom recovery because when unlocking the bootloader, the phone must first make a factory reset using the stock recovery before the bootloader can be unlocked (this is to prevent unauthorized access to your data). If you don't have the stock recovery, your phone will try to boot it, custom recovery will boot instead of the stock one, unlock process will fail because the script is made for the stock recovery, phone will reboot to bootloader mode with the phone still in the locked/relocked state. Unfortunately, you can not boot custom software (recovery/rom/kernel) if the bootloader is locked/relocked. Flashing the recovery partition also requires an unlocked bootloader. You're kinda stock in an endless loop... You need to unlock the bootloader, bootloader unlock requires stock recovery, flashing back the stock recovery requires an unlocked bootloader... Long story short, never relock if custom software is installed.
When the phone is S-ON and (re)Locked, you can only flash signed files (official HTC files) that are same or newer version than what is already on your phone. You'll need to find either the 7.17.661.52 RUU or a 7.17.661.52 firmware.zip. (firmware.zip can be extracted from an ota update.zip so the 7.17.661.52 update file would be ok).
Click to expand...
Click to collapse
Thanks alray for your response.
So, that PN07IMG_M7_UL_L50_SENSE60_MR_TELUS_WWE_7.17.661.7_ Radio_4T.35.3218.16_10.33Q.1718.01L_release_420202 _signed.zip file can't flash somehow my 7.17.661.52 firmware? I was not able to find any other file for my phone then this one. I don't use the phone on the Telus network anymore. is there any workaround?

vik919 said:
Thanks alray for your response.
So, that PN07IMG_M7_UL_L50_SENSE60_MR_TELUS_WWE_7.17.661.7_ Radio_4T.35.3218.16_10.33Q.1718.01L_release_420202 _signed.zip file can't flash somehow my 7.17.661.52 firmware? I was not able to find any other file for my phone then this one. I don't use the phone on the Telus network anymore. is there any workaround?
Click to expand...
Click to collapse
There is a 7.17.661.52 ruu on ir-file.com but downloading from this website requires a paid subscription
Sent from my HTC One using XDA Labs

alray said:
There is a 7.17.661.52 ruu on ir-file.com but downloading from this website requires a paid subscription
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
Is this the one you mean?
pn07img_m7_ul_l50_sense60_mr_telus_wwe_7.17.661.52_radio_4t.35.3218.16_10.33q.1718.01l_release_460209_signed.zip

vik919 said:
Is this the one you mean?
pn07img_m7_ul_l50_sense60_mr_telus_wwe_7.17.661.52_radio_4t.35.3218.16_10.33q.1718.01l_release_460209_signed.zip
Click to expand...
Click to collapse
Yes
Sent from my HTC One using XDA Labs

alray said:
Yes
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
I wouldn't mind to pay that 20 bucks if I knew that it would get me through the first steps to fix my phone. My only concern is that I already tried the
PN07IMG_M7_UL_L50_SENSE60_MR_TELUS_WWE_7.17.661.7_Radio_4T.35.3218.16_10.33Q.1718.01L_release_420202_signed.zip
file and it did not work. This is the one which went in once, but I didn't get the opportunity to flash second time. It is now hanging in brackets in my bootloader beside the 7.1.7.661.52 firmware number.
Also, I checked this file and I can't see any zip file in it I could extract. Wouldn't it be with that paid one which looks pretty much the same except the firmware version number?
PN07IMG_M7_UL_L50_SENSE60_MR_TELUS_WWE_7.17.661.52_Radio_4T.35.3218.16_10.33Q.1718.01l_release_46020 9_signed.zip
Wait a minute!
I just double checked and found at IR-File.com under Firmware an other file for my phone.
pn07img_m7_ul_l50_sense60_mr_telus_wwe_7.17.661.7_radio_4t.35.3218.16_10.33q.1718.01l_release_420202_signed_hboot.zip
This file ending with _hboot.zip only 493.0 MB in size compare to the other two files which are both about 1.5 GB. Is it possible that this latter one has the firmware.zip in it I could extract?
Please, advise, which one do I need?

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