As the title says, why isn't my kernel changing?
I'm currently on Galaxy S7 (G930F) with Oreo-rom and TGP-Kernel, TWRP 3.2.1-1
When I try to flash another kernel, for instance Notorious Kernel or my own modified boot.img, the install is successful in TWRP, but when I look in settings it still says "TGP Kernel bla bla bla...".
Why is this happening, and how can I make my new kernel "stick"?
Any help is appreciated, thanks!
EDIT: I even made a custom cooked rom with a modified boot.img (both stock based), format data and made an advanced wipe including everything except OTG & SD.
AND TGP IS STILL PRESENT?!
Related
Hi, as XDA doesn't allow me to ask this neither on the Omega Thread and on Ktoonsez Thread of the S4 development, I'l have to ask it here untill I have 10 posts.
I have a i9505 Galaxy S4, (I had an S3, a Note II with Omega, and an S2) and installed Omega 5.0 through the way ::indie:: indicates on Omega's thread which is as follows:
Installation Instructions:
1. Backup all your app and data so you can restore them to Omega v5.0 (I use Titanium Backup)
2. Make a full wipe (Data, System, cache, dalvik Cache) from recovery then boot to download mode immediately and flash Stock I9505XXUBMEA with odin
Get the firmware from here.
Flashing stock XXUBMEA is needed to make wifi work. Many users reported that it took them many flashes with odin to make wifi work on stock firmware.
3. Make sure all are working ok with stock XXUBMEA firmware, check if wifi + LTE (if your provider supports LTE) are working ok
4. Flash TWRP Recovery with odin, get it from here
5. Boot to TWRP Recovery and flash Omega Rom.
Wipe data from recovery is not needed, wipe your data only if you want to.
6. If LTE is not working flash this zip: I9505_Enable_LTE.zip
Ok.
Everything working great!
But then I installed Katoonsez GREAT WONDERFULL Kernel, but the device got so hot, and I could observe throught KTweaks that my cores were allways ever online and the clocks weren't adjusting well.
This happened with every governor and scheduler.
Then I could install every Kernel including reintalling the rom with the original kernel afterwards that this happened. The only way to make it stop was going to recovery (TWM didn't helped, but CWM allowed me to format every folder like system folder) and only after formating everything, and installing XUAME2 stock ROM through Odin would make my phone not boot so warm again.
It happened several times and got me lots of flashings to dyscover the baove procedure to make the phone not get warm.
Once, it wokrd I don't know why, with Omega 3.1 and KT-SGS4-TW-JB-INTL-05-30-2013. Actually it had the same issues, but specifically with intelidemand it suddenly started to work fine for the first time, and was the best week I ahd with a phone ever!!!
Then yesterday I tried to update to Omega 5.0 and KT-SGS4-TW-JB-INTL-06-06-2013 and all the madness started again :crying:
I'm stuck in the loop and I simply don't know what in the process is making this happens. I tryed to flash in sevral different ways, but in every single way this happens.
I tried flashing the kernel in the same CWM session as I instal the ROM, I tryed doing separately, I tryed wiping wvwrything, I tried wiping only some things and not others, I tried fixing permissions and not fixing permissions after Kernel install (they recomend to fix permissions)...
Well, it is a nightmare!!! All I wish is to get my phone working as lovely as it was with Omega 3.1 again, but even installing the same files in the same way I did, I'm not geting it!
Please help!!!
BTW when I updated to KT-SGS4-TW-JB-INTL-06-05-2013 also on Omega 3.1 it was still working great.
Even on undervolted note 2 I never seen a Battery last longer! It was amazing! Then yesterday when trying to updadte to get HDR video on Omega 5.0 it all started again...
Wouldn't it make more sense for you to have asked this in the i9505 forum if you're using an i9505?
Sent from my SCH-I545 using Tapatalk 4 Beta
Last time I flashed my phone I used ODIN and a modded AT&T ICS stock rom. This time I used directions from the following site and when I boot to CM after flashing it goes through a process that says optimizing applications then reboots and hangs on the CM logo spiining which I'm assuming means it locking up during boot.
I changed recovery from odin to CWM before flashing which appears to work fine. I restored my backup I made with CWM after installing and my phone is working again. Any ideas what I'm doing wrong here or should I try a different ROM? Thanks.
AT&T Samsung I777
http://tech.gamotech.com/how-to-install-android-4-3-jelly-bean-on-att-samsung-galaxy-s2-i777/
@keeperofthecode,
The ROM is fine, it's the method that i question.
Once you're comfotably back to stock, this is the easiest way to get from stock to custom recovery on the i777:
Framaroot <-- tool to establish root-access to the device
Mobile Odin Lite(or pro) <-- tool that uses root-access to install...
Custom Kernel <-- a custom kernel (there are many available) installed primarily to provide cwm recovery, but are also commonly used to:
-install a different ROM
-provide additional functionality to the existing ROM
-backup your ROM install
-install a different kernel
-flash cleanup scripts
-and many many other things
The ROMs are usually packaged with their own kernels, so the kernel used above only remains in place until another ROM is flashed, which will overwrite the existing recovery with one specifically designed for the ROM flashed.
This guide will walk you through the steps, but read through the thread carefully to be sure that you understand everything before leaping.
-happy flashing
edit - it seems you already had root and cwm, so I'm not sure what went wrong. Before flashing the ROM, try a ROM cleaning script, or at least:
-factory reset
-format /system
Thanks. Reset and wiped then installed perfectly. UDMAN
I can't seem to be able to install a custom kernel on my s9+ G965F . It's the: https://forum.xda-developers.com/ga...lopment/kernel-elementalx-1-00-s9-s9-t3767753
The Aroma Installer of the Kernel gives the error:
''Installer Status: 7'' and ''set_perm:some changes failed''
I did successfully installed it (a few hours before) on a stock Rom from Samsung and worked very good (3800 and 9700on geekbench 4).But as the human nature is, I WANTED MORE: a Custom Rom (https://forum.xda-developers.com/ga...g96xf-fd-n-stock-rom-soldier9312-1-0-t3771346) .It flashed good (just some errors at the end) and rom worked good then I flashed the Elemental Kernel again and got ''Installer Status: 7'' and ''set_perm:some changes failed''.
Now the strange thing is, i restored the twrp backup i did of the stock firmware and then flashed Elemental Kernel again and now the same error ''Installer Status: 7'' and ''set_perm:some changes failed'' appears (even though half an hour before the exact same combination worked).
Note: Between Roms\Kernels I always format everything in twrp with ''yes'' and then also wipe system, date , internal storage , dalvik etc and then flash the oem patch fix with root, and the no-verity zip from jesec.
Note2: installing Busybox (from playstore) also didnt help ..Because in both Kernel install Log and Rom install Log there are some errors about busybox..
I've attached both Logs (from Kernel installation and Rom installation)
What am I doing wrong?
I asked this on the Kernel- and also on the Soldier Custom Rom -Threads and on both Threads they said it does work, lot of people use this combination. But that really doesn't help me..
I've been flashing every galaxy samsungs since s6, so I thought I knew everything(or at least enough) but it seems not..
I would be very grateful for some advice that helps me...:angel:
UPDATE:
LOOOOOOOLLLLLL I just re-downloaded the kernel and it works. Boots and cpu frequency at 2.89Ghz . funny cus the same zip on the sd card worked yersterday.. but only the first time..so its like the kernel zip BECAME corrupted in time on the sd card!!!
Mods can delete this thread now
Hi, i found my old gt 9100 galaxy s2 and i want to flash some roms on it or the original one back and working again, but twrp 2.3.2.3 is not letting me flash anything, it says unable to mount '/system, , if anyone could help me i ll appreciate it thanks?
KonC13 said:
Hi, i found my old gt 9100 galaxy s2 and i want to flash some roms on it or the original one back and working again, but twrp 2.3.2.3 is not letting me flash anything, it says unable to mount '/system, , if anyone could help me i ll appreciate it thanks[emoji16]
Click to expand...
Click to collapse
To flash roms like android 4.4.4 you need newer (kitkat compatible) twrp. Yours is outdated.
To flash latest roms you need also an isorec kernel and isorec twrp and you need to increase size of system- and data-partition (there are many threads how to do).
For stockrom you need odin to flash.
Sent from my [device_name] using XDA-Developers Legacy app
TriboDoP said:
To flash roms like android 4.4.4 you need newer (kitkat compatible) twrp. Yours is outdated.
To flash latest roms you need also an isorec kernel and isorec twrp and you need to increase size of system- and data-partition (there are many threads how to do).
For stockrom you need odin to flash.
Click to expand...
Click to collapse
I tried to flash isorec kernel from odin but it fails, and also whatever im trying to flash from twrp is says unable to mount system, and in the mount tab the system is unchecked and i cant check it!
KonC13 said:
I tried to flash isorec kernel from odin but it fails, and also whatever im trying to flash from twrp is says unable to mount system, and in the mount tab the system is unchecked and i cant check it!
Click to expand...
Click to collapse
No idea on which rom you are and what exactly you tried to flash.
So what i would do: using your twrp i would flash a kitkat-compatible custom recovery (cwm or twrp). Then boot straight this kk recovery (do not boot system) and make a clean flash of latest unofficial lineage 11 android 4.4.4 by grzwolf together with isorec twrp 3.1.xxx.zip by the.gangster (this rom has already isorec-kernel).
After that you could carry on with repartioning system and data and flashing nougat roms etc. (Having made a backup before doing all sorts of thing is of course adviced)
Sent from my [device_name] using XDA-Developers Legacy app
TriboDoP said:
No idea on which rom you are and what exactly you tried to flash.
So what i would do: using your twrp i would flash a kitkat-compatible custom recovery (cwm or twrp). Then boot straight this kk recovery (do not boot system) and make a clean flash of latest unofficial lineage 11 android 4.4.4 by grzwolf together with isorec twrp 3.1.xxx.zip by the.gangster (this rom has already isorec-kernel).
After that you could carry on with repartioning system and data and flashing nougat roms etc. (Having made a backup before doing all sorts of thing is of course adviced)
Click to expand...
Click to collapse
Thanks man you saved me!!!!!
Hi there,
Not sure what happened - I'm using my Tab S3 (SM-T820) for ages in the same (stable) configuration - rooted Stock, no changes/installations for months.
This morning it was in Odin/Download mode and I cannot boot into system.
I can get into recovery (TWRP), but I cannot boot into system from there either, it always returns to Odin (tried wiping Cache/Dalvik, didn't help).
For now my only idea is to let it completely discharge, charge again and give it another try.
No buttons appear to be stuck.
Any ideas or suggestions, eg sth I could check in TWRP to see what's going on?
(hopefully nothing wrong with the system partition).
Note - I'm only familiar with the typical TWRP functions needed to install custom firmware, haven't used it for much else. Obviously would prefer not to destroy my (stable) setup and spent a full day re-installing everything
Thanks a lot for your help everyone!
@Whoooo? Backup whatever possible with TWRP onto external storage (SD or OTG).
Check if file manager can access download/DCIM folders and save them as well.
Although the charging thing might help I wouldn't set my hopes to high.
Probably somethings wrong with system or boot partitions or any file needed by them.
I'm afraid you will have to reflash stock via Odin, root again and try if restoring TWRP saved Data works.
That would reduce setting up time.
bmwdroid said:
@Whoooo? Backup whatever possible with TWRP onto external storage (SD or OTG).
Check if file manager can access download/DCIM folders and save them as well.
Although the charging thing might help I wouldn't set my hopes to high.
Probably somethings wrong with system or boot partitions or any file needed by them.
I'm afraid you will have to reflash stock via Odin, root again and try if restoring TWRP saved Data works.
That would reduce setting up time.
Click to expand...
Click to collapse
Hi there,
Thanks a lot for your reply - yes, I will try that once the complete discharge is finished.
Reflashing stock - could cause this any troubles as it's already unlocked/rooted?
Or is there a chance dirty flashing the Tweaked Stock ROM could work, too?
Tablet was still on the original Stock it came with, but rooted with magisk and manually debloated...
Thanks again!
I think Odin won't care about unlocked bootloader.
But might be necessary to unlock again.
Dirty flashing afaik only works with TWRP so only flashing of zip or img files possible.
Except you sideload although Idk if that's possible on Samsungs.
Dirty flashing of a before the problem arose made backup might work.
Did you debloat while already installed or externally?
What file format does it have?
My T825 uses the debloated ROM by rorymc628 which can be flashed with TWRP as it's a zip file.
bmwdroid said:
I think Odin won't care about unlocked bootloader.
But might be necessary to unlock again.
Dirty flashing afaik only works with TWRP so only flashing of zip or img files possible.
Except you sideload although Idk if that's possible on Samsungs.
Dirty flashing of a before the problem arose made backup might work.
Did you debloat while already installed or externally?
What file format does it have?
My T825 uses the debloated ROM by rorymc628 which can be flashed with TWRP as it's a zip file.
Click to expand...
Click to collapse
Hi there and thanks again -
Took me a while to try everything but finally it's working again.
Complete battery drain didn't help, but dirty flashing did - once I got the correct version.
Basically made a nandroid backup, then flashed the tweaked rom over my existing one, starting with newer versions down to older ones.
So, flash, reboot - didn't work, restore nandroid (all), flash slightly older rom....
Till it started booting with v2.0 (probably matching my existing rom close enough).
Had to reflash Magisk as the 2.0 Rom included didn't match my Magisk Manager, but now my Tab S3 is working again!