yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] whitslack:
You flash a recovery by using flash_image or fastboot. Like I said, I think there is an application (try searching the market for "ROM Manager") that can flash recoveries too.
[EVO 4G Android Development] whitslack:
Yes, Nandroid backs up everything. Restore just the data partition using fastboot.

fastboot flash userdata data.img
[EVO 4G Android Development] tcd2004:
Do I just go into an adb window and paste that line?
[EVO 4G Android Development] whitslack:
No. fastboot is not related to adb in any way. You need to obtain the fastboot program and then reboot the phone into fastboot. (For the rebooting, you can use adb reboot bootloader, or you can turn on the phone by holding Volume Down and Power until the white HBOOT screen appears and then select FASTBOOT from the menu.)
[EVO 4G Android Development] tcd2004:
I found that after I made the post. I'm in the fastboot menu and it gives me the option for bootloader, reboot, reboot bootloader, and power down. How would I go about restoring my system data from there ?
[EVO 4G Android Development] whitslack:
Now you use the fastboot program on the computer, as I explained previously, to flash the data.img image to the userdata partition. (You need to have moved the data.img file to your computer so the fastboot program can read it.)
[EVO 4G Android Development] johntiger:
So I've looked at pretty much everything to get my 4G fixed. Everything else seems to be working fine but the 4G. I've noticed that the it will go from scanning to authenticating to connecting then flash connecting briefly then go back to scanning it will do this twice and then stay at scanning. Anyone with any ideas?
[EVO 4G Android Development] GumboChief:
Glad I could help.
[EVO 4G Android Development] shortbus182:
How do I check which wimax version I have? I did everything in the first post, and it went great. My radio is now the latest, but my wimax seems to just scan. I do not have 4g in my area, so I'm not too concerned right now. I just want to be sure it will work when I am around 4g.
[EVO 4G Android Development] Gor3:
New to the forums :)

This method worked for me :)

Thanks!
[EVO 4G Android Development] whitslack:
The easiest way I know of is to run wimax_mtd as root in an adb shell. Near the beginning of its (very long) output, it displays the version of the firmware currently installed.
[EVO 4G Android Development] chumba8:
Yeah i tried this tho and really messed my I/O evo up you have to remove the recovery before you use this so you have your same recovery you were using it bogs at the recovery and messes up your phone i am getting a replacment right now hopefully i get old software verision
[EVO 4G Android Development] canteli:
I just have a quick question,

I'm stuck with non-working wimax, tried them all...currently running on the lastest system/radio/wimax, though I noticed something which feels off overall. My sequansd.log, report the following during the detection of the interface:

16:20 8.966 >| THSP/Manager info >| 19. register internal serviceQty= 6 kind=LOCAL

16:20 8.976 >| SQND/Itf info >| Version 4.6.2.2-25459

16:20 9.040 >| SQND/drvpoll info >| New interface detected: wimax0

16:20 9.040 >| DCX/SPY info >| Waiting for connect...

16:20 9.082 >| DC/Device audit >| 0x3E030000 Created

16:20 9.082 >| DC/Device info >| 0x3E030000 not_detected => plugged

16:20 9.086 >| DC/Device info >| 0x3E030000 plugged => firmware_upload

16:20 9.086 >| DC/bfh audit >| started

16:20 9.086 >| SQND/Device info >| N/A dead => attached

16:20 9.088 >| DC/bfh info >| Resolving THSP services

16:20 9.088 >| DC/bfh info >| Fetching tags

16:20 9.092 >| DC/bfh detail >| Board name: 'HTC-CERC32'

16:20 9.092 >| DC/bfh info >| Retrieving firmware

16:20 9.092 >| DC/bfh detail >| fwmode_value =

16:20 9.092 >| DC/bfh detail >| Selected firmware: /data/wimax/default.fw

16:20 9.094 >| DC/bfh info >| Uploading

the "Version 4.6.2.2-25459" should in fact be "25641_" right? I couldn't find a reference to this version anywhere, being the previous version "25043". Could it be possible I'm stuck in an intermediate state, or is that "Version 4.6.2.2-25459" in the sequansd.log referring to something else?

All other logs/properties_file/ diagnostic check, indicate my correct MAC/UID/PSW/Version otherwise.

Any idea? (I tried to flash different versions/sources of wimax images and the sequansd.log never register a version change!!)

Thanks.
[EVO 4G Android Development] Jackdup:
Worked for me.

The OP worked for me. My 4g was just 'scanning' and never connecting.

2 days of learning how to adb and reading every EVO post on xda and I'm fully functional with root, nand unlock, 4g, and wireless tether.

THANK YOU EVERYONE WHO CONTRIBUTES TO TEACHING NOOBS LIKE ME.

and THANK YOU WHITSLACK for this great solution.

If any noobs on a MAC, coming from unrevoked OTA v2 patch need help, I'll be glad to assist.
[EVO 4G Android Development] whitslack:
I have the same thing. I think that's the version of sequansd, not the version of the WiMAX firmware.
[EVO 4G Android Development] canteli:
Oh well,

I guess I didn't find the cure then :-P Though, I'm still not buying the whole idea that the major issue behind all this would be the deletion of the certs/keys...why would they not get reprovisioned through the network?? I really don't understand why the phone would come with preinstalled keys that do not update/regenerate OTA...i mean it successfully register to the network, fetch the account info(UID/PWD), etc, why would sprint/htc keep such a crucial signed data exchange out of the OTA update loop?

On a BB for example, you call the provider and tell them to provision your handset for this or that service and they send the keys ota. none of this makes any sense to me...
[EVO 4G Android Development] wmstwo002:
Worked perfect! I tried another method a few days ago which fixed my 4G but messed up my WiFi and Bluetooth. Used your method and everything works perfect! Thanks a million.....
[EVO 4G Android Development] canteli:
while we are at it, do you have any insight regarding this(still from sequansd.log):

16:20 18.466 >| OMADM/ WARNING >| [0mInvalid tree reference: './WiMAX/WiMAXRadioModule/0/TO-FUMO-REF' points to './FUMO' which is not exist

16:20 18.640 >| OMADM/ detail >| Board name: 'HTC-CERC32'

[1;31m

16:20 20.476 >| OMADM/ SEVERE >| [0mPolling server not deleted in a synchronized manner!

[1;31m

16:20 22.182 >| OMADM/ WARNING >| [0mNode '.' at '' doesn't match DDF

[1;31m

16:20 22.238 >| OMADM/ WARNING >| [0mThere are no parent node '' for node '.'

[1;31m

16:20 22.240 >| OMADM/ WARNING >| [0mInvalid tree reference: './WiMAX/WiMAXRadioModule/0/TO-FUMO-REF' points to './FUMO' which is not exist

The Fumo folder does exist, but it's on /sdcard/FUMO, so it's obvious it doesn't find it if it looks in the root folder... also if it's './fumo' it should be in root and hidden, right?
[EVO 4G Android Development] mrblotto:
In the market "paid apps category not showing up after doing this
[EVO 4G Android Development] whitslack:
Did you sign into your Google account?
[EVO 4G Android Development] whitslack:
I think those paths are XPaths (i.e., inside an XML document), not file system paths. Given that those are classified as warnings and not errors, I doubt that's the reason for any connection troubles. (I see the same thing, fwiw. I don't know whether I can use 4G, though, since I live in the middle of nowhere.)
[EVO 4G Android Development] mrblotto:
Yes. And my paid apps show in my downloads. I just dont have the paid app category
[EVO 4G Android Development] whitslack:
Well I don't know what to tell you. You've either lost your mind or you've installed some other version of Android Market. The one that comes with system 1.47.651.1 definitely has the "Top Paid" button at the top when you get into an application category.
[EVO 4G Android Development] frankenstein\:
I to have warnings in the log re this ./FUMO directory/file however it is not interfering with my ability to connect to or use WIMAX.

I ran a search of the file system and couldn't find it anywhere on the sd card or elsewhere. For me it just doesn't exist.

I don't think this is causing your problem.
[EVO 4G Android Development] aldo37:
Question: I did the previous instructions for this, but for whatever reason my recovery was borked (I get the triangle/exclamation point in front of a phone when I try to get into recovery). The phone boots and everything works fine though.

Since I cannot get into recovery to flash the su-2.1-e-unsecure-signed.zip file, I can't try to flash recovery.img to fix. In ADB I get a permission denied when I try to su.

Would there be any issues with trying to install the new PC36IMG-1.47.651.1_eng-hboot_RA-1.7.0.1.zip right over my install? I worry because this was essentially what was bricking phone's when it was first released no? Or is there some other way I can get root to flash a new recovery image? Or should I just start over?
[EVO 4G Android Development] whitslack:
Sounds like you have the stock recovery and no root access. Refer to this table to see what you should do next. It depends on whether you have the engineering HBOOT and which system version you're running.
[EVO 4G Android Development] aldo37:
Sweet! Had to use flashboot. I kept getting flashed failed with the official amon recovery, but it was good with toast's version.
[EVO 4G Android Development] herzzreh:
+1

Same problem here.
[EVO 4G Android Development] herzzreh:
Umm... what was it?
[EVO 4G Android Development] chumba8:
hey can someone help me to update to the ota THE RIGHT WAY I tried this on my previously rooted evo and it messed up recovery and gave me no root access I am BUYING a NEW evo without the OTA tonigh or tomorrow and want to know how to do this right this time I heard you have to take out recovery out of the winzip file or something so PM me or something gtalk/email me chumba8@gmail.com i would be happy to donate to someone for help
[EVO 4G Android Development] herzzreh:
I can't write anything to /system.

It mounts fine, but no write.

# mount -o rw,remount -t yaffs2 /dev/block/mtdblock4 /system
# mount
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
/dev/block/mtdblock4 /system yaffs2 rw 0 0
/dev/block/mtdblock6 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock5 /cache yaffs2 rw,nosuid,nodev 0 0
tmpfs /app-cache tmpfs rw,size=8192k 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
$ ./adb push Mms.apk /system/app/Mms.apk
failed to copy 'Mms.apk' to '/system/app/Mms.apk': Permission denied
[EVO 4G Android Development] ThorSonic:
O.K., I did Toast's 1 and 2. Followed everything in this thread. Everything seems to be fine (I won't be able to test 4G until Wednesday), but my PRI shows 1.34_003. My understanding is that after the update it should be 1.40...

I've done a PRI update, but it doesn't change.

Is this a problem?

Thanks!
[EVO 4G Android Development] whitslack:
That's a symptom of being on the release HBOOT (i.e., NAND locked). You need to be using the engineering HBOOT if you want to be able to write to /system and flash recoveries while fully booted.
[EVO 4G Android Development] whitslack:
PRI and PRL are different. There is no option to update the PRI anywhere in the system's user interface. The PRI (at present) is tied to the bootloader. It didn't change with the latest OTA because the bootloader didn't change.

At the moment (until someone figures out whether it's possible and desirable to separate the PRI from HBOOT), you have to choose whether you want the engineering HBOOT or PRI 1.40. Frankly, I haven't heard any arguments saying the later-versioned PRI gives any advantage. The engineering HBOOT definitely does.
[EVO 4G Android Development] timkdodson:
I did this and my 4g worked once but now yet just scans connects them immediately disconnects itself.. Not really sure what the problem is but I am hopeful that with the source code out a lot of these types of problems will be fixed
[EVO 4G Android Development] mpa4712:
Sounds like your MAC is hosed.
[EVO 4G Android Development] herzzreh:
Nope, HBOOT-0.76.2000 for me.
[EVO 4G Android Development] RevAtB:
Thank you

This and the related matrix of process helped me. I was hoping to be able to figure out where to go next as there are so many possible combinations currently of where you are right now w/ radio, wimax, hboot, recovery, NAND...

Luckily I was pretty stock, just 1st OTA so .6 runnign with unrevoked....uninstalled and then proceeded to just do step 1 & 2 of the "simple 3 click root". Step one didnt fly on its own so I just moved the PC36IMG.zip manually and moved forward.

Step 2 was fine, then came back to here and followed your steps 1-18.

Happy camper now.

Now just need to clean up /system from sprint nascar, NFL, voicemail, stocks, zone, qik, peep, footprints, friendstream, Amazon.

Flash my custom splash1 and bootanim

Thank you for sorting this all out.
[EVO 4G Android Development] A10Loogie:
Thank you!

Thank you so much. This is the most informative post I've read on this forum yet. Very educational to us n00b's.
[EVO 4G Android Development] GumboChief:
Did you su first?
[EVO 4G Android Development] A10Loogie:
One Last Sanity Check

Ok, I've read this thread and my head is spinning from version #'s and different methods. I'm running a fully rooted EVO with the RvU1.32 ROM and everything works fine. I have the ClockworkMod recovery and HBOOT 0.76.2000. So if I read this right, I can go through the steps on the very first post of this thread and end up with a phone with the 1.47 OTA applied and all the radio updates as well. Is that correct?

What's the advantage of the Amon RA recovery vs Clockwork?

I suppose when the process is done that I can just load ROM Manager and flash Clockwork Recovery back in right? Sorry for all the questions but after reading this thread there seems to be a lot of issues with 4G and I want to make sure that in fact, everything IS working before going forward.

I don't quite understand the differences between the PC36IMG files and the ROM files. Since I already have the HBOOT and custom recovery, is it possible to just flash the updated ROM? Something tells me the answer is no, but hopefully someone can explain why not so that I can learn how this system comes together.

On last question. If I want to take a virgin Nandroid backup of the system before I boot it up will I be able to do it after the second flash? Does Amon include Nandroid?

Thanks so much for the effort from all you guys!
[EVO 4G Android Development] zpilot:
Would be incredibly helpful if there is a youtube video showing how to root the new evo...
[EVO 4G Android Development] whitslack:
All good questions.

Yes, since you have the engineering HBOOT already, you can start right at this post; you already have the prerequisite. You will end up running 1.47.651.1 with the latest radio and WiMAX firmwares but still the engineering HBOOT, and you'll have Amon RA recovery.

I confess I've never tried Clockwork's recovery. I've read a few posts saying it doesn't have as many features as Amon RA. I can't comment on that. Regardless, you have the freedom to flash a different recovery after you finish the process. You can probably use ROM Manager to do that. You can definitely use flash_image or fastboot to do that.

The PC36IMG.zip is a bundle of images that HBOOT (the bootloader) can write directly to the NAND flash memory. HBOOT has no knowledge of file systems, but it doesn't need any since it just copies the images byte-for-byte onto the NAND. In contrast, an update.zip that a recovery would apply typically contains a whole bunch of files and a script directing how to extract those files to the /system file system. That does require knowledge of the file system, so HBOOT can't handle that. To flash an update.zip, you need a recovery program, which is actually a miniature Linux system, complete with kernel, so it can handle the file system operations.

Since you already have the engineering HBOOT, you could use fastboot to manually flash the system.img image from the PC36IMG.zip instead of flashing the whole bundle from HBOOT. You'd also want to flash the radio and WiMAX images.

Amon RA recovery does include Nandroid.
[EVO 4G Android Development] seankent4uf:
From what I've read, Clockwork has some issues in correctly writing to all blocks. Amon RA recovery is a very nice tool, and seems to be more stable. Once you've finished the process, just keep Amon RA recovery and use it to do full nandroid backups, wipe data, cache, etc.
[EVO 4G Android Development] darth1289:
OK, this worked for me, Here is what I did

I got my Evo a few weeks ago.

1) Did OTA update that flashed the .6 update on my EVO

2) Got root via Toast's Part 1

3) Did nand unlock via Toast's part 2

4) Tried a few custom rom's - worked but had some issues

5) Flashed back stock .6

6) Went with unrEVOked

I used this for a couple of weeks

When the new OTA update came,

7) Re did, Toast's part 1 as directed in posts here

8) Re did Toast's part 2 as directed in posts here

9) Deleted recovery image from the PC36IMG-1.47.651.1_eng-hboot_RA-1.7.0.1 posted here and re-saved zip file.

10) Flashed the new zip without the recovery as directed here

11) Flashed the su-2.1-e-unsecure-signed as directed here

I now have root, latest OTA update and my 4G still works!!, although I can't say I saw any perceivable gain in my 4G signal. I have been playing with it for only a couple of hours now. I browsed, messaged, did some GPS navigation in car with car charger plugged in, took some pictures and uploaded them etc. Can't say I noticed any huge battery improvement. Battery still seemed to run down at about the same rate as it did when I had UnrEVOked and OverClockWidget.

I did have issues with device not seeing HTC sync on PC after the update, but upgraded to the latest version of HTC sync (2.0.40) and that seemed to fix it.

Hope that helps somebody.
[EVO 4G Android Development] frankenstein\:
I wrote a small novel answering Loogie's questions but whitslack posted before me so I'll just add a few comments.

It would be better to let HBOOT flash this for you because using recovery to flash the new wimax image has been causing people some problems. you'll see posts about this and a variety of fixes for the various problems all over the board currently.

On the clockwork v/s ra recovery issue, clockwork is a good recovery but it's been reported to be having some issues. Specifically, it's not wiping the data, cache & dalvik cache partitions correctly resulting in boot loop issues when flashing new roms. RA also has some other nifty things like the ability to wipe battery info to reset your phone's stats on the battery, etc...

Be aware that RA and Clockwork both do nandroid backups the same way but store them in different locations. Clockwork places them in the clockwork dir on the sdcard. RA places them in the nandroid directory on the sdcard. if you want to restore a clockwork backup with RA you will need to move the files around so the restore process can find them. Run a backup once you've completed the process so you can see where and how RA stores the files...
[EVO 4G Android Development] frankenstein\:
There are. The only stoper you will find is if the store that sold it to you updated it to the 1.47 ota before they gave it to you. I don't believe that version has been rooted yet.

---Edit---

It appears that I spoke to soon. It looks like there is now a means to root the 1.47 update posted in the forum. I haven't tried it or examined it yet but I'm going to take a look now....
[EVO 4G Android Development] yznhmr:
ok so i made it through step 1 and step 2.. fully rooted and unlocked nand...

now what is the best way to get to the new update...1.47

I believe if i follow the instructions in the first post here, i should be good?

don't really care about custom Roms at the moment.. just want the update 1.47 and to be able to tether.. (do i have to do anything special to tether?, i was using unrevoked, before i did the full root) what do i click on to do the tether now?

please advise..

thanks in advance..

lol im so slow, it took like 4 hours for me to follow the instructions and get the ROOT to work..lol

edit:

ok i followed the instructions in this thread.. and the update worked.. but my 4g is just "scanning" it wont connect.. ..Yes i am in a 4g area. any thoughts on what to do? I tried doing the prl update.. no help..
[EVO 4G Android Development] A10Loogie:
Great info whitslack! Thanks very much for the clear explanation.
[EVO 4G Android Development] A10Loogie:
Thanks a bunch for taking the time to put together these informative replies! It's al good info for us n00b's.
[EVO 4G Android Development] Stillmatic:
tag..................
[EVO 4G Android Development] mattrb:
Lets not hate on ClockworkMod. Amon RA is not making updates anymore. As well, ClockworkMod was updated a few days ago and I am sure that the issues that you mentioned are fixed.
[EVO 4G Android Development] yznhmr:
ok i followed the instructions in this thread.. and the update worked.. but my 4g is just "scanning" it wont connect.. ..Yes i am in a 4g area. any thoughts on what to do? I tried doing the prl update.. no help..[/QUOTE]

another hour of reading, and still cant fig out why my 4g just scans.. little help please?

edit .. ok its not broke ..so to speak.. it will connect.. if i walk outside, hold it up in the air.. and wait.. it will connect, and then disconnect.. its actually worse then it was before the 1.47 update.. my 3g has fewer bars also... seemed like the phone conversations, were less clear also...
[EVO 4G Android Development] sdc177:
I went through this method and then changed the idle sleep to 300 in ##DATA# because I had the constant 3G/4G alternating issue but my MAC was okay. Now my 4G is definitely faster and doesn’t alternate with 3G however it will disconnect after a while and won’t reconnect (just scans) until I disable 4G and enable it again and then I’m fine for a while until it drops again.

Does anyone know what these symptoms mean and how to fix them? The only thing I haven’t tried was the deleting or renaming the tree.xml whatever and honestly I’m a little intimidated.

I’ve had 2 EVOs and both of them have suffered from the 3G/4G alternating after doing toasts 1 & 2 root method. I’ve never touched the unrevoked stuff.
[EVO 4G Android Development] posguy99:
IMHO, as long as Clockwork doesn't do signature verification, it should not be used. As for updates to Amon Ra recovery... what needs to be updated? Amon Ra is always responsive to *bugs*.
[EVO 4G Android Development] onyx00:
I originally rooted using "Simple root" in this same forum, and then applied this to get the updates.

One thing I am noticing now is that after about 10-15 minutes charging suddenly halts while connected to my Windows 7 system, and it runs off battery. I never had this problem prior to applying this. I confirmed it charges fine on the wall outlet charger. Also, when I power down the phone it charges fine.

Not sure what is going on. Also, I was confused about not being able to write data to the system folders, etc. until I re-read the instructions and saw I have to made it rw.

I'll probably flash some other ROMs and see if the charging issue persists, unless anyone here has some suggestions/ideas.
[EVO 4G Android Development] posguy99:
You've remounted the filesystem, that's good, but your adb push isn't happening as root, and only root has read/write access to the /system/app directory. It's set 0755, root:root.

It's not a NAND problem, it's a simple permissions problem.
[EVO 4G Android Development] posguy99:
Capability, no. But it makes it harder to do things like push to /system/app, because even if you remount in a different shell, permissions on the directory stop you from writing to it unless you're root.