My Moto G XT1033 Hard Bricked

[wasconet]

I was having a problem with my Moto G XT1033 yesterday as most apps get closed automatically at launch. this morning i installed AVG to do a scan, i also used Root file manager to clean up some files (junks, duplicates etc)

I then did a restart after which my phone will not boot to home screen again.

It boots up showing the boot animation bout after that i get a black blank screen which back light on.

Things i have tried

1. did cache partition wipe
2. did wipe/restore

all to no avail

I then downloaded a stock ROM from Blur_Version.221.21.56.falcon_umtsds.AsiaRetail.en.03.zip

downloaded minimal ADB and fastbook.

- put the phone to fastboot
- on android system recovery mode i clicked apply update from ADB
then on PC i confirmed it can see my phone by typing adb devices, my phone get listed.

I then do adb sideload Blur_Version.221.21.56.falcon_umtsds.AsiaRetail.en.03.zip

Finding update package.........
Opening update package........
Verifying update package........
Installing update..........

Then i get Package expects build fingerprint of motorola/falcon_asia_ds/falcon_umtsds:5.0./LXB22.46-28/30:user/release-keys or motorola/falcon_asia_ds/falcon_umtsds:5.1/PB23.13-56:user/release-keys; this device has motorola/falcon_asia_ds/falcon_umtsds:5.1/LPBS

E:Error in /sodeload/package.zip (status 7)

Install aborted.

Device Details
Moto G
XT1033
build LPBS23
Indian version
running Android 5.1.1 (running latest android for the device, i only do OTA updates/upgrades)
Not rooted
no custom OS


I will really appreciate any help to get the device up again

 

[Professor Gibbins]

I was having a problem with my Moto G XT1033 yesterday as most apps get closed automatically at launch. this morning i installed AVG to do a scan, i also used Root file manager to clean up some files (junks, duplicates etc)

I then did a restart after which my phone will not boot to home screen again.

It boots up showing the boot animation bout after that i get a black blank screen which back light on.

Things i have tried

1. did cache partition wipe
2. did wipe/restore

all to no avail

I then downloaded a stock ROM from Blur_Version.221.21.56.falcon_umtsds.AsiaRetail.en.03.zip

downloaded minimal ADB and fastbook.

- put the phone to fastboot
- on android system recovery mode i clicked apply update from ADB
then on PC i confirmed it can see my phone by typing adb devices, my phone get listed.

I then do adb sideload Blur_Version.221.21.56.falcon_umtsds.AsiaRetail.en.03.zip

Finding update package.........
Opening update package........
Verifying update package........
Installing update..........

Then i get Package expects build fingerprint of motorola/falcon_asia_ds/falcon_umtsds:5.0./LXB22.46-28/30:user/release-keys or motorola/falcon_asia_ds/falcon_umtsds:5.1/PB23.13-56:user/release-keys; this device has motorola/falcon_asia_ds/falcon_umtsds:5.1/LPBS

E:Error in /sodeload/package.zip (status 7)

Install aborted.

Device Details
Moto G
XT1033
build LPBS23
Indian version
running Android 5.1.1 (running latest android for the device, i only do OTA updates/upgrades)
Not rooted
no custom OS


I will really appreciate any help to get the device up again

Firstly, I would like to point out that your phone is merely soft-bricked. Hard bricks are much more serious and happen when your phone does not turn on at all. So, in future, please do not complain about a hard brick where there is none.

Onto the actual issue, it appears to be an easy fix. The problem was simply that you were attempting to sideload an OTA update, as opposed to flashing full firmware, which will not work. So all you need to do is flash the full factory firmware using fastboot flash, not adb sideload. To do this, flash factory firmware from here using the fastboot commands linked on that thread.

 

[wasconet]

Firstly, I would like to point out that your phone is merely soft-bricked. Hard bricks are much more serious and happen when your phone does not turn on at all. So, in future, please do not complain about a hard brick where there is none.

Onto the actual issue, it appears to be an easy fix. The problem was simply that you were attempting to sideload an OTA update, as opposed to flashing full firmware, which will not work. So all you need to do is flash the full factory firmware using fastboot flash, not adb sideload. To do this, flash factory firmware from here using the fastboot commands linked on that thread.

im sorry for the false alarm.


Thanks! :good: