Related
Okay i only started looking at multirom around 4hours before releasing this, so i am aware we already have a multiROM thread, however i do believe it's outdated, and perhaps unsupported now, so i am merging a supported multirom with my TWRP thread where i will be keeping both updated, thanks to @Tasssadar for bringing multiROM to the android community. I failed hard with outdated sources from adam so i have written my own stuff, but i think iodak is using his .diff
Taken and modified from official thread at Flo
Introduction
MultiROM is one-of-a-kind multi-boot mod for Nexus 7. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Installation
Manual installation
Find all needed files here: MOD Edit: Links removed
I think Iodak has the kexec patch so use his Rom, i'm not too sure on how to add a kexec so i'll look into it, this does support KK roms as i tried it, and so has dan.
MultiROM has 3 parts you need to install:
MultiROM multirom.zip - download the ZIP file from second post and flash it in recovery.
Modified recovery (TWRP_Mrom.zip) - download and flash in recovery.
Patched kernel - Iodaks kernel i believe is kexec patched, worked for me, have a play, i use share kernel for KK roms of the same type. I suggest this.
You current rom will not be erased by the installation.
Download links are somewhere below
Adding ROMs
Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Updating/changing ROMs
Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Source code
MultiROM - https://github.com/Tasssadar/multirom/tree/master (branch master)
Modified TWRP - https://github.com/Tasssadar/Team-Win-Recovery-Project (branch master)
Device Tree for building Mrom and TWRPhttps://github.com/Fluoxetine/android_device_lge_p880 (branch TWRP)
Thanks and Links
Official thread with screenshots, donate link, and changelogs
Original Thread for 4xHD by @Adam77Root
FAQ and other notes
About security
In order to make multi-booting possible, MultiROM has to sacrifice some security measures. Firstly, on secondary Android ROMs, /system is not mounted read-only. While there are other things preventing malicious software from messing with /system, this might potentialy make it easier for such software to attack that system.
Next, MultiROM doesn't work with /data encryption. Not many people who use custom ROMs also use encryption anyway, so that isn't much of a concern.
What do the ROMs share?
All ROMs are separate, except /sdcard, which is shared between all Android ROMs.
How many ROMs can I have?/Where are the ROMs stored?
You can have as many ROMs as you can fit in your /sdcard. All the ROMs are stored in /sdcard/multirom/roms or on an USB drive. This folder is unaccessible in Android, to prevent mediascanner from scanning it. You can either in recovery, or obtain root and go to /data/media/0/multirom/roms.
Can I have different versions of Android working alongside
Yes. As long as you select "Don't shere kernel" when installing the secondary ROM, the systems are separated.
MultiROM recovery says it's 2.6.3.0. Why isn't it updated to 2.6.3.*highernumber*?
It is, it just shows wrong version.
The menu with all the ROMs won't show up during boot, how to fix it?
Either re-flash the MultiROM zip or go to recovery, Advanced -> MultiROM -> Inject curr. boot sector.
The reason for this is that something rewrote your boot.img, which happens for example when you flash a kernel. MultiROM's boot menu is part of the boot image, so it has to be added into it again.
Will you port MultiROM to device X?
No, probably. I won't port MultiROM to any device I don't own, because it is very difficult to provide the level of support I want to provide if I can't test things myself, as proven by the Nexus 4 port. I'll probably keep buying Nexus devices and keep porting MultiROM to those myself, but I can't buy every single device - I'm still a student, all my existing devices were bought using some kind of money grant or donations from users.
But, you can port it yourself, the wiki should give you at least some idea how to do that: https://github.com/Tasssadar/multirom/wiki/Porting-MultiROM
Message from Fluoxetine
I spend a lot of time trying to bring new roms/mods to this and many other devices, this doesn't really cost me anything so i will not ask for money, however i am open to other donations, if you can supply me with a donated spot on a build server that would be great! Otherwise, you can supply me with Drink and Food to snack on whilst i work away, just PM me with an amount and i'll choose a product from amazon and send you my address and info for it to be shipped directly to me Thanks for your time guys.
Click to expand...
Click to collapse
-
-
-
-
-
-
Changelog from my end and not multiROM (Ascending Order)
Code:
- [I] Release within 4 hours of solid working on it [/I]
- Fix Recovery
- Fix touch input
- Build Multirom.zip
- Remove weird vibration
- Fix MultiRom button
- Fix Layout
- Build Modified TWRP
- Create TWRP.fstab
- Build MultiRom.zip
- Fix Sizing
- Build Initial MultiRom.zip
- Create mr_init_devices.c
- Create a modified BoardConfig.mk
- Sync Modified TWRP
- Sync MultiRom
- Sync Omni
Reserved
Great work
Sent from my LG-P880 using Tapatalk
Ha, it's working... Somtimes it's a bit tricky to install secondary ROMs. To get Zaiben RC8 booting I installed it from a backup.
Pure CM11 (20140220 nightly) without gapps is booting, after flashing gapps in MultiROM it dosn't boot. Only using a backup to create it as secondary works for me...
But no way to install AnyKernels like Iodak9.95 om secondary. For CM/ASOP you can try sharing option, for stock-based the only way is using backup with installed custom kernel...
Since AnyKernel there are no boot images for different roms, so there is nothing to inject...
One downer for me is missing ADB in recovery. I've tried mounting USB-Device first, no way. Device manager in Windows shows nothing.
In bootmenue ADB is working, but it's useless without mounted system, data etc. When I use "adb shell mount -o remount,rw system" I got "mount: can't find system in /proc/mounts"
And I noticed after booting any secondary ROM, primary needs wiping cach/dalvikcache to prevent a bootloop...
EDIT: Got system access from ADB...
Code:
adb shell mount /dev/block/platform/sdhci-tegra.3/by-name/APP /system
Nice work man! Does ADB work in MultiROM? Did you check new hardboot patches? It doesn't need target kernel to be patched anymore.
Sent from my OmniROM-powered LG Optimus 4X HD
Adam77Root said:
Nice work man! Does ADB work in MultiROM? Did you check new hardboot patches? It doesn't need target kernel to be patched anymore.
Sent from my OmniROM-powered LG Optimus 4X HD
Click to expand...
Click to collapse
I've got ADB only working from boot menu. With correct mounts from ADB shell I'm able to modfy anthing I need...
But ADB working in TWRP would be nice
Adam77Root said:
Nice work man! Does ADB work in MultiROM? Did you check new hardboot patches? It doesn't need target kernel to be patched anymore.
Sent from my OmniROM-powered LG Optimus 4X HD
Click to expand...
Click to collapse
I don't think ADB works in multiROM, i saw in your patch a few ADB related stuff but in all honesty i think i left them and am still using all the same ones as grouper :') But i will be looking into this.
Also i haven't checked out any of the new hardboot patches, because in all honesty i have no clue what they are :highfive: but i can learn, i'll look into it now I just threw myself at multirom and looked at whatever the other devices had, and then just made it for p880 :3 Touch was an asshole Till i realized all i had to do was change b to an a.
Edit 1: This was the device specific mrom stuff i needed to add https://github.com/Fluoxetine/android_device_lge_p880/blob/TWRP/mr_init_devices.c
Edit 2: Added https://github.com/Tasssadar/androi...mmit/005cf387c1404eac862cc35153d7641d18faef4c this commit manualy, well for the files we had i added, we didn't have lge_devices or reboot.c and reset.c was different :s
Compiling stock CM11 kernel with this patch and see if i can dual boot stock with stock kernel that isnt patched, or cm10.1 with stock cm10.1 selecting "don't share"
Edit 3: Getting Errors with the changes i made, so gonna need some more time to amend them for the p880, i think i might have to call on some other devs to help out with this, i have no idea what i'm doing..
Nice work, could I ask you to prepare multirom uninstaller also?
It is working very well, thanks for this. All I do was I installed a CM-based Kitkat rom (Mokee) in the internal, and for the secondary, I installed stock rom (Zaiben) with kernel sharing enabled. Both roms are working flawlessly.
Thanks man I love your work!!
We can install FirefoxOS and Ubuntu too? MultiRom Manager working?
Sent from my LG-P880 using XDA Premium 4 mobile app
Can't seem to get anything to boot as secondary, I've tried zaiben and nameless. From backup and from zip, with and without kernel sharing.
Most times device just shuts down, once I got to boot animation and then it froze.
All backups normally boot as primary.
Primary uses latest iodak.
Probably I'm doing something wrong since others report it working.
Sent from my LG-P880 using Tapatalk
dcos said:
Can't seem to get anything to boot as secondary, I've tried zaiben and nameless. From backup and from zip, with and without kernel sharing.
Most times device just shuts down, once I got to boot animation and then it froze.
All backups normally boot as primary.
Primary uses latest iodak.
Probably I'm doing something wrong since others report it working.
Sent from my LG-P880 using Tapatalk
Click to expand...
Click to collapse
Try having your device connected to ac power while rebooting to secondary. If that works, then its the same problem as with adams multiboot, but it has two workarounds
Will you keep the non-dualboot twrp ?
I'm really not into this dual boot gimmicks and really like, and am still using your "clean" twrp version that works flawless BTW
Tapatalked from my CM11-LG4XHD-P880
remorema said:
Will you keep the non-dualboot twrp ?
I'm really not into this dual boot gimmicks and really like, and am still using your "clean" twrp version that works flawless BTW
Tapatalked from my CM11-LG4XHD-P880
Click to expand...
Click to collapse
You can use this recovery witout flashing the multiboot binarys... And the N7 multirom uninstaller works after editing the updater-script.
dcos said:
Can't seem to get anything to boot as secondary, I've tried zaiben and nameless. From backup and from zip, with and without kernel sharing.
Most times device just shuts down, once I got to boot animation and then it froze.
All backups normally boot as primary.
Primary uses latest iodak.
Probably I'm doing something wrong since others report it working.
Sent from my LG-P880 using Tapatalk
Click to expand...
Click to collapse
When you see in listeted roms with shared boot "remove boot.img" ,you can do this.
When I klicked "share boot" on ROM installation and after flashing it have its own boot.img. Don't know why, those ROMs will not boot on my device...
I lose signal on Miui 4.2.2 and CM10.1.3 dosen't boot.
I use Omnirom 4.4 and Iodak 9.95 as default.
Dual boot would be intresting if Android/data/ of secondary rom was on the external sdcard. I'm not very confident of using a secondary rom sharing that same folder as the primary rom. IMO that could cause some issues. Example: if I uninstall a game I'm secondary ROM the obb file of that ROM will be deleted on primary ROM and vice versa.
Tapatalked from my CM11-LG4XHD-P880
love you guy! i like the idea of having multiple roms, but I never got this stuff running not on my Lg 4X either on my nexus 7 - hope to get it working now with this release
Kexec for stock Cm11 kernel?
Can someone patch stock Cm11 kernel with kexec-hardboot ?
Okay so, i have uploaded CM11 stock kernel with a kexec patch, although this is not the same patch as used in iodak or stock patched kernel, i have taken the commits from groupers kernel with kexec and have implemented them into our stock cm11 kernel (took ages, had to do it manually).
This should mean that the target kernels do not need to be patched, only the host kernel needs the patch, i tried this with carbon-kk with my kernel flashed and added Carbon-KK WITHOUT SHARING kernel, then when i selected it to boot, as soon as the screen goes black HOLD THE POWER BUTTON, and then it will boot into the secondary Rom with the stock kernel that comes with it!
Well i think so anyway, Danny is testing for me now, maybe some of you could test it too? I'm not sure what will happen, i only tried it with carbon and my kexec as host, and stock carbon as target.
Link is here for the kernel http://d-h.st/j9Z or just check my folder in OP for the MultiROM stuff
For those who are having signal problems or no mobile internet connection from secondary ROM(s) with kernel sharing, you have to copy the kernel modules (baseband_usb_chr.ko, raw_ip_net.ko, scsi_wait_scan.ko) from internal ROM module folder (/system/lib/modules) to your secondary ROM. Make sure to change the permissions as well.
Just my 20 cents .
not able to flash kernel in secondary roms
hi, i have Enox rom as default rom and i installed omni 4.4.2 kk rom as secondary, and no kernel sharing.
now it boots my Enox rom but doesn't boot omni with error to have kernel with patch
so i go in advance > multirom > select omni > flash zip > and flash iodak kernel 9.95, but it fails every time, i tried iodak 9.5 too, but same,
am i doing something wrong or its not possible to flash kernels in secondary roms?
then what am i supposed to do now?
i really don't wanna change kernel of my default rom, it's working perfect with amazing battery life that i want, but i want secondary roms with different kernels ?
WARNING: THIS IS A BETA, USB CABLES MAY CATCH FIRE, YOUR CHAIR MAY BREAK, AND TRUMP MAY WIN THE ELECTION!
Welcome to the thread on Kali NetHunter for the Galaxy S5.
These Kali NetHunter builds are designed for CyanogenMod 12.1 and CyanogenMod 13.0.
I have TouchWiz builds as well, but NetHunter has not been tested on TouchWiz.
In theory, they should work fine on all AOSP based ROMs. The TouchWiz might work on most custom TouchWiz 5.0 ROMs too!
I am releasing on a nightly based development schedule similar to CyanogenMod.
Occasionally builds can show up more than once per night. This usually happens when there's a big update like a new device added to the line or an apk update for the NetHunter app.
These builds are NOT Aroma enabled, however, it should be no issue to just drag apps you don't need to the uninstall button in your app drawer.
Aroma support is going to be phased out for a while, especially with new TWRP releases coming out soon that may have newer kernels that aren't compatible with Aroma.
DOWNLOAD
Current version: 3.0.1 (beta, 2016-01-21)
Please be careful to download the right version based on this table:
SM-G900F, SM-G900W8, SM-G900T, SM-G900M, SM-G900A, SM-G900S, SM-G900K: klte
SM-G900I: kltedv
SM-G900P: kltespr
SCL23 kltekdi
CyanogenMod 12.1: lollipop
CyanogenMod 13.0: marshmallow
Nightly TWRP flashable zips are located at: https://idlekernel.com/nethunter/nightly/
Kernel only installers are in the kernel-only directory inside each build directory. It might be a better idea to try and install that first and see if you can boot before flashing the entire NetHunter.
BEFORE INSTALLING
Do not flash the NetHunter update zip with a fresh data partition!
Most ROMs will wipe it clean on the first boot if you haven't completed the Android Setup Wizard yet, there's no need to wipe your ROM or data to try it out. I do advise backing up your data partition before flashing the zip though.
Please make sure your phone boots fine and runs fine before flashing NetHunter. It's confusing when people report bugs that exist in CyanogenMod by itself.
The Kali chroot and apps are installed on your data partition (in /data/local for chroot). To initialize the chroot and install Kali Linux, you need to start the Kali NetHunter app.
If you are already rooted or know you have systemless SuperSU installed, you will need to go into the SuperSU app and do a full unroot then reflash CyanogenMod (for the unmodified boot partition) and Gapps. The NetHunter installer does not play well with systemless SuperSU at this time.
The NetHunter installer will automatically install SuperSU in system mode, which I consider to be more stable. Since NetHunter already modifies your system partition, there is no need to use systemless SuperSU anyways.
FULL FRESH INSTALL STEPS
Flash CyanogenMod installer zip
Flash Gapps if you want them (preferably OpenGapps pico)
Boot into device
Complete setup wizard
Reboot into recovery
Flash the Kali NetHunter installer zip from this thread
Boot into device
Open the NetHunter app
Use the Kali Chroot Manager to install Kali on your phone
You're done!
UPDATING TO A NEWER BUILD
Going from 3.0.0 and up, all you have to do is flash the new build in recovery and wipe dalvik cache.
Upgrading from NetHunter 2.0 is not recommended, and may break the NetHunter app in some cases.
RAN INTO AN ISSUE OR BUG?
In order for me to help you, you have to at minimum reply with:
The link to the exact zip you downloaded
Your device model (klte, kltecan, kltesovietrussia, etc.)
The name of the ROM you're flashing it on
The version and build date of the ROM you're flashing it on
A complete description of your problem
Optional: An audio recording of you reading this entire post
If your issue is with a specific app, it might be better to contact the developer of that app.
If your issue is during the installation (ex. flashing the NetHunter zip), then please collect a TWRP recovery.log for me.
If you found a problem and were able to fix it, and no one's mentioned it in the thread already, it would be kind to state the issue and your fix for others to make use of as well.
You can join me and the other NetHunter developers on IRC at the #nethunter room on freenode to more handily diagnose problems together.
I apologize, but I can't do house calls at this time.
KNOWN ISSUES
F2FS - You need to have an ext4 data partition. I'm not sure why, but having a Kali chroot on your data partition totally breaks booting f2fs /data.
There is currently no fstab modifications in NetHunter, but I do plan on making a zip to automatically modify the fstab for f2fs later.
Marshmallow - New android app permissions API can wreak all sorts of havoc. On first boot, accept all permissions after opening the NetHunter app then reboot your phone. You might need to battery pull if it freezes up completely. Once app permissions are accepted, the next reboot should hopefully not freeze up and allow you to install your chroot normally. (once the NetHunter app has full support for the new Android API this should no longer be an issue)
USB Keyboard - The keyboard is unusable on some devices (ex. the Note 3) due to a depth bug that causes your key presses to go right through the keyboard into the swipe pad.
Terminal App - Full screen programs like nano or vi are unusable because they can't be rendered properly. Learn sed for text file editing. Just kidding that's cruel.
Install OpenSSH server in Kali and use the JuiceSSH app as an alternative to NetHunter Terminal. (it's wayyyy better sorry jmingov)
THE KERNEL
The NetHunter kernel for the Galaxy S5 is based on CyanogenMod 13.0 kernel sources.
It has the following changes:
F2FS updated to Jaeguek Kim's latest kernel.org f2fs-stable sources
UKSM Ultra Kernel Same-page Merging KSM support
Updated and enabled USB (OTG) Atheros, Ralink, and Realtek WiFi drivers
Krait specific Cortex-A15 & Neon-VFPv4 + -O2 compiler optimizations
Compiled with Linaro's branch of GCC 4.9.4
Simple IO (SIO) scheduler as default IO scheduler
USB HID Gadget keyboard support
mac80211 packet injection support
Additional drivers built in for the full Kali NetHunter experience
SCREENSHOTS
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DEVELOPMENT
For the kernel included in NetHunter for the Galaxy S5, you can find the sources here: https://github.com/jcadduono/nethunter_kernel_klte
You can see my branch of the installer development here: https://github.com/jcadduono/kali-nethunter
Alternatively, but not updated as often, it is also available as another branch on the Offensive Security NetHunter GitHub: https://github.com/offensive-security/kali-nethunter/tree/master-jcadduono
The original branch of development is located here: https://github.com/offensive-security/kali-nethunter
DISCLAIMER
I am not affiliated with Offensive Security. They seem like cool guys though.
I'm not even a novice when it comes to security and penetration. I'm just a simple system administrator with a passion for breaking Android.
Please restrain yourselves from asking me security related questions.
Reserved
NOT SO MUCH AS SEEN ON MR. ROBOT, BUT PROBABLY EVEN BETTER
Hey Jcadduono, just wanted to say thanks! i was trying to do the same thing but never had enough time to fix all kernel recompile issues i got.
I am going to install this and run it as my daily driver i will let you know if i come up with any issues.
Thanks again and keep up the good work! If you need help anytime just say i am willing to help anytime anyway i can.
What about touchwiz
sielhadi said:
What about touchwiz
Click to expand...
Click to collapse
It's possible I could create a touchwiz branch (forked from my CM13 branch), but it would be unofficial and probably less maintained.
It would have a bunch of hacks to force the kernel to always be permissive to get past some issues, as well as merged latest drivers from touchwiz.
I would like to see if this CyanogenMod kernel works first though.
mixa2038 said:
Hey Jcadduono, just wanted to say thanks! i was trying to do the same thing but never had enough time to fix all kernel recompile issues i got.
I am going to install this and run it as my daily driver i will let you know if i come up with any issues.
Thanks again and keep up the good work! If you need help anytime just say i am willing to help anytime anyway i can.
Click to expand...
Click to collapse
Feel free to clone my nethunter_kernel_klte git branch, it's fully compliant with GCC 4.9.X. If you need any specific features you can send pull requests and it might merge them into main.
You should have no problems building it with build.sh or build_nethunter_images.sh (just edit the path variables in config sections of each file to point to right directory and compiler)
To build for kltecan, for example, just type
Code:
./build.sh can
You will get a zImage and a dtb.img inside ./build/arch/arm/boot folder.
Flashing kernels takes a little bit more work. You have to clone my kali-nethunter branch. Copy the zImage and dtb.img (replace the current ones) in ./nethunter-installer/kernels/androidversion/klteX/.
Then all you have to do is go to the ./nethunter-installer folder and do
Code:
./build.py -d klteX --androidversion -k
The -k flag builds just a kernel flashing zip out of your new zImage and dtb.img. Replace androidversion with marshmallow or lollipop. Replace X with your klte variant, ex. kltecan.
You can then flash that zip in TWRP and it will install your new kernel.
jcadduono said:
It's possible I could create a touchwiz branch (forked from my CM13 branch), but it would be unofficial and probably less maintained.
It would have a bunch of hacks to force the kernel to always be permissive to get past some issues, as well as merged latest drivers from touchwiz.
I would like to see if this CyanogenMod kernel works first though.
Feel free to clone my nethunter_kernel_klte git branch, it's fully compliant with GCC 4.9.X. If you need any specific features you can send pull requests and it might merge them into main.
You should have no problems building it with build.sh or build_nethunter_images.sh (just edit the path variables in config sections of each file to point to right directory and compiler)
To build for kltecan, for example, just type
Code:
./build.sh can
You will get a zImage and a dtb.img inside ./build/arch/arm/boot folder.
Flashing kernels takes a little bit more work. You have to clone my kali-nethunter branch. Copy the zImage and dtb.img (replace the current ones) in ./nethunter-installer/kernels/androidversion/klteX/.
Then all you have to do is go to the ./nethunter-installer folder and do
Code:
./build.py -d klteX --androidversion -k
The -k flag builds just a kernel flashing out of your new zImage and dtb.img. Replace androidversion with marshmallow or lollipop. Replace X with your klte variant, ex. kltecan.
You can then flash that zip in TWRP and it will install your new kernel.
Click to expand...
Click to collapse
You are AWESOME!
Thank you very much. I will try this as soon as i have time.
Got a bootloop on cm12 29.12.15 version. Clean install, no gapps, fully setup before flashing kali zip. Note that the device stays in the starting screen for like half a minute and goes to bootscreen then which it usually doesnt
dr460nf1r3 said:
Got a bootloop on cm12 29.12.15 version. Clean install, no gapps, fully setup before flashing kali zip. Note that the device stays in the starting screen for like half a minute and goes to bootscreen then which it usually doesnt
Click to expand...
Click to collapse
Do you get the same result with kernel-only zip? (if you flashed full zip, you will have to restore system, data, boot backups before trying kernel only)
Sorry for being a bit ignorant, but can someone explain me what is NetHunter? I've seen it for some devices but still have no idea what is it & what does it do...
I cannot, for the life of my get the 19-19 build to boot up, should I try another nightly? I'm flashing the full zip file ontop of a booted cm 13 + gapps install.
---------- Post added at 11:30 PM ---------- Previous post was at 11:29 PM ----------
Sorry should of added this, I'm on kltespr, and am flashing the 2nd one that came out.
pro_granade said:
I cannot, for the life of my get the 19-19 build to boot up, should I try another nightly? I'm flashing the full zip file ontop of a booted cm 13 + gapps install.
---------- Post added at 11:30 PM ---------- Previous post was at 11:29 PM ----------
Sorry should of added this, I'm on kltespr, and am flashing the 2nd one that came out.
Click to expand...
Click to collapse
sorry I need feedback from people who are just installing the kernel zip right now. I need to pinpoint whether the issue is kernel related or NetHunter script related.
for folks trying the kernel-only zips: Are you stuck on a neverending Kali boot logo, or the black screen with set warranty bit?
jcadduono said:
first
NOT SO MUCH AS SEEN ON MR. ROBOT, BUT PROBABLY EVEN BETTER
Click to expand...
Click to collapse
i am downloading right now this alone convices me
jcadduono said:
sorry I need feedback from people who are just installing the kernel zip right now. I need to pinpoint whether the issue is kernel related or NetHunter script related.
for folks trying the kernel-only zips: Are you stuck on a neverending Kali boot logo, or the black screen with set warranty bit?
Click to expand...
Click to collapse
bootloop
pro_granade said:
bootloop
Click to expand...
Click to collapse
doesn't help, boot loop is not specific
ALSO I really want recovery.log from TWRP with it!! (from when you flashed it)
Stuck at samsung screen
malbert16442 said:
Edit:will update with info starting fresh again
Click to expand...
Click to collapse
I might have found the issue. I was recompressing the ramdisk to the format it came in, rather than recompressing to gzip which is what the NetHunter kernels are set to use. I'm not sure what format CyanogenMod's klte ramdisks come in, but if it was anything other than gzip or xz then it wouldn't boot.
3.0.1-20160119-1913 forces ramdisks to gzip -9 instead. Hopefully that one will fix it. I suggest restoring original boot.img before flashing.
Edit: Your log says the compression was gzip, so I have no clue why it wouldn't boot. Gonna need more infos.
Also your log shows that there was no wallpaper in /data, do you have an empty data partition? It won't boot properly if android is not set up.
Update: 3.0.1-20160119-1944 will check to see if it's okay to install before trying to install.
jcadduono said:
I might have found the issue. I was recompressing the ramdisk to the format it came in, rather than recompressing to gzip which is what the NetHunter kernels are set to use. I'm not sure what format CyanogenMod's klte ramdisks come in, but if it was anything other than gzip or xz then it wouldn't boot.
3.0.1-20160119-1913 forces ramdisks to gzip -9 instead. Hopefully that one will fix it. I suggest restoring original boot.img before flashing.
Edit: Your log says the compression was gzip, so I have no clue why it wouldn't boot. Gonna need more infos.
Also your log shows that there was no wallpaper in /data, do you have an empty data partition? It won't boot properly if android is not set up.
Update: 3.0.1-20160119-1944 will check to see if it's okay to install before trying to install.
Click to expand...
Click to collapse
So this new update should be okay to flash?
pro_granade said:
So this new update should be okay to flash?
Click to expand...
Click to collapse
probably not, I still need someone to get me some form of logs while booting with kernel-only zip. I can't think of anything at all that could be preventing boot. it's even more confusing that you guys aren't even hitting the cyanogenmod boot splash.
jcadduono said:
probably not, I still need someone to get me some form of logs while booting with kernel-only zip. I can't think of anything at all that could be preventing boot. it's even more confusing that you guys aren't even hitting the cyanogenmod boot splash.
Click to expand...
Click to collapse
I dont know why log didn't show it but it did display an error about unpacking boot image. I had data and apps installed.
Are you going to compile from your source again or you want to find a definite answer.
P.s same issue with 12.1 and 13.0 with kernel.
Sent from my Samsung Galaxy S5 using Tapatalk
I think I might have fixed the issue. SELinux related. Will have new builds up soon.
Update:
https://idlekernel.com/nethunter/nightly/3.0.1-20160121-0200/
are these working for you guys?
I decide to share it there because I don't know better place for this...
This is an Xposed framework variant built for MIUI based devices running Android 5.0, 5.1 and 6.0.
Tested and working on latest ROM's on various devices.
Fully working resource hooking and themes.
Prerequisite:
- Custom recovery (CWM, TWRP)
Bugs report:
- If you get any lag, broken feature or any App force closing, post your Xposed logs.
- If you get a boot-loop, reboot and get the logcat with "adb logcat -v time".
Please pay attention:
Archive with Xposed installation contains some necessary information and it is very important to successfully installation to choose right archive.
- "arm" means the devices that are running arm32 operating system and uses ARM architecture CPU.
- "arm64" means the devices that are running arm64 operating system and uses ARM64 architecture CPU.
- "x86" means the devices that are running x86 operating system and uses x86 architecture (Intel) CPU.
- "sdk21" means Android Lollipop 5.0.x
- "sdk22" means Android Lollipop 5.1.x
- "sdk23" means Android Marshmallow 6.0.x
If you try to install wrong archive it will not installed and error message appears in TWRP installation log.
Magisk
Magisk (systemless) variants of archives separated only by Android versions (sdk21, sdk22 and sdk23). CPU architecture will be detected automatically.
How to install:
- Install Xposed Installer app
- Make a nandroid backup
- Copy the Xposed file and the uninstaller to your sdcard
- Flash "xposed-vxx-sdkxx-armxx-MIUI-edition-by-SolarWarez-xxxxxxxx.zip" through a custom recovery (TWRP/CWM...)
- Reboot and wait, it may take several minutes to boot up depending on your ROM size and installed apps amount. If phone still not boot after 5 minutes then you need get boot log by "adb logcat -v time", reboot into recovery and restore backup or de install Xposed
Attention!
Starting from v86 official version of Xposed become more compatibly with ROMs that use a Resources subclass for e.g. theming, like MIUI.
So, try firstly official Xposed on your device. If it will works well (take a look at themes, if they works well, then all Ok), then you doesn't need this version of Xposed.
But I suppose that on some devices official Xposed still may cause bootloops.
Donate to @rovo89
All credits go to @rovo89 for his amazing job on Xposed framework
Can you post your sources? Are the "Resources" and "TypedArray" the only changes?
Share your sources please
Thanks
in mi4c works perfect!!!thanks man
the only thing that ''breaks'' is edge utility!!!and another that dowload modules manual not from inside app(doesnt care at all) just mention it!!!thanks again!!!
Can't download MODULES directly from xposed app.
Sent from my MI 4S using Tapatalk
ViTAMiNCHEG said:
Can't download MODULES directly from xposed app.
Sent from my MI 4S using Tapatalk
Click to expand...
Click to collapse
That was always a issue with xposed and miui, even when I've used it on my nexus 4. Guess it have something to do with permissions with miui.
Line app unable to open photo selector activity https://drive.google.com/file/d/0B3TzmNRa2nE6RE1kbHhuNUV5Y2c/view?usp=drivesdk
Sent from my hermes using XDA Labs
Nice! I submitted a request for include this in Material Design Xposed Installer. It would be awesome!
If i already flashed v80, do i need to flash the uninstall.zip before flashing v83, or can i flash v83 directly?
dagger1 said:
If i already flashed v80, do i need to flash the uninstall.zip before flashing v83, or can i flash v83 directly?
Click to expand...
Click to collapse
Flash it directly without uninstalling
Sent from my MI 4S using Tapatalk
Hey bro i was using miui v80 on mi4 wile long but accidently i flashed official xposed v83 file from xposed installer and got boot loopbafter that i had uninstalled xposed with zip and rebooted phone!! My mi4 booted normaly but now if i am flashing miui xposed v80 which i previously used and clear dalvik cach than phone does not optimizing any apps and system apps crashing!! Cant do any opration!! Same is happen with v83 also and also i updated my whole miui devloper rom to new version thus i cant flash xposed got same error!! Plzzz help!!
Sent from my MI 4W using Tapatalk
saiyammorakhiya said:
Hey bro i was using miui v80 on mi4 wile long but accidently i flashed official xposed v83 file from xposed installer and got boot loopbafter that i had uninstalled xposed with zip and rebooted phone!! My mi4 booted normaly but now if i am flashing miui xposed v80 which i previously used and clear dalvik cach than phone does not optimizing any apps and system apps crashing!! Cant do any opration!! Same is happen with v83 also and also i updated my whole miui devloper rom to new version thus i cant flash xposed got same error!! Plzzz help!!
Sent from my MI 4W using Tapatalk
Click to expand...
Click to collapse
I had similar problem, fixed by deleting the xposed folder in /data partition
@SolarWarez Got bootloop after install xposed tweak (ROM: 6.4.28)
Firstly i was install xposed in my phone (arm x64 v83 hermes) and i just need to wait until it finished boot
Then i install extMIUIv7, check tickbox for enabled it, and reboot
And voila, i got bootloop
I tried to format art cache in TWRP and it fixed it.
Well this is weird seems global beta + xposed break ART Caching
Sent from my hermes using XDA Labs
Not working
Can't install on Redmi Note 2, MIUI 7.3.1 stable (Android 5.0.2).
Error is: "chown: /system/lib/libart.so.orig.gz: Read-only file system".
Manual mounting in r/w mode does not help =(
Actually, this file libart.so.orig.gz is not the first in batch and not the last, but error happens only with it.
update: I have modified SolarWarez's package, now installs normally. Tested, working.
(what i did is disabled script interruption on some errors while setting owner and permissions on files).
Download here: https://drive.google.com/open?id=0B4lahQDWFyqqOHJKaFFfbEtmZlE
How to uninstall Xposed?
I have flashed xposed-v83-sdk22-arm64-MIUI-edition-by-SolarWarez-20160428 but any downloaded and enabled module won't work (even after reboot).
Moreover my Xiaomi Redmi 3 Pro is laggy now.
How can I unistall it?
ROM MIUI 7 by miui.it 6.5.5 based on Android 5.1.1.
Edit:
Uninstalled flashing xposed-uninstaller-20150831-arm64.zip by TWRP
I'll use it when I buy my Xiaomi... in the future...
Hi just discovered a bug: when in stock browser I go to bookmarks/history browser force closes. This also happens when browser tries to show a dialog window (for instance, when you go to xiaomi.eu it asks to install tapatalk). Log attached
Edit: attached another log got when getting to copy text in stock browser
I have flashed xposed-v83-sdk22-arm64-MIUI-edition-by-SolarWarez-20160428 on MIUI7 using Lenovo A7000-a
Xposed give error, Phone freezes and I have to retart it by pulling battery of mobile phone. I am using Xposed for only XInternalSD because its mount SD Card as internal Memory.
When is v84 coming? Hope bugs get resolved and there's compatibility with miui 8
THIS PROJECT IS NO LONGER SUPPORTED.
# F2FS Loopback Bug Workaround
## README.md
### Copyright (C) 2017-2018, VR25 @ xda-developers
#### License: GPL v3+
---
#### DISCLAIMER
This software is provided as is, in the hope that it will be useful, but without any warranty. Always read/reread this reference prior to installing/upgrading. While no cats have been harmed, I assume no responsibility under anything which might go wrong due to the use/misuse of it.
A copy of the GNU General Public License, version 3 or newer ships with every build. Please, read it prior to using, modifying and/or sharing any part of this work.
To prevent fraud, DO NOT mirror any link associated with this project; DO NOT share ready-to-flash-builds (zips) on-line!
---
#### DESCRIPTION
Some kernels from devices with F2FS-formatted data partition (i.e., Motorola) have a bug which prevents loopback devices (.img files) from being mounted read-write. This limits systemless modifications that can otherwise be achieved with Magisk.
This module works by moving magisk.img to the cache partition (EXT[2-4]-formatted) and linking it to its actual location (i.e., /data/adb/magisk.img). The other half of the process consists on automatically recreating magisk_merge.img shortly after boot and handling it the same way as magisk.img.
With this workaround, a patched kernel is dispensable.
Cache partition's size is essentially the only limiting factor -- and that's pretty much self-explanatory.
/cache/magisk_.img is automatically backed up to/data/adb on boot (only if modified) & restored on install. Thus, whenever cache is wiped, magisk_.img and its respective symlink can easily be restored by simply reinstalling the module.
---
#### PRE-REQUISITES
- Magisk v15+
- F2FS-formatted data partition
- EXT[2-4]-formatted cache partition
---
#### SETUP STEPS
Fist time
- Install from custom recovery as a regular flashable zip.
Upgrades
- Install from Magisk Manager or custom recovery.
- Reinstall after cache wipes to restore magisk.img backup.
---
#### NOTES/TIPS
Always install large modules from custom recovery only. In fact, I recommend installing every module from recovery if your device's cache partition has a very small size (i.e., only a few Megabytes).
To revert changes, uninstall the module, boot into custom recovery and delete </data/adb/magisk.img> & <magisk.img.bkp>. Lastly (while still in custom recovery), move </cache/magisk_.img> to </data/adb/magisk.img>.
Updates and reinstalls can be carried out from Magisk Manager as well.
---
#### ONLINE SUPPORT
- [Facebook Support Page](https://facebook.com/VR25-at-xda-developers-258150974794782/)
- [Git Repository](https://github.com/Magisk-Modules-Repo/f2fs-loopback-bug-workaround/)
- [XDA Thread](https://forum.xda-developers.com/apps/magisk/guide-magisk-official-version-including-t3577875/)
---
#### RECENT CHANGES
**2018.10.9 (201810090)**
- Bug fixes
- Latest module template, with added sugar.
- Magisk 15-17.2 support
- Updated documentation
**2018.9.2 (201809020)**
- Improved compatibility
- Major optimizations
- Updated documentation
**2018.8.1 (201808010)**
- General optimizations
- Striped down (removed unnecessary code & files)
- Updated documentation
**2018.7.24 (201807240)**
- Fixed modPath detection issue (Magisk V16.6).
- Updated documentation
Works with stock roms as well ?
My cat lost two and half lives because of this thread. Sadly, the disclaimer is in order, so I can't sue.
Is this for Nougat or Marshmallow?
does this work on nougat update or only on MM?
Can someone please confirm if it will work on retin channel with dual sim... I am running stock nougat... Will it work or does it only work on MM rom...
Anybody know how to fix notifications without breaking safety net?
VR25 said:
DISCLAIMER
Not taking responsibility for any thermonuclear war or cat harm. Do it at your any risk.
NEEDED
[Unlocked Bootloader] https://youshouldknowthisbynow.com
[Latest TWRP] https://forum.xda-developers.com/mo...recovery-unofficial-twrp-moto-z-play-t3495629 credits @Alberto97
[Latest FSFS patched Kernel] https://forum.xda-developers.com/moto-z-play/development/kernel-stock-kernel-f2fs-patched-t3546732 credits @tomparr
[Latest Magisk zip] https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 credits @topjohnwu
[Latest Magisk Manager app] https://play.google.com/store/apps/details?id=com.topjohnwu.magisk&hl=en credits @topjohnwu
PROCEDURE
0. reboot bootloader
1. fastboot boot twrp.img
2. adb sideload fsfs patched kernel
3. adb sideload magisk
4. reboot system
5. install magisk manager from play store
6. reboot bootloader [yes, again]
7. fastboot boot twrp.img [yes, again]
8. adb sideload magisk [yes, again]
9. reboot system [yes, ag... you get the point]
10. open magisk manager settings, enable "magisk hide"
11. reboot, done
Click to expand...
Click to collapse
Works like a charm.
I however did not temporarly boot into TWRP, I flashed it as such.
mhp1995 said:
does this work on nougat update or only on MM?
Click to expand...
Click to collapse
I'm on Android 7.0 Nougat.
Thanks!
Erwin
fortunz said:
My cat lost two and half lives because of this thread. Sadly, the disclaimer is in order, so I can't sue.
Click to expand...
Click to collapse
Hopefully your cat is ok now
jjdavis699 said:
Is this for Nougat or Marshmallow?
Click to expand...
Click to collapse
mhp1995 said:
does this work on nougat update or only on MM?
Click to expand...
Click to collapse
mhp1995 said:
Can someone please confirm if it will work on retin channel with dual sim... I am running stock nougat... Will it work or does it only work on MM rom...
Click to expand...
Click to collapse
It should work on both Marshmallow and Nougat, as long as you pick the appropriate kernel for your system version (6 or 7). @mhp1995, I don't think the software channel matters. It should work across all (retus, retin , reteu, etc.).
xxBrun0xx said:
Anybody know how to fix notifications without breaking safety net?
Click to expand...
Click to collapse
No idea at this point, man. I've never had to fix mine. Perhaps only some people have it...?
@erwin, I chose not to touch the stock recovery to keep OTA installations straightforward. Easy for everyone.
one question... if i wanted to install viper4android and xposed framework, should i download it from the magisk download tab or shud i flash them manually via TWRP? thanks
mhp1995 said:
one question... if i wanted to install viper4android and xposed framework, should i download it from the magisk download tab or shud i flash them manually via TWRP? thanks
Click to expand...
Click to collapse
There are specific versions of these modified for systemless root. DO NOT install the standard versions. You should follow the instructions given in Magisk Manager app to download and install.
VR25 said:
There are specific versions of these modified for systemless root. DO NOT install the standard versions. You should follow the instructions given in Magisk Manager app to download and install.
Click to expand...
Click to collapse
Ok :good: I think xposed is not available at the moment for nougat ..Its WIP....If possible when the time comes try to include installing xposed via Magisk tutorial in this thread too.... Coming to the posts, u mind if i add this rooting tutorial in my all-in-one thread? Of course credits will be given
mhp1995 said:
Ok :good: I think xposed is not available at the moment for nougat ..Its WIP....If possible when the time comes try to include installing xposed via Magisk tutorial in this thread too.... Coming to the posts, u mind if i add this rooting tutorial in my all-in-one thread? Of course credits will be given
Click to expand...
Click to collapse
Oh, yes the availability... I forgot to mention that. Hopefully a proper Xposed version will be available for nougat very soon. When that happens, I'll update the thread.
About adding the tutorial to your thread... sure, go ahead.
I honestly declare I didn't read whole thread - is this method work for stock Nougat rom - I need root for Titanium Backup only for now , since facebook messenger goes crazy on my new phone MZP :-/ . Or maybe there is a way to restore old conversations ,not restored automatically in Facebook Messenger - anybody knows how to do it ? . On every phone I had I used root for two things mainly - Titanium Backup and to block adds - dns66 do block adds very well without root but , Titanium Backup has no alternative for me .
Just for the records: Magisk 12 release works fine.
@sebx_g1 incredible 2 pages! That are more than 10 postings! Sure nobody can read so much. And nearly all ask or answer your question, but it is just too much ...
tag68 said:
Just for the records: Magisk 12 release works fine.
@sebx_g1 incredible 2 pages! That are more than 10 postings! Sure nobody can read so much. And nearly all ask or answer your question, but it is just too much ...
Click to expand...
Click to collapse
[emoji4] but voting is only 3 works 2 not, so?
Wysłane z mojego XT1635-02 przy użyciu Tapatalka
What is expected to be done for next OTA to work? Just restore Nandroid backup of boot partition and everything should be ready for patchlevel newer than January 2017, right? And afterwards f2fs fixed kernel and Magisk again for having root again of course.
(twrp not flashed, no logo modified, system should be untouched)
---------- Post added at 09:14 PM ---------- Previous post was at 09:11 PM ----------
sebx_g1 said:
[emoji4] but voting is only 3 works 2 not, so?
Click to expand...
Click to collapse
Xposed does not work on Nougat by now. Magisk does. The 2 negative votes you counted referred to Xposed
Anyone have an adblock that works with systemless and passes safetynet? Do we need to check the "enable systemless for adblocks" in Magisk settings?
DNS66 do the same what do adblock, you can use it without root. But yes, there is special version of adblock systemless.
Wysłane z mojego XT1635-02 przy użyciu Tapatalka
Worked fantastically, thanks a lot!
http://pecholite.blogspot.com.es/2017/03/multi-rom-tripl3t-b594-odex.html?m=1
MULTI-ROM TRIPL3T B594 ODEX
Multi-rom Tripl3t is the first rom for pecholite that adapts to all types of users and allows to start the smartphone with Emui 4.0, LineageOS 14.1 or AOSP 7.1.1 (Nougat).
I present my first custom rom based on fellow cerberus v2 + John Miller . The Lineage part is @XePeleato and the Aosp of @haky86.
Too much for you?
More novice users should not be scared because the installation and configuration is incremental and that is why I say that it fits any user profile.
User Profiles:
Depending on the concerns that are most suited to your profile you should take the installation to the point that best meets your needs.
As a user I want ...
1- I want a stock experience with some extras but without Root.
You must install the rom file by TWRP and dot. The rom is the same as the cerberus V2 but comes with no root.
It incorporates among others ..., gyroscope, call recording, multiwindow ...
REQUIRED REQUIREMENTS:
-Bootloader Unlocked.
-TWRP
- Android 6 - C432B594 Stock - Recommended.
2- I want you to have root access too.
After installing the rom you must enter the store and download the application magisk manager and ready. You already have root access and get the most out of the rom, but not only that, but root access can be hidden to play PoGo or use payment applications and pass the SafetyNet test.
3- I want to activate extra functions and transform and customize the rom butt.
Well what you have to do is install this file from TWRP point.
We will achieve the following:
- Activate Multiuser
- Enable Local Update
- You can choose whether to install the Huawei magnifier or not
- Busybox, Viper4Android and SLC disappear
- You can choose to install the busybox and the viper in a systemless way and in this way the SLC is no longer necessary
- Advanced Reset
- New lock screen 100% customizable.
- The screen automatically turns on and off when opening and closing the mobile phone case
- Incorporates system apps uninstaller
- Total Commander
- Greenify
- Etc...
4- I want to be able to choose which rom to start the smartphone.
For that it is necessary to have followed steps 1, 2 and 3 and it is necessary to configure magisk to have default access to all requests per adb and applications and install the multiboot option.
To install Dualboot you must go to the file EXTRAS.ZIP that you will find inside the system folder of the rom. Uncompress your content in the external memory and install the DualBoot app and keep the files in memory because we will need them for later.
Then we start the dualboot application to be granted superuser permissions automatically. Then with SimpleReboot we restart a recovery and make a backup of boot.img in case something goes wrong, since it will be the only thing we will need to repair a possible failure or error.
VERY IMPORTANT: We need to have 3Gb of available space in the External SD for each additional rom we want to install, that is, if we are going to install Lineage and Aosp we will need 6Gb of available space.
4.1- I want AOSP.
We must download these files and install them at the same time and in order from TWRP
- Rom
- Aniboot
- Gaaps
- Magisk
4.1- I want LineageOS.
We must download these files and install them at the same time and in order from TWRP
- Rom
- Aniboot
- Gaaps
- Magisk
4.3 I want the 3 Roms at a time.
Then follow steps 4.1 and 4.2
Restarting the system will take us directly to the last ROM installed. Once started and configured we installed the dualboot app that we had left on hand in the external SD. Repeat the operation on each of the additional roms installed. Once installed dualboot in all you can remove the app from the sd and of course all the corresponding installation files.
To change rom you have to enter the dualboot app and choose which one to start the system and restart.
MENTAL NOTE 01:
The 3 roms will have the same bugs as the originals. I am not yet qualified to fix them or even try, but I think that to be my first job is more than enough.
MENTAL NOTE 02:
The DualBoot application also installs an app called Leaks that controls possible bugs to send them to the original DualBoot developer.
I do not want to forget to give credits and thanks for:
@topjohnwu for creating magisk
@chenxiaolong for creating DualBoot and @BrainNotFound for portarlo
+ John Miller to create CerberusV2
@haky86 for creating Aosp and CWMR
@XePeleato for creating LineageOs and TWRP and Kernel
Greetings from Barcelona (Catalonia)
Fedroid said:
MULTI-ROM TRIPL3T B594 ODEX
Multi-rom Tripl3t is the first rom for pecholite that adapts to all types of users and allows to start the smartphone with Emui 4.0, LineageOS 14.1 or AOSP 7.1.1 (Nougat).
I present my first custom rom based on fellow cerberus v2
Click to expand...
Click to collapse
Please delete, XDA app crashed while writing
Fedroid said:
MULTI-ROM TRIPL3T B594 ODEX
Multi-rom Tripl3t is the first rom for pecholite that adapts to all types of users and allows to start the smartphone with Emui 4.0, LineageOS 14.1 or AOSP 7.1.1 (Nougat).
I present my first custom rom based on fellow cerberus v2
Click to expand...
Click to collapse
Link please :laugh::laugh::good::good:
kilroystyx said:
Link please :laugh::laugh::good::good:
Click to expand...
Click to collapse
MULTI-ROM TRIPL3T B594 ODEX
http://pecholite.blogspot.com.es/2017/03/multi-rom-tripl3t-b594-odex.html?m=1
Fedroid said:
MULTI-ROM TRIPL3T B594 ODEX
http://pecholite.blogspot.com.es/2017/03/multi-rom-tripl3t-b594-odex.html?m=1
Click to expand...
Click to collapse
Why in the screenshots there is a ss with a lockscreen asking for a fingerprint to unlock? I know that no P8Lite has a fingerprint sensor
hi6120sft ale-l21 said:
Why in the screenshots there is a ss with a lockscreen asking for a fingerprint to unlock? I know that no P8Lite has a fingerprint sensor
Click to expand...
Click to collapse
Because it is cool, no more reasons sorry
I stucked on a first logo
blewko said:
I stucked on a first logo
Click to expand...
Click to collapse
Try a factory reset with stock recovery and flash again.
It helps in most cases
Does Xposed from Magisk work on our device?
I tried, but it stucks at boot logo.
arviit said:
Does Xposed from Magisk work on our device?
I tried, but it stucks at boot logo.
Click to expand...
Click to collapse
he should work... i have magisk and xposed but on C432B596 ROM
arviit said:
Does Xposed from Magisk work on our device?
I tried, but it stucks at boot logo.
Click to expand...
Click to collapse
It worked for me once but I think I reflashed something or so and then it didn't. After flashing it wait at least 1 hour before stopping the boot. After that, it doesn't seem to work.
xander33 said:
he should work... i have magisk and xposed but on C432B596 ROM
Click to expand...
Click to collapse
Are you passing Safety net?
arviit said:
Does Xposed from Magisk work on our device?
I tried, but it stucks at boot logo.
Click to expand...
Click to collapse
It works. Flash Xposed and don't forget to wipe cache.
Phone will start in about 30 minutes.
It works. Use SDK 23 for this rom
Vinnipinni said:
It worked for me once but I think I reflashed something or so and then it didn't. After flashing it wait at least 1 hour before stopping the boot. After that, it doesn't seem to work.
Are you passing Safety net?
Click to expand...
Click to collapse
No with the B596 ROM (i think its related to the new security patch)
With the B588 instead you have to disable xposed reboot the phone and safety net will be ok
xander33 said:
No with the B596 ROM (i think its related to the new security patch)
With the B588 instead you have to disable xposed reboot the phone and safety net will be ok
Click to expand...
Click to collapse
I can confirm Xposed works. Not the Magisk one though.
Use the one from the mega root thread https://forum.xda-developers.com/p8lite/general/mega-thread-root-unbricking-updating-t3400994.
I also know the xposed torch works. Like to recommend xEmui module.