yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] dudewithnofood:
I don't either but it has worked up until now. I used to use the hotspot app before I rooted and got tether. Not sure if it was affected by this update or no.
[EVO 4G Android Development] bstapley:
I flashed according to the instructions on the first post. I guess i didnt flash the wimax update or something b/c here's what I currently have:

Baseband: 2.05.00.06.10

Build number: DamageControl v3.2.2.1

Software number: 1.47.651.1

(the above is all normal)

but here's the weird part:

when i went to check my wimax version, i get this:

Check Firwmare Version (4.6.2.2_v24722) ........ 4.6.2.2_v24722

So it looks like I may have the older wimax from Toast.....

So my question is this: would you guys recommend flashing to the latest wimax or just sticking with this one until everything gets ironed out? I will be visiting a 4g area tomorrow, so i can test. If i dont flash to the latest, will wimax still work correctly? Also, if I flash to the latest wimax, will i have the potential of breaking my 4g all together? Thanks in advance for helping a poor junior member out! :)
[EVO 4G Android Development] gundamz2001:
I followed all the steps again without the permission step and dcpowertop is working again. Thank you very much for all the insights
[EVO 4G Android Development] VoXHTC:
Hmm..correct me if I'm wrong but if you don't live in a 4G area won't it just sit at "Scanning..." and do nothing else?

I've seen several people state 4G just "scans." do you have 4G? Otherwise what else would it do?
[EVO 4G Android Development] Krandor311:
Realized the problem was because I was using the the lockscreen fix from the Desire and not Flipz for his Fresh ROM, oops.
[EVO 4G Android Development] dpilcher:
Have been waiting for these to be updated. Great work K. Aloysius rocks on DC
[EVO 4G Android Development] dpilcher:
All answered #2 with a little reading...this Rom is unsurpassed....keep it up DT & thanks for the hard work.
[EVO 4G Android Development] nolandrew:
Holy Smokes! I got my 4G workin! I've been following this thread since Monday after the update. Treve was awesome fast to put up the new DC built from the update. = )

Then i worked through the new radio and wimax files...finally got the correct new wimax updated and BAM no more 4G ... I never had the mac change on me. I checked back tonight after a long day and checked Post #2 first thing cuz I knew if there was another fix Treve would post it and sure enough all the steps were there that i had done probably 5 times over but the last step was what fixed it...moving the tree.xml

So THANKS to everyone working hard on this and Treve for keeping up with it all and posting the results on #2.

I LOVE THE DC ROM! thanks damage and treve!
[EVO 4G Android Development] nolandrew:
I know this thread seems like a 4G thread now, but I have a question about the ROM and kernel. I'm still new and don't really know what the kernel is for. I searched the thread for "kernel" and read every post. I understand what the Godmode kernel is and don't want to try that out. But...

Is the Original DC Kernel on post #2 different than the EVO Stock kernel? Is it something necessary for the DC Rom?

I have 2.6.29-789bf291 htc-kernel@and18-2 #1...is this different then the DC kernel?
[EVO 4G Android Development] smw6180:
Yes and no. I couldn't get 4g to work WITHOUT the fix permissions from Flipz.
[EVO 4G Android Development] linflas:
For some reason DC updater says an update is available but I am on 3.2.2.1 so I am assuming it is wrong. Did not see a new update on post #2.

Thanks for insight, still figuring Android out. Very new to it.

sent from my telepathic bunghole
[EVO 4G Android Development] fallentimm:
Update is koni full color theme, awesome stuff!!
[EVO 4G Android Development] fallentimm:
Maybe flip last two steps around? Does your dcpowertop work?
[EVO 4G Android Development] smw6180:
Nope. The permissions on /system/bin are root shell. The group needs to be changed back to root, but unfortunately I haven't been able to get it done yet.

chgrp (or busybox chgrp) root /system/bin just returns permission denied.

As for changing steps around I tried a couple of different things...but now I'm reluctant to mess around again since I finally have functional 4g back.
[EVO 4G Android Development] fallentimm:
Yeah I think all your system bin permissions get whacked out including busybox and stuff.

Sounds like we need a more proper fix
[EVO 4G Android Development] sk63:
http://en.wikipedia.org/wiki/Kernel_(computing)

In a sense it is like an engine in a car, everything relies on the kernel to work.

As far as I know, the DC kernel is the same as the stock kernel. However, Damage and TrevE tweak some of the environmental settings in order to increase performance/battery life. They are not modifying and recompiling the the kernel though.

Now if you ever decide to replace the kernel in DC with a custom one, it *might* work so long as the modded kernel doesn't interfere with the settings DC tweaks.
[EVO 4G Android Development] linflas:
Thanks didn't hit the themes button

sent from my telepathic bunghole
[EVO 4G Android Development] itmustbejj:
agreed 10charsblahblah
[EVO 4G Android Development] itmustbejj:
This is the contents of the update script for flipz's 4g fix for what it's worth:

assert compatible_with("0.2") == "true"

show_progress 0.1 0

set_perm_recursive 0 0 0755 0644 SYSTEM:

set_perm_recursive 0 2000 0755 0755 SYSTEM:bin

set_perm 0 3003 06755 SYSTEM:bin/ip

set_perm 0 3003 02755 SYSTEM:bin/netcfg

set_perm 0 3004 02755 SYSTEM:bin/ping

set_perm 0 2000 06755 SYSTEM:bin/reboot

set_perm_recursive 1002 1002 0755 0440 SYSTEM:etc/bluez

set_perm 0 0 0755 SYSTEM:etc/bluez

set_perm 1002 1002 0440 SYSTEM:etc/dbus.conf

set_perm 1014 2000 0550 SYSTEM:etc/dhcpcd/dhcpcd-run-hooks

set_perm 0 2000 0550 SYSTEM:etc/init.goldfish.sh

set_perm 0 0 04755 SYSTEM:bin/su

show_progress 0.1 10

So I guess the magic question is how do we tweak this to not break 4g but still retain permissions for running commands and utilities

Update:

Here are all the users from the script with their ids:

0 => root

2000 => shell

3003 => inet

3004 => net_raw

1002 => bluetooth

1014 => dhcp

list of permission-denied commands I've found (as root):

dcpowertop

cp

grep

dcpowertop has these permissions:

-rwxr-xr-x root shell 107 2008-08-01 08:00 dcpowertop

which seems to be affected by this line:

set_perm_recursive 0 2000 0755 0755 SYSTEM:bin
[EVO 4G Android Development] mpa4712:
Mine is doing the same thing...

I have this in logcat everywhere:

E/Wimax ( 329): <DCP HEADER PROBLEM> proVersion is 17526

I/Wimax ( 329): <DC SOCKET READER DEBUG> Incorrect header was received

E/Wimax ( 329): <DCP HEADER PROBLEM> proVersion is 13671

I/Wimax ( 329): <DC SOCKET READER DEBUG> Incorrect header was received

E/Wimax ( 329): <DCP HEADER PROBLEM> proVersion is 29004

I/Wimax ( 329): <DC SOCKET READER DEBUG> Incorrect header was received

E/Wimax ( 329): <DCP HEADER PROBLEM> proVersion is 26704

I/Wimax ( 329): <DC SOCKET READER DEBUG> Incorrect header was received

E/Wimax ( 329): <DCP HEADER PROBLEM> proVersion is 25197

I/Wimax ( 329): <DC SOCKET READER DEBUG> Incorrect header was received

E/Wimax ( 329): <DCP HEADER PROBLEM> proVersion is 19010

I/Wimax ( 329): <DC SOCKET READER DEBUG> Incorrect header was received

E/Wimax ( 329): <DCP HEADER PROBLEM> proVersion is 14441

I/Wimax ( 329): <DC SOCKET READER DEBUG> Incorrect header was received

E/Wimax ( 329): <DCP HEADER PROBLEM> proVersion is 17237

I/Wimax ( 329): <DC SOCKET READER DEBUG> Incorrect header was received

E/Wimax ( 329): <DCP HEADER PROBLEM> proVersion is 21334

I/Wimax ( 329): <DC SOCKET READER DEBUG> Incorrect header was received

E/Wimax ( 329): <DCP HEADER PROBLEM> proVersion is 18290

I/Wimax ( 329): <DC SOCKET READER DEBUG> Incorrect header was received

E/Wimax ( 329): <DCP HEADER PROBLEM> proVersion is 20779

I/Wimax ( 329): <DC SOCKET READER DEBUG> Incorrect header was received

E/Wimax ( 329): <DCP HEADER PROBLEM> proVersion is 21357

I/Wimax ( 329): <DC SOCKET READER DEBUG> Incorrect header was received

E/Wimax ( 329): <DCP HEADER PROBLEM> proVersion is 29044

I/Wimax ( 329): <DC SOCKET READER DEBUG> Incorrect header was received

E/Wimax ( 329): <DCP HEADER PROBLEM> proVersion is 29268

Mine are already at 666. Should that file be root:root or wimax:wimax?

Has anyone who farked up their MAC address gotten 4G to work? I get a notice that 4G is available, then upon connecting I get 4G going on and off.
[EVO 4G Android Development] mpa4712:
This is interesting..I got the same write errors when I did a ##786# reset..It would be nice if it referenced where the error came from..
[EVO 4G Android Development] fifoloveritas:
Actually, I'd like to know this as well. It is a nice wallpaper, but I cant' find it...
[EVO 4G Android Development] nief1313:
anytime i download something using dcupdater and then click apply i reboot into a picture of a droid with an exclamation mark and i need to pull the battery to restart. The only solution i have came up with is to use rom manager to install the themes or patches that I have downloaded using dcupdater. Anyone have any insight on how to make it work with dcupdater?
[EVO 4G Android Development] fifoloveritas:
I had the same problem; ended up with booting to recovery and updating manually.
[EVO 4G Android Development] nief1313:
Yea I had this problem on 3.2 and now on 3.2.2.1
[EVO 4G Android Development] beerock:
here you guys go......here is your wallpaper, also attached another one I like....

On another note, what are the permissions supposed to be on the macaddress.tree.xml file?? If anyone has 4g working I would like to know what there permissions are on that file you can easily see them by using Root Explorer

/data/misc/wimax........
[EVO 4G Android Development] itmustbejj:
I nandroided to a previous version and checked the file and there were no permissions on it. It was ---------
[EVO 4G Android Development] beerock:
and your 4g was working on that backup? What version were you running on that one?

Do you have 4g working with 3.2.2.1?

Sorry for all the questions, and thanks for the answers itmustbejj
[EVO 4G Android Development] itmustbejj:
Actually you might want to disregard that. I think I loaded the wrong nandroid, doh. That was was 3.2.2 before flashing the radios, let me flash back to a 3.1.2 nandroid.

I do not live in a 4g area unfortunately.

Edit: I went all the way back to a DC 3.0 nandroid I had and I got:

---------- root root 201040 2010-07-02 10:35 001841xxxxxx.tree.xml

Doh I just looked at the date of that file....the nandroid is from 6-16 and that file is from 7-02 so I guess that nandroid doesn't include that file or it just got recreated over the top.....
[EVO 4G Android Development] beerock:
np...I think this is all a lost cause for me, I am not able to fix 4g (not enough skill/talent). Just have to wait till someone else figures it out... I refuse to waste another day on this. lol haha

But I do know the fresh 4g fix screws up things worse with 3221, Though I had it for a minute after running the fix permissions with Rom Manager saw my 4g icon for the first time in awhile but quickly it vanished. I knew this $10 extra was going to be a waste. /end rant. ;)
[EVO 4G Android Development] mikeleachone:
Boot Loops?

I've tried the two previous versions of this ROM and got boot loops. I re-installed 2 different stock rooted versions with no problem. I've been using toast method in all cases. I've always enjoyed "damageless" ROM's on my Hero and want to use this latest version. Anbody have this or similar issues? I've always wiped everything before flashing.
[EVO 4G Android Development] itmustbejj:
Yeah I am driving to Kansas City this weekend and I was hoping to get my first taste of 4g, but it looks like it might not be so...bollocks...

Did you say that fixing permissions with rom manager undid the permission damage of the flipz 4g patch?
[EVO 4G Android Development] fallentimm:
You have all not read post two

Clockwork does not work with updater.

Bootloops are because you aren't nand unlocked

READ!!!!!
[EVO 4G Android Development] TrevE:
This is a 4g fix that should work with dc. I think the issue is for people who have applied themes maybe things are getting out of whack? Not really sure and cant really test but if someone can verify if this works or not itd be appreciated...

this should fix issues of those who used flipz fix breaking powertop and such. it might fix 4g for other people stuck scannign still. I updated directions in post 2 of how i see this working. Let me know if she does the trick.
[EVO 4G Android Development] simzz:
Thanks for everyone's help.

Right now my biggest issue is that I can connect to 4G, but if I drop coverage for even a second, it goes right back to "Scanning". The only way to get it to connect again is to turn off 4G and back on again.

Anyone NOT seeing this?
[EVO 4G Android Development] itmustbejj:
So if we did the whole 10 step routine, just flash this overtop?
[EVO 4G Android Development] TrevE:
maybe :P i have no 4g so i cant test for myslef but thats what id assume would work...

Themes are also going back up in dcupdater!!!
[EVO 4G Android Development] E-MAC:
It seems like that's what is happening to me. I guess I'll give the 4g fix TrevE posted above a shot, but won't be able to test for a couple of hours.

My log looks like this:

OMADM/ WARNING >| [0mInvalid tree reference: './WiMAX/WiMAXRadioModule/0/TO-FUMO-REF' points to './FUMO' which is not exist

OMADM/ SEVERE >| [OmPolling server not deleted in s synchronized manner!

OMADM/ WARNING >| OmNode '.' at ' ' doesn't match DDF

OMADM/ WARNING >| [0mThere are no parent node ' ' for '.'

OMADM/ WARNING >| [0mInvalid tree reference: './WiMAX/WiMAXRadioModule/0/TO-FUMO-REF' points to './FUMO' which is not exist

Further down the log, there's also a severe warning 'DNS server returned answer with no data', and just below that 'Resolving WIB server is failed'.
[EVO 4G Android Development] TheMike1:
This was never answered, and I am having the same problem. Will someone shed some light on this?
[EVO 4G Android Development] TrevE:
yeah its not in there yet to move audio/texts to sd. the code is only given out to testers right now.
[EVO 4G Android Development] itmustbejj:
Well I will be in Kansas City with 4g in about 10 hours, I will let you know then :P

Thanks perfect timing, as I was able to push it right as I'm leaving.
[EVO 4G Android Development] TheMike1:
Thanks TrevE :D Currently using SMS Backup which is actually an awesome app, pushes your text messages to your gmail account under the label SMS. I recommend it to those who cannot wait for this to be functioning. Keep up the good work :)
[EVO 4G Android Development] nief1313:
Im pretty sure im nand unlocked.
[EVO 4G Android Development] beerock:
no offense to this thread or this rom, I love it and will be running it but I just wiped and flashed version 8 of baked snack and bam connected to 4g so not sure what the hell but Im sure it will get ironed out,

Flashing back 3221 right now, just wanted to make sure 4g actually works. I still think it sucks though, horrible signal strength in home, spotty and really fastest ive ever got was about 2.x mbps/1.x so fooey Ill just stay on my wireless N and call it a day
[EVO 4G Android Development] pastert33:
I just installed this, as well as did a PRL and Profile update and I still don't have 4G. I know I'm in a 4G area BC I've gotten it here before. Just stuck scanning.
[EVO 4G Android Development] simzz:
Beerock,

With Baked Snack, would the 4G stick, or if it disconnected would you have to turn 4G on and off again before it would connect again.

I am just trying to find a good 4G solution.

Thanks
[EVO 4G Android Development] itmustbejj:
Treve the dcproper fix for sure fixed my permission issues.will let u know about 4g when I get to KC later.
[EVO 4G Android Development] welrope:
anyone having issues buying apps from market? I can use market no prob, as long as i don't buy. IF so i get a FC..

Thanks and otherwise awesome rom!
[EVO 4G Android Development] TrevE:
gfdagadfgadfgad
[EVO 4G Android Development] Criimson:
I am DLing the new version right now and will let you know if I can get 4g. I live in Seattle and it is a 4g area.
[EVO 4G Android Development] fallentimm:
I just flashed baked snack and my speedtest.net results were slower? Actually if you diff wimax files in lib and bin calkuin listed he used preota files it seems. They crc the same so you won't get benifits of ota, increase in speed

This is why it works no problem my guess. Dc makes use of all ota patches as confirmed by calkuin

EvenMore proof in baked snack look in system etc init.d placeholder.

Its got flipz tag in it. He used his system dump
[EVO 4G Android Development] Emrys_90:
TrevE, did the whole 10 step thing and was still stuck at Scanning. Just applied your new patch and it still is stuck at Scanning.
[EVO 4G Android Development] TrevE:
repeat the last 2 steps and try these attached files

oh yeah make SURE You update profile at the end and the nreboot if it doesnt work.
[EVO 4G Android Development] rehh:
Booting into Flash recoery with simple root, installing zip from there, will let you know in minute, no themes applied.

No fix for me. I applied this fix last night http://xdaforums.com/showthread.php?t=715525 and now my 4G doesn't connect at all, was connecting for a minute or two on every reboot before.
[EVO 4G Android Development] beerock:
pfffhhf, I really hate this thanks to simzz..lol I went back to check and it wont connect again so I guess baked snack no better, only worked once.
[EVO 4G Android Development] halorin:
I'm on Baked Snack v8 right now. 4G will connect after a few scanning, obtaining loops. If I move out of 4G I will need to turn 4G off and back on to get it to work again. I'm in Alexandria, VA so I doubt I'm in an official 4G spot.

To clarify, I'm on the latest radio and wimax after using using that stock to latest ota root method whitslack put out.
[EVO 4G Android Development] TrevE:
gah i relaly dont know about the peopel who had F'ed up MAC addys. i havent looked into that fix yet. I know that process in post 2 helped alot of people here that wernt borked before...
[EVO 4G Android Development] iceat:
My 4g scans now and tries to connect but cannot obtain the IP address.
[EVO 4G Android Development] TrevE:
with what patch? can you

adb logcat

adb shell dmesg

and get me the results of just turning 4g on, scanning, and the failure?
[EVO 4G Android Development] Just_s:
When I try to do this :

I get back this:

Any thoughts?
[EVO 4G Android Development] iceat:
Im running the latest from 3.2.2.1 and all the new radio wimax, did the whole ten step deal...

Ill get a log here in a bit.
[EVO 4G Android Development] TrevE:
even i have more stuff in there than that and i havent used 4g. can you flip the radio on and see if it gets generated?
[EVO 4G Android Development] TrevE:
yes but after the 10 step deal read back a few posts. t heres 2 additioanl patches.

have you EVER had a brokenn mac? have you verified your stuff is OK and your username/pass are correctly entered?
[EVO 4G Android Development] Emrys_90:
Deleted the file in /data/misc/wimax/ then went into Recovery and flashed your fix2. Rebooted and updated Profile then rebooted again, still stuck at Scanning.
[EVO 4G Android Development] TrevE:
Im updating post 2. From now on we will require the following for any error report

DC 3.2.2.1 works for alot of people with 4g if you read back through the posts. there has to be something everyone else is missing...
[EVO 4G Android Development] rehh:
never had the mac addy problem, mac been good for me the whole time.

Been trying all the diff patches and fixes. everything working but 4G.

guess I might try a wipe/clean install again with 3.2.2.1 and if no go, then wipe/clean and go back to 3.2.1.
[EVO 4G Android Development] pastert33:
Just tried the 2nd fix and still stuck at scanning. If it makes any difference, my wimax code is the same as the one on the back of the battery so I don't know whats the deal.
[EVO 4G Android Development] iceat:
no MAc never broken, and as far as I know wimax_mtd my username passowrd is good.

Ill check back on the two new patches
[EVO 4G Android Development] Just_s:
Rebooted, tried again and all good. Now if I can just get back to a 4G area and test it :)
[EVO 4G Android Development] redsolar:
I have been doing some more testing with an evo with a working 4G on it.

The ERROR_1 is present when doing Profile update, as well as DC Header notices in logcat, so that's likely not our issue, since it appears on both working and non-working 4G setups.

I have compared the /data/wimax files, and they are mostly identical, except for Boot.bin file. The one on non-working 4G is smaller, and is missing a large chunk of plain text from its end.

I am attaching both files, maybe someone will have some additional insight into it.

Replacing it on a non-working evo does not fix the issue, and it's overwritten on reboot. If you are going to try replacing them, please make sure to edit the MAC address in the file, to be your MAC - 1, just like before.

I am currently back to DC 3.2.1 where I used to have working 4G (not anymore) so that the software is at least partially comparable to the working evo, which has only been part 1 unlocked (i.e. no NAND root applied) and is running a .6 update at the moment.

wimax_mtd returns largely the same results, other than MACs, passwords and usernames, as well as "Dump BOOTS firmware" size (which is what got me looking at Boot.bin sizes in the first pace). Both also segfault at the end, so I guess that's not a big deal either in getting 4G back.

If someone with a working 4G can take a look at their /data/wimax/Boot.bin size (or send their Boot.bin to me so I can do a diff compare), that may also provide some useful information.

Note, although files have a .zip extension, they are not zipped, just as is, since the forum doesn't allow .bin attachments :)
[EVO 4G Android Development] itmustbejj:
Has anyone tried whitslack's method and flashed DC on top? His method sounds legit.

Would try if I was at a computer
[EVO 4G Android Development] TrevE:
use dcupdater. show all roms in settings, aslong as you dont have clockwork your good.
[EVO 4G Android Development] itmustbejj:
Beerock ever heard of attatchments? :p
[EVO 4G Android Development] itmustbejj:
Clockwork here :(
[EVO 4G Android Development] fallentimm:
http://xdaforums.com/showpost.php?p=7032384&postcount=182

For those of you stick scanning are you sure you removed that tree file? Even people on official ota have this problem and that us always fix
[EVO 4G Android Development] Vandam500:
I really want to flash this ROM but so many people are having so many problems with the 4G. Its a real shame really because 3.0 was so solid. Hope there is a definite fix for the 4G issue soon.
[EVO 4G Android Development] beerock:
no who is attachments? Is he/she nice? Can they fix 4G? :D
[EVO 4G Android Development] nief1313:
he is talking about adding an attachment to your post of your log so you dont make us have to scroll so much. you can do this in a few ez steps:

click 'post reply'

click 'manage attachments'

select your attachment

click 'ok'

type your reply

finally click 'submit reply'

Follow these easy steps and you too can post attachments :D
[EVO 4G Android Development] ThornXBL:
Pretty sure he was being sarcastic ;)
[EVO 4G Android Development] beerock:
ha wow! u guys....... :P
[EVO 4G Android Development] nief1313:
im pretty sure who ever typed up that guide was probably being sarcastic too. not sure though, just guessing :D
[EVO 4G Android Development] ThornXBL:
Heh, perhaps. It's Friday on a holiday weekend; happy thoughts.
[EVO 4G Android Development] beerock:
funny...funny :D
[EVO 4G Android Development] whyviet:
I've rooted/nand unlocked via Toast's tutorials and followed the steps to install DC 3.2.2.1.

My 4g isn't connecting.

All I get in logcat is:

D/WimaxStateTracker( 346): GetAvailableMs

D/WimaxStateTracker( 346): GetAvailableMs

....

Does this mean I'm out of range of any service? FYI I live in a 4g city (Dallas).

Thanks in advance!