[International / GSM] Recovery/Restore question

[darkcyber]

Just curious before I start flashing everything as to what is the route back to a good install if things go bad? Let me explain my question. Like on the Droid X, we could always do an sbf back to complete stock if we needed to. Since ClockworkRecovery hasn't been sticking and if things go bad, then how are we getting back to stock or restoring a nandroid image if we can't get into CWR?

 

[scary alien]

Just curious before I start flashing everything as to what is the route back to a good install if things go bad? Let me explain my question. Like on the Droid X, we could always do an sbf back to complete stock if we needed to. Since ClockworkRecovery hasn't been sticking and if things go bad, then how are we getting back to stock or restoring a nandroid image if we can't get into CWR?

Yes, a Nandroid backup of a good, known setup is your best safety net. Just make sure you've also got it backed-up somewhere externally to your phone just in case. If you run into issues, you should just be able to reboot back into ClockworkMod and restore that known good backup.

You've also got the ability to flash everything completely back to stock if necessary, too.

As far as ClockworkMod not "sticking", have you seen the following in this post?:

http://androidforums.com/verizon-galaxy-nexus-all-things-root/474570-how-all-things-root-samsung-galaxy-nexus.html#post3736600

Flashed custom recovery won't "stick"?

Do this:

- remount /system in read/write mode (use something like the Root Explorer app or ES File Explorer; both have root modes (check the app's settings) for remounting /system as writable)

- rename the /system/recovery-from-boot.p to /system/recovery-from-boot.p-bak

(note: you could delete it, but renaming is much safer since its easily reversible)

- you could also do this manually in an adb shell or on-phone Terminal session:

+ mv /system/recovery-from-boot.p /system/recovery-from-boot.p-bak

Cheers!

 

[triplejnj]

I just went through the motions of reverting my rooted phone back to stock so that I can take it in for an exchange. Using your links in "all things root" http://androidforums.com/galaxy-nex...root-samsung-galaxy-nexus.html#stock-recovery
I was able to quickly unroot, re-image, restore factory recovery, and relock the bootloader. Thanks for the detailed information!

 

[darkcyber]

Yes, a Nandroid backup of a good, known setup is your best safety net. Just make sure you've also got it backed-up somewhere externally to your phone just in case. If you run into issues, you should just be able to reboot back into ClockworkMod and restore that known good backup.

You've also got the ability to flash everything completely back to stock if necessary, too.

As far as ClockworkMod not "sticking", have you seen the following in this post?:

http://androidforums.com/verizon-ga...gs-root-samsung-galaxy-nexus.html#post3736600

Flashed custom recovery won't "stick"?

Do this:

- remount /system in read/write mode (use something like the Root Explorer app or ES File Explorer; both have root modes (check the app's settings) for remounting /system as writable)

- rename the /system/recovery-from-boot.p to /system/recovery-from-boot.p-bak

(note: you could delete it, but renaming is much safer since its easily reversible)

- you could also do this manually in an adb shell or on-phone Terminal session:

+ mv /system/recovery-from-boot.p /system/recovery-from-boot.p-bak

Cheers!

Thanks for the information. Yes, I had looked through that thread before. So, IF you were ever to loose CWR sticking (for whatever reason), there is no way to hook up your Nexus and restore like we did doing the sbf on the Droid X?

 

[scary alien]

Thanks for the information. Yes, I had looked through that thread before. So, IF you were ever to loose CWR sticking (for whatever reason), there is no way to hook up your Nexus and restore like we did doing the sbf on the Droid X?

Well, you can always easily re-flash ClockworkMod or softboot it via the fastboot command to invoke it...you're only a PC (fastboot) command away from invoking CWM if you can't get into Android proper.

Re-flashing (via fastboot) the stock Android images is akin to SBF'ing like for the DX:

How to un-root (return to stock)

Cheers!

 

[darkcyber]

Well, you can always easily re-flash ClockworkMod or softboot it via the fastboot command to invoke it...you're only a PC (fastboot) command away from invoking CWM if you can't get into Android proper.

Re-flashing (via fastboot) the stock Android images is akin to SBF'ing like for the DX:

How to un-root (return to stock)

Cheers!

Ahhh, Ok. So, you can access the Nexus if it gets goofed up via computer using fastboot...ok.

 

[riverboat2001]

Okay, all rooted now, and happy to stick with standard rom to begin with.

When i tried to reboot into recovery, nothing was there (i have run the clockwork recovery flash)

So i assume i'm having problems with the flash recovery not sticking.

I've read this:


- remount /system in read/write mode (use something like the Root Explorer app or ES File Explorer; both have root modes (check the app's settings) for remounting /system as writable)

- rename the /system/recovery-from-boot.p to /system/recovery-from-boot.p-bak

(note: you could delete it, but renaming is much safer since its easily reversible)

- you could also do this manually in an adb shell or on-phone Terminal session:

+ mv /system/recovery-from-boot.p /system/recovery-from-boot.p-bak

But i don't understand where i run this mv command , do i need a command prompt with phone connected.

 

[scary alien]

Okay, all rooted now, and happy to stick with standard rom to begin with.

When i tried to reboot into recovery, nothing was there (i have run the clockwork recovery flash)

So i assume i'm having problems with the flash recovery not sticking.

I've read this:


- remount /system in read/write mode (use something like the Root Explorer app or ES File Explorer; both have root modes (check the app's settings) for remounting /system as writable)

- rename the /system/recovery-from-boot.p to /system/recovery-from-boot.p-bak

(note: you could delete it, but renaming is much safer since its easily reversible)

- you could also do this manually in an adb shell or on-phone Terminal session:

+ mv /system/recovery-from-boot.p /system/recovery-from-boot.p-bak

But i don't understand where i run this mv command , do i need a command prompt with phone connected.

If you use an app like Root Explorer (costs) or ES File Manager (free), you can re-mount your /system partition in read/write mode (you have to do this in order to be able to rename or delete a file from that partition). That's probably the easiest way to do this.

The other "mv " (move) command was for those that are comfortable with an "adb shell" (yes, connected to your PC via the USB cable) or directly on your phone via an on-phone terminal emulator (like Android Terminal Emulator).

You'd still have to have re-mounted /system in read/write mode beforehand before doing this manually, so that's why we usually tell folks to use a rooted file manager like those listed above.

If you use ES File Explorer, I can dig-up some notes for doing it via that app (I don't have Root Explorer myself).

Cheers!

 

[riverboat2001]

Well, i've downloaded ES file explorer, but can't find the path to the files i need to change.
I also can't see any option within ES File explorer to "re-mount your /system partition in read/write mode"

Having used pc's since green screen days, i'm happy using DOS commands, but would rather learn how to use the ES file explorer program as it looks pretty neat (especially for free!)

Found it!
Just watched a video that showed me how to get to the system file, once i'd enabled read/write mode.
Guess i should change that now i've done what needed to be done.

 

[scary alien]

Well, i've downloaded ES file explorer, but can't find the path to the files i need to change.
I also can't see any option within ES File explorer to "re-mount your /system partition in read/write mode"

Having used pc's since green screen days, i'm happy using DOS commands, but would rather learn how to use the ES file explorer program as it looks pretty neat (especially for free!)

Give me a minute to dig-up my notes in another thread...sorry, I got caught-up in something else that kept me from replying promptly to you.

BRB

 

[scary alien]

Okay, sorry for the delay...

I'll give you a few links for reference, then I'll sum it up since the might make more sense (but you'll have the other links just in case):

http://androidforums.com/verizon-galaxy-nexus-all-things-root/477813-clockwork-mod.html#post3759674

references three posts in this thread:

http://androidforums.com/verizon-galaxy-nexus-all-things-root/472557-cwm-recovery-problem.html#post3723336
http://androidforums.com/verizon-galaxy-nexus-all-things-root/472557-cwm-recovery-problem.html#post3724245
http://androidforums.com/verizon-galaxy-nexus-all-things-root/472557-cwm-recovery-problem.html#post3725898

But here's what I did:

- download / install / launch ES File Explorer

- press the menu icon (bottom right)

- select Settings

- select Home Directory

- change your Home Directory to "/" (without the quotes, of course)

- return to the Settings screen

- scroll down to the bottom of the screen

- check the "Root Explorer" box in the Root Settings area (you'll get the Superuser whitelist app's pop-up asking for permission for this app)

- when you want to mount / and /system as writeable, check the "Mount File System" box under the "Root Explorer" checkbox

- hit the back button to return to the file navigation

- press the "Up" directory icon in the toolbar at the top of the screen--that should take you to the / (root) filesystem

- from there, you should be able to navigate to the /system filesystem and look for the recovery-from-boot.p file

Let me know if you have questions.

Cheers!