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).
Related
All,
I have a big problem. When I try to start my phone I get the black screen with google and the unlocked padloack, after which the screen goes dark and nothing happens anymore.
What I did before this are two things. I had been mukking around with the screen resolution (I had it set at 240 and 280, as some apps did not show up in the market) also downloaded LCD density to solve the market issue.
I then rebooted the device and entered CWM to do a backup which as far as I knew succeeded. unfortunately after rebooting, see the above.
I have tried a couple of reboots, tried restoring the nandroid (the above was the only one I had). that didn't work, so tried to connect to the PC to load a new ICS rom (original 4.0.4 by google), unfortunately my device can not go into USB mode in CMW (it comes up with UMS lunfile missing....)
so I am woring in circles. can't start the device to download a rom, can't open USM to load a ROM to start the device again.....
any help would be appriciated
thanks
Patrick
hey
flash a new ROM via fastboot then, there are enough guides
-Syn
Edit: Alternatively, flash the stock Google ROM via GNex toolkit and go from scratch.
as mentioned, I can't get a rom on the phone so that I can flash it.
I can't start the phone to donwload one, and can't connect it to usb to get one on the storage....
sorry, you mentioned fastboot.... not USB.
so connect it to usb cable. I then entered fastboot devices, no number came up, as was also the case with ADB. thinkin I might not have the correct USB drivers for my windows machine. any idea where to get teh correct one?
pwvandeursen said:
as mentioned, I can't get a rom on the phone so that I can flash it.
I can't start the phone to donwload one, and can't connect it to usb to get one on the storage....
Click to expand...
Click to collapse
To flash stock images the files are on your PC, not the phone.
If you can get the phone to boot into fastboot (via vol up + vol dn + power) and get your PC to recognize it you're good to go.
thats the issue. pc cannot recognize the phone, so cannot get any files from the PC to the phone (ie. cannot get a rom file to the phone...)
pwvandeursen said:
as mentioned, I can't get a rom on the phone so that I can flash it.
I can't start the phone to donwload one, and can't connect it to usb to get one on the storage....
sorry, you mentioned fastboot.... not USB.
so connect it to usb cable. I then entered fastboot devices, no number came up, as was also the case with ADB. thinkin I might not have the correct USB drivers for my windows machine. any idea where to get teh correct one?
Click to expand...
Click to collapse
Either directly from Samsung or download the GNex Toolkit (You might want to use it anyways to flash the stock image), the drivers come with it.
After you installed the drivers and have you phone plugged in, go to the device manager to check if it is connected properly.
pwvandeursen said:
[snip]
thinkin I might not have the correct USB drivers for my windows machine. any idea where to get teh correct one?
Click to expand...
Click to collapse
For the drivers, I would recommend you remove all old drivers and install these. If you don't know how to install them, or are having issues, look here.
pwvandeursen said:
as mentioned, I can't get a rom on the phone so that I can flash it.
I can't start the phone to donwload one, and can't connect it to usb to get one on the storage....
sorry, you mentioned fastboot.... not USB.
so connect it to usb cable. I then entered fastboot devices, no number came up, as was also the case with ADB. thinkin I might not have the correct USB drivers for my windows machine. any idea where to get teh correct one?
Click to expand...
Click to collapse
I had a similar issue with regard to my PC recognizing the drivers. I googled around and found that people were having success with installing the PdaNet drivers, so maybe you can try that too. I had installed the Android SDK as well as the PdaNet drivers, and I eventually got mine to work.
I would probably follow Efrant's links first though - if that doesn't work for you, then maybe you can try PdaNet drivers and/or installing the SDK.
Good luck.
Why not just do a factory reset from within recovery?
¢ £®0π π€XU$ |||
the factory reset didn't help, the phone just wouldn't go past the black lockscreen. So in the end I used the galaxy nexus toolkit. installed the drivers for the PC, was able to go through fastboot and push files and flash a new rom.
Al is now solved, just need to do a lot of work to bring the phone back to where it was and make a backup asap.
thansk all for the help!
case closed.
pwvandeursen said:
the factory reset didn't help, the phone just wouldn't go past the black lockscreen. So in the end I used the galaxy nexus toolkit. installed the drivers for the PC, was able to go through fastboot and push files and flash a new rom.
Al is now solved, just need to do a lot of work to bring the phone back to where it was and make a backup asap.
thansk all for the help!
case closed.
Click to expand...
Click to collapse
Good to hear you got it.
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?
Hello all!
I have a major, major, problem. Last night I wanted to flash a new ROM, so I had everything wiped from my sdcard so it will be like new again. Sadly, I was retarded enough to also do a wipe on /system. Now there is no Android OS loaded on my phone anymore and no ROMs on my internal sdcard to flash it.
The phone would boot up and will be stuck on the screen with the white Google logo and the white unlocked lock.
I am still able to boot into Download mode, Fastboot mode and CWM. The bootloader is also unlocked.
The problem is that none of my PCs and Laptops would recognize my phone, not even trying numerous tutorials and reading different similar threads.
http://forum.xda-developers.com/showthread.php?t=1760787
http://forum.xda-developers.com/showthread.php?t=1869380
http://forum.xda-developers.com/showthread.php?t=1379875
http://forum.xda-developers.com/showthread.php?t=2370684
http://forum.xda-developers.com/showthread.php?t=1529058
http://forum.xda-developers.com/showthread.php?t=1777593
Also Odin and GNEX Toolkit doesn't see that my device is plugged in, both in Fastboot mode and Download mode, so I cannot flash with that either.
I hope someone had experienced the same problem or knows a solution to my problem.
Thanks in advance!
you have a driver problem. you need to uninstall your drivers and reinstall them.
So normally my PC would detect my phone even without it having any data or OS on it?
Could you maybe point out for me what kind of drivers I actually need? I have tried so many I got really confused.
iKaosTony said:
So normally my PC would detect my phone even without it having any data or OS on it?
Could you maybe point out for me what kind of drivers I actually need? I have tried so many I got really confused.
Click to expand...
Click to collapse
Focus on getting the correct fastboot drivers installed, and try to get your computer to recognize the phone when you type "fastboot devices" while connected via USB.
Flash a stock image from Google in fastboot mode. Boot into it at least once in order to regenerate the internal storage partition, before futzing around with custom recovery, root and new ROMS etc. If you flash CWM/TWRP without first booting once into the OS, you may be unable to write files to internal storage hence blocking any further progress.
I have tried almost everything to get the drivers installed on all the PCs I have at home, non of them is regocnizing my device.
tried it on both Windows 7 64Bit and Windows XP 32Bit.
Is my warrenty void if the bootloader is unlocked?
iKaosTony said:
I have tried almost everything to get the drivers installed on all the PCs I have at home, non of them is regocnizing my device.
tried it on both Windows 7 64Bit and Windows XP 32Bit.
Is my warrenty void if the bootloader is unlocked?
Click to expand...
Click to collapse
You're holding it wrong. Either that or your USB port/USB cable has died.
A few weeks after rooting and installing CM10 on my GS3, it stopped recognizing any form of USB data connection. It still charges from both computer and wall adapter, but I cannot initiate a data transfer or recognize my device using ADB.
I have tried:
three different OEM Samsung cables (from SG3/SG4 phones)
all the ports on two different Win 7 laptops
all the ports on an Ubuntu desktop
enabling or disabling USB debugging
with different combinations each time. No "USB connection" dialog has shown up on the phone, and no "new device" dialog has shown up on any of the computers. I know that I can get ADB working with a different Android phone (HTC Inspire 4G) so I know that my main laptop has USB ports that work and the cables I've tried work as well, so I'm left to assume that the issue is with the GS3. External visual inspection does not suggest the USB port on the phone is damaged, and the phone is only a year old, so I don't believe that is the cause.
Is there a system setting that I may have modified on the GS3 that would disable all forms of USB communication?
(The end goal is to get at least ADB working so I can try and recover some deleted files from the internal memory; I haven't found a reliable method that does not require ADB so I'm trying to get that to work. I know that transferring files on or off can be accomplished with the external SD card or over Wifi but that is not what I'm looking for)
Any suggestions from anyone?
I am not sure. Could be a software issue. I would try backing up your current cm ROM and try installing a fresh touchwiz ROM to see of that works, to rule out software issues. This could also be a android 4.3 issue. Could try stickmount or a similar otg app from the market.
Sent from my Nexus 7
stelv said:
I am not sure. Could be a software issue. I would try backing up your current cm ROM and try installing a fresh touchwiz ROM to see of that works, to rule out software issues. This could also be a android 4.3 issue. Could try stickmount or a similar otg app from the market.
Sent from my Nexus 7
Click to expand...
Click to collapse
I don't think any OTG app like stickmount will help; I'm not trying to connect devices to my phone. I'm trying to get my computer to recognize my phone (and vice versa) in order to get ADB working.
If I can avoid flashing a RAM I'd like to, because I'm still interested in recovering those deleted files. If that is the only thing that would help, though, then I'll do it. Any other suggestions?
Install Kies and that should get the drivers for the pc in place. Odin should recognize the device when it is in the download mode. If that works, then the pc to phone connection is OK and I'd look to software instead of hardware.
Or, if you boot into your custom recovery, either CWM or TWRP, you should be able to get ADB to recognize the device and issue commands including pulling the files on Internal storage. TWRP also has a file browser built in that might be useful.
I have tried uninstalling any Samsung drivers then using the SGS3 toolkit to install the official drivers, but that didn't change anything on the PC end.
Additionally, I tried finding my device while it was in recovery using ADB and there was no connection indication either.
I currently have CWM installed, but I didn't see a mounting option like I've seen for TWRP. Can I flash TWRP without a computer?
Or try this out: Download mode>Connect via USB>Let Windows download and update all drivers until the notification in the bottom right says it's ready to use>Unplug>Battery Pull>Boot normally>connect again. Voila! It works every time when it's being wonky and its a simple way that doesn't require a bunch of downloads!
installing insecure adb might help
Rebooting into download mode does nothing.
I believe rooting and installing CM10 means I already have insecure adb?
thanks
thanks
what next?
aEx155 said:
Rebooting into download mode does nothing.
I believe rooting and installing CM10 means I already have insecure adb?
Click to expand...
Click to collapse
I have this same issue, in download mode, the device is still not connecting.
what is the next step? I have followed this thread and have the still have the same issues.
I'm totally lost, I have tried everything in the world to get my Nexus 7 2ed gen to get out of a self inflicted boot loop. It all started when I wanted to upgrade it from 4.4.4 to 5.0.2. It was rooted and I have TWRP recovery installed, I wiped the data and chose the wrong thing to do. I instead of a simple wipe, wiped the entire OS and everything.... So now i'm stuck with a rather nice paperweight.... I can boot into recovery (TWRP) and Fastboot. But regardless of what i do I cant get the damn thing to be seen on my computer via ADB or fastboot, so I can't install the stock OS onto it. I've tried re-installing the drivers for The tablet and ADB/fastboot, a countless number of times and nothing works. I've tried it on other computers, that doesn't work, and from how I see it It should.... Anyone out there know what I did to screw this up and how to fix it?
Get an OTG cable and load a ROM onto a flash drive. Then flash the ROM and your choice of gapps.
Sent from my LG-D850 using XDA Free mobile app
^That would be the easiest but still why would fastboot not work?
If adb can't see it in twrp or fastboot on the bootloader screen it's gotta be a driver or connection issue right?
You've probably done it but try different cables/make sure the usb ports are clean.
I'm guessing you flashed twrp with fastboot and know how to use fastboot. If not make sure you're in the fastboot directory before typing the commands in the command prompt.
Only thing left that you already tried is reinstalling everything. Uninstall any fastboot/adb/drivers anything related to android really.
Install the sdk. Install the google usb driver from the sdk manage in the sdk folder.
Boot the tablet to the bootloader screen and plug it in, driver should install automatically. Open a command prompt in the platform-tools folder in the sdk folder and type fastboot devices.
If that doesn't work I have no idea. Oh you could try reinstalling java.
Ok I went ahead and ordered an OTG cable. I also tried installing all the drivers and such another time, but this time when I plugged it in, while it was in bootloader mode, the driver didn't install? I tried several cords, could it be that the tablets port itself is the issue?