Its simple
All you need to do is to flash some files and then you will have Mi- Pop
1# Download zip file(links are in a txt file which is in folder as zip )
2# And flash the zip that you will get
Reboot and done
If you don't have a flash image get this (its in a txt file in folder as zip) lewa recovery image for nokia x (recommended for nokia xl) and flash it with rasher or any other to whom you trust and after flashing the image it will reboot and lewa recovery will start. Then chose install , then chose zip file that you downloaded earlier wait for to finish and then reboot.
FaQ
Did i built any of these files?
Ans: no
All these files belong to you?
Ans: Not a single one
Who's files are these?
And: These files belongs to Dom (thnks)
Have you test it on some device?
Ans: Yes. On my nokia xl working perfectly.
Why nokia x flash image ?
And: Because i did it with it. But i prefer chose cmw recovery image specific for your mobile
And do it on your own risk. I am not responsible for any kind of demage.
Was it helpfull click thnksss and remember me in your prayers and its my first theat so there can be mistakes so help me to learn more and links are in txt because i am under 10 posts. Thats why i have to zip it
I have a Cubot Cheetah 2 with Nougat (7.0) [build CUBOT_6143C_CHEETAH_2_V15_20170623].
I have managed to unlock the bootloader (and confirmed it is unlocked) and was hoping to use the following
"Fastboot boot TWRP.img"
to open and use TWRP to take a pre-root copy of my phone without flashing and then proceed to flash TWRP and then Root it.
I have tried several copies of TWRP 3.0 (supposedly for a Cubot Cheetah 2) extracting image files from the zip or rar files and running Fastboot as above. In all cases I get the following message;
downloading 'boot.img'...
OKAY [ 0.931s]
booting...
FAILED (remote: invalid kernel address: not lie in memory)
finished. total time: 0.947s
Understandably the time taken varies a little each time but I'm unable to understand why files intended for the Cheetah 2 do not work. If this will not work using the Fastboot boot option, I suspect it will not work with flash option.
Can anyone help me please.
Thanks.
TWRP and Rooting a Cubot Cheetah 2 (Nougat)
Android_Dog_Walker said:
I have a Cubot Cheetah 2 with Nougat (7.0) [build CUBOT_6143C_CHEETAH_2_V15_20170623].
I have managed to unlock the bootloader (and confirmed it is unlocked) and was hoping to use the following
"Fastboot boot TWRP.img"
to open and use TWRP to take a pre-root copy of my phone without flashing and then proceed to flash TWRP and then Root it.
I have tried several copies of TWRP 3.0 (supposedly for a Cubot Cheetah 2) extracting image files from the zip or rar files and running Fastboot as above. In all cases I get the following message;
downloading 'boot.img'...
OKAY [ 0.931s]
booting...
FAILED (remote: invalid kernel address: not lie in memory)
finished. total time: 0.947s
Understandably the time taken varies a little each time but I'm unable to understand why files intended for the Cheetah 2 do not work. If this will not work using the Fastboot boot option, I suspect it will not work with flash option.
Can anyone help me please.
Thanks.
Click to expand...
Click to collapse
I have done a lot of searching and found the following;
a) Fastboot boot recovery.img does not work on this phone, There may be some Kernel options required to be passed but I cannot find them,
b) Flashing MDSTWRP_3.0.2-7ES_Cubot_Cheetah2 from Needrom, flashes ok by either using "SP Flash tool" or "Fastboot flash recovery recovery image", but when you start the phone or reboot using "Fastboot reboot" and enter recovery, the stock rom has overwritten it. I have tried multiple flashes and erasing the partition first with no success.
The above appear to mean that I cannot use TWRP (or other Custom recovery) and so cannot install the SuperSu.zip. I have raised this on Needrom with TWRP creator who cannot offer a solution.
Before I try using an app, I'd like to ask if anyone has a solution to stop recovery being overwritten. (I have been unable to find a pre rooted image or an image containing TWRP).
Thanks
Solution Found.....The file available from NeedROM will not work with Nougat on a Cheetah 2.
rebuilt MDSTWRP_3.0.2-7ES_Cubot_Cheetah2 using Carliv Image Kitchen and the Nougat stock rom Recovery and.... the Fastboot boot recovery.img works. I will confirm if the flashing option works during the next couple of days, but this helps understanding of why earlier attempts failed.
The Cubot Cheetah 2 gives no error messages if you are trying to start an incompatible recovery file, it just overwrites recovery with stock recovery and opens that.
This thread can now be closed
I confirm that my modified version works (flash or boot). I do not know how to modify the version info yet, so I cannot publish it.
Any idea on when you might be able to post some info on the modified build? Or even some instructions for us to try and follow your lead?
I would be happy to share my version but I am concerned that it is a ported version based on the current version in Needrom created by MDSdev and the opening screens reflect that ROM build info. If someone would advise me what the rules are regarding this I am happy to change it and then publish.
Alternatively I could finish writing out the process (already started) I went through so that I have a record and others can use it to port their own version, but each version created will also reflect MDSdev's original configuration information and this does not sit well as they did the hard bit of configuring TWRP to work with Cubot Cheetah 2 hardware and earlier Android (6.0/6.1). All I have done is get it working on a Nougat(7.0) version of the Cheetah 2. Advice from an expert in these matters would be helpful.
Gotcha, hopefully someone will
chime in, I would hope given the nature of xda, as long as those who input are acknowledged and recognised all should be well....
Cubot Cheetah 2 Android 7 Root by EpicFail2017
Hi Guys i have a Cubot Cheetah 2 Android 7.
Sorry my english sucks realy!
I found only a soulution to Root it with Magisk 14.2 beta!
1 First Step Download only PC Flash Files V14 170719 and unpack it !
http://forum.cubot.net/viewtopic.php?f=21&t=1475
The ROM this FilePC Flash Files V14 170719
https://mega.nz/#F!YIt2UKLL!E2PGw3IJ_KeCuVwXhstdFw
------------------------------------------------------------------------------------------------------------
2 Step Download and Install last version!
http://spflashtools.com/windows/sp-flash-tool-v5-1728
------------------------------------------------------------------------------------------------------------
3. Step
Download Magisk v14.2 Beta and Magisk Manager Version: v5.3.0, pu it on your SDCard!
Latest Stable Magisk Version: v14.2
Latest Magisk Manager Version: v5.3.5
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
----------------------------------------------------------------------------------------------------------------------------
4 Step
Download and unzip my Patched boot.img ,then Replace the boot.img in Folder from Step 1 !
https://mega.nz/fm/Q6YV3QrZ
http://www117.zippyshare.com/v/EiwE8p57/file.html
----------------------------------------------------------------------------------------------------------------------------
5 Step
Flash with SpFlash the Rom from Step 1 in Format +Download Mode.
Make a backup first from all your Stuff and Apps!
---------------------------------------------------------------------------------------------------------
6 Step
Start Android and make dev option enabel. Usb debug etc!
Install Latest Magisk Manager Version: v5.3.5 from SdCard!
Start and make under Options update beta kanal!
Install Magisk 14.2 Beta and rebot your Phone!
Wolla you have Root this ***** !
---------------------------------------------------------------
7 Step
Download Maui META ver 9.1724.0.00 to fix The Invalid Imei Problem after flashing!
For me this step was need after flashing root+room!
https://www.needrom.com/download/mauimeta-version-9-1724/
Mfg
EpicFail2017
Any idea why the IMEI might get lost? I'm aware that that can happen in mediatek stuff with custom, but is this due to a binary check of boot.img or one of the other ROMS? Or is it the spflash util acting up because of boot.img?
I've two of these phones at the min, one of them already has some issues so don't want to play with that one as of yet - power on issues and fingerprint sensor seems to act up - anyone else?
I'm already on nougat, and your procedure is exactly the same as I was thinking (already patched boot.img using magisk 14.0 but maybe I need use the beta as you did). I didn't get to the flashing of boot.img as I'm more comfortable doing flashing the partition straight from PC (adb/fastboot etc). I'm guessing mediatek can only be flashed safely with sptool? Do we need to reflash ALL partitions as IF we can, flashing boot.img to an upgraded phone should work without loss of data/imei? maybe?
What is the 'R' near the signal in your screenshots?
I'll answer my own questions with a way to root The Cubot Cheetah 2 (Nougat) in just a few minutes ..
I was already on the same version of nougat as the download before I started.
1. Download the ROM shown above and extract, grab the SPFlash too and the drivers. Ensure unknown sources is ticked, unlock bootloader - I also disabled pin security etc (dunno if this was needed).
* Note, install the drivers with the phone NOT connected via USB.
2. Transfer the boot.img to your phone and run it through Magisk (I used the beta 14.2 as documented above and manager 5.35), patch the image file (boot.img)
3. Move the patched boot.img from the magisk folder back to the computer.
4. Run the SPFlash tool load the scatter file, select DOWNLOAD and untick everything asides from boot.img
5. With phone switched off, connect it via USB
Flash
Wait until complete
Reboot
Rooted
No loss of IMEI or data.
It's good to see some responses. I seemed to struggle with TWRP and rooting for a while and now several options are apparently available. My personal opinion (I would say this wouldn't I!) is that if I can get advice on publishing/sharing the working version of TWRP on Cubot Cheetah 2, it is really simple to root the device by flashing TWRP, copy latest version of Supers.zip onto to SD card, open phone in recovery (Which is now TWRP), set English as default language (a one time action), install the Supers.zip. Job done, rooted with the best SuperSu facilities and an industry recognised backup facilities.
Unfortunately I have not yet had any advice on how to version the Nougat version from anyone on XDA yet and I am looking at trying to get MDSdev (the Cheetah 2 Marshmallow TWRP developer) to adopt the Nougat version.
That was my worry, not sure of compatibility of TWRP or boot time stuff on the mediatek devices. Rooting is now very very simple with the previous instructions, I was thinking flashfire or flashify or similar to push recovery onto the recovery partition but it's making sure TWRP is aware of the partitions. 10 years ago I'd have had a good look through the sourcecode for any possible problems but simply don't have the time these days :/
Love the phone but was put off using it as my primary phone due to lack of root. Okay I had to install stuff on the computer to flash this, but it's turned out it's very very easy and seems very safe too!
You may like to note that MDSdev have now published a new version of TWRP that works on Nougat (this is also a later version of TWRP).
https://www.needrom.com/download/twrp-3-1-1-1-mdsdev/
Android_Dog_Walker said:
You may like to note that MDSdev have now published a new version of TWRP that works on Nougat (this is also a later version of TWRP).
https://www.needrom.com/download/twrp-3-1-1-1-mdsdev/
Click to expand...
Click to collapse
EpicFail2017 said:
Hi Guys i have a Cubot Cheetah 2 Android 7.
Sorry my english sucks realy!
I found only a soulution to Root it with Magisk 14.2 beta!
1 First Step Download only PC Flash Files V14 170719 and unpack it !
http://forum.cubot.net/viewtopic.php?f=21&t=1475
The ROM this FilePC Flash Files V14 170719
https://mega.nz/#F!YIt2UKLL!E2PGw3IJ_KeCuVwXhstdFw
------------------------------------------------------------------------------------------------------------
2 Step Download and Install last version!
http://spflashtools.com/windows/sp-flash-tool-v5-1728
------------------------------------------------------------------------------------------------------------
3. Step
Download Magisk v14.2 Beta and Magisk Manager Version: v5.3.0, pu it on your SDCard!
Latest Stable Magisk Version: v14.2
Latest Magisk Manager Version: v5.3.5
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
----------------------------------------------------------------------------------------------------------------------------
4 Step
Download and unzip my Patched boot.img ,then Replace the boot.img in Folder from Step 1 !
https://mega.nz/fm/Q6YV3QrZ
http://www117.zippyshare.com/v/EiwE8p57/file.html
----------------------------------------------------------------------------------------------------------------------------
5 Step
Flash with SpFlash the Rom from Step 1 in Format +Download Mode.
Make a backup first from all your Stuff and Apps!
---------------------------------------------------------------------------------------------------------
6 Step
Start Android and make dev option enabel. Usb debug etc!
Install Latest Magisk Manager Version: v5.3.5 from SdCard!
Start and make under Options update beta kanal!
Install Magisk 14.2 Beta and rebot your Phone!
Wolla you have Root this ***** !
---------------------------------------------------------------
7 Step
Download Maui META ver 9.1724.0.00 to fix The Invalid Imei Problem after flashing!
For me this step was need after flashing root+room!
https://www.needrom.com/download/mauimeta-version-9-1724/
Mfg
EpicFail2017
Click to expand...
Click to collapse
Anyone uploading a mirror of nougat TWRP, please.
Also i´m kind of shy flashing the recovery with patched boot.img, any experience?
Someone with nougat and superSU here? Magisk seems to have some errors with some xposed moduls duo lag of "su-root-floder"
Do you password protect your recovery?
I have now tried the Magisk and TWRP routes to achieve rooting. My preference is the TWRP route because it has the fewest steps and works!.
An point worth noting is that if you are a new user on needrom, you need to register using Chrome, Firefox or other non Microsoft browser. Once registered Microsoft Edge works. I don't know why the registration with Edge fails but It is annoying when you complete the process and do not get the registration e-mail. Without registering you cannot get the TWRP download referenced above.
Hi,
Everything seems fine except if i make a wipe of dalvik cache every app stop working. The only solution is to wipe data or flash rom again with flashtool.
any can fix it on TWRP 3.1.1.1 ?
EpicFail i´m not sure, maybe security related issue. Instead of flashing rom i prefer restore backup^^
Still did not find a public nougat TWRP download
Both old 6.0 twrp freeze if timer is set and screen is going to turn off. Isn´t an issue anymore?
Today i hardly crashed system, it was in relation to magisk modul (busybox) update issue https://forum.xda-developers.com/apps/magisk/module-canstantly-module-updated-reboot-t3696943
EDIT: switched to supersu, busybox now working
Yesterday xposed appsops was getting a fix it is still unoffical
https://forum.xda-developers.com/xposed/modules/xposed-appopsxposed-appops-4-3-t2564865/page89
Edit:
updated to magisks unoffical xposed framework 3.1.4
Currently having trouble as my device does not want to be ADB friendly from the temp flash of TWRP so I need a zip file to flash twrp from as the old ones fail to boot but I'm having trouble finding an installer file. Is there one available?
Yes it's in the op of the twrp thread, it's called the unified unofficial installer
It's literally in the first post of the thread :
https://androidfilehost.com/?fid=1899786940962593412
https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
I just unlocked my bootloader and was able to flash a recovery, LR recovery to be exact. I currently use the stock miui android 11 and I'm not sure if I'll be able to flash roms like evolution, corvus and etc. I don't understand the vendor thing when flashing a custom rom, will you help me out on how to make things clear for me on what is a vendor and how to know if it's the right one for my phone. Thank you in advance.
TheSilhouette said:
I just unlocked my bootloader and was able to flash a recovery, LR recovery to be exact. I currently use the stock miui android 11 and I'm not sure if I'll be able to flash roms like evolution, corvus and etc. I don't understand the vendor thing when flashing a custom rom, will you help me out on how to make things clear for me on what is a vendor and how to know if it's the right one for my phone. Thank you in advance.
Click to expand...
Click to collapse
IF this is the INDIAN poco x2, then your device model id is PHOENIXIN_in_global, so you cant install any custom roms here. If you can mod the id to PHOENIX then all the roms here are open for installation. However upon inspection of extracted fastboot versions (not recovery version) of Miui roms I've seen vendor files which are images, now if you can replace the vendor files from your desired rom with your model's specific vendor image files you can practically install any rom.
You'll have to extract the fastboot rom which is when you'll be able to see these files. And again just get platform tools and copy past all files from the rom to install by just clicking on flash_all.bat
AIDROOS said:
IF this is the INDIAN poco x2, then your device model id is PHOENIXIN_in_global, so you cant install any custom roms here. If you can mod the id to PHOENIX then all the roms here are open for installation. However upon inspection of extracted fastboot versions (not recovery version) of Miui roms I've seen vendor files which are images, now if you can replace the vendor files from your desired rom with your model's specific vendor image files you can practically install any rom.
You'll have to extract the fastboot rom which is when you'll be able to see these files. And again just get platform tools and copy past all files from the rom to install by just clicking on flash_all.bat
Click to expand...
Click to collapse
Very Useful Information..
Thanks))
So practically every ROM has to be altered and installed only in Fastboot version?
And how about recovery version as Install Zip Files? do you recommend it>
AIDROOS said:
IF this is the INDIAN poco x2, then your device model id is PHOENIXIN_in_global, so you cant install any custom roms here. If you can mod the id to PHOENIX then all the roms here are open for installation. However upon inspection of extracted fastboot versions (not recovery version) of Miui roms I've seen vendor files which are images, now if you can replace the vendor files from your desired rom with your model's specific vendor image files you can practically install any rom.
You'll have to extract the fastboot rom which is when you'll be able to see these files. And again just get platform tools and copy past all files from the rom to install by just clicking on flash_all.bat
Click to expand...
Click to collapse
Hey Could you please explain in detail how I can do this? I want to install a custom rom(Arrow OS) on my phone(miui 12.1.2) but I keep getting the following error when I try to do it using twrp:-
E1001 failed to update system image. ERROR 1
Failed to mount /system_root(invalid argument)
Failed to mount /product(no such directory)
I'm new to this and any help would be greatly appreciated.
PS: I get the same error for anything else I flash too.
Hey guys, my junior asked me to speed up his A51 (running stock rom) and decided to try havoc os.
I managed to install twrp but I only have experience installing ROMs in ZIP format through twrp.
Havoc distributes img.xz files - see https://download.havoc-os.com/?dir=arm64-ab
Help appreciated - how do I install img.xz file with twrp?
You must Install Orange Recovery with the zip File for the Galaxy a51 (you can get the File from another Threads here). Then you must use 7zip on Windows to extract the IMG.xz File to an .img (you can click extract here in 7zip and youre done), then transver the .img File with an USB cable to your Phone, at least Install the .img File of Havoc as System image an use Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip in order to be able to boot and then you have Havoc OS Installed