Tried to flash my YP-G70 int. with new May 2012 OS through ODIN. I followed the guides and Info. and It flashed fine, passed and everything, up until it started bootlooping on 1st re-boot.
Its still in Download mode "Yellow Android digging" screen, but my PC will no longer recognise it, saying "device has malfuncvtioned" so it wont show up in ODIN.
Im using Win7x64 with x64 samsung drivers, i also have a laptop with XPx86, but it wont reconise it on that either.. any advice.
Thanks in advance
FIXED:
I hope this helps someone with USB issues:
I installed Kies, then uninstalled but kept USB Driver..
I then held down power button for 10 secs for forced RESET, started bootlooping again.. put it back into D/L mode (Vol Dwn + Pwr) and it recognised the MTP device, opened ODIN flashed rjs and it booted fine
The problem is with my model: the only way it will work with stock rom is with rjs kernel, it bootloops with KPF Stock (the KPF on rjs post thread).
Any Tips or advice
Related
MUIE DUTZU!
Had a SGS2 I9100-G, Gingerbread 2.3.5, XXKI4.
1)Tried to flash ICS RR, rebooted, stuck at SAMSUNG LOGO + Exclamation mark;
2)Tried to flash STOCK ROM, got NAND error in Odin, PC - ! - Phone logo shows up;
3)Flashed the GINGERBREAD VERSION kernel from [GUIDE] Fix an unflashable or soft bricked GSII (I9100G/M/P/T VERSION INCLUDED!), rebooted, now the SAMSUNG LOGO + Exclamation mark shows up again;
4)Tried to flash Lightning ROM, Odin failed after writing a while, PC - ! - Phone logo shows up again;
5)Did step 3 again;
6)Tried to flash the Recovery Package/ROM from [GUIDE] Fix an unflashable or soft bricked GSII (I9100G/M/P/T VERSION INCLUDED!) without .PIT and without Re-Partition (steps 1-4), got NAND error;
7)Did step 3 again, JAM;
-----------------------
Now my device cannot be powered on by any combination of buttons, except when I connect it to a power source(PC, AC). After I plug the device, the SAMSUNG LOGO + Exclamation mark shows without any push of button and I cannot acces DOWNLOAD MODE anymore.
Tried evey combination possible: download mode combination before the device gets plugged in, after, long pressing, short pressing ... and nothing.
How can I fix this?
Thank you.
Later: I've made myself a jig. I'll post a photo with it later when I'll manage to get this done.
Later2: **** IT! The jig worked just fine, entered download mode a couple of times. Noticed the counter was still the same, but I didn't care as long as I had could access the download mode. Now the jig is useless ... the download mode no longer shows up. The solding is fine, but I don't see any reason for the jig to stop working. Any ideas?
MUIE DUTZU!
Bump!
I solved the problem minutes ago. Here's what happened:
1)I was getting the NAND error because the KIES service was still running, althou the processes were killed;
2)The USB cable I was using wasn't working as expected, althou the drivers were installed correctly;
3)The ROM I was trying to flash isn't compatible with 9100G, that's why I had bricked it;
4)When I was unable to access download mode, I've made myself a JIT and succeded to flash a new kernel, but suddenly it stopped working; the JIT was no longer able to enter the download mode ... because the device's battery was empty;
5)Finally I flashed a STOCK GINGERBREAD ROM through PDA and everything went good.
Thanks ... for the views.
Hope this helps someone else.
Hello,
Some threads with similar issues are already around, but I didn't find one with the same problem as me.
What I was doing when the issue happened:
I was trying to install cyanogenmod from the isntaller method (apk isntalled on the phone, application running on windows that installs it automatically). At certain point, it rebooted the device and the cyanogenmod logo was on the screen. After a while, the program gave an error "'We couldn't talk to your phone' - Samsung devices ONLY", which is described in their wiki. So the pc lost connection to the phone.
What I did:
1 - Since I had installed the clockwork recovery and tested it before, I thought "hey, no problem. I'll hust recover this S*it". So I disconnected the SIII from the PC and tried to enter recovery mode pressing "volume ip + home + power". While I have these pressed, the phone in in an infinite loop on the initial screen showing the brand and model. When I release them, it goes straight to the cyanogenmod blue creepy robot just there staring.
2 - Since that didn't work out since I now don't have a recovery mode and I don't have any functioning rom either, I found several tutorials for using Odin and reflashing and or repartitioning. PROBLEM: Odin seems to recognize the phone (com port), I click on the option and... FAIL!
2.1 - What I have tried: Different Odin versions (1.83 and 3.09), stock drivers from Kies, Zadig drivers.
So. There you go. I pretty much exhausted everything I could get from my head and interpret from google. So, No recovery, no ROM, fail at odin.
Any ideas?
Thanks in advance.
Remove kies from the pc reinstall drivers and flash a cwm recovery. From there flash a custom rom in recovery from ext sd. Odin 3.04 is good. I would keep trying to get into recovery though. Do you have that red mark in the corner on Sammy splash screen?
Hi Please help.
I had jellybean running on my phone flashed with philzcwm and did it wit Odin. My phone crashed so i did a factory restore from it now its suck in this mess. (Volume up+Home+Power) and wont read SD card and hangs on this image.messages. Volume down+Home+Power displays Odin mode to download And hangs on this image. Windows 8.1 will not detect phone at all ive tried downloading all drivers needed and still not working. Ive tried different SD cards and USB cables Front and back.
Hello! I'm new in flashing and i think i need little help, because i'm afraid i can brick my phone. I wanted to install CM on my GT-9100. I run stock JB 4.1.2 on it.
I started with flashing Clockworkmod from this thread http://forum.xda-developers.com/galaxy-s2/orig-development/kernel-clockworkmod-recovery-6-0-2-9-t1118693 . I had some troubles when installing samsung USB drivers - installer interrupts in the middle - but when i pluged my phone into PC Win8 installed some drivers automatically so i thought i can give it a shot and flashed CWM. I got pass status in Odin, reboot my phone and now when i try to run it everytime i get past starting screen with yellow triangle, the screen goes black and i can only hear starting sounds. I can enter both download mode and Clockworkmod recovery, so i figured out i'll try to backup and go on with instalation, but when i plug my phone into my computer it doesn't see my phone so i can't copy any files. I also tried to plug it on Ubuntu and on the other PC with Win7 and Kies installed but it doesn't work there either.
Do you think the drivers might be an issue? What do you thin I should do? Should i go on with CM instalation, wipe cache or what? Thanks in advance.
A while back I unsuccessfully tried to root my Samsung Galaxy S3.
The phone still worked OK, rebooted fine, etc., was using it for months.
Just recently though I decided to factory reset so I can give my phone to a family member, and this happened (see pics below ). Now it just hangs on T-Mobile screen and never boots at all.
http://imgur.com/gallery/0BWqcUA
Can anyone point me in the right direction to flash the default factory image back on there.
This is with T-Mobile in case that matters.
Thanks in advance.
UPDATE:
I located this thread:
http://forum.xda-developers.com/galaxy-s3
Also tried downloading this driver:
http://www.samsung.com/us/support/owners/product/SGH-T999ZWATMB
The problem right now is neither ODIN nor ADB sees my device. I have the device in "Downloading" mode (boot power down key, home ,power button).
Also tried the up-volume boot and adb side load.
Uninstall all Samsung drivers, reboot, and install Samsung Kies. This will setup the drivers you need, then you can use Odin to restore. If this doesn't work, try different cables, ports, or another computer. Check in Device Manager to see which driver is loading and manually switch if needed.
PS. You're not going to be able to communicate with the phone via adb without it booted and USB Debugging enabled or with a custom recovery that you're booted into.