So, I've done goofed. Ill admit it, i was stupid. Anyways, I was in ClockworkMod Recovery V6.0.1.5 because i wanted to restore to older backup because CN Mod update screwed up my play access. While mucking around in it, i went ahead and deleted everything (formatted sdcard, systen, cache, data). So yea my rom is gone but i wasnted to worried because i could install everything again from recovery. Now the thing is, my phone wont connect to the pc. I cant find an option in recovery to enable phone to connect to pc (or is that supposed to be automatic?). I tried fastboot and adb but without phone connecting to pc, no dice. I went into ODIN mode and the pc would recognize it but the windows install driver would always fail. Any help in solving this would be really appreaciated. Thanks.
PS. It a Fido Galaxy Nexus GT-i9250M
Looks like you havent installed the drivers properly.
I use the drivers that come along with the PdaNet installer for windows (google it).
In case you are using Windows 8, you'll have to enable installation of digitally unsigned drivers. You can google this too as well.
Just use the nexus tool kit 1.7.6 by wugfresh is can fix all your problems
osiandtrix said:
Just use the nexus tool kit 1.7.6 by wugfresh is can fix all your problems
Click to expand...
Click to collapse
Even teaching a user to install drivers on Windows?
beekay201 said:
Even teaching a user to install drivers on Windows?
Click to expand...
Click to collapse
Yes.
Sent from my Galaxy Nexus using xda app-developers app
Yeah it is basically a one button method and it also tells you how to get out of a soft boot loop so if it does happen you can restore from a backup and not to flash from a program like ODIN
Sent from my AOSP on Maguro using XDA Premium 4 mobile app
Try "Setting Up ADB for Our Device", it's in the first paragraph of this thread by the great Juba.
http://forum.xda-developers.com/showthread.php?t=1529058
---------- Post added at 05:01 PM ---------- Previous post was at 04:59 PM ----------
Also you can try "Setting up Drivers" from this thread also by Efrant
http://forum.xda-developers.com/showthread.php?t=1626895
---------- Post added at 05:11 PM ---------- Previous post was at 05:01 PM ----------
And since I'm link happy, if you feel like trying to get your data back, try this thread from Wartickler.
http://forum.xda-developers.com/showthread.php?t=1994705
Thank you all, i fixed it.
Heres what i did for future reference:
Turns out the drivers were the problem. I used the tool kit osiandtrix suggested and that helped remove all previous installations of the drivers. After i rebooted the pc i just left the phone connected to windows and let windows do it thing. I clicked on the universtal drivers option but not sure if it did anything. From there i went into recovery and used adb sideload to put the new cm update and flash it. Everything is good now.
Related
Has anyone seen this? I can't flash anything at all via the toolkit or ADB or fastboot.
On my nexus's screen it keeps saying this at the bottom in blue:
Fastboot Status - FAILWrite Fail
Here's the background. My bootloader is unlocked. I have root or had (when i "upgraded" to 4.0.2 superuser is there but I can't seem to give anything root access anymore).
I decided to start fresh and just wipe the phone and use the factory images to install 4.0.4 onto the phone. But it seems no matter which drives I try, ADB just won't recognize my phone in bootloader mode.
You're doing it wrong.
iphone. helping computer illiteracy become popular since 2007.
@rbiter said:
You're doing it wrong.
iphone. helping computer illiteracy become popular since 2007.
Click to expand...
Click to collapse
Thank you for the extremely helpful response.
Does anyone else have any ideas?
ksc6000 said:
Thank you for the extremely helpful response.
Does anyone else have any ideas?
Click to expand...
Click to collapse
uhhhh did you even unlock your bootloader?
Sent from my Galaxy Nexus using xda premium
Diger36 said:
uhhhh did you even unlock your bootloader?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yes, it's unlocked.
Make sure you have the galaxy nexus files? I was a moron and had same issue when I accidentally downloaded nexus s
Sent from my Galaxy Nexus using xda premium
ksc6000 said:
Yes, it's unlocked.
Click to expand...
Click to collapse
Sorry, didn't read your OP right... My mistake.
Do you have a proper backup? If so: Maybe a lock and unlock bootloader might work. It's just a long shot but the message triggers me in that direction. Off course you will loose all your data, inclusing on /sdcard.
Diger36 said:
Sorry, didn't read your OP right... My mistake.
Do you have a proper backup? If so: Maybe a lock and unlock bootloader might work. It's just a long shot but the message triggers me in that direction. Off course you will loose all your data, inclusing on /sdcard.
Click to expand...
Click to collapse
Worth a try. I don't mind losing everything as I made a backup of the SD card on my computer before attempting.
EDIT: Nope, was able to re-lock and unlock the bootloader but still when trying to flash anything it says: FAILED <remote: Write Fail>
aimetti said:
Make sure you have the galaxy nexus files? I was a moron and had same issue when I accidentally downloaded nexus s
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
That is exactly what I did. SMH @ myself
adb wont recognize your phone in bootloader? Because ADB is when android is running. You need fastboot when you're in bootloader.
try another usb cable. and yes, either that or you're holding it wrong.
use fastboot: http://andwise.net/?attachment_id=270
and make sure you have the drivers for fastboot
do exactly as it says here http://andwise.net/?p=268
i got the same thing .. i flashed a kernel on my stock rom and then i was trying to flash the factory image and i had write fail thing
Ok. So we have a couple of symptoms, here.
1: You try to flash via fastboot, phone says: "Nuhu! Not with me, bro!"
2: The ADB/fastboot won't recognize the phone.
3: Some guys answering this thread, are just idiots...
Solutions:
1: Try erasing, before flashing. It helps
2: Reinstall the ADB/fastboot drivers (Check my signature, and do that (It works with every distribution of Windows form Vista+) This will reinstall the drivers, and the ADB/fastboot command/deamon will be able to communicate, with the deamon on the phone...
3: Ask a moderator, if he can delete some of those nasty n00b answers...
LG familyguy59
---------- Post added at 02:14 PM ---------- Previous post was at 02:10 PM ----------
M7amad90 said:
i got the same thing .. i flashed a kernel on my stock rom and then i was trying to flash the factory image and i had write fail thing
Click to expand...
Click to collapse
Again, read my sig.
TO ALL: Before creating a new thread, save memory (on the servers) and search function!!
Beatsleigher said:
Ok. So we have a couple of symptoms, here.
1: You try to flash via fastboot, phone says: "Nuhu! Not with me, bro!"
2: The ADB/fastboot won't recognize the phone.
3: Some guys answering this thread, are just idiots...
Solutions:
1: Try erasing, before flashing. It helps
2: Reinstall the ADB/fastboot drivers (Check my signature, and do that (It works with every distribution of Windows form Vista+) This will reinstall the drivers, and the ADB/fastboot command/deamon will be able to communicate, with the deamon on the phone...
3: Ask a moderator, if he can delete some of those nasty n00b answers...
LG familyguy59
---------- Post added at 02:14 PM ---------- Previous post was at 02:10 PM ----------
Again, read my sig.
TO ALL: Before creating a new thread, save memory (on the servers) and search function!!
Click to expand...
Click to collapse
I had the same problem, erasing userdata before flashing bootloader helps in solving,
actually i flashed the fact image via nexus toolkit and it asked to erase teh userdata first.
i wiped my os by accident, got the flash tool but it says my side-by-side config is incorrect...tryed changing compatibility to xp but same thing....im downloading it again hoping it was a bad download....was just wondering if theres a easy fix for it in the mean time....im running win7 premium x64
buckedup12 said:
i wiped my os by accident, got the flash tool but it says my side-by-side config is incorrect...tryed changing compatibility to xp but same thing....im downloading it again hoping it was a bad download....was just wondering if theres a easy fix for it in the mean time....im running win7 premium x64
Click to expand...
Click to collapse
If you still have recovery, just install a stock ROM.
If you need help on the tool, try the LGFlashtool thread. It would get you more responses. http://forum.xda-developers.com/showthread.php?t=2443185
i do have recovery still but there is no OS on the phone, so it will not mount usb
buckedup12 said:
i do have recovery still but there is no OS on the phone, so it will not mount usb
Click to expand...
Click to collapse
Then adb sideload. Hang on and I'll post you the link
Sent from my LG-LS970 using XDA Premium 4 mobile app
---------- Post added at 11:21 AM ---------- Previous post was at 11:20 AM ----------
Here. http://forum.xda-developers.com/showthread.php?p=36270473
Sent from my LG-LS970 using XDA Premium 4 mobile app
buckedup12 said:
i wiped my os by accident, got the flash tool but it says my side-by-side config is incorrect...tryed changing compatibility to xp but same thing....im downloading it again hoping it was a bad download....was just wondering if theres a easy fix for it in the mean time....im running win7 premium x64
Click to expand...
Click to collapse
download this and install it . here the link
http://www.mediafire.com/download/a5g06vsl59wbxfl/Setup_LGFlashTool_1.4.1.330R.zip
then redo exactly everything in the guide. if it ask too override everything then accept it.
Hi i Just bought a used Galaxy, with 4.3 Android. Can someone please post the right guide for My N7100XXUEMj9?
There are sooo many guides And no one seems to work. I would like Root and install cwm or twrp. I tried with Odin with Previous release
But They didn't work... Any suggestions?
http://www.w0lfdroid.com/2013/12/Safe-Root-Android-4.3-Galaxy-S3-S4-Note-No-Warranty-Void.html
Diegentarodie said:
Hi i Just bought a used Galaxy, with 4.3 Android. Can someone please post the right guide for My N7100XXUEMj9?
There are sooo many guides And no one seems to work. I would like Root and install cwm or twrp. I tried with Odin with Previous release
But They didn't work... Any suggestions?
Click to expand...
Click to collapse
---------- Post added at 12:07 AM ---------- Previous post was at 12:06 AM ----------
Twrp Odin Http://goo.gl/SSyv53
Thanks i Will try It tomorrow. I found a link for safe root tool.
Where Can i find My usb driver download?
Your computer should install.the drivers needed.when you plug the phone into.it. also connect it after.putting it into download mode, that installs more drivers. Dont know why. If.it.doesnt for whatever reason there are plenty around: http://drivers.softpedia.com/get/MOBILES/Samsung/SAMSUNG-USB-Driver-for-Mobile-Phones-15290.shtml
Diegentarodie said:
Thanks i Will try It tomorrow. I found a link for safe root tool.
Where Can i find My usb driver download?
Click to expand...
Click to collapse
What I did:
I was using XperiaN ROM 7.0 then the beta came out I downloaded the beta and via TWRP flashed the BOOT+SYSTEM+VENDOR and it removed my TWRP now I wan to flash TWRP and cannot as the device is not recognised by fastboot (windows 10) Please help me I wan to go back to 7.0 on CM 14.
Same problem here and spent most of yesterday trying different things but no joy. Even tried leaving the beta program this morning which downloaded the latest 7.0 but despite starting again from scratch still cant get passed fastboot recognising. ADB all ok.
It's blooming frustrating.
xdanikhil164 said:
What I did:
I was using XperiaN ROM 7.0 then the beta came out I downloaded the beta and via TWRP flashed the BOOT+SYSTEM+VENDOR and it removed my TWRP now I wan to flash TWRP and cannot as the device is not recognised by fastboot (windows 10) Please help me I wan to go back to 7.0 on CM 14.
Click to expand...
Click to collapse
divvykev said:
Same problem here and spent most of yesterday trying different things but no joy. Even tried leaving the beta program this morning which downloaded the latest 7.0 but despite starting again from scratch still cant get passed fastboot recognising. ADB all ok.
It's blooming frustrating.
Click to expand...
Click to collapse
Update your platform tools. Then make sure to plug the phone only once booted into the bootloader
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Update your platform tools. Then make sure to plug the phone only once booted into the bootloader
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
No joy.
this is what someone in another thread suggested
ReeVestrife said:
Finaly got it to work, with help from this answer:
http://forum.xda-developers.com/showpost.php?p=64236079&postcount=12
After trying all that i mentioned in previous post, i killed ADB from task manager, switched off phone, booted to bootloader, with hardware buttons, plugged in cable, only after i was already in bootloader, and the voodoo started working for me! i can now see my device in fastboot!
Click to expand...
Click to collapse
divvykev said:
No joy.
Click to expand...
Click to collapse
im having the same problem and it all happens after the major windows 10 update.
anyone tried to reinstall the windows update and see if it works again?
Hey guys, no answers and I should have searched first, but I just posted a similar thread.
---------- Post added at 03:43 PM ---------- Previous post was at 03:27 PM ----------
jd1639 said:
Hey guys, no answers and I should have searched first, but I just posted a similar thread.
Click to expand...
Click to collapse
Edit, OP, what version of Windows are you running? I'm on 1607 and have similar issues.
jd1639 said:
Hey guys, no answers and I should have searched first, but I just posted a similar thread.
---------- Post added at 03:43 PM ---------- Previous post was at 03:27 PM ----------
Edit, OP, what version of Windows are you running? I'm on 1607 and have similar issues.
Click to expand...
Click to collapse
tried to uninstall the latest windows update build which is 1607 and........... voila!!!! still doesnt work
http://forum.xda-developers.com/showpost.php?p=69273414&postcount=33
This post shows the solution which worked for me
Many thanks to @TheeWolf
I was going to do a factory reset/wipe on this phone and through twrp checked the box for wipe system and now my phone has no OS installed on it. I downloaded the latest files but when i put it in download mode my pc wont recognize the phone. A little box pops up that says something like "your pc malfunctioned since last time this usb device was plugged in and now cant recognize it" So i reinstalled the samsung usb drivers, and it still does the same thing. What can i do from here? Or am i screwed?
BDog21 said:
I was going to do a factory reset/wipe on this phone and through twrp checked the box for wipe system and now my phone has no OS installed on it. I downloaded the latest files but when i put it in download mode my pc wont recognize the phone. A little box pops up that says something like "your pc malfunctioned since last time this usb device was plugged in and now cant recognize it" So i reinstalled the samsung usb drivers, and it still does the same thing. What can i do from here? Or am i screwed?
Click to expand...
Click to collapse
Try using a USB cleaner (http://www.thewindowsclub.com/usboblivion-remove-usb-traces-windows) and remove all Samsung devices. Reboot. Then try reinstalling.
If you can get the phone recognized in Download mode, I just posted the newest TAR file in my thread here: https://forum.xda-developers.com/sp...uide-links-files-update-root-restore-t3366862
Good luck and post your results.
That's where I got it. Thanks. I'll try that when I get home and post results.
Oh and I'm pretty sure that file, inside the zip is just a .tar.md5 file. I just extract then use that in the AP line in Odin?
BDog21 said:
That's where I got it. Thanks. I'll try that when I get home and post results.
Oh and I'm pretty sure that file, inside the zip is just a .tar.md5 file. I just extract then use that in the AP line in Odin?
Click to expand...
Click to collapse
Correct.
Nope, didnt work
It boots into TWRP?
Sent from my SM-G925P using Tapatalk
---------- Post added at 12:58 AM ---------- Previous post was at 12:54 AM ----------
If so, you could install a rom on it.
https://forum.xda-developers.com/showthread.php?t=3550677
Sent from my SM-G925P using Tapatalk
nhail47 said:
It boots into TWRP?
Sent from my SM-G925P using Tapatalk
---------- Post added at 12:58 AM ---------- Previous post was at 12:54 AM ----------
If so, you could install a rom on it.
https://forum.xda-developers.com/showthread.php?t=3550677
Sent from my SM-G925P using Tapatalk
Click to expand...
Click to collapse
ya, it will boot into twrp, but idk how i would get the file onto the phone storage at this point...
BDog21 said:
ya, it will boot into twrp, but idk how i would get the file onto the phone storage at this point...
Click to expand...
Click to collapse
Do you have an OTG cable? If so, you could transfer the rom to a flash drive.
When you connect your S6 to the computer, hit the Windows key and type in device manager. Try to find the phone there. Right click and go to properties. Click update driver and "choose one of the drivers already installed." See what pops up there. I had this issue with my s3, switched the driver and got access to my storage.
Sent from my SM-G925P using Tapatalk
nhail47 said:
Do you have an OTG cable? If so, you could transfer the rom to a flash drive.
When you connect your S6 to the computer, hit the Windows key and type in device manager. Try to find the phone there. Right click and go to properties. Click update driver and "choose one of the drivers already installed." See what pops up there. I had this issue with my s3, switched the driver and got access to my storage.
Sent from my SM-G925P using Tapatalk
Click to expand...
Click to collapse
Got it flashed by putting it on an sd card and using my OTG cable. Forgot I even had that thing, thanks for the suggestion!
Not a problem. Glad I could help! Those cables are a godsend for devices like ours. I'm still baffled at why they thought it was a good decision to take it out.