yashsingh1/xdaforums huggingface dataset:
[Moto G Q&A, Help & Troubleshooting] redbull93:
I've got the same problem after trying to convert my Moto G to Google Play Edition (worked fine up to 4.4.4), then I wanted to install Android 5.0.1 OTA and ended in the Reboot Loop.

I followed the first link and was able to get 4.4.4 working again. Then I tried to continue with the second link to get the chance to update later on 5.0.1, but everytime I wanted to run the command "mfastboot flash system system.img_sparsechunk.0" my Moto G in Fastboot alerts "File Size too large". Is there a way to get an 4.4.4 which enables me OTA Update to 5.0.1?
[Moto G Q&A, Help & Troubleshooting] BobDiaz:
Wel... The answers:

1) Yes. You'll loose all your user data. One of the steps during the installation of any room is erase all the cache partitions and the userdata. That way, you can prevent any compatibility issues.

2) You phone will "forget everything about it's past", and will "think" that it is Brazilian now. If you don't like it, try downloading an ADB compatible DE rom. But, in my opinion, the Lollipop is way better than the Kit Kat. Unless you need the Xposed Modules.

Cheers!

Merry Christmas! :laugh:

---------- Post added at 01:30 AM ---------- Previous post was at 01:19 AM ----------

Did you did everything like said in the tutorial? Well, if yes, I suggest trying to do as the first link before. That way, all the partition table will be in the correct place.

Give us a feedback!

Cheers!

:)
[Moto G Q&A, Help & Troubleshooting] stechiocca:
[MENTION=6266181]BobDiaz[/MENTION] do you think i should also erase dalvik cache? because i do everything step by step but it does remain in bootloop with the google logo ....
[Moto G Q&A, Help & Troubleshooting] BobDiaz:
Let me just understand:

Did you try the first tutorial again or you are in the second for the first time?

You ALWAYS need to erase your cache partitions. Doing a clean installation always prevent bugs and incompatibility issues.

I'll ask for photos again. Show me, if possible, the step-by-step; Or upload a video on youtube.

Cheers!
[Moto G Q&A, Help & Troubleshooting] redbull93:
Thanks for your answer! I tried to do everything as described, the first tutorial worked fine. Then I wanted to flash the Brazilian kitkat image image with fastboot like described in the second tutorial. While flashing the phone dropped the error notice "Image File Size too Large" while flashing system.img_sparsechunk.0, system.img_sparsechunk.1 and system.img_sparsechunk.2. I was able to finish the further steps but after rebooting the bootloader the Moto G was back in Boot Loop.

Can I do the second part of this tutorial (transfering moto g brazilian update to the phone and apply the update from sd card) also with the image of the first tutorial? How does this work?
[Moto G Q&A, Help & Troubleshooting] BobDiaz:
Actually, you can't.

You can only apply UPDATES to the rom it was meant to be. You cannot apply an Lollipop Update made to an 4.4.4 Retail-BR to an GPE, even if it was an 4.4.4. It will bug the partition table, leading your device to bootloop.

If you've already tried to do as the second tutorial said more than one time, following all the steps, and it still is in bootloop, i recommend you to try searching for a alternative.

Give us the feedback anyway!

Cheers!
[Moto G Q&A, Help & Troubleshooting] redbull93:
Here are some pictures of the error that occurs during flashing Kitkat 4.4.4 like it is described in the second tutorial.

Before, I launched the first tutorial and got a running 4.4.4 on my Moto G.

Image 1: State after entering "mfastboot flash system system.img_sparsechunk.0"

Image 2: Feedback on the Windows console after entering "mfastboot flash system system.img_sparsechunk.0"

Image 3: State after entering the last "flash system .. " command
[Moto G Q&A, Help & Troubleshooting] BobDiaz:
You may need to flash gpt.bin from 4.4.4 (it is in the 4.4.4 flashable). This will create a new correctly sized partition table.

Also, make sure you are using the mfastboot to flash (a.k.a motorola fastboot) and not the Google fastboot.

This is probably a partition table error.

Give us the feedback!

=]

________________________________________

I've seen this in other topic:

http://xdaforums.com/moto-g/general/guide-restore-moto-firmware-gpe-t2914884
[Moto G Q&A, Help & Troubleshooting] stechiocca:
I can't find the gpt.bin file, probably this is why i'm getting "image is too large" error... can you please explain to where i can find it?? :)
[Moto G Q&A, Help & Troubleshooting] BobDiaz:
I could not upload here in XDA the gpt.bin that I've used.

Try catching the one that comes with any ADB flashable rom (it is called "gpt.bin").

Try the stock from your country.
[Moto G Q&A, Help & Troubleshooting] stechiocca:
hey, how are you? i'm really happy because it finally worked! I just had to "mfastboot flash partition gpt.bin" to make it works and i didn't get the "image is too large" problem... now i'll do the second part of the second guide ;) hope it will work!! thank you a lot [MENTION=6266181]BobDiaz[/MENTION]
[Moto G Q&A, Help & Troubleshooting] BobDiaz:
Excellent.

Try the other tutorial and tell me how did it go.
[Moto G Q&A, Help & Troubleshooting] stechiocca:
[MENTION=6266181]BobDiaz[/MENTION] Now i'm currently running correctly lollipop 5.0 brazil en BR, am i able to install a custom recovery and flash any rom whenever i want?
[Moto G Q&A, Help & Troubleshooting] redbull93:
I damaged finally the bootloader, now my device is hard-bricked :( have to wait until Motorola publishes the official Lolipop update ...

I tried another time to flash a 4.4.2 Google Play Edition and after the OTA Update to 4.4.4 my device wasn't able to boot any more.

I will follow this guide: http://xdaforums.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
[Moto G Q&A, Help & Troubleshooting] BobDiaz:
NICE!!!

About the Custom Recovery, yes, you can. I am using the CM Touch available in this subsection of the forum.

About the rom, I don't know, but probably yes. You just need to flash the gpt.bin from a 4.x.x before (but I can't say exactly, since I didn't try it).

Happy holidays!

=]

---------- Post added at 01:25 PM ---------- Previous post was at 01:23 PM ----------

Hard bricked?

Please, post a photo.

Can you get in the Recovery or Bootloader mode?
[Moto G Q&A, Help & Troubleshooting] redbull93:
Not bootable any more, got only black screen ... no Bootloader or Recovery Mode. The only sign of life is that my computer recognizes the device as "qhsusb_bulk". So no help for me until Motorola releases the official Update ...
[Moto G Q&A, Help & Troubleshooting] Petrovski80:
How is the official update going to help if you cannot boot into the bootloader?
[Moto G Q&A, Help & Troubleshooting] redbull93:
When the official update is released, this tutorial will be updated and I will be able to repair my bootloader, at least I hope so ;)

http://xdaforums.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
[Moto G Q&A, Help & Troubleshooting] Petrovski80:
You can follow that guide now, no need to wait for lollipop rom.
[Moto 360] Cr4z33:
I don't want to drain my 360 battery therefore usually when I wear a coat I disable the tilt function, but I wonder if I should disable/enable anything else to prevent the screen from turning on automatically or by accidentally tapping it? :confused:

Sent from my Samsung Galaxy Tab Pro 10.1
[Moto 360] deadgiveaway:
Theatre mode is what i like to use ....
[Moto 360] chaco81:
i have started to use theater mode also

my leather coat will register touches just as if i was touching it...
[Moto 360] 640k:
having a mostly nylon/fleece lined coat i haven't had this issue. haven't even considered leather causing this problem.
[Moto 360] Darkne0:
Just enable Coat Mode.
[Moto 360] gilbertbold:
Lol
[Moto 360] slaydog:
I wish the watch had a proximity sensor, so the screen would automatically turn on when you pull your sleeve back - and stay off when covered...
[Moto 360] jutley:
I find the watch last ages in aero plane mode when you need to connect to phone when driving then enable the aeroplane mode but if you want really good battery life do aero plane mode
[Nexus 5 Q&A, Help & Troubleshooting] aspico:
Hi, after i flashed 5.0.1 my hotspot doesn't work, when i turn it on it goes off and on, after that my wifi wont turn on, i have to reboot the device so i can use wifi again. Any solutions? Thanks
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Temasek's UNOFFICIAL CM13.0 BUILDS

I will attempt to get builds out as soon as Temasek releases a new version, however due to commitments i may miss a release. I will not upload a ROM until i have flashed it myself. Please report any bugs or issues that you see; when applicable, Thank you.

DISCLAIMER

/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
*/

This thread is currently under maintenance. Should there be any inaccurate information, please PM me. Images and formatting will be handled at a future date.

...not ready yet

I use my TWRP version linked in Second post

Clean Install

1. Download the appropriate ROM using links provide in the second post.

2. Download the appropriate GApps following the links in the second post.

3. Back up any and all important data.

5. WIPE DALVIK/CACHE/DATA/FACTORY RESET.

6. WIPE SYSTEM. <<-- You don't have to do this unless you want too

7. Flash the ROM in recovery.

7.1. DO NOT FIX PERMISSIONS AFTER FLASHING, doing so will cause a bootloop.

8. Flash the GApps.

9. Reboot Device.

Dirty Flash

1. Download the appropriate ROM using links provide in the second post.

2. WIPE CACHE/DALVIK. (I find wiping /SYSTEM can stop some issues with play store F/C’s)

3. Install the zip from recovery.

4. Install GApps (ensure that they are from the same build, otherwise you must do a clean installation when using a newer GApps package)

3.1. DO NOT FIX PERMISSIONS AFTER FLASHING, doing so will cause a bootloop.

5. Reboot Device.

More:

Screenshot 2

screenshot 3

probably others i havn't found as yet

FAQ: "Q: Have problems connecting to your Wi-Fi router? -> A: Make sure you have selected the correct region/country code in the advanced wi-fi settings!"

[MENTION=3463426]RaymanFX[/MENTION] - without him there would be no original trees for our device, simple.

[MENTION=3594812]ShevT[/MENTION] - without him there would be no cm-13.0 for our device, simple.

[MENTION=2332422]temasek[/MENTION]

[MENTION=4898097]arter97[/MENTION]

[MENTION=631273]Chainfire[/MENTION]

[MENTION=4240943]benand[/MENTION] - for highlighting a dam error that i had missed for over a month, thanks

CM Team]

Source

Joshndroid Source

Note 10.1 Device Tree

Note 10.1 Kernel

Note 10.1 Vendor Files

Temasek

Rom Source

Changelogs

Temasek Github Changelog
​
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Shared Google Drive Device Folder (have Rom shared directly to your Google Drive Folder)

see here for further - http://xdaforums.com/showpost.php?p=65559375&postcount=2252

Basketbuild Download - Backup Download Location (OR for those not in Google Shares)

https://basketbuild.com/devs/Joshndroid/Temasek Roms/lt03wifi

GApps - 6.0 GApps Package

http://opengapps.org/ (select ARM & 6.0)

I have be extremely pleased with Open Gapps and you can even download daily packages, I have tried the micro, mini and nano packages with good success so far - All credit to their team and original thread source can be found here for important information and updates - http://xdaforums.com/android/software/pa-gapps-continuation-t3098071

SuperSU for flashing via recovery - Credit to [MENTION=631273]Chainfire[/MENTION]

http://download.chainfire.eu/supersu
[Galaxy Note 10.1 (2014 Edition) Android Developmen] lsherif:
Any plans to support P601 variant, only Phone calls & 3G to be activated or added.

Much appreciated if you got the time to add this to your rom building, :)
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Unfortunately not. Firstly because I don't have the device. Secondly I don't have the skill set to create a working device tree from relative scratch. Lastly Samsung suck for exynos based devices, sorry.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] lsherif:
Thought as long as they have the same Hardware , same tree would be applied and just adding a modem to it.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] temasek:
Lol

Not so simple.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] lsherif:
I know that for sure it is not that simple, but if you got the time to support this , would be my pleasure to test :)
[Galaxy Note 10.1 (2014 Edition) Android Developmen] donshelf:
need p601

p601 support please all devs i beg for this :cowboy:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] jeanmarce:
thank,merci

hello :D thanks you for this new rom
[Galaxy Note 10.1 (2014 Edition) Android Developmen] SamsungGalaxySamsung:
Nice job!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] jasonm253:
P605/P607 please someone. A realible working one!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] davitox87:
I'm using temaseks build for my note 3 and love it. Is there anyway to get it ported for the 605 lte model? I'd try but I have no idea how to build/port roms
[Galaxy Note 10.1 (2014 Edition) Android Developmen] jasonm253:
Running it on my S5 and I love it. P605 or P607 for me would be lovely.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] mohamadreza33:
after I tested...

I have this rom installed on my P601...

Not workings:

Camera

Flash light

Mobile Data and Sim Card

SuperSU

And some more...

But there is some thing that i love this rom... And it's because VPN connections works well

And it doesn't become so hot.. And will not die anymore... Nice work..:good::good::o
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Well at least you know it is not for your device? lol...

I always flash latest version of supersu and never rely on inbuilt su... I believe it may be addressed in temasek source though

New build tomorrow being a shift worker sucks sometimes.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] temasek:
SuperSU built-in from next build.

I might even totally remove Superuser.

BTW I'm a shift worker too and I spin builds like nobody business.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] perozu:
How is battery life with this one? And stylus functionalities? Not that I use it... ever. Just wondering how close it is getting.

Since it's tema's name in the name of the rom, I'm considering tearing my warranty into pieces:p

Any additional encouragements (or discouragements)?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Yeah I have been reading github for additions

It's just the lack of time, a fresh cleaned out folder takes about an hour to build with lollipop no matter device. Takes 4 minutes with a dirty out folder. Comparison kitkat took 36 minutes with a fresh out folder and about 16 for a dirty. I want to be able to eventually build for about 4 or 5 devices so Just grabbed a new charger for my older i7 qosmio laptop... Gonna throw a big ssd in it coupled with a 1tb hdd and use it as a dedicated build box, rather burn that out churning builds than my clevo beast..

I'm getting good battery life as for stylus I'll try my note 3 stylus and report back
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Stylus works as it should the little mouse arrow shows and can even move the pointer around without actually touching the screen
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Build v5.4 is now live.. Theme chooser is there for cm12 give thanks and enjoy cheers
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Hi Josh!

Updated to new 5.4 release but when I try to install themes over playstore the installation failed. If I try to install over the themes chooser link to plays than it installs fine, but the themes are not visible in theme chooser.

The only theme showing is GreatFreedomTheme. Lol

The rest works like ever, fast and snappy!

Thanks!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Cm11 themes are not going to work on cm12... They were made with different app different status bars all sorts of things cm12 theme chooser is like a whole reboot on the original theme chooser
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Build v5.5 is now up... not going to update the thread title on very minor

New addition is the expanded mode

For reference, while I'm not at work I can get updates out quicker but when I'm on work days I may get only 1 release or miss a release altogether (only if it's minor update)
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Hi Josh!

5.5 works so far normal, but in quick-settings_select-and-order the operation of the tiles slipped one row to the top. I do not know if it's because I dirty flashed the rom or if it's a bug.

Wipe caches have no effect and fix permissions I have not tried, because of the known error.

New expanded mode for location tile works great.

Big thanks!

And as for future updates I would say, they come when they come!

We all knows it's only your hobby and you have a real life and family to care!:good:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
I dont understand what u talking about with the quick settings move
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
I mean, if I want to add a new tile normal is press the +tile, but it not work.

I must press the tile a row higher, in my case I have to press screen cast tile than pop-up the selection field for more tiles.

Operation is simply a row slipped up.

See screenshot below!

But if you ask what I mean, then the error seems to be only with me and I need a fresh install!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Ah yeah I see what you mean.. It doesn't do it on my note 3 maybe the update I'm cooking it is fixed never noticed it before as I just leave the stock amount of tiles on it
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Maybe [MENTION=2332422]temasek[/MENTION] may know what it is as he may face the same drama when porting to his nexus7 3g.. Only does it in the quick settings screen

Build v5.6 is the same and is uploading to basketbuild right now still couple hours to go
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Yeah!

I know this issue also from my S3 last year or so! Is not a big thing and I'm with you that Tema knows what to do.

Indeed, thanks for v5.6:good:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Build v5.6 is online on basketbuild.. Download and enjoy cheers
[Galaxy Note 10.1 (2014 Edition) Android Developmen] dronarg:
Thank you. I installed it. First time I use this Rom and it works very well. Two things I have noticed :

- Camera is broken its written on 1st page ;)

- I cant use another keyboard. Settings FC when I try to change.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] temasek:
Keyboard settings fc trigged due to high sensitivity support. Will fix the issue by next build. It's a cm bug.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
v5.7 uploading to basketbuild
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Build V5.7 is now online... give thanks and enjoy... cheers
[Galaxy Note 10.1 (2014 Edition) Android Developmen] pentiger:
We give thanks!

Please work on the camera, no hangouts, no skype at this moment.

Thank you.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Hi Pentinger!

For a working camera we have to wait untill RaymanFX have fixed it.

CM12 is still in beta so have a bit patient!

You can switch back to stock CM12/build from 12/05 to get a working cam but I would recommend to wait, because Rayman comes closer to a solution!:good:

@ Josh!

Is High Touch Sensitivity enabled by default or is there a settings entry that I have not found yet?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] pentiger:
.

This icon is not theamable.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Unless someone makes a icon pack with it included it is going to miss out
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Update coming in a couple hours
[Galaxy Note 10.1 (2014 Edition) Android Developmen] TruThug407:
No issues with sdcard here either besides da camera not working I think its running smooth even with latest xposed installed, keep it up josh u a beast do wat u do I know you'll get a solid build running soon....:good::cool:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] enotar:
I like the build very much. Thank you for this. Two issues so far: bsplayer fc and tablet reboot and you cant delete browser history.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Thanks, Juggaknot77!

seems I need a pc to safe my data and format my sdcard! I'm back home tonight and will report later if it's working!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
New 20160207 build is up on basketbuild

https://s.basketbuild.com/filedl/devs?dev=Joshndroid&dl=Joshndroid/Temasek
[Galaxy Note 10.1 (2014 Edition) Android Developmen] soza971:
Not working

Envoyé de mon SM-P600 en utilisant Tapatalk
[Galaxy Note 10.1 (2014 Edition) Android Developmen] enotar:
Downloading right now.

What s the changelog?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Hey Soza971,

Take it from the first page, post 2!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Stogie87:
Correct Link: https://s.basketbuild.com/devs/Joshndroid/Temasek Roms/cm-13.0-testing/lt03wifi
[Galaxy Note 10.1 (2014 Edition) Android Developmen] juggaknot77:
New build is smooth as butter, thanks!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Latest test-build works great here!

New build dirty flashed with latest open gapps and all is very well! Fast and snappy how it should be! :good:

My sdcard issues are also solved.

Have another sdcard fitted and formatted, then put back the old card in, and the issues are gone.:D

Update:

Settings>buttons>pa pie control>pie color settings force close when I try to change something. Apart from that the rom works very well and rock stable!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Stogie87:
I also tested the new build, but like on every other AOSP Rom i have massive sound problems. It is crazy and everything startet after i updatet for the first time to TW 5.1.1. Now i have sound problems even with the older Temasek builds and the official CM 12.1 builds. Only the Stock Rom builds working without any issue on my device. If i don't find a fix for this problem i have to stay on stock rom... forever... pleaase noooo!!!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] enotar:
Can you clean browser history?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Hi Enotar,

nope! No way to delete browser history!

What's happening?

Checks someone how many porns you look?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Sy Borg:
At what stage should this new version have it's own thread?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Probably will just rename thread as cm12.1 is no longer maintained
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DirkStorck:
Flashed new build. Everything is working fine ??

Thank you
[Galaxy Note 10.1 (2014 Edition) Android Developmen] enotar:
No but I think there are other problems with permissions and memory access. I dont think this is related to CM 13 as I have it on my S4 and all is fine.

Correction: This is a CM 13 issue......