Recent content by ohcalcutta

  1. O

    Android 7.0 "I Got my OTA" Thread

    I got a replacement 6P from Google on 9/15 and enrolled it in the beta hoping to have Nougat pushed to my phone immediately, as it did with my old 6P when I enrolled. Been waiting two days and still have not received the update. I did get the update above "preparing my phone for Nougat." No...
  2. O

    [HOW-TO] TiBu The Easy Way!

    So I had to flash the stock image for 4.1.1 (wiping everything from my sd card in the process). I do have my TitaniumBackup folder backed up to my desktop, but I forgot to copy it back into sd card after flashing the stock image. You can probably guess what I'm going to say next but.. I went...
  3. O

    Verizon Galaxy Nexus: Any way to force 4.2.2 update?

    Re: Anyway to force 4.2.2 update? It was a status 7 error. I actually went back and temporarily unrooted, got the OTA update to pop up again and got the same deal. Untrusted packaged -> install anyway -> status 7 error.
  4. O

    Status 7 Error when flashing any ROM

    I didn't use a toolkit. I unlocked in fastboot and flashed the su zip file in CWM to gain root. Anyway, I'm still getting a status 7 when the update that came OTA attempts to install so I guess I'm going to have to wipe and go back to square one.
  5. O

    Verizon Galaxy Nexus: Any way to force 4.2.2 update?

    Re: Anyway to force 4.2.2 update? I'm rooted and unlocked on stock 4.1.1. Got the 4.2.2 update and after installing, ClockworkMod asked if I wanted if I wanted to install untrusted package. I selected yes then got an error after it attempted to install. Anyone else seen this issue or have any...
  6. O

    Finally caught up! 4.2.2 (JDQ39)

    I think that's going to be my only option, unfortunately. Was hoping to do this without wiping my phone though. Will probably just wait for OTA.
  7. O

    Finally caught up! 4.2.2 (JDQ39)

    The only thing I've done is unlock the bootloader and root the phone. Have not changed anything else.
  8. O

    Status 7 Error when flashing any ROM

    Hey, I'm getting a status 7 when I attempt to flash the JDQ39 4.2.2 stock rom over JRO03O 4.1. I'm unlocked and rooted, have the latest version of CWM and it is definitely the right file. Downloaded the file straight from droid-life. Any other suggestions?
  9. O

    Finally caught up! 4.2.2 (JDQ39)

    That's what I thought. So if I'm just pulling the update on to the phone and flashing in CWM, the version of adb shouldn't have any bearing on the status 7 I'm getting when I attempt to flash, right? Oh well, guess I'm just waiting for OTA since this won't install over stock 4.1.1 for me for...
  10. O

    Finally caught up! 4.2.2 (JDQ39)

    Thanks. Does this get installed to my phone in any way though? I'm not seeing how that would be what caused the status 7. All I did was download the update, transfer it to my phone and attempt to flash the zip in CWM.
  11. O

    Finally caught up! 4.2.2 (JDQ39)

    Apparently the status 7 I'm getting may have something to do with my version of adb. I'm running 1.0.29, the most current appears to be 1.0.31. Is there an adb guide somewhere? Trying to figure out how to install 1.0.31..
  12. O

    Finally caught up! 4.2.2 (JDQ39)

    Whole thing.
  13. O

    Finally caught up! 4.2.2 (JDQ39)

    I'm getting an error 7 when I attempt to flash this in CWM. I have CWM 6.0.2.3. My understanding is that I should be able to install this over 4.1.1 without wiping if I'm running stock. Is that correct? Anyone else getting this error?
  14. O

    [GUIDE] How To Unlock Bootloader and Root Verizon Galaxy Nexus

    So essentially, if I don't want to remove that file, my options for getting to CWM recovery are to flash it through ROM Manager or using adb fastboot commands to boot into it.
  15. O

    [GUIDE] How To Unlock Bootloader and Root Verizon Galaxy Nexus

    One quick question: When I flash CWM through adb or ROM Manager, it only uses the custom recovery temporarily, correct? When will it revert to the stock recovery? On reboot? I've read on how to permanently boot into a custom recovery, this was the only part that wasn't clear to me.