Root Universal 1 Click Eris App Apk - No PCs, No Scripts Needed, EASY

[erisuser1]

itbedave,

The only thing I can think of as to why this works comes from zach.xtr dev thread over on XDA where he says:

Cache Location (Cache2cache):
By default, the dalvik-cache has been relocated from the internal /data/dalvik-cache/ directory to the internal /cache/dalvik-cache directory. The Eris comes with an internal /cache/ file block of 130mb that is not used! After reviewing a number of xda member file system usage reports (thanks xtrROM and xtrSENSE users!) the MOST reported use of this space was 5%... So by moving the dalvik-cache to this free area you now have over 150mb on internal /data/ for apps and over 75mb in internal /cache/ for dalvik-cache. This means that you can probably install close to 100 apps WITHOUT having to partition and move anything to the SD Card ext!

Pretty cool, really. So, I'm wondering (guessing, really) if your Dalvik-cache was rebuilt anyway for you when you first booted (like it would have to be if you wiped your Dalvik-cache).

Anyone know for sure?

Cheers!

That's a pretty good catch there , s.a.

Almost every dev ROM wipes /system at the beginning of the install, so if the dalvik cache is relocated, then the only thing which remains is the market apps and "settings and data" for all apps. Clearly there will not be an incompatibility between the Market apps and their data, so what remains in question is only a possible version conflict between system apps and their data. In this case, though, the system apps were largely Sense 2.1 in both cases (before and after), so it is highly unlikely there was any version changes for the Sense 2.1 apps or their foundation classes.

I don't think that an example like this - overlaying one ROM with a nearly identical 2nd ROM - can be used as a justification for never wiping (although I certainly understand what the appeal is)

 

[scary alien]

That's a pretty good catch there , s.a.

Lol, thanks, I appreciate that! Even a broken watch is right twice a day, eh?

Some of this stuff is starting to sink in...(a vast portion of which is through your tutelage).

 

[MrGrimxx]

Oh Hi there. Ok well im looking into rooting my Eris, tired of it slowing down and stuff. Can I use this "1 click method" and then just use the new V35 Rom KaosFroyo.
And thats all I will need and to do?

 

[sparhawk]

I rooted my Eris last night and went with V35-1 Rom KaosFroyo and love it. Like having a new phone. I read around a lot and chose the 1 click method mainly because I wanted to find a simple way I could port to all my technically challenged friends. Everything went well, and Im pleased. Couple quick things.

I understand the confusion between step #2 and #3 discussed earlier in the thread. Might be different somehow for others but for me, running the 1 click app DOES NOT auto reboot your phone. It DOES take a normal manual reboot and then a second shutdown before bringing it back up into recovery mode. Recovery mode for me was Vol -(down) and the power button, not Vol +(up) and power as the guide states. Took me a few tries to figure that part out. All in all a great guide though, thanks. Since I was loading a custom rom i did the wipe on both memories.

 

[scary alien]

I understand the confusion between step #2 and #3 discussed earlier in the thread. Might be different somehow for others but for me, running the 1 click app DOES NOT auto reboot your phone. It DOES take a normal manual reboot and then a second shutdown before bringing it back up into recovery mode. Recovery mode for me was Vol -(down) and the power button, not Vol +(up) and power as the guide states. Took me a few tries to figure that part out. All in all a great guide though, thanks. Since I was loading a custom rom i did the wipe on both memories.

Glad this worked well for you, sparhawk, and welcome to Android Forums!

Thank you for the reboot clarification--I'm sure that will help a few future rooters out (provided they read this ).

Yeah, there've been a few members posting about their difficulties in entering recovery and a few alternatives have been posted in this thread already (eu1 has already conjectured that some phones (HBOOT 1.46.xxx?) can't seem to enter recovery using vol-UP + end/power). Thankfully, there's a couple of ways to skin that cat...

Cheers!

 

[erisuser1]

I understand the confusion between step #2 and #3 discussed earlier in the thread. Might be different somehow for others but for me, running the 1 click app DOES NOT auto reboot your phone. It DOES take a normal manual reboot and then a second shutdown before bringing it back up into recovery mode.

It behaves that way for everybody. I know that "prj" was trying to be helpful, but appearances are that he put together his guide without even attempting to test what he was saying. Worse yet, rather than just editing his instructions- after being told something like 3 times that his instructions were incorrect between (the first) steps #2 & #3 - he duplicated the incorrect instructions 3 times.

[ Edit ] prj corrected his instructions on 9/26/2010, so the following is now obsolete.

I wish he would change them - all three of them.

As I said, I know that "prj" was trying to be helpful, because the OP was very brief; but being correct is part of being helpful.

eu1

 

[sparhawk]

Ok, this is slightly off topic, but hopefully someone can point me in the right direction.

Here is where I'm at.

I used 1 Click and rooted perfectly, all is good, and im happy with results.

I loaded the custom rom V35-1 Rom KaosFroyo and its working great. I chose to load this rom instead of the rootme.zip that came with 1 Click b/c I was sure KaosFroyo was for me. (ive read and researched ALOT)

Now to my issue: My end goal here is PS3Freedom, but im not asking for help with that here. What I've found is that although I'm rooted, I do not get the "S-Off" when I go into recovery, meaning I cant do fastboot (needed for PSFreedom and some other stuff im reading). So I've read this means that my bootloader is not fully unlocked.

I am trying to learn what exactly this means, I cant find a clear explanation anywhere. I want to be able to add this additional function to my rooted phone, hopefully without having to reroot or anything real drastic. I've read a few places that there are *.zip files out there that will flash this to an already rooted phone without starting all over.

Any help with this would be much appreciated.

 

[doogald]

I used 1 Click and rooted perfectly, all is good, and im happy with results.

I loaded the custom rom V35-1 Rom KaosFroyo and its working great. I chose to load this rom instead of the rootme.zip that came with 1 Click b/c I was sure KaosFroyo was for me. (ive read and researched ALOT)

Now to my issue: My end goal here is PS3Freedom, but im not asking for help with that here. What I've found is that although I'm rooted, I do not get the "S-Off" when I go into recovery, meaning I cant do fastboot (needed for PSFreedom and some other stuff im reading). So I've read this means that my bootloader is not fully unlocked.

I think that the instructions that you need are here: How To Install Engineering bootloader FOR LEAK ROOTERS - xda-developers

 

[sparhawk]

I think that the instructions that you need are here: How To Install Engineering bootloader FOR LEAK ROOTERS - xda-developers

OK I've figured this out and now I have the correct S-OFF bootloader installed and Im back up with my custom rom as good as before. Was a bit stressful though.

The link you gave had ALOT of conflicting info in it, as is often the case. Filtering through I was able to get it done. I'm going to post a quick guide here hoping to help anyone else who wants to do this too, since there is NO good guide out there that I could find.

Assumptions/Prereqs

1. You have already rooted your phone
2. You have already loaded any custom rom, doesnt matter which one
3. You have made a nandroid backup of your current phone setup
4. You are doing this b/c you want to have a unlocked or "S-Off" bootloader that will let you use fastboot among other things.
5. You must install the android SDK on your PC, google it.
6. You must install the USB drivers for your phone if you havnt already. Easy way to do this is download and install the PDAnet PC client from Download PdaNet and install it. Part of its install sets up the USB drivers easily.

Step by Step (files needed can be found on other forums, start with the links at the bottom of this post if you are having any trouble finding them)

1. Download the Original Root Rom PB00IMG.zip and put it in the root of your SD Card.
2. Download Amon's Recovery recovery.img , and put it in your tools directory of the SDK
\tools\recovery.img
3. Copy your Nandroid backup off of your SD Card and put it in the tools directory of the SDK as well, you need 3 flies.
\tools\boot.img
\tools\system.img
\tools\data.img
4. Power off your phone and boot it while holding down Vol- and power. This will autoload the PB00IMG.zip file and it will take awhile, watch the blue progress bar in the upper right corner of the screen. It will eventually ask if you want to update, choose yes and let it do its thing. After it finishes it will ask you to reboot.
5. This is VERY important. Save yourself some trouble, I didnt do this and the resulting worry headache I got plagues me still. REMOVE your SD Card from the phone and using a card reader or whatever other method, delete that PB00IMG.zip file from the card. If you dont, this process will just repeat over and over since it loads it automatically in step #4.
6. Put your card back in and then reboot with Vol- and power. You will now see the S-Off at the top of the screen instead of the S-On that was there before. Plug your phone to the PC and select Fastboot on the phone.
7. From a command prompt in the tools directory of the SDK type this:
fastboot flash recovery recovery.img
It will do this:
sending 'recovery' (3834 KB)... OKAY
writing 'recovery'... OKAY

All Done now you just have to load your Nandroid image and you will be back to normal with a newly unlocked bootloader. At this point you could just load up another custom rom as you did when you rooted from the recovery screen, if you dont mind doing all your setup all over again.

Recovering your Nandroid:

I had an issue here where my phone WOULD NOT load the Nandroid image from the recovery menu. Dont know why, I wasnt expecting that, if someone knows why please let me know. I had to find an alternative method to reloading my Nandroid (this is why I had you put your Nandroid image in the tools directory before we started.)

*EDIT* I have since learned that my problem was most likely that my battery was below 30% at this point in the mod, and Amon's Recovery will not restore when it is that low. I have not tested it but I think that was the problem. So, the below instructions for recovering your nandroid still apply if for some reason Amon's Recovery will not load them, but as long as you are above 30% battery, you can do it the normal way from within the recovery program.

At this point if you havnt touched anything your phone is plugged to the USB and you are sitting at a command prompt having just loaded that recovery file. Now we load your Nandroid image through the command prompt as well.

1. Run these commands on the PC cmd prompt in the tools directory:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata data.img
Confirmations of it sending and writing the files will follow after each command when you run it.
2. Thats it, unplug your phone and do a NORMAL boot. You will be right where you left off before you were crazy enough to try to unlock your bootloader and change it to S-Off.


This seems like alot I know, but its really not that much. I put it all down in detail because I hate it when someone posting a guide is not clear and precise.

Tying this all back up with the 1 Click Root experience, it leaves me wondering if someone could put an unlocked bootloader within 1 Click and save people the trouble of all this mess. I'm not a Dev so I dont know if its even possible, but it sure would save people alot of work. Anyway, if you read this far, thanks for reading and I hope I helped someone other than myself. 1 Click is a great application/method and I wanted to give back a bit.

I have to give credit to the guys posting in the following forums for this. I picked and poked at what they said, and added in my own experiences.

How To Install Engineering bootloader FOR LEAK ROOTERS - xda-developers
http://androidforums.com/eris-all-things-root/75384-visual-example-pb00img-zip-update-method.html
How to Restore a Nandroid Backup - GetYourDroidOn

 

[scary alien]

sparhawk,

Congrats! You just rooted the old-school way (like a lot of us did) .

FYI, you should be able to move or remove the PB00IMG.zip file after you've booted for the first time using that base root ROM (i.e., you don't really have to physically remove the /sdcard). You can just boot normally (into that very early, buggy version of 2.1 Android), and download Astro from the Market, navigate to the /sdcard folder and delete or rename that file.

Booting into HBOOT like you did (volume-DOWN and end/power simultaneously takes you into HBOOT and a file named PB00IMG.zip is exactly the file that he's looking for). So, yes, deleting or moving that file is a good idea .

Also, regarding your Nandroid backup, you didn't happen to rename your Nandroid backup folders to contain spaces in the name did you? That will keep Amon_RA's custom recovery from seeing your backups.

Here's some information, courtesy of erisuser1, regarding the engineering bootloader:

- http://androidforums.com/eris-all-t...o-pcs-no-scripts-needed-easy.html#post1283520

- http://androidforums.com/eris-all-things-root/139536-s-off-1-49-2-hboot-update-zip-format.html (jcase has pulled the plug on this for now...)

Cheers!

 

[sparhawk]

sparhawk,

Congrats! You just rooted the old-school way (like a lot of us did) .

FYI, you should be able to move or remove the PB00IMG.zip file after you've booted for the first time using that base root ROM (i.e., you don't really have to physically remove the /sdcard). You can just boot normally (into that very early, buggy version of 2.1 Android), and download Astro from the Market, navigate to the /sdcard folder and delete or rename that file.

Booting into HBOOT like you did (volume-DOWN and end/power simultaneously takes you into HBOOT and a file named PB00IMG.zip is exactly the file that he's looking for). So, yes, deleting or moving that file is a good idea .

Also, regarding your Nandroid backup, you didn't happen to rename your Nandroid backup folders to contain spaces in the name did you? That will keep Amon_RA's custom recovery from seeing your backups.

Cheers!

OK that explains a few things to me then. I didnt realize that PB00IMG.zip was an actual rom much like any other custom rom. The info I found was very unclear about that. When I did my own custom rom load I did it by firing it off in Amon's so I didnt make that connection. You say that PB00IMG.zip is an old buggy version of 2.1, I noticed it updated the radio and a few other things when it was flashing the bootloader. (I didnt trust the battery pull method, so I just let it complete) Do I now need to check my radio and make sure I didnt revert it back to an older less functional version? And if so, how do I do that, and where would I get the updated radio.

For the Nandroid, no I didnt rename any directories or files when I tried to get Amon's to load it. It was on my SD card wherever Amon's natively stores it. I wish I would have written down the error it gave me, b/c I want to understand for future reference. But I do remember that it returned with an error telling me that Amon's could not restore and said to try manually using the adb push method. My research lead me to a fastboot method, and since that was working now, I used that method instead.

 

[doogald]

Do I now need to check my radio and make sure I didnt revert it back to an older less functional version? And if so, how do I do that, and where would I get the updated radio.

It may be different for the exact spot, but settings->about phone, you are looking for the baseband version. I'll give you the location of the new radio, with the caveat that if you do not have problems like the silent audio bug, you may just want to stay where you are.

The latest radio is 2.42.01.04.27 and you can find it here: July 2010 Eris Radio - 2.42.01.04.27 - xda-developers

For the Nandroid, no I didnt rename any directories or files when I tried to get Amon's to load it. It was on my SD card wherever Amon's natively stores it. I wish I would have written down the error it gave me, b/c I want to understand for future reference. But I do remember that it returned with an error telling me that Amon's could not restore and said to try manually using the adb push method. My research lead me to a fastboot method, and since that was working now, I used that method instead.

Just a guess, but was your battery lower than 30% when you tried to restore? Amon's Recovery will stop the Nandroid restore if the battery is too low, probably as a safety measure to make sure that you don't end up with a partial restore when the battery fails.

 

[sparhawk]

It may be different for the exact spot, but settings->about phone, you are looking for the baseband version. I'll give you the location of the new radio, with the caveat that if you do not have problems like the silent audio bug, you may just want to stay where you are.

The latest radio is 2.42.01.04.27 and you can find it here: July 2010 Eris Radio - 2.42.01.04.27 - xda-developers




Just a guess, but was your battery lower than 30% when you tried to restore? Amon's Recovery will stop the Nandroid restore if the battery is too low, probably as a safety measure to make sure that you don't end up with a partial restore when the battery fails.

Thanks for the radio info. My radio is 2.40.00.01.22 is there any known issue with that version, should I update it? I dont currently notice any problems but if it were to mean a stronger signal places that I'm normally weak, it might be worth it.


Yes that was it, most definitely was below 30%, started at 100% when I began the mod, but I did notice when it was all over i had about 10% left (which scared me a bit). That's great, it would have bothered me not knowing. I have sense done another nandroid restore (now that I understand everything better I wanted a clean install) and it went fine with Amon's so that had to be it.

 

[doogald]

Thanks for the radio info. My radio is 2.40.00.01.22 is there any known issue with that version, should I update it? I dont currently notice any problems but if it were to mean a stronger signal places that I'm normally weak, it might be worth it.

I had no problems with that radio myself, but I did the manual update. I noticed no difference at all - in signal reception, etc. People with the silent call bug I believe have had that problem fixed with the new radio. It may have also fixed WiFi issues for others - I can't recall.

You can install it if you wish, but do make sure that the battery is very high! Check the MD5 hash of the file when you move it to the phone to make sure that the file is complete. Scary Alien has written a great Android app to check MD5s right on the phone; see here: http://androidforums.com/eris-all-things-root/168942-phone-rom-checksum-verifier.html

(The MD5 hash of the radio file is right in that first post of the thread I gave you a couple of posts ago.)

 

[knitpurlgurl]

Okay, please be gentle - I'm an utter tech idiot. I downloaded this app. Then I rebooted. I have no idea if I have Amons recovery or not. Also if I go into the reboot screen (power, vol up), I cannot toggle between the choices with my trackball. HELP, please. Does this mean I am not yet rooted? And also, I know this is another really newb question, but how can I tell if I am rooted?

Thanks again for being so patient!

 

[scary alien]

Okay, please be gentle - I'm an utter tech idiot. I downloaded this app. Then I rebooted. I have no idea if I have Amons recovery or not. Also if I go into the reboot screen (power, vol up), I cannot toggle between the choices with my trackball. HELP, please. Does this mean I am not yet rooted? And also, I know this is another really newb question, but how can I tell if I am rooted?

Thanks again for being so patient!

knitpurlgurl (cool name, btw), welcome to the Android Forums!

First off, you need to be really specific about what you have done...if you've only downloaded the app and rebooted, then nothing really happened--but that's okay and easy to fix.

Just carefully follow jcase's steps in the very first post (like I'm sure you've read). You might want to read through all of the posts in this thread (its actually not a very long thread compared to some others) so you can get a feel for where others have gotten stuck and subsequently unstuck .

Assuming you've still got the app downloaded, go ahead an re-do step #2 (run the app). Then, for step #3 (reboot) you need to power off the phone and then power it back on.

Once you've done that, you can try booting into recovery by doing this:

- power down the phone again

- boot into Amon_RA's custom recovery by holding and pressing the volume-UP button (don't let go yet) AND the end/power button simultaneously. Keep hold the volume-UP button until you see Amon_RA's recovery menu (it should only take about 10 or 15 seconds and will look like figure 33 in this post http://androidforums.com/eris-all-things-root/127861-universal-eris-root-dummies.html#post1186824) [by the way, reading that particular post (and thread) will explain and demonstrate a lot of good root practices and information--you would be doing yourself a big favor by reading through it. In fact, if you are going to flash a custom ROM, you really need to read through this post so that you know how to make a Nandroid backup, do the wipes, an flash your selected target file.]

From here, you'll select either the "rootme.zip" file that jcase's app already put in the top-level of your /sdcard or a custom root ROM that you've downloaded and placed there too, and select the "Flash zip from sdcard" option in Amon_RA's custom recovery

After you've flashed one of the above, you will be "rooted" and you can return to the main menu (use the volume-down toggle) and select "Reboot system now" (what happens when you reboot depend of whether or not you used the rootme.zip or a custom ROM)

Finally, make sure USB debugging is on (Settings -> Applications -> Development -> USB debugging (checked))

To see the fruits of your rooting, you can download something like drocap2 (screen capture) to test-out if you are rooted. There are several other ways to tell to: download and install Android Terminal Emulator, type "su" and see if you are prompted by the SuperUser app for permission. If you are rooted (and are prompted and give the app permission), then you'll see a "#" prompt which indicates root capability.

Okay, I saved your trackball question for last...if you really are able to get into Amon_RA's custom recovery and your trackball isn't working...well, things get a little stickier. I would first advise trying to clean your trackball (http://androidforums.com/htc-droid-eris/54173-trackball-cleaning.html#post449512). I'm reluctant to post more information regarding alternatives until we hear more about your current situation.

Hope this helps! Cheers.

 

[knitpurlgurl]

knitpurlgurl (cool name, btw), welcome to the Android Forums!

First off, you need to be really specific about what you have done...if you've only downloaded the app and rebooted, then nothing really happened--but that's okay and easy to fix.

Just carefully follow jcase's steps in the very first post (like I'm sure you've read). You might want to read through all of the posts in this thread (its actually not a very long thread compared to some others) so you can get a feel for where others have gotten stuck and subsequently unstuck .

Assuming you've still got the app downloaded, go ahead an re-do step #2 (run the app). Then, for step #3 (reboot) you need to power off the phone and then power it back on.

Once you've done that, you can try booting into recovery by doing this:

- power down the phone again

- boot into Amon_RA's custom recovery by holding and pressing the volume-UP button (don't let go yet) AND the end/power button simultaneously. Keep hold the volume-UP button until you see Amon_RA's recovery menu (it should only take about 10 or 15 seconds and will look like figure 33 in this post http://androidforums.com/eris-all-things-root/127861-universal-eris-root-dummies.html#post1186824) [by the way, reading that particular post (and thread) will explain and demonstrate a lot of good root practices and information--you would be doing yourself a big favor by reading through it. In fact, if you are going to flash a custom ROM, you really need to read through this post so that you know how to make a Nandroid backup, do the wipes, an flash your selected target file.]

From here, you'll select either the "rootme.zip" file that jcase's app already put in the top-level of your /sdcard or a custom root ROM that you've downloaded and placed there too, and select the "Flash zip from sdcard" option in Amon_RA's custom recovery

After you've flashed one of the above, you will be "rooted" and you can return to the main menu (use the volume-down toggle) and select "Reboot system now" (what happens when you reboot depend of whether or not you used the rootme.zip or a custom ROM)

Finally, make sure USB debugging is on (Settings -> Applications -> Development -> USB debugging (checked))

To see the fruits of your rooting, you can download something like drocap2 (screen capture) to test-out if you are rooted. There are several other ways to tell to: download and install Android Terminal Emulator, type "su" and see if you are prompted by the SuperUser app for permission. If you are rooted (and are prompted and give the app permission), then you'll see a "#" prompt which indicates root capability.

Okay, I saved your trackball question for last...if you really are able to get into Amon_RA's custom recovery and your trackball isn't working...well, things get a little stickier. I would first advise trying to clean your trackball (http://androidforums.com/htc-droid-eris/54173-trackball-cleaning.html#post449512). I'm reluctant to post more information regarding alternatives until we hear more about your current situation.

Hope this helps! Cheers.

Thanks so much for your infinite patience!!! I will read the entire thread and also the thread on universal eris root for dummies!!! Let me read through those and then try the steps again. Then I'll post an update! Again, thanks so much!!

 

[willy0508]

Also note: after flashing just the rootme.zip, you will have a rooted 2.1 phone. Your root "powers" at this point will be the ability to run root-only applications like wi-fi tethering, drocap2, Root Explorer, etc. You will not be able to overclock [yet] (there is a way, but you've got more stuff to do).

Hi all, great thread! New to posting but been reading a lot! I'm ready to root (in the morning as I'm getting tired). Read this whole thread and wonder if Scary alien can elaborate more on the quote.

Can I overclock using the rootme.zip? If so how? Or do I need to flash a custom rom to get overclock ability. I like my stock setup but wanted to overclock. I may just go with xtrSENSE as it looks pretty good but wanted to keep all my settings.

Thanks and sorry if I missed this info somewhere.
willy0508
And thanks to all who developed this method and those who answered all our 'newbie' questions!

 

[scary alien]

Hi all, great thread! New to posting but been reading a lot! I'm ready to root (in the morning as I'm getting tired). Read this whole thread and wonder if Scary alien can elaborate more on the quote.

Can I overclock using the rootme.zip? If so how? Or do I need to flash a custom rom to get overclock ability. I like my stock setup but wanted to overclock. I may just go with xtrSENSE as it looks pretty good but wanted to keep all my settings.

willy0508,

Sure...no problem. If you just root your phone "in-place" with the rootme.zip, you are basically just giving your current phone, root access / capability. This allows you to keep everything you've got and setup on your phone without losing anything and yet gaining root.

That being said, you are fairly limited on what you can do with these new root abilities (installing root-only apps, removing bloatware, etc.). To do something like overclocking, you'd have to replace your phone's kernel with one that supports being overclocked.

To do this, you would obtain (download) something called Zanfur's overclock patch and flash it like you would/did the rootme.zip file. Here's a post I made a while back about how to do this: http://androidforums.com/eris-all-things-root/135849-how-do-i-flash-oc-patch.html#post1253948

After you do this, you just reboot like normal. Then, you can download setCPU from the Market (just a buck or two (or free from XDA if you register over there)). The setCPU program (there's also something called the Overclock Widget, but I don't have much experience with that one) will then be able to manipulate things in the kernel to cause overclocking to occur.

Check out the other posts in that same thread above (http://androidforums.com/eris-all-things-root/135849-how-do-i-flash-oc-patch.html) that point you to other threads regarding good settings for overclocking.

By the way, xtrSense comes highly-recommended. Most custom root ROMs either are overclocked or are overclock-ready. You'll have to read the dev's thread for a particular ROM for any details.

Good luck and I hope this helped. Cheers!

P.S. welcome to the Android Forums!

 

[willy0508]

Thanks, just the answer I was looking for. I'll probably do Zanfur's first then make the switch to xtrSENSE. You guys are the best!

I'm sure I'll be back lurking and asking more questions.

 

[prj]

It behaves that way for everybody. I know that JPS was trying to be helpful, but appearances are that he put together his guide without even attempting to test what he was saying. Worse yet, rather than just editing his instructions- after being told something like 3 times that his instructions were incorrect between (the first) steps #2 & #3 - he duplicated the incorrect instructions 3 times.

I wish he would change them - all three of them.

As I said, I know that JPS was trying to be helpful, because the OP was very brief; but being correct is part of being helpful.

eu1

JPS? I assume your referring to me? In any case if there is a screw up in the instructions I did...moderators feel free to edit my post.

 

[scary alien]

JPS? I assume your referring to me? In any case if there is a screw up in the instructions I did...moderators feel free to edit my post.

prj,

You clearly spent a lot of time and effort to rewrite the OP's instructions, presumably with the intent of wanting to share and help others. Asking the moderators to update your posts to make some fairly simple edits is a little unfair, IMO.

I've been on the receiving-end (many times) of having it pointed-out that my posts were either incorrect or incomplete. Although chagrined at having tried my best to not make mistakes in the first place, I was happy to go back and re-edit so that future readers would not be led astray.

I hope you'll reconsider.

 

[erisuser1]

JPS? I assume your referring to me?

Yep. See? everybody makes mistakes - me too. I'll go back and edit my post; pretty simple to do, really. And I'll even delete my complaint-post when your corrections are finished. (Sure, it will make the thread read a little funny, but at least when others follow in our footsteps they won't experience a mis-step.)

eu1

 

[sparhawk]

I've been using my rooted eris now for almost a week, since I first came to this thread. I must say I'm very pleased. Everything is faster and more stable, I'm so glad I dont have to wait 2-3 seconds just for the call button to catch up with me like it used to.

Since first rooting with 1 Click, ive done the following:

-tried several custom roms, i still like Kaos Froyo the best
-rerooted (sort of) to get the unlocked S-off bootloader
-updated my radio with a zip flash
-rooted my wifes phone
-rooted my friends at work
-got fastboot working and launched into PSFreedom

Im a tech junkie and all this extra fun i've had with my somewhat dated phone has been a blast. Thanks to everyone who helped.

 

[prj]

prj,

You clearly spent a lot of time and effort to rewrite the OP's instructions, presumably with the intent of wanting to share and help others. Asking the moderators to update your posts to make some fairly simple edits is a little unfair, IMO.

I've been on the receiving-end (many times) of having it pointed-out that my posts were either incorrect or incomplete. Although chagrined at having tried my best to not make mistakes in the first place, I was happy to go back and re-edit so that future readers would not be led astray.

I hope you'll reconsider.

I edited my post #192 and fixed the issue between steps 2 & 3.

You'll have to forgive me. I have been participating on another android forum where the users aren't allowed to edit their posts and I was thinking that it was this forum for some reason. That is why I had asked the moderators to edit as necessary.