Related
Hello guys, I open a Question and Answer Thread for all SuperKernel users, so even users under 10 posts can ask their questions here.
Below I added some basic Q&A stuff which here so hopefully it will answer most of your questions!
Q: How to get into Download Mode?
A: Power off your phone, than hold: home + volume down + power on button until you see the download mode.
Q: How to get into Recovery Mode?
A: Power off your phone, than hold: home + volume up + power on button until you see the recovery mode.
Q: I get verification failed at start up!?!? My phone is broken now?
A: Yes, you have to buy a new phone now. Just kidding You did not disable force encryption in TWRP (how to do so you will find below in how to decrypt your phone).
Q: I get FRP LOCK? WHYYYYYY???
A: Very simple answer, you did not enable OEM Unlock in developer options. Now you need to flash full rom with odin again and start from scratch. But don't forget to enable OEM Unlock this time!
Q: I got FC's and other Problems with the kernel, what to do?
A: Take a logcat for me, developers use to say: without a log, it never happened . A logcat can be grapped with a PC and ADB installed, simply type: adb logcat > log.txt while your phone is connected and the error is happening.
Q: What kind of logs can I provide to help you?
A: Logcat: This one is for general infos about FC's
DMESG: this is for kernel related things
Last_Kmsg: this can be used after a random reboot
Q: How to get logs?
A: 1. Connect your phone to your pc
2. Make sure you got usb debugging enabled
3. Install Minimal ADB tool
4. After install open it and type: adb logcat > logcat.txt, adb shell dmesg > dmesg.log, adb shell cat proc/last_kmsg kmsg.log
5. Send me the file you got
Q: Which devices are supported at the moment?
A: Current supported devices are: SM-G930F/FD/W8. All other exynos models can work but are UNTESTED
Q: Is this kernel working on Snapdragon 820 variants?
A: No, sadly not.
Q: Help, I never had a code and now after installing the rom my phone asks for a password??
A: Your device is still encrypted, on step 0 it tells you to be sure you're not. So, what do you need to to in case you are still encrypted:
1. Boot into TWRP
2. Select Wipe
3. Select wipe data
4. Then you manually need to type "yes" with the keyboard
5. Confirm the wipe (this will remove the encryption)
6. Reboot your recovery
Q: Is there a way to get rid of encryption which is simpler?
A: Not really, you could also wipe data with stock recovery but this is quite a big hassle so above method works better.
Q: On TWRP there is an error about /data mount, what to do?
A: Your device is encrypted, follow the above steps to get rid of your encryption.
Q: Synapse shows no UCI support!
A: Reflash kernel, a script of you may overwrite my synapse config
Q: I want to switch kernel, how?
A: Since we have systemless xposed and systemless supersu, we have patches in ramdisk of boot.img. This means you have to reflash xposed and supersu after every change of kernel!.
Q: I lost root after installing this rom. What to do?
A: All mods (like supersu, phh's root, xposed and magisk) are stored in /ramdisk of kernel boot.img. So if you flash this rom, and after this another kernel (Which has supersu included by default) you can not do much. You have to stick to the two kernels provided in rom. Also when switching kernel, you need to flash all related zips again after changing it. Last tip: Do not use magisk until you really need it for android pay!
Q: I got random reboots, heeelp!
A: This is most likely from a custom kernel, if you face random reboots please check if you have the latest kernel installed or switch back to the stock kernel included in the rom.
Q: My screen is kind of yellow/orange and the touchscreen doesn't work at all!
A: You have chosen the wrong kernel in aroma selection. Reflash the rom without any wipe selecting the right kernel version.
should i do Factory reset before upgrading my samsung galaxy s7 from Marshmallow to Nougat ??????
plz tell me
( in ur opinion which is better in performance and battery life ,,, M or N ??? )
ThnQ
Casanova887 said:
should i do Factory reset before upgrading my samsung galaxy s7 from Marshmallow to Nougat ??????
plz tell me
( in ur opinion which is better in performance and battery life ,,, M or N ??? )
ThnQ
Click to expand...
Click to collapse
Of course you should factory reset in such a major upgrade, about the MM or N, I think N is better but many people say the opposite, so it depends on your usage
can you use ANY of the open source stuff without tripping knox ?
as i see the open source kernel listed on many (mainly jrkruse) threads and how they are able to do small modifications to system files without tripping DM-Verity thus staying 'stock'
was opensource implemented in this accomplishment, or was it just lucky that TMO boot.img allows it ? (vulnerability if you will)
a budding dev, Mick ..
miniminus said:
can you use ANY of the open source stuff without tripping knox ?
as i see the open source kernel listed on many (mainly jrkruse) threads and how they are able to do small modifications to system files without tripping DM-Verity thus staying 'stock'
was opensource implemented in this accomplishment, or was it just lucky that TMO boot.img allows it ? (vulnerability if you will)
a budding dev, Mick ..
Click to expand...
Click to collapse
Not tripping dmverity is an easy thing, you simply don't compile it in the kernel and it can't do the check. Knox is something completly else. It's build into bootloader and you can't get around it if you want to install anything custom. As soon as something custom is flashed, an efuse chip is tripped and that can't be changed
Tkkg1994 said:
Not tripping dmverity is an easy thing, you simply don't compile it in the kernel and it can't do the check. Knox is something completly else. It's build into bootloader and you can't get around it if you want to install anything custom. As soon as something custom is flashed, an efuse chip is tripped and that can't be changed
Click to expand...
Click to collapse
first Thankyou for replying, seems hard to be able to speak to dev people for us budding devs...
so could this be used in conjunction with the stock boot.img to get around DM-Verity ?
or will that break the checksum check for the .img file overall ?
is this what jrkruse uses ? i know he lists the opensource kernel on his OP's...
or is/was that just a happy t-mobile boot.img signed error/vulnerability ?
(where dm-verity is switched on, but it seems to ignore basic system file change) ...
cheers again Mick
miniminus said:
first Thankyou for replying, seems hard to be able to speak to dev people for us budding devs...
so could this be used in conjunction with the stock boot.img to get around DM-Verity ?
or will that break the checksum check for the .img file overall ?
is this what jrkruse uses ? i know he lists the opensource kernel on his OP's...
or is/was that just a happy t-mobile boot.img signed error/vulnerability ?
(where dm-verity is switched on, but it seems to ignore basic system file change) ...
cheers again Mick
Click to expand...
Click to collapse
No problem, I'm here to help whenever I can.
I have no idea who are you talking about and who that jrkruse is and what kernel he made etc. Can you link me maybe?
Tkkg1994 said:
No problem, I'm here to help whenever I can.
I have no idea who are you talking about and who that jrkruse is and what kernel he made etc. Can you link me maybe?
Click to expand...
Click to collapse
its most appreciated.
yes heres one of his 'ROMS', but its based around the, i think, stock vulnerable boot.img...
https://forum.xda-developers.com/tmobile-s7-edge/development/rom-t3572739
https://forum.xda-developers.com/verizon-s7-edge/development/rom-t3569416
adaway example
https://forum.xda-developers.com/showpost.php?p=71331817&postcount=2
will give you some background info...
ive been trying to convert some stuff over to the s7active,
(which is basiclly same s7 snapdragon/qualcomm but with extra hardware buttons, bigger battery, in a armoured case)
At first i was just trying to get the GearVR goin on them, but many hours later, i feel its kernel locked ??? as NOTHING happens logcat wise when plugging them in...
but that lead me to debloating etc as i now could understand that...
so following his roms/debloat scripts, i tried to port it over.... MANY many hours later, as learning as i go, i find at the base of the mods is a tmomible boot.img, which seems to allow basic file changes in system, and doesnt trip dm-verity/bootloops..
so enables you to for example, from stock, flash engboot.img, which allow adb root, swop out host file for adaways one, reflash back the TMO boot.img, and it boots, and you keep stock, and saftynet etc etc
took me far longer than i wanna admit to reach that info, after many hours reading and messing with scripts etc thinking scripts was the culprit.
i think, i found a post that he says he just using the TMO img as it allows it.... but read so much now, and got lost in so many threads i cannot re-find which one it was in !!! (will try and find it now)
but after all, it HAS tought me alot along the way, as im now releasing a 'rom'
but wanted to understand it all abit more, and maybe even get back to my original quest !
been told that opensource kernels out for active (SM-G891a) but not able to find it anyhows..
oops sorry my long post !! Cheers Mick,,
EDIT
added adaway example as it shows the vulnerability off nicely
EDIT 2
well i was mistaken, its not a boot.img vulnerability...
from jrkruse ""It's not the boot.img it's the dm verity process of the cdma firmware when gsm firmware is flashed over the top of cdma firmware. That's why in every case you have to start on cdma firmware it doesn't have to be Verizon""
Hi every one, I am building my own kernel for galaxy s6 (nougat) with source code downloaded form opensource.samsung.com
Everything was fine until I flash my boot.img via odin.
After flashing, the phone reboot and this error appeared "Kernel is not seandroid enforcing"
I've done a lot of searching on google but all of them are just about to re-flash the stock kernel to fix this.
The thing I need to know is why did this error happend to my kernel and how to fix this error (by changing the code or anything else, not to flash the stock kernel).
If anyone experienced this case, please help me.
Thanks for reading my question. Your help will be very highly appreciated.
Thank you !
nguyen_vh said:
Hi every one, I am building my own kernel for galaxy s6 (nougat) with source code downloaded form opensource.samsung.com
Everything was fine until I flash my boot.img via odin.
After flashing, the phone reboot and this error appeared "Kernel is not seandroid enforcing"
I've done a lot of searching on google but all of them are just about to re-flash the stock kernel to fix this.
The thing I need to know is why did this error happend to my kernel and how to fix this error (by changing the code or anything else, not to flash the stock kernel).
If anyone experienced this case, please help me.
Thanks for reading my question. Your help will be very highly appreciated.
Thank you !
Click to expand...
Click to collapse
This is a common message on custom kernel, I have a s6 with custom mm rom and custom mm kernel, and I have that message come up, but my phone still boots up fine. Just a note you need to post in correct forum to get the right help, if you look in the general section there is actually a thread by a dev on how to create custom kernels, it's by the user thesickness, posting in there will get you some help.
It's just a warning, not an error.
sofir786 said:
This is a common message on custom kernel, I have a s6 with custom mm rom and custom mm kernel, and I have that message come up, but my phone still boots up fine. Just a note you need to post in correct forum to get the right help, if you look in the general section there is actually a thread by a dev on how to create custom kernels, it's by the user thesickness, posting in there will get you some help.
Click to expand...
Click to collapse
Thank you for moving my thread to the right box. In my case, the warning seandroid forcing appeared and also the phone could not boot. (nougat). I will read your recommended threads.
I have bled my heart out trying to make a ROM with SUPER R kitchen. Boot loop every time. I used stock MM tar. I want DeOdex/ZipAlign/Init.d support/deKNOX/SEpermissive. I'll debloat and Su/xposed on my own. I just for the life of me can not get a zip from Super R Kitchen to boot. Or even if no1 could make 1, but point me in the right direction, ID give hella thanks.
N915G
PS. My phone was purchased unlocked, so that's not the issue. Using TWRP 3.1.0 built for this model.
Here is my attempt at making my desired rom in zip format. It is not sogned (not enough ram). Its raw.img format. Doesnt include /data.
https://www.mediafire.com/download/aj33z92u189jvxp
Built with Super R Kitchen. All I got was bootloop no matter my set up, free linux version on Ubuntu.
Also, could i just turn off secure boot (dm-verity) via my build prop?
Is there a way to turn off knox without cooking a rom? I think i know how to get init.d activate via terminal .zip, seems to work for this phone. The test shows up in data but universal init.d apk still says my kernel doesnt support init.d.
Also could you change to SEpermissive using stock kernel?
If there is anyone, say something lol.
Here r screenshots of my phone info. Also will have link for stock .tar up in a few via Google Drive.
Stock Image (.tar format)
https://drive.google.com/file/d/0BxuJcdyzHiZ8aEg5YlFMaFBPMTQ/view?usp=drivesdk
Edit: This is the wrong stock image for my phone, maybe thats where my issues came from lol ill have new stock image in new thread once i have a wotking rom lol.
I tried to use a stockish rom made by someone else but it would bootloop, inless youbused like mickey kernel or emotion kernel, and i lost my screen off edge detection when i used it last. So i was trying to make my own. Ill end up buying super R kitchen for windows see if it does any better on a note edge MM Rom. If there any other suggestions im open to them. Thanks
Chris2thepher92 said:
I tried to use a stockish rom made by someone else but it would bootloop, inless youbused like mickey kernel or emotion kernel, and i lost my screen off edge detection when i used it last. So i was trying to make my own. Ill end up buying super R kitchen for windows see if it does any better on a note edge MM Rom. If there any other suggestions im open to them. Thanks
Click to expand...
Click to collapse
I can't think of anything to say except good luck and keep is posted.
The Radius Kid said:
I can't think of anything to say except good luck and keep is posted.
Click to expand...
Click to collapse
Edit: there will be a delay, i got a working rom to intall after cooking it, but low and behold i got the infamous contacts has stopped error. Recooking today.
Update: will have a a working rom up(2 versions, 1 debloat stock, 1 is what i run to the t).
Full details and a link to the new post will be linked with this post.
Ended up using a different kitchen/twrp.
Update: as of this morning I hard bricked my Note Edge, so until I can get the bootloader fixed, fingers crossed, this is on hold. I'm running a ZTE Zmax Pro ATM so...
https://forum.xda-developers.com/note-edge/general/unblock-img-4-n915g-t3678089
I have a working ROM for N915G, it's not DeOdex, but has Su,BB,Xposed,Init.d,su.d,sqlite,Multi-user,Dark UI mod, and Debloat(I'll upload debloat file so you can see what I took out)
Chris2thepher92 said:
Update: as of this morning I hard bricked my Note Edge, so until I can get the bootloader fixed, fingers crossed, this is on hold. I'm running a ZTE Zmax Pro ATM so...
https://forum.xda-developers.com/note-edge/general/unblock-img-4-n915g-t3678089
I have a working ROM for N915G, it's not DeOdex, but has Su,BB,Xposed,Init.d,su.d,sqlite,Multi-user,Dark UI mod, and Debloat(I'll upload debloat file so you can see what I took out)
Click to expand...
Click to collapse
Hope you get it fixed.
Good luck.
Good day everyone, just got my note pro WiFi version? Already rooted and has custom kernel civz, tablet feels slow so I'm planning on changing rom maybe lineageOS but I'm concerned about the procedure because I'm not sure where I'm standing with every change done to this device, any help is appreciated I just don't want to brick this device trying to flash a new rom.
Currently it's running stock rom 5.0.2, 3.4.39 civz kernel and knox 2.3, if someone could provide a step by step on what should I do or check in this device to be on the safe road id really appreciate it. Btw I don't even know what recovery I have or how do I access it.
Bump
honestly most samsung devices are the same so id suggest getting the full stock system and using odin to revert to stock, from there start by getting a custom recovery and seeing what else you need to set up your rom
someone correct me if im wrong
heres the page for official stock "images"
https://www.sammobile.com/firmwares/galaxy-note-pro/SM-P900/
xxjahasotoxx said:
honestly most samsung devices are the same so id suggest getting the full stock system and using odin to revert to stock, from there start by getting a custom recovery and seeing what else you need to set up your rom
someone correct me if im wrong
heres the page for official stock "images"
https://www.sammobile.com/firmwares/galaxy-note-pro/SM-P900/
Click to expand...
Click to collapse
someone told me that I just need to install twrp as it is and start flashing roms, dont know if this the best way to do it what do you think?
It could work just keep in mind that you don't know exactly what the previous owner did to it so if they installed a custom kernel you'll be stuck with that, could be a good thing could be a bad thing
You could always give it a shot and if it gives you problems go back to stock then TWRP then start rom-ing
Hey guys i got a short question..
I rootet my Galaxy s8+ because i got some issues and i thaught i could solve them with root. The Problems i had are gone now but i would like to go back to stock and get my security and functionality back. In my opinion i lose more then i get with root. Some things are unstable or crashing and the speaker sound with the rom i am running is just awful.
ok lets start with my request. I need some help going back to stock. i tried it with some guides but i am not shure if i have to change my kernel first oder something like this. For example if i Flash "PDA" with odin, i dont know if my kernel is in there or in another package. Another question is if i have to use firmware for switzerland to keep all things working (i am in switzerland). i know, that i may need the right modem but i dont know about the other things..
What i need is a step by step guide wich packages i have to flash and in wich order.. if someone is interested we could write in skype or somethin like this if somebody wants a small donation for his work.
Infos you may need:
Rooting method: Odin
Kernel: NX-R17
Basebrand: G955FXXU4CRI9
Bootloader: G955XXU4CRJ5
PDA: G955FXXU4CRJ5
CSC: G955FOXM4CRJ3
Rom: Renovate ice 14.1
recovery: Team Win recovery 3.2.3-2
a knox status app shows me tha my phone rootstatus is 0x0.. i thaught thats imposible?
by the way i dont know why the other guides to unroot didnt work for me, sorry. the only thing i know, is that Odin couldnt flash and i guess there was a kernel error message.