[Q] As resurrect a bricked xt1097? - Moto X Q&A

Hi guys, i have a Motorola Moto X 2014 (2gen) XT1097 , in a update from android 5.1 my android don't completed the update and don't power, and don't fastboot more ...
I've tried making the ways forum here however I get the following error:
C:\motox\blankflash>qflash.exe -com5 -ramload MPRG8960.hex -mbn 33 MSM8960_boot
oader_singleimage.bin -v -o
Motorola qflash Utility version 1.3
COMPORT :COM5
RAMLOADER :MPRG8960.hex
type is 0x21
7 mbn file name MSM8960_bootloader_singleimage.bin type 33
verbose mode on
Motorola qflash dll version 1.6
warning: read size exceeded expected expected length, possible command failure
data received: 0x01000000300000000200000001000000000400000000000000000000000000
00000000000000000000000000000000004000000100000000d0000000100000004000000100000
00d00000001000000
dmss_software_version_req: received invalid or no response
Failed to send software version request
Click to expand...
Click to collapse
or the error:
C:\motox\blankflash>qflash.exe -com5 -ramload MPRG8960.hex -mbn 33 MSM8960_boot
oader_singleimage.bin -v -o
Motorola qflash Utility version 1.3
COMPORT :COM5
RAMLOADER :MPRG8960.hex
type is 0x21
7 mbn file name MSM8960_bootloader_singleimage.bin type 33
verbose mode on
Motorola qflash dll version 1.6
dmss_software_version_req: received invalid or no response
Failed to send software version request
C:\motox\blankflash>
Click to expand...
Click to collapse
please help-me
(SORRY MY ENGLISH -> BY GOOGLE TRANSLATE)

wrong forum..this is for 2013 moto x 1st gen

Related

[Q] Help!!! aka "is my phone bricked?"

So i plugged in my Milestone to my PC and ran the Motorola Software Update, in hopes that 2.2 will get flashed.
Everything went smoothly until the update stopped and my phone was stuck with "SW Update In progress... " on the screen. The Motorola program on my PC had disappeared.
I waited for a bit but nothing happened to my phone, so I took out the battery and rebooted it. Then it booted into the bootloader and said shows "Err:A5,69,4E,00,3D".
Tried to boot into Recovery (i rooted my phone with openrecovery a few months back) but same, won't load recovery, won't boot Android either. Same error message.
Then I tried to flash the vulnerable SBF again, RSDLite shows all ok but I still can't enter into Recovery mode. Then I tried to flash the whole SBF instead of just the vulnerable recovery, and RSDlite stopped at 19% with this error:
ERROR: Flash failure: Phone[0000]: Error flashing subscriber unit. Device API Error: 0xE003003F Address: 0xD304DB80 Command: ADDR (Error Code: e003003f),
Detailed Error Details: Direction of the Error=2000, Command Value=200000, Code Group Number=39
Device ID: 0
Click to expand...
Click to collapse
Did Google search on this, found nothing useful, I don't know what is the problem. Have tried UK, HK and SG firmware but nothing works. Did my phone just become a brick? Now the IMEI and other details doesn't even show up on RSDLite anymore...
My system is Windows 7 32-bit, using RSDLite 4.9, latest drivers (4.8.0). Here is the full RSDLite log:
00:21:44, January 25, 2011
Line: 527
ERROR: AP Die ID: 22700114fe980304000000002400
00:21:44, January 25, 2011
Line: 534
ERROR: BP Die ID: 0000000000000000000000000000
00:21:44, January 25, 2011
Line: 541
ERROR: AP Public ID: 449dd7999eac8318cda5dc848722cd304fb725de
00:21:44, January 25, 2011
Line: 548
ERROR: BP Public ID: 0000000000000000000000000000000000000000
00:25:42, January 25, 2011
Line: 340
ERROR: Phone[0000]: Error flashing subscriber unit. Device API Error: 0xE003003F Address: 0xD304DB80 Command: ADDR
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
00:25:42, January 25, 2011
Line: 1190
ERROR: Phone[0000]: Flash failed.
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\PST_FP_FlashThread.cpp
Device ID: 0
00:25:42, January 25, 2011
Line: 597
ERROR: Flash failure: Phone[0000]: Error flashing subscriber unit. Device API Error: 0xE003003F Address: 0xD304DB80 Command: ADDR (Error Code: e003003f),
Detailed Error Details: Direction of the Error=2000, Command Value=200000, Code Group Number=39
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
Click to expand...
Click to collapse
What about the bootloader mode (aka fastboot mode)?
Does that work? Does a "fastboot devices" work at that point?
If fastboot sees your devices, you could flash from there.
Fastboot gives you the option to flash an update.zip, a specific partition or all partitions...
Sent from my Milestone using Tapatalk
A855 Boot Loop
Rooted - Rom Manager Clockwork Mod install
Liquid Frozen Yogurt 1.95
Phone boots to animation screen and reboots
Can not reboot into recovery
Will boot into bootloader
ADB recognizes phone when it is at animation screen in windows - "adb reboot recovery" reboots phone but not into recovery - same for "adb reboot bootloader"
Suggestions?
Love,
Guy with a pretty paperweight

help me rsd lite error msg

help me error message rsd lite flashing error
iam used Droid a855 and bootloader 2c7c FRG32D
Code:
08:13:04, March 09, 2011
Line: 527
ERROR: AP Die ID: 1a90011715680304000000002400
08:13:04, March 09, 2011
Line: 534
ERROR: BP Die ID: 0000000000000000000000000000
08:13:04, March 09, 2011
Line: 541
ERROR: AP Public ID: ffffffffffffffffffffffffffffffffffffffff
08:13:04, March 09, 2011
Line: 548
ERROR: BP Public ID: 0000000000000000000000000000000000000000
08:20:33, March 09, 2011
Line: 962
ERROR: Interface BP: Error sending RAM download for bootloader. Device API Error: 0xE003003F Address: 0x152000 Command: ADDR
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\RDLOp.cpp
Device ID: 0
08:20:33, March 09, 2011
Line: 1190
ERROR: Phone[0000]: Flash failed.
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\PST_FP_FlashThread.cpp
Device ID: 0
08:20:33, March 09, 2011
Line: 597
ERROR: Flash failure: Interface BP: Error sending RAM download for bootloader. Device API Error: 0xE003003F Address: 0x152000 Command: ADDR (Error Code: e003003f),
Detailed Error Details: Direction of the Error=2000, Command Value=200000, Code Group Number=257
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
and now restart the phone normal but cannot flashing the prl
I am Having Same issue. Phone Keeps failing. tried on Multiple computers and multiple os's (Windows 7 32/64, ubuntu) nothing seems to work. Only thing I have done to phone is Adeo (REDUX) and Superuser.
Now I want to go to 1.5.7 and I can not. I am attempting to flash back to vanilla 1.2.6 and am getting this error. ANY help with this would be greatly appreciated!
Been at this for a week now
BTW, Mine in an Atrix (AT&T) but same issue

[Q] Moto x blank flash complete but not enter fastboot

C:\Android>qflash.exe -com10 -ramload MPRG8960.hex -mbn 33 MSM8960_bootloader_si
ngleimage.bin -v -o
Motorola qflash Utility version 1.3
COMPORT :COM10
RAMLOADER :MPRG8960.hex
type is 0x21
7 mbn file name MSM8960_bootloader_singleimage.bin type 33
verbose mode on
Motorola qflash dll version 1.6
RAMLOADER VERSION: PBL_DloadVER2.0
------------------------------------------------------
DEVICE INFORMATION:
------------------------------------------------------
Version : 0x8
Min Version : 0x1
Max Write Size: 0x600
Model : 0x90
Device Size : 0
Description : Intel 28F400BX-TL or Intel 28F400BV-TL
------------------------------------------------------
Using passed in packet size, changing from 0x600 -> 0x600
EXTENDED_LINEAR_ADDRESS_REC @ 0x2a000000
Write 65536 bytes @ 0x2a000000
100EXTENDED_LINEAR_ADDRESS_REC @ 0x2a010000
Write 11840 bytes @ 0x2a010000
100START_LINEAR_ADDRESS_REC @ 0x2a000000
EOF_REC
Sleeping for 3s
-----------------------------------------------------
RAM DOWNLOADER INFORMATION
-----------------------------------------------------
cmd : 0x2
description : QCOM fast download protocol targ
version_number : 0x7
compatible_version: 0x2
max_block_size : 0x400
flash_base_address: 0x0
flash_id_len : 0x4
flash id : eMMC
window_size : 0x1e
number_of_sectors : 0x80
-----------------------------------------------------
sdl_send_security_mode: secutiry mode 0x0
Flashing MSM8960_bootloader_singleimage.bin 1969664 bytes into device
Keeping the first packet (1024 bytes) as hostage
Will release it if all is flashed well
100
Hostage released!
done
@ but same problem here. not come to fastboot and mobile like dead.
please help me. @
Not sure what exactly you are attempting to flash? Or how?
Can you provide more details on what happened to your device and what you are now trying to do?
Thanks!
Also note, questions go in the Q&A section, not general. This thread will be moved to Q&A for you. ?
Ah! This is what you are trying...
http://forum.xda-developers.com/showthread.php?t=2629057
Unfortunately, if the method is followed exactly in that thread, and doesn't work.... There isn't much else you can do. Going to a repair shop might be the only way.
Darth said:
Not sure what exactly you are attempting to flash? Or how?
Can you provide more details on what happened to your device and what you are now trying to do?
Thanks!
Also note, questions go in the Q&A section, not general. This thread will be moved to Q&A for you.
Click to expand...
Click to collapse
My moto x xt1052 older android version 4.4.4, then i am trying to flash (ATT_XT1058_4.4-13.11.1Q2.X-69-3_CFC_1FF.xml) with RSDLite but (gpt.bin) file not to be enter. then i am unlock bootloder (Device is UNLOCKED. Status Code: 3 )
then i am trying to flash with (XT1052_RETAIL-EU_4.4.4_KXA21.12-L1.26_54_cid7_CFC_1FF.xml) then gpt.bin and some file enter but others file not to be enter then not come to fastboot and mobile like dead. then i am completely success with blank flash but same problem here. not come to fastboot and mobile like dead.
You've either downgraded and bricked, or attempted to downgrade and bricked. Ask for help in the thread I linked. But if it doesn't work, your device is likely dead. You'll need a repair shop to look at it.
What could you solve it?

[Q] [HELP]Atrix HD hard bricked, try blankflash but some problem I can't understand.

I use common MSM8960 unbrick tool to flash my phone which connect to computer display QHSUSB_DLOAD, and driver install complete, but i flash the data, it display:
D:\刷机\blankflash>qflash -com3 -ramload MPRG8960.hex -mbn 33 MSM8960_bootloader
_singleimage.bin -v -o
Motorola qflash Utility version 1.3
COMPORT :COM3
RAMLOADER :MPRG8960.hex
type is 0x21
7 mbn file name MSM8960_bootloader_singleimage.bin type 33
verbose mode on
Motorola qflash dll version 1.6
RAMLOADER VERSION: PBL_DloadVER2.0
------------------------------------------------------
DEVICE INFORMATION:
------------------------------------------------------
Version : 0x8
Min Version : 0x1
Max Write Size: 0x600
Model : 0x90
Device Size : 0
Description : Intel 28F400BX-TL or Intel 28F400BV-TL
------------------------------------------------------
Using passed in packet size, changing from 0x600 -> 0x600
EXTENDED_LINEAR_ADDRESS_REC @ 0x2a000000
Write 65536 bytes @ 0x2a000000
100EXTENDED_LINEAR_ADDRESS_REC @ 0x2a010000
Write 11840 bytes @ 0x2a010000
100START_LINEAR_ADDRESS_REC @ 0x2a000000
No data read from USB. This may not be an error. Trying again...
No data read from USB. This may not be an error. Trying again...
No data read from USB. This may not be an error. Trying again...
No data read from USB. This may not be an error. Trying again...
No data read from USB. This may not be an error. Trying again...
Still no data, giving up!
dmss_go : failed to receive ACK
Error loading MPRG8960.hex into device
why can't ?

General issue in Android Studio - Cannot launch AVD in emulator.

Hello,
I could not find an answer on how to preload the expected libaries so I hope anyone can help me here.
I am a complete noob In devloping with Android Studio.
I tried to write a small app and ran it with the following errors while loading th e AVD (Android 5.1 , WVGA):
Code:
Cannot launch AVD in emulator.
Output:
libGL error: unable to load driver: i915_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: i915
libGL error: unable to load driver: swrast_dri.so
libGL error: failed to load driver: swrast
X Error of failed request: GLXBadContext
Major opcode of failed request: 155 (GLX)
Minor opcode of failed request: 6 (X_GLXIsDirect)
Serial number of failed request: 49
Current serial number in output stream: 48
emulator: ERROR: virtual device name contains invalid characters
emulator: could not find virtual device named '3.2_QVGA_(ADP2)_API_22'
I think to get this solved will not be quiet diffcult for advanced users.
Thank you verry much for your help! :good:
Some infos that might help you:
OS: Kubuntu 16.04
Android Studio 2.2.3
used coding language: Java

Categories

Resources