Recently acquired a bricked moto x pure. No way of knowing for sure how it was bricked but I'm guessing attempted downgrade. When starting up the Bootloader logs say:
AP fastboot flash mode (secure)
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Fastboot reason: Fall-through from charger boot mode
CID read failure
Invalid CID status 0x69
Click to expand...
Click to collapse
fastboot getvar all gives:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8992-A0.48(*)
(bootloader) product: clark
(bootloader) board: clark
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x2
(bootloader) emmc: 16GB Samsung REV=07 PRV=01 TYPE=57 PNM=AGND3R
(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: TA084034CW
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x8d
(bootloader) uid: 3862CC001E000000000000000000
(bootloader) unlocked: no
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 536870912
(bootloader) reason: Fall-through from charger boot mode
(bootloader) date: 10-07-2015
(bootloader) sku: XT1575
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Mar 9 14:23:32 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/clark_retus/clark:6.0/MPH
(bootloader) ro.build.fingerprint[1]: S24.49-18-3/3:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.201.3.clark_retus
(bootloader) ro.build.version.full[1]: .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-g6898f68 (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 Sat Jan 30 14:35:02 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.48-0-g8c942c6
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier: retus
all: listed above
finished. total time: 0.422s
Click to expand...
Click to collapse
I attempted to flash the CLARK_RETUS_6.0_MPHS24.49-18-3_cid9_subsidy-DEFAULT_CFC.xml stock firmware but got the following error:
fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.094s]
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.953s
Click to expand...
Click to collapse
I also tried using mfastboot, with the same results. Anybody know how to fix this?
Is your bootloader locked?
thebaconbox said:
Is your bootloader locked?
Click to expand...
Click to collapse
Yes it is. Tried to unlock it already but I get:
>fastboot oem get_unlock_data
...
(bootloader) Failed to get unlock data, please try again!
FAILED (remote failure)
finished. total time: 0.016s
Click to expand...
Click to collapse
Just ignore the gpt.bin error and continue... The partition table hasn't changed since Marshmallow released on this device.
Any reason not to use the 18-4 firmware? It is readily available...
acejavelin said:
Just ignore the gpt.bin error and continue... The partition table hasn't changed since Marshmallow released on this device.
Any reason not to use the 18-4 firmware? It is readily available...
Click to expand...
Click to collapse
I tried 18-4 as well and got the same results. 18-3 seemed to be what was on the device before it was bricked so I tried that one first. If I continue get more errors:
>fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (2699 KB)...
OKAY [ 0.094s]
writing 'bootloader'...
(bootloader) flashing aboot ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash aboot
FAILED (remote failure)
finished. total time: 1.961s
>fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (3687 KB)...
OKAY [ 0.141s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.234s
Click to expand...
Click to collapse
I get the same errors if I try to flash anything.
jml1290 said:
I tried 18-4 as well and got the same results. 18-3 seemed to be what was on the device before it was bricked so I tried that one first. If I continue get more errors:
I get the same errors if I try to flash anything.
Click to expand...
Click to collapse
Try 'fastboot oem fb_mode_clear' followed by 'fastboot oem fb_mode_set' and try again.
acejavelin said:
Try 'fastboot oem fb_mode_clear' followed by 'fastboot oem fb_mode_set' and try again.
Click to expand...
Click to collapse
Here's what I get:
>fastboot oem fb_mode_clear
...
OKAY [ 0.000s]
finished. total time: 0.000s
>fastboot oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.000s
>fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (2699 KB)...
OKAY [ 0.078s]
writing 'bootloader'...
(bootloader) flashing aboot ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash aboot
FAILED (remote failure)
finished. total time: 1.561s
Click to expand...
Click to collapse
jml1290 said:
Here's what I get:
Click to expand...
Click to collapse
Hmm... Looks bad... Nothing will write, erase, or format, like the emmc module is bad.
acejavelin said:
Hmm... Looks bad... Nothing will write, erase, or format, like the emmc module is bad.
Click to expand...
Click to collapse
That's what I was afraid of. My only other idea was to try and force the phone into HS-USB QDLoader mode and fix it from there. But I have no idea how to do this and if there was something physically wrong with the emmc I doubt it would help anyway. Thanks for the input!
jml1290 said:
That's what I was afraid of. My only other idea was to try and force the phone into HS-USB QDLoader mode and fix it from there. But I have no idea how to do this and if there was something physically wrong with the emmc I doubt it would help anyway. Thanks for the input!
Click to expand...
Click to collapse
Sorry... But if the bootloader is locked you might be able to register it on your Motorola account and file a warranty claim, couldn't hurt to try.
I have my 6P connected via USB to my PC. I see the device in Device Manager as Android Bootloader Interface. I on the 6P, in bootloader mode, listed at the bottom is "Connect USB Data Cable". I know the USB cable works as I was able to boot into Android and see it as a drive on my PC.
Other items listed:
Product/Variant: ANGLER-VN2
Device is locked
Qfuse Status: ENABLED
Download Mode: Disabled
Should still be working. Try running fastboot getvar all, or just fastboot devices, on it and see if it works. I know mine always shows the "Connect USB Data Cable" text regardless.
eragon5779 said:
Should still be working. Try running fastboot getvar all, or just fastboot devices, on it and see if it works. I know mine always shows the "Connect USB Data Cable" text regardless.
Click to expand...
Click to collapse
fastboot devices:
84B5T15A29016374 fastboot
C:\WINDOWS\system32>fastboot getvar all
(bootloader) version:0.01
(bootloader) unlocked:no
(bootloader) hardware-revision:ANGLER-VN2
(bootloader) version-baseband:angler-03.84
(bootloader) version-bootloader:angler-03.75
(bootloader) display-panel:
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x1d800000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x6400000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x66257ee00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xc0000000
(bootloader) serialno:84B5T15A29016374
(bootloader) kernel:lk
(bootloader) product:angler
all:
finished. total time: 0.190s
I was able to unlock it this try.
C:\WINDOWS\system32>fastboot flashing unlock
...
(bootloader) Please select 'YES' on screen if you want to continue...
(bootloader) Unlocking bootloader...
(bootloader) Unlocked!
OKAY [ 11.930s]
finished. total time: 11.930s
C:\WINDOWS\system32>
Hello there,
I am trying to root my nokia 6 TA - 1033.
(bootloader) version:0.5
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4029000
(bootloader) variant:FIH eMMC
(bootloader) unlocked:no
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0xf0000000
(bootloader) partition-type:userdata:ext4
(bootloader) kernel:lk
(bootloader) product1C
1. cmd : fastboot oem dm-verity XXXXXXXXXXXXXXXXXXXXXXXX (MD5 number)
FAILED (remote: unknown command)
finished. total time: 0.005s
2. no help with this cmd too : adb reboot "dm-verity enforcing"
fastboot oem disable_dm_verity
3. fastboot flash recovery /home/$USER/me.twrp.twrpapp-26.apk
target reported max download size of 535822336 bytes
sending 'recovery' (2703 KB)...
OKAY [ 0.109s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.113s
gaganhere said:
Hello there,
I am trying to root my nokia 6 TA - 1033.
(bootloader) version:0.5
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4029000
(bootloader) variant:FIH eMMC
(bootloader) unlocked:no
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0xf0000000
(bootloader) partition-type:userdata:ext4
(bootloader) kernel:lk
(bootloader) product1C
1. cmd : fastboot oem dm-verity XXXXXXXXXXXXXXXXXXXXXXXX (MD5 number)
FAILED (remote: unknown command)
finished. total time: 0.005s
2. no help with this cmd too : adb reboot "dm-verity enforcing"
fastboot oem disable_dm_verity
3. fastboot flash recovery /home/$USER/me.twrp.twrpapp-26.apk
target reported max download size of 535822336 bytes
sending 'recovery' (2703 KB)...
OKAY [ 0.109s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.113s
Click to expand...
Click to collapse
WhatsApp me at 9650710447 for bootloader unlock
sltushar said:
WhatsApp me at 9650710447 for bootloader unlock
Click to expand...
Click to collapse
I also want to root nokia 6.1 plus
rohitgnw said:
I also want to root nokia 6.1 plus
Click to expand...
Click to collapse
I also want to root my device.... Any help?
rohitgnw said:
I also want to root nokia 6.1 plus
Click to expand...
Click to collapse
You need bootloader unlock key, pm me for that on WhatsApp
Hello
any one can help please, I relocked my bootloader. Since that day, I can only access : fastboot.
It seems I can flash recovery with fastboot, but the phone never boots into recovery (loop on ZTE logo B2017G ).
I've tried to put my device in EDL mode with DeepFlash cable but without success.
-------------
fastboot getvar all
(bootloader) version:0.5
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3447000
(bootloader) variant:TULIP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x12c00000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5ebb79e00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x100000000
(bootloader) serialno:bc13c89a
(bootloader) kernel:lk
(bootloader) product:TULIP
all:
finished. total time: 0.022s
------
fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.007s]
finished. total time: 0.007s
-------
Thanks
Hi there,
im trying to fix an htc u ultra. the problem is a endless bootloop.
Recovery and Download mode doesnt works but still the fastboot.
when i try to boot the phone into dl or recovery mode it still restarts after some seconds.
when i try to get sone informations with htc_fastboot getvar all i got this result
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:Surf eMMC
(bootloader) boot-mode:FASTBOOT
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0xe000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xdbf000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xdc000000
(bootloader) serialno:CENSORED
all:
finished. total time: 0.397s
htc_fastboot finished. total time: 7.437s
i have the stock rom but i dont know how to flash because the dl mode doesnt works..
the bootloader is locked and S-ON