Database Info

Busybox problem

I've tried to flash multiple roms on my HTC Dream (t-mobile G1). Every time I flash something other than Cyanogen or complete Ecalir it says that there is an error on the SYSTEM busybox. I have the newest recovery mode on my phone. Can anyone tell me what i can do to fix this?

[Q] Can you retain the original recovery image with UnrEVOked?

I don't think this question has been asked before. I searched and couldn't see a duplicate.
I am interested in rooting my HTC Desire with UnrEVOked 3.21 (or better) but I really don't want to change the recovery image from the standard. The phone is a contract one with a long time still to run, so I really only want to enable the "su" functionality and not start flashing in custom ROMs.
So:
a) can UnrEVOked be told or altered to not attempt to flash a recovery image at all?
b) If a) cannot be done, can I substitute the "recovery.img" file that was shipped with the last FOTA download? This would flash back an identical copy to the one that's currently installed, resulting in a "no-op".
Thanks,
Z.

Some fastboot questions re: nexusS4G

I'm coming from a samsung vibrant on tmobile, I never used fastboot with my vibrant. I used adb alot, and this whole fastboot is new to me.
Is this something specific to sprint or specific to the nexus S bootloader?
on my vib I just rooted it and downloaded rom manager, went into the app and told it to flash the recovery and off I go, doesn't seem to be the case here. Here I use fastboot to flash an image, and it doesn't stick around although I heard theres a way to do it, maybe renaming the crespo image file or moving a script on the filesystem. Just trying to figure out the basics as to how they would relate to how I've been doing things for months already on the vibrant, was surprised that it was this different being from the same manufacturer.
-J

jbeez said:
I'm coming from a samsung vibrant on tmobile, I never used fastboot with my vibrant. I used adb alot, and this whole fastboot is new to me.
Is this something specific to sprint or specific to the nexus S bootloader?
on my vib I just rooted it and downloaded rom manager, went into the app and told it to flash the recovery and off I go, doesn't seem to be the case here. Here I use fastboot to flash an image, and it doesn't stick around although I heard theres a way to do it, maybe renaming the crespo image file or moving a script on the filesystem. Just trying to figure out the basics as to how they would relate to how I've been doing things for months already on the vibrant, was surprised that it was this different being from the same manufacturer.
-J
Click to expand...
Click to collapse
Fastboot is an open source utility for flashing. Once rooted you can use rom manager like any other phone. It's not necessary to use an exploit to gain root and then flash a recovery like most phones, you can just unlock the bootloader and flash it directly using fastboot. From there you can flash the such binary and do whatever you please.
There is a script that runs on boot and restores the stock recovery, /etc/install-recovery.sh. After you flash the su binary just rename this or delete it and your recovery will not be overwritten on boot.
Sent from my Nexus S using XDA Premium App

How to update kernel through update.zip possible?

So i have done some research and i beleive the kernel that i flashed (Cant remeber which one it was) it has changed the driver in my phone to where no computer will recognize my phone. I have stock recovery but my phone is unlocked. So i am not able to fastboot or adb the phone to correct my mistake because no computer will recognize my phone. Question is, Is there anyway to change my kernel to stock through flashing an update.zip through stock recovery?

Hi Chris,
I am not an expert buy have you tried terminal emulator? That might work but you may need to have a non stock recovery to do this. Hope that helps.

Can't change splash screen with Rooted TMoUS OTA

I was able to change it easily on the original 2.3.3 ROM after root, cw mod, etc.
BUT, after installing the OTA (or one of the rooted OTA's on the forums), I can change things like permissions on system files, etc., can change up and down animations, etc., but can NOT change the splash screen using:
adb reboot bootloader
fastboot flash splash1 splash.img
This worked fine previously, but I just can't get it to work in the new OTA. Any ideas?
Thanks for your help.
EDIT: NEVERMIND - I'm an idiot, I was typing a wrong file name.