1. Check out our app, Forums for Android! Download and leave feedback here!

HELP! Froyd update fine, Radio update not!

Discussion in 'Android Devices' started by sid378, Sep 13, 2010.

  1. sid378

    sid378 Well-Known Member
    Thread Starter
    16

    Feb 3, 2010
    62
    3
    16
    As title says, today i updated my GSM hero with Froydvillain 1.5, hours of playing around, installing a kernel (All well and good) i decide to install the latest radio update, as the one i had was ancient

    Followed instructions to the letter, waited until Formatting Cache was complete (left the room and was gone for 5 minutes, looked at it for a bit longer and no status bar, assume it completed)

    Reboot phone and now it's just sitting on the 'HERO' part of startup, what do i do ?

    I had an urge to pull the battery, but i'm not sure if it's 'okay' at this point, since instructions specifically said NOT to.

    Help? :(
     

    Advertisement

  2. Slug

    Slug Check six!
    Moderator
    2,043

    Aug 1, 2009
    20,553
    16,986
    2,043
    Male
    Mobile phone retail
    Inverness, UK
    Five minutes is more than enough time for the cache formatting, as it's practically instantaneous. If it didn't eventually boot after your post, pull the battery for a couple of minutes then try again - chances are it will boot fine. I get this occasionally after using the recovery (Amon_RA 1.7.0.1) and removing the battery/rebooting always works.
     
  3. sid378

    sid378 Well-Known Member
    Thread Starter
    16

    Feb 3, 2010
    62
    3
    16
    This can be closed, or stickied.. had trouble finding anything with my specific issue, but yeah the problem wasn't at the cache formatting step, since i read somewhere it's near instant (Has a status bar that quickly dissapears)

    Problem was it was stuck on the Hero boot-up part, after about an hour i pulled the battery (despite what was warned) and tried again, it got as far as the Quitly Hopeless (Froydvillain) and hung there for ages... then it shut off, no lights, no response, no nothing, even pulled the battery and tried again!

    Turns out it had been lingering on the first hero boot-up screen for so long it drained the battery :O

    In short, all is well and good now.. with the sole exception of mms not correctly working for me.

    Thanks for your reply though :)
     
  4. Slug

    Slug Check six!
    Moderator
    2,043

    Aug 1, 2009
    20,553
    16,986
    2,043
    Male
    Mobile phone retail
    Inverness, UK
    Cool Sid, thanks for the update.
     
  5. Xyro

    Xyro 4 8 15 16 23 42
    Moderator
    1,413

    Dec 1, 2009
    12,845
    9,129
    1,413
    UK
    The 'do not pull the battery' warnings are only for flashes that go as planned.

    If your phone hangs permanently, like yours did, sometimes it's all you can do. Good call on waiting for an hour though :)
     
  6. sid378

    sid378 Well-Known Member
    Thread Starter
    16

    Feb 3, 2010
    62
    3
    16
    That's what i thought too, couldn't get any 'reactions' from the phone any other way, so no matter what that's the only thing i could do.. atleast this will hopefully serve as a heads-up for others :p

    My thoughts as to why it hung was probably battery-related.. when i finally had it booting past the HERO part, it just shut off in the middle of the 'Quietly Hopeless' part, heh.

    Also who the hell would pull the battery when flashing.. you get all the info on screen, with the exception of the reboot into recovery mode halfway when you see the phone out of box icon, that's a few seconds of panic :D
     
  7. daveybaby

    daveybaby Well-Known Member
    93

    Sep 21, 2009
    919
    105
    93
    Software engineer
    UK
    Really? I'd always figured that building the dalvik cache was a pretty time+cpu intensive process. Whenever i download+install an app, the install part takes a noticable amount of time (typically around 10-20 seconds), and impacts the performance of any other app that's running. If it's not building the dalvik cache that takes the time, what is it?

    My hero always takes a LOOOONG time (well over 5 minutes) to boot the first time after updating a radio or a kernel. I'd always figured that was due to having to rebuild the dalvik code for every app.

    Actually, on a fairly related topic: i've been wondering - is the Froyo JIT compiler actually a JIT compiler, or does it compile into native code once at installation? It seems crazy to use JIT compilation on an installed app... :thinking:
     
  8. Slug

    Slug Check six!
    Moderator
    2,043

    Aug 1, 2009
    20,553
    16,986
    2,043
    Male
    Mobile phone retail
    Inverness, UK
    Oh it is, but I don't think that's what is done during the "formatting cache..." part of a radio flash. This occurs in the recovery menu remember?
     
  9. daveybaby

    daveybaby Well-Known Member
    93

    Sep 21, 2009
    919
    105
    93
    Software engineer
    UK
    Ah, yeah, got my wires crossed there :eek:
     
Tags:

Share This Page

Loading...