Develop Bugs

Bricked Pixel C?

Hi all,
I recently picked up a new Pixel and was wanting to flash it. I ended up enabling USB debugging and set OEM unlock within Android settings.
Yet when I use fastboot flashing unlock, it keeps telling me that OEM unlock isn't set. In my haste, I ran flash-all with a new Google build and this overwrote the existing ROM, but left the bootloader intact it seems. Now when I boot, it says I have a damaged OS and I should use recovery. The problem is that even recovery is damaged and it keeps rebooting to the bootloader. So adb won't work either. The only thing that works is fastboot.
Is there anything I can do to fix this or is it completely bricked? I can't seem to use fastboot to flash any ROM to the device - keeps erroring. I tried to match a ROM with the bootloader but that didn't work either.
Any ideas?

I used Nexus Root Toolkit when I got semi-bricked.

Use erase Command on flashboot for data and system then do flash_all again

As was mentioned, if you have fastboot you are ok. You can flash as mentioned above or use this -
https://forum.xda-developers.com/showpost.php?p=70611434&postcount=78

NRT is good for people like me who barely know what they're doing, enough to get bricked in the first place like I did. What i like is that it takes away a little of the uncertainty about whether I'm using the right files.
I hadn't rooted and unlocked and done all the setup in about a year so I forgot everything.
Save yourself some trouble and look at the "TWRP bootloops" thread. It's easy to avoid if you follow some specific steps, frustrating otherwise.

Thanks all, but will this even work, given that the bootloader is still locked? I have no way of unlocking it via any fastboot commands. That's why I am completely stuck.
Will NRT do that somehow in a way that fastboot can't? If so, I'll go find a windows machine from somewhere (who still uses Windows!?)

hamazoza said:
Thanks all, but will this even work, given that the bootloader is still locked? I have no way of unlocking it via any fastboot commands. That's why I am completely stuck.
Will NRT do that somehow in a way that fastboot can't? If so, I'll go find a windows machine from somewhere (who still uses Windows!?)
Click to expand...
Click to collapse
Won't work IF bootloader is still locked. Try this command > fastboot continue
That will work with locked bootloader, but not sure if it'll solve your problem. Nothing to loose by trying...

hamazoza said:
Thanks all, but will this even work, given that the bootloader is still locked? I have no way of unlocking it via any fastboot commands. That's why I am completely stuck.
Will NRT do that somehow in a way that fastboot can't? If so, I'll go find a windows machine from somewhere (who still uses Windows!?)
Click to expand...
Click to collapse
Yes, you can unlock bootloader from fastboot.
Um...
fastboot oem unlock
Learn fastboot. It's your friend!
btw, you don't need it unlocked to flash the stock image!

d j a said:
Yes, you can unlock bootloader from fastboot.
Um...
fastboot oem unlock
Learn fastboot. It's your friend!
btw, you don't need it unlocked to flash the stock image!
Click to expand...
Click to collapse
Um...no You missed what I wrote in the first post - oem unlock (actually flashing unlock) doesn't work.
So how on earth do i flash the original image - I've tried to do that multiple times and it always fails.

cam30era said:
Won't work IF bootloader is still locked. Try this command > fastboot continue
That will work with locked bootloader, but not sure if it'll solve your problem. Nothing to loose by trying...
Click to expand...
Click to collapse
Yeah didn't think NRT would work because of the locked bootloader! Fastboot continue just gets out of fastboot - what is that gonna solve? I have a damaged set of partitions it seems - going from bootloader -> recovery boots back to the bootloader so it's clear that partition is damaged.
Is there any way I can just push some build to rebuild the partitions or can I do absolutely nothing until the bootloader is unlocked. And if so, how on earth can i unlock it if the only thing that works is fastboot?

hamazoza said:
Um...no You missed what I wrote in the first post - oem unlock (actually flashing unlock) doesn't work.
So how on earth do i flash the original image - I've tried to do that multiple times and it always fails.
Click to expand...
Click to collapse
Try this.
https://forum.xda-developers.com/showpost.php?p=70611434&postcount=78
You'll need to extract the system image and flash that.
fastboot -w update image-ryu-n4f26i.zip

d j a said:
Try this.
https://forum.xda-developers.com/showpost.php?p=70611434&postcount=78
You'll need to extract the system image and flash that.
fastboot -w update image-ryu-n4f26i.zip
Click to expand...
Click to collapse
I'll try that tonight. FWIW, I know I copied the line from flash-all to just flash recovery.img and even the system image, and both failed.
The only difference I see between that and yours is you have '-w update'. Maybe that's the trick.

d j a said:
Try this.
https://forum.xda-developers.com/showpost.php?p=70611434&postcount=78
You'll need to extract the system image and flash that.
fastboot -w update image-ryu-n4f26i.zip
Click to expand...
Click to collapse
So I tried that...no luck...it created the partitions and at the end, I get this error:
"erasing 'boot'...
FAILED (remote: unsupported command)
"

hamazoza said:
So I tried that...no luck...it created the partitions and at the end, I get this error:
"erasing 'boot'...
FAILED (remote: unsupported command)
"
Click to expand...
Click to collapse
Try the SkipSoft tool. You can download and flash the entire stock image using that and FASTBOOT.
https://forum.xda-developers.com/pi...tool-skipsoft-android-toolkit-google-t3277106

d j a said:
Try the SkipSoft tool. You can download and flash the entire stock image using that and FASTBOOT.
https://forum.xda-developers.com/pi...tool-skipsoft-android-toolkit-google-t3277106
Click to expand...
Click to collapse
I don't think that'll work. OEM unlock wasn't set in developer settings.

hamazoza said:
I don't think that'll work. OEM unlock wasn't set in developer settings.
Click to expand...
Click to collapse
You don't need that. I actually unlocked mine without it. The tool also has a unlock feature. Its worth a try.

Look for this forum post: flashing to stock android npd90g twrp t3424863
This helped me too. Only difference is I had TWRP installed.
Try unlocking bootloader via termjnal, then use the fastboot command via terminal (pc) fwtool vbnv write dev_boot_fastboot_full_cap 1 to reenable fastboot, then erase the partitions manually as mentioned in the tutorial and reflash them either manually or together using skipsoft / nrt or manual commands and a factory image.
Normally there should not be anything wrong with your bootloader image since modifying it is disabled for bootloader locked devices. Let us know about your progress.
Oh, also never flash an older system image than your current one.

Trying to Flash January OTA

I still haven't received the January Security Update, so i tried updating via the OTA. But i get the following error message. When i type adb reboot recovery. Its like my stock recovery is broken because i get a no command error. My phone isnt' recognized in win10 anymore. Anyone else having this issue? My bootloader is unlocked. Not sure why that would matter.

Tried flashing factory image. I can't install because my bootloader doesn't match. Any ideas? I'm wondering if the January update isn't ready for my phone version

It maybe a bad data cable I had the same issue kinda cable must have put out to much power or something next day I tried it and everything worked.
Adb wouldn't work but fastboot commands would sometimes then next day was able to do all the commands to root and install kernal
Sent from my Pixel 2 XL using Tapatalk

sjpritch25 said:
Tried flashing factory image. I can't install because my bootloader doesn't match. Any ideas? I'm wondering if the January update isn't ready for my phone version
Click to expand...
Click to collapse
The boot loader not matching usually means you did not fully unlock it. I would bet you did unlock, but skipped unlock critical. You need the second one to be able to flash the bootloader. Otherwise you can only flash the same bootloader.

sjpritch25 said:
Tried flashing factory image. I can't install because my bootloader doesn't match. Any ideas? I'm wondering if the January update isn't ready for my phone version
Click to expand...
Click to collapse
Saw this same issue with another user on another thread. First of all, do you have OEM unlocking and USB debugging turned on in developer options?
Did you already run BOTH bootloader unlocking commands?
Since your OTA and factory image flash didn't work, you'll need to go back to the factory image you were on before you started this process.
If your able to get this all accomplished, then you can proceed to the January update. Best of luck :good:

How do I go about fully unlocking the bootloader? My phone came with 8.0. I do recall that after unlocking I got the mo command booting into recovery.

I do have OEM unlocking turned on

sjpritch25 said:
I do have OEM unlocking turned on
Click to expand...
Click to collapse
And you ran both bootloader unlocking commands?
---------- Post added at 04:06 AM ---------- Previous post was at 04:00 AM ----------
sjpritch25 said:
I do have OEM unlocking turned on
Click to expand...
Click to collapse
You probably should read this thread my friend.
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418

Thanks. I see things I didn't do correct

I had to re flash december ota and now i just got done flashing January. Had to wipe phone again though to fix the unlocked bootloader.

sjpritch25 said:
I had to re flash december ota and now i just got done flashing January. Had to wipe phone again though to fix the unlocked bootloader.
Click to expand...
Click to collapse
unsuccessful updated to January image. I updated adb and still got the corrupt bootloader message. flashed december image and have a phone again. I guess, I might need to relock the bootloader and then unlock again? my current working bootloader is TMZ12a. The January image is TMZ12b i believe and for some reason its not working.

sjpritch25 said:
unsuccessful updated to January image. I updated adb and still got the corrupt bootloader message. flashed december image and have a phone again. I guess, I might need to relock the bootloader and then unlock again? my current working bootloader is TMZ12a. The January image is TMZ12b i believe and for some reason its not working.
Click to expand...
Click to collapse
In fastboot mode type
Fastboot oem device-info
Is unlock critical still locked?
If so, issue the command to unlock it. If that fails, yeah it looks like you will have to do what the other thread suggests and relock it.

sjpritch25 said:
I still haven't received the January Security Update, so i tried updating via the OTA. But i get the following error message. When i type adb reboot recovery. Its like my stock recovery is broken because i get a no command error. My phone isnt' recognized in win10 anymore. Anyone else having this issue? My bootloader is unlocked. Not sure why that would matter.
Click to expand...
Click to collapse
Don't do adb reboot recovery.
Turn it off, hold volume down, press power, and when bootloader screen shows, move volume button to choose Recovery.
When little green Android symbol shows, press Power, then Volume Up for a moment. You're now in Recovery.
Choose Apply Update from ADB, then follow instructions here: https://developers.google.com/android/ota
It will update you without wiping.

michaelbsheldon said:
Don't do adb reboot recovery.
Turn it off, hold volume down, press power, and when bootloader screen shows, move volume button to choose Recovery.
When little green Android symbol shows, press Power, then Volume Up for a moment. You're now in Recovery.
Choose Apply Update from ADB, then follow instructions here: https://developers.google.com/android/ota
It will update you without wiping.
Click to expand...
Click to collapse
Or adb reboot bootloader if you happen to be there but yes most of the time I just hit power to bring up restart then I hold volume down till it loads into bootloader
Sent from my Pixel 2 XL using Tapatalk

TonikJDK said:
In fastboot mode type
Fastboot oem device-info
Is unlock critical still locked?
If so, issue the command to unlock it. If that fails, yeah it looks like you will have to do what the other thread suggests and relock it.
Click to expand...
Click to collapse
I didn't have that & that was the issue earlier. I've done that & device was wiped again. Let me try those commands & I'll post them

TonikJDK said:
In fastboot mode type
Fastboot oem device-info
Is unlock critical still locked?
If so, issue the command to unlock it. If that fails, yeah it looks like you will have to do what the other thread suggests and relock it.
Click to expand...
Click to collapse
bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
OKAY [ 0.038s]
finished. total time: 0.048s

sjpritch25 said:
bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
OKAY [ 0.038s]
finished. total time: 0.048s
Click to expand...
Click to collapse
Download the full factory image. Not just the OTA. Open the flash-all.bat file and look near the end and edit out the -w and save it.
As long as you remove the -w that will flash the whole factory image but save your date, apps and set up.
So after the edit put it back in fastboot mode and run the flash-all.bat file.

Tried the January image & did that. Phone won't boot & I get corrupt message at bootlicker

sjpritch25 said:
Tried the January image & did that. Phone won't boot & I get corrupt message at bootlicker
Click to expand...
Click to collapse
Have you verified the sha-256 of the image you downloaded to ensure it's not corrupt?
Goto https://developers.google.com/android/images and copy the SHA-256 checksum from the Full Image you downloaded and compare it to the file downloaded here: http://onlinemd5.com/
- Make sure to choose sha-256 on the md5 site. This will rule out if the downloaded image you have is corrupted or not.

sjpritch25 said:
Tried the January image & did that. Phone won't boot & I get corrupt message at bootlicker
Click to expand...
Click to collapse
what version of adb/fastboot are you using ?
adb version
fastboot --version
---------- Post added at 04:53 PM ---------- Previous post was at 04:51 PM ----------
michaelbsheldon said:
Don't do adb reboot recovery.
Click to expand...
Click to collapse
Why should they not do that ?

Has any one successfull flashed update via doad volume up and down plus power

im trying to fix my device wondering has any one ever flased a update package via sdcard and dload mode mines fail at 5 percent everytime

same here...

this might be closest we have for 7x at this point
This is only for nougat . And after reading the guide few more times, I see it is incomplete.
https://androidcure.com/unbrick-honor-7x-variants-stock-firmware/
untill we can get a "service rom" for 7x "service rom" is apparently what is needed for dload to work.

pLaTiNiO said:
same here...
Click to expand...
Click to collapse
aye bro i just fixed my honor 7x finally i paid the dc pheonix and took the risk it didnt work but what it do was write to the devic e whille frp was locked so me being a semi genuis lol i set up my fastboot to flash twrp the dc pheonix program does sometype of backdoor fastboot trick i hurried up and flashed before the program started and unplugged my device and walla it succeded i got the program for 72 hours and im not no stingy nigga pm so you can fix yours too

dcraffam said:
aye bro i just fixed my honor 7x finally i paid the dc pheonix and took the risk it didnt work but what it do was write to the devic e whille frp was locked so me being a semi genuis lol i set up my fastboot to flash twrp the dc pheonix program does sometype of backdoor fastboot trick i hurried up and flashed before the program started and unplugged my device and walla it succeded i got the program for 72 hours and im not no stingy nigga pm so you can fix yours too
Click to expand...
Click to collapse
Oh man, there should have been this kind of post a while ago. I wanted to go completely stock on emui 8 stable as I was stuck on emui 8 beta and I trusted the dload method so I locked everything up stock recovery, BL relock etc... Now, the dload fails at 5% and my phone is as good as bricked.
Can you tell me about this DC tool? How much did it cost? Even if I'm able to get rid of that frp lock, I can unlock bootloader again and flash any rom I want.
---------- Post added at 02:26 AM ---------- Previous post was at 02:17 AM ----------
mrmazak said:
this might be closest we have for 7x at this point
This is only for nougat . And after reading the guide few more times, I see it is incomplete.
https://androidcure.com/unbrick-honor-7x-variants-stock-firmware/
untill we can get a "service rom" for 7x "service rom" is apparently what is needed for dload to work.
Click to expand...
Click to collapse
Hi, the guide never says "unlocked bootloader" so how does that Huawei tool installs twrp without Unlocked BL? Does it?
See, in my situation to unbrick my phone, all I need is to get that frp unlock. I can only do it by going into settings but my phone is all wiped out when I relocked the bootloader.
So, I saw your post in other thread about some command "fastboot frp-erase " "fastboot frp-unlcok unlock code" I know I don't remember the commands but my point is can we erase the frp with that command? or can we get frp unlock code from some service and unlock it? so I can simply Unlock BL by "fastboot oem unlock unlock code"?? I can get myself out of trouble by flashing any rom or twrp backup that I have. Now, my phone is as good as dead. Please reply!!

Thetpcguy said:
Oh man, there should have been this kind of post a while ago. I wanted to go completely stock on emui 8 stable as I was stuck on emui 8 beta and I trusted the dload method so I locked everything up stock recovery, BL relock etc... Now, the dload fails at 5% and my phone is as good as bricked.
Can you tell me about this DC tool? How much did it cost? Even if I'm able to get rid of that frp lock, I can unlock bootloader again and flash any rom I want.
---------- Post added at 02:26 AM ---------- Previous post was at 02:17 AM ----------
Hi, the guide never says "unlocked bootloader" so how does that Huawei tool installs twrp without Unlocked BL? Does it?
See, in my situation to unbrick my phone, all I need is to get that frp unlock. I can only do it by going into settings but my phone is all wiped out when I relocked the bootloader.
So, I saw your post in other thread about some command "fastboot frp-erase " "fastboot frp-unlcok unlock code" I know I don't remember the commands but my point is can we erase the frp with that command? or can we get frp unlock code from some service and unlock it? so I can simply Unlock BL by "fastboot oem unlock unlock code"?? I can get myself out of trouble by flashing any rom or twrp backup that I have. Now, my phone is as good as dead. Please reply!!
Click to expand...
Click to collapse
The DC tool is 15euros to use for 72 hours I still have it and you can use it if you want my bootloader was unlocked and frp locked but niether of those matter because the program does some back door fastboot trick to flash......... To restore your phone or at least get a working version of TWRP I recommend you install the DC tool configure the update app in the application for your device once all the files are extracted in the application it will try to flash and it will fail then it will say backdoor open and you have to have your CMD prompt ready to flash your TWRP so all you have to do is hit enter it will flash real quick then pull the cable from your phone and boot into TWRP and fix from there

(Re)lock bootloader on Huawei Mate 20x

Hello,
How can I relock bootloader on Mate 20x? I have EVR-L29.
Thanks!

Try this method
"How to Relock Bootloader via Fastboot
Setup ADB and Fastboot on your PC.
Connect your device to the PC, and open a command window on the PC.
Issue the following command to boot device into bootloader mode:
adb reboot bootloader
Now issue the following commands (any one) to relock bootloader. You don’t need to use all the commands given below. If any one works, stop there and follow the next step.
fastboot oem lock
fastboot flashing lock
fastboot oem relock
Once bootloader is locked. Reboot your device with the following command:
fastboot reboot"
Font: theandroidsoul com / relock-bootloader-fastboot-android /

thiagoserrao said:
Try this method
"How to Relock Bootloader via Fastboot
Setup ADB and Fastboot on your PC.
Connect your device to the PC, and open a command window on the PC.
Issue the following command to boot device into bootloader mode:
adb reboot bootloader
Now issue the following commands (any one) to relock bootloader. You don’t need to use all the commands given below. If any one works, stop there and follow the next step.
fastboot oem lock
fastboot flashing lock
fastboot oem relock
Once bootloader is locked. Reboot your device with the following command:
fastboot reboot"
Font: theandroidsoul com / relock-bootloader-fastboot-android /
Click to expand...
Click to collapse
On fastboot oem lock... I get "Command not allowed".
On the other 2... "root type is risk".
Not working.

same here

So... No method to lock the bootloader once it is unlocked?!

Update through OTG. It will relock bootloader.

alexcraciun said:
Update through OTG. It will relock bootloader.
Click to expand...
Click to collapse
any one can verify this method ?
greets, Peter

why would you want to relock when everyone is trying to unlock it?

the re-lock and un-lock bootloader function,
is it the same as the OEM lock and unlock option in developer mode ?
pardon me if this is a noob question but i really
TIA

How can i make an Full-OTA ? I have unlocked Bootloader, flash the stock erecovery back (with App Partitions Backup 2.2.1) and later i
flash the stock recovery over the twrp. And then ?
The erecovery download only the latest version (9.1.xxxx) but i like go back to my 9.0.xxxxx
in my dload directory i have three files: (its the 9.0.208 for EVR-L29)
update_sd_base.zip <- 3.7GB size
update_sd_cust_EVR-L29_hw_eu.zip
update_sd_preload_EVR-L29_hw_eu_R1.zip
What is now the next step ?
Update: dload-Method not function, long time at 5% and show "installing Update", then after 5 minutes : Reset!
greets, Peter

I am looking to buy unlocked bootloader evrL29.
So if you wish to lock before you sell it there are many people willing to buy unlocked

CCJ22 said:
I am looking to buy unlocked bootloader evrL29.
So if you wish to lock before you sell it there are many people willing to buy unlocked
Click to expand...
Click to collapse
sorry, sell my unlocked evr-l29 yesterday
greets, Peter

Anyone willing to sell unlocked bootloader EVR-L29 please DM me your price

alexcraciun said:
Hello,
How can I relock bootloader on Mate 20x? I have EVR-L29.
Thanks!
Click to expand...
Click to collapse
Relock your Bootloader with your Unlock Code.
Command:
fastboot oem relock your Code (16 character)
---------- Post added at 04:29 PM ---------- Previous post was at 04:23 PM ----------
greddy said:
How can i make an Full-OTA ? I have unlocked Bootloader, flash the stock erecovery back (with App Partitions Backup 2.2.1) and later i
flash the stock recovery over the twrp. And then ?
The erecovery download only the latest version (9.1.xxxx) but i like go back to my 9.0.xxxxx
in my dload directory i have three files: (its the 9.0.208 for EVR-L29)
update_sd_base.zip <- 3.7GB size
update_sd_cust_EVR-L29_hw_eu.zip
update_sd_preload_EVR-L29_hw_eu_R1.zip
What is now the next step ?
Update: dload-Method not function, long time at 5% and show "installing Update", then after 5 minutes : Reset!
greets, Peter
Click to expand...
Click to collapse
Use this File and Dload Method works
https://www.androidfilehost.com/?fid=6006931924117916589

letschky said:
Use this File and Dload Method works
Click to expand...
Click to collapse
Do I lose my data if I go back to 9.0?

KalleGermany said:
Do I lose my data if I go back to 9.0?
Click to expand...
Click to collapse
Yes,please Backup your Data!

i have a huawei mate 20 x emerald bootloader unlocked with resurrection remix rom running 9.0 android for sale
$250.00 good condition

BlvckSensei816 said:
i have a huawei mate 20 x emerald bootloader unlocked with resurrection remix rom running 9.0 android for sale
$250.00 good condition
Click to expand...
Click to collapse
No thank you.

The Only Thing Stopping Me From Rooting This Device...

So, I got this phone today, its a major upgrade... I got it to replace my oh so crappy a10e. Got really lucky, only 250 bucks and its like new.
Now, the only reason I haven't rooted it is I've realized there's 2 different fastboot's... Fastbootd and the bootloader
I looked into it, fastbootd can't unlock bootloader and all that. When I boot into bootloader where I should be able to flash it... No driver I've found for this device has let my computer see the phone in bootloader/fastboot mode.
Anyone know where the heck we can get the drivers for this? I've tried the "Add Legacy Drivers" and that didn't work either
Update on this: I got the pc to recognize it in Fastboot/bootloader, Fastbootd, recovery sideload and ADB. Some fastboot oem commands work, but none of the standard oem unlock methods work

Android 10 feature
Flash boot, recovery, dtbo, vbmeta, and super in fastbootd
All other operation on bootloader

if you ever get this device rooted please let us know. I'm waiting for a root on this device before I will purchase. You may have to unlock the bootloader or get a engineer bootloader before you can root this device. I'm not sure because I do not own one yet.
---------- Post added at 06:43 PM ---------- Previous post was at 06:29 PM ----------
Have you tried King root yet?