Related
Alright guys, I'm lost here and could really use some help.
I was trying to root my Samsung Galaxy S2 Epic Touch 4G for Sprint. I most likely flashed the wrong bootloader or something in Odin. Long story short, I bricked it.
I went into download mode and tried again with different (presumably correct) files. Now it automatically boots into system recovery mode. I can still access download mode but both Kies and Windows fail to recognize the device (meaning I can't use Odin).
Also, when in recovery mode I can't select anything. I can scroll through the options but the only button that does anything is the search button which seems to just toggle text on the screen.
Any help is appreciated.
*UPDATE*
When booting into recovery mode when it says updating application it now says:
--Updating application...
E:install-application_for_customer:can't unmount/preload
copy application failed.
same problem here bro, im sure someone will figure out something
JooshPole said:
Alright guys, I'm lost here and could really use some help.
I was trying to root my Samsung Galaxy S2 Epic Touch 4G for Sprint. I most likely flashed the wrong bootloader or something in Odin. Long story short, I bricked it.
I went into download mode and tried again with different (presumably correct) files. Now it automatically boots into system recovery mode. I can still access download mode but both Kies and Windows fail to recognize the device (meaning I can't use Odin).
Also, when in recovery mode I can't select anything. I can scroll through the options but the only button that does anything is the search button which seems to just toggle text on the screen.
Any help is appreciated.
Click to expand...
Click to collapse
I had a problem with the Galaxy S the other day and it wasn't even turning on. I used a jig to get into Download mode which you obviously can do and then tried Odin. It would not recognize my phone just like yours is doing. What helped me was a program called Heimdall that found proper drivers and reloaded the stock rom and boot.im which helped me out of a tough situation. I am not sure where it is for our phones but see if you can use that program instead of Odin. It worked for me at least.
Sorry thats the best I got
JooshPole said:
Also, when in recovery mode I can't select anything. I can scroll through the options but the only button that does anything is the search button which seems to just toggle text on the screen.
Click to expand...
Click to collapse
w/r/t recovery, "Home" is select, "Power" is back, "Vol +/-" scrolls, "Menu" sometimes toggles screen modes back to text-mode.
sfhub said:
w/r/t recovery, "Home" is select, "Power" is back, "Vol +/-" scrolls, "Menu" sometimes toggles screen modes back to text-mode.
Click to expand...
Click to collapse
I know what to press, but it will only let me scroll and toggle text with the search key.
And you cannot get into download mode? It may help if you could post what you flashed.
iSkylla said:
And you cannot get into download mode? It may help if you could post what you flashed.
Click to expand...
Click to collapse
I can still access download mode.
Originally I followed this guide:
http://software2tech.com/2011/12/19/how-to-root-samsung-galaxy-s2-i9100g-dzkj2-2-3-6/
The second time I flashed it, I put this:
http://www.multiupload.com/N2A3457E2X
JooshPole said:
I can still access download mode.
Click to expand...
Click to collapse
Try plugging it into a different computer and see if the computer reacts at all, make some USB ding sounds, etc. If there is no reaction the USB port is not active and new drivers wouldn't help. If it reacts but doesn't ultimately install the drivers because they aren't present, that is ok, just have to find the right drivers for it to get recognized.
If you have no reaction from the new PC, try booting into Android and press ##8778# in the dialer. If a screen comes up, select "All" and press the [Back] capacitative button.
I don't know if that will do anything with the ROM/bootloader you have installed, but it changes what interfaces the USB port exports on the regular E4GT software.
sfhub said:
Try plugging it into a different computer and see if the computer reacts at all, make some USB ding sounds, etc. If there is no reaction the USB port is not active and new drivers wouldn't help. If it reacts but doesn't ultimately install the drivers because they aren't present, that is ok, just have to find the right drivers for it to get recognized.
If you have no reaction from the new PC, try booting into Android and press ##8778# in the dialer. If a screen comes up, select "All" and press the [Back] capacitative button.
I don't know if that will do anything with the ROM/bootloader you have installed, but it changes what interfaces the USB port exports on the regular E4GT software.
Click to expand...
Click to collapse
It won't respond when plugged into any computer. Also, if I could boot Android I wouldn't have a problem.
Check what you flashed. If it was for another phone install the drivers for that phone. This typically happens when you try to flash something for another phone and it looks like that phone to windows.
More than a few did this tying to flash ics
Sent from my SPH-D710 using XDA App
lifyre said:
Check what you flashed. If it was for another phone install the drivers for that phone. This typically happens when you try to flash something for another phone and it looks like that phone to windows.
More than a few did this tying to flash ics
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
Excellent idea! That makes sense. Based on the links I posted earlier, can you figure out what drivers I need to install?
I'm honestly considering this right now...
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-ii-jtag-brick-repair/
If you don't hear the USB ding sounds at all nor see any reaction from the new PC trying to find drivers that aren't there, new drivers won't help. The PC doesn't see anything because the USB interface isn't active.
If you can play around with various resets and get to the point you hear ding sounds or the PC starts reacting, then there is hope.
When booting into recovery mode when it says updating application it now says:
--Updating application...
E:install-application_for_customer:can't unmount/preload
copy application failed.
I'm assuming you have stock android recovery?
jasone4gt said:
I'm assuming you have stock android recovery?
Click to expand...
Click to collapse
What are you asking? Do I have a ROM for it?
When you boot into recovery, is it the stock android recovery or do you have clockworkmod recovery? Where are you seeing the:
--Updating application...
E:install-application_for_customer:can't unmount/preload
copy application failed.
Hey OP this thread deals with drivers I have a feeling some or all of the info in this thread will help you out. There are links to international sgs2 drivers and other useful info. like the earlier post stated knowing what you actually flashed is your first step at getting your computer to recognize your phone if ya flashed it to another version then you need the drivers for that phone installed in comp.
Good luck. Hope this helps. http://forum.xda-developers.com/showthread.php?t=1399551
jasone4gt said:
When you boot into recovery, is it the stock android recovery or do you have clockworkmod recovery? Where are you seeing the:
--Updating application...
E:install-application_for_customer:can't unmount/preload
copy application failed.
Click to expand...
Click to collapse
It's stock Android Recovery.
Rather than trying to fix it myself what do you guys think about just taking it to Sprint? I read somewhere that you can clear the flash counter with a Jig so sprint won't know I tried to root it.
So it seems that ODIN can only recognize my phone if the phone is powered on and running but will not recognize it in download mode. I am using the same cables I have used in the past as well as the same computer running Windows 7. Running stock ICS FH13 Unrooted and trying to root but cannot because once I enter download mode, ODIN stops seeing the device. Have tried re installing drivers many times and all USB ports on the computer with different USB cables. Hoping that somebody has a suggestion for getting the phone to be recognized in download mode for me.
ZeusIII said:
So it seems that ODIN can only recognize my phone if the phone is powered on and running but will not recognize it in download mode. I am using the same cables I have used in the past as well as the same computer running Windows 7. Running stock ICS FH13 Unrooted and trying to root but cannot because once I enter download mode, ODIN stops seeing the device. Have tried re installing drivers many times and all USB ports on the computer with different USB cables. Hoping that somebody has a suggestion for getting the phone to be recognized in download mode for me.
Click to expand...
Click to collapse
Is usb debugging checked
Sent from my SPH-D710 using xda premium
Yes debugging is checked.
Some more information. Turns out the phone (originally my friend's) needed to be taken in for service and when he did this he read somewhere about the USB jig to remove the custom binary counter. When he did this he flashed a gingerbread bootloader to use the jig. Only thing is, he didn't ask me for help (I've usually helped him out with this stuff in the past) and I think he flashed an international version of the bootloader. Reason being when I boot the phone it says Samsung Galaxy SII GT-I9100 where it should not have that last part. I remember reading somewhere about this and how it happened to somebody but they had CWM recovery and flashed a special zip. I do not have this option because of the stock recovery and unrooted ROM. Just wondering if there is anything that can be done to reverse this. I can run the phone and use it still but would rather root it and continue the way I have always done with my past phones.
ZeusIII said:
Some more information. Turns out the phone (originally my friend's) needed to be taken in for service and when he did this he read somewhere about the USB jig to remove the custom binary counter. When he did this he flashed a gingerbread bootloader to use the jig. Only thing is, he didn't ask me for help (I've usually helped him out with this stuff in the past) and I think he flashed an international version of the bootloader. Reason being when I boot the phone it says Samsung Galaxy SII GT-I9100 where it should not have that last part. I remember reading somewhere about this and how it happened to somebody but they had CWM recovery and flashed a special zip. I do not have this option because of the stock recovery and unrooted ROM. Just wondering if there is anything that can be done to reverse this. I can run the phone and use it still but would rather root it and continue the way I have always done with my past phones.
Click to expand...
Click to collapse
Does it have the yellow triangle when you see that? My phone shows that when I have the triangle.
No yellow triangle.
Mine has said gti9100 before. Don't remember what I flashed. Think it was a leak through mobile odin. So you may or may not be screwed...
sent from my BAD A$$ Epic touch
Hoping not but this is stock FH13. Did not flash anything and my computer/ODIN does not recognize my phone being plugged in when in download mode... Hoping someone can chime in here about something they would try or something I might have missed. I think I got all the basic troubleshooting stuff out of the way but if anybody can point something out, great!
Do u put your phone in download mode then hit volume up then connect to usb?
Sent from my SPH-D710 using xda premium
Yes, I go from full power off with USB unplugged and press and hold the power and vol down keys until I get the warning screen. I then hit vol up to continue and then plug in my phone to the computer.
With further research seems as though I am hosed. In download mode it lists my device as "product name: GT-i9100" where it should say "product name: SPH-D710" Still hoping someone can save me so I'm not stuck on stock but seems as though this device had a international phone's bootloader flashed onto it.
Yes, I go from full power off with USB unplugged and press and hold the power and vol down keys until I get the warning screen. I then hit vol up to continue and then plug in my phone to the computer.<br />
<br />
With further research seems as though I am hosed. In download mode it lists my device as "product name: GT-i9100" where it should say "product name: SPH-D710" Still hoping someone can save me so I'm not stuck on stock but seems as though this device had a international phone's bootloader flashed onto it.
Click to expand...
Click to collapse
Thats the problem i couldnt help u there but u can try installing the drivers u need
Sent from my SPH-D710 using xda premium
You could get Mobile Odin and flash using that. There's a lite option that will let you flash Agat's kernel and then you can go from there.
Searched all over and google yada yada yada. So i end up opening a thread here.
Hello guys/babes/kids/oldfags/ifags in disguise . I have a galaxy nexus here that will only boot into
-download mode,
- fastboot (not working at all, pc wont detect its fastboot and buttons all dead when in recovey/fastboot)
- safe mode - will boot into safe mode if i did combo buttons when attached to charger/pc
The story :
When i booted it from batt pull via only power button press, it will go into download mode straight and if i power off or factory reset in safe mode, it will reboot back into safe mode.
I cant flash anything since fastboot is broken. Ive tried Odin back to factory image of Galaxy Nexus GSM ICS and Jellybean but the prob isnt solved and fastboot is still broken. Tried repartition and bootloader update in ODIN yet still fail. And after every successful flash of repackaged stock, it will directly boot into safe mode (for both ICS and JB factory image). Why i didnt flash using fastboot? Fastboot is broken that is. Lets continue...
Other hardwares are still fine as in safe boot, ive tested all the buttons, display, calls, speaker etc. This is fastboot relate i believe as no matter what pc ive tried and all types of gnex drivers i tried. It wont even fart when connecting to pc(win7 x86). ADB works fine though when i booted into the safe mode. Im able to do adb stuffs but whenever i query it to reboot to fastboot or recovery, a dead end again. OMAPflash the tuna edition for omap4460? Tried yet still the same.
Additional facts : The phone was not unlocked and tempered by any way before the prob happened but now the bootloader is unlocked after i flashed the repackaged ODIN (chainfire posted it)
So XDA Gnex'ers, LET THE HUNT BEGIN!
Sent from my GT-I9100 using xda premium
Reserved for updates
Have you stumbled across this yet?
http://forum.gsmhosting.com/vbb/f63...-i9100g-via-usb-cable-freeeeeeeeeeee-1465412/
iowabowtech said:
Have you stumbled across this yet?
http://forum.gsmhosting.com/vbb/f63...-i9100g-via-usb-cable-freeeeeeeeeeee-1465412/
Click to expand...
Click to collapse
thats omapflash, to be more precise.
op, try that. also, might want to read something more, efrant has a link on it on one of his threads.
sent from my i9250
bk201doesntexist said:
thats omapflash, to be more precise.
op, try that. also, might want to read something more, efrant has a link on it on one of his threads.
sent from my i9250
Click to expand...
Click to collapse
Yup, tried it but its still the same. Fastboot still dosent work and relashing packaged factory images in odin dosent fix the fastboot
Sent from my GT-I9100 using xda premium
Saw a Jtag service nearby and thinking of sending it in. Its roughly after conversion from RM(Malaysian Ringgit) around USD$90. Possible recovery from the issue?
Sent from my GT-I9100 using xda premium
does it try to create an error log? or are you able to pull bug report?
it boots into download mode and safemode so, there's hope.
override182 said:
Searched all over and google yada yada yada. So i end up opening a thread here.
Hello guys/babes/kids/oldfags/ifags in disguise . I have a galaxy nexus here that will only boot into
-download mode,
- fastboot (not working at all, pc wont detect its fastboot and buttons all dead when in recovey/fastboot)
- safe mode - will boot into safe mode if i did combo buttons when attached to charger/pc
The story :
When i booted it from batt pull via only power button press, it will go into download mode straight and if i power off or factory reset in safe mode, it will reboot back into safe mode.
I cant flash anything since fastboot is broken. Ive tried Odin back to factory image of Galaxy Nexus GSM ICS and Jellybean but the prob isnt solved and fastboot is still broken. Tried repartition and bootloader update in ODIN yet still fail. And after every successful flash of repackaged stock, it will directly boot into safe mode (for both ICS and JB factory image). Why i didnt flash using fastboot? Fastboot is broken that is. Lets continue...
Other hardwares are still fine as in safe boot, ive tested all the buttons, display, calls, speaker etc. This is fastboot relate i believe as no matter what pc ive tried and all types of gnex drivers i tried. It wont even fart when connecting to pc(win7 x86). ADB works fine though when i booted into the safe mode. Im able to do adb stuffs but whenever i query it to reboot to fastboot or recovery, a dead end again. OMAPflash the tuna edition for omap4460? Tried yet still the same.
Additional facts : The phone was not unlocked and tempered by any way before the prob happened but now the bootloader is unlocked after i flashed the repackaged ODIN (chainfire posted it)
So XDA Gnex'ers, LET THE HUNT BEGIN!
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
First of all, bricked mean there is nothing beside a black screen. Nowaday device are hard to brick. second, One does not simply flash a gnex with odin. It's simply a big wtf that is shining through my head. 3rd, if fastboot is not working, it's because it need a special driver that i suppose you didnt install. If you can boot your phone in fastboot but can connect to it, it's because you have a broken USB port, which is not the case since you can access adb. 4th, i'm still trying to know how you achieved this. It look to me you were following some instruction and it either ended, tl;dr i will skip a few step, hope it will work which didnt or you missed electricity. Install Kies, get your phone in download and recover your phone from it. Never attempt again to play on custom rom. Man, how can someone derp a galaxy nexus, it is like the easiest device to work with.
chadouming said:
First of all, bricked mean there is nothing beside a black screen. Nowaday device are hard to brick. second, One does not simply flash a gnex with odin. It's simply a big wtf that is shining through my head. 3rd, if fastboot is not working, it's because it need a special driver that i suppose you didnt install. If you can boot your phone in fastboot but can connect to it, it's because you have a broken USB port, which is not the case since you can access adb. 4th, i'm still trying to know how you achieved this. It look to me you were following some instruction and it either ended, tl;dr i will skip a few step, hope it will work which didnt or you missed electricity. Install Kies, get your phone in download and recover your phone from it. Never attempt again to play on custom rom. Man, how can someone derp a galaxy nexus, it is like the easiest device to work with.
Click to expand...
Click to collapse
Thx for the reply.
Some clarification here, im not the owner of this phone. Im using 9100 and im just helping a friend to recovery. Ive tried few pcs and it wont even fart when i plugged in during fastboot or recovery (i read someone that in recovery you can do some commands) but the pc(s) wont even detect a hardware being plugged in.
Plus, in fastboot, i cant press any of the hardware keys. No vol up or vol down and the power button dosent work in recovery. I only got to the 3e stock recovery via 'adb reboot recovery' during in fast mode where it booted into the relaxing chillin android with the triangle + red exclamation mark on its tummy. Pressed all buttons and it went to the 3e recovery.
At the 3e, only power button works. I cant toggle a bit using the vol keys. Note that the vol buttons work to boot the phone into fastboot and download mode and also during safe mode, all the keys works flawlessly.
So, i tried the odin method to recovery this living Gnex but with a faulty heart and kidney but it will still boot to safe mode regardless of ICS or Jellybean.
How did this happen?
I have no idea. The owner of the phone claimed that he has never rooted or tempered it in any way. Plus it was still on ICS when i first got the phone (all data was still intact but it was in safe mode at that time).
Regarding drivers, ive attempted many pcs with almost every drivers available. Shall i list em here:
- KIES
- Naked Nexus drivers
- PDA.net
- the 'official' gnex verizon driver set which is said working on GSM devices etc.
Tried those and adb+download mode works fine. Pcs detect em and tried to install the hardware n search for the drivers but not in fastboot. Its just dead.
killersloth said:
does it try to create an error log? or are you able to pull bug report?
it boots into download mode and safemode so, there's hope.
Click to expand...
Click to collapse
Adb works fine so im able to pull anything when its booted. Im not sure if we can pull anything in download mode. Adb/fastboot didnt work in download mode. Am i correct? Mind to share some light here on this. And in fastboot, none. No vol keys to operate and the 4-5 pc ive tried wont even fart a sound or hint anything saying a hardware connected. Its like its a dead circuit plugged only in fastboot.
This is quite a super rare case here. Most of the dead gnex i found on the next and also in XDA has a working fastboot that only needs drivers to make it working but on this unit, even the vol keys is dead. Awkwarddddd
Sent from my GT-I9100 using xda premium
override182 said:
Thx for the reply.
Some clarification here, im not the owner of this phone. Im using 9100 and im just helping a friend to recovery. Ive tried few pcs and it wont even fart when i plugged in during fastboot or recovery (i read someone that in recovery you can do some commands) but the pc(s) wont even detect a hardware being plugged in.
Plus, in fastboot, i cant press any of the hardware keys. No vol up or vol down and the power button dosent work in recovery. I only got to the 3e stock recovery via 'adb reboot recovery' during in fast mode where it booted into the relaxing chillin android with the triangle + red exclamation mark on its tummy. Pressed all buttons and it went to the 3e recovery.
At the 3e, only power button works. I cant toggle a bit using the vol keys. Note that the vol buttons work to boot the phone into fastboot and download mode and also during safe mode, all the keys works flawlessly.
So, i tried the odin method to recovery this living Gnex but with a faulty heart and kidney but it will still boot to safe mode regardless of ICS or Jellybean.
How did this happen?
I have no idea. The owner of the phone claimed that he has never rooted or tempered it in any way. Plus it was still on ICS when i first got the phone (all data was still intact but it was in safe mode at that time).
Regarding drivers, ive attempted many pcs with almost every drivers available. Shall i list em here:
- KIES
- Naked Nexus drivers
- PDA.net
- the 'official' gnex verizon driver set which is said working on GSM devices etc.
Tried those and adb+download mode works fine. Pcs detect em and tried to install the hardware n search for the drivers but not in fastboot. Its just dead.
Adb works fine so im able to pull anything when its booted. Im not sure if we can pull anything in download mode. Adb/fastboot didnt work in download mode. Am i correct? Mind to share some light here on this. And in fastboot, none. No vol keys to operate and the 4-5 pc ive tried wont even fart a sound or hint anything saying a hardware connected. Its like its a dead circuit plugged only in fastboot.
This is quite a super rare case here. Most of the dead gnex i found on the next and also in XDA has a working fastboot that only needs drivers to make it working but on this unit, even the vol keys is dead. Awkwarddddd
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Great to know you are not the one who did that . So if i understand correctly, you say download mode work ? If yes, flash another stock rom from chainfire using odin. No one wan't to flash with odin, but if fastboot is not working, you shall at least try it. Also, when you are putting the phone in download mode and connecting it to kies, it should detect it has to be restored. i would say the main reason for it to not work is that android debugging is not ticked in developer options. But that would be strange that adb work on safe mode. There is probably a way to that with adb but you will have to google it. Tell your friend to follow instruction next time. And ffs, do not use odin ! (Little idea too, try to get in fastboot not connected on PC and wait a few minutes then see if you can move with the volume button, then try to connect it on pc)
chadouming said:
Great to know you are not the one who did that . So if i understand correctly, you say download mode work ? If yes, flash another stock rom from chainfire using odin. No one wan't to flash with odin, but if fastboot is not working, you shall at least try it.
Click to expand...
Click to collapse
Yes i have already did that few times. Few times of ICS factory image and few with JB. All are repacked version provided by chainfire. Its the full package not the software only with stripped bootloader n recovery. Its still the same
Sent from my GT-I9100 using xda premium
http://forum.xda-developers.com/showthread.php?t=1392310
download and install toolkit from that thread ^^^^^^
uninstall all gnex drivers you installed
reboot pc, open gnex toolkit, with phone unplugged install the drivers
fastboot should work
killersloth said:
http://forum.xda-developers.com/showthread.php?t=1392310
download and install toolkit from that thread ^^^^^^
uninstall all gnex drivers you installed
reboot pc, open gnex toolkit, with phone unplugged install the drivers
fastboot should work
Click to expand...
Click to collapse
Thx, tried it on a few pcs but it still wont work. Even the volkeys in fastboot didnt work :8
Sent from my GT-I9100 using xda premium
override182 said:
Thx, tried it on a few pcs but it still wont work. Even the volkeys in fastboot didnt work :8
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
did you try flashing google's factory image in odin??
my fastboot once was unresponsive, but rebooting into it fixed it
from safemode, if you adb reboot bootloader it is unresponsive?
killersloth said:
did you try flashing google's factory image in odin??
my fastboot once was unresponsive, but rebooting into it fixed it
from safemode, if you adb reboot bootloader it is unresponsive?
Click to expand...
Click to collapse
Yes i had, still boots to safe mode and the fastboot is still dead. Yes ive tried adb reboot bootloader but its dead in fastboot, again.
Sent from my GT-I9100 using xda premium
only suggestion left is to just boot into fastboot, leave it alone for awhile (5-10 mins), then try and plug it in and mess with it.
Try doing the whole driver thing mentioned above but instead of flashing a Google image just do the boot loader portion, what settings are you using to flash in Odin?
Sparx639
killersloth said:
only suggestion left is to just boot into fastboot, leave it alone for awhile (5-10 mins), then try and plug it in and mess with it.
Click to expand...
Click to collapse
Tried yesterday, nothing happened
Sparx639 said:
Try doing the whole driver thing mentioned above but instead of flashing a Google image just do the boot loader portion, what settings are you using to flash in Odin?
Sparx639
Click to expand...
Click to collapse
First tried pda only with auto reboot, no gooding. The i tried with booloader, no good. Then bootloader only, still no good. Then i tested all including pit file, still no good.
Update, sent in for Jtagging few min ago. The phone is not with me now and ill get it back in 3days working or not. I shall report in back after 3 days. Thanks to all by giving suggestion and ideas. See u guys again in 3 days
Sent from my GT-I9100 using xda premium
chadouming said:
Also, when you are putting the phone in download mode and connecting it to kies, it should detect it has to be restored. i would say the main reason for it to not work is that android debugging is not ticked in developer options.
Click to expand...
Click to collapse
adb does not work in download mode/bootloader. adb only works when adbd (adb service) is started, and that happens in android boot process. it means android debug bridge.
sent from my i9250
Sorry for the long delay to anyone waiting for the answer/status.
Jtag cant fix it. Returned the device to a friend. Prolly a mobo replacement is the solution but its damn pricy here in Malaysia. It costs 80% of the price to get a new Gnex.
Hell yeah and thx to everyone supporting this.
Sent from my GT-I9100 using xda premium
Newbie to rooting, using a VZW Galaxy Nexus.
I tried flashing 4.2.2 this evening, and somewhere along the way I bricked my phone. Simply turning on the phone results in the Google and Unlock icon screen, as does pressing Power and Volume Up. I can only boot into Odin mode (with Power + Volume Down), which I discovered by accident, and I've no idea what that does.
At this point, I'd be happy just getting back to stock 4.1.1. Any and all help greatly appreciated.
ODIN has no place being used on a Nexus device. You are in fastboot mode. There are several stickies at the top of this section on how to properly root your device. Read them.
063_XOBX said:
ODIN has no place being used on a Nexus device. You are in fastboot mode. There are several stickies at the top of this section on how to properly root your device. Read them.
Click to expand...
Click to collapse
I wasn't trying to use Odin; it's simply the only thing my phone will do at this point. The actual rooting of the phone went fine - I used Nexus Root Toolkit (1.6.3). The phone bricked when I was attempting to restore the backup I'd made.
My computer won't recognize the phone when plugged in. I downloaded drivers from Samsung - nothing. The Toolkit doesn't find the phone when attached.
I'm at a loss.
Again. Follow the stickies right at the top of this section.
You're at a loss because you used a toolkit rather than the slightly more challenging and infinitely more educational "right" way.
Have you tried booting with volume up+down+power, to see if the bootloader is still there?
salvation eedsfur
bodh said:
Have you tried booting with volume up+down+power, to see if the bootloader is still there?
Click to expand...
Click to collapse
Just tried and yes, bootloader is still there. But since my computer won't recognize the phone (I've tried installing and re-installing the ADB drivers), I can't figure out how to flash a ROM (stock or otherwise).
http://forum.xda-developers.com/showthread.php?t=1626895 You need fastboot drivers in fastboot / bootloader mode. And you're all set.
bodh said:
http://forum.xda-developers.com/showthread.php?t=1626895 You need fastboot drivers in fastboot / bootloader mode. And you're all set.
Click to expand...
Click to collapse
So far, so good. Still had issues installing the ADB driver, but finally got it to work. Many, many thanks.
If you can't flash your device in a regular way (via fastboot) there's also a possibility for Odin flash. It's not recommended but it works (it has never let me down). There are few threads about it.
m.kochan10 said:
If you can't flash your device in a regular way (via fastboot) there's also a possibility for Odin flash. It's not recommended but it works (it has never let me down). There are few threads about it.
Click to expand...
Click to collapse
Thanks, m.kochan - the problem was getting the computer to recognize the device. It finally came down to trail-and-error with installing and re-installing drivers. I had to boot into recovery, uninstall every Samsung/Google/Android related driver, reboot the computer, then install only the ADB driver. From there, I was able to flash the stock image using efrant's guide for dummies.
I was running CM10 but I got a message whenever I got into the Camera App that said "Unfortunately, Gallery has stopped working", after a research in here I found that I wouldn't get that msg again if I installed this "gapps-jb-picasa-20121011-signed" thing.
I did, but when I got into my Camera App, I didn't have the other options like "Image Effects" and all that stuff.
So, what I did was to Restore my phone from my BackUp folder that I've created before installing CM10, but for my surprise I got a msg saying "VolumeError" or something like that and other things that I can't really remember... and as a good Mexican that I am, I ignored it and hit the Reboot System Now..
What happened next almost made me cry...
I was expecting to get in my stock rom without any problems and yadda yadda but... OH SURPRISE!
I got stuck on the boot screen, where it says "Samsung" and the website of it and I didn't freak out... I waited like 5-6 mins and took the battery out. When I turned again, I tried to get in Recovery Mode but the screen just kept turning off and on and saying the exact same thing, the "Samsung" logo and it's website.
I hope you can help me and please answer me. I don't know if I'm 1000000% screwed but I will only wait for the worst. Sorry for my bad english and don't hate me for being mexican
I don't know if I can get into my phone from my PC but whenever I plug my phone in, it just loads it as if it was in Charging Mode
PLEASE HELP ME!
I BEG YOU!
Flash again CM10 with wipe data, cache, dalvik
If still stuck
Odin to stock ROM, you can search on google to odin the epic
Sent from my JellyBeer v.4.14 epicmtd (b3)
Questions go in Q&A
Thread moved
Friendly Neighborhood Moderator
Like @dropple said, it seems you stuck "SAMSUNG" and in this case you can't get into recovery so you can't flash CM10 as of now. Go find some tutorials and Odin back to stock via download mode. Then install CWM recovery if you want and do whatever you like. Should get you outta trouble.
Sent from HTC Incredible S @ PACman v21
AndyYan said:
Like @dropple said, it seems you stuck "SAMSUNG" and in this case you can't get into recovery so you can't flash CM10 as of now. Go find some tutorials and Odin back to stock via download mode. Then install CWM recovery if you want and do whatever you like. Should get you outta trouble.
Sent from HTC Incredible S @ PACman v21
Click to expand...
Click to collapse
Thanks to Everyone!
I solved this like 2 hrs after all this happened.
I got it by Odin. I couldn't go into Recovery Mode, but I got in Download Mode and do it by Odin.
Sorry, I'm a n00b to all this.
Greetings from México and thanks for all your support.
Here's a weird one for you,
Same thing as OP stated. Device is stuck on logo. Can't get into CWM. Was on People's Rom. Device was lagging really bad. Then the system requested superuser permissions. Yes the system requested. Being as I did not request it, I declined. Shut the device down to see if that would help with the extremely bad lag (i mean BAD lag. Like..........................ok it does something then.......................................................................ok it does something else. 10-20 seconds lag)
Connect device to computer to Odin back to Stock or whatever ROM would have worked, computer recognizes device..... wait for it.......
But in download mode Odin does not see it. Com Port will not illuminate. Tried 3 different cables. Tried 6 different USB ports on computer. Still nothing.
Any ideas, because I'm all out?!?
To the OP:
I would follow the instructions in this video from the part where qbking77 talks about putting the phone in download mode, as you presumably did when you first rooted your phone. Download all the files linked/referenced on the site, especially the Samsung mobile drivers, Odinv3 1.87, CWMRecovery, and the deOxed versions of the stock ROM. In sum:
1) get into recovery mode by holding onto the volume down, camera buttons, and then without letting either of those go, press and hold the power button.
if you get into recovery mode, skip to step 4
2) while your phone is completely off, hold onto the "1" button on the slide out keyboard first, then without letting the 1 button go, press and hold the power button until you're in download mode.
3) flash the version of Clockworkmod
4) once in recovery mode, wipe your phone, clear the cache, and dalvik cache, and then flash the deOxed version of the stock ROM
niteNarmor said:
Here's a weird one for you,
Same thing as OP stated. Device is stuck on logo. Can't get into CWM. Was on People's Rom. Device was lagging really bad. Then the system requested superuser permissions. Yes the system requested. Being as I did not request it, I declined. Shut the device down to see if that would help with the extremely bad lag (i mean BAD lag. Like..........................ok it does something then.......................................................................ok it does something else. 10-20 seconds lag)
Connect device to computer to Odin back to Stock or whatever ROM would have worked, computer recognizes device..... wait for it.......
But in download mode Odin does not see it. Com Port will not illuminate. Tried 3 different cables. Tried 6 different USB ports on computer. Still nothing.
Any ideas, because I'm all out?!?
Click to expand...
Click to collapse
Do you have the mobile drivers installed on the computer you're trying to connect your phone to?
Yes. The drivers have been installed previously. The computer will see the device as "Samsung SPH-D700 Card USB Device". But Odin3 1.85 will not see it.
EDIT: When I put device into download mode and connect to computer, the computer only sees it as "Gadget Serial".
niteNarmor said:
Yes. The drivers have been installed previously. The computer will see the device as "Samsung SPH-D700 Card USB Device". But Odin3 1.85 will not see it.
EDIT: When I put device into download mode and connect to computer, the computer only sees it as "Gadget Serial".
Click to expand...
Click to collapse
Uninstall and reinstall drivers.
Sent from my SPH-D700 using Tapatalk 2
Have already done that. But just for laughs, I did do it again with no change.
can you get your D700 into download mode as described above?
Yes I can get into download mode but without Odin recognizing the device (not computer. The computer recognizes the device) there is not much I can do.
niteNarmor said:
Yes I can get into download mode but without Odin recognizing the device (not computer. The computer recognizes the device) there is not much I can do.
Click to expand...
Click to collapse
Try to install another version of Odin or getting Odin from a different server.
My phone is fully recovered and now I'm only SuperUser 'cause I don't want any CM by now.
Greetings from Mexico!
I'm using the same version of Odin I used to root the device. Would a different version really help and if so, what version to use?
I actually have a different version of Odin I used for another device and tried that one as well, with no luck.
EDIT: I have now downloaded and tried 4 different Odin programs with no avail. Again, that makes 6 Odin programs, 6 different USB ports, 3 different cables with the same exact results. The computer recognizes device but Odin will not.
niteNarmor said:
I'm using the same version of Odin I used to root the device. Would a different version really help and if so, what version to use?
I actually have a different version of Odin I used for another device and tried that one as well, with no luck.
Click to expand...
Click to collapse
Had a simular issue when I had two odins on the same computer, for a lark and as I had nothing better to do, tried installing drivers and one version of odin to a vertual machine running vista and checked to see if my computer's vertual machine would reconize and it did, I took it as a sine that at one point I had done something to my computer's main os sometime between rooting my epic 4g and frying it (recovering from a backup from a different parition layout I think, bad times with bootloops and seeing way to much of the samsung logo.) So as I'm not brave enough to run odin on vm I instead removed all of odin from my main os and all of the samsung drivers, then reinstalled rebooted and repluged my epic in, got reconition and reflashed with plesure.
The other issue might be that your computer is reconizing the device and try/failing/hanging and not allowing odin in. Had an issue when my computer was failing to pop up a 'what do I do with this' window and hanging round in the system. A reboot with the internet unpluged strangely solved that for some reason, might be the reboot might be the combo, but I find better connection reconition with my computer when I've fewer things connected.
Don't mind the spelling to much I clean up with my other device.
Sent from my T-Mobile myTouch 3G Slide using xda app-developers app
One question I noticed that hasn't been asked is when you plug the phone into the computer while the phone is on, is usb debugging checked? If not, check it, and reinstall drivers again.
Sent from my SPH-D700 using Tapatalk 2
jeffreyjicha said:
One question I noticed that hasn't been asked is when you plug the phone into the computer while the phone is on, is usb debugging checked? If not, check it, and reinstall drivers again.
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
Phone does not boot past the "Samsung - www.samsung.com" logo. Plus, as with all of my devices, USB debugging is always checked.
Thanks for the suggestion though. Always helps to double check things.
I believe I am going to take it to Sprint tomorrow.
If I can't get into it, they should not be able to get into to it either. If they can't get into it, HELLO WARRANTY....
Perhaps before doing the whole getting found out thing with the return center, perhaps they do know what they're doing, try rolling this link past your eyes?
http://forum.xda-developers.com/showthread.php?t=773032
I know I've been in your boot problem situation and recovered, it just took persistence and eyenumbing amounts of reading.
Note On the multiple Odin, USB, and driver installation: if you've access to another computer it could be worth wile to run once though on a previously virgin computer, meaning your phone and computers' USB's have never touched. Just do the installation, rebooting, and plugging in exasperatingly meticulous order.
Sent from either my SPH-D700 or myTouch3Gs using XDA app
"it never hurts to help"
Yep tried the "virgin computer" computer as well. The computer sees the device but Odin does not. Com light will not illuminate.
Sounds grim.
So to rap up all the cables, plugs, computer, and software with odin is out of the debug process.
So I did some digging into the past and if your computer is reconizing and odin is not then ADB (android debug bridge) and the sdk are the other option
http://forums.androidcentral.com/epic-4g-rooting-roms-hacks/33427-how-access-your-adb-shell.html
Ran across this and it might just be what you need. Its not quick but it has worked for me in the past.
The other thing that may work is ejecting the sd card and battery before doing anything. Though its likely something you've already tried.
Sent from either my SPH-D700 or myTouch3Gs using XDA app
"it never hurts to help"