yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] TrevE:
cant ifconfig just reset a mac? if its hardcoded in both the original ota an dthis one im sure its there for a reason...
[EVO 4G Android Development] myndwire:
oops! i knew i was missing one. i use bt so infrequently that i completely forgot :)
[EVO 4G Android Development] Cordy:
Yes we are and I look forward to your feedback.

That made me lol, technically according to the powers that be we were wrong for rooting our phones in the first place. But yeah we do this all for our own enjoyment, fascination with technology, and furthering the community and ourselves.
[EVO 4G Android Development] smw6180:
From the ifconfig man page on my linux box:

hw class address
Set the hardware address of this interface, if the device driver
supports this operation. The keyword must be followed by the
name of the hardware class and the printable ASCII equivalent of
the hardware address. Hardware classes currently supported
include ether (Ethernet), ax25 (AMPR AX.25), ARCnet and netrom
(AMPR NET/ROM).
[EVO 4G Android Development] liquidkernel:
You can change the MAC address by going: ifconfig <interface> hw ether <address>
[EVO 4G Android Development] TrevE:
yeah you would have to prefix it with busybox in our case (ifconfig is symlinked to dumbeddown version in toolbox by default)

question is does 4g show up as an interface? id hope it would..
[EVO 4G Android Development] myndwire:
you CAN set it manually with ifconfig *if* the 4g radio comes up as a viewable device. the only thing i can see via /system/xbin/ifconfig is eth0, which ends up being my wifi.

should be able to use mii-tool/mii-diag compiled (if not already in the os) to set your mac as well, but again.. ifconfig would do it if it shows up. i'm sure the system SETS the mac when it starts up (like when you bring up an interface), hence that wimax startup executable we were playing with earlier to get our wimax versions. it may even sit in a flat config file... OR during init... think about checking out the startup inits, or any configs associated with the wimax stuff.
[EVO 4G Android Development] jrpointer:
so did I miss something....how did you guys fix the mac address problem? was it via hex editor or was it through adb shell?
[EVO 4G Android Development] smw6180:
Yep. Under wimax.

wimax0 Link encap:Ethernet HWaddr 00:18:XX:XX:XX:XX
inet6 addr: fe80::218:41ff:fe86:b9e4/64 Scope:Link
UP BROADCAST RUNNING MTU:1400 Metric:1
RX packets:415 errors:0 dropped:0 overruns:0 frame:0
TX packets:3625 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:10251 (10.0 KiB) TX bytes:5019444 (4.7 MiB)
[EVO 4G Android Development] TrevE:
awesome. can someone with a boned mac try to reset it with busybox ifconfig wimax0 hw ether macaddresshere
[EVO 4G Android Development] myndwire:
sure does, wimax0:

/system/xbin/ifconfig

lo Link encap:Local Loopback

inet addr:127.0.0.1 Mask:255.0.0.0

inet6 addr: ::1/128 Scope:Host

UP LOOPBACK RUNNING MTU:16436 Metric:1

RX packets:2333 errors:0 dropped:0 overruns:0 frame:0

TX packets:2333 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0

RX bytes:142196 (138.8 KiB) TX bytes:142196 (138.8 KiB)

rmnet0 Link encap:Ethernet HWaddr 26:CD:C2:3B:1A:xx

inet addr:173.101.240.xxx Bcast:173.101.240.191 Mask:255.255.255.252

inet6 addr: fe80::24cd:c2ff:fe3b:xxxx/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:18204 errors:0 dropped:0 overruns:0 frame:0

TX packets:20062 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:23510095 (22.4 MiB) TX bytes:1846354 (1.7 MiB)

wimax0 Link encap:Ethernet HWaddr 00:18:41:82:4E:xx

inet6 addr: fe80::218:41ff:fe82:4e22/64 Scope:Link

UP BROADCAST RUNNING MTU:1400 Metric:1

RX packets:555 errors:0 dropped:0 overruns:0 frame:0

TX packets:3756 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:14582 (14.2 KiB) TX bytes:5028500 (4.7 MiB)

haha. beat me to it. the trick to keeping a changed mac is having it happen during init though. i'm 90% sure it won't stick unless it's part of some sort of system startup init, or config file for bringing up the interface.
[EVO 4G Android Development] liquidkernel:
Try: ifconfig -a

Should show all the interfaces.
[EVO 4G Android Development] redsolar:
Yes, the interface is wimax0

Nm, I reply as i read :P
[EVO 4G Android Development] TrevE:
really? i thought once it was set with ifconfig it was set. i remember doing ifenslave and having to mess with mac's and dont really remember setting them somewhere but i guess its posible.
[EVO 4G Android Development] myndwire:
10 to be exact (with everything on). sick.. 3 rmnetx interfaces.. 0's the 3g.
[EVO 4G Android Development] myndwire:
it honestly depends on the os binaries... they very well have made it stick with their modified ifconfig binary. anyone try yet? i'm still sitting on 3.2.1.
[EVO 4G Android Development] Cordy:
I get an error, command not supported.
[EVO 4G Android Development] redsolar:
I have been looking for the init script for wimax in /etc for a while, so far no luck, as I reverted to stock RUU (and now in the process of re-rooting) I stopped that activity.
[EVO 4G Android Development] TrevE:
i just changed usb0 mac address and it took, but i rebooted right after and it did get reset.
[EVO 4G Android Development] liquidkernel:
/init.rc

/init.supersonic.rc

Try those perhaps.
[EVO 4G Android Development] smw6180:
Start 4g first, then try it. busybox ifconfig -a isn't showing wimax0 unless it's up. Seems like a virtual interface, or something.
[EVO 4G Android Development] TrevE:
ok wimax looks like it gets started with some config file:

system\etc\wimax\sequansd\sequansd_app.xml

i know this is right because at the top there is

<ip>127.0.0.1</ip>

<port>7771</port>

which wimax keeps trying to connect to on startup for some reason.

in there there is a reference to /data/wimax. If you look in adb shell theres a few files that are wimax related.

default.fw

boot.bin

wimax_properties - defiently contains username/password to connect

mfg_default.fw

pls_default.dat

log

im digging into this now.. i wonder if that data directory is needed somehow and were getting boned by wipe? regard;ess there looks like some old fws maybe that we can revert to to fix max f-ups if you boned your addy
[EVO 4G Android Development] Cordy:
I did, I turned on 4G waited until it showed up and ran the command. Unless my syntax is off.
[EVO 4G Android Development] smw6180:
There's no support in the kernel for changing the wimax0 HW address. I just tried it.
[EVO 4G Android Development] Cordy:
Thanks for confirming, glad I'm not crazy!
[EVO 4G Android Development] smw6180:
I didn't say you're not crazy. I'm not qualified to make that diagnosis. ;)
[EVO 4G Android Development] Knight2011:
Does the 4g wimax problem apply to everyone the flashes this rom?
[EVO 4G Android Development] Kshawn:
So much info...links and everything just all jammed together..talk about wicked headache...

DO I flash 3.2.2.1 then radio then wimax? in that order Yes/No? and hope nothing breaks?
[EVO 4G Android Development] Cordy:
That's the simplest way of putting it. However what is really happening is the last flash for updating the WiMax is not actually taking place and when we got it to apply it changed our MAC address.

aside: Nice to see someone else from the VI on here.
[EVO 4G Android Development] plmiller0905:
How do you know if the Wimax flash stuck or not? I flashed DC 3.2.2.1 last night and flashed the radio and wimax over it. I don't live in a 3G area but i travel to Chicago a lot and it has 4G

I tried running "wimax_mtd" but it will not let me scrool all the way to top to see all the information.
[EVO 4G Android Development] TrevE:
what i find intresting is in bold. it loads data/wimax/Boot.bin and it SEEMS it grabs the mac from this?

just thinking outloud if we wiped and this got wiped out then flashed the wimax image could it be falling back to a default because this Boot.bin doesnt exist?

<4>[ 1391.910980] supersonic_wimax_power
<4>[ 1393.114105] supersonic_wimax_set_carddetect: 1
<7>[ 1393.114227] mmc1: card_present 1
<4>[ 1393.114440] supersonic_wimax_status
<6>[ 1393.114562] mmc1: Slot status change detected (0 -> 1)
<6>[ 1393.114685] supersonic_wimax_set_status on:1
<6>[ 1393.115509] sequans_xxx: Driver has been registered
<3>[ 1395.635589] mmc1: Command timeout (cmd= 8 mci_st=00000004)
<4>[ 1395.642425] mmc1: card claims to support voltages below the defined range.
These will be ignored.
<4>[ 1395.643157] mmc1: SDIO card claims to support the incompletely defined 'lo
w voltage range'. This will be ignored.
<6>[ 1395.667785] mmc1: new SDIO card at address 0001
<6>[ 1395.672760] sequans_xxx: module parameters: firmware_name='sequans_boot.bi
n' load_firmware=1
<6>[ 1395.673492] sequans_xxx: found SQN1210 card
[B]<6>[ 1395.674316] sequans_xxx: trying to find bootloader image: "../../../data/w
imax/Boot.bin"
<6>[ 1395.675018] sequans_xxx mmc1:0001:1: firmware: requesting ../../../data/wi
max/Boot.bin
<6>[ 1395.688079] sequans_xxx: loading bootloader to the card...
<6>[ 1395.688812] sequans_xxx: setting MAC address from bootloader: 00:18:41:xx:xx:xx[/B]
<3>[ 1395.692565] init: untracked pid 1699 exited
<6>[ 1395.699462] sequans_xxx: bootting the card...
<6>[ 1395.699951] sequans_xxx: done
<6>[ 1395.704437] sequans_xxx: wimax0: Sequans WiMAX adapter
<6>[ 1395.704986] sequans_xxx: wait until FW is started...
<6>[ 1396.212371] sequans_xxx: setup GPIO40 for wakeup form SQN1210
<6>[ 1396.217010] sequans_xxx: KTHP initialized
<6>[ 1396.217437] sequans_xxx: card initialized successfuly
<4>[ 1398.140899] select 1094 (id.partnersetup), adj 15, size 4986, to kill
<4>[ 1398.141326] select 1302 (MessageUploader), adj 15, size 4991, to kill
<4>[ 1398.142059] send sigkill to 1302 (MessageUploader), adj 15, size 4991
[EVO 4G Android Development] sk63:
you need to redirect to it to file using the adb shell wimax_mtd > "file to direct output to"

you can also use the terminal emulator since it should let you scroll far enough
[EVO 4G Android Development] mpa4712:
check out /data/wimax/wimax_properties Can you let me know which mac address you have listed in there?
[EVO 4G Android Development] linflas:
Does anyone have link to flipzmode's 4g permissions fix, been looking all over and can't seem to enter the right search terms to find it.

Thanks
[EVO 4G Android Development] Kshawn:
Ahh I see thanks a lot for the reply. So should I just flash the radio and wait out until this Wimax issue is semi-resolved? because I do have 4g hear while i'm in Houston.

Also: What part of the vi you're from? I'm from STT
[EVO 4G Android Development] plmiller0905:
They just posted a new update Wimax fix that supposedly flashes correctly:

http://xdaforums.com/showthread.php?t=713770&page=25
[EVO 4G Android Development] ewells38:
Here you are :cool:
[EVO 4G Android Development] sk63:
It's something like 10 pages back
[EVO 4G Android Development] kamiller42:
Version 3.3?

Will there be a version which has Sprint OTA patch, the latest radio and WiMax updates, and any other enhancements floating around like increased FPS? Is it doable? I am hoping to get updates in as few steps as needed.
[EVO 4G Android Development] Cordy:
Honestly if you have an older DC up and running fine with 4G I would just wait this whole thing out.

Off-Topic2: I'm from STT as well
[EVO 4G Android Development] TrevE:
i dont see a mac in there unless im blind...

im still going after boot.bin based on that kernel output i think it makes sense..
[EVO 4G Android Development] TrevE:
no this is a rom, we got a bit off topic fixing 4g problems looking for radios but whatever We will update boot, we will always keep radio/wimax separate. this does include the ota stuff from sprint already.

the FPS fix breaks camera, until it doesnt we will not include that either.
[EVO 4G Android Development] Cordy:
Guess what's located inside the Boot.bin on my phone, that damn generic MAC address
[EVO 4G Android Development] Kshawn:
Well I flashed 3.2.2.1 and nothing else, rebooted and connected right back to 4g so I'll take your advice and wait this thing out. thanks again =]

STT:D
[EVO 4G Android Development] TrevE:
guess whats in mine? my valid mac address. can you nandroid back to a previous time before you flashed wimax, try to pull that file, then replace it in your current setup?
[EVO 4G Android Development] Stickboy46:
So how do we go about getting the Vanilla Lock Screen WITHOUT it being broken or breaking the power button?
[EVO 4G Android Development] Cordy:
Nandroid, whats that??? lol I kid, will do and report back.
[EVO 4G Android Development] mpa4712:
It's there.. and it's actually got the 05 at the end and not the 04.. here's my local copy:

[email]prop_existpersist.wimax.Cold_Boot_Flag1persist.wimax.STANDBY_TIME600000persist.wimax.SCAN_RATE1800000persist.wimax.Realm@sprintpcs.compersist.wimax.CenterFrequency2647000,2657000,2667000persist.wimax.Bandwidth10,10,10persist.wimax.0.ManSEQUANSpersist.wimax.0.ModSQN1210persist.wimax.0.FwV24836persist.wimax.0.HwVREV0944persist.wimax.0.SwV4.6.2.2persist.wimax.0.MAC[B]00:16:08:00:24:05[/B]persist.wimax.0.TO-FUMO-REF./FUMOpersist.wimax.TO-WiMAX-REF./WiMAXSupppersist.wimax.IPv4TRUEpersist.wimax.IPv6TRUEpersist.wimax.ServerInitiatedTRUEpersist.wimax.CLInit.PollSuprtTRUEpersist.wimax.CLInit.PollIntrvl-1persist.wimax.WorkMode2persist.wimax.Session_Conti0persist.wimax.Scan_Timeout1persist.wimax.Scan_Retry300persist.wimax.Idle_Sleep10persist.wimax.Entry_RX-89persist.wimax.Entry_CINR4persist.wimax.Entry_Delay300persist.wimax.Exit_CINR2persist.wimax.Exit_Delay2persist.wimax.0.H-NSP-ID000004persist.wimax.OperatorNameSPRINTpersist.wimax.PollingIntervalpersist.wimax.Primary.Namepersist.wimax.Primary.ActivatedFALSEpersist.wimax.0.METHOD-TYPE13persist.wimax.0.VENDOR-IDpersist.wimax.0.VENDOR-TYPEpersist.wimax.0.USER-IDENTITYmarkarmstrong08@sprintpcs.compersist.wimax.0.PSEUDO-IDENTITYpersist.wimax.0.PASSWORDvh369tpersist.wimax.0.REALMsprintpcs.compersist.wimax.0.USE-PRIVACYpersist.wimax.0.ENCAPSpersist.wimax.0.VFY-SRVR-REALMTRUEpersist.wimax[/email].0.S-RLM.0.S-RLMsprintpc

Same here. Well..same as Cordy :) I'll try a nandroid restore and see what it looks like. Ive got an old one here somewheres...
[EVO 4G Android Development] TrevE:
:) curious did you wipe when you flahsed wimax?

I would pull all of /data/wimax. its looking like Boot.bin contains our mac and wimax_properties contains your username and password to connect. im guessing somehow ours got blown away so its reverting to the defaults in the .img file.
[EVO 4G Android Development] Cordy:
I always wipe first. ;) and I will pull the whole folder once I boot back up

Edit: So the Evo must hate me as I nandroided back to a previous rom and guess who shows up with me, mr. generic mac address.
[EVO 4G Android Development] TrevE:
and your sure thats before you flashed wimax? hmmmmmm can you do that wimax version test? did it revert to previous(not sure if nandroid touhcves wimax)
[EVO 4G Android Development] RavenII:
The mac address shouldn't have changed so easily, and it more than likely won't be as easy to change back...seeing as how it's the only authentication method for 4G...changing the mac would mean you could easily get free service.
[EVO 4G Android Development] redsolar:
http://xdaforums.com/showpost.php?p=7017988&postcount=246 link to the actual post, since I use max posts per page, had to scroll up and down.

Will test it in a sec, I have successfully downgraded my wimax firmware back to 4.6.2.2_v24722 (and radio to .04.26) and testing re-provisioning, to see if my mac gets properly switched back.
[EVO 4G Android Development] Cordy:
Yeah, trying a second one I have, they're both from when I first rooted the Evo earlier in the month.

Edit: Second one same thing.
[EVO 4G Android Development] TrevE:
someone back a few pages was able to change it by using vi against the wimax image... lol im guessing they figure if your registered on the network with 4g you have axx to data anyway...

If you look at dmesg you can see it pulling mac addy right out of Boot.bin this somehow has to be related...
[EVO 4G Android Development] mpa4712:
I also did a nandroid back to fresh 0.3. Here's a split screen of my boot.bin and wimax_properties..
[EVO 4G Android Development] TrevE:
dude i wouldnt have posted that, its got your sprint pcs username/pass in it..
[EVO 4G Android Development] myndwire:
man, unless that can be dynamically set automatically, we're in for some bs.. has anyone mucked with the new wimax patch from the thread? i'm feeling it may end up doing the same thing...
[EVO 4G Android Development] sjwaste:
I wiped, redid Toast's Part 2, and then flashed back the stock RUU. I'm back on 4G now!

Is there a safe method to fully update? If not, can I safely install 3.2.2.1 without the radio/wimax patches and still have 4G?
[EVO 4G Android Development] Emrys_90:
I just used the newest signed copy of the WiMax flash image, and now my doing the whole wimax_mxd or whatever it was shows I have the latest version. However, 4G is still stuck at scanning it seems.
[EVO 4G Android Development] TrevE:
do you have the borked mac addy?

im flashing it now :)
[EVO 4G Android Development] myndwire:
got my fingers crossed!!
[EVO 4G Android Development] TrevE:
im going to try 2 ways, first with my stuff in place, then im going to whack that /data/wimax

nandroid does bring back to older wimax revisions right?
[EVO 4G Android Development] mpa4712:
That's the least of my problems with 4g right now :)

Can the data/system img files from the nandroid backups be extracted without actually using a restore? I want to extract the files locally here to see what they look like before init.
[EVO 4G Android Development] TrevE:
you could nandroid, after nandroid is done go into

adb shell

mount -a

then pull the files.
[EVO 4G Android Development] mpa4712:
Didn't bring mine back.
[EVO 4G Android Development] mpa4712:
going to manually wipe each partition and then do what you suggested..
[EVO 4G Android Development] Decoil:
Nandroid backs up cache, data, system, and two others. Notably not wimax.
[EVO 4G Android Development] TrevE:
im nandroiding now and am going to just whack the boot.bin with my old wimax revision and then reboot. i want to see if it falls back to that "Default mac". then ill run a few tests on the new wimax.
[EVO 4G Android Development] Danny DiMarzio:
YES!

Profile and Prl Update works for me....... Yaayyyyy!
[EVO 4G Android Development] mpa4712:
I wiped /data and /system, restored a nandroid backup from 6/20 and then pulled all of /data/wimax and my boot.bin and wimax_properties both have the correct (non dev) mac...

let's see what happens when I go through init..
[EVO 4G Android Development] Cordy:
Well we are making some progress, I pulled the files as soon as I nandroided (without booting back into android) and my original boot.bin showed up!

Edit: I can now confirm nandroiding does initially resotre the wimax folder in data however booting into android replaces it with the generic one.
[EVO 4G Android Development] mpa4712:
That's exactly what I found to be true as well.

Anyone have a quick link to the old wimax? I want to do my nandroid restore, then restore that old version before going through init to see if it will stick.
[EVO 4G Android Development] TrevE:
what if you slip in your good copy after you boot to android with 4g off? can you sneak the files in there? i wonder wtf its replacing those copies with defaults
[EVO 4G Android Development] jdawg0024:
I got a new problem now... I installed 3.2.2.1 earlier today and did reinstall all my apps via the market. Now I cant install anything from the market at all I get an error saying insuffecient storage. (I have 301MB on internal) I have tried a dozen different apps to make sure it wasnt one app.

all was working earlier

Edit: Nevermind seems to be working now... Took about 4 reboots to get it working again... Maybe a market issue?
[EVO 4G Android Development] Cordy:
I'll test in a few if what I'm testing doesnt work, I'm seeing what happens if I nandroid restore, then immediately flash the eng rom. Also from looking at it, the Boot.bin and wimax_properties are probably both needed. The mac in properties matches that of the back of the phone/box and the one in boot.bin is almost identical with the last number being one less.
[EVO 4G Android Development] TrevE:
I just flashed http://xdaforums.com/showpost.php?p=7017988&postcount=246

my findings is this. i had 4g on when i flashed. i did not wipe data or anything

initial boot to android /data/wimax/wimax_properties had some settings in it, but it was stripped down to what i initially had. noteably there is NO username / password entered. wimax_mtd shows me at new revision. Mac addy looked the same. i updated profile. Now the file is blank??? I tried turning off and turning on 4g and it wouldnt turn on. ut oh

i rebooted. looked at wimax_properties again. This time it has more info in it like my sprint username/pass. i cannot verify 4g, but i can verify its scanning and did not wipe out mac...
[EVO 4G Android Development] mpa4712:
This is interesting..

I reformated /system and /data.

restored a nandroid backup from 6/20. I checked out wimax_properties and boot.bin and they both had my correct MAC address.

However, doing a wimax_mtd before booting the phone up still shows the new wimax installed. I think if I can sneak in the old wimax before booting, I can get the old MAC to stick. Anyone have the old one?
[EVO 4G Android Development] TrevE:
what if once you have the old files with your correct mac you flash the new wimax zip file?
[EVO 4G Android Development] jrmithdobbs:
Think I have a fix.

I modified the broken img file to have 1 less than my real mac address instead of the default in both places where it appears (just with vi). Then re-flashed it.

Then I flashed all the way back to the original RUU and am going through the root process now.

I checked boot.bin and wimax_config before flashing the engineering build and they had the correct values. (made backups)

I'm up to having the engineering build flashed on there. I'm getting **** signal since it's got the 1.32 radio on it at the moment but it is reporting the correct MAC and it is *attempting* to connect to sprint (signal is very low in my apartment) without turning wimax on/off over and over again.

Next I'm going to wait for the battery to charge to safe levels then finish the nand unlock, do the 1.39 radio update, and restore my nand backup from be for .47.

Edit: Going back to the engineering rom also successfully downgraded wimax:

Check Firwmare Version (4.6.2.2_v24722) ........ 4.6.2.2_v24722
[EVO 4G Android Development] Cordy:
You can pull it from the eng rom you used to root.

@TrevE I tried replacing the files with 4G off then turning it back on but it still reverted to the default
[EVO 4G Android Development] mpa4712:
In will try that next.

What is even more interesting is that after I ran the wimax_mtd, the boot.bin and wimax_properties files received the dev MAC. No boot, no init. They had the correct MAC before I ran the wimax_mtd
[EVO 4G Android Development] TrevE:
gah im not drunk enough to think about this crap, it makes my head hurt. cant imagine what someone coming halfway through the game must think./
[EVO 4G Android Development] Cordy:
No go either, nandroided then flashed still reverts.
[EVO 4G Android Development] redsolar:
So it looks like we have a segfault on our hands...

After which Wimax will reboot

The above is a result of a logcat on a device which is running 3.2.2.1, latest wimax and latest radio, with ipdated PRL and Profile through System Updates....

I am going to try permissions fix next, but those who have 4G working, and locking in - can you try running one cmd window with

adb logcat > c:\logcat.txt

and another window - issue a reboot command

adb reboot

So we can compare what's going on

PS I did flash the "fake" image file in which I decremented by 1 my MAC to get my mac that's on the label behind the battery.

I am now getting a correct MAC, but still no 4G