I was running an AOKP milestone release with franco kernel alpha 66 on a Sprint Galaxy Nexus, in attempting to update to a newer version of AOKP and a newer kernel I boot locked my phone. Here's the list of things I've done to try to fix it and flash back to stock or a stable version of AOKP.
1. Used CWM to flash wipe data/catch and flash old AOKP and Kernel - Continually reboots
2. Attempted to connect adb after it boots to use fastboot to flash stock images - Couldnt stay on long enough to connect
3. Tried Odin and Heimdall to connect and flash in download/odin mode - Phone is not recognized by computer, it will show as either samsung Android USB device or unknown device, neither of which will connect for Odin or Heimdall to do their magic.
4. Uninstalled and re-installed multiple different combinations of drivers for Samsung and the phone to try to get it to connect (including deleting registry entries; the whole nine yards) - still no sustained android usb connection
5. Tried two different cables, one of which I am sure is a Samsung, the other of which I am pretty sure is from my phone originally
6. Tried two different computers, my laptop which already had drivers and a desktop which has never seen this phone, it would not install drivers for it
At this point, I'm completely at a loss as to my next attempts, any ideas? Also, please ask away for anything I didn't explain fully. I have well enough backups from titanium (no image though cause I'm an idiot) so I would probably like to just go clear back to stock and start over if possible.
p.s. - My volume down button works intermittently so its a pain to boot to the bootloader and I just use a usb jig to boot to odin.
Thanks!
Update -
When in download mode, If i plug into my computer, some times it will make the connect sound then quickly disconnect while sometimes it will make the connect sound then stay as an "unknown device", I can't really figure out what makes the different responses happen. Any ideas?
why are you trying to use ODIN mode?
just use fastboot if you want to go back to stock.
Sounds like your having some driver issues. Have you tried a factory reset in cwm?
Related
First and foremost, been a long time lurker here (first time poster) on XDA... and the community here is just outstanding.
So I've decided to root my epic, everything was great. I used the one click 2.5CWM root, and realized I wanted to try out another rom that wasn't compatible. Reflashed with the( ReRFS.Format.ROM.EC05 ) (since it kept me stuck on the samsung black screen) then went ahead and flashed the zip for CWM 3.0.0.6 with viperrom,...
Now here's where it gets interesting... I want to be able to revert back to a stock rom, and flash syndicate... but for some reason my CWM wont allow me to flash any .zip files from SD card. It says "failed to mount /sdcard". i formated it on my pc, it reads / writes fine, but anytime i boot into clockwork, it can't mount my sd card. I can still boot into my phone, it's still usable for daily usage, but it just doesn't look like what I like.
Now I've tried running Odin, but when im in the download mode, odin will not recognize my phone being plugged in. I've downloaded the proper drivers, for both my win7 x64 and 32 bit computers, tried every USB port etc... and it still wont work.
any idea on what I can do to get my CWM to work?
Use Odin with a non-stock cable.
I've tried it with 4 different data cables, 2 Samsung OEM, and 2 generics...
Have you tried a different PC, or Heimdall?
Make sure you're using Odin 1.61, the correct PIT, and the EC05 TAR.
http://k0nane.info/rom/odin-pit.zip
http://k0nane.info/rom/SPH-D700-EC05-8gb-REL.tar
Also there is a small amount of phones that did not want to Odin correctly unless the battery was out. You can try that too.
So I've tried to run Heimdall, and i'm still experiencing the same issue that I was having with Odin.
Every time I plug in my device via USB (samsung OEM data cable, only cable i have that will prompt that a device is connected) windows will pop up with a message, device not recognized (unknown device in device manager when in download mode) it seems to be fine and it'll recognize it correctly when I have the phone running (booted up into the rom)
I ran the zadig.exe for the drivers, and nothing seems to work.
Instead of Odin, try the SWUpdate for EB13, it is much less fickle
Place your phone in download mode (keyboard #1 and the power button) and see if it will connect/install
If It works, you can then move on to either upgrade to EC05 using the stock update zip, or install CWM and flash your FAV ROM
My comp doesn't seem to want to recognize the phone anymore... everything is "unknown device" now
Yeah get your hands on a blackberry cable. My guess it will help your cause. Make sure the drivers are installed on your pc as well.
im just going to reformat my netbook and do a fresh install on the drivers, too tires of the "guess work" i'll keep you guys posted on how that goes
SUCESS!
my epic is back to full stock via Heimdall. (took a little playing around to get)
@qbking77 - Thanks for the tip, I ended up using a 7" black berry data cable, and heimdall recognized it.
The only thing now though, all of the wires i have now, don't seem to let me use One Click Root CWM 3.0.2.5 I'll try it with my OEM samsung cable (that worked before) when i get home, I'll keep you guys posted.
Thanks again!
I'm new and I hope I'm not posting this in the wrong place or re-posting an old question, but I have been searching on this and other sites for days and haven't been able to find anything pertaining to my question, so sorry in advance If I'm not posting this correctly.
I have a rooted epic touch with rogue boot loader installed and UnNamed rom installed. I really liked the way it was running until I had some kind of malfunction happened and now the battery charge light won't shut off and the battery drains within a couple hours of standby time. the phone is only a couple months old and would like to take it to the sprint store as I'm assuming this is an obvious hardware issue. My problem is that my pc doesn't recognize my phone anymore so I can't flash back to stock and get rid of root, voiding my warranty. I have tried uninstalling and reinstalling kies and stand alone drivers multiple times with no avail. I've tried with the battery and sd card removed and have also tried on multiple pc's (2 win7 and and xp machine). every time it says the drivers weren't installed successfully and to replace the device being connected.
My question: Is there a way to revert to stock off of the internal memory of the phone? I know there are zip roms you can flash from the boot loader but I was wondering if there was a way to flash a rom from zip and install the original boot loader as well as get rid of root? Any help I can get would be extremely appreciated and again I apologize if I am wasting anyone's time by asking in the wrong place or re-asking a question.
Ok so I downloaded the Calkin's_Stock_Rooted_EK02_ROM_v1.0 and got it on my sd card via dropbox. Flashed and now have a stock rom on it which I think is a step in the right direction.
The only thing is now I have clockwork boot loader and still rooted. and still not recognizing on pc. anyone know of an unrooted zip with original boot loader?
I couldn't get my PC to recognize either of my 2 E4GT's, each due to a different reason, both issues were resolved by going through each step in sfhub's debugging checklist:
sfhub said:
This post is for the FAQ section:
Why is the install stuck waiting for device to be connected?
Your phone isn't being recognized by your PC as an Android device.
When the drivers are installed and the phone is properly recognized, you should see the following in start->run->devmgmt.msc
Code:
Android Phone
SAMSUNG Android ADB Interface
Modem
SAMSUNG Mobile USB Modem
Until you get the SAMSUNG Android ADB Interface to show up, neither ADB nor this script will work.
Here is a debugging checklist:
1) dial ##UPST# (##8778#) in the dialer and verify AP (or ALL) is checked (if CP is checked, phone won't be recognized as an Android device)
2) restart the ADB server (choose Option G to stop the server, it'll get started automatically by the script)
3) verify USB Debugging is ENABLED
4) verify USB drivers are installed (Win7-64bit see below)
5) try a different usb cable
If you are in Win7-64bit try changing the default install location for the drivers:
If you see an error like this:
Try running the CMD prompt (or e4gtauto-sfx.exe) as Administrator. Right-click on the CMD icon (or e4gtauto-sfx.exe) and select "Run As", then select Administrator.
If that doesn't work, try disabling windows firewall.
Click to expand...
Click to collapse
I went down that list and everything seemed to be in order but still no recognition by pc. I kept uninstalling and reinstalling the drivers and switching usb ports and it finally installed the drivers successfully long enough for odin to recognize it and to flash back to stock. As soon as it was done the machine stopped recognizing it again. Lucky break I guess. So I can now return it to sprint and deal with the hardware issue.
I would still like to find a zip file like the tar that I flashed that installs stock recovery and non rooted ek02 rom and kernel from cwm, if that's even possible.
Thanks Godswrath, for helping me out.
You could use wifi explorer to get files on to sd card and mobile Odin to flash the tar file back to stock....
Sent from my SPH-D710 using xda premium
Lol....I am a noob.
They make a mobile Odin? That would have saved my like 4 hours....
Ok I think my samsung galaxy nexus maguro is soft bricked. I can get to the odin screen, I can get to the TWRP screen, and I can get to the bootloader screen, but for the life of me I can not get it to talk over the usb. I have downloaded the Samsung USB Drivers, Ive tried Kies, I ve tried them both separately installed, I've tried them installed toether. I've even tried running it on another computer. I've tried the Universal Nexus Linux Toolkit on Ubuntu. I've gone through 6 different cables, and although I do not have the actual cable that came with this phone, I have tried an actual samsung mobile phone data cable and I can not get the computer to recognize the device.
Does anyone have any ideas?:fingers-crossed:
I'd even be willing to hear off the wall ideas at this point. It is not useable in the state that its in.
bump
bump
gnsoftbrick said:
bump
Click to expand...
Click to collapse
use adb sideload or flash from recovery.
set up correctly adb & fastboot in pc. boot to recovery first, command ~ adb devices * to check your devices is connected or not.
should be no problem if u still have custom recovery installed.
are u using ubuntu or window??
or use odin here~
http://forum.xda-developers.com/galaxy-nexus/general/guide-restore-to-stock-unbrick-galaxy-t2065470
gnsoftbrick said:
Ok I think my samsung galaxy nexus maguro is soft bricked. I can get to the odin screen, I can get to the TWRP screen, and I can get to the bootloader screen, but for the life of me I can not get it to talk over the usb. I have downloaded the Samsung USB Drivers, Ive tried Kies, I ve tried them both separately installed, I've tried them installed toether. I've even tried running it on another computer. I've tried the Universal Nexus Linux Toolkit on Ubuntu. I've gone through 6 different cables, and although I do not have the actual cable that came with this phone, I have tried an actual samsung mobile phone data cable and I can not get the computer to recognize the device.
Does anyone have any ideas?:fingers-crossed:
Click to expand...
Click to collapse
You can factory reset your phone and if this does not solve your problem the use wugfresh nexus root toolkit
a) If you can still get the device into fastboot mode try to flash the partitions with fastboot (grab the stock images from the google developers page and flash them partition by partition). You can also flash the recovery with fastboot.
b) There is an open source odin implementation called heimdall. But you should be extremly cautious before trying that one. You may also find original odin copies. But YMMV and those tools come with some risk.
Make sure you've got a reliable usb connection to your phone. Charge your phone if possible (or charge the battery with a working phone / external charger first).
I have an SM-P607T with an active T-Mobile plan - though I bought it from a third party then added it to my account. Previously everything worked fine, as I tried CM and a few ROMs on it, but ultimately went back to stock TMo ROM, 4.4.2, and just rooted it. Hadn't used it in awhile, grabbed it and thought I'd update to official Lollipop build.
First off, I disabled SuperSU and tried to apply the 4.4.4 update, assuming after that it'd offer me 5.1.1. Applying the 4.4.4 update failed. I factory reset the device in recovery mode (stock recovery), which of course fully removed SuperSU. Still fails updating. I downloaded the Lollipop ODIN tar, and that's where I started running into showstopper issues.
When I plug in a USB cable from a PC, the tablet starts charging, and that's it. There is no sign in windows that a device has been connected, no ding that something has been attached, no driver search. I tried this on 3 Win10 PCs. On all of them I installed Samsung Drivers, and even installed Samsung Easy Switch (new KIES). It would never register that it was plugged into a PC. I tried plugging my Note 4 in, registers and works fine (I read a thread on here by someone saying Win10 wouldn't recognize Samsung devices - not the case for me, phones work fine, just the tablet that won't show up). There is NO driver issue because the system never acknowledges anything is connected at all. I tried 3 PCs and 4 USB cables. I tried Samsung Easy Switch/KIES device recovery - tried putting tablet in download mode and tried putting it in recovery mode; neither ever shows up on PC. I tried using ADB, does not show up in devices (I have USB Debugging checked, Unknown Sources checked, etc etc).
I downloaded the Lollipop ODIN tar.md5 and put it on the microSD card. I loaded stock recovery, chose to flash from external storage, selected the .tar.md5, it said it was flashing it, said it flashed successfully even. Rebooted and it hadn't flashed at all.
Does ANYONE have ANY idea how to get my tablet updated? I can handle not being able to connect to PC, but I want to at least get OTA updates working. Factory reset, apply 4.4.4 OTA, fails after reboot every time.
Help?!
I have the similar problem as you. Someone said it could be easily resolved by enable CP logging in the recovery menu. I saw the solution after I got my device working so I did not try that.
My procedure is
1. Enter this using calculator (+30012012732+
2. enter *#0808#
3. switch to "DM+MODEM+ADB " option, OK, and reboot
4. until now, I could see the USB device in my Windows Device Manager, but MTP function won't work
5. repeat step 1 and 2
6. switch to "MTP+ADB" option, OK, and reboot
7. Done. Device could be identified. (Windows 10 x64 Pro)
Hope it could be useful for you.
Hi i have a similar problem as you, my Note is the SM-P600 that I rooted and has TWRP v2.8.7.0 and last time I went into recovery, the thing came up with a stock red upper left hand side text say "recovery in not seandroind enforcing" then ended up with the "Firmware upgrade encountered an issue please select recovery mode in kies and try again" but the damn thing will not connect. 2 usb 3 ports and 2 usb 2 ports multiplecables- anker, samsung you name it-musical ports, tried right clicking the 4 usb port hubs and unchecking power saving in power mgnt- nothing- yet my the usb drivers see my note 4 just fine, in device mngr, the note tablet shows up in usb at the bottom as samsung device, I am just perplexed as to how to un**** this thing. If you have any suggestions and can let me know I'd appreciate it.
bigillz said:
I have an SM-P607T with an active T-Mobile plan - though I bought it from a third party then added it to my account. Previously everything worked fine, as I tried CM and a few ROMs on it, but ultimately went back to stock TMo ROM, 4.4.2, and just rooted it. Hadn't used it in awhile, grabbed it and thought I'd update to official Lollipop build.
First off, I disabled SuperSU and tried to apply the 4.4.4 update, assuming after that it'd offer me 5.1.1. Applying the 4.4.4 update failed. I factory reset the device in recovery mode (stock recovery), which of course fully removed SuperSU. Still fails updating. I downloaded the Lollipop ODIN tar, and that's where I started running into showstopper issues.
When I plug in a USB cable from a PC, the tablet starts charging, and that's it. There is no sign in windows that a device has been connected, no ding that something has been attached, no driver search. I tried this on 3 Win10 PCs. On all of them I installed Samsung Drivers, and even installed Samsung Easy Switch (new KIES). It would never register that it was plugged into a PC. I tried plugging my Note 4 in, registers and works fine (I read a thread on here by someone saying Win10 wouldn't recognize Samsung devices - not the case for me, phones work fine, just the tablet that won't show up). There is NO driver issue because the system never acknowledges anything is connected at all. I tried 3 PCs and 4 USB cables. I tried Samsung Easy Switch/KIES device recovery - tried putting tablet in download mode and tried putting it in recovery mode; neither ever shows up on PC. I tried using ADB, does not show up in devices (I have USB Debugging checked, Unknown Sources checked, etc etc).
I downloaded the Lollipop ODIN tar.md5 and put it on the microSD card. I loaded stock recovery, chose to flash from external storage, selected the .tar.md5, it said it was flashing it, said it flashed successfully even. Rebooted and it hadn't flashed at all.
Does ANYONE have ANY idea how to get my tablet updated? I can handle not being able to connect to PC, but I want to at least get OTA updates working. Factory reset, apply 4.4.4 OTA, fails after reboot every time.
Help?!
Click to expand...
Click to collapse
---------- Post added at 11:04 AM ---------- Previous post was at 11:02 AM ----------
I am confused what you mean by calculator, I am on Win 10 and have a similar problem, my Note is the SM-P600 that I rooted and has TWRP v2.8.7.0 and last time I went into recovery, the thing came up with a stock red upper left hand side text say "recovery in not seandroind enforcing" then ended up with the "Firmware upgrade encountered an issue please select recovery mode in kies and try again" but the damn thing will not connect. 2 usb 3 ports and 2 usb 2 ports multiplecables- anker, samsung you name it-musical ports, tried right clicking the 4 usb port hubs and unchecking power saving in power mgnt- nothing- yet my the usb drivers see my note 4 just fine, in device mngr, the note tablet shows up in usb at the bottom as samsung device, I am just perplexed as to how to un**** this thing. If you have any suggestions and can let me know I'd appreciate it.
shineliu said:
I have the similar problem as you. Someone said it could be easily resolved by enable CP logging in the recovery menu. I saw the solution after I got my device working so I did not try that.
My procedure is
1. Enter this using calculator (+30012012732+
2. enter *#0808#
3. switch to "DM+MODEM+ADB " option, OK, and reboot
4. until now, I could see the USB device in my Windows Device Manager, but MTP function won't work
5. repeat step 1 and 2
6. switch to "MTP+ADB" option, OK, and reboot
7. Done. Device could be identified. (Windows 10 x64 Pro)
Hope it could be useful for you.
Click to expand...
Click to collapse
shineliu said:
I have the similar problem as you. Someone said it could be easily resolved by enable CP logging in the recovery menu. I saw the solution after I got my device working so I did not try that.
My procedure is
1. Enter this using calculator (+30012012732+
2. enter *#0808#
3. switch to "DM+MODEM+ADB " option, OK, and reboot
4. until now, I could see the USB device in my Windows Device Manager, but MTP function won't work
5. repeat step 1 and 2
6. switch to "MTP+ADB" option, OK, and reboot
7. Done. Device could be identified. (Windows 10 x64 Pro)
Hope it could be useful for you.
Click to expand...
Click to collapse
thank you very much. it worked.
Hey there guys!
Recently I wanted to get some custom ROM on my brother's Gio. It had stock Samsung software on it, did a factory wipe in recovery, worked perfectly, then I installed CWM in the orignal recovery from the SD card - didn't root before. Since then I can't boot into Recovery, however Android booted up. I tried to use some apps in software to get rid of this problem, but ROM Manager said the device is not supported, then I tried another one called Rashr, which had a question relating to recovery I guess instantly on the app's startup, I hit "Reboot" since then the phone is bricked. If I turn it on with just the power button, it shows the Samsung logo, stuck in a bootloop. I can't access recovery, only dumpram, and Download Modes. I tried fixing this with reinstalling the stock stuff through Odin, but the software doesn't detect the phone. Tried installing Kies, standalone USB drivers, multiple Odin versions, different cables, ports, different computer, nothing worked. When I connect the phone to my PC it plays the "device connected sound" but I got a message, that it's an unidentified device. Went into Device manager, where it recognizes it as a Samsung USB device, with the yellow triangle. Tried updating the driver manually from the manufacturer's list, uninstalling then reinstalling the drivers with no luck. Also I tried cleaning the USB port of the phone, still nothing.
The computers I've tried are running Windows 8.1.
Please help me, I think I've tried everything still the device is bricked.
I have same problem.
did you fix it ?
weLL ,sad to say it but ,its neither worth the effort,time or my typing these letters up here to remind you ,that it's neither the end of days or expensive to buy something this side of the stone aGe ! have fun but not with that one ;(
https://forum.xda-developers.com/galaxy-gio/orig-development
search here, download mode should be enough