Related
Hi there,
I tried a number of ways to change the ROM on my phone from the stock to an upgraded or custom ROM. Using Odin I was always able to at least get the stock ROM back up and running.
This time I tried ClockWorkMod and something has gone wrong. I cannot turn the phone on, boot into recovery mode, or download mode and the phone is completely unresponsive. Nothing appears on the screen.
I've tried re-flashing the stock ROM through Odin and it will recognize that the phone is there and connected via USB however when I try to flash the stock ROM back onto it the program hangs at:
<1> Setup connection...
I'm running from Administrator on Windows 7, I don't have Kies installed, I have the most up to date Samsung USB drivers.
I really want to at least get the phone into download mode to flash the stock ROM back on... is really hope there is a way to do this.
Twisted_Daemon said:
This time I tried ClockWorkMod and something has gone wrong. I cannot turn the phone on, boot into recovery mode, or download mode and the phone is completely unresponsive. Nothing appears on the screen.
I've tried re-flashing the stock ROM through Odin and it will recognize that the phone is there and connected via USB however when I try to flash the stock ROM back onto it the program hangs at:
<1> Setup connection...
Click to expand...
Click to collapse
just curious... how you try re-flashing through odin, while the phone can not boot in download mode?
when you charge the phone, does it show the battery indication?
I get no battery charge indicator while the phone is plugged in via usb...
However Odin does recognize that I have the phone plugged in. I hoped that this would be enough to send a flash to it through Odin but it gets stuck at '<1> Setup Connection'
I'm currently installing Android SDK. If the computer knows it's there maybe I can send a command to make it reboot into download mode?
you need to have kies to let odin work
Sent from my GT-S5830 using xda premium
Ok re-installed Kies and gave it a go.
While Kies was open I got:
<1> --- cannot open the usb serial port. code: 5
I'm assuming because Kies was trying to do something with it at the same time.
While Kies is not open I get:
<1> setup connection... (<Hangs here like before)
Installed android SDK.
Tried running: adb reboot download
Response was: error: device not found
Both Kies and Odin know that something is there, but the SDK doesn't seem like it knows it's there and doesn't look like it can send commands to it
Twisted_Daemon said:
Installed android SDK.
Tried running: adb reboot download
Response was: error: device not found
Both Kies and Odin know that something is there, but the SDK doesn't seem like it knows it's there and doesn't look like it can send commands to it
Click to expand...
Click to collapse
first you needed to type adb devices
Sent from my GT-S5830 using xda premium
adb devices just brings up an empty list...
It says 'List of devices attached' and then nothing
I just really want to get it into download mode again, Odin and Kies know it's there to an extent but can't really do anything with it just yet...
Hiya!
Have exact same problem with my Ace...totally black but Odin find it. Then i stuck with that annoying "setup connection"
I connect my phone(or brick!!) with usb-cable, have no battery in it. Then i press vol down+home+power buttons and I think its in download mode. It´s just that I can´t see it becouse the screen is black.
[email protected] said:
Hiya!
Have exact same problem with my Ace...totally black but Odin find it. Then i stuck with that annoying "setup connection"
I connect my phone(or brick!!) with usb-cable, have no battery in it. Then i press vol down+home+power buttons and I think its in download mode. It´s just that I can´t see it becouse the screen is black.
Click to expand...
Click to collapse
Run
Code:
adb devices
And that will tell you if it is actually in download mode... it should list the device then the mode it is in on the right..
Most of the phones that couldnt boot into download mode were diagnosed as bricked, from what ive seen here in XDA, the SGA community.
However, you could spend a small penny on 3 100ohms resistors to create a USB jig as a last resort.
Try this :
-Put out battery
-Plug the usb cable pc - ace
-Make manipulation for download mod : home + power + sound - and plug battery in the same time
-Device go to download mod
Flash trought odin =)
Peanuts
Sorry for my ugly english, i'm french what ! ^^'
Whippopotamus said:
Run
Code:
adb devices
And that will tell you if it is actually in download mode... it should list the device then the mode it is in on the right..
Click to expand...
Click to collapse
Do you mean Tools--->manage AVDs in Android SDK?
Thanks for your help
Was it called ROM Manager on Market/Play? If so lie to service centre saying kies crashed when updating, there is nothing you can do. Sorry :/
[email protected] said:
Do you mean Tools--->manage AVDs in Android SDK?
Thanks for your help
Click to expand...
Click to collapse
no
cmd
type adb devices and a menu with
some text will apear
unwritten sentance
Or try tu use unbrick plug, which is nothing more than normal usb plug witch resistor 300K or set of resistors equal to 303K(it is more preciouse) shorted to 4 and 5 pin.
Are youll guys serious?? look at the date please ---feb 08 that guy hss probably fixed or thrown his phone out....who are youll talking to???
You know you are rooted when you use XDA more than FB
i think you have permanently bricked your ace, take it back to the store and say odin crashed while you were flashing gingerbread 2.3.7
Now I tried everything except the USB jig. I try to make one in next weekend. Else I must tanke it to the Samsung store and say something smart I let u guys know how it goes. Thanks for all help this far:thumbup:
Sent from my GT-I9100 using XDA
Uh hi.
I'm a herp.
So I may have accidently tried to root and flash my friend's Samsung Vibrant. It was going smoohtly but now, I'm all sorts of messed up.
The problem: I may have used the wrong kernel (zImage) when using heimdall-frontend (which I downloaded from xda). This is causing the phone to power on; it shows the Samsung Galaxy S 4g load screen, then Overstock, then the T-Mo logo sign (with the music), and then a longer Galaxy S load screen. After the load screen, the screen goes completely black, but all the touch buttons light up. Once like this, I can turn it off, and make it go back into recovery mode and also download mode.
Please help. I've been trying to solve this with my friend for about.. 4 hours.
P.S. I've looked up all the guides for using ODIN to get back to JFS, none works due to the reason that when I put it back into download mode, the computer does not recognize it. But it does at the same time. (it shows the "safetly remove hardware" and says that is an "USB mass storage device" ((but does not appear in "My Computer" when in the unresponsive screen-- but when in the download screen, it shows the same thing, only labeled "SAMSUNG USB Composite Device", which also cannot be accessed through "My Computer")
P.P.S. I'm sure it is a Samsung Galaxy S Vibrant, exclusive from T-Mobile. My computer is Windows Vista 32-bit, and I have as many Samsung drivers as humanly possible when it comes to the Vibrant.
Can anyone help a poor fool?
Try this, get in to download mode, open Odin, then disconnect the usb cable, then reconnect the usb cable and Odin should recognize it then. Good luck!
Using XDA premium, you should be too!
johnny12times said:
Try this, get in to download mode, open Odin, then disconnect the usb cable, then reconnect the usb cable and Odin should recognize it then. Good luck!
Using XDA premium, you should be too!
Click to expand...
Click to collapse
Sorry. That did not work. It just doesn't recognize it in ODIN when in download mode. My computer doesn't even see it. But it does say "Safely Remove Hardware" -- "SAMSUNG USB Composite Device"
Sounds really odd. Do you have any roms you can try reflashing from recovery?
Using XDA premium, you should be too!
depaer said:
Uh hi.
I'm a herp.
So I may have accidently tried to root and flash my friend's Samsung Vibrant. It was going smoohtly but now, I'm all sorts of messed up.
The problem: I may have used the wrong kernel (zImage) when using heimdall-frontend (which I downloaded from xda). This is causing the phone to power on; it shows the Samsung Galaxy S 4g load screen, then Overstock, then the T-Mo logo sign (with the music), and then a longer Galaxy S load screen. After the load screen, the screen goes completely black, but all the touch buttons light up. Once like this, I can turn it off, and make it go back into recovery mode and also download mode.
Please help. I've been trying to solve this with my friend for about.. 4 hours.
P.S. I've looked up all the guides for using ODIN to get back to JFS, none works due to the reason that when I put it back into download mode, the computer does not recognize it. But it does at the same time. (it shows the "safetly remove hardware" and says that is an "USB mass storage device" ((but does not appear in "My Computer" when in the unresponsive screen-- but when in the download screen, it shows the same thing, only labeled "SAMSUNG USB Composite Device", which also cannot be accessed through "My Computer")
P.P.S. I'm sure it is a Samsung Galaxy S Vibrant, exclusive from T-Mobile. My computer is Windows Vista 32-bit, and I have as many Samsung drivers as humanly possible when it comes to the Vibrant.
Can anyone help a poor fool?
Click to expand...
Click to collapse
Sounds like you used the wrong odin files. if your screen is showing a galaxy s 4g logo then you must have mistakenly flashed a galaxy s 4g odin/heimdall package. on the back of your phone what is the model number. What on earth is JFS? ive heard of JFD which is the stock firmware that the phone shipped with.
If you flashed the wrong bootloader you are more or less stuck between a rock and a hardplace and will require a jtag. now the fact that teh screen does turn on is a good thing.
You need to keep trying to get it into download mode maybe try using a jig. Once youve gotten it into download mode try every single usb port you can find on your pc. When i need to odin i need to use one of my usb ports on the rear io panel none of the others will work. Once you get odin running and recognizing your device use the files posted in my sig as the odin files. any others and i cant help you cuz i dont know what your source is. Odin should be able to recover your device if it is still booting to the splash screen.
If for whatever reason you cant boot into download mode but can get into recovery here is what you do: make sure you have the android SDK installed (dont know what that is go here: http://developer.android.com/sdk/index.html and follow their directions) then open up command prompt while in recovery type the following command: adb reboot bootloader this should put you into download mode. If nothing ive mentioned works you may require a JTAG there is a company called MOBILETECHVIDEOS (http://mobiletechvideos.mybigcommerce.com/) that has a JTAG service.
Good luck
-Cheers
Ok so i think i bricked my phone but not completely happened when i flashed CWM Touch but must of not of been the version for the note. I can boot it up goes to Samsung logo but then all black this happened when i went to my Rom and rebooted it to recovery to see the CWM touch worked so no its just staying on the logo and I cant reboot it to Recovery mode anymore I can however boot to download mode some freinds over at BlackStar Rom Thread helped out how to fix it I just cant get my darn PC to install the drivers even if i Downloaded them on the Samsung Website and still says Unknown Device...
Any help will be appreciated ...I am very unhappy without my note lol...but yea i am
I would uninstall any Samsung Driver you have and then download fresh just the driver here: http://d-h.st/jfx then reinstall them and reboot you pc after uninstall and reinstalling.
And if you are running BStar, bigfau doesn't mind if you post your questions or issues in his thread, he and the folks there are very helpful and like keeps all in the thread.
Just a side note....
Okay will ask in the thread then thanks also tried what you said and uninstalled kies still get unknow device
So you have no Com connection in download mode while using Odin ?
If you have download mode, then Odin should work .....as the drivers on the device side are still working..
Or are you seeing the download " limp" mode ???
With the pictures of a computer and phone on your phone screen ????
If so ...go to the " note super everything thread " and scroll down to the post ...." Odin tips for better success "....
It explains a bit more ....
Good luck ......g
yes i just get a error 43 says windows has stopped device when i try to load the drivers it does nothing says has the most best driver for the phone i get into download mode shows the pic of android and says on top odin mode and my phones model number other than that it wont read to my pc so i can get the install going via odin or kies i currently have kies uninstalled did as Bigjoe said and uninstalled drivers and reinstalled all with always rebooting my pc
still no sucess thinking of buying some usb to micro cords and see if that will help my pc still says unknown device even after uninstalling and reinstalling the drivers
Hello All,
I've been reading posts from here for a long time but this is my first post.
I'm coming here as a last resort to save my Galaxy s2 (SGH-T989) which has a stock ROM.
Here's what happened.
I dropped my phone and then it got stuck in bootloop (it only boots until I see the "SAMSUNG" word animation and stops there).
At that point, ODIN 'sees' that there's a connected device; KIES keeps "connecting...." but can't actually connect; ADB does not show any connected device.
So, what I wanted to do was to factory "reset" the phone. The problem is I can't get the phone into Recovery mode. I believe it's because my volume down button was acting up when the phone was working. However, I can get to "Download Mode" using a USB Jig.
So, the next thing to do is to flash a new stock ROM. However, whenever I connect my phone when it's in "Download Mode", ODIN does not see it.
Yes, I've installed, re-installed, removed, re-installed all drivers and Kies and I've done that so many times you can't even believe it.
The problem is that the device driver "SAMSUNG Mobile USB CDC Composite Device" gives the following error "This device cannot start. (Code 10)", and I don't know why or how I can get rid of that. As mentioned above, I've tried all the device driver installation fixes but none has worked.
I mean, when the phone is not in Download Mode and I connect it to my PC, all device drivers are working fine with no error, but when it's in Download Mode, I get the error mentioned above "This Device cannot start.".
So, my questions:
1) Is there a way to get to Recovery Mode without using the button combinations? (The phone is in bootloop)
2) How can I fix the device driver error mentioned above to get ODIN to see my device?
3) Is there anything else I need to be doing?
This problem is really frustrating and I've been on it for more than 2 weeks and nothing has worked so far. Any help is greatly appreciated.
1. I think you have flashed an bad kernel if you cant get into recovery mode and i dont get it why your volume down acts like up?.
2. http://support.microsoft.com/kb/943104 try to maybe also disable kies and try again.
3. Kies is on, adb doesnt work at samsung/download screen, try to reinstall samsung usb drivers again :/ yes I know but to be sure, disable driver signature or something like that if you are on windows 8.x, try another usb cable.
2weeks dont sound good. I hope these tips could help a bit but I still wonder why your phone got in bootloop when you dropped it !?!? What were you doing at that time and did the battery go out?
wulsic said:
1. I think you have flashed an bad kernel if you cant get into recovery mode and i dont get it why your volume down acts like up?.
2. try to maybe also disable kies and try again.
3. Kies is on, adb doesnt work at samsung/download screen, try to reinstall samsung usb drivers again :/ yes I know but to be sure, disable driver signature or something like that if you are on windows 8.x, try another usb cable.
2weeks dont sound good. I hope these tips could help a bit but I still wonder why your phone got in bootloop when you dropped it !?!? What were you doing at that time and did the battery go out?
Click to expand...
Click to collapse
Thanks for the quick reply, wulsic.
1. No, I did not flash any kernel on this phone, everything on it is stock and was working just fine before it was dropped. I meant that the volume down was not working properly, not that it was acting like up.
2. I tried that but did not work
3. The drivers are working fine when the phone is not in Download Mode, it's only when it's in Download Mode that I get the error and I've tried re-installing drivers and everything, I think the problem is with the device itself not a driver problem.
This latest tool also allows you to boot your Samsung Smartphone and tablets into the download mode without pressing the physical keys. If in case your Samsung device physical keys are not working, then this latest Samsung tool is useful for all of you. The best thing about this tool is that it is not necessary to have the USB debugging active. The tool only detects your device and restarts it in download mode to do the flashing by ODIN.
How to use Samsung 300K Tool
This latest tool is useful for those users who have Samsung devices that do not enter download mode with the failure of keys.
After download file is complete simply Run for install.
Make sure that the Samsung drivers are installed
Before connecting the device open the program and the following screen instructions.
Now connect your device to the computer and make sure that the cable is properly or correctly connected, and the screen will change.
In this last step click on the figure of the image where the strain point and your cell phone connected or not enter the download mode quickly in 2 seconds, but I recommend doing the operation with the phone is connected.
Done.
Admin Edit: Attachment has been removed as it was flagged by Google as "uncommon download". Also locking thread.
speechless said:
This latest tool also allows you to boot your Samsung Smartphone and tablets into the download mode without pressing the physical keys. If in case your Samsung device physical keys are not working, then this latest Samsung tool is useful for all of you. The best thing about this tool is that it is not necessary to have the USB debugging active. The tool only detects your device and restarts it in download mode to do the flashing by ODIN.
How to use Samsung 300K Tool
This latest tool is useful for those users who have Samsung devices that do not enter download mode with the failure of keys.
After download file is complete simply Run for install.
Make sure that the Samsung drivers are installed
Before connecting the device open the program and the following screen instructions.
Now connect your device to the computer and make sure that the cable is properly or correctly connected, and the screen will change.
In this last step click on the figure of the image where the strain point and your cell phone connected or not enter the download mode quickly in 2 seconds, but I recommend doing the operation with the phone is connected.
Done.
Click to expand...
Click to collapse
The attached Samsung 300k file gives a CRC error when extracted. also its an exe and doesnt run on Windows 10. Is there an equivalent file that will allow my samsung galaxy T4 (sm-231 v4.4.2 Kitkat) to enter download mode? Its home key is not working right now. Using ADB i am able to enter Manual mode, but not Download mode! So ODIN does not recognize it ( ID:COM is not highlighted). I have installed the latest Samsung USB drivers.
any help will be most appreciated.
sifar786 said:
The attached Samsung 300k file gives a CRC error when extracted. also its an exe and doesnt run on Windows 10. Is there an equivalent file that will allow my samsung galaxy T4 (sm-231 v4.4.2 Kitkat) to enter download mode? Its home key is not working right now. Using ADB i am able to enter Manual mode, but not Download mode! So ODIN does not recognize it ( ID:COM is not highlighted). I have installed the latest Samsung USB drivers.
any help will be most appreciated.
Click to expand...
Click to collapse
When the phone is booted up normally and the way you would normally use it, when you connect your phone and open ODIN, does it still not pick up the phone on the COM port?
And (I'm sure you do), do you have USB debugging turned on and all the other usual things (like you mentioned, having installed the latest drivers)?
Samsung galaxy tab 4 (sm-t231) kitkat v4.4.2
Max_Terrible said:
When the phone is booted up normally and the way you would normally use it, when you connect your phone and open ODIN, does it still not pick up the phone on the COM port?
And (I'm sure you do), do you have USB debugging turned on and all the other usual things (like you mentioned, having installed the latest drivers)?
Click to expand...
Click to collapse
yes, i finally used "adb reboot download" to boot into download mode. Now when i am using ODIN and trying to root my cell by installing TWRP 3.2.1-0-degas.img.tar, it says PASS (success 1/fail 0), but my mobile still shows "DOWNLOADING..." with a horizontal blue line. I can also reboot and load normally, but it seems TWRP has not got installed and still ROOTCHECKER says my mobile is not rooted. Am i using the wrong versions of TWRP recovery or ODIN etc? Can you advice next steps?
sifar786 said:
yes, i finally used "adb reboot download" to boot into download mode. Now when i am using ODIN and trying to root my cell by installing TWRP 3.2.1-0-degas.img.tar, it says PASS (success 1/fail 0), but my mobile still shows "DOWNLOADING..." with a horizontal blue line. I can also reboot and load normally, but it seems TWRP has not got installed and still ROOTCHECKER says my mobile is not rooted. Am i using the wrong versions of TWRP recovery or ODIN etc? Can you advice next steps?
Click to expand...
Click to collapse
When you've flashed TWRP, the phone will stay in download mode. Nothing will change on screen, that is normal. You have to reboot the device manually, using the button combination it says, then immediately as the device restarts, you change the combination to boot into TWRP. All of these steps are explained in whichever thread or wherever you found TWRP.
As far as rooting is concerned; TWRP doesn't inherently root the device. It just replaces the bootloader to allow you to flash custom packages, like the one needed to root the device.
If you're struggling to get the device rooted and there isn't a very specific reason why you need root, then my best recommendation would be to rather just leave it stock.
As far as I know, flashing TWRP won't trigger Knox, so you'll still have that functionality. Recently, it's become less and less necessary to have root and fewer apps require it, as well.
Like I said, unless there is a very specific reason, you'll likely be better off just leaving it the way it is.
EDIT: I'm realising now the original problem was that your home button wasn't working. In that case, it'll be difficult to get into TWRP, anyway. I also made some assumptions about Knox, because this is on the Note8 sub forum. I don't know if your device has Knox. And You're on a rather old version of Android also, so I understand why you may want to root, but without your home button working, it could become difficult to get into the places where you need to be to make that possible.