I'm afraid I'm stuck in a bootloop... followed the instructions, everything went swimmingly, flashed kaosfroyo 3.1, and now the screen is black with "android" in white and a sort of light scrolling by behind the letters (if that makes sense) for the past 40 minutes. I'm thinking I'll just go to bed and see what it looks like in the AM - but wondering what is the next step, assuming it's still stuck? Battery pull presumably, but then what?
thanks in advance, and g'night all...
(KaosFroyo V31, not v3.1, right?)
95 out of 100 bootloops seem to always be due a short list of things:
1) Failure to perform a "Wipe data/factory reset" immediately prior to flashing a new ROM file (from the SD card), or
2) A problem with the SD card of some sort, or
3) There was actually an error thrown during flashing and the person doing the flashing didn't take notice of it.
You can try doing either of these two alternatives; in both cases, please charge your phone up very well (100% is a good number!) before you begin:
(1)
- Reboot into the (Amon_RA v1.6.2) recovery, and:
- Wipe data/factory reset
- Flash the same ROM again
- Power the phone off
- Eject the SD card before you...
- ...power the phone back on
This first method eliminates the first two most common causes of bootloops; also, note that you should not need to wait 40 minutes. If your phone has not booted completely within 10 minutes, it is in a bootloop. If it boots successfully, go through an initial configuration of your phone, and then insert the SD card to see if it gets recognized.
(2)
- Reboot into the (Amon_RA v1.6.2) recovery, and
- Restore the Nandroid backup that you made.
- Reboot.
You did make a Nandroid backup, right?. This 2nd alternative allows you to use the phone OS and configuration that you are familiar with to download a different ROM (or re-try downloading/copying the same ROM), and proves to you that all is not lost - you can always get back to where you were if you have good backups (in a safe place).
eu1
__________________
Please don't send me PMs - post your questions so others may benefit from any answers given.
n00bs here...
i want to ask, if i only want to root and not flashing into customize ROM what should i do.?
which part is different base on the first post.
n00bs here...
i want to ask, if i only want to root and not flashing into customize ROM what should i do.?
which part is different base on the first post.
thx
The set of instructions in this thread - right up to the point where you have completed making a Nandroid backup and you would be getting ready to "wipe before you flash a new ROM" are identical. That (first) part of the instructions merely installs a custom recovery onto your phone, and doesn't touch the OS which is already installed.
What you do after that backup is a little bit different: rather than just "wiping and then flashing", you DO NOT perform a wipe - instead, you flash the "engtools3.zip" file which is mentioned in the "One Click" rooting method thread.
What that does is install only three programs into your OS: "su", "SuperUser.apk", and "flash_image". Everything else about your ROM remains the same. Note that while your ROM is "rooted", about the only thing you can do from there is to get a "root" shell via adb, or install apps which are root-aware, such as Root File Explorer (and others) - you will not be able to overclock, nor run a2sd. But, your phone will be rooted, and in such a way that none of your other settings or applications will get disturbed.
Good Luck
eu1
The Following 2 Users Say Thank You to erisuser1 For This Useful Post:
The set of instructions in this thread - right up to the point where you have completed making a Nandroid backup and you would be getting ready to "wipe before you flash a new ROM" are identical. That (first) part of the instructions merely installs a custom recovery onto your phone, and doesn't touch the OS which is already installed.
What you do after that backup is a little bit different: rather than just "wiping and then flashing", you DO NOT perform a wipe - instead, you flash the "engtools3.zip" file which is mentioned in the "One Click" rooting method thread.
What that does is install only three programs into your OS: "su", "SuperUser.apk", and "flash_image". Everything else about your ROM remains the same. Note that while your ROM is "rooted", about the only thing you can do from there is to get a "root" shell via adb, or install apps which are root-aware, such as Root File Explorer (and others) - you will not be able to overclock, nor run a2sd. But, your phone will be rooted, and in such a way that none of your other settings or applications will get disturbed.
Good Luck
eu1
Thx alot for the answer...
now i know what should i do...
can i ask another chain question....
if i flashing a customize ROM, then i want to change back to my original one. what should i do..?
you can ignore my question because is OOT to this tread.
Thx alot for the answer...
now i know what should i do...
can i ask another chain question....
if i flashing a customize ROM, then i want to change back to my original one. what should i do..?
you can ignore my question because is OOT to this tread.
Friendly Regards,
You would restore your Nandroid backup.
Note the boldface in my post above - making Nandroid backups before you wipe and flash a new ROM is incredibly important for exactly the reason you mentioned. Don't leave home without a backup.
95 out of 100 bootloops seem to always be due a short list of things:
1) Failure to perform a "Wipe data/factory reset" immediately prior to flashing a new ROM file (from the SD card), or
2) A problem with the SD card of some sort, or
3) There was actually an error thrown during flashing and the person doing the flashing didn't take notice of it.
You can try doing either of these two alternatives; in both cases, please charge your phone up very well (100% is a good number!) before you begin:
(1)
- Reboot into the (Amon_RA v1.6.2) recovery, and:
- Wipe data/factory reset
- Flash the same ROM again
- Power the phone off
- Eject the SD card before you...
- ...power the phone back on
This first method eliminates the first two most common causes of bootloops; also, note that you should not need to wait 40 minutes. If your phone has not booted completely within 10 minutes, it is in a bootloop. If it boots successfully, go through an initial configuration of your phone, and then insert the SD card to see if it gets recognized.
(2)
- Reboot into the (Amon_RA v1.6.2) recovery, and
- Restore the Nandroid backup that you made.
- Reboot.
You did make a Nandroid backup, right?. This 2nd alternative allows you to use the phone OS and configuration that you are familiar with to download a different ROM (or re-try downloading/copying the same ROM), and proves to you that all is not lost - you can always get back to where you were if you have good backups (in a safe place).
eu1
Let's see...
1. Right, kaosfroyo31, not 3.1. I had a DOS flashback.
2. I did do the wipe/factory reset - was following directions VERY carefully (and thanks so much for putting together such a clear set of directions!)
3. Yes, I did a nandroid backup.
[I will admit I was watching the Red Sox game while doing this, so wasn't watching the screen the whole time while flashing the kaos ROM. So I could have missed an error.]
The phone charged overnight while bootlooping (if that's a word) - pulled the battery this AM. Results follow.
Rebooted into Amon_RA. Did another wipe/reset. Flashed PlainJane. Hit the reboot option. Took the dog out. Came back in - there's my nice new ROM, all waiting for me to set up the phone! Yay. I will admit the font isn't what I'm used to, but that's a separate issue. I will set up email, etc. on the train.
Just wanted to say that it's the best freakin' root guide ever. It finally let me easily root my Eris because the stock firmware was driving me insane with freezes and bugs! So far new custom ROM is working great. Many thanks to OP who wrote the guide - it was easy to follow and generally well done.
Sigh.. I've done about every method to root my phone which is 2.1 OTA and this has been my last try to do so and nothing. I can never get it to work for me. I do every step as posted and nothing. Something up with my phone I can't root it? If anyone can help me
Sigh.. I've done about every method to root my phone which is 2.1 OTA and this has been my last try to do so and nothing. I can never get it to work for me. I do every step as posted and nothing. Something up with my phone I can't root it? If anyone can help me
If you want decent help, you need to actually describe what is happening when you attempt a given method.
Saying "can't get it to work" provides NO INFORMATION AT ALL.
Sorry for shouting, but after a while it gets exhausting playing guessing games with people. I can't see your phone, and neither can anybody else here.
If you want some help, go back an try it again, but this time:
- Compare your results step-by-step with what you see in the instructions,
- Write down on a piece of paper (or on the computer) what you notice that seems to be different than the screen shots.
- Report those things in a post, item by item - along with a description about how you satisfied every one of the prerequisites listed in the instructions (including any troubles you experienced do those things, too).
Well, it just does not work >.< it says everything installed perfectly but then I go to reboot everything and its the same old thing and I download Terminal from Market and do the su command and says permission denied so meaning I do not have root. Is there any specific detail I am missing here? This is why I didn't post any other detail because everything says it worked fine. No error of any sort. My firmware says its "2.1" and that's all. Sorry for not saying exactly what was wrong. If there is any other detail needed please let me know. I can do a step by step on what it says when I do it.
Well, it just does not work >.< it says everything installed perfectly but then I go to reboot everything and its the same old thing and I download Terminal from Market and do the su command and says permission denied so meaning I do not have root. Is there any specific detail I am missing here? This is why I didn't post any other detail because everything says it worked fine. No error of any sort. My firmware says its "2.1" and that's all. Sorry for not saying exactly what was wrong. If there is any other detail needed please let me know. I can do a step by step on what it says when I do it.
Again, be specific.
The first 3 posts in this thread ONLY INSTALL A CUSTOM RECOVERY - they do not touch the main OS on the phone.
I can't tell from what you just wrote whether or not you ever attempted to
- boot the recovery (Vol-Up+End)
- Make a Nandroid backup?
- Wipe & flash a new ROM (or no wipe + flash engtools3.zip)
If you successfully flashed a new ROM, then you certainly would not see the same thing after rebooting. If you didn't flash a new ROM, then you certainly WOULD still see the same ROM as the original. If you tried flashing a ROM and that failed a verification step, then you would be left with the original ROM - but reset back to "factory" state (assuming that you followed the instructions and performed a "wipe" before the ROM flashing step).
Based on the limited information that you provided, namely "same old thing", I can not deduce what you did.
I've been at this for more then 10 hours now going everywhere trying to see if I am the only one with this issue. Also, I've done this through the whole SDK and Command screen way as well. I do the whole rooting thing then the flash part the rom you want and nothing. I even tried the whole PB000 thing whatever and it says I can't because I have a newer version installed on my phone already?
The first 3 posts in this thread ONLY INSTALL A CUSTOM RECOVERY - they do not touch the main OS on the phone.
I can't tell from what you just wrote whether or not you ever attempted to
- boot the recovery (Vol-Up+End)
- Make a Nandroid backup?
- Wipe & flash a new ROM (or no wipe + flash engtools3.zip)
If you successfully flashed a new ROM, then you certainly would not see the same thing after rebooting. If you didn't flash a new ROM, then you certainly WOULD still see the same ROM as the original. If you tried flashing a ROM and that failed a verification step, then you would be left with the original ROM - but reset back to "factory" state (assuming that you followed the instructions and performed a "wipe" before the ROM flashing step).
Based on the limited information that you provided, namely "same old thing", I can not deduce what you did.
Well, I suppose I will just guess which one you did most recently.
If you got to Amon_RA's recovery menu, then the first part of rooting worked.
To refresh your memory, that initial screen (fig. 33) looks like this:
If you see that, the essential part of the "Dummies" rooting process worked correctly. The root exploit had to have worked correctly for Amon_RA recovery to get installed on to your phone
So, that leaves me to surmise that (probably) your flashing operation failed.
So, for the moment, I'll ask you to do a couple things.
1) F*ck those other methods; I don't care. Let's focus on one thing at a time.
2) Tell me what ROM you are attempting to install, how many bytes long it is, and what it's MD5 checksum is.
3) Charge your phone well (> 80%) and boot into Amon_RA (Is it still there?)
4) Attempt to perform the Wipe data/factory reset and Flash ROM from SD card,
paying close attention to whether you see any message on-screen which start with "E:" (those are error messages)**
** Note that you do not perform a wipe if you are planning on installing just a few root tools (e.g. engtools3.zip) in order to preserve your current ROM. I am guessing that you are not doing that, but you haven't told me otherwise. (Again, a guess).
ok i like the stock sense rom. if i did this, then downloaded superuser permissions, could i use an app2sd gscript from xtrom and would it install the apps to my sd card??
I've been at this for more then 10 hours now going everywhere trying to see if I am the only one with this issue. Also, I've done this through the whole SDK and Command screen way as well. I do the whole rooting thing then the flash part the rom you want and nothing. I even tried the whole PB000 thing whatever and it says I can't because I have a newer version installed on my phone already?
Trust me, Uye, you've got the attention and are getting help from the best person on this forum possible, erisuser1. You are in excellent hands.
I wasn't trying to be flippant to you per se, just making a reference to another recent post by eu1. I apologize if I gave offense.
There must be something strange going on here, because eu1's method is usually pretty straightforward. I don't want to get in the way here other than assuage your fears--if there's a way to solve your problem, there's none more qualified and helpful than erisuser1. He will help you get to the bottom of things.
Well, I suppose I will just guess which one you did most recently.
If you got to Amon_RA's recovery menu, then the first part of rooting worked.
To refresh your memory, that initial screen (fig. 33) looks like this:
If you see that, the essential part of the "Dummies" rooting process worked correctly. The root exploit had to have worked correctly for Amon_RA recovery to get installed on to your phone
So, that leaves me to surmise that (probably) your flashing operation failed.
So, for the moment, I'll ask you to do a couple things.
1) F*ck those other methods; I don't care. Let's focus on one thing at a time.
2) Tell me what ROM you are attempting to install, how many bytes long it is, and what it's MD5 checksum is.
3) Charge your phone well (> 80%) and boot into Amon_RA (Is it still there?)
4) Attempt to perform the Wipe data/factory reset and Flash ROM from SD card,
paying close attention to whether you see any message on-screen which start with "E:" (those are error messages)**
** Note that you do not perform a wipe if you are planning on installing just a few root tools (e.g. engtools3.zip) in order to preserve your current ROM. I am guessing that you are not doing that, but you haven't told me otherwise. (Again, a guess).
eu1
The order I did everything was backward the way I posted. So, the way you are showing last and so forth. I do get to that screen and I have tried to install the
Uye go here Index of /shipped/Desire click the bottom link as that is the stock 2.1 rom from verizon. run it, and you'll be on stock, then run the rooting process again. I almost bricked my phone once and this helped out alot.
I will redo everything and see if I get an E: on my screen. Also, phone is 100% charged. I do do the Wipe then flash from SD Card.
Make sure you report the file length of the ROM file and if possible it's MD5 sum.
I would say that (conservatively) more than 90% of the "problems" flashing ROMs which are reported by people here and on XDA is corruption of the ROM file - before or during the time it gets placed on the SD card.
Uye go here Index of /shipped/Desire click the bottom link as that is the stock 2.1 rom from verizon. run it, and you'll be on stock, then run the rooting process again. I almost bricked my phone once and this helped out alot.
> 95% chance that doing that will merely prolong his agony. He already has a rooted phone, but is just having troubles flashing a ROM.
So, I tried a different Buuf download and it actually worked this time. Also I noticed the Kaos ROM was like only 3 KB. So I take it I had messed up ROM's. Thanks a lot! Now I know to notice the size very well >.<
So, I tried a different Buuf download and it actually worked this time. Also I noticed the Kaos ROM was like only 3 KB. So I take it I had messed up ROM's. Thanks a lot! Now I know to notice the size very well >.<
Whew. Welcome to Root. Please Press the Thank You button over there ==>
There have been multiple ways that folks got their ROM downloads corrupted; these are the most common:
1) Download to PC (or phone) times out. Short file.
2) Transfer from PC using "Disk Drive Mode" & USB where the user incorrectly disconnects the phone. The proper procedure is to:
- Copy the file from the PC to the mounted drive (E:, F:, G:, whatever)
- Wait a litle bit
- Use the "Safely Remove Hardware" control in the system tray to disconnect the phone - wait for a balloon to pop up saying "OK to remove" or similar
- Turn off "Disk Drive Mode" on the phone.
3) Using Safari to download the file (may automatically unzip the file)
4) Unzipping and re-zipping the file
5) Bad SD Card (least likely)
In EVERY ONE OF THESE CASES, the Amon_RA recovery will issue an error message on the screen. The error messages always start with "E:".
Keep your eyes peeled for errors when using Amon_RA.
You can take steps to avoid these problems to begin with by Verifying your Download files with checksums (Thanks to scary alien for that excellent write-up and his free App, too!)
If you flash a new ROM and you get an error, and you decide
"Dang, I would really like to boot my phone up to download another file or perform other checks", you do not need to boot your phone up with the ROM that just had it's /data partition (settings & apps) wiped in the previous step. (You would need to wait for a long configuration boot and re-configure your phone if you just boot it up after a wipe) Just perform a Nandroid restore operation with the Nand backup that your made right before the wipe operation, and your phone will be back to where it was before you started fooling around with ROM flashing.
I would encourage you - RIGHT NOW - to get familiar with Nand backups and Restores (or maybe after you go to bed following your 12-hour battle with your phone). They will save your ass, more than once.
eu1
The Following 3 Users Say Thank You to erisuser1 For This Useful Post:
I will answer your question - reluctantly, but first, yet another cranky complaint from eu1: your question is off-topic, and would be better placed in either a more relevant thread, or a new topic that you start. Don't be afraid to start your own threads - just make sure to give them a title which relates to the question you are asking.
Quote:
Originally Posted by nyccharlie
ok i like the stock sense rom. if i did this, then downloaded superuser permissions, could i use an app2sd gscript from xtrom and would it install the apps to my sd card??
Yes and no.
If you try it the way you describe it, no. The reason for that is that the baked-in goodness/badness of apps2sd starts during the booting process - so you need things inside the boot partition to make it all hang together correctly so it will start correctly from boot-up.
Also, you will need to carefully review the script to make sure that all the dependencies it needs are satisfied - my bet is that may require a version of busybox to be installed on the phone, too.
It is possible, however to preserve your existing OS and slip in a different boot image right underneath it. You might want to do this anyway, as it would give you an opportunity to use a new kernel with overclocking (The kernel is part of the "boot.img" file). Just make sure that you use an Android 2.1 ROM for the source of your apps2sd/a2sd scripts and "boot.img"
If you try this, make absolutely sure that you create good Nandroid backups before you begin. What I would recommend is that you use a2sd/apps2d and a boot image from the same ROM.
You can manually install a new boot image (after you make a Nandroid backup!) via adb with Amon_RA booted:
- boot Amon_RA, then:
Code:
adb shell mount /sdcard
adb push boot.img /sdcard/new_boot.img
adb shell md5sum /sdcard/new_boot.img
( do not proceed if the MD5 signature is not valid )
adb shell flash_image boot /sdcard/new_boot.img
adb shell rm /sdcard/new_boot.img
adb shell umount /sdcard
Maybe I will put together a related post about doing similar things - in an easier way (not apps2sd specific, though)
eu1
The Following User Says Thank You to erisuser1 For This Useful Post:
i've done everything correctly but after i flashed the plain jane rom, and everything goes smooth but then i'm having boot loops like the ERIS screen will come up then the Plain Jane on top of it will appear then it will just repeat itself...
i've done everything correctly but after i flashed the plain jane rom, and everything goes smooth but then i'm having boot loops like the ERIS screen will come up then the Plain Jane on top of it will appear then it will just repeat itself...
what is wrong?
My first guess is that you forgot do the "Wipe data/factory reset" step immediately prior to the step where you flash the ROM from the .zip on the SD card.
Charge your phone well, go back in to Amon_RA recovery, perform only those two steps, and reboot; keep your eyes peeled for any messages which appear on the screen that start with "E:"
I've done the wipe and factory reset option multiple times then went and flashed the rom would factory resetting on the phone itself instead of doing it in recovery mode help?
I will answer your question - reluctantly, but first, yet another cranky complaint from eu1: your question is off-topic, and would be better placed in either a more relevant thread, or a new topic that you start. Don't be afraid to start your own threads - just make sure to give them a title which relates to the question you are asking.
Yes and no.
If you try it the way you describe it, no. The reason for that is that the baked-in goodness/badness of apps2sd starts during the booting process - so you need things inside the boot partition to make it all hang together correctly so it will start correctly from boot-up.
Also, you will need to carefully review the script to make sure that all the dependencies it needs are satisfied - my bet is that may require a version of busybox to be installed on the phone, too.
It is possible, however to preserve your existing OS and slip in a different boot image right underneath it. You might want to do this anyway, as it would give you an opportunity to use a new kernel with overclocking (The kernel is part of the "boot.img" file). Just make sure that you use an Android 2.1 ROM for the source of your apps2sd/a2sd scripts and "boot.img"
If you try this, make absolutely sure that you create good Nandroid backups before you begin. What I would recommend is that you use a2sd/apps2d and a boot image from the same ROM.
You can manually install a new boot image (after you make a Nandroid backup!) via adb with Amon_RA booted:
- boot Amon_RA, then:
Code:
adb shell mount /sdcard
adb push boot.img /sdcard/new_boot.img
adb shell md5sum /sdcard/new_boot.img
( do not proceed if the MD5 signature is not valid )
adb shell flash_image boot /sdcard/new_boot.img
adb shell rm /sdcard/new_boot.img
adb shell umount /sdcard
Maybe I will put together a related post about doing similar things - in an easier way (not apps2sd specific, though)
eu1
I'm relativley new to the rooting thing. i have no idea about coding so i'm sure i'd fudge that up if i tried. it sounds like alot of fun though. might have to learn using a vm of ubuntu.
I'm having problems transferring the zip file to my phone, when it's done transferring the size of it wouldn't be the same as the original file on my computer.
I'm having problems transferring the zip file to my phone, when it's done transferring the size of it wouldn't be the same as the original file on my computer.
How do i fix??
Make sure you are using "Safely Remove Hardware" on the PC after you copy the file but before you turn off "Disk Drive Mode" on the Eris. Don't yank the USB cable.
Ok, so after reading numerous posts and articles on rooting, kernels and roms...and deciding that this looks like the most competent and current info, my question is this:
If by following original posted instructions, will (1) I be able to over clock my wife’s eris as well as (2) recover her gmail contacts by simply entering the email address as before.
Ok, so after reading numerous posts and articles on rooting, kernels and roms...and deciding that this looks like the most competent and current info, my question is this:
If by following original posted instructions, will (1) I be able to over clock my wife’s eris as well as (2) recover her gmail contacts by simply entering the email address as before.
Yutt!!
Yes, once rooted the Eris can be overclocked. However some (many?) of us are finding that with a decent ROM overclocking is not necessary.
Yes her contacts will come back IF (!) they are set up as 'Google' contacts. If they are 'Phone' then they won't be restored.
Let me start off by saying I am sorry for being a dummie. So I try to read up on the Root for Eris for Dummies, but the hole just keeps getting deeper, every step brings me to another thread and I am getting more confused. I am even confused on downloading the Plain Jane ROM, with different options from the link on first post. So I am not sure what I am downloading ? !! I am a total noobie as everyone can tell. Is there a very very dumb down thread step by step to root the Eris. Then theres the A Ron Recovery, nandroid recovery and titanium backup and other special wipes I need to do. It's making my head hurt. I only want my phone to work like a regular phone, so damm slow. It is so slow when I press call and it dont do anything, I press it again and after some time, the stupid phone has placed 2 calls to the same number. What happened to my phone ? Maybe it's beyond my capabilities. I am thinking of not pursuing this rooting thing any further.
Let me start off by saying I am sorry for being a dummie. So I try to read up on the Root for Eris for Dummies, but the hole just keeps getting deeper, every step brings me to another thread and I am getting more confused. I am even confused on downloading the Plain Jane ROM, with different options from the link on first post. So I am not sure what I am downloading ? !! I am a total noobie as everyone can tell. Is there a very very dumb down thread step by step to root the Eris. Then theres the A Ron Recovery, nandroid recovery and titanium backup and other special wipes I need to do. It's making my head hurt. I only want my phone to work like a regular phone, so damm slow. It is so slow when I press call and it dont do anything, I press it again and after some time, the stupid phone has placed 2 calls to the same number. What happened to my phone ? Maybe it's beyond my capabilities. I am thinking of not pursuing this rooting thing any further.
914,
You are not a dummie. There's a ton of information to absorb and understand (really). Don't give up hope...there's lots of folks around here that would be happy to help. Its getting a smidge late for me to hang through the rest of the night, but let me try to make the picture a little clearer for you.
1. First, to get root, you have to replace the stock recovery partition on the phone with a custom one (usually Amon_RAs). This custom recovery partition, when you boot it, will present you with a simple menu that will allow you do special things to your phone like flash (install) new software or even an entire Android operating system (i.e., a custom ROM).
It will also let you make a snapshot backup of your phone which is called a Nand (or Nandroid) backup. You can later restore from this backup should anything untoward happen to your phone.
2. To get the stock recovery installed, you have to utilize a "root exploit". This took quite a while for the devs to figure-out, but there is a pretty simple and clever one discovered by wag3slav3 over at XDA. This exploit works by re-securing the recovery partition (where the stock recovery resides) to allow it to be over-written with the custom (Amon_RA's) recovery.
The only basic difference between all of them is the amount of detail in the instructions and the amount of work and interaction from the user.
4. At some point in each of the above methods, you will be asked to reboot your phone in "recovery mode" so that you can flash (install) either a custom ROM (such as PlainJaneT2) or a special "update.zip" type of file (such as rootme.zip or engtools3.zip).
The difference between these two types of things you flash are that the custom ROMs will replace the entire Android O/S of your phone and the special "update.zip"-type files (rootme.zip or engtools3.zip) will simply install the su program and SuperUser app on your phone, preserving your current phone's O/S and giving you root capability. Note: there are other "update.zip"-type files that do other things (i.e., install / update other programs and files), but I didn't want to get too deep into that.
5. That's basically it. Once you've got the custom recovery installed and decided to either replace your O/S with a custom rooted ROM or to simply do an in-place root (via the rootme.zip or the engtools3.zip)--you are rooted.
----------------------------
There are other details that you should be aware of:
1. If you do not install a custom ROM, you will not be able to overclock right away. You will have to flash (install) an updated, overclockable kernel and acquire and use the setCPU utility. Also, if you do not install a custom ROM, you do not have to do any "wipes" (see below), but you should do/take Nandroid backups at the appropriate time.
2. Not all custom ROMs have implemented overclocking in the same way, but you should at least be able to overclock to a safe speed of 710MHz (which is usually acceptable for most folks).
3. You should always make a Nand(roid) backup before flashing anything on your phone. So, at the earliest moment that you are able to make a Nandroid backup after you've rooted, you should do so. Then, before you do anything "scary" (yeah ), you should take a Nandroid backup first so that you can restore should you need to. See figures 33-37 in this very same thread for awesome instructions and pictures regarding doing and how to do this.
4. You will see instructions about doing "wipes" on your phone before flashing a custom ROM. This is a process where you are removing files that your previous O/S had used and the removal of which will keep the next custom ROM's O/S from getting confused. There are two types that you do "Wipe data/factory reset" (which should always be done before flashing a new ROM) and "Wipe Dalvik-cache" (which doesn't always have to be run but doesn't hurt if you do). These wipes are done via the custom recovery discussed earlier. See figures 38-39 in this very same thread for awesome instructions and pictures regarding doing and how to do this.
5. I would urge you to re-read eu1's first four posts in this thread. He does a better job than anyone in explaining what is going on, why its being done, and how to do it. You can and should also read through the other root method's threads to compare and contrast. This will reinforce your overall understanding. You will actually learn the most by actually doing it.
That's all I got for now...sleep calls...hope this helps a little. I'll check back tomorrow to see if you have any additional questions. Cheers!
First off I want to say THANK YOU Scary Alien for staying up late and typing up that extensive reply to me. I am sorry I kept you up. So I feel a little braver today. I guess I just had to sleep on it.
One question I had was the step where to check the files MD5 checksum. I am a bit lost on that. What am I checking the gscript file or the Plain Jane ROM file. Am I checking it at the megaupload site or the file on my computer as compared to the checksum afterwards on my SD card ?
First off I want to say THANK YOU Scary Alien for staying up late and typing up that extensive reply to me. I am sorry I kept you up. So I feel a little braver today. I guess I just had to sleep on it.
One question I had was the step where to check the files MD5 checksum. I am a bit lost on that. What am I checking the gscript file or the Plain Jane ROM file. Am I checking it at the megaupload site or the file on my computer as compared to the checksum afterwards on my SD card ?
So I am ready to pull the trigger so do speak
Thank You
No problem...I was working on something anyway that was keeping me up. Funny enough, its related to your MD5 sum question (). Read through this thread: verify your file's MD5 checksums!
You want to check the completeness of the files that you've downloaded from outside sources (aren't they all outside sources? ). The MD5 sums (and the file's size) just let you know that you've got a full, complete, and uncorrupted file. Hopefully, the publisher of the file has posted the MD5 sum and size of the file so you can check on it after you download it and after you put it on your phone (/sdcard) (or where ever it ends-up being).
I'm assuming you meant the file "PlainJaneT2_v2.0.zip", right? Here's it file size (bytes): 104,734,809 and here's its MD5 sum: 561481120922708b1fc8139204fdd948
Its a good idea to check all files, but the larger ones like ROMs tend to be more problematic since folks don't always do a "safe eject" in Windows to make sure that every last byte gets transferred before the connection to your phone is closed.
Hope this helps. Good luck, you'll be fine (especially since it looks like you are using erisuser1's thread (very nice, eh?)).
The Following User Says Thank You to scary alien For This Useful Post:
Only thing I can think of I have messed up is in order to prevent the screen from timing out out I pressed on the body of the script. But I did not add anything. Can start over or ?
I re-read forgot to turn off the phone between steps 1 and 2. I will turn ON phone and hope thats it.
Update: Still no go after turning phone off and on. Do I need to wait longer with power off or need to pull the battery.
I will wait for instructions from the experts.
Thank You.
Last edited by 914; September 5th, 2010 at 12:02 AM.
Only thing I can think of I have messed up is in order to prevent the screen from timing out out I pressed on the body of the script. But I did not add anything. Can start over or ?
I re-read forgot to turn off the phone between steps 1 and 2. I will turn ON phone and hope thats it.
Update: Still no go after turning phone off and on. Do I need to wait longer with power off or need to pull the battery.
I will wait for instructions from the experts.
Thank You.
Sorry, I saw your post in my email and thought you were okay...then I refreshed the page and saw your edit .
You have to reboot (turn off and back on) after root_part1 is done--this allows root_part2 to actually install your custom recovery.
Just go back and re-start from figure 28 where you invoke root_part1 (also, see the paragraph right before figure 28...eu1 thought of everything, didn't he?).
The Following User Says Thank You to scary alien For This Useful Post:
THANK YOU Scary Alien, I DID IT, I rooted and running Plain Jane, trying to remember how to setup my yahoo mail ? I hope I can copy the settings from my wifes phone. Now I can go to sleep better tonight.
Thank you so much scary alien. You were my crutch on this very scary procedure. Hope you have a nice Labor Day !!!!!!!!!
THANK YOU Scary Alien, I DID IT, I rooted and running Plain Jane, trying to remember how to setup my yahoo mail ? I hope I can copy the settings from my wifes phone. Now I can go to sleep better tonight.
Thank you so much scary alien. You were my crutch on this very scary procedure. Hope you have a nice Labor Day !!!!!!!!!
Thank You, Thank You, Thank You !!!!
Congratulations and welcome to root! (w00t!)
I was no problem at all! [be sure to thank erisuser1, too...he actually did all of the heavy-lifting].
I was waiting for you just to make sure all was okay. You learned a lot, didn't you? I'm sure you were as, let's call it "anxious" , as I was when I rooted (but I didn't know eu1 yet and did it the "old fashioned way" (well, it was actually a combination of methods, lol)).
You picked a very good ROM (I've heard lots of good things about PJT2).
Have a great Labor Day weekend and enjoy your rooted phone!
Cheers!
P.S. If you have any other questions or issues, just search for another, related thread or start a new one of your own. There are tons of great folks out there that would be happy to help you.
P.P.S. a great search tip that I use all of the time: launch Google in your browser and enter "site:androidforums.com/eris-all-things-root xxxxxx" where "xxxxxx" is the term or phrase you want to search for. You'll get better "hits" with this method sometimes than the standard forum search.
I have possibly a stupid question, but I can't find anyone that talks about this. I rooted my phone and installed a custom ROM and I feel that my phone actually works better! Smoother texting, no more keyboard lag, its awesome.
My question is this, since I wiped my phone, how do I go about intalling a different ROM? Is this process easier now that my phone has already been rooted?
I have possibly a stupid question, but I can't find anyone that talks about this. I rooted my phone and installed a custom ROM and I feel that my phone actually works better! Smoother texting, no more keyboard lag, its awesome.
My question is this, since I wiped my phone, how do I go about intalling a different ROM? Is this process easier now that my phone has already been rooted?
HELP PLEASE!
The same way you installed the first ROM (but without the initial rooting steps).
- Download the ROM you are interested in, plus any other .zip files recommended by the developer on his/her announcement page. Move them to the top folder of your SD card.
- Charge phone very well (>80%)
- Boot to Amon_RA recovery. and then do these 3 steps:
- Perform a Nandroid backup (so you can restore back to the same spot later if needed)
- Wipe data/factory reset
- Flash .zip file from SD card (plus any "extras" recommended by the dev, if any)
Done. Reboot your phone and wait 5 or 6 minutes.
Please be on the lookout for any messages that begin with "E:" while using Amon_RA
"E:" means ERROR
eu1
PS. To say that this hasn't been covered before is ludicrous; it's the fourth post of this very thread, with copious pictures and explanations.
I have loaded gscript to the SD card. How do I launch it?
I am stuck at "figure 19".
Thanks!!
Blizzard, its also an app that you download from the Market (it is a little confusing that there is a "Gscript Lite" app and a "gscript.zip" file, but they are two separate, but related things). The "gscript.zip" file contains scripts that the Gscript Lite app will use in these rooting method.
Check post #1 where it says:
Code:
Before you get started, please review this checklist:
1) Did you choose a ROM, download it to your SD card, and check the MD5
signature/file length on the copy of the file on your SD card?
2) Did you install from the market the free apps "Gscript Lite" and
"EStrongs File Manager"?
3) Did you download the "gscript.zip" file (link above) using the phone's
browser?
There's lots of little steps and details, but you should be fine. Cheers!
Just like everyone else who used this thread to root their phone, I want to say thank you so much! I rooted my Eris last night and it has never been better! I'm really enjoying it!
The HTC Droid Eris launched for Verizon Wireless on November 6th in part as the carrier's first Android Phone. However it was overshadowed by the other member of the inaugural Verizon Droid duo - the Motorola Droid. The Droid Eris might look fa... Read More
), you should take a Nandroid backup first so that you can restore should you need to. See figures 33-37 in this very same thread for awesome instructions and pictures regarding doing and how to do this.
