yashsingh1/xdaforums huggingface dataset:
[Moto G Android Development] coloxim:
Yeah....of course ..is the first thing...

I've tryed to flash recovery on windows and Mac....same result...the phone print a pink phrase (after the yellow ones) the there is no memory... I've to try a full reset?

Inviato dal mio XT1032 utilizzando Tapatalk
[Moto G Android Development] krypto16:
Mine said the partition size was a mismatch but I still had recovery on the phone and it worked. Not sure what to try as I had a different result. Have you tried going to bootloader and booting into recovery? What happens?
[Moto G Android Development] danger2u:
flashed not working

i got bootloader warning i press power and volume up but the phone not goes into recovery

some help please
[Moto G Android Development] krypto16:
Plug phone into computer and accept the warning on the phone, open command prompt in your working ADB directory, type command 'ADB reboot recovery' and tell me what happens.

Volume up plus power is not how you boot into recovery...you have to volume down plus powerwhich boots into bootloader, then select recovery from there
[Moto G Android Development] danger2u:
device not found
[Moto G Android Development] denzel09:
You have drivers problem. Reinstall all. Reinstall adb and fastboot.
[Moto G Android Development] krypto16:
This is a setup issue and has nothing to do with the recovery or anything else. Are you sure you have the drivers loaded for that phone? you have accepted the warning on the phone when you plugged into the computer (you have to agree to let that computer access your phone). Do you have ADB debugging checked in Developer settings? I would assume yes to these questions as you said you have already tried to push the recovery to the phone but if all of these are true then I have no idea how to help any further without having your phone in hand.
[Moto G Android Development] danger2u:
working great

my mistake

my root wasn t doing well

now i put cwmode and it s works

4.2.2. i coming :))

thanks for help
[Moto G Android Development] coloxim:
I've that message... But when I try to enter in recovery my phone reboot in android...

Or sometimes I've black screen...

Inviato dal mio XT1032 utilizzando Tapatalk
[Moto G Android Development] krypto16:
Try through ADB, this is the only way I can get it to work for me...If you flashed successfully and got that message you should be able to connect phone to computer and ADB Reboot Recovery and boot into TWRP. If that does not work, then try pushing the recovery again.

of course i am rooted so I use extended boot menu which gives reboot to recovery option and this too works. I am assuming you are rooted so download an app called quickboot from the play store and grant SU permissions select the reboot recovery option and it will reboot into recovery.
[Moto G Android Development] coloxim:
OK...when I'm at home I'll try...

When I'm in fastboot after flashed the recovery I've type adb reboot recovery?

Inviato dal mio XT1032 utilizzando Tapatalk
[Moto G Android Development] krypto16:
Nope, flash the recovery in fastboot then just turn your phone on normally, go to Developer settings and make sure USB debugging is checked, connect to a computer, accept the message on the phone screen to allow access from computer, open command prompt in your ADB working directory and type ADB Reboot recovery...this should reboot the phone into recovery. Are you rooted already? If so, you can skip all those steps by downloading that quickboot app and using that.
[Moto G Android Development] coloxim:
i'm not rooted.....i'm in recovery now....but it is stock,,,,

i don't know why...

anyway i'v click to push update from sd cart....and put inside the sd supersu but in the end i've installation aborted...

dosen t work.....

and if i try to enter in the stovk recovery from bootloader i ve black screen...
[Moto G Android Development] mikelara130:
Hey guys, I'm trying to get TWRP on a German Moto G on which I've flashed US firmware as per this thread, and with the 4.4.2 OTA update.

It all seems to work fine but when I try to boot into recovery, be it through the bootloader (using the up volume key and not the power key of course), or through adb (using "adb reboot recovery"), the phone just boots into system normally. If you have any idea what might be going wrong or suggestions to try I'd appreciate it.
[Moto G Android Development] krypto16:
I had the same problem.. Only way to go to 4.4.2 and stay rooted with recovery is to downgrade then flash the zip file from the repack thread. Make sure to read through the thread though as there is a modified zip a few pages in that works. The zip in the original post breaks wifi
[Moto G Android Development] PRNSTR:
Just now also Tried this one on german 1032 with us retail rom and 4.4.2 OTA, but going to recovery also just shows the android logo with the text: No command.
[Moto G Android Development] alex1301:
For me too.
[Moto G Android Development] tillaz:
like i have said a few times > Link try this
[Moto G Android Development] alex1301:
It´s not working. My phone is directly booting to the homescreen.

EDIT: can somebody provide the stock recovery of 4.4`?
[Moto G Android Development] Jkmoran:
Don't work for me. Just boots into bootloader and the boot into the system. Thanks for your work :good:
[Moto G Android Development] flibblesan:
That doesn't help unfortunately. Something else has changed.. possibly something with the bootloader.
[Moto G Android Development] Durteedee:
Yea same issue with me I flashed the KitKat then tried to flash a new recovery tried to root after KitKat still nothing like in fastboot selecting recovery just reboots the phone and trying to flash an custom recovery leads in partitions don't match

sent from the kitty kat Atrix HD Maxx
[Moto G Android Development] Cooptx:
I seem to have a problem where I can't flash any files. No zip files are being detected by CWM. I had to deal with TWRP's buggy touch screen to try and get root.
[Moto G Android Development] denzel09:
Recoveries are WIP. They have still bugs.
[Moto G Android Development] readonly24:
Hope we get a good, stable TWRP soon.
[Moto G Android Development] ferreinf:
Devs are workin on CM11, but yeah i also prefer twrp, lets wait :)
[Moto G Android Development] nupi:
CWM can flash supersu through adb sideload but refuses to do much other than that in my case (well it creates backups but then refuses to flash them) ...
[Moto G Android Development] salingpusa:
mismatched partition

when flashing this i encountered mismatched partition size (recovery).

would gladly appreciate it if somebody can point me to the right direction to correct this.

Thanks

**whoops - wrong thread (for CWM)**
[Moto G Android Development] Entropy512:
I think I figured out the 4.4 bootloader compatibility issue.

It seems like 4.3 bootloaders were OK with kernel images where the device tree was tacked onto the kernel zImage

4.4 bootloaders require the dt image to be a separate component of the boot image file.

CM11 and Omni 4.4's mkbootimg supports the --dt parameter for this capability. What got me a working (well, at least successfully boots with "fasboot boot") TWRP image is:

Take the download in the OP of this thread

Use unpackbootimg to extract its ramdisk

Extract the zImage, dt.img, and ramdisk of stock 4.4 recovery using a dt-aware unpackbootimg (right now, only CM11's unpackbootimg does this, I'll be fixing up omni so it can do this too in the next few days - I have all the patches on my machine but I need to upload them to gerrit, hopefully I can do that tomorrow...)

Replace the stock recovery ramdisk with the one from TWRP

Repack the boot image using a dt-aware mkbootimg

The one issue is that colors are screwy - TWRP is reddish-orange instead of blue. I haven't really tested any functionality yet. No touchscreen issues either.

I'll upload the image once I've tested it further and I have all the required patches uploaded to omni

Edit: holy hell touch is REALLY flaky. I was dead wrong about "no touchscreen issues". Not even going to upload this horrific mess...
[Moto G Android Development] KuGeL94:
Can't use TWRP, it won't accept any touch command, gonna stick with CWM, I have no preferences. :)
[Moto G Android Development] enrique097:
After installing the TWR does not respond to any touch switch it off with the power button then start the fastboot mode and then go into recovery TWR will respond try a couple of times to unlock and it will work, it is still buggy but it works.

Also anyone after I install the recovery in fastboot mode in the phone comes "Mismatched partition size (recovery)" what is the meaning of this, I am doing something wrong? it seems to work afterwards... but just to be sure what is happening please explain.

Thank you.
[Moto G Android Development] a1Pha:
I suggest using CWM as long as we didn't figure out the touch issues.

The "mismatched partition size" is just a warning, our custom recovery doesn't match the size of stock recovery. Even if it would, it' would still throw a signature mismatch warning, so you can simply ignore this.
[Moto G Android Development] Entropy512:
When I get home I'll talk to Dees_Troy about debugging touch issues. We've solved booting on 4.4 bootloaders, just need to solve touch response.
[Moto G Android Development] immortal_yash:
well for graphical issues use 'RGBX8888' to turn them back to blue ;) tested on Moto G :)
[Moto G Android Development] Entropy512:
I figured it was something silly like that... I don't yet have device trees set up to build recoveries for the G, something I'll be working on when I get home.
[Moto G Android Development] immortal_yash:
When you start can you join irc channel maybe i can be of some help as i had got cm11 booting on moto g till dhacker29 updated his kernel :P i can't just help in kernel not my cup of tea ;)
[Moto G Android Development] Entropy512:
You'll see me on IRC when I return home - I haven't been on IRC at all (ANY channel) since I drove to visit family for the holidays. :)

Although I'll probably be idling a lot for the next day or two.
[Moto G Android Development] immortal_yash:
Same here btw happy new year :)
[Moto G Android Development] Entropy512:
BTW, where's the device tree you built TWRP from?
[Moto G Android Development] a1Pha:
Actually, it is gone due to a harddisk failure. My build env was one of the things I did not backup. But this should be a working one for TWRP. Do not use it for CM or similar stuff, it won't work.
[Moto G Android Development] vocoderism:
it seems be timeout on synaptics_i2c_rmi4 device driver that goes in error state with return code 1 and the retry and work

can you try to compile inline kernel stock in BoardConfig of device tree and add on defconfig

CONFIG_TOUCHSCREEN_SYNAPTICS_I2C_RMI=y

CONFIG_TOUCHSCREEN_SYNAPTICS_RMI4_I2C=y

CONFIG_SYNA_MULTI_TOUCH=y

and then

make recoveryimage
[Moto G Android Development] Cooptx:
Hey, which update version is that fixed in? I will include it in my root tools and remove the boot loader downgrade step :thumbup:
[Moto G Android Development] Faruko:
Noob here...

1. Do i need to Root my phone for this ?

2. Im guessing this is installed using the SDK isnt ?
[Moto G Android Development] asheehanjr:
I'm having the same issue but with the US version. It's starting to annoy me! lol I have done everything else right like root and unlock boot loader but, can't get the darn recovery to flash. When I do try to flash it it says partition mismatch or something like that. I don't know. Any suggestions? I looked through all of the pages here and couldn't find anything that worked. Any suggestions would be appreciated! Thank you! :D
[Moto G Android Development] coloxim:
same for me...

;)
[Moto G Android Development] Mr Ace:
I installed the twrp recovery, but just after installing when I press volume down and click recovery it eventually comes up with the bootloader warning screen and reboots. Please help really frustrated
[Moto G Android Development] immortal_yash:
Anyone tried this out should i try it?
[Moto G Android Development] vocoderism:
Try please i bricked cell this night use christopher83 toolchain v 4.7

Inviato dal mio XT1034 utilizzando Tapatalk
[Moto G Android Development] Entropy512:
No one has released a binary since it's almost useless due to the touch issues.

See my post above a bit - I documented how to properly repack recoveries so they boot.
[Moto G Android Development] immortal_yash:
You you release your twrp recovery that works with 4.4 bootloader even if it has touch issues
[Moto G Android Development] Entropy512:
Figured out the touch issues. Interestingly, Samsung N80xx (Note 10.1) devices also have the EXACT same issue (confirmed by building TWRP with TWRP_EVENT_LOGGING set to true):

https://gerrit.omnirom.org/#/c/4176/

Attached is a TWRP recovery that has working touch events. This was generated by repacking the ramdisk created from my device tree (I'll be pushing my changes soon, but they're nearly identical to dhacker's device trees currently) into recovery.img from the 4.4.2 AWSRetail factory image distribution. It appears that 4.3 kernels, even if repacked properly, don't provide graphics with the new bootloader. Annoying... :(

Actually, this was built from a 4.4 source tree, so it will likely have issues when flashing any ZIP from 4.3 or earlier that contains asserts...

WARNING: It turns out this is too large to fit in the recovery partition. As a result, it will ONLY work when using

fastboot boot twrp_falcon_44.img

DO NOT try to flash this to your device!

grumble 4.4 property system changes...
[Moto G Android Development] vocoderism:
Seems some delay in init.mmi.touch

sh inside kernel ramdisk can you confirm?

Inviato dal mio XT1034 utilizzando Tapatalk
[Moto G Android Development] immortal_yash:
Did dees_troy suggest something? Last time i asked him he said maybe some sensor giving problem
[Moto G Android Development] vocoderism:
sorry i have a problem to flash recovery to test according to falcon partition layout recovery an boot are 10240KB recovery img is too big

is it possible?

(bootloader) Image size exeeded partition limits
[Moto G Android Development] ferreinf:
Touch is working fine, but no backup, and all settings are restore to defaults at every boot..

It's blue :)

Sent from my Moto G
[Moto G Android Development] Entropy512:
He wasn't around, but I got some hints on how to turn touch event debugging from aaaarggh (old buddy from the xdandroid on HTC Rhodium days), and once I found the cause, Ibrahim Awwal (working on getting the Note 10.1s working with Omni) said he had the exact same issue and linked me to that commit I linked.

Crap. For now, you need to use "fastboot boot"... I wonder if there is a way to compress the dt image...

Hmm, I didn't test backing up, i'll look into that... Settings restoring to defaults is PROBABLY a result of booting via "fastboot boot" but I'm not sure.

It will at least allow you to root your device. :)
[Moto G Android Development] vocoderism:
OK THX you only modifed 2 files in a post of gerrit in recovery? Have you compile with stock prebuilt kernel?

Inviato dal mio XT1034 utilizzando Tapatalk
[Moto G Android Development] vocoderism:
I have retail italian model nere you are my running partition layout

u0_a142@falcon_umts:/ $ su

root@falcon_umts:/ # cat /proc/partitions

major minor #blocks name

7 0 22901 loop0

179 0 7634944 mmcblk0

179 1 65536 mmcblk0p1

179 2 512 mmcblk0p2

179 3 32 mmcblk0p3

179 4 512 mmcblk0p4

179 5 200 mmcblk0p5

179 6 400 mmcblk0p6

179 7 32 mmcblk0p7

179 8 512 mmcblk0p8

179 9 2048 mmcblk0p9

179 10 2332 mmcblk0p10

179 11 512 mmcblk0p11

179 12 200 mmcblk0p12

179 13 400 mmcblk0p13

179 14 32 mmcblk0p14

179 15 512 mmcblk0p15

179 16 1052 mmcblk0p16

179 17 1536 mmcblk0p17

179 18 1536 mmcblk0p18

179 19 512 mmcblk0p19

179 20 8 mmcblk0p20

179 21 1536 mmcblk0p21

179 22 1 mmcblk0p22

179 23 8 mmcblk0p23

179 24 1024 mmcblk0p24

179 25 128 mmcblk0p25

179 26 3072 mmcblk0p26

179 27 4096 mmcblk0p27

179 28 4096 mmcblk0p28

179 29 8192 mmcblk0p29

179 30 512 mmcblk0p30

179 31 10240 mmcblk0p31

259 0 10240 mmcblk0p32

259 1 678016 mmcblk0p33

259 2 999424 mmcblk0p34

259 3 8192 mmcblk0p35

259 4 5791616 mmcblk0p36

179 32 512 mmcblk0rpmb

254 0 22900 dm-0

root@falcon_umts:/ #

P31 and 32 that correspond to boot and recovery are 10240 (10MB)

Can you post output of

cat /proc/partitions of your device?

Inviato dal mio XT1034 utilizzando Tapatalk
[Moto G Android Development] immortal_yash:
Well first great job to finally fix the touch issue and for the failing of backup please check the mount points as my recovery once had the same problem
[Moto G Android Development] jmoore4294:
I don't know how good or bad this may be, but since I was not near my computer when Entropy512 posted his recovery I was able to flash it via Flashify from the play store. When I got home and tried via fastboot it told me it was too big, but Flashify was able to successfully flash it for me no problem.
[Moto G Android Development] asheehanjr:
Exactly the same issue that i'm having. No backup but everything else works ok.
[Moto G Android Development] vocoderism:
OK strange but with flashify works fine.twrp.fstab si correct for working backup boot in recovery go to settings tag and tap restore defaults.then go to backup click on storage and select internal storage .then tab reboot and select recovery. When boot up to recovery again backup and restore work

Edit backup recognize now internal storage but fail with error unable to create folder .monday i ll compile from my device tree with fix of entropy

Inviato dal mio XT1034 utilizzando Tapatalk
[Moto G Android Development] immortal_yash:
Can you show is the error on recovery?
[Moto G Android Development] asheehanjr:
Ok cool. I forgot to mention that I flashed via flashify.
[Moto G Android Development] vocoderism:
for cm11 i had second compilation with audio media gps working

for ril camera and wifi i attach a debug log of xt1032

can someone check the error in fs_device_efs_rmts.c for rild and children process?

I think that in cm11 branch compilation we need to add this sources from motorola

http://sourceforge.net/projects/mot...motorola_security_moto_crypto.tar.gz/download

5>[ 13.457698,1] init: starting 'qcamerasvr'^M

<6>[ 13.459513,1] init: waitpid returned pid 895, status = 00000100^M

<5>[ 13.459624,1] init: process 'qmuxd', pid 895 exited^M

<5>[ 13.459801,1] init: process 'qmuxd' killing any children in process group^M

<6>[ 13.459900,0] init: Created socket '/dev/socket/pps' with mode '660', user '1000', group '1000'^M

<6>[ 13.461831,1] init: waitpid returned pid 897, status = 00000100^M

<5>[ 13.461933,1] init: process 'qcamerasvr', pid 897 exited^M

<5>[ 13.462092,1] init: process 'qcamerasvr' killing any children in process group^M

<6>[ 13.466504,1] init: waitpid returned pid 896, status = 00000100^M

<5>[ 13.466670,1] init: process 'ppd', pid 896 exited^M

<5>[ 13.466796,1] init: process 'ppd' killing any children in process group^M

<6>[ 13.467218,1] init: waitpid returned pid 894, status = 0000ff00^M

<5>[ 13.467408,1] init: process 'ril-daemon', pid 894 exited^M

<5>[ 13.467575,1] init: process 'ril-daemon' killing any children in process group^M

<3>[ 13.475066,0] Notify: smsm init^M

<6>[ 13.521219,1] pil-q6v5-mss fc880000.qcom,mss: mba: Power/Clock ready interrupt received^M

<6>[ 13.521268,0] pil-q6v5-mss fc880000.qcom,mss: Subsystem error monitoring/handling services are up^M

<6>[ 13.522702,0] subsys-restart: subsystem_restart_wq_func(): [e3f3c000]: Restart sequence for modem completed.^M

<3>[ 13.668968,0] ^M

<3>[ 13.668974,0] SMSM: Modem SMSM state changed to SMSM_RESET.^M

<3>[ 13.669271,0] Fatal error on the modem.^M

<3>[ 13.669466,0] modem subsystem failure reason: fs_device_efs_rmts.c:154:[8 ,1572864, 1] EFS: rmts_get_buffer api failed.^M

<6>[ 13.669649,0] subsys-restart: subsystem_restart_dev(): Restart sequence requested for modem, restart_level = RELATED.^M

<3>[ 13.669915,0] Notify: start reset^M

<6>[ 13.670821,0] subsys-restart: subsystem_shutdown(): [e3f3c000]: Shutting down modem^M
[Moto G Android Development] vocoderism:
Entropy can you share please a fix for touch events to integrate it in future cm build?

Inviato dal mio XT1034 utilizzando Tapatalk
[Moto G Android Development] immortal_yash:
Just re sync twrp sources ;)
[Moto G Android Development] vocoderism:
From teamwin branch twrp2.7?

Inviato dal mio XT1034 utilizzando Tapatalk
[Moto G Android Development] immortal_yash:
From omnirom sources
[Moto G Android Development] Entropy512:
I used dhacker's device trees to build, with only minor changes to get them to build within omni's trees. I'll try to push the device tree stuff tonight.

I did not build the full kernel from source - 4.4 bootloaders won't boot 4.3 kernels (well, they will boot but graphics won't work)

As a result I had to repack the TWRP ramdisk into Moto's prebuilt boot image for 4.4

I linked to the gerrit submission earlier. Not sure if it's merged. Ibrahim ifdeffed it so you'll now need a small change to the device tree to flip the fix on.
[Moto G Android Development] caveman102:
error on comand pront

when flashing recovery i get an error saying "target reported max download size of 536870912 bytes" it continues next line with "error:cannot load 'recovery.img' : no error" any suggestions im not a noob but i can use some help point me in the right direction i get there..... bootloader unlock already android 4.3 8gb model gsm global
[Moto G Android Development] flibblesan:
Read the red text on http://xdaforums.com/showpost.php?p=49122115&postcount=129
[Moto G Android Development] vocoderism:
so i fixed a backup and file manager empty problem from twrp modified from entropy

set ro.build.product from falcon to falcon_umts for assert issue during flash and future compatibility of cm-11 flash for falcon xt1032

to flash correctly

1) Download this zip and plug your device to usb on pc

https://www.dropbox.com/s/pq7y7kvczkrcyjs/Twrp_MotoG_signed_010814_163615.zip

2) adb push Twrp_MotoG_signed_010814_145044.zip /sdcard/

3) Go to Recovery Mode (i think also CWM work in flash of this zip)

4)Install zip from recovery previously flashed and choose after Reboot recovery

5) test touch,backup,restore,flash and file manager operations
[Moto G Android Development] denzel09:
I ll try thanks. Do you have news about en.EU update?
[Moto G Android Development] obvious:
Installed and seems to work fine. Backup up too. Haven't run a restore yet. Cheers
[Moto G Android Development] vocoderism:
the only problem is flashing zip that not have inside updater-script expected assert

the rest should be work fine now

i tested also restore and flash zip with correct assert and works fine also flashing

:eek:
[Moto G Android Development] a1Pha:
Please test the new recovery builds and send me a PM when it is considered stable, I'll update OP then :)
[Moto G Android Development] jmoore4294:
So far so good on vocoderism's build. Backup and restore work flawlessly. No touchscreen issues to speak of. Flashing mods and the one 4.4 rom available work great as well.
[Moto G Android Development] vocoderism:
OK a1pha if you want download zip and publish recovery on yout first Page.thaks all for testing

Next Step cm11 moto g from team-moto-g i hope

Inviato dal mio Nexus 7 utilizzando Tapatalk
[Moto G Android Development] nupi:
Does it work with encryption?
[Moto G Android Development] vocoderism:
I do not test it try please and post result

Inviato dal mio XT1034 utilizzando Tapatalk
[Moto G Android Development] jmoore4294:
Encryption is working fine. There are only two options I have noticed that aren't there or don't work. One is adjustable screen brightness. Don't know if that is a feature of twrp or just something my HTC one had. But its not a big deal. Second thing is that the dates on backups are off by about 10 years. Keeps coming up with the year as 2024. Again, not a big deal.
[Moto G Android Development] vocoderism:
You must set backup name as you prefer it is normal on twrp

Inviato dal mio XT1034 utilizzando Tapatalk

---------- Post added at 09:22 AM ---------- Previous post was at 08:59 AM ----------

I think last build si very stable and for daily use.waiting for update link in first page from thread's author

Inviato dal mio XT1034 utilizzando Tapatalk