Database Develop

2.3.3 Keeps overwriting my custom recovery...

The title says it all, anyone experiencing similar issues ?
Running 2.3.3 thru manual updates with a stock recovery, then after everything was done I fastboot flashed amon RA's recovery and it keeps getting replaced with the stock recovery ... Not quite sure when it's doing it, working on that now.

Not sure, but I think this will happen as long as you're not rooted?
Stock 2.2 did the same thing to me...

I'm rooted via flashing Superuser zip from ChainsDD...

negroplasty said:
I'm rooted via flashing Superuser zip from ChainsDD...
Click to expand...
Click to collapse
Hmmm...yeah, I don't know what I'm talking about lol.
Seems like there was some kind of fix for this in 2.2 though...maybe Superboot? Maybe that's why I'm thinking it has to do with rooting? Think something has to change in boot.img?
EDIT: Have you tried using the rooted stock ROM in the dev section?

If you are upgrading to a non-modified stock rom, it will overwrite your custom recovery.
You need to flash a rooted stock rom to keep your custom recovery.
Edit: Oh and you need an unlocked bootloader to fastboot a custom recovery.

Thanks for your help guys, I guess I'll just flash one of the stock but rooted roms now that they're available... Don't know why I thought that would work come to think about it, it was hopeful thinking at best lol...
Thanks again.

Just look up how to stop this from happening on stock froyo roms.
A bone stock rom with just root will do the same thing that your current rom is doing.
Sent from my Nexus One using XDA App

negroplasty said:
The title says it all, anyone experiencing similar issues ?
Running 2.3.3 thru manual updates with a stock recovery, then after everything was done I fastboot flashed amon RA's recovery and it keeps getting replaced with the stock recovery ... Not quite sure when it's doing it, working on that now.
Click to expand...
Click to collapse
That is because there are two files in a stock ROM (/system/recovery-from-boot.p and /system/etc/install-recovery.sh) that flash the stock recovery every boot. You need to delete (or rename) those two files after flashing a stock ROM, and then re-flash your custom recovery.

efrant said:
That is because there are two files in a stock ROM (/system/recovery-from-boot.p and /system/etc/install-recovery.sh) that flash the stock recovery every boot. You need to delete (or rename) those two files after flashing a stock ROM, and then re-flash your custom recovery.
Click to expand...
Click to collapse
If you don't mind my asking what are the commands I can use to delete these files? I'm in the process of looking up how to do this but wanted to ask as well.

Foxwolfe said:
If you don't mind my asking what are the commands I can use to delete these files? I'm in the process of looking up how to do this but wanted to ask as well.
Click to expand...
Click to collapse
The easiest way would be to use Root Explorer, mount the /system partition as r/w, navigate to each of the two directories, long-press on the files and click delete.
Or you can do it in a terminal emulator: open a terminal and type the following commands:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
rm /system/recovery-from-boot.p
rm /system/etc/install-recovery.sh

Just flash this from recovery...
http://db.tt/cp7De8G
Sent from my Nexus One using XDA App

efrant said:
The easiest way would be to use Root Explorer, mount the /system partition as r/w, navigate to each of the two directories, long-press on the files and click delete.
Or you can do it in a terminal emulator: open a terminal and type the following commands:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
rm /system/recovery-from-boot.p
rm /system/etc/install-recovery.sh
Click to expand...
Click to collapse
Only the shell script has to be deleted. I'm not sure why everyone includes the other file as well.

GldRush98 said:
Only the shell script has to be deleted. I'm not sure why everyone includes the other file as well.
Click to expand...
Click to collapse
Not sure. The reason I do is because those are the two files that are added every time there is an update. Hence those are the two files I delete...

GldRush98 said:
Only the shell script has to be deleted. I'm not sure why everyone includes the other file as well.
Click to expand...
Click to collapse
What's the value in keeping the other file?
Sent from my Nexus One using XDA App

danger-rat said:
What's the value in keeping the other file?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
None really. It just seems weird to arbitrarily delete a file that does nothing on its own.

GldRush98 said:
None really. It just seems weird to arbitrarily delete a file that does nothing on its own.
Click to expand...
Click to collapse
Because it's bloat. Those are the two files used to reflash the stock recovery on each and every boot. They have no other purpose. Why keep one? Or the other? Why not just get rid of them both?

[How-To] Restoring Recovery when Device running - An easy way (CWM / Stock)

Restoring stock recovery: (without Download mode)
[Preparation]
Our FIH partition which you could see in download mode is huge. (Size: 105 MB Used: 43 MB only)
You could easily keep loads of file in this partition without any problem to your device. (I have not faced any, as of yet!)
Just keep a backup of stock recovery in the "image" folder itself with the name "stock_recovery.img" (size: 4.5 MB only)
[Optional] And backup of CWM recovery too with the name "cwm_recovery.img" (size: 5 MB)
[Requirement]
Rooted phone
Apps like: GScripts Lite or Any script manager or Terminal emulator
[How to restore]
Just run following commands using any script manager or save them in a ".sh" file and use
"sh script.sh" in terminal emulator.
Commands:
Code:
mkdir /sdcard/fih
mount -t vfat /dev/block/mmcblk0p1 /sdcard/fih/
cd /sdcard/fih/image/
mv ./stock_recovery.img ./recovery.img
cd /
umount /sdcard/fih
rm -r /sdcard/fih/
(You can use "cp" instead of "mv" if you are not going for warranty claiming and just wants to use stock recover.img. Replace "stock" with "cwm" if you want to use that)
Thats it!
Now restart your phone in recovery using any reboot apps with recovery reboot option or just type in terminal "reboot recovery". You will boot into your desired recovery.
[Note]
When you install any official "fb0" ROM your phone is no more rooted, so you will need to root your phone first before using these steps again.
[Disclaimer]
I am not to be held liable/responsible if you damage your phone by following/not following this thread.

Napstar said:
Restoring stock recovery:
[Preparation]
Our FIH partition which you could see in download mode is huge. (Size: 105 MB Used: 43 MB only)
You could easily keep loads of file in this partition without any problem to your device. (I have not faced any, as of yet!)
Just keep a backup of stock recovery in the "image" folder itself with the name "stock_recovery.img" (size: 4.5 MB only)
[Optional] And backup of CWM recovery too with the name "cwm_recovery.img" (size: 5 MB)
[Requirement]
Rooted phone
Apps like: GScripts Lite or Any script manager or Terminal emulator
[How to restore]
Just run following commands using any script manager or save them in a ".sh" file and use
"sh script.sh" in terminal emulator.
Commands:
Code:
mkdir /sdcard/fih
mount -t vfat /dev/block/mmcblk0p1 /sdcard/fih/
cd /sdcard/fih/image/
mv ./stock_recovery.img ./recovery.img
cd /
umount /sdcard/fih
rm -r /sdcard/fih/
(You can use "cp" instead of "mv" if you are not going for warranty claiming and just wants to use stock recover.img. Replace "stock" with "cwm" if you want to use that)
Thats it!
Now restart your phone in recovery using any reboot apps with recovery reboot option or just type in terminal "reboot recovery". You will boot into your desired recovery.
[Note]
When you install any official "fb0" ROM your phone is no more rooted, so you will need to root your phone first before using these steps again.
[Disclaimer]
I am not to be held liable/responsible if you damage your phone by following/not following this thread.
Click to expand...
Click to collapse
i have much more easier way..
try this
put this phone in the download mode (power + volume up key)
connect to pc
open the drive as it will be shown as a usb storage
go to image folder..
copy your phone's stock version of recovery.img file paste to any drive of your pc .. woho backed up
now copy cwm recovery image
before copying rename it to recovery insteed to cwmrecovery
past to image folder of fih drive overwrite
done... you are now on clock work mode recovery

kshitij_bhatt said:
i have much more easier way..
try this
put this phone in the download mode (power + volume up key)
connect to pc
open the drive as it will be shown as a usb storage
go to image folder..
copy your phone's stock version of recovery.img file paste to any drive of your pc .. woho backed up
now copy cwm recovery image
before copying rename it to recovery insteed to cwmrecovery
past to image folder of fih drive overwrite
done... you are now on clock work mode recovery
Click to expand...
Click to collapse
True...
That's the most generic way to that, but it requires those tedious button pressings.
And also it requites a PC!!
My method can be used if you are on the go and still wants to restore any recoveries.
Sent from my CSL-MI410

Napstar said:
True...
That's the most generic way to that, but it requires those tedious button pressings.
And also it requites a PC!!
My method can be used if you are on the go and still wants to restore any recoveries.
Sent from my CSL-MI410
Click to expand...
Click to collapse
hehehe i found a on the go method too...
if you have root access and can install root explorer then just do this
go to root explorer
locate sdcard
select the image file you copied on it and press and hold over it
now select copy
press back now you r in root menu .. locate fih
find iamge folder in it
and paste if asked over write if not backup old one and chage present one as recovery Remember recovery and NOT Recovery
and you r done

kshitij_bhatt said:
hehehe i found a on the go method too...
if you have root access and can install root explorer then just do this
go to root explorer
locate sdcard
select the image file you copied on it and press and hold over it
now select copy
press back now you r in root menu .. locate fih
find iamge folder in it
and paste if asked over write if not backup old one and chage present one as recovery Remember recovery and NOT Recovery
and you r done
Click to expand...
Click to collapse
Well, that's good news then..
But as far as I remember there is no fih folder in root of the system unless it is mounted by some init script.
Which is your current rom?
Sent from my CSL-MI410 using Tapatalk

Napstar said:
Well, that's good news then..
But as far as I remember there is no fih folder in root of the system unless it is mounted by some init script.
Which is your current rom?
Sent from my CSL-MI410 using Tapatalk
Click to expand...
Click to collapse
You can only access it in download mode as far as I know.

Sergekarol said:
You can only access it in download mode as far as I know.
Click to expand...
Click to collapse
No. Thats not the only way.
Thats why I have created this thread to show the other possible way to access it when your phone is booted and running.

Napstar said:
Well, that's good news then..
But as far as I remember there is no fih folder in root of the system unless it is mounted by some init script.
Which is your current rom?
Sent from my CSL-MI410 using Tapatalk
Click to expand...
Click to collapse
well at that time i was on the tj_style's custom rom rc2 and i found that folder in root explorer ... i think .. confused..
aannnn any way i m a new B what else can u expect

kshitij_bhatt said:
well at that time i was on the tj_style's custom rom rc2 and i found that folder in root explorer ... i think .. confused..
aannnn any way i m a new B what else can u expect
Click to expand...
Click to collapse
No problem dude!
Anyway I will be posting a completely new recovery soon. This will have both stock recovery and cwm recovery access simultaneously. (Hopefully )
So this How-To wont be required then...

Napstar said:
No problem dude!
Anyway I will be posting a completely new recovery soon. This will have both stock recovery and cwm recovery access simultaneously. (Hopefully )
So this How-To wont be required then...
Click to expand...
Click to collapse
Coool .... koi mujhe bhi accha sa teacher bata do jo ye saab developing and all mujhe bhi sikha de... Vb se aage kabhi kuch sikh hi nahi paya main to

kshitij_bhatt said:
Coool .... koi mujhe bhi accha sa teacher bata do jo ye saab developing and all mujhe bhi sikha de... Vb se aage kabhi kuch sikh hi nahi paya main to
Click to expand...
Click to collapse
Google

kshitij_bhatt said:
Coool .... koi mujhe bhi accha sa teacher bata do jo ye saab developing and all mujhe bhi sikha de... Vb se aage kabhi kuch sikh hi nahi paya main to
Click to expand...
Click to collapse
What does this mean?

ardX said:
What does this mean?
Click to expand...
Click to collapse
He is asking napster for a teacher to teach development...
Sent from my CSL-MI410 using XDA App

bandukia said:
He is asking napster for a teacher to teach development...
Sent from my CSL-MI410 using XDA App
Click to expand...
Click to collapse
hehehe yaa i wanna learn development programming and i got my teacher GOOGLE

nb0 files through CWM????
when napstar???

bandukia said:
nb0 files through CWM????
when napstar???
Click to expand...
Click to collapse
Finally its done!!
[RecoveryMenu] CWM based Recovery menu to enter stock or CWM recovery
Enjoy!!

Napstar said:
Finally its done!!
[RecoveryMenu] CWM based Recovery menu to enter stock or CWM recovery
Enjoy!!
Click to expand...
Click to collapse
@Napstar .... You are Gr8 nicely done work...

Napstar said:
Finally its done!!
[RecoveryMenu] CWM based Recovery menu to enter stock or CWM recovery
Enjoy!!
Click to expand...
Click to collapse
lol..that was fast.. thnx

bandukia said:
lol..that was fast.. thnx
Click to expand...
Click to collapse
Was debugging it for last few days. It was just finished yesterday and since you asked so here it is.

Napstar said:
Restoring stock recovery: (without Download mode)
[Preparation]
Our FIH partition which you could see in download mode is huge. (Size: 105 MB Used: 43 MB only)
You could easily keep loads of file in this partition without any problem to your device. (I have not faced any, as of yet!)
Just keep a backup of stock recovery in the "image" folder itself with the name "stock_recovery.img" (size: 4.5 MB only)
[Optional] And backup of CWM recovery too with the name "cwm_recovery.img" (size: 5 MB)
[Requirement]
Rooted phone
Apps like: GScripts Lite or Any script manager or Terminal emulator
[How to restore]
Just run following commands using any script manager or save them in a ".sh" file and use
"sh script.sh" in terminal emulator.
Commands:
Code:
mkdir /sdcard/fih
mount -t vfat /dev/block/mmcblk0p1 /sdcard/fih/
cd /sdcard/fih/image/
mv ./stock_recovery.img ./recovery.img
cd /
umount /sdcard/fih
rm -r /sdcard/fih/
(You can use "cp" instead of "mv" if you are not going for warranty claiming and just wants to use stock recover.img. Replace "stock" with "cwm" if you want to use that)
Thats it!
Now restart your phone in recovery using any reboot apps with recovery reboot option or just type in terminal "reboot recovery". You will boot into your desired recovery.
[Note]
When you install any official "fb0" ROM your phone is no more rooted, so you will need to root your phone first before using these steps again.
[Disclaimer]
I am not to be held liable/responsible if you damage your phone by following/not following this thread.
Click to expand...
Click to collapse
But then I cannot start up my phone! It vibrates and the download screen show up! Help! ( csl mi410 )
Any advices is really appreciated!

[ROM] STOCK Android 3.2.1 v3.2.79 -rooted- ext4/squashfs for SDE

First ....THANKS @letama, and last but not least thanks to @tRAcE3k for .ext4 build.
Official Stock Firmware v3.2.79 => ROOT, Update : Su binary v3.0.3.2, Superuser v3.0.7 and busybox v1.19.3, Add : enables vibrator and adjust volume !
(There is no need to install busybox.apk or busybox installer.apk from market, busybox is already installed into /system/xbin/ - only for .ext4)
This ROM is only for SDE enable ( recovery) ....you can use it as a daily ROM...
These are the files you need :
- zImage => http://www.4shared.com/file/KXp8bLDa/zImage.html
- initramfs.cpio.gz => http://www.4shared.com/archive/6Y9sMqJ5/initramfscpio.html
- archos_3.2.79.squashfs => http://www.4shared.com/zip/-vo5gkRr/firmware_3279squashfs.html (...version without busybox and update!)
- archos_3.2.79.ext4 => http://www.4shared.com/zip/dmrcBtJM/3279_updat.html
How install this :
- connect device via USB cable
- adb push archos_3.2.79.squashfs data/media/ ........for read-only /system
- adb push archos_3.2.79.ext4 data/media/..............for read-write /system and other stuff
- reboot into recovery , Recovery System-> Developer Edition Menu -> Remove Kernel ( for boot only to SDE) -> I Understand -> Ok -> Developer Edition Menu -> Flash Kernel and Initramfs -> copy zImage and initramfs into new driver -> Ok ! that's all

hi, If I have your archos_3.2.78.ext4, can I copy only archos_3.2.79.ext4 to data/media? Or for every new rom is always necessary copy even zImage and initramfs.cpio.gz? thank you

hitman72 said:
hi, If I have your archos_3.2.78.ext4, can I copy only archos_3.2.79.ext4 to data/media? Or for every new rom is always necessary copy even zImage and initramfs.cpio.gz? thank you
Click to expand...
Click to collapse
No, you have to flash zImage and initramfs.cpio.gz in sde developer menu each time. First, filename changed and it's hardcoded in initramfs, second, Archos bugfixes are also in the kernel so new zImage is required.
Thanks surdu_petru for taking the relay!

letama said:
No, you have to flash zImage and initramfs.cpio.gz in sde developer menu each time. First, filename changed and it's hardcoded in initramfs, second, Archos bugfixes are also in the kernel so new zImage is required.
Thanks surdu_petru for taking the relay!
Click to expand...
Click to collapse
old firmware (3.2.77 etc) must be removed manually from device?

ext link is invalid "......". ciao ;-)

gegabit said:
old firmware (3.2.77 etc) must be removed manually from device?
Click to expand...
Click to collapse
When everything works, yes, you can remove the previous .ext4 from internal storage. That's the only thing you have to remove.

hitman72 said:
ext link is invalid "......". ciao ;-)
Click to expand...
Click to collapse
now its upload to share.
- archos_3.2.79.ext4 => /.......future upload ..... it's 512Mb ext4...........
Click to expand...
Click to collapse

Hi Folks.
Thought I'd do my bit. Here are some more sources to download the ext4 firmware.zip
http://www.multiupload.com/0OTX0D54XW
Thanks to surdu_petru for the original image and tRAcE3k for the repacking instructions in this post.
Thanks
Trev

hitman72 said:
hi, If I have your archos_3.2.78.ext4, can I copy only archos_3.2.79.ext4 to data/media? Or for every new rom is always necessary copy even zImage and initramfs.cpio.gz? thank you
Click to expand...
Click to collapse
[email protected] sure is right....on the ather hand, every new firmware ( ex. firmware_archos_it4.aos) has its own boot image ( boot.img = zImage + initramfs) -used to boot devices and has its own flash files / system files which are grouped in an archive ( contains - libraries, aplikations, and other stuff ) - used to run system android , and all these are closely linked ....I think you can now better understand how to use them, and why ......

hitman72 said:
ext link is invalid "......". ciao ;-)
Click to expand...
Click to collapse
Ok...Now is valid link : http://www.4shared.com/zip/bp7XjWzY/archos_3279ext4.html....
Good luck!

Downloaded the ext4 version and couldn't get it to work.
Only root through the ADB Shell functioned, anything else Superuser automatically got denied, even though in the Superuser app it was set to prompt.
Chmodded the su binary to 6755 and it started to work

droobey said:
Downloaded the ext4 version and couldn't get it to work.
Only root through the ADB Shell functioned, anything else Superuser automatically got denied, even though in the Superuser app it was set to prompt.
Chmodded the su binary to 6755 and it started to work
Click to expand...
Click to collapse
Ok! Now just upload new update .....

First off Thanks very much surdu_petru for the work!
Please excuse my novice ability here, but...
I'm not sure if I did everything correctly, but I don't have root anymore. (i did with 3.2.78)
I did the adb push of the archos_3.2.79 to /data/media
then did the flash of intramfs and zImage from the beginning of this post.
I rebooted into developer and Root Checker says i don't have Root anymore?
Do i need to chmod the SU binary now to fix? if so where is the SU binary located in the filesystem? (i'm not sure how i would execute that command, via adb?)

revere521 said:
First off Thanks very much surdu_petru for the work!
Please excuse my novice ability here, but...
I'm not sure if I did everything correctly, but I don't have root anymore. (i did with 3.2.78)
I did the adb push of the archos_3.2.79 to /data/media
then did the flash of intramfs and zImage from the beginning of this post.
I rebooted into developer and Root Checker says i don't have Root anymore?
Do i need to chmod the SU binary now to fix? if so where is the SU binary located in the filesystem? (i'm not sure how i would execute that command, via adb?)
Click to expand...
Click to collapse
OK! Try >adb shell chmod 6755 system/bin/su

Thanks!
I ran adb shell chmod 6755 system/bin/su, the rebooted into developer again.
In file explorer, SU is listed as Readable:Yes Writable:no and hidden:no
Root Checker Basic still says i don't have proper root access, titanium backup and busybox show denied in the log.
I broke it lol, maybe i need to try again from the beginning.

revere521 said:
Thanks!
I ran adb shell chmod 6755 system/bin/su, the rebooted into developer again.
In file explorer, SU is listed as Readable:Yes Writable:no and hidden:no
Root Checker Basic still says i don't have proper root access, titanium backup and busybox show denied in the log.
I broke it lol, maybe i need to try again from the beginning.
Click to expand...
Click to collapse
same problem here the chmod doesn't solve it.
Eacy root command runed gets a deny from superuser even when tel superuser to allow everything

revere521 said:
Thanks!
I ran adb shell chmod 6755 system/bin/su, the rebooted into developer again.
In file explorer, SU is listed as Readable:Yes Writable:no and hidden:no
Root Checker Basic still says i don't have proper root access, titanium backup and busybox show denied in the log.
I broke it lol, maybe i need to try again from the beginning.
Click to expand...
Click to collapse
.....after install all....try to update Superuser into Market......

Update doesn't help :-(
surdu_petru said:
.....after install all....try to update Superuser into Market......
Click to expand...
Click to collapse
Update doesn't help :-(
tryed the update fix of superuser also
Update of the su binarie failde at md5sum check

basd82 said:
Update doesn't help :-(
tryed the update fix of superuser also
Update of the su binarie failde at md5sum check
Click to expand...
Click to collapse
OK I know.....just wait max 1 hour and I'll uploaded the new archos_3.2.79 files...with it everything works perfectly ( I have tested all , root_explorer, es file explorer, Root Check ....it's OK !!!!!).

basd82 said:
same problem here the chmod doesn't solve it.
Eacy root command runed gets a deny from superuser even when tel superuser to allow everything
Click to expand...
Click to collapse
ok! but now problem was solved.....just redownload the new firmware_3.2.79 files , unpack and enjoy*

Nexus S & Galaxy Nexus one click root toolkit ! Unlock bootloader+CWM+Su(or)SuperSu

Nexus S & Galaxy Nexus one click root toolkit ! Unlock bootloader+CWM+Su(or)SuperSu
This tool will root you nexus s/Galaxy Nexus install su or super su and ClockWorkMod recovery!!
For Nexus S:4G,I9020T,I9023,I9020A.
Galaxy Nexus:GSM/Verizon/Sprint
Disclaimer!
Your warranty is now void.
I am not responsible for bricked or damaged devices
YOU are choosing to make these modifications.
Click to expand...
Click to collapse
DOWNLOAD
Click to expand...
Click to collapse
Current Version (Nexus S + Galaxy Nexus) 3.5: http://d-h.st/qaL
MIRROR:http://www.mediafire.com/download.php?1if2rvgpcte2rcs
Old versions:
3.0: http://d-h.st/mhO
2.0: http://dev-host.org/gcZ (nexus s only)
1.0: http://dev-host.org/bEE (nexus s only)
HOW-TO
Click to expand...
Click to collapse
just unzip the content and run the tool ! drivers are included in case you need them.
incase you had any problems try rerunning the tool,and if you got superuser/supersu app but you are unable to use root apps,update superuser/supersu from the play store then update the binary from inside the app.
CHANGELOG
Click to expand...
Click to collapse
V3.5
-added support for jelly bean
-few script optimization
-updated superuser and supersu
V3.0
-added support to galaxy nexus and all it's variants.
-added support to install super su.
-moved from *.bat to *.exe
-new icon
-su/super su, will now automatically flash no need to touch "install zip"
-skip bootloader unlock if you are already unlocked.
-update drivers
V2.0
-Removed "sticky.bat"
-modified su flashing script.
-the recovery now will stick automatically no need to flash any file after rooting or running any script.
V1.0
-initial release
ALL DATA WILL BE WIPED FROM DEVICE(only if bootloader is locked)
credits
-Chainfire for super su
-ChainsDD for superuser
-Pdanet for drivers
-Clockworkmod team for recovery
-my friend for the icon​

am i going to loose everithing on USB storage ? or jjust sistem data ? i have to have a full rom right ?

raducux said:
am i going to loose everithing on USB storage ? or jjust sistem data ? i have to have a full rom right ?
Click to expand...
Click to collapse
if your bootloader is locked then yes you will loose everything on USB storage,if the bootloader is already unlocked you will not loose any data,you don't need to flash a rom after rooting the device as it will not wipe the system.

Hi, I installed the drivers on my computer and am currently running the run.bat file. It's saying my device is not found. I have USB Debugging on, and USB storage is on. Any ideas?

Sticky please
Can i replace CWR with newest img version?
PLEASE STICKY THIS THREAD ON TOP.

Romaniac said:
Hi, I installed the drivers on my computer and am currently running the run.bat file. It's saying my device is not found. I have USB Debugging on, and USB storage is on. Any ideas?
Click to expand...
Click to collapse
Turn off the usb storage,you just need usb debugging enabled if you turned on usb storage it will not work
stewie-droid said:
Can i replace CWR with newest img version?
PLEASE STICKY THIS THREAD ON TOP.
Click to expand...
Click to collapse
The tool includes the latest cwm img,but if you want to replace it with another one you can do,just make sure you rename it to same name of the img in the root tool folder,but make sure that the recovery you will use is compatible with the nexus s

After I execute run.bat the phone is rooted. I reboot using ClockWorkMod Recovery. Then, when I run sticky.bat and follow the instructions I get the following:
[email protected]:/ $ su
su
[email protected]:/ # rm /etc/installrecovery.sh
rm /etc/installrecovery.sh
rm failed for /etc/installrecovery.sh, No such file or directory
What should I be doing? Please help.

Ritwik7 said:
After I execute run.bat the phone is rooted. I reboot using ClockWorkMod Recovery. Then, when I run sticky.bat and follow the instructions I get the following:
[email protected]:/ $ su
su
[email protected]:/ # rm /etc/installrecovery.sh
rm /etc/installrecovery.sh
rm failed for /etc/installrecovery.sh, No such file or directory
What should I be doing? Please help.
Click to expand...
Click to collapse
The phone should booted normally when running the sticky.bat (On the home screen),there is nothing to worry about just Complete the instructions normally one of the two scripts will fail since the name of the file differ in gingerbread and ics,try this rm /etc/install-recovery.sh and continue the instruction it should work and clockworkmod recovery would stick.

Thanks for your reply. I used a FixRecovery.zip file from another thread and flashed it after executing run.bat again. Now I am able to boot into ClockWorkMod.

Ritwik7 said:
Thanks for your reply. I used a FixRecovery.zip file from another thread and flashed it after executing run.bat again. Now I am able to boot into ClockWorkMod.
Click to expand...
Click to collapse
My friend can you guide where i can find this .zip because i m facing the same problem.thank you in advance

Ok I got it to stick by using Root Explorer to mount it as read/write first then ran the sticky.bat. ICS is the rm /etc/install-recovery.sh command.

m.sabra said:
The phone should booted normally when running the sticky.bat (On the home screen),there is nothing to worry about just Complete the instructions normally one of the two scripts will fail since the name of the file differ in gingerbread and ics,try this rm /etc/install-recovery.sh and continue the instruction it should work and clockworkmod recovery would stick.
Click to expand...
Click to collapse
I tried this and when I want to do the sticky.bat, when I type the "rm /etc/install-recovery.sh" it sais rm failed for /etc/.., Read-only file system

I had the same problem with sticky.bat.
Once you 're done with run.bat and it reboots in cwm just flash fix-recovery.zip
http://forum.xda-developers.com/showthread.php?p=20432966&highlight=fix-recovery#post20432966

karx23 said:
I had the same problem with sticky.bat.
Once you 're done with run.bat and it reboots in cwm just flash fix-recovery.zip
http://forum.xda-developers.com/showthread.php?p=20432966&highlight=fix-recovery#post20432966
Click to expand...
Click to collapse
thanks ! added the link to the OP in case anyone had problems like this.

Argh, I seem to have successfully unrooted my Nexus S 9020t and had it rebooted back in, but while it was booting up again I accidentally pressed a button and it told me "error: device not found" twice followed by "<waiting for device>".
Unfortunately my phone has already been rebooted, but it still seems to be waiting for my device. I'm not sure if I can disconnect this device from USB while this is going on, so uh, what do I do?
Edit: Disconnected and reconnected the USB cable on the phone to see what would happen, and it seems to be ok. I'm still stuck on "waiting for device" though. Should I consider restarting the process again?
Edit Edit: Decided to just try to redo the process all over again...seems to have worked!

Updated tool to version 2.0 ! check the changelog in OP, it should solve all sticky recovery related problems,as i removed sticky.bat and now the recovery will stick automatically without the need of running any commands or flashing any fixes.
thanks for reporting problems and feedbacks

thank you for this

Okay, I've tried to run this but it always fails at flashing the recovery.. Any help?

Lelouche said:
Okay, I've tried to run this but it always fails at flashing the recovery.. Any help?
Click to expand...
Click to collapse
Ok first have you unlocked your bootloader when the tool asked you to use volume buttons to chose yes and unlock ? (If you did this you should see an unlocked lock under google logo when booting the phone) if you didn't just run the script again and unlock the bootloader.
Are the drivers installed properly ? When you connect the phone to the pc check device manager to see if the PC recognizes the phone (the drivers are included in the tool in case you need them .
And last check the root tool folder on your pc it should have a file called cwm.img if it doesn't then download the tool again.

SuperUser is not visible after the process
I am on stock ICS, I had previously unlocked the bootloader, then I did the whole process mentioned in this thread. It showed me the CWM menu but when I did the reboot, I couldn't find the superuser app. Then to test whether it is rooted or not, I installed titanium backup but it says the device isnt rooted. What to do now? I tried SuperOneClick but it doesn't seem to work.
Edit: Thanks guys, sorry. It was my mistake, I didnt do the whole process in a right way. It is working as expected.

[Offering] CWM 6 recovery for Stock ICS with new bootloader [new: v28G based]

I've successfully ported / combined wkpark's CWM5 for early P990 ICS build to the latest v28G build and its completely different recovery.img
Update Nov 12: re-based on different CWM 5 and the latest v28G recovery image base. Update recommended!
Update Nov 15: re-based on CWM 6 and the latest v28G recovery image base. Update recommended! No more big font!
Requirements: Stock v28E ICS or later => new partitioning structure, new bootloader (unlocked)
Download: look at the bottom
Installation:
Installation directly on the phone using dd with root permission
when you have already rooted your device you can use "dd" to install cwm.img
like as following
(using adb shell or terminal app) - type the following things in terminal (first copy the recovery image you want to install to your internal SD card):
Code:
su
dd if=/dev/block/mmcblk0p8 of=/sdcard/backup-recovery.img
dd if=/sdcard/[B]<putNameOfRecoveryImageHere>[/B].img of=/dev/block/mmcblk0p8
Click to expand...
Click to collapse
Installation via NVFlash:
- Download NVFlash version of v28G-based CWM 6 recovery here: Not yet available
- extract archive, connect phone in NVFlash mode (search yourself how to do it, explained in my ROM threads as well), run flash-recovery.bat (Windows only)
Click to expand...
Click to collapse
If you get error messages in CWM, stating that /cache can't be mounted: just format /cache partition in CWM
Click to expand...
Click to collapse

thanks mate.....

Under usb debugging mode i flashed it. but when i try to enter cwm, an android with spinning cube appears and phone restarts. It erased my internal memory and it starts with 'welcome' wizard'

naazgulla said:
Under usb debugging mode i flashed it. but when i try to enter cwm, an android with spinning cube appears and phone restarts. It erased my internal memory and it starts with 'welcome' wizard'
Click to expand...
Click to collapse
I can confirm this ! happened to me too !

I cant install I think it cant mount data for r/w or something (i've unlocked bootloader). Also i cant do remount because when i enter adb remount i get this:
remount failed: Operation not permitted

Didn't happen for me. I flashed it directly from the phone without adb.
Also I don't understand why you execute the psneuter exploit Stefan? It is more than sufficient to just do the dd if=/location/to/recovery of=/destination part.
Maybe the psneuter exploit does something with the internal storage??

TheSSJ said:
Didn't happen for me. I flashed it directly from the phone without adb.
Also I don't understand why you execute the psneuter exploit Stefan? It is more than sufficient to just do the dd if=/location/to/recovery of=/destination part.
Maybe the psneuter exploit does something with the internal storage??
Click to expand...
Click to collapse
Ok, I did:
[email protected]:/sdcard # dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p8
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p8
13680+0 records in
13680+0 records out
7004160 bytes transferred in 2.740 secs (2556262 bytes/sec)
BR.
Edit: backing up ICS v28E rom

TheSSJ said:
Didn't happen for me. I flashed it directly from the phone without adb.
Also I don't understand why you execute the psneuter exploit Stefan? It is more than sufficient to just do the dd if=/location/to/recovery of=/destination part.
Maybe the psneuter exploit does something with the internal storage??
Click to expand...
Click to collapse
Can u please elaborate on your method?

naazgulla said:
Can u please elaborate on your method?
Click to expand...
Click to collapse
Copy the recovery.img to your /sdcard/ and then do as stated in this post:
http://forum.xda-developers.com/showpost.php?p=34001124&postcount=7

Stefan Gündhör said:
I've successfully ported / combined wkpark's CWM5 for early P990 ICS build to the latest v28E build and its completely different recovery.img
When from CWM connecting to PC as mass storage, you can access both SD cards.
Also you can most of the times directly boot to CWM using the well known VOL DOWN + POWER
Requirements: Stock v28E ICS or later => new partitioning structure, new bootloader (unlocked)
Download: http://d-h.st/5e5
Installation: Unpack, connect phone via adb, then run either Windows, Linux, or Mac script (thanks to Harsh for the scripts!)
Click to expand...
Click to collapse
Sorry, could you possibly point me to how to connect the phone in ADB mode. I know APX, but not ADB.
Thx so much

i did the dd thing but how can i enter recovery mode?? I tried su, reboot recovery. Doesnt work.

wawyed said:
i did the dd thing but how can i enter recovery mode?? I tried su, reboot recovery. Doesnt work.
Click to expand...
Click to collapse
Shutdown your phone. Then keep volume down button AND power button pressed until you are in recovery mode. Important: BOTH pressed constantly.

I have 28e version of ics and root with smarthflash and i can´t instal cwm =(
C:\Users\rogerio.figueiredo\Desktop\cwm5-p990-ICS-for_unlocked_new_bootloader\cw
m5-p990-ICS-for_unlocked_new_bootloader>adb-windows push psneuter /data/local/ps
neuter
failed to copy 'psneuter' to '/data/local/psneuter': No such file or directory
C:\Users\rogerio.figueiredo\Desktop\cwm5-p990-ICS-for_unlocked_new_bootloader\cw
m5-p990-ICS-for_unlocked_new_bootloader>adb-windows shell chmod 4755 /data/local
/psneuter
- exec '/system/bin/sh' failed: No such file or directory (2) -
C:\Users\rogerio.figueiredo\Desktop\cwm5-p990-ICS-for_unlocked_new_bootloader\cw
m5-p990-ICS-for_unlocked_new_bootloader>adb-windows shell /data/local/psneuter
- exec '/system/bin/sh' failed: No such file or directory (2) -
C:\Users\rogerio.figueiredo\Desktop\cwm5-p990-ICS-for_unlocked_new_bootloader\cw
m5-p990-ICS-for_unlocked_new_bootloader>adb-windows wait-for-device

TheSSJ said:
Shutdown your phone. Then keep volume down button AND power button pressed until you are in recovery mode. Important: BOTH pressed constantly.
Click to expand...
Click to collapse
DO NOT do that . there's something wrong with the recovery ! it wipes /data !!

For those having trouble copy recovery.img to internal sd. Open terminal and type su and grant permission. Then type
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p8
Mind the spaces.
Then type reboot.
Done!
Sent from my LG-P990 using xda app-developers app

thamerkh said:
DO NOT do that . there's something wrong with the recovery ! it wipes /data !!
Click to expand...
Click to collapse
The recovery is fine but the flashing part seems to be broken. I've removed the link for now and might add it lateron with a new flashing method.

Is it only me but I can't access my external SD after booting into CWM. Only internal. Just letting u know. Thx!

Peteflyman said:
Is it only me but I can't access my external SD after booting into CWM. Only internal. Just letting u know. Thx!
Click to expand...
Click to collapse
ITs working fine for me....just flashed new 28g rom and addons from external sd. Although log was showing lot of errors...but it was opening. Try going to mounts and storage and mount external sd from there.. just a thought.

naazgulla said:
ITs working fine for me....just flashed new 28g rom and addons from external sd. Although log was showing lot of errors...but it was opening. Try going to mounts and storage and mount external sd from there.. just a thought.
Click to expand...
Click to collapse
I will provide a new recovery.img soon, based on v28G

naazgulla said:
Try going to mounts and storage and mount external sd from there.. just a thought.
Click to expand...
Click to collapse
Yea, forgot to mention that I tried that but no success. Will try to reboot a third time and in case not working I'll reflash again and see if it makes any difference.