-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root Universal Eris Root for Dummies!
- Thread starter erisuser1
- Start date
-
- Tags
- htc droid eris
I figured it out... apparently there must have been some conflict with the Astro File Manager and apps backup file I had made. Because I deleted that and the script ran perfectly after that. Odd?
danknerd,
I'm sure eu1 will weigh-in on this as soon as he's on-line, but are you sure that you got the root_part1 done correctly? Part1 sets up things for part2 to work so that it can flash (write) the custom recovery image. I don't exactly know that a "no space to write" message would be what you would received if part1 was not successfully done, but I do suspect this.
Do you see the messages in the root_part2 screen that look just like figure 31? (i.e., right under the "All systems go if /dev/mtd/mtd1 has file mode 777 :" you should see the ls output of the mtd1 (recovery partition) and it should show permissions setting exactly like is shown in the instructions: "crwxrwxrwx" (which equates to "777"). If you are not seeing this, then root_part1 must not have been successful.
I would suggest you go back and carefully re-do things starting from figure 28 where you run the root_part1 script. Pay careful attention to all of erisuser1's instructions, making sure all steps are followed.
Good luck.
edit: just saw your post...glad to see you got things working
I'm glad to hear this - first, because you succeeded, and second, so we don't have to go through a long series of back-and-forth posts
What ROM did you choose, BTW?
Good Luck
eu1
.
eu1,
Was I on the right track? Don't want to steer anyone the wrong way...
Thanks.
Was I on the right track? Don't want to steer anyone the wrong way...
Thanks.
Well, not seeing a mode 777 ("crwxrwxrwx") listing would indicate that the reboot had never taken place, or if it had, that part1 had not been run (or mysteriously failed - I don't know how that could even happen, though).
The out of space message has something to do with the /sqlite_stmt_journals mount point - it is a "tmpfs" filesystem (present in HTC 1.5 and 2.1 releases for the Eris) that is sort of small - it is quite possible that other apps running on the phone could have filled it, so that there was no space left for copying in recovery.img (3.9 Mb) and flash_image (9 kB). That would explain why fooling about with a totally unrelated app would change the behavior of root_part2.
There was a reason that I used /sqlite_stmt_journals instead of /data/local - probably it had something to do with a -noexec mount option, but I really can't recall right now. Perhaps I should just mod the part2 script so that it leaves the recovery image (3.9 MB) on the SD card, although I think this is the first occurrence of this problem.
eu1
Universal means "for every factory HTC phone". That includes the original 2.1 OTA, and the follow-on July 2.1 OTA patch.
Look at the Sticky Thread "One Click". It's even easier than this thread, although the instructions provided don't come with lots of pictures and details. If you use that method, you might want to refer to the 3rd post in this thread on how to make your first Nandroid backup, and how to flash the ROM of your choice.
eu1
.
clvpatterson
Newbie
The process was great!!!! My phone rooted beautifully... BUT now when I try to reload the DROID X keyboard (the black keyboard) - I can't. I intalled the APK for the DROID X, when to type a text and "long press", but I get nothing..
What may be the problem??
Thx
Cynthia
What may be the problem??
Thx
Cynthia
Cynthia,
I think you've got to go into Settings -> Language & keyboard -> Input method and select "Multi-touch keyboard". Did you do this already?
clvpatterson
Newbie
Excellent - thx much!! that did it.. I missed that part..
Cynthia,
Glad this worked for you - and I'm also glad that scary alien is in here watching this thread
Once you are up and running on a ROM, if you have additional troubles or questions about software issues or behaviors of the ROM you are using, you might get more help if you start a new thread - there are a lot of experts on a wide variety of topics who watch this forum, but I'm not sure if any of those folks but scary alien and myself are looking at this thread any longer (except for the new folks, of course).
But I'm glad everything worked out; good luck, and enjoy your "new" phone.
eu1
talespin
Newbie
I downloaded gscript from the above link; estrong claimed it had successfully extracted the file but it didn't show after several refreshes. . . or after several additional attempts to extract. I tried it with androzip and it said the extraction failed. I deleted the file and re-downloaded it with the same results. Do I maybe need more space on my card? is the file corrupted? I had hoped to get further into the process before I hit a wall. Grrrrr. >sigh<
talespin
Newbie
***( 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 )
Any suggestions for when neither works?
Any suggestions for when neither works?
Did you resolve the problem in your prior post?
What happens when you try either button-press sequence, does the phone just boot normally, or something else?
Are you making sure that you are pressing both keys down until the screen lights up (making sure that you pressed the appropriate volume button before the End button)?
eu1
talespin
Newbie
My apologies -- yes, I resolved the earlier problem by downloading it to my pc and unzipping it to the connected phone's sd card.
The boot problem is more stubborn; yes, I've been very careful to press and hold the two buttons through the power up. Usual OS comes up. vol-down + end just results in the phone vibrating to tell me the volume is down and displaying the "shut phone off?" screen. I've powered it down dozens of times. I left it to fully charge. I even took out the battery. Nada. I'm stumped.
The boot problem is more stubborn; yes, I've been very careful to press and hold the two buttons through the power up. Usual OS comes up. vol-down + end just results in the phone vibrating to tell me the volume is down and displaying the "shut phone off?" screen. I've powered it down dozens of times. I left it to fully charge. I even took out the battery. Nada. I'm stumped.
OK gotcha. I am wondering if you also have the 1.46.0000 bootloader.
This statement confuses me - it sounds like you are pressing these buttons when the phone is up and running, rather than with the phone off. Am I misinterpreting that statement?
Well, there are a couple more things you can try. I am not positive the first of these will work, because it seems that HTC fooled around with the functions of different key sequences when they went from 1.46 -> 1.47 -> 1.49 (bootloaders). But, let's give it a try.
- Try powering off the phone, and then starting it by holding down both the Send key and the End key at the same time (press the Send key before the End key). Hold them down until the screen lights up. If you are fortunate, you will be in "FASTBOOT" mode, and on the screen it will say something like
<VOL DOWN> Hboot Mode
press the Vol-Down key to go into "HBOOT" Mode.
(while you are here, please write down the HBOOT version number reported in the second line at the top of the screen)
Now, in this screen you should see a line that says something like
<VOL UP> Recovery
Let's try that and see if it gets you to the recovery menu.
eu1
.
Harmageddon
Lurker
Im not for sure but I think that it was like 710. It started when I enabled profiles and tried to use that. I deleted the app and found one called Overclock Widget and I have it set to 768 and have no problems what so ever. Granted it isnt as detailed as SetCPU but it has a screen off setting and one for on, just not for battery monitor. Maybe it just doesnt like my Eris... lol
On another topic, is the procedure for flashing another ROM (curr using PJT2v2) the same as when I put this one on here. I used the GScript Lite tut to do it. I know that I dont have to rerun GScript just do the wipe and flash. I guess my question is is there anything else that I have to do when flashing a new ROM? Im really new to this but I think that I am getting the hang of it. I finally figured out how to run the DeleteBloatWare.zip that came with the ROM...lol. Also, in your great and humble opinion, what would you recommend for a ROM? There are so many choices and methods I get lost in all the commotion. Any advice would be greatly appreciated. Thanks
Most excellent.
And strange, too - I actually rolled my phone back to the 1.47 bootloader to test this method, and had no similar problems with Vol-Up+End. I wonder what the problem is - more than a few people have had the same troubles.
Happy rooting - and please remember to make Nandroid backups at the very beginning, and often after that!
eu1
.
talespin
Newbie
Um...new problem. I'm at the "flash zip from sd" and it's coming up "E:no zip files found". It's there -- or, it was. I downloaded plainjane from your link above. what now? (and, sorry)
Can I reboot and start over? is that gonna kill the phone? Can I connect it to the computer and have a look at the sd card? Can I power it down and recharge? (it's gonna need it soon). Eeep.
Can I reboot and start over? is that gonna kill the phone? Can I connect it to the computer and have a look at the sd card? Can I power it down and recharge? (it's gonna need it soon). Eeep.
If you continue to have OS crashing or freezing problems, you should strongly suspect the overclocking app as the root cause. I know that in the case of the SetCPU widget, people reported problems using it with various ROMs, but not when they just used the SetCPU app. I have no a priori reason to believe that Overclock Widget exhibits the same troubles - but it is possible. Keep your eyes open.
You should ALWAYS make a Nandroid backup of your current ROM just before you do the "Wipe data/factory reset" step. Let me emphasize that:
[SIZE=+4]ALWAYS![/SIZE]
Well, OK... there is only one reason why you wouldn't do that: if your current ROM is horribly messed up, and you know you will never return to it ever again. But, the usual case is that you've got something set up which works for you pretty well, and you are about to step off of a cliff. That's why the "ALWAYS" emphasis.
I get lost in the commotion too. By no means have I tried them all. Lately I have had on my phone these ROMs:
KaosFroyo V30
TazzFroyoCM V8
xtrSense 4.0.6.1
At the moment, if I had to pick between the two above Froyo ROMs, I would pick Tazz V8. It is just a tiny bit harder to install (you need to flash the new "Gapps" bundle right after you flash the Tazz ROM, but before you boot).
The xtrSense 4.0.6.1 ROM is really nice and smooth without needing to fool with SetCPU - and because it is a Sense-derived ROM, everything just plain works. I'm not sure that you would find it a whole lot different than PJT2, though.
The thing is, what people find objectionable (or fantastic) about a ROM varies widely. For instance, even though the cameras are now working in the (above) Froyo ROMs, I find their focus behavior to be worse than that in stock or dev 2.1 ROMs, and the controls are quite limited, too. And you must overclock them to get snappy behavior out of them. I also find the POP3 mail client app to be worse - because I can't "select all" when it is time to delete lots of email. OTOH, the new Google "Voice Actions" are pretty cool, and the auto-restore of apps and settings in Froyo are pretty cool, Gmail is improved, etc etc etc. But if you want to use Exchange, I'm not sure you can do it on Froyo without buying a paid market app. See what I mean?
One piece of advice I will give you though, which I think is pretty practical: if you want to try a bunch of different ROMs, avoid using A2SD/APPS2SD. Froyo ROMs won't even boot with a partitioned SD card, so flip-flopping between 2.1 and Froyo ROMs is a major hassle if you have your prior (Nandroid backed up) ROMs set up to use A2SD. Royal pain in the butt for little real benefit if you ask me (A2SD, that is). I have a bunch of 2.1 ROMs backed up in Nandroid, and now that I am using Froyo ROMs, I regret that I ever used it.
Anyway, I ramble. Just remember that you have backups in the form of Nandroid backups of prior ROMs, so trying out a new ROMs doesn't mean that you are giving up your old ROM forever - you can go back to it whenever you like if the grass is not greener on the other side of the fence. Just make sure that you occasionally backup your entire SD card to your computer - accidents happen.
eu1
Your phone will charge (slowly) with Amon_RA running. Faster if you turn it off and use the wall charger though. I think it is a very good idea to only flash ROMs with a really good battery charge - that's why I am mentioning it first.
If you already did a "Wipe data/factory reset", your phone will not boot into the regular OS - it's not there any more. Don't panic, though.
You can use the "USB-MS toggle" (with your phone plugged into the computer via the USB cable) to copy files to the SD card with Amon_RA running. (Just like using "Disk Drive Mode" in the OS). If you use this method - that is, download the file to your PC, and then "mount" the phone on the PC (as the D:, E:, F:, or whatever drive), make sure you use the "Safely Remove Hardware" control in the system tray (Or "Eject drive" in Windows 7 from Windows Explorer) before you toggle "USB-MS toggle" off after you have finished copying the file to the SD Card.
I'm not sure why you don't see any zip file in your SD card, but that's mostly because I don't know how you got it there - you didn't provide that detail.
If you downloaded it directly to the phone using the phone's web browser, it needs to be moved to the "/sdcard" folder (it would have been DL'ed to /sdcard/download).
Other explanations are: if you moved it from the PC, you accidentally renamed the file extension (it's not something.zip any longer), you didn't put it in the top-level folder from the PC, or you accidentally unpacked the zip file (some Mac users have reported this).
Does this help?
eu1
.
talespin
Newbie
Okay. I connected to the pc and checked the sd card -- yup, still in the downloads folder. I moved it and proceeded with the next step; its installing now and so far so good. Thank you so much for your patience and prompt, clear responses.
'kay. I've got the plainjane welcome screen and am hoping for smooth seas here on in.
'kay. I've got the plainjane welcome screen and am hoping for smooth seas here on in.