08-07-2012 02:25 PM
420 ... 11121314151617
tools
  1. wormy987123's Avatar
    I noticed it this morning I have 2 backups with that date.......


    Sent from my LG-LS670 using Tapatalk 2
    Pkt_Lnt likes this.
    06-27-2012 02:57 PM
  2. Pkt_Lnt's Avatar
    Drew, getting some more info on the 1980 date issue. thekraven's new CAI 16, 16b, 16c have flash / boot issues. A logcat shows that same date.
    Code:
    <6>[ 95.247333] request_suspend_state: wakeup (0->0) at 95251073299 (1980-01-06 02:13:54.302528299 UTC)
    http://forums.androidcentral.com/lg-...ml#post1893687

    http://forums.androidcentral.com/lg-...ml#post1893991

    Not saying it is COT, but would like to have your knowledge involved in this, might be related.
    06-27-2012 03:20 PM
  3. Zhara's Avatar
    Caught it in action! It went back to the correct date and time when I turned airplane mode off. Anyway I'll shutup now as it really has nothing to do with the recovery. (Sorry Drew :o)
    06-27-2012 10:21 PM
  4. lichan's Avatar
    If I remember correctly, this 1980 date has something to do with time zero in the Unix and, therefore. Linux system, which is where the various kernels originate. Times are kept as an offset to some specific date in 1980.
    Pkt_Lnt likes this.
    06-28-2012 01:01 AM
  5. drewwalton19216801's Avatar
    Everyone that is experiencing this strange behavior, what ROM were you using when you made the backup that is displaying this date?
    06-28-2012 05:16 AM
  6. kylemaguire's Avatar
    Everyone that is experiencing this strange behavior, what ROM were you using when you made the backup that is displaying this date?
    Quatramis for me. And this new rom over in the V forums called paranoid android

    Sent from my LG-VM670 using Android Central Forums
    06-28-2012 05:31 AM
  7. drewwalton19216801's Avatar
    Quatramis for me. And this new rom over in the V forums called paranoid android

    Sent from my LG-VM670 using Android Central Forums
    Interesting. I'm going to wait for more responses before I make a hypothesis, but I have a hunch that this may be somehow related to the clock sync bug experienced in ICS-based ROMs. I will say though that the issues a few have had flashing CAI alpha16 are concerning.
    06-28-2012 06:02 AM
  8. strabo231's Avatar
    Interesting. I'm going to wait for more responses before I make a hypothesis, but I have a hunch that this may be somehow related to the clock sync bug experienced in ICS-based ROMs. I will say though that the issues a few have had flashing CAI alpha16 are concerning.
    Just to kinda help support the "not drew's recovery" theory here, I've had that same thing happen two or the times, always with ICS roms, but using CWM.

    Sent from my LG-VM670 using Android Central Forums
    kylemaguire likes this.
    06-28-2012 06:53 AM
  9. Pkt_Lnt's Avatar
    Everyone that is experiencing this strange behavior, what ROM were you using when you made the backup that is displaying this date?
    Thekraven Cold as Ice a15f. Still not able to get past boot anim in a16 b-d.

    edit - tdm quatrrimus nightly 06282012 that has the speaker phone fix flashes and boots fine. That speaker fix is where this problem began with CAI.

    Kindle Fire w twa_priv ICS / CM9 linaro based on SG7 & Hashcode 3.0 kernel - Tapatalk 2
    06-28-2012 11:56 AM
  10. sblood86's Avatar
    If I remember correctly, this 1980 date has something to do with time zero in the Unix and, therefore. Linux system, which is where the various kernels originate. Times are kept as an offset to some specific date in 1980.
    This is my understanding as well; I've seen this bug occur on the Optimus S in Xionia as well as COT. I've also seen it occur on the Kindle Fire in both an old CWM by the DooMLoRD and COT (only actually happened when the device died and I didn't allow the system to reset the clock before going to recovery).
    06-28-2012 09:32 PM
  11. vernotzy21's Avatar
    Q:I tried to flash paranoid rom for the v I don't have service so I don't care about radio IV flashed v roms before but it wont let me with this one is it the rom or recovery? Or cause I look funny?

    Sent from my LS670 using Android Central Forums
    06-29-2012 01:03 AM
  12. drewwalton19216801's Avatar
    Q:I tried to flash paranoid rom for the v I don't have service so I don't care about radio IV flashed v roms before but it wont let me with this one is it the rom or recovery? Or cause I look funny?

    Sent from my LS670 using Android Central Forums
    Error messages or logs please... saying "it won't let me flash it" means literally nothing.
    06-29-2012 01:55 AM
  13. pdxguy77's Avatar
    ive seen a few of my backups over the last few months show the 1980 dates...not just with cannibal...but for the most part the timestamps are 3 hours off from my time zone
    06-29-2012 10:26 AM
  14. Pkt_Lnt's Avatar
    ive seen a few of my backups over the last few months show the 1980 dates...not just with cannibal...but for the most part the timestamps are 3 hours off from my time zone
    Is your time zone 3 hours offset from GMT?

    - via Kindle Fire w twa_priv ICS / CM9 linaro based on SG7 & Hashcode 3.0 kernel - Tapatalk 2
    06-29-2012 11:01 AM
  15. Pkt_Lnt's Avatar
    Drew, do you have a quick list of error codes, [Status X]? I have gotten Status 0 errors on flashing a ROM, reboot recovery in COT and flash again is successful. I forget to save log, will get one if it happens again.

    - via Kindle Fire w twa_priv ICS / CM9 linaro based on SG7 & Hashcode 3.0 kernel - Tapatalk 2
    06-29-2012 11:06 AM
  16. kylemaguire's Avatar
    Error messages or logs please... saying "it won't let me flash it" means literally nothing.
    in this case, the developer left out some sound files and it screwed up the sig verification.

    Sent from my LG-VM670 using Android Central Forums
    06-29-2012 12:33 PM
  17. hlxanthus's Avatar
    Just flashed this via recovery over v1.0.8, and man this is one awesome recovery! Love the auto backup feature!
    07-01-2012 08:03 PM
  18. Pkt_Lnt's Avatar
    I keep getting [Status 0] errors, wish I knew why.
    07-01-2012 08:06 PM
  19. thewraith420's Avatar
    I really like this recovery also but I don't care for the auto backup..... Here's why.... I go into mounts & storage and format everything then wipe dalvik then flash a rom and it just made a backup of nothing

    Sent from my VM670 using Tapatalk 2
    07-01-2012 08:07 PM
  20. wormy987123's Avatar
    if you read the prompts it ask if you want to back up its not making you, I dislike the feature because I always make a fresh backup when I flash a new rom

    Sent from my LG-LS670 using Tapatalk 2
    07-01-2012 08:10 PM
  21. Buddlespit's Avatar
    I keep getting [Status 0] errors, wish I knew why.
    from ClockworkMod Recovery - RootzWiki :

    STATUS 0
    This is usually caused by an incompatible update-binary in edify ZIPs. Replacing it with a compatible one, then re-signing the ZIP, will usually fix this error.

    I'm going to assume that an incompatible ROM is being installed or you forgot to set notepad++ to UNIX format (Edit-->EOL Conversion-->Convert to UNIX Format).
    Pkt_Lnt likes this.
    07-01-2012 08:17 PM
  22. Pkt_Lnt's Avatar
    from ClockworkMod Recovery - RootzWiki :

    STATUS 0
    This is usually caused by an incompatible update-binary in edify ZIPs. Replacing it with a compatible one, then re-signing the ZIP, will usually fix this error.

    I'm going to assume that an incompatible ROM is being installed or you forgot to set notepad++ to UNIX format (Edit-->EOL Conversion-->Convert to UNIX Format).
    I was searching for Cannibal Status codes, never thought to try CWM, duh.

    Nope, this was from the SuperSU zip and some of the fix zips for thekraven and tdm. Sometimes a second flash works, usually I have to power down fully and then use the three button direct to recovery and it works.

    Only editing build.prop so far, but I do have notepad++ configured, thanks.
    07-01-2012 08:24 PM
  23. Buddlespit's Avatar
    Did you have any memory errors when you flashed this recovery? I had it happen twice, and I almost didn't catch it the first time. Only the first few lines reported out of memory, but the rest of the lines stated that the rest of the blocks were written correctly. It happened the second time, but the third was a charm. That was the one and only time I flashed it from the ROM (via adb). Before that, I've always flashed it (via adb) from the recovery.
    07-01-2012 08:48 PM
  24. Pkt_Lnt's Avatar
    Did you have any memory errors when you flashed this recovery? I had it happen twice, and I almost didn't catch it the first time. Only the first few lines reported out of memory, but the rest of the lines stated that the rest of the blocks were written correctly. It happened the second time, but the third was a charm. That was the one and only time I flashed it from the ROM (via adb). Before that, I've always flashed it (via adb) from the recovery.
    No, I have gone back and forth between COT and CWMT using adb installs. I have a tall adb window open with plenty of buffer so I can scroll and check all output first. No errors. I gave up on the superSU zip and just installed from the Play store and used root explorer to delete the old superuser apk. The patches from thekraven and tdm make me wonder, especially with the problems now on CAI. Lubarsky, blame it on Lubarsky.
    07-01-2012 08:53 PM
  25. drewwalton19216801's Avatar
    I really like this recovery also but I don't care for the auto backup..... Here's why.... I go into mounts & storage and format everything then wipe dalvik then flash a rom and it just made a backup of nothing

    Sent from my VM670 using Tapatalk 2
    Read the first post again. There are instructions on how to disable that feature.
    07-01-2012 09:47 PM
420 ... 11121314151617
LINK TO POST COPIED TO CLIPBOARD