Yes, it said "1804 KB/s (3356672 bytes in 1.816 seconds)", which matches the size of the file on the card exactly. So my next question is: If the file is there, what might cause it to respond correctly to the recovery flash entry without actually flashing it?
I'm certain that I did that as instructed, and repeated the process twice when the flash failed. I"ll reboot the phone and try it again. Thanks again for your help and patience.
Thanks for the confirmation, Drew. I've rebooted the phone, opened the cmd line, cd'd back to the SDK tools folder, and re-entered lines 15-18. I don't even get a 1-2 second delay; it simply echoes the entry syntax, then immediately returns the root prompt on the next line. I ran the reboot recovery entry, got the quick vibration and HTC logo, and the phone went dead a second later. It's been at least 5 or 6 minutes and the phone is still dead and unresponsive to any button input. No flaming Sprint logo animation, no Hero logo or animation. If I pull the battery, it will do a full reboot, but if I try to force a recovery reboot to run a Nandroid backup, it will rapidly scroll several error messages and freeze up on the HTC logo.
I was able to flash v1.2.3 successfully and run a Nandroid backup. I rebooted and tried to flash v1.5.2, which returned 11 read errors, out of memory, each specifying a different address. What now?
Thank you for compiling all the data and your continued support to the thread! If it wasn't for your post I probably wouldn't have rooted. It just seemed so daunting before (and I consider myself a pretty tech savvy person). But within 1 hour (it would have been less had HTC Sync actually worked for me) I was rooted and loading up Fresh 1.1. HOLY SMOKES!!! What a big difference. Thank you, thank you, thank you. And especially thanks to the people who figured out the root and built the ROMS. Just further proving why Android is far superior.
Following the error addresses, the cmd line says "[1] Killed su", with the $ shell prompt on the next line. Have you seen that response, and do you still think that v1.5.2 is correctly flashed? Thanks.
Hey, no problem, I just appreciate that you're helping me at all. One thing I may not have communicated well though, is that the memory errors were not the result of pushing the file, they were a result of trying to flash it. Is that still ok to go on and try the back up and flash a rom?Yes, that is normal. I have seen that. To be sure, go ahead and using an app like astro and make sure that your 1.5.2 img is on your SD card. If it is (as stated in tutorial) you should be good to go on manually.
Also, as an FYI, I am currently at work (been here since 8am est) and can only check this every now and then. If I do not respond to a question, hopefully someone else can, or I will get back to you as I am able
Yes, and got a nandroid backup from it, with the folder copied to my PC.
I got it from step 3, so I will now try the one from pre-kitchen. Does it matter if I push a new img file on top of the file that's already there, or is it better to delete the current one and start over?Ok good. So you are rooted and have a stable RA. That is good news
Where did you get your 1.5.2 img from? Are you using the one from pre-kitchen or the one in the link in step 3?
Whichever you are using, try the other. Just to be sure, after your phone is hooked up to your PC, double to check to make sure USB Debugging is still enabled. If so, push the 1.5.2 img. Are you able to push the img successfully?
