Hi,
My Phone is now hanging up at the ":
"Samsung Galaxy S6 powered by android" screen
I can still get into recovery and downloadmode.
The pc "sees"the internal storage, but it wont allow me to copy a rom or anything to it,so that i may reflash a rom
Also if i use the "kies"or "smartswitch" programme, it says it cant connect to the Phone.
if reinstelled the samsung driver via kies
Also i have tried deleting the kies and driver from the pc, rebooting and reinstalling kies and driver, bit still the same result
It seems to me that if i could get a rom back on the internal storage i would be able to flas a new rom and get things working again?
Can anyone assist?
thaanks in advance
Related
Hi. newbie here..
I successfully flashed darky 9.3 rom..bit here is the problem...I can't access my internal SD card and external SD card. they dont show up on the phone and on the pc if I plug it in.. why is this so?
I tried to restore to my custom rom using clockwork backup/restore and it is successful..after rebooting it gets stuck on the galaxy s logo..
Can anybody help me?
You mean access from your computer or access from the phone itself?
I doubt the phone would boot, if it couldnt access /sdcard.
Did you check the Settings?
Try to select 'Ask on connection'
Same initial problem
I have the same problem. After connecting phone to pc no message on pc nor on phone itself.
While connected to pc phone windows shows something like "one of the devices plugged to usb had a wrong behavior and Windows cannot recognize it"
I wondered why the phone doesn't show the usb connection option anymore.
I tried switching all options (kies, massive storage, ask on connection), reflashed the costum rom and restored factory settings. But no way to establish usb connection.
GT-i9000 with 2.3.3 custom rom since april 2011
Well, suddenly my phone works again. I have usb connection back... I can' t explain it.
But I can flash roms again!
Sent from my GT-I9000 using Tapatalk
im stuck on the samsung galaxy s 19000 boot screen and i can go into download mode but not into recovery... but the problem is that i cant get my phone to connect to computer thru kies or anything and i tried using another cable and computer...can anybody help me plaese??
Did you install the drivers for your phone on the computer? I was in a similar situation with a Samsung fascinate. I got stuck on a boot/flash loop. What I did was look for the phones drivers, installed them on the computer, get it into download mode (with the android shoveling), looked for the Odin software, looked for the fascinates factory rom, and flashed it through Odin.
Sent from my ADR6300 using XDA App
yea i installed the drivers and reinstalled them but it still says usb device not recognized and on device maneger says unknown device and i dont know waht to do.. if it at least get it to connect once i will be very happy
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
Today I was messing around with flashify and tried updating my TWRP recovery. Something went wrong...
The tablet is now stuck at the first Samsung boot screen and loops constantly.
I am running GNABO v8 ROM.
Kies is as useless as usual.
I can get into download mode, but my PC (windows 8.1) won`t recognize the device (Device Descriptor Failure). This is a problem I have had since installing GNABO, but unfortunately now I cannot use ODIN.
I have downloaded and installed the correct Samsung drivers but the PC won`t recognize them automatically.
I want to try to force install the correct driver, but they have weird names like swallowtail, Shrewsbury etc etc.
My question is which driver / .inf file should I try to install?
I accidentally deleted the root to my s3 and left it unrooted, im not too sure what else I accidentally deleted but I've been trying to reroot it with it's stock firmware... But its extra hard since my computer detects the device but refuses to connect with it and does not let me interact with it at all (open internal storage). When I start it up, it only shows the SAMSUNG screen and then the Samsung Galaxy S3 screen and then just stays there.... I tried rerooting it using Odin3 but the connection from the phone to the computer failed so now my phone is stuck on the screen where it says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." So i downloaded Kies but again, I cant access the device through computer so Kies says, "Device not responding. To resolve issue, reboot the device." Please Help!!!
As this is a double post I will lock the thread.