Database Users

Installing CyanogenMod by using fastboot

Hello,
The home button of my device (Magic) does not work at all. So, I can not confirm to install the CyanogenMod in the recovery screen.
Am I able to install the ROM via fastboot? or does anybody has another suggestion?
Regards,
Omer

Yes, you can flash ROMs via fastboot, but you'll need a system and data img for the ROM, and I'm not aware of a method to package them up based on an update.zip.

I checked inside the archive and saw the images but there also some scripts need to run. That's why; I couldn't dare to flash.
Is there a method I can follow?

osaatcioglu said:
I checked inside the archive and saw the images but there also some scripts need to run. That's why; I couldn't dare to flash.
Is there a method I can follow?
Click to expand...
Click to collapse
You don't need any scripts, just a system and data to flash.
fastboot flash data.img
fastboot flash system.img
You wont find these images inside the update.zip, the sys/data-imgs need to be created from the sys/data folders. Best bet is to ask someone to perform a nandroid backup, backup the imgs, wipe, flash cyan, send you those imgs, restore their old imgs.

Thank you. But, the someone's device should be identical to magic, right? I have dream also. So, I can use the nandroid backups of it. However; I don't think this would be possible. what do you think?

osaatcioglu said:
Thank you. But, the someone's device should be identical to magic, right? I have dream also. So, I can use the nandroid backups of it. However; I don't think this would be possible. what do you think?
Click to expand...
Click to collapse
I'm really not sure, but I think the device would need to have the same size data and system partitions as the Magic, which the Dream doesn't.

Use mkyaffs2 to make the System and Data .img Files
What operating system do you have because if you have linux or a linux virtual machine you could extract the update zip and use the mkyaffs2 utility code.google.com/p/yaffs2utils/ to make the system and data images.
There is also a much easier program called yaffey http://forum.xda-developers.com/showthread.php?t=1645412 but it is windows only

So this thread is kind of old, but I stumbled upon it looking for stuff.
Im using a google galaxy nexus and have a strange issue where I cant connect it via usb when in a different state than fastboot mode. I replaced the usb port (flex cable) already, but it doesnt help (if you got any advice on that, please tell me)
What I actually want to say is that I can't install cyanogen from recovery because I can't connect my phone when in recovery, but I can flash firmware normally via bootloader, I tried that already, so how exactly do I get the images for cyanogen? Because I don't fully grasp it yet.

[GUIDE] How to root your ZTE Android device

This method doesn't rely on any root exploits & will work with any Android version on the ZTE Blade (and all variants). It should work on any phone with an unlocked bootloader (all zte android devices are sold with unlocked bootloaders).
Software needed:
adb (windows/linux/mac versions available as part of the android sdk - http://developer.android.com/sdk/index.html You will find adb in the tools directory.)
fastboot (windows/linux/mac versions available here: http://koushikdutta.blurryfox.com/G1/ )
windows drivers for the phone (if you use windows: http://support.zte.com.cn/support/news/NewsDetail.aspx?newsId=1000442 )
ClockworkMod (http://clockworkmod.com/rommanager - download zte blade clockwork recovery image)
SuperUser ( http://androidsu.com/superuser/ Download Eclair/Froyo/Gingerbread/Honeycomb (2.1 – 3.2) version) - Alternatively you can use any rooted custom rom
If your phone is running Android 2.1, then it is probably a 'gen1' device, search for "Mr Pigfish" on Android market if you're unsure. Gen1 blades will need an older version of clockworkmod, 3.0.1.4 - http://download.clockworkmod.com/recoveries/recovery-clockwork-3.0.1.4-blade.img
Method:
Download/install adb & fastboot. Install drivers for the phone if needed (on Windows).
Plug your phone into your pc using the usb cable, mount usb storage, then copy the Superuser or custom rom zip onto it & unmount usb storage.
Make sure that usb debugging is enabled on your phone, there should be an icon in the status bar, you can enable it in settings (settings -> applications -> development -> usb debugging).
Open a command terminal window & change to the directory that you downloaded recovery-clockwork-[version]-blade.img to. Type...
Code:
adb reboot bootloader
This will make the phone reboot, wait for the android logo (or custom splash screen) on the phone then type...
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-blade.img
fastboot reboot
You have just installed ClockworkMod recovery. Your phone will reboot back into android, when it has done that turn it off, then turn it on with the vol- button held to start clockworkmod. Use vol+/- to navigate, home button to select an option, back button to go back. You should create a backup now before you flash anything, when that backup is complete use 'install zip from sdcard' to either install superuser to root your stock rom, or install a custom rom. If you're installing a custom rom then you'll need to wipe data/factory reset too (you will lose all data). reboot, you're done.

I'm not sure if this is the right section for the thread, it'd probably be better in blade general. I forgot that newbies can't reply here.
Anyway, for those that can reply, can you suggest any improvements? I'll find links for adb, fastboot & windows drivers later.

Everything is clear except where to find adb and fastboot for noob users... (like me).
I did a little search and found out that adb is installed with the Android SDK... so, i installed it, installed the android platform-tools package, the usb driver but i am stuck with fastboot...
There is no fastboot in the Android SDK installation directory... and i can't find it on the web... so, i can't install clockworkmod recovery and i'm stuck...
Can u help me plz ?

Yeah, as I said, I'm still looking for links. you get fastboot when you compile android from source, but that is a bit of a long & complicated way.
Here is a pre-compiled version of fastboot for windows, linux & macos http://koushikdutta.blurryfox.com/G1/
adb works without the sdk too, I'll see if I can find links for that.
The windows driver is on zte's site somewhere, but that's a pain to find anything on. I'm not sure if the Google driver works. I don't even run windows, so if anybody can help write that part...

Probably best to for XP use the exe driver installer (Thats in the pcsuite.iso in the official 2.3.5 rom)
Windows 7 just works (gets drivers from windows update).
Does the superboot apk deal with changing default.prop (to allow adb remount etc).
If not could do that (use the same thing the CM7 universal converter uses to split the boot.img).

unrandomsam said:
Probably best to for XP use the exe driver installer (Thats in the pcsuite.iso in the official 2.3.5 rom)
Windows 7 just works (gets drivers from windows update).
Click to expand...
Click to collapse
Not everybody is running the official 2.3.5 rom, it's probably a tiny fraction of users. 2.1 roms don't have the driver iso. I found the drivers & updated the first post. The drivers on the phone should work fine, if you are running an unmodified 2.2 or 2.3 stock rom, just plug the phone in & it should mount a driver cd image over usb to install the drivers.
Does the superboot apk deal with changing default.prop (to allow adb remount etc).
Click to expand...
Click to collapse
It's superuser, it's a clockworkmod zip file & no, it doesn't change default.prop. It installs superuser & su.
If not could do that (use the same thing the CM7 universal converter uses to split the boot.img).
Click to expand...
Click to collapse
Tell ChainsDD, it isn't my software, I just wrote a quick idiot's guide.

Hi wbaw....
nice to see you posting helpful stuff here....
Can I ask what is perhaps a silly question, about the rooting process for ZTE devices, without relying on root exploits?
How is this different, or better, than using the z4Root modified by kallt_kaffe App, which I have linked (MoDaCo).
Is it just the use of the exploit, or is there another reason?
I have used it on my OSF/Blade, and never lost root or had any other problem, AFAIK.
Also, I see you are not showing your previous GEN1/Gen2 all-in-one TPT for GSF any more...is it available any more for ppl who may want to try it?
Thanks in advance

The exploit that z4root uses doesn't work on newer versions of Android (2.2.2 & above), ZTE are selling some phones with these newer versions of Android.
If z4root works for you, then that's fine, there's nothing wrong with it. It just doesn't work for everybody.
If you are using a version of Android that z4root (or other root exploits) do work on, then you should update Android asap. Otherwise a malicious app could use the same exploit to take over your phone. Root exploits themselves aren't bad (as long as you're doing it to your own device, or with permission of the owner) - the fact that root exploits work is bad & a sign that you need to update the software asap.
GSF has it's own thread. You can get the same effect by using the gen1 to gen2 tpt & then installing gsf. It is buggy & old, I think there is a nasty remote root exploit out there for 2.3.4 too. Just use CyanogenMod, it's much better, less buggy, more secure, they keep up with the latest Android fixes & it has more customisation options.

Thank you for the explanation...I will go ahead and do what you have advised.
I am just continuing to use good old Swedish Spring RLS5, which I think was kallt_kaffe (Cold Coffee) also......GEN 2 thanks to your Gen 1>Gen 2 TPT.
I think t is 2.2.
If I want to proceed to permanently root as you describe, should I use z4root to unroot first?
I will probably move to CyanogenMod, so I should use your exploit-free root instructions first.
BTW, I will be sad to move on from SS, as it does seem to be as near a perfect fit as I have found for the Blade.
I did put on GSF ,some time ago, and to be very honest, I just lasted a night with it, then restored the SS Nandroid.......it didn't feel at all as satisfactory a UI experience as SS.
Perhaps it was me, you know, you get used to an old pair of sneakers, etc.
As you said, it was and is always beta...it was an early version!!!
Thanks again, and keep up the good work in these calm(er) waters

Custom roms are already rooted. You don't need to root a custom rom, you just install it with clockworkmod.
If you already have a custom rom installed then you don't need any of this guide, you've already got clockworkmod. All this guide does is tell you how to install clockworkmod.
This is for people with phones on a stock rom who want to be able to install clockworkmod to root their stock rom or install a custom rom.
You shouldn't still be using Android 2.2 because the root exploit in z4root works on it, therefore other more malicious apps could use a similar exploit without asking you first.

Hi..... does this work on any Android phone?
I have in mind the new Samsung W i 8150.
Getting one for Xmas.... AFAIK
Sent from my ZTE-BLADE using Tapatalk

It should work on some other android phones, but they'll need adb & an unlocked bootloader, so it wont work with every phone. It should work on any ZTE android phone or tablet (except maybe the tureis?).

Hi!I have a Zte Blade with 2.3.5 OS. I tried to root my phone using this tutorial, but when i write : "fastboot flash recovery recovery-clockwork-5.0.2.0-blade.img" in Comand Prompt program, i get this message : "error: cannot load : recovery-clockwork-5.0.2.0-blade.img".
Can anyone help me, please?
Thanks!

stanangel said:
Hi!I have a Zte Blade with 2.3.5 OS. I tried to root my phone using this tutorial, but when i write : "fastboot flash recovery recovery-clockwork-5.0.2.0-blade.img" in Comand Prompt program, i get this message : "error: cannot load : recovery-clockwork-5.0.2.0-blade.img".
Can anyone help me, please?
Thanks!
Click to expand...
Click to collapse
You need to download clockwork recovery & be in the directory that you downloaded it to, to run that command.

Thank you!It works. Now, can I put Cyanogenmod 7.1 on 2.3.5 OS with this root and clocworckmod ?

stanangel said:
Thank you!It works. Now, can I put Cyanogenmod 7.1 on 2.3.5 OS with this root and clocworckmod ?
Click to expand...
Click to collapse
You can put clockworkmod on, but cm7 might not work without a bit of fixing, it is designed for 2.2 blades, zte's 2.3.5 has a different radio firmware.
Is this a 2.3.5 blade? where did you buy it?

Well, first time i had 2.1 update-1.After that I updated the version to 2.2 Boygues (or something like this) and then i found on this forum the official image.bin (2.3.5) and I decided to update.But now, i want to try CM.

stanangel said:
Well, first time i had 2.1 update-1.After that I updated the version to 2.2 Boygues (or something like this) and then i found on this forum the official image.bin (2.3.5) and I decided to update.But now, i want to try CM.
Click to expand...
Click to collapse
I see, you'll need to use another image.bin to go back to 'gen2' - the zte froyo radio firmware. Otherwise you wont get any phone signal, 3g or gps on CM7 because the 2.3.5 image.bin that you installed contained new radio firmware.
You don't need to root it first, you can install clockworkmod with a gen2 radio firmware using a custom image.bin like this one that http://www.mediafire.com/?jb4crw3em2m4r4x Amphoras made.
The 2.3.5 image.bin contained another new version of the radio firmware, which isn't compatible with CM7.

Uhuuu, it works.Thank you a lot! CM7.1 is awsome.This forum is awsome.

Hey I cant acess adb after doing adb reboot bootloader. When I come to the chinese letter I cant do nothing. So i cant fastboot flash recovery recovery-xxx.img.
What im i doing wrong?

Update fails - want to flash custom rom - need some advice

Now here's the situation:
I'm still on an older ROM version (4.2.1 - see attachment)
A while ago my tablet told me there was an update. I wanted to get it, it downloads but it always fail to apply the update.
What I've done to the device so far is that I've used motochopper to root the device and got rid of some ASUS apps.
So since it refuses to update, I've decided to unlock it, flash a custom recovery and get myself a custom rom.
But I've read a lot about people bricking their devices and I doubt it'll be as easy as it was on Nexus 4 and Nexus 7 - so I need some advice on how exactly to do it.
Recently I found the thread that enables us some sort of nvflash although being on JellyBean. They were talking about a specific version of bootloader and I'm not certain if I have this bootloader since I'm on an older JellyBean version. Of course I would like to use this bricksafe as well - just in case
Can someone lead me to a guide or instruct me how to do it? I don't want to brick this device
Thx in advance

l33ch0r said:
Now here's the situation:
I'm still on an older ROM version (4.2.1 - see attachment)
A while ago my tablet told me there was an update. I wanted to get it, it downloads but it always fail to apply the update.
What I've done to the device so far is that I've used motochopper to root the device and got rid of some ASUS apps.
So since it refuses to update, I've decided to unlock it, flash a custom recovery and get myself a custom rom.
But I've read a lot about people bricking their devices and I doubt it'll be as easy as it was on Nexus 4 and Nexus 7 - so I need some advice on how exactly to do it.
Recently I found the thread that enables us some sort of nvflash although being on JellyBean. They were talking about a specific version of bootloader and I'm not certain if I have this bootloader since I'm on an older JellyBean version. Of course I would like to use this bricksafe as well - just in case
Can someone lead me to a guide or instruct me how to do it? I don't want to brick this device
Thx in advance
Click to expand...
Click to collapse
This THREAD has all the info you need to do NVFlash. It's based on 10.6.1.15 something bootloader which I believe is the same as the latest Asus official. If you're on 4.2 rom, you can flash the flatline img. and generate the necessary files from there. Once that done, you can use either the provided CWM or the latest 4.2 TWRP to flash any compatible custom rom (4.3). Have fun.

graphdarnell said:
This THREAD has all the info you need to do NVFlash. It's based on 10.6.1.15 something bootloader which I believe is the same as the latest Asus official. If you're on 4.2 rom, you can flash the flatline img. and generate the necessary files from there. Once that done, you can use either the provided CWM or the latest 4.2 TWRP to flash any compatible custom rom (4.3). Have fun.
Click to expand...
Click to collapse
First of: thanks for your reply
Guide says something about bootloader 10.6.1.15.3 - I still have an even older one (10.6.1.8...) - will it still work?

l33ch0r said:
First of: thanks for your reply
Guide says something about bootloader 10.6.1.15.3 - I still have an even older one (10.6.1.8...) - will it still work?
Click to expand...
Click to collapse
Yes, that version will work because it is on the 4.2 bootloader.
Sent from my TF300T using xda app-developers app

Only works on unlocked device?
Ok I'll try like this
These are the steps I would do: (I pray someone to look over these steps and correct me if I'm wrong )
1.) Go to asus site and download unlock_v8 and run it so to unlock my tablet.
2.) I go to androidroot.mobi and download flatline_tf300.img and nvflash-tools-win32.zip (win32? Hope that does not stand for 32-bit and hope it will work on 64-bit)
3.) I reboot my device into Fastboot (don't know exactly what that means "Please note that for transformer tablets the fastboot command might require the option "-i 0x0b05"" - at this stage the device is already connected to the pc and just in case it's not in fastboot I should run this command?)
4.) I use cmd.exe to type in these commands. In which directory? In the directory where I unzip the files from nvflash-tools-win32.zip? The guide is not too specific on that.
5.) I type in "$ fastboot flash recovery flatline_device.img" (I know for device I use tf300) which will flash the recovery.
6.) I reboot my device (let android boot?) and reboot again into recovery. (power + vol down?)
7.) I select "Advanced - Wheelie" and Step 1: Flash AndroidRoot BL and find myself with a custom bootloader.
8.) It says the device will power off. Automatically? However, I boot into android and after that reboot again into recovery mode.
9.) I choose Step 2 which will generate wheelie blobs
10.) I follow the on screen prompt to retrieve my blobs (anyone has a screenshot of that? Or is it self-expalantory?)
All this time the device is connected to pc via usb?
11.) Now I reboot my tablet into APX mode - after Step 10: am I still in recovery or booted to Android?
12.) If my tablet is recognized I type "$ wheelie --blob blob.bin" into cmd
13.) Then I will type in the commands to obtain the backups
Still got a few questions though. The device is connected to PC throughout this whole procedure, right? Where to start cmd (do I have to put the files from nvflash-tools into a specific folder from where I start cmd.exe?)
And after this procedure is done do I need to flash anything else? Or will I be then equipped with a working recovery that allows me to flash custom roms?
Thanks in advance for anyone who's taking time to answer my maybe uninformed questions but I'm kind of having troubles following the guide

[Q&A] [MOD][SEP 14] MultiROM v28 (Redesigned GUI!)

Q&A for [MOD][SEP 14] MultiROM v28 (Redesigned GUI!)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

I'm trying to get ubuntu touch RTM running with MultiRom on my Nexus 4, and it's erroring out on boot. When I try to view the log it seems like it gets overwritten by the log for the successful android boot every time I try and get the phone to a place where I can actually access it.
I couldn't find a way to view it through recovery, and copying it to the sd card doesn't give an option to re-name, so it gets overwritten. How can I actually view the log?

rooting secondary rom
Tassadar, i have your lollipop factory image installed as secondary rom. I have a question about rooting it. I have read in other threads one cannot just flash supersu zip for root to work, that people are using CF Autoroot instead. Would this method overwrite multirom recovery ? Could you say best method for rooting. Thanks

does this contain the new radio, bootloader etc?

Solved by flashing permissive boot image zip from skypompos thread and super su 2.19 zip.

Grabbed lrx21t_mako.zip from OP's basketbuild site, fresh installed as secondary ROM, stuck at boot animation forever.
Primary ROM is stock 4.4.4, with latest 4.4.4 kernel+1105recovery+v29 all installed by multirom.

5.0.1
Hey man,
I know its just out,
but a 5.0.1 LRX22C_mako.zip would be awesome!
Thanks

question
Hi, can i use multirom on my nexus 4 with lollipop? And can i use as secondary rom a rom based on kitkat?

Does MultiRom work on lg optimus g (e975) mako unlocked and by modifying build prop to nexus 4?

[Q]
Hey , i just downloaded 5.0.1 and flashed my nexus 4 with stock 5.0.1 , rooted and flashed custom recovery too, used your kernel for 5.0.1,and flashed your custom TWRP
installed multirom and now, TWRP->Advance..->Multirom->Add new rom -> android-> zip-> and here, renamed my " occam-jdq39-factory-345dc199.tgz (4.2.2)" to " occam-jdq39-factory-345dc199.ZIP" to be able to flash ZIP
when i select " occam-jdq39-factory-345dc199.zip " to flash as secondry ROM ,after 1sec TWRP restart, i mean it close itself and reopen at TWRP main page, and then i can see "occam-jdq39-factory-345dc199" in rom list
but cant boot it and getting error
(log file attached)
whats wrong?

How do I restore a backup of any secondary ROM?
Hey, I have just made a back up of the data partition of my secondary ROM but, when I tried to restore it I realised that it's only possible to restore a back up for the primary ROM. There's any way to do that? Thanks.

[A]
Eraicos said:
Hey, I have just made a back up of the data partition of my secondary ROM but, when I tried to restore it I realised that it's only possible to restore a back up for the primary ROM. There's any way to do that? Thanks.
Click to expand...
Click to collapse
Hello,
You can Swap your roms, swap primary with secondary, restore your data partition backup, then swap back,

Stuck at google logo.
Hi everyone, first post here, two days after buying this phone and I'm already in trouble.
I followed the instructions to use MultiROM to add Ubuntu Touch; and everything was fine, until I decided I wanted RW access. Then, I had the idea to sudo apt-get upgrade within Ubuntu... it failed to complete the installation of the packages (though it had space... I think), then I tried to reboot the phone.
Now it gets stuck at the google logo; and if you press the power button to shut it down, it starts again after a second or two.
I can access recovery mode pressing the three buttons, and within, I get to MultiROM TWRP by choosing "Recovery Mode"; but there's a lot of options here and I could not find anything that allows me to boot on either Android ("Internal" seems to be gone) or Ubuntu.
I'm an experienced linux user but -as can be seen- this is my first foray with Android, smartphones, and the like.
Let me know what other information should I provide; and thanks in advance for your help.

Gorsh said:
Hi everyone, first post here, two days after buying this phone and I'm already in trouble.
I followed the instructions to use MultiROM to add Ubuntu Touch; and everything was fine, until I decided I wanted RW access. Then, I had the idea to sudo apt-get upgrade within Ubuntu... it failed to complete the installation of the packages (though it had space... I think), then I tried to reboot the phone.
Now it gets stuck at the google logo; and if you press the power button to shut it down, it starts again after a second or two.
I can access recovery mode pressing the three buttons, and within, I get to MultiROM TWRP by choosing "Recovery Mode"; but there's a lot of options here and I could not find anything that allows me to boot on either Android ("Internal" seems to be gone) or Ubuntu.
I'm an experienced linux user but -as can be seen- this is my first foray with Android, smartphones, and the like.
Let me know what other information should I provide; and thanks in advance for your help.
Click to expand...
Click to collapse
Nevermind. I flashed everything from scratch and now the phone is back on its feet.

I am not sure what is the problem, but adding specific radio images for secondary ROMs is not working. I tried with Sailfish OS and MIUI to include older radio images for them to work, but nothing changed.

Update primary rom
Hello.
I want to do a clean install of euphoria as the main rom. If I do I might lose the second rom?
Thank you for your attention.

Noelito3 said:
Hello.
I want to do a clean install of euphoria as the main rom. If I do I might lose the second rom?
Thank you for your attention.
Click to expand...
Click to collapse
according to the main thread in the section update /modify not
---------- Post added at 04:29 PM ---------- Previous post was at 04:16 PM ----------
silly question maybe but if I want to make my secondary rom the interal one and wipe the current internal, a copy secondary to internal would just do that right?
I wanted to do a swap first to be on the safe side, but I don't have enough free space for that

other remark : the app doesn't see that Ubuntu touch us already installed?

Multirom Ubuntu touch start error
İ have an issue about Ubuntu touch. İ installed multirom and installed what it recomemmends. İ installed Ubuntu stable with multirom. İt installed and opened first time. i choose my lang. etc . İt says phone is ready but there is an ubuntu icon rolling. Nothing else... İ cannot skip this icon. i Waited 1 hour or more 3 times. i have a nexus 4 with stock 5.1

I have some wondering what bothers me:
1. Internal rom is mounted read-only ?
2. Matter where I install the rom that I use more often,daily use ?
3. In system I do not realize if it moves slower but in recovery does(and load slower at startup),it can influence the performances and battery life in system?

Newb needs help rooting, unlocking Bootloader and getting a Custom ROM for ALE-L21

Hey there,
I need help, hope you have some for me . I want to use the 6.0.1. OpenKirin OmniROM on my phone and struggle even figuring out a way to get there.
I just bought a used ALE-L21 DualSIM phone with the B602 Build and EMUI 4.0.3 installed. The device is not rooted, nor has its bootloader been unlocked. The EMUI update service does not offer me any patches.
Could someone please line out to me which steps I have to take in order to root my ALE-L21 and get this ROM to work?
Disclaimer: No, I'm not just a lazy moron who does not want to read other topics on this forum - I'm a mere user with less-than-average knowledge of Android development or stuff like that. And I just can't make complete sense of the various posts I've found, since English is not my mother tongue and there seems to be a whole bunch of ways to do certain things with a phone. Well, since obviously I don't want to brick my new phone, I'm not too sure how to best puzzle together the pieces this Forum offers me. It would be insanely helpful if I could get a list that reads out something like:
1. Action - Source (for needed files, e.g.) - Result, on to step 2
2. Action - Source (for needed files, e.g.) - Result, on to step 3
3. ... and so on...
Okay, just so you see that I'm not entirely lost, I'm gonna show you the picture which is currently in my mind.
From what I understand so far, there's the following steps to get there (please rectify or rearrange steps as far as needed):
1. Update the device to Vanilla EMUI 4.1, Build B895 or B896 (I am currently downloading the B896 Build from this forum - which one is recommended? My phone is DualSIM)
2. Unlock Bootloader (What's the best way to do it? Huawei CS? Heard it's not even sure you get an answer. DCUnlocker? Wants money... Please help me clarify)
3. get TWRP 3.1.1.0 (I already have the IMG file, how do I get it to run on my phone?)
4. Root the device (I'd like to go with MAGISK, does anyone have a link for a MAGISK build confirmedly working on ALE-L21?)
5. Do some magic with TWRP (Which steps exactly?)
6. Flash the ROM Zip file via TWRP
7. Flash Gapps via TWRP
Is that about it?
As I said, please feel free to add to/adjust my list!
Thanks in advance,
Pako

If you haven't already install minimal adb tools on computer (windows) found here :
http://bit.ly/2jxX4ya
You then need to unlock bootloader using minimal adb tools and the unlock code
Unlock Code:
http://bit.ly/2z9EFhV
Unlock Bootloader Method in this thread here:
http://bit.ly/2oIASBs
After you are done unlocking the bootloader
Install twrp find that here :
http://bit.ly/2ok9BTi
There was a tool that was here somewhere to install twrp but I will link to my copy here
http://bit.ly/2ATBgRP
What you do is put the twrp image file in data folder
then change the name of the twrp file to TWRP_3.1.1-0_ALICE.img or
edit the install.bat file line data\fastboot.exe flash recovery data\TWRP_3.1.1-0_ALICE.img to the name of your twrp file
Once twrp is installed then you can pick which rom you want
The 6.0 roms arent going to be supported anymore so i suggest going for 7.0 ROM
I'm on AOSPA which is the cleanest and has good battery life
To install 7.0 rom you need B895 or B896 found here on the first post:
http://bit.ly/2jypIij
this is installed through twrp (which is accessed when Phone is off by holding volume up + power then let go once it vibrates or connect the phone to the computer and then type adb devices then adb reboot recovery in minimal adb tool)
once in twrp you need to install the B895.zip or B896.zip file then reboot your phone will boot into emui
you need to install twrp again as B895 or B896 wipes it
After installing twrp you can then install any custom rom of your choice
let the rom boot and then go back into twrp and install gapps found here: "http://bit.ly/1JOWjUqi recommend nano or even pico pick am64 7.1
I would also recommend installing Galactic forced deepsleep http://bit.ly/2ANVdbS

Hey there,
thank you very, very much for your comprehensive walkthrough! (Almost*) everything worked to perfection and I am now a happy user of OpenKirin's OmniROM 6.0.3. mod! Yeah, no 7.x... but I'd prefer to wait with that until the "issues" section of AOSPA does not contain any relevant things anymore. OmniROM seems to have no issues anymore, so I'm content with my choice. I will now follow your last advice and flash the Deep Sleep Mod to improve my device's battery life, and then I'm just happy.
* = The only issue I encountered was when having flashed TWRP, the device booted to the crappy EMUI eRecovery instead of TWRP. I solved this issue using this advice from another thread.
So, once again, thank you! All you xdaDevs, keep on developing ways to improve people's lives with their android devices!
Cheers,
Pako