Database Info

One S not booting up after OS deleted, PLEASE HELP!

I have One S (s4), accidentally erased OS and everything while in recovery, I tried to install CWM because I think I'm familiar with this recovery but after the phone went down for rebooting nothing happens! now the phone is like dead, tried to connect it to pc to use HTC One S All-in one Tool kit but to no avail. It's not recognizing my phone and pc is always saying can't install the right driver for my phone. please help!

kasuma_asuma said:
I have One S (s4), accidentally erased OS and everything while in recovery, I tried to install CWM because I think I'm familiar with this recovery but after the phone went down for rebooting nothing happens! now the phone is like dead, tried to connect it to pc to use HTC One S All-in one Tool kit but to no avail. It's not recognizing my phone and pc is always saying can't install the right driver for my phone. please help!
Click to expand...
Click to collapse
Try Power button + volume down ... Hold them for some seconds and see of you can boot into bootloader and then we can move forward.
Sent from my HTC One S using Tapatalk 4 Beta

thank you for the respond. it's not working. when I connect it to my laptop it shows "MT65xx pre-loader error' something like that, I think I bricked my One S. Oh man! I'm lost!

"QHSUSB_DLOAD driver not found" says on my laptop. I think it's the end of my phone. geez, I'm so stupid!

kasuma_asuma said:
"QHSUSB_DLOAD driver not found" says on my laptop. I think it's the end of my phone. geez, I'm so stupid!
Click to expand...
Click to collapse
I suppose that's it. You can send it to HTC if you have warranty, or JTAG.

khan.orak said:
I suppose that's it. You can send it to HTC if you have warranty, or JTAG.
Click to expand...
Click to collapse
I guess, It's just that I've never thought that my phone could end up like this. Damn, my wife's gonna kill me.

Are you sure that you flashed the correct device's recovery? Not the S3 or 64GB SE recovery?
I don't know why you'd choose CWM anyway, I think I'm the only person with a Galaxy S4 that uses TWRP (which is really, really slow on the GS4), CWM is disgusting...
Sent from my GT-I9505 using xda premium

SOLVED!
hey guys! I have an update on my phone! I'm here in the Philippines and I was able to find a guy who has a riff/jtag box to use on my One S. My phone got bricked too after wiping OS on TWRP and tried to install incorrect CWM but anyways, phone dead so I tried following Tecardo's advise, we were able to open up the phone and since we don't have any connector or jigg? I dunno, but long story short, we opened up One s, just solder the riff box's connector to the motherboard and revived the phone. he was able to revived the phone and it's looking good. been using it for 2 days now.
here's my phone now, figure I want to unlocked it again and root it and everything but I'm a bit afraid I might messed it up again. thanks to @Tecardo and now I wanna know how can I buy him a beer?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Stuck at LG logo

i booted into recovery, made a full backup, wiped everything but internal storage, flashed to lollipop 5.1 but decided to go back to my backup. so rebooted into recovery again and restored the backup. everything seemed to work correctly but after rebooting phoned stuck at lg logo. so i rebooted into recovery by holding "volume - and power" and the factory data reset screen came up and i confirmed that i wanted to reset phone, expecting it to boot into twrp but it went to the the black screen with the android on his side (or something like that), which i assume it did do a factory reset.
so still stuck at lg logo with no custom recovery anymore apparently. among other things, i used srktool to nuke download mode, so phone immediatly goes into fastboot mode. now im trying to use the "fix fastboot mode" but it just sits there saying waiting for device even though i have phone connected to computer in fastboot mode.
is it likely that if/when it did the factory reset, that would disable the usb debugging setting and that's why srktool just shows "waiting for device"?

im betting that your OS got corrupted. You can try to reflash your ROM, or you might be relegated to going into download mode and reflashing the OS back to stock. I have a link for the LG recovery tool and the stock 4.4.2. All youll need from there is towel root and the recovery i have in a separate post

hi i have same problem con you explein how can i do this
hi i have same problem con you explein how can i do this

l.musaj said:
hi i have same problem con you explein how can i do this
Click to expand...
Click to collapse
try this
http://forum.xda-developers.com/att-g2/development/twrp-5-0-d800-g2s-t3247754

youdoofus said:
try this
http://forum.xda-developers.com/att-g2/development/twrp-5-0-d800-g2s-t3247754
Click to expand...
Click to collapse
thank you but my lg d800 dosnt entry in download mode it stuck
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
he stuck here in ports dosnt show nothink but in USB controllers its unknown device

l.musaj said:
thank you but my lg d800 dosnt entry in download mode it stuck
he stuck here in ports dosnt show nothink but in USB controllers its unknown device
Click to expand...
Click to collapse
uninstall the usb driver and let windows find the correct driver for it and follow the stuff in the link i provided after the computer recognizes the device. If that doesnt work do the stuff in the link on another computer or try a different cable. If you can get to download mode, youre likely ok. The issue is either the computer or the cable, not the phone.

Hard brick after official OTA update from 4.4.4 to 5.1

I was running the Brazillian Retail 4.4.4 stock ROM and decided to update to 5.1 normally OTA. The phone was previously downgraded to 4.4.4 from 5.1 normally. After the software update, the screen was black and my pc recognized it as QHSUSB_BULK. I followed the normal un-hardbrick instructions using the lollipop qboot tool with the blankflash command, and it restarted into fastboot as expected. But now, I cannot flash the partition or motoboot of any version of the stock builds, including 4.4.4, 5.0.2 and 5.1. I really need this phone fixed, so I need some help ASAP if I can. Also, the phone was unlocked before the brick.
Here's a screenshot of the phone on fastboot mode.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
excuse the poor quality
Moto G XT1033 (Dual SIM)
EDIT: I fixed it by using a ROM from this thread http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795 :good:

Is the phone recognised by PC in fastboot mode ?
Power it on in fastboot mode : Hold Power et Volume- during 3-4 secondes and release.

djibe89 said:
Is the phone recognised by PC in fastboot mode ?
Power it on in fastboot mode : Hold Power et Volume- during 3-4 secondes and release.
Click to expand...
Click to collapse
It is recognized normally by the PC, but I cannot flash a partition table (usually called gpt.bin in stock ROMs) with the error message "version downgraded for primary_gpt".

I just managed to fix it by using a ROM from this thread http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Thanks for the help anyway :good:

foxpersonman said:
I was running the Brazillian Retail 4.4.4 stock ROM and decided to update to 5.1 normally OTA. The phone was previously downgraded to 4.4.4 from 5.1 normally. After the software update, the screen was black and my pc recognized it as QHSUSB_BULK. I followed the normal un-hardbrick instructions using the lollipop qboot tool with the blankflash command, and it restarted into fastboot as expected. But now, I cannot flash the partition or motoboot of any version of the stock builds, including 4.4.4, 5.0.2 and 5.1. I really need this phone fixed, so I need some help ASAP if I can. Also, the phone was unlocked before the brick.
Click to expand...
Click to collapse
I have a moto g (XT1031), which also got hard bricked by the same method (stupid of me....). Unlike OP, my phone is not restarting with the blankflash command. It says, "could not open device" and the screen stays blank. I tried holding down the power button for 2-3 minutes........ Nothing. Any suggestions/help appreciated. Thanks.

greenlantern2014 said:
I have a moto g (XT1031), which also got hard bricked by the same method (stupid of me....). Unlike OP, my phone is not restarting with the blankflash command. It says, "could not open device" and the screen stays blank. I tried holding down the power button for 2-3 minutes........ Nothing. Any suggestions/help appreciated. Thanks.
Click to expand...
Click to collapse
Try using another driver. I don't know how effective that will be, but it could work :fingers-crossed:
I won't share the driver I used because I'm afraid ill end up sharing malware, because the website I got it from was kinda sketchy.
Try googling for the QHSUSB_BULK driver.
Uninstalling the driver is very simple:
Go to the Start menu and type in Device Manager, and open it.
Right click on the "QUALCOMM HS-USB QDLOADER 9008" device (probably under "Ports (COM & LPT)") and click Uninstall.
Tick the "Delete the driver software for this device." checkbox and click OK.
At this point the PC should recognize the device as QHSUSB_BULK again.
Now install the new one

[Help][xperia f3113][dead]

Hello, excuse my bad english I'm using google translate.
The problem I have is that my xperia xa is dead.
the reason of it, was that I wanted to flash the rom of my cell to remove the applications that come with the mobile company.
when I realized my error, was that I did the following, in the flash tool, in the rom selection, I made the error, not selecting the following settings:
-APPS_LOG
-DIAG
-QNOVO
-USERDATA
-CUST-RESET
as shown in the following image:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
when the flash operation ended, the cell phone did not want to turn it on, the only function it had and has so far, is that it does not vibrate, it does not turn on, it does not go into flash or fastboot mode, it's dead, it just turns on the red led.
when I try to perform the flash operation again, I simply get the following message when I connect the device.
in the windows device manager, recognizes the phone as "usb serial device (com)".
I searched the net, and I did not find the solution to this problem, I appreciate your attention, and I expect some help.
PD: I already tried the connection with pc companion, and even the function from system symbol of windows with the tool fastboot to flash the boot, with the img.
the problem is that the device does not go into any mode

1990macsfull said:
Hello, excuse my bad english I'm using google translate.
The problem I have is that my xperia xa is dead.
the reason of it, was that I wanted to flash the rom of my cell to remove the applications that come with the mobile company.
when I realized my error, was that I did the following, in the flash tool, in the rom selection, I made the error, not selecting the following settings:
-APPS_LOG
-DIAG
-QNOVO
-USERDATA
-CUST-RESET
as shown in the following image:
when the flash operation ended, the cell phone did not want to turn it on, the only function it had and has so far, is that it does not vibrate, it does not turn on, it does not go into flash or fastboot mode, it's dead, it just turns on the red led.
when I try to perform the flash operation again, I simply get the following message when I connect the device.
in the windows device manager, recognizes the phone as "usb serial device (com)".
I searched the net, and I did not find the solution to this problem, I appreciate your attention, and I expect some help.
PD: I already tried the connection with pc companion, and even the function from system symbol of windows with the tool fastboot to flash the boot, with the img.
the problem is that the device does not go into any mode
Click to expand...
Click to collapse
2 times so far, my XA died the same way after trying to flash a mod. Both times I was eventually able to resurrect it by holding down various combinations of buttons while plugging and unplugging, trying different cables, etc. The second time, it wouldn't do anything until the next day, and then it suddenly came to life when using a different cable and plugging into the wall while holding power and volume down. I would try it. I'm not too familiar with flashtool on XA. I have used it for 3 years with my Z1c and never hard bricked a phone with it. Seems like X series have a little bit different rules, but I don't see why your phone would hard-brick just because you didn't wipe a few partitions... Also good idea to check in with FT thread.

If the computer does recognize it, maybe you need to reinstall your usb drivers. If its not, then u have a big problem with it, before making anything you need to see if there is a way to connect it by Fastboot, and install his custom TWRP. if u are able to do that, there is a sollution for you.
Remember always to install your usb flash drivers, and the fastboot drivers too.

Same problem my XA F3113 is dead. The LOG says everything was ok but after disconnect it from PC the phone dies.
Look like exist a way to get it back to life but we need the SCATTERED FILE.
Can somebody share us the SCATTERED FILE of this Model?

Really appreciate this guy....
Awesome person. He had recover my dead XA ultra through online. Just with 500 INR.
wrundawan said:
Whats app me +918147499618 I can help you to fix your dead phone.
Click to expand...
Click to collapse

i have a same problem
please help. my phone f3113 is dead after downgrade

wrundawan said:
Whats app me +918147499618 I can help you to fix your dead phone.
Click to expand...
Click to collapse
Be careful this guy is a cheater he cheated $30 from me

Who the hell has cheated you?
Check your paypal with your open eyes since you had raised claim on your money inside paypal your money was refunded by them. And I am helpless as I didn't got your money.
mballe francois said:
Be careful this guy is a cheater he cheated $30 from me
Click to expand...
Click to collapse

mtk scatter

Hard bricked LG D686 - Tried with test point method phone is detcted by PC now but...

Well I have tried every way to get my LG D686 up and running again before that let me revise how I got here
1 - i rooted the LG D686 in 2016, it worked well for a year until one day I had got a certification boot error msg on start up and had no access to bypassing that except the download mode
2 i downloaded a firmware for D685 instead and flashed it with LG FLASHTOOL. It got hard bricked. When ever I would connect it to the pc it would just connect and disconnect repeatedly. it would not turn on or go in recovery or download mode nothing
3- then i tried to use this method here https://forum.xda-developers.com/optimus-g-pro/help/exclusive-solution-lg-d686-dead-flash-t3330691 . I opened the phone managed to short the resistor to ground and got the PC to recognize the phone in mtk mode. Used SP flash tool flashed it successfully but the phone still wont turn on and even tried a hard reset.
4 - I only want to know if its bricked for good or is there still a chance. The mobile repair shop says hardware and software is gone for a toss , will cost allot to fix, however that was before i tried the testpoint method here https://forum.xda-developers.com/optimus-g-pro/help/exclusive-solution-lg-d686-dead-flash-t3330691. Since I was able to short the resistor on the mother board now the pc detects my phone and never disconnects (in MTK mode) which is a good thing ( i have closed the phone so for now its assembled, i have been able to do a format/downlad 100% successfully with the phone assembled
Do I have a bricked phone for good ? or is there any chance?
I have also attached photos of my progress but my phone will never turn on be it fastboot mode , recovery mode, hard reset, no vibration too. Once I even kept the phone charged for a whole night and checked the battery voltage with a multimeter and it says about 90% charge again that was before i tried this test point method, now if i keep it charged on the charger adaptot the back of the phone right near the sim card slot is never warm as before. its cool which i feel its not being charged now. but if its connected to the PC yes , the area near the simcard slots is warmer, so i guess its getting charged.
I have d686 scatter firmware files from A_1st™ Support Team
I have SP flash tool (tried latest one as well however this version works well for scanning emmc.txt)
drivers are detected properly on PC . i have attached an image for that as well
I apologize if creating this thread is breaking any rule violations but there was no reply on the page/ thread i was seeking help for hence I thought I will start a new thread
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Any one have any idea the hardware needs replacement ???

Is this phone to old for an answer ? Just a simple yes or no . Is it bricked for good that the mother board needs to be replaced ? Or is there a chance I can recover it ?