yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] firewalkwithme:
OK I used your syntax from a few posts up (replacing the N with 4 in my case) and it repeats the command back to me, then when I exit the shell I get a permission denied error when I try to push a zip to /system. Am I missing something?
[EVO 4G Android Development] whitslack:
Yeah, ADB still isn't running as root. If you want to use adb push, you'll have to push the file somewhere that the shell user can write, and then move the file into place (or copy and delete) as root. It's definitely not as elegant as having adb run as root on the phone, but as far as I know, that's not possible without hacking the boot image.
[EVO 4G Android Development] ao7996:
I believe this should help

http://xdaforums.com/showpost.php?p=7115929&postcount=639
[EVO 4G Android Development] firewalkwithme:
aha, thanks, that's what I figured. Putting it on the sd card and using cat works great!
[EVO 4G Android Development] S4Rs:
I'm such a newb

I have spent so much time searching for why this method didn't give me any root access at all when i tried to run titanium backup.

Would help to install busybox again...
[EVO 4G Android Development] spincycle76:
Just did this tonight, it was easy as pie. I really appreciate the work that went into this, even if it's not a big deal for you. I like being able to have an almost stock rom, with root, it's rockin'!
[EVO 4G Android Development] jimmyeason:
ok got i ? i used the simpleroot method ota and i noticed it downgraded my software. i want the updates. so will this take me back to the 1.47 software and radio. Im already fully rooted.
[EVO 4G Android Development] tkrechel:
this will give you a fully stock, fully rooted phone with the newest radio and wimax. no other way to put it lol
[EVO 4G Android Development] ewilson:
OK got a question for you guys I did the start over works great 4g works great stays connected. But one problem where I works donot have 4g so I turns 4g off when I come home or get in 4g area I turns 4g back on it finds sprints says connected then stay stuck on obtaining IP sometimes it connects goes back to scanning. So I would have to turn phone off reboot or run update prl then it works. But once it works it fine and great. I'm running DC 3.2.3. Do anybody know why this happens

I am in Greensboro NC we have 4g
[EVO 4G Android Development] sparhawk6:
Although its a little hard to understand your post, I think I have seen this behavior in my phone after I did this method. When I return home to a non-4g area, I turn 4g off. When I go back to the 4g area (work), I turn 4g back on, but it does not connect. I have to do a PRL update and reboot for it to work again.
[EVO 4G Android Development] fuzion22:
Quick question. I am fully rooted with the 1.47.651.1 Software number (rooted stock rom). If I flash a custom rom (DC or Fresh) will i lose the current software number i have? Do I also have to reflash updated WIMAX or Radios if I flash a custom rom.

Thanks!
[EVO 4G Android Development] kamiller42:
I can enter a 4g area, turn on 4g, and connect. When I leave a 4g area, turn off 4g, then turn 4g back on before re-entering 4g area and enter a 4g area, it is stuck scanning. It never attaches to the 4g network in the area I entered. If I turn 4g off and on while in 4g area, it will connect.

Are unrooted stock users having these problems? It is a real let down and PITA. Is 4g working perfectly in all scenarios for any rooted user?
[EVO 4G Android Development] ewilson:
Yes that's what I'm saying also Bluetooth doing same thing wont connect to paired device unless reboot any fix for this
[EVO 4G Android Development] sw99:
Since the OTA, I can manually connect a Bluetooth headset. Before the OTA my headset would connect automatically. Miss that capability, but I added a shortcut to the bluetooth settings on my home screen, so that at least I can connect quickly.

Same here after the update. I thought maybe it just takes a long time to scan, so I left my 4G on today when I went out to lunch - no luck.
[EVO 4G Android Development] sdc177:
I'm in the same boat as you and have yet to see anything that specifically addresses this behavior.
[EVO 4G Android Development] ewilson:
This just sucks I mean once you reboot it connects but why do we have to reboot. Do anybody know if this is just for rooted and custom roms or is this like this with the stock 1.47 roms also? Because if this is only like this with custom roms ill just redo the start over flash method and remove bloat ware and wait till DC work out a fix.
[EVO 4G Android Development] sw99:
The 4G reconnect issue has already gotten lost once in this topic. Might I suggest we move it to an already created topic:

http://xdaforums.com/showthread.php?t=717307&highlight=4g+reconnect

This will also expose the problem to other folks who may have not rooted, or who have an alternative ROM.
[EVO 4G Android Development] cmart4:
To the OP:

Thanks you so much for this post, it really saved me some time and aggravation in getting my 4G working again!
[EVO 4G Android Development] Rocklee99:
if i am NOT rooted, will this work for me or no, im on 1.47
[EVO 4G Android Development] jimmyeason:
ok got a ? i used simpleroot for ota and it downgraded my software and radio. everyone is telling me to use this method to get 1.47 rooted. im fully rooted now i just want the update stuff so i can run flips roms. If i do this over my root already will i brick my phone. One other thing do i renamed the PC36IMG zip to PC36IMG.zip or just PC36IMG since its already a zip file, i ask cause i see diff things about this in diff threads
[EVO 4G Android Development] Rocklee99:
Do u know if i have to be rooted to use this method?
[EVO 4G Android Development] tonyh703:
I first rooted with simpleroot, then used this method. It works perfectly if you follow directions.
[EVO 4G Android Development] tonyh703:
also, as long as it is a zip file it will be ok. you do not want it to be pc36img.zip.zip
[EVO 4G Android Development] whitslack:
Be careful doing that. It's mtdblock4 if you're booted in the system.

Always run mount with no arguments first to see what MTD partition the system is on. Then use that partition in your remount command.
[EVO 4G Android Development] mobilemaniac:
Thanks! This makes a lot more sense.
[EVO 4G Android Development] enormous:
Same circumstances here.

HBOOT-0.79.0000
[EVO 4G Android Development] numus:
Thiis doesnt work with the offical OTA update :(
[EVO 4G Android Development] c0mputerp0et:
Greatest OP ever. ( in the EVO-verse anyways ) Thank you so much for this information. I've just spent 20 mins "rebooting" my Evo + Titanuim removal of the sprint warez. I dare say my reception is better on 3G .... but maybe just my heightened excitement with this method.

Again thank you for your time and effort on this.
[EVO 4G Android Development] bprinehart:
We're F'd numus.
[EVO 4G Android Development] nunyabiziz:
If his phone has the OTA then this will also fail during boot version verification of any PC36IMG.zip with an older version.
[EVO 4G Android Development] enormous:
Confirmed :(
[EVO 4G Android Development] whitslack:
That's the same HBOOT version as the original 1.32.651.1 release had. Have you tried Toast's Part 2? (His PC36IMG.zip is not an amalgamation of system from 1.32.651.1 and HBOOT from 1.17.651.1 like mine is. His is all the older version, meaning the zip might be signed, and the release version of HBOOT might accept it.)

EDIT: If you're getting a MainVer error and not a signature error, you might try flashing the mtd-eng.img to fool HBOOT into thinking you're not downgrading. Of course, that requires you to have root already...
[EVO 4G Android Development] GumboChief:
According to this thread, nothing works-

http://xdaforums.com/showthread.php?t=714157
[EVO 4G Android Development] whitslack:
Has anyone thought to try simply changing the "MainVer" in the android-info.txt file inside the PC36IMG.zip? If you change it to the system version you're currently running, HBOOT might not complain.

For example, the android-info.txt in my PC36IMG.zip from the OP has "MainVer: 1.32.651.1". Perhaps that could simply be changed to "MainVer: 1.47.651.1", and then maybe HBOOT wouldn't realize that you were trying to downgrade.

EDIT: Never mind. I see that this has been attempted.
[EVO 4G Android Development] SharkUW:
"Partition update fail!"

When flashing the PC36IMG everything goes correctly except for "recovery" which ends up with "Fail-PU" as the status. The phone will boot OK but attempting to enter recovery mode will hang and I have to remove the battery. I've already attempted redownloading a fresh copy to see if it was an issue with a corrupt file, but I'm having the same issue. Prior to this I was NAND unlocked running DamageControl 3.1.

Does anybody else have this issue? Does anybody know how I can get the recovery partition to flash correctly or what would be a safe method to get a working recovery?
[EVO 4G Android Development] whitslack:
If you have root access from the booted system, you can use flash_image to flash a recovery image of your choosing.

EDIT: If the engineering HBOOT flashed successfully, you could also try flashing a recovery using fastboot.
[EVO 4G Android Development] numus:
We were discussing the digital signature in another thread... if you change anything in teh zip the digital signature (256 byte header) will not be correct for the changes and it will fail hboot...
[EVO 4G Android Development] nunyabiziz:
Now it becomes an unsigned file and will fail also because the SD access is locked down after the OTA
[EVO 4G Android Development] enormous:
Well hell, got my hopes up there for a bit. Thanks for your efforts whitslack.
[EVO 4G Android Development] SharkUW:
Sounds good. In hindsight I realize when rooting that I got fail messages when flashing the recovery and simply instinctively reflashed again to get a good flash. I'm guessing the EVOs utility doesn't give it a 2nd or 3rd go on a fail. That's a bricktastic process. Good thing it's just that one giving me issues :eek:
[EVO 4G Android Development] GumboChief:
I am still surprised at the number of posts I've read where people admit to running the OTA (and losing root), of their own free will.

I mean, if you are reading/posting here, wouldn't you kind of have to know better?
[EVO 4G Android Development] bprinehart:
Actually I didn't run the OTA, I flashed a "rooted" rom and all hell broke loose.
[EVO 4G Android Development] mobilemaniac:
So it sounds like you still have to do Toast's part 2. It won't let me flash either (on HBOOT .79).
[EVO 4G Android Development] kamiller42:
I am starting to think there is code in common with these activities that's not firing correctly, like a break down in an internal notification system. I have seen similar, though much more rarely, behavior with my wifi. I was connected to my wifi, leave its range for a while, and then re-enter and it did not automatically reconnect.
[EVO 4G Android Development] Raptor1214:
Can't get to recovery

Having a huge problem... I tried to follow the instructions but I'm having a problem with the new pc39img.zip.... I got the Older version problem but i can't get it to boot up to get back into adb shell... it also won't boot into recovery
[EVO 4G Android Development] jimmyeason:
thanks man it worked
[EVO 4G Android Development] caseyweed:
I just had that same problem if your talking about the "Fail-PU" issue. I deleted the "recovery-RA-evo-v1.7.0.1.img" file like it talked about in the post and replaced it with the older recovery file. (I can't post a link yet apparently) megaupload.com/?d=UJK3PQTY

hope that helped...
[EVO 4G Android Development] Raptor1214:
No recovery

Where would I be deleting that file... I can't get my computer to recognize the phone or boot into recovery... All i can do is get to the bootloader and flash different versions of PC36img.zip
[EVO 4G Android Development] reekotubbs:
I just completed this method last night on my EVO, before I was on 1.32, but only step 1.

My 3G connection was super fast and always stayed connected before I updated using this method to 1.47.

Now my 3G stays grayed out most of the time and when it is lit up it takes very long to load or download anything.

Please can someone shed light on this issue.

So again :

Firmware 1.32.651.1 HBOOT-0.79.0000

-Always connected 3g

-download speeds very fast

-phone very fast

Firmware 1.47.651.1 HBOOT-0.76.2000

-3G mostly grayed out

-horrible download speeds very slow

-phone very slow and lagging

Any way to increase speed and regain functionality?
[EVO 4G Android Development] vlug:
I must say this stock rom has a superb battery charge...... I had it unplug for a whole day. it lost 30% in half a day and 10% over night and this morning it was around 58% and i have been using it all day i even had a hour long conversation recently and percentage was at 8%
[EVO 4G Android Development] rg8rc18:
flashing dc.

Hi,

I just rooted my Evo today.. I'm on this rooted stock now. But I was just wondering if I flash DamageControl over this one. How do I go back to it if I ever want fully rooted stock again?? Sorry if this been ask before. Thanks in advance.
[EVO 4G Android Development] fuzion22:
Create Nandroid back up with Rom Manager (clockwork) before you flash Damage Control. Once you create the back-up, flash Damage Control and if you ever want to go back to fully rooted stock, just restore that file you backed up.
[EVO 4G Android Development] Burt Reynolds:
zip-a-dee-do-dah

This may have been stated before, I haven't read all the posts. But when you rename PC36IMG-1.47.651.1_eng-hboot_RA-1.7.0.1.zip to PC36IMG.zip, if you have file extensions hidden you just double zipped it & HBOOT wont find it. Took me about half an hour to figure that one out.

Thank you to all the smart people out there.
[EVO 4G Android Development] Kwincy:
Worked for me, thanks!
[EVO 4G Android Development] caseyweed:
You would be deleting the file out of the PC36img.zip file your downloaded from the first post of this thread, but your computer would have to recognize the phone in disk drive mode to put the modified zip file on.
[EVO 4G Android Development] saintsfan:
4g in and out

Is anyone else getting issues with 4g...I will stay connected until i go out of a 4g area, then when i return to a 4g, area it con't to scan and never connect. Is there a fix for this or is the norm.
[EVO 4G Android Development] MikeC84:
Thanks for this! I am now fully rooted with nand unlock.
[EVO 4G Android Development] sw99:
See this thread:

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

We are trying to figure it out.
[EVO 4G Android Development] davenukem:
Can I just flash a radio and wimax image? Our do I have to do this whole thing?
[EVO 4G Android Development] brownhornet:
Has anyone using this method successfully flashed a theme over it? Or do I need to just flash a custom rom altogether for that?
[EVO 4G Android Development] saintsfan:
thanks i will keep a lookout on that post.
[EVO 4G Android Development] nYdGeo:
I am sad to admit that I am completely confused (and a noob). In the first post it says:

“Note: This process will only work if you already have the engineering HBOOT. (If you have NAND unlocked, you already have it and can proceed confidently.) If you'd like to check the actual version, you can boot into HBOOT and look near the top of the screen: it should say HBOOT-0.76.2000, not 0.79.0000. If you have 0.79.0000, you will need to do Toast's Part 2 first before starting here.”

The above appears to indicate that I’d need to do Toast’s Part 2 in order to be able to perform this procedure. A few pages later, I saw this:

Originally Posted by whitslack

The only purpose behind Toast's part 2 is to get the engineering HBOOT installed. Everything else it installs is a waste of time, since it all gets overwritten subsequently anyway. Just start at the top of my instructions, and you'll get the same engineering HBOOT as you'd get from Toast's part 2, but you'll waste a lot less time.

This would seem to indicate that whitslack’s procedure installs the engineering HBOOT and I don’t need to do Toast’s part 2. Then there are still other posts that point in various directions and now my head is spinning. I’ve read probably 30 pages of this and I confess that I am a bit lost. I have no doubt that this is just due to my general lack of knowledge on this subject.

So if I may ask, if one has a stock, unrooted Evo running the current, stock 1.47.651.1 software, and would LOVE to be running this rooted version of the stock ROM, what would one need to do first (to get the engineering HBOOT?) before beginning the procedure in the first post of this thread. Can someone maybe translate it into noob-speak? There are references made all through this thread that I am not familiar with. I know...pretty sad for an IT guy.

Thank you one and all for any and all assistance.
[EVO 4G Android Development] JelloB:
From one noob to another:

This is how I did it. Download the simple root program here:

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

Follow the instructions and run the program. *When you get to step 3 where it tells you to visit the flash game site, make sure you refresh that screen once after the initial load as the instructions say. * After step 4 is completed, go to the extras tab and run one of the 2 flash recoveries. (I would suggest the RA version because from what I can tell clockwork's is not doing a davlik-cache wipe.)

That's going to leave you rooted but in a previous software version. Then go back to the beginning of this thread and follow the OP's instructions. Upon completion that should leave you with a fully rooted, 1.47.651.1 software stock phone.

Once you reboot after completing this process, go into your apps folder and scroll toward the bottom. Look for an app called Superuser Permission and an icon with a little ninja dude in black holding a rifle. If you see that....congratulations. You made it pal.

After this I would suggest powering down and booting into fastboot. Hold the volume down and power button simultaneously. When the screen loads, scroll down to recovery....then backup....then Nand backup. Select and run that. Once it's done you will have the ability to return back to this point at any time in the future.

(One note: For some reason my phone would not recognize the PC36IMG.zip as named. At some point I noticed it was scanning duplicating the .zip and trying to read it as PC36IMG.zip.zip. Once I deleted the .zip and just had it named PC36IMG then it read it correctly as PC36IMG.zip and everything worked like a charm.)
[EVO 4G Android Development] reekotubbs:
I did this method two nights ago and have had horrible 3G since.

I am at 74kbps per mobilespeedtest.com

before I seemed to be running over 2mps.

It seems to center around the PRI downgrading to 1.34_003.

Does any one know, maybe to OP, how to get back to PRI 1.40_003. I am willing to loose root if this is possible or even go back to firmware 1.32.651.1.

Please, someone help me, I am very stuck.
[EVO 4G Android Development] initial:
anyone getting the <DCP> Bad return status 0xffffffff error in logcat when turning on Wimax?
[EVO 4G Android Development] jacc1234:
As you know I had the same error when running BakedSnack. I am still having it after starting over.

Also I assume this is a normal message but I see this error all the time in logcat:

E/Wimax ( 90): <DC CONNECT> IO error: msg='/127.0.0.1:7771 -

If someone could explain that message I would appreciate it.

Also, I am in an area where 4G has never worked from my phone although it does work from the standalone modem so not connecting here is nothing new. I am going to try again on my drive home and hopefully will be able to connect.

Have we been able to prove that the "<DCP> Bad return status 0xffffffff" error is representative of not being able to use 4G?
[EVO 4G Android Development] initial:
I get this message after turning off 4G. It can be eliminated with a reboot but once you turn 4G on and back off, it comes back.
[EVO 4G Android Development] sw99:
I too get "<DCP> Bad return status 0xffffffff" , I doubt it's anything important, it seems to happen right before the 4G connects - successfully. Regarding the 127.0.0.1 msg, do you have AdBlock installed, I saw this too, and after removing that app, the problem seemed to go away. If you look at AdBlock it mentions this address for routing. I think it re-routes ad requests to your internal IP.

EDIT: Nevermind, I am seeing the 127.0.0.1 error again.
[EVO 4G Android Development] X-Kenshin-X:
wow this is a super informative thread, wish i had seen it before...
[EVO 4G Android Development] initial:
If I understand you correctly. You are successfully connecting and using 4G and still getting the Bad return status error message?

That puts my mind at ease.
[EVO 4G Android Development] jacc1234:
Sounds like it. Man it took a while for someone with working 4G to actually respond to all of our requests for a logcat. I kinda thought it was probably nothing significant but there was no way to know without data.

Still, I would invite anyone with a few seconds of time and working 4g to run logcat when you start 4G and see if you also get that specific error.
[EVO 4G Android Development] pilo99:
thanks for all these steps am not sure what am doing wrong i did all that but when i went to the first page the 1st step went smooth but when i added second file to go through recovery i get a red triangle not sure why ..i would appreciate any help
[EVO 4G Android Development] dglowe343:
Scary thought man. Thanks for this, it was as simple and easy as possible. Much appreciated
[EVO 4G Android Development] bob6789x:
I just bought a brand new evo today which was running 1.47.651.1 and tried simple root and a couple other methods. By that point I was running 1.17.something and i couldn't get wifi tether to work for the life of me (assuming I never got root). I followed the 19 step guide in the first post and it worked flawlessly and put me on 1.47.651.1 again with root access and wifi tether worked fine right from google code. I couldn't be happier. (NEW android user, coming from an iPhone 3g and 4)
[EVO 4G Android Development] Blackhalo:
I can't get this to work after doing simple root, my HBOOT is-0.76.2000, placed/renamed the pc36.img file on the root and it wont find it. Any suggestions?

(EDIT)Removed the .zip on the end and got it work.
[EVO 4G Android Development] jacc1234:
So I have once again followed this guide to get back to root. I have not hat 4G since I first rooted after the OTA update using simple root. I am unable to test from my house but will take a drive tomorrow and hopefully it will work.

I have tried everything in the other 4G threads so hopefully this will work. If it doesn't the only thing I can think to do is return the phone. I had 4G work once before rooting but thats it so I am wondering if there might be a hardware issue.

Any advice would be appreciated.
[EVO 4G Android Development] jglaza904:
Thanks!!! Worked Great for Me!
[EVO 4G Android Development] bwtl1000r:
This method worked great for me. I still have my 4g radio and everything. Thanks for all the work done by everyone that made this method possible!
[EVO 4G Android Development] scottspa74:
first 2 wks...

Ok, first 2 wks of this thread I was glued, BUT the last several days I haven't had time to read. BUT, I'm wondering, ...I figured I need hboot eng 76.2 (meaning toast method which wipes all data to get it) . But I just reread first post where it mentions how to know if yore totally screwed. Now that I reread, I'm wondering, I have orig hboot 79.000 but I'm still on original

ROM, no 1.47 OTA update. According to first post im wondering, 'even without toasts method to get hboot 7.26 , if I'm still on 1.32 original Rom , can I just use this without the toast/adb method. Cuz I don't do adb. ; any tips much appreciated.

O.ly care about tethering, no update onmy phone yet, essentially stock. Any advice much appreciated.

T.I.A