Related
Gonna try and cover as much as possible but dont be afraid to comment or correct me as I might forget to mention something
ZUK Z1 Specs:
5.5 inch IPS Screen
Snapdragon 801 @ 2.5GHz
3GB RAM
64GB Storage
Dual sim - 2G/3G/4G (doesnt have LTE band 20 unfortunately)
13MP camera with OIS and 8MP front
USB-C charging/data connector
Fingerprint reader
Wifi A/B/G/N/AC
GPS Glonass
Bluetooth 4.1
4100mAh battery
Activate developer settings and ADB + OEM unlock (needed for bootloader unlock among other things)
1. Open settings and scroll to bottom and press "About phone"
2. Scroll to bottom again and press 5 times on "Version" (the one above "SElinux-status") and it should say "developer settings now activated"
3. Press back button once and you should now have a new option "Developer Settings" above "About Phone"
4. Press "Developer Settings" and scroll down to USB debugging and activate it.
5. You can also find the OEM-unlock which unlocks bootloader. If nothing happens when you try to unlock the bootloader then you can use adb command to unlock instead.
Download "Android debug bridge", can recommend minimal ADB by shimp208
http://forum.xda-developers.com/showthread.php?t=2317790 and install it.
You also need adb driver for the phone
https://mega.nz/#!l8pVHIpT!UkcW3Jg4B7YilDjZatvLqGBi_R4vVUYVdkrsUL_Ve9k
or from the chinese site
http://bbs.zuk.cn/z1/t16224/
When driver and adb is installed then type "adb devices" to check if phone is detected. If its detected then you can type "adb reboot bootloader" and after that you might wanna check device manager that your phone driver is installed and working then type "fastboot -i 0x2b4c oem device-info" to see the bootloader lock status and type "fastboot -i 0x2b4c oem unlock" to unlock it, doublecheck with "fastboot -i 0x2b4c oem device-info" again to see if its actually says unlocked before you reboot. Either type "fastboot -i 0x2b4c reboot" or hold power button til it restarts.
Ps. If you are running windows 10 and have issues with adb not detecting any devices, then download updated binary (credits goes to mrcoldbird) and replace the three files in your adb installation https://www.androidfilehost.com/?w=...164e5e9c078239797e768e69027c4effaf26930b8050b
After you´ve replaced the files, type "adb kill-server" and then try "adb devices" again and it should hopefully work. Dont forget to authorize your computer on the phone when the dialog pops up or else you wont be able to perform any commands.
How to enter recovery mode, flash mode
To enter recovery mode you need to make sure phone is turned off.
Then you press and hold vol - and + (both yes) and push the power button and release as soon as the screen is lit (still hold vol+ and vol- until you see the recovery screen).
To enter flash mode you need to make sure phone is turned off.
Then you press and hold vol+ and insert the usb data cable and your computer should have found new hardware. The iffy part here is that the phone is only in flashmode for like 5sec or so, so you need to be quick. Flash mode is currently used for when you wanna unbrick phone or factory reset to the chinese android version called ZUI
How to enter diagnostic mode
There are 2 ways of doing this, the first way is making sure no cable is inserted into phone and turning the phone off. Then hold vol+ and insert usb cable and it will be in diag mode for a brief moment (which can be quite annoying)
The second way (which requires root) makes it easier to fiddle around in diag mode. Activate ADB in developer settings and plug in your phone and authorize it, then type
Code:
adb shell
su
setprop sys.usb.config rndis,diag,adb
and voila you got diag mode activated
Flash TWRP (recovery) onto your phone
Download a twrp file for this phone (credits to JoaoPaulo)
https://www.androidfilehost.com/?fid=24269982087019837
1. Make sure you have adb on pc, driver installed, phone developer settings activated and bootloader is unlocked. Just use the above guide where I explain how to "Activate developer settings and ADB + OEM unlock"
2. Plug in cable if it isnt already and type "adb devices" to check if phone is detected, if not then try "adb kill-server" and try "adb devices" again. If detected then type "adb reboot bootloader".
3. Again make sure phone still has connection with pc by typing "fastboot -i 0x2b4c oem device-info" (since "adb devices" mostly dont work in bootloader mode we use oem device-info command instead to check communication)
4. You can then type "fastboot -i 0x2b4c flash recovery TWRP-2.8.7.0-ham-fixSystem-fixADB.img" to flash the recovery onto phone.
5. If all good and no error messages then reboot phone by typing "fastboot -i 0x2b4c reboot" or hold power button til it restarts.
6. Check that recovery is there and works by shutting down phone, then press and hold vol+ and vol- and press power button til screen goes on then you can release it (still keep hold vol+ and vol- til recovery screen is up)
Flash ZUI, Unbrick phone or fix wierd issues such as problem with activating Wifi or bluetooth
First you need to download the QPST flash program
https://mega.nz/#!4tom3DqL!4a-rRcLef1yS6HJSrBfne_-r9atg6yF3kI_HW8lDaPY
And then you also need the ZUI rom file
https://mega.nz/#!chQkEAwR!IHeYRxWx38QdML6VxjPdVz08BgbZD-Z-xVuSG150qPU
And if you havent already fixed the driver then that aswell
https://mega.nz/#!l8pVHIpT!UkcW3Jg4B...UYVdkrsUL_Ve9k
After you installed QPST, you will get a bunch of programs associated to it, start QFIL from the QPST folder
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.
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.
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
Download and install Gapps
Open http://opengapps.org/
and for first column select "ARM"
Second column, if you are running CM12 or the ZUI 1.2.x for example it is 5.1 you want
If you are running CM13 or ZUI 1.5.x it is 6.0 you want.
Then last column is just how many of the google apps you want to have installed, you can press the link "Version Information" in red text at the bottom left to see the what each package contains.
I usually go with nano since you get the necessary apps to sync your account and then ill just download the rest I want/need from play store. Its also a smaller download so goes quicker to flash aswell
Activate Root on Cyanogenmod
First you need to activate developer settings if you havent already (tap version 5 times in "about phone"), then enter developer settings menu and there you´ll have an option called "Root access" which you can set to either "only apps" and "only ADB" or both. "Only apps" is preferred and thats it, you can now run root priveliged apps (after you have confirmed each apps authorisation).
Convert from ZUI to cyanogenOS/mod
Check the guide from Paul on Modaco for this
http://www.modaco.com/forums/topic/375804-convert-z1-from-zukui-to-cyanogen-os/
Troubleshooting
If you are having usb connectivety issues, please try using another PC. Can also be a bit iffy getting connection going with windows 10 so try windows 7 if possible. You could also run windows 7 in a virtual machine and get it working that way as an example.
Also when troubleshooting connectivety issues working with adb, dont forget to try and "adb kill-server" to reset the connection before you try adb commands again if phone isnt detected in the first place between any changes you may have made.
If you have issues with rom then its good to start fresh with a factory reset and if that doesnt help then flash zui through QPST and any issues should now be resolved unless there is a hardware issue ofc.
Keep in mind that you should almost always do a factory reset when doing a large update, like if you update from kitkat to lollipop then factory reset or from lollipop to marshmallow also factory reset but this also applies when you change from cyanogen to Zui for example regardless of it its lollipop or marshmallow. Only time when its ok to "dirty flash" (in my opinion) is when you do smaller updates such as updating nightly to nightly on CM12 or nightly to milestone/rc or final. Also applies on modified roms which uses CM12 as base, as long as you are staying on the same rom its fine but if you swap from modified cm12 to vanilla/stock cm12 then you might experience issues.
CM12 Nightly -> CM12 newer Nightly OK
CM12 Nightly -> CM12 Milestone OK
CM12 Nightly -> ZUI any version definately NOT OK
CM12 Nightly -> CM13 NOT OK
CM13 Nightly -> CM13 newer Nightly OK
CM12 MOKEE -> CM12 nightly NOT OK
CM12 MOKEE -> CM13 NOT OK
Stuff "might" work if you update from CM12 to CM13 and also going from a modified CM12 to vanilla or the other way around but it might also cause wierd issues which you might not think of, batterydrain, slow phone, force close etc etc
Downloads and links:
Driver Zuk Z1 Win Vista/7/8/10
https://mega.nz/#!l8pVHIpT!UkcW3Jg4B7YilDjZatvLqGBi_R4vVUYVdkrsUL_Ve9k
Flash program QPST
https://mega.nz/#!4tom3DqL!4a-rRcLef1yS6HJSrBfne_-r9atg6yF3kI_HW8lDaPY
Password: bbs.zuk.cn
Kernel
Chromakernel http://forum.xda-developers.com/zuk-z1/development/kernel-chroma-kernel-r1-tester-t3254724
Minimal ADB
http://forum.xda-developers.com/showthread.php?t=2317790
ROMS (mostly TWRP)
CyanogenOS 12.1 http://forum.xda-developers.com/zuk-z1/development/official-ota-update-links-ota-updating-t3226990 and http://forum.xda-developers.com/zuk-z1/development/rom-cyanogen-os-12-1-yog4pas3oh-t3248820
Cyanogenmod 12.1 http://forum.xda-developers.com/zuk...om-cyanogenmod-12-1-nightlies-lenovo-t3249009
Cyanogenmod 13 http://forum.xda-developers.com/zuk-z1/orig-development/unofficial-cm13-t3277885
Zui QPST version https://mega.nz/#!chQkEAwR!IHeYRxWx38QdML6VxjPdVz08BgbZD-Z-xVuSG150qPU
Zui 1.2.070 (Lollipop) http://bbs.zuk.cn/zui/t53638/
Zui 1.5.x (Marshmallow) http://forum.xda-developers.com/zuk-z1/development/android-6-0-official-zui-1-5-077-beta-t3270587
Exodus http://forum.xda-developers.com/zuk-z1/orig-development/rom-exodus-android-zuk-z1-t3244026
Mokee http://forum.xda-developers.com/zuk...om-mokee-opensource-project-official-t3254984
Toolkit
http://forum.xda-developers.com/zuk-z1/development/win-zuk-z1-toolkit-0-1-alpha-t3235964
Unlock Bootloader without wiping data
http://forum.xda-developers.com/zuk-z1/help/guide-unlock-bootloader-zuk-z1-wiping-t3251801
TWRP (Recovery) by JoaoPaulo
https://www.androidfilehost.com/?fid=24269982087019837
Thanks to everyone involved in helping making this a better device
Thanks to Breadcrust for the initial developing and help
Thanks to javirenart for porting a Toolkit to our device
Thanks to Paulobrien at Modaco for the guide on converting ZUI to CM
And whomever else I have forgotten to mention (shout at me and ill update)
Special thanks to @MrColdbird for fixing a working CM13 with Wifi/Data/GPS/DT2W/bugs and @JoaoPaulo for helping out and giving us an updated and fixed TWRP, kernel stuff and hopefully fingerprint reader!
Some recommended apps
Check hardware sensors
Sensor box for android https://play.google.com/store/apps/details?id=imoblife.androidsensorbox
Check hardware and some sensors
CPUZ https://play.google.com/store/apps/details?id=com.cpuid.cpu_z
Underclock to gain more batterytime
Kernel Auditor https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor
(Personally ive used 1497MHz on cpu keeping interactive governor and put GPU on 200MHz with great result, phone still feels snappy on CM13)
Reserved 2
Great job man....It's really helpful for everyone, instead of searching every where.
You forget how to unlock to boot loader without wiping the device
Tengo10 said:
You forget how to unlock to boot loader without wiping the device
Click to expand...
Click to collapse
Not sure how you would do that? Looked quickly if anyone had written any guides already about it but didnt see any and search function is temporary disabled or unavailable :/
@Titokhan and I tested it and it workes perfect... link: http://forum.xda-developers.com/zuk-z1/help/guide-unlock-bootloader-zuk-z1-wiping-t3251801
@Tengo10
which version you used to kingroot? the latest 4.6.5 b2?
Inviato dal mio Z1 utilizzando Tapatalk
Thanks for your work but some downloads needs password,also to unzip downloads is asked for password.
Can you provide them
---------- Post added at 12:29 PM ---------- Previous post was at 11:51 AM ----------
Thanks for your work but some downloads are asking for password,also in the downloads witch are not asking for password ,the zip files are asking for it.
Can you provide them please ?
fr4nkr0c said:
@Tengo10
which version you used to kingroot? the latest 4.6.5 b2?
Inviato dal mio Z1 utilizzando Tapatalk
Click to expand...
Click to collapse
Oh sry didn't get a message, the kingroot version was the newest but that's not interesting cause it loads the scripts from the web
Reserved
Enviado desde mi Z1 mediante Tapatalk
While trying to unlock band 20 on another phone I tried it on the zuk z1 aswell but didnt work, anyway found out how to enter diagnostic mode in a more permanent matter instead of the brief 5sec you get when using vol+ and inserting usb cable before the phone boots.
Ive added it in first post but the magic is
Code:
adb shell
su
setprop sys.usb.config rndis,diag,adb
unbrick phone method didnt work for me, fails when downloading through QFIL
Driver Zuk Z1 Win Vista/7/8/10
https://mega.nz/#!l8pVHIpT!UkcW3Jg4B...UYVdkrsUL_Ve9k
Could you please insert the correct link of MEGA?
Thanks a lot
Need the drivers for Win 7 @tndb
the mega link u posted needs a decryption key, please post the same
satsmagic said:
Need the drivers for Win 7 @tndb
the mega link u posted needs a decryption key, please post the same
Click to expand...
Click to collapse
Sorry about that, link is updated
tndb said:
Sorry about that, link is updated
Click to expand...
Click to collapse
thanks for posting the link. I am using the International version of Zuk Z1
However, even after installing the drivers you posted my device is not connecting properly to my Win 7 laptop, I tried on a XP machine too.
When i connect the device, by default, it connnects in charging mode and I get a popup saying device not recognised.
If i switch to MTP mode, nothing happens. I wait till the screen turns off, when i turn on the screen again, it again shows in charging mode. I have to disconnect and then reconnect, then it connects in MTP mode. This should not happen, I should be able to swap between the modes without disconnecting and reconnecting the device
If i select Mass storage mode, then it shows an addtional drive in My computer as removable disk, but does'nt show its capacity. If i click on it, it says please insert a disk. so Mass storage mode doesnt work. I have to select MTP again, disconnect and then reconnect to get in MTP mode.
Anyone else facing this issue, what can be a solution for this.
I am on 12.1-YOG4PAS7DF
Also, i found these C-apps on this link https://cyngn.com/c-apps
Should i flash these, would these update anything on my ROM version
please help me !!!!!
Let me know how i can turn off Zuk Z1 as my touch is not working, i tried to root is using Farmaroot and when i restarted it the touch stopped working. Hardware keys are working fine.
I am using zui version 1.2.070 in India, how to upgrade this ??,, I am a simple user, don't have much tech knowledge about this ,kindly guide me
Hi guys,
a week ago my ZUK Z1 started to bootloop without any evident reason.
I found it in this state picking it up from my pocket, so I guessed it was due to some random reboot that occasionally happened to it.
So, stating that:
- I'm with original stock CyanogenOS,
- I never rooted, or even accessed to the recovery menu prior to this event,
- I'm perfectly able now to communicate and send commands to device via adb or in fastboot mode,
problem is that I did NOT enable "USB debugging" and I did NOT OEM unlock when I had the chance to reach Developer options menu through the Android GUI (now I'm blocked by bootloop), resulting in an obvious "no unlocked device" error message each time I try to flash or write system partitions.
The output from "fastboot oem get-info" confirms this status.
I'm operating from a shell with adiministrator's grant in Windows 8.
No luck with "fastboot oem unlock", "fastboot flashing unlock_critical" or "adb root".
I used also "-i 0x2b4c" (vendor code) option in my commands.
Then, my question for you:
is there still a way to unlock bootloader in order to recover with CyanogenOS stock image, in this condition?
I saw there's a "debuggable" image on Cyanogen site, but I've no hint on how to use it and if it could help me.
Maybe ZUK has to provide to me an unlock key: I read on this forum that OnePlus and Huawei have similar option.
Thanks a lot in advance for any hint and suggestion you can give to me.
---------- Post added at 05:43 PM ---------- Previous post was at 05:43 PM ----------
[/COLOR]
dalviking said:
Hi guys,
a week ago my ZUK Z1 started to bootloop without any evident reason.
I found it in this state picking it up from my pocket, so I guessed it was due to some random reboot that occasionally happened to it.
So, stating that:
- I'm with original stock CyanogenOS,
- I never rooted, or even accessed to the recovery menu prior to this event,
- I'm perfectly able now to communicate and send commands to device via adb or in fastboot mode,
problem is that I did NOT enable "USB debugging" and I did NOT OEM unlock when I had the chance to reach Developer options menu through the Android GUI (now I'm blocked by bootloop), resulting in an obvious "no unlocked device" error message each time I try to flash or write system partitions.
The output from "fastboot oem get-info" confirms this status.
I'm operating from a shell with adiministrator's grant in Windows 8.
No luck with "fastboot oem unlock", "fastboot flashing unlock_critical" or "adb root".
I used also "-i 0x2b4c" (vendor code) option in my commands.
Then, my question for you:
is there still a way to unlock bootloader in order to recover with CyanogenOS stock image, in this condition?
I saw there's a "debuggable" image on Cyanogen site, but I've no hint on how to use it and if it could help me.
Maybe ZUK has to provide to me an unlock key: I read on this forum that OnePlus and Huawei have similar option.
Thanks a lot in advance for any hint and suggestion you can give to me.
Click to expand...
Click to collapse
Sideload the official stock rom with zuk z1 tool. That s how i managed to un-brick my zuk. Download the stock rom , cm-12.1-YOG4PAS3OH-ham-signed.zip from this page https://cyngn.com/support. Use the toolkit provided here : http://forum.xda-developers.com/zuk-...alpha-t3235964 to sideload the rom. Wait until the phone restarts and thats it. You must also install adb and fastboot and have adb driver installed.I used the shenqi adb composite driver, but i guess the universal adb driver can work too. I had the same problem. Stuck in bootloop with USB debugging not enabled and bootloader locked.
Or you can try to fastboot the stock rom with the command provided in this useful tool.
Extentho said:
---------- Post added at 05:43 PM ---------- Previous post was at 05:43 PM ----------
[/COLOR]
Sideload the official stock rom with zuk z1 tool. That s how i managed to un-brick my zuk. Download the stock rom , cm-12.1-YOG4PAS3OH-ham-signed.zip from this page https://cyngn.com/support. Use the toolkit provided here : http://forum.xda-developers.com/zuk-...alpha-t3235964 to sideload the rom. Wait until the phone restarts and thats it. You must also install adb and fastboot and have adb driver installed.I used the shenqi adb composite driver, but i guess the universal adb driver can work too. I had the same problem. Stuck in bootloop with USB debugging not enabled and bootloader locked.
Or you can try to fastboot the stock rom with the command provided in this useful tool.
Click to expand...
Click to collapse
Thanks a lot Extentho for your feedback.
I've already tried your fair suggestion: unfortunately, I'm stuck at the end of sideloading the signed .zip.
In fact, I see on screen logs that it's applying the update "unconditionally" (that sounds good), but nevertheless, when finished it returns "xfer: 1.00x" on PC shell and in recovery menu, on device.
Now, either if I reboot or power down and boot it again, the result is the same: still bootloop-ing.
Of course, at any other attempts leveraging on administrative privilege, it says that "device is locked", including those done through the shell tool.
Some excerpts from my last launched commands:
c:\_APP\CM>adb devices
List of devices attached
51f8941d sideload
c:\_APP\CM>adb shell
error: closed
c:\_APP\CM>adb kill-server
c:\_APP\CM>adb root
error: closed
c:\_APP\CM>adb kill-server
c:\_APP\CM>adb usb
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: closed
c:\_APP\CM>adb kill-server
c:\_APP\CM>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
51f8941d sideload
c:\_APP\CM>adb sideload cm-12.1-YOG4PAS3OH-ham-signed.zip
Total xfer: 1.00x
You must have the phone in sideload mode. There is an option to sideload in recovery menu.
Then use the command to sideload from the toolkit. The stock rom must pe renamed sideload and placed on desktop.
If the phone communicates in any way with pc, there is still hope. When you start the sideload process from pc, the phone should show an animation showing the flashing process. Post some pictures from where you are stuck, so i can make an idea about what is going on
my zuk z1 stuck to bootloop,
and android debugging is disabled.
phone can not detecting in fastboot mode.
please help.
Extentho said:
You must have the phone in sideload mode. There is an option to sideload in recovery menu.
Then use the command to sideload from the toolkit. The stock rom must pe renamed sideload and placed on desktop.
If the phone communicates in any way with pc, there is still hope. When you start the sideload process from pc, the phone should show an animation showing the flashing process. Post some pictures from where you are stuck, so i can make an idea about what is going on
Click to expand...
Click to collapse
I've tried also with the toolkit, but it's heavy bugged (also in 5.4 version) and, after all, it gets the exact same problem like me (not surprising, it launches my same commands ).
There's no useful image or snapshot I can share, because I see the animated green android logo moving its antennas on my device, while logs below saying that it's verifying package and then it's unconditionally overwriting system partition.
It seems all so normal and plain.
At the end of the process, no "installation complete" message, but simply I get back to recovery menu (where I started from).
In other attempts, I also wiped cache and user data, prior to rebooting, just to test if it was going to change something, but no luck.
The phone reboots, the "Cyanogen" logo starts to glow for 7/8 times and then... bzzzz, short vibration and all over again (i.e. bootloop).
I tried with an older official signed .zip from Cyanogen OS (cm-12.1-YOG4PAS3AJ-ham-signed, instead of newer cm-12.1-YOG4PAS3OH-ham-signed), but even worst, it fails at "verify package" step, aborting procedure.
MD5 signatures triple-checked each time versus source.
I saw some threads where it seems possible to change the bit, on system image, controlling developer option, to manually post-enable unlocking, but it's suitable only for Nexus or OnePlus One. No instructions for ZUK Z1.
Or maybe do I need a "donor" sharing a stock .zip with this option yet enabled?
Bootloop would be still there, but I possibly could enable to "flash", "boot" and "shell" vs the device, giving me much more options to try.
One last doubt anyway. If I press "Volume Down" + "Power" button at boot, I get into a menu like this:
http: // postimg.org/image/s5badiefh/ (remove extra spaces).
Viewing other examples posted on forums, I noted that at least the "Factory reset" is missing.
Could it be an hint for anything useful?
dalviking said:
I've tried also with the toolkit, but it's heavy bugged (also in 5.4 version) and, after all, it gets the exact same problem like me (not surprising, it launches my same commands ).
There's no useful image or snapshot I can share, because I see the animated green android logo moving its antennas on my device, while logs below saying that it's verifying package and then it's unconditionally overwriting system partition.
It seems all so normal and plain.
At the end of the process, no "installation complete" message, but simply I get back to recovery menu (where I started from).
In other attempts, I also wiped cache and user data, prior to rebooting, just to test if it was going to change something, but no luck.
The phone reboots, the "Cyanogen" logo starts to glow for 7/8 times and then... bzzzz, short vibration and all over again (i.e. bootloop).
I tried with an older official signed .zip from Cyanogen OS (cm-12.1-YOG4PAS3AJ-ham-signed, instead of newer cm-12.1-YOG4PAS3OH-ham-signed), but even worst, it fails at "verify package" step, aborting procedure.
MD5 signatures triple-checked each time versus source.
I saw some threads where it seems possible to change the bit, on system image, controlling developer option, to manually post-enable unlocking, but it's suitable only for Nexus or OnePlus One. No instructions for ZUK Z1.
Or maybe do I need a "donor" sharing a stock .zip with this option yet enabled?
Bootloop would be still there, but I possibly could enable to "flash", "boot" and "shell" vs the device, giving me much more options to try.
One last doubt anyway. If I press "Volume Down" + "Power" button at boot, I get into a menu like this:
http: // postimg.org/image/s5badiefh/ (remove extra spaces).
Viewing other examples posted on forums, I noted that at least the "Factory reset" is missing.
Could it be an hint for anything useful?
Click to expand...
Click to collapse
For me, this method worked exactly as described, booting into stock rom correctly.
now, if you mentioned it in the picture, there is another option. so, i ve noticed too this menu. There is an app called QPST wich can help you. Follow this thread: http://forum.xda-developers.com/zuk-z1/help/bricked-zuk-z1-t3277257 .
So when you enter in QFIL, connect the phone to computer and boot with volume down+ power into this menu from your picture. The Qfil app should detect some ports. You must choose the 9008 one, from what i have read.
Anyway, for me this method, didn t work because the pc couldn t detect the right port, only the zuk tookit did it for me.
You read the thread i suggested, and try that method, it may work for you.
Extentho said:
For me, this method worked exactly as described, booting into stock rom correctly.
now, if you mentioned it in the picture, there is another option. so, i ve noticed too this menu. There is an app called QPST wich can help you. Follow this thread: http://forum.xda-developers.com/zuk-z1/help/bricked-zuk-z1-t3277257 .
So when you enter in QFIL, connect the phone to computer and boot with volume down+ power into this menu from your picture. The Qfil app should detect some ports. You must choose the 9008 one, from what i have read.
Anyway, for me this method, didn t work because the pc couldn t detect the right port, only the zuk tookit did it for me.
You read the thread i suggested, and try that method, it may work for you.
Click to expand...
Click to collapse
Thanks again Extentho.
I saw QPST trick, but it's not catching right port and/or not getting right permission to stop phone from re-booting.
I think that adb/toolkit method should work also for me. I made attempts with other official ROMs: I noticed that for the older ones, the result is a bit different. They get stuck in a "black screen + notify led lighted in blue" state, rather than bootlooping.
Maybe erasing system partitions is needed, but I'm very reluctant to such dangerous way, without expertised advice.
Weirdest thing is that I did anything to get this situation, I just found my device in this mess.
Of course ZUK official support is well silent at my requests.
dalviking said:
Thanks again Extentho.
I saw QPST trick, but it's not catching right port and/or not getting right permission to stop phone from re-booting.
I think that adb/toolkit method should work also for me. I made attempts with other official ROMs: I noticed that for the older ones, the result is a bit different. They get stuck in a "black screen + notify led lighted in blue" state, rather than bootlooping.
Maybe erasing system partitions is needed, but I'm very reluctant to such dangerous way, without expertised advice.
Weirdest thing is that I did anything to get this situation, I just found my device in this mess.
Of course ZUK official support is well silent at my requests.
Click to expand...
Click to collapse
Try to post some pics about the troubles you encounter. If we receive a solution, this may be helpful for all of us in the future. Now, exactly, what can you acces on phone(recovery, fastboot, )?
Also, check varios threads from other phones with the same problems(one plus one, lg , htc) ,etc. Find a solved situation like yours, and we may adapt that solution to you
Hi guys,
Just to close this topic.
I was finally able to install the ZUI ROM through the QFIL program.
It's a little bit tricky, due to the fact that it is strongly suggested:
- to use a Windows 7 machine started without Signature Enforcement enabled;
- to start QFIL (admin mode) and be prepared with all needed files loaded in its GUI;
- to power off the phone, then, while pressing volume up button, inserting the USB cable, attached (better if) on a 2.0 port to PC;
- to be fast pressing "Download" button on QFIL program.
After that, I unlocked the bootloader and performed a lot of alternative recovery process.
So, I installed on the device:
- ZUI ROM
- Cyanogen OS convert from ZUI ROM
- Cyanogen OS last updated ROM
- CyanogenMod 12.1 last nightly ROM
- CyanogenMod 13.0 last nightly ROM
and the winner is...
...
...
...
... none of the above.
Each time the very same behaviour: bootloop. So, my last conclusion is: hardware failure (I guess wi-fi module).
I give up.
But for anyone searching a safe way to unlock a bootloader without accessing to developer options: the QFIL method works like a charm (once installed properly).
Thanks for support.
Messed my zuk z1
I tried to flash stock room in my zuk z1 , I downloaded Qualcomm file for the ROM and installed the required in my laptop,I wiped all data in my phone using TWRP .though my power button is not working I used tool kit to reboot my phone by connecting into fast boot mode,here comes the prob by mistake I entered the wrong command which locks my bootloader .I don't know what to do...help me.....
Today I got my new Xiaomi 3S (4G, 3GB RAM, 32GB ROM) played around with it a little bit and disabled all Google Apps to be found on the phone Except Google Services that couldn't be disabled.
Connected it via WLAN and got promptly OTA offered. I didn't wrote down the MIUI and Android builds but remember manufacturing date August 2016, MIUI was version 7 something.
After the updates where downloaded I was asked to reboot the device what I confirmed and the updates where installed. Now the phone is stuck with a black screen and white "MI Powered By Android" on it.
Nothing changed since 3 hours now. Any idea what to do?
Phone can't even be turned off/does not recognize hardware button presses.
This is a known issue, disabling google apps causes issues . You should now try following this guide http://en.miui.com/thread-327861-1-1.html
timbohobbs said:
This is a known issue, disabling google apps causes issues . You should now try following this guide http://en.miui.com/thread-327861-1-1.html
Click to expand...
Click to collapse
Thanks a lot for your reply, tried it already yesterday while the Phone was in endless boot queue without luck, hence the non working buttons update.
But today after the battery was emptied over night I got into the recovery mode menu!
Just a question before I go ahead to follow the step by step guide:
Though I read this thread/vote I'm non the smarter. If I want to go google free, Xiaomi Global or Xiaomi EU ROM?
I'd also use XPosed framework with XPrivacy again. IMUI seems nice, is CM 13 the only alternative for non google/XPosed/Xprivacy then?
I currently have a 3s prime but it's a present for my son so haven't flashed anything, just take ota's. I have read quite a bit though and you should maybe just check the rom threads for roms with separate gapps packages, that way you could remove what you want prior to flashing. Don't know about xposed but again, ask in the rom threads. [emoji106]
Update: No success, when going into recovery mode (pushing volume up and power button) and choose download mode the phone will just reboot into endless boot-loop.
For people with the same problem (after disabling google apps) maybe they can get their device back to work with this http://en.miui.com/thread-378963-1-1.html
The only Way to get you phone back is to use a Deep Flash Cable i think
I was able to solve the problem by installing a fastboot-rom. Pressing power button and volume + for around 20 seconds got me into recovery menu.
Than I was just following a guide to install an original MIUI rom on devices with locked bootloader.
well to get to download mode you can enter "fastboot oem edl" without the "" and you will go to edl from fastboot mode. HOPE THIS HELPS
timbohobbs said:
This is a known issue, disabling google apps causes issues . You should now try following this guide http://en.miui.com/thread-327861-1-1.html
Click to expand...
Click to collapse
Now I know why my phone went into a bootloop. Won't disable any Google apps anymore.
Disabling any apps in MIUI8 will cause the phone cannot reboot... you can format everything through a recovery (have to flash manually because it doesn't come with recovery), or flash a new ROM through fastboot mode (if you have unlocked your bootloader), or send back to service center to claim warranty (if there is any service center in your area), or throw it and buy a new one
abhi0005 said:
well to get to download mode you can enter "fastboot oem edl" without the "" and you will go to edl from fastboot mode. HOPE THIS HELPS
Click to expand...
Click to collapse
I have same problem but in my case developer option is locked so oem is off and thus port COM10 is not being shown in Miflash, also fastboot oem edl says device is locked, oem edl is not allowed. In my case 3s prime went into bootloop while Iwas using youtube. Please help!!
Current state:
TWRP is version 3.2.1-0 — If I want to shut-off, device restarts with:
g.co/ABH error: "lock the bootloader" — how do I get rid of this nuissance?
Fastboot displays with tiny font (due to the high screen resolution I guess) — but is fully responsive to commands from my notebook
Which system would you suggest? Does LinageOS support the camera-features?
Thank you for all assistance!
[email protected] said:
Current state:
TWRP is version 3.2.1-0 — If I want to shut-off, device restarts with:
g.co/ABH error: "lock the bootloader" — how do I get rid of this nuissance?
Fastboot displays with tiny font (due to the high screen resolution I guess) — but is fully responsive to commands from my notebook
Which system would you suggest? Does LinageOS support the camera-features?
Thank you for all assistance!
Click to expand...
Click to collapse
Any updates?
Warning message is normal with unlocked bootloader. For system, you can follow lineage flashing procedures from whichever verion (14, 15, 16, etc.) you're wanting. Camera features work pretty good with Open Camera App. I'm currently using the Fulmics Rom, but I tend to try others over time.
LineageOS 17 up and running
Aimless Rambler said:
Any updates?
Click to expand...
Click to collapse
Yes, I succeeded in installing Lineage. It appears, that the device might have a hardware problem: the switch/fingerprint reader seems to be little responsive.
Need to figure that out now…
The fingerprint sensor might just be faulty, as it is connected to the motherboard with around 10 springs that may be damaged when the phone is opened and closed.
Yes, I replaced the sensor. Even the volume became faulty. The LG5 is too delicate!
Today I wanted to install LOS17 + LOS recovery. But I fail to boot into recovery, saw it once shortly. Always end-up in fastboot again!!!
#fastboot reboot recovery won't work. Any suggestion for a fastboot cmd that works?
Thx.
Hi everyone,
I have the all classic fingerprint sensor not working after display got changed problem and even an MDM tool flash / EDL mode did not fix it.
If I calibrate it from the debug menu it works until the next restart
Does anyone have the corresponding and in an OK state persist.img? (I have the European version)
Thank you!
side info:
To calibrate it I type in the dialer: "*#899#", then "After Sales Calibration" and 6776.