I've got files from a website that sells the loader file for the sd and he qfil files but they don't seem to be working. I've tried both solutions/methods. The QFIL method just says Sahara failure and download failure. The loader method is to suppose to make my micro sd card bootable but when I put it the device nothing comes up. I was thinking about doing both but idk what will happen and I don't want to mess anything else. Does anyone have some advice?
(to see the website just search up the title and it should be in the first few links)
I literally have been trying to fix mine for the past month everything on the internet doesn't work at least from my experience.. I did learn a couple of things the SD card method works if you have the ( 9008 ) error but only if your emmc is read by the computer I think this is called the ( New 9008 ) error or what ever but the one I have is the worst no emmc just Qualcomm 9008 error at this point I think octopus is the only thing that can bring the phone back to life I've read all the post and every one is pretty much clueless or doesn't care ??
@OriginalHit Please could you share the files here...?
Related
i bricked my phone to a point where it will not even hboot or fastboot, it does show up in device manager as qualcomm hs-usb qdloader 9008 (COM3). can anyone give me a runthrough to get it back to fastboot?
I dont have much money, but i would be willing to pay $20 via paypal to the person who helps me fix it.
what did you do before it happened?
This is a community bro, I'm sure someone can help you. Is adb working on it? Maybe you can try flashing a radio on it. I would start there!
bricked phone
i was flashing an ruu when the power went out, adb does not work and neither does fastboot.
Look's like Hboot is damaged. You need to use QPST - Qualcomm Product Support Tools, and to push inside your phone a good hboot. The main problem is that QPST dows support bootloader in hex format...
I will try to back-up my phone in hex format with QPST and put the hex file on this forum.
bubu782001 said:
Look's like Hboot is damaged. You need to use QPST - Qualcomm Product Support Tools, and to push inside your phone a good hboot. The main problem is that QPST dows support bootloader in hex format...
I will try to back-up my phone in hex format with QPST and put the hex file on this forum.
Click to expand...
Click to collapse
Dude if you do this PLEASE do it as a tutorial, im pretty sure it would make a sticky and solve alot of bricks
If you do this you would save tons and tons of sensation phones
I am in the same position with my phone. It died during the night and nothing will switch it back on. Is there any development in this problem?
Hi everyone
I have an LG Thrill 4G . Got this one from Ebay.
I experimented with cyanogen CM7 ROM.
And it/the ROM instead of formatting the external sd card formatted everything including the bootloader stuff.
Refer to this for more info - [-warning-brick-via-use-externalinternal-sd-selection/[/url] cyanogen mode
I have been searching on xda/google for solution to this type of brick,but as of now i have not found any solution.
This is what i have tried till now.
1. lg thrill recovery,lg tools.
2. the problem is device is not detected as lg com port. but as omap4430 and it gets frequently connected and disconnected.
3. i tried omap flash tool wid custom scripts. but it is of no use as device is not being detected.
Any idea about why the device is not being detected. and what part has exactly got damaged.
Any toolkits? i know jtag is not possible in this device as there are no pins.
Can i get the motherboard online? from somewhere, cheaper than the service center. i have no warranty. and in India things are really expensive compared to U.S .
P.S - FYI i have tried almost all the threads on XDA or anywhere else on this planet. so don't provide any vague/not working solutions unless you exactly know how to bring it back from dead.
I am already irritated from that frequent omap4430 connection and disconnection.
Any one with a hand on second stage bootloader flash? like flashing the thing on an external sd card and den device booting up from it.
Waiting for a response.
techygeeks said:
Hi everyone
I have an LG Thrill 4G . Got this one from Ebay.
I experimented with cyanogen CM7 ROM.
And it/the ROM instead of formatting the external sd card formatted everything including the bootloader stuff.
Refer to this for more info - [-warning-brick-via-use-externalinternal-sd-selection/[/url] cyanogen mode
I have been searching on xda/google for solution to this type of brick,but as of now i have not found any solution.
This is what i have tried till now.
1. lg thrill recovery,lg tools.
2. the problem is device is not detected as lg com port. but as omap4430 and it gets frequently connected and disconnected.
3. i tried omap flash tool wid custom scripts. but it is of no use as device is not being detected.
Any idea about why the device is not being detected. and what part has exactly got damaged.
Any toolkits? i know jtag is not possible in this device as there are no pins.
Can i get the motherboard online? from somewhere, cheaper than the service center. i have no warranty. and in India things are really expensive compared to U.S .
P.S - FYI i have tried almost all the threads on XDA or anywhere else on this planet. so don't provide any vague/not working solutions unless you exactly know how to bring it back from dead.
I am already irritated from that frequent omap4430 connection and disconnection.
Any one with a hand on second stage bootloader flash? like flashing the thing on an external sd card and den device booting up from it.
Waiting for a response.
Click to expand...
Click to collapse
Any chance you could post up the custom scripts that you used with OMAPFlash?
kidkoala_uk said:
Any chance you could post up the custom scripts that you used with OMAPFlash?
Click to expand...
Click to collapse
they were of no use to me as device is not detected on com port.
i think we need to do something like booting the device from external sd card like installing all required stuff on external sd card and then booting the device of it. i read this somewhere. i think it was omap bootloader project.
but the articles are a bit outdated.
L27.G.5_OMAP4_GingerBread_Release_Notes
search for this on omappedia wiki.. i hope it helps.
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
I really need some serious help and advice. Could anybody who is experienced it this filed please help me, or even put me in the right direction.
I am stuck in the qualcomm download mode with my device as QHSUSB_Dloader9008.
Yes it is a hard brick and 99% of the google searches have just confused me.
So here is the story.
I was developing for the Lg Vista D631, and trying to port a rom from the v10lte tablet due to the exact same architecture. The only main difference was the screen size.
Anyhow i was using fastboot to mess arount with the LG Security Error but nothing worked.
I didnt find out that much. So i just flashed back stock and then restored from cwm.
Well i went back to fastboot to try some more and i typed fastboot erase aboot, all went well. Then as i was in the middle of typing fastboot flash aboot my dang phone battery fell out my phone. And this is what i recieved... It Took it off my cmd prompt screen, i now have a nice crack in the screen, and a wonderful bricked phone....
It read up as Android Net USB, and it also came up as a removable disk with 64mb free on it. so i looked and i looked for something just to flash the aboot partiton back to the phone. But nothing came up. I even tried win32 imager.
I googled jtag and read that there are test points which would i could short to reset the devices bootloader to the wualcomm safe bootloader to flash the emmc chip and partition table back to stock. Which would thus repair the partition and open up recovery and or download mode.
I attempted to trace the circut to find out what point to short' and yea i even tried a few which only reset the phone. So i said screw it and formatted the removable disk....... And bam my pc detected a new device and installed the qhsusb dload9008 driver.
So now im in qpst fail safe download mode, i have it set to com41, and qpst detects it too.
And now th issue and question at hand.. I need the files to flash an msm8296. As the mbn, hex, and what nots are all not working with me. Do
When i try to use eMMC downloader I just kept getting the same response from qpst 4.0.2.
"Download failed could not communicate with flash programmer"
then in software download i keep recieving that the hex file is invalid, and could not detect the hex scrambling method. The file is invalid.
I have the lg d631 and have many unofficial kdz files i compiled. I could use the vs88010b for any other ones needed too. As i found out which ones are compatible through my testing phase.
When thia gets fixed though, the development for this phone will skyrocket, as anything will be possible.
So i am stuck. I messed up. And need to fix my mistake.
djacks222 said:
I really need some serious help and advice. Could anybody who is experienced it this filed please help me, or even put me in the right direction.
I am stuck in the qualcomm download mode with my device as QHSUSB_Dloader9008.
Yes it is a hard brick and 99% of the google searches have just confused me.
So here is the story.
I was developing for the Lg Vista D631, and trying to port a rom from the v10lte tablet due to the exact same architecture. The only main difference was the screen size.
Anyhow i was using fastboot to mess arount with the LG Security Error but nothing worked.
I didnt find out that much. So i just flashed back stock and then restored from cwm.
Well i went back to fastboot to try some more and i typed fastboot erase aboot, all went well. Then as i was in the middle of typing fastboot flash aboot my dang phone battery fell out my phone. And this is what i recieved... It Took it off my cmd prompt screen, i now have a nice crack in the screen, and a wonderful bricked phone....
It read up as Android Net USB, and it also came up as a removable disk with 64mb free on it. so i looked and i looked for something just to flash the aboot partiton back to the phone. But nothing came up. I even tried win32 imager.
I googled jtag and read that there are test points which would i could short to reset the devices bootloader to the wualcomm safe bootloader to flash the emmc chip and partition table back to stock. Which would thus repair the partition and open up recovery and or download mode.
I attempted to trace the circut to find out what point to short' and yea i even tried a few which only reset the phone. So i said screw it and formatted the removable disk....... And bam my pc detected a new device and installed the qhsusb dload9008 driver.
So now im in qpst fail safe download mode, i have it set to com41, and qpst detects it too.
And now th issue and question at hand.. I need the files to flash an msm8296. As the mbn, hex, and what nots are all not working with me. Do
When i try to use eMMC downloader I just kept getting the same response from qpst 4.0.2.
"Download failed could not communicate with flash programmer"
then in software download i keep recieving that the hex file is invalid, and could not detect the hex scrambling method. The file is invalid.
I have the lg d631 and have many unofficial kdz files i compiled. I could use the vs88010b for any other ones needed too. As i found out which ones are compatible through my testing phase.
When thia gets fixed though, the development for this phone will skyrocket, as anything will be possible.
So i am stuck. I messed up. And need to fix my mistake.
Click to expand...
Click to collapse
Hello and thank you for using XDA Assist.
We cannot provide technical support nor can other members reply to your posts here on XDA Assist. There is no forum specifically for the LG Vista at this time but you may want to ask your question with all relevant details in the friendly general Android Q&A, Help & Troubleshooting forum at http://forum.xda-developers.com/android/help where you have already posted several times. Since your device is relatively uncommon, please be patient and give the experts plenty of time to respond. I also see a number of references to your model from a site search at http://forum.xda-developers.com/sitesearch.php?q=lg vista which might be worth reviewing.
Good luck!
This thread is closed.
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...