eek. Bricked xt1068 detected as Qualcomm HS-USB QDLoader 9008 (COM3) - G 2014 Q&A, Help & Troubleshooting

I have a dual SIM UK Moto G 2014. I made some resizing adjustments to the data partition and after rebooting I have nothing on the screen. Just black, no back-light. Windows 8 recognizes the device as Qualcomm HS-USB QDLoader 9008 (COM3). (I searched that but could only find posts for other devices suggesting sending them to the manufacturer). I did my best to google my way out of this but I think I need help.
Is this a scenario where I'd need MBM-CI 5.0? Or would that not help? I'm not sure what to do next.
Many thanks!
edit: If I send it for warranty repair would they check if I've modified it?

Okay. I'm sending it for repairs tomorrow with Motorola (unless anyone can think of a good reason not to).
Thanks.

Only thing I could find is this thread: http://forum.xda-developers.com/moto-g-2014/general/unbrick-hard-bricked-moto-g-2nd-gen-5-0-t2966010
Maybe thereĀ“s something that can help you.

I've actually tried the steps in that thread already. I disabled driver signing in Windows 8 and tried to apply the driver to the device but still disallows me from using it. It's not showing qh_usb so I wasn't expecting it to work.

BER
After chasing and chasing (what terrible customer service!) Motorola are saying my device is 'beyond economical repair' and are returning my device to me, and are saying they will not replace it because it is BER; I don't think that's the real reason they're not replacing it...but what can a guy do?
Any further advice before I go and buy a new phone?
Many thanks.

Their support came back and said that the mainboard was 'warped'. LOL.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Does that look warped to you? I'd sure as hell like to know what constitutes straight.

Related

[Q] N/A on RSD Lite

i get this...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i get this in the device properties....and it will not boot past the white m symbol
please help
anybody ? please
I'm pretty sure I've had this and just went through with flashing anyway. Maybe I'm mistaken and if you don't want to risk it, wait for more opinions.
What's happening when you choose a *.sbf for flashing?
Zatapatalkowane z MotoStone'a
i tried flashing anyway but still the device doesn't pass the white m symbol
Which drivers do you have?
BooZon said:
Which drivers do you have?
Click to expand...
Click to collapse
the lastest..
do you have a different pc to try it on? rsdlite works on my laptopn while it doesnt really work on my moms for some reason. id try it on a different pc first. next i'd like to know what sbf file your trying to flash. it could be corrupt or something, try a test with another sbf file like from peter alfonsos site and see if it works.
***wow, apparently i have to wait 5 whole minutes before posting becuase im apparently a "new" user whos been here since may of 2010... i guess i should crank out more posts heh? (looks at watch, seems to be January 2 of 2012 )
You won't be able to initiate the flash process until the phone boots directly into bootloader mode, which involves a mostly black screen with small white text. Keep trying while holding down the proper buttons and you should be able to get there.

Help me to select between octopus or octoplus to unbrick ls991 qload 9008

I have two choices to buy whether octopus or octoplus box.
One non-jtag and other has jtag so whoch one I should buy to fix my ls991 hard bricked.
One's cost is 100$ and other is 300$ around.
My guess is you need the jtag version. Not 100% sure tho.
irbaaz said:
I have two choices to buy whether octopus or octoplus box.
One non-jtag and other has jtag so whoch one I should buy to fix my ls991 hard bricked.
One's cost is 100$ and other is 300$ around.
Click to expand...
Click to collapse
tabp0le said:
My guess is you need the jtag version. Not 100% sure tho.
Click to expand...
Click to collapse
Ive read claim that some do it without the jtag. But from ive read the only way is jtag.
TheMadScientist420 said:
Ive read claim that some do it without the jtag. But from ive read the only way is jtag.
Click to expand...
Click to collapse
I have bought the octoplus box.
Now has new issue it is showing some weird pinout have CLK , 1.8V , 2.8V and so on.
Only cable I have found with package is 20 pin cable which is matching with it.
So I waiting for octoplus people to confirm that this cable will do the job.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

D415 possibly faulty?

My LG D415 has been acting weird lately. The phone would randomly reboot even in TWRP and when the phone is actually usable, the hardware buttons + touch would not work for a minute or two sometimes. Then out of the blue one day the phone just bricked itself and was detected as Qualcomm HS-USB QDloader 9008 when plugged into a PC. Since theres no known way for D415 users to get out of that I just simply left the phone alone for a few days and it started working again somehow. I reflashed the bootstack and went back to CM13 (was on turbo 7.0) and that seemed to stop the random bricking but the random reboots still occur along with the hardware issues.
The thing that really freaked me out was when I adb shell my phone and got garbled text for the phone name
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What i'm really wondering is if my D415 board is screwed and if it is could I fix this with reflashing the .kdz?
The phone appears not to turn on but when I plug it in it mounts as a usb?
Inside theres modem files and such. Totally clueless on what to do here I need help ASAP!
Edit: I pulled the battery out in panic and plugged in the phone w/o battery and it shows a picture of a battery with a triangle BUT so i put battery back in and this time around it boots into fastboot and only fastboot.
Edit2: Pulled the battery again to try to get the phone to mount as a usb and instead started working normally again... fml

Locked phone into "Flashed with unauthorized software" state, IMEI at 0

To make a long story short, a relative bought a phone off ebay that was in Retail/Demo mode and I was tasked with trying to get it out of that state by flashing a different stock ROM onto it. I used to have absolutely no issue before with older phones, but, after a few softboots with no success, I've eventually ended up reaching this far in nuking the phone, and even the IMEI in download mode is showing a 0 (though I'm not sure if that wasn't always like that).
From what I've seen the phone is certainly the Snapdragon variant, and yet there was no way to activate OEM unlocking within the phone. I know this situation is rather insane and I could be SOL but here's to hoping someone could point me in a direction to help fix this thing. I haven't tried flashing the unofficial TWRP in fear that it's going to screw over my recovery (in which I forgot to mention it works perfectly fine at the moment). Alongside with the security error, I have the secure check fail with modem displaying as well. Is there a certain ROM version that might help? I've attached a screenshot that I took right before I fell into the abyss, so hopefully that'll help (unless you can't see it out of me being new). Thanks for any replies in advance.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It's a brick without an imei number
Sent from my SM-N960F using Tapatalk
Contact seller, we don't discussion this here
Thread closed!

Samsung SM-N950F/DS sensors stopped after update.

Hello everyone. I'm sure many people are having problems with their Note8s specially after receiving updates. Mine also did broke at some point where I lost the track. What I have done to try to fix it so far is;
Went into download mode - had this ;
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I think the phone is in Egypt variant since it says carrier ID is Egypt?
For the Recovery mode I had these;
So as you see, I tried many things to fix this without sending it to SC since I live in North Cyprus. I'm pretty sure that it is not hardware related but more likely a software stuff. Any ideas to fix this? Thanks.
Btw, I am not sure if the images are visible or not, can someone leave me a feedback please?
tMrz said:
Btw, I am not sure if the images are visible or not, can someone leave me a feedback please?
Click to expand...
Click to collapse
Images are not visible
zzThrain said:
Images are not visible
Click to expand...
Click to collapse
They should be fixed now, thanks for the feedback
i got the problem too
No one has any idea about how to fix this instead of sending phone to Samsung Care? Like draining the battery completely etc? Or possible software conflicts? Since I have updated to bootlader 6, I cannot go back to 5 either.

Categories

Resources