So I have Scott's CleanROM GBE 1.7.5 on my phone. I was wandering through my phone's settings, and accidentally hit something in the update area. I do not know what I was thinking, but I know I expected it to ask me if I was sure I wanted to update. So far it has only done the first part where it prepares the phone for the update. I do not know when the other part is coming but I assume it is automatic. I was planning on updating to a rooted ICS once I felt comfortable with it (just seemed a little harder than my original flash of rooted GB). So if it would be easier to just update to ICS some way now, I would be very willing to do that. I am s-on, I believe I installed Amon Ra, but I am not sure how to check and not sure if I have an actual recovery rom or not.
I checked around and found similar problems, but nothing really like mine since my update has not gone all the way thru yet. If anyone could help, it would be greatly appreciated. THank you.
Easiest way is to relock your bootloader, run the newest ruu, unlock and flash recovery again. That way you will be set up to run any ics Rom without having to worry about flashing a patch
Sent from my ADR6425LVW using Tapatalk 2
pwned3 said:
Easiest way is to relock your bootloader, run the newest ruu, unlock and flash recovery again. That way you will be set up to run any ics Rom without having to worry about flashing a patch
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Ok just to make sure I know and don't mess anything else up. I relock (should be easy to.find a guide) . Then run the update on my phone? Then unlock thru HTC again, and flash the actual amon or CWM to my phone? And from there I will be able to flash any ICS Rom with more ease?
And thank you for the quick reply.
Edit: I searched the internet more for less-similar situations. I think all I have to do is re-lock. Download the newest RUU from Android police and put it in the root of the SD card as PH98IMG.zip (I'm assuming it should be the internal memory, but please correct me if I am wrong.) Hold volume down & power to boot into bootloader, then the phone takes it from there?
Also,nothing I have to do as far as unrooting?
malignancyy said:
Also,nothing I have to do as far as unrooting?
Click to expand...
Click to collapse
Nope just relock the bootloader
AshtonTS said:
Nope just relock the bootloader
Click to expand...
Click to collapse
Okay, thanks a lot. And I edited this into a prior post, but I just wanted to make sure:
I have to re-lock. Download the newest RUU from Android police and put it in the root of the SD card as PH98IMG.zip (I'm assuming it should be the internal memory, but please correct me if I am wrong.) Hold volume down & power to boot into bootloader, then the phone takes it from there?
malignancyy said:
Okay, thanks a lot. And I edited this into a prior post, but I just wanted to make sure:
I have to re-lock. Download the newest RUU from Android police and put it in the root of the SD card as PH98IMG.zip (I'm assuming it should be the internal memory, but please correct me if I am wrong.) Hold volume down & power to boot into bootloader, then the phone takes it from there?
Click to expand...
Click to collapse
Then you just have to press continue when it tells you to.
PS: Another way to get to the bootloader is to use adb (make sure USB debugging is enabled on your phone)
Command:
adb reboot bootloader
I find it easier than holding down buttons for a long time, but that's just my personal preference.
(Also, most custom ROMs can reboot to bootloader from within the ROM. I forget if CleanROM GBE includes the advanced power menu.)
pwned3 said:
Easiest way is to relock your bootloader, run the newest ruu, unlock and flash recovery again. That way you will be set up to run any ics Rom without having to worry about flashing a patch
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Good advise, and if he RUUs to ICS, then he should not even get asked to install the update because it will already be installed on his phone.
Also RUU twice. Just reboot into bootloader right away and install the RUU a second time. Then boot up normally and remove the zip file from the sdcard.
Thanks, you all helped a lot. I was able to get the stock rom, rooted, and running smoothly. But, once I tried to install custom roms I had problems. I decided to S-off to make it easier from here on out. After a few tries, it said I had successfully done the S-off. I tried to install Juopunutbear custom hboot, directly afterwards and it said it installed but I was stuck on the Juopunutbear screen. After this, I have not been able to get past hboot.I do not think the custom hboot actually installed. It is saying from the top:
***TAMPERED***
***LOCKED***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.27.0000
RADIO-2.22.10.0801r/2.22.10.0803r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Aug 6 2012, 19:24:37
My external sd card needed formatting, so I just did that. And my plan is to RUU again (i guess twice), flash recovery (when clicked on currently, nothing happens), I guess root although I am not sure about this part, then try to install a custom rom.
Didn't want to make another thread just to check on this, but does this sound about right?
And as far as installing rom since I am now s-off, just go to recovery and flash it, nothing else at all to worry about?
malignancyy said:
Thanks, you all helped a lot. I was able to get the stock rom, rooted, and running smoothly. But, once I tried to install custom roms I had problems. I decided to S-off to make it easier from here on out. After a few tries, it said I had successfully done the S-off. I tried to install Juopunutbear custom hboot, directly afterwards and it said it installed but I was stuck on the Juopunutbear screen. After this, I have not been able to get past hboot.I do not think the custom hboot actually installed. It is saying from the top:
***TAMPERED***
***LOCKED***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.27.0000
RADIO-2.22.10.0801r/2.22.10.0803r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Aug 6 2012, 19:24:37
My external sd card needed formatting, so I just did that. And my plan is to RUU again (i guess twice), flash recovery (when clicked on currently, nothing happens), I guess root although I am not sure about this part, then try to install a custom rom.
Didn't want to make another thread just to check on this, but does this sound about right?
And as far as installing rom since I am now s-off, just go to recovery and flash it, nothing else at all to worry about?
Click to expand...
Click to collapse
The jbear hboot might have failed because you are on the newest global update with 2.27 hboot, and I believe the controlbear tool still has the 2.25 hboot. (someone correct me if I'm wrong)
I think there is an unguarded 2.27 hboot somewhere, so you should flash that manually.
Sent from my NeoMax Rezound
Right now, like I said the hboot says at the top 2.27.0000
When I reboot from there, or boot it regularly it goes to a JuopunutBear, black and green writing screen.
I have tried to install this forum.xda-developers.com/showthread.php?t=1843030 ([HBOOT] HBoot 2.27 (from 4.03.605 OTA) Unlocked) from both, but cannot figure out how to do so.
edit: within JuopunutBear, wiping says "can't open" and applying update gives "failed to open loopdevice" and "failed to mount /sdcard" when I try to update.
Within the regular hboot, I get "no image" as it searches for files.
Well, I put the same file on a new sd card, and it worked on the first try, kinda.
Now it appears my phone is bricked. It will not boot at all. She barely lasted a few hours s-off before I messed it up. Any tips anyone out there can give to this sad fellow, or am I off to get a replacement?
A little more info on this. Windows tries installing QHUSB_DLOAD driver for it when plugged in, but unsuccessfully. The charging indicator does not come on either. Have tried to turn it on plugged in with battery out, and battery in both ways.
malignancyy said:
Well, I put the same file on a new sd card, and it worked on the first try, kinda.
Now it appears my phone is bricked. It will not boot at all. She barely lasted a few hours s-off before I messed it up. Any tips anyone out there can give to this sad fellow, or am I off to get a replacement?
Click to expand...
Click to collapse
Depending on what caused the brick, it may be recoverable.
Check out the unbricking thread in the dev section.
Sent from my NeoMax Rezound
Wanted to post this in the NeoMax thread, but I am currently not allowed to. I gave up on my last Rezound, and am getting a replacement here soon. I did a bunch of reading before and after I got my Rezound, and a bunch more the past few days as I wanted to get an ICS rom. Unfortunately, the one time I deferred from guides I followed (installing the JBear hboot), I killed my Rezound. I now want to stay S-on, at least until I gain some more familiarity and skill with this whole process.
What I plan on doing is once I get the Rezound, installing the OTA update, possibly having to wait for it to do so. I assume this would be the newest, .2, global update. I plan to unlock, flash recovery, then root. The rom I really want however is NeoMax. There are limited instructions on how I go about this. But from what I understand I change the filename to PH98IMG and flash it from hboot? The file name is originally, GlobalRuuPH98IMG.zip, but the thread title claims ICS De-Sensed 3.14.605.12, which I believe is two versions prior. So here I am lost. If it is in fact older, I have to flash the rom through recovery, then flash the kernel, correct? If so, do I just use the 3.14.605 that was in the NeoMax thread?
Sorry to bother you all with what i'm sure others have done many times. Like I said, I have read a lot on this, its just that I either did not understand in the least what the guides were saying, or it seemed like this situation was much different. And on a side note, if there is any other rom out there that someone would recommend that would make this easier (such as being on the latest kernel), I wouldn't be opposed to trying it. I just want one that is desensed, as it is one of my main reasons for wanting a custom rom.
malignancyy said:
Wanted to post this in the NeoMax thread, but I am currently not allowed to. I gave up on my last Rezound, and am getting a replacement here soon. I did a bunch of reading before and after I got my Rezound, and a bunch more the past few days as I wanted to get an ICS rom. Unfortunately, the one time I deferred from guides I followed (installing the JBear hboot), I killed my Rezound. I now want to stay S-on, at least until I gain some more familiarity and skill with this whole process.
What I plan on doing is once I get the Rezound, installing the OTA update, possibly having to wait for it to do so. I assume this would be the newest, .2, global update. I plan to unlock, flash recovery, then root. The rom I really want however is NeoMax. There are limited instructions on how I go about this. But from what I understand I change the filename to PH98IMG and flash it from hboot? The file name is originally, GlobalRuuPH98IMG.zip, but the thread title claims ICS De-Sensed 3.14.605.12, which I believe is two versions prior. So here I am lost. If it is in fact older, I have to flash the rom through recovery, then flash the kernel, correct? If so, do I just use the 3.14.605 that was in the NeoMax thread?
Sorry to bother you all with what i'm sure others have done many times. Like I said, I have read a lot on this, its just that I either did not understand in the least what the guides were saying, or it seemed like this situation was much different. And on a side note, if there is any other rom out there that someone would recommend that would make this easier (such as being on the latest kernel), I wouldn't be opposed to trying it. I just want one that is desensed, as it is one of my main reasons for wanting a custom rom.
Click to expand...
Click to collapse
Don't worry, you're not bothering anyone.
The people who claim to have bricked their phones when they have a boot loop and say nothing about their rom and firmware are bothering people.
Keep doing what you are currently doing and people will always be willing to help you.
Ok, so back to helping...
Of you're starting on GB, make sure you update to 3.14.605.12 before updating to the most recent one.
If you update via OTA then you don't need to worry.
Keep in mind that NeoMax is based off of the 3.14.605.12 build, so you'll have to mix n match the right way to get it to work on the latest firmware.
I believe it was you have to use the new kernel if you use the new radios and hboot.
So after installing NeoMax, flash the PH98IMG that contains the newer kernel, not the 3.14.605.12 version.
Or use fastboot to flash the kernel. (my preferred method while s-on)
Sent from my NeoMax Rezound
PS: A good way to get the required 10 posts to post in the dev section is post random stuff in the off topic thread.
wlmeng11 said:
Don't worry, you're not bothering anyone.
The people who claim to have bricked their phones when they have a boot loop and say nothing about their rom and firmware are bothering people.
Keep doing what you are currently doing and people will always be willing to help you.
Ok, so back to helping...
Of you're starting on GB, make sure you update to 3.14.605.12 before updating to the most recent one.
If you update via OTA then you don't need to worry.
Keep in mind that NeoMax is based off of the 3.14.605.12 build, so you'll have to mix n match the right way to get it to work on the latest firmware.
I believe it was you have to use the new kernel if you use the new radios and hboot.
So after installing NeoMax, flash the PH98IMG that contains the newer kernel, not the 3.14.605.12 version.
Or use fastboot to flash the kernel. (my preferred method while s-on)
Sent from my NeoMax Rezound
PS: A good way to get the required 10 posts to post in the dev section is post random stuff in the off topic thread.
Click to expand...
Click to collapse
As far as which kernel, this is what was said in the NeoMAX Q&A:
Q: "I flashed your rom and my phone gets really hot after a while. In fact, Ive noticed it on all the newer roms lately. What could be causing it and how can I attempt to fix it?"
A: "Make sure you have updated your radio to the latest available and then flash the 2nd to latest kernel. This combination has been known to have the best rom performance for all my roms and decreased heat"
SO this means I should use the 4.03.605.1? And the newest radio will automatically still be on there from the OTA update, or will I have to flash those as well? I have no experience in flashing radios so this is new ground to me.
malignancyy said:
As far as which kernel, this is what was said in the NeoMAX Q&A:
Q: "I flashed your rom and my phone gets really hot after a while. In fact, Ive noticed it on all the newer roms lately. What could be causing it and how can I attempt to fix it?"
A: "Make sure you have updated your radio to the latest available and then flash the 2nd to latest kernel. This combination has been known to have the best rom performance for all my roms and decreased heat"
SO this means I should use the 4.03.605.1? And the newest radio will automatically still be on there from the OTA update, or will I have to flash those as well? I have no experience in flashing radios so this is new ground to me.
Click to expand...
Click to collapse
That QA is outdated.
It was referring to using the 3.14.605.07 kernel as opposed to the then-most-recent 3.14.605.10
Back then those two builds were similar enough that they could mix n match without issues.
Between 3.14.605.12 and 4.03.605.1 is a lot of changes. (whole number change to represent it) Specifically, new hboot and radios. Therefore, it is incompatible with the older kernels.
When you're S-ON you can't touch the radios except through an official RUU.
Even with s-off I doubt you can flash radios from recovery (not sure on this one), and NeoMax doesn't have any radio files anyway. (nor does any rom I know for this phone)
If you haven't yet updated to 4.03.605.1 then I recommend that you stay on 3.14.605.12 until Neo updates the ROM.
If you already updated, it is still possible to run NeoMax. You just have to manually flash the new 4.03.605.1 kernel after installing the ROM.
Sent from my NeoMax Rezound
This AM I was:
S-ON
HBOOT: 1.19
Running a version of Fresh
11PM I am:
S-OFF w/ DirtyRacun
HBOOT 1.15.2222
Radio 1.05.11.0606
I have access to Bootloader & I have TWRP 2.4.1.0
I have reformatted internal SDcrd, and I've reformatted internal memory
The phone is blank besides Bootloader and TWRP
Any ROM's I attempt to flash "FAILS"
My attempts at flashing a kernal has been dubious.. I don't know what I'm doing on the kernal front.
Is there a plain Jane Rom out there that will load every time? I'm just not sure where to go from here.
2/20/13 Comment - I forgot to mention, after achieving S-Off with Racun, the phone was basically stock, so I re-rooted with 1.22_RUU_PLUS_ROOT which seemed to flash with no problems and install TWRP. It was at this point I tried to flash (over confidently, I did not make a backup) fresh-evo-lte-5.3.1. The Flash never made it through the process, and restarted. There's where it sits. Now all Rom's very quickly start to flash then, "Fail."
Ffej4ord said:
This AM I was:
S-ON
HBOOT: 1.19
Running a version of Fresh
11PM I am:
S-OFF w/ DirtyRacun
HBOOT 1.15.2222
Radio 1.05.11.0606
I have access to Bootloader & I have TWRP 2.4.1.0
I have reformatted internal SDcrd, and I've reformatted internal memory
The phone is blank besides Bootloader and TWRP
Any ROM's I attempt to flash "FAILS"
My attempts at flashing a kernal has been dubious.. I don't know what I'm doing on the kernal front.
Is there a plain Jane Rom out there that will load every time? I'm just not sure where to go from here.
2/20/13 Comment - I forgot to mention, after achieving S-Off with Racun, the phone was basically stock, so I re-rooted with 1.22_RUU_PLUS_ROOT which seemed to flash with no problems and install TWRP. It was at this point I tried to flash (over confidently, I did not make a backup) fresh-evo-lte-5.3.1. The Flash never made it through the process, and restarted. There's where it sits. Now all Rom's very quickly start to flash then, "Fail."
Click to expand...
Click to collapse
try downgrading TWRP. Some ROMs aren't compatible with the latest release. The Dev has to bake something in the ROM. Version 2.3.1.0 seems to be the "sweet spot". Get it here. Since you're s-off just use the "Download - Bootloader Method:" make sure you rename it to PJ75IMG.zip and place it on the root of your EXTERNAL sdcard.
Similar Issues
I have a similar issue as the OP. I've looked around, and to avoid created a new thread, I'm going to pseudo-bump this into a new topic.
S-ON
HBOOT: 2.09
Running TWRP 2.6
Radio 1.13.11.0830
When stock, I was on 3.17 baseband. I saw that DirtyRacun was had the capability to unlock it, and they (If I read correctly) completely abandoned windows. MeanBean is on 3.16. I'm not adverse to Linux, but I have no idea how to use it past the GUI, and I don't want to install another OS to do something that should be accomplish able on the regular PC.
I have tried DirtyRacun, FacePalm, and Moonshine to get S-Off, no avail on any front unless I'm doing it wrong, which is completely possible.
I have access to Bootloader & I have TWRP 2.6.3.0
I have reformatted internal SDcrd, and I've reformatted internal memory
I am running Mean Bean due to its interesting method of installation, separating the Rom from kernel.
Any other ROM's I attempt to flash "FAILS"
I have flashed a kernel but no ROM I try will install regardless of my attempts. I have used Flash Image GUI from the Play store, but it doesn't seem to help any.
The only reason I am still trying to get a different ROM, MeanBean has no audio. Granted, it plays Pandora, but it has no ringtones, cannot install Amazon MP3, Cannot use Zedge (Crashes every time, not even FC), and cannot see my SD card to use manually loaded music. So I have no music or notification capabilities. No alarm, no text, nothing but the stock ringtone and I think a default e-mail that works about half the time. It also has no loaded sounds, so I cant even set any of the stock ones, which I could suffer until I get the Nexus 5. My Phone, like most people, is my alarm and my life line, so... I really wanna get it back in shape. I appreciate any and all help! I already got help getting out of Limbo once, now I just need one more little piece of info to get comfy again.
Part of your issue is that you're S-on, and you really need to be S-off (fairly simple using the newest Rumrunner method, which is Windows friendly).
As far as MeanBean, I'm not quite sure why you're having those issues with audio, as I and countless others have used that same ROM and have not encountered those issues. What other ROM's have you tried to flash?
Take a look at the top link in my sig. It has some useful info which hopefully you'll find helpful.
If you continue to have issues after exhausting all efforts, shoot me a PM.
Sent from my HTC EVO 4G LTE
I had been running CM10.0 for a while when it decided to lose my internal SD card. I think it has somethin gto do with TWRP and unmounting/remounting sdcards. In any case... I decided to flash CM10.1 just because it would be something to do and maybe it would solve the problem.
It got stuck at the splash screen.
I flashed back to CM10.0 and cleared cache/dalvik and got the same result. At this point I was S-On.
I re-locked and RUU'd. Everything seemed to work fine (including the sdcard issue). Sweet .
I unlocked it (HTC-Dev), flashed TWRP 2.4.4.0, flashed CM10.1 and it gets stuck on the splash screen.
Long story short, I RUU'd and updated everything OTA (1210 radio, etc).
I then used dirty Racun (with Baby Racun) and wen't S-Off.
This put me at 2.09 (was there already) and radio 1119, with S-Off.
I then flashed TWRP 2.4.4.0 again...
So ....
I'm S-Off, Unlocked, Radio 1119, HBoot 2.09, 3.15.651.16...
If I flash CM10.1, then Gapps from 20130312 I still get stuck at the cm boot screen. Same thing happens with the latest nightly, the M2 and the 10.0 that I was running before.
Any ideas? I've serached the forum (the best I could... I can't get any results unless I try to make a thread and just take a look at the "related results" it comes up with)...
I just tried flashing the boot.img from the CM10.1 nightly through fastboot directly and nothing doing. Same issue.
So I was in the middle of running the RUU found at unlimited.io here --> (Won't let me post a URL yet... The 2.09 RUU anyway...) which I've done a few times during this project to get back to a stock ROM. I just do a few of the middle steps starting with locking the device and it happened to reboot into the OS instead of fastboot this time when I locked it...
And it booted into CM10.1...
WTH?
Well whatever... Anyway...
I'm going to make a backup and then try to unlock (HTC Dev token) the recovery and then if that works I'll be good to go...
Weird...
I know this is a little late, but did you try flashing another ROM besides CM? It shouldn't matter, really...just a thought.
How long were you stuck at the boot animation? Did you try using an older twrp?
Sent from my EVO using xda premium
Thank you for the reply...
Once I got into CM10.1 I realized I couldn't send texts... so I messed around with APN's etc, and finally came across an "error 16..." thread that indicated that my phone had been newly locked out of the sprint network due to the S-Off state. So I called Sprint and had that solved in a few moments...
But I had already RUU'd and updated everything to stock, S-Off, re-locked...
So I thought "Sweet... now that I know what that solution is I'll go for CM10.1 again..."
Now I'm stuck at the boot screen again . I tried what seemed to have worked before (fastboot oem relock) and that doesn't seem to have done the trick this time.
Still kicking at it though .
To answer you questions... I tried TWRP 2.4.4.0 and TWRP 2.3.1.0, and as far as how long it sat in the boot animation... I left until the battery died once...
Ok, so long story short, I got fed up with the latest update (4.05.605.14) downloading onto my phone and then failing every time it tried to install itself. Deferring didn't work and it would do it about 5 times a day. So I decided to try and manually install it. That was a mistake, as I think I used a method that was for S-Off instead. I ended up with a phone that wouldn't boot past the 4G LTE screen. I have searched the forums all day and tried everything I could, including trying to install the 3.14.605.12 RUU to take me back to stock. Even locked I can't get it to flash. It checks the PH98IMG.zip but when it installs it fails and says that the "Main Version is older!" So at this point I'm lost. If any of you have any ideas and can help me get my phone back it would be so great.
Thanks in advance.
S-On
Locked
HBOOT: 2.28.0000
Radio: 2.2310.0123r/2.23.10.0124r
Recovery Amon Ra 3.14
You might just need to flash the proper kernel. Pull the boot.img from the ROM based on the OTA (linked below) and flash it and see if that does it. s-off phones don't need to flash kernel separately.
fastboot flash boot boot.img
http://forum.xda-developers.com/showpost.php?p=40949419&postcount=11
no boot
Here on xda is Hassoon's Rezound All-In-One kit #3.2.
It has a tool to set main version for you. And more.
Do it in Fastboot.
michaelbsheldon said:
Here on xda is Hassoon's Rezound All-In-One kit #3.2.
It has a tool to set main version for you. And more.
Do it in Fastboot.
Click to expand...
Click to collapse
Is that going to work for an RUU? The RUU will want to actually change the hboot version to an older one.
I think I saw an RUU feature in Hassoon's Rezound Toolkit as well.
You can always flash just a radio or hboot later if you want.
It does have a Mainver Error Fix listed so it would be worth a try. Also downloading the kernel to try and flash that. Thank you both for the suggestions. Hopefully they keep coming in because I've tried about everything I've seen in the forums to date...
well neither of those worked. The all in one couldn't even find the phone. Guess I severely borked it... :crying:
borkness
Gonna be a lot of work, but you may have to re-educate your phone with
RUU 3.14.xxxx.xx.
After that, install AmonRa recovery. Then mebbe a custom rom or your old nandroid backup.
That's all assuming you can get into fastboot-usb.
I have no problem getting into fastboot usb. It's about the only thing I don't have a problem with. How does one reducate a phone?
There's no RUU that you can run since you have a newer hboot than all of them.
Try flashing the ROM linked in my post #2 above. It's stock based on the OTA. That worked for someone else who was having issues with other methods. Flash the boot.img after you flash the ROM.
Yep
What Feralicious said...
This might help
kirkman81 said:
Ok, so long story short, I got fed up with the latest update (4.05.605.14) downloading onto my phone and then failing every time it tried to install itself. Deferring didn't work and it would do it about 5 times a day. So I decided to try and manually install it. That was a mistake, as I think I used a method that was for S-Off instead. I ended up with a phone that wouldn't boot past the 4G LTE screen. I have searched the forums all day and tried everything I could, including trying to install the 3.14.605.12 RUU to take me back to stock. Even locked I can't get it to flash. It checks the PH98IMG.zip but when it installs it fails and says that the "Main Version is older!" So at this point I'm lost. If any of you have any ideas and can help me get my phone back it would be so great.
Thanks in advance.
S-On
Locked
HBOOT: 2.28.0000
Radio: 2.2310.0123r/2.23.10.0124r
Recovery Amon Ra 3.14
Click to expand...
Click to collapse
Hi, I had similar issues. ROM and Kernel weren't matching. See this thread where I got some great help. Hopefully it gets you on your way too.
http://forum.xda-developers.com/showthread.php?p=41261391&posted=1#post41261391
Thanks for the suggestions, all. I had to switch phones finally because nothing was working but I'll give the last two suggestions a try when I have some time. I'll let you know if anything worked.
Sent from my DROID BIONIC using xda app-developers app