I have a NS i9020T which was running the latest MIUI ROM until I tried to update it to MIUI ICS. I had noticed, while running pre-ICS, that my computer wouldn't mount USB storage. As a working around (rather that trying to fix the issue) I just FTPed files. When I tried to install MIUI ICS something went wrong (probably corrupt ROM image) and now my NS won't boot.
If I go through Clockwork Recovery to mount USB mass storage, nothing happens. I'm running OS X, but I've tried mounting in Ubuntu 11 and Win7 -- Windows recognizes that there is a device there but the drivers won't recognize it (I think).
Finally, I've tried flashing a new recovery using fastboot but I get "<waiting for device>" in Terminal.
My best guess is that the USB connection is shot, which would probably require me ripping the NS open and tinkering around (which I have zero experience doing).
Does anyone have any ideas for fixing what is likely a permanent brick? I can boot into Win7, OS X, or Linux to troubleshoot. Also I'm on the XDA IRC as "threepape" right now trying to solve this issue.
Thanks in advance!
I was working with threepape on IRC trying to narrow down the issue.
Basically he's had his phone rooted, tried flashing a rom and now it's stuck at the boot screen. He went to connect to his computer and it gave him an error. and wouldn't let him connect his phone to the os. This is a problem.
So he then downloaded kies to see if it would install drivers automatically, downloaded odin and then tried to see if odin would recognize the phone. It did not and his computer gave him the error "unknown USB device, error code 43"
So we reviewed what we could control: trying different cords, checking drivers, etc.
Now we are going to try booting into an osx platform, installing heimdall and seeing if "heimdall detect" prompt will detect the phone. If that doesn't work we're going to either need more help or rule it out as a hardware issue.
<threepape>
Failed to detect compatible download-mode device.
[8:55pm] <ddrt>
so you typed out heimdall, then heimdall detect and it came back with that?
[8:55pm] <ddrt>
and you are 100% it was in download mode?
[8:55pm] <threepape>
yep
[8:56pm] <threepape>
it does ay on my phonee "USB Control Init USB Control Init End"
Click to expand...
Click to collapse
edit: device is not being detected on multiple os using different programs, device will not wipe fully when doing a factory restore through CWM. I am at a loss.
So here's my major problem. I factory reset my N5 for my dad to use since I got a 1+1. It was rooted so i went into the settings for supersu and hit full un-root. Well that just broke everything and when I try to boot, I get a bootloop. So at this point i'm like, okay. I've fixed this before. My process. power off>fastboot>recovery>recovery settings>wipe cache/partition>done>factory reset>done.>reboot. Still get bootloop so I thought, okay ****. Flash a factory image and start a-new. I start up fastboot, and plug the phone into computer(Win7 32-bit) and do all this jazz. I realize i factory reset and wiped it so usb debugging won't be checked, so of course my computer doesn't list the device. ****. I check Device Manager and the Android setting shows up so I see it has the "ADB Bootloader Interface" as the driver. Kinda weird since I thought I used "ADB Composite Interface" last time. But my Nexus must be showing up at least in the drivers. So essentially, here's the compounded issues.
1. Bootloop
2. Can't boot so no USB debugging is checked
3 .Can't flash a stock image if device doesn't show up on computer for fastboot stuff.
4. Drivers are all messed up. I got them directly from google too.
5. ****.
I think I'm screwed on this unless I can somehow enable USB debugging from fastboot without the device itself being recognized, or something. Pls help.
My dad thinks i'm a failure now.
You don't need USB debugging for fastboot. It might be a driver issue if fastboot doesn't see it. Maybe try installing them again.
Sent from my Nexus 5 using XDA Premium App
Download some program to wipe all android drivers from the system. Restart the computer. Boot the device to bootloader. Connect the device to the PC. Go to device manager. Manually update those drivers. The drivers are the same for fastboot or adb, it's just that you need to feed Windows the same drivers twice: one when device is in bootloader, another when the device has adbd (adb daemon/server) running. Adbd doesn't run when the device is in bootloader - it's an Android thing.
a maguro wrote this.
Hi Everyone ^^
I sort of got my Samsung Galaxy GT-S5660 bricked without being able to find a fix for it..
I've followed an installation Guide to the letter, yet i now find my Phone stuck on all sides
Been searching and reading XDA & Google, thus-far without any fix in sight :x
Setup:
- I'm running a Windows 8 PC, updated & running properly, all Drivers Installed
- Before all of this, the Phone worked properly on default ROM, un-tampered with, PC could connect and transfer files to the Phone while it was running. Didn't try the download mode until after brick.
Used this XDA Thread to first root the Phone, using Recovery Mode to install the zip from SD: http://forum.xda-developers.com/showthread.php?t=1111414
Then followed this Guide to the Letter to install the CM10.1, also installing it using Recovery Mode, installing the zip from SD: http://www.android.gs/update-galaxy-gio-android-4-2-2-jb-cm10-1/
Thats where the fun ended ... it rebooted and ... nothing :x
Resulted into this situation:
- Normal Boot (Pwr-Btn): The Phone wont boot, it first loads a static Samsung logo, then after a bit shows the ''GALAXY Gio GT-S5660" logo and just permanently holds on that
- Boot into Recovery Mode (Home-Btn + Pwr-Btn): No longer works, Instead of going into old Recovery Mode or CWM Recovery mode, it just displays the static Samsung logo for a looong time, then reboots into "Normal Boot" described above. So no more installing from SD Card ... No more Recovery Mode
- Boot into Download Mode (Vol-Down + Home-Btn + Pwr-Btn): No problem, displays the yellow "Downloading..." mid-screen. Problem is, PC's keep telling me "USB Device is not Recognized".. Any USB-Cable, any PC, none recognize the device. Tried every driver i could find, trying and retrying, the Samsung Kies Drivers and app as well, every version of it. Still, i can not get a PC to recognize the device in Download Mode, so Odin doesn't find it either.
- Boot into Emergency Download Mode (Vol-Up + Vol-Down + Home-Btn + Pwr-Btn): PC recognizes the device, Odin detects it aswel, i can do the Odin setup i found here: http://forum.xda-developers.com/showpost.php?p=20896513&postcount=2 , and Odin verifies all files correctly, detects the device on the COM Port, all seems well. When pressing the Start button in Odin it starts out fine, displays the log saying "Download Start..., etc", but it stops at "<1> setup connection...", and there it stays ...
Been trying to find an XDA-Thread or Google solution for this scenario but i'm coming up empty, thus i come here to post the problem ...
Nutshell:
- Phone wont Boot into Android OS, simply won't boot ..
- I can't boot into Recovery Mode to load from SD, simply no more Recovery Mode
- Can boot into Download Mode, but all PC's seem to throw up a "USB Device not Recognized" error, no matter the USB-Cable, thus Odin does not detect the Device
- Can boot into Emergency Download Mode, but Odin doesn't seem to want to install in this manner and halts at setting up the connection...
= What am i to Do????
Please Help! ^^
- Is there some magical driver that will result in the Device Being recognized while it's in Download Mode?
- Is there something i can use or do to install a CWM using Emergency Download Mode or SOMETHING? (Maybe get Recovery Mode working again, or have Odin work with Emergency Download Mode)
Thanks for your time,
Kind Regards!
x6XceS6x said:
Hi Everyone ^^
I sort of got my Samsung Galaxy GT-S5660 bricked without being able to find a fix for it..
I've followed an installation Guide to the letter, yet i now find my Phone stuck on all sides
Been searching and reading XDA & Google, thus-far without any fix in sight :x
Setup:
- I'm running a Windows 8 PC, updated & running properly, all Drivers Installed
- Before all of this, the Phone worked properly on default ROM, un-tampered with, PC could connect and transfer files to the Phone while it was running. Didn't try the download mode until after brick.
Used this XDA Thread to first root the Phone, using Recovery Mode to install the zip from SD: http://forum.xda-developers.com/showthread.php?t=1111414
Then followed this Guide to the Letter to install the CM10.1, also installing it using Recovery Mode, installing the zip from SD: http://www.android.gs/update-galaxy-gio-android-4-2-2-jb-cm10-1/
Thats where the fun ended ... it rebooted and ... nothing :x
Resulted into this situation:
- Normal Boot (Pwr-Btn): The Phone wont boot, it first loads a static Samsung logo, then after a bit shows the ''GALAXY Gio GT-S5660" logo and just permanently holds on that
- Boot into Recovery Mode (Home-Btn + Pwr-Btn): No longer works, Instead of going into old Recovery Mode or CWM Recovery mode, it just displays the static Samsung logo for a looong time, then reboots into "Normal Boot" described above. So no more installing from SD Card ... No more Recovery Mode
- Boot into Download Mode (Vol-Down + Home-Btn + Pwr-Btn): No problem, displays the yellow "Downloading..." mid-screen. Problem is, PC's keep telling me "USB Device is not Recognized".. Any USB-Cable, any PC, none recognize the device. Tried every driver i could find, trying and retrying, the Samsung Kies Drivers and app as well, every version of it. Still, i can not get a PC to recognize the device in Download Mode, so Odin doesn't find it either.
- Boot into Emergency Download Mode (Vol-Up + Vol-Down + Home-Btn + Pwr-Btn): PC recognizes the device, Odin detects it aswel, i can do the Odin setup i found here: http://forum.xda-developers.com/showpost.php?p=20896513&postcount=2 , and Odin verifies all files correctly, detects the device on the COM Port, all seems well. When pressing the Start button in Odin it starts out fine, displays the log saying "Download Start..., etc", but it stops at "<1> setup connection...", and there it stays ...
Been trying to find an XDA-Thread or Google solution for this scenario but i'm coming up empty, thus i come here to post the problem ...
Nutshell:
- Phone wont Boot into Android OS, simply won't boot ..
- I can't boot into Recovery Mode to load from SD, simply no more Recovery Mode
- Can boot into Download Mode, but all PC's seem to throw up a "USB Device not Recognized" error, no matter the USB-Cable, thus Odin does not detect the Device
- Can boot into Emergency Download Mode, but Odin doesn't seem to want to install in this manner and halts at setting up the connection...
= What am i to Do????
Please Help! ^^
- Is there some magical driver that will result in the Device Being recognized while it's in Download Mode?
- Is there something i can use or do to install a CWM using Emergency Download Mode or SOMETHING? (Maybe get Recovery Mode working again, or have Odin work with Emergency Download Mode)
Thanks for your time,
Kind Regards!
Click to expand...
Click to collapse
Try with heimdall, an alternative to Odin : http://glassechidna.com.au/heimdall/ . For the emergency download mode, you won't be able to do anything with it. And make sure you have the samsung usb drivers : http://developer.samsung.com/technical-doc/view.do?v=T000000117
Tried, same result
Dear TheIcE65,
Thank you for your quick response.
I've tried the USB Drivers you supplied, clean install
Unfortunately these drivers result in the same problem. While the Phone is in Download Mode, once connected windows still throws up a "USB Device not Recognized" error.
Heimdall also does not recognize the device, as Windows doesn't either.
Please help, I'd like to get this Phone un-bricked!
Kind regards
Anyone found a fix for this ?
Exactly the same issues here
same issue
facing the same issue. cant find any solution anywhere. hoping someone can help
Hello everyone.
Just to get it out of the way, I am very inexperienced with android products. At the moment, I'm having trouble getting my HTC One X (at&t) version to turn on. It all started when I decided to update the android version from 4.1. something to 4.2.2. I went to this site, the HTC website (www . htc . com / us/support/htc-one-x-att/news/) and downloaded the executable file and ran it . Once installation was done a message popped up on my computer stating an error occurred. I look at the phone and it shows the HTC splash screen for a few seconds and it shuts off and immediately turns back on with the HTC splash screen again, a bootloop. I then found out that I can restore the device by entering fastboot and selecting the factory restore option. This didn't restore the device but just entered the bootloop process again. I entered fastboot mode again and this time I selected the recovery option which also failed. I hook up the phone with USB 2.0 to the computer to transfer a stock ROM but computer doesn't recognize the phone anymore ( the computer did at first recognize the phone during installation of 4.2.2). After various attempts to get the phone to be recognized by computer, I gave up and called it quits and decided to power it off through the fastboot option. And now I can't even turn on the phone at all. I plug it to the computer to see if that will prompt the phone to turn on but all that does is charge the battery. The computer does recognize that something is connected to it but fails to recognize the phone.
Is there anything I can do to get this phone working again? I would much appreciate any help with this.
Ok guys I managed to get the phone to turn on again, buts its still in bootloop. Once the phone turns on, the computer notices that the phone is connected and tries to install the drivers but fails as soon as the phone restarts. Essentially the computer is unable to finish installing the proper drivers in time. The driver that its trying to install is "HTC MTP Device".
Put the phone into bootloader mode and run the RUU executable again.
Transmitted via Bacon
Ok its finally working. Thanks for the help!
Hi all,
sorry if there is plenty of these threads already floating around but wasnt able to find a relevant one to my problem. I'm hoping someone here might be able to help.
This is the primary XZ rooting guide i have been following, with other supplimentary guides 1 & 2
These have been my steps:
- Managed to successfully update fastboot driver with "android_winusb.inf-file" from 'Google USB Driver' within android studio.
- Unlocked bootloader
- Installed AndroPlus Kernel sucessfully "fastboot flash boot boot.img"
Now went to reboot device as stated by instructions (mistake) and now the device is not recognized in cmd "waiting for device". I've replugged the usb in multiple ports and the device shows up as "android" in devices and printers. I go to update the android "SOMC Flash Device" to the platform tools directory but makes no difference in cmd. Still "waiting for device". In Device Manager there is no sign of the device either.
When the phone is turned on it shows your device has been "unlocked and cant be trusted will reboot in 5 seconds" then proceeds to xperia logo and freezes. With no recoveries theres not much options.
Is there a way to continue from here or even return to a previous state? It seems like i hit a brick wall. Please help
MugenG said:
Hi all,
sorry if there is plenty of these threads already floating around but wasnt able to find a relevant one to my problem. I'm hoping someone here might be able to help.
This is the primary XZ rooting guide i have been following, with other supplimentary guides 1 & 2
These have been my steps:
- Managed to successfully update fastboot driver with "android_winusb.inf-file" from 'Google USB Driver' within android studio.
- Unlocked bootloader
- Installed AndroPlus Kernel sucessfully "fastboot flash boot boot.img"
Now went to reboot device as stated by instructions (mistake) and now the device is not recognized in cmd "waiting for device". I've replugged the usb in multiple ports and the device shows up as "android" in devices and printers. I go to update the android "SOMC Flash Device" to the platform tools directory but makes no difference in cmd. Still "waiting for device". In Device Manager there is no sign of the device either.
When the phone is turned on it shows your device has been "unlocked and cant be trusted will reboot in 5 seconds" then proceeds to xperia logo and freezes. With no recoveries theres not much options.
Is there a way to continue from here or even return to a previous state? It seems like i hit a brick wall. Please help
Click to expand...
Click to collapse
Installed adb SystemWide?
adb drivers are Installed corrcetly? , better to reinstall them.