Develop Bugs

ROM for Huawei Honor8 - FRD-AL10

Hi everyone! I have a real problem with my phone. I tried to update the OS of the EMUI and Android from the server and the system crashed and i don´t know why!!! It force me to try to update and when it try connect to server, the phone shows it can´t connect to server. Someone have the ROM for the chinese market version of the Huawei Honor 8 (FRD-AL10) please!!! I looked in YouTube and the only way to update it reinstall the firmware, i founded one but it´s not working good at all (don´t show the keyword for example).
I downloaded this ROM to the SD card and force to update EMUI by the SD.
If someone can explain me another way for update the phone or the firmware, please tell me!!! Thank you!!!

I believe you can find your firmware version here : https://forum.xda-developers.com/honor-8/how-to/stock-rom-frd-t3459293

wyldemdd said:
I believe you can find your firmware version here : https://forum.xda-developers.com/honor-8/how-to/stock-rom-frd-t3459293
Click to expand...
Click to collapse
Thank you very much. Can i ask you wich method did you use for updated this phone. I mean how do i install the update please??
Send me a YouTube video if you like.

Daligon said:
Thank you very much. Can i ask you wich method did you use for updated this phone. I mean how do i install the update please??
Send me a YouTube video if you like.
Click to expand...
Click to collapse
You can extract the UPDATE.APP from the zip file and create a dload folder with the UPDATE.APP in it and copy it to the SD card. I believe your recovery is stock so power off your phone, power on the phone while holding VOL+ & VOL-. You will see emui recovery and it will install the UPDATE.APP from the SD card. Once finish just reboot your phone.
if you have TWRP install, you may have to flash the phone with the original recovery image first. Extract the required "RECOVERY.img" from an original "UPDATE.APP" file using the Huawei Update Extractor and then flash it using fastboot:
Enable developer mode and connect via USB
adb reboot bootloader
fastboot flash recovery RECOVERY.img
Reboot
Then, created a "dload" folder on your SD card and placed the original "UPDATE.APP" inside. Unplug USB (important!) and reboot while holding Vol+ & Vol-. This should install the original firmware from your SD card. You will lose all your data!
Finally, you can lock your bootloader:
Enable developer mode and connect via USB
adb reboot bootloader
fastboot oem relock <YourPersonalUnlockCodeHere>
Reboot

wyldemdd said:
You can extract the UPDATE.APP from the zip file and create a dload folder with the UPDATE.APP in it and copy it to the SD card. I believe your recovery is stock so power off your phone, power on the phone while holding VOL+ & VOL-. You will see emui recovery and it will install the UPDATE.APP from the SD card. Once finish just reboot your phone.
if you have TWRP install, you may have to flash the phone with the original recovery image first. Extract the required "RECOVERY.img" from an original "UPDATE.APP" file using the Huawei Update Extractor and then flash it using fastboot:
Enable developer mode and connect via USB
adb reboot bootloader
fastboot flash recovery RECOVERY.img
Reboot
Then, created a "dload" folder on your SD card and placed the original "UPDATE.APP" inside. Unplug USB (important!) and reboot while holding Vol+ & Vol-. This should install the original firmware from your SD card. You will lose all your data!
Finally, you can lock your bootloader:
Enable developer mode and connect via USB
adb reboot bootloader
fastboot oem relock <YourPersonalUnlockCodeHere>
Reboot
Click to expand...
Click to collapse
Thank you very much for your response, I will review this information this weekend and see if it works for me.

Dear, try to run the update by the process of volume up and down to take from the SD but it was impossible, I still throw the error.
I wanted to ask if you know how to unlock the bootloader to be able to do it by ADB and watch videos on YouTube and try different bootloader unlocking processes but did not serve.

Daligon said:
Dear, try to run the update by the process of volume up and down to take from the SD but it was impossible, I still throw the error.
I wanted to ask if you know how to unlock the bootloader to be able to do it by ADB and watch videos on YouTube and try different bootloader unlocking processes but did not serve.
Click to expand...
Click to collapse
Did you get your unlock from Huawei website? If not then register an account here
Once you're registered, login to your account and go to this site and click on unlock. scroll down and tick the agreement and click next.
Insert all the required details and proceed. you will get your unlock code. Save the code and keep it incase your need to relock your bootloader.
make sure you have enable USB debugging and enable oem unlock, then connect your phone to PC. In Adb type adb reboot bootloader to boot to fastboot mode. when in fastboot mode in adb type fastboot oem unlock *unlock code*

My problem is that I can not start the S. O, this with fail and I can not do the OEM authorization from it, if not already had it unlocked easier from the same android entering the code that I have.
I need to know if there is any way to unlock the bootloader to be able to enter the code ADB, the problem is that when you login to bootloader is locked, I need to find the way to unblock it without having to enable the debugger and OEM that I'm not Being able to enable it because the system does not work.
Since without this I am seeing that the ADB does not start me. It throws me error when running the FastBoot

Nexus 7 update from 4.3

I just bought a brand new Nexus 7 16 GB wrapped in it's plastic unused. Charged it turned it on, as expected it's on 4.3.
Problem is when I check for updates it says the tablet is up to date and will not update to 6.0 which I believe is the latest this tab will go to.
Question is will this self correct if left on or will I need to manually update using OTA update from a PC. Also if I do need to manually update will I need to find and install every intervening update between 4.3 and 6.0?

It'll be easiest to use the factory image to flash it to 6.0.
If you go the OTA route you'd have to go through every update individually to get to 6.0.

fr4nk1yn said:
It'll be easiest to use the factory image to flash it to 6.0.
If you go the OTA route you'd have to go through every update individually to get to 6.0.
Click to expand...
Click to collapse
Thanks, Sorry to be a noob but how do I install a factory image?

telfish said:
Thanks, Sorry to be a noob but how do I install a factory image?
Click to expand...
Click to collapse
Download ADB from here and install: https://forum.xda-developers.com/showthread.php?t=2588979
Download the image, making sure you have the correct one. I'm assuming you have a Wi-Fi version so it would then be the "Razor": https://developers.google.com/android/images#razor
Boot into the bootloader by powering off, then holding the power and volume down buttons simultaneously.
Connect to your computer with the USB cable, open a CMD, or terminal, window and type fastboot oem unlock. That will wipe the device. I don't remember if it reboots automatically afterward. if so boot back into the bootloader the same as before.
Extract the system image. Open the extracted folder then if you're on Windows just double click the flash-all.bat file. after it's done it will ultimately reboot to Android.
-edit: If you're adventurous once in the bootloader you can flash TWRP and the Oreo Go ROM from here.

fr4nk1yn said:
Download ADB from here and install: https://forum.xda-developers.com/showthread.php?t=2588979
Download the image, making sure you have the correct one. I'm assuming you have a Wi-Fi version so it would then be the "Razor": https://developers.google.com/android/images#razor
Boot into the bootloader by powering off, then holding the power and volume down buttons simultaneously.
Connect to your computer with the USB cable, open a CMD, or terminal, window and type fastboot oem unlock. That will wipe the device. I don't remember if it reboots automatically afterward. if so boot back into the bootloader the same as before.
Extract the system image. Open the extracted folder then if you're on Windows just double click the flash-all.bat file. after it's done it will ultimately reboot to Android.
-edit: If you're adventurous once in the bootloader you can flash TWRP and the Oreo Go ROM from here.
Click to expand...
Click to collapse
Thanks so much, managed to get it to 6.1 and all is working fine.

Rooting pixel 2xl

I have a stock Pixel 2xl running android 10. Can't root it, no matter what i try. Any help would be greatly appreciated. Thanks

grunt0300 said:
I have a stock Pixel 2xl running android 10. Can't root it, no matter what i try. Any help would be greatly appreciated. Thanks
Click to expand...
Click to collapse
Is your bootloader unlocked?

Badger50 said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
Yes it is.

grunt0300 said:
Yes it is.
Click to expand...
Click to collapse
Ok. So you've installed the latest platform-tools on your pc?
Downloaded the factory image that coincides with your current build?
Extracted the factory image, then extracted the image.zip, and moved the boot.img to your phones internal storage?
Magisk manager is installed on your phone. Then you patched the boot.img, and then moved it to your pc platform-tools?
Put your phone into bootloader mode, opened a command prompt on you platform-tools folder, typed in "fastboot devices" to make sure your pc recognizes your phone?
Then fastbooted your patched boot.img to both slots with...
fastboot flash boot magisk_patched.img --slot=all
And then booted up with root?

What happens when you run the fastboot command "fastboot flashing unlock"?

Badger50 said:
Ok. So you've installed the latest platform-tools on your pc?
Downloaded the factory image that coincides with your current build?
Extracted the factory image, then extracted the image.zip, and moved the boot.img to your phones internal storage?
Magisk manager is installed on your phone. Then you patched the boot.img, and then moved it to your pc platform-tools?
Put your phone into bootloader mode, opened a command prompt on you platform-tools folder, typed in "fastboot devices" to make sure your pc recognizes your phone?
Then fastbooted your patched boot.img to both slots with...
fastboot flash boot magisk_patched.img --slot=all
And then booted up with root?
Click to expand...
Click to collapse
Sorry, i've been trying to root this phone all afternoon and i'm burnt out. Maybe tomorrow. Thanks

OK, i tried to root it again, and this is what i got....Your device is corrupt. It can't be trusted and may not work properly. The phone is not recognized by my pc. I can get into "bootloader mode", but can't do a thing with it. I could sure use some help. In the meantime, i'll pop the sim card into my trusty nexus 6, and wait to hear from one of you nice people. Thanks.

grunt0300 said:
OK, i tried to root it again, and this is what i got....Your device is corrupt. It can't be trusted and may not work properly. The phone is not recognized by my pc. I can get into "bootloader mode", but can't do a thing with it. I could sure use some help. In the meantime, i'll pop the sim card into my trusty nexus 6, and wait to hear from one of you nice people. Thanks.
Click to expand...
Click to collapse
Go to the guide in my signature, follow the step by step instructions there.
Make sure you have done the following:
-SDK tools are up to date,
-the proper platform folders are unzipped (there are two),
-you have a couple different USB cables handy.

Az Biker said:
Go to the guide in my signature, follow the step by step instructions there.
Make sure you have done the following:
-SDK tools are up to date,
-the proper platform folders are unzipped (there are two),
-you have a couple different USB cables handy.
Click to expand...
Click to collapse
I just put the sim card back into the pixel 2xl, and it booted up as if it was brand new. Plugged it into pc, got into bootloader mode, typed in command "adb devices", and it recognized the phone. I have all those files downloaded onto my desktop, so what's my next move?

grunt0300 said:
I just put the sim card back into the pixel 2xl, and it booted up as if it was brand new. Plugged it into pc, got into bootloader mode, typed in command "adb devices", and it recognized the phone. I have all those files downloaded onto my desktop, so what's my next move?
Click to expand...
Click to collapse
Like @Az Biker said, follow the guide in his signature :good:

Badger50 said:
Like @Az Biker said, follow the guide in his signature :good:
Click to expand...
Click to collapse
Doesn't work. I can't "fastboot" into anything. When i try, the pc stops recognizing the phone.

grunt0300 said:
Doesn't work. I can't "fastboot" into anything. When i try, the pc stops recognizing the phone.
Click to expand...
Click to collapse
Did you try a different usb cable? And you activated "developer options" and turned on usb debugging?
Also, try typing CMD in the url line from within the same platform tool folder where the platform tools application is located.

Az Biker said:
Did you try a different usb cable? And you activated "developer options" and turned on usb debugging?
Also, try typing CMD in the url line from within the same platform tool folder where the platform tools application is located.
Click to expand...
Click to collapse
OK, after waiting an hour, i tried typing into that command line that popped up within the platform tools folder. I tried adb devices, and my phone was recognized. Now, my phone is not in fastboot mode, and i don't have the sim card in it. What's my next move, please.

grunt0300 said:
OK, after waiting an hour, i tried typing into that command line that popped up within the platform tools folder. I tried adb devices, and my phone was recognized. Now, my phone is not in fastboot mode, and i don't have the sim card in it. What's my next move, please.
Click to expand...
Click to collapse
Have you patched the boot.img with magisk yet? If you look a few posts ago, I gave you exact instructions on how to patch and flash the modified boot.img
Also, adb devices is a command while your in your OS. You need to power off the phone, then enter bootloader mode manually by holding the power + volume down button until you enter the bootloader screen.
Then plug your phone in, open the command prompt on your platform-tools folder, and type in "fastboot devices". If you see your phone's ID number, then you have a good interface. Then you can fastboot the patched boot.img :good:
https://forum.xda-developers.com/pixel-2-xl/help/rooting-pixel-2xl-t4033453/post81455679

Badger50 said:
Have you patched the boot.img with magisk yet? If you look a few posts ago, I gave you exact instructions on how to patch and flash the modified boot.img
Also, adb devices is a command while your in your OS. You need to power off the phone, then enter bootloader mode manually by holding the power + volume down button until you enter the bootloader screen.
Then plug your phone in, open the command prompt on your platform-tools folder, and type in "fastboot devices". If you see your phone's ID number, then you have a good interface. Then you can fastboot the patched boot.img :good:
https://forum.xda-developers.com/pixel-2-xl/help/rooting-pixel-2xl-t4033453/post81455679
Click to expand...
Click to collapse
Can't get into "recovery mode". I have all the files in the file mgr on the phone. Do i have to put the sim card back into the phone in order for this to work?

grunt0300 said:
Can't get into "recovery mode". I have all the files in the file mgr on the phone. Do i have to put the sim card back into the phone in order for this to work?
Click to expand...
Click to collapse
Recovery mode? You need to be in bootloader mode. What files exactly do you have on your phone that your talking about? Just curious, but have you read through any of the directions that myself and @Az Biker have given you? Things seem to be getting lost in translation.

Badger50 said:
Recovery mode? You need to be in bootloader mode. What files exactly do you have on your phone that your talking about? Just curious, but have you read through any of the directions that myself and @Az Biker have given you? Things seem to be getting lost in translation.
Click to expand...
Click to collapse
Right now, i'm so confused that i don't know what day it is. I've got files all over my desktop. If i can get this phone up and running, i'll sell it and use the money towards a Note 9(USA version). I still have my rooted Nexus 6, and i NEVER had this trouble rooting it. Anyway, i'm done with this for now. If you want, i'll send you the Pixel 2xl, and when you get it working send it back to me, and we'll figure out the compensation. Thanks for trying.

grunt0300 said:
Right now, i'm so confused that i don't know what day it is. I've got files all over my desktop. If i can get this phone up and running, i'll sell it and use the money towards a Note 9(USA version). I still have my rooted Nexus 6, and i NEVER had this trouble rooting it. Anyway, i'm done with this for now. If you want, i'll send you the Pixel 2xl, and when you get it working send it back to me, and we'll figure out the compensation. Thanks for trying.
Click to expand...
Click to collapse
Please follow the step by step guide in my sig.
It explains EVERYTHING from step one all the way through the final reboot.
If your SDK tools are up to date (link provided), and your have multiple USB cables (trust me it's a known, unexplained issue) and you've unzipped the platform tools folder AND unzipped the second platform tool folder (this is the one where you type CMD in the url line) and then follow each step as written, you should have NO problem at all.
If you skip steps or go ahead using your own or another process there's no guarantee, but if you follow the steps in the guide, you should have no problems at all. This guide has been followed by myself and many others with ZERO issues, so I know the written process works.

Az Biker said:
Please follow the step by step guide in my sig.
It explains EVERYTHING from step one all the way through the final reboot.
If your SDK tools are up to date (link provided), and your have multiple USB cables (trust me it's a known, unexplained issue) and you've unzipped the platform tools folder AND unzipped the second platform tool folder (this is the one where you type CMD in the url line) and then follow each step as written, you should have NO problem at all.
If you skip steps or go ahead using your own or another process there's no guarantee, but if you follow the steps in the guide, you should have no problems at all. This guide has been followed by myself and many others with ZERO issues, so I know the written process works.
Click to expand...
Click to collapse
Did i mention that i already have android 10 on the phone?

grunt0300 said:
Did i mention that i already have android 10 on the phone?
Click to expand...
Click to collapse
The guide process works the same for 9x and Android 10.
In the guide, it is stated:
NOTE: On Android 10, when flashing TWRP Installer, kernels, magisk , etc. in TWRP, ignore the warning "FAILED TO MOUNT '/system' (invalid argument) this is a known issue with TWRP + 10 but affects nothing
Once you verify 'fastboot devices' on command prompt
Type flash-all to install factory image (allow it to install, and boot into system)
Hold vol down and power button to boot into bootloader
Fastboot into twrp 3.3.0-0.IMG
Flash the twrp installer 3.3.0-0.ZIP,
Flash Cust Kernel (I use Flash -not supported after 3.19 Nov 2018 or Sultan Kernel or Elemental X (EX) kernel) BE SURE TO SELECT THE CORRECT 9X OR ANDROID 10 KERNEL
Let the system boot up to verify.
Reboot back into twrp and flash latest magisk
Reboot to system
Profit
I guess I'm confused as to why you are simply not just following the guide from step one.........

[GUIDE] Relock bootloader (Should work in all versions)

Guide updated!!!!!
If you wanna get back to stock ROM and relock bootloader + get OTAs working again, this is the right place!
DISCLAIMER: Relocking bootloader erases all your data/internal storage and (off course) remove TWRP/modules/root, so do a backup of all your data first. Also, I'm not responsible for any bricked devices (phones, SD Cards, etc). I tested it in my XT1955-1 and it worked fine, but we all know that errors might occur.
Finally, let's go to the steps.
Step 1 - Downloading necessary files
Download Android Platform Tools here and then extract it.
Install Motorola Drivers on your PC (download here).
Download the lastest firmware according to your variant/software channel here and extract it in the same folder you had extracted Android Platform Tools.
Download the "Lock Script" here, according to your android version and PC's OS.
For example: if your PC uses Windows as OS, and your phone is in android 10, download the "Lock-10q_windows.bat" file.
Or if you have a Linux distro on your PC and android 9 on your phone, download "Lock-9pie_linux.sh" file.
Place the file inside the platform-tools folder, where the ROM was extracted too.
Step 2 - Preparing your phone
Remove all your google account in device's settings and then go to Developer Options. Enable Android debugging and OEM unlocking (if you can't enable OEM unlocking, you may need to root your device first to get it avaible again (see Rooting thread)).
Power off your phone and put it fastboot mode. Connect it on PC using USB cable.
Step 3 - Installing Stock ROM and re-locking bootloader
Just double click on the Lock.bat/.sh file and it will reflash stock ROM and lock bootloader. Now all you have to do is wait till it finishes. This should take a few minutes to be done.
The phone will boot automatically after the last command is executed.
It seems to be a little hard, but it's easy. If you have any questions, let me know, I'll try to answer ASAP.

Very nice, it's really working! Thanks!

Works on xt1955-4 thanks very much, will the warranty still apply?

piotr1859 said:
Works on xt1955-4 thanks very much, will the warranty still apply?
Click to expand...
Click to collapse
run
Code:
fastboot getvar all
Will tell you if warranty is voided.
Sent from my ali using XDA Labs

piotr1859 said:
Works on xt1955-4 thanks very much, will the warranty still apply?
Click to expand...
Click to collapse
Yes, should work fine. Afaik, once you unlock your bootloader, your warranty is avoid, theoretically. But I guess you can send it to service center (if it's needed) with no problems. They don't always check if you have unlocked your bootloader or not.

Warning: Due to some changes in bootloader and people getting hard bricks in February security patch, i don't recommend to relock bootloader in that version, do it in December security patch instead!

Hello guys. I have Motorola Moto G7 Power (XT1955-4). I've tried to put in twrp and a rom, but when I rebooted my device it don't power on anymore. So I've searched many guides to repair. I've used "blankflash" and after many times I was finally power on my device and go in Fastboot Mode. But now there's another problem. When I connect with usb and open CMD and type "adb devices" appear:
LIST OF DEVICES ATTACHED
or
WAITING FOR DEVICES
I tried many things to fix it but nothing work. Now I've uninstalled everything on my pc, drivers too.
Maybe I've installed bad "blankflash"???
How can I fix my troubles?

DarkAngelNoctis said:
Hello guys. I have Motorola Moto G7 Power (XT1955-4). I've tried to put in twrp and a rom, but when I rebooted my device it don't power on anymore. So I've searched many guides to repair. I've used "blankflash" and after many times I was finally power on my device and go in Fastboot Mode. But now there's another problem. When I connect with usb and open CMD and type "adb devices" appear:
LIST OF DEVICES ATTACHED
or
WAITING FOR DEVICES
I tried many things to fix it but nothing work. Now I've uninstalled everything on my pc, drivers too.
Maybe I've installed bad "blankflash"???
How can I fix my troubles?
Click to expand...
Click to collapse
If the device is in fastboot mode only fastboot commands will work
Code:
fastboot getvar all
edit:grammer
Sent from my ali using XDA Labs

sd_shadow said:
If the device is in fastboot mode only fastboot commands work like
Click to expand...
Click to collapse
Ok. Thanks!

LuisLFSS said:
Warning: Due to some changes in bootloader and people getting hard bricks in February security patch, i don't recommend to relock bootloader in that version, do it in December security patch instead!
Click to expand...
Click to collapse
hey would it be safe to use this method on security patch version April1,2020? if not please point me in the right direction.
thanks

darko454 said:
hey would it be safe to use this method on security patch version April1,2020? if not please point me in the right direction.
thanks
Click to expand...
Click to collapse
Yes, it's safe. Now we have blankflash so it's safe

LuisLFSS said:
Yes, it's safe. Now we have blankflash so it's safe
Click to expand...
Click to collapse
ok thanks!

LuisLFSS said:
Yes, it's safe. Now we have blankflash so it's safe
Click to expand...
Click to collapse
Hi, can you send a link to blankflash for XT1955-1?
THANK YOU.

hawkdown77 said:
Hi, can you send a link to blankflash for XT1955-1?
THANK YOU.
Click to expand...
Click to collapse
Yes, join in my group: t.me/motog7brasil

LuisF201707 said:
If you wanna get back to stock ROM and relock bootloader + get OTAs working again, this is the right place!
DISCLAIMER: Relocking bootloader erases all your data/internal storage and (off course) remove TWRP/modules/root, so do a backup of all your data first. Also, I'm not responsible for any bricked devices (phones, SD Cards, etc). I tested it in my XT1955-1 and it worked fine, but we all know that errors might occur.
Finally, let's go to the steps.
Step 1 - Downloading necessary files
Download Android Platform Tools here and then extract it.
Install Motorola Drivers on your PC (download here).
Download the lastest firmware according to your variant/software channel here and extract it in the same folder you had extracted Android Platform Tools.
Step 2 - Preparing your phone
Remove all your google account in device's settings and then go to Developer Options. Enable Android debugging and OEM unlocking (if you can't enable OEM unlocking, you may need to root your device first to get it avaible again (see Rooting thread)).
Power off your phone and put it fastboot mode. Connect it on PC using USB cable.
Step 3 - Installing Stock ROM
If you're already in stock ROM with no modules and stuff installed on it, just skip this and jump to the next step. If you're not, then stay here.
Open CMD (command prompt) in the same folder you had extracted firmware and android platform tools.
Shift+right click and then "Open command window here" or just type CMD in the folder path bar at the top in windows explorer. Run this commands all at once in CMD:
Once it is done, DON'T power on your phone, just leave it as it is and let's go to the last step.
Step 4 - Relocking Bootoader
In cmd, run this commands all at once
Done! The phone will boot automatically after the last command is executed.
It seems to be a little hard, but it's easy. If you have any questions, let me know, I'll try to answer ASAP.
Click to expand...
Click to collapse
There is an bat file out to relsash stock rom with out trying all that stuff in manually

Help
I followed all the steps and managed to block the bootloader but when I turn on the phone I get "start up failed" can someone help me.
I did it in the April 1 patch

JPalomo1997 said:
I followed all the steps and managed to block the bootloader but when I turn on the phone I get "start up failed" can someone help me.
I did it in the April 1 patch
Click to expand...
Click to collapse
Which android version? There's april security patch for android 9 and 10...

roadkill42 said:
There is an bat file out to relsash stock rom with out trying all that stuff in manually
Click to expand...
Click to collapse
I know... I'll update the thread soon

chrisbchrisb85 said:
For step 4 relocking the bootloader what does "run these commands all at once" mean??? As soon as I lock the bootloader I can no longer flash anything else, therefore still stuck with a boot screen warning
Click to expand...
Click to collapse
"run these commands all at once" = copy all the commands and execute them in cmd...
And which android version did you install? because the commands to flash android 10 are different than android 9 ones

Guide updated!!!!!
I removed those annoying commands and put a link to download Scripts that already do everything automatically. Now the guide is simpler and easier

Question Bricked my phone, please help!!!

I tried ro go back from beta 13 to public 12 and stuck on fastboot. I tried to sideload from recovery the 13 beta or the 12 version but it said error because i didnt opened the usb debugging before i stucked at fastboot(adb devices not recognize the phone) what can i do??? Please helpppp!!
Edit:Fixed!!

@avivasaf
Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own)

roirraW edor ehT said:
@avivasaf
Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own)
Click to expand...
Click to collapse
I tried it, it said oem unlocking is not checked, go to developer options, which i cant do

@avivasaf There may not be anything you can do to fix it, then. To fool around with Android Betas, you really should unlock the bootloader first so that you have more recovery options. Hopefully, someone else with more experience recovering from such a situation responds with some other ideas.

avivasaf said:
I tried it, it said oem unlocking is not checked, go to developer options, which i cant do
Click to expand...
Click to collapse
Device Unlock Disabled​For security reasons, you need to enable "OEM unlocking" in order to flash your device. See the device preparation instructions for more information.

avivasaf said:
I tried ro go back from beta 13 to public 12 and stuck on fastboot. I tried to sideload from recovery the 13 beta or the 12 version but it said error because i didnt opened the usb debugging before i stucked at fastboot(adb devices not recognize the phone) what can i do??? Please helpppp!!
Click to expand...
Click to collapse
Have you tried going into recovery and then scrolling down to wipe data/factory reset and doing that?

You might be able to sideload the beta again.
get the ota here as some people have claimed USB debugging or OEM unlock is not required to sideload
Boot into recovery (power > volume up > tap volume up when you see the android with an exclamation mark)
Right-click on the downloaded ota.zip and open an terminal in your adb folder (platform tools)
Code:
adb sideload "paste the path here"
It's worth a shot. Good luck

Lughnasadh said:
Have you tried going into recovery and then scrolling down to wipe data/factory reset and doing that?
Click to expand...
Click to collapse
Tried it, didn't help

fil3s said:
You might be able to sideload the beta again.
get the ota here as some people have claimed USB debugging or OEM unlock is not required to sideload
Boot into recovery (power > volume up > tap volume up when you see the android with an exclamation mark)
Right-click on the downloaded ota.zip and open an terminal in your adb folder (platform tools)
Code:
adb sideload "paste the path here"
It's worth a shot. Good luck
Click to expand...
Click to collapse
Its start 0% to sideload and stopped after 1 second"failed", in the phone "success 1"

avivasaf said:
Its start 0% to sideload and stopped after 1 second"failed", in the phone "success 1"
Click to expand...
Click to collapse
I don't understand that one. Sideloading should be possible, you just can't downgrade, should just be able to tap 'apply update from adb' in recovery mode and be good to go.
The first thing one should do when getting an android is enable USB debugging.

fil3s said:
I don't understand that one. Sideloading should be possible, you just can't downgrade, should just be able to tap 'apply update from adb' in recovery mode and be good to go.
The first thing one should do when getting an android is enable USB debugging.
Click to expand...
Click to collapse
I know that, but in my case its to late, any suggestions?

avivasaf said:
I know that, but in my case its to late, any suggestions?
Click to expand...
Click to collapse
I'm sorry mate. It might be a brick. I know its a crappy thing to hear, but it's one of those life lessons learned the hard way I guess.
All I would try to do is remove the device in device manager, install google USB driver in fastboot and try again.

You can try to use Google's flash tool (it's reportedly worked for some with even locked bootloaders) to get a booting device.
Android Flash Tool
flash.android.com
If you can't get your PC to recognize your P6P while it's in bootloader mode, and you're using Google's own USB driver (which is obviously recommended) for Windows, I had this very issue today. I solved it by abandoning the Google driver for clockworkmod's universal adb driver which after installation, allowed my PC to finally recognize my P6P in bootloader mode...

You might have to wait for Official Android 13 to drop with a locked bootlaoder

Fixed!!!
I downloaded the ota file! Not the one that didnt worked from beta program, the ota file could sideload and phone back to life!
After that used android flash tool to return to public Android 12

fil3s said:
You might be able to sideload the beta again.
get the ota here as some people have claimed USB debugging or OEM unlock is not required to sideload
Boot into recovery (power > volume up > tap volume up when you see the android with an exclamation mark)
Right-click on the downloaded ota.zip and open an terminal in your adb folder (platform tools)
Code:
adb sideload "paste the path here"
It's worth a shot. Good luck
Click to expand...
Click to collapse
Your ota file saved me, thanks alot

avivasaf said:
Your ota file saved me, thanks alot
Click to expand...
Click to collapse
I'm kind of confused. That OTA file that was linked to you is the same as the latest official one for A13 Betas. Were you just trying to sideload the wrong OTA file to begin with?
Btw, glad you got it going

Lughnasadh said:
I'm kind of confused. That OTA file that was linked to you is the same as the latest official one for A13 Betas. Were you just trying to sideload the wrong OTA file to begin with?
Btw, glad you got it going
Click to expand...
Click to collapse
There are 2 files the one that call ota is the one that saved me, the other one is the the one from beta program