Develop Bugs

Stock unrooted and bricked? Help

So today I had a problem with an app not opening correctly so I rebooted the device. The device was stuck in the kit kat boot sequence. I turned it off and charged it. Tried booting to no avail. So I go into stock recovery mode and wiped cache and then proceeded to wipe/factory reset. It then got stuck on factory reset. I let it sit there on the charger for awhile and it was still stuck on factory reset. So i rebooted to attempt again. Now it won't even go into recovery mode. It'll boot to the fastboot screen but when trying to go into recovery it gets stuck on the white Google logo. Is there anything I can do or do I need to send it back? I bought it in July-ish so it should still be on warranty.

It should be easy to restore the stock ROM. Do you have the device drivers installed and a copy of fastboot?
http://developer.android.com/sdk/win-usb.html
http://www.xda-developers.com/andro...ng-fast-adb-fastboot-and-driver-installation/
Boot your Nexus 7 to the fastboot screen, then connect it to your PC. Open a command prompt window with administrator privileges, cd to the fastboot directory (let me know if you need help here), then type the following commands:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
This will wipe everything on your Nexus 7, preparing it for a full flash of the stock recovery and ROM. You can download the stock ROM from here, and there's a "flash-all.bat" file inside that will restore recovery and the ROM all by itself.
https://developers.google.com/android/nexus/images#razor

Pandae said:
It should be easy to restore the stock ROM. Do you have the device drivers installed and a copy of fastboot?
http://developer.android.com/sdk/win-usb.html
http://www.xda-developers.com/andro...ng-fast-adb-fastboot-and-driver-installation/
Boot your Nexus 7 to the fastboot screen, then connect it to your PC. Open a command prompt window with administrator privileges, cd to the fastboot directory (let me know if you need help here), then type the following commands:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
This will wipe everything on your Nexus 7, preparing it for a full flash of the stock recovery and ROM. You can download the stock ROM from here, and there's a "flash-all.bat" file inside that will restore recovery and the ROM all by itself.
https://developers.google.com/android/nexus/images#razor
Click to expand...
Click to collapse
when trying any commands in adb it says waiting for device and hangs on that.

Use adb if your tablet is booted into Android, and use fastboot if you're only at the bootloader.
Do you have the drivers installed? At a command prompt (again must be administrator permissions), type "fastboot devices" and see if it gives a response.

Pandae said:
Use adb if your tablet is booted into Android, and use fastboot if you're only at the bootloader.
Do you have the drivers installed? At a command prompt (again must be administrator permissions), type "fastboot devices" and see if it gives a response.
Click to expand...
Click to collapse
fastboot devices does nothing. I am in the fastboot directory. I thought I had the drivers installed, but in device manager it shows up as Android with an exclamation mark

OK, that explains it. Delete the driver by hitting Del, and just to be safe, click "View" at the top, then select to show hidden devices. Delete anything else that might be for any Android devices. Then install the drivers I linked to. They're generic drivers that work with either Nexus 7 generation, plus other Nexus devices.

Pandae said:
OK, that explains it. Delete the driver by hitting Del, and just to be safe, click "View" at the top, then select to show hidden devices. Delete anything else that might be for any Android devices. Then install the drivers I linked to. They're generic drivers that work with either Nexus 7 generation, plus other Nexus devices.
Click to expand...
Click to collapse
ok done now fastboot devices shows something, typed in fastboot erase boot and it says erasing boot...seems like it is stuck on this command

wildside84 said:
ok done now fastboot devices shows something, typed in fastboot erase boot and it says erasing boot...seems like it is stuck on this command
Click to expand...
Click to collapse
Couldn't you just try to boot a recovery IMG?
fastboot boot recovery path/to/recovery.img
That will let you run recovery without flashing it
Sent from my Nexus 7 using Tapatalk 4 Pro
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Erasing boot shouldn't take too long. Hopefully the partition isn't damaged.
SwoRNLeaDejZ, I believe he couldn't get into recovery. For problems like this, I like to erase recovery and everything else anyway, especially since flash-all.bat will restore stock recovery as part of the process.

Pandae said:
Erasing boot shouldn't take too long. Hopefully the partition isn't damaged.
SwoRNLeaDejZ, I believe he couldn't get into recovery. For problems like this, I like to erase recovery and everything else anyway, especially since flash-all.bat will restore stock recovery as part of the process.
Click to expand...
Click to collapse
no commands work. on erase recovery command it says failed command write failed invalid argument
edit: fastboot boot recovery fails also "command write failed unknown error"
edit: i get a lot of fastboot.exe has stopped working errors on windows. redownloaded platform tools and still happens. I'm at a loss I guess I have to get Google to replace it entirely

I may have taken something for granted. Did you unlock the bootloader?
fastboot oem unlock

Pandae said:
I may have taken something for granted. Did you unlock the bootloader?
fastboot oem unlock
Click to expand...
Click to collapse
no and whats funny is I just got done trying that before i read your message. i restarted the device and my computer and just decided to see if it would dirty flash the flash-all.bat and it was actually going through not giving the write errors but did say bootloader is locked. so i typed fastboot oem unlock and the screen popped up on the device to say yes or no. i selected yes and it, again, got stuck for 10-15 minutes on erasing data...rebooted the device, unlock appears to have failed. argh

If you power down and reboot back into the bootloader, it still says unlocked? What if you try unlocking again?

Pandae said:
If you power down and reboot back into the bootloader, it still says unlocked? What if you try unlocking again?
Click to expand...
Click to collapse
it says the bootloader is locked. i am trying again right now. i get to the yes no screen, select yes and on the command prompt it is stuck on erasing userdata

I've never seen it take very long. Let it sit for a while, maybe plug it in and just wait?

Pandae said:
I've never seen it take very long. Let it sit for a while, maybe plug it in and just wait?
Click to expand...
Click to collapse
ill let it sit, but i think there is something wrong with the device. i had a similar prob with a gs2 and it wouldnt erase or write anything to partition. would usb debugging have to have already been enabled? i cant remember if that was checked or not. or does that matter?

USB debugging is necessary for connecting once the tablet has booted into Android, but it isn't needed for fastboot and the bootloader level. At this point I fear there's more corruption than can be fixed, but let's wait a little while and see.

Pandae said:
USB debugging is necessary for connecting once the tablet has booted into Android, but it isn't needed for fastboot and the bootloader level. At this point I fear there's more corruption than can be fixed, but let's wait a little while and see.
Click to expand...
Click to collapse
Just received an email from Google support. They are unwilling to help because I purchased the device from Best Buy rather than Google Play...WTH? Best Buy won't help either I won't even bother. At this point I'll have to hope Asus will take it in for repair. That kind of bummed me out about Google. Not sure if I want to buy another nexus device again now.

wildside84 said:
no commands work. on erase recovery command it says failed command write failed invalid argument
edit: fastboot boot recovery fails also "command write failed unknown error"
edit: i get a lot of fastboot.exe has stopped working errors on windows. redownloaded platform tools and still happens. I'm at a loss I guess I have to get Google to replace it entirely
Click to expand...
Click to collapse
use usb jig and flash via odin nice work :good:

wildside84 said:
Just received an email from Google support. They are unwilling to help because I purchased the device from Best Buy rather than Google Play...WTH? Best Buy won't help either I won't even bother. At this point I'll have to hope Asus will take it in for repair. That kind of bummed me out about Google. Not sure if I want to buy another nexus device again now.
Click to expand...
Click to collapse
Is Google writing the book "How Not to Stand Behind Your Product"? Sheesh!
Sorry I couldn't be of more help. Good luck and speedy repairs to you. I must admit that with the touchscreen problems, and that it took someone who isn't a Google employee to fix it for a lot of people, all while Google is still silent, I myself don't care to buy another product by Google and/or Asus.
---------- Post added at 12:24 AM ---------- Previous post was at 12:18 AM ----------
VerlyAnanda said:
use usb jig and flash via odin nice work :good:
Click to expand...
Click to collapse
Odin is for Samsung devices, unless something's happened I didn't hear about.

The system has been destroyed

I was using the Mitool tool, and suddenly the machine shut down and the message "the system has been destroyed" appears and it does not start anymore, the only option I have access and the fastboot, would anyone have the solution?

ghtcp said:
I was using the Mitool tool, and suddenly the machine shut down and the message "the system has been destroyed" appears and it does not start anymore, the only option I have access and the fastboot, would anyone have the solution?
Click to expand...
Click to collapse
Is your bootloader unlocked?
Did the PC shut down or the phone?
If your bootloader is locked you will need to open the back of the phone and flash a new firmware with PC and pressing the test point on the inside of the phone.
If unlocked you can fastboot the firmware as you normally would

Dobsgw said:
If your bootloader is locked you will need to open the back of the phone and flash a new firmware with PC and pressing the test point on the inside of the phone.
Click to expand...
Click to collapse
You can flash images with Mi Flash on locked bootloader no problem.

marinespl said:
You can flash images with Mi Flash on locked bootloader no problem.
Click to expand...
Click to collapse
They can try but if recovery isn't accessible then fastboot is the only option and without unlocked bootloader you cannot use it.
Test point is then the only way.
Obviously its best to try flashing without opening the phone first.

marinespl said:
You can flash images with Mi Flash on locked bootloader no problem.
Click to expand...
Click to collapse
Wtf! You can't use mi flash tool unless your bootloader is unlocked

The problem was tense, but it's already been resolved. I find it hard to understand more I will try to explain.
-------------------------------------------------- ------------------------------------- 1º It was with the Global Beta rom and the bootloader unlocked and installing the TWRP for the mitool, however for lack of attention I selected the option to block the bootloader.
After confirming the bootloader block by mitool, the cell phone appeared the message "the system has been destroyed", and it was restarting on this same screen, the only option I had access was to the fastboot.
Since I had access to the fastboot, I tried to install the rom by the miflash only that it gave the message "remote: Erase is not allowed in loke state".
4º After despairing and thought to open the cell to do the testpoints method.
5º Since probably the bootloader had been blocked by the mitool, I decided to enter the site and ask Xiaomi to release the code to unlock the bootloader again.
6th I put the chip in another device and thanks to the holy protector of the cell phones Xiaomi quickly released the code, I did process to unlock the bootloader and the cell phone ran again.
-------------------------------------------------- -------------------------------------END

ghtcp said:
The problem was tense, but it's already been resolved. I find it hard to understand more I will try to explain.
-------------------------------------------------- ------------------------------------- 1º It was with the Global Beta rom and the bootloader unlocked and installing the TWRP for the mitool, however for lack of attention I selected the option to block the bootloader.
After confirming the bootloader block by mitool, the cell phone appeared the message "the system has been destroyed", and it was restarting on this same screen, the only option I had access was to the fastboot.
Since I had access to the fastboot, I tried to install the rom by the miflash only that it gave the message "remote: Erase is not allowed in loke state".
4º After despairing and thought to open the cell to do the testpoints method.
5º Since probably the bootloader had been blocked by the mitool, I decided to enter the site and ask Xiaomi to release the code to unlock the bootloader again.
6th I put the chip in another device and thanks to the holy protector of the cell phones Xiaomi quickly released the code, I did process to unlock the bootloader and the cell phone ran again.
-------------------------------------------------- -------------------------------------END
Click to expand...
Click to collapse
The bootloader gods have smiled upon you this time

Hello! I have locked bootloader with "fastboot oem lock". I was in panic, but randomly I press "Volume -" + "power-on" and my Mi A1 have loading in Fastboot mode, where I was able to unlock bootloader again.
Hope, this can help you.

HI there I also stuck in the same condition and it seems your phone's bootloader is locked now, this happens because you root the phone or installed custom libs or twrp in it and locked the bootloader. So unlocking the bootloader will fix this problem. You can unlock it by going into Fastboot mode (pressing power button + volume down (-) button) and then with platform tools you can unlock it again by typing "fastboot oem unlock" and then "reboot".
I hope this will help someone

same issue in redmi note 4
indersethi said:
HI there I also stuck in the same condition and it seems your phone's bootloader is locked now, this happens because you root the phone or installed custom libs or twrp in it and locked the bootloader. So unlocking the bootloader will fix this problem. You can unlock it by going into Fastboot mode (pressing power button + volume down (-) button) and then with platform tools you can unlock it again by typing "fastboot oem unlock" and then "reboot".
I hope this will help someone
Click to expand...
Click to collapse
After i flashed lots of roms in redmi note 4 there is no problem i have seen but, right now my device suddenly rebooted because of rooted and flashed imgs and it shows ''system has been detroyed''.I tried the commands using adb fastboot oem unlock then its shows ''token verification failed;i can only acess to fastboot. what i have to do now ??.....

Basilp275 said:
After i flashed lots of roms in redmi note 4 there is no problem i have seen but, right now my device suddenly rebooted because of rooted and flashed imgs and it shows ''system has been detroyed''.I tried the commands using adb fastboot oem unlock then its shows ''token verification failed;i can only acess to fastboot. what i have to do now ??.....
Click to expand...
Click to collapse
Reflash your rom with fastboot and hope you haven't messed up anything related to your data so you can still use and have access to it.

ccelik97 said:
Reflash your rom with fastboot and hope you haven't messed up anything related to your data so you can still use and have access to it.
Click to expand...
Click to collapse
Yes,it's worked

Basilp275 said:
Yes,it's worked
Click to expand...
Click to collapse
Cool then ?

I had the same problem today. my phone was distroed when I tried to install Gcam.
my phone was not unlocked so that the flash of the new stock of the ROM was not possible. The solution is to connect the phone to a PC in fastboot mode and from the platform tools in cmd to type fastboot oem unlock. After that, I did not have to have a flash phone. Everything worked as if I only had to backup the data.
now I have a new phone.
People, with Mi A1, cling to two things - slot A or slot B and lock or unlock. The easiest way to do this is a cardinal error.
Greetings.

Same thing happened to me. Had global rom with bootloader unlocked, then I installed TWRP and reinstall MIUI 10, as well as no-verity and Magisk. When installed the phone showed some issues with the proximity sensors so I decided to reinstall, after installing and booting MIUI showed a message, "the device is locked", I couldn't connect to the internet to unlock it, so I decided to do a fresh installation through miflash, after a couple attempts all of a sudden TWRP was not there anymore. Now the bootloader shows unlocked on '''fastboot oem device-info'''. Now the real problem: miflash doesn't work because bootloader is locked, I didn't unlocked it in the first place so I cannot do a fresh installation through miflash, when booting TWRP it shows the message, The system has been destroyed....
I tried miflash, fastboot oem unlock, fastboot recovery flash for TWRP, fastboot -w then fastboot flash recovery ....zip. Absolutely nothing is working.
How did you make it work exactly?

jesus4android said:
Same thing happened to me. Had global rom with bootloader unlocked, then I installed TWRP and reinstall MIUI 10, as well as no-verity and Magisk. When installed the phone showed some issues with the proximity sensors so I decided to reinstall, after installing and booting MIUI showed a message, "the device is locked", I couldn't connect to the internet to unlock it, so I decided to do a fresh installation through miflash, after a couple attempts all of a sudden TWRP was not there anymore. Now the bootloader shows unlocked on '''fastboot oem device-info'''. Now the real problem: miflash doesn't work because bootloader is locked, I didn't unlocked it in the first place so I cannot do a fresh installation through miflash, when booting TWRP it shows the message, The system has been destroyed....
I tried miflash, fastboot oem unlock, fastboot recovery flash for TWRP, fastboot -w then fastboot flash recovery ....zip. Absolutely nothing is working.
How did you make it work exactly?
Click to expand...
Click to collapse
With locked bootloader I got no chance to flash anything. Neither fastboot nor MiFlash - any solutions? Also would be helpful to enabke USB Debugging via fastboot. Anyone knows?

If you brick your device on the way as it happened to me... check: https://forum.xda-developers.com/showpost.php?p=77755947&postcount=11
These guys helped me unbricking my mi8 using EDL (Test Point) and Mi-flash!

I want to sell my Google Play app developer license.
Please email me or call me if you are interested.
phone - +917007797787
Email- [email protected]

I got a bricked Mi 6 from a friend. He was trying to flash firmware, and somehow messed up. Trying to boot normally or into recovery showed "The system has been destroyed". `fastboot continue` did not work. Bootloader was locked ( = no possibility to do fastboot oem unlock). On top of that, the phone only accepted fastboot commands right after the usb cable was connected ( => I had to run a fastboot command, like `fastboot getvar all`, fastboot would output `< waiting for any device >`, then I connected cable, and it would work). Running fastboot commands later resulted only in fastboot hanging / getting stuck, with no output, can not be terminated with ctrl+c unless cable was disconnected.
I got myself a windows computer (I use linux), tried to do bootloader unlock. Failed on "add your mi account in Settings -> Developer -> blablabla" - no way to do that with a bricked phone. Then I found out about EDL (Emergency download) mode. This is what worked.
The only way to get into the EDL mode in this state was the hardware way (shortcutting the pins / "PCB test points"). Search online for "mi 6 edl mode testpoints". Basically, you have to:
1. remove the rear cover
2. remove the screws on the plastic part above the battery, remove the plastic piece
3. disconnect the battery (shorter connector on the left side)
4. shortcut the pins using a tweezer (the pins are just above the battery connector)
5. while the pins are connected, connect the USB cable
6. check in device manager that you have "HS-USB QDloader 9008" in the COM devices
7. use mi flash tool to flash the fastboot firmware
The pins (from https://www.mobilerdx.com/2019/02/xiaomi-mi-6-test-points-xiaomi-mi-6-edl-mode-pinout.html):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And after you succeed, maybe unlock your bootloader, so that you don't have to do this again

How to relock bootloader

I unlocked bootloader using official app by Asus but now I want to relock it to be able to install OTA updates if anyone have any idea on how to relock bootloader kindly guide me with the process thank you.

Bump

chandru.biradar2 said:
I unlocked bootloader using official app by Asus but now I want to relock it to be able to install OTA updates if anyone have any idea on how to relock bootloader kindly guide me with the process thank you.
Click to expand...
Click to collapse
You can't relock but you can manually install captured ota packages...

chandru.biradar2 said:
I unlocked bootloader using official app by Asus but now I want to relock it to be able to install OTA updates if anyone have any idea on how to relock bootloader kindly guide me with the process thank you.
Click to expand...
Click to collapse
Same

MithunBeats said:
Same
Click to expand...
Click to collapse
If you. Get it solution please text here because am also stuck with bootloader unlocked warning

Indercheeda said:
If you. Get it solution please text here because am also stuck with bootloader unlocked warning
Click to expand...
Click to collapse
Ok sir

[ZS620KL] Relock bootloader?
I saw that the following commands will be able to relock the bootloader of the ZS620KL device:
fastboot flashing lock
fastboot flashing lock_critical
Click to expand...
Click to collapse
But it seems that the command is showing a permission error.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Does anyone know how to elevate the permission to do bootloader relocking?

Relock
peter_betos said:
I saw that the following commands will be able to relock the bootloader of the ZS620KL device:
But it seems that the command is showing a permission error.
Does anyone know how to elevate the permission to do bootloader relocking?
Click to expand...
Click to collapse
Am also stuck on it

Cheeda212 said:
Am also stuck on it
Click to expand...
Click to collapse
Can you guys please share if you find a solution on how to lock the bootloader back?

Does this needs a key of some sort? I see other manufacturers using a key before being permitted to execute these commands.
Sent from my ASUS_Z01RD using Tapatalk

Anyone found solution to relock bootloder on 5z?

did anyone find solution to relock bootloader on 5z? Pls help

Try
Fastboot oem asus_lock
or
Fastboot oem asus_lock 2>&1

how to lock bootloader
How to lock bootloader easily?!

Karma6069 said:
How to lock bootloader easily?!
Click to expand...
Click to collapse
I don't think locking bootloader is possible in 5z. Atleast not in direct methods.

ajbash007 said:
I don't think locking bootloader is possible in 5z. Atleast not in direct methods.
Click to expand...
Click to collapse
Process to downgrade ASUS ZENFONE 5Z to pie.
I HAVE ATTACHED THE RELOCK BOOTLOADER ARCHIVE.
ENJOY!
Step 1: Download this firmware on pc from the given link - https://dlcdnets.asus.com/…/WW-ZS620KL-90.11.162.111-MR5-us…
Step 2: Extract in pc
Step 3: boot your phone in fastboot mode and connect your device to pc
Step 4: Click on "updateimg.bat" file and let it go on.
After completing your phone will reboot and you will have successfully downgraded to pie.
NOTE: BACKUP YOUR DATA FIRST.
This method works well! I tried it and it worked! And also, big thanks to all involved, helping us! I even tried the relock method and it worked!
Relock bootloader After you have downgraded as instructed!
Be sure to backup all your data!
https://t.me/ASUSZenfone5ZGroup/244677
-extract
-boot phone to fastboot mode
-run the Step3xxxxx.bat file
-done
NOTE
IT WILL WIPE YOUR INTERNAL DATA

AllenConstantine said:
Process to downgrade ASUS ZENFONE 5Z to pie.
I HAVE ATTACHED THE RELOCK BOOTLOADER ARCHIVE.
ENJOY!
Step 1: Download this firmware on pc from the given link - https://dlcdnets.asus.com/…/WW-ZS620KL-90.11.162.111-MR5-us…
Step 2: Extract in pc
Step 3: boot your phone in fastboot mode and connect your device to pc
Step 4: Click on "updateimg.bat" file and let it go on.
After completing your phone will reboot and you will have successfully downgraded to pie.
NOTE: BACKUP YOUR DATA FIRST.
This method works well! I tried it and it worked! And also, big thanks to all involved, helping us! I even tried the relock method and it worked!
Relock bootloader After you have downgraded as instructed!
Be sure to backup all your data!
https://t.me/ASUSZenfone5ZGroup/244677
-extract
-boot phone to fastboot mode
-run the Step3xxxxx.bat file
-done
NOTE
IT WILL WIPE YOUR INTERNAL DATA
Click to expand...
Click to collapse
After entering fastboot how to run it?

Download the archive to your PC, and follow the instructions given.
Relock bootloader After you have downgraded as instructed!
Be sure to backup all your data!
-extract
-boot phone to fastboot mode
-run the Step3xxxxx.bat file
-done
NOTE
IT WILL WIPE YOUR INTERNAL DATA

AllenConstantine said:
Download the archive to your PC, and follow the instructions given.
Relock bootloader After you have downgraded as instructed!
Be sure to backup all your data!
-extract
-boot phone to fastboot mode
-run the Step3xxxxx.bat file
-done
NOTE
IT WILL WIPE YOUR INTERNAL DATA
Click to expand...
Click to collapse
My Zenfone is on stock Android 9
After entering fastboot idk what to do

I do not get your point, man! Seriously! I described what you should do. Download the relock bootloader rar file, put it in your pc and follow the instructions given. Sorry, but a child can do it!

Motorola z2 force flashing_locked and brick

I TRY TO BLOCK AGAIN THE BOOTLOADER OF MY Z2 FORCE BUT AT THE MOMENT OF DO IT MY PHONE IS BRICKE NOW I CAN NOT FLASH ANYTHING, AND I DO NOT KNOW HOW TO REMOVE THE FLASHING LOCKED

What is the state of your phone now? Does the PC recognize it?

HI
Yes bro , my pc recognize my phone i can still start flash mode but i try to relock my bootloader and my phone bricked
now i dont cant flash anythhing
and in the flashmode say flashing locked
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (9884 KB)...
OKAY [ 0.286s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) flash permission denied
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

ISRAELPS2002 said:
Yes bro , my pc recognize my phone i can still start flash mode but i try to relock my bootloader and my phone bricked
now i dont cant flash anythhing
and in the flashmode say flashing locked
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (9884 KB)...
OKAY [ 0.286s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) flash permission denied
Click to expand...
Click to collapse
Rerun the unlock process from fastboot. Hopefully you still have your unlock code.

Uzephi said:
Rerun the unlock process from fastboot. Hopefully you still have your unlock code.
Click to expand...
Click to collapse
C:\Program Files\Minimal ADB and Fastboot>fastboot oem unlock Q5CAKITVJDH2OFDQLF5F
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.014s]
finished. total time: 0.0
I can not activate the unlocking oem because this brick

ISRAELPS2002 said:
C:\Program Files\Minimal ADB and Fastboot>fastboot oem unlock Q5CAKITVJDH2OFDQLF5F
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.014s]
finished. total time: 0.0
I can not activate the unlocking oem because this brick
Click to expand...
Click to collapse
Have you tried flashing unlock?

Can you use LMSA restore?

I have same issue, did your problem solved?
how you did when flashing_locked device, and how fix it?

AHMN48 said:
I have same issue, did your problem solved?
how you did when flashing_locked device, and how fix it?
Click to expand...
Click to collapse
With a locked bootloader, you can only flash current or newer firmware for your variant. What is your varaint xt1789-?? Who is your carrier?
Once you're able to boot you need to be able to enable oem unlocking and adb, then you can unlock your bootloader again and get back to good.

41rw4lk said:
With a locked bootloader, you can only flash current or newer firmware for your variant. What is your varaint xt1789-?? Who is your carrier?
Once you're able to boot you need to be able to enable oem unlocking and adb, then you can unlock your bootloader again and get back to good.
Click to expand...
Click to collapse
My Phone is XT1789-05, I flashed Verizon, I thought it will work, but after flash when phone turned on, I locked the bootloader, then stuck in the Initial setup in Verizon welcome screen, everything works fine, but I can't skip step, this is the problem
Please wait, this may take a few minutes
I waited for 30 minutes, still same, I found QR setup, but can't find WIFI, I can't enter to OS for enable OEM unlock
so tell me, how can I flash current version or the newer version with locked bootloader?
I must flash XT1789-05 rom or Verizon I already installed?
tell me and help me, how can flash the current version?
thanks

AHMN48 said:
My Phone is XT1789-05, I flashed Verizon, I thought it will work, but after flash when phone turned on, I locked the bootloader, then stuck in the Initial setup in Verizon welcome screen, everything works fine, but I can't skip step, this is the problem
Please wait, this may take a few minutes
I waited for 30 minutes, still same, I found QR setup, but can't find WIFI, I can't enter to OS for enable OEM unlock
so tell me, how can I flash current version or the newer version with locked bootloader?
I must flash XT1789-05 rom or Verizon I already installed?
tell me and help me, how can flash the current version?
thanks
Click to expand...
Click to collapse
Do you remember what your original software channel was? Who was your provider? In the meantime, you can boot to recovery and do a factory reset to see if you can get past setup enough to get to settings. If that doesn't work hit fastboot and enter 'fastboot -w' to clear your data and see if that will let you work through setup. Did you by any chance flash a pie firmware?

41rw4lk said:
Do you remember what your original software channel was? Who was your provider? In the meantime, you can boot to recovery and do a factory reset to see if you can get past setup enough to get to settings. If that doesn't work hit fastboot and enter 'fastboot -w' to clear your data and see if that will let you work through setup. Did you by any chance flash a pie firmware?
Click to expand...
Click to collapse
Let me explain at first
I bought this Phone from coolicool.com, the China Website, Phone belong retcn
First of all I flashed to RETAIL Android 8 It was fine for a while, then I flashed to RETIN Android 9, but it was so buggy, then I saw in Internet people talking about Verizon firmware better than others, it makes temptation for me, so I flashed Verizon, when Phone successfully startup, and show Verizon Logo, Hello Animation and Language selector, I thought it's ok, let's Lock Bootloader, I locked bootloader, Now I'm in the Hell
I can access Bootloader and Recovery easily, phone startup fine, even I found QR setup in the startup but it needs WIFI, and I can't find any WIFI, there is any way?
1. Enter a fake or demo WIFI SSID to bypass WIFI section
2. There is any way to bypass Verizon (Please wait, this may take a few minutes)
3. how can I re-flash device?
4. it's possible to flash device through micro SD card?
5. there is any way to flash device via fastboot or recovery when the bootloader is locked?
6. there is any way to Unlock Bootloader or access setting in Android initial setup?
7. I saw https://www.youtube.com/watch?v=IWKXn2Vgkqo bypass android Wizzard, must be one way to bypass for Android 7 too?
please help me, please

AHMN48 said:
Let me explain at first
I bought this Phone from coolicool.com, the China Website, Phone belong retcn
First of all I flashed to RETAIL Android 8 It was fine for a while, then I flashed to RETIN Android 9, but it was so buggy, then I saw in Internet people talking about Verizon firmware better than others, it makes temptation for me, so I flashed Verizon, when Phone successfully startup, and show Verizon Logo, Hello Animation and Language selector, I thought it's ok, let's Lock Bootloader, I locked bootloader, Now I'm in the Hell
I can access Bootloader and Recovery easily, phone startup fine, even I found QR setup in the startup but it needs WIFI, and I can't find any WIFI, there is any way?
1. Enter a fake or demo WIFI SSID to bypass WIFI section
2. There is any way to bypass Verizon (Please wait, this may take a few minutes)
3. how can I re-flash device?
4. it's possible to flash device through micro SD card?
5. there is any way to flash device via fastboot or recovery when the bootloader is locked?
6. there is any way to Unlock Bootloader or access setting in Android initial setup?
7. I saw
bypass android Wizzard, must be one way to bypass for Android 7 too?
please help me, please
Click to expand...
Click to collapse
This is why you never relock. As said before you need to toggle unlock in settings to fix this and re-unlock the bootloader.

Uzephi said:
This is why you never relock. As said before you need to toggle unlock in settings to fix this and re-unlock the bootloader.
Click to expand...
Click to collapse
Dear, I can't enter to OS, how can I go to setting, when I can't enter to OS?
give me a solution for god sick
thanks a lot

AHMN48 said:
Dear, I can't enter to OS, how can I go to setting, when I can't enter to OS?
give me a solution for god sick
thanks a lot
Click to expand...
Click to collapse
If you can't, then you won't be able to fix this. Sorry, there isn't a magical fix to unlock

Uzephi said:
If you can't, then you won't be able to fix this. Sorry, there isn't a magical fix to unlock
Click to expand...
Click to collapse
give me a solution to bypass Android 8 Setup wizard, and there is should a way to fix this issue
help me thanks a lot

AHMN48 said:
Dear, I can't enter to OS, how can I go to setting, when I can't enter to OS?
give me a solution for god sick
thanks a lot
Click to expand...
Click to collapse
If you can't, then you won't be able to fix this. Sorry, there isn't a magical fix to unlock after you made modifications that made a no boot then relocked it. We have to find a way for you to boot. Most flash all most likely won't work but are with a shot if they are for your version.
---------- Post added at 06:52 PM ---------- Previous post was at 06:50 PM ----------
AHMN48 said:
give me a solution to bypass Android 8 Setup wizard, and there is should a way to fix this issue
help me thanks a lot
Click to expand...
Click to collapse
Your best bet is to try a USB-c Ethernet adapter. I know someone in this forum used it to get data. Bypassing setup isn't enough. You need to have some sort of network connection to toggle bootloader unlock in dev options.

Uzephi said:
If you can't, then you won't be able to fix this. Sorry, there isn't a magical fix to unlock after you made modifications that made a no boot then relocked it. We have to find a way for you to boot. Most flash all most likely won't work but are with a shot if they are for your version.
Click to expand...
Click to collapse
At least tell me how can flash the same version again?
or how can I bypass damn Android Wizard?
if I get ethernet Adaptor is it possible to bypass setup wizard and go to setting?
can I share the internet from the computer through USB?

Just Help me and tell me how can I bypass Android 8 Welcome Wizard?

If possible you should try and flash retail pie, not retin, retbr, plain old retail 9
Being flashing locked, with vzw firmware, you might not be able to, but try. Once you flashed pie, oreo went out the window.
You might try using the lenovo moto smart tool to rescue your phone, but who knows if it will recognize it or even what it will see the device as.
The OTG cable might be your last option.
Flashing Verizon was bad, locking the bootloader was worse, you're kind of up against it. There is no spoon.

Question Android 13 and unlocked bootloader

Hello,
Fist, I will say it, I am a total newbie in rooting. So, I followed one of the excellent guides here. Little by little, I begin to understand the process. So I have succeeded to root my pixel 6 pro using magisk.
Then, Android 13 has come. I think, pretty sure, that the bootloader need to be locked again to update. At least, I tried, I removed magisk and so the root, but the update fails.
Then I have reset the phone. Now I try to lock again the bootloader. However, withadb reboot bootloader, I cannot see the phone. fastboot devices shows nothing.
fastboot flashing lock stay on <waiting for any device>
Then I tried adb reboot fastboot. Here, the phone is found when I type fastboot devices. However fastboot flashing lock displays:
FAILED (remote: 'Unrecognized command flashing lock')
fastboot: error: Command failed
Click to expand...
Click to collapse
So, my questions:
1.) do I really need to lock the bootloader to update to android 13 ?
2.) what did I do as mistake ? I want to understand, especially if one day I need to sell the phone, I want to be able to lock again the bootloader. Is fastboot flashing lock the right command ?

Ralendil said:
Hello,
Fist, I will say it, I am a total newbie in rooting. So, I followed one of the excellent guides here. Little by little, I begin to understand the process. So I have succeeded to root my pixel 6 pro using magisk.
Then, Android 13 has come. I think, pretty sure, that the bootloader need to be locked again to update. At least, I tried, I removed magisk and so the root, but the update fails.
Then I have reset the phone. Now I try to lock again the bootloader. However, withadb reboot bootloader, I cannot see the phone. fastboot devices shows nothing.
fastboot flashing lock stay on <waiting for any device>
Then I tried adb reboot fastboot. Here, the phone is found when I type fastboot devices. However fastboot flashing lock displays:
So, my questions:
1.) do I really need to lock the bootloader to update to android 13 ?
2.) what did I do as mistake ? I want to understand, especially if one day I need to sell the phone, I want to be able to lock again the bootloader. Is fastboot flashing lock the right command ?
Click to expand...
Click to collapse
You don't need to do all of that to upgrade to android 13. You can read how to upgrade to android 13 here: https://forum.xda-developers.com/t/...-6-pro-bootloader-central-repository.4352027/
as well as here: https://forum.xda-developers.com/t/pixel-6-pro-easy-step-by-step-unlock-root-update.4361847/
it is a long thread with a lot of information, so I'll just give you an adlibbed version of how to upgrade
I read that you have removed root. You can re-root after upgrading. Make sure your bootloader is unlocked first.
First make sure you have the latest sdk platform tools version here: https://developer.android.com/studio/releases/platform-tools
Download the android 13 factory image here: https://developers.google.com/android/images
Extract the platform tools and the factory image, and make sure the flash-all.bat file is in the same location as adb.exe and fastboot.exe
If you want to keep your data, do this. If you don't want to lose your data and don't mind wiping your phone, skip this step and just run flash-all.bat in fastboot.
Edit the flash-all.bat file and remove the -w flag from the
Code:
fastboot update -w image-raven-tp1a.220624.021.zip
command. So it'll just be
Code:
fastboot update image-raven-tp1a.220624.021.zip
Save it, edit again just to double check that -w flag is gone. If it is, reboot your phone back into fastboot and run flash-all.bat.
It'll upgrade and do everything for you. You're on Android 13 now and your data is still intact.
Once your phone is booted, you can patch the boot image from the factory image you downloaded with Magisk and flash it in fastboot again by doing fastboot flash boot --slot=all (drag and drop patched boot.img here) OR type in the file name magisk_patched-xxxxxxxxxx.img. Then you will have root.
If you want to go back to complete factory with a locked bootloader, run Android Flash Tool from Google here: https://flash.android.com/welcome?continue=/back-to-public
Make sure "Wipe Device", "Lock Bootloader", and "Force Flash All Partitions" are checked.

You could always try the 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). It's possible you could also take advantage of it's new option to flash only the 13 bootloader to both slots, and then will update the current slot to 13 completely.
Lughnasadh said:
FYI: Even though Android Flash Tool does not flash the whole image to both slots, they have added an option to flash the A13 bootloader to the inactive slot. This may be the easiest option to use when updating to A13 from A12.
Just to be clear, when updating to A13 from A12 a prompt will show up asking whether you want to also flash the bootloader to the inactive slot as well. It doesn't show up in the regular tick boxes.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
FYI, you most definitely didn't need to re-lock the bootloader. Also, a pro tip for rooters. Once you unlock a device's bootloader, never ever re-lock it except in very rare circumstances. This didn't count as rare before you consult us.

I would have loved that it would be a solution.
It would allow me only to install android 12... and locking the bootloader make me affraid… I think I will never be able to unlock it cause I can’t use bootloader (see under)
For now, I try to make bootloader drivers working.
Every time I reboot to bootloader, the phone is not recognized by the computer and no adb/fastboot command can be used. So, I cannot use the flash-all.bat script.
Also, now when I use adb reboot fastboot the fastboot screen appears, then bootloader is loaded immediately...
I can’t believe I will spend several hours to be able to install that… I am stuck.
I tried to uninstall several drivers and reinstall drivers, but no changes... or yes a change. Now it is worst, Pixel 6 pro isn’t listed in device manager, and adb bootloader driver has disapear replaced by an adb driver line. Anyways, bootloader driver was never activated.
Edit: I should add that the update through the phone doesn’t work.
Don’t know why... the interface for google android flash tool changed... and now I was able to choose the version and I could flash the two slot with a13 bootloader.
Thanks for the idea...
Even if… I would love to understand why I did not succeed to install it...
Final edit: Android 13 has been successfully installed
Now, time to root it