Hello I believe I'm finally on the right track but need help getting back to the stock bootloader.
This thread was quite helpful to get from EDL black screen -> caprip bootloader for fastboot.
I now would like to go back to the stock bootloader while also retaining root via magisk and my personal files.
you know what bootloader is?
Yeah, I have a bootloader.img for version of android I was previously using. Can I simply "fastboot flash bootloader.img" to regain previous functionality?
Or should I compile a list of commands on the basis of the flashfile.xml?
flashfile.xml contents:
<?xml version="1.0" ?>
<flashing>
<header>
<phone_model model="borneo_retail"/>
<software_version version="borneo_retail-user 11 RZBS31.Q2-143-27-1 ac324 release-keysHA10_29.11.02.95.01R"/>
<subsidy_lock_config MD5="d41d8cd98f00b204e9800998ecf8427e" name="slcf_rev_d_default_v1.0.nvm"/>
<regulatory_config SHA1="da39a3ee5e6b4b0d3255bfef95601890afd80709" name="regulatory_info_default.png"/>
<sparsing enabled="true" max-sparse-size="536870912"/>
<interfaces>
<interface name="AP"/>
</interfaces>
</header>
<steps interface="AP">
<step operation="getvar" var="max-sparse-size"/>
<step operation="oem" var="fb_mode_set"/>
<step MD5="a6e69b4be7b38e19757508fd6315a7ad" filename="gpt.bin" operation="flash" partition="partition"/>
<step MD5="6718b5992fb363f9f343a5aa281171b3" filename="bootloader.img" operation="flash" partition="bootloader"/>
<step MD5="3aba48d9c519c3024c8874fd901d3902" filename="vbmeta.img" operation="flash" partition="vbmeta"/>
<step MD5="3396b7ca48f9090c8a10b77e84e9d3cd" filename="radio.img" operation="flash" partition="radio"/>
<step MD5="378ac81bcdbc0f6efb85590c4967d6e7" filename="BTFM.bin" operation="flash" partition="bluetooth"/>
<step MD5="59d248cb50acb0e7bfab993e30bb40d2" filename="dspso.bin" operation="flash" partition="dsp"/>
<step MD5="ea32733b53d8ce3463e25c61c064549c" filename="logo.bin" operation="flash" partition="logo"/>
<step MD5="3af4dad6c994f44a47abb31c7e136d0c" filename="boot.img" operation="flash" partition="boot"/>
<step MD5="e466a5c3a859cf191fcda1f904924788" filename="dtbo.img" operation="flash" partition="dtbo"/>
<step MD5="bb67d30feb2e4ddc18a56ae87d1d0faa" filename="recovery.img" operation="flash" partition="recovery"/>
<step MD5="8daf1443b7e74832cf395541b6288e99" filename="super.img_sparsechunk.0" operation="flash" partition="super"/>
<step MD5="e1c26711a719d38abc3f1fbe2576b64f" filename="super.img_sparsechunk.1" operation="flash" partition="super"/>
<step MD5="e3e175adb695d6e25dd846578af81955" filename="super.img_sparsechunk.2" operation="flash" partition="super"/>
<step MD5="ad06ce4895abae93d25fcf6be75609e4" filename="super.img_sparsechunk.3" operation="flash" partition="super"/>
<step MD5="24169d563179ff530936ffb4ab8f1708" filename="super.img_sparsechunk.4" operation="flash" partition="super"/>
<step MD5="783d44ba6021148d8bbbc1ebef450993" filename="super.img_sparsechunk.5" operation="flash" partition="super"/>
<step MD5="6e08b2a5bbb8950c0a77bc3174154a25" filename="super.img_sparsechunk.6" operation="flash" partition="super"/>
<step MD5="06442d338aac038a9e4caba6a1a88d5e" filename="super.img_sparsechunk.7" operation="flash" partition="super"/>
<step MD5="1391100f17c3843c17c3649c28ee925f" filename="super.img_sparsechunk.8" operation="flash" partition="super"/>
<step MD5="f3cd898d7d57c476028470cca4dc6355" filename="super.img_sparsechunk.9" operation="flash" partition="super"/>
<step operation="erase" partition="carrier"/>
<step operation="erase" partition="userdata"/>
<step operation="erase" partition="metadata"/>
<step operation="erase" partition="ddr"/>
<step operation="oem" var="fb_mode_clear"/>
</steps>
</flashing>
I assume flashing gpt.bin would cause repartitioning = data loss, but for sure erase userdata will erase your files
what is the current state of the phone?
what is your goal?
what is previous functionality?
Thanks for the help!
what is the current state of the phone?
Current state of the phone. The issue started when the phone was hardbricked after selecting, "Install to Inactive Slot (After OTA)" in Magisk. I blankflashed retus borneo but the phone remained in hardbricked in edl mode. I found the post on blankflashing caprip and was able to enter fastboot mode, albeit with the a mismatched bootloader.
what is your goal?
My goal at the bare minimum is to get working phone. I would really appreciate if I was able to retain my current data and magisk root.
what is previous functionality?
A phone rooted with magisk. I have a dump of firmware used during the rooting process, including a patched boot img. The only caveat is the boot.img is for version 23.00 while I believe I've patched it to version 25.2 during my time using the phone.
Keeping this all in mind, what files from the firmware dump should I flash via fastboot in order get my phone back into the state prior to the initial hardbrick.
Also obligatory fastboot getvar all:
fastboot getvar all
(bootloader) slot-suffixes: not found
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-caprip_retail-1bb4bb6ec5-211027
(bootloader) product: borneo
(bootloader) board: borneo
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 2
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SAMSUNG DP6DAB RV=08 PV=02 FV=0000000000000002
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5-M8=01 07 01 12
(bootloader) cpu: SM_KAMORTA_H 1.0
(bootloader) serialno:
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 0C9810F6
(bootloader) token: inactive
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 804466688
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) battery-voltage: 4158
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier:
(bootloader) ro.build.fingerprint:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) git:abl: MBM-3.0-caprip_retail-1bb4bb6ec5-211027
(bootloader) frp-state: no protection (err)
(bootloader) current-slot: a
(bootloader) running-bl-slot: unknown/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: unknown
(bootloader) slot-successful:_b: unknown
(bootloader) slot-unbootable:_a: unknown
(bootloader) slot-unbootable:_b: unknown
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x200
(bootloader) is-userspace: no
(bootloader) pcb-part-no:
(bootloader) primary-display: djnboe_ft8009_video_display
(bootloader) secondary-display:
to me it looks like your partitions are gone already. get a second opinion and decide to drop userdata, then just flash the whole stock rom from lolinet.com
you can stage it into several attempts
1) only bootloader
2) only boot super dtbo dsp bluetooth modem fsg radio logo + twrp vbmeta.empty without erase anything
3) full flash including gpt
Thanks!
Sounds like a plan, assumed this is would be the course of action.
Really I was wondering what the blankflash replaced other than the bootloader.img
Would I just issue the command below for route 1) only bootloader?:
Code:
fastboot flash bootloader bootloader.img
Below is what I found for 3) full flash:
Code:
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot flash bluetooth BTFM.bin
fastboot oem fb_mode_clear
echo -------------------------------------------------------------------------
echo please scroll up and check your flash for any errors
echo -------------------------------------------------------------------------
pause
fastboot reboot
exit
basically yes, but I would do all lines manually (haven't double checked) and start with --set-active=a to get better control in which slots flashed. for vbmeta I would add --disable-verity and --disable-verification flags.
Here are my results so far, it doesn't seem great.
Code:
fastboot --set-active=a
Setting current slot to 'a' FAILED (remote: '')
fastboot: error: Command failed
Code:
fastboot flash bootloader bootloader.img
Sending 'bootloader' (13824 KB) OKAY [ 0.354s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Invalid partition name keymaster
(bootloader) Invalid partition name hyp
(bootloader) Invalid partition name tz
(bootloader) Invalid partition name devcfg
(bootloader) Invalid partition name storsec
(bootloader) Invalid partition name prov
(bootloader) Invalid partition name rpm
(bootloader) Invalid partition name abl
(bootloader) Invalid partition name uefisecapp
(bootloader) Invalid partition name qupfw
(bootloader) Invalid partition name xbl_config
(bootloader) Invalid partition name xbl
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
I had to issue fastboot flash partition gpt.bin to get rid of the errors when flashing the bootloader.
My only question is if I can retain any my user data by not issuing the 'erase' commands? I doubt it due to the partitioning change, but I figure it's worth asking.
I've successfully run the below commands so far.
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
Success! I retained all my userdata by running the below commands:
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot erase carrier
fastboot flash bluetooth BTFM.bin
fastboot oem fb_mode_clear
I left out:
Code:
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
The only problem now is that I lost root due to flashing the stock boot.img
glad you solved! you can patch stock boot.img with Magisk again, then flash magisk_patched.img (and maybe vbmeta with flags)
Yep! Just had to create a new patched boot image and off to the races. Just like how it was
Funnily enough I have another hardbricked one I've been saving for parts. After using the caprip flash it runs into a hardbrick bootloop (signified by led flashes when plugged in) with no access to EDL, I'm considering retrying it by shorting the EDL pins, but that's a different issue
The only difference seems to be that the one that bootloops shipped with Android 10, but was upgraded to Android 11, while the success came with Android 11 stock
I have learned from you flashing gpt does not repartition whole emmc, only scatter is updated. Thx
I figured it out! The other one that was bootlooping (flashing led after caprip blankflash whenever plugged in) was due to insanely low battery.
To bypass this simply unplug the battery (pic attached related). Then simply plug in the USB to a computer. Finally hold power and volume down to enter fastboot, then simply repeat the steps above with the firmware archive of your choice. Reconnect the battery and close the phone up, and there you go! No test pins required!
A thank you to @Pleasehelpmeoif for pointing me in the right direction with your post here!
Related
Zenfone 3 Deluxe ZS550KL / ZS570KL / ZS570KL PRO
How to Downgrade this device
Disclaimer:
Code:
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricks,
thermonuclear war, or you getting
fired because the alarm app failed.
* Please do some research if you have any concerns
Q/A:
Q: Is QuickCharge 3.0 working with every charger if I downgrade to Marshmallow?
A: Can't test it since i only have the original charger. If Asus disabled it with Nougat it should work, because we will replace every essential system file on the phone. But maybe it never worked with other chargers.
Q: Links would make this tutorial easier/where are the links Today the needed files and/or how can i install ADB?
A: Links are missing on purpose. I want you to go read and research for yourself since an user mistake (flashing wrong files...) will brick the device.
Q: Is there an easier way?
A: Yes. You could write a batch File with the commands Inside. But without error detection there would be a risk of bricking.
Maybe you could just delete the system directory and just flash the bootloader and recovery and copy the rom in the sd-card and update from stock recovery (not tested!!)
Warning!
Always have your original firmware, recovery and boot files in case things don't go as expected
Backup your personal data!
PLEASE MAKE SURE you are using the respective files for your CPU (ZS570KL SD820 2.15Ghz - ZS570KL PRO SD821 2.3GHz)
Prerequisites
- Adb and Fastboot installed and working
- Python 2.X or 3.X installed.
- WW target firmware. You can download it from the ASUS official website
- sdat2simg toolkit
Guide
1. Extract the sdat2simg toolkit
2. Extract system files from firmware
Open the firmware zip and extract system.new.dat and system.transfer.list into the input folder.
3. Run sdat2simg
The tool will first convert the system.new.dat and system.transfer.list into a raw ext4 image, then it will be converted into a sparse flashable image.
4.Put the phone in fastboot mode and run following commands (if done and no error happens, fastboot will will output "OKAY":
Code:
fastboot flash boot boot.img
Code:
fastboot flash modem firmware-update NON-HLOS.bin
Code:
fastboot flash dsp firmware-update/adspso.bin
Code:
fastboot flash cmnlib firmware-update/cmnlib.mbn
Code:
fastboot flash cmnlib64 firmware-update/cmnlib64.mbn
Code:
fastboot flash devcfg firmware-update/devcfg.mbn
Code:
fastboot flash aboot firmware-update/emmc_appsboot.mbn
Code:
fastboot flash hyp firmware-update/hyp.mbn
Code:
fastboot flash keymaster firmware-update/keymaster.mbn
Code:
fastboot flash rpm firmware-update/rpm.mbn
Code:
fastboot flash tz firmware-update/tz.mbn
Code:
fastboot flash pmic firmware-update/pmic.elf
Code:
fastboot flash xbl firmware-update/xbl.elf
Code:
fastboot flash mdtp firmware-update/mdtp.img
Code:
fastboot flash system system.img
5. Reboot and enjoy.
Since this is my first tutorial here, feedback is appreciated an will lead Today better future postings.
Hi.Thanks for our guide.
As I updated to Oreo but I'm experiencing dramatic battery drain, your procedure is applicable also to downgrade from Oreo 8.0 back to Nougat? Thanks in advance.
Yes it doesn't matter in which firmware you start or end as long as the bootloader is unlocked. The way is the same.
Please triple check you downloaded the files suitable for your phone (2.4ghz vs 2.15ghz) so you don't accidentally brick it.
do you know how to check my variant? because my Z016D stuck at fastboot mode, bootloader is locked, hang on ASUS logo can't get into menu, i got these infos from running fastboot getvar all
(bootloader) cputype:8996
(bootloader) version:0.5
(bootloader) cpusn:893855352
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4188000
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:APD:ext4
(bootloader) partition-size:APD: 0xd700000
(bootloader) partition-type:ADF:ext4
(bootloader) partition-size:ADF: 0x2800000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x10000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xd154af000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xf3c00000
(bootloader) serialno:GCAZGF018098PG6
(bootloader) kernel:lk
(bootloader) product:QC_REFERENCE_PHONE
screen size is 5.7 inch
i need to flash stock firmware, if the bootloader is locked, will it be possible to push stock firmware to the internal storage and flash it using fasboot command?
thanks for helping me out...
the reason i stuck on ASUS screen is because i use fastboot command to flash this file UL-Z016_1-WW-5.14.44.2096-user.zip (the flashing process failed at start)
without realising there is 3 or 4 variants of this Z016D
You have zs570kl 2.15 ghz version. (Cpu 8996).
With locked bootloader you can only use same or newer rom to flash. Downgrading will fail.
There is a new downgrade thread with qfil tools and raw firmware. This should work even when locked (didn't try myself).
followed your process, after reboot android prompts for password. tried everything i could think of and nothing. won't boot into fastboot and no recovery installed anymore (twrp before). zs570kl unlocked and was attempting to downgrade to UL-Z016-WW-4.12.40.1698-user. was on oreo prior.
I can think of two things (if you flashed the right files and got no errors):
1. Your userdata (sd-card) is encrypted and after the downgrade it needs to be decrypted. Passwort is unfortunately not necessary the same as the google password.
2. Your device is FRP protected. You will need Today enter the google account details which where on the phone before.
Please add a screenshot of the password prompt so we can check.
Your device is not lost since you can just restore the factory raw rom (see other threads here about locking bootloader) with qfil. Don't know if it will reset frp. If this phone isn't yours you may be out of luck because it would still ask for a password.
have 1650-03 did data reset for bootloop issue now soft bricked trying to sideload official rom but adb giving error of \Program Files (x86)\Minimal ADB and Fastboot> .\adb devices
List of devices attached
serialno## sideload
PS C:\Program Files (x86)\Minimal ADB and Fastboot> .\adb sideload xt1650-03.xml
adb: failed to stat file xt1650-03.xml: No such file or directory
PS C:\Program Files (x86)\Minimal ADB and Fastboot>
File is in minimal adb and fastboot directory I renamed for shorter typing but have done copy\ paste for both filenames. I have read/tried lots of other threads and haven't fond resolution
why not use fastboot?
eLaDiio said:
why not use fastboot?
Click to expand...
Click to collapse
using fastboot returns a <waiting for any device> with adb I am at least getting my device recognized. realize I may be typing command incorrectly
PS C:\Program Files (x86)\Minimal ADB and Fastboot> .\adb reboot fastboot
error: closed
PS C:\Program Files (x86)\Minimal ADB and Fastboot> .\adb reboot bootloader
error: closed
PS C:\Program Files (x86)\Minimal ADB and Fastboot> .\fastboot reboot
< waiting for any device >
and then my device times out waiting for a package
Also my limited reading indicates that if I want to flash full rom sideload was the easier way compared to fastboot?
It also seems to me that if both adb and fastboot are in same directory tree then if adb wont recognize the file for transmit neither will fastboot correct?
jbabb said:
using fastboot returns a <waiting for any device> with adb I am at least getting my device recognized. realize I may be typing command incorrectly
PS C:\Program Files (x86)\Minimal ADB and Fastboot> .\adb reboot fastboot
error: closed
PS C:\Program Files (x86)\Minimal ADB and Fastboot> .\adb reboot bootloader
error: closed
PS C:\Program Files (x86)\Minimal ADB and Fastboot> .\fastboot reboot
< waiting for any device >
and then my device times out waiting for a package
Also my limited reading indicates that if I want to flash full rom sideload was the easier way compared to fastboot?
It also seems to me that if both adb and fastboot are in same directory tree then if adb wont recognize the file for transmit neither will fastboot correct?
Click to expand...
Click to collapse
Try this, power off the phone, later turn on with the volume - key press, if all go ok, you will are in a screen that said the info of you phone, connect the phone to your PC and try the command in cmd, fastboot device, if recognized you can use it, if not I think can be a drivers problem
eLaDiio said:
Try this, power off the phone, later turn on with the volume - key press, if all go ok, you will are in a screen that said the info of you phone, connect the phone to your PC and try the command in cmd, fastboot device, if recognized you can use it, if not I think can be a drivers problem
Click to expand...
Click to collapse
thanks I have re-updated drivers (third time) this allowed device to be found. Resolved original question of file not found--had a second exstension .xml.zip (been long time since I did this type of work). trying to flash a twrp.imi and getting
PS C:\Program Files (x86)\Minimal ADB and Fastboot> .\fastboot flash recovery twrp.imi
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
error: cannot load 'twrp.imi': Permission denied
PS C:\Program Files (x86)\Minimal ADB and Fastboot>
working from start screen
have not yet read up on this yet and I thank you for your assistance
jbabb said:
thanks I have re-updated drivers (third time) this allowed device to be found. Resolved original question of file not found--had a second exstension .xml.zip (been long time since I did this type of work). trying to flash a twrp.imi and getting
PS C:\Program Files (x86)\Minimal ADB and Fastboot> .\fastboot flash recovery twrp.imi
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
error: cannot load 'twrp.imi': Permission denied
PS C:\Program Files (x86)\Minimal ADB and Fastboot>
working from start screen
have not yet read up on this yet and I thank you for your assistance
Click to expand...
Click to collapse
mmm, try with fastboot boot twrp.img, that it could work
PS C:\Program Files (x86)\Minimal ADB and Fastboot> .\fastboot oem unlock begin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.063s]
finished. total time: 0.063s
PS C:\Program Files (x86)\Minimal ADB and Fastboot> .\fastboot boot twrp.img.zip
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
creating boot image...
creating boot image - 11196416 bytes
downloading 'boot.img'...
OKAY [ 0.360s]
booting...
(bootloader) permission denied!
**>tried flash partition GPT.bin and received security fail
do I need to downgrade back to7.1.1 then let ota back to 8(oreo)
**>tried flash partition GPT.bin and received security fail
do I need to downgrade back to7.1.1 then let ota back to 8(oreo)[/QUOTE]
was finally able to flash GRIFFIN_OPL27.76-51_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml (7-11-2018)downloaded from android file host but my boot loop issue was not resolved. my phone is out of warranty may try to root will keep researching and if anyone has something that may work please post-- thank all for their help.
i insist, try to enter the bootloader mode with the phone off and without being connected to the computer, if the phone starts in this mode, you can boot into TWRP with the command fastboot boot twrp.img by pc, if boot correctly you can flash some rom , if possible, based on oreo
install and try to connect your device with Lenovo Moto Smart Assistant... I hope that will work for you. from Lenovo Moto Smart Assistant also u can install the Stock Rom.
eLaDiio said:
i insist, try to enter the bootloader mode with the phone off and without being connected to the computer, if the phone starts in this mode, you can boot into TWRP with the command fastboot boot twrp.img by pc, if boot correctly you can flash some rom , if possible, based on oreo
Click to expand...
Click to collapse
**From power off I can enter bootloader mode with vol- and power button no usb conncected. When I try to fastboot boot twrp.img I still get permission denied
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock begin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.062s]
finished. total time: 0.062s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot twrp-3222-griffin.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
downloading 'boot.img'...
OKAY [ 0.748s]
booting...
(bootloader) permission denied!
FAILED (remote failure)
finished. total time: 0.748s
**so not sure what I am doing wrong yet. Have tried three versions of twrp(3.1.1.0 3.2.1.0 3.2.2.2) downloaded from team win page. phone is oem locked.
saifprvz said:
install and try to connect your device with Lenovo Moto Smart Assistant... I hope that will work for you. from Lenovo Moto Smart Assistant also u can install the Stock Rom.
Click to expand...
Click to collapse
I did try your suggestion of Lenovo moto smart assistant but it doesn't support my model actuall model is xt1650-03-SS . I have flashed stock rom GRIFFIN_OPL27.76-51_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml (7-11-2018) using ADB FASTBOOT but I am still in boot loop-- this is why am trying to get a TWRP to boot. Have also tried using RsdLITE but that was failing on packet 3/34 when I finally found a ROM that is would decompress.
jbabb said:
I did try your suggestion of Lenovo moto smart assistant but it doesn't support my model actuall model is xt1650-03-SS . I have flashed stock rom GRIFFIN_OPL27.76-51_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml (7-11-2018) using ADB FASTBOOT but I am still in boot loop-- this is why am trying to get a TWRP to boot. Have also tried using RsdLITE but that was failing on packet 3/34 when I finally found a ROM that is would decompress.
Click to expand...
Click to collapse
I assume The Problem here is you are not getting the right Rom which works on your phone. so in that case ... try both below Roms -
https://forum.xda-developers.com/moto-z/development/stock-moto-z-8-0-firmware-t3805226
https://forum.xda-developers.com/moto-z/how-to/how-to-relock-bootloader-moto-z-xt-1650-t3821817
So since I can get ROMs to load( loaded GRIFFIN_OPLS27.76-51-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml) to my phone but I am still having bootloop issue maybe I am missing something when flashing. This is the command list I have been using
fastboot oem unlock begin
fastboot oem unlock begin
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem lock
fastboot reboot
jbabb said:
So since I can get ROMs to load( loaded GRIFFIN_OPLS27.76-51-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml) to my phone but I am still having bootloop issue maybe I am missing something when flashing. This is the command list I have been using
Code:
fastboot oem unlock begin
fastboot oem unlock begin
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem lock
fastboot reboot
Click to expand...
Click to collapse
scripts are correct... as i told u before, the roms which you are trying to install on your phone are not for the model which you have it.
saifprvz said:
scripts are correct... as i told u before, the roms which you are trying to install on your phone are not for the model which you have it.
Click to expand...
Click to collapse
I understand that but even the two that you posted links for in your earlier post didn't work although I do thank you for giving them to me so I could try them. In desperation I requested the bootloader unlock code for my device so I could try and ROOT but the code I received is not unlocking my boot loader and yes I know it is case sensitive (using copy paste)
:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock *mycode* and command input twice
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.061s]
finished. total time: 0.061s
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
[C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8996-92.03
(bootloader) product: sheridan
(bootloader) board: sheridan
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 2
(bootloader) storage-type: ufs
(bootloader) ufs: 64GB TOSHIBA THGBF7G9L4LBATRB FV=0300
(bootloader) ram: 4GB SAMSUNG LP4 DIE=8Gb M5=01 M6=05 M7=00 M8=08
(bootloader) cpu: MSM8996
(bootloader) serialno: *********
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: 68408FD500000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) ro.carrier: retus]
good evening
Help solve the problem.
Watch A1612, there was a customized firmware with a Russian.
I tried to roll it 2,8,0,5 did not work, the clock just does not start, an eternal reboot.
I tried to roll back to 1.3.0n by the instructions
https://forum.xda-developers.com/smartwatch/amazfit/tutorial-unbrick-huami-amazfit-t3547300
The firmware was installed, when trying to update on OTA to 1.3.8a immediately after the reboot I receive an inscription on the screen "ERROR" and an exclamation mark.
Help me please.
Thank you
C:\adb\huangheUS-1.3.0n>fastboot getvar all
(bootloader) version-bootloader: U-Boot 2013.07-00096-gf3b140c
(bootloader) version-baseband: N/A
(bootloader) version-hardware: V1.1 20130322
(bootloader) version-cdma: N/A
(bootloader) variant: watch
(bootloader) serialno: 0123456789abcdef
(bootloader) product: watch
(bootloader) secure: no
(bootloader) unlocked: yes
(bootloader) uart-on: NO
(bootloader) partition-size:bootloader: 0x0000
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:recovery: 0x1000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:boot: 0x2000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:system: 0x3000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x4000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x5000
(bootloader) partition-type:userdata: ext4
(bootloader) max-download-size: 0x4000000
all:
Finished. Total time: 0.280s
Flash latest INTL stock, then before you start it:
Code:
adb wait-for-device
adb shell reboot bootloader
fastboot erase data
fastboot erase cache
fastboot erase userdata
fastboot reboot
lfom said:
Flash latest INTL stock, then before you start it:
Code:
adb wait-for-device
adb shell reboot bootloader
fastboot erase data
fastboot erase cache
fastboot erase userdata
fastboot reboot
Click to expand...
Click to collapse
Did you mean - flash latest international ROM 2.8.0.5 and after implement your code?
Could you please describe in more details?
Thanks
ExtrimVF said:
Did you mean - flash latest international ROM 2.8.0.5 and after implement your code?
Could you please describe in more details?
Thanks
Click to expand...
Click to collapse
Exactly what you said (and that's what I said previously).
lfom said:
Exactly what you said (and that's what I said previously).
Click to expand...
Click to collapse
I've done exactly what you said.
Installed latest ROM by this link
https://forum.xda-developers.com/smartwatch/amazfit/fw-tool-stock-firmware-installers-2017-t3725494
and run script what you gave me.
Now i have always booting watch
Please help
ExtrimVF said:
I've done exactly what you said.
Installed latest ROM by this link
https://forum.xda-developers.com/smartwatch/amazfit/fw-tool-stock-firmware-installers-2017-t3725494
and run script what you gave me.
Now i have always booting watch
Please help
Click to expand...
Click to collapse
Try this if you are on Windows:
Code:
adb wait-for-device & adb reboot wipe
or this on Linux/macOS:
Code:
adb wait-for-device; adb reboot wipe
If you still cannot boot, I suggest and you use the code I gave you before to fully erase data on watch, then use the unbrick tutorial but flash an old firmware like 1.3.0 first, then try to boot watch.
Could you please help me to find right instruction and rom package?
help do not know why this happen cannot boot up.thanks for any help.
Hi , it means that you have enter into FastBoot mode , and also your Software is not official !
Anyway to exit from fastboot mode just press 5 times Vol + and One time power key . Now again turn On your device and it should boot up normaly . Good Luck
Teddy Lo said:
Hi , it means that you have enter into FastBoot mode , and also your Software is not official !
Anyway to exit from fastboot mode just press 5 times Vol + and One time power key . Now again turn On your device and it should boot up normaly . Good Luck
Click to expand...
Click to collapse
Thank you for your reply but still will not work here is the screen shot of what happens when i do what you have said..Thanks again
So for you the problem is probably corrypted OTA updates which didn't go well because your battery in that moment didn't had enough energy .
Anyway to bring your device in working condition you need:
1. PC with working internet
2. USB cable
3. Download REpair Assistant https://www.verizonwireless.com/support/knowledge-base-116950/#windows
https://www.verizonwireless.com/support/knowledge-base-116950/#windows
Install this tool on your pc once you installed reboot your PC and once boot is finish plug your device with usb cable inside the PC , run the Repair Assistant and follow instructions .
Good luck
thanks again
Teddy Lo said:
So for you the problem is probably corrypted OTA updates which didn't go well because your battery in that moment didn't had enough energy .
Anyway to bring your device in working condition you need:
1. PC with working internet
2. USB cable
3. Download REpair Assistant https://www.verizonwireless.com/support/knowledge-base-116950/#windows
https://www.verizonwireless.com/support/knowledge-base-116950/#windows
Install this tool on your pc once you installed reboot your PC and once boot is finish plug your device with usb cable inside the PC , run the Repair Assistant and follow instructions .
Good luck
Click to expand...
Click to collapse
no luck
Hi , tell me full model name for your device so I can send you firmware which you can flash with fastboot terminal ...
motog 1540
Teddy Lo said:
Hi , tell me full model name for your device so I can send you firmware which you can flash with fastboot terminal ...
Click to expand...
Click to collapse
I have the original software but i need to know the steps i need to do through fastboot in terminal.When i say abd devices it shows no device?Here are 3 screen shots from recovery i chose update from sd card then also wipe all data then reboot shot.thanks for your help..
Hi , download this firmware :
https://androidfilehost.com/?fid=889764386195908045
Once the downloading file is finished , put firmware to the ADB folder ( directory where is your minimal adb & fastboot installed) for example :
C:/ADB/
Now to get your device into adb mode you need to select Apply update from ADB and then wait for adb drivers to be instaled if is not .
Next write adb devices and you should see your device and sideload inside terminal ...
Now flash this firmware with command:
adb sideload osprey_retasia_ds-user+6.0.1+MPIS24.107-55-2-17+19.zip and press Enter .
Good luck
Teddy Lo said:
Hi , download this firmware :
https://androidfilehost.com/?fid=889764386195908045
Once the downloading file is finished , put firmware to the ADB folder ( directory where is your minimal adb & fastboot installed) for example :
C:/ADB/
Now to get your device into adb mode you need to select Apply update from ADB and then wait for adb drivers to be instaled if is not .
Next write adb devices and you should see your device and sideload inside terminal ...
Now flash this firmware with command:
adb sideload osprey_retasia_ds-user+6.0.1+MPIS24.107-55-2-17+19.zip and press Enter .
Good luck
Click to expand...
Click to collapse
Thanks again for your help but adb devices cannot find any devices or emulators and i cannot get inside of android to enable usb debugging is there a way using fast boot to flash the recovery because fastboot devices comes up with my serial number?
Try the same file osprey_retasia_ds-user+6.0.1+MPIS24.107-55-2-17+19.zip with command :
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot -w update osprey_retasia_ds-user+6.0.1+MPIS24.107-55-2-17+19.zip
And see what is happening .
Teddy Lo said:
Try the same file osprey_retasia_ds-user+6.0.1+MPIS24.107-55-2-17+19.zip with command :
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot -w update osprey_retasia_ds-user+6.0.1+MPIS24.107-55-2-17+19.zip
And see what is happening .
Click to expand...
Click to collapse
Another sreen shot before i rebooted still nothing ,You area very patient man.Thanks
klassic1 said:
Another sreen shot before i rebooted still nothing ,You area very patient man.Thanks
Click to expand...
Click to collapse
Hi , I need little more information .
1. What is full model name ? ( open the battery cover and see what model is or send me private imei to check )
2. For which carier is your device ? ( SPRINT , USC , Retus )
Teddy Lo said:
Hi , I need little more information .
1. What is full model name ? ( open the battery cover and see what model is or send me private imei to check )
2. For which carier is your device ? ( SPRINT , USC , Retus )
Click to expand...
Click to collapse
Thanks again for your patients.
The carrier is Telus here in Canada and here is the info you requested.
Great , now once we know the right information you can finaly rest ^_^ .
Download this firmware:
https://drive.google.com/uc?export=download&id=0Bw_NsGJYGFyVaXc3dFMxYUNxaEk
Once you downloaded extract all files inside location where minimal ADB & fastboot is installed .
For example C:/ADB ...
Now put your phone to Bootloader mode then open Minimal ADB and Fastboot terminal and write one by one commands:
fastboot devices and press Enter ( just to make sure that your device is recognised )
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Good luck , and let me know if you fixed or not .
Teddy Lo said:
Great , now once we know the right information you can finaly rest ^_^ .
Download this firmware:
https://drive.google.com/uc?export=download&id=0Bw_NsGJYGFyVaXc3dFMxYUNxaEk
Once you downloaded extract all files inside location where minimal ADB & fastboot is installed .
For example C:/ADB ...
Now put your phone to Bootloader mode then open Minimal ADB and Fastboot terminal and write one by one commands:
fastboot devices and press Enter ( just to make sure that your device is recognised )
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Good luck , and let me know if you fixed or not .
Click to expand...
Click to collapse
Did all you asked first shot show no slots did that for all.then second picture of what it said at reboot
Hi , you did it wrong !
This file XT1540_OSPREY_RETCA-TELUS_6.0_MPI24.65-33.1-2_cid14_subsidy-TELUS_CFC.xml.zip you need to extract to minimal adb and fastboot directory !
So if you didn't understand
1. Uninstall minimall adb and fastboot toll completely .
2. Download this minimal adb & fastboot terminal and instal normaly into C: directory
https://androidfilehost.com/?fid=745425885120698566
here is example how to install just click on next ... Make sure is on C partition.
https://forum.xda-developers.com/showthread.php?t=2317790
Once instaling is finished go to C: partition and you will see one folder with name "ADB" that is your minimal adb & fastboot directory.
3. Extract with 7-zip XT1540_OSPREY_RETCA-TELUS_6.0_MPI24.65-33.1-2_cid14_subsidy-TELUS_CFC.xml.zip to the ADB folder .
If you don't have the 7-zip download grom here :
https://www.7-zip.org/download.html
4. Once you extracted all , put your device into bootloader mode and now put your phone to Bootloader mode then open Minimal ADB and Fastboot terminal and write one by one commands:
fastboot devices and press Enter ( just to make sure that your device is recognised )
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase logo
fastboot oem fb_mode_clear
fastboot reboot
If you are still facing same error you should unlock bootloader :
write command :
fastboot oem get_unlock_data
it shloud look like this something like this
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
just copy and paste here all stings like this example .
This is what i get ..
D:\platform-tools-latest-windows\platform-tools>fastboot devices
TA391006KH fastboot
D:\platform-tools-latest-windows\platform-tools>fastboot flash partition D:\XT1572_CLARK_RETEU_6.0.1_MPHS24.107-58-5_cid7_subsidy-DEFAULT_CFC.xml\gpt.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.393s
D:\platform-tools-latest-windows\platform-tools>fastboot flash bootloader D:\XT1572_CLARK_RETEU_6.0.1_MPHS24.107-58-5_cid7_subsidy-DEFAULT_CFC.xml\bootloader.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (2699 KB)...
OKAY [ 0.155s]
writing 'bootloader'...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing pmic ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing hyp ...
(bootloader) flashing sdi ...
OKAY [ 1.637s]
finished. total time: 1.805s
D:\platform-tools-latest-windows\platform-tools>fastboot flash logo D:\XT1572_CLARK_RETEU_6.0.1_MPHS24.107-58-5_cid7_subsidy-DEFAULT_CFC.xml\logo.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:logo: not found
target reported max download size of 536870912 bytes
sending 'logo' (3687 KB)...
OKAY [ 0.081s]
writing 'logo'...
OKAY [ 0.116s]
finished. total time: 0.204s
D:\platform-tools-latest-windows\platform-tools>fastboot flash boot D:\XT1572_CLARK_RETEU_6.0.1_MPHS24.107-58-5_cid7_subsidy-DEFAULT_CFC.xml\boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (40960 KB)...
OKAY [ 0.985s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.702s
D:\platform-tools-latest-windows\platform-tools>fastboot flash recovery D:\XT1572_CLARK_RETEU_6.0.1_MPHS24.107-58-5_cid7_subsidy-DEFAULT_CFC.xml\recovery.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (41040 KB)...
OKAY [ 0.961s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.728s
D:\platform-tools-latest-windows\platform-tools>fastboot flash system D:\XT1572_CLARK_RETEU_6.0.1_MPHS24.107-58-5_cid7_subsidy-DEFAULT_CFC.xml\system.img_sparsechunk.0
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (257199 KB)...
OKAY [ 5.813s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.232s
D:\platform-tools-latest-windows\platform-tools>fastboot flash system D:\XT1572_CLARK_RETEU_6.0.1_MPHS24.107-58-5_cid7_subsidy-DEFAULT_CFC.xml\system.img_sparsechunk.1
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (255632 KB)...
OKAY [ 5.848s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.917s
D:\platform-tools-latest-windows\platform-tools>fastboot flash system D:\XT1572_CLARK_RETEU_6.0.1_MPHS24.107-58-5_cid7_subsidy-DEFAULT_CFC.xml\system.img_sparsechunk.2
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (255866 KB)...
OKAY [ 5.851s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.920s
Only this is someone else's but mine does exactly the same...with telus zip
Hello everybody!
My brother got a Moto One (XT 1941-3) last year and tried to flash it, but somehow he got the wrong Rom and bricked it.
I'm trying to recover the phone to its stock rom, but the device says that it is OEM_locked, so I can't install a new firmware on it.
fastboot oem unlock asks for a code (which is given when you input the unlock data in moto support website) , but fastboot oem get_unlock_data displays that "unlock data unavailable"
fastboot getvar all is here:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-deen_retail-6f8d34a-190722
(bootloader) product: deen
(bootloader) board: deen
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SAMSUNG RH64AB RV=08 PV=05 FV=0000000000000005
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: 0050511872
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: B8C94CFA00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 534773760
(bootloader) reason: Fall-through from charger boot mode
(bootloader) imei: 359547090224541
(bootloader) meid:
(bootloader) date: 01-10-2019
(bootloader) sku: XT1941-3
(bootloader) carrier_sku: XT1941-3
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun Oct 27 14:28:52 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/deen/deen_sprout:9/PPKS29
(bootloader) ro.build.fingerprint[1]: .68-16-21-11/b3804:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.39.381.12.deen.retai
(bootloader) ro.build.version.full[1]: l.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.r1-02500-89xx.0
(bootloader) version-baseband: M8953_16.15.02.23R DEEN_LATAMDSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.115-perf-gb0f0dde (hu
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 201
(bootloader) kernel.version[2]: 50123 (prerelease) (GCC) ) #1 SMP PREEMP
(bootloader) kernel.version[3]: T Mon Jul 22 06:12:31 CDT 2019
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: MBM-2.1-deen_retail-6f8d34a-190722
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier: retbr
(bootloader) current-slot:
(bootloader) running-boot-lun: 0
(bootloader) running-slot:
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: No
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: No
(bootloader) slot-bootable:_b: No
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.103s
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any possible solutions?
Karlloz said:
Hello everybody!
My brother got a Moto One (XT 1941-3) last year and tried to flash it, but somehow he got the wrong Rom and bricked it.
I'm trying to recover the phone to its stock rom, but the device says that it is OEM_locked, so I can't install a new firmware on it.
fastboot oem unlock asks for a code (which is given when you input the unlock data in moto support website) , but fastboot oem get_unlock_data displays that "unlock data unavailable"
fastboot getvar all is here:
Any possible solutions?
Click to expand...
Click to collapse
Did you try to flash stock boot.img anyway? Maybe because it has a wrong rom it displays wrong info.
borksek said:
Did you try to flash stock boot.img anyway? Maybe because it has a wrong rom it displays wrong info.
Click to expand...
Click to collapse
Tried it again now:
Code:
fastboot flash boot boot.img
error: Failed to identify current slot
Then I tried to boot it directly:
Code:
fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 1.813s]
booting...
(bootloader) permission denied!
FAILED (remote failure)
finished. total time: 1.824s
Setting a or b slots to active also doesn't work:
Code:
fastboot --set-active=a
Setting current slot to 'a'...
(bootloader) Command is not allowed
FAILED (remote failure)
finished. total time: 0.019s
fastboot --set-active=b
Setting current slot to 'b'...
(bootloader) Command is not allowed
FAILED (remote failure)
finished. total time: 0.019s
Semms that it needs to unlock the bootloader, but, as my first post explain, I'm unable to unlock it :crying:
Karlloz said:
Tried it again now:
Code:
fastboot flash boot boot.img
error: Failed to identify current slot
Then I tried to boot it directly:
Code:
fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 1.813s]
booting...
(bootloader) permission denied!
FAILED (remote failure)
finished. total time: 1.824s
Setting a or b slots to active also doesn't work:
Code:
fastboot --set-active=a
Setting current slot to 'a'...
(bootloader) Command is not allowed
FAILED (remote failure)
finished. total time: 0.019s
fastboot --set-active=b
Setting current slot to 'b'...
(bootloader) Command is not allowed
FAILED (remote failure)
finished. total time: 0.019s
Semms that it needs to unlock the bootloader, but, as my first post explain, I'm unable to unlock it :crying:
Click to expand...
Click to collapse
I see in getvar that cid returns 0x0000.which means it's unlockable. You probably wouldn't be able to unlock it anyway since you first have to enable the "oem unlock toggle" in dev settings before you can get it unlocked in fastboot.
Question is how he was able to flash it in the first place if it's locked, unless it's possible to flash original files without unlocking.
Have you tried to full flash latest retbr firmware or tried to use lenovo/moto smart assistant to recover it?
tys0n said:
I see in getvar that cid returns 0x0000.which means it's unlockable. You probably wouldn't be able to unlock it anyway since you first have to enable the "oem unlock toggle" in dev settings before you can get it unlocked in fastboot.
Question is how he was able to flash it in the first place if it's locked, unless it's possible to flash original files without unlocking.
Have you tried to full flash latest retbr firmware or tried to use lenovo/moto smart assistant to recover it?
Click to expand...
Click to collapse
Maybe the phone was unlocked during the flashing of the wrong ROM, but after it locked itself? Dunno, really doesn't make sense...
I tried to flash all the the stock rom, and to use the assitant, but none could solve the problem.. when flashing using the commands from 'flashfile.xml' (converted to .bat), all files output "okay", but after rebooting it stills goes back to the same "no bootable a/b slot".
Karlloz said:
Maybe the phone was unlocked during the flashing of the wrong ROM, but after it locked itself? Dunno, really doesn't make sense...
I tried to flash all the the stock rom, and to use the assitant, but none could solve the problem.. when flashing using the commands from 'flashfile.xml' (converted to .bat), all files output "okay", but after rebooting it stills goes back to the same "no bootable a/b slot".
Click to expand...
Click to collapse
Try doing flash bootimage boot_a
borksek said:
Try doing flash bootimage boot_a
Click to expand...
Click to collapse
Tried a couple commands related to boot.img:
Code:
fastboot flash bootimage boot_a
error: cannot load 'boot_a': No such file or directory
Fastboot seems to be searching for boot_a as a file, not as the partition. Then I tried to invert the command:
Code:
fastboot flash boot_a boot.img
target reported max download size of 534773760 bytes
sending 'boot_a' (65536 KB)...
OKAY [ 2.018s]
writing 'boot_a'...
OKAY [ 0.911s]
finished. total time: 2.932s
it did transfer the file to boot_a, but when I rebooted the phone to check, still got the same error, no change. Tried to flash into boot_b too, exaclty the same...
Also:
Code:
fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 1.805s]
booting...
(bootloader) permission denied!
FAILED (remote failure)
finished. total time: 1.813s
There should be some way to unlock the bootloader, it appears to be the only reason i cant flash the system..
Karlloz said:
Tried a couple commands related to boot.img:
Fastboot seems to be searching for boot_a as a file, not as the partition. Then I tried to invert the command:
it did transfer the file to boot_a, but when I rebooted the phone to check, still got the same error, no change. Tried to flash into boot_b too, exaclty the same...
Also:
There should be some way to unlock the bootloader, it appears to be the only reason i cant flash the system..
Click to expand...
Click to collapse
Im not really good with Motorola's but with Samsung's atleast, you should be able to flash stock without any problem, as long as it's signed
Karlloz said:
Maybe the phone was unlocked during the flashing of the wrong ROM, but after it locked itself? Dunno, really doesn't make sense...
I tried to flash all the the stock rom, and to use the assitant, but none could solve the problem.. when flashing using the commands from 'flashfile.xml' (converted to .bat), all files output "okay", but after rebooting it stills goes back to the same "no bootable a/b slot".
Click to expand...
Click to collapse
I guess I was wrong about cid 0x0000. They can be unlocked, but for that to happen you'd have to first enable oem toggle in developer settings, then get the unlock data in fastboot mode, send the data to motorola which will then send the unlock key to you. Any idea if he's done that?
And no, it shouldn't lock itself without proper lock commands in fastboot mode.
So your flash commands looks like this?
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
same problem
I have the same problem, did you find a solution?
contacto
ISRAELSANDOVAL29292 said:
I have the same problem, did you find a solution?
Click to expand...
Click to collapse
hablas español hacemos contacto x whatss
---------- Post added at 09:22 PM ---------- Previous post was at 09:13 PM ----------
Karlloz said:
Tried a couple commands related to boot.img:
Code:
fastboot flash bootimage boot_a
error: cannot load 'boot_a': No such file or directory
Fastboot seems to be searching for boot_a as a file, not as the partition. Then I tried to invert the command:
Code:
fastboot flash boot_a boot.img
target reported max download size of 534773760 bytes
sending 'boot_a' (65536 KB)...
OKAY [ 2.018s]
writing 'boot_a'...
OKAY [ 0.911s]
finished. total time: 2.932s
it did transfer the file to boot_a, but when I rebooted the phone to check, still got the same error, no change. Tried to flash into boot_b too, exaclty the same...
Also:
Code:
fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 1.805s]
booting...
(bootloader) permission denied!
FAILED (remote failure)
finished. total time: 1.813s
There should be some way to unlock the bootloader, it appears to be the only reason i cant flash the system..
Click to expand...
Click to collapse
hi are you flashing with fastboot commands or are you using some software. use RSD lite
alguien encontró solucion tengo el mismo problema
lucasymax said:
hablas español hacemos contacto x whatss
---------- Post added at 09:22 PM ---------- Previous post was at 09:13 PM ----------
hi are you flashing with fastboot commands or are you using some software. use RSD lite
Click to expand...
Click to collapse
Hi there! just for rules, I wrote in english, but I speak spanish, anyway I have same trouble, pm to create wsp group.
reply
darwyn001 said:
Hi there! just for rules, I wrote in english, but I speak spanish, anyway I have same trouble, pm to create wsp group.
Click to expand...
Click to collapse
hey bro, have you managed to solved that?
Dahirock said:
hey bro, have you managed to solved that?
Click to expand...
Click to collapse
Not yet! I tried flashing every security patch downloaded from Lolinet, nothing fix it.... I will wait for Q and try again
tengo el mismo problema
alguien pudo encontrar una solucion motorola one 1941-3
I've tried with android Q and and still have the same result
darwyn001 said:
Not yet! I tried flashing every security patch downloaded from Lolinet, nothing fix it.... I will wait for Q and try again
Click to expand...
Click to collapse
I've tried flashing XT1941-3_DEEN_RETBR_10_QPK30.54-22_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC rom via fastboot and RSDlite and sill have the same problem
J4m3sB4rn3s said:
I've tried flashing XT1941-3_DEEN_RETBR_10_QPK30.54-22_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC rom via fastboot and RSDlite and sill have the same problem
Click to expand...
Click to collapse
Try LMSA's Flashing/Rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
sd_shadow said:
Try LMSA's Flashing/Rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Click to expand...
Click to collapse
That was my first attempt to unbrick my phone, but didn't work
J4m3sB4rn3s said:
That was my first attempt to unbrick my phone, but didn't work
Click to expand...
Click to collapse
I think your device is bricked same as mine. I have been flashing every phone that I have owned and never have I bricked a phone but even with that experience i understand that mine was a novice mistake flashing a lower version of Android. I think you will need to look at qcom blank-flash options.