Hey guys...I'm having an issue.
I did the first step for rooting without the Recovery.img or Root.zip in the Folder.
Now I tried to do the reboot to go on the fastboot for 2nd step (recovery.img) and I get this error on my Windows:
QHSUSB_BULK
I believe it was because I had the phone plugged in. Anyway it was not going to fastboot.
So anyway I tried to do a factory reset too, and now fastboot is working, but I have no idea if it was because the phone was plugged in or because of the factory reset.
So, how do I know if the phone is bootloader unlocked or not after my factory reset?
What should I do?
Repeat Step one to unlock it again or do step 2? Thanks!
Is there any harm in doing fastboot oem unlock again just in case?
ok i believe its all done.
I have the phone rooted, should I keep debugging USB on?
Should I check the "Disable CM Recovery Protection" ?
Whats the best to do the OTA's without bricks or issues?
Related
Hi!
Nexus 5 16Gb, lot of acore and gapps errors when boot, then cyclical reboot. When i try unlock bootloader with fastboot mode, it shows UNLOCKED, but has status LOCKED again when reboot.
Any ideas, please
TIA
backup your apps/data, do a factory reset, flash your favorite ROM.
most likely you are having issues because of dirty flashed several incompatible ROMs
igchy said:
backup your apps/data, do a factory reset, flash your favorite ROM.
most likely you are having issues because of dirty flashed several incompatible ROMs
Click to expand...
Click to collapse
Factory reset was done, can't flash ROM because bootloader won't stay unlocked when i unlock it thru fastboot!
If the bootloader can't be unlocked, you can't do anything other than factory reset. The fact that the bootloader is locked even after unlocking points to a hardware issue.
BTW, After doing fastboot oem unlock did you select "YES" on the onscreen window which pops up?
vin4yak said:
BTW, After doing fastboot oem unlock did you select "YES" on the onscreen window which pops up?
Click to expand...
Click to collapse
Sure i did this
and then "fastboot reboot"
I'm not 100% sure it's possible, but can you re-flash/update bootloader?
because i think all cyanogen nightly builds after 03/17 require the latest bootloader.
Have you tried formatting? If you're not comfortable with it, don't try it, but it's certainly a step up from a factory reset. I'd bet it's just artifacts, as mentioned earlier.
I did factory reset many times (from recovery), but i can't unlock bootloader : when phone reboot after "fastboot oem unlock" command - bootloader is locked again
Not being able to unlock your bootloader is a good indication of emmc falling. You're most likely going to have to rma your device.
Sent from my Nexus 5
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.
Hello, I have problem with my softbricked Nexus 5.
phone is full stock
bootloader is locked
USB debugging is not enabled
Android 6.0.1
all buttons are working
USB socket is fine
Factory reset from recovery mode is not working - still bootlooping
My purpose is to bring it to live, but I am stuck. Due to locked bootloader I have to use LG Flash Tool. Some time ago I used it with my other Nexus 5 and it was fine - worked excellent. Now I want to do it again with other phone but I am stuck on start: Can't enter download mode (volume up+usb cable). When I am trying to enter to download mode,charging battery icon appears and after few seconds my phone is being recognized as MTP USB device in device manager. I thought it is a problem with the phone, but tried with another working Nexus and there is no difference - it looks like problem with phone-pc connection to me. I tried few cables (original samsung and nokia) and two pc's - no difference. Tried all USB ports etc. Clean reinstall (with registry keys delete) doesn't help, updated version 4.2 neither. Do you have any ideas how to fix it?
Download mode? Never heard of that on the Nexus 5. There is a fastboot mode for flashing stock ROMs and to unlock the bootloader.
I recommend unlocking the bootloader and using NRT to flash a stock ROM.
audit13 said:
Download mode? Never heard of that on the Nexus 5. There is a fastboot mode for flashing stock ROMs and to unlock the bootloader.
I recommend unlocking the bootloader and using NRT to flash a stock ROM.
Click to expand...
Click to collapse
I have NRT but problem is that to unlock bootloader I have to enable USB debugging - I can't do it with bootlooping phone.
Bootloader can be unlocked without enabling debugging as you are not running adb commands, you need to run fastboot commands.
audit13 said:
Download mode? Never heard of that on the Nexus 5. There is a fastboot mode for flashing stock ROMs and to unlock the bootloader.
I recommend unlocking the bootloader and using NRT to flash a stock ROM.
Click to expand...
Click to collapse
audit13 said:
Bootloader can be unlocked without enabling debugging as you are not running adb commands, you need to run fastboot commands.
Click to expand...
Click to collapse
Thanks! Can I do it with NRT also?
Easiest way to unlock the bootloader on a windows machine is to do this:
make sure that the necessary fast boot drivers are installed;
boot phone into fast boot mode by holding down volume up, volume down, and power;
connect the phone to the computer;
type "fastboot oem unlock" without the quotation marks and press enter key.
Unlocking will wipe the phone.
Once unlocked, you can flash a stock ROM using fastboot commands.
audit13 said:
Easiest way to unlock the bootloader on a windows machine is to do this:
make sure that the necessary fast boot drivers are installed;
boot phone into fast boot mode by holding down volume up, volume down, and power;
connect the phone to the computer;
type "fastboot oem unlock" without the quotation marks and press enter key.
Unlocking will wipe the phone.
Once unlocked, you can flash a stock ROM using fastboot commands.
Click to expand...
Click to collapse
Ok I did it. Do I have to proceed "fastboot reboot" command? when I am doing it it reboots and still bootlooping. When I enter bootloader it is locked again
If the bootloader relocks itself when the phone is rebooted, the memory chip is damaged and will need a motherboard replacement.
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.