bootloader is bricked

Search This thread

codGmer

Senior Member
Apr 27, 2015
59
2
0
Hello,

I have bricked my bootloader in the past to refresh my bootloader. I have unbricked my phone to bootloader 1.03 with blank flash. Now when i try to flash, erase do ANYTHING it won't allow me because my OEM_LOCKED state. If i try to unlock my bootloader it says:

Code:
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [  0.032s]
finished. total time: 0.036s

but there is no android installed.

When i try to flash a stock rom it says:

Code:
C:\Users\nick\Desktop\total firmware>fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (1848 KB)...
OKAY [  0.068s]
writing 'logo'...
(bootloader) Invalid partition name logo
FAILED (remote failure)
finished. total time: 0.088s

C:\Users\nick\Desktop\total firmware>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [  0.540s]
writing 'boot'...
(bootloader) Invalid partition name boot
FAILED (remote failure)
finished. total time: 0.576s

C:\Users\nick\Desktop\total firmware>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [  0.548s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.568s

C:\Users\nick\Desktop\total firmware>fastboot flash dsp adspso.bin
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [  0.532s]
writing 'dsp'...
(bootloader) Invalid partition name dsp
FAILED (remote failure)
finished. total time: 0.560s

C:\Users\nick\Desktop\total firmware>fastboot flash oem oem.img
target reported max download size of 536870912 bytes
sending 'oem' (124713 KB)...
OKAY [  3.993s]
writing 'oem'...
(bootloader) Invalid partition name oem
FAILED (remote failure)
finished. total time: 4.017s

C:\Users\nick\Desktop\total firmware>fastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (261790 KB)...

Everything is 'invalid partition name'.


when i try to brick my bootloader again to install try again it says

Code:
target max-sparse-size: 256MB
sending 'sbl1' (264 KB)...
OKAY [  0.020s]
writing 'sbl1'...
(bootloader) Invalid partition name sbl1
FAILED (remote failure)
finished. total time: 0.036s
rebooting...

And when i try to flash another bootloader it says:
Code:
PS C:\Users\nick\Desktop\total firmware> fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (3651 KB)...
OKAY [  0.141s]
writing 'bootloader'...
(bootloader) validating: bootloader.default.xml ...
(bootloader) Invalid partition name aboot
(bootloader) will fail: flash:aboot
FAILED (remote failure)
finished. total time: 0.250s
PS C:\Users\nick\Desktop\total firmware>

please help
 
Last edited:

codGmer

Senior Member
Apr 27, 2015
59
2
0
Yes i know, but i cant flash any partitions or fix Them. I have Read the whole threath but i cannot find a solution.
 
Last edited:

givitago

Member
May 13, 2017
25
16
0
Yes i know, but i cant flash any partitions or fix Them. I have Read the whole threath but i cannot find a solution.

Did you run all stock steps in order? In particular this one first:

Code:
 fastboot flash partition gpt.bin

That will restore your partition table which seems to be messed up. Make sure you try to restore firmware version that was last working for you.

If your phone is completely wiped and you have no backups of ALL of the partitions, I doubt you can recover as some of the partitions have phone specific data for IMEIs and such.
 

codGmer

Senior Member
Apr 27, 2015
59
2
0
Did you run all stock steps in order? In particular this one first:

Code:
 fastboot flash partition gpt.bin

That will restore your partition table which seems to be messed up. Make sure you try to restore firmware version that was last working for you.

If your phone is completely wiped and you have no backups of ALL of the partitions, I doubt you can recover as some of the partitions have phone specific data for IMEIs and such.

I dont think all is wiped but when i try to flash the gpt.bin it says 'cannot find partition gpt'
 

Vs1607

Member
Jun 16, 2017
19
1
3
Did you run all stock steps in order? In particular this one first:



I dont think all is wiped but when i try to flash the gpt.bin it says 'cannot find partition gpt'
I too have this question bro .... Plus help me if you find a solution ... I m a newbie... Nd face the same problem as yours
 

givitago

Member
May 13, 2017
25
16
0
Sounds like fastboot expects a working partition table to start with then.

I would boot into twrp from fastboot (from an image on your PC) and use adb shell to take a look at what the flash looks like (fdisk -l command). You may have to restore the partition table first via sgdisk or dd. I've never done it and I'm no expert on this stuff but Google is your friend. General linux forums are just as helpful as android specific forums as at this level, we aren't even talking about android.

Good luck.
 

codGmer

Senior Member
Apr 27, 2015
59
2
0
Sounds like fastboot expects a working partition table to start with then.

I would boot into twrp from fastboot (from an image on your PC) and use adb shell to take a look at what the flash looks like (fdisk -l command). You may have to restore the partition table first via sgdisk or dd. I've never done it and I'm no expert on this stuff but Google is your friend. General linux forums are just as helpful as android specific forums as at this level, we aren't even talking about android.

Good luck.

Im affraid i already tried booting twrp but without success.
 

codGmer

Senior Member
Apr 27, 2015
59
2
0
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8952-B1.03(*)
(bootloader) product: athene_16mp
(bootloader) board: athene_16mp
(bootloader) secure: yes
(bootloader) hwrev: P2A
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG QE13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8952
(bootloader) serialno: 74f9d6fa
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: A420B70000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) hyp.git: hyp.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) aboot.git: git=MBM-NG-VB1.03-0-gb44c0ee
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.147s
 

king_priithvi

New member
Jan 7, 2018
1
0
0
hey bro , did you get any solution of this problem?
i am getting
fastboot reason : failed to initialize partition table
any solution?
 
Last edited:

Outfield303

Senior Member
Nov 6, 2016
286
220
43
I think you're flashing older bootloader & GPT then it is already installed on your device;
take a look here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
from that thread download the latest ROM and firstly flash GPT and boot-loader by following command:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
but however after flashing the latest firmware the current blankflash that we have won't work, because GPT and boot-loader version is higher.
now after you flashed the GPT and bootloader then flash the whole firmware by following commands:
Code:
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 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 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
Now once you flashed it then you're good to go:good:
 

king_prithvi

New member
Jan 7, 2018
1
0
0
i cant flash anything , my android is not installed
it kept saying
AP Fastboot Flash Mode (Secure)
Fastboot Reason: Failed to initialize partition table
ERROR: No BootImage Found. skip to fastboot
boot up failed
 

kiyip

Member
Sep 24, 2015
23
3
3
I am getting an error when I try to flash twrp. I want to make sure I am doing it right

in the linux terminal I typed this
adb reboot bootloader
then
fastboot flash recovery twrp-3.2.1-motorola-x4.img

then I got this error

target reported max download size of 536870912 bytes
sending 'recovery' (19276 KB)...
OKAY [ 0.447s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.453s


has anyone else run into this problem. Am I doing something wrong?
 

echo92

Senior Member
Jan 1, 2017
3,732
1,989
223
Plymouth
I am getting an error when I try to flash twrp. I want to make sure I am doing it right

in the linux terminal I typed this
adb reboot bootloader
then
fastboot flash recovery twrp-3.2.1-motorola-x4.img

then I got this error

target reported max download size of 536870912 bytes
sending 'recovery' (19276 KB)...
OKAY [ 0.447s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.453s


has anyone else run into this problem. Am I doing something wrong?

What device do you have? I'm guessing it's a Moto X4 from the TWRP name?

Are you on Nougat or Oreo? From looking at this thread, you've got 2 different build: https://forum.xda-developers.com/moto-x4/development/dev-testing-t3707432

If you are running a X4, you may have better luck over there rather than here on the Moto G4 forums, as there's more users familiar with the A/B partitioning on the Moto X4.
 

Mono27zs

New member
Feb 16, 2018
1
0
0
got the same problem any luck yet?

Any luck yet? I got a suggestion that the problem could only get fixed flashing the memory of the phone directly with this kind of device... (search for the octopus box, I cant post links yet im new here) but im lost and they say that thing is expensive... I really want my phone to be saved on my computer. My case is exactly the same as you.... oem locked and failed partition everything and remote failure.:eek::eek::eek:
 

mrsojitra

Member
Apr 8, 2018
7
0
0
SOLVED!! Failed to initialize partition table

;) ;) ;) ;) ;) ;) ;) ;) ;) ;) ;) ;) ;) ;) ;) ;)..
First of all convert phone to hard brick to Softbrick...
After that if you want to bootup phone than..IT shows bootloader log::
Failed to initialize partition Table
SOLUTION:-
1) Download Minimal ADB Drivers , gpt.bin, Motorola Device driver
For link mail me on [email protected]
2.) Now Install adb and motorola drivers .
3.) Copy gpt.bin file in ADB folder in installed drive.
4.) Open Minimal ADB and Fastboot.exe
Now Run the following command

fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot

The cell phone should restart after this if you do not type the last code and enter if still yes it is not just hang up and call to enter the fastboot.
Now YOUR PROBLEM SOLVED
 

girirajy

New member
Jun 4, 2016
2
1
0
I dont think all is wiped but when i try to flash the gpt.bin it says 'cannot find partition gpt'

Even I got the same error. Its because adb couldn't find the gpt.bin file in the adb folder from where you had executed the command window.
Copy the gpt.biin file in that folder and try again, that should work.
 
  • Like
Reactions: master_of_game

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    I dont think all is wiped but when i try to flash the gpt.bin it says 'cannot find partition gpt'

    Even I got the same error. Its because adb couldn't find the gpt.bin file in the adb folder from where you had executed the command window.
    Copy the gpt.biin file in that folder and try again, that should work.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone