yashsingh1/xdaforums huggingface dataset:
[Moto X Android Development] Q9Nap:
i just verified that flashing back to 4.4 works fine on unlocked device as long as you don't flash motoboot/gpt. also able to reapply the 4.4.2 update.
[Moto X Android Development] Q9Nap:
i did upgrade the bootloader when i flashed the ota over 4.4, and then was able to flash back to 4.4 by not flashing the 4.4 bootloader(motoboot) or gpt.

those partitions are not revertible, but once upgraded, they don't prevent you from flashing everything else from 4.4. that is the beauty of having an unlocked bootloader.
[Moto X Android Development] cvhovey:
In other words, when you flashed back to 4.4 (from 4.4.2), you didn't flash these portions of the 4.4 fxz:

fastboot flash partition gpt.bin

fastboot flash motoboot motoboot.img

This may not be relevant, but here's what I'm wondering. I'm still on 4.4 with update files frozen via TiBu so I don't get nagged with the 4.4.2 OTA. Instead of taking the OTA, I was going to just fastboot boot, system, modem, and fsg from your 4.4.2 unofficial fxz. If I really like what I see, especially improved battery life, then I might reflash the 4.4 stuff and take the full OTA.

However, after doing the above 'partial' fastboot to 4.4.2, theoretically it seems I could still flash back all the way to the 4.2.2 camera update where I had my best battery life ... since I hadn't taken the full OTA nor flashed 4.4.2 motoboot/gpt which blocks downgrading? Just want to be sure I'm fully understanding my options.
[Moto X Android Development] Q9Nap:
you should be able to flash back to 4.2.2 anyway, even after taking the 4.4.2 ota. again, just don't flash motoboot or gpt from the 4.2.2 fxz. but yeah, if you want to play it safe, just flash boot, system, modem, and fsg from this fxz.
[Moto X Android Development] cvhovey:
Thanks! After having bitten and flashed a "leak" back on my Razr Maxx ... then shortly after that we who flashed it learned we could not go back, I just want to be quadriple sure before I paint myself into a corner with paint that don't dry. :silly:
[Moto X Android Development] Q9Nap:
haha, i understand. i've been messing around with locked moto devices since the droid x, which is why i was reluctant to update the bootloader and partition from initial 4.2.2 that my moto x came with. but it seems to be necessary to be on the latest versions, or at least the 4.4 versions, for everything to work properly on 4.4.2.

lower bootloader/partition versions never affected performance on previous devices iirc.
[Moto X Android Development] cvhovey:
I'm sure I've used your work a couple of times, definitely on my Razr Maxx and also on Razr M. Glad you're still tinkering with the Motorola devices!

The 'unofficial' update to 4.4.2 sans motoboot/gpt was easy and was up and running again faster than I'd anticipated. Thanks for putting together this tool!
[Moto X Android Development] NWKENT:
Thanks for all your help..

sent by my 4.2.2_139.15.1

Jelly Bean XT1060 XDEV

Please donate to: jcase & Hashcode (if you can)
[Moto X Android Development] Q9Nap:
updated op with link to fxz download page; official 4.4.2 is now available. i'd recommend using the official one over the one i made, but i'll leave mine up for now, for educational purposes.
[Moto X Android Development] Q9Nap:
removed unofficial fxz, added latest moto fastboots zip, clarified op with notes for using rsd lite and fastboot. hope this helps...
[Moto X Android Development] Mike7143:
Not trying to bash on anyone's work or anything, I'm just curious. What makes the files on that website (droid-developers.org) "official"? Who owns the domain? If for some reason I really really wanted true "official" images I'd think one would wait for them to be available on Motorola's site, which is currently still hosting 4.4. Just asking. Thanks!
[Moto X Android Development] Q9Nap:
if they weren't offiicial, they wouldn't be flashable on locked devices.

you are welcome to wait for moto to post 4.4.2 on their dev site.

download 4.4 from both sites and compare partition images; you'll find they are identical.
[Moto X Android Development] Mike7143:
Thanks. Yeah, I did that. I also compared md5s of the files in OP to the ones on droid-developers and they were different so I knew they weren't just moved to their site. Guess I'm just confused how official files are hosted on a non-Motorola domain. Or maybe it's just a case of accepting they're there and not asking how they got there!

Glad to see they're posted though!
[Moto X Android Development] piccit:
No, I think you misunderstood what files he was saying to compare. The 4.4 ones from moto vs the 4.4 ones from sbf.droid-developers. The old ones from this OP were unofficial.

AFAIK the sbf.droid-developer ones are only official in the sense that they're leaks of the official files (the ones carrier/moto support would use). Before Moto started officially making the files available, this was the only way to get them.
[Moto X Android Development] stanrc:
Is there any harm or benefit in installing the official over your previously posted fxz?

Is there a way to install these not through fastboot/rsd? My phone is encrypted so I assume if I do this through fastboot/rsd it will fail or soft brick the phone because its breaking the encryption.
[Moto X Android Development] Q9Nap:
the only real benefits of flashing official fxz vs the unofficial fxz i made are:

the official fxz system.img is not pre-rooted with koush's superuser; rooting was necessary to create the unofficial system.img.

the official fxz NON-HLOS.bin is actual modem binary vs. the dd dump of the modem partition in the unofficial fxz.

fastboot and rsd lite are the only methods i know of to flash.

i don't use encryption, so i don't know how or if it affects flashing. my guess is flashing an encrypted device will work fine, since the purpose of fxz is to restore the device to out of the box condition. you'll just have to re-encrypt after flashing.
[Moto X Android Development] stanrc:
Thanks for info, I guess I'll have to wipe to stock, then update and then re-encrypt my phone.

Ok after some research it looks like encryption only happens on the data partition, so using fastboot to overwrite other partitions won't cause issues.
[Moto X Android Development] cvhovey:
I followed your input, quasi-updating to 4.4.2 flashing just the portions you suggested. From what I've seen so far, wasn't impressed with 4.4 battery life (compared to 4.2.2). And I'm not seeing any improvement on 4.4.2 after several days ... getting about the same battery life while using phone less.

So, since I didn't flash the 4.4.2 motoboot/gpt, and since 4.4 is supposedly backwards compatible to the 4.2.2 camera update fxz, then I should be able to flash back to 4.2.2 camera update sans recovery.img and userdata erase? Or would it be better to erase userdata (then do factory reset on top of that) and selectively restore from TiBu? Alternately it looks like I might have a barebones nandroid of 4.2.2 before I took the 4.4 OTA ... I should have renamed that nandroid so I could tell if it was pre/post OTA upon getting my DE...sigh.

Haven't decided if I'm going to go that route. But overall seeing nothing on 4.4/4.4.2 that I would miss. Just wanting to see if that possible adventure carries any risks ... given that I've not flashed anything from the 4.4.2 partitions that would appear to prevent me from going all the way back.
[Moto X Android Development] NWKENT:
Yep..my conclusion also..nothing in KK 4.4.2 for me..its a downgrade it seems, compared to JB 4.2.2

I did flash back to 4.2.2_12.15.15..and will absolutely set right here..until GREAT things come from KK..if ever..

:)

sent by my 4.2.2_139.15.1

Jelly Bean TWRP 2.6.3.1

XT1060 Moto XDEV

Please donate to: jcase & Hashcode (if you can)
[Moto X Android Development] Q9Nap:
dev editions are almost impossible to permanently brick. pretty much the only way you could permanently brick would be by flashing an erroneous file to the bootloader partition, preventing the ability to access the bootloader menu.

since you didn't flash the 4.4.2 motoboot/gpt, you should be able to fully flash whatever. again, even if you had flashed 4.4.2 motoboot/gpt, you could flash whatever except the downgraded motoboot/gpt.

erasing userdata in fastboot/rsd lite is the same as factory reset in stock recovery. factory reset in custom recovery preserves sdcard contents.

whatever build version you choose, it is a good idea to keep the latest modem (NON-HLOS.bin) and probably fsg.mbn as well.
[Moto X Android Development] cvhovey:
Perfect ... really appreciate those insights!
[Moto X Android Development] edthesped:
If you do downgrade to 4.2.2 please follow up and let us know how it goes. Also, what about 4.2.2 is better to you? If I wasn't remodeling my bathroom and helping kids school I'd try to downgrade for the adventure.
[Moto X Android Development] cvhovey:
Well ... that didn't go so good. Though I could downgrade to 4.2.2, I bootlooped unless doing data wipe. After that, booted up alright and started to selectively restore a few things. However, when restoring Apex launcher ... crashed and went into bootloop.

So ... fastboot files back to 4.2.2 then went into recovery to restore nandroid to where I was at before this adventure.

May retry again later when I have more time to pick up the pieces along the way.
[Moto X Android Development] piccit:
You can't restore apps/data that are 4.4 specific (which I imagine is quite a few)
[Moto X Android Development] cvhovey:
Apex Launcher is "4.0+" compatible so in theory should not cause a crash/bootloop issue. When I have a whole lot more time to kill, might try this again later.
[Moto X Android Development] piccit:
That doesn't necessarily mean 4.2.x and 4.4.x receive the same version when you install it from the playstore
[Moto X Android Development] Mickoou:
I flashed a nandroid backup between bootloops in twrp

---------- Post added at 12:02 PM ---------- Previous post was at 11:59 AM ----------

Sorry wrong tred
[Moto X Android Development] aviwdoowks:
Op's server is down.

??
[Moto X Android Development] Q9Nap:
well, it wasn't my server to begin with, it was matt's. and yes, it is unfortunately down permanently afaik...
[Upgrading, Modifying and Unlocking] Essem G:
So I got a prompt saying there is a system update for my phone, I accepted it.

It simply booted into recovery, started some process and then it said failed.

So then considering it is the installer version I plug it into the installer. This time the screen on my phone looks like I've installed the ROM for the first time. But this time it went to recovery and just sat there. And then on the installer on my computer after a minute it said it couldn't speak to my device.

Using CWM I hit reboot and it says Android apps are updating but after that my phone is exactly how it was before and when I go to settings it says I have an update available.

What does this mean, and how can I fix it? My phone runs the ROM fine but it's not updating. All solutions will be considered
[Verizon Samsung Galaxy S III] aypeeootrek:
I'm having trouble trying to run scripts in terminal. When I enter terminal, hit su> enter , I'm not gaining access to root. Seemed to happen after I flashed the latest beans Rom because I was able to run scripts while in wicked.

At first I was trying with Rom toolbox pro and it wasn't working. Then I downloaded terminal emulator from the play store and that didn't work. Su app shows it has root access and I even made it reprompt me to reallow access. That didn't work. Tried installing busy box from the market and that didn't work either. Out of idea plus I googled the hell out of it too. Thanks!
[Verizon Samsung Galaxy S III] buhohitr:
I saw you have # prompt meaning you do have root access, but when you tried to execute another command and it said command not found, sounds like there's an issue with your other app, but not root. If you download root checker from the market and verify you have root then the issue is not with root.
[Verizon Samsung Galaxy S III] aypeeootrek:
Hey thanks for replying. And I kinda figured that with the root issue. Just really unsure how else to describe my issue. Any suggestions?
[Verizon Samsung Galaxy S III] buhohitr:
Do you have SuperSu app on the phone? if not download it, if you do open up the app and check see if will update (if it update it should fixed your issue) and what version do you have, should be 1.93
[Verizon Samsung Galaxy S III] aypeeootrek:
Believe it's up to date
[Verizon Samsung Galaxy S III] aypeeootrek:
Not the biggest deal but there are a few scripts I want to run like operation killjoy and the crystal clear
[Verizon Samsung Galaxy S III] buhohitr:
give this a try, uncheck re-authentication and default access change from Prompt to Grant. Run the script command and let me know the error. The issue maybe with the scripts not Su.
[Verizon Samsung Galaxy S III] aypeeootrek:
Same thing. Also, when terminal gains su access, isn't there another line that gets displayed in terminal and then you're allowed to type command. Like it pretty much tells you that you now have access. And the scripts worked previously on w wicked 4.3 tw and some 4.4 roms too
[Verizon Samsung Galaxy S III] buhohitr:
Try another terminal app..
[Verizon Samsung Galaxy S III] aypeeootrek:
I did lol. Tired rom toolbox and terminal emulator. When I get some time, I'm going to restore a nano and see if it works. I'll backup this rom as well and try a fresh install. Thanks for taking the time to try and help
[One (M7) Q&A, Help & Troubleshooting] emezrahi:
Hey all,

I'm desperate for some help. I recently decided to ditch Sense 5.5 and go to AOSP. I installed CM11 stable, with a clean flash. Everything was great except the Bluetooth. I was able to pair the device to the car, but once paired, it would work for about 15 seconds then force close. I looked a little on the forums, and I found some similar issues, which stated to turn the wifi off while using the Bluetooth. Alas, this did not work for me. I then installed, Liquidsmooth (clean flash), which, unfortunately, had the same issue. I am out of ideas. Can someone please help? I'm running S OFF, if that makes a difference.

Thanks in advance.
[One (M7) Android Development] DJLamontagneIII:
SlimKangs by DJLaMontagneIII​

This is a self-compiled build of the Latest SlimKat source that include's added features and build optimizations to enhance Slim's already great experience. Don't flash this if you’re not comfortable with testing out new and possibly broken features. Credits and Thanks to CyanogenMod, Rascarlo, The SlimBean team, BeerGang, temasek, Cristiano Matos, sbradymobile, Paranoid Android, Der_Schubi, fusionjack, sparksco, n3ocort3x, Tbalden, flar2, Faux123, FranciscoFranco, and trippinin@xda for Hosting.

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.
*/

HOW TO INSTALL

First Time Installing

Download the Rom

Download compatible Gapps

Reboot to TWRP, or CWM

WIPE DATA/FACTORY RESET

Flash the Rom

Flash Gapps

Reboot

Already Installed SlimKangs

Download the Rom

Reboot to TWRP, or CWM

WIPE Cache

WIPE Dalvik Cache

Flash the Rom

Reboot

Changelog and Rom Downloads in POST #2

MISC LINKS

Gapps

Kernel Source
[One (M7) Android Development] DJLamontagneIII:
Known Bugs
[One (M7) Android Development] emezrahi:
So no bugs?
[One (M7) Android Development] DJLamontagneIII:
Not at the moment.
[One (M7) Android Development] emezrahi:
OK. I will install in the morning and report back. Thanks for this ROM!
[One (M7) Android Development] DJLamontagneIII:
No prob man its worth a flash the toolchains and build flags make a nice improvement to the snappiness and smoothness of the ui. All kernel settings can be tweaked with TricksterMod.
[One (M7) Android Development] poondog:
Welcome :)
[One (M7) Android Development] DJLamontagneIII:
Thanks man :)
[One (M7) Android Development] kiko3:
Can you cherry pick halo?
[One (M7) Android Development] remix92:
Lockscreen notification included ?
[One (M7) Android Development] DJLamontagneIII:
I can look into it.. Pa might be dropping it for something different that's why its been sitting in the gerrit for a few months so will see.

Don't think so it has Dashckock that has extensions for different notifications like email, hangouts, mms.
[One (M7) Android Development] hedifezai:
Thanks for sharing. I'll download and report back, keep it up.
[One (M7) Android Development] kickassdave:
Was getting some terrible UI lag and stuttering (including during playing music)

Loaded Trickster Mod and FINALLY found switching MP-Decision off (which was on by default) fixed it completely.
[One (M7) Android Development] DJLamontagneIII:
Yea that shouldn't be enabled the kernel uses cpuquiet not mpdecision. Interactive Gov seems better than smartmax too. You have to set up the kernel the way your device can handle this kernel is also OC up to 2Ghz and GPU to 450Mhz some devices may not be able to handle the OC as well as others.
[One (M7) Android Development] kickassdave:
I found the Smartmax governer was just fine tbh.

The MP-Decision setting was the killer, so I hope that is fixed.

On the subject of CPU speed, I immediately limit the CPU to a max of 1674MHz and modify the thermal control immediately and apply -50mV to all frequencies. Anything to reduce the finger melting that this phone is capable of lol.
[One (M7) Android Development] DJLamontagneIII:
Yea it can get hot I always keep mine at 2Ghz. Trickstermod can derp at times I don't even have a mpdecision setting This was the first build anyways it will get better with future releases.
[One (M7) Android Development] Zzoro:
How to set default DPI?
[One (M7) Android Development] DJLamontagneIII:
You can change it in the build.prop or use a app.. Build 2 coming today has dpi changer on the fly build in.
[One (M7) Android Development] DJLamontagneIII:
Update is up!! The Speed up booting on multicore devices commit make a big difference when rebuilding dalvik and art.
[Moto X Q&A] derekwilkinson:
I took my phone out to take a picture and it took fine, but immediately after there was an artifact on them preview screen. I took another picture and now there is definitely something wrong with the camera (seen in top right). I have never dropped my phone or put in a position to be damaged. Any ideas???
[Moto X Q&A] Schaweet:
Dust?

Sent from my Dev Edition Moto X
[Moto X Q&A] derekwilkinson:
I've tried cleaning it multiple times with a microfiber cloth and can't get the spot to even move so I'm not sure if that is the problem :( It is just strange how it was fine one picture and with no change in conditions it has this problem.
[Moto X Q&A] Schaweet:
Have you rebooted? Try force stopping the camera app and clearing the app data. Just a thought.

Sent from my Dev Edition Moto X
[Moto X Q&A] derekwilkinson:
Just tried it and it didn't help. I really don't think it is a software problem, unfortunately. I'm going to see if I can remove the backing of the phone to get a better look at the lens.
[Moto X Q&A] Schaweet:
Yikes.

Good luck!

Sent from my Dev Edition Moto X
[Moto X Q&A] hovax615@hotmail.com:
Get it replaced.

MOTO X Slapped
[Moto X Q&A] derekwilkinson:
I think that is what I'm going to do after looking at the instructions for removing the backing. I wonder if it is even something wrong with the camera ribbon cable.
[Verizon Samsung Galaxy S III] psycdoc:
Hello, I am still learning about custom ROM's, boot loader, etc, so I apologize if my question sounds like a noob one. I have the S III and I have put a custom ROM, boot loader, Kernal, (and radio?). I want to put my phone back to a stock ROM and everything else as I want to sell it on ebay or somewhere else. Can anyone point me to where I can find the stock ROM's and other items to bring back my phone to its "Original" state (or whatever state it would be in if it were to receive the Verizon OTA updates?)

Thanks for your help!
[Verizon Samsung Galaxy S III] buhohitr:
download this image http://www.androidfilehost.com/?fid=23134718111254196 and flash with Odin. After flash once it boot up make sure you disable OTA update. If you have the latest 4.3 stock rom it's harder to sell on ebay. If you want pure stock once boot up just turn off wifi and 4g.
[Verizon Samsung Galaxy S III] psycdoc:
Thank You! One last question where do you disable OTA updates?
[Verizon Samsung Galaxy S III] buhohitr:
If you want to sell it as pure stock, just disable wifi, turn off the phone then remove the sim card, now you can sell the phone as stock. If you disable OTA then the phone is not 100% pure stock since you need to modify couple system files and root the phone.
[Galaxy S 4 Q&A, Help & Troubleshooting] johnny13oi:
Hey guys, I am thinking about buying a Galaxy S 4 on Verizon and using it on t-mobile. What I was wondering is, will the phone have bad battery life? Will it be constantly searching for Verizon signal while I have a Tmobile SIM inserted? Also is the Verizon version any worse than say the Tmobile one? I will be getting a good deal on the Verizon one which is why I am asking.
[MDA III, XDA III, PDA2k, 9090 General] oldpipe:
after i set ringtone and picture for a special contact of someone, it's still not work when the caller calling in. any help?

thanks a lot!!!

SPV M2000 (O2 TaiWan version)

ROM:1.40.06CHT

RADIO: 1.13.00

PROT:1337.42

EXT: 1.40.902CHT
[Nexus 5 Q&A, Help & Troubleshooting] DREWHAMM974:
Where is everyone cherrypicking Lockscreen Notifications from?
[Nexus 5 Q&A, Help & Troubleshooting] Gnome:
Look for it in AOSPAL git.
[Verizon Samsung Galaxy S III] SiawnOverseas:
Using SynergyROM at the moment due to the Pdroid integration. I want to upgrade though to 4.3 or 4.4, and am looking for a ROM that has WORKING privacy controls. Pdroid works fairly well on Synergy and has kept my data from the prying eyes of developers. Any recommendations on a new ROM? Synergy hasn't updated beyond 4.1.

Requirements:

Verizon Samsung Galaxy S3 I535

Android 4.3 or 4.4

Working Camera/GPS

Working Privacy controls.

I've been watching the Android development forum, but it seems like the privacy options have fallen out of the newer ROMS. Did they finally bake the controls into the base kernels?

Siawn
[Verizon Samsung Galaxy S III] Naddict:
As XDA is not a support site, members are expected to do their own research as to what suits them the best...rom recommendation threads get closed as they become arguments over which one is "Best".
[Samsung Galaxy Mega] parasurfer1979:
My phone then reboots and locks on the SprintSpark screen. I only have a mobile phone so I'd love to at least know "why" its doing it. I'm not rooted so phone is completely stock. Only other issue I've had was random reboots but it always worked. Please help me at least go into the Sprint store with a better reason than they would/could through out.
[Samsung Galaxy Mega] parasurfer1979:
Okay... Sprint ordered a replacement. Will be here in a couple of days.
[Nexus 5 Q&A, Help & Troubleshooting] wardawgmalvicious:
I am debating on whether to buy the pro version and flash Franco's Kernel for my Nexus 5 and 7 (2013). I just want to know what I bits of extra I can really do with it.. And if its worth it. I'm more worried about stability than anything I guess. I don't want to run into little issues whether it be audio, video, whatever it may be. Also I have never flashed a kernel or another ROM, I've always stuck with stock. I am running 4.4.2 right now utilizing Gravity Box and Wanam Kit, and a few other modules. Any input would be greatly appreciated. If this thread has been done before, my apologies. I am a brand new forum user, never really get on the computer.