Just took an update through Samsung Kies - I545VRUDMI1
- Thread starter jessie02
- Start date
Chicago is an area with AWS but I am in the burbs. Maybe just downtown.
Sent from my SCH-I545 using xda app-developers app
I just ran two speed tests. Inside my office I got 5 down. Outside of it (literally in the hallway) I got 30 down.....
Also, there is only one place where I drop calls on my drive. I started dropping calls there maybe a month ago and as of yesterday and today, I don't drop the calls. I'm thinking they took a tower off to upgrade and now it is back up and allowing AWS.
Doesn't sound very definitive! You need to confirm that' it's working when you are testing 
I got between 8 and 15+ down and between 4+;and 8 up.
On Nassau Cty, Long Island. Don't know what we have?
Sent from my Xoom using Tapatalk 4
I got between 8 and 15+ down and between 4+;and 8 up.
On Nassau Cty, Long Island. Don't know what we have?
Sent from my Xoom using Tapatalk 4
Last edited:
@Surge1223, I didn't notice a dedicated thread yet. Have you posted this modem? I'm interested in its MD5 too before I attempt a flash. Many thanks!
Update: Chrome on my phone wasn't handling the download right. Using a different browser and device it worked
--OctOS powered VZW GS4 Dev Edition
Last edited:
Are you congratulating him for no reason? You 100% sure this new update uses the new AWS?
Sent from my Galaxy S4
Sir_Eagle
Senior Member
Are you congratulating him for no reason? You 100% sure this new update uses the new AWS?
Sent from my Galaxy S4
Any links to threads or sites for this new root method?
I can confirm that using voodoo ota root keeper does in fact work. Mind you I'm only rooted, no safestrap or anything. Glad it worked, been a few months since I've been on android (returned from an iPhone 5)and glad not much has changed.
Sent from my SCH-I545 using Tapatalk
Sent from my SCH-I545 using Tapatalk
Might have to download to the pc first and transfer, I don't know why that matters sometimes for some people but it seems too. I DL last night straight to the phone . No issues. Ran the radio all day. Less impressed now than I was last night. But if it enables that extra band it would be worth it.
Sent from my SCH-I545 using xda app-developers app
I was congratulating him because he had problems flashing the modem and he succeeded. I'm not guaranteeing anythingAre you congratulating him for no reason? You 100% sure this new update uses the new AWS?
Sent from my Galaxy S4
Sent from my SCH-I545 using Tapatalk 2
To see what band you are on dial *#0011# and you will see the lte engineering screen.
Band class 13 is 700mhz lte
band class 4 is aws lte
The DL Bandwidth tells you which bandwidth of LTE is in your area
For example "DL Bandwidth: 10mhz"
Means you are on a 10x10mhz lte deployment.
Once someone shows band 4 on an engineering screen screenshot we know this modem enables AWS.
Band class 13 is 700mhz lte
band class 4 is aws lte
The DL Bandwidth tells you which bandwidth of LTE is in your area
For example "DL Bandwidth: 10mhz"
Means you are on a 10x10mhz lte deployment.
Once someone shows band 4 on an engineering screen screenshot we know this modem enables AWS.
You need to have dialer codes enabled. There is a thread for it here http://xdaforums.com/showthread.php?t=2303905
I just took a quick look at aboot.mbn in this update and it looks like the "version" has been updated from the ME7 aboot. This likely means if you flash the MI1 bootloaders, you will NOT be able to revert to ME7/MDK bootloaders. The highlighted values below are checked when aboot is updated and most likely triggers the qfuse update if the new aboot ver > curr qfuse ver.
(Disclaimer: I don't have an i545, but I'm basing this off my analysis of the MF3 (ATT) bootloaders, which are very similar)
For reference, I'll show the change you can find with a simple hex editor:
MI1
ME7
(Disclaimer: I don't have an i545, but I'm basing this off my analysis of the MF3 (ATT) bootloaders, which are very similar)
For reference, I'll show the change you can find with a simple hex editor:
MI1
Code:
0000000[B][COLOR="Red"]4[/COLOR][/B]00000009 SW_ID1ME7
Code:
0000000[B][COLOR="Red"]3[/COLOR][/B]00000009 SW_ID1
Flashed the new modem via safestrap. Thank you for posting the zip. In the event that I wish to flash back to the old me7 modem, is that available as well in a flashable zip?
Sent from my SCH-I545 using Tapatalk
Sent from my SCH-I545 using Tapatalk
I'm not trying to be an ass but I ran a search for me7 radio and found this link http://xdaforums.com/showthread.php?t=2384362 I hope this helps! :good:
I didn't take it that way at all...I did search but only came up with Odin results... I'm tired I guess... Thank you for the help.
Sent from my SCH-I545 using Tapatalk
Sent from my SCH-I545 using Tapatalk
FYI this is what the screen looks like
I flashed the new modem in safestrap. I am only seeing band 13 (700mhz) in my area (Tulsa, OK)
FYI this is what the screen looks like
I flashed the new modem in safestrap. I am only seeing band 13 (700mhz) in my area (Tulsa, OK)
Since I'm only rooted, not unlocked (was on ME7, now MI1) I was a bit hesitant to try the steps for unlocking the codes myself. I did find and use the app on the play store and also verified band 13 here in Chicago suburbs. We'll see if it's the same at work tomorrow, closer to the city.
Similar threads
- Poll
Top Liked Posts
-
There are no posts matching your filters.
-
116PLEASE NOTE BEFORE UPDATING TO THIS NEW BUILD
If you are on VRUAMDK, of course do not update AT ALL (due to the same bootloader situation that was on VRUAME7 - this has not changed). Just wait until the dev for the ROM you are currently running updates it to the new VRUDMI1 build themselves and then flash that.
If you are on VRUAME7, it is not yet confirmed that the root exploit is patched in VRUDMI1. The VRUAME7 root method does not work yet on VRUDMI1 because that exploit was coded to check for VRUAME7 build even if it does work on other builds. I am currently trying to get a hold of the user who helped to modify that exploit to work on VRUAME7 to do the same for the new build so we can test if the entire exploit is patched as of yet or not. Until then, please note there is no confirmation that the exploit has patched in the new build. As far as Safestrap is concerned, that will have to be determined AFTER we get root up and running on a full VRUDMI1 build (however if I had to guess, most likely Safestrap was not yet patched, but again, we will have to wait and see after we get root).65I just took a quick look at aboot.mbn in this update and it looks like the "version" has been updated from the ME7 aboot. This likely means if you flash the MI1 bootloaders, you will NOT be able to revert to ME7/MDK bootloaders. The highlighted values below are checked when aboot is updated and most likely triggers the qfuse update if the new aboot ver > curr qfuse ver.
(Disclaimer: I don't have an i545, but I'm basing this off my analysis of the MF3 (ATT) bootloaders, which are very similar)
For reference, I'll show the change you can find with a simple hex editor:
MI1
Code:0000000[B][COLOR="Red"]4[/COLOR][/B]00000009 SW_ID1
ME7
Code:0000000[B][COLOR="Red"]3[/COLOR][/B]00000009 SW_ID1
