Issues with USB connectivity etc. and root / A2SD

[Guest xhemp]

Yes, this is just an idea (i am a noob with Linux / android )

Cool but I can still test.

I'm new to the world of Android but not that new to Unix :P

But why would you think that it flipped to USB OTG mode?

Will reply as soon as I test it.

[Guest xhemp]

Paul, maybe USB port is now in USB OTG mode (driver maybe in the kernel of the test rom)? Don't have the hardware to test it ....

For the sake of it, I've tested but the device can't see the hard disk so it's not on host mode too I believe.

[Guest Specialist79]

For the sake of it, I've tested but the device can't see the hard disk so it's not on host mode too I believe.

Did you verify this by inspecting the dmesg output?

[Guest NOFX]

Hope some of you geniuses find a solution :-).

First thing after I'm back on full speed I'm gonna purchase my Ad-Free MoDaCo subscription and cook myself the perfect ROM (without A2SD LOL)

[Guest ZiCoN]

Paul.... Any news on an SPL to work with? (I know you'll give word when you do.. but an update would be much appreciated :P )

[Guest jeckyllhavok]

No new updates i fear, a desire without usb, bt and fm is not mouch fun

[Guest Biliskner]

No new updates i fear, a desire without usb, bt and fm is not mouch fun

I'm seeing all these ROMs that I want to flash but cannot... sigh :)

(don't care about BT or USB data connectivity, FM is a bit of an inconvenience)... really only need USB for flashing recovery, other than that, hardly use it.. :|

[Guest xhemp]

Did you verify this by inspecting the dmesg output?

Yes, I've checked dmesg and /dev, no joy.

Any other idea? :)

[Guest vastloper]

Yes, I've checked dmesg and /dev, no joy.

Any other idea? :)

I think we can do a lot when we can get in at command mode.

There are a lot of at commands that can be used.

Only problem is how do we get in that mode.

On other phones it is rtask a

so i tried fastboot oem rtask a

but then i only 3 dots as reponce and everything seems to hang. Grrrrr

Greetings from a vastloper

edit:

When i look in the hboot file i see text like:

AT@CID= %d: Change CID to

AT+HTC_DM=C841746477616F70

%d: Unlock NV with SPC DM000.dat..............

AT@SIMLOCK=1,%x,%s

AT@CID=12345678

ÿÿc AT-Command Interpreter ready

AT@SECURITY=

Edited May 12, 2010 by vastloper

[Guest jeckyllhavok]

I think we can do a lot when we can get in at command mode.

There are a lot of at commands that can be used.

Only problem is how do we get in that mode.

On other phones it is rtask a

so i tried fastboot oem rtask a

but then i only 3 dots as reponce and everything seems to hang. Grrrrr

Greetings from a vastloper

edit:

When i look in the hboot file i see text like:

AT@CID= %d: Change CID to

AT+HTC_DM=C841746477616F70

%d: Unlock NV with SPC DM000.dat..............

AT@SIMLOCK=1,%x,%s

AT@CID=12345678

ÿÿc AT-Command Interpreter ready

AT@SECURITY=

What we need is a way to security unlock the bootloader or an engeneering spl. Some people think that a simple oem eraseconfig would help

[Guest nilezon]

Some people think that a simple oem eraseconfig would help

The idea of eraseconfig solving this problem probably came from this information:

http://android.modaco.com/index.php?s=&amp...t&p=1235366

[Guest jeckyllhavok]

The idea of eraseconfig solving this problem probably came from this information:

http://android.modaco.com/index.php?s=&amp...t&p=1235366

It's a device with an HTC own kernel, too. I don't believe in a real brick or so, it just s***s that HTC have the SPL Security locked

[Guest vastloper]

It's a device with an HTC own kernel, too. I don't believe in a real brick or so, it just s***s that HTC have the SPL Security locked

fastboot oem rtask eraseconfig seems to be a valid rtask command also indeed

same 3 dots then phone hanging.

Hmmm

Need differend fastboot program perhaps ?

[Guest jeckyllhavok]

fastboot oem rtask eraseconfig seems to be a valid rtask command also indeed

same 3 dots then phone hanging.

Hmmm

Need differend fastboot program perhaps ?

The command is just fastboot oem eraseconfig, dunno if there's another fastboot app

[Guest NOFX]

You can flash via fastboot oem rebootRUU then fastboot flash zip zipfilename (where zipfilename is a signed zip).

I have a question - did any of those having this issue use the 'USB mount' function in recovery?

P

Sorry guys, but this doesn't help me.

I can get into fastboot by holding the 'back' button and turning on. And I can navigate to the androidsdk/tools folder no problem. But when I here type fastboot rebootRUU I get an error.

Which file should be where on my harddrive, and on my SD-card?

The same question goes with the 'fastboot flash zip zipfilename'. Which zip is this, where should I put it, and where do I get it?

I just want to flash a stock ROM - and I can't by just running the .exe file. It says something about having 'too many images' or something. And it gets stuck while 'waiting for bootloader'. This runs to 100, and then gives me an error-message. Annoying!

Thanks guys :-)

Edited May 12, 2010 by NOFX

[Guest NOFX]

Sorry - what it says when I run the .exe file is:

Imageversion: version-main FAILED (status read failed (Too many links))

After trying to update (no bootloader found) I get an Error (171): USB-connection-error

Hmmmm. What does that mean?

Edited May 12, 2010 by NOFX

[Guest jeckyllhavok]

Sorry guys, but this doesn't help me.

I can get into fastboot by holding the 'back' button and turning on. And I can navigate to the androidsdk/tools folder no problem. But when I here type fastboot rebootRUU I get an error.

Which file should be where on my harddrive, and on my SD-card?

The same question goes with the 'fastboot flash zip zipfilename'. Which zip is this, where should I put it, and where do I get it?

I just want to flash a stock ROM - and I can't by just running the .exe file. It says something about having 'too many images' or something. And it gets stuck while 'waiting for bootloader'. This runs to 100, and then gives me an error-message. Annoying!

Thanks guys :-)

For me it worked with the following:

take out sim an sdcard

get in fastboot

plug desire to your pc

wait some seconds

run the exe

[Guest NOFX]

Just tried removing both SD and SIM-card - but still no joy. Same error - gets stuck while waiting for Bootloader.

GRRRRRR - really annoying. But can't I use the fastboot commands - how, and with which files where?

[Guest jeckyllhavok]

Just tried removing both SD and SIM-card - but still no joy. Same error - gets stuck while waiting for Bootloader.

GRRRRRR - really annoying. But can't I use the fastboot commands - how, and with which files where?

Can you unzip the exe? I think there should be the images inside

[Guest NOFX]

Can you unzip the exe? I think there should be the images inside

Nope - I rename the .exe file to .zip - and I'm able to extract the boot.img file - but not the large .zip-file.

What am I doing wrong?

[Guest NOFX]

... and suppose I get it all unzipped - where should I place the files?

in the c:\androidsdk\tools folder?

[Guest jeckyllhavok]

... and suppose I get it all unzipped - where should I place the files?

in the c:\androidsdk\tools folder?

What OS are you using?

[Guest NOFX]

What OS are you using?

XP Professional...

[Guest Biliskner]

fastboot oem rtask eraseconfig seems to be a valid rtask command also indeed

same 3 dots then phone hanging.

Hmmm

Need differend fastboot program perhaps ?

If Paul can get hold of an Eng Bootloader, those commands would definitely work - it's all a question about whether we can get one, or are we stuck with no usb/recovery mode forever... :|

[Guest vastloper]

If Paul can get hold of an Eng Bootloader, those commands would definitely work - it's all a question about whether we can get one, or are we stuck with no usb/recovery mode forever... :|

I think we just need to find a way to make this rtask function work.

All the functions are allready implemented in the hboot but somehow the phone is crashing when trying to do them now.

I need to remove the battery to make phone work again after trying an implemented rtask command.

Even a batterytest command crashes the phone. Dont think that command is locked.