Hi, I've been a lurker here for quite some time but this is my first post.
I just tried to upgrade my Verizon XV6700 from AKU2.2 to AKU3.3 using the RUU I downloaded from the pcdphones.com web site (APA_Verizon_31430_314208_14300_WWE_Ship_2.exe). The RUU correctly identified my current radio, CE and Extended firmware versions but failed during the upgrade with error 116 (General Error). Doing a hard reset on the phone brings up the reset screen but after clearing the memory the phone just displays a blank screen. I can manually get into the bootloader (USB v2.05) and I tried re-running the AKU3.3 RUU again but now it says that my model ID is incorrect. I also tried running the AKU2.2 RUU (APA_VZW_20720_206_11000_WWE_Ship.exe) to get back to my original state but it doesn't work either (Error 101 Connection Error).
I downloaded Newbootloader_RUU and tried copying the 3 .nbf files for AKU3.3 into the directory and it seems to upgrade but it only runs for a short time (less than a minute) before saying the upgrade is complete and after doing a hard reset I still get a blank screen. I suspect that the ROM was not actually upgraded.
I downloaded mtty1.43 and I can get to a USB> prompt and have tried a few of the suggestions I found on the forums here but none have helped. I suspect that the model ID and possibly other information may have been corrupted by my first upgrade attempt. Here's some of the info I've recorded:
USB>info 1
2.05
USB>info 2
VZW__001 9ÿmïHTCE
USB>info 3
PA10A1ä TÝHTCE
USB>info 4
[email protected]ๆHTCE
USB>info 5
USB>info 6
T ÚÈÒHTCE
USB>info 7
HTC Integrated Re-Flash Utility for bootloader Version : 1.50a, APACHE HW Version : 2.05
Built at: Sep 18 2007 21:54:57
Copyright (c) 1998-2005 High Tech Computer Corporation
Turbo = 312 MHz, Run = 208 Mhz
Memory Frequency = 208 MHz
SDRAM Frequency = 104 MHz
Board ID is 2, Display is 0 (0=Ty,1=Sg)
USB>info 8
DOCInfoTableinitHW+
Binary0 Size: 0x100000
FAT0 Size: 0x4000000
FAT1 Size: 0xA00000
FAT2 Size: 0x2840000
All Size: 0x7340000
FAT0_ADDR=0x100000,FAT1_ADDR=0x4100000,FAT2_ADDR=0x4B00000
USB>info 9
USB>
Before I attempted the upgrade I recorded some information from the phone. I don't know how useful it might be but here it is:
Verizon XV6700 Startup Splash Screen:
H/W = 2
M = 12
U = 4
P SNAZ-40306
R 1.10.00
D 2.07.20 WWE
Device Information, Version:
ROM version 2.07.20 WWE
ROM date 02/24/06
Radio version 1.10.00
Protocol version SNAZ-40306
ExtROM version 2.07.200 WWE
Hardware version 0041
PRL version 51344
PRI version 1.14_002
Browser version MSIE 4.01
ESN 3674D2B4
Device Information, Hardware:
CPU Intel(R) PXA270
Speed 416 MHz
RAM size 64 MB
Flash size 128 MB
Flash chip type M-Systems
Data bus 32 bits
Storage size 39.59 MB
LCD 240 x 320 TFT
Colors 65536
Device Information, Identity:
Model No. PA10A1
Platform PocketPC
About, Version:
Microsoft Windows Mobile Version 5.0
OS 5.1.195 (Build 14928.2.2.0)
Processor: PXA270-416MHz
Memory: 49.23 MB
At this point I would welcome any suggestions. I've searched through the forums here but I haven't come up with anything else to try.
Thanks for your help.
Hello,
I was just wondering if this stupid Super CID prevent FOTA updates ?
I made capture of the update request to HTC servers:
As you can see Super CID is sent ...
POST /check-in/rws/and-app/update HTTP/1.1
Content-type: application/json
Content-Length: 459
Host: apu-chin.htc.com
Connection: Keep-Alive
User-Agent: AppUpdate-Checkin/2.3
{"timestamp":"-1","openSenseSdk":-1,"apiLevel":"10","checkIn":{"connectMedia":"W","mid":"PH06*****","build":{"serialNo":"SH19HVXXXXXX","mainVersion":"1.54.2","bootLoader":"1.07.0000","cl":"189894","radio":" 47.23.35.3033H_7.51.35.19","romVersion":"1.54.401.2 CL189894 release-keys","sku":"401","key":"R"},"clientVersion":"A2.3","cid":"11111111","checkType":"M","ip":"","mccMnc":"20810"},"locale":"fr_FR","imei":"XXXXXXXXXX","modelNum":"HTC ChaCha A810e"}
Answer from server:
HTTP/1.1 200 OK
Date: Sat, 31 Dec 2011 03:57:08 GMT
Transfer-Encoding: chunked
Content-Type: application/json;charset=UTF-8
X-Powered-By: Servlet/2.5 JSP/2.1
0031
{"overall":{"apkNumber":0,"interval":1209600000}}
0000
Other thing, I have a "cwkeys" file on the root of the file system containing a start address and followed by an array of 2 x 64 int64.
Any idea of what this file is ?
Yes it does. As all S-ON devices have a specific CID for each region/provider/brander, the superCID (111111) prevents OTA updates, as the server will ignore the request and respond with a "wrong CID" message.
Thanks for the answer.
I really wish I can get the original CID in the phone one day.
mike796 said:
Hello,
I was just wondering if this stupid Super CID prevent FOTA updates ?
I made capture of the update request to HTC servers:
As you can see Super CID is sent ...
POST /check-in/rws/and-app/update HTTP/1.1
Content-type: application/json
Content-Length: 459
Host: apu-chin.htc.com
Connection: Keep-Alive
User-Agent: AppUpdate-Checkin/2.3
{"timestamp":"-1","openSenseSdk":-1,"apiLevel":"10","checkIn":{"connectMedia":"W","mid":"PH06*****","build":{"serialNo":"SH19HVXXXXXX","mainVersion":"1.54.2","bootLoader":"1.07.0000","cl":"189894","radio":" 47.23.35.3033H_7.51.35.19","romVersion":"1.54.401.2 CL189894 release-keys","sku":"401","key":"R"},"clientVersion":"A2.3","cid":"11111111","checkType":"M","ip":"","mccMnc":"20810"},"locale":"fr_FR","imei":"XXXXXXXXXX","modelNum":"HTC ChaCha A810e"}
Answer from server:
HTTP/1.1 200 OK
Date: Sat, 31 Dec 2011 03:57:08 GMT
Transfer-Encoding: chunked
Content-Type: application/json;charset=UTF-8
X-Powered-By: Servlet/2.5 JSP/2.1
0031
{"overall":{"apkNumber":0,"interval":1209600000}}
0000
Other thing, I have a "cwkeys" file on the root of the file system containing a start address and followed by an array of 2 x 64 int64.
Any idea of what this file is ?
Click to expand...
Click to collapse
I wonder if its due to the same reason that I cannot update to latest version by OTA.
How did you capture the above data ?
UPDATE: I DONT KNOW IF CHANGING THE CABLE IS WHAT FINALLY DID IT, BUT IT IS DONE. THANK YOU ANYWAY. SORRY I POSTED SO SOON. I DONT USUALLY DO THAT. ALSO, IT WAS THE Z3X THAT FINALLY DID THE TRICK. ALSO THE FILE SIZE WAS 2.15K. ANY BODY ELSE THAT MAY WANT MORE DETAILS I WILL BE GLAD TO HELP.
Hey guys I really need some help and I am unable to find anything about it. I keep getting this error. Security damaged. I do the repair, it says its good then when I try and repair the imei it errors out. Here is the print out.
Platform: Samsung Android
Selected port: COM14
Selected model: SM-G925T
Please, press "OK" button on the phone to allow USB debugging..
Detected phone model: SM-G925T
Firmware compiled date: Sat Sep 19 16:29:03 KST 2015
PDA version: G925TUVU3DOI1
CSC version: G925TTMB3DOI1
SW version: G925TUVU3DOI1
Phone IMEI: Unknown
Phone SN: 00000000000
Android version: 5.1.1 (LMY47X)
Checking Root:
Phone is Rooted.
Reading security backup, please wait...
Backup saved as C:\Program Files (x86)\Octoplus\Octoplus_Samsung\BACKUP\Security-SM-G925T-Unknown14-10-2015_00-35-44-.asec file
Wiping EFS...
Phone will restart now. Please don't disconnect cable!
EFS wipe successfully
Searching for a phone. Please wait...
Detected phone model: SM-G925T
Firmware compiled date: Sat Sep 19 16:29:03 KST 2015
PDA version: G925TUVU3DOI1
CSC version: G925TTMB3DOI1
SW version: G925TUVU3DOI1
Phone IMEI: Unknown
Phone SN: 00000000000
Android version: 5.1.1 (LMY47X)
Repairing security
Security repair successfully
-----------------------------------------------------------------------------------
Platform: Samsung Android
Selected port: COM14
Selected model: SM-G925T
Selected file: C:\Users\John\Downloads\cert-sm-g925t_359146060661913_r58g50kgewk.cert
Detected phone model: SM-G925T
Firmware compiled date: Sat Sep 19 16:29:03 KST 2015
PDA version: G925TUVU3DOI1
CSC version: G925TTMB3DOI1
SW version: G925TUVU3DOI1
Phone IMEI: Unknown
Phone SN: 00000000000
Android version: 5.1.1 (LMY47X)
Checking Root:
Phone is Rooted.
Checking Certificate file...
Certificate file successfully checked
Phone connected successfully
Writing certificate...
Security damaged, please Repair Security and try again
Well I started comparing file size and the file that is in the phone is 2.15k, while the other g925t, as well as the other vairents of this cert are all 2.16k. Now when I flash with either octo or z3x I get the security damaged. I did find one file that was 2.15k and did get a successful flash, which gave me a ser #, but a defective imei. Please help.
Welcome to Octoplus/Octopus Box Samsung software version 2.0.4
-----------------------------------------------------------------------------------
To connect SM-G925T phone you have to perform the following steps:
1. Disconnect USB cable from phone.
2. Go to Menu->Settings->More->About Device.
3.Tap on "Build number" 7 times to enable developer options.
4. Go to Menu->Settings->More->Developer options.
5. Turn on "USB Debugging" option.
-----------------------------------------------------------------------------------
Platform: Samsung Android
Selected port: COM18
Selected model: SM-G925T
Selected file: C:\Users\John\Downloads\cert-sm-g920t-
357746060831994-r58g31myxyb.cert
Detected phone model: SM-G925T
Firmware compiled date: Sat Sep 19 16:29:03 KST 2015
PDA version: G925TUVU3DOI1
CSC version: G925TTMB3DOI1
SW version: G925TUVU3DOI1
Phone IMEI: Unknown
Phone SN: R58G50TKDNH
Android version: 5.1.1 (LMY47X)
Checking Root:
Phone is Rooted.
Checking Certificate file...
Certificate file successfully checked
Phone connected successfully
Writing certificate...
Security damaged, please Repair Security and try again
-----------------------------------------------------------------------------------
Platform: Samsung Android
Selected port: COM18
Selected model: SM-G925T
Selected file: C:\Users\John\Downloads\Cert-SM-G900-
358021058471446-RF1D93A24AK.cert
Detected phone model: SM-G925T
Firmware compiled date: Sat Sep 19 16:29:03 KST 2015
PDA version: G925TUVU3DOI1
CSC version: G925TTMB3DOI1
SW version: G925TUVU3DOI1
Phone IMEI: Unknown
Phone SN: R58G50TKDNH
Android version: 5.1.1 (LMY47X)
Checking Root:
Phone is Rooted.
Checking Certificate file...
Checking Certificate failed
Writing Certificate failed
-----------------------------------------------------------------------------------
Platform: Samsung Android
Selected port: COM18
Selected model: SM-G925T
Selected file: C:\Users\John\Downloads\cert-sm-g925f_
359521066036817_rf8g51vfezn.cert
Detected phone model: SM-G925T
Firmware compiled date: Sat Sep 19 16:29:03 KST 2015
PDA version: G925TUVU3DOI1
CSC version: G925TTMB3DOI1
SW version: G925TUVU3DOI1
Phone IMEI: Unknown
Phone SN: R58G50TKDNH
Android version: 5.1.1 (LMY47X)
Checking Root:
Phone is Rooted.
Checking Certificate file...
Certificate file successfully checked
Phone connected successfully
Writing certificate...
Security damaged, please Repair Security and try again
-----------------------------------------------------------------------------------
Platform: Samsung Android
Selected port: COM18
Selected model: SM-G925T
Detected phone model: SM-G925T
Firmware compiled date: Sat Sep 19 16:29:03 KST 2015
PDA version: G925TUVU3DOI1
CSC version: G925TTMB3DOI1
SW version: G925TUVU3DOI1
Phone IMEI: Unknown
Phone SN: R58G50TKDNH
Android version: 5.1.1 (LMY47X)
Checking Root:
Phone is Rooted.
Reading security backup, please wait...
Backup saved as C:\Program Files (x86)\Octoplus\Octoplus_Samsung
\BACKUP\Security-SM-G925T-Unknown14-10-2015_04-34-29-.asec
file
Wiping EFS...
Phone will restart now. Please don't disconnect cable!
EFS wipe successfully
Searching for a phone. Please wait...
Detected phone model: SM-G925T
Firmware compiled date: Sat Sep 19 16:29:03 KST 2015
PDA version: G925TUVU3DOI1
CSC version: G925TTMB3DOI1
SW version: G925TUVU3DOI1
Phone IMEI: Unknown
Phone SN: R58G50TKDNH
Android version: 5.1.1 (LMY47X)
Repairing security
Security repair successfully
-----------------------------------------------------------------------------------
Platform: Samsung Android
Selected port: COM18
Selected model: SM-G925T
Selected file: C:\Users\John\Desktop\cert-sm-g920f_35984506420518
_rf8g410tn3e.cert
Detected phone model: SM-G925T
Firmware compiled date: Sat Sep 19 16:29:03 KST 2015
PDA version: G925TUVU3DOI1
CSC version: G925TTMB3DOI1
SW version: G925TUVU3DOI1
Phone IMEI: Unknown
Phone SN: R58G50TKDNH
Android version: 5.1.1 (LMY47X)
Checking Root:
Phone is Rooted.
Checking Certificate file...
Certificate file successfully checked
Phone connected successfully
Writing certificate...
Security damaged, please Repair Security and try again
PLEASE PUT THIS IN THE RIGHT PLACE. I AM SO FLUSTERED BY THIS I may have PUT IT IN THE WRONG PLACE.
Hi,
Glad to know you got it fixed
Thread closed
process stop here
i tried 2 time but same result.
any solution?
device info:
dev[1] SH1BMVN04965
Mode: fastboot
Hardware: pico
Manufactory: HTC
MID: PJ0310000
Device Info
Security status: S-ON
Model Id: PJ0310000
Custom Id: VODAP034 (VODA-EU)
Serial number: SH1BMVN04965
Product: pico
IMEI: 357953049560823
Platform: HBOOT-7225A
Bootloader ver: 1.03.0000
Baseband ver: 1.11.82.17
Cpld verersion: None
Microp version: None
Main version: 1.29.161.3
Battery Status: good
Battery Volt: 4124mV
PartitionLayout: HTC
Commitno bl: 30d3dcb5
Hbootpreupdate: 12
i am waiting for reply from someone handsome..........
please solve my problem.
I have a problem with and unlock my galaxy N9250T with Z3X SamsungToolPRO_24.3 it gives me this message.
Operation: Read Codes
Selected model: SM-N920T
Software version: 24.3
Please wait, generating hash codes file, this can take few minutes... OK
Waiting ADB device...
Please, allow USB debugging on phone... OK
Reading phone info...
Model: SM-N920T
Android version: 5.1.1
Product code: SM-N920TZWATMB
Phone version: N920TUVU2COJ5
PDA version: N920TUVU2COJ5
CSC version: N920TTMB2COJ5
CSC country code: USA
CSC sales code: TMB
HW version: REV0.2
Phone S/N: RF8G903HHRY
Modem board: SHANNON333
RF cal date: 20150902
IMEI:
Checking Super user right... true
Initialization AT RIL...
Exception: Access violation at address 004074E0 in module 'SamsungToolPRO.exe'. Read of address 00000000
Done with Samsung Tool PRO v.24.3
I have the same damn problem...
Operation: Unlock SPRNT
Selected model: SM-N920P
Software version: 24.3
Waiting ADB device... OK
Reading phone info...
Model: SM-N920P
Android version: 6.0.1
Product code: Not Active
Phone version: N920PVPS3BQB1
PDA version: N920PVPS3BQB1
CSC version: N920PSPT3BQB1
CSC country code: USA
CSC sales code: SPR
HW version: N920P.04
Phone S/N: 00000000000
Modem board: MDM9635M
RF cal date: 2016.01.21
IMEI:
Initialization AT RIL...
Exception: Access violation at address 004074E0 in module 'SamsungToolPRO.exe'. Read of address 00000000
Done with Samsung Tool PRO v.24.3