zuk z1 bootloader locked when twrp installed - Zuk Z1 Q&A, Help & Troubleshooting

what i messed up?
i have installed custom official cynogen14.1 rom and twrp recovery. everything was working fine.
but i messed up with bootloader. I have locked oem from fastboot mode without enabling option for oem unlocking in developer settings.
Now as my phone have custom rom and twrp installed it went into bootloop and only shows zuk logo and again restart.
What i diid till now?
i have opened backcover so that i can turn of bootloop and phone by disconecting battery.
I can enter into fastboot mode by pressing vol.+ and vol- buttons sumultaneously and connecting usb cable.
But i cannot unlock bootloader as it says unlocking bootloader not allowed. I have tried device specific commads like "fastboot -i 0x2b4c oem unlock" and "fastboot -i 0x2b4c oem unlock-go" but nothing works.
i have stock recovery image but cannot flash while bootloader is locked.
i can enter into adb sideload by following method:
by loading stock recovery by typing "fastboot boot recovery.img" (this does not work with twrp as it says signature varification failed)
and then selecting apply update >> selecting apply fron adb
this much i can do does anyone knows how to recover from such a state.
please help me or my phone will be a waste.
is there any way to install stock recovery i think phone will boot properly if i managed to install stock recovery.

Related

[Q] Data transfer failure ((Too many links) while sending 'system'

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" ?

Help! G530W not recognized by Fastboot [SOLVED]

I can't seem to get ADB or Fastboot working in Recovery or Download Mode.
In recovery if I select the option 'install update from adb sideload' then my device shows up is adb (not useful to me right now) but not in fastboot, which is what I need to execute the 'fastboot oem unlock' command (is that the right way? I've already enabled oem unlocking in settings). I can flash files via Odin, do I need to flash twrp or something?
Any help would be appreciated!
EDIT:
So it turns out that the toggle 'allow oem unlocking' unlocks the bootloader. The reason i thought it didn't was because when I flashed the cf-auto-root file I got stuck in a bootloop. Turns out I had to flash the file, then go into recovery, then reboot which solved my problems.
Samsung devices do not support fastboot mode.
The device is already OEM unlocked. You should be able to boot into Download or Odin mode and flash pretty much anything.
ODIN only

XT1700 Fastboot oem unlock fails

I seem to have lost the ability to unlock the bootloader of my XT1700. I previously had unlocked the bootloader and installed TWRP and SuperSU, which took a while to figure out, but it worked. Today I tried to install a newer version of the stock firmware using SP flash tool (from here), which seemed to work fine, except now I find I am unable to reinstalled TWRP or SuperSU because I cannot unlock the boot loader.
When the phone boots, I still see the "device unlocked" message, and I have enabled oem unlocking and USB debugging in the developer options menu, however when I go into fastboot mode, if I run the "fastboot oem unlock" command, when the phone prompts me to press up or down, I get an "unlocking failed" error, and Fastboot reports "Unlock operation is not allowed"
Any ideas on how I can unlock this device again?
So it seems like those firmware images must have locked boot loaders. I ended up installing an xt1706 firmware instead (from here) and was able to unlock the boot loader successfully.
Anyone know where to get xt1700 stock firmwares with unlocked boot loader?

Bootloader question on 906k

Hello,
I have a galaxsy s5 906k and I've been reading on how to unlock the bootloader as I'm trying to install Remix OS and it seems I've come across a lot of misinformation.... and if possible can someone tell me what exactly I need to unlock the bootloader, as I can't find a list of the appropriate tools? Do I need twrp for my specific device?? Some have said yes and some no.
My phone is already rooted.
Also post unlock bootloader question, can I use the 900k rom from remix to install on my 906k?
EDIT**
I can only boot into download mode, not fastboot mode. adb devices returns the device, but fastboot devices returns nothing. Tried adb reboot-bootloader`and it just shows waiting for any device.
These all boot into download/odin mode!!!!!!
adb reboot download
adb reboot bootloader / adb reboot-bootloader
fastboot oem unlock
fastboot flashing unlock
Only one that boots into recovery mode! Then I go to Reboot to bootloader and it comes back to recovery mode!!!!!!!!!!
adb reboot recovery

LG v20 h990 bricked

Hello. I have a lg v20 H990N. I flashed TWRP by dirty santa method and wanted to go back to stock. As per the instructions on the link https://forum.xda-developers.com/v20...-h990-t3624296, I used method 1a for going back to stock. I ran the code as mentioned in the method while using my backed up "abootbackup.img" but I accidently ran the code twice.
Code:
dd if=abootbackup.img of=/dev/block/bootdevice/by-name/aboot
sync
sleep 30
sync
After booting to bootloader. this is what I see written on the boot loader screen.
___________________________________
Welcome to fastboot mode for bootloader unlock:
*Quick Guidnance
1) Read Device Id
fastboot oem device-id
2) Write unlock key
fastboot flash unlock unlock.bin
3) Check boiotloader is unlocked
Fastboot getvar unlocked
*How to exit fastboot mide
USe "Fastboot reboot' command if fastboot is available
________________________________________
This is the meassage that pops up in fastboot. I can use fastboot but can't use "fastboot flash recovery twrp-3.0.2-1-h990.img" as it exits with error that remote: device is locked. I can't flash kdz with lg Up as Lg up says " there is no haadset connected". TWRP recovery is also not boot neither is the nougat rom that was installed. More \over my device is shown as "Kedacom USB device " in device manager in fastboot mode. Not in Com ports.
It apperas that my bootloader has locked somehow after flashing abootbackup and I can't unlock it as h990N is not supported by LG to unlock bootloader. screenshot attached.
Please help!!!
Yeah flashing the stock bootloader relocks most v20 variants, (the dirty santa bootloader can't truely unlock them, it just ignores the lock)
I'm not sure what you expected? Your link is broken, but it sounds like you reflashed stock firmware and then the stock bootloader and expected to be in a different situation than a fresh unrooted device?
You should be able to boot normally to Android or boot I to download mode and reroot from scratch.
.

Categories

Resources