yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] TrevE:
*shrug* i have no clue what that command actually is for. i found it by just running anythign wimax related in /system/bin when we were looking for version.
[EVO 4G Android Development] itmustbejj:
It wasn't doing it in my logcat from yesterday...but I have seldom tried to enable 4g. So maybe it just shows up after you enabling 4g, even after it is turned off

Edit: it's gone after rebooting
[EVO 4G Android Development] mpa4712:
Word..I'll work with that one next. Need to upgrade to the new OTA files first...

The problem with writing your own MAC into the Boot.img file in /data/wimax is that file is not static. If you run a a wimax_mtd, or reboot, that Boot.img file will be generated again.

You should be able to do a temporary restore of your MAC by turning off 4G, writing your MAC into the Boot.img file /data/wimax, then running a update PRL. Once done, if you turn 4G on, your MAC will be what it should be. Don't run a wimax_mtg though. For those that know they have 4G, this is a good way to test it.

The more concrete solution is the one I came up with last night in which the MAC can be restored and persist through reboots. It's not pretty, but here's what you need to do.

1. Download the wimax flash for your current version of wimax. I'm on 24722 at the moment, but I think either should work. You will want to open up the IMG file for that wimax and replace the default MAC with your own, minus 1. So, if your true mac ends in B1, you'd enter your MAC with B0 at the end.

2. Add the IMG file that you just modified back into the zip file that you are going to flash through recovery. Put the zip file on your SDcard.

3. Reboot into recovery. When you are at the recovery screen, go into a command prompt and run:

adb shell mount -a

4. Next, open up an adb connection:

adb shell

5. Remove/delete your existing Boot.img that is in /data/wimax:

#rm /data/wimax/Boot.img

-or-

# mv /data/wimax/Boot.img /data/wimax/Boot.img.old

6. Go back to your recovery and flash the wimax update from the zip file you put on your SDcard. Once it is done, boot the phone back up.

7. Now, lets check and see if your hacked wimax file worked:

go to your command prompt and run something like:

adb shell pull /data/wimax/Boot.bin C:\wimaxfiles

8. Open up the Boot.bin file and see if your true MAC is there. If so, you should ok to reboot/turn on 4G/run a wimax_mtg

Some problems you might run into is that a lot of these wimax update files floating around here aren't actually updating anything when you run them. If you reboot and you have the 00:16 MAC, that is likely the case. I can provide my files later on if needed.

Now, I don't know that this actually restores 4G!! It is, however, a big step in the right direction for those of us that messed up our MAC. IF you are in a 4G area, please test it and let me know.
[EVO 4G Android Development] Cordy:
If you check out the beginning of the log when running the wimax_mtd it scans parition 7 finds that it's the wimax parition opens it and then prints out that information. So it's safe to say this is why we are having issues, the wimax partition is flashed with that damned default mac address
[EVO 4G Android Development] david279:
@mpa4712 what did you use to edit the wimax.img file?
[EVO 4G Android Development] Cordy:
Yeah last night I figured out it would not stick and would be regnerated upon reboot, I PM'd that info to TrevE this morning. And as I figured we'd have to hardcode the value into the wimax image being flashed to the wimax partition as it is what is showing the default address. also you keep stating boot"IMG" I assume you mean Boot."BIN"
[EVO 4G Android Development] Franteeko:
Question about updating.

Please bear with me as I am really nooby to this whole thing. I flashed yesterday doing the simple 123 method and loaded damage control on my evo. I'm enjoying it so far. For some reason i didnt load the newest version on it. I'm running 3.1.2.

It took me most of the day yesterday to root, unlock nand, and flash DC as well as reload all my apps and set up the phone the way I had it (I didnt start using the simple 123 method). I would really hate to have to do all that over again.

My question is two parts:

1.) Using the simple123 flashed clockwork. To patch am I supposed to load into recovery and flash the update over the already installed rom? Do I need to wipe factory/dalvik? And if thats the case, will my phone loose all the apps I have and settings I have for everything (keyboard, brower, bookmarks, wifi etc...)?

2.) I'm certain I need to flash the new radio updates. Reading the thread about the new radio version it says I need to have the system files from the 1.47.651.1 OTA sprint released update. Should I update to the new DC version and then do the radio update? How should I approach this problem?

Thanks for help xda =)
[EVO 4G Android Development] itmustbejj:
I did not wipe from 3.1.2 to 3.2.2. General rule of thumb for me is if you switch from one rom to another (Flipz to DC) then you should wipe everything, but if you are just upgrading to a different version of same rom you can usually get by without wiping unless it was a major revision. This is at least true for Damage Control in my experience.

Just know that if you run into any issues after flashing without wiping, you can normally know why. If I was you, I would update to 3.2.2.1, flash the radio

and stay away from the wimax flashing until this whole thing is ironed out.

Edit: I flashed the radio update from neotelos
[EVO 4G Android Development] Fixter:
Damn it to hell. I wipe data and Dalvik to reflash 3.2.2.1 to flash the new Aly theme and now I get a Error 131 and a whole lot of FC and I even rewiped and reflash and still the same problem!
[EVO 4G Android Development] sstory792:
You can update dc versions without wiping no problem won't loose anything but you will probably have 4g problems like the last 20 pages on this thread.

Edit: lol I type way to slow...
[EVO 4G Android Development] TrevE:
yeah somethigns wrong with aloysis still from what im hearing everywhere...

koni needs an evo
[EVO 4G Android Development] mpa4712:
This is likely..here are the mount points the system uses, I think the bold one is our daisy:

/dev/block/mtdblock4

/system	yaffs2	rw

/dev/block/mtdblock5

/cache	yaffs2	rw

/dev/block/mtdblock6

/data	yaffs2	rw

/dev/block/mmcblk0p1

/sdcard vfat rw

any hex editor will do.

Correct. I've been looking at these files so long, all I see is boot.* :)

I think though, there is a little more to it than that. If you hardcode your MAC into the actual IMG file for wimax, that won't work alone. The boot.bin file has to be MIA when flashing for it to take, in my testing at least...
[EVO 4G Android Development] nief1313:
So I upgraded to 3.2.2.1 flashed the latest radio and trying to update profile and PRL but everytime i hit update I get "Data call Failure Error code 131 .Sign-in Failed....."

any ideas on how to fix?
[EVO 4G Android Development] Franteeko:
Wow guys, thank you for the quick replys, itmustbejj and sstory. Is there any way to rep you guys on this forum?
[EVO 4G Android Development] redsolar:
I did something similar, however instead of playing with Boot.bin I forced the MAC -1 in the flashable wimax image. So far, no dice here.

I will post the instructions on how to break things shortly with file links, if someone feels like joining people with broken Wimax :)
[EVO 4G Android Development] bigbiff:
I just tried to reapply the 4g perm fix through recovery and got this issue too when updating PRL. wimax_mtd has may username in it.

Also I still cannot connect to 4g while OTA stock users in the same area can.
[EVO 4G Android Development] itmustbejj:
only if he flashes the wimax update after flashing dc 3.2.2.1
[EVO 4G Android Development] Fixter:
I never flashed the new Aly Theme. I just wiped and flashed DC 3.2.2.1 and I'm getting the Sprint Error 131 which is activation. The thing is that now with this new Radio. I can't go back to 3.2. Wth am I suppose to do now?
[EVO 4G Android Development] redsolar:
I am pretty sure that is SD card partition 1 (fat32 whether you have stock SD card or formatted it with fat32/ext2/swap layout)
[EVO 4G Android Development] rldev:
How do I check this. I have everything setup and properly flashed. But PRL and PRI updates fail. "Error Code 131 - sigin failed.Your pcsvision username or password may be invalid"

Thanks.

dmseg log:

7>[ 427.585998] wimax0: no IPv6 routers present

4>[ 432.218109] select 1089 (ufou.android.su), adj 15, size 4711, to kill

4>[ 432.218444] select 1153 (eautifulwidgets), adj 15, size 5217, to kill

4>[ 432.218627] select 1435 (s:FriendService), adj 15, size 5280, to kill

4>[ 432.218933] select 1501 (.qikffc.android), adj 15, size 5372, to kill

4>[ 432.219238] select 1791 (app.systempanel), adj 15, size 6029, to kill

4>[ 432.219390] send sigkill to 1791 (app.systempanel), adj 15, size 6029

6>[ 435.044677] sequans_xxx: tx_queue len 0, enabling netif_queue

6>[ 435.456268] sequans_xxx: card switched to DROPPED state

6>[ 437.215911] sequans_xxx: got RX data, card is not asleep

6>[ 438.856048] sequans_xxx: waking up the card...

3>[ 438.856567] mmc1: Command timeout (cmd=52 mci_st=00400004)

6>[ 438.866699] sequans_xxx: wait for completion (timeout 800 msec)...

6>[ 438.885650] sequans_xxx: card is waked up successfully

4>[ 440.467742] wds: 0020 @ 01

3>[ 440.468139] qmi: wds: network start failed (000e)

6>[ 441.031585] sequans_xxx: got RX data, card is not asleep

3>[ 449.369232] msm_pm_wait_state(2, 0, 0, 0) failed 11001

6>[ 449.369232] msm_sleep(): msm_pm_wait_state failed, 11001

3>[ 458.810699] msm_pm_wait_state(2, 0, 0, 0) failed 11001

6>[ 458.810699] msm_sleep(): msm_pm_wait_state failed, 11001
[EVO 4G Android Development] nief1313:
I think it might be the radio, I used the link that Flixter posted
[EVO 4G Android Development] Freelancerx:
wow ive been following damage control for a while now and i currently have version 3.2.1 on my phone, but this whole wimax mess is pretty ridiculous, ive been combing through this whole thread and it seems like there sooo much confusion going on, i mean we got a bunch of different versions of wimax files, tong of speculation about how to install and no real confirmed method that works properly. TREV if you know a confirmed way to upgrade damage control to 3.2.2.1 and the wimax as well as the radio, so that 4g is properly working along with all the latest update stuff can you PLEASE add it to your second post (along with link to the files that work properly)? if there currently is no solid info on how to do this without messing up 4g can you please state on your second post as well...right now it seems to be pretty hit or miss... perhaps its still too early to have a proper working update...so please if you can update the second post with some information to clarify things for the loyal damage control followers that would be great. for instance i would like to know if update to 3.2.2.1 and i DONT update either the radio or wimax will my 4g stop working? these are the sort things that would be nice as something to clarify.
[EVO 4G Android Development] sstory792:
Ya. I'm not really in the loop as far as the 4g goes because mn has none avail. I've just been confused by all this craziness!

Thanks for the info though
[EVO 4G Android Development] mpa4712:
Looking a bit closer, it looks like anything in /dev/block/ will be different for everyone, or at least not exactly the same. For example, in /dev/block right now I have:

# ls -l

ls -l

drwxr-xr-x root root 2010-07-01 11:14 vold

brw------- root root 31, 6 2010-07-01 11:14 mtdblock6

brw------- root root 31, 5 2010-07-01 11:14 mtdblock5

brw------- root root 31, 4 2010-07-01 11:14 mtdblock4

brw------- root root 31, 3 2010-07-01 11:14 mtdblock3

brw------- root root 31, 2 2010-07-01 11:14 mtdblock2

brw------- root root 31, 1 2010-07-01 11:14 mtdblock1

brw------- root root 31, 0 2010-07-01 11:14 mtdblock0

brw------- root root 179, 1 2010-07-01 11:14 mmcblk0p1

brw------- root root 179, 0 2010-07-01 11:14 mmcblk0

These seem like they are almost like tiny swap partitions for when you load up something that uses an image file. Might be able to modify /system/lib/modules/sequans_sdio.ko to mount these on /sdcard instead so we can see what's in them.
[EVO 4G Android Development] Cordy:
Ah so after you hardcoded your MAC into the WiMax image you still don't get 4G. curiously are you using the corresponding wimax ver for the appropriate sw version? I forgot where I found it before but the WiMax partition is a raw partition.
[EVO 4G Android Development] sparhawk6:
Question amidst the mayhem: can I flash the latest version of the ROM, the latest version of the radio (but NOT the latest version of WiMax), and still have 4g working as it was before?
[EVO 4G Android Development] Freelancerx:
would like to know this as well
[EVO 4G Android Development] itmustbejj:
no but feel free to pm me with any issues you have. I am happy to help and it will help keep the forum less cluttered while you get up to speed.
[EVO 4G Android Development] mpa4712:
From what we have heard, if you have the latest OTA files but not the latest Wimax files, then your 4g won't work.
[EVO 4G Android Development] chaseclear:
so i flashed 3.2.2.1, reboot, flashed radio via amon's recov, reboot, flashed wimax, reboot, (wimax flash didnt work) flashed PC36IMG through fastboot, rebooted, pulled the test.txt through adb shell and have my MAC and updated 4.6.2.2v25641.

Did I just get really lucky or something? Not understanding why others had there MAC changed? hmmmm

EDIT: I forgot to mention that I unpdated the prl and profile after doing each flash for good measure... could it be that this is what kept my MAC?!
[EVO 4G Android Development] Fixter:
I dont get this at all. I flashed the Radio and now it seems to be working. But I try to update the profile and it justs gets berserk and shows the 131 error for a couple of mins and then goes back to normal. Stupid. -.-
[EVO 4G Android Development] sparhawk6:
Darn. I suspected that.
[EVO 4G Android Development] icantdrawanime:
After stuggling to get wimax to update to the proper firmware version for most of the night, I decided to downgrade back to 1.32.651.6. I kept the 2.0 radio and have confirmed that my 4g works...
[EVO 4G Android Development] nebenezer:
fail :(

About an hour after this I had an actual complete reboot from the HTC splash screen.. just fyi

I'll repost settings once I tweak this a little more
[EVO 4G Android Development] Fixter:
Omg I'm so cool. I can fix my own mistakes. :cool: LMAO xD
[EVO 4G Android Development] TrevE:
guys i dont have 4g myself so i have nothing confirmed. if we come up with atleast a few people that can make a writeup on confirmed 4g process ill link it from post 2.

all i know is on the backend what needs to be in order for stuff to work.That is all the **** in here:

http://xdaforums.com/showpost.php?p=7020516&postcount=3826
[EVO 4G Android Development] Fixter:
To everyone having the 131 Issue:

Wipe, Data, Cache and Dalvik.

Flash 3.2.2.1 and Flash the Signed Radio that I posted back a couple of pages back. This should fix everything. :D
[EVO 4G Android Development] zikronix:
I dont have 4g in az, but followed this and everything is as expected. checking logcat and dmesg for errors now
[EVO 4G Android Development] Fixter:
Glad I was able to help. :P
[EVO 4G Android Development] kamiller42:
+1 on what this guy said.

I would be very appreciative if the DC team picks a release of the radio and WiMax patches, sanction it as compatible with DC, and put the links in the opening posts along with an overview of the installation steps.
[EVO 4G Android Development] Stickboy46:
Ok, my last post got lost in the 4G madness. How do you enable the FIXED Vanilla lock screen without breaking the power button (like in freshs new rom)
[EVO 4G Android Development] TrevE:
so fixter, do you have confirmed 4g?
[EVO 4G Android Development] jblazea50:
i was able to flash the wimax from this thread: http://xdaforums.com/showthread.php?t=715485

now i have the latest wimax under wimax_mtd check, but it is still in "scanning"; i updated profile/PRL after installing the wimax; also flashed the 4g fix by flip, but still scanning

not sure how some of you are able to get it on this rom
[EVO 4G Android Development] nief1313:
Agreed :D I would definitely love to see this when everything gets ironed out
[EVO 4G Android Development] Fixter:
I just booted up 4G. And confirmed the address with the one on ##DATA#. And the information there is the one that should be on there. So I don't see why it shouldn't work. But I dont have 4G signal nowhere near here.
[EVO 4G Android Development] PAPutzback:
Noob? Why can't these apps, fixes, patches, radio be rolled into the ROM? Is it because the ROM might install them in the wrong order or they have prerequisites that need to be installed first.

I am coming from a Palm Treo Pro world and after installing a ROM we'd always have to install a ringer update. I never knew why.
[EVO 4G Android Development] mongoose8p:
I doubt it will I had the exact same info and it doesn't work for me
[EVO 4G Android Development] mercuryhayes:
anyone wanna point me to where i can get the apk for the android music app thats in this rom. (with thte different sized widgets)
[EVO 4G Android Development] sstory792:
It is in /system/app/Music.apk

I can't upload it from here but that's where you can get it...
[EVO 4G Android Development] jrmithdobbs:
I have progress. I had a 00:16:08* mac.

After flashing with a modified rom with my mac-1 set I fixed that, then downgraded the wimax firmware by flashing the engineering build.

I'm now back up on 3.2.2.1 with newest radio and wimax flashed (unmodified) and showing the correct mac address but I get this in the log file in /data/wimax/log/:

==========

12:11 40.210 >| OMADM/ WARNING >| Invalid tree reference: './WiMAX/WiMAXRadioModule/0/TO-FUMO-REF' points to './FUMO' which is not exist

12:11 40.382 >| OMADM/ detail >| Board name: 'HTC-CERC32'

12:11 42.478 >| OMADM/ SEVERE >| Polling server not deleted in a synchronized manner!

12:11 44.338 >| OMADM/ WARNING >| Node '.' at '' doesn't match DDF

12:11 44.394 >| OMADM/ WARNING >| There are no parent node '' for node '.'

12:11 44.396 >| OMADM/ WARNING >| Invalid tree reference: './WiMAX/WiMAXRadioModule/0/TO-FUMO-REF' points to './FUMO' which is not exist

==========

And I just keep getting 'scanning...' in a place I know has (weak) 4G coverage.

That value seems to be referenced in /etc/wimax/sequansd/DefaultTree.xml.

Can someone with working wimax with the newest wimax firmware give me a copy of that file from their device? There's no usernames/pass/macs listed in it. Also can you see if you have similar output in /data/wimax/log/sequansd.log ?
[EVO 4G Android Development] welrope:
Funny, i was going to ask the same. I am getting the same thing in my wimax log. Would love to have this output from a working 4g

Is the reference to the FUMO folder normal. that folder is on my card, and i think it is for the OTA updates, but it is empty.
[EVO 4G Android Development] Jonnei:
The radio is a risky thing to flash because it can brick a phone if done incorrectly. To minimize risk, ROMs don't include the radio, that way its only flashed when it needs to be updated.

I flash ROMS, sometimes, several times a week. I'm glad I don't have to worry about bricking the phone that often.
[EVO 4G Android Development] TrevE:
OK so im doing some diffs on those xml files between version 3.2 (pre-ota) and 3.2.2.1 (post ota). the xml files in /system/etc/wimax/sequansd only had polling timeout changes, everything else is the same for the most part.

In sequansd_app.xml, the only one that seemed relevant is this

in 3.2.2 the line reads:

msstate none? does this mean no provisioning? Could this be why some people get wimax some dont, something to do with provisioining.... it makes some sense to me.
[EVO 4G Android Development] Stickboy46:
Is there supposed to be anything in DCUpdater? I have the newest DC 3.2.2.1 i think is the version. When i check for themes, i get nothing.

I go into Menu -> Configuration -> Theme Update Settings -> Manage Theme Servers -> Menu -> Update Featured Theme Servers and i get this

"org.apache.harmony.xml.

ExpatParser$ParseException: At Line 1,

Column 0: not well-formed(invalid token)"

Any ideas?
[EVO 4G Android Development] mongoose8p:
Honestly right now theres no reason anymore to be messing around with the new wimax - the radio is fine to use but wimax isn't worth it. There is no method that works overwhelmingly for anyone and at this point we should just wait for the ruu so devs can do an accurate analyzation. If you want to be on 3221 with new wimax try my "ghetto fix" it does work. It involves having the old wimax and new radio on 3221 and it works just you dont have upated radio
[EVO 4G Android Development] fallentimm:
Dude your on to something with 3221 my phone went into a screen when I first voted that looked exactly like update profile. I didn't think anything if it but I have working 4g with nw radio. I bet ita auto provisions hen its pushed.
[EVO 4G Android Development] TrevE:
i think this is enough confirmation for me. can someone remove that line from the xml and try to update profile or something? Why fallen got the update screen automatically and nobody else did idk but this seems promising...
[EVO 4G Android Development] Cordy:
Can't link threads on the phone but for anyone who had a bad MAC check out geniusdog254 thread. I'm at work so can't try it but as I figured you had to change the mac on the partition. He figured out the fastboot command for it. Will do it myself once I get home tonight.
[EVO 4G Android Development] jrmithdobbs:
Removing that line so it's like <3.2.2 makes no difference for me. (with a full restart of that daemon and unload/reload of the wimax modules)

Didn't try and update PRL/Profile. Doing that now.

No difference, still just get this over and over in logcat:

D/WimaxStateTracker( 629): GetAvailableMs

D/WimaxStateTracker( 629): GetAvailableMs

D/WimaxStateTracker( 629): GetAvailableMs

D/WimaxStateTracker( 629): GetAvailableMs

D/WimaxStateTracker( 629): GetAvailableMs

D/WimaxStateTracker( 629): GetAvailableMs
[EVO 4G Android Development] TrevE:
can you do an update profile, then reboot?

your macaddy is in order everywhere and your on the newest wimax too right?

what i think is interesting is somehow he was provisioned or something after update. that has to mean SOMETHING
[EVO 4G Android Development] jrmithdobbs:
Tried, no difference.

Yes, my mac address matches what's under the battery according to dmesg, wimax_mtd, about phone, and theres a /data/wimax/<macaddress>.tree.xml on my device.
[EVO 4G Android Development] ThornXBL:
Ok; I haven't done anything yet to be safe.

I see there are 2 (at least) newer versions of WiMax out there right now, after 4.6.2.2_v24722.

As far as updating PRL/Profile goes; how exactly would I do that if needed? Tried to search for it but couldn't find anything; it's probably right under my nose. >.<
[EVO 4G Android Development] bigbiff:
Reflashed radio and updated prl/profile and got rid of the 153 errors. Now getting the above error in logcat too.
[EVO 4G Android Development] jrmithdobbs:
More possible progress. I moved /data/misc/wimax/<mac>.tree.xml to .xml.tmp ... It regenerated the file without my correct sprint username/password in and is now doing the on/off loop but at least attempting to connect to sprint!

Going to try putting the correct username/password into the regenerated file.

That doesn't seem to have worked. Still doing the on/off loop instead of just scanning now.

Trying to update prl/profile again, reboot, and see if it fixes itself.
[EVO 4G Android Development] afitchguy07:
loaded 3.2.2.1 and splashscreen gif looped for the whole time i was doing p90x.. re flashed 3 times, same result. Outta control.
[EVO 4G Android Development] itmustbejj:
Where is the FUMO directory located and does anyone have anything in it?