Related
ClockworkMod-based recovery for Geeksphone peak! This recovery will allow you to backup your system along with userdata and restore at any time in the future. This will also help you to install ROMs right from your device, my subsequent Android / Firefox OS ROM builds for Geeksphone Peak can be flashed with these recoveries.
Cheers! Check the Downloads tab above to download the recoveries.
Installation
Make sure you have ADB and Fastboot installed. Reboot into fastboot mode.
Code:
adb reboot bootloader
Then move into the directory you saved the recovery image in and run this command from a Terminal / Command Prompt.
Code:
fastboot flash recovery cwm-*****.img
XDA:DevDB Information
ClockworkMod Recovery for Geeksphone Peak, Tool/Utility for the Android General
Contributors
tuxboy
Version Information
Status: Beta
Created 2014-10-06
Last Updated 2014-10-06
Hi Tuxboy, I'm looking for a Jellly Bean rom for my Peak, KitKat would be awesome. Are you developing one?
Thank you
Multiple custom Android recovery solution for Xperia M2.
Requirements:
Rooted Sony Xperia M2 D2302-6/D2403
Installed ADB Interface Driver *
Stock firmwares (Android 4.3 - 5.1.1).
Locked bootloader.
How to use:
Extract recovery installer zip into your computer hard drive.
Enable USB Debugging.
Connect computer with the device via USB.
Execute installation script and follow the instruction on the screen.
Enter into recovery:
Power ON phone.
When the cyan led glows push/press the appropriate button:
Volume Down - PhilZ
Volume UP - TWRP
Camera button - CWM
Download recovery:
v0.1
PhilZ Touch Installer
PhilZ Touch flashable
v0.2
PhilZ Touch Installer
PhilZ Touch flashable
v0.3
PhilZ Touch Installer
PhilZ Touch flashable
v0.4
TWRP Installer
TWRP flashable
v0.5
PhilZ TWRP CWM Installer
v0.6
PhilZ TWRP CWM Installer
v0.7
PhilZ TWRP CWM Installer
v0.8
PhilZ TWRP CWM Installer
v0.9
XperiaM2 MultiRecovery Installerhttp://forum.xda-developers.com/attachment.php?attachmentid=3754953&stc=1&d=1463594740
Download pre-rooted flashable.zip:
D2303_1281-1548_18.3.1.C.1.13 pre-rooted
D2303_1281-1538_18.3.1.C.1.17 pre-rooted
Includes:
- SuperSU v2.46
- PhilZ Touch Recovery
- RICDefeat (modulecrcpatch and wp_mod.ko based on code by @cubeundcube)
Install pre-rooted flashable zip:
Enter into recovery and create a backup of current firmware:
. Backup and Restore -> Backup to storage/sdcard1/clockworkmod/backup/yy-mm-dd.fw.vesrion
. Copy pre-rooted flashable.zip to storage/sdcard1:
. Wipe and Format Options -> Wipe Dalvik/ART Cache or Clean to Install a New ROM
. Install Zip -> Choose zip from /storage/sdcard1 -> choose the path to the folder that contains the flashable.zip
. Confirm..
Questions & Answers:
Q: Do I need root access to install and use MultiRecovery?
Q: How to disable Sony RIC on Xperia M2?
A: Yes. The root is mandatory. EagleRootTool_20160531 * is my recommendation for a successful completion of these tasks (on Android 5.1.1).
Q: Do I need to 'install' any pre-rooted flashable.zip beforehand?
A: No. This is an optional feature and is there for if and when you’d ever like to try it.
Q: Is it possible to flash any custom ROM?
A: Yes. On unlocked bootloader you can flash a custom kernel with this tool, included.
Changelog:
v0.9
Date: 2016-05-18
Update and recompile Android 'init'.
Update CWM and PhilZ to latest builds.
Add selinux_mod and copymodulecrc to installation script.
The module loading stage is logged in mr.log file.
v0.8
Date: 2016-01-19
Added installation script with separate adb support for Linux OS.
Stripped version of byeselinux LKM to reduce size.
Relevant bug fixes, update LEDs (media and notifications one) in regular Xperia M2.
MOBILE [aka Emergency] version, which consists on a shell script that can be executed from an elevated Terminal Emulator.
Demo video preview *
v0.7
Date: 2015-11-09
Use of Chargemon instead of e2fsck as base script to trigger the Recovery.
Usage of ByeSELinux kernel module to change SE Linux Status from Enforcing to Permissive during boot. (Many thanks to NUT and zxz0O0).
(After the user interaction time span, the module is unloaded to continue to regular boot.)
The same 3 recoveries as KitKat are included, TWRP, PhilZ and CWM.
Compatibility with legacy e2fsck script inside the installer (Option number 2: "Install MultiRecovery (Android 4.4.x)")
New Linux/OSX installer script (WIP, only supports installation of Android 5.1.1 Recovery. Will be improved in the future).
Updated BusyBox.
More information can be found here *
v0.6
Date: 2015-08-22
Fixed USB connection, adb shell commands can be used while device is in recovery mode.
v0.5
Date: 2015-06-22
Added button management, vol-up for TWRP, camera button for CWM.
Added TWRP Recovery v2.8.1.0 to installer.
v0.4
Date: 2015-05-19
Temp fixes in a script to catch key events.
v0.3
Date: 2015-05-19
Changes in recovery.fstab to avoid messages about /misc partition.
Used a new compilation of busybox * to correct error: unzip zip flags 1 and 8 are not supported.
v0.2
Date: 2015-04-01
The zip files is packed with new binary interpreter.
The flashable zip can be used with PRFcreator *
v0.1
Date: 2015-03-06
Initial public release.
Credits and thanks:
Phil3759 for source.
Team Win Recovery Project.
DooMLoRD for ramdisk.
rachitrawat and [NUT] for recovery installer.
zxz0O0 for PRFCreator.
@Andrej732 and @linuxct for improvements on installer script.
XDA:DevDB Information
XperiaM2 MultiRecovery for locked bootloader, Device Specific App for the Sony Xperia M2
Contributors
AleksJ, linuxct
Version Information
Status: Stable
Created 2015-03-06
Last Updated 2016-05-17
I'm not responsible for any problems caused by using anything from here, so do it at your own risk!
What about 18.3.1.C.1.13 4.4.4 firmware?
Not tested for now .
Yes, it is tested and works on recent (18.3.1.C.1.13) version.
Edit:
Please note that for proper installation Sony RIC protection must be disabled( the related source code can be found here ) .
ric_disabler
ric_disabler-flashable
The recoveries from first post are assembled and designed to be used on locked bootloader, recent additions of TA and modem partitions is only for backup purposes.
The builds linked here can be used on unlocked devices with stock based Android ROM's.
I test it out my own, but if fail... Can i restore stock? Is this kernel or only recovery?
Edit!
Working and Device succesfully booted up
Working on 18.3.1.C.1.13 4.4.4 firmware
This is an only one fresh compiled PhilZ Touch recovery, you can make and restore backup to your android, e.g. KitKat 4.4 - 18.3.1.C.0.21.
Also you can use PRFCreator to create a pre-rooted stock firmware, and then flash with this recovery.
I hope this will be useful for people who can't unlock their BL for some reason/restriction, but want to have the possibility to use a custom Android recovery.
May try this over the weekend if I get time. Need a recovery on my m2, as currently rooted on 18.1.3.c.0.21 with no recovery. :thumbup:
Installed no problems now have a working recovery thanks:thumbup:
sent from my Rooted B/l 4.4.4 kk Xperia D2303
Works on 18.3.C.0.37
~Patryk said:
Works on 18.3.C.0.37
Click to expand...
Click to collapse
Thank you for your confirmation
Good work bro!! Thanks !
can you show us some roms that we can try plz
Here is a complete log of my backup/restore process, right before I post this thread.
You can try this, or If you like, make one for yourself.
Most of Pre-Rooted firmware created with PRFCreator like this , also can be flashed.
can I use this recovery on unlocked bootloader?
vladcepesh said:
can I use this recovery on unlocked bootloader?
Click to expand...
Click to collapse
Basically it is made to work with a Locked Bootloader, so that most likely it will not work correctly without some extra work.
Tried this method, not booting into recovery
I can see the Cyan LED, but no there's no effect with all button combinaison....
Hi @NoobZik
The button is the last thing for what you need to worry about.
Can you please post :
Your kernel version.
The method you are using to disable RIC kernel module.
The contents of a log file located at /cache/recovery/last_log right after a failed recovery boot attempt.
p.s.
And if there is still some misunderstanding :
This recovery is for Locked Bootloader
AleksJ said:
Basically it is made to work with a Locked Bootloader, so that most likely it will not work correctly without some extra work.
Click to expand...
Click to collapse
Is not it easier made when the bootloader unlocked?
https://gist.github.com/Noobzik/3ad32df03a11de27e656
18.3.1.C.0.21
I've re-Locked before proceeding
vladcepesh said:
Is not it easier made when the bootloader unlocked?
Click to expand...
Click to collapse
Yes, but that was not my goal.
Currently I don't have unlocked Eagle device, so I can't test it for myself.
NoobZik said:
https://gist.github.com/Noobzik/3ad32df03a11de27e656
18.3.1.C.0.21
I've re-Locked before proceeding
Click to expand...
Click to collapse
Assume that you have installed correctly Superuser or SuperSU, and RIC is disabled.
Check if this files exist for you after installation:
Code:
/system/bin/recovery.cpio
/system/bin/e2fsck ( this file should be a script )
/system/bin/e2fsck.bin
/system/bin/recovery.sh
Try reinstall your current busybox with this script.
also can be used to open not boot?
no longer need to be changing the kernel to flash
alba46d said:
also can be used to open not boot?
no longer need to be changing the kernel to flash
Click to expand...
Click to collapse
Yes xd
Hi. The Symphony H50 custom rom ported by Miui 7.1.
1. Root your phone.
2. Need recovery of TWRP. (if not available download: http://*******/1aHo9z or http://filesrightnow.com/file/0579x72)
3. Download custom rom from http://*******/1aHlAK or https://drive.google.com/file/d/0B_W9Vs6WyGMuMlJSSTJaempSa3M/view?usp=sharing
4. unzip by 7zip. password http://filesquick.net/file/0579J85
5. Zip all files and send to SD card or phone memory (if TWRP not recognize SD card)
4. Wipe all and install it by TWRP recovery.
5. restart phone and
enjoy.
XDA:DevDB Information
Miui 7.1 ported for Symphony H50)
Contributors
salahuddin85
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Version Information
Status: Testing
Created 2016-05-15
Last Updated 2016-05-15
Download Link
Please direct link give me
Please give direct link
Please provide direct download link
salahuddin85 said:
Hi. The Symphony H50 custom rom ported by Miui 7.1.
1. Root your phone.
2. Need recovery of TWRP. (if not available download: http://*******/1aHo9z or http://filesrightnow.com/file/0579x72)
3. Download custom rom from http://*******/1aHlAK or https://drive.google.com/file/d/0B_W9Vs6WyGMuMlJSSTJaempSa3M/view?usp=sharing
4. unzip by 7zip. password http://filesquick.net/file/0579J85
5. Zip all files and send to SD card or phone memory (if TWRP not recognize SD card)
4. Wipe all and install it by TWRP recovery.
5. restart phone and
enjoy.
XDA:DevDB Information
Miui 7.1 ported for Symphony H50)
Contributors
salahuddin85
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Version Information
Status: Testing
Created 2016-05-15
Last Updated 2016-05-15
Click to expand...
Click to collapse
Bro Download link not working plz give me other link
Lollipop 5.1 Lenovo A369i
Code:
Disclaimer: I am not responsible for anything that happens as a result of flashing these files.
This is Pure Lollipop 5.1 with TWRP 3.0 recovery for A369i
Im not developer of this rom, found it on 4pda.
This is not a flashable zip, PC required using SPFlashtool
Note: This firmware is for row is S108/S110 only, dont attempt to flash this on other row or it will brick your device.
Instructions:
*First you must have Correctly driver installed first. (Driver has already in the archive).
*Backup your data.
*Device at least 50% Battery percent.
Lets start
1. Download the file, then extract it on your desired directory.
2. Open SPFlashtool on the extracted file.
3. Load scatter file on the extracted file located on target_bin folder
4. Power off device (untick quickboot), then remove the battery
5. Connect/Plug Usb cable on device after 3-5 sec click firmware upgrade
6. Wait until green circle pop up
7. Unplug and turn on your device, first boot takes 8-10 min.
Download Link:
https://yadi.sk/d/bL2Ry_SmsmWjQ
Bugs:
Accelerometer
3G (see 2nd post for fix)
Credits:
darklord4822
[email protected]
XDA:DevDB Information
Lollipop 5.1, ROM for Lenovo A369i (see above for details)
Contributors
test_only
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Row S108/S110
Based On: AOSP
Version Information
Status: Stable
Created 2017-08-09
Last Updated 2017-08-08
For 3G fix flash the attached zip.
As for the root just search for supersu flashable zip then flash it on recovery.
f.. off man.. my phone was working fine, and, doenst even power on !!! Fuc.. uu
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