Database Users

Bootloader splash screen

hello,
I need to return the phone to retailer, but cannot get rid of the tux penguin, I need the old ZUK bootloader splash to return the phone. How can I do this? Would returning the phone to Stock COS 12.1 with a COS recovery do this?
cheers
I've updated to the unofficial CM13 ROM http://forum.xda-developers.com/zuk-z1/orig-development/unofficial-cm13-t3277885
I've also updated to the MM firware, Bootloader latest https://www.androidfilehost.com/?fid=24351979186684091

Just flash the original COS Version, if everything works, flash the stock Rom, then lock the bootloader and you should be on the safe side
---------- Post added at 03:22 PM ---------- Previous post was at 03:21 PM ----------
Stock recovery on ROM sry

Flash the emmc-appboot file from a COS fastboot package into the aboot partition, that should restore your previous Cyanogen screen.
You might have to also flash the sbl1 file into the same named partition when doing this.

MrColdbird said:
Flash the emmc-appboot file from a COS fastboot package into the aboot partition, that should restore your previous Cyanogen screen.
You might have to also flash the sbl1 file into the same named partition when doing this.
Click to expand...
Click to collapse
Thank you - Would flashing the whole cm-12.1-YOG4PAS3OH-ham-signed-fastboot.zip file via TWRP achieve the same result or would I need to flash the files only you mention via TWRP be needed?

EggZenBeanz said:
Thank you - Would flashing the whole cm-12.1-YOG4PAS3OH-ham-signed-fastboot.zip file via TWRP achieve the same result or would I need to flash the files only you mention via TWRP be needed?
Click to expand...
Click to collapse
This is what I did:
Download the fast signed image of COS 12.1 here http://builds.cyngn.com/factory/ham/...d-fastboot.zip
Unzip it
Open cmd or terminal
Go to the unzipped folder
Execute this step by step:
fastboot -i 0x2b4c flash aboot emmc_appsboot.mbn
fastboot -i 0x2b4c flash modem NON-HLOS.bin
fastboot -i 0x2b4c flash rpm rpm.mbn
fastboot -i 0x2b4c flash sbl1 sbl1.mbn
fastboot -i 0x2b4c flash dbi sdi.mbn
fastboot -i 0x2b4c flash splash splash.img
fastboot -i 0x2b4c flash tz tz.mbn
fastboot -i 0x2b4c flash persist persist.img
This will restore your bootloader with logo to stock Cyanogen. It will remain unlocked.

How to flash stock images - brick recovery

I managed to soft brick my Storm with one of the CM13 updates (both normal boot and recovery just resulted in a black flickering screen), it seems others are having similar issues so here are instructions for restoring your phone to the stock image, this fixed the brick for me.
You need fastboot so download and install the Android SDK if not already present: http://developer.android.com/sdk/installing/index.html
Download and uncompress the stock Cyanogen OS fastboot zip: https://cyngn.com/support
Boot your phone into fastboot mode, (plug in USB then hold down vol+ and power until rebooted, keep holding vol+ until in fastboot)
Start a shell/command prompt on your computer to execute the commands below.
THIS WILL WIPE EVERYTHING!!! - THIS IS A COMPLETE STOCK RESTORATION!!!
Execute these fastboot commands from within the extracted stock zip directory:
Code:
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
If the cache command gives an error try continuing anyway.
If you want to try to save your user data skip the userdata command, but no guarantees.
Search the other threads on XDA for instructions on booting or flashing custom recoveries, ROMs, root etc.

I've also bricked my Storm with cm13 update in January . I flashed every img using fastboot and it recovered. i skipped the other files and it still works. Good that someone written tutorial for others. I was planning to write it by myself but you were faster

I have made a simple batch script that executes the commands by itself. You need to unzip and place these 2 files into images direction. It should look like this:
View attachment 3656958
Click on picture to make it bigger
then just connect your device in fastboot mode and open the FLASH-ALL.bat file. Press enter. It will flash all the images. IT WILL ONLY WORK IF FILES WILL BE PLACED LIKE ON THE SCREENSHOT!!

I got blinking brick. I can not go into fastboot

@up Don't connect the usb cord. While it's blinking press and hold vol up+ power for 10 seconds, release power button and it should go into fastboot.
If no, let it fully discharge, and then try volup + power

95% of the time flashing system should do the trick. Otherwise the flashall argument should save you a lot of typing.

aciupapa said:
I've also bricked my Storm with cm13 update in January . I flashed every img using fastboot and it recovered. i skipped the other files and it still works. Good that someone written tutorial for others. I was planning to write it by myself but you were faster
Click to expand...
Click to collapse
my storm is dead, i cant get into recovery or download mode....any advice...i did get it rooted and the recovery...i flash the cm 13 kipper and it went dead...red light comes on when charging or usb connection.

miSAKe said:
I managed to soft brick my Storm with one of the CM13 updates (both normal boot and recovery just resulted in a black flickering screen), it seems others are having similar issues so here are instructions for restoring your phone to the stock image, this fixed the brick for me.
You need fastboot so download and install the Android SDK if not already present: http://developer.android.com/sdk/installing/index.html
Download and uncompress the stock Cyanogen OS fastboot zip: https://cyngn.com/support
Boot your phone into fastboot mode, (plug in USB then hold down vol+ and power until rebooted, keep holding vol+ until in fastboot)
Start a shell/command prompt on your computer to execute the commands below.
THIS WILL WIPE EVERYTHING!!! - THIS IS A COMPLETE STOCK RESTORATION!!!
Execute these fastboot commands from within the extracted stock zip directory:
Code:
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
If the cache command gives an error try continuing anyway.
If you want to try to save your user data skip the userdata command, but no guarantees.
Search the other threads on XDA for instructions on booting or flashing custom recoveries, ROMs, root etc.
Click to expand...
Click to collapse
Perfect, thanks.
Would have worked FIRST time if I'd read your instructions properly, instead it worked the SECOND time. Important to download "the stock Cyanogen OS fastboot zip" from the Cyngn support page - there are two similar looking files and obviously I picked the wrong one first.
Thanks again.

miSAKe said:
Hello,
As you know, cyngn.com is unavailable. i need kipper files, specially original recovery.img
do you know any alive link(s)? or can you upload/send to me?
thanks very much
Click to expand...
Click to collapse

ftabashir said:
miSAKe said:
Hello,
As you know, cyngn.com is unavailable. i need kipper files, specially original recovery.img
do you know any alive link(s)? or can you upload/send to me?
thanks very much
Click to expand...
Click to collapse
here
https://www.androidfilehost.com/?w=files&flid=59917
Click to expand...
Click to collapse

ghertas said:
ftabashir said:
here
https://www.androidfilehost.com/?w=files&flid=59917
Click to expand...
Click to collapse
thanks. but this is the whole ROM. i downloaded it and couldn't find "recovery.img". how can i find original recovery for kipper (wileyfox storm)?
Click to expand...
Click to collapse

ftabashir said:
ghertas said:
thanks. but this is the whole ROM. i downloaded it and couldn't find "recovery.img". how can i find original recovery for kipper (wileyfox storm)?
Click to expand...
Click to collapse
cm-13.1.2
instal via ADB Fastboot
youtube help you to how instal
recovery.
https://www.androidfilehost.com/?fid=24727376692773052
full rom
https://www.androidfilehost.com/?fid=24727369092694607
Click to expand...
Click to collapse

ghertas said:
ftabashir said:
cm-13.1.2
instal via ADB Fastboot
youtube help you to how instal
recovery.
https://www.androidfilehost.com/?fid=24727376692773052
full rom
https://www.androidfilehost.com/?fid=24727369092694607
Click to expand...
Click to collapse
Thanks. but I downloaded recovery from this link.
Then i tried to run "fastboot flash recovery cm-13.1.2-ZNH2KAS3NA-kipper-boot-debuggable-6c1a30b194.img"
but it said:
OEM locked device can't boot unsigned image. Do you want to continue?
Yes
No
I pressed no and it said:
target reported max download size of 268435456 bytes
sending 'recovery' (20866 KB)...
OKAY [ 0.791s]
writing 'recovery'...
FAILED (remote: Image could brick the device. Flashing canceled.)
finished. total time: 2.129s
I ran the command again and this time I chose Yes and it said:
target reported max download size of 268435456 bytes
sending 'recovery' (20866 KB)...
OKAY [ 0.783s]
writing 'recovery'...
OKAY [ 16.962s]
finished. total time: 17.751s
but as it said, when i try to boot recovery i saw this message: OEM locked device can't boot unsigned image. oem unlock or flash signed boot image.
I need a signed recovery, but i couldn't find such recovery anywher. Please help me
Also when i try to run fastboot oem unlock it says that: FAILED (remote: oem unlock is not allowed)
So the only solution would be installing a signed recovery.
Note: 3day ago i installed a custom recovery without oem unlock. now my device stops at boot animation and i cant boot into android. also i can't boot into recovery because oem is locked and recovery is not signed. I need a signed recovery.
Click to expand...
Click to collapse

miSAKe said:
I managed to soft brick my Storm with one of the CM13 updates (both normal boot and recovery just resulted in a black flickering screen), it seems others are having similar issues so here are instructions for restoring your phone to the stock image, this fixed the brick for me.
You need fastboot so download and install the Android SDK if not already present: http://developer.android.com/sdk/installing/index.html
Download and uncompress the stock Cyanogen OS fastboot zip: https://cyngn.com/support
Boot your phone into fastboot mode, (plug in USB then hold down vol+ and power until rebooted, keep holding vol+ until in fastboot)
Start a shell/command prompt on your computer to execute the commands below.
THIS WILL WIPE EVERYTHING!!! - THIS IS A COMPLETE STOCK RESTORATION!!!
Execute these fastboot commands from within the extracted stock zip directory:
Code:
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
If the cache command gives an error try continuing anyway.
If you want to try to save your user data skip the userdata command, but no guarantees.
Search the other threads on XDA for instructions on booting or flashing custom recoveries, ROMs, root etc.
Click to expand...
Click to collapse
How did you enter fastboot without enabling usb debugging/developer option?

Mobile network issue

Hello, i have ZTE axon 7 ZTE A2017G model. When i bought it from china, via allieexpress, it was on stock 4.0 mifavor chinese version. It was not updating to the latest nougat. I tried updating manually via recovery mode through SD card. I was succesful to update it to 7.1.1 nougat. Unfortunately my Mobile network became completely disabled. I understand that i used an incorrect firmware. Current build number: ZTE A2017GV1.2.0B05. How and what should i do in order to restore my mobile network. I am currently living in UK. Should i completly hard reset, install chinese or Eu version, i am confused. Anyone can help me with this?

Hi,
Hardwares are different between china and europe model, therefore radio firmwares within the roms also.
I would advise you to flash the latest chinese version of the rom to go back to normal.
However if you have an unlocked bootloader, you can try flashing only the radio modem via adb.
Good luck

Cojy said:
Hi,
Hardwares are different between china and europe model, therefore radio firmwares within the roms also.
I would advise you to flash the latest chinese version of the rom to go back to normal.
However if you have an unlocked bootloader, you can try flashing only the radio modem via adb.
Good luck
Click to expand...
Click to collapse
Thank you. And maybe if you would so kind, any links for the best guide how to flash radio modem via adb?
Cheers

A bit of a late reply, I did not get any notification.
First reboot into fastboot (adb reboot bootloader, the screen ued to display fastboot on my other android phone)
After that it is a 'fastboot flash radio signed_radio.img'
You can flash every .img file that you find in a rom via fastboot (if you have issues with gyroscope, modem, radio...)
here are some common commands:
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash rpm rpm.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
It is usually fastboot flash <component> <component>.img like flash boot boot.img or flash radio radio.img...
Let us know if it solves your issue

Cojy said:
A bit of a late reply, I did not get any notification.
First reboot into fastboot (adb reboot bootloader, the screen ued to display fastboot on my other android phone)
After that it is a 'fastboot flash radio signed_radio.img'
You can flash every .img file that you find in a rom via fastboot (if you have issues with gyroscope, modem, radio...)
here are some common commands:
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash rpm rpm.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
It is usually fastboot flash <component> <component>.img like flash boot boot.img or flash radio radio.img...
Let us know if it solves your issue
Click to expand...
Click to collapse
Thanks for the reply.
Unfotrunately, i am completely new to this kind of thing. I managed to reboot into fastboot. But now im not sure what to do. Do i just put in commands? Do i need to download the radio.img files or? If you would be so kind to provide a bit more detail to this.
Thanks again

Fruktoze said:
Thanks for the reply.
Unfotrunately, i am completely new to this kind of thing. I managed to reboot into fastboot. But now im not sure what to do. Do i just put in commands? Do i need to download the radio.img files or? If you would be so kind to provide a bit more detail to this.
Thanks again
Click to expand...
Click to collapse
The usual saying is don't do that if you don't know what you are doing ! This could block your phone and you would have a hard time restoring it if you are not at ease with that sort of things.
This being said, you need to retrieve the .img file from your operating system image, put it in your adb folder (or whatever folder but you will have to add the path) and run the aforesaid commands.

Flashing Redmi note 4 (Mido) via CMD

Download Firmware From here---> http://en.miui.com/a-234.html
Extract everything , Copy all file & images into Adb Folder
Minimal ADB and Fastboot ---> https://forum.xda-developers.com/showthread.php?t=2317790
Commands
fastboot flash rpm rpm.mbn
fastboot flash rpmbak rpm.mbn
fastboot flash tz tz.mbn
fastboot flash tzbak tz.mbn
fastboot flash devcfg devcfg.mbn
fastboot flash devcfgbak devcfg.mbn
fastboot flash dsp adspso.bin
fastboot flash sec sec.dat
fastboot flash splash splash.img
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash cache cache.img
fastboot flash mdtp mdtp.img
fastboot flash lksecapp lksecapp.mbn
fastboot flash cmnlib cmnlib.mbn
fastboot flash cmnlibbak cmnlib.mbn
fastboot flash cmnlib64 cmnlib64.mbn
fastboot flash cmnlib64bak cmnlib64.mbn
fastboot flash keymaster keymaster.mbn
fastboot flash keymasterbak keymaster.mbn
fastboot flash cust cust.img
fastboot reboot
Copy to a text File and save as .bat
Copy bat file to adb folder
Now open bat now it will getting flash
Sit Back & Relax
In My case mi tool was not working so i did this to flash
Thank You .

Is this method working fine bro?
Sent from my Redmi Note 4X using Tapatalk

abees said:
Is this method working fine bro?
Sent from my Redmi Note 4X using Tapatalk
Click to expand...
Click to collapse
Works Fine NO Issues Bro Tested On Three Different as well Devices

bparihar said:
Works Fine NO Issues Bro Tested On Three Different as well Devices
Click to expand...
Click to collapse
Thanks a lot man.. for me too the miflashtool is not working
Sent from my Redmi Note 4X using Tapatalk

Cool bro Thnkz

i have only flash system recovery cache n boot files ..my device is working fine..is there any problem

[email protected] said:
i have only flash system recovery cache n boot files ..my device is working fine..is there any problem
Click to expand...
Click to collapse
[no problem but a fresh clean flash is a must (have a backup)]

The extracted images package already includes .bat and .sh files for different purposes, why create another one?
Just execute flash_all.bat or flash_all.sh are you're done.

in my case in part "fastboot flash system system.img" notification "error " cannot load system.img"
before bootloop I used ROM epic miui 10 .
now my MIDO stuck in logo MI and restart again adn again ..
help me please fix this error..

[ROM][October Update] [V9.6.15.0.ODIMIFE][Fastboot rom]

FASTBOOT firmware for MI A2 Android 8.1.0_V9.6.15.0.ODIMIFE
with the October security update
complete set for firmware and tools and boot patched by magisc patched_boot.img
checked by me flash_all_exept_data over the 14th beta
Invalid file format with a magic header - do not pay attention
flashing long time, about 20-30 minutes
Thanks to the 4PDA and XDA communities

I mean ... is the October fastboot rom ready to flash with miflash and comes with root?

rulezman said:
FASTBOOT firmware for MI A2 Android 8.1.0_V9.6.15.0.ODIMIFE
with the October security update
complete set for firmware and tools and boot patched by magisc patched_boot.img
checked by me flash_all_exept_data over the 14th beta
Invalid file format with a magic header - do not pay attention
flashing long time, about 20-30 minutes
Thanks to the 4PDA and XDA communities
Click to expand...
Click to collapse
Heard that there are two Oct updates, may I know if yours is the latest?

.15 is the second (latest) October update.

Guys, my phone is currently in august update (and I've unlocked and rooted the device with Magisk to enable camera api 2). What should I do to OTA successfully and safely? Thanks in advance!

Can't flash through miui flasher. Is it possible to flash this through recovery?

Are U tested?

I tested, it worked. Updated to Oct update thru fast boot.
There's a minor glitch - you have to remove the space of the folder name, otherwise windows cannot find correct folder location.

Xyam said:
I tested, it worked. Updated to Oct update thru fast boot.
There's a minor glitch - you have to remove the space of the folder name, otherwise windows cannot find correct folder location.
Click to expand...
Click to collapse
You mean remove space "_" ?
MI_A2_Android 8.1.0_V9.6.15.0.ODIMIFE_fastboot

Ind33d said:
You mean remove space "_" ?
MI_A2_Android 8.1.0_V9.6.15.0.ODIMIFE_fastboot
Click to expand...
Click to collapse
There is a space between "Android" and "8.1.0", the space must be removed or replaced by other characters.

Xyam said:
There is a space between "Android" and "8.1.0", the space must be removed or replaced by other characters.
Click to expand...
Click to collapse
MI_A2_Android8.1.0_V9.6.15.0.ODIMIFE_fastboot
Like this?

Ind33d said:
MI_A2_Android8.1.0_V9.6.15.0.ODIMIFE_fastboot
Like this?
Click to expand...
Click to collapse
Yup

i lost my wlan mac adress by flashing this, im flashing again now without without_data
anyone ever seen that problem?
nvm, the 3rd time it worked

9.6.16 is out can you provide fastboot archive?

hugopg said:
Guys, my phone is currently in august update (and I've unlocked and rooted the device with Magisk to enable camera api 2). What should I do to OTA successfully and safely? Thanks in advance!
Click to expand...
Click to collapse
I researched for such a long time on this, I'm exactly the same in your situation, rooted with magisk, camera2api substratum things like that on august patch.
Later on i figured myself a way to update without losing any data or wiping the phone which is :
1. download the full stock rom of august patch, it should be tgz files, extract it.
2. Make sure u got adb fastboot all the stuff installed on pc, and also mi a2 drivers.
3. On the phone, go to developer options and turn on usb debugging, guess u already done it since you rooted the phone.
4 now connect the phone to pc in fastboot mode.
5. After extract the tgz august stock rom, locate to folder "image".
6. Hold shift and right click open cmd or in my case open windows power shell.
7. Type fastboot devices to see if your phone is connected properly.
8. Paste these codes and hit enter.
9. After that the phone will be rebooted and after success booting go to settings > system update and start installing the ota without issues.
The codes :
fastboot flash bluetooth_a bluetooth.img
fastboot flash bluetooth_b bluetooth.img
fastboot flash devcfg_a devcfg.img
fastboot flash devcfg_b devcfg.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash xbl_a xbl.img
fastboot flash xbl_b xbl.img
fastboot flash pmic_a pmic.img
fastboot flash pmic_b pmic.img
fastboot flash rpm_a rpm.img
fastboot flash rpm_b rpm.img
fastboot flash tz_a tz.img
fastboot flash tz_b tz.img
fastboot flash hyp_a hyp.img
fastboot flash hyp_b hyp.img
fastboot flash keymaster_a keymaster.img
fastboot flash keymaster_b keymaster.img
fastboot flash cmnlib64_a cmnlib64.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash cmnlib_a cmnlib.img
fastboot flash cmnlib_b cmnlib.img
fastboot flash abl_a abl.elf
fastboot flash abl_b abl.elf
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash mdtp_a mdtp.img
fastboot flash mdtp_b mdtp.img
fastboot flash splash splash.img
fastboot flash mdtpsecapp_a mdtpsecapp.img
fastboot flash mdtpsecapp_b mdtpsecapp.img
fastboot flash storsec storsec.mbn
fastboot reboot
Guess that every patches on mi a2 will work with thus method, haven't tested with any version other than august patch. Let me know if it's work !

pani690 said:
Can't flash through miui flasher. Is it possible to flash this through recovery?
Click to expand...
Click to collapse
Search google for mi a2 manually flash firmware.
The result that said "techdroider.com" will be the answer you looking for.
If you don't want to lose any data but still wanna update, remove line "fastboot....userdata.img"

No November update?

Xyam said:
I tested, it worked. Updated to Oct update thru fast boot.
There's a minor glitch - you have to remove the space of the folder name, otherwise windows cannot find correct folder location.
Click to expand...
Click to collapse
Flie link not exist plz give working link