hi there.
maybe I am using wrong words but I cannot find any post similar to my subject.
I am on stock ICS but it is not working well - I wanted to downgrade, but it looks like it is not possible to downgrade on stock recovery. I know I have to change the recovery to sth else like ClockWork.
I know about fastboot way - and here my problems starts.
I have all the drivers, phone is visible in Device Manager while it is booten into Android. I can go into Fastboot mode BUT
when phone is in fastboot mode it is not visible in Windows Device Manager at all.
It is not a driver problem. There is no new device I can use the driver for.
I tried different computers. Win7 64bit and 32bit and WinXP 32bit
My phone does not show up on any of them.
I think it ia a problem with the bootloader - my current version is XXKL1 - as when I am in the fastboot mode my volume keys are not working, while they work perfectly well in recovery or in the OS.
Any ideas appreciated.
Cheers
My phone wasn't showing in w7 i had turn on usb debugging in settings -> developer options. I m not sure if this helps but might be worth a try
Sent from my Nexus S using Tapatalk
Thx gm'
It is not an issue for me to connect to Windows when I am booten into android.
Only when I am in fastboot mode the phone is not discovered by windows - and in fastboot mode thre is no USB debbuging - but thx anyway
..
vstar said:
Thx gm'
It is not an issue for me to connect to Windows when I am booten into android.
Only when I am in fastboot mode the phone is not discovered by windows - and in fastboot mode thre is no USB debbuging - but thx anyway
Click to expand...
Click to collapse
Know what u mean.
Windows finds u phone but not in recovery mode.
Download pdanet for android and this will solve ur problem buddy.
http://junefabrics.com
I just realize that what I done a while ago.
You don't need install pdanet app on ur phone as long u have drivers u might get some errors if u press not install but will work anyway.
Hope this will help.
Sent from my Nexus S using Tapatalk
XXK1 sounds like the baseband/radio to me. Granted I never actually looked in the bootloader for a model number. You sure that's not the radio?
What rom is on the phone now? Does it work? Are you rooted? If you got working phone with root you can flash custom recovery from inside the os. Boot directly into it via terminal or adb or any app that does it.
The volume buttons not working sounds odd and does worry me though
did you try to boot into bootloader/fastboot without being connected to any machine (holding vol up + power) to check if your volume keys work or not?
your issue might not be driver related, but you can always try if the test above was ok.
http://forum.xda-developers.com/showthread.php?t=1138755
best of luck
OK guys. I am on 4.0.3 stock. Works almost fine. This phone is unlocked but not rooted. So no chance for any other recovery but the stock one as far as I know. So I am not able to downgrade easily. Yes I can boot into fast boot without being attached to USB. Volume keys still not working here. But working in recovery mode no problem. GM no drivers will help if phone does not show in windows device menadzer at all. I have tried Linux approach but it looks phone is not being discovered there in fast boot mode as well. I have tried unbrick software - does not discover the phone.
And yes it says on fast boot screen boot loader : I9020XXK1
I have run out of ideas.
Downgrade would be best but how to put any recovery manager without root privileges
Sent from my Nexus S using XDA App
you can use ROM manager to jump back to 2.3.x
..
I am not rooted so I cannot use from manager and I do have stock recovery not clockwork so I cannot install superuser.zip
Sent from my Nexus S using XDA App
And for SuperOneClick phone needs to be visible in fastboot mode.
Sent from my Nexus S using XDA App
vstar said:
And for SuperOneClick phone needs to be visible in fastboot mode.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
for SuperOneClick phone needs to be visible in usb debugging mode.
Sorry mate but it only starts in USB Debug/Android mode - then it reboots the phone to fastboot shell and then same issue - phone is not discovered by windows hence nothing else happens.
Is there no other way of gaining root access instead of fastboot option - this would solve all my pains
Thx everyone for input
..
i suggest just follow zedomax tutorial on how to root your ics phone. He also have the download links for all the files that you will need. once your phone is rooted then you can download the old stock version of your phone.
http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/
Looks like a driver issue, when phone isn't discovered by windows in fast boot mode. (You are booting with vol up+power, right?)
Forget about any one-click-stuff etc - unlocking and cwm is the way to go. Everything else just makes troubles.
What I don't get is how you unlocked your phone without fastboot working?! That's not possible... for the moment forget about rooting - superuser isn't needed to flash stuff via fastboot/cwm.
Concentrate on getting fastboot to work. After that it's a piece of cake. Check you have drivers and fastboot set up properly on your PC.
Edit:
By this I mean following the sticky-guides, using the sdk from Google (not any downloads pretending to make it quick'n'easy. Go the official way!)
You should also give the 4.0.4-stockrom (ported from ns4g-leak) a try - it's way better than 4.0.3!
Edit: talking about this one: http://forum.xda-developers.com/showthread.php?t=1474878
OK guys - I have no idea how should I say it in different way - this is not a matter of a driver - the phone is physically not visible to the computer. There is no unknown device of anykind so I have nothing to use a driver for. It is not that fastboot command does not recognize the phone - the phone does not exists in Windows Device Manager. Looks like when phone is in fastboot mode the usb port is dead. So no chance of rooting in standard way.
And I have unlocked it as it was working before. I did realize it is not working when I tried to downgrade recently.
Election Day: I have tried 3 different cables, couple of computers and 3 different operating systems - ubuntu included. How this trick with hairdrier works? If it is a flash why does it work for everything else but not fastboot mode? Should I heat it up without cover and battery? Any specific area? Should I plug in while hot?
Thx guys.
usb working with sys booted up, but broken on bootloader?! makes no sense at all, i hope you can see that for yourself. can't be a hw-failure (then it would be broken everywhere).
have you reinstalled the driver from the sdk? the problem is on your pc, not the phone...
and forget about rooting for the moment, you don't need that to flash a rom. or are you mixing things up?!
that nonsense about heating up the phone with a hair drier was a joke, right?
..
Related
Hey, I'm having trouble getting my phone recognised in Fastboot mode. I can get to the bootloader, but Windows 7 64 bit doesn't recognise it. And -- I think this is important -- I don't see the USB Control Init/USB Control Init End messages which usually appear when it's connected. Added to that, the Vol Up/Down keys don't work in Fastboot, but they do work in recovery and when ICS is running.
I've tried most, if not all, of the guides on Fastboot with Windows 7 64 bit. Yes, I've tried using the PdaNet drivers and all that. It used to work before, even without the PdaNet drivers.
All the symptoms are:
- Vol Up/Vol Down don't work in the bootloader. They do work in stock recovery and when the OS, ICS, is running.
- No USB Init messages appear at the bottom of the bootloader screen when the phone is connected to the PC (Win7 x64).
- Not recognised even PDANet drivers. adb devices lists the device, fastboot devices doesn't list the device, and fastboot flash recovery recovery.img says <Waiting for Device>
- i9020T with ICS 4.0.3 (Stock)
Any help would be great, thanks guys/gals.
Related:
My phone fell from a desk about waist height and now the Power Button doesn't work. Trying to get Fastboot working so I can install a ROM with Volume Wake since I'm running stock.
I'm having this EXACT same problem. Someone please help!
I'm also have this issue. Any help would be great
Tom Foolery said:
I'm also have this issue. Any help would be great
Click to expand...
Click to collapse
Same issue here.
Has someone solved?
Sorry guys/gals, I didn't manage to get it resolved. I ended up getting a Galaxy Nexus.
Hello,
My phone had been experiencing a host of problems, so I formatted all partitions. (/sdcard, /system, /cache, /data, /boot)
I planned on using the "mount USB storage" to transfer a copy of CM10 to the sdcard and flash that from recovery,
but the device does not appear in my computer or device manager in windows, and Linux doesn't see it either.
In it's current state, it's soft bricked, is there anything I can do to fix it?
It now says "fastboot mode - no boot or recovery IMG", and I have no drivers to communicate with it under adb or fastboot.
Thanks,
-Max
Use this guide to recover your device.
Thanks, but my issue is that I can't install the drivers, could it be a windows 8 thing?
Everything seems to require that I enter USB debugging first, which is impossible for me now.
I think the ADB driver is impossible to install, unless I can do it over CWM, and every fastboot driver I've tried has failed too.
How did you erase everything? Was it through fastboot or CWM?
I did it through CWM. I had just recently installed Windows 8, and hadn't connected it since then so no drivers are installed.
maxmalynowsky said:
I did it through CWM. I had just recently installed Windows 8, and hadn't connected it since then so no drivers are installed.
Click to expand...
Click to collapse
In my opinion, its safer to erase everything from fastboot.
If fastboot recognizes your phone, then you can erase or install whatever you want.
If fastboot does not recognize your phone, then you can't erase it. You then need to find out why. Bad drivers, wrong folders, bad usb cable...In the meantime you phone will still work.
On my windows 7 box, under the administrator account, it took a while to set up the drivers, don't know why, but windows would not take it at first.
Maybe you can mail the phone to a xda member to get it going again...
maxmalynowsky said:
Hello,
My phone had been experiencing a host of problems, so I formatted all partitions. (/sdcard, /system, /cache, /data, /boot)
I planned on using the "mount USB storage" to transfer a copy of CM10 to the sdcard and flash that from recovery,
but the device does not appear in my computer or device manager in windows, and Linux doesn't see it either.
In it's current state, it's soft bricked, is there anything I can do to fix it?
It now says "fastboot mode - no boot or recovery IMG", and I have no drivers to communicate with it under adb or fastboot.
Thanks,
-Max
Click to expand...
Click to collapse
I am sorry to hear about your phone. You are not alone I did the exact same thing a few days ago. Don't beat yourself up I have done that enough for both of us. Through my research into this i found there a few things that you might try (I don't own a PC so I haven't yet)
To get the drivers, I read a couple people had success downloading PDANet and installing them that way. I think they are located in "legacy drivers"
From the original "root, un-root" thread for your model download the stock boot img and try to flash that using ADB
follow the instructions to un-root and start over with rooting.
I also was going to look into Wug's toolkit (in the dev section) it looks like that may be an easy option to flash a working boot and recovery img.
I hope this helps please let me know.
I gave up to quick and ordered a GNex but I'm not touching that until I get my NS4G sorted out (my faith in my abilities is shaken and I could not handle bricking a brand new phone). I will be going to a friends house tonight to use their PC and try to get my NS running. I will be back to let you known what works and what doesn't. If you try or find anything would you please post? Two heads working on this issue are better then one. Thanks and good luck.
Sent from my temp PC36100 while my Nexus is sick using Tapatalk 2
*** success ***
The solution was an easy one thanks to our developers, the hard part was finding the answer and of course, beating myself up for making the mistake in the first place. Here's what you do...
Leave your phone with the battery out for a while. Download "Wug's Nexus Toolkit" In found it in the NS4G dev section but I believe it covers all variants (not sure which you have) at the select your model and custom JB ROM download the drivers (from the actual toolkit) turn on, plug in and select flash stock img, relock boot loader, pick the stock ROM you want and press go and your phone will be flashed and reboot in under a minute. Sign in on your phone (the toolkit should auto populate your new ROM and then just follow the steps to unlock, flash and install a custom recovery then pick any ROM you want and start over.
I really hope this helps you as I'm sure you find the whole situation as stomach-churning as I did. Please PM me and let me know.
If it does work please leave a thank you or donation to the dev for creating such an awesome tool. Again, good luck hope you get your nex back online.
Sent from my Galaxy Nexus using Tapatalk 2
The Nexus Toolkit was actually my first option, it's helped me out before. I went back and tried installing the drivers using the 3 options it gives. # 3 & #2, RAW and Samsung signed drivers don't work. Option #1, the PDAnet drivers didn't work last time I tried it (all 3 options require USB debugging enabled). However, I just tried #1 again by turning on the device in CWM and that seemed to work, but I'm not sure (installation went according to the guide). However, once I tried to flash stock img, it gave me errors about not being able to reach the device in fastboot. Can you elaborate on those two steps, driver installation and flashing? As soon as I can get fastboot to recognize my device I can pretty much take it from there. BTW, I've got a i9020A and using NRT 1.6.1; and what's the significance of leaving the phone with the battery out for a while?
Mine was in the box with the battery out overnight. When I had access to a PC and plugged it in it said something at the bottom of the fastboot screen in grey that it did not before and I actually think that was the trick (System normal or system OK or something like that and when replugged to the USB the message just repeated and stacked up on the lower left of the fastboot screen). Try letting the phone sit for a while. All driver options failed for me except the tool kit.
Sent from my Galaxy Nexus using Tapatalk 2
Tried your fix, but the phone remains unable to have it's drivers installed. It's always giving "USB device not recognized" errors no matter what I do. I'm just going to shelf it and accept my loss. Thanks for the help though!
edit: Tried using some Linux tools, much greater success! This guide finally got my device listed under fastboot: http://forum.xda-developers.com/showthread.php?t=1447040
edit2: Up and running again with the android-tools-fastboot package for Linux and a standard stock image flash: http://forum.xda-developers.com/showthread.php?t=1572307
I am so glad to hear it! I stayed subscribed to the nexus s forum just to keep up on your progress and to try and help. Good for you.
Sent from my Galaxy Nexus using Tapatalk 2
I've searched the whole sight and tried a bunch of so called fixes and still when i plug in my atrix 2 in boot mode (only it boot mode it does this) all i hear is instead of the dehdo that lets u know its connected i hear duhduhduh and RSD doesnt detect my device... im trying to fxz to 2.3.5 then ota upto ICS then root but i cant do any of these because of this please help.
greatanomaly said:
I've searched the whole sight and tried a bunch of so called fixes and still when i plug in my atrix 2 in boot mode (only it boot mode it does this) all i hear is instead of the dehdo that lets u know its connected i hear duhduhduh and RSD doesnt detect my device... im trying to fxz to 2.3.5 then ota upto ICS then root but i cant do any of these because of this please help.
Click to expand...
Click to collapse
First and foremost, this belongs in the q&a section. Is your phone an MB865, an ME865, is it AT&T branded? Have you tried uninstalling then reinstalling the Motorola drivers on your PC? Tried a different USB port and/or another PC? Can you give a little more information? Awesome sound effects, by the way.lol
Sent from this thing.
1BadWolf said:
First and foremost, this belongs in the q&a section. Is your phone an MB865, an ME865, is it AT&T branded? Have you tried uninstalling then reinstalling the Motorola drivers on your PC? Tried a different USB port and/or another PC? Can you give a little more information? Awesome sound effects, by the way.lol
Sent from this thing.
Click to expand...
Click to collapse
thank u lol but im sure u can imagnine the sound an...
AT&T
MB865
and i do believe i said ive tried nearly everything that is listed on this site well other sites to...
I dont need special files for my special model phone or the fact that its at&t but if that information helps u make it connect to my pc like it does when its not in fastboot then there ya go and btw to the Q/A section they can move it...
greatanomaly said:
thank u lol but im sure u can imagnine the sound an...
AT&T
MB865
and i do believe i said ive tried nearly everything that is listed on this site well other sites to...
I dont need special files for my special model phone or the fact that its at&t but if that information helps u make it connect to my pc like it does when its not in fastboot then there ya go and btw to the Q/A section they can move it...
Click to expand...
Click to collapse
Yeah, I was kidding. This site can be too serious at times. I know you said you tried everything, but a lot of people say that and it isn't always true, especially when they ask questions on the same day they became a member. I wasn't trying to offend you or insinuate anything. I asked if you had an AT&T branded phone because I was curious as to why you wanted to flash to 2.3.5 then ota to 2.3.6 then ota again to 4.0.4 instead of using this:
http://forum.xda-developers.com/showthread.php?t=1961310
to go straight to 4.0.4?
So your PC isn't detecting your phone, but ONLY when in fastboot mode, correct? Is the phone detecting the PC? By that I mean, on my phone when I boot into fastboot mode, at first it says:
AP Fastboot Flash Mode (S)
0A.72
Battery OK
OK to Program
Connect USB
Data Cable
Then when I connect it to the PC it changes to:
AP Fastboot Flash Mode (S)
0A.72
Battery OK
OK to Program
Transfer Mode:
USB Connected
Are you at least getting that?
Sent from this thing.
stuck on boot logo
1BadWolf said:
Yeah, I was kidding. This site can be too serious at times. I know you said you tried everything, but a lot of people say that and it isn't always true, especially when they ask questions on the same day they became a member. I wasn't trying to offend you or insinuate anything. I asked if you had an AT&T branded phone because I was curious as to why you wanted to flash to 2.3.5 then ota to 2.3.6 then ota again to 4.0.4 instead of using this:
http://forum.xda-developers.com/showthread.php?t=1961310
to go straight to 4.0.4?
So your PC isn't detecting your phone, but ONLY when in fastboot mode, correct? Is the phone detecting the PC? By that I mean, on my phone when I boot into fastboot mode, at first it says:
AP Fastboot Flash Mode (S)
0A.72
Battery OK
OK to Program
Connect USB
Data Cable
Then when I connect it to the PC it changes to:
AP Fastboot Flash Mode (S)
0A.72
Battery OK
OK to Program
Transfer Mode:
USB Connected
Are you at least getting that?
Sent from this thing.
Click to expand...
Click to collapse
no sir ny fone is not showing this
it still says
Connect Usb
data cable
i stuck while i was on jbleak 4.1.2 and through SD card i flashed CM 10.1
once it worked but now it stucked on the boot logo ... it appears and gone ... and then shows black screen.
even in recovery when i tried to reinstall same zip file of CM10.1 it failed on signature verification.
please help me sir help me..!!
:crying::crying::crying::crying::crying::crying::crying::crying::crying:
Gr8mobiPro said:
no sir ny fone is not showing this
it still says
Connect Usb
data cable
i stuck while i was on jbleak 4.1.2 and through SD card i flashed CM 10.1
once it worked but now it stucked on the boot logo ... it appears and gone ... and then shows black screen.
even in recovery when i tried to reinstall same zip file of CM10.1 it failed on signature verification.
please help me sir help me..!!
:crying::crying::crying::crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
Chill man..nothing to worry about..please install motorola drivers..it should work.
its still not working
nishant203 said:
Chill man..nothing to worry about..please install motorola drivers..it should work.
Click to expand...
Click to collapse
wot motorola driver ..?? i have installed moto device manager and it is not showing any thing connected.. because it remain in boot mode..:crying::crying::crying::crying::crying::crying::crying:
Use Virtual PC
I still have the same issue. I have installed Windows 7 on VM Ware workstation i.e virtual desktop and then followed the below steps :-
-Reboot your Virtual PC
-Install Motorola drivers.
-Reboot your computer
-Install RSD Lite
-Reboot your computer
-Boot your phone into Fastboot mode
-Connect your phone to your computer using a high-quality (preferably OEM) cable.
-Let your PC install any necessary drivers. When it finishes it should tell you that the device "Fastboot Edison S" is ready for use.
-Turn your phone off, disconnect the cable
-Reboot your computer
-Boot your phone back into Fastboot mode
-Wait a couple seconds then connect your phone to your computer
-Wait a couple more seconds, then look at the bottom text that's displayed on your phone. It should say
This means that your phone is connected to your computer.
-Open up RSD Lite
-Wait a couple seconds. At the top of the list should be your phone (under model it should say "Fastboot Edison S")
-If you've done all this and everything has worked out for you, flash the fxz! Make sure to follow the instructions in the noob thread as specifically as possible
Gr8mobiPro said:
wot motorola driver ..?? i have installed moto device manager and it is not showing any thing connected.. because it remain in boot mode..:crying::crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
This seems to be happening more lately. it IS a driver issue of some sort, that is for sure. I would just use one of the scripts, or moto-fastboot manually. they do the same thing as rsd but through command line either with your own typing, or a .bat script.
This may also work better in linux, so you can try downloading a live cd/usb of ubuntu and seeing if it is recognized. no need for drives with linux, just download one of the scripts that includes the moto-fastboot utility. Let me know if you need more help.
same issue
i am having the same issue with my at&t atrix 2. it is soft bricked due to an upgrade from gb to jbleak. ap fastboot flash mode (s) oa.65 battery ok ok to program connect usb data cable same message i have installed different motorola usb driver versions. i have also soldered the 4 pin to the 1 red+5v factory usb cable
https://www.google.com/url?q=http:/...ds-cse&usg=AFQjCNE6DkvEZi41YPAYKVPqH_AlA4f4cQ
but still my pc says unable to recognize usb device. i dnt what to do any more. im in mexico and purchasing a new phone is very expensive i need help is there something any one can do i am sure my device is not completely bricked i just cant get the mofokin pc to recognize the mofokin phone in fastboot
Hi u all!
First of all thank you for your time and sorry for my english, I speak spanish.
I have a nexus s i9023. I was using CyanogenMod 11 experimental 24042014.
I was having many problems and decided to downgrade to the stable version 10.1.2
It downloaded ok, installed all the updates, rebooted and then got stuck in the logo screen when booting.
The problem is that my nexus s has a broken the power button, it doesn't work.
As for right now the olny thing I can do is to enter the bootloader screen, but cant move throgh the options with the volume keys, it's like its stuck.
If I plug in the device when in the bootloader (fastboot mode) screen my PC doesn't recognice it, I search in the device manager but it doesn't appear.
If it helps when I plug in the battery the phone starts on in it's on.
Please, any help is appreciated.
Im really sad because I love my nexus.
Thank you!!!
Same here. Any help for us would be great. Thanks.
shd128 said:
Hi u all!
First of all thank you for your time and sorry for my english, I speak spanish.
I have a nexus s i9023. I was using CyanogenMod 11 experimental 24042014.
I was having many problems and decided to downgrade to the stable version 10.1.2
It downloaded ok, installed all the updates, rebooted and then got stuck in the logo screen when booting.
The problem is that my nexus s has a broken the power button, it doesn't work.
As for right now the olny thing I can do is to enter the bootloader screen, but cant move throgh the options with the volume keys, it's like its stuck.
If I plug in the device when in the bootloader (fastboot mode) screen my PC doesn't recognice it, I search in the device manager but it doesn't appear.
If it helps when I plug in the battery the phone starts on in it's on.
Please, any help is appreciated.
Im really sad because I love my nexus.
Thank you!!!
Click to expand...
Click to collapse
kijp15 said:
Same here. Any help for us would be great. Thanks.
Click to expand...
Click to collapse
Seems like a driver issue. Can you try installing the drivers in a different system?
If it goes well, then use install cwm touch recovery from fastboot. You can take backup and flash new ROMs after that.
Try Nexus Root Toolkit to install drivers if you don't have access to a different system.
smit.sanghavi said:
Seems like a driver issue. Can you try installing the drivers in a different system?
If it goes well, then use install cwm touch recovery from fastboot. You can take backup and flash new ROMs after that.
Try Nexus Root Toolkit to install drivers if you don't have access to a different system.
Click to expand...
Click to collapse
Don't I need to have android debugging enabled? If so, I don't think Nexus Root Toolkit will work. I flashed a ROM to my NS4g & I get boot loops. I flashed the wrong Gapps a few months ago.
I was hoping there would be a way to automatically turn android debugging on. I know it may sound dumb & also probably impossible.
Any other tips.
Tell me I'm screwed. Haha.
kijp15 said:
Don't I need to have android debugging enabled? If so, I don't think Nexus Root Toolkit will work. I flashed a ROM to my NS4g & I get boot loops. I flashed the wrong Gapps a few months ago.
I was hoping there would be a way to automatically turn android debugging on. I know it may sound dumb & also probably impossible.
Any other tips.
Tell me I'm screwed. Haha.
Click to expand...
Click to collapse
I disabled USB debugging. Rebooted to bootloader. Fired up 'fastboot devices' on cmd and could see my phone. This tells me that I do not need USB debugging on fastboot.
If you see an unknown device in Device Manager while in fastboot then use Universal Naked Driver to install the drivers. But since you don't, you'll need another PC to do this stuff. Once drivers are installed, you can do a 'fastboot reboot recovery' to get into recovery and fix the the problems. The first thing I advice is to flash a touch recovery. The rest is up to you.
Flash back the original soju firmware back onto your device by first using "nexus s root toolkit v.1.8.2 by wugfresh". It may take a little of your time downloading the roms and installing the drivers but trust me it should be working and your phone will boot into stock android 4.1.2. You can then root your device and install custom recovery as normal. Anything do pm me :laugh: ps, click the bricked option one the software is loaded up and remember to connect your device only and remove other phones from your computer
Hi guys hopefully I posted this in the right place. I have a rooted Nexus 5 with multirom installed and had a few ROMs in mind that I wanted to try out, most of them just installed simply and booted without problems however when I chose to try and install slimrom or another (can't remember the name of the other ROM sorry) a message would appear stating I need to install a different bootloader IMG to install/ boot that ROM. I searched around for a while and found an image to install through twrp but when I installed it I now can't boot the phone to launch a ROM or get into recovery mode as the screen will go black. Any ideas? I'm trying to used adb to install a twrp img but so far it doesn't detect the device :/ I would much appreciate any help or suggestions! Ask me if you have any questions! Thanks.
Have tried to flashing back to a completely stock rom?
Problem is I can't get my computer to recognize my nexus 5 in the boot loader mode if I could I could then flash twrp again and flash the stock rom but it doesn't detect
Does the phone boot into fastboot mode? You tried different USB ports, cables, computers, and operating systems?
The only mode I can get my Nexus into is boot loader mode so yes fast boot. I have a windows xp and 8 so I use 8 as its the only PC that I can run adb & fast boot on without problems. I have used a USB cord the recognized my sisters phone also so it shouldn't be a faulty cable I'm pretty sure. Thanks for those ideas I appreciate your help a lot!
Rooted Droid said:
The only mode I can get my Nexus into is boot loader mode so yes fast boot. I have a windows xp and 8 so I use 8 as its the only PC that I can run adb & fast boot on without problems. I have used a USB cord the recognized my sisters phone also so it shouldn't be a faulty cable I'm pretty sure. Thanks for those ideas I appreciate your help a lot!
Click to expand...
Click to collapse
Use the cable that came with the phone.
Use this well made thread
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
I once wiped my system and rebooted and got stuck in a loop. at his thread is what I used to save my phone. Hope it helps.
Sent from my Nexus 5 using Tapatalk
Speaking from personal experience, I found that the USB cable could make a difference. I also have Samsung phones and, although the USB cable allowed win7 to install drivers, I could never flash anything. Once I switched back to the original cable, flashing works without any problems.
tahnks guys i managed to fix my problem using the nexus in bootloader mode on Windows 7 as windows 8 and xp wouldn't recognize it for some reason. From there i managed to install twrp reset the device, flash theserurection remix rom and flash a correct bootloader. Thanks for your help as it lead me in the right direction!