yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] PhenixInk:
whitslack, I was able, somehow to get it to work on my phone, got everything to run and install and work. But now when I try to flash it on my wife's phone it says

adb shell

cat /sdcard/flash_image > /data/flash_image

chmod 755 /data/flash_image

/data/flash_image misc /sdcard/mtd-eng.imgadb shell

adb: not found

# cat /sdcard/flash_image > /data/flash_image

chmod 755 /data/flash_image

/sdcard/flash_image: No such file or directory

when I plug my phone back in and run adb shell I get this

* daemon not running. starting it now *

* daemon started successfully *

error: device not found.

I was reading a tutorial and following along when I got mine to take. I'm still not sure how to run sdk or adb so can you give me an idea how to get the other phone to go through correctly?
[EVO 4G Android Development] effluent:
So this unrooted me I guess..pcimg wouldn't flash recovery..so tried clockwork and amon ra, neither would work and after a few reboots trying all this apparently I no longer have su?
[EVO 4G Android Development] mobilemaniac:
This is essentially what happened to me (and many others) using the old version of this method. In that version, we first flashed to 1.32.651.1. At that point, flashing recovery failed and I lost root and could not enter recovery. I had to redo Toast part 1 and 2. With the new version, I think you are locked out of doing the Toast root because you are already on 1.47.651.1. However, you should still have the engineering HBOOT, so you should be able to flash whatever you want. Did you try using fastboot to get a custom recovery?
[EVO 4G Android Development] gmorgen1:
FYI - The simple steps described in the original post unrooted me

Titanium backup would not install. I had completed toast's methods 1 and 2 previously - guess I will have to go there again......
[EVO 4G Android Development] effluent:
I'm hoping I'm just lost here because when I did go into fast boot I saw no options about choosing a device or whatever from the instructions on the thread about flashing from fastboot. So I'm completely stuck.
[EVO 4G Android Development] sw99:
Having the same problem. Seems to have happened only after the update. I am wondering if any of the other settings need to be tweaked, such as "standby time" I have no idea what they were before the update.

When I have a 4G connection, it is rock solid. As soon as I lose it, I can't get it back without cycling the 4G switch.
[EVO 4G Android Development] nswenson:
Thanks whitslack! The updated approach for obtaining a rooted 1.47* worked flawlessly for me. Installed Titanium and restoring apps successfully.

Thank you!
[EVO 4G Android Development] effluent:
Much resentment and jealousy feel for you I do.
[EVO 4G Android Development] fapstick:
Guys,

Just want to say thanks to everyone who helped in this thread. Especially the posts on fastboot and recovering data.img. I must say fastboot is the shizznit!

Whitslack, especially.. you da man! if you are ever in Socal shoot me a PM, I will buy you a sixer of West Coast IPA! w00t!
[EVO 4G Android Development] GumboChief:
Did you enable USB Debugging?
[EVO 4G Android Development] mobilemaniac:
So fastboot can't see the device? Make sure you have the drivers installed and your computer can see the phone. I had to install the new version of HTC Sync after my first flash. Be sure you have USB debugging enabled and you are not in disk drive mode (should be charging only).
[EVO 4G Android Development] kidslow:
broken Connect to PC?

>> No matter which option I choose it will now mount the SD card on my desktop.

Turned out to be doubletwist forcing a USB mount. WOOT!
[EVO 4G Android Development] effluent:
Guess I'll pretend I never installed all this stuff and do it over. So installing HTC Sync should do the trick? Got a link? Thanks..
[EVO 4G Android Development] mobilemaniac:
HTC Sync is just another way to get the USB drivers (assuming you're on a Windows PC).

http://www.htc.com/us/support/evo-sprint/downloads/
[EVO 4G Android Development] yedranedra:
Recovery is failing

So, I am following the OP instructions and I have confirmed I have 76.2000 HBoot, but each time I try to install the PCIMG update I get Fail-PU on the recovery step, which causes me to not be able to get into recovery mode. Any suggestions on how to remedy this?
[EVO 4G Android Development] frankenstein\:
RA's recovery image may not flash properly for some people via the PC36IMG.zip file. You can overcome this by using winrar or 7zip to remove the recovery image from the PC36IMG.zip file before you try to flash it with HBOOT. If you do so you will have to flash it separately.

Here is the thread with RA's recovery in it and the instructions on how to do this.

http://xdaforums.com/showthread.php?t=705026
[EVO 4G Android Development] frankenstein\:
OK, I've extracted the boot image from this update, unpacked it, and modified the default.prop so that when you do adb remount it will work and when you do adb shell you will go straight to the # prompt instead of having to do SU to get root access.

I've repacked it into a .img file format and I'm testing it now. (gota love fastboot) I'm going to run it for a few hours to ensure it's stable and fully functional. If it passes the litmus test I'll post for those that would like to continue to run this stock rom but want these functions to work.

I'm not expecting any problems since I only made the one change. It's still 100% the stock kernel with the single attribute in default.prop changed to allow adb remount and adb shell direct to root access.

I'll package it up to make it easy to flash with recovery when it's ready. I'll probably put it up later tonight.
[EVO 4G Android Development] tool2269:
hmm just noticed.. my BT file transfer doesnt work anymore. can't send or recieve.

edit: bt earpiece works.. just sending/recieving arent working.
[EVO 4G Android Development] slapbet:
I also had the Fail-PU error. Anyway to salvage the situation if I already flashed the original PC36IMG.zip? I was rooted and NAND unlocked prior to flashing.

I tried flashing the PC36IMG.zip with the recovery removed afterward, but it didn't work. Should make sense given that nothing about the recovery would be modified (correct me if I'm wrong).
[EVO 4G Android Development] evohnoo:
Yes, if you still have root, just flash another recovery via shell. You are correct, the pc36img really has nothing to do with the recovery. Many (including myself) are removing it from the zip file before flashing...there fore no conflicts are created during the flash...
[EVO 4G Android Development] slapbet:
Could you elaborate on the procedure? My understanding is that everything is rooted, but I can't install the superuser package. Can I still flash recovery via the shell?

I'm still fairly new to Android.
[EVO 4G Android Development] mobilemaniac:
Just FYI for everyone having problems flashing RA's recovery. I had to use recovery-RA-evo-v1.7.0.2.img because version 1.7.0.1 just wouldn't work. You'll find it in the same thread.
[EVO 4G Android Development] twin001:
This worked flawlessly! I used Amon Ra 1.7.0.1 and everything went smooth. I was previously rooted using Toasts 1 and 2 methods. Flashing Damage 3.2.3 now, then theming with Konikub's red theme.

My Evo is happy now..........until a stable fully functional Froyo comes out!
[EVO 4G Android Development] myculito:
Followed the directions to a T. Worked flawlessly, and is the cleanest root I've seen yet. Glad this makes 4G work again.

Thanks OP!
[EVO 4G Android Development] evohnoo:
Did you load the 2nd file in the first post? Thats where root is regained, and superusers app is loaded

If youre rooted, yes, you can flash the recovery via shell
[EVO 4G Android Development] slapbet:
In my present state, do I need a PC to do this?
[EVO 4G Android Development] effluent:
My head is totally spinning now. I can't get any adb stuff to work now, I guess because somewhere along the way here I lost su access. So I can't do recovery via adb, Fastboot apparently doesn't recognize the device, there's no option for 'fastboot devices.' I re-installed HTC Sync and ADB. And how can I get su if I can't flash a recovery to flash a rooted rom?
[EVO 4G Android Development] evohnoo:
lol, i know the feeling... you need to get root back, most likely by doing what you did... again...

When thats done, you flash a recovery, then you boot to recovery to flash the rom

Just a question, you flashed the 1.47 on the main page right? And then you lost root? If this is true, did you load the second file? That gives you root access again, as well as superusers app
[EVO 4G Android Development] effluent:
Well it's on the card but never flashed it because I have no recovery.
[EVO 4G Android Development] evohnoo:
Ok, I gotcha now. Re root your phone... then before you flash the PC36IMG file located on the first post of this page, open it with win-rar, or something and remove the recovery.img file inside. Then reflash the PC36IMG file, the update will not touch your recovery, and you'll be good to go.

Its a snag mentioned way back in posts on this very thread.
[EVO 4G Android Development] robtrevino:
I tried this and now my 4G isn't working. Any help?
[EVO 4G Android Development] slapbet:
So to clarify, reroot starting at Toast step 1? Step 2?
[EVO 4G Android Development] evohnoo:
If you went back to 1.32 then yea run Toast... if youre on 1.47, I used http://forum.ppcgeeks.com/showpost.php?p=1853598&postcount=792

Yes, just reroot based on your OTA...

Flash a recovery, remove file from PC36IMG I mentioned THENNNN follow the instructions on the original post to install both files
[EVO 4G Android Development] apexi350z:
This is suppose to fix the 4G and not break it. Try to flash again if you can..

My 4G works great after coming from DC and Fresh.
[EVO 4G Android Development] robtrevino:
I did twice :(
[EVO 4G Android Development] slapbet:
It seems like reverting to 1.32 would be easiest via an RUU, but I'm under the impression you can't do that with HTC Sync if you're already on 1.47, regardless of HBOOT 0.76.200 or root.
[EVO 4G Android Development] evohnoo:
You may be right, ive only flashed back to an earlier version, not via RUU, so just root the 1.47 version you got and work from there
[EVO 4G Android Development] robtrevino:
it just retries over and over
[EVO 4G Android Development] frankenstein\:
Stock 1.47 kernel that enables adb remount and direct adb shell root access

OK, as promissed...

Here is the kernel with the modified default.prop that allows the use of adb remount to remount the /system partition read\write. This mod also allows you to go directly to the # prompt when you do adb shell without having to enter su to get root access in the shell. The only mod in this kernel is the change to default.prop which allows these things.

I've been running the kernel with the moded default.prop for about 6 hours with no problems. I've run quadrant and linpack as well as google goggles, Layar, mahjong, jewels and a significant number of other apps as well; constantly since loading the mod all without problem. Everything works.

Do a nandroid backup before you flash this. Then you can easily fail back to the original kernel by restoring your nandroid backup or by flashing the stock-kernel.zip I've included here as well.

To flash, just copy it to the root of your sd card then reboot into recovery and select flash zip. Then select the zip file and let fly.

I'm attaching both the unmodified kernel as stock-kernel.zip

and

the one with the modified default.prop as default-prop-mod-kernel.zip

both are signed and can easily be flashed via recovery.
[EVO 4G Android Development] frankenstein\:
there is a link toward the bottom of the op's instructions on pg 1 that may help you.
[EVO 4G Android Development] effluent:
It's a Festivus miracle! Right before I was going to root via the link above I tried fastboot adb to flash a recovery and it worked..I don't know what I did different, nothing that I can see..but whatever. Was able to boot into recovery and flash.

Thanks for the help and patience of evohnoo and others.
[EVO 4G Android Development] robtrevino:
Thanks, I tried it, but it didn't help. It still experiences the same behavior. Scanning -> Connecting -> Disconnected -> Scanning.
[EVO 4G Android Development] slapbet:
Thanks to all for your help, I was able to figure this out. Just to clarify for anyone that runs into this particular scenario, I found the easiest way to solve the problem was through fastboot.

What I failed to realize at the outset was that selecting fastboot on the phone only allows the fastboot application on your PC to work. Amon_RA's instructions regarding fastboot are executed on the PC. You can get fastboot via the following link: http://developer.htc.com/adp.html

Scroll down to where the binaries are.

I'm such a noob. Thanks, everyone, for the patience and advice.
[EVO 4G Android Development] evohnoo:
Hey glad to hear and youre welcome... Im glad it worked for you, funny how one time it doesnt work, and you do it again and it works... found that to be the case in many scenarios here. Congrats
[EVO 4G Android Development] slag02:
well..

I was hesitant to mess with rooting again after getting burned on unrevoked ota p1 - i was lucky and sprint swapped my phone

tonight I gave in

went through toast p1 and p2 and then this and it appears it is fully rooted stock 1.47 and 4g works

Thanks dev's for all the hard work
[EVO 4G Android Development] tool2269:
ok, here's my issue..i can recieve BT files from another's phone. i just can't 'send' bt files to another phone. each time, the notification area shows me trying to send a file but then says 'failed'

bt connects to my headset just fine and i can listen to music (i assume i can make calls)

this issue is new since i rooted/ did this ota because prior to that i was able to send files via astro just fine.

any ideas?
[EVO 4G Android Development] robtrevino:
Is anyone willing to help me via PM? I've done all this three times and I still cannot connect to 4G.
[EVO 4G Android Development] robtrevino:
This is the output of dmesg

<6>[ 3584.663085] sequans_xxx: loading bootloader to the card...

<6>[ 3584.663543] sequans_xxx: setting MAC address from bootloader: 38:e7:d8:XX:XX:XX

<3>[ 3584.667022] init: untracked pid 1508 exited

<6>[ 3584.674072] sequans_xxx: bootting the card...

<6>[ 3584.674499] sequans_xxx: done

<6>[ 3584.678588] sequans_xxx: wimax0: Sequans WiMAX adapter

<6>[ 3584.679443] sequans_xxx: wait until FW is started...

<6>[ 3585.183044] sequans_xxx: setup GPIO40 for wakeup form SQN1210

<6>[ 3585.187530] sequans_xxx: KTHP initialized

<6>[ 3585.187957] sequans_xxx: card initialized successfuly

<7>[ 3595.612884] wimax0: no IPv6 routers present

<6>[ 3600.537963] sequans_xxx: tx_queue len 0, enabling netif_queue

<6>[ 3600.982452] sequans_xxx: card switched to DROPPED state

<6>[ 3604.962249] sequans_xxx: got RX data, card is not asleep

<6>[ 3604.978301] sequans_xxx: waking up the card...

<6>[ 3604.981140] sequans_xxx: wait for completion (timeout 800 msec)...

<6>[ 3604.983703] sequans_xxx: card is waked up successfully

<6>[ 3605.379638] sequans_xxx: WiMAX carrier LOST [ignored]

<6>[ 3615.659545] sequans_xxx: WiMAX carrier LOST [ignored]

<6>[ 3615.852447] sequans_xxx: card switched to DROPPED state

<6>[ 3617.883514] sequans_xxx: got RX data, card is not asleep

<3>[ 3618.568908] msm_pm_wait_state(2, 0, 0, 0) failed 11001

<6>[ 3618.568908] msm_sleep(): msm_pm_wait_state failed, 11001
[EVO 4G Android Development] apexi350z:
you did this already?

If you are stuck scanning for 4g:

go into

adb shell

ls /data/misc/wimax/

look for a file with your macaddress ending in .tree.xml. we want to move that to another location so it gets regenerated.

mv /data/misc/wimax/macaddress.tree.xml /data/misc/wimax/macaddress.tree.xml.orig

update profile, update prl. Reboot and check 4G.
[EVO 4G Android Development] howdyace:
Worked to a tee whitslack. I had been putting off updating my radios and stuff till a better solution was had.

Much obliged.
[EVO 4G Android Development] i killed tupac:
looks like it's rooted, but didn't work the first time

ROM manager cannot flash recovery tho, so, can't use that :(
[EVO 4G Android Development] robtrevino:
Ok,

If I run this:

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

will It all go back to normal?
[EVO 4G Android Development] rugedraw:
No, I never backed it up. Once I ran the original PC36IMG file, I got an error in the recovery process saying Fail-PU. I tried doing it again by removing the recovery file and flashing PC36IMG again, but then without a custom recovery, I used the unrevoked method BEFORE flashing the 1.47.xx file. After flashing it the 1.47.xx and su.2.1 file, the unrevoked su app remained and I did not get a new su app icon.

I've read this thread several times over already; I must have missed that while looking for answers to other questions I've had. To answer your question about the super user app, just compare it to the superuser app you have on your phone after doing this......does it look like mine? I know that the su app I had before was a blue icon with a number sign on it.....the one I have now is from the unrevoked method.
[EVO 4G Android Development] mobilemaniac:
My icon is the same as yours. I believe it comes from this guy:

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

I guess unrevoked is using it too.
[EVO 4G Android Development] XmentalX:
i just wanted to say thank you very much for posting this

OTA'd Evo + simple root ota + this setup = fully rooted post-ota device :-)
[EVO 4G Android Development] Success100:
agreed, great write up and thanks to everyone for the help
[EVO 4G Android Development] saintsfan:
thanks for posting this ROM. I went from RVU 1.3.2 (great rom) to this one cause i wanted to have the latest update.
[EVO 4G Android Development] robtrevino:
Any Help? I posted my findings a while back. I hope someone can take pity.
[EVO 4G Android Development] WhorrerHouse:
Does this ROM come with the new radio and wimax, or will I have to flash those myself?
[EVO 4G Android Development] mpa4712:
I saw your MAC a few posts back. It looks right at the moment. At any point did you have a bad MAC? The behavior your are seeing is a symptom of a bad MAC being changed to a legit MAC.
[EVO 4G Android Development] evohnoo:
Yes, if you run that RUU, it will go back to a stock unrooted phone. However, why dont you run the rooted 1.47 version that can be found on these forums?

Just make sure you do a nand backup, and have a recovery flashed. Then flash the rooted 1.47, and have essentially a "stock" phone, with root?

Theres a small catch when flashing it though, be thorough and read the posts others have put up, specifically with removing the recovery.img from pc36img BEFORE flashing the 1.47 update
[EVO 4G Android Development] robtrevino:
Thanks, no, I've never had a bad MAC. It's very weird.
[EVO 4G Android Development] robtrevino:
I've went through all of it just now. I downgraded to the old radio and old rom,everything stock. And that didn't fix it. I went through: the OP and toast's method. and Still :(
[EVO 4G Android Development] mpa4712:
Can you let me know which methods you've tried to update your radios? The provision error you are getting are likely due to the rsa keys missing from your wimax partition.
[EVO 4G Android Development] evohnoo:
You try this? http://xdaforums.com/showthread.php?t=715525
[EVO 4G Android Development] evohnoo:
I agree... can you also tell us what other items.. roms, backups etc you installed
[EVO 4G Android Development] robtrevino:
Well, I haven't tried that link because I don't have a bad mac address.

It all started when I flashed damage's rom. I used toast's method then the one here, and then on top of that damage's rom.

It didn't work. So someone suggested I try flip's .zip file. I flashed that. It didn't work. So I decided to try and go back to the very beginning and flash the old radio. I've tried the guide on the OP several times. but It's not working. I also tried removing the .tree.xml file.
[EVO 4G Android Development] robtrevino:
Where can I get the RSA keys from?
[EVO 4G Android Development] mpa4712:
From the new phone you'll have to get after you trade that one in :)

The reality of the rsa key situation is very grim. We can't duplicate or regenerate them. They are added to the phone from HTC. I ended up having to send my phone in for a replacement due to the rsa keys.

There are ways to confirm that the rsa keys are indeed missing. Are you familiar with the fastboot utility at all?

Thanks,

Mark
[EVO 4G Android Development] tonyh703:
3G issues

Hey all, I seem to be having poor 3G performance after performing these methods. I also tried a few other ROMs and had the same issue (BakedSnack and Ava-FroyoV1). Is there any way to tell what could be causing these 3G issues?I've attached a screenshot of my software information. Thanks :D
[EVO 4G Android Development] robtrevino:
Well, I know it's there, that's all I know. But how do I check to see if they are in fact there? P.S. Thanks for the help
[EVO 4G Android Development] mpa4712:
There are directions here:

http://xdaforums.com/showpost.php?p=7045410&postcount=1

You just need to basically dump your wimax partition, then open it up in a hex editor. You should be able to easily search for the RSA key.
[EVO 4G Android Development] robtrevino:
Ok, let me try it.

I just tried this: http://xdaforums.com/showthread.php?t=715525

It didn't fix it.
[EVO 4G Android Development] robtrevino:
So I pulled the wimax.bin and wimax.raw files. How do I search for the RSA key? I opened up the files in a hex editor already. But I don't know what I'm looking for.
[EVO 4G Android Development] MrTheGeekGuy:
have you updated your radio?
[EVO 4G Android Development] mpa4712:
Just use the find or search feature in your hex editor and search for RSA followed by a huge 2048 bit string of letters/numbers.
[EVO 4G Android Development] robtrevino:
Yup,

It's there. It starts with RSA PRIVATE KEY and ends with END RSA PRIVATE KEY... has a huge block of text in the middle
[EVO 4G Android Development] mpa4712:
If I were you, at this point I would flash the first radio/wimax firmwares, then run the first RUU that was released.

I might even reboot into recovery first before the RUU and format your /system /data and cache partitions first.

If you still have the RSA keys, then there is a fix out there for you somewhere.
[EVO 4G Android Development] robtrevino:
I hope...

This one?

http://geekfor.me/evo/radio/radio139000531/

Or this one?

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

Where can I get the radio and wimax .zips?

There are so many versions out there, I don't know which one to trust.
[EVO 4G Android Development] cosine83:
After using the root method for 1.47 and then loading the engineering SPL and HBOOT then doing this my camera isn't working. Any ideas? I'm also having issues getting ClockworkMod recovery on.
[EVO 4G Android Development] mobilemaniac:
Check the first post.
[EVO 4G Android Development] mpa4712:
I would go here for the wimax and radio files:

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

your second link for the RUU looks good. Someone correct me if I'm wrong but I THINK the RUU will restore the original radio/wimax. I'm only maybe 50% sure on that though.

You want the 24722 wimax and the 1.36 radio.
[EVO 4G Android Development] retrolive:
how do i do da radio update ting, do i create into a zip file and then flash it or use adb ? if so explain to me how, i'm pretty new in this rooting thing
[EVO 4G Android Development] robtrevino:
Ok, So I'm going to try this:

http://www.mattwhitlock.com/radio-1.39.00.04.26.7z

and this:

http://www.mattwhitlock.com/wimax-4.6.2.2v25043_R04.7z

Then this:

http://rapidshare.com/files/389983490/RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_release_171253.exe

Correct?

Another thing is that when I had tried to flash the 1.32 file (exe file connected to the computer). It failed saying somehting about the boot image or boot loader being the wrong version.

Also, how do I flash the img files inside the .7z files?
[EVO 4G Android Development] robtrevino:
I'm guessing Fastboot, but I don't want to mess it up.