Database Info

Need help. Phone has bad rom, can't access recovery

i may be up a creek now. i've tried everything i can.
here's the whole situation, maybe someone can offer some guidance on how i can get my phone back.
i installed this rom, http://forum.xda-developers.com/showthread.php?t=1835478, but did not see that there was a problem with people getting stuck at the initial google boot logo. i wouldn't have tried it if i did.
but it's too late now. so i too have that problem. in addition, i also have that problem with the nexus s in that the power button is busted, works only to boot the phone.
so i boot the phone normally, i get to that boot logo indefinitely.
i press up and power button i get to fastboot screen. for some reason the volume buttons don't work on that screen so i can't pick recovery there. only thing that works is hitting the power button and reboots the bootloader.
i plug the phone into my pc and i can't access it through adb, fastboot... does not recognize a device is connected.
so in summary, all i can do is access the fastboot screen or the boot logo screen.
if someone can help me figure out how to do one of the following: boot into recovery instead of fastboot, figure out how to use the volume buttons in fastboot, or get the phone recognized by my pc so i can use adb, that would be awesome.
i feel like i just bricked it for good....
thanks

Install the SDK. Launch it. Find the drivers to download in the SDK. Install them. Boot the phone into fastboot and connect it to pc. Open up a command prompt IN the directory that has fastboot in it. Type in the command prompt fastboot devices.
If your serial number shoes your good to go. Get the .img of your custom recovery and type fastboot flash recovery nameofile.img. with that being the exact file name ( hint type the first letter of the recovery and hit tab)

Yep, you gotta get fastboot working again. It's pretty important.
Sent from my Nexus S 4G using xda premium

i've had the sdk/driver installed already.
like i said, the phone when it boots is not being recognized by the laptop at all, as if it's not even plugged in. so when i do fastboot devices, nothing shows up.

Was it recognized prior?
Sent from my Nexus 7 using Tapatalk 2

in the prior rom it was recognized by the laptop, before i tried to flash the rom i linked above that created this mess...

albundy2010 said:
Install the SDK. Launch it. Find the drivers to download in the SDK. Install them. Boot the phone into fastboot and connect it to pc. Open up a command prompt IN the directory that has fastboot in it. Type in the command prompt fastboot devices.
If your serial number shoes your good to go. Get the .img of your custom recovery and type fastboot flash recovery nameofile.img. with that being the exact file name ( hint type the first letter of the recovery and hit tab)
Click to expand...
Click to collapse
AlphaEchoViktorSierra said:
Yep, you gotta get fastboot working again. It's pretty important.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Yep fastboot is a great tool, if you have a nexus s then you MUST get it working!
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
wookietv said:
i've had the sdk/driver installed already.
like i said, the phone when it boots is not being recognized by the laptop at all, as if it's not even plugged in. so when i do fastboot devices, nothing shows up.
Click to expand...
Click to collapse
Seems like your nexus s drivers are not installed in your laptop
google the nexus s usb drivers download them and put in the respective folder
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
albundy2010 said:
Was it recognized prior?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
was gonna ask the same question

like i said, i already had the sdk and drivers installed.
they worked fine before i installed that rom.
this definitely seems like it's on the fault of the phone, not the laptop.

looks like you got busted like a SIR!!
Just kidding man dont take it seriously...
I might sound silly but i hope you have tried this but if you have not then do try
Go here and try changing the usb plugs
http://forum.xda-developers.com/showthread.php?t=1785672
IT shows flashboot steps, you need to connect phone in bootloader mode which you are achieving atm, and see if it works
and if it doesnt then let me know i will try to help out more if i could
P.S I am also new in android so pardon my noobnes

i went another route...
i figured i had nothing to lose at this point... so i ripped the phone apart and attempted to fix the power button, which i believed in turn would fix not being able to use the volume keys in the fastboot screen.
i was correct. i jiggled with the power button inside and it seemed to work. the volume keys now reacted in the fastboot screen.
i was able to then get into recovery, wipe the phone, connect the phone to the laptop and put a new rom on it.
i'm not sure if its fixed the button completely, but at least i can get into the new rom :laugh:

well thats a relief and i am glad that you problem is solved
a little advice, get repaired that power button for good so that you have no hassle in near future

converse5 said:
well thats a relief and i am glad that you problem is solved
a little advice, get repaired that power button for good so that you have no hassle in near future
Click to expand...
Click to collapse
+1, I agree with you. It does not cost much as well. I had this problem and was managing with apps. But finally got it replaced for good.

"Key Driver Not Found.. " on Bootloader 4.2.1

So this morning my brother was using his TF300T in its dock. He undocked it and the screen went blank. Screen was still on but nothing displayed. I rebooted it for him (volume down and power button for 10s). After a minute of it powered on the screen went blank again, so I rebooted it again, but this time the Asus splash screen displays and the lock screen flickers before quickly going blank.
Thought a reinstall of the ROM would fix the problem but I now can't even boot into recovery or fastboot! Had no problem the first time I rebooted and selected cold-boot in the bootloader options. With the tablet on and screen blank I plugged it into a PC and Win7 detected and installed the proper drivers (I think). ADB commands seem to work, but the command to boot into bootloader only resets the tablet. Fastboot command does not work. Also noticed the below message flash before a flicker of bootloader options are shown. The PC seems to have access to the internal storage (I can see folders from the tablet) when plugged in via USB.
"Key driver not found.. Booting OS
Android cardhu-user bootloader <2.00 e> released by "US_ePad-10.6.1.8-20130PPt" A03"
Could it be a hardware issue? I ask because I see similar problems with the Asus splash screen indicative of a logic board problem when diagnosing a PC (images pixelated)...

MaMMiTs said:
So this morning my brother was using his TF300T in its dock. He undocked it and the screen went blank. Screen was still on but nothing displayed. I rebooted it for him (volume down and power button for 10s). After a minute of it powered on the screen went blank again, so I rebooted it again, but this time the Asus splash screen displays and the lock screen flickers before quickly going blank.
Thought a reinstall of the ROM would fix the problem but I now can't even boot into recovery or fastboot! Had no problem the first time I rebooted and selected cold-boot in the bootloader options. With the tablet on and screen blank I plugged it into a PC and Win7 detected and installed the proper drivers (I think). ADB commands seem to work, but the command to boot into bootloader only resets the tablet. Fastboot command does not work. Also noticed the below message flash before a flicker of bootloader options are shown. The PC seems to have access to the internal storage (I can see folders from the tablet) when plugged in via USB.
"Key driver not found.. Booting OS
Android cardhu-user bootloader <2.00 e> released by "US_ePad-10.6.1.8-20130PPt" A03"
Could it be a hardware issue? I ask because I see similar problems with the Asus splash screen indicative of a logic board problem when diagnosing a PC (images pixelated)...
Click to expand...
Click to collapse
It is unlikely windows installed the proper drivers for adb and fastboot. The drivers for accessing the internal sdcard yes.
See my signature for installing proper drivers in windows 7 and another for entering the bootloader after you have the proper drivers.
When I have seen that message it does not relate to hardware but software.
I don't suggest plugging and unplugging the dock when powered.

tobdaryl said:
It is unlikely windows installed the proper drivers for adb and fastboot. The drivers for accessing the internal sdcard yes.
See my signature for installing proper drivers in windows 7 and another for entering the bootloader after you have the proper drivers.
When I have seen that message it does not relate to hardware but software.
I don't suggest plugging and unplugging the dock when powered.
Click to expand...
Click to collapse
Will try what you suggested, but does it matter that I'm using the same PC I used to initially fastboot TWRP to the tablet? I thought once the driver is installed it there would be no need to re-install the driver...

MaMMiTs said:
Will try what you suggested, but does it matter that I'm using the same PC I used to initially fastboot TWRP to the tablet? I thought once the driver is installed it there would be no need to re-install the driver...
Click to expand...
Click to collapse
It will probably be ok. I was going by your comment "I plugged it into a PC and Win7 detected and installed the proper drivers (I think)"

tobdaryl said:
It will probably be ok. I was going by your comment "I plugged it into a PC and Win7 detected and installed the proper drivers (I think)"
Click to expand...
Click to collapse
Yeah. My problem is I can't get to fastboot mode on the tablet itself, and based on what I saw on another thread it seems like I'm going to have to replace the mainboard .

MaMMiTs said:
Yeah. My problem is I can't get to fastboot mode on the tablet itself, and based on what I saw on another thread it seems like I'm going to have to replace the mainboard .
Click to expand...
Click to collapse
OK.
Good Luck!

I unplug mine and reconnect all the time when on. Never had a issue.
Sent from magical jelly bean.

My brother's TF300T is back up and running!
As a last resort I opened it up to disconnect the battery. Still could not get into fastboot, so I left the battery plugged in and let the battery run out. After 48 hours of the battery being completely dead I charged it fully to see if I could do anything. Battery LED indicator was green and the first thing I noticed was that the unit was still off. (I wasn't able to completely shut it down before letting the battery completely drain). I powered it on thinking it would display a blank screen, but it powered up as usual! Everything seems to be working. I immediately flashed CROMI-X 4.3b6 on it (what my brother originally wanted me to do).
Thought I'd post this as a last resort hope for those who think they may have bricked their machine. I do recall completely draining the battery then waiting over 24 hours as a solution for one of the many machines I've hacked. Just thought disconnecting the battery would achieve the same purpose. Guess I was wrong . Hopefully this is a solution for someone else out there who may have bricked their machine. Sure doesn't hurt to try .
I'm actually mystified as to why this worked. Anyone know? I'm guessing completely draining the battery reset whatever was inside. I also have noticed more users have reportedly bricked their machines after Android 4.2.1. Coincidental? Thank God I'm perfectly happy with Android 4.1.1 based CROMI v3.4.6 .

[Q] Hard Bricked my Nexus, possibly?

After flashing a nightly of CM10.2, my phone never booted and instead got stuck in fastboot. My power button has also been broken for months, so it's impossible to navigate the menus in the fastboot ui. When I take my battery out, it automatically boots into fastboot on its own.
Additionally, I found a way to boot into recovery without a power button, but the device is not being recognized as plugged in by my computer.
Any help??? It'd be greatly appreciated, I'm without a phone until I can find a way to fix this.

sinaisinai43 said:
After flashing a nightly of CM10.2, my phone never booted and instead got stuck in fastboot. My power button has also been broken for months, so it's impossible to navigate the menus in the fastboot ui. When I take my battery out, it automatically boots into fastboot on its own.
Additionally, I found a way to boot into recovery without a power button, but the device is not being recognized as plugged in by my computer.
Any help??? It'd be greatly appreciated, I'm without a phone until I can find a way to fix this.
Click to expand...
Click to collapse
I'm having the same exact issue, except with SlimBean 4.3. My phone is stuck in Fastboot (and says "FASTBOOT - NO BOOT OR RECOVERY IMG") and my phone will charge but can't be detected by *any* computer. I've tried three Windows 7 PCs of different makes and an Ubuntu 13.04 box and three different USB cables that all connect my other phone and my tablet fine - none can see it. (It was connecting fine to PC including being seen by ADB prior to this)
My power button is working, but it is also automatically booting into fastboot on its own when I plug it into the computer. Any of the options (besides "Power Off", which performs as advertised) just brings it back to Fastboot.
When I say can't be detected by a computer, I mean there is no USBDeview device listed and there is no 'connect' or 'disconnect' sound on the PC. ADB can't see it.

Yeah, it's strange. Did you find a solution yet, by chance?

sinaisinai43 said:
Yeah, it's strange. Did you find a solution yet, by chance?
Click to expand...
Click to collapse
Nothing yet. Thinking of buying an phone with a busted screen or something and swapping out the internals... I think it's PROBABLY the NAND chip. What I'm suspecting is that because there are several versions of the Nexus S, we might have used the wrong images. I have no idea if this is correct, but it's the only thing I can think of.
My phone's sticker says i9020 on the inside, but D720 (or whatever) when I look up the EIN.

Just hoping somebody sees this and offers a suggestion... I'm getting ready to buy a refurb and put the 'new' body over it so at least I have a functioning, new-ish phone.

Oneplus One Dead

Hey guys. I'm kinda desperated so let's see if there is anything else I can do.
I was playing a game on my phone and it started rebooting alone.
At this point, I long pressed the power button, don't ask me why, but I did it. and bang. it is dead. No boot, no loading, nothing. It still vibrates when I try to turn it on.
I had 30% Battery left.
I have root and my phone for 3 months.
I had Nandroid backup.
Long press power button, volume up + power, volume down + power doesn't work.
When connected to PC, I get the QHSUSB_BULK device on.
Tried to ColorOS Method but:
I cannot install ColorOS drivers cause it doesn't detect them.
I tried Qualcomm drivers and they worked, so then I used the program Msm8974DownloadTool to install ColorOS.
It went okay, all finished and I got the green letters in the end.
Still doesn't boot up, nothing changed.
I cannot detect my phone via ADB. Tried with the drivers and without the drivers and with clean drivers.
What can I do? I always had such care for my phone in case of an emergency, but for some weird reason this happened. I wasn't even messing up with the phone, it just died cause I turned it off while booting up?

Okay so, for some reason, I managed to get my phone on fastboot.
I used this guide http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
To reset my phone.
and the phone did all the new loadings and installs ETC....in the end?
My phone still doesn't boot.
Like wow?...

cyldman said:
Okay so, for some reason, I managed to get my phone on fastboot.
I used this guide http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
To reset my phone.
and the phone did all the new loadings and installs ETC....in the end?
My phone still doesn't boot.
Like wow?...
Click to expand...
Click to collapse
I'm sorry I can't help but one bad move was probably resetting back to stock because now you lost your root and adb access..

jukiewalsh said:
I'm sorry I can't help but one bad move was probably resetting back to stock because now you lost your root and adb access..
Click to expand...
Click to collapse
What do you mean I lost my adb access? I can still find my phone there and it's still working. (aparrently)
I tried to use the command "fastboot reboot" and while it turns off the device from windows, it still doesn't boot back up.

cyldman said:
What do you mean I lost my adb access? I can still find my phone there and its still working. (aparrently)
I tried to use the command "fastboot reboot" and while it turns off the device from windows, it still doesnt boot back up.
Click to expand...
Click to collapse
Disregard that then, when the phone is booted you have to manually give adb access but you're right when it's in recovery or other modes it's already there.
Does your screen power on at all? Do you think your LCD/digitizer could've somehow just died on you?

I highly doubt it, it happened when I shut off the phone when it was rebooting. I dont hear anything when I turn on the phone and i cant press anything or slide to unlock. nothing. so ....yeah. Weird stuff is that I did fastboot reboot and now i can't get to fastboot again. sigh.

Read this thread:
http://forum.xda-developers.com/oneplus-one/help/wrong-kernel-black-screen-fastboot-adb-t2835696
Somewhere within it is the solution to your QHSUSB_BULK problem.

Already did bro, and I fixed it, did you even read my full post? I managed to install colorOS, but it's still not booting up.

Hello guys! Last update! My phone was not even vibratting when i pressed power button. I put it to charge and finnaly I got a screen. its not what I wanted...but its a small step!
Its the Low battery charge icon! So...I've heard about this other issue about the phone not charging. Could this be it? I will be trying some techniques like https://forums.oneplus.net/threads/...een-opo-not-booting-due-over-discharge.88107/.
Hopefully it will help, but it may take some days.

[Q] My One is not booting at all, and does not react when i try to charge it

If i just use my charger, there is no response from the phone. When i try with the laptop, my laptop makes a sound to show that the phone has been plugged in, but the phone does not respond at all. I had a cm12 nightly flashed, and tried to flash Francos kernel on it, which made the phone get stuck on that blue alien logo when booting. After trying various fixes with no results, i just wiped everything ( i had no backups because i am a stupid ****) and then it got stuck on the Oneplus One logo. Now i am trying this http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541[1] and while i used the flash all.bat file, i noticed that cmd just kept showing waiting for device response (or something like that) which was weird, since it had completed some of the previous actions. Then i looked at my phone, with nothing at the screen. And it is now that it does not boot at all (not into the recovery, fast boot, normally, nothing) and does not show anything while i try to charge. What can i do?
Before the cmd process, the phone was showing up as a unit under Computer, but it is not anymore.
Just before, when i plugged it in, windows showed that something had been connected, but it did not know what, so i assume that there are some driver issues or something, though i have installed the qpst driver.
I also made a reddit post about it, where i got some response, but i could not go through with those either https://www.reddit.com/r/oneplus/comments/3bzwel/my_one_is_not_booting_at_all_and_does_not_react/
Do you know what i am doing wrong? Got any other fixes? Thanks in advance.

One get a otg cable then flash any custom rom using ur pen drive or go to adb and connect ur phone and check in device manager if it shows ur phone there or install any adb driver the try that flashall.bat it will surely work!! But I would say get a otg cable
Transmitted via Bacon

alan2500 said:
If i just use my charger, there is no response from the phone. When i try with the laptop, my laptop makes a sound to show that the phone has been plugged in, but the phone does not respond at all. I had a cm12 nightly flashed, and tried to flash Francos kernel on it, which made the phone get stuck on that blue alien logo when booting. After trying various fixes with no results, i just wiped everything ( i had no backups because i am a stupid ****) and then it got stuck on the Oneplus One logo. Now i am trying this http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541[1] and while i used the flash all.bat file, i noticed that cmd just kept showing waiting for device response (or something like that) which was weird, since it had completed some of the previous actions. Then i looked at my phone, with nothing at the screen. And it is now that it does not boot at all (not into the recovery, fast boot, normally, nothing) and does not show anything while i try to charge. What can i do?
Before the cmd process, the phone was showing up as a unit under Computer, but it is not anymore.
Just before, when i plugged it in, windows showed that something had been connected, but it did not know what, so i assume that there are some driver issues or something, though i have installed the qpst driver.
I also made a reddit post about it, where i got some response, but i could not go through with those either https://www.reddit.com/r/oneplus/comments/3bzwel/my_one_is_not_booting_at_all_and_does_not_react/
Do you know what i am doing wrong? Got any other fixes? Thanks in advance.
Click to expand...
Click to collapse
Go here:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
yashshan said:
One get a otg cable then flash any custom rom using ur pen drive or go to adb and connect ur phone and check in device manager if it shows ur phone there or install any adb driver the try that flashall.bat it will surely work!! But I would say get a otg cable
Transmitted via Bacon
Click to expand...
Click to collapse
That won't work, the phone isn't turning on.

Heisenberg said:
Go here:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
That won't work, the phone isn't turning on.
Click to expand...
Click to collapse
Thanks a lot, i dont know how i did not come upon that link while trying various fixes, now i can boot the phone again

Heisenberg said:
Go here:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
That won't work, the phone isn't turning on.
Click to expand...
Click to collapse
Uh, new problem, i used the toolkit to unlock the bootloader, and i had to use the Ultimate Tool kit to get TWRP on it. When i connect the phone to the pc (windows 7) i keep getting a message saying i have to format the phone before i can use it. When i click that, it says its writing protected. When i boot up the phone, it turns on, and i can go to the home screen (some times) but after a few seconds, it just turns off it self. Sorry for asking for your help again, but do you know of this problem? Google just came up with results for people with battery problems.

Heisenberg said:
Go here:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
That won't work, the phone isn't turning on.
Click to expand...
Click to collapse
I am just going to message you again before i mess up my phone even more, after a lot of hassle, i messed something up and redid the guide in the link you sended to me. According to the Oneplus one toolkit, my bootloader is unlocked. I can not enter fastboot, so i can not get a custom recovery or root. I can not turn on the phone normally either. I can Volume up+power button though, which takes me to the ColorOS RECOVERY screen. I would appreciate your help.

alan2500 said:
I am just going to message you again before i mess up my phone even more, after a lot of hassle, i messed something up and redid the guide in the link you sended to me. According to the Oneplus one toolkit, my bootloader is unlocked. I can not enter fastboot, so i can not get a custom recovery or root. I can not turn on the phone normally either. I can Volume up+power button though, which takes me to the ColorOS RECOVERY screen. I would appreciate your help.
Click to expand...
Click to collapse
Get rid of the toolkit,they're nothing but trouble. Plus, you don't need it. Plus, they allow you to bypass some very crucial learning experience. Power + volume up should take you to fastboot, not recovery, the button combo for recovery is power + volume down. Are you sure you can't get into fastboot? Is adb working in ColorOS recovery?

Heisenberg said:
Get rid of the toolkit,they're nothing but trouble. Plus, you don't need it. Plus, they allow you to bypass some very crucial learning experience. Power + volume up should take you to fastboot, not recovery, the button combo for recovery is power + volume down. Are you sure you can't get into fastboot? Is adb working in ColorOS recovery?
Click to expand...
Click to collapse
Oh brainfart, yup, its volume down+power that goes to the recovery. I just tried volume up+power, and now it goes into fastboot. I did try before, and the vibration was there, but no text on the screen. Not sure what to say about adb, when i launch adb.exe the CMD window just opens up, types a bunch in so fast that i cant read it, and then it closes down. It does the same thing when my phone is not plugged in, so i assume it does not work.

alan2500 said:
Oh brainfart, yup, its volume down+power that goes to the recovery. I just tried volume up+power, and now it goes into fastboot. I did try before, and the vibration was there, but no text on the screen. Not sure what to say about adb, when i launch adb.exe the CMD window just opens up, types a bunch in so fast that i cant read it, and then it closes down. It does the same thing when my phone is not plugged in, so i assume it does not work.
Click to expand...
Click to collapse
Ok, you're not meant to launch adb.exe like that though. You go to the folder where adb.exe is located, then hold shift and right click the mouse, and select "open command prompt here" from the menu, then you can issue adb commands. The same process goes for using fastboot. Anyway, now that you have access to fastboot all you should need to do is flash the stock images, go to section 8 of my guide thread for instructions:
http://forum.xda-developers.com/showthread.php?t=2839471

Heisenberg said:
Ok, you're not meant to launch adb.exe like that though. You go to the folder where adb.exe is located, then hold shift and right click the mouse, and select "open command prompt here" from the menu, then you can issue adb commands. The same process goes for using fastboot. Anyway, now that you have access to fastboot all you should need to do is flash the stock images, go to section 8 of my guide thread for instructions:
http://forum.xda-developers.com/showthread.php?t=2839471
Click to expand...
Click to collapse
Thanks a bunch, i got through it this time lol. So just to be sure that i do not end up bricking my phone again, can i just install TWRP, root, then dirty flash the latest CM nightly? I have no idea whats best to go with, and other than long battery life and good performance, i do not really have any needs, so i am thinking the latest cm will be fine. It was a nightly i was running before i bricked the phone actually.

alan2500 said:
Thanks a bunch, i got through it this time lol. So just to be sure that i do not end up bricking my phone again, can i just install TWRP, root, then dirty flash the latest CM nightly? I have no idea whats best to go with, and other than long battery life and good performance, i do not really have any needs, so i am thinking the latest cm will be fine. It was a nightly i was running before i bricked the phone actually.
Click to expand...
Click to collapse
Don't dirty flash, clean flash. Try out the Exodus ROM, great battery life and great features too.