Hi all,
Looked through the forum here but mine's slightly different. Installed MM ROM and tried to do factory reset. Phone booted and now stuck on "flashing" TWRP screen. Can't connect through ADB/Odin as getting msg "USB device not recognised.. device malfunction etc". Tried 4 cables and all same. I've both Samsung USB and universal ADB drivers installed on PC. Any help would be appreciated.
Thanks.
Related
Hi there, my phone is soft bricked and freezes at the Samsung logo when booting up.. been reading / trying all sorts but can't seem to resolve it so thought i'd come here for help.
Windows or Odin wont recognize my device even though I have the latest Samsung Drivers installed, Windows is saying 'USB Device not recognized' and that it may have malfunctioned.
Could I have messed up the phones USB drivers which is why they're only half working? If so is it possible for me to put something onto my SD card to then install through CWM?
Any help is much appreciated as this is really starting to frustrate me.
Hello,
i tried to update my Nexus 5 to 5.1 by using adb sideload.
First i installed the driver which did not work, i removed them and used an another and the device was recognized after that on windows.
So I started the sideload and it stopped at about 60% and the USB Connection was lost. I can not see the device in the device manager and if i use my linux computer i can not see any new entry if i use 'dmesg'. I used an another USB cable to check if this is broken. I tried to format the cache and it now still boots to the recovery mode.
Can it be that the USB driver in the N5 is broken now?
I wanted to prevent a factory reset, but i dont think that a FR will help here if i can not connect even in the recovery mode
Any suggestions?
Thank you!
wwwiesel said:
Hello,
i tried to update my Nexus 5 to 5.1 by using adb sideload.
First i installed the driver which did not work, i removed them and used an another and the device was recognized after that on windows.
So I started the sideload and it stopped at about 60% and the USB Connection was lost. I can not see the device in the device manager and if i use my linux computer i can not see any new entry if i use 'dmesg'. I used an another USB cable to check if this is broken. I tried to format the cache and it now still boots to the recovery mode.
Can it be that the USB driver in the N5 is broken now?
I wanted to prevent a factory reset, but i dont think that a FR will help here if i can not connect even in the recovery mode
Any suggestions?
Thank you!
Click to expand...
Click to collapse
Hmmm, intermittent ADB occured before attempted sideload falure.
Boot to bootloader and see if you can
fastboot devices
If you can detect the device in fastboot, but still cant ABD, then maybe take a look here http://forum.xda-developers.com/showpost.php?p=59420668&postcount=322
After looking there, if you are absolutely certain that it is not a driver issue, you might be looking at a hardware failure of the charging port.
https://www.youtube.com/watch?v=qqCEXEmcj4Y
If it were me, I'd replace the port and re-attempt ADB sideload.
I usually keep flashing ROMS.
This time in sheer confidence I didnt charge the battery full.
I was switching from mokee 4.4 to CM11.
I wiped everything for a fresh install and unfortunately CM11 didnt install.
The tab restarted and now it wont go into recovery. what just happened?
It is just showing logo and I cannot get into Odin more either.
The tab had about 30% battery when it shut off and I cannot reach a charger for it for the next 4 hours.
Can I switch it off in any way to save battery?
the phone has switched off now. Is service center the only alternative? the tab was rooted with mokee installed.
devarshi84 said:
the phone has switched off now. Is service center the only alternative? the tab was rooted with mokee installed.
Click to expand...
Click to collapse
Try charging it when you have time and then try re flashing the stock Rom before taking it to service center
will the tab 2 charge without a recovery or ROM in place?
devarshi84 said:
will the tab 2 charge without a recovery or ROM in place?
Click to expand...
Click to collapse
I think it should
Ok, the tab2 is charging. thank you
I installed all the necessary drivers and odin and recovery on my laptop.
The tab2 is giving error on pc (this device wont start) mtp uSB. THe tab is stuck at 'samsung p3100' logo.
If it is any help, I have a working p3100 also running on stock firmware.
what should be my next step? I think I can manage if only I can get odin to recognize my phone or get into recovery (both of which seem to be missing.)
devarshi84 said:
Ok, the tab2 is charging. thank you
I installed all the necessary drivers and odin and recovery on my laptop.
The tab2 is giving error on pc (this device wont start) mtp uSB. THe tab is stuck at 'samsung p3100' logo.
If it is any help, I have a working p3100 also running on stock firmware.
what should be my next step? I think I can manage if only I can get odin to recognize my phone or get into recovery (both of which seem to be missing.)
Click to expand...
Click to collapse
Try reinstalling drivers
@shsagnik : Thank you very much for helping out.
I got installed all drivers by using the other P3100. But when I connect the bricked p3100, pc doesnt install MTP USB drivers. Under device manager it says " failed to start".
ODIN doesn't recognize it. either.
My mistake was I flashed everything on the phone including the internal memory.
PS: Can I force ODIN to recognize my phone?
Ok, my almost bricked device is back and runnning.
This might just help somebody. but my android handset was on a logo only mode. something in the combination of
Attaching it to pc (windows 7 64-bit)
re-installing and rejigging drivers
trying to let ODIN identiify
connecting via Samsung kies (I also tried restore on kies).
connecting a working android phone instead of the dead phone with pc to find and install drivers.
worked.
PS: I also let it sit dead powered off (worked only when charger was attached) for a whole day before trying to boot into recovery or bootlaoder (both worked).
devarshi84 said:
Ok, my almost bricked device is back and runnning.
This might just help somebody. but my android handset was on a logo only mode. something in the combination of
Attaching it to pc (windows 7 64-bit)
re-installing and rejigging drivers
trying to let ODIN identiify
connecting via Samsung kies (I also tried restore on kies).
connecting a working android phone instead of the dead phone with pc to find and install drivers.
worked.
PS: I also let it sit dead powered off (worked only when charger was attached) for a whole day before trying to boot into recovery or bootlaoder (both worked).
Click to expand...
Click to collapse
Awesome, now please change the title to solved
Hello, a friend of mine brought me probably bricked sm G920F (galaxy s6). he was on custom rom and twrp 3.0.2. He accidentaly wipped everything on the device and now it is stacked on twrp loading screen. i downloaded usb drivers and odin to flash back to stock but the pc is not recognizing my device when i boot into download mode. So i am a bit stacked since twrp is not loading and the phone is not recognized by my pc. We tried on different pcs with different cables and usb ports but still the phone is not get recognized.
Any suggestions?
hey, I'm in a similar boat.. been wrangling with it for a few days I am attempting the Emergency Software Recovery using Samsung Smart Switch, have you tried that?
It's shown when inquiry adb devices?
You must flash original firmware with ODIN
Hello guys, I'm really STUCK with the galaxy S6 (G920F) at the moment.
A friend gave it to me he said it suddenly turned off while he was playing a game and couldn't boot anymore.
I can't turn it off, it will keep on turning on automatically.
I can't go into recovery mode.
I can only go into download mode and flash a firmware with odin
I flashed the stock firmware with the latest odin and it flashed successfully. But it's still stuck on the Samsung logo (powered by Android) and won't boot into recovery or do anything at all.
So I read it could be the battery, so I bought a new one and replaced the battery.
But the problem remains. On Windows 7 x64 it's detected as "Gadget Serial" and "SAMSUNG Mobile USB CDC Composite Device" when I'm in download mode.
Odin detects the phone fine.
I then tried using Samsung Kies, and Samsung Smart Switch. Samsung Smart Switch detects an "unsupported device" and Samsung Kies doesn't detect anything at all and is stuck at "connecting...".
I don't have any ideas anymore and I fear it's a dead flash chip or any other board malfunctions.
Any suggestions maybe? Pleasee?
nekrosmsk said:
Hello guys, I'm really STUCK with the galaxy S6 (G920F) at the moment.
A friend gave it to me he said it suddenly turned off while he was playing a game and couldn't boot anymore.
I can't turn it off, it will keep on turning on automatically.
I can't go into recovery mode.
I can only go into download mode and flash a firmware with odin
I flashed the stock firmware with the latest odin and it flashed successfully. But it's still stuck on the Samsung logo (powered by Android) and won't boot into recovery or do anything at all.
So I read it could be the battery, so I bought a new one and replaced the battery.
But the problem remains. On Windows 7 x64 it's detected as "Gadget Serial" and "SAMSUNG Mobile USB CDC Composite Device" when I'm in download mode.
Odin detects the phone fine.
I then tried using Samsung Kies, and Samsung Smart Switch. Samsung Smart Switch detects an "unsupported device" and Samsung Kies doesn't detect anything at all and is stuck at "connecting...".
I don't have any ideas anymore and I fear it's a dead flash chip or any other board malfunctions.
Any suggestions maybe? Pleasee?
Click to expand...
Click to collapse
Sounds to me like it has run out of storage space and has no room to cache files when it boots.
Have you tried extracting the stock recovery.img from the stock firmware file then converting the recovery.img to a .tar.md5 file, then flashing the recovery and try to boot directly to it after flashing? If you can get into recovery, you can factory reset the device and wipe the cache partition. Sometimes this solves a bootloop issue after flashing stock firmware.
You can also try flashing a copy of TWRP for your device and then use TWRP to factory reset and wipe the device.
Sent from my Amazon Tate using Tapatalk