I've been dealing with what appears to be constant modem hangs which bring the data throughput to 0 and is often resolved with toggling airplane mode. I often have major issues with Verizon and their throttling (deprioritization) but this is a different animal. I'm kind of at the end of my rope, just waiting for July and hoping it fixes it.
I've tried flashing May's image but it won't boot and just sits on the G logo and I have to flash back to June. I also tried doing a network settings reset and that did bubkiss other than to make more work for me.
Has anybody else run into this issue, and have a solution, or can at least commiserate?
It truly is unusable.
~ $ ping google.com
PING google.com (216.58.193.206) 56(84) bytes of data.
64 bytes from lax02s23-in-f14.1e100.net (216.58.193.206): icmp_seq=2 ttl=114 time=552 ms
64 bytes from lax02s23-in-f14.1e100.net (216.58.193.206): icmp_seq=4 ttl=114 time=811 ms
64 bytes from lax02s23-in-f14.1e100.net (216.58.193.206): icmp_seq=5 ttl=114 time=653 ms
64 bytes from lax02s23-in-f14.1e100.net (216.58.193.206): icmp_seq=8 ttl=114 time=869 ms
64 bytes from lax02s23-in-f14.1e100.net (216.58.193.206): icmp_seq=9 ttl=114 time=393 ms
64 bytes from lax02s23-in-f14.1e100.net (216.58.193.206): icmp_seq=10 ttl=114 time=587 ms
64 bytes from lax02s23-in-f14.1e100.net (216.58.193.206): icmp_seq=17 ttl=114 time=1104 ms
64 bytes from lax02s23-in-f14.1e100.net (216.58.193.206): icmp_seq=21 ttl=114 time=922 ms
64 bytes from lax02s23-in-f14.1e100.net (216.58.193.206): icmp_seq=22 ttl=114 time=840 ms
64 bytes from lax02s23-in-f14.1e100.net (216.58.193.206): icmp_seq=24 ttl=114 time=1229 ms
64 bytes from lax02s23-in-f14.1e100.net (216.58.193.206): icmp_seq=28 ttl=114 time=961 ms
--- google.com ping statistics ---
31 packets transmitted, 11 received, 64% packet loss, time 30523ms
rtt min/avg/max/mdev = 393.309/811.524/1229.624/236.701 ms, pipe 2
Tb0n3 said:
I've been dealing with what appears to be constant modem hangs which bring the data throughput to 0 and is often resolved with toggling airplane mode. I often have major issues with Verizon and their throttling (deprioritization) but this is a different animal. I'm kind of at the end of my rope, just waiting for July and hoping it fixes it.
I've tried flashing May's image but it won't boot and just sits on the G logo and I have to flash back to June. I also tried doing a network settings reset and that did bubkiss other than to make more work for me.
Has anybody else run into this issue, and have a solution, or can at least commiserate?
Click to expand...
Click to collapse
Flashing just the radio.img from May should work. Don't quote me, though.
andybones said:
Flashing just the radio.img from May should work. Don't quote me, though.
Click to expand...
Click to collapse
I actually did try that it became extremely unstable and would keep killing the data connection every 10 seconds.
I thought I was the only one who had bad service on Verizon all of a sudden, I'm on a12 beta 3 and it is a little better but since June update Ive seen my signal turn to complete crap, I even opened a Google Fi account and it was the same
Related
People have been reporting problems with corruption and losing files on memory cards, particularly 2GB ones.
I am having the same problem with a PQI 2GB bought from Fry's(PLU# 5044075 and P/N: AE62-2030R01F4) in Houston, TX.
When I try to download something from an FTP Client to the storage card, it fails and when I leave stuff on it, it becomes corrupt and stuff disappears. Also, when transferring files over FTP, it moves at about 5-8 KBps.
I took my roommate's 64MB PQI from his Sidekick III and it worked like a charm. It was as follows.
1 Head
1 Cylinder
Type: FAT12
Sector: 512 Bytes
Cluster Size: 16 KB
BackupFAT: Yes
I used Pocket Mechanic(amazing interface) and Resco which is great and clean as well! Thank you for the recommendation. I scanned my card for bad sectors and they were all good.
This morning I used my co-workers SanDisk 1GB card and downloaded files from my FTP at 22KBps over EDGE which blew my mind. Furthermore, they weren't corrupted. His file system was FAT32.
My conclusion is that it isn't the formatting options, but the PQI cards and the old motto of "You get what you pay for". I am going to have to break down and buy another card which I really didn't want to do, but it's obvious that SanDisk clearly holds it's weight in these devices.
Thanks to everyone who made recommendations and turned me on to some great apps in the process. I'll update this when I get my new card and let you guys know how it went. Thanks again for being a great community!
EDIT: Could people without problems with a 2GB Post the following info to help those trying to buy a card?
Brand:
Part No:
Format Method
Type:
Sector:
Cluster Size:
Flash memory doesn't have heads or cylinders
I know, but the stat was there so I included it in case someone got a different value reported back to them...
soopahfly said:
Flash memory doesn't have heads or cylinders
Click to expand...
Click to collapse
Correct, but there may still be logical heads and cylinders for backwords compatibility with some OSes or software.
I dont know about the case with SD cards, but CF cards can be directly connected to an IDE bus and emulate an HD.
Since this afternoon my phone will not connect to either GPRS and/or 3G anymore.. it will just keep trying and after 2 tries it gives me an error that the connection has failed...
Does anyone know whats going on?
i tried soft-resetting and reconfigure my provider settings with the htc provder wizard..
help??
I cant enable WLAN either..!! chip fried? i drove my car today and it was VERY hot (no airco)
changing the radio to 1.65.20.29 also didnt work..
How hot are we talking? My tilt has been in 90d Fahrenheit cars without ill effects.
Did you try a hard reset?
just tried a hard reset and it still doesnt work! omg..
i think around 115F / 45C
*edit; it seems that my provider has some problems. lets hope it will be over,
Wifi is fixed with an other commanager..
Code:
Cmd>task 32
Cmd>info 2
HTCS00000000jR*¥HTCE
Cmd>info 8
--- 2K bytes sector version ---
DEVICE NAME=samsung_k9k2g08
DEVICE ID=0xAA
DEVICE MAKER ID=0xEC
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x800
BLOCK PAGE=0x40
Checking block information
BLOCK 0 (0x0) is reversed block
BLOCK 1 (0x1) is reversed block
BLOCK 2 (0x2) is reversed block
BLOCK 8 (0x8) is reversed block
BLOCK 9 (0x9) is reversed block
BLOCK 10 (0xA) is reversed block
BLOCK 11 (0xB) is reversed block
Partition[0], type=0x20, start=0x2, total=0x63E
Partition[1], type=0x23, start=0x640, total=0x740
Partition[2], type=0x25, start=0xD80, total=0x7DC0
Partition[3], type=0x4, start=0x8B40, total=0x12780
CE Total Length(with sector info) = 0x45E5A00
CE CheckSum Length(without sector info) = 0x45A0000
Cmd>getdevinfo
GetDevInfo: Get backup CID
HTCSKAIS1300HTCE
Cmd>
Who's your provider ?
My guess would be Vodaphone
i feel very stupid, it was my provider.. well it was strange because my phone acted weird at the same as well, AND because my commanager was broken wlan couldnt be activated via commanager, so i kinda freaked out i guess..
problem solved!
Hello! Today my Kaiser (a T-Mobile Vario III) decided to brick. It ran out of power, I charged it up & back on, some texts were missing, performance was very sluggish, restarted it... & now it doesn't get part the T-Mobile startup screen, i.e. Windows Mobile doesn't boot.
Searching around draws me to only one place - here , where people modify their ROMS and troubleshoot similar problems. EXCEPT I haven't modded a ROM at all; this is a vanilla phone that just locks up as if the ROM has bricked.
T-Mobile support just tell me to upgrade Windows via ActiveSync, which of course I can't do as it won't boot. :headdesk:
I've used mtty.exe to try and READ data from the phone, & in the process read the FAQ, learnt about the bootloader, etc. I have not made ANY writes to the phone.
I suspect the phone is nearly physically full, somehow leading to filesystem corruption.
I have NOT yet tried a hard reset, as some pictures/texts from today would be lost, & I'd like to avoid that & somehow recover the data.
So:
Is there a way to copy filedata (photos, etc.) from the phone via the bootloader/mtty? I doubt it from my searches, but it's worth asking.
Is there a way to check/fix phone contents WITHOUT wiping it with another ROM?
Is there anyone who can help with the output from mtty.exe below? (Phone locks up at "UserStorageSIPreload" )
Or will I just have to suck it up & do a hard reset?
Code:
Cmd>info 8
--- 2K bytes sector version ---
DEVICE NAME=samsung_k9k2g08
DEVICE ID=0xAA
DEVICE MAKER ID=0xEC
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x800
BLOCK PAGE=0x40
Checking block information
BLOCK 0 (0x0) is reversed block
BLOCK 1 (0x1) is reversed block
BLOCK 8 (0x8) is reversed block
BLOCK 10 (0xA) is reversed block
BLOCK 11 (0xB) is reversed block
BLOCK 887 (0x377) is bad block
BLOCK 1189 (0x4A5) is bad block
Partition[0], type=0x20, start=0x2, total=0x63E
Partition[1], type=0x23, start=0x640, total=0x700
Partition[2], type=0x25, start=0xD40, total=0x8800
Partition[3], type=0x4, start=0x9540, total=0x11D80
CE Total Length(with sector info) = 0x4AEAA00
CE CheckSum Length(without sector info) = 0x4AA0000
Cmd>boot
InitDisplay: Display_Chip=1
No card inserted
OSSIReadBack ++
Read SI data from flash success
tail signature match
Checksum match
UserStorageSIPreload ++
Thanks, thanks, thanks in advance!
1-try removing ur battery for 10min then placing it back in.
2-If u have data on ur SD then its shouldnt matter if u hard reset.
3-final option, Hard Reset or upgrade ur rom.
Or be patient, maybe someone has better suggestions than me and will chime in for sure
GL
I tried those options, & a thorough search & trying out of the various tools - it didn't seem possible via the bootloader. It was just my texts & some pictures held on there which I deliberately didn't back up, & I'm fighting my urge to semi-obsessively document my life, so I let them go & hard-reset... thanks anyway guys.
Hey all!
I'm curious about what causes lots of loss in disk drives like when you buy a 320 Gb HDD, it's only 292 Gb. I knew it some time ago but forgot it Tried to google it but had hard time finding the right query, endind up wrong results. Thanks in advance.
http://en.wikipedia.org/wiki/Gigabyte
"Although most manufacturers of hard disk drives and flash-memory disk devices define 1 gigabyte as 1000000000bytes, software like Microsoft Windows reports size in gigabytes by dividing the total capacity in bytes by 1073741824, while still reporting the result with the symbol "GB". This practice is a cause of confusion, as a hard disk with an advertised capacity of, for example, "400 GB" (meaning 400000000000bytes) might be reported by the operating system as only "372 GB"
I bought a knockoff iPod off eBay a few weeks ago and it came in today. I immediately jumped online to try and find a program that can check the validity of the storage space, to make sure it's truly 16GB as it says it is. I found H2testw, which seems to be the most suggested program.
Anyway, 2 hours later, the test if finally done. I'm not exactly sure how to understand the results and would love if someone could explain it a bit to me. I've never used it, and I'm sure someone on here likely has.
I would greatly appreciate it.
(at first glance it appears it's fake or faulty and is only 7GB, not 16GB as stated but again, I don't exactly know how to understand it)
The media is likely to be defective.
7.6 GByte OK (16003088 sectors)
8.3 GByte DATA LOST (17430512 sectors)
Details:8.3 GByte overwritten (17430512 sectors)
0 KByte slightly changed (< 8 bit/sector, 0 sectors)
0 KByte corrupted (0 sectors)
8 KByte aliased memory (16 sectors)
First error at offset: 0x00000001e8602000
Expected: 0x00000001e8602000
Found: 0x00000001e8600000
H2testw version 1.3
Writing speed: 5.26 MByte/s
Reading speed: 6.73 MByte/s
H2testw v1.4
Click to expand...
Click to collapse
Yeah, I think it means 7.6GB of actual storage with 8.3GB of corrupt storage meaning the actual capacity is only 7.6GB...at least from what I read from the description on the website for the program I used.
Sample Output For A Fake 64 GB Drive
The media is likely to be defective.
3.8 GByte OK (8084847 sectors)
58.6 GByte DATA LOST (122921617 sectors)
Details:710.5 KByte overwritten (1421 sectors)
7.6 MByte slightly changed (< 8 bit/sector, 15630 sectors)
58.6 byte corrupted (122904566 sectors)
710.5 KByte aliased memory (1421 sectors)
First error at offset: 0x000000003cef8470
Expected: 0xeb7ac43a237c5170
Found: 0xeb7a843a237c5170
H2testw version 1.3
Writing speed: 9.24 MByte/s
Reading speed: 10.8 MByte/s
H2testw v1.4
Click to expand...
Click to collapse
Would still like some input from anyone who might know better then myself.