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

so you were at stock 2.1-update1, and woke up this morning with an update that changed you to FRG22D? Was it a single large file?

Ya know what I didn't even check, it was 5:30 AM and my brain wasn't functioning properly, I just clicked install. Honestly I was expecting it to be FRG01B. But, when it rebooted and I checked about phone it said FRG22D.

But, you know for sure that you were on 2.1-update1 before you woke up at 5:30? These seems somewhat likely as I would think Verizon would want one big file to update to 22D if needed...

Absolutely sure, I had manually loaded the 2.1-update1 after flashing back to 2.0.1
 
Ya know what I didn't even check, it was 5:30 AM and my brain wasn't functioning properly, I just clicked install. Honestly I was expecting it to be FRG01B. But, when it rebooted and I checked about phone it said FRG22D.

But, you know for sure that you were on 2.1-update1 before you woke up at 5:30? These seems somewhat likely as I would think Verizon would want one big file to update to 22D if needed...

Absolutely sure, I had manually loaded the 2.1-update1 after flashing back to 2.0.1

wonder if there's a file sitting in your cache still or if it clears it out upon install... *looks at motocache*
 
I was wondering the same thing. I'd like a copy of FRG22D nonrooted full install.

Sent from my Droid using Tapatalk

If it does exist - which I'm guessing it does - I wonder if there's a google link like other OTAs... I know on FRG01B someone over at androidforums.com just simply figured it out based on the previous OTA links. So here's what we have so far (I'm taking out "https://"so it shows the full link in text):

FRG01B - android.clients.google.com/updates/voles/signed-voles-FRG01B-from-ESE81.e48e48ff.zip

FRG22D patch - android.clients.google.com/updates/voles/signed-voles-FRG22D-from-FRG01B.688e3520.zip

So maybe it can be figured out ;)

Hmm... this might be getting a bit off topic for this thread...
 
Well, I tried but I can't figure it out. I think you have to know the whole file name...I hope someone posts it.
As for off topic for this thread, I don't know but if the unrooted full-install FRG01B runs better than patched version, might not the full-install FRG22D be better to root? Or flash back to if you need to return your phone to VZW.!

sent via subspace radio
 
Well, I tried but I can't figure it out. I think you have to know the whole file name...I hope someone posts it.
As for off topic for this thread, I don't know but if the unrooted full-install FRG01B runs better than patched version, might not the full-install FRG22D be better to root? Or flash back to if you need to return your phone to VZW.!

sent via subspace radio
I posted a possible solution in another thread. I had too many open at the time. Lemme dig it up...

Okay, here goes -- and deleting that last one since it was in the wrong thread.

http://androidoverdrive.com/pete/OEM..._SW_UPDATE.sbf

You could always use this, update it to FRG22D, root it, and then make an nandroid backup, save that backup, and always have a "return to 'stock'" backup option. Of course, you'd wipe your phone in the process, but if you made a backup first... More trouble than I want, but hey, it'd work. :)
 
Disable the OTA upgrade notice

Sorry if these questions are a repeat.

Last Sunday I used these excellent instructions and got root access to my FRG01B Droid. (still no problems and still loving it). Today I started getting pop-ups messages about installing a new version (OTA FRG22 I assume). Haven't let it upgrade yet., don't have a reason to now.

1) So how do I stop the upgrade messages from popping up?

2) What happens if I let it the OTA proceed?
 
Let it install. SPRecovery will BLOCK it. In fact, you cannot force FRG22D to install at all. If you keep getting update notices you'll have to install a ROM that will block it, but let's stick with the "let it install so it can be blocked" method. :)
 
Thanks Rich. I've got all those. Actually, what I was referring to is with the OTA files. There are two general types of OTA for any given release. An update OTA (that is intended to update one specific release to another -- like FRG01B to FRG22D), and then a "master OTA" that updates pretty much any release to another (i.e. anything to FRG22D). I have the FRG01B-to-FRG22D OTA, but would like to have a copy of the "master OTA" for FRG22D if one exists. I could make one, but that just wouldn't be the same.
 
Don't know for sure what this all means, but it leads me to think that it had something to do with my original installation of RSDlite 4.6 that 4.7 didn't fix and it was only the total removal of RSD and reinstalling a different RSD download that corrected the problem.

Hmmm, interesting. I used the same RSDLite 4.6 file from the OP and neither 4.6 nor 4.7 would work for me on Windows 7 (after multiple installs and uninstalls) until I moved the sbf file to C:\ and shortened the name.
 
Thanks Rich. I've got all those. Actually, what I was referring to is with the OTA files. There are two general types of OTA for any given release. An update OTA (that is intended to update one specific release to another -- like FRG01B to FRG22D), and then a "master OTA" that updates pretty much any release to another (i.e. anything to FRG22D). I have the FRG01B-to-FRG22D OTA, but would like to have a copy of the "master OTA" for FRG22D if one exists. I could make one, but that just wouldn't be the same.
Someone over on the main FRG22D thread reported getting one of those, actually. HOPEFULLY it'll hit some Droid-community servers soon! :)
 
thanks for the help i appreciate it.
so i get to step 4 and it keeps saying adb not found. i downloaded adb before attempting.
sorrry this response was so slow.
Common pitfall with ADB. The Android SDK is kinda weird (by Windows norms) in that you unzip it in whatever location you want to run it from and then just run it from there (as opposed to "installing it"). Lots of folks put it in c:\android which will then end up placing ADB in c:\android\tools. If you did (or do) yours this way, then you have a few choices for running ADB:

  1. In the command prompt, do a cd c:\android\tools before trying to run ADB.
  2. Instead of just running ADB, run c:\android\tools\ADB.
  3. Add c:\android\tools to your system's PATH environment variable and then you can run ADB from anywhere easily (recommended).
There is a thorough ADB guide on this site somewhere. It has all sorts of goodies in it and is worth checking out.
i checked into a "how to set up ADB/USB drivers on androids" from How To: Set Up ADB/USB Drivers for Android Devices | TheUnlockr and i finaly got the update.zip to work!! you were definetly right, i didnt have the adb. thank you so much for helping me!!
 
Back
Top