11-12-2012 11:42 PM
374 ... 131415
tools
  1. Montclair's Avatar
    Do me a favor--

    Type this:

    Code:
    fastboot devices
    Anything?

    NO GOOD

    Then try this:

    Code:
    fastboot-windows devices
    I GET: 0146B00206010013 fastboot

    If the latter works, try altering the flash command to this:

    Code:
    fastboot-windows flash recovery [nameofrecovery].img
    Success?
    If I "flash" recovery, what do I do when the next update comes out? Can I flash back the stock recovery, so I can get the OTA?

    By the way, the code would look like " fastboot-windows flash recovery recovery-clockwork-touch-6.0.1.0-toro.img " or replace flash with boot?
    09-24-2012 08:16 PM
  2. dmmarck's Avatar
    If I "flash" recovery, what do I do when the next update comes out? Can I flash back the stock recovery, so I can get the OTA?

    By the way, the code would look like " fastboot-windows flash recovery recovery-clockwork-touch-6.0.1.0-toro.img " or replace flash with boot?
    If you don't want to flash the recovery, you're correct--replace flash with boot or ALLOW IT TO REVERT like it did before (by pressing "no" when you get to the promot after reboot system).

    Are you using the latest version of Wug's btw? Or better asked: where did you get the fastboot-windows.exe from?

    EDIT: NM, I presume you got the fastboot-windows.exe from the package in that guide? (I'm not the original author of that, so my knowledge of its exact contents is sparse; see the very last page for an updated guide for unlocking/rooting with Windows ).

    And yes, your code should this:

    Code:
    fastboot-windows boot recovery recovery-clockwork-touch-6.0.1.0-toro.img
    Montclair likes this.
    09-24-2012 08:19 PM
  3. Montclair's Avatar
    If I "flash" recovery, what do I do when the next update comes out? Can I flash back the stock recovery, so I can get the OTA?

    By the way, the code would look like " fastboot-windows flash recovery recovery-clockwork-touch-6.0.1.0-toro.img " or replace flash with boot?
    DUH, I had an extra "recovery" in there. All good now! CWM booted!
    dmmarck likes this.
    09-24-2012 08:21 PM
  4. dmmarck's Avatar
    DUH, I had an extra "recovery" in there. All good now! CWM booted!
    Well you need that recovery in there (as I typed it) to tell fastboot "where" to go, so to speak .

    For future reference, this is what I've been updating:

    [GUIDE] How To Unlock Bootloader and Root Verizon Galaxy Nexus
    Montclair likes this.
    09-24-2012 08:30 PM
  5. Montclair's Avatar
    Well you need that recovery in there (as I typed it) to tell fastboot "where" to go, so to speak .

    For future reference, this is what I've been updating:

    [GUIDE] How To Unlock Bootloader and Root Verizon Galaxy Nexus
    this is the exact command that worked:
    Code:
    fastboot-windows boot recovery-clockwork-touch-6.0.1.0-toro.img
    This did not work:
    Code:
    fastboot-windows boot recovery recovery-clockwork-touch-6.0.1.0-toro.img
    I got fastboot-windows from the original guide, authored by, I believe, Cyber Warrior.

    Updated the binaries in SU. I'm back to rooted. Hey, I almost know what I'm talking about!!

    Do I still need to update SU in Play Store?
    dmmarck likes this.
    09-24-2012 08:43 PM
  6. dmmarck's Avatar
    Doh, I'm a dummy, since it's just booting you don't need that.

    My apologies, it's been a long day. Shows you how often I've used fastboot just to boot stuff

    Sent from my Galaxy Nexus using Android Central Forums
    Montclair likes this.
    09-24-2012 09:11 PM
  7. Zach41's Avatar
    I thought I would post this for anyone wondering if they should go from the leaked OTA to the official release....I was running the leaked OTA with no complaints, but I decided I wanted the official release. So I used dmmarck's Return to Stock/Factory Images (a big THANK YOU to dmmarck once again) to return to ICS and then took the official release. I have been using the official release for a day now and I can't see any difference. I would say it was a complete waste of time except that I am new to rooting and flashing and it has given me some comfort to know that I can return to stock if I want to.

    That being said I am now going to root my device again and flash my first custom rom. I think I am going to try AOKP as my first custom rom and then tryout Theme zipper to start. Wish me luck.
    dmmarck, Montclair and lpt2569 like this.
    09-25-2012 12:33 AM
  8. moracca's Avatar
    When I try to flash the JRO030 from IMM76K image, I am getting an assert failed: apply_patch_check message. I am using clockworkmod recovery, booted, selected zip. Am I missing anything? it doesn't need to be factory reset does it?

    I have redownloaded the image, and retransferred to phone, but still getting the error
    09-25-2012 10:42 PM
  9. dmmarck's Avatar
    When I try to flash the JRO030 from IMM76K image, I am getting an assert failed: apply_patch_check message. I am using clockworkmod recovery, booted, selected zip. Am I missing anything? it doesn't need to be factory reset does it?

    I have redownloaded the image, and retransferred to phone, but still getting the error
    Are you sure you're on IMM76K?

    If it keeps failing, try going back to stock IMM76K first.

    Or, you can flash the images via my Return to Stock guide.
    09-26-2012 10:21 AM
  10. LabRat's Avatar
    When I try to flash the JRO030 from IMM76K image, I am getting an assert failed: apply_patch_check message. I am using clockworkmod recovery, booted, selected zip. Am I missing anything? it doesn't need to be factory reset does it?

    I have redownloaded the image, and retransferred to phone, but still getting the error
    Try loading the IMM76Q update first, then load JRO030.
    09-26-2012 04:09 PM
  11. moracca's Avatar
    yes, I'm definitely on IMM76K. Can you link me to a download of IMM76Q image that I can flash without returning to stock? My phone never got a notification of the IMM76Q OTA update
    09-27-2012 06:55 PM
  12. Beyond Fire's Avatar
    I need a little help as I'm kind of confused of what I need to do. First of all how do I find out if I'm on IMM76K or IMM76Q? I have not updated my phone on any official firmware since I bought the phone in december, I've been running custom ROMS since. Right now I'm running CM10 4.1. Second is updating to the official better any better then just flashing ROMS? I don't really know what I need to do to get this official update...do I need to flash to a stock version of 4.0.4? If so which one 76K or 76Q? Doing so will relock and unroot me, which means I should make everything up correct? Sorry for being a noob, any help is appreciated.
    09-27-2012 07:53 PM
  13. mds54's Avatar
    What happens after October 3rd for those of us that don't have access to wifi? Do we get JB via 4G?
    09-27-2012 10:18 PM
  14. mds54's Avatar
    .... . First of all how do I find out if I'm on IMM76K or IMM76Q?.... .
    Go to: Settings / About Phone / Build Number (at the bottom of the screen).
    09-27-2012 10:23 PM
  15. dmmarck's Avatar
    What happens after October 3rd for those of us that don't have access to wifi? Do we get JB via 4G?
    Hopefully!

    Sent from my Galaxy Nexus using Xparent Cyan Tapatalk 2
    09-28-2012 05:25 PM
  16. DB12088's Avatar
    Dmmarck quick question for you, I got the wife a gnex, it us unlocked and rooted. I flashed twrp and now when I try to get into recovery mode is get the red triangle. How do I rename the recovery image for twrp for it to stick

    Edit: I dl'ed the img file from team win and will flash via adb in the morning

    Edit: Edit: that didn't work any ideas guys, I thanks in advance
    Sent from my Galaxy Nexus using Android Central Forums

    Edit x3: I figured it out she is still on stock so on reboot the recovery img is being overwritten, my bad guys
    10-05-2012 11:24 PM
  17. dmmarck's Avatar
    Dmmarck quick question for you, I got the wife a gnex, it us unlocked and rooted. I flashed twrp and now when I try to get into recovery mode is get the red triangle. How do I rename the recovery image for twrp for it to stick

    Edit: I dl'ed the img file from team win and will flash via adb in the morning

    Edit: Edit: that didn't work any ideas guys, I thanks in advance
    Sent from my Galaxy Nexus using Android Central Forums

    Edit x3: I figured it out she is still on stock so on reboot the recovery img is being overwritten, my bad guys
    Yup, it's that "reboot-from-recovery.p" file that's doing that .
    DB12088 likes this.
    10-06-2012 11:57 AM
  18. sfmcrfuller's Avatar
    I updated to jellybean and it was working fine, but then I accidentally reverted back to 4.0.2 by recovering into it, and now it won't let me re-install the 4.0.4 patch or the jellybean patch
    10-15-2012 12:00 AM
  19. dmmarck's Avatar
    I updated to jellybean and it was working fine, but then I accidentally reverted back to 4.0.2 by recovering into it, and now it won't let me re-install the 4.0.4 patch or the jellybean patch
    What do you mean by "recovering" into it? You mean by restoring an old backup?
    10-15-2012 05:32 AM
  20. sfmcrfuller's Avatar
    Yes, I restored through clockworkmod and it reset it back to 4.0.2.
    10-15-2012 08:43 AM
  21. dmmarck's Avatar
    Yes, I restored through clockworkmod and it reset it back to 4.0.2.
    That's probably because you restored an older backup or used an old ROM.
    10-15-2012 10:00 AM
  22. sfmcrfuller's Avatar
    What should I do to get back to jellybean?
    10-15-2012 11:03 AM
  23. dmmarck's Avatar
    What should I do to get back to jellybean?
    You could try a restore with factory images. Or you could flash a JB rom.

    Dropped by Felix from 24 Miles above the Earth
    10-15-2012 11:19 AM
  24. TexasNexus1's Avatar
    11-12-2012 11:42 PM
374 ... 131415
LINK TO POST COPIED TO CLIPBOARD