The troubles are fine-- It was a learning experience for me, I suppose. I had never used an update.zip installer, nor had I used and Odin, so I'm happy to have gotten to do so.
Now then, I'm camping at the moment, which means I won't have much of a chance to work with flashing it over for a while. So far, with the stock pre-rooted, the only thing that's bugging me is the constant notification about updating, but that can be fixed by editing build.prop, so I'm not complaining.
I do, however, have a question. Have you had any luck using UOT Kitchen with Gingerbread on the Replenish? If you haven't tried, I would be willing to be a test subject, I suppose. It seems like it would work fine, as it has the QVGA size of our screen listed.
One other thing-- Your website is currently offline, as I was going to download the stock to my netbook(What I'm currently on, via EasyTether. If I'm not back on tonight anytime, it's because I messed up flashing CWM5, which I'm going to go do after this post.
I really hope I can get this working~ When you flashed to PheoniX for the first time, were you running FroYo, or Gingerbread?
I used the kitchen way back when I was on LeafROM because the rom was de-odexed, however mine currently is not. I'll be making another attempt at it before the final 0.3 version is out though. I just checked my website and it is fine for me, though I've been having trouble with me email, I might have to file a ticket with the stupid web host again.. Thanks for letting me know it went down.
The first time I ran PhoeniX, I was already on GB. I flashed back to a stock version of Froyo and did the upgrade, then I built PhoeniX based off of LeafROM by Shabbypenguin and we've since added a but more to it, most notably the custom kernel by DMRLook. You may have success flashing from Froyo to PhoeniX, I just haven't tried it myself since I'm the one dumping all the different versions and building them. I kinda lose track pretty easily which versions are what, too :P
Well, I attempted to use PheoniX.tar for CWM5(From 0.2), and it stuck my phone at SPH-M580 for the last half hour, then it went black. Upon going black, I tried to press the Power button to see if it had booted and just auto-locked, and the keyboard lit up, but not the screen. CWM5 is accessible, but for some reason, it hangs at SPH-M580. I didn't install PheoniX, only CWM5.
As for the website, it's still showing the site as unavailable. Could you post a direct link to your stock GB ROM? I REALLY need it.
A bit of an update-- I'm in McDonald's right now, downloading the stock rooted ROM.
When I used PheoniX.tar, it sent me into that frozen boot screen, like I said, Which leads me to believe that something's wrong with the CWM5 package from 0.2. Once you get the fixed 0.3 .zips ready, will they be flashable from the stock recovery?
I tried to update with the Sprint 0.3 package. The installer runs but it hangs on boot and will not pass the Custom Kernel screen. I then tried to reflash 0.2 and right away 0.3, but it still hangs.
And when I tried to go back to 0.2 without the 0.3 update is still hangs. Seems like a problem with the new CWM.
Sorry it was the boot.img that was messed up reflashed it with the original and boots fine with the updated system.
Last edited by sprintHTC; 04-23-2012 at 02:28 AM.
why is this version unrooted?!
Fixed with SuperOneClick.
Last edited by sprintHTC; 04-23-2012 at 03:20 AM.
The bluetooth in 0.3 is broken. When activated it sends the device into a hot reboot loop.
If you read above, you'll see that Fireball, the dev for this project, he already stated that 0.3 has a modem issue, and your Bluetooth issue culd be caused by the sasame thing happening. Please note that this software is neither official nor complete, and thus, will have bugs. I plan on using the stock 2.3.6 pe-rooted ROM he uploaded to his site until there's a proven working method for flashing this ROM to the Sprint device.
Sent from my SPH-M580 using Tapatalk 2
Lolwut Fireball? Firehak*
Sent from my SPH-M580 using Tapatalk 2
Any chance you can write a small script that we could run to stop the OTA update prompts? I went in and changed all the “EK18″ in /system/build.prop to say “FA19″ (or at least I think I got them all!) but I'm still getting the prompts. After a couple days, it finally stops bugging me, but if I reboot, then the whole process starts all over.
If I had a clue how to do it, I'd write one, but my programming is really old school - FORTRAN and Pascal...and some BASIC sprinkled in for flavor. (And I haven't used it in 20+ years!)