Database Users

Do you have the OTA problem? (LFW73W recovery)

Do you have the OTA problem? (LFW73W recovery)
Let's see the % of Nexus 9 errors.
Problem
There is one problem with a lots of Nexus 9 what failed to apply correctly the new OTA (LRX21Q).
The problem seems to be that the first Nexus 9 OTA (LRX21L) failed to update the Recovery partition of Nexus 9, maintained the old version (LFW73W).
The fix?
This OTA can't be applied! There are two solutions:
Waiting until Google releasing another OTA. OTA RELEASED LRX21R from LRX21L - http://android.clients.google.com/p...is-LRX21R-from-LRX21L-factory-recovery-ok.zip
Unlock the bootloader (Erasing all data) and apply the full LRX21Q Factory Image.
Other stuffs
How too Enter in the recovery mode?
Put your device into the bootloader menu by either the following command or by holding down the power button and the volume down button while your Nexus is turned off.
Now use the volume down button twice until you have scrolled to Recovery mode, and press the power button to select it. It will look like your Nexus is restarting itself but an image of an Android with a red exclamation mark over it will appear. Next hold down the power button and press the volume up button, and you will be in recovery mode.
See it here -> https://www.youtube.com/watch?v=DuuSTnbQSlM (from 2:10 until 4:31)
How too apply the new Factory Image
Unlock the bootloader (will erase all data)
Download the factory image. Extract the .tar.gz then extract the zip too. You will have a folder that has 5 .img filesnin it. Flash one at a time with fastboot.
PHP:
fastboot devices
fastboot flash bootloader bootloader-flounder-3.43.0.0114.img
fastboot flash radio <radio file name here>.img (If exists)
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash cache cache.img (erase cache; not needed)
fastboot flash userdata userdata.img (If exists, erase user data; not needed)
fastboot reboot

How check the recovery version ?

fblasot said:
How check the recovery version ?
Click to expand...
Click to collapse
Put your device into the bootloader menu by either the following command or by holding down the power button and the volume down button while your Nexus is turned off.
Now use the volume down button twice until you have scrolled to Recovery mode, and press the power button to select it. It will look like your Nexus is restarting itself but an image of an Android with a red exclamation mark over it will appear. Next hold down the power button and press the volume up button, and you will be in recovery mode.

i have the problem but im waiting for #2..

#3 solution. Download the factory image. Extract the .tar.gz then extract the zip too. You will have a folder that has 5 .img filesnin it. Flash one at a time with fastboot.
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash vendor vendor.img
Then :
fastboot reboot
This is what worked for me.

I'm having the exact problem.
Sent from my Nexus 9 using Tapatalk

Cuzz1369 said:
#3 solution. Download the factory image. Extract the .tar.gz then extract the zip too. You will have a folder that has 5 .img filesnin it. Flash one at a time with fastboot.
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash vendor vendor.img
Then :
fastboot reboot
This is what worked for me.
Click to expand...
Click to collapse
Don't work if you have the bootloader locked. So is the same was #1.

Cuzz1369 said:
#3 solution. Download the factory image. Extract the .tar.gz then extract the zip too. You will have a folder that has 5 .img filesnin it. Flash one at a time with fastboot.
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash vendor vendor.img
Then :
fastboot reboot
This is what worked for me.
Click to expand...
Click to collapse
Thx Cuzz1369, flashed (unlocked/relocked bootloader) like you mentioned works like a charm. Running LRX21Q now.
Don't forget to enable "OEM unlock" in developer options otherwise unlocking/locking bootloader doesn't work.
>sent from my lollipopped Nexus 9<

Cuzz1369 said:
#3 solution. Download the factory image. Extract the .tar.gz then extract the zip too. You will have a folder that has 5 .img filesnin it. Flash one at a time with fastboot.
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash vendor vendor.img
Then :
fastboot reboot
This is what worked for me.
Click to expand...
Click to collapse
Worked perfectly. Thanks!

marcomsousa said:
Don't work if you have the bootloader locked. So is the same was #1.
Click to expand...
Click to collapse
Obviously......... Sigh

Cuzz1369 said:
#3 solution. Download the factory image. Extract the .tar.gz then extract the zip too. You will have a folder that has 5 .img filesnin it. Flash one at a time with fastboot.
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash vendor vendor.img
Then :
fastboot reboot
This is what worked for me.
Click to expand...
Click to collapse
Thanks for sharing these steps and thanks to the TS for creating this thread.
Now, is there an idiots version to this? I have never manually updated / flashed any device before.
I understand I can just wait for the OTA, but now that I have a Nexus device I'd love to learn how to do this.
I have already downloaded and unzipped the LRX21Q Factory Image, installed Minimal ADB and Fastboot from here, and enabled OEM unlocking in the developer options. What should I do next?
Also, is my understanding correct in that my data will be erased and my device factory reset if I perform this manual update and that future OTA updates will still work if I choose not to manually update down the road?

I have a bit of a problem if i flash all the stock img files manually ( this is not my first nexus ) but after reboot i still get the recovery error ?

marcomsousa said:
Put your device into the bootloader menu by either the following command or by holding down the power button and the volume down button while your Nexus is turned off.
Now use the volume down button twice until you have scrolled to Recovery mode, and press the power button to select it. It will look like your Nexus is restarting itself but an image of an Android with a red exclamation mark over it will appear. Next hold down the power button and press the volume up button, and you will be in recovery mode.
Click to expand...
Click to collapse
Every time i try this part "Next hold down the power button and press the volume up button, and you will be in recovery mode." i bounce back to the bootloader menu ?

Hogyoku said:
Every time i try this part "Next hold down the power button and press the volume up button, and you will be in recovery mode." i bounce back to the bootloader menu ?
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=DuuSTnbQSlM
See from 2:10 until 4:31

marcomsousa said:
https://www.youtube.com/watch?v=DuuSTnbQSlM
See from 2:10 until 4:31
Click to expand...
Click to collapse
Thanks that did the trick !

livinginavacuum said:
Thanks for sharing these steps and thanks to the TS for creating this thread.
Now, is there an idiots version to this? I have never manually updated / flashed any device before.
I understand I can just wait for the OTA, but now that I have a Nexus device I'd love to learn how to do this.
I have already downloaded and unzipped the LRX21Q Factory Image, installed Minimal ADB and Fastboot from here, and enabled OEM unlocking in the developer options. What should I do next?
Also, is my understanding correct in that my data will be erased and my device factory reset if I perform this manual update and that future OTA updates will still work if I choose not to manually update down the road?
Click to expand...
Click to collapse
Go to the folder with fastboot and adb. Unzip everything in that folder.
Shift + right click in the folder and open command prompt.
Type "adb devices" to make sure your device shows up.
Then type in commands mentioned above

Also had this problem, and option #3 worked for me. Thanks!

No problem here, am on 21Q and the LFW73W recovery

I'm starting to think I'm the only person in the world who hasn't received the ota update. Am I?

Nope, I don't have it yet either.

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?

Official fastboot rom x829 & regular twrp rom

Only For X829 owners... 16s stock rom
https://mega.nz/#!ZG4G1YiS!FHW2u7EAwzVkXr1djEJlAaoZxa2AvjkZlakCRuLLmZw
https://drive.google.com/file/d/0B9KXxWUKQWYBaml4aEhFeFV5N2M/view
Extract zip file in adb on your c:/ directory.
Fastboot rom execute Chinese bat file in fastboot mode.
---Instructions---
How to flash it! First flash or boot twrp via fastboot. Do a clean wipes. Reboot into fastboot. Execute the chinese word bat file.
There will be a few error. Missing file. The zip provided was not complete. Missing stock recovery etc. Anyway, it work. For stock recovery here https://forum.xda-developers.com/le-max-2/development/official-lemax2x820x822-t3508823
After finishing youget fully working stock 5.8.16s LEX829.
Also these will change ur device info in fastboot to le_x2_na_oversea
More info >> https://forum.xda-developers.com/showpost.php?p=72708251&postcount=29
If you have problems with bat.. Put all rom files Inside tools file type on cmd as administrator one by one
It may some files missing inside rom... Don't worry
fastboot flash ddr ddr.mbn
fastboot flash dsp adspso.bin
fastboot flash boot boot.img
fastboot flash bluetooth BTFM.bin
fastboot flash cmnlib cmnlib.mbn
fastboot flash cmnlibbak cmnlib.mbn
fastboot flash cmnlib64 cmnlib64.mbn
fastboot flash cmnlib64bak cmnlib64.mbn
fastboot flash devcfg devcfg.mbn
fastboot flash devinfo devinfo.bin
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot flash hyp hyp.mbn
fastboot flash hypbak hyp.mbn
fastboot flash keymaster keymaster.mbn
fastboot flash keymasterbak keymaster.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash pmic pmic.elf
fastboot flash pmicbak pmic.elf
fastboot flash rpm rpm.mbn
fastboot flash rpmbak rpm.mbn
fastboot flash splash splash.img
fastboot flash system system.img
fastboot flash tz tz.mbn
fastboot flash tzbak tz.mbn
fastboot flash xbl xbl.elf
fastboot flash xblbak xbl.elf
fastboot reboot

Hey @CrisBalGreece
Could you give some more specification of the rom?

paxcolo said:
Hey @CrisBalGreece
Could you give some more specification of the rom?
Click to expand...
Click to collapse
Official 16s X829 fastboot rom from US officials forums.

Thank you for posting this man ?

im getting error zipfile is corrupt shuld i download again?
Ok I downloaded it again and it's saying zip file corrupted still

allrockedout said:
im getting error zipfile is corrupt shuld i download again?
Ok I downloaded it again and it's saying zip file corrupted still
Click to expand...
Click to collapse
Check your adb and drivers otherwise go manually one by one. Read OP info. Download it only through pc.

I just got my x829 with a shop rom that does not allow for OTA updates.
Is your stock rom the same one I have on my phone currently?

Please help I know it's not exactly related but I'm getting this in twrp now
I don't understand fastboot and CMD very well
This is to complicated i just want to flash its not working

Here's a log from twrp I'm still getting corrupt zip file error, when trying to flash official x829 zip ?
https://mega.nz/#!dFYVTBYY!NSzhFbQca87Em5XtnQ_-sCKf4FDFwWe0s3avpKkRjKo

Hi
I have x829 and now I'm on 19S indian. But this rom doesn't support polish language and I want back to original 16S from USA.
I do not have TWRP installed, can I rename the file to update.zip and move it to the root directory? Then install from recovery ?

ymmi21 said:
Hi
I have x829 and now I'm on 19S indian. But this rom doesn't support polish language and I want back to original 16S from USA.
I do not have TWRP installed, can I rename the file to update.zip and move it to the root directory? Then install from recovery ?
Click to expand...
Click to collapse
I haven't try that but you can still try it through fastboot commands.

CrisBalGreece said:
Only For X829 owners... 16s stock rom
If you don't know how to flash fastboot rom and make the above just flash this through TWRP
TWRP zip Flashable rom
https://mega.nz/#!ZG4G1YiS!FHW2u7EAwzVkXr1djEJlAaoZxa2AvjkZlakCRuLLmZw
Click to expand...
Click to collapse
I tried this file with renamed to update but after reboot and turn on it to normal recovery I received update field - file incorrect.
Something like that. But I pushed back button and then phone restart normally but on 19S.
Any idea ? How back to 16S without fastboot (now I'm at work) and TWRP ?

ymmi21 said:
I tried this file with renamed to update but after reboot and turn on it to normal recovery I received update field - file incorrect.
Something like that. But I pushed back button and then phone restart normally but on 19S.
Any idea ? How back to 16S without fastboot (now I'm at work) and TWRP ?
Click to expand...
Click to collapse
Yes I was afraid so. Try to contact with your seller or put TWRP and after installation put back the official recovery with the same Way.

Why on web I find only files for x822 and x820 ? Where is a department with the files of rom for USA version X829 ?

ymmi21 said:
Why on web I find only files for x822 and x820 ? Where is a department with the files of rom for USA version X829 ?
Click to expand...
Click to collapse
I don't know. You may ask to moderators to make new threads for x829.

allrockedout said:
Here's a log from twrp I'm still getting corrupt zip file error, when trying to flash official x829 zip
https://mega.nz/#!dFYVTBYY!NSzhFbQca87Em5XtnQ_-sCKf4FDFwWe0s3avpKkRjKo
Click to expand...
Click to collapse
This Logcat is from flashing and backing up Omni rom for max2. That you have or this is the one you try to wipe. Sorry I haven't understood....

Yes I know that I can write to moderators for new threads but for what ? I'm looking this rom on Leeco company site. Not here. (not exactly, this family of xda is big support )
Why do not they have it on their website ? I found only for Chinese and Indian versions, but not for USA (x829).
---------- Post added at 01:57 PM ---------- Previous post was at 01:55 PM ----------
CrisBalGreece said:
I don't know. You may ask to moderators to make new threads for x829.
Click to expand...
Click to collapse

ymmi21 said:
Yes I know that I can write to moderators for new threads but for what ? I'm looking this rom on Leeco company site. Not here.
Why do not they have it on their website ? I found only for Chinese and Indian versions, but not for USA (x829).
---------- Post added at 01:57 PM ---------- Previous post was at 01:55 PM ----------
Click to expand...
Click to collapse
I don't know why. All so given by my friends in Greece that they have it and flash to give it back to seller after fingerprint issues.

CrisBalGreece said:
Only For X829 owners... 16s stock rom
https://mega.nz/#!ZG4G1YiS!FHW2u7EAwzVkXr1djEJlAaoZxa2AvjkZlakCRuLLmZw
https://drive.google.com/file/d/0B9KXxWUKQWYBaml4aEhFeFV5N2M/view
Extract zip file in adb on your c:/ directory.
Fastboot rom execute bat file in fastboot mode.
If you have problems with bat.. Put all rom files Inside tools file type on cmd as administrator one by one
fastboot flash ddr ddr.mbn
fastboot flash dsp adspso.bin
fastboot flash boot boot.img
fastboot flash bluetooth BTFM.bin
fastboot flash cmnlib cmnlib.mbn
fastboot flash cmnlibbak cmnlib.mbn
fastboot flash cmnlib64 cmnlib64.mbn
fastboot flash cmnlib64bak cmnlib64.mbn
fastboot flash devcfg devcfg.mbn
fastboot flash devinfo devinfo.bin
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot flash hyp hyp.mbn
fastboot flash hypbak hyp.mbn
fastboot flash keymaster keymaster.mbn
fastboot flash keymasterbak keymaster.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash pmic pmic.elf
fastboot flash pmicbak pmic.elf
fastboot flash rpm rpm.mbn
fastboot flash rpmbak rpm.mbn
fastboot flash splash splash.img
fastboot flash system system.img
fastboot flash tz tz.mbn
fastboot flash tzbak tz.mbn
fastboot flash xbl xbl.elf
fastboot flash xblbak xbl.elf
fastboot reboot
If you don't know how to flash fastboot rom and make the above just flash this through TWRP
TWRP zip Flashable rom
https://mega.nz/#!ZG4G1YiS!FHW2u7EAwzVkXr1djEJlAaoZxa2AvjkZlakCRuLLmZw
Click to expand...
Click to collapse
Where you found this rom or it is yours ?
Which exactly bat file I have to open ?In file of first link I find 2 bat files, scripts.bat and some chinese signs.bat ?
File of last link (kind of like for twrp) is the same like file of first link ?
Where are differences ?

Rom 16s
CrisBalGreece said:
Check your adb and drivers otherwise go manually one by one. Read OP info. Download it only through pc.
Click to expand...
Click to collapse
1. Error when unzipping on file system.img !
2. Link to download firmware for TWRP the same as for flashing in FASTBOOT !!!
Please fix it, thanks in advance

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.

Twrp 3.2 not work on wileyfox storm kipper

Hello,
I try to install new ROM on my wileyfox storm.
I forgot to backup the old ROM.
When I flash recovery with Twrp 3.2.x (all versions on Android developer), the recovery doesn't reboot correctly.
My phone information :
FASTBOOT MODE
PRODUCT_NAME - KIPPER
VARIANT - QRE eMMC
BOOTLOADER VERSION - kipper-N-g6dffaf3
BASEBAND VERSION -
SERIAL NUMBER - xxxxxx
SECURE BOOT - enabled
DEVICE STATE - unlocked
I can install twrp 3.0.x, but with this version I can't install all the custom ROM and the installation of GAPPS fail and the twrp reboot without any error message.
Please help me.
Thanks
Thomas

tested TWRP :
88839c45b0a7d2bf6d64d458b59bc254 *TWRP-2.8.7.0-kipper-blue-recovery.img => recovery not launch
031da5da7e96c55cf6d6dd7c427f5c44 *TWRP-2.8.7.0-kipper-recovery.img => recovery not launch
5a7019c140308aff75946b38ceae055f *twrp-3.0.2-1-kipper.img => recovery OK
936495c6ec995e8b375ad414ef2e8674 *TWRP-3.0.3.0-kipper.img => recovery OK
0dcd6636fd71d85ecb497d9c21ff761a *TWRP-3.2.1-0.img => recovery not launch
cf037bbe6e4f0266ddf70fe5a68fd999 *twrp-3.2.1-0-kipper-20180110.img => recovery not launch
01a2a04bf5ce789d9a08bd737c7518b5 *TWRP-3.2.2-0-kipper.img => recovery not launch
TWRP 3.1.0-0.img => not found on web
TWRP 3.1.1-1.img => not found on web
TWRP3.1.1-0.img => not found on web
For Gapps :
936495c6ec995e8b375ad414ef2e8674 *TWRP-3.0.3.0-kipper.img => impossible to install GAPPS
5a7019c140308aff75946b38ceae055f *twrp-3.0.2-1-kipper.img => impossible to install GAPPS
Only one ROM can be installed :
AospExtended-v5.8-kipper-20180926-1028-UNOFFICIAL.zip => but without gapps, it's useless and the GPS doesn't work
:crying::crying:
Thomas

OK i try another method.
Download CM from this site : https://cyanogenupdatetracker.com/downloads/
3c8ad411f960acee450ee3644503650e *cm-13.1.2-ZNH2KAS3NA-kipper-signed-fastboot-1eb4b5e94b.zip
unzip and launch this command manually
Code:
fastboot flash aboot emmc_appsboot.mbn
fastboot erase DDR
fastboot flash sbl1 sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash hyp hyp.mbn
fastboot flash rpm 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 boot boot.img
fastboot reboot
Phone boot with the CM Recovery only

OK,
I tried to "apply update" with CM recovery and this file :
2a0d058f73d29a66be85d4b048a4562b *SW23-WF-KIPPER-CM-13.1.5-ZNH2KAS7EC-RECOVERY.zip
the phone boot and the gapps are already in the phone