yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] ViViDboarder:
... And you are? It's not like they are permanently broken. Sprint is the only one who can re-generate these keys. It's no loss to them. They just don't teach their employees enough to perform service so it's the only option.

As for stop trying to do flashing... Are you kidding me? You come to a board like this and make that kind of suggestion acting like you're all high and mighty with your 1 post?

Congrats Troll.
[EVO 4G Android Development] hbfreekwan:
i guess the ones rooting the phones at unrevoked arent big boys? cause they are the ones that created a patched ota that broke my wimax and havent released a fix in close to a month... you sir are retawded.

P.S. your probably too stupid to talk the people at sprint into returning your phone.
[EVO 4G Android Development] kpoz:
If you are holding off, then so am I.
[EVO 4G Android Development] pairodimes:
Thanks for posting...I really appreciate all the hard work you guys do to help out us newbs.

looks like your server is getting slammed though. Any other place you could put that download?
[EVO 4G Android Development] joeykrim:
not sure who this request is direct to. since i just posted a link to a file on my server a few posts ago, i double checked and my server is having no issues.

downloads just fine for me, plus its a very small file.

if this question was directed towards somebody else, apologies for the extra post!
[EVO 4G Android Development] blkswanpres:
I still get the same error after the switch.
[EVO 4G Android Development] joeykrim:
its working for others, not sure why you weren't able to get it to work.

you provided very little detail so expect some very vague suggestions:

download corrupted, download it again?

file wasn't loaded correctly onto the phone? adb push again?

system is writeable? be sure you have write access to system?
[EVO 4G Android Development] slag02:
I applied it late last night - but it appears I can not connect to a wimax network after the update

it says connecting to sprint - then it turns the wimax radio off and starts scanning again - once I saw it say Authenticating but then it restarted the wimax radio

in the phone info the wimax and bluetooth MAC address' is listed as unknown

my evo shows baseband 1.39.00.05.31

Any suggestions would be helpful

Thanks
[EVO 4G Android Development] ViViDboarder:
Worked well for me. Easy tool to use too.

I just downloaded the Zip from them and followed the directions.

My Firmware shows the update but the modem still shows "1.39.00.05.31". From what I gathered... this isn't really an issue. I'm sure if they thought this was serious they'd have pulled the dl link. Likely, when HTC/Sprint release the next version of the OTA this will be fixed.

What I want to know is if I can still run the Simple Root method now to permanently unlock my NAND or if I am going to have to wait for them to update. I know I'm already rooted and have Clockwork, but I feel like it's safer to have the full NAND unlock.
[EVO 4G Android Development] blkswanpres:
Sorry about that, I used root explorer to replace the file, and I still get the status 7 error. I am gonna try to redownload it and do an adb push.
[EVO 4G Android Development] slag02:
is 4G WiMax working for you?
[EVO 4G Android Development] Calkulin:
Being one that messed with this update all morning yesterday, I noticed the same issues they had ONLY when I was using a custom recovery console because it looks like they don't handle the radio commands correctly. If you use the stock HTC one, everything will update correctly. So until the devs update the recovery consoles to do the commands correctly or the full radio img is extracted(from the RUU when posted or from the phone), then people will have this issue with that zip(or official for that matter). But for those that are using the stock console/ROM, everything will update but they will lose root, so it's one of those pick your poison situations :rolleyes:
[EVO 4G Android Development] kpoz:
It sounds like you and Joeykrim are on the same page, so you've probably hit the nail on the head. Theoretically, shouldn't everyone should have the issue, then? This was posted by the unrevoked team and is supposed to work with unrevoked2, which flashes a custom recovery. Step 2 of the installation instructions states that a custom recovery from unrevoked2 is required, although I'm sure a custom recovery can be achieved by other means.

I think the best option is to wait for Sprint to release the revised OTA update and go from there.
[EVO 4G Android Development] ViViDboarder:
Didn't check and I don't get WiMax here at work.

I'll know when I get home.
[EVO 4G Android Development] joeykrim:
this was my theory and i had posted something similar but didnt want to make a point of telling the custom recovery ppl they're recoveries aren't setup to handle the stock android update scripts properly, especially w/o me taking the time to look thru their source code.

it makes sense and im sure it will all be sorted out soon enough. knew that radio.diff looked like trouble! thanks for the update from your experience, confirms what i was suspecting.
[EVO 4G Android Development] Calkulin:
If they are running a custom recovery like the ones I tested, then yes, all that use their method will not update WiMax or the radio.

Unless Sprint finds other issues with the update, all they are going to do IMO is verify radio version before writing the radio.diff(which they don't do in the current OTA) or include the whole radio.img, so it can be overwritten without problems
[EVO 4G Android Development] Calkulin:
I think the problem is the recoveries are not handing off the instructions to the bootloader to do the flashing but you would know better than me on that issue ;)
[EVO 4G Android Development] joshua_:
We'll look at the radio stuff on custom recovery tonight. In the mean time, we believe it is still safe to flash the update. Likely I will respin the update tonight to conditionally update the radio (i.e., only if it has not already been updated), and to fix whatever reason it is not updating right now. (If anyone has any knowledge of why the custom recovery isn't updating the radio, but the real one is, I'd be interested.)

In the mean time, do we have any reports of WiMAX working? If we are getting a lot of reports of WiMAX broken, and no reports of WiMAX working, I think I need to pull the update.

I don't check the forums all that often, so send me a message or hit me up on IRC if you need me.

joshua, team unrevoked
[EVO 4G Android Development] joeykrim:
to be fair, im making a main assumption which could be wrong. im assuming the stock OTA applied thru the stock recovery updates the radio version number correctly.

off the top of my head and in my opinion, the most thorough way to examine this, would be to compare the android stock recovery source code in eclair to the source code for the custom recoveries. id prob start first with verifying the write_firmware_image function is implemented the same way and go from there ... but you prob already knew this.

since it seems HTC is reviewing this OTA, its hard to say if a modified version of radio.diff/img will be released or not going forward.

appreciate the information and update!
[EVO 4G Android Development] joshua_:
Yeah -- actually, my suspicion is that HTC has a patched recovery updater that is not the same as that in git. I do know that they have some custom functions. If I get some time tonight, I'll crack it open in IDA.
[EVO 4G Android Development] kpoz:
I am curious to see if you're right. Maybe they should hire you :D

I wonder how long it will take them to roll out a new update.
[EVO 4G Android Development] gthing:
This didn't work for me. I still get this error:

Verifying current system...
assert failed: apply_patch_check(/system/bin/build.prop", "a bunch of crap here")

E:Error in /sdcard/update.zip
(status 7)

Installation aborted.

Slightly different then the other error code which showed a problem with reboot - I have a problem with build.prop apparently. Any ideas?
[EVO 4G Android Development] Calkulin:
Flash this build.prop to fix that
[EVO 4G Android Development] joeykrim:
Ah, that makes the most sense to me. They do keep pushing recovery.img files with different md5 hash sums meaning something is being changed and HTC does seem to have a history of preferring to customizing stock android features.

I need to learn more bout this IDA, seems to be the magic tool the hardcore people are able to use for reverse engineering these binary files.

I am very curious how HTC implements the write firmware function and why they didn't use the write radio function like they did for other .img files (perhaps since its a .diff) but I'm not sure without seeing the source code.

We look forward to learning more and appreciate your updates, good luck!
[EVO 4G Android Development] gthing:
Just to be clear - I should rename it to update.zip and flash it through recovery?
[EVO 4G Android Development] joeykrim:
its just a basic update.zip file which will copy the build.prop inside to your /system directory for you.

if you're using a custom recovery, you don't need to rename it. just select install/apply .zip file and select it from your sdcard.
[EVO 4G Android Development] dougm0:
It seems were in need of the rest of the Devs to work together to fix these issues with the radio.

I know where Damage has been.... anyone know where Toast and some of the others have been hiding?
[EVO 4G Android Development] gthing:
Thanks - that did it.

My baseband does show 1.39.00.05.31 now, though. My WiMax didn't work before anyway for some reason but I will test this at lunch (don't get wimax at work) and report back.
[EVO 4G Android Development] bandagraph:
I can confirm that 4g is not working after this update (unrevoked 2). When I do it from the settings section it goes like this:

1. Turning on

2. Scanning

3. Connected to Sprint

4. Turning off

Anyone want anything else tested? 3g tethering seems to work fine with Wireless Tether

Question: Why did it kill all my non-HTC widgets? Seems like i can delete them and re-add them to my home screen and they are fine.
[EVO 4G Android Development] Spookymonster:
Out of curiosity, are there instructions posted on how to un-unrevoked2 a system? That is, go back to the stock recovery?
[EVO 4G Android Development] hbfreekwan:
installed this update and it finds the 4g signal but never connects....
[EVO 4G Android Development] joshua_:
Ok, I have pulled the update temporarily while we investigate WiMAX issues. If any of you guys have installed the update from the OTA (not from our patch), please get in touch with me. Sorry for the inconvenience.

e: I have an idea of what is going on. It looks like the update is supposed to re-embed keys that are on the device. Anyone who has *not* done the update, it would also be useful if you got in touch with me.

e:2: OK, I think I have fixed it. For those having WiMAX issues, please go to settings, system updates, update profile, and see if that solves your problems. Let me know if that works for you.
[EVO 4G Android Development] mysterioustko:
I have NOT done the update, how can I be of service? :D
[EVO 4G Android Development] jonathaflores:
well it says my pcs vision usser name and pasword might be incorrect so yea!!
[EVO 4G Android Development] slag02:
Updating the profile was one of the first things I tried - but it still did not work

I will try again
[EVO 4G Android Development] brad65807:
Not sure if this helps, but i could not connect to wimax either. Just "scanning". I did a ##786# and all was fixed.
[EVO 4G Android Development] jonathaflores:
what exactly did you do???
[EVO 4G Android Development] brad65807:
did a ##786#, put my MSL in, phone restarted...it updated my PRL, and profile.. after that it connected perfectly.
[EVO 4G Android Development] bandagraph:
I tried updating the profile and the ##786#. Neither made WiMAX work.

Actually, i might not have done the ##786# part correctly. I opened the phone and entered that. It brought me to "Reverse Logistics Support". WHat do I do from there? Also, what is MSL?
[EVO 4G Android Development] joeykrim:
MSL is a six digit number unique to your phone.

two ways to get it, using cdma workship, there is a thread on this board, search for it. or call up sprint and tell them your 4g isnt workin after the OTA update and you need to "manually provision" or "manually update your profile" your phone. they'll give you the MSL over the phone while they walk you thru the process.

i dont know if this will fix the issue but those are the two best methods im aware of obtaining your MSL on the EVO.
[EVO 4G Android Development] freeza:
Maybe we should all compare settings in ##3282# WiMAX for whose who have 4G working and those who don't.
[EVO 4G Android Development] jonathaflores:
tryin to get my msl from the rep!! i think i might get lucky!!!
[EVO 4G Android Development] slag02:
Was yours resetting or was it just scanning?

Mine resets the radio after scanning and trying to connect
[EVO 4G Android Development] brad65807:
Mine just was 'scanning' the whole time.
[EVO 4G Android Development] joshua_:
So, when we reflashed the WiMAX radio, a few things happened. For one, the username and password were lost. (This was fixed when we did an 'update profile'). The other thing that happened was that the WiMAX radio's MAC address was lost. All of these things are recoverable; we're working on a tool to do just that right now.
[EVO 4G Android Development] jonathaflores:
my 4g just scans and when tries to connect it resets again!!

got my code from the sprint rep, just act stupid!!
[EVO 4G Android Development] ViViDboarder:
Did using the directions in this thread and entering your code work?
[EVO 4G Android Development] jonathaflores:
nope it did not!! but the rep told me to dial this number ##3282# which it has options to edit, evdo, Wimax, i dont know it my help!!
[EVO 4G Android Development] ViViDboarder:
Damn... I hope joshua_ and his team can come up with a fix then. :)
[EVO 4G Android Development] slag02:
Not sure if this is helpful but here is a cleaned up dmesg log as I tried to connect to 4G

sequans_xxx: Sequans SDIO WiMAX driver, version 1.2.153
<6>[ 4261.067596] sequans_xxx: Copyright SEQUANS Communications
<4>[ 4261.067810] supersonic_wimax_power
<4>[ 4262.270416] supersonic_wimax_set_carddetect: 1
<7>[ 4262.270538] mmc1: card_present 1
<4>[ 4262.270751] supersonic_wimax_status
<6>[ 4262.270874] mmc1: Slot status change detected (0 -> 1)
<6>[ 4262.270996] supersonic_wimax_set_status on:1
<6>[ 4262.271820] sequans_xxx: Driver has been registered
<3>[ 4264.793304] mmc1: Command timeout (cmd= 8 mci_st=00000004)
<4>[ 4264.800170] mmc1: card claims to support voltages below the defined range. These will be ignored.
<4>[ 4264.800567] mmc1: SDIO card claims to support the incompletely defined 'low voltage range'. This will be ignored.
<6>[ 4264.838287] mmc1: new SDIO card at address 0001
<6>[ 4264.843170] sequans_xxx: module parameters: firmware_name='sequans_boot.bin' load_firmware=1
<6>[ 4264.843902] sequans_xxx: found SQN1210 card
<6>[ 4264.844726] sequans_xxx: trying to find bootloader image: "../../../data/wimax/Boot.bin"
<6>[ 4264.845458] sequans_xxx mmc1:0001:1: firmware: requesting ../../../data/wimax/Boot.bin
<6>[ 4264.879425] sequans_xxx: loading bootloader to the card...
<6>[ 4264.880157] sequans_xxx: setting MAC address from bootloader: 00:16:08:00:24:05
<3>[ 4264.883453] init: untracked pid 3870 exited
<6>[ 4264.889678] sequans_xxx: bootting the card...
<6>[ 4264.890106] sequans_xxx: done
<6>[ 4264.894348] sequans_xxx: wimax0: Sequans WiMAX adapter
<6>[ 4264.894897] sequans_xxx: wait until FW is started...
<6>[ 4265.396789] sequans_xxx: setup GPIO40 for wakeup form SQN1210
<6>[ 4265.401306] sequans_xxx: KTHP initialized
<6>[ 4265.401733] sequans_xxx: card initialized successfuly
<7>[ 4275.926666] wimax0: no IPv6 routers present
<6>[ 4283.457702] sequans_xxx: card switched to DROPPED state
<6>[ 4283.520233] sequans_xxx: waking up the card...
<6>[ 4283.522369] sequans_xxx: wait for completion (timeout 800 msec)...
<6>[ 4283.524322] sequans_xxx: card is waked up successfully
<6>[ 4286.387451] sequans_xxx: got RX data, card is not asleep
<6>[ 4286.407867] sequans_xxx: waking up the card...
<6>[ 4286.410705] sequans_xxx: wait for completion (timeout 800 msec)...
<6>[ 4286.412414] sequans_xxx: card is waked up successfully
<6>[ 4287.335510] sequans_xxx: WiMAX carrier LOST [ignored]
<3>[ 4288.113983] init: untracked pid 3873 exited
<6>[ 4297.584472] sequans_xxx: free GPIO40 interrupt
<6>[ 4297.599731] sequans_xxx: KTHP cleaned up
<6>[ 4297.600219] sequans_xxx: wait until RX is finished
<6>[ 4297.856842] sequans_xxx: wait until TX is finished
<6>[ 4297.857574] sequans_xxx: card removed successfuly
<6>[ 4297.859893] sequans_xxx: Driver has been removed
<4>[ 4297.860290] supersonic_wimax_set_carddetect: 0
<7>[ 4297.860687] mmc1: card_present 0
<4>[ 4297.861358] supersonic_wimax_status
<6>[ 4297.861755] mmc1: Slot status change detected (1 -> 0)
<4>[ 4297.862152] supersonic_wimax_power
<6>[ 4297.878906] supersonic_wimax_set_status on:0
[EVO 4G Android Development] joeykrim:
the OTA released yesterday was 21.4 MB. they pulled the update last night and released it again today. the OTA today is telling me its 30.2 MB, im grabbing it now but 3g is slow at my work.

out of curiosity, have you looked into this file difference?

i'm not sure what they changed, if anything, but seems at bare minimum the file size changed...

edit: only difference in file sizes appears to be radio.diff and bspatch are gone and replaced with radio.img inside of the firmware.zip. didnt run md5sum but file sizes are identical for everything but those three files mentioned.
[EVO 4G Android Development] apexi350z:
Correct, just did the manual check on update and saw this:

System Upgrade 1.47.651.1 (30.15MB)

-FOTA update
[EVO 4G Android Development] joshua_:
Joey, if you could send me the new OTA, I'd appreciate that. I'll add that to our update when we rerelease with WiMAX fixed.
[EVO 4G Android Development] joeykrim:
of course.

link pulled ...

filename is long but thats how it came. pulled it from /cache after accepting the OTA download.

haven't applied yet. waiting for confirmations unrevoked2 works over it or the user debug RUU flashes over it.
[EVO 4G Android Development] joshua_:
I have it now. You can pull it if you like.
[EVO 4G Android Development] pp7:
Will I be able to install the OTA update if I have unrevoked1 installed? Must I uninstall and reboot first before applying the update?
[EVO 4G Android Development] ViViDboarder:
Do not install the OTA update. It will break your root.
[EVO 4G Android Development] joeykrim:
the OTA, through the radio.img will update the Main Version in the bootloader, flash back the stock recovery, and patch the exploit hole used for unrevoked1.

basically, they patch up all our known methods of root through this OTA.

if you want to see the technical details on this, i've detailed them out here http://xdaforums.com/showthread.php?t=714157

im hoping once unrevoked is able to get the wimax mac address issue resolved, they're able to release another method to obtain root so i can flash over the main version and use the PC36IMG.zip userdebug/eng build to root my EVO again.
[EVO 4G Android Development] ViViDboarder:
joshua_

What are your thoughts on these:

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

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

Could flashing either of those possibly fix the radio? I'm new to firmware type stuff but it seems as if it would just overwrite whatever is done to the radio with the update again. He patches have been modified to preserve root by extracting only the Wimax/Radio updates and there have been users confirming that their 4G was still working (not people who already ran the unrevoked patch though yet).

To anyone else here... if you tried these and they brought your 4G back, let me know and I'll try too. :)
[EVO 4G Android Development] kpoz:
Correct me if I'm wrong, but are you saying that you updated at are no longer rooted?
[EVO 4G Android Development] joeykrim:
using the full official OTA will remove root and yes, im no longer rooted! dang!

so in order to work towards obtaining root again i started another thread tracking our attempts and progress - http://xdaforums.com/showthread.php?t=714157

im hopeful unrevoked is able to find another root exploit...and def willing to test!
[EVO 4G Android Development] kpoz:
Noooooo. Let me guess, you were your own guinea pig?
[EVO 4G Android Development] joeykrim:
yea, next time ill have to squelch my spirit of adventure.

many people still haven't been able to purchase an EVO due to them being out of stock and the white one being released in short while at Best Buy, there will be plenty of new users coming who aren't able to use the old root methods on their new devices.

we're off topic...wish was more we could do to contribute to the unrevoked effort! short of another userdebug or eng build RUU being leaked, which seems unlikely, they're a reliable source for root/custom recovery methods ....
[EVO 4G Android Development] kpoz:
That stinks.

I have a question for you. I've been following the thread started by whitslack. In Post #20, he says the following:

"That can only mean that you're not using the stock ROM (w/ root added). This is an incremental update straight from the official sources with one slight tweak to preserve root access, so you must be using a stock system in order for it to apply. Users of custom ROMs should be flashing new versions of those custom ROMs. The incremental upgrade path here will not work on custom ROMs."

I have your odexed 1.0.8 ROM installed with the kitchen on top. Would I be able to install this rooted update, or would I have to somehow revert to your update without the kitchen? I only used the kitchen to remove a few apps.

Also, what are the consequences of installing an update with a radio? Can I potentially brick my phone? If I have a few nandroid backups in place, will I be able to revert if everything didn't properly install? Will I be able to install your kitchen on top of the new update?

I'm on the newer side of this whole rooting adventure, so any help would be appreciated. Consider me a guinea pig, but anything I do can't have the ability to brick my phone, so please keep that in mind.
[EVO 4G Android Development] kpoz:
Joeykrim, FYI: I posted a question similar to the one I asked you in the whitslack thread.
[EVO 4G Android Development] optim9x:
unrevoked 2

unfortunately I updated my evo 2 days ago and lost my tether I tried the reflash and installed the usb drive but keep getting stuck at "the reflash will continue without authorization" can anyone help?
[EVO 4G Android Development] gthing:
I got my msl code and I opened up the reverse logistics support menu, but I don't know what to do now. Any help?

There is a reset option in the menu that warns me it will delete all my data. Should I android first ir is this the wrong thing?
[EVO 4G Android Development] ViViDboarder:
You should try to get in touch with Joshua.

Sent from my EVO 4G using the XDA App.
[EVO 4G Android Development] GPiet:
So the unrEVOked2 patch was applied and I am one of the few who lost 4G.

As I understand it, the "fix for WiMAX/4G" is in progress, however I was more curious that if the WiMAX fix is taking up time of the folks that know what they are doing, could the people who implemented unrevoked2 prior to the OTA patch just do a restore and be back to WiMAX... then wait for an update that covers people who did the official OTA?

I do not know the inner working of the system well enough to try a restore without checking if that is counterproductive.
[EVO 4G Android Development] ViViDboarder:
Everyone who flashed the unrevoked version of the OTA lost WiMAX. Re-flashing the old WiMAX does not work due to some keys that were written over.

The team is looking for a way to restore 4G. You can try and play dumb and get Sprint to replace the broken 4G phone and say it was the OTA though.

Sent from my EVO 4G using the XDA App.
[EVO 4G Android Development] GumboChief:
New version is up. If your 4G was broken by v1, this will not fix it.

http://www.unrevoked.com/rootwiki/doku.php/public/evo_ota_2_patch