moto xt1033 showing remote failure while flashing - Android Q&A, Help & Troubleshooting

A couple of days ago, I got an error on my phone (Motorola XT1033) saying that it cannot load the home screen. So, I restarted it in order to resolve the issue. However, it didn't reboot and since then it has been stuck in the Motorola logo.
I tried to do recovery or factory reset, but all the options lead to the same Motorola logo with no luck.
The only option that is working is AP Fastboot. I managed to unlock the bootloader by getting an unlock code from Motorola's website and using the mfastboot command. So I assume that the fastboot command is working since it detects the devices; however, I couldn't make ADB command to work since it give the error: 'device not found'.
Anyway, the second step is to flash the phone. According to this question, I should be able to do that. However, when I am running the command fastboot flash partition gpt.bin, I am getting the following result:
(bootloader) Variable not supported!
target max-download-size: 30MB
sending 'partition' (32 KB)...
OKAY [ 0.022s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 0.154s
I have been searching for days to solve this problem, but nothing yet! I don't know which part I am doing wrong.

Related

Locked & bricked xt1524

Hi guys,
So I have made the mistake of relocking the bootloader after unlocking it. Now my phone is bricked, and the bootloader is locked.
I have downloaded the stock rom XT1524_RETEUALL_MOTOE2(4G-LTE)_5.0.2_LXI22.50-13_cid7_subsidy-DEFAULT_CFC.xml, the cid and product reference are matching, also my phone was on 5.0.2.
But my phone won't flash, for example, I get :
"C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.3
target reported max download size of 268435456 bytes
sending 'system' (254911 KB)...
OKAY [ 8.012s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.072s"
when I input some of the commands for flashing.
My bootloader logs show :
"failed to validate system image"
I don't understand why it would be doing that as the stock is matching, I have checked on several threads and I can't find any concrete solution for fixing this.
Please help.
Thanks,
No one has a clue ?
Having the same prolem with my XT1521 please somebody helppppppppppp
up..
try to use mfastboot, its included in my modem flash zip (https://mega.nz/#!pglHWQ6B!zYNHtO9qERuFqrbv40M62kgpULS2TK53m_vB3msCC6g ), Windows only.
also there is a guide here: http://forum.xda-developers.com/mot...e-restore-moto-e-2015-stock-firmware-t3044936
and flash in order as shown in the guide
Is Your Fastboot working or your phone completely bricked ?
Hi Gentlemen,
Thanks for the replies.
Sorry, all the above I've tried with mfastboot. It just won't flash it. Probably cause the phone is locked now.
The above is what it's returning.
Also I cannot unlock the phone anymore, it returns "FAILED (remote failure)"
"Check 'Allow OEM unlock' in Developper options"
Mine its also bricked, same situation, same problems :c

Oneplus x not booting into recovery - soft bricked(no os); please help!!

OnePlus X (Onyx) - Soft bricked
Boots into Fastboot mode, gets detected by PC.
No OS, No Recovery.
Problem: Recovery gets flashed successfully using adb and fastboot. But when trying to boot into recovery using commands, it says FAILED (remote:dtb not found); and when trying to boot into recovery using physical buttons, then it just stays on the OnePlus boot logo till eternity.
I tried using a flash tool as well(got from XDA), but the result is same.
Here is a look from cmd:
C:\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
C:\platform-tools>fastboot flash recovery twrp-3.0.2-0-onyx.img
target reported max download size of 536870912 bytes
sending 'recovery' (14758 KB)...
OKAY [ 0.466s]
writing 'recovery'...
OKAY [ 0.260s]
finished. total time: 0.728s
C:\platform-tools>fastboot boot twrp-3.0.2-0-onyx.img
downloading 'boot.img'...
OKAY [ 0.465s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.505s
I tried flashing twrp 2.8.7.0(onyx) but still I got the same error. (remote:dtb not found). No matter what, but it just won't boot into recovery.
How it happened:
Long back, I unlocked my bootloader, installed twrp recovery and also achieved root access. Then I flashed CM13. It was working quite fine. But then OOS 3(Official) came out for OnePlus X, so I decided to download it and flash it too. It was working all fine. But then I realised that I lost my root access and my recovery was changed back to stock OnePlus recovery. After that I tried for 2 days to flash twrp back, but I continued to get that (remote:dtb not found) error. It was quite desperate; then I thought to lock the bootloader back and unlocking it back again. But the moment I used the command "fastboot oem unlock", my phone didn't ask me for a yes or no, so I tried restarting it. But it was too late, my phone got soft-bricked till then. I am trying to fix this since days, PLEASE SOMEONE HELP!!
Try to create a Thread in the One Plus X Section .

Oneplus x soft bricked; won't boot into recovery (no os) please help!

OnePlus X (Onyx) - Soft bricked
Boots into Fastboot mode, gets detected by PC.
No OS, No Recovery.
Problem: Recovery gets flashed successfully using adb and fastboot. But when trying to boot into recovery using commands, it says FAILED (remote:dtb not found); and when trying to boot into recovery using physical buttons, then it just stays on the OnePlus boot logo till eternity.
I tried using a flash tool as well(got from XDA), but the result is same.
Here is a look from cmd:
C:\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
C:\platform-tools>fastboot flash recovery twrp-3.0.2-0-onyx.img
target reported max download size of 536870912 bytes
sending 'recovery' (14758 KB)...
OKAY [ 0.466s]
writing 'recovery'...
OKAY [ 0.260s]
finished. total time: 0.728s
C:\platform-tools>fastboot boot twrp-3.0.2-0-onyx.img
downloading 'boot.img'...
OKAY [ 0.465s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.505s
I tried flashing twrp 2.8.7.0(onyx) but still I got the same error. (remote:dtb not found). No matter what, but it just won't boot into recovery.
How it happened:
Long back, I unlocked my bootloader, installed twrp recovery and also achieved root access. Then I flashed CM13. It was working quite fine. But then OOS 3(Official) came out for OnePlus X, so I decided to download it and flash it too. It was working all fine. But then I realised that I lost my root access and my recovery was changed back to stock OnePlus recovery. After that I tried for 2 days to flash twrp back, but I continued to get that (remote:dtb not found) error. It was quite desperate; then I thought to lock the bootloader back and unlocking it back again. But the moment I used the command "fastboot oem unlock", my phone didn't ask me for a yes or no, so I tried restarting it. But it was too late, my phone got soft-bricked till then. I am trying to fix this since days, PLEASE SOMEONE HELP!!

Unlocking Bootloader and Installing TWRP Recovery Problems HELP

First off, I received this phone from a friend of mine who received it brand new from textnow through the mail. I went through the steps to unlock the bootloader and errors came of that, but on the device it says "Device is UNLOCKED. Status Code: 3" so i assumed the bootloader was already unlocked based on what i have already researched and found. If this is incorrect, let me know and i will answer accordingly.
Assuming that my assumption is right, I keep getting errors when i try to install twrp. either that, or it appears to do nothing.
Going by the instructions on the cyanogenmod wiki for flashing twrp, fastboot returns this when i enter the "fastboot flash recovery your_recovery_image.img" command where "twrp.img" was my image name and then does nothing:
C:\Users\Me\Downloads\android-sdk_r24.4.1-windows\android-sdk-windows\platform-tools>fastboot flash recovery 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' (6808 KB)...
OKAY [ 0.219s]
writing 'recovery'...
OKAY [ 0.302s]
finished. total time: 0.524s
I did the same with mfastboot and there are no errors, but it still does nothing:
C:\Users\Me\Downloads\mfastboot-v2>mfastboot flash recovery twrp.img
target max-sparse-size: 256MB
sending 'recovery' (10270 KB)...
OKAY [ 0.329s]
writing 'recovery'...
OKAY [ 0.448s]
finished. total time: 0.779s
I tried each of these a few times to no avail. Ive tried waiting at each step, tried the "fastboot reboot" and "mfastboot reboot" commands after the flash commands to where it booted straight up to android, tried the "fastboot reboot" and "mfastboot reboot" commands after the flash commands where i held the buttons to go back to fastboot mode and nothing.
Other things to note:
-Power+Volume down boots to a screen that has "AP Fastboot Flash Mode (Secure)" in red letters where there is device information at the bottom and I can only cycle through one option at a time at the top (if that makes sense).
-Selecting "Restart Bootloader" and "Recovery Mode" brings me back to this same screen mentioned.
Thank you in advance for your replies. I am completely new to this and appreciate the help.
I am only able to boot into fastboot mode and not the bootloader if that was not clear previously. I was up until 6am last night (or this morning) trying to figure it out and it didnt cross my mind this may be my actual issue. Thanks.

[oneplus 6][android 9.0] probleme fastboot

C:\Android>fastboot devices
317251cf fastboot
C:\Android>fastboot erase data
erasing 'data'...
FAILED (remote: Check device console.)
finished. total time: 0.004s
I want to erase data because i can't do this unbrick method (https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665)
despite that it worked before.
this problem appeared after many successful uses of the method mentioned above. The problem appeared after wanting to install an older rom on my OP6 for downgrade the play services
I am desperate, I searched for hours and hours on the internet so if a little genius goes through, a little help would not be refused

Categories

Resources