Database Develop

HTC Shift Debug Tools and SD access

Dear All,
Just installed the 1.29 which enables voice calling (but no mic).
I noticed that there's a full suite of debug tools on this rom, and especially interesting are :
QXdmSDlog.exe - seems to be able to write to SD ! (I coudn;t get it to work yet)
Debugtools 3.2 (one can set the radio flags in here, and also enable USB bridging it seems
GPSRouter.exe seems to be able to route GPS info to the Vista part (unconfirmed)
I wonder if there's anyone who has done some testing with these three debugtools, and what success they have.
I set the radio flags to 4xx as described, but the SD tool won't log to SD yet.
There's a difference in DebugTools, one has to access them from the SnapVue settings icon, not from the start menu...

Please dump the tools and attach on this thread
Hi,
Appreciate if you can copy the tools or the folder (HTC Debug folder) and zip and attach it here on this thread

lucid said:
Dear All,
Just installed the 1.29 which enables voice calling (but no mic).
I noticed that there's a full suite of debug tools on this rom, and especially interesting are :
QXdmSDlog.exe - seems to be able to write to SD ! (I coudn;t get it to work yet)
Debugtools 3.2 (one can set the radio flags in here, and also enable USB bridging it seems
GPSRouter.exe seems to be able to route GPS info to the Vista part (unconfirmed)
I wonder if there's anyone who has done some testing with these three debugtools, and what success they have.
I set the radio flags to 4xx as described, but the SD tool won't log to SD yet.
There's a difference in DebugTools, one has to access them from the SnapVue settings icon, not from the start menu...
Click to expand...
Click to collapse
I have tested with BTRouter and BTTest and found by disabling the port you could write to COM8 and once you disable it USB port would go away.
If you could provide me the tools you are talking about and the ROM, I can take a look into that.
Note: I can say one thing, since the SD is not activated, probably SD tool wont log to SD. I may be wrong too, that tool might be activating it too.
Thanks
Ram

Cannot enable Wifi driver , not a network configuration issue

Since I applied the froyo update from Paul's site wifi was working fine for 36 hours.
After a crash caused by copying files on my sdcard I rebooted the phone several times to recover it (another story).
Then wifi stopped working, by "stopped working" I mean the driver won't even load, giving me a warning in logcat, some timeouts in dhd_module_init and "Error" in the control panel.
It has nothing to do with my router configuration because I cannot even enable the wifi to scan for some ssid so it's not a "false alarm" issue...
I tried to flash Stock rom and radio, flash superboot FRF50, the last cyanogen, wipe a few thousand times between all of this but nothing seems to give life back to my wifi chip... I tried flashing InsectRaven and cyanogen .34 kernels with no results...
I can't stop thinking it is hardware related but why ??!! There was no shock, no fall, no EMP from a nuke in the vicinity, everything was smooth when I got back from work and bam !
Is there some options to pass to the driver when I insmod to "reset" the chip in a healthy state ?
Can I somehow compile a debug build giving more informations on my hardware when it is crashing like **** ?
I don't know where to look anymore ... and I'd like some proof thats it is indeed fried...
Here are logs from various sources when I enable wifi in the settings (or insmod /system/lib/modules/bcm4239.ko)
From dmesg : http://pastebin.com/uaRM4EyK
From logcat :
Code:
E/WifiService( 83): Failed to load Wi-Fi driver.
From insmod /system/lib/modules/bcm4239.ko :
Code:
# insmod bcm4329.ko
insmod: init_module 'bcm4329.ko' failed (Invalid argument)
I2C errors in dmesg : http://pastebin.com/ehB7RtN7

Another question , has someone successfully compiled "strace" and "modinfo" to run on android ?
I guess it will be helpful to debug my issue.

Hi,
I'm having a similar issue, thought on another device. Did you find a fix for this?
Thx
Raph

[Q] DS7 stuck on setup wizard

Hi,
I'm using a TMobile 4G DS7 in Europe (no SIM card); last week as I restarted it (battery was very low) I started receiving error messages (Email app has stopped unexpectedly, then Gmail and you name it...) and was sent back to the setup wizard.The DS7 was running on the original setup, no OS upgrade had been done.
I tried a factory reboot which didn't change anything.
I started reading this forum and tried the 3 options which are described
1- updating with a 306 .pkg file on the SDCard
the following takes place
Booting kernel recovery Image
Blue text
Finding update package
Opening update package
Verifying update package
Install modem error . System will upgrade again. (90% bar)
Screen turns black then reboots
and back to square one !
Trying other packages results in an error message, process stops at verifying update package .
2- Fastboot mode
I downloaded and installed the drivers
I put DS7 in fastboot mode and get the fwg :
Username : cmbuild hostname : ***** buildnumber : ******
Build on Mar 11 2011 17:19:36
Starting Fastboot USB download protocol
On PC I go to the directory where the fastboot.exe is stored .
When I type < Fastboot devices>
I get <? fastboot> which seems to indicate that no device is identified ( under Config panel in Windows I can see that the device is recognized as an Android device) ....
3- NVFlash mode
I put the DS7 in NVFlash mode connected it to my PC . The config panel showed there was a prob (yellow triangle). I installed the driver .... and now the device does not even appear when I go Config panel / System
So I get nowhere under any of the 3 options ; can I just throw away my DS7 or is there still some hope ? things I haven't done correctly ?
Any help suggestion would be most appreciated.
Thx in advance to whoever wil read this thread.
FG

the ???? Device under fastboot is normal
ONce you put the device into NVFlash mode and you install the drivers, open up Device Manager and look under the USB section, you should see something about Nvidia recovery mode.

giveen said:
the ???? Device under fastboot is normal
ONce you put the device into NVFlash mode and you install the drivers, open up Device Manager and look under the USB section, you should see something about Nvidia recovery mode.
Click to expand...
Click to collapse
You're right. I flashed everything went all right but after "pinbooting" no change still stuck.

FGMareil said:
You're right. I flashed everything went all right but after "pinbooting" no change still stuck.
Click to expand...
Click to collapse
You might be in read-only mode, which can only be fixed by Dell

giveen said:
You might be in read-only mode, which can only be fixed by Dell
Click to expand...
Click to collapse
The OP stated that the battery was low which is one reason some have claimed to cause this.

Is my Lumia 1320 beyond help?

Hi there,
I have a nearly three year old Lumia 1320 that I have as my daily driver, and have been using the Windows 10 DP since early days. Recently, the W10 release it had was the one that stuffed up SD card storage (and was getting random reboots) so I decided to go back to 8.1 and updated it to the Update 2 release.
So far so good. However, the newest W10 release came out so I decided to give it another go (especially as SD card issue resolved) so ran the appropriate software, it downloaded, and applied the image, then it failed. It said to try again, so I did and then started saying things like I didn't have enough storage. The Storage app wouldn't load, nor would Store, Phone, Messages etc. so tried the recovery tool to reflash it back to stock 8.1
This tool failed during the process and said it couldn't flash the device.
Tried various reset techniques and they all failed to get a good result. The symptom was to get the red NOKIA screen for a split second then it loaded the OS.
Now I'm getting concerned and bring out the big guns! Read the XDA tutorial on Windows Phone flashing, downloaded the tools, installed the unsigned driver, downloaded the appropriate image for my phone and went to flash.
Got to 2% and failed:
Sorry! Your device could not be flashed with the image you selected.
Please correct the following error and try again:
Failed to flash with device error { 0xd, 0x0, 0x0, 0x2, 0x0, 0x0 } : Status: 0x80000008
I looked up this 0xd code on the MS site and the error is this:
0xD While applying the image to disk, a block write operation failed.
So now to the ultimate question - does this mean my phone has a hardware error that prevents flashing, or can anyone suggest a workaround to get past this?
The model is RM-994 - the image is 059V5K2 (Australia/NZ Vodafone)
PC I am flashing with is a Core i7 2600, 8GB, Windows 10 Pro x64 with latest November update.
Any advice much appreciated.
Darren

No one?
Really no replies? Anyone on here know more low-level details or tests I can perform?
Even if someone confirms my suspicions that there is a hardware fault that simply can't be overcome, I can move on.
The phone is still running, alarms work, lock screen works (even updates Bing photo), but no Store, Storage Sense, Messages, plus many others and if I delete apps listed as unavailable, or even current apps, such as Tweetium, they disappear and return after a reboot of the device.
I have even tried remote wipe from the web and the device reboots and goes straight back to where it was.
Regards
Darren

Question Soft bricked X90 Pro Plus

well my x90 pro plus deep uncharged, wouldn't power one anymore before I connected it for like 3-4 minutes - and once powered one it was soft bricked - it would boot to the screen showing vivo symbol and get stuck there. So first I thought let's try to update/reinstall the system (in order to not lose data).
can access now only fastboot, recovery and wifi update page (via recovery). Phone will not boot past the vivo message - likely also not fully load system partitition.
-- Wiping Data
Error: logwrapper : Cannot log to file /dev/fscklogs/log
Error: recovery: Open failed: /metadata/ota: No such file or diretory
Formating /data....
Error: logwrapper : Cannot log to file /dev/fscklogs/log
Error: logwrapper : Cannot log to file /dev/fscklogs/log
Formating /metdata...
Data wipe compelte.
Can wipe cache.
Can get to update menu - however on entering the wifi password it starts searching for updates - then goes to another screen saying retry.
Bootloader is locked.
System file integrity check fails with:
Now check beings, please wait...
use sha256 check:
--mount System fs_type_invalid
System check success
Local update isn't possible as I have no local system.zip in root.
How do I even contact support? I have no invoice as I bouth this via an importer that doesn't pass on invoices. I remember I once checked warranty and as on first use I selected Austria - it told me warranty is in Austria (not that X90PP is even sold there). But I don't know where to login to my vivo account without having the phone. I will be in Austria in a month or so - right now in a country where Vivo isn't sold at all.
Guess I should take a hammer and smash this crap phone.
The first time I went into software updates it actually started downloading the full OTA - it started upgrading but then crashed 2/3 thorugh. Tried the same thing again - same problem. Then went into hard reset - which failed. And since then it's as above ant not even downloading software anymore.
Now not sure what happened there. Maybe it bricked while failing of the software update?
Also it doesn't shut down anymore with power cable connected (without it does), it will just crash and run out of battery deep discharging while being connected and getting crazy hot.
If switched off and connecting a charging cable - power spark symbol will pop up (but not charge!) then pull power cable and the symbol stays there until battery is fully depleted with phone running hot.