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
Related
Hey guys. I was going to post this on the Android Forums, but the L9 board there isn't getting hardly any traffic, so I suppose I'll just repaste here:
Hey guys, it's loopy time. xD
I've been through XDA, again, nobody seems to really have an answer for this, or even an answer for me. There's this guy over there named Kuma that made a stock 2nd-init locked bootloader ROM based off of 10e. I don't really desire to go back to it, but I like the fact that it comes with the xposed framework which you all know is an easy way to theme things that you should be able to theme, like making the status bar and notification area transparent.
I made a mistake in thinking that you can install Chainfire 3D on a locked BL, boy was I wrong. Two soft bricks later, I end up on 10d then do the OTA update to 10e. I've got the LG Mobile Support tool working as the offline flash. So I threw d on there and it worked....until I decided that I wanted to enable USB debugging.
There was a thread where I was advised to use Fastboot to flash the U and X boots, which I succeeded, but it wiped most of the partitions. At first I was panicking like...OMG, the family is going to worry because at this point I thought I was hard bricked, and my father is ill yada yada. So after about twenty minutes of crying and flipping out, I was able to get the USB for fastboot working with OMAP (which is tricky to install!) Three bottles of Pepsi Cola later, some chips, and a honey bun, I was able to get back to stock 10d.
Now, I've tried various drivers to try and get this thing to a go for ADB so I could root, install 2nd-init, and get Kuma's ROM back. I tried the updated drivers from the LG website. I have tried LG drivers 3.8.1.
The issue that I am having is that I am unable to access any of the connectivity modes while USB debugging is checked. If I uncheck it and try to plug it in, everything works perfectly. However, when USB Debugging is checked, no matter what connectivity mode I am on, I suffer with the LG Software coming up in autoplay and furthermore disconnecting after about ten seconds.
I tried in Ubuntu Linux to get it to work, and the same thing happens. This leads me to believe that either there is something wrong with the phone or something wrong with my computer, but other devices work. I'm really confused. Is there partitions for 10e MS769 MetroPCS that I can flash via fastboot to correct this? Is there another tool I can use to do this? I pretty much know fastboot is the key, but i'm going to need some assistance.
Hope you guys have an answer. I sure don't.
Please help me with this. I am familiar with fastboot maybe its a bad .bin file?
Assistance would be appreciated.
Thanks,
LoopyD
Bump.
Anyone?
Had the same problem, usb debug and any sort of adb connection doesn't work. Kuma comes to the rescue like the super hero he is and helped me fix it. Here is the post http://forum.xda-developers.com/showthread.php?p=49475336#post49475336 . Oddly enough this problem got worse for me I had it for about 3 months and it resulted in constant crashes and constant resets. Thank Kuma's post if it works!
Thank you sir. The ADB executable installer now shows the device. Problem solved.
Thanks
Sent from my LGMS769 using Tapatalk
The phone notified me there is a system update so I went ahead. Unfortunately, towards the end, it gave me an error message. I remember seeing the big Android robot lying flat on its back.
Now, the phone is completely dead. When I connect it to my computer I can hear the "new hardware connected" sound then immediately the disconnecting sound. This goes on and on for ever.
I tried using the tools provided on Leagoo's site, but they're useless as the computer is not able to recognize the phone.
Is there a hard reset key combination?
Thanks.
Eddie
silentmonolith said:
The phone notified me there is a system update so I went ahead. Unfortunately, towards the end, it gave me an error message. I remember seeing the big Android robot lying flat on its back.
Now, the phone is completely dead. When I connect it to my computer I can hear the "new hardware connected" sound then immediately the disconnecting sound. This goes on and on for ever.
I tried using the tools provided on Leagoo's site, but they're useless as the computer is not able to recognize the phone.
Is there a hard reset key combination?
Thanks.
Eddie
Click to expand...
Click to collapse
I've here 4 brick-phone (friends have updated with the same result!).
leagoo support didn't answer to my polite email of support.
Anyone can give us a sugestion to recover it!?
j045 said:
I've here 4 brick-phone (friends have updated with the same result!).
leagoo support didn't answer to my polite email of support.
Anyone can give us a sugestion to recover it!?
Click to expand...
Click to collapse
In the end, I was able to finally recover it. I just kept trying and trying: while the phone was connected to the computer, I removed the battery, then I put it back in; as well I was disconnecting it from the computer, then plug it back - I did this several times until the software on the computer was able to recognize it.
Even so, when I managed to reflash it, around 60%-70%, I got a message that it failed; so I tried again - it failed around 80% then I tried one more time and it was successful. Now the phone is working fine.
So my advice to you is to keep trying - leave the software on and click on the "download firmware" or whatever it was called, meanwhile keep unplugging the phone (and play with the battery as well).
Good luck! (you will need it)
Same problem, but leagoo responded with driver, firmware, flash tool, instructions and a video.
But nothing changed, so i have to retry.
Thanks for your post.
Edit:
I was thinking that was a hardware problem with micro usb connector!
ItalianWolf said:
Same problem, but leagoo responded with driver, firmware, flash tool, instructions and a video.
But nothing changed, so i have to retry.
Thanks for your post.
Edit:
I was thinking that was a hardware problem with micro usb connector!
Click to expand...
Click to collapse
i did it! just tried a lot of times, but firmware from leagoo doesn't work, display shows only "stipes".
I found another firmware (don't remember where) and then all things went good.
Now the phone notified me there is a system update, i have to do it?
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
So, I downloaded the OFFICAL kdz file from the OFFICAL LG website and when the program on my pc reached 100% the bar on my phone was at 99% I waited a minute before unplugging the device, after that It still didn't change screens on my phone so I removed the battery and put it back to find that I can't do anything. If I plug it into my pc it shows "Qualcomm hs-USB qdloader 9008". Any help will be appreciated.
Found out that it wasn't stock it was from MyLG(not related to the official LG)
Nevermind, just forget it. By the time someone reads the thread and posts the phone will be gone. what a damn waste of time.
MySQL_Syntax said:
Nevermind, just forget it. By the time someone reads the thread and posts the phone will be gone. what a damn waste of time.
Click to expand...
Click to collapse
Did you ever figure it out because I have the exact same problem.
It's been hardbricked for almost a month now. I've looked everywhere on how to unbrick this specific model on XDA but didn't find anything.
I know it's been done for models like the V10, G3, etc.. so I thought there might be some hope from bringing my phone back to life.
I goofed up accidentally installing the wrong ROM for the phone. It had TWRP and all but the phone won't turn on at all.
Does anybody have system dump files for the RS988?
CP100 said:
It's been hardbricked for almost a month now. I've looked everywhere on how to unbrick this specific model on XDA but didn't find anything.
I know it's been done for models like the V10, G3, etc.. so I thought there might be some hope from bringing my phone back to life.
I goofed up accidentally installing the wrong ROM for the phone. It had TWRP and all but the phone won't turn on at all.
Does anybody have system dump files for the RS988?
Click to expand...
Click to collapse
Hello!
When you say that the phone won't turn on at all, do you mean that the LG logo does not appear when you attempt to turn it on? In any case, your phone seems to be recognized by your computer, so download LGUP (with UPPERCUT) and see if they can communicate. You can flash the stock firmware using the .kdz files linked by @autoprime in his All-in-One G5 thread. I believe the firmware made for the RS988 Brightpoint (BPT) variant doesn't have anti-rollback protection, so you'll have the most luck flashing it. Make sure, though, if you go that route, to flash the non-carrier firmware afterwards.
NextDroid said:
Hello!
When you say that the phone won't turn on at all, do you mean that the LG logo does not appear when you attempt to turn it on? In any case, your phone seems to be recognized by your computer, so download LGUP (with UPPERCUT) and see if they can communicate. You can flash the stock firmware using the .kdz files linked by @autoprime in his All-in-One G5 thread. I believe the firmware made for the RS988 Brightpoint (BPT) variant doesn't have anti-rollback protection, so you'll have the most luck flashing it. Make sure, though, if you go that route, to flash the non-carrier firmware afterwards.
Click to expand...
Click to collapse
The Logo doesn't appear, after being plugged in to my PC, it just gets a little warm.
As for the LGUP with uppercut, I ran the program and it gives me a message of it saying "no handset connected". It is currently on COM3 in device manager named "Qualcomm HS-USB QDLoader 9008".
CP100 said:
The Logo doesn't appear, after being plugged in to my PC, it just gets a little warm.
As for the LGUP with uppercut, I ran the program and it gives me a message of it saying "no handset connected". It is currently on COM3 in device manager named "Qualcomm HS-USB QDLoader 9008".
Click to expand...
Click to collapse
Interesting. This reminds me of APX mode from the NVIDIA Tegra devices.
I think there's a Qualcomm-developed firmware flashing tool that can detect the device via the COM3 port. I cannot recall the name, but if you find it, you should give it a try.
I also have same issue flashed wrong Rom showing qualcomm 9008,complete black screen not even showing charging also,no recovery mode no download mode.is there any solution for it.
balu9999 said:
I also have same issue flashed wrong Rom showing qualcomm 9008,complete black screen not even showing charging also,no recovery mode no download mode.is there any solution for it.
Click to expand...
Click to collapse
I don't know if they exist. You need qfil and whatever firmware parts and edl recovery files. Your fire hose programmer for your chipset.
I've read some guys claim sd card method. But I've never done it on this device
Where you ever able to unbrick the phone?
I am currently experiencing the same issue, the best method that would seem to work so far is through QFIL but I can't find the firehose file.
same problem, any help?
CP100 said:
It's been hardbricked for almost a month now. I've looked everywhere on how to unbrick this specific model on XDA but didn't find anything.
I know it's been done for models like the V10, G3, etc.. so I thought there might be some hope from bringing my phone back to life.
I goofed up accidentally installing the wrong ROM for the phone. It had TWRP and all but the phone won't turn on at all.
Does anybody have system dump files for the RS988?
Click to expand...
Click to collapse
I have the exact same problem but i have the h850