Jump to content

[HELP] Can't boot into recovery after flashing rootedupdate.zip and another issue!


Recommended Posts

Guest localman
Posted (edited)

Hey Paul / guys, I need your help.

First, I successfully rooted my HTC Desire. After two weeks of testing I tried to cook a ROM.

I took Pauls "rootedupdate.zip" and put it into the kitchen. I removed and added several apps and flashed it on my device.

The flash has finished and I thought everything was working. After 10 minutes, I wanted to flash another ROM. So I had to go in the Recovery Mode. I typed this command (which always worked) in the terminal: "./recovery-linux.sh" I typed it again and again. But it didn't work.

"Device not found"

If I normal boot the desire, the pc AND the desire don't see the SD card. I have no idea what I can do. I tried a lot of things but nothing worked. For example: I tried to flash the stock ROM, to root the device again... but the result is always the same: "Device not found" If i try to root my device again, the step1 works perfectly but the step2 makes the known problem.

What can I do? I hope you understand my problem. Please help me.

P.S. Sorry for the bad English, I'm Swiss.

Edited by localman
Guest geek78
Posted
Hey Paul / guys, I need your help.

First, I successfully rooted my HTC Desire. After two weeks of testing I tried to cook a ROM.

I took Pauls "rootedupdate.zip" and put it into the kitchen. I removed and added several apps and flashed it on my device.

The flash has finished and I thought everything was working. After 10 minutes, I wanted to flash another ROM. So I had to go in the Recovery Mode. I typed this command (which always worked) in the terminal: "./recovery-linux.sh" I typed it again and again. But it didn't work.

"Device not found"

If I normal boot the desire, the pc AND the desire don't see the SD card. I have no idea what I can do. I tried a lot of things but nothing worked. For example: I tried to flash the stock ROM, to root the device again... but the result is always the same: "Device not found" If i try to root my device again, the step1 works perfectly but the step2 makes the known problem.

What can I do? I hope you understand my problem. Please help me.

P.S. Sorry for the bad English, I'm Swiss.

Sorry ....

http://android.modaco.com/content/htc-desi...-and-root-a2sd/

Guest Too51oll
Posted
Does that mean he's bricked?

Unfortunately it sounds like. Another one :)

Guest xhemp
Posted
But I didn't install A2SD.

Did you by any chance used the "USB Mount" by mistake on the green recovery screen?

It's the second option just below Reboot device.

Guest Pyr0x64
Posted

i've used that option in the past and had no problems :)

Guest xhemp
Posted
i've used that option in the past and had no problems :)

Well, myself and maybe 20 more had a problem after using that option so maybe's something there ;)

Guest Pyr0x64
Posted

guess i won't be using that again then :)

Guest xhemp
Posted
guess i won't be using that again then :)

Please, don't, we don't another one in the USB/BT/FM-less club ;)

Guest localman
Posted (edited)
Did you by any chance used the "USB Mount" by mistake on the green recovery screen?

It's the second option just below Reboot device.

Yes I did :S

About 4 times.

Is there already a solution to fix this? :)

Edited by localman
Guest craigcrawford1988
Posted (edited)

I installed A2SD+ and partitioned my SD card with fat32, ext2, and linux-swap. I haven't moved the apps over yet, what should I be worried about?

What do I need to avoid doing in other words?

Edited by craigcrawford1988
Guest xhemp
Posted (edited)
Oh man.

That means I can't do anything? :)

Just wait?

Well, you can return your device and get a new one, if you managed to do that but there's still no fix for this unfortunately.

I installed A2SD+ and partitioned my SD card with fat32, ext2, and linux-swap. I haven't moved the apps over yet, what should I be worried about?

What do I need to avoid doing in other words?

This happened for most of us (some people claim that they didn't touch it) when we activated the USB Mount option (2nd option) on the Recovery menu.

So, avoid doing that at least.

Edited by xhemp
Guest craigcrawford1988
Posted
Well, you can return your device and get a new one, if you managed to do that but there's still no fix for this unfortunately.

This happened for most of us (some people claim that they didn't touch it) when we activated the USB Mount option (2nd option) on the Recovery menu.

So, avoid doing that at least.

I can still get to recovery so I guess I'm ok as long as I don't press that menu option lol.

Guest xhemp
Posted
I can still get to recovery so I guess I'm ok as long as I don't press that menu option lol.

Yep, like I said, there are people that used that and didn't have any problems but the vast majority didn't have a good outcome so it's better be safe than sorry :)

Guest Too51oll
Posted
Yep, like I said, there are people that used that and didn't have any problems but the vast majority didn't have a good outcome so it's better be safe than sorry :)

I'm one of those that using this option almost everytime I flash my phone. First there was a theory that apps2sd caausing this problem now it's mount USB in recovery. Hmm... I better not to use it again, just in case.

Guest craigcrawford1988
Posted

I guess the best information at the moment is to avoid using A2SD/A2SD+ or the USB Mount.

Guest localman
Posted

Ok, I try to return my device and get a new one. I hope the store will give me a new desire.

Guest geek78
Posted

I have my new one since 2 hours. I won't root it again without a solution for those issues ...

Guest localman
Posted

I don't bring my phone to the store because they problably won't give me a new one ;)

So I try it myself. If anyone has a good idea, please tell me :)

I will inform you if I get it.

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.