Related
Well I got myself into a real pickle here. I was trying to get the newer OTA with my unlocked rooted 3D I tried everything I have here on how to do it but now my phone just reboots itself after it get to the sprint screen sometimes it does make it to where is show the info bar at the top with the time but reboots soon after. I have tried a stock recovery and a new OTA RUU using hboot and the PG86IMG.IMG which did install at hboot but I still have the same issues. Any ideas on how to at least get back to normal?
mviars said:
Well I got myself into a real pickle here. I was trying to get the newer OTA with my unlocked rooted 3D I tried everything I have here on how to do it but now my phone just reboots itself after it get to the sprint screen sometimes it does make it to where is show the info bar at the top with the time but reboots soon after. I have tried a stock recovery and a new OTA RUU using hboot and the PG86IMG.IMG which did install at hboot but I still have the same issues. Any ideas on how to at least get back to normal?
Click to expand...
Click to collapse
What hboot are you ? Also what software are you on 2.08 ? You are CDMA I am guessing? If all else fails man boot into your recovery and wipe just not your SD card and go back to hboot relock your phone and use the latest 2.17 ruu exe.. Works every time and then root again and your set... This info is for CDMA only Not GSM>>>
THanks reaper. I was on hboot 1.5 and CDMA sorry for not stating. I ended up just taking it back to sprint and they gave me a new phone which I am actually happy about because of a few blemishes I had on the phone. I think I will wait till after ICS and see if they can get it rooted. I really only want the ability to wireless tether.
Again thanks for the reply
Is there anyway to reset the Rezound to the factory locked bootloader?
http://forum.xda-developers.com/showthread.php?p=25165453
Assuming you have done the HTC Dev unlock, you must do S-off and follow the guide here to get back to reading "Locked" and "S-on" simultaneously.
Edit: Ok, so I see you are S-off at the moment, you are going to want to backup all your data in your custom recovery if you haven't done so already (still on CWM or got that straightened out?)
Going to download the latest official RUU available (the GB OTA at the moment); here is a link to the GB OTA thanks to con247: http://forum.xda-developers.com/sho...uide to S-On to restore that too if you wish.
PhantasmRezound said:
http://forum.xda-developers.com/showthread.php?p=25165453
Assuming you have done the HTC Dev unlock, you must do S-off and follow the guide here to get back to reading "Locked" and "S-on" simultaneously.
Edit: Ok, so I see you are S-off at the moment, you are going to want to backup all your data in your custom recovery if you haven't done so already (still on CWM or got that straightened out?)
Going to download the latest official RUU available (the GB OTA at the moment) and have it handy; here is a link to the GB OTA thanks to con247: http://forum.xda-developers.com/showthread.php?p=22045045
Now make sure your bootloader is Locked before running the RUU. Check this and be certain; have to do a bit of extra work if it isn't, so please say you didn't Dev Unlock again after doing S-off lol. (I did this. Had to repeat the whole S-off process to achieve a "Locked" message ultimately. Not fun.)
Ok, after making sure bootloader is Locked... Running that RUU should put the stock hboot back on, verify that after the process. And remeber to turn USB Debugging back on in the stock ROM after running that RUU lol . Then proceed with the guide on the same computer you got all those Dev tools on from doing S-off.
Click to expand...
Click to collapse
If I remember correctly if it's a patched hboot and not the stock hboot your not supposed relock it because you can brick that way. Since the phone is S-OFF just running the GB RUU will be fine then just factory reset from hboot after the RUU finishes and your good to go. Also it's ok to keep it S-OFF because some phones come stock that way but if you really want you can run the command to get S-ON.
Sent from my ICS Rezound
LakerStar25 said:
If I remember correctly if it's a patched hboot and not the stock hboot your not supposed relock it because you can brick that way. Since the phone is S-OFF just running the GB RUU will be fine then just factory reset from hboot after the RUU finishes and your good to go. Also it's ok to keep it S-OFF because some phones come stock that way but if you really want you can run the command to get S-ON.
Sent from my ICS Rezound
Click to expand...
Click to collapse
Yes, this. Didn't mean to suggest actually trying to Relock your phone post S-off. That would definitely be bad if you accepted the JuopunutBear hboot or flashed the Engineer one instead of Stock hboot.
So in any case, you should go ahead and run the RUU after backing up data, do the factory reset, and follow through with turning the security flag to ON if you're wanting the full original state (though Verizon almost certainly won't check or care, and the next user mostly benefits from S-off)
((Sorry, I was just thinking how I jumped the whole gun the hour after JuopunutBear came out. Kept my stock hboot before anybody knew why the process was wanting to push that patched hboot to the phone lol. I used the Dev unlock procedure again *after* S-off. So, at this point I would have to do this process twice to get the same result, to first get a plain Locked status by running the RUU and doing the S-off procedure again... then RUU and do S-on too. Totally forgot those custom JB hboots will say "JuopunutBear" instead of whatever lock status it may be. Edited original post.))
PhantasmRezound said:
Yes, this. Didn't mean to suggest actually trying to Relock your phone post S-off. That would definitely be bad if you accepted the JuopunutBear hboot or flashed the Engineer one instead of Stock hboot.
So in any case, you should go ahead and run the RUU after backing up data, do the factory reset, and follow through with turning the security flag to ON if you're wanting the full original state (though Verizon almost certainly won't check or care, and the next user mostly benefits from S-off)
((Sorry, I was just thinking how I jumped the whole gun the hour after JuopunutBear came out. Kept my stock hboot before anybody knew why the process was wanting to push that patched hboot to the phone lol. I used the Dev unlock procedure again *after* S-off. So, at this point I would have to do this process twice to get the same result, to first get a plain Locked status by running the RUU and doing the S-off procedure again... then RUU and do S-on too. Totally forgot those custom JB hboots will say "JuopunutBear" instead of whatever lock status it may be. Edited original post.))
Click to expand...
Click to collapse
Cool I was just trying to help out lol.
Sent from my ICS Rezound
Picked a 3D up on CL, clean ESN, $50, I couldn't pass it up. In great shape, so I'm a couple weeks into this, read, read, read, and managed to get the wire trick to work on 1.58 so I'm S-Off. Now what?
I guess my main question is, I'm reading S-off trumps all, but how exactly does your HBOOT version affect what ROMs you can load? Is it tied to Kernel basically? Or the base the ROM works on?
This hasn't been so clear in my search education.
I'm running Trib's SolidROM ver 2.1, at the moment (which is stellar), but I'm a flashaholic in need of a fix every few days... and there are so many options, but I can't seem to see the forest for the trees...
Thanks in advance. This place rocks.
trouinky said:
Picked a 3D up on CL, clean ESN, $50, I couldn't pass it up. In great shape, so I'm a couple weeks into this, read, read, read, and managed to get the wire trick to work on 1.58 so I'm S-Off. Now what?
I guess my main question is, I'm reading S-off trumps all, but how exactly does your HBOOT version affect what ROMs you can load? Is it tied to Kernel basically? Or the base the ROM works on?
This hasn't been so clear in my search education.
I'm running Trib's SolidROM ver 2.1, at the moment (which is stellar), but I'm a flashaholic in need of a fix every few days... and there are so many options, but I can't seem to see the forest for the trees...
Thanks in advance. This place rocks.
Click to expand...
Click to collapse
Well there are very few rom's that are compatible with the 1.58 hboot so if your a flashoholic then you better off going to hboot 1.40 since with 1.40 hboot you can run both ICS & GB. GB has better compatibility in fact it can only play the 3d games and older gameloft games.
If you downgrade to a lower hboot please let me know how it went because I am thinking of upgrading to 1.58 to try out a new rom but I am afraid to because I am already s-off hboot 1.4.
trouinky said:
Picked a 3D up on CL, clean ESN, $50, I couldn't pass it up. In great shape, so I'm a couple weeks into this, read, read, read, and managed to get the wire trick to work on 1.58 so I'm S-Off. Now what?
I guess my main question is, I'm reading S-off trumps all, but how exactly does your HBOOT version affect what ROMs you can load? Is it tied to Kernel basically? Or the base the ROM works on?
This hasn't been so clear in my search education.
I'm running Trib's SolidROM ver 2.1, at the moment (which is stellar), but I'm a flashaholic in need of a fix every few days... and there are so many options, but I can't seem to see the forest for the trees...
Thanks in advance. This place rocks.
Click to expand...
Click to collapse
90% sure of the following information.
Roms that are based directly on the Sprint ICS OTA require 1.58, some roms have used some tricks to let it run on 1.50 like SolidROM did.
1.58 for you means u can flash any ROM and not bootloop.
S-OFF means u can flash a rom FULLY, some of these ROMS have custom Kernels, and without flashing the kernel u get bootloops. u can also add your own Kernel.
so in conclusion your in good shape. u can flash Gingerbread- VM ICS - sprint ICS.
just be sure to stay away from changing your HBOOT, especially any VM firmware!
Hboot 1.58: Can load the new ICS kernel and all sense ICS ROMs. Cannot load AOSP and GB ROMs.
Hboot 1.4 (and others): Can load most ROMs (sense with vm leak kernel, GB, AOSP). Cannot load the new ICS kernel (or any ROM with that).
hboot 1.5 s-off
How can I go back to my original hboot 1.5 s-off, the other day I flashed MeanROM ICS v2.6 and upgrade my hboot to 1.58, for the 2.89 kernel
I also try out SOS M | VER 2.6, and ZR3DX-Sense 3.6, wifi teather will not work on none of those roms, any one know how to get the teathering working. I'm thinking of going back to hboot 1.5 s-off any one know how to go back to 1.5 s-off.
cc2278 said:
How can I go back to my original hboot 1.5 s-off, the other day I flashed MeanROM ICS v2.6 and upgrade my hboot to 1.58, for the 2.89 kernel
I also try out SOS M | VER 2.6, and ZR3DX-Sense 3.6, wifi teather will not work on none of those roms, any one know how to get the teathering working. I'm thinking of going back to hboot 1.5 s-off any one know how to go back to 1.5 s-off.
Click to expand...
Click to collapse
Go to juopunutbear website and download hboot for GB. Rename to PG86IMG.zip and place at root of SD card. boot to boot loader. Select yes and then reboot. Don't forget to delete from SD card root!
Sent from my PG86100 using xda premium
plaidcounty said:
Go to juopunutbear website and download hboot for GB. Rename to PG86IMG.zip and place at root of SD card. boot to boot loader. Select yes and then reboot. Don't forget to delete from SD card root!
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
I'll try that thanks.
cc2278 said:
How can I go back to my original hboot 1.5 s-off, the other day I flashed MeanROM ICS v2.6 and upgrade my hboot to 1.58, for the 2.89 kernel
I also try out SOS M | VER 2.6, and ZR3DX-Sense 3.6, wifi teather will not work on none of those roms, any one know how to get the teathering working. I'm thinking of going back to hboot 1.5 s-off any one know how to go back to 1.5 s-off.
Click to expand...
Click to collapse
I answered you on the other place you posted this.
Read, Search, Read again, ... Then Ask with Tapatalk 2
plaidcounty said:
Go to juopunutbear website and download hboot for GB. Rename to PG86IMG.zip and place at root of SD card. boot to boot loader. Select yes and then reboot. Don't forget to delete from SD card root!
Click to expand...
Click to collapse
Thanks! This worked great. My research had me thinking the only way to do this was a ridiculously complex 15 step process.
I did the OTA update to ICS and hboot 1.58 and was trying to flash to PagePlus but ran into problems doing "APN Backup and Restore"; it's not allowed on ICS, I tried to go back to a gingerbread ROM but it kept bootlooping because I had hboot 1.58. Your advice got me back to hboot 1.50, then I installed an old cyanogenmod ROM, so I can do the APN backup.
JunoBear 1.50 s-off
4ext recovery
Mean ICS v2.6
Anthrax kernel 3.2.2
Radio 1.06.1216
Sprint CDMA
Problems:
Phone reboots randomly, even when in call
Phone freezes randomly
Holding down power button>power options> to restart> doesn't fully restart
getting a lot of roaming from home to work which never happened. Have to update prl back and forth from work to home which is annoying in itself.
What i have tried:
usually have to take battery out then can power back the phone on.
1.Wipe cache+dalvik, cache, dalvik cache
2.format system, data, everything, even sd card
3.tried superwipe
4. tried different roms MikVirgin 1.01, Mean ICS, Paranoid
5. tried different hboot eng 1.04, 1.40
6. tried the kernel with flashed rom, anthrax kernel, buttertoast
7. tried different variations with different roms,h-boot, etc.
Your radio is the problem. The ROMs and kernels you have mentioned on here run on the latest radio firmware. That the would explain why your phone freezes up when you try calling people and the random reboots are kernel and hboot incompatibilities. Heres a short list of what I mean.
Anthrax kernels can run on any hboot.
So can butteredtoast.
Most ICS roms can only run on hboot 1.58.00.00 or 1.58.5858
With the exception of zr3d Xl plus and viper3d.
All aosp ROMs can only be run on hboot 1.5 or lower.
All of these ROMs run on radio 1.09.0706
I would reccomend flashing this file to get you back on stock and on latest radios (1.09.0706 SPRINT 2.89)
http://forum.xda-developers.com/showthread.php?t=1193101
I reccomend you downloading this from your PC. Place it on the root of your sdcard and rename it PG86IMG in all caps. Insert the card back into your phone and power your into bootloader. When your phone detects the file, press the volume key up to start the update. Once finished, you can reflash your recovery, and then flash a ROM. Remember that ICS sense ROMs work with hboot 1.58 and Aosp ROMs works with 1.5 or lower. Good luck.
Jsparta26 said:
Most ICS roms can only run on hboot 1.58.00.00 or 1.58.5858
With the exception of zr3d Xl plus and viper3d.
Remember that ICS sense ROMs work with hboot 1.58 and Aosp ROMs works with 1.5 or lower. Good luck.
Click to expand...
Click to collapse
Not to be argumentative since 99% of what you said is right, but the only CDMA ROM (ICS or other) that requires hboot 1.58 is Coolexe's ROM. Viper doesn't anymore and the others never have. Some prefer certain radios and firmware though as you said.
If what jsparta said doesn't work, then I'd run the ruu.exe located in ramjet's thread http://forum.xda-developers.com/showthread.php?t=1889438 . It will put you back to stock but s-off still. All firmware, radios, etc will be updated. If phone runs fine stock, then flash hboot, custom recovery and custom ROM. When I had issues, this fixed it fit me.
thanks guys. i'll give both a try. hopefully it will fix the problems.
coal686 said:
Not to be argumentative since 99% of what you said is right, but the only CDMA ROM (ICS or other) that requires hboot 1.58 is Coolexe's ROM. Viper doesn't anymore and the others never have. Some prefer certain radios and firmware though as you said.
If what jsparta said doesn't work, then I'd run the ruu.exe located in ramjet's thread http://forum.xda-developers.com/showthread.php?t=1889438 . It will put you back to stock but s-off still. All firmware, radios, etc will be updated. If phone runs fine stock, then flash hboot, custom recovery and custom ROM. When I had issues, this fixed it fit me.
Click to expand...
Click to collapse
Wow I had no idea lol. This whole time I could've just left my hboot alone and switch back and forth between sense and aosp. Thanks coal that was very useful information. Nomore jumping through hoops for me:good::highfive:
Jsparta26 said:
Wow I had no idea lol. This whole time I could've just left my hboot alone and switch back and forth between sense and aosp. Thanks coal that was very useful information. Nomore jumping through hoops for me:good::highfive:
Click to expand...
Click to collapse
I haven't flashed an hboot since viper was fixed. I run 1.4 revolutionary all the time with no issues.
okay, i updated the radio to 1.09, but i'm still getting a reboots, even while in call. should i wipe dalvik cache or anything?
What ROM, kernel and hboot combination are you using?
Jsparta26 said:
What ROM, kernel and hboot combination are you using?
Click to expand...
Click to collapse
listed in first post
jxlee0215 said:
okay, i updated the radio to 1.09, but i'm still getting a reboots, even while in call. should i wipe dalvik cache or anything?
Click to expand...
Click to collapse
Did you try the ruu yet?
coal686 said:
Did you try the ruu yet?
Click to expand...
Click to collapse
i'm getting ready to try it today. i was giving it a day or so to see if the freezing problem was just a one time thing, but it turn out it's still doing it daily. And just today when my battery died, i charged the phone up, and powered it on, then it went into a boot loop.
any how for the ruu, is it necessary to relock the bootloader or can i just flash the ruu.exe?
update: i did the "fastboot oem lock" command, but output came up ...... <bootloader> Device was already locked!
my hboot screen shows
= JuopnutBear =
Shooter XC ship s-off RL
HBOOT-- 1.50.5050
Looking at your specs, it is not necessary to unlock or relock your bootloader being s-off. Your green lights to go ahead and run the ruu from your PC.
Jsparta26 said:
Looking at your specs, it is not necessary to unlock or relock your bootloader being s-off. Your green lights to go ahead and run the ruu from your PC.
Click to expand...
Click to collapse
just ran the ruu. bootloader relocked. however i can't seem to access htcdev.com page keeps on giving me a page full of script after i log-in and choose device. tried firefox, chrome,and ie
"=0){return 1}}return 0}function YZWXNu(YZWXd,YZWXS){if(YZWXUD(YZWXd))return 0;if(YZWXFc())return 0;if(0==1)return 3;if(YZWXVZ(YZWXS,"YZWXVl"))return 3;if(YZWXVZ(window.location.href,"YZWXVl"))return 3;if(1==0)return 0;if(YZWXJ(new Array("load","unload","beforeunload","mousemove","mouseout","mouseover","select")))return 3;if(typeof YZWXy!='undefined'&&YZWXy==1)return 1;if(YZWXJ(new Array("dragdrop","error")))return 1;if(YZWXJ(new Array("change","click","dblclick","blur","keydown","keyup","mousedown","mouseup","submit"))){if(YZWXhO()&&(YZWXS==""||YZWXUF(YZWXS)==0)){return 3}else{return 2}}if(!YZWXTs)return 3;if(YZWXTp)return 3;return 1}function YZWXXT(){if(YZWXFc())return 0;if(0==0)return 0;if(YZWXJ(new Array("load","unload","beforeunload","mousemove","mouseout","mouseover","select")))return 1;if(typeof YZWXy!='undefined'&............................................."
blah......it was the my pop up blocker.
okay. i relocked, ruu.exe, and unlocked the boot loader back. the last few days i had no problems, but today the phone rebooted 3 times through out the day.....didn't mess with the settings or anything. it was just laying there.
hboot revolution 1.40
radio 1.09
s-0ff
team dirt unofficial jellybean
can anyone help with this. i'm still getting reboots and freezing. i tried changing my hboot also to eng 1.04 but it didn't help. radio at 1.09
jxlee0215 said:
can anyone help with this. i'm still getting reboots and freezing. i tried changing my hboot also to eng 1.04 but it didn't help. radio at 1.09
Click to expand...
Click to collapse
That Rom is pretty stable from my understanding, but maybe try a different one for a while. Maybe one that is sense 3.6 based, like zr3dxl.
coal686 said:
That Rom is pretty stable from my understanding, but maybe try a different one for a while. Maybe one that is sense 3.6 based, like zr3dxl.
Click to expand...
Click to collapse
after a few weeks. i'm still getting reboots, freezes and shut down..now more frequent, 2-3 times a day. i did the shooter ruu and tried different roms. currently using Mean ics v2.6 what am i doing wrong?
Honestly, with the problems you're describing, it sounds like you need to flash back to stock and take it in to a Sprint repair center. I'm assuming all the freezes and reboots have been an ongoing problem?
Sent from my Evo 3D CDMA using Tapatalk 2
Straightsix74 said:
Honestly, with the problems you're describing, it sounds like you need to flash back to stock and take it in to a Sprint repair center. I'm assuming all the freezes and reboots have been an ongoing problem?
Sent from my Evo 3D CDMA using Tapatalk 2
Click to expand...
Click to collapse
that's not really an option. has a bad esn
Then, you're hosed. What you're describing with the freezes and reboots on multiple roms screams hardware issue and no about of flashing software is going to fix that.
Sent from my Evo 3D CDMA using Tapatalk 2
So I s-offed my wifes evo 3d a little bit ago, Afterwards I put the 1.04 hboot and CM 10.1 on her sd and flash them, Of course wiping in recovery because of the hboot flash, And it bootloops, So i'm like wtf, And I re-wipe, and re-flash. Still a bootloop, So I throw the sd in the pc and realize it corrupted so I format it, And throw back on the 1.04 bootloader and reflashed the rom, Still a bootloop,
So I run the ruu, It goes through, And boots back up so I'm like, Okay, Got it all taken care of.
So I flash the 1.04 bootloader once again and as i'm rebooting for the first time, bootloop. So, This is now seeming like a problem to me, Anyhelp? Ramjet maybe?
This is the same copy same download as the 1.04 bootloader that's running on my phone with CM 10.1 doing just fine.
Can't_Live_Without_My_Evo said:
So I flash the 1.04 bootloader once again and as i'm rebooting for the first time, bootloop. So, This is now seeming like a problem to me, Anyhelp? Ramjet maybe?
This is the same copy same download as the 1.04 bootloader that's running on my phone with CM 10.1 doing just fine.
Click to expand...
Click to collapse
Try the JBear 1.50.5050 hboot.
ramjet73
ramjet73 said:
Try the JBear 1.50.5050 hboot.
ramjet73
Click to expand...
Click to collapse
I'm currently running the RUU again trying to get it to at least boot stabily a time or two.
It's so weird seeing the stock boot animation boot loop lol.
Got it to boot, I feel a little better lol.
Is there a chance somethings seriously wrong? I tried 1.40 and 1.04 and both bootlooped.
ramjet73 said:
Try the JBear 1.50.5050 hboot.
ramjet73
Click to expand...
Click to collapse
Isn't that one GB?
Edit: After a ruu and a run through set up, I unchecked fastboot and checked usb debugging and then flashed the 1.50.5050 and it also bootloops.
What. The. Hell.
The only thing that'll boot up is stock.
Edit 2: So after the RUU I flash the 1.50.5050 you suggested, Bootloop as above stated, So I take out the sd and put the 1.58 stock hboot on it and flash that and it boots back up just fine. Which makes sense, But doesn't... ya know.
Edit 3: So I went to go unlock the bootloader on 1.58 and I'm on the "Unlock Bootloader?" screen, But I can't select yes, I know the dang power button works, I've pressed it 20 times, held it, it wont recognize, I also tried the camera button, don't work
I just tried to select no, and guess what, it'll work for that
Anyone ever seen this?
I unlocked it successfully like, 2 hours ago, with no effort at all. What. The. Hell.
Edit 4: Alright even though it wouldn't go through and reboot when hitting yes, and I even hit no to reboot it, I pulled the battery and went into the bootloader and it's unlocked.
So I wrote a recovery, I'm gonna make a back up of the stock rooted rom and see what we can't figure out here.
Okay, So it'll boot a custom rom on the 1.58 hboot. And I've made a backup of the stock rooted rom, I'm gonna try and flash the 1.04 again, and if it bootloops i'm gonna try and restore the backup of the stock rooted rom from the 1.58 hboot (Will that be a problem)
OKAY! Flashed the 1.04 hboot over Common-Sense (Thanks Turtle) and it finally booted up, Time to flash some jb goodness and hope we've got success.
Can't_Live_Without_My_Evo said:
Isn't that one GB?
Edit: After a ruu and a run through set up, I unchecked fastboot and checked usb debugging and then flashed the 1.50.5050 and it also bootloops.
What. The. Hell.
The only thing that'll boot up is stock.
Edit 2: So after the RUU I flash the 1.50.5050 you suggested, Bootloop as above stated, So I take out the sd and put the 1.58 stock hboot on it and flash that and it boots back up just fine. Which makes sense, But doesn't... ya know.
Click to expand...
Click to collapse
Sorry, I didn't realize that you were still on the stock ROM. As you found out, the only hboots that will boot that is 1.58 and JBear 1.58.5858.
The JBear 1.50.5050 hboot is a customized version of the latest Sprint GB bootloader and should boot everything that the engineering (ENG) 1.04 hboot does. I prefer to use that over the ENG version for day-to-day stuff since it's partition configuration is closer to the stock 1.58 hboot.
ramjet73
ramjet73 said:
Sorry, I didn't realize that you were still on the stock ROM. As you found out, the only hboots that will boot that is 1.58 and JBear 1.58.5858.
The JBear 1.50.5050 hboot is a customized version of the latest Sprint GB bootloader and should boot everything that the engineering (ENG) 1.04 hboot does. I prefer to use that over the ENG version for day-to-day stuff since it's partition configuration is closer to the stock 1.58 hboot.
ramjet73
Click to expand...
Click to collapse
I've got it working now, But I still don't understand the problem.
Everything worked fine except changing hboots.
The first time I flashed the hboot and then the rom without booting into anything and it boot looped, And I know 1.04 and JB work together.
The way I fixed it doesn't make sense to me either, But I'm not complaining about that.