[MOD] Unsecured boot.img for stock ICS

---

Hi fellows,

i've modified and repacked the stock boot.img that comes with the OTA upgrade of these days, to make adb working.

The only thing i modified is the ro.secure parameter, no tweaks, no other strange fixes (i like to have the most "stock version" as possible on my phone).

This mod is intended for who wants to use adb and don't want to flash a custom rom.

You can test this image rebooting your phone into bootloader and then

fastboot boot boot.img

then, if you like it, you can flash with

fastboot flash boot boot.img

hope you'll enjoy.

http://dl.dropbox.com/u/234100/boot.img

Thanks, works flawlessly.

glad it was useful to you

Thank you! Exactly what I was looking for!!!

Sorry, I did not understand the goal of this boot.

When should I use it and when it is not necessary?

I'm android modding noob sorry

i'll give you a practical example to let you understand

Pick a stock rom, flash the superuser binary and install the superuser apk from market, you're now rooted right?

Now let's assume you wanna remove the install-recovery.sh script from your phone, to avoid the clockwork overwriting after every reboot, to do that you must plug your phone via usb and launch "adb remount" to access /system in rw mode.

In this case you'll see a "permission denied", because your kernel ramdisk image is still secured.

Originally Posted by Lostpassword

i'll give you a practical example to let you understand

Pick a stock rom, flash the superuser binary and install the superuser apk from market, you're now rooted right?

Now let's assume you wanna remove the install-recovery.sh script from your phone, to avoid the clockwork overwriting after every reboot, to do that you must plug your phone via usb and launch "adb remount" to access /system in rw mode.

In this case you'll see a "permission denied", because your kernel ramdisk image is still secured.

question about this.

I wiped and installed the ICS zip file, no OTA. Bootloader is unlocked. flashed the CWM recovery. Flashed the for ICS updated SU (bin+app). Opened es file explorer and picked root and mount /system as rw. And I managed to rename the install-recovery.sh to .bak.

Never got the permission denied despite not having a unsecured boot.img.

You know why?

probably because file explorer is launching the full command as root (mount -o remount etc etc...), the unsecured boot image is needed when using ADB.

Originally Posted by Lostpassword

i'll give you a practical example to let you understand

Pick a stock rom, flash the superuser binary and install the superuser apk from market, you're now rooted right?

Now let's assume you wanna remove the install-recovery.sh script from your phone, to avoid the clockwork overwriting after every reboot, to do that you must plug your phone via usb and launch "adb remount" to access /system in rw mode.

In this case you'll see a "permission denied", because your kernel ramdisk image is still secured.

thank you lostpassword, then if I have understand (as you have written in forst post):

this is only for stock rom, Cyanogen 9 alpha 16 or NexusBeam, for example, don't have this problem (they have a different install-recovery.sh?)

But install-recovery.sh overwrite recovery at every reboot with sotck ROM? I did not know this. All stock ROM have it?

thanks very much, now my noob level is a bit more low

Yes, it's needed only for stock rom simply because every custom rom comes with an unsecured boot.img by default

The install-recovery.sh issue is related only to the nexus s, i don't know why google made this decision, but if you flash clockwork on a stock rom and reboot your phone you'll lose the custom recovery because of this script (is a well know issue, if you make a search into the forums you'll find the related topic).

Btw, that was an example, the unsecured boot.img let you use adb with your phone, and isn't strictly related to the install-recovery.sh issue