rachelen

I'm completely new to the Android system and rooting, so I'm terribly sorry if I've missed something in my research of these forums, but I'm lost and have no idea what's going on with my phone.

I rooted my Eris and tried to flash the GSB 2.5, but it's stuck on the little blue cyanogen (mod) 7 screen and keeps looping. I've wiped the cache and everything. I've now rebooted my phone a few times and restarted the whole process (going into recovery and reflashing rom), but it doesn't seem to be doing anything. I'm not sure what I'm doing wrong and I'm going crazy! please help!

metlcat

How long did you wait when you first restarted the phone after flashing GSB? The initial reboot can take a long time, I think 5 minutes has been the longest for me. Also, did you make sure to flash the gapps package right after GSB before rebooting?

I've never interrupted a ROM's initial startup, so I don't know if you can just restart it and let it go now, but you can always try to flash it again. Wipe data/factory reset, wipe dalvik, flash GSB, flash gapps, then reboot. At that point, give it up to 10 minutes to restart. Also, try to do all of this with your phone plugged it as it can eat up a lot of battery.

rachelen

I must have done something wrong. I downloaded a one-click root from the market and downloaded GSB to the sdcard. I rooted and rebooted right after that. Then I flashed the GSB right away, and it was on the screen I mentioned for over an hour, so I pulled out the battery, restarted and reflashed the rom. It's still stuck on the blue cyanogen screen, looping over and over. did I brick it??

metlcat

Don't worry, you are not bricked.

Did you make a nandroid backup like the directions in the one-click thread said? If so, it might be good to restore that so your phone is working again. Boot into Amon_Ra (where you flashed GSB), wipe data/factory reset, wipe dalvik, then go to backup/restore>nand restore, and select the nandroid backup you made. After it has restored, reboot and your phone should be usable in whatever state it was in when you made the backup. From there, check to see if you have a program called Super User. If you do not see this app, go to the market, and download Android Terminal Emulator. Once installed, open ATE and you'll see a "$". Type "su" without the quotes. If the $ changes to #, then you have root and someone should be able to help you from there.

If you did not make a nandroid backup, then you'll have to wait for someone who knows more about fixing problems with rooting than I do. However, if it turns out you do not have root, I would suggest using this rooting method: Universal Eris Root for Dummies!

rachelen

Thanks for your help! Unfortunately, it appears that I did not make the nandroid backup like I thought. Can anyone provide some help??

scotty85

its possible that you had a bad or incomplete download of GSB. i would either re-download it,or possibly just try another rom for now.

were you using your phone or your pc to download the rom? did you check the md5 sum?

hopefully you used your pc so youll be familiar with this method. since you cant boot into a functioning rom at the moment,you can either remove your sd card from your phone and insert it into the pc with a usb adapter,or boot back into Amons recovery and toggle the usb on. you can then transfer your download via usb cable.

since you have Amon_RA recovery,obviously that part worked. even if something had happened to superuser,i do not think that would keep the rom from loading. we can worry about that once you have a working rom and functional phone again.

try a different rom and let us know what happens. when you get back to a working phone,get scary aliens "track ball optional" recovery working(its good insurance-trackballs are a comon prollem on these lil guys ) and then immediately boot back into recovery and make a nand backup.

tracball optional recovery here:
Amon_RA 1.6.2 Custom Recovery: trackball not required!

__________________
The Delivery Guy
If someone has helped you,please click the THANKS button on that post.
Please post questions so others can benefit from the answers.
follow me on twitter @scotty1223

doogald

First of all, I doubt that it was a bad or incomplete download. If the flash completed, the zip file was surely good and passed signature verification. The odds that a zip file that was incomplete and passed signature verification, installed well enough to reach the initial CM boot screen, are extremely infinitesimal.

The OP says that s/he "wiped Dalvik and everything" but there is a lot of "everything" that must be done for a proper flash. For GSB, these should be the steps that you take:

1. Download and put into the SD card both the GSB zip file and the Google apps zip file
2. Restart in Recovery
3. [optional, but strongly recommended] Nandroid backup
4. Wipe data/factory reset
5. Wipe Dalvik cache
6. Flash the GSB zip file
7. Flash the Google apps zip file
8. Restart the phone

I suspect that step number 4 was skipped in this case; it would certainly explain a stuck initial boot. To rachelen, did you do all of these steps? (Well, I guess you missed the Nandroid backup.)

xx_bishop_xx

^ Sacly.

scotty85

well, i have no idea what infinitesimal means but i do apologize for the mis information. for some reason i was thinking that a signed file would pass the verification even if it were missing bits.

main reason incomplete download popped into my head was this comment:
but if the rom is reflashed multiple times without the correct wipes it will indeed produce the same result.

Last edited by scotty85; April 4th, 2011 at 02:30 PM.