Zuk Z1 not boots after update Cyanogen 13 nightly to snap
I downloaded Cyanogen 13 snap version moved to cm update folder. And from developer menu i activated flash recovery during update. but usb debugging was off. From update menu i clicked snap and install. Now phone not boots. Tried Volume - & Power, Volume + & Power none of them not works. Phone screen blinks every 3 secound.
C:\WINDOWS\system32>adb devices
List of devices attached
24cc9ceb unauthorized
C:\WINDOWS\system32>adb reboot bootloader
error: device unauthorized.
This adbd's $ADB_VENDOR_KEYS is not set; try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
What can i do ?
you cant't upgrade from nightly to snap it was write in the release note you have to wipe and after flash the snap
---------- Post added at 04:38 PM ---------- Previous post was at 04:31 PM ----------
you can try to delete adbkey file in C:Users/$Name/.android if adbkey.pub is missing.
and restart they should appear
tomdan95 said:
you cant't upgrade from nightly to snap it was write in the release note you have to wipe and after flash the snap
---------- Post added at 04:38 PM ---------- Previous post was at 04:31 PM ----------
you can try to delete adbkey file in C:Users/$Name/.android if adbkey.pub is missing.
and restart they should appear
Click to expand...
Click to collapse
Phone not boots... deleting adbkey will not help
yes, it dosn't boot because there nothings to boot. upgreading from nightly to snap you have corupt system and recovery partition, you have to turn off your zuck and turn it on putting it in fastboot mode; wipe recovery partition and flash twrp, after that start the recovery twrp and from twrp wipe system and data partition and flash the snap zip in the system partition and reboot
---------- Post added at 03:11 PM ---------- Previous post was at 03:07 PM ----------
you can try to press volume + & volume - for force the fastboot mode
---------- Post added at 03:18 PM ---------- Previous post was at 03:11 PM ----------
if it dosen't work try to turned it off and keep the data cable to the computer disconnect, press: [volume down key] [Power Key] waiting to enter the fastboot mode.
---------- Post added at 03:41 PM ---------- Previous post was at 03:18 PM ----------
if all this things dosen't work last chance is install ZUI on your phone and when you have a working zui install COS or CM
for do that you have to:
0. Download the ZUI Full ROM file from here and extract to your computer. Here is the link https://mega.nz/#!fYYh0QDA!nYf0vvXpz...__vaHO_Weyg-YU
1. You need to install Qualcomm driver and ZUK Z1 driver to you PC, you can download it from this link https://mega.nz/#F!LcgDmRyC!4unf8UQqOBoZayAuv-D3Tg
2. The Qualcomm driver file shouldn't be signed so most of the windows operating system will not allow you to install, to install the Qualcomm driver you need to enable the unsigned driver installation.
If you are using windows 10 or windows 8. or 8.1 you can enable in this way. (go to the power option from the start menu hold the shift key from the keyboard and select restart option) for more information you can see this link http://www.howtogeek.com/167723/how-...igned-drivers/
If you are using windows 7 you can disable the driver signature verification from the boot menu. (when you see your computer motherboard name or pc logo just type F8 so there you can choose the option disable driver verification)
3. If you install the driver files successfully then you need to download and install the QFIL tool you can download the file from this link https://mega.nz/#!qIx0ybKC!YfeWZMHTF...8rEqDr5rEOYUc4
4.start QFIL from the QPST folder
5.Click browse on the programmer path row and select prog_emmc_firehose_8974.mbn from the directory where you unzipped the QPST ZUI ROM
and then click browse on the search path row and select the xml file + the other patch file which comes after it.
6. When thats done, make sure phone is off and then hold vol+ while you are inserting usb cable into phone and QFIL should then detect phone,
you may need to select port in the QFIL program and be quick with it, took me a few tries before I got it right so just take out the cable
and turn off and try again if you fail to make them connect.
Not only you need to select comport, you also need to press the download button aswell as soon as possible or else phone will continue booting as normal.
7.If everything went well then you should have ZUI loaded onto your phone and you are met with Chinese language as default.
On the first screen you are met with, just press the button in the bottom (on screen), then press cogwheel (which is the settings),
scroll down to yet another cogwheel in here which should be below a lock icon, then press second option in here and then the top option
to change language to english incase you cant make out the chinese and you should be good to go
My phone is unlocked and I had installed TWRP. I restored from previous backup because I was not satisfied with latest global developer ROM. after restoring I am not able to reboot into recovery. when I boot into recovery, my phone starts normally without going into recovery. i tried flashing twrp again and it works only once. phone boots normally without going into recovery. i have to flash twrp everytime i need to use recovery. any solutions?
Do you confirm the thing TWRP asks you on first boot (something about allowing system modifications or what)? Otherwise system may remove it on boot. Do you use command 'fastboot boot 'recoveryname'' after flashing (I don't know why is it necessary, but it's in every guide for R3S)?
Send from my Redmi 3S
Make sure 'OEM unlocking' is checked in developers mode.
Pwr + vol+ + vol- until it vibrates, then release pwr, but keep both vol-keys pressed.
---------- Post added at 12:37 PM ---------- Previous post was at 12:33 PM ----------
Another option is adb: Use "adb reboot recovery". If you don't know how, ask me!
Find the solution here
https://forum.xda-developers.com/xiaomi-redmi-3s/help/boot-twrp-t3606570
run miflash unlocker and unlock bootloader i know this problem and i fixed it
I try to flash this version "twrp-3.1.0-0-vtr.img" on my "P10 plus" (Model VKY-L09), through the 3 steps :
1. Enter fastboot mode on unlocked device
2. flash recovery using the following command: fastboot flash recovery twrp-3.1.0-0-vtr.img
3. reboot to recovery!
But when i try to boot mainy times into recovery by holding "vol+ & power button" it show unsafe screen each time i do it and it pass to Huawei eRecovery!!
I choose another method through prompt commands via this commnad "fastboot boot twrp-3.1.0-0-vtr.img", then an error message appear "command remote not allowed".
Tell me Guys if there another efficient method to root P10 plus.
thank you
try HWOTA is best flash tool https://drive.google.com/open?id=0B3zr0V7YRX9pMlJkVXpNQzZ0Vmc
when you flash TWRP installed then unplug cable close flash tool dont get next step
---------- Post added at 12:55 AM ---------- Previous post was at 12:54 AM ----------
try HWOTA is the best flash tool https://drive.google.com/open?id=0B3zr0V7YRX9pMlJkVXpNQzZ0Vmc
At the moment I'm just starting to write this guide. My English is bad , so please help me: write down the mistakes I made and how to fix them. :highfive:
Software
ADB/Fastboot
Drivers for ADB/Fastboot
Flash.bat
Needed firmware (now i recomend install TOS373J)
Remember! With firmware you will lose all your data!
Installing
1. Unpack adb.zip and flash.zip to C:\Android
2. Unpack your shoosen firmware to C:\Android
3. Open developer options and turn on "OEM unlocking"
4. Power off smartphone,press "+" and "power"
5. Connect smartphone to PC and install drivers
6. Open cmd and write "cd C:\Android"
7. Next "fastboot oem unlock" and accept on display of smartphone
8. After reboot power off smartphone and press "+" and "power"
9. Write "fastboot flashing unlock_critical" and accept on display of smartphone
10. Open flash.bat in C:\Android and press "enter"
11. Wait when flashing finish and disconnect smartphone
12. After flash finishing write "fastboot flashing lock_critical" and wait reboot
13. Next boot to fastboot and write "fastboot oem lock" and wait reboot
I'm trying to use this on my swift 2 (Oreo) I get a lot of errors when I run flash.bat.
---------- Post added at 08:54 PM ---------- Previous post was at 08:47 PM ----------
Are there commands to flash the image via cmd?
Kenif1983 said:
I'm trying to use this on my swift 2 (Oreo) I get a lot of errors when I run flash.bat.
---------- Post added at 08:54 PM ---------- Previous post was at 08:47 PM ----------
Are there commands to flash the image via cmd?
Click to expand...
Click to collapse
Need flash via cmd.exe.
I recently acquired an lg v35 ThinQ that seems to be stuck on the fastboot loader, it only says reboot and shutdown and reboots to the fastboot recovery but wont boot up. Help!
I would recommend backing up and erasing laf_a and laf_b. Then restoring the original boot_a, boot_b, abl_a, and abl_b and starting over. If you need any of these files for the ULM version, I have them.
Error-404-Go-Home said:
I would recommend backing up and erasing laf_a and laf_b. Then restoring the original boot_a, boot_b, abl_a, and abl_b and starting over. If you need any of these files for the ULM version, I have them.
Click to expand...
Click to collapse
If you have them they would be of great help since i did not do this in the first place, just trying to fix it
I extracted these from the V350ULM10i_00_NAO_US_OP_0221.kdz using these scripts: https://github.com/ehem/kdztools
These files are for Oreo V350ULM only, they will not work with the V350AWM image (I have tried)
This method has worked for me in the past. Just flash these to their respective partitions with QFIL and it should work again (without root, of course... that requires you to modify boot_a and boot_b). If you need any more images (system_a, system_b...) from this kdz or others feel free to ask.
https://drive.google.com/drive/folders/11kWqa7k1MBSCDwP_ThN9VOT8CbsDVra0?usp=sharing
Error-404-Go-Home said:
I extracted these from the V350ULM10i_00_NAO_US_OP_0221.kdz using these scripts: https://github.com/ehem/kdztools
These files are for Oreo V350ULM only, they will not work with the V350AWM image (I have tried)
This method has worked for me in the past. Just flash these to their respective partitions with QFIL and it should work again (without root, of course... that requires you to modify boot_a and boot_b). If you need any more images (system_a, system_b...) from this kdz or others feel free to ask.
https://drive.google.com/drive/folders/11kWqa7k1MBSCDwP_ThN9VOT8CbsDVra0?usp=sharing
Click to expand...
Click to collapse
Qfil does not recognize any usb device
TheLaptopBros12 said:
Qfil does not recognize any usb device
Click to expand...
Click to collapse
the lg v35 only shows the fastboot screen
You should still be able to put it in 9008 mode by holding power + volume down + rapidly pressing volume up while plugged into a pc
---------- Post added at 06:46 PM ---------- Previous post was at 06:45 PM ----------
You can open up QFIL and try over and over again until it shows up as QUALCOM USB... instead of "no port"
Error-404-Go-Home said:
You should still be able to put it in 9008 mode by holding power + volume down + rapidly pressing volume up while plugged into a pc
---------- Post added at 06:46 PM ---------- Previous post was at 06:45 PM ----------
You can open up QFIL and try over and over again until it shows up as QUALCOM USB... instead of "no port"
Click to expand...
Click to collapse
I cant seem to do it.
Can't get it into 9008 mode or open QFIL?
Error-404-Go-Home said:
Can't get it into 9008 mode or open QFIL?
Click to expand...
Click to collapse
QFIL works but 9008 does not. it only gets to the fastboot menu.
You can also install ADB and use "fastboot flash abl_a path/to/abl_a.image" to flash it in fastboot mode. That only works if your bootloader is unlocked though.
Error-404-Go-Home said:
You can also install ADB and use "fastboot flash abl_a path/to/abl_a.image" to flash it in fastboot mode. That only works if your bootloader is unlocked though.
Click to expand...
Click to collapse
i dont think it is. i also tried download mode, does not work.
If you have not executed fastboot oem unlock in fastboot mode I would recommend trying it and flashing the files previously mentioned. If oem-unlock does not work, I would recommend to continue trying to get it into 9008 mode. I have previously been stuck in fastboot mode as well and I just held power and volume down, where it instantly turned off, (because fastboot mode had power off selected) then, as I kept holding the power and the volume down buttons it rebooted and I started rapidly spamming the volume up button (while still holding power and volume down). That got it into 9008 mode, I would recommend similar steps, or just try holding power and volume down while rapidly spamming volume up until it works.
---------- Post added at 08:39 PM ---------- Previous post was at 08:33 PM ----------
You can also try "fastboot flashing unlock" instead of "fastboot oem unlock"
Im In, how do i set the files in QFIL? Never done before
into 9008 mode and qfil Works and detects
I recommend reading over the
"Step 2: Partition Extraction, Modification and Bootloader Unlock"
section of this great guide
https://forum.xda-developers.com/lg-v35/development/bootloader-unlock-root-instruction-t4052145
but the gist is
Set the "emmc" in the bottom right to "ufs"
then select "Flat build" and select the "firehose" file as a programmer (that can be downloaded from the guide)
and open up partition manager under tools in the upper left of QFIL
once you have the partition manager open, you can select a partition (ex. abl_a), click manage partiton, then click load image. Then load the respective image file.
Do that for laf_a, laf_b, abl_a, abl_b, boot_a, and boot_b
Then exit out of the partiton manager, reboot the device, and it should work
---------- Post added at 08:58 PM ---------- Previous post was at 08:54 PM ----------
Note: I have noticed that if you are in 9008 mode for too long, then it will error when you try to open the partiton manager saying Sahara mode FAILED or something like that. This just means that you have to hold volume down and power until it reboots and get it back into 9008 mode like before, then try to open the partition manager quicker.
Error-404-Go-Home said:
I recommend reading over the
"Step 2: Partition Extraction, Modification and Bootloader Unlock"
section of this great guide
https://forum.xda-developers.com/lg-v35/development/bootloader-unlock-root-instruction-t4052145
but the gist is
Set the "emmc" in the bottom right to "ufs"
then select "Flat build" and select the "firehose" file as a programmer (that can be downloaded from the guide)
and open up partition manager under tools in the upper left of QFIL
once you have the partition manager open, you can select a partition (ex. abl_a), click manage partiton, then click load image. Then load the respective image file.
Do that for laf_a, laf_b, abl_a, abl_b, boot_a, and boot_b
Then exit out of the partiton manager, reboot the device, and it should work
---------- Post added at 08:58 PM ---------- Previous post was at 08:54 PM ----------
Note: I have noticed that if you are in 9008 mode for too long, then it will error when you try to open the partiton manager saying Sahara mode FAILED or something like that. This just means that you have to hold volume down and power until it reboots and get it back into 9008 mode like before, then try to open the partition manager quicker.
Click to expand...
Click to collapse
I can't reboot, stuck in 9008 mode
Hold power and volume down to reboot
Error-404-Go-Home said:
Hold power and volume down to reboot
Click to expand...
Click to collapse
I got it.
problem though, now to says it is not secure and onlly boots to fastboot but before that it shows the link g.co/ABH
TheLaptopBros12 said:
I got it.
problem though, now to says it is not secure and onlly boots to fastboot but before that it shows the link g.co/ABH
Click to expand...
Click to collapse
and now back at square 1, now again
like this guy https://forum.xda-developers.com/lg-v35/how-to/v35-bricked-sad-t3960057
you likely did not have the right version of android for the files I gave you. There isn't much of a way to tell I guess.
---------- Post added at 10:45 PM ---------- Previous post was at 10:41 PM ----------
Can you get into download mode? Try turning the phone off via fastboot mode (use volume keys to select the "Power Off" option) then hold volume down while plugging it into a computer. If that doesnt work try again holding volume up. If this gets you into download mode, then you might be able to flash the whole kdz with LGUP.