Related
Hi!
I can't take credit for this solution... someone else posted it here, but I can't remember where or who this awesome person is. If that person sees this thread, please let me know so I can edit this post and give proper credit... because you're a life saver to anyone who wants to use DamageControl ROMs but needs MNS wired tether working.
I have posted this as a separate thread because this seems to be a hot issue which frequently comes up, and so many people don't search the forums well.
1. Completely wipe your phone in recovery. (Factory/Data, Dalvik, and SD Ext)
2. Install DamageControlv1.1beta5 and reboot after the install, verify in Settings>Software that your PRI is 2.11_002.
3. Reboot to recovery, wipe everything again (although you don't have to wipe SD-Ext, but you should always wipe Data/Factory and Dalvik) and install whatever ROM you want that doesn't usually allow MNS, such as the newest version of DamageControl.
4. Once you're up and running with the ROM of your choice, check to make sure your PRI is still 2.11_002.
5. Plug phone into USB and select Internet Sharing.
I have found that sometimes you have to plug it in a couple of times for the PC to authenticate, but I think that might be a PC issue of mine and not a phone issue.
I can verify that this method does enable MNS wired tether on DC v2.5 and DC v2.6. However, I am not sure if/what other side effects might come from having the 2.11_002 PRI. Market works for me still, Sprint Apps still work too, but there may be other things that don't like this PRI. For example (thanks Flipz for the clarification), PRL will not auto update with this PRI. But if the most important thing to you is MNS on a DamageControl ROM, then this is the way to go.
*Don't flash a ROM that automatically fixes your PRI though, or else all of the trouble you're going to will be undone!
Link to DamageControlv1.1beta5 which contains the PRI you need... http://forum.xda-developers.com/showthread.php?t=652564
ROMs that I can verify have MNS Wired Tether Internet Sharing working using this procedure
DamageControl v2.5
DamageControl v2.6
DarchLegend v5.0
I can confirm this works with DC 2.06, thanks for posting! I went from Flipz 2.0D with his proprietary PRI and MNS didn't work. I couldn't get MNS to work on DC2.06 or DarchLegend 5. My normal PRI is/was 1.70_003 which I understand is one of the culprits responsible for the error 67 message when trying to access MNS. MNS did work great with that PRI on DarchLegend 4.2.2 however.
With the new PRI I am back to the network being "unknown" and no Sprint designations on the lockscreen or task bar. Haven't tried any of the updates (PRL is currently at 60663) but I can update that manually by nandroiding back to a 1.5 rom.
Not sure what other evils may arise due to the new PRI but having MNS working is pretty awesome.
ive been gone for a while, and with all the drama i missed its hard to sift through a search. after trying all the new roms, i ended up with flipz pri. could someone point me to where i might be able to obtain the standard one?
i thankyou most kindly
The updated PRI sometimes breaks Sprint applications. We reverted to have Sprint show up as the carrier again.
sinistermeshes said:
ive been gone for a while, and with all the drama i missed its hard to sift through a search. after trying all the new roms, i ended up with flipz pri. could someone point me to where i might be able to obtain the standard one?
i thankyou most kindly
Click to expand...
Click to collapse
Well, flipz's pri I think is the same as 1.70_003, just renamed in the menu.
You could do the pri reset with your msl to get it back to 1.70_003 though
MrTrip said:
The updated PRI sometimes breaks Sprint applications. We reverted to have Sprint show up as the carrier again.
Click to expand...
Click to collapse
So far, so good with the new PRI. Market works, Sprint Nav works and everything else 'non-Sprint' works. I don't use TV, NFL, Nascar (uninstalled all of them anyway) but best of all, MNS works. I'll keep playing with it and update as neccesary.
Quick question, for MNS, would I have to use USB-tethering app?
pseudoremora said:
Quick question, for MNS, would I have to use USB-tethering app?
Click to expand...
Click to collapse
Unless you're talking about the default menu that pops up when you plug the phone into the computer via USB (the one that gives you four options - charge only, htc sync, disk drive, internet sharing), then no, there's no additional app to download or install in order to make this work. Should be native in any 2.1 ROM.
raynda said:
Unless you're talking about the default menu that pops up when you plug the phone into the computer via USB (the one that gives you four options - charge only, htc sync, disk drive, internet sharing), then no, there's no additional app to download or install in order to make this work. Should be native in any 2.1 ROM.
Click to expand...
Click to collapse
Oh ****, I should have realized that, the default menu. Thanks. There aren't any problems like the older versions of MNS (like on 1.5), where you have to try and beat the network connection so you can tether, right?
pseudoremora said:
Oh ****, I should have realized that, the default menu. Thanks. There aren't any problems like the older versions of MNS (like on 1.5), where you have to try and beat the network connection so you can tether, right?
Click to expand...
Click to collapse
not if you're using the wrong pri
it should work fine.
im curious if this method would work on fresh 2.0d... i know when you "flash" it your pri gets fixed, but what if you flashed DC, thus fixing your PRI and then restored the fresh 2.0d nandroid?
dmc971989 said:
im curious if this method would work on fresh 2.0d... i know when you "flash" it your pri gets fixed, but what if you flashed DC, thus fixing your PRI and then restored the fresh 2.0d nandroid?
Click to expand...
Click to collapse
That should work since the nandroid won't touch the PRI
abcdfv said:
That should work since the nandroid won't touch the PRI
Click to expand...
Click to collapse
fresh is by far the most stable daily rom for me plus i get crazy battery life out of it, the only thing its been missing is MNS... ill test this out tommorow and report back
raynda said:
Hi!
I can't take credit for this solution... someone else posted it here, but I can't remember where or who this awesome person is. If that person sees this thread, please let me know so I can edit this post and give proper credit... because you're a life saver to anyone who wants to use DamageControl ROMs but needs MNS wired tether working.
I have posted this as a separate thread because this seems to be a hot issue which frequently comes up, and so many people don't search the forums well.
1. Completely wipe your phone in recovery. (Factory/Data, Dalvik, and SD Ext)
2. Install DamageControlv1.1beta5 and reboot after the install, verify in Settings>Software that your PRI is 2.11_002.
3. Reboot to recovery, wipe everything again (although you don't have to wipe SD-Ext, but you should always wipe Data/Factory and Dalvik) and install whatever ROM you want that doesn't usually allow MNS, such as the newest version of DamageControl.
4. Once you're up and running with the ROM of your choice, check to make sure your PRI is still 2.11_002.
5. Plug phone into USB and select Internet Sharing.
I have found that sometimes you have to plug it in a couple of times for the PC to authenticate, but I think that might be a PC issue of mine and not a phone issue.
I can verify that this method does enable MNS wired tether on DC v2.5 and DC v2.6. However, I am not sure if/what other side effects might come from having the 2.11_002 PRI. Market works for me still, Sprint Apps still work too, but there may be other things that don't like this PRI. For example (thanks Flipz for the clarification), PRL will not auto update with this PRI. But if the most important thing to you is MNS on a DamageControl ROM, then this is the way to go.
*Don't flash a ROM that automatically fixes your PRI though, or else all of the trouble you're going to will be undone!
Link to DamageControlv1.1beta5 which contains the PRI you need... http://forum.xda-developers.com/showthread.php?t=652564
ROMs that I can verify have MNS Wired Tether Internet Sharing working using this procedure
DamageControl v2.5
DamageControl v2.6
DarchLegend v5.0
Click to expand...
Click to collapse
ugh the link for the 1.6.2 recovery in your signature is for the GSM hero! i flashed that to my phone by mistake took me forever to figure out what was going on.
raynda said:
Hi!
I can't take credit for this solution... someone else posted it here, but I can't remember where or who this awesome person is. If that person sees this thread, please let me know so I can edit this post and give proper credit... because you're a life saver to anyone who wants to use DamageControl ROMs but needs MNS wired tether working.
I have posted this as a separate thread because this seems to be a hot issue which frequently comes up, and so many people don't search the forums well.
1. Completely wipe your phone in recovery. (Factory/Data, Dalvik, and SD Ext)
2. Install DamageControlv1.1beta5 and reboot after the install, verify in Settings>Software that your PRI is 2.11_002.
3. Reboot to recovery, wipe everything again (although you don't have to wipe SD-Ext, but you should always wipe Data/Factory and Dalvik) and install whatever ROM you want that doesn't usually allow MNS, such as the newest version of DamageControl.
4. Once you're up and running with the ROM of your choice, check to make sure your PRI is still 2.11_002.
5. Plug phone into USB and select Internet Sharing.
I have found that sometimes you have to plug it in a couple of times for the PC to authenticate, but I think that might be a PC issue of mine and not a phone issue.
I can verify that this method does enable MNS wired tether on DC v2.5 and DC v2.6. However, I am not sure if/what other side effects might come from having the 2.11_002 PRI. Market works for me still, Sprint Apps still work too, but there may be other things that don't like this PRI. For example (thanks Flipz for the clarification), PRL will not auto update with this PRI. But if the most important thing to you is MNS on a DamageControl ROM, then this is the way to go.
*Don't flash a ROM that automatically fixes your PRI though, or else all of the trouble you're going to will be undone!
Link to DamageControlv1.1beta5 which contains the PRI you need... http://forum.xda-developers.com/showthread.php?t=652564
ROMs that I can verify have MNS Wired Tether Internet Sharing working using this procedure
DamageControl v2.5
DamageControl v2.6
DarchLegend v5.0
Click to expand...
Click to collapse
also after flashing 1.1beta5 my pri still remains at 1.70_003..any ideas?
ajaholic said:
also after flashing 1.1beta5 my pri still remains at 1.70_003..any ideas?
Click to expand...
Click to collapse
I was going through this procedure last night and the same thing happened to me. I did steps 1 and 2 a second time and after that the PRI was set to 2.11_002.
And thanks for the directions OP! This is the first time I've had wired tethering working on my Hero (without a paid application)
i would like to add that this does work on fresh 2.0d... but for some reason my nandroid wouldnt restore correctly, i had to restore an older nandroid and i lost a couple things
dmc971989 said:
i would like to add that this does work on fresh 2.0d... but for some reason my nandroid wouldnt restore correctly, i had to restore an older nandroid and i lost a couple things
Click to expand...
Click to collapse
I'm building a feature in to the kitchen that will let you easily switch between PRI's. I know I've said that somewhere else but I don't think I did in this thread. So keep an eye out for that.
flipzmode said:
I'm building a feature in to the kitchen that will let you easily switch between PRI's. I know I've said that somewhere else but I don't think I did in this thread. So keep an eye out for that.
Click to expand...
Click to collapse
This is very exciting news!
does anyone have the new pri to update manually? the one link in the damagecontrol 2.07_2 thread is dead
If you have 4G connection issues, be sure to update Profile after updating by going into Settings\System Updates
Combo - Must be NAND unlocked(S-OFF) to flash - May require reflashing the kernel afterwards
EVO_Radio_2.15.00.08.08_WiMAX_27243_PRI_NV_2.15_003 - Includes latest Radio, WiMAX, PRI & NV
Radio - Must be NAND unlocked(S-OFF) to flash - May require reflashing the kernel afterwards
EVO_Radio_2.15.00.08.08 - Latest
EVO_Radio_2.15.00.05.02
EVO_Radio_2.15.00.04.08
EVO_Radio_2.15.00.11.19
EVO_Radio_2.15.00.09.01
EVO_Radio_2.15.00.07.28
EVO_Radio_2.15.00.07.21
EVO_Radio_2.05.00.06.10
EVO_Radio_1.39.00.05.31
EVO_Radio_1.36.00.04.02
WiMAX - Must be NAND unlocked(S-OFF) to flash
EVO_WiMAX_27243 - Latest
EVO_WiMAX_27925
EVO_WiMAX_27167_R01
EVO_WiMAX_26023_R01
EVO_WiMAX_25641_R01
EVO_WiMAX_25043_R04
EVO_WiMAX_24722
PRI - Must be NAND unlocked(S-OFF) to flash
EVO_PRI_2.15_003 - Latest
EVO_PRI_1.90_003
EVO_PRI_1.77_003
EVO_PRI_1.34_003
NV - Must be NAND unlocked(S-OFF) to flash
EVO_NV_2.15_003 - Latest
EVO_NV_1.90_003
EVO_NV_1.77_003
EVO_NV_1.71_003
EVO_NV_1.40_003
HBoot - Must be NAND unlocked(S-OFF) to flash - May require reflashing the kernel afterwards
EVO_HBoot_2.16.0001 - Not downgradeable - Latest
EVO_HBoot_2.15.0001 - Not downgradeable
EVO_HBoot_2.10.0001 - Not downgradeable
EVO_HBoot_2.02.0000 - Not downgradeable
EVO_HBoot_0.97.0000
EVO_HBoot_0.93.0000
EVO_HBoot_0.76.2000 - ENG, supports Fastboot commands
Thanks For CalKulin.. Sometimes we forget the little things..
K, so this is from newest to oldest I see, top-down..
Oh, and of course the grand question of it all, does the new wimaxx "write" itself..
Thanks..
Yes I flashed them and verified they all write correctly
is the lates radio and wimax update available to be used with the newest fresh evo 0.5.3, or does it still require yesterdays OTA update system files.
6.10 when did this happen
sent with my evo from a secret place
Calkulin said:
Yes I flashed them and verified they all write correctly
Click to expand...
Click to collapse
K, going to to test the new wimaxx radio.. Thanks Cal for this always..
Hopfully this will work with the new DC 3.2.2.1.. Or just the rooted rom you made of the OTA..
Oh, can we please get update 1.2 or 2.0 since this is a new rom.. From you..
I always trust things from you as I have from the Moment.. Thanks Dude..
I'm new to android/rooting so I have a couple of questions. I just did a full root, and from what I've read, I just have to get into recovery mode (via prompt -> "adb reboot recovery", is there a easier way?) and then select the package and install from the menu, right? Aside from that, is it safe to downgrade radios in the case where a newer one performs poorly?
detusueno said:
I'm new to android/rooting so I have a couple of questions. I just did a full root, and from what I've read, I just have to get into recovery mode (via prompt -> "adb reboot recovery", is there a easier way?) and then select the package and install from the menu, right? Aside from that, is it safe to downgrade radios in the case where a newer one performs poorly?
Click to expand...
Click to collapse
Yeah, if you run into an issue with a radio, feel free to play around and find which one works for you.
Personally, I've had all sorts of issues with the newest 3G radio. Lots of data connection lost message, and other garbage.
Okay, I want to make a note of this:
This is for CalKulins good work..
I have tested the new wimaxx and it works, it really writes and works.. I can now access 4G on the new 1.47 ota.. And all others under it.. Along with great reception and all working well with the new radio..
K, Thats out the way, this is for you others who are leery, go on and flash, it is fixed..
Not sure if those links are signed (for protected recovery users) but they are available below if needed .
MEGAUPLOAD: HTC Evo Radio 2.05.00.06.10
MEGAUPLOAD: HTC Evo Wimax 25641_R01
Crackbone said:
Yeah, if you run into an issue with a radio, feel free to play around and find which one works for you.
Personally, I've had all sorts of issues with the newest 3G radio. Lots of data connection lost message, and other garbage.
Click to expand...
Click to collapse
Cool.. I'm flashing the newest ones now. I just remember their being issues when flashing back to older radios on WinMo, of course, this ain't WinMo anymore but it never hurts to be sure.
can I use these with the new fresh rom
I'm interested in knowing the same as others, is it possible to just flash over any other ROM, like Fresh or does it have to be the over new OTA system files only?
Thanks!
Can this be flashed on top of the Unrevoked root?
Worked great, thanks Calk.
Scanning forever, but that's to be expected with the newest radio/older firmware.
thanks for the links. Worked great
I'm currently on DC 3.2.2 with the latest Radio (2.05.00.06.10) and the oldest WiMax (24722).
My MAC address currently matches the one on my rear label.
I'm not 100% sure on what my next step should be. I'm not sure how one updates the PRL/Profile, but I've seen it mentioned a lot. Should I just grab the latest WiMax from here and flash it? I unfortunately have no 4G near me to test my phone to make sure it's even working right now, but I will be in Baltimore a lot this summer and wish to use it there.
From what I can see the wimax radio did not overwrite my mac address but no 4G so
freeza said:
Worked great, thanks Calk.
Scanning forever, but that's to be expected with the newest radio/older firmware.
Click to expand...
Click to collapse
What ROM are using? 1.32 or 1.47 based?
ThornXBL said:
I'm currently on DC 3.2.2 with the latest Radio (2.05.00.06.10) and the oldest WiMax (24722).
My MAC address currently matches the one on my rear label.
I'm not 100% sure on what my next step should be. I'm not sure how one updates the PRL/Profile, but I've seen it mentioned a lot. Should I just grab the latest WiMax from here and flash it? I unfortunately have no 4G near me to test my phone to make sure it's even working right now, but I will be in Baltimore a lot this summer and wish to use it there.
Click to expand...
Click to collapse
You can flash the latest WiMAX if you want and update prl & profile are in settings/system updates
so i everything went fine using bubbys method to root my inspire, (thank you by the way) i have not done anything after rooting the phone, everything works fine, except the mobile network, the little symbol is still there and my phone says its connected to the mobile network, but when i goto use it it says connection dropped, i opened the internet browser and it took 20 min to load google, before i rooted this was an instant load no waiting, i had no problems with internet before i rooted my phone, i would appreciate any help and advice, thanks
Flash a different Rom. Gingerbeast is a good'n but be sure to make a nandroid first.
when making a nandroid, do i have to save it to my pc, or do i leave it on the phone, i would like to stay with this rom for a while if i could get the connection back to where its supposed to be, is the a radio that would fix this? anyone's help would be greatly appreciated
greentrees89 said:
when making a nandroid, do i have to save it to my pc, or do i leave it on the phone, i would like to stay with this rom for a while if i could get the connection back to where its supposed to be, is the a radio that would fix this? anyone's help would be greatly appreciated
Click to expand...
Click to collapse
Nandroids are saved to your SD card.
The radio is not backed-up when doing a nandroid...meaning, it's not touched at all... Not backed-up, not restored either... The same radio will persist from ROM-to-rom, nandroid restore of a previous ROM, etc.
Trying different radios may or may not improve your situation. It's a very user-specific thing. Personal testing/experimentation is the only way to find out.
If you do decide to play around with radios, start with the inspire only radio thread in the dev section. Use that method outlined in post #1, and those flashable radio files, also in that first post.
any one already have this problem? i need help
i would like do go back to the OTA radio that i had before i rooted my phone, does any one know a safe way to do that, ive heard so much on this im over whelmed, some say my APN settings are to blame, some say its the radio, some say i just have to flash a different ROM, i want the stock rom with the ATT crap removed, but i also need my internet back to where it was, what do you guys think?, one time i had problems with my internet before i rooted, i called ATT and they had me read of some info from the about phone section of the settings and then they fixed it over the air, do you think i could get away with this?
greentrees89 said:
i would like do go back to the OTA radio that i had before i rooted my phone, does any one know a safe way to do that, ive heard so much on this im over whelmed, some say my APN settings are to blame, some say its the radio, some say i just have to flash a different ROM, i want the stock rom with the ATT crap removed, but i also need my internet back to where it was, what do you guys think?, one time i had problems with my internet before i rooted, i called ATT and they had me read of some info from the about phone section of the settings and then they fixed it over the air, do you think i could get away with this?
Click to expand...
Click to collapse
So you're saying that before you rooted, you had actually received the new OTA update that "enabled the pseudo-4G," correct?
That radio and RIL is available from the "inspire only radio thread" by tribalartgod in the dev section.
here
It's the one that ends in "06.30_M" and is noted as the recent OTA. There's two choices, one with rcdata and one without. Rcdata is a file that was included with the ota, that is not critical for the radio to flash properly, but if you want a "pure" OTA radio experience, you should flash this one.
There are settings in that extra rcdata file that are related to that radio, though not much is known about what they actually do, ATT included it, so its probably a good idea to use that one, just in case. I did, and if you had done the OTA prior to rooting, you did to. So use the radio file with rcdata.
Just folllow the instructions in that thread, and you'll have that radio, as you did prior to rooting.
i did that dindent help
so i correctly applied both the radio and ril, and restarted twice and waited 30 min and my speed went fron 200kb to 600kb down and still at 90kb for up, what now, and what of these was i supposed to choose:
AT&T OTA Update - Released 04-29-2011
Radio OS Base: FroYo
Radio: 12.39a.60.19x_26.06.06.30_M
MD5 Sum: 991dc7acd70fa13d47ca6d0a4b6f857f
With RCDATA: 12.39a.60.19x_26.06.06.30_M
MD5 Sum: 7c9ffb634314ff952a8fb49b7f86ee11
Ril: HTC-RIL 2.2.0079HM
MD5 Sum: 29dc8bc64fd61a0168dcd1c31e9aae34
AOSP Ril: HTC-RIL 2.2.0018G
MD5 Sum: a9972f35d8d4e1155fea9f49aa29f483
i used the ones in bold?
Hmm, I personally did not have this issue, but I also used a different method, but to fix this I would definitely attempt to do a full wipe and install a new rom. I highly recommend using the rom Android Revolution HD, but that's your choice. Hope this works!
im not haveing any luck
so i flashed a new rom and i love the rom everything is great except the moblie connection, same problem as with the last rom, i cant even load google or the market, it says im connected, i ran speedtest.net app, very poor results. 500down/90up, someone please help
I tried installing BAMF 3.0 RC2 on my phone, and I can't seem to get it working properly. Upon startup it force closes a bunch of things and the radio shows no signal at all. I have ran the MD5 on the download to ensure integrity. Also did a complete wipe prior to flashing. Could this be a radio problem? I haven't done any radio upgrades.
STEyeAndroid said:
I tried installing BAMF 3.0 RC2 on my phone, and I can't seem to get it working properly. Upon startup it force closes a bunch of things and the radio shows no signal at all. I have ran the MD5 on the download to ensure integrity. Also did a complete wipe prior to flashing. Could this be a radio problem? I haven't done any radio upgrades.
Click to expand...
Click to collapse
You need a gingerbread radio for a gingerbread rom.. so MR2 or MR2.5
Sent from my ThunderBolt using XDA Premium App
i have the same problem and ive been trying to flash both radios its acting like its doing it in hboot but everything still is the same and no mobile network for me. can someone please tell me a way to get it working how do i check my md5 of my rom and stuff
poloboogie said:
i have the same problem and ive been trying to flash both radios its acting like its doing it in hboot but everything still is the same and no mobile network for me. can someone please tell me a way to get it working how do i check my md5 of my rom and stuff
Click to expand...
Click to collapse
when you say everything is the same, do you mean it still has the previous radio version number?
I'd suggest that you both:
1) Wipe data/dalvik/cache and flash back to a froyo ROM where you do have a signal
2) Upgrade from froyo to the MR2/2.5 radio
3) Re-wipe data/dalvik/cache (or even do it twice for good luck ) and re-flash BAMF 3.0
If its worth doing, its worth overdoing, especially when you're messing with radios and the like. Best of luck!
That's the same problem I first had with gingeritis before flashing the correct radio.. if you are still experiencing the problems after the radio flash i would suggest confirming the radio did install by checking the version number..
if it is all correct do as MattBeyers said and wipe and reflash
Thanks, that seemed to work. I still got a couple of force closes but much less than before. Also I can see my radio now! If I wanted to restore my old my Backup (Stock Froyo - MR1), do I restore my backup then flash MR1? If so, does anyone have a link the MR1 image? TIA!
I'm always one to upgrade/downgrade radios before I flash a ROM, so I would say to downgrade to MR1 and then flash the Froyo backup. Also, try going into ROM manager and using the Fix Permissions tool to see if that helps with some of the force closes.
Sent from my Mecha using XDA Premium App
MattBeyers said:
I'm always one to upgrade/downgrade radios before I flash a ROM, so I would say to downgrade to MR1 and then flash the Froyo backup. Also, try going into ROM manager and using the Fix Permissions tool to see if that helps with some of the force closes.
Sent from my Mecha using XDA Premium App
Click to expand...
Click to collapse
Any reason for flashing one before the other? Reading through several of the ROM threads, it seems like everyone has a preference, but no one explains why.
I tried mr2 and mr2.5 but could only get 3g. Went back to CM7.
Sent from my ThunderBolt using XDA Premium App
Mr_Joshua said:
Any reason for flashing one before the other? Reading through several of the ROM threads, it seems like everyone has a preference, but no one explains why.
Click to expand...
Click to collapse
I just feel like the radio, being the thing that, well, controls every useful function on the phone, should be installed and present when a new ROM is flashed. I may be wrong, but it would seem logical to me that a new ROM would talk to the radio in order to make sure everything is kosher. But what if that's something that a ROM will only do once, at the first boot, and not once a new radio is flashed? Then, all of a sudden, you have the right radio, but its configured improperly by your ROM, since the ROM has already gone through its initial boot set up with the old radio. Therefore, my theory is radio > ROM (Please note, theory. )
Make sure u have a gb radio mr2 or mr2.5
MattBeyers said:
I just feel like the radio, being the thing that, well, controls every useful function on the phone, should be installed and present when a new ROM is flashed. I may be wrong, but it would seem logical to me that a new ROM would talk to the radio in order to make sure everything is kosher. But what if that's something that a ROM will only do once, at the first boot, and not once a new radio is flashed? Then, all of a sudden, you have the right radio, but its configured improperly by your ROM, since the ROM has already gone through its initial boot set up with the old radio. Therefore, my theory is radio > ROM (Please note, theory. )
Click to expand...
Click to collapse
This makes sense from a logical reason. Perhaps a ROM developer on this site can confirm this.
Hi all -
I recently updated to the 4.4.3 VzW firmware and upgraded from Viper 1.8.0 to Viper 2.5.0. Since upgrading, I have been having troubles with my hotspot. After being on and other devices have been using it for a bit, my M8 begins to rapidly turn on/off the Data Connection. This doesn't stop and the only way to fix the problem is go into airplane mode and back out again. I figured that I may have had a bad flash, so i tried reflashing clean downloads of both the firmware and a full wipe and reinstall of ViperOne, but still seeing the exact same issue. I seem to be also experiencing a problem where my phone is reporting a 4G connection, but data is disconnected and i cannot get anything over the data channel. Voice works fine. Again, to fix it's a cycle through airplane mode.
I tried applying the changes recommended by for the 4G handoff fix, even though the problem described does not seem to be exactly the same as mine. It did not seem to help, and mae it even harder to get a reliable 4G connection.
http://forum.xda-developers.com/verizon-htc-one-m8/general/verizon-4g-handoff-fix-t2868778
Has anyone else seen anything like this and have any recommendations for a fix?
Just realized this would be better in the troubleshooting forum. Is there a way for me to move it there or does that require a moderator?
Check http://forum.xda-developers.com/verizon-htc-one-m8/help/loss-lte-data-using-ap-t2900047
I have had the same thing, going back to 1.55.605.2 FW does seem to be the fix, I think its something with 4.4.3 FW.
One of the so called improvements is Mobile hotspot connectivity, but maybe that's only with phones that don't use the patched default.xml,
the ones that really pay for the mobile hotspot.
kc6wke said:
I have had the same thing, going back to 1.55.605.2 FW does seem to be the fix, I think its something with 4.4.3 FW.
One of the so called improvements is Mobile hotspot connectivity, but maybe that's only with phones that don't use the patched default.xml,
the ones that really pay for the mobile hotspot.
Click to expand...
Click to collapse
Thanks for the reply - do you have a link for the old firmware, so i can flash and revert back to that?
Also - are you still running Viper 2.x or did you roll back to a prior ROM as well?
After some more searching, i found this link for stock 4.4.2 on VzW, but was wondering if anyone has the firmware only, so don't have to restore recovery, and rom afterwards.
http://forum.xda-developers.com/showthread.php?t=2727831
I certainly can and will do it, if necessary, just would prefer to have the firmware only, if someone has it available. Anyone?
Thanks in advance for the help!
Dave
deh2k7 said:
Thanks for the reply - do you have a link for the old firmware, so i can flash and revert back to that?
Click to expand...
Click to collapse
https://www.androidfilehost.com/?w=files&flid=13966
Dl the one without boot img
Thanks, downloaded and reverted. Long boot times, but things working. Now to give the hotspot a few tests. I'll update with my results.
deh2k7 said:
Thanks, downloaded and reverted. Long boot times, but things working. Now to give the hotspot a few tests. I'll update with my results.
Click to expand...
Click to collapse
initial tests are very promising. hotspot seems to be stable and hasn't dumped the data connection yet. Looks like good old VzW managed to screw up the firmware update as usual. Would be nice if they didn't always to be different. Thank god for these forums and the hardworking devs here!
I spoke too soon. Still seeing the same issue after reverting the FW back to 1.55.605.2. Anyone seeing this? Any thoughts on if reverting back to Viper 1.8 would help?
deh2k7 said:
I spoke too soon. Still seeing the same issue after reverting the FW back to 1.55.605.2. Anyone seeing this? Any thoughts on if reverting back to Viper 1.8 would help?
Click to expand...
Click to collapse
I don't think it is the firmware that is the issue, I think it is the kernel. You should be good going back to Viper 1.8 as it uses an older kernel. I would think you would also be fine using the newer firmware and an older ROM version.
jsaxon2 said:
I don't think it is the firmware that is the issue, I think it is the kernel. You should be good going back to Viper 1.8 as it uses an older kernel. I would think you would also be fine using the newer firmware and an older ROM version.
Click to expand...
Click to collapse
I'm starting to believe this as well, that there's something flaky in the 2.x Viper ROMS for VzW and hotspots, and likely in the kernel. I've already reverted back to the old firmware, and I'm going to go back to a clean 1.7.x full install, then OTA to 1.8. Will update with the results.
deh2k7 said:
I'm starting to believe this as well, that there's something flaky in the 2.x Viper ROMS for VzW and hotspots, and likely in the kernel. I've already reverted back to the old firmware, and I'm going to go back to a clean 1.7.x full install, then OTA to 1.8. Will update with the results.
Click to expand...
Click to collapse
Any luck fixing this issue?