Related
Hello Everyone,
Captivate owner/user here, but had a question regarding a buddy's Epic. I have looked all over the forums, but have not found anyone else who has encountered this problem, so I apologize if this is a repeat thread. I believe my friend was running BakedSnack v1.6 with the DK28 modem. He went ahead and tried flashing ViperRom Trinity, and got stuck at the Samsung screen. I'm not familiar with flashing on this device, so I dont know the correct methods. I did however try to Odin his phone, and have failed to get my pc/odin to recognize his phone. I've tried every driver file I could find and nothing works. He has access to CWM so I hope it's not fully bricked. I figured his pc would recognize it, having has the drivers previously installed, but nothing. Any feedback is greatly appreciated, thanks.
Try a different cable and a different USB port on the computer. These phones can be picky with the cables.
You are not bricked if you can get to CWM.
Neckberg said:
Try a different cable and a different USB port on the computer. These phones can be picky with the cables.
You are not bricked if you can get to CWM.
Click to expand...
Click to collapse
Originally, we kept trying on my Captivate's cable to no luck. My pc would not even beep or see it. Then we tried another micro usb cable, and this time my pc saw it, but couldnt identify it, due to drivers im assuming. That was as close as I got unfortunately...
Torridred04 said:
Originally, we kept trying on my Captivate's cable to no luck. My pc would not even beep or see it. Then we tried another micro usb cable, and this time my pc saw it, but couldnt identify it, due to drivers im assuming. That was as close as I got unfortunately...
Click to expand...
Click to collapse
get the driver from here: http://www.multiupload.com/O9ZLS8GZP8. This was posted in this thread: http://forum.xda-developers.com/showthread.php?t=963652
amosher13 said:
get the driver from here: http://www.multiupload.com/O9ZLS8GZP8. This was posted in this thread: http://forum.xda-developers.com/showthread.php?t=963652
Click to expand...
Click to collapse
Tried that driver already, still no luck. At first i was thinking my pc wasn't installing the driver correctly until he installed it on his computer and had no luck as well. I installed it multiple times and uninstalled it, still never recognized the phone.
might want to install the android sdk, i actually remember having issues as well on my win7 pc until i did that. then look for adb in C:\Program Files\android-sdk-windows\platform-tools or that relative to where you install it.
Torridred04 said:
I did however try to Odin his phone, and have failed to get my pc/odin to recognize his phone. Any feedback is greatly appreciated, thanks.
Click to expand...
Click to collapse
In order to Odin the phone you MUST be in Download Mode. Turn the phone off the press the 1 key while pressing the Power key.
Appreciate the replies everyone. I did have the phone in download mode when trying to Odin but it failed to show the COM message indicating its been recognized. Download & CWM work & boot up, but the computers don't recognize the device and every driver I've tried installing has had no effect.
Sent from my Captivate
If no com on the screen your drivers not installed correctly, try unplugging and plugin the cable back in. Try different pc with WinXP if u can cuz Win7 is a real pain unless u doing the drivers right after windows installation. Hope this helps.
Sent from my SPH-D700 using XDA App
The same thing happens with my Epic and new roms...
To solve it, I pull the battery, replace the battery and boot with the Samsung "three finger salute"...
Just hold power+camera+volume down and it will boot direct to recovery. Just reboot from recovery and it should work OK.
Okay so my friend bricked his galaxy nexus (Gave it to me because he said its bricked) of course i accepted it lol. But i tried to fix it i did everything i could from reading forums i swear i have worked forever looking for a fix. It is completely unresponsive no download mode. no ADB connection because when it plugs into a computer it shows up as OMAP 4440 or something like that. i have tried all kinds of different drivers and i have tried on multiple computers (Xp, Windows7, even a mac) he said he was flashing the sdcard or something and unplugged it by accident. So i could understand that being a issue since the phone only has a internal sd card. Anyone know how to get it back? i havent seen a Jtag yet for it and i have a Jig for my Galaxy Sii Skyrocket but it doesnt work on the nexus (FYI to anyone out there the jig works on my dads samsung windows phone) HELP!
You tried different drivers? You should just use the most current ones for the phone. Did you try the new toolkit mskip posted? Did you isntall the SDK?
paperhurts said:
You tried different drivers? You should just use the most current ones for the phone. Did you try the new toolkit mskip posted? Did you isntall the SDK?
Click to expand...
Click to collapse
Thanks for the response i didnt use mskips i dont think. i have tried the galaxy nexus toolkit 6.0 or whatever but i have tried all kinds of drivers including the google official galaxy nexus i515 or something like that. it shows up as omap 4440 in app manager and disconnects and connects constantly then says device didnt install properly. what do you mean by the sdk? i cant find any way to access my phone. i think i tried something with sdk but im not sure
Yes i read up i did do that GNex Toolkit v6.0 and it wouldnt find my phone (Because of the omap 4440 disconnect and reconnect thing i believe.
First off, on't use a toolkit.
Second, when you plug it in, go to device manager, right click the "OMAP 4460" and click install driver. Either install PDANet or find the driver online and your phone should be able to be used in fastboot.
Finally, if your (Or your friends) phone was "Fully Bricked" it wouldn't be recognized by the computer, it wouldn't turn on, it would literally not be able to do anything except sit there, the fact that the computer sees it means that it is "Soft Bricked" which is much less serious.
miketoasty said:
First off, on't use a toolkit.
Second, when you plug it in, go to device manager, right click the "OMAP 4460" and click install driver. Either install PDANet or find the driver online and your phone should be able to be used in fastboot.
Finally, if your (Or your friends) phone was "Fully Bricked" it wouldn't be recognized by the computer, it wouldn't turn on, it would literally not be able to do anything except sit there, the fact that the computer sees it means that it is "Soft Bricked" which is much less serious.
Click to expand...
Click to collapse
i appreciate it but when i install the driver which one should i select? it is the Verizon LTE one and i have tried manually choosing the driver but there is so many. What one should i choose?
When i try to install pdanet it always uninstalls at the end automaticaly? why is that?
IRusselldABear said:
When i try to install pdanet it always uninstalls at the end automaticaly? why is that?
Click to expand...
Click to collapse
I couldn't get PDAnet to work for me either. It asks you to enter Debugging mode and I can't get into android
I cant get into android neither thats the problem... it is unresponsive except for the fact that it says omap 4440 over and over. im gonna play with it more when i get home but im currently in school. LOL
is it possible to volume+power into recovery mode?
Jsweetser2 said:
is it possible to volume+power into recovery mode?
Click to expand...
Click to collapse
I can get mine into CWM, but whenever I'm flashing a ROM, it reboots itself.
Install PDANet and when it asks for your phone, go into Task Manager and force close the process. This will keep the driver/program installed without needing your phone and it should then be seen in recovery.
Not working still :/
Thanks for highjacking my post twinky lol. i have seen the answer to yours around... google a little more.
TwinkyOfHope said:
I can get mine into CWM, but whenever I'm flashing a ROM, it reboots itself.
Click to expand...
Click to collapse
Jsweetser2 said:
is it possible to volume+power into recovery mode?
Click to expand...
Click to collapse
Please Help!
My phone goes into boot loader and download mode however every time I flash Stock it finishes successfully and goes to the same google screen its always stuck on. I'm kinda a n00b so if anyone could help me with this (try to have a lot of detail) I would be grateful. Thanks
It sounds like what I did to my Galaxy Note before I bought my Nexus. When unrooting I overwrote my bootloader with a missed character through ADB. I tried everything, naked drivers, ODIN, all it would come up with was OMAP on the PC. I ended up having to return it to AT&T. Ask him if he was trying to root it the old way through ADB.
samiaziz said:
My phone goes into boot loader and download mode however every time I flash Stock it finishes successfully and goes to the same google screen its always stuck on. I'm kinda a n00b so if anyone could help me with this (try to have a lot of detail) I would be grateful. Thanks
Click to expand...
Click to collapse
samiaziz, make sure you're wiping everything before flashing a stock rom. It wouldn't hurt to wipe system, cache and dalvik and then restart recovery (in advanced menu) and wipe again before flashing the stock rom.
Ok, as long as it shows up, it's still working
OMAP440 is the processor, which means, that is is working, but the bootloader is corrupt, or missing. I'd say it's corrupt (Flash-error)
The best way I've found, check this website: http://www.mobiletechvideos.com and see if they have a JTAG solution... (My JTAG device will arrive in a few weeks )
Even if they don't, send it in, and they'll figure out a way to do that I think they do some special offer, if you send it in for testing purposes...
But, other than that, there's no way I can help you. The firmware is completely fu**ed...
Tried That
I have already tried getting into recovery but that dosnt work. it takes me to the google splash screen
2 words: fastboot, linux.
sent from my i9250
Instead of JTAG-ing it, you could always try this. The maker of the Riffbox JTAG has come out with a solution for unbricking by reflashing the OMAP processor.. Aptly named OMAPFlash.
I've used it with success several times, but also had it fail on me. It can't hurt though, if your phone is already bricked.
If it's coming up with OMAP4460 (even briefly) when the phone is plugged into your computer without a battery, you are able to run the program. You just need to install the drivers for it.
See http://forum.gsmhosting.com/vbb/f634/unbrick-dead-samsung-gt-i9250-galaxy-nexus-32gb-prime-via-usb-cable-freeeeeeeeeeee-1465412/ for download.
Lemme know if you need instructions.
Hello! I'm having some trouble rooting my device. I have rooted my previous device (i9100) before so I'm not a complete noob about this and I followed the instructions EXACTLY.
What's happening is whenever I hit start on Odin to root my phone it comes up with an error "No PIT partition found". The phone is working perfectly well normal but it just seems to get stuck here no matter what I do. I've searched all over the internet and I cannot seem to find a solution to this. I've tried enable/disable debugging and allow unknown sources downloads. I've plugged into different USB's, heck even different computers and installed Kies on(Phone gets recognised by Kies so that's confirmation that I have drivers). I've also set up Odin first then plug my device whilst it's in recover/download (the home/power/volume down one) and vice versa. Nothing...All I keep getting is that error.
I have no clue what's going on but I have contacted Samsung support. The problem is, is that I bought this device off eBay and the seller said it was an unwanted upgrade. So it was still new and when I checked it was. It's also a real Note 2 (Checked it all). I'm not sure if I can still get warranty so I would love it if anyone here could help me with this!
These were errors coming up using Odin version 1.85. However, I have tried everything with Odin 3.
With the newer version I just get " Get PIT for mapping.."
and it stays there and eventually says Failed.
I am running windows vista on this computer and I tested it also on an older xp computer to which I had no success.
jonnyh1994 said:
These were errors coming up using Odin version 1.85. However, I have tried everything with Odin 3.
With the newer version I just get " Get PIT for mapping.."
and it stays there and eventually says Failed.
I am running windows vista on this computer and I tested it also on an older xp computer to which I had no success.
Click to expand...
Click to collapse
Vista hates every thing!!
Driver problem.
Download and install drivers from ketan's thread.
If you have windows 8 then there is a special procedure.
Search samsung drivers and see in one of the xda threads.
Sent from my GT-N7100
Make sure when you put device in download mode (Vol down +home +power) next screen is warning and you pressing Vol up to put device in download mode.
Kies should not run in background
Close if any antivirus installed
Turn off firewall
Then retry
Sent from my GT-N7100 using xda premium
Ive uninstalled kies so it shouldnt be the thing interrupting and have kept drivers because I can still use phone as storage and it recognises it. I am in odin download mode because it says cutom firmware no etcetc. Its all right and ive double checked it. It just doesnt seem tp work :/
I asked the person I bought it off and they said it came factory unlocked and came with his EE contract but it was unwanted upgrade so he sold it. If that information helps
Guys, sorted it out. I tried flashing it through odin on my windows 8 laptop. I think the note 2 will only flash with either windows8 or only on USB2.0 sockets. All computers I have tested and failed on were USB1.0! So happy!
Hey guys i've been looking through alot of google and can't seem to come up with anything so i turn to you awesome people.
My friend got a Galaxy Nexus GSM and he bought it with a boot loop problem. The phone is rooted and bootloader unlocked. I know because i can go to CWM recovery and also theres the unlock sign on it. However I can't get my computer to recognize it what so ever not even mount the storage. I figure i need to get the drivers to install but i need it to be recognized in device manager to do it through a rootkit. I tried to install the ADB drivers but also got no luck. I then tried to get to ODIN for it to work but ODIN won't recognize it either. Is there any way to install the drivers so i can put on a ROM on this. I think the person he bought it from formatted everything and messed it up. Is there anyway i can install the drivers without getting it to recognize first? I tried it in windows 7 and in windows 8. ANY HELP IS GREATLY APPRECIATED!!!
dnpmoney45 said:
Hey guys i've been looking through alot of google and can't seem to come up with anything so i turn to you awesome people.
My friend got a Galaxy Nexus GSM and he bought it with a boot loop problem. The phone is rooted and bootloader unlocked. I know because i can go to CWM recovery and also theres the unlock sign on it. However I can't get my computer to recognize it what so ever not even mount the storage. I figure i need to get the drivers to install but i need it to be recognized in device manager to do it through a rootkit. I tried to install the ADB drivers but also got no luck. I then tried to get to ODIN for it to work but ODIN won't recognize it either. Is there any way to install the drivers so i can put on a ROM on this. I think the person he bought it from formatted everything and messed it up. Is there anyway i can install the drivers without getting it to recognize first? I tried it in windows 7 and in windows 8. ANY HELP IS GREATLY APPRECIATED!!!
Click to expand...
Click to collapse
read the stickies
http://forum.xda-developers.com/showthread.php?t=1626895
Pay attention to Section A. Forget Odin, no need to be using that.
First off thanks so much for the reply and help it is very aprreciated!
Secondly i did come across this sticky however like i stated the phone is in a boot loop which means i cant get past the google logo in order to set it in developer mode and set usb-debugging neither can my computer recognize the phone when i plug it in, using the original cable i've tried every port there is on my desktop and laptop and nothing comes up in device manager. The phone is completely wiped and no OS is on it. Is there any way i can get a ROM on the phone?! This is one idea i have but i don't know if it'll work, I was thinking of buying a another working nexus install the drivers with that one and then i can get the bootloop one to get recognized? and return the new one. Will that work?
dnpmoney45 said:
First off thanks so much for the reply and help it is very aprreciated!
Secondly i did come across this sticky however like i stated the phone is in a boot loop which means i cant get past the google logo in order to set it in developer mode and set usb-debugging neither can my computer recognize the phone when i plug it in, using the original cable i've tried every port there is on my desktop and laptop and nothing comes up in device manager. The phone is completely wiped and no OS is on it. Is there any way i can get a ROM on the phone?! This is one idea i have but i don't know if it'll work, I was thinking of buying a another working nexus install the drivers with that one and then i can get the bootloop one to get recognized? and return the new one. Will that work?
Click to expand...
Click to collapse
You need to get adb to work with your device, which you can do in a custom recovery. You don't need to have USB debugging enabled, you would if you were booting into the OS, but not the recovery.
You can get drivers setup while in recovery or fastboot just as easy as if you were booted into the OS, so no you don't need another device.
cupfulloflol said:
You need to get adb to work with your device, which you can do in a custom recovery. You don't need to have USB debugging enabled, you would if you were booting into the OS, but not the recovery.
You can get drivers setup while in recovery or fastboot just as easy as if you were booted into the OS, so no you don't need another device.
Click to expand...
Click to collapse
thanks thats great news cause i dont have that kind of cash but how do i get ADB to work with the phone every installation guide i've looked at requires that i have the phone recognized om device manager. Is there anyway to install adb without having the device to recognize?
dnpmoney45 said:
thanks thats great news cause i dont have that kind of cash but how do i get ADB to work with the phone every installation guide i've looked at requires that i have the phone recognized om device manager. Is there anyway to install adb without having the device to recognize?
Click to expand...
Click to collapse
again, read the thread i gave you. if you're still asking this question, read it again.
Isn't that for the nexus 4? And I did pay attention to section A but it told me how to install the drivers which is the same way as every other tutorial I've looked at. My device doesn't show up on my computer and I can't install their way. As for the fastboot driver installation idk what their talking about. I followed the instructions though and got no results. I didn't do the whole thing cause for part C I need the original rom for galaxy nexus and also I don't know if the platform tools zip is for my device so I haven't gone through with it just yet. I'm sorry it's not my phone so I don't want to mess it up even further. I've read about the part with it being in recovery mode with the volume up + power option but I'm at work and haven't tried that yet but I doubt that will work since the phone is clean. Can u please be a little more specific there's 99 pages that I have to go through for that sticky. If u can't it's ok I'll just have to go through it next week. Once again thanks for pointing me in the right direction and giving me some hope.
Sent from my Nexus 4 using xda premium
WTF, how in the hell did that thread get here, sorry man
This is the right one
http://forum.xda-developers.com/showthread.php?t=1626895
a maguro wrote this.
Oh ok thanks this makes a lot more sense. Sorry for not telling u that earlier lol.
seriously thanks ill try it tonight.
Sent from my Nexus 4 using xda premium
ok so i tried the link but im always stuck with part A. When i go into fastboot and then try the command "fastboot devices" it hangs on waiting for the device. I can't see the device anywhere on my computer to install the fastboot drivers as instructed by 1wayjonny in this post http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1
Am i missing something here? i did everything in the other steps such as downloading all the files into the same directory and everything. Im using windows 7 and i updated all my drivers for usb and even tried different usb cables including the original and usb2.0 and 3,0 ports but still no dice. I also tried it on windows 8 and got the nada.
dnpmoney45 said:
I can't see the device anywhere on my computer to install the fastboot drivers as instructed by 1wayjonny in this post http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1
Click to expand...
Click to collapse
You reboot the device into bootloader/fastboot mode, then you connect the USB, and there's no sign at all that a USB device has been installed?
Remove all drivers, reboot, and start over. Get a tool for Windows that allows you to really dig on all of the installed drivers and remove all Nexus devices drivers permanently. Rant: Umm, Windows sucks bad. Thanks Linus!
bk201doesntexist said:
You reboot the device into bootloader/fastboot mode, then you connect the USB, and there's no sign at all that a USB device has been installed?
Remove all drivers, reboot, and start over. Get a tool for Windows that allows you to really dig on all of the installed drivers and remove all Nexus devices drivers permanently. Rant: Umm, Windows sucks bad. Thanks Linus!
Click to expand...
Click to collapse
I've done it both ways just to ensure it wasn't something that simple. I uninstalled all drivers i can possibly find theres non no where i used CC to look for more and device deview and even unistalled the java se and eclipse and android SDK and all the packages and installed them again and still nothing. My nexus 4 however recognizes both in adb and fastboot ......
Anything at all? Anyone?
Sent from my Nexus 4 using xda premium
dnpmoney45 said:
Anything at all? Anyone?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Well, maybe you could try omapflash. If you can't get several PCs to see the device, then something's wrong with the USB port?
Not even on Linux?
a manta wrote this.
bk201doesntexist said:
Well, maybe you could try omapflash. If you can't get several PCs to see the device, then something's wrong with the USB port?
Not even on Linux?
a manta wrote this.
Click to expand...
Click to collapse
I did a little looking up about omapflash and from what i can see so far there needs to be drivers installed first. I may be wrong but i have to do some more research on it and i dont have a linux pc my laptop is down thanks to a power pin connector pin being pulled out. and i dont know if the device port is good or bad i can get a charge but that doesnt mean its fine. What if i get another device and install drivers via that and then try to get it to recognize? would that work?
dnpmoney45 said:
What if i get another device and install drivers via that and then try to get it to recognize? would that work?
Click to expand...
Click to collapse
To really make sure that the issue isn't on the host side but rather the USB port on the device? Yeah, that would rule it out.
Also, I just remembered: you're not using the USB ports of your PC case are you? Make sure you're using the motherboards' own USB ports.
a maguro wrote this.
bk201doesntexist said:
To really make sure that the issue isn't on the host side but rather the USB port on the device? Yeah, that would rule it out.
Also, I just remembered: you're not using the USB ports of your PC case are you? Make sure you're using the motherboards' own USB ports.
a maguro wrote this.
Click to expand...
Click to collapse
Thats all it would do?! What about making me able to install the drivers and get the phone to be recognized? No wont work im dreaming?
And no im not using case ports at all i use them for charging and thats all i know at least that those arent reliable.
Windows 8 64-bit...drivers install...stuck
even I am stuck on the same roadblock. have my GNex stuck on the google logo. can access recovery mode though (TWRP 2.5.0.0). Now i just upgraded my PC to Windows 8 64-bit and cant seem to be able to install drivers.
the problem is that almost all the methods require:
1. GNex to be connected with USB Debugging ON
2. install ADB Drivers
3. get into Fastboot or Recovery
4. install Bootloader Drivers
since i cant get past the Google logo on my GNex...i cant perform Steps 1 & 2.
and if i directly try to install the bootloader drivers the OS returns an error (yellow exclamation next to the installed driver)
Added pictures to help explain better.
Thnx in advance.
rej_ares said:
even I am stuck on the same roadblock. have my GNex stuck on the google logo. can access recovery mode though (TWRP 2.5.0.0). Now i just upgraded my PC to Windows 8 64-bit and cant seem to be able to install drivers.
the problem is that almost all the methods require:
1. GNex to be connected with USB Debugging ON
2. install ADB Drivers
3. get into Fastboot or Recovery
4. install Bootloader Drivers
since i cant get past the Google logo on my GNex...i cant perform Steps 1 & 2.
and if i directly try to install the bootloader drivers the OS returns an error (yellow exclamation next to the installed driver)
Added pictures to help explain better.
Thnx in advance.
Click to expand...
Click to collapse
SOLVED (Dont know how but it worked):
1. Factory reset (TWRP)
2. Installed an old ROM which was already on the GNex
3. Restart...it gets stuck at the Google logo...remove battery
4. TWRP - Factory reset
5. reboot...
Hey everyone! My second post here!
So my nexus 7 is having a bit of trouble being recognized by my PC. Ive tried to change between PTP & MTP with nothing, I've also tried turning debugging off. As well as trying to update/reinstall drivers. Didn't work :c
So please help
Is your AndroidSDK up to date? Try different cables and USB ports?
nhizzat said:
Is your AndroidSDK up to date? Try different cables and USB ports?
Click to expand...
Click to collapse
im having the exact same problem.. im using the nexus root toolkit ive updated, uninstalled, cleared, restarted.. about all i can handle..
ive succesfully unlocked my device but adb driver/nexus 7 always cant be found or doesnt work in windows 7
nhizzat said:
Is your AndroidSDK up to date? Try different cables and USB ports?
Click to expand...
Click to collapse
Trying SDK now, and yes I tried different cables and usb ports
DjTawmeh said:
Hey everyone! My second post here!
So my nexus 7 is having a bit of trouble being recognized by my PC. Ive tried to change between PTP & MTP with nothing, I've also tried turning debugging off. As well as trying to update/reinstall drivers. Didn't work :c
So please help
Click to expand...
Click to collapse
This is what I use and it works with all versions of Android that I have used..
Its a universal driver for most Android devices.. It has never failed me
https://www.dropbox.com/s/t6x8szvi4kjun6n/latest_usb_driver_windows.rar?dl=0
Install this driver in Your Device Manager.. First Uninstall the old or current one your using..
then install the driver.. it also works on my Windows 10 test machine...
Edit: You might want to disable Device Driver Signing.. In case the driver refuses to install.
DjTawmeh said:
Hey everyone! My second post here!
So my nexus 7 is having a bit of trouble being recognized by my PC. Ive tried to change between PTP & MTP with nothing, I've also tried turning debugging off. As well as trying to update/reinstall drivers. Didn't work :c
So please help
Click to expand...
Click to collapse
I had exactly the same problem even after re-installing drivers etc nothing appeared to work. Prior to updating to Lollipop I did a factory reset (set up from new) and since then my PC has no problems seeing the Nexus 7. So as painful as it is you could always try a factory reset.
Sounds like you may have the wrong drivers in Windows.
The WUG toolkit has a script that you can follow that will walk you through manually removing all the drivers in Windows. That usually will get you straightened out.