How I upgraded from the original FRG22 leak to official FRG22D - stock, rooted

Discussion in 'Android Hacks and Help' started by MotoCache1, Aug 30, 2010.

  1. MotoCache1
    Offline

    MotoCache1 Chief Droid Scientist

    Joined:
    Jun 30, 2010
    Messages:
    530
    Likes Received:
    1
    Trophy Points:
    0
    I've had a couple questions on this, so I figured rather than answering it privately, repeatedly I'd just make a post. This is not going to be one of my huge treatises - just a quick bullet list and you'll have to search if you don't know how to do any of the things in any of the bullets.

    Chance are that most folks will find it simpler to just install metiCkOne's package from here which would probably achieve a similar outcome. The below is for those that kind of like to roll their own starting with files directly from Momma Motorola (or Google or whoever).

    On my phone that I actually use (i.e. not my DEV phone) I originally started with a new in box (ESE81 - Android 2.1) phone, used ESE81_SPRecovery to put on SPRecovery, and then flashed the original FRG22 leak (not the more recent FRG22D leak). That leak was pre-rooted. Subsequently I upgraded to one of ChevyNo1's overclocking kernels.

    Once the official FRG22D OTA came out I wanted to upgrade so that the Market would show correctly and so I'd be running basically a virgin build -- but rooted of course.

    To do it the way I did it you'll need:

    1. ADB and appropriate drivers installed
    2. The FRG01B "master OTA"
    3. The FRG01B to FRG22D OTA
    4. Just the .zip file from my "root any Droid 1" procedure (if you do it right - or the whole procedure if you don't).
    5. The .zip file for whatever kernel you want to run if you don't want to stick with the stock kernel.
    This all assumes that you're running a rooted phone that has a custom recovery on it. Remember, I was already running a FroYo build -- just an older one than I was upgrading to, so if you're coming from a 2.1 build, your experience could vary (heck, it could vary anyway).

    Note: Do a full Nandroid backup (not simple) just in case things turn out crummy. It's cheap insurance.

    Also: I did not do a factory reset or clear cache or anything else. The result appears to be flawless. No boot issues, all my apps are still there - they all still have their same settings, etc. The only extra step I had to do was go into the settings for the Market and clear data (for that app only) to get Adobe Flash to show up in the Market.
    On the one hand, I was going from FRG22 to FRG22D, so you might expect this. On the other hand, I went straight from ESE81 to FRG22 without clearing data or cache either. Maybe just lucky.

    In the steps below where I "adb push" files to the phone, I always "adb shell" in afterward and make sure the right file is there (look at the size). Also make sure that you're seeing everything on the SD card. If you don't see anything on the SD card or only see the one file you just pushed, you failed to mount /sdcard in recovery. Do "mount /sdcard" in recovery and re-push the file. You only need to do this once -- it will stay mounted for the duration.

    Here's what I did:

    1. Unless your phone is already in recovery, do "adb reboot recovery" to get it there.
    2. Mount /sdcard in recovery.
    3. "adb push" the FRG01B master OTA to /sdcard/update.zip. This OTA is meant to write over top of just about any prior version of Android -- including the original FRG22 leak. Verify the right file is there in adb shell.
    4. Install the update.zip. Afterward stay right where you are in SPRecovery.
    5. "adb push" the FRG01B to FRG22D OTA to /sdcard/update.zip. Verify the right file is there in adb shell.
    6. Install the update.zip (you should just be able to run that same menu choice again without ever leaving the menu).
    7. "adb push" my .zip file from "what you need" #4 above to /sdcard/update.zip. Verify the right file is there in adb shell.
    8. Install update.zip again.
    9. If you're going to install a different kernel, repeat steps #7 and #8 using the .zip file for your kernel.
    10. Reboot the phone.
    As long as you don't reboot before you do step #8 your custom recovery should still be intact. If you messed up and rebooted prior to #8, chances are that Flash Recovery Service put your recovery back to stock and now you'll need to flash the SBF from my other topic in order to get SPRecovery back.

    In hindsight this topic will possibly cause more problems than it solves for most people. I could be wrong, but I think that most folks that can follow the above without help probably already did it and those that need this procedure may not know how to do the steps with the minimal detail provided. If that prediction turns out to be true for you, just ignore this thread and perhaps go with metiCkOne's package.

    Geez, that still turned out to be a huge post. I just can't write short procedures I guess.
    Last edited: Aug 30, 2010
  2. pc747
    Online

    pc747 DF Administrator Staff Member Rescue Squad

    Joined:
    Dec 23, 2009
    Messages:
    17,552
    Likes Received:
    1,071
    Trophy Points:
    113
    good write up.
  3. SDraconis
    Offline

    SDraconis New Member

    Joined:
    Sep 2, 2010
    Messages:
    25
    Likes Received:
    0
    Trophy Points:
    0
    Great guide. I just used this to upgrade from FRG10B.

    Just as a note, Step #4 failed for me due to a build number error as I expected it would being as I had already installed that exact full update. Apart from that, everything worked beautifully. I am now on FRG22D with root access and Clockwork recovery still intact.

    One small thing to note: When I booted in I still had the system update notification on my screen as I had received it prior to rebooting into recovery. I just hit "Install Later" and it hasn't bugged me again. About phone screen says my system is up to date.
    Last edited: Sep 2, 2010
  4. eggsped
    Offline

    eggsped New Member

    Joined:
    Sep 2, 2010
    Messages:
    91
    Likes Received:
    0
    Trophy Points:
    0
    OK you knew the newb questions were coming so here goes...

    I'm able to follow through the guide but am having problems in clockwork recovery, I cannot access any files via adb. I see them when the phone is in standard mode but not recovery. I figured I'd try to install them directly from clockwork recovery and the installation fails. Is this a clockwork recovery issue or am I missing something?

    Thanks

    switched to sprecovery and still no go. I can't access any files on the sdcard via adb, I see directories but no files are visible when I ls. (I was never into Linux but spent a lot of time on Unix in college so I'm a little rusty)
    Last edited: Sep 2, 2010
  5. MotoCache1
    Offline

    MotoCache1 Chief Droid Scientist

    Joined:
    Jun 30, 2010
    Messages:
    530
    Likes Received:
    1
    Trophy Points:
    0
    Did you do Step #2?
  6. eggsped
    Offline

    eggsped New Member

    Joined:
    Sep 2, 2010
    Messages:
    91
    Likes Received:
    0
    Trophy Points:
    0
    I think I got it now... I was trying to "adb push" while in "adb shell" a quick read here helped immensely. I'm in the process of installing the FRG01B update now. Hopefully I'll get this right. I mainly root to have the ability to back up all apps and delete bloatware, otherwise I like to keep it stock.

    Thanks for sharing this method as it's exactly what I want.
  7. eggsped
    Offline

    eggsped New Member

    Joined:
    Sep 2, 2010
    Messages:
    91
    Likes Received:
    0
    Trophy Points:
    0
    OK halfway there...

    When I try to install the FRG01B to FRG22D update I get the following error message...

    "file_getprop: failed to stat "/system/build.prop": No such file or directory
    E:Error in /sdcard/update.zip (status 7)
    Installation aborted"

    Any ideas?

    edit:

    I had to unmount the sdcard to get the install to take.

    All is golden now!

    Thanks a million!!!
    Last edited: Sep 2, 2010
  8. log
    Offline

    log New Member

    Joined:
    Aug 26, 2010
    Messages:
    51
    Likes Received:
    0
    Trophy Points:
    0
    Thanks for this alternate method Motocache. I had another question, maybe you can help. I'm looking to upgrade from FRG01B already rooted to FRG22D. As you might remember I was planning just trying the OTA upgrade before flashing sprecovery (using the root any version instructions, and now even these instructions)

    After lots of research and thought, it seems the best course of action is to take a full nandroid backup first of my current system since it's running absolutely great right now and want to be able to revert back to this version if something goes wrong.

    Do you think I could have success with this method?

    1) Flash sprecovery using ROM Manager (FRS is already disabled per your previous instructions)
    2) Take full nandroid backup
    3) Using FRG01B->FRG22D signed zip, unzip, update updater-script file per below, re-zip
    Code:
    ** Comment out lines:
    246 (check boot image)
    732-741 (patch boot image, install FRS)
     ** add after line 744 (recursive permission)
    set_perm(0, 0, 6755, "/system/bin/su");
    4) Apply this modified update.zip using sprecovery

    I though it this would work but what threw me off is your "fixsuperm" script included in your root any version updater-script. Should I also be adding this script to be executed as well?
  9. MotoCache1
    Offline

    MotoCache1 Chief Droid Scientist

    Joined:
    Jun 30, 2010
    Messages:
    530
    Likes Received:
    1
    Trophy Points:
    0
    You're welcome. I bet you didn't know you had your own commercial:

    Your handle made me remember that from Ren and Stimpy for some reason.

    Anyway, let's see...

    Good plan so far.

    Not the way I'd do it, but it would probably work OK...

    I'm liking where you're headed...

    Excellent -- good attention to detail.

    I'd also take out 756 since the file won't be there to set permissions on. If you didn't, it would be fine because there is no "assert" around it. If there is an assert around the call, then the whole thing will die right there if that step fails.

    Yep.

    Well, that's a cleanup thing if the current version of Superuser.apk that you're running is old and might have incompatible data in the database/directory for Superuser. The original developer is no longer even putting it in his package because many phones have trouble with it. Our phone seems to be fine calling an external shell script in SPRecovery. I'd say keep it or kill it -- it probably won't matter.

    Good work! Let me know how it goes.
  10. log
    Offline

    log New Member

    Joined:
    Aug 26, 2010
    Messages:
    51
    Likes Received:
    0
    Trophy Points:
    0
    Per you suggestions, updated it and everything worked great. Thanks for reviewing and your advice!

    Here is the final version of changes to updater-script that I performed that was successful.

    Code:
    * Comment out line 740-741 (install FRS)
    * Add after line 744 (fixes su permission)
    set_perm(0, 0, 6755, "/system/bin/su");
    Last edited: Sep 4, 2010
  11. yorT
    Offline

    yorT New Member

    Joined:
    May 11, 2010
    Messages:
    50
    Likes Received:
    0
    Trophy Points:
    0
    Awesome! Thanks Moto. Everything worked out great. I came from FRG01B by Pete rooted and now I am running FRG022D rooted. Everything went good and I'm currently downloading Flash 10.1 from the market. On a side note, I was sure how to Verify the right file is there in adb shell. It's all good I just managed to look at the size of the file that was pushed and made sure it matched the one on my computer. Thanks again!
  12. ralphtrent
    Offline

    ralphtrent New Member

    Joined:
    Mar 1, 2010
    Messages:
    39
    Likes Received:
    0
    Trophy Points:
    0
    if I am already running the 2.2 OTA, can skip that push and just push the 2.2 to frg22d? I just received the update this morning but have not installed it yet.

    Thanks
  13. ralphtrent
    Offline

    ralphtrent New Member

    Joined:
    Mar 1, 2010
    Messages:
    39
    Likes Received:
    0
    Trophy Points:
    0
    I get a similar error but umounted does not help. My error is
    assert failed: !less_than_int(1279140904, getprop("ro.build.date.utc"))

    OK that error was due to the 2.2 ota trying to be installed, I was already on that. When i try to install the 2.2 to frg22d error, I get this error:
    assert failed: apply_patch_check("/system/lib/modules/tiwlan_drv.ko","[really long string]","[really long string]")

    Could this be because the frg22d ota was sent to my phone this morning but not installed?

    Thanks,
    Ralph
    Last edited: Sep 5, 2010
  14. banderbe
    Offline

    banderbe New Member

    Joined:
    Feb 28, 2010
    Messages:
    148
    Likes Received:
    0
    Trophy Points:
    0
    Wow, seriously?

    I just downloaded the deodexed copy from MyDroidWorld, told ROM Manager I wanted to update from my SD card, pointed it to the zip, and boom.

    Done.
  15. ralphtrent
    Offline

    ralphtrent New Member

    Joined:
    Mar 1, 2010
    Messages:
    39
    Likes Received:
    0
    Trophy Points:
    0
    I believe that file is the one that is 76+ meg, From what OS did you come from? Can you repost the link?
  16. drelbar
    Offline

    drelbar New Member

    Joined:
    Sep 6, 2010
    Messages:
    1
    Likes Received:
    0
    Trophy Points:
    0
    Thanks for the instructions and the files. I had a Droid with the leaked FRG22 rooted with Easy Root but I needed another step to get FRG01B to install. Maybe this might help someone else.

    Step 4 (install FRG01B) failed with a message like "assert failed... getprop("ro.build.date.utc")".

    I found a post by DarkDvr at xdadevelopers about this build date issue
    at [ FIXED! ] Can't flash FRF91, throws "assert failed... getprop("ro.build.date.utc")" - xda-developers. His fix was to use
    Rom Manager to install an older version of Clockwork Recovery (v2.0.1.3) before installing the Rom.

    I also had to use the menu option in Easy Root to "Force Re-root", since Easy Root said my phone was rooted but it really wasn't anymore (not sure when it unrooted...)

    After that, I used Rom Manager "All ClockworkMod Recoveries" to install 2.0.1.3.

    I was then able to follow MotoCache1's instructions, install FRG01B, and do the rest of the steps to get to FRG22D with his zip file installed also.

    I then used Rom Manager "Flash ClockworkMod Recovery" option to go back to the latest version of ClockworkMod Recovery.

    Now everything seems to be OK - FRG22D and root.

    Thanks again.
  17. MotoCache1
    Offline

    MotoCache1 Chief Droid Scientist

    Joined:
    Jun 30, 2010
    Messages:
    530
    Likes Received:
    1
    Trophy Points:
    0
    That's quite lovely if you want to run an unsigned ROM prepared by someone else - but that's not what this topic is about.
  18. MotoCache1
    Offline

    MotoCache1 Chief Droid Scientist

    Joined:
    Jun 30, 2010
    Messages:
    530
    Likes Received:
    1
    Trophy Points:
    0
    Actually that error is just saying that your tiwlan_drv.ko file isn't the one that was expected. I know some (many, most?) of the update.zip files for the custom kernels will replace some of the wifi (tiwlan) files. If you went with the "master OTA" FRG22D (don't have a link right off but someone here posted it), it replaces that file with stock when it installs. Then you could redo your custom kernel afterward.
  19. ralphtrent
    Offline

    ralphtrent New Member

    Joined:
    Mar 1, 2010
    Messages:
    39
    Likes Received:
    0
    Trophy Points:
    0
    Moto, thanks for the feedback.

    Are you saying that since I replaced my kernal (Which I did with a chevy), that is whats causing this, but if I install the ota'd frg22d that should work? Isnt that the file you link to in this post or is that something else?

    The funny thing is I am no longer being asked to update and my "about phone" still says frg10b. All I did was let my 2 year old play with my phone, next thing i know he's in the recovery menu (I have a widget that will reboot the phone into recovery) and now I am not longer being asked. Not sure what happened there. I can go to phone/system updates and it says I am up to date. i do not get it.
  20. ralphtrent
    Offline

    ralphtrent New Member

    Joined:
    Mar 1, 2010
    Messages:
    39
    Likes Received:
    0
    Trophy Points:
    0
Search tags for this page
failed to stat /system/build.prop : no such file or director
,
failed to stat /system/build.prop:no
,

file getprop failed to stat /system/build.prop

,

file getprop failed to stat /system/build.prop no such file

,
file getprop: failed to stat /sdcard/kernal.pro
,
file getprop: failed to stat /system/build.prop : no sch fil
,
file-getprop failed to stat kernel.prop no such file to
,
how to fix file getprop:failed to stat
,
razr i cwm file getprop failed to stat /system/build.prop
,
system/build.prop no such file or directory