So I was running CM10 and decided to jump from stable to the latest nightly. After doing that I couldnt get any calls out or connect to either cdma or lte. So I figured I would go back to stock and wiped and put RUU 2.13 on, but I still have the same problem. Called sprint, they tried refreshing network services and no dice. I just want to have a working phone again, can anyone give me a hand or some ideas to try?
Here's where the phones at:
RUU: 2.13
s-on
Hboot 1.19
Radio 1.12.11.0809
Phone wont update prl or profile. I have the MSL and tried manually inputting my phone number and msid but when i hit commit changes it said it failed.
Next thing I was going to try is downgrading the hboot back to 1.12 then flashing an older ruu, but at this point I'll try anything.
EDIT: I resolved the issue using DirtyRacun s-off.
http://unlimited.io/dirtyracun.htm
Related
Hey guys, i updated my Evo 3D with the OTA update that's posted in the development section. Now everything is fine except I don't have WiFi. My Wifi just says error...doesn't even try to start.
I tried to use the RUU to downgrade back to shipped/stock ROM but it gives me the 140 Invalid bootloader error. This is because the hboot got upgraded to 1.40 from 1.30. I am assuming to go back to the original shipped ROM, I need to downgrade hboot back to 1.30.
Any ideas? I've created a Goldcard also and tried to apply the OTA update using that, but I get some "invalid operations.....boot successful" error and it doesn't even update anything...just reboots. I'm not sure if I created the goldcard correctly or whats going on. But right now I have no Wifi and I'm out of country so I have no cellular data either and I can't go to Sprint store either.
Please help!
Is anyone else having a problem updating your PRI after flashing the ENG bootloader? I remember having this issue with my Evo 4G and the ENG bootloader. I have tried both the RUU and stock.zip and still at PRI Version 1.15_003. My OCD is currently at high alert.
nunyabiziz said:
Is anyone else having a problem updating your PRI after flashing the ENG bootloader? I remember having this issue with my Evo 4G and the ENG bootloader. I have tried both the RUU and stock.zip and still at PRI Version 1.15_003. My OCD is currently at high alert.
Click to expand...
Click to collapse
i'm completely stock but have ran revolutionary so i'm on their hboot with a custom recovery.
my PRI version is 1.15_003 also ...
i do remember these issues on the EVO and it was essential due to lack of a full update being released by HTC/Sprint. In their OTA files and RUU files we were usually only given pieces of the update which generally lacked and updated PRI.
hope we aren't having those same issues with the EVO 3D!
It looks like it might be better to update to the latest RUU/OTA before rooting or s-off. My other evo 3d took the ota update before rooting so it does have PRI version 16.
Ever since i've updated to the 1.24_003 PRI, ive had terrible service even with my airave in the house... constantly roams and when it does go on sprint signal, its on 1x with 1 bar never more in places where i used to get perfect full bar 3G. Tried flashing diff radios, updated profile, updated PRL... nothing seems to work. If anybody knows where i could get my hands on the 1.15_003 please shoot me a PM and HELPPPPPPPPPPP! lol
Try this if you haven't already.
Open up your stock dialer and dial
##3382#
Then select edit when the menu appears.
Then enter your msl number.
Then select data profile.
Then select automatic if its not already selected.
Then press menu and select commit/save changes.
Then another window will appear stating that your phone will reboot in 10 seconds or you can select ok and reboot the device Manually. At this point just waiit the 10 seconds.
When the phone is rebooted check and see how your signal and data are then.
I'm not sure if this will help your issue or not but I think its worth a shot.
Also you have to have your msl. If you don't you can call sprint and request it which IMO is the difficult way of obtaining it or if your rooted you can download an app called msl reader from the market for free and it will give you your msl in like 20 seconds. I hope this helps.
Locked & Loaded
" Shooter on Deck "
So i had to take my phone in because my radio died and could not get cell reception. And of course they had to give me a hboot 1.50. So i used the downgrade trick and got it to 1.40 which of course security flagged the phone. No problem I flashed the 1.13.651.7 OTA/RUU exe and the phone booted up ran revolutionary on it and unlocked the bootloader flashed 1.04 and installed recovery. Everything was going swell. Updated the radio to 1216 and tried out a ICS ROM and phone would shut off some times when i hit the power to turn it on and it would reboot. tried a few ics roms got same results. so tried out some of the 2.08.651.2 roms and it still would reboot randomly. now im ticked. So i flash the 0.97.10.0808 no hboot it flashes more then just the radio but radio 2 and some other things and use the 2.08.651.2 steel rom and no more reboots. I was going on 8 hours with no reboots with 0808. so i figure maybe its fixed now so i put the 1216 radio back on and phones rebooting like clockwork every 20 mins or so. If i did not love this thing it would be bouncing off the walls right now. Of course ive not changed the rom back to a ICS one yet. but any ideas what the heck is going on?
Thanks in advance
Stealthee
Anybody with any idea on this ? There was one other thread started on this and no one answered or put in input on it either.
I had a similar issue with reboots after updating to that radio. I was only flashing the radio update. Freeza made a combo that updates a couple other bits and now I'm rock solid again. Here is the link to freeze'a thread:
http://forum.xda-developers.com/showthread.php?p=21374142
hope that helps if you're still having an issue.
TL;DR fixed it so that I could get on the VZW network but I can't update to the latest global firmware. My Baseband version is 2.22.100801r/2.22.10.0803r but the RUU won't run.
OK so I was getting horrible speeds (50kB/sec down) on neo's new ROM and I noticed that my radio/firmware wasn't matching (one ended in 21r and the other ended in 23r) so I decided to update the radio to the newest global by running the global RUU but it wouldn't run it just said "parsing" and then would bring me back to hboot. So I downloaded the latest firmware/radio combo from the combo thread in android dev and flashed it. I rebooted into the ROM and it said "baseband unknown" and wouldn't connect to cell or data, so I wiped data and rebooted then android.phone kept crashing, so I tried to run the firmware update again and it didn't change the radio. The RUU wouldn't run either. I tried flashing the radio partition using the radio.img from the RUU and it was successful but upon reboot the radio/firmware version didn't change.
I'm at a loss of what to do now.
I'm s-off, on hboot 2.27 and my radio version is 2.22.100801r/2.22.10.0803r
OpenDSP-v14.6.0.7708.00.0507
The radio image that I grabbed from that thread said that it was the latest and was from last month so I figured it was correct.
I'm in desperate need of help...
edit: I just relashed a ROM to get it so that it would boot to Android and it connected to 3G and the cell network so that's good and I'm back in business. The only remaining question is how can I get it updated to the current firmware?
brando56894 said:
TL;DR fixed it so that I could get on the VZW network but I can't update to the latest global firmware. My Baseband version is 2.22.100801r/2.22.10.0803r but the RUU won't run.
OK so I was getting horrible speeds (50kB/sec down) on neo's new ROM and I noticed that my radio/firmware wasn't matching (one ended in 21r and the other ended in 23r) so I decided to update the radio to the newest global by running the global RUU but it wouldn't run it just said "parsing" and then would bring me back to hboot. So I downloaded the latest firmware/radio combo from the combo thread in android dev and flashed it. I rebooted into the ROM and it said "baseband unknown" and wouldn't connect to cell or data, so I wiped data and rebooted then android.phone kept crashing, so I tried to run the firmware update again and it didn't change the radio. The RUU wouldn't run either. I tried flashing the radio partition using the radio.img from the RUU and it was successful but upon reboot the radio/firmware version didn't change.
I'm at a loss of what to do now.
I'm s-off, on hboot 2.27 and my radio version is 2.22.100801r/2.22.10.0803r
OpenDSP-v14.6.0.7708.00.0507
The radio image that I grabbed from that thread said that it was the latest and was from last month so I figured it was correct.
I'm in desperate need of help...
edit: I just relashed a ROM to get it so that it would boot to Android and it connected to 3G and the cell network so that's good and I'm back in business. The only remaining question is how can I get it updated to the current firmware?
Click to expand...
Click to collapse
try the full global ruu from android police or one from the roms that have it in their op! that should help, do you have a stock hboot or modified one?
brando56894 said:
TL;DR fixed it so that I could get on the VZW network but I can't update to the latest global firmware. My Baseband version is 2.22.100801r/2.22.10.0803r but the RUU won't run.
OK so I was getting horrible speeds (50kB/sec down) on neo's new ROM and I noticed that my radio/firmware wasn't matching (one ended in 21r and the other ended in 23r) so I decided to update the radio to the newest global by running the global RUU but it wouldn't run it just said "parsing" and then would bring me back to hboot. So I downloaded the latest firmware/radio combo from the combo thread in android dev and flashed it. I rebooted into the ROM and it said "baseband unknown" and wouldn't connect to cell or data, so I wiped data and rebooted then android.phone kept crashing, so I tried to run the firmware update again and it didn't change the radio. The RUU wouldn't run either. I tried flashing the radio partition using the radio.img from the RUU and it was successful but upon reboot the radio/firmware version didn't change.
I'm at a loss of what to do now.
I'm s-off, on hboot 2.27 and my radio version is 2.22.100801r/2.22.10.0803r
OpenDSP-v14.6.0.7708.00.0507
The radio image that I grabbed from that thread said that it was the latest and was from last month so I figured it was correct.
I'm in desperate need of help...
edit: I just relashed a ROM to get it so that it would boot to Android and it connected to 3G and the cell network so that's good and I'm back in business. The only remaining question is how can I get it updated to the current firmware?
Click to expand...
Click to collapse
Looks like you're on the latest firmware to me. Your baseband version and hboot are the newest
Oh OK thanks, I didn't know if that was the newest baseband because in Neo's new rage AOSP ROM he mentions that you should be on the newest firmware which he states is 1.22.10.0424r
If I am truly on the latest firmware then that makes complete sense as to why it won't upgrade
brando56894 said:
Oh OK thanks, I didn't know if that was the newest baseband because in Neo's new rage AOSP ROM he mentions that you should be on the newest firmware which he states is 1.22.10.0424r
If I am truly on the latest firmware then that makes complete sense as to why it won't upgrade
Click to expand...
Click to collapse
I believe he just meant the ICS original ota radios. I can't speak for him, however, the radios and hboot you have are all current, so you're good to go!
Hi all my phone is stuck on the 4G screen and won't boot up. I'm not sure what to do at this point. I've been in ra recovery and wiped and flashed and wiped and flashed some more. I'm stuck and need some help.
what rom are you on?
OK so I've tried googling and all that but this problem doesn't seem to be as common as the mainver is older issue.
Background:
Just sold the phone on swappa but I need to return to stock before I send it, hopefully tomorrow. I was s on running neo 1.7 before I got into this mess.
Issue:
I booted into recovery and did a factory reset. I then booted into hboot and did a factory reset there also. I think I then selected the wipe internal storage option. I then proceeded to relock the bootloader which I believe was successful since it says relocked now.
I have downloaded and tried flashing 3 different ICS RUUs by renaming them to the appropriate phxxx name and flashing them in hboot. It goes thru the process a little ways and then all of a sudden I get the "hboot is older" error and "update failed" message. My Hboot version is showing 2.27 which i believe is the newest one. I can't do anything and can't find a solution. I really need to figure out how to fix this asap so I can get the buyer his phone. All help is greatly appreciated!
It is impossible to downgrade HBoot without S-Off, so you will only be able to run an RUU with HBoot version 2.27 or higher (I believe that's either the ICS OTA or the Global leak - correct me if I'm wrong).
To get completely stock, i.e., stock firmware and Locked (as opposed to Relocked), you will need to get S-Off, then flash whatever RUU you want, then get S-On again.
However, just flashing any RUU - either the ICS OTA or the Global leak, and staying Relocked should be fine - many people receive used phones with custom ROMs and all, so an RUU would be a big step up from that (in terms of being as stock as possible).
EDIT: as LOBBS said (below), you will need to run the Global Leak RUU. That will get you on the latest leaked firmware / radios, which is probably the best anyway if you are selling the phone to the 'average', uninformed user (or to the informed user, for that matter). You will have Relocked bootloader.
Alternatively, you could get S-Off and then get on stock firmware / radios, Locked bootloader, and back to S-On, but I assume you won't want to bother to do all that just to sell the phone.
Hboot 2.27 is the global leak RUU 4.03.605.
Sent from my ADR6425LVW using xda app-developers app
Thanks fellas. I will try that one. I thought I had already but maybe I haven't. Let ya know what happens!
I flashed the global leak and all went well. Thanks for the quick help!