Database Info

XV6700 upgrade from AKU2.2 to AKU3.3 failed

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.

[GUIDE] Radio S-OFF, SuperCID, SimUnlock + Root

Hi ppl here is a guide on how to gain radio S-OFF, Super CID , SimUnlock
What You Need
-- This File
-- If on OSX / Linux ADB binary (they are not included in the .zip)
-------------------------------------------------------------------------------------------
Bits in red Are Only for people who dont already have perm root
Bits in Blue are for everyone
-------------------------------------------------------------------------------------------
1) Extract the zip file (to your adb directory if on mac / linux)
2) Open a command prompt / shell and navigate to your where you extracted the files
3) run
adb install visionaryplus-r14.apk
Click to expand...
Click to collapse
4) open visionary on phone
5) tick Run visionary.sh after root" and "set system r/w after root"
6) Now click "temproot now" and wait 30 - 60 sec
7) run line per line
adb push gfree /data/local
adb shell
su
cd /data/local
chmod 777 gfree
./gfree
sync
reboot
Click to expand...
Click to collapse
Now We Are Radio S-OFF and SuperCID + SimUnlocked
8) If you where not already perma rooted run visionary Temp root, then perm root.
[To Check]
1) run
adb reboot bootloader
Click to expand...
Click to collapse
ON SHIP HBOOT
Just check the top line if you see
SHIP S-OFF (it worked )
SHIP S-ON (it didnt )
ON ENG HBOOT
2) tap bootloder option
3) use vol down to get to system info and tap
4) check CID for CID-11111111 (if you have this all is done 100%)
5) reboot
[PROBLEMS]
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IF THIS DOESNT WORK AND U GET
***WARNING***: Did not find brq filter.
Click to expand...
Click to collapse
Get either a stock kernel CM/SENSE or my buzz-1.0.7 as its confirmed working on those
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
[FAQ]
Does this install the ENG hboot ?
No as that is no longer required, still an opition if you want to gain the extra functions
Click to expand...
Click to collapse
How can i install custom recovery for roms without ENG hboot ?
Just get rom manger from marked and install with that
Click to expand...
Click to collapse
What does all this mean ?
Radio S-OFF = we have s-off regardless or hboot we are using so if you update the hboot s-off will stay
Super CID = Allow to install RRU's from ANYONE
Click to expand...
Click to collapse
[CREDITS]
Paul O'Brien for visionary
scotty2 and others who found the method to patch P7
everyone else who has worked on the G2 root and wpthis

hey there, thanks for the guide but something didnt work while running ./gfree
Code:
./gfree
Section header entry size: 40
Number of section headers: 44
Total section header table size: 1760
Section header file offset: 0x000138b4 (80052)
Section index for section name string table: 41
String table offset: 0x000136fb (79611)
Searching for .modinfo section...
- Section[16]: .modinfo
-- offset: 0x00000a14 (2580)
-- size: 0x000000cc (204)
Kernel release: 2.6.32.25-Buzz-1.0.6-OCUV
New .modinfo section size: 212
Attempting to power cycle eMMC... OK.
Searching for mmc_blk_issue_rq symbol...
- Address: c02ccc70, type: t, name: mmc_blk_issue_rq, module: N/A
Kernel map base: 0xc02cc000
Kernel memory mapped to 0x40001000
Searching for brq filter...
- ***WARNING***: Did not find brq filter.
Patching and backing up partition 7...
after some seconds it rebooted on its own but nothing happened to my cid. any ideas?

same here

That will be the live kernel patching failing as it cant find where to patch .... try running with my 1.0.7 kernel and then restore back (shuld run on stock kernels)... as i know that works ill relay this info to scotty2 and see if he can fix for these kernels.
Can you post your kernel info from the about phone menu ?

Apache14 said:
Can you post your kernel info from the about phone menu ?
Click to expand...
Click to collapse
here it is
2.6.32.25-Buzz-1.0.6-OCUV
[email protected] #66
Sat Nov 27 18:38:35 GMT2010

Worked great
To verify all went well, do this:
Plug in your phone to your computer
In the Terminal/command line, type this:
PHP:
adb shell
this puts you in the phone's shell. now it's a simple matter of the following:
(note the # is your prompt. Don't type the "#". The lines without the # are returned by the phone.)
PHP:
# stop ril-daemon
# cat /dev/smd0 &
# echo -e 'ATE1\r' > /dev/smd0
0
#
# echo -e 'ATV1\r' > /dev/smd0
OK
# echo -e '[email protected]?\r' > /dev/smd0
@CID: 11111111
OK
echo -e '[email protected]?40\r' > /dev/smd0
# [email protected]?40
@SIMLOCK= 00
OK
#echo -e '[email protected]?AA\r' > /dev/smd0
[email protected]?AA
@secu_flag: 0
OK
It should look something like that anyway. It may look slightly different if you were typing while the computer was sending you back information.
Did it work? Here's what you're looking for:
@CID: 11111111 <--- this response means you have superCID! Congrats!
@SIMLOCK= 00 <--- this means your simlock is off. Mazel Tov!
@secu_flag: 0 <--- this means your radio is S-OFF. Hurrah!

Hi,
not work for me.
Code:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. Alle Rechte vorbehalten.
C:\Users\Administrator>d:
D:\>cd D:\Handy\HTC Desire HD\SuperCID
D:\Handy\HTC Desire HD\SuperCID>adb push gfree /data/local
adb server is out of date. killing...
* daemon started successfully *
1939 KB/s (683255 bytes in 0.344s)
D:\Handy\HTC Desire HD\SuperCID>adb shell
# su
su
# cd /data/local
cd /data/local
# chmod 777 gfree
chmod 777 gfree
# ./gfree
./gfree
Section header entry size: 40
Number of section headers: 44
Total section header table size: 1760
Section header file offset: 0x000138b4 (80052)
Section index for section name string table: 41
String table offset: 0x000136fb (79611)
Searching for .modinfo section...
- Section[16]: .modinfo
-- offset: 0x00000a14 (2580)
-- size: 0x000000cc (204)
Kernel release: 2.6.32.25-Buzz-1.0.6-OCUV
New .modinfo section size: 212
Attempting to power cycle eMMC... OK.
Searching for mmc_blk_issue_rq symbol...
- Address: c02ccc70, type: t, name: mmc_blk_issue_rq, module: N/A
Kernel map base: 0xc02cc000
Kernel memory mapped to 0x40001000
Searching for brq filter...
- ***WARNING***: Did not find brq filter.
Patching and backing up partition 7...
D:\Handy\HTC Desire HD\SuperCID>
with friendly greet
starbase64

For the moment
IF THIS DOESNT WORK AND U GET
***WARNING***: Did not find brq filter.
Get either a stock kernel CM/SENSE or my buzz-1.0.7 as its confirmed working on those

Hi,
now works (or not ), but system info is no longer available on bootloader
with friendly greet
starbase64

Yep it worked
Look at the top SHIP S-OFF

Hi,
but how i can see the SuperCID? System info?
with friendly greet
starbase64

starbase64 said:
Hi,
not work for me.
Code:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. Alle Rechte vorbehalten.
C:\Users\Administrator>d:
D:\>cd D:\Handy\HTC Desire HD\SuperCID
D:\Handy\HTC Desire HD\SuperCID>adb push gfree /data/local
adb server is out of date. killing...
* daemon started successfully *
1939 KB/s (683255 bytes in 0.344s)
D:\Handy\HTC Desire HD\SuperCID>adb shell
# su
su
# cd /data/local
cd /data/local
# chmod 777 gfree
chmod 777 gfree
# ./gfree
./gfree
Section header entry size: 40
Number of section headers: 44
Total section header table size: 1760
Section header file offset: 0x000138b4 (80052)
Section index for section name string table: 41
String table offset: 0x000136fb (79611)
Searching for .modinfo section...
- Section[16]: .modinfo
-- offset: 0x00000a14 (2580)
-- size: 0x000000cc (204)
Kernel release: 2.6.32.25-Buzz-1.0.6-OCUV
New .modinfo section size: 212
Attempting to power cycle eMMC... OK.
Searching for mmc_blk_issue_rq symbol...
- Address: c02ccc70, type: t, name: mmc_blk_issue_rq, module: N/A
Kernel map base: 0xc02cc000
Kernel memory mapped to 0x40001000
Searching for brq filter...
- ***WARNING***: Did not find brq filter.
Patching and backing up partition 7...
D:\Handy\HTC Desire HD\SuperCID>
with friendly greet
starbase64
Click to expand...
Click to collapse
Try with 1.07 kernel.
If it doesnt work try with stock kernel which works fine
I think only the ENG Hboot shows system info...

Flawless, cheers

starbase64 said:
Hi,
but how i can see the SuperCID? System info?
with friendly greet
starbase64
Click to expand...
Click to collapse
fastboot getvar all

So can we now flash radio's without fear of being locked down again?

Apache14 said:
fastboot getvar all
Click to expand...
Click to collapse
I love ur 1.0.6 kernell.
Can I flash 1.0.7, S-OFF radio, and then back 1.06??

yep u can flash official HTC RUUS / RADIO / HBOOT without any fear of loosing root

xmoo said:
I love ur 1.0.6 kernell.
Can I flash 1.0.7, S-OFF radio, and then back 1.06??
Click to expand...
Click to collapse
yep yep thats fine

Is there anyway to undo this? Incase of garanty issues?

dubstepshurda said:
Is there anyway to undo this? Incase of garanty issues?
Click to expand...
Click to collapse
S-OFF has nothing to do with legal or illigal.
In somecases when you send your phone for repair, they S-off it, and forget to remove it.
So just remove superuser, install stock rom. And don't matter S-ON or s-OFF
"ON ENG HBOOT
2) tap bootloder option
3) use vol down to get to system info and tap
4) check CID for CID-11111111 (if you have this all is done 100%)
5) reboot"
2) tap bootloader option You fotgot the A.

[Q] Cannot allocate TUN/TAP dev dynamically HTC Desire

I use, HTC desire
HBOOT Alpharev 1.8, BRAVO
Android 2.2
Baseband version
2.6.32.15-gf5a401c
HTC-kerneland18-2
Build number:
2.29.405.5
Make, S-OFF with Alpharev, it's very good install busybox is ready.
But, I like use OPENVPN, with ca, key, files. I copyed from sd card and USE OPENVP INSTALLER,
Binary installed:
/system/xbin/openvpn
/system/bin/openvpn
OPENVPN setting, load the ovpn, config and start the connecting...
-»USR/PASSW-»Auth-»Get Config....
"Cannot allocate TUN/TAP dev dynamically"
I read, diferent forums and, my linux knowledge and try find the error from adb-shell.
test:
$ openvpn --dev tunX
Sun Jan 9 18:32:02 2011 OpenVPN 2.1.1 i686-pc-linux-gnu [SSL] [LZO2] [EPOLL] built on Feb 2 2010
Sun Jan 9 18:32:02 2011 IMPORTANT: OpenVPN's default port number is now 1194, based on an official port number assignment by IANA. OpenVPN 2.0-beta16 and earlier used 5000 as the default port.
Sun Jan 9 18:32:02 2011 NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Sun Jan 9 18:32:02 2011 ******* WARNING *******: all encryption and authentication features disabled -- all data will be tunnelled as cleartext
Sun Jan 9 18:32:02 2011 Note: Cannot open TUN/TAP dev /dev/tun: No such file or directory (errno=2)
Sun Jan 9 18:32:02 2011 Note: Attempting fallback to kernel 2.2 TUN/TAP interface
Sun Jan 9 18:32:02 2011 Cannot allocate TUN/TAP dev dynamically
Sun Jan 9 18:32:02 2011 Exiting
$
Can someone help me ?

WP7 hacking ...

Hello,
i look on my WP7 and see cert ...
Look on a root cert, name is :
with fallow entry:
Schlüssel-ID=8b 4b 6d ed d3 29 b9 06 19 ec 39 39 a9 f0 97 84 6a cb ef df
Zertifikataussteller:
Verzeichnisadresse:
CN=QuoVadis Root Certification Authority
OU=Root Certification Authority
O=QuoVadis Limited
C=BM
Seriennummer des Zertifikats=3a b6 50 8b
Who can tell me now what it is for cert !?
it is not a hash for root ?!
THX
P.S.
Will learn what make my machine
//Edit:
Fingerprint Algorythm is :
sha1
Typ des Antragstellers=Zertifizierungsstelle
Einschränkung der Pfadlänge=Keine
Typ of Applicant= CA
Zertifikatsignatur, Offline Signieren der Zertifikatsperrliste, Signieren der Zertifikatsperrliste (06)
Sorry, cant translate it XD
Have look on Internet and have found this:
http://www.quovadisglobal.ch/Repository/DownloadRootsAndCRL.aspx#QuoVadis Root CA
here you can download cert and root cert
http://www.quovadisglobal.ch/Repository/~/media/Files/Roots/quovadis_rca_der.ashx
This is cert, that is on my phone who can tell me now what it is
Have a nother cert found, it is whit RSA Key and 1024bit
here is a report that there found a security hole in RSA
http://www.eecs.umich.edu/~valeria/research/publications/DATE10RSA.pdf
But i see that in cert are 2048 bit XD
is this for root access !?
"Microsoft Secure Server Authority"

[REQUEST]: dump of /persist folder

Hi,
Would someone with a carrier/SIM-unlocked Moto G be able to provide me with a dump of their /persist folder?
I think you'll probably need to be rooted also.
After starting an adb shell, I did this:
cp -r /persist /storage/emulated/legacy/download
and then was able to copy the persist folder from the Download folder onto my PC
What I'm hoping is that the SIM unlock status is stored in a file in the persist folder...
My attempts to unlock via code have been unsuccessful -- I've tried 3 different unlock services but they've all come back unable to find a code for my IMEI.
My phone is a XT1032 that's locked to Telus/Koodo in Canada.
cheers
albert.

Bump. I'm sitting in the same boat as are many other Canadian moto g owners.
Sent from my XT1032 using XDA Premium 4 mobile app

AlbertDude said:
Hi,
Would someone with a carrier/SIM-unlocked Moto G be able to provide me with a dump of their /persist folder?
I think you'll probably need to be rooted also.
After starting an adb shell, I did this:
cp -r /persist /storage/emulated/legacy/download
and then was able to copy the persist folder from the Download folder onto my PC
What I'm hoping is that the SIM unlock status is stored in a file in the persist folder...
My attempts to unlock via code have been unsuccessful -- I've tried 3 different unlock services but they've all come back unable to find a code for my IMEI.
My phone is a XT1032 that's locked to Telus/Koodo in Canada.
cheers
albert.
Click to expand...
Click to collapse
I have rooted and SIM unlocked Moto G.
I checked /persist and it's folders and sub-folders..........
I can find no file or data with date newer than Nov 7, 2013 which are original files as I only SIM Unlocked Dec 5th. and I only acquired phone just days before that!!
So, where in /persist do you think this data resides???

I was hoping that it would be a flag in one of those *nv.bin files. But from their names (".bt_nv.bin" and "WCNSS_qcom_wlan_factory_nv.bin"), it looks like they might be config files for bluetooth and wlan.
If you don't mind doing some digging, I would be interested in knowing if there were any files modified when you SIM unlocked (Dec. 5).
I think these series of steps would work to do so:
adb shell
su
cd /
ls -lR | grep 2013-12-05
Hopefully, you didn't do much else with the phone on Dec. 5...
irishpancake said:
I have rooted and SIM unlocked Moto G.
I checked /persist and it's folders and sub-folders..........
I can find no file or data with date newer than Nov 7, 2013 which are original files as I only SIM Unlocked Dec 5th. and I only acquired phone just days before that!!
So, where in /persist do you think this data resides???
Click to expand...
Click to collapse

AlbertDude said:
I was hoping that it would be a flag in one of those *nv.bin files. But from their names (".bt_nv.bin" and "WCNSS_qcom_wlan_factory_nv.bin"), it looks like they might be config files for bluetooth and wlan.
If you don't mind doing some digging, I would be interested in knowing if there were any files modified when you SIM unlocked (Dec. 5).
I think these series of steps would work to do so:
adb shell
su
cd /
ls -lR | grep 2013-12-05
Hopefully, you didn't do much else with the phone on Dec. 5...
Click to expand...
Click to collapse
Hi...sorry, just seen this...
can i get back to you, i don't have the phone here, but as soon as i get home, I'll do that for you, OK??

AlbertDude said:
I was hoping that it would be a flag in one of those *nv.bin files. But from their names (".bt_nv.bin" and "WCNSS_qcom_wlan_factory_nv.bin"), it looks like they might be config files for bluetooth and wlan.
If you don't mind doing some digging, I would be interested in knowing if there were any files modified when you SIM unlocked (Dec. 5).
I think these series of steps would work to do so:
adb shell
su
cd /
ls -lR | grep 2013-12-05
Hopefully, you didn't do much else with the phone on Dec. 5...
Click to expand...
Click to collapse
see attached file....
but grep o/p shown below???
[email protected]_umts:/ # ls -lR | grep 2013-12-05
drwxr-xr-x mot_pwric mot_pwric 2013-12-05 21:43 batt_health
-rw-r----- mot_pwric mot_pwric 32 2013-12-05 21:43 batt-0123456789abcdef_0
drwxrwx--- system mot_tcmd 2013-12-05 18:35 svcs
-rw-rw---- u0_a0 mot_tcmd 8 2013-12-05 18:35 activation_date
Click to expand...
Click to collapse

Interesting!
I assume that the "activation_date" file is in the "svcs" folder?
Could you do some more digging to find the full path to this file?
I think you can do a search for that file from adb shell with these commands:
cd /
find -name activation_date
I won't be able to check my phone for this file till late tonight.
cheers.
irishpancake said:
see attached file....
but grep o/p shown below???
Click to expand...
Click to collapse

AlbertDude said:
Interesting!
I assume that the "activation_date" file is in the "svcs" folder?
Could you do some more digging to find the full path to this file?
I think you can do a search for that file from adb shell with these commands:
cd /
find -name activation_date
I won't be able to check my phone for this file till late tonight.
cheers.
Click to expand...
Click to collapse
Hi, find is busybox command, so I installed it!!! [using terminal emul]
OK, here is the output: [just bolded and colored the path to activation_date for clarity]
[email protected]_umts:/ $ su
[email protected]_umts:/ # cd /
[email protected]_umts:/ # pwd
/
[email protected]_umts:/ # find -name activation_date
./pds/public/svcs/activation_date
find: ./proc/21679/task/21679/ns/net: No such file or directory
find: ./proc/21679/ns/net: No such file or directory
find: ./proc/22243: No such file or directory
find: ./proc/22421/task/22421/ns/net: No such file or directory
find: ./proc/22421/ns/net: No such file or directory
1|[email protected]_umts:/ #
1|[email protected]_umts:/ #
Click to expand...
Click to collapse

I have the "activation_date" file also. Mine has a modification date of Dec 06 -- which is when I unlocked the bootloader and rooted the phone.
It's contents (via a hex editor are):
0000000: 0000 0142 c73e 7789 ...B.>w...
irishpancake: would you be able to share the contents of your version of the file?
thanks!
irishpancake said:
Hi, find is busybox command, so I installed it!!! [using terminal emul]
OK, here is the output: [just bolded and colored the path to activation_date for clarity]
Click to expand...
Click to collapse

AlbertDude said:
I have the "activation_date" file also. Mine has a modification date of Dec 06 -- which is when I unlocked the bootloader and rooted the phone.
It's contents (via a hex editor are):
0000000: 0000 0142 c73e 7789 ...B.>w...
irishpancake: would you be able to share the contents of your version of the file?
thanks!
Click to expand...
Click to collapse
OK, using HxD
Code:
Offset (h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
00000000 00 00 01 42 C4 0B 1B 5B ...BÄ..[
Original file Permissions: rw-rw-rw- [0666]
Path: /pds/public/svcs/activation_date
Size: 8.008B
Last modified: Dec 05, 2013 08:35:00 pm
Owner: u0_a0
Group: mot_tcmd

Well,
that was disappointing -- the data is actually a timestamp (which makes sense for a file called "activation_date").
It's the number of milliseconds since the Unix epoch (1970-01-01).
Back to the drawing board...
irishpancake said:
OK, using HxD
Code:
Offset (h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
00000000 00 00 01 42 C4 0B 1B 5B ...BÄ..[
Original file Permissions: rw-rw-rw- [0666]
Path: /pds/public/svcs/activation_date
Size: 8.008B
Last modified: Dec 05, 2013 08:35:00 pm
Owner: u0_a0
Group: mot_tcmd
Click to expand...
Click to collapse

AlbertDude said:
Well,
that was disappointing -- the data is actually a timestamp (which makes sense for a file called "activation_date").
It's the number of milliseconds since the Unix epoch (1970-01-01).
Back to the drawing board...
Click to expand...
Click to collapse
OK, sorry, thanks for the info anyway!!!
It was an interesting exercise for me :good:
If I can do anything else, within my not inconsiderable limits, let me know.....cheers

Thanks for trying. So I'm guessing it's a no-go.
Sent from my XT1032 using XDA Premium 4 mobile app

Koodo is offering the code for $50. What a rip!
Sent from my XT1032 using XDA Premium 4 mobile app

So I SIM-unlocked my Moto G with an unlock code (after trying 4 unlock services) but prior to unlocking, I dumped a bunch of files onto my PC.
I grabbed these same files after unlocking and took a look to see which of these files were changed.
The only thing that I noted that changed after unlocking was in
./proc/config/time.offset
I wasn't actually able to copy the files from ./proc since they were all 0 bytes (see http://www.tldp.org/LDP/Linux-Filesystem-Hierarchy/html/proc.html)
However, I was able to view their contents using 'cat'
The time.offset data changed from:
Tag: Name [time.offset:llong] Size: [8]
Data:
[0x42] [0x71] [0x29] [0xED] [0xFF] [0xFF] [0xFF] [0xFF]
to:
Tag: Name [time.offset:llong] Size: [8]
Data:
[0x41] [0x71] [0x29] [0xED] [0xFF] [0xFF] [0xFF] [0xFF]
So the first byte of the "time.offset" data might be a SIM-lock indication.
Would be interesting to see what other people's phones show for this data.

How exactly do I read /proc/config/time.offset?
"cat /proc/config/time.offset" gives the error that it's a directory.

It's easier to check the values in the folder: /proc/config/all
where you can do a 'cat < new'
However, checking my phone's value today shows:
Tag: Name [time.offset:llong] Size: [8]
Data:
[0x3F] [0x71] [0x29] [0xED] [0xFF] [0xFF] [0xFF] [0xFF]
So it looks like that first byte isn't related to the sim-lock status as its value has changed again.
Also if you go into the /proc/config/time.offset folder you'll see 3 files: ascii, raw, type
'cat < raw' shows:
3F7129EDFFFFFFFF
So back to square one with no clue as to where the SIM-lock status is stored.
lost101 said:
How exactly do I read /proc/config/time.offset?
"cat /proc/config/time.offset" gives the error that it's a directory.
Click to expand...
Click to collapse

Should I just throw in the towel and sell this phone?
Sent from my XT1032 using XDA Premium 4 mobile app

I bought two Moto G, both cannot unlocked. so what I can do?

Buy retail, unlocked moto g (any phone) next time. Or port nr to provider they are locked to.