Related
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?
{
"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"
}
Introduction
MultiROM is one-of-a-kind multi-boot mod for Galaxy A5. It can boot any Android ROM as well as other systems like Ubuntu Touch, Plasma Active, Bohdi Linux or WebOS port, once they are ported to our 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, daily prebuilt image files to install Ubuntu Touch 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
* Use for example Ubuntu Touch or Desktop alongside with Android, without the need of device formatting, once they are ported to Galaxy A5
* Boot from USB drive attached via OTG cable
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is messing with boot sector and data partition. 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
1) Flash Modified TWRP with odin or extract the tar file and install the img file with flashify or another recovery that has img install feature
2) Flash MultiROM zip in TWRP
3) enjoy
MultiROM has 3 parts you need to install:
Modified recovery Download the Modified TWRP for MultiROM
Patched kernel *OPTIONAL* : Not Needed
MultiROM download the ZIP file from second post and flash it in recovery.
Downloads:
Modified TWRP for MultiROM: https://www.androidfilehost.com/?w=files&flid=110082 Since the recovery image was too big for recovery partition, I used LZMA compression instead of LZO for the kernel, which saved about 3 MB
MultiROM: https://www.androidfilehost.com/?w=files&flid=110089
MultiROM Uninstaller: https://www.androidfilehost.com/?w=files&flid=110117
If you get force closes on secondary nougat ROMs:
Flash the rom, open /sdcard/multirom/roms/rom_name/system/build.prop on primary, or on TWRP with "vi" editor
and change:
Code:
ro.sys.sdcardfs=true
to
Code:
#ro.sys.sdcardfs=true
Then reboot.
DO NOT reboot the rom before changing build.prop line otherwise you will still get force closes!
You current rom will not be erased by the installation.
Important: Since the Kernel hasn't Kexec Hardboot patch, you have to check "use no kexec workaround" box in multirom settings
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Using USB drive (not tested yet)
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs
1. 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 boot sector.
2. 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.
Explanation of recovery menus
Main menu
- Add ROM - add ROM to boot
- List ROMs - list installed ROMs and manage them
- Inject boot.img file - When you download for example kernel, which is distrubuted as whole boot.img (eg. franco kernel), you have to use this option on it, otherwise you would lose MultiROM.
- Inject boot sector - Use this option if MultiROM does not show up on boot, for example after kernel installation.
- Settings - well, settings.
Manage ROM
- Rename, delete - I believe these are obvious
- Flash ZIP (only Android ROMs) - flash ZIP to the ROM, for example gapps
- Add/replace boot.img - replaces boot.img used by this ROM, this is more like developer option.
- Re-patch init - this is available only for ubuntu. Use it when ubuntu cannot find root partition, ie. after apt-get upgrade which changed the init script.
How does Kexec workaround works
You need to a kexec-hardboot supporting kernel or the non-kexec workaround as described perfectly by @nkk71 here: http://forum.xda-developers.com/show...26&postcount=4 (Be sure to leave him a thanks!)
Source code
MultiROM - https://github.com/nkk71/multirom
Modified TWRP - https://github.com/nkk71/android_bootable_recovery
Device Tree: https://github.com/DeadSquirrel01/android_device_samsung_a5ultexx branch cm-13.0-mrom
Kernel w/ kexec-hardboot patch: NOT NEEDED
Credits
A big thanks for:
@nkk71 For kexec workaround and for helped me in IRC
@Tasssadar For MultiRom Source Code
That made this possible
Donations (Please donate to the Creator @Tasssadar )
I'd be glad if you could spare a few bucks. You can use either paypal or Bitcoins, my address is 172RccLB2ffSnJyYwjYbUD3Nx4QX3R8Ris
Click to expand...
Click to collapse
XDA:DevDB Information
MultiROM for Galaxy A5 (SM-A500), Tool/Utility for the Samsung Galaxy A Series
Contributors
DeadSquirrel01
Version Information
Status: Beta
Current Beta Version: 1.0
Beta Release Date: 2016-09-10
Created 2016-09-10
Last Updated 2016-09-10
Reserved
AWESOME!!!!!!!!!!!!!!!FINALY!!!!!!!!!!!:good::good::good:
-CALIBAN666- said:
AWESOME!!!!!!!!!!!!!!!FINALY!!!!!!!!!!!:good::good::good:
Click to expand...
Click to collapse
He he thanks
one lil question from me.my current rom be untouched when i flash it,right?Because my current rom is working perfect and i dont need fail,thanx.
-CALIBAN666- said:
one lil question from me.my current rom be untouched when i flash it,right?Because my current rom is working perfect and i dont need fail,thanx.
Click to expand...
Click to collapse
No, it will br untouched, but a backup waste only 5 times, at massimum, so, if you have some free space make a backup, but as I said, it will be untouched
;DD will it work like this?
primary - stock touchwiz
secondary - cm 13
?
Thanks
supertiger1234 said:
;DD will it work like this?
primary - stock touchwiz
secondary - cm 13
?
Thanks
Click to expand...
Click to collapse
Sure
It's working perfectly! Thanks! hmm is cm 13 the best or rr? or anything else? xD
Edit: I'll choose your PacRom ;D
supertiger1234 said:
It's working perfectly! Thanks! hmm is cm 13 the best or rr? or anything else? xD
Click to expand...
Click to collapse
CM is pure android, rr has lots of feature regarding the personalization, so, if you want a rom wich is pure android, get the cyanogenmod, otherwise, if you like to personalize your android get the resurrection remix. Oh you installed multirom, so you can install both of them (you can install more than 2 roms) and decide which one is better for you
EDIT: if you use pac-rom you have to move this as primary, because it has a bug that won't boot if you set it as secondary
hmm is it normal to have "failed to mount /preload (invalid argument)"? happens when i flash rr
Edit: when i choose rr from the list, the device just reboots to multirom menu. hmm
supertiger1234 said:
hmm is it normal to have "failed to mount /preload (invalid argument)"? happens when i flash rr
Click to expand...
Click to collapse
Not, try to reboot to recovery and then reflash
DeadSquirrel01 said:
Not, try to reboot to recovery and then reflash
Click to expand...
Click to collapse
Okay I deleted and reflashed the rom, still the same error, hmm
Edit: when i go to mount and try to tick preload, it doesnt tick
Mmm, maybe i have to remove preload from the fstab. Now i'll do and notify once it's done
Works on my A500M with Stock 6.0.1 and CyanogenMod 13, thank you very much for port this mod to Galaxy A5
supertiger1234 said:
Okay I deleted and reflashed the rom, still the same error, hmm
Edit: when i go to mount and try to tick preload, it doesnt tick
Click to expand...
Click to collapse
Fixed, now download new twrp version (link in main post) and it should work
@codebseraph thanks for the support
DeadSquirrel01 said:
Fixed, now download new twrp version (link in main post) and it should work
@codebseraph thanks for the support
Click to expand...
Click to collapse
Hmm, The errors fixed buut now when I choose my second rom, it reboots to multirom menu xD
The non-kecex link doesn't work. Is there something important there?
Is the secondary rom pac-rom?
If yes, u have to move it as primary because it has a bug
DeadSquirrel01 said:
Is the secondary rom pac-rom?
If yes, u have to move it as primary because it has a bug
Click to expand...
Click to collapse
I'm trying rr and it's not working xD it's scary swapping
ResurrectionRemix-M-5.7.3-20160830-a5ultexx
supertiger1234 said:
I'm trying rr and it's not working xD it's scary swapping
ResurrectionRemix-M-5.7.3-20160830-a5ultexx
Click to expand...
Click to collapse
Well, it's a problem of the zip of the ROM. move it as primary or wait until I create a working installer
EDIT: maybe try with this installer https://www.androidfilehost.com/?w=file-thanks&fid=24591020540824243&mid=71&download_id=vlofv1jeu8k8ubpcpd375ql164&tid=1473585621&hc=c6de356c2e1c646fcb44f52216b36595df13152b92265bbb693814053fe5ca85
{
"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"
}
For kenzo/kateSupports all Roms (SHOULD)
NOTE:
Code:
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this Kernel
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
What is MultiRom?
MultiRom is one-of-a-kind multi-boot mod. It can boot any Android Rom as well as other systems like Ubuntu Touch, Plasma Active, Bohdi Linux or WebOS port, once they are ported to our 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. Roms are installed and managed via the modified TWRP recovery. You can use standard ZIP files to install secondary Android Roms, daily prebuilt image files to install Ubuntu Touch and MultiRom even has its own installer system, which can be used to ship other Linux-based systems.
I am not the developer of MultiRom. All Credits for it goes to Tasssadar, the actual developer of it.
Features:
MultiBoot any number of Android Roms
Restore Nandroid Backup as secondary ROM
Use for example Ubuntu Touch or Desktop alongside with Android, without the need of device formatting
Boot from USB drive Attached via OTG cable
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is messing with boot sector and data partition. 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 Stock Rom zips again. Make backups. Always.
TESTED ON ROMS:
Test and Report
SUPPORTED DEVICES:
kenzo
kate
Please Test it in other Similar SD Variants and Report it Below.
Bugs:
You tell me
SCREENSHOTS:
All Screenshots HERE
INSTALLATION INSTRUCTIONS:
Via The MultiRom Manager App:This is the easiest way to install everything MultiRom needs... Just follow the Below Instructions:
Install the app (Links Below)
Select MultiRom and Recovery on the Install/Update card.
Press "Install" on the Install/Update card to start the installation.
DONE! MULTIROM IS READY TO ROCK!
You current rom will not be erased by the installation.
Download link is in the second post.
Adding ROMs:
Android
Boot into MultiRom Recovery -> select MultiRom -> Add Rom -> Select the Rom's zip file and click Confirm.
Updating/changing ROMs:
1. Primary Rom (Internal)
Flash Rom's zip File as Usual, Do factory reset if needed (it won't erase secondary Roms)
Go to MultiRom in recovery and do Inject curr. boot sector.
2. Secondary Android Roms
If you want to change the Rom, delete it and add new one. To update the Rom, follow these steps:
Go to MultiRom -> List Roms and select the Rom you want to update.
Select "Flash zip" and Flash the Rom's zip File.
Explanation of recovery menus:
Main menu
- Add Rom - Add Rom to Boot
- List Roms - List Installed Roms and Manage Them
- Inject boot.img File - When you Download something, for example a Kernel, which is Distributed as a Whole boot.img (eg. Qassam Kernel), you have to use this option on it, otherwise you would lose MultiRom.
- Inject curr. boot sector - Use this option if MultiRom does not show up on boot, for example after Kernel Installation.
- Settings - Well, SETTINGS!
Manage Rom
- Rename, Delete - No Need to Explain this I Think!
- Flash Zip (Only Android Roms) - Flash zip to the Rom, for example GAPPS
- Add/Replace boot.img - Replaces boot.img used by this Rom, this is more like a Developer Option.
- Re-Patch init - This is available only for Ubuntu. Use it when Ubuntu cannot find the root partition, i.e. after apt-get upgrade which changed the init script.
GitHub Source Codes:
MultiRom Organization for Xiaomi DevicesKenzo/Kate MultiRom Device TreesMultiRom Manager App Source Codes
Current Status:
Test and Report...
CREDITS:
Rishabh Rao (ME) - For Porting MultiRom to kenzo/kate
Tasssadar - For his awesome MultiRom
nkk71 - For his No-KEXEC workaround
Version Information:
Status: Unofficial, IN TESTING, Version 33
ENJOY!:good:
XDA:DevDB Information
MultiRom For kenzo/kate, Tool/Utility for the Xiaomi Redmi Note 3
Contributors
Rishabh Rao
Source Code: https://github.com/multirom-xiaomi
Version Information
Status: Testing
Current Beta Version: v33
Beta Release Date: 2017-03-29
Created 2017-03-29
Last Updated 2017-03-30
1.Can I flash any Other Kernel?
- YES! You CAN flash ANY Kernel!!!
2. Can I Flash Roms to USB-OTG? How?
- Yes, You CAN Flash Roms to USB-OTG.
Follow these steps to do so:
1. Boot into TWRP Recovery.
2. Tap on Multirom.
3. Tap on Add Rom.
4. Select the correct Location and Flash it...
Note: Flashing on a USB-OTG takes some Time, so be patient & Don't Worry!
3.Where to Find Roms Installed in my USB-OTG Drive? How to Boot into Them?
- After Flashing the Rom you will be Booted into the MultiRom Boot Menu.
All your Roms Flashed on the Internal Memory will be in Internal Tab.
All Others will be in the External Tab.
4. How to Rename/Remove/Delete/Wipe Dalvik Cache or Flash any Other zips to an Existing Rom?
- Follow these steps:
1. Boot into TWRP Recovery.
2. Tap on Multirom.
3. Tap on the Rom which you want to Remove/Add zips.
You will find all the options you need there!
5. "Unable to Flash, I am getting Errors" / "Executing Updater Script Failed" / "Rom is not Booting". ANY HELP???
- Please Provide Logs. It will be located in /sdcard/multirom/error.txt OR if that's not present here: /proc/last_kmsg
It would be Great if you can Provide Some Screenshots.
Press Volume Down + Power Buttons Together to take Screenshots.
6. How to Disable Auto Boot / Change Rom Name / Hide Roms / Change Brightness of MultiRom Boot Menu?
- Follow these steps:
1. Boot into TWRP Recovery.
2. Tap on Multirom.
3. Tap on the 3 Dots on the Top Right of the Screen.
4. Select Settings.
You will find all the Customizations of the MultiRom Boot Menu you need there!
7. What is the No-Kexec Workaround?
- The No-Kexec Workaround by @nkk71 allows you to use MultiROM without having to flash a Kexec Enabled Kernel.
Please read More about No-Kexec Workaround from the author words only (to avoid duplicity and to get the latest information), thanks to @nkk71 once again!
http://forum.xda-developers.com/showpost.php?p=68738134&postcount=4
Download Links:
MultiRom Manager App 2.4-rishabhrao
Guys please test this in your Kenzo/Kate and Please tell me how it works
Will it work on 16 gb
pdpmoto said:
Will it work on 16 gb
Click to expand...
Click to collapse
All devices which support TWRP 3.1 official for kenzo or kate should definitely support this
Well try it out, definitely won't harm your device....
Also, uninstaller inckuded
Sent from my LeEco Le 2 using XDA Labs
Will test after exam
---------- Post added at 12:10 PM ---------- Previous post was at 12:00 PM ----------
Everything is ok as of now twrp flashed but will check more if i am in my town because If something go wrong then i will fix with my pc
Does it support the sailfish os?
Is f2fs supported?
Because I can't inject current boot sector
Anyone know if MIUI works?
Installing now on miui,reaaaally thx,because I was working on it without any result....
I will report if it worked
---------- Post added at 08:26 AM ---------- Previous post was at 08:17 AM ----------
It doesn't work on miui
It injects mltrm but,after a reboot boots normally.
Also its impossible to add roms,it says:
Failed to extract update script
Erasing incomplete Rom...
Plz fix it....
SMYM said:
Installing now on miui,reaaaally thx,because I was working on it without any result....
I will report if it worked
---------- Post added at 08:26 AM ---------- Previous post was at 08:17 AM ----------
It doesn't work on miui
It injects mltrm but,after a reboot boots normally.
Also its impossible to add roms,it says:
Failed to extract update script
Erasing incomplete Rom...
Plz fix it....
Click to expand...
Click to collapse
Hey Thanks a lot for trying and reporting...
Can you test something?
Just install mrom from app
Then goto recovery and add rom and see if you can add roms?
Also try once without injecting anything?
Coz that sometimes works too?
Sent from my LeEco Le 2 using XDA Labs
午夜听雪 said:
Does it support the sailfish os?
Click to expand...
Click to collapse
try it !
Rishabh Rao said:
Hey Thanks a lot for trying and reporting...
Can you test something?
Just install mrom from app
Then goto recovery and add rom and see if you can add roms?
Also try once without injecting anything?
Coz that sometimes works too?
Click to expand...
Click to collapse
I can't add any rom and the mltrm menu hasn't been shown up...
SMYM said:
I can't add any rom and the mltrm menu hasn't been shown up...
Click to expand...
Click to collapse
Let me check it out once...
EDIT: Can anyone try on some Rom other than miui?
So i can get a sure idea if it's a problem only with Miui or with all Roms...
Sent from my LeEco Le 2 using XDA Labs
I tried installing a few different ROMs and it always gave an error..
Hope this helps
Doesn't seem it is able to install roms to the sd card
4I-I said:
I tried installing a few different ROMs and it always gave an error..
Hope this helps
Click to expand...
Click to collapse
I have exactly the same error...
SMYM said:
I have exactly the same error...
Click to expand...
Click to collapse
Download links
[email protected] said:
Download links
Click to expand...
Click to collapse
Download via the app attached to first post
{
"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"
}
Latest Stable Magisk Version : v14.0 [2017.9.6]
Latest Magisk Manager Version : v5.3.0 [2017.9.6]
Hello, welcome to the official Magisk Release For Zenfone 2 Z00A/Z008 taken from 4pda.ru forum!
Magisk can ROOT your device, along with standard common patches.
It packs with a super powerful Universal Systemless Interface, allowing unlimited potential!
Magisk modifies boot image and add files to /data and /cache
It touches your /system partition only if root installed in /system is detected!
Features
100% fully open source and easy to build!
Magic Mount :
Allow you to do any system (vendor) modification without actually tampering the partitions.
Anything can be loaded with Magisk systemless-ly!
MagiskSU : Open Source Root Solution
Root your device with MagiskSU, based on phh's Superuser, which is based on CM Superuser.
Magisk Manager :
MagiskSU Root Management, Upgrade Magisk in-app,
Manage, Upgrade, Download, Install Magisk Modules from the community driven online Magisk Module Repo.
Magisk Hide :
Hide Magisk from detection, mainly targeting Google's SafetyNet
Resetprop :
Allow you to do any modifications to system props (build.prop), including read-only props.
It is also used along with magiskhide for tricking various device states
Multiple Entry Points :
Provide several entry points to developers, reliably pausing the boot process before everything is done.
Include post-fs (cache) mode, which happens even earlier than data is mounted (used to replace Boot Animation etc.)
Standard Stuffs :
Remove dm-verity, forceencrypt, unlock partitions blocks to support remount to rw
Installation Instructions
If you already have Magisk installed, you can directly upgrade through Magisk Manager Through TWRP Recovery
For installing Magisk the first time!
(never update magisk through application it will caused bootloop)
(If you have Xposed safetynet won't work)
Install Lastest Magisk Manager Apk
Reboot To TWRP Recovery
Select Lastest Magisk ZIP, then flash it
Reboot To Systems (wipe cache and dalvik is'nt needed if you want it then go for it)
Downloads
Lastest Magisk : https://drive.google.com/file/d/0B_t_ymFu4cH4eDNaYkhjU3lJb28/view
Lastest Magisk Uninstaller : https://drive.google.com/file/d/0B_t_ymFu4cH4bktMb2xTdk10Yzg/view
Lastest Magisk Manager Apk : https://drive.google.com/file/d/0B_t_ymFu4cH4dkpNUHh3NXVuOWc/view
Credits & Specials Thanks To All Developer XDA Forum & 4PDA Forum!
where to get uninstaller?
Arerive said:
where to get uninstaller?
Click to expand...
Click to collapse
haha forget to add it, wait bro
nice, thanks you so much, btw i had Magisk 13.3 installed, do i need to remove my module before flashing the new Magisk?
sushuguru said:
nice, thanks you so much, btw i had Magisk 13.3 installed, do i need to remove my module before flashing the new Magisk?
Click to expand...
Click to collapse
no just reflashed is ok bro no problem, same source.
mine from 12.0 to 14.0 without anyproblem
FYI : if you have xposed installed, safetynet won't work or gone
Thanks for the update! just relating here a mess i did:
You noticed the update today 2:15am XDA time, so i did wrong, opened Magisk Manager, and did the update.
what do i did to fix it:
1 -Once having Viper OS 3.0 on pc, i downloaded magisk installer, plus last HoloN kernel i was using. Taking advantage of that I was doing a dirty flash, i also down'ed last Gapps (but down'ed wrong version . . .)
Turned off phone, toke SD & plug on PC, put all downloadeds in external SD card;
2 - My Z00AD was in bootlop, so i reboot it in recovery and:
3 - Advanced Wipe > Wipe DAlvik/art cache + System + cache (JUST IT ONES!);
4 - Install ROM > Install last HoloN 6s0 version > flash Gapps and ... I downloaded x86-x64 version. Stopped here. . .
. . . So i had a previous Gapps version on PC, then . . .
Turn off Phone > pull out SD card & place x86pico 7.1 gapps version on SD
reboot ZF2 in recovery > did all step by step again:
1 - Advanced Wipe > Wipe Dalvik/art cache + System + cache (JUST IT ONES!);
2 - Install ROM > Install last HoloN 6s0 version > flash Gapps > flash Magisk > reboot.
So, i hope no other ones pass thrught that, keep attention with root stuffs . . .
El Cruz said:
Thanks for the update! just relating here a mess i did:
You noticed the update today 2:15am XDA time, so i did wrong, opened Magisk Manager, and did the update.
what do i did to fix it:
1 -Once having Viper OS 3.0 on pc, i downloaded magisk installer, plus last HoloN kernel i was using. Taking advantage of that I was doing a dirty flash, i also down'ed last Gapps (but down'ed wrong version . . .)
Turned off phone, toke SD & plug on PC, put all downloadeds in external SD card;
2 - My Z00AD was in bootlop, so i reboot it in recovery and:
3 - Advanced Wipe > Wipe DAlvik/art cache + System + cache (JUST IT ONES!);
4 - Install ROM > Install last HoloN 6s0 version > flash Gapps and ... I downloaded x86-x64 version. Stopped here. . .
. . . So i had a previous Gapps version on PC, then . . .
Turn off Phone > pull out SD card & place x86pico 7.1 gapps version on SD
reboot ZF2 in recovery > did all step by step again:
1 - Advanced Wipe > Wipe Dalvik/art cache + System + cache (JUST IT ONES!);
2 - Install ROM > Install last HoloN 6s0 version > flash Gapps > flash Magisk > reboot.
So, i hope no other ones pass thrught that, keep attention with root stuffs . . .
Click to expand...
Click to collapse
as I said on the post, dont update magisk from apk stuff you will get bootloop hehe
I installed it and reboot but my phone stuck at the Oneplus - Powered by Android Logo. Can someone help me? Im using Oneplus 5 btw
Andy1N said:
I installed it and reboot but my phone stuck at the Oneplus - Powered by Android Logo. Can someone help me? Im using Oneplus 5 btw
Click to expand...
Click to collapse
Try flashing Uninstaller zip first, and then flash the proper magisk package for your mobile... If you look at the title, you will see here "... for Zenfone" [emoji52]
Inviato dal mio ASUS_Z00AD utilizzando Tapatalk
Andy1N said:
I installed it and reboot but my phone stuck at the Oneplus - Powered by Android Logo. Can someone help me? Im using Oneplus 5 btw
Click to expand...
Click to collapse
bro its for zenfone 2 hahaha ??
Does it work with BORETS rom? And can i just flash it via recovery with borets rom?
@indunrise bro., i think the zip missing a file when installed.,the "busybox" file should be in /data/magisk/ since the newest magisk module uses that file to run.,but its absent.,so im keep getting error 1 when flashing any new v14.0 modules through twrp...it works fine now after i've put the "busybox" file at the proper place i've mentioned above...can u include the busybox file into the zip n give it proper permission ? Thanks
Here u go @indunrise
sushuguru said:
Does it work with BORETS rom? And can i just flash it via recovery with borets rom?
Click to expand...
Click to collapse
yes you can, im using borets roms
Luq4dmin said:
@indunrise bro., i think the zip missing a file when installed.,the "busybox" file should be in /data/magisk/ since the newest magisk module uses that file to run.,but its absent.,so im keep getting error 1 when flashing any new v14.0 modules through twrp...it works fine now after i've put the "busybox" file at the proper place i've mentioned above...can u include the busybox file into the zip n give it proper permission ? Thanks
Click to expand...
Click to collapse
thanks for report bugs, if i have some time will add it soon
Luq4dmin said:
Here u go @indunrise
Click to expand...
Click to collapse
if you guys needed module on magisk download and copy this to data/magisk
I've installed this, root working and satefynet passing. How can install xposed now? I've tried with app and xposed-v87.3-sdk23-topjohnwu.zip file, neither worked.
I flash magisk on lineageos and success, work fine.
But then I switch to XOSP rom of nilac and can't flash magisk. I did the same steps.
Do you know how to make it work? Thanks in advance @indunrise
ketrooo said:
I've installed this, root working and satefynet passing. How can install xposed now? I've tried with app and xposed-v87.3-sdk23-topjohnwu.zip file, neither worked.
Click to expand...
Click to collapse
Which version of Android are you using
Sent from my Z00A using XDA Labs
{
"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"
}
DISCLAIMER
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you
I've put a huge amount of time and effort in this SOLO project (no other dev has been involved), so respect me and respect my work. You are NOT allowed to use this rom, its vendor or any of the other files included as base for your projects.
FEATURES
OneUI 2.0 under Android 10, ported from the SM-A750FN
All G610 variants should be supported
Arm64 with Treble support
Fully deodexed
SIMPLE-KERNEL included, compiled from A600FNXXU5CTB9 sources. Built permissive
Deknoxed, debloated, and removed all samsung useless security stuff in rom and kernel level
N20 multi CSC with additional features (call recording, etc)
And many more!
KNOWN BUGS
Light in capacitive buttons for those devices with hardware buttons
Some 3rd camera apps like footej don't work. Whatsapp video calls could be bugged too. If so, use Whatsapp business
Other inherent bugs from OneUI and/or 7870 limitation
You tell me
DOWNLOAD
Current version: 6.0 (02/12/2020)
More info in 2nd post
INSTALLATION
Vendor partition is required.
Wipe system, data (clean install mandatory), vendor, dalvik&cache and cache
Flash rom zip
Reboot
First boot will take much time, be patient
SCREENSHOTS
https://imgur.com/a/Q5Ysvoz
ROOT
Flash Magisk canary. Stable Magisk will give bootloop.
SUPPORT
Telegram group
CREDITS
Me, for infinite hours spent with this project
Special thanks to @ananjaser1211, @SPARTANICUS and @Valera1978 for their huge contribution to the 7870 development
Thanks to my testers and @neel0210 for camera rework
And thanks one more time to @SaiFurR for his design work with banner
@topjohnwu for Magisk
DONATIONS
I don't need them, I don't need coffees or beers. I really hate see here people with high end devices asking for donations, but you can still donate money to charity. Donate money or simply help people that is really needed. If you like this rom you can make me very happy just pushing THANKS
XDA:DevDB Information
H-ROM A7 PORT, ROM for the Samsung Galaxy J7
Contributors
Astrako
Source Code: https://github.com/samsungexynos7870/android_kernel_samsung_exynos7870/tree/simple_q_permissive
ROM OS Version: Android 10
ROM Kernel: Linux 3.x
ROM Firmware Required: Oreo bootloader
Version Information
Status: Stable
Current Stable Version: 4.0
Created 2020-07-19
Last Updated 2020-08-27
H-ROM A7 PORT V6.0 (02/12/2020)
November security patch
Fixed Dual sim detection
Added High Perfomance mode
Setting volume in different apps should be fixed
You will need around a 3100Mb system partition, so if you dont have it, go and flash my repartition script
GoogleDrive folder
Mega
Md5: a9f3cacee034142024fd2802eed21b61
Spoiler: Old versions
H-ROM A7 PORT V5.0 (27/08/2020)
Spoiler: Old versions
Firmware ported from A750FNXXU4CTG2. July security patch
Added SIMPLE kernel
Echo in calls should be fixed. Other minor bugs can be present depending the phone/variant
You will need around a 3100Mb system partition, so if you dont have it, go and flash my repartition script
GoogleDrive folder
Mega
Md5: 87fc5ef5c031a2f586d762debcf7b3e0
Added a navbar enabler/disabler to the download folder
H-ROM A7 PORT V4.0 (19/07/2020)
Firmware ported from A750FNOXM4CTE3. June security patch
Specifig bugs: echo in calls
GoogleDrive folder
https://drive.google.com/drive/folders/13UG-hdqWU8nud1JCm6DD0vQXAQjeJCVP
Remember, a lot of time has been put in this project. If you like it and want to support me, no donations at all are required, just pushing thanks buttons.
Reserved
Great job
what is vendor partition? can you explain more detail? this is the first time im going to try treble rom. i dont understand what is vendor partition (what is that? is it a flashable file? or what?)
leo31 said:
what is vendor partition? can you explain more detail? this is the first time im going to try treble rom. i dont understand what is vendor partition (what is that? is it a flashable file? or what?)
Click to expand...
Click to collapse
Vendor partition is a partition that comes with treble supported phones j7 isnt one of them but with project spaget you can enable treble support on our phone so that it can install treble roms. To get the vendor partition got to this link and download the latest version (spaget x) and flash create vendor 2.0 and you will have a vendor partition.
which kernal is install ? .... i have downloaded h20 rom for g610f but i face some problem such as phone stuck and reboot automatically.... so i need to know whick kernal is installed......
Great work on the ROM
Kindly help with a working SIM Toolkit zip file for this ROM. Or anybody with a working SIM Toolkit zip file can help me with it. Thanks.
HELP! no me deja hacer vídeos llamadas en ws, en j7 prime
won't let me make video calls on
facing random reboot twice on setup screen, now it boot. no flash light on camera (light burst from screen?) like stock oreo.
hyperlapse - wide selfie nor working
i dont even know what is hyperlapse
@Astrako will you keep H-ROM A7 and S20 versions support simultaneously?
Adriano-A3 said:
@Astrako will you keep H-ROM A7 and S20 versions support simultaneously?
Click to expand...
Click to collapse
Don't ask ?... just install the rom and enjoy bro
Mscreams said:
Don't ask ... just install the rom and enjoy bro
Click to expand...
Click to collapse
Bruh
I can't install it please get me a complete manual for install
With spaget x project get bootloop l
Without show logo cant boot
Recovery: Orange Fox
Vendor 2
G610f/ds
use vendor create v1 not v2
yahiaashraf111 said:
use vendor create v1 not v2
Click to expand...
Click to collapse
And don't need change recovery ?
Now it's OrangeFox based twrp 3.4.0
Should install spaget x?
What working :
1. Wifi
2. Mobile data
3. Hotspot
4. Bluetooth
5. Gps
6. Camera
7. Phone
8. Live drawing camera
9. screen recording
10. Almost everything are working well
But, so far i found some 'not so important' bugs :
1. Opening battery usages give me FC.
2. I cant rename, remove files inside priv-app folder, but copying files to folder inside priv-app worked.
3. Removing app which located on priv-app folder using titanium backup, did not removed the apps. After reboot, the apps are there again. (Problem number 2, i cant remove apk inside priv-app)
4. no blue-light filter (i dont use it, so i dont care)
5. Some camera feature not working (hyperlase, wide selfie, front facing camera only support 4:3 size for taking photo, but video are fine). I dont know what is the function of icon at the right side of resolution inside camera (right side of 4:3 icon)
6. Since aod is not working and im not using it, better remove it.
7. Cant change clock style on lockscren (inside phone setting), but fixed by installing lockstar
8. Screen mode inside display setting has no effect at all (even stock rom does not have that feature, so.... No problem at all)
I really love this rom! Why? Because :
1. Battery life is PERFECT
2. Performance? This rom is running perfectly smooth on UI, and also while playing game and opening apps.
3. Multitasking is great
4. Android Q on 2016 device? Hell yeah.
Please fix the 1st and 2nd problem, because i need to replace gametool apk inside priv-app folder.
Installation variant 610mn-16gb
Installation variant 610mn-16gb
1- Have prepared the Vendor.zip and revertvendor files specifically this => Spaget Treble ARM64 Vendor V3.0 Based on A750FN Vendor <= not vendor v2.0 and it is not necessary to download Exynos7870_Spaget_X-V3.0. If you want root, download the magisk provided on the first page. Also have OrangeFox-R10.1_2-Unofficial-on7xelte and a version of a preferable rom oreo available to reverse the vendor and reinstall for anything.
2- Before flash create vendor, install OrangeFox-R10.1_2-Unofficial-on7xelte and restart fox recovery, then flash create vendor, without deleting anything and restarting recovery, once in TWRP-Fx, follow the steps on the first page , wipe 1DC, 2C, 3S, 4V, 5D. Internal memory is not necessary (if you view the preload between the partitions, in this step, read notes below), once the wipe has finished, install the ROM and restart. Everything should work perfectly, (at the end of the startup, perform a hard restart before configure, and then it starts without problems, that happened to me, in particular, since generally when finishing the installation of the ROM and when rebooting it usually restarts again, in this case it did not, I start directly until hello .. and then reboot)
3- Optional, once the startup is configured, restart TWRP-FX and flash magisk.
Notes: At the beginning, you could not install any ROMx64, or you needed the vendor partition, you can check the following: when you install TWRP 3.3 and when you start TWRP, the following appears in red letters at the top: “recovery is not seandroid enforcing… .. etc ”it only comes out with twrp from version 3.3, definitely you will not be able to install any rom x64, gsi, etc, since you don't have to get any errors or messages. It means that also like mine you have the smartphone since marshmallow 6.0 and it was root with supersu and odin, and you were making updates from that version; solution: restore with stock Firmware android 8.1 via odin all the partitions (BL-AP-CP-CSC-USERDATA) can be found on the network and downloaded according to your country, but always being oreo stock 8.1. Once this is done, install TWRP 3.2 with odin and then root with magisk latest stable version, not the one provided here. After that, you will be able to install several roms that you could not previously and will not have problems with the vendor, create and revert if you want. Some only install the AP to fix, but I decided on a full restore and start from scratch.
PD: I felt the need to share this experience with you so that those who have the 610mn and have problems can install it without problems, always remember to back up your important data before flashing and having a good battery charge *GOOGLE TRANSLATE*
RODRI2688 said:
Installation variant 610mn-16gb
1- Have prepared the Vendor.zip and revertvendor files specifically this => Spaget Treble ARM64 Vendor V3.0 Based on A750FN Vendor <= not vendor v2.0 and it is not necessary to download Exynos7870_Spaget_X-V3.0. If you want root, download the magisk provided on the first page. Also have OrangeFox-R10.1_2-Unofficial-on7xelte and a version of a preferable rom oreo available to reverse the vendor and reinstall for anything.
2- Before flash create vendor, install OrangeFox-R10.1_2-Unofficial-on7xelte and restart fox recovery, then flash create vendor, without deleting anything and restarting recovery, once in TWRP-Fx, follow the steps on the first page , wipe 1DC, 2C, 3S, 4V, 5D. Internal memory is not necessary (if you view the preload between the partitions, in this step, read notes below), once the wipe has finished, install the ROM and restart. Everything should work perfectly, (at the end of the startup, perform a hard restart before configure, and then it starts without problems, that happened to me, in particular, since generally when finishing the installation of the ROM and when rebooting it usually restarts again, in this case it did not, I start directly until hello .. and then reboot)
3- Optional, once the startup is configured, restart TWRP-FX and flash magisk.
Notes: At the beginning, you could not install any ROMx64, or you needed the vendor partition, you can check the following: when you install TWRP 3.3 and when you start TWRP, the following appears in red letters at the top: “recovery is not seandroid enforcing… .. etc ”it only comes out with twrp from version 3.3, definitely you will not be able to install any rom x64, gsi, etc, since you don't have to get any errors or messages. It means that also like mine you have the smartphone since marshmallow 6.0 and it was root with supersu and odin, and you were making updates from that version; solution: restore with stock Firmware android 8.1 via odin all the partitions (BL-AP-CP-CSC-USERDATA) can be found on the network and downloaded according to your country, but always being oreo stock 8.1. Once this is done, install TWRP 3.2 with odin and then root with magisk latest stable version, not the one provided here. After that, you will be able to install several roms that you could not previously and will not have problems with the vendor, create and revert if you want. Some only install the AP to fix, but I decided on a full restore and start from scratch.
PD: I felt the need to share this experience with you so that those who have the 610mn and have problems can install it without problems, always remember to back up your important data before flashing and having a good battery charge *GOOGLE TRANSLATE*
Click to expand...
Click to collapse
Hello
Thanks for your help
This installation help isn't for F variant?
SyntaxDroid said:
Hello
Thanks for your help
This installation help isn't for F variant?
Click to expand...
Click to collapse
Really if it could work, especially if you have been making updates from android v6, it is best to start the root from android v8.0 or 8.1, once achieved, try the installation, but if you already come from that version, you shouldn't have drawbacks. Try it, it's really worth it.