Help Programming Code

[Droidula]

Do any of the steps in the "turn your phone into..." thread alter the ability for your phone to use programming codes? Lately I have noticed an issue again with a lost signal for a short period of time. My texts take a while to go through. I recently tried calling my phone when I noticed this, and the phone didn't ring and went straight to voicemail. This is similar to the error many of us used to get, it just lasts for a shorter amount of time and isn't as bad. At the same time, I don't want to be missing calls at all. I had VM refresh my services and all that, but when I went to do the ##847446# code, nothing happened. I'm wondering if I should replace my phone while it's under warranty, or if it's something else. According to the rep, there are no network issues in my area.

 

[remanifest]

I used service codes with no problem, though I'm not sure what ##847446# does, and don't want to try unless I know...

 

[Droidula]

It's for the activation menu.

 

[remanifest]

What radio are you using? I just did that code and nothing happened here either. It seems weird to need to access the activation menu if your phone is already activated?

 

[Droidula]

Yeah but I guess if they refresh your services sometimes, they also want you to power cycle and and go through the activation again. My radio is: 0.97.10.0530

 

[remanifest]

Maybe try a different radio, 0.97.10.0808 and 1.09.00.0706 seem to work well for a lot of people.

Index of /shooter/radio is a working link to get the radios - also get the wimax installed after the radio if you do the 0.97.10.0808 radio

Index of /shooter/wimax/29047

 

[Droidula]

That's a good idea, maybe I'll try a different radio. I wonder if those will make a noticeable difference. Would you know where to check what wimax...version? is currently installed as well? Thank you for the suggestion, and the links.

 

[remanifest]

No problem, if you go into a terminal emulator on your phone, and type this:

[HIGH]su
wimax_mtd[/HIGH]Read the line that says Check Firmware Version - you're looking for the number in the parentheses - the version is the last part (mine is 29047 for example).

You can also do this from adb (hook your phone up to the computer with a USB cable), then do:
[HIGH]adb shell
wimax_mtd[/HIGH]

 

[Droidula]

Got it, thank you!

 

[OverByter]

A lot of custom roms install a different dialer, if you go into the app drawer and choose the phone alot of times the stock dialer is accessible along with the dialer codes.
OB

 

[Droidula]

That's a good tip, but I'm currently on stock, so no custom dialers here.

 

[Droidula]

Maybe try a different radio, 0.97.10.0808 and 1.09.00.0706 seem to work well for a lot of people.

Index of /shooter/radio is a working link to get the radios - also get the wimax installed after the radio if you do the 0.97.10.0808 radio

Index of /shooter/wimax/29047

I didn't want to mess with wimax right now so I was going to try flashing the .0706 one first. But when I flashed hboot 1.04 before changing the radio, my phone boot-looped, so I had to flash back to 1.57. I'm not sure why that's happening, but do I need to be on hboot 1.04 to flash the .0706 radio, or will it work on 1.57 too? I thought 1.57 is VM anyway- is the .0706 the latest VM radio? If so, it should work, right?

Edit: I also just booted into recovery, and saw that after I flashed back to hboot 1.57 my bootloader is locked again?

 

[Droidula]

Update: When I flash the 1.57 hboot from here it locks the bootloader, but I downloaded it from here instead, and now it says "Juopunutbear" in the bootloader screen. But, it still won't flash a radio.

 

[Brian706]

Your bootloader version (i don't think) will prevent you from flashing a radio. Are you s-off?
How are you flashing the radio? Needs to be done through the bootloader not recovery and should be named PG86IMG.zip.

 

[Droidula]

Yes, I'm s-off. The first thing I tried was changing my 1.57 hboot to 1.04, to flash the radio (this thread said that you should be on hboot 1.04 to flash them). I did it through the bootloader, using the PG86IMG file. It flashed, but after that my phone wouldn't load up, just kept looping. So I switched back to 1.57, downloaded from this link. When I went back to the bootloader, it no longer said unlocked. I tried to re-flash the radio I already have, .0530, because I read if you switch ROMs, sometimes it helps just to reflash the radio. But it wouldn't flash. I then downloaded the Juopunutbear hboot 1.57 from the website, and it flashed back. But when I tried to again re-flash the radio I already have, I believe it said "CID incorrect." So that's where I'm at now...I'm not sure if my bootloader is unlocked or not anymore?

 

[Brian706]

Hmmm weird. Are you sure you weren't already locked? How soon ago did you get s-off? When you do the wire trick it turns your bootloader back to locked. That won't affect a radio flash though.

I have never been on hboot 1.04. Many people flash radios from the stock hboot.

Try downloading the radio from my thread here:
http://androidforums.com/cdma-evo-3d-all-things-root/648902-radios-hboot-firmware-all-downloads.html

All of them are specified to work with Evo 3d and Evo V so you shouldn't hit any CID errors with those ones. I made them myself so I know that they are CID'd for both devices.

Also in that thread, if you click show, there is some tips and stuff for flashing PG86IMG.zip files. The reason you hit a boot loop must have been because of a compatibility issue with your current rom and the new hboot.

 

[remanifest]

That is really odd behavior...

When you're in recovery, does it confirm S-OFF?

If so, I would start from the beginning of this guide, and work all the way through:

http://androidforums.com/evo-v-4g-a...ng-turning-your-phone-into-evo-3d-thread.html

From there, you should be able to do anything you want without a hitch.

 

[remanifest]

Also if you would like help troubleshooting this over IRC or Teamviewer just let me know. IRC channel is chat.freenode.net #oudhitsquad - Teamviewer I'll PM you if you want to do that route.

 

[Droidula]

When you're in recovery, does it confirm S-OFF?

If so, I would start from the beginning of this guide, and work all the way through:

http://androidforums.com/evo-v-4g-a...ng-turning-your-phone-into-evo-3d-thread.html

It does confirm s-off. I originally went back to that guide, and that's where I got the .0530 radio from again, which won't flash now.

Hmmm weird. Are you sure you weren't already locked? How soon ago did you get s-off? When you do the wire trick it turns your bootloader back to locked. That won't affect a radio flash though.

I have never been on hboot 1.04. Many people flash radios from the stock hboot.

Try downloading the radio from my thread here:
http://androidforums.com/cdma-evo-3d-all-things-root/648902-radios-hboot-firmware-all-downloads.html

All of them are specified to work with Evo 3d and Evo V so you shouldn't hit any CID errors with those ones. I made them myself so I know that they are CID'd for both devices.

Also in that thread, if you click show, there is some tips and stuff for flashing PG86IMG.zip files. The reason you hit a boot loop must have been because of a compatibility issue with your current rom and the new hboot.

I did s-off back in October. I don't remember for certain, but I don't recall seeing it say "locked" in the bootloader screen after that, until now. However, I flashed a bunch of ROMs after that, and never had a problem. I haven't used the bootloader, recovery, or anything else in a while though, as I was happy with my phone. I flashed back to jmz stock (link doesn't seem to be there anymore), if that makes a difference? I think I used odex.

I will try the radio from your thread when I get back home and in front of my computer.

Also, could it just be that I can't change my hboot or flash this radio from the jmz stock ROM? I found this from Leslie Ann in another thread:

The stock roms cannot handle Hboot changes.
If you change the hboot, flash the radio and PRI, then go back to the original hboot it will work.

 

[Droidula]

Also if you would like help troubleshooting this over IRC or Teamviewer just let me know. IRC channel is chat.freenode.net #oudhitsquad - Teamviewer I'll PM you if you want to do that route.

Thanks so much. I'm not going to be in front of the computer in a few minutes, but if I can't figure this out later when I get back, that could be helpful. I appreciate it!

 

[Droidula]

Brian706, I flashed the .0706 radio from your thread that you linked; it flashed, no bootloop. So maybe I just can't change hboots (or, change to the particular ones I tried, anyway) with the stock ROM that I'm on. Still not sure why it wouldn't let me re-flash the original radio that I already had, though. But hopefully the one I flashed will resolve the issues I've been having, we shall see. If not, I will try to flash back to the other radio. Thank you both so much for the help!

 

[Brian706]

It does confirm s-off. I originally went back to that guide, and that's where I got the .0530 radio from again, which won't flash now.
I did s-off back in October. I don't remember for certain, but I don't recall seeing it say "locked" in the bootloader screen after that, until now.

Ahh... I think I know why. When you go s-off, it does return the bootloader to LOCKED. But you probably installed the custom hboot after s-off. So it probably read Juopunut Bear at the top. Then when you changed hboots, it displayed LOCKED because the Juopunut Bear hboot was gone and along with it went the custom text that it displayed.

Brian706, I flashed the .0706 radio from your thread that you linked; it flashed, no bootloop. So maybe I just can't change hboots (or, change to the particular ones I tried, anyway) with the stock ROM that I'm on. Still not sure why it wouldn't let me re-flash the original radio that I already had, though. But hopefully the one I flashed will resolve the issues I've been having, we shall see. If not, I will try to flash back to the other radio. Thank you both so much for the help!

Yeah, the most likely reason for the bootloop was that the hboot you flashed just wasn't compatible with the rom you were on. It happens to people a lot when they switch hboots. I have posted instructions for changing hboots and avoiding bootloops in the post you got the radio from.

Glad it's working!!

 

[Droidula]

Ahh... I think I know why. When you go s-off, it does return the bootloader to LOCKED. But you probably installed the custom hboot after s-off. So it probably read Juopunut Bear at the top. Then when you changed hboots, it displayed LOCKED because the Juopunut Bear hboot was gone and along with it went the custom text that it displayed.




Yeah, the most likely reason for the bootloop was that the hboot you flashed just wasn't compatible with the rom you were on. It happens to people a lot when they switch hboots. I have posted instructions for changing hboots and avoiding bootloops in the post you got the radio from.

Glad it's working!!

Initially, I used the hboot in Leslie Ann's thread, but soon after changed it to 1.57. I don't remember it saying locked after that, but I can't be sure. It said Juopunut only yesterday, after I was trying to figure out why I couldn't change my hboot and radio. But yes, so far the radio I flashed yesterday seems a bit more stable, so I'm happy. Thanks again.

 

[remanifest]

When you go s-off, it does return the bootloader to LOCKED.

Do you know of any way to unlock the bootloader again? When I try to go through the steps, i.e. fastboot oem get_identifier_token the only thing that is returned now is this:

[HIGH]~$ fastboot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.006s]
finished. total time: 0.006s
[/HIGH]This happens in both Linux and Windows. I'm thinking it's because I no longer have the "oem" HBOOT?

 

[Brian706]

Do you know of any way to unlock the bootloader again? When I try to go through the steps, i.e. fastboot oem get_identifier_token the only thing that is returned now is this:

[HIGH]~$ fastboot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.006s]
finished. total time: 0.006s
[/HIGH]This happens in both Linux and Windows. I'm thinking it's because I no longer have the "oem" HBOOT?

Are you on a stock hboot? If you flashed an engineering hboot or patched hboot I don't think it will work. You can actually use the same token to unlock again but you have to be on a stock hboot to flash it.