2.3.3 Keeps overwriting my custom recovery... - Nexus One Q&A, Help & Troubleshooting

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?

Related

how should i change a rom from 1 to another?

??????????????
tink-14 said:
??????????????
Click to expand...
Click to collapse
more info on how your doing it....
generally
Alt-w
Alt-s
i mean like is it as easy as wipe and ad flash new rom on
I actually really recommend the switchrom.sh script over in the development section on the forum. You just make a backup using the script, then flash the new one (alt-w, alt-s), and if you ever want to go back, restore the backup. It works a little nicer than nandroid in the fact that it keeps all your apps, as well as app data, so you don't have to set everything back up, log in, stuff like that.
tink-14 said:
i mean like is it as easy as wipe and ad flash new rom on
Click to expand...
Click to collapse
Generally. If you have your apps on an ext partition and your phone bootloops after flashing a new ROM, you may need to wipe it.
If you do get a bootloop, type this in the recovery console, then wipe and reflash the ROM.
Code:
mount -o rw /dev/block/mmcblk0p2 /system/sd
rm -r /system/sd/*
If I have cyan's stable build and I just got the app from the market that can check for updates to his ROMs, can I just use that app to do everything? I am not familiar with how it works. Sounds like it is based off of JFs if anyone uses it.

[Q] Q. Is it possible to unwittingly lose Custom Recovery? Please Help.

Firstly, my nexus one is Locked + Rooted with Stock FRF91.
OK, So I rooted with 1-click, installed a custom recovery (first Clockwork then Amon RA 1.8.0.0).
Did a full backup
Tried out a couple of Roms
Reverted to Stock from backup. All good!
Now 1 week later, I really want to try MiUI Rom so I power on phone with VOL-, select Recovery - all I see is the yellow exclamation in a white triangle with a green Android below. Isn't that normal / stock recovery???
Could the FRG83 OTA that I have not installed (it is still bugging me to do so ) have restored the stock recovery?
Did I clear something / do something wrong when performing the Stock backup or restore?
TIA for any advice.
The OTA update did install, and in the process replaced install-recovery.sh and recovery-from-boot.p, which meant that the stock recovery was automatically reinstalled by the OS on reboot.
Hi rusty, thanks for the reply. I have not installed the update, it is still asking to be installed. I even checked the build number in about phone - frf91.
Are you saying that with out my explicit permission the ota has modified my phone and restored the stock recovery - that certainly would explain it.
I misread your post, sorry about that.
However, restoring your backup is probably the cause, due to the same reasons above.
To simplify, you can lose your recovery in this fashion:
Start with stock ROM
Root
Install custom recovery without removing the .sh and .p files mentioned
Boot up phone
Now, if you install custom recovery using several automated methods, OR manually remove the files previously mentioned in thread, no problem. But if those files remain the stock ROM will automatically run them and restore the recovery image. Happens to a lot of people.
So likely that's what happened; restoring and using your stock ROM had those scripts in the image.
khaytsus said:
To simplify, you can lose your recovery in this fashion:
Start with stock ROM
Root
Install custom recovery without removing the .sh and .p files mentioned
Boot up phone
Now, if you install custom recovery using several automated methods, OR manually remove the files previously mentioned in thread, no problem. But if those files remain the stock ROM will automatically run them and restore the recovery image. Happens to a lot of people.
So likely that's what happened; restoring and using your stock ROM had those scripts in the image.
Click to expand...
Click to collapse
Thankyou both for your help. It makes a bit more sense now.
So in order to get back to a custom recovery, will I need to reinstall it or will removing these .sh and .p files do the trick?
Ps, what is the exact location of these and how would I delete them (i assume they are system/ protected)
Thanks, Steve.
You'll have to remove/rename the files and flash it again.
They are: /system/recovery-from-boot.p and /system/etc/install-recovery.sh
You could rename them:
Code:
mv /system/recovery-from-boot.p /system/recovery-from-boot.p.bak
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
or remove them altogether
Code:
rm /system/recovery-from-boot.p
rm /system/etc/install-recovery.sh
My advice would be to rename, just incase you feel like stock recovery again at some point.
Rusty! said:
You'll have to remove/rename the files and flash it again.
They are: /system/recovery-from-boot.p and /system/etc/install-recovery.sh
You could rename them:
Code:
mv /system/recovery-from-boot.p /system/recovery-from-boot.p.bak
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
Click to expand...
Click to collapse
Perfect. Understood.
I'll try to remember to update this thread with how I get on once i'm done but even if I dont, I think the info contained is pretty clear.
Thanks Rusty & khaytsus.
Also I'm pretty sure that if you use ROM Manager to flash custom recovery, it automatically zaps the files that would otherwise revert you to stock recovery.
Sent from my Nexus One using XDA App
I did use rom manager and I have since done clockworkmod through rom manager but when I go into recovery I get the stock one. that's why I did the manual process installing ra after clockwork the first time round.
Anyone else has that where rom manager seems to install the custom recovery but then when you go there its stock?

[HOWTO] get root back after ota update!

this is how i did it anyways. i had to flash the boot.img and update via stock recovery to get the ota to flash. but then no root!
so heres how i got it back:
download the superboot/paulobrien method (http://forum.xda-developers.com/showthread.php?t=882333).
boot phone to fastboot.
Code:
fastboot boot boot.superboot.img
let phone boot, open terminal, su, just to check.
reboot phone.
rooted and ota'd now!
I've got root back, but not by that method. I think it might be a mistake to flash that boot.img, as the 2.3.1 update patched boot.img... so replacing it with one from 2.3 might not be the best idea. But I guess no one really know what the changes might be.
I guess time will tell
The method I used was:
1. Boot into fastboot.
2.
Code:
fastboot flash recovery recovery-clockwork-3.0.0.0-crespo.img
3. Reboot from fastboot directly into recovery (not doing so will cause android to replace CWR).
4. Mount USB, copy su-2.3.6.1-ef-signed.zip to the /sdcard via windows/linux
5. Mount /system
6. Install update from zip (browse to were you put su-2.3.6.1-ef-signed.zip).
7. Install it, and reboot.
8. open root explorer, and rename /etc/install-recovery.sh to install-recovery.sh.old
9. open ROM Manager, reflash CWR.
now you are all done, rooted, w/ CWR
I reflashed CWM, then from CWM, remounted /system, then used adb to chmod 6775 su. That restored root pretty easily.
What Recovery image are you using? Are you able to get into it consistently? I can't from fastboot except for if I immediately hit it up after flashing CWM with fb, or from ROM Manager (flash from RM, then select reboot to recovery).
Luxferro said:
I've got root back, but not by that method. I think it might be a mistake to flash that boot.img, as the 2.3.1 update patched boot.img... so replacing it with one from 2.3 might not be the best idea. But I guess no one really know what the changes might be.
I guess time will tell
Click to expand...
Click to collapse
its not flashing it. read the command. its only booting to that image to install su. then reboot will bring you back to stock 2.3.1 boot.img.
distortedloop said:
I reflashed CWM, then from CWM, remounted /system, then used adb to chmod 6775 su. That restored root pretty easily.
What Recovery image are you using? Are you able to get into it consistently? I can't from fastboot except for if I immediately hit it up after flashing CWM with fb, or from ROM Manager (flash from RM, then select reboot to recovery).
Click to expand...
Click to collapse
im using stock recovery.
I'm rooted on 2.3.1 but I lose clockwork recovery when I reboot an gota reflash it using rom manager. Anyone having this problem
k0mpresd said:
its not flashing it. read the command. its only booting to that image to install su. then reboot will bring you back to stock 2.3.1 boot.img.
Click to expand...
Click to collapse
Sure it is. But on Android bootup, a script is running somewhere to replace it with stock recovery. They did this on Droid_1 after the first or second update (that's my only other android phone... so my android experience is limited).
edit: I just found the script. It's /etc/install-recovery.sh .... just renamed my to install-recovery.sh.old. gonna reflash CWR and test it now.
edit2: yep, works great now. CWR, and retained my 2.3.1 boot.img
So is this something that the devs of clockworkmod need to fix in order to not lose clockwork recovery when u reboot the phone
chris6278 said:
So is this something that the devs of clockworkmod need to fix in order to not lose clockwork recovery when u reboot the phone
Click to expand...
Click to collapse
No, it's a safety mechanism so you can't lose recovery... It has nothing to do with clockworkmod. Someone can make a root script or app that disables it easily. Or people can just do it themselves manually.
edit: actually, all that needs to be done is add some code to the update script inside su-2.3.6.1-ef-signed.zip so when it installs the update, it renames install-recovery.sh
distortedloop said:
I reflashed CWM, then from CWM, remounted /system, then used adb to chmod 6775 su. That restored root pretty easily.
What Recovery image are you using? Are you able to get into it consistently? I can't from fastboot except for if I immediately hit it up after flashing CWM with fb, or from ROM Manager (flash from RM, then select reboot to recovery).
Click to expand...
Click to collapse
I want to attempt to restore my root by using your method. But I'm lost at the part when you use adb chomd 6775 su,
When I go into adb, do i just type chomd 6775 su? Do I have to download something else to use this? Please explain, thanks
If u dont mind can u please provide the instructions on how to do it manually. Id really appreciate it. Sorry im a noob lol
Where in root explorer do i need to rename
Where in root explorer do i rename it
plmiller0905 said:
I want to attempt to restore my root by using your method. But I'm lost at the part when you use adb chomd 6775 su,
When I go into adb, do i just type chomd 6775 su? Do I have to download something else to use this? Please explain, thanks
Click to expand...
Click to collapse
chmod needs to be done at a # prompt.
chris6278 said:
Where in root explorer do i rename it
Click to expand...
Click to collapse
I'm trying not to be rude... but if you can post in this thread, you can read it to. Before you asked your question a couple different step by step posts outlined all you need to know.... and this thread is only 2 pages...
Is it just me or does adb remount no longer work?
If I use the old koush rootboot.img it works, but no wifi, if I use the stock boot.img, I get no wifi but am able to remount.
I can read an ive done all the steps u posted but my ? Is where in root explorer do i find /etc/install-recovery.sh so i can rename it? Im learning this as i go so excuse me if i sound stupid sometimes
chris6278 said:
I can read an ive done all the steps u posted but my ? Is where in root explorer do i find /etc/install-recovery.sh so i can rename it? Im learning this as i go so excuse me if i sound stupid sometimes
Click to expand...
Click to collapse
do you have root explorer? if not, it's just a file explorer that has root access. by default when you open it you are at /
you need to scroll down to /etc
go in that folder and find the install-recovery.sh
look up top for the button to turn it from read-only to read-write, click it
go back to the file long press it, and then choose rename.
Luxferro said:
I'm trying not to be rude... but if you can post in this thread, you can read it to. Before you asked your question a couple different step by step posts outlined all you need to know.... and this thread is only 2 pages...
Click to expand...
Click to collapse
Thanks..I already rerooted but thanks anways
I got root explorer an followed ur directions an now everything works great. Thanx for ur help an sorry for being a pain lol

[ROM][STOCK][EUR] P7500XWKG9 [3G Only] Deodexed , rooted

[size=+2]Backup your rom and files before you start anything. You have been warned!!!!![/size]
[size=+1]If you have P7500-XWKG9 and rooted you can skip to step 7. Tnx to zaphyr[/size]
1. Download Stock Rom P7500-XWKG9 EUR 3G Only http://www.multiupload.com/SGV6N78YY7 [password: samfirmware.com] (Source http://www.samfirmware.com/)
2. Download ODIN3 V1.85 http://forum.xda-developers.com/attachment.php?attachmentid=581913&d=1304094576
3. Extract stock rom somewher on your computer also Odin, run Odin and don't touch anything except PDA where you will select previously extracted stock file.
4. Put Tab in Download mode, connect tab to computer, power off, hold power off and volume - till you see two icons then press volume + and if it ask are you sure pres volume + one more time and you are in download mode then ( order of buttons is _power_ _volume -_ _volume+_ )
5. You should see yellow background on first box of odin and that is good your Tab is ready to flash, then click start on ODIN and wait till it reboot.
6. Now we need to root your Tab, as it is on this topic, so download this and put it on the sdcard, then put your Tab to Recovery mode power off, hold power off and volume - till you see two icons then press volume - ,then volume + and you should go to apply update zip file and you will select this file and when it is done you should reboot your device.
6.1 Download & Install Bussybox installer market link from the market,
run it and superuser will ask to allow root access, you should allow it and then exit application, after that run it again and install bussybox, that is all... Tnx to ChronoWerX
7. Download Deodexed system files http://www.multiupload.com/4QZVAVUPW8
8. Extract downloaded file to sdcard so you have done_app and done_frame folders in the root of sdcard.
9. You should have adb installed or get it from the google, run next commands:
Code:
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
10. After that get back to recovery mode and wipe data/factory reset and reboot.
You have now fully deodexed and rooted GT7500-XWKG9 3G tab working and ready for making changes
----------------------------------------------------------------------------
[size=+1]Browser mod ( Desktop UA String as default ) CWM update.zip files : (credits to DocRambone who explained how to do this)[/size]
Browser_mod.zip
Restore:
Browser_restore.zip
Yeah! Finally! I'm gonna wait a little still, but this changes everything <3
Sent from my GT-P7500 using Tapatalk
zaphyr said:
Yeah! Finally! I'm gonna wait a little still, but this changes everything <3
Sent from my GT-P7500 using Tapatalk
Click to expand...
Click to collapse
This works 100% but you will lost all app and data coz it requires factory reset... Browser mod is comming for this rom today
secretfile said:
This works 100% but you will lost all app and data coz it requires factory reset... Browser mod is comming for this rom today
Click to expand...
Click to collapse
Mine is already @ p7500xwkg9 with root and and CWM, so I should skip to step 7?
Sent from my GT-P7500 using Tapatalk
zaphyr said:
Mine is already @ p7500xwkg9 with root and and CWM, so I should skip to step 7?
Sent from my GT-P7500 using Tapatalk
Click to expand...
Click to collapse
Yes i forgot to tell that you can skip to step 7. if you have all of these but be aware that data and apps will get erased i mean you can try without wipe data factory reset but each time i tryed that i got bootloop...
secretfile said:
Yes i forgot to tell that you can skip to step 7. if you have all of these but be aware that data and apps will get erased i mean you can try without wipe data factory reset but each time i tryed that i got bootloop...
Click to expand...
Click to collapse
Data and apps can be restored, no problem. I won't have access to a computer with adb for at least a week, as I'm hospitalized atm, but as soon as I'm home again I will try this for sure!
Sent from my GT-P7500 using Tapatalk
not worked for me, i became:
255|[email protected]:/ $ su
su
[email protected]:/ # stop
stop
[email protected]:/ # mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
[email protected]:/ # cp /sdcard/done_app/* /system/app/
cp /sdcard/done_app/* /system/app/
sh: cp: not found
Click to expand...
Click to collapse
zaphyr said:
Yeah! Finally! I'm gonna wait a little still, but this changes everything <3
Sent from my GT-P7500 using Tapatalk
Click to expand...
Click to collapse
Lol yes it does.... I know you have been waiting for this for a while
ChronoWerX said:
not worked for me, i became:
Click to expand...
Click to collapse
Hmm that is strange especially because CP is system function for copying, so my question is: did you run this commands with adb.exe?
secretfile said:
Hmm that is strange especially because CP is system function for copying, so my question is: did you run this commands with adb.exe?
Click to expand...
Click to collapse
yes i did, but i read that busybox is needed ... and there is no functional busybox for gt 10.1
ChronoWerX said:
yes i did, but i read that busybox is needed ... and there is no functional busybox for gt 10.1
Click to expand...
Click to collapse
There is, so i will edit my tutorial coz now when i think about it you need it...
what's the password for the rom zip? also, the link you have for ODIN actually goes to CWM - have a link for the correct version of ODIN to use?
thanks
EDIT: password: samfirmware.com
jrinco11 said:
what's the password for the rom zip? also, the link you have for ODIN actually goes to CWM - have a link for the correct version of ODIN to use?
thanks
EDIT: password: samfirmware.com
Click to expand...
Click to collapse
You are totaly right it is wrong pasted .. will fix it and tnx for reminding me that there is password...soon i will release CWM ROM for this so all this will be one Update.zip at the end
secretfile said:
There is, so i will edit my tutorial coz now when i think about it you need it...
Click to expand...
Click to collapse
what i have to do now?
ChronoWerX said:
what i have to do now?
Click to expand...
Click to collapse
https://market.android.com/details?id=com.jrummy.busybox.installer&hl=en This is the app that can install bussybox on your tab fully working with droidexplorer etc...
when flashing this rom in odin 3 v1.85, what options do we check? re-partition, auto reboot, f. reset time, flash lock?
jrinco11 said:
when flashing this rom in odin 3 v1.85, what options do we check? re-partition, auto reboot, f. reset time, flash lock?
Click to expand...
Click to collapse
don't check anything only default ones that are prechecked when you open odin
Step 3.
secretfile said:
https://market.android.com/details?id=com.jrummy.busybox.installer&hl=en This is the app that can install bussybox on your tab fully working with droidexplorer etc...
Click to expand...
Click to collapse
It works, perfect ... will install themed files by me later
theme mods for wxkg9 would be nice! specially a darker / black control bar. if someone did mods, share it please!
i have applied the mods from first post including the browser mod and now i get only corrupted 1kb files when i try to download a picture. dolphin browser does the same. what could i do to fix this bug?
edit: false alarm. does it only on one host (postimage.org) which is really often used in the wallpapers thread in the gtab 10.1 themes and apps section.

[Request] Stock(5.5.959) virgin system.img needed

We are trying to solve how to make our own fastboot system.img files from dd the system partition on a phone. If we can get a stock, 5.5.959, system.img that has never been mounted read/write, then we should be able to compare it to a fastboot system.img and figure out the exact difference. We already have a start of an idea, but it has to be perfect.
By virgin, no OTA patches, and no mounting read/write. You do have to root the phone, but on the temporary root. Put busybox in /data/tmp or somewhere. Next chmod 755 /data/tmp/busybox . Then do something like /data/tmp/busybox dd if=/dev/block/system of=/data/tmp/system.img . Finally copy /data/tmp/system.img off the phone and post it in this thread, please.
Busybox
We already have this file.
You have had it for days, in fact. You converted it to system.tar.gz for me.
Source: erismaster
Satisfies all of your requirements -- 5.5.959 (not OTA!), Verizon, temp ADB root, never mounting /system, dd with those arguments.
psouza4 said:
We already have this file.
You have had it for days, in fact. You converted it to system.tar.gz for me.
Source: erismaster
Satisfies all of your requirements -- 5.5.959 (not OTA!), Verizon, temp ADB root, never mounting /system, dd with those arguments.
Click to expand...
Click to collapse
Is there anyways to get my hands on this? My phone is purely in fastboot mode only and have no other real options to me, so if i could somehow flash this via fastboot, it may actually solve my issue.
(I cant even get into recovery)
edru said:
Is there anyways to get my hands on this? My phone is purely in fastboot mode only and have no other real options to me, so if i could somehow flash this via fastboot, it may actually solve my issue.
(I cant even get into recovery)
Click to expand...
Click to collapse
http://www.megaupload.com/?d=N2FPWHE6
I tried a fastboot flash of this system.img and it gave me a crc check failure.
You can't flash it, it's not signed. It's only useful for development.
Sent from my DROID3 using XDA App
Thanks very much!
No worries about finding a system.img that hasn't ever been mounted . . . we now have "Like a Virgin" images for repeated re-mounting and her pleasure.
Location please?
Wolfhere said:
Location please?
Click to expand...
Click to collapse
the thread is on the main page . . . . http://www.necrotania.com/Download/swu.zip

Categories

Resources