Related
C:\Users\Admin\.android>fastboot flash zip 0P9CIMG.zip
sending 'zip'... (38480 KB) OKAY
sending time = 2.555 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAIL99 unknown fail
FAILED (remote: 99 unknown fail)
Execution time is 7(s)
MY GETVAR
C:\Users\Admin\.android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.31.50.0215
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA484MZ00350
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid: A1000037D94F05
(bootloader) product: a5_dwg
(bootloader) platform: hTCBmsm8226
(bootloader) modelid: 0P9C51000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 09813c97
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Execution time is 13(ms)
And i Get this error
C:\Users\Admin\.android>fastboot oem unlock
... (bootloader) [ERR] Command error !!!
OKAY
Execution time is 3(ms)
Help Me Out!!!
My Device Is HTC DESIRE 816 Dual Sim (INDIA)
sujay123 said:
C:\Users\Admin\.android>fastboot flash zip 0P9CIMG.zip
sending 'zip'... (38480 KB) OKAY
sending time = 2.555 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAIL99 unknown fail
FAILED (remote: 99 unknown fail)
Execution time is 7(s)
MY GETVAR
C:\Users\Admin\.android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.31.50.0215
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA484MZ00350
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid: A1000037D94F05
(bootloader) product: a5_dwg
(bootloader) platform: hTCBmsm8226
(bootloader) modelid: 0P9C51000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 09813c97
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Execution time is 13(ms)
And i Get this error
C:\Users\Admin\.android>fastboot oem unlock
... (bootloader) [ERR] Command error !!!
OKAY
Execution time is 3(ms)
Help Me Out!!!
My Device Is HTC DESIRE 816 Dual Sim (INDIA)
Click to expand...
Click to collapse
Do you have HTC drivers installed?
Sent from my HTC Desire EYE using Tapatalk
xXminiWHOOPERxX said:
Do you have HTC drivers installed?
Sent from my HTC Desire EYE using Tapatalk
Click to expand...
Click to collapse
Yeah I guess, I'm new to this stuff. So could you be a bit more Specific.
sujay123 said:
Yeah I guess, I'm new to this stuff. So could you be a bit more Specific.
Click to expand...
Click to collapse
Do you have HTC Sync installed is what I'm asking
Sent from my HTC Desire EYE using Tapatalk
xXminiWHOOPERxX said:
Do you have HTC Sync installed is what I'm asking
Sent from my HTC Desire EYE using Tapatalk
Click to expand...
Click to collapse
Yeah, But its unable to recognize the device.
sujay123 said:
Yeah, But its unable to recognize the device.
Click to expand...
Click to collapse
1st. Remove imei and imei 2 from first post for safety reasons.
2. Uninstall HTC Sync but keep everything else it installed..
3. Make sure you have Java installed ( not sure if you need it , but I always have it installed )
4. Have you tried flashing the zip again ? Boot loader locked ?
fastboot flash zip (name of zip)
If fails it should say flush again.. then redo the command.
Sent from my HTC Desire EYE using Tapatalk
xXminiWHOOPERxX said:
1st. Remove imei and imei 2 from first post for safety reasons.
2. Uninstall HTC Sync but keep everything else it installed..
3. Make sure you have Java installed ( not sure if you need it , but I always have it installed )
4. Have you tried flashing the zip again ? Boot loader locked ?
fastboot flash zip (name of zip)
If fails it should say flush again.. then redo the command.
Sent from my HTC Desire EYE using Tapatalk
Click to expand...
Click to collapse
1) Done
2) Done
3) Have It
4)
C:\Users\Admin\.android>fastboot flash zip 0P9CIMG.zip
sending 'zip'... (38480 KB) OKAY
sending time = 2.558 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
FAILnot allowed
FAILED (remote: not allowed)
Execution time is 6(s)
C:\Users\Admin\.android>fastboot flash zip 0P9CIMG.zip
sending 'zip'... (38480 KB) OKAY
sending time = 2.554 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
FAILnot allowed
FAILED (remote: not allowed)
Execution time is 6(s)
C:\Users\Admin\.android>fastboot oem unlock
... (bootloader) [ERR] Command error !!!
OKAY
Execution time is 0(ms)
sujay123 said:
1) Done
2) Done
3) Have It
4)
C:\Users\Admin\.android>fastboot flash zip 0P9CIMG.zip
sending 'zip'... (38480 KB) OKAY
sending time = 2.558 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
FAILnot allowed
FAILED (remote: not allowed)
Execution time is 6(s)
C:\Users\Admin\.android>fastboot flash zip 0P9CIMG.zip
sending 'zip'... (38480 KB) OKAY
sending time = 2.554 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
FAILnot allowed
FAILED (remote: not allowed)
Execution time is 6(s)
C:\Users\Admin\.android>fastboot oem unlock
... (bootloader) [ERR] Command error !!!
OKAY
Execution time is 0(ms)
Click to expand...
Click to collapse
Okay lock boot loader first if it's already unlocked
fastboot oem lock
Then try flashing the zip again.
Sent from my HTC Desire EYE using Tapatalk
xXminiWHOOPERxX said:
Okay lock boot loader first if it's already unlocked
fastboot oem lock
Then try flashing the zip again.
Sent from my HTC Desire EYE using Tapatalk
Click to expand...
Click to collapse
C:\Users\Admin\.android>fastboot oem lock
... (bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) [PGFS] partition_update_pgfs: pg2fs_sec_recovery
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) WARM RESET: 9
(bootloader) [INFO] Rebooting device
FAILED (status read failed (No such file or directory))
Execution time is 1(s)
And WNIDOWS ERROR : FASTBOOT.EXE Has Stopped Working
Now Waiting for my battery to drain
sujay123 said:
C:\Users\Admin\.android>fastboot oem lock
... (bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) [PGFS] partition_update_pgfs: pg2fs_sec_recovery
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) WARM RESET: 9
(bootloader) [INFO] Rebooting device
FAILED (status read failed (No such file or directory))
Execution time is 1(s)
And WNIDOWS ERROR : FASTBOOT.EXE Has Stopped Working
Now Waiting for my battery to drain
Click to expand...
Click to collapse
Okay I need to know what you did that left your phone in the state that it is.
Sent from my HTC Desire EYE using Tapatalk
xXminiWHOOPERxX said:
Okay I need to know what you did that left your phone in the state that it is.
Sent from my HTC Desire EYE using Tapatalk
Click to expand...
Click to collapse
First I Rooted it, Via CWM
Then I tried to Partition My SD card ,but failed , so i got it back to its original state.
Then Tried to install some random theme.zip through CWM
That's when the problem started (Stuck At black screen on Booting)
Then I'm not sure about this : I probably formatted the SYSTEM via CWM (Probably the reason for absent OS)
And I'm Not sure how I lost CWM : probably while flashing stock recovery.img (via Fastboot)
and then FASTBOOT OEM LOCK, tried to unlock it but i keep getting the same error.
and then i downloaded and installed this HTC SPECIAL FASTBOOT DRIVER DOWNLOAD & ADB SETUP DRIVER
and again tried to flash RECOVER.IMG, but failed.
So I Repeated the unlock procedure from the HTC website.
I get option , I select unlock , The Device REBOOTS, and FASTBOOT OEM UNLOCK : FAILED
But , even then I try to Flash 0P9CIMG.zip which fails again and again.
I have no Idea Whats going on
I can only Access the bootloader menu.
Cannot Access recovery , a red triangle and ! appears.
PLEASE TELL ME YOU HAVE A SOLUTION.
I'M READY TO DOWNLOAD A NEW RECOVERY.IMG AND RUU FOR A5_DWG
sujay123 said:
First I Rooted it, Via CWM
Then I tried to Partition My SD card ,but failed , so i got it back to its original state.
Then Tried to install some random theme.zip through CWM
That's when the problem started (Stuck At black screen on Booting)
Then I'm not sure about this : I probably formatted the SYSTEM via CWM (Probably the reason for absent OS)
And I'm Not sure how I lost CWM : probably while flashing stock recovery.img (via Fastboot)
and then FASTBOOT OEM LOCK, tried to unlock it but i keep getting the same error.
and then i downloaded and installed this HTC SPECIAL FASTBOOT DRIVER DOWNLOAD & ADB SETUP DRIVER
and again tried to flash RECOVER.IMG, but failed.
So I Repeated the unlock procedure from the HTC website.
I get option , I select unlock , The Device REBOOTS, and FASTBOOT OEM UNLOCK : FAILED
But , even then I try to Flash 0P9CIMG.zip which fails again and again.
I have no Idea Whats going on
I can only Access the bootloader menu.
Cannot Access recovery , a red triangle and ! appears.
PLEASE TELL ME YOU HAVE A SOLUTION.
I'M READY TO DOWNLOAD A NEW RECOVERY.IMG AND RUU FOR A5_DWG
Click to expand...
Click to collapse
Have you tried placing zip on external SDCard and name it 0P9CIMG.zip and let the boot loader do the RUU Update it's self.
Sent from my HTC Desire EYE using Tapatalk
xXminiWHOOPERxX said:
Have you tried placing zip on external SDCard and name it 0P9CIMG.zip and let the boot loader do the RUU Update it's self.
Sent from my HTC Desire EYE using Tapatalk
Click to expand...
Click to collapse
Okay I Think This is it (Hope It Works)
Flashing ZIP file....
:fingers-crossed:
Do you Want to Start Update
<VOL UP> Yes
<VOL DOWN> No
Going With Yes
sujay123 said:
Okay I Think This is it (Hope It Works)
Flashing ZIP file....
:fingers-crossed:
Do you Want to Start Update
<VOL UP> Yes
<VOL DOWN> No
Going With Yes
Click to expand...
Click to collapse
Well?
Sent from my HTC Desire EYE using Tapatalk
xXminiWHOOPERxX said:
Well?
Sent from my HTC Desire EYE using Tapatalk
Click to expand...
Click to collapse
I got the OS- (2.34.720.1)
Update is in progress
flashing zip file
Is this it?
xXminiWHOOPERxX said:
Well?
Sent from my HTC Desire EYE using Tapatalk
Click to expand...
Click to collapse
OMG :crying: Thank you So Much , I LOVE YOU.
Just A few More Queries
1 ) Can/How Do I Unlock OEM
2) How do I get to know the status of My Device rooted/unrooted
3) Which one is preferred CWM/TWRP , and do I put it back using the normal procedure.?
4) Can I modify/Change the Stock recovery.img
5) Should I install the SuperSU.zip/apk
sujay123 said:
OMG :crying: Thank you So Much , I LOVE YOU.
Just A few More Queries
1 ) Can/How Do I Unlock OEM
2) How do I get to know the status of My Device rooted/unrooted
3) Which one is preferred CWM/TWRP , and do I put it back using the normal procedure.?
4) Can I modify/Change the Stock recovery.img
5) Should I install the SuperSU.zip/apk
Click to expand...
Click to collapse
1) To sim unlock I'm unsure of because I don't own a dual sim device ..
Unlock boot loader on htcdev.com
2&3) install official twrp from their website and download SuperSU 2.56
Sent from my HTC Desire EYE using Tapatalk
Red triangle with stock recovery flash
Cannot Access recovery , a red triangle and ! appears.
Just to chime in on the red triangle issue . I had that same issue when reflashing my stock recovery back to my rooted 816 single SIM and the issue was that the stock recovery was there but had that screen due to the fact that I had altered the phone and the triangle is an indicator of that for HTC I guess. I was able to get into the stock recovery by pressing and holding the power button then pressing volume up and waiting . When the stock recovery screen shows up you release the volume button I believe but it might be releasing both. It's been a while. Either way I got into the stock recovery but I ended up just reflashing TWRP custom recovery back and not doing my stock update as the zip file kept failing. Glad you got expert help with your issues and got it resolved.
sujay123 said:
C:\Users\Admin\.android>fastboot flash zip 0P9CIMG.zip
sending 'zip'... (38480 KB) O
And i Get this error
C:\Users\Admin\.android>fastboot oem unlock
... (bootloader) [ERR] Command error !!!
OKAY
Execution time is 3(ms)
Help Me Out!!!
My Device Is HTC DESIRE 816 Dual Sim (INDIA)
Click to expand...
Click to collapse
Could u plz post the link to that zip file, becos im also using a5dwg
thoctor said:
Cannot Access recovery , a red triangle and ! appears.
Just to chime in on the red triangle issue . I had that same issue when reflashing my stock recovery back to my rooted 816 single SIM and the issue was that the stock recovery was there but had that screen due to the fact that I had altered the phone and the triangle is an indicator of that for HTC I guess. I was able to get into the stock recovery by pressing and holding the power button then pressing volume up and waiting . When the stock recovery screen shows up you release the volume button I believe but it might be releasing both. It's been a while. Either way I got into the stock recovery but I ended up just reflashing TWRP custom recovery back and not doing my stock update as the zip file kept failing. Glad you got expert help with your issues and got it resolved.
Click to expand...
Click to collapse
I had tried every combination, nothing worked. It was either restart or was stuck at the boot screen (HTC white Logo) or a Black screen.
Yeah me too!!
Hello,
The first day I got my moto x style (XT1572) I started to root, everything was more or less well until I tried to install the SU when I finished installing the binary from the TWRP custom recovery-3.0.2-0- clark you say yes to install the root since the phone would not start and remains in boot loop.
After much look I followed some tutorial XDA (http://forum.xda-developers.com/moto-x-style/help/brick-downgrade-6-0-to-5-1-heeeeelp-t3253716) to return to flash the phone with the rom that theory came from factory cbox1s_XT1572_CLARK_RETEU_6.0_MPHS24.49-18-3_cid7_subsidy-DEFAULT_CFC.xml after following all the steps mobile and well lit and seems it was all sorted.
Well, I went back to the load to make root and remove the message that the bootloader was unlocked this time all fu well, except now every time I reboot I enter into fastboot mode and have to select START to boot normal to me.
Any ideas or suggestions to fix it?
regards,
PD: Sorry for my google translate english i'am spanish a my english level is very bad :crying:
SOLVED, the problem was the BP Tools in the fastboot, i had "Fastboot Reason: UTAG "bootmode" configured as fastboot" i changed to "Normal Powerup" and all perfect
same problem with Motorola z xt1650-03 , unlocked bootloader , every time I start up remain stuck in fastboot mode , after ,push the power button for start , and start normal.
I try to reload stock firmware 7.0 with fastboot mode but when try to flash partition.gpt he say bad key .
now I used like this ,
sagutxo97 said:
SOLVED, the problem was the BP Tools in the fastboot, i had "Fastboot Reason: UTAG "bootmode" configured as fastboot" i changed to "Normal Powerup" and all perfect
Click to expand...
Click to collapse
What? how do you do it? can you tell me how to do it more specific? I'm new so I don't understand what you mean and how you do it :/
thank you.
Moto devices have a flashing mode called "fb_mode" that when enabled causes the bootloader to start on each boot, it is used for flashing stock firmware images since in some cases the device needs to reboot after flashing a certain partition or image and it needs a way to return to the fastboot mode. Remember when flashing a stock image you may have entered "fastboot oem fb_mode_set"? If not then a toolkit or other flashing tool may have done it but not cleared it correctly. To clear it manually you need to literally clear it with a fastboot command... With the phone in the bootloader, enter this command from your computer"
fasboot oem fb_mode_clear
And reboot, it should no longer go to the bootloader unless you are holding VOL DN and the operating system should start normally.
acejavelin said:
Moto devices have a flashing mode called "fb_mode" that when enabled causes the bootloader to start on each boot, it is used for flashing stock firmware images since in some cases the device needs to reboot after flashing a certain partition or image and it needs a way to return to the fastboot mode. Remember when flashing a stock image you may have entered "fastboot oem fb_mode_set"? If not then a toolkit or other flashing tool may have done it but not cleared it correctly. To clear it manually you need to literally clear it with a fastboot command... With the phone in the bootloader, enter this command from your computer"
fasboot oem fb_mode_clear
And reboot, it should no longer go to the bootloader unless you are holding VOL DN and the operating system should start normally.
Click to expand...
Click to collapse
You saved my [email protected]#! Thanks.
I'm trying help a friend with her Moto X Style. The buttoms RETURN, HOME and APP is not working. I'm trying upload a ROM, but I got errors everytime and the fastboot was entering every boot.
acejavelin said:
Moto devices have a flashing mode called "fb_mode" that when enabled causes the bootloader to start on each boot, it is used for flashing stock firmware images since in some cases the device needs to reboot after flashing a certain partition or image and it needs a way to return to the fastboot mode. Remember when flashing a stock image you may have entered "fastboot oem fb_mode_set"? If not then a toolkit or other flashing tool may have done it but not cleared it correctly. To clear it manually you need to literally clear it with a fastboot command... With the phone in the bootloader, enter this command from your computer"
fasboot oem fb_mode_clear
And reboot, it should no longer go to the bootloader unless you are holding VOL DN and the operating system should start normally.
Click to expand...
Click to collapse
I did this several times and it set continues it say fasboot reason reboot mode set to fastboot and I tried fastboot oem fb_mode_clear but it just says boot loader slot count not found and etc
Sam to me. Any help?
ninormalen said:
Sam to me. Any help?
Click to expand...
Click to collapse
Yea I do need help, I had flashed a custom rom with twrp recovery on my phone but every time I reboot I either loads into recovery or boot loader if I fb mode clear or not. Even if theirs a system to boot, I have to manually boot into through boot loader and start. If I go to bootloader logs it just says reboot mode set to fastboot.
typo - fastboot, not fasboot
fastboot oem fb_mode_clear
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
When I type this commend, I get the following error:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
Can someone tell me whats is the problem?
lucas.passos said:
When I type this commend, I get the following error:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
Can someone tell me whats is the problem?
Click to expand...
Click to collapse
There is no problem... The Moto X does not have A/B software slots, the messages above are merely informational and completely normal.
With mfastboot there is no messages like this. Only "OKAY" one
However it didn't help with my Moto G (falcon).
What helped was checking the kernel. My "smartness" told me to flash Nouagt when I had Pie rom...
Dunken415 said:
Yea I do need help, I had flashed a custom rom with twrp recovery on my phone but every time I reboot I either loads into recovery or boot loader if I fb mode clear or not. Even if theirs a system to boot, I have to manually boot into through boot loader and start. If I go to bootloader logs it just says reboot mode set to fastboot.[/QUOTE
same problem here brother did you find any solution to it?? please help me brother.
Click to expand...
Click to collapse
sagutxo97 said:
SOLVED, the problem was the BP Tools in the fastboot, i had "Fastboot Reason: UTAG "bootmode" configured as fastboot" i changed to "Normal Powerup" and all perfect
Click to expand...
Click to collapse
How'd you do that? i have the same problem how do switch back to normal powerup?
XT-1570 "bootmode-recovery"
Dunken415 said:
I did this several times and it set continues it say fasboot reason reboot mode set to fastboot and I tried fastboot oem fb_mode_clear but it just says boot loader slot count not found and etc
Click to expand...
Click to collapse
I am having the same issue. Would appriciate any help.
E:\fastboot oem fb_mode_clear
...
OKAY [ 0.000s]
finished. total time: 0.016s
PS E:\Backup\Android - XT1570> fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8992-A0.43
(bootloader) product: clark
(bootloader) board: clark
(bootloader) secure: no
(bootloader) hwrev: 0x82A0
(bootloader) radio: 0x3
(bootloader) emmc: 64GB Toshiba REV=07 PRV=00 TYPE=57 PNM=064G38
(bootloader) ram[0]: 3072MB SK Hynix S8 SDRAM DIE=6Gb M5=x6 M6=x3 M7=x0
(bootloader) ram[1]: M8=x3B
(bootloader) cpu: MSM8992
(bootloader) serialno: LX7C2xxxxx
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0xDEAD
(bootloader) uid: EFFA2C001E000000000000000000
(bootloader) unlocked: Not supported
(bootloader) securestate: Engineering
(bootloader) iswarrantyvoid: Not supported
(bootloader) mot_sst: 1
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 35550006xxxxxxx
(bootloader) meid:
(bootloader) date: 04-30-2015
(bootloader) sku: XT1570
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Jul 18 7:57:55 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/clark_retasia_ds/clark_ds
(bootloader) ro.build.fingerprint[1]: :6.0.1/MPHS24.107-58-5/4:user/rele
(bootloader) ro.build.fingerprint[2]: ase-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.221.5.clark_retas
(bootloader) ro.build.version.full[1]: ia_ds.retasia.en.03
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.10.84-perf-gb67345b (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x-goo
(bootloader) kernel.version[2]: gle 20140827 (prerelease) (GCC) ) #1 SMP
(bootloader) kernel.version[3]: PREEMPT Thu Sep 29 00:24:52 CDT 2016
(bootloader) sbl1.git: git=MBM-NG-VA0.43-0-g8cea836
(bootloader) rpm.git: git=90a41be
(bootloader) tz.git: git=16279de-dirty
(bootloader) hyp.git: git=16279de-dirty
(bootloader) sdi.git: git=52a3f93
(bootloader) pmic.git: git=MBM-NG-VA0.43-0-g8cea836
(bootloader) aboot.git: git=MBM-NG-VA0.43-0-gde54c6f
(bootloader) qe: qe 1/1
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.172s
C:\fastboot oem fb_mode_clear
...
OKAY [ -0.000s]
finished. total time: -0.000s
Today in the morning my XT1575 didn't boot and got directly into fastboot mode.
Every time I try to start it I get this message:
Start up failed:
Your device didn't start up successfully.
Use the Software Repair Assistant on computer to repair your device.
Connect your device to your computer to get the Software Repair Assistant.
Click to expand...
Click to collapse
I searched for a solution but still can't reach one.
I didn't try to downgrade nothing, in fact the phone isn't mine, it's my wife's and she doesn't know anything about flashing ROMs and stuff, so the problem was not there. The phone actually started to get tilted and slow one or two days ago and then today finally "died".
Here's the getvar all I get:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8992-A0.4D
(bootloader) product: clark
(bootloader) board: clark
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x2
(bootloader) emmc: 32GB Toshiba REV=07 PRV=00 TYPE=57 PNM=032G72
(bootloader) ram[0]: 3072MB SK Hynix S8 SDRAM DIE=6Gb M5=x6 M6=x3 M7=x0
(bootloader) ram[1]: M8=x3B
(bootloader) cpu: MSM8992
(bootloader) serialno: ZY223MG4VS
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x8d
(bootloader) uid: 16C4F0001E000000000000000000
(bootloader) unlocked: no
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 536870912
(bootloader) reason: Last time flashing failed
(bootloader) imei: 358195071196980
(bootloader) meid:
(bootloader) date: 11-08-2016
(bootloader) sku: XT1575
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Jul 31 20:42:21 UTC 2017"
(bootloader) ro.build.fingerprint[0]: motorola/clark_retus/clark:6.0/MPH
(bootloader) ro.build.fingerprint[1]: S24.49-18-16/8:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.231.16.clark_retu
(bootloader) ro.build.version.full[1]: s.retus.en.US
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband: M8992_1255331.29.01.88.02R SUPER_NA
(bootloader) kernel.version[0]: Linux version 3.10.84-perf-g94afac7 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x-goog
(bootloader) kernel.version[2]: le 20140827 (prerelease) (GCC) ) #1 SMP
(bootloader) kernel.version[3]: PREEMPT Thu Dec 8 06:11:12 CST 2016
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) hyp.git: hyp.git
(bootloader) sdi.git: sdi.git
(bootloader) pmic.git: pmic.git
(bootloader) aboot.git: git=MBM-NG-VA0.4D-0-g3d9d261
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier: retus
all: listed above
finished. total time: 0.466s
Click to expand...
Click to collapse
The CID say 0xDEAD. It switches to 0x0009 when I flash TWRP with windroid but I still can't flash any other rom because I keep getting these errors (the rom im trying to install is the official one, from motorola's web, MPH24.49-18_18):
C:\Users\Flia Boquense\Desktop\motox>fastboot flash partition gpt.bin
target max-download-size: 512MB
sending 'partition' (32 KB)...
OKAY [ 0.097s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.816s
BOOTLOADER LOG: "version downgraded for primary_gpt"
C:\Users\Flia Boquense\Desktop\motox>fastboot flash boot boot.img
target max-download-size: 512MB
sending 'boot' (40960 KB)...
OKAY [ 1.142s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.857s
BOOTLOADER LOG: "hab check failed for boot
failed to verify hab image boot"
C:\Users\Flia Boquense\Desktop\motox>fastboot flash recovery recovery.img
target max-download-size: 512MB
sending 'recovery' (41040 KB)...
OKAY [ 1.143s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.858s
BOOTLOADER LOG: "hab check failed for boot
failed to verify hab image boot"
C:\Users\Flia Boquense\Desktop\motox>fastboot flash system system.img
target max-download-size: 512MB
sending sparse 'system' (509631 KB)...
OKAY [ 15.608s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 16.565s
BOOTLOADER LOG: "hab check failed for boot
failed to verify hab image boot
invalid PIV signed system image"
Click to expand...
Click to collapse
I can't find a way to make it work again, any help will be appreciated, i'm pretty much a noob in all these stuff.
Your bootloader is locked? It appears so...
(bootloader) unlocked: no
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
Click to expand...
Click to collapse
How are you flashing TWRP with a locked bootloader?!?!?!
With a locked bootloader you cannot downgrade, the version on Moto's official site (MPH24.49-18_18) is actually just MPH24.49-18, which is the original Marshmallow when first released in December 2015. Moto support has been notified of this mistake in version and date on the website and have yet to change it in over 6 months since it was mis-posted.
You require MPHS24.49-18-16, which is the December 2016 security update released via OTA in February 2017, or newer version, but the problem is that it is not available. At this point we do not know if/when newer versions of factory firmware images will leak out or not in the future. The newest version we have available is MPHS24.49-18-8, you can attempt that and skip bootloader.img and gpt.bin, but I am guessing with a locked bootloader it will fail since it is still a downgrade.
You have a locked bootloader, with a bootloader state of 0? Contact Moto for repair, without an unlocked bootloader there is nothing we can can do at this point.
acejavelin said:
Your bootloader is locked? It appears so...
How are you flashing TWRP with a locked bootloader?!?!?!
With a locked bootloader you cannot downgrade, the version on Moto's official site (MPH24.49-18_18) is actually just MPH24.49-18, which is the original Marshmallow when first released in December 2015. Moto support has been notified of this mistake in version and date on the website and have yet to change it in over 6 months since it was mis-posted.
You require MPHS24.49-18-16, which is the December 2016 security update released via OTA in February 2017, or newer version, but the problem is that it is not available. At this point we do not know if/when newer versions of factory firmware images will leak out or not in the future. The newest version we have available is MPHS24.49-18-8, you can attempt that and skip bootloader.img and gpt.bin, but I am guessing with a locked bootloader it will fail since it is still a downgrade.
You have a locked bootloader, with a bootloader state of 0? Contact Moto for repair, without an unlocked bootloader there is nothing we can can do at this point.
Click to expand...
Click to collapse
Yes, my bootloader is locked. I understand that to unlock it, i have to get into developer's tools and change some option so I can get the code, am i right? Unluckily, there's no way i can do that since the phone won't start. Any other way to unlock it?
I tried to load other versions but it wont work, the errors i get are the same i get when installing the version from the webpage, so i guess they are related to the fact that they are older versions.
To sum it all, i have a rock with the form of a phone until Motorola's people hear us and upload the latest version??? Any crazy idea i could try to make the phone work?
Thank you for your time acejavelin, really appreciated.
I would contact Motorola support and see what they can do for you.
It will help to know which version of the Moto X that you have. Your thread title has Moto X Style, with the model number of the Moto X Pure Edition. The style is XT1572.
I would tell them that you tried to follow instructions listed on the phone with no luck. Remind them that current software is not available on their web site.
pizza_pablo said:
I would contact Motorola support and see what they can do for you.
It will help to know which version of the Moto X that you have. Your thread title has Moto X Style, with the model number of the Moto X Pure Edition. The style is XT1572.
I would tell them that you tried to follow instructions listed on the phone with no luck. Remind them that current software is not available on their web site.
Click to expand...
Click to collapse
Sorry, my bad, i have the Pure edition, XT1575. I will try to do that hoping to have some luck.
lcn23 said:
Yes, my bootloader is locked. I understand that to unlock it, i have to get into developer's tools and change some option so I can get the code, am i right? Unluckily, there's no way i can do that since the phone won't start. Any other way to unlock it?
I tried to load other versions but it wont work, the errors i get are the same i get when installing the version from the webpage, so i guess they are related to the fact that they are older versions.
To sum it all, i have a rock with the form of a phone until Motorola's people hear us and upload the latest version??? Any crazy idea i could try to make the phone work?
Thank you for your time acejavelin, really appreciated.
Click to expand...
Click to collapse
Any other way to unlock? Nope, impossible actually.
Basically, you need to contact Moto... because you are still locked and stock it can be repaired, either in or out of warranty. Once the bootloader has been unlocked Moto won't even look at it. And that "Software Repair Assistant" was Verizon specific I guess (weird, right), but you can try it https://www.verizonwireless.com/support/knowledge-base-209216/ since it seems to have support for Moto Z Force (it's in the sample picture) so who knows, might work.
Motorola doesn't release firmware images, except for what is on their webpage (which is old for all models listed) and even their requirements are for an unlocked bootloader. The only firmware images we have are ones that are leaked, and that source has reported that it is very difficult (almost impossible) to access these builds now... I would speculate it in part goes back to Moto's pattern of planned obsolescence, but at the same time these images affect such a small number of individuals that they probably don't care anyway.
---------- Post added at 08:31 PM ---------- Previous post was at 08:29 PM ----------
I just realized this is in the old Moto X 2013 area... I will request a Mod to move it.
MY wife somehow made it power on today in the morning. I guess that's the only hope as I wait for the Motorola Support to give me an answer. Impossible to send it to them for repair as i'm from Argentina and i bought it in USA.
Sorry about the misplacement.
Is there any recovery image I could somehow install bypassing the locked status?? The Windroid application "installs" a TWRP and it somehow manages to switch the CID from 0xDEAD to 0x0009, whatever that means.
You can try flash this (from the OP):
https://forum.xda-developers.com/moto-x-style/general/xt1575-stock-mphs24-49-18-16-files-t3641863
I suggest flash with fastboot. Just like you did before. @lcn23
dzidexx said:
You can try flash this (from the OP):
https://forum.xda-developers.com/moto-x-style/general/xt1575-stock-mphs24-49-18-16-files-t3641863
I suggest flash with fastboot. Just like you did before. @lcn23
Click to expand...
Click to collapse
Will try! Thank you!
dzidexx said:
You can try flash this (from the OP):
https://forum.xda-developers.com/moto-x-style/general/xt1575-stock-mphs24-49-18-16-files-t3641863
I suggest flash with fastboot. Just like you did before. @lcn23
Click to expand...
Click to collapse
No man, not working. I only got something different when trying to flash partition gpt.bin. The new error message is this one:
C:\Users\Flia Boquense\Desktop\motox\rom16>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.091s]
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: 0.963s
Click to expand...
Click to collapse
Your phone still is dead?
Try to flash only boot & system. @lcn23
---------- Post added at 06:38 PM ---------- Previous post was at 06:35 PM ----------
Are you using the newest minimal adb...?
https://devs-lab.com/download-minimal-adb-fastboot-tool.html
UPDATE: Somehow the fastboot changed, the buttons with the options turned into a menu with options inside a light blue bubble and an image of the android pet with his belly open appeared. Seeing this, I tried to flash the gpt bin dzidexx gave me and it worked, but after that I tried to flash the bootloader and it didn't work. I guess I will try again later, because now I'm leaving to work. I will try what you told me later dzidexx. Thanks.
UPDATE 2: After that happened and i rebooted the phone, now its status switched from "stuck at fastboot" to "doesn't power up". I guess I screwed up. How can I fix that? When I plug it to the computer, the PC makes the sound of something being connected to one of her USB ports, but other than that there's nothing I get, it doesn't even appear in Windows Explorer as a connected device. @dzidexx
Nothing you can do in home.
I think the motherboard is broken(before you asked here) - memory.
Sometimes it happens.
Only warranty repair or other GSM service(motherboard replacement). @lcn23
I guess it has something to do with the aboot, because that was the only thing that got installed when flashing bootloader.img.
With locked BL you cannot check/repair it. @lcn23
Then I guess I hard fkin bricked it, damn me.
@acejavelin any ideas of how can I take it out of QHSUSB state??
lcn23 said:
@acejavelin any ideas of how can I take it out of QHSUSB state??
Click to expand...
Click to collapse
Nope... Bootloader is gone if it's going QLoad mode, nothing can be done now but get Moto to fix it. We don't have the necessary files to flash in this state.
lcn23 said:
Today in the morning my XT1575 didn't boot and got directly into fastboot mode.
Every time I try to start it I get this message:
I searched for a solution but still can't reach one.
I didn't try to downgrade nothing, in fact the phone isn't mine, it's my wife's and she doesn't know anything about flashing ROMs and stuff, so the problem was not there. The phone actually started to get tilted and slow one or two days ago and then today finally "died".
Here's the getvar all I get:
The CID say 0xDEAD. It switches to 0x0009 when I flash TWRP with windroid but I still can't flash any other rom because I keep getting these errors (the rom im trying to install is the official one, from motorola's web, MPH24.49-18_18):
I can't find a way to make it work again, any help will be appreciated, i'm pretty much a noob in all these stuff.
Click to expand...
Click to collapse
Go here, https://forum.xda-developers.com/moto-x-style/general/xt1575-stock-mphs24-49-18-16-files-t3641863, and flash recovery. Then tell us if it works.
when i trying to install latest gpt.bin and bootloader and i try older also it is showing
(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 [ 0.000s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.078s
Bootloader
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (3651 KB)...
OKAY [ 0.126s]
writing 'bootloader'...
(bootloader) validating: bootloader.default.xml ...
(bootloader) Invalid partition name aboot
(bootloader) will fail: flash:aboot
FAILED (remote failure)
finished. total time: 0.263s
please help.
Which blankflash files are you using that are causing this error, the September 2017 or June 2017 ones?
You may wish to try the December 2017 GPT and bootloader files : https://drive.google.com/open?id=1IfAX7v94ooB5wS7KTJGNYfQ2kXkHxP80
If the December 2017 GPT/bootloader files work, then you will want to re-flash the NPJS25.93-14-13 stock ROM (mainly for Brazil, India, EU and UK users, may flash onto other region's devices) to fully repair: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Likhith Emmanuel said:
when i trying to install latest gpt.bin and bootloader and i try older also it is showing
(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 [ 0.000s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.078s
Bootloader
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (3651 KB)...
OKAY [ 0.126s]
writing 'bootloader'...
(bootloader) validating: bootloader.default.xml ...
(bootloader) Invalid partition name aboot
(bootloader) will fail: flash:aboot
FAILED (remote failure)
finished. total time: 0.263s
please help.
Click to expand...
Click to collapse
Same error while unlocking bootloader..moto g4 xt1624
Samruddh said:
Same error while unlocking bootloader..moto g4 xt1624
Click to expand...
Click to collapse
Can I ask what steps you've tried when unlocking the bootloader please? Have you followed this guide, https://forum.xda-developers.com/showpost.php?p=67031801&postcount=2 and if so, what errors are you getting? If you could, please post a screenshot of the error or the text of the error.
Is your device bought from a carrier (and thus carrier locked) or an Amazon Prime device or was it from Amazon/a retailer?
Could we see your getvar info please?
1)Boot your device to the bootloader. Connect via USB to your computer.
2)In the ADB terminal, type 'fastboot getvar all' without quotes. Press Enter.
3)Paste the output into a post here please. You may wish to remove IMEI numbers.
echo92 said:
Can I ask what steps you've tried when unlocking the bootloader please? Have you followed this guide, https://forum.xda-developers.com/showpost.php?p=67031801&postcount=2 and if so, what errors are you getting? If you could, please post a screenshot of the error or the text of the error.
Is your device bought from a carrier (and thus carrier locked) or an Amazon Prime device or was it from Amazon/a retailer?
Could we see your getvar info please?
1)Boot your device to the bootloader. Connect via USB to your computer.
2)In the ADB terminal, type 'fastboot getvar all' without quotes. Press Enter.
3)Paste the output into a post here please. You may wish to remove IMEI numbers.
Click to expand...
Click to collapse
Yeah i ordered in amazon
Samruddh said:
Yeah i ordered in amazon
Click to expand...
Click to collapse
Okay, was it an Amazon Prime device (with the adverts on the lock screen) or just a retail device sold by Amazon?
As far as I know, the Amazon Prime version cannot have its bootloader unlocked, and Motorola won't issue an unlock key for such devices. You'll know if it's an Amazon Prime device from adverts on the lockscreen and if you go to Settings>About Phone, under software channel it'll say AMZ. On retail devices it'll be retin (retail India) or reteu (retail Europe) etc.
echo92 said:
Okay, was it an Amazon Prime device (with the adverts on the lock screen) or just a retail device sold by Amazon?
As far as I know, the Amazon Prime version cannot have its bootloader unlocked, and Motorola won't issue an unlock key for such devices. You'll know if it's an Amazon Prime device from adverts on the lockscreen and if you go to Settings>About Phone, under software channel it'll say AMZ. On retail devices it'll be retin (retail India) or reteu (retail Europe) etc.
Click to expand...
Click to collapse
Retin it is showing..pls do check attachment..help me with this..i want to root my phone to do customizations..im bored with this 7.0
Samruddh said:
Retin it is showing..pls do check attachment..help me with this..i want to root my phone to do customizations..im bored with this 7.0
Click to expand...
Click to collapse
Okay, and can you post the getvar info as previously requested please?
Can I ask what steps you performed to attempt to unlock your bootloader as well? I'd like to know how far you got so we can help you.
echo92 said:
Okay, and can you post the getvar info as previously requested please?
Can I ask what steps you performed to attempt to unlock your bootloader as well? I'd like to know how far you got so we can help you.
Click to expand...
Click to collapse
Ok ll execute getvar command soon..
I followed same steps as u shown in that link..
* Switched on developer option to enable oem unlocking n usb debugging
*Downloaded n installed sdk tools
*From motorola website Writing commands to unlock oem data by opening shift+right button command window
It always shows
Failed to get unlock data
0.350(some seconds)
Finished
Samruddh said:
Ok ll execute getvar command soon..
I followed same steps as u shown in that link..
* Switched on developer option to enable oem unlocking n usb debugging
*Downloaded n installed sdk tools
*From motorola website Writing commands to unlock oem data by opening shift+right button command window
It always shows
Failed to get unlock data
0.350(some seconds)
Finished
Click to expand...
Click to collapse
The same it shows as in the following attachment
Samruddh said:
Ok ll execute getvar command soon..
I followed same steps as u shown in that link..
* Switched on developer option to enable oem unlocking n usb debugging
*Downloaded n installed sdk tools
*From motorola website Writing commands to unlock oem data by opening shift+right button command window
It always shows
Failed to get unlock data
0.350(some seconds)
Finished
Click to expand...
Click to collapse
Can you try with the minimal ADB tools as well? https://forum.xda-developers.com/showthread.php?t=2317790 and with the minimal ADB tools, use 'fastboot oem get_unlock_data' without quotes.
Have you had your motherboard changed? If not, and you cannot get the unlock data, then you may have to post to the official Lenovo/Motorola forums: https://forums.lenovo.com/t5/forums/v3_1/forumtopicpage/board-id/230/thread-id/2654/page/1
As requested in the first post of that page, please provide the getvar info and the result of the get_unlock_data (whatever it is) in your post, else the admin may not forward your request to the internal team.
Samruddh said:
I tried with adb tools and I've not changed motherboard..here s result of getvar
Click to expand...
Click to collapse
Hmm, you have a CID of 0x0000 which should be unlockable. I wonder what's happened to your ro.carrier though, that should read retin rather than unknown.
I'd post on the Lenovo/Motorola forum I linked above with the information requested in the opening post of that thread. By the way, you can copy by right clicking in the menubar of the command line window then going to Edit>Copy. Saves you having to take a screenshot and they'll want a text entry.
echo92 said:
Hmm, you have a CID of 0x0000 which should be unlockable. I wonder what's happened to your ro.carrier though, that should read retin rather than unknown.
I'd post on the Lenovo/Motorola forum I linked above with the information requested in the opening post of that thread. By the way, you can copy by right clicking in the menubar of the command line window then going to Edit>Copy. Saves you having to take a screenshot and they'll want a text entry.
Click to expand...
Click to collapse
Ok..ll paste the text info from next! Thanks!
echo92 said:
Hmm, you have a CID of 0x0000 which should be unlockable. I wonder what's happened to your ro.carrier though, that should read retin rather than unknown.
I'd post on the Lenovo/Motorola forum I linked above with the information requested in the opening post of that thread. By the way, you can copy by right clicking in the menubar of the command line window then going to Edit>Copy. Saves you having to take a screenshot and they'll want a text entry.
Click to expand...
Click to collapse
Any updates on this?
Samruddh said:
Any updates on this?
Click to expand...
Click to collapse
Did you post on the Lenovo/Motorola official forum thread as directed? They are the only ones likely to help you at this stage.
I see one new report from an athene device in the last few days, but that device is from Argentina. As an aside, that report has no IMEI, which may slow down the help to get their code.
Please post in the Bootloader Unlock thread on the Motorola/Lenevo forum, with the getvar info (with IMEI) and the result of the get_unlock_data as directed. They then should forward the message to their internal teams and look for an email response in 48-72 hours (or 2-3 working days).
facing same issue
anyone found solution for this?
i have an indian version xt1643
"failed to initialize partition table" main problem i guess
it'd be great if i get any help
Utcresta said:
anyone found solution for this?
i have an indian version xt1643
"failed to initialize partition table" main problem i guess
it'd be great if i get any help
Click to expand...
Click to collapse
Hmm, what have you tried so far? Can you describe what happened before experiencing this error?
Looking through your image, though it's quite low resolution, I see no entries in your firmware version or kernel or baseband, which suggests you used the blankflash at some point?
echo92 said:
Hmm, what have you tried so far? Can you describe what happened before experiencing this error?
Looking through your image, though it's quite low resolution, I see no entries in your firmware version or kernel or baseband, which suggests you used the blankflash at some point?
Click to expand...
Click to collapse
I had Resurrection Remix Oreo on the device. I was just using the phone casually with vanced youtube running on the background and facebook messenger too. Suddenly it froze so i tried to restart it but no response and then after some time the screen went blank. When plugged in to charge, the led glowed and screen was plain blank without the screen lighting up. So I googled and found the following thread.
https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016
Followed the procedure then the screen was up again. The screen i got after doing this is below. Sorry for the low resolution hope you can understand it.
https://imgur.com/a/mAUFgiJ
IMEI is gone. It shows all 0s in the imei field. Tried flashing stock recovery, custom recovery, twrp no luck. The device is recognized as "fastboot athene_16mp S" when connected to pc.
Hope you can help.
Utcresta said:
I had Resurrection Remix Oreo on the device. I was just using the phone casually with vanced youtube running on the background and facebook messenger too. Suddenly it froze so i tried to restart it but no response and then after some time the screen went blank. When plugged in to charge, the led glowed and screen was plain blank without the screen lighting up. So I googled and found the following thread.
https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016
Followed the procedure then the screen was up again. The screen i got after doing this is below. Sorry for the low resolution hope you can understand it.
https://imgur.com/a/mAUFgiJ
IMEI is gone. It shows all 0s in the imei field. Tried flashing stock recovery, custom recovery, twrp no luck. The device is recognized as "fastboot athene_16mp S" when connected to pc.
Hope you can help.
Click to expand...
Click to collapse
That isn't your actual fastboot mode. fastboot getvar will not show proper details. I too had tried and got imei as multiple 0 with "fastboot getvar", also had seen a lot of other things missing too.
Download and flash the latest stock nougat from here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Before flashing stock rom, you will need to flash latest "bootloader" and "gpt". First flash bootloader and gpt and then reboot to bootloader (fastboot reboot bootloader).
Now you will have your original bootloader back. Now you can flash stock nougat rom and everything will be back to normal.
I hope you have not upgraded to soak test oreo by "locked bootloader" method because if you did then you will have to wait till fastboot rom for oreo comes out or ask someone who is on soak test oreo to provide their bootloader and gpt partitions (if they upgrades by locked bootloader method), as you wouldn't be able to flash nougat bootloader and gpt partitions.
i have a similar problem on my xt1643 as it is only booting to the locked bootloader, and tried all the gpt.bin till april 2018 while all the others gave the downgrade error, april 2018 gave the following error.
PS C:\adb> 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 [ 0.005s]
writing 'partition'...
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) Failed to write EFI backup GPT header.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 0.086s
PS C:\adb>
---------- Post added at 03:03 PM ---------- Previous post was at 03:00 PM ----------
Athul56 said:
i have a similar problem on my xt1643 as it is only booting to the locked bootloader, and tried all the gpt.bin till april 2018 while all the others gave the downgrade error, april 2018 gave the following error.
PS C:\adb> 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 [ 0.005s]
writing 'partition'...
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) Failed to write EFI backup GPT header.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 0.086s
PS C:\adb>
Click to expand...
Click to collapse
PS C:\adb> fastboot getvar all
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8952-B1.07
(bootloader) product: athene_16mp
(bootloader) board: athene_16mp
(bootloader) secure: yes
(bootloader) hwrev: P2A
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB MICRON Q3J97V RV=08 PV=10 FV=00000000000000A2
(bootloader) ram: 3GB MICRON LP3 DIE=6Gb M5=03 M6=00 M7=00 M8=7B
(bootloader) cpu: MSM8952
(bootloader) serialno: ZY223RFGVV
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: DB66230200000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Last time flashing failed
(bootloader) imei: *************
(bootloader) meid:
(bootloader) date: 01-07-2017
(bootloader) sku: XT1643
(bootloader) battid: SNN5970A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Aug 2 4:37: 6 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/athene_f/athene_f:7.0/NPJ
(bootloader) ro.build.fingerprint[1]: S25.93-14-18/3:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.25.236.3.athene.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.BR.1.3.6-01710-8976.0
(bootloader) version-baseband[0]: M8952_70030.25.03.62.02R ATHENE_INDIA_
(bootloader) version-baseband[1]: DSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.10.84-ge03508d-00131-g44
(bootloader) kernel.version[1]: 2576f ([email protected]) (gcc version
(bootloader) kernel.version[2]: 4.8 (GCC) ) #1 SMP PREEMPT Wed Mar 28 06
(bootloader) kernel.version[3]: :58:16 CDT 2018
(bootloader) sbl1.git: git=MBM-NG-VB1.07-0-g57d1343
(bootloader) rpm.git: git=MBM-NG-VB1.06-0-ga970ead
(bootloader) tz.git: git=69dd24b-dirty
(bootloader) hyp.git: git=69dd24b-dirty
(bootloader) keymaster.git: git=69dd24b-dirty
(bootloader) cmnlib.git: git=69dd24b-dirty
(bootloader) aboot.git: git=MBM-NG-VB1.07-0-gf9b89ba
(bootloader) qe: qe 0/0
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retin
all: listed above
Hey, Im new to the site so sorry if this has been covered. I've searched but Im at a loss.
I've got a moto g7 from amazon I attempted to flash stock firmware to. I got it unlocked but after much trouble I decided to lock it and give up. I locked it with the signed boot.img but now it only boots into fastboot mode. Im assuming I might've wiped the firmware somehow? It'll only boot to the moto logo and fastboot setting. I just want to get it functioning again if possible. Can anyone help me out with some concise direction/help? Not sure what all info is needed but I will answer best I can. Much appreciated.
retrosk8r said:
Hey, Im new to the site so sorry if this has been covered. I've searched but Im at a loss.
I've got a moto g7 from amazon I attempted to flash stock firmware to. I got it unlocked but after much trouble I decided to lock it and give up. I locked it with the signed boot.img but now it only boots into fastboot mode. Im assuming I might've wiped the firmware somehow? It'll only boot to the moto logo and fastboot setting. I just want to get it functioning again if possible. Can anyone help me out with some concise direction/help? Not sure what all info is needed but I will answer best I can. Much appreciated.
Click to expand...
Click to collapse
Do fastboot commands still work?
Like
Code:
fastboot getvar all
Sent from my mata using XDA Labs
sd_shadow said:
Do fastboot commands still work?
Like
Code:
fastboot getvar all
Sent from my mata using XDA Labs
Click to expand...
Click to collapse
Yes, they do.
HTML:
(bootloader) version: 0.5
(bootloader) version-bootloader: MB
(bootloader) product: river
(bootloader) board: river
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB MICRON S0J9
(bootloader) ram: 4GB MICRON LP3 DI
(bootloader) cpu: SDM632
(bootloader) serialno: ZY226H2MPG
(bootloader) cid: 0x0032
(bootloader) channelid: 0x93
(bootloader) uid: 7C674ACC000000000
(bootloader) securestate: flashing_
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536
(bootloader) reason: Volume down ke
(bootloader) meid:
(bootloader) date: 07-21-2019
(bootloader) sku: XT1962-1
(bootloader) carrier_sku: XT1962-1
(bootloader) battid: SB18C34004
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 26843
(bootloader) current-time: "Fri Feb
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband: <not
(bootloader) kernel.version[0]: Lin
(bootloader) kernel.version[1]: clb
(bootloader) kernel.version[2]: ere
(bootloader) kernel.version[3]: 16
(bootloader) sbl1.git: MBM-2.1-rive
(bootloader) rpm.git: MBM-2.1-river
(bootloader) tz.git: MBM-2.1-river_
(bootloader) devcfg.git: MBM-2.1-ri
(bootloader) keymaster.git: MBM-2.1
(bootloader) cmnlib.git: MBM-2.1-ri
(bootloader) cmnlib64.git: MBM-2.1-
(bootloader) prov.git: MBM-2.1-rive
(bootloader) aboot.git: MBM-2.1-riv
(bootloader) frp-state: no protecti
(bootloader) ro.carrier: amz
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: No
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 3
(bootloader) slot-retry-count:_b: 0
retrosk8r said:
Yes, they do.
product: river
secure: yes
Click to expand...
Click to collapse
Not sure if this got cutoff does it say flashing_unlocked here
securestate: flashing_
iswarrantyvoid: yes
Click to expand...
Click to collapse
You may want to remove this line from your post
imei: xxxxxxxxxx
sku: XT1962-1
carrier_sku: XT1962-1
Click to expand...
Click to collapse
Did you start with amazon software channel?
ro.carrier: amz
current-slot: a
slot-count: 2
slot-successful:_a: No
slot-successful:_b: No
slot-bootable:_a: Yes
slot-bootable:_b: Yes
Click to expand...
Click to collapse
Sent from my mata using XDA Labs
sd_shadow said:
Not sure if this got cutoff does it say flashing_unlocked here
securestate: flashing_
You may want to remove this line from your post
imei: xxxxxxxxxx
Did you start with amazon software channel?
ro.carrier: amz
Sent from my mata using XDA Labs
Click to expand...
Click to collapse
Yes, its flashing_unlocked
Thanks, I removed it. Forgot about that.
No, I haven't. Not sure what you mean. Sorry if its obvious, new here.
retrosk8r said:
Yes, its flashing_unlocked
Thanks, I removed it. Forgot about that.
No, I haven't. Not sure what you mean. Sorry if its obvious, new here.
Click to expand...
Click to collapse
Looks like bootloader is still unlocked
Which software channel did you flash? Retus, amz, ...
Which commands?
Sent from my perry_f using XDA Labs
sd_shadow said:
Looks like bootloader is still unlocked
Which software channel did you flash? Retus, amz, ...
Which commands?
Sent from my perry_f using XDA Labs
Click to expand...
Click to collapse
Oh, I was trying to use Retus.
If you are not sure about weather it was on
Amazon software channel
Retus is a fairly safe choice with unlocked bootloader
https://mirrors.lolinet.com/firmware/moto/river/official/RETUS/
Sent from my perry_f using XDA Labs
---------- Post added at 05:25 AM ---------- Previous post was at 05:24 AM ----------
retrosk8r said:
Oh, I was trying to use Retus.
Click to expand...
Click to collapse
It say Amazon now
Sent from my perry_f using XDA Labs
sd_shadow said:
If you are not sure about weather it was on
Amazon software channel
Retus is a fairly safe choice with unlocked bootloader
https://mirrors.lolinet.com/firmware/moto/river/official/RETUS/
Sent from my perry_f using XDA Labs
---------- Post added at 05:25 AM ---------- Previous post was at 05:24 AM ----------
It say Amazon now
Sent from my perry_f using XDA Labs
Click to expand...
Click to collapse
I wanted to flash retus stock firmware to get rid of the amazon trash. Gave up and tried locking the bootloader to get rid of the 5 second warning screen but ended up with a frozen moto logo boot screen and access to only fastboot.
Edit: I take that back, now it only boots into fastboot.
You can use the commands from
https://forum.xda-developers.com/moto-g7/how-to/manually-update-g7-using-fastboot-t3917381
Or see my
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
I suggest flashing each command one at a time.
Then see if it boots
If it boot and wif and lte work
You could try locking the bootloader again
See relocking link in my thread
Sent from my perry_f using XDA Labs
sd_shadow said:
You can use the commands from
https://forum.xda-developers.com/moto-g7/how-to/manually-update-g7-using-fastboot-t3917381
Or see my
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
I suggest flashing each command one at a time.
Then see if it boots
If it boot and wif and lte work
You could try locking the bootloader again
See relocking link in my thread
Sent from my perry_f using XDA Labs
Click to expand...
Click to collapse
Can I flash retus or am I required to use amz?
retrosk8r said:
I wanted to flash retus stock firmware to get rid of the amazon trash. Gave up and tried locking the bootloader to get rid of the 5 second warning screen but ended up with a frozen moto logo boot screen and access to only fastboot.
Edit: I take that back, now it only boots into fastboot.
Click to expand...
Click to collapse
Flashing Retus should work
Sent from my perry_f using XDA Labs
I see. Thanks. I'll try it tomorrow. Its late where I am and I have work. I'll post back into this thread regarding any issues or if it works out.
I followed the commands from https://forum.xda-developers.com/mot...tboot-t3917381 and its booted. So far everything seems functional but I'll play around with it for a week or two to be sure before locking it. I assume after locking it I will be able to retrieve updates? Thanks for the help, majorly.
retrosk8r said:
I followed the commands from https://forum.xda-developers.com/mot...tboot-t3917381 and its booted. So far everything seems functional but I'll play around with it for a week or two to be sure before locking it. I assume after locking it I will be able to retrieve updates? Thanks for the help, majorly.
Click to expand...
Click to collapse
I did this not too long ago and mine has been fine afterward. If it does continue to reboot into fastboot (mine does) just hit start and it should be just fine. Mine is actually faster since I rooted it.
retrosk8r said:
Hey, Im new to the site so sorry if this has been covered. I've searched but Im at a loss.
I've got a moto g7 from amazon I attempted to flash stock firmware to. I got it unlocked but after much trouble I decided to lock it and give up. I locked it with the signed boot.img but now it only boots into fastboot mode. Im assuming I might've wiped the firmware somehow? It'll only boot to the moto logo and fastboot setting. I just want to get it functioning again if possible. Can anyone help me out with some concise direction/help? Not sure what all info is needed but I will answer best I can. Much appreciated.
Click to expand...
Click to collapse
Get "Lenovo Moto Support Assistant" Here is executable link: https://download.lenovo.com/consumer...0.14_setup.exe