Zui to Cyanogen - Zuk Z1 Q&A, Help & Troubleshooting

Is there any way to convert ZUI to Cyanogen
Download the modified recovery image - DOWNLOAD (ROMraid)
Download the stock (re-signed) Cyanogen OS system image - DOWNLOAD (ROMraid)
Ensure you have fastboot and adb on your machine
If you are using Windows, install the drivers from this topic
Enable the developer menu (tap ZUI version several times) and enable USB debugging in the developer menu
Type 'adb reboot bootloader' to put your device in bootloader mode
Type 'fastboot -i 0x2b4c oem get-device-info' and check your bootloader is unlocked - if it is not, use 'fastboot -i 0x2b4c oem unlock'
Type 'fastboot -i 0x2b4c boot z1.recovery.testkeys.img' to boot the custom recovery image
Select the option to wipe the device (important!)
Select the install update / from USB option
Type 'adb sideload z1.cyanogen.convert.signed.zip'
Wait for this to complete then reboot
i trying to do with your steps, above steps are passed, but on step adb sideload z1.cyanogen.convert.signed.zip I have error message show " loading: 'z1.cyanogen.convert.signed.zip' error: device '<null> not found" how can i do? help me please ...

Well I also couldn't follow this guide but I finally managed to solve the issue with the help of a friend!
Put the ROM on the storage of the zuk!
Do all steps and unlock the bootloader.
I mean do all this:
Download the modified recovery image - DOWNLOAD (ROMraid)
Download the stock (re-signed) Cyanogen OS system image - DOWNLOAD (ROMraid)
Ensure you have fastboot and adb on your machine
If you are using Windows, install the drivers from this topic
Enable the developer menu (tap ZUI version several times) and enable USB debugging in the developer menu
Type 'adb reboot bootloader' to put your device in bootloader mode
Type 'fastboot -i 0x2b4c oem get-device-info' and check your bootloader is unlocked - if it is not, use 'fastboot -i 0x2b4c oem unlock'
Type 'fastboot -i 0x2b4c boot z1.recovery.testkeys.img' to boot the custom recovery image
Select the option to wipe the device (important!)
Boot into cm recovery and make a factory reset! Don't wipe media!
Now flash the rom.zip as usual! The same way you flash any rom via recovery!
Now reboot system.
You will have cyanogen! No need for any sideload or push commands in adb!
Once cyanogen boots, make a full factory reset from within the settings!
Enjoy!

Recovery img cannot load when i flash it
Hello if i may ask why cant i get recovery to flash i did follow all steps. But stuck at recovery flashing .. says it cannot load. What am i missing here pls help tnx

codding said:
Is there any way to convert ZUI to Cyanogen
Download the modified recovery image - DOWNLOAD (ROMraid)
Download the stock (re-signed) Cyanogen OS system image - DOWNLOAD (ROMraid)
Ensure you have fastboot and adb on your machine
If you are using Windows, install the drivers from this topic
Enable the developer menu (tap ZUI version several times) and enable USB debugging in the developer menu
Type 'adb reboot bootloader' to put your device in bootloader mode
Type 'fastboot -i 0x2b4c oem get-device-info' and check your bootloader is unlocked - if it is not, use 'fastboot -i 0x2b4c oem unlock'
Type 'fastboot -i 0x2b4c boot z1.recovery.testkeys.img' to boot the custom recovery image
Select the option to wipe the device (important!)
Select the install update / from USB option
Type 'adb sideload z1.cyanogen.convert.signed.zip'
Wait for this to complete then reboot
i trying to do with your steps, above steps are passed, but on step adb sideload z1.cyanogen.convert.signed.zip I have error message show " loading: 'z1.cyanogen.convert.signed.zip' error: device '<null> not found" how can i do? help me please ...
Click to expand...
Click to collapse
How do i get rid of the watermark?

Related

[Q] Stuck in FIrefox OS.

So I moved my Android zips off of my phone to make some extra room for Firefox OS. And when I was done playing with it I found out that the USB connection to get into the SD card does not work (another reason to have removable storage). I have Google_Nexus_4_ToolKit_v2.0.0 and tried everything I could think of in there. I dont know how to ADB except to put the phone into sideload mode and you use command prompt. I have CWM recovery on it. So any help would be awesome. I will take a good link or some step by step stuff. Thank you.
jaed.43725 said:
So I moved my Android zips off of my phone to make some extra room for Firefox OS. And when I was done playing with it I found out that the USB connection to get into the SD card does not work (another reason to have removable storage). I have Google_Nexus_4_ToolKit_v2.0.0 and tried everything I could think of in there. I dont know how to ADB except to put the phone into sideload mode and you use command prompt. I have CWM recovery on it. So any help would be awesome. I will take a good link or some step by step stuff. Thank you.
Click to expand...
Click to collapse
Calm down, there's solution.
1. Download Google Factory Image from here(4.3)
2. Extract it in your adb directory. You should see some files, but we oly need the radio.img, bootloader.img and image-occam-blabla.zip
3. Open a command window in your adb directory.
4. Reboot into bootloader and write the following code:
Code:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-blablabla.img
> fastboot reboot-bootloader
> fastboot flash radio radio-blablabla.img
> fastboot reboot-bootloader
> fastboot -w update image-blablabla.zip
5. The phone will reboot. Now u can use the toolkit to flash a recovery again (select 4.2.2 firmware) and starting rooting and flashing roms again.
Good luck! If u need any help just quote my comment so I get notified
luiseteyo said:
Calm down, there's solution.
1. Download Google Factory Image from here(4.3)
2. Extract it in your adb directory. You should see some files, but we oly need the radio.img, bootloader.img and image-occam-blabla.zip
3. Open a command window in your adb directory.
4. Reboot into bootloader and write the following code:
Code:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-blablabla.img
> fastboot reboot-bootloader
> fastboot flash radio radio-blablabla.img
> fastboot reboot-bootloader
> fastboot -w update image-blablabla.zip
5. The phone will reboot. Now u can use the toolkit to flash a recovery again (select 4.2.2 firmware) and starting rooting and flashing roms again.
Good luck! If u need any help just quote my comment so I get notified
Click to expand...
Click to collapse
Ok. So what I did was kinda following your setup here. I had to get the Android SDK first. Then extract that into C:/. Then I got the 4.3 like you said and extracted that C:\adt-bundle-windows-x86_64-20130917\sdk\platform-tools. Then because of the new SDK I put the phone into the first 3-button mode. I then ran flash-all. And after a minute I had stock 4.3.

[Q] yu yureka not rooting after yesterday update of 73 mb

Dear Developers
Please help me, i really need yur help
yesterday i got my new yu yureka, around 7 pm i root my phone by unlocking bootloader and flashing twrp recovery and flashing super user by twrp
using cmand prompt
fastboot -i 0x1ebf devices
fastboot -i 0x1ebf oem unlock
fastboot -i 0x1ebf flash recovery yu-twrp-recovery.img
fastboot -i 0x1ebf reboot
all done and phone root
but this monday morning when i saw a update of 73 mb , i update my phone and it come to know, now my phone is unroot again, super user app gone
then i again become developer--mode and click usb dibbuging
doing all this commands as i mentioned above...it said..ok ok ok ok
but when i go to recovery mode to flash super user.......it shows ....cyanogen recovery mode..not twrp recovery
i changed recovery file and use cwm recovery and flash it using command prompt..but in recovery mode it shown only cyanogen mode
fastboot -i 0x1ebf oem lock....................using this command..i lock my bootloader again and fastboot -i 0x1ebf oem unlock...again unlock ....but nothing happens....plzzzz tell me...how to root
harish joshi said:
Dear Developers
Please help me, i really need yur help
yesterday i got my new yu yureka, around 7 pm i root my phone by unlocking bootloader and flashing twrp recovery and flashing super user by twrp
using cmand prompt
fastboot -i 0x1ebf devices
fastboot -i 0x1ebf oem unlock
fastboot -i 0x1ebf flash recovery yu-twrp-recovery.img
fastboot -i 0x1ebf reboot
all done and phone root
but this monday morning when i saw a update of 73 mb , i update my phone and it come to know, now my phone is unroot again, super user app gone
then i again become developer--mode and click usb dibbuging
doing all this commands as i mentioned above...it said..ok ok ok ok
but when i go to recovery mode to flash super user.......it shows ....cyanogen recovery mode..not twrp recovery
i changed recovery file and use cwm recovery and flash it using command prompt..but in recovery mode it shown only cyanogen mode
fastboot -i 0x1ebf oem lock....................using this command..i lock my bootloader again and fastboot -i 0x1ebf oem unlock...again unlock ....but nothing happens....plzzzz tell me...how to root
Click to expand...
Click to collapse
Yes after update there is some problem in installing recovery and rooting.
So after unlocking the bootloader do the following steps
1. Download superuser. zip and place it in your external sd-card
2. Now flash the recovery.img using fastboot
3. Now boot into recovery using "vol up+vol down+power"
4. Flash the superuser. zip
*note: please don't do normal reboot after flashing recovery because it will write the stock recovery again into recovery partition.
Regards,
aashking
Enable developer mode & enter developer menu
Go to -> update CM recovery.
That was ticked by default, untick it and then flash custom recovery.

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

How to install and use ADB and fastboot

1.
Connect your Android device to computer via USB.
2.
Ensure USB Debugging mode is ENABLED on Android device.
Settings > About Phone > Build number > Tap it 7 times to become developer;
Settings > Developer Options > USB Debugging.
3.
download adb driver
http://adbdriver.com/downloads/
download Minimal ADB and Fastboot
https://forum.xda-developers.com/showthread.php?t=2317790
4.
unzip adb driver and instal it
http://adbdriver.com/documentation/...river-installer-for-windows-xp-vista-7-8.html
http://adbdriver.com/documentation/how-to-install-adb-driver-on-windows-8-10-x64.html
5.
Extract the Minimal ADB and Fastboot Tool file to your PC
6.
Download your RecoveryFile.img file or full fastboot Rom file
and put under the extracted folder “ Fastboot or Minimal ADB and Fastboot ”
so all files will be in single folder
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
7.
open folder Minimal ADB and Fastboot
in the folder , On your keyboard press SHIFT and right click with your mouse " Shift + right click "
click on " open command window here "
8.
Now type following command
adb fastboot
Unlocking the bootloader
Note: Using the fastboot command
When the fastboot command is used on the Storm, the vendor id command option must be added.
The vendor id for the Storm is 0x2970. For example, fastboot devices, would be fastboot -i 0x2970 devices.
Enable OEM unlock in the Developer options settings on the device.
(Note: Not all devices have this setting, so continue with next step if yours does not.)
Connect the device to the computer through USB.
From a terminal on a computer, type the following to boot the device into fastboot mode:
adb reboot bootloader
Once the device is in fastboot mode, verify your PC sees the device by typing fastboot devices
If you don't see your device serial number, and instead see "<waiting for device>", fastboot is not configured properly on your machine. See fastboot documentation for more info.
If you see "no permissions fastboot", try running fastboot as root.
From the same terminal, type the following command to unlock the bootloader:
fastboot -i 0x2970 oem unlock-go
If the device doesn't automatically reboot, reboot it from the menu. It should now be unlocked.
Since the device resets completely, you will need to re-enable USB debugging on the device to continue.
fastboot reboot
Installing a custom recovery using fastboot
Open a terminal on your PC and reboot the device into fastboot mode by typing
adb reboot bootloader
or by using the hardware key combination for your device while it is powered off.
Once the device is in fastboot mode, verify your PC sees the device by typing
fastboot devices
Flash recovery onto your device by entering the following command:
fastboot flash recovery your_recovery_image.img
where the latter part is the filename of the recovery image.
fastboot reboot
full rom fastboot
adb reboot bootloader
fastboot devices
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot erase DDR
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl1bak sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash tzbak tz.mbn
fastboot flash hyp hyp.mbn
fastboot flash hypbak hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash rpmbak rpm.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash cache cache.img
fastboot erase splash
fastboot flash splash splash.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot reboot
Thanks for the great step by step tutorial.
I've tried to instal the Fastboot Image via the above guidem
1. Connect your Android device to computer via USB.
2. Ensure USB Debugging mode is ENABLED on Android device.
3. download adb driver
4. unzip adb driver and instal it
5. Extract the Minimal ADB and Fastboot Tool file to your PC
6. Download your RecoveryFile.img file or full fastboot Rom file and put under the extracted folder “ Fastboot or Minimal ADB and Fastboot ” so all files will be in single folder. (Which I've done with TOS319I Fastboot Image file)
7. open folder Minimal ADB and Fastboot, click on " open command window here "
8. Now type following command
adb fastboot
Unlocking the bootloader
adb reboot bootloader
fastboot reboot
Then, adb reboot bootloader
fastboot devices
*** But when I use the fastboot flash recovery TOS319I.img and to use the downloaded and renamed recover image, it says unable to load file TOS319I.img
Can you please let me know what should I do?
Thanks in advance
sellfy said:
Thanks for the great step by step tutorial.
I've tried to instal the Fastboot Image via the above guidem
1. Connect your Android device to computer via USB.
2. Ensure USB Debugging mode is ENABLED on Android device.
3. download adb driver
4. unzip adb driver and instal it
5. Extract the Minimal ADB and Fastboot Tool file to your PC
6. Download your RecoveryFile.img file or full fastboot Rom file and put under the extracted folder “ Fastboot or Minimal ADB and Fastboot ” so all files will be in single folder. (Which I've done with TOS319I Fastboot Image file)
7. open folder Minimal ADB and Fastboot, click on " open command window here "
8. Now type following command
adb fastboot
Unlocking the bootloader
adb reboot bootloader
fastboot reboot
Then, adb reboot bootloader
fastboot devices
*** But when I use the fastboot flash recovery TOS319I.img and to use the downloaded and renamed recover image, it says unable to load file TOS319I.img
Can you please let me know what should I do?
Thanks in advance
Click to expand...
Click to collapse
i know that you should use cyanogen os version rom of wileyfox storm (FIRST)
then you can flash custom rom or upgrade to official android 7 rom
that means , first you should downgrade to cyanogen 13
Again bootloop
ghertas said:
1.
Connect your Android device to computer via USB.
2.
Ensure USB Debugging mode is ENABLED on Android device.
Settings > About Phone > Build number > Tap it 7 times to become developer;
Settings > Developer Options > USB Debugging.
3.
download adb driver
http://adbdriver.com/downloads/
download Minimal ADB and Fastboot
https://forum.xda-developers.com/showthread.php?t=2317790
4.
unzip adb driver and instal it
http://adbdriver.com/documentation/...river-installer-for-windows-xp-vista-7-8.html
http://adbdriver.com/documentation/how-to-install-adb-driver-on-windows-8-10-x64.html
5.
Extract the Minimal ADB and Fastboot Tool file to your PC
6.
Download your RecoveryFile.img file or full fastboot Rom file
and put under the extracted folder “ Fastboot or Minimal ADB and Fastboot ”
so all files will be in single folder
7.
open folder Minimal ADB and Fastboot
in the folder , On your keyboard press SHIFT and right click with your mouse " Shift + right click "
click on " open command window here "
8.
Now type following command
adb fastboot
Unlocking the bootloader
Note: Using the fastboot command
When the fastboot command is used on the Storm, the vendor id command option must be added.
The vendor id for the Storm is 0x2970. For example, fastboot devices, would be fastboot -i 0x2970 devices.
Enable OEM unlock in the Developer options settings on the device.
(Note: Not all devices have this setting, so continue with next step if yours does not.)
Connect the device to the computer through USB.
From a terminal on a computer, type the following to boot the device into fastboot mode:
adb reboot bootloader
Once the device is in fastboot mode, verify your PC sees the device by typing fastboot devices
If you don't see your device serial number, and instead see "<waiting for device>", fastboot is not configured properly on your machine. See fastboot documentation for more info.
If you see "no permissions fastboot", try running fastboot as root.
From the same terminal, type the following command to unlock the bootloader:
fastboot -i 0x2970 oem unlock-go
If the device doesn't automatically reboot, reboot it from the menu. It should now be unlocked.
Since the device resets completely, you will need to re-enable USB debugging on the device to continue.
fastboot reboot
Installing a custom recovery using fastboot
Open a terminal on your PC and reboot the device into fastboot mode by typing
adb reboot bootloader
or by using the hardware key combination for your device while it is powered off.
Once the device is in fastboot mode, verify your PC sees the device by typing
fastboot devices
Flash recovery onto your device by entering the following command:
fastboot flash recovery your_recovery_image.img
where the latter part is the filename of the recovery image.
fastboot reboot
full rom fastboot
adb reboot bootloader
fastboot devices
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot erase DDR
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl1bak sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash tzbak tz.mbn
fastboot flash hyp hyp.mbn
fastboot flash hypbak hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash rpmbak rpm.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash cache cache.img
fastboot erase splash
fastboot flash splash splash.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
I've exactly followed your instructions for *"full rom fastboot"*, and all was done 'OK'. But Still the device is in bootloop and not going into recovery OR andriod system
ghertas said:
"full rom" was a zip file of cyanogen version
cyanogen realised two files of each rom
recovery version and fastboot version
if you want to install a custom rom on your device
Yes, I've download cyanogen Fastboot version, The only problem i've got is that my phone doesn't go into recovery mode although I've flashed TWRP also cn 13, but still the device only boots in fastboot only
When I select Recovery mode in Fastboot menu the device goes into bootloop.
Click to expand...
Click to collapse
idforpc said:
ghertas said:
"full rom" was a zip file of cyanogen version
cyanogen realised two files of each rom
recovery version and fastboot version
if you want to install a custom rom on your device
Yes, I've download cyanogen Fastboot version, The only problem i've got is that my phone doesn't go into recovery mode although I've flashed TWRP also cn 13, but still the device only boots in fastboot only
When I select Recovery mode in Fastboot menu the device goes into bootloop.
Click to expand...
Click to collapse
"fastboot reboot"
after boot the device , "Power off" the device and press volume down and power at the same time until you see the recovery on screen
"TWRP" is a custome recovery for install custom rom s
did you do all of those on " lineage wiki " ?
https://wiki.lineageos.org/devices/kipper/install
download the last version of twrp recovery
https://androidfilehost.com/?fid=1395089523397922500
Click to expand...
Click to collapse

zuk z1 bootloader locked when twrp installed

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.

Categories

Resources