Root Unique question about rooting my Eris - FLASHING

[Frisco]

This is my 3rd day.

I'm on board.

 

[ACD168]

Personally I would never not wipe before loading a ROM unless the dev says to do so and that should only be when on the same rom and doing an update for that ROM, and even then im iffy. happy flashings

 

[erisuser1]

You dont need to wipe before a restore. That would be pointless because it takes everything... settings, apps, contacts, and the rom. to the same exact thing at the time of the NAND backup.

+1

ERISLOVER is 100% correct.

The Amon_RA (v 1.6.2) recovery for Eris actually goes one step further than what ERISLOVER suggests: it actually wipes the /system and /data partitions before it does a restore (with "unyaffs") You don't need to do a wipe before a Nandroid Restore - because there is one built in to the script which does the restore operation!

eu1

 

[Frisco]

Beautiful, informative post, Erisuser1.

That stuff is very, very valuable as we learn about rooting.

Thank you.. I'll always do the wipe, but I have to say that when I have a great set up and system like the Senseable 3.1 is running on my Eris, it makes me want to find a way to be able to get back to it exactly as it is if I don't like, say, White Widow 4.1.

I'm wondering if there is a way to do that, perhaps using my computer as a way to back everything up and then reload it once I decide to flash back to Senseable. Doesn't the wipe get rid of what was restored from the previous ROM?

 

[erisuser1]

Hey Frisco -

My apologies for temporarily steering you (or anyone else) in the wrong direction. ERISLOVER is 100% correct - there is no need to wipe anything before performing a Nandroid restore. (It doesn't hurt to do it, but there is no need to do it, either) The restore operation actually does the wipe itself before it begins unpacking files from the backup.

The menus of the Amon_RA recovery boot call the script nandroid-mobile.sh (with a bunch of arguments) in order to perform backup & restore operations; during restore operations it mounts the appropriate filesystem, removes every file in that filesystem, and then performs the restore.

e.g. restore

/sbin/sh -c /sbin/nandroid-mobile.sh -r -e --norecovery --nocache --nomisc --nosplash1 --nosplash2 --defaultinput -s BDS-20100621-0514 1>&2

eu1

 

[erisuser1]

Bump. Corrected my two prior posts. Sorry for the bad info. eu1

 

[A-Train]

Uh... what? Why do I get the feeling that my thread was hijacked?

 

[A-Train]

ALso, I couldn't find Backup, so i went to restore and a symbol came up with My Eris and a triangle with this in the middle: !

 

[cableguynoe]

Uh... what? Why do I get the feeling that my thread was hijacked?

Sorry about that...lol

But this kinda turned into Frisco's welcome to Root thread.
Now, let me go back and read that first post again

 

[erisuser1]

Uh... what? Why do I get the feeling that my thread was hijacked?

You're right; my apologies.

I think you are not getting much traction with your original query, mostly because there's not that many people that port their phone to another service.

It's not exactly the same situation as yours (different carrier), but do a search in the Eris forums for a post by user pkopalek entitled "Fully on Cricket" (or similar).

Not only does that procedure not look easy; it certainly also looks like it involves configuration changes that would not survive a new ROM installation.

But I'm not an expert in this area, so I'll shut up now; I hope you find that other thread mildly useful.

eu1

 

[A-Train]

Apologies accepted. I was reading most of what people posted and tried applying to my situation and I got lost like in the first 3 posts. lol