Database Users

bricken N7, no OS installed

i was stuck in a bootloop after flashing a ROM, and didnt have any backups or other ROMs on the devices storage, so i was attempting to push files to it via ADB, but it wouldnt connect. i went back into the custom recovery image, and accidentally wiped the whole thing, so now i have no OS installed, and not even the seeminly 'faulty' ROM in /sdcard either. i can still get into the bootloader and the custom recovery, but cant seem to get it to connect to ADB. any ideas what i can do?

If you could boot into fastmode, then just flash stock rom.

Leonhan said:
If you could boot into fastmode, then just flash stock rom.
Click to expand...
Click to collapse
how do i boot into fastmode? all that i can access is the bootloader, and TWRP. when on the bootloader screen it sort of connects to my PC. i can go into device manager, and will see 'android bootloader interface' in there, and i have updated the drivers as per the instructions in the nexus root toolkit, but it wont seem to talk to ADB for some reason.
edit: ok, this is really odd. when i use the NRT to try pushing a zip file, if i start the it trying to push the file, then open a command line and use 'adb usb' NRT will say that it has connected to the device, and goes through its various steps, and ends up booting the device into recovery, but the actual zip it was supossed to have pushed isnt there...
it made it enter twrp, so it must be communicating in some way, but when i type 'adb devices' it doesnt show up...

bmoreyce said:
how do i boot into fastmode? all that i can access is the bootloader, and TWRP. when on the bootloader screen it sort of connects to my PC. i can go into device manager, and will see 'android bootloader interface' in there, and i have updated the drivers as per the instructions in the nexus root toolkit, but it wont seem to talk to ADB for some reason.
edit: ok, this is really odd. when i use the NRT to try pushing a zip file, if i start the it trying to push the file, then open a command line and use 'adb usb' NRT will say that it has connected to the device, and goes through its various steps, and ends up booting the device into recovery, but the actual zip it was supossed to have pushed isnt there...
it made it enter twrp, so it must be communicating in some way, but when i type 'adb devices' it doesnt show up...
Click to expand...
Click to collapse
Stop using the toolkit and read the sticky that's not too far above your post... the one titled, "[GUIDE] Flashing a Factory Image with fastboot / return to stock." Coincidentally, it happens to be exactly what you need.

najaboy said:
Stop using the toolkit and read the sticky that's not too far above your post... the one titled, "[GUIDE] Flashing a Factory Image with fastboot / return to stock." Coincidentally, it happens to be exactly what you need.
Click to expand...
Click to collapse
when i use ADB in a cmd window, it just says theres nothing connected. ive downloaded the stock image, and am currently writing it using the toolkits function, and it seems to be working so far, whereas doing it the other way, i cant seem to even get ADB to work. no idea whats going on, but it seems to be working with the toolkit
EDIT: the toolkit worked. am back on stock. thanks for your help guys.

bmoreyce said:
when i use ADB in a cmd window, it just says theres nothing connected. ive downloaded the stock image, and am currently writing it using the toolkits function, and it seems to be working so far, whereas doing it the other way, i cant seem to even get ADB to work. no idea whats going on, but it seems to be working with the toolkit
EDIT: the toolkit worked. am back on stock. thanks for your help guys.
Click to expand...
Click to collapse
You don't need ADB if you are in the bootloader- you use fastboot.

[Q] Help please--Nexus stuck on bootloader

I am a noob at android--just putting that out there. But trying...
I just received my new nexus 7 2013. I used Wugfresh's version 1.6.6 toolkit to backup the nexus prior to unlocking it, and then the plan was to root it. Something happened in the process--can't say for certain what, but at some point the tool brought up TWRP on the nexus and a file that the tool said was supposed to be there, wasn't. The end result now is that my nexus is stuck on the bootloader. None of the buttons seem to work, other than restart bootloader. Turn off DOES turn off the nexus, but then when pressed again, goes right back to the bootloader. The recovery one flashes the screen quickly, then goes back to the bootloader. The Start option makes it so the screen shows the "Google" icon indefinitely with the unlocked lock icon. I need to note that the option to get into the bootloader (power + vol up and vol down) did not work for me—the only way I was able to go into the bootloader was the power and vol down. Currently though, pressing the power button makes the nexus go directly into the bootloader.
When plugged into computer via the usb cord, windows xp currently doesn't recognize anything is plugged in, although I do have the latest USB drivers installed.
I downloaded and ran SDK and went through the various fastboot commands from within a cmd window. The fastboot devices command does bring up a device number, so it is recognized by fastboot.
Here's where others will start to shake their heads in bewilderment...in my haste to try and get this up and working and out of the endless bootloader menu, I *could* have flashed it with the nexus 7 2012 recovery image, because when using fastboot to do so, at end says something about grouper and my device says flo (although nothing changed with the nexus—as in there are no obvious changes as still in bootloader). I am aware that the official flo factory image is not yet available, although at this point, I don’t have much confidence in that doing anything.
If I open up Wugfresh’s Toolkit, I can’t do anything with it, as it says that ADB doesn’t work or something and to enable USB debugging, which I can’t do because I’m stuck on the bootloader.
I don't know where to go from here--I don't know if the device is salvageable or if it is completely toast and I should just return it and get another one...I see that in the day since I downloaded Wugfresh’s Toolkit, he has released two more versions—not sure if the new version can do anything—haven’t tried yet. Can anyone with more knowledge than myself give me a hand or some advice? Thanks in advance.

You first need to have the bootloader unlocked before flashing any custom recovery to make a nandroid backup.

Username invalid said:
You first need to have the bootloader unlocked before flashing any custom recovery to make a nandroid backup.
Click to expand...
Click to collapse
it is unlocked. I am able to use the fastboot commands to unlock and lock. it currently is unlocked.

Easiest thing to do is just flash back to stock and start over.
Grab the zip file from here. It has the stock rom, stock recovery, and stock boot that you need.
You can either run the .bat file, or issue the commands yourself:
fastboot oem unlock
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot -w

"I used Wugfresh's version 1.6.6 toolkit to backup the nexus prior to unlocking it" which I assumed you meant you tried to make a nandroid backup before unlocking.

Username invalid said:
"I used Wugfresh's version 1.6.6 toolkit to backup the nexus prior to unlocking it" which I assumed you meant you tried to make a nandroid backup before unlocking.
Click to expand...
Click to collapse
I will try the one click factory restore method posted by Geodude when I get home from work--at this point I have nothing to lose.
And Username invalid, sorry, no nandroid backup--by backup I meant just the basic backup of settings that are shown on Wugfresh's Toolkit.
Hopefully the one click restore will work....thank you very much.

busdonic said:
I will try the one click factory restore method posted by Geodude when I get home from work--at this point I have nothing to lose.
And Username invalid, sorry, no nandroid backup--by backup I meant just the basic backup of settings that are shown on Wugfresh's Toolkit.
Hopefully the one click restore will work....thank you very much.
Click to expand...
Click to collapse
I assumed that as doing an app and setting backup on a brand new device does not seem to make much sense.

Username invalid said:
I assumed that as doing an app and setting backup on a brand new device does not seem to make much sense.
Click to expand...
Click to collapse
Yeah, I see that....not sure why I did it myself actually, cuz now that you mentioned it, does seem pretty stupid--I guess that explains why I'm here asking for advice
I'm assuming that the one click restore will work. If it doesn't, I think I found a non-official flo factory image. I think (?) if I flash that to the tablet in fastboot, that will restore it, or at least get it past either the bootloader menu or past the Google icon shown at startup.

Geodude074 said:
Easiest thing to do is just flash back to stock and start over.
Grab the zip file from here. It has the stock rom, stock recovery, and stock boot that you need.
You can either run the .bat file, or issue the commands yourself:
fastboot oem unlock
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot -w
Click to expand...
Click to collapse
this worked--thanks much. Am much relieved to be up and running again....

Nexus 7 2012 (GSM) Booting Failed/No OS

i have access to ADB and fastboot mode.
i also try google factory image(see the attach picture for the result)

niceguy01 said:
i have access to ADB and fastboot mode.
i also try google factory image(see the attach picture for the result)
Click to expand...
Click to collapse
Yes, me too. I can't load anything except ADB & Fastboot. I used the Nexus 7 Toolkit to try to update to Kit Kat and now I have a soft bricked device. HELP!!!:crying:

Have you tried using adb shell command prompt to push the files to your device instead of a root toolkit?

cr0wnest said:
Have you tried using adb shell command prompt to push the files to your device instead of a root toolkit?
Click to expand...
Click to collapse
what file do i need to push in my device??

Effing toolkits again. When will they be banned for once and for all?
Oh that's right. They bring in ad revenue from lazy people.
Sent from my Nexus 5

niceguy01 said:
what file do i need to push in my device??
Click to expand...
Click to collapse
Check out this sticky here, it gives instructions on how to do it and what files are required. Its quite a lengthy guide, but its the safest method. http://forum.xda-developers.com/showthread.php?t=1907796

Pirateghost said:
Effing toolkits again. When will they be banned for once and for all?
Oh that's right. They bring in ad revenue from lazy people.
Sent from my Nexus 5
Click to expand...
Click to collapse
sorry im just a newbie:angel:

UPDATE: booting failed already gone by flashing cyanogen rom
the problem now is stuck in booting.see the attach picture
what is the meaning of
archive does not contain boot.sig
archive does not contain recovery.sig
archive does not contain system.sig

Got the same problem...I used RTK to flash 4.4 and ended up with a soft bricked N7.
Well initially I haven't been able to update any newer versions of CM. I was stuck on 10.2 nightly. I got a notification that there's an update so I downloaded it and tried installing. I get stuck when my N7 will go into recovery, I'll always get the droid with the red exclamation point and I have to stop the update. But I will always be able to do a system reboot and use the N7. After flashing using the RTK, all I can do is boot into the Bootloader mode. Choice at that point it Recovery, Reboot Recovert, Reboot Bootloader and Power Off. If I choose Recovery nothing happens. So the real choice is only to power off or reboot the bootloader.
I tried using fast boot but the guide I got was asking me to put the tablet in debugging mode (which I can't really do). And I get an error when doing the steps in CMD. I think I wasn't able to properly load the drivers because I am not seeing my device listed with serial number when I run >dab devices.
Kindda stuck and waiting where this thread will lead to as well so I can fix my N7.
Also, when I get the factory image (JWR66V) and run 7-zip on it, I don't see these files: bootloader-grouper-4.23.img, image-nakasi-jwr66y.zip, flash-all.sh, flash-base.sh. I only see 1 file.

As mentioned in about 5 billion threads, USB debugging has nothing to do outside of a booted OS.
Fix your drivers.
Unzip the factory image archive.
Sent from my Nexus 5

^Fixed my drivers (via SDK). PC recognised the device via fast boot devices. Ran a set of commands fast boot erase boot, cache, recovery, system, and user data. Flashed boot loader and reboot boot loader. Flashed 4.3 factory image (extracted via 7zip). Flashing/Update FAILED (I think the error was 'too mani links') and it went back to a blinking cursor.
@niceguy01 - just wait for CMD to process the entire thing. I was worried as well when I saw the system does not contain boot.sig etc error. Waited for it and started getting some scripts after. Wasn't able to complete the flash though but little steps getting there.

where should i flash radio.img?
boot,bootloader,recovery.system or userdata??see the picture
thanks

None of the above
Sent from my Nexus 5

Pirateghost said:
None of the above
Sent from my Nexus 5
Click to expand...
Click to collapse
thanks:good:

finally i got manage to fix my N7,thanks anyone who help me:good:
-----------thread close------------
i use google nexus toolkit v4 and install sdk drivers

[Q] Boot doesn't go beyond rotating circles. Help!!

I tried to search, but in vain.
Hardware: Nexus 4
Software : Android 4.4.4
For reasons that are not clear to me the machine restarted and is stuck in those 4 rotating circles, and doesnt go beyond it. Tried multiple things such rebooting, rebooting into recovery and booting again, tried adb to see if it can see the machine in recovery mode, but to no avail.
Can someone please help? Thanks in advance.

Did you do anything, flash anything to get the boot loop? Boot loop can usually be cleared by doing a factory reset. But you'll have to reset up your phone afterwards
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Did you do anything, flash anything to get the boot loop? Boot loop can usually be cleared by doing a factory reset. But you'll have to reset up your phone afterwards
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
This is a stock android and have no changes whatsoever except automatic update to 4.4.4. Only thing that is different is it is unlocked.
For last one week the phone kept complaining that it was unable to back up photos and videos. So I kept the wifi on over the night, and next morning I saw what i thought was it was trying to reboot but unable to do.
Is it possible to connect to machine while it is in recovery mode? My ADB can't discover the device either in recovery mode or while it is trying to boot. Is there a way to press some button and hard reset it?

Concoran said:
This is a stock android and have no changes whatsoever except automatic update to 4.4.4. Only thing that is different is it is unlocked.
For last one week the phone kept complaining that it was unable to back up photos and videos. So I kept the wifi on over the night, and next morning I saw what i thought was it was trying to reboot but unable to do.
Is it possible to connect to machine while it is in recovery mode? My ADB can't discover the device either in recovery mode or while it is trying to boot.
Click to expand...
Click to collapse
Can you get into the bootloader? If so you can flash a custom recovery. ADB won't work in the stock recovery.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Can you get into the bootloader? If so you can flash a custom recovery. ADB won't work in the stock recovery.
Click to expand...
Click to collapse
I can get into bootloader - if you mean by pressing down volume button and powering on - so you see a few options such as 'Start', 'Restart Bootloader' et al.'
If I can get into this, what option do I have? How I can I some custom recovery such as TWRP?
Also, I saw a youtube video where a gentleman shows how to completely reset from Recovery mode (hold power button and press up volume key), but that doesn't seem to work for me.

Concoran said:
I can get into bootloader - if you mean by pressing down volume button and powering on - so you see a few options such as 'Start', 'Restart Bootloader' et al.'
If I can get into this, what option do I have? How I can I some custom recovery such as TWRP?
Also, I saw a youtube video where a gentleman shows how to completely reset from Recovery mode (hold power button and press up volume key), but that doesn't seem to work for me.
Click to expand...
Click to collapse
Yes, that's the bootloader. Google 15 second adb install xda and install that. Then download the latest version of this http://techerrata.com/browse/twrp2/mako
Rename it recovery and put it in the same directory as fastboot.exe which will be installed with the 15 second adb install
Open a Windows command prompt in the same directory as fastboot and then with your phone connected to the pc and in the bootloader type the command in the command window
fastboot flash recovery recovery.img
This will instal twrp to your phone
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Yes, that's the bootloader. Google 15 second adb install xda and install that. Then download the latest version of this http://techerrata.com/browse/twrp2/mako
Rename it recovery and put it in the same directory as fastboot.exe which will be installed with the 15 second adb install
Open a Windows command prompt in the same directory as fastboot and then with your phone connected to the pc and in the bootloader type the command in the command window
fastboot flash recovery recovery.img
This will instal twrp to your phone
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
My Biggest concern right now is not TWRP. I need to somehow get the machine to boot. It is stuck in those 4 circling things, and I need to somehow get the OS to work (or re-install if needed).
I am able to get to recovery where I see options to 'apply aupdate from ADB,' 'wipe data' and 'wipe partition'. I have wiped off everything, now I need to somehow get OS to install, and I don't know how. I tried using 'adb sideload 'image-occam-ktu84l.zip', but it fails.That file was extracted from occam-ktu84l-factory-0d3fd624.tgz from Android site.
Update: Great, now TWRP is installed. What next? I don't want CM at this point. Just stock Os. How do I get on to the machine?

Concoran said:
My Biggest concern right now is not TWRP. I need to somehow get the machine to boot. It is stuck in those 4 circling things, and I need to somehow get the OS to work (or re-install if needed).
I am able to get to recovery where I see options to 'apply aupdate from ADB,' 'wipe data' and 'wipe partition'. I have wiped off everything, now I need to somehow get OS to install, and I don't know how. I tried using 'adb sideload 'image-occam-ktu84l.zip', but it fails.That file was extracted from occam-ktu84l-factory-0d3fd624.tgz from Android site.
Update: Great, now TWRP is installed. What next? I don't want CM at this point. Just stock Os. How do I get on to the machine?
Click to expand...
Click to collapse
Adb side load this http://forum.xda-developers.com/showthread.php?p=47476426
Edit, you could also flash the .zip you mentioned in your post by
fastboot update your file.zip
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Adb side load this http://forum.xda-developers.com/showthread.php?p=47476426
Edit, you could also flash the .zip you mentioned in your post by
fastboot update your file.zip
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Now that I have TWRP, how do I install CM? I would eventually like to return to stock, but at least for now, I need to get the phone going.
UpdateOk, the TWRP wasn't functioning well (swipe function wouldn't work), so got CWM recovery, and installed CM. CM too goes into infinite loop. Now I am completely stuck, I have no idea what else I can do.

Concoran said:
Now that I have TWRP, how do I install CM? I would eventually like to return to stock, but at least for now, I need to get the phone going.
UpdateOk, the TWRP wasn't functioning well (swipe function wouldn't work), so got CWM recovery, and installed CM. CM too goes into infinite loop. Now I am completely stuck, I have no idea what else I can do.
Click to expand...
Click to collapse
Flash the factory image in fastboot
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Flash the factory image in fastboot
Click to expand...
Click to collapse
I installed both TWRP and CWM alternatively, installed factory images using flash-all.bat, install CM11. But in both cases, 1. factory image : The system get stuck in boot mode where those 4 circles keep rotating around each other, 2. In CM11, the arrow keep rotating indefinitely.
I don't know what else I can do.
Any pointers? Thanks in advance.
I am beginning to suspect hardware malfunction. In which case, is there a log somehow I can see?
As an Aside: 1. Adb refuses to see the device in fastboot mode. Not sure if this is an expected behavior. Fastboot can.
2. Stock Android USB Drivers never work. I had to get the WugFresh Development drivers.
This is Windows 8 environment.

jd1639 said:
Flash the factory image in fastboot
Click to expand...
Click to collapse
As I said earlier, both factory image and CM go into infinite loop at bootup. I have no idea what else to do.
Question now is to see if something is wrong with hardware. I don't know how to check that. Is there a way to do some diagnostics

Concoran said:
As I said earlier, both factory image and CM go into infinite loop at bootup. I have no idea what else to do.
Question now is to see if something is wrong with hardware. I don't know how to check that. Is there a way to do some diagnostics
Click to expand...
Click to collapse
You probably have a failure of the emmc. What happens if you try to lock the bootloader and then reboot? Does it stay locked?
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
You probably have a failure of the emmc. What happens if you try to lock the bootloader and then reboot? Does it stay locked?
Click to expand...
Click to collapse
Yes, after locking (fastboot oem lock), bootloader the status says locked and I no longer see that unlocked icon when booting.
- At the moment I have CWM, and I see advanced options to format different folders which I have already done. But what I am not able to do is to use adb to copy the image-occam-ktu84l.zip to sdcard. Only way I have been able to install any zip is using sideload. Is that normal? I wonder if I am following right steps to begin with.
- Also, are there tools that can run and check if emmc has no bad sectors etc?
- In CWM I formatted whole log of folders, and now when CWM boots, it can't find /cache/recovery/* files. Which I take as a good sign - since old stuff is now gone. From here I don't know how to proceed. Any help - very thanful.

Concoran said:
Yes, after locking (fastboot oem lock), bootloader the status says locked and I no longer see that unlocked icon when booting.
- At the moment I have CWM, and I see advanced options to format different folders which I have already done. But what I am not able to do is to use adb to copy the image-occam-ktu84l.zip to sdcard. Only way I have been able to install any zip is using sideload. Is that normal? I wonder if I am following right steps to begin with.
- Also, are there tools that can run and check if emmc has no bad sectors etc?
- In CWM I formatted whole log of folders, and now when CWM boots, it can't find /cache/recovery/* files. Which I take as a good sign - since old stuff is now gone. From here I don't know how to proceed. Any help - very thanful.
Click to expand...
Click to collapse
If you can side load you should be able to adb push a rom. When in recovery type adb devices. Does it show that your device is connected? Do you get an error?
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
If you can side load you should be able to adb push a rom. When in recovery type adb devices. Does it show that your device is connected? Do you get an error?
Click to expand...
Click to collapse
I can sideload from adb. (adb sideload <filename>.zip while CMW is waiting for abd sideload). But can't push since adb doesn't recognize the device while in fastboot - the way fastboot can.

Concoran said:
I can sideload from adb. (adb sideload <filename>.zip while CMW is waiting for abd sideload). But can't push since adb doesn't recognize the device while in fastboot - the way fastboot can.
Click to expand...
Click to collapse
You have to be in recovery to run adb commands. The bootloader is only for fastboot commands. Try pushing while you're in recovery, not the bootloader.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
You have to be in recovery to run adb commands. The bootloader is only for fastboot commands. Try pushing while you're in recovery, not the bootloader.
Click to expand...
Click to collapse
Here 's what I see when I to sideload,
In CWM, I choose 'install from zip, which takes me to next page where i chose to select from sideload. I then start sideload from 'adb sideload occam-ktu84l-factory-0d3fd624.tgz' (sometime I use the extracted zip from that tgz),
Following is what I see on CMW,
'Restarting adb
Finding update package...
Opening update package...
E: Can't open /tmp/update.zip
(bad)
installation aborted'

Concoran said:
Here 's what I see when I to sideload,
In CWM, I choose 'install from zip, which takes me to next page where i chose to select from sideload. I then start sideload from 'adb sideload occam-ktu84l-factory-0d3fd624.tgz' (sometime I use the extracted zip from that tgz),
Following is what I see on CMW,
'Restarting adb
Finding update package...
Opening update package...
E: Can't open /tmp/update.zip
(bad)
installation aborted'
Click to expand...
Click to collapse
Ok, you can't use that file (tgz) in cwm, adb or fastboot. What you can do is extract it and then use the zip file. But, you'll have to boot into the bootloader and then use the command
fastboot update update.zip
Sent from my Nexus 5 using XDA Free mobile app

How to lock the bootloader?

Hi,
I have TWRP but I want to use the default bootloader. Is there a way to restore it back to stock without losing my apps and settings?
I downloaded (A2017UV1.1.B35 (Nougat) (Post # 2 or Click Here)) from here:
https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484
https://androidfilehost.com/?w=file...c9cf15e47b9a9c4af6f1239b585792c06c0520ebc3480
I extracted the recovery.img
then I followed this:
https://www.theandroidsoul.com/how-to-install-twrp-recovery-via-fastboot/
But after I type this:
adb reboot bootloader
I am in the booting black screen for 5 seconds, as the loading screen tells me, before it reboots. Either way when I call this command right after:
fastboot flash recovery recovery.img
I am getting "waiting for device" print and it never finishes. Before that ADB sees my device. What do I need to do so I can fix this?
Thanks in advance.

lachdanan said:
Hi,
I have TWRP but I want to use the default bootloader. Is there a way to restore it back to stock without losing my apps and settings?
I downloaded (A2017UV1.1.B35 (Nougat) (Post # 2 or Click Here)) from here:
https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484
https://androidfilehost.com/?w=file...c9cf15e47b9a9c4af6f1239b585792c06c0520ebc3480
I extracted the recovery.img
then I followed this:
https://www.theandroidsoul.com/how-to-install-twrp-recovery-via-fastboot/
But after I type this:
adb reboot bootloader
I am in the booting black screen for 5 seconds, as the loading screen tells me, before it reboots. Either way when I call this command right after:
fastboot flash recovery recovery.img
I am getting "waiting for device" print and it never finishes. Before that ADB sees my device. What do I need to do so I can fix this?
Thanks in advance.
Click to expand...
Click to collapse
First of all it would be a good start to actually get fastboot mode :laugh: You should actually follow a guide instead of trying to do this by your own. Find a guide for the U (assuming that you have an U). You'll have to install fastboot via miflash or whatever

Thanks the guides I found online all advise to use that fastboot command. That's why I couldn't figure it out. I have A2017U yes. Do you know any guide for this?
I will google more using your miflash keyword. Thanks again

The toolkit can do this for you. Make sure you are 100% stock bootstack, recovery, and system, with everything working, before you attempt to lock your bootloader. Lots of people ignore that warning and brick their phones. I'm not sure if your apps and data survive a lock.

I tried to lock mine via adb and bricked it. Luckily, the RMA people believed me that it was a failed software update and fixed it for me. I wouldn't try to do that again ^^

lachdanan said:
Thanks the guides I found online all advise to use that fastboot command. That's why I couldn't figure it out. I have A2017U yes. Do you know any guide for this?
I will google more using your miflash keyword. Thanks again
Click to expand...
Click to collapse
Were the guides that you found online for the Axon 7? Because I meant HERE AT XDA...