Hi
for my assignment in university i need to build a custom kernel. su/busybox worked fine so far, but i'm stuck with clockworkmod. i can boot fine into recovery, but the OS boot is stuck in the bootanimation (without sound btw) and logcat isn't really helpful.
what i've done so far:
when i got the device i flashed the latest stock ROM i found (XWKJ2), got temp root with ZergRush and pushed the latest SU binary. i unpacked the initramfs from the stock kernel, repacked and flashed it for testing purposes, which worked. i got the CWM zip (4.0.1.5) for the S2, extracted into the initramfs and repack/flashed. now CWM seems to work fine, but if i want to start android it is stuck in a bootloop while waiting for media.player (says logcat).
Now i downloaded https://github.com/teamhacksung/clockworkmod_galaxys2_initramfs
from codeworkx and it obiously worked fine, but i'm not so sure what the difference is besides busybox. also i don't get how changing the recovery binary will affect the boot process. any pointers on how to resolve this issue would be nice. maybe even codeworkx himself :/
will provide more info/logs/sources if needed.
Related
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.
After having overheating issues (presumably voltage related?) with the official XWLP7 XEU (UK) ROM I decided to try my luck on a custom slim version.
Phone was successfully CF rooted before Dynamic v1.4 ★[ICS][Slim][Performance & Battery life][25April] was installed.
Custom ROM is running fine, however when I was playing around in the recovery menu the phone screen randomly displayed artifacts after selecting "reboot now". So I was wondering if it's possible to downgrade clockworkmod to the generic public release version - namely this puppy?
Thanks for reading my first post lol
I suspect CWM went retarded during the CF to Dynamic v1.4 transition - can someone provide some insight here? I've deduced kernels were changed, but was unaware of the implications to the recovery console in doing so
Functionality only becomes an issue in the recovery menu before OS loads otherwise everything is tight as a drum
Recovery is linked to the kernel. Obviously your kernel changed when you flashed that ROM. If you want to change your CWM recovery, flash a different kernel which has the version you want.
Ok, I've gone ahead and been an inpatient muppet installing ROM manager from Google play and flashed the respective recovery console. Will this cause conflicts? It seems the original one still stands using the the three button combo when powering up where as the generic recovery console I just put on has to be executed via OS.
no issues keeping both if working perfectly....
Normaly there is a mismatch seen between ROM manager and other custom recoveries..
if you are rebooting from ROM manager to CWM if the update package flashes smoothly and flashed CWM is appears then no issue you can use it. i think its only flashes temporerly,
when you use the 3 combo you can get the recovery which is incorporated with your kernel....we only need a working CWM to flash zips, and backup,
Hey guys,
well i have a pretty nasty problem:
I am flashing the latest Cyanogenmod nightly for the HTC One X+ onto my phone.
This works without errors. The adb sideload installation operation returns a "successfully completed", too.
But when i reboot the device, there simply is no cyanogen mod on it.
I tryed with adb push and manually selecting the .zip file, too.
Again successfully completed. And again no ROM installed.
Actually this not only happens with the CyanogenMod Rom.
It happens with the Carbon Rom, too.
I am very confused! Can anyone help?
which recovery (+version) are you using?
have you flashed the kernel (boot.img) seperataly?
wiped data/ factory reset?
hey, i was using 6.0.4.7 i think. well now i have flashed the boot.img out of the cyanogenmod.zip seperately as boot. now the phone only gets stuck into the HTC bootscreen and doesnt do anything anymore
I have now wiped my phone completely and redone all steps from the cyanogen wiki once again.
Runs smoothely now, have no idea what went wrong before. Thanks anyway.
Hello everyone,
I recently picked up a couple GS2's for dirt cheap just to mess around with. I am having a very hard time getting any custom recovery installed on them and I was wondering if there is a trick to it that I am not seeing. I've tried flashing various CWM modified kernels using odin with no luck. They flash successfully but still boot to 3e when I boot into recovery. I tried flashing a modified update.zip from the CM website and it fails with the error "failed to verify whole-file signature". Most recently I did a complete restore using odin with a rooted image, then used Rom manager to install CWM. Rom managed says it is successful, but when I reboot into recovery it launches 3e and attempts to do something that returns the same error "failed to verify whole-file signature". Any input of suggestions would be appreciated.
Bklynrx7 said:
Hello everyone,
I recently picked up a couple GS2's for dirt cheap just to mess around with. I am having a very hard time getting any custom recovery installed on them and I was wondering if there is a trick to it that I am not seeing.
Click to expand...
Click to collapse
The recovery is compiled into the kernel on this phone, but it seems that you understand that already. The kernel and system must match. You probably need to be rooted. You have not given any specifics about the firmware, what is already installed, what specific item you are trying to install, etc.
I've tried flashing various CWM modified kernels using odin with no luck. They flash successfully but still boot to 3e when I boot into recovery.
Click to expand...
Click to collapse
This does not actually seem logical. I'm wondering if you are not mentioning something that I would need to know to determine why you are getting this result. If you install a custom kernel containing a custom recovery, you should then be able to boot into the custom recovery. If you still have 3e recovery, it indicates that you still have the stock kernel installed.
I tried flashing a modified update.zip from the CM website and it fails with the error "failed to verify whole-file signature".
Click to expand...
Click to collapse
I would not expect that to be successful. Among other things, it is probably not specific for the I777.
Most recently I did a complete restore using odin with a rooted image, then used Rom manager to install CWM. Rom managed says it is successful, but when I reboot into recovery it launches 3e and attempts to do something that returns the same error "failed to verify whole-file signature". Any input of suggestions would be appreciated.
Click to expand...
Click to collapse
Do not use Rom manager. It does not work with the I777, and can cause unrecoverable damage in some cases. There is a sticky post about it here in the forums.
You can find various resources in the Download Repository. See the link in my signature.
Here's what I would do:
Flash the latest stock Jellybean firmware, UCMD8, from the Repository.
Root using Framaroot with the Aragorn exploit.
Flash the AJK v4.9 NoSwap kernel using Mobile Odin Pro or Mobile Odin Lite. You have to extract the boot.img from the kernel zip and flash that, but don't let it boot into system. Instead, you can boot directly into CWM and flash the AJK v 4.9 NoSwap kernel zip, or if you prefer, you can flash some other custom firmware at this point.
creepyncrawly said:
The recovery is compiled into the kernel on this phone, but it seems that you understand that already. The kernel and system must match. You probably need to be rooted. You have not given any specifics about the firmware, what is already installed, what specific item you are trying to install, etc.
This does not actually seem logical. I'm wondering if you are not mentioning something that I would need to know to determine why you are getting this result. If you install a custom kernel containing a custom recovery, you should then be able to boot into the custom recovery. If you still have 3e recovery, it indicates that you still have the stock kernel installed.
I would not expect that to be successful. Among other things, it is probably not specific for the I777.
Do not use Rom manager. It does not work with the I777, and can cause unrecoverable damage in some cases. There is a sticky post about it here in the forums.
You can find various resources in the Download Repository. See the link in my signature.
Here's what I would do:
Flash the latest stock Jellybean firmware, UCMD8, from the Repository.
Root using Framaroot with the Aragorn exploit.
Flash the AJK v4.9 NoSwap kernel using Mobile Odin Pro or Mobile Odin Lite. You have to extract the boot.img from the kernel zip and flash that, but don't let it boot into system. Instead, you can boot directly into CWM and flash the AJK v 4.9 NoSwap kernel zip, or if you prefer, you can flash some other custom firmware at this point.
Click to expand...
Click to collapse
Sorry if I want clear. The phones are currently on 2.3.6. I tried using framaroot but it was not successful. The app said it was successful, but there was no supersu after I rebooted. I successfully got the phone rooted using one of the one-click odin flashers posted on these forums that are said to return it to factory + root. I then tried to use rom manager which said it was successful, but wasn't. That makes sense now that you're telling me its not compatible. Ill try upgrading to the JB firmware first, then ill try framaroot. Thanks for the suggestion
I just wanted to update the thread and say that this worked. Thanks again. I'm having an issue getting Gapps flashed but that's another topic. My big concern was that the phones wouldn't charge without boot looping because they had the wrong battery installed. The Stock Jellybean with the kernel you suggested fixed that.
Bklynrx7 said:
I just wanted to update the thread and say that this worked. Thanks again. I'm having an issue getting Gapps flashed but that's another topic. My big concern was that the phones wouldn't charge without boot looping because they had the wrong battery installed. The Stock Jellybean with the kernel you suggested fixed that.
Click to expand...
Click to collapse
Maybe I could help. What error does it give when you flash gapps?
Hello everyone! With some struggle I've managed to port CWM to an old tablet ONDA V703. Everything seems to be working, but CWM auto-terminates the session (interactive or adb) every time after 3-4 minutes. I have googled extensively but couldn't find anyone having the same problem.
Here are some details:
Android is version 4.1.1. CWM is v6.0.2.8. Built on Ubuntu using boot.img from the original firmware, and hand-editing a few files. Installed using flash_image over adb as root (this tablet doesn't support fastboot). After the first boot into CWM I cleared the cache.
I would be thankful for any hint; I'm a software developer, just need a little push (or pull) in the right direction.
amanda
Sorry... by "terminate" I mean the tablet is rebooted.
Update:
I've reflashed the original stock recovery - I wanted to see if it does auto-reboot the same way as CWM. It does! So, the issue is not with the CWM, but most likely with the kernel. Maybe some boot parameters influence the kernel when booting into recovery... This is driving me cuckoo.
amanda
Update:
OK, resolved. I had to add "write /sys/class/boot_monitor/boot_timer 0" to bootable/recovery/etc/init.rc file, and rebuild CWM.
amanda