Hi guys,
I have looked at numerous threads and just can't find exactly what I need or maybe I'm too dumb/too much of a noob to understand what I need, I am on CM10.1 nightlies with CWM and I can no longer flash the nightlies. It gives me assert fail messages. After some digging, I think the problem is that I need to update the bootloader as they no longer support the ICS bootloader (I am assuming I am on ICS bootloader, how would I know?). But then I couldn't find the latest bootloader and how to install it. Is that even the problem? Any help is appreciated or even if you can point me to the right thread, that would be awesome. Thanks for the help.
jlor23 said:
Hi guys,
I have looked at numerous threads and just can't find exactly what I need or maybe I'm too dumb/too much of a noob to understand what I need, I am on CM10.1 nightlies with CWM and I can no longer flash the nightlies. It gives me assert fail messages. After some digging, I think the problem is that I need to update the bootloader as they no longer support the ICS bootloader (I am assuming I am on ICS bootloader, how would I know?). But then I couldn't find the latest bootloader and how to install it. Is that even the problem? Any help is appreciated or even if you can point me to the right thread, that would be awesome. Thanks for the help.
Click to expand...
Click to collapse
I'm not 100% sure what the problem is, but I'll take you through step-by-step of what I'd do if my phone were giving me this problem.
Double check the md5sums of the CM10.1 Nightly Zip: It doesn't seem like this is the problem, but it's always the first thing I check.
Update your modem/firmware/baseband: I know the most recent build of LiquidSmooth require you to be on baseband MD4. You can get it over on Freeza's thread. The file you're looking for is:
MD4 Firmware:
MD4 Firmware/modem/baseband update
MD5: EEEAFDBE59CF9C5B492B1A591EC92D02
Click to expand...
Click to collapse
All you have to do is wipe cache and dalvik cache and flash this Rom in your recovery. Reboot and now you're on MD4.
Update your Recovery: I normally run the latest and greatest TWRP, but others like the stability of some of the older builds. I'd flash the latest 2.5.0.0 TWRP from Naddict's thread.
Those would be the first three things I'd try.
topherk said:
I'm not 100% sure what the problem is, but I'll take you through step-by-step of what I'd do if my phone were giving me this problem.
Double check the md5sums of the CM10.1 Nightly Zip: It doesn't seem like this is the problem, but it's always the first thing I check.
Update your modem/firmware/baseband: I know the most recent build of LiquidSmooth require you to be on baseband MD4. You can get it over on Freeza's thread. The file you're looking for is:
All you have to do is wipe cache and dalvik cache and flash this Rom in your recovery. Reboot and now you're on MD4.
Update your Recovery: I normally run the latest and greatest TWRP, but others like the stability of some of the older builds. I'd flash the latest 2.5.0.0 TWRP from Naddict's thread.
Those would be the first three things I'd try.
Click to expand...
Click to collapse
Awesome! Your 2nd suggestion worked! I had tried your other 2 suggestion already with no luck but #2 was what I needed. Thanks so much!
topherk said:
I'm not 100% sure what the problem is, but I'll take you through step-by-step of what I'd do if my phone were giving me this problem.
Double check the md5sums of the CM10.1 Nightly Zip: It doesn't seem like this is the problem, but it's always the first thing I check.
Those would be the first three things I'd try.
Click to expand...
Click to collapse
Yes that most definitely was his problem, the new cm10.1 nightlies require the md4 firmware update because of the bootloader.
Sent from the future via Xparent Green Tapatalk 2
I was coming off of CM 10.1.3 OS 4.2 and flashed DanDroid 5.1 (4.3). I also had to flash a 4.3 bootloader to run DanDroid. I was having some issues with the rom so I wanted to go back to CM 10 but found this error I kept getting: assert failedgetprop("ro.bootloader"). I started reading From this site http://androidromupdate.com/2012/08...original-ics-4-0-4-t999uvalh2-stock-firmware/ states the This procedure should not be used if your device already updated to official 4.3, the 4.3 update has a secured bootloader. I do hope this is not true and that someone can really help me seriously!! I did manage to flash stock 4.1.2 but when I went back to CWM recovery to flash CM 10.1.3 OS 4.2 it won't let me. i do hope this makes sense I am really trying to explain, if you need more info or not understanding any of this info please be nice and respectful in requesting or sharing info about this problem.
Also please don't ask why I wouldn't want to stay on 4.3 or 4.4 I have my reasons and typing this is taking to long anyway
Thank you advance for your assistance,
mr wizard said:
I was coming off of CM 10.1.3 OS 4.2 and flashed DanDroid 5.1 (4.3). I also had to flash a 4.3 bootloader to run DanDroid. I was having some issues with the rom so I wanted to go back to CM 10 but found this error I kept getting: assert failedgetprop("ro.bootloader"). I started reading From this site http://androidromupdate.com/2012/08...original-ics-4-0-4-t999uvalh2-stock-firmware/ states the This procedure should not be used if your device already updated to official 4.3, the 4.3 update has a secured bootloader. I do hope this is not true and that someone can really help me seriously!! I did manage to flash stock 4.1.2 but when I went back to CWM recovery to flash CM 10.1.3 OS 4.2 it won't let me. i do hope this makes sense I am really trying to explain, if you need more info or not understanding any of this info please be nice and respectful in requesting or sharing info about this problem.
Also please don't ask why I wouldn't want to stay on 4.3 or 4.4 I have my reasons and typing this is taking to long anyway
Thank you advance for your assistance,
Click to expand...
Click to collapse
How in the world did you go back to 4.1.2 if you've already updated to the 4.3 bootloader? Unless you used MJ2...anywho, you'll need to edit the assert in the updater-script found inside the zip file and remove everything that says "getprop.bootloader" (somewhere along those lines...) and then you can flash.
rani9990 said:
How in the world did you go back to 4.1.2 if you've already updated to the 4.3 bootloader? Unless you used MJ2...anywho, you'll need to edit the assert in the updater-script found inside the zip file and remove everything that says "getprop.bootloader" (somewhere along those lines...) and then you can flash.
Click to expand...
Click to collapse
Thanks so much for the reply. Yeah I don't know how I got 4.1.2 stock back on either it was T999UVDMD5. I am not sure how to edit the assert you are talking about. Also if I need to use a computer to do this I am on a Mac and I have seen from other forums that Macs are not as useful then Windows when it comes to scripting or de compiling or I could be wrong?
Thanks,
mr wizard
Background:
Decided to fresh install CM via the fancy new installer and just refresh everything.
This wouldn't complete correctly.
Attempted to manually install 10.2 but get an assert failure.
Reinstalled 10.1.3 and it is currently running.
Current problem; CM10.2 / CM11 will not install correctly.
I'm pretty sure its just a matter of updating recovery or something silly but I can't find any concrete information regarding this.
Running: CWM v6.0.4.5
When I attempt to install either version I get an Assert Failed.
Suggestions?
6.0.4.5 is the latest CWM.
Are you sure you are choosing the CM for YOUR device ?
Perseus71 said:
6.0.4.5 is the latest CWM.
Are you sure you are choosing the CM for YOUR device ?
Click to expand...
Click to collapse
Pretty sure, since if I choose 10.1.3 and install it from the same download page it works.
I've always used d2tmo
It's a Samsung Galaxy S3 from WIND mobile.
Mod: SGH-T999V
I've tried the following CM versions from get.cm
cm-10.2.0-RC1-d2tmo.zip
cm-11-20140104-SNAPSHOT-M2-d2tmo.zip
cm-10.2-20131102-SNAPSHOT-M1-d2tmo.zip
If that's the case then edit the updater script and add your device to the Asserts or remove them alltogether.
Perseus71 said:
If that's the case then edit the updater script and add your device to the Asserts or remove them alltogether.
Click to expand...
Click to collapse
Yeah my baseband is currently T999VVLLH2 when looking at about phone, which I don't see in the list when its failing the assert.
Currently failing looking for;
T999UVDLJA
T999UVDLJC
T999UVDMD5
T999UVUEMJC
T999VVLDLL1
T999LUVAMB7
T999VVLDMF2
T999VVLUEMK5
Vyr1s said:
Yeah my baseband is currently T999VVLLH2 when looking at about phone, which I don't see in the list when its failing the assert.
Currently failing looking for;
T999UVDLJA
T999UVDLJC
T999UVDMD5
T999UVUEMJC
T999VVLDLL1
T999LUVAMB7
T999VVLDMF2
T999VVLUEMK5
Click to expand...
Click to collapse
Updated my baseband to match "T999VVLUEMK5".
Still failing though.
Vyr1s said:
Updated my baseband to match "T999VVLUEMK5".
Still failing though.
Click to expand...
Click to collapse
Updated to the newest bootloader, updated the modem again, finally accepted CM11 snapshot, installed gapps for KK and everything is gravy now.
Vyr1s said:
Updated to the newest bootloader, updated the modem again, finally accepted CM11 snapshot, installed gapps for KK and everything is gravy now.
Click to expand...
Click to collapse
Its not the baseband but the Bootloader that it was looking for. So when you updated the bootloader, it accepted that. Glad its all sorted out.
Vyr1s said:
Updated to the newest bootloader, updated the modem again, finally accepted CM11 snapshot, installed gapps for KK and everything is gravy now.
Click to expand...
Click to collapse
Hi,
I am having the same issue, can you point me the thread that shows the step by step procedure to update my boatloader pls
dealguy007 said:
Hi,
I am having the same issue, can you point me the thread that shows the step by step procedure to update my boatloader pls
Click to expand...
Click to collapse
Try this thread.
I'm trying to help out a friend and update his Galaxy S3 SGH-I747. He originally had cyanogenmod installed but he restored his phone back to stock and flashed a stock recovery back to the phone. When he tries to do an OTA updated it downloads but fails to install? His current android version is 4.1.1 but his baseband is I747UCUFNE4 which if im not mistaken is for android 4.4.2 what would be the easiest way to get his phone updated to the stock 4.4.2 software?
Follow one of enewman17's how to update threads in General.
4.4.2 upgrade stops at 28%
DocHoliday77 said:
Follow one of enewman17's how to update threads in General.
Click to expand...
Click to collapse
Can you be a bit more specific?
Thanks
bmoliver said:
Can you be a bit more specific?
Thanks
Click to expand...
Click to collapse
The beauty of search: http://forum.xda-developers.com/search.php?searchid=292146343
Two threads from enewman17: UCUEMJB to UCUFNE4 firmware update; How to update SGH-I747 to UCUFNE4_4.4.2
DocHoliday77 said:
Follow one of enewman17's how to update threads in General.
Click to expand...
Click to collapse
BWolf56 said:
The beauty of search: http://forum.xda-developers.com/search.php?searchid=292146343
Two threads from enewman17: UCUEMJB to UCUFNE4 firmware update; How to update SGH-I747 to UCUFNE4_4.4.2
Click to expand...
Click to collapse
Thanks, I had found the last link (....2789917) by doing a Google search (i.e., searching within the forum was less successful).
Hey bmoliver and BWolf56,
I am in the same boat as your friend where my baseband (bootloader) version is I747UCUFNE4 but the software version is stuck at 4.1.1. AT&T is identifying a OTA update, downloading but the update is failing.
I tried the method described in http://forum.xda-developers.com/showthread.php?t=2789917. But when I am trying to flash MJB bootloader, it is failing. I read elsewhere in this forum that downgrading from UCU to MJB is not really advisable.
I am stuck in 4.1.1 and my phone is half functional at the moment with the camera, nfc, bluetooth not functional :crying:.
Was your friend able to get this resolved bmoliver?
I tried searching for a I747UCUFNE4 md5 file that I can flash using odin (just a hope that it might work) but could not find.
It would be great if one of you can point me to it.
PS: I am a complete newbie to this entire thing and so far from what I read, my phone is probably soft-bricked and am hoping that someone would guide and help me get out of this.
EDIT: One more thing that I observed is when I am trying flash something in the download mode, I get the error and "sw rev check fail fused 3 binary 0" and it fails
Thanks,
CJ
bmoliver said:
Thanks, I had found the last link (....2789917) by doing a Google search (i.e., searching within the forum was less successful).
Click to expand...
Click to collapse
jchennuri said:
Hey bmoliver and BWolf56,
I am in the same boat as your friend where my baseband (bootloader) version is I747UCUFNE4 but the software version is stuck at 4.1.1. AT&T is identifying a OTA update, downloading but the update is failing.
I tried the method described in http://forum.xda-developers.com/showthread.php?t=2789917. But when I am trying to flash MJB bootloader, it is failing. I read elsewhere in this forum that downgrading from UCU to MJB is not really advisable.
I am stuck in 4.1.1 and my phone is half functional at the moment with the camera, nfc, bluetooth not functional :crying:.
Was your friend able to get this resolved bmoliver?
I tried searching for a I747UCUFNE4 md5 file that I can flash using odin (just a hope that it might work) but could not find.
It would be great if one of you can point me to it.
PS: I am a complete newbie to this entire thing and so far from what I read, my phone is probably soft-bricked and am hoping that someone would guide and help me get out of this.
Thanks,
CJ
Click to expand...
Click to collapse
You don't want to downgrade bootloaders, that will brick your phone.
You'll have to flash NE4 with Odin (or a NE4 custom ROM through custom recovery) to get your baseband and software matching.
The thread you linked should work if you follow it to a T. If something doesn't work, let us know and be specific about what happened.
Thanks for the info BWolf56,
Sorry for asking a trivial question (just getting accustomed to the lingo used here) .
When you say I should follow it to a T, are you just referring to follow all the steps.
I tried two things
1. follow each step, but failed at step 3 since I was trying to downgrade my bootloader.
2. I jumped from step 2 to step 6 and tried to flash 4.4.2OTA.zip in recovery mode but that also failed. I dont remember the exact error I got, I can try it again to give you more details if you think it is safe.
Thanks
BWolf56 said:
You don't want to downgrade bootloaders, that will brick your phone.
You'll have to flash NE4 with Odin (or a NE4 custom ROM through custom recovery) to get your baseband and software matching.
The thread you linked should work if you follow it to a T. If something doesn't work, let us know and be specific about what happened.
Click to expand...
Click to collapse
jchennuri said:
Thanks for the info BWolf56,
Sorry for asking a trivial question (just getting accustomed to the lingo used here) .
When you say I should follow it to a T, are you just referring to follow all the steps.
I tried two things
1. follow each step, but failed at step 3 since I was trying to downgrade my bootloader.
2. I jumped from step 2 to step 6 and tried to flash 4.4.2OTA.zip in recovery mode but that also failed. I dont remember the exact error I got, I can try it again to give you more details if you think it is safe.
Thanks
Click to expand...
Click to collapse
If you jumped to #6, you didn't flash a custom recovery, which you need to flash the OTA.
I did install TWRP 2.6.3.1 which I am guessing is the custom recovery (as part of step 2) and then I tried to flash the OTA. Am I missing something here?
BWolf56 said:
If you jumped to #6, you didn't flash a custom recovery, which you need to flash the OTA.
Click to expand...
Click to collapse
jchennuri said:
I did install TWRP 2.6.3.1 which I am guessing is the custom recovery (as part of step 2) and then I tried to flash the OTA. Am I missing something here?
Click to expand...
Click to collapse
What error did you get when flashing it?
I just tried flashing it again and got the following error.
I loaded the zip into my internal SD and went to recovery mode (twrp gui, Power+Home+Volume Up)
and tried installing the zip
_______________
Updating partition details...
Running boot script...
Finished running boot script.
Installing '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Package expects build fingerprint of samsung/d2u (the screen does not allowing me to scroll to the right to look at the complete line after 'd2u')
E: Error executing updater binary in zip '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Error flashing zip '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Updating partition details...
FAILED
_________________
This is the error I am getting.
Am I missing something? Please let me know if you need any more info
Thanks a ton!!!
BWolf56 said:
What error did you get when flashing it?
Click to expand...
Click to collapse
jchennuri said:
I just tried flashing it again and got the following error.
I loaded the zip into my internal SD and went to recovery mode (twrp gui, Power+Home+Volume Up)
and tried installing the zip
_______________
Updating partition details...
Running boot script...
Finished running boot script.
Installing '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Package expects build fingerprint of samsung/d2u (the screen does not allowing me to scroll to the right to look at the complete line after 'd2u')
E: Error executing updater binary in zip '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Error flashing zip '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Updating partition details...
FAILED
_________________
This is the error I am getting.
Am I missing something? Please let me know if you need any more info
Thanks a ton!!!
Click to expand...
Click to collapse
Sounds like you'll have to use Odin to flash Stock.
Your build.prop is most likely borked (or has been changed to something it's not). d2u is not a variant of the S3, nor does it exist.
Thanks a ton for helping me identify the problem.
I just have to look if a stock file to flash using odin is out there somewhere.
I will post in http://forum.xda-developers.com/showthread.php?t=2789917 to see if enewman17 or someone from the community have a tar or md5 file that I can use.
I will try that and update on how it goes.
BWolf56 said:
Sounds like you'll have to use Odin to flash Stock.
Your build.prop is most likely borked (or has been changed to something it's not). d2u is not a variant of the S3, nor does it exist.
Click to expand...
Click to collapse
jchennuri said:
Thanks a ton for helping me identify the problem.
I just have to look if a stock file to flash using odin is out there somewhere.
I will post in http://forum.xda-developers.com/showthread.php?t=2789917 to see if enewman17 or someone from the community have a tar or md5 file that I can use.
I will try that and update on how it goes.
Click to expand...
Click to collapse
You can grab the stock ROM here: http://forum.xda-developers.com/showthread.php?p=33570269#post33570269
Just make sure you grab the right version.
Thanks for the pointing me there.
I could not find the stock firmware for NE4 though.
They only have MJ2, LK3, LG1, LEM versions, no MJB either.
BWolf56 said:
You can grab the stock ROM here: http://forum.xda-developers.com/showthread.php?p=33570269#post33570269
Just make sure you grab the right version.
Click to expand...
Click to collapse
jchennuri said:
Thanks for the pointing me there.
I could not find the stock firmware for NE4 though.
They only have MJ2, LK3, LG1, LEM versions, no MJB either.
Click to expand...
Click to collapse
There isn't a NE4 stock for Odin. I just noticed the post hasn't been updated in a while.
I though I could find it on Sammobile.com but they have LK3 as their latest too.
Since you somehow have the 4.4.2 modem, you can not flash anything older than the 4.4.2 firmware. Currently there is nothing that you can flash to fix this. Normally, I would say to flash an older modem, but if Odin is seeing it as already updated to 4.4.2 (SWREV 3), and the only thing you have that is 4.4.2 is the modem, flashing anything older will likely hard brick.
You need either the full stock firmware, which there is not one, Thanks AT&T!, or a recovery flashable firmware for 4.4.2. Enewman17 has this, but it will not work for you because of how the modem is flashed. For some reason, he has it patching the 4.3 modem rather than including the full updated one like with the other partitions. If someone makes the same thing, but with the already updated modem, you could probably flash that. No guarantees though. Running 4.1.1 firmware/bootloaders with a 4.4.2 modem is a scenario which is highly unpredictable, so anything you try to flash might cause more problems, we just don't know.
I've PM'd enewman17 to ask if there was a specific reason he updated the modem the way he did. If there is not an issue doing it like i mentioned someone can try to make a new package like that for you to try.
Thanks Doc!
Hopefully enewman17 can come up with a solution for this.
Just an information which I was not able to completely comprehend but maybe pros like you or Bwolf56 will be able to.
I opened Kies and this is what it says.
Firmware information
This is the latest firmware.
Current firmware version: PDA:LK3 / PHONE:NE4 / CSC:LK3 (ATT)
Any thoughts on how do I get the PDA and CSC updated (not even sure what exactly they are)
Thanks
DocHoliday77 said:
Since you somehow have the 4.4.2 modem, you can not flash anything older than the 4.4.2 firmware. Currently there is nothing that you can flash to fix this. Normally, I would say to flash an older modem, but if Odin is seeing it as already updated to 4.4.2 (SWREV 3), and the only thing you have that is 4.4.2 is the modem, flashing anything older will likely hard brick.
You need either the full stock firmware, which there is not one, Thanks AT&T!, or a recovery flashable firmware for 4.4.2. Enewman17 has this, but it will not work for you because of how the modem is flashed. For some reason, he has it patching the 4.3 modem rather than including the full updated one like with the other partitions. If someone makes the same thing, but with the already updated modem, you could probably flash that. No guarantees though. Running 4.1.1 firmware/bootloaders with a 4.4.2 modem is a scenario which is highly unpredictable, so anything you try to flash might cause more problems, we just don't know.
I've PM'd enewman17 to ask if there was a specific reason he updated the modem the way he did. If there is not an issue doing it like i mentioned someone can try to make a new package like that for you to try.
Click to expand...
Click to collapse
Ok, enewman17 just put this together if you want to try it. This includes the full NE4 stock firmware minus system, kernel, cache and recovery.
So flashing it will preserve your current Rom, kernel and recovery, but will otherwise fully update your base firmware/bootloaders to NE4.
This should be perfectly safe to use, but seeing as it is untested, I cannot make any guarantees that it won't make things worse. (I wouldn't post it if I thought it would, but there is always the possibility)
Flash from custom recovery such as TWRP.
http://www.androidfilehost.com/?fid=23578570567716667
Sent from my SGH-T999 using Tapatalk
---------- Post added at 08:31 PM ---------- Previous post was at 08:29 PM ----------
If you want to fully update your system (rom) to stock NE4, enewman17 has a thread in the development section with stock rooms you can flash via recovery after you update your firmware posted above.
Sent from my SGH-T999 using Tapatalk
Hello,
I OTA updated from CM 10.2 stable to CM 11 M12 snapshot and I installed the gapps separately. Almost everything seems fine except for "No Service" issue. Data connection is not working, but am able to make and receive calls. There is no APN settings and adding one does not gets saved.
I searched xda and few threads state that it is due to old modem. However, this thread in xda says that the bootloader and the modem version has to be match, otherwise installing a modem with mismatching bootloader may hard brick the phone.
According to "Phone info *Samsung*" app my
Bootloader version is : I747UCDMG2
Baseband version is: I747UCDMG2
1. Do I just get the latest Modem ONLY from this thread or do I need to get BOTH bootloader and modem from dstruct2k thread.
2. If I can't solve the issue, can I just flash stable CM 10.2 back with corresponding gapps? Will it cause any such issue, because somewhere in the above thread it was mentioned that dowgrading modem might hard brick the phone too.
Thanks in advance. Any help is really appreciated.
Looks like your bootloader and modem are too old to fully supported your updated ROM.
You will need to update both; however, once updated, you can never downgrade either to be safe.
audit13 said:
Looks like your bootloader and modem are too old to fully supported your updated ROM.
You will need to update both; however, once updated, you can never downgrade either to be safe.
Click to expand...
Click to collapse
Thanks. Is there a order in which both has to be flashed like bootloader first and then modem next? Do I flash both at the same time or flash one first, reboot and then flash the other?
Also, if I don't proceed to flash the new bootloader and modem, can I safely flash CM 10.1 now without bricking the phone?
Thanks again for your reply and help.
spk_xda said:
Thanks. Is there a order in which both has to be flashed like bootloader first and then modem next? Do I flash both at the same time or flash one first, reboot and then flash the other?
Also, if I don't proceed to flash the new bootloader and modem, can I safely flash CM 10.1 now without bricking the phone?
Thanks again for your reply and help.
Click to expand...
Click to collapse
not to buttin in , cause @audit13 knows a heck of alot more than me , but this thread
http://forum.xda-developers.com/showthread.php?t=2808654
has bootloader/modem combo zip. i think mjb and ne4. just flash and it updates both at same time. be sure to read OP first though.
"all i can really do , is stay out of my own way and let the will of heaven be done"
Both should be flashed in tandem.
Yes, you can go back to cm10.2 as cm roms don't flash a bootloader or modem.
mrrocketdog said:
not to buttin in , cause @audit13 knows a heck of alot more than me , but this thread
http://forum.xda-developers.com/showthread.php?t=2808654
has bootloader/modem combo zip. i think mjb and ne4. just flash and it updates both at same time. be sure to read OP first though.
"all i can really do , is stay out of my own way and let the will of heaven be done"
Click to expand...
Click to collapse
audit13 said:
Both should be flashed in tandem.
Yes, you can go back to cm10.2 as cm roms don't flash a bootloader or modem.
Click to expand...
Click to collapse
Thank you very much to both of you. I followed the thread you mentioned and installed the MJB bootloader/modem combo and I got the data connectivity back. I did not install NE4 though as I dont really need it now I guess. Thanks again.
good to hear you got it fixed. :thumbup:
"all i can really do , is stay out of my own way and let the will of heaven be done"