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.

[GUIDE] How to recover from OnePlus soft bricked?

I decided to write a guide on how to recover from a bricked OnePlus One. This is my first guide.
About me: I am a newbie on Android.However, the XDA community has taught me a lot about my Android phone for the first month of using it. That's right! I have only been using Android for less than one month so take this guide with a grain of salt. But if you happen to soft brick your One, this is the guide to turn to. I have created two mind-bending/heartbreaking/frightening scenarios that I have experienced. Though, resolved thanks to this community.
Note: This will wipe your phone!
Scenario 1:
Soft bricked, (CM gear keeps spinning but won't boot to lock screen)
Scenario 2: Updated kernel on a non-compatible firmware.
Soft bricked, screen on 1+ logo and won't boot to lock screen.
Solution:
1. Download the toolbox from: (Make sure you download your version)
http://forum.xda-developers.com/oneplus-one/development/toolbox-oneplus-one-toolbox-t2808987
2. Install the file.
3. Disconnect your OnePlus One from computer and power off your phone.
4. Go into Fastboot Mode (Volume Up + Power button) wait on vibrate
5. Plug in your OnePlus One.
6. Locate and open the OPO Toolbox.
7. Click Flash CM XNPH22R.
8. You should see command prompt open, just wait until it finishes doing it's thing.
9. Unplug and power off your phone.
10. Power ON your phone and wait until it prompts you re-setup your phone.
Congrats you have just fixed your phone from a soft brick. Simply follow the video from the link provided on step 1 to re-root your phone.
Note: If you have unlocked your bootloader, you do not need to unlock it again.
How to find out if you have unlocked bootloader:
1. Locate the folder where you installed the OPO Toolbox.
2. Hold Shift and right click on ANY white area within the folder.
3. Left click 'Open command window here'
4. Type:
fastboot oem device-info
If it returns True on tampered. Then you have unlocked your bootloader.
I hope this guide helps solve your soft-bricked problem. Good luck!

I suggest that a mod moves this to the General section

pandasa123 said:
I suggest that a mod moves this to the General section
Click to expand...
Click to collapse
Report the thread if you think its necessary.

Well I got this FAILED in the command line, and afterwards didnt got a re- setup...
what am I doing wrong here?:crying:

Digital Arm said:
Well I got this FAILED in the command line, and afterwards didnt got a re- setup...
what am I doing wrong here?:crying:
Click to expand...
Click to collapse
You don't have an unlocked bootloader.
Transmitted via Bacon

timmaaa said:
You don't have an unlocked bootloader.
Transmitted via Bacon
Click to expand...
Click to collapse
Thx got it:cyclops:

Scenario 2: Updated kernel on a non-compatible firmware.
Soft bricked, screen on 1+ logo and won't boot to lock screen.
Solution:
1. Download the toolbox from: (Make sure you download your version)
http://forum.xda-developers.com/oneplus-one/development/toolbox-oneplus-one-toolbox-t2808987
2. Install the file.
3. Disconnect your OnePlus One from computer and power off your phone.
4. Go into Fastboot Mode (Volume Up + Power button) wait on vibrate
5. Plug in your OnePlus One.
6. Locate and open the OPO Toolbox.
7. Click Flash CM XNPH22R.
8. You should see command prompt open, just wait until it finishes doing it's thing.
9. Unplug and power off your phone.
10. Power ON your phone and wait until it prompts you re-setup your phone.
Congrats you have just fixed your phone from a soft brick. Simply follow the video from the link provided on step 1 to re-root your phone.
Note: If you have unlocked your bootloader, you do not need to unlock it again.
Hi i am stuck in scenario 2...I did all a u said but i cant flash CM XNPH22R ...where do i find this file...i cant find it on my phone either ..pls help ??

Thank god for this thread omg, saved my life

Locked Bootloader
This didn't work...
My phone is Soft Bricked (oneplus logo freeze) locked bootoader and usb debuging is not enabled.
What can I do to fix it??

RiccoSuave said:
This didn't work...
My phone is Soft Bricked (oneplus logo freeze) locked bootoader and usb debuging is not enabled.
What can I do to fix it??
Click to expand...
Click to collapse
But why happened this ? Whats the last actions attempted to do with the phone before the brick?
Tecleado desde mi 1+1.

Champi12301 said:
But why happened this ? Whats the last actions attempted to do with the phone before the brick?
Tecleado desde mi 1+1.
Click to expand...
Click to collapse
I did an ota update and it went in to a boot-loop, so I went into fast-boot and accidentally locked the boot-loader.
I think I have to try to hard-brick it and try the hard-brick solution with the qualcom drivers.

RiccoSuave said:
I did an ota update and it went in to a boot-loop, so I went into fast-boot and accidentally locked the boot-loader.
I think I have to try to hard-brick it and try the hard-brick solution with the qualcom drivers.
Click to expand...
Click to collapse
Then first you need to unlock the bootloader via fastboot,but that action erases all data. I assume,if you modified the boot via fastboot, USB DEBUGGING is working,so after try to do the softbrick tutorial of the thread.
Tecleado desde mi 1+1.

how do i know which tool box version is mine ?
---------- Post added at 07:42 PM ---------- Previous post was at 07:26 PM ----------
i tried the fastboot method, i successfully run alll the commands but still stuck in the bootloop.
i even tried adb, but i cant go into recovery mode for my computer to detect it. The weird thing is i can easily go into the fastboot mode but for some reason i can go into recovery mode. i tried turning of the phone by holding power button too long and then vol down + power button, still no luck, now im stuck with 2 options,
1. the toolkit solution
2. the qualcom thingy. It's been two days without my opo, and i feel so lost ! PLS if anyone sees my comments plss respond to me PLS! i willl forever be grateful to you!

deanwinchester370 said:
how do i know which tool box version is mine ?
---------- Post added at 07:42 PM ---------- Previous post was at 07:26 PM ----------
i tried the fastboot method, i successfully run alll the commands but still stuck in the bootloop.
i even tried adb, but i cant go into recovery mode for my computer to detect it. The weird thing is i can easily go into the fastboot mode but for some reason i can go into recovery mode. i tried turning of the phone by holding power button too long and then vol down + power button, still no luck, now im stuck with 2 options,
1. the toolkit solution
2. the qualcom thingy. It's been two days without my opo, and i feel so lost ! PLS if anyone sees my comments plss respond to me PLS! i willl forever be grateful to you!
Click to expand...
Click to collapse
Did you find a solution ?
I'm facing the exact same issue on my OPO.
>> bootloader locked
>> no recovery
>> impossible to unlock the bootloader
>> OPO stuck at 1+ logo and keep rebooting agin and again and again...
....i think my OPO is dead T_T
Is it a way to force the bootloader unlock ?
Please HELP !!!

Didn't work for me
I'll give the background first as it might help. I long while back I did a manual upgrade to CM12s using the guide in this video "How to Install CM12S on OnePlus One - No Root or TWRP Required, No Data LOSS" from the oneplus exclusive Youtube channel.
It worked great no problems.
I recently I got the OTA update to CM13. There were several features I didn't like so I decided to go back. I repeated the process shown in the video but now my phone gets stuck on the CM logo screen and won't go past. I tried again but the same result. Then (I can see heads shaking, sorry) I tried a factory reset from the recovery screen, still the same goes past the 1+ logo but gets stuck at the CM logo. Then I found this guide, downloaded the toolbox but when I try to plash it says "fastboot is not recognized as an internal or external command.
Any ideas?
Found a link on one of the threads here that said a guide on Reddit was useful, that didn't work as well. I am trying.

All done
davmeva said:
I'll give the background first as it might help. I long while back I did a manual upgrade to CM12s using the guide in this video "How to Install CM12S on OnePlus One - No Root or TWRP Required, No Data LOSS" from the oneplus exclusive Youtube channel.
It worked great no problems.
I recently I got the OTA update to CM13. There were several features I didn't like so I decided to go back. I repeated the process shown in the video but now my phone gets stuck on the CM logo screen and won't go past. I tried again but the same result. Then (I can see heads shaking, sorry) I tried a factory reset from the recovery screen, still the same goes past the 1+ logo but gets stuck at the CM logo. Then I found this guide, downloaded the toolbox but when I try to plash it says "fastboot is not recognized as an internal or external command.
Any ideas?
Found a link on one of the threads here that said a guide on Reddit was useful, that didn't work as well. I am trying.
Click to expand...
Click to collapse
No one replied to this but never mind, took me two days but I now have a working phone. So you can call in the dogs, cheers

hi davmeva
did you fixed your oneplus one till now or not because i have also same situation here and no success till now .
i did by mistake all this stuff and now nothing work still same condition
if you got any solution please share it

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.

Nexus 5 HARD BRICKED ( wont come on )

i was trying to flash android L through root toolkit ( wug fresh )
but i got an errors saying max download limit ????? bytes
then i just unplugged the phone from the computer and like an idiot
and now it wont come on
when i plug it in charge it doesnt show anything aswell
Please Help how can fix ? I Bought this with my own pocket money brand new from play store for £300
:crying: :crying: :crying:

you know that the "max download size" thing is just a WARNING message, in fact a lot of phones displays it for all operations(being all operations all fastboot flash operations), on the n5 it only shows when installing recovery (afaik).
anyway, see if it really wont come on, my phone was like that, but in fact it was in qualcomm´s QD-LOADER 9008 (i had to install some drivers for it to show up on pc). if your phone does get detected(even if as an unknown device)then you have some hope, if not - too bad you are mostly screwed.
Check your device manager

opssemnik said:
in fact a lot of phones displays it for all operations(being all operations all fastboot flash operations), on the n5 it only shows when installing recovery (afaik).
Click to expand...
Click to collapse
It showed for every fastboot flash I did just a few days ago. I don't recall that warning showing up back when I flashed 4.4.4 and prior. I think it's a change with the new bootloader.

Have you tried to use Google recovery that flashes stock ROM on your device ?
I had made a very bad thing with my N5, which resulted in a bootloop, two hours after receiving the N5 and I was almost crying. Download a stock recovery from android dev site. A Nexus is unbrekable

shiva-x said:
Have you tried to use Google recovery that flashes stock ROM on your device ?
I had made a very bad thing with my N5, which resulted in a bootloop, two hours after receiving the N5 and I was almost crying. Download a stock recovery from android dev site. A Nexus is unbrekable
Click to expand...
Click to collapse
Wrong...

Google- said:
i was trying to flash android L through root toolkit ( wug fresh )
but i got an errors saying max download limit ????? bytes
then i just unplugged the phone from the computer and like an idiot
and now it wont come on
when i plug it in charge it doesnt show anything aswell
Please Help how can fix ? I Bought this with my own pocket money brand new from play store for £300
:crying: :crying: :crying:
Click to expand...
Click to collapse
Tried a forced reboot? (Power + volume down button for bout 15 seconds).
Seems like the go-to solution but I see no one asked you yet.
Do this while connected to a charger.

Also try booting into the secondary bootloader by pressing volume up , down and power simultaneous.

Noob + Toolkit = Leathal combo
Try to learn fastboot and adb so you have control over whats happening and don`t use toolkits.

gee2012 said:
Noob + Toolkit = Leathal combo
Try to learn fastboot and adb so you have control over whats happening and don`t use toolkits.
Click to expand...
Click to collapse
Agree , but it should still be salvageable - assuming the incomplete firmware didn't cause hardware damage.

Is there any solution found? I ran into the same situation. I installed CM 11S and that prompted me an error which was unable to read the binary input file. I then reinstalled the firmware and did a reboot Now, it's hard bricked. Won't boot at all.
How do I power my N5 back?

nirmal212 said:
Is there any solution found? I ran into the same situation. I installed CM 11S and that prompted me an error which was unable to read the binary input file. I then reinstalled the firmware and did a reboot Now, it's hard bricked. Won't boot at all.
How do I power my N5 back?
Click to expand...
Click to collapse
any new device showing up in the device manager when you connect your phone to your pc?

bitdomo said:
any new device showing up in the device manager when you connect your phone to your pc?
Click to expand...
Click to collapse
It's showing up as "QHSUSB_BULK". Then I tried to install the qualcomm driver. Now nothing is showing up.

nirmal212 said:
It's showing up as "QHSUSB_BULK". Then I tried to install the qualcomm driver. Now nothing is showing up.
Click to expand...
Click to collapse
press and hold volume_down+volume_up+power keys until you see it again. It should take 20-25 seconds. Try to fix the drivers (turning off dirver signature enforcement helps a lot) to show Qualcomm HSUSB QDLoader 9008 device then follow my guide here

bitdomo said:
press and hold volume_down+volume_up+power keys until you see it again. It should take 20-25 seconds. Try to fix the drivers (turning off dirver signature enforcement helps a lot) to show Qualcomm HSUSB QDLoader 9008 device then follow my guide here
Click to expand...
Click to collapse
Can I perform this action even if my device is not started? I tried all the button options and still the device won't power on.

Bootloop and unable to access fastboot or recovery mode

welcome
I wanted to install twrp for xiaomi redmi 9 global version miui 12.5.1
These were the commands I used:
1 - fastboot flash recovery twrp-3.4.2B-0108.img
2 - fastboot flash misc misc.bin
3 - fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
4 - fastboot boot twrp-3.4.2B-0108.img
After that, the device restarted but MIUI did not start again. "Redmi" appears on the screen for a few seconds then restarts again and again.
And now comes the real problem and also the reason for this post...
I cannot access recovery or fastboot mode!
I can't even turn off the device.
I can't do anything but wait for the battery to run out.
If I hold Power + VolumeUp = It keeps rebooting
If I hold Power + VolumeDown = It keeps rebooting
If I only hold Power = It keeps rebooting
If I hold all of them it stops rebooting and keeps the black screen as if it's off, but when I stop holding, the bootloop starts again.
I don't know what to do, I hope any of you can help me.
Thanks for the attention.

Re-flash Stock ROM to get rid off of all modificatins you applied so far.

jwoegerbauer said:
Re-flash Stock ROM to get rid off of all modificatins you applied so far.
Click to expand...
Click to collapse
Hello
Thanks for the quick reply
Please can you explain how this works?

It's typically done via ADB Sideload method - what of course requires USB Debugging got enabled on phone and you have the Stock ROM in .ZIP-file format on hand.

jwoegerbauer said:
It's typically done via ADB Sideload method - what of course requires USB Debugging got enabled on phone and you have the Stock ROM in .ZIP-file format on hand.
Click to expand...
Click to collapse
I cannot access recovery or fastboot mode!
I can't even turn off the device.
I can't do anything but wait for the battery to run out.

You were told to to use ADB Sideload method: This has nothing to do with Recovery mode or Fastboot mode.

jwoegerbauer said:
You were told to to use ADB Sideload method: This has nothing to do with Recovery mode or Fastboot mode.
Click to expand...
Click to collapse
Sorry to bother you and thank you
But due to my lack of experience in the field, I was unable to find a detailed explanation of the ADB Sideload process that you told me about, could you please explain how this works Steps or send a link with details or a video, please Knowing that the phone does not appear on the computer due to its continuous restart all the time I am sorry again

That's another issue you report now,
My recommendation: Take phone to authorized service center and let them try to fix it.

I already took it to fix it but no result He told me that I have to replace the motherboard and this is wrong because my problem is a problem with the phone system
jwoegerbauer said:
That's another issue you report now,
My recommendation: Take phone to authorized service center and let them try to fix it.
Click to expand...
Click to collapse

hey..I know I'm a whole year late but i have a solution!!!
reply if you still need it

vader404 said:
hey..I know I'm a whole year late but i have a solution!!!
reply if you still need it
Click to expand...
Click to collapse
hello I wanna know how you did it.

vader404 said:
hey..I know I'm a whole year late but i have a solution!!!
reply if you still need it
Click to expand...
Click to collapse
hellow whay is the solution? i got this problem too now, i have experience to unbrick some android phone, but this thing is very rare. Because it repeatedly restarting cant go to fastboot to connect to pc or to recovery mode to reformat. Thank u in advance.