Is there a way to run something in the stock when it reboots?
thanks
Related
My question may be easy but I can't understand this...I had vr 2.1 and went to vr 2.3 by flashing the Rom through recovery mode.all ok.then I installed Ninphetamine kernel 2.0.2 but then I lost root access.is this normal or did I screw up something?after losing root I flashed with odin cf-root and now everything is ok but I prefer Ninphetamine...any help?
Sent from my GT-I9100 using XDA App
You probably need more than Ninphetamine's kernel to get root. (I have no clue about this) But Cognition uses the Ninphetamine kernels too and it works just fine. Maybe they're incompatible with VR?
The way I understand it (each phone manufacturer seems to be different) is that the kernel frequently blocks either access to root, or the installation of specific files.
To have root, you need the su executable, and an apk which allows applications to ask for root priviledges. Both of these are stored in /system, and are not part of the kernel. However, in order to install these, you either need to re-flash a ROM with them pre-installed, or install a kernel and other files over the top of your existing rom using ODIN.
Flashing a new kernel may remove recovery (CWM), but doesn't (as I understand it) affect root. Some kernels are incompatible with certain ROMs though (I'm still on the stock kernel)
Now you have root again, try re-installing the kernel (point CWM app at the zip file did it for me)
I'm having a lot of trouble deleting install-recovery.sh. As many of you know, this resets the Android recovery, flashing the stock recovery over the Custom CWM-based recovery that I had. I'm trying to install Ubuntop.
I very well know I could simply install it once, install ubuntop, and go along on my merry way, but I need CWM for piece of mind, access to my backup, etc.
According to Romracer's post:
[quote user=mrinehart93]The system runs /system/etc/install-recovery.sh on boot with the stock rom. On boot it checks the recovery partition for some update and with CWM installed decides to reflash the stock recovery over it.
Rename or delete the file and the CWM should stick.[/quote]
I've tried Terminal Emulator with root access, a root file explorer, everything. Unless theirs some hidden ADB method.
I also know I could get rid of this problem by installing a custom ROM.
However, I'm not so in tune with all the ROMs and kernels like I was with my EVO.
Any type of solution that doesn't involve me changing my stock ROM and kernel is appreciated.
If their isn't a solution, point me towards a nice deodex'd ROM. Please no undervolting/overvolting/OC'd stuff. Thanks~
To any of you wondering, I fixed it by installing Alien ROM.
To anyone who may fall into this problem later: Download This.
Ok, I gotta be a noob for a second. I've been married to this message board since Thanksgiving when I got my Rezound, I've read nearly every word written over the last week since we got unlock/ root..... but I am lost on one thing....
What is this boot.img file all about? There is a lot of talk about how to flash it, but I am not clear on when or why you need it. It sounds like it's part of the ROM zip file, but I'm running BAMF and it does not contain a boot.img file, and it doesn't appear that it was needed in this case since everything is working.
Can someone hook me up with a quick 101 course on this file?
Basically that file is the kernel of the OS.
The big deal with it is the fact that we can not flash the file directly as part of the normal ROM flashing procedure. This is because we do not have S=off. No ROMs for the Rezound will include a boot.img in the .zip, other devices with S=off will have the boot.img
This means that whenever we flash a ROM, the kernel is untouched by the ROM flash, we must then use fastboot to flash the kernel necessary for the ROM.
This isn't a big deal for ROMs strictly based on the stock ROM. Just flash the ROM and go, you can even switch between stock based ROMs with no problem or need to flash the kernel. (as long as you have not flashed a different kernel)
Now if the ROM is stock based but uses a kernel different than the stock kernel, you must flash the kernel it comes with after you flash the ROM.
This goes for any ROMs not stock based as well. AOSP, MIUI, and others will need to have a separate boot.img file available for download that you will need to flash in fastboot in order for the ROM to boot.
The real problem comes when you want to run a custom kernel (One that did not come with the ROM originally, or not purposely designed for the ROM you are using) This is because there are files within the ROM itself that are unique to the kernel being used. If you want to use a custom kernel then you must alter these files to be compatible with the new kernel. you then must flash those files into the ROM before you flash the new kernel.
Luckily we have a new tool that can do this for us, but the process is still a pain.
Marine6680 said:
Basically that file is the kernel of the OS.
The big deal with it is the fact that we can not flash the file directly as part of the normal ROM flashing procedure. This is because we do not have S=off. No ROMs for the Rezound will include a boot.img in the .zip, other devices with S=off will have the boot.img
This means that whenever we flash a ROM, the kernel is untouched by the ROM flash, we must then use fastboot to flash the kernel necessary for the ROM.
This isn't a big deal for ROMs strictly based on the stock ROM. Just flash the ROM and go, you can even switch between stock based ROMs with no problem or need to flash the kernel. (as long as you have not flashed a different kernel)
Now if the ROM is stock based but uses a kernel different than the stock kernel, you must flash the kernel it comes with after you flash the ROM.
This goes for any ROMs not stock based as well. AOSP, MIUI, and others will need to have a separate boot.img file available for download that you will need to flash in fastboot in order for the ROM to boot.
The real problem comes when you want to run a custom kernel (One that did not come with the ROM originally, or not purposely designed for the ROM you are using) This is because there are files within the ROM itself that are unique to the kernel being used. If you want to use a custom kernel then you must alter these files to be compatible with the new kernel. you then must flash those files into the ROM before you flash the new kernel.
Luckily we have a new tool that can do this for us, but the process is still a pain.
Click to expand...
Click to collapse
Thanks Man This Information Is Greatly Appreciated. I Definitely Had The Right Idea In My Head And Now You've Clarified That For Me And Anyone Else Who's Wondering.
Much thanks Marine, that's exactly what I was looking for. My confusion has been alleviated... for now at least....
I currently have busines gingersense ,which by the way is sweet ,thanks Nills ,I have my stock Rom backed up w/ amon ra. Now if I want to try business ICS and then go back to gb, will I be able to reload in recovery like any other Rom or does this require special steps, I have read about other ics roms not being able to recover so easily, if so would anybody care to do a step by step. Thanks ...
Sent from my ADR6425LVW using XDA App
You need to flash the stock kernel to use GB ROMs if you have used an ICS ROM (a copy is located in scotts GB based ROMs, just unzip the file and find the boot.img)
You can flash the kernel before or after you restore the backup.
I find it easier to do before, then selecting the reboot to recovery option, allowing me to then flash the new ROM or backup.
Use the cleanflash tool to flash the kernel (boot.img) if you need a simple method.
I have installed CPU analyser, and with stock ROM I think the slowest it goes is 300mhz, WIth a modded ROM it slows down to 110mhz. So I'd like to use modded kernel with stock ROM (I've found no ROM's to be as quick or stable as stock)
Is it possible to have stock LK1 firmware, but with rafa's modded kernel? My procedure is
1) Recover LD1 firmware with ODIN
2) Reboot update LK1 in KIES
3) add super user. Boots, make calls etc
4) Apply kernel and modules. Boot and lost IEMI. I have tried restoring IEMI from my backup in galaxy toolbox, rebooted. But it still doesn't work.
Am I doing something wrong, or does the stock ROM not support modded kernel/modules in anyway?
Also if I do get it working, do I need some kind of CPU/battery saver or are the routines built into the kernel, no other apps are needed? I tried one app, it seems to work but it keeps on popping up with a message that it's using superuser priv, so it's quite annoying.
flash modules of kernel after flashing the kernel without rebooting in between!
this way u won't loose imei!!
whenever superuser permission message come up, there's an option below to remember the choice, click it and then message won't appear again!
ah so flash kernel, then modules without rebooting? I'm pretty sure a couple of guides say flash kernel, reboot (go straight back into recovery) then flash modules.
which specific (filename) kernel and modules to use with stock LK1 ROM?
201303051129-E3-boot.img
and
201303051129-modules
did that, emergency calls only! arggh
Try flashing modules after reboot.. Flashing modules should solve imei problem!
Sent from my GT-S5830i using xda app-developers app