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

[Completed] Android Note 2 stuck on firmware encounter an issue

Hope this is the right place to be asking this question
First timer so pls excuse if i miss out anything.
I was doing an ota firmware update to my t mobile Samsung note 2 (SGH-T889) using kies 3.1. My phone was stuck on 41 percent for about an hour so i disconnected the phone thinking that it will reboot and ask me to reconnect. Well since it didnt, its been stuck on this firmware encounter an issue please selcet recovery mode in kies and try again.
I hooked it back up and now in kies it just says connecting but nothing happens.
i tried putting my phone in download mode to see if itll connect to kies and still nothing. The phone wont allow me to get into recovery mode due to this issue. Im a mac user so i even downloaded wine to use odin i downloaded all samsung drivers needed for a connection and odin cant even detect my phone. Im not sure if usb debugging is on in my phone . I cant access nothing on my phone i tried many tricks on youtube looked at xda forms i even went into tmobile and they didnt kno what to do. Im using the factory usb, i tried diff ports and just cant seem to get a good connectiong between either programs. Please helps its been 3 days without a phone..thank you

Hi,
I see you've already asked about this in the appropriate section for your device.
http://forum.xda-developers.com/note-2-tmobile/help/note-2-stuck-firmware-encounter-issue-t3217172
That's awesome! :good:
As XDA Assist is here to help navigate the site, not for support... I'll close this thread since you already found your way.
Good luck!

[Completed] HELP!!! Unbrick Xperia S (bootloader problem no flashmode)

I have a Xperia S running cm 12.1 with unlocked bootloaders TWRP installed and i tried to partition my SD card [http://forum.xda-developers.com/showthread.php?t=2584759] but clearly something went wrong and now the phone wont boot. I made a lot of research and tried everything but all the guides require to be able to boot into flashmode . My phone is dead the only sign of life is a red led when its charging which after some hours of charge will shut off. When the light is off and the phone connected on PC, the PC can recognize the device on unspecified devices (QHSUSB_DLOAD). i have installed all the needed drivers from Sony, google drivers from sdk, and adb drivers(adb wont see the device and i tried everything to do so, but nothing seem to work). I got a market for android on my pc called mobogenie that when i connect the phone it detects that a phone is connected but wont see what phone.The hardware reset buttons work but its useless in the current position. Concluding, the phone is bricked and wont open in fastboot-flashboot-bootloader-TWRP, its recognized as a device but not as "Xperia s" i got all the drivers and i want to flash the original firmware (already downloaded) to fix it. A possible problem is that the partition table is destroyed and after the flash it will hopefully be restored. The problem is not on the hardware but on software. I tried to trigger the download mode with the Samsung way (USB jig, 300k ohm ) but nothing happened as expected. Every solution i found required flash mode which is not accessible at the moment and i tried lots of things to go into fastboot(ever the rubber band trick,remove the battery etc). PLEASE help i dont know what to do, please help me flash it (i already got flashtool, Emma) or anohter solution. Thanks for the help in advance. (its my first thread in the forum, i hope to post it on the right section, i posted it here because i need the assistance of the developers i guess)

Hi,
You've asked in the correct section: http://forum.xda-developers.com/xperia-s/help/how-to-unbrick-xperia-s-lt26i-tried-t3265523/
so I'll close this thread.

[Completed] Oneplus One bootloop with Linux

Apologies if something similar has already been posted on here already. I have had a look, but can't seem to find anything.
I was trying to root my oneplus one this evening, and was following a very useful link here....
https://forums.oneplus.net/threads/like-a-boss-how-to-root-your-oneplus-one.58493/
....and got to the bit that says "sudo fastboot oem unlock" - waited a minute, and the phone rebooted showing the android and 1+ logo. But before anything else happens it turns itself off, then back on again. And continues to do this indefinitely. I can get it into fastboot mode, but not recovery. When it is in fastboot mode the pc doesn't recognise it. Something obviously isn't right, but I'm not sure what. I'm guessing something is possibly corrupt.
What I think I need to do is firstly, get the pc to recognise the phone somehow. Secondly, install a recovery on to it and thirdly, flash a rom. I've been scratching my head all night trying to work out how to get the phone recognised, and Googling like a teenager who's just discovered porn is available on the Internet.
Is there anybody out there who is familiar with Linux who can possibly walk me through what I need to get my phone working again?
Thanks for taking the time to read this, and for any help that may be offered.

XDA Visitor said:
Apologies if something similar has already been posted on here already. I have had a look, but can't seem to find anything.
I was trying to root my oneplus one this evening, and was following a very useful link here....
https://forums.oneplus.net/threads/like-a-boss-how-to-root-your-oneplus-one.58493/
....and got to the bit that says "sudo fastboot oem unlock" - waited a minute, and the phone rebooted showing the android and 1+ logo. But before anything else happens it turns itself off, then back on again. And continues to do this indefinitely. I can get it into fastboot mode, but not recovery. When it is in fastboot mode the pc doesn't recognise it. Something obviously isn't right, but I'm not sure what. I'm guessing something is possibly corrupt.
What I think I need to do is firstly, get the pc to recognise the phone somehow. Secondly, install a recovery on to it and thirdly, flash a rom. I've been scratching my head all night trying to work out how to get the phone recognised, and Googling like a teenager who's just discovered porn is available on the Internet.
Is there anybody out there who is familiar with Linux who can possibly walk me through what I need to get my phone working again?
Thanks for taking the time to read this, and for any help that may be offered.
Click to expand...
Click to collapse
Hi and welcome to XDA.
Your device has a dedicated forum here:
OnePlus One > ONE Q&A, Help & Troubleshooting
All questions regarding your device belong in the forum linked above. You'll need to create an account first so you can post in the main forums.

Question Rog Phone 5 Brick

Hello to all,
I apologize in advance for this message.
I mistakenly bricked my phone,
It was running WW-18.0840.2201.226 (Android 11).
I'm not sure if I'm going to be able to use it again, but I'm sure I'll be able to use it again in the future.
The recovery mode does not work anymore. It remains stuck on the logo.
Concerning the device manager :
In Bootloader, nothing is detected
When I test the recovery mode, it detects 'Android Composite ADB interface'.
However, the ADB commands do not work (Unauthaurized)
This is a call for help, I don't know which tutorial to look at to help me.
Do I need to get a Deep Flash Cable to restore the phone?
Excuse my English, I'm French ^^'

Hi, I'm not sure, but I think you will have to delete this POST... It doesn't respect the forum rules... That said, you can follow this link for your problem. https://forum.xda-developers.com/t/...to-unlock-bootloader-to-modify-country-cn-to- ww.4353865/não lido

Hi Rico,
If I have to delete the post I will do it, it's not a problem.
Do you think I can put this post in the topic you gave me?
I had come across it in my research but I didn't know if it needed a Deep Flash Cable
I didn't know that my problem was similar to the one in the post because I don't have a 9008 mode
B.

Balmyr said:
Hi Rico,
If I have to delete the post I will do it, it's not a problem.
Do you think I can put this post in the topic you gave me?
I had come across it in my research but I didn't know if it needed a Deep Flash Cable
I didn't know that my problem was similar to the one in the post because I don't have a 9008 mode
B.
Click to expand...
Click to collapse
There is nothing wrong with your post at all.
Do you have access to see and send Fastboot commands to the phone when on the bootloader screen? You need to get that right first and get your driver on your PC sorted. Forget ADB, that's not going to help you here.
Once you have sorted the above, doing a RAW flash following one of the guides you can find on this form with a rom version that matches your device should get you back on track.
At this stage you shouldn't need EDL or a deep flash cable before exploring the above option.
Good luck.

Hello Andrologic,
Thanks for your reply
I only have access to the Bootloader with 'Start / Restart Bootloader / Recovery Mode / Power Off'.
I bought a Deep Cable, this one detects me when I connect it to the pc, previously my other cables did not want it
So I can indeed use the Fastboot commands whereas before I couldn't

Andrologic said:
There is nothing wrong with your post at all.
Do you have access to see and send Fastboot commands to the phone when on the bootloader screen? You need to get that right first and get your driver on your PC sorted. Forget ADB, that's not going to help you here.
Once you have sorted the above, doing a RAW flash following one of the guides you can find on this form with a rom version that matches your device should get you back on track.
At this stage you shouldn't need EDL or a deep flash cable before exploring the above option.
Good luck.
Click to expand...
Click to collapse
Thank you very much Andrologic!
The phone works like magic again, I can't believe it T_T
When I should do the updates, should I reflash the phone?
It doesn't offer me any new ones even though I'm on Android 11
B.

Balmyr said:
Thank you very much Andrologic!
The phone works like magic again, I can't believe it T_T
When I should do the updates, should I reflash the phone?
It doesn't offer me any new ones even though I'm on Android 11
B.
Click to expand...
Click to collapse
Nice. No, I would suggest updating the conventional way, i.e download ROM for ASUS and let the device pick it up and flash it. If you have TWRP installed, you can flash from there too, but there is no need for that unless the first method is not working