Database Info

Help !! I cannot install a rom

Hello,
Few months ago , the power button of my nexus s had broken. I used volume rocker and I could turn on the screen.
Today I tried to flash a rom . I have done this before many times and I know the process.
After I had wiped all the data ( system , faxtory reset, cache) , I pulled off the battery.
When the phone starts it stucks on google logo , because there is no rom in it.
When I boot it into the fastboot mode , my pc cannot recognize it at all, I plug it in my pc and there is no sign that a new hardware has been installed.
I don't know what else to do. If I could get it recognized by my pc , I would be able to silve the problem.
Any suggestions on how can I fix it? Can I fix the fastboot mode problem????
Thanks for your time
I am looking forward hearing your replies...

If you don't have this installed on your PC already, you should install it and follow the directions for installing the drivers carefully. It worked for me.
P.S. this thread belongs in Q&A

Thanks for the reply but it cannot do anything. I posted here so as I can get help from developers who know more stuff than other users.

unless your thread is about ANDROID DEVELOPMENT ... IE your own ROM / KERNEL / MOD etc... it should be in q and a or general.

OP that is not how it works, posting in the Development Section because you believe the help is great there....WRONG! Sir, you will find the best help is in the proper place in the proper Threads....Please familiarize yourself with the Forum Rules on Posting. Thank You and Moved here.

When you connect your phone to your PC while it's in fastboot mode, if you haven't tried already, go to device manager (assuming your pc is running windows), there should be an unrecognized device in the list, if so you can right click on it and choose update driver, then select driver manually and navigate to the data/drivers folder where ever you have Wug's tool installed (if you don't have it installed then you should), that should properly install the drivers and allow your computer to recognize the phone, then you can use the flash stock+unroot option to repair your phone.
If you don't see any change in device manager when your phone is connected to your computer then I can't help much, maybe try a different usb port if you haven't already.
Good luck

jj_z1 said:
When you connect your phone to your PC while it's in fastboot mode, if you haven't tried already, go to device manager (assuming your pc is running windows), there should be an unrecognized device in the list, if so you can right click on it and choose update driver, then select driver manually and navigate to the data/drivers folder where ever you have Wug's tool installed (if you don't have it installed then you should), that should properly install the drivers and allow your computer to recognize the phone, then you can use the flash stock+unroot option to repair your phone.
If you don't see any change in device manager when your phone is connected to your computer then I can't help much, maybe try a different usb port if you haven't already.
Good luck
Click to expand...
Click to collapse
There are no changes when I plug in the phone, I tried all the usb ports , other pc and other new cable but nothing work.
Thanks for the reply

[Help] Google Nexus 5 might be bricked

Heya. First things first:
My Google Nexus 5 is quite... Well bricked.
I've updated CarbonROM a couple of hours ago and since then the phone's been stuck on the Google Logo, as well as starting automatically after shutting it down.
Here's some specifications:
Recovery: ClockworkMod Recovery v6.0.4.5
ROM: Carbon. The version I updated to was CARBON-KK-NIGHTLY-20140706-0428-hammerhead (Edit: For a strange reason, it didn't update to the latest version available.)
I've tried performing:
Reinstall of the same Rom
Factory reset
Following the many unbricking tutorials that require the computer to actually recognize the phone yet no "Nexus 5" appears... Actually nothing appears in devices other than my regular devices.
Phone has been already rooted (obviously) using tutorials here on XDA.
Please help :3

Almogpas said:
Heya. First things first:
My Google Nexus 5 is quite... Well bricked.
I've updated CarbonROM a couple of hours ago and since then the phone's been stuck on the Google Logo, as well as starting automatically after shutting it down.
Here's some specifications:
Recovery: ClockworkMod Recovery v6.0.4.5
ROM: Carbon. The version I updated to was CARBON-KK-NIGHTLY-20140706-0428-hammerhead
I've tried performing:
Reinstall of the same Rom
Factory reset
Following the many unbricking tutorials that require the computer to actually recognize the phone yet no "Nexus 5" appears... Actually nothing appears in devices other than my regular devices.
Phone has been already rooted (obviously) using tutorials here on XDA.
Please help :3
Click to expand...
Click to collapse
if no new devices appear in your device manager we cant yet do much for you. Get the phone recognised in fastboot or in recovery on any pc then restore stock rom or sideload new rom

bitdomo said:
if no new devices appear in your device manager we cant yet do much for you. Get the phone recognised in fastboot or in recovery on any pc then restore stock rom or sideload new rom
Click to expand...
Click to collapse
Do you think I should get a new phone or maybe take it to a professional? I just can't get the pc to recognize it even though I have the drivers installed. (Although even if the drivers weren't installed it would still recognize it...)

Almogpas said:
Do you think I should get a new phone or maybe take it to a professional? I just can't get the pc to recognize it even though I have the drivers installed. (Although even if the drivers weren't installed it would still recognize it...)
Click to expand...
Click to collapse
hmmm... try lg flashtool. Link in my signature.

Almogpas said:
Do you think I should get a new phone or maybe take it to a professional? I just can't get the pc to recognize it even though I have the drivers installed. (Although even if the drivers weren't installed it would still recognize it...)
Click to expand...
Click to collapse
Adb drivers are different when compared to mtp drivers (windows reconizes it as mtp when swtiched on) ... U need adb drivers for pc to recognize it in fastboot mode...will fetch u the link wait
http://developer.android.com/sdk/win-usb.html

doctor_droid said:
Adb drivers are different when compared to mtp drivers (windows reconizes it as mtp when swtiched on) ... U need adb drivers for pc to recognize it in fastboot mode...will fetch u the link wait
Click to expand...
Click to collapse
The main problem in all these solutions is that the phone isn't even recognized by the computer. I'm pretty sure it's the computer's problem but you may never know. Tomorrow I'm retrieving my main rig and I'll post if that rig discovers my phone. If it does, it will make me happier than Columbus discovering America. It not, it will make my wallet really sad as I will be obliged to buy a new one.

Almogpas said:
The main problem in all these solutions is that the phone isn't even recognized by the computer. I'm pretty sure it's the computer's problem but you may never know. Tomorrow I'm retrieving my main rig and I'll post if that rig discovers my phone. If it does, it will make me happier than Columbus discovering America. It not, it will make my wallet really sad as I will be obliged to buy a new one.
Click to expand...
Click to collapse
Yup if the pc is not detecting the phone best is to try wid another usb cable and a different pc... let us knw tomorrow

Did you install those libraries properly?
Freshly baked from my Nexus 5

This universal ADB driver + this ADB and Fastboot pack always does the trick for me.
When you get either ADB or Fastboot working we can help you recover the device.

USB driver problems, drivers not being kept

So after trying to find a straightforward guide for installing the USB drivers for my OPO, almost every link says to use the OnePlus One toolkit, so I followed the 'manage drivers' section of the toolkit but for some reason, whenever I come to use my phone with my PC, the drivers seem to wipe themselves out! After I've done the initial driver installation, everything works fine, but after a day or 2, when when I plug my phone in, it will show 'unknown device' or it will show 'A0001' but with an exclamation mark next to it in the device manager and my phone isn't recognized. I'm using windows 7 x64 and the original red OPO cable.
I must be doing something wrong with these drivers, does anyone have a guide for deleting old drivers and reinstalling drivers for the OPO?
Edit: Ive reinstalled them again using the toolkit guide but I dont know if they will keep again, either way, im flashing blisspop now, maybe its an issue with 5.0 stock rom or something?

donk165 said:
So after trying to find a straightforward guide for installing the USB drivers for my OPO, almost every link says to use the OnePlus One toolkit, so I followed the 'manage drivers' section of the toolkit but for some reason, whenever I come to use my phone with my PC, the drivers seem to wipe themselves out! After I've done the initial driver installation, everything works fine, but after a day or 2, when when I plug my phone in, it will show 'unknown device' or it will show 'A0001' but with an exclamation mark next to it in the device manager and my phone isn't recognized. I'm using windows 7 x64 and the original red OPO cable.
I must be doing something wrong with these drivers, does anyone have a guide for deleting old drivers and reinstalling drivers for the OPO?
Edit: Ive reinstalled them again using the toolkit guide but I dont know if they will keep again, either way, im flashing blisspop now, maybe its an issue with 5.0 stock rom or something?
Click to expand...
Click to collapse
I had similar issue with lollipop ROMs, didn't find any solution except flashing fastboot images of CMOS12 or simply downgrading to CM11S.

Mr hOaX said:
I had similar issue with lollipop ROMs, didn't find any solution except flashing fastboot images of CMOS12 or simply downgrading to CM11S.
Click to expand...
Click to collapse
Fair enough, well i'm thinking I may move back to CM11S if things don't work out on Blisspop. If I turn off USB debugging and then switch to camera (PTP) mode and then back to MTP mode, my phone then connects fine. I wanted it to connect so I could copy my Titanium backup files off the phone and onto the PC. In the end, my mate told me about Airdroid and I managed to download them through that as a ZIP file. For some reason, the titanium backup folder isn't visible from your computer, I tried copying it to the DCIM folder and it just gave me a 1kb file. I also tried a new folder called backups and it was empty when I looked on my PC, but the files were visible when using Airdroid and also when I used a file browser on my phone.
Weird stuff!

Just wanted to bump this and see if anyone has a solution or even just an explanation.
Whenever I plug my OPO into my PC (with the original cable), the device, A0001 is found but is shown in Device Manager with an exclamation point. If I then right click on it and chose uninstall, and then reconnect the phone, it will connect and work fine for MTP/PTP modes. If I put USB debugging on, the MTP doesn't always work after. But no matter what, if I shutdown my PC, and then come to connect the phone the next day etc, I have to do the uninstall of the driver then reconnect for MTP to work. Pretty frustrating!
Anyone know why the phone isn't remembered by my PC correctly? I'm on Windows 7 x64 if that means anything.

I'm moving back to stock ROM soon so I'll see then if its something to do with the unlocked bootloader or using a custom ROM. I'll report back if I have any luck

Bumping this again, its still the same on 6.0. I don't fancy moving back to stock ROM, I like CM over Cyanogen OS, but this problem is really frustrating. Every single time I connect the phone to the PC, it will come up as A0001 but with an exclamation mark next to it in Device Manager, if I right click and uninstall the driver, then reconnect the phone, it works fine then. But if I restart my PC, it does the same thing where it cant find the right driver for the phone.
Is there anything I can try to fix this?

[SOLVED] Soft bricked Z5 - Require Assistant

So, i havent been modding Android phones in a long time and when I wanted to flash MM on my Z5, i forgot that i dont have the Z5 drivers. Now, based on what i know, i did have SONY PC COMPANION installed prior to soft bricking my device, so i would assume the drivers are installed. My current situation is as follows:
-Device wont turn on, switches between RED/GREEN led with error message of "update failed, please connect to PC etc..."
-Sony pc companion doesnt seem to recognize the phone as i cant repair it
-Cannot flash FTF through as it keeps failing to flash at different points, do not know if not having the Z5 drivers play a factor here. I got the drivers from there but i do not know what to do with it as it is not .exe file, i also have the latest flashtool installed.
-I backed up my files prior to this, so i am willing to wipe everything.
Thank you, i would appreciate if i can get some assistant on this. Stupid me for making this mistake in the first place.
Regards,
Litoni

Use PC Companion repair option (marked with a red box on my screenshot).

LitoNi said:
So, i havent been modding Android phones in a long time and when I wanted to flash MM on my Z5, i forgot that i dont have the Z5 drivers. Now, based on what i know, i did have SONY PC COMPANION installed prior to soft bricking my device, so i would assume the drivers are installed. My current situation is as follows:
-Device wont turn on, switches between RED/GREEN led with error message of "update failed, please connect to PC etc..."
-Sony pc companion doesnt seem to recognize the phone as i cant repair it
-Cannot flash FTF through as it keeps failing to flash at different points, do not know if not having the Z5 drivers play a factor here. I got the drivers from there but i do not know what to do with it as it is not .exe file, i also have the latest flashtool installed.
-I backed up my files prior to this, so i am willing to wipe everything.
Thank you, i would appreciate if i can get some assistant on this. Stupid me for making this mistake in the first place.
Regards,
Litoni
Click to expand...
Click to collapse
What Windows version ?
Follow
# STEP 1 - GENERAL GUIDE
INSTALL / CHECK DRIVERS
of
http://forum.xda-developers.com/xperia-z5/general/guide-sony-xperia-z5-unlock-root-tweaks-t3298224
and (re-)boot into (newer) Windows by disabling the driver signature verification.
Log in with administrator rights,
Extract the zip-file,
there you have inf files
https://en.wikipedia.org/wiki/INF_file
https://msdn.microsoft.com/en-us/library/windows/hardware/ff549520(v=vs.85).aspx
right-click on those and choose install - so that the device drivers are installed.
Reboot (of Windows) shouldn't be necessary.
Entering Fastboot mode should still be possible, check whether it's being recognized now (via Minimal ADB and Fastboot).
Remember: in case the device goes crazy because it's not being detected upon connection - you can still turn it off via
Emergency off
(listed under "#FASTBOOT / FLASHMODE / RECOVERY / etc.")

Install the drivers that are inside flashtool.

Mr_Bartek said:
Use PC Companion repair option (marked with a red box on my screenshot).
Click to expand...
Click to collapse
As mentioned, SPCC doesn't recognize my phone. It somewhat does but doesn't give me the option to repair. There are these other screens which i think are prior to the repair page (hopefully) but i was stuck at the page when it asks me to remove the battery or skip if built in. It asks me to press ok to skip but hitting the ok button didn't do anything.
zacharias.maladroit said:
What Windows version ?
Follow
# STEP 1 - GENERAL GUIDE
INSTALL / CHECK DRIVERS
of
http://forum.xda-developers.com/xperia-z5/general/guide-sony-xperia-z5-unlock-root-tweaks-t3298224
and (re-)boot into (newer) Windows by disabling the driver signature verification.
Log in with administrator rights,
Extract the zip-file,
there you have inf files
https://en.wikipedia.org/wiki/INF_file
https://msdn.microsoft.com/en-us/library/windows/hardware/ff549520(v=vs.85).aspx
right-click on those and choose install - so that the device drivers are installed.
Reboot (of Windows) shouldn't be necessary.
Entering Fastboot mode should still be possible, check whether it's being recognized now (via Minimal ADB and Fastboot).
Remember: in case the device goes crazy because it's not being detected upon connection - you can still turn it off via
Emergency off
(listed under "#FASTBOOT / FLASHMODE / RECOVERY / etc.")
Click to expand...
Click to collapse
Thanks my desktop is running windows 10 and i know theres so many issues with it.
gm007 said:
Install the drivers that are inside flashtool.
Click to expand...
Click to collapse
The drivers from flashtool does not include any xperia Z5 series.
Thank you guys for the quick responses, I managed to reflash the .200 through flashtool without any hiccups. which is weird that it didn't work for .163 earlier. I didn't wipe anything, so after flashing .200 i updated the SDK stuff from Google SDK.exe which i think it solved some, from there I flashed .163 (MM) again and it worked. Kept all data intact, even my encrypted Class 10 SD card worked without any issues. So far so good, haven't really encountered any errors, fingers crossed :fingers-crossed: once again thank you for the quick responses.

Tab 2 not recognized by PC

I installed some cyanogen rom on my tablet and now everytime I try to plug it into my laptop or PC It says USB not recognized device descriptor request failed. I tried with 3 different cables and 3 different computers. I have samsung drivers installed. I just need to get it to connect so I can restore my tablet to stock ROM. I was trying it on my own with mobile odi n(app) and tried to flash it but it went into a loop and deleted recovery. Now the tablet does power on and works - apps crash all the time and no root available. So basically its useless and I do now know what do to... Please, someone just help me out here >.< :crying:

hi....dou have enabled android debugging? if yes go to downloading mode and flash cf auto root and recovery

ashkineeeeee said:
hi....dou have enabled android debugging? if yes go to downloading mode and flash cf auto root and recovery
Click to expand...
Click to collapse
Yes I tried to enable debugging still did not work... I can not flash it because it doesn't get recognized by any computer.

If you manage to get root, then you can use FlashFire from play store to flash the stock rom.

john99ap said:
If you manage to get root, then you can use FlashFire from play store to flash the stock rom.
Click to expand...
Click to collapse
I tried already the root app simply keeps trashing no matter what-

dionex2k said:
I installed some CyanogenMod on my tablet and now every time I try to plug it into my laptop or PC It says USB not recognized device descriptor request failed. I tried with 3 different cables and 3 different computers. I have Samsung drivers installed. I just need to get it to connect so I can restore my tablet to stock ROM. I was trying it on my own with mobile Odin(app) and tried to flash it but it went into a loop and deleted recovery. Now the tablet does power on and works - apps crash all the time and no root available. So basically it's useless and I do now know what do to... Please, someone just help me out here >.<: crying:
Click to expand...
Click to collapse
Basically, because what you get is a CyanogenMod, which does not relate to any piece of the Samsung Driver. All you need is Google USB Driver which supports almost all Android phones in the world. A thread in XDA talks about 15 seconds Google USB Driver Program for Windows which can be found somewhere in the XDA thread world.
And more here, for the problem about root access, have you tried installing a SuperSu flashable zip through your recovery yet? That should work a lot. Then, if you update your firmware using recovery without using an OTA update manually, apps may not be compatible and will crash. Reinstalling all your crashing apps from the Google Play Store should help.
Finally, if you want to update your phone through recovery, not an OTA-received ROM, please make sure not to install many apps on it, because when it crashes, you can do nothing but to reinstall it. although, all add-ons (Such as GApps, SuperSu, Xposed Framework, et cetera) need to be reinstalled so you don't lose them during a manual update, so don't delete your flashable add-on zips once you installed, you might need them forever.
Recovery is like a mobile version of Odin, use a Desktop version of Odin so you can get yourself out. A tutorial might be found somewhere on YouTube.
Hope you have a good day,
Shippo

I can't just install a new ROM or recovery - my tab does not get recognized by any PC or laptop

dionex2k said:
I can't just install a new ROM or recovery - my tab does not get recognized by any PC or laptop
Click to expand...
Click to collapse
There is a tool called Forget Windows Use Linux in which all necessary drivers come preinstalled and your tab should be recognised from your pc with no problem if it's a driver issue. Try it

Try this slide down from upper left of the screen. If the window indicates charge only, click on it. It should then offer file transfer. In order to get adb to see the tablet turn on deveper options and enable USB debug mode. Hopefully that works for you.

hello
there is something very very very very very old which is called cf autoroot
every needed is in the zip use it
regards