• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Universal Eris Root for Dummies!

So I'm having a problem.

Everything seemed to work fine, I got the "you have ROOT" message and I couldn't boot into the custom recovery.

Holding up and power booted the original OS.

Holding down and power too me to the hboot (1.47) and I hit the volume up as instructed and it opened the "lock sim" iirc, phone rebooted and nothing. It does seem to be acting a bit wacky now as well as I can't update my PRL. Text send fine and calls seem to be fine s'well.

tried running root part 2 a second time and got some error, can't remember. but I kind of gave up. Suggestions?
 
JoshH1 said:
So I'm having a problem.

Everything seemed to work fine, I got the "you have ROOT" message and I couldn't boot into the custom recovery.

Holding up and power booted the original OS.

Holding down and power too me to the hboot (1.47) and I hit the volume up as instructed and it opened the "lock sim" iirc, phone rebooted and nothing. It does seem to be acting a bit wacky now as well as I can't update my PRL. Text send fine and calls seem to be fine s'well.

tried running root part 2 a second time and got some error, can't remember. but I kind of gave up. Suggestions?
Click to expand...

Try this rooting method and see if you get a different result:

http://androidforums.com/all-things...is-app-apk-no-pcs-no-scripts-needed-easy.html


The root exploit which is being used is so simple that it is extremely hard to believe that what you are observing has anything to do with this method. In particular, the only time I have ever observed that "lock sim" menu item in the bootloader was when there was a PB00IMG.ZIP file on the root folder of the SD card, and then I aborted out of an install of that file. ??

Here's what the root exploit does.

1) It replaces a world-writable file with a symbolic link which points to the device file for the recovery partition. (This is "part1") Then you reboot the phone.

It does this because the HTC boot scripts have some startup code which perform a "chmod 777" on that file. But because there is no file there, but a symbolic link instead, what happens is that the device file for the recovery partition gets set to a file mode of "777" - which means that any user can then write data into that (recovery) partition

When you reboot the phone, it is possible that the recovery partition gets corrupted - normally, the "mid.txt" file (which gets replaced by the symlink) is 16 bytes long, so, if the first 16 bytes of the recovery partition got overwritten, then it could be corrupted. However,

2) After the reboot, the "part2" script overwrites the recovery partition with the custom recovery (Amon_RA), and then removes the symbolic link and puts the "mid.txt" file back so that no further corruption of the recovery partition is possible.



JoshH1 said:
tried running root part 2 a second time and got some error, can't remember.
Click to expand...

If you don't know what the error message is, then I certainly don't either. Is this an invitation to play 20 questions?

Try either the alternate method (link above) or, repeat this method again. When you repeat it, pay special attention to the following:

- Did you verify the md5sum of the "gscript.zip" file you downloaded?
- Did you make sure there is no PB00IMG.ZIP file in the root folder of your SD card?
- run part1, then reboot, then run part2, then power off ASAP
- press Vol-DOWN + End/Power to start the phone in HBOOT mode, and press Vol-Up to go into recovery.

eu1


PS Because your phone has the 1.47 bootloader on it, it can also be rooted the "old-fashioned" way with the ROOT PB00IMG.ZIP file. Not saying you should try that just yet, because it requires using the PC with the SDK and setting up Windows drivers and all that - the two newer methods are a lot easier. You should try those methods first before doing the original rooting method.
 
Thank you. I'm going to attempt the .apk method. I appreciate your help.

Would the "lock sim" be causing the PRL updates not working? Or am I just being hesitant?
 
erisuser1 said:
Are you saying that the phone will not boot at all, or that it hangs only when you try to start the recovery boot with Vol-Up+End/Power ? (There is no reason to believe that this method - if you only perform those first two steps - would keep the pre-existing OS from booting/running correctly)

(BTW, it should normally take about 8-10 seconds after the 3 skateboarding Droids before you see the Amon_RA recovery menu).

If the phone boots the normal OS correctly, then I would repeat both root_part1 and root_part2. Please inspect the output screen in each case for any evidence of unusual error messages.

eu1


PS As the instructions say, you should not be performing root_part2 unless your battery is well charged - say, > 80%
Click to expand...

It will boot if i just use power on like before i tried this rooting process. My problem is that after i get the message congrats you have root like in figure 31 i lock up when trying to boot into recovery. When i do it the way listed with the volume up and power it locks at the 3 skaters and i have let it set for 30 minutes. I then have to remove the battery to get off the screen. If i try it using volume down and power it takes me to the screen where i can hit volume up and into recovery but as soon as i select that it locks with the 3 skaters again and i am forced to remove the battery to do anything.
 
JoshH1 said:
Thank you. I'm going to attempt the .apk method. I appreciate your help.

Would the "lock sim" be causing the PRL updates not working? Or am I just being hesitant?
Click to expand...


Doubtful. "Lock Sim" applies to GSM phones, and the Eris is not a GSM phone. (I know it seems a little weird that you would even see anything related to GSM on your phone, but HTC likely shares bootloader code across many models of phones)

eu1
 
vannman17 said:
It will boot if i just use power on like before i tried this rooting process. My problem is that after i get the message congrats you have root like in figure 31 i lock up when trying to boot into recovery. When i do it the way listed with the volume up and power it locks at the 3 skaters and i have let it set for 30 minutes. I then have to remove the battery to get off the screen. If i try it using volume down and power it takes me to the screen where i can hit volume up and into recovery but as soon as i select that it locks with the 3 skaters again and i am forced to remove the battery to do anything.
Click to expand...
Try repeating

- part1
- reboot
- part2
- shut down
- boot to HBOOT with Vol-Down followed by Vol-up (as indicated in the menu).

If you see any error messages, please report what you see verbatim.



Just out of curiosity, is your HBOOT version also 1.47 ?

eu1
 
erisuser1 said:
Try repeating

- part1
- reboot
- part2
- shut down
- boot to HBOOT with Vol-Down followed by Vol-up (as indicated in the menu).

If you see any error messages, please report what you see verbatim.



Just out of curiosity, is your HBOOT version also 1.47 ?

eu1
Click to expand...

Ok tried again and i got no errors at all. Before i started i removed all the files and started over by downloading GScript again and followed all instructions.

Sure enough after i got the congrats you have root message i power off and then power back on with Vol up and end and it locked again at the skaters. I removed battery and tried with vol down and end and it took me to where i can hit vol up to boot to recovery and once doing that it goes to the 3 skaters and locks again.

That screen said i was on HBOOT 1.46
 
vannman17 said:
Ok tried again and i got no errors at all. Before i started i removed all the files and started over by downloading GScript again and followed all instructions.

Sure enough after i got the congrats you have root message i power off and then power back on with Vol up and end and it locked again at the skaters. I removed battery and tried with vol down and end and it took me to where i can hit vol up to boot to recovery and once doing that it goes to the 3 skaters and locks again.

That screen said i was on HBOOT 1.46
Click to expand...

I asked you to try it by going in to HBOOT first (Vol-Down+End) to see if trying to launch recovery with Vol-up+End was causing the trouble.

I recall now that the 1.46 and 1.47 bootloaders in fact used a different key combination to boot directly from power-off state into recovery. (Unfortunately, I can't recall what that key combination was)

Please try again, one more time, but try going to recovery only through the HBOOT menu (Vol-Down+End followed by Vol-up after HBOOT comes up)
 
erisuser1 said:
I asked you to try it by going in to HBOOT first (Vol-Down+End) to see if trying to launch recovery with Vol-up+End was causing the trouble.

I recall now that the 1.46 and 1.47 bootloaders in fact used a different key combination to boot directly from power-off state into recovery. (Unfortunately, I can't recall what that key combination was)

Please try again, one more time, but try going to recovery only through the HBOOT menu (Vol-Down+End followed by Vol-up after HBOOT comes up)
Click to expand...

Opps sorry about that. Ok just re-ran the root file part one and booted and then part 2 and booted. When i tried to boot after part 2 i used vol down and end and it is still locked at the skaters screen and has been for about 3 minutes now.
 
vannman17 said:
Opps sorry about that. Ok just re-ran the root file part one and booted and then part 2 and booted. When i tried to boot after part 2 i used vol down and end and it is still locked at the skaters screen and has been for about 3 minutes now.
Click to expand...

Well, I'm stumped.

You could try an alternate phone-only rooting method:

http://androidforums.com/all-things...is-app-apk-no-pcs-no-scripts-needed-easy.html

Or, you could try loading the Leak V3 PB00IMG.ZIP file (See the sticky post "Visual Example...."), and then following it up with either this rooting method or the "one click" method. You can do all of this without ever using a PC.

The only downside to doing the latter is that you would not be able to back up your current ROM. On the positive side of things, it sets up the phone into a known state before you begin rooting - one which many people have reported success with.

eu1
 
erisuser1 said:
JoshH1, for the benefit of others that might read this, could you indicate what worked for you, or what you (think) might have been going wrong?

eu1
Click to expand...
As I said, the first method didn't work out for me. I used the .apk method from jcase. Once I ran the app I rebooted, after that I shut off my phone and held Power + Vol Down. From the HBOOT I selected Recovery and everything worked awesome.
 
I have a weird problem. I transfered my old SD card from my old phone because it had a bunch of music on it. For some reason (I probably did some renaming that I shouldn't have in the past, but I don't remember it), the root directory of the SD is nested within the SD "folder" (which is now named Storage CArd (bad caps exactly as it appears). Well, anyway, I was able to unzip Gscript and see the tools folder and the two batch files but I inadvertantly extracted to \sdcard\sdcard instead of \sdcard (due to the weird directory structure). I found Gscript in the apps and ran it, but didn't see the files. That's when I realized that I didn't have it in the right place. So I deleted the files and started over, making sure that I moved everything to the root directory (\sdcard). However, now the Gscript app doesn't appear in the app listing. The files and the tools folder seem to be the right place but the app iteslf doesn't seem to have been created.

I pulled out the almost unused SD card that came with the Eris and I've mounted it and am willing to start over, since the directory structure should be intact.

Two questions:

Can anyone figure out why the app isn't being created from the SD card that I've replaced?

And, when it comes time to install my new ROM, can I simply switch out the cards and run it from there (I downloaded the ROM to the same SD card that I tried to run Gscript from), or could I end up with some similar problems because of the weird directory structure? I could be on the safe side and download the ROM to the "new card" but I'd rather just run it from the card where I originally downloaded it from.

I know that it's a little confusing so if anyone needs additional info, let me know. Currently, I have the SD card with almost nothing on it in the Eris, but i can put the other one back in.
 
erisuser1 said:
Well, I'm stumped.

You could try an alternate phone-only rooting method:

http://androidforums.com/all-things...is-app-apk-no-pcs-no-scripts-needed-easy.html

Or, you could try loading the Leak V3 PB00IMG.ZIP file (See the sticky post "Visual Example...."), and then following it up with either this rooting method or the "one click" method. You can do all of this without ever using a PC.

The only downside to doing the latter is that you would not be able to back up your current ROM. On the positive side of things, it sets up the phone into a known state before you begin rooting - one which many people have reported success with.

eu1
Click to expand...

Will i be able to do a Nand backup doing the one click method? I would hate to not have that handy.

P.S. Thanks for all your help.
 
teleburst,

I think you are over-complicating things.

No matter what you do to the SD card, no matter what files are on it, the Eris always "mounts" the SD card at "/sdcard". You can't have "the root folder inside another folder", because the definition of "root folder" is the same thing as "where it gets mounted" - which is "/sdcard".

Perhaps Gscript no longer shows up because when you swapped cards there was no longer a "/sdcard/gscript" folder present. But that is easy enough to fix - just uninstall Gscript and reinstall it (once you have figured out what SD card you plan on using).

You can use whatever SD card you want, but the easiest thing to do is just use a clean SD (newly formatted) card, and then start over - all the instructions and examples will line up with what you need to do.

eu1
 
vannman17 said:
Will i be able to do a Nand backup doing the one click method? I would hate to not have that handy.

P.S. Thanks for all your help.
Click to expand...

Yes.

It installs the same Amon_RA recovery boot. You might want to refer to the instructions in this thread on how to do the Nandroid backup, as jcase's thread doesn't provide all the gory details (with pictures) on how to do that.

eu1
 
So, I decided to go through the downloading of the gscript zip file from scratch. Extracted it according to instructions. A couple of weird things: I didn't have to hit the / button as the gscript folder was created directly in the root directory. I checked and the tools folder and the two scripts are there. And yet, once again, no app present in the app list. I used Gesture Search to find the app, which it did. When I hit it, I got an error message which didn't stay up long enough for me to transcribe but asked something about enabling it with something regarding "granting permission". and now, when I redid the Gesture Search, it doesn't show up at all.

Weird, eh?

Can't figure out for the life of me what's going on.
 
teleburst said:
So, I decided to go through the downloading of the gscript zip file from scratch. Extracted it according to instructions. A couple of weird things: I didn't have to hit the / button as the gscript folder was created directly in the root directory. I checked and the tools folder and the two scripts are there. And yet, once again, no app present in the app list. I used Gesture Search to find the app, which it did. When I hit it, I got an error message which didn't stay up long enough for me to transcribe but asked something about enabling it with something regarding "granting permission". and now, when I redid the Gesture Search, it doesn't show up at all.

Weird, eh?

Can't figure out for the life of me what's going on.
Click to expand...

Just back up your SD card to the PC and then reformat it and start over.

[Edit] Re-read your post. Start over - with a newly formatted SD card, and uninstall Gscript and re-install it before you begin downloading anything.
 
I went back to the first SD card, remounted it and deleted the gscript folder and re-extracted the zip file (you're right about it coming up with the root directory). Once again, the gscript folder showed up without having to hit the / button. The folder and files were there, but again, no app in the app listings and nothing to be found with Gesture Search.

Edited to note the reply above. I'll reformat and try again...
 
teleburst said:
I went back to the first SD card, remounted it and deleted the gscript folder and re-extracted the zip file (you're right about it coming up with the root directory). Once again, the gscript folder showed up without having to hit the / button. The folder and files were there, but again, no app in the app listings and nothing to be found with Gesture Search.

Edited to note the reply above. I'll reformat and try again...
Click to expand...

I am pretty sure that the difficulties you are having are conceptual errors, and that your phone is not "behaving differently than everybody else's phone".

There are exactly two things which will create the "gscript" folder:

1 - unzipping the "gscript.zip" file
2 - running Gscript Lite and clicking on Menu -> Add script

#2 will ALWAYS, ALWAYS create that folder at /sdcard/gscript
#1 will ONLY ONLY create that folder at /sdcard/gscript IF you follow the directions and move the "gscript.zip" file to the /sdcard folder before you unpack it. This is exactly the reason that we go to all the trouble of moving the "gscript.zip" file into the /sdcard folder before unzipping it - so that it will unpack all it's contents to /sdcard/gscript

As for your Gscript Lite app:

- I don't know why it would have mysteriously disappeared, but it probably has something to do with you swapping SD cards. Or, it may be that you pressed the "List SD-Card" control in the app - which will fail because you do not have a rooted phone (yet). Nowhere in the instructions did I indicate you should use that App option. So, since the app is still sitting there in memory, every time you restart it, you get a strange error. If you are using a Task Killer, see if you get the same result if you kill Gscript Lite and then restart it. Either that, or just uninstall and re-install it - and stay away from the "List SD-Card" option - I suppose it doesn't work on a non-rooted phone.

eu1
 
Still no app. I was curious this time and clicked on the zip file and found that it already had the folder and two files before I extracted it. Is it getting prematurely unzipped perhaps? Could this be keeping the app itself from being created?

Could just looking at the zip file itself prior to unzipping have caused the glitch?
 
"running Gscript Lite and clicking on Menu -> Add script"

See, that's the problem - I can't get there from here because there's no app to run. The very first time I tried (but didn't have it in the correct place), the app actually showed up. I got the page that shows the executables and when I hit the menu button to add script, no files showed up. That's when I knew that I had screwed up and so, I started again and tried several times. But the app never reappeared in my app listing.

As to the second part, the only thing different from your procedure is that the folder didn't "disappear". It was right there so I didn't have to refresh anything.

As to the List SD-Card control, I don't remember doing anything other than unchecking the box and hitting the menu key.

I have gotten the same results with my newly formatted, clean SD card.

I think that "conceptual errors" is too kind <g>.
 
teleburst said:
Still no app. I was curious this time and clicked on the zip file and found that it already had the folder and two files before I extracted it. Is it getting prematurely unzipped perhaps? Could this be keeping the app itself from being created?

Could just looking at the zip file itself prior to unzipping have caused the glitch?
Click to expand...

Simply put, you are not following the instructions. If you just "click" on a .zip file, you will see a "preview" of what is in the .zip file, just the same way that a "preview" will occur if you browse a .zip file in Windows with Windows Explorer.

You see a preview, but they are not unpacked.

No where did I say to "just click" the .zip file in the instructions, except for when the "gscript.zip" file is in the "cut sash".

Look; you can verify whether or not you have unpacked your files correctly by using ES File manager to just browse around. If you unpacked them correctly, you will see four files, just like it is explained in the 2nd post in this thread. Two of them (the scripts) will be in /sdcard/gscript, and two will be in the /sdcard/gscript/tools folder:

/sdcard/gscript/root_part1.sh
/sdcard/gscript/root_part2.sh
/sdcard/gscript/tools/flash_image
/sdcard/gscript/tools/recovery.img
 
teleburst said:
"running Gscript Lite and clicking on Menu -> Add script"

See, that's the problem - I can't get there from here because there's no app to run.
Click to expand...

Go to Settings -> Applications -> Manage applications

and find Gscript Lite, and then:

1) Force Stop (if that button is lit up)
2) Clear Data
3) Uninstall

... and then go back to the Market and re-install it.
 
You must log in or register to reply here.
Back
Top Bottom