So I dropped my Turbo and the screen shattered. I'd taken the Turbo apart before (replacing battery) so I am familiar with how to do it and what NOT to do. Note that this happened last week so the Turbo has been sitting in pieces without the battery attached to the motherboard.
Note: My Turbo is unlocked, rooted, with TWRP recovery and has Resurrection Remix custom ROM installed.
Ordered a new screen and digitizer; replaced it and put the Turbo back together. Powered it up and - woo hoo (I thought) - The Moto logo showed up fine on the new screen! Problem is, it boot loops constantly thru the Moto logo - can't get any further than that.
I can boot to my bootloader, which shows:
AF Fastboot Flast Mode (Secure)
...
...
Device is UNLOCKED. Status Code: 3
Software Status: Modified
Transfer Mode: USB Connected.
And ran mfastboot.exe getvar all which returned:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-apq8084-70.8A
(bootloader) product: quark
(bootloader) board: quark
(bootloader) secure: yes
(bootloader) hwrev: 0x84A0
(bootloader) radio: 0x4
(bootloader) emmc: 32GB Sandisk REV=07 PRV=01 TYPE=57
(bootloader) ram: 3072MB Samsung S8 SDRAM DIE=6Gb
(bootloader) cpu: APQ8084 ES1.1
(bootloader) serialno: xxxxxxxxxxxxxxxxxxxxxxxxx
(bootloader) cid: 0x0002
(bootloader) channelid: 0x00
(bootloader) uid: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
(bootloader) unlocked: yes
(bootloader) securestate: unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid:
(bootloader) date: 09-29-2014
(bootloader) sku: XT1254
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Apr 19 9:58:54 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/quark_verizon/quark:5.1/S
(bootloader) ro.build.fingerprint[1]: U4TL-44/44:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.23.21.44.quark_veriz
(bootloader) ro.build.version.full[1]: on.verizon.en.US
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.10.40-perf-g90ddf4a (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (GCC)
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Tue Sep 1 22:50:23 CDT
(bootloader) kernel.version[3]: 2015
(bootloader) sdi.git: git=MBM-NG-V70.8A-0-gf291c61
(bootloader) sbl1.git: git=MBM-NG-V70.8A-0-g60ea7e6
(bootloader) rpm.git: git=MBM-NG-V70.8A-0-g18b261e
(bootloader) tz.git: git=MBM-NG-V70.8A-0-gce6d7d0
(bootloader) aboot.git: git=MBM-NG-V70.8A-0-g021bfc8
(bootloader) partition-type:modem: raw
(bootloader) partition-type:sbl1: raw
(bootloader) partition-type:sdi: raw
(bootloader) partition-type:sec: raw
(bootloader) partition-type:ddr: raw
(bootloader) partition-type:aboot: raw
(bootloader) partition-type:rpm: raw
(bootloader) partition-type:utags: raw
(bootloader) partition-type:tz: raw
(bootloader) partition-type:factorytune1: raw
(bootloader) partition-typeadA: raw
(bootloader) partition-type:sbl1bak: raw
(bootloader) partition-type:abootBackup: raw
(bootloader) partition-type:rpmBackup: raw
(bootloader) partition-type:utagsBackup: raw
(bootloader) partition-type:tzBackup: raw
(bootloader) partition-type:mdm1m9kefs1: raw
(bootloader) partition-type:mdm1m9kefs2: raw
(bootloader) partition-typeadB: raw
(bootloader) partition-type:frp: raw
(bootloader) partition-type:logs: raw
(bootloader) partition-typeersist: raw
(bootloader) partition-type:mdm1hob: raw
(bootloader) partition-type:mdm1dhob: raw
(bootloader) partition-type:sp: raw
(bootloader) partition-type:cid: raw
(bootloader) partition-typeds: raw
(bootloader) partition-type:logo: raw
(bootloader) partition-type:clogo: raw
(bootloader) partition-type:misc: raw
(bootloader) partition-typeadC: raw
(bootloader) partition-type:mdm1m9kefs3: raw
(bootloader) partition-type:mdm1m9kefsc: raw
(bootloader) partition-type:ssd: raw
(bootloader) partition-type:kpan: raw
(bootloader) partition-type:boot: raw
(bootloader) partition-type:recovery: raw
(bootloader) partition-type:factorytune2: raw
(bootloader) partition-type:cache: raw
(bootloader) partition-type:system: raw
(bootloader) partition-type:userdata: raw
(bootloader) partition-size:modem: 0x0000000008000000
(bootloader) partition-size:sbl1: 0x0000000000060000
(bootloader) partition-size:sdi: 0x000000000000e000
(bootloader) partition-size:sec: 0x0000000000004000
(bootloader) partition-size:ddr: 0x0000000000008000
(bootloader) partition-size:aboot: 0x0000000000100000
(bootloader) partition-size:rpm: 0x0000000000040000
(bootloader) partition-size:utags: 0x0000000000080000
(bootloader) partition-size:tz: 0x000000000007d000
(bootloader) partition-size:factorytune1: 0x0000000000300000
(bootloader) partition-sizeadA: 0x000000000010f000
(bootloader) partition-size:sbl1bak: 0x0000000000060000
(bootloader) partition-size:abootBackup: 0x0000000000100000
(bootloader) partition-size:rpmBackup: 0x0000000000040000
(bootloader) partition-size:utagsBackup: 0x0000000000080000
(bootloader) partition-size:tzBackup: 0x000000000007d000
(bootloader) partition-size:mdm1m9kefs1: 0x0000000000100000
(bootloader) partition-size:mdm1m9kefs2: 0x0000000000100000
(bootloader) partition-sizeadB: 0x000000000020f000
(bootloader) partition-size:frp: 0x0000000000080000
(bootloader) partition-size:logs: 0x0000000000200000
(bootloader) partition-sizeersist: 0x0000000002000000
(bootloader) partition-size:mdm1hob: 0x0000000000040000
(bootloader) partition-size:mdm1dhob: 0x0000000000008000
(bootloader) partition-size:sp: 0x0000000000100000
(bootloader) partition-size:cid: 0x0000000000020000
(bootloader) partition-sizeds: 0x0000000000300000
(bootloader) partition-size:logo: 0x0000000000800000
(bootloader) partition-size:clogo: 0x0000000000b00000
(bootloader) partition-size:misc: 0x0000000000100000
(bootloader) partition-sizeadC: 0x0000000000198000
(bootloader) partition-size:mdm1m9kefs3: 0x00000000000c3000
(bootloader) partition-size:mdm1m9kefsc: 0x0000000000000400
(bootloader) partition-size:ssd: 0x0000000000002000
(bootloader) partition-size:kpan: 0x0000000000800000
(bootloader) partition-size:boot: 0x0000000001000000
(bootloader) partition-size:recovery: 0x0000000001004000
(bootloader) partition-size:factorytune2: 0x0000000001008000
(bootloader) partition-size:cache: 0x0000000059af4000
(bootloader) partition-size:system: 0x00000000d3000000
(bootloader) partition-size:userdata: 0x0000000608be0000
(bootloader) qe: qe 1/1
(bootloader) ro.carrier: vzw
all: listed above
finished. total time: 0.158s
I can boot fine into the bootloader, but that is all. Can't reboot into Recovery, and the ROM won't boot. Just boot loops constantly in the Moto Logo. I double checked all my connections and everything looks fine. I tried reflashing TWRP recovery (which said it worked) but that didn't help either.
Any ideas? Could leaving the motherboard unpowered for days have caused everything to be erased from ROM/RAM? If so, what do I do now? Am stumped, any ideas appreciated.
-Tom
Don't know about the pros, but I'd try flashing twrp via ADB while in bootloader. Once on, you can wipe stuff, and reflash your ROM from TWRP.
Sent from my XT1254 using Tapatalk
Einsteindks said:
Don't know about the pros, but I'd try flashing twrp via ADB while in bootloader. Once on, you can wipe stuff, and reflash your ROM from TWRP.
Click to expand...
Click to collapse
Thanks, but I did try that; adb said the flash worked, but it won't boot into recovery. Still bootloops at the logo.
OK I may post this question as a new post, but: To try to at least get a booting phone: Is there ANY stock ROM and Bootloader that I can flash that will still keep my phone UNLOCKED? I don't want to relock it and then have it locked forever (which I think the latest stock updates does),
SimpTheChimp said:
OK I may post this question as a new post, but: To try to at least get a booting phone: Is there ANY stock ROM and Bootloader that I can flash that will still keep my phone UNLOCKED? I don't want to relock it and then have it locked forever (which I think the latest stock updates does),
Click to expand...
Click to collapse
You can flash the latest firmware from Motorola and it won't lock your bootloader
I'll second that firmware flash. Bootloader doesn't get re-locked that way. Your TWRP file used may either have not been for quark phones, or was a corrupted file. I use version 3.1.0.0. Although the latest, and reported stable 'ver4' of that is out, 3.1.0.0 likes my Turbo.
Sent from my XT1254 using Tapatalk
I believe that if you can only get to the bootloader, you'd run fastboot commands not adb. Just want to make sure that's what you're doing.
Other than that, back up all the files you can get to through your PC and flash the stock image or run the Verizon repair assistant. Neither will relock your bootloader. You just get to start over from scratch, not necessarily a bad thing in situations like this.
Sent from my XT1254 using Tapatalk
SpyderPride said:
I believe that if you can only get to the bootloader, you'd run fastboot commands not adb. Just want to make sure that's what you're doing.
Other than that, back up all the files you can get to through your PC and flash the stock image or run the Verizon repair assistant. Neither will relock your bootloader. You just get to start over from scratch, not necessarily a bad thing in situations like this.
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
Spyder: Thanks, I did just that and it worked. Unfortunately, my new screen works but the digitizer doesn't. I.E. I can boot and see everything on the screen, but touching the screen yields nothing - can't scroll, can't select anything, can't even continue with the phone startup! I went through and double-checked all my connections and everything looks correct - just no digitizer.
Kinda strange that the screen works but the digitizer (touch portion) doesn't. Don't suppose you got any ideas on that?
You get the screen from a reputable seller? Did you do an all-in-one screen, or try to do an individual repair?
Sent from my XT1254 using Tapatalk
Einsteindks said:
You get the screen from a reputable seller? Did you do an all-in-one screen, or try to do an individual repair?
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
Yeah, the seller is an eBay 'company' but reputable (at least their rating is good); plus screen looked basically brand new when it arrived. It was screen+digitizer which I put on my old Turbo frame, reattached motherboard, battery, etc. Fairly experienced with taking the Turbo apart; have done so previously to install new battery.
Just strange that the screen works perfectly but no touch. I read somewhere else that sometimes pressing the top left corner of the screen (where it was mentioned that the digitizer exists) can possibly get it going - but not in my case. And as far as I can tell, there is only 1 connection of the screen to the motherboard, and I know that is connected properly.
So....
SimpTheChimp said:
Yeah, the seller is an eBay 'company' but reputable (at least their rating is good); plus screen looked basically brand new when it arrived. It was screen+digitizer which I put on my old Turbo frame, reattached motherboard, battery, etc. Fairly experienced with taking the Turbo apart; have done so previously to install new battery.
Just strange that the screen works perfectly but no touch. I read somewhere else that sometimes pressing the top left corner of the screen (where it was mentioned that the digitizer exists) can possibly get it going - but not in my case. And as far as I can tell, there is only 1 connection of the screen to the motherboard, and I know that is connected properly.
So....
Click to expand...
Click to collapse
Ribbon came not fully seated?
Sent from my DROID Turbo using Tapatalk
I have the same situation with my phone, is there any solution?
Related
I have searched for this and could only find one reference to this where a guy had this but then got flooded with people asking for him to dump the image so he freaked out cursing at everyone and than dissappeared. Am I only finding this one reference to this because this is just standard with a Nexus 6 or is it something to worry about? The comment was made on his post "I bet XDA would be interested in the image that you have on your device" leading me to believe he had something not standard. Ill post a getvar all here: I erased certain portions as im not sure which I need to not show.
I am also now seeing the "warranty void:yes" flag is tripped.... I literally just took it out of the box!
The sim card is in it and it is functioning normally.
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-apq8084-71.03
(bootloader) product: shamu
(bootloader) board: shamu
(bootloader) secure: yes
(bootloader) hwrev: 0x83A0
(bootloader) radio: 0x6
(bootloader) emmc: 32GB Sandisk REV=07 PRV=01 TYPE=57
(bootloader) ram: 3072MB Hynix S8 SDRAM DIE=6Gb
(bootloader) cpu:
(bootloader) serialno:
(bootloader) cid: 0x00DE
(bootloader) channelid: 0x00
(bootloader) uid:
(bootloader) unlocked: no
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 2
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 11-17-2014
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Nov 11 10:53:33 UTC 2014"
(bootloader) ro.build.fingerprint: none
(bootloader) ro.build.version.full: none
(bootloader) ro.build.version.qcom: none
(bootloader) version-baseband:
(bootloader) kernel.version: none
(bootloader) sdi.git: git=
(bootloader) sbl1.git: git=
(bootloader) rpm.git: git=
(bootloader) aboot.git: git=
(bootloader) partition-type:modem: raw
(bootloader) partition-type:metadata: raw
(bootloader) partition-type:sbl1: raw
(bootloader) partition-type:sdi: raw
(bootloader) partition-type:sec: raw
(bootloader) partition-type:ddr: raw
(bootloader) partition-type:aboot: raw
(bootloader) partition-type:rpm: raw
(bootloader) partition-type:utags: raw
(bootloader) partition-type:tz: raw
(bootloader) partition-typeadA: raw
(bootloader) partition-type:sbl1bak: raw
(bootloader) partition-type:abootBackup: raw
(bootloader) partition-type:rpmBackup: raw
(bootloader) partition-type:utagsBackup: raw
(bootloader) partition-type:tzBackup: raw
(bootloader) partition-type:versions: raw
(bootloader) partition-type:frp: raw
(bootloader) partition-type:mdm1m9kefs1: raw
(bootloader) partition-type:mdm1m9kefs2: raw
(bootloader) partition-type:mdm1m9kefs3: raw
(bootloader) partition-typeadB: raw
(bootloader) partition-type:sp: raw
(bootloader) partition-type:keystore: raw
(bootloader) partition-type:logs: raw
(bootloader) partition-typeersist: raw
(bootloader) partition-type:mdm1hob: raw
(bootloader) partition-type:mdm1dhob: raw
(bootloader) partition-type:cid: raw
(bootloader) partition-type:logo: raw
(bootloader) partition-type:misc: raw
(bootloader) partition-typeadD: raw
(bootloader) partition-type:mdm1m9kefsc: raw
(bootloader) partition-type:ssd: raw
(bootloader) partition-type:recovery: raw
(bootloader) partition-type:kpan: raw
(bootloader) partition-type:boot: raw
(bootloader) partition-type:cache: ext4
(bootloader) partition-typeem: raw
(bootloader) partition-typeadC: raw
(bootloader) partition-type:system: raw
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:modem: 0x0000000007000000
(bootloader) partition-size:metadata: 0x0000000001000000
(bootloader) partition-size:sbl1: 0x0000000000060000
(bootloader) partition-size:sdi: 0x000000000000e000
(bootloader) partition-size:sec: 0x0000000000004000
(bootloader) partition-size:ddr: 0x0000000000008000
(bootloader) partition-size:aboot: 0x0000000000100000
(bootloader) partition-size:rpm: 0x0000000000040000
(bootloader) partition-size:utags: 0x0000000000080000
(bootloader) partition-size:tz: 0x000000000007d000
(bootloader) partition-sizeadA: 0x000000000040f000
(bootloader) partition-size:sbl1bak: 0x0000000000060000
(bootloader) partition-size:abootBackup: 0x0000000000100000
(bootloader) partition-size:rpmBackup: 0x0000000000040000
(bootloader) partition-size:utagsBackup: 0x0000000000080000
(bootloader) partition-size:tzBackup: 0x000000000007d000
(bootloader) partition-size:versions: 0x0000000000001000
(bootloader) partition-size:frp: 0x0000000000080000
(bootloader) partition-size:mdm1m9kefs1: 0x0000000000100000
(bootloader) partition-size:mdm1m9kefs2: 0x0000000000100000
(bootloader) partition-size:mdm1m9kefs3: 0x0000000000100000
(bootloader) partition-sizeadB: 0x0000000000100000
(bootloader) partition-size:sp: 0x0000000001000000
(bootloader) partition-size:keystore: 0x0000000001000000
(bootloader) partition-size:logs: 0x0000000000200000
(bootloader) partition-sizeersist: 0x0000000002000000
(bootloader) partition-size:mdm1hob: 0x0000000000040000
(bootloader) partition-size:mdm1dhob: 0x0000000000008000
(bootloader) partition-size:cid: 0x0000000000020000
(bootloader) partition-size:logo: 0x0000000000800000
(bootloader) partition-size:misc: 0x0000000000100000
(bootloader) partition-sizeadD: 0x0000000000278000
(bootloader) partition-size:mdm1m9kefsc: 0x0000000000000400
(bootloader) partition-size:ssd: 0x0000000000002000
(bootloader) partition-size:recovery: 0x0000000001004000
(bootloader) partition-size:kpan: 0x00000000008e0000
(bootloader) partition-size:boot: 0x0000000001000000
(bootloader) partition-size:cache: 0x0000000010000000
(bootloader) partition-sizeem: 0x0000000004000000
(bootloader) partition-sizeadC: 0x0000000000100000
(bootloader) partition-size:system: 0x0000000080000000
(bootloader) partition-size:userdata: 0x00000006a13e0000
(bootloader) qe: qe 1/1
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.172s
AFAIK the bootloader will show Software status: modified when your bootloader is locked but the OS is rooted.
I can confirm my Nexus 6 also listed "modified" before even unlocking, although the warranty thing I didn't see/notice
Sent from my Nexus 6 using XDA Free mobile app
compuw22c said:
I can confirm my Nexus 6 also listed "modified" before even unlocking, although the warranty thing I didn't see/notice
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the info, can anyone confirm or bring some insight to the "(bootloader) iswarrantyvoid: yes" line?
Also, like I said I just turned the phone on first time a few hours ago and an update has already been downloaded and waiting for auth to install. Should I or should I not install this before unlocking and rooting? It just says system update android 5.0 and yes it is already running 5.0 ` Im guessing just a standard revision update?
bda714 said:
Thanks for the info, can anyone confirm or bring some insight to the "(bootloader) iswarrantyvoid: yes" line?
Also, like I said I just turned the phone on first time a few hours ago and an update has already been downloaded and waiting for auth to install. Should I or should I not install this before unlocking and rooting? It just says system update android 5.0 and yes it is already running 5.0 ` Im guessing just a standard revision update?
Click to expand...
Click to collapse
I would run all available updates before unlocking (less important) but more importantly in terms of TWRP and root, you'll save yourself an extra step or two if you update to current first then do those last 2 things. But yes just run the updates up to current.
thank you
compuw22c said:
I would run all available updates before unlocking (less important) but more importantly in terms of TWRP and root, you'll save yourself an extra step or two if you update to current first then do those last 2 things. But yes just run the updates up to current.
Click to expand...
Click to collapse
Thank you for the speedy reply, helps as I am right now trying to get this all figured out considering I am comiung from an HTC on verizon being the last device i messed with. First time had no problem and then got it replaced because of a cracked screen and when I got the new device I was never and still never able to unlock it. All because updating to 4.4
Anyways one more quick question if you know, where is the default location that the OTA is stored after downloading?
When I went to T-Mobile to buy my phone, I noticed that the recovery mode said "modified". Luckily I hadn't left the store, so they exchanged it for me.
That phone was defective for some reason and just wouldn't boot up. (waited for around 20 minutes)
bda714 said:
Thank you for the speedy reply, helps as I am right now trying to get this all figured out considering I am comiung from an HTC on verizon being the last device i messed with. First time had no problem and then got it replaced because of a cracked screen and when I got the new device I was never and still never able to unlock it. All because updating to 4.4
Anyways one more quick question if you know, where is the default location that the OTA is stored after downloading?
Click to expand...
Click to collapse
/cache I believe is where they're stored
I just received a Nexus 6 32GB that showed software modified out of the box and warrantyvoid was flagged yes.
It may be worth mentioning I got an RMA for my N5 with no questions asked regarding rooting or unlocking. Can't remember if I relocked it or not but at least if you bought it from the play store they seem VERY lenient on the subject.
Sent from my Nexus 6 using XDA Free mobile app
bda714 said:
I have searched for this and could only find one reference to this where a guy had this but then got flooded with people asking for him to dump the image so he freaked out cursing at everyone and than dissappeared. Am I only finding this one reference to this because this is just standard with a Nexus 6 or is it something to worry about? The comment was made on his post "I bet XDA would be interested in the image that you have on your device" leading me to believe he had something not standard. Ill post a getvar all here: I erased certain portions as im not sure which I need to not show.
I am also now seeing the "warranty void:yes" flag is tripped.... I literally just took it out of the box!
The sim card is in it and it is functioning normally.
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-apq8084-71.03
(bootloader) product: shamu
(bootloader) board: shamu
(bootloader) secure: yes
(bootloader) hwrev: 0x83A0
(bootloader) radio: 0x6
(bootloader) emmc: 32GB Sandisk REV=07 PRV=01 TYPE=57
(bootloader) ram: 3072MB Hynix S8 SDRAM DIE=6Gb
(bootloader) cpu:
(bootloader) serialno:
(bootloader) cid: 0x00DE
(bootloader) channelid: 0x00
(bootloader) uid:
(bootloader) unlocked: no
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 2
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 11-17-2014
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Nov 11 10:53:33 UTC 2014"
(bootloader) ro.build.fingerprint: none
(bootloader) ro.build.version.full: none
(bootloader) ro.build.version.qcom: none
(bootloader) version-baseband:
(bootloader) kernel.version: none
(bootloader) sdi.git: git=
(bootloader) sbl1.git: git=
(bootloader) rpm.git: git=
(bootloader) aboot.git: git=
(bootloader) partition-type:modem: raw
(bootloader) partition-type:metadata: raw
(bootloader) partition-type:sbl1: raw
(bootloader) partition-type:sdi: raw
(bootloader) partition-type:sec: raw
(bootloader) partition-type:ddr: raw
(bootloader) partition-type:aboot: raw
(bootloader) partition-type:rpm: raw
(bootloader) partition-type:utags: raw
(bootloader) partition-type:tz: raw
(bootloader) partition-typeadA: raw
(bootloader) partition-type:sbl1bak: raw
(bootloader) partition-type:abootBackup: raw
(bootloader) partition-type:rpmBackup: raw
(bootloader) partition-type:utagsBackup: raw
(bootloader) partition-type:tzBackup: raw
(bootloader) partition-type:versions: raw
(bootloader) partition-type:frp: raw
(bootloader) partition-type:mdm1m9kefs1: raw
(bootloader) partition-type:mdm1m9kefs2: raw
(bootloader) partition-type:mdm1m9kefs3: raw
(bootloader) partition-typeadB: raw
(bootloader) partition-type:sp: raw
(bootloader) partition-type:keystore: raw
(bootloader) partition-type:logs: raw
(bootloader) partition-typeersist: raw
(bootloader) partition-type:mdm1hob: raw
(bootloader) partition-type:mdm1dhob: raw
(bootloader) partition-type:cid: raw
(bootloader) partition-type:logo: raw
(bootloader) partition-type:misc: raw
(bootloader) partition-typeadD: raw
(bootloader) partition-type:mdm1m9kefsc: raw
(bootloader) partition-type:ssd: raw
(bootloader) partition-type:recovery: raw
(bootloader) partition-type:kpan: raw
(bootloader) partition-type:boot: raw
(bootloader) partition-type:cache: ext4
(bootloader) partition-typeem: raw
(bootloader) partition-typeadC: raw
(bootloader) partition-type:system: raw
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:modem: 0x0000000007000000
(bootloader) partition-size:metadata: 0x0000000001000000
(bootloader) partition-size:sbl1: 0x0000000000060000
(bootloader) partition-size:sdi: 0x000000000000e000
(bootloader) partition-size:sec: 0x0000000000004000
(bootloader) partition-size:ddr: 0x0000000000008000
(bootloader) partition-size:aboot: 0x0000000000100000
(bootloader) partition-size:rpm: 0x0000000000040000
(bootloader) partition-size:utags: 0x0000000000080000
(bootloader) partition-size:tz: 0x000000000007d000
(bootloader) partition-sizeadA: 0x000000000040f000
(bootloader) partition-size:sbl1bak: 0x0000000000060000
(bootloader) partition-size:abootBackup: 0x0000000000100000
(bootloader) partition-size:rpmBackup: 0x0000000000040000
(bootloader) partition-size:utagsBackup: 0x0000000000080000
(bootloader) partition-size:tzBackup: 0x000000000007d000
(bootloader) partition-size:versions: 0x0000000000001000
(bootloader) partition-size:frp: 0x0000000000080000
(bootloader) partition-size:mdm1m9kefs1: 0x0000000000100000
(bootloader) partition-size:mdm1m9kefs2: 0x0000000000100000
(bootloader) partition-size:mdm1m9kefs3: 0x0000000000100000
(bootloader) partition-sizeadB: 0x0000000000100000
(bootloader) partition-size:sp: 0x0000000001000000
(bootloader) partition-size:keystore: 0x0000000001000000
(bootloader) partition-size:logs: 0x0000000000200000
(bootloader) partition-sizeersist: 0x0000000002000000
(bootloader) partition-size:mdm1hob: 0x0000000000040000
(bootloader) partition-size:mdm1dhob: 0x0000000000008000
(bootloader) partition-size:cid: 0x0000000000020000
(bootloader) partition-size:logo: 0x0000000000800000
(bootloader) partition-size:misc: 0x0000000000100000
(bootloader) partition-sizeadD: 0x0000000000278000
(bootloader) partition-size:mdm1m9kefsc: 0x0000000000000400
(bootloader) partition-size:ssd: 0x0000000000002000
(bootloader) partition-size:recovery: 0x0000000001004000
(bootloader) partition-size:kpan: 0x00000000008e0000
(bootloader) partition-size:boot: 0x0000000001000000
(bootloader) partition-size:cache: 0x0000000010000000
(bootloader) partition-sizeem: 0x0000000004000000
(bootloader) partition-sizeadC: 0x0000000000100000
(bootloader) partition-size:system: 0x0000000080000000
(bootloader) partition-size:userdata: 0x00000006a13e0000
(bootloader) qe: qe 1/1
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.172s
Click to expand...
Click to collapse
I'm sorry if you're problem has already been fixed, but I just received a brand new White 64GB Nexus 6 from the Google Play Store, got it all set up with Sprint and noticed this Software status: modified message. That's actually what led me here. I found that it only shows that with the default bootloader that the phone ships with. I flashed the latest LMY47I bootloader and firmware, and the message goes away along with the iswarrantyvoid message. Everything is good if you just update through the Android SDK and fastboot tools.
My turbo1254 is now in Qualcomm HS-USB QDLoader 9008 mode.
Here is the story:
1. I did OTA Update from 4.4 to 5.1
2. Pressed reboot, black screen and.... nothing happend. My Nexus doesn't start at all.
I can't boot into Recovery or Download Mode.
I'm unlocked.
Can anybody help me?
My turbo1254 is now in Qualcomm HS-USB QDLoader 9008 mode.
Click to expand...
Click to collapse
Do you have any way of taking a picture of what you're seeing in this mode? I've never heard of anyone getting into it before.
1. I did OTA Update from 4.4 to 5.1
Click to expand...
Click to collapse
Were you rooted with Moforoot on 4.4?
2. Pressed reboot, black screen and.... nothing happend. My Nexus doesn't start at all.
Click to expand...
Click to collapse
Uhm... Nexus? please tell me you just typed the wrong device and didn't try flashing images for one device on another...
I'm unlocked.
Click to expand...
Click to collapse
Unlocked as in carrier or bootloader?
immadeofpixels27 said:
Do you have any way of taking a picture of what you're seeing in this mode? I've never heard of anyone getting into it before.
Were you rooted with Moforoot on 4.4?
Uhm... Nexus? please tell me you just typed the wrong device and didn't try flashing images for one device on another...
Unlocked as in carrier or bootloader?
Click to expand...
Click to collapse
I have the same case with the post starter
and this case look like that post
http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057
and now i want to use the Qualcomm QPST tools or other way to fix bootloader programs.
now i can find the port called Qualcomm HS-USB QDLoader 9008 (COM(The com port number which will vary but its important to know)) in Device Manager ，and i can find the phone In Qpst it is detected as Phone in Download Mode and in QPST Configuration as Sahara Memory Dump (Connected Phone: Q/QCP-XXX). but i have not the hex files and the mbn files for the APQ8084 processor to fix it in qpst emmc software download mode or Flashing the BLANK BOOTLOADER like the moto-x fix post http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057
Look in the development threads,there is a unbrick tool that will reflash the bootloader.Just pick which version you were on,KitKat or lollipop and follow the directions in the post.It works,used it myself a few times
kinglove1211 said:
Look in the development threads,there is a unbrick tool that will reflash the bootloader.Just pick which version you were on,KitKat or lollipop and follow the directions in the post.It works,used it myself a few times
Click to expand...
Click to collapse
at last time i flash the rom i use the command fastboot getvar all get a Snapshot like this
F:\BaiduYunDownload\RE+\Windows>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-apq8084-70.86
(bootloader) product: quark
(bootloader) board: quark
(bootloader) secure: yes
(bootloader) hwrev: 0x84A0
(bootloader) radio: 0x4
(bootloader) emmc: 32GB Samsung REV=07 PRV=0B TYPE=57
(bootloader) ram: 3072MB Hynix S8 SDRAM DIE=6Gb
(bootloader) cpu: APQ8084 ES1.1
(bootloader) serialno: ZX1F22P9MM
(bootloader) cid: 0x0002
(bootloader) channelid: 0x00
(bootloader) uid: 11620B01110000000000001111111
(bootloader) unlocked: yes
(bootloader) securestate: unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 990005113544333
(bootloader) meid:
(bootloader) date: 12-08-2014
(bootloader) sku: XT1254
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Sep 2 4: 5:50 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/quark_verizon/quark:5
(bootloader) ro.build.fingerprint[1]: U4TL-44/44:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.23.21.44.quark_v
(bootloader) ro.build.version.full[1]: on.verizon.en.US
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.10.40-perf-g90ddf4a
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (G
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Tue Sep 1 22:50:23
(bootloader) kernel.version[3]: 2015
(bootloader) sdi.git: git=MBM-NG-V70.86-0-gf291c61
(bootloader) sbl1.git: git=MBM-NG-V70.86-0-g60ea7e6
(bootloader) rpm.git: git=MBM-NG-V70.86-0-g18b261e
(bootloader) tz.git: git=MBM-NG-V70.86-0-g51b120f
(bootloader) aboot.git: git=MBM-NG-V70.86-0-g88bfdfd
(bootloader) partition-type:modem: raw
(bootloader) partition-type:sbl1: raw
(bootloader) partition-type:sdi: raw
(bootloader) partition-type:sec: raw
(bootloader) partition-type:ddr: raw
(bootloader) partition-type:aboot: raw
(bootloader) partition-type:rpm: raw
(bootloader) partition-type:utags: raw
(bootloader) partition-type:tz: raw
(bootloader) partition-type:factorytune1: raw
(bootloader) partition-typeadA: raw
(bootloader) partition-type:sbl1bak: raw
(bootloader) partition-type:abootBackup: raw
(bootloader) partition-type:rpmBackup: raw
(bootloader) partition-type:utagsBackup: raw
(bootloader) partition-type:tzBackup: raw
(bootloader) partition-type:mdm1m9kefs1: raw
(bootloader) partition-type:mdm1m9kefs2: raw
(bootloader) partition-typeadB: raw
(bootloader) partition-type:frp: raw
(bootloader) partition-type:logs: raw
(bootloader) partition-typeersist: raw
(bootloader) partition-type:mdm1hob: raw
(bootloader) partition-type:mdm1dhob: raw
(bootloader) partition-type:sp: raw
(bootloader) partition-type:cid: raw
(bootloader) partition-typeds: raw
(bootloader) partition-type:logo: raw
(bootloader) partition-type:clogo: raw
(bootloader) partition-type:misc: raw
(bootloader) partition-typeadC: raw
(bootloader) partition-type:mdm1m9kefs3: raw
(bootloader) partition-type:mdm1m9kefsc: raw
(bootloader) partition-type:ssd: raw
(bootloader) partition-type:kpan: raw
(bootloader) partition-type:boot: raw
(bootloader) partition-type:recovery: raw
(bootloader) partition-type:factorytune2: raw
(bootloader) partition-type:cache: raw
(bootloader) partition-type:system: raw
(bootloader) partition-type:userdata: raw
(bootloader) partition-size:modem: 0x0000000008000000
(bootloader) partition-size:sbl1: 0x0000000000060000
(bootloader) partition-size:sdi: 0x000000000000e000
(bootloader) partition-size:sec: 0x0000000000004000
(bootloader) partition-size:ddr: 0x0000000000008000
(bootloader) partition-size:aboot: 0x0000000000100000
(bootloader) partition-size:rpm: 0x0000000000040000
(bootloader) partition-size:utags: 0x0000000000080000
(bootloader) partition-size:tz: 0x000000000007d000
(bootloader) partition-size:factorytune1: 0x0000000000300000
(bootloader) partition-sizeadA: 0x000000000010f000
(bootloader) partition-size:sbl1bak: 0x0000000000060000
(bootloader) partition-size:abootBackup: 0x0000000000100000
(bootloader) partition-size:rpmBackup: 0x0000000000040000
(bootloader) partition-size:utagsBackup: 0x0000000000080000
(bootloader) partition-size:tzBackup: 0x000000000007d000
(bootloader) partition-size:mdm1m9kefs1: 0x0000000000100000
(bootloader) partition-size:mdm1m9kefs2: 0x0000000000100000
(bootloader) partition-sizeadB: 0x000000000020f000
(bootloader) partition-size:frp: 0x0000000000080000
(bootloader) partition-size:logs: 0x0000000000200000
(bootloader) partition-sizeersist: 0x0000000002000000
(bootloader) partition-size:mdm1hob: 0x0000000000040000
(bootloader) partition-size:mdm1dhob: 0x0000000000008000
(bootloader) partition-size:sp: 0x0000000000100000
(bootloader) partition-size:cid: 0x0000000000020000
(bootloader) partition-sizeds: 0x0000000000300000
(bootloader) partition-size:logo: 0x0000000000800000
(bootloader) partition-size:clogo: 0x0000000000b00000
(bootloader) partition-size:misc: 0x0000000000100000
(bootloader) partition-sizeadC: 0x0000000000198000
(bootloader) partition-size:mdm1m9kefs3: 0x00000000000c3000
(bootloader) partition-size:mdm1m9kefsc: 0x0000000000000400
(bootloader) partition-size:ssd: 0x0000000000002000
(bootloader) partition-size:kpan: 0x0000000000800000
(bootloader) partition-size:boot: 0x0000000001000000
(bootloader) partition-size:recovery: 0x0000000001004000
(bootloader) partition-size:factorytune2: 0x0000000001008000
(bootloader) partition-size:cache: 0x0000000059af4000
(bootloader) partition-size:system: 0x00000000d3000000
(bootloader) partition-size:userdata: 0x0000000608be0000
(bootloader) qe: qe 1/1
(bootloader) ro.carrier: vzw
all: listed above
finished. total time: 0.166s
Click to expand...
Click to collapse
and i try the fix hard brick / qhsub_bulk after bad flash / cm12 flash from 5.1
http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
the blank-flash.bat is working for nexus6
but in my phone the flash is pass and reboot
but the phone does not start to fastboot.
i think the singleimage.bin programmer.mbn version is not for XT1254
and i need to help.
yunfeitao said:
My turbo1254 is now in Qualcomm HS-USB QDLoader 9008 mode.
Can anybody help me?
Click to expand...
Click to collapse
http://forum.xda-developers.com/droid-turbo/general/turbo-unbrick-t3139811
ilia3367 said:
http://forum.xda-developers.com/droid-turbo/general/turbo-unbrick-t3139811
Click to expand...
Click to collapse
Thank you for the great contribution, i have the start to bl mode with your tools.
but failed to flash gpt.bin
i think i would be try the moto RSD Lite?
or because the phone is locked by flash unbrick tools？
it's after the phone reboot in bl mode snapshot
D:\boot\Turbo>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.004s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.091s
D:\boot\Turbo>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.004s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.071s
D:\boot\Turbo>fastboot flash radio radio.img
error: cannot open 'radio.img'
D:\boot\Turbo>fastboot flash radio radio.img
target reported max download size of 536870912 bytes
sending 'radio' (86165 KB)...
OKAY [ 2.742s]
writing 'radio'...
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 2.748s
D:\boot\Turbo>fastboot flash bootloader bootloader.img
error: cannot open 'bootloader.img'
D:\boot\Turbo>fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (2163 KB)...
OKAY [ 0.072s]
writing 'bootloader'...
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.077s
D:\boot\Turbo>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-apq8084-70.86(*)
(bootloader) product: quark
(bootloader) board: quark
(bootloader) secure: yes
(bootloader) hwrev: 0x84A0
(bootloader) radio: 0x4
(bootloader) emmc: 32GB Samsung REV=07 PRV=0B TYPE=57
(bootloader) ram: 3072MB Hynix S8 SDRAM DIE=6Gb
(bootloader) cpu: APQ8084 ES1.1
(bootloader) serialno: 3925b8b8
(bootloader) cid: 0xFFFF
(bootloader) channelid: 0xDEAD
(bootloader) uid: 11620B0111000000000000000000
(bootloader) unlocked: Not supported
(bootloader) securestate: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) mot_sst: 8
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sdi.git: sdi.git
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) aboot.git: git=MBM-NG-V70.86-0-g88bfdfd
(bootloader) qe:
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.043s
D:\boot\Turbo>
Click to expand...
Click to collapse
very thanks for @ilia3367
---------- Post added at 11:16 AM ---------- Previous post was at 10:44 AM ----------
i try the moto rsd lite tools to flash the rom VRZ_XT1254_SU4TL-44_44_CFC twice
first fails to flash boot.img.
but second that's all pass
The phone was saved.
Thank all the people!
hello please help me i have phone xt1254 but not worked i need flash my phone with fastboot but the problem my bootloader is locked
please this my informations about my phone . i can flash my phone without unlock bootloader?
...
(bootloader) 9900062352232020#5A583146323258
(bootloader) 5A563800585431323534000000#6D68
(bootloader) 96C83C0C4B4DE0E6B3DA2981554B9CA
(bootloader) B181E#0C58AE0011000000000000000
(bootloader) 0000000
OKAY [ 0.214s]
finished. total time: 0.215s
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-apq8084-70.8A
(bootloader) product: quark
(bootloader) board: quark
(bootloader) secure: yes
(bootloader) hwrev: 0x84A0
(bootloader) radio: 0x4
(bootloader) emmc: 32GB Sandisk REV=07 PRV=01 TYPE=57
(bootloader) ram: 3072MB Samsung S8 SDRAM DIE=6Gb
(bootloader) cpu: APQ8084 ES1.1
(bootloader) serialno: ZX1F22XZV8
(bootloader) cid: 0x0002
(bootloader) channelid: 0x00
(bootloader) uid: 0C58AE0011000000000000000000
(bootloader) unlocked: no
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 04-13-2016
(bootloader) sku: XT1254
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Nov 3 21:12:37 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/quark_verizon/quark:6.0.1
(bootloader) ro.build.fingerprint[1]: /MCG24.251-5/9:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.81.5.quark_verizo
(bootloader) ro.build.version.full[1]: n.verizon.en.US
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband: MDM9625_104651.11.05.16.03R QUARK_CUST
(bootloader) kernel.version[0]: Linux version 3.10.40-perf-gcd46769 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (GCC)
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Thu Nov 3 16:34:02 CDT
(bootloader) kernel.version[3]: 2016
(bootloader) sdi.git: git=MBM-NG-V70.8A-0-gf291c61
(bootloader) sbl1.git: git=MBM-NG-V70.8A-0-g60ea7e6
(bootloader) rpm.git: git=MBM-NG-V70.8A-0-g18b261e
(bootloader) tz.git: git=MBM-NG-V70.8A-0-gce6d7d0
(bootloader) aboot.git: git=MBM-NG-V70.8A-0-g021bfc8
(bootloader) partition-type:modem: raw
(bootloader) partition-type:sbl1: raw
(bootloader) partition-type:sdi: raw
(bootloader) partition-type:sec: raw
(bootloader) partition-type:ddr: raw
(bootloader) partition-type:aboot: raw
(bootloader) partition-type:rpm: raw
(bootloader) partition-type:utags: raw
(bootloader) partition-type:tz: raw
(bootloader) partition-type:factorytune1: raw
(bootloader) partition-typeadA: raw
(bootloader) partition-type:sbl1bak: raw
(bootloader) partition-type:abootBackup: raw
(bootloader) partition-type:rpmBackup: raw
(bootloader) partition-type:utagsBackup: raw
(bootloader) partition-type:tzBackup: raw
(bootloader) partition-type:mdm1m9kefs1: raw
(bootloader) partition-type:mdm1m9kefs2: raw
(bootloader) partition-typeadB: raw
(bootloader) partition-type:frp: raw
(bootloader) partition-type:logs: raw
(bootloader) partition-typeersist: raw
(bootloader) partition-type:mdm1hob: raw
(bootloader) partition-type:mdm1dhob: raw
(bootloader) partition-type:sp: raw
(bootloader) partition-type:cid: raw
(bootloader) partition-typeds: raw
(bootloader) partition-type:logo: raw
(bootloader) partition-type:clogo: raw
(bootloader) partition-type:misc: raw
(bootloader) partition-typeadC: raw
(bootloader) partition-type:mdm1m9kefs3: raw
(bootloader) partition-type:mdm1m9kefsc: raw
(bootloader) partition-type:ssd: raw
(bootloader) partition-type:kpan: raw
(bootloader) partition-type:boot: raw
(bootloader) partition-type:recovery: raw
(bootloader) partition-type:factorytune2: raw
(bootloader) partition-type:cache: raw
(bootloader) partition-type:system: raw
(bootloader) partition-type:userdata: raw
(bootloader) partition-size:modem: 0x0000000008000000
(bootloader) partition-size:sbl1: 0x0000000000060000
(bootloader) partition-size:sdi: 0x000000000000e000
(bootloader) partition-size:sec: 0x0000000000004000
(bootloader) partition-size:ddr: 0x0000000000008000
(bootloader) partition-size:aboot: 0x0000000000100000
(bootloader) partition-size:rpm: 0x0000000000040000
(bootloader) partition-size:utags: 0x0000000000080000
(bootloader) partition-size:tz: 0x000000000007d000
(bootloader) partition-size:factorytune1: 0x0000000000300000
(bootloader) partition-sizeadA: 0x000000000010f000
(bootloader) partition-size:sbl1bak: 0x0000000000060000
(bootloader) partition-size:abootBackup: 0x0000000000100000
(bootloader) partition-size:rpmBackup: 0x0000000000040000
(bootloader) partition-size:utagsBackup: 0x0000000000080000
(bootloader) partition-size:tzBackup: 0x000000000007d000
(bootloader) partition-size:mdm1m9kefs1: 0x0000000000100000
(bootloader) partition-size:mdm1m9kefs2: 0x0000000000100000
(bootloader) partition-sizeadB: 0x000000000020f000
(bootloader) partition-size:frp: 0x0000000000080000
(bootloader) partition-size:logs: 0x0000000000200000
(bootloader) partition-sizeersist: 0x0000000002000000
(bootloader) partition-size:mdm1hob: 0x0000000000040000
(bootloader) partition-size:mdm1dhob: 0x0000000000008000
(bootloader) partition-size:sp: 0x0000000000100000
(bootloader) partition-size:cid: 0x0000000000020000
(bootloader) partition-sizeds: 0x0000000000300000
(bootloader) partition-size:logo: 0x0000000000800000
(bootloader) partition-size:clogo: 0x0000000000b00000
(bootloader) partition-size:misc: 0x0000000000100000
(bootloader) partition-sizeadC: 0x0000000000198000
(bootloader) partition-size:mdm1m9kefs3: 0x00000000000c3000
(bootloader) partition-size:mdm1m9kefsc: 0x0000000000000400
(bootloader) partition-size:ssd: 0x0000000000002000
(bootloader) partition-size:kpan: 0x0000000000800000
(bootloader) partition-size:boot: 0x0000000001000000
(bootloader) partition-size:recovery: 0x0000000001004000
(bootloader) partition-size:factorytune2: 0x0000000001008000
(bootloader) partition-size:cache: 0x0000000059af4000
(bootloader) partition-size:system: 0x00000000d3000000
(bootloader) partition-size:userdata: 0x0000000608be0000
(bootloader) qe: qe 0/0
(bootloader) ro.carrier: vzw
all: listed above
finished. total time: 0.837s
Can you give a little more info? What happened? How did you bricked?
Your imei is still present in your post.
Full firmware is not available, yet. When it is; it will be posted on the forum.
BBB
Think Spoon
Sent from my XT1254 using Tapatalk
yes imei still in my phone
i want to flash my phone but this flash is wrong
now my phone totaly bricked only i have access to fastboot
hamza_iraki said:
yes imei still in my phone
i want to flash my phone but this flash is wrong
now my phone totaly bricked only i have access to fastboot
Click to expand...
Click to collapse
And you still didn't type what you did that bricked your phone. If you want somebody to help you, give more info.
first i buy this phone locked with google account access and after i try to flash my phone with other firmware with fastboot mode
now my phone is bricked i can only enter to recovery and fastboot
please samone give me rom for adb flash i need original firmware
hamza_iraki said:
first i buy this phone locked with google account access and after i try to flash my phone with other firmware with fastboot mode
now my phone is bricked i can only enter to recovery and fastboot
please samone give me rom for adb flash i need original firmware
Click to expand...
Click to collapse
On which firmware was phone? If it's Marshmallow, you can't downgrade, and official marshmallow files for flashing are not released (yet).
I have latest version 24.81.5 6.0.1
I need official rom 24.81.5 with adb or fastboot
hamza_iraki said:
I have latest version 24.81.5 6.0.1
I need official rom 24.81.5 with adb or fastboot
Click to expand...
Click to collapse
It's not released yet. I'm making one right now , but it's not easy , can't promisse anything. Righ now I'm stuck at flashing system.img due to files not signed properly. Help from more experienced would be great, but feel that droid turbo section is dead and nobody is interested about that phone anymore lol.
Thank you sir im waiting you release latest firmware for locked bootloader
hamza_iraki said:
I have latest version 24.81.5 6.0.1
I need official rom 24.81.5 with adb or fastboot
Click to expand...
Click to collapse
[FXZ] Official Stock Firmware 6.0.1 MCG24.251-5
https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3531571
thank you now my phone work thank you foor all
help with failed to validate system image
EjđiSixo said:
It's not released yet. I'm making one right now , but it's not easy , can't promisse anything. Righ now I'm stuck at flashing system.img due to files not signed properly. Help from more experienced would be great, but feel that droid turbo section is dead and nobody is interested about that phone anymore lol.
Click to expand...
Click to collapse
Hi hi, I am desparate to get my phone working so I can send it back to Verizon.
Here's the history.
I unlocked my bootloader. Verizon pushed the marshmallow update. No problems at all. I relocked my bootloader with fastboost. Now I get failed to validate system image.
Now that the phone is locked, what can I do?
droidfun1 said:
Hi hi, I am desparate to get my phone working so I can send it back to Verizon.
Here's the history.
I unlocked my bootloader. Verizon pushed the marshmallow update. No problems at all. I relocked my bootloader with fastboost. Now I get failed to validate system image.
Now that the phone is locked, what can I do?
Click to expand...
Click to collapse
The answer is right here on this page and you ignored it to post your question yet again in multiple threads. READ!
Nexus 6
Não existe salvador pra isso... ao menos que a motorola libere o bootloader dele:good:
Anailson said:
Não existe salvador pra isso... ao menos que a motorola libere o bootloader dele:good:
Click to expand...
Click to collapse
There is no savior for this ... unless the motorola releases its bootloader
Click to expand...
Click to collapse
Why do you say that? Droid Turbo bootloader can be unlocked with Sunshine app, since November 2015.
[GUIDE] How to unlock your bootloader, install TWRP and gain root access
https://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
How do you think we have all these ROMS for the Droid Turbo?
Verizon (big important U.S. carrier) won't let Motorola give free bootloader unlock like all the other Quarks (Moto Maxx XT1250, Moto Maxx XT1225, Moto Turbo XT1225). Moto Maxx XT1250 = Droid Turbo XT1254, but with free bootloader unlock code from Motorola. SAME exact phone.
But Sunshine devs found an exploit that can do it.
Oh, and post in English, please. XDA rules.
Hello, I have a moto g 2014 xt1063 , from a friend who gave it to me to repair it (which left me with no more remedies to consult, since I read everywhere and still, I do not find any solution)
The phone gave me already in fastboot mode, with different errors to enter the recovery (boot up) and no way to install a stock, since in all I get "FAILED (remote failure)"
In the roms that I have tried (the ones that are supposed to be stocks for this type of phone). The skinny to know nothing android, I did not know in which stock version was (if 4.4.4 or 5.0.2) I put a fastboot getvar all and I throw this:
(bootloader) version: 0.5
(bootloader) version-bootloader: 4807(*)
(bootloader) product: titan
(bootloader) secure: yes
(bootloader) hwrev: 0x8400
(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: ZX1D726FMS
(bootloader) cid: 0x000C
(bootloader) channelid: 0x05
(bootloader) uid: B6331F080F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Fall-through from recovery boot mode
(bootloader) imei: 353332060924115
(bootloader) meid:
(bootloader) date: 06-20-2015
(bootloader) sku: XT1063
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Jun 27 12:40:47 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/titan_retla/titan_umts:4.
(bootloader) ro.build.fingerprint[1]: 4.4/KXB21.85-23/30:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) ro.build.version.full[0]: Blur_Version.21.11.23.titan_retla
(bootloader) ro.build.version.full[1]: .retla.en.01
(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.045
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-g668a77b ([email protected]
(bootloader) kernel.version[1]: ilclbld31) (gcc version 4.7 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Tue Aug 26 20:03:02 CDT 2014
(bootloader) sdi.git: git=MBM-NG-V48.07-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V48.07-0-g683cb0c
(bootloader) rpm.git: git=MBM-NG-V48.07-0-g71b1aae-dirty
(bootloader) tz.git: git=MBM-NG-V48.07-0-ga27c415
(bootloader) aboot.git: git=MBM-NG-V48.07-0-ge875a20
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 0/0
(bootloader) productid: ZX1D726FMS
(bootloader) sutinfo:
all: listed above
finished. total time: 0.062s
I assumed by what I said that it was a 4.4.4 download from here, the stock firmware, however as I said above the blessed error in the fastboot FAILED (remote failure)
In each command set, the bootloader is unlocked. I already probe with fastboot oem fb_mode_clear, and other things reviewed in xda. I do not know what else to do ... Any solutions? (Clarify the bootloader also throws me the error (bootloader) Failed to flash partition recovery, but by reading does not matter said error)
Now at the moment, after several attempts, I get this "fastboot reason: failure-through from boot boot mode" error.
Try to put a TWRP recovery for titan (do not try some cyanogen), since the errors when flashing the recovery are the same that always throw me.
If you need more information, let me know.
Sorry for my horrible English. I speak Spanish, by the doubts.
From already thank you very much!
I am stuck in the AP Fastboot Flash Mode (S). Recovery, Factory, BP Tools doesn't function, giving the same line "failed to validate xxx image". I can't flash stock ROMs through fastboot commands, all of those were "Failed". The bootloader lock can't even be unlocked, same reason above. Anybody from XDA can help me with this? I desperately tried almost everything on the forum and nothing has progressed so far. Here is the getvar-all information of my device:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 4887
(bootloader) product: titan
(bootloader) secure: yes
(bootloader) hwrev: 0x8400
(bootloader) radio: 0x1
(bootloader) emmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Elpida S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: ZX1D325JTJ
(bootloader) cid: 0x0009
(bootloader) channelid: 0x8d
(bootloader) uid: AAED95070F000000000000000000
(bootloader) unlocked: no
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 359297055872880
(bootloader) meid:
(bootloader) date: 01-21-2015
(bootloader) sku: XT1063
(bootloader) battid: (null)
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Nov 1 4:11:27 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/titan_retuglb/titan_umts:
(bootloader) ro.build.fingerprint[1]: 6.0/MPBS24.65-34-4/6:user/release-
(bootloader) ro.build.fingerprint[2]: keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.201.4.titan_retug
(bootloader) ro.build.version.full[1]: lb.retuglb.en.US
(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.045
(bootloader) version-baseband[0]: MSM8626BP_1032.3116.99.00R RETUSA_GLB_
(bootloader) version-baseband[1]: CUST
(bootloader) kernel.version[0]: Linux version 3.4.42-g495dfd8 ([email protected]
(bootloader) kernel.version[1]: ilclbld36) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Wed Aug 24 07:20:10 CDT 2016
(bootloader) sdi.git: sdi.git
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) aboot.git: git=MBM-NG-V48.87-0-g1b80345
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe:
(bootloader) productid:
(bootloader) sutinfo:
(bootloader) ro.carrier: retus
all: listed above
finished. total time: 34.876s
I would really appreciate if somebody can solve this problem for me.
Hi! Sorry if im late, but did you use a 1 click flash tool? I reflashed 5.0.2 on my 1063 but i used a 6.0 flash tool and i got the same error! It got corrected once i used the correct flash tool
Angel064able said:
Hi! Sorry if im late, but did you use a 1 click flash tool? I reflashed 5.0.2 on my 1063 but i used a 6.0 flash tool and i got the same error! It got corrected once i used the correct flash tool
Click to expand...
Click to collapse
I used mfastboot and manually entered the codes. Where can I get that flashtool?
imnewbieplsnokick said:
I used mfastboot and manually entered the codes. Where can I get that flashtool?
Click to expand...
Click to collapse
I used this video:youtu.be/Jav4tIv5sCI
Credit to the creator.
Did you downgraded the ROM of your device? The one which comes out of the box? The chances are this happens when you flash downgraded Stock flash files on upgraded bootloader. Try flashing latest factory image available for your device and firstly re flash partition, boot, recovery and bootloader files. Then go for all other flash files serially. This solution 'might' help. Otherwise there's nothing you can do.
imnewbieplsnokick said:
I used mfastboot and manually entered the codes. Where can I get that flashtool?
Click to expand...
Click to collapse
Did you solved your issue? My device went to the same state while I was trying to relock the bootloader and re-unlocking it fixed it!
Angel064able said:
Did you solved your issue? My device went to the same state while I was trying to relock the bootloader and re-unlocking it fixed it!
Click to expand...
Click to collapse
Sorry, I was quite busy with my mid-semester. I tried it out and it didn't work. I guess it is dead now. However, I am thinking about breaking the phone, turning it into a hard-brick state and then reincarnate it back to life. Is it possible?