Hi all,
Note: this method is not guaranteed (recommended as a last hope before thrown your phone into the trash) and should be performed only by an adult.
problem:
bricked my S5830 after downgrading to froyo.
black screen no showing what so ever (not even samsung logo,recovery or download mode).
tried couple of method ,nothing worked.
solution:
remove battery,SD and SIM card
place backside of the device near heating source (slight heating for half minute) such as hair dryer. put the battery back and press (volume down + power + home) to enter the download mode.
hope it will help somebody
regards,
WTF is this!!??
This looks kinda akward to do to your phone, and i dont think it will work, but if my phone gets bricked this will be my last try afyer all the other methods
Sent from my GT-S5830 using XDA App
is this really working?? coz i did really BRICKED my Ace!
but this sounds rediculious!
i need help!!
I hit the thanks button coz that post really gave me a laugh, but I'm with Jc_master it might get a try if I ever can't unbrick my ace!
This method DOES work, but you don't really need the heat source. Remove the battery, leave the phone alone for a minute, then while holding volume down + power + home insert the battery. If successful, you will see the download screen.
Otherwise, you may need to make a usb jig (youtube dot com /watch?v=Rdn5GoRjhn0) or just buy one from the guy in the video. I did both and now I have a sloppy 5 resistor (3 100K and 2 1K) electrical tape usb kludge job, and one of Mobile Tech Videos' slightly more professional fully plastic encased jigs.
that method is like forgetting the contents in the memory for a very fast way, through the use of heat, and reactivating some IC's.
Samsung service centre repaire it so not need to put phone in trash
so any one not know how to unbrick then safe way to go service centre
This sounds like the mobile equivalent of "banging it hard"
Would not advice the untechnical to follow this without seeking every other support first.
snuffdaddy1 said:
This sounds like the mobile equivalent of "banging it hard"
Would not advice the untechnical to follow this without seeking every other support first.
Click to expand...
Click to collapse
Stop bumping with unnecessary replies in the future, the OP already stated this:
gohn smith said:
Note: this method is not guaranteed (recommended as a last hope before thrown your phone into the trash) and should be performed only by an adult.
Click to expand...
Click to collapse
Hello, sorry about this but I'm pretty sure my cdma evo is hard bricked. The led starts as an extremely dim red when I try and start and then a few seconds later the led goes even dimmer to where it is barely visible. It shows up as QHSUSB_DLOAD when I connect it to my computer. It started 2 days ago when I was being very stupid reading some threads on here and read a line that was something like "Securityflag 3" to be entered with fastboot and so that's when all this started, me being curious and I think breaking my phone. Is there any way to fix it besides sending it to jtag repair?
Koonook said:
Hello, sorry about this but I'm pretty sure my cdma evo is hard bricked. The led starts as an extremely dim red when I try and start and then a few seconds later the led goes even dimmer to where it is barely visible. It shows up as QHSUSB_DLOAD when I connect it to my computer. It started 2 days ago when I was being very stupid reading some threads on here and read a line that was something like "Securityflag 3" to be entered with fastboot and so that's when all this started, me being curious and I think breaking my phone. Is there any way to fix it besides sending it to jtag repair?
Click to expand...
Click to collapse
If you used the writesecureflag command while using an "unofficial" HBOOT then you bricked your evo. Lucky for you, theres a fix for that type brick. Its the HTC unbricking project located here. Ive never used it so I cant help with instructions.
You should be more careful than you were being when you used that command. Fastboot commands can be very powerful and can screw your device up beyond repair. Good luck.
Wikd said:
If you used the writesecureflag command while using an "unofficial" HBOOT then you bricked your evo. Lucky for you, theres a fix for that type brick. Its the HTC unbricking project located here. Ive never used it so I cant help with instructions.
You should be more careful than you were being when you used that command. Fastboot commands can be very powerful and can screw your device up beyond repair. Good luck.
Click to expand...
Click to collapse
Well I had it s-off with the jopuonut wiretrick, Also found out something interesting, I bought it online nearly 9 months ago for 280 he claimed there was no problems, and I have it taken apart right now and the plastic tape holding the plugins for the screen into the mainboard is crumpled up, like the screen was replaced. There was a small dent and scratch on the cover when I got it so now I know why.
would it be stupid to think I could use another htc devices hardware to somehow fix it?
Well, I got my phone back to the bootloader! No longer bricked thankfully.
How>
Koonook said:
Well, I got my phone back to the bootloader! No longer bricked thankfully.
Click to expand...
Click to collapse
How did you unbricked your phone? Please Tell me
awaisdbz said:
How did you unbricked your phone? Please Tell me
Click to expand...
Click to collapse
I'm sure by following and using Unknownforce's universal tool as already suggested. It is in the development forum.
I tried to unlock bootloader in my D620r running V10g EUR firmware. It is unbranded G2 Mini bought in polish electronic store.
I used this instruction: http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
After all described actions, I'm left with some nice black brick :/
It does not power on, enter to download mode, hard reset, not even battery charging during phone is off - no animated battery screen.
The only reaction is when the battery is removed from the phone - then plugging in the USB cable results in screen, that battery was removed and question mark. That's all.
Phone is not recognized as any USB device, like it was not connected at all.
I tried to revive it with this instruction: http://forum.xda-developers.com/showthread.php?t=2582142 , but it didn't help. Linux does not see it - USB subsystem is not even triggered that something was plugged in.
Can anyone confirm this behaviour of D620r? What is your advice? Is any chance to revive my phone? Is flasing NAND at phone shack could help?
Try this (with G2 Mini files!):
http://forum.xda-developers.com/showthread.php?t=2582142
Vagelis1608 said:
Try this (with G2 Mini files!):
http://forum.xda-developers.com/showthread.php?t=2582142
Click to expand...
Click to collapse
I already tried, but as I wrote phone is not seen in Linux. Devices sdX<numbers> are not populating, there is nothing in the system logs,
USB driver does not see phone - there is no USB communication at all No LG logo, screen still OFF.
The same thing that happen to you, has happen to me as well.
Check my signature. I don't think there is any other way:/
Vagelis1608 said:
The same thing that happen to you, has happen to me as well.
Check my signature. I don't think there is any other way:/
Click to expand...
Click to collapse
Oh, I expected it. I'm about to send it to service like you. It's my first phone which I bricked that hard
Is your phone still at service now, or they repaired it for you some time ago? I think they will use some
kind of hardware box/flasher to flash firmware directly to EEPROM/NAND/NVM whatever sits there,
am I right?
twinsen.net said:
Oh, I expected it. I'm about to send it to service like you. It's my first phone which I bricked that hard
Is your phone still at service now, or they repaired it for you some time ago? I think they will use some
king of hardware box/flasher to flash firmware directly to EEPROM/NAND/NVM whatever sits there,
am I right?
Click to expand...
Click to collapse
It's been 2 weeks now.
Personally, I believe that they will simply sent a new phone. (They won't have to pay an employee to fix it and they will use the working parts as replacement parts for other phones - with them, nothing goes to waste )
BTW, don't tell them you did it. Tell them you don't know what happen
BTW, does anyone knows why there is a possibility to hard brick LG's that easy? What is wrong with some software mess? Is this some LG's mechanism to prevent phone modification? Some claims that only motherboard exchange in some hard brick cases is needed. Why? Can't service specialist just flash directly to chip?
twinsen.net said:
BTW, does anyone knows why there is a possibility to hard brick LG's that easy? What is wrong with some software mess? Is this some LG's mechanism to prevent phone modification? Some claims that only motherboard exchange in some hard brick cases is needed. Why? Can't service specialist just flash directly to chip?
Click to expand...
Click to collapse
If the aboot is broken, then the bootloader can get messed up.
You mean like JTAG? They don't seem to do that.
Sent from my GT-I5500 [CM11]
@twinsen.net I have d620r and I have used same instructions as you did. It worked like a charm.I now have unlocked bootloader, custom recovery and cm11. My phone is also locked on network.. Maybe you did something wrong?
Vagelis1608 said:
Personally, I believe that they will simply sent a new phone. (They won't have to pay an employee to fix it and they will use the working parts as replacement parts for other phones - with them, nothing goes to waste )
Click to expand...
Click to collapse
2 more weeks later...
I was right. LG sent a new phone as "they couldn't fix it" (as per their words).
So, they kept the battery, screen and etc, aka the parts people will pay to fix
I have a new LG G3 from Verizon I bought to replace my aging Motorola Droid RAZR M. It seems this one is a model "vs985K" which I have never seen mentioned before. It shipped with 47A Marshmellow, and conventional tot flash methods (using 35B dll and such) do not work. States "no ks version."
So I dd'd in the relevant partitions from the 35B bootstack, and TWRP as needed. It bricked the phone. Black screen. Nothing.
Fortunately, I am not a noob at this. I shorted the testpoints to get into qualcomm 9008 mode, and to my absolute horror, even BoardDiag 3.99 would not talk to the board. It seems this may be a new part number. Swapping some files from a another tool got it to finally flash, and I'm still trying to recreate what I did, but however I did it now I know I have a tool that can debrick it via qualcomm 9008 mode and so I'm ready to try again.
After some messing, it seems the exploitable aboot is what makes it brick. Unless I am missing something. Anyhow that's not the point of this post. The point of this post is to discuss this potential new variant, and how the heck to get this on 10B. Any ideas? It really seems tough if I can't use the exploitable aboot.
PS: I would post how to debrick a vs985K, but because it uses tools and software that is of questionable copyright status, I can't. PM me if you are desperate and maybe I can help you, though.
The K is probably just referring to the color. Is it black?
Some people get bricked doing what you did, others it works fine including me when I tested that method several times. I have a thread in the General section about that method. The title includes "KS Error".
When some people do something that causes the black screen, they're still able to go through the motions of putting it in Download mode and you can see its in that mode in Device Manager, and then able to flash either the 10B TOT (with downgraded partitions, there's a chance you wouldn't get the KS Error any more) or the 10B KDZ, since the downgraded partitions would now let you flash any KDZ you want.
As far as I know, everyone who tried that method - those who didn't brick and those who did, were able to downgrade to 10B via TOT or KDZ after. Read the thread for more details.
Yeah, I was following your post. It led to a black screen. I know I got all the partitions but I had to short the test pins and use qualcomm 9008 mode to get back.
I'll try again and report back. Don't see what I could've possibly missed though. I'm trying to get back to 10B in the end.
Back at the black screen. LG FlashTool for TOT method seems to not want to flash it even though I can "kinda" get it into download mode (it just doesn't show anything on screen, but registers in device manager)
See attachment.
KDZ Methods similarly fail with "upgrade stopped due to an error"
Currently sitting at qualcomm 9008 mode with boarddiag, so if you have any ideas of what to flash, I can do basically anything, lol.
It seems flashing aboot is the culprit. I can flash just about any other part of the bootstack without issue. Is it possible 47A is blowing a qfuse or something to prevent aboot downgrades?
I really couldn't speculate, I refrain from guessing. There's guesses out there covering at least a few possibilities, but the only circumstancial evidence is the "KS error" and the fact that some get the black screen, but it's weak evidence since I'm pretty sure that some who got the KS error were successful downgrading without a hitch, and I know for sure others who bricked were definitely able to recover.
I'd try a different PC. Using the original USB cable? Using a USB 2.0 port that comes directly off your PC's motherboard, and not a USB 3.0 port or a USB hub?
Do you have the right special drivers to use with BoardDiag?
As far as I know, I've never come across anyone who couldn't downgrade eventually, and all our VS985s have a letter after the model number signifying the color.
roirraW "edor" ehT said:
I really couldn't speculate, I refrain from guessing. There's guesses out there covering at least a few possibilities, but the only circumstancial evidence is the "KS error" and the fact that some get the black screen, but it's weak evidence since I'm pretty sure that some who got the KS error were successful downgrading without a hitch, and I know for sure others who bricked were definitely able to recover.
I'd try a different PC. Using the original USB cable? Using a USB 2.0 port that comes directly off your PC's motherboard, and not a USB 3.0 port or a USB hub?
Do you have the right special drivers to use with BoardDiag?
As far as I know, I've never come across anyone who couldn't downgrade eventually, and all our VS985s have a letter after the model number signifying the color.
Click to expand...
Click to collapse
Thanks. I didn't know about the extra letter, and mine is indeed black.
You've given me some leads to chase, if nothing else.
I'm not afraid to mess as I can debrick just about anything. First up on my list of things to try is a different USB port (I was using a USB 3.0 port).
Weird, after experimenting a lot, I find that the KDZ tool (from a fresh 47A install) let's me downgrade to 35B, but it ALSO gives me a black screen with similar behavior.
No idea what that means, but for whatever reason, it seems this device will not accept pre-marshmellow boot loaders.
http://forum.xda-developers.com/showpost.php?p=66096623&postcount=965
This does suggest a qfuse is blown by 47A. Unfortunately, it seems newer production phones like mine DO obey the qfuse, and I would furthermore speculate that LG/Verizon did this intentionally to cover these new phones.
The fact that mine can't flash (or rather can, but dies) a 35B KDZ, and was purchased fairly recently directly from Verizon (preflashed with 47A) all support this.
It looks like we may need to find an exploit for the marshmellow bootstack (or an outright bootloader unlock) if we want to unlock newer production phones. Unfortunately, I doubt this platform is new enough to attract devs with that kind of skill. However, I'm still here and willing to test any and all exploits, being if there's one thing I CAN do, it is unbrick a phone.
R-T-B said:
http://forum.xda-developers.com/showpost.php?p=66096623&postcount=965
This does suggest a qfuse is blown by 47A. Unfortunately, it seems newer production phones like mine DO obey the qfuse, and I would furthermore speculate that LG/Verizon did this intentionally to cover these new phones.
The fact that mine can't flash (or rather can, but dies) a 35B KDZ, and was purchased fairly recently directly from Verizon (preflashed with 47A) all support this.
It looks like we may need to find an exploit for the marshmellow bootstack (or an outright bootloader unlock) if we want to unlock newer production phones. Unfortunately, I doubt this platform is new enough to attract devs with that kind of skill. However, I'm still here and willing to test any and all exploits, being if there's one thing I CAN do, it is unbrick a phone.
Click to expand...
Click to collapse
@R-T-B For the sake of discussion and trying to add more content I will add to this post. What you experienced was similar to what I had...well sorta. I have 4 LG G3's in my family. The first of which was mine from over a year ago. I was able to use KDZ and TOT methods to do what was necessary in rooting and then taking advantage of the aboot exploit for the first 2. However, I want to say that the 3rd and 4th version of the VS985 gave me a few fits. It was the 3rd handset that I had received that my wheels were spinning with trying to downgrade using the TOT and KDZ methods. Eventually, TOT worked for me, but similar to you I had gotten into an issue where the black screen of death was upon me. It felt like the grim reaper had come to take my new handset... I swapped USB ports, cables, DLL's and through much hair pulling finally was able to recognize the phone properly with the TOT method and downgraded. I never really got the phone display to work... I went into download mode blind by using another phone as a guide. Regardless of all the trouble I finally achieved success. By the time my fourth handset came from VZW, VS985K, I was running into the LAF/KS ERROR. Used the same cables, ports, dll's, etc etc. NEVER was able to downgrade... The only method that worked as a last ditch effort was the afore mentioned. Speculation is certainly dangerous, but I would surmise that VZW maybe made some slight hardware changes. Perhaps a slight change in manufacturing of the IC of the motherboard...who knows. But certainly everything done here is at our own risk. I was willing to flash mine immediately, as falling back on the 30 day satisfaction guarantee was there from me.
b00ster23 said:
@R-T-B For the sake of discussion and trying to add more content I will add to this post. What you experienced was similar to what I had...well sorta. I have 4 LG G3's in my family. The first of which was mine from over a year ago. I was able to use KDZ and TOT methods to do what was necessary in rooting and then taking advantage of the aboot exploit for the first 2. However, I want to say that the 3rd and 4th version of the VS985 gave me a few fits. It was the 3rd handset that I had received that my wheels were spinning with trying to downgrade using the TOT and KDZ methods. Eventually, TOT worked for me, but similar to you I had gotten into an issue where the black screen of death was upon me. It felt like the grim reaper had come to take my new handset... I swapped USB ports, cables, DLL's and through much hair pulling finally was able to recognize the phone properly with the TOT method and downgraded. I never really got the phone display to work... I went into download mode blind by using another phone as a guide. Regardless of all the trouble I finally achieved success. By the time my fourth handset came from VZW, VS985K, I was running into the LAF/KS ERROR. Used the same cables, ports, dll's, etc etc. NEVER was able to downgrade... The only method that worked as a last ditch effort was the afore mentioned. Speculation is certainly dangerous, but I would surmise that VZW maybe made some slight hardware changes. Perhaps a slight change in manufacturing of the IC of the motherboard...who knows. But certainly everything done here is at our own risk. I was willing to flash mine immediately, as falling back on the 30 day satisfaction guarantee was there from me.
Click to expand...
Click to collapse
Yeah, examination of my PCB shows it is version "2" as well, suggesting maybe this isn't the first revision. Maybe they are getting smarter.
I tried to go through the prcoess of accessing download mode with the black screen but the phone was completely dead to all input and would not respond to LG flash commands anymore.
Don't get me wrong, I am not complaining I still have a phone afterall and I know this is all at my own risk. This may be speculation but I'd like to think it is educated speculation that a new hardware revision exists.
Is anyone else willing to open their phone to see if the top of their PCB (The part near the camera) has similar markings to mine? It is inscribed (in gold) "VS985 HW V1.0 (2)". Note the "(2)" that makes me think they revised it a second time.
I'm going to try to use boarddiag to flash the entirety of the TOT. Any reason why this would be a bad idea? Seems as good as any at this point to see if it truly can't run 10B.
This may take a very long time, but heck, why not try?
Did not work. I think we can safely say whatever variant I have, a pre marshmellow bootloader will never load.
R-T-B said:
Is anyone else willing to open their phone to see if the top of their PCB (The part near the camera) has similar markings to mine? It is inscribed (in gold) "VS985 HW V1.0 (2)". Note the "(2)" that makes me think they revised it a second time.
Click to expand...
Click to collapse
Is it necessary to disassemble the phone to expose that part of the pcb? Received my factory refurb vs985 two days ago, and am interested in rooting it. Just removed the back and don't see any part of the pcb.
Sent from my LG-D801 using Tapatalk
---------- Post added at 01:01 PM ---------- Previous post was at 12:57 PM ----------
SofaSpud said:
Is it necessary to disassemble the phone to expose that part of the pcb? Received my factory refurb vs985 two days ago, and am interested in rooting it. Just removed the back and don't see any part of the pcb.
Sent from my LG-D801 using Tapatalk
Click to expand...
Click to collapse
My device shows a mfr date of 10/26/15. Settings/about identifies as Rev 1.0, don't see any model reference numbers with "ks" suffix.
Sent from my LG-D801 using Tapatalk
I wouldn't advise disassembly to check for the markings unless you've already voided your warranty for some reason, but thank you for thinking of me and looking around your phone.
My advice to you would be to start by poking around the forums and looking up how to do a 10B TOT revert. You'll need the TOT file, and a .dll to go with it most likely. This is the safest way (if it works) to revert to firmware where you can get (and keep) root.
R-T-B said:
I tried to go through the prcoess of accessing download mode with the black screen but the phone was completely dead to all input and would not respond to LG flash commands anymore.
Click to expand...
Click to collapse
Could you clarify something? Have you been able to recover from the black screen issue? I was under the impression you have but now I'm not sure.
roirraW "edor" ehT said:
Could you clarify something? Have you been able to recover from the black screen issue? I was under the impression you have but now I'm not sure.
Click to expand...
Click to collapse
Yes, I recovered, but it was complicated.
First off, I had to use a modified version of BoardDiag (I can upload this if anyone needs it, but I'm unsure as to it's legal status) with the qualcomm drivers and testpoint shorted. Second, I had to reflash the 47A files via that method, anything lower than 46A will brick it again.
All in all, it's pretty messy to recover from what I did, but I was confident enough that I've probably done it 4 times now... unfortunately all without success reaching anything below 46A. Even a 35B flash bricks it.
I have a vs985wk, just recently purchased. I believe that the 'W' is for the color, which is white.
SofaSpud said:
I have a vs985wk, just recently purchased. I believe that the 'W' is for the color, which is white.
Click to expand...
Click to collapse
Interesting. What's the "K" mean then?
R-T-B said:
Interesting. What's the "K" mean then?
Click to expand...
Click to collapse
Good question! After reading your posts I looked around a bit for info re the 'k' but didn't find much.
I have yet to root (or even carrier activate) mine. I just received the Totalwireless similar today, but am thinking that perhaps I shouldn't activate until after rooting and disabling OTA, in hopes of avoiding further lock down against rollback. Device is rollback level 2, FW 47A.
Sent from my LG-D801 using Tapatalk