yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] ewells38:
Here you are ;)
[EVO 4G Android Development] TrevE:
cool ill check it out in a sec. at work now need to do a bit of somethign today :P
[EVO 4G Android Development] jblazea50:
thanks, do i just flash this in recovery?
[EVO 4G Android Development] shawnten:
what all do i need to wipe for this rom coming from stock rooted 1.39
[EVO 4G Android Development] TrevE:
awesome glad i dont havta fix anything :)

i like logcat too, i kinda wish i could get logcat on boot instead of a bootscreen :) i saw a logcat lwp but on hero it just made me dizy
[EVO 4G Android Development] TrevE:
so just to confirm 3.2.2.1 + that 4g permission fix made your 4g work again?
[EVO 4G Android Development] asrebel:
Just an FYI: It didn't for me. I'd be happy to send you another logcat if you want.
[EVO 4G Android Development] jrpointer:
doesn't look like it.....it works for a while than drops out for no reason......now I'm stuck back in scanning mode???? its really odd because it at least lets me connect so 4g can't be completely broken
[EVO 4G Android Development] TrevE:
and your on this wimax and radio right?

http://xdaforums.com/showthread.php?t=713770

if so yeah send me a logcat.
[EVO 4G Android Development] IAMCLP1:
I just configured those settings rebooted the phone, and now it wont load past the 4G startup screen ... I was sitting on this for about 7-9 min's, I pulled the battery only to watch it do this all over again -

Thoughts before I flash recovery?
[EVO 4G Android Development] itmustbejj:
Does BluetoothHandsfree always run even when bluetooth is off?
[EVO 4G Android Development] gessin64:
Yeah i confirmed its the updated Aloysius Theme - DamageContol 3.2.2 causing the force close on the gallery while attemping to play videos and also on some HTC process.
[EVO 4G Android Development] qteezyfosheezy:
Cool i was just going to ask about that.. well goodbye aloysius theme :(
[EVO 4G Android Development] rldev:
Hmm. I tried the radio updates, but my update PRL or Profile no longer work. They do nothing when I press them. I try to go back to the NAND backup I made before applying the radios but the baseband is not changing. Am I missing something? Shouldn't the Baseband revery back to the prior version on a NAND restore, or do I have to flash the old radio back to test? ASt this point I don't really know if the prl update worked prior to this specific update.

Turns out it was startup cleaner blocking a service. I still don't have 4G, stuck scanning. I will check my friends stock evo tomorrow.
[EVO 4G Android Development] TrevE:
yeah i see it all the time seems its something in phone.apk. happens on every rom ive seen.

cool - good detective work :P post over in koni's thread hes the man im sure hell get ti fixed.
[EVO 4G Android Development] mrono:
Oops wrong thread.
[EVO 4G Android Development] asrebel:
Yes, I'm on that wimax and radio. I just pm'd you the logcat info.

Thanks for your help!
[EVO 4G Android Development] smw6180:
I'm also in philly right now. 4g is fine

On 3.2.1, not on 3.2.2.1.

--Sent from my Evo 4g.
[EVO 4G Android Development] mongoose8p:
I can confirm 4G does not work with the updated radio/wimax on 3.2.2.1 but IT DOES work with the updated radio/wimax on 3.2.1 sooo somethings changed with the update thats killed 4G even with new radio/wimax
[EVO 4G Android Development] itmustbejj:
On a completely unrelated note, does anyone have any bootanimations they really like? We can carry the discussion over to PM, but I'm struggling to find one I am really happy with.
[EVO 4G Android Development] TrevE:
ok im freekin confused here.

3.2.1 == older sprint release

3.2.2 == new OTA.

From what ive read new ota wimax cannot be used with older release without the new system files. what your saying is contradicting alla that. are we sure wimax is getting updated here? this all makes my head spin...
[EVO 4G Android Development] mongoose8p:
I have run both the radio/wimax update SEVERAL times so I'm fairly confident it is applied. I have also tried wiping to 3.2.2.1/updating to 3.2.2.1 literally everything with no luck. The only fix for me is the new radio (if you want screenshot) and wimax on 3.2.1... im as confused as you are.
[EVO 4G Android Development] IAMCLP1:
You have been cut off from beer ... or maybe you need more? Wait didn't you say you were at work? :D
[EVO 4G Android Development] tatnai:
i don't think it was being updated; a new wimax update was added here just before noon that is supposed to actually update, unlike the old one. so if you had to return to 3.2.1 it may be because you were NOT updating wimax when you thought you were, so you had to return to the old baseband to have it work. run the new one and post back, I don't have wimax in my area.
[EVO 4G Android Development] SouL Shadow:
From a different thread, looks like the wimax update was missing a step in the flashing. Some ppl got it to work and others didn't. I'm just guessing, but based on ppl's posts I think clockwork recovery wasn't flashing right and amonRA was (as long as you had the signed zip).

If wimax wasn't flashing that would explain why 4g was only working on the old system files. (like radio, wimax flashes to it's own partition, so it's unaffected by the different rom flashes)

I haven't tried any of this yet and don't have 4g coverage in my area so I can't confirm anything, just passing along what collectively read in various threads.
[EVO 4G Android Development] TrevE:
awesome - people with 4g issues listen to this guy he sounds like hes ontop of the game, thanks man.

http://xdaforums.com/showpost.php?p=7004269&postcount=3336

this is what iw as refering to from calkiun. so 4g on 3.2.1 should not work with new wimax files and 3.2.2 should not work with old ones if things are working properly.
[EVO 4G Android Development] myndwire:
that makes perfect sense -- the signed files are required for amon ra which most people are using i'm sure. i like how clockwork does nandroids, but as far as flashing stuff, i've had major issues with just flashing roms in the past and always go back to amon ra. i'm concerned though... if these files were updated around noon, the signed ones likely weren't...
[EVO 4G Android Development] Cordy:
I actually updated my WiMxax using Calkulin zip in that same thread. And 4G from what I tested is a no go for me.
[EVO 4G Android Development] myndwire:
signed or unsigned? clockwork or amon ra? that's the test that we need you guys in 4g markets to try.

1. do 3.2.2.1 (wiping first)

2. flash new radio (signed zip) in amon ra

3. flash over new wimax (signed zip) in amon ra

4. test 4g

also, it may be prudent to go through this procedure with the unsigned files (or even both sets) with clockworkrecovery and see what the outcome of both are.
[EVO 4G Android Development] TrevE:
can someone who thinks they updated wimax try this?

adb shell wimax_mtd >c:\test.txt

im not sure if this is a true test, but from what i see:

im guessing fw version shoudl be increased on new wimax. im on the old one i have not touched update yet.
[EVO 4G Android Development] Cordy:
I did a clean install this morning. Using Amon_Ra 1.7.0.2 flashed Neotelos_com Radio which shows a baseband of 2.05.06.10 And used Calk's WiMax update.

Interestingly enough my WiMax version matches yours TrevE
[EVO 4G Android Development] jblazea50:
TrevE, any chance of uploading the stock kernel from 3.2.2.1? i tried flashing the 30fps uncapped kernel and it broke the touch screen, so i went back to the previous stock kernel i had (3.1.2 i think) and now my wifi doesn't work;

so i'm assuming if i get the stock kernel from the latest rom, it should be fine

thanks
[EVO 4G Android Development] ssgelm:
Flashing the zip that CalKulin provided at http://xdaforums.com/showpost.php?p=7003714&postcount=116, I get:

Check Firwmare Version (4.6.2.2v25641_) ........ 4.6.2.2v25641_
[EVO 4G Android Development] runner77:
I nand back to 3.2.1, still running the new radio, and I'm posting this using 4G.

What do you need me to test Treve?
[EVO 4G Android Development] Cordy:
Interesting, I'll try it once more, curiously what recovery are you using?
[EVO 4G Android Development] ssgelm:
Clockwork.
[EVO 4G Android Development] myndwire:
which zips did you use, the signed or unsigned? i think clockwork doesn't have the signed requirement.
[EVO 4G Android Development] Cordy:
Thats just what I thought. Even though I prefer it there seems to be a recurring issue with using Amon_Ra's recovery with these radio flashes. Calk's zip is signed otherwise Amon's recovery wouldn't let it run.

Edit: I switched to toasts recovery just to test this out and applied Calk's WiMax update and it still doesn't seem to have taken, still shows the same version number as TrevE's.
[EVO 4G Android Development] TrevE:
OK now were getting somehwere. some people who are flashing wimax are not getting updated. i think this is causing confusion . seems that check is valid for wimax revisions.

*Edit* - Here is my testing theories for 4g. if your 4g does not work make SURE you are on new wimax with this check. Then if it still does not work try the 4g permission fix. for 4g issues make sure you tell me what version of dc you are on, what version of wimax, what update.zips have been applied.
[EVO 4G Android Development] asrebel:
I got the latest wimax (performed the check you specified) and I've performed the permission fix...same result. :confused:
[EVO 4G Android Development] cj10488:
here is what I get

Scan MTD partitions ........ 7

Find WiMAX partitions ........ OK

Open WiMAX partition ........ ERROR

OK

[1] Segmentation fault wimax_mtd
[EVO 4G Android Development] fallentimm:
Im on 25641 and wimax works fine here
[EVO 4G Android Development] gtkansan:
Im trying to test out these but no luck. What is the adb command to test firmware versions for wimax?

To throw a wrench in, I was using the rooted 1.47 with the new radio and wimax flashed in. I did a system update, boom 4g works.

Then, flashed damage 3.2.2.1 and no 4g. Tried system update, no dice.

Then to be sure nothing went wrong with the flashing of damage (i.e. to mod the radio or wimax) I reflashed the RADIO ONLY and bang 4g is back and kicking.... So perhaps the radio is being overwritten by the damage install?

Oh and to everyone else, prior to this i was getting about 3 mbps on wimax in my office, now im getting 7 down and 1.5 up.... i love wimax.
[EVO 4G Android Development] Cordy:
Well it seems no matter which recovery I use and whether I use Neotelos_com or Calkulin's WiMax update I'm stuck at the same WiMax version. Very peculiar.
[EVO 4G Android Development] cj10488:
Nevermind seems after I flashed 3.2.2.1 it reads correctly.

Will be able to test out 4g here in an hour or so.

James
[EVO 4G Android Development] SnoopDawg:
I had issues but I was able to connect with WiMax today, using 3.2.2.

Here is the deal.

Scenario 1 -

You have WiMax and it goes up and down like a cheap ho, but you are able to connect. You could be on the old version.. 4.6.2.2_v24722 - where you should be rollin like Trey describes with 3.2.1. It will likely exhibit this behavior, unless you update the firmware to the newest version, with a ROM that has the most OTA files(you will have to make sure you match the oxed/deoxed rom of your choice.

Scenario 2 -

You have fallen and can't get up. You updated to 3.2.2.x and your WiMax is scanning.. This is the symptom that most people are complaining about.

Important note - the recovery piece doesn't matter, so don't focus on if you lose recovery, you can get it back.

CalKulin - Flash do work with the 3.2.2, I have updated and if you see my earlier threads, I was able to get > than 5MB D/L speeds.

I tried Neo's update and it was still scanning, this was my bad because I had rock solid WiMax. I have connected today, I may reflash CalKulin's just to make sure.

C:\evo-recovery>adb-windows.exe shell wimax_mtd |findstr /i check
Check Firwmare Version (4.6.2.2v25641_) ........ 4.6.2.2v25641_

EDIT: Funny stuff, I see that my assumptions match TrevE's.

EDIT 2: I was able to connect to 4G for a short time, where I am at the moment, I don't get a strong signal but I was able to connect to 4G after flashing again.
[EVO 4G Android Development] ssgelm:
In the latest bugless roms there is a "godmode" script that enables one to use astro as root. Any chance of getting this on DC? (Mainly cause not having tab completion in the shell drives me insane for moving files.)
[EVO 4G Android Development] jdawg0024:
having troube doing the test on what version I have

when running the code (through CMD on win 7 machine) i get

cannot create c:test.txt read -only file system
[EVO 4G Android Development] gtkansan:
Seems me too. I can connect, get good speed, but its fickle.

No matter which zip I use, wimax is not being written over to anything other than the 24722 one.
[EVO 4G Android Development] chaseclear:
okay so have wiped, flashed 3.2.2.1, reboot, flashed radio, reboot, flashed wimax, reboot... Everything looks great but I am trying to do the adb shell wimax command and I keep getting "access denied". Im pretty new to using the shell but i navigated to "c:\sdk\tools\" where adb and everything is located and try the command "adb shell wimax_mtd >c:\test.txt" but still get access denied. my device is synced and shows up when i do adb devices... any ideas? did i lose root? or did I lose nand unlock? sorry if super noob hmmm :confused: thanks guys
[EVO 4G Android Development] runner77:
Same here. I've tried both WiMax files and I'm still reporting the older version.

I'm running 3.2.2.1.

Maybe if I go back to 3.2.2??
[EVO 4G Android Development] TrevE:
ok snoopdawg def wins for the best post evar. but i think these confirm 4g will work with 3.2.2+ with the right wimax stuff. now the tricky part is figuring why some people get it some dont...
[EVO 4G Android Development] siverson612:
I'm in the same boat. No matter what I do I'm stuck with wimax v4.6.2.2_v24722. Any ideas what to try?
[EVO 4G Android Development] sk63:
Try adb shell wimax_mtd > ./Documents/text.txt

This should put the file in your document folder
[EVO 4G Android Development] jblazea50:
yup, seems like whenever i flashed neo's and/or caulkin's, the wimax version doesn't change therefore i can't connect

need to find out how to fix that issue and it should be working
[EVO 4G Android Development] TrevE:
glad i finally found that wimax_mtd command. seems like were making headway. im glad the DC stuff seems to be working too means we dont need another update :) phew.
[EVO 4G Android Development] linflas:
Same boat as you three

Scan MTD partitions ........ 7

Find WiMAX partitions ........ OK

Open WiMAX partition ........ OK

Get HTC WiMAX Tag ........ OK

Verify WiMAX Tag (HTC-WiMAX-SQN1130)........ PASS

Read WiMAX partition ........ OK

Check Firwmare Version (4.6.2.2_v24722) ........ 4.6.2.2_v24722
[EVO 4G Android Development] chaseclear:
thanks! so i have 4.6.2.2_v24722 firmware... :( i have amon_ra recovery.. and flashed both the radio and wimax from Neotelos... cant confirm 4g because im not in the city right now.. should i try a diff wimax image?
[EVO 4G Android Development] jdawg0024:
I'm also having issues (sorry Im not to good at ADB stuff) heres what Im doing

C:\androidSKD\tools

adb shell

wimax_mtd >c:\test.txt

cannot create c:test.txt: read-only file system
[EVO 4G Android Development] E-MAC:
Same issue here, I've tried both zips and can't get beyond 24722.

I'm on 3.2.2 and using Clockwork recovery.
[EVO 4G Android Development] TrevE:
dont go into shell to run that command. in CMD just do

adb shell wimax_mtd >c:\test.txt

all on one line. then go to my computer, c, open test.txt.
[EVO 4G Android Development] chaseclear:
try "adb shell wimax_mtd >c:\androidSKD\tools\test.txt"

that should create the text in your same folder as your adb... although makesure the path is correct.. might be androidSDK :D
[EVO 4G Android Development] jdawg0024:
this is what i get now

I launch CMD

then

adb shell wimax_mtd >c:\test.txt

access denied
[EVO 4G Android Development] gtkansan:
Interesting result: been stuck on 24722 or whatever for a while.

Tried both amonra and clockwork to flash, no dice. Used both zip files...

Now when I tried the 2.05.00.06.10 zip file in amonra, I get a message

"updating wimax radio...

E:multiple firmware images

E: can't store wimax image

Installation aborted"

This help with the diagnosis? Is a clear command needed before attempting to write the wimax radio file?
[EVO 4G Android Development] TrevE:
snoopdawg posted a good comment that should work too

adb shell wimax_mtd |findstr /i check
[EVO 4G Android Development] asrebel:
Latest Radio/WiMax - Still no 4G worky

I hope that when everyone gets their wimax update it works, but I'm skeptical since mine is updated and I've gone through reflashing the ROM & subsequent Radio/Wimax updates twice with the same results.

I'm attaching my logcat for anyone who has any ideas. I'm stumped
[EVO 4G Android Development] jdawg0024:
thanks that worked

I have: Check Firwmare Version (4.6.2.2_v24722) ........ 4.6.2.2_v24722

will apply the wimax update that I got yesterday from Caulkin to see if it changes will report back

After doing the update (went with no errors) the FWV did not change still 24722

I am using the recovery.img that came with Part 2 of Toats method

Just tried the new file EVO_WiMax_2.05.00.06.10.zip and it still did not take I still have 24722 So I figure when I do get into a 4G area (this weekend) it will not work?
[EVO 4G Android Development] boogief1:
Get back To stock and your 4G working

with this i put it together and it works for me like a charm im a happy camper now and im juts gunna hold off till something stable comes out

http://xdaforums.com/showthread.php?p=7014645#post7014645
[EVO 4G Android Development] TrevE:
dont revert :P we need people getting up to latest wimax to test. :)

im pretty sure from the reports i have seen here DC is working fine. Its just confusion with raido/wimax
[EVO 4G Android Development] jdawg0024:
I am with you TrevE, my problem is that with the WiMax updates out there I cant seem to get my WiMax to change... Always staying at 24722 on the recovery.img in part 2 of toast's method. I have not gotten any errors when I updated.
[EVO 4G Android Development] TrevE:
have you tried different radios/wimax floating around?
[EVO 4G Android Development] jrpointer:
I'm also stuck on 24722 with an inconsistent (rare) 4g connection. Any update on this?
[EVO 4G Android Development] asrebel:
I have the latest radio/wimax and I'm still having issues: http://xdaforums.com/showpost.php?p=7014525&postcount=3558

Thoughts??
[EVO 4G Android Development] jdawg0024:
I have only see these 2

newwimax.zip

EVO_WiMax_2.05.00.06.10

both are from Caulkin so I dont know if they are the same
[EVO 4G Android Development] chaseclear:
exact same boat here.. will continue to try different wimax img's to see what may work.. if i were in town (austin) i could check 4g but i assume its not working
[EVO 4G Android Development] Fixter:
I just wanna see Damage face when he gets back. Its gonna be like... *Enter Thread* *Shuts Down Computer* xD :D
[EVO 4G Android Development] TrevE:
have you seen this? seems he had to reflash radio after dc?

http://xdaforums.com/showthread.php?p=7013780#post7013780

have you tried the 4g permission fix?
[EVO 4G Android Development] Cordy:
Well I was able to flash the wimax image after a bunch of trial and error. I created a PC36IMG.zip with an updated android-info.txt as well as the new wimax image loaded up bootloader and it asked if I wanted to flash it I selected yes then said ok then asked if I wanted to reboot selected yes. Once booted into android checked my version and voila it is updated.
[EVO 4G Android Development] TrevE:
kickass. Now does 4g work?
[EVO 4G Android Development] jdawg0024:
can you post that file?

I would like to try. All it does is update the WiMax through the Bootloader right?
[EVO 4G Android Development] gtkansan:
can you please post this for the rest of us? Or what file within the wimax zip do we need to change when we name it pc36img? I tried this but it didnt like it (as I didnt know to do what you mentioned about the file change).
[EVO 4G Android Development] Cordy:
LOL for that I'll have to take another drive, don't get signal inside the house.

Edit: here it is, yes I only placed the updated wimax image inside along with a modified android-info.txt with the number of the latest software ver. as I'm sure it checks it. Oh and obviously remove "WiMax_" from it when you place it on your sdcard. I only named it that so you could distinguish it.

Edit2: After reading I see people are getting duplicate MAC addresses after using this, I'm going to pull it down for now.
[EVO 4G Android Development] KERKEDAGAIN:
...for the record, I'm running 3.2.2.1 with the confirmed latest wimax radio and have 4G n e'rthang working like a sharm!

*oh and I use ROM Manager for all my flash needs!
[EVO 4G Android Development] jschulman:
I have: Check Firwmare Version (4.6.2.2v25641_) ........ 4.6.2.2v25641_

I used the attached files to upgrade and I'm using recovery RA 1.7.0.1 on DC 3.2.2.1. They were posted somewhere in this thread, but for clarity, they are reattached.

That said, 4G doesn't work.
[EVO 4G Android Development] TrevE:
this thread needs an enema

see http://xdaforums.com/showpost.php?p=7014871&postcount=3569

have you tried any of that?
[EVO 4G Android Development] jdawg0024:
Thanks for this I can confirm that my WiMax has changed

Scan MTD partitions ........ 7

Find WiMAX partitions ........ OK

Open WiMAX partition ........ OK

Get HTC WiMAX Tag ........ OK

Verify WiMAX Tag (HTC-WiMAX-SQN1130)........ PASS

Read WiMAX partition ........ OK

Check Firwmare Version (4.6.2.2v25641_) ........ 4.6.2.2v25641_

Will be able to confirm 4G or not on Saturday when i go to L.A... will not be doing anymore updating until then.
[EVO 4G Android Development] ehren13:
I'm digging up an old thread here, but after searching around awhile, I couldn't find that anyone ever responded to this one.

I was having the same behavior (phone going into Disk Mode even though Charge Only was selected), and after 5 reflashes, I noticed it only started to occur AFTER I installed a batch of apps from AppBrain.

After removing damn near everything, I reinstalled apps one by one, rebooting everytime (I was getting paranoid about this...), and found that it was fricken' DoubleTwist that was doing it. Apparently, it has an "auto-mount" setting that will mount the SD card regardless of what USB option you choose upon plug-in.

I hope this helps. If it's not DoubleTwist, it's probably some other application with similar behavior.
[EVO 4G Android Development] TrevE:
just saw this too, the new OTA update is the same as the old. There has never been risk for rooted users on this only unrooted applying update 2x. The patches in this release are still the latest and greatest

http://www.engadget.com/2010/06/30/latest-evo-4g-update-is-back-online-presumably-wont-brick-your
[EVO 4G Android Development] VoXHTC:
Don't....think.... I can...stay....awake.... /thump
[EVO 4G Android Development] spurnout:
Don't give up now!
[EVO 4G Android Development] soxozor:
What happened to very soon lol
[EVO 4G Android Development] RikusHaven:
I can't wait for the new release! =D Went to sleep in hopes of waking up to it, but it's still not here. D= But I can't wait! =D
[EVO 4G Android Development] Fixter:
I'm pretty sure damage went to sleep :p
[EVO 4G Android Development] Fixter:
What up with the DcUpdater crashing every time I open it? :confused:
[EVO 4G Android Development] endoracing:
anyone elses backlight for their buttons not work ? I dont know if it is because of the roms or if its a hardware problem with my phone ....
[EVO 4G Android Development] Fixter:
They work, they are just light sensitive. The phone has a sensor on the top part. If you turn off the lights you'll see the buttons do turn up.
[EVO 4G Android Development] endoracing:
I dont think that is it ... my friend has the same phone and the lights come on, mine do not.

However, mine is rooted and with a different rom and his is not. so I dont know if that has anything to do with it.

Mine dont even come on at night with all the lights off.