yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] GumboChief:
I had been. I followed these directions to fix it. Changes the 4G idle time.

See post #6

http://xdaforums.com/showthread.php?t=700927&highlight=Wimax_Idle_Sleep

You will need a passcode known as MSL to edit this number (you can view current value without passcode). I got the number by calling sprint tech support. It seems most people here follow this thread to get the number:

http://xdaforums.com/showthread.php?t=697487
[EVO 4G Android Development] martouf13:
I was wondering how do I know if I have the engineering HBOOT installed? At the top is shows the version as 0.76.2000
[EVO 4G Android Development] afxtwn:
Off to do that now!

thanks.
[EVO 4G Android Development] kjprice26:
hello i need a bit of help. when i finished these steps i lost my wireless tethering. does anyone have the apk file for the wireless tethering.
[EVO 4G Android Development] whitslack:
It's in the Android Market. Just search for Wireless Tether.
[EVO 4G Android Development] Land Master:
YES. You have the engineering HBOOT
[EVO 4G Android Development] whitslack:
That is the version of the engineering build. Congrats.

EDIT: Land Master wins again. :P
[EVO 4G Android Development] klbjr:
Is this information confirmed? Just checked the usual sites and saw nothing about "Mid-July". "Near future" was the term used.
[EVO 4G Android Development] Land Master:
<Rant On>

You know. Perhaps my OCPD actually comes in handy when performing "hacks". I typically read the entire thread to see how others have progressed and if any specific issues are detected. This way I am prepared to handle any oddities that might crop up. So far i guess I have been lucky because any issues I experienced had already been solved by others, I was prepared, and I employed the proper solutions/methods..In the case of the method described in this thread I had ZERO issues.

It seems as if a majority of people read the first post, dive in and then move to the end of the thread asking questions when things go haywire. In fact, it doesn't even seem like they read the first post thoroughly enough.

Maybe I'm out of line and this "is" Whitslack's thread, but I have been attempting to contribute something back by answering any questions I can when he appears to be offline. He has been very accommodating upon his return and has answered the the same questions over and over again displaying little or no negativity doing so.

In my opinion its time to say what should have been said awhile back.

READ THE THREAD. YOUR QUESTION HAS PROBABLY ALREADY BEEN ANSWERED.

Sorry Whitslack. I'm speaking on my own behalf, but you are apparently much more patient than I am.

<Rant Off>
[EVO 4G Android Development] afxtwn:
pardon my noobieness but the toast instructions say to go to shell in windows and type a line of code, when I go to power shell nothing works.

Any help?
[EVO 4G Android Development] whitslack:
The irony is that the folks to whom you're speaking won't ever read your rant because they won't ever read the thread. *sigh*
[EVO 4G Android Development] afxtwn:
thats all I read. :)

Kiddin.
[EVO 4G Android Development] whitslack:
My personal experience with Windows is that nothing works, period. :p However, if you insist on using that operating system, I guess you should try using the standard "Command Prompt."
[EVO 4G Android Development] Land Master:
It works FANTASTIC too!

Wireless Tether Authors: Muller, Lemmons, Buxton

http://android-wifi-tether.googlecode.com

I'm currently on Version 2.0.2 (theory of evolution)
[EVO 4G Android Development] regulator207:
i have no idea what your post means? so are you confirming it works?
[EVO 4G Android Development] whitslack:
In fact, you could actually flash the PC36IMG.zip and then install the official OTAs straight from HTC using the on-phone update process. Since neither of the OTAs included an HBOOT image, you'd still have the engineering HBOOT at the end of the OTA updates, so you could just use fastboot to flash the Amon RA recovery and then use the recovery to install the su-2.1-e-unsecure-signed.zip, and poof, you'd have root. The only foot in the door you need is the engineering HBOOT, and like I said, neither of the official OTAs touch it.
[EVO 4G Android Development] jonathaflores:
no 4g doesnt work, it goes on, then starts to scan and then goes off!
[EVO 4G Android Development] whitslack:
You're using the released HBOOT, not the engineering one. Have you tried running the RUU exe?
[EVO 4G Android Development] whitslack:
Have you tried this?
[EVO 4G Android Development] awesomeindeed:
This method WORKS for me. I am currently sitting with my phone on my desk "connected to Sprint" with 4G. Going to try writing to /system with adb now.
[EVO 4G Android Development] jonathaflores:
trying now!!
[EVO 4G Android Development] halorin:
You are my hero. This worked! How can I make a donation?
[EVO 4G Android Development] bprinehart:
I think I'm hosed. Everytime I try to flash something, I get a signature verification failed, or a "Not Allowed" for example when I try to boot into recovery. It seems as though I lost all permissions. I was holding out some hope since I still had fastboot access, but that appears to be a dead end as well.

C:\Users\user\Downloads\android-sdk_r06-windows\android-sdk-windows\tools>fastboot.exe update PC36IMG.zip

archive does not contain 'boot.sig'

archive does not contain 'recovery.img'

archive does not contain 'system.sig'

--------------------------------------------

Bootloader Version...: 0.79.0000

Baseband Version.....: 1.39.00.05.31

Serial Number........:

--------------------------------------------

sending 'boot' (2280 KB)... OKAY

writing 'boot'... INFOsignature checking...

FAILED (remote: signature verify fail)
[EVO 4G Android Development] whitslack:
I don't want any donations. Believe it or not, this was actually insanely easy to put together. I just needed to have the right knowledge about how all this works, which I've been accruing over the past few days.
[EVO 4G Android Development] whitslack:
If you have only the released HBOOT (so fastboot won't flash anything) and a broken recovery and a broken system, then yeah, you're hosed. :(
[EVO 4G Android Development] Land Master:
Yeah OK...If you say so :D

Honestly I am a n00b that has learned all I can in the last month. What you guys do and how you do it always impresses me but most of the technical stuff is over my head. I'm real good at following specific instructions to a T and have been successful so far. I have NOT attempted anything since the OTA was released.

With that said I somewhat follow what you are saying but wonder why (if I understand correctly) if replacing the HBOOT gives us total control over the phone why wasn't done from day one? Do I understand that the the "root hole" that was patched by the latest OTA did NOT touch the HBOOT and that in order for them to "plug" it in the future they would need to push a new HBOOT file?

I know you will be busy addressing last minute questions so no obligation to answer these questions. I'm just curious and trying to learn even more.

Thanks again!
[EVO 4G Android Development] theoner1:
HUGH THANK YOU TO YOU SIR!!! You my friend just made my day. I had major problem after a bad flash and was up til 4am last night and again this even until I saw your post. For what ever reason my bootloader would not let me flash any PC36IMG.zip without say Main version is older, but whatever your PC36IMG got made my bootloader to not show Main version is older any more (kept looping bootloader actually, which is a good thing compare to Main Version is older). I later then follow up with Toast root #2 again and BAM EVERYTHING IS BACK TO NORMAL.

SO FOR EVERYONE WITH PROBLEM AFTER TO NEW OTA UPDATE try this man PC36IMG.zip first than follow by Toast root# 2 method. THANKS A MILLION FOR ALL YOUR HELP!!!!
[EVO 4G Android Development] whitslack:
Total control over the phone comes from fastboot, which is a utility in two parts: half of it lives on the phone as a piece of HBOOT, and the other half lives on the computer as the fastboot program. The release version of HBOOT has its half of fastboot crippled. The engineering version of HBOOT has a fully working fastboot.

With a working fastboot, you can overwrite any partition on the NAND with anything you want. It's carte blanche. That's all you need to flash a new system image (in .img format). Or, you can flash a custom recovery and use it in turn to flash an update zip.

If HTC were to push out a new HBOOT in an OTA update, yes, it would cripple us. But we can always remove the HBOOT from the update before applying it, so it really wouldn't do them any good to try it. (Hear that, HTC?! Don't bother!) :D

EDIT: The hole they plugged was a security vulnerability in the kernel that allowed an unprivileged process to escalate its privileges to root. That's how unrEVOked works. That has nothing to do with HBOOT. Think of it as coming at the problem from opposite sides. Fastboot lets you flash a system in which you already have root from outside any system at all; the "root hole" formerly let us attain root from inside a system in which we did not already have root.
[EVO 4G Android Development] ramiss:
/\/\ What he asked
[EVO 4G Android Development] You stole Boo Boo's Name:
going to guess since mine got stock otad to 147. that this wont work to root it back out
[EVO 4G Android Development] awesomeindeed:
Just in case anyone was in disbelief...
[EVO 4G Android Development] Cordy:
Curiously for anyone whom which this method worked, did anyone of you have a bad MAC, fixed your MAC and then followed then used this method?
[EVO 4G Android Development] mobilemaniac:
Ok. I was just working my way through Toast's rooting method. I finished part 1 and was trying to get all the files together for part 2, so I haven't unlocked NAND or installed Toast's recovery yet. Should I just follow the instructions in the OP and skip Toast part 2 now?
[EVO 4G Android Development] Land Master:
Dude....I mean GOD. I hope you understand that this seems too good to be true. I'm certainly not questioning you (as I do not have the knowledge to do so) but I have followed the Damage Control thread for 3 days now and wonder why they didn't just skip trying to figure out the radio thing and concentrate on this method. Why didn't all the Dev's do so for that matter? Were they just trying to come up with a "fix" to problems created by jumping the gun initially?

If I understand, you have (with three days experience) provided us with a fully rooted device FOREVER.

If this is in fact the case, put up a donation button. The others have them!
[EVO 4G Android Development] afxtwn:
Im not quite understanding , cmd cant command adb
[EVO 4G Android Development] Land Master:
If its the same step that I remember you need to navigate to the:

C:\android-sdk-windows directory

Hold the shift key down, right click on the "tools" directory, and select:

"Open Command Window Here"

Hope you read this entire post :) ;)
[EVO 4G Android Development] afxtwn:
HELP!! I stopped at navigate!
[EVO 4G Android Development] Land Master:
Ooooo. That could be bad if you don't know where you are going. :)

At least your question broke up the monotony.

Good luck!
[EVO 4G Android Development] afxtwn:
Down is up, Up is down dogs marrying cats, its mass hysteria!
[EVO 4G Android Development] frankenstein\:
Slightly off topic but related.

I have been unable to execute code commands on my phone such as ##DATA# or ##786# since running your patch update process Whit so I hooked the device up to my computer and ran logcat while entering the code.

What I see are a lot of system.err entries complaining about calling java classes, each group of these includes lines as follows:

W/System.err( 448): java.net.UnknownHostException: localhost

and

W/System.err( 448): Caused by: java.net.UnknownHostException: No address associated with hostname

I believe this is telling me that the phone is trying to launch the requested function/tool but is unable to do so because the java class used to build/display the tool is called via the localhost host name and the phone is unable to resolve it.

I am most interested in resolving this. I've tried adding a hosts file to /system/etc with an entry as follows:

127.0.0.1 localhost

but, this hasn't corrected the problem.

Now this may be due to some tinkering I did myself and not Whit's patch but I'm not sure and I thought I might be able to get some insight here as this thread is pretty active.

I'm open to any suggestions for resolution to this problem.

When I adb shell into the phone and ping 127.0.0.1 I get responses just fine. When I ping localhost I get host unknown. Does anyone know where/how the phone is supposed to resolve the localhost host name? /system/etc/hosts doesn't seem to be doing the trick for me.

Perhaps someone could go check /system/etc to see if they have a hosts file there please? If you do, could you post it so I could compare it to what I've done?

Thanks,
[EVO 4G Android Development] whitslack:
For what it's worth, the 1.47.651.1 system includes a /system/etc/hosts file already. It contains only 127.0.0.1 localhost.

ping localhost works for me.
[EVO 4G Android Development] frankenstein\:
Can you post the file for me so I can try using it instead of the one I have please?

Thank you for looking for me!
[EVO 4G Android Development] martouf13:
Please don't start a OSX vs Windows war... As we all know Windows is far superior anyway! LOL j/k Truthfully if you want the best "OS" then you would go Linux IMHO. I personally like Windows better and it supports a ton more software available to the public but thats just me. But truthfully it really is to each their own; there is no need to rip on people for using whichever OS... Why can't people just let that be!
[EVO 4G Android Development] cnstarz:
thanks whitslack, this is the only way to bring 4g back to my phone after putting fresh rom. i followed all the other guides for fixing 4g and nothing helped but this thread. thanks again. gonna leave my phone stock from now on.
[EVO 4G Android Development] martouf13:
Yes it can.. Simply open a command prompt by running cmd.exe and then navigate to the tools directory which has adb in it. From there is where you do all the commands!
[EVO 4G Android Development] ebuechler3:
i had to flash a custom rom using rom manager instead of the aa mon method.... everything is good now
[EVO 4G Android Development] afxtwn:
searched for this first,

I cant flash the flash_image file it keeps saying

cannot create flash_image: read-only file system

I tried adb remount as well.
[EVO 4G Android Development] frankenstein\:
what command are you using? have you completed part 1 of toast's root process?
[EVO 4G Android Development] whitslack:
This is the exact file pulled from my phone: http://www.mattwhitlock.com/hosts

EDIT: Frankenstein\! You're using Internet Explorer. For shame, sir!
[EVO 4G Android Development] afxtwn:
yeah I did part 1 a few days ago and im trying to get through the first line of the command cat g:/flash_image blah blah blah.

Should I try part 1 again?
[EVO 4G Android Development] frankenstein\:
The problem was the format of the hosts file. Apparantly it needs a specific number of spaces between the ip and host name which was incorrect because I used instructions and a sample file from a post about blocking adds. I have corrected it by pulling the hosts file from another rom.

Thanks for your help looking at that for me Whitslack!
[EVO 4G Android Development] frankenstein\:
when you "adb shell" into the phone, do you have a # prompt or a $ prompt?

you need the # prompt.

then you have to copy the flash_image file to the sd card. make sure it's the file, not the directory. it's a file with no extension.

Once you copy it to the sd card along with the image file you want to flash (i.e. mtd-eng.img and/or recovery.img), change the phone from Disk Drive mode to Charge Only mode so the sd card is available to the phone and not locked to the pc.

Then you do:

cat /sdcard/flash_image > /data/flash_image

chmod 755 /data/flash_image

flash_image [partition name] /sdcard/{image file name}
[EVO 4G Android Development] afxtwn:
Thats exactly what I did, im almost done redoing part 1, Ill report back soon!

And I get a #
[EVO 4G Android Development] jm5503:
So if I received the new official OTA and currently running a completely stock evo this will give me root access?????

@!! h@i! k!ng Evo!!!!
[EVO 4G Android Development] whitslack:
You're probably boned, but check here.
[EVO 4G Android Development] afxtwn:
I dont believe so.
[EVO 4G Android Development] sdc177:
Yep simple as that. And because the remember box was checked I won't have to worry about it again...until I'm brave enough for a custom ROM again:D.
[EVO 4G Android Development] athasian:
Wanted to chime in and say Thank you so much OP. I spent all week trying to get my 4g working again, and nothing was doing it.

Saturday I started with your original list , but because I was also at work at the time, didn't get finished before you'd added the new set of instruction. On the way home from work, using just the original stock image you provided, i was ecstatic to see the 4g connect!

When I arrived home, I started over with your new set of instructions, and I must say that today the 4G worked flawlessly when I went into town. Now if we could just find out how to flash the new PRI I would be in total heaven. (I have this obsession with "the most current" - probably what caused my issues to begin with LOL ) :)
[EVO 4G Android Development] whitslack:
The primary purpose of a bootloader (HBOOT on our phones) is to load the kernel and the initial RAM disk into memory. Then it hands off control of the CPU to the kernel. From that point forward, the bootloader does absolutely nothing. Therefore, as long as the bootloader is correctly performing its task of loading the kernel into memory and handing control to it, there is no reason to change the bootloader.

On our phones, HBOOT has a secondary purpose: it supports the Fastboot protocol, by which images may be flashed onto the phone's NAND flash memory. If the Fastboot protocol ever gains new capabilities, then there might be a reason for us to want a new version of HBOOT. Until then, there isn't.

One last comment: in the case of HBOOT, the newest version does one other tiny (but annoying) thing before handing control over to the kernel: it sets the lock bits on some of the MTD partitions. That's why we can't write to /system, even after remounting it read/write, or flash a new recovery image, when we're using the latest HBOOT. The slightly older HBOOT (the engineering version) does not do this tiny, annoying little thing, so the NAND remains writable.

EDIT: Addendum: If HTC releases a new version of HBOOT, it's possible that we could hack it to skip over the setting of the NAND lock bits and to skip over the checking of flash image signatures. It's also quite possible that their new HBOOT wouldn't have any advantage for us over the engineering HBOOT whatsoever, in which case we'd stick with what we have.

Edit again: Rereading your post, I think I misunderstood you. You're asking about the PRI specifically and if some day we'll figure out how to flash it independently of the bootloader. My answer: probably, if there's reason to.
[EVO 4G Android Development] iknowsquat:
whitslack-I think OMJ v1.6 needs a modded boot.img. We are getting adb remount failure.

getprop ro.secure returns a 1 instead of a 0

Is the solution on the user end to flash the boot.img for 1.47xxxxx from Post #1?

Is there a simpler fix? Still searching myself but saw "your was light on" and figured I'd ask.

TIA.

EDIT:

btw-already saw this:

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

but I ASSUMED I'd need a different boot.img
[EVO 4G Android Development] whitslack:
If ro.secure is 0, then adb shell takes you straight into a root shell, and adb remount works. If ro.secure is 1, then adb shell takes you to a user shell, and adb remount fails.

To get a root shell, you only need issue the su command. No big deal.

To remount the /system file system read/write, you can use the mount command at a root shell instead of the adb remount command on the computer. (It's slightly more typing but accomplishes the same thing.)

Since there's really no missing capability by having adb.secure = 1, I don't see altering the boot image as being worth the trouble.
[EVO 4G Android Development] gapoochi:
HI, I did this last week and everything was great but I am now having a problem with accessing recovery. Everytime I try to do that, I get the red triangle with exclamation point. I don't know what I can do at that point...

how do I flash roms or themes? I remember having done this already since doing this but I may be wrong? Is there another step I need to take?

I'm not very knowledgeable about all this so I would appreciate any help you could give me.

thank you!
[EVO 4G Android Development] whitslack:
You're back on the stock recovery. Assuming you still have the engineering HBOOT and root access, you can use flash_image to flash a new recovery image. I think possibly there's an app that will do this for you. (Clockwork?)
[EVO 4G Android Development] iknowsquat:
Thanks! Guess I was making a mountain out of a molehill :)
[EVO 4G Android Development] johntiger:
So I'm a little confused about this whole process what's the point of the second portion of the entire thing you know the whole part where I mount or what ever is going on by going into the shell. Am I missing something? I flash the first two roms so what then
[EVO 4G Android Development] whitslack:
The information about how to make changes to /system is just supplemental. I'll make that more clear. Sorry for the confusion.
[EVO 4G Android Development] afxtwn:
Alright guys I got everything working!

One question though, If I flash the OTA update, am I boned forever or just untill people bust this update? Im trying to figure out whats up with my wimax and people say the ota update helps so I Wanna check it out but dont want to be "boned" forever.
[EVO 4G Android Development] PikkonX:
If you've completed the steps from the first post, you already have the OTA installed with root capabilities.

Sent from my HTC Evo
[EVO 4G Android Development] afxtwn:
I sheeeee, so what are people installing thats screwing them from rooting?
[EVO 4G Android Development] PikkonX:
Installing the actual OTA that their phone notified them was available is what's breaking root. The process you did installed the same exact files, but it's been modified to maintain root access.

Sent from my HTC Evo
[EVO 4G Android Development] tcd2004:
Plan on doing this when I get home, one quick question though. Will this wipe my phone back to stock after I complete these two steps, or will it just update?
[EVO 4G Android Development] ewells38:
Thanks.. worked wonderfully :D
[EVO 4G Android Development] Childofthehorn:
Thanks guys this worked this first time with no issues. I am eternally grateful as the battery life is sooo much better and the radio is definately a.bar stronger as well.

Though as something interesting, my 002 hardware definately connects to a weaker 4g more consistantly and with greater ease than my BF's 003. Maybe hardware differences are.a.bit more than skin deep.
[EVO 4G Android Development] whitslack:
It wipes. You can make a backup of your data partition using Nandroid and restore it using fastboot. (Don't restore the system partition, though, or you'd be back where you started, except for the radios.)
[EVO 4G Android Development] gapoochi:
Is this something I download?

How can I flash something if I can't get to the recovery part (that's the only way I've ever done it before)

Thank you!
[EVO 4G Android Development] tcd2004:
When I go into recovery (i'm using clockwork v2.0.1.3) and click on nandroid backup, it doesn't give me an option for just the data partition, it just backs up everything. Is this normal? If so, how would I just restore the data portion?

Edit: There is also an option in titanium backup to backup system data. Could I do it that way instead?