[Recovery] Twrp 2.8.7.0 Kipper - Wileyfox Storm

I have build a twrp recovery for Wileyfox storm (kipper)
Enjoy it.
All credits go to TeamWin developpers.
flash with fastboot
fastboot flash recovery TWRP-2.8.7.0-kipper-recovery.img
TWRP-2.8.7.0-Kipper-brown-recovery
Edit:
TWRP-2.8.7.0-Kipper-blue-recovery

Nice job ;D

Awesome. It works flawlessly Is there any chance of any custom rom? maybe pure AOSP marshmallow with layers support? is the kipper source released?

I saw twrp 3.0.0.0 can you please compile it?

This works very well, backup, restore. Just one thing i just hope would be great to be there is the OTG drive support.

aciupapa said:
I saw twrp 3.0.0.0 can you please compile it?
Click to expand...
Click to collapse
What extra features does twrp3.0.0.0 have please? The current cm13 marshmallow nightly for wileyfox storm require the cm recovery to install the update zip.

You can able to update to every nightly even you're on TWRP 2.8.7.0 ( I've been using it since and been able to do nandroid backup for that matter, which you can't using CM recovery).
BTW TWRP main highlight is "•Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow"
If your using adopted storage on Android M, using TWRP 2.8.7.0 will not show the adopted SD card.
You can further check the released note from TWRP website for more info.

backfire_12 said:
You can able to update to every nightly even you're on TWRP 2.8.7.0 ( I've been using it since and been able to do nandroid backup for that matter, which you can't using CM recovery).
BTW TWRP main highlight is "•Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow"
If your using adopted storage on Android M, using TWRP 2.8.7.0 will not show the adopted SD card.
You can further check the released note from TWRP website for more info.
Click to expand...
Click to collapse
https://s.basketbuild.com/devs/beroid/Wileyfox%20Storm%20-%20Kipper/TWRP
Anyone tried TWRP_3.0.0-0_kipper recovery at all yet? I have the TWRP_3.0.1-0_crackling_20160402 recovery working fine on my Swift, however since my backups are from the TWRP 2.8.7.0 kipper recovery i have not tested the TWRP_3.0.0-0 version on my Storm!

On the 3.0.0 v2 touchscreen doesnt work for me

aciupapa said:
On the 3.0.0 v2 touchscreen doesnt work for me
Click to expand...
Click to collapse
I had a try at installing both test version 1 and 2 however the recovery loads yet none of the tile's responded after installation/ loading up completed.

hi i need video how do this recovery plz

Ok so I tried to install the given 2.8.7 version and it worked, but it always said 'wrong password' when trying to decrypt my phone. The same password worked when regularly booting the system. So I thought I might try a newer version and downloaded the _test.zip from the link provided in the thread. Unfortunately, now my phone seems to be bricked! It always boots into Recovery, which asks for my password but does not react to any input on the touchscreen. I can not boot the system or the bootloader, adb and fastboot do not find the device and if I hold the power button (or volume-down + power button) for several seconds it just again reboots into the broken recovery. Does anyone have an idea how to get out of this? Any help is greatly appreciated.
Edit: OK, now I feel dumb. The key combination to get into the bootloader is volume-up+power, not volume-down+power. Now I can continue to try different recoveries in the hope that one of them can decrypt the phone correctly and reacts to the touchscreen.

saikoa7a8a said:
hi i need video how do this recovery plz
Click to expand...
Click to collapse
If that's how you write, good luck breaking your phone... This thread has good instructions if you want to risk it, just replace the recovery image it has you download and use with this one.
http://forum.xda-developers.com/wileyfox-storm/general/root-wileyfox-storm-t3250992

Related

[RECOVERY] TWRP Recovery [v2.8.6.0]

CM dropped CWM support in CM-12.0 in favor of CM's own recovery, which has different bugs and is generally very simplified recovery (does only wiping/flashing images). So I decided to go on with a different recovery from now on.
This recovery is LVM compatible.
Requirements
U8800 with 404020 baseband (If you ever installed 2.3 stock firmware, you're ok!)
Strongly recommended: Unlocked pink screen
How to install
Method 1 (by recovery)
Download the zip from downloads below
Save it to your phone (internal or external SD)
Reboot to your current recovery
Install the zip
Reboot recovery
Method 2 (by pink screen)
Download the zip from downloads below
Save it to your PC
Reboot your phone in pink screen mode
Extract recovery.img from the zip
Save the zip on your phone's image/ directory (where boot.img and other files are located)
Reboot to recovery
Downloads
LegacyHuawei
twrp-recovery-v2840.zip
twrp-recovery-lvm-v2830.zip
Things to know
When backupping, tick "cust". This holds boot.img and other files which are grucial for restoring a full backup.
Thanks for the great job Blefish. It works flawlessly
Uploaded TWRP recovery v2.8.4.0.
Changes:
* Support for offmode charging
* LVM/NON-LVM compatible. You can use this recovery for NON-LVM ROMs.
Hi Blefish
Thanks for the updated recovery.
I had a question, if we were to flash say your CM11 rom, I guess we need to uninstall LVM as you had mentioned before or just flash directly using this recovery
Great job again
mohammad.nomaan said:
Hi Blefish
Thanks for the updated recovery.
I had a question, if we were to flash say your CM11 rom, do we need to uninstall LVM or just flash directly using this recovery
Great job again
Click to expand...
Click to collapse
You can use this recovery, however LVM needs to be uninstalled. The new BlePart-LVM-11 script makes it easier for you . However, I still want to do one mor CM11 release, with LVM support. Theoretically the new CM12 release is LVM/NON-LVM compatible too but it has problems on installing the ROM (the space on /system is not enough).
Blefish said:
You can use this recovery, however LVM needs to be uninstalled. The new BlePart-LVM-11 script makes it easier for you . However, I still want to do one mor CM11 release, with LVM support. Theoretically the new CM12 release is LVM/NON-LVM compatible too but it has problems on installing the ROM (the space on /system is not enough).
Click to expand...
Click to collapse
Thanks Blefish for the update.
Just installed the new recovery, Off-Mode charging is working fine.
I like the new white charging animation
Blefish, thanks a lot!!
Perhaps, in the next update, you could enable the LED to show the charging progress , if possible..
tsioy said:
Blefish, thanks a lot!!
Perhaps, in the next update, you could enable the LED to show the charging progress , if possible..
Click to expand...
Click to collapse
Yes, I am planning that. The thing was that in CM's healthd (charger is using that) it is supported, but in Omni's healthd it's not supported. I will probably implement it myself if someone has not done it yet.
VERY NICE, thanks!
New version uploaded, enjoy!
Next releases will be uploaded at LegacyHuawei
This version adds the RPC side charging (more stable) and it also enables charging led indicators.
I installed 2850 and now I can't access the sdcard (in TWRP). It works fine if I boot it normally, so I'm guessing it's not a problem with the sd card?
I tried the option to mount the sdcard, but when I try it, TWRP doesn't tick that option. All the others work, though (cust, system, data, ...)
Any suggestions?
phone wont boot into twrp now, it just shows the twrp splash screen then restarts
New version uploaded!
No changes have been done on my side, other than updating to android-5.1 codebase where this recovery is compiled from.
@Blefish On the U8800 Pro version it doesn't mount my external SD card. This has been a problem on many recoveries, but on twrp 2.8.1.0 by @Lihis it works. Can you find a way to make twrp 2.8.6.0 detect the SD Card? And BTW ADB Sideload does not work either, but works on 2.8.1.0
Webtag said:
@Blefish On the U8800 Pro version it doesn't mount my external SD card. This has been a problem on many recoveries, but on twrp 2.8.1.0 by @Lihis it works. Can you find a way to make twrp 2.8.6.0 detect the SD Card? And BTW ADB Sideload does not work either, but works on 2.8.1.0
Click to expand...
Click to collapse
Try replugging the SD card while in recovery. Sideload was working well for me, but it does require updated ADB. Does it tell you an error message on the screen?
Blefish said:
Try replugging the SD card while in recovery. Sideload was working well for me, but it does require updated ADB. Does it tell you an error message on the screen?
Click to expand...
Click to collapse
Replugging the SD does nothing, and I only get error message in Adb sideload mode after about 5-10 min. This is the same problem that @rexnanet had with version 2.8.4.0, but my sd doesn't mount after inserting it when in TWRP
Webtag said:
@Blefish On the U8800 Pro version it doesn't mount my external SD card. This has been a problem on many recoveries, but on twrp 2.8.1.0 by @Lihis it works. Can you find a way to make twrp 2.8.6.0 detect the SD Card? And BTW ADB Sideload does not work either, but works on 2.8.1.0
Click to expand...
Click to collapse
I've did some dirty edits in the recovery ramdisk and the SD Card can now be read and cm12.1 can be installed: http://www.mediafire.com/download/vzzc64h9zoh60h4/image-new.img
Hopefully Blefish will do a proper fix soon, though
CrysisLTU said:
I've did some dirty edits in the recovery ramdisk and the SD Card can now be read and cm12.1 can be installed: http://www.mediafire.com/download/vzzc64h9zoh60h4/image-new.img
Hopefully Blefish will do a proper fix soon, though
Click to expand...
Click to collapse
Hello CrysisLTU this imagen-new and Blepart-LVM, can used in U8800pro o U8800-51?
Links are gone. Pls someone upload the latest file to somewhere.

TWRP won't allow me to flash other roms

Hey I have this huge problem with TWRP. I wiped the usual files, and then tried to flash a rom. It said ERROR: failed to update binary zip or something like that. FYI, I installed Multi Boot and have two roms installed. I tried uninstalling the secondary rom and wiped the phone, but still no luck. I even used multiboot cleaner and it still says the samething. Help?
Which version of twrp is on the phone?
Use another recovery
use CWM its way better than TWRP!
wajid iqbal said:
use CWM its way better than TWRP!
Click to expand...
Click to collapse
Thats not true!
TWRP 2.8.7.0 is running perfectly till Android 6 roms and all!! TW-Roms,so use this!You can use Flashify to install.
cheers
audit13 said:
Which version of twrp is on the phone?
Click to expand...
Click to collapse
My Current recovery is TWRP 2.8.6.0
Use 2.8.7 version of twrp. Many ROMs need twrp.
audit13 said:
Use 2.8.7 version of twrp. Many ROMs need twrp.
Click to expand...
Click to collapse
how can i get it?
Wow...
I installed the new TWRP and it still doesn't work. This started to happened when I was creating a backup with my OTG then i canceled it, and did another backup in the internal storage of my phone.
You are using twrp 2.8.7?

[RECOVERY] Unofficial TWRP

This is an unofficial port of TWRP for the OnePlus 3
Downloads:
https://basketbuild.com/filedl/devs?dev=Grarak&dl=Grarak/oneplus3/recovery.img
Sources:
https://github.com/Grarak/android_device_oneplus_oneplus3
https://github.com/Grarak/android_kernel_oneplus_msm8996
Installation:
Download the recovery image and make sure your bootloader is unlocked
reboot into fastboot and execute
Code:
fastboot flash recovery recovery.img
Known issues:
Mouse pointer is hovering in the middle of the screen all the time, doesn't affect usability.
I am not sure if OTG works right now, last time I tried it didn't.
Everything else is working including decryption!
XDA:DevDB Information
TWRP OnePlus 3, Tool/Utility for the OnePlus 3
Contributors
Grarak
Version Information
Status: Beta
Created 2016-06-18
Last Updated 2016-06-18
hello, i have problems copying my old files to my new OP3 and i think it might have something to do with the encrypted storage on the new phone. (when i copy my files to the phone, the last modified date changes to the current date and i want to keep the correct timestamps)
how can i decrypt the data partition in twrp?
~MaX~ said:
hello, i have problems copying my old files to my new OP3 and i think it might have something to do with the encrypted storage on the new phone. (when i copy my files to the phone, the last modified date changes to the current date and i want to keep the correct timestamps)
how can i decrypt the data partition in twrp?
Click to expand...
Click to collapse
TWRP will either automatically decrypt your data or ask for your password.
OTG doesn't work.
How does this differ from the other twrp thread thats already posted?
This ones handles device encryption (which is on by default)
Therefore you can see/use internal storage
Vitriol_Drinker said:
This ones handles device encryption (which is on by default)
Therefore you can see/use internal storage
Click to expand...
Click to collapse
I can see and access my internal. Even made a stock backup.
Awesome! I hope OTG can be sorted soon Thanks for all your efforts Grarak
Sent from my ONE A2003 using Tapatalk
Awesome work man, now I'll get to enjoy Broken OS when I get my OP3.
fix-this! said:
I can see and access my internal. Even made a stock backup.
Click to expand...
Click to collapse
Can you upload the stock recovery somewhere?
If you did back it up, before installing TWRP?
Gesendet von meinem OnePlus One
jamesn2k said:
Awesome work man, now I'll get to enjoy Broken OS when I get my OP3.
Click to expand...
Click to collapse
Where did you see BrokenOs for OP3?? I'm very intrested! Thanks.
After flashing SuperSU in TWRP and doing a factory reset/wipe, how long should it take the OP3 to boot?
I feel like I've been stuck on the 1+ Powered by Android screen for far too long.
Grarak said:
This is an unofficial port of TWRP for the OnePlus 3
I have a problem with that recovery. Every time after I restore a backup I have made with that recovery my phone starts up and the unlock pattern is not valid anymore.
I have that now for the third time. Do you have a fix for that?
Edit: Fixed the pattern. But there is something wrong with that recovery. Please fix that
Click to expand...
Click to collapse
Planet X said:
I have a problem with that recovery. Every time after I restore a backup I have made with that recovery my phone starts up and the unlock pattern is not valid anymore.
I have that now for the third time. Do you have a fix for that?
Edit: Fixed the pattern. But there is something wrong with that recovery. Please fix that
Click to expand...
Click to collapse
i have the same issue^^ after restoring any rom, my pin / my pattern isn't valid anymore.
Planet X said:
I have a problem with that recovery. Every time after I restore a backup I have made with that recovery my phone starts up and the unlock pattern is not valid anymore.
I have that now for the third time. Do you have a fix for that?
Edit: Fixed the pattern. But there is something wrong with that recovery. Please fix that
Click to expand...
Click to collapse
From Nexus 6P guide - 4. How To Make A Nandroid Backup With TWRP Recovery:
Note: If you happened to forget to remove lockscreen security (PIN/Pattern/Fingerprint) before creating your backup, and you cannot get into your OS after restoring, you can do the following to fix the issue. Boot into TWRP and use the built in file manager to delete /data/sytem/locksettings.db. This should be enough to get you into your OS again. If it isn't you can also try deleting /data/system/locksettings.db-shm and /data/system/locksettings.db-wal. If this still doesn't fix your issue you can delete /data/system/gatekeeper.password.key and /data/system/gatekeeper.pattern.key.
Click to expand...
Click to collapse
I had to do it few times when I was restoring nandroid with pattern secured lock screen.
Natakranta said:
From Nexus 6P guide - 4. How To Make A Nandroid Backup With TWRP Recovery:
I had to do it few times when I was restoring nandroid with pattern secured lock screen.
Click to expand...
Click to collapse
That was what I had to do: delete /data/system/gatekeeper.pattern.key from Filmmanager. But still, that shouldn't be necessary.
why are there 3 different twrp threads? which one is recommended to use?
Did anybody try to
fastboot boot recovery.img
it?
It's not booting this way. I wanted to just boot it from PC and make a nandroid of all partitions including stock recovery.
i had the pattern issues too, luckily when i made the 1st initial back up of 3.1.0 i didn't have a key, b/c when i flashed 3.1.3 full zip xposed does not work, so i had restore my 3.1.0 nandroid and dirty flash the 3.1.3 after i installed xposed.
so in other words if u clean flash the 3.1.3 zip via TWRP i cannot get xposed to work
After updating to full OxygenOS 3.1.3 I can no longer flash this recovery does anyone have any suggestion ?
I try just like before but when I want to reboot into recovery from the OS it says "Factory device reset....rebooting"
And then it boots into OnePlus recovery
fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (17776 KB)...
OKAY [ 0.398s]
writing 'recovery'...
OKAY [ 0.136s]
finished. total time: 0.536s
Click to expand...
Click to collapse
---------- Post added at 23:12 ---------- Previous post was at 22:35 ----------
I was finally able to boot into recovery using "fastboot boot" and flash SuperSU like this but now I am still on stock recovery.
Good thing is that this way i hope to receive the next OTA so till then I will probably try and stay this way.

[GUIDE][How to][custom recovery] [custom rom][Redmi Note 3 SD]

I am not responsible for anything done wrong for you and your device. Sorry!!
You have two options to follow, the 1st one is long, may be difficult to follow. I recommend you to read option 1 and 2 both but to follow option 2
OPTION 1
Hello friend this is a short tutorial for those who have just bought the Beast Red Mi Note 3.
This guide is only for Redmi Note 3(Qualcomm Snapdragon 650 2GB/3GB version) users.
The Device's codename is kenzo. It also called Xiaomi Redmi Note 3 Pro. On MIUI sites Its also mentioned as HMNote3Pro so don't get confused.
The below mentioned MiFlash-Tool is required in emergency. Installing Mi-FlashTool in PC also install all the Quallcomm and Xiaomi Drivers to make your device function with PC at any mode( recovery, fastboot or system mode) Make sure before installing MiFlash-beta setup, You have disabled Driver Signature Enforcement in your Windows PC. To know how to disable check on Microsoft sites for your particular OS.
Requirements
1. A PC with windows 7,8,8.1 or 10 32-bit or 64-bit with .NET Framework version 3.5 installed. Before you install Mi Flash. To download .NET framwork visit the microsoft website.
2.Download Xiaomi MiFlash-Beta(This beta version works good and also support 32-bit Windows OS) http://en.miui.com/forum.php?mod=at...2NGJkfDE0ODE4MTQxMTh8MTU5MjAzMDUwMXwyODE5Nzk=
3.TWRP Recoveries- download all these 3 recoveries
a. Alka TWRP http://en.miui.com/forum.php?mod=at...xMmZifDE0ODE4MTY5NzZ8MTU5MjAzMDUwMXwyODI3NzM= (for emergency backup and restore) (this recovery is most necessary to backup all the partition of our device. RN3 comes with all about 40 partitions, and their are many important files stored their. So at anytime you get any problem just restore. The recovery image file is compressed in a .zip file. Therefore, you may need to firstly extract it using Winzip on your PC or extract it using ES File Explorer on your phone. One more thing, this build is for Redmi Note 3 Qualcomm Snapdragon (Kenzo).
b. Cofface TWRP https://drive.google.com/open?id=0B5bSNUUrjm6JQjFhUEkzZXZ2bkk (zip password www.cofface.com)
c. Official TWRP https://dl.twrp.me/kenzo
If you want to flash custom Rom like Cyanogenmod, xiaomi.eu, Resurrection Remix etc. This tutorial will help you to use all those thing which can be done on our Beast .
:angel: first of all you guys get the Bootloader unlocking permission from en.miui.com/unlock/ (recommended) and always sign in the Mi Account with valid mobile number and e-mail which is used by you currently and can be accessed by you anytime. Goto setting in the phone and register for Mi account and login. Enable Find Device feature.
i have not checked ZC-X TWRP RECOVERY because i have seen some people getting problem from zcx, but now it is upgraded. So it can be universal for everything( like flashing any official/stock/custom rom(as cofface and official do), maybe it supports all partition backup( like alka do) and also it can be used to update or upgrade you MIUI based rom. Check it at your own risk.
3.USB DATA cable (the one that came with your device).
4. device battery charged at least 50%.
5. A good observer and patient most of patient.
I don't think about any other way to unlock bootloader. You can find them on other places but I don't find them easy than this.
So I am supposing that you guys using your phone with stock MIUI Rom that should be MIUI 7 or MIUI 8 with stock recovery and You got the permisssion official to unlock your beast .
So just unlock the bootloader by using MiUnlock tool from PC. Store all these tools in your PC for future process.
Now you have unlocked bootloader to check the status just boot your phone into fastboot mode by pressing volume down+power key when your device is off then use this fastboot command fastboot oem device-info to check the bootloader info if it says bootloader unlocked:true then you are ready to go. If you don't know how to setup adb-fastboot environment and driver check it here http://forum.xda-developers.com/showthread.php?t=2588979
Put unlocked bootloader phone in fastboot mode,connect device to PC using USB cable and check the bootloader status again to verify it is unlocked or not by using command fastboot oem device-info. Now copy(don't cut because you should have a backup plan for each process) all the recoveries ALKA TWRP, CoffaceTWRP and official TWRP recovery to the adb fastboot folder and rename alka twrp to alka.img,cofface twrp to cofface.img and official twrp to official.img. Please copy and rename one by one for don't getting confused. If you accidently rename cofface to alka then it will be not good to you after flashing. So take each step carefully.
(if you have managed environment variables on PC then you can use adb fastboot commands any where in PC, That is a good idea. So if you want to know how to set environment variables just comment here I will give you all the steps.)
Now just press continuously the Shift key and press RIGHT CLICK on the blank area of window.
An option menu will be showed click on open command prompt here.
A black backgrounded command shell will be opened.
Now type fastboot oem device-info and press enter key.
If it shows bootloader unlocked :true then proceed to the step 1 and if shows false then don't proceed unlock your bootloader which is shown above with this symbol :angel:.
Step 1:
A.First of all take backup of internal sd by copying all the folder and files in your PC's folder and name this folder to KenzoInternal you can use any name. And delete more files in internal to get atleast 5GB space.
B.You shuould have atleast 5GB space in your internel to back up your all device partition through ALKA TWRP.
C. copy all three recoverys(cofface.img,official.img and alka.img) in your phone's Internal SD directly or make a folder recovery and place there.
Now go,read and follow the instruction from below
Boot your phone in fastboot mode and connect with PC
open command prompt in adb-fastboot folder where you have copied all the recovery images(official.img,cofface.img and alka.img)
Type on command prompt:
fastboot flash recovery alka.img
it will be flased in atleast 10 seconds.
Now we have to go directly to recovery mode from fastboot mode not in system so care fully press volume up + power key at the same time in your REDMI NOTE 3 and when your device vibrate leave the power key but don't leave the volume up key until the recovery window get shown. If your device get booted to system not in recovery then maybe your flashed 'alka' will be replaced with stock recovery, and may be it get bootloop or maybe it will boot successfully but have some problems like Wi-Fi radio get disabled.
Read the above step again and do everything carefully.
Step 2:
[[ If on welcome screen the language shows in chinese or other, then simply swipe on first screen and touch on the 2nd column and 3rd row in menu and then touch on the icon(shows like earth or sphere) and choose English and then done. ]]
In recovery go to BACKUP and mark all the partition I said all the partitions (you can leave unmarked the DATA partition if you are not wanting to make backup of your own installed applications and their data. It will decrease the backup size and also the TIME) their may be 35+ partitions. And swipe to backup. Their are some partitions like system,efs(stores modem and radio and may be your IMEI information) etc have the sensitive data. So you are mostly recommended to mark all the partition except DATA(optional).
GREAT!!! wait until getting backup.
Step 3:
Now touch on Install menu in recovery and touch on Install Image that is always in the right below of the screen upto the swipe handle.
Now browse to the root of internal sd or the folder where you have copied all the recovery images(cofface.img,alka.img and official.img). And choose the cofface.img and swipe to install.
Now get back by touching on back arrow symbol on left bottom.
Step 4:
Touch on REBOOT menu in recovery and then touch on Reboot to recovery or to recovery.
Your RN3 will reboot again to recovery(which is now cofface).
[[ If on welcome the language shows in chinese or other then simply swipe on first screen and touch on the 2nd column and 3rd row in menu and then touch on the icon(shows like earth or sphere) and choose english and then done. ]]
Now touch on reboot and thenreboot to system.
If it shows that your recovery will be
If any query shows saying your phone is not rooted just touch on Do not Install
your phone will boot to MIUI system as it was. and it has a custom recovery(currently cofface).
if you want to root your device then download superSu.zip from https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip and place it in your internal sd card of phone and then boot to recovery by pressing power key+volume up key on same time then go to install and choose to install for supersu_vx.xx.zip file and swipe to flash. Then get back and wipe cache and dalvik/ART cache or some times it also reboots automatically.
Kindly follow the on-screen instruction which shows on screen during installation.
NOTE: It may be bootloop or take too much time on first boot after installing superSu.
SuperSU app and all the applets(including busybox tools) also comes with superSU zip file. So no need to install it through PlayStore. However you can update from PlayStore.
You are strongly recommended to take the backup(whole partition backup taken by ALKA TWRP) and copy it to Your PC that is the life of your mobile. I know you can flash An official MIUI rom through PC using fastboot or EDL method but If you lost your EFS partition then You will lost your IMEI which is unique to each and every devices. In Qualcomm Snapdragon based phone It is hard to recover IMEI. I say hard not impossible. Their are many forum that give solution to this but It is highly recommended to have this backup copy to your PC. You can find your backup in the /sdcard/TWRP/Backup/ OR open Internal SD then go to TWRP folder then open BACKUP and then a folder like 5exxxye. just copy this folder to your PC and keep it safe or you can save it to other places also that will be more good and also show your smartness.
How to install custom ROM or OSs in RN3Snapdragon?? Hmm come here
NOTE: Always flash all custom ROM(Except MIUI) through official TWRP. But when you have made your mood to install custom ROM you have to flash official twrp through either with TWRP(currently cofface in your device) or with fastboot command using same method that I have explained above when we have flashed coffaceTWRP in your device or use this commandfastboot flash recovery official.img
I have tested many ROMs but I found most stable Resuurection Remix(based on Marshmallow) and CyanogenMod 13(based on Marshmallow) yet. Everything is working fine except VoLTE. Their are many available ROms that supports VoLTE based on Nougat(Android 7.0 or 7.1) but have some bugs with camera. (The Cyanogenmod 14.1 officially is also declared but in experimental mode(nightly)(not recommended for you.))
I am going to show you the steps to flash custom ROMs without getting into any problem but you are recommended to follow each steps carefully. Thanks
Suppose you have downloaded official released Cyanogenmod 13 for your phone from here https://download.cyanogenmod.org/get/jenkins/174586/cm-13.0-20160816-SNAPSHOT-ZNH5YAO0FI-kenzo.zip (It is recommended to download it to your PC for backup plan). Having a copy of this backup in your PC makes you free to delete it from internal SD to free the space when you are in a Stable Rom or in a ROM you loved and want to be always with it.
then place it to your internal SD. now follow these steps... Check out your device battery is 50+ % charged.
Step 1:
Reboot to recovery. Go to install and choose install image. Now choose official.img(officialTWRP) and then swipe to flash/install it.
Step 2:
Now reboot again to recovery by choosing REBOOT in recovery menu and then RECOVERY
your phone will be rebooted to official TWRP recovery which is not supported by MIUI. I mean official recovery doesn't have the ability to patch the boot image., that is why I said it is not supported.
Step 3:
Now go to wipe/format menu in TWRP recovery(I am supposing you have the back up with alka twrp before and have copied it to your PC also.). Choose 'advanced wipe' and Mark these partition System,Data,Cache,Dalvik/ART cache. Do not choose Internal SD, Micro SD or USB OTG. and swipe to wipe.
Step 4:
After wiping now you have not any Operating System installed. Just touch INSTALL in RECOVERY MENU and choose the ROM ZIP file which is cm-13.0-20160816-SNAPSHOT-ZNH5YAO0FI-kenzo.zip (for example). Always use the ROM that is build for Your Device. Since above zip file's name shows it is for kenzo that is your RedmiNote3 Quallcomm Snapdragon.(just check the underlined word in zip file.)
and swipe to flash and wait no matter how much time it takes. Just wait don't try to reboot.
if you want to flash google apps(GApps) like play store and play store services you have to install it also after flashing the ROM zip file. to download GoogleApps go to opengapps.org and choose arm64 from architecture menu and choose android version for this ROM(Cyanogenmod 13) choose 6.0. choose which package you want I recommend you to use pico it will only install play store and services and you can also install other google apps through Play Store later.
If you want all google apps then choose 'aroma' it has a built-in file explorer to choose particular app in recovery.
Step 5:
After installing cyanogenmod and GApps wipe cache and Dalvik/ART cache again. Do not wipe anything else.
Now its time to reboot to the system.
first time it will take atleast 2 to 10 mins (depends on the open GApps package type) for optimization of apps.
After that go and enjoy..
Any problem comment below.
To revert back to MIUI again.
just copy the backup folder you have taken before, to the folder /sdcard/TWRP/BACKUP/ and reboot to recovery(currently official).
and choose to install image in recovery menu and then choose alka.img and then reboot to recovery again(using recovery menu).
You will again reboot to recovery (currently ALKA).
In alka recovery menu choose to WIPE and wipe these partition SYSTEM,DATA,CACHE,DALVIK/ART CACHE.
then choose RESTORE from recovery menu and select your backup folder and it will show the list of all the partition you have made backup. Mark all and swipe to restore.
Note:sometimes it shows an error during restore that it can't restore firmware partition. If it show this error kindly choose to restore again and mark all partition except firmware partition then swipe to restore.
After restoring backup(MIUI) do not reboot just. choose to install image and install cofface.img again because this recovery works with MIUI.(Cofface twrp paches boot image automatically which is required to make custom recoveries to work with MIUI ROMs ) after installing cofface.img. Reboot to recovery again and then reboot to system.
Now wait if it takes too much time (may be 15 to 20 mins).
Now you are come back to your MIUI ROM.
MUST READ:
1.Always check your bootloader status after and before flashing any ROMs(boot to fastboot mode connect USB to PC and type the command in command window fastboot oem device-info.
2.If any time it shows bootloader unlocked: false then use Mi Unlock tool to unlock the bootloader again. You have to use same user-name/mobile number/e-mail and password to sign-in the UnlockTool which you have sihned in your phone.
3.No matter how many ROM you have flashed or which OS you currently using. MiUnlock-tools always recognises your phone.
4. During unlocking the phone your PC must have an internet connection from other sources.
5.You can't use your phone's wi-fi hotspot to unlock its bootloader because it should be in fastboot mode.
6.Always make back up and store them in safe place.
Credit
to the respective developer,manufacturer.
OPTION 2
Now you can use zcx recovery which is Universal to flash custom/stock/miui ROM without any problem. So unlock your bootloader and flash ZC-X twrp recovery, and follow the instruction comes with it, you don't need to follow the long procedure given above. You should use it with Marshmallow based MIUI ROM too which comes with by default DATA partition encryption. It can automatically decrypt DATA partition. So go for it here https://www.google.co.in/url?sa=t&r...DwoAzQEtfzPxp4Shw&sig2=SOZcDMBpgO_teBIK6lNnhw
Thanks any problem comment below. Enjoy
can't i use zc-x rom ? for all purpose ?
You can.. but must use alka twrp for backup and restore
jangid said:
can't i use zc-x rom ? for all purpose ?
Click to expand...
Click to collapse
What do you mean by zc-x rom? If you want to say zcx recovery then yes You can.. but must use alka twrp for backup and restore always
If i want to flash custom MiUi rom like miui.eu or epic miui ROM, should I use cofface recovery or official twrp ?
Sent from my Redmi Note 3 using XDA-Developers mobile app
This tut has been pretty clear but I have a typical doubt! If I unlock my phone using mi flash tool by using the miui7.1.8 fastboot rom and flash twrp and if I later how do I update my miui? If I would be able to update it in some way doesent the bootloader get locked again? If it gets locked and I need to downgrade to older miui version! Pls help!
If I use offical twrp and take my unrooted miui backup and flashed cm14.1 and then latter restore my unrooted miui i wouldn't work?
---------- Post added at 05:58 AM ---------- Previous post was at 05:57 AM ----------
Also we can't flash cm14.1 rom using any other recoveries like Alka zcx coaffe ?
gaurav1322 said:
What do you mean by zc-x rom? If you want to say zcx recovery then yes You can.. but must use alka twrp for backup and restore always
Click to expand...
Click to collapse
Seriously dude , zcx supports all partition backup like alka twrp+6.0 encryption problem is also solved ,inbuilt boot image patcher + miui ota support
This guide just made procedure to flash ROMs more hectic and uneasy and long process.
I Recommend user to just flash zcx twrp and do all the stuff you want,flash any roms including miui.
NVDX11 said:
Seriously dude , zcx supports all partition backup like alka twrp+6.0 encryption problem is also solved ,inbuilt boot image patcher + miui ota support
This guide just made procedure to flash ROMs more hectic and uneasy and long process.
I Recommend user to just flash zcx twrp and do all the stuff you want,flash any roms including miui.
Click to expand...
Click to collapse
Can i restore miui backup after flashing cm14.1 in zcx recovery ?
a.broken.star said:
If i want to flash custom MiUi rom like miui.eu or epic miui ROM, should I use cofface recovery or official twrp ?
Sent from my Redmi Note 3 using XDA-Developers mobile app
Click to expand...
Click to collapse
Then must use cofface because MIUI based custom rom like
Xiaomi.eu etc. Are also need boot image patching..but 1st
Take full nandroid backup through alka and copy it to pc
Before flashing it. After flashing MIUI based custom rom use
Check your bootloader status because some of them locks your Bootloader again..
ckflash09 said:
This tut has been pretty clear but I have a typical doubt! If I unlock my phone using mi flash tool by using the miui7.1.8 fastboot rom and flash twrp and if I later how do I update my miui? If I would be able to update it in some way doesent the bootloader get locked again? If it gets locked and I need to downgrade to older miui version! Pls help!
Click to expand...
Click to collapse
1st of all the bootloader status(lock/unlock) get changed
From rom to rom. So everytime if you wanna flash something
Like any rom(official/stock/custom) or any recovery you need to check your bootloader status 1st. I have told in post that if u wanna flash Miui rom or wanna update it,just flash through cofface recovery. And one thing to remember, never downgrade miui version through cofface (for example Miui8 to miui7). But if u want to upgrade(for ex. Miui7 to miui8) or want to update(ex.- miui 8.0.1 to miui 8.1.1 or something like this) then you can use cofface twrp recovery and also zcx twrp recovery. Before flashing make sure you have full backup through alka twrp. You should read the post again.
vikasb32 said:
If I use offical twrp and take my unrooted miui backup and flashed cm14.1 and then latter restore my unrooted miui i wouldn't work?
---------- Post added at 05:58 AM ---------- Previous post was at 05:57 AM ----------
Also we can't flash cm14.1 rom using any other recoveries like Alka zcx coaffe ?
Click to expand...
Click to collapse
It will work if your miui backup from official twrp contains backup of firmware partition. Since official twrp doesn't supports all partition backup. So you need to flash a miui based fastboot rom then unlock bootloader again if it get locked and then flash alka to take all partition backup then save this backup to pc. And after that check the post again for what you want.
vikasb32 said:
Can i restore miui backup after flashing cm14.1 in zcx recovery ?
Click to expand...
Click to collapse
Yep sure! No prob.
NVDX11 said:
Seriously dude , zcx supports all partition backup like alka twrp+6.0 encryption problem is also solved ,inbuilt boot image patcher + miui ota support
This guide just made procedure to flash ROMs more hectic and uneasy and long process.
I Recommend user to just flash zcx twrp and do all the stuff you want,flash any roms including miui.
Click to expand...
Click to collapse
you are right but zcx doesn't support all about 40 partitions. Maybe it comes with all features that we get in all other twrp recoveries like cofface,alka etc. but for whole partitions backup alka is necessary.
But it is true that ZCX supports important partitions that are more important while ALKA twrp supports whole with important and not important
This post is not so long or uneasy. It is for noobies to understand. This is not for PROs. Thank you!
gaurav1322 said:
you are right but zcx doesn't support all about 40 partitions. Maybe it comes with all features that we get in all other twrp recoveries like cofface,alka etc. but for whole partitions backup alka is necessary.
Click to expand...
Click to collapse
Zcx supports all partitions backup,i am using it for long time,never faced a single prob and i am not shooting arrows in dark bruh,i have tested and its my experience,if you dont believe try it by urself.
But just dont post like it doesnt support partition backup like alka.
NVDX11 said:
Zcx supports all partitions backup,i am using it for long time,never faced a single prob and i am not shooting arrows in dark bruh,i have tested and its my experience,if you dont believe try it by urself.
But just dont post like it doesnt support partition backup like alka.
Click to expand...
Click to collapse
okk bro I am wrong. I am also using it and thanks for the info. I will add it in the tutorial. Thanks
No problem bro, i know you have made guide for new comers( i wont call them noobies) & it's a good one.
But i am just in favor of "if we can do things on easiest way,no need to choose harder ones"
I will try to suggest if some steps need to be included and what other things which we can short doing the flashing procedures.
NVDX11 said:
No problem bro, i know you have made guide for new comers( i wont call them noobies) & it's a good one.
But i am just in favor of "if we can do things on easiest way,no need to choose harder ones"
I will try to suggest if some steps need to be included and what other things which we can short doing the flashing procedures.
Click to expand...
Click to collapse
Thats the good idea bro actually i haven't any knowledge about zcx recovery till the post was submitted. And I have seen somewhere that it comes with few bugs but I think now it gets updated.
Now I am going to re-post the tutorial by editing it and at last thank you so much..
Flashed miui globle dev rom in unofficially unlocked bootloader
even flashed lazy flasher script
disabled dm verify
yet bootloader got locked
now how to flash rom without loosing data
Trustzone error 7
Hello,
currently i am on MIUI 8.2 and when i try to flash any custom ROM based on android N like Lineage OS or Resurrection Remix ROM using official TWRP, I always get trustzone error 7 with following messege:
Checking for TZ version TZ.BF.4.0.1-77307
assert failed: xiaomi.verify_trustzone("TZ.BF.4.0.1-77307") == "1"
Updater process ended with ERROR: 7
which prevents me to flash any of the ROMs. Please help me out....

A2017G V1.2 0B09 - Cannot install ROMs without Gapps

My phone is bootloader unlocked & rooted + TWRP but still using the original Nougat firmware from ZTE. Now, for some unexplained reason I cannot install any custom ROM that does NOT have Gapps incuded, like Resurrection Remix or similar slim ROMs without Gapps. TWRP just gives the usual can't install error.
Moreover, even if I install a ROm with Gapps successfully I cannot go past the 'Google verifying account' (have to wait for 24 hours) nonsense.
Any advise appreciated.
xectis said:
My phone is bootloader unlocked & rooted + TWRP but still using the original Nougat firmware from ZTE. Now, for some unexplained reason I cannot install any custom ROM that does NOT have Gapps incuded, like Resurrection Remix or similar slim ROMs without Gapps. TWRP just gives the usual can't install error.
Moreover, even if I install a ROm with Gapps successfully I cannot go past the 'Google verifying account' (have to wait for 24 hours) nonsense.
Any advise appreciated.
Click to expand...
Click to collapse
What's your TWRP version?
I guess you are installing the Universal Bootloader, right? Do you install a newer TWRP img after that?
Which are the ROMs that fail?
What's the failure error?
Have you ever formatted data? What's its filesystem?
Choose an username... said:
What's your TWRP version?
I guess you are installing the Universal Bootloader, right? Do you install a newer TWRP img after that?
Which are the ROMs that fail?
What's the failure error?
Have you ever formatted data? What's its filesystem?
Click to expand...
Click to collapse
Thanks for the response. I used Axon7 Toolkit for all actions, including boot unlocking (no idea which version Axon Toolkit installed). It also installed TWRP 3.1.1.0 alisa which I've had all the time.
The ROMs that failed were 'XenonHD-170609-Unofficial.zip' and 'Resurrection Remix' (RR-N-v5.8.5-20171108-axon7-Official.zip). Also I installed successfully 'A2017G(N-B06)_AROMA_SL!M2+DF!NR_by_raystef66.zip' which has Gapps included....but the problem was that I could not get past the google account verification, even though I know my google details. It says I had to wait 24 hours before signing in.
The failure error from XenonHD and Resurrection Remix ROMs was: Updater process ended with error: 7
Yes I formatted data each time I installed a ROM.
I don't know how to find out what the file system is.
xectis said:
Thanks for the response. I used Axon7 Toolkit for all actions, including boot unlocking (no idea which version Axon Toolkit installed). It also installed TWRP 3.1.1.0 alisa which I've had all the time.
The ROMs that failed were 'XenonHD-170609-Unofficial.zip' and 'Resurrection Remix' (RR-N-v5.8.5-20171108-axon7-Official.zip). Also I installed successfully 'A2017G(N-B06)_AROMA_SL!M2+DF!NR_by_raystef66.zip' which has Gapps included....but the problem was that I could not get past the google account verification, even though I know my google details. It says I had to wait 24 hours before signing in.
The failure error from XenonHD and Resurrection Remix ROMs was: Updater process ended with error: 7
Yes I formatted data each time I installed a ROM.
I don't know how to find out what the file system is.
Click to expand...
Click to collapse
I believe you forgot to flash the Universal Bootloader. That's an error on your end.
Basically, what the Universal Bootloader does is change your device's info to something 'universal' (it somewhat standardizes A2017s, A2017Us and A2017Gs into an intermediate so that you can flash any custom ROM on any of the 3). It also installs TWRP 3.0.2-N or sth like that. So basically you need to have TWRP-3.1.1-0.img on your phone, then flash the Universal Bootloader, then the modem for your device (get the latest from Raystef66's download center), then the ROM and whatever ZIPs you want to install (ALWAYS install SuperSU or Magisk or you'll get the internal storage encrypted and you'll have to format the internal storage every time you want to change ROM), and lastly Install Image - the TWRP.img - install to recovery partition.
You can get the Universal Bootloader from the LOS thread. There are also modem files for the 3 models but they are rather old, so just get the B09 modem from the download center
Choose an username... said:
I believe you forgot to flash the Universal Bootloader. That's an error on your end.
Basically, what the Universal Bootloader does is change your device's info to something 'universal' (it somewhat standardizes A2017s, A2017Us and A2017Gs into an intermediate so that you can flash any custom ROM on any of the 3). It also installs TWRP 3.0.2-N or sth like that. So basically you need to have TWRP-3.1.1-0.img on your phone, then flash the Universal Bootloader, then the modem for your device (get the latest from Raystef66's download center), then the ROM and whatever ZIPs you want to install (ALWAYS install SuperSU or Magisk or you'll get the internal storage encrypted and you'll have to format the internal storage every time you want to change ROM), and lastly Install Image - the TWRP.img - install to recovery partition.
You can get the Universal Bootloader from the LOS thread. There are also modem files for the 3 models but they are rather old, so just get the B09 modem from the download center
Click to expand...
Click to collapse
Thanks for your help and your suggestions. Will try a few things as I go along. Thanks again.
xectis said:
Thanks for your help and your suggestions. Will try a few things as I go along. Thanks again.
Click to expand...
Click to collapse
Just two things, you mentioned "and lastly Install Image - the TWRP.img - install to recovery partition". I already have TWRP 3.1.1.0 installed so did you mean to install it again after flashing the Universal Bootloader and modem?
Also, is this the correct link for the LOS thread you mentioned: https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547
xectis said:
Just two things, you mentioned "and lastly Install Image - the TWRP.img - install to recovery partition". I already have TWRP 3.1.1.0 installed so did you mean to install it again after flashing the Universal Bootloader and modem?
Also, is this the correct link for the LOS thread you mentioned: https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547
Click to expand...
Click to collapse
Yes and no
The Universal bootloader flashes an old TWRP version. After you reboot and enter the recovery again you will get an old TWRP. So to avoid this you have to flash the Universal Bootloader and then TWRP 3.1.1 or 3.2.1
That's the download center... I mean the LineageOS thread over at the ROMs section. By Unjustified Dev
Choose an username... said:
Yes and no
The Universal bootloader flashes an old TWRP version. After you reboot and enter the recovery again you will get an old TWRP. So to avoid this you have to flash the Universal Bootloader and then TWRP 3.1.1 or 3.2.1
That's the download center... I mean the LineageOS thread over at the ROMs section. By Unjustified Dev
Click to expand...
Click to collapse
I see. All clear now. You've been most helpful, thank you again.
[/QUOTE]
xectis said:
I see. All clear now. You've been most helpful, thank you again.
Click to expand...
Click to collapse
Hi again, almost everything worked as per your suggestions except installing ROMs without Gapps as mentioned previously such as Resurrection Remix. I get the dreaded 'To Start Android, Enter Password' notice (pic attached). Even after putting a random password it comes up with 'The password you entered is correct, but unfortunately your data is corrupt'. I did a factory reset but no joy. So it looks like I have to install Gapps also?. By the way my device is not encrypted.
On a different note, do you know of a link that has a mod for increasing the volume in the ear speaker so I can hear callers with a louder volume.
Hi again, almost everything worked as per your suggestions except installing ROMs without Gapps as mentioned previously such as Resurrection Remix. I get the dreaded 'To Start Android, Enter Password' notice (pic attached). Even after putting a random password it comes up with 'The password you entered is correct, but unfortunately your data is corrupt'. I did a factory reset but no joy. So it looks like I have to install Gapps also?. By the way my device is not encrypted.
On a different note, do you know of a link that has a mod for increasing the volume in the ear speaker so I can hear callers with a louder volume.[/QUOTE]
You have to format the internal storage, because it is encrypted. Do this:
You need to have Magisk 15.1 or 14 or SuperSU 2.79 ready. I recommend the latest Magisk. If you have an SD card, put it there. If not, leave it on your PC and have the phone connected.
Go to TWRP, Wipe, Advanced Wipe, Format data. Be sure that it formats as ext4 (it will say 'formating using make-ext4fs or something, if it says f2fs then leave it format and then use Change filesystem to ext4).
Right after that, install Magisk. If you have the SD card it's easy, if you don't, try to connect the phone to the PC, if it appears as a mass storage option then put it there and flash it with Install. If it doesn't appear as mass storage use adb sideload
NEVER leave the phone without SuperSU or Magisk! If you change the ROM, ALWAYS install Magisk or SuperSU right after you install the ROM. Otherwise you'll have to format the internal storage again the next time you change the ROM.
Choose an username... said:
Hi again, almost everything worked as per your suggestions except installing ROMs without Gapps as mentioned previously such as Resurrection Remix. I get the dreaded 'To Start Android, Enter Password' notice (pic attached). Even after putting a random password it comes up with 'The password you entered is correct, but unfortunately your data is corrupt'. I did a factory reset but no joy. So it looks like I have to install Gapps also?. By the way my device is not encrypted.
On a different note, do you know of a link that has a mod for increasing the volume in the ear speaker so I can hear callers with a louder volume.
Click to expand...
Click to collapse
You have to format the internal storage, because it is encrypted. Do this:
You need to have Magisk 15.1 or 14 or SuperSU 2.79 ready. I recommend the latest Magisk. If you have an SD card, put it there. If not, leave it on your PC and have the phone connected.
Go to TWRP, Wipe, Advanced Wipe, Format data. Be sure that it formats as ext4 (it will say 'formating using make-ext4fs or something, if it says f2fs then leave it format and then use Change filesystem to ext4).
Right after that, install Magisk. If you have the SD card it's easy, if you don't, try to connect the phone to the PC, if it appears as a mass storage option then put it there and flash it with Install. If it doesn't appear as mass storage use adb sideload
NEVER leave the phone without SuperSU or Magisk! If you change the ROM, ALWAYS install Magisk or SuperSU right after you install the ROM. Otherwise you'll have to format the internal storage again the next time you change the ROM.[/QUOTE]
I did everything you suggested but I still get the 'To start Android use your password'. No wories I'll go back to my old ROM. Thanks anyway.
***Update*** I made a mistake in formatting SYSTEM instead of DATA. Now it works fine installing the ROM's I mentioned. You are a champ!
Now all I need is to somehow find a way to raise the in-call volume (ear speaker).
xectis said:
Now all I need is to somehow find a way to raise the in-call volume (ear speaker).
Click to expand...
Click to collapse
Try this
https://forum.xda-developers.com/axon-7/how-to/patch-enable-ak4490-hifi-dac-custom-rom-t3707738
It'll probably not work but you'll end up with the AK4490 anyways
Choose an username... said:
Try this
https://forum.xda-developers.com/axon-7/how-to/patch-enable-ak4490-hifi-dac-custom-rom-t3707738
It'll probably not work but you'll end up with the AK4490 anyways
Click to expand...
Click to collapse
Thanks for the link, however I recently discovered that with the 'XenonHD-170609-Unofficial' ROM the in-call volume is pretty loud as well as the sound from the normal sounding speakers. It also has just about everything I'd want in a lite ROM. So far it's the ROM I'll keep.
xectis said:
Thanks for the link, however I recently discovered that with the 'XenonHD-170609-Unofficial' ROM the in-call volume is pretty loud as well as the sound from the normal sounding speakers. It also has just about everything I'd want in a lite ROM. So far it's the ROM I'll keep.
Click to expand...
Click to collapse
Use the zip anyways
Choose an username... said:
Use the zip anyways
Click to expand...
Click to collapse
Ok I'll give it a try.

Categories

Resources