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]
Related
I tried to restore and reinstall ROM in numerous ways, including adb, fastboot and sdcard. I even tried Funky Huawei.
Currently I can get to eRecovery and to TWRP. Fastboot works without problem. But that's about it, boot sometimes goes to Lineage boot splash, which I used prior the Magisk update.
Thanks for help in advance
Here is info from fastboot:
fastboot oem get-product-model:
<bootloader> CMR-AL09
fastboot getvar vendorcountry:
vendorcountry: hw/eu
fastboot oem get-build-number:
(bootloader) :CMR-AL09 8.0.0.122(C432)
fastboot getvar rescue_enter_recovery:
getvar:rescue_enter_recovery FAILED (remote: FAIL:need all image flashed!)
fastboot oem oeminforead-system_version
FAILED (remote: The reason of failed input oem_nv_item error!)
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.
Purchased a bricked Pixel3a of ebay.
I cannot RMA it since i am not the original owner of the device.
"The device boots to Cant Find Valid operating system."
I can boot the device into fastboot mode.
is there anyway i can restore recovery with "FASTBOOT OEM citadel" commands?
Code:
PS C:\Program Files (x86)\Minimal ADB and Fastboot> .\fastboot.exe oem citadel
(bootloader) citadel <command>
(bootloader) Commands:
(bootloader) rescue Try to rescue Citadel
(bootloader) state Print current Citadel state
(bootloader) reset Reset Citadel
(bootloader) reset-locks Reset AVB locks
(bootloader) version Print citadel OS version
(bootloader) reprovision Reprovision device after a RMA unlock
(bootloader) suzyq on|off Enable or disable SuzyQable
FAILED (remote: '')
fastboot: error: Command failed
PS C:\Program Files (x86)\Minimal ADB and Fastboot>
i have try to use the "rescue" command by staging the exact boot image on the system. (.\fastboot.exe stage bootloader-sargo-b4s4-0.2-5402313.img)
it return with this error "FAILED (remote: 'failed to rescue citadel Bad Buffer Size')"
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot> .\fastboot.exe oem citadel
(bootloader) citadel <command>
(bootloader) Commands:
(bootloader) rescue Try to rescue Citadel
(bootloader) state Print current Citadel state
(bootloader) reset Reset Citadel
(bootloader) reset-locks Reset AVB locks
(bootloader) version Print citadel OS version
(bootloader) reprovision Reprovision device after a RMA unlock
(bootloader) suzyq on|off Enable or disable SuzyQable
FAILED (remote: '')
fastboot: error: Command failed
PS C:\Program Files (x86)\Minimal ADB and Fastboot> .\fastboot.exe stage bootloader-sargo-b4s4-0.2-5402313.img
Sending 'bootloader-sargo-b4s4-0.2-5402313.img' (8349 KB) OKAY [ 0.349s]
Finished. Total time: 0.412s
PS C:\Program Files (x86)\Minimal ADB and Fastboot> .\fastboot.exe oem citadel rescue
(bootloader) Recovering citadel - it may take a couple of minutes
FAILED (remote: 'failed to rescue citadel Bad Buffer Size')
fastboot: error: Command failed
PS C:\Program Files (x86)\Minimal ADB and Fastboot>
does anyone has any other ideas or commands i can try or ideas?
thanks
zimmie said:
Purchased a bricked Pixel3a of ebay.
I cannot RMA it since i am not the original owner of the device.
"The device boots to Cant Find Valid operating system."
I can boot the device into fastboot mode.
is there anyway i can restore recovery with "FASTBOOT OEM citadel" commands?
i have try to use the "rescue" command by staging the exact boot image on the system. (.\fastboot.exe stage bootloader-sargo-b4s4-0.2-5402313.img)
it return with this error "FAILED (remote: 'failed to rescue citadel Bad Buffer Size')"
does anyone has any other ideas or commands i can try or ideas?
thanks
Click to expand...
Click to collapse
Seems like this should be posted in
https://forum.xda-developers.com/pixel-3a/help
Sent from my mata using XDA Labs
sd_shadow said:
Seems like this should be posted in
https://forum.xda-developers.com/pixel-3a/help
Sent from my mata using XDA Labs
Click to expand...
Click to collapse
I didnt post it there because the Fastboot "OEM Citadel" command seems to work on all Pixel phones.
Back to the topic it seems like im getting some where.
If i stage the image file, Run ".\fastboot.exe oem citadel reprovision" and then ".\fastboot.exe oem citadel rescue"
That seems to be doing something....after 30 mins i ended up disconnecting the phone since i had to go.
I'll try to run it for a few hrs on Monday and ill report back. I'm not sure if its hanging or it actually doing something.. but its progress..
one thing i'd like to know is, when i look inside the zip file i downloaded from google. there are 2 boot images.
Name: "bootloader-sargo-b4s4-0.2-5736883.img" and "boot.img" inside another archive.
what the difference between the 2 and which one should i be restoring order to get into recovery.
I'm not familiar with Android boot partitions.
I have flashed (fastboot method) twrp.img to my locked device and now I'm stuck at boot. At first I was getting boot loop and "corrupt" message (g.co/ABH). Luckily, I could still access fastboot mode. By looking around, I managed to remedy that a bit by:
Code:
$ wget https://dlcdnets.asus.com/pub/ASUS/ZenFone/AI2202/UL-ASUS_AI2202-ASUS-33.0804.2060.100-1.1.1-2302-user.zip
$ unzip *zip
$ payload_dumper payload.bin
$ for i in boot dtbo vendor_boot vbmeta vbmeta_system
do
fastboot flash $i output/$i.img
done
$ fastboot reboot fastboot
# these will fail due to resizing partitions on a locked device
$ for i in system system_ext product odm vendor
do
fastboot flash $i output/$i.img
done
Resizing partition ... (Can't in locked state)
Now I get bootloader, fastbootd, and stock recovery. Wiping/resetting in recovery mode almost succeeds:
Code:
misc_vab_msg.version: 0x2
misc_vab_msg.magic: ...
misc_vag_msg.merge_status: 0x0
misc_vag_msg.source_slot: 0x1
-- Wiping data...
E:Open failed: /metadata/ota: No such file or directory
-- Clean boot sound files...
Formatting /data...
Formatting /metadata...
-- Data wipe complete.
At this point, restarting the system results in the device turning itself off a few seconds after the ASUS logo.
My phone is on stock firmware 33.0804.2060.100 (android 13). Could someone kindly help me and tell me what to do next?
Here's all the info I can get now:
Code:
$ fastboot oem device-info
(bootloader) Verity mode: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Device authorized: false
(bootloader) Device authorized2: false
(bootloader) WaterMask unlock: N
(bootloader) XBL:
(bootloader) ABL: 0.0.029.0-WW-user
(bootloader) SSN: ...
(bootloader) ISN: ...
(bootloader) IMEI: ...
(bootloader) IMEI2: ...
(bootloader) CID: ASUS
(bootloader) COUNTRY: EU
(bootloader) Project: DAVINCI
(bootloader) DT ID: 66
(bootloader) SB: Y
(bootloader) SBNR: Y
(bootloader) DDR Manufacturer ID: 1
(bootloader) DDR Device Type: 8
(bootloader) TotalDMCounter: 0
(bootloader) DMCounter: 0
(bootloader) SlotARetryCounter: 0
(bootloader) SlotAUnbootableCounter: 0
(bootloader) SlotBRetryCounter: 0
(bootloader) SlotBUnbootableCounter: 0
(bootloader) BOOT_COUNT: 0
(bootloader) LOCK_COUNT: 0
(bootloader) Check_APDP: 1
(bootloader) rawdump_en: false
(bootloader) force start logcat-asdf: false
(bootloader) Current Slot: a
(bootloader) Slot_a bootable: Bootable
(bootloader) AVB Verity: Enable
(bootloader) Verify vbmeta ret: 0
(bootloader) ABL_FTM: FALSE
(bootloader) UART-ON Status: false
I have a feeling that I'm not using the right image for this purpose. I don't know how to get my hands on a RAW image. I keep reading about some android beta page, but just can't find a link for Zenfone 9.
You dont need any raw fw, flash stock recovery and reboot:
fastboot flash recovery recovery.img
Download Data package from February 25th.
Size of the data package: 100 MB. Free transfer of up to 6 GB of photos, videos and documents. Send large files via email or a link to share. No registration, no ads, just simple file sharing!
filetransfer.io
Recovery from UL-ASUS_AI2202-ASUS-33.0804.2060.100
@NisseGurra thanks for your input. I checked the md5sum of your recovery image and the one I extracted from the payload.bin. They are indeed the same. I have flashed it alright:
Code:
$ fastboot flash recovery recovery.img
Sending 'recovery' (102400 KB) OKAY [ 3.396s]
Writing 'recovery' OKAY [ 0.162s]
Finished. Total time: 3.570s
Now, what should I do? reboot to bootloader -> recovery? then what?
Because still letting the device boot normally will lead to its shutdown in 20 seconds.
lordbit said:
@NisseGurra thanks for your input. I checked the md5sum of your recovery image and the one I extracted from the payload.bin. They are indeed the same. I have flashed it alright:
Code:
$ fastboot flash recovery recovery.img
Sending 'recovery' (102400 KB) OKAY [ 3.396s]
Writing 'recovery' OKAY [ 0.162s]
Finished. Total time: 3.570s
Now, what should I do? reboot to bootloader -> recovery? then what?
Because still letting the device boot normally will lead to its shutdown in 20 seconds.
Click to expand...
Click to collapse
Seems something got messed up.
You have some options: find an recovery that have adb sideload support: flash the stock fw from it,
adb sideload xxx.zip
Option 2
Repack the stock fw (use payload dumper to extract all img), create an folder with all extracted img and add adb.exe, fastboot.exe, AdbWinApi.dll, AdbWinUsbApi.dll and install.bat (attached, rename to .bat)
Connect phone, enter fastboot and click on the bat file, it should install full rom.
Thanks! I will try it.
I tried your second method. Most of the images got flashed alright, except these ones:
Code:
Sending 'odm' (1248 KB) OKAY [ 0.055s]
Writing 'odm' FAILED (remote: '(odm_a) No such partition')
fastboot: error: Command failed
Sending sparse 'product' 1/4 (524236 KB) OKAY [ 19.285s]
Writing 'product' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Sending sparse 'system' 1/7 (524232 KB) OKAY [ 19.632s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Sending 'system_ext' (386600 KB) OKAY [ 14.180s]
Writing 'system_ext' FAILED (remote: '(system_ext_a) No such partition')
fastboot: error: Command failed
Sending sparse 'vendor' 1/3 (524176 KB) OKAY [ 18.675s]
Writing 'vendor' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Sending 'vendor_dlkm' (73448 KB) OKAY [ 2.577s]
Writing 'vendor_dlkm' FAILED (remote: '(vendor_dlkm_a) No such partition')
fastboot: error: Command failed
I think those should be flashed after a
Code:
fastboot reboot fastboot
But in that case, the "flash" command will try to resize the partitions and I get an error that says "Resizing in a locked state of the device is not possible". I am paraphrasing here.
Option 3, install https://forum.xda-developers.com/t/paranoid-android-topaz-alpha-1-asus-zenfone-9.4557631/
Use the suggested image way. It install new recovery, if i rember correct it has adb support
Reboot recovery and use option2
@NisseGurra sorry if my question seems dumb. But I have not unlocked my bootloader (when I had the chance). Do these recovery.img methods with adb work for me?
lordbit said:
@NisseGurra sorry if my question seems dumb. But I have not unlocked my bootloader (when I had the chance). Do these recovery.img methods with adb work for me?
Click to expand...
Click to collapse
If you bootloader is locked so you cant flash anything not signed by Asus, no twrp etc, So strange it got messed up
Yeah it's weird that you could flash anything at all, that isn't signed
anyway, it seems like you where able to flash the asus recovery?
can you boot it?
If so try booting it and tipe "adb reboot sideload" if everything goes well it should reboot and allow you to sideload unmodified (asus signed) .zips, do this
Also consider data wipe from recovery
Darkmasterhk said:
Yeah it's weird that you could flash anything at all, that isn't signed
anyway, it seems like you where able to flash the asus recovery?
can you boot it?
If so try booting it and tipe "adb reboot sideload" if everything goes well it should reboot and allow you to sideload unmodified (asus signed) .zips, do this
Also consider data wipe from recovery
Click to expand...
Click to collapse
1. I pressed power button + vol-up, ended up in "bootloader" menu.
2. Chose "Recovery mode"
3. At this point, on my laptop, I executed "adb reboot sideload" as you suggested.
However, I am prompted with an error that this device is unauthorized.
Code:
adb devices
List of devices attached
N...P unauthorized
How can I "authorize" this? When I had access to fully-booted system, I just needed to confirm some dialogue. Here there is no question.
Aww that's bad, I don't know how to allow a device from recovery, sorry.
Usually, if it worked under Android itself, it works in recovery as well.
Just to make sure, it worked under Android, right?
I assume u use a Linux system and I somehow had trouble under Linux, with adb and authorization
Yes, "adb" did work between my Linux system and phone before it gets stuck in this mode.
I managed to fix the problem by using a RAW image from romdevelopers. Extracted the content of the zip file and executed "flashall_AFT.cmd" on a Windows machine with the right drivers installed.
For the record, these posts [1][2] are pretty close to what I did.
Thank you both for your support.
EDIT:
I converted the "flashall_AFT.cmd' to "flashall_AFT.sh", so I could be able to achieve the same on a Linux system. USE IT AT YOUR OWN RISK.