there are two file you need to have on your sd card:
flash_image.zip
mtd-eng.zip
edit: make sure that you exract the files to the card.
I actually already have them there, i dont know why it cant find it...

Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
there are two file you need to have on your sd card:
flash_image.zip
mtd-eng.zip
edit: make sure that you exract the files to the card.
I actually already have them there, i dont know why it cant find it...
![]()
can you provide a screen shot of your adb commands for steps 11 and 12?
or what does the output say?
ok yes that is the issue then. maybe try and re-download the flash image zip file and re-extract it. delete the old file from the card and replace it with the new one.
Is it supposed to have a associated file type? like a .img AFTER I extract it?
well it will depend on how you have the computer setup. on mine it does not show extensions. but it should not have anything attached to it after you extract it.
I just realized that it doesnt find the file only in "
cat /sdcard/flash_image > /data/flash_image"
It passes
chmod 755 /data/flash_image
and
/data/flash_image misc /sdcard/mtd-eng.img
Any ideas?
and just to make sure but you do have usb debugging turned on and your phone set to disk drive correct?
debugging on and charge only.... not disk drive... is that why?!
ooops sorry i meant charge only
this is odd cuz i never ran into this issue. it sounds like you are doing everything correct. what size card are you using?
stock 8gb...
Would it be easier if i just wanted root access?
I've learned to be patient when working on devices, but this one... this one is being a little prick. lol I've never wanted to throw my beloved evo against a wall before today!
well unlocking it is definitely easier, but you will still have the watermark. i would take a break for a few hours then comeback and try it again. i have had these things like this miraculously working after a break. maybe captain throwback can come in and chime in as well.
Agreed. I'll come back to it. Thank you very much for all the help! Hopefully by the time i get back we get some more input from others!
My recommendation is just to proceed with being unlocked and the custom recovery. The advantages of having S-OFF are minimal at this point, since there likely won't be any additional firmware updates to this device. And, since I think every EVO 4G has to be at least a year old, the device being under warranty shouldn't be an issue either.well unlocking it is definitely easier, but you will still have the watermark. i would take a break for a few hours then comeback and try it again. i have had these things like this miraculously working after a break. maybe captain throwback can come in and chime in as well.
My recommendation is just to proceed with being unlocked and the custom recovery. The advantages of having S-OFF are minimal at this point, since there likely won't be any additional firmware updates to this device. And, since I think every EVO 4G has to be at least a year old, the device being under warranty shouldn't be an issue either.
Where did you get a brand new EVO? I could use one. I've gotten nothing but refurbs. They don't even make them anymore. Did you find some old stock somewhere?I am working with a stock evo. brand new. with warranty. lol
Where did you get a brand new EVO? I could use one. I've gotten nothing but refurbs. They don't even make them anymore. Did you find some old stock somewhere?
At any rate, my recommendation still stands. If it turns out you need to return it for repairs at some point, you can try the task of downgrading the misc partition then, when you'll likely have a bit more knowledge about the device, adb, fastboot, and how it all works.
P.S. A surefire way to find out whether your device is new or a refurb is to open the Phone app, and dial ##786#. Then scroll to "Reconditioned Status" or "Refurbishment Status" and see what it says.
Yes, that's what I'm saying. And thanks for the thanksI purchased one a white one, the store held it for me because i was out of town, came back and they had sold it from under me. i complained, spoke to a buddy of mine, and i got my hands on a white one that was kept under glass (after they went ahead and gave me a black one). haha its all always about who you know. Anyway, i no longer have my white one so i have the new black one.
Anyway, so you're saying to just go ahead and use the htcdev method and worry about the watermark later if i need to?
P.S. That number had some helpful info! and I wanted to be your 666th thanks. Not that I'm satanic or anything... haha
If you have TEP, then you don't need to worry about the watermark, if your device is out of warranty and needs to be replaced. Asurion doesn't care if your device is watermarked, rooted or whatever. If it breaks, you'll still have to pay the deductible, and they'll send you a "comparable replacement."I'm having the exact same issue. I'm no noob to using TacoRoot. I have double checked and triple checked everything and I still cannot get flash_image to move for the life of me. On the github, it lists this:
Patching MISC
I have always patched by taking an image of the partition, and taking a hex editor to it. Due to sdcards not liking to mount on boot with tacoroot, you will either need to go the hex editor route or use a modified version of misc_version.
The only thing keeping me from saying screw it is me worrying that the HTCDev way will end up voiding my TEP with Sprint somehow.
Yes, that's what I'm saying. And thanks for the thanks.
If you have TEP, then you don't need to worry about the watermark, if your device is out of warranty and needs to be replaced. Asurion doesn't care if your device is watermarked, rooted or whatever. If it breaks, you'll still have to pay the deductible, and they'll send you a "comparable replacement."
I figured I'd give tacoroot one last go, and now, whenever I type in an adb command it says
"adb server is out of date... now killing...
*daemon started successfully*"
What did I do...?!