Hi guys,
my girlfriends (non-rooted, vanilla) HTC Desire X did an OTA update and has been dead ever since. Power on + Volume Down does nothing, removing battery for days didn't change anything and in an USB scan it only appears as the dreaded QHSUSB_DLOAD and never as an USB mass storage device (which is what fastboot etc. tries to look for).
So, I guess the OTA update broke the boot-loader or similar in such a way so the Qualcomm chipset doesn't recognize it anymore, and fallbacks into the USB recovery mode.. and hence I really want to find a way to restore at least as much of the bootloader that I can access the eMMC userdata partition because there are photos I want to recover for her.
I know you can access the bootblock etc. through a soldered JTAG port and the RIFF box or similar, but the phone has warranty and I don't really want to void it by soldering away (in case maybe the phone actually was hardware broken). Also, since the photos on the phone are valuable I don't want to give it to the HTC service guys without at least trying something else first (whom I talked to and they say they would just swap the PCB and have to send in the old one to HTC, so I can't even get it afterwards to do the JTAG surgery on it...)
Any ideas? Is it possible at all to reflash the bootloader through the QHSUSB_DLOAD recovery protocol for these devices?
thanks
mnemonoid said:
Hi guys,
my girlfriends (non-rooted, vanilla) HTC Desire X did an OTA update and has been dead ever since. Power on + Volume Down does nothing, removing battery for days didn't change anything and in an USB scan it only appears as the dreaded QHSUSB_DLOAD and never as an USB mass storage device (which is what fastboot etc. tries to look for).
So, I guess the OTA update broke the boot-loader or similar in such a way so the Qualcomm chipset doesn't recognize it anymore, and fallbacks into the USB recovery mode.. and hence I really want to find a way to restore at least as much of the bootloader that I can access the eMMC userdata partition because there are photos I want to recover for her.
I know you can access the bootblock etc. through a soldered JTAG port and the RIFF box or similar, but the phone has warranty and I don't really want to void it by soldering away (in case maybe the phone actually was hardware broken). Also, since the photos on the phone are valuable I don't want to give it to the HTC service guys without at least trying something else first (whom I talked to and they say they would just swap the PCB and have to send in the old one to HTC, so I can't even get it afterwards to do the JTAG surgery on it...)
Any ideas? Is it possible at all to reflash the bootloader through the QHSUSB_DLOAD recovery protocol for these devices?
thanks
Click to expand...
Click to collapse
Ouch. QHSUSB_DLOAD is an effed up thing. What did your girlfriend do after she did the ota? Also what version is it?
Sent from my Nexus 7 using Tapatalk HD
Stereo8 said:
Ouch. QHSUSB_DLOAD is an effed up thing. What did your girlfriend do after she did the ota? Also what version is it?
Click to expand...
Click to collapse
Hi, actually she just woke up, saw the phone asking about the upgrade, pressed yes and when she looked at it again later it was dead. So she didn't do anything after, and I think it was the stock android as shipped with the phone when she got it, must have been more than 6 months ago.
I did some research and it seems like the RIFF Box guys made a tool for their RIFF Manager software that can actually set up their DCC Loader monitor without the JTAG port, just using USB and the qualcomm communication (QHSUSB_DLOAD). After that, it's possible to both read and write to the flash areas I guess.
Problem is, they only support up to snapdragon S2 and the Desire X is an S4 (MSM8225 is the chipset as far as I know). Didn't seem that they had any plans to support this anytime soon.
Do you know if the internal flash in the Desire X is an eMMC or a NAND-flash by the way? The one that keeps the userdata and kernel.
mnemonoid said:
Hi, actually she just woke up, saw the phone asking about the upgrade, pressed yes and when she looked at it again later it was dead. So she didn't do anything after, and I think it was the stock android as shipped with the phone when she got it, must have been more than 6 months ago.
I did some research and it seems like the RIFF Box guys made a tool for their RIFF Manager software that can actually set up their DCC Loader monitor without the JTAG port, just using USB and the qualcomm communication (QHSUSB_DLOAD). After that, it's possible to both read and write to the flash areas I guess.
Problem is, they only support up to snapdragon S2 and the Desire X is an S4 (MSM8225 is the chipset as far as I know). Didn't seem that they had any plans to support this anytime soon.
Do you know if the internal flash in the Desire X is an eMMC or a NAND-flash by the way? The one that keeps the userdata and kernel.
Click to expand...
Click to collapse
I'm pretty sure it's emmc... If she didn't press any button combos and just long pressed the power button, she should be fine. But in this case, QHSUSB_DLOAD wasn't called by the user, so that update screwed up something that the system fell back to it...
Sent from my HTC Desire X using Tapatalk HD
Related
I need help. My htc amaze 4g is rooted and I have s off and super cid and i was running on android revolution hd rom, an app by the name of root mobile odin pro was installed on my phone, it was attempting to create a dump file so that I could give it to the dev so that he could possibly make my cell phone compatible with the app. But now my phone will no longer power on, it does not charge, no led light, the battery is full, has sd card, no sim card. under device manager on windows 7 it comes up as QHSUSB DLOAD. Will not run into recovery mode when vol down and power button is held. Computer does not recognize it. Can not run adb in cmd prompt, no reboot command works because device can not be found. I've tried to do everything on unlimited io page to no avail. When I do connect the phone to the PC it does make a sound to inform me that I just connected it. But the screen remains black and the light remains off.
I am using the UNBRICK PROJECT THAT IS ON http://forum.xda-developers.com/showthread.php?p=25501116
I AM ON UBUNTU BUT WHEN I TYPE IN
./brickdetect.sh
INTO THE TERMINAL IT DOES NOT DETECT MY DEVICE
Please help!
Sincerely,
Desperate Soul
Can you boot into fastboot? Battery pull, replace and Vol Down + Power
I can't
Double0EK said:
Can you boot into fastboot? Battery pull, replace and Vol Down + Power
Click to expand...
Click to collapse
No I can not
what recovery? and have you tried a different battery?
my recovery is...
andy55 said:
what recovery? and have you tried a different battery?
Click to expand...
Click to collapse
Recovery: 4ext
and my bf has the same phone, I tried his full battery, no response, when plugged in no led light to confirm it's charging.
jlnive said:
I need help. My htc amaze 4g is rooted and I have s off and super cid and i was running on android revolution hd rom, an app by the name of root mobile odin pro was installed on my phone, it was attempting to create a dump file so that I could give it to the dev so that he could possibly make my cell phone compatible with the app. But now my phone will no longer power on, it does not charge, no led light, the battery is full, has sd card, no sim card. under device manager on windows 7 it comes up as QHSUSB DLOAD. Will not run into recovery mode when vol down and power button is held. Computer does not recognize it. Can not run adb in cmd prompt, no reboot command works because device can not be found. I've tried to do everything on unlimited io page to no avail.
I am using the UNBRICK PROJECT THAT IS ON http://forum.xda-developers.com/showthread.php?p=25501116
I AM ON UBUNTU BUT WHEN I TYPE IN
./brickdetect.sh
INTO THE TERMINAL IT DOES NOT DETECT MY DEVICE
Please help!
Sincerely,
Desperate Soul
Click to expand...
Click to collapse
What did you do with the app? Did you attempt to flash ANYTHING on the phone? Sounds like you did however and messed up with one of its internal partitions.
EDIT: I'm going to go ahead and say you bricked your phone. I just re-read and... Why would you install something meant for *SAMSUNG* phones, on a *HTC* phone? You messed up right there. The unbricking project only will unbrick HTC Amazes when they're bricked in a certain fashion. It specifically states that it is known to be working for "writesecureflag 3" type of bricks. You could try and see if it will work in your case, but it probably won't. More likely than not, with the app you used, you might have accidentally wiped a partition that would have been safe for samsung devices (but dangerous on HTC devices).
Like he said ^^^ anything odin is for Samsung... u now have a nice coaster
Sent from my Wicked Galaxy S III
devestated
Keylogger_0 said:
What did you do with the app? Did you attempt to flash ANYTHING on the phone? Sounds like you did however and messed up with one of its internal partitions.
EDIT: I'm going to go ahead and say you bricked your phone. I just re-read and... Why would you install something meant for *SAMSUNG* phones, on a *HTC* phone? You messed up right there. The unbricking project only will unbrick HTC Amazes when they're bricked in a certain fashion. It specifically states that it is known to be working for "writesecureflag 3" type of bricks. You could try and see if it will work in your case, but it probably won't. More likely than not, with the app you used, you might have accidentally wiped a partition that would have been safe for samsung devices (but dangerous on HTC devices).
Click to expand...
Click to collapse
*** I am so devastated, my cell phone was so valuable to me. Can't believe I was so senseless to make such an error as this. The app was for Samsung but the app said it could create a dump file so that my device would become compatible . But that sounds so stupid to me now . A little too late. I'm so sad. I wish there was some way to fix it. Wish there was a USB jig for HTC's.
IF YOU KNOW OF ANYTHING, ABSOLUTELY ANYTHING THAT MAY HELP PLEASE LET ME KNOW!!!!!!!
(Thank you for all the reply's)
IT happens
Hey it happens, that how we learn thing sometimes, and sometime it can cost us. You could try these things
1) See if it can be JTAGed (cheapest possibility)
2) If it's still under warranty (which it probably isn't) send it off, and say it wouldn't power on after a update.
3) Find a Amaze with a broken or cracked screen, and replace the motherboard yourself.
That's all I can think of. Good luck
I'm just wondering if you can completely Hard Brick a LG G2 to a point, where there is no revive possible.
I can purchase a cheap LG G2 international version, but the seller says that he broke it during flashing a Kernel.
Can you for example revive a phone,that had a Kernel from completely different phone flashed?
Any insight would be greatly appreciated.
Sent from my C6503 using Tapatalk 2
If it's true he only flashed a new kernel then u can restore it. If he messed with the partitions then.... No. If he used a broken usb cable and fried it....
Well ask to try the phone before u by it. Also check if it's stolen
Alright, I gathered some more information from the seller.
He tried updating TWRP, but he followed wrong instructions from some website.
He can´t enter Recovery or Download Mode on the Phone.
The Display is active, but only Backlight.
When he connects the Phone to his Computer, it shows multiple Mass Storages, but the LG Software doesn´t recognize it.
Is this a common problem, that is easy to fix, or should I rather wait for another Deal to come up.
p.s. I asked him for a receipt, and he says that he has one.
E-I-K-E said:
Alright, I gathered some more information from the seller.
He tried updating TWRP, but he followed wrong instructions from some website.
He can´t enter Recovery or Download Mode on the Phone.
The Display is active, but only Backlight.
When he connects the Phone to his Computer, it shows multiple Mass Storages, but the LG Software doesn´t recognize it.
Is this a common problem, that is easy to fix, or should I rather wait for another Deal to come up.
p.s. I asked him for a receipt, and he says that he has one.
Click to expand...
Click to collapse
If the guy was updating through TWRP, he probably have some knowledge on the matter, and the chances that he bricked it for good is high.
When I messed up my G2 a few times, being able to enter in download mode was the hint that the phone was revivable, if him really can't enter the download mode, then it is probably a bigger problem.
But the question is, by buying this possible lemon, how much will you be saving compared to buying a brand new?
If it's showing up like that, if you have a Linux machine you may be able to use dd to flash factory images to the partitions. There is a guide to it somewhere on here. But even if you were successful in flashing those, it really depends on how badly he screwed it up. In particular I really hope he didn't damage or wipe his efs. Or at least has it backed up.
Honestly, I'd point him to the right guides and have him fix it. If he screwed up his efs, or messed the partitions up, or fried something, it's dead and not coming back. If all he did was flash a kernel in twrp and it was actually from this phone and it was just a bad download or flash or something, then you'd probably be okay, but if that were the case you'd get a secure boot error and still be able to enter download mode. Personally, I would not buy a phone that won't boot, especially if the seller isn't even sure what's wrong with it.
Sent from my LG-G2 using Tapatalk
sounds recoverable, if there is a backlight and mass storage comes up that's good, you can dd partitions with linux
no backlight + no recognizable usb device at all = bricked
still, buy at your own risk
It is.. i just did by flashing a broken rom.. sent it to the repair center and they replaced the motherboard
Right, I asked him if the Device shows as qhsusb_bulk in device Manager, and it does.
The only thing that worries me, is that there is no Boot Logo, most of the people in the Linux Fix Thread atleast get a LG Logo and not just Backlight.
I´m really unsure what to do, I can save like 150€ by buying the broken G2, but well . . . I dont know if I can fix it.
Another problem is, that I have not a single clue on how to operate Linux/Ubuntu, and the only real fix requires either of those
E-I-K-E said:
Right, I asked him if the Device shows as qhsusb_bulk in device Manager, and it does.
The only thing that worries me, is that there is no Boot Logo, most of the people in the Linux Fix Thread atleast get a LG Logo and not just Backlight.
I´m really unsure what to do, I can save like 150€ by buying the broken G2, but well . . . I dont know if I can fix it.
Another problem is, that I have not a single clue on how to operate Linux/Ubuntu, and the only real fix requires either of those
Click to expand...
Click to collapse
Just look up a guide on how to install an Ubuntu virtual machine. You should be able to connect your G2 to that virtual if you let it capture the USB port. If you can get it cheap, buy it and try to negotiate so you might have a chance on selling it for higher later on if you can't fix it. To me though, it sounds quite fixable, I would go for it.
E-I-K-E said:
The only thing that worries me, is that there is no Boot Logo, most of the people in the Linux Fix Thread atleast get a LG Logo and not just Backlight.
Click to expand...
Click to collapse
this doesn't really matter, when I was trying to mess with the bootloader and corrupted it a few times I've never had the LG logo, as long as it comes up as storage you can DD it - the only time its a true brick is with no backlight and no usb device
if theres no boot logo you probably need to DD the aboot in
dr87 said:
this doesn't really matter, when I was trying to mess with the bootloader and corrupted it a few times I've never had the LG logo, as long as it comes up as storage you can DD it - the only time its a true brick is with no backlight and no usb device
if theres no boot logo you probably need to DD the aboot in
Click to expand...
Click to collapse
This.. If you have bulk mode, you can fix it!
kewkie said:
It is.. i just did by flashing a broken rom.. sent it to the repair center and they replaced the motherboard
Click to expand...
Click to collapse
That's actually just killing a fly with a sledgehammer. 99.9999% sure you got a softbrick.
Sent from my Moto G using XDA Premium 4 mobile app
Savoca said:
That's actually just killing a fly with a sledgehammer. 99.9999% sure you got a softbrick.
Sent from my Moto G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Tried 3 different laptops
1x windows 8.1 (with ubuntu)
1x window 7 x64
1x windows 7 x86
Reinstalled all drivers, tried everything, but i couldnt get any usb connection.
- Factory reset? Freeze
- Normal boot? Stuck at bootlogo
- Download mode? Stucking at the loading screen
E-I-K-E said:
Alright, I gathered some more information from the seller.
He tried updating TWRP, but he followed wrong instructions from some website.
He can´t enter Recovery or Download Mode on the Phone.
The Display is active, but only Backlight.
Click to expand...
Click to collapse
I had that problem when updating TWRP too. You have to be careful because these recoveries are only made for specific firmware versions. I cant remember how I fixed the issue after only being able to get a backlight on and no image, but I did fix it and my phone works fine. I do think you will need the TWRP files already on the phone to fix though, so you can somehow manage to flash back. They will need to be on the phone since you can push anything via ADB
E-I-K-E said:
Right, I asked him if the Device shows as qhsusb_bulk in device Manager, and it does.
The only thing that worries me, is that there is no Boot Logo, most of the people in the Linux Fix Thread atleast get a LG Logo and not just Backlight.
I´m really unsure what to do, I can save like 150€ by buying the broken G2, but well . . . I dont know if I can fix it.
Another problem is, that I have not a single clue on how to operate Linux/Ubuntu, and the only real fix requires either of those
Click to expand...
Click to collapse
i've been in this bricked situation when i was trying the 4.4.2 update manually...completely bricked, could not get into download mode too...so gave it to the service centre which at first said the main board will have to be changed when recovering through software upgrade failed...next day i got the phone back as they managed to flash the software back on it...
does not end here...i tried to flash optimus g pro 2 rom through twrp and same thing happened again...but was lucky this time as i could enter download mode and flashed kdz to recover...
E-I-K-E said:
I'm just wondering if you can completely Hard Brick a LG G2 to a point, where there is no revive possible.
I can purchase a cheap LG G2 international version, but the seller says that he broke it during flashing a Kernel.
Can you for example revive a phone,that had a Kernel from completely different phone flashed?
Any insight would be greatly appreciated.
Sent from my C6503 using Tapatalk 2
Click to expand...
Click to collapse
And yes i truly believe that our device can be hard bricked like i did mine today.
I tried to compile a custom bootloader for G2 using Qualcom's sources and fraction of LK. But in doing so i left my phone in a quasi-state where it will not connect as a usb device coz it does not pass the bootloader (Although bootloader is working as it should). .
So the only two option remain here for me is
1. To send phone back to LG service center where they'll do idk what.
2. To use JTAG or short the ic (Wonder if it could be done ) i.e manually open the phone and boot into the primary bootloader(Qcom legacy BL).
See that's how you can hard brick ur phone the right way
fizzy177 said:
And yes i truly believe that our device can be hard bricked like i did mine today.
I tried to compile a custom bootloader for G2 using Qualcom's sources and fraction of LK. But in doing so i left my phone in a quasi-state where it will not connect as a usb device coz it does not pass the bootloader (Although bootloader is working as it should). .
So the only two option remain here for me is
1. To send phone back to LG service center where they'll do idk what.
2. To use JTAG or short the ic (Wonder if it could be done ) i.e manually open the phone and boot into the primary bootloader(Qcom legacy BL).
See that's how you can hard brick ur phone the right way
Click to expand...
Click to collapse
Your LK build wouldn't have matched the sbl1, anything other than LG's signed aboot wouldn't work.. /:
Sent from my Nexus 5 using XDA Premium 4 mobile app
Savoca said:
Your LK build wouldn't have matched the sbl1, anything other than LG's signed aboot wouldn't work.. /:
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
But it did work coz our bootloader enfoces the signature check not in the sbl.(Our Primary boot loader)
i'm sure of it because it tries to go to download option but freezes at initial stage.
had it been the case my device would've been detected as qucom_bulk device or so..
---------- Post added at 09:03 AM ---------- Previous post was at 08:58 AM ----------
kewkie said:
Tried 3 different laptops
1x windows 8.1 (with ubuntu)
1x window 7 x64
1x windows 7 x86
Reinstalled all drivers, tried everything, but i couldnt get any usb connection.
- Factory reset? Freeze
- Normal boot? Stuck at bootlogo
- Download mode? Stucking at the loading screen
Click to expand...
Click to collapse
You my dear friend are a victim of a curroupt bootloader seqence(NOT THE CoRRUPT BOOTLOADER) i.e
Your phone would start something like
1- EFI initialization ok
2-Primary Boot Load -ok
3-Vendor Boot Load -ok
4- Error unable to find proper boot sequence- system halted
So ur best options are the one that i've stated just above this thread.
My case. I root and flash custom recovery then apply OTA = medium brick. Download mode was not functioning, only recovery. To make matter worse, I flashed KK stock rom through ADB in recovery = super brick. Then I went to LG service center with poker face asked for reparation. They asked (confirm) whether your phone is rooted or not (they had already know though) and I just said like It is my sister's phone. Then they they open the phone and maybe directly format the sd card with some stuff. My phone is restored again afterward. In my opinion, software modification can always be repaired unless you fry your phone through overclock or overvolt.
ramabg said:
My case. I root and flash custom recovery then apply OTA = medium brick. Download mode was not functioning, only recovery. To make matter worse, I flashed KK stock rom through ADB in recovery = super brick. Then I went to LG service center with poker face asked for reparation. They asked (confirm) whether your phone is rooted or not (they had already know though) and I just said like It is my sister's phone. Then they they open the phone and maybe directly format the sd card with some stuff. My phone is restored again afterward. In my opinion, software modification can always be repaired unless you fry your phone through overclock or overvolt.
Click to expand...
Click to collapse
It's not a brick if it was restored... meh.
I bought this phone a few days ago on a swap site on facebook and seemed to have hard bricked it within an hour. it was running android 4.1.2 and i wanted to try upgrading the firmware by flashing CM. first step was backing up to the h1 broadband. done. next rooting. done. good. last step was unlocking the bootloader. i saw a post that said since i was running 4.1 i would be ok to use ez unlock. Big mistake. i reset the phone and now nothing. the only light i can manage to get is a red power light when connected to a charger with no battery. I tried the SD card approach with the verizon unbrick image since the phones are similar but the file i had did not work. I have also tried the USB jig. it didnt work either. next Im planning to try the USB jig with the unbrick image but i was curious to see if the unbrick image for the straight talk version was floating around anywhere. After hours of searching, i have not came across it myself. Anybody know my options outside of jtag or replacing the logic board? and if you have the unbrick image please let me know! thanks.
I dont know if this is helpful or not but in my usb devices if i hit the power button on the phone it pops us with a Qualcomm driver. ive looked around and found that it shows up in other rom flashers like miflash but im not able to send any files to the device. Obviously its doing something if the computer recognizes it right?
nobody here able to help me with this??
Hello everyone, so the other day I put my sim on my v10 just for a change. This v10 is rooted with elimators kernel with twrp.3.0.2. Anyway I had no radio at all. The bars showed but no activity there. I went to about phone and found that all information about the phone identity was gone , imei, service, baseband unknown, etc. I wiped to system and started fresh with lgups and tot. Files re-rooted the phone and to no avail. It still had none of the information avalable . so it thought maybe I was missingoing the baseband so I foolishly flashed one though twrp after it flashed it was light out,, power button nothing, the phone literally went cold, colder then I've ever felt. it. It felt dead for reals.........I did have it show up in device manager with Husb....bla bla... the it went to quamcom..... bla..bla... and now the computer don't see it any longer. Unless it just got sick and tired of me shoving the USB cord in and out of the socket and deactivated the USB port.... I know there is a lot of stuff out there as far as mega bricks, if anyone out there can get me out of this ,it would be awesome... my last brick with this phone was there was no root yet and I almost got though a combination of software .etc... that took me three months to Un brick it.. this brick is even worst because of No sign of life. So I'm open to use this phone as a Guinny pig for some new stuff If anyone out there's got a solution to try...... thanks
Wutever1969 said:
Hello everyone, so the other day I put my sim on my v10 just for a change. This v10 is rooted with elimators kernel with twrp.3.0.2. Anyway I had no radio at all. The bars showed but no activity there. I went to about phone and found that all information about the phone identity was gone , imei, service, baseband unknown, etc. I wiped to system and started fresh with lgups and tot. Files re-rooted the phone and to no avail. It still had none of the information avalable . so it thought maybe I was missingoing the baseband so I foolishly flashed one though twrp after it flashed it was light out,, power button nothing, the phone literally went cold, colder then I've ever felt. it. It felt dead for reals.........I did have it show up in device manager with Husb....bla bla... the it went to quamcom..... bla..bla... and now the computer don't see it any longer. Unless it just got sick and tired of me shoving the USB cord in and out of the socket and deactivated the USB port.... I know there is a lot of stuff out there as far as mega bricks, if anyone out there can get me out of this ,it would be awesome... my last brick with this phone was there was no root yet and I almost got though a combination of software .etc... that took me three months to Un brick it.. this brick is even worst because of No sign of life. So I'm open to use this phone as a Guinny pig for some new stuff If anyone out there's got a solution to try...... thanks
Click to expand...
Click to collapse
Sorry for your brick and if you can get into that Qualcomm USB mode again you may be OK, see here
http://forum.xda-developers.com/tmo...brick-phone-h901-qualcomm-9008-t3440359/page7
The issue may be due to the anti roll back 'feature' lg gave us, if it finds firmware from a lower version you can brick or could just be a mismatch between radio and bootloader
Neither are good but you may be in luck with tungkick's method
so here is an update date, I am back to my device manger seeing the phone under Qualcomm HS-USB QDLoader 9008, i have been able to install qualcomm drivers and qualcomm's QPST config program does see the phone on COM port 5, I guess now my hold up is i need the manufactures firmware which im not sure i can get, so again im stuck i guess unless there someone out there with those files
Wutever1969 said:
so here is an update date, I am back to my device manger seeing the phone under Qualcomm HS-USB QDLoader 9008, i have been able to install qualcomm drivers and qualcomm's QPST config program does see the phone on COM port 5, I guess now my hold up is i need the manufactures firmware which im not sure i can get, so again im stuck i guess unless there someone out there with those files
Click to expand...
Click to collapse
Did the files in the link i gave you not contain what you need?
demkantor said:
Did the files in the link i gave you not contain what you need?
Click to expand...
Click to collapse
i did thank you i, i have not had a chance to look over any of it yet. the link you gave me sends me to google drive with lots of programs, which direction are you pointing me towards , forgive me if i sound alittle retarded i have been working on a lot of different phones lately. this v10 has fried my brain, as far as LG's programs like UPS and Bridge neither of them see the phone, it still in COM's HS-USB Qloader 9008, i was messing with qualcomm's manufacture software, but with out LG's manufacture rom i have not gotten far.... anyway thanks again ,,,,,i did see this sd card thing is that what i need to be trying? let know ,again thanks brian
Hi guys!
I think I did something stupid while updating my XT1650-03 to Nougat.
What I did was manually flash stock nougat ROM (retbr) through fastboot, following the instructions within flashfile.xml, but, as I've read some bad things about the updated bootloader I stupidly decided not to flash it. The result is that it won't power up, even though I've tried: pressing power+vol. down; power; plugging the charger; fastboot commmands ( I was hoping it was just the screen that was off); to no avail.
I've noticed that when I plug the usb cable to the computer it plays that sound of connected devices.
Any suggestions? I'm probably going to have to take my device to authorised repair (off warranty, I know), but they usually take weeks to fix anything, so you guys are my best bet for now.
Thanks in advance!
martonto said:
Hi guys!
I think I did something stupid while updating my XT1650-03 to Nougat.
What I did was manually flash stock nougat ROM (retbr) through fastboot, following the instructions within flashfile.xml, but, as I've read some bad things about the updated bootloader I stupidly decided not to flash it. The result is that it won't power up, even though I've tried: pressing power+vol. down; power; plugging the charger; fastboot commmands ( I was hoping it was just the screen that was off); to no avail.
I've noticed that when I plug the usb cable to the computer it plays that sound of connected devices.
Any suggestions? I'm probably going to have to take my device to authorised repair (off warranty, I know), but they usually take weeks to fix anything, so you guys are my best bet for now.
Thanks in advance!
Click to expand...
Click to collapse
Don't even bother going to the service center. The same happened with my device and they refused to give me the warranty. Motorola voids it the moment you get the unlock code. So my device was dead for 3 months. And I fixed it few days back. The good news is that your PC is detecting the device.
I will post the solution with a new thread in few minutes.
Manish54 said:
Don't even bother going to the service center. The same happened with my device and they refused to give me the warranty. Motorola voids it the moment you get the unlock code. So my device was dead for 3 months. And I fixed it few days back. The good news is that your PC is detecting the device.
I will post the solution with a new thread in few minutes.
Click to expand...
Click to collapse
Thank you so much for your reply, it's very much appreciated! I didn't think anyone would reply that soon
I'll wait for your thread!
There ya go
https://forum.xda-developers.com/moto-z/how-to/guide-how-to-unbrick-moto-z-hardbricked-t3590133
So, I'm totally lost.
As I posted in the thread above, even though Manish54 has been very kind to help, that solution did not work for me, so I've been trying to find another way. The thing is, this issue is beyond my comprehension. I'm not new to flashing and stuff, but I am new to moto Z. I understand that I should've been more careful and also have read a bit more before starting to mess with a new device, so feel free to judge me .
For instance, I don't know what fsg.mbm, adspso.bin, BTFM.bin and oem.img are for, since my old phone didn't have those (or at least I didn't need to mess with those), and I also don't know it they're relevant to my problem. If anyone could point me to some info on that, it'd be greatly helpfull.
Besides that, I've found mentions to tools like qualcomm's BoardDiag and QPST QFIL, but I'm not really sure if they apply for my situation, or even if I can manage to adapt the guides I've found to work on the Moto Z.
Any help is very much appreciated!
Thank you!
Solved!
I managed to unbrick my phone.
If anyone needs it, the details are in the thread made by Manish54.
https://forum.xda-developers.com/mo...rick-moto-z-hardbricked-t3590133#post71876064
Is there any way to solve it ?
Hillterpty said:
Is there any way to solve it ?
Click to expand...
Click to collapse
Did you even read the posts?
Ajuda
martonto said:
I managed to unbrick my phone.
If anyone needs it, the details are in the thread made by Manish54.
https://forum.xda-developers.com/mo...rick-moto-z-hardbricked-t3590133#post71876064
Click to expand...
Click to collapse
Amigo tb estou com o meu morto, me ajuda, qual o modelo do seu.
https://uploaddeimagens.com.br/imagens/sem_titulo-jpg--9130
hard brick moto z
Manish54 said:
There ya go
https://forum.xda-developers.com/moto-z/how-to/guide-how-to-unbrick-moto-z-hardbricked-t3590133
Click to expand...
Click to collapse
hello friends, I'm with hard brick on the moto z xt1650-3
due to an update via ota, when my bootloader was unlocked I was in the android oreo (8.0), however I went back to 7.0, due to an update via ota, the device did not call anymore, I tried several blankflash and nothing, I am very annoyed at this, thinking of dropping my hand, I took some assists nobody can solve, I hope someone here can help me, at least inform me something that is useful to recover my cell phone.
my cell phone is still recognized as "qualcomm hs-usb qdloader 9008 (com3)
please join the telegram group:
https://t.me/motozz
Hey, my phone was dead two (brazilian xt1650-03), i spent three days struggling until i could bring him back. Thanks to the help in this forum. Your phone probably has the latest update opls27-76-51-7-july, so it must work:
first, you have to bankflash it with blankflash_OPL_27.76-51, its in the 30+ page topic tutorial here in this forum. Very important, must be in windows 7 or 8, with usb2.0
second, use this rom opls27-76-51-7-july-moto-z. it must work because its the last one. Its not brazilian, evething works fine but the netflix app didnt , but hey, at least our phone is alive again.
The secret is in the version of the firmware instaled before the brick, it must be the rom installed or latest to work