yashsingh1/xdaforums huggingface dataset:
[X 2014 General] tKoHaXoR:
I was already on 5.0 stock pure edition rooted with unlocked bootloader and TWRP recovery installed and did these steps to get 5.1 on my Moto X

Tutorial is NOT NOOB PROOF. Follow at your own risk.

MUST HAVE MOTO X DRIVERS INSTALLED ON PC

Moto X USB Drivers

Back up your data to your computer (pics, music, etc.) and copy the 5.1 update file to your phone storage

5.1 OTA UPDATE FILES CAN BE FOUND ON FIRST POST

EASY WAY (If you have TWRP Backup of Stock unrooted):

- Reboot to TWRP and Wipe/Factory Reset

- Restore TWRP backup of stock 5.0 unrooted if you have it

- Flash stock recovery.img file from 5.0 LXE22.46-11 Build (Link Below) thru mfastboot

mfastboot flash recovery recovery.img

- Boot to stock recovery and apply 5.1 update

- DONE.

HARD WAY:

1. Flash 5.0 Build: LXE22.46-11 with mfastboot v2 to get back to stock

MUST HAVE BOOTLOADER UNLOCKED + RECOMMENDED TO DO OVER 5.0 BASE ONLY - ONLY TESTED ON X1095

NOT TESTED ON 5.1 LEAK BASE POSSIBLE BRICK

5.0 Build: LXE22.46-11 Pure Edition Stock Image Files

MFastboot v2

- Unzip 5.0 Build: LXE22.46-11 image files and mfastboot files to same folder

- Boot phone in fastboot mode and plug phone to computer (Power off phone and hold

Volume Down + Power

)

- Open command prompt by right clicking on folder where files are in while holding shift and type "mfastboot devices" to make sure mfastboot is detecting your phone

- Flash images with these easy commands to get back to stock

mfastboot flash boot boot.img

mfastboot flash recovery recovery.img

mfastboot flash system system.img

2. Boot to stock recovery and and flash update from phone storage

3. Reboot and you should now have 5.1

4. Power off and boot into fastboot again and mfastboot flash TWRP recovery

mfastboot flash recovery twrp-2.8.6.0-victara.img

TWRP 2.8.6 Latest recovery for Moto X

Optional: Make TWRP backup of 5.1 fresh install before using phone and restore your backed up files to your phone if anything was erased during this entire installation process)

5. Reboot and you should now be on 5.1 OTA with TWRP recovery installed

6. PENDING (Will post how to root 5.1 later)
[X 2014 General] phamine:
I've found that the radios(baseband) update with the OTA. No need to update individual radios.

5.0

5.1
[X 2014 General] pro.gangster:
So is there any benefit of moving from first soak test to second one? or is there any benefit of second soak test over stock 5.0?
[X 2014 General] prasad.adam:
Followed what is mentioned in the OP and now on latest lollipop. [emoji4]
[X 2014 General] billteeth:
I am guessing that the differences between this and the previous 5.1 soak test are nearly unnoticeable, but I'd love to hear from someone with an opinion on it.
[X 2014 General] Mnemoch:
When did 23.11.14 come out? Thought it was final (oops) and sideloaded today, now I see them announcing that still in soak test, and that they fixed an issue "last week".
[X 2014 General] gowboy84:
I have been trying to for the last ten hours, I'm stuck with 60.16 bootloader no matter what I do. Every time I finish fastboot flash everything I try to install Ota but get fingerprint error. I am out of options please help
[X 2014 General] tKoHaXoR:
Is your bootloader unlocked? Did you reboot into system once 5.0 was installed? Do you have the XT1095 and not another variant of the moto x?
[X 2014 General] MrMeeseeks:
I don't buy these instructions not to flash partition and motoboot. There is a reason Moto specifically tells you to on their own website. I say this because, after all the talk of not doing it and how dangerous it was, I decided not to flash those. I downgraded to 5.0 but then decided to upgrade back to the latest 5.1 soak. Bad idea. Now I have a $500 paperweight. This never happened when I downgraded to 4.4.4 and flashed partition and motoboot. I was able to take OTA's with no problems. I will follow Motorola's instructions from now on. After all, wouldn't they know how to properly flash their own software more so than some random person on a forum?
[X 2014 General] wolfu11:
I agree with you but I think there's a real issue with the 23.11.14 soak.

Were you on the 23.11.14 soak or the 23.1.28?

I never had a problem downgrading to 4.4 via moto website instructions and taking the OTA to 5.0 then side loading the 23.1.28 soak;

I've done that many times my bootloader went from 60.14 back to 60.11 during the 5.0 ota.

Once I tried the 23.11.14 soak my bootloader went to 60.16 and when I went to 4.4 downgrade I tried to side load the 4.4 to 5.0 because of all the warnings on here about taking the OTA and the same thing happened to me. Instant brick I called Moto and am getting a warranty replacement. But I will no longer try these soaks posted on here.

Moto pulled the 23.11.14 soak right away saying there was a problem but didn't state what it was.

For those of us silly enough to try it we are at the mercy of the bootloader issues.

This crap has even happened to the Nexus 6 but CCFRIES released the files for that one and people are able to fix it themselves. http://xdaforums.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518

Thankfully I have my rock solid Nexus 5 as a back up to get me through until my replacement arrives.

Hopefully you get a replacement and it all works out for you.
[X 2014 General] MrMeeseeks:
I think you're right because I was on the 23.11.14 soak as well. And I've heard of others bricking while on that stupid 60.16 bootloader. I have never bricked a device until yesterday, and I flash stuff all the time. :crying:

Update: Just got done talking to Moto and they are sending me a replacement. :good:
[X 2014 General] tonyleeloveyou:
-The Guide to do this can be found on Motorola's site here >>>>> https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images

The guide is at the bottom below downloads.... Make Sure you follow those instructions carefully as I am NOT RESPONSIBLE for you bricking your device!

DO NOT FLASH bootloader (motoboot) and partition table (gpt) Thanks JulesJam :)

I unlocked my phone to downgrade to 5.0,but i couldn't relock the phone according this instruction
[X 2014 General] prasad.adam:
Little sluggish after some use.

I have found that the version in the OP starts to stutter after some prolonged usage (possibly a memory leak issue). The one below is the latest version and seems super fast and no sluggishness issues. I would recommend below one:

http://xdaforums.com/moto-x-2014/general/ota-t3132045
[X 2014 General] ice20978:
Any update for 23.16.3?

Maybe since the final version is out now, we will get a direct update from 23.1.28... has anyone still on this gotten one?
[X 2014 General] projectzero_droid:
after update to 5.1 OTA i found out that sleep display not working anyone get the same problem ?
[X 2014 General] Jmaniac55:
Is it giving you any sort of error when you try to relock??
[X 2014 General] Jmaniac55:
Can't say that I have really, my works perfectly
[X 2014 General] Jmaniac55:
I wouldn't be so quick to blame the guide seems how you are the only one claiming to have a $500 paperweight. I was told that you shouldn't flash those by a senior member here so I think he would know.

What exactly happened that got you to that point? Maybe we can help :)
[X 2014 General] MrMeeseeks:
I'm not the only one who bricked this way. Does your senior member work for Motorola? No. Did he/she develop the software? No. But what I know is I have never bricked after flashing partition or motoboot but I did the one time I didn't flash them.
[X 2014 General] Jmaniac55:
okay well can you explain what happened? Maybe we can fix it
[X 2014 General] MrMeeseeks:
Well, I was on the soak with the 60.16 bootloader. I think it was build number 23.1.28. I downgraded to 5.0 using the files from graffixnyc. That when fine but I didn't flash partition or motoboot. When I tried to update using the same soak I was originally on, the phone shut down. Now it won't power on at all. You can't get into fastboot or anything. I don't know that it had anything to do with not flashing the bootloader and partition, but I never had any problem when I did flash those two when downgrading to KitKat.
[X 2014 General] Dark9781:
23.1.28 had a bootloader version of 60.14. The bootloader for 23.11.14 was 60.16. If your bootloader version was 60.16 then you were on 23.11.14. Sounds like after you downgraded to 5.0 you may of accidentally flashed 23.1.28 causing the bootloader to be downgraded which in turn caused a brick.
[X 2014 General] Jmaniac55:
I would have to agree with dark there that sounds about right, although if you unlocked the bootloader like you were supposed to, it shouldn't have been a problem
[X 2014 General] MrMeeseeks:
My bootloader was unlocked. That's one of the first things I did when I got the phone.
[X 2014 General] Ownage516:
Since this thread was made on June 1st, the actual OTA has came out since then. I'm sorta a noob when it comes to android, so if anyone can help me out, that would be awesome.

So I sideloaded the 23.1.28 soak. Do I still follow the instructions from the orginal guide? Because the OTA is now 23.16.3.
[X 2014 General] Dark9781:
Yes. You will need to downgrade back to 5.0 before you can take the ota.
[X 2014 General] Jmaniac55:
okay, was your phone charged when you attempted this? have you tried leaving it plugged in for a while?
[X 2014 General] MrMeeseeks:
Battery was at 80-85 percent. But it's OK. I've already sent it in for a warranty replacement.
[X 2014 General] Jmaniac55:
Well I am sorry you had this experience
[X 2014 General] adm1jtg:
Just my 2 cents on this... I am on bootloader 60.11 the original bootloader that came with the phone and 5.0 Since receiving the phone I have flashed the system.img and boot.img for kk and 5.1 and 5.0 and moved back and forth multiple times without an issue at all. Notice I DIDNT mess with the gpt or the bootloader at all and i DID do a factory format after changing system mversions. I have had no issues on any of the 3 configurations other then known system issues. It is perfectly feasible to fastboot ONLY system and boot and have a fully working system on whatever version os.

Thus like was stated above NO NEED FOR BOOTLOADER OR GPT to be flashed. So why do they update these... who knows but I have not seen anything on a user level that would make me believe they need to be updated
[X 2014 General] Dark9781:
They only update it to patch security holes and my personal opinion is to prevent people that don't know what they are doing from screwing up their devices.
[X 2014 General] walrusmonarch:
The gpt is the partition scheme, so if any of the partitions need to be altered (size increase etc.) for the new firmware, you will need to flash it. As for the bootloader, they patch security holes, etc. The new baseband/modem may require it as well. These changes may not be visible to the user, but that doesn't mean they are not there. It's not like they update bootloaders just for fun :)

The fact that downgrading bootloaders/gpt can sometimes lead to bricks is unfortunate. However, I don't think Motorola intended these to be open to downgrading. They should put some kind of warning about this on their factory image pages and add checks to their OTA scripts...
[X 2014 General] Dark9781:
Their usually are checks in the OTAs that will prevent bootloaders from being downgraded, but for whatever reason bootloader version 60.16 slips through the check. As for a warning on their image site, there are warnings and the images are available for Developer editions only. Most people are getting the images from other sources which don't provide warnings.
[X 2014 General] livefree79:
Seriously thank you for the guide. I followed a youtube guide on how to install the first soak. Under the impression I'd still get updates. But we all know that's not true. So I followed this guide downgraded to 5.0. After first boot I had a 5.1 update waiting. Phone works just like it should. Nice to be back on official software. Nice to know I'll get updates again. So thank you for your time in writing up the guide.
[X 2014 General] hizzy06:
Do I have to use moto fastboot or can I just use the regular fastboot?
[X 2014 General] morCrckrsPlz:
Hey I'm not very experienced. When you say "do not flash motoboot or gpt" does that mean just delete those files from the zip before transfering over to the device?
[X 2014 General] morCrckrsPlz:
disregard that comment. I currently have the 5.1 soaktest, which I installed manually by moving the file onto my phone, entering fb mode, and installing it from there. I was under the impression that I would install these the same way. Can anyone clarify why you have to downgrade. I've had another senior member tell with with confidence that I can flash the newest version (motoboot, partition and all) straight from my current (soaktest 23.1.28) version.
[X 2014 General] AGISCI:
You do not need to downgrade. In the past downgrade was the only way BEFORE the full firmware was released. Downgrading so that you can upgrade is dangerous. Many people have bricked their phones permanently by downgrading then trying to upgrade to the latest version. You should never downgrade unless you have a good reason. And downgrading to then later upgrade is NOT a good reason.

The full firmware for 5.1 with the stagefright patch is now available which makes downgrading unnecessary and unsafe.
[X 2014 General] hizzy06:
So I can just flash the latest 5.1 image from the moto website without downgrading?
[X 2014 General] AGISCI:
Correct, downgrading is not necessary and is unadvised.
[X 2014 General] hizzy06:
Hmm okay. Do I follow the same instructions on the moto website as well? I'm currently on 5.1 soak test and would like to go to the official 5.1.
[X 2014 General] AGISCI:
Yes the instructions in their website are what you need to follow.
[X 2014 General] hizzy06:
Thanks appreciate your reply sir. Last question, do I flash motoboot and gpt?
[X 2014 General] AGISCI:
Yes.
[X 2014 General] HCanseco:
Looking forward

Already updated but now im looking a way to get root again?

Already got a method?
[X 2014 General] AGISCI:
Flash TWRP to the phone. Run TWRP. When you exit TWRP it will ask if you want to root. Super simple stuff.
[X 2014 General] pen_sil:
hi mate

did u successfully upgrade your device to the latest 5.1 without downgrade to 5.0 first??
[Galaxy S 5 Q&A, Help & Troubleshooting] Meggaboo2:
Hey all!

So I just got the S 5 about a month ago and I was messing around with the box today out of boredom and I saw the headphones. Tonight, I was going to plug them in so I could fall asleep to music but they don't stay in the adapter? I've never had a galaxy before so I don't know if they have a certain way the headphones go in but the headphones that came with the phone don't fit into the phone. Help? ??
[Galaxy S 5 Q&A, Help & Troubleshooting] Safe0716:
Then you probably have fake ones, because the OEM headphones perfectly fit in the S5 without any adapter, why on earth would Samsung give headphones that aren't compatible with the phone ?

And yeah it's just a basic 3.5mm, like most headphones out there
[Galaxy S 5 Q&A, Help & Troubleshooting] Meggaboo2:
Well they can't be fake if I got them from the Verizon store with the phone.
[Galaxy S 5 Q&A, Help & Troubleshooting] andROIDS:
Take everything back to Verizon and show them.
[Galaxy S 5 Q&A, Help & Troubleshooting] Bodisson:
Are you sure you are plugging them all the way in?

I had a similar problem on my SGS4... but it was me not plugging them correctly...
[Galaxy S 5 Q&A, Help & Troubleshooting] Meggaboo2:
I thought that so I was very aware of what I was doing and I am plugging them in all the way, they just don't stay plugged in.
[Galaxy S 5 Q&A, Help & Troubleshooting] lingowistico:
Yeah you're not plugging them in all the way. It's kind of a new thing, the 3.5 port is harder to plug in to than on previous models. If there's even the slightest gap between the plug's rubber and the phone's 3.5 port and you can see the plug's metal then you're not plugging it all the way in. Otherwise go back to verizon store and explain your problem
[8125, K-JAM, P4300, MDA Vario Software Upgrading] Lunatixz:
Hi can somebody please post the 2.19.11 G3 Wizard radio rom...

I need to downgrade because of missed calls, but can't find my copy of the old rom..

Thanks

Please post just the radio update if you have.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] mattk_r:
I would have said to start with the Wiki if you have a need for info: Wiki, however I didn't see it posted.

Here it is: 2.19
[8125, K-JAM, P4300, MDA Vario Software Upgrading] ChristoA1:
Can this be used on an unlocked G4? Still waiting on info from IMEI-Check... Unlike yesterday, no emails from them today...
[Galaxy S 5 Q&A, Help & Troubleshooting] entalent:
I'm using a Chinese version of Galaxy S5, and the model is SM-G9006W. It's a dual-sim phone, supporting TD-LTE network(baseband version is G9006WZNU1BOE3 ). But the stock ROM has no Google service installed, and could not install any google apps, including chrome...:crying: So is there any custom ROM, for example some version of Cyanogenmod(with google services) that may work for this device? Thank you!
[Xperia Z3 Q&A, Help & Troubleshooting] marchingknight11:
I'm looking into unlocking the bootloader on my Xperia Z3 (D6603). I'm wondering if A) it can be done without entering a code on the Sony website and B) if it will actually void my warranty if I have a hardware failure. I've read things about laws differing in different countries but no one has actually said what they are in the different countries. I live in the US. if I unlock my bootloader and then I find a manufacturing defect, will Sony fix it under warranty or am I SOL?
[Xperia Z3 Q&A, Help & Troubleshooting] gregbradley:
No

Yes, it says so on the Sony Website

They may fix it, but they will charge you through the nose for it.
[G3 Q&A, Help & Troubleshooting] GiladP:
Hey there

I took out my SD card for about a week for some reason, and after trying to put it back in, the phone doesn't see that card..

I've tried another SD card and it doesn't work either

I've tried both SD cards on a different phone and both of them are working...

Does any1 have any idea of what could've happen?

I've tried restart the phone with and without the card and it is still the same, with SIM card even...
[Nexus 6  General] vikramjatt11:
My Nexus 6 purchased straight from Google finally shows on Verizon. I was able to apply my $25 off month-to-month no contract discount, just called in and they applied it right away. Also, on Verizon wireless, it shows my device as "Nexus 6 Non VZW".
[Nexus 6  General] akellar:
All known and been discussed for a couple weeks in the Verizon thread that already exists
[Nexus 6  General] crachel:
Thanks, looks like there's already some discussion of this here

Closed
[Galaxy Grand 2 Q&A, Help & Troubleshooting] marcoscousseau:
Hello, i have the SM-G710 version, a grand 2 whithout LTE, NFC and dual sim.

This version is in 4.3 jelly bean, i download roms of Cyanogenmod 12, to see the asserts in the updater-script

assert(getprop("ro.product.device") == "ms013g" || getprop("ro.build.product") == "ms013g" || getprop("ro.product.device") == "ms01lte" || getprop("ro.build.product") == "ms01lte" || abort("This package is for device: ms013g,ms01lte; this device is " + getprop("ro.product.device") + "."););

"ms013g" is the SM-G7102

"ms01lte" is the SM-G7105

the SM-G710 is "ms013gss"

Is logical what the build product names are different, but the mainboard is the same:

Galaxy Grand 2

<ro.product.model>SM-G710</ro.product.model>
<ro.product.name>ms013gssxx</ro.product.name>
<ro.product.device>ms013gss</ro.product.device>
<ro.product.board>MSM8226</ro.product.board>
<iso.3166-a3>INT</iso.3166-a3>

Galaxy Grand 2 Duos

<ro.product.model>SM-G7102</ro.product.model>
<ro.product.name>ms013gxx</ro.product.name>
<ro.product.device>ms013g</ro.product.device>
<ro.product.board>MSM8226</ro.product.board>
<iso.3166-a3>INT</iso.3166-a3>

Galaxy Grand 2

<ro.product.model>SM-G7105</ro.product.model>
<ro.product.name>ms01ltexx</ro.product.name>
<ro.product.device>ms01lte</ro.product.device>
<ro.product.board>MSM8926</ro.product.board>
<iso.3166-a3>INT</iso.3166-a3>´

Galaxy Grand 2

<ro.product.model>SM-G7105L</ro.product.model>
<ro.product.name>ms01lteub</ro.product.name>
<ro.product.device>ms01lte</ro.product.device>
<ro.product.board>MSM8926</ro.product.board>
<iso.3166-a3>LAT</iso.3166-a3>

The question is, what changes need the rom to can someone develop a port of CM?

Thanks!
[Galaxy Grand 2 Q&A, Help & Troubleshooting] gracefang:
This is not the right place to ask questions post you questions and queries in the Q and A section so kindly ask your question at the right place
[Sony Smartwatch 3] supac:
This new update is garbage, greatly reduced my battery life, wifi off, cloud sync off, minimal apps installed.

How do I rollback update?
[Sony Smartwatch 3] tmlrem:
Thru companion app :) im going to do the same...

---------- Post added at 06:38 PM ---------- Previous post was at 05:54 PM ----------

After trying it out it seems like Sony updated the companion app with 5.1 aswell. From here im not sure how to roll back.
[Sony Smartwatch 3] fer2503:
sony pc companion says: Sony Update Engine doesn't have software available for your phone

any solution?
[Sony Smartwatch 3] Sievers:
My guess would be that you would have to find the 5.02 image file on the forums and flash it through ADB.
[Sony Smartwatch 3] senectus:
I'm not sure you can.

If fact if you could I suspect OTA would update without asking you.... The update before the last one did for me.. I had it on charge looked over to it and it was rebooting after installing the update. No warning, No questions... just did it.
[Sony Smartwatch 3] gtriamy:
So I wondered this at the last update--from v4 to v5--and after much research, AndroidWear is very much like any Android rom on a phone or tablet. Officially, going backwards in an update is impossible using the stock recovery because each OTA only allows for an update from x version to y version and will error if you try to update from w version. The only way to get backwards is to unlock the bootloader, replace the recovery with something like TWRP and flash an old image. Among many problems that you might experience though is that OTAs are not system images in that they sometimes they only update specific partitions. In short, you run the risk of bricking your watch, just as you could with a phone or tablet.

If you can live with it, keep it. If you can't, start doing your research.
[Sony Smartwatch 3] dan-htc-touch:
Isn't there a repacked stock rom in development forum? It gets flashed via twrp
[Sony Smartwatch 3] Sean09:
Is there a way to block updates from getting pushed to the watch?
[Xperia Z1 Compact Q&A, Help & Troubleshooting] thenexus6:
Happened to me earlier today, only getting volume through the left headphone with my apple EarPods. The port seems a little loose, I can spin the cable around and they always come out by accident. I just tried with some bigger sony over-ear headphones and they work fine.. but I am not using them for outside use.

Any advice or tips or am I boned? I listen to podcasts every day for a few hours so this is a bummer.
[Xperia Z1 Compact Q&A, Help & Troubleshooting] AMDFenics:
Look for dirt in the jack port. Try carefully to clean it out, may a toothpick will help you ;)
[G4 Q&A, Help & Troubleshooting] monkmeister901:
I'm pretty sure I've ready somewhere that the G4 has slomo video recording, but I have no idea how to make it work. Has anyone else played with this feature?
[G4 Q&A, Help & Troubleshooting] jimmydigital00:
Click on the settings icon and then the 16:9. This will give you all of the shooting options. One of them is Slow-Mo