I hope this is the right place to post this. I'm new to rooting and flashing but did tons of research and got my vibrant rooted and running great with Nero v.3. Did the same to my roommate's phone with equal success. I tried the Gingerbread experimental rom from Team Whiskey and now I can't get rid of it. I've tried using Odin like the post says but my phone won't go into download mode no matter what I try and Odin won't recognize it, so I can't flash the voodoo kernel back. I've tried every combo of buttons and battery, sim, sd card removals, etc. I got sdk android set up and followed all the posts but when I try adb reboot recovery my computer says adb is not a known command, process, or batch file. I have the environment variables set up in advanced settings for my computer but still nothing. To make it worse my phone had no service detected now and keeps powering itself on and off consistently. Any advice on why adb won't work or another way to get to download mode? Something other than odin?
For one, ADB is not set up correctly if you are getting that error. I had to manually adjust the environment settings on my Win7 pc to get it to run right. It does not write it correctly to Win7's environment settings for some reason.
Second, if you cannot get into DL mode, you could always try this:
http://forum.xda-developers.com/showthread.php?t=889128&highlight=jig
It says for Captivate but should work just fine on the Vibrant. There are other threads on this in the i9000 forums as well.
adb
So can anyone help with the setting required for Win 7 in the environment settings to get ABD to work?
criswell01 said:
So can anyone help with the setting required for Win 7 in the environment settings to get ABD to work?
Click to expand...
Click to collapse
Did you place a copy of the adb.exe and the adbwinapi.dll into your system32 folder? Thats necessary to allow adb to be run from any command line location.
Ginger Clone's of the World Unite! Via the XDA App
Sorry for all the questions but where would I find the system 32 folder?
You need to insatll the nexus s drivers for adb and odin to.see.the phone.
For download mode, turn phone off, unplug the usb. Hold vol up and down and.plug.in.usb. will put you right into dl mode. If it doesnt...then you.need a jig
Sent from my SGH-T959 using XDA App
criswell01 said:
Sorry for all the questions but where would I find the system 32 folder?
Click to expand...
Click to collapse
Your system32 folder is on your windows machine. C:\windows\system32
Ginger Clone's of the World Unite! Via the XDA App
I know nothing about ADB, nothing at all, however I was able to install it with no problem, and it detects my phone.
I followed the step by steps directions posted directly by Google.
edit:
Seems like I installed SDK. Wait are the two the same?
Anyway, I followed the directions at the link below, and seems like I'm running ADB via command prompt.
http://developer.android.com/sdk/index.html
click on "installing the sdk"
edit:
yup, sure enough I have ADB. LOL now i'm confused. SDK and ADB are the same? Anyways, I followed the link above, installed sdk, and I have ADB too. I'm using drivers via samsung kies.
The android sdk installs adb I do believe. I've gotten into the habit of just copying my sdk folder to (random pc's) c drive, if I'll need the functions in there, and/or copying the two files over and going in commando style. Just copying the files over to system32 on most pc's will give you basic adb commands, for more advanced functions sdk is necessary. Probably not the surest way but its been working for me.
Ginger Clone's of the World Unite! Via the XDA App
SamsungVibrant said:
I know nothing about ADB, nothing at all, however I was able to install it with no problem, and it detects my phone.
I followed the step by steps directions posted directly by Google.
edit:
Seems like I installed SDK. Wait are the two the same?
Anyway, I followed the directions at the link below, and seems like I'm running ADB via command prompt.
http://developer.android.com/sdk/index.html
click on "installing the sdk"
edit:
yup, sure enough I have ADB. LOL now i'm confused. SDK and ADB are the same? Anyways, I followed the link above, installed sdk, and I have ADB too. I'm using drivers via samsung kies.
Click to expand...
Click to collapse
Again, you need to install the Nexus S drivers.
http://www.fileserve.com/file/5bgRBX5
Download and extract.
When you plug your phone in, go to Device Manager, you'll see that Nexus S was unable to install. Right click and choose update driver.
navigate to where you extracted the files to, and install.
It will now install the ADB driver, which also allows ODIN to see the phone in Download mode.
First thanks to everyone for the help and suggestions. I've got adb working now, it recognizes my phone and the adb commands work. I updated the nexus drivers in the device manager. Now when I connect the phone and use the adb reboot recovery command it shuts down, goes to a charging screen for a second, then boots back up to gingerbread. I tried using the adbrebootdownload in the adb bat file and once again the phone shut down and booted back up to gingerbread. The phone is unusable but doesn't seemed to be "bricked" (based on my understanding of bricked). Very frustrating. I had Nero v.3 with voodoo working amazing, Im so pissed at myself. Any other thoughts?
to get to download you need to do the 3 button combo.
power down, unplug, hold vol up and down, and plug in usb.
Thanks but the three button method wont work. Am I wrong in assuming that using ADB you can get into download mode without using the button method? The op said that all I need to do is use odin to flash the previous kernel to get the phone back to nero. I'm stuck! Has anyone had problems using adb recovery?
krylon360 said:
Again, you need to install the Nexus S drivers.
http://www.fileserve.com/file/5bgRBX5
Download and extract.
When you plug your phone in, go to Device Manager, you'll see that Nexus S was unable to install. Right click and choose update driver.
navigate to where you extracted the files to, and install.
It will now install the ADB driver, which also allows ODIN to see the phone in Download mode.
Click to expand...
Click to collapse
No, I got ADB working by installing SDK, using the link I provided, and using the normal drivers from kies. However, I did this a couple months ago, maybe the driver requirments have changed now, I'm not sure, but it works for me.
criswell01 said:
Thanks but the three button method wont work. Am I wrong in assuming that using ADB you can get into download mode without using the button method? The op said that all I need to do is use odin to flash the previous kernel to get the phone back to nero. I'm stuck! Has anyone had problems using adb recovery?
Click to expand...
Click to collapse
The adb command for download mode is adb reboot download, be sure usb debugging is switched on on your phone. If that doesn't trigger download mode, I think the jig is your only hope.
Ginger Clone's of the World Unite! Via the XDA App
criswell01 said:
Thanks but the three button method wont work. Am I wrong in assuming that using ADB you can get into download mode without using the button method? The op said that all I need to do is use odin to flash the previous kernel to get the phone back to nero. I'm stuck! Has anyone had problems using adb recovery?
Click to expand...
Click to collapse
Try this method:
1) remove batt, sim, and sd
2) plug in usb cable (and attached to computer with odin open)
3) hold down both vol keys
4) pop in battery
This always works for me.
Related
Well, im having some problems going into Download Mode...i have tried lots of different combinations, tryed using virtual terminal, toying with the USB Cable and the battery, any suggestions? Is there some kind of bug that affects phones making them unable to go into Download Mode?
I can get to Recovery just fine, the problem is Download Mode.
What are you running?
Can you describe what you are doing (rather than me list it out if you are already doing it right)
be detailed.
s15274n said:
What are you running?
Can you describe what you are doing (rather than me list it out if you are already doing it right)
be detailed.
Click to expand...
Click to collapse
Well, im running latest CM7 Stock.
I have tried pressing both Vol. Up and Down and connecting the USB. Also tried taking the battery out, pressing both buttoms, connecting USB and then insert battery back. Also tried with the Pwr buttom pressed too, but it just goes into a bootloop in the Vibrant screen, and after i release the Pwr buttom, it goes to recovery.
I also tried using Virtual Terminal, and using "reboot download", but it just does a normal reboot, and goes back to the ROM. Am i missing something?
Have you installed the Nexus S drivers?
Here you go, if not.. from the FAQ:
Q: Where can I get the Nexus S drivers?
A: Download and install the Android SDK here then download "Google USB Driver package, revision 4"
Once downloaded, right click on "Computer", "Manage", "Device Manager", "Nexus S", "Update Driver Software", and point it to wherever you isntalled the SDK
s15274n said:
Have you installed the Nexus S drivers?
Here you go, if not.. from the FAQ:
Q: Where can I get the Nexus S drivers?
A: Download and install the Android SDK here then download "Google USB Driver package, revision 4"
Once downloaded, right click on "Computer", "Manage", "Device Manager", "Nexus S", "Update Driver Software", and point it to wherever you isntalled the SDK
Click to expand...
Click to collapse
Thanks for that, but even after installing that driver and being able to use ADB (thanks to the driver, now i can use adb), the phone still can't go into Download Mode.
Anymore suggestions? Im not using the stock cable that came with my phone because i bought it from a friend, and he was using a BB charger and usb cable, and he gave me those to me.
Bump! Bump! Need some help here!
Now that you have ADB and the drivers... can you now use "adb reboot download" with success?
Do you have odin up and loaded, usb into pc, battery out, plug into phone, holding both volumes insert battery... still nothing?
s15274n said:
Now that you have ADB and the drivers... can you now use "adb reboot download" with success?
Do you have odin up and loaded, usb into pc, battery out, plug into phone, holding both volumes insert battery... still nothing?
Click to expand...
Click to collapse
I have Odin open...but how do i know if its "up and loaded"?
"adb reboot download" doesn't work, neither "usb into pc, battery out, plug into phone, holding both volumes insert battery"...altough, with the phone not connected to the USB, i pressed Vol UP, the Home Buttom and Power, and i was able to enter into "Unknown Upload Mode"...just to mention it.
Anymore suggestions?
EDIT: When i try to into download mode, when the phone turns on, instead of showing the "Vibrant Samsung" screen, it shows a loading circle, and the goes to directly to the "Galaxy S CyanogenMod" screen...that only happens when i try to go into Download Mode.
I just noticed that i didn't state the purpose of going into Download Mode...i want to flash my phone back to stock to flash some ROMs, im kinda stuck in CM7 now...SOOO, if there are others way to flash others ROMs other than flashing stock....
EDIT2: I have a question: I do have a Nandroid Backup of Bionix V1.3.3, should i use that back up? Or would it mess up the phone because of the file system CM7 uses?
Buump!!!!
Sent from my SGH-T959 using XDA App
djluis48 said:
Buump!!!!
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
With all the trouble you seem to be having just buy a jigg. You may need it if you plan on flashing and have such a difficult time getting into download mode.
Sent from my SGH-T959 using XDA Premium App
Here, try this.
1. Take out EVERYTHING from your phone (SIM card, MicroSD card, Battery(make sure USB isn't plugged into your phone when you do this))
2. Plug in the USB cable
3. Hold VOL up and VOL down
4. Put the battery in.
This is the ONLY way I can get into download mode from CM7, so it may work for you (sorry if you tried this method already, I skimmed through the thread, but didn't see this posted).
what happens when you run adb with your phone connected.
do you get #
when you are in shell type "adb devices" or devices can't remeber
you should get the name and serial number of your phone
If you do your sdk is installed properly and recognizes your phone.
then try "reboot recovery"
If you have a voodoo lagfix and
if you are in red recovery on the phone
go to voodoo in recovery and the lagfix menu should come up and you will see a selection for reboot download. Select that and you should see download.
But, if your phone is recognized by adb (see above) and you cannot use the reboot download command in the shell then ... I don't know.
I would check your sdk setup and make sure the phone is recognized.
I just want to point out that I've seen this problem twice and I was able to correct using a full JTAG write to the on board NAND. I'm not saying that's the only way to fix it but in my cases it solved it both times. I spent a few hours before asking the owner if he was ok with giving it a shot and I just made a backup to revert to in case it didn't work, but it worked great. PM me if you are interested in letting me correct yours with JTAG using the same methods...
Otherwise, good luck and please post what solved the problem if you fix it!
Longcat14 said:
Here, try this.
1. Take out EVERYTHING from your phone (SIM card, MicroSD card, Battery(make sure USB isn't plugged into your phone when you do this))
2. Plug in the USB cable
3. Hold VOL up and VOL down
4. Put the battery in.
This is the ONLY way I can get into download mode from CM7, so it may work for you (sorry if you tried this method already, I skimmed through the thread, but didn't see this posted).
Click to expand...
Click to collapse
Thanks for posting this method, but i had no luck with this one...
gongshow said:
what happens when you run adb with your phone connected.
do you get #
when you are in shell type "adb devices" or devices can't remeber
you should get the name and serial number of your phone
If you do your sdk is installed properly and recognizes your phone.
then try "reboot recovery"
If you have a voodoo lagfix and
if you are in red recovery on the phone
go to voodoo in recovery and the lagfix menu should come up and you will see a selection for reboot download. Select that and you should see download.
But, if your phone is recognized by adb (see above) and you cannot use the reboot download command in the shell then ... I don't know.
I would check your sdk setup and make sure the phone is recognized.
Click to expand...
Click to collapse
I don't the red recovery, i have the orange one, so no voodoo options for me there.
And ADB its working fine, if i type "adb shell" i get the "#", if i type "reboot recovery", the phone reboots and go to recovery, but if i try "reboot download", the phone just reboots like i just said "reboot".
I guess i will have to build a jigg...i was trying to avoid that trip to the electronics store since its really far away from where i live, and i don't have a car right now. If this doesn't work, then i MIGHT give connexion2005 a shot, but i really don't like the idea of JTAGing, but i have seen some cases of JTAGing in wich the phone was succesfully brought back to life.
Ask for a replacement from t-mobile and they will give you a new one free, just mess it up or something and theyll give you a replacement.
Just download the app easy reboot on the market. Plug in usb and click download mode.
Sent from my SGH-T959 using XDA App
Im having the same problem.. I cant get into Download mode.. But I can enter recovery mode... How can I go to another rom? or stock?
Im really scared right now
Can I go to another rom just by flashing it with the recovery?
ivan0550 said:
Im having the same problem.. I cant get into Download mode.. But I can enter recovery mode... How can I go to another rom? or stock?
Im really scared right now
Can I go to another rom just by flashing it with the recovery?
Click to expand...
Click to collapse
Which ROM are you using?
all of u guys having the problem getting into download mode, are ur phones hardware locked as in meaning they cant get into dl mode by the 3 button combo?
Another option, put a 2.2 rom on your sdcard.
2. Flash a 2.2 kernel in sgs kernel flasher
3. It will reboot and then pull battery
4. Go into recovery with three button method
5. Flash a 2.2 rom
6. It probably will not boot because of the filesystem but from there you can go into download mode without jig. A lot of people have trouble getting into download mode from CM7, but once you are on a normal samsung rom it is easy.
If this does not work do the following:
Download the attached file at the end
Put it on the root of your sd card
Go into CWM and click apply sd card:update.zip
You should be in CWM 2.5.1.2
Now you need to flash a 2.2 rom
Finally, you should be able to get into download mode
Another method if all else fails
Download this 2.2 rom http://www.mediafire.com/?whl91yw8s3bf1jf This is m11, Jellette's rom, I just modded it so you can flash it from CWM 3, CM7's recovery.
Now, reboot it might or might not work, if it does not pull the battery and go to download mode with normal three button method.
IF I helped you click thanks
I am completely new to this so bear with me. I am trying to root my samsung fascinate. What are the steps i need to take to do so?
http://forum.xda-developers.com/showthread.php?t=1238070
Refer to section 5
http://bit.ly/uLiskn
Use guide by Droidstyle......nuff said
Sent from my SCH-I500 using XDA App
I have been able to do this on my wife's phone pretty easy and all I do it find a copy if CWM recovery (often called CWM all), a copy of update.zip, and the latest version if Odin. Use your factory USB cord and plug your phone into your PC. Let it install all the drivers. Once I stalled open your phone and mount the SD card so you can see it as a hard drive. Place the update.zip file on the SD card, but not in any folder. From there unhook your phone and power it down. Remove the battery and start Odin. Plug your USB part of the phone cord into the PC (don't connect it to the phone yet). Hold down the volume down button and power button while connecting the phone cord to the phone. You will see a yellow triangle and Droid on the screen. From there click the PDA button and find the CWM file you downloaded. Click start and let it do its thing. The phone will power down and you can then replace the battery and start your phone. I usually let my phone power up and then power it down again. After it is off you will then need to hold the volume up, volume down, and power button to boot into recovery. Once in Recovery you can choose the option to install update.zip. Let it do its thing and then reboot the phone. You should be good to go.
icemanwbs said:
Use guide by Droidstyle......nuff said
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Sent from my SCH-I500 using XDA App
zander78 said:
http://bit.ly/uLiskn
Click to expand...
Click to collapse
LMAO... you crack me up man.
millwood said:
I have been able to do this on my wife's phone pretty easy and all I do it find a copy if CWM recovery (often called CWM all), a copy of update.zip, and the latest version if Odin. Use your factory USB cord and plug your phone into your PC. Let it install all the drivers. Once I stalled open your phone and mount the SD card so you can see it as a hard drive. Place the update.zip file on the SD card, but not in any folder. From there unhook your phone and power it down. Remove the battery and start Odin. Plug your USB part of the phone cord into the PC (don't connect it to the phone yet). Hold down the volume down button and power button while connecting the phone cord to the phone. You will see a yellow triangle and Droid on the screen. From there click the PDA button and find the CWM file you downloaded. Click start and let it do its thing. The phone will power down and you can then replace the battery and start your phone. I usually let my phone power up and then power it down again. After it is off you will then need to hold the volume up, volume down, and power button to boot into recovery. Once in Recovery you can choose the option to install update.zip. Let it do its thing and then reboot the phone. You should be good to go.
Click to expand...
Click to collapse
Hi Guys-
I'm having a problem with my Samsung Fascinate as well. Its currently running Gingerbread 2.3.5 build EH03. I had my phone flashed to MetroPCS a couple of days ago with Talk/Text only. Now I'm trying to root my phone using Odin. I want to install CyanogenMod, because I ran it on my old HTC Hero and was satisfied with it.
The problem is that my phone will not mount as a USB Storage. I'm using a Mac, however I have Parallels running Windows XP SP3. I have installed the Samsung drivers from the Samsung website and the drivers do show up in the device manager, but it still doesn't mount as a USB storage device in Windows. On the phone I receive the notification that its USB Connected - select to copy files to/from your computer. But, again nothing happens when I select it.
Whenever I plug my phone in the USB port Odin recognizes it, but when I put the phone into download mode it doesn't show up in Odin. I've also tried to see if it shows up using ADB from the Android SDK. Its not listed as a device when I run the command adb devices.
Is there anyway to root the phone if its not showing up in Odin when its download mode?
stevebanks said:
Hi Guys-
I'm having a problem with my Samsung Fascinate as well. Its currently running Gingerbread 2.3.5 build EH03. I had my phone flashed to MetroPCS a couple of days ago with Talk/Text only. Now I'm trying to root my phone using Odin. I want to install CyanogenMod, because I ran it on my old HTC Hero and was satisfied with it.
The problem is that my phone will not mount as a USB Storage. I'm using a Mac, however I have Parallels running Windows XP SP3. I have installed the Samsung drivers from the Samsung website and the drivers do show up in the device manager, but it still doesn't mount as a USB storage device in Windows. On the phone I receive the notification that its USB Connected - select to copy files to/from your computer. But, again nothing happens when I select it.
Whenever I plug my phone in the USB port Odin recognizes it, but when I put the phone into download mode it doesn't show up in Odin. I've also tried to see if it shows up using ADB from the Android SDK. Its not listed as a device when I run the command adb devices.
Is there anyway to root the phone if its not showing up in Odin when its download mode?
Click to expand...
Click to collapse
no...you need odin to flash cwm recovery so you can three finger into that recovery to flash the superuser.zip
Try another Pc!
stevebanks said:
Hi Guys-
I'm having a problem with my Samsung Fascinate as well. Its currently running Gingerbread 2.3.5 build EH03. I had my phone flashed to MetroPCS a couple of days ago with Talk/Text only. Now I'm trying to root my phone using Odin. I want to install CyanogenMod, because I ran it on my old HTC Hero and was satisfied with it.
The problem is that my phone will not mount as a USB Storage. I'm using a Mac, however I have Parallels running Windows XP SP3. I have installed the Samsung drivers from the Samsung website and the drivers do show up in the device manager, but it still doesn't mount as a USB storage device in Windows. On the phone I receive the notification that its USB Connected - select to copy files to/from your computer. But, again nothing happens when I select it.
Whenever I plug my phone in the USB port Odin recognizes it, but when I put the phone into download mode it doesn't show up in Odin. I've also tried to see if it shows up using ADB from the Android SDK. Its not listed as a device when I run the command adb devices.
Is there anyway to root the phone if its not showing up in Odin when its download mode?
Click to expand...
Click to collapse
I think you can root the phone without having to flash CWM recovery, but it does require ADB so I don't know if that would be any help. FWIW, I have a mac too, and haven't had any luck using heimdall (it doesn't recognize the device), although I haven't tried any sort of VM or anything like crossover to use odin on it. I've just accepted using a windows machine when odin is required
Does your ADB work with other devices? For whatever reason, I couldn't get it working with the fascinate, then I tried it a few days ago and it worked all of a sudden. Another workaround is to use the wirelessADB app from the market. If you search for "galaxy s mac" you'll see that you're unfortunately definitely not alone in having connectivity issues with OSX.
k_nivesout said:
I think you can root the phone without having to flash CWM recovery, but it does require ADB so I don't know if that would be any help. FWIW, I have a mac too, and haven't had any luck using heimdall (it doesn't recognize the device), although I haven't tried any sort of VM or anything like crossover to use odin on it. I've just accepted using a windows machine when odin is required
Does your ADB work with other devices? For whatever reason, I couldn't get it working with the fascinate, then I tried it a few days ago and it worked all of a sudden. Another workaround is to use the wirelessADB app from the market. If you search for "galaxy s mac" you'll see that you're unfortunately definitely not alone in having connectivity issues with OSX.
Click to expand...
Click to collapse
very true...ADB is another option to root, but I never recomend it because most folks will have trouble using it....dont mean the in a condescending way, just sayin.
For sure, just thought I would throw it out there. Looks fairly simple actually from the guide nitsuj17 posted in the OP of the EH03 odin/heimdall package, well maybe straightforward would be a better word, just since it's laid out step-by-step.
I actually had problems using cwm... it failed to flash the su.zip properly. So I used the latest version of GeeWiz recovery on stock EH03. Worked fine. Roots every time. #hopethathelps
Sent from my SCH-I500 using xda premium
There is a thread with a stock root with voodoo lag fix and ROM manager. Step by step instructions as well.
Sent from my SGH-T959P using xda premium
cant install roms
Hi, guys new to rooting and custom roms but ive hit a snag.
I have acheived root by using section 5 here (http://forum.xda-developers.com/showthread.php?t=1238070)
but i cannot install any roms all i get when i select the zip file is a screen that shows the unpacking then it goes to a triangle with an exclamation point. then reboots into normal android loosing everything i had installed. i made a backup using rom manager but it has dissapeared so now i have nothing to lose. can anyoone help.
all i want to be able to do is put ics with very few apps and overclock my cpu
Any help would be great
Samsung fascinate running android2.3.5 with superuser
thx
1. You don't need to be root first before flashing roms.
2. It sounds like you're possibly booting into the stock recovery.
If you want to flash ICS, just follow the steps in that section 3 of the guide you've already been using.
I tried but it failed on step 9/10
So you're saying that it fails after you press start in odin (flashing the stock EH03 package)? What error are you getting and when exactly is it happening?
If you're not on any rom and just on stock EH03, I'd think you should be able to just odin the CWM recovery and install ICS from there.
not sure what the exact message was but yes after i hit start it initalized did nothing for about 3 minutes of the five and got a fail message
And you're sure you're using the correct files and selecting the right things in odin? Make sure the stock EH03 rom is in the PDA section, the atlas 2.2 file for PIT, and repartition is checked. Could possibly be a bad download too, I'd maybe try redownloading the files and trying again. Also, are you using Odin 1.3 that was linked in the guide?
Alternatively, you could just try flashing the CWM4 fixed for CM7 in odin, then three-finger into recovery and flash ICS from there.
Oh and just making sure you're getting into download mode the right way, I personally pull the battery, that way it doesn't reboot after you flash whatever it is you're flashing. If none of that works, I'd try a different USB port/cable. Is odin recognizing the device properly?
Hi everyone, I understand and accept my noob status, but I have searched high and low and can't find my answer.
My SGP has been bricked for about a month now, and I have no idea what I need to do to fix it. It's the international player with the hardware button. When I bought it, the guy who sold it said it was from Peru, and it had a custom start-up animation. I wanted to get rid of that, so I started trying to flash things before I really understood what I was doing.
I had it rooted, so that was a good first step, but it collapsed from there. I've been using Odin to try to fix things.
The player will not start up at all on its own. At one point it did, but went into a bootloop. I don't have linux and windows on the same computer, so what I do is, I plug the player into a powered usb hub, and connect it to my linux machine. I have unbrickable on there, so I run that and it gets it to the download screen, except the download screen isn't centered, it's off to the side a bit. Then I unplug the cable that runs between the hub and the laptop, and plug that into my windows machine, and try to flash with Odin.
I've been trying to put a new kernel, new rom, everything on there, but I confess I just don't know what's wrong and what I need. Odin seems to connect fine, and the green bar fills part or most of the way, and then just stops. I never get any sort of "successful" message from Odin.
So please please please help me, folks. I've tried to provide as much detail as I can, but just ask if you have any questions. I'm here to learn and thanks in advance for your help.
Did you try flashing the stock firmware through odin 1.7?
iurnait said:
Did you try flashing the stock firmware through odin 1.7?
Click to expand...
Click to collapse
Yes, several times. Odin hangs. I've tried flashing the md5.tar file both with and without the .pit file, and it always hangs.
pjd711 said:
Yes, several times. Odin hangs. I've tried flashing the md5.tar file both with and without the .pit file, and it always hangs.
Click to expand...
Click to collapse
what about rj's kernel?
That's another thing I guess I'm a little fuzzy on. Can I flash just a kernel? Do I put that in the "PDA" window in Odin? I can't remember if or how I tried that before but can give it a shot.
Sent from my HTC_Flyer_P512_NA using xda app-developers app
pjd711 said:
That's another thing I guess I'm a little fuzzy on. Can I flash just a kernel? Do I put that in the "PDA" window in Odin? I can't remember if or how I tried that before but can give it a shot.
Sent from my HTC_Flyer_P512_NA using xda app-developers app
Click to expand...
Click to collapse
Yes, you can flash just a kernel. I've done it on my USA 5.0 multiple times. Use the PDA window, as you already stated. Be sure to double check and make sure you have the correct kernel before flashing (I'm pretty sure rj's kernel is the right one).
Let us know how it goes! :fingers-crossed:
codehunter2000 said:
Yes, you can flash just a kernel. I've done it on my USA 5.0 multiple times. Use the PDA window, as you already stated. Be sure to double check and make sure you have the correct kernel before flashing (I'm pretty sure rj's kernel is the right one).
Let us know how it goes! :fingers-crossed:
Click to expand...
Click to collapse
Tried it twice, and it failed both times. Is it a concern that the Download Mode screen isn't centered?
pjd711 said:
Tried it twice, and it failed both times. Is it a concern that the Download Mode screen isn't centered?
Click to expand...
Click to collapse
This is going to sound silly, but have you tried re-installing the drivers on your computer for your Player? I had a similar issue with my Nexus 7 once (I believe I was flashing back to stock). Something wonky had happened laptop-side, and I had to re-install the driver before it would even recognized that I had connected my N7. Be sure to connect directly; don't use a hub. Also, are you using a USB 3.0 port, or a 2.0 port? I've read that that can cause issues too.....
Hope that helps. Let us know if it doesn't. Don't give up the fight!
try odin 1.85. i tried this just now (had a bootloop) and got stock firmware flashed. also make sure u are using the samsung cable.
also, can you get into recovery?
Yes, I have reinstalled drivers. I'm using a USB 2.0 port. Just downloaded Odin 1.85 and will try with that.
I never got a Samsung cable b/c I bought the thing used. I've been using the powered hub b/c I don't have linux and windows on the same computer. The unit is completely unresponsive normally; I can get it to download mode with Unbrickable (which, from what I've read, only works on linux). So once I do that, then I unplug the linux computer and plug to the windows computer for Odin (which, from what I've read, only works on windows).
I have Heimdall on my linux computer, but read that it doesn't work on Galaxy Players. So unless there's some way to do everything on only linux or only windows, I have to have the powered hub to keep the Download Mode screen on. The linux machine is an old netbook and is too weak to run Wine BTW.
Is there anything I'm missing or incorrect? Because the alternative is to install linux on my windows machine, which I just upgraded to 8, and I don't even like/know how to use that very much.
pjd711 said:
Yes, I have reinstalled drivers. I'm using a USB 2.0 port. Just downloaded Odin 1.85 and will try with that.
I never got a Samsung cable b/c I bought the thing used. I've been using the powered hub b/c I don't have linux and windows on the same computer. The unit is completely unresponsive normally; I can get it to download mode with Unbrickable (which, from what I've read, only works on linux). So once I do that, then I unplug the linux computer and plug to the windows computer for Odin (which, from what I've read, only works on windows).
I have Heimdall on my linux computer, but read that it doesn't work on Galaxy Players. So unless there's some way to do everything on only linux or only windows, I have to have the powered hub to keep the Download Mode screen on. The linux machine is an old netbook and is too weak to run Wine BTW.
Is there anything I'm missing or incorrect? Because the alternative is to install linux on my windows machine, which I just upgraded to 8, and I don't even like/know how to use that very much.
Click to expand...
Click to collapse
On your windows 8 machine, does ADB recognize your device when it's plugged in? (Command Prompt, type: adb devices)
Also, can you get your device into recovery mode (not download mode)? Do you have CWM installed/flashed?
codehunter2000 said:
On your windows 8 machine, does ADB recognize your device when it's plugged in? (Command Prompt, type: adb devices)
Also, can you get your device into recovery mode (not download mode)? Do you have CWM installed/flashed?
Click to expand...
Click to collapse
adb wasn't a recognized command by windows. The computer sees the device in Control Panel, but it sees it as "SEC 5Spc110 Test B/D" and won't let me attach a driver to it. I point it at the folder where the drivers are, and windows says it can't find the drivers.
Enraging.
Edit: I'm not certain but I don't think I got CWM to work before all this went on. I cannot get to recovery mode.
pjd711 said:
adb wasn't a recognized command by windows. The computer sees the device in Control Panel, but it sees it as "SEC 5Spc110 Test B/D" and won't let me attach a driver to it. I point it at the folder where the drivers are, and windows says it can't find the drivers.
Enraging.
Edit: I'm not certain but I don't think I got CWM to work before all this went on. I cannot get to recovery mode.
Click to expand...
Click to collapse
To get adb working in command prompt, use these instructions here: http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
If you shutdown your Player, can you boot into recovery? There's a button combo you are supposed to use (Power, volume up, home button I think), but I have no idea what the combo is. At school, so I can't look it up.
pjd711 said:
Yes, I have reinstalled drivers. I'm using a USB 2.0 port. Just downloaded Odin 1.85 and will try with that.
I never got a Samsung cable b/c I bought the thing used. I've been using the powered hub b/c I don't have linux and windows on the same computer. The unit is completely unresponsive normally; I can get it to download mode with Unbrickable (which, from what I've read, only works on linux). So once I do that, then I unplug the linux computer and plug to the windows computer for Odin (which, from what I've read, only works on windows).
I have Heimdall on my linux computer, but read that it doesn't work on Galaxy Players. So unless there's some way to do everything on only linux or only windows, I have to have the powered hub to keep the Download Mode screen on. The linux machine is an old netbook and is too weak to run Wine BTW.
Is there anything I'm missing or incorrect? Because the alternative is to install linux on my windows machine, which I just upgraded to 8, and I don't even like/know how to use that very much.
Click to expand...
Click to collapse
Heimdall does on fact work quite well on the galaxy player 5. If you're keen to use the command line, extract the kernel from any zip or tar and do a 'heimdall flash --kernel /path/to/kernel'. If that works, I can give you further instructions on fixing your bootloaders.
And being offset does not affect download mode functionality.
codehunter2000 said:
To get adb working in command prompt, use these instructions here: http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
If you shutdown your Player, can you boot into recovery? There's a button combo you are supposed to use (Power, volume up, home button I think), but I have no idea what the combo is. At school, so I can't look it up.
Click to expand...
Click to collapse
If the resurrector detects it, it has broken bootloaders, so no recovery.
Sent from my Galaxy Nexus
Mevordel said:
Heimdall does on fact work quite well on the galaxy player 5. If you're keen to use the command line, extract the kernel from any zip or tar and do a 'heimdall flash --kernel /path/to/kernel'. If that works, I can give you further instructions on fixing your bootloaders.
And being offset does not affect download mode functionality.
If the resurrector detects it, it has broken bootloaders, so no recovery.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Ok, got out my netbook and took at stab at it with Heimdall. I'm a little fuzzy with how to use it, but tried flashing with a stock package that I had, which included a kernel. I got an error message that it failed to send end session packet, and on the bottom it says "Failed to confirm end of file transfer sequence".
So, what specific files should I be putting where? On the first tab, I can load a firmware package, and that fills in the PIT section on the "Flash" tab in Heimdall. Is that correct? Does it matter what type of file I select for the Heimdall Firmware Package?
On the "Flash" tab, should I have the "Repartition" and "No Reboot" boxes picked?
Anything I'm doing wrong or can change to get this end session packet problem solved?
Thanks everyone for all the help so far!
pjd711 said:
Ok, got out my netbook and took at stab at it with Heimdall. I'm a little fuzzy with how to use it, but tried flashing with a stock package that I had, which included a kernel. I got an error message that it failed to send end session packet, and on the bottom it says "Failed to confirm end of file transfer sequence".
So, what specific files should I be putting where? On the first tab, I can load a firmware package, and that fills in the PIT section on the "Flash" tab in Heimdall. Is that correct? Does it matter what type of file I select for the Heimdall Firmware Package?
On the "Flash" tab, should I have the "Repartition" and "No Reboot" boxes picked?
Anything I'm doing wrong or can change to get this end session packet problem solved?
Thanks everyone for all the help so far!
Click to expand...
Click to collapse
Download the bootloader tar from the hard brick recovery thread, and the appropriate PIT file. Then flash the tar, and check repartition and use the downloaded PIT. If that works, you should be able to get to download mode normally.
The titel says it all , and I need some help. I can still go in recovery but adb won't recongize my HTC, but I can still find it in fastboot. I formatted the sdcard, so I have nothing on there. Help would be much appreciated.
vsp33ddyv said:
The titel says it all , and I need some help. I can still go in recovery but adb won't recongize my HTC, but I can still find it in fastboot. I formatted the sdcard, so I have nothing on there. Help would be much appreciated.
Click to expand...
Click to collapse
Oh, trust me that's not your phone being bricked. You guys seriously need to know the correct vocabulary.
Bricking the phone: The phone's only use is to use it as a literal brick. It does not turn on, does not recover, does not charge, does not do anything and it can never be restored.
HOX+ can NOT be bricked unless you are S-Off'ed. Now that we got that out of the way,
you seem to understand that ADB is the solution here, that you need to sideload a rom, the question that you have is the adb does not recognize your phone, so follow these steps:
-Connect the phone using a different usb port, (basically thats the easiest thing), if its 2.0 then try 3.0 and vice versa.
-Restart your computer
-Restart your phone
-If you are on windows Vista and later, open start menu search for "cmd" then right click and run it as administrator, then you need to cd to your adb directory.
Code:
cd C:\Android\sdk\platform-tools
for example. then try adb devices.
Anyway hope you get it to work and have fun
Ghand0ur said:
Oh, trust me that's not your phone being bricked. You guys seriously need to know the correct vocabulary.
Bricking the phone: The phone's only use is to use it as a literal brick. It does not turn on, does not recover, does not charge, does not do anything and it can never be restored.
HOX+ can NOT be bricked unless you are S-Off'ed. Now that we got that out of the way,
you seem to understand that ADB is the solution here, that you need to sideload a rom, the question that you have is the adb does not recognize your phone, so follow these steps:
-Connect the phone using a different usb port, (basically thats the easiest thing), if its 2.0 then try 3.0 and vice versa.
-Restart your computer
-Restart your phone
-If you are on windows Vista and later, open start menu search for "cmd" then right click and run it as administrator, then you need to cd to your adb directory.
Code:
cd C:\Android\sdk\platform-tools
for example. then try adb devices.
Anyway hope you get it to work and have fun
Click to expand...
Click to collapse
The only thing I can do is use fastboot , thx for noticing that I know I need adb sideload If I look in devices on my PC I can see 'ONE' with a yellow triangle next to it ( so this means drivers) I downloaded my HTC drivers and I right clicked on the device and then update from PC , I go to the folder where I installed it and click on search and it says it can't find a driver for this device.
I also tried 4 different USB ports both 2.0 or 3.0 , no result. I also tried to install TWRP instead of cmw but on TWRP my touchscreen doesn't work while on cmw it does. So i went back and flashed my recovery to cmw again ( I tried version 2.6 - 2.7.0.1 , no result )
So my problem right now can be solved once my device can be recognized by my PC. (Have HTC maneger installed , also downloaded drivers formy phone , got fastboot and adb on my PC )
For anyone who knows thanks
vsp33ddyv said:
The only thing I can do is use fastboot , thx for noticing that I know I need adb sideload If I look in devices on my PC I can see 'ONE' with a yellow triangle next to it ( so this means drivers) I downloaded my HTC drivers and I right clicked on the device and then update from PC , I go to the folder where I installed it and click on search and it says it can't find a driver for this device.
I also tried 4 different USB ports both 2.0 or 3.0 , no result. I also tried to install TWRP instead of cmw but on TWRP my touchscreen doesn't work while on cmw it does. So i went back and flashed my recovery to cmw again ( I tried version 2.6 - 2.7.0.1 , no result )
So my problem right now can be solved once my device can be recognized by my PC. (Have HTC maneger installed , also downloaded drivers formy phone , got fastboot and adb on my PC )
For anyone who knows thanks
Click to expand...
Click to collapse
Hmmm. I would say in the device manager right click on the one and uninstall. Then in fastboot mode unplug and replug the device, let it install fastboot again and then try if adb can read it now.
Ghand0ur said:
Hmmm. I would say in the device manager right click on the one and uninstall. Then in fastboot mode unplug and replug the device, let it install fastboot again and then try if adb can read it now.
Click to expand...
Click to collapse
Still can't read it...
This has happened to my phone twice... fixed it the first time by using USB deview to remove all Android/HTC drivers, then reinstalled them with the HTC Sync installer. Couldn't get that to fix it last time though, so I tried another computer and it worked just fine. So my advice would be to find another computer and try it.
911jason said:
This has happened to my phone twice... fixed it the first time by using USB deview to remove all Android/HTC drivers, then reinstalled them with the HTC Sync installer. Couldn't get that to fix it last time though, so I tried another computer and it worked just fine. So my advice would be to find another computer and try it.
Click to expand...
Click to collapse
YES THIS IS WHAT WORKED ONLY I DID SOME OTHER STEPS TOO!!! Now I got adb running again and I can only push , I'll explain later in a full tutorial how to fix this now you guys can help me , I'm trying to download a cyanmod for my HTC because the stock is german and I can't download it , so can anyone upload the cyanmod endeavouru for me I keep getting error 502 bad gateway I almost fixed it !!!!! I need it badly !
OOkay so I thought I had figured it out , I uste TWRP to push files from PC to my Phone , then I installed cmw and tried to install the ROMS , but apperantly my roms were deleted. (I can't use TWRP because I need touch and the touch doesn't work , while in cmw the touch does work)
So if we can fix the TWRP touch I will know how to fix my problem !
I fixed the problem
I fixed the problem , thread how comming soon !
Here is my thread http://forum.xda-developers.com/showthread.php?p=52550145
I currently have a rooted Note 8 running Android 7.1.1 Nougat, running build NMF26X.N950USQ2BQL5. I am trying to update it to Oreo. I have installed Odin v3.13.1, v3.12+ (PrinceComsy), and v3.12.3 with no success. I have extracted the firmware from SamFirm and downloaded from a third-party source and nothing.
My issue is when I run Odin, either I get stuck on Setup Connection or beforehand. I have never gotten past this point. Device status currently says Custom. I have looked throughout this forum for some answers but couldn't find any. I apologize if this has been answered. Please direct me to the thread if this answer has been answered. Thank you. I have spent far too long working on this and it is really annoying.
Not even related to the root.
Stuck at setup connection means theres a connection problem between the phone and computer. try a different usb port, usb cable, reboot comp and phone and try a different comp(this is the order of trying things)
me2151 said:
Not even related to the root.
Stuck at setup connection means theres a connection problem between the phone and computer. try a different usb port, usb cable, reboot comp and phone and try a different comp(this is the order of trying things)
Click to expand...
Click to collapse
So far none of these methods work. I tried each method stated.
afjohn483 said:
So far none of these methods work. I tried each method stated.
Click to expand...
Click to collapse
You have installed the drivers?
stonedpsycho said:
You have installed the drivers?
Click to expand...
Click to collapse
I have, twice actually. I can't find the link to one I download, but I know it was the same as I previously download.
Here are the steps I have taken as I tried again today after the first response:
1. Run Odin as Administrator ( I tried the newest version today, v3.13.1)
2. Add each file to the corresponding location (AP to AP, BL to BL, etc.) using the latest firmware extracted from SamFail which I believe to be Oreo update from T-mobile)
3. Manually enter Download mode using Volume Down + Power button + Bixby button
4. Press Volume-up to enter Download mode
5. Connect via USB, to the computer using the USB ports apart of the motherboard itself
6. Click Start
7. After 2-3 minutes, failed. And that happens at least ten times in the last two days. No matter if I switch USB ports, change cables, restart the computer, restart the Note 8.
You didnt mention changing the computer...
Is a red message on the phone displayed after Odin fails? What does it say?
me2151 said:
You didnt mention changing the computer...
Click to expand...
Click to collapse
That is the only thing I haven't tried yet.
then that will fix it
stonedpsycho said:
Is a red message on the phone displayed after Odin fails? What does it say?
Click to expand...
Click to collapse
See the attachment. That what I have seen every time I tried to run it
Use a different computer...
me2151 said:
Use a different computer...
Click to expand...
Click to collapse
So I switch to a new computer and the same error. I follow another guide which stated I need to first update to N950USQS2BQK2 then ADB Sideload. I tried updating, but Odin didn't see the files. Only when I first extract them, it would briefly see it then go away completely. I realize I was already on that update and tried to sideload, got an error twice when it first started to unpack the file. I tried to use Odin to the latest update for the Note 8, same error. I genuinely don't know what to do anymore.
first check with adb command to see if device is showing connected and recognized , then use adb command to reboot to download mode,
adb reboot download
after that odin shall work . it worked in my case ..