What's new
DroidForums.net | Android Forum & News

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

[HACKS] Root Droid 1 - regardless of OS version

Just used this on my Ubuntu box. Easiest thing ever. Windows users that are frustrated might want ot try Ubuntu as a live CD, there's no timing issues. You run the sbf_flash, it does its thing, and you have Psycho's recovery.
 
I've downloaded everything, made a list of all my apps, installed RSDLite, I've read the instructions ten times. I'm all ready ... except for one question ...

At what point in the instructions do I get a chance to run Titanium Backup? That's what has me confused. I need to have root access to run Titanium, but in getting root access I will wipe the things that I need to back up in the first place ...

Right? Help?
This is my question too. If I should ever have to return my phone, how do I get it back to stock without a backup?

Inside ROM Manager are stock images, without Superuser.apk. Flash that, you're good to go.
 
This is my question too. If I should ever have to return my phone, how do I get it back to stock without a backup?

I'm not talking about getting back to stock. I can assure you the instructions for doing that are earlier in this thread.

What I want to know is when to backup my apps, so that I can restore them AFTER I have root.

And I can't restore apps if I haven't backed them up.

And so I ask at what point I should run Titanium?
This SBF DOES NOT DO ANYTHING EXCEPT replace your recovery image with SPRecovery and install the superuser.apk and busybox.

Sorry for the caps earlier. I had a cat on my lap and was distracted, didn't realize I had the caps lock.

As such, you don't need to replace your apps. You can runn Ti Backup immediately after doing this so that when you flash a custom ROM you'll have a way to put your apps back PDQ.
 
Ok I have run RSD lite with the correct file on my FRG22D D1 and my results only say "In Process" and my phone has been booted up for about 10 min now. I have been waiting for it to display pass. When I reboot into recovery the stock recovery is there and not sp recovery. I have tried to read through the thread but I am not about to read 50 pages. If someone has a quick solution please help me out.
Thanks!
 
Ok I have run RSD lite with the correct file on my FRG22D D1 and my results only say "In Process" and my phone has been booted up for about 10 min now. I have been waiting for it to display pass. When I reboot into recovery the stock recovery is there and not sp recovery. I have tried to read through the thread but I am not about to read 50 pages. If someone has a quick solution please help me out.
Thanks!

Sounds like you will need to re-flash the sbf file using RSDLite. Re-read 9 and 10 in the OP under Detailed Procedure. This should help.
 
Rooting issues

Non-rooted Droid 1 with stock FRG01B OTA ROM. I have have a rooted for for a while now, made the FRG01B and FRG22D ROM upgrades, and I am currently trying out some low voltage O/C kernels. The wife needed the Hot Spot enabled, so hey no problem, I'm pretty comfortable with the hardware now... that's where I first went wrong. 2.0.1 was around for a while, and there was plenty of documentation around to root it, with the latest two back to back updates, well that's a different story. So I started with the steps included in this thread... being a network engineer, I know enough that sometimes you have to RTFM, so I followed the steps to the letter. Everything goes picture perfect. I flashed it with RSD on Vista, caught the FSR before it tried to reflash after the reboot, RSD showed PASS, and the phone came up in recovery, loaded update.zip and reloaded...

That's when I got the boot loop... pulled the battery x3, still looping. Put it into recovery, and mounted USB and pushed P3Droid's latest stock rooted Froyo ROM, and rebooted.

Well the phone booted up this time, but immediately popped up a force close message on com.android.vendor which I closed. It then asked for the google credentials and started populating contacts, which I was not expecting to happen. I checked, and text messages were gone, but the POP mail account data was still there. I also noticed some menu options were missing most notably the Silent and Airplane modes on pressing the power button.

I thought maybe it was a radio issue so I verified the C_01.43.01P baseband was installed. I went ahead and did a *228 just to be sure the phone was activated with Verizon. I also noticed the phone was a little laggy.

I rebooted into recovery, wiped cache and reinstalled the P3Droid ROM. No change. At the time, I just figured the wife would have to live with the Market error, it was getting late, and I had to visit a customer in the morning. I made and completed a test call from this phone to mine.

Mid day today, I get a text. "My phone is going straight to voicemail". So I spent this evening searching the forums for the Market app error. I bounced every setting item off of my working Droid. At this time, I decided to make it look eactly like my Droid, so I loaded up ClockworkROMmod in between force close messages, and flashed with the clockwork recovery ROM and started with testing Pete's stock rooted ROMS FRG01B and FRG22D, wiped cache.. same problem.

The fix: I finally resorted to wiping cache one last time, performed a factory reset in Clockwork, and installed Pete's FRG22D stock rooted ROM. The phone just finished downloading the apps from Market, synced contacts and calendars and it rings again.

Root of the problem: there must be a setting in a configuration file somewhere in FRG01B that doesn't get cleared out during the FRG22B upgrade process, and it is causing a conflict. The only non-stock app that was installed on this phone was Trapster, so I doubt it was a Market issue.
 
Last edited:
Root of the problem: there must be a setting in a configuration file somewhere in FRG01B that doesn't get cleared out during the FRG22B upgrade process, and it is causing a conflict. The only non-stock app that was installed on this phone was Trapster, so I doubt it was a Market issue.
Great writeup rogers-ranch. First, hopefully the file you loaded was FRG22D, not FRG22B. There was such a thing as FRG22B, but I don't think most folks have access to it (or would want it). Also you said FRG22D at the outset of your post so I assume the "B" is just a typo. Was your FRG22D the OTA one? Was it the FRG01B-to-FRG22D, or the "master OTA", or someone else's package?

I agree with you about the wiping though. The whole "when to wipe and not" thing is kinda haphazard. I think a lot of it depends on the "history" of the phone (what ROMS have been run in the past, etc.). Generally you shouldn't need to do any sort of "clearing" with the OTA updates (or they'd put the "clear" in the package), but I had to clear the Market data to get it to find Flash, so obviously it's not perfect.

Good work getting it fixed, and even better work realizing that there's nothing in the rooting packages that has anything to do with it and it's just one of those things you've got to work through.
 
Thanks!

thank you so much for this article. i have been interested in rooting my droid for quite some time, but every time I Google'd it, I found a different way to do it so I was hesitant. your article was easy to read and understand and now I am sitting here with a rooted droid and a very happy man!
 
Back
Top