im trying to use cf auto root with Android N latest build but its bootlooping on the red android logo after it runs the script and boots to google unlock screen and then goes back to red android logo...
i need help.. what to do...
Is your bootloader unlocked?
"fastboot OEM unlock" from a command prompt (without quotes) - if you've not done this before, it will wipe your userdata folder
Then try again.
Wiltron said:
Is your bootloader unlocked?
"fastboot OEM unlock" from a command prompt (without quotes) - if you've not done this before, it will wipe your userdata folder
Then try again.
Click to expand...
Click to collapse
my bootloader is unlocked
Run the command again then.. if it's unlocked already, nothing will happen.
If it's locked or in a semi-locked state, then it will (should?) unlock.
Related
It took me about two days to figure out how to unroot and relock my Moto X. Figured I'd create a total noob guide for those who are also looking to do the same. This is for the Verizon Wireless Developer Edition Moto X ONLY! I have no clue if this will work for other variants like Sprint, AT&T, T-Mobile, etc. So just play it safe and don't...
I've unrooted and relocked my VZW Dev Edition Moto X twice using this method, so as long as you follow the steps below you should be fine. Also please note that I'm not at all responsible for anything that happens to your beloved phone.
Btw, this process wipes your phone completely clean, so back your sh** up.
So here goes.
1. You need a Windows PC.
2. Download and install the Motorola Device Manager (USB Drivers) to your PC. This will allow your Moto X to be recognized by your computer.
3. Plug your Moto X into your PC and let the drivers install automatically.
4. Download and unzip the VZW Developer Edition Factory Image for the Moto X to your desktop.
5. Download both the fastboot.exe and AdbWinApi.dll files and place them in the folder you just unzipped in step step 4.
6. Now grab your Moto X, unplug it from your PC and power it off. Once powered off, press and hold both the Power and Volume Down buttons for about 10 seconds or so to access Fastboot mode.
7. Now, back on your PC, open the folder you extracted on Step 4. Hold down the Shift key on your keyboard and Right Click on an empty space within that folder. From the menu that pops up, click on Open command window here. A command prompt window should open. Plug your phone back into your PC.
8. In the command prompt type fastboot devices to make sure your X is being detected. You should see something similar T0620059GA. If you don't see it, then you may have to reinstall the USB Drivers from Step 2.
9. Once your X has been detected by your computer, and while still in Fastboot mode, type the following commands (in the order shown) into the command prompt on your PC:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase cache
fastboot oem lock
fastboot reboot
...
That's it! You should now be locked and unrooted; back to the out of the box factory state. Don't forget to hit thanks and share!
Did re-locking ur bootloader get rid of the Bootloader Unlocked Warning Message?
tonyf7 said:
7. Now, back on your PC, open the folder you extracted on Step 4. Hold down the Shift key on your keyboard and Left Click on an empty space within that folder. From the menu that pops up, click on Open command window here. A command prompt window should open. Plug your phone back into your PC.
Click to expand...
Click to collapse
Right click sir.
mschumacher69 said:
Did re-locking ur bootloader get rid of the Bootloader Unlocked Warning Message?
Click to expand...
Click to collapse
Yes.
tonyf7 said:
Yes.
Click to expand...
Click to collapse
Just to make sure we're on the same page here, after re-locking ur bootloader, when u boot the phone, u get the Moto logo instead of the message that says Warning Bootloader Unlocked?
Because many other users said that u would still get this message even if u re-lock ur bootloader.
When I relocked the bootloader and rebooted the phone I didn't get the warning message. Went straight to the Moto logo. But then I immediately rooted and unlocked again. Only reason I unrooted and relocked in the first place was because I flashed a zip file that corrupted and broke Google Voice Search on my phone.
The second time I did this process I stopped right before locking the bootloader since I was going to root again anyways.
So maybe those other people are right. I've only rebooted my phone once since relocking the bootloader.
Sent from my XT1060 using xda app-developers app
If you want to get rid of the warning on startup, just flash the logo.bin. You can do this and remain unlocked. The instructions provided should have your phone looking and acting the same as it did out of the box. However, fastboot may note that it's been unlocked, to the OP, do you recall what status fastboot was reporting?
you need to reflash to stock in order to lock your bootloader? If not, I would appreciate if you separate the steps to just lock your boot loader.
I have my boot loader unlocked and the only reason I am considering to lock it again is so that if the phone is stolen, someone can't reimage it easily. I'm not sure that gives me any sort of protection though. But its just a thought.
In other words, I see unlocking and locking as a switch that stops you from flashing firmware. The OP makes it sound like the switch is tied to the firmware, ie only stock can have bootloader locked. I am not sure which is right.
esidnD Selim
I did it and keep receiving the warning unlock bootloader screen.
lopescesar304 said:
I did it and keep receiving the warning unlock bootloader screen.
Click to expand...
Click to collapse
Did u re-lock on your phone's ROM or after flashing another carrier's ROM?
mschumacher69 said:
Did u re-lock on your phone's ROM or after flashing another carrier's ROM?
Click to expand...
Click to collapse
My phone is Retail, I used the retail ROM to flash.
My device won't lock. I've run your commands listed, as well as the fastboot oem lock on it's own, and I can't seem to lock the device. Any help?
flavinator said:
My device won't lock. I've run your commands listed, as well as the fastboot oem lock on it's own, and I can't seem to lock the device. Any help?
Click to expand...
Click to collapse
Welcome to the "Relock" party..
The OP does not mention (that I can see) what OS version..are you on KK 4.4 and is there a "Factory Image" for KK 4.4 available for your device.?
sent by my 4.3_14.14.14
XT1028 (aka) Moto-G
NWKENT said:
Welcome to the "Relock" party..
The OP does not mention (that I can see) what OS version..are you on KK 4.4 and is there a "Factory Image" for KK 4.4 available for your device.?
sent by my 4.3_14.14.14
XT1028 (aka) Moto-G
Click to expand...
Click to collapse
Yes, there is, flashed it, ran commands, and the relock command, multiple times and get:
(bootloader) FAIL: Please run fastboot oem lock begin first!
OKAY [ 0.120s]
finished. total time: 0.122s
Not sure what I am doing wrong.
flavinator said:
Yes, there is, flashed it, ran commands, and the relock command, multiple times and get:
(bootloader) FAIL: Please run fastboot oem lock begin first!
OKAY [ 0.120s]
finished. total time: 0.122s
Not sure what I am doing wrong.
Click to expand...
Click to collapse
I'd think you ran this as the first flash >> fastboot oem lock begin first!
Then all the OS files and then this for the last command >> fastboot oem lock > as the last command.?
sent by my 4.3_14.14.14
XT1028 (aka) Moto-G
http://forum.xda-developers.com/showthread.php?t=2575586
NWKENT said:
I'd think you ran this as the first flash >> fastboot oem lock begin first!
Then all the OS files and then this for the last command >> fastboot oem lock > as the last command.?
sent by my 4.3_14.14.14
XT1028 (aka) Moto-G
Click to expand...
Click to collapse
I have no clue. At first I just flashed back using RSD Lite. Then I ran the lock command and got that error. Afterwards, I searched online, trying a bunch of different fastboots. That's when I stumbled on this list of commands, figured I'd run it from scratch, see if it makes a difference. Once it got to the relock command though, I got the same issue. And now I'm just frustrated...
---------- Post added at 06:41 PM ---------- Previous post was at 06:36 PM ----------
shane1 said:
http://forum.xda-developers.com/showthread.php?t=2575586
Click to expand...
Click to collapse
I think this might work, thanks shane1
@NWKENT have u managed to re-lock your bootloader yet?
mschumacher69 said:
@NWKENT have u managed to re-lock your bootloader yet?
Click to expand...
Click to collapse
Yes Sir..with Kit Kat 4.4..I have successfully"Unlocked", "Relocked" and "Unlocked" again..my XT1080MDEV (Droid Maxx)..No one could tell me exactly how to do it..Motorola Tech Line was absolutely NO HELP either..SO..after hours upon hours..I did figure it out..Now I'm working on "Relock" on JB 4.2.2
Sounds easy..and many have probably "Unlocked and "Relocked" on JB 4.2.2..BUT..The difficult part is once the XT1080 has been on KK 4.4..is when alot more firey hoops must be jumped thru..
ANYONE can chime in with help on this..NOT ADVICE..but proven procedures..
sent by my 4.3_14.14.14
XT1028 (aka) Moto-G
Yes, thanks guys.
PROBLEM SOLVED! I used another pc, my usb ports were the problem! I recently got my Nexus 7 (2012), wi-fi only , I unlocked it's bootloader, installer TWRP recovery, and rooted it. For all these operations i used the N7 toolkit , because back then, I was a noob. The rooted tablet (4.2.2) worked Perfectly! But, after about 3 months, it's "volume down" button stopped working. I rebooted it, but it went in bootloader, instead of normal system. So I just select "Start" and it was in Safe Mode! OK, my "volume down" didn't work in Safe Mode (and bootloader mode) neither! And every time I reboot it, it goes to bootloader! I thought that it was a software problem confused , so I began flashing a new ROM. I didn't want to use the toolkit because everyone says that it's bad . I downloaded AndroidSDK, I re-downloaded the ADB and Fastboot drivers, and I downloaded the newer version of the bootloader (4.23, .img) . Tablet was already in bootloader and I connected it to the PC. In platform-tools folder I ran the "fastboot devices" command, and It was able to see it . So I copied the bootloader img to the same folder, and I ran "fastboot flash bootloader bootloader-grouper-4.23.img" . Then I rebooted it into bootloader again. IT WORKED! But, it didn't solve the "volume down" problem. My rooted 4.2.2 and TWRP were still on the system. Everytime I power off the tablet, and then hold the "Power" button, it goes into bootloader. It was that button issue causing that. Then I decided to take it to the service (same place where I bought iw the unloct) , but I couldn't because if they saked bootloader, non-stock recovery and the root, the wouldn't accept the warranty . I decided to download the latest 4.3 stock android, and stock recovery, flash them, and lock the bootloader. I downloaded 4.3 stock from google's official site, (nakasi-jwr66y) and I used the flash-all.bat command that came with it.
.bat command looks like this:
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
ping -n 10 127.0.0.1 >nul
fastboot -w update image-nakasi-jwr66y.zip
echo Press any key to exit...
pause >nul
exit
I ran it. It successfully did the oem unlock (it was already unlocked) , all the erase commands, and flash bootloader command. But it was stuck on
"fastboot -w update image-nakasi-jwr66y.zip" . It stays steady for about 30secs , and than it says
"sending 'system' (x-kb)"
After some time it just says Data transfer failure(too manly links) ...
I tried the same process billion more times, but same error :/
I tried
-Re-downloading and installing the drivers
-Changing the usb ports, and microUSB cables,
-Restarting the pc (of course)
-Re-downloading the nakasi-jwr66y
-Downloading the twrp recovery (it successfully flashes it)
-Re-downloading the whole SDK
But it DOESN'T WORK? What should I do? Is the volume-down issue hardware or software ?
Sorry for my bad English :////////
P.S. What is the difference between "fastboot flashall" and "fastboot update" ?
Hi friends,zenfone 3 bootloder opened the lock.Now I want to close .Relock bootloader.
Ive tried asking this before for my Ze520kl, someone said it isn't possible to relock the bootloader
I would like to know if someone has an update about that...
When I tried to root my phone (ZE552KL Androïd 7.0) I installed an app to unlock the bootloader of my phone (ZE552KL_SIGNED_Android_M_UnlockTool_2016_0715). I used it and ever since, when I turn on my device, I get a warning screen saying "Your device software cannot be checked for corruption. Please lock the bootloader." It sends me to this link for information. The notification disappear after 10 seconds and androïd starts.
I was quite stupid to do that because I do not have to knowledge to properly root my device. So I give up, but I would like to get back my device without that security warning.
I have already flashed it from the recovery menu, with an sd card, wiping data and cache. But it didn't work.
Any advice?
my69 said:
Hi friends,zenfone 3 bootloder opened the lock.Now I want to close .Relock bootloader.
Click to expand...
Click to collapse
I found this on the bootloader source:
Code:
fastboot oem unlock
fastboot oem unlock-go
fastboot oem lock
fastboot flashing unlock
fastboot flashing lock
fastboot flashing lock_critical
fastboot flashing unlock_critical
fastboot flashing get_unlock_ability
but they're all untested, trying them would make you take the risk of
killing your phone
OR
locking the bootloader
keep in mind that Asus also keeps track of system mounts as read write changes, so if you're trying to fool them, locking the bootloader won't be enough
Commands do not work.
gkillershots said:
I found this on the bootloader source:
Code:
fastboot oem unlock
fastboot oem unlock-go
fastboot oem lock
fastboot flashing unlock
fastboot flashing lock
fastboot flashing lock_critical
fastboot flashing unlock_critical
fastboot flashing get_unlock_ability
but they're all untested, trying them would make you take the risk of
killing your phone
OR
locking the bootloader
keep in mind that Asus also keeps track of system mounts as read write changes, so if you're trying to fool them, locking the bootloader won't be enough
Click to expand...
Click to collapse
Commands do not work.
myheartloves said:
Commands do not work.
Click to expand...
Click to collapse
well, I think Asus disabled thoose ones
sorry
I have a Axon 7 with the bootloader unlocked but it is unrooted and doesn't have TWRP on it. When I go to settings to try to enable OEM unlocking it is grayed out saying "Bootloader is already unlocked" and I can't enable it. I've tried to boot into fastboot and it just takes me to the bootloader screen. Is their any way to enable OEM unlock using adb or something else?
Donte Dub said:
I have a Axon 7 with the bootloader unlocked but it is unrooted and doesn't have TWRP on it. When I go to settings to try to enable OEM unlocking it is grayed out saying "Bootloader is already unlocked" and I can't enable it. I've tried to boot into fastboot and it just takes me to the bootloader screen. Is their any way to enable OEM unlock using adb or something else?
Click to expand...
Click to collapse
Use axon7tool, don't try to use fastboot
Donte Dub said:
I have a Axon 7 with the bootloader unlocked but it is unrooted and doesn't have TWRP on it. When I go to settings to try to enable OEM unlocking it is grayed out saying "Bootloader is already unlocked" and I can't enable it. I've tried to boot into fastboot and it just takes me to the bootloader screen. Is their any way to enable OEM unlock using adb or something else?
Click to expand...
Click to collapse
The bootloader screen is where you issue fastboot commands. So when you reboot to bootloader just type "Fastboot oem unlock" (minus quotes) should bring up a menu that says something about unlocking wipes device etc. use volume rocker to select yes and power button to accept. When you use adb reboot bootloader and you're booted into the bootloader it will tell you if your bootloader is already unlocked.
There isn't a fastboot mode. Fastboot is just a protocol for issuing commands in order to flash to different partitions outside of recovery.
Choose an username... said:
Use axon7tool, don't try to use fastboot
Click to expand...
Click to collapse
When you try to root or flash TWRP it the toolkit reboots to fastboot.
jgates86 said:
The bootloader screen is where you issue fastboot commands. So when you reboot to bootloader just type "Fastboot oem unlock" (minus quotes) should bring up a menu that says something about unlocking wipes device etc. use volume rocker to select yes and power button to accept. When you use adb reboot bootloader and you're booted into the bootloader it will tell you if your bootloader is already unlocked.
There isn't a fastboot mode. Fastboot is just a protocol for issuing commands in order to flash to different partitions outside of recovery.
Click to expand...
Click to collapse
I've tried that and it says <Waiting for any device>
Donte Dub said:
I've tried that and it says <Waiting for any device>
Click to expand...
Click to collapse
I said axon7tool, not axon7toolkit. Axon7tool uses EDL mode which is finicky as hell but it sure works if you set everything right. Use Controllerboy's guide to root the A2017G but only do the TWRP part.
---------- Post added at 08:56 PM ---------- Previous post was at 08:55 PM ----------
jgates86 said:
The bootloader screen is where you issue fastboot commands. So when you reboot to bootloader just type "Fastboot oem unlock" (minus quotes) should bring up a menu that says something about unlocking wipes device etc. use volume rocker to select yes and power button to accept. When you use adb reboot bootloader and you're booted into the bootloader it will tell you if your bootloader is already unlocked.
There isn't a fastboot mode. Fastboot is just a protocol for issuing commands in order to flash to different partitions outside of recovery.
Click to expand...
Click to collapse
Short and simple, there is no bootloader screen. ZTE killed it on the G and U versions. You can use MiFlash to get it back though
Choose an username... said:
I said axon7tool, not axon7toolkit. Axon7tool uses EDL mode which is finicky as hell but it sure works if you set everything right. Use Controllerboy's guide to root the A2017G but only do the TWRP part.
Click to expand...
Click to collapse
I've tried axon7tool and I followed all the steps but I still get no luck with trying to flash TWRP. I use the command axon7tool -w recovery recovery.bin and I get...
Connecting to device...
Sending programmer...
Connecting to programmer...
log: Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke getnumdisksectors
log: Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke getnumdisksectors
Usage:
axon7tool -r <boot|recovery|gpt> ...
axon7tool -w <boot|recovery>
When I go back to the bootloader and try to reboot into recovery it boots into stock recovery.
Donte Dub said:
I've tried axon7tool and I followed all the steps but I still get no luck with trying to flash TWRP. I use the command axon7tool -w recovery recovery.bin and I get...
Connecting to device...
Sending programmer...
Connecting to programmer...
log: Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke getnumdisksectors
log: Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke getnumdisksectors
Usage:
axon7tool -r <boot|recovery|gpt> ...
axon7tool -w <boot|recovery>
When I go back to the bootloader and try to reboot into recovery it boots into stock recovery.
Click to expand...
Click to collapse
Be sure that you have show file extensions enabled, otherwise you're naming the file "recovery.bin.img" without knowing
Choose an username... said:
Be sure that you have show file extensions enabled, otherwise you're naming the file "recovery.bin.img" without knowing
Click to expand...
Click to collapse
Ahh, it worked! Thank you so much for helping me get TWRP back.
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