Related
I am in a bit of a pickle. I'm one of the unfortunate souls who's brand new Evo doesn't take kindly to flashing. I am rooted and running sprintlovers Rom, but would like to try some overclock goodness, not to mention having the framerate unlocked. My thought is that, though I can't flash anything from recovery (when you try to flash anything, it just bootloops right back into recovery when you restart), I may be able to flash an OC'd kernel through fastboot. I looked into how to do this myself, but it still seems a bit over my head. Is there a kind soul out there who would make me a boot.img out of either or both of these???
netarchy-toastmod-4.1.9.1-cfs-NoHAVS-universal
netarchy-toastmod-4.2.1-cfs-bfq-havs-less-smartass-universal (Less Aggressive Undervolting)
Thanks a lot for your help!!!!!
Richard
you can't flash anything from recovery?
Put it on your PC, open up the .zip and you may find a little surprise in there...
xHausx said:
you can't flash anything from recovery?
Click to expand...
Click to collapse
Nope. I have S-off, I am running sprintlovers and have root, but when I boot to recovery, flash something, and then reboot.....all I get are bootloops. Yesterday, I opened up logcat just before booting. Here us the one and only log entry:
Code:
C:\A>adb logcat
- waiting for device -
link_image[1995]: failed to link /system/bin/sh
CANNOT LINK EXECUTABLE
Igotsanevo4g said:
Put it on your PC, open up the .zip and you may find a little surprise in there...
Click to expand...
Click to collapse
Lol, I may be new to the evo, but I'm not a total n00b. That was the first thing I checked. There is no flashable boot.img file in the kernel folder. Now, maybe one of the files in that folder just needs to be renamed, I'll admit my ignorance right upfront. I did do research before I made this thread, but when they started talking hex editing (of which I've only done a little) and running prl scripts, I knew I was getting over my head.
EDIT: BTW, I have tried both clockwork and Amon-Ra recoveries. Both have the same basic logcat readout, just a slight variation in syntax.
Afternoon bump
tejasrichard said:
Afternoon bump
Click to expand...
Click to collapse
if its the new evo u cant flash a kernel or any rom that isnt based on the latest OTA's. Its because they have a few different drivers and the kernels dont support them yet so thats why u cant flash anything really. so just sit tight with a rom like sprint lovers or Vaelpak and you should be good for now
Use the Android kitchen in the chef's forums. It will inject that kernel into whatever boot.img you want real fast
May be a dumb reply but did you wipe and clear cache?
You can strip the zimage file out of the .zip and push it to the phone using adb...
(Avis aux intéressés, j'ai parti une discussion en français sur Frandroid.)
Hello everyone,
Here's my ArpegGioMod ROM, for the Galaxy Gio GT-S5660M. Current (and final) version is 0.9
(ArpegGioMod has had over 1500 downloads! Thanks!)
Features:
Rooted
Deodexed apps and framework. (Optional)
Working FM radio (remember, your headphones are the antenna!)
No power on sound.
Restored support for the normal Android bootanimation.zip format. Right now it's just running the "base" animation (with the green Android text). I'm open to suggestions/logos/proposals!
CRT screen off animation re-enabled, you do need to turn back animations on in the settings to see it.
ADW Launcher (I just used the "standalone" version and placed it in /system/app/, not the cleanest way, but it works, and leaves you the choice between that and Touchwiz Launcher)
Removed all Bell software, as well as some Samsung apps.
New in 0.6
Added options to the power button menu: Reboot (Normal), Reboot Recovery Mode and Reboot to Download Mode.
Car mode.
New in 0.7
Phone will not relock itself to Bell after doing a factory reset without a SIM card in the phone.
Changed the default browser homepage to Google instead of Bell's.
New in 0.8
Phone will not relock itself to Bell after doing a factory reset without a SIM card in the phone. (Turns out I mixed up some files and uploaded a version with Bell apps left in the CSC folder, along with the unmodified customer.xml. Not an issue, until someone did a factory reset.)
Unsecure kernel. So now, adb remount and push work. adb shell is permanently root.
New in 0.9
CWM installation instead of Odin
Using Phiexz's customized stock ROM kernel, with support for both ext4 and RFS partitions. The kernel also includes different wifi drivers, and they work for me!
Updated superuser apps (3.0.7) and binaries (3.0.3.2). The upgrade of su from 3.0.3 to 3.0.3.2 seems to have fixed whatever caused the crashes.
Reodexed, this seems to provide better performance.
Removed the annoying "Full charge" notification.
Enabled native SIP functionality. (Untested.)
Removed the "Android Tips" widget.
Added the "Roboto" FlipFont apk, found on XDA.
No-frills CPU Control 1.20
Google Application updates:
Android Market 3.4.4
Gmail 2.3.5.2
Google Maps 6.3.0
Google Search 1.3.3.247963
Street View 1.7.1.0
Voice Search 2.1.4
YouTube 2.3.4
To do:
Implement BLN by patching /system/framework/services.jar
Things I will not do. (Or at least, not without significant assistance from those requesting it.)
Additional languages.
Files required to install 0.9:
Galaxy Gio ext4 converter
Backup RFS User Data (Optional)
Restore User Data to ext4 (Optional)
ROM Zip file: ArpegGioMod 0.9 MD5 hash: 010DA7C4542537443D2DD2E9BDBAFC43
Re-odex script (Optional)
Short Version 0.9 Installation instructions:
If you're upgrading from a stock ROM or ArpegGioMod 0.8: Backup User Data Script
(You'll probably want to delete the two tar.gz files remaining on your SD card afterwards.)
As required: format from RFS to ext4.
If you're upgrading from a stock ROM or ArpegGioMod 0.8: Restore User Data Script
Flash ROM zip
Re-odex as required
Detailed Version 0.9 Installation instructions:
(Or, the "this is my first time trying this out and frankly I'm a little overwhelmed with information" version.)
I'm going to start this one with a brand new, freshly out of the box Gio. I will however assume that you already have a working Odin and Android SDK install. Plenty of tutorials out there for both. (See links below for the correct Odin version.)
Copy the zip files to your MicroSD card.
Reboot your phone in Download Mode. (Hold Volume Down + Home + Power. There will be a pink warning screen. Press Volume Up.)
Flash ClockWorkMod Recovery with Odin.
Reboot the phone into Recovery Mode. (adb reboot recovery, or Home + Power)
"install zip from sdcard"
"choose zip from sdcard"
Install the ext4 converter zip.
Install the ROM zip.
Install the Re-odex script zip.
Reboot
Optional: adb shell, then dd if=/dev/block/bml5 of=/sdcard/bml5 bs=4096 to get your unlock code as per Tweakradje's unlock tutorial.
Enjoy!
Version 0.8 Installation instructions:
Un7zip and flash with Odin.
I strongly suggest you do a factory reflash and reset if you're flashing from something other than stock or ArpegGioMod.
Version 0.8: http://www.mediafire.com/?nxp0ce21909c676 7-Zip file MD5 hash: 6CEE73812AF9D30189A5F808CE0A7DEA
(Thanks Koodiifin!)
Tools and additional information:
CWM 5.0.2.7-based recovery, compiled for the 5660 by Phiexz, modified for the 5660M by Peteragent5: http://forum.xda-developers.com/showthread.php?t=1493932
"Supersafe" bml5 unlock method by Tweakradje, originally meant for the GT-I5500, should also work with little or no modifications for the 5660M: http://forum.xda-developers.com/showthread.php?t=828534
My other thread from which all of this started: Samsung Galaxy Gio GT-S5660 and GT-S5660M Partition Mapping This thread contains links to a rooted, but otherwise completely stock ROM backup I made prior to starting my work on ArpegGioMod.
Older Clockworkmod-based recovery, meant for the Europe/Asia 5660, but working fine on the 5660M: http://particle.blurringexistence.net/samsung-gt-s5660/clockworkmod-recovery
Tutorial on flashing with Odin, with link for the appropriate version for our phone.
Goodbye,
Darkshado
Just installed ArpegGio on my Virgin Mobile 5660M and it seems to be working great. 3G wifi and FM are working, plus I am glad to be rid of a bunch of carrier garbage apps. Thanks Darkshado I can't wait to see a2sd in there. Could I install it the manual way on this FW?
OT:
Thanks too Darkshado for all your tips for 5660M owners. I got mine 3 days ago, rooted and unlocked on day 2, flashed your FW on day 3. Reminds me of my days making custom OS for my blackberry
hardran3 said:
Just installed ArpegGio on my Virgin Mobile 5660M and it seems to be working great. 3G wifi and FM are working, plus I am glad to be rid of a bunch of carrier garbage apps. Thanks Darkshado I can't wait to see a2sd in there. Could I install it the manual way on this FW?
Click to expand...
Click to collapse
If you mean by modifying your boot.img ramdisk, yes. That's what I've been unable to do. I suspect an outdated/incompatible mkbootimg binary, and can't download the source make a new one as of writing this since kernel.org is still down.
If you're feeling adventurous, you could also try flashing an Euro 5660 boot.img. But I can't guarantee there won't be other issues.
OT:
Thanks too Darkshado for all your tips for 5660M owners. I got mine 3 days ago, rooted and unlocked on day 2, flashed your FW on day 3. Reminds me of my days making custom OS for my blackberry
Click to expand...
Click to collapse
You're welcome.
Hi, This is going to be my first flash for my S5660M. I've a small question for it. What mode should I choose in ODIN? Do I need to care about the ops file?
Sorry for my newbie question. Thank you.
You have to rebuild kernel with ext support. To create system.rfs or other *.rfs you have to type in console
Code:
mkfs.ext4 -O ^huge_file system.rfs
or it won`t boot. Of course you need modify initscripts. You can change from rfs to ext4 and it should work.
My problem is that due to the troubles at kernel.org I haven't been able to download the AOSP source yet.
I already suspected it wouldn't work with the stock kernel boot.img before trying.
For the conversion, I used a modified Galaxy Tab ext4 conversion update with the mkfs binaries included. That worked like a charm, CWM mounted the partitions, no questions asked.
I'll have to wait until an official AOSP repo comes back online to take this further.
Goodbye,
Darkshado
Sent from my Nexus S using XDA App
It will work with stock kernel, but you need change build config.
Hi
Just installed your rom this sunday... It work nice and no problem!
Was wondering, is the factory reset from the cwm is better than the one within the phone app? And or is the same?
And keep up the good work it is really appreciated
Thx Dark!
Sent from my GT-S5660M using XDA App
Darkshado said:
Hello everyone,
New in 0.6
[*]Added options to the power button menu: Reboot (Normal), Reboot Recovery Mode and Reboot to Download Mode.
[*]Car mode.
[/LIST]
Goodbye,
Darkshado
Click to expand...
Click to collapse
Nice job, very nice.
Is it duable to create that option in a aditional zipfile.
That you can flash it in recoverymode with a other rom????
You would make me very happy with that.
You have to modify framework-res.apk framework.jar and android.policy.jar for this to work, and it requires editing Smali code.
I did it by loosely following guides meant for the I9000 found here.
You could always push those files from my ROM to give it a try like that, but I wouldn't count on the framework from the 5660M to be fully compatible with the 5660 (which I understand you have from some of your other posts).
Question: has anyone else managed to re-Sim-lock their phone?
It's happened to me inadvertently, twice. Not knowing why on Earth the phone did this, I decided to get to the bottom of things.
The unlock code from bml5 still works, but I find this annoying to say the least.
I found some strings in the CSC files (customer.xml to be exact) that seemed to tell the phone what network to lock itself to.
I managed to make the phone relock itself by going into recovery, wiping user data, and rebooting the phone without a SIM card in. Checking lock status with *#7465625# shows Network Lock [ON]
I turned off the phone, put a foreign SIM back in, unlocked the phone again, and re-wiped user data, leaving the non-Bell SIM in for the first boot. No relock.
I relocked the phone as above. Rebooted into recovery and pushed modified customer.xml files, without the network lock strings, to my /system/csc/ and /system/csc/BMC/system/csc/ directories. No relock!
Those modified CSC files are going to be included in ArpegGioMod from now on.
Goodbye,
Darkshado
Darkshado said:
You have to modify framework-res.apk framework.jar and android.policy.jar for this to work, and it requires editing Smali code.
I did it by loosely following guides meant for the I9000 found here.
You could always push those files from my ROM to give it a try like that, but I wouldn't count on the framework from the 5660M to be fully compatible with the 5660 (which I understand you have from some of your other posts).
Click to expand...
Click to collapse
Hi, thx for the reply
Yes i have the 5660 ( no M ).
But i don't have a linux machine........
And i need that to compile those files.
I supose a linux-live dristri doesn't ad up for the job
Amadeus01 said:
Hi, thx for the reply
Yes i have the 5660 ( no M ).
But i don't have a linux machine........
And i need that to compile those files.
I supose a linux-live dristri doesn't ad up for the job
Click to expand...
Click to collapse
I think a live distro would work fine... Me I installed Vmware player (free) to run a virtual ubuntu machine and it work fine for editing some of the the tar file... so a live distro would even be better i'm sure!
Sent from my GT-S5660M using XDA App
I unlocked with safe bml5 trick and wiped a couple of time but i did not put back a non bell sim since then... So i dont really know...
Did you use some script or some like that in you Rom? Because I got like almost 400-500 more point on antutu benchmark.... Nice
Sent from my GT-S5660M using XDA App
theboo23, Amadeus01: Practically all of my ROM work has been done under Windows so far!
You need:
Java JDK
Android SDK
apktool
Cygwin
A hex editor (I've used Frhed so far)
Notepad++ (Free, open source, tons of features: syntax highlighting and Unix line ending support to name a few)
(Optional) A program that can open FAT format image files such as MagicISO, to extract files from RFS partition images.
(Optional) xUltimate, to simplify deodexing a great deal.
(Optional) 7-Zip
I have installed Ubuntu (on an external USB drive with Wubi and Grub4DOS) to attempt boot.img and kernel modifications, and to build from AOSP/CyanogenMod source.
However, kernel.org, which hosts AOSP repositories, is still down almost three weeks after having been hacked. So those parts of my project have been stalled in the meantime as I hadn't downloaded the source beforehand.
theboo23: There have been multiple reports of deodexing increasing performance, that might explain the points increase on the benchmark. To be frank, I don't bother with them unless I have something really specific to test.
Goodbye,
Darkshado
Darkshado said:
Those modified CSC files are going to be included in ArpegGioMod from now on.
Click to expand...
Click to collapse
By "from now on" I suppose you mean ver 0.7 included which is also on the changelog for it. However, it's exaclty after I flashed 0.7 (from 0.6 and stock before that) that my phone re-locked again and I had to use the unlock code (which I retreived while ago using bml5 method and still keep). I wiped before flashing 0.6 on top of stock, but did now wipe before flashing 0.7 on top of 0.6.
By the way, I knew already that at one point I will need my unlock code again. Having unlocked 6 or 7 5660Ms in the last week I have noticed that, once unlocked for a network (say, Fido) and you put a different SIM (Chatr), it gets locked again! Not only that, if you put the Fido SIM back, it is still locked. You have to enter the unlock code again, and luckily it's always the same. So, I resorted to writing down the code on the back of the phone under the back plate for further reference
And a couple of questions: your ROM has only one file/partition in it - system.rfs - and apparently this is the only thing that it replaces, everything else remains stock. One other custom ROM available on this site contains two files in the .tar - system.rfs and boot.img.
Q1: will it be safe to flash that other ROM on a 5660M having in mind it only replaces those two files/partitions? I know you already answered this before, just being extra cautious
Q2: if I want to return to ArpegGioMod after that, how do I proceed? Where do I get the boot.img from? Posible answer here: I have made a full backup via CWM of the stock ROM. It contains boot.img. Can I insert it in your .tar and flash and expect to get the same as flashing ArpegGioMod directly on stock?
Q3: if I get the system.img (renamed to system.frs) and boot.img from the SWM backup, put them in a .tar and flash, will that give me stock phone?
stfn74 said:
By "from now on" I suppose you mean ver 0.7 included which is also on the changelog for it. However, it's exaclty after I flashed 0.7 (from 0.6 and stock before that) that my phone re-locked again and I had to use the unlock code (which I retreived while ago using bml5 method and still keep). I wiped before flashing 0.6 on top of stock, but did now wipe before flashing 0.7 on top of 0.6.
Click to expand...
Click to collapse
I tried a couple more wipes and SIM swaps (T-Mobile USA, Koodo and Telna) with no relock occurring, so I hate to say, but I'm a bit stumped if there's something else than the CSC files causing this.
By the way, I knew already that at one point I will need my unlock code again. Having unlocked 6 or 7 5660Ms in the last week I have noticed that, once unlocked for a network (say, Fido) and you put a different SIM (Chatr), it gets locked again! Not only that, if you put the Fido SIM back, it is still locked. You have to enter the unlock code again, and luckily it's always the same. So, I resorted to writing down the code on the back of the phone under the back plate for further reference
Click to expand...
Click to collapse
I take it you work at a Rogers/Fido kiosk or store right? You're probably going to get more data on this than I ever will. I too wrote my code in the battery door just in case after it relocked a second time.
Q1: will it be safe to flash that other ROM on a 5660M having in mind it only replaces those two files/partitions? I know you already answered this before, just being extra cautious
Click to expand...
Click to collapse
Should be safe, if the boot.img is meant for the Euro 5660, you could encounter some bugs. I haven't tested those boot partitions and kernels.
Q2: if I want to return to ArpegGioMod after that, how do I proceed? Where do I get the boot.img from? Posible answer here: I have made a full backup via CWM of the stock ROM. It contains boot.img. Can I insert it in your .tar and flash and expect to get the same as flashing ArpegGioMod directly on stock?
Click to expand...
Click to collapse
You could just restore that nandroid backup.
Otherwise, tarring the boot.img with Cygwin and flashing with Odin should work. Then flash ArpegGioMod. Or make a single tar file with both partitions in Cygwin.
Here's a "universal" command: tar -H ustar -c amss arm11boot mibib oemsbl qcsbl boot.img recovery.img csc.rfs system.rfs data.rfs efs.rfs > GT-S5660M_MUGKG3.tar
I put it in a text file with the .sh extension, in cygwin/bin/ making it a command that can be invoked directly. (It's actually part of a set of batch files I've made to automate the copy and preparation of ArpegGioMod updates.)
Q3: if I get the system.img (renamed to system.frs) and boot.img from the SWM backup, put them in a .tar and flash, will that give me stock phone?
Click to expand...
Click to collapse
No reason it shouldn't.
Darkshado said:
I take it you work at a Rogers/Fido kiosk or store right?
Click to expand...
Click to collapse
No, I'm just an user, my job has nothing to do with mobile business. It's just Futureshop had a great deal on 5660Ms last week and half of my family and friends got one I was the first to root and unlock mine so... had to do it with everybody else's. I'm playing with custom ROM flashing now and want to make sure I got everything right, because I suspect I will be doing it number of times.
So I'm using the opportunity to say "Thank you!" for your work!
i used this rom with m 5660m and i still got wifi problems. wont turn correctly. im seeing you mention about ops file and boot img modding.dont kno how to do that
chairsz said:
i used this rom with m 5660m and i still got wifi problems. wont turn correctly. im seeing you mention about ops file and boot img modding.dont kno how to do that
Click to expand...
Click to collapse
Did you flashed a 5660 rom? You'll need to flash the stock 5660m rom first. The link is here;
http://forum.xda-developers.com/showthread.php?t=1233719
I have experimented with different ROMs and two versions of TWRP, and have installed the fff bootloader. (I have two working cracked-glass KF's that I picked up cheap in addition to a like-new one, so I can try different ROMs, etc., at the same time.)
I had presumed until recently that the kernel was a part of the ROM that was locked in by the ROM developer. It appears, though, judging by the two lengthy threads about a kernel 3.0, that users can install different combinations of kernel and ROM.
Can somebody explain, or point to an explanation of, the relationship between a kernel and a ROM and how one installs a desired combination of the two? Can one install a new kernel over an existing ROM, install the kernel and then a ROM, or is it necessary to do something else, such as editing a .zip file before installing it?
I realize that if I were to read a few hundred messages in a few threads, I might come up with the answers myself, but I might also transition from being a still-coherent old guy to one with senile dementia before I got to that point. Aside from my personal needs, though, it seems that an explanation of this matter deserves to be someplace where it can be easily found.
The kernel is the main component of the operating system (ROM). The kernel is essentially the middle man between the applications and the processing being executed at a hardware level. Basically the kernel is the communicator between software and hardware.
With that said, ROM developers will use a specific kernel with their ROM. You are not locked in to use the kernel which came with "x" ROM. A new kernel can be installed. You want to make certain if you are using an ICS ROM you parallel it with an ICS kernel. If you flash an incompatible kernel that could be a problem. Some kernels work better with some ROMS. Different combinations produce different bugs. It's just a matter of tinkering until you find the combination which suits you best. Hash's latest 3.0 kernel (http://forum.xda-developers.com/showthread.php?t=1591850) is popular and seems to be mostly stable with the ICS ROMS for the KF.
Installing a kernel is just like flashing a ROM although you don't need to wipe anything. Just boot in to recovery and select the kernel you've downloaded.
Should the custom kernel be installed after the ROM? It would seem that that would be necessary if the ROM itself comes with a kernel, as it apparently does.
Also:
? Are both the kernel and the rest of the ROM installed into the system partition, /dev/block/mmcblk0p9? If not there, then where?
? Does the kernel include the compiled code for all the standard linux commands, or only the system-level ones? Does it include the Dalvik interpreter?
aarons510 said:
Should the custom kernel be installed after the ROM? It would seem that that would be necessary if the ROM itself comes with a kernel, as it apparently does.
Also:
? Are both the kernel and the rest of the ROM installed into the system partition, /dev/block/mmcblk0p9? If not there, then where?
? Does the kernel include the compiled code for all the standard linux commands, or only the system-level ones? Does it include the Dalvik interpreter?
Click to expand...
Click to collapse
1. boot.img
2. Kernel come with system calls, or API, the commands you mentioned is binutils (most popular is GNU's). In Android you can install busybox to get these commands.
Gửi từ Kindle Lửa của tôi qua Tapatalk 2
linktohack said:
1. boot.img
Click to expand...
Click to collapse
What part of my question is this an answer to? I'm guessing that it's meant to answer the questions in the third paragraph of my original post, but it's a bit cryptic, to say the least. I do want to confirm that the new kernel gets installed after the ROM is installed, if that is indeed the case.
2. Kernel come with system calls, or API, the commands you mentioned is binutils (most popular is GNU's). In Android you can install busybox to get these commands.
Click to expand...
Click to collapse
I just checked the version of ICS I have installed on one KF and the CM7 installation I have on another. On both of them, the system calls seem to be in /system/bin while the file manipulation and document processing commands are in /system/xbin. Most of the latter are, indeed, symlinks to busybox while many of the former are symlinks to toolbox.
So, when one installs a new kernel, is one just over-writing /system/bin and maybe other directories with a new set of system calls, or is something else going on? And where does the dalvik interpreter fit in? Is it part of the kernel, part of the ROM, or neither?
aarons510 said:
What part of my question is this an answer to?
Click to expand...
Click to collapse
I think he meant to tell you that the kernel is usually distributed as boot.img in the ROM zips.
aarons510 said:
I do want to confirm that the new kernel gets installed after the ROM is installed, if that is indeed the case.
Click to expand...
Click to collapse
The kernel is installed along with whatever ROM you install. Let's say you pick MadeUpRom and it features kernel #8 with it. You'd have to flash kernel #11 after installing said ROM.
aarons510 said:
So, when one installs a new kernel, is one just over-writing /system/bin and maybe other directories with a new set of system calls, or is something else going on? And where does the dalvik interpreter fit in? Is it part of the kernel, part of the ROM, or neither?
Click to expand...
Click to collapse
Kernels are installed to the boot partition, which is separate from the ROM's /system partition. Installing a new kernel will overwrite the existing one. For the dalvik, read this to understand it better: http://stackoverflow.com/questions/7541281/what-is-dalvik-and-dalvik-cache
aarons510 said:
What part of my question is this an answer to? I'm guessing that it's meant to answer the questions in the third paragraph of my original post, but it's a bit cryptic, to say the least. I do want to confirm that the new kernel gets installed after the ROM is installed, if that is indeed the case.
I just checked the version of ICS I have installed on one KF and the CM7 installation I have on another. On both of them, the system calls seem to be in /system/bin while the file manipulation and document processing commands are in /system/xbin. Most of the latter are, indeed, symlinks to busybox while many of the former are symlinks to toolbox.
So, when one installs a new kernel, is one just over-writing /system/bin and maybe other directories with a new set of system calls, or is something else going on? And where does the dalvik interpreter fit in? Is it part of the kernel, part of the ROM, or neither?
Click to expand...
Click to collapse
In Android world, a kernel is an image contains a Linux kernel and a ramdisk which is named *boot.img* and will be *write* (byte copy) to the boot partition.
A complete ROM is a singed zip file contains at least /system files and a kernel. When you flash a ROM, it will unpack and *copy* file of /system to the system partition (that's why we wipe the system partiton aka. factory reset before we flash a new ROM) then *write* boot.img to boot partition.
Usually, a kernel needs external modules, offen reside at /system/lib/modules, so developer create an *uncomplete* ROM, which contains only kernel and these external files. This flashable kernel looks like a ROM, but it's really small size compare to complete ROM.
Like I said above, files in /system/bin/ and /system/xbin/ is not related to kernel (boot.img). They are just binaries, compiled to use system calls that kernel (and modules) offer.
--- Dev only ---
System calls is not binaries, they are CPU interupt instructions. Your programs need to be compiled to call them.
In linux, system calls are called through interupt *0x80*
Hi All,
I've been trying a few different kernels on my d2spr, and though I backed up my system in complete before flashing anything, I'm curious if there's an easy way to remove kernel scripts before flashing a new one to avoid having to restore a backup every time.
For instance - I run the kernel cleaner script, then I flashed kernel X. After a bit I decided I wanted to give Freeza's stock optimized a run, so I again flashed the kernel cleaner script, then Freeza's kernel.
I'm noticing that a lot of the previous kernel X (edited and new) scripts are still on my system. Like qcom post boot sh, and other files files.
Is there a good way to get rid of these when going between kernels? I find that when they stay on the system, my OS starts acting wonky / cpu settings don't stick after rebooting / etc.
Thanks for any assistance!
-Dirk
dirkdigles said:
Hi All,
I've been trying a few different kernels on my d2spr, and though I backed up my system in complete before flashing anything, I'm curious if there's an easy way to remove kernel scripts before flashing a new one to avoid having to restore a backup every time.
For instance - I run the kernel cleaner script, then I flashed kernel X. After a bit I decided I wanted to give Freeza's stock optimized a run, so I again flashed the kernel cleaner script, then Freeza's kernel.
I'm noticing that a lot of the previous kernel X (edited and new) scripts are still on my system. Like qcom post boot sh, and other files files.
Is there a good way to get rid of these when going between kernels? I find that when they stay on the system, my OS starts acting wonky / cpu settings don't stick after rebooting / etc.
Thanks for any assistance!
-Dirk
Click to expand...
Click to collapse
root explorer>system>etc>init.d. I had this issue with the kernal I am running-Click Here To See My Post
dirkdigles said:
Hi All,
I've been trying a few different kernels on my d2spr, and though I backed up my system in complete before flashing anything, I'm curious if there's an easy way to remove kernel scripts before flashing a new one to avoid having to restore a backup every time.
For instance - I run the kernel cleaner script, then I flashed kernel X. After a bit I decided I wanted to give Freeza's stock optimized a run, so I again flashed the kernel cleaner script, then Freeza's kernel.
I'm noticing that a lot of the previous kernel X (edited and new) scripts are still on my system. Like qcom post boot sh, and other files files.
Is there a good way to get rid of these when going between kernels? I find that when they stay on the system, my OS starts acting wonky / cpu settings don't stick after rebooting / etc.
Thanks for any assistance!
-Dirk
Click to expand...
Click to collapse
Init.qcom.post_boot.sh isn't added by any kernel. It has to be there.
You can easily remove any additions by browsing the zip you flashed. See what things were added.
However, if anything was replaced, you will need to restore a backup or reflash your rom.
Sent from my buttered S3
In the Op of THIS THREAD there is a Kernel Cleaner listed. It's also linked in the post HERE.
Hi guys, I've looked all over XDA and I can't seem to find anything related to this, so here goes.
I have a rooted HTC One m8 a custom Marshmellow 6.0.1 Rom with TWRP installed.
however, when I try to install mods that modify the system, like busybox or audio mods, they never install and the changes don't stick when I reboot my phone. (e.g; busbox will say it's not installed after I reboot when it clearly has been, but everything done is reverted after I reboot the phone.) Does this mean my phone is NAND locked or something? or does it have something to do with /vendor restoring things? I've looked in /vendor and /system/vendor but none of them have any of the named files busybox or any lib or /etc files that should be replaced upon reboot, so idk where to go from there. Do I just delete the entire /vendor folder?
I really want to get this to work, but none of my mods will install because they keep asking me to install busybox, which I must have done 1,000 times by now, but the changes always revert on reboot.
Can anyone help me please? Thank you
The system is write protected now. You need to flash a permissive kernel. ElementalX works good.
Above suggestion works, or you can also flash the write protection mod (wp_mod) posted in the following ROM thread:
http://forum.xda-developers.com/htc-one-m8/development/rom-stock-unlocked-developer-sense-7-t3262894
I was looking for that link, but didn't find it. Thanks for jumping in buddy!