Related
As the title states: Why does some computer fail to recognize the Universal via USB on bootloader mode?
I recently reformatted my computer, which I usually do once a year. After installing all my apps back and running windows update on my computer, I installed active sync. Performed a normal reset on my computer, attached my Universal and active sync worked.
Here comes the problem: I decided to roll back to my old AKU 2 QTEK ROM. Of course, I know how to use the Ma_Upgrade No ID file. The problem is my computer now fails to recognize my Universal no matter what I do on bootloader mode. To make it worst, I am now stuck at the bootloader mode with my computer not recognizing it. Any suggestions as to why my computer failed to recognize my Universal?
OK, I was able to get the ROM upgrade going again, by removing my SIM Card and 4GB SD Card. I'll post back if I was able to revive my Universal.
So it seems that my computer failed to recognize my Universal because either the SIM Card or SD Card is causing the conflict.
I had the same problem.... I have two computers one with Win Vista (with the same problem) and another with XP sp1. This computer recognize my pda in boot loader, doesn't matter if still SD card and SIM inside....
Sorry for my english and I didn't tell you a solution...
Hi,
i had the same (very annoying) problems but i always was able to get the Universal back into Windows Mobile.
It was very strange because i started the ROM update and than e.g. it did not go in the Bootloader but back in Windows Mobile so i started it again and than it stucked in the Bl. Hardreset and putting the device again into Bl did not help and i was already very annoyed. I tried to plug in and out the USB-cable but it was always telling me SERIAL and not USB and Windows showed this ****ing popup that one device is not recognized or something like that. I tried a trick to let the cable plugged in USB and than reset and it showed me USB but wheter MA_Upgrade (No ID of course) nor mtty were able to find the device. After several trys and resetting and resetting again i was able to bring it into USB but MA_Upgrade did not work.
The only way to bring back the device from the Bl is the method described in XDA-Wiki (http://wiki.xda-developers.com/index.php?pagename=Instructions for those stuck on Boot Screen)
The problem is that this method does work only half. I did the steps until the command "set 14 0" and started MA_Upgrade BUT it always told me that the device is not connected, it never worked. I was already frustrated so i did again the reset and what happend? It started back into Windows Mobile!
So what i think that after using the command set 14 0 AND running MA_Upgrade reactivated the start of Windows Mobile. I tried the steps very often because i tried to find a solution for the contacts between WM5 and AKU 3.2 or higher but the only way is to ActiveSync them. This really works and this is for sure the guaranteed way to get (at least my) the Universal back to Windows.
Btw for the people who are to lazy to use the search function:
The damn ROM upgrade does NOT work on Vista until now! Even not with the Windows Mobile Device Connection Center (or how it's called). I tried several steps on the RTM Vista but it never worked. Don't waste your time on it!
So far from my side, i hope these experience will help some people
I Got It To Work!!!
I was so worried. Wheeeeew! Anyway back to normal again. I got it to work.
My observation is: My computer failed to recognize my Universal because I was using Active Sync Version 4.5 Beta 2 to update my Universal. The solution is to completely uninstall active sync using the windows remove program under control panel, and manually deleting the active sync folder from the hard drive. I then installed Active Sync Version 4.1 and all was well again.
So my next question to all the guys/gals who had problems with upgrading their device because the computer FAILED to recognize their Universal via USB is: ARE YOU USING THE BETA VERSION OF ACTIVE SYNC?
Actually when you try to upgrade with SD card inserted - only then you will get this error - I spend so many hours of GOD prays for my Universal - and after that I just remove a SD card and everything is back to normal
agisofttm said:
Actually when you try to upgrade with SD card inserted - only then you will get this error - I spend so many hours of GOD prays for my Universal - and after that I just remove a SD card and everything is back to normal
Click to expand...
Click to collapse
What is the size of the SD Card you are using? Because when a 2 GB SD Card is inserted, it works just fine. But I experience the error with my 4 GB SD Card.
Unfortunately, i don't share the same luck with all of you.
I've already take out both SD and SIM and try thousand times with ActiVeSync 4.1, 4.2 and 4.5 beta, softreset, hardreset, mtty'ing, but what i got? BIG ZERO.
So my pc always recognise my ppc as "Unknown Device" and there is no, even some slim chance, to get it to work.
Any idea for reviving my uni from black slumber of bootloader screen?
Any help would be appreciated.
DuLanTus said:
Unfortunately, i don't share the same luck with all of you.
I've already take out both SD and SIM and try thousand times with ActiVeSync 4.1, 4.2 and 4.5 beta, softreset, hardreset, mtty'ing, but what i got? BIG ZERO.
So my pc always recognise my ppc as "Unknown Device" and there is no, even some slim chance, to get it to work.
Any idea for reviving my uni from black slumber of bootloader screen?
Any help would be appreciated.
Click to expand...
Click to collapse
use MTTY with "task 28 55aa", "set 14 0", "set 14 9, "set 14 10" and "set 14 20" as described. bootloader screen may be replaced with a blank one, boot it on bootloader mode by "Backlight+Power+Reset"
http://wiki.xda-developers.com/index.php?pagename=Universal_Resets
now upgrade as usual, then If you stuck on the bootloader again after upgrading, try to upgrade the bootloader itself
go to
http://forum.xda-developers.com/showpost.php?p=1255206&postcount=52
i have done all this... but there is something with vista... they do not recognised it when it is on bootlad screen... what should i do can anyone help me??
moixalakix said:
i have done all this... but there is something with vista... they do not recognised it when it is on bootlad screen... what should i do can anyone help me??
Click to expand...
Click to collapse
Hi, yes you could be bang on in saying there is a problem with vista, my machine did that as well, I really thought I'd turned the phone into a brick, luckily I've got an xp machine that let me connect with the tools that everybody else is talking about here, the one I used was UNI_ExitBootloader.exe (from this site somewhere) which sends all the codes for you and it only worked from the xp machine, it totally failed on the vista machine.
Tried all suggestions, but no luck
So a failed upgrade has left my Uni stuck in bootloader mode saying "Serial" and "v1.00". When I plug the thing into my Windoze XP machine with Active Sync 4.5 one of three things happens seemingly at random:
1. My mouse stops working
2. It tells me that the USB device is malfunctioning and cannot be recognized
3. Nothing happens
In all cases the Uni still shows the same "Serial" message.
The Uni has no SD or SIM cards in it. I have tried hard resetting it. I've removed and reinstalled Active Sync. I've rebooted this windoze pile of crap about a thousand times.
Anyone got any ideas?
Thanks,
Saline
Welcome to forums
Have a read here:
http://wiki.xda-developers.com/index.php?pagename=Uni_Stuck_Bootloader_Serial
Hope it helps,
Hi. Thanks for the quick reply. Unfortunately I have already tried the suggestions on that page (that's how I found this thread). As I mentioned above, the device has no similar nor SD in it.
Have you tried to reflash from SD card?
instructions on the link on my sig
Hey everyone! Not a huge poster here however, I've been watching the threads in this forum for the past week or so awaiting root and attempting root myself. After days of attempts I have finally achieved root! I will lay down some of the specifics of what I was working with here and then give some helpful tips that will hopefully help others.
Computer OS - Windows 7 64bit (Installed HTC Sync previously and SDK)
Phone - Hboot .77 (Installed OTA accidently last week) w/ Kingston 2gb microsd
For days I had been trying every single method that I had come across and here is what had worked for me.
**Combined methods from other XDA forum members**
Power off phone with usb plugged in (usb debugging enabled previously)
Ran a batch file called root.bat that I made to run in command prompt consisting of the following (I ran this file before I turned on the phone)
:hello
adb shell
GOTO Hello
Click to expand...
Click to collapse
Hold the optical trackpad button while powering on
Press power once to enter fastboot
Wait for the fastboot to check the sdcard
Press volume down to highlight recovery
Press power to select recovery
Clicked the sdcard in and out
Eventually I entered the recovery screen on the incredible and the command window running my root.bat kept saying
- exec '/system/bin/sh' failed: No such file or directory (2) -
Click to expand...
Click to collapse
I pressed control-C then Y to end the batch file and continued on with the methods listed here
androidforums.com/all-things-root-incredible/98180-prs-complete-rooting-guide.html
Click to expand...
Click to collapse
**KEY NOTES**
I had been cracking at this for the past few days and had plugged the usb from my incredible into the BACK of the computer instead of the front and the FIRST TIME I had done this I was able to obtain root and adb recovery had worked (These are usb ports that are DIRECTLY connected to the mobo and this might have been a huge impact in my success)
Also, I kept running across my drivers detecting my phone in recovery as disk drives so I used the method here
addictivetips.com/windows-tips/how-to-disable-automatic-driver-installation-in-windows-vista/
Click to expand...
Click to collapse
To uninstall the disk drives and the USB Mass storage device and prevent them from automatically installing everytime I uninstalled. Then I went ahead and did a "Update driver manually" and pointed it to the drivers in SDK\USB
One trick I just did that seemed to work was I booted the phone and went into recover (black screen with the red logo). At that point, Device Manager showed two HTC devices listed under 'disk drives'. I uninstalled both of those devices, pulled the battery, popped it back in and went in with down arrow+power. At that point Windows loaded the 'Android 1.0' driver unsuccessfully. Uninstalled that from Device Manager, then did the down arrow + power (and held it down) to go into the black recover screen and *poof* it loaded.
I'm using Windows 7 32bit.
quagmire0 said:
One trick I just did that seemed to work was I booted the phone and went into recover (black screen with the red logo). At that point, Device Manager showed two HTC devices listed under 'disk drives'. I uninstalled both of those devices, pulled the battery, popped it back in and went in with down arrow+power. At that point Windows loaded the 'Android 1.0' driver unsuccessfully. Uninstalled that from Device Manager, then did the down arrow + power (and held it down) to go into the black recover screen and *poof* it loaded.
I'm using Windows 7 32bit.
Click to expand...
Click to collapse
WOW. N1. Proof that worrying about drivers is pointless!
rynosaur said:
WOW. N1. Proof that worrying about drivers is pointless!
Click to expand...
Click to collapse
I think that to an extent it doesn't matter.
It seemed to refuse to work with me if the drivers were being loaded at disk drives. Therefore if the drivers weren't loaded at all and there was nothing installed it could work and if the CORRECT drivers were installed then it would work. But again, for me in my experience it was refusing to work if it had the disk drives were installed as the drivers for recovery.
kentoe said:
I think that to an extent it doesn't matter.
It seemed to refuse to work with me if the drivers were being loaded at disk drives. Therefore if the drivers weren't loaded at all and there was nothing installed it could work and if the CORRECT drivers were installed then it would work. But again, for me in my experience it was refusing to work if it had the disk drives were installed as the drivers for recovery.
Click to expand...
Click to collapse
Ok, but if you look at Unrevoked's newest DIY post, they show a logcat which starts at a card check and ends at adb starting, a five second gap. This is internal stuff, not going to the host/usb -- at least not listed in the logcat. If this exploit depended on host intervention at all, I'm guessing someone would have written a linux or windows script/program to talk to the DI. Rather, all the PC can do is try to open an adb session, it's like knocking at a door -- you can't make the person home no matter how well or correctly you knock, you just hope they'll answer.
When I obtained adb shell, had all three devices show up in Device Manager: ADB Composite (I used the API 8 driver), Generic Volume G:\ and Generic Volume H:\ -- drive letter specific to my windows install, of course. All hands were on deck. The glitch happens between the software, hardware and sdcard.
In any case, I'm glad you were successful!
rynosaur said:
Ok, but if you look at Unrevoked's newest DIY post, they show a logcat which starts at a card check and ends at adb starting, a five second gap. This is internal stuff, not going to the host/usb -- at least not listed in the logcat. If this exploit depended on host intervention at all, I'm guessing someone would have written a linux or windows script/program to talk to the DI. Rather, all the PC can do is try to open an adb session, it's like knocking at a door -- you can't make the person home no matter how well or correctly you knock, you just hope they'll answer.
When I obtained adb shell, had all three devices show up in Device Manager: ADB Composite (I used the API 8 driver), Generic Volume G:\ and Generic Volume H:\ -- drive letter specific to my windows install, of course. All hands were on deck. The glitch happens between the software, hardware and sdcard.
In any case, I'm glad you were successful!
Click to expand...
Click to collapse
Ahh, okay. Well whatevs, yeah I'm glad I'm rooted now! =D It was probably the connection with the front usb ports vs the back usb ports on my computer since the back are directly on the mobo. It worked the first time I switched it to the direct USB ports.
So glad I got lamppu, wifi tether, and removed city id along with obtaining titanium backup!
I was also trying to get root for a few days and had some issues. I eventually got in on my 4th MicroSD card try- which was a junky 1GB that wasn't even labeled for speed...
I tried a16GB Class 2, 8GB class 4, 4GB class 4 and none would stay with 'device not found'- even after trying for 20+ times on each. My next step was to buy a class 6, but a random 1GB I had laying around worked. It connected after the 1st attempt with the 1GB card.
Another note- I got the '/system/bin/sh' message about 30 seconds after it went into recovery mode- not right at the start as I see it happening in the videos.
Easiest way is to yank the battery and start over if you don't get it; I used the vol down + power start up option.
Nothing worked for me. Tried all methods with lots of cards.
Stock SanDisk 2gb C4
Lexar 8gb C4
Lexar 8gb C6
DaneElec 4gb C4 (same as PNY 4/4 and Kingston 4/4)
As I was about to put my Inc for sale on Ebay. NiX threw out a suggestion on IRC. I tried it w/ the DaneElec and it worked.
It worked first try and every try since. Tried it with the stock sandisk 2/2 and no go. Haven't tried the Lexars.
Give it a shot. Good luck.
loop shell / Vol- + Power. / Hboot / wait for 4secs / insert card / highlight recovery / hit power + count to 3 or 5 and insert usb / wait till 10secs after /!\
Thanks OP - Using the oldest/slowest card I have (old 1gb Corsair card formatted Fat32), enabling the driver local policy you mentioned, pulling the battery while phone was on, and the eject method described above - I finally got in. I have no idea if it was pure luck or if it had anything to do with the above, but yours was the last thread I read so you get a thanks.
**EDIT**
After trying to get back in after realizing I needed to remove any apps before rebooting, I once again have zero luck getting in... so I'm leaning towards the complete chance/luck idea.
seanmcd72 said:
Thanks OP - Using the oldest/slowest card I have (old 1gb Corsair card formatted Fat32), enabling the driver local policy you mentioned, pulling the battery while phone was on, and the eject method described above - I finally got in. I have no idea if it was pure luck or if it had anything to do with the above, but yours was the last thread I read so you get a thanks.
Click to expand...
Click to collapse
You're welcome! I'm glad my information has helped!
i have a hard bricked s3 at&t i747 model. it bricked after i used the wrong rom which was for the i9300. my phone will not boot no lights no sign of life. when i connect to the computer the device is recognized as QHSUSB_DLOAD. this mind you is after i sent my phone for a jtag repair and it was successfully resurrected via the riff box but it wont go into download mode. any advice????
nick1386 said:
i have a hard bricked s3 at&t i747 model. it bricked after i used the wrong rom which was for the i9300. my phone will not boot no lights no sign of life. when i connect to the computer the device is recognized as QHSUSB_DLOAD. this mind you is after i sent my phone for a jtag repair and it was successfully resurrected via the riff box but it wont go into download mode. any advice????
Click to expand...
Click to collapse
So you hard bricked, sent for jtag, received working and now won't go into download mode?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I recently went through something similar; I hard bricked my phone (I deleted the check that made sure it was the right phone). I sent it to MobileTechVideos.com for JTag repair and they did a great job and brought the phone back to life (I don't want to sound like an advertisement, but seriously, they were awesome in just about every way).
However, they seemed to just restore it to the last boot-able state. That last state was not completely stable (I had tried installing the rom, then installed Google apps that matched my the rom but not what was originally installed, it booted but apps just didn't work, tried re-installing the rom, noticed that the rom install error'ed out, deleted the check for the correct cell phone, and then bricked it). So when I got the phone back, it was in the state with the bad Google apps; I had to go back and install the correct version.
Long story short, think back to exactly what state the phone was in before it was hard bricked, and try to work backwards from there.
KorGuy123 said:
So you hard bricked, sent for jtag, received working and now won't go into download mode?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
i sent it to repair but the technician could not get the phone to reboot after successful jtag.
Tr to force download like this:
Have phone hooked up with no battery
Hold Vol Down + Home
Insert battery still holding those two keys
Please I need help, I know is not te correct place but hopes you can help me. I have an Galaxy Note, flashing a ROM my phone turned off and I cannot boot, charge or going any recovery or download mode. Today morning I tried JTAG and device wasn´t recognize, how can I fix it? What problems there are for JTAG doesn´t recognize device?
Qhsusb_dload for Tmobile T999 Fix
Hello,
I bricked my phone trying to put the International S4 Revolution rom on it. It had the qhsusb_dload driver request on the computer. It would not power on or connect to the computer. I tried everything and I could not get it into download mode. I tried a usb jig to no avail. After spending 2 nights trying to unbrick my Samsung Galaxy SGH T999 I finally was unable to unbrick it without using Ubuntu or Linux software.
I had trouble with those types of software because I could not fully understand the coding and my computer is a slower laptop from 2007 and it is very laggy and frustrating to use.
To unbrick my phone, I made a image loadable sd card with the debrick image from Tmobile. To do this I used my 16 gb sd card that I kept in my tablet. I copied all of the files off of it to a folder on my desktop and then I deleted everything off of the sd card. Then I quick formated the sd drive. I downloaded the Tmobile Debrick Image' Then I downloaded Win32 Disk Imager. I selected the image file of the debrick image and then selected the drive my sd card was on and then hit write.
I then took the sd card out of my tablet and I put it in my bricked phone. After 3 seconds my phone lit up and went into download mode where I flashed the stock Tmobile rom for my Samsung S3 T999 using Odin 3.07 and voila.. I am back in service. I created this post because I am a novice at this type of thing and none of your forums where able to help me. All of them kept persuading me to send it to JTAG for a fee. People try this first before you pay anyone.
shines915 said:
Hello,
I bricked my phone trying to put the International S4 Revolution rom on it. It had the qhsusb_dload driver request on the computer. It would not power on or connect to the computer. I tried everything and I could not get it into download mode. I tried a usb jig to no avail. After spending 2 nights trying to unbrick my Samsung Galaxy SGH T999 I finally was unable to unbrick it without using Ubuntu or Linux software.
I had trouble with those types of software because I could not fully understand the coding and my computer is a slower laptop from 2007 and it is very laggy and frustrating to use.
To unbrick my phone, I made a image loadable sd card with the debrick image from Tmobile. To do this I used my 16 gb sd card that I kept in my tablet. I copied all of the files off of it to a folder on my desktop and then I deleted everything off of the sd card. Then I quick formated the sd drive. I downloaded the Tmobile Debrick Image' Then I downloaded Win32 Disk Imager. I selected the image file of the debrick image and then selected the drive my sd card was on and then hit write.
I then took the sd card out of my tablet and I put it in my bricked phone. After 3 seconds my phone lit up and went into download mode where I flashed the stock Tmobile rom for my Samsung S3 T999 using Odin 3.07 and voila.. I am back in service. I created this post because I am a novice at this type of thing and none of your forums where able to help me. All of them kept persuading me to send it to JTAG for a fee. People try this first before you pay anyone.
Click to expand...
Click to collapse
Thanks bro, this actually works!
Thanks dude!
shines915 said:
Hello,
I bricked my phone trying to put the International S4 Revolution rom on it. It had the qhsusb_dload driver request on the computer. It would not power on or connect to the computer. I tried everything and I could not get it into download mode. I tried a usb jig to no avail. After spending 2 nights trying to unbrick my Samsung Galaxy SGH T999 I finally was unable to unbrick it without using Ubuntu or Linux software.
I had trouble with those types of software because I could not fully understand the coding and my computer is a slower laptop from 2007 and it is very laggy and frustrating to use.
To unbrick my phone, I made a image loadable sd card with the debrick image from Tmobile. To do this I used my 16 gb sd card that I kept in my tablet. I copied all of the files off of it to a folder on my desktop and then I deleted everything off of the sd card. Then I quick formated the sd drive. I downloaded the Tmobile Debrick Image' Then I downloaded Win32 Disk Imager. I selected the image file of the debrick image and then selected the drive my sd card was on and then hit write.
I then took the sd card out of my tablet and I put it in my bricked phone. After 3 seconds my phone lit up and went into download mode where I flashed the stock Tmobile rom for my Samsung S3 T999 using Odin 3.07 and voila.. I am back in service. I created this post because I am a novice at this type of thing and none of your forums where able to help me. All of them kept persuading me to send it to JTAG for a fee. People try this first before you pay anyone.
Click to expand...
Click to collapse
Dude you are a lifesaver! I cannot thank you enough!
Which model?
TH3F4LL3N said:
Dude you are a lifesaver! I cannot thank you enough!
Click to expand...
Click to collapse
which model did u use , i am trying with i747m but nothing is happening.
---------- Post added at 08:21 AM ---------- Previous post was at 08:20 AM ----------
frohyu said:
Thanks bro, this actually works!
Click to expand...
Click to collapse
what model is ur phone? not working on i747m.
carlos1984 said:
which model did u use , i am trying with i747m but nothing is happening.
---------- Post added at 08:21 AM ---------- Previous post was at 08:20 AM ----------
what model is ur phone? not working on i747m.
Click to expand...
Click to collapse
My phone is the US version, the i747. You have the Canadian variant. That's what the m means.
TH3F4LL3N said:
My phone is the US version, the i747. You have the Canadian variant. That's what the m means.
Click to expand...
Click to collapse
From what i was told the i747 and i747m is the same cause I flashed attroms on it. Did you use the win32diskimager or a linux distro. I think either my sd card is the problem or windows, when i write the img, the sd shows one folder namded "image" with 70 something folders in it.
carlos1984 said:
From what i was told the i747 and i747m is the same cause I flashed attroms on it. Did you use the win32diskimager or a linux distro. I think either my sd card is the problem or windows, when i write the img, the sd shows one folder namded "image" with 70 something folders in it.
Click to expand...
Click to collapse
I used win32diskimager. I got it to work fine for a while, but I couldn't get booted up without the card, no matter how many times I flashed the bootloader. I ended up taking to AT&T, where they gave me a new one because even the JTAG couldn't bring it back. I wish I could be of more assistance, mate.
shines915 said:
Hello,
I bricked my phone trying to put the International S4 Revolution rom on it. It had the qhsusb_dload driver request on the computer. It would not power on or connect to the computer. I tried everything and I could not get it into download mode. I tried a usb jig to no avail. After spending 2 nights trying to unbrick my Samsung Galaxy SGH T999 I finally was unable to unbrick it without using Ubuntu or Linux software.
I had trouble with those types of software because I could not fully understand the coding and my computer is a slower laptop from 2007 and it is very laggy and frustrating to use.
To unbrick my phone, I made a image loadable sd card with the debrick image from Tmobile. To do this I used my 16 gb sd card that I kept in my tablet. I copied all of the files off of it to a folder on my desktop and then I deleted everything off of the sd card. Then I quick formated the sd drive. I downloaded the Tmobile Debrick Image' Then I downloaded Win32 Disk Imager. I selected the image file of the debrick image and then selected the drive my sd card was on and then hit write.
I then took the sd card out of my tablet and I put it in my bricked phone. After 3 seconds my phone lit up and went into download mode where I flashed the stock Tmobile rom for my Samsung S3 T999 using Odin 3.07 and voila.. I am back in service. I created this post because I am a novice at this type of thing and none of your forums where able to help me. All of them kept persuading me to send it to JTAG for a fee. People try this first before you pay anyone.
Click to expand...
Click to collapse
This gives me hope. My phone randomly hardbricked after flashing CWM from Rom Manager. I flashed it from the app, turned the phone off, and then it wouldn't turn on. I want to try this, does anyone know if this works with the at&t i747? And what debrick image should I use for the at&t version?
---------- Post added at 10:55 PM ---------- Previous post was at 10:46 PM ----------
TH3F4LL3N said:
I used win32diskimager. I got it to work fine for a while, but I couldn't get booted up without the card, no matter how many times I flashed the bootloader. I ended up taking to AT&T, where they gave me a new one because even the JTAG couldn't bring it back. I wish I could be of more assistance, mate.
Click to expand...
Click to collapse
Which debrick image did you use?
shines915 said:
Hello,
I bricked my phone trying to put the International S4 Revolution rom on it. It had the qhsusb_dload driver request on the computer. It would not power on or connect to the computer. I tried everything and I could not get it into download mode. I tried a usb jig to no avail. After spending 2 nights trying to unbrick my Samsung Galaxy SGH T999 I finally was unable to unbrick it without using Ubuntu or Linux software.
I had trouble with those types of software because I could not fully understand the coding and my computer is a slower laptop from 2007 and it is very laggy and frustrating to use.
To unbrick my phone, I made a image loadable sd card with the debrick image from Tmobile. To do this I used my 16 gb sd card that I kept in my tablet. I copied all of the files off of it to a folder on my desktop and then I deleted everything off of the sd card. Then I quick formated the sd drive. I downloaded the Tmobile Debrick Image' Then I downloaded Win32 Disk Imager. I selected the image file of the debrick image and then selected the drive my sd card was on and then hit write.
I then took the sd card out of my tablet and I put it in my bricked phone. After 3 seconds my phone lit up and went into download mode where I flashed the stock Tmobile rom for my Samsung S3 T999 using Odin 3.07 and voila.. I am back in service. I created this post because I am a novice at this type of thing and none of your forums where able to help me. All of them kept persuading me to send it to JTAG for a fee. People try this first before you pay anyone.
Click to expand...
Click to collapse
Hi,
Thanks for useful post and a description!! When you were turning on the phone with the SD card in which button combination were you pressing:
1) Were you just holding power button for 3 seconds OR
2) Push and release power button and after 3 seconds you see the screen OR
3) You were you pushing a combo: [POWER_BTN] + [HOME] + [VOL_DOWN]?
also where did you get a debrick image?
Please clarify and thanks for help!!
shines915 said:
Hello,
I bricked my phone trying to put the International S4 Revolution rom on it. It had the qhsusb_dload driver request on the computer. It would not power on or connect to the computer. I tried everything and I could not get it into download mode. I tried a usb jig to no avail. After spending 2 nights trying to unbrick my Samsung Galaxy SGH T999 I finally was unable to unbrick it without using Ubuntu or Linux software.
I had trouble with those types of software because I could not fully understand the coding and my computer is a slower laptop from 2007 and it is very laggy and frustrating to use.
To unbrick my phone, I made a image loadable sd card with the debrick image from Tmobile. To do this I used my 16 gb sd card that I kept in my tablet. I copied all of the files off of it to a folder on my desktop and then I deleted everything off of the sd card. Then I quick formated the sd drive. I downloaded the Tmobile Debrick Image' Then I downloaded Win32 Disk Imager. I selected the image file of the debrick image and then selected the drive my sd card was on and then hit write.
I then took the sd card out of my tablet and I put it in my bricked phone. After 3 seconds my phone lit up and went into download mode where I flashed the stock Tmobile rom for my Samsung S3 T999 using Odin 3.07 and voila.. I am back in service. I created this post because I am a novice at this type of thing and none of your forums where able to help me. All of them kept persuading me to send it to JTAG for a fee. People try this first before you pay anyone.
Click to expand...
Click to collapse
You are a life save, for real. Thank you so much! Only post to actually help. Simple and gets to the point fast. :cyclops:
Can’t access to Download Mode or Recovery Mode after bricking AT&T Galaxy S3 i744 4.3
Hi I have (had) a AT&T galaxy S3 i747 with android 4.1.1
{
"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"
}
Because the phone is in another country I couldn’t update it by OTA to android 4.3
So I started to read forums that said how to Update AT&T S3 i747 to android 4.3 (I747UCUEMJB)
The S3 was not Root
I installed all the phone drivers in the computer
This is what I did: (http://forum.xda-developers.com/showpost.php?p=52341582&postcount=38)
- Use Odin 3.07
- Check Auto Reboot and Re-Partition, and uncheck all the boxes
- I put my phone in USB debugging in the developer options
- I turned it off
- Started to put the phone on Download Mode pressing volume DW+home+power button at the same time
- In Odin on the PDA box I checked and loaded the file .tar.md5 (I747UCUEMJB_2024954_REV04_user_low_ship.tar.md5 )
- Pressed the button Start
The installation seemed to go right, the program never showed anything weird.
When the Programs finished the installation the phone turned off and then turned on and show the logo of android (seemed to be lying down or inclined) and after that it turned off.
The computer showed that something was connected (QHSUSB_DLOAD) but couldn’t install any driver, so I disconnected it of the computer.
I couldn’t turn on the phone :crying:, I took the battery out and put it in and tried to start the phone and nothing happened, I tried pressing any button to access to recovery o download mode and none of this worked.
I started to search forums that talk about restart or turn on a brick AT&T S3 i747
I found one (http://forum.xda-developers.com/showthread.php?t=2549068) that said to download a image (debrick-SGH-I747U-CUEMJB3.img) and using the program “Win32DiskImager” to put the image inside of a micro SD to make the phone turn on,
I put the micro SD inside the phone and when I pushed the power button for almost 3 seconds it Turned on , the phone seems to be fine an it has android 4.3 (I747UCUEMJB) installed.
I can use it normally so far.
But the problem is that I can’t turn on the phone if the micro SD card is not inserted on the phone.
Without the micro SD inside don’t show any sign of life
When the micro SD is inside I can turn on the phone and use its apps.
I have tried to enter to Recovery mode or Download mode with the micro SD inside but the phone only show what its supposed to happen for 1 second then turns off and then turns on by its own (after that I can use it normally)
Does anyone know how can I Fix my phone ?
How can I boot my phone without using the micro SD card?
How can I access to download mode?
And if I could access to download mode what should I do next ?
The only files I have now are:
Odin3 v3.07
I747UCUEMJB_2024954_REV04_user_low_ship.tar.md5( 905 Mb)
debrick-SGH-I747U-CUEMJB3.img (80 Mb)
Maralex1520 said:
Hi I have (had) a AT&T galaxy S3 i747 with android 4.1.1 View attachment 2790313
Because the phone is in another country I couldn’t update it by OTA to android 4.3
So I started to read forums that said how to Update AT&T S3 i747 to android 4.3 (I747UCUEMJB)
The S3 was not Root
I installed all the phone drivers in the computer
This is what I did: (http://forum.xda-developers.com/showpost.php?p=52341582&postcount=38)
- Use Odin 3.07
- Check Auto Reboot and Re-Partition, and uncheck all the boxes
- I put my phone in USB debugging in the developer options
- I turned it off
- Started to put the phone on Download Mode pressing volume DW+home+power button at the same time View attachment 2790314 View attachment 2790315
- In Odin on the PDA box I checked and loaded the file .tar.md5 (I747UCUEMJB_2024954_REV04_user_low_ship.tar.md5 )
- Pressed the button Start View attachment 2790316
The installation seemed to go right, the program never showed anything weird. View attachment 2790317
When the Programs finished the installation the phone turned off and then turned on and show the logo of android (seemed to be lying down or inclined) and after that it turned off.
The computer showed that something was connected (QHSUSB_DLOAD) but couldn’t install any driver, so I disconnected it of the computer.
I couldn’t turn on the phone :crying:, I took the battery out and put it in and tried to start the phone and nothing happened, I tried pressing any button to access to recovery o download mode and none of this worked.
I started to search forums that talk about restart or turn on a brick AT&T S3 i747
I found one (http://forum.xda-developers.com/showthread.php?t=2549068) that said to download a image (debrick-SGH-I747U-CUEMJB3.img) and using the program “Win32DiskImager” to put the image inside of a micro SD to make the phone turn on,
I put the micro SD inside the phone and when I pushed the power button for almost 3 seconds it Turned on , the phone seems to be fine an it has android 4.3 (I747UCUEMJB) installed.View attachment 2790318
I can use it normally so far.
But the problem is that I can’t turn on the phone if the micro SD card is not inserted on the phone.
Without the micro SD inside don’t show any sign of life
When the micro SD is inside I can turn on the phone and use its apps.
I have tried to enter to Recovery mode or Download mode with the micro SD inside but the phone only show what its supposed to happen for 1 second then turns off and then turns on by its own (after that I can use it normally)
Does anyone know how can I Fix my phone ?
How can I boot my phone without using the micro SD card?
How can I access to download mode?
And if I could access to download mode what should I do next ?
The only files I have now are:
Odin3 v3.07
I747UCUEMJB_2024954_REV04_user_low_ship.tar.md5( 905 Mb)
debrick-SGH-I747U-CUEMJB3.img (80 Mb)
Click to expand...
Click to collapse
same problem facing by me, no sign of life without sd card, is there any fix for this?
I'm bricked!!!
shines915 said:
Hello,
I bricked my phone trying to put the International S4 Revolution rom on it. It had the qhsusb_dload driver request on the computer. It would not power on or connect to the computer. I tried everything and I could not get it into download mode. I tried a usb jig to no avail. After spending 2 nights trying to unbrick my Samsung Galaxy SGH T999 I finally was unable to unbrick it without using Ubuntu or Linux software.
I had trouble with those types of software because I could not fully understand the coding and my computer is a slower laptop from 2007 and it is very laggy and frustrating to use.
To unbrick my phone, I made a image loadable sd card with the debrick image from Tmobile. To do this I used my 16 gb sd card that I kept in my tablet. I copied all of the files off of it to a folder on my desktop and then I deleted everything off of the sd card. Then I quick formated the sd drive. I downloaded the Tmobile Debrick Image' Then I downloaded Win32 Disk Imager. I selected the image file of the debrick image and then selected the drive my sd card was on and then hit write.
I then took the sd card out of my tablet and I put it in my bricked phone. After 3 seconds my phone lit up and went into download mode where I flashed the stock Tmobile rom for my Samsung S3 T999 using Odin 3.07 and voila.. I am back in service. I created this post because I am a novice at this type of thing and none of your forums where able to help me. All of them kept persuading me to send it to JTAG for a fee. People try this first before you pay anyone.
Click to expand...
Click to collapse
Hey I tried this method[/watch?v=tWnHesLPikQ][/url] "that's a youtube link"
(I think it's the same as yours) but I'm still bricked, I tried installing s4 revolution that's why I'm bricked, can you please help me.
Can you please give the image loadable sd card
shines915 said:
Hello,
I bricked my phone trying to put the International S4 Revolution rom on it. It had the qhsusb_dload driver request on the computer. It would not power on or connect to the computer. I tried everything and I could not get it into download mode. I tried a usb jig to no avail. After spending 2 nights trying to unbrick my Samsung Galaxy SGH T999 I finally was unable to unbrick it without using Ubuntu or Linux software.
I had trouble with those types of software because I could not fully understand the coding and my computer is a slower laptop from 2007 and it is very laggy and frustrating to use.
To unbrick my phone, I made a image loadable sd card with the debrick image from Tmobile. To do this I used my 16 gb sd card that I kept in my tablet. I copied all of the files off of it to a folder on my desktop and then I deleted everything off of the sd card. Then I quick formated the sd drive. I downloaded the Tmobile Debrick Image' Then I downloaded Win32 Disk Imager. I selected the image file of the debrick image and then selected the drive my sd card was on and then hit write.
I then took the sd card out of my tablet and I put it in my bricked phone. After 3 seconds my phone lit up and went into download mode where I flashed the stock Tmobile rom for my Samsung S3 T999 using Odin 3.07 and voila.. I am back in service. I created this post because I am a novice at this type of thing and none of your forums where able to help me. All of them kept persuading me to send it to JTAG for a fee. People try this first before you pay anyone.
Click to expand...
Click to collapse
hey I'm really stucked, can you please give image loadable sd card because I tried this methode and it didn't worked :/
My LG E980 is bricked. I can access download mode and that is it! I am unable to boot into recovery,
and the hard reset screen simply sits there forever. My computer only recognizes my device as an "unknown usb device."
I'm unsure what can be done about this, but I feel like this is better than the infamous QHSUB icon displayed when the device cannot be recovered.
Does anyone have a remedy for this problem?? I have GOT to fix this phone and can't afford to Jtag the device, but I'm losing hope that this is possible, PLEASE help. :crying:
Have you installed the LG drivers for your pc and tried the unbrick method?
Yeah dude there's an unbrick method. If this doesn't work just sell the phone on Ebay. http://forum.xda-developers.com/showthread.php?t=2302660
There is never a time when this device cant be recovered. even the qhusb is a fairly simple fix. ill go ahead and make a sdcard boot image tonight. do you have a 32gb sdcard? (or larger) and an sdcard reader, if you have those two things i can make an unbrick.img that you flash toi the sdcard and put in the non-booting phone and it will get you to download mode/recovery mode. ill have to check out what partitions are where as i dont wish to include my efs along with it all .
twill1987 said:
My LG E980 is bricked. I can access download mode and that is it! I am unable to boot into recovery,
and the hard reset screen simply sits there forever. My computer only recognizes my device as an "unknown usb device."
I'm unsure what can be done about this, but I feel like this is better than the infamous QHSUB icon displayed when the device cannot be recovered.
Does anyone have a remedy for this problem?? I have GOT to fix this phone and can't afford to Jtag the device, but I'm losing hope that this is possible, PLEASE help. :crying:
Click to expand...
Click to collapse
Happened to me.
1. With the phone on download mode and plugged in the computer; uninstall the unknown device on your computer using device manager. The computer should try to get the drivers for your phone.
2. If it doesn't. Repeat step one and install the drivers first.
That worked for me hopefully I'll work for you.
Sent from my LG-E980 using XDA Premium 4 mobile app
Yes
riki126 said:
Have you installed the LG drivers for your pc and tried the unbrick method?
Click to expand...
Click to collapse
Yes I tried that. The drivers won't install. I even used another windows 8 computer my roommate has and switched out
the usb cables, still came back "unknown device"
shabbypenguin said:
There is never a time when this device cant be recovered. even the qhusb is a fairly simple fix. ill go ahead and make a sdcard boot image tonight. do you have a 32gb sdcard? (or larger) and an sdcard reader, if you have those two things i can make an unbrick.img that you flash toi the sdcard and put in the non-booting phone and it will get you to download mode/recovery mode. ill have to check out what partitions are where as i dont wish to include my efs along with it all .
Click to expand...
Click to collapse
I do have a 16gb sd card, but I can pick up at 32 gb sd at my local best buy. I have an Asus laptop running windows 8 and it has an SD card reader. I am a little confused (semi-noob) as to how this will work because my phone will boot up, and the led changes colors on the home button for about 4 seconds and then the light stops flashing. The phone is stuck on the LG boot screen, and there is no way out of it but to pull the battery or to reset with power button. Of course no recovery as previously mentioned. I really just want to get back to stock, but I can't manage to get both the windows 8 computers I've tried to detect the phone in download mode. Ever since I switched to the Candykat rom 4.4 the computer wasn't able to recognize the phone, even when the phone was fully functional inside the rom.
I have tried it on my dads windows 7 laptop as well with no dice. Instaled LG drivers, uninstalled LG Drivers, uninstalled device from the Device Manager. I've done everything I could think of. I previously was in a Philz touch recovery, but every rom I tried to flash wouldn't work. I tried to flash another recovery from inside it and then the device bricked like it is now. What a head ache. If you think this method would work, I am more than willing to try it, just unfamiliar with what I need to do on my end.
Okay
stulzerl said:
Happened to me.
1. With the phone on download mode and plugged in the computer; uninstall the unknown device on your computer using device manager. The computer should try to get the drivers for your phone.
2. If it doesn't. Repeat step one and install the drivers first.
That worked for me hopefully I'll work for you.
Sent from my LG-E980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I will give your method a shot, but I have done this a lot already. The only thing I can think of is I usually unplug the phone from the computer right after deleting the drivers and uninstalling in device manager. Maybe I should just leave the phone plugged in and see if the computer automatically downloads the drivers, but I don't think it will because I've tried to update the drivers before. It gives me an error code "10" and says the device has malfunction or stopped working This phone has been undetectable via USB since flashing the candykat 4.4 rom. Every computer I've tried (3) and every USB cable (3 again) has displayed it as an "unknown device"
twill1987 said:
I will give your method a shot, but I have done this a lot already. The only thing I can think of is I usually unplug the phone from the computer right after deleting the drivers and uninstalling in device manager. Maybe I should just leave the phone plugged in and see if the computer automatically downloads the drivers, but I don't think it will because I've tried to update the drivers before. It gives me an error code "10" and says the device has malfunction or stopped working This phone has been undetectable via USB since flashing the candykat 4.4 rom. Every computer I've tried (3) and every USB cable (3 again) has displayed it as an "unknown device"
Click to expand...
Click to collapse
I've had similar issues when i had my optimus g. I had to use a pc with xp to flasht he phone, dunno why though. You could give that a shot.
twill1987 said:
I do have a 16gb sd card, but I can pick up at 32 gb sd at my local best buy. I have an Asus laptop running windows 8 and it has an SD card reader. I am a little confused (semi-noob) as to how this will work because my phone will boot up, and the led changes colors on the home button for about 4 seconds and then the light stops flashing. The phone is stuck on the LG boot screen, and there is no way out of it but to pull the battery or to reset with power button. Of course no recovery as previously mentioned. I really just want to get back to stock, but I can't manage to get both the windows 8 computers I've tried to detect the phone in download mode. Ever since I switched to the Candykat rom 4.4 the computer wasn't able to recognize the phone, even when the phone was fully functional inside the rom.
I have tried it on my dads windows 7 laptop as well with no dice. Instaled LG drivers, uninstalled LG Drivers, uninstalled device from the Device Manager. I've done everything I could think of. I previously was in a Philz touch recovery, but every rom I tried to flash wouldn't work. I tried to flash another recovery from inside it and then the device bricked like it is now. What a head ache. If you think this method would work, I am more than willing to try it, just unfamiliar with what I need to do on my end.
Click to expand...
Click to collapse
I dont know lg's download mode, kdz, tot etc all that well. im more of a samsung guy. however qualcomm since the s4 chipset has allowed for sdcards that are properly formatted to boot the os instead of the internal emmc. here is a decent guide, just need to make teh image for this device. this will let your device boot no matter how bad it gets you are welcome to try with 16gb, the rule of thumb i know of is as big as teh emmc is use that same size or larger sdcard, however some people have had sucess withs maller, just not many that i know of. http://forum.xda-developers.com/showthread.php?t=2439367
however afaik the only way to reflash teh bootloader partitions is via kdz/download mode so perhaps the sdcard will let you get into that mode and then you can flash, so long as you keep your sdcard like that it will boot fully, but in order ot get your sdcard back you need to repair teh files on your phone .
Thanks
WeActOnImpulse said:
Yeah dude there's an unbrick method. If this doesn't work just sell the phone on Ebay. http://forum.xda-developers.com/showthread.php?t=2302660
Click to expand...
Click to collapse
I have tried this and unfortunately since the USB drivers aren't detected by the computer there is no way for me to flash back to stock.
Thanks for the information though, I appreciate it.
shabbypenguin said:
I dont know lg's download mode, kdz, tot etc all that well. im more of a samsung guy. however qualcomm since the s4 chipset has allowed for sdcards that are properly formatted to boot the os instead of the internal emmc. here is a decent guide, just need to make teh image for this device. this will let your device boot no matter how bad it gets you are welcome to try with 16gb, the rule of thumb i know of is as big as teh emmc is use that same size or larger sdcard, however some people have had sucess withs maller, just not many that i know of. http://forum.xda-developers.com/showthread.php?t=2439367
however afaik the only way to reflash teh bootloader partitions is via kdz/download mode so perhaps the sdcard will let you get into that mode and then you can flash, so long as you keep your sdcard like that it will boot fully, but in order ot get your sdcard back you need to repair teh files on your phone .
Click to expand...
Click to collapse
Wow, that sounds awesome. I followed most of that. I access download mode on the device by pressing vol up and down simultaneously and plugging in the usb cable. I am more willing to try this, and if it works I will pay you from my paypal. I guess all I need now are those files to run to the sd card. I read the tutorial you posted for the samsung and downloaded the windows disk manager. I am eager to try this method, though it is admittedly very new to me.. If you can post those files, I will follow the instructions you give and pay you a little bit of money for your help!
I am a broke college student so it won't be much, but I really appreciate your response and information on this method with the qualcomm s4.
Here is the unbrick image. follow the guide for your platform (gunna guess windows) and write this to your sdcard after backing it up. from there you need to restore your partitions by flashing them .
https://mega.co.nz/#!YB5xWQ7Y!Qcnx9UmcNn-f6skfiIFN-jd0EeYxdmrQGA1zzP5hfA0
Just wrote it to sd card
shabbypenguin said:
Here is the unbrick image. follow the guide for your platform (gunna guess windows) and write this to your sdcard after backing it up. from there you need to restore your partitions by flashing them .
https://mega.co.nz/#!YB5xWQ7Y!Qcnx9UmcNn-f6skfiIFN-jd0EeYxdmrQGA1zzP5hfA0
Click to expand...
Click to collapse
Okay so I bought the 32 gb sd card. Just wrote the .img file you sent me to the sd card.
I powered on the phone and nothing happened, I got the same LG screen where the led flashes and then stops.
I followed that guide, but am I supposed to go to download mode instead of just powering on the device?
I got a little confused by the samsung jargon lol. I just want to know after I've written the unbrick.zip to the sd card
how do I get my phone to recognize the card is there? And once I am able to do that how do I "restore my partitions by flashing them?"
I do have the factory firmware set to flash through lg flashtool, but the phone can't be detected of course due to the usb issue.
Just want to say thanks for walking me through it this far, I feel like I'm close hopefully but unsure what to do next.
twill1987 said:
Okay so I bought the 32 gb sd card. Just wrote the .img file you sent me to the sd card.
I powered on the phone and nothing happened, I got the same LG screen where the led flashes and then stops.
I followed that guide, but am I supposed to go to download mode instead of just powering on the device?
I got a little confused by the samsung jargon lol. I just want to know after I've written the unbrick.zip to the sd card
how do I get my phone to recognize the card is there? And once I am able to do that how do I "restore my partitions by flashing them?"
I do have the factory firmware set to flash through lg flashtool, but the phone can't be detected of course due to the usb issue.
Just want to say thanks for walking me through it this far, I feel like I'm close hopefully but unsure what to do next.
Click to expand...
Click to collapse
you wrote the image to the sdcard? i wonder if its because you still have the low level bootloaders that it may not be booting from the sdcard, normally this is done to fix qhusb errored devices. as for restoring the partitions all you would need to do is one its booted up push the unbrick image to the phone and use rooted adb shell to write it back onto your phone.
Possible hope??
shabbypenguin said:
you wrote the image to the sdcard? i wonder if its because you still have the low level bootloaders that it may not be booting from the sdcard, normally this is done to fix qhusb errored devices. as for restoring the partitions all you would need to do is one its booted up push the unbrick image to the phone and use rooted adb shell to write it back onto your phone.
Click to expand...
Click to collapse
I meant I used the windows tool to write the debrick.img to the sd card. But no dice, the device isn't recognised.
However! I installed a driver clean up tool and now if I plug in the device it is recognized as Android Original ADB Interface.
The LG Flashtools even says the port is ready! But I get the error code "10" "device cannot start, A request for the USB device descriptor failed."
So now I am stuck on that instead lol. This just sucks.
that sucks about the sdcard, it must be because you arent "truly" bricked. sorry i thought it would help ya :/.
What is the driver repair tool you used? I know this thread is old but I'm having the same problem. I was trying to root my E980 and now my computer wont recognize my device. The phone works perfect, its just when I plug it in to the computer it isnt recognized. How can I fix this?
+1
Just wondering if anyone's come across a solution to this besides a sledge hammer... been having the same "Code 10: Device failed to start" when in Download Mode, though Windows finds a driver fine when the phone is stuck on the LG screen... doesn't help much, though, 'cause it won't receive adb commands. I manually installed the LG USB Composite Device driver, which added a modem and a COM port, both of which Windows recognized to be active, but the LG FlashTool USB Viewer showed no open pipes. I'm a relative noob, so please feel free to point out the obvious, like an alternative to adb that the phone can always receive or a way to brick it the rest of the way so the MicroSD trick will work.
I came across this problem like the OP and just wanna let everyone know that you have to use computer with USB 2.0 port then the driver issue would be fixed.
Hello guys,
I'm using my 3T carefully as a media device just at home. But suddenly I couldn't control my system anymore. I could swipe and open settings, but couldn't turn on WiFi or start any app. So I restarted my phone but it never booted. Screen is completely black and even charging leds doesn't work anymore. I can't access TWRP recovery. I used the button combinations ... Nothing! But when I connect my phone to my computer windows plays the typical sound like when you plug in an USB stick. Windows sayed once that the connected device is buggy and cannot be detected. Nothing more. When I reconnect no more message or pop up again.
Has anyone any idea? Thanks a lot!
slev!n said:
Hello guys,
Screen unit is completely dead. It even doesn't show a charging led anymore. I can't access TWRP recovery. I used the button combinations ... Nothing! But when I connect to the computer windows registers my phone by playing the 'connected sound'. But nothing more. Has anyone any idea or know where I can discuss my issue? Thanks a lot!
Click to expand...
Click to collapse
That's weird. Sounds like your screen (if not more parts) died. Hardware issue? Water damage? Might be better to contact a repair center since if you can't even access recovery I doubt the problem is related to LOS. Never happened on my 3T over the 4 years I've had it, though it's had its fair share of damage.
knpk13 said:
That's weird. Sounds like your screen (if not more parts) died. Hardware issue? Water damage? Might be better to contact a repair center since if you can't even access recovery I doubt the problem is related to LOS. Never happened on my 3T over the 4 years I've had it, though it's had its fair share of damage.
Click to expand...
Click to collapse
But before my restart I could use the screen it just looks like something in the system doesn't work: could type on apps and settings, it just doesn't open or pop back. And the charging led is not part of the screen unit as I know.... If I could take out the battery I would do it. It often works in other phones. But I don't have tools here for my 3T. :/
knpk13 said:
That's weird. Sounds like your screen (if not more parts) died. Hardware issue? Water damage? Might be better to contact a repair center since if you can't even access recovery I doubt the problem is related to LOS. Never happened on my 3T over the 4 years I've had it, though it's had its fair share of damage.
Click to expand...
Click to collapse
slev!n said:
But before my restart I could use the screen it just looks like something in the system doesn't work: could type on apps and settings, it just doesn't open or pop back. And the charging led is not part of the screen unit as I know.... If I could take out the battery I would do it. It often works in other phones. But I don't have tools here for my 3T. :/
Click to expand...
Click to collapse
slev!n said:
Hello guys,
I've got an issue and don't know if it belongs to the build or not. I'm on the last build with my 3T and today after charging my phone I couldn't turn on WiFi or start any app. It just didn't open. So I restated my phone but it never booted. Screen unit is completely dead. It even doesn't show a charging led anymore. I can't access TWRP recovery. I used the button combinations ... Nothing! But when I connect to the computer windows registers my phone by playing the 'connected sound'. But nothing more. Has anyone any idea or know where I can discuss my issue? Thanks a lot!
Click to expand...
Click to collapse
Sounds to me like an hardware error involving (but not necessarily limited to) emmc access. That would explain, why the parts still in ram (like homescreen) were still working but apps won't start anymore, as well as the blank screen on device startup (even the logo needs emmc access to read the logo partition).
Try unbricking (I'm afraid your pc won't find the device, if my guess is correct), if that fails: rma or repair center.
slev!n said:
Has anyone any idea or know where I can discuss my issue? Thanks a lot!
Click to expand...
Click to collapse
here
You need to be more spesific about the connected sounds, does it shows up on device manager or else, in detail (with SS/photos etc to prevent misjudge)
150208 said:
here
You need to be more spesific about the connected sounds, does it shows up on device manager or else, in detail (with SS/photos etc to prevent misjudge)
Click to expand...
Click to collapse
Thanks, I'll create a post there. Just one more post here:
I used this phone just carefully at home as a media device. So this brick came totally out of nowhere. When I connect my bricked 3T now to my computer it makes the typical sound like when you plug in an USB stick. Windows sayed once that the connected device is buggy and cannot be detected. Nothing more. When I reconnect no more pop up again.
slev!n said:
I'll create a post there.
Click to expand...
Click to collapse
When you've created that post ask the moderators to move this complete conversation from this thread to the newly created on in the help forum, please. This helps to keep this thread readable and searcheble.
For your trouble: if you can't boot rom, recovery nor fastboot mode, it doesn't make sense to debug the usb connection: what should the pc connect to if none of the three is bootable? There is just nothing up to connect to. That's why I recommended unbrick tool - if that fails rma or go to a repair center.
Hello guys,
I'm using my 3T carefully as a media device just at home. But suddenly I couldn't control my system anymore. I could swipe and open settings, but couldn't turn on WiFi or start any app. So I restarted my phone but it never booted. Screen is completely black and even charging leds doesn't work anymore. I can't access TWRP recovery. I used the button combinations ... Nothing! But when I connect my phone to my computer windows plays the typical sound like when you plug in an USB stick. Windows sayed once that the connected device is buggy and cannot be detected. Nothing more. When I reconnect no more message or pop up again.
Has anyone any idea? Thanks a lot!
Post SS of the device manager after connecting the phone to the PC
150208 said:
Post SS of the device manager after connecting the phone to the PC
Click to expand...
Click to collapse
It doesn't make sense to debug the pc conmection: if neither recovery, fastboot mode nor rom is bootable, there is nothing up and running the pc can connect to (maybe unbrick tool can still access the msm hardware directly, but that's not sure - confirmation is still missing from @slev!n). I'm writing this the second time.
If none of recovery, fastboot mode nor rom is bootable, the last resource before rma or repair center is unbrick tool. I'm writing this the third time!
@slev!n: please ask the moderators to move the existing conversation to thos from the los16 thread here. If all postings have moved, ask the moderators to move this thread from op3/help to op3t/help.
@nvertigo67 I wanted to do so and was searching how to contact moderators but couldn't find it in my XDA app. Maybe someone can give me a hint? I'm kind of new on xda... Thanks!
@150208 And as I wrote: it's not possible to get any kind of message on windows anymore. Just the sound appears when I connect and disconnect.
@nvertigo67 I was also following your advice to use the unbrick tool. I followed the steps on oneplus forum:
https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/
When it comes to the integrity check windows doesn't accept "TESTSIGNING ON". And so windows doesn't recognise my phone in the device manager for the next steps.
And I guess RMA or repair centres are super expensive. I don't know if it's worth it? I thought about buying a device with a broken screen on eBay and try to change the motherboard...
Log in with a web browser locate each posting of the comversation. For each posting in question use the little triangle icon at the botom on the left side, report each posting, set non-urgent and pit the link of this thread together with something like "Please move this posting to the linked thread, thanx in advance".
For disabling driver signature enforcement try method 2. from this post: http://maxedtech.com/about-testmode/
Most of tbe time xda postings are more reliable and more current then the Oneplus forums: https://forum.xda-developers.com/oneplus-3/how-to/op3-collection-unbrick-tools-t3896722, https://forum.xda-developers.com/oneplus-3/how-to/op3-collection-unbrick-tools-t3896722
slev!n said:
[MENTION=4405529]i thought about buying a device with a broken screen on eBay and try to change the motherboard...
Click to expand...
Click to collapse
If you already have a thought why do you keep asked here though? If you want another possible solution, at least put an effort to provide the information needed when asked by the one who tried to help you
I'm not into a guessing games, so i'm out
nvertigo67 said:
It doesn't make sense to debug the pc conmection: if neither recovery, fastboot mode nor rom is bootable, there is nothing up and running the pc can connect to (maybe unbrick tool can still access the msm hardware directly, but that's not sure - confirmation is still missing from @slev!n). I'm writing this the second time.
If none of recovery, fastboot mode nor rom is bootable, the last resource before rma or repair center is unbrick tool. I'm writing this the third time!
Click to expand...
Click to collapse
There are 2 possible reason when the phone is not detected by the computer, driver or hw problem.
To know it i need to look at the device manager status
If it's hw problem, i'll try not to jump on MB conclussion yet, since there are still another possible reason
When talking about MSM, you need to make sure it's available first on the device manager
Otherwise, it's a waste of data for downloading the tool in these human malware days
Oh yes, the msm guide is quite lag behind. You don't need to boot into test mode anymore with the current driver for qualcomm
I flashed a lot qualcomm devices with w10 without the need to boot into test mode
150208 said:
There are 2 possible reason when the phone is not detected by the computer, driver or hw problem.
To know it i need to look at the device manager status
Click to expand...
Click to collapse
True, if only "win is not detecting the device" is known. Since we know much more (neither rom, recovery nor fastboot mode are bootable), the debugging of the usb driver doesn't make sense. The msm tool uses it's own drivers to detect the hardware BEFORE one of the three is booted. If the msm tool has unbricked the device and booting recovery, rom and/or fastboot, you can start debugging the "nprmal" qc usb drivers, if still necessary.
For the costs of rma: maybe it's expensive - maybe oneplus will be obliging... Since you don't relay on the device as your daily driver, you can ask for an estimate of costs - so you can decide if it's worth the costs.
nvertigo67 said:
True, if only "win is not detecting the device" is known. Since we know much more (neither rom, recovery nor fastboot mode are bootable), the debugging of the usb driver doesn't make sense. The msm tool uses it's own drivers to detect the hardware BEFORE one of the three is booted. If the msm tool has unbricked the device and booting recovery, rom and/or fastboot, you can start debugging the "nprmal" qc usb drivers, if still necessary.
Click to expand...
Click to collapse
Wait, I fail to see your explanation in line with mine. I want to start debug it on the windows side, but you seems to see it on the phone side.
Do you realize there are cases where everything is black/nothing responding but it's still detected by computer? That when emmc is corrupt, but repairable if you format it.
150208 said:
Do you realize there are cases where everything is black/nothing responding but it's still detected by computer? That when emmc is corrupt, but repairable if you format it.
Click to expand...
Click to collapse
If neither fastboot mode nor recovery is bootable, you need the msm interface to refprmat somethimg on emmc. In other words: if there's no recovery nor fastboot, you can't utilize adb or fastboot to reformat or to fix the partition table. You need something to connect to to do the fixing, but without recovery or fastboot, there is nothing adb or fastboot can conmect to, no matter of the driver status on the pc/win side. Once this is fixed (at least fastboot mode is up again) you can utilize the "normal" usb connection again.
What do you want to do with the usb connection, if neither fastboot mode nor recovery is up amd running? What is your suggested next step, if the device is recognized? What should the pc recognize if neither fastboot nor adb os an option? Which command or procedure will fix the emmc?
nvertigo67 said:
If neither fastboot mode nor recovery is bootable, you need the msm interface to refprmat somethimg on emmc.
Click to expand...
Click to collapse
Yes, there are other tools but i'm not gonna bother since it's paid
nvertigo67 said:
In other words: if there's no recovery nor fastboot, you can't utilize adb or fastboot to reformat or to fix the partition table. You need something to connect to to do the fixing, but without recovery or fastboot, there is nothing adb or fastboot can conmect to, no matter of the driver status on the pc/win side.
Click to expand...
Click to collapse
This is the part where you're incorrect. There are 4 status when a device plugged into the pc.
1. detected and driver is loaded
2. detected and driver isn't loaded
3. detected but not recognized
4. no sign at all
1 and 2 is sw problem, 3 and 4 is hw problem
In order for MSM to do it's job, you need to have either problem no 1 or 2 with qualcomm qloader 9008 driver already or later detected in devmanager
So it's important to know the driver status
OP states there was sounds coming then nothing, which mean it's either 2 or 3, more like 3 but again i repeating myself i don't like guessing games
I don't understand the part why you're explaining/asking about fastboot recovery or etc, his phone is on dead state, nothing-literally-no sign of life unless he plug it to the pc and then it making sounds for the first time,
Why do you even bother thinking about it?
nvertigo67 said:
Which command or procedure will fix the emmc?
Click to expand...
Click to collapse
No procedure will fixed his phone since there are no enough information
I think your other question should be already answered. If else, i don't know what to say anymore.
150208 said:
nvertigo67 said:
In other words: if there's no recovery nor fastboot, you can't utilize adb or fastboot to reformat or to fix the partition table. You need something to connect to to do the fixing, but without recovery or fastboot, there is nothing adb or fastboot can conmect to, no matter of the driver status on the pc/win side.
Click to expand...
Click to collapse
This is the part where you're incorrect.
Click to expand...
Click to collapse
If so, please explain how you can format a partition or fix the partition table if neither fastboot mode nor recovery (or a rooted system for that matter) is bootable.
@slev!n: please give a screenshot of the device manager to @150208. I'm too curious to learn how to fix a broken emmc without recovery nor fastboot mode.
Thank you so far!
I dont want to bother someone. Just thinking about further options thats why I wrote my thought about replacing the motherboard down.
I 'm in test mode now and I did this:
"Step 4 :- Press the power button for 40 seconds to turn off the phone.
Step 5 :- Press only volume up button for a few seconds and while keeping it pressed,connect your phone to PC.Keep volume up pressed till your device shows in device manager as [Unknown Device,QHUSB_BULK (under Unknown Devices) or Qualcomm HS USB (under COMs and Ports)]."
But no device is listet in my device manager. But in msmtool my phone is connected. Does it mean I cann't continue with this tool somehow?
slev!n said:
But no device is listet in my device manager. But in msmtool my phone is connected. Does it mean I cann't continue with this tool somehow?
Click to expand...
Click to collapse
The pic is from msm tool, not the device manager. No unknown device in device manager?