Database Info

[Q] Need help with t989d unbricking

Hello everyone! I'm new to the forums as a member, but used this for info since a few years back. Ok, so i've spent the past week trying to unbrick a samsung galaxy s2x (t989d on telus or koodo) and it seems alot of people are having trouble with this model. I've brought back another one identical to this one before, but it was only softbricked, so i could still enter download mode and use odin and just searched my butt off to find original roms and all and wound up bringing it back to life.
This one though... It's hard bricked with the dreaded QHSUSB_DLOAD mode. Found drivers for it to use it in windows, found QPST 2.7 build 422 and tried that to no avail since QPST always tells me the HEX files have a scrambling method which cannot be determined (even with it's own hex files that come with it, and tried on 2 different computers, one x86, one x64) so still stuck there. Tried ADB in windows but it never wanted to work in any way, also tried ADB with ubuntu linux but the devices list always ends up empty no matter how hard i try and what i change, even with other phones that are not bricked it won't list them at all... Also tried to use the SD card method and push an image on it to try and boot off the external SD using original rom from odin i have found, but have no idea exactly which image i need to push into the SD or if it need modification in any way to be able to boot like that, or if even the t989d does in fact truly support external SD card booting.
Before anyone says:" Ya you need to JTAG that, it's the only method..." First, no one around here has anything to jtag with and i don't want to cross the border to get it done, second this is the kind of job i need to get done without spending any money if at all possible cause phone is not mine and client on a restricted budget. Now i know this CAN be done as alot of people here and there were able to fix their phone that were on the same qualcomm series chipsets. I just need some help to do this on this phone, and any SERIOUS help would be apreciated.
I have access to original rom file for the particular MC4 version i have in hand, i have original rom file for another version of the 989d which i got to unbrick the first t989d a friend sent me, i have a NVbackup qcn file pulled out of my firends working t989d, and i also have a full backup made with TWRP on my friend's working phone. Wanted to pull out a better backup using darkspr1te's Brixfix-2-1 tool but like i said, in windows ADB wont work in any way even with python installed and all that, drivers also installed, but ADB isn't a recognised command. And in Ubuntu, no way to list any phone at all, even if i installed all the ADB files, JDK, did the whole rules file, changed attributes to the rules file, did the .ini file, and killed and restarded hdev and server... So i'm kind of at witts end right now, plus i've been sick and had a major headache for the past 2 days, and spent so far around 38 hours on this phone plus my normal job this week... So ANY help would be GREATLY apreciated, and i will gladly use this experience to help out the community and help put out a tool or whatever to unbrick all these damned t989d
Just le me know if you need any more info or files to help out and i will gladly do all i can to comply
Thank you in advance to this great community

Nobody?? not even a troll ?? pretty sure that not even a mouse is stirring

Update: I have finally been able to start to get somewhere with this. I was able to extract most of the MBN files needed for QPST from the stock rom, and created my own partition.mbn out of a PIT file i had from a previous t989d. And now i get the phone to accept download and don't get errors for those files, but it stays stuck when sending reset packets. So my guess is that either the partition.mbn file isn't good, or the mprg8660.hex file i used to substitute and test isn't 100% compatible with the MSM8260 chipset. I tried all i could but never was able to find the real mprg8260.hex file anywhere. So if anyone has mprg8260.hex and/or a working partition.mbn for the t989d, i would be grateful to get those so i can continue troubleshooting this and get it working. If you want any of the MBN files and everything i have so far, just send a PM or reply to this thread and i will gladly upload for you.

Don't use the 8660 hex, it might make it go out of DLOAD or SD mode and you'll get a HS-USB 9005 state instead of a HS-USB 9008 or a HS-USB 9006 state, and then you'll need to manually flash it while it reboots every 5 secs in factory recovery mode. Not fun stuff. Also, if you're playing in QPST, make sure you using 2.7.411 or later. And be careful. there is a 2.7.422 that is actually an old version with a Trojan floating around.. Also, be warned, If you don't know what your doing in QPST, you can make things a lot worse.

Lord Zog said:
Don't use the 8660 hex, it might make it go out of DLOAD or SD mode and you'll get a HS-USB 9005 state instead of a HS-USB 9008 or a HS-USB 9006 state, and then you'll need to manually flash it while it reboots every 5 secs in factory recovery mode. Not fun stuff. Also, if you're playing in QPST, make sure you using 2.7.411 or later. And be careful. there is a 2.7.422 that is actually an old version with a Trojan floating around.. Also, be warned, If you don't know what your doing in QPST, you can make things a lot worse.
Click to expand...
Click to collapse
So far i had no problems using 8660hex, only stays on 9008 download mode so far, even after it's supposed to pop back to diag mode. And i AM using 2.7.422 but it doesn't seem to have a trojan or anything or else my anti-virus would've told me, but still kinda looks like an old version since most of the devices supported are the old ones and has nothing newer than 7XXX series on protocol modes in the settings menu. But like i said, so far i got it to respond with the 8660 and accept the mbn files, but still no change yet, still wont reset/reboot, still wont turn on or anything, just stays in download mode seen as a 9008. So i'll check to find 2.7.411 to try it out and see if does anything else. Even if it would reboot every 5 secs in factory recovery mode it would still be a step further than i am now right now it does nothing and stays in download mode. But thanx alot for the info!!

Suraido said:
So far i had no problems using 8660hex, only stays on 9008 download mode so far, even after it's supposed to pop back to diag mode. And i AM using 2.7.422 but it doesn't seem to have a trojan or anything or else my anti-virus would've told me, but still kinda looks like an old version since most of the devices supported are the old ones and has nothing newer than 7XXX series on protocol modes in the settings menu. But like i said, so far i got it to respond with the 8660 and accept the mbn files, but still no change yet, still wont reset/reboot, still wont turn on or anything, just stays in download mode seen as a 9008. So i'll check to find 2.7.411 to try it out and see if does anything else. Even if it would reboot every 5 secs in factory recovery mode it would still be a step further than i am now right now it does nothing and stays in download mode. But thanx alot for the info!!
Click to expand...
Click to collapse
hi,
were you able to resolve this ? I have the Skyrocket (I727R) and i was wondering if you could share the files and possibly how you fixed this problem,
any help would be appreciated.
thanks

Help bring my G3 back to life!!!

So, here's the story: I wanted to root my d850 on LP version D85021R, Tried all methods posted here, including this, this, and this. None worked. So I decided to downgrade to KK using tot/kdz method by hyelton. Downloaded LGD850AT-01-V10d-310-410-JUN-19-2014+0.tot file and LG flash tool 1.8.x and flashed the tot file. Progress went above 85% and then phone rebooted, but never came back to life; super-bricked, no led, no boot screen, no download mode, no recovery mode, NOTHING! except that it identified as QHUSB_BULK in Win7, which upon installation of drivers turned to qhsusb_dload 9008. Tried all unbricking methods including Board Diag, Flashtool ,etc. none worked. So I took it to a repair guy, who probably used octopus box to copy image from another g3 (at least that's what I think, he would not let me see but i sort of glanced over). After copying that image to my g3, it turned back to life, i.e., boot screen appeared and download mode/recovery mode worked, but it was in a boot loop. however, that guy also tried flashing V10D using flashtool, and same thing happened, i.e., super-brick again. After a day of trying he gave up on it but was kind enough to give it back half alive. So now boot screen appears, download mode works, gets recognized as LGE Mobile USB Serial Port, and LGE Android MTP Device with a yellow triangle. I cannot access fastboot mode due to locked bootloader, or else I would have tried flashing partition images through fastboot, as bootloader and boot partitions are intact, so I would not touch them but could try flashing other partitions. LG Flashtool flashes the whole package so the boot sector also gets over written, which somehow is not compatible with stock rom. One thing which I have not mentioned is that I did not buy it new but refurb one, so may be some part was changed, but which one, no idea. I tried to get it recognized it in linux, but does not work; shows up as libmtp-1-1 in /dev, which is not mountable. However I was able to pullout one interesting fact, which might give some hint. dmesgs shows a serial number for this device which starts as LGD855xxxxxxx, whereas the serial number printed on the back is different, where it shows as d850 and serial number is also different, i.e., 406KPXVxxxxxx.
Now I am out of options. Can someone please suggest what else to do. Also, can someone confirm that the serial number shown in dmesgs when connected to USB port, starting with LGD855xxxxxx can be a d850?
Any help is welcome

First off when flashing almost every time it'll fail at 85%. That's normal. Anything after80% is just rebooting of the phone.
Now what your having is not normal. Maybe whatever the repair shop did changed the serial? And your issue usually means your bricked completely sadly.
Before your downgraded, was your phone booting normally or did the root do something to make it originally boot loop before trying to downgrade ?
Sent from my iPhone using Tapatalk

Thanks for replying hyelton. I fully understand that and also that rebooting should bring the phone to blue reset screen, but it didn't. Instead it died.
The serial number and IEMI fortunately are intact, and are read by firmware when present. Sadly I tried to flash the firmware again through Board DL option, but failed again, so back to QLoader 9800 mode. On WinXP, smart boot diagnostics recognized it and proceeded to flash boot/recovery, but sadly the accompanied AP_Chip file neither has D850 nor D855 Smart_Boot.bin files. So I flashed EUR xxxx.xxx version. Phone still dead, but no Qloader 9800 mode, instead Android Phone device started showing up, which had no supported drivers. After some effort, Windows 7 download drivers and it got recognized as AlCatel Android Phone, lol! No adb and fastboot in Windows, and no Serial communication was possible. I tried linux and there fastboot was showing a device without id, like ??????????, but it did allow me to flash individual mbn paritions extracted from D850 tot to their respective partition, but I discovered I cannot flash through fastboot files larger than 2GB, so no system and no userdata; those were erased only. Upon reboot and return to windows, phone is still dead (without any life) and back to Qloader 9800 mode.
So now I'm stuck due to lack of firmware files. I am afraid to flash a boot or recovery partition extracted from any other firmware, but can try D855 since it worked partially to bring download/recovery partitions and LG logo was also displayed upon turning on. I think it even booted basic kernel in download mode, because I was able to send reboot command through Send_Command.exe and it rebooted. So scripting was also a possible option, but not anymore.
Is the partition layout of D850 and D855 available somewhere? I tried to find but could only find for D851. If someone having these variants is willing to help, I'll post the commands to get partitions layout, or even partition images could be created using dd command if phone is rooted.
To your question, no, the rooting methods did nothing. It was working normal. But somehow I came across a lot of threads that suggested hassle-free downgrading to KK for rooting, and pointed to your guide which surely is hassle-free but not for a troubled phone like mine
BTW, I do have Flashtool log files for original downgrade and then reflashing yesterday. If someone wants to take a look...

Further development: Today I visited the main mobile market in my city, and first went to same shop from where I bought this set. They had a number of other sets in the same batch, so I copied partition tables info and prop files from each device. Also, I had to buy the same set for a friend. I have asked him to lend it over to me for weekend. Now, first I'll try to find the rom versions installed on these sets and see what I can do.
Secondly, is there a way I can copy the whole emmc partitions from alive phone to dead phone? The dead phone can be accessed on serial port. I know I can get partition dumps, but how to write them on bricked phone, that is the question. There must be a software that can access emmc through phone ports and clone it. Help please!

unikorn74 said:
Further development: Today I visited the main mobile market in my city, and first went to same shop from where I bought this set. They had a number of other sets in the same batch, so I copied partition tables info and prop files from each device. Also, I had to buy the same set for a friend. I have asked him to lend it over to me for weekend. Now, first I'll try to find the rom versions installed on these sets and see what I can do.
Secondly, is there a way I can copy the whole emmc partitions from alive phone to dead phone? The dead phone can be accessed on serial port. I know I can get partition dumps, but how to write them on bricked phone, that is the question. There must be a software that can access emmc through phone ports and clone it. Help please!
Click to expand...
Click to collapse
Flash it to D855 Lollipop version via octopus than write DUMP

It does work, indeed. We did it together, didn't we, aamszia?
To elaborate further, Aamir helped me out by writing D855 bootloader through octopus box. That was done before but flashing a KK rom again bricked it. Only this time, he flashed a d855 lollipop kdz rom (v20g, if I remember correctly). That made it functional; everything worked, except radio. Flashing a d850 LP radio would not work; flashing a KK radio would brick it. So I took a dump of mmcblk0 from a fully functioning, rooted, recovery flashed LP d850, via terminal using dd command (I chose to write only first 4gb or so due to smaller sdcard I had. That covered all partitions except cache and userdata, which were not needed anyway). Then I wrote back the dump on the bricked d850 using dd command from terminal. I tried flashing TWRP on it first, but somehow it did not work, and gave secure bootloader error. So I had to do it via terminal. I knew once it starts writing, the system would become unstable due to overwriting of partition table, kernel, system, and stuff, but I had to give it a try, and it worked! Screen went off immediately, but I touched it again after half an hour; pulled out and reinserted the battery; tried recovery and there it was. Rest was easy. Just formatted cache and data, and my phone was back to life.

Strangest "Bricked" Oneplus One: No recovery, locked OS, can't unlock bootloader

Strangest "Bricked" Oneplus One: No recovery, locked OS, can't unlock bootloader
Hi there, I've come in to the possession of the most stubbornly bricked phone that I've ever seen . Bought a OPO off Craigslist, someone cracked the screen and sold it for cheap instead of fixing it. It had been remote wiped but still has some strange difficult software. Posted this problem to the Oneplus Forum but have had no response, thought XDA would be more qualified!
From what I can tell it's a Oneplus One that was sold through a re-seller that replaced all the software on the phone with a high-security version of Android. It's called EncroChat and from their website (encrochat.network or encrochatsure.com) it looks like it removes the recovery from the phone and replaces it with an EncroChat OS (some kind of Cyanogen) that you can boot to in addition to the Android OS.
Well I assume during the remote wipe something went wrong with the software and the phone no longer really functions. It boots up fine but can't connect to Wifi, cellular, not detected when connected to my PC, and has no real apps to speak of. I think most of the device's drivers are missing. Trying to boot to recovery instead boots to their EncroChat OS which is locked behind a password that neither I nor the person I bought it from knows.
I can get to fastboot and my PC will detect the phone then but running the bootloader unlock command doesn't work, the phone just reboots into the locked EncroChat OS. My idea now is to try and hardbrick the phone and then re-do everything on the phone over again, but I can't figure out how to do that. Does anyone else have any ideas?

Contacting EncroChat
Tried contacting EncroChat via email form, twitter, and reddit. No luck! Still stuck with this. I want to try this unbrick guide: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 for hardbricks but I can't get my phone to show as QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008. Any idea how I can do that? This guy seems to have done it:
evronetwork said:
Had one GOOD soft brick in the past, I've used coloros rom(from the Chinese OnePlus One) and fix my phone ...it deleted all media of course but manage to unbrick the phone. Don't ask me how to, it's been a while, google it
It would fix even the most stubborn soft bricks you'll see. Before that I tried everything that was available at the time, no boot as well only fastboot(not even recovery)
Click to expand...
Click to collapse

broccolicakes said:
Tried contacting EncroChat via email form, twitter, and reddit. No luck! Still stuck with this. I want to try this unbrick guide: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 for hardbricks but I can't get my phone to show as QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008. Any idea how I can do that? This guy seems to have done it:
Click to expand...
Click to collapse
For your phone to be recognized in your PC as QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008, you need to install proper drivers. follow this guide
http://www.androidbrick.com/ultimat...agons-are-unbrickable-qhsusb_dload_qpst_qfil/
let me know, if I can help you furthermore.

broccolicakes said:
Tried contacting EncroChat via email form, twitter, and reddit. No luck! Still stuck with this. I want to try this unbrick guide: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 for hardbricks but I can't get my phone to show as QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008. Any idea how I can do that? This guy seems to have done it:
Click to expand...
Click to collapse
Hello dude,
While it was quite some time when I did this unbrick, it was successful ...expect ALL data to be deleted from phone. Google is your friend and I did get all the files from somewhere
You use a special software from the phone, it's coloros software and with provided files it recognise the phone and flash it(2-3 seperate flashes through the software if I remember correctly) - don't worry as long as the phone turns on(mine was turning on but did nothing ...blank, only way to turn it off was to hold power button and hold it(forced turn off))
P.S. The phone wasn't recognised by the OS ...only from this app(cool? ..weird if you ask me - I'm a computer repair tech guy and find this hard to believe if it didn't happen and see it with my own eyes - on the other hand it could be somewhere hidden in the system and recognised like something else so I won't put my hand in fire to verify this )

Thanks!
evronetwork said:
Hello dude,
While it was quite some time when I did this unbrick, it was successful ...expect ALL data to be deleted from phone. Google is your friend and I did get all the files from somewhere
You use a special software from the phone, it's coloros software and with provided files it recognise the phone and flash it(2-3 seperate flashes through the software if I remember correctly) - don't worry as long as the phone turns on(mine was turning on but did nothing ...blank, only way to turn it off was to hold power button and hold it(forced turn off))
P.S. The phone wasn't recognised by the OS ...only from this app(cool? ..weird if you ask me - I'm a computer repair tech guy and find this hard to believe if it didn't happen and see it with my own eyes - on the other hand it could be somewhere hidden in the system and recognised like something else so I won't put my hand in fire to verify this )
Click to expand...
Click to collapse
I figured it out, thanks ! Now I'm stuck with a more minor problem of only having 16gb visible on my 64gb phone. Can't write the userdata_64G image to my phone. Still trying some stuff out and I'll probably just make a new post if I can't get it to work. Thanks again!

broccolicakes said:
I figured it out, thanks ! Now I'm stuck with a more minor problem of only having 16gb visible on my 64gb phone. Can't write the userdata_64G image to my phone. Still trying some stuff out and I'll probably just make a new post if I can't get it to work. Thanks again!
Click to expand...
Click to collapse
I read just the other day that someone needs the 64gb image instead of the 16gb image. You did so well so far, I'm sure you'll figure this one out. Congrats! "Encrochat Beware!"
The mention of the 64gb vs 16gb image is here:
https://forums.oneplus.net/threads/solution-recover-from-hard-bricked-oneplus-one.104943/
He links to the images here:
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541

help
broccolicakes said:
I figured it out, thanks ! Now I'm stuck with a more minor problem of only having 16gb visible on my 64gb phone. Can't write the userdata_64G image to my phone. Still trying some stuff out and I'll probably just make a new post if I can't get it to work. Thanks again!
Click to expand...
Click to collapse
Hi broccolicakes, cane you please tell me how you figured it out. Because Am at your same position with an Oneplus x ??
please tell me how you did it????

redi.c said:
Hi broccolicakes, cane you please tell me how you figured it out. Because Am at your same position with an Oneplus x ??
please tell me how you did it????
Click to expand...
Click to collapse
Hi there, sorry in advance this might not be very helpful in your situation. I ended up using the ColorOS repair tool for Oneplus One that I mentioned earlier in the post. It turned out I just didn't have the correct drivers so once I sorted those out the tool was able to bypass all the software and replace everything on the phone so that I could then install my own OS.
I guess the trick would be to find a version of this tool for OneplusX. I'm not sure if there is one available, I haven't looked. Maybe make a separate post about that? The ColorOS tool I'm talking about is from here: http://forum.xda-developers.com/showpost.php?p=55024864&postcount=136 and it just looks directly for the Qualcomm chip and writes to that. I'm not sure where that tool came from, if it made its way out of Oneplus directly or if someone created it afterwards...

TWRP Recovery can it help after deleting firmware and where to find one

Hello everyone,
let me start off with what I want:
1. I want to know if I understood it correctly and I can save my device by using another device's (of the same make and model) backup.
2. Hopefully, anyone knows where to find a suitable backup.
Device: Lenovo TB-8704f
Device Situation:
I flashed pretty much badly over every storage in my attempts of doing something useful. Boot and system are flashed with non-working software, so for all purposes, we can regard them as empty. Recovery has TWRP on it.
How did I get here?
So, this part is only if you're interested in why I was this stupid. I tried to condense all the relevant information about my problem above. Anyway, I checked if my tablet has custom firmware and I found one. I overlooked that the firmware said 8703 instead of 8704. So I was convinced I had a working ROM. Now, I am very inexperienced with Android flashing, and when I fastbooted the device to run TWRP, the guide said, I could boot it directly from fastboot with
Code:
fastboot boot twrp.img
and I could then flash it if I wanted. Well, I did not read up on it beforehand and so I went in with
Code:
fastboot flash boot twrp.img
. Bye, bye boot partition. After doing it finally right, I got it running and wiped my system, then copied over the zipped custom ROM and after a few attempts, I finally read the error message careful enough to see that it stated that my device wasn't compatible. At this point, I started to figure out how to go back to stock, since I had no backup due to my previous flashing mistake. Well, I found the firmware from some Russian forum and a few guides that described how I could load it onto the system with QFIL. After spending hours trying to do that, I finally understood what my issue was. All the guides were speaking about the 9008 Port for QFIL. And I only saw a diagnostics port. Found a thread about a different Lenovo device in which it was explained that the diagnostics port was a stripped down 9008 protocol. And it couldn't load any data. Well, that explains my failing. Now that other device could be put in the 9008 by unplugging the battery and holding down up and down button while reconnecting, but I don't have the tools to perform surgery on my tablet, so I just decided to leave it bricked until finally hopefully someone brings out a custom ROM. That was two weeks ago and in the meantime, I had the idea of asking you guys if anyone has a TWRP backup and/or if that would help me in my situation.

LG W41 (LM-K610IM) dead bricked by my stupidity. Could it be somehow revived?

Greetings everyone. I didn’t find a thread for this specific phone model. So I am putting it up here. Few days back I decided to unlock the bootloader of my LG W41 (LM-K610IM) and upgrade to a custom ROM. So, I used fastboot mode to unlock the bootloader and up until now everything went like a dream. Problems started when I couldn't get a TWRP recovery for my specific model. I downloaded a generic one and first tried to push it to my recovery partition. That's when I learned my phone doesn't have a recovery partition. I don't know what came to me then I used fastboot flash command to flash the TWRP image to my boot partition. It was successful but my phone won't start after that. It was a softbrick. Only the LG logo started bootlooping. But the worse was still not over. In an attempt to restore my device I searched everywhere for the stock ROM as the official website is down, but couldn't find any. At last, I zeroed in on a similar device by the same manufacturer LG K52. It had the ditto hardware like LG W41. Even the model number was similar. So, I downloaded the KDZ file. Extracted the dz from the kdz and the boot.img from the dz using LG KDZ extractor . Made a scatter file using a Hovatek instruction and using WWR MTK tool and formatted my device using SP flash tool and flashed everything. Till now my device was detected by the Windows 11 PC as a LGE device. Anyways the SP tool successfully flashed everything but after that my won't turn on any more. It's total dead. It won't power on, pc won't recognize it. I have tried connecting using USB and all possible hardware key combinations. It is dead bricked I think. All because of my stupidity. Now my question is, does it have any hope left or should I throw it away and buy a new device? I am keeping my fingers crossed and hope to find a superhero
Edit 1: SP Flash tool doesn't see my device any more. I have all the specific drivers installed. From LG and from Mediatek.

Try LG Bridge or check lg-firmwares.com
or
buy/borrow second device and 1:1 clone with mtkclient

Thanks for the quick response, but I have already tried LG Bridge, LGUP . After soft brick LGUP was seeing device as "unknown at COM Port 9". After hard brick it doesn't see it any more. Actually my PC won't see the device anymore

The firmware is not available at LG-firmwares.com but I have requested for it there. Keeping fingers

you should be able to repair preloader from bootrom mode (BROM)

How to enter bootrom mode. I am sorry if it is a noob question

Soumyadip999 said:
How to enter bootrom mode. I am sorry if it is a noob question
Click to expand...
Click to collapse
XRed_CubeX said:
To put your device in BRom mode you may need a different key combination or a test point, find out on the internet how to put the device in BRom mode or ask various devs of that device
Click to expand...
Click to collapse
find KCOL0 test point and short to GND
https://forum.hovatek.com/thread-11802.html

Okay let me ask and I will follow up. Thank you for the amazing guidance. Let's see if the poor device could be saved

you should poll lsusb in linux while trying to connect usb with both vol keys pressed. disconnect battery from pcb if possible to ensure phone is off.