Database Info

[Q] I can't boot into recovery mode after rooting

Hey all,
I used the "root your phone with Ubuntu" guide from the Nexus S Development forum, and then did a "fastboot oem lock" but when I try to reboot into recovery mode, the phone just sticks at the Google logo. I never see the /!\ icon to proceed further to install the 2.3.2 update manually.
I tried an "adb reboot recovery" to see if that would get me into recovery, but no luck there either, it just sits at the Google logo.
I have to remove the battery in order to boot the phone properly.
I'm curious how to proceed.

cormyn said:
Hey all,
I used the "root your phone with Ubuntu" guide from the Nexus S Development forum, and then did a "fastboot oem lock" but when I try to reboot into recovery mode, the phone just sticks at the Google logo. I never see the /!\ icon to proceed further to install the 2.3.2 update manually.
I tried an "adb reboot recovery" to see if that would get me into recovery, but no luck there either, it just sits at the Google logo.
I have to remove the battery in order to boot the phone properly.
I'm curious how to proceed.
Click to expand...
Click to collapse
you need to flash a recovery via fastboot.
Download the clockwork recovery recovery-clockwork-3.0.0.0-crespo.img image, and save it to the ..\android-sdk-windows\tools directory
renamed it to recovery.img
then type...
fastboot flash recovery recovery.img
and hit enter
Click to expand...
Click to collapse

simms22 said:
you need to flash a recovery via fastboot.
Click to expand...
Click to collapse
There's a new version of CWM to flash...that one you're linking is causing issues to people trying to apply updates. CWM is now 3.0.0.5
http://koush.tandtgaming.com/recoveries/recovery-clockwork-3.0.0.5-crespo.img

distortedloop said:
There's a new version of CWM to flash...that one you're linking is causing issues to people trying to apply updates. CWM is now 3.0.0.5
http://koush.tandtgaming.com/recoveries/recovery-clockwork-3.0.0.5-crespo.img
Click to expand...
Click to collapse
fixed it, thanks!

simms22 said:
you need to flash a recovery via fastboot.
Click to expand...
Click to collapse
Huh, I thought the recovery reset itself... Thanks for the info.

Ah, drag, I had already locked my nexus back up, and unlocking it is going to wipe the phone all over again.
I think if I'm going to wipe my phone anyway, I'll just wipe it back to factory and leave the phone unrooted... Too much hassle with the internal SD getting wiped every time.

cormyn said:
Huh, I thought the recovery reset itself... Thanks for the info.
Click to expand...
Click to collapse
Only after a successful reboot to the normal system, and only if you're on 2.3.1 or greater, and only if you've not renamed the /etc/install-recovery.sh file.
cormyn said:
Ah, drag, I had already locked my nexus back up, and unlocking it is going to wipe the phone all over again.
I think I'm just going to unroot my phone. Too much hassle with the internal SD getting wiped every time.
Click to expand...
Click to collapse
Yeah, that sucks. I don't relock my bootloader.

Incidentally, I had flashed a recovery, it was called recovery-clockwork-herring.img as suggested in the original "root your nexus s with ubuntu" guide. Maybe someone should tell that author to suggest a newer/better recovery.

cormyn said:
Incidentally, I had flashed a recovery, it was called recovery-clockwork-herring.img as suggested in the original "root your nexus s with ubuntu" guide. Maybe someone should tell that author to suggest a newer/better recovery.
Click to expand...
Click to collapse
Use this one: http://koush.tandtgaming.com/recoveries/recovery-clockwork-3.0.0.5-crespo.img

Thanks for the info, distortedloop. I think I'm just going to factory wipe and leave my phone unrooted for a while.
... assuming of course that a factory reset will get me back to a place where I can install OTA updates, or a recovery mode where I can manually install update.zip files?

distortedloop said:
Use this one: http://koush.tandtgaming.com/recoveries/recovery-clockwork-3.0.0.5-crespo.img
Click to expand...
Click to collapse
i was using the older CW recovery 3.0.0.0 also, so i just decided to flash version 3.0.0.5. since im at work, i cant fastboot it to my phone. i did it via the terminal emulator on my phone. 1st time i got a bunch of out of space errors so i booted into recovery just to check, and it was gone. nothing there. so i rebooted and tried it again via terminal. 2nd time was a success. to flash the recovery in the terminal emulator, download the recovery and put it on the root of your sd card and rename it recovery.img . now open the terminal and type...
su(press enter)
flash_image recovery /sdcard/recovery.img(press enter)
reboot recovery(press enter)

well, apparently a factory wipe was a bad move, 'cause now the phone rebooted and is stuck at the Google logo, like it's trying to get back into the recovery.

cormyn said:
Thanks for the info, distortedloop. I think I'm just going to factory wipe and leave my phone unrooted for a while.
... assuming of course that a factory reset will get me back to a place where I can install OTA updates, or a recovery mode where I can manually install update.zip files?
Click to expand...
Click to collapse
Factory reset won't remover the su binary and symlinks it makes. Factory reset only wipes the /data partition, not the /system one.
An oem lock, then oem unlock might, but I'm not sure...that definitely wipes the sdcard, though, unlike a factory reset does, so back that up first!
There's some thread on here someplace about how to completely remove root.

Pulled the battery, went back into bootloader mode, did a 'fastboot oem unlock', then flashed the crespo 3.0.5 img, and then 'fastboot oem lock' and the phone reboots properly.
Thanks again!

[Q] Stuck in "FASTBOOT MODE - NO BOOT OR RECOVERY IMG"

My NExus S is stuck on the screen that says:
Fastboot Mode No Boot or Recovery IMg.
Product Name - Herring
HW Version - Rev34
Bootloader Version - D720SPRKC5
Baseband Version - D720SPRLCI
Carrier Inro - SPR
Serial Number 32300E25C33500EC
Lock State - Locked
options to select
Reboot Bootloader (gives me exact same screen) except it only says "Fastboot"
Reboot Back to the "FASTBOOT MODE - NO BOOT OR RECOVERY IMG"
Recovery (Can boot to CWM but I can't mount anything)
Power OFF (That works fine)
Then the little green man and the android logo
Followed by USB Control INIT
USB Control INIT End
STANDARD_SET_CONFIGURATION
Conventional wisdom says download some files and fix via fastboot. However in fastbootI can't run ANY of the steps without running FASTBOOT OEM UNLOCK. When I run it my phone asks if I really want to unlock the bootloader. when I choose YEs and hit power it just freezes there.
My next thought Boot to recovery and restore. A restore through recovery followed by a reboot leads me back to the original no boot or recovery img.
Okay I'll just sideload a working rom by mounting usb storage. Then I can flash it with CWM and be up and running.
but when I try to do mount the USB Storage I get "E:Unable to write to ums 1unfile (No such file or directory)"
Finally, Last ditch Effort, I'll load up ODIN and use that to put on a working recovery. there's forums all over the place explaining how to do that right? Well yes, but the links to the Tar file are all broken.
What next my friends? I'd really like to get this phone working.

Wug's Nexus Root Toolkit.

ej8989 said:
Wug's Nexus Root Toolkit.
Click to expand...
Click to collapse
I tried doing the Flash stock + unroot in wug's kit but no luc. any other ideas?

swing4thefence said:
I tried doing the Flash stock + unroot in wug's kit but no luc. any other ideas?
Click to expand...
Click to collapse
Your bootloader is LOCKED. You must first UNLOCK the bootloader by clicking "Unlock" on Nexus Root Toolkit.

ej8989 said:
Your bootloader is LOCKED. You must first UNLOCK the bootloader by clicking "Unlock" on Nexus Root Toolkit.
Click to expand...
Click to collapse
No matter how I try to do it, it always freezes at the unlock bootloader step.

Did you install proper drivers?

ej8989 said:
Did you install proper drivers?
Click to expand...
Click to collapse
I thought so. My wife is on the computer so if she ever gives it back I'll re-install the drivers and try again.

swing4thefence said:
I thought so. My wife is on the computer so if she ever gives it back I'll re-install the drivers and try again.
Click to expand...
Click to collapse
Reinstalled Drivers. Still no luck.

I have the same problem.

Same situation for me, because i pressed "Reboot" in CWM without having flashed a Rom (stupid ). Broken power button, hanging on Google logo or in Fastboot mode.
I hope RTK will help me :good: :laugh:
Edit: I have no idea how to revive my Nexus S. Status: Broken Power button, Bootloop, can access Fastbood Mode but dont select someting, Bootloader unlocked, RTK doesn´t find any devices in Fastboot Mode, Device is rooted and has CWM

!Lür said:
Same situation for me, because i pressed "Reboot" in CWM without having flashed a Rom (stupid ). Broken power button, hanging on Google logo or in Fastboot mode.
I hope RTK will help me :good: :laugh:
Edit: I have no idea how to revive my Nexus S. Status: Broken Power button, Bootloop, can access Fastbood Mode but dont select someting, Bootloader unlocked, RTK doesn´t find any devices in Fastboot Mode, Device is rooted and has CWM
Click to expand...
Click to collapse
what about just using adb? Can you find it when you type fastboot devices? If so there's a command in fastboot to reboot to recovery I think.
I on the other hand am screwed. I read in another forum that it hangs on unlock because the internal memory is fubar.

swing4thefence said:
what about just using adb? Can you find it when you type fastboot devices? If so there's a command in fastboot to reboot to recovery I think.
I on the other hand am screwed. I read in another forum that it hangs on unlock because the internal memory is fubar.
Click to expand...
Click to collapse
Solution for me:
1. Turn device on into Bootloop
2. Connect it via USB (PC founds it)
3. type in CMD "adb reboot recovery"
4. device is in recovery
5. reflash everything i wanted :good:
Requirement is a working Android-SDK!

I wish it was that easy for me. I can access recovery just fine. It's the memory I can't touch. Unless someone knows a way to fix corrupted memory...
Sent from my SCH-I510 using xda app-developers app

Im having this same issue too i can still get to CWM recovery but nothing really helps from there. I can still mount my storage and put zip files on there etc but nothing seems to fix the problem...any progress?

swing4thefence said:
I wish it was that easy for me. I can access recovery just fine. It's the memory I can't touch. Unless someone knows a way to fix corrupted memory...
Sent from my SCH-I510 using xda app-developers app
Click to expand...
Click to collapse
I think I'm going to try using my computer to mount and format the internal memory. any ideas as to the correct settings to use when I try this? at this point what have I got to lose?

swing4thefence said:
I think I'm going to try using my computer to mount and format the internal memory. any ideas as to the correct settings to use when I try this? at this point what have I got to lose?
Click to expand...
Click to collapse
Was this solved by any means ??, i am myself stuck at that position

Flash the stock image again using the Nexus Toolkit
Sent from my Nexus S using xda app-developers app

Akbar89 said:
Flash the stock image again using the Nexus Toolkit
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
Wug's Nexus toolkit ?? It is stuck on bootloader unlock menu, as unlocking bootloader makes it freeze. Without unlock it doesn't flashI anything.
If there is another tool please guide me with link.
Avoid Spells!!! "Auto correct : ON"

stuck on fastboot mode(lenovo S860)
recently i've bought lenovo s860 (2GB version).....its latest updates had bugs....so i was trying to downgrade to lower version(jelly bean).....in the way i got stuck in fastboot mode......is there any way to get out of it??

same problem in galaxy nexus i9250m
ej8989 said:
Did you install proper drivers?
Click to expand...
Click to collapse
i have same problem in galaxy nexus i9250m
my bootloader showingh no boot or recovery img
i have working fastboot, workin adb and driver
my oem is unlocked with fastboot
bt i am unable to flash recovery and rom

[Q] Nexus 5 stuck on boot, and wont go into recovery help?

Well, I was using an app called screen dimmer, and did pressed the button to dim the screen when all of a sudden it froze. It was like this for a while so I restarted it, it is able to go in fastboot, but nothing else. When i start It it hangs on the boot loader screen and can stay like that all day. if I go into recovery the screen goes black and the display is only backlit. I was going to try to to use the adb to factory reset it, but I could not get it to recognize the nexus 5 as a device. I used a bunch of different drivers. I did root my phone, and have the exposed framework but this was done a long time ago and I had no problems since. no idea how to fix this any help?!?!? Sorry if this is the wrong place to put this I'm new to this site.

2point said:
Well, I was using an app called screen dimmer, and did pressed the button to dim the screen when all of a sudden it froze. It was like this for a while so I restarted it, it is able to go in fastboot, but nothing else. When i start It it hangs on the boot loader screen and can stay like that all day. if I go into recovery the screen goes black and the display is only backlit. I was going to try to to use the adb to factory reset it, but I could not get it to recognize the nexus 5 as a device. I used a bunch of different drivers. I did root my phone, and have the exposed framework but this was done a long time ago and I had no problems since. no idea how to fix this any help?!?!? Sorry if this is the wrong place to put this I'm new to this site.
Click to expand...
Click to collapse
You need to find a driver that works so it'll recognize the device. Once you do this, you need to flash boot.img to restore the recovery since not working. Then, redo the ROM or restore from backup if you can. Flashing a new recovery boot.img should fix the issue.

2point said:
Well, I was using an app called screen dimmer, and did pressed the button to dim the screen when all of a sudden it froze. It was like this for a while so I restarted it, it is able to go in fastboot, but nothing else. When i start It it hangs on the boot loader screen and can stay like that all day. if I go into recovery the screen goes black and the display is only backlit. I was going to try to to use the adb to factory reset it, but I could not get it to recognize the nexus 5 as a device. I used a bunch of different drivers. I did root my phone, and have the exposed framework but this was done a long time ago and I had no problems since. no idea how to fix this any help?!?!? Sorry if this is the wrong place to put this I'm new to this site.
Click to expand...
Click to collapse
Hi, In first place, You are in the right place to get help:good:
2. ADB won't work on fastboot nor in a damaged recovery.
3. fastboot works:victory: Try to flash recovery once again (fastboot flash recovery recoveryname.img)
4. if 3 works, wipe system, caches. Flash the Rom you want, don't use that app anymore.

GUGUITOMTG4 said:
Hi, In first place, You are in the right place to get help:good:
2. ADB won't work on fastboot nor in a damaged recovery.
3. fastboot works:victory: Try to flash recovery once again (fastboot flash recovery recoveryname.img)
4. if 3 works, wipe system, caches. Flash the Rom you want, don't use that app anymore.
Click to expand...
Click to collapse
Thanks! got to recognize any way to do this without loosing data?

2point said:
Thanks! got to recognize any way to do this without loosing data?
Click to expand...
Click to collapse
There is a chance to keep your data + storage contents. If you manage to flash and boot into recovery, in 'wipe' menu manually check-mark "cache,system"
don't mark internal "storate and data", nothing will happen to your media and apps data.

2point said:
Thanks! got to recognize any way to do this without loosing data?
Click to expand...
Click to collapse
May be able to dirty flash but most likely, since you had the screen dimmed too much, you'll have to wipe data in order to override/remove the problem. You can try this way but may just send you back through this whole process if problem reoccurs. I'd just wipe the data to be safe.

2point said:
Well, I was using an app called screen dimmer, and did pressed the button to dim the screen when all of a sudden it froze. It was like this for a while so I restarted it, it is able to go in fastboot, but nothing else. When i start It it hangs on the boot loader screen and can stay like that all day. if I go into recovery the screen goes black and the display is only backlit. I was going to try to to use the adb to factory reset it, but I could not get it to recognize the nexus 5 as a device. I used a bunch of different drivers. I did root my phone, and have the exposed framework but this was done a long time ago and I had no problems since. no idea how to fix this any help?!?!? Sorry if this is the wrong place to put this I'm new to this site.
Click to expand...
Click to collapse
Oy vey! You shouldn't have been tinkering as you clearly don't know what you're doing.
[TUTORIAL] How to flash a factory image | Return to stock | Unroot your Nexus 5
2point said:
Thanks! got to recognize any way to do this without loosing data?
Click to expand...
Click to collapse
No, and if you had done your homework you would know that. If the data is so important, back it up before modding.

GUGUITOMTG4 said:
There is a chance to keep your data + storage contents. If you manage to flash and boot into recovery, in 'wipe' menu manually check-mark "cache,system"
don't mark internal "storate and data", nothing will happen to your media and apps data.
Click to expand...
Click to collapse
When I do fastboot boot recovery.img I get the android bot with a red exclamation but nothing else I might just do flashall

2point said:
When I do fastboot boot recovery.img I get the android bot with a red exclamation but nothing else I might just do flashall
Click to expand...
Click to collapse
Reflash the recovery.img

2point said:
When I do fastboot boot recovery.img I get the android bot with a red exclamation but nothing else I might just do flashall
Click to expand...
Click to collapse
The general idea is that your recovery is broken.
So, you need to flash a new recovery by placing a recovery.img file into your fastboot folder in the computer(recommend twrp). Like you did the first time you fladhed a recovery.
Then, turn off the phone, press volume down+ power button and it will boot into bootloader. Make sure it is on fastboot mode. After that, on the computer open cmd on the fastboot folder and and type:
fastboot flash recovery nameofrecoveryfile.img,
press enter.
It should flash a new recovery image if done correctly. Then, poweroff the phone, boot again into bootloader, choose recovery and it will reboot into recovery. Then follow. The steps of my first post.

jd1639 said:
Reflash the recovery.img
Click to expand...
Click to collapse
GUGUITOMTG4 said:
The general idea is that your recovery is broken.
So, you need to flash a new recovery by placing a recovery.img file into your fastboot folder in the computer(recommend twrp). Like you did the first time you fladhed a recovery.
Then, turn off the phone, press volume down+ power button and it will boot into bootloader. Make sure it is on fastboot mode. After that, on the computer open cmd on the fastboot folder and and type:
fastboot flash recovery nameofrecoveryfile.img,
press enter.
It should flash a new recovery image if done correctly. Then, poweroff the phone, boot again into bootloader, choose recovery and it will reboot into recovery. Then follow. The steps of my first post.
Click to expand...
Click to collapse
Did that and get a
C:\Users\nkkou_000\programs\adt-bundle-windows-x86_64-20131030\sdk\platform-tool
s>fastboot flash recovery openrecovery-twrp-2.6.3.4-hammerhead.img
sending 'recovery' (13272 KB)...
OKAY [ 0.620s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 44.593s
C:\Users\nkkou_000\programs\adt-bundle-windows-x86_64-20131030\sdk\platform-tool
s>

But I can do fastboot boot openrecovery-twrp-2.6.3.4-hammerhead.img and will will boot into the recovery just fine
And that twrp says that i have no os installed

2point said:
But I can do fastboot boot openrecovery-twrp-2.6.3.4-hammerhead.img and will will boot into the recovery just fine
And that twrp says that i have no os installed
Click to expand...
Click to collapse
You have a couple of options depending on how much data you can afford to lose on your phone. The least intrusive is to adb push a Rom on to your phone when you're in twrp Then flash that rom in twrp
The easier, but you'll lose all data on your phone is to flash the flash-all.bat file in fastboot
Sent from my SAMSUNG-SGH-I957 using xda app-developers app

2point said:
But I can do fastboot boot openrecovery-twrp-2.6.3.4-hammerhead.img and will will boot into the recovery just fine
And that twrp says that i have no os installed
Click to expand...
Click to collapse
Then, it seems recovery now is good. If you have rom zip in the storage. Just wipe system and cache, flash the rom and see what happens

When in the twrp I can't get fastboot to recognize it as a device, or adb either

2point said:
When in the twrp I can't get fastboot to recognize it as a device, or adb either
Click to expand...
Click to collapse
Your adb drivers aren't setup correctly. They're different than the fastboot ones. Try Google tool adb fastboot drivers xda.

jd1639 said:
Your adb drivers aren't setup correctly. They're different than the fastboot ones. Try Google tool adb fastboot drivers xda.
Click to expand...
Click to collapse
When you are on twrp. You dont need to use fastboot nor adb. Just flash a rom if have one to flash

GUGUITOMTG4 said:
When you are on twrp. You dont need to use fastboot nor adb. Just flash a rom if have one to flash
Click to expand...
Click to collapse
How do i do that?

2point said:
How do i do that?
Click to expand...
Click to collapse
Have you flashed roms before? And do you have one on your internal sdcard? If so flash it in twrp

jd1639 said:
Have you flashed roms before? And do you have one on your internal sdcard? If so flash it in twrp
Click to expand...
Click to collapse
I have the factory image from google for my nexus 5

[Q] Help! problems after instaling twrp 2.7

Ok so today i wanted to root my nexus 5 so i unlocked bootloader via androidSDK slim everything went fine but i did not power up my device yet thet i flash the recovery.img of twrp after that i booted into recovery and for a second it displayed some error i could not see it but it said could not read /e..... or i think so and it reboted itself and started booting android and now i think im stuck in boot loop because its booting up for 10 mins. can someone help me?

So now your Bootloader is unlocked, right?
First boot after unlocking the Bootloader takes time... Wait for 10 more mins and then reboot once again and see whether you can get the OS to bootup...
If you can't, you can either try factory reseting from Bootloader or you can flash a custom recovery and then install a custom rom of your choice.
Or you can also go full stock and start over again by flashing a factory image...
-Sent from an IceCold Hammerhead!

You're supposed to reboot the bootloader before flashing anything.

vin4yak said:
So now your Bootloader is unlocked, right?
First boot after unlocking the Bootloader takes time... Wait for 10 more mins and then reboot once again and see whether you can get the OS to bootup...
If you can't, you can either try factory reseting from Bootloader or you can flash a custom recovery and then install a custom rom of your choice.
Or you can also go full stock and start over again by flashing a factory image...
-Sent from an IceCold Hammerhead!
Click to expand...
Click to collapse
yes it is unlocked as i sad and i installed twrp so i have custom recovery ok ill wait a bit more and see what happends. what happens if i factory reset from bootloder?

rootSU said:
You're supposed to reboot the bootloader before flashing anything.
Click to expand...
Click to collapse
after it sad that unlocking is done with ulocking on command promt on my pc and on my phone i flashed the recovery right away. Now i turned my phone down by pressing power and vol down button and booted recovery and it did boot fine in twrp no with errors like first time so i gone to reboot and then system and it said that my phone is not rooted and to install super su i did that and now its booting up for like 10mins again still cant boot up into android. what can i do to fix this?

Alexandar92zr said:
after it sad that unlocking is done with ulocking on command promt on my pc and on my phone i flashed the recovery right away
Click to expand...
Click to collapse
This was your first mistake
Alexandar92zr said:
i turned my phone down by pressing power and vol down button and booted recovery and it did boot fine in twrp no with errors like first time so i gone to reboot and then system and it said that my phone is not rooted and to install super su i did that
Click to expand...
Click to collapse
And this the second mistake. Nothing should have been done before first restarting the bootloader.
Alexandar92zr said:
what can i do to fix this?
Click to expand...
Click to collapse
Flash the factory images from google for the nexus 5. There is a guide in General.
Once your phone boots, flash a recovery

rootSU said:
This was your first mistake
And this the second mistake. Nothing should have been done before first restarting the bootloader.
Flash the factory images from google for the nexus 5. There is a guide in General.
Once your phone boots, flash a recovery
Click to expand...
Click to collapse
can you link me the tutorial how to do that?

Alexandar92zr said:
can you link me the tutorial how to do that?
Click to expand...
Click to collapse
It's in General.

rootSU said:
This was your first mistake
And this the second mistake. Nothing should have been done before first restarting the bootloader.
Flash the factory images from google for the nexus 5. There is a guide in General.
Once your phone boots, flash a recovery
Click to expand...
Click to collapse
rootSU said:
It's in General.
Click to expand...
Click to collapse
sorry im a bin nervous becausemy phone is not working. i ment a tutorial how to flash factory images.

Alexandar92zr said:
sorry im a bin nervous becausemy phone is not working. i ment a tutorial how to flash factory images.
Click to expand...
Click to collapse
Don't be tense, you will tend to do more damage. Calm down m8.
here you go: http://forum.xda-developers.com/showthread.php?t=2513701

vin4yak said:
Don't be tense, you will tend to do more damage. Calm down m8.
here you go: http://forum.xda-developers.com/showthread.php?t=2513701
Click to expand...
Click to collapse
i found a tutorial on yt and now my phone is ok and running now i will flash custom recovery. thanks anyway and thanks a lot @rootSU

Alexandar92zr said:
sorry im a bin nervous becausemy phone is not working. i ment a tutorial how to flash factory images.
Click to expand...
Click to collapse
That was the answer. The tutorial is in the general forum here. ALL our important tutorials are in general

rootSU said:
That was the answer. The tutorial is in the general forum here. ALL our important tutorials are in general
Click to expand...
Click to collapse
now im rooted and everything is working as it should be thanks

[Q] Bricked one

os deleted and just stuck on one+ logo can boot in to twrp or fast boot what can i do?

brooklynchildxbc said:
os deleted and just stuck on one+ logo can boot in to twrp or fast boot what can i do?
Click to expand...
Click to collapse
Push a custom rom via adb and flash in recovery or flash stock images via fastboot

acuicultor said:
Push a custom rom via adb and flash in recovery or flash stock images via fastboot
Click to expand...
Click to collapse
i tried adb won't work and fastboot not doing anything i keeping getting a error saying that bootloader locked or can't erase
what really pisses me off i didn't even brick it a dumbass friend of mine did thinking he knew what he was doing.

brooklynchildxbc said:
i tried adb won't work and fastboot not doing anything i keeping getting a error saying that bootloader locked or can't erase
what really pisses me off i didn't even brick it a dumbass friend of mine did thinking he knew what he was doing.
Click to expand...
Click to collapse
Is fastboot working? Unlock bootloader and push custom recovery there. Go to adb sideload and that should work eventually. I had an issue with HTC One M7 - someone deleted sytem, and cyanogenmod installer helped, because it pushed CWM recovery, maybe try that one as well?

boober78 said:
Is fastboot working? Unlock bootloader and push custom recovery there. Go to adb sideload and that should work eventually. I had an issue with HTC One M7 - someone deleted sytem, and cyanogenmod installer helped, because it pushed CWM recovery, maybe try that one as well?
Click to expand...
Click to collapse
thank you so much i gave up then tried what you said then all of a sudden adb connected and i sideloaded the update file and got it back

brooklynchildxbc said:
thank you so much i gave up then tried what you said then all of a sudden adb connected and i sideloaded the update file and got it back
Click to expand...
Click to collapse
No problem. I'm glad I could help
Sent from my One using Tapatalk

brooklynchildxbc said:
thank you so much i gave up then tried what you said then all of a sudden adb connected and i sideloaded the update file and got it back
Click to expand...
Click to collapse
Don't give up.... I was in the same position like you for a couple days....and now is fix by my self..... If you unlock your bootloader try to lock back (fastboot oem lock) now try to flash via fastboot Philz Recovery ( try until is rebooting himself into recovery) .... After that put on a memory stick the new system .... You may need to mount the USB flash drive ..... That's exactly what I have done....Good Luck ...

It is damn near IMPOSSIBLE to actualy, truly "brick" these devices. There are way too many safeguards in place.
Be careful before announcing that you are "bricked". Bootlooping (which is what your device was doing) is not "bricked". As long as you have fastboot, you can always reflash recovery, and then use recovery to reflash your custom ROM (or you can bypass all of that and reflash the factory images from fastboot).
Don't panic, you know more than you think you know. Just don't get freaked out, and read. You'll be fine.