Moto G3 is Bricked,
Device is Locked Status Code:0
XT1550
Tried recovery Mode gives error:
==========
Your Status didn't startup successfully. Use the Software Repair Assistant on Computer to repair your device.
==========
Tried Fastboot it says
C:\Users\admin\Downloads\ADB\ADB and Fastboot>fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.048s
Please help.
radnam said:
Moto G3 is Bricked,
Device is Locked Status Code:0
XT1550
Tried recovery Mode gives error:
==========
Your Status didn't startup successfully. Use the Software Repair Assistant on Computer to repair your device.
==========
Tried Fastboot it says
C:\Users\admin\Downloads\ADB\ADB and Fastboot>fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.048s
Please help.
Click to expand...
Click to collapse
Flash stock firmware from here : https://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
Download links and FAQ are present in that thread.
adityak1303 said:
Flash stock firmware from here : https://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
Download links and FAQ are present in that thread.
Click to expand...
Click to collapse
I have tired doing the steps given. However it gives the following error:
C:\Users\admin\Downloads\ADB and Fastboot\ADB and Fastboot>fastboot oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.031s
C:\Users\admin\Downloads\ADB and Fastboot\ADB and Fastboot>fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 0.459s
C:\Users\admin\Downloads\ADB and Fastboot\ADB and Fastboot>astboot flash bootloader bootloader.img
'astboot' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\admin\Downloads\ADB and Fastboot\ADB and Fastboot>fastboot flash bootloader bootloader.img
target reported max download size of 268435456 bytes
sending 'bootloader' (2546 KB)...
OKAY [ 0.094s]
writing 'bootloader'...
(bootloader) flashing sbl1 ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash sbl1
FAILED (remote failure)
finished. total time: 1.424s
Just to be sure, you are running this in as an Administrator command window, correct?
It's bricked... Nothing is writing to the internal storage and everything is coming back FAILED. Seen a few of these recently, if it was a different error we might be able to do something but doing 'fastboot oem fb_mode_set' should never give an error.
acejavelin said:
Just to be sure, you are running this in as an Administrator command window, correct?
It's bricked... Nothing is writing to the internal storage and everything is coming back FAILED. Seen a few of these recently, if it was a different error we might be able to do something but doing 'fastboot oem fb_mode_set' should never give an error.
Click to expand...
Click to collapse
That's what I was wondering. And yes I am running Administrator Command Window.
I am just keeping my fingers crossed that someone can help me resolve the issue.
My story goes.
Had happy running TugaPower Rom
Decided to install MultiRom and Ubuntu.
Then after running for a week or so, decided to wipe and install TugaPower alone.
All has run well for a while. Decided to wipe and make a fresh install.
MultiRom I am unable to fully remove, even trying to replace with original TWRP.
When I try to flash the ROM, I get reported that this cant be installed as the model is . not bacon or A0001. error 7
I have edited the updater-script to not make a check on the model and it then installs.
When i reboot it goes straight back to the recovery!!!
I have tried reinstalling multirom and then flashing but again it keeps going to the recovery.
Ive tried to fastboot the original OS via https://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541, but fastboot reports `FAILED (remote: Device not unlocked cannot flash or erase)`
(Full output at bottom)
The install all end with 1 and multirom could see the roms
ive tried extracting just the .img and flashing to get going
im at a loss, any help much appreciated
Code:
[email protected]:sudo fastboot oem unlock
...
OKAY [ 0.009s]
finished. total time: 0.009s
[email protected]:/home/steve/Downloads/cm# ./flash-all.sh
target reported max download size of 1073741824 bytes
sending 'modem' (57457 KB)...
OKAY [ 1.805s]
writing 'modem'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 1.806s
target reported max download size of 1073741824 bytes
sending 'sbl1' (273 KB)...
OKAY [ 0.011s]
writing 'sbl1'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.013s
target reported max download size of 1073741824 bytes
sending 'dbi' (11 KB)...
OKAY [ 0.004s]
writing 'dbi'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.006s
target reported max download size of 1073741824 bytes
sending 'aboot' (445 KB)...
OKAY [ 0.015s]
writing 'aboot'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.017s
target reported max download size of 1073741824 bytes
sending 'rpm' (186 KB)...
OKAY [ 0.008s]
writing 'rpm'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.010s
target reported max download size of 1073741824 bytes
sending 'tz' (325 KB)...
OKAY [ 0.012s]
writing 'tz'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.015s
target reported max download size of 1073741824 bytes
sending 'LOGO' (328 KB)...
OKAY [ 0.013s]
writing 'LOGO'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.015s
target reported max download size of 1073741824 bytes
sending 'oppostanvbk' (10240 KB)...
OKAY [ 0.322s]
writing 'oppostanvbk'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.323s
target reported max download size of 1073741824 bytes
sending 'recovery' (9968 KB)...
OKAY [ 0.314s]
writing 'recovery'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.315s
target reported max download size of 1073741824 bytes
erasing 'system'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.000s
target reported max download size of 1073741824 bytes
sending 'boot' (7274 KB)...
OKAY [ 0.231s]
writing 'boot'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.232s
target reported max download size of 1073741824 bytes
erasing 'cache'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.000s
target reported max download size of 1073741824 bytes
erasing 'userdata'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.000s
rebooting...
finished. total time: 0.050s
Boot the phone into fastboot mode and open cmd with administrative rights and go into the adb platform tools folder and enter in cmd fastboot OEM -device info
kallum7 said:
Boot the phone into fastboot mode and open cmd with administrative rights and go into the adb platform tools folder and enter in cmd fastboot OEM -device info
Click to expand...
Click to collapse
C:\Windows\system32>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.016s]
finished. total time: 0.016s
now run script
C:\Windows\system32>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Windows\system32>fastboot boot C:\Users\Steve\Downloads\twrp-3.2.3-0-bacon.img
downloading 'boot.img'...
OKAY [ 0.438s]
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.438s
C:\Windows\system32>fastboot oem unlock
...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Windows\system32>fastboot boot C:\Users\Steve\Downloads\twrp-3.2.3-0-bacon.img
< waiting for device >
downloading 'boot.img'...
OKAY [ 0.438s]
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.438s
C:\Windows\system32>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.016s]
finished. total time: 0.016s
Try another USB micro cable
Thank you for your reply.
I have tried two other cables I have and still having the same issues
Are you using Linux or windows
kallum7 said:
Are you using Linux or windows
Click to expand...
Click to collapse
I have both available,
I am trying each OS at each new try
Ran all three of the files on here to get the triggers to true / true
https://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
I then ran `fastboot boot twrp.img`
This gave me twrp and i then installed a rom as normal...
im back up and running
thanks for all your patience and help
stevieag said:
Ran all three of the files on here to get the triggers to true / true
https://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
I then ran `fastboot boot twrp.img`
This gave me twrp and i then installed a rom as normal...
im back up and running
thanks for all your patience and help
Click to expand...
Click to collapse
Im having problems again..
OTA lineage update came up..
i clicked to install.
Phone restarted and immediately went to the multirom twrp screen.
I have had this in the past and have needed to install from this screen but i couldnt find the file to install
So on phone restart it loops back to the multirom twrp
I can still adb and fastboot see below
Code:
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.006s]
finished. total time: 0.006s
on fastboot boot twrp.img
it seems to restart but sits on fastboot screen
story:
on fastboot
send command
fastboot screen goes brighter
Any ideas
I have tried windows and linux plus 2 cables
What would be ideal would to completely clear multirom from my phone and get back to stock or stock twrp so i can flash as normal
stevieag said:
Im having problems again..
OTA lineage update came up..
i clicked to install.
Phone restarted and immediately went to the multirom twrp screen.
I have had this in the past and have needed to install from this screen but i couldnt find the file to install
So on phone restart it loops back to the multirom twrp
I can still adb and fastboot see below
Code:
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.006s]
finished. total time: 0.006s
on fastboot boot twrp.img
it seems to restart but sits on fastboot screen
story:
on fastboot
send command
fastboot screen goes brighter
Any ideas
I have tried windows and linux plus 2 cables
What would be ideal would to completely clear multirom from my phone and get back to stock or stock twrp so i can flash as normal
Click to expand...
Click to collapse
sorted
https://forum.xda-developers.com/oneplus-one/general/tool-oneplus-one-return-to-stock-t2970390
Ultimate fix
Right, i ended with a boot loop i couldnt sort
so
i downloaded - cm-13.1.2-ZNH2KAS3P0-bacon-signed-fastboot.zip (to big for upload)
This contains all the files you need including os
Once in fastboot
volume up and power or in recovery
Code:
adb reboot bootloader
In windows in a terminal (search next to start menu for cmd, right click on the pop up cmd and choose open as admin)
Run each of these
Code:
fastboot flash aboot emmc_appsboot.mbn
fastboot flash LOGO logo.bin
fastboot flash modem NON-HLOS.bin
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash oppostanvbk static_nvbk.bin
fastboot flash tz tz.mbn
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata_64G.img
fastboot reboot
THIS IS FOR 64GB ONLY with 16GB change userdata_64.img to the file userdata.img
In Linux open terminal, drop to root
Code:
sudo su -
you can then run above files or run flash-radio.sh
Code:
./flash-radio.sh
weirly may still need sudo!!!
This will install the os etc and you are back to stock (although old)
Now you can install twrp as normal
Code:
fastboot flash recovery twrp.img
Code:
fastboot reboot
here you should be back to normal twrp recovery
Copy over your ROM and Gapps
Install as normal twrp and done
im now on pie with 3.2.2 twrp and gapps 9
This installed ROMs that were complaining of not the right model, error 7, error 255 ........ and on
All sorted, in fact ive installed 3 different roms now without fails
I have a strange issue on my moto g3 (XT1550) after installing RR 9 official 19052019 ROM with pico gapps after some days I can't access the twrp, I mean when I'm booting on twrp it's only show the logo of twrp and then reboot the system.
Also the developers option not present in ROM or it disappeared.
Phone is non rooted.
Not able to reset phone.
Not able to change lock screen.
Anyone knows what's going on?
Phone status.
& errors when trying to install twrp.
Fastboot boot twrp.img also can't boot recovery.
After fastboot -w command,
again flashed recovery and it booted but can't mount system, data & cache, showing invalid argument.
It solved by repairing file system.
Now working fine.
$ su
[email protected]:/data/data/com.termux/files/home # fastboot boot /sdcard/twrp.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
downloading 'boot.img'...
OKAY [ 0.462s]
booting...
OKAY [ 0.156s]
finished. total time: 0.619s
[email protected]:/data/data/com.termux/files/home #
fastboot -w
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
wiping cache...
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 1.928s]
erasing 'cache'...
OKAY [ 0.019s]
finished. total time: 1.947s
[email protected]:/data/data/com.termux/files/home #
fastboot flash recovery /sdcard/twrp.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 268435456 bytes
sending 'recovery' (8176 KB)...
OKAY [ 0.506s]
writing 'recovery'...
OKAY [ 0.142s]
finished. total time: 0.648s
[email protected]:/data/data/com.termux/files/home #
Please help!!
I have messed up my oneplus one bacon
I was using lineageos 16 and all was fine. For some dumb reason like getting 'Screen mirroring' feature, I decided to go back to lineageos 15.1. Somewhere in the instructions I [mis]read, a clean wipe is recommended to go back to previous release.
I wiped all my partitions from twrp. That's why, my system partition is gone.
I tried a bunch of things after searching on these forums for similar symptoms, but no luck as of yet.
I tried to flash the stock recovery and stock ROM
Recovery flash was successful and so I am on CWM, but the ROM failed as the system partition could not be mounted/unmounted
Now, my phone's state -- I have Cyanogen recovery
ADB devices does not work.
> adb reboot bootloader
adb server is out of date. killing...
* daemon started successfully *
error: device not found
Fastboot works, but am unable to unlock my bootloader, not sure how it got locked.
>fastboot oem unlock
OKAY [ 0.009s]
Finished. Total time: 0.019s
It simple reboots to the recovery without unlocking
>fastboot oem device-info
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.021s]
Finished. Total time: 0.028s
I tried sideload to upload files like stock ROM, I get verification errors.
I was hoping this thread would help me. But not sure how to apply this fix
I am unable to flash or boot as I get the following error
> fastboot flash recovery recovery.img
target reported max download size of 1073741824 bytes
sending 'recovery' (9968 KB)...
OKAY [ 0.317s]
writing 'recovery'...
FAILED (remote: Device not unlocked cannot flash or erase)
>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.318s]
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.339s
Please help!!!
Hi all,
I need help with my phone being stuck in fastboot...
Today i tried to flash Lineage OS using this guide. I did this from scratch with a stock phone, not rooted or unlocked or anything.
Everything went fine until Step 4 under ROM Installation. My phone refused to start into TWRP. It didn't even start the lineage rom, it always just warned me about my phone being a risk because it is unlocked and then proceeded to start the stock Rom. So i tried the whole thing over and over again a couple of times, always with the same result. Then i read someone writing about how he first had to use wipe > format data before flashing the Rom in TWRP in the Guide Thread (Page 3). So i tried that too. But i must have done something wrong because it now led to my phone restarting into a fastboot mode, which didn't look like the fastboot screen it booted into before e.g. different font style, black background without the little android thingy on the top, and it now says "oem_locked" again.
When i try to boot the system it says:
No bootable A/B slot
Failed to boot Linux, falling back to fastboot
Boot up failed
I tried to unlock the phone again using "fastboot oem unlock MYKEY" on my computer it says:
(bootloader) feature disabled
OKAY [ 0.003s]
finished. total time: 0.004s
So i tried to flash back to the stock image as described here.
But i get a "remote failure" error after every command.
Here is the output from Powershell:
PS D:\Minimal ADB and Fastboot> ./fastboot oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.002s
PS D:\Minimal ADB and Fastboot> ./fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (45 KB)...
OKAY [ 0.005s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.055s
PS D:\Minimal ADB and Fastboot> ./fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (7419 KB)...
OKAY [ 0.249s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Invalid partition name aboot
(bootloader) Invalid partition name rpm
(bootloader) Invalid partition name tz
(bootloader) Invalid partition name devcfg
(bootloader) Invalid partition name cmnlib
(bootloader) Invalid partition name cmnlib64
(bootloader) Invalid partition name keymaster
(bootloader) Invalid partition name prov
(bootloader) Invalid partition name sbl1
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.437s
PS D:\Minimal ADB and Fastboot> ./fastboot flash modem_a NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem_a' (65396 KB)...
OKAY [ 2.147s]
writing 'modem_a'...
(bootloader) Invalid partition name modem_a
FAILED (remote failure)
finished. total time: 2.158s
PS D:\Minimal ADB and Fastboot> ./fastboot flash fsg_a fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg_a' (11684 KB)...
OKAY [ 0.379s]
writing 'fsg_a'...
(bootloader) Invalid partition name fsg_a
FAILED (remote failure)
finished. total time: 0.392s
PS D:\Minimal ADB and Fastboot> ./fastboot erase modemst1
erasing 'modemst1'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.010s
PS D:\Minimal ADB and Fastboot> ./fastboot erase modemst2
erasing 'modemst2'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.027s
PS D:\Minimal ADB and Fastboot> ./fastboot flash dsp_a adspso.bin
target reported max download size of 536870912 bytes
sending 'dsp_a' (16384 KB)...
OKAY [ 0.531s]
writing 'dsp_a'...
(bootloader) Invalid partition name dsp_a
FAILED (remote failure)
finished. total time: 0.538s
PS D:\Minimal ADB and Fastboot> ./fastboot flash logo_a logo.bin
target reported max download size of 536870912 bytes
sending 'logo_a' (1285 KB)...
OKAY [ 0.046s]
writing 'logo_a'...
(bootloader) Invalid partition name logo_a
FAILED (remote failure)
finished. total time: 0.057s
PS D:\Minimal ADB and Fastboot> ./fastboot flash boot_a boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (32768 KB)...
OKAY [ 1.085s]
writing 'boot_a'...
(bootloader) Invalid partition name boot_a
FAILED (remote failure)
finished. total time: 1.093s
PS D:\Minimal ADB and Fastboot> ./fastboot flash dtbo_a dtbo.img
target reported max download size of 536870912 bytes
sending 'dtbo_a' (1760 KB)...
OKAY [ 0.058s]
writing 'dtbo_a'...
(bootloader) Invalid partition name dtbo_a
FAILED (remote failure)
finished. total time: 0.066s
PS D:\Minimal ADB and Fastboot> ./fastboot flash system_a system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system_a' (258873 KB)...
OKAY [ 8.397s]
writing 'system_a'...
(bootloader) Invalid partition name system_a
FAILED (remote failure)
finished. total time: 8.409s
PS D:\Minimal ADB and Fastboot> ./fastboot flash system_a system.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system_a' (249260 KB)...
OKAY [ 8.139s]
writing 'system_a'...
(bootloader) Invalid partition name system_a
FAILED (remote failure)
finished. total time: 8.153s
PS D:\Minimal ADB and Fastboot> ./fastboot flash system_a system.img_sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system_a' (262081 KB)...
OKAY [ 8.677s]
writing 'system_a'...
(bootloader) Invalid partition name system_a
FAILED (remote failure)
finished. total time: 8.693s
PS D:\Minimal ADB and Fastboot> ./fastboot flash system_a system.img_sparsechunk.3
target reported max download size of 536870912 bytes
sending 'system_a' (262141 KB)...
OKAY [ 8.533s]
writing 'system_a'...
(bootloader) Invalid partition name system_a
FAILED (remote failure)
finished. total time: 8.540s
PS D:\Minimal ADB and Fastboot> ./fastboot flash system_a system.img_sparsechunk.4
target reported max download size of 536870912 bytes
sending 'system_a' (257008 KB)...
OKAY [ 8.366s]
writing 'system_a'...
(bootloader) Invalid partition name system_a
FAILED (remote failure)
finished. total time: 8.374s
PS D:\Minimal ADB and Fastboot> ./fastboot flash system_a system.img_sparsechunk.5
target reported max download size of 536870912 bytes
sending 'system_a' (242308 KB)...
OKAY [ 7.906s]
writing 'system_a'...
(bootloader) Invalid partition name system_a
FAILED (remote failure)
finished. total time: 7.912s
PS D:\Minimal ADB and Fastboot> ./fastboot flash system_a system.img_sparsechunk.6
target reported max download size of 536870912 bytes
sending 'system_a' (262060 KB)...
OKAY [ 8.585s]
writing 'system_a'...
(bootloader) Invalid partition name system_a
FAILED (remote failure)
finished. total time: 8.596s
PS D:\Minimal ADB and Fastboot> ./fastboot flash system_a system.img_sparsechunk.7
target reported max download size of 536870912 bytes
sending 'system_a' (255940 KB)...
OKAY [ 8.420s]
writing 'system_a'...
(bootloader) Invalid partition name system_a
FAILED (remote failure)
finished. total time: 8.436s
PS D:\Minimal ADB and Fastboot> ./fastboot flash system_a system.img_sparsechunk.8
target reported max download size of 536870912 bytes
sending 'system_a' (261918 KB)...
OKAY [ 8.584s]
writing 'system_a'...
(bootloader) Invalid partition name system_a
FAILED (remote failure)
finished. total time: 8.594s
PS D:\Minimal ADB and Fastboot> ./fastboot flash system_a system.img_sparsechunk.9
target reported max download size of 536870912 bytes
sending 'system_a' (83808 KB)...
OKAY [ 2.728s]
writing 'system_a'...
(bootloader) Invalid partition name system_a
FAILED (remote failure)
finished. total time: 2.738s
PS D:\Minimal ADB and Fastboot> ./fastboot flash system_b system_b.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system_b' (262140 KB)...
OKAY [ 8.349s]
writing 'system_b'...
(bootloader) Invalid partition name system_b
FAILED (remote failure)
finished. total time: 8.357s
PS D:\Minimal ADB and Fastboot> ./fastboot flash system_b system_b.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system_b' (262024 KB)...
OKAY [ 8.368s]
writing 'system_b'...
(bootloader) Invalid partition name system_b
FAILED (remote failure)
finished. total time: 8.376s
PS D:\Minimal ADB and Fastboot> ./fastboot flash system_b system_b.img_sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system_b' (43968 KB)...
OKAY [ 1.414s]
writing 'system_b'...
(bootloader) Invalid partition name system_b
FAILED (remote failure)
finished. total time: 1.423s
PS D:\Minimal ADB and Fastboot> ./fastboot flash vendor_a vendor.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'vendor_a' (259120 KB)...
OKAY [ 8.524s]
writing 'vendor_a'...
(bootloader) Invalid partition name vendor_a
FAILED (remote failure)
finished. total time: 8.531s
PS D:\Minimal ADB and Fastboot> ./fastboot flash vendor_a vendor.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'vendor_a' (147628 KB)...
OKAY [ 4.843s]
writing 'vendor_a'...
(bootloader) Invalid partition name vendor_a
FAILED (remote failure)
finished. total time: 4.850s
PS D:\Minimal ADB and Fastboot> ./fastboot flash oem_a oem.img
target reported max download size of 536870912 bytes
sending 'oem_a' (103040 KB)...
OKAY [ 3.370s]
writing 'oem_a'...
(bootloader) Invalid partition name oem_a
FAILED (remote failure)
finished. total time: 3.377s
PS D:\Minimal ADB and Fastboot> ./fastboot flash oem_b oem_other.img
target reported max download size of 536870912 bytes
sending 'oem_b' (185456 KB)...
OKAY [ 6.032s]
writing 'oem_b'...
(bootloader) Invalid partition name oem_b
FAILED (remote failure)
finished. total time: 6.044s
PS D:\Minimal ADB and Fastboot> ./fastboot erase userdata
erasing 'userdata'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.016s
PS D:\Minimal ADB and Fastboot> ./fastboot erase DDR
erasing 'DDR'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.005s
PS D:\Minimal ADB and Fastboot> ./fastboot oem fb_mode_clear
...
OKAY [ 0.001s]
finished. total time: 0.005s
PS D:\Minimal ADB and Fastboot> ./fastboot reboot
rebooting...
finished. total time: 0.001s
And now i'm pretty lost and don't really know how to proceed. It would be great if somebody hat some advice
This situation takes place when you switch to the empty Slot B without copying contents of Slot A there. I have exactly the same problem and my phone has been put to the box, until a proper solution can be found, if any. I have downloaded blankflash files recently, but the command line shows only "waiting for device", in such a way I havent managed to use it propely.
kry52 said:
This situation takes place when you switch to the empty Slot B without copying contents of Slot A there. I have exactly the same problem and my phone has been put to the box, until a proper solution can be found, if any. I have downloaded blankflash files recently, but the command line shows only "waiting for device", in such a way I havent managed to use it propely.
Click to expand...
Click to collapse
Thats unfortunat
I tried the blankflash too, with the same outcome. Then i guess i'll do the same.... put in the box and wait for a solution, if there will ever be any :fingers-crossed:
Anyway... thank you for the reply
Tried switching slots?
To check active slot
Code:
fastboot getvar current-slot
To change to slot a
Code:
fastboot --set-active=a
To change to slot b
Code:
fastboot --set-active=b
To toggle from active to inactive Slot
Code:
fastboot set_active other
Sent from my mata using XDA Labs
---------- Post added at 02:39 AM ---------- Previous post was at 02:38 AM ----------
kry52 said:
... I have downloaded blankflash files recently, but the command line shows only "waiting for device", in such a way I havent managed to use it propely.
Click to expand...
Click to collapse
Was phone in emergency download mode?
Sent from my mata using XDA Labs
In this mode phone will not be in EDL, but you can place it into by issuing `fastboot oem blankflash`. See `fastboot oem help` Afterwards you should be able to restore phone using blank flash file, see this HERE
@sd_shadow Switching slots does nothing. I always get the "remote failure" error massage. And when i'm trying to switch to slot b it tells me there wouldn't be a slot b.
Here the output of the suggested commands:
D:\Minimal ADB and Fastboot>fastboot getvar current-slot
current-slot:
finished. total time: 0.000s
D:\Minimal ADB and Fastboot>fastboot --set-active=a
Setting current slot to 'a'...
(bootloader) Command is not allowed
FAILED (remote failure)
finished. total time: -0.000s
D:\Minimal ADB and Fastboot>fastboot --set-active=b
Slot b does not exist. supported slots are:
a
D:\Minimal ADB and Fastboot>fastboot set_active other
Setting current slot to 'a'...
(bootloader) Command is not allowed
FAILED (remote failure)
finished. total time: -0.000s
D:\Minimal ADB and Fastboot>
@Geoffrey I was able to put it into EDL. It shows up in my Device Manager as Qualcomm HS-USB QDLoader 9008 but when im trying to run the blankflash like in the guide i get this result:
D:\Downloads\Moto\blankflash_ocean_PDOS29.114-134-2 (1)>.\qboot.exe blank-flash
Motorola qboot utility version 3.40
[ 0.000] Opening device: \\.\COM4
[ 0.001] Detecting device
[ 4.007] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.007] Check qboot_log.txt for more details
[ 4.009] Total time: 4.012s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error
D:\Downloads\Moto\blankflash_ocean_PDOS29.114-134-2 (1)>pause
Drücken Sie eine beliebige Taste . . .
Here is the Log File:
**** Log buffer [000001] 2019-11-02_19:45:56 ****
[ 0.000] Opening device: \\.\COM4
[ 0.002] Detecting device
[ 4.010] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.010] Check qboot_log.txt for more details
[ 4.011] Total time: 4.014s
[ 4.011]
[ 4.011] qboot version 3.40
[ 4.011]
[ 4.011] DEVICE {
[ 4.011] name = "\\.\COM4",
[ 4.011] flags = "0x64",
[ 4.011] addr = "0x61FE4C",
[ 4.011] api.bnr = "0xFF2F20",
[ 4.011] }
[ 4.011]
[ 4.011]
[ 4.011] Backup & Restore {
[ 4.011] num_entries = 0,
[ 4.011] restoring = "false",
[ 4.011] backup_error = "not started",
[ 4.011] restore_error = "not started",
[ 4.011] }
[ 4.011]
Any suggestions?
bondu546 said:
@sd_shadow Switching slots does nothing. I always get the "remote failure" error massage. And when i'm trying to switch to slot b it tells me there wouldn't be a slot b.
Here the output of the suggested commands:
D:\Minimal ADB and Fastboot>fastboot getvar current-slot
current-slot:
finished. total time: 0.000s
D:\Minimal ADB and Fastboot>fastboot --set-active=a
Setting current slot to 'a'...
(bootloader) Command is not allowed
FAILED (remote failure)
finished. total time: -0.000s
D:\Minimal ADB and Fastboot>fastboot --set-active=b
Slot b does not exist. supported slots are:
a
D:\Minimal ADB and Fastboot>fastboot set_active other
Setting current slot to 'a'...
(bootloader) Command is not allowed
FAILED (remote failure)
finished. total time: -0.000s
D:\Minimal ADB and Fastboot>
@Geoffrey I was able to put it into EDL. It shows up in my Device Manager as Qualcomm HS-USB QDLoader 9008 but when im trying to run the blankflash like in the guide i get this result:
D:\Downloads\Moto\blankflash_ocean_PDOS29.114-134-2 (1)>.\qboot.exe blank-flash
Motorola qboot utility version 3.40
[ 0.000] Opening device: \\.\COM4
[ 0.001] Detecting device
[ 4.007] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.007] Check qboot_log.txt for more details
[ 4.009] Total time: 4.012s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error
D:\Downloads\Moto\blankflash_ocean_PDOS29.114-134-2 (1)>pause
Drücken Sie eine beliebige Taste . . .
Here is the Log File:
**** Log buffer [000001] 2019-11-02_19:45:56 ****
[ 0.000] Opening device: \\.\COM4
[ 0.002] Detecting device
[ 4.010] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.010] Check qboot_log.txt for more details
[ 4.011] Total time: 4.014s
[ 4.011]
[ 4.011] qboot version 3.40
[ 4.011]
[ 4.011] DEVICE {
[ 4.011] name = "\\.\COM4",
[ 4.011] flags = "0x64",
[ 4.011] addr = "0x61FE4C",
[ 4.011] api.bnr = "0xFF2F20",
[ 4.011] }
[ 4.011]
[ 4.011]
[ 4.011] Backup & Restore {
[ 4.011] num_entries = 0,
[ 4.011] restoring = "false",
[ 4.011] backup_error = "not started",
[ 4.011] restore_error = "not started",
[ 4.011] }
[ 4.011]
Any suggestions?
Click to expand...
Click to collapse
I have the same issue x.x is really hard to unbrick this phone at this point :C my phone boot into a diferent type of bootloader with the START in green color and no android logo, and my pc doesn't recognize de device...
jodytejada said:
I have the same issue x.x is really hard to unbrick this phone at this point :C my phone boot into a diferent type of bootloader with the START in green color and no android logo, and my pc doesn't recognize de device...
Click to expand...
Click to collapse
My PC shows "Android ADB Interface" when the phone is loaded in this emergency fastboot mode, but anyway - ADB commands don't work, fastboot commands bring failures because of the partitions issue and more than that - this emergency fastboot loader is oem_locked and can't be unlocked in a standard way
Will this 134-2 file work on a phone updated to 134-4 ??
Geofferey said:
In this mode phone will not be in EDL, but you can place it into by issuing `fastboot oem blankflash`. See `fastboot oem help` Afterwards you should be able to restore phone using blank flash file, see this HERE
Click to expand...
Click to collapse
This is a 134-2 blankflash file - will it work on 134-4 ??
Despite everyone else being able to flash to a different variant of the XT1955 firmware - apparently the Verizon XT1955-6 is OEM locked at the boot.img stage.
Currently there is no PDOS29.114-134-4 firmware to download at https://mirrors.lolinet.com/firmware.../official/VZW/ to repair it by a re-install of the firmware with - and one cannot install an earlier version . . . unless you know of a way . . .
Everything will re-flash but boot.img and dtbo.img
The Lenovo MOTO Smart Assistant comes back and says it is not supported . . . after recognizing it
Is there a way to re-set the OEM issues of the phone to take earlier versions of the OS - or other variants that you know of ??
Even factory reset is not available - I will look for a fastboot command that can do it - because that is all I can do - it boots right to fastboot now only
estofjlw said:
This is a 134-2 blankflash file - will it work on 134-4 ??
...
Click to expand...
Click to collapse
It should work for any XT1955-5
Sent from my ocean using XDA Labs
sd_shadow said:
It should work for any XT1955-5 /QUOTE]
OK I can try it. I have a xt1955-6 - Verizon
Everything flashes with a xt1955-5 RETUS firmware except the boot.img and dtbo.img
If blank flash is an OEM signed file - maybe it will push over the existing boot.img
I will see if in the middle of the flash - the oem get_unlock_data has changed with the retail bootloader on the phone
From what I saw in vars - some vars had changed in the bootloader
But what I read at https://forum.xda-developers.com/g5/help/how-to-develop-blank-flash-t3791525 it seems to say of the boot.img file is newer - the blank flash will fail
Click to expand...
Click to collapse
estofjlw said:
sd_shadow said:
It should work for any XT1955-5 /QUOTE]
OK I can try it. I have a xt1955-6 - Verizon
Everything flashes with a xt1955-5 RETUS firmware except the boot.img and dtbo.img
If blank flash is an OEM signed file - maybe it will push over the existing boot.img
I will see if in the middle of the flash - the oem get_unlock_data has changed with the retail bootloader on the phone
From what I saw in vars - some vars had changed in the bootloader
But what I read at https://forum.xda-developers.com/g5/help/how-to-develop-blank-flash-t3791525 it seems to say of the boot.img file is newer - the blank flash will fail
Click to expand...
Click to collapse
I believe the boot.img in the blank flash can be updated too.
Sent from my mata using XDA Labs
Click to expand...
Click to collapse
What happend when the device is not recognized by the blank flash and onlly appears Moto ADB Interface???
jodytejada said:
What happend when the device is not recognized by the blank flash and onlly appears Moto ADB Interface???
Click to expand...
Click to collapse
It's not in Emergency Download Mode
PC should see it as
Qualcomm QHSUSB_Bulk or qloader
Sent from my ocean using XDA Labs
VZW update locks out any other firmware
sd_shadow said:
estofjlw said:
I believe the boot.img in the blank flash can be updated too. /QUOTE]
That would be great except if it updates to newer than the RETUS firmware boot.img - which will cause a pre-flash error instead of an oem boot.img error
I have not tried yet . . . but the RETUS 134-4 firmware is older than the VZW 134-4 firmware which has not been posted on the https://mirrors.lolinet.com/firmware/moto/ocean/official/VZW/ website.
No other ocean variant I looked at is newer either - some have the 11/04 modify date - but inside the folder it is not the 134-4 firmware that is for that date.
Verizon's 134-4 update came down between November 2 and 4 in three updates as 1, 2 and then straight to 4 - behind my back on wifi and since the bootloader is still oem locked - and because it is Verizon - not eligible for an unlock code from Motorola due the Verizon ordering it as an oem branded phone, unless I can make it look like a RETUS bootloader to Motorola in the middle of the flash while the bootloader can be unlocked so they provide an unlock code for it _ I am betting I am screwed until the https://mirrors.lolinet.com/firmware/moto/ocean/official/VZW/ site has a post for the 134-4 VZW firmware
Right now it boots to fastboot mode immediately - so I do not want to make it worse and actually brick it
I looked inside the blank flash zip and there is no boot.img - but from my understanding the blank flash contacts the boot img and updates it - to what and how I do not know - in my case it needs to "downgrade" it an earlier date - I sure I had Magisk so it could patch the boot.img and fix this. See https://www.reddit.com/r/MotoG/comments/cdsbw6/quick_reference_moto_g7_power_manually_flashing/
The trouble is of course there is no access to ADB copy, push and pull commands in fastboot
I have a XT1955-5 True Factory unlocked Retail US Phone on the way - and this one will have to be shelved
Click to expand...
Click to collapse
Click to expand...
Click to collapse
sd_shadow said:
It's not in Emergency Download Mode
PC should see it as
Qualcomm QHSUSB_Bulk or qloader
Sent from my ocean using XDA Labs
Click to expand...
Click to collapse
Any solution at this point? or onlly a brick to my collection?
sd_shadow said:
estofjlw said:
I believe the boot.img in the blank flash can be updated too.
Click to expand...
Click to collapse
Well I have my answer . . . the Verizon XT1955-6 version restricts using blankflash and it will not go in EDL at all
C:\>fastboot oem blankflash
...
(bootloader) command restricted
FAILED (remote failure)
Since I can flash the RETUS bootloader can anyone suggest another work around to get past boot.img and DTBO.img
Click to expand...
Click to collapse
I'm having a similar problem. After flashing firmware is stuck in fastboot with the OEM relocked and the unlock code does not unlock it. Mine is retus xt1955-5
KeRbYRoK said:
I'm having a similar problem. After flashing firmware is stuck in fastboot with the OEM relocked and the unlock code does not unlock it. Mine is retus xt1955-5
Click to expand...
Click to collapse
Look for retus blank flash
Thanks man.
Ok what I did was hit it with blankflash. That still wouldn't clear out the faulty bootloader that was from the wrong firmware. But I found a new Android 10 firmware flashed it all checks were good and I'm sending this message from it right now.