05-10-2012 03:01 PM
937 ... 23456 ...
tools
  1. drezliok's Avatar
    there's still mine that I posted. Use that quickly before i too pull it. But you have to find it.
    Found it, downloaded it. But I am sitting on it for now. In my area I could really use it but I don't flash stuff with out seeing how things pan out.
    03-19-2012 10:50 AM
  2. anthonycr's Avatar
    I'm on CWM 3.0.2.5 or something like that... can anyone confirm a good flash with that?
    03-19-2012 10:58 AM
  3. anthonycr's Avatar
    I'd like to flash it because the only cell tower is a mile from my house and other people not on VM get four bars at my house while I get only one... I'm hoping this would change it... if I can find it and it works.
    03-19-2012 10:59 AM
  4. mjs2011's Avatar
    personally, i think it's better that no one distributes this for two reasons:

    1. there are at least 4 reports of phones completely bricked, possibly beyond repair.

    2. we've all seen how many people continue to brick their phones by using ROM manager or by hitting the Factory Reset option even though there are warnings.

    regarding #2 though, i'm a little disappointed by the reaction by some to the people that bricked their phones, including the "some people can't read or think" comment in the OP. i find myself pretty saavy with flashing and i'm always extra careful and thorough with reading directions, yet i was within a hare of flashing this thing in Touch Recovery this morning until i checked the comments one last time. i can't imagine breaking my phone and having to shell out money for a new one, and then being insulted on top of it.

    not trying to spark any battles or anything, i just think we're all better than that.
    03-19-2012 11:00 AM
  5. anthonycr's Avatar
    Yes this definitely wasn't anything like ROM Manager, I agree. Its just sad that so many people had to brick. I don't think this was really anyone's fault since LealieAnn could have no way of knowing the touch recovery would flash this over the firmware or something like that. There was no warning signs to me about flashing this except that it was art of an update that was told would totally make our phones unrootable. If you see my post back on the first page "I'm Scared" and Curiousnoobs comment that he was too, we came out alive because we waitex to flash until we could see the results.

    I'm very sad that this happened and I too don't want to see anyone, people posting links or the people flashing the radios made fun of.
    mjs2011 likes this.
    03-19-2012 11:09 AM
  6. drezliok's Avatar
    I'd rather use LeslieAnn's but I didn't download her version last night. I know my recovery is safe. Tracked Tvall's down though.
    03-19-2012 11:10 AM
  7. tvall's Avatar
    I'd rather use LeslieAnn's but I didn't download her version last night. I know my recovery is safe. Tracked Tvall's down though.
    Mine and leslieann's are almost exactly the same. I'm going to add tons of warnings to mine later and re upload.
    03-19-2012 11:36 AM
  8. kirurus's Avatar
    IHO Recovery / Backside ROM = Did not brick.
    03-19-2012 12:19 PM
  9. tvall's Avatar
    I'd rather use LeslieAnn's but I didn't download her version last night. I know my recovery is safe. Tracked Tvall's down though.
    Actually, I posted a new one. Use it
    03-19-2012 12:36 PM
  10. drezliok's Avatar
    Actually, I posted a new one. Use it
    Where did you post it at? I did a quick search for all your posts and didn't immediately see it.
    03-19-2012 01:17 PM
  11. tvall's Avatar
    Where did you post it at? I did a quick search for all your posts and didn't immediately see it.
    Same post as the first one. Just changed the link
    03-19-2012 01:21 PM
  12. DizzmalDan420's Avatar
    Well, this was enough to make me bail on the touch recovery, at least for now. Flashed back to Xionia and installed the radio update. Worked fine with Xionia recovery and BACKside IHO ROM. Wish I was the adventurous type and could afford a new phone. I find myself wondering how it'd react if I'd flash back to touch recovery now that the radio update is already installed. Can't afford to find out the hard way, though.

    Has anyone tried this update with Quattrimus ROM?
    03-19-2012 01:21 PM
  13. mjs2011's Avatar
    Well, this was enough to make me bail on the touch recovery, at least for now. Flashed back to Xionia and installed the radio update. Worked fine with Xionia recovery and BACKside IHO ROM. Wish I was the adventurous type and could afford a new phone. I find myself wondering how it'd react if I'd flash back to touch recovery now that the radio update is already installed. Can't afford to find out the hard way, though.

    Has anyone tried this update with Quattrimus ROM?
    yeah, i think i'm going to ditch the recovery as well. makes me wonder about issues i had when installing the Lewa ROM too. after multiple download and flash attempts, it was real wonky.
    03-19-2012 01:36 PM
  14. EarthnFire78's Avatar
    The Touch Recovery was nice and since my camera button is a little wonky worked, I may just go back to the RA 3.0.6.0 Recovery.
    03-19-2012 01:41 PM
  15. DizzmalDan420's Avatar
    LEWA worked fine for me with touch, but Quattrimus was wonky as all hell for me. Also had some issues with MD5 mismatches when restoring with touch recovery. As much as I love the touchscreen convenience, I'm going back to mashing my poor volume and camera buttons with Xionia.

    P.S. The radio update didn't seem to make a damn bit of difference with anything as far as I can tell.
    03-19-2012 01:42 PM
  16. tvall's Avatar
    Well, this was enough to make me bail on the touch recovery, at least for now. Flashed back to Xionia and installed the radio update. Worked fine with Xionia recovery and BACKside IHO ROM. Wish I was the adventurous type and could afford a new phone. I find myself wondering how it'd react if I'd flash back to touch recovery now that the radio update is already installed. Can't afford to find out the hard way, though.

    Has anyone tried this update with Quattrimus ROM?
    Touch recovery works fine, just not for installing it. (I think I read that radio flashing was disabled in it, I guess trying to just causes it to freak out and break)

    I'm not running quattrimus exactly, running cm9 with all the patches and stuff from tdm except mms and it works well. Pretty much the same
    DizzmalDan420 likes this.
    03-19-2012 01:55 PM
  17. JerryScript's Avatar
    Warning

    Do not use the same version as LeslieAnn posted.

    It has two versions of the same script. Please just be patient so no one else bricks their phone. We still don't know exactly what went wrong.
    03-19-2012 02:27 PM
  18. DKGerbil2's Avatar
    So for those of us who aren't idiots... is there a working link? Everything seems to be fine for those of us without the touch recovery.
    03-19-2012 03:38 PM
  19. tvall's Avatar
    Warning

    Do not use the same version as LeslieAnn posted.

    It has two versions of the same script. Please just be patient so no one else bricks their phone. We still don't know exactly what went wrong.
    I'm pretty sure the problem is cwmt has radio flashing "disabled" in a way that makes it break when a flash is attempted.

    Have you looked at my updater yet?
    03-19-2012 03:41 PM
  20. LeslieAnn's Avatar
    whoa whoa whoa is there a ~secret~ link for the people who CAN read/think? ;D
    Maybe, but I don't like feeling even partially responsible for messing up peoples phones.

    I don't like carrying that burden, others may be able to just brush it off easily, but I can't.


    personally, i think it's better that no one distributes this for two reasons:

    1. there are at least 4 reports of phones completely bricked, possibly beyond repair.

    2. we've all seen how many people continue to brick their phones by using ROM manager or by hitting the Factory Reset option even though there are warnings.

    regarding #2 though, i'm a little disappointed by the reaction by some to the people that bricked their phones, including the "some people can't read or think" comment in the OP.
    The first few phones were accidents, we didn't know about the problem.
    We DO know there is an issue and issued appropriate warnings.

    Rom Manager is different.
    We don't have control over it, and can't warn people ahead of time or have it removed. We do have some control over this.

    While it may sound like I don't give a sh*t, it's quite the opposite. I don't like the idea that something I helped make or distributed causing problems or is looked at in the same vein as Rom Manager. I care too much to let this continue to happen which is why I pulled it.

    Which is also why you got the comments you are offended by.
    I tried to give as much warning and things as I could and some still wouldn't pay attention, so to keep myself from feeling worse about this crap, I removed it. Like I said, I can't just easily brush that sort of thing aside like others can, this will bother me for a while. Pulling it down was for your sake as well as mine. When I pulled it down I was very angry and sad at the same time.

    I didn't say none of you could read or think, just some of you. If it offended you, then maybe you feel you fall into that camp.


    Do not use the same version as LeslieAnn posted.

    It has two versions of the same script. Please just be patient so no one else bricks their phone. We still don't know exactly what went wrong.
    That doesn't have any effect, it's just how Virgin set it up, I have seen similar before and it hasn't caused any issues. At worst, it flashes it twice. No big deal.

    I suspect the problem is that the touch recoveries do not understand "write_radio_image" and are just installing the image right over boot.img or system, but it''s only a guess.
    03-19-2012 03:51 PM
  21. mjs2011's Avatar
    The first few phones were accidents, we didn't know about the problem.
    We DO know there is an issue and issued appropriate warnings.

    Rom Manager is different.
    We don't have control over it, and can't warn people ahead of time or have it removed. We do have some control over this.

    While it may sound like I don't give a sh*t, it's quite the opposite. I don't like the idea that something I helped make or distributed causing problems or is looked at in the same vein as Rom Manager. I care too much to let this continue to happen which is why I pulled it.

    Which is also why you got the comments you are offended by.
    I tried to give as much warning and things as I could and some still wouldn't pay attention, so to keep myself from feeling worse about this crap, I removed it. Like I said, I can't just easily brush that sort of thing aside like others can, this will bother me for a while. Pulling it down was for your sake as well as mine. When I pulled it down I was very angry and sad at the same time.

    I didn't say none of you could read or think, just some of you. If it offended you, then maybe you feel you fall into that camp.


    i understand that you were frustrated and i completely accept your explanation.

    for the record, no, i don't feel that i fall in the camp of those that "can't read or think". reading up is the only reason i didn't break my phone last night.
    LeslieAnn likes this.
    03-19-2012 04:00 PM
  22. jack454's Avatar
    LeslieAnn you have done to much good for the V community to even feel a little at fault. Everyone that comes here knows or should know the risk of flashing anything to their phone. I say thankyou for what you have and will do for us all.
    03-19-2012 04:15 PM
  23. EarthnFire78's Avatar
    LeslieAnn, I to say thank you for your work with OV'ers and don't feel bad, the ones that had the recovery should have read the info, this includes me.

    Radio.img flashing has been disabled (read: should be disabled). So we should have known that flashing a Radio.img with it was/is a bad idea.

    The Touch Recovery works well at what it does, never had a problem with it, but it does say Radio flash is disabled, so I would not blame the recovery either or the dev: just carelessness on the part of people.
    Vishwar likes this.
    03-19-2012 04:53 PM
  24. llamadon's Avatar
    LeslieAnn, I to say thank you for your work with OV'ers and don't feel bad, the ones that had the recovery should have read the info, this includes me.

    Radio.img flashing has been disabled (read: should be disabled). So we should have known that flashing a Radio.img with it was/is a bad idea.

    The Touch Recovery works well at what it does, never had a problem with it, but it does say Radio flash is disabled, so I would not blame the recovery either or the dev: just carelessness on the part of people.

    That was not nice. I though I could find someone else to blame for bricking my phone. Now I have to take responsibility for my own actions, that does not seem fair.

    Also, no so far I do not thing my computer can even see it. May be off to t-mobile for me. I was just staying becouse I had a phone and could not afford to get a new one right now but... (Better coverage where I am.)
    EarthnFire78 and Syntax357 like this.
    03-19-2012 05:04 PM
  25. EarthnFire78's Avatar
    That was not nice. I though I could find someone else to blame for bricking my phone. Now I have to take responsibility for my own actions, that does not seem fair.

    Also, no so far I do not thing my computer can even see it. May be off to t-mobile for me. I was just staying becouse I had a phone and could not afford to get a new one right now but... (Better coverage where I am.)
    That is why I believe that it flashed the Radio Image over the whole firmware, from recovery to data/cache everything is now the radio. I had the touch recovery and was about to flash it, and reading that about the radio showed that I did not even read the OP.
    Syntax357 likes this.
    03-19-2012 05:15 PM
937 ... 23456 ...
LINK TO POST COPIED TO CLIPBOARD