Showing posts with label hardbricked. Show all posts
Showing posts with label hardbricked. Show all posts

Saturday, 10 October 2015

[HOW TO] Fix your hard-bricked LG G2



DISCLAIMER These methods were not found by me. I am just simply making a noob friendly guide.
Okay guy's I'm back with a guide on how to recover your cellphone from a hard brick. Apologies for the late thread.
This means your phone is the following:
- completely black doesn't turn on
- doesn't display anything on the screen
- qhsusb_bulk mode
- and lastly Qualcomm HS-USB QDLoader 9008

Notes:
1. You DO NOT need to pry open your cellphone
2. This method is for 9008 mode, I am not sure about 9006 mode.
3. You don't need no VM (virtual machine) or Windows XP machine. I got mine working on Windows 10 Enterprise 64-bit
4. Most tutorials/guides don't include the first part of this one and about turning off your phone
5. If after you have completed all the steps and your phone is still not booting into the interface but you do see the LG G2 logo
please follow the steps on my other tutorial/guide that I made here

Prerequisites:
A) Qcomm Drivers (Virus Scan)
B) BoardDiag v2.99a (Virus Scan)
C) Choose your phones correct TOT model here or here
D) Make sure you have Visual C++ Redistributable Packages and or system libraries installed (Only if you can't open BoardDiag program)

1. Install the Qualcomm Driver









After you installed the driver, you should see qhsusb_bulk mode turn into Qualcomm HS-USB QDLoader 9008




2. Open up BoardDiag & extract the .TOT file which makes a partition.txt file that you need. Once the extraction is finished you will notice another window open up that says "complete"




Extracted files will look as such




3. Now change the following:



- AP Chipset (PICK the right model for your cellphone)
- Choose the correct port (the port you saw once you installed the driver)
- Change the "Target Dir" (to where ever you extracted your .TOT file)
- AP check (check mark it)
- EMMC TEST (check mark it)
- SDRAM TEST (possibly optional but I had mine checked)





4. THIS STEP IS IMPORTANT



BEFORE you click "start" You need to unplug your cellphone and make sure it is off.
now you are probably saying "it is off, because its not displaying anything" that's not true. Make sure its off by pressing the power button for 1 minute.
After you have done that, Hold down the volume + (Volume up) then plug in your phone to the USB. Then click start
OTHERWISE
you will see this error




5. After you have done everything above correctly you will see something like the image below (which is my image after I fixed my hard-bricked phone)







That's it guys & gals after you have done all of these steps you will have a full working cellphone once more! enjoy!



[Q] Moto E X1025 Hard-Bricked, Solutions?



i can't do a blankflash without programmer_8210.mbn and singleimage_8210.bin , does anyone has those files?



Thursday, 8 October 2015

Phone hardbricked after following "[Solved] Secure Boot Error" thread. What do I do?



I followed the one click root method, which worked out well. After that, I installed su, flashify, and twrp. I then tried installing a custom rom, but upon booting into recovery mode, I received the Secure Boot Error text. It wasn't too big of a deal since I could still take out the battery, put it back in, and boot normally.
But, after seeing this thread:
http://forum.xda-developers.com/lg-g...-boot-t3054977
and how simple the instructions were, I proceeded to give it a shot. I entered in the 4 commands, powered off my phone, and attempted to boot into recovery mode. But unlike before when I booted into recovery mode, nothing appeared. No lg logo, backlight power, nothing. It's acting exactly as it would as if there wasn't anything powering. Now I'm stuck with a bricked phone, and sincerely need some advice on where to proceed next. Could someone help me?

Oh, btw, when I plug the phone the computer, I do "the device was successfully installed" message. The phone appears in device manager, under Ports as LGE AndroidNet USB Serial Port or as LG AndroidNet Phone under devices and printers. It doesn't appear under This PC at all.



Wednesday, 7 October 2015

Hardbricked Nexus 7 Deb (QHSUSB_DLOAD problem)



I've had my Nexus 7 for a while, and I actually recently got a Nexus 10 and handed off the 7 to my fiance, who was using it to browse tumblr and read fanfiction, and that's about it as far as I can tell. I do have it rooted and unlocked and running Paranoid Android Beta 4.6 (and has been for a very long time), however since I haven't messed with it in so long I couldn't tell you anything else about it (kernel, etc.)

Since I know she wouldn't have tried to do anything like update or anything like that, my guess is that the problem is stemming from the fact that she just lets it die a lot, then charges it. She charged it all night and it would not turn on so she had me look at it. I tried everything I could think of, holding power for various amounts of time, both alone and in combination with either of the volume buttons to try to access fastboot or just anything. I should mention I even followed Google's troubleshooting steps, which involved strange charging times, having it plugged into the PC for a spell, then unplugging and replugging and trying to power on. But the battery icon does not even show up. The screen just stays black.

I plugged it into my computer to see if anything would happen, and it showed up in Device Manager as QHSUSB_DLOAD, so I googled this problem and it seems to be some sort of hardbrick where the bootloader is corrupted, and some people have found solutions for other devices, mainly HTC devices, but there doesn't seem to be anything that particularly pertains to this device. If I hold down the power button while plugged into the PC it will intermittently "disconnect" and "reconnect" (Windows plays the sounds) and disappear and reappear in Device Manager.

I'd like to try to fix it if I can, but I'm not gonna send it in for repairs/replacement or anything like that. I'd rather just buy a brand new device at that point, but if anyone somehow has a solution, I'd gladly welcome it.

Thanks so much!