Database Info

Stuck at Google logo :(

EDIT: so i tried a couple of things.. Everytime i unlock the bootloader and reboot it starts locked again (as if i never unlocked it), i tried to flash factory image using fastboot but gives me "flash write failure", tried flashing custom recoveries (both cwm and twrp) they flash fine but when i boot into recovery mode the stock recovery appears, so i tired sthg new : booting from the custom recovery without flashing... Cwm boots fine..fails to factory reset (it just gives error and reboots the phone especially when i try anything with the cache partition) so i went to boot twrp.. It takes half an hour to open twrp after its "teamwin" screen... But it helped me as it showed that : system and firmware partitions are working well (format /mount) but cache, persist and data partitions don't (no mounting and error while formating) plus data partition shows zero Mb size.... Basically any change i do either gives an error or dissappears on reboot..... Please helppp! ?
Old post:
Hey all,
My hammerhead is stuck at Google logo, the problem is that bootloader is locked and usb debugging is disabled... Can't boot to enable it, can't flash new rom.. What can i do with no usb debugging and locked bootloader? Thanks in advance

Gofersamy said:
Hey all,
My hammerhead is stuck at Google logo, the problem is that bootloader is locked and usb debugging is disabled... Can't boot to enable it, can't flash new rom.. What can i do with no usb debugging and locked bootloader? Thanks in advance
Click to expand...
Click to collapse
You can boot into recovery and do a factory reset. It'll wipe your data. Or you can unlock the bootloader, it'll wipe your data, and flash the factory image.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
You can boot into recovery and do a factory reset. It'll wipe your data. Or you can unlock the bootloader, it'll wipe your data, and flash the factory image.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
As far as i understand unlocking the bootloader would require enabled usb debugging right?

Gofersamy said:
As far as i understand unlocking the bootloader would require enabled usb debugging right?
Click to expand...
Click to collapse
No. fastboot oem unlock - http://forum.xda-developers.com/goo...urce-guides-info-threads-linked-read-t2784527

Gofersamy said:
As far as i understand unlocking the bootloader would require enabled usb debugging right?
Click to expand...
Click to collapse
No, you'd don't need usb debugging enabled to unlock the bootloader. You just need fastboot on your pc. Google 15 second adb install xda. That'll setup fastboot. Then boot into your bootloader and from a command window on your pc run the command
fastboot oem unlock
Sent from my Nexus 5 using XDA Free mobile app

Bootlooping, Recovery Corrupted, Cant enable USB Debugging am I screwed?

After messing around with my shield last night and not being able to get root access on cm12. I tried to reinstall one of the ota updates from a while back. Now I am bootlooping and when I try to boot into CWM it looks to be corrupted and doesn't load. I cant use ADB because usb debugging is no longer active. Does anybody have any suggestions to re-install recovery or somehow enable debugging or am I dead in the water here? Any help would be greatly appreciated

Is your bootloader unlocked?
Can you get into fastboot mode?
HW method:
Turn off the device
Press and hold "Back"+"Home"+"SHIELD" buttons till device boots
Click to expand...
Click to collapse
If you can get into fastboot mode and your bootloader is unlocked, you can use a command like "fastboot boot recovery.img" to have the device boot a recovery.img from your computer without flashing anything.
If you can get into fastboot mode, but your bootloader isn't unlocked you could try unlocking your bootloader, but this will wipe your data - so only try this if you don't have anything important saved. The command is "fastboot oem unlock".
~Troop

The bootloader is unlocked Whenever I try fastboot mode the device is not recognized because USB debugging is disabled .
Update: Fixed

Nexus 5 Stuck at erasing mode after factory resetting

Guys I have been using Nexus 5 since the day it was released. This evening I was factory resetting my Nexus 5 after it rebooted it just got stuck on Erasing. I'm unable to go in recovery mode also as after booting into bootloader mode and selecting recovery it just shows andriod logo and erasing, it's more than and hour like this. Can anyone please help me out with it ?
Edit: The thing is USB debugging is not activated on my device and now fastboot is not recognising my Nexus 5 on my new laptop I think it might be because of either USB Debugg or Driver problems. Ay help would be appreciated.

Can you get into fastboot and unlock the bootloader? If the bootloader remains unlocked after a reboot, you could flash a stock rom. Unlocking the bootloader will wipe the phone.

To be clear, USB debugging has nothing to do with fastboot. It is a driver or cable issue if your computer is not recognizing it. Fix the drivers and try what audit13 said.

audit13 said:
Can you get into fastboot and unlock the bootloader? If the bootloader remains unlocked after a reboot, you could flash a stock rom. Unlocking the bootloader will wipe the phone.
Click to expand...
Click to collapse
wangdaning said:
To be clear, USB debugging has nothing to do with fastboot. It is a driver or cable issue if your computer is not recognizing it. Fix the drivers and try what audit13 said.
Click to expand...
Click to collapse
Thanks guys it worked.

Nexus Stuck on Google Logo

Hello guys, I dont know whats happening with my Nexus 5 right now. Its stuck on Google logo which appears during restarting of the phone.
I have tried everything. I try to go into recovery it dosent work. I tried changing it to CWM from TWRP still it stays TWRP i get errors while flashing .bat files like (error: failure to write). Please help been stuck on this since past 72hours. Any help to resolve this issue is appreciated. Thanks :crying::crying::crying:

If the bootloader is unlocked, relock the bootloader and reboot into fastboot mode. If the bootloader unlocks itself, the internal memory is probably damaged. If the bootloader remains locked, unlock it and flash 4.4 using fastboot commands.

audit13 said:
If the bootloader is unlocked, relock the bootloader and reboot into fastboot mode. If the bootloader unlocks itself, the internal memory is probably damaged. If the bootloader remains locked, unlock it and flash 4.4 using fastboot commands.
Click to expand...
Click to collapse
OEM can be locked and unlocked. But the only problem now is i cannot override the previous partitions as there is an error "failed to write" i dont understand why is this happening this is also the reason i cannot get into my recovery as when i enter recovery it gets stuck for some reason.

audit13 said:
If the bootloader is unlocked, relock the bootloader and reboot into fastboot mode. If the bootloader unlocks itself, the internal memory is probably damaged. If the bootloader remains locked, unlock it and flash 4.4 using fastboot commands.
Click to expand...
Click to collapse
Also what does flash 4.4 mean? Sorry new to this!

audit13 said:
If the bootloader is unlocked, relock the bootloader and reboot into fastboot mode. If the bootloader unlocks itself, the internal memory is probably damaged. If the bootloader remains locked, unlock it and flash 4.4 using fastboot commands.
Click to expand...
Click to collapse
Also i tried to erase partitions manually but i always got an error as (remote: failed to erase partition)

Let's start with the bootloader.
Boot into fastboot mode, lock the bootloader, reboot into fastboot mode. Does the bootloader stay "locked" or does it go back to say "unlocked"?

audit13 said:
Let's start with the bootloader.
Boot into fastboot mode, lock the bootloader, reboot into fastboot mode. Does the bootloader stay "locked" or does it go back to say "unlocked"?
Click to expand...
Click to collapse
It goes back to unlocked

audit13 said:
Let's start with the bootloader.
Boot into fastboot mode, lock the bootloader, reboot into fastboot mode. Does the bootloader stay "locked" or does it go back to say "unlocked"?
Click to expand...
Click to collapse
Do you have discord or teamspeak or any other apps to chat directly?

NeXussssssssss said:
It goes back to unlocked
Click to expand...
Click to collapse
The internal memory may be damaged.
You might want to try this: https://forum.xda-developers.com/google-nexus-5/general/how-fixed-bricked-nexus-5-corrupted-t2903593

audit13 said:
The internal memory may be damaged.
You might want to try this: https://forum.xda-developers.com/google-nexus-5/general/how-fixed-bricked-nexus-5-corrupted-t2903593
Click to expand...
Click to collapse
I tried the 1st step by overwriting twrp with cwm dint work. Also ADB isnt connected. I tried to but just fastboot works.

I recommend flashing stock 4.4 using fastboot commands.
Stock ROMs are here: https://developers.google.com/android/images

audit13 said:
I recommend flashing stock 4.4 using fastboot commands.
Stock ROMs are here: https://developers.google.com/android/images
Click to expand...
Click to collapse
I tried flashing new roms it says failure to write to cache,boot,recovery everything fails!
There is no way to erase partitions as it fails!

I would say the internal memory is damaged and will require a motherboard change.

your device is corrupted and cannot be trusted.

Hello,
I have OP8 and its was rooted before, I did oem lock from fastboot then I got this message. " your device is corrupted and cannot be trusted"
i can't even flash stock rom. fastboot not accept command

OmanGhost said:
Hello,
I have OP8 and its was rooted before, I did oem lock from fastboot then I got this message. " your device is corrupted and cannot be trusted"
i can't even flash stock rom. fastboot not accept command
Click to expand...
Click to collapse
Sounds like the bootloader was modified, which breaks the digital signature.
Try unlocking the bootloader again and reboot. Go into developers options and turn usb debugging on. Then connect a cable between your computer and the phone. An RSA signature key should be presented. Check the box "always accept from this computer". Then try rebooting into fastboot and flashing stock.
Not sure of this will help but that's the best advice I can offer.
Cheers,
B.D.