Hello,
My phone died two evenings ago and now won't get any further than the flashing Samsung logo when booting up. I have tried:
- different batteries,
- leaving the phone with no battery in for hours before retrying
- going into download mode, but device is not recognised by Kies (although does appear under devices and printers as Samsung_Android)
- going into recovery mode and attempting ADB but again device is not recognised by Kies
- going into recovery mode and accessing CWM-based recovery v.6.0.1.4 (CWM-non-touch-6.0.1.4-i91000.zip) but restore fails due to an MD5 mismatch (??)
If the phone is totally tanked that's fine, I'll do a factory reset, but I would if possible at least like to be able to get last few months of photos off the phone before wiping and starting again.
Any suggestions for help?
Thank you :good:
try installing your ROM via recovery from the SD card wipe chache, dalvik, install the kernel you had, wipe cache, dalvik and reboot, worked for me with a similar problem
Flash cwm or trp recovery, and you can mount your internal & sd memory from recovery , then you can copy your files to pc first! Then your can resolve your problem! dont look for phone in devices and printers!!! go to device manager and check your usb cable, usb ports!
Also I had this problem, here is how I've solved it:
Reinstall USB Drivers
Turn off the device
Boot in download mode
Flash a stock firmware via ODIN
Reboot
Related
Hi all i recently installed the kg3 firmware and ever since doing so i cannot get any pc to recognise the device. i have tried in all ports and 3 pc's.
I have bought a new cable but same issue.
I tried doing a factory reset. and a reset through the manual mode.
I have reinstalled kies and uninstalled and put just the drivers on but same issue.
I think it's firmware as it happened as soon as i did the update ?
is there any way i can manually do a firmware update onto a ofial release stock if i can get it into the phones memory, I don't have a micro sd at this time?
Please help or any suggestions otherwise i may send back as faulty unit for warranty just incase the usb bit internally some how broke.
thanks in advance
Also for got to mention i tried it in usb dev mode and not
Also i tried now usb dev mode on to see of the development tools will pick it up and they also do not.
Anyway to recover the firmware on the phone with out access to usb ?
You can try flashing firmware with Odin. Read Chainfire thread in Original Development section.
Sent from GT-I9100
Do you have CWMrecovery?
If so boot into it, plug your phone in, select mounts, select mount usb storage.
If that works its firmware, if not its hardware.
If you have CWM recovery take your sd card out and copy a rom zip to it, boot into your rom, copy that rom into internal storage, reboot into CWM recovery, wipe data/cache and flash the rom from the apply zip from sd card menu item.
hi, I don't have cwmrecovery installed and it can be only installed via odin right?
In regards to ODIN i cannot get it to detect the handset to flash anything.
Hello,
my device (i9300) as mentioned above got stuck in a boot loop.
First I did was I installed the latest pac-man ROM from here. After successful testing I decided to flash the latest OmniRom 4.4 from here.
Now here comes the dilemma with: My Failure was that I had a old Recovery (CWM-based Recovery v5.5.0.4) and I didn't see the point where it says that I have to update it first.
My USB Connection to my PC was already broken before I started to flash any of the ROMs. So I can't connect to the PC to flash via Odin. It fails on the driver installtion. (I copied everything in my cloud and downloaded it to the internal sd)
The Device Manager shows alwas a ! in a yellow triangle near the "Samsung Mobile USB CDC Composite Device" (Download Mode) with a errer code 10: Device cannot start. I did millions of solutions but nothing worked against this issue ...
Currently my device starts where the Samsung galaxy s3 logo pops up, get stuck by that with a red 1 on the upper left corner and boots into the "old" recovery.
This is my Problem. Please help me to fix this (and the USB bug).
Thank you very much
Kind regards,
A.R.Cante
A.R.Cante said:
Hello,
my device (i9300) as mentioned above got stuck in a boot loop.
First I did was I installed the latest pac-man ROM from here. After successful testing I decided to flash the latest OmniRom 4.4 from here.
Now here comes the dilemma with: My Failure was that I had a old Recovery (CWM-based Recovery v5.5.0.4) and I didn't see the point where it says that I have to update it first.
My USB Connection to my PC was already broken before I started to flash any of the ROMs. So I can't connect to the PC to flash via Odin. It fails on the driver installtion. (I copied everything in my cloud and downloaded it to the internal sd)
The Device Manager shows alwas a ! in a yellow triangle near the "Samsung Mobile USB CDC Composite Device" (Download Mode) with a errer code 10: Device cannot start. I did millions of solutions but nothing worked against this issue ...
Currently my device starts where the Samsung galaxy s3 logo pops up, get stuck by that with a red 1 on the upper left corner and boots into the "old" recovery.
This is my Problem. Please help me to fix this (and the USB bug).
Thank you very much
Kind regards,
A.R.Cante
Click to expand...
Click to collapse
To fix the USB bug, you must uninstall that driver and download the driver ( try to install kies for example )
To fix the bootloop try to do a full wipe in recovery mode
abidifethi said:
To fix the USB bug, you must uninstall that driver and download the driver ( try to install kies for example )
To fix the bootloop try to do a full wipe in recovery mode
Click to expand...
Click to collapse
None of your advices worked. I did unistall all drivers and also Kies. Reinstalled and it doesn't worked. So I uninstalled it again and installed only the drivers but this didn't worked too.
Everytime I uninstall the drivers and connect the device to the PC it is trying to Install the Drivers over Windows Update and Kies isn't reacting at all.
Now since I wiped data/factory reset, cache partition, dalvik cache and formated /system and /preload my device won't start automatically in the recovery anymore. It get stuck on the Samsung Galaxy SIII Logo with the red 1 in the upper left corner. To Access to the Recovery I have to take the battery out and and insert it again and press volume up + home + power.
What can I do now?
Thanks in advance
A.R.Cante said:
None of your advices worked. I did unistall all drivers and also Kies. Reinstalled and it doesn't worked. So I uninstalled it again and installed only the drivers but this didn't worked too.
Everytime I uninstall the drivers and connect the device to the PC it is trying to Install the Drivers over Windows Update and Kies isn't reacting at all.
Now since I wiped data/factory reset, cache partition, dalvik cache and formated /system and /preload my device won't start automatically in the recovery anymore. It get stuck on the Samsung Galaxy SIII Logo with the red 1 in the upper left corner. To Access to the Recovery I have to take the battery out and and insert it again and press volume up + home + power.
What can I do now?
Thanks in advance
Click to expand...
Click to collapse
Try to download any custom ROM if you don't done yet and put it in your external sd card ( use an other phone or card reader ) and now try to enter in recovery mode and install it and let us know the result
abidifethi said:
Try to download any custom ROM if you don't done yet and put it in your external sd card ( use an other phone or card reader ) and now try to enter in recovery mode and install it and let us know the result
Click to expand...
Click to collapse
I tried this now on my Desktop Computer and it worked fine. I didn't need to install drivers manually. It installed it by itself and therefore i was able to use odin!
I flashed the new recovery and put the omnirom and pa-gapps on my sd card (I also tried this on my notebook but my card reader is maybe broken)
so i installed teamwin recvovery over pc, put rom and gapps on my sd card and flashed them over recovery.
Now all works fine.
Thank you for your help.
But what I don't understand is my Win 7 OS (32 bit) is recently set up on my VM everything was fresh but it didnt recognized my device... Google says a lot of people are having this issues. I've tried everything whenever I found allegedly a solution for this problem. None of them worked. I simply switched the computer and everything is fine. This is ridiculous. One year ago, when I had running windows as main OS, there were no problems at all. If the problem was caused by a virtual machine I think that not many people would complain about this issue.
Kind regards
Why would old Win 7 recognize your device unless you install drivers .
JJEgan said:
Why would old Win 7 recognize your device unless you install drivers .
Click to expand...
Click to collapse
I don't really understand your comment. The Problem of this USB error has no root. When your Windows System says error code 10: device cannot start then you have a big problem because you don't know why and how to fix this. Try and Google this. You will find thousands of people complaining the same error. Everyone has other solutions for that. Some edit their registry, others simply do a soft-reset and try another USB-Port.
Samsung support can't help you at all because they don't know why this is happening. And the solving of this problem is really random. i tried for hours to solve this with no success (except switching to another computer).
Windows says on my laptop the device cannot start but it is perfectly connecting to my other computer. How can this happen? I don't know. Maybe the error code 10 is not that specific and there is something other wrong than my device.
Hi, XDA! I need your help.
So I'm on this unofficial version of CM 12, link : http://forum.xda-developers.com/galaxy-s3/development/wip-cyanogenmod-12-t2936990
I was on Weekly 8/7/6 of it( I don't remember exactly) (refer to changelog, the top entry date 1/4/15 is weekly 10) and wanted to upgrade to weekly 3(refer to changelog), of cm 12.1 made by the same guy who made the rom i was using, link: http://forum.xda-developers.com/galaxy-s3/development/5-1-x-cyanogenmod-12-1-t3066864. I dirty flashed(if that's what flashing a new rom on top of an old one without factory resetting means) because it was just CM 12.1 ported to S3, and i thought that CM says on it's website that you don't need to factory reset to flash a rom which has a new android version.
When I opened recovery mode, I found out that I had this new recovery, called Cyanogen Recovery. I was like 'Whatevs'. I flashed the new ROM, but about halfway in, it stopped and on the top of the failure report, it said: "cannot load volume /misc" it also said further down "signature verification failed". Now let me tell you that this recovery is pretty limited,no mounting features, no system wiping, no dalvik cache wiping, no signature verification toggle, etc. and on top of that, factory resetting, wiping media or cache didn't show a log of it as it happened, so you didn't know whether it had actually happened. My phone was bricked and it would stay keep going on the starting screen( the head of The CM mascot, the blue android bot, with ripples spreading from it)
I was like 'okay, i can do this'. I connected my phone to my pc, installed samsung usb drivers from the net, installed Odin, downloaded philz touch recovery ( a tar md5 version) (to flash it using ODIN and then flash one of the different cm 12/ cm 11 roms located in my external sd card,using the new recovery) , put the phone in download mode, but Odin wouldnt recognize it. It was admin mode, just so you know. No ID:COM would show up. I tried everything, putting in download mode before connecting it to the PC, reinstalling the drivers, trying different versions of the drivers, trying different versions of Odin, allowing Odin all access and security permissions for all users to my PC, compatibility mode for windows 7(im on win 8), factory resetting, wiping media and cache, using different wires and ports, even the ones on the back of the system unit(system box or CPU), doing all this stuff on my mum's laptop(it's a windows 7 laptop), like doing almost everything. My phone starts charging, so it isn't a problem with the phone. I looked up the issue on Google, and found other people had the volume /misc and signature issue too. My phone starts charging when I connect it, so it isn't an issue with the phone's micro USB port, but if it is, please tell me. I read somewhere that USB debugging might have something to do with it, but I can't change that setting cos' my phone's bricked.
XDA, HELP ME PLEASE!
If you can still go to your cm recovery, you can install philz from there.
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/i9300/philz_touch_6.48.4-i9300.zip
Download the zip file, flash it through cm recovery , turn off your phone and boot it to new recovery.
https://www.dropbox.com/s/qzgn1abhr4qcmls/Ultimate_Kernel_Cleaning_Script_v1.0_en_SGS3.zip?dl=0
https://www.dropbox.com/s/f1zbm0tvsvh5ww5/MegaWipe_-_GS3.zip?dl=0
Also use these two to wipe clean your entire phone even kernel or system leftovers. If odin still doesnt see your phone, try to install a custom rom
Hi,
I was using S6 edge from almost 2 years and I rooted it after 1st year of use.
I installed many roms including few stock roms and changed many recovery modes using ODIN. I was using TWRP recovery for many days. I used to wipe all the data( including internal storage ) from recovery mode itself which wipes out the custom rom too. After wiping out, the phone usually boots to recovery mode as it is the only thing present on it and the system detects it as a USB storage which allows me to copy a new rom on to the internal storage of phone.
I did the same thing now and wiped out all the data using TWRP recovery, and after that phone boots to recovery mode as usual. But this time system is not detecting the phone's storage and so I tried to install a stock rom using ODIN. Then to my surprise, ODIN also doesn't recognize the phone this time. I tried to disconnect and connect again, it says 'USB device not recognized'.
I was using the same USB drivers from almost a year and still, I tried to uninstall and re-install the USB drivers, the problem remains the same.
I am not sure what to do here as ODIN itself is not detecting. I tried all USB ports with different cables, but not use.
Can anyone suggest me a fix for this?
Thanks in advance.
Samsung authorized service center says system is not detecting mobile even for them and needs to replace the motherboard....!!
Hi all,
I'm trying to get my old s2 to a point where I can think about flashing one of the Lineage roms 14 or 15.
First hurdle is that i need to replace the current custom recovery (Philz 3) with TWRP. Ordinarily I'd do this through Odin and not think twice about it. However I cannot get my windows machine to recognise the USB connection to the phone. It will charge and nothing more. The phone obviously used to connect, many years ago.
Device : Samsung Galaxy sII - GT-I9100 (has root)
Recovery : Philz Touch 3 - CWM Base 6.0.1.8
OS : Jellybean 4.1.2 (stock unbranded)
PCs : Win 7 ent x64, Win 10 ent x64, Win 10 ent x64
I've scoured the forums here and have tried the following to get the usb connection working.
Tried 4 different usb cables across 3 different PCs
Tried with USB debugging on and off
The phone does not have any options to choose the type of USB connection I want (MTP etc)
Tried installing kies and drivers
Tried installing device drivers only (specifically for this model)
Tried installing device drivers (whole package)
Tried switching engineering mode to modem and back to usb through *#7284#
Tried a recovery flashable zip version of twrp 3.0, through Philz (it fails)
Tried cleaning the contacts on the port on the device.
Have stripped out the old device usb port and installed a new one.
Have tried to install mobile odin but it fails to get update (addon package from xda, and will not run)
Have tried various timings of plugging usb into the phone when entering download mode
Have factory reset the phone from OS
Have factory reset the phone from recovery
Have tried clearing the various caches and wiping pretty much everything.
The phone reliably boots into OS, recovery and download modes.
Other android and samsung devices are seen by all the PCs I've tested on
At no point are the PC and the s2 connected
Is there another way to flash twrp to recovery?
Is there another way to flash a complete stock rom including stock recovery, to start from scratch.
What else can I try? Any help greatly appreciated.
Cheers P
Ptolamy said:
(...)Is there another way to flash twrp to recovery?
Is there another way to flash a complete stock rom including stock recovery, to start from scratch.(...)
Click to expand...
Click to collapse
A safe method to start with. Place twrp-3.0.3-0-i9100-signed.zip and the recovery.img extracted from it and lineage-11-20191223-UNOFFICIAL-i9100.zip in the SD memory.
Run the current recovery and select the recovery zip or img installation from the external SD memory.
I don't know PhilZ Touch so I don't know where to choose zip or img.
Restart recovery mode and make a backup in TWRP to the external SD memory.
Only then wipe the Cache, System, Data, Dalvik and install ROM.
Many thanks. I'm gonna give that a go this evening. Will report back on how it goes.
I feel like my usb connection woes will disappear if i get a new rom on it.
Cheers.
Manages to update to Philz to version 6 ...I after which I did get the lineage Rom onto the phone but it booted once then went into a boot loop.
I gave up
Thanks for those who helped anyway though.