So when I type sudo -s I get a message
"sudo: can't stat /etc/sudoers: Input/output error
sudo: no valid sudoers sources found, quitting"

And it just goes back to the prompt ubuntu@ubuntu:~$

What am I supposed to see there (I assume it shouldn't be an error)? Any idea how I can fix it? This is with Ubuntu running off a flash drive.

Originally Posted by WatermelonSlim

So when I type sudo -s I get a message
"sudo: can't stat /etc/sudoers: Input/output error
sudo: no valid sudoers sources found, quitting"

And it just goes back to the prompt ubuntu@ubuntu:~$

What am I supposed to see there (I assume it shouldn't be an error)? Any idea how I can fix it? This is with Ubuntu running off a flash drive.

Log in with an Administrative account.

Originally Posted by QueNerdo

Whenever I try to boot my phone into recovery, even when it's not plugged in to a computer, it goes straight to the picture of a phone with a red exclamation point.

Any one have any ideas on why this happens? I just did a factory reset so it's basically a brand new phone. I have a nonstock battery and nonstock SD card, could those be an issue?

This is the normal recovery screen... What are you getting at here? Are you going to be downgrading or are you in the process (there is no part of this that requires recovery, other than tacoroot, which tells you what you're supposed to do when those screens come up)

I'm not sure what you're doing with recovery...

Originally Posted by QueNerdo

Whenever I try to boot my phone into recovery, even when it's not plugged in to a computer, it goes straight to the picture of a phone with a red exclamation point.

Any one have any ideas on why this happens? I just did a factory reset so it's basically a brand new phone. I have a nonstock battery and nonstock SD card, could those be an issue?

You need to flash a Recovery image to your phone. If you have already unlocked the phone, boot into the BootLoader, switch into FastBoot USB and then from a terminal enter

fastboot flash recovery "\path\to\recovery.img"

Originally Posted by QueNerdo

Whenever I try to boot my phone into recovery, even when it's not plugged in to a computer, it goes straight to the picture of a phone with a red exclamation point.

Any one have any ideas on why this happens? I just did a factory reset so it's basically a brand new phone. I have a nonstock battery and nonstock SD card, could those be an issue?

It sounds like your recovery got wiped. Try flashing it again by zip or using fastboot.

From the responses that I've seen in this thread, I believe I can now declare the HBOOT Downgrade Toolkit 0.2.2 Boot CD as Stable.

Whoo!

Thanks to everyone who reported back their results with the Boot CD.

I have a few tricks up my sleeve for the next version. Hint: First step is pretty much one-command. This includes misc_version change. Also zergRush Temp Rooting is now a one-command process. (Still working on TacoRoot (and maybe one or two more things) before pushing it.)

With that said, I have realized that posts related to the Live CD have taken up more comments than I expected. Out of respect for Unknownforce, I am planning on starting a thread for the Live CD as soon as I have the new version done. I may however need Unknownforce's good graces if I start a thread in the EVO 3D Development Forum (if you wouldn't mind, of course ), as I can see myself getting some strange looks from moderators.

~co~

Originally Posted by closeone

From the responses that I've seen in this thread, I believe I can now declare the HBOOT Downgrade Toolkit 0.2.2 Boot CD as Stable.

Whoo!

Thanks to everyone who reported back their results with the Boot CD.

I have a few tricks up my sleeve for the next version. Hint: First step is pretty much one-command. This includes misc_version change. Also zergRush Temp Rooting is now a one-command process. (Still working on TacoRoot (and maybe one or two more things) before pushing it.)

With that said, I have realized that posts related to the Live CD have taken up more comments than I expected. Out of respect for Unknownforce, I am planning on starting a thread for the Live CD as soon as I have the new version done. I may however need Unknownforce's good graces if I start a thread in the EVO 3D Development Forum (if you wouldn't mind, of course ), as I can see myself getting some strange looks from moderators.

~co~

When can we expect the new version? No rush or anything.

So I made it past the first step. The mainver said 1.10.651.2 like it's supposed to.

I went to step 2, put the PG86IMG.zip on the storage card (nothing else was on the storage card), rebooted to bootloader, it found the file, plugged it into AC, and then hit volume up.

I saw updating on the screen, waited about 5 seconds and pulled the power cord then plugged it right back in. Now my phone is stuck on an HTC screen. I get a bright power light if I plug the charger in.

Not sure if the device is ready for the Linux part yet or not. Which brings me to another issue, lol

In Ubuntu, when I open 4 terminal windows, chmod 0755 /path/to/emmc_recover works as expected. However, when I do the ./emmc_recover --flash hboot_1.4.nb0 --device /dev/sdb13 it works on 3 termnals only. I got b, c, and d. On the 4th, I tried e but it gives a message "bash: ./emmc_recover: No such file or directory" It gives me that same message on the 4th window no matter what letter I put there too.

Meantime, my phone won't boot up. It just goes to the HTC screen.

I probably need to start over, but not exactly sure how I can do that? When I try tacoroot, it just flies right through with a bunch of "'/system/bin/sh' failed: No such file or directory (2)- " errors. Then at the end it says to wait for the phone to finish booting and unplug the USB cord, blah blah blah, press any key to continue.

What should I do?

Originally Posted by WatermelonSlim

So I made it past the first step. The mainver said 1.10.651.2 like it's supposed to.

I went to step 2, put the PG86IMG.zip on the storage card (nothing else was on the storage card), rebooted to bootloader, it found the file, plugged it into AC, and then hit volume up.

I saw updating on the screen, waited about 5 seconds and pulled the power cord then plugged it right back in. Now my phone is stuck on an HTC screen. I get a bright power light if I plug the charger in.

Not sure if the device is ready for the Linux part yet or not. Which brings me to another issue, lol

In Ubuntu, when I open 4 terminal windows, chmod 0755 /path/to/emmc_recover works as expected. However, when I do the ./emmc_recover --flash hboot_1.4.nb0 --device /dev/sdb13 it works on 3 termnals only. I got b, c, and d. On the 4th, I tried e but it gives a message "bash: ./emmc_recover: No such file or directory" It gives me that same message on the 4th window no matter what letter I put there too.

Meantime, my phone won't boot up. It just goes to the HTC screen.

I probably need to start over, but not exactly sure how I can do that? When I try tacoroot, it just flies right through with a bunch of "'/system/bin/sh' failed: No such file or directory (2)- " errors. Then at the end it says to wait for the phone to finish booting and unplug the USB cord, blah blah blah, press any key to continue.

What should I do?

You're not bricked if u see the splashscreen or hboot. Keep trying to brick.

Originally Posted by Unknownforce

Not sure how, but just had a user recover from a bricked S-OFF, theirs was not intentionally bricked, but it was in DL Mode when plugging in...

This person bricked their device somehow by flashing a rom via ROM Manager (ICS Playground ROM to be exact)

I personally don't know how that is possible, as ROM's do not contain anything that would brick a device, but it definitely was bricked, and the user brought it back to life using Step 3 on this guide, and it still reads S-OFF, kind of makes me want to try to see what I can come up with on the whole S-OFF/EMMC Mode theory, but I think I've risked my device enough for a bit, maybe when I'm planning on upgrading, I'll check it out

I flashed the ICS playground ROM released earlier today before I heard it bricked a few people's phones. It bricked mine. I was s-off on the eng hboot and I tried to install playground via boot manager pro. It said it installed successfully and I tried to boot into the ROM. The phone rebooted, showed my splash screen for ~10 seconds, then shut off. I haven't been able to get it to turn on or show a charge light since.

I posted a thread in the Q&A about this and someone recommended I come here. I tried using step 3 and followed all instructions. I opened terminals in ubuntu and went from sda13 - sdk13, and none of the windows reacted when I plugged my phone in while holding down the vol down button. I'm going to reboot ubuntu and try a different linux kernel (since I just installed a new kernel yesterday night, so it might be buggy still) and I'm going to go through sda13-sdz13.

Does anyone have suggestions for me, or does anyone who's already recovered from this problem using the emmc_recover method have any pointers? Everything was entered properly in the terminal, I didn't have any root errors or anything, it's just that none of the windows changed anything after saying waiting for device...

EDIT: I'm a little confused from the instructions, should my battery be out when I plug it in while attempting step 3? I'm gonna try this now either way, it can't hurt my phone any more than already having it bricked, right? here goes nothing