yashsingh1/xdaforums huggingface dataset:
[Moto G Android Development] a1Pha:
I am also trying to compile CWM for my unlocked G.

I used unmkbootimg, which gave me the following output:

unmkbootimg version 1.2 - Mikael Q Kuisma <kuisma@ping.se>
Kernel size 6198344
Kernel address 0x8000
Ramdisk size 653995
Ramdisk address 0x2000000
Secondary size 0
Secondary address 0xf00000
Kernel tags address 0x1e00000
Flash page size 2048
Board name is ""
Command line "console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 vmalloc=400M utags.blkdev=/dev/block/platform/msm_sdcc.1/by-name/utags"

*** WARNING ****
This image is built using NON-standard mkbootimg!
OFF_KERNEL_ADDR is 0xFE208100
OFF_RAMDISK_ADDR is 0x00200100
OFF_SECOND_ADDR is 0xFF100100
Please modify mkbootimg.c using the above values to build your image.
****************

Extracting kernel to file zImage ...
Extracting root filesystem to file initramfs.cpio.gz ...
All done.
---------------
To recompile this image, use:
mkbootimg --kernel zImage --ramdisk initramfs.cpio.gz --base 0x1dfff00 --cmdline 'console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 vmalloc=400M utags.blkdev=/dev/block/platform/msm_sdcc.1/by-name/utags' -o new_boot.img

Using the values above I patched mkbootimg.c to contain the following lines:

unsigned kernel_offset = 0xfe208100;
unsigned ramdisk_offset = 0x00200100;
unsigned second_offset = 0xff100100;

So my BoardConfig.mk looks like this:

USE_CAMERA_STUB := true

# inherit from the proprietary version
-include vendor/motorola/xt1032/BoardConfigVendor.mk

TARGET_ARCH := arm
TARGET_NO_BOOTLOADER := true
TARGET_BOARD_PLATFORM := msm8960
TARGET_CPU_ABI := armeabi-v7a
TARGET_CPU_ABI2 := armeabi
TARGET_CPU_VARIANT := cortex-a9
TARGET_ARCH_VARIANT := armv7-a-neon
ARCH_ARM_HAVE_TLS_REGISTER := true

TARGET_BOOTLOADER_BOARD_NAME := xt1032

BOARD_KERNEL_CMDLINE := console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 vmalloc=400M utags.blkdev=/dev/block/platform/msm_sdcc.1/by-name/utags
BOARD_KERNEL_BASE := 0x1dfff00
BOARD_KERNEL_PAGESIZE := 2048

BOARD_HAS_LARGE_FILESYSTEM := true
BOARD_HAS_NO_REAL_SDCARD := true
RECOVERY_SDCARD_ON_DATA := true

# fix this up by examining /proc/mtd on a running device
BOARD_BOOTIMAGE_PARTITION_SIZE := 10485760
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 10485760
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 1023410176
BOARD_USERDATAIMAGE_PARTITION_SIZE := 5930614784
BOARD_FLASH_BLOCK_SIZE := 131072

TARGET_PREBUILT_KERNEL := device/motorola/xt1032/kernel

BOARD_HAS_NO_SELECT_BUTTON := true

where kernel is the zImage which resulted as an output from unmkbootimg.

But somehow I can't get it to boot on my G, it just reboots into normal startup mode.

Any ideas?
[Moto G Android Development] seapoint:
What about

adb reboot recovery
[Moto G Android Development] Rusty!:
OK I'm home and have actually attached the file this time.
[Moto G Android Development] a1Pha:
Same as with my attempts. Your image does not boot into recovery.

Neither "fastboot boot" nor flashing it leads to success.

Did you read my post on the first page? Maybe we could try to build it together :)
[Moto G Android Development] shaftenberg:
Guys, can't help with know-how, but I'm refreshing this thread every 2 minutes :D keep on rocking!
[Moto G Android Development] Rusty!:
Typical... not surprising though.

I can post up my board_config later, I noticed you put Cortex A9 in yours, I used A7 since I'm pretty sure that's what the Snapdragon 400 is
[Moto G Android Development] a1Pha:
Indeed. Thanks.

Just recompiled with cortex-a7, no effect though.
[Moto G Android Development] Rusty!:
Just a thought, but it might be that fastboot boot is the problem, some things don't actually support it and this could be one of ones that don't.

Quick way to check would be to try and fastboot boot the stock recovery.
[Moto G Android Development] yaulapman:
that means no cwm?
[Moto G Android Development] Rusty!:
Not right now, but people are trying.
[Moto G Android Development] a1Pha:
I already flashed our attempts, it won't boot.
[Moto G Android Development] ferreinf:
How about twrp?

Just asking, waiting for u guys :)

Thanks
[Moto G Android Development] a1Pha:
fastboot boot does not boot stock recovery.img neither. Had to reflash for it to work.

But since we have stock recovery.img I don't see any danger in flashing our custom recoveries.
[Moto G Android Development] the|gamer:
You can upload the stock recovery.img please? I would like to try something :)
[Moto G Android Development] a1Pha:
Here you go :)
[Moto G Android Development] the|gamer:
Nice! will extract it an look forward on building an CWM.

So sad the CWMbuilder does not work anymore http://builder.clockworkmod.com/
[Moto G Android Development] Rusty!:
Welcome to the club
[Moto G Android Development] alex1301:
If we could get the boot.img of the Moto G, we could use this tutorial.
[Moto G Android Development] a1Pha:
Stock boot.img - you can find my BoardConfig.mk on the first page in this thread. Replace cortex-a9 with cortex-a7. Still doesn't boot.

---------- Post added at 04:32 PM ---------- Previous post was at 04:27 PM ----------

My recovery.fstab:

# mount point	fstype device	[device2]

/boot mtd boot
/cache yaffs2 cache
/data yaffs2 data
/misc mtd misc
/recovery mtd recovery
/sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
/system yaffs2 system
/sd-ext ext4 /dev/block/mmcblk0p2
[Moto G Android Development] alex1301:
Hm, ok, i am not a dev, that was only a suggestion :D
[Moto G Android Development] Rusty!:
I used the stock recovery.fstab, the one that got generated was all over the place with it's filesystem types
[Moto G Android Development] a1Pha:
My bad, already had figured this out and extracted the fstab from initramfs. Was not going to wipe anything yet :D

Will post progress later when I'm home.
[Moto G Android Development] a1Pha:
Had a look at serrano, tried some configuration options. No success though.

I think the BOARD_KERNEL_BASE and/or the ramdisk offset I am using are wrong.
[Moto G Android Development] shaftenberg:
:(

But I am sure you'll get it... :)
[Moto G Android Development] alex1301:
News for root:

I asked jcase if he could help us to get at least root :D I am waiting for his answer, but I will think we will have root soon ;)
[Moto G Android Development] shaftenberg:
I asked jcase several days ago. I tried PawnMyMoto and RockMyMoto with his help, both failed due to closed exploits. He said we have to wait unfortunately.
[Moto G Android Development] a1Pha:
Okay, so I have thrown away the stock boot.img and am tinkering with the stock recovery.img.

Its offset is being reported as 0x0. Additionally, I get the following output from the stock android:

shell@falcon_umts:/ $ cat /proc/iomem
[B]00000000-083fffff[/B] : System RAM
00008000-00c2f2cf : Kernel code
00e14000-011088cb : Kernel data
0c400000-0d1fffff : System RAM
0f600000-0f9fffff : System RAM
0ff00000-3f3fffff : System RAM
f991f000-f991ffff : msm_serial_hsl
f9924000-f9924fff : f9924000.i2c

So I assume 0x0 is the right BOARD_KERNEL_BASE. Still can't get CWM to boot.

I am running out of ideas. Any suggestions?
[Moto G Android Development] yggdrasil31:
I would say BOARD_KERNEL_BASE is 0x8000, but reading this http://xdaforums.com/showthread.php?t=1513432, maybe there is an offset to apply to convert this address into physical address on the board. Hope this could help...
[Moto G Android Development] a1Pha:
According to this (referenced here) and this, our base is indeed 0x0 :S
[Moto G Android Development] N00BY0815:
Do you have a git I can have a look at? We had to overwrite the cmdline arguments, so a bigger file would be accepted. And what happens if you replace the cwm zImage with the stock one, just to try? This way you could probably see, if it is a ramdisk or zImagr issue. Hope it works ;)

P.S Ich bin auch aus Deutschland :)
[Moto G Android Development] a1Pha:
I can set up a git repository, if you want ;) Give me a few mins.

The generated CWM recovery.img is in fact smaller than the stock one (8mb vs 10mb).

I am already using the prebuilt kernel I extracted from stock recovery.img :(

P.S.: LG aus Hamburg ;)
[Moto G Android Development] N00BY0815:
Ah ok, it might also be the prebuilt kernel ;) i am just asking for the sourcecode, as we speak :D
[Moto G Android Development] a1Pha:
The git repo you requested: https://github.com/Zanooda/xt1032

I think the sourcecode is going to be released soon - the Moto X source has been published 5 days after device release :)
[Moto G Android Development] a1Pha:
I asked Motorola for the kernel sources - here is their response.
[Moto G Android Development] cloogshizer:
Cool, thank you for asking and sharing! I already wonder what goodies there are in the sources :)
[Moto G Android Development] t-bon3:
Maybe we should keep an eye on this link:

http://sourceforge.net/projects/motog.motorola/?source=directory
[Moto G Android Development] a1Pha:
I am already F5'ing the **** out of this url ;)
[Moto G Android Development] cloogshizer:
Your question to [MENTION=1142255]motorolas[/MENTION]upport made it to the GSMArena blog (http://blog.gsmarena.com/motorola-moto-g-plagued-by-a-recovery-bug/) , so maybe this will speed things up ;)
[Moto G Android Development] a1Pha:
Well, that's another tweet I wrote. It is related to a bug in the stock recovery, have a look at this thread ;)
[Moto G Android Development] helinhof:
Root

And the Moto G already has root :D
[Moto G Android Development] a1Pha:
It's not working for me.

---------- Post added at 08:03 PM ---------- Previous post was at 07:28 PM ----------

Update on kernel sources.
[Moto G Android Development] helinhof:
One week till the fun starts...
[Moto G Android Development] N00BY0815:
I dare to bet, that the kernel offset needs to be:

BOARD_KERNEL_BASE := 0x00008000

but let's see next week :D
[Moto G Android Development] toby913:
hey,

any progress on this?

:D
[Moto G Android Development] yggdrasil31:
waiting for the kernel source code to check how to configure CWM
[Moto G Android Development] toby913:
This is the last thing I heard... Were they already released?
[Moto G Android Development] LuisUrrutia:
The sources will be published this week.
[Moto G Android Development] a1Pha:
No CWM without kernel sources, stock kernel does not allocate enough memory for CWM or TWRP in initrd.
[Moto G Android Development] flargen:
The kernel sources (and sources of some other packages) have just been released by Motorola:

http://sourceforge.net/projects/motog.motorola/files/14.10.0Q3.X-76-LCG-8/

Thread on XDA about the sources:

http://xdaforums.com/showthread.php?t=2558581

:cool: :cool: :cool:
[Moto G Android Development] American Graffiti:
A guy in HTCMania.com has published (just 20minutes ago) a TWRP Recovery compiled from Motorola sources, but it hasn't been tested cause he doesn't got the MotoG already.

I've asked him about publishing here, so I wish it should be published here in a little.

---------------------------------------------------------------------------------------------------------------------------

_edit: I talked to [MENTION=4812668]josalaito[/MENTION] and he agreed to publish it, so here we go.

Hi, here I bring the TWRP recovery compiled by me from sources, although I have no cell phone and as such, is not tested, but everything is checked before compiling and should work perfectly.

I need a tester with BL unlocked, if anyone is encouraged here is the link:

LINK: http://d-h.st/5oN

To flash it, you have to turn on the mobile in bootloader mode, connect to pc and use fastboot to:

fastboot flash recovery recovery.img

Should not be alarmed not work, I leave the stock, which flashed in the same way as above, removes all problems:

LINK: http://d-h.st/e0c

BUGS: The phone did not charge off (You will enter a recovery), if we check that boots, I fix it.
[Moto G Android Development] josalaito:
I'm that guy and i can clarify some things for unbooted cwm, first of all, you should use this fstab: https://github.com/oblikas/android_device_motorola_ghost/blob/master/recovery.fstab (It says moto x but is the same) and this parameter in BoardConfig: BOARD_MKBOOTIMG_ARGS := --ramdisk_offset 0x02000000 , i only need the BOARD_KERNEL_BASE for make a functional kernel, but when i use readers, the result is 0x0000000, so that's a problem.
[Moto G Android Development] IINexusII:
I have tested this, and it fails. same issue you guys are having with CWM. it fails to boot into recovery, it will just reboot back into the bootloader

screenshot:
[Moto G Android Development] josalaito:
Ok, we need to found kernel base size, all my resources says 0x00000000 so i think we need to found it in kernel source

LOL https://github.com/josalaito/android_kernel_motorola_msm8226/blob/debdeb44b5ce8fc2f2becca4bb11ad0b85f88de9/arch/arm/mach-msm/Kconfig#L1141
[Moto G Android Development] sioxz:
Keep up your good work in making a recovery run on this phone as it's one important part on if i should buy this phone or not
[Moto G Android Development] the|gamer:
what does cat /proc/mtd say?
[Moto G Android Development] josalaito:
New build of twrp in few minutes, some important changes and fixed ramdisk offset, should works.
[Moto G Android Development] a1Pha:
Could you share your kernel .config and your BoardConfig.mk please?

//EDIT: I have built my own kernel from Motorolas sources, it won't boot the stock recovery.
[Moto G Android Development] josalaito:
I'm using stock kernel, lg g2 for example has the same BASE_SIZE(0x00000000) and it works, the problem is offset ramdisk.

If someone could try this recovery build: http://d-h.st/PWY

My sources(If doesn't work, you only need to change ramdisk offset to 0x02000000) 0x02000000
[Moto G Android Development] a1Pha:
Kernel base ist 0x0, ramdisk offset is 0x01000000. We already tried booting custom recoveries with stock binary kernel, it didn't succeed. I think it was because our custom recoveries were larger than the stock allocated ramdisk size, so you should have to recompile the kernel.
[Moto G Android Development] josalaito:
https://github.com/josalaito/android_kernel_motorola_msm8226/blob/debdeb44b5ce8fc2f2becca4bb11ad0b85f88de9/arch/arm/mach-msm/Kconfig#L1141

I'm sure that base size is 0X0

EDIT: Can you try my recovery build? Maybe works but i haven't got the phone yet
[Moto G Android Development] a1Pha:
As I said before ;)
[Moto G Android Development] josalaito:
Now, i unpackbootimg the kernel and it's says Ramdisk Load Address : 0x02000000

So when i unpack boot.img ramdisk is 0x02 but when i unpack recovery.img ramdisk is 0x01, maybe if we make two builds, one for offset,one of they boot.
[Moto G Android Development] a1Pha:
Yeah, had this strange behaviour before. unpackbootimg on boot.img gave me 0x02 but 0x01 on recovery.img..

---------- Post added at 11:31 PM ---------- Previous post was at 11:30 PM ----------

Did you try to recompile the kernel on your own?
[Moto G Android Development] josalaito:
I'm compiling one with 0x02, can you try it?
[Moto G Android Development] a1Pha:
Of course. Just send me the link.
[Moto G Android Development] josalaito:
This is with 0x01: http://d-h.st/PWY

And this with 0x02 http://d-h.st/xjc
[Moto G Android Development] a1Pha:
Flashed both of them via fastboot, none of them work =/
[Moto G Android Development] josalaito:
Maybe is the custom init.rc?

For this things the online builder of cwm was the best, give you some idea of how make your config.
[Moto G Android Development] the|gamer:
Yes! So sad it is deactivated now! It helped me a lot when bringing CWM on foreign Devices
[Moto G Android Development] helinhof:
CWM Builder - Falcon

In the latest builds page at CWM builder - is it just a failed attempt?
[Moto G Android Development] artov:
+1 the CWM builder seems to be alive and kicking
[Moto G Android Development] tillaz:
those are just failed builds, its still disabled look http://jenkins.cyanogenmod.org/job/recovery/

download it and you will see

http://jenkins.cyanogenmod.org/job/...droid_device_motorola_falcon_umts.zip/*view*/
[Moto G Android Development] t-bon3:
I tried both of these via 'fastboot boot recovery.img', they both boot but only to a garbled screen. I used fastboot.exe included in the stock firmware image.

On pressing power something changes on the screen but I cannot see what.

'adb devices' can see the phone and reports that it is in 'recovery' mode.
[Moto G Android Development] a1Pha:
Okay, that is highly demotivating. Looks like the same problem as in Pauls superboot.img - some devices could boot it, others wouldn't.

I will continue to try to get a custom kernel booting later this day.

//EDIT: Looks like there is a just a graphics.c that needs to be adjusted :)
[Moto G Android Development] t-bon3:
It seems to be working on my device, if I pull the framebuffer image with adb it looks like this:
[Moto G Android Development] a1Pha:
Now that my own kernel is starting up, I will continue trying to get CWM booting :)
[Moto G Android Development] josalaito:
Ok, i know the graphics bug, fixed today in a build
[Moto G Android Development] a1Pha:
TWRP boots, display output is working. Have to fix touch now.
[Moto G Android Development] ximmox:
Very nice guys, I won't have my Moto G until January, but you work seems very promising! In a few days there will be everything ready to kickstart the Moto G Original Android Development Forums, keep it up!
[Moto G Android Development] a1Pha:
I have just posted my build of TWRP here.
[Moto G Android Development] the|gamer:
Wo what did the trick?
[Moto G Android Development] a1Pha:
I used my own kernel build ;)
[Moto G Android Development] the|gamer:
So it is a good Idea to put the Kernel Soruces in the DevTree and don't use a prebuild kernel, is anyone working on a Devtree? I would like to help, if someone could create a Git for this!
[Moto G Android Development] josalaito:
OK, i made a compilation with f2fs support(Data now can be flashed and wiped) and i'm going to make a thread in a few minutes.
[Moto G Android Development] Doublepranks:
Where would it save backups?
[Moto G Android Development] a1Pha:
Updated my github repo with josalaitos f2fs fix, uploading new build. This should support encrypted /data, too. If anyone is willing to try...

MODS: Can we merge all the CWM threads into a single one?
[Moto G Android Development] SouSoulebarbu:
+1
[Moto G Android Development] Rusty!:
Yeah totally do that, my thread is pretty pointless now.
[Moto G Android Development] michalurban:
Is this official? Or when/where will be official? And does it even matter? :D
[Moto G Android Development] Rusty!:
No it's not official (this one doesn't even work anyway), others are unofficial. Will/when will it be official? Noone knows. Does it matter? Not in the slightest.
[Moto G Android Development] michalurban:
Im not sure how to use this recovery for backup and restore. Ive always thought that if I wanted to restore a backed up system I should make factory reset + format /system ... and then to restore from backup. Thats what Ive always been doing on Nexus S. But here I cant make a factory reset prior the restoration because it would delete the CWM backup files on /sdcard (I mean /data/media) ...

EDIT: Disregard it. I see now that CWM wont affect my files ... :)
[Moto G Android Development] denzel09:
Hi, now that Philz recovery is open source and that philz no more will update in future any devices, someone can take this ownership?

Thanks

http://xdaforums.com/showthread.php?p=51461679
[Samsung Galaxy W I8150] dudiadudia1:
hi,

i have the galaxy W with CM10 4.1.2 on it. the device is rooted ofcourse.

is there a way to mount the ex SD card as USB mass storage device?

i want to be able to connect it to my car's multimedia system and it has a USB input plug.

thanks.
[Samsung Galaxy W I8150] saleelsalam:
It works man.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] salcirabisi:
Is it true that once we install the 4.3 leak (loserskater, agriff, saranhai roms for AT&T Galaxy S3 I747) there is no going back to stock?:confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] salcirabisi:
Continued....

I understand these 4.3 ROM's are stock but I'm wondering about the possibility of returning to stock via ODIN and upgrading non-root via AT&T?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kirkgbr:
From what I've read in many threads here last couple days, the correct statement is:

Once you have updated to 4.3 via OTA you cannot return to previous versions(ie 4.1.1 or 4.1.2) in any way.
[Xperia Tablet Z Q&A, Help & Troubleshooting] woggly4:
Hi,

I'm planning to buy a XTZ. But I'm not sure whether buying the LTE or Wifi version.

How does the LTE-module affect battery drain, compared to Wifi?

thanks,

woggly4
[Xperia Tablet Z Q&A, Help & Troubleshooting] DooshPastesh:
I'm not using LTE now but 3g only. It drains A LOT. But when I'm on plane mode (for turnig of mobile data permamently - trick from asus tablets) and only wifi, it works much longer.

Wysłane z mojego SGP321 za pomocą Tapatalk 2
[Sony Xperia P, U, Sola, Go] alt_Smog_:
Hello everyone.

Who can install a driver fastboot/flashtool on windows 8.1?

I installed but the PCs don't see phone.
[Sony Xperia P, U, Sola, Go] Wind07:
Not at the moment
[Sony Xperia P, U, Sola, Go] XperianPro:
Compleatly same problem,windows blue cant recognize it.
[Sony Xperia P, U, Sola, Go] alt_Smog_:
maybe virtual machin help, me?. I will try virtyal machine and write here about result.
[Sony Xperia P, U, Sola, Go] ChikeD:
If by "blue" you mean USB 3 port, there is a thread in this forum with drivers that work on windows 8 for Intel boards, search.
[Sony Xperia P, U, Sola, Go] Wind07:
I will just go to win 7 lol

Sent from my Experimental Device Xperia neo v
[LG Optimus G (International)] banangrg:
Hi everyone,

i've got a big problem. Today i've installed Adverntures of Tin Tin game and when I run it, it shows my device is not compabitible with this app. Anyway i want to try sth, because the game was working on older Adreno devices, so...i tried to edit build.prop for cheating the app ("Change" my phone to for example HTC Desire HD).

When I try to edit build.prop (tried with Root Explorer and ES too), i have (in theory) mounted as r/w in file explorer, but when i try to copy or edit or do anything in /system/ i see "Permission denied" label. I've also tried to push my edited build.prop using adb, but the result is the same: "Permission Denied". Anyone help me?:)
[JASJAR, XDA Exec, MDA Pro Software Upgrading] Gilbert:
Hello All,

Everyone seems to be talking about a new EXEC or PRO rom for their devices but no news on a Qtek 9000 new rom. Does one actually exists or is in the making?

Gilbert
[JASJAR, XDA Exec, MDA Pro Software Upgrading] Gilbert:
Anyone

Anyone has an ideo on when Qtek 9000 will have a rom update and if it is available now can someone give me the link to download it.

Best regards,

Gilbert
[JASJAR, XDA Exec, MDA Pro Software Upgrading] sank5:
What's the most stable version so far?

Does it matter if you use another manufacturers ROM's?

What are the consequencies?

Thanks
[Android Q&A, Help & Troubleshooting] falf123:
I Have A G-tide E52 Mobile here are some of the specs

Android 2.3.5

3.2 Capitative Touch Screen

Spreadtrum SC6820 Chip

SP6820a CPU 1GHZ

My Problem Is That I Tried To Flash A Rom Without Backing Up (I Know It's So Stupid Of Me!)

anyway ,, As Expected, It Failed And Now I'm Stuck On A White Screen Without A Bootlogo! ,, All I See Is The Splash Screen "G-Tide" And Then Blank White Screen! :(

I Have No Recovery Because All I Could Find Was For 3.5 and 4 inch Screen And Mine Is 3.2 !

I Only Have Access To Fastboot now

If You Can Help Please Reply!
[General Questions and Answers] aeronium:
Hi all.

I was just wondering if it is possible to show more than four icons in folders on the android desktop?

I sometimes have apps in the folders and have no idea they are in it until I open the folder.

Thanks!
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] imputazz:
Hey everyone i saw some posts at sammobile saying that we were getting the 4.3 update yester day, my i9195 didn't get the update and also i changed the time zone to canada and nothing :$

anyone there got the 4.3?