But if you thought Jcase's spin on the new wag3slav3 rooting method was minimalist, this variation of it should help the fence-sitters and tech-intimidated join the world of Eris root.
- ZERO typing!
- NO SDK Installs!
- NO USB Driver Installs!
- NO Command Lines!
- NO PC NEEDED! A Phone-only Rooting method!
Basically this is just a repackaging of the wag3slav3 method (as modified by jcase) into a form which allows you to do everything from the Eris without using a PC, and without any typing - just tap the Eris' screen in all the right places.
For experts who are already have successfully set up the SDK and USB drivers, and are comfortable with the command line and adb, it is probably faster to just use the manualmethod. This method was created for the folks who have had trouble with, or are intimidated by, those things. Or, for those times when you want to help someone root their Eris without schlepping a "dev station" to their location.
- Eris w/ any HTC/VZW release (including 1.5, all leaks V1-V3, & root-ROM)
- Install free Market app Gscript Lite (PinkVenture)
- Install free Market app EStrongs File Explorer
- Download gscript.zip (MD5 92796a8c6e61e8f1ee36e315c0acae7d)
edit: please also reference this post Universal Eris Root for Dummies! for downloading the gscript.zip file; I've also updated the link (as of 8/27/2012) to have a new, alternate download link.
- The ROM of your choice downloaded onto your SD card in the root folder. (T2noob's PlainJaneT2 V2.0 looks good - includes the July 2010 updates.)
I have organized this walk-through as a picture-book in a couple of posts:
OK, this post is "long but vapid" - it's mostly pictures, in keeping with the "Dummies" theme. Pretty simple stuff for advanced users.
The objective of this post in the thread is to simply to unpack the "gscript.zip" file using a file manager, so that the rooting scripts end up in a folder called "gscript" underneath the root folder of the SD card. This example uses the free app "EStrongs File Explorer".
When we finish this step, we will have four files in place on the SD card like this:
(NOTE: If you are familiar with a different file manager that can move files around and unzip .zip files, feel free to use that, but beware: the zip file must be unpacked so that it's contents end up in the folder "/sdcard/gscript")
We start with the assumption that you are not using a PC, and have downloaded the gscript.zip file using the web browser on the phone, so that it will be located in the /sdcard/download folder of the SD card.
Launch the Estrongs File Manager (ES File Manager) app; it will look like the screen below (fig. 1)
[ fig. 1 ]
[ fig. 2 ]
[ fig. 3 ]
[ fig. 4 ]
[ fig. 5 ]
[ fig. 6 ]
[ fig. 7 ]
[ fig. 8 ]
[ fig. 9 ]
[ fig. 10 ]
[ fig. 11 ]
[ fig. 12 ]
[ fig. 13 ]
[ fig. 14 ]
[ fig. 15 ]
[ fig. 16 ]
[ fig. 17 ]
[ fig. 18 ]
Last edited by erisuser1; July 20th, 2010 at 09:48 AM.
The Following 34 Users Say Thank You to erisuser1 For This Useful Post:
It turns out that rooting the phone will only take two taps... but a fair number of other "taps" or "long presses" are needed just to get the "Gscript Lite" tool set up to do those two taps.
So, let's get started. Launch the Gscript Lite app.
[ fig. 19 ]
Figure 19 shows the Gscript Lite app after it has been started for the first time. The first thing we want to do is to press the "Menu" softkey on the Eris.
[ fig. 20 ]
In fig. 20, we have pressed the Menu softkey on the Eris; now tap the "Add Script" button.
[ fig. 21 ]
Note that the screen that comes up next is nearly blank. Make sure to uncheck the checkbox labeled "Needs SU?". Clearly, we don't have root yet, so this should be de-selected for both of our scripts - they won't run at all if you leave that option checked.
[ fig. 22 ]
Tap the "Load file" button (fig. 22).
[ fig. 23 ]
If you previously unpacked the "gscript.zip" file in the correct location ( /sdcard/gscript ), you should see our two root scripts listed. If you don't see them listed, you didn't unzip them to the correct location. ( Gscript Lite does not allow you to browse around for files - they must be in that /sdcard/gscript folder. )
Tap on "root_part1.sh"
[ fig. 24 ]
Fig. 24 looks intimidating, but all we are going to do here is tap the "Save" button. Before you do that, though, double check to make sure the "Needs SU?" checkbox is turned off. Do NOT click on the script or edit it in any way - if you are curious what is in it, look at them with a text file viewer, NOT HERE. It is simply asking for trouble for you to use the text widget to scroll around inside that text entry box - there is a good chance you will accidentally break the script. Just make sure that "Needs SU?" checkbox is turned off, and tap the "Save" button.
[ fig. 25 ]
Fig. 25 shows that Gscript Lite now shows that it is aware of the root_part1 script. (Again, note that it does NOT require root - "Needs SU: false")
At this point, please repeat the prior steps (starting with a tap of the Menu softkey, followed by "Add script") to load the second script "root_part2.sh" into Gscript Lite.
[ fig. 26 ]
Just as before, simply tap the "Save" button after checking that "Needs SU?" is de-selected.
[ fig. 27 ]
Good news! We are just about ready to root.
First, we are going to triple-check that "Needs SU?" thing one more time. Inspect your screen; it should look like Fig. 27. Note that both scripts are listed, and they both say "Needs su: false".
CAUTION! If you should make a mistake, you can delete the entries you just performed by LONG PRESSING the affected entry, and selecting the "delete" option from the pop up menu. PLEASE BE AWARE that if you "tap" the script name, rather than LONG PRESSING, the script will execute immediately.
The good news is that these scripts are (surprisingly) almost harmless, and also nearly idempotent - you can re-run them if you have a problem. Also, because of the way that Gscript Lite works, if you delete the entry, you are NOT deleting the file on the SD card.
[ fig. 28 ]
Are you ready to start rooting? Carefully tap the "root_part1" script.
[ fig. 29 ]
Fig 29 shows you what you will see in part one. I added a battery check - please make note of the charge % of your phone in the first line! Note that no ROM flashing takes place in part one, so it is completely safe to perform no matter what the battery state is. On the other hand, DO NOT RUN part2 until you have a good charge on your battery. HTC says 40%, but I'm not comfortable with that - you should have lots and lots of headroom above that - say 70% charge or higher.
Now, power your phone off, and then turn it back on again.
[ fig. 30 ]
After the phone completely reboots, re-start Gscript Lite.
Now we are ready to do part2 of the rooting process - the part that installs the Amon_RA recovery.
Figure 30 reminds you that you merely need to tap on the "root_part2" entry to complete the custom recovery installation.
Once again, I'll remind you: DO NOT RUN part2 until you have a good charge on your battery. Note that there is no "hurry" to do this: there are no race conditions, the rooting process is completely deterministic. Bottom line: you have plenty of time available to you to charge the phone after part1 has run, and you can continue to use your phone normally in the meantime while waiting for it to charge. DO NOT FLASH ROMs WHEN YOUR BATTERY IS NOT WELL CHARGED.
When you are ready, tap the "root_part2" script in the Gscript Lite app to install the Amon_RA recovery.
[ fig. 31 ]
Figure 31 shows you what the display will look like after it completes.
CONGRATULATIONS! You have installed a "custom recovery" (Amon_RA v1.6.2) on the Eris, and you are only two or three steps from having a custom ROM on your phone.
If you see a "clean" display like this, you can proceed to the next steps - using Amon_RA recovery boot. To get there, power your phone off, and then power it back on by pressing and holding Vol-Up & End/Power at the same time.
Hopefully, this is what you will see:
[ fig. 32 ]
The Following 37 Users Say Thank You to erisuser1 For This Useful Post:
In this last step, we are going to do three things:
- Make a Nandroid Backup of your current ROM
- Wipe the Eris to prep for a new ROM install
- Install the new ROM (of your choosing)
You have powered down your phone, and restarted it by simultaneously holding down the Vol-Up & End/Power buttons. YOU NEED TO CONTINUE TO HOLD BOTH OF THEM DOWN UNTIL THE SCREEN LIGHTS UP AND YOU SEE THE 3 SKATEBOARDING DROIDS.***. This starts up the custom recovery you just installed.
***( A number of people have reported that the Vol-Up + End/Power key combination does not boot the custom recovery, but instead just boots the normal phone O/S. If this happens to you, instead, use Vol-Down + End/Power to boot into HBOOT mode, and then press Vol-Up to start the Amon_RA Recovery )
[ fig. 33 ]
Figure 33 shows the Main menu of the custom recovery (Amon_RA v1.6.2.)
Navigation is performed by using a the trackball, the Vol-Down button, and the End/Power button. In general, these are set up on the Eris as follows:
Trackball Scroll Up/Down -> move up/down in a menu
Trackball Click -> select a new menu or start an action
Vol-Down -> Escape from the pending action, or go up one level in the menu.
Let's start by making the Nandroid Backup.
[ fig. 34 ]
Using the trackball, scroll down to the menu item "Backup/Restore". Click on this menu item with the trackball.
[ fig. 35 ]
Click on "Nand Backup" with the trackball (fig. 35)
[ fig. 36 ]
Amon_RA will ask you to confirm your choice (fig. 36). Click on the Trackball to confirm.
[ fig. 37 ]
The Nandroid backup will show progress by painting dots along the screen as it works. Please be patient and wait; it will print a message "Backup complete!" when it has finished.
At this point, press the Vol-Down button to escape out of the Backup menu and return back to the main menu (fig. 33)
[ fig. 38 ]
Scroll down with the trackball to the "Wipe" menu item in the main menu (fig. 38), and press the trackball. This will take you
to the Wipe sub-menu shown below.
[ fig. 39 ]
We want to select the first action in the list: "Wipe data/factory reset"
With this item highlighted, click with the trackball.
Amon_RA will ask you to confirm this choice - click with the trackball again to confirm, and wait for the wipe to occur.
When finished, press the Vol-Down button to return to the main menu (fig. 33)
Scroll down in the main menu and click on the 4th item: "Flash zip from sdcard"
[ fig. 40 ]
You will see something similar (not identical) to figure 40 above.
Amon_RA recovery will list every ZIP file it finds in the root of the SD card (Just because it is listed does not mean it works as an update! In particular - PB00IMG.ZIP files can not be installed as "updates").
Scroll Down and Choose the ROM (.zip) file that you transferred to the root folder of your SD card at the beginning of this process. Click with the trackball once, and then click again to confirm and install the ROM.
Be patient! Many ROMs are quite large - 100+ MBytes, and it takes over one minute to flash the complete ROM file.
When the ROM is installed, press the Vol-Down button to return to the main menu.
[ fig. 41 ]
With the Reboot system now entry highlighted, click using the trackball. This will reboot your phone without requiring a second (confirmation) click.
Many ROMs take a number of minutes to completely boot the first time - this is because the Dalvik cache needs to be populated, and some ROMs also perform other one-time, time consuming tasks.
PLEASE BE PATIENT THE FIRST TIME YOUR ROM BOOTS UP! When in doubt, let the phone sit for as much as 20 minutes before you decide that it is "hung". (If you want, you can plug it in to a charger or USB so the battery won't drain further).
Some Final Thoughts
Providing an "easy to use" rooting method is a bit like cutting the locks off the doors to the local dynamite factory, and setting up a billboard announcing the fact - there's probably gonna be some teenagers who get hurt.
Root privilege gives you the power to create - and also to destroy. The fact that an "easy" path to rooting is available does not mean that no learning needs to take place for you to use root safely. If you start doing things to your phone without understanding, there is a chance you could brick your phone. By reading this sentence, you agree that all further activities with the phone are "on your own head".
I think it is a really good idea to get the engineering bootloader installed on the device (thanks jcase!), as a backstop to accidents that could take out the Amon_RA recovery. I didn't include instructions in this thread because the method currently uses ADB/fastboot with a PC, and I want the instuctions in this thread to only include methods that do not require a PC. (I think it is possible to package it up as an "update.zip"/ROM-style install)
Note that the wag3slav3 method actually "damages" the factory installed recovery partition (by writing 16 bytes to it) - if you perform "part1" of the method, without doing "part2", your phone is actually worse off than if you never did anything at all. If you do "part1", you really should also complete "part2".
This also means that if you use the current method, and then afterwards run "part1" only (for instance, to show a friend) - you might render the Amon_RA custom recovery unbootable. This puts you in a precarious place, especially if something goes wrong with your ROM. It is probably a good idea to remove the scripts in the "/sdcard/gscripts/" folder on your SD card, and also remove the Gscript Lite app from your phone. You have been warned.
enjoy
erisuser1
Last edited by erisuser1; August 8th, 2010 at 03:39 PM.
The Following 71 Users Say Thank You to erisuser1 For This Useful Post:
EU1, this looks awesome!! It will definitely help those that either 1) can't get the sdk to work or 2) get confused with the command lines. Once again your work in the community is very much appreciated!
It's amazing how far we've come in such a short time. From "no root for leakers" to this. Thanks to all of the trailblazers for the time/knowledge/talent. It seems like just yesterday we were watching a live broadcast of tereg in his v-neck and the "timing step".
Many thanks to all involved, everyone knows it's not easy to develop this stuff. And you did it all for the Eris users/community. Thank you.
The Following User Says Thank You to xx_bishop_xx For This Useful Post:
eu, you may want to add a standard disclaimer that people should do this at their own risk, that you won't take responsibility if they brick their device, etc.
eu, you may want to add a standard disclaimer that people should do this at their own risk, that you won't take responsibility if they brick their device, etc.
Quote:
Originally Posted by erisuser1
By reading this sentence, you agree that all further activities with the phone are "on your own head".
LOL.
When you buy a car, the dealer doesn't warn you that you might run over an infant with it.
Device(s): S3, Galaxy Nexus(wifi), TB(backup), DI(wife), Eris (love that thing)
Carrier: Not Provided
Thanks: 336
Thanked 484 Times in 358 Posts
Only one word comes to mind. "This is an incredible post" ! OK 5 words. I don't know how long it took you to do this but it's a monumental effort. Great work.
Device(s): Galaxy Nexus-AOKP w/ LeanKernel
Kindle Fire
Transformer Prime
Carrier: Not Provided
Thanks: 298
Thanked 273 Times in 200 Posts
I know that this is the root forum and it's where people are supposed to go to learn about root, but I think many people may shy away from it because a) they don't realize that there is now an easy root method or b) they are intimidated. Something like this should be stickied in main Eris forum. Surgeon and I wrote a Mac and PC tutorial...there are always a lot of questions that don't even pertain to the phone. I will be interested to see any roadblocks that people run into with this method. You just follow the pictures!
I can't wait to make my Eris a device I actually want to use (again)!
One question: There was tons of talk about using a SLOW SD card before you rooted. I believe that was during the "old" methods of rooting. Perhaps that is a moot topic now?
I can't wait to make my Eris a device I actually want to use (again)!
One question: There was tons of talk about using a SLOW SD card before you rooted. I believe that was during the "old" methods of rooting. Perhaps that is a moot topic now?
Correct - that was based on a rooting method that has been abandoned. "Old" in the sense of two or three weeks ago, LOL.
Root away!
The Following User Says Thank You to erisuser1 For This Useful Post:
Ok, I rooted my phone with the new version that came out a week ago. For the leakers. I can't get the boot loader engineering thing to work. the "S" is still on. Now am I rooted, or should I do this to finish and get the "S" off. So much info and so many places to find it, I got lost in the process.
Ok, I rooted my phone with the new version that came out a week ago. For the leakers. I can't get the boot loader engineering thing to work. the "S" is still on. Now am I rooted, or should I do this to finish and get the "S" off. So much info and so many places to find it, I got lost in the process.
This process does not (presently) touch either the "misc" partition or the bootloader ("hboot"). It produces the same result as what you used last week - the only real difference is this is set up so that there is no need to use a PC (either "adb" or "fastboot").
I am pretty sure that the "Main Version" overwrite (misc partition) method that jcase put together can be packaged up so that it can be installed using the Amon_RA recovery, as if it were a ROM overlay or "update.zip" type of install. I hope to get to that early next week, assuming that jcase doesn't beat me to it.
Once that happens, the process would be:
- make a Nandroid backup
- install the "misc/MainVersion" partition hack using Amon_RA recovery
- reboot into HBOOT with the ROOT PB00IMG.ZIP on the SD card, and install the ROOT ROM (overwriting the whole phone)
- re-perform this method (if you please, there are other ways too) on the "root ROM" install to re-install the Amon_RA recovery,
- boot into Amon_RA recovery, and restore your Nandroid backup.
That would give you a fully rooted phone (bootloader AND recovery), and with the same ROM you started with.
Once we have the "update.zip"-type install for the misc partition hack, the whole process can be achieved without using a PC at all.
Loops are funny because there are so many causes.... well, not funny to the user watching it going on.
Anyway, how about starting over? It's a pretty straightforward process.. make sure there is enough battery.. I'd charge it all the way up before starting.
I found that after a few false starts on rooting the very first time, it was best to just go real REAL slowly through the steps in a "dry run" prior to actually getting going on it.. patience.
so, should i just start from the recovery, since i dont think i can get back to the beginning?
So far you haven't really said what you did. Did you use this method? If so, what ROM did you try and load? Can you still get the recovery boot menu to show up?
The instructions tell you to make note of the battery charge state prior to running part2 - did you do that? What was the % value?
Note that if your phone will not boot, but the Amon_RA recovery boot comes up, you can still copy files to your phone by choosing the (Amon_RA) menu item
"USB-MS toggle".
You would do this if you thought something was wrong with your ROM, or you wanted to copy a different ROM onto your SD card from the PC.
All the normal precautions of copying files to the SD card need to be observed - for instance, always, always, always use the "Safely Eject Hardware" control on the (Windows) PC, waiting for it to tell you that it is "safe to remove hardware" before you dismount the SD card from the phone menu (in this case "USB-MS toggle")
Worst case, if you followed the instructions, you have a Nandroid backup - just charge your phone to 100%, reflash the Leak-V3 ROM (using the PB00IMG.ZIP method), and start over with the rooting procedure.
Thank you very much, i tried this method with 50% battery life, maybe that was it. still waiting on charging it, and i am still able to get to the recovery menu. just playing the waiting game right now i guess
This is an incredible write-up with incredible effort (as has been stated before). Absolutely well-written and written well for the intended audience. Awesome job.
I will wait for the zip file to be made for the "s" thing and boot loader. I can't get the engineering bootloader thing to work. I can't get past the custom.img to register in my cmd prompt. thanks for all the great work you guys are doing.
Just wondering how to do this? "Pick ROM of your choice downloaded onto your SD card in the root folder"" Do you just use your phone browser and download? How do u put it on your SD card in the root folder?
Just wondering how to do this? "Pick ROM of your choice downloaded onto your SD card in the root folder"" Do you just use your phone browser and download? How do u put it on your SD card in the root folder?
Thanks,
Big Dummy
If you download a ROM with the phone, it will end up in the
/sdcard/download
folder. But that's OK, because the above tutorial shows you exactly how to move a file from /sdcard/download to the "root" folder /sdcard. (Don't unzip the ROM file though!).
Because the ROMs are large (~ 70-100 MB), it takes a while to download a ROM to the phone - I suggest you plug the phone in to a charger, and set the option
Settings -> Applications -> Development -> Stay awake
so that the phone won't fall asleep while you are downloading. (If you are using WiFi, you might also want to set Settings -> Wireless & networks -> WiFi Settings -> (Menu -> Advanced) -> WiFi sleep policy -> Never while plugged in).
You can also copy it from a PC by connecting the phone to the PC via USB - but I'm not going to cover that, because this thread is about rooting without using a PC.
As far as picking a ROM, go do some reading at XDA Droid Eris Android Development. You might want to spend some time at this before you make a decision - some of the ROMs are quite similar to the "stock" OS and pretty rock-solid, and some of them require several workarounds to get certain features to work correctly.
What I would suggest you do is look carefully at the posts by the devs that release the ROMs - but not only for the information about the ROM. Look beyond that, and it will become evident to you which devs are thorough, and which ones rush to push things out without testing. Sloppy posts, weak details, no changelogs, no MD5 signatures - all hint that lack of attention to detail probably also happens while putting the ROM together.
Arrggghfh so freakin close! I followed all the steps, i got through step 1 no problem. Step 2 no problem. Even said i was rooted. Turned off phone. Turned it back on with vol up and end key got screen with recov like in example. Went to use scroll down with track ball,and the screenwouldnr move. Could not scroll with track ball. Only option was to re starr the the phone track ball click works but cant scroll to nand back up. also said I was rooted after I did 2nd script, however when I checked bootloader I was still on 1.49 with s still on . What the French? Toast?! Am I rooted ? If not can I just go back and tap on the two scripts to re run them? I thought the post said I could, I jusr wanted to confirm before I fry my phoone cause that's the luck I have had with root.
So i can go from the official OTA 2.1 with this? Or do I still need to go back to 1.5?
RyRy
edit: I see on post 18 that you did test on 2.1. My phone was just updated OTA with the July update. So this procedure works with this OTA OS? and I am able to do Kaosfroyo-v23 with this too? This is my first time ever doing a root to any phone and dont want to fudge it up.
Last edited by ticklemedaly; July 21st, 2010 at 08:01 AM.
So i can go from the official OTA 2.1 with this? Or do I still need to go back to 1.5?
RyRy
edit: I see on post 18 that you did test on 2.1. My phone was just updated OTA with the July update. So this procedure works with this OTA OS? and I am able to do Kaosfroyo-v23 with this too? This is my first time ever doing a root to any phone and dont want to fudge it up.
yes! i had the OTA and got this working! first time too, i thought i was going to mess it up, but i got a custom rom on there now.
__________________
HTC Eris
The Following User Says Thank You to rick311 For This Useful Post:
So i can go from the official OTA 2.1 with this? Or do I still need to go back to 1.5?
RyRy
edit: I see on post 18 that you did test on 2.1. My phone was just updated OTA with the July update. So this procedure works with this OTA OS? and I am able to do Kaosfroyo-v23 with this too? This is my first time ever doing a root to any phone and dont want to fudge it up.
Works with any official or leaked VZW/HTC release, so yes.
There is nothing about this method that specifically prevents or allows any given ROM; you could load ar stable one or a buggy one.
I'm a bit surprised that some folks that are brand new to this are choosing a FroYo ROM as their first plunge into rooting. While they are getting better all the time, they have been the least trouble free of all the ROMs - because they use a code base which is as far away from stock as you can possibly get.
But, I haven't been keeping up with them lately - perhaps I should have another look.
eu1
PS: You will always have your "stock" ROM to return to, should you decide you don't like your root experience, so long as you make a nandroid backup (making backups of your SD card to your PC is a good idea too - so you have a backup of your backup)
The Following User Says Thank You to erisuser1 For This Useful Post:
Arrggghfh so freakin close! I followed all the steps, i got through step 1 no problem. Step 2 no problem. Even said i was rooted. Turned off phone. Turned it back on with vol up and end key got screen with recov like in example. Went to use scroll down with track ball,and the screenwouldnr move. Could not scroll with track ball. Only option was to re starr the the phone track ball click works but cant scroll to nand back up. also said I was rooted after I did 2nd script, however when I checked bootloader I was still on 1.49 with s still on . What the French? Toast?! Am I rooted ? If not can I just go back and tap on the two scripts to re run them? I thought the post said I could, I jusr wanted to confirm before I fry my phoone cause that's the luck I have had with root.
Rats! I thought I answered this last night, and I get up in the morning, and my post is gone. Probably hit the preview button... I was dead tired last night.
A small number of people have reported trackball issues with the Amon_RA custom recovery. If I recall correctly, it happened to me once - but I pulled the battery, and never had the problem since.
The problem - whatever it is - must be something about the way the Amon_RA kernel interacts with the trackball; it doesn't have anything to do with this particular method of rooting, as the same thing has been occasionally reported using other rooting methods.
As for a fix, you might try completely powering off the device, removing the battery, and operating the trackball to eliminate any static charge when the device is first booted. Or, see if you observe any difference with the device with/without power applied through the USB. Or, just reboot a couple times and see if that makes any difference.
ok, so I tapped on part 1 and part 2 again hoping that the situation would change. it didnt. still frozen on fig 31 and track ball not moving . shut phone down after part 2 completed and said congratulations! you have root
edit nice i just now saw your post eu1 I will try this please tell me that i didnt screw my phone bu tapping parts 1 and two again? turned off phone and pulled bat. will leave like this for a few minutes and then see what happens. hopefully I will have good news. I appreciate all of your help
Last edited by kamots; July 21st, 2010 at 09:15 AM.
ok, so I tapped on part 1 and part 2 again hoping that the situation would change. it didnt. still frozen on fig 31 and track ball not moving . shut phone down after part 2 completed and said congratulations! you have root
edit nice i just now saw your post eu1 I will try this please tell me that i didnt screw my phone bu tapping parts 1 and two again? turned off phone and pulled bat. will leave like this for a few minutes and then see what happens. hopefully I will have good news. I appreciate all of your help
No, you didn't screw up your phone. The fact that you are seeing the Amon_RA menu means my part of things are working. Repeating the install is unlikely to help, other than the effects that rebooting might have.
The Following User Says Thank You to erisuser1 For This Useful Post:
so is there any benefit of rooting with the manual method over this method?
do you get the same results with either method?
likewise. Also, approx how much time does this take? Im about to head out on a trip for the weekend and my time is very limited. Dont want to not have a phone if something gets screwed on my end due to myself screwing it up.
And, do I need to have the same SD card in at all times afterwords? I have my stock 8GB one that I'm not using, and like my PSP that I hacked years ago, I had a second SD card for doing the dirty work, while keeping my good one for normal everyday use.
Help I followed your directions to a T and I got to the last one to flash a new rom and I can't find the rom I downloaded All I have is gscript.zip and pb00img.zip any ideas? Thanks
4Likes
Universal Eris Root for Dummies!
[ fig. 1 ]
[ fig. 2 ]
[ fig. 3 ]
[ fig. 4 ]
[ fig. 5 ]
[ fig. 6 ]
[ fig. 7 ]
[ fig. 8 ]
[ fig. 9 ]
[ fig. 10 ]
[ fig. 11 ]
[ fig. 12 ]
[ fig. 13 ]
[ fig. 14 ]
[ fig. 15 ]
[ fig. 16 ]
[ fig. 17 ]
[ fig. 18 ]
[ fig. 19 ]
[ fig. 20 ]
[ fig. 21 ]
[ fig. 22 ]
[ fig. 23 ]
[ fig. 24 ]
[ fig. 25 ]
[ fig. 26 ]
[ fig. 27 ]
[ fig. 28 ]
[ fig. 29 ]
[ fig. 30 ]
[ fig. 31 ]
[ fig. 32 ]
[ fig. 34 ]
[ fig. 35 ]
[ fig. 36 ]
[ fig. 37 ]
[ fig. 38 ]
[ fig. 39 ]
[ fig. 40 ]
instead of a retort.
it keeps looping the "htc quietly brilliant" image
My rom .zip file can't be found
