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
Related
Hi guys!I have a weird problem on my HTC one.which is Google Play Edition.First of all,I was updating my htc to 5.0.1 lollipop which is official via OTA.It took a lot of time and I shut down the phone.And then everything is going to worse.It stuck bootloop unfortunately usb debugging is off ,and the phone is completely stock.(stock recovery,s-on,locked bootloader) I cant do anything due to this problem.I tried "adb push" and flash ruu but they also didnt work.How can I do?Thanks for helping.
reset?
what's the sound like on it?
i know on the ones with htc sense it is hit and miss call quality (with an audible hissing sound).........
fatihlale said:
Hi guys!I have a weird problem on my HTC one.which is Google Play Edition.First of all,I was updating my htc to 5.0.1 lollipop which is official via OTA.It took a lot of time and I shut down the phone.And then everything is going to worse.It stuck bootloop unfortunately usb debugging is off ,and the phone is completely stock.(stock recovery,s-on,locked bootloader) I cant do anything due to this problem.I tried "adb push" and flash ruu but they also didnt work.How can I do?Thanks for helping.
Click to expand...
Click to collapse
You could try to erase cache using fastboot and see if it can boot. If not try a factory reset.
If factory reset still doesn't work you'll have to unlock your bootloader, flash a custom recovery and resotre a nanadroid backup or flash a stock rom of 5.0.1.
alray said:
You could try to erase cache using fastboot and see if it can boot. If not try a factory reset.
If factory reset still doesn't work you'll have to unlock your bootloader, flash a custom recovery and resotre a nanadroid backup or flash a stock rom of 5.0.1.
Click to expand...
Click to collapse
It doesn't work. How can I unlock boot loader while usb debugging is off. Is there any method?
fatihlale said:
It doesn't work. How can I unlock boot loader while usb debugging is off. Is there any method?
Click to expand...
Click to collapse
you don't need usb debugging. Usb debugging is only needed to have adb connectivity when the phone is booted in android.
for gpe device you should be able to unlock it using fastboot from the bootloader.
Code:
fastboot oem unlock
If this method doesnt work you'll need to use HTCdev.com to unlock it.
Don't forget that unlocking your bootloader will wipe everything on your phone.
alray said:
you don't need usb debugging. Usb debugging is only needed to have adb connectivity when the phone is booted in android.
for gpe device you should be able to unlock it using fastboot from the bootloader.
Code:
fastboot oem unlock
If this method doesnt work you'll need to use HTCdev.com to unlock it.
Don't forget that unlocking your bootloader will wipe everything on your phone.
Click to expand...
Click to collapse
It doesn't work bro because off usb debugging is disable. I tried many times but It doesn't work look at the attachmentView attachment 3059584
fatihlale said:
It doesn't work bro because off usb debugging is disable. I tried many times but It doesn't work look at the attachmentView attachment 3059584
Click to expand...
Click to collapse
It have nothing to do with usb debugging! Like I said above, the only purpose of usb debugging is to enable adb connectivity when the phone is booted in android.
Even if usb debugging is turned off, you still have the ability to use fastboot commands from the bootloader (like you have tried) and to use adb commands from a custom recovery (which you don't have access to because of your locked bootloader)
With that said, I'm sorry to tell you that what you are seeing after doing "fastboot oem unlock" (PG_ERROR) is typical of the infamous GPE bootloader bug. This bug make impossible to unlock your bootloader from using oem unlock or by using HTCdev.com method. So your phone is bricked sorry.
you are not alone, see this thread: http://forum.xda-developers.com/showthread.php?t=2547894
fatihlale said:
It doesn't work bro because off usb debugging is disable. I tried many times but It doesn't work look at the attachmentView attachment 3059584
Click to expand...
Click to collapse
so my device is going to rubbish am I right?
fatihlale said:
so my device is going to rubbish am I right?
Click to expand...
Click to collapse
Maybe keep it in a drawer and hope that HTC will release a 5.11.1700.3 or higher version official RUU so you'll be able to flash it with s-on and a locked bootloader.
or maybe you could ask the guys at fonefunshop if they are able to s-off it using their method which doesnt require to boot in the rom.
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.
I was installed with Twrp and had rooted my oneplus 3.
I unticked root access in supersu.
Booted to bootloader and typed on my pc in command prompt ,"Fastboot oem lock"
This gave a confirmation on my device,I confirmed locking.
And after that my device did not booted up.I managed to get in bootloader again as I was not even able to open the recovery and unlocked the bootloader once again by this my device booted up.
I flashed stock recovery and repeated the relocking process,this time I was able to open recovery also but no able to boot up.
I again unlocked the bootloader and installed twrp back turned my device up.
Then I unchecked oem unlocking under developer options.
Relocked the bootloader once again.
And now I am stuck at bootloader,not able to unlock it even this time as I turned off oem unlocking.
Now I can only open bootloader.
Please help!
hchawla98 said:
I was installed with Twrp and had rooted my oneplus 3.
I unticked root access in supersu.
Booted to bootloader and typed on my pc in command prompt ,"Fastboot oem lock"
This gave a confirmation on my device,I confirmed locking.
And after that my device did not booted up.I managed to get in bootloader again as I was not even able to open the recovery and unlocked the bootloader once again by this my device booted up.
I flashed stock recovery and repeated the relocking process,this time I was able to open recovery also but no able to boot up.
I again unlocked the bootloader and installed twrp back turned my device up.
Then I unchecked oem unlocking under developer options.
Relocked the bootloader once again.
And now I am stuck at bootloader,not able to unlock it even this time as I turned off oem unlocking.
Now I can only open bootloader.
Please help!
Click to expand...
Click to collapse
OEM locking a bootloader on a phone that was rooted is a big mistake.
You'll need to flash stock recovery, then flash the stock ROM via adb sideload.
Can be done with this tool http://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
Thanks for reply
Newyork! said:
OEM locking a bootloader on a phone that was rooted is a big mistake.
You'll need to flash stock recovery, then flash the stock ROM via adb sideload.
Can be done with this tool http://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
Click to expand...
Click to collapse
with that tool I was only able to wipe cache.
Nothing else is working
It says failed
hchawla98 said:
with that tool I was only able to wipe cache.
Nothing else is working
It says failed
Click to expand...
Click to collapse
Can you access stock recovery?
NO
Newyork! said:
Can you access stock recovery?
Click to expand...
Click to collapse
I can't access it as I am installed with TWRP Recovery as it is also not starting.
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.
Hello, I have a vanilla Pixel 2 which corrupted itself and will not boot. It boots to recovery mode, but Bootloader is locked. I have not done a factory reset, and am attempting to recover the files. Fastboot mode works but will not allow temporary boot or unlocking of bootloader. I can access adb but only in sideload mode. OTA images successfully sideload but it still will not boot... After hours of scouring google I'm stumped. Any thoughts or suggestions welcome.
Hint: Add Pixel 2 to this thread's title thus mainly owners of such a phone get addressed.
jm001 said:
Hello, I have a vanilla Pixel 2 which corrupted itself and will not boot. It boots to recovery mode, but Bootloader is locked. I have not done a factory reset, and am attempting to recover the files. Fastboot mode works but will not allow temporary boot or unlocking of bootloader. I can access adb but only in sideload mode. OTA images successfully sideload but it still will not boot... After hours of scouring google I'm stumped. Any thoughts or suggestions welcome.
Click to expand...
Click to collapse
I see that u want to keep your files but sorry to say this but your gonna have to do a factory reset because their is no other way to fix this
To do this boot into recovery mode and perform a factory reset
If u can't boot into recovery mode u probably have to unlock bootloader than install twrp
But that's probably only gonna work if u enabled oem unlock and enabled usb debugger before your device got bricked
Because if u try to unlock the bootloader with oem unlock and usb debugger disenable your gonna receive error when trying to unlock bootloader
Try to start in recovery mode. Otherwise only restore is the option.
You can start mobile in fastboot mode. You can back up mobile.
adb backup -all
jm001 said:
Hello, I have a vanilla Pixel 2 which corrupted itself and will not boot. It boots to recovery mode, but Bootloader is locked. I have not done a factory reset, and am attempting to recover the files. Fastboot mode works but will not allow temporary boot or unlocking of bootloader. I can access adb but only in sideload mode. OTA images successfully sideload but it still will not boot... After hours of scouring google I'm stumped. Any thoughts or suggestions welcome.
Click to expand...
Click to collapse
On Android-side bootloader initializes ADB and mounts partitions. Hence check whether phone is accessible via ADB:
Code:
adb reboot
adb devices
If it is, and partitions got mounted, then you can fetch the user-data you are interested in by means of adb pull method.