Hello there!
I was following this tutorial using mskip's SGN II toolkit. Everything is fine, except the 0:[COM:4] wont appear and light up light blue after I connect the phone.. Everything stays white.
The drivers should be fine, the serial number appears and it recognises the phone anyway.
What should I do?
Regards,
robi54321
It's interesting, that when I close the toolkit and boot manually into download mode, plug the phone in and open odin, it turns light blue as it's supposed to. It's not working only when running from the toolkit.
Related
Well I followed the [HOW TO] Debranding /Installing different/recovering bricked firmware on your Defy by Higgsy and All it gave me was a black screen and my led light white!! heard the white led is good but My PC wont recognize it tried reinstalling and updating, even clean and reinstall all the drivers for it but nothing.. I used the JORDN_U3_6.36.0, and even the JORDN_U3_6.19.0 for T-mobile USA and rsdlight worked thought I hade it but now I cant even pull up Bootloader the LED Will only come on when I plug it into PC I cant even charge it... NO screen at all on phone when I connect to pc or charger tried recovery mode boot loader still nothing the only thing I get is when i plug into pc and thats a white LED.. SOMEONE PLEASE HELP
You need to let it plugged in for a while so that it can charge. You can't see it though. Install driver and rslite. Then open rslite sbf hope your phone gets found. Then flash an sbf. There us a full guide on the forum somewhere. Can't post link from post.
edit: search for McGyver. Its a guide to unbrick a phone like yours.
Sent from my MB525
Hey Everyone,
I'm hoping someone can help me find a way to un-brick my Galaxy Nexus GSM 16GB (GT-I9250M). Before you call me an idiot, I'll have you know I wasn't flashing it or anything. I was simply listening to music when the screen went all glitchy and the sound started looping. Then the phone attempt to restart, but mid way through booting, it would glitch out again. It would repeat this until I finally pulled the battery. When I got home, I tried to get it into Fastboot mode or Download/Odin mode. Neither of which worked. I was running the stock version of android. If I recall correctly, it was running 4.0.2.
So in a nutshell, here's the status of the phone:
Regardless of what I do, Fastboot mode and Download/Odin are not accessible.
No matter what combination of buttons I press, the screen always shows: Phone ... Yellow Alert Triangle ... Computer
Using Galaxy Nexus Toolkit or Wug's Toolkit, the phone is not listed under Fastboot or ADB devices.
While the phone is plugged in via USB without a battery, I see device manager adding and releasing an OMAP4440 device every second or so.
When I plug in the phone (with the battery) in via USB while its off, it will turn itself on showing the alert screen mentioned above.
ODIN is about the only app/toolkit I've used that "sees" the device.
Using ODIN, I have tried various stock images mentioned in the forums. All of them have either failed or get stuck on "NAND Write Start!!"
I've read dozens of posts on various forums but I could not find a concrete solution, so I'm appealing to you guys for help. Any help would be great appreciated.
Thank you!
Based on what you have described, even if I could get it working again, I would try to get a warranty replacement, provided that is an option. Sounds like a hardware failure. Like I said, even if it somehow started working again, I wouldn't trust it.
1. first off you need to download "Odin 3 v1.85" here
2. also download CF-Root-GGN_YAKJU_ICL53F-v5.1 here
3. open Odin in your computer
4. where it says PDA put CF-Root-GGN_YAKJU_ICL53F-v5.1
5. Power on the device and when you have the "phone triangle pc screen" connect it to your PC.
6. ???
7. PROFIT!!!
kmdub said:
Based on what you have described, even if I could get it working again, I would try to get a warranty replacement, provided that is an option. Sounds like a hardware failure. Like I said, even if it somehow started working again, I wouldn't trust it.
Click to expand...
Click to collapse
You're probably right. I still have my Nexus S which I can fall back to resort to this. I will try what nonione has suggested, and if that doesnt work, I will likely look to replace the phone.
I've never seen a samsung phone that couldn't be recovered (other than physical or water damage).
You can easily get the phone back with odin (no you do not have to be in odin mode on the phone).
Study up on it....tons of threads, use search.
Never seen a bricked Samsung....ever...and I've had at least 6 or 8 different models.
(edit)
There;s quite a bit more to it than nonione tried to walk you thru.
You will need the correct drivers on your computer first...buncha other steps too.
Study hard before you try odin.
Google, "Galaxy Nexus OMAP Unbricker". Download it and when the OMAP devices comes up in the Device Manager quickly right click on it and install the driver includes with the OMAP download. Once the driver has installed run the .bat file in the download. Should go to Fastboot now.
Then:
http://forum.xda-developers.com/showthread.php?p=27160425
Download the .pit file here:
http://forum.xda-developers.com/showthread.php?p=27152659
Sent from my SGH-T769 using Tapatalk 2
That's easy to repair, dude
That's not a brick, that's just telling you, that the firmware files are corrupt, all you need, is a jig, a Windows PC, Odin and chainfires ODin files
I can walk you through, on Teamviewer, if you want. I've had this problem quite a lot (Not on the GNex, though) I jope I get it, so I get a GS 3 ^^
I do have the same phone with the same problem..but currently out of the country, so cant get it replaced.. I get no yellow triangle my phone is completely dead..I tried the omap flash no luck..please let me know if the omap flash tool worked for you..
Hey guys,
So a bit of an update. I tried using Odin to flash. None of the files suggested worked for me. I also tried the OMAP flasher. While it "did something" without erroring out, it did not switch to fastboot mode for me. My phone is simply stuck in that yellow alert state. So now, i'm going to try using a Jig as familyguy59 has suggested. I saw a video of one guy use one to fix the exact same issue as I'm having, albeit with his Samsung Galaxy 2, but it looks promising. I purchased one a couple days ago and it should come soon. I'll let you guys know how it goes.
Hey Guys,
So I tried the jig i bought. No dice. I'm pretty disappointed. : / I guess off to Samsung it goes... I just don't have any luck with Samsung products.
Hey all, just got my S3 today on Rogers, first thing I tried to do was root it. Being my first Android phone, I had absolutely no idea what to do, and following a Youtube video I tried to use the Galaxy S3 Toolkit (V4). After Odin did it's stuff, my phone will no longer boot, whether it be normally, Download Mode, or Recovery Mode. If I try to power it on any of these way, the phone will vobrate, the Samsung logo appears for a second, and then shuts off again. Is it done for?
If so, what are my next steps here, I just got the phone, Rogers has some defect replacement option for the first 15 days or something, should I treat it as that and try to exchange it? Thanks for any help!
GtwoK said:
Hey all, just got my S3 today on Rogers, first thing I tried to do was root it. Being my first Android phone, I had absolutely no idea what to do, and following a Youtube video I tried to use the Galaxy S3 Toolkit (V4). After Odin did it's stuff, my phone will no longer boot, whether it be normally, Download Mode, or Recovery Mode. If I try to power it on any of these way, the phone will vobrate, the Samsung logo appears for a second, and then shuts off again. Is it done for?
If so, what are my next steps here, I just got the phone, Rogers has some defect replacement option for the first 15 days or something, should I treat it as that and try to exchange it? Thanks for any help!
Click to expand...
Click to collapse
Had to be user error, so in order to get some help you're going to have to do some backtracking and try to narrow down what went wrong. Does your computer recognize your phone when you plug it in via usb? Can you still connect to the toolbox or adb prompt?
Try a USB jig and see if that forces you into download mode. Then you can ODIN back to stock. I don't think its done for if it boots to Samsung logo.
Make sure you pull the battery and then put it back in. Then try and access recovery or download mode again.
Newbie here.
So I've rooted and flashed CM10 on my phone. I'm trying to restore my phone back to the way it was when I first got my phone (with samsung touchwiz, tmobile bloatware, etc.)
I'm trying to flash the stock rom using Odin but when I connect my phone to my computer, the box turns blue instead of yellow. I can confirm this is not a driver issue and usb debugging is enabled on my phone.
kwookoh said:
Newbie here.
So I've rooted and flashed CM10 on my phone. I'm trying to restore my phone back to the way it was when I first got my phone (with samsung touchwiz, tmobile bloatware, etc.)
I'm trying to flash the stock rom using Odin but when I connect my phone to my computer, the box turns blue instead of yellow. I can confirm this is not a driver issue and usb debugging is enabled on my phone.
Click to expand...
Click to collapse
Man I swear I just reset my phone from cm10 to stock just now using odin 1.85v. Just download the stock md5. I got it from here.
unzip it,put your s3 into download mode. Forget usb debugging and all that doesnt matter here. Once you're in download mode. Plug your phone to your computer. Start odin. check pda, click on pda, browse to the file you extracted from this link, and click start. thats all you have to do. Wait til it's completed and then if your stuck in a boot loop. Go into stock recovery using vol. down home and power and wipe data/ reboot and you should be good!
Hit the thanks bruh...
kwookoh said:
Newbie here.
So I've rooted and flashed CM10 on my phone. I'm trying to restore my phone back to the way it was when I first got my phone (with samsung touchwiz, tmobile bloatware, etc.)
I'm trying to flash the stock rom using Odin but when I connect my phone to my computer, the box turns blue instead of yellow. I can confirm this is not a driver issue and usb debugging is enabled on my phone.
Click to expand...
Click to collapse
If you're talking about the COM whatever box in the actual ODIN software, then it doesn't matter if it's blue or yellow... it's just different versions of ODIN that are floating around.
Hello.
I just try Cyanogenmod installer and everything was ok till during installation, with blue cyanogen guy displayed on my Note II, the PC application says : sorry, can't talk to your phone. And since then i stuck with this blue guy on my phone. And application in PC stuck on Detecting Device screen. Can't even go to recovery mode on phone, holding down volume up\home\power do nothing, this blue guy shows again. Anyone have situation like this and find some solution maybe ? Every help will be appriciated
small update : ODIN don't see the phone.
withoutnickname said:
Hello.
I just try Cyanogenmod installer and everything was ok till during installation, with blue cyanogen guy displayed on my Note II, the PC application says : sorry, can't talk to your phone. And since then i stuck with this blue guy on my phone. And application in PC stuck on Detecting Device screen. Can't even go to recovery mode on phone, holding down volume up\home\power do nothing, this blue guy shows again. Anyone have situation like this and find some solution maybe ? Every help will be appriciated
small update : ODIN don't see the phone.
Click to expand...
Click to collapse
Hold on Vol up + Menu and then Power key for 4~8sec it'd reboot into recovery mode. Otherwise remove phones battery & insert and try boot into recovery/download menu.
I'm not able do anything except boot in download mode, but then i can't do anything, Odin still don't see phone
Do you've right drivers installed for PC & os?, because of missing drivers it doesn't show the phone.
Sent from my GT-N7100 using XDA Premium 4 mobile app
withoutnickname said:
I'm not able do anything except boot in download mode, but then i can't do anything, Odin still don't see phone
Click to expand...
Click to collapse
what m.b.jikre said or make sure you use original samsung usb cable to connect your phone and try another USB port on your computer/laptop
for some mysterious reason, using win 7 installed on my mac.......works . now i run cyanogen, so far without problema, just after every reboot of phone i must agree to terms of play store
same problem
Having the same problem, except I don't have Odin, the blue guy keeps appearing when I try to boot into recovery or download mode. Using Samsung galaxy S2 gt-i9100. I rebooted my PC as suggested by the cyanogenmod installer, but now it doesn't detect device. Pls help