Database Users

Nexus 7 Bricked??/Broken

Nexus 7 was rooted,unlocked bootloader and was running paranoid anroid 3.90+ i think . i plugged it into the computer to get a new rom using nexus root toolkit v1.7.2. i was asked to update a few things, so i clicked yes. i then tried to flash stock + unroot and chose 4.3 cause i wanted to try the new OS. but i guess something happened because when i turned my nexus 7 back on i was stuck on the load screen (GOOGLE image with a unlocked lock) i could cycle thru a few options using volume keys (start,recovery,power off) .all of them seemed useless as they would just bring me back to where i was.when clicking start "booting failed" come up on the upper left side. when trying to flash stock +unroot using NRT i get up to the sending "bootloader" part and my nexus 7 just freezes, how do i fix this. please and thanks

download the factory image from the google factory image and extract the archive.
try flashing the bootloader manualy with fastboot.
locate your fastboot binary and copy the bootloader image to that directory.
open a commandline in that directory and type
fastboot flash bootloader name-of-bootloader.img
after that you can try to flash the whole factory image with the flash-all.sh script.

Simple
dieselmonkeyy said:
i could cycle thru a few options using volume keys (start,recovery,power off) .all of them seemed useless as they would just bring me back to where i was.when clicking start "booting failed" come up on the upper left side.
Click to expand...
Click to collapse
Boot failed??? That's a bad flash of the stock ROM. I had the same problem at my first attempt trying to flash Stock ROM, but don't worry! Let's do this:
WARNING: Before you continue you are accepting that I'm not responsible of anything can happen to your Nexus and your battery is fully charged.
When you download the stock ROM you have to uncompress the zip file. You will find the bootloader and another zip.
Uncompress that zip file, put fastboot program, the bootloader and the files together.
Then start your Nexus into bootloader mode, connect it to your PC, open a console (cmd for Windows, Terminal for Linux and Mac OS X) and type this:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
WARNING: Your Nexus is FULLY EMPTY!!! Don't reboot it because it can get a full brick (It will not turn on any more).
Now type this:
fastboot flash bootloader bootloader-grouper-X.XX.img
NOTE: Replace X.XX with your version.
Now type:
fastboot reboot-bootloader
Your Nexus will reboot.
Type this:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img #Will take a very long time. DON'T INTERRUPT THE PROCESS!!!!!
fastboot flash userdata userdata.img
Now reboot again with:
fastboot reboot-bootloader
Re-unlock bootloader to get a full wipe:
fastboot oem lock
Reboot again:
fastboot reboot-bootloader
And then unlock the bootloader:
fastboot oem unlock
Press "Yes" to the petition screen and reboot:
fastboot reboot
Ready the Nexus!
I had the same problem and I did this.
I hope I can help you.
Sorry for my bad English. I'm from Argentina and I'm learning.
Well,
Good luck!

MlucianoEze said:
Boot failed??? That's a bad flash of the stock ROM. I had the same problem at my first attempt trying to flash Stock ROM, but don't worry! Let's do this:
WARNING: Before you continue you are accepting that I'm not responsible of anything can happen to your Nexus and your battery is fully charged.
When you download the stock ROM you have to uncompress the zip file. You will find the bootloader and another zip.
Uncompress that zip file, put fastboot program, the bootloader and the files together.
Then start your Nexus into bootloader mode, connect it to your PC, open a console (cmd for Windows, Terminal for Linux and Mac OS X) and type this:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
WARNING: Your Nexus is FULLY EMPTY!!! Don't reboot it because it can get a full brick (It will not turn on any more).
Now type this:
fastboot flash bootloader bootloader-grouper-X.XX.img
NOTE: Replace X.XX with your version.
Now type:
fastboot reboot-bootloader
Your Nexus will reboot.
Type this:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img #Will take a very long time. DON'T INTERRUPT THE PROCESS!!!!!
fastboot flash userdata userdata.img
Now reboot again with:
fastboot reboot-bootloader
Re-unlock bootloader to get a full wipe:
fastboot oem lock
Reboot again:
fastboot reboot-bootloader
And then unlock the bootloader:
fastboot oem unlock
Press "Yes" to the petition screen and reboot:
fastboot reboot
Ready the Nexus!
I had the same problem and I did this.
I hope I can help you.
Sorry for my bad English. I'm from Argentina and I'm learning.
Well,
Good luck!
Click to expand...
Click to collapse
what do i type into cmd inorder to be able to type
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
and get it to work. im a noob . thanks in advance

You have to be in the folder with fastboot inside else those commands will not work.
It will be easier if you put the images extracted from the zip into the zip together with the fastboot program.
If you don't understand yet I'll try to be more specific.
Sent from my Nexus 7 using xda app-developers app

dieselmonkeyy said:
what do i type into cmd inorder to be able to type
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
and get it to work. im a noob . thanks in advance
Click to expand...
Click to collapse
It can be intimidating... and the so-called tool-kits don't help you learn
I assume you are using Windows.
follow the unzip instructions from the previous poster. (not quoted here). note the directory.
find the directory containing your android tools... ADB.exe and FASTBOOT.exe.
transfer your unzipped files to this directory. Open your CMD prompt window and change to this directory if necessary.
plug in your Nexus.
type fastboot device at the prompt. MAKE SURE YOUR NEXUS 7 is listed (serial number)
proceed with the complete instructions from the previous poster.
that should do it.

YES!!!
thanks alot for the instructions, it worked!!! i hope people use ur instructions as reference if they have the same problem. THANKS ALOT!!!

dieselmonkeyy said:
thanks alot for the instructions, it worked!!! i hope people use ur instructions as reference if they have the same problem. THANKS ALOT!!!
Click to expand...
Click to collapse
I'm glad the problem is solved. Do not forget to click the THANKS button.
Sent from my Nexus 7 using xda app-developers app

Hello. My brother's Nex 7 is also has this issue. I cannot follow any of the steps as it gets stuck on erasing any of the partitions. I tried erasing those partitions in any order and they still get stuck. His device was stock and bootloader locked too. When I try to unlock the bootloader, it gets stuck as well at the erasing userdata part. I suspect a bad memory chip. Anyone else experience this?

Yes, mine is sticking on the (bootloader) erasing userdata on bootloader unlock as well.
It also sticks on any fastboot ERASE command.
Factory reset had a bunch of errors and no longer comes up. none of the FLASH commands work because the BOOTLOADER is locked.
And since it freezes on the unlocking bootloader commands I believe I am screwed.
This was a factory installed, never flashed, unlocked or rooted Nexus 7 wifi 2nd gen. After installing the 4.4.2 that popped up it loaded once then crashed and never loaded again
I have tried every tool I can find. They all stick on the erase part.

jophisdrazin said:
Yes, mine is sticking on the (bootloader) erasing userdata on bootloader unlock as well.
It also sticks on any fastboot ERASE command.
Factory reset had a bunch of errors and no longer comes up. none of the FLASH commands work because the BOOTLOADER is locked.
And since it freezes on the unlocking bootloader commands I believe I am screwed.
This was a factory installed, never flashed, unlocked or rooted Nexus 7 wifi 2nd gen. After installing the 4.4.2 that popped up it loaded once then crashed and never loaded again
I have tried every tool I can find. They all stick on the erase part.
Click to expand...
Click to collapse
Send your device for repair. My brother did so. My suspicions were correct. A faulty chip. They replaced the whole board, according to my brother.
Sent from my Nexus 7 using Tapatalk

Can not unlock bootloader 21s (oem unlock is not allowed)

I have followed the guides to the best of my ablity
This is the procedure I followed: From this thread
Have ADB/Fasboot tools on your computer (I am not helping you here, it you're lucky, maybe your friends will help)
Make sure you have enabled the developer tools, turned on USB debugging, and authorized your computer on your device (again, I'm not helping with that)
Make sure adb can see your device when you run "adb devices"
Run "adb reboot bootloader"
Run "fastboot devices" to make sure you see your device
Run "fastboot oem unlock-go" to unlock your device temporarily
FAILED (remote: oem unlock is not allowed)
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device product name: [le_zl1_oversea]
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Serial hw output enabled: false
(bootloader) Display panel:
OKAY [ 0.100s]
finished. total time: 0.100s
I then tried to downgrade to s19, but does not seem to work.
Anyway, if anyone has any ideas it would be welcomed, thank you

Is there an option you can turn on in dev options called "allow bootloader unlocks"? Because my mom's Le 2 has it and I assume it allows the unlock to go through. Are you on a vendor ROM? Flash the original stock Chinese 18s for your device.

Closest setting like that I have is the "OEM unlock" and I have it enabled

Well, did you have it enabled back when you were trying to unlock it? Because not having it enabled is usually what causes the unlock to fail.

Simple fix. You need to manually flash the emmc_appsboot.mbn from fastboot. You can get the file you need in the zip here: https://www.androidfilehost.com/?fid=313042859668275431
Code:
fastboot flash aboot emmc_appsboot.mbn
You may need to do the XBL as well:
Code:
fastboot flash xbl xbl.elf
Then
Run
Code:
fastboot reboot bootloader
and then
Code:
fastboot oem device-info
to verify.

slgooding said:
Simple fix. You need to manually flash the emmc_appsboot.mbn from fastboot. You can get the file you need in the zip here: https://www.androidfilehost.com/?fid=313042859668275431
Code:
fastboot flash aboot emmc_appsboot.mbn
You may need to do the XBL as well:
Code:
fastboot flash xbl xbl.elf
Then
Run
Code:
fastboot reboot bootloader
and then
Code:
fastboot oem device-info
to verify.
Click to expand...
Click to collapse
I will try this asap, thanks

Woot! that worked
Hey can i lock the bootloaded after I am done? I want to use like android pay and stuff
Well I figured out I can relock it, bit now my issue is when I am in fastboot mode adb does not see the device...
I installed the drivers, did not work....
Even went to my wife's laptop that I have never once plugged my phone in to... Installed adb, and plugged in the phone in fastboot... Still not being seen when I do an "adb devices"
I really want to use android pay

Don't understand
slgooding said:
Simple fix. You need to manually flash the emmc_appsboot.mbn from fastboot. You can get the file you need in the zip here: https://www.androidfilehost.com/?fid=313042859668275431
Code:
fastboot flash aboot emmc_appsboot.mbn
You may need to do the XBL as well:
Code:
fastboot flash xbl xbl.elf
Then
Run
Code:
fastboot reboot bootloader
and then
Code:
fastboot oem device-info
to verify.
Click to expand...
Click to collapse
Hi I know this is a older thread but I cannot get past the oem unlock is not allowed on my pro 3. I have all the drivers installed and the cmd recognizes my device but when I try to unlock I get the error. I downloaded the files you provided and when I try to insert from fastboot on command prompt it says the files is not recognized as internal or external command. I don't know what else to do at this point. Any help would be appreciated.

bobster82 said:
Hi I know this is a older thread but I cannot get past the oem unlock is not allowed on my pro 3. I have all the drivers installed and the cmd recognizes my device but when I try to unlock I get the error. I downloaded the files you provided and when I try to insert from fastboot on command prompt it says the files is not recognized as internal or external command. I don't know what else to do at this point. Any help would be appreciated.
Click to expand...
Click to collapse
Make sure ur files are in the right directory or cd to where they are.

bobster82 said:
Simple fix. You need to manually flash the emmc_appsboot.mbn from fastboot. You can get the file you need in the zip here: https://www.androidfilehost.com/?fid=313042859668275431
You may need to do the XBL as well:
Then
Run
and then
Hi I know this is a older thread but I cannot get past the oem unlock is not allowed on my pro 3. I have all the drivers installed and the cmd recognizes my device but when I try to unlock I get the error. I downloaded the files you provided and when I try to insert from fastboot on command prompt it says the files is not recognized as internal or external command. I don't know what else to do at this point. Any help would be appreciated.
Click to expand...
Click to collapse
You need adb installed on your computer.

You don't need adb installed, you just need platform-tools. https://www.xda-developers.com/install-adb-windows-macos-linux/
You usually have to preface every command with adb shell. So after enabling USB Debugging and connecting to your device (make sure to allow your PC on your phone when the prompt comes up), type adb shell fastboot flash aboot emmc_appsboot.mbn in the terminal.

thanks everyone. I tried everything suggested and nothing worked. I switched to my wifes computer witht he same files and seemed tp brick the pro 3. How in the world did I do this through adb?

bobster82 said:
thanks everyone. I tried everything suggested and nothing worked. I switched to my wifes computer witht he same files and seemed tp brick the pro 3. How in the world did I do this through adb?
Click to expand...
Click to collapse
Do you have fastboot yet if not you will have to try to unbrick it.
Which model do you have?
Sent from my LEX720 using xda premium

mchlbenner said:
Do you have fastboot yet if not you will have to try to unbrick it.
Which model do you have?
Sent from my LEX720 using xda premium
Click to expand...
Click to collapse
I dontI don't its bricked bricked. When I plug it in it comes up as hus9009 ..I have the US model 727

bobster82 said:
I dontI don't its bricked bricked. When I plug it in it comes up as hus9009 ..I have the US model 727
Click to expand...
Click to collapse
Power of push power down and volume down when you are plugged in to your PC.
Make sure you adb installed on your computer.
What did you flash on your phone.
Sent from my LEX720 using xda premium

mchlbenner said:
Power of push power down and volume down when you are plugged in to your PC.
Make sure you adb installed on your computer.
What did you flash on your phone.
Sent from my LEX720 using xda premium
Click to expand...
Click to collapse
see this the only thing I don't understand. I booted into fastboot and attempted to flash the files eemc and the xl files to unlock bootloader. The first try gave me an error and then the screen went black and has not come back on yet. No vibrations,no lights, no nothing.
---------- Post added at 05:09 PM ---------- Previous post was at 05:07 PM ----------
sk8223 said:
You don't need adb installed, you just need platform-tools. https://www.xda-developers.com/install-adb-windows-macos-linux/
You usually have to preface every command with adb shell. So after enabling USB Debugging and connecting to your device (make sure to allow your PC on your phone when the prompt comes up), type adb shell fastboot flash aboot emmc_appsboot.mbn in the terminal.
Click to expand...
Click to collapse
I had all the files you listed and followed to a T and for some reason it bricked my device. Any idea how to resurrect it?

bobster82 said:
I had all the files you listed and followed to a T and for some reason it bricked my device. Any idea how to resurrect it?
Click to expand...
Click to collapse
Well, I simply rephrased slgooding's post in this thread. See the first page. And by brick, I assume you only have fastboot working.
Try the other commands: https://forum.xda-developers.com/showpost.php?p=74123111&postcount=5

hey I got it unbricked by using the flash 2.0 method. The only thing is now its reading 720 instead of 727. Also When I get into FASTBOOT it says the bootloader is already unlocked but when I try put twrp recovery into the command prompts its telling me the image file is corrupt. What am I doing wrong with this adb command?

bobster82 said:
hey I got it unbricked by using the flash 2.0 method. The only thing is now its reading 720 instead of 727. Also When I get into FASTBOOT it says the bootloader is already unlocked but when I try put twrp recovery into the command prompts its telling me the image file is corrupt. What am I doing wrong with this adb command?
Click to expand...
Click to collapse
Make sure you have correct image recovery for your device.
Redo due unlocking commands you may have flash a bootloader on it.
What build are you on
Sent from my LEX727 using xda premium

mchlbenner said:
Make sure you have correct image recovery for your device.
Redo due unlocking commands you may have flash a bootloader on it.
What build are you on
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
Hi I made sure I downloaded the correct twrp recovery and when I command in prompt its telling me now that it cannot load the image error. the build is Le_zl1 -eng 6.0.1 WAXCNFN5841510281D eng.letv.
I'm almost fixing to give up cause no matter what I do I cannot get into twrp recovery

Help unable to relock the bootloader

I am trying to relock the bootloader in adb terminal by using command fastboot oem lock I get a message during boot stating that the system has been destroyed and boot loop.
How to relock bootloader with out flashing stock rom
Thanks in advance ?

Vishal21896 said:
I am trying to relock the bootloader in adb terminal by using command fastboot oem lock I get a message during boot stating that the system has been destroyed and boot loop.
How to relock bootloader with out flashing stock rom
Thanks in advance
Click to expand...
Click to collapse
use reflash tutorial from this site:
HTML:
https://xiaomifirmware.com/roms/download-official-roms-xiaomi-mi-a1/
. Just download tool, extract, then exctract downloaded rom in this tool folder. Conect A1 in fastboot and start flash_all_lock.bat file in folder with room (I used flash_all.bat). This is how I fixed my bootlops...

You need to reflash. There's no other way.

Did you have the original stock Oreo with January security patch?
I would also like to re-lock the bootloader but now I have read your post I am unsure if its safe.

Use this command in adb
fastboot oem relock (your unlock code if needed)

Youssef Reda said:
Use this command in adb
fastboot oem relock (your unlock code if needed)
Click to expand...
Click to collapse
If I enter fastboot oem relock with MagiskManager or Magisk 15.3 installed, will I brick the phone?

amzazine said:
If I enter fastboot oem relock with MagiskManager or Magisk 15.3 installed, will I brick the phone?
Click to expand...
Click to collapse
Maybe
I didn't try it but it may brick your phone

Developers should make clear that Re-locking the bootloader is not as easy as the unlock process and there is a high risk you will brick your phone.

i just have this issue ,which is i unlock then i lock the oem and then the message ' system has been destroyed ' and when i try to unlock back the message 'error: oem unlock is not allowed' so i really need your help ..how can i fix my phone ...plsss send a respond quickly

My PH-1 bricked ,I am so sad.What should I do?

question:
today I locked the booloader,but my PH-1 can't boot,it siad"Your devices is corrput,It can't be trusted and will not boot."
I use adb cant find devices.But it can use"fastboot decives".
"fastboot -w"is failed,the remote is "remote: Erase is not allowed in Lock State."
"fastboot flash boot.img" or "fastboot flash recovery twrp.img" also failed. the remote is "remote: Erase is not allowed in Lock State"
can anyone tell me how to get devices?
[IMG="https://drive.google.com/open?id=1cAIFNdksNV9-yUEQQBzwz7S1uDxgNhGp"]

[email protected] said:
question:
today I locked the booloader,but my PH-1 can't boot,it siad"Your devices is corrput,It can't be trusted and will not boot."
I use adb cant find devices.But it can use"fastboot decives".
"fastboot -w"is failed,the remote is "remote: Erase is not allowed in Lock State."
"fastboot flash boot.img" or "fastboot flash recovery twrp.img" also failed. the remote is "remote: Erase is not allowed in Lock State"
can anyone tell me how to get devices?
[IMG="https://drive.google.com/open?id=1cAIFNdksNV9-yUEQQBzwz7S1uDxgNhGp"]
Click to expand...
Click to collapse
Can you boot to recovery and factory reset?

ktmom said:
Can you boot to recovery and factory reset?
Click to expand...
Click to collapse
no,the phone can't do this

[email protected] said:
no,the phone can't do this
Click to expand...
Click to collapse
Have you tried unlocking again in fastboot?

ktmom said:
Have you tried unlocking again in fastboot?
Click to expand...
Click to collapse
Yes,but it failed. remote is Flashing Unlock is not allowed .

[email protected] said:
Yes,but it failed. remote is Flashing Unlock is not allowed .
Click to expand...
Click to collapse
It sounds like the OEM unlock was turned off in developer settings.
If you can't get to recovery and you can't boot to be able to unlock again, you're stuck [emoji17]

This is a warning to others. Don't lock bootloader. You can leave phone unrooted, no TWRP, and bootloader unlocked. It has the annoying warning splash screen with every reboot, but a lot safer than locking bootloader

HueyT said:
This is a warning to others. Don't lock bootloader. You can leave phone unrooted, no TWRP, and bootloader unlocked. It has the annoying warning splash screen with every reboot, but a lot safer than locking bootloader
Click to expand...
Click to collapse
Exactly. This has been highlighted many times - relocking the BL after unlocking it once is a bad idea...

Shoot me a msg I May Be of help

question:
today I locked the booloader,but my PH-1 can't boot,it siad"Your devices is corrput,It can't be trusted and will not boot."
I use adb cant find devices.But it can use"fastboot decives".
"fastboot -w"is failed,the remote is "remote: Erase is not allowed in Lock State."
"fastboot flash boot.img" or "fastboot flash recovery twrp.img" also failed. the remote is "remote: Erase is not allowed in Lock State"
can anyone tell me how to get devices?
Click to expand...
Click to collapse
For "Your devices is corrput,It can't be trusted and will not boot." Press power button?
Try
fastboot oem disable_dm_verity
Then
If able boot into recovery (hard reset button combination)
adb reboot "dm-verity enforcing"
Worth a shot ...

Aimless Rambler said:
For "Your devices is corrput,It can't be trusted and will not boot." Press power button?
Try
fastboot oem disable_dm_verity
Then
If able boot into recovery (hard reset button combination)
adb reboot "dm-verity enforcing"
Worth a shot ...
Click to expand...
Click to collapse
also failed……

Need help to root

hi, I'm trying to root my p9 lite to use it to run a 3d printing server ( https://github.com/d4rk50ul1/klipper-on-android )
I tried some rooting apps but it was unsuccesful.
after researching I used potatoNV to change the bootloader code
and SKR Tools to unlock bootloader and install twrp but i couldn't acces twrp via the phone. i locked back the bootloader with skr tools and now i can't get back to android, the phone is stuck on the " your device has been unlocked and can't be trusted. your device is booting now... " page, i left it like this for the nignt and it's not booting. I can't turn it off, My pc is not seeing it when pluged and I unpluged the battery for ten minutes but it's doing the same after replugging it .
what can i do to repair, root and use it ?

KilianBLRD said:
i locked back the bootloader with skr tools and now i can't get back to android,
Click to expand...
Click to collapse
you can relock bootloader only on clean stock firmware. If you did this on a modded system (TWRP installed etc.) you probably bricked the phone.

-Alf- said:
you can relock bootloader only on clean stock firmware. If you did this on a modded system (TWRP installed etc.) you probably bricked the phone.
Click to expand...
Click to collapse
what does this mean and what can i do ?

KilianBLRD said:
what does this mean and what can i do ?
Click to expand...
Click to collapse
A. Try your luck with testpoint & board software (check unfamiliar terminology by google or xda.
The instructions do not perform, if you do not know what you're doing.)
B. Use "DC-Phoenix" (paid service) .

-Alf- said:
A. Try your luck with testpoint & board software (check unfamiliar terminology by google or xda.
The instructions do not perform, if you do not know what you're doing.)
B. Use "DC-Phoenix" (paid service) .
Click to expand...
Click to collapse
I'm new to that, can you eplain a bit more please ?

Try to connect phone to PC in fastboot mode, run commands:
in fastboot mode run commands :
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
Some might fail, so don't worry about it.

-Alf- said:
Try to connect phone to PC in fastboot mode, run commands:
in fastboot mode run commands :
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
Some might fail, so don't worry about it.
Click to expand...
Click to collapse
my pc is not seeing the phone

Maybe it's brick when you try to relock but it's still bootloader unlocked Don't worry
You can fix it with 4 method
1. Flashing with board firmware
2.fastboot flashing method
3.sd card upgrade method
4.usb upgrade method

KilianBLRD said:
my pc is not seeing the phone
Click to expand...
Click to collapse
i know but try the following:
press and hold the Power + Vol Down buttons for at least 10 sec and when the screen turns off, connect the USB cable to the phone.

-Alf- said:
i know but try the following:
press and hold the Power + Vol Down buttons for at least 10 sec and when the screen turns off, connect the USB cable to the phone.
Click to expand...
Click to collapse
What should I do next ?

KilianBLRD said:
What should I do next ?
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/need-help-to-root.4571641/post-88366105

-Alf- said:
https://forum.xda-developers.com/t/need-help-to-root.4571641/post-88366105
Click to expand...
Click to collapse
But fastboot mode is not working

KilianBLRD said:
But fastboot mode is not working
Click to expand...
Click to collapse
Do I really have to repeat everything twice???
https://forum.xda-developers.com/t/need-help-to-root.4571641/post-88366083
Good luck!

-Alf- said:
Try to connect phone to PC in fastboot mode, run commands:
in fastboot mode run commands :
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
Some might fail, so don't worry about it.
Click to expand...
Click to collapse
it says waiting for device and nothing happen

KilianBLRD said:
it says waiting for device and nothing happen
Click to expand...
Click to collapse
to check that the connection to the computer in fastboot mode is established normally, type the command
fastboot devices
,the serial number of the phone should be displayed.
If not, you're not in fastboot mode.