yashsingh1/xdaforums huggingface dataset:
[Moto G Original Android Development] wskelly:
Yes, [MENTION=5034190]riyosakura[/MENTION], you are right -- as it is only software, the phone can't be completely broken. I think that is the good way to look at it.

BUT.

Without the bootloader you are done. The bootloader is the first thing to start. It calls some sort of utility to open the USB port, turn on the screen, power some devices, etc -- basically the code that will *allow* you to flash. The reason you can flash and update over the USB port is because a bootloader started and ran some code that enabled all of that stuff. Without this, you aren't flashing anything with the usual user tools.

This is off topic slightly, but look at this sequence of events to boot a Raspberry Pi:

http://raspberrypi.stackexchange.com/questions/10442/what-is-the-boot-sequence

There are actually three bootloaders in place there. And the RPi is open everything, so you can ask the guys who designed it exactly how it works. But the one that the user will mess with is on the SD Card. The other two bootloaders can't get altered.

https://www.raspberrypi.org/forums/viewtopic.php?f=24&t=31927

Back to your phone: If you know the places on the motherboard to attach some sort of low level flash tool, I think you could still bring it back. However this would involve the special hardware (and software) to do it, and knowledge of the locations on the board to attach it to. Any phone that is so-called hard-bricked (unless it was damaged physically, like in water or something) can probably be brought back with these special tools. If you knew someone at Motorola, they could probably bring the phone back from any state.
[Moto G Original Android Development] Pinktank:
Is wifi sleep more aggressive or is it me? I find my wifi asleep a lot of the time, it finds and connects after I wake up the phone.
[Moto G Original Android Development] bogante:
Same as me, install a kernel and should work normally. I have "Optimus Kernel"
[Moto G Original Android Development] ironman38102:
I myself bricked one of my devices after upgrading the BL to the 41.18 and then flashing 4.4.3(which didn't hard brick my phone) to 4.4.4 via OTA(this hard bricked it). I still had no choice but to upgrade my BL on my replaced phone as well(I got a replacement for my dead moto g) but I promised myself whatever happens I will not install 4.4.4 via ota from 4.4.3
[Moto G Original Android Development] sjandroiddeveloper:
Yes most of people who have hardbricked their devices are because they first downgraded from lollipop to 4.4.2 and applied ota of 4.4.4(which downgraded the bootloader and boom)

But there are very few people who have hardbricked by flashing wrong bootloader file because now most people know that they must not flash gpt.bin and bootloader while downgrading and that bootloader is same on both xt1033 and xt1032
[Moto G Original Android Development] matmutant:
False, Bootloader is not really pure software it is so low-level software it could even be considered as "high-level" hardware

+1

On our devices the bootloader can be compared to PC BIOS: if missed flashed, then you are doomed...

On my old AM2 MSI motherboard a missed flash had killed the BIOS, great thing was that the BIOS was a plugged chip and a friend had the exact same motherboard so we could swap the chips, boot, swap again and reflash

On one gigabyte motherboard i have, there is a secondary backup BIOS soldered on it that can boot if the first is screwed and reflash it

We don't have these security on MotoG ...

Flashing a bootloader is like high-speed driving, or any extrem sport : do it at your own risk, feel the adrenaline when things are close to be dead... But assume when it is...

Oh yeah, and follow "If it ain't broke, don't fix it" .. At least when you work on critical applications or on your work tool ;)
[Moto G Original Android Development] Mchasard:
Strangely I can't no more receive or send MMS under the last build from 04/05
[Moto G Original Android Development] riyosakura:
Im sure there is way to fix that dead moto g. Just dont give up yet.

I have ever once fix a wrong bootloader replacement. Even though is not on moto g. Its on mtk devices.

Maybe its differ from our moto g. But I believe there must be a way to fix it.

I dont know the fact that there is someone who making his phone completely dead just because messing up with BL, since im new moto g user (its not more than a week yet).

If So, every user must be warn regarding a BL flashing.
[Moto G Original Android Development] sjandroiddeveloper:
But there is a way to fix the hard bricked moto g on 4.4.4 using blank flasher tool

5.0.2 is yet to come

I read the threads they said they need mbm-ci 5 for that

So let's not loose hope

And I don't understand why there is so much fear

If someone is flashing the correct bootloader there is technically no way you could end up with a bricked device

There are so much people here who have successfully updated their bootloader that is why majority of users have updated bootloaders

And its obvious if you mess up with the bootloader you will kill your device
[Moto G Original Android Development] matmutant:
That's what the FAQ is made for, giving answers about questions and warnng about potential danger of some actions.

http://xdaforums.com/moto-g/help/rc-faq-cm12-frequently-questions-t2996087/post59520890#post59520890

As soon as someone comes here and start playing with the core of the device, i assume he is not a newbie in flash craving and took time to read at least the FAQs (that are not fully completed i know, but most questions are already answered there).

On my old Sony-Ericsson (e10i) the bootloader wasn't unlocked and only bypassed meaning we couldn't brick it (custom roms were possible thanks to custom tricks, but in case of failure the BL was still there to save the device...)

[MENTION=3101826]wskelly[/MENTION] : btw the bootloader i provided is not a "random file" since i extracted it from the Brazilian system image, and then compared its md5sum/SHA256 with others from XT1033/XT1032 images to prove they were only one BL for both, some users took the high risk of flashing it on XT1034 [unconfirmed to be working at that time], it worked for them [luckily].

The bootloader image i provided has been downloaded more than 5500 times ==> this is in favor of a fully working thingy compared to the few hardbrick complains...

BUT i see that most users are simply insane since only 2000 people downloaded the md5sum .... meaning that only 36% actually verified the file intergrity before flashing :eek::eek::eek::eek::silly::silly::silly::silly:

PS: i'm not even sure that every single person that downloaded the md5sum actually used it :rolleyes:

No, i can list hardware reasons for a BL flash fail:

Faulty USB cable

Faulty USB port

Faulty USB driver

PC OS crash or instability during flash

Electricity failure during flash when using a desktop computer

Having a cat

having a younger Brother/Sister hanging around

...

I personnally upgraded my own bootloader, but i was aware of risks and would not cry/complain if it had failed.
[Moto G Original Android Development] sjandroiddeveloper:
Yes quite obvious reasons and some are funny too but these are to be taken care by user himself using his common sense and not knowledge of android core software
[Moto G Original Android Development] matmutant:
"Common sense"... if "Common sense" was used more often, lots of things posted here would have not been :rolleyes:
[Moto G Original Android Development] Pinktank:
That's a bandaid, and I do not want to install a kernel, I was trying to give a bug report
[Moto G Original Android Development] wskelly:
[MENTION=3816475]matmutant[/MENTION], I was not directing that at you. Thank you for taking the time to make the file available and updating the FAQ. It was just a general comment toward users, not just for Falcon but another thread I was reading, thus time for Nexus 4 I think... Same story, an assert from CM caused mass confusion on that thread, and I read something like, "oh no, I was so tired and I think I just flashed recovery.img to the boot partition... Phone isn't booting... What do I do?"

I will open a bug to have the assert removed (it will get rejected) since everyone seems to agree there isn't a reason to update if you don't need to. As this phone is a *perfect* candidate for CM because it is a couple years old now, I think the list of users causing bricks will grow... (but the success list is growing faster)

Funny list too [emoji5] !
[Moto G Original Android Development] matmutant:
Should i upgrade my BL, Update my ROM?

Time for a reminder, for that i will simply quote the update notes of my favourite distro :

This works for the current BootLoader story but can be applied to ANY case implying an update.

Better know the risk before trying anything. From my place i'm not saying people should not upgrade the BL, only that they should understand the risks before doing so.
[Moto G Original Android Development] UltraMaks:
Have you ever heard anything about confidence? :) I trusted you so everything went fine even without checking md5 :)
[Moto G Original Android Development] matmutant:
I'm quite happy i'm "trusted" but ...

Confidence is the key that lead to disaster, didn't you think that the download could have failed and your downloaded image get corrupted?

I had verified the image before AND after my upload to make sure the file wasn't corrupted, but i can't guarantee that the file won't get corrupted during the download process, that's what md5sum are made for, verifying the the file stored on the server is the same as the one on your computer

Luckily your download when fine and the flashing process too, but i hope that next time you'll check the sum ;)

[I ALWAYS check the md5sum of everysingle nightly before flashing... that can't be done using CyanDelta, but i hope their process features some integrity check before installing updates...]
[Moto G Original Android Development] Shub77:
I had to modify a string inside the zip, but thanks, now it works. Appreciated. :)
[Moto G Original Android Development] alex_is_the_1:
I was one of them who flashed your extracted BL on an XT-1034. Everything is working fine, I took the risk because I have this moto e as a backup. I made sure to read the comments and experiences from other users who also flashed it. Thanks again for making it available to us who don't have the bandwith to download an entire stock ROM for a 10 MB BL.

Sent from my Moto E
[Moto G Original Android Development] Orjakone:
I take one doubt, where the ambient display?

Would be one of the new features of CM 12.1: http://www.cyanogenmod.org/blog/all-about-l-part-2
[Moto G Original Android Development] sjandroiddeveloper:
Ambient display is present on the main CM code tree but its not present for falcon yet

Sent from falcon

PRESS THANKS IF HELPED
[Moto G Original Android Development] moralesnery:
Moto G branch (falcon build) has Ambient display disabled because problems in the animations and phone performance. Better waiting for a good implementation or go to 5.1 GPE /Motorola 5.0.2 for a working Ambient Display.
[Moto G Original Android Development] bogante:
Somebody have problems with flash? Is a common bug? My flash is not working when I take a picture/video/Lantern.
[Moto G Original Android Development] sjandroiddeveloper:
Working fine here

I am using Motorola camera and gallery
[Moto G Original Android Development] bogante:
Apparently my flash is not working (hardware problem) when I change the motherboard I forgot to check it out lol.
[Moto G Original Android Development] sjandroiddeveloper:
Maybe you can change the flash led yourself

BTW -Why did you change your motherboard

sent from falcon

PRESS THANKS IF HELPED
[Moto G Original Android Development] frsdesign:
Hi all,

Can somebody tells me which of the new gapps to choose using falcon and CM12.1 nightly ?

Arm or arm64 ?

http://wiki.cyanogenmod.org/w/Google_Apps

Thank you !
[Moto G Original Android Development] sjandroiddeveloper:
The Arm one

Sent from falcon

PRESS THANKS IF HELPED
[Moto G Original Android Development] sjandroiddeveloper:
If anyone wants to use custom kernels then I have found these two to be good

ATTACKED KERNEL

OPTIMUS KERNEL

Sent from falcon

PRESS THANKS IF HELPED
[Moto G Original Android Development] UltraMaks:
And what is the reason of changing "stock CM" kernel?
[Moto G Original Android Development] sjandroiddeveloper:
Only thing which I found useful is over clocking the GPU from 450mhz to 533mhz means a little increase in performance

Sent from falcon

PRESS THANKS IF HELPED
[Moto G Original Android Development] matmutant:
In Benchmarks or i real-life?
[Moto G Original Android Development] sundeep97:
Not on both... :p On papers :laugh:
[Moto G Original Android Development] sjandroiddeveloper:
Not tested in real life but I got more FPS in antutu benchmarks so yes it affects a little

---------- Post added at 06:33 PM ---------- Previous post was at 06:32 PM ----------

Lame joke, it totally sucked
[Moto G Original Android Development] frsdesign:
Hi and thank you for the reply ,

I have a second question, is it possible to downgrade from CM12.1 to Stock Kitkat using the mfastboot commands without any problems (Moto G 1st Gen XT1032) ?

Thanks !
[Moto G Original Android Development] UltraMaks:
If you upgrade your bootloader to LP's bootloader (without it you won't be able to install latest versions of CM 12.1) then I would not suggest (you will receive flickering issue on stock KitKat). But obviously yes - you can :)
[Moto G Original Android Development] frsdesign:
Ok thanks, so no way to rollback ? I upgraded my bootloader yes.... sooooo ohhhhh noooo...
[Moto G Original Android Development] rahulxda:
Yes, you can just follow the below link it has step-by-step procedure.

http://www.droidviews.com/restore-moto-g-to-stock-and-downgrade-firmware/

Hit Thanks, if I helped u:)
[Moto G Original Android Development] frsdesign:
Hmmm thank you but i already know that procedure, but it doesn't seem to be successful in my case, it's a downgrade after a bootloader upgrade, and this guide from february 2014 doesn't come with this little particularity :/
[Moto G Original Android Development] sjandroiddeveloper:
CyanogenMod doesn't effect your phones core software that is bootloader and partition table

What you need to be careful about is the bootloader and downgrade according to that

Sent from falcon

PRESS THANKS IF HELPED
[Moto G Original Android Development] 73IGH:
Has notification sound crackle been fixed yet anyone?
[Moto G Original Android Development] riyosakura:
Its improve performance and battery life. Plus, you can have double tap to wake feature. Its better than pushing the power button to wake the phone up.

Why do you need to rollback?

One of the reason why im buying moto g is because the devices is supported very well by google and the devs. So that we can got a stable 5.1 early.

I think kitkat is old. It just white holo style plus transparent status bar, compare to jelly bean. And it still using dalvik which is consume much more battery than art.

Im just curious what is the reason for people that need to rollback to previous version.
[Moto G Original Android Development] moralesnery:
A lot of apps are still buggy or incompatible on Lollipop (IPTV running via MX Player in example), some people doesn't like the white UI, or the battery usage of white colors on AMOLED screens.

In fact ,originally Moto G was dalvik-optimized, for me it seems like ART consumes a little bit more battery than dalvik and the installed apps uses more storage space.

I like a lot 5.1, use it only for basic stuff and won't downgrade but I can understand people who wants to.
[Moto G Original Android Development] OldYellowBricks:
offline charging works fine here with latest nightly xt1033

Only thing that bugs me is that the offline chaRGING logo/symbol is so 2009-ish haha
[Moto G Original Android Development] diogobuique:
Ooooo Thanks for your information!!!
[Moto G Original Android Development] JoaoMarcos:
All my apps are restarting (no memory) in CM 12.1 :crying::crying::crying:

All stock
[Moto G Original Android Development] riyosakura:
About white UI, there is theme on CM12.

Moto g dalvik optimized? Can you explain to me.

However art created to optimize android. I dont think its gonna consume more battery than dalvik.

Yes, it take much more storage, but its not a problem today, with a larger storage on device itself. Even a lower end devices can run lollipop nowaday with the devs optimation.

For incompatibility, just wait, the devs will make it work, because they have to step forward to art.

Btw, i got a problem, music stop working when browsing on chrome. Anyone else got the same bug?

Try installing custom kernel. Maybe it gonna make it better.
[Moto G Original Android Development] bogante:
What Kernel do you recommend?
[Moto G Original Android Development] SammyP6:
I use attacked but try them both. Flash one wait couple days flash the other. See which one you like better and use that.
[Moto G Original Android Development] sjandroiddeveloper:
Use ATTACKED KERNEL , it gave better results for me

Sent from falcon

PRESS THANKS IF HELPED

---------- Post added at 07:12 PM ---------- Previous post was at 06:42 PM ----------

Guys offline charging is still not working for me on latest nightly on my xt1033

Can anybode suggest a solution???
[Moto G Original Android Development] JoaoMarcos:
Android is killing music player (no memory, I think).
[Moto G Original Android Development] Eurofighter_ty:
Yes, the memory leak is still not fixed... fu**k google !!!!!!!!!!!!
[Moto G Original Android Development] riyosakura:
Even with memory leak we still have very good performance device till now.

And prepare to be surprised when all the bug is fixed. ??
[Moto G Original Android Development] JoaoMarcos:
But memory leak is a f****** bug, I think this bug should be the first to be corrected.
[Moto G Original Android Development] tzzeri:
But moto g isn't oled
[Moto G Original Android Development] owaisnaim:
I think offline charging is a kernel related thing If u r using any other kernel revert back to cm stock kernel, Ur problem will be solved.!!
[Moto G Original Android Development] OldYellowBricks:
I can confirm this. custom Kernel needs to be updated with LATEST cm changes to get offline charging working.

Tested this myself.
[Moto G Original Android Development] matmutant:
Then help.

CM team needs more people working on "this issue".

btw, it is not "one memory leak" but "many memory leakS" ==> there are a lot of core services that leak some after running/closing, there was camera leaking when KSM was enabled, screenOff animation, Trebuchet had one fixed recently, but there are obviously others still living...

+1
[Moto G Original Android Development] geekasm:
stuck in CM boot

Hi,

XT1033: bootloader unlocked, rooted, stock rom 4.4.4

TO: 5.0.2

Flashed 4118 bootloader, as detailed in http://xdaforums.com/moto-g/help/rc-faq-cm12-frequently-questions-t2996087

It was successful.

Followed http://xdaforums.com/moto-g/general/guide-how-to-flash-root-cyanogenmod-12-t3090805

formatted system, data, cache, wipe-cache (recovery: clockworkmod-6.0.4.7)

installed CM, Gapps

CM: https://download.cyanogenmod.org/?device=falcon

Gapps: https://www.androidfilehost.com/?fid=96039337900114916

After rebooting, the phone is stuck on the Cyanogenmod boot icon (blinking cat face) since past half hour.

Please guide how to debug/recover.

Thanks,
[Moto G Original Android Development] matmutant:
Thank you for this detail issue report, that will help a lot ;)

force reboot (hold power button until it reboots) and see if still bootlooping

force reboot to bootloader (power+vol-down), go to recovery and wipe again + reflash (make sure the md5sum of both zips are good!)

if still nothing good flash TWRP recovery instead and retry :)
[Moto G Original Android Development] geekasm:
Thanks [MENTION=3816475]matmutant[/MENTION] for your tips.

Mine is a asia retail XT1033. I hope your bootloader is fit for it. (I think so since issue comes in cm boot, not bootloader)

But in the recovery, screen flickering is there.

I have done the reflashes multiple times. havent checked the md5sum of both zips.

I checked twrp. It doesnt show moto g in the supported devices list. Could you share an appropriate link ?

Is there any way I could check logs ?

Also I have flashed latest CM Falcon : https://download.cyanogenmod.org/get/jenkins/109667/cm-12.1-20150508-NIGHTLY-falcon.zip

Is it confirmed to be working ? anyone ?

Thanks for your kind help,
[Moto G Original Android Development] matmutant:
here is the link to TWRP (it was in post #2): http://xdaforums.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621

If you didn't transformed your device to GPE use the twrp-2.8.6.0-falcon.img - 9.9 Mo (else use the GPE dedicated one)

The Flickering in recovery is that your CWM is older than the Bootloader ;)

If you want, you can first use the factory reset slider on TWRP, then advanced wipe and tick dalvik-cache, cache and system.

In TWRP, "Wipe data" wipes ALL DATA (even the "internal storage" where your flashable files may be stored) ==> in the case you want you wipe all the data, then you'll need an USB OTG cable to load from a USB key, or you may use ADB sideload.
[Moto G Original Android Development] geekasm:
I dont know whether my phone is GPE one. However, I downloaded the twrp you linked to. and flashing it. it shows following error :(

cmd: getvar:partition-type:recovery

cmd: getvar:max-download-size

cmd: download:009f2000

cmd: flash:recovery

Mismatched partition size (recovery)

I saw the posts. guess its common error. recovery works !

I am reinstalling and shall update you once it completes.

Thanks again.

---------- Post added at 02:58 PM ---------- Previous post was at 02:47 PM ----------

also I had matched the md5sum of both the zips.

had reflashed several times.

Its still booting since past ~6 minutes. :(

only step remains is to completely wipe everything (internal storage) and retry.

other one is to download another cm12.1/cm12 build ?

please advise.

Thanks for your support.
[Moto G Original Android Development] matmutant:
I would format the whole /data this time (it was reported that some things on /data/media aka 'internal storage' or 'sdcard0' could prevent some installation to succeed) and sideload the zips or use OTG :)

Btw i'm still on 20150503 nightly (so you may try this one too)

you may try not to have any SIM card in the slots too, XT1033 has issues with them during the first boot set up (but only in case it goes to that point...)
[Moto G Original Android Development] geekasm:
formatted internal storage and pulled sim out.

Amen ! I finally see past the blinking cat.

crazy day. Thanks tons [MENTION=3816475]matmutant[/MENTION]

Now I see another issue, as soon as android is starting is finished optimizing the apps and the welcome screen opens.

google play store crashed and it repeatedly shows the error box every 1 sec. till I am forced to shut down. :(
[Moto G Original Android Development] matmutant:
Do what everyone should do when getting that kind of issue:

Force reboot, sometimes force rebooting makes things getting better, or

Boot to recovery, wipe /system, /dalvik-cache, /cache and reflash ROM + gapps

you may also try other 5.1 GAPPS packages http://xdaforums.com/android/software/reborn-gapps-5-t3074660 ==> i use the micro one.
[Moto G Original Android Development] jonnug:
Not sure if anyone else had experienced this bug but I thought I'd share it:

When using SIM 2 as the data SIM, it will not reengage data after disconnecting from Wi-Fi. Cycling aeroplane mode wakes the connection up again. Not a deal breaker, but annoying!

Phone is Asia XT1033 on latest nightly. Has done this as far back as my usage on 12.1, a few weeks.
[Moto G Original Android Development] sjandroiddeveloper:
Thanks , its working now(after flashing cm boot image)

I didn't know offline charging depends on boot image

BTW - The charging screen is from ancient times, almost when android came into existence