yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] SUTHRNFRIED:
RSA report stops at

RSA request

RSA reply

There is no other info given after that point.

Running Myn warm 2.2 beta 5

custom SBC htc #15 v7 kernel

Access with root explorer because my computer skills are lame and I don't know how to adb with my mac...

Used terminal emulator to see rsa report.

Hardware 002

Flashed older 2.5 clockwork recovery because the newer one wouldn't work anymore.

This is my current standings...

When I lost 4g I was on rls4 of myns rom and ran radio combo before he had released the new 3.70 software. I was still on the previous software.

Hope this helps you to help me.

Myn 2.2 Rls 5 beta nightly - evo on steroids!
[EVO 4G Android Development] Powerslave2112:
Error message solved

OP walked me through steps and after much digging found I had another instance of adb running. Killed it in task manager and was good to go. Thanks guys at xda. Your the best in that you can drag a schlep like me through this process.
[EVO 4G Android Development] illogos:
Did you make a nandroid backup using Amon-RA 1.8 at any point? Do you still have that backup? If you do then you need to do the following:

1. In ClockworkMod flash alternate recovery Amon-RA 2.1.1

2. Copy the nandroid folder back to your sdcard if you moved it to a computer at some point.

3. Reboot Recovery into Amon-RA

4. Toggle USB mode

5. Go into your nandroid folder, go into your devices subfolder, and you will see a list of folders BCDS-xxxxxxxx-xxxx. Make a new folder and name it 20110105-1457. Now go into one of the BCDS-xxxxxxxx-xxxx folders and copy wimax.img then paste it into the 20110105-1457 folder.

6. Toggle USB off

7. Goto back/restore

8. Restore 20110105-1457

That should allow you to restore just your wimax partition without using adb.
[EVO 4G Android Development] rtmeikle:
Can you give me a step-by-step of what you did? I got the same error with unrevoked. I'm currently s:off, but don't have superuser app.

Did you just go through this entire process? I might give this a try tonight.

Thanks!

Rob
[EVO 4G Android Development] illogos:
If your recovery is working correctly and is Amon RA(don't try clockwork) then just download the zip for superuser from http://xdaforums.com/showthread.php?t=682828 and flash it in recovery.

If your recovery is not working, download the fix broken recovery zip from the OP and follow instructions to get recovery working. Then flash the superuser zip...or a custom rom.

S-OFF is the hard part. You are there though.
[EVO 4G Android Development] zikronix:
im guessing you used cw 3.0.0.1 or what ever to flash those radios?

illigos pretty much out lines it

Did you make a nandroid backup using Amon-RA 1.8 at any point? Do you still have that backup? If you do then you need to do the following:

1. In ClockworkMod flash alternate recovery Amon-RA 2.1.1

2. Copy the nandroid folder back to your sdcard if you moved it to a computer at some point.

3. Reboot Recovery into Amon-RA

4. Toggle USB mode

5. Go into your nandroid folder, go into your devices subfolder, and you will see a list of folders BCDS-xxxxxxxx-xxxx. Make a new folder and name it 20110105-1457. Now go into one of the BCDS-xxxxxxxx-xxxx folders and copy wimax.img then paste it into the 20110105-1457 folder.

6. Toggle USB off

7. Goto back/restore

8. Restore 20110105-1457

if not....your sol.

[Not directed towards you]

I swear to god...unreovked and cw costing people **** again.
[EVO 4G Android Development] zikronix:
follow the fix broken recovery directions...

then download sprint lovers rom copy to root of sd

flash through bootloader by holding power + vol-down when it ask you to update say yes and yes to reboot.
[EVO 4G Android Development] SUTHRNFRIED:
At the time it was the clockwork before 3.0.0.1...im thinking 2.0.5 something. The last 2. Whatever build.

Myn 2.2 Rls 5 beta nightly - evo on steroids!
[EVO 4G Android Development] zikronix:
yea...those didnt back up wimax....if you never did a backup with amon ra (which if you rooted this method) you should have. then your sol
[EVO 4G Android Development] catseyenu:
:(:rolleyes:

These failures undermine confidence in the platform & brand as well as giving manufacturers ammo/excuses for locking phones down further.

/Captain Obvious
[EVO 4G Android Development] badger1802:
4G issues

Went back to sprint lovers and did the PRL and profile updates and now have 4G!!!!!! Thank You so much!!!!!
[EVO 4G Android Development] SUTHRNFRIED:
Sad face!!!

Myn 2.2 Rls 5 beta nightly - evo on steroids!
[EVO 4G Android Development] zikronix:
it was part of step 14...so if you followed this guide then...it should have been done...you can try to return your phone through sprint.
[EVO 4G Android Development] glenwill:
The only other thing I did was run a nand backup after fixing recovery and before flashing. Probably a good safety measure.
[EVO 4G Android Development] zikronix:
i forgot we did that...lol...prolly because I was having keyboard issues.
[EVO 4G Android Development] rtmeikle:
Thanks! I did this, and then flashed the sprint lovers ROM. Now I'm rooted.

I really appreciate your help!

Rob
[EVO 4G Android Development] rtmeikle:
Thanks! I'm rooted now!
[EVO 4G Android Development] teeism:
Thank you for the great guide. It's very thorough and informative. I stumbled a few times but got it done without any major problem.

I've been following this thread since about v6. zikronix, you are very dedicated to this. I can see this when you update your zip and OP within hours whenever something new comes out, like when the new RA recovery came out. Thank you again for this very helpful thread and for keeping it updated constantly!!
[EVO 4G Android Development] zikronix:
A guide is no good with out the users using it or if its out dated.
[EVO 4G Android Development] mrjaydee82:
I've been running cm 6.1.2 for a while now. I went into rom manager and accidently flashed clockwork recovery. Once I realized that I flashed back to the other recovery. Do you think I screwed up my keys for 4g or u think ill be okay. How do u check to make sure its good? I do not have 4g in my area so I can flash a rom that has 4g to find out. Thank u in advance
[EVO 4G Android Development] Powerslave2112:
Did Same Thing

Mr. Jay, I did same thing and lost my rsa keys for 4g. Steps to check RSA keys are in the FAQ section on 1st page of post. If you followed all steps including optional rsa backup in root instructions your rsa keys should be backed up. Only problem i see so far is nobody has told us how to restore rsa keys. I'm a noob and am patiently waiting.
[EVO 4G Android Development] mrjaydee82:
Ill check it out. Ty. Big problem is I didn't backup keys. I guess if its messed up ill just swap phones since I'm within my 30days
[EVO 4G Android Development] jefbal99:
Amon has released a new Recovery, 2.2 which has selective Nandroid, few new error message/warnings and some speed increases.

http://xdaforums.com/showthread.php?p=10379077
[EVO 4G Android Development] mrjaydee82:
export PATH=/data/local/bin:$PATH

$ export PATH=/data/local/bin:$PATH

$su

# adb shell

adb: not found

# cat /dev/mtd/mtd0 | grep RSA

RSA-REQUEST

RSA-REPLY

RSA-REJECT

RSA-ACK

RSA-1024

RSA-REQUEST

RSA-REPLY

RSA-REJECT

RSA-ACK

RSA-1024

RSA

ReRSA

RSA requests

RSA replies

-----BEGIN RSA PRIVATE KEY-----

-----END RSA PRIVATE KEY-----#

Okay this is what I got in android terminal. Does it look like my 4g will be okay or should I go swap phones?
[EVO 4G Android Development] Powerslave2112:
That's alot further than mine. 1st command after adb replied broken pipe.
[EVO 4G Android Development] CodedAlchemy:
Hi thanks for this guide! I am having trouble with step 7, it says "No such file or directory" I have not done anything else yet....am I missing something I have done everything up to this point correctly...should I just continue with the next steps???
[EVO 4G Android Development] mdwoods:
All worked great on a hboot 2.1 3.70.651.1 hw 0003. Only issue i ran into was the broken recovery. This phone was not rooted or messed with prior to following this guide. Followed the broken recovery fix and all is good.

Something in the procedure caused the recovery to bork, but the fix worked.

not my first root on the evo just on this hboot and version.

nice job.
[EVO 4G Android Development] zikronix:
you should be ok....Id make sure your running the latest recovery.

There is two places where they get backed up...one optional one before root and then in step 14....if you rooted with this guide that procedure has been there since version one

saw that im rebuilding it now.
[EVO 4G Android Development] VTEC4ME:
Can we use the the latest recovery version from Amon_RA:

recovery-RA-supersonic-v2.2.img - MD5Sum: 8f2f12ea65460c57a58b91062f46fb27

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

Or do we have to use the recovery included in this package only??
[EVO 4G Android Development] zikronix:
yes its already repackaged into the version that is now posted on the first page

if you follow the fix broken recovery options on the first post this also includes a quick easy flashable zip to update to 2.2 :)
[EVO 4G Android Development] Hypeo:
Link to the package is dead.. anyone have a mirror??
[EVO 4G Android Development] Hypeo:
Spoke too soon.. version just got updated.. :-)
[EVO 4G Android Development] VTEC4ME:
So, in the fix broken recovery section of the first page, the download link does have the latest reocvery 2.2???

FIX BROKEN RECOVERY

This is really only needed if you rooted with one of the previos guides version 6 or lower or if you installed a different recovery like I told you not to.

1) Download File

PC36IMG_Recovery.zip

and Rename to PC36IMG.zip.

copy to the root of your SDCard and power off phone

Or do I need to get it from the main package? Where do we see what the MD5Sum is?
[EVO 4G Android Development] zikronix:
yes that has the latest recovery
[EVO 4G Android Development] cthulhu33:
Many thanks to you guys

I rooted this morning using this method and it went flawlessly. I do have a few questions tho. Can I delete the 2 pc36img files from my sd card. As I understand it one was an engineering rom that we temporarily needed and the other was the sprint lovers rom that we flashed at the end, correct? Also im a bit confused on what roms will work. Im on hw0003 and hboot 2.1, build 3.70 and kernel 2.6#15. Any roms built off 3.7 and use a #15 kernel should work right? Thanks
[EVO 4G Android Development] VTEC4ME:
Thanks.

How/Where do we see what the MD5Sum is to make sure it's not corrupted????

Edit:....Nevermind.
[EVO 4G Android Development] badger1802:
4G Broken

helping some friends root after sucessfully doing mine but having some problems with the 4G. when i look for the tree.xml file its not there, the only thing listed is:

sockets

and when I do the cat /dev/mtd/mtd0 | grep RSA to view the keys I get:

grep: not found

write: Broken Pipe

I did make a backup of the RSA keys in step 6 but i'm not sure what is going on here, any advice?
[EVO 4G Android Development] takeheart:
My pleasure. One last thing - after I configured my phone a bit, I noticed the issue had come back. I did the tree.xml trick and it fixed it again, but should I expect to have to perform that regularly?
[EVO 4G Android Development] lithid-cm:
Using linux... its not really working at this last part.

lithid@lithid-desktop:~/Desktop/Evo/2.02$ sudo /usr/local/android-sdk-linux/tools/./adb shell busybox --install /sbin
- exec '/system/bin/sh' failed: Permission denied (13) -

Ideas?

Edit: I fixed it.

lithid@lithid-desktop:~/Desktop/Evo/2.02$ chmod -R +x recovery/

Silly me
[EVO 4G Android Development] matthewdavisnelson:
Okay, I had to take a short break but I'm back to work. I've downloaded the new zip file, hboot202-s_off-V6.2.zip, and extracted it to my hard drive. I'm stuck on Step 16 but it doesn't appear that any of the previous steps have changed.

I'm trying to push the recovery folder to my EVO (adb-windows push recovery /) but I get an error:

push: recovery/etc/mtab -> /etc/mtab

failed to copy 'recovery/etc/mtab' to '/etc/mtab': Read-only file system

I'm re-downloading the aforementioned zip file with the hope that the mtab file from the error message was messed up. Viewing the properties of the zip file's contents, nothing is read-only.

EDIT: I failed to boot the phone into recovery. Once in recovery, the recovery folder copied to the device w/o issue.
[EVO 4G Android Development] takeheart:
After I get 4G up and running, and then reboot the phone, upon reboot, 4G says "Failed" and then just sticks at Turning On without going anywhere.. This is not ideal. Anybody running into this issue?
[EVO 4G Android Development] zikronix:
no...just make sure your using a rom with a stock kernel for your phone based of .30 after the tree.xml you should reboot and do the profile and it should be ok
[EVO 4G Android Development] zikronix:
something didnt execute...thats your phones file system thats read only
[EVO 4G Android Development] matthewdavisnelson:
I am now rooted with the custom recovery in place. Per Step 19, I've stopped before flashing to a custom ROM to update the profile and PRL.

With my stock ROM, I used to select "Update Profile" or "Update PRL" and I'd be taken to another screen, where I could press a button to start the update. With the current ROM (installed during the process of rooting), I don't see these other screens. Pressing "Update Profile" or "Update PRL" highlights the items in question but doesn't seem to start any updates.

Does my experience match anyone else's? Again, bear in mind that I've yet to flash a custom ROM.
[EVO 4G Android Development] zikronix:
thats seems weird...but im not sure if its necessarily ab normal
[EVO 4G Android Development] Soligna:
Just went through the entire process flawlessly until flashing PC36IMG.zip I got main version is older. Here is my phone's version.

SUPERSONIC EVT2-3 SHIP S-ON

HBOOT-2.02.0000

MICROP-041f

TOUCH PANEL-ATMELc03_16ac

RADIO-2.15.00.09.01

OCT 14 2010, 19:14:47
[EVO 4G Android Development] kc_sheets:
ok I have done the manual root method, was getting radio_pu errors but i had root access and s-off, could not use a rom it would error out, i had to use the stock 3.30 pc36img.zip from (aegiswa

http://www.morninglion.com/tp2martin...209_signed.zip from ) to make my phone work. So phone is working and I tried flashing (fresh, calkulins) rom, every time i load into recovery it says (E: invalid command argument), i have a hw 003, im glad i have root. but i cannot use a custom rom and when this new update keeps asking me to install it fails, and when i tried to dl the one provided and apply through recovery it failed and i had to reload the pc36img

this is becoming a hassle. can anyone help!! also when i make a recovery point just 30 min ago after reinstall and removing base apps, my phone restarted failed and i had to reload again. Does this new method fix the radio pu issue i just want to get this done and not have to reload my phone 15x

i get this when loading a rom

assert failed: write_raw_image("/tmp/boot.img". "boot")

E:error in /sdcard/fresh-evo-3.4.0.1.zip

status 7

install aborted
[EVO 4G Android Development] zikronix:
I think we determined...you have bad blocks....return your device
[EVO 4G Android Development] zikronix:
you didnt flash mtd-eng
[EVO 4G Android Development] kc_sheets:
can you explain better what do you mean bad blocks and how can i return my phone! if its says hboot s 0ff
[EVO 4G Android Development] zikronix:
you can turn s-on by following the guide on the front. Going into detail about the bad blocks issues has been discussed adnauseum on thesed forums....but basically all memory had bad blocks and errors. Some of the roms are too big and you dont have the availaible space needed to flash the rom. the stock rom works which will fit in the space on your phone.
[EVO 4G Android Development] Soligna:
Is there some sort of a confirmation when flashing mtd-eng i entered the command i dont think it flashed it when i did though.
[EVO 4G Android Development] matthewdavisnelson:
I could be mistaken but a handful of the commands that you'll execute, e.g., making the CHMOD changes, don't supply any confirmation that they're done or executed successfully. If you make a typo, though, you should receive an error message.
[EVO 4G Android Development] chubbzlou:
I'm rooted and running sprintlover rom flash via bootloader. I think since we have the new hardware on our phone the boot.img in recovery flash roms need to be updated.

I will try to look in the .img files to see what is the difference between the sprintlovers boot.img and all others. Before we can really state that we have bad blocks
[EVO 4G Android Development] zikronix:
Im just reciting what was discovered.
[EVO 4G Android Development] kc_sheets:
ok should i put s- on and start over with the manual s-off or just put s on and take it to the store kind of lost and i searched the forum for bad blocks and see nothing but threads of useless info nothing really solid
[EVO 4G Android Development] aglide:
Success!

I took the plunge and followed the guide last night using "V6.2" of the download package, and it went perfectly, as far as I can tell. One caveat: I decided to go with CyanogenMod so I'm not sure if my 4G is working, because Cyanogen doesn't support 4G yet.

I'm using one of the new EVOs with the new camera.
[EVO 4G Android Development] zikronix:
you didnt flash clockwork recovery did you?
[EVO 4G Android Development] jefbal99:
Thanks for this, was able to root and unlock two hardware 004 EVOs four family members :)

Swyped from my Fresh EVO via XDA App
[EVO 4G Android Development] badger1802:
nope, flashed the recovery that came with the root procedure.

we did a backup image of the wimax partition, is there any way to restore this image?

I can't find anyone who has explained how to restore this backup that we are told to do.
[EVO 4G Android Development] cthulhu33:
Bump

I'm pretty sure I have most this figured out. I'm just looking for some verification of the info in my post. I like the included rom but I was wanting to try something off sense or something modified. I have the roms for VP3.70-B20 and Azrael_X_v3.1_by_Ricsim78. Im pretty sure these will work but I just wanted to make sure. You guys are great.
[EVO 4G Android Development] dkdude36:
try the fix broken recovery file at the bottom of the op post.
[EVO 4G Android Development] devonparrish:
Too bad that doesn't answer the question.
[EVO 4G Android Development] gpz1100:
Why didn't you answer the question??

As I understand it, the nandroid backup file is nothing more than a zip. So make a copy of it, then using appropriate zip tools, remove all the other img files other than wimax.

Perform restore, and the wimax.img should go in its rightful place. Right?
[EVO 4G Android Development] easy1600:
I'm getting the same message (I am using the supplied adb.exe). Where did you find the other instance of adb.exe to kill? I don't see it in task manager.

The message is after I type 'adb sync' I get back; "adb: Product directory not specified; use -p or define ANDROID_PRODUCT_OUT"

edit: Nevermind, I continued on anyways and everything is working just fine. Thanks for the super detailed guide. You guys keep rockin'.
[EVO 4G Android Development] gpz1100:
zikronix,

Got a question for you about the unrooting process itself as it pertains to 0004 hardware versions.

In step #9, the PC36IMG.zip (the renamed ENG one) gets flashed. I believe this contains the .76 ver of hboot.

In step 11, the PC36IMG-MR.zip gets renamed and flashed. However, the file itself does not contain a hboot.img file.

What I don't understand is since hboot is not flashed again, how does it revert back to 2.10?

The bases for this question comes from the other thread where folks are trying to maintain the ENG version of hboot, and are unsuccessful on 0004 hardware (due to the eraseblock size?)

If such is the case, how does flashing the hboot within the ENG zip work with these hardware revision?

If the answer to this is beyond the scope of this thread, please redirect where this is discussed. Thanks!

Thanks!
[EVO 4G Android Development] zikronix:
The first pc36img file you flash (the eng one) is a signed file from HTC. If I had my choice I would pull those files out of that zip however, doing so would break that siganture and it wouldnt flash. We never downgrade the hboot in this process. When you flash that first file it bypases the bootloader, and usually at least one or two more things.

In short the bootloader is protected against downgrades, for various reasons. As you probably already know downgrading an hboot can be extremely dangerous, it may or may not work. If your phone happens to have the old partition structure then it will probably work if not...you just bricked yoru device most likely (some times they can be recovered)

and for as why there is no hboot in the second pc36img file...because now that we have s-off that file is unsigned, so there is no reason to have it in there. In fact if we had it in there it could potentially unroot the phone or cause other problems.

Hope this answers your questions and Happy rooting
[EVO 4G Android Development] zikronix:
Rough procedure for restoring wimax.

If you rooted this using this thread there are two places we backed up wimax.img files. There should be a wimax.img file in the root of your sdcard. and one in the nandroid that you did in step 14

If you plug in your phone and browse the SDcard

navigate to the folder "nandroid" on the sdcard. Inside there you will see your phones serial number. It may look something like this "HTxxxxxxxxxxx" where the x's are is various letters and numbers.

Go into that folder, inside there you should see some folders that are named similar to this format here "BCDS-20101230-2106"

So now create a new folder and lets call it "RSA-PR-BACKUP" then copy that wimax.img from the root of your SDcard to that folder that we just created.

once you did that reboot into recovery goto the backup/restore and select it. then select nandroid restore, select your serial number, then select wimax back up.

Now it will restore but it will throw an error because there is no md5 in that folder so the backup cant be verified

once thats done back out and reboot the phone when it comes up do a prl/profile update and test...I think it should work
[EVO 4G Android Development] zikronix:
I modified the guide and the faq to put the wimax backup into a folder

So if your using the new updated guide here is a Rough procedure for restoring wimax.

If you rooted this using this thread there are two places we backed up wimax.img files.

If you plug in your phone and browse the SDcard

navigate to the folder "nandroid" on the sdcard. Inside there you will see your phones serial number. It may look something like this "HTxxxxxxxxxxx" where the x's are is various letters and numbers. There should also be a folder called "RSA-PR-BACKUP"

Copy the "RSA-PR-BACKUP" to the folder with your phones serial number

Once you did that reboot into recovery goto the backup/restore and select it. then select nandroid restore, select your serial number, then select wimax back up. Now it will restore but it will throw an error because there is no md5 in that folder so the backup cant be verified once thats done back out and reboot the phone when it comes up do a prl/profile update and test...I think it should work
[EVO 4G Android Development] gpz1100:
Thanks for the reply. Yes, this does clear things up. I'm understanding that hboot is more or less analogous to a bios on a computer. Flash the wrong bios and the board becomes a brick (or a rather nice wall decoration). One thing that still puzzles me is during the rooting process on my device, I could of sworn I saw a different version at the bootloader screen than 2.10. Or is this because there was a different bootloader, but only temporarily/in memory?

As your describe, I do remember seeing some files skipped during the flashing of the first rom (possibly of the second one too, don't remember). I wish I knew then what I know now with regard to the different partitions and their use. No point in unrooting to rediscover at this point.