Develop Bugs

[Q] Bricked T999L Failed Bootloader update

Hi! I need some serious help. I accidentally bricked my phone while updating the Bootloader.
It's a Samsung Galaxy S3 SGH-T999L (T-Mobile, but it works with my Vodaphone SIM)
Absolutely nothing on the screen, no boot, no recovery mode (just installed CWM), no download mode. Just a red LED when plugged in via USB.
Device Manager shows this: "QHSUSB_DLOAD"
I live in Egypt so there's no such thing as 'insurance' or 'warranty'.
I tried the instructions here: http://forum.xda-developers.com/showthread.php?t=2439367
Didn't work.
Is this the end? Or is there yet hope for it?

Need to know the details of what you flashed and what steps you followed.
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
Need to know the details of what you flashed and what steps you followed.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I just installed the CWM custom recovery via Android Toolkit, and was preparing to flash Cyanogen. It said that an S3 needed a Bootloader update to install Cyanogen versions greater than 10.1, So I followed the links and I think I accidentally flashed the Bootloader for SGH-T999 (not the T999L).
CWM said it succeeded, rebooted the phone (did not fix root when it asked), and it just never turned on since (it's been a while)

P.s: Idk if this even matters when its as deep as the Bootloader, but the phone had been rooted for months before.
Oh, and I found this and am downloading the latest T999L in case I need it if ODIN can help: http://forum.xda-developers.com/showthread.php?t=2439367
And from yet more Google I found these drivers, but it won't let me post outside links
But Device Manager says "Driver is not intended for this platform."
That's all I got so far, will keep looking for a good driver and check this thread as often as I can

This is gonna probably sound stupid, but I tried an emergency recovery with Kies, but it needed me to get it in Recovery Mode.
No change so far. Any help finding the right drivers would be very helpful.

Kygies27 said:
This is gonna probably sound stupid, but I tried an emergency recovery with Kies, but it needed me to get it in Recovery Mode.
No change so far. Any help finding the right drivers would be very helpful.
Click to expand...
Click to collapse
YAY! Found working drivers here: http://forum.xda-developers.com/showthread.php?t=1536354&page=4
By: richardlibeau
ATTACHED FILES
File Type: zip QHSUSB_Drivers_(x64).zip - [Click for QR Code] (72.3 KB, 568 views)
File Type: rar qhsusb_dload_Drivers.rar - [Click for QR Code] (56.0 KB, 584 views)

More Google (Where is everybody?)
Found this: http://forum.gsmhosting.com/vbb/f824/karbonn-a9-dead-qualcomm-hs-usb-qdloader-9008-how-fix-1740061/
It seems if I can just find the corresponding hex files, etc, this could work.
Or I could somehow reprogram my CPU and make things even worse...
I'm really stuck now.
P.s: I've ofc by now seen nearly everyone go for a JTAG repair. I will check the shops around here when they open, but I don't know if they can do anything about it.

Jtag should be able to repair that kind of brick. Unfortunately, when its due to flashing a different devices firmware, our device methods won't usually work.
You can try the d ebrick method we have posted in development, but just don't expect much. (You never know though, you might get lucky).
I doubt following this instructions will work as they are for a different device. Big risk to try it imo. Might make it non-recoverable by any means. (The process might work, I don't know, but you'd likely need specific files for your device).
Jtag is probably your best option. And in the future, stay away from the toolkit! Its bricked a number of devices and the dev just ignores support requests, even from those who buy it...
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
Jtag should be able to repair that kind of brick. Unfortunately, when its due to flashing a different devices firmware, our device methods won't usually work.
You can try the d ebrick method we have posted in development, but just don't expect much. (You never know though, you might get lucky).
I doubt following this instructions will work as they are for a different device. Big risk to try it imo. Might make it non-recoverable by any means. (The process might work, I don't know, but you'd likely need specific files for your device).
Jtag is probably your best option. And in the future, stay away from the toolkit! Its bricked a number of devices and the dev just ignores support requests, even from those who buy it...
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Yeah, shops open soon so hopefully I can see what can be done.
I figured not to bother with the qualcomm tools, messing with things I didn't quite understand was how I got in this trouble in the first place.
But just to clarify something, the Android Toolkit wasn't what bricked it, I tried to install the firmware from a .zip on my SDcard viz CWM recovery, but it was the wrong one (I was so damn sure I was T999, not T999L).
Thank you guys for all the help, I'll post if the guy fixes it!

I know, I only mentioned it because you mentioned using it. Just warning you for the future is all.
Good luck!

HTC one m8 stuck and desperate owner

Guys I am kind of screwed here, could you help me out?
Ok so I wanted to root my HTC one m8 and flash a custom rom on it (the sky dragon one, but that is irrelevant). So I looked up a video on youtube called; "how to root you htc one m8 **made easy** " and everything went well (it did take me about 3 hours... I am not a proud man right now...), until I had to install a custom rom. I wiped my phone, cache etc. (including phone storage) and here's where I start to notice my failure. I don't exactly know what steps I did and where exactly everything went wrong, but basically this is what I've got to work with: -a htc one m8 that gets stuck on the htc boot-up screen -roms complaining about missing md5 files and verification error or something -and last but not least; a very concerned owner who, after about 7hours of non-stop trying, is pretty desperate for help...
right now is there anyone who could help me with this, it would mean a lot to me (and my phone)
Edit: I remember where exactly my phone got stuck in the boot-up htc screen; it was right after I rooted my phone, but supersu said it was missing binary files or something. I installed, according to the guy from the video this woul fix it, supersu version 2.4 updater or something, and from that point the phone would't get past the boot-up screen. Again: any help is, at this point, very very veerryy appreciated

abramo2001 said:
I looked up a video on youtube called; "how to root you htc one m8 **made easy** " and everything went well (it did take me about 3 hours... I am not a proud man right now...)
Click to expand...
Click to collapse
Beware of such Youtube tutorial videos. I normally advise against using them. They often contain outdated information that can easily screw you up. And even more important, they are often used to shortcut the learning process, spoon-feeding you the steps in a way that pretty much means you won't learn anything; and leave you high and dry without the proper knowledge, when things inevitably do south.
Word to the wise: read, learn and understand before trying anything else. I know XDA can be a bit intimidating (like trying to drink out of a firehose, as one new member phrased it). But all the information is here, for those willing to take the time to read and learn.
abramo2001 said:
Ok so I wanted to root my HTC one m8 and flash a custom rom on it (the sky dragon one, but that is irrelevant).
Click to expand...
Click to collapse
Its completely relevant and important what ROM and version number you tried to install. Skydragon GPE or Sense? And what version number?
abramo2001 said:
Edit: I remember where exactly my phone got stuck in the boot-up htc screen; it was right after I rooted my phone, but supersu said it was missing binary files or something. I installed, according to the guy from the video this woul fix it, supersu version 2.4 updater or something, and from that point the phone would't get past the boot-up screen
Click to expand...
Click to collapse
Not clear from your description when you tried to root. But its probably at least part of the problem. You don't need to root if you are installing a custom ROM. You don't need to root in order to flash it (just an unlocked bootloader, and custom recovery), and you don't need to root after flashing, as all the custom ROMs are already pre-rooted.
For further help, we'll need more info on the phone. If you know how to use fastboot, do a fastboot getvar all, and post the results (delete your IMEI and serial number before posting). If you don't know how to use fastboot . . . well, time to start reading.
Also, need to know what TWRP version, and SuperSU version you tried.

redpoint73 said:
Beware of such Youtube tutorial videos. I normally advise against using them. They often contain outdated information that can easily screw you up. And even more important, they are often used to shortcut the learning process, spoon-feeding you the steps in a way that pretty much means you won't learn anything; and leave you high and dry without the proper knowledge, when things inevitably do south.
Word to the wise: read, learn and understand before trying anything else. I know XDA can be a bit intimidating (like trying to drink out of a firehose, as one new member phrased it). But all the information is here, for those willing to take the time to read and learn.
Its completely relevant and important what ROM and version number you tried to install. Skydragon GPE or Sense? And what version number?
Not clear from your description when you tried to root. But its probably at least part of the problem. You don't need to root if you are installing a custom ROM. You don't need to root in order to flash it (just an unlocked bootloader, and custom recovery), and you don't need to root after flashing, as all the custom ROMs are already pre-rooted.
For further help, we'll need more info on the phone. If you know how to use fastboot, do a fastboot getvar all, and post the results (delete your IMEI and serial number before posting). If you don't know how to use fastboot . . . well, time to start reading.
Also, need to know what TWRP version, and SuperSU version you tried.
Click to expand...
Click to collapse
Thank you very much for your help and in the future I will definetly do some more research before doing this ind of stuff, but I EXTREMELY glad to tell you: I FIXED IT . I googled and googled and all in all it probably took me around 15 hours, but I installed the marshmallow stock gpe rom for my phone via fastboot and after about 70 tries, learning and googling along the way, it worked. I don't know what went wrong the first time I tried (with the rooting), but everything is fully functional right now and my battery life, along with my free storage (bloat used to take up around 4 gigs), has improved significantly. I really really appreciate your response and I wil certainly be more careful in the future. Also, am I now allowed to call myself a "hacker"? I am right? . Have a great day; android is masterrace!

abramo2001 said:
I googled and googled and all in all it probably took me around 15 hours, but I installed the marshmallow stock gpe rom for my phone via fastboot and after about 70 tries, learning and googling along the way, it worked. I don't know what went wrong the first time I tried (with the rooting), but everything is fully functional right now
Click to expand...
Click to collapse
Probably could have cut down on the amount of time finding the problem, and the reason root failed; if you had provided the info requested in my last post. My last post was meant to be taken "post the required info, and we'll help you more". But glad you sorted it out, anyway; and you're welcome and glad to have helped in whatever way you found useful.
I'd also suggest sticking to XDA search function for these types of mods (or at least, reputable mod websites). Googling random websites will often lead to outdated info; and the info is often stolen from XDA, anyway.

Help Installing Custom Recovery on LG G Pad 8.3

So i just got this tablet out of the blue, didnt realy expect it and its not something thats really needed but it could come in handy. I figured id mod the hell out of it so it would be ready to go when i did decide to use it. I figured it being a name brand that doing all this would be easy. I havnt even looked into ROMs yet id figured id start with some custom recovery TWRP. Everything has been a complete disaster tho.
I had the thing for less than a few hours and done had it bricked and then about 10 more times after that. Ive been able to unbrick each time using the LG Flash Tool 2014 and a stock android 4.2.2 rom. I have the newer stock roms up to 5.?.? whitch is what i think was oroginal on it when i got it, but i figured downgrading would make everything easier. I still cant get anything to work right ive watched dozens of videos and posted and there so much crap out there its kinda hard to know what to use and to try, Were my particular tablet works into this time line.
Ive tried simple one click stuff that i think was the original tools. Ive tried the apps on the device. Ive tried hooking up to the pc. Using the command line on pc and on phone. Ive tried a million and one diffrent tools, programs, and files. My whole desktop is filled up with crap. The one thing i am able to do is root the drvice using kingroot but i beleave thats the one app you guys dont realy aprove of, but its so easy to use. I tried using some other root methods to see if that would help, but it didnt.
I read some were about the bootloader being locked and that being the problem, So i tried different things to unlock that but no luck. Then there was something about needing to downgrade the bootloader to the 4.?.? version or something, IDK. I am so lost any more idk were to go from here. I only get a new android device every few years because as long as it makes call i dont care and i dont tend on modding it all that much because theres the possibility i could be with out a phone for a few days. ive always been pretty good at modding stuff over the years but it just seems like android stuff just gets harder and harder over the years. Its starting to be more trouble then its worth but i guess thats the point. Ive always love doing this stuff but i just dont have the time like i use to spend all day looking this stuff up and getting stuff done but i just dont have the time to do that anymore. My eyes and back cant handle the hours starring down the keybored like they use to. Sometimes taking brakes screws up my concentration and it takes me a minute to get back on track.
Anywase like i said im kinda lost not sure were to go from here and i just figured id post and see if anybody would through me a line. If not well its cool ill figure it out eventually or just use it the way it is.
Dont have original info - I know I should have wrote everyhting down before diving in, but i didnt. This info is from the current stock ROM installed
Model # VK810 4G
Hardware Version # Rev.1.0
Android Version # 4.2.2
Baseband Version # M9615A-CEFWTAZM-4.0.10353
Kernal Version # 3.4.0
Build # JDQ39B
Software Version # VK81011A
Any other needed info please ask.
O its from Verizon

Did i post this in the wrong place.

I encountered the same problem but i've solved it by downgrading the stock ROM because the recovery is locked with last version of stock ROM.

BololFR said:
I encountered the same problem but i've solved it by downgrading the stock ROM because the recovery is locked with last version of stock ROM.
Click to expand...
Click to collapse
I downgraded the stock rom still couldn't get it to do anything.

telcar said:
I downgraded the stock rom still couldn't get it to do anything.
Click to expand...
Click to collapse
Which version do you have ?
Have you root your device ?
Have you try Official TWRP App for flashing recovery ?

BololFR said:
Which version do you have ?
Have you root your device ?
Have you try Official TWRP App for flashing recovery ?
Click to expand...
Click to collapse
All that info was given in my original post at top

"Please get the approval to use factory binaries (abl)"

When trying to flash a combination file, using Odin 3.13.
Also saw the same error with "(pit)" at the end.
This is on an A705W variant. (A705WVLU2ASI5). I was mucking about with an outdated cracked version of Z3X but it didnt list my phone, so I was being a bit hesitant
If anybody here has any thoughts on how to get past this, I would be very grateful to hear them.
I really like the phone. In spite of a few small shortcomings, I think it's a darn nice machine. The screen is big. Bright and clear. And it's quite fast, with a ton of storage. BUT I WANT ROOOOTZ!
Even TWRP, too
So any help.. would be awesome please and thank you too!

wyldnewbie said:
When trying to flash a combination file, using Odin 3.13.
Also saw the same error with "(pit)" at the end.
This is on an A705W variant. (A705WVLU2ASI5). I was mucking about with an outdated cracked version of Z3X but it didnt list my phone, so I was being a bit hesitant
If anybody here has any thoughts on how to get past this, I would be very grateful to hear them.
I really like the phone. In spite of a few small shortcomings, I think it's a darn nice machine. The screen is big. Bright and clear. And it's quite fast, with a ton of storage. BUT I WANT ROOOOTZ!
Even TWRP, too
So any help.. would be awesome please and thank you too!
Click to expand...
Click to collapse
Hi, sorry to revive an old thread but did you ever resolve this issue?
I don't have a Z3X Box or anything but I'm trying to flash a combination file but have the same problem.
Phone is a A705FN/DS
I downloaded a PIT file for the A705FN and the message changed from
"Please get the approval to use factory binaries (pit)" to
"Please get the approval to use factory binaries (abl))"which to me means it's doing more than before.
Phone is running A705FNXXU5DUI1
Combo firmware i'm trying to use is COMBINATION_FAC_FA90_A705FNXXU5ATA3_FACFAC_CL16099365_QB28522265_REV00_user_mid_noship_MULTI_CERT.tar
Any advice would be appreciated

"No operating system found" Issue after re-locked bootloader

Yes, I screwed up. Here's what happened:
>New Razr 5g aquired
>Rooted it first thing with magisk (TWRP was just temporarily booted iirc, not installed)
>No customROM, no other system modifications
>Used it only for a few weeks to play around, no magisk modules or mods installed (root was used pretty much just for AFWall+)
>Decided to sell it again (though the device itself is epic, android just isn't my thing if no real root is available)
>Reset the device through android settings
>In order to get rid of message at boot, re-locked the bootloader with normal single fastboot command
And that's basically it. Instead of Booting it now just displays "No operating system found". There also seems to be no recovery installed anymore.
I've tried everything google/XDA offered (not much, sadly). I've downloaded the stockROM firmware aswell (couldn't find one with the exact same build date but one shortly after and shortly before for the same model and channel/region/etc. - both didn't work, permission error due to locked bootloader).
The only thing I found that might help is EDL mode. I've tried forcing it (https://forum.xda-developers.com/t/...nbrick-your-moto.3042687/page-8#post-84347359) and everything else I could find, but no success.
I would very very very much appreciate any help. (P.S.: Should I try contacting Motorola? I bought the device from a private party so no going to the store option)

@sd_shadow mentioned an "EDL cable" in a thread. Googling brought me here: https://android.stackexchange.com/questions/221973/enter-edl-mode-in-motorola-devices
Does the method from the answer there really work, and is it worth a try? Anything else I need to be aware of before trying it?
Edit: Looking around a bit more about EDL, it seems I need special drivers. If anyone could hint me in that direction that'd be nice. Unless there's a better method, of course. I'm currently on Linux but I fear I might have to setup a Windows machine for this in order to install neccessary drivers/tools..

techHatesMe said:
@sd_shadow mentioned an "EDL cable" in a thread. Googling brought me here: https://android.stackexchange.com/questions/221973/enter-edl-mode-in-motorola-devices
Does the method from the answer there really work, and is it worth a try? Anything else I need to be aware of before trying it?
Edit: Looking around a bit more about EDL, it seems I need special drivers. If anyone could hint me in that direction that'd be nice. Unless there's a better method, of course. I'm currently on Linux but I fear I might have to setup a Windows machine for this in order to install neccessary drivers/tools..
Click to expand...
Click to collapse
Give this a try.This link has the mobile driver,and the firmware needed to recover it.
How to unbrick Motorola Razr 5G (Smith) 9008 EDL - ROM-Provider
step by step guide to unbrick Motorola Razr 5G by using the QCOM 9008 EDL Mod, tested method to fix hang on logo, bootloop, software bug
romprovider.com

techHatesMe said:
@sd_shadow mentioned an "EDL cable" in a thread. Googling brought me here: https://android.stackexchange.com/questions/221973/enter-edl-mode-in-motorola-devices
Does the method from the answer there really work, and is it worth a try? Anything else I need to be aware of before trying it?
Edit: Looking around a bit more about EDL, it seems I need special drivers. If anyone could hint me in that direction that'd be nice. Unless there's a better method, of course. I'm currently on Linux but I fear I might have to setup a Windows machine for this in order to install neccessary drivers/tools..
Click to expand...
Click to collapse
How did you go with this?

I have the same problem what happens??