yashsingh1/xdaforums huggingface dataset:
[8125, K-JAM, P4300, MDA Vario General] hksmr2:
I am trying to install the PDAMobiz Wizard Crossbow_AKU 3 for G3, I have ungraded from cingular 8125 OEM 2.25 to RUU Molski Biz 226102_22610105_022511_WWE. So my question is on the splash screen (boot up) the info are as follows:

IPL 2.26

SPL 2.26

GSM 2.47.11

OS: 1.5.4.2

WHY is that?

In device Info:

ROM Ver 1.5.4.2 WWE

Rom date: 11/08/05

Radio version: 02.47.11

Protocol version: 4.1.13.24

Ext Rom Version: 2.26.10.2 Molski.Biz.

I can't upgrade to the pdamobiz 3.0 rom? I know it is cid unlock I make sure to run the enable rapi every time i did the upgrade reboot then do the upgrade. I don't know why I can't do it. I did the upgrade fine to pdamobiz 3.0rom for my friends mda. 2 of them to be exact. Help Please. I'm going crazy. Thanks
[Galaxy Grand 2 Original Android Development] k2wl:
reserved
[Galaxy Grand 2 Original Android Development] k2wl:
reserved 2
[Galaxy Grand 2 Original Android Development] Mr. 23:
Ohh my god ! It's good news for Grand 2 Family.

Very excited now ! It's really unbelievable.

Thanks [MENTION=943196]k2wl[/MENTION] & whole CM team.
[Galaxy Grand 2 Original Android Development] mithun84:
Bro [MENTION=943196]k2wl[/MENTION], eagerly waiting for ur Complete CM11 for G2............

Hopefully, very soon we will be going to Download the Complete CM11 ROM for our G2..........
[Galaxy Grand 2 Original Android Development] k2wl:
i need boot.img from G7102DDUBNJ2 firmware...

any one having that firmware????
[Galaxy Grand 2 Original Android Development] sbsharma:
https://www.dropbox.com/s/qqzyis3uomlpj8a/boot.img?dl=0
[Galaxy Grand 2 Original Android Development] keshavt:
If i take a nandroid backup before installing this rom then restore it. Will i have any problems? [MENTION=943196]k2wl[/MENTION] ?

Sent using XDA Premium app.
[Galaxy Grand 2 Original Android Development] nar67:
Calls not working ?

Muted
[Galaxy Grand 2 Original Android Development] k2wl:
if you install nandroid back up after installing this you will get back to your stock rom you are using.

@	nar67 read first post ...
[Galaxy Grand 2 Original Android Development] manan001:
hey bro good news for us android Lollipop AOSP source available.
[Galaxy Grand 2 Original Android Development] keshavt:
Please update us about the progress?

Sent using XDA Premium app.
[Galaxy Grand 2 Original Android Development] k2wl:
still stuck with camera hal...until camera hal is resolved we cant move on to next thing....

@manan001 android l is very much big step......even cm team will have hard time supporting their all devices...right now....too many changes ...to code...security...requirements...i dont think we should worry of android l right now....may be after january 2015 when cm code stables we can look into it.
[Galaxy Grand 2 Original Android Development] keshavt:
Some bugs that i would like to inform you. :)

Credits: David Parker

Sent using XDA Premium app.
[Galaxy Grand 2 Original Android Development] keshavt:
Progress update please?

Sent using XDA Premium app.
[Galaxy Grand 2 Original Android Development] jackeagle:
Check This Quote From OP ...Developer will update anything whenever its necessary hence no need of asking the same has it will look like asking ETA itself ...Developer has other works too so just wait if nay updates/progress is needed to be updated then k2wl will update :)
[Galaxy Grand 2 Original Android Development] nar67:
Any new for this rom ?
[Galaxy Grand 2 Original Android Development] white7561:
[MENTION=943196]k2wl[/MENTION] did the gps works very good? If yes. Pls try sending me the gps binary from cm . cause i wanna try. .. Maybe bad gps is at stock driver/binary thx

If you like my post.. Dont say thanks... Click the Thanks Button :)
[Galaxy Grand 2 Original Android Development] nar67:
CM 12 now working with grand i9082

CM 11 not working with my grand sm-7102 ???
[Galaxy Grand 2 Original Android Development] k2wl:
My grand 2 is hard bricked. so i have no device anymore. but i will keep building for grand 2.

thanks.
[Galaxy Grand 2 Original Android Development] Aditya_Butterfly:
Development dead ?
[Galaxy Grand 2 Original Android Development] raj wedhikar:
What else we can expect for our g2 -_-
[Galaxy Grand 2 Original Android Development] Aditya_Butterfly:
We really want this development to be taken forward ! -.-
[Galaxy Grand 2 Original Android Development] Frappy:
READ OP! Just stay patient and wait. I'm pretty sure that k2wl has a lot of other things to do in life :)
[Galaxy Grand 2 Original Android Development] Aditya_Butterfly:
[MENTION=5396524]mukulsoni[/MENTION] i know you are very much busy with the Cm12 project right now. But you too had a cm11 project you couldn't complete. Would you like to help here if you have some free time ?

Would be great. Thanks
[G 2014 Q&A, Help & Troubleshooting] QA Bot:
Q&A for Moto G (2014) Factory Firmware Images

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for Moto G (2014) Factory Firmware Images. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)
[G 2014 Q&A, Help & Troubleshooting] NWKENT:
One can also, boot into "bootloader mode" then "barcodes".. this screen will display the model, mfg date and more..then you'll be sure of which FXZ to flash..

Sent by my 4.4.4_21.11.17_titan

(Unlocked) XT1064 Moto G (2nd Gen.)

http://waynekent.com/page6.html

"Praise Jah" YOU people.!
[G 2014 Q&A, Help & Troubleshooting] vrivr:
Has anyone got the xt1064 21.11.24.titan_niimx.niimx.en.MX? Please, thank you. :D
[G 2014 Q&A, Help & Troubleshooting] Jackie CDP:
Requesting the Firmware from the Mexico's Nextel version of the XT1064.

Here's all the info I have from it.
[G 2014 Q&A, Help & Troubleshooting] sekk:
How to Root

Hi man, if you don't understand portuguese I'm sorry, but I found a tutorial on youtube, that help you how to unlock bootloader, install custom recovery and how to root...

If you want, here is the link:

Unlock bootloader: youtube.com/watch?v=hINYZDaEx3w&list=UUIhmXuqtOQVJCPbh_tXns1g

Root and Custom Recovery: .youtube.com/watch?v=aizVV9aPISk&list=UUIhmXuqtOQVJCPbh_tXns1g

I can't post links here, sorry. I hope that I helped you

Thanks a lot
[G 2014 Q&A, Help & Troubleshooting] rafael_reis:
Moto G (2014) Factory Firmware Image

Hi,

I need the firmware 21.11.24.titan_retbr_ds.retbr.en.BR (KXB21.85.-24), this is the installed in two sim versions in Brazil (XT1068)

Thanks
[G 2014 Q&A, Help & Troubleshooting] feligoni:
Is this the one you need? http://motofirmware.com/files/file/943-retbr-xt1068-444-kxb2185-18-cid12-cfcxmlzip/ . You can browse that web, it has all firmwares
[G 2014 Q&A, Help & Troubleshooting] rafael_reis:
ROM Moto G 2014 Firmware

Hi feligoni.

This showed me that is old, would like to install an equal to the one I have. because I want to unlink the operator TIM Brazil.

I want to leave the ROM operator TIM Brazil, because I have not received the update ROM android 5 lollipop, I'm on android kikat 4.4.4.

picture below the hardware information.
[G 2014 Q&A, Help & Troubleshooting] luca020400:
XT1068

Requesting the Firmware for the XT1068.

Base Band :

MSM8626BP_1032.394.88.00R,

EMEA_DSDS_CUST

System Version :

21.11.23.titan_retaildsds.reatildsdsall.en.03

reteu

Build Number :

KXB21.85-23

Thanks ;)

Found it ;)
[G 2014 Q&A, Help & Troubleshooting] EJSMiranda:
I need your help guys :S

Requesting the Firmware from the Mexico's Retail version of the XT1064.

Here's all the info I have from it

Quote:

Base Band

MSM8626BP_1032.394.8800R,

NIIBC4MX_CUST

Core

3.4.42-g915e599

hudsoncm@ilclbld34 #1

Thu Sep 4 16:31:26 CDT 2014

System Version

21.11.24.titan_niimx.niimx.en.mx niimx

Build Number

KXB21.85-24

Please! :)
[G 2014 Q&A, Help & Troubleshooting] Transdimensionalotaku:
Anyone have this one?

Requesting stock firmware for the XT1068

I need this exact same ROM, it's what my phone had by default and now I'm afraid that I won't get the OTAs if it's not that specific version... (I've sideloaded KXB21.85-27 and rooted it)

Info I have :

Base Band :

MSM8626BP_1032.394.88.00R,

EMEA_DSDS_CUST

System Version :

21.11.23.titan_retaildsds.reatildsdsall.en.03

reteu

Build Number :

KXB21.85-23
[G 2014 Q&A, Help & Troubleshooting] lath93:
what shud i do?

i flashed a 5.0.2 rom on my motog(xt1068) than while searching for stock roms i installed same factory image(assuming that was a rom i downloaded but while installing i come to now that was a factory image) with build no 85.27... and as lollipop is now released in india to moto g2014(xt1068) n moto g 2013, but i have not been recevd update, shud i wait or again root my device n flash a new rom and please do share a stock rom link am new to these things so bit confused.... thank you
[G 2014 Q&A, Help & Troubleshooting] estero2002:
Latam XT1068

Hello everyone,

Do you know if it would be safe to flash european/international stock image for XT1068 (such as RETAILDSDSALL_XT1068_4.4.4_KXB21.85-27_cid7_CFC_SVC) into my latinamerican XT1068?

Comp Version: KXB21.85-24

Sys Version: 21.11.24.titan_retla_ds.retla.en.01 retla

Also, can I flash the lollipop OTA images that are around in the forum?

Thanks in advance,

Steve.
[G 2014 Q&A, Help & Troubleshooting] reefuge:
its in my signature (green) firmware 'b'

---------- Post added at 04:59 PM ---------- Previous post was at 04:50 PM ----------

any xt1068 version can be flashed to any xt1068 but its, if the GSM bands work in your country - if you can find or still have your latinamerican firmware to put back just in case it doesnt work-

i have flashed brazil to UK phone boots but no sims work. put eu/uk back works fine
[G 2014 Q&A, Help & Troubleshooting] aiwa78:
XT1032 firmware from Greece

Hi,

my XT1032 moto g was stuck in boot, so I used RootJunky script to unbrick it. It was partly succesfull, because although the device came back to life it does not recognize the SIM card.

My assumption is that this happens because rootjunky's script installs US firmware but I live in Greece. Do you think this is the reason? And also could you recommend a firmware for Greece?
[G 2014 Q&A, Help & Troubleshooting] doppelhelix:
Wrong forum. This forum is for Moto G 2014 (XT106x). Better go to http://xdaforums.com/moto-g
[G 2014 Q&A, Help & Troubleshooting] Harsh.gundecha:
i also need that

just want to ask you where you found it as i too want it.

is it indian version?

i am on cm12 and i wish to have stock images but i dont remember exasctly which version i had as it was similar to that of you, so if you can provide live link it would be helpful to me

thank you :D
[Android Apps and Games] LittleBizkit:
FUT 15 Cards​

Are you a big fan of the FIFA 15 game and the Ultimate Team (FUT) mode? If the answer is yes, this app is for you!

This app helps you to find the best players for your team!

FUT 15 Cards is the only app which helps you to find the best cards which match your needs. In this app you will find many functions which make it easier for you to have the best overview in the ultimate team mode. This app includes all skills of all players which you can look for.

This following features are implementet in this app:

- Search for players per name

- Search for players by filters

- Tax calculator

- All level players cards like gold, silver and bronze

- All skills of all players

- All leagues, nations and clubs

To download the app, search for FUT 15 Cards or com.sudstud.cards15.database

Thank you for every download and feedback
[Moto G Q&A, Help & Troubleshooting] QA Bot:
[Q&A] [Ubuntu Touch - Utopic][PORT]STOPED][Test-BUILD][2014-08-27] Ubuntu Touch for

Q&A for [Ubuntu Touch - Utopic][PORT]STOPED][Test-BUILD][2014-08-27] Ubuntu Touch for falcon

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for [Ubuntu Touch - Utopic][PORT]STOPED][Test-BUILD][2014-08-27] Ubuntu Touch for falcon. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)
[Moto G Q&A, Help & Troubleshooting] vivekj:
Is there any way to flash the boot.img and system.img using multirom. I found about multirom installer (*.mrom files). But didn't had any luck with it.
[Moto G Q&A, Help & Troubleshooting] the_MUKe:
I tried to compile the Android pieces on my own but I get an error with libmake_f2fs_intermediates:

make: *** No rule to make target `<.....>/out/target/product/falcon/obj/STATIC_LIBRARIES/libmake_f2fs_intermediates/export_includes', needed by `<.....>/out/target/product/falcon/obj/EXECUTABLES/recovery_intermediates/import_includes'. Stop.

I checked out the Ubuntu Touch code using Canonical's manifest. I did not use h2o64's manifest.

In my local manifest I added the CyanogenMod projects for falcon, as well as dependencies:

<?xml version="1.0" encoding="UTF-8"?>

<manifest>

<remote fetch="git://github.com/" name="github" />

<project name="cyanogenmod/android_kernel_motorola_msm8226" path="kernel/motorola/msm8226" remote="github" revision="cm-11.0" />

<project name="cyanogenmod/android_device_motorola_falcon" path="device/motorola/falcon" remote="github" revision="cm-11.0" />

<project name="cyanogenmod/android_device_motorola_msm8226-common" path="device/motorola/msm8226-common" remote="github" revision="cm-11.0" />

<project name="cyanogenmod/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-11.0" />

<project name="cyanogenmod/android_hardware_qcom_fm" path="hardware/qcom/fm" remote="github" revision="cm-11.0" />

<remove-project name="aosp/platform/hardware/qcom/display" />

<project name="cyanogenmod/android_hardware_qcom_display-caf-new" path="hardware/qcom/display-caf-new" remote="github" revision="cm-11.0" />

<remove-project name="aosp/platform/hardware/qcom/media" />

<project name="cyanogenmod/android_hardware_qcom_media-caf-new" path="hardware/qcom/media-caf-new" remote="github" revision="cm-11.0" />

</manifest>

Apart from that I did not make any changes. Just trying to get the sources compiled.

Can somebody tell me why I get this error and how to fix it?
[Moto G Q&A, Help & Troubleshooting] cauanboss:
The system is restarting all the time

I followed all the steps of the fórum and the system is restarting all the time
[Moto G Q&A, Help & Troubleshooting] ShinobiX9X:
multirom

is it possible to install the ubuntu touch image via multirom manually?
[Moto G Q&A, Help & Troubleshooting] the_MUKe:
Errors during build

I have finished downloading the sources including your local manifest. Now I am trying to build and will report some errors here. Once I have a successful build, I am happy to share logs (if accessible) and help debugging.

I directly encountered this error:

build/core/base_rules.mk:134: *** hardware/qcom/display/msm8x26/liblight: MODULE.TARGET.SHARED_LIBRARIES.lights.msm8226 already defined by device/motorola/falcon/liblight. Stop.

So I renamed old module to lights.msm8226.old

hardware/qcom/display/msm8x26/liblight/Android.mk:160:

LOCAL_MODULE := lights.$(TARGET_BOARD_PLATFORM).old

No the build process stops after only a few lines with:

make: *** No rule to make target `[...]/Ubuntu_Touch/out/target/product/falcon/kernel', needed by `prebuilt'. Stop.

---------- Post added at 07:50 PM ---------- Previous post was at 07:40 PM ----------

I also noticed that not all the dependent projects are added in the local manifest.

android_device_motorola_falcon

depends on

android_device_motorola_msm8226-common

depends on

android_device_qcom_common

android_kernel_motorola_msm8226

android_hardware_qcom_fm

android_hardware_qcom_display-caf-new

android_hardware_qcom_media-caf-new

Will add the missing ones and try to build again.

Edit: Just saw that you included the files already in device/motorola/falcon.
[Moto G Q&A, Help & Troubleshooting] h2o64:
I'm fixing things guys :D

Wait :p

(I'll tell here when the major issues (building issues) are fixed

---------- Post added at 11:35 AM ---------- Previous post was at 11:27 AM ----------

You forgot to add "CyanogenMod/android_external_f2fs-tools" revison cm-11.0

And include it in main.mk
[Moto G Q&A, Help & Troubleshooting] omniaholic:
KMSG log file

I hope it's useful.

Logfile is attached.

thx
[Moto G Q&A, Help & Troubleshooting] h2o64:
The last build is useless and outdated

But thank you for sending. I'll notificate you when a new build will come
[Moto G Q&A, Help & Troubleshooting] the_MUKe:
Update on build process

First thanks for the responses. Indeed I forgot to add the subdir in main.mk before. However, now I making sure that all subdirs are included...

Just to inform you about what I have done so far. I started building based on the phablet repo and added my own local manifest (attached).

added device/motorola/falcon and dependencies

copied vendor/motorola from existing (and recent) CyanogenMod

added subdirs in build/core/main.mk

added external/f2fs-tools

removed APKs and JARs from vendor/motorola/msm8226-common/proprietary

replaced hardware/qcom/keymaster with CyanogenMod version (some error with original keymaster)

replaced all hardware/qcom project with CyanogenMod versions (helpful?)

Workaround: deleted gps from device/motorola/msm8226-common (libnativehelper would be required, plus several undeclared constants)

Workaround: force include of all subdirs in device/qcom/common/Android.mk (dtbToolCM is required)

Workaround: deleted power in device/qcom/common (some undeclared constants)

Now the build process runs through but there are errors with creating the recovery image and the boot image.

However, I noticed that h2o64 made some changes to android/system/core, in particular mkbootimg. So I will see if I can also use the CyanogenMod version here.

If anyone has better solutions for these Workaround items, please let me know.
[Moto G Q&A, Help & Troubleshooting] h2o64:
Changing hardware/qcom was a BIG mistake!

Revert it and try to change things line by line.

Anyway! Good job!
[Moto G Q&A, Help & Troubleshooting] the_MUKe:
Accessing the boot log...

[MENTION=4792450]h2o64[/MENTION]: Great to hear that you made progress!

In my repo I managed to finish the build process. I flashed the boot.img and ran the rootstock-touch-install script without errors. I needed to raise the size of the ext4fs: make_ext4fs -l 256M $WORKDIR/system.img $TMPMOUNT

The 256M are just a value I put in there, no idea which value would be best.

Unfortunately, when booting the device, the screen remains at the Motorola logo.

I bootet into recovery and took the dmesg output. Not sure whether this also includes the previous boot log or only the log of booting into recovery...

In the Ubuntu Wiki in the Deprecated Porting Guide they suggest to look at /proc/last_kmsg

In the Debug section they also recommend to pass command line arguments to the kernel:

If you encounter initrd issues while booting you can add to your kernel boot arguments the following line "break=top"...

This should then pause the boot process and open an adb shell.

But in which file can I set the kernel arguments? There are several config files in the kernel directory...

Well, as soon as h2o64 has finished updating his repo, I will try with his local manifest. And then try to provide boot logs, etc.
[Moto G Q&A, Help & Troubleshooting] h2o64:
You made a very impressive work :)

Last_kmsg is the best we can take... The kernel patch... Hmm... It's not fit me.

To be honest I'm kind of lazy xD

I need to redo the hardware qcom part..

Do you have hangout? We can talk about it with more serious details?
[Moto G Q&A, Help & Troubleshooting] the_MUKe:
hardware/qcom projects

No, I don't use Hangouts. Maybe IRC might do?

But I am also fine to post the (bigger) issues here. Then also somebody else could possibly find a solution.

The hardware/qcom part seems to be indeed a bit tricky.

When using the projects from Ubuntu Touch repo, eventually some kernel headers cannot be found, e.g. a file inside hardware/qcom/display/... includes "linux/msm_ion.h" which cannot be found.

I tried manually setting the kernel_includes in hardware/qcom/display/msm8x26/common.mk: kernel_includes := kernel/motorola/msm8226/include

But this only leads to multiple C++ errors like: narrowing conversion of 'dst->copybit_image_t::w' from 'const uint32_t {aka const unsigned int}' to 'int' inside { } is ill-formed in C++11 [-Werror=narrowing]

Also the liblight module is duplicated (but one can easily be renamed).

These problems do not occur when using the corresponding projects from CyanogenMod instead.

I am still undecided whether to stick to the original Ubuntu Touch projects for hardware/qcom or better go consistently with all the hardware/qcom projects from CyanogenMod. Not sure which other interdependencies exist there...
[Moto G Q&A, Help & Troubleshooting] h2o64:
I did fix it on the previous release. I'll do it again.
[Moto G Q&A, Help & Troubleshooting] h2o64:
I start working back on it.

Check my github
[Moto G Q&A, Help & Troubleshooting] the_MUKe:
Will download your .img files, flash them and provide my last_kmsg log.

Will probably also build it using your manifest - just to check if build goes through also on my machine (Ubuntu 14.04 64-bit).

I noticed in the recent log provided by Awesomeslayerg that the init process could not find a system partition:

[ 4.326129,1] initrd: Couldn't find a system partition.

It's towards the end of the log. There were a few other errors but this might be a critical one?

I also had this error with my previous build (when using all hardware/qcom projects from CyanogenMod).

And did you make any changes in the rootstock-touch-install script?
[Moto G Q&A, Help & Troubleshooting] ADr0n:
It will work on 5.0.1 lollipop bootloader??
[Moto G Q&A, Help & Troubleshooting] the_MUKe:
Results with provided .img files

The recovery you provided is not working in my case - I get a blank screen. So I flashed back to TWRP.

I actually had the Ubuntu recovery (a reduced CWM with Ubuntu Logo) working when using all hardware/qcom projects from CyanogenMod.

I also flashed your boot.img and used the rootstock-touch-install script to get the system.img together with vivid files onto the phone. The script finished very fast but all steps were completed.

When booting up, the phone gets stuck while the Motorola logo is still showing.

So I rebooted into recovery and obtained the last_kmsg log (attached).
[Moto G Q&A, Help & Troubleshooting] h2o64:
Very nice.

Yeah... My hardware display & media are weirdly inconsistent... I'll redo them

Thanks for your report!

(please, speak on the main thread ;))

---------- Post added at 12:03 AM ---------- Previous post was at 12:03 AM ----------

Nope
[Moto G Q&A, Help & Troubleshooting] brainwave92:
Dual Boot Android on Moto G

Hi Guys,

Would you know what I can do, to make ubuntu dual boot on moto g? I tried looking at the dual boot scrit that is found on ubuntu site. I can edit it accordingly but I do not know how to place the ubuntu recovery, image files etc. and make something boot it up from there. Any help?
[Moto G Q&A, Help & Troubleshooting] h2o64:
The rom doesn't boot yet
[Moto G Q&A, Help & Troubleshooting] the_MUKe:
Just need to get my post count above 10 first. But working on it little by little. :D
[Moto G Q&A, Help & Troubleshooting] h2o64:
See the main thread quickly ^^

I did my huge daily progress update.

There won't be any build today after all.

First. We need to adapt audio-hal