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
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've flashed a few phones in my time including 2 S2's and an S3 although I had a big problem with this S3 my friend had. It had 4.1.2 default samsung software on it and i tried to ODIN flash an autoroot cwm v5 file i usually use to root phones, it did not go as expected eg. it just turned the phone off but came out as a pass on ODIN, and ii flashed it again with another CWM recovery file i found from the net, this time its V6+ and it flashed like a charm you know the usual result right. Now that CWM works i tried to flash 4.4.2 on the phone and it gave me that "set metadata recursive some changes failed" error thing and the phone wont restart. I have wiped the data, dalvik and cache every single time i flash mind you using the CWM recovery. Now when i flash to some random rom lower than KITKAT it would flash well and would function quite well. I once again tried to flash kitkat by downloading rom manager and flashing to the latest version of CWM but here's the thing it CWM wont update and the current version installed just wont flash the KITKAT rom and just gives the same 'set metadata recursive some changes failed error' and again wont boot to system if i didn't flash back to 4.3 i tried twrp too to the same result "set metadata recursive some changes failed". The fix that the forums explained was updating to the latest CWM(CWM touch wont flash neither) but it didnt work forme even TWRP didnt work, someone help please.
First reset all you've done by flashing a full stock 4.3 rom, factory reset and make sure everything works.
Then flash philz recovery and use that to flash your custom rom.
Make sure you read the guides in general forum, sticky threads before you start.
So first of all, hello
I'm pretty new to this whole universe of custom roms, rooting etc.
My main problem is that I tried to install a custom rom (2 to be exact,
http://forum.xda-developers.com/galaxy-s3/development/rom-archidroid-v2-4-6-power-hands-t2354859
and http://forum.xda-developers.com/galaxy-s3/development/5-1-x-cyanogenmod-12-1-t3066864)
So, the whole rooting process was on this side:
http://www.techverse.net/root-samsung-galaxy-s3-android-4-3-jellybean/
I did everything and it worked like a charm
now I wasn't really sure about the crossfire recovery so I wanted to get cwm (because I had that one on my s2)
I downloaded it here:
http://forum.xda-developers.com/gal...covery-clockworkmod-touch-6-0-3-2-gt-t1719744
flashed it via odin 3.07 and everything worked fine
now I just wanted to install a custom rom:
Trying to install the cyanogenmod 12 resulted in a status 7 installation aborted error. I figured that this may have something to do with my
cwm version so I left it alone. The bootloop started on this try. I wiped Dalvik, Cache and Data
I thought that the bootloop resulted because I didn't have a single firmware installed so I tried to install a second rom. This time it was Archidroid. The Aroma launcher started, everything started, I chose my stuff etc. The installation began and I thought it would work. I was dead wrong. Some things failed on the installation but it still resulted in a finished message. This didn't help the bootloop tho. I made a factory reset, wiped dalvik, wiped cache and data, but nothing helped so far.
The only options I haven't tried are restoring my stock firmware and flashing another recovery (most like CF auto root).
Can somebody help me? I should mention that my phone is a samsung galaxy s III gt-I9300
Things u should consider:
Are u 100% sure U have the international galaxy S3 gt-i9300?
Are u sure ur download of the rom was completed? Sometimes the download can end up generating a corrupt zip.
I don't know which CWM versions comes by default, but it may not be updated, in this case u should use the recovery update option inside Aroma from Archidroid 3.1 as in the post (http://forum.xda-developers.com/galaxy-s3/development/rom-archidroid-v2-4-6-power-hands-t2354859)
If u r a new user maybe u could try an older version of Archidroid, cause the last version is a bit buggy, there is no CM12.1 running perfectly yet, maybe u can try Oldstable: "ArchiDroid 3.0.2 GitHub | XDA Direct | XDA Torrent" from the same post.
About recovery the Philz Touch recovery is easier to use, BUT is no longer updated, the last version i found is philz_touch_6.48.1-i9300-JustArchi.zip in http://d-h.st/users/Archi/?fld_id=34646#files or u may find a newer version here http://goo.im/devs/philz_touch/CWM_Advanced_Edition/i9300 (but I'm unable to resolve the DNS for the moment for this link)
TheRuan said:
Things u should consider:
Are u 100% sure U have the international galaxy S3 gt-i9300?
Are u sure ur download of the rom was completed? Sometimes the download can end up generating a corrupt zip.
I don't know which CWM versions comes by default, but it may not be updated, in this case u should use the recovery update option inside Aroma from Archidroid 3.1 as in the post (http://forum.xda-developers.com/galaxy-s3/development/rom-archidroid-v2-4-6-power-hands-t2354859)
If u r a new user maybe u could try an older version of Archidroid, cause the last version is a bit buggy, there is no CM12.1 running perfectly yet, maybe u can try Oldstable: "ArchiDroid 3.0.2 GitHub | XDA Direct | XDA Torrent" from the same post.
About recovery the Philz Touch recovery is easier to use, BUT is no longer updated, the last version i found is philz_touch_6.48.1-i9300-JustArchi.zip in http://d-h.st/users/Archi/?fld_id=34646#files or u may find a newer version here http://goo.im/devs/philz_touch/CWM_Advanced_Edition/i9300 (but I'm unable to resolve the DNS for the moment for this link)
Click to expand...
Click to collapse
I'm about 90% sure that my s3 is the international version (I'm not really sure how to check that)
as for the recovery update option in Archidroid. I'm actually really afraid that the update could somehow damage the recovery. Is it a safe process?
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?!