Android 4.3 failing even after flashing stock recovery


Last Updated: 2013-07-29 20:41:56
  1. Modman

    Modman Well-Known Member

    I got the dead Android error. Now I can't get the ota back to try again.

    Advertisement
  2. palmtree5

    palmtree5 Sunny Vacation Supporter! Moderator

    Try using the factory image and flash your device that way. Back up first though
  3. Modman

    Modman Well-Known Member

    I might as a last resort but I don't want to have to reinstall everything yet. Last time a guy named Scary Alien helped me fix the file that was breaking it I already have a twrp image I created before flashing stock recovery.
  4. jmar

    jmar Nexican VIP Member

    Yeah, you can use his OTA Verifier app find out why it isn't working. I helped test the app, so if you need help I should be able to assist.
    scary alien and Modman like this.
  5. Modman

    Modman Well-Known Member

    Where do I point ota verifier again?
  6. jmar

    jmar Nexican VIP Member

    The .zip file should be in /cache/ or /cache/recovery/
  7. Modman

    Modman Well-Known Member

    I hope the ota notification shows up so I can try again
  8. jmar

    jmar Nexican VIP Member

    It wasn't in there?
  9. Modman

    Modman Well-Known Member

    ==================
    Detailed Analysis
    ==================

    - you have 1 frozen system apps; this may impact the ability of the OTA's apply_patch script to update these apps and cause the OTA install to fail

    - there were 1 failed expressions; see below for the details about these tests that will cause your OTA install to fail

    - there were no bypassed expressions (good!)

    -------------------------------
    Frozen system apps analysis:

    1. ASUS Keyboard

    -------------------------------
    statistics:

    frozen system apps: 1
    success count: 466
    fail count: 1
    ignore count: 465
    partition count: 2
    protected count: 2
    bypassed count: 0

    -------------------------------
    updater-script analysis details:

    FAILED: line #290:

    assert(apply_patch_check("/system/bin/debuggerd", "a2323a0c8e245e3879d6b8beff6b2c4802045271", "df2e705da097e4d535b4f4d98fab3bd76601e76c"));

    (the above text has been copied to the clipboard)

    Last time scary made me an otaverify.zip

    If I open it and use it again. I get a debuggered file problem just like last time.
    Last time he gave me his debuggered file and that fixed it.
    scary alien and jmar like this.
  10. jmar

    jmar Nexican VIP Member

    Okay, so unfreeze the ASUS keyboard and remove that file and run the app against the OTA .zip and report back.
  11. jmar

    jmar Nexican VIP Member

    I start work in an hour, but I have to get ready now. I'll call in scary alien to assist. Good luck sir.
    scary alien and Modman like this.
  12. jmar

    jmar Nexican VIP Member

    Okay, pinged scary alien. Not sure when, but he should drop in soon. Gotta run. Good luck my friend.
    scary alien likes this.
  13. Rxpert83

    Rxpert83 Dr. Feelgood Moderator

    The Asus keyboard actually comes frozen stock for some reason. If you do a factory restore with the image file from google and check titanium its frozen.
    jmar and scary alien like this.
  14. Modman

    Modman Well-Known Member

    Asus keyboard is supposed to be frozen but I will rename the file and replace it with a copy and then rerun it. Glad I never deleted the one I used
    jmar likes this.
  15. scary alien

    scary alien not really so scary Moderator

    Hey guys! :wavey:

    Thanks for the heads-up, jmar! :thumbup:

    Yeah, we figured-out that the Asus keyboard does come frozen on stock (different language version, etc.?). I don't think you need to mess with the one you have...

    Hey Modman! How's it going? :)

    So is that OTA Verifier output what you had last time or is that a new run?

    When an OTA file is downloaded, it will (should) be in the /cache folder, so when it comes again (or we can probably force it to), check in that directory and see what the scoop is.

    You can also take a peek in the /cache/recovery/log file for the details on why the OTA actually failed. If you could post that log file here, that would be great!

    Will be watching and waiting :).
    colchiro, Modman, jmar and 1 other person like this.
  16. Groid

    Groid Well-Known Member

    I had the 'debuggerd' error and a kind soul took pity on me and sent it. I replaced the problem one (probably from installing Stickmount) and flashed the 4.3 update zip file in custom recovery successfully. Let me know if you still need the good 'debuggerd' file. It should let you take the OTA update with your stock recovery.
    Modman, jmar and scary alien like this.
  17. scary alien

    scary alien not really so scary Moderator

    OMG, that is awesome, Groid! Thanks and :thumbup:!

    Interesting bit of info about Stickmount being the possible culprit...

    Yeah, if you have it for Modman, that's a whole lot easier than me booting-up my Linux box, downloading the factory image, mounting the /system partition (though some voodoo I have to lookup in my notes :p), and sending it to Modman.

    I'm happy to do that if need be, though :).
    jmar and Modman like this.
  18. Modman

    Modman Well-Known Member

    ==================
    Detailed Analysis
    ==================

    - you have 1 frozen system apps; this may impact the ability of the OTA's apply_patch script to update these apps and cause the OTA install to fail

    - there were no explicitly failed expressions (good!)

    - there were no bypassed expressions (good!)

    -------------------------------
    Frozen system apps analysis:

    1. ASUS Keyboard

    -------------------------------
    statistics:

    frozen system apps: 1
    success count: 467
    fail count: 0
    ignore count: 465
    partition count: 2
    protected count: 2
    bypassed count: 0

    (the above text has been copied to the clipboard)

    Which means every time you reflash recovery debuggered gets corrupted. Solved. Now if only I could get that stupid ota prompt back to complete the update and reflash twrp.
    jmar likes this.
  19. scary alien

    scary alien not really so scary Moderator

    LOL and :thumbup:, Modman!

    Lemme dig-around...there's a way to force the OTA to start (I think it involves killing one of the system apps)...

    BRB.
    jmar and Modman like this.
  20. jmar

    jmar Nexican VIP Member

    Wipe data on Google Services Framework app under settings --> apps --> all.

    Then check for the OTA.

    I start in five minutes! Hurry up! ;)
    colchiro, scary alien and Modman like this.
  21. scary alien

    scary alien not really so scary Moderator

    This post over on XDA is what I remember:

  22. Modman

    Modman Well-Known Member

    If worse comes to I'll have to wait till it comes back.
  23. scary alien

    scary alien not really so scary Moderator

    Hey, you're supposed to be at work instead of ninja'ing me!!! :mad: ;) :p :D :)
    Modman and jmar like this.
  24. Modman

    Modman Well-Known Member

    This is not a nexus phone.

    Just deleted refreshing framework checking not working.
    scary alien likes this.
  25. Modman

    Modman Well-Known Member

    I think the stupid RPC error eventually went away last time but it really sucks no Google play store and no way to get ota back unless it pushes itself again.

Share This Page