Hard bricked Moto G XT1032 (bootloader v41.13) - Moto G Q&A, Help & Troubleshooting
My Moto G bootloader (v41.13 from 4.4.4 upgrade) is corrupted and the device is recognized by computer as "qhsusb_bulk". So I installed Riffbox JTAG drivers and now it's recognized as "Qualcomm HS-USB QDLoader 9008". I tried to run many times the flashblank tool but I keep getting errors. This is what I get:
Code:
C:\qualcomm_boot_tool>.\qboot.exe blank-flash
opening device: \\.\COM19
OKAY [ -0.000s]
greeting device for command mode
OKAY [ -0.000s]
identifying device
...serial = 0x3B93E14
...chip-id = 0x800 (MSM8226)
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.010s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ 0.010s]
validating files
OKAY [ -0.000s]
switching to download mode
OKAY [ -0.000s]
greeting device for image downloading
OKAY [ -0.000s]
sending programmer
OKAY [ 0.010s]
flashing singleimage
[B]FAILED (blank-flash:sdl-transfer-image:sdl-hello:invalid HDLC frame)[/B]
or:
Code:
C:\qualcomm_boot_tool>.\qboot.exe blank-flash
opening device: \\.\COM19
OKAY [ 0.010s]
greeting device for command mode
OKAY [ 0.000s]
identifying device
...serial = 0x3B93E14
...chip-id = 0x800 (MSM8226)
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.010s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ 0.010s]
validating files
OKAY [ 0.000s]
switching to download mode
OKAY [ 0.010s]
greeting device for image downloading
OKAY [ 0.000s]
sending programmer
OKAY [ 0.010s]
flashing singleimage
[B]FAILED (blank-flash:sdl-transfer-image:sdl-hello:error sending packet)[/B]
debug log:
Code:
I - opening device: \\.\COM16
D - \\.\COM16 opened
I - OKAY [ 0.004s]
I - greeting device for command mode
D - Receiving HELLO packet
D - TARGET PROTOCOL INFO:
D - name: sahara
D - version: 2
D - compatible version: 1
D - maximum packet length: 1024
D - mode: Image transfer pending
D - Switching to "Command" mode
D - Sending HELLO_RESP packet
D - Receiving COMMAND_READY packet
I - OKAY [ 0.026s]
I - identifying device
D - Reading device serial number
D - Sending CMD_EXEC packet, cmd=1
D - Receiving CMD_EXEC_RESP packet
D - Reading device id
D - Sending CMD_EXEC packet, cmd=2
D - Receiving CMD_EXEC_RESP packet
D - Reading SBL SV
D - Sending CMD_EXEC packet, cmd=7
D - Receiving CMD_EXEC_RESP packet
I - ...serial = 0x3B93E14
I - ...chip-id = 0x800 (MSM8226)
I - ...chip-rev = 0x0
I - ...sv-sbl = 0x0
I - OKAY [ 0.043s]
I - finding files
I - ...programmer = programmer.mbn
I - ...singleimage = singleimage.bin
I - OKAY [ 0.020s]
I - validating files
I - OKAY [ 0.003s]
I - switching to download mode
D - Sending CMD_SWITCH_MODE packet
I - OKAY [ 0.005s]
I - greeting device for image downloading
D - Receiving HELLO packet
D - TARGET PROTOCOL INFO:
D - name: sahara
D - version: 2
D - compatible version: 1
D - maximum packet length: 1024
D - mode: Image transfer pending
D - Sending HELLO_RESP packet
I - OKAY [ 0.031s]
I - sending programmer
D - Loading file: programmer.mbn
D - Receiving READ_DATA packet
D - Sending 80 bytes
D - Receiving READ_DATA packet
D - Sending 4096 bytes
D - Receiving READ_DATA packet
D - Sending 4096 bytes
D - Receiving READ_DATA packet
D - Sending 4096 bytes
D - Receiving READ_DATA packet
D - Sending 4096 bytes
D - Receiving READ_DATA packet
D - Sending 4096 bytes
D - Receiving READ_DATA packet
D - Sending 4096 bytes
D - Receiving READ_DATA packet
D - Sending 4096 bytes
D - Receiving READ_DATA packet
D - Sending 4096 bytes
D - Receiving READ_DATA packet
D - Sending 4096 bytes
D - Receiving READ_DATA packet
D - Sending 4096 bytes
D - Receiving READ_DATA packet
D - Sending 4096 bytes
D - Receiving READ_DATA packet
D - Sending 3452 bytes
D - Receiving END_IMAGE_TX packet
D - Sending DONE packet
D - Receiving DONE_RESP packet
I - OKAY [ 0.070s]
I - flashing singleimage
D - Loading file: singleimage.bin
D - Pinging RDL...
D - \\.\COM16 closed
FAILED (blank-flash:sdl-transfer-image:sdl-hello:invalid HDLC frame)
Any developer can help me to figure out how to fix this?
I have the same problem.
I see from your signature that the device was upgraded to 4.4.4 like mine. I understand the 4.4.4 upgrade repartitions the phone, perhaps this also changes the bootloader section so that blank-flash tool does not have the correct file to flash?
If so, hopefully a new file will become available.
I'd like to ask the question in the thread for the blank-flash tool but don't have enough posts yet to to do so.
I have this too it happened after i tried to flash gpe firmware possibly 4.4.4 (dont know) and tried bootloader corrupter to try to downgrade the bootloader but then got this currently cant do anything.
Yeah probably the tool doesn't work due to 4.4.4 upgrade, maybe the boot partition needs to be repartitioned or something like that, in order to flash singleimage.bin.
I'm pretty sure there is (or there will be) a way to unbrick our device. The flash-blank tool I used comes from 4.3 JellyBean tar.gz official firmware, if our argument is right we need a 4.4.4 tar.gz package to extract a working flash-blank tool, but I never saw a tar.gz firmware after 4.3... I also thought to try with the factory cable but probably nothing would change unless you bricked with low battery (mine was around 50%). A lot of people bricked and got that kind of error so I'm sure a solution is coming. Let's wait for a fix, maybe Boss442 can help us as well.:good:
my xt1033 brinked on bootloader 41.11
fastboot dont write nothing on then..
i recive OK feedback, but nothing change..
i try use another versions but i recive 'downgrade' msg's
where is the 41.13 image?,
think i will can instal it in my device, because is a upgrade..
maybe work.
i put various logs about this on my thread
see: http://forum.xda-developers.com/moto-g/help/help-downgrading-cm4-4-4-to-stock4-4-3-t2804228
hansdepaula said:
my xt1033 brinked on bootloader 41.11
fastboot dont write nothing on then..
i recive OK feedback, but nothing change..
i try use another versions but i recive 'downgrade' msg's
where is the 41.13 image?,
think i will can instal it in my device, because is a upgrade..
maybe work.
i put various logs about this on my thread
see: http://forum.xda-developers.com/moto-g/help/help-downgrading-cm4-4-4-to-stock4-4-3-t2804228
Click to expand...
Click to collapse
Wrong thread, here we discuss about hard brick, you soft bricked. I think you just need to pick up the motoboot.img from a 4.4.4 firmware to get the 41.13 bootloader.
no man, my bootloader as corrupted..
this dont write nothing on my phone..
my partition is all 'RAW' system..
i try flash 4.4.4 files taked on OTA, not work..
nothing change..
i cant enter in recovery or anything, only bootloader..
we are together on bricked..
hard or soft i d'nt know but my (and your?) device stay unusable. :/
if you have time to waste,
see my thread: http://forum.xda-developers.com/moto-g/help/help-downgrading-cm4-4-4-to-stock4-4-3-t2804228
hansdepaula said:
no man, my bootloader as corrupted..
this dont write nothing on my phone..
my partition is all 'RAW' system..
i try flash 4.4.4 files taked on OTA, not work..
nothing change..
i cant enter in recovery or anything, only bootloader..
we are together on bricked..
hard or soft i d'nt know but my (and your?) device stay unusable. :/
if you have time to waste,
see my thread: http://forum.xda-developers.com/moto-g/help/help-downgrading-cm4-4-4-to-stock4-4-3-t2804228
Click to expand...
Click to collapse
Seems something is gone wrong with partitioning... You could try the bootloader bricker tool but even if it works you will get a completely dead Moto G like us so I think it's not a good idea... The flashblank tool can't fix the 41.13 bootloader for now, we are all waiting for a solution. Stay tuned.
moto g muerto
hola amigos, disculpen por escribir en español. sucede que instale la rom GPE 4.4.2 y actualice a 4.4.4. luego, no se porque, quize regresar a GPE 4.4.2, y fue ahi donde se me jodio el bootloader. trate de instalar todas las rom que se me cruzo por el camino y nada. luego encontre el post de boss442 e hice todos los pasos y el resultado es como se decribe al inicio. los mismo errores. espero que pronto algun desarrollador nos ayude a resucitar nuestros moto g. realmente ya no se que mas hacer. gracias
diosdiablo said:
hola amigos, disculpen por escribir en español. sucede que instale la rom GPE 4.4.2 y actualice a 4.4.4. luego, no se porque, quize regresar a GPE 4.4.2, y fue ahi donde se me jodio el bootloader. trate de instalar todas las rom que se me cruzo por el camino y nada. luego encontre el post de boss442 e hice todos los pasos y el resultado es como se decribe al inicio. los mismo errores. espero que pronto algun desarrollador nos ayude a resucitar nuestros moto g. realmente ya no se que mas hacer. gracias
Click to expand...
Click to collapse
Don't despair. My sixth sense tell me we can solve this issue with an updated singleimage.bin
Please be patient, if we are lucky we have to wait weeks... otherwise months. I can't do nothing until an official 4.4.4 full image (not OTA) will be released. Stay tuned (or buy a new device).
I'm too hardbricked my moto g with blbrick, but i have a lower bootloader, 41.11, it's from 4.4.3, i suppose, does anyone can extract it from stock rom of us.retail.umts?
i can unpack some files from firmwares, may it can help?
kenji3111 said:
I'm too hardbricked my moto g with blbrick, but i have a lower bootloader, 41.11, it's from 4.4.3, i suppose, does anyone can extract it from stock rom of us.retail.umts?
i can unpack some files from firmwares, may it can help?
Click to expand...
Click to collapse
Did you get error? It's strange, the old tool should work with the 4.4.3...
oversleeper said:
Did you get error? It's strange, the old tool should work with the 4.4.3...
Click to expand...
Click to collapse
no, it's not working, the same error
where can i find the needed files in firmware?
kenji3111 said:
no, it's not working, the same error
where can i find the needed files in firmware?
Click to expand...
Click to collapse
I will post those file when they will be available... At the moment the last available is for 4.4.2...
oversleeper said:
I will post those file when they will be available... At the moment the last available is for 4.4.2...
Click to expand...
Click to collapse
can you post it, just for try?
kenji3111 said:
can you post it, just for try?
Click to expand...
Click to collapse
I can't, it doesn't exist. You must wait a few weeks or more.
qpst
May be QPST may help us?
I tried it, the phone is stuck on download mode and if you try to flash something you will get "Could Not Communicate with Flash Programmer". I don't wanna try more, the risk to mess up my device even more is high with a such program. Unfortunately nobody can/want help us with our issue, we have to wait until a new blankflash tool will be released...
oversleeper said:
I tried it, the phone is stuck on download mode and if you try to flash something you will get "Could Not Communicate with Flash Programmer". I don't wanna try more, the risk to mess up my device even more is high with a such program. Unfortunately nobody can/want help us with our issue, we have to wait until a new blankflash tool will be released...
Click to expand...
Click to collapse
my also gives me the same error
Me sumo al pedido, tengo un xt1032 brickeado probando kernels. Solo lo detecta como Hs-Usb QUalcomm
Desde ya gracias, un abrazo.
Me too brick mine (xt1032) changing kernel in Slimkat 4.4.4. Only is detected HS-USB QUALCOMM.
If anyone want try a solution with my Moto G, just tell me.
Thanks in advance.
Related
Moto G dead Help! [SOLVED]
Hi, mi moto G suddently dead... i will try to share the history
Suddently my moto g don't start after doing a downgrade, only if i plug on my pc show a driver (qhsusb_bulk) on xda very people have this problem so i download the qualcomm drivers... in the firmware folder for my stock phone, have some things (...)\mbm\blankflash
so i run blankflash.bat and my phone now go to the fastboot :victory:
but show as locked, they dont let me flash nothing and i can't unlock, my imei is 00000000000000000000
and don't start (Failed to initialize partition table)
anyone can help me?
here some pics:
{
"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"
}
after 30 attempts using the same method (via fastboot) the same firmware the same pc. the phone reboot bootloader and show unlocked, let me flash all the system and work good ._. really i don't know what is going on... but works :highfive: EDIT: yes, work using the .bat on 4.4.2 not 4.3 so the problem is the bootloader who i can't downgrade... maybe i make a guide to save the phone EDIT2: found the problem, never, NEVER flash the .mbn files on the firmware folder, only flash motoboot who take care of these flash files
I've had my shares of problems with that mbn files myself. And after I was searching more things about them - I did notice that Moto X users have the same problems. The thing is that once you upgrade those files, you can't downgrade them.
moto g bricked hi, i'm sorry, but i need help urgently. I unlocked the bootloader and flashed an international firmware so i can update to 4.4.2, since kitkat is not available in my country yet. then i tried to root my phone using superboot-windows.bat, and when the phone restarted it showd the moto logo, but it faded to black. so i turned it off, but now it doesn't turn on. is there a way to turn it on via adb or fastboot from windows? please help i'm panicking...
darkeingel said: I've had my shares of problems with that mbn files myself. And after I was searching more things about them - I did notice that Moto X users have the same problems. The thing is that once you upgrade those files, you can't downgrade them. Click to expand... Click to collapse u cant downgrade them until you blank-flash the bootloader... the problem is you really dont need to flash the .mbn files because motoboot file do that and is downgradable cancheritos said: hi, i'm sorry, but i need help urgently. I unlocked the bootloader and flashed an international firmware so i can update to 4.4.2, since kitkat is not available in my country yet. then i tried to root my phone using superboot-windows.bat, and when the phone restarted it showd the moto logo, but it faded to black. so i turned it off, but now it doesn't turn on. is there a way to turn it on via adb or fastboot from windows? please help i'm panicking... Click to expand... Click to collapse view if in the pc show as qhsusb_bulk and i will explain how to unbrick
open multi failed hi everytime i tried the blank-flash.bat it shows this log: from Boss442 to XDA opening device: \\.\COM40 OKAY [ 0.002s] greeting device for command mode ReadFile() failed, error=31 opening device: \\.\COM40 OKAY [ 0.003s] greeting device for command mode opening device: \\.\COM40 OKAY [ 0.002s] greeting device for command mode opening device: \\.\COM40 OKAY [ 0.004s] greeting device for command mode ReadFile() failed, error=31 opening device: \\.\COM40 OKAY [ 0.002s] greeting device for command mode opening device: \\.\COM40 OKAY [ 0.002s] greeting device for command mode ReadFile() failed, error=31 opening device: \\.\COM40 OKAY [ 0.004s] greeting device for command mode opening device: \\.\COM40 OKAY [ 0.003s] greeting device for command mode OKAY [ 0.974s] identifying device ...serial = 0x1D18785 ...chip-id = 0x800 (MSM8226) ...chip-rev = 0x0 ...sv-sbl = 0x0 OKAY [ 0.009s] finding files ...programmer = programmer.mbn ...singleimage = singleimage.bin OKAY [ 0.006s] validating files OKAY [ 0.002s] switching to download mode OKAY [ 0.006s] greeting device for image downloading OKAY [ 0.004s] sending programmer OKAY [ 0.013s] flashing singleimage Target LOG: Open multi failed, unknown error Target ERROR: 7 - Open multi failed, unknown error Failed to open multi image, status = 7 FAILED (sdl-transfer-image:send-image:sdl-open-multi:error opening multi image) Presione una tecla para continuar . . . someone can help me?
Boss442 said: after 30 attempts using the same method (via fastboot) the same firmware the same pc. the phone reboot bootloader and show unlocked, let me flash all the system and work good ._. really i don't know what is going on... but works :highfive: EDIT: yes, work using the .bat on 4.4.2 not 4.3 so the problem is the bootloader who i can't downgrade... maybe i make a guide to save the phone EDIT2: found the problem, never, NEVER flash the .mbn files on the firmware folder, only flash motoboot who take care of these flash files Click to expand... Click to collapse Did you get back you data(like photoes、music)?Please tell me because I'm facing the same problem.Thank you!
gavinft said: Did you get back you data(like photoes、music)?Please tell me because I'm facing the same problem.Thank you! Click to expand... Click to collapse The data is formatted when you clean userdata partition Enviado desde mi Moto G mediante Tapatalk
I hope it will be solved soon.
Minervamc said: I hope it will be solved soon. Click to expand... Click to collapse i forgot to mark as solved, sorry
will be lesson in here....... i have problem...boot loop on flash cm11
Boss442 said: i forgot to mark as solved, sorry Click to expand... Click to collapse No problem.
xkorex said: hi everytime i tried the blank-flash.bat it shows this log: from Boss442 to XDA opening device: \\.\COM40 OKAY [ 0.002s] greeting device for command mode ReadFile() failed, error=31 opening device: \\.\COM40 OKAY [ 0.003s] greeting device for command mode opening device: \\.\COM40 OKAY [ 0.002s] greeting device for command mode opening device: \\.\COM40 OKAY [ 0.004s] greeting device for command mode ReadFile() failed, error=31 opening device: \\.\COM40 OKAY [ 0.002s] greeting device for command mode opening device: \\.\COM40 OKAY [ 0.002s] greeting device for command mode ReadFile() failed, error=31 opening device: \\.\COM40 OKAY [ 0.004s] greeting device for command mode opening device: \\.\COM40 OKAY [ 0.003s] greeting device for command mode OKAY [ 0.974s] identifying device ...serial = 0x1D18785 ...chip-id = 0x800 (MSM8226) ...chip-rev = 0x0 ...sv-sbl = 0x0 OKAY [ 0.009s] finding files ...programmer = programmer.mbn ...singleimage = singleimage.bin OKAY [ 0.006s] validating files OKAY [ 0.002s] switching to download mode OKAY [ 0.006s] greeting device for image downloading OKAY [ 0.004s] sending programmer OKAY [ 0.013s] flashing singleimage Target LOG: Open multi failed, unknown error Target ERROR: 7 - Open multi failed, unknown error Failed to open multi image, status = 7 FAILED (sdl-transfer-image:send-image:sdl-open-multi:error opening multi image) Presione una tecla para continuar . . . someone can help me? Click to expand... Click to collapse Did you get your problem sloved?I've met the familar error "FAILED (sdl-transfer-image:send-image:sdl-open-multi:error reading packet)".What did you do next?
gavinft said: Did you get your problem sloved?I've met the familar error "FAILED (sdl-transfer-image:send-image:sdl-open-multi:error reading packet)".What did you do next? Click to expand... Click to collapse Same problem here. My Moto G is dead
Hello !!! Some solution to problem moto g ?
Boss442 said: Hi, mi moto G suddently dead... i will try to share the history Suddently my moto g don't start after doing a downgrade, only if i plug on my pc show a driver (qhsusb_bulk) on xda very people have this problem so i download the qualcomm drivers... in the firmware folder for my stock phone, have some things (...)\mbm\blankflash so i run blankflash.bat and my phone now go to the fastboot :victory: but show as locked, they dont let me flash nothing and i can't unlock, my imei is 00000000000000000000 and don't start (Failed to initialize partition table) anyone can help me? here some pics: Click to expand... Click to collapse do you have MBM_CI files? as i can see by your moto g bootlaoder version which is 41.19. correct me if i wrong... how did you flashed i mean there is no such solution for Lollipop, how did you do it? if you have solution why don't you share it with others?
@sahir1993 - V41.19 is the Bootloader version included with GPE 5.1. It's available as motoboot.img in the GPE 5.1 Factory Firmware Images.
Hello @Boss442 Can you explain better how do you unbrick your moto g i got the same problem with mine, you can pm me and we can speak on spanish. Enviado desde mi XT1063 mediante Tapatalk
lost101 said: @sahir1993 - V41.19 is the Bootloader version included with GPE 5.1. It's available as motoboot.img in the GPE 5.1 Factory Firmware Images. Click to expand... Click to collapse http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798 see this you 'll know what i'm asking for?
AYUDAAA Hola! Cada vez que ejecuto el archivo blankflash.bat me dice: "FAILED <sdl-transfer-image:send-image:sdl-open-multi:error reading packet>" y no puedo reestablecer el bootloader Ayuda por favor Moto G 1032 :crying:
Help! Error with the bootloader when installing new ROM
Hello, since yesterday I have a super inconvenient problem when trying to install again when trying to install any ROM on my device. Whenever I changed the ROM and never had problems, but yesterday when trying to be the Google Play Edition ROM it just the the following errors: Ps.: already have the bootloader unlocked and even redid the process of unlocking it and still the error persists, save me! C:\Users\Emerson\Videos\MOTO G>fastboot flash motoboot motoboot.img target reported max download size of 536870912 bytes sending 'motoboot' (1953 KB)... OKAY [ 0.109s] writing 'motoboot'... (bootloader) flashing tz ... (bootloader) flashing rpm ... (bootloader) flashing sdi ... (bootloader) flashing aboot ... (bootloader) flashing sbl1 ... OKAY [ 1.267s] finished. total time: 1.389s C:\Users\Emerson\Videos\MOTO G>fastboot flash logo logo.bin target reported max download size of 536870912 bytes sending 'logo' (1060 KB)... OKAY [ 0.101s] writing 'logo'... OKAY [ 0.099s] finished. total time: 0.208s C:\Users\Emerson\Videos\MOTO G>fastboot flash boot boot.img target reported max download size of 536870912 bytes sending 'boot' (10240 KB)... OKAY [ 0.414s] writing 'boot'... OKAY [ 0.808s] finished. total time: 1.230s C:\Users\Emerson\Videos\MOTO G>fastboot flash system system.img_sparsechunk.0 target reported max download size of 536870912 bytes erasing 'system'... (bootloader) Erase allowed in unlocked state OKAY [ 0.569s] sending 'system' (249247 KB)... OKAY [ 8.483s] writing 'system'... (bootloader) WARNING: System partition size is 0x34800000 (bootloader) Only multiples of 0x1000000 allowed for write-protection (bootloader) Write protect will not be enabled OKAY [ 7.111s] finished. total time: 16.177s C:\Users\Emerson\Videos\MOTO G>fastboot flash system system.img_sparsechunk.1 target reported max download size of 536870912 bytes erasing 'system'... (bootloader) Erase allowed in unlocked state OKAY [ 0.585s] sending 'system' (250602 KB)... OKAY [ 8.534s] writing 'system'... (bootloader) WARNING: System partition size is 0x34800000 (bootloader) Only multiples of 0x1000000 allowed for write-protection (bootloader) Write protect will not be enabled OKAY [ 6.785s] finished. total time: 15.917s C:\Users\Emerson\Videos\MOTO G>fastboot flash system system.img_sparsechunk.2 target reported max download size of 536870912 bytes erasing 'system'... (bootloader) Erase allowed in unlocked state OKAY [ 0.692s] sending 'system' (248370 KB)... OKAY [ 8.447s] writing 'system'... (bootloader) WARNING: System partition size is 0x34800000 (bootloader) Only multiples of 0x1000000 allowed for write-protection (bootloader) Write protect will not be enabled OKAY [ 6.338s] finished. total time: 15.490s C:\Users\Emerson\Videos\MOTO G>fastboot flash modem NON-HLOS.bin target reported max download size of 536870912 bytes sending 'modem' (47152 KB)... OKAY [ 1.656s] writing 'modem'... OKAY [ 1.242s] finished. total time: 2.906s C:\Users\Emerson\Videos\MOTO G>fastboot erase modemst1 erasing 'modemst1'... OKAY [ 0.061s] finished. total time: 0.065s C:\Users\Emerson\Videos\MOTO G>fastboot erase modemst2 erasing 'modemst2'... OKAY [ 0.092s] finished. total time: 0.097s C:\Users\Emerson\Videos\MOTO G>fastboot flash fsg fsg.mbn target reported max download size of 536870912 bytes sending 'fsg' (102 KB)... OKAY [ 0.097s] writing 'fsg'... OKAY [ 5.605s] finished. total time: 5.710s C:\Users\Emerson\Videos\MOTO G>fastboot erase cache ** Did you mean to fastboot format this partition? erasing 'cache'... OKAY [ 0.366s] finished. total time: 0.370s C:\Users\Emerson\Videos\MOTO G>fastboot erase userdata ** Did you mean to fastboot format this partition? erasing 'userdata'... OKAY [ 3.408s] finished. total time: 3.412s C:\Users\Emerson\Videos\MOTO G>fastboot reboot rebooting... finished. total time: 0.006s Click to expand... Click to collapse Eu já tenho todos os drivers instalados, portas USB funcionando corretamente e tudo mais... o problema é que ele simplesmente não inicia, ele trava no boot logo da Motorola/Google ao liga-lo e nunca inicia. O que fazer?
Cceli said: Hello, since yesterday I have a super inconvenient problem when trying to install again when trying to install any ROM on my device. Whenever I changed the ROM and never had problems, but yesterday when trying to be the Google Play Edition ROM it just the the following errors: Ps.: already have the bootloader unlocked and even redid the process of unlocking it and still the error persists, save me! Eu já tenho todos os drivers instalados, portas USB funcionando corretamente e tudo mais... o problema é que ele simplesmente não inicia, ele trava no boot logo da Motorola/Google ao liga-lo e nunca inicia. O que fazer? Click to expand... Click to collapse How to solve this? Como resolveu isso? Aqui a mesma coisa
Huawei p6 don't works
Hi everybody, yesterday I install cyanogenmod 11 unofficial in my Huawei p6, I have unlocked the bootloader, all works fine, I used for a long time, after that I started charging from the computetr USB port , I went out for 3 hours, when I back the smartphone was off, I turned on, but the Logo Huawei ascend don't change, , after I go to recovery mode, I had installed TWRP 2.8.1.0, when I try to wipe, a error ocurred, "unable to mount /data" and other folders, after that I try to restored the original recovery, I used Fastboot, but nothing happens, the flash is good, but when I reboot in recovery mode appears TWRP, please help me, this smarphone is new, I bought them one month ago. I'll be very grateful if someone helps me:crying::crying: When I flash boot and recovery. "F:\Programas\Ejecutables\Sdk y Eclipse para android\sdk\platform-tools>fastboot erase boot erasing 'boot'... OKAY [ 0.002s] finished. total time: 0.002s F:\Programas\Ejecutables\Sdk y Eclipse para android\sdk\platform-tools>fastboot flash boot boot.img target reported max download size of 838860800 bytes sending 'boot' (5658 KB)... OKAY [ 0.188s] writing 'boot'... OKAY [ 0.300s] finished. total time: 0.489s F:\Programas\Ejecutables\Sdk y Eclipse para android\sdk\platform-tools>fastboot erase recovery erasing 'recovery'... OKAY [ 0.005s] finished. total time: 0.005s F:\Programas\Ejecutables\Sdk y Eclipse para android\sdk\platform-tools>fastboot flash recovery recovery.img target reported max download size of 838860800 bytes sending 'recovery' (16384 KB)... OKAY [ 0.529s] writing 'recovery'... OKAY [ 0.664s] finished. total time: 1.195s"
try this try this forum out and if that is something you have tried pm me and ill help you to fix your problem http://forum.xda-developers.com/showthread.php?t=2534420
Didn't work Deltax82 said: try this forum out and if that is something you have tried pm me and ill help you to fix your problem http://forum.xda-developers.com/showthread.php?t=2534420 Click to expand... Click to collapse I was watching and I can not modify any folder in the root directory, eg put a file in "/ system", I reset the smarphone and the file disappears, I probe this command from the console windows "adb shell dmesg" and showed some errors, I think they are serious --------------------------------------------------------------------------------------------------------------------------------- <7> [104.0, recovery] [13.020177] EXT4-fs (mmcblk0p19): ext4_orphan_cleanup: deleting unreferenced inode <2> [104.0, recovery] [14.755787] EXT4-fs error (device mmcblk0p19): ext4_readdir: 214: inode # 113127: blo ck 460238: comm recovery: path (unknown): bad entry in directory: rec_len is smaller than minimal - offset = 0 (0), inode = 16777216, rec_len = 0, name_len = 0 <3> [104.0, recovery] [14.755814] Aborting journal on device mmcblk0p19-8. <2> [104.0, recovery] [14.755824] EXT4-fs (mmcblk0p19): Remounting filesystem read-only <2> [104.0, recovery] [14.823290] EXT4-fs error (device mmcblk0p19): ext4_readdir: 214: inode # 113247: blo ck 459687: comm recovery: path /data/data/de.robv.android.xposed.installer/app_webview: bad entry in direct ory: rec_len% 4 = 0 - offset = 0 (0), inode = 1118398749, rec_len = 55815, name_len = 0! --------------------------------------------------------------------------------------------------------------------------------- is a part, the there are more lines of this.
Format data Wipe Type 'Yes'
[Completed] Moto g xt1039 doesn't writes anything,
Saludos, Recientemente compré un MOTO G XT1039 que al principio no entraba al recovery, baje una infinidad de recoverys, ninguno conseguia flashearlo, logré hacerlo con la herramienta Mototools AIOV3, pero no puedo instalar roms, ni recovery, nada, el bootloader esta desbloqueado. logre bootear el TWRP con el comando fastboot boot recovery.img de ahi pruebo instalar los recovery o roms pero no los flashea, cuando enciende enciende como si no hubiera hecho nada. los errores que obtengo flasheando desde fastboot son "hab check failed for boot" "hab check failed for recovery" o "preflash validation failed" la version de recovery actual el Android System Recovery PLB23.13-17 El telefono antes de morir tenia 5.1 Aca el log de una instalacion de un firmware 4.4.4 C:\4.4.4>mfastboot flash partition gpt.bin sending 'partition' (32 KB)... OKAY [ 0.045s] writing 'partition'... Preflash validation failed FAILED (remote failure) finished. total time: 0.357s EN EL CELULAR: Version downgraded for primary_gpt (Estoy haciendo un downgrade asique este fallo estaría bien) C:\4.4.4>mfastboot flash motoboot motoboot.img sending 'motoboot' (1953 KB)... OKAY [ 0.124s] writing 'motoboot'... Motoboot: Preflash validation for tz Preflash validation failed FAILED (remote failure) finished. total time: 0.406s EN EL CELULAR: version downgraded for tz C:\4.4.4>mfastboot flash logo logo.bin sending 'logo' (1060 KB)... OKAY [ 0.112s] writing 'logo'... OKAY [ 0.086s] finished. total time: 0.198s C:\4.4.4>mfastboot flash boot boot.img sending 'boot' (10240 KB)... OKAY [ 0.409s] writing 'boot'... OKAY [ 0.647s] finished. total time: 1.057s EN EL CELULAR: hab check failed for boot C:\4.4.4>mfastboot flash recovery recovery.img sending 'recovery' (10240 KB)... OKAY [ 0.416s] writing 'recovery'... OKAY [ 0.638s] finished. total time: 1.056s EN EL CELULAR: hab check failed for recovery Hasta aca deberia estar una parte Ahora los comandos, este telefono es europeo asique debe llevar estos C:\4.4.4>mfastboot flash system system.img_sparsechunk.0 sending 'system' (248267 KB)... OKAY [ 7.857s] writing 'system'... OKAY [ 8.538s] finished. total time: 16.395s C:\4.4.4>mfastboot flash system system.img_sparsechunk.1 sending 'system' (248994 KB)... OKAY [ 7.873s] writing 'system'... OKAY [ 7.609s] finished. total time: 15.481s C:\4.4.4>mfastboot flash system system.img_sparsechunk.2 sending 'system' (257391 KB)... OKAY [ 8.132s] writing 'system'... OKAY [ 8.055s] finished. total time: 16.187s C:\4.4.4>mfastboot flash system system.img_sparsechunk.3 sending 'system' (20588 KB)... OKAY [ 0.732s] writing 'system'... OKAY [ 13.263s] finished. total time: 13.995s C:\4.4.4>mfastboot flash modem NON-HLOS.bin sending 'modem' (59132 KB)... OKAY [ 1.874s] writing 'modem'... OKAY [ 0.985s] finished. total time: 2.860s C:\4.4.4>mfastboot erase modemst1 erasing 'modemst1'... OKAY [ 0.011s] finished. total time: 0.011s C:\4.4.4> C:\4.4.4>mfastboot erase modemst2 erasing 'modemst2'... OKAY [ 0.011s] finished. total time: 0.012s C:\4.4.4>mfastboot flash fsg fsg.mbn sending 'fsg' (710 KB)... OKAY [ 0.065s] writing 'fsg'... OKAY [ 3.169s] finished. total time: 3.234s C:\4.4.4>mfastboot erase cache erasing 'cache'... OKAY [ 0.015s] finished. total time: 0.015s C:\4.4.4>mfastboot erase userdata erasing 'userdata'... OKAY [ 0.018s] finished. total time: 0.018s pero cuando reinicio solo se queda en la pantalla del bootloader desbloqueado, si pruebo instalando desde el recovery me pone que no hubo fallos pero cuando reinicio no pasa nada. cuando instalo un recovery no lo instala, los comandos no muestran errores, pero cuando reinicio no cambió el recovery ya he intentado todo, la unica herramienta que pudo modificarme en algo el telefono fue mototools AIO v3
Hello, please edit your post with an English translation. Kind regards Trafalgar Square XDA Assist
Procedura Root
Buongiorno ho effettuato la procedura descritta nel video su un MOTOROLA ONE MACRO XT2016-1 con bootloader sboccato ma eseguendo il comando fastboot flash boot boot.img mi viene visualizzato il seguente messaggio: C:\adb2>fastboot flash boot boot.img target reported max download size of 268435456 bytes sending 'boot' (32768 KB)... OKAY [ 1.302s] writing 'boot'... (bootloader) Invalid partition name boot FAILED (remote failure) finished. total time: 1.314s Qualcuno mi potrebbe aiutare a risolvere tale problema per effettuare il root. Tengo a precisare che non mi è possibile nemmeno installare una recovery TWRP in quanto non esiste per il mio device. Grazie
Amaranto1914 said: Buongiorno ho effettuato la procedura descritta nel video su un MOTOROLA ONE MACRO XT2016-1 con bootloader sboccato ma eseguendo il comando fastboot flash boot boot.img mi viene visualizzato il seguente messaggio: C:\adb2>fastboot flash boot boot.img target reported max download size of 268435456 bytes sending 'boot' (32768 KB)... OKAY [ 1.302s] writing 'boot'... (bootloader) Invalid partition name boot FAILED (remote failure) finished. total time: 1.314s Qualcuno mi potrebbe aiutare a risolvere tale problema per effettuare il root. Tengo a precisare che non mi è possibile nemmeno installare una recovery TWRP in quanto non esiste per il mio device. Grazie Click to expand... Click to collapse you should not flash the boot img nor the recovery image, you shoud boot fron recovery using fastboot boot "path to trpimg.img " once in recovery you can flash any twr zip file.