What's the procedure for looking at what has been backed up. Not sure if I'm asking what I'm thinking.
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root Universal Eris Root for Dummies!
- Thread starter erisuser1
- Start date
-
- Tags
- htc droid eris
The Nandroid backup backs-up everything on your phone (excluding the /sdcard, of course).
So, if you look in the /sdcard/nandroid directory (using something like Astro File Manager), its contents, or lack thereof, will tell you if you have a backup of your stock O/S (assuming that the backup is timestamped near the time that you actually rooted and that you actually did the Nandroid backup
).
Thanks Scary Alien your the man. I have HTXXXXXXXXXX BDS-XXXXXXXX-XXXX. So this is my stock rom?
First, edit your post and redact the HTxxxxxxxxxx like I did (that's your serial number that identifies your phone (and therefore, you
)).If this was created right around the time that you rooted, it probably is your stock ROM--and if you used this (erisuser1's) thread, then this is what he has you do right after rooting, it really should be your post-root stock ROM.
You could always take another Nandroid backup (like figures 34-37 shows you), then restore the old one and see if it looks like your pre-root stock ROM. Then, just re-restore your most current Nandroid backup to get you back to where you are now.
Nandroid backups and restores seem scary at first, but they shouldn't be as long as you make a backup before you do anything potentially destructive. Always make sure you have a good charge on your phone before using anything in custom recovery--I always have mine plugged-in and charging when I do something like this.
Simple, right?
Oops my bad. Changed it. So that's got to be it cause I did it by Erisuser 1's book. I was in unfamiliar territory untill I did it and now I should have done it a long time ago.
No problem... By the way, the BDS-ccyymmdd-hhmm portion of your Nandroid backup is non-secret info, so you didn't need to redact all of it.
Looks like the backup you made was on 11/23 at around 6:03 PM (or so, I don't know if you are GMT-4 or GMT-5)...sound right?
Cheers!
That would be right.
I was looking at a thread earlier about partitioning the sd card and ran across the xtrsense 4.6.5 and tried to download it but the link must have been broke. It looks pretty cool. Does it have many bugs or is it stable.
I downloaded and installed it on my Eris last weekend... My Droid X is my primary phone, so I don't really "play" with my Eris too much other than research things, but everyone seems to be of the consensus that Zach xtrROM and xtrSense are top of the line ROMs. Should be very fast and very stable. Read through the dev's thread:
[ROM][GPL][11/5/2010] xtrSENSE4.6.5 [cache2cache,apps2sd,oc,jit]-HTC Sense - xda-developers
Here's the download link I used:
And the download link looks okay to me: http://zach.xtr.i6ix.com/xtrSENSE4.6.5.zip
Good luck!
Thanks downloading now. Can't upgrade untill next april. Wanted the X but want to see what comes next.
fotroofgrl
Lurker
Many thanks to erisuser1 for posting these steps. I've lurked on this forum for the year since I got my Eris on the day it came out. Tweaked things here and there with leaks, etc. I'd thought about rooting but felt too uncomfortable taking the risk. Finally got so fed up with the darn thing breaking my heart with quirks and freezes, I decided it was my last ditch effort to salvage my relationship with this phone before giving up and replacing it.
It took me a little more than 30 minutes yesterday, smooth as silk! Thank you for making it so easy! Hopefully the next few weeks will prove the decision to be a wise one.
It took me a little more than 30 minutes yesterday, smooth as silk! Thank you for making it so easy! Hopefully the next few weeks will prove the decision to be a wise one.
Keep in mind that your decision is reversible - There is a ROM which you can flash that will take you back to factory state, should you decide that is what you want:
[ROM][10/20/2010]FlashBack21 v1 -Return to Factory Stock - UPDATED - xda-developers
eu1
fotroofgrl
Lurker
<Grin> Yeah, that was one of the reasons I felt comfortable moving forward! Thanks again!
eris3141592
Lurker
can somebody help me pretty please?
i just rooted my phone but haven't done the backup yet, i tried downloading the ROM onto my sd card before but it didn't actually download...can i download it now and just continue the process or do i have to start over?
sorry, i'm not very good at technology stuff
i just rooted my phone but haven't done the backup yet, i tried downloading the ROM onto my sd card before but it didn't actually download...can i download it now and just continue the process or do i have to start over?
sorry, i'm not very good at technology stuff
can somebody help me pretty please?
i just rooted my phone but haven't done the backup yet, i tried downloading the ROM onto my sd card before but it didn't actually download...can i download it now and just continue the process or do i have to start over?
sorry, i'm not very good at technology stuff
eris3141592 (Pi, nice!
), welcome to Android Forums!You'll be fine. If you've rooted and do indeed have your custom recovery, go ahead and do your Nandroid backup as the instructions demonstrate (i.e, starting with figure 33 (i.e., post #4)).
Yes, you can download and place your custom ROM in the top-level of your /sdcard at any time and then flash it (good idea to have that backup first though
).Let us know if you have any other questions. Cheers!
eris3141592
Lurker
yay! thank you sooo much 
!!
!!
yay! thank you sooo much
No problem...read and digest erisuser1's post #4 and follow his directions carefully:
1. Make your Nandroid backup
2. Do the wipes as instructed
3. Flash your custom ROM
4. Reboot (be patient, it might take a few minutes)
5. Enjoy your new custom rooted Eris
Cheers!
EU1 you are seriously amazing. My boyfriend (with his super fast Incredible, arrr) has been making fun of my slow Eris and its 2.1 for ages. What's worse, I work for one of the major cell phone manufacturers and play with our super fast devices all day, then have to go home to my tiny little Eris, just puttin along in its operations....
Until I found you!
Had tried to root previously the "classic" way via PC and something was wrong. Was about to give up. But all is good in the world now that I'm running 2.2 woohoo!
Until I found you!
Had tried to root previously the "classic" way via PC and something was wrong. Was about to give up. But all is good in the world now that I'm running 2.2 woohoo!
i need some help !
can anyone help?
Nehneh,
Is your phone a Hero (i.e., are you trying to run the script on your Hero)?
This script / thread / method is only intended for the HTC Droid Eris (code name desirec).
If it detects that your phone model is not a desirec then it will refuse to run. You wouldn't want to install a recovery partition intended specifically for Eris on a Hero would you ('cause that would be "bad").
That's correct; I put that check in there specifically so that newbs would not wreck their phones using my scripts.
AFAIK, most Android 2.1 phones could be rooted with the exact same method -
but a (phone) model-specific recovery would need to be installed.
For non-Eris owners, that is left as an exercise for the reader.
eu1
eu1,
Thank you again by the way for your efforts in creating these scripts.
I dissected and examined your Gscript scripts and got to know them very well whilst trying to create installation scripts for the alternate trackball-optional custom recovery. So, I very much appreciate the time, care, and effort you must have put into creating them.
Props and kudos to you, as always!
Cheers!Off-topic, but speaking of which, I've been meaning to check to see if you updated the "ro.modversion" property string in your modded Amon_RA recovery - my Flashback21 ROM has not only a device check, but also a build version check that might interfere with the ability of someone using your trackball-free mod of Amon_RA to install that ROM - to wit:
Code:
assert getprop("ro.modversion") == "RA-eris-v1.6.2"eu1
Short answer: no, because I did not change the ro.modversion property.
Why, you ask? (proceed further at your own risk
).At first, I was going to update the version number, but I thought that was a little presumptuous of me, without knowing the proper protocol or gaining persmission from Amon_RA.
I was also thinking that functionally, my version should behave identically to the original version--except, of course, for the navigation changes.
Then, I realized that I'm not really sure what version Amon_RA's custom recovery for the Eris actually is. I say that for a couple of reasons:
It clear to me (now, anyways) that the "1.6.2" labeled version of Amon_RA's custom recovery is not actually 1.6.2 (nervous LOL
). The reason I say this is that when I built my first trackball-optional version of the custom recovery, I used the 1.6.2 recovery.c source which did not include support for any of the Partition sdcard menu options--which the current version that virtually everyone has, actually does. Thanks to TheLedge and mhotovec for pointing this out.
It appears to me that (somehow) the 1.6.2 version widely in use did not get its "ro.modversion" updated when it was compiled and was most likely compiled/built with the 1.7.1 version of the recovery.c file. Alas, I don't think this can be gleaned soley from examining the contents of the recovery.img file--I think we'd have to ask Amon_RA himself.
I did not want to presume that it was okay for me to update the version number without Amon_RA's consent or instruction (he is aware of the side-version that I've made). Also, he's indicated that he is working on updating all of the custom recoveries to a latest-and-greatest version level (date not yet announced). [I am hoping that he might include the alternate-key functionality in his future versions too given other's experiences with wonky trackballs.]
Also, I did not (or have not yet) upload my version as a separate branch in packetlss's github (which I probably will (and should) do at some point).
Anyway, bottom line / sorry-it-took-so-long-to-answer response is: no, I have not
.Does the above many any sense? I think I outlined it more succinctly in the "alternate trackball" thread (after I was made aware of the partition discrepancies and built yet a second version of the custom recovery
).Cheers!
sa,
That indeed does make sense, and I'm glad to find out that I don't need to change anything. I originally put that check in there (for the FlashBack ROMs) mostly because I did not personally test the install using Clockwork - and I didn't want to release it for something I had not tested myself. ( iirc, some of the shell-script logic uses some *nix featurisms which might not be present in the shell that Clockwork provides.)
Thanks for the thorough reply.
eu1
That indeed does make sense, and I'm glad to find out that I don't need to change anything. I originally put that check in there (for the FlashBack ROMs) mostly because I did not personally test the install using Clockwork - and I didn't want to release it for something I had not tested myself. ( iirc, some of the shell-script logic uses some *nix featurisms which might not be present in the shell that Clockwork provides.)
Thanks for the thorough reply.
eu1