Issues with USB connectivity etc. and root / A2SD

[Guest xTc is loVe]

Yeh I've got those tools. But can't get it to connect to my phone on COM ports. Anyone want them - I can upload.... (if it's not against forum rules)

It should not be against the rules. Just upload it in a zip file =)

What do you ALL think? Paul didnt test this before? o.O

[Guest Biliskner]

It should not be against the rules. Just upload it in a zip file =)

What do you ALL think? Paul didnt test this before? o.O

Ok, link here:

Qualcomm XP drivers I found + QPST + QXDM

http://www.mediafire.com/?zjdmufmimhw

[Guest pina]

Ok, link here:

Qualcomm XP drivers I found + QPST + QXDM

http://www.mediafire.com/?zjdmufmimhw

someone at XDA managed to run the recovery from the SD-card, without the need of a computer. Great news but I doubt it useful for us since the problem isn't ROM-related, but something much deeper into the heart of the system which is still locked for us

[Guest StuMcBill]

someone at XDA managed to run the recovery from the SD-card, without the need of a computer. Great news but I doubt it useful for us since the problem isn't ROM-related, but something much deeper into the heart of the system which is still locked for us

I haven't seen any posts on xda that say this, someone has got it dual booting so you can run another Rom off your SD card, but it won't run recovery atm.

[Guest pina]

I haven't seen any posts on xda that say this, someone has got it dual booting so you can run another Rom off your SD card, but it won't run recovery atm.

i thought it does, but it would be the first step for recovery from sd card

Edited May 28, 2010 by pina

[Guest xTc is loVe]

someone at XDA managed to run the recovery from the SD-card, without the need of a computer. Great news but I doubt it useful for us since the problem isn't ROM-related, but something much deeper into the heart of the system which is still locked for us

No i have to know how to use the tools :(

NO there is NO way to start the recovery from sdcard! There is in near future a option to boot from sdcard, but for now its not working!

[Guest Normola]

I've come across a new diagnostics screen (to me)

if you type *#*#3424#*#* (*#*#DIAG#*#*) you get a list of tests to run. Nothing much to help here, but I thought it was interesting.

[Guest kiokoman]

i was playing with some executable in a terminal inside /system/bin and found this:

# radiooptions

Usage: radiooptions [option] [extra_socket_args]

0 - RADIO_RESET

1 - RADIO_OFF

2 - UNSOL_NETWORK_STATE_CHANNEL

3 - QXDM_ENABLE

4 - QXDM_DISABLE

5 - RADIO_ON

6 - apn- SETUP_PDP apn

7 - DEACTIVE_PDP

8 - number - DIAL_CALL number

9 - ANSWER_CALL

10 - END_CALL

11 - rsp - FAKE_UNSOL

12 - command - UNIAT

Edited May 28, 2010 by kiokoman

[Guest Normola]

Could someone with a bricked phone run this:

adb shell "find | grep usb" > usb.txt

And supply the usb.txt file?

[Guest eViL D:]

From XDA:

Hi again!

I managed to grow some balls and for the sake of science booted into recovery (still in it), and just pushed the files and ran a shell to investigate.

Turns out my theory (of the files push overwritting some critical memory positions that contain bootloader configuration) is starting to make more sense!

The files are being pushed into / which is a "rootfs" device, meaning its essentially RAM memory we are writing into:

[B]rootfs on / type rootfs (rw)[/B]

tmpfs on /dev type tmpfs (rw,mode=755)

devpts on /dev/pts type devpts (rw,mode=600)

proc on /proc type proc (rw)

sysfs on /sys type sysfs (rw)

/dev/block/mtdblock4 on /cache type yaffs2 (rw,nodev,noatime,nodiratime)

/dev/block/mtdblock5 on /data type yaffs2 (rw,nodev,noatime,nodiratime)

My suggestion to devs is stop writing to / and push files into a data subdir and change the scripts and code to point to /data instead. Leave rootfs, alone and bricks should disappear.

I don't know if its possible to entirely run off /data without a single symlink (shared libraries come to mind), but I believe with some changes to scripts and source, it should be possible.

Plus, you only needed to push files once, then you could just run the recovery script anytime.

[Guest Normola]

From XDA:

Interesting. It opens up doors to some kind of 'super-root'. May even be possible to roll back bootloaders, etc...

[Guest ZiCoN]

Could someone with a bricked phone run this:

adb shell "find | grep usb" > usb.txt

And supply the usb.txt file?

Sorry... no adb..

[Guest Normola]

Sorry... no adb..

You'll find a copy in the directory with all the files you used for rooting. It'll be called adb-windows.exe or adb-linux depending on which platform you're on.

[Guest ZiCoN]

You'll find a copy in the directory with all the files you used for rooting. It'll be called adb-windows.exe or adb-linux depending on which platform you're on.

I mean... You can't adb a bricked desire... We've only got fastboot...

[Guest Normola]

I mean... You can't adb a bricked desire... We've only got fastboot...

Sorry. Wasn't thinking :(

You can run the find | grep usb from a terminal app and dump the output to an sdcard, but it's not *that* important.

[Guest ZiCoN]

Sorry. Wasn't thinking :(

You can run the find | grep usb from a terminal app and dump the output to an sdcard, but it's not *that* important.

I'll try :( > which lead to "permission denied" :o Don't have root.... But thinking about doing the testRUU.exe from bootRUU

Edited May 28, 2010 by ZiCoN

[Guest dimor]

i was playing with some executable in a terminal inside /system/bin and found this:

# radiooptions

Usage: radiooptions [option] [extra_socket_args]

0 - RADIO_RESET

1 - RADIO_OFF

2 - UNSOL_NETWORK_STATE_CHANNEL

3 - QXDM_ENABLE

4 - QXDM_DISABLE

5 - RADIO_ON

6 - apn- SETUP_PDP apn

7 - DEACTIVE_PDP

8 - number - DIAL_CALL number

9 - ANSWER_CALL

10 - END_CALL

11 - rsp - FAKE_UNSOL

12 - command - UNIAT

couldn't find anything useful in radiooptions... :(

[Guest jdouce]

last night I got the drivers for the three qualcomm devices, and after installing them on a x86 windows machine, they're listed as:

Qualcomm HS-USB Modem 9002

Qualcomm HS-USB Diagnostics 9002 (COMx)

Qualcomm HS-USB NMEA 9002 (COMx) (assuming for GPS)

Seeing that the they're COM ports, we might have some hope...

whoever did this ...

make a dial up connection using the qualcomm modem and your carrier AP settings... if you can get an active tether .... we know we got the usb working

dial up number is *99#

if you leave username and password blank ur phone should detect somehting is trying to use the built in settings

if not

try using ur carriers ap settings

Edited May 28, 2010 by jdouce

[Guest kiokoman]

static int bravo_phy_init_seq[] = { 0x0C, 0x31, 0x31, 0x32, 0x1D, 0x0D, 0x1D, 0x10, -1 };

static struct msm_hsusb_product bravo_usb_products[] = {

	{

		.product_id	= 0x0ff9,

		.functions	= 0x00000001, /* usb_mass_storage */

	},

	{

		.product_id	= 0x0c87,

		.functions	= 0x00000003, /* usb_mass_storage + adb */

	},

	{

		.product_id	= 0x0c03,

		.functions	= 0x00000101, /* modem + mass_storage */

	},

	{

		.product_id	= 0x0c04,

		.functions	= 0x00000103, /* modem + adb + mass_storage */

	},

	{

		.product_id	= 0x0c05,

		.functions	= 0x00000021, /* Projector + mass_storage */

	},

	{

		.product_id	= 0x0c06,

		.functions	= 0x00000023, /* Projector + adb + mass_storage */

	},

	{

		.product_id	= 0x0c07,

		.functions	= 0x0000000B, /* diag + adb + mass_storage */

	},

	{

		.product_id	= 0x0c08,

		.functions	= 0x00000009, /* diag + mass_storage */

	},

	{

		.product_id	= 0x0c88,

		.functions	= 0x0000010B, /* adb + mass_storage + diag + modem */

	},

	{

		.product_id	= 0x0c89,

		.functions	= 0x00000019, /* serial + diag + mass_storage */

	},

	{

		.product_id	= 0x0c8a,

		.functions	= 0x0000001B, /* serial + diag + adb + mass_storage */

	},

	{

		.product_id	= 0x0c93,

		.functions	= 0x00000080, /* mtp */

	},

	{

		.product_id	= 0x0FFE,

		.functions	= 0x00000004, /* internet sharing */

	},

};

check with lsusb on linux and compare

example

#lsusb

Bus 002 Device 003: ID 0bb4:0c87 High Tech Computer Corp.

in this example my htc is set to /* usb_mass_storage + adb */

Edited May 28, 2010 by kiokoman

[Guest xTc is loVe]

Maybe its dumb but i find with Root Explorer in /data/data/recovery there is a log file and i JUST THINK i found some intresting lines? (I am bricked :/)

I mark the lines

Starting recovery on Fri May 28 10:29:16 2010

can't open /dev/tty0: No such file or directory

framebuffer: fd 3 (480 x 800)

Fixing execute permissions for /cache

E:Can't open /cache/recovery/command

I:Set boot command "boot-recovery"

Command: "/sbin/recovery"

ro.secure=0

ro.allow.mock.location=0

ro.debuggable=1

persist.service.adb.enable=1

ro.ril.ecc.VIRGIN-UK=112,999,911

ro.ril.ecc.HTC-ELL=92,93,94

ro.ril.ecc.HTC-WWE=999,999

ro.ril.hsdpa.category=8

ro.ril.hsupa.category=5

ro.ril.hsxpa=2

ro.ril.disable.fd.plmn.prefix=23402,23410,23411

ro.ril.enable.sdr=0

ro.ril.enable.a52.HTC-ITA=1

ro.ril.enable.a53.HTC-ITA=1

ro.ril.enable.a52.VODA-Portugal=0

ro.ril.enable.a53.VODA-Portugal=1

ro.com.google.clientidbase=android-htc

ro.build.id=ERE27

ro.build.display.id=htc_bravo-userdebug 2.1-update1 ERE27 eng.root.20100429.001945 test-keys

ro.build.version.incremental=172503

ro.build.version.sdk=7

ro.build.version.codename=REL

ro.build.version.release=2.1-update1

ro.build.date=Thu Apr 29 00:20:34 CST 2010

ro.build.date.utc=1272471634

ro.build.type=userdebug

ro.build.user=root

ro.build.host=Oven-X05

ro.build.tags=test-keys

ro.product.model=HTC Desire

ro.product.brand=htc_wwe

ro.product.name=htc_bravo

ro.product.device=bravo

ro.product.board=bravo

ro.product.cpu.abi=armeabi-v7a

ro.product.cpu.abi2=armeabi

ro.product.manufacturer=HTC

ro.product.locale.language=hdpi

ro.product.locale.region=

ro.wifi.channels=

ro.board.platform=qsd8k

ro.build.product=bravo

ro.build.description=1.21.405.1 CL172503 test-keys

ro.build.changelist=172503

ro.product.ua=

ro.build.fingerprint=htc_wwe/htc_bravo/bravo/bravo:2.1-update1/ERE27/172503:userdebug/test-keys

ro.product.version=1.21.405.1

keyguard.no_require_sim=1

ro.sf.lcd_density=240

rild.libpath=/system/lib/libhtc_ril.so

ro.ril.enable.dtm=1

ro.ril.gprsclass=12

ro.telephony.default_network=0

wifi.interface=eth0

wifi.supplicant_scan_interval=15

ro.opengles.version=131072

dalvik.vm.heapsize=24m

ro.ril.def.agps.mode=2

ro.phone_storage=0

ro.ril.disable.power.collapse=1

ro.ril.avoid.pdp.overlap=1

ro.ril.enable.prl.recognition=1

ro.media.enc.file.format=3gp,mp4

ro.media.enc.vid.codec=m4v,h263

ro.media.enc.vid.h263.width=176,1280

ro.media.enc.vid.h263.height=144,720

ro.media.enc.vid.h263.bps=64000,2000000

ro.media.enc.vid.h263.fps=1,30

ro.media.enc.vid.m4v.width=176,1280

ro.media.enc.vid.m4v.height=144,720

ro.media.enc.vid.m4v.bps=64000,2000000

ro.media.enc.vid.m4v.fps=1,30

ro.media.dec.jpeg.memcap=20000000

ro.htc.checkin.url=http://andchin.htc.com/android/checkin

ro.htc.checkin.crashurl=http://andchin.htc.com/android/crash

ro.bt.chipset=Broadcom BCM4329-B1

ro.bt.version=Bluetooth 2.1 + EDR

ro.bt.stack=Broadcom BTL-A

ro.bt.stack.version=2.0.47.005

ro.bt.profiles=4270339

ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html

ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html

ro.com.google.networklocation=1

ro.setupwizard.mode=DISABLED

ro.config.ringtone=Innovation.mp3

ro.config.notification_sound=Color.mp3

ro.config.alarm_alert=Light.mp3

ro.config.cal_notification=Vector.mp3

ro.config.msg_notification=Ascend.mp3

ro.com.google.gmsversion=2.1_r3

media.a1026.nsForVoiceRec=0

htc.audio.alt.enable=0

htc.audio.hac.enable=0

dalvik.vm.dexopt-flags=m=y

net.bt.name=Android

net.change=net.bt.name

ro.config.sync=yes

dalvik.vm.stack-trace-file=/data/anr/traces.txt

ro.factorytest=0

ro.serialno=HT04APL00392

ro.bootmode=recovery

ro.baseband=4.06.00.02_2

ro.carrier=O2-DE

ro.bootloader=0.80.0000

ro.hardware=bravo

ro.revision=129

ro.cid=O2___102

init.svc.choice_fn=stopped

init.svc.adbd=running

init.svc.recovery=running

I:Set boot command ""

I:Unlink

I am in Recovery if i understand it right and if i understand right ADB is enabled !?

Edited May 28, 2010 by xTc is loVe

[Guest kiokoman]

adb is running but without a working usb is of no use

i don't have /data/data/recovery in my unbricked desire

what else there is inside?

[Guest dimor]

adb is running but without a working usb is of no use

i don't have /data/data/recovery in my unbricked desire

what else there is inside?

i got:

OMADM

HTCFOTA

log

in /data/data/recovery

[Guest kiokoman]

http://en.wikipedia.org/wiki/OMA_Device_Management

HTCFOTA = htc firmware on the air

can you upload the files ?

Edited May 28, 2010 by kiokoman

[Guest xTc is loVe]

http://en.wikipedia.org/wiki/OMA_Device_Management

HTCFOTA = htc firmware on the air

can you upload the files ?

In mine only the log file appears .... i run recovery again to see whats happen !

Is a full "backup" or so from a bricked desire good for helping us? :( If yes tell me waht to do ;-)

Edited May 28, 2010 by xTc is loVe

[Guest dimor]

http://en.wikipedia.org/wiki/OMA_Device_Management

HTCFOTA = htc firmware on the air

can you upload the files ?

i don't really have a way to copy these files... i get permission denied for "cp"