I re-did my kernel and all is well except it breaks both CM root and SU root. Where would be a good place to start looking in source?
Nexus 6, Marshmallow.
apophis9283 said:
I re-did my kernel and all is well except it breaks both CM root and SU root...
Click to expand...
Click to collapse
Flash SU as the last from Twrp-recovery.
NLBeev said:
Flash SU as the last from Twrp-recovery.
Click to expand...
Click to collapse
Flashing supersu does nothing it refuses to run
apophis9283 said:
Flashing supersu does nothing it refuses to run
Click to expand...
Click to collapse
CM has an option to enable or disable root. enable it. i really do dislike CM.
simms22 said:
CM has an option to enable or disable root. enable it. i really do dislike CM.
Click to expand...
Click to collapse
Im pretty sure its gonna be an anykernel issue where my ramdisk replaces the ROMs
apophis9283 said:
Im pretty sure its gonna be an anykernel issue where my ramdisk replaces the ROMs
Click to expand...
Click to collapse
nope, considering any kernel that works on aosp should also work on CM. anyways, you cant lise root by flashing a kernel. simce root is in sysyem, beside systemless root. and kernels dont touch your system.
simms22 said:
nope, considering any kernel that works on aosp should also work on CM. anyways, you cant lise root by flashing a kernel. simce root is in sysyem, beside systemless root. and kernels dont touch your system.
Click to expand...
Click to collapse
I cant get root on any ROM. AOSP or CM based. Now if I flash my old kernel it runs fine. On the new "rebased" kernel root is broken. Both SuperSU and CM root
apophis9283 said:
I cant get root on any ROM. AOSP or CM based. Now if I flash my old kernel it runs fine. On the new "rebased" kernel root is broken. Both SuperSU and CM root
Click to expand...
Click to collapse
now this might help me, if you cant get root on any rom, that it is a problem that you are doing yourself.. which version of supersu are you using?
simms22 said:
now this might help me, if you cant get root on any rom, that it is a problem that you are doing yourself.. which version of supersu are you using?
Click to expand...
Click to collapse
RR ROM uses CM root. Although Ive tried SuperSU and it just doesnt respond
apophis9283 said:
RR ROM uses CM root. Although Ive tried SuperSU and it just doesnt respond
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3059493/
This is a prerooted lite stock rom with no issues.
When the info of @simms22 doesn't solve the root issue; give it a try.
RR rom is pre rooted as well. Ive had people test it on other roms still got snake eyes. Must be something i missed
apophis9283 said:
RR ROM uses CM root. Although Ive tried SuperSU and it just doesnt respond
Click to expand...
Click to collapse
try supersu 2.74 BETA-SuperSU-v2.74-2-20160519174328.zip
I think the issue is why its not working as it should. Pre rebase it works fine. Im missing something i just dont know what
Edit: if I knew what files could effect root I would have a place to start
apophis9283 said:
RR rom is pre rooted as well. Ive had people test it on other roms still got snake eyes. Must be something i missed
Click to expand...
Click to collapse
Have you read/searched about bump scripts.
http://forum.xda-developers.com/showthread.php?p=59907588/
Related
Hi, i have root my phone, however i found that, whatever i changed thing in the build.prop, it turn to original after a reboot, do i have to do s-off to get permission of changing things in the build.prop?
karnavont said:
Hi, i have root my phone, however i found that, whatever i changed thing in the build.prop, it turn to original after a reboot, do i have to do s-off to get permission of changing things in the build.prop?
Click to expand...
Click to collapse
It's not a S-Off problem. I had that on stock ROM as well. which ROM are you using/intending to use?
karnavont said:
Hi, i have root my phone, however i found that, whatever i changed thing in the build.prop, it turn to original after a reboot, do i have to do s-off to get permission of changing things in the build.prop?
Click to expand...
Click to collapse
Flash a new kernel.
The stock kernel has protection against system modifications.
I was getting random reboots every time certain apps tried to modify /system.
Not an issue for me since flashing ElementalX kernel
OllieD said:
Flash a new kernel.
The stock kernel has protection against system modifications.
I was getting random reboots every time certain apps tried to modify /system.
Not an issue for me since flashing ElementalX kernel
Click to expand...
Click to collapse
I'm using ARHD 12.2 with stock kernel, and can do changes to build.prop with ES Explorer (root) just fine
nkk71 said:
I'm using ARHD 12.2 with stock kernel, and can do changes to build.prop with ES Explorer (root) just fine
Click to expand...
Click to collapse
Doesn't ARHD come with its own kernel?
OllieD said:
Doesn't ARHD come with its own kernel?
Click to expand...
Click to collapse
Yes, but it's supposed to be completely stock
nkk71 said:
Yes, but it's supposed to be completely stock
Click to expand...
Click to collapse
I think its just based on stock with a couple of tweaks.
OllieD said:
I think its just based on stock with a couple of tweaks.
Click to expand...
Click to collapse
Could be, dont really know
ARHD is the stock kernel.
AllAboutTheCore said:
ARHD is the stock kernel.
Click to expand...
Click to collapse
its not 100% stock.
It lists in its features:
"Unsecured boot.img"
boot.img is the kernel and in order to disable the security they would have to alter the kernel source.
I seem to remember that mike_1986 credits flar2 (in Aroma setup ) for his mod regarding write protection (disabled)
Sent from my HTC One using xda app-developers app
I have arhd GPe 3.2 with elementalx kernel, but never work on any kind of rom
Sent from my HTC One using Tapatalk 4
Hi Advance Users
here is my tutorial
Requirements:
1.CWM v8 (v9 is too buggy cant install anything) https://www.androidfilehost.com/?fid=23269279319202183
2.UPDATED ROOT :http://download.chainfire.eu/376/SuperSU/UPDATE-SuperSU-v1.89.zip
3.Working CWM or any recovery
Flash Leaked ROM
Flash Root
Then Flash CWM v8
Turn off
Flash kernel from the leaked rom zip via fastboot
Reboot!!
Then cheers!!! your phone is rooted with cwm installed
Dont Forget to Give "Thanks"
i see the leaked Rom has no CWM installed.
so how could i flash the ROOT zip ??
im stuck, Jai
Use a kernel with cwm already, such nk or cm based. Then directly flash JB kernel afterwards. But flashing root and cwm before booting the room is more convenient as op instructed. Great.
Sent from my LT25i using XDA Premium 4 mobile app
ydaud said:
Use a kernel with cwm already, such nk or cm based. Then directly flash JB kernel afterwards. But flashing root and cwm before booting the room is more convenient as op instructed. Great.
Sent from my LT25i using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank man! Its worked
its very useful
JyRo said:
Flash kernel from the leaked rom zip via fastboot
Click to expand...
Click to collapse
You don't have to do this, since the ROM's zip flashes the kernel too
paxy97 said:
You don't have to do this, since the ROM's zip flashes the kernel too
Click to expand...
Click to collapse
Yes...but not any kernel wont work with 4.3 version.
ok so i tried this 10000 times with your JyrROM version of the ROM and it just wouldnt work...
is there no way to root that ROM???
doenen said:
ok so i tried this 10000 times with your JyrROM version of the ROM and it just wouldnt work...
is there no way to root that ROM???
Click to expand...
Click to collapse
but mine worked fine. what I did is flash the ROM(JyROM), flashed SuperSU v1.91 and it is done!
shadowhunter20 said:
but mine worked fine. what I did is flash the ROM(JyROM), flashed SuperSU v1.91 and it is done!
Click to expand...
Click to collapse
After this, do u have working super SU and CWM!?!?!?!?!?!
doenen said:
After this, do u have working super SU and CWM!?!?!?!?!?!
Click to expand...
Click to collapse
Super SU is working fine but since JyROM don't have CWM in it, I just installed CWM again, I installed the v6 of CWM..
shadowhunter20 said:
Super SU is working fine but since JyROM don't have CWM in it, I just installed CWM again, I installed the v6 of CWM..
Click to expand...
Click to collapse
yeah...well it didnt work that way for me and i think i will wait till official JB 4.3 is out. i hope jyro will make another version of his ROM i really liked the strong "debloation" and the opimization for battery life...
root works but i can't use xposed it's impossible to reboot and install it...
francescohtc said:
root works but i can't use xposed it's impossible to reboot and install it...
Click to expand...
Click to collapse
You can use this for xposed.
http://forum.xda-developers.com/showthread.php?t=
Pangkoy08 said:
You can use this for xposed.
http://forum.xda-developers.com/showthread.php?t=
Click to expand...
Click to collapse
link is not valid... :crying:
EDIT:
Solved installing this: http://forum.xda-developers.com/showpost.php?p=48484642&postcount=6846
Here's the 26A Stock, Rooted, Debloated ROM.
Full ROM was not possible as it would not flash. Was too big.
You need to be on a custom recovery to flash this.
Only tested being on 24A with Freedom Tools to get custom recovery.
Used 24A kernel to get this to boot thank to dr87.
Dev's feel free to use this to get a working kernel that activates Knock-ON. Just credit. Thanks
Download:
https://mega.co.nz/#!sMkm2SCb!iROSBS_IPo-iSDNCfxzG9Y0Tb0EysVoDOGKPRKy-_TU
KNOCK ON-CODE FIX:
Use Dorimanx's kernel to enable knock code:
Flash from recovery: This works even though it says no know code on file. I tested....
http://dorimanx.shine.sk/LG/VS980/K...Code-KK-[15-10]-[17-09]-LG-VS980-PWR-CORE.zip
26A, the 25b is already old...
Jimi Mack said:
26A, the 25b is already old...
Click to expand...
Click to collapse
Yea, Verizon must have caught a bad bug and patched it right away!! lol
This is a very rare event!!!!
Unheard of actually. It must've been really bad.
Looks like 4.4.4
For your reading pleasure:
http://www.mylgphones.com/verizon-w...d-4-4-4-kitkat-volte-support-and-bug-fix.html
Will the VoLTE work on this rom.
wr442 said:
Will the VoLTE work on this rom.
Click to expand...
Click to collapse
Not sure. Might need 26A kernel. Using 24 kernel to boot.
That article said 4.4.4?
Its not. Have the official update on work phone. Still 4.4.2
Mightycaptain said:
Its not. Have the official update on work phone. Still 4.4.2
Click to expand...
Click to collapse
Dang got all excited for nothing. ? Thanks for verifying
gorm said:
Dang got all excited for nothing. ? Thanks for verifying
Click to expand...
Click to collapse
Just curious what is missing from 4.4.4?
Sent from my VS980 4G using Tapatalk
i have knock on on 26A :silly:
updated with this tut
http://forum.xda-developers.com/showthread.php?p=54761453#post54761453
read from: http://www.mylgphones.com/verizon-w...d-4-4-4-kitkat-volte-support-and-bug-fix.html
4.4.4 kitkat and Advance Calling 1.0 features via VoLTE are responsible for the size this large
Yeah, I have knock on also when I flash Dorimanx 7.7 with "No Knock Code".
My baseband still says 25B though, but my software version is 26A.
Everything works otherwise. Thank you MicroMod--saving me from KDZ back to 24A to take OTA
Good to see you around still Micro. Ill play with this rom over the weekend.
I just upgraded to 26A, baseband, kernel, etc. through the "System Upgrade" in Settings, and made a debloat zip (flashed in twrp) for myself to remove the bloat. Knock-on works fine on 26A kernel. It's much quicker than flashing a whole Rom.
bouchigo said:
I just upgraded to 26A, baseband, kernel, etc. through the "System Upgrade" in Settings, and made a debloat zip (flashed in twrp) for myself to remove the bloat. Knock-on works fine on 26A kernel. It's much quicker than flashing a whole Rom.
Click to expand...
Click to collapse
Share? :good:
HueyT said:
Share? :good:
Click to expand...
Click to collapse
You might want to check the udpater script and remove some of the lines...I have it remove all the GApps because they can be downloaded from the Play Store, plus I don't like GApps residing in /system; it's just a personal preference.
Debloater: http://www.mediafire.com/download/wbvsfwbjj444njb/Debloat_LG_G2_26A.zip
bouchigo said:
You might want to check the udpater script and remove some of the lines...I have it remove all the GApps because they can be downloaded from the Play Store, plus I don't like GApps residing in /system; it's just a personal preference.
Debloater: http://www.mediafire.com/download/wbvsfwbjj444njb/Debloat_LG_G2_26A.zip
Click to expand...
Click to collapse
Thanks, I mainly need/want the baseband so will do. :highfive:
bouchigo said:
I just upgraded to 26A, baseband, kernel, etc. through the "System Upgrade" in Settings, and made a debloat zip (flashed in twrp) for myself to remove the bloat. Knock-on works fine on 26A kernel. It's much quicker than flashing a whole Rom.
Click to expand...
Click to collapse
What ROM are you on?
Rooted N6 stock rom 6.0
I flashed the newest update of Franco Kernel only meant for 6.0.1 and now im in a boot loop.
please help!!! aaahhhhhh
Thanks in advance
nexus1ace said:
Rooted N6 stock rom 6.0
I flashed the newest update of Franco Kernel only meant for 6.0.1 and now im in a boot loop.
please help!!! aaahhhhhh
Thanks in advance
Click to expand...
Click to collapse
reflash your rom or push a 6.o kernel to your phone and flash it.
before you make anymore mods to your phone, you want to make a backup within twrp recovery, in case you end up like this. then you can always restore it.
nexus1ace said:
Rooted N6 stock rom 6.0
I flashed the newest update of Franco Kernel only meant for 6.0.1 and now im in a boot loop.
please help!!! aaahhhhhh
Thanks in advance
Click to expand...
Click to collapse
Its important to first flash the kernel and then the latest superSU.zip from here http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344.
gee2012 said:
Its important to first flash the kernel and then the latest superSU.zip from here http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344.
Click to expand...
Click to collapse
you do realize that when flashing kernels, that you dont have to reflash supersu(if you already have root)? :silly:
simms22 said:
you do realize that when flashing kernels, that you dont have to reflash supersu(if you already have root)? :silly:
Click to expand...
Click to collapse
I was (am) under the impression that after every kernel flash superSU had to be flashed too At least with 6.0.1.
gee2012 said:
I was (am) under the impression that after every kernel flash superSU had to be flashed too At least with 6.0.1.
Click to expand...
Click to collapse
well, im not on 6.0.1, im on 6.0, and i flashed a kernel yesterday without flashing supersu, and i still have root. in theory, on 6.0.1, it should still be the same, as your supersu doesnt get removed when you flash another kernel. but, im not perfect, so i guess i could be wrong when it comes to 6.0.1 :angel:
simms22 said:
well, im not on 6.0.1, im on 6.0, and i flashed a kernel yesterday without flashing supersu, and i still have root. in theory, on 6.0.1, it should still be the same, as your supersu doesnt get removed when you flash another kernel. but, im not perfect, so i guess i could be wrong when it comes to 6.0.1 :angel:
Click to expand...
Click to collapse
Thought i read it on Chainfire`s systemless root page, will look into it and post it here
BTW i could have missread.
Answered by @franciscofranco:
Quote:
Originally Posted by j4rp0
Should i flash the supersu zip always after a franco kernel update? Even if coming from systemless root?
Enviado desde mi Nexus 6 mediante Tapatalk
Yup.
gee2012 said:
Thought i read it on Chainfire`s systemless root page, will look into it and post it here
BTW i could have missread.
Click to expand...
Click to collapse
i havent even investigated any new info. i guess if there is something new, ill figure it out when the time comes.
maybe its about his new systemless root only? i still do it the old fashioned way.
If you have taken the soak test marshmallow update, can your phone pass safetynet? Mine can't even though the software status says official, qe 0/1.
I believe if your bootloader is unlocked, that's enough to trip it now:
https://www.reddit.com/r/Android/comments/587ss9/psa_android_safetynet_now_tripped_by_unlocking/
ski4404 said:
I believe if your bootloader is unlocked, that's enough to trip it now:
https://www.reddit.com/r/Android/comments/587ss9/psa_android_safetynet_now_tripped_by_unlocking/
Click to expand...
Click to collapse
But using isu, all of the CM 14.1 based custom roms pass safetynet.
TheSt33v said:
But using isu, all of the CM 14.1 based custom roms pass safetynet.
Click to expand...
Click to collapse
Because @bhb27 is very smart dev?
ChazzMatt said:
Because @bhb27 is very smart dev.
Click to expand...
Click to collapse
Yes he is, but if I remember correctly, even he said that there was nothing he could do about hiding an unlocked bootloader from safetynet. Isu only hides cm root.
Hmm. Looks like CM can pass safetynet because they patched dm-verity in the kernel. Uhhhgggg. Sooo...anyone want to make a custom kernel for the Verizon soak test that patches dm-verity?
TheSt33v said:
Hmm. Looks like CM can pass safetynet because they patched dm-verity in the kernel. Uhhhgggg. Sooo...anyone want to make a custom kernel for the Verizon soak test that patches dm-verity?
Click to expand...
Click to collapse
you may want to ask CF directly for that.
koftheworld said:
you may want to ask CF directly for that.
Click to expand...
Click to collapse
I don't think he is in the business of editing kernels.
TheSt33v said:
Hmm. Looks like CM can pass safetynet because they patched dm-verity in the kernel. Uhhhgggg. Sooo...anyone want to make a custom kernel for the Verizon soak test that patches dm-verity?
Click to expand...
Click to collapse
koftheworld said:
you may want to ask CF directly for that.
Click to expand...
Click to collapse
TheSt33v said:
I don't think he is in the business of editing kernels.
Click to expand...
Click to collapse
@bhb27 makes a kernel that will install on stock Motorola Marshmallow Brazil. Maybe his will also install on stock Verizon.
ChazzMatt said:
@bhb27 makes a kernel that will install on stock Motorola Marshmallow Brazil. Maybe his will also install on stock Verizon.
Click to expand...
Click to collapse
True. I'll give that a shot when I get home. It didn't allow the other stock roms to pass safetynet, but those other roms were modified, so maybe it'll work for this one.
TheSt33v said:
True. I'll give that a shot when I get home. It didn't allow the other stock roms to pass safetynet, but those other roms were modified, so maybe it'll work for this one.
Click to expand...
Click to collapse
Brazil stock just got some kind of update, and he's not yet changed the kernel to work with it. He will when he gets time. See this page. It's possible Verizon's version of 6.0.1 has the same changes. So, it may not work right now.
http://forum.xda-developers.com/moto-maxx/development/kernel-bhb27-kernel-t3207526/page129
this appears to be an answer but we dont have kernel source yet to patch it. https://github.com/sultanxda/androi...mmit/abc05b16bbd33521c2fffaf491c5657a94bfcfc5
quantum tao said:
this appears to be an answer but we dont have kernel source yet to patch it. https://github.com/sultanxda/androi...mmit/abc05b16bbd33521c2fffaf491c5657a94bfcfc5
Click to expand...
Click to collapse
That commit is from October. As far as I know, CM14.1 roms (at least RR. I haven't tried the others) only started failing safetynet recently. I know for a fact that I could pass safetynet on AOKP a few weeks ago.