yashsingh1/xdaforums huggingface dataset:
[X 2014 General] mrvirginia:
5.0 Baseband

can someone tell me what their Baseband version is who is running Lollipop 5.0 22.11.6 (the actual OTA)?

Settings>About Phone
[X 2014 General] tebower:
I only copied the executable.
[X 2014 General] SamuriHL:
From a screen shot that someone sent yesterday that I helped get this installed, it's showing as:

MSM8974BP_4125.184.08.26R
[X 2014 General] tebower:
Msm8974bp_4125.184.08.26r, victara_tmo_cust
[X 2014 General] mrvirginia:
thanks. what i have as well.
[X 2014 General] SamuriHL:
Well that's definitely odd. But good to know thanks. The person having trouble with fastboot in the factory image could try replacing the AdbWinApi.dll file in the factory image's Windows directory with the one from platform tools and see if that works.
[X 2014 General] tebower:
Literally I kept all of the files installed by the SDK and just replaced fastboot. Then everything worked. I didn't mess with anything in the Windows folder of the factory image. I took what I needed from the ZIP and ignored the rest.
[X 2014 General] mrvirginia:
Do not tamper

This should go without saying, but for those who tend to be a bit more adventurous like myself, if you have root I strongly advise against tampering with files. Until we have Lollipop Factory Images from Motorola I would suggest holding off.
[X 2014 General] SamuriHL:
Understood. I'm trying to figure out how to help people that downloaded my script that may not have platform tools installed for whatever reason. If switching out the dll ends up being the simple answer then that'd be awesome.

---------- Post added at 02:08 PM ---------- Previous post was at 02:06 PM ----------

OH HELL YES. To this man you listen. :) It's not even 100% sure (I've not seen any confirmation of anyone doing so yet) that a TWRP 2.8.1.0 backup will restore properly, either, so relying on a nandroid to save your bacon may or may not work. If someone's done so I'd love to know that it was successful or not.
[X 2014 General] ShawnGotBANDZ:
Can anyone show how to flash this if you have a Mac? I have recently came back to Android from iPhone and I'm lost. My phone is not rooted and it is the pure edition. I hate to be the person asking to be walked through something but I'm unsure and I'd rather be safe than sorry. Thanks in advance to anyone who's willing to help.
[X 2014 General] SamuriHL:
The process isn't any different on a mac as it is on windows. The factory image contains the darwin binary for fastboot. The commands are fairly straight forward...you flash boot, system, recovery, and modems, wipe the cache, boot into recovery, and use adb to sideload the update. (You'll have to install platform tools for your mac to get adb I think). That's really all there is to it.

P.S. And most people have had to boot into TWRP using fastboot boot twrp.img where twrp.img is the twrp filename and then do an advanced wipe to wipe dalvik cache before booting the new update for the first time.
[X 2014 General] mrvirginia:
a good recommend for everyone who updates, even if they might not need to.
[X 2014 General] ShawnGotBANDZ:
I'm downloading the Android SDK for mac right now. I found a guide on how to set up adb and fastboot, I'm gonna set that up and come back to this thread. Thanks for responding.
[X 2014 General] SamuriHL:
The fastboot included with the SDK won't flash the system img so be sure to use the one that's included in the factory image provided by Moto. ADB will work fine for sideloading, however.
[X 2014 General] ShawnGotBANDZ:
I already downloaded the one from Moto, thanks though! I really appreciate the helpfulness. I'll come back if I have any questions.
[X 2014 General] 0.0:
Can't we just do the process Samuri posted to downgrade and sideload the ota without losing data?

sent from my Moto X (2014)
[X 2014 General] SamuriHL:
I'd be very careful with that if you're on .6. The partition table has changed and you CAN NOT downgrade the GPT partition (the partition table). This is how people bricked previous Moto X devices (the 2013 versions) even when they were unlocked. I'd HIGHLY NOT recommend doing that.
[X 2014 General] mrvirginia:
if you mean downgrade from 22.11.6, i personally wouldn't try that. although the gentleman i spoke with finally emailed me and suggested that, it clearly states on Motorola's own 5.0 Lollipop release notes not to do this
[X 2014 General] SamuriHL:
You updated your post too fast. :p Yes, I agree.
[X 2014 General] mrvirginia:
exactly. so much this. i would not downgrade from the official OTA 22.11.6.

hence my warning of tampering. you could be screwed until we get factory images.

---------- Post added at 03:37 PM ---------- Previous post was at 03:36 PM ----------

yep, i had to re-read the question. i was assuming he was talking about 22.11.5 and not official 22.11.6.
[X 2014 General] SamuriHL:
It's very strange that they changed the partition table in .6 but hadn't done so in .5. This is the strangest release I've seen in years from Moto. I can only think of one other situation that mirrors how this one has gone down.
[X 2014 General] mrvirginia:
ditto. i don't understand why they did that. i do know that the part block for /system is now the same as the 2013 dev edition. maybe the others match. i haven't compared.
[X 2014 General] SamuriHL:
That's not a positive thing. It might be if this build will help them get the 2013 updates out faster (if all devices share the same partition table, perhaps they can share a significant portion of the 5.0 update...maybe). However, when they started messing with partition tables on other devices it's when we started seeing more and more people bricking unlocked devices. Which shocked the hell out of me. There is no way in hell I'd flash this update on a non xt1095 version of this phone. I know people put the .5 release on xt1097's etc but doing so with this release? Not a good idea. Likewise, downgrading to 4.4.4 now imposes significant risk. SIGH.
[X 2014 General] 0.0:
oh darn. well how about an FDR? will that restore the files if I were to tamper with them?
[X 2014 General] SamuriHL:
No. I wish this idea would die. Factory Data Reset does *NOTHING* to the system partition at all. ALL it does is erase the userdata partition and perhaps the internal sdcard, as well. That's it. Nothing more, nothing less. I'm not sure where the myth that FDR would restore system files came from, but, I really truly wish it'd die a painful death. :D
[X 2014 General] SolarTrans:
SAME.

Soooo dumb why people continue to think that.
[X 2014 General] mrvirginia:
I do have a clean system.img, though. doesn't even have root.
[X 2014 General] SamuriHL:
I can create boot and recovery images if you can get me a file off your phone. That'd at least give a somewhat recoverable way to restore devices in emergencies for now. The file I need is:

/system/etc/recovery-resource.dat
[X 2014 General] mrvirginia:
Stock 5.0 Recovery

does anyone still have their stock recovery after updating to Lollipop 5.0 22.11.6?

there was a link posted earlier and that was NOT it. if you do, i can tell you how to pull it.
[X 2014 General] vince0312:
is it safe to update it even rooted previously with the .6 version now?

I just did unlock/root for greenify so far, did not mess with any file system, should have left it alone :(
[X 2014 General] SamuriHL:
See above. I'll generate the signed copy of it.
[X 2014 General] mrvirginia:
https://www.dropbox.com/s/k7yxy87nyd3u6jf/recovery-resource.dat?dl=0
[X 2014 General] SamuriHL:
Thanks. Give me about 30 or so. I gotta make dinner but I'll generate boot and recovery images in a bit and post them for you. They'll be fully signed.
[X 2014 General] mrvirginia:
it will fail if you are saying you're trying to go from KitKat to Lollipop. there is a file that needs to be re-installed. i created an unroot zip that will cleanly remove it. you need to be bone stock first with the exception being root.

---------- Post added at 05:26 PM ---------- Previous post was at 05:26 PM ----------

i have the stock boot.img. just need recovery. i wrongfully assumed recovery.img would have been readily available. thanks!
[X 2014 General] graffixnyc:
It doesn't look like it came with one. I had noticed that with .5 as well. There is no recovery.img in the OTA that I saw.
[X 2014 General] graffixnyc:
I also think it was a bad idea. Honestly, it's the first time I have seen anyone change the partition tables after a device was released. I have seen them do it but only with dev devices not released. By the time it's released the partitions will be different maybe. But I have never come across this where they changed the partitions after a device was released. I mean there is the find 7 change to unified storage but that's because people *****ed about it. I had noticed it when chainfire and I were trying to get root to work. recovery was saying p38 and I scratched my head and thought.. "it's 37 I know that for sure" then saw a lot of them changed. I usually flash stuff using the block number.. good thing I noticed before I flashed something to the wrong place. It could trip up even an experienced guy. I mean I usually never check after an OTA if the effing partitions changed..I guess now I do. :P
[X 2014 General] mrvirginia:
didn't even think to look in the OTA zip. that would be correct.
[MENTION=2812087]SamuriHL[/MENTION] we are good. i have a clean boot.img and system.img. i will pack them together in a single zip and throw it on my server.
[X 2014 General] SamuriHL:
Actually they have. RAZR M/HD were both changed going to 4.4.2 and it really screwed things up, as well. It's a VERY bad idea for Moto to continue doing this.
[X 2014 General] mrvirginia:
it did. i flashed a crap load of stuff to p37 lawl. i flash via block too and just forgot to change that single digit. good thing it's cache and can easily be erased :p
[X 2014 General] SamuriHL:
I can make the recovery image easy enough. Just need a couple minutes of free time and I'll get it done.
[X 2014 General] mrvirginia:
it didn't change from KK so we have it

[MENTION=3537886]graffixnyc[/MENTION]

what does your /system/bin/install-recovery.sh file look like?

from my clean pull, it has all of the moto stuff in it.

now it looks like this:

/system/etc/install-recovery.sh

edit: my /system/etc/install-recovery.cfg file does exist
[X 2014 General] SamuriHL:
Trust me, it changed:

4.4.4 recovery: A5673547C4A78B255CCE3C64AA854A2B

.6 recovery: 50A61059721AB1D3B2D3E2B20289AE58

So yea, it's different. And it matters.

http://www.mediafire.com/download/69e541abgsuabxc/MotoX2014-22.11.6-boot_recovery.zip
[X 2014 General] mrvirginia:
crap. the upload for the other images just finished ahaha alright give me one moment

edit: boot.img is good. ie same as what i have. give me a few minutes to zip and re-up
[X 2014 General] SamuriHL:
Check your boot.img against the one I posted, as well. Mine is generated so it's signed. If yours is the same then good to go. If not, replace it with mine.
[X 2014 General] mrvirginia:
as above. exactly the same :)

and THANKS for the recovery!
[X 2014 General] SamuriHL:
Excellent. I like an abundance of caution with this kind of stuff. At least now you have a way to unbrick in case you mess something up. This is very good.

---------- Post added at 06:09 PM ---------- Previous post was at 06:09 PM ----------

You're quite welcome. I can teach you to make them if you're interested.
[X 2014 General] mrvirginia:
yes, please. if you could maybe write something up, shoot it to me, i'll add it to my arsenal.
[X 2014 General] SamuriHL:
Matt Groff taught me how to do this originally. I incorporated this as automated processes into the House of Bionic and my ODIN building script for the S4 GPE. This is how you do it manually. Automating this is a *****. :)

Extract the OTA zip

Copy the following files to your /sdcard mount using adb push:

system/recovery-from-boot.p

patch/boot.img.p

Previous boot.img (from 4.4.4 FXZ in this case)

recovery-resource.dat from current system partition (alternatively if you only have the previous version's recovery-resource.dat you can patch it for the new version)

Open the META-INF\com\google\android\update-script file in a text editor and search for boot.img.p. You'll find a line like this:

assert(apply_patch("EMMC:/dev/block/platform/msm_sdcc.1/by-name/boot:10444800:3123d161b1deb55f4cbefb11c93efd0ebb7fb1e4:10444800:5842fee35eb6ed6c1a5230254db8073d6ddcccf2",

"-", 5842fee35eb6ed6c1a5230254db8073d6ddcccf2, 10444800,

3123d161b1deb55f4cbefb11c93efd0ebb7fb1e4, package_extract_file("patch/boot.img.p")));

We're going to convert that to an applypatch command. Applypatch has the following syntax:

usage: applypatch [-b <bonus-file>] <src-file> <tgt-file> <tgt-sha1> <tgt-size>

[<src-sha1>:<patch> ...]

or applypatch -c <file> [<sha1> ...]

or applypatch -s <bytes>

or applypatch -l

So in our case, the applypatch command would be:

applypatch boot.img boot5.0.img 5842fee35eb6ed6c1a5230254db8073d6ddcccf2 10444800 3123d161b1deb55f4cbefb11c93efd0ebb7fb1e4:boot.img.p

So you do an adb shell then su then cd /sdcard followed by the applypatch command. This gives you a boot5.0.img on your sdcard

Next we want to build recovery. Open system/etc/install-recovery.cfg. It'll look something like this:

boot_size=10444800

boot_sha1=5842fee35eb6ed6c1a5230254db8073d6ddcccf2

recovery_size=10526720

recovery_sha1=041ca7e306925c40eda26c3bc264019576be9d3a

boot_type=EMMC

boot_device=/dev/block/platform/msm_sdcc.1/by-name/boot

recovery_type=EMMC

recovery_device=/dev/block/platform/msm_sdcc.1/by-name/recovery

bonus_args=-b /system/etc/recovery-resource.dat

Using the syntax from applypatch, we craft the following command using the info from the cfg file:

applypatch -b recovery-resource.dat boot5.0.img recovery5.0.img 041ca7e306925c40eda26c3bc264019576be9d3a 10526720 5842fee35eb6ed6c1a5230254db8073d6ddcccf2:recovery-from-boot.p

That will give us recovery5.0.img on your sdcard

Use adb pull /sdcard/filenamegoeshere to pull the imgs to your local dir.

Enjoy!
[X 2014 General] mrvirginia:
XT1095 Lollipop 5.0 22.11.6 BOOT.img RECOVERY.img SYSTEM.img

Here is a Stock Unrooted Boot/Recovery/System.img for the Moto X 2014 XT1095. This is all we have for now.

Lollipop 5.0, System version 22.11.6, Build number LXE22.39-6

http://apollyon-dev.com/motox/XT1095_Lollipop5_22.11.6_BOOT_RECOVERY_SYS.zip

md5: 6A527AFB1DEED2248AE2D3B4ACCF04ED

here's a mirror

https://mega.co.nz/#!H0wn2LoT!hHqhasTUnLjxMxACvODWcRIrtm3jTGjg1MEqxZfP5lo
[X 2014 General] SamuriHL:
That's awesome. Something we should consider is the modem, as well. I know, I know.
[X 2014 General] mrvirginia:
dude, YES! if someone could pull that haha

also thanks for the write-up. i apparently had to wait for someone to post before replying. it just kept appending my thank you reply to the stock files link

edit: also, the mirror link is uploading. it's not going to finish before i leave work so i'll link it when i get home in about an hour. my server is faster but people have complained about it before for whatever reason.
[X 2014 General] SamuriHL:
For the S4 GPE I can patch modem files, too, and get signed non-hlos and fsg imgs but Moto is doing some weird stuff with how they patch the modems so I can't generate them the same way. They'll have to be dd extracted which means unless you can figure out exactly how many bytes they are they won't be signed. But probably close enough.
[X 2014 General] mrvirginia:
i was just going to say, mine may be messed up (which is why i'd like them) so it wouldn't be good for me to pull them...
[X 2014 General] SamuriHL:
Hopefully someone else can. And someone just sent me this....FML

http://www.androidpolice.com/2014/1...e-means-update-will-fail-system-modified-way/
[X 2014 General] mrvirginia:
ahhh we're good. i have an unroot zip already made for Lollipop too ahahaha. i imagine Motorola would have factory images out if that's how it's going to be moving forward.

i have /system covered. just need to double check modem files.
[X 2014 General] SamuriHL:
We shall see. I'm going to have problems on the S4 GPE for sure. This is going to suck. Badly.
[X 2014 General] Axam:
What is the difference between .5 and .6 in terms of battery drain? I'm aware about changed partition table, new version of baseband and recovery. Anything else changed?

Can someone tell me more details about wakelock issues with .5?
[X 2014 General] mrvirginia:
i'm not looking forward to updating my ROM for that. i'm really not.

the mirror is up for the Lollipop image files

see this post>>>http://xdaforums.com/showpost.php?p=56733038&postcount=1317
[X 2014 General] SamuriHL:
http://xdaforums.com/showpost.php?p=56734350&postcount=506

See that response I got. Maybe it'll make us all sleep better at night I don't know.
[X 2014 General] mrvirginia:
that makes a lot of sense as to why that would apply only to the Nexus line. guess we'll find out soon enough.
[X 2014 General] SamuriHL:
As it applies to Nexus, I couldn't care less as I'll only use factory images to update my NX6 anyway. If it applied to any phone without an image....OMG kill me now. LOL
[X 2014 General] mrvirginia:
[MENTION=2812087]SamuriHL[/MENTION] so the reason i ended up flashing the other recovery was because i thought i'd messed mine up somehow. booting to stock recovery, then holding both volume up/down for about 5 secs and hitting power does nothing with the 5.0 recovery. the old one works as intended. really not sure what's up with that...
[X 2014 General] SamuriHL:
Wonder if they changed the key combo.....AGAIN. It's definitely signed so it's not a corrupt image. That's messed up though.
[X 2014 General] mrvirginia:
yeah i'm positive it's a good img. and that could be the case. i don't care enough to bother with it right now. i only needed it for future OTA purposes haha so thanks again.
[X 2014 General] SamuriHL:
No problem at all. Enjoy!
[X 2014 General] purejoy:
[MENTION=2651267]mrvirginia[/MENTION] same with u, i cann't run the stock recovery after the .6 ota.It hangs on the dead robot and yellow traffic triangle display. If i re-flash the recovery img you upload,can i get the .6 stock recovery back? Thx!

No luck,still cann't trigger the recovery menu by pressing power+ vol up
[X 2014 General] fvc2000:
I'm sorry if this was already discussed here, but I don't think I understood quite well...

The .6 update doesn't have stock recovery, or am I missing something.

On another issue, when I downgraded from .5 to 4.4.4 I had a locked bootloader. Is that the reason I got a error message when I tried to flash motoboot.img?

Although I followed with the downgrade and afterwards I updated to .6 via ota, may I have problems in the future because of that failed motoboot.IMG flash? Or when I updated to .6 via ota, did it get rightfully updated (the motoboot)?

And I swear... Last question. To use the 256bit encryption, I need to factory reset the device on .6? Just reseting through the menu will do it?

Tks already to anyone willing to help!
[X 2014 General] sxp123731:
Once you in dead android logo with triangle, press power button then press volume Up (without releasing power button) you will go to recovery
[X 2014 General] purejoy:
Nice,it's always been there.I had always pressed VOL UP first.Many thanks!
[X 2014 General] kcustom11:
So just to satisfy my curiosity, it's not possible to downgrade or it's just dangerous? And not that I want to downgrade, but how what you go about doing it now that the system block has changed. Maybe that should be in some bold print on some of these threads with stock images.
[X 2014 General] SamuriHL:
If I owned this phone, I wouldn't. Period.
[X 2014 General] phonepersonality:
When I go into my recovery (or should I say 'attempt to'), I have the resting Android with the red exclamation mark/triangle thingie with a 'No Command' statement written in white underneath him.

I wonder if this is because my Lollipop is rooted.

Thoughts?

Oh and I'm also unable to bring up the menu using Vol_Up + Power
[X 2014 General] mrvirginia:
the recovery I posted is 22.11.6 - stock

button combo changed as stated above. power + vol up
[X 2014 General] SolarTrans:
^^This.
[X 2014 General] phonepersonality:
[IMG="Mine lools like this. So lazy!"]http://i59.tinypic.com/qzluft.jpg[/IMG]
[X 2014 General] purejoy:
Yeah,thanks. BTW, Power first,then VOL UP without releasing Power
[X 2014 General] byt3b0mb:
I thought there was a question about whether taking the ota and then restoring to a backup worked. I can confirm. I was stock and rooted then flashed stock 4.4.4 installed .6 ota and have restored my kk twrp backup. I have twrp 2.8.0.1 installed and also can confirm that /system partition is 38
[X 2014 General] purejoy:
[MENTION=2651267]mrvirginia[/MENTION] [MENTION=2812087]SamuriHL[/MENTION] A friend of mine succeed in downgrading to KK 4.4.4 from .6 OTA . At the begining he flashed the .6 ota through KK stock recovery,then he wanted to root his 22.11.6 system through chianfire's method but got some errors when pathcing the kernel. He asked somebody for help but still no luck,hence he decideded to restore to KK 4.4.4. He flashed all main partions including GPT and Bootloader.It's amazing the downgradeing was so smooth without a single error. Now his 1095 even has a 0x600c version bootloader.
[X 2014 General] mrvirginia:
maybe the bootloader is why. not sure. I still wouldn't risk it lol
[X 2014 General] SamuriHL:
I know you claim "Without a single error" but if gpt or motoboot were flashed, there were errors. Those cannot be downgraded. I'm happy it seemed to work for your friend but it's not something people should be doing. You have no idea how many "foolproof downgrade guides" have been posted that seemed to work for one or two people and bricked others following the exact same steps. Some people get lucky and it works for them. Others find themselves in a much different position. You can roll the dice if you choose, but I wouldn't on a 500 dollar phone.
[X 2014 General] jadsru1:
Hold both together for 4 secs or so, release power then hold vol up a little longer before release.
[X 2014 General] etoile:
[MENTION=2812087]SamuriHL[/MENTION] and [MENTION=2651267]mrvirginia[/MENTION], I would like to clarify one thing. Like everyone I was on the .5 before and followed [MENTION=2812087]SamuriHL[/MENTION] instruction and script to downgrade and upgrade again to .6. I was on the locked bootloader. So that twrp booting was failed and end up wiping user data and cache. Everything fine so far.

After following this thread and found out that you guys are saying .6 recovery isn't in the zip. Which mean not in the [MENTION=2812087]SamuriHL[/MENTION]'s one? If so do I still need to flash the recovery alone what you guys are talking about awhile ago?

Thanks!
[X 2014 General] SamuriHL:
No. That's not what was said. They were looking for recovery.img in the OTA zip file but it's a generated file not just included. It's included in factory images, though, but, we don't have one for .6 yet. What you have is fine.
[X 2014 General] etoile:
Thanks a lot for the clarification [MENTION=2812087]SamuriHL[/MENTION]. Also appreciate your effort for the script and instruction.

Cheers!
[X 2014 General] ShawnGotBANDZ:
Hello, just an update. I just dragged and dropped onto My phone via usb and ran as update from sd card and it flashed just fine without having to do anything else.
[X 2014 General] JarJarWinks:
Does the lollipop update fix the lag in the front camera in low light situations?

MY DEVICES: Moto x 2014 (XT1092), Nexus 7 2013 (razor), HTC Desire X (proto)
[X 2014 General] matt99017d:
The lag is 100* better
[X 2014 General] tjarvis:
anyone working on an advanced power menu? I hate having to play finger twister to boot to recovery... I'm planning on yanking out an android.policy.jar from kitkat and plug it in to see what I come up with. I'll post if I get something good. If I get a bunch of force closes and/or bootloops I'll let you know.
[X 2014 General] tiaoalvino:
https://play.google.com/store/apps/details?id=phongit.quickreboot

It's not an advanced menu, but, works! :D

It needs root. :good:
[X 2014 General] tjarvis:
thanks! still want a menu from the power button though... I think I will continue my tinkering, I found an android.policy.jar that has what I want so I'm backing up now and then I will inject. *fingers crossed*