Database Users

Remove ClockworkMod Recovery and relock after bricked

So I tried to update to KitKat 4.4 and was never able to get passed the loading screen. I booted into ClockworkMod Recovery and wiped everything and now the device will not go passed the Google loading screen. The device is no longer recognized when I plug into the computer and I cannot access through Wugs.
I called Google and they are sending out an RMA for this device (I did not tell them it was unlocked) and they are sending out a replacement.
Is there anyway that I can remove ClockworkMod Recovery and re-lock this device without being able to access the device through a computer?

BrianXP7 said:
Whoa, RMA's should be only used for last resort bootloader bricks! Since you still have the bootloader ("Google" logo at startup), hold Power + Volume Down to enter Fastboot mode and try reflashing the factory images. Just to be safer, use the Universal Naked Drivers and skip with bootloader image. Don't forget to have the ADB and Fastboot binaries in the same folder. I wouldn't recommend toolkits as they don't expose new users with these situations.
If you need anything else, let me know. If I completely missed on what you needed, sorry about that.
Also, just as long as the bootloader update isn't interrupted or type "fastboot erase bootloader" you should be fine without an RMA.
Click to expand...
Click to collapse
thanks for the reply.
I am able to boot in recovery mode on the device and this is recognized by Wugs as "ADB - device on". When I attempt any flash, it checks Fastboot status and I receive notification that the "Fastboot device was not found". I cannot find a compatible driver when I am in fastboot mode running on a Windows 7 x64 machine.
Any idea on how I can get this N7 to function, return to stock, or at least remove ClockworkMod and lock the bootloader so I can RMA?

nexus 6p doesn't boot, with error when trying to unlock

Greeting,
My nexus 6P, suddenly while having a phone call, got freeze, then rebooted,
Then it keeps rebooting, showing Google “in white” while booting, then off, restart again “by itself”, and same in loop
Started the device into fastboot mode, selected recovery mode
Again same issue, restart, shows Google “in white” then restart again
Tried to follow the instructions, at [GUIDE] Unlock/Root/Flash for Nexus 6P
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Commands and results are here
C:\nexus6p\angler-n4f26o>adb version
Android Debug Bridge version 1.0.36
Revision 0e9850346394-android
C:\nexus6p\angler-n4f26o>adb devices
List of devices attached
<Notice no result returned>
C:\nexus6p\angler-n4f26o>fastboot devices
8XV7N16126000082 fastboot
Please note, I checked those points
ADB and fastboot, downloaded from the link provided in the guide, as well I downloaded it from Google directly
USB driver, updated with latest from google
Java, updated
And of course, I cannot run the device, to do any required configuration on it
And here is a copy of the device details

malibusa said:
Greeting,
My nexus 6P, suddenly while having a phone call, got freeze, then rebooted,
Then it keeps rebooting, showing Google “in white” while booting, then off, restart again “by itself”, and same in loop
Started the device into fastboot mode, selected recovery mode
Again same issue, restart, shows Google “in white” then restart again
Tried to follow the instructions, at [GUIDE] Unlock/Root/Flash for Nexus 6P
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Commands and results are here
C:\nexus6p\angler-n4f26o>adb version
Android Debug Bridge version 1.0.36
Revision 0e9850346394-android
C:\nexus6p\angler-n4f26o>adb devices
List of devices attached
<Notice no result returned>
C:\nexus6p\angler-n4f26o>fastboot devices
8XV7N16126000082 fastboot
Please note, I checked those points
ADB and fastboot, downloaded from the link provided in the guide, as well I downloaded it from Google directly
USB driver, updated with latest from google
Java, updated
And of course, I cannot run the device, to do any required configuration on it
And here is a copy of the device details
Click to expand...
Click to collapse
If you can get into bootloader mode then maybe try fastest flashing things like stock recovery. If you manage to get stock recovery then boot into it and adb sideload a stock OTA from Google Developer website. Other than that I'm not too sure, you might need to contact Google/Huawei if that or anything else doesn't work.
---------- Post added at 08:43 PM ---------- Previous post was at 08:35 PM ----------
Okay, in bootloader mode try flashing the stock bootloader image from their OTA by typing fastboot flash bootloader (drag bootloader image here) then type fastboot reboot-bootloader. After that type fastboot flash radio (drag radio image here). Then type fastboot reboot-bootloader again. After that you can try booting up. If you are somehow able to get into recovery mode whether you can boot up normally or not then you can simply adb sideloading the stock OTA. If nothing I have said gets you into recovery or to boot up the device then you are probably screwed to be honest. Good luck

Hi,
thanks for your reply,
let me make sure, that i understood you clearly,
when i boot into bootloader, and select the recovery mode,
it get rebooted, shows Google “in white” then restart again, and again in same loop exactly as if i booted normally, not into the bootloader
as i read in other posts, i should expect the device to show me a confirmation message, or something similar,
but in my case, nothing at all, restart, and keep restarting
The options i have with bootloader are
1- Start
2- Reboot bootloader
3- Recovery mode
4- Power off
5- Barcodes

malibusa said:
Hi,
thanks for your reply,
let me make sure, that i understood you clearly,
when i boot into bootloader, and select the recovery mode,
it get rebooted, shows Google “in white” then restart again, and again in same loop exactly as if i booted normally, not into the bootloader
as i read in other posts, i should expect the device to show me a confirmation message, or something similar,
but in my case, nothing at all, restart, and keep restarting
The options i have with bootloader are
1- Start
2- Reboot bootloader
3- Recovery mode
4- Power off
5- Barcodes
Click to expand...
Click to collapse
In bootloader mode, not recovery try flashing the bootloader and radio like I said.

Hi... RMA your phone... Contact google or Huawei depending where you bought your N6P.
Check this link. A lot of people seem to be in the same situation at the moment:
https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528

You're in the same boat as a few of us.
Phone is stuck in a bootloop, won't go to recovery. Only boots to fastboot, but your bootloader is locked so you cannot boot/flash any zips, even official ones. That means no recovery access, which means no adb commands. ADB commands *might* be useful to reboot into EDL mode for QFIL flashing, or for wiping partitions. Problem is - if that bootloader wasn't unlocked, it's not going to be. You need to check "Allow OEM unlocking" in settings BEFORE the phone dies, otherwise you will not be able to unlock the bootloader and thereby reflash the phone.
In a perfect world - we could use EDL mode (or something) to use QFIL/MiFlash to completely rewrite the partitions and MAYBE bring the phone back to life, but the stock bootloader does not allow access to EDL. (tried the custom fastboot.exe meant to send the reboot-edl command, didn't work). If someone can figure out the JTAG pins, we might be able to move forward by purposely bricking it to QHUSB_BULK mode.
The thing is - we don't know why the phones started bootlooping in the first place. For some people, a simple cache wipe/factory reset fixes the loop and away they go. HOWEVER, those of us stuck in fastboot mode with a locked bootloader have no way to erase/wipe/format/write partitions, and even if we could, there's no guarantee it was a software issue that caused the loop in the first place.
TL/DR - You have a locked bootloader and cannot access recovery mode, this means you won't be able to flash/wipe/format partitions or images. Best bet is to contact Huawei/Google, but you'll need the original receipt. If that's not an option for you, you're gonna have to wait until the XDA geniuses out there grant us some answers.
Here's a related thread with some deep info:
https://forum.xda-developers.com/nexus-6p/general/qpst-qfil-answer-to-issues-t3455779

singularoctopi said:
You're in the same boat as a few of us.
Phone is stuck in a bootloop, won't go to recovery. Only boots to fastboot, but your bootloader is locked so you cannot boot/flash any zips, even official ones. That means no recovery access, which means no adb commands. ADB commands *might* be useful to reboot into EDL mode for QFIL flashing, or for wiping partitions. Problem is - if that bootloader wasn't unlocked, it's not going to be. You need to check "Allow OEM unlocking" in settings BEFORE the phone dies, otherwise you will not be able to unlock the bootloader and thereby reflash the phone.
In a perfect world - we could use EDL mode (or something) to use QFIL/MiFlash to completely rewrite the partitions and MAYBE bring the phone back to life, but the stock bootloader does not allow access to EDL. (tried the custom fastboot.exe meant to send the reboot-edl command, didn't work). If someone can figure out the JTAG pins, we might be able to move forward by purposely bricking it to QHUSB_BULK mode.
The thing is - we don't know why the phones started bootlooping in the first place. For some people, a simple cache wipe/factory reset fixes the loop and away they go. HOWEVER, those of us stuck in fastboot mode with a locked bootloader have no way to erase/wipe/format/write partitions, and even if we could, there's no guarantee it was a software issue that caused the loop in the first place.
TL/DR - You have a locked bootloader and cannot access recovery mode, this means you won't be able to flash/wipe/format partitions or images. Best bet is to contact Huawei/Google, but you'll need the original receipt. If that's not an option for you, you're gonna have to wait until the XDA geniuses out there grant us some answers.
Here's a related thread with some deep info:
https://forum.xda-developers.com/nexus-6p/general/qpst-qfil-answer-to-issues-t3455779
Click to expand...
Click to collapse
I'm stuck with a black screen and QFIL and XiaoMiFlash won't work. My bootloader is unlocked but I can't get to fastboot. Screen is always black but Quallcomm HS-USB QDLoader 9008 appears in device manager. No red light or vibration when connecting the phone.

vcharette said:
I'm stuck with a black screen and QFIL and XiaoMiFlash won't work. My bootloader is unlocked but I can't get to fastboot. Screen is always black but Quallcomm HS-USB QDLoader 9008 appears in device manager. No red light or vibration when connecting the phone.
Click to expand...
Click to collapse
Have you read this thread: https://forum.xda-developers.com/nexus-6p/general/howtos-debrick-nexus-6p-stuck-edl-9008-t3552838
Maybe try asking here, explaining the things you tried.

Bootloop after fingerprint sensor and ROM died

Hello,
problem above, maybe it's a hardware malfunction which would be awful.
I tried:
- whipe everything in the CyanogenRecoveryMenu
- sideload via Minimal ADB / Fastboot
- a lot more commands and helps on this site and on the internet (push,
Details:
- fingerprinter died, then the phone always crashed with blue and green flashing lights on the screen and now a bootloop
- "stock" CyanogenOS installed, but no TWRP
- the phone gets detected by my computer (sound)
- i don't remember if usb debugging is enabled (probably not)
- the command "adb devices" shows my phone when its in ADB mode (recovery menu)
- i sometimes get the error "error:closed" on my computer
Thank you for any help
doebelfish

doebelfish said:
Hello,
problem above, maybe it's a hardware malfunction which would be awful.
I tried:
- whipe everything in the CyanogenRecoveryMenu
- sideload via Minimal ADB / Fastboot
- a lot more commands and helps on this site and on the internet (push,
Details:
- fingerprinter died, then the phone always crashed with blue and green flashing lights on the screen and now a bootloop
- "stock" CyanogenOS installed, but no TWRP
- the phone gets detected by my computer (sound)
- i don't remember if usb debugging is enabled (probably not)
- the command "adb devices" shows my phone when its in ADB mode (recovery menu)
- i sometimes get the error "error:closed" on my computer
Thank you for any help
doebelfish
Click to expand...
Click to collapse
Did you also tried factory reset already?
If you have adb access you can only try to get bootloader unlocked which wipes all if not happened yet. Then you can try installing twrp and another rom and see if boot is OK.
If your bootloader is still locked go to service center if you have warranty!

strongst said:
Did you also tried factory reset already?
If you have adb access you can only try to get bootloader unlocked which wipes all if not happened yet. Then you can try installing twrp and another rom and see if boot is OK.
If your bootloader is still locked go to service center if you have warranty!
Click to expand...
Click to collapse
Thanks for a reply,
After a full reset I have downloaded a twrp.img file for my device
I tried:
- command "fastboot devices" while in fastboot-mode (I pressed reboot to bootloader in the recovery menu to get there)
-> no device detected despite a sound after connecting
- command "fastboot flash twrp.img" -> "waiting for device" without any further reaction
My device is only detected in ADB mode, not in fastboot mode, how can I change that? I must unlock the boot loader in fastboot mode right?

doebelfish said:
Thanks for a reply,
After a full reset I have downloaded a twrp.img file for my device
I tried:
- command "fastboot devices" while in fastboot-mode (I pressed reboot to bootloader in the recovery menu to get there)
-> no device detected despite a sound after connecting
- command "fastboot flash twrp.img" -> "waiting for device" without any further reaction
My device is only detected in ADB mode, not in fastboot mode, how can I change that? I must unlock the boot loader in fastboot mode right?
Click to expand...
Click to collapse
Did you have actually drivers installed for fastboot? See guides like this http://forum.xda-developers.com/zuk-z1/general/guide-how-to-unlock-root-install-twrp-t3394037
Also qfil method can help http://www.androidbrick.com/lenovo-zuk-phones-qfil-roms-unbrick-guide/
But consider service center in case of warranty.

same problem. fingerprint died. then after a empty battery shutdown i face bootloop. but hopefully i have TWRP installed and i could recover my data. but i dont know how to access factory reset menue or install another fresh rom

Stuck in Bootloop

US996 Unlocked, stock rom. I was in XDA Forums and saw there were app updates, one being Play Store. I updated. When I tried to get into Play Store, the message "this version of play store is incompatible with your device, go to settings and disable app update (or something like that). I tried but the app was not listed in settings. I tried to reboot and now the phone bootloops. All I can get is the warning that the software cannot be checked for corruption and then a quick display of the LG logo, then screen off, and then LG logo again and then warning screen, etc. If I try to reboot into recovery I get the Factory data reset screens and I answer both "yes" and the phone goes into adb mode.. From adb mode I can fastboot reboot, which puts me back into the above loop, or fastboot bootloader, which merely returns me to the adb screen. What can I do now?

Maybe try relocking the bootloader. I am pretty sure (someone correct me if I am wrong) that that pop-up of the "cannot check for corruption" usually only shows when the bootloader is unlocked.

XP_1 said:
Maybe try relocking the bootloader. I am pretty sure (someone correct me if I am wrong) that that pop-up of the "cannot check for corruption" usually only shows when the bootloader is unlocked.
Click to expand...
Click to collapse
Is that even possible? Don't know how to do it.

PhoneBull said:
Is that even possible? Don't know how to do it.
Click to expand...
Click to collapse
Try entering
Code:
fastboot oem device-info
into Fastboot on your computer to see if it says it is unlocked when in fastboot mode.

XP_1 said:
Try entering
Code:
fastboot oem device-info
into Fastboot on your computer to see if it says it is unlocked when in fastboot mode.
Click to expand...
Click to collapse
I get "FAILED (remote: unknown command)"

Do you have fastboot installed on your computer? (Something you would have had to have intentionally installed) If not google Minimal Fastboot /ADB and install it, enter the supposed ADB screen you are talking about and see if it makes contact with your phone.

XP_1 said:
Do you have fastboot installed on your computer? (Something you would have had to have intentionally installed) If not google Minimal Fastboot /ADB and install it, enter the supposed ADB screen you are talking about and see if it makes contact with your phone.
Click to expand...
Click to collapse
I have the fastboot on the PC that I used to unlock the bootloader.. I enter fastboot on the PC via the administrative command prompt. With the phone in the fastboot mode, I type "fastboot devices" on the PC and get a proper response (LGUS996ab**** fastboot). If I enter ""fastboot reboot" I get the bootloop. If I enter "fastboot bootloader" I wind up in Fastboot Mode on the phone again. I was hoping there was a "fastboot recovery" command but there doesn't seem to be. I don't know what to do next. I am not all that familiar with what can be done from fastboot. My only experience with it was when I unlocked the phone. I am desperate!

Okay, so if you do not have TWRP installed on your phone, then I don't know if you can save your data. You can try to
Code:
fastboot erase cache
and see if it helps, or if not and just reset the device fastboot oem lock I think. Maybe ask around in the unlocking help threads or perhaps someone with more knowledge will chime in. If none of this works, then there are some instructions on how to get your phone back to stock in the News and Guides section.
EDIT: Maybe try the power+volume down. It may work? I have tried it and never got it to successfully work. But you can try it.

XP_1 said:
Okay, so if you do not have TWRP installed on your phone, then I don't know if you can save your data. You can try to
Code:
fastboot erase cache
and see if it helps, or if not and just reset the device fastboot oem lock I think. Maybe ask around in the unlocking help threads or perhaps someone with more knowledge will chime in. If none of this works, then there are some instructions on how to get your phone back to stock in the News and Guides section.
Click to expand...
Click to collapse
Thanks for your help. I DO have TWRP installed and have used it often for backups. But now the only way I know to TRY to get to it is by the power/vol down until LG logo, then release/repress power button sequence but this just gets me into fastboot mode. II have some recent backups saved on my micro SD card - is there any way to flash one of them through fastboot if I load one onto the PC?

Yeah. My bad. Okay, so how I get into TWRP is through the EasyRecowvery.
Go ahead and download it from Git-Hub (1.3b3).
Now extract it and run the cmd program. Enter 5. which is extras and stuff and then enter 5 again in the sub menu which will let you boot into recovery. When you are in recovery, and plugged into your computer, you should be able to either flash or drag and drop like a flash drive on the the phone. Hope that helps a little bit.

XP_1 said:
Yeah. My bad. Okay, so how I get into TWRP is through the EasyRecowvery.
Go ahead and download it from Git-Hub (1.3b3).
Now extract it and run the cmd program. Enter 5. which is extras and stuff and then enter 5 again in the sub menu which will let you boot into recovery. When you are in recovery, and plugged into your computer, you should be able to either flash or drag and drop like a flash drive on the the phone. Hope that helps a little bit.
Click to expand...
Click to collapse
I don't have T-Mobile. I have Verizon Wireless on the US996. Will that work?

PhoneBull said:
I don't have T-Mobile. I have Verizon Wireless on the US996. Will that work?
Click to expand...
Click to collapse
Since you are only rebooting into recovery and not flashing anything it might. If not, it will just fail and not harm anything. Last thing to try is the
Code:
adb reboot recovery
which is the only thing I can think of and I think you already tried it. Otherwise you will need to just go stock.

Back to stock, relock bootloader problem waiting for device

Hi,
i used Miflash in edl mode to get back to stock rom. after flash and reboot I used the recovery mode to do a factory reset.
It seems to work. It shows Android Recovery, but the bootloader is still unlocked.
What mode do I need to enter to use the "fastboot oem lock" command? I always see "waiting for device" and nothing happens
When I type "adb devices" I can see the phone. I saw there is a command "fastboot devices", too. but it shows me no result.

Stevie123 said:
Hi,
i used Miflash in edl mode to get back to stock rom. after flash and reboot I used the recovery mode to do a factory reset.
It seems to work. It shows Android Recovery, but the bootloader is still unlocked.
What mode do I need to enter to use the "fastboot oem lock" command? I always see "waiting for device" and nothing happens
When I type "adb devices" I can see the phone. I saw there is a command "fastboot devices", too. but it shows me no result.
Click to expand...
Click to collapse
Reboot to fastboot using
adb reboot fastboot
Click to expand...
Click to collapse
Then, try to use fastboot cmd

Thanks, before I can try that I have to solve another problem.

That doesn't work. The phone isn't entering a special mode. I can choose fastboot from the bootmenu, too. But nothing happens. The phone does a restart, shows the bootmenu again and boots android after 5 seconds.

@Stevie123
You need to enable fastboot (bootloader) mode since it is disabled by ZTE, so that the selection from menu to be effective (after enabling it, in fastboot mode, your command "fastboot devices" (to check) and "fastboot oem lock" (to lock bootloader) will be accepted).
You can use Axon 7 EDL tool to unlock the bootloader.

It's already unlocked. I have to make another unlock procedure again to get access to fastboot? The EDL Tool tells me that I have to wipe and reset the phone after it. So it seems I can't keep my data and just lock the bootloader.

Either Lock or Unlock will wipe your data. And yes, the unlock procedure by Axon 7 EDL tool includes the enabling of fastboot. So you have to re-unlock if you want to relock.

I think this EDL tool doesn't work very good. It flashed something to make fastboot available, but I had a green ZTE Logo screen and this screen also had errors like white spots. The original ZTE logo is in cyan. But the fastboot worked and I could lock the phone. But I couldn't do anything else anymore. I couldn't reach Android and reflashing also didn't work. So I tried to use the EDL Tool to unlock my bootloader again. It said success, but it didn't work. It was still locked.
Well, I had to wait until the phone was empty. Luckily I could reach EDL Mode again. I used the MiFlash again to Downgrade to Android Nougat B12. I read somewhere that the fastboot is included there. So I had the right ZTE Logo back and it worked. I could leave the Bootloader locked. The final update I did with a SD Card to the lastest Android Software for Axon 7. Luckily without a brick. It's a pity that they don't offer any Updates anymore.