Related
Hi all, try to be brief, but not simple:
First, I swear I've read many posts with cases similar to mine and I tried so many commands and tricks without success, so I decide to publish mine.
I have an HTC Inspire 4G, AT&T, rooted, S-off, and running Trickdroid. After a while I decided to return it to the original stock. However, when using the RUU utility, I got an error message and my phone it ruined.
Try to summarize as much as possible the conditions and the current situation:
Environments: Windows XP, Windows 7, Mac OS.
Power not work
Power + Vol Down do not work.
If I connect it to the outlet orante LED turn on, and charging it, but I must not press any buttons at all, after ten minutes, HTC logo appears with four exclamation marks on the screen. However, Windows can not find the device until 5 or 10 minutes later.
I have access to fastboot commands, but not ADB. I tried to format the partitions, reflash, do recovery, recover partitions, etc, endless commands that do not give me a result.
The information obtained from the achievement of limited screen or fastboot commands is as follows:
ACE PVT HIP S-OFF RL
HBOOT-0.85.0019
MICROP-0438
RADIO-26.06.04.06_M
eMMC-BOOT
Dec 27 2012, 14:47:30
RUU
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.85.0019
(bootloader) version-baseband: 26.06.04.06_M
(bootloader) version-cpld: None
(bootloader) version-microp: 0438
(bootloader) version-main: 2.47.502.7
(bootloader) serialno: HTxxxxxxxxxx
(bootloader) product: ace
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PD9812000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4196mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-9854d819
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) region-id: 0
all: Done!
finished. total time: 0.171s
fastboot oem boot
< waiting for device >
...
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x8D08BECC
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x27E0E
(bootloader) TAG:hero panel = 0x830012
(bootloader) TAG:engineerid = 0x0
(bootloader) MCP dual-die
(bootloader) MCP dual-die
(bootloader) TAG:mono-die = 0x0
(bootloader) Device CID is super CID
(bootloader) CID is super CID
(bootloader) Backup CID is CWS__001
(bootloader) setting->cid::CWS__001
(bootloader) serial number: HT19VT207144
(bootloader) commandline from head: no_console_suspend=1
(bootloader) command line length =506
(bootloader) active commandline: board_spade.disable_uart2=0 board_spade.
(bootloader) usb_h2w_sw=0 board_spade.disable_sdcard=0 diag.enabled=0 boa
(bootloader) rd_spade.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e
(bootloader) mmc=true androidboot.baseband=26.06.04.06_M androidboot.cid
(bootloader) =CWS__001 androidboot.batt_poweron=good_battery androidboot.
(bootloader) carrier=ATT androidboot.mid=PD9812000 enable_zcharge=1 andro
(bootloader) idboot.keycaps=qwerty androidboot.mode=normal androidboot.se
(bootloader) rialno=HT19VT207144 androidboot.bootloader=0.85.0019 zygote_
(bootloader) oneshot=off kmemleak=off no_console_suspend=1
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=cache
(bootloader) aARM_Partion[5].name=userdata
(bootloader) aARM_Partion[6].name=devlog
(bootloader) aARM_Partion[7].name=pdata
(bootloader) partition number=8
(bootloader) Valid partition num=8
(bootloader) Delay 98712(us) for dpram command before goto AMSS...
(bootloader) jump_to_kernel: machine_id(2844), tags_addr(0x4000100), kern
(bootloader) el_addr(0x4008000)
(bootloader) -------------------hboot boot time:0 msec
FAILED (status read failed (Too many links))
finished. total time: 232.216s
I used the commands, among many others:
Fastboot oem boot
fastboot flash recovery recovery.img (or zip)
fastboot oem resetRUUflag
fastboot reboot -bootloader (this just turn the phone off)
fastboot oem get_identifier_token (answer: (bootloader) [ERR] Command error !!!)
fastboot format userdata
formatting 'userdata' partition...
FAILED (remote: unknown command)
FAILED (remote: unknown command)
finished. total time: 0.020sfastboot format cache
formatting 'cache' partition...
FAILED (remote: unknown command)
FAILED (remote: unknown command)
finished. total time: 0.017s
In many cases the response message in the command line is: remote no allowed
SD card formatted.
I have no access to the SD card from the phone connected.
Please tell me if there is any other way to recover my phone, or if it is just an expensive piece of nothing.
Thanks for everything.
What happened when you tried to flash recovery from fastboot?
bananagranola said:
What happened when you tried to flash recovery from fastboot?
Click to expand...
Click to collapse
./fastboot flash zip PD98IMG.zip
sending 'zip' (3619 KB)...
OKAY [ 0.623s]
writing 'zip'...
No more response, stuck there...
In many other commands (I just don't remember after trying several) I got the message "remote not allowed"
Frogzter said:
./fastboot flash zip PD98IMG.zip
sending 'zip' (3619 KB)...
OKAY [ 0.623s]
writing 'zip'...
No more response, stuck there...
In many other commands (I just don't remember after trying several) I got the message "remote not allowed"
Click to expand...
Click to collapse
That's because you need a recovery.img, not a PD98IMG.zip:
Code:
fastboot flash recovery recovery.img
bananagranola said:
That's because you need a recovery.img, not a PD98IMG.zip:
Code:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
I got this:
./fastboot flash recovery r.img
sending 'recovery' (4456 KB)...
OKAY [ 0.764s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.771s
Why?
Click to expand...
Click to collapse
Is your phone in fastboot mode?
bananagranola said:
Is your phone in fastboot mode?
Click to expand...
Click to collapse
Yes, it is, or at least I think so, because the command fastboot devices, found my device, besides, the command fastboot getvarr all, also works...
No more responses guys?
Where are you getting the recovery? How are you putting your phone in fastboot? Are you running the command from the folder where the recovery is? Are you sure you are S-Off?
bananagranola said:
Where are you getting the recovery? How are you putting your phone in fastboot? Are you running the command from the folder where the recovery is? Are you sure you are S-Off?
Click to expand...
Click to collapse
Power button not work
Power + Vol Down not work either.
If I connect it to the outlet orange LED turn on, and charges the battery, after ten minutes, HTC logo appears with four exclamation marks on the screen. However, Windows can not find the device until 5 or 10 minutes later, after this 10 minutes, if I connect via USB the device is responsive to fast boot devices command...
besides the screen shows:
ACE PVT HIP S-OFF RL
I have to command and the recovery file in the same folder
Er, what about the rest of my questions? How are you getting to fastboot with broken buttons? Is there an "adb reboot fastboot"?
Frogzter said:
Power button not work
Power + Vol Down not work either.
If I connect it to the outlet orange LED turn on, and charges the battery, after ten minutes, HTC logo appears with four exclamation marks on the screen. However, Windows can not find the device until 5 or 10 minutes later, after this 10 minutes, if I connect via USB the device is responsive to fast boot devices command...
besides the screen shows:
ACE PVT HIP S-OFF RL
I have to command and the recovery file in the same folder
Click to expand...
Click to collapse
What RUU did you use?? that sounds like a messed bootloader....
bananagranola said:
Er, what about the rest of my questions? How are you getting to fastboot with broken buttons? Is there an "adb reboot fastboot"?
Click to expand...
Click to collapse
I don't do anything.. I can't... if I plug the usb cable and touch any button nothing happen but if just plug it and let the phone alone, after 20 minutes do to fastboot mode...
"adb devices" don't detect the device.. just "fastboot devices" does
glevitan said:
What RUU did you use?? that sounds like a messed bootloader....
Click to expand...
Click to collapse
Well, now I feel ashamed, I can't remember with one I used... I just google the last version, because I wanted to get back to the original rom...
I formatted the computer with MAC OS, Linux, Win 7 and Win XP, looking for fix it, so I don't have much trace of with one I used.
HTC INSPIRE. att cws_001 bootloader 2.00.0030 s-on
Same thing on mine except my phone never comes on but fastboot is the only thing that recognizes my phone with limited commands. when I do a faceboot devices I get this ☺ ⌠σ fastboot no serial numbers as it use to have. Phone will not turn on at all. while nothing plugged in no light or anything even when trying to power on or get to hboot no sign of life at all. When I plug it in I get solid orange light. Pc sees it as android usb devices - my htc. but stock rom exe dont find phone. this happened to me when I was using xlmultitool 2.1. I was tyring for s 0ff after the option to [5] Flash HBOOT S-OFF Unprotected (via adb) this is when my troubles started. cant flash anything to it. when I try to flash the stock rom I get error file to big. In need of help.......I do have a gold card....
C:\Android>fastboot flash zip PD98IMG_Inspire_S-ON_FactoryRestore_GB_1.07.zip.
sending 'zip' (315734 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader:
(bootloader) version-baseband: 26.09.04.11_M2
(bootloader) version-cpld: ☺
(bootloader) version-microp: ☺
(bootloader) version-main: ♦
(bootloader) serialno: ☺ ⌠σ
(bootloader) imei: 3544550xxxxxxxx ......just sits here tells me nothing more
C:\Android>fastboot flash recover recovery.img
< waiting for device >
sending 'recover' (5532 KB)...
OKAY [ 0.624s]
writing 'recover'...
FAILED (remote: partition does not exist!)
finished. total time: 0.625s
C:\Android>fastboot flash system system.img
sending 'system' (571388 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.002s
C:\Android>fastboot oem boot
...
(bootloader) [DISPLAY_ERR] allocate heap for splash image fail!!!
(bootloader) [SD_HW_ERR] SD: No device attached
(bootloader) [SD_HW_ERR] SD: No device attached
(bootloader) [ERR] Boot/Recovery image does not exist!!!
OKAY [ 0.116s]
finished. total time: 0.117s
C:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.002s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.008s
C:\Android>fastboot oem lock
...
(bootloader) Device was already locked!
OKAY [ 1.004s]
finished. total time: 1.005s
sorry to double post but its been about a year is there a fix for this please someone help....
wacky_35016 said:
sorry to double post but its been about a year is there a fix for this please someone help....
C:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.002s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.008s
C:\Android>fastboot oem lock
...
(bootloader) Device was already locked!
OKAY [ 1.004s]
finished. total time: 1.005s
Click to expand...
Click to collapse
Sounds like it's still s-on. Where did you get your Unlock_code.bin from? Have you tried using htc dev to get one or a new one?
Hi folks,
first I apologies for my English!
I have some problems with my Moto G. Bought it very cheap, because it wasn't able to power up.
What I had done already:
It's possible to access the bootloader again. Then I tried to flash a stock firmware.
I got the following error in cmd: (for DE an EU Retail)
C:\Users\Stardust\Desktop\Androidzeug\Moto G\RETAIL-EU_4.4.2_KLB20.9-1.10-1.9_ci
d7_CFC_1FF_v8.xml>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (251136 KB)...
OKAY [ 8.112s]
writing 'system'...
OKAY [ 11.918s]
finished. total time: 20.030s
C:\Users\Stardust\Desktop\Androidzeug\Moto G\RETAIL-EU_4.4.2_KLB20.9-1.10-1.9_ci
d7_CFC_1FF_v8.xml>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (249008 KB)...
OKAY [ 8.034s]
writing 'system'...
OKAY [ 9.454s]
finished. total time: 17.503s
C:\Users\Stardust\Desktop\Androidzeug\Moto G\RETAIL-EU_4.4.2_KLB20.9-1.10-1.9_ci
d7_CFC_1FF_v8.xml>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (214009 KB)...
OKAY [ 6.911s]
writing 'system'...
(bootloader) Failed to validate sparse image
OKAY [ 18.330s]
finished. total time: 25.241s
Click to expand...
Click to collapse
And the Moto G bootloader tells me:
"PIV hash validation failed for PIV entry 0"
Mainly I tried this with many of DE, EU and GB Retails. Also US. (I live in germany)
DE and EU I got the same error. With US the bootloader shows some more errors.
At this state I can try to boot but got sucked in a bootloop sometimes or the Moto G get stacked in a blackscreen after the "bootloaderunlock-warning-logo"
Then i flashed a CWM recovery. And it's possible to enter the Recovery.
And this is the point where i don't know what to do.
I can access bootloader and recovery but can't flash a stock firmware.
Please help me!
PS: Want to past the errors when I flash: US_retail_XT1032_KXB20.9-1.8-1.4_CFC.xml
bootloader inside Moto G:
hab check failed for boot
hab check failed for recovery
hab check failed for system
Invalid PIV signed system image
cmd (last system_sparse.img):
(bootloader) Failed to validate sparse image
ikarugaski said:
Hi folks,
first I apologies for my English!
I have some problems with my Moto G. Bought it very cheap, because it wasn't able to power up.
What I had done already:
It's possible to access the bootloader again. Then I tried to flash a stock firmware.
I got the following error in cmd: (for DE an EU Retail)
And the Moto G bootloader tells me:
"PIV hash validation failed for PIV entry 0"
Mainly I tried this with many of DE, EU and GB Retails. Also US. (I live in germany)
DE and EU I got the same error. With US the bootloader shows some more errors.
At this state I can try to boot but got sucked in a bootloop sometimes or the Moto G get stacked in a blackscreen after the "bootloaderunlock-warning-logo"
Then i flashed a CWM recovery. And it's possible to enter the Recovery.
And this is the point where i don't know what to do.
I can access bootloader and recovery but can't flash a stock firmware.
Please help me!
PS: Want to past the errors when I flash: US_retail_XT1032_KXB20.9-1.8-1.4_CFC.xml
bootloader inside Moto G:
hab check failed for boot
hab check failed for recovery
hab check failed for system
Invalid PIV signed system image
cmd (last system_sparse.img):
(bootloader) Failed to validate sparse image
Click to expand...
Click to collapse
Those Errors are supposed to be normal my Friend!
They shouldn't be an issue!
Did you stop at the error? or did you complete the process?
Thaks for the answer!
Yes, I run it several times until the end. Just followed the "Moto G - Restore stock firmware" guide.
But this little G beast won't boot up.
Sometimes it does something like a bootloop and sometimes it ends in a blackscreen after the logo.
But then.... nothing.
ikarugaski said:
Thaks for the answer!
Yes, I run it several times until the end. Just followed the "Moto G - Restore stock firmware" guide.
But this little G beast won't boot up.
Sometimes it does something like a bootloop and sometimes it ends in a blackscreen after the logo.
But then.... nothing.
Click to expand...
Click to collapse
You own a DE Retail correct?
I'll help you after I write tomorrow's exam
Hi, try this guide, it worked for me.
https://www.youtube.com/watch?v=laU6NQ0LxR0
@deej_roamer
good luck for your exam!
Yeah, I think its an Retail, but maybe it could be an "O2 Germany" (the Moto bill says something of an O2 Combo). As I sayed I buyed it bricked.
Take youre time. I don't have freetime during weekend for the G.
Thanks for the link kirmr. I'll have a look.
I own a Moto G from O2 myself, however I was able to flash the regular german retail version without any errors (except for removing O2's bloatware, but I wouldn't exactly count that as an error ).
You might want to try redownloading the rom, extract it or try the german retail version. The error simply says that the disk image could not be validated. This could be because the sparse-images are defect, got written incorrectly or there might be an actual defect on the disk.
ikarugaski said:
@deej_roamer
good luck for your exam!
Yeah, I think its an Retail, but maybe it could be an "O2 Germany" (the Moto bill says something of an O2 Combo). As I sayed I buyed it bricked.
Take youre time. I don't have freetime during weekend for the G.
Thanks for the link kirmr. I'll have a look.
Click to expand...
Click to collapse
Did you try flshing this firmware?
Thanks for the wishes though!
If that doesnt work!
Please post your bootloader info. Copy what's written when bootloader boots.
That would give a better view!
EDIT: IF you are a lazy ass like me and dont wont to type. I suggest dump output of "fastboot getvar all" here
I'm back and now we can solve the problem hopefully!
I'll post a picture where you can see all firmware i had tried. (thats why i'm thinking all of them can't be defect. )
As you can see the one you suggested is in that list.
Just flashing the firmware again than i'll past the bootloader info here.
{
"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"
}
That's the answer of the getvar all command:
(bootloader) version: 0.5
(bootloader) version-bootloader: 4105
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: ***
(bootloader) cid: 0x0007
(bootloader) uid: 59D062020F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: ***
(bootloader) meid:
(bootloader) date: 01-24-2014
(bootloader) sku: XT1032
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Jan 6 6: 7: 5 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_retde/falcon_umts:
(bootloader) ro.build.fingerprint[1]: 4.3/14.10.0Q3.X-76-LGG-11/57:user/
(bootloader) ro.build.fingerprint[2]: release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.14.91.11.falcon_umts
(bootloader) ro.build.version.full[1]: .Retail.en.DE
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_JB_3.2_RB2.04.03
(bootloader) ro.build.version.qcom[1]: .00.129.057
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.0-g7161c60 ([email protected]
(bootloader) kernel.version[1]: l93lnxdroid92) (gcc version 4.7 (GCC) )
(bootloader) kernel.version[2]: #1 SMP PREEMPT Fri Oct 25 00:41:55 CDT 2
(bootloader) kernel.version[3]: 013
(bootloader) sdi.git: git=MBM-NG-V41.05-0-gac19e15
(bootloader) sbl1.git: git=MBM-NG-V41.05-0-g6863770
(bootloader) rpm.git: git=MBM-NG-V41.05-0-g4018bbe
(bootloader) tz.git: git=MBM-NG-V41.05-0-g11658be
(bootloader) aboot.git: git=MBM-NG-V41.05-0-gf4ab363
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 1/1
all: listed above
finished. total time: 0.109s
Click to expand...
Click to collapse
I have Problems since months to Flash Stock JB or Kitkat. Every Time if i try to Boot, the Phone get stucked..
Only GPE Fastboot Flash Works great for me. After this i van Flash Every Rom with twrp..
Gesendet von meinem Moto G mit Tapatalk
Just now i tried to install something via TWRP / CWM (sideload because i had no assecc
Both are
- unable to mount /system
- unable to mount /data
- unable to mount /cache
ikarugaski said:
Just now i tried to install something via TWRP / CWM (sideload because i had no assecc
Both are
- unable to mount /system
- unable to mount /data
- unable to mount /cache
Click to expand...
Click to collapse
Format all of them! i mean /system /data /cache
I am unable to install Stock Firmware on My MOTO G
hydromän said:
I have Problems since months to Flash Stock JB or Kitkat. Every Time if i try to Boot, the Phone get stucked..
Only GPE Fastboot Flash Works great for me. After this i van Flash Every Rom with twrp..
Gesendet von meinem Moto G mit Tapatalk
Click to expand...
Click to collapse
Plz read this .... Give A Solution ... I hope U can Solve This Problem
I did following steps....
1. Installed motarola usb drivers, minimal adb drives and Adroid sdk
2.Extracted stock firmware by using win.rar (fastboot_falcon_asia_ds_user_4.3_14.10.0Q3.X-84-7-LCG-4_4_release-keys-cid7-AsiaRetail_03.tar.gz) file into folder which contains adb.exe and other stuff (C:\Android-SDK\platform-tools)
3. For Downgrading: i deleted following text and saved
Lines 89-90 in the flashall.bat file:
Code:
CALL :fastboot_flash partition gpt.bin
IF %errorlevel% NEQ 0 EXIT /b 1
Lines 120-121 in the flashall.sh file:
Code:
run $fastboot -s "$serial_number" flash partition gpt.bin
if [ $? -ne 0 ]; then echo "ERROR: fastboot failed."; exit -1; fi
4. Turn off the phone for 5 seconds.
Press and hold Volume Down + Power buttons together for few seconds until a Bootloader mode gets appeared
Connected the device to PC through a USB Cable.
Now on PC, go under the extracted files, there pressed “**** Key + Right Mouse Click” button, then from this selected “open command window here“. A command prompt window will opened.
On command prompt window, typed the following command:
flashall.bat /eu
installed the firmware, it take from 5-10 minutes to complete.
Its done, phone is restarted....
5. After that unlock bootloader warning massage appear for 5sec. then black screen and stacked...
no pink color warning massages while installing
deej_roamer said:
Format all of them! i mean /system /data /cache
Click to expand...
Click to collapse
I think there is the problem...
formatting 'system' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.047s
Click to expand...
Click to collapse
I don't know if it's possible to repair a corrupted filesystem...
ikarugaski said:
I think there is the problem...
I don't know if it's possible to repair a corrupted filesystem...
Click to expand...
Click to collapse
I meant from recovery not fastboot!
Okay, that worked fine for me in CWM!
Could you find something in the "getvar" text btw?
These creepy moto still won't boot. :silly:
Just want to mention that the command format will not work.
Instead you have to use erase.
Is it possible to format boot in CMW somehow?
I don't know how, but today i managed to see the CM logo with the cycling arrow, after flashing CM11 with CMW.
But it doesn't boot up, got stuck in the logo with cycling arrow.
And it only showed up ones, never saw it again.
I don't know what happens to the Moto but everything is quite irregular.
Sometimes it boot recovery (sometimes it won't), sometimes got suck with the "warning bootloader" or after that in blackscreen, ones it shows the CM11 logo....
My moto g get stucked on a blank screen after the motorola logo animation.
I tried going into the recovery and wiping data and cache. Nothing happened.
I tried unlocking the bootloader --> No problem, it's unlocked now.
I tried reflashing the stock ROM via fastboot. Apparently all goes OKAY, all commands pass without problems, but when I reboot, still a blank screen.
I tried flashing a new ROM (5.0.2 Lollipop). Same problem, apparently it flashes everything ok but when reboots... nothing.
I tried to update only the recovery to ither Team Wins or Clockwork, they flash without problems but when I go to the recovery I get the stock one (I didnt reboot the phone went straight to recovery after flashing, and tried rebooting the phone as well).
I also tried to update only the bootloader (right now I'm at 41.13) tried to update it to 41.18, same problem... Apparently it flashes but when I reboot I still get the 41.13
Finally, I tried to hard-brick my phone using the Bootloader Bricker Tool posted here: http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798 and nothing happened.
So basically, it seems that everything I do via fastboot (or mfastboot - I tried both) it goes through without problems, but then it either reverts back to stock when the phone reboots or actually it doesnt write anything.
Any help, will be greatly appreaciated.
This is my getvar:all
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 4113
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: T09290UV3C
(bootloader) cid: 0x000C
(bootloader) channelid: 0x00
(bootloader) uid: ADC65E030F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Jun 26 18: 9:42 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_amxar/falcon_umts:
(bootloader) ro.build.fingerprint[1]: 4.4.4/KXB21.14-L1.40/37:user/relea
(bootloader) ro.build.fingerprint[2]: se-keys
(bootloader) ro.build.version.full[0]: Blur_Version.210.12.40.falcon_umt
(bootloader) ro.build.version.full[1]: s.AmericaMovil.en.AR
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.020
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-gb89c9dd ([email protected]
(bootloader) kernel.version[1]: ilclbld28) (gcc version 4.7 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Fri Jun 20 04:31:45 CDT 2014
(bootloader) sdi.git: git=MBM-NG-V41.13-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.13-0-g683cb0c
(bootloader) rpm.git: git=MBM-NG-V41.13-0-g71b1aae
(bootloader) tz.git: git=MBM-NG-V41.13-0-ga27c415
(bootloader) aboot.git: git=MBM-NG-V41.13-0-g7dc8e78
(bootloader) qe: qe 0/1
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.057s
Sounds like possible Bootloader corruption. I would try again with the unbrick tool. Best ask in the thread. Avoid trying to update Bootloader (motoboot.img) - Lollipop is not supported.
Here is the exact 4.4.2 Firmware Image:
http://www.filefactory.com/file/793...9_7_release-keys-cid12-AmericaMovil_AR.tar.gz
Thanks for the reply.
Ok, I'll head over to the unbrick thread again. The thing is my phone doesn't seem to be hard-bricked, because it boots to bootlader and it's not recognized by the PC as "qhsusb_bulk" in Device Manager.
That's why I tried to "brick" it using the tool on that thread, but it didnt get bricked at all :\
The unbrick tool should allow you to restore the Bootloader - if it is indeed corrupted.
lost101 said:
The unbrick tool should allow you to restore the Bootloader - if it is indeed corrupted.
Click to expand...
Click to collapse
I tried it several times now... The problem is that my phone is not being detected by Windows as "qhsusb_bulk" in the Device Manager. So I can't do what the instructions tell me to do.
So I used the Bootloader Bricer Tool
oversleeper said:
Bootloader Bricker Tool: If the previous tool had no effect or you think your bootloader is seriously damaged, this script will make your phone recognized as "qhsusb_bulk" so you can perform a blank flash
Click to expand...
Click to collapse
And this is what I get:
Code:
WARNING: READ CAREFULLY BEFORE YOU PROCEED!
THIS SCRIPT WILL DESTROY THE BOOTLOADER OF YOUR DEVICE.
DO NOT ATTEMPT TO USE UNLESS YOU'RE SURE ABOUT WHAT YOU'RE DOING.
ONLY YOU ARE RESPONSIBLE FOR YOUR ACTIONS.
Do you want to continue [Y/N]?Y
target max-sparse-size: 256MB
sending 'sbl1' (264 KB)...
OKAY [ 0.033s]
writing 'sbl1'...
OKAY [ 0.031s]
finished. total time: 0.067s
rebooting...
finished. total time: 0.002s
Your device is now hard bricked!
When it automatically reboots, it's like nothing happened: motorola logo, full animation, then blank screen. I can still enter the bootloader, run fastboot commands, etc etc...
epexy said:
I tried it several times now... The problem is that my phone is not being detected by Windows as "qhsusb_bulk" in the Device Manager. So I can't do what the instructions tell me to do.
So I used the Bootloader Bricer Tool
And this is what I get:
Code:
WARNING: READ CAREFULLY BEFORE YOU PROCEED!
THIS SCRIPT WILL DESTROY THE BOOTLOADER OF YOUR DEVICE.
DO NOT ATTEMPT TO USE UNLESS YOU'RE SURE ABOUT WHAT YOU'RE DOING.
ONLY YOU ARE RESPONSIBLE FOR YOUR ACTIONS.
Do you want to continue [Y/N]?Y
target max-sparse-size: 256MB
sending 'sbl1' (264 KB)...
OKAY [ 0.033s]
writing 'sbl1'...
OKAY [ 0.031s]
finished. total time: 0.067s
rebooting...
finished. total time: 0.002s
Your device is now hard bricked!
When it automatically reboots, it's like nothing happened: motorola logo, full animation, then blank screen. I can still enter the bootloader, run fastboot commands, etc etc...
Click to expand...
Click to collapse
I have two devices with the same problem as yours, one = motorola logo -> full animation -> black screen. And another boots up normally, but have a forgotten password, but if I try to enter recovery mode then "Boot Up Failed" message appear, and after I flash the device (and use erase userdata command), the device still have the password and all data apparently (the device boot up fast too).
The only thing that seems to work with fastboot is unlocking bootloader, and relock fails (even showing sucessful)
No one have this problems and have solutions ?????
I have the exact same problem. Was on a slim6 rom before. Tried to return to STOCK_ASIA_RETAIL. All fastboot commands successfully executed but no apparent change. I have the exact same wallpaper, the same layers RRO navbars, everything. I would not need to go to STOCK but since the slim installation is unstable and everything force closes, the phone is unusable.
Additional note: Somehow even TWRP is stuck in the splash screen, so cant flash any other ROM. Even tried to access TWRP using adb, but the TWRP service fails to start.
I fastboot flashed phillz recovery, stock recovery & newer TWRP versions, but nothing happens. Phone still stuck in TWRP screen.
To my surprise I was able to pull my personal files from the internal SD using ADB (which still works btw).
But I'm left with a phone in a zombie unusable condition, it just doesn't react to anything.
Any help from the XDA community would be greatly appreciated. I am still keeping my fingers crossed, so that one day a guide comes up to brick my device (STOCK 5.1 bootloader) and unbrick it using some sort of unbrick tool.
Hi there!
After stupidly flashing CM on a hiaeuhl device, every time I boot the device it reboots to bootloader with the "init fs_mgr_mount_all failed" error.
Obviously I try to restore my own Stock TWRP backup, but still blocked.
Then I try some RUU/ROM flashing, but since I'm S-ON and 1.27.401.5, I find nothing working for my device.
Have you got any advice?
Thank you so much!
Code:
Product: htc_hiaeuhl
Status: S-ON / Unlocked
CID: HTC__034
MID: 2PQ910000
OS: 1.27.401.5
Radio: [email protected]
Fingerprint: htc/hiaeuhl_00401/htc_hiaeuhl:6.0/MRA58K/656287.5:user/release-keys
OK, I'm on it since two days, post it and solve it in 30min...
For reference, it's possible to downgrade the ROM.
Have to use htc_fastboot and push 1.10.401.7 images.
See http://forum.xda-developers.com/showpost.php?p=64586583&postcount=146 and http://forum.xda-developers.com/showpost.php?p=64509541&postcount=122
InTheNorth said:
Hi there! funny mine to
My is unlocked with S-on
After stupidly flashing CM on a hiaeuhl device, every time I boot the device it reboots to bootloader with the "init fs_mgr_mount_all failed" error.
Obviously I try to restore my own Stock TWRP backup, but still blocked.
Then I try some RUU/ROM flashing, but since I'm S-ON and 1.27.401.5, I find nothing working for my device.
Have you got any advice?
Thank you so much!
I have also tried Cyanogenmod 13. I changed the "updater script" to target my device model too and added the letter "h" in text-editor hiaeul to hiaeuhl with boot loops
Code:
Product: htc_hiaeuhl
Status: S-ON / Unlocked
CID: HTC__034
MID: 2PQ910000
OS: 1.27.401.5
Radio: [email protected]
Fingerprint: htc/hiaeuhl_00401/htc_hiaeuhl:6.0/MRA58K/656287.5:user/release-keys
Click to expand...
Click to collapse
I have the exakt problem too... Your hardware&Software description is identical.
I flash through htc_fastboot.exe and I flash system partition with wrong method
Code:
htc_fastboot flash system apppreload.img
I used images from combined
2PQ9IMG_HIA[email protected]51002.3_29.05_F_release_454007_combined_signed
my
Code:
fastboot get var all
is
h:\>htc_fastboot.exe getvar all
Code:
(bootloader) version:0.5
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x10000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x29b000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xc6000000
(bootloader) serialno:HT5A????secret
getvar all from download mode is
Code:
(bootloader) kernel: lk
(bootloader) product: htc_hiaeu[B]h[/B]l
(bootloader) version: 1.0
(bootloader) imei: *************secret
(bootloader) version-main: 1.27.401.5
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PQ910000
(bootloader) cid: HTC__034
a
Is changing manifest working? I'm not sure...
So you have restore your phone with those images?
InTheNorth said:
Is changing manifest working? I'm not sure...
So you have restore your phone with those images?
Click to expand...
Click to collapse
I still haven't succeded to restore phone to factory state... I didn't twrp backup it after root.
Status is unlocked, S-ON
I have tried your links to
I did
H:\>fastboot oem rebootRRU
Code:
:\>htc_fastboot.exe flash zip HTC_A9_1.10.401.7_partial.zip
sending 'zip'... (88062 KB) OKAY
sending time = 8.050 secs
writing 'zip'... (bootloader) HOSD CL#656287
(bootloader) ERR [SD_UPDATE_ERR] Main version NOT ALLOWED
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 19
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP signature checking failed...
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 19
(bootloader) [email protected]
FAIL19 RU_MAIN_VER_FAIL os-version in android-info missing or i
FAILED (remote: 19 RU_MAIN_VER_FAIL os-version in android-info missing or i)
Execution time is 12(s)
I think it isn't same partition size, I also tried regular fastboot and htc_fastboot in oem-mode.
Code:
>fastboot flash system system.img
target reported max download size of 800000000 bytes
system size on windows is 2,92 GB
according to this guy nenebear http://forum.xda-developers.com/showpost.php?p=64509541&postcount=122 I have another international model.
I am not sure wich version I have... according to this post
International version don't flash is images . Because the unlocked version of the system partitions of different size and international version .
unlocked version system partitions -- mmcblk0p62: d9000000 00000200 "system"
international version system partitions -- mmcblk0p62: c6000000 00000200 "system"
I have tried RUU.exe file with fail to not same main version
I flash zipped with fail
fastboot flash zip 2PQ9IMG_HIAE_UL_ATT_1.27.502.5_firmware.zip
Meanwhile i see that fastboot flash system system.img is working now haha it just took time to read/send system.img that is almost 3GB
thank you for your link, I needed that system.img file
fastboot flash system H:\Htc-blocket\rom\upNorth\partial\system.img
target reported max download size of 800000000 bytes
erasing 'system'...
OKAY [ 2.748s]
sending sparse 'system' (769748 KB)...
OKAY [ 71.392s]
writing 'system'...
(bootloader) HOSD CL#656287
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 34.540s]
sending sparse 'system' (778860 KB)...
OKAY [ 72.596s]
writing 'system'...
(bootloader) HOSD CL#656287
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 34.080s]
sending sparse 'system' (770834 KB)...
OKAY [ 72.728s]
writing 'system'...
(bootloader) HOSD CL#656287
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 33.950s]
sending sparse 'system' (752915 KB)...
OKAY [ 70.736s]
writing 'system'...
(bootloader) HOSD CL#656287
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 33.562s]
finished. total time: 426.364s
Many seconds here, 7 minutes
Click to expand...
Click to collapse
H:\>fastboot flash boot H:\Htc-blocket\rom\upNorth\partial\boot.img
target reported max download size of 167000000 bytes
sending 'boot' (45799 KB)...
OKAY [ 4.548s]
writing 'boot'...
(bootloader) HOSD CL#656287
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 3.868s]
finished. total time: 8.416s
H:\>fastboot flash recovery H:\Htc-blocket\rom\upNorth\partial\recovery.img
target reported max download size of 800000000 bytes
sending 'recovery' (47229 KB)...
OKAY [ 4.416s]
writing 'recovery'...
(bootloader) HOSD CL#656287
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 4.038s]
finished. total time: 8.454s
Solved! Thank you!
So CM is not available for the hiaeuhl ? I bought this device, didn't kno there were variants...
exploreresp said:
So CM is not available for the hiaeuhl ? I bought this device, didn't kno there were variants...
Click to expand...
Click to collapse
You have to remove the /system partition protection (S-on=Secure ON=you licensing the device, S-off=Security off=you own the device=God over your device) because the bootloader is checking the partition integrity and finds out if you did something with it (writing/deleting/etc).
:cyclops: Unfortunately I tried to logcat, adb-watch my device under the hood during the unlocking process by an app named "sunshine.apk" when is was unlocking (S-off'ing) with secret methods/(unshared knowledge), Unfortunately they (the app) kill logcat-process continuously all the way, in and out, out and in so I could'nt figure out that secret method the use....
You can still root your device since the Master of the masterdeveloper named ChainFire is putin th su binaries on a separate partition /su/bi and symlink some how (just guessing, correct me if I'm wrong) with a modified unlocked boot.img.
Forget xposed-framework, forget CyanogenMod unless you release/unchain your phones locked /system partition and other partitions too (not necessary) . It will cost you 25$ dollar, sorry, it is not my faults, I am just like you a hardware-owner of a Taiwanese cellphone.
After you S-off'ed your phone with money (25$) you can install CM13 or CM14 (year 2017). Hopefully some hardware/kernel hacker figure out an easy way to s-unlock/s-off without paying crying: there are more poor people in this world than there are rich people)
Me too bought this phone with the mind of put in CyanogenMod... I don't trust other manufactures android-OS. Also I can overclock/underclock etc and install the mothers of all hack... the xposed-framework... ayhem!
---------- Post added at 04:47 PM ---------- Previous post was at 04:38 PM ----------
exploreresp said:
So CM is not available for the hiaeuhl ? I bought this device, didn't kno there were variants...
Click to expand...
Click to collapse
You simply convert your phone with money and this method in this linked thread
Read further, there is hope with money! :victory: and a payPal / visa account
Cheers :good:
InTheNorth said:
Hi there!
After stupidly flashing CM on a hiaeuhl device, every time I boot the device it reboots to bootloader with the "init fs_mgr_mount_all failed" error.
Obviously I try to restore my own Stock TWRP backup, but still blocked.
Then I try some RUU/ROM flashing, but since I'm S-ON and 1.27.401.5, I find nothing working for my device.
Have you got any advice?
Thank you so much!
Code:
Product: htc_hiaeuhl
Status: S-ON / Unlocked
CID: HTC__034
MID: 2PQ910000
OS: 1.27.401.5
Radio: [email protected]
Fingerprint: htc/hiaeuhl_00401/htc_hiaeuhl:6.0/MRA58K/656287.5:user/release-keys
Click to expand...
Click to collapse
you should be able to install CM13 on your device...
check: http://forum.xda-developers.com/one-a9/general/cm13-t3290846/post64882819#post64882819
Edit: It seems you need to convert to us version first
Hey all,
Bringing that post up because I'm having the same issue here and none of the solutions proposed worked...
Problem is my phone began freezing 2mn after booting (I was still able to use it, apps, phone etc... but after around 2mn can't do anything anymore) after I took it with me in very low temperature. I tried to restore it and then this error appeared "init fs_mgr_mount_all failed"...
I had TWRP, unlocked, S-OFF and tried a few things :
This one first, didn't work : http://android-revolution-hd.blogspot.cl/2013/10/fix-data-htc-one.html
Then tried the solution proposed here, didn't work either : http://forum.xda-developers.com/showpost.php?p=64509541&postcount=122
And as it turned out I came back to the stock recovery ... (wasn't sure of what I was doing) so now I only have adb sideload...
Tried installing CM using sideload, didn't work (signature verification failed... which is pretty normal).
Anyway I'm posting because it is really my last resort... don't have anything left under my sleeve. I'm currently downloading a 1.27.112.5 stock rom (http://forum.xda-developers.com/one-a9/general/wip-ruu-htc-one-a9-t3240344) to try to downgrade but not sure the problem will be solved...
If someone can help, it would be great!!
Code:
Product: htc_hiaeuhl
Status: S-OFF / Unlocked
CID: HTC__034
MID: 2PQ910000
OS: 1.56.401.70
Radio: [email protected]
Aliass01 said:
Hey all,
Bringing that post up because I'm having the same issue here and none of the solutions proposed worked...
Problem is my phone began freezing 2mn after booting (I was still able to use it, apps, phone etc... but after around 2mn can't do anything anymore) after I took it with me in very low temperature. I tried to restore it and then this error appeared "init fs_mgr_mount_all failed"...
I had TWRP, unlocked, S-OFF and tried a few things :
This one first, didn't work : http://android-revolution-hd.blogspot.cl/2013/10/fix-data-htc-one.html
Then tried the solution proposed here, didn't work either : http://forum.xda-developers.com/showpost.php?p=64509541&postcount=122
And as it turned out I came back to the stock recovery ... (wasn't sure of what I was doing) so now I only have adb sideload...
Tried installing CM using sideload, didn't work (signature verification failed... which is pretty normal).
Anyway I'm posting because it is really my last resort... don't have anything left under my sleeve. I'm currently downloading a 1.27.112.5 stock rom (http://forum.xda-developers.com/one-a9/general/wip-ruu-htc-one-a9-t3240344) to try to downgrade but not sure the problem will be solved...
If someone can help, it would be great!!
Code:
Product: htc_hiaeuhl
Status: S-OFF / Unlocked
CID: HTC__034
MID: 2PQ910000
OS: 1.56.401.70
Radio: [email protected]
Click to expand...
Click to collapse
Just use a RUU, that's how you get everything back to stock.
Sent from my HTC One A9 using XDA-Developers mobile app
Hi, I am new here and I wanted some assistnce to get my old Moto G working. Its stuck in boot loop. When I power it on, it is looping on the Moto screen. I tried flashing it seeing some old threads here and was getting remote failure. I also tried custom recovery but it was failing. I can see Motorola AD Interface on the PC and I have installed all drivers as well. Whatever i try just fails with the same message. "FAILED (remote failure)"
I also a saw thread which talked about the PC to show QLoader9008 in device manager but that also doesnt show in my device manager. I can just see Motorola ADB Interface.
Anything we can do to fix it. I'd really want it to get back to life if its possible.
Thank You for the help in advance.
Images tried
Motorola_Moto_G_XT1033_Falcon_ASIA_DS_5.1_LPBS23.13-56-2_CID7_CFC1
XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.xml by jame
Motorola_Moto_G_XT1033_FALCON_TIMBR_DS_5.1_LPBS23.13-56-2_CID12_5.1
Tools used
RSDLite 6.2.4
mfastboot-v2
Fastboot
Log Sample
F:\DownloadsFolder\Motorola_Moto_G_XT1033_Falcon_ASIA_DS_5.1_LPBS23.13-56-2_CID7_CFC1\Motorola_Moto_G_XT1033_Falcon_ASIA_DS_5.1_LPBS23.13-56-2_CID7_CFC\Firmware>fastboot flash partition gpt.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 9.950s]
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: 15.225s
If
maau1985 said:
Hi, I am new here and I wanted some assistnce to get my old Moto G working. Its stuck in boot loop. When I power it on, it is looping on the Moto screen. I tried flashing it seeing some old threads here and was getting remote failure. I also tried custom recovery but it was failing. I can see Motorola AD Interface on the PC and I have installed all drivers as well. Whatever i try just fails with the same message. "FAILED (remote failure)"
I also a saw thread which talked about the PC to show QLoader9008 in device manager but that also doesnt show in my device manager. I can just see Motorola ADB Interface.
Anything we can do to fix it. I'd really want it to get back to life if its possible.
Thank You for the help in advance.
Images tried
Motorola_Moto_G_XT1033_Falcon_ASIA_DS_5.1_LPBS23.13-56-2_CID7_CFC1
XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.xml by jame
Motorola_Moto_G_XT1033_FALCON_TIMBR_DS_5.1_LPBS23.13-56-2_CID12_5.1
Tools used
RSDLite 6.2.4
mfastboot-v2
Fastboot
Log Sample
F:\DownloadsFolder\Motorola_Moto_G_XT1033_Falcon_ASIA_DS_5.1_LPBS23.13-56-2_CID7_CFC1\Motorola_Moto_G_XT1033_Falcon_ASIA_DS_5.1_LPBS23.13-56-2_CID7_CFC\Firmware>fastboot flash partition gpt.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 9.950s]
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: 15.225s
Click to expand...
Click to collapse
If you have not already, first you need to unlock your bootlloader before flashing anything.