Related
Hi Guys,
I need your elp in resolving a problem that has been racking my brain for the last month.I have a Lumia 900 that came with 7.8104 (http://twhitpic.com/bbp85o) which has a Qualcomm bootloader.
I have tried updating it to Tango using Zune, but Zune says that my current software version is the latest.I even used the Zune "disconnect network to force update" trick with zero results.
I have tried flashing in new Fimware using Nokia Care Suite but the phone is not recognized by the Product Support Tool (I even tried USB Dead Flash with no results).
I have tried pushing in 8779 cabs with their languages using WP7 Cab Sender, but i keep getting 8018400D error right at the end of the flash process. (http://twitpic.com/bbnho2) (http://twitpic.com/bbn0p2)
I don't know what i should do now..
The only thing I can think of to resolve this problem is using the back up files of an updated Lumia 900 to restore my devices to the latest OS version. The process would be as follows:
Someone who has an unlocked Lumia 900 hard resets their device then backs it up (this way no personal data is saved in the backup)
They then share this back up file with me.
I restore my Lumia 900 using this back up file.
Will this update my phone to Tango (8779)? If so, would anyone be willing to help me out with their backup file?
Thanks.
Hmm... Try to hard reset your lumia (switch off, then Camera + Vol Down + Power button). After that try to flash it with Care Suite. Your problem may be caused by computer problem, so I recommend you to do this on another PC.
valuxin said:
Hmm... Try to hard reset your lumia (switch off, then Camera + Vol Down + Power button). After that try to flash it with Care Suite. Your problem may be caused by computer problem, so I recommend you to do this on another PC.
Click to expand...
Click to collapse
Thanks for the suggestion, but I've already done Hard Reset several times and tried flashing on 3 different laptops (2 x64 and 1 x32) with the same result.
My remaining hope will be the release of HSPL for the Lumia900
The qualcomm bootloader is probably the problem, and heathcliff already said there's nothing they can do even with the qualcomm bootloader for the community. So, I'd just send it in to Nokia at this point.
Hello all.
Yesterday i was using my XDA App on my XZL and somehow the xda app mislead me to some Samsung subforum instead of the ZL original Android Development Forum where i surely clicked on that. Then i thought there was a new rom... downloaded and flashed with no errors inside NUT's Recovery and then it turned into a brick. So no response from my ZL no charging LED, there is no way to go into Fastboot or Flashmode. It will be always recognized as QHSUSB_DLOAD in windows.
What i tried is a tool for linux from here http://unlimited.io/qhsusbdload.htm and at the end it says qdl reset but its still bricked. So i dont know what to do anymore. Oh and i never Unlocked my ZL i just had Exsistenz 5.0.0 Rom installed on it.
What happens when you connect it with your pc, does your computer still recognize it as a phone? Did you try to use pc companion repair function?
when i connect it will be seen as QHUSB_DLOAD, PC Companion and SEUS dont see the because of that.
have you tried the reset button? press it and hold it in and you should feel one vibration after a few seconds....keep holding it untill it vibrates 3 more times and it should turn it off/reset it.
then try using flashtool.
Yeah i tried the reset button but its not working anymore its not even vibrating. It seems its complete dead.
there is one thing i could do, to rewrite the phone through QPST from qualcomm but i dont have the files for my phone, so i would need a backup from an c6503 from QPST
just a thought...there was a time or two when just pressing the rest button did not work for me, what i had to do was hold in the power button at the same time as pressing the reset. hold them both till you feel one vibration, keep holding till you feel 3. sorry if thats no help.
i Tried that but dont works too. Now i startet again ubuntu and did try the QHSUSB fix, so the ZL will be recognized as qualcomm modem blabla QDL mode that means qualcomm download mode. So when i do the qhsusb fix it will exit the qdl mode and try to reboot, but there are no partitions anymore on the phone so the phone enters again in QDL mode. When it exits QDL mode it will be connected as Qualcomm inc. in Ubuntu. at this time the Red led flashes for a few seconds until it gets back to QDL mode.
When the phone is unplugged and i press Power button one single time then the Led flashes 3 times Red, when i plug it in at the charger it flashes 1 time for maybe 1 second in Red, but doesnt start to charge. Then it seems to hang up so i need to press the reset button and it goes to QDL mode again, thats all i found out now. And sorry for my bad english
I hope some Dev could help me.
Now i found and Linux app called emmc_recovery which i can flash some .sin files some succesfull with no errors and some files abort. so i need an bootloader for my zl c6503 doesnt matter what file type it is. So how can i find one ?
Sorry, I can't help you. But there is a threat called Disaster Recovery. It's created by NUT, the dev who created the dual recovery for our phone. Since that threat covers ZL, Z and other Xperia-phones, many more people will read it. Maybe you can get help there:
http://forum.xda-developers.com/showthread.php?t=2229250
Sorry, but your phone is hard bricked. I experienced the exact same issue on my Xperia T. The only fix is through JTAG, or send it back to Sony and hope they replace it.
Sent from my Nexus 10 using XDA Premium 4 mobile app
Yeah i will sent it to repair center and it was my first and last sony phone. Will go back to HTC.
Vendetto said:
Yeah i will sent it to repair center and it was my first and last sony phone. Will go back to HTC.
Click to expand...
Click to collapse
So you somehow through your own ineptitude or ignorance attempted a flash of Samsung software on a Sony phone and it bricked.....and you blame Sony? Interesting.
TAL333 said:
So you somehow through your own ineptitude or ignorance attempted a flash of Samsung software on a Sony phone and it bricked.....and you blame Sony? Interesting.
Click to expand...
Click to collapse
Where i ever blamed sony for my fault ?? And where i am ignorant ? You seem a typical troll.
If the XDA App would lead me to to right forum this would never ever happen. I flashed thousand times and never had a brick with my HTC One X. You can say what you want but the quality of Sony is far behind.
In my case, I flashed a custom Xperia T kernel from a dev who modified S1_BOOT and the bad flash put my phone in the QHSUSB_DLOAD mode. I tried absolutely everything and nothing worked, the phone was completely bricked. Now, if this can happen with a bad flash from Sony, imagine the havoc cross flashing device manufacturer's causes! Samsung software on a Sony platform? It's deader than dead.
Hello all,
Well, it's here... Unfortunately my phone got bricked last night
Can't boot into main screen and can't go to download mode anymore. The cause is, my phone was stuck when upgrading firmware and there's nothing to do about it except remove the battery, and then, BOOM!... "Secure Booting Error! Cause: boot certification verify"
Any LG G3 users here already experienced this problem?
I followed the solution on LG G2 sub-forum, but my ubuntu doesn't detect the port, although Windows recognized it.
If this happens to your G3 and you solved it, please share your experience
Thanks
haris182 said:
Hello all,
Well, it's here... Unfortunately my phone got bricked last night
Can't boot into main screen and can't go to download mode anymore. The cause is, my phone was stuck when upgrading firmware and there's nothing to do about it except remove the battery, and then, BOOM!... "Secure Booting Error! Cause: boot certification verify"
Any LG G3 users here already experienced this problem?
I followed the solution on LG G2 sub-forum, but my ubuntu doesn't detect the port, although Windows recognized it.
If this happens to your G3 and you solved it, please share your experience
Thanks
Click to expand...
Click to collapse
Help me too
haris182 said:
Hello all,
Well, it's here... Unfortunately my phone got bricked last night
Can't boot into main screen and can't go to download mode anymore. The cause is, my phone was stuck when upgrading firmware and there's nothing to do about it except remove the battery, and then, BOOM!... "Secure Booting Error! Cause: boot certification verify"
Any LG G3 users here already experienced this problem?
I followed the solution on LG G2 sub-forum, but my ubuntu doesn't detect the port, although Windows recognized it.
If this happens to your G3 and you solved it, please share your experience
Thanks
Click to expand...
Click to collapse
If Windows recognizes it then try using LGflashtool again.
Sent from my LG-D851 using Tapatalk
Skizzy034 said:
If Windows recognizes it then try using LGflashtool again.
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
Windows does not recognize the phone...
Skizzy034 said:
If Windows recognizes it then try using LGflashtool again.
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
Not at all.
Finally, I claimed my warranty with LG, and the motherboard got replaced.
It's all working now
You could have unbricked it... I've done that twice already
im stuck in this, how?
I'm stuck at the same thing since yesterday.
could you tell us the solution @nofait?
I've been researching about this and noticed one thing,
if I hold the lg combo (vol up + usb cable), and keep holding it until it passes the secure boot error and the screen becomes black,
my device (d855) goes to the Qualcomm Download Mode (it's detected as ''Qualcomm HS-USB QDLoader 9008'' on windows 8.1 x64)
Apparently, on that mode we could use Qualcomm tools (QPST) to reflash the bootloader and the matching laf image (the one that brings up the download mode)
so we could then flash any KDZ using LG Flash Tool.
To do so we need to extract the bootloader files, sbl1.bin, aboot.bin, rpm.bin, tz.bin, boot.bin, and laf.bin, from a tot/kdz firmware converting them to mbn format.
Then using QPST eMMC Download Tool, we load the partition table xml and 2 image files: the flash programmer file and the qcom boot image, which I'm still trying to figure out where to get them since I can't dump my own phone, and then we might be able to recover it.
I'm still looking into it and hopefully we can find a way.
I did not send my phone to lg service, yet, because I think they will take too long to fix it.
It happened to me a few days ago, but i had TWRP fully working so i could simply flash a ROM and then recover my things.
That thing about windows recognizing it as a msm8474 was a drivers issue (al least for me), i have a S5 too, i think that when i was tryng to get Heimdall working it changed the drivers (as you may know, s5 and g3 have the same board), so i just simply uninstalled it and then reinstall everything using .exe files from LG's website, after that windows 8.1 recognize it perfectly and i could flash KDZ without problems.
Other experience i had and that may help is what happened to me using an LGOG, couldn't boot, no recovery, no nothing, just trying to turn it on, it managed to get in fastboot mode (but with screen off and red LED all the time),from that point it was just about typing commands and flashing img to get it working
diego-ch said:
I'm stuck at the same thing since yesterday.
could you tell us the solution @nofait?
I've been researching about this and noticed one thing,
if I hold the lg combo (vol up + usb cable), and keep holding it until it passes the secure boot error and the screen becomes black,
my device (d855) goes to the Qualcomm Download Mode (it's detected as ''Qualcomm HS-USB QDLoader 9008'' on windows 8.1 x64)
Apparently, on that mode we could use Qualcomm tools (QPST) to reflash the bootloader and the matching laf image (the one that brings up the download mode)
so we could then flash any KDZ using LG Flash Tool.
To do so we need to extract the bootloader files, sbl1.bin, aboot.bin, rpm.bin, tz.bin, boot.bin, and laf.bin, from a tot/kdz firmware converting them to mbn format.
Then using QPST eMMC Download Tool, we load the partition table xml and 2 image files: the flash programmer file and the qcom boot image, which I'm still trying to figure out where to get them since I can't dump my own phone, and then we might be able to recover it.
I'm still looking into it and hopefully we can find a way.
I did not send my phone to lg service, yet, because I think they will take too long to fix it.
Click to expand...
Click to collapse
Hi,
You'll need to use a Windows 7 machine and the proper LG USB Driver (first post of this message) and change it to the COM41.
Do a BOARD DL and when the screen comes up and tells you to not touch it, ignore and press OK. Then press the power button and at the same type touch the "Normal +power". It should reboot and everything should be fine
Cheers!
nofait said:
Hi,
You'll need to use a Windows 7 machine and the proper LG USB Driver (first post of this message) and change it to the COM41.
Do a BOARD DL and when the screen comes up and tells you to not touch it, ignore and press OK. Then press the power button and at the same type touch the "Normal +power". It should reboot and everything should be fine
Cheers!
Click to expand...
Click to collapse
So,
Should I use windows 7 32 bit or is it fine with 64 bit?
Will I need a .TOT file and a DLL for my model ( D855P 16gb ) or can I use a KDZ file?
EDIT: ok so I tried it, but flash tool failed to get model information from the phone.
were you in download mode? I can't get to download mode here.
diego-ch said:
So,
Should I use windows 7 32 bit or is it fine with 64 bit?
Will I need a .TOT file and a DLL for my model ( D855P 16gb ) or can I use a KDZ file?
EDIT: ok so I tried it, but flash tool failed to get model information from the phone.
were you in download mode? I can't get to download mode here.
Click to expand...
Click to collapse
I send my phone to warranty service, where they changed all the motherboard with new IMEI and SN.
Hope that they don't ask for money to repair the phone.
hi all, having this problem as well. anyone resolve this?? Need help!
[/COLOR]
nofait said:
Hi,
You'll need to use a Windows 7 machine and the proper LG USB Driver (first post of this message) and change it to the COM41.
Do a BOARD DL and when the screen comes up and tells you to not touch it, ignore and press OK. Then press the power button and at the same type touch the "Normal +power". It should reboot and everything should be fine
Cheers! .
Click to expand...
Click to collapse
hi thanks for idea but could you explain in detail because is not working on my end. what screen comes up? i get ready in com41 . then download fail! (0 sec)
---------- Post added at 11:29 AM ---------- Previous post was at 11:26 AM ----------
paolotheking said:
I send my phone to warranty service, where they changed all the motherboard with new IMEI and SN.
Hope that they don't ask for money to repair the phone.
Click to expand...
Click to collapse
did you get it back?
prana_Sky said:
did you get it back?
Click to expand...
Click to collapse
Yes, with new mainboard.
prana_Sky said:
hi all, having this problem as well. anyone resolve this?? Need help!
Click to expand...
Click to collapse
I have the same problem did you find any solution ?
edit: solved somehow
First of all my english is terrible
I downloaded and successfully installed the kasha malaga android into my nokia x,I opened it and tried to open the play store but it keeps force closing i tried everything the internet said but nothing worked so i decided to try reinstalling it. i went to the setting and factory reset my nokia x. when i turn on my phone it of course let me to the setup wizard.but when i accepted to choose English as my primary language and press next and then a pop up comes out saying that setup wizard has stopped working and then it restart the setup wizard process so basically im stuck there. the only way i can acess my setting is open wifi let it sense and then press the available wifi network. then it takes me to wifi setting from there i can back and be at the settings!i even tried hard reset that didn't work..... and the worst part is my computer cannot sense my phone through usb cable. Pls help im desperate!
try this
you can follow the steps here http://forum.xda-developers.com/showthread.php?t=2668005
files are here http://forum.xda-developers.com/showthread.php?t=2779284
bryanjay420 said:
you can follow the steps here http://forum.xda-developers.com/showthread.php?t=2668005
files are here http://forum.xda-developers.com/showthread.php?t=2779284
Click to expand...
Click to collapse
that was my answer to all.. but my phone can't detect my computer or any computer. Is there a way to flash using the sd card on the normal recovery that nokia gave?
Whiteshockwave said:
that was my answer to all.. but my phone can't detect my computer or any computer. Is there a way to flash using the sd card on the normal recovery that nokia gave?
Click to expand...
Click to collapse
use updated usb driver by dom at the general thread. then flash stock rom by using nokia x flasher. maybe it should work
Whiteshockwave said:
that was my answer to all.. but my phone can't detect my computer or any computer. Is there a way to flash using the sd card on the normal recovery that nokia gave?
Click to expand...
Click to collapse
i also having problem with the usb drivers. in the device manager i cant install updated drivers for my xl (it shows Exclamation point) but nokia x flasher can detect it in fastboot mode (holding power button + volume down for 15 seconds) then i connect my phone to my pc
hard reset
You can try hard reset by hard key
none of the above worked. Looks like my phone is a goner
Don't be so negative. I has bricked my phone but I recovered it and its fully working now. Just flash your phone with stock rom via nokia care suite and your phone will be as good as new.
Sent from my Nokia_XL using Tapatalk
anubhav_143 said:
Don't be so negative. I has bricked my phone but I recovered it and its fully working now. Just flash your phone with stock rom via nokia care suite and your phone will be as good as new.
Sent from my Nokia_XL using Tapatalk
Click to expand...
Click to collapse
and dont forget to make backup always...almost bricked my phone lot of times by installing custom rom but still managed to recover by flashing backups from different recoveries of it that didnt work flash with stock rom
Hello folks, I'm developer for embedded and I see that many persons have a problem with the driver QHSUSB_BULK.
This is a RAW driver in the Lumia phones differently the reason to occur the Android phones, in android phones is indicate a usually problem in partitions, but the bootloader is intact, in windows mobile, this index indicate a series of extreme problems in the ROM and bootloader, but if the driver can be installed with the windows device recovery tool, its ok, your phone can be repared using the thor2 option in the WDRT, but if the phone dont recognized and the driver can't be installed, the driver stay QHSUSB_BULK, the phone is dead, just using JTAG to recovery the ROM and the bootloader together, bcz in windows phone the partitions are different that the present in android, in android the partitions are in stuff like a computer and the bootloader controls the boot (like a BIOS n POST in PC), but in windows mobile the bootloader is incremented in ROM, how the windows 8.1 boot in PC, it is an auto control inside the system.
Well guys, its a explanation why someone can recovery the phone and another cannot to do.
My lumia is full-bricked too, bcz the windows 10 was upgraded yesteday, just remember folks, who are using the W10M disable the auto-upgrade, its is brick a lot of lumias. The upgrade can be doing, but first give a rollback in cellphone using the WDRT.
Best regards friends.
rogjr8086 said:
Hello folks, I'm developer for embedded and I see that many persons have a problem with the driver QHSUSB_BULK.
This is a RAW driver in the Lumia phones differently the reason to occur the Android phones, in android phones is indicate a usually problem in partitions, but the bootloader is intact, in windows mobile, this index indicate a series of extreme problems in the ROM and bootloader, but if the driver can be installed with the windows device recovery tool, its ok, your phone can be repared using the thor2 option in the WDRT, but if the phone dont recognized and the driver can't be installed, the driver stay QHSUSB_BULK, the phone is dead, just using JTAG to recovery the ROM and the bootloader together, bcz in windows phone the partitions are different that the present in android, in android the partitions are in stuff like a computer and the bootloader controls the boot (like a BIOS n POST in PC), but in windows mobile the bootloader is incremented in ROM, how the windows 8.1 boot in PC, it is an auto control inside the system.
Well guys, its a explanation why someone can recovery the phone and another cannot to do.
My lumia is full-bricked too, bcz the windows 10 was upgraded yesteday, just remember folks, who are using the W10M disable the auto-upgrade, its is brick a lot of lumias. The upgrade can be doing, but first give a rollback in cellphone using the WDRT.
Best regards friends.
Click to expand...
Click to collapse
rogjr8086,
I have the exact same problem on my Lumia 640 LTE RM-1073. I have tried everything and nothing has worked. I have spent countless hours and days. I finally decided to call Microsoft and get warranty service, and what a pain even that was. First to get a hold of the right person/phone number was a royal pain, but finally got someone on the phone for Windows Phone support: (888)665-4228 and (800)246-6542. Turns out there is a 1 year warranty on all Windows phones. So they had me go to https://www.microsoft.com/en-us/mobile/support/warranty-checkers/. Only problem was when I would enter my IMEI number it said it was out of warranty, yet I bought it from the Microsoft store. So while on the phone the agent took my info, sent me an email and I had to take screen shots of my order email from November of last year and email the screen shots back to him. I now have to wait 2-4 days to get a result from the warranty dispute and supposedly a shipping label. If it was out of warranty, it would be about $45 to get repaired from what another agent had said. Either way, hope some of this info helps someone else as it truly was a pain to just get a hold of someone at MS. I would love to fix the phone in the meantime, but I just cannot get it to boot not matter what I try.
Thanks,
Jim
rogjr8086 said:
Hello folks, I'm developer for embedded and I see that many persons have a problem with the driver QHSUSB_BULK.
This is a RAW driver in the Lumia phones differently the reason to occur the Android phones, in android phones is indicate a usually problem in partitions, but the bootloader is intact, in windows mobile, this index indicate a series of extreme problems in the ROM and bootloader, but if the driver can be installed with the windows device recovery tool, its ok, your phone can be repared using the thor2 option in the WDRT, but if the phone dont recognized and the driver can't be installed, the driver stay QHSUSB_BULK, the phone is dead, just using JTAG to recovery the ROM and the bootloader together, bcz in windows phone the partitions are different that the present in android, in android the partitions are in stuff like a computer and the bootloader controls the boot (like a BIOS n POST in PC), but in windows mobile the bootloader is incremented in ROM, how the windows 8.1 boot in PC, it is an auto control inside the system.
Well guys, its a explanation why someone can recovery the phone and another cannot to do.
My lumia is full-bricked too, bcz the windows 10 was upgraded yesteday, just remember folks, who are using the W10M disable the auto-upgrade, its is brick a lot of lumias. The upgrade can be doing, but first give a rollback in cellphone using the WDRT.
Best regards friends.
Click to expand...
Click to collapse
Drivers should be perfectly installed, otherwise phone can't detect ,it will leads to brick phone ,when some thing goes wrong & driver not detect the device,thankfully dell drivers for usb 3.1 for 950/xl working perfectly, when other drivers not working,uninstall all usb drivers /portable device ,install dell drivers works perfectly .dell drivers usb 3.1 Link
vecdid said:
rogjr8086,
I have the exact same problem on my Lumia 640 LTE RM-1073. I have tried everything and nothing has worked. I have spent countless hours and days. I finally decided to call Microsoft and get warranty service, and what a pain even that was. First to get a hold of the right person/phone number was a royal pain, but finally got someone on the phone for Windows Phone support: (888)665-4228 and (800)246-6542. Turns out there is a 1 year warranty on all Windows phones. So they had me go to https://www.microsoft.com/en-us/mobile/support/warranty-checkers/. Only problem was when I would enter my IMEI number it said it was out of warranty, yet I bought it from the Microsoft store. So while on the phone the agent took my info, sent me an email and I had to take screen shots of my order email from November of last year and email the screen shots back to him. I now have to wait 2-4 days to get a result from the warranty dispute and supposedly a shipping label. If it was out of warranty, it would be about $45 to get repaired from what another agent had said. Either way, hope some of this info helps someone else as it truly was a pain to just get a hold of someone at MS. I would love to fix the phone in the meantime, but I just cannot get it to boot not matter what I try.
Thanks,
Jim
Click to expand...
Click to collapse
do you realize that phone is worth around that 45$ unlocked on ebay in almost new condition? heck I just bought a 830 unlocked for a friend at 60$ and it came with an almost invisible scratch on a corner
Guys..i quick question before i give up on my lumia 640 RM-1077. The device is completely dead and when connected to PC it reads as QHSUSB_BULK. Is there any which way to recover the device? I understand from your discussion here that there is no hope when a Lumia encounters that message.. but just wanted to confirm it before giving up on bringing it back to life.
lumia 640 RM-1075 QHSUSB_BULK
I have the same problem with my lumia 640 RM-1075.