Okie, I'm having a small issue of storage space....or lack thereof. It's important to note that IRL, I am a major packrat of the "I might need that!" sort. So, I'm disinclined to delete things. I see on xda that there is an Apps2SD. Will that help my storage problems? Is there anything special to know about using Apps2SD? Is there a ROM that includes Apps2SD already? Or will I need to install it on its own?
~Amy~
It sounds as though Apps2sd is exactly what you need. There are plenty of ROMs available that have it by default, you will need to partition your sdcard for this to work so backup everything off of your sdcard prior to partitioning as it will erase everything. Take a look at XDA for plenty of ROMs and if you like the stock ROM T2noob has a ROM posted here with apps2sd already caled plain Jane 2.0 I think.
Try booting back into recovery and do another wipe/factory reset along with a wipe dalvik-cache, then reboot.
K so i pulled the battery, booted into recovery and did both wipes. When i rebooted, it loaded the usual skateboard boot screen. It then vibrated 5 times and remained on the boot screen.
This post is the greatest I have ever seen. There is lot of work done on Moto Droid but Eris kinda left alone for a while. I used a leak version to get to 2.1 and then could not get the root to change it. Today finally the curse is broken and I got the Froyo.
Unfortunately, I do not see an MD5 sum listed for that ROM in the developer's thread for this ROM on XDA. These checksums should be posted by the devs so you can make sure you've got a complete, uncorrupted, and proper version of the file in question.
Perhaps someone else that has downloaded this custom ROM could publish their MD5 sum so you could at least compare that? Anyone?
Or, at the very least, you can verify that the file you downloaded matches what you placed on you /sdcard (that helps a little).
Great post my friend. I've been pondering root for a long time now but I wasn't willing to take the chance. With your walk through specifically categorized "For HTC Eris" I was able to root my phone with no problems.
K so i pulled the battery, booted into recovery and did both wipes. When i rebooted, it loaded the usual skateboard boot screen. It then vibrated 5 times and remained on the boot screen.
Unfortunately, I do not see an MD5 sum listed for that ROM in the developer's thread for this ROM on XDA. These checksums should be posted by the devs so you can make sure you've got a complete, uncorrupted, and proper version of the file in question.
Perhaps someone else that has downloaded this custom ROM could publish their MD5 sum so you could at least compare that? Anyone?
Or, at the very least, you can verify that the file you downloaded matches what you placed on you /sdcard (that helps a little).
sa,
I don't think that the "toolbox" executable of the HTC-shipped ROMs supplied a "md5sum" function - so folks that are getting started rooting (i.e., don't already have root) can not run "md5sum" from their phone without installing an app to do that.
There is an alternate way to check that a ROM is at least "intact" - that is, not corrupted or truncated. It does not verify authenticity, however, and it also involves the PC.
That method is to use "jarsigner -verify ROM_name.zip" on the PC ("jarsigner" is included in the JDK - if you set up your PC with the Android SDK, the JDK is required as a prerequisite) It unpacks the zip and compares the SHA1 signatures of every file in the manifest.
This does not verify that it is the same ROM as that published by the author, as the signing keys used by all the "cooks" is the same key, and widely available (not really private any longer) - someone could pick apart a ROM, put some of their own stuff in it, re-sign it with the same keys, and it would pass this test. (The probability of this happening at the download link provided by the ROM author is pretty low, although it would be much easier if someone was "hosting a copy")
I suppose you could do this check on a PC, and if it passes, then look at the length of the file in bytes (on both the PC and the phone); if they are the same, the probability of them being different is pretty darn low. Doing things this way is not as good as performing the MD5 check right on the phone, but it is better than nothing at all.
But, it does indicate that the ROM file will pass the "verification" phase of the ROM install by the Amon_RA recovery boot.
As a practical matter, though, the problems most folks have with "corrupted" ROMs are due to far simpler problems (rather than single-bit errors):
- Their OS "hides" file extensions (Windows) or Automatically unpacks .Zip files (O/S X)
- Their initial download times out, and they are left with a "short" file.
- They copy the file to their SD card via the USB cable, and fail to properly eject/unmount the SD card, so that the file ends up short/corrupted on the SD card, even though it was intact on the PC.
In the most desirable scenario, the dev would publish both the exact file length (bytes) and MD5 signature when they post a download link. Because it is essentially impossible to make a single-byte change to a file to produce the same MD5 signature, publishing the file length is usually regarded as optional - verifying the MD5 signature validates that you have the same file, even if the file length is not stated.
The thing which should be pointed out is that it is not possible to install a corrupted ROM - it won't pass the "verification" check performed before any files are being flashed.
My guess is that folks who experience boot-loop symptoms after installing a ROM have this happen for a couple of reasons:
1) They failed to perform a wipe in Amon_RA (where required) prior to the ROM install, or
2) They used a ROM which expects a partitioned SD card for a2sd, or
3) They used a partitioned SD card with an ext format (either ext2 or ext4) which is not supported by the target ROM, or
4) The ROM developer kitted their ROM so that it was necessary to flash a (full-wipe) base ROM, and then overlay some update flashes to get the correct behavior, and the user failed to add the overlay flashes, or
5) They flashed their ROM with a very low battery - say 50% or less, and the installed file really was corrupted (in NAND memory, but not on the SD card), or
6) They had previously rooted and used A2SD, and have some apps in the ext partition on their SD card which are completely incompatible with the new ROM.
(Note that ROMs which are pre-configured to start adbd up on boot will have a shell available which comes alive about 8-9 seconds into the boot - in these cases it is sometimes possible to observe the exact cause of the boot-loop by using either "logcat" or ddms: the kernel is actually booted, but the looping is occurring in the initial housekeeping stage of the Android boot process. But, this is sort of advanced for a casual user - and, as I said, I want this thread to concentrate on phone-only techniques)
I put the suggestion to "check the MD5 or file length" in my original posts mostly so that folks without SD card readers would not end up wiping their phone and then finding out afterward that they had mangled their ROM .zip file when downloading or transferring it to the phone. (Even that is not a disaster, because they would have the "USB-MS toggle" functionality of Amon_RA, but that was a detail that I touched on only lightly).
eu1
Last edited by erisuser1; August 3rd, 2010 at 01:34 PM.
The Following User Says Thank You to erisuser1 For This Useful Post:
Thank you (yet again! ) for a highly informative and relevant post! I appreciate all of the bonus and related information too.
It also occurred to me at lunch that some of the custom rooted ROMs might also not have the MD5 sum utility in them or their busybox version is not playing "nice" (i.e, varkie is getting "illegal instruction" for some reason). Your point is well taken...(btw, I'm trying to build my first Android app w/help from jcase and a simple MD5 summer is my target idea--lots of stuff to learn...).
I think I've spouted the mantra of "check your MD5 sums" to folks mostly to make sure they're obtaining their files from reputable sources (remember theUnlockr "incident"? (edit: although if theUnlockr had published the MD5 sum, it would not have dissuaded folks from downloading the non-root (2.1 leak) ROM, if anything, it would have made them feel more secure that it was the right file))--i.e., making sure they are getting the file that they expect to.
I will include a link to this post in the MD5 sum thread that I made.
Thanks again!
Last edited by scary alien; August 3rd, 2010 at 02:38 PM.
This is awesome, as I've got the newer bootloader which couldn't previously be rooted. Taking the plunge now... I've followed the first two parts and successfully gotten the blue screens and the "you've got root message".
which folder exactly should we be moving the roms into? the tutorial says the "root" folder.
I'm trying senseable, so I moved the zip into the root of the card after checking the hash, then using es file explorer I tried to move the zip into the /sdcard/root folder, but the file "cannot be copied".
should I leave it in the /sdcard folder (or root of the folder when mounting on pc) or am I doing some really wrong?
This is awesome, as I've got the newer bootloader which couldn't previously be rooted. Taking the plunge now... I've followed the first two parts and successfully gotten the blue screens and the "you've got root message".
which folder exactly should we be moving the roms into? the tutorial says the "root" folder.
I'm trying senseable, so I moved the zip into the root of the card after checking the hash, then using es file explorer I tried to move the zip into the /sdcard/root folder, but the file "cannot be copied".
should I leave it in the /sdcard folder (or root of the folder when mounting on pc) or am I doing some really wrong?
Leave it in /sdcard ; that is the root folder (when viewed using a file manager on the phone)
( Note that if you downloaded the ROM directly to the phone using the phone's browser, you would move it from /sdcard/download to /sdcard in exactly the same manner that we moved the "gscript.zip" file in the example given )
You will know you are doing the right thing because when you pick the (Amon_RA) main menu item "Flash zip from sdcard", your file will be listed.
When using the PC, it will be the E:, F: or similar drive letter.
If you copy the file from the PC using the USB cable, make sure you have correctly dismounted the Eris from the PC by using the "Safely Remove Hardware" control in your (Windows PC) system tray first - before you toggle off the "Disk Drive Mode" on the phone.
eu1
Last edited by erisuser1; August 3rd, 2010 at 04:18 PM.
The Following User Says Thank You to erisuser1 For This Useful Post:
I'm running in a problem at figures 13-17. I'm extracting the gscript.zip file into the gscript/ folder, but when I click "OK" I get a popup that says "counting files size", but the status bar doesn't move. That screen minimizes and i get a popup saying "extract is done". I then click the / button and then click on "SDCARD", but there is no "gscript" folder.
I'm running in a problem at figures 13-17. I'm extracting the gscript.zip file into the gscript/ folder, but when I click "OK" I get a popup that says "counting files size", but the status bar doesn't move. That screen minimizes and i get a popup saying "extract is done". I then click the / button and then click on "SDCARD", but there is no "gscript" folder.
What am I doing wrong?
Beats me.
Because I can't see what you are seeing, I have to guess.
I just did the extract process about 10 times, and I can tell you that not once does anything appear on the screen which says "counting file size". I see something similar to figure 12, where the green progress bar moves (quickly!) across the screen - there are only 4 files after all.
A very small popup briefly appears on the screen (perhaps for 1 second) which says "extract is done" after extraction is completed.
Here is what I would do if I were you.
Using ES file explorer, delete the "gscript.zip" file from /sdcard
Then, download it again using the phone's browser, and repeat the cut-and-paste steps used to move it from /sdcard/download/gscript.zip to /sdcard/gscript.zip.
Before you do the "Extract", long-press on gscript.zip and scroll down and select "Properties". You should see that its' size is listed as
Size: 3.73 MB (3,915,189 bytes)
I don't really know what is happening in your case - it could be that the download was corrupted somehow, or it could be a simple usage mistake on your part.
If you want, you can certainly experiment with ES File Explorer and other zip files to familiarize yourself with how it is supposed to work - grab some (smallish) Zip files and extract them, and then poke around in the folders that are created by the extraction (using ES File Explorer), just to get familiar with how it works. If you are making a simple mistake, you will probably discover it by becoming more familiar with how ES File Explorer behaves.
If you can't get this to work, there is an even easier method of rooting available (but it doesn't come with lots of pictures and instructions):
It's an app that does the work in one click (released about a week or so after I released this method). It is "charity ware" - the developer asks that in lieu of payment, you make a charitable donation.
Good Luck
eu1
The Following User Says Thank You to erisuser1 For This Useful Post:
If I don't want to install a custom ROM am I done after figure 31? Do I even need to boot into recovery or can I just jump into my now-rooted phone? If I simply reboot I'll still be rooted and be able to turn my phone into a wifi hotspot right? (that's the main reason I'm doing it) So could anyone please answer my root question, then point me in the right direction to the best way to tether for rooted users (I'm pretty sure it's a simple app) and perhaps some recommendations of ROMS should I ever want to install one?
erisuser1, thank you so much for this tutorial! I would have never rooted if you hadn't explained it so well.
I liked my Eris before I rooted, now I LOVE it.
If I don't want to install a custom ROM am I done after figure 31? Do I even need to boot into recovery or can I just jump into my now-rooted phone? If I simply reboot I'll still be rooted and be able to turn my phone into a wifi hotspot right? (that's the main reason I'm doing it) So could anyone please answer my root question, then point me in the right direction to the best way to tether for rooted users (I'm pretty sure it's a simple app) and perhaps some recommendations of ROMS should I ever want to install one?
Well, by "Congratulations, you have root" I meant that you have nearly full control over the phone at that point - but nothing has been changed except for the Recovery Boot partition. The main O/S ( boot, system, data, and cache partitions) have been essentially untouched at the completion of Fig. 31.
If you want to keep what you've got, but add root capability to your current HTC ROM, what you want to do is an "update flash".
This proceeds more or less like the set of figures following fig. 31 with one exception: YOU DO NOT PERFORM A WIPE (fig 38) FOR AN "UPDATE" or "OVERLAY" flash.
So, what you do is you download the "engtools3.zip" file from this post over on XDA (thanks Jcase!):
and then flash this (engtools3.zip) file using the Amon_RA main menu item "Flash zip from sdcard"
This installs exactly three things to your phone (in addition to whatever is already there):
/system/app/SuperUser.apk (Super-user App)
/system/bin/su (su executable)
/system/bin/flash_image
That will install a minimum set of root tools for you to begin fooling with your phone.
eu1
PS0 It is absolutely reckless to skip the initial Nandroid backup of your existing ROM.
PS1 With some searching (code.google.com) you should be able to easily find the Wireless Tether app (.apk)
PS2 A lot of dev ROMs install an app called "busybox" into either /system/bin or /system/xbin, and then create symlinks to it for all the different functions that it can perform. This is NOT done by engtools3.zip. You might find that many scripts that get used on root ROMs will not work for you, because they presume that many common tools provided by busybox are "in your PATH".
PS3 You will not be able to overclock with the stock kernel. You need to replace the boot partition to do that.
Last edited by erisuser1; August 3rd, 2010 at 09:47 PM.
The Following User Says Thank You to erisuser1 For This Useful Post:
Finally got it working this morning thanks to EU1! I guess I got a bad download or something.
One question: Once I've flashed the .zip files, can I remove them from my memory card or should I leave them be?
You can delete them if you want...
What I do is move them to a subfolder (called otherstuff) in my download folder so they are out of the way (and out of sight for custom recovery), but I've still got them if I need them. Plus, I've got plenty of space on my /sdcard, so no worries there.
I've read over this thread and a few others several times and am ready to root ... but ... my phone is stock 2.1 OTA.
Should I hold off for now because of the "possible loss of 3G" issue that Trident posted about?
Right now, all I'm looking for is longer battery life and less lag when I'm at work (out in the boonies)
I mainly surf the 'net and text since the phone part of the friggin' phone is a joke! I'm hoping a new ROM will take care of that annoying problem, but I can wait to flash one - if it's suggested.
What say You(s)?
P.S. Just realized that I haven't seen "3G" in the notification bar in days. Is there any way to check on it? I can send and receive texts.
Last edited by Munkyme; August 4th, 2010 at 02:32 PM.
Reason: PS added
I've read over this thread and a few others several times and am ready to root ... but ... my phone is stock 2.1 OTA.
Should I hold off for now because of the "possible loss of 3G" issue that Trident posted about?
The "factory reset" performed by a stock HTC phone alters more than gets changed when you perform a ROM replacement during rooting. Rooting certainly does not touch the non-volatile memory areas of the phone where handset activation data is stored. Anyway, my own opinion is that the "possible loss of 3G" claim is likely to be complete BS - it is simply too hard to believe, as it is reported to occur to nearly every handset maker and model, independent of software version or (proprietary) bootloader.
Quote:
Originally Posted by Munkyme
Right now, all I'm looking for is longer battery life and less lag when I'm at work (out in the boonies)
If you see a signal down around -90 dBm or lower (more negative) where you work "out in the boonies", your battery life is being affected by how much power it is commanded to use by the nearest tower. A new ROM probably won't help as much as Airplane Mode in that case.
Quote:
Originally Posted by Munkyme
P.S. Just realized that I haven't seen "3G" in the notification bar in days. Is there any way to check on it? I can send and receive texts.
3G reception comes and goes in weak signal areas; the best way to test the phone is to take it someplace where there is a good signal and see if it reports "3G".
I want to start off by saying thanks for making this easy. I rooted using this option and then downloaded rom manager after a friend told me about it. I installed clockwork mod and would like to get Amons recovery back. Does anyone know how to do this using this rooting method?
I want to start off by saying thanks for making this easy. I rooted using this option and then downloaded rom manager after a friend told me about it. I installed clockwork mod and would like to get Amons recovery back. Does anyone know how to do this using this rooting method?
donaldb1986,
If you still have all of the files in-place from when you did this before, you should be able to just re-run the root_part1.sh and root_part2.sh scripts in Gscript Lite like you did before.
The root_part1.sh script just re-secures your recovery partition so it can be over-written with Amon_RA's custom recovery by the root_part2.sh script.
After you re-run root_part2.sh, when you boot into recovery, it should take you into Amon_RA's recovery instead of ClockWorkMod's.
Note: all other rules still apply: make sure you have a good charge on your phone, don't flash a new ROM without first making a Nandroid backup, etc. All of erisusers1's instructions are gold and his warnings and notes should always be heeded.
Last edited by scary alien; August 7th, 2010 at 10:37 AM.
Thanks simply cannot describe my grattitude. I just followed it and now I have root.. which I kind of still don't know what to do with but now I can take my phone to metro pcs and get it flashsed to their network. -
I now have options so that's good enough for me.
Hi guys, this is my first post here, I've been reading these forums ever since I got my Eris a few months ago! I followed all of the instructions laid out here, double and triple checked everything, and I am stuck on a boot-loop of the VZW logo and "HTC Quietly Brilliant." I read something about this same exact circumstance earlier in the post, but I couldn't draw any conclusions about how to solve the problem.
Stuff to know:
2.1 OTA + July OTA pre-root
Suave Smash ROM
Used information in this thread to root my device.
Any help would be greatly appreciated, and if you need any more information let me know
Hi guys, this is my first post here, I've been reading these forums ever since I got my Eris a few months ago! I followed all of the instructions laid out here, double and triple checked everything, and I am stuck on a boot-loop of the VZW logo and "HTC Quietly Brilliant." I read something about this same exact circumstance earlier in the post, but I couldn't draw any conclusions about how to solve the problem.
Stuff to know:
2.1 OTA + July OTA pre-root
Suave Smash ROM
Used information in this thread to root my device.
Any help would be greatly appreciated, and if you need any more information let me know
agg009,
Just a few questions:
1. Did you make a Nandroid backup before flashing the new custom ROM?
2. Did you do the wipes before flashing the new custom ROM?
hello, what a totally amazing thread. Yes I have been lurking for months, deciding if and when to take the plunge and root my lil' ol' Eris. I have to say I for the confidence to do so from this thread. I used the "1 click" method and went as smooth as freaking silk. So a huge thanks to the devs as well as all the contributors to this thread. You all rock in my opinion.
Now to figure out how to access a2sd built into PlainjaneT2 v2.0. And yes I partioned and did the ext2 - ext3 thing from recovery, not sure if I missed something or what the deal is. If there is another ROM out there that makes it easier to access, I am game.
Just a huge thanks once again to all of you awesome folks!
Hey all. Im new to the root scene and wanted to get in on the action. I used the method in this thread and had a few hiccups (forgot to move the PJ rom to the sd root folder). I thought I had bricked my phone. I had to reboot and it went to stock so I was able to move the rom to the correct folder. I redid all the steps and now have root. BTW, I started with the 2.1 that came on phone when I bought it. I downloaded the term emu and at the $ prompt I typed su and got # so I know that I am rooted. THANKS FOR THE DUMMY WRITEUP, cause if it wasnt for that I would still be stock and running out of space on my phone. I have a few things that I would like to find out about.
1) Is there any other way to stop the wifi hotspot app besides using ATK? I press stop tether and it restarts a few seconds later.
2) I dont see anything the the A2SD. That is the MAIN reason that I wanted root and now that I am I cant seem to find it.
Other things I would love your input on are good roms to use and what all goes into putting a different one on now that I am rooted. Any (valid, non flamming) responses would be greatly appreciated. Thanks to all, EU1 especially for the remarkable tut.
Harmageddon
Did a little searching and I think I found how to get A2SD working. Sorry for the NOOB post...lol
So I did the partition and installed a new app, checked the figures and then uninstalled and it showed that the app was installed to the internal mem and not SD. Can anyone offer any advise as to what else I need to do to make this work. Thanks in advance.
Last edited by Harmageddon; August 8th, 2010 at 02:28 PM.
I have rooted my Moto Droid and her phone is now ripe for the picking... She will (hopefully) not know that this was ever done, only that new vistas have been opened up.
She hated the upgrade from 1.6 to 2.1, so anything is possible with her. Hopefully she will be grateful for it and not tear into me. I guess I could always ask for permission first.......
I appologize if this is common knowledge but I'm new to the whole root thing and don't have time to read the entire thread right now... (Thanks for this great tutorial, BTW).
Is a wipe required every time you flash a new ROM or do you just flash over the top of the old one? I'd rather not have to set up my phone and re-install all my apps every single time, unless I need to.
I appologize if this is common knowledge but I'm new to the whole root thing and don't have time to read the entire thread right now... (Thanks for this great tutorial, BTW).
Is a wipe required every time you flash a new ROM or do you just flash over the top of the old one? I'd rather not have to set up my phone and re-install all my apps every single time, unless I need to.
In general, yes: it is usually the case that you wipe before installing a new ROM.
There are only two exceptions to this:
1) You are upgrading to a new version of the same ROM, and the dev has explicitly indicated that it is safe to "flash over" or "overlay" the new version of the ROM on top of the old one.
2) You are adding an enhancement or "update" package to a ROM.
If you do a nandroid restore from a prior backup, there is no need to do a wipe, as a wipe is built-in to Nandroid restores.
Sorry; it's a pain to configure a fresh ROM install, but there isn't much of a way around that.
The Following User Says Thank You to erisuser1 For This Useful Post:
my eris got stolen and the insurance sent me one wit hboot 1.59, which from what ive read, was supposedly unrootable. with this method i was able to root. now i just have to find the rom i was using again. i had a normal android 2.1 with superuser. hate that i have to go thru this process over again because i had my phone set up for me perfect, now i gotta go and delete all the stock apps once again.
my eris got stolen and the insurance sent me one wit hboot 1.59, which from what ive read, was supposedly unrootable. with this method i was able to root. now i just have to find the rom i was using again. i had a normal android 2.1 with superuser. hate that i have to go thru this process over again because i had my phone set up for me perfect, now i gotta go and delete all the stock apps once again.
Sorry for your loss.
Some good might come of it though, as it serves to remind people to back up their SD card regularly. If you had that, your hard work would only be an easy root and a Nandroid restore away.
It is a good idea to back up your SD card regularly, not only to guard against loss or theft, but also against media failure or corruption.
my eris got stolen and the insurance sent me one wit hboot 1.59, which from what ive read, was supposedly unrootable. with this method i was able to root. now i just have to find the rom i was using again. i had a normal android 2.1 with superuser. hate that i have to go thru this process over again because i had my phone set up for me perfect, now i gotta go and delete all the stock apps once again.
my eris got stolen and the insurance sent me one wit hboot 1.59, which from what ive read, was supposedly unrootable. with this method i was able to root. now i just have to find the rom i was using again. i had a normal android 2.1 with superuser. hate that i have to go thru this process over again because i had my phone set up for me perfect, now i gotta go and delete all the stock apps once again.
edit: sorry, I just realized I had mis-read you post...its what I get for trying to read and reply from my phone instead of my desktop. Apologies again.
Last edited by scary alien; August 11th, 2010 at 11:13 AM.
I've created a simple app that you can use to calculate an MD5 or an SHA1 checksum directly on your phone.
Ironically, in the course of developing and testing this, I also realized/discovered you can also use Astro File Manager to see a file's MD5 checksum (i.e., long-press on a file and view details).
Anyway, all of eu1's cautions / information about the appropriateness and value of checking a file's MD5 checksum still apply. I just though that those of you have have checked or do check these things might like to check-out this app.
Thanks.
Last edited by scary alien; August 11th, 2010 at 08:43 PM.
Reason: spelling
The Following User Says Thank You to scary alien For This Useful Post:
Just wanted to say thanks for the Universal Eris Root for Dummies.
I've been rooted with the PlainJaneT2V2.0 and overclocking at 768 for a couple of weeks now. Love the options rooting has opened up, especially installing apps to the SD card. The PlainJane ROM could not have been more perfect for this noob.
Thanks again to everyone who's contributed to this thread.
Help a noob, please. Went thru the steps very slow to not miss anything. After running root_part2 i get the congrats you have root message. I turn off phone and try to boot up and it always freezes at the 3 skateboarders screen. I have tried to use the down arrow and end call and then select recovery menu but then get the same lock down at the 3 skateboarders.
Help a noob, please. Went thru the steps very slow to not miss anything. After running root_part2 i get the congrats you have root message. I turn off phone and try to boot up and it always freezes at the 3 skateboarders screen. I have tried to use the down arrow and end call and then select recovery menu but then get the same lock down at the 3 skateboarders.
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%
Last edited by erisuser1; August 11th, 2010 at 10:06 PM.
4Likes
) for a highly informative and relevant post! I appreciate all of the bonus and related information too.
(edit: although if theUnlockr had published the MD5 sum, it would not have dissuaded folks from downloading the non-root (2.1 leak) ROM, if anything, it would have made them feel more secure that it was the right file))--i.e., making sure they are getting the file that they expect to.
-
especially for the remarkable tut.
