BEWARE of downloading the "Rooted Gingerbread"
I managed to screw up my droid x by not knowing what I was doing, while trying to download "rooted gingerbread". I attempted the the 2 part method. This post is about what happened and what not to do!
My droid x running was running froyo rooted by 4Zroot ( loved it!). I had all the usual, droid x bootstrap and titanium back pro for rooted (loved both ). I loved my rooted X and the various apps for the rooted phone.
According to the instruction on droid-life
A) Root my phone (done)
B) download droid 2 bootstrap (done)
1) Wasn't sure if I was suppose to have droid x bootstrap running along with droid 2 bootstrap. First Attempt left droid x bootstrap functional along with droid 2
C) download part 1 & 2 on to my sd card ( this is where things started to go wrong)
1) part 1 downloaded without issue or so it would seem. The message in my notification bar said that download is complete. (that's the last time I saw that from this point on)
2) part 2 attempted to download it multiple times and each time my notification bar stated that download was aborted/incomplete. I deleted whatever parts of part 2 which was downloaded on my card.
3) After many attempts, I download the files on to my mac, drag, and drop part 2 right below part 1 into the download folder of my sd card in my phone.
4) Click on Part 1 ( you know, the one that downloaded allegedly without issue)
5) File won't open. I forgot the error message exactly. The basic message is that the file is corrupted. ( I did't believe it because, I couldn't imagine how)
6) Idea???Maybe, I'm not supposed to have both versions of bootstrap. I uninstall droid x bootstrap and decide to drag and drop Part 1 into my phone like I did Part 2.
7) I click on Part 1 and nothing is happening.
8) Thought?? Maybe neither Part 1 or Part 2 are working. Let's click on part 2 and see if that is getting the same type of error message that I was getting with Part 1.
OMG....Part 2 starts to open and do it's thing. I new I had to stop part 2 because part 1 is supposed to go first.
9) How do I abort?? Pull the battery!
D) ALL HELL BREAKS LOOSE!!!
1) When I replace the battery, First thing I see is red motorola symbol.
2) My phone goes black, then kick into bootloader ( what the heck is that??)
3) Basically my phone appears to be in the equivalence of DOS.
OMG, OMG, OMG....Now I've really done it! Guess what? There is no direct way to get to clockwork, titanium back or anything else. It says at this point it's OK to program. It's official "Little Red Riding Root" is screwed! There are no crumbs for her get out of the woods. The woods keep getting deeper and darker, because now it's not ok to even program( As if I could). Other then the obvious ??? This is now draining my battery even though the phone is plugged into the charger. Now it's not ok to program and it says my battery is low! This is hard to believe because the back of my phone feels like a hot plate.
ROOTIN LITTLE BOYS & GIRLS SHOULD BEWARE! If you attempt the "easy" method 2 to getting the rooted gingerbread and there is any glitches. STOP. Seek professional help. WARNING: DO NOT TRY TO FIGURE IT OUT!
I tried everything. My computer wouldn't even recognize my phone anymore! I looked through various forums and I couldn't find a solution that worked for me. Various possible solutions included reinstalling the software from a pc ( I have a mac). Solutions involved find drives, programs, running said drivers and programs from a CD. I can't tell you the last I used a C.D. on a computer. Unfortunately, I had to go to work and my job relies on my cell phone.
After a day and a half without a phone, I took it to Verizon. I told them that my phone went into bootload 30.04 after trying to install an update with a low battery. Which was kind of true. Fortunately, my Verizon tech support person had seen this error message before. It took about two hours for them the wipe my phone clean of everything, reinstall the software, and voila they updated my phone to gingerbread.
I no longer have root! I did back up my phone using clockwork and titanium back up to sd card. Thing is without root access, I can't get into my back up files. Just so you know that, I'm not a "complete" *****. This rootin gangster has the phone insured which covers rooted phones and I'm due for my upgrade. The whole process just sucked and I lost business because I could not be reached by phone.
Next time (wink,wink), I will immediately go to Verizon see if they can fix it. I didn't think I could bring my phone to Verizon because my phone was rooted. Now that I know, I'm insurance covers rooted phones.... If they can't, I will activate my old blackberry storm 2 and wait for the replacement. Unless, the Droid Bionic comes out first!
Question?? How do I get my root back and keep gingerbread?? Remember who you are talkin too!
- 06-02-2011, 02:56 AM #2
- 20 Posts
why didnt you just sbf it back to 2.2? you sound like an *****. i have the 2.3.3/.595 leak...and today i just installed the 596 leak with no problems. I used the team black hat version thats in 3 files and i chose the deodexed over the odexed. ive had no problems. maybe you should get an iphone...
- 06-02-2011, 06:27 AM #3
- 261 Posts
NO issues here either. SBF'd back to 2.2, installed the two parts and bingo. Easy as pie.Samsung Galaxy S3
- 06-02-2011, 08:11 AM #4
- 23 Posts
Soundlike you had a bad download. I used the part 1 and 2 files with no issues at all. BUT...I have had ROMs download and be corrupt before, which is why I always browse the .zip folder on my computer before trying to flash it. If you can open the .zip and look at the contents on your computer, the .zip is not corrupt.
- 06-02-2011, 08:20 AM #5
Sorry you had a bad experience, but I think you're being a bit melodramatic. Everyone else seems to be doing just fine with this process so far...
- 06-02-2011, 08:32 AM #6
Last edited by davidnc; 06-02-2011 at 08:42 AM.SGSIII : White 32 gb model with 32 gb sdcard
RoM : CleanRom 5.5.1_ jb
Kernel : n/a
- 06-02-2011, 08:50 AM #7MacGyver Wannabe
- 608 Posts
The problem is you used a Mac to download the zip files. You need to use Chrome or Firefox with a Mac or the files won't remain as properly zipped files once downloaded.
The rooted GB is perfectly safe. You simply weren't educated on the process and didn't follow it correctly.
- 06-02-2011, 08:55 AM #8
- 06-02-2011, 09:52 AM #9
That story was entertaning, not only they couldn't manage to read the installation instructions correctly, but it's posted everywhere, to sbf back to froyo and how in the event of such....
before i even start hankering my device, i check to make sure there is software available to get back to factory and how. and all that info is spread across the net on many sites.
- 06-02-2011, 10:14 AM #10
- 140 Posts
I've only used the stock recovery with official update.zip files before. I was afraid the 2 file process was going to wipe my settings and apps. I did a ****load of reading before I attempted it, and everything went fine.
I'm glad Verizon was able to get you back in business. Hopefully a root method you can use comes out soon.
- 06-02-2011, 10:53 AM #11
- 57 Posts
- CyanogenMod 7.1
- 06-02-2011, 11:03 AM #12
All the files I need to sbf are on my computer with the line code. All I have to do is open a terminal window and copy, paste and hit enter.
The VZW tech must have had a sandwich and a half pack of cigarettes and said it took as long as it did, lol.
- 06-02-2011, 11:05 AM #13
- 06-02-2011, 11:49 AM #14
- 06-02-2011, 05:46 PM #15
- 06-02-2011, 07:51 PM #16Android Enthusiast
- 2,105 Posts
- 06-02-2011, 10:39 PM #17
- 145 Posts
- Rooted Gingerbread!
Safari automatically extracts .zip files? ...Really?
Note...The original post was a warning of what might and in my case did go wrong.
I am aware that this went smoothly for many. I was sharing my personal experience of what went wrong, why, what happened, and my immediate solution. I posted this as a newbie primarily for other newbies and to point developers in a direction that might help them further "child proof" their programs/roms.
It's because it appeared soo easy to soo many, that I thought it was a simple process. I thought I understood. When your new, you don't always know when your might have not understood. I was shouting out my warning in all the places that newbies
such as myself might be silently lurking.
My story clearly points out that it was my user error. Others maybe too embarrassed to speak of their folly. There are a lot of opinions in these forums, which is why they exist. Ultimately, I share this story so that others may learn from my mistakes. This was a cautionary tale. I intend to learn from my mistakes, probably make new ones and evolve from my experiences!
I know more now than I did last week. Brace yourselves for when I actually know what I'm doing!![/HL]
- 06-02-2011, 11:48 PM #19
Whoa!!! Quit beating so hard on newbies errors!
Remember I'm new. You are not the worse, some other guy called me an *****. There is a lot of information on these various forums, sometimes just missing a turn can cause a collision. Sometimes I think I got it, but didn't. This was a melodramatic experience for me. I lived to tell the tale.
I would like to say that when someone states from the beginning that they are new and that they made mistakes, the better approach is patience and tolerance in tone when you are obviously trying to be helpful. This will encourage more new comers to post questions before they make a major error.
To be human is to error. I thought the idea of this forum was to share, exchange ideas, learn from, and support each other. I find that humor takes the bite out of most tricky situations. I think mean spirited comments ( not referring to you ) is counter productive in a learning environment.
P.S. You are tough, but I do get that you mean well.[/HL]
- 06-03-2011, 07:28 AM #21
- 496 Posts
- Jelly Belly
Wow, the OP sounds terribly uninformed... I don't even own an X, and I know how to SBF back to stock in case something goes wrong. Always have the way to fix your screwups ready before you screw up.Android: If it ain't broke, you haven't flashed nearly enough stuff yet...
- 06-03-2011, 08:15 AM #22