Related
Advanced Stock ICS Kernel for Xperia SHere is a kernel based on the Stock ICS kernel with some features which come from DoomLord's GB kernel.
Features
autorooting
CWM recovery (with reboot recovery support)
init.d support (thanks DoomLord)
TUN/TAP driver
Download links
Build 17 (Fastboot)
Build 17 (CWM)
Build 16 (Fastboot)
Build 16 (CWM)
Prerequisites
An unlocked bootloader: Tuto here.
A stock ICS ROM (6.1.A.0.452 to 6.1.A.2.55). Don't expect this kernel to work with CM9/10.
How to flash
For elf files :
Read DoomLord's guide
You just have to replace kernel.elf by the name of the downloaded kernel in the flash command (eg : ics4.elf)
For zip files:
Flash the zip file from the recovery
Changelogs
Build 17 (08/12/12) :
Merge 6.1.A.2.55 kernel sources
Autodetect rom version in default.prop based on build.prop
Updated recovery, adbd and busybox (JB version)
Build 16 (01/11/12) :
Random reboot issue probably fixed (patch from CM10 kernel, thanks Kali)
Rom version increased to 6.1.A.2.50
Updated recovery, adbd and busybox (JB version)
SD card mounted by default in recovery
Vibration at boot removed, only led and backlight now
Build 15 (05/09/12) : Increase ROM version in default.prop from 6.1.A.0.452 to 6.1.A.2.45
Build 14 :
New MMC driver (from codeaurora) : it fixes issue while formatting partitions in CWM
Wifi module built from source (in the ramdisk)
Updated recovery
Disable again hardware clock
Build 13 :
Backup / Restore fixed with dedupe
Backlight enabled in CWM
Better "reboot recovery" handling in adbd / busybox and recovery
Build 12 :
Updated recovery
Hardware clock correctly saved (from CM9 kernel)
Build 11 : Go back to GCC 4.4 (fix artifacts with camera preview)
Build 10 :
Kernel built with GCC 4.6
Several autoroot fixes (Superuser app pushed just once and correctly removed in /data)
Working reboot recovery command (with adb too)
Updated su (3.1.1) and Superuser (3.1.3)
A bunch of new command included in the new busybox (ifconfig, wget, vi, and many more !)
Build 9 :
Kernel built from sources
TUN/TAP driver included (for VPN)
Build 8 : Fix mass storage in CWM
Build 7 : Fix MTP
Build 6 : Key mapping in CWM fixed
Build 5 :
New recovery built from latest CM9 sources
Fixed generation of md5sum with nandroid
Increased font size in CWM
Boot partition backup and restore
New adbd built from CM9 sources (fixed an issue with hardcoded sh path in /system)
Build 4 :
Correct su binary
Don't wait 3 sec if /cache/recovery/boot exists
Build 3 :
Leds and vibrator at startup fixed
Sources
Ramdisk sources
Kernel sources
Credits
DoomLord : many thanks to him for its kernel and all his scripts.
championswimmer and sminki for their help
FreeXperia team for their work on CM
makes it perfectly start does not make any errors
greetings and thanks
yes it boots!
(maybe you can help with my Question here )
Hey, I also have tested several times to include recovery, but withut succes, didn't get any further then a booting kernel without recovery or vibration and LED on to enter recovery but no entering recovery and kernel that doesn't boot.
Please pm me if you want to work together, I saw your kernel is from ICX team? I know nick very well so I'd would be a pleasure to work with you too
sminki said:
yes it boots!
(maybe you can help with my Question here )
Click to expand...
Click to collapse
for this question and any other other question similar to this
head here
http://forum.xda-developers.com/showthread.php?t=1659584
it has menu driven process to extract and repack kernel.elf (ramdisk also can be extracted and packed )
Welcome Champ, good to see you mate.
I will leave the thread here as knowing you, you will have a kernel ready for us in a few hours.:fingers-crossed:
thanks for the test guys... so now i'm diving into including recovery....
good to know i could pull off kernel.elf editing in my first attempt lol
@colossus if not in hours, then definitely within 1 or 2 days
EDIT :
can someone send me the kernel.elf from FXP122 cm9 ??
will save me the time to download the whole ROM
This is sweet, good job!!
john9 said:
This is sweet, good job!!
Click to expand...
Click to collapse
Only a few files to edit now
We'll keep you updated
Sent from my LT26i using XDA
championswimmer said:
btw if anyone wishes to do this before me,
this diffstats should help you
https://github.com/championswimmer/xps-ramdisk/commit/a61969aefca00ce3a6e4e112e97403fb6f0c79e9
it shows how doomlord added recovery to gb kernel..
Click to expand...
Click to collapse
cool.. well that's a hell of a lot easier than the manual route I was taking. This was my goal, but for personal rather than pseudo "xda glory" as I'm working with DooM's stuff I didn't feel right posting it without his permission, but he's probably too busy to care
go for it championswimmer :victory:
Excuse my noob-ish question, but... what's the difference between a 'stock' kernel with recovery and a completely custom kernel like DoomLord's? Is it to do with core frequencies/governors?
fNOOB said:
Excuse my noob-ish question, but... what's the difference between a 'stock' kernel with recovery and a completely custom kernel like DoomLord's? Is it to do with core frequencies/governors?
Click to expand...
Click to collapse
Frequencies and governors are one possible customicing for kernels, for the most users the most important thing. also Kernel modifing can allows you init.d support, undervoltscripts and also allows (or denies) MSC support... and, for shure, clean out some tings, make things more efficiently and and and... a dev is nearly totaly free to create a very customiced kernel with or without special Driver support or so
noob.fl said:
Frequencies and governors are one possible customicing for kernels, for the most users the most important thing. also Kernel modifing can allows you init.d support, undervoltscripts and also allows (or denies) MSC support... and, for shure, clean out some tings, make things more efficiently and and and... a dev is nearly totaly free to create a very customiced kernel with or without special Driver support or so
Click to expand...
Click to collapse
Cheers mate
sminki said:
cool.. well that's a hell of a lot easier than the manual route I was taking. This was my goal, but for personal rather than pseudo "xda glory" as I'm working with DooM's stuff I didn't feel right posting it without his permission, but he's probably too busy to care
go for it championswimmer :victory:
Click to expand...
Click to collapse
using someone's work just because 'he's too busy to care' is not the aim which we at xda strive for ...
i've already talked with Doomlord regarding using his recovery... and as long as I clearly mention it's his work and provide links back to his thread, he has no issues with anyone else using it...
(and i'll surely do that ^^ when i release a kernel containing his recovery, if i ever do that)
championswimmer said:
using someone's work just because 'he's too busy to care' is not the aim which we at xda strive for ...
i've already talked with Doomlord regarding using his recovery... and as long as I clearly mention it's his work and provide links back to his thread, he has no issues with anyone else using it...
(and i'll surely do that ^^ when i release a kernel containing his recovery, if i ever do that)
Click to expand...
Click to collapse
cool, i was only making a bad joke, we all know DooM cares
sminki said:
cool, i was only making a bad joke, we all know DooM cares
Click to expand...
Click to collapse
lol.. ok
and i'll bring you some unicorns soon
championswimmer said:
lol.. ok
and i'll bring you some unicorns soon
Click to expand...
Click to collapse
I can't wait! :victory:
so this kernel has the ro.secure property in default.prop set to 0??
Tnaks mate for your job!
tested right now the test version and the sony logo fades and reboots
can you plug it into a pc and run a logcat from command prompt and give me the output of any comes??
This is a permissive kernel built from source for galaxy E series.
As a music lover I always used to enjoy viper4android made by @zhuhang on my old phone.
Then I found about xtrememusic by PDesire and Divinebeats by @TheRoyalSeeker
Then I got the E series and those sound mods didnt work with selinux set to enforcing.
And now it runs flawlessly
All kernels are built from source with little to no improvement only selinux set to permissve.
Although I might have done some overclock or undervolting. I dont really remember. So enjoy.
If you are a music freak the i suggest to flash the xtrememusic mod or divinebeats mod . THEY ARE AWESOME.
This will trip the knox flag thereby potentially voiding your warranty.
I hold no responsibility in any case if you decide to flash this product.
DOWNLOADS:
SM-E700F
E500
Downloads for other variants will be coming soon.
I have seen that kernel of both E500F and E500H are compatible to each other so its tested
PLEASE LEAVE FEEDBACK AND HIT THAT THANKS BUTTON.
CREDITS: Samsung for the source code @jackeagle, @androidexpert35, @zhuhang, @TheWhisp, @TheRoyalSeeker
reserved
how can i install it?
1 how to install it
2 is it stable ? problems ?
3 does it work on E500f ?
thx
E700H?
excellent work
this is working with E700h/dd. I have checked and its changed to permissive
nepalbiraj said:
this is a permissive kernel built from source for galaxy e series.
as a music lover i always used to enjoy viper4android made by @zhuhang on my old phone.
Then i found about xtrememusic by pdesire and divinebeats by @theroyalseeker
then i got the e series and those sound mods didnt work with selinux set to enforcing.
And now it runs flawlessly
all kernels are built from source with little to no improvement only selinux set to permissve.
Although i might have done some overclock or undervolting. I dont really remember. So enjoy.
If you are a music freak the i suggest to flash the xtrememusic mod or divinebeats mod . They are awesome.
this will trip the knox flag thereby potentially voiding your warranty.
I hold no responsibility in any case if you decide to flash this product.
downloads:
sm-e700f
e500
downloads for other variants will be coming soon.
I have seen that kernel of both e500f and e500h are compatible to each other so its tested
please leave feedback and hit that thanks button.
Credits: Samsung for the source code @jackeagle, @androidexpert35, @zhuhang, @thewhisp, @theroyalseeker
Click to expand...
Click to collapse
work on e700m
thanks !
Someone tell us the instruction?
iamjibril said:
Someone tell us the instruction?
Click to expand...
Click to collapse
1.download the kernel ImG
2.install flashify from playstore
3.grand su permissions and install the kernel img reboot
4.remember to backup stock kernel.
Mem_0 said:
1 how to install it
2 is it stable ? problems ?
3 does it work on E500f ?
thx
Click to expand...
Click to collapse
1.download the kernel ImG
2.install flashify from playstore
3.grand su permissions and install the kernel img reboot
4.remember to backup stock kernel.
YES ITS STABLE.NO MAJOR BUGS ONLY PRIVATE MODE IS NOT WORKING.
YES IT IS TESTED ON SM-E700F
do press thanks.
iamjibril said:
E700H?
Click to expand...
Click to collapse
It will be supported soon.
You can try it but it is not tested.
instructions are above
srijesh said:
this is working with E700h/dd. I have checked and its changed to permissive
Click to expand...
Click to collapse
Now install Xtrememusic and enjoy:good:
Willing to wait for e700h thanks buddy. And btw what do I choose on flashify? Boot img or recovery img? Thank you
working in e700h
It is also working in e700h.
download the .img
then download flashy from playstore
press boot.img & select the downloaded .img
it will automatically restart & then see in about phone
Sucessfully to permissive
Can you please send me screenshot of your e700h about phone thank you
I was successful in flashing this but suddenly my root access gone. Is it safe to reroot?
root again
no problem you can flash the root again
srijesh said:
It is also working in e700h.
download the .img
then download flashy from playstore
press boot.img & select the downloaded .img
it will automatically restart & then see in about phone
Sucessfully to permissive
Click to expand...
Click to collapse
thank you srijesh for testing it out. Can you post screenshot for confirmation?
Works on E500M?
screenshot
http://c:\screenshot.png
---------- Post added at 06:34 AM ---------- Previous post was at 06:33 AM ----------
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/
This is an unofficial TWRP 3.x build for the Huawei Honor 3C (h30u10/H30-U10)
This project is abandoned! I'll reopen the thread if I have any progress in the future... If you want anything from me you can contact me in my email address, in Telegram (@iamnotstanley) or in private message.
Only use this binary with your own responsibility, and please read the "known issues" list.
Working:
Everything, except the things in the "known issues" list.
TWRP functional checklist, but in this list not everything applies for our device
Known issues:
flash/restore image (boot&recovery) (installing with a zip [if you're using codelover's fixed update-binary] and backup working correctly) **need help **
Download:
Latest and older versions: See the DevDB Downloads page or click here. (Mirror)
Install:
You can install this recovery in 4 way:
Using an another version of TWRP: install the downloaded zip
Using an another version of TWRP: extract the zip and flash the image
Using SP Flash Tools: extract the zip and flash the image
Using Flashify or other flashing app: extract the zip and flash the image
Revert easily to codelover's TWRP:
Download from here the UPDATE-TWRP-2.8.6.0_H30-U10.zip or the UPDATE-TWRP-2.8.6.0_V2_H30-U10_EU.zip and install it inside the TWRP, after that if you reboot to recovery, you will see the old version.
Changelog:
TWRP changelog: here
Device changelog:
3.1.1-0:
Updated to the latest version.
We still have the the "image flash" problem!
3.1.0-0:
First release for Huawei Honor 3C (h30u10)
Built with omnirom android-5.1 tree
Prebuilt kernel: EU B306 (3.4.67)
Screenshots: See the DevDB Screenshots page or click here.
Credits:
iamnotstanley
codelover
carliv for his bootimg module
MSF-Jarvis for his initial device tree
TeamWin team
omnirom team
XDA:DevDB Information
TWRP for Huawei Honor 3C, Device Specific App for the Honor 3C
Contributors
iamnotstanley, codelover, carliv, MSF-Jarvis, TeamWin team & omnirom team
Source Code: https://github.com/iamnotstanley/android_device_huawei_h30u10/tree/android-5.1
Version Information
Status: Abandoned
Current Beta Version: 3.1.1-0
Beta Release Date: 2017-05-13
Created 2017-04-01
Last Updated 2018-01-29
Reserved
Nice woork bro
why did not you patch it bro for img files flashing??
Can you Send Me sources
hassanjavaid8181 said:
Nice woork bro
why did not you patch it bro for img files flashing??
Can you Send Me sources
Click to expand...
Click to collapse
Thanks.
I'm working on the image flashing fix, but I'm building from source code and nearly scratch, and now I finding the cause of the problem. I'll fix it as soon as I can.
My source code (TWRP device tree) is in the post: https://github.com/iamnotstanley/android_device_huawei_h30u10
iamnotstanley said:
Thanks.
I'm working on the image flashing fix, but I'm building from source code and nearly scratch, and now I finding the cause of the problem. I'll fix it as soon as I can.
My source code (TWRP device tree) is in the post: https://github.com/iamnotstanley/android_device_huawei_h30u10
Click to expand...
Click to collapse
really appreciate your efforts:good:
good luck
Bro can we flash magisk by this version.
mnumaher said:
Bro can we flash magisk by this version.
Click to expand...
Click to collapse
If Magisk doesn't work in the older or other recoveries, it won't work in this recovery.
I think, because Magisk modify the boot image and MT6582 phones has a boot image with a special MTK header, and I think Magisk currently doesn't support this format. (Like the "new" systemless SuperSU.)
Thanks bro bringing twrp 3x to our device!!
I'm hoping you keep maintain this project as well till reach bugless
iamnotstanley said:
If Magisk doesn't work in the older or other recoveries, it won't work in this recovery.
I think, because Magisk modify the boot image and MT6582 phones has a boot image with a special MTK header, and I think Magisk currently doesn't support this format. (Like the "new" systemless SuperSU.)
Click to expand...
Click to collapse
Thanks.
Is touch working correctly in this version?
mnumaher said:
Thanks.
Is touch working correctly in this version?
Click to expand...
Click to collapse
For me, yes. This version has B306 kernel. If your phone's touch is working on B306, it'll work, but it's not, you will need to change kernel. You can try this first, but if isn't working, tell me which kernel has working touch for your phone and I'll make a version for that.
Kernels: https://forum.xda-developers.com/showpost.php?p=60721740&postcount=861
Rayquaza said:
Thanks bro bringing twrp 3x to our device!!
I'm hoping you keep maintain this project as well till reach bugless
Click to expand...
Click to collapse
Thanks for your support. I'll maintain this project while I have this phone. I'm trying to fix the img flash issue, but I think I need help with it.
iamnotstanley said:
For me, yes. This version has B306 kernel. If your phone's touch is working on B306, it'll work, but it's not, you will need to change kernel. You can try this first, but if isn't working, tell me which kernel has working touch for your phone and I'll make a version for that.
Kernels: https://forum.xda-developers.com/showpost.php?p=60721740&postcount=861
Thanks for your support. I'll maintain this project while I have this phone. I'm trying to fix the img flash issue, but I think I need help with it.
Click to expand...
Click to collapse
Ty bro it's working absolutely fine.
When we will be able to flash img.
mnumaher said:
Ty bro it's working absolutely fine.
When we will be able to flash img.
Click to expand...
Click to collapse
I'm working on it, but I think I need help to fix that. I hope maybe somebody can help me.
working fine cheers!
iamnotstanley said:
I'm working on it, but I think I need help to fix that. I hope maybe somebody can help me.
Click to expand...
Click to collapse
hi and great work, thanks for that
codelover maybe have a patch for that, past time he say i forget it, but can help you to know how solve that
Hi @iamnotstanley, to answer your question:
If i recall correctly i did explained about the problem in my thread earlier - the problem lies on 3C KK kernels. (MTK variant only)
H30-U10 stock KK kernels do not permit writing to the boot partition (/dev/bootimg) directly, the partition is mounted as read only.
Interestingly, there are some ported recoveries out there that doesn't work, and user doesn't even know about it. (eg: ROM appeared to be flashed successfuly but failed to boot because boot.img didn't get through, missing assert() to stop)
If you find a working H30-U10 recovery that can write to boot for 3C, it's likely using JB kernel or KK kernel from other 6582 compatible KK kernel, not sure if someone has compiled a fully working 3C kernel.
With JB kernel, you will be missing SELinux & some other features, while KK kernel from other device is dangerous IMHO, unless you are 100% sure it's compatible, sometimes i wonder whether those permanently bricked 3C with partition error were using these 'patched' recoveries...
My TWRP 2.8.6.0 has been customized to deal with this, i wrote a few C custom functions for twrp, it works like this;
1) read the partition table while flashing, loop through until you find the details for target partition that you need to write.
2) calculate the size and offset to write (you will need to convert the hex to int, then some math again to get the bs, skip, etc value for dd)
3) use 'dd' to write directly to mmcblock0, instead of C fwrite to the specific built-in partition mount point, eg: /dev/bootimg
Wish i could help more, unfortunately i don't have 3C data with me anymore (hdd crashed), and my work is killing me.
Good luck with that!
codelover said:
Hi @iamnotstanley, to answer your question:
...
Click to expand...
Click to collapse
Hi!
Thanks for your answer, I really appreciate your help.
So the problem is mainly in the kernel. I don't think I can fix this, but I'll try after my exams.
TWRP updated to 3.1.1-0
Hello guys!
I updated the TWRP to 3.1.1-0 yesterday. Unfortunately it still have the image flash issue. If you're interested you can download from the DevDB Downloads page or the Github mirror.
Huawei Honor 3C H30-U10
Hello guys
I m new on this site and want to know about my huawei honor 3c h30-u10
I want to root and install TWRP custom recovery in my cell without PC. .
I am using EMUI 3 and android ver 4.4.2 whereas build number is B310
Please any one give me detail with images.
Thanx in advance
SHBhatti said:
Hello guys
I m new on this site and want to know about my huawei honor 3c h30-u10
I want to root and install TWRP custom recovery in my cell without PC. .
I am using EMUI 3 and android ver 4.4.2 whereas build number is B310
Please any one give me detail with images.
Thanx in advance
Click to expand...
Click to collapse
Try rooting with root applications such as Baidu root and etc.
TamaziAce said:
Try rooting with root applications such as Baidu root and etc.
Click to expand...
Click to collapse
I was Try to root with king root, king root said that your device is rooted successfully but root checker said no root???? what should i do now..?
This tool/app will allow any number of ROMs to be installed at the same time. It works by patching the secondary ROM's installation scripts and boot image to load the ROM files from an alternate location (/system/multiboot, /cache/multiboot, and /data/multiboot). Because of the way this is implemented, no changes to the primary ROM are necessary
Donators
A huge thanks goes out to all of the donators for supporting this project! I if forgot to add you (and you want to be added), please send me a quick PM.
See all of our supporters here: https://gist.github.com/chenxiaolong/3f3fb485cbd0cb77c4281941433ec54d
It patches...
Custom kernels for dual boot support
ROMs so that they can be installed as secondary
Google Apps packages for AOSP-based ROMs
SuperSU so that it can be used in the secondary ROM
NOTE: If you want to dualboot an EUI ROM, I highly recommend installing EUI as the primary ROM.
How to use the patcher
Android
Download the patcher apk and run it. Tap "Patch Zip File" from the navigation drawer and choose the file you want to patch.
Windows (GUI)
Double click DualBootPatcher.exe and choose the file you want to patch.
--------
After patching the zip file, a new file, like some_rom_dual.zip file will be created. For example, patching ktoonsez's
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013.zip
would create a new
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013_dual.zip
Instructions for dual booting
Before doing anything, download the Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Dual: Dual/Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
Extsd-slots: There can be an unlimited number of extsd slots. These install to the external SD card, which is useful as it keeps the ROMs off of the internal storage. Note that the ROM's data files are still stored on the data partition.
With that said, let's get to the "how to"!
First, boot into your primary ROM and install the Dual Boot Patcher app
Open the app and go to "Roms" in the navigation drawer. It will ask if you want to set the kernel. Make sure that you do.
Go to "Patch zip file" in the navigation drawer and patch the ROM or zip you want to install. You can select one of the installation locations described above.
There are two ways of flashing the patched zip file. You can either flash it normally from recovery or flash it using the in-app flashing feature. Both methods are explained below.
Flashing from recovery
To flash from recovery, just flash the patched zip file like you would for any other zip. Nice and simple.
In-app flashing
To use in-app flashing, go to "Roms" in the navigation drawer, tap the floating button on the bottom right, and add the zips you want to install. You can queue multiple zips and they will all be flashed in one go. Once you've added all the zips you want to flash, click the check mark in the action bar and they will be flashed right away.
A normal backup from recovery will backup every ROM. If you would like to back up ROMs individually, please see @rlorange's awesome tool: http://forum.xda-developers.com/showthread.php?t=2491299
How do I...?
Switch the ROM if something doesn't work properly?
You can flash the DualBootUtilities zip from recovery. It will provide a menu interface that allows switching to the various ROMs.
If you have TWRP, you can also switch manually by tapping Install -> Images (bottom right) -> Go to /sdcard/MultiBoot/[Your ROM]/ -> flash boot.img.
Wipe /cache, /data, /system, or dalvik-cache?
The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".
Alternatively, flash the DualBootUtilities zip from recovery, which will also allow you to wipe a ROM.
NOTE: Don't use the recovery's built-in wiping abilities as that may delete non-primary ROMs!
Update the primary ROM?
Patch the zip for primary and flash it. The "primary" installation target is designed so that other ROMs won't be affected when you want to flash something for the primary ROM.
Update a non-primary ROM?
Patch and flash the zip exactly like how you did it the first time.
Flash a mod or custom kernel for the primary ROM?
Patch it for primary before flashing. If the zip does not wipe /cache, it is also safe to flash it directly.
Flash a mod or custom kernel for a non-primary ROM?
Just patch and flash it
Downloads:
[LINK] Dual Boot Patcher (Snapshots) and DualBootUtilities recovery zip
Donations:
Donations are not required, but are greatly appreciated Donators will have their names listed in a nice big font on this post and will also be listed in the README file of the patcher.
Source code:
DualBootPatcher: https://github.com/chenxiaolong/DualBootPatcher
Build instructions: https://github.com/chenxiaolong/DualBootPatcher/tree/master/docs
Please note, any bugs regarding app itself can be created over at https://github.com/chenxiaolong/DualBootPatcher/issues
Any other device-specific stuff can be asked over here itself.
XDA:DevDB Information
Dual Boot Patcher, Tool/Utility for the LeEco Le 1S
Contributors
chenxiaolong, DroidThug, https://github.com/chenxiaolong/DualBootPatcher/graphs/contributors
Source Code: https://github.com/chenxiaolong/DualBootPatcher
Version Information
Status: Snapshot
Current Beta Version: 9.2.0.r25.g0638efb
Beta Release Date: 2017-04-11
Created 2017-04-11
Last Updated 2017-04-11
FAQ
What does this do:
It allows you to multiboot between ROMs
What does it require:
It requires an unlocked bootloader, and root access
I have problems regarding this app:
1. Post the MultiBoot.log from your internal storage
2. Describe the problems with details such as which ROM, Kernel etc, and which variant of device you own (e.g x501, x507 etc.)
Does it support VoLTE:
This is not related to the tool. Do not ask for it
Help! I hardbricked/softbricked my device:
Sure, just describe what you did exactly
___ MORE TO COME
Any builds from and after 9.2.0.r25.g0638efb dated Mon, 10 Apr 2017 timed 19:57:27 should be okay to use for Le 1S
Can you make video how to install and run this app
sumitgp said:
Can you make video how to install and run this app
Click to expand...
Click to collapse
There are some out in youtube. But they are kinda outdated. Maybe someone will make it in the near future
DroidThug said:
There are some out in youtube. But they are kinda outdated. Maybe someone will make it in the near future
Click to expand...
Click to collapse
Your welcome bro
And ur contribution marvelous
Just keep going we are with u
Love u bhai thanks
is it work on LETV Le 1s x507
thanks for app
Iam asking because I dont understand LeEco 1S Products
Because LeEco 1s is X509
LETV 1S is x507
Is it also works on LETV Le 1s x507? please
fire3k said:
thanks for app
Iam asking because I dont understand LeEco 1S Products
Because LeEco 1s is X509
LETV 1S is x507
Is it also works on LETV Le 1s x507? please
Click to expand...
Click to collapse
Yes it work on le 1s x507
sumitgp said:
Yes it work on le 1s x507
Click to expand...
Click to collapse
Thnaku very much
then I'll try
fire3k said:
Thnaku very much
then I'll try
Click to expand...
Click to collapse
Thanku Very Much
I installed DualBootPatcher in My Le1S x507
and installed anlogside EUI, LineageOS 14.1 and Resurrection Remix 5.8.2 .
and they both working fine and installed gapps in both ROMS.
But 1 problem: that I installed SuperSu in LineageOS 14.1 and its working fine but when I try to install Supersu in Resurrection Remix 5.8.2, it installed perfectly there is no errors but when I open SuperSu app in Resurrection Remix 5.8.2 , It said that su binaries not installed
then I try to install Magisk12 in Resurrection Remix 5.8.2 and it gives some error.Please Giveme some Suggetion how to install magisk
Note: before install magisk, I already Patched it for RR 5.8.2
fire3k said:
Thanku Very Much
I installed DualBootPatcher in My Le1S x507
and installed anlogside EUI, LineageOS 14.1 and Resurrection Remix 5.8.2 .
and they both working fine and installed gapps in both ROMS.
But 1 problem: that I installed SuperSu in LineageOS 14.1 and its working fine but when I try to install Supersu in Resurrection Remix 5.8.2, it installed perfectly there is no errors but when I open SuperSu app in Resurrection Remix 5.8.2 , It said that su binaries not installed
then I try to install Magisk12 in Resurrection Remix 5.8.2 and it gives some error.Please Giveme some Suggetion how to install magisk
Note: before install magisk, I already Patched it for RR 5.8.2
Click to expand...
Click to collapse
Bhai check devloper option if there is any setting for root
If this will not work then try to share apps (super su app)
If above mentioned methods not work then try isu (higher version) of super su u can found it on los site
Thanks and warm regards
sumitgp said:
Bhai check devloper option if there is any setting for root
If this will not work then try to share apps (super su app)
If above mentioned methods not work then try isu (higher version) of super su u can found it on los site
Thanks and warm regards
Click to expand...
Click to collapse
Thanks for sugestion
but there is no option in Setting or devoloper option in Resurrection Remix 5.8.2 . only setting available in Magisk manager but it displays message that there is no root in system. Also tried chainfire Supersu. installs SuperSu App and when I tried to open it displays that There is no root binaries. Please help.
root is functioning in Resurrection Remix 5.8.2, when I install ROM without Dual Boot Patcher. but Only installs One ROM at a time no multiboot. Please any suggestion?
Thanks For Dual Boot Patcher
Atlast Solved
First I Flashed Chainfire SuperSu, then reboot then check root , it failed, and then I reboot and flash Magisk 12 and reboot. This Time All Ok Root Succeded
thanks for the updates!
If any one have le 1s related problem and solution or any one want to try new rom or kernal asap then all of u are welcome in our group on telegram so plz join with us
Requriemt
1. Download telegram from play store
2. Just click below link
https://telegram.me/LeSuperGroup
Thanks all of u
error
it shows error while booting 2nd rom
pravesh46 said:
it shows error while booting 2nd rom
Click to expand...
Click to collapse
What error? Be specific or give logs-,-
'have to try this! Thanks.
But, could this by any way interfer or get problem with F2FS formatted partitions (data,cache) ?
I'm also having some errors while installing the secondary rom...like extracting system errors
Hi! my Le1S gone in bootloop. Is there any solution to boot into the Primary ROM (i.e. eUI) via twrp? I have installed dual boot patcher & made eui as primary rom, lineage as secondary rom in "rrnougat" data slot & resurrection remix as secondary rom in " rrnougat2 " data slot.
From the past 2 weeks, I am using resurrection remix rom & sometimes eui. Today, I was on rr & my phone was hanging. So, I simply just restarted it & then, it gone in bootloop.
So, canI boot into my primary eui rom via twrp?, as dual boot patcher app cannot be accessed. Please help.
iamkamlesh said:
Hi! my Le1S gone in bootloop. Is there any solution to boot into the Primary ROM (i.e. eUI) via twrp? I have installed dual boot patcher & made eui as primary rom, lineage as secondary rom in "rrnougat" data slot & resurrection remix as secondary rom in " rrnougat2 " data slot.
From the past 2 weeks, I am using resurrection remix rom & sometimes eui. Today, I was on rr & my phone was hanging. So, I simply just restarted it & then, it gone in bootloop.
So, canI boot into my primary eui rom via twrp?, as dual boot patcher app cannot be accessed. Please help.
Click to expand...
Click to collapse
You can switch to other rom using dualbootutilities.zip. Just flash the zip . Then select ROM u want to switch & then select switch to..
Hello to everyone!
Here is a new Grass kernel line, which work with Kernel SU on POCO M3 (probably all chime).
It provides systemless root access on a kernel level for chosen apps only. No root access visible in system - nothing to hide.
Installation:
If you have magisk - flash uninstall.zip in recovery; then flash stock boot.img from your ROM; last flash grass-kernel.zip.
Manager run from apk file.
If you want back magisk with it's modules, you can install it from magisk.apk, grant root access from KernelSU manager, than you can patch boot via direct install (recommended). After reboot you can add your favorite modules like usually in Magisk.
The kernels are in next post.
Don't forget to change extension (apk->zip)!
Update from 19.05:
So, kernels are here:
Change extension from .apk to .zip, flash it in recovery and enjoy!
[email protected] is the latest one.
Will upload here one more time kernel for juice/chime and latest KernelSU apk:
Latest version of Grass kernel:
Optimised very good and working with 0.6.0 app. ver.
Also latest zygisk for kernel SU:
Version 10999:
Do u mean magisk module can co exist along with kernelsu. I mean i want root with KernelSu+magisk modules
Exactly. Root from KSU, modules from Magisk.
tariqa said:
Exactly. Root from KSU, modules from Magisk.
Click to expand...
Click to collapse
I'm wondering about root detection... You have double root(KSU&MagiskSU)...
Which one controls the root actually ? KSU has the better prevention from root detection but MagiskSU hasn't. If MagiskSU controls the root, it seems not to be a good idea ...
Kris Chen said:
I'm wondering about root detection... You have double root(KSU&MagiskSU)...
Which one controls the root actually ? KSU has the better prevention from root detection but MagiskSU hasn't. If MagiskSU controls the root, it seems not to be a good idea ...
Click to expand...
Click to collapse
Root is controlled by KSU.
Hello
Is this kernel for miui or Aosp Roms ? Please specify , and also mention andriod version Supported by this Kernel