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

Root Rooted GB and phone is getting angry. help?

thanks guys! Im a little irritated now, as my SD card isn't recognized by my comupter so I cant put my gingerbread files on it! How do I fix that? I even reformated it with another computer, and still my computer that I have everything saved from wont recognize the damn card. Its always something...
 
I've never had my sd card not be recognized by my computer, so I don't know how to fix that. I'd suggest to start simple, reboot your computer lol.
 
I've never had my sd card not be recognized by my computer, so I don't know how to fix that. I'd suggest to start simple, reboot your computer lol.


I have restarted, and downloaded special software to try to recognize it. Pretty dumb. Im gonna try a different computer, just a pain to transfer all those files!
 
I'm really starting to think that you'd be better off sbf'ing back to froyo, and starting completely fresh.


That's what I did yesterday. Froyo sux haha. Which route should I use to go back to gingerbread? 1 file and gingerbreak or 3 files? I then will end with 595. Thanks!
 
Did you make sure to unmount your sd card from the phone first? Sometimes if you don't unmount an sd card it will lock it and won't be recognized by another device. Always use the 3 file .588 then move up to the .595.
 
Full, (practically) foolproof instructions to get onto .595 with the updated baseband et al:

If you've already SBF'd, skip step 3 :P

Step by step if you want to get to the newest Gingerbread:

Note: If you are already on stock .340 and you have not deleted any bloatware, not themed, not deodexed, not installed a ROM, and have unfrozen anything you might have frozen before, you can skip step 3. If you've rooted and done anything you think might not be close to stock, I'd SBF just to be safe. Its good to know how to do it anyway.

1. Download z4root (here), Droid 2 Bootstrap (here), the 3 parts of the .588 install (here), and .595 deodexed (here) and put them all onto your SD card (.588 files and .595 should be in a folder, not the root of your SD card)
2. Backup your files and whatnot from your current build however you usually do. I did a TiBU of all of my user apps+data as well as my user dictionary. Also did a backup of my call log using "call log backup and restore"
3. Get to .340 stock via SBF (instructions here) Make sure it is the .340 full SBF. NOT system only. If you get into a bootloop after SBFing, 100% of the time it can be fixed by getting into stock recovery (hold home and power) and doing a factory reset/data wipe.
(3.5) Once you get to stock and boot for the first time, you can skip reauthenticating your phone by just touching all four corners of the screen with the android on it when you boot up in clockwise order, starting with the upper left. This is optional, just saves a few minutes fiddling with settings.
4. Install z4root and root with it. If it doesn't work, reboot your phone and try again.
5. install droid 2 bootstrap. Bootstrap recovery, reboot into recovery, wipe data/cache, and install all 3 parts of .588, sequentially. To install them, you will go through "install zip from sd card" and "choose zip from SD card." You must install all 3 parts before you leave recovery. Wipe data/cache again here. (Yes, you're wiping it a lot when there shouldn't be anything on there, but its the easiest way to avoid bootloops)
6. Install .595 same as you did .588. You don't even need to leave recovery from the previous step.
7. At this point I'd reboot (first boot may take up to 10 minutes), reinstall droid 2 bootstrap, and do a quick backup of the clean GB install. Then I'd start restoring everything I backed up during step 2. (Note: The first time you open Ti backup after installing .595, hit the "problems?" button and reinstall busybox. Otherwise TiBU will not function)

Finally, if you are getting the blue triangle icon and are no longer connected to Verizon, simply open your dialer and dial *22899 to reauthenticate.

Note: You will need to SBF back to .340 before you can take the OTA. OTA won't be rootable for a while though, so I'd stick with .595 for now.

PS. if you follow these instructions, you can't really screw it up. Even if you somehow flash files in the wrong order or something, you will only be an SBF away from fixing it. (Make sure it is the .340 full SBF. If your file says "system only" it is the wrong one and will not work) The only circumstances in which you could break your phone is if your battery dies mid-flash. So have a full (or almost full) battery before you start.
 
SWEET MOTHER OF GOD THIS TEXTING IS STILL ****ED!

Im now on 595 and the texting application is still ****ed. What do I do? How should I go about fixing it? This is annoying as shit to say the least. Can I go through and reinstall the series of GB zips overtop of this or no?

Why not just use Handcent...best sms app out. Stock sms app is not really that good...IMO.
 
The texting problem is BACK! WTF?! Im running the .595 software. I sbf'ed and brought it up to .595, and now randomly the texting problem comes back a week or two after.
What is going on here?!
 
I just dont get it, I sbfed and it seems to work fine again. WTF.
This time I did the two part method from froyo that takes you right to .596. We shall see if this lasts more than a couple of weeks. :D
 
Son of a bitch. Its already screwing up again!! I have switched to swype input and typing manually and son far the spacebar is working.. What can I does to permanently fix this POS?? :(
 
At this point, I think it must be an application issue. I think some app (and it might not be text related) is causing issues on the phone.

Unfortunately those types of issues can be really hard to track down. But I haven't read or heard of anyone else having these types of issues.

EDIT - Here is a keyboard issue and fix that might work for you.
 
At this point, I think it must be an application issue. I think some app (and it might not be text related) is causing issues on the phone.

Unfortunately those types of issues can be really hard to track down. But I haven't read or heard of anyone else having these types of issues.

EDIT - Here is a keyboard issue and fix that might work for you.


That edit u posted fixed the issue for now!! I wonder why this continues to be a problem on very few phones?
 
Back
Top Bottom