Hi guys!
Just saw at SBf Developers that hey have uploaded some new updates there.
AS my comes from Brazil, i saw that fastboot-ghost_retbr-user-4.2.2-13.9.0Q2.X-116-LCX-35-36-release-keys-cid12-Brasil-BR.tar.gz is avaliable. But my question is: how can i flash this kinda if files since they arent RSD lite type and are fastboot ones? Do i need unlocked bootloader?
If someone can help me, i appreciate a lot!
AFAIK, RSD is only a front end for fastboot, so technically you can flash those files with fastboot, because they are stock and signed by motorola (no unlocked BL needed). You just have to know the partitions in wich you're gonna flash each file
waiflih said:
AFAIK, RSD is only a front end for fastboot, so technically you can flash those files with fastboot, because they are stock and signed by motorola (no unlocked BL needed). You just have to know the partitions in wich you're gonna flash each file
Click to expand...
Click to collapse
Thanks my friend! But do uo have the steps for this? Cause i couldnt found any specific to Moto X.
As i unzip the tar file, i have these files as attached.
I don't have the exact steps, but you can look at the flashall.bat file inside your zip
regards
waiflih said:
I don't have the exact steps, but you can look at the flashall.bat file inside your zip
regards
Click to expand...
Click to collapse
Thanks again!
Any ideas?
Do you have the phone in fastboot mode and connected to your PC while running the BAT file?
xitake said:
Do you have the phone in fastboot mode and connected to your PC while running the BAT file?
Click to expand...
Click to collapse
No,but as the programa asks, i don have a JTAG flex?
xpc21 said:
No,but as the programa asks, i don have a JTAG flex?
Click to expand...
Click to collapse
I also didn't know what a JTAG flex is. After some googling, it seems that it is a sort of cable for flashing the image directly to the memory, internally, like in the photo below (not a Moto X).
So, I assume you don't have a JTAG flex connected, right? So it should be good to go
xitake said:
I also didn't know what a JTAG flex is. After some googling, it seems that it is a sort of cable for flashing the image directly to the memory, internally, like in the photo below (not a Moto X).
So, I assume you don't have a JTAG flex connected, right? So it should be good to go
Click to expand...
Click to collapse
Have you my friend flash or know about fastboot program? Case i have in more popular android phones but Moto X is so new that i dont wanna risk doing something wrong.
Flahing stock SBF
xpc21 said:
Have you my friend flash or know about fastboot program? Case i have in more popular android phones but Moto X is so new that i dont wanna risk doing something wrong.
Click to expand...
Click to collapse
Try this maybe it'll work
1. Connect your Moto x, make sure developer options is enabled and tick usb debugging.
2. open command window on the folder including the new extracted firmware.
3. Type adb devices to confirm that Moto X is detected by your computer.
4. Type adb reboot bootloader, Moto X will reboot in fastboot mode.
5. Run the batch file flasfall.
wait until it finishes it might take sometime, and you'll see the flashing process on both computer and Moto X.
kkhadr said:
Try this maybe it'll work
...
wait until it finishes it might take sometime, and you'll see the flashing process on both computer and Moto X.
Click to expand...
Click to collapse
Is it OK to do this if the phone is rooted and modified with xposed modules?
Also, from what I can see, this is the version .35
So as it is older than .51, pwnmymoto should still work, right?
Anyone else?
[email protected]
xitake said:
Is it OK to do this if the phone is rooted and modified with xposed modules?
Also, from what I can see, this is the version .35
So as it is older than .51, pwnmymoto should still work, right?
Click to expand...
Click to collapse
If this version includes the camera patch then it won't be rooted, but I flashed TMO 4.3 the test build it's working great but off course I lost root, and I'm sure in a few days it will be rooted again, so nothing to fear.
this is the OPs 3rd post about the same topic. One under q&a, one under dev that got moved to q&a, and now one under moto x general. Someone needs to teach him a lesson because he has gotten responses on all three threads. Really frustrating. Won't be getting anymore help from me...
Looks like fastboot-ghost_retbr-user-4.2.2-13.9.0Q2.X-116-LCX-35-36-release-keys-cid12-Brasil-BR.tar.gz have the same camera app as in ATT, TMO, Sprint after OTA (with improved camera). Camera app in new Brazilian firmware have version 3.0.211 - the same as in TMO rom with OTA installed.
Kind of straight forward
You just need to unpack the tgz container. Inside the folder there is a bunch of files.
I'm my case since I'm using OSX I just ran flashall.sh and done. There is a flashall.bat that I believe is designed to work with windows.
Put your phone in bootloader mode, connect the cable, go to folder the files lies and run the command. In about 5 minutes it is done. :good:
Have anyone tried it? I was trying to wait for the official OTA update, but it's taking too long. I need to know if it's safe.
Oh, and what if I use other flashboot file like from Verizon instead of the brazilian retail one? Is there any problem?
rodrigorox said:
Have anyone tried it? I was trying to wait for the official OTA update, but it's taking too long. I need to know if it's safe.
Oh, and what if I use other flashboot file like from Verizon instead of the brazilian retail one? Is there any problem?
Click to expand...
Click to collapse
rodrigorox,
I have called motorola on friday and it seems we will be getting the update in the next week or so...
I'd hold on on flashing it if all you look for is the OTA that US got.
Related
Here are the .IMG files that Motorola has posted on their MOTODEV site. .
ATTENTION: DO NOT ATTEMPT TO FLASH THIS FILE ON ANYTHING BUT THE VERIZON WIRELESS MOTOROLA XOOM Z600 (3G MODEL) OR YOU WILL HAVE A SHINEY PAPER WEIGHT!!!!
These files are from Motorola's Development site but I take no liability with anything that happens with your device if something goes wrong.
Official HRI39 Motorola .IMG files:
http://www.multiupload.com/9XP1B8LSWC
Official HRI66 Motorola .IMG files:
http://www.multiupload.com/POUDJY1255
The following are the steps from the MOTODEV site
1. Extract files into android sdk /tools folder.
2. Start command prompt/ terminal from the android sdk tools folder. (How this is done on Mac I do not know, Windows: shift+left click and select "open command window here")
3. adb reboot bootloader
4. fastboot flash boot boot.img
5. fastboot flash system system.img
6. fastboot flash recovery recovery.img
7. fastboot flash userdata userdata.img
8. fastboot erase cache
9. fastboot oem lock
The device will lock and reboot.
You are now back to out of box state. However I do not know if it is still detectable by VZ Moto if you have unlocked the device after doing this.
Also fyi the sbf file is still an option but you will have to go in and do the fastboot oem lock after it completes
u mispelled cache
Fixed. Thanks had a long day and missed that at proof reading
Thanks for the files, does seem a lot simpler to just use the sbf file though.
bwcorvus said:
Thanks for the files, does seem a lot simpler to just use the sbf file though.
Click to expand...
Click to collapse
Its always good to have more options and the Xoom gives us many and hopefully soon sdcard support will provide the final key piece, the CM recovery!
In the meantime it is very good to have all of the official files at our disposal.
If anyone is wondering what the the reflash file from the first leak is, it is an SBF format installation of the stock boot image and a blank user data image to wipe data and return to stock via RSD Lite without touching the system partition.
This provides yet another way to reset that should be examined, especially if it works over a modified system partition.
We also may be able to use any or all of these files to build our own SBF files and other one step solutions for recovering and or modifying the Xoom. This can be very valuable and must also be thoroughly explored along with the NVM so we can really start to tak better control of the radio functions.
Lots to look at...
I am in love with fastboot. I am so use to the days of the OG Droid where the bootloader wasnt locked but you didnt have fastboot as an option. I can see a lot of easier days in the Dev community coming.
jmc2543 said:
I am in love with fastboot. I am so use to the days of the OG Droid where the bootloader wasnt locked but you didnt have fastboot as an option. I can see a lot of easier days in the Dev community coming.
Click to expand...
Click to collapse
Yea having these images is one BIG step...now we just need sdcards
Just finished doing this. I'm back at stock. Of course no I'll b the last to get an update. And by the same time tomorrow I'll be unlocking and re-rooting.
by doing this does it erase everything on your xoom?
bishop72 said:
by doing this does it erase everything on your xoom?
Click to expand...
Click to collapse
Yes it would. Itll bring it back to what it was like when you first bought it.
For those that updated, were you able to reroot?
17akota said:
Yes it would. Itll bring it back to what it was like when you first bought it.
Click to expand...
Click to collapse
I saw multiple threads about Titanium backup not working with the Xoom. Are there alternative apps that will save all my configuration like home screen layout etc? It was a lot of work B-)
Sent from my Xoom using Tapatalk
It is just Android 3.0
3.0.1 is HRI66
Do I need to do this if I have rooted, just unlocked? Can I just "fastboot oem lock" and be good to go?
Aaron636r said:
Do I need to do this if I have rooted, just unlocked? Can I just "fastboot oem lock" and be good to go?
Click to expand...
Click to collapse
Oh no. I did the "fastboot oem lock" and now I get "Failed image LNX 0x0002". Cant boot past Dual Core logo screen.
Ok, re-unlocking it fixed it.
Ok so we have the original flash so we can get the OTA thats great. And Moto confirmed on their forum they will upgrade devices that have been unlocked and rooted. If they cannot install the software they will ship it back with just the new hardware. Can't wait to see what people can really start doing now.
For those of you that are like me and hate having to using mega upload and crap to download things here is a direct link on my web server to the file released by Moto.
DMCA Noticed by Moto
This was taken directly from the Moto Dev site myself.
If you browse the directory, which I think I left on for this one... There is also the sbf archive and RSD there to download. If anyone needs a place to store some files let me know. I have unlimited storage and bandwidth. When some of the OG Droid releases came out I was pumping over 11GB a week in downloads with no issues. It's the least I can do to help the community.
I got to be honest I don't know what the hell i should do to get the update and what will cause me to either have a clean install or lose root
All reports so far indicate it will not break root and rooted users have been getting the notification. They are also probably doing a controlled rollout if you have not yet gotten the notification. My XOOM is at home right now which sucks I won't be able to get my hands on it for about 6 hours and see what I can all do.
This is the boot.img and system.img from a stock Wifi xoom!
DO NOT USE TO RE-LOCK YOUR ZOOM
How did I get it? I flashed the tiamat boot to my recovery partition, and booted to it. Then I pulled the pristine boot and system partitions.
The system.img is here: http://www.mediafire.com/file/2fknnmy6nw6i19n/StockWiFiSystem.zip
IMPORTANT: These are unmodified images from my stock xoom. You can't re-oem-lock with them (probably due to the lack of userdata.img). If you do, you run the chance of a brick. (After seeing a complaint of this, I verified it with my own xoom.)
-Jim
Have you verified that once you are rooted, you can flash back this stock image and relock the wifi xoom?
Is this all we need to flash it back to stock? I looked at the official Stock images from Motodev for the 3g version and their zip file contained 4 files: boot.img, recovery.img, system.img, userdata.img. It looks like you extracted boot.img and system.img. Are the other 2 files (recovery.img and userdata.img) needed?
ericdabbs said:
Have you verified that once you are rooted, you can flash back this stock image and relock the wifi xoom?
Is this all we need to flash it back to stock? I looked at the official Stock images from Motodev for the 3g version and their zip file contained 4 files: boot.img, recovery.img, system.img, userdata.img. It looks like you extracted boot.img and system.img. Are the other 2 files (recovery.img and userdata.img) needed?
Click to expand...
Click to collapse
Recovery shouldn't be change, as there is no aftermarket recovery yet. Userdata will create itself on boot with the new system.
Sent From My Evo
If you should need it for some reason, you can get the recovery image from this thread.
ok guys, i tried this this morning.
pushed the stock images and relocked.
now i'm stuck at FAILED TO BOOT LNX 0X0004.
can't get adb OR the computer to recognize the xoom now.
any ideas??
Chris
Has anyone else tried the stock images posted in this thread?
I've reflashed, and booted with them multiple times with no problem. BUT, they don't appear to be enough to do an oem-lock. If you do, you get the "FAILED TO BOOT" error.
-Jim
Since I was the guinea pig and tried this how do i get it running again?
Windows won't recognize that the xoom is pugged in. ADB just says device not found.
Chris
ke5hde said:
Since I was the guinea pig and tried this how do i get it running again?
Windows won't recognize that the xoom is pugged in. ADB just says device not found.
Chris
Click to expand...
Click to collapse
Chris. Hopefully an expert with this stuff can answer your question soon. If not, do you have the receipt so you can exchange it at the store? I am sure they will take it.
Sure I have the receipt but REALLY don't want to have to return it if I don't have to.
Hoping this can be fixed. I'll just have to wait it out for a while.
You are braver than I, your problem ids one that CAN be fixed..... but not at the moment that I know of.
What happened is, your device tried to OEM Lock but did not have all of the files. So it did in fact flash you back but is missing 2 other core files that were not pulled.
The only way that I know there is to fix this is to actually flash the SBF file through RSD Lite....... there is one problem though. Motorola has not released this yet.
Honestly, your best bet is to take it back and get a new one because who knows when Moto will get off their thumbs and push some simple files online for everyone to use. :-/
Good luck
RSD would be nice but the xoom doesn't even show up there, not really sure if I CAN sbf back since the computer doesn't even know the xoom is connected.
Sent from my liberated Droid X
Well I ran into the same problem with the 3G version and SBF recognized it but nothing else would. Like I said, best bet would be to just take it back and say it is defective and hope they trade it out.... or wait for the complete dump to come out.
stevenege said:
Well I ran into the same problem with the 3G version and SBF recognized it but nothing else would. Like I said, best bet would be to just take it back and say it is defective and hope they trade it out.... or wait for the complete dump to come out.
Click to expand...
Click to collapse
Someone did provide the system dump for the wifi version. Not sure if this will help though.
http://forum.xda-developers.com/showthread.php?t=1011484
No, sorry I meant something else.
I meant Moto needs to release the SBF and the Stock everything so developement can actually get kind of started. The ability to root and un-root is great..... when we can un-root.
The system.img supplied by OP corrected my wifi xoom that I'd bjorked by installing the 3G unlock/root on.
In the interim I'd installed the wifi modules. It ran fine but because it considered itself a 3G it wanted to download and install HR166 update which was getting annoying.
I don't think that these imgs will get you back to OEM/locked but that should be available soon enough from MOTO.
Exchanged....I will no longer be a guinea pig. Lol
Sent from my liberated Droid X
ke5hde said:
Exchanged....I will no longer be a guinea pig. Lol
Sent from my liberated Droid X
Click to expand...
Click to collapse
Thats good
This is the problem with being home with a broken femur and hip for the past 3 months. I do nothing but get in trouble. ;-)
same happened to me quick questions
would you be able to flash 3g abf to xoom and then just reflash everything back to stock once you get it out of the "lock"?
So it has been reported that GE HTC One's are shipping. We would like to get all the paritions dumped so that we can use the images to fully convert our normal Ones into full fledged Google Edition Ones.
Before you do ANYTHING with it (before you root, before you flash a recovery etc...) Follow these directions courtesy of cschmitt Found Here This will ensure we get all the partitions
I have pasted the steps below. This will help the community out greatly!
cschmitt said:
I have a windows command script that uses adb to dump and pull every partition from a One, excluding cache (meaningless) and userdata (to large).
He would need adb and fastboot on his computer, no need for S-off, since we are only reading partitions.
Generally the process would be:
Enable USB Developer options and USB debugging on phone.
Connect phone to usb, install drivers from zip folder if prompted.
Copy SuperSU-v1.41.zip to sd card.
Reboot into bootloader. (Power off, hold power on an vol-down.)
Open command prompt into \htconedump folder.
Unlock bootloader, fastboot oem unlock should do it.
Reboot back into bootloader (via hboot menu.)
From command prompt:
fastboot erase cache
fastboot boot openrecovery-twrp-2.5.0.0-m7.img (Take note we are not flashing recovery, just booting into it so we can root. If you flash the recovery we will not be able to get the stock GE recovery pulled)
Once TWRP boots, flash SuperSU-v1.41.zip via TWRP to root device.
Reboot back into system.
Run pullmmc01-37.cmd command script from a windows command prompt.
Zip up the dump directory containing all of the mmcblk0p??.bin files.
I've packaged everything up into a zip file containing ADB, fastboot, HTC drivers, superuser.zip, TWRP image, and the pullmmc01-37.cmd command script.
htconedump.zip"
Click to expand...
Click to collapse
Also make sure to take note of your CID in the bootloader and also report that in this thread. You can get this by running fastboot getvar all while in the bootloader. The MID and the CID will be listed. Please make note of both.
I would advise anyone doing it that they do it without fully setting up the phone because once you unlock the bootloader it will wipe your data. So boot into android and just skip through the whole set up process because you'll just have to do it again after you unlock the bootloader
EDIT: Got this info from the Dump thread on Android Central. Just need to confirm it's correct with someone who has the device
ro.product.name=m7_google
cid=GOOGL001
mid=PN0712000
cidlist=GOOGL001
Reserving this space for conversion instructions.
http://forum.xda-developers.com/showthread.php?t=2356654 Using dump of released device??
bobsie41 said:
http://forum.xda-developers.com/showthread.php?t=2356654 Using dump of released device??
Click to expand...
Click to collapse
We have the system and the boot.img but for us to do a full conversation we need the bootloader, the recovery etc.. Sure, we can all run the rom now but if we get ALL the partitions dumped we can essentially convert our normal ones into full fledged google editions (I think if we had just the bootloader and the recovery we would be ok)
Have you asked Mike?
we would need the 4.3 system dump
bobsie41 said:
Have you asked Mike?
Click to expand...
Click to collapse
Mike used the same dump everyone has been using. It was only system and boot not the bootloader or recovery. The guy who did the dump flashed a custom recovery before he did the dump so we did not get the stock GE recovery which is needed if we want a full conversion and be able to get OTA's just like the GE One would get.
hello00 said:
we would need the 4.3 system dump
Click to expand...
Click to collapse
Yeah here is to wishing they ship with 4.3 lol
The idea here is not for us to be able to run the rom but to fully do a conversion. As of now we have the 4.2.2 rom and boot image. I have two ones and I want to fully convert one to a GE. I know others are interested in performing a full conversion as well. And if we do the full conversion when the 4.3 OTA drops we would get it as an OTA and not have to wait for other devs to package it all up for everyone
graffixnyc said:
Mike used the same dump everyone has been using. It was only system and boot not the bootloader or recovery. The guy who did the dump flashed a custom recovery before he did the dump so we did not get the stock GE recovery which is needed if we want a full conversion and be able to get OTA's just like the GE One would get.
Click to expand...
Click to collapse
Ok. I assumed that, due to the delay in Mike releasing his GE rom, that he had perhaps acquired his own information.
If anybody lives in the viscinity of Old York City, struggling to dump the required information, I could offer the same service as you have for those near New York City........Highly unlikely I guess.
I am very interested in trying this out.
RaptorMD said:
I am very interested in trying this out.
Click to expand...
Click to collapse
Hey! I remember you! Didn't you use one of my roms at one time(Either on the HTC View or GS3)? If I remember correctly you're also from NY?
This is a great idea. If not for the missing T-Mobile LTE band I would have bought the GE. I hope you get what you need. Would probably cure my Flashaholics disease too, if you're always up to date with the latest and greatest.
Sent from my One using Tapatalk 2
Yea i cant wait for the dump. I bought this phone specifically to make it a GE. Im on AT&T, running an unlocked Tmobile HTC One. The best of both worlds
graffixnyc said:
Hey! I remember you! Didn't you use one of my roms at one time(Either on the HTC View or GS3)? If I remember correctly you're also from NY?
Click to expand...
Click to collapse
I did on the HTC View and very likely the GS3 as well and I am from NY Its nice to run into you again. The HTC One is finally a phone worth KEEPING, finally. Now that I am off VZW and enjoying GSM and a Developer Edition H1 life is far more interesting.
---------- Post added at 06:41 PM ---------- Previous post was at 06:40 PM ----------
serialtoon said:
Yea i cant wait for the dump. I bought this phone specifically to make it a GE. Im on AT&T, running an unlocked Tmobile HTC One. The best of both worlds
Click to expand...
Click to collapse
I look forward to what the devs cook up in the ROM kitchen. I am very keen to try out the GE ROM's but I would also like HTC to just offer up the option for DE to get it now and to allow anyone to flash it if they want.
I am also interested in converting my s4 gt-9505 into a full google edition s4 with OTA.
slikr said:
I am also interested in converting my s4 gt-9505 into a full google edition s4 with OTA.
Click to expand...
Click to collapse
Wrong forum?
surely will try this out
Any news I'm anticipating fully converting to GE!!
Hopefully in the next few hours it will arrive! Cant wait to receive it
Aerys said:
Hopefully in the next few hours it will arrive! Cant wait to receive it
Click to expand...
Click to collapse
Are you going to try to dump the partitions? If so, I would advise anyone doing it that they do it without fully setting up the phone because once you unlock the bootloader it will wipe your data. So boot into android and just skip through the whole set up process because you'll just have to do it again after you unlock the bootloader
For anyone interested here is the firmware image for Verizon Nexus 6 [5.1] [ LMY47E].
VRZ_XT1103_5.1_SHAMU_LMY47E_release-keys_subsidy-default_CFC.xml.zip
http://www.filefactory.com/file/12c...Y47E_release-keys_subsidy-default_CFC.xml.zip
Nexus 6 Firmware Folder
http://www.filefactory.com/folder/74e3c3d68254b075
This where I upload my stuff so sorry if I offend anyone for doing so.
So the difference in between whats out there and this is? I'm curious as the build is different.
coldconfession13 said:
So the difference in between whats out there and this is? I'm curious as the build is different.
Click to expand...
Click to collapse
Not sure what's actually different but the build number is different, LMY47D vs LMY47E.
Could this be flashed with twrp without losing custom recovery?
Sent from my Nexus 6 using XDA Free mobile app
Hopefully we will find out if there are any significant changes or additions. I really hope that I do not need to follow a Verizon firmware through the life of this phone. I hope that there is nothing meaningful in the E version.
Not positive as I am just downloading it, but pretty sure it is the factory image for the Nexus 6 for VZW so I imagine it will remove root and probably custom recovery.
But the nice thing about the Nexus 6 is that you are NOT tied to your carrier's firmware/ROM's for it. Unlike previous phones, there are only two versions, US and International. So we don't have to worry if 'x ROM' is for the T-Mobile version, the Sprint version, etc., etc.
Well no worries this all but confirms vzw is rootable and unlockable
Anyone Flash this yet?
Has anyone flashed this yet...very interested how you went about it and what the results are.....thx
Is there a rooted version??
Parsing the image filename
coldconfession13 said:
So the difference in between whats out there and this is? I'm curious as the build is different.
Click to expand...
Click to collapse
Also waiting another few hours for download to complete. In the mean time, just parsing all the attributes of the file name:
LMY47E: Newer than LMY47D, which is explicitly called 5.1.0 on the Nexus Factory Image page (not the usual numbering convention, which would be 5.1; possibly foreshadowing that they know 5.1.1 is hot on its heels)
release-keys: signed by Google
subsidy-default: Includes parameters that resets the SIM Lock on the radio to "default" status, which we assume is factory-unlocked.
CFC: any idea what means?
I would assume this also gives us an image for the /oem partition
Judging by the name this was made on the same day as the image on Google's website, so it is very unlikely that there are major changes.
Nexus 6 subsidy lock config
@autoprime:
1. Does the contents of the included slcf_rev_b_default_v1.0.nvm look like plain QMI commands to you?
2. Do you still have a user-friendly one-click tool that can send DFS commands to a device in diag mode?
How to Flash
Maybe a dumb question... but can this be TWRP flashed (I thinking no) or is there some other method? I was thinking this was a standard recovery image that could be flashed in stock recovery?? Other than that, I am not sure... if anyone has success flashing let me know!
edit...
duh.... ok sorry... my bad for not looking into the zip.... I see the flash all .bat
mahst68 said:
Maybe a dumb question... but can this be TWRP flashed (I thinking no) or is there some other method? I was thinking this was a standard recovery image that could be flashed in stock recovery?? Other than that, I am not sure... if anyone has success flashing let me know!
Click to expand...
Click to collapse
I believe you will need the Motorola Fastboot tool (mfastboot) to flash this in the motoboot mode. You can get it from the MotoDev site, or search on the forums. Note that this is NOT the same as the standard fastboot that ships with the Android SDK (which will also work with the Nexus 6, but not with this particular zip file).
Did It!!!
DA6030 said:
I believe you will need the Motorola Fastboot tool (mfastboot) to flash this in the motoboot mode. You can get it from the MotoDev site, or search on the forums. Note that this is NOT the same as the standard fastboot that ships with the Android SDK (which will also work with the Nexus 6, but not with this particular zip file).
Click to expand...
Click to collapse
As described, used mfastboot... flashed each individual image file based on the steps in the flashfile.xml!!! Booted up everything real nice.... download myverizon and voicemail as soon as I went through initial setup.... rooting now!!! :good:
bootloader remained unlocked the whole time!!!!
mahst68 said:
As described, used mfastboot... flashed each individual image file based on the steps in the flashfile.xml!!! Booted up everything real nice.... download myverizon and voicemail as soon as I went through initial setup.... rooting now!!! :good:
bootloader remained unlocked the whole time!!!!
Click to expand...
Click to collapse
Does the firmware seem configured for VZW? VZW ringtones and boot animation and the like? Or does it appear like something that Google will drop on us in the near future? I wonder if it will ever hit the factory images page?
elreydenj said:
Does the firmware seem configured for VZW? VZW ringtones and boot animation and the like? Or does it appear like something that Google will drop on us in the near future? I wonder if it will ever hit the factory images page?
Click to expand...
Click to collapse
only thing Verizon really are the 2 app downloads.... everything else is the same... not boot animations nothing. Root and TWRP setup worked fine as well.... Not going to relock bootloader though... I know the horror stories of Hard Bricks.... Not going to take off force encrypt either.... was having trouble with the phone wanting to go bootloopy with the regular image from google when I made it force before... I will let everyone know bugs and post some pictures as well once I set it up fully!! :highfive:
mahst68 said:
only thing Verizon really are the 2 app downloads.... everything else is the same... not boot animations nothing. Root and TWRP setup worked fine as well.... Not going to relock bootloader though... I know the horror stories of Hard Bricks.... Not going to take off force encrypt either.... was having trouble with the phone wanting to go bootloopy with the regular image from google when I made it force before... I will let everyone know bugs and post some pictures as well once I set it up fully!! :highfive:
Click to expand...
Click to collapse
Question: I think I may have been under the same circumstances as you. I am rooted, with TWRP, and bootloader unlocked. I am however, running a custom rom (5.0.1 encrypted). I won't be relocking the bootloader. What steps (if you are able to provide them) should I take to achieve 5.1 with bootloader still locked and then root and install TWRP. (Please keep in mind I a have not had a Nexus device since the very first one).
Edit: I am on VZW network but Google Play Store Nexus 6.
TIA
Will do... I am still setting up the phone. Once I complete it and make sure it works fine for a little bit then I'll post. Don't want to cause any issues that might lead to someone bricking their phone
Initial observations
DA6030 said:
LMY47E: Newer than LMY47D, which is explicitly called 5.1.0 on the Nexus Factory Image page (not the usual numbering convention, which would be 5.1; possibly foreshadowing that they know 5.1.1 is hot on its heels)
Click to expand...
Click to collapse
System partition looks complete, but I won't have time to do a diff between the two until next week. But by then, we might have an official changelog.
DA6030 said:
subsidy-default: Implies there's something within this file that sets the SIM Lock parameters on the radio? Extracting that could be very interesting to AT&T and Sprint customers.
Click to expand...
Click to collapse
I don't have an AT&T device to test, but applying this file certainly attempts to set the SIM lock to it's default factory-unlocked state. But it's also possible the radio firmware could reject the unlock commands if it has been previously locked by a carrier. Only way to know is to test.
DA6030 said:
I would assume this also gives us an image for the /oem partition
Click to expand...
Click to collapse
There is an oem partition file within the zip, but it's literally just the string "Hi, Fly Guy". Just open oem.img with a text editor to see it. I cannot imagine that is a valid ext img file, so I'm shocked that it was able to be flashed. If so, that would suggest that the Verizon devices will ship with no unique customizations (e.g., bootanimation, ringtones, that cannot be removed without root), and has a sense of humor.
---------- Post added at 10:39 AM ---------- Previous post was at 10:32 AM ----------
mahst68 said:
As described, used mfastboot... flashed each individual image file based on the steps in the flashfile.xml!!!
Click to expand...
Click to collapse
@mahst68, did you flash only the image files, or also the subsidy_lock_config file (slcf....nvm)? What mfastboot command did you use to send the slcf? What was the response did you get back from that command? And when you flashed the oem.img what response did you get back?
Greetings XDA Members,
I am seeing alot of people repeating this same question again and again like "Hey, I have messed up I flashed this and this and now I want to get all setup to take the official Lollipop OTA of MOTO X, Please help" the same question over and over again in several other threads so I thought it might be a good idea to sum up everything in one thread and make this easier for other members to point any person having issue like these to this thread. Now keep in mind that I am not a professional developer, Im just here to tell the basics of flashing a stock firmware, IF I make any mistake please let me know and also this thread will be a long briefly explained one so please read carefully and consider everything before applying anything.
To start off, the point of this thread is to help our new members of XDA to have an idea of what to do and how to do, Now the main topic of this thread is to point our newbie fellows on how to flash a stock firmware on a messed up MOTO X (Any Model), By messed up I mean: Either the user corrupted or damaged or somehow got stuck between anything like bootloops,not getting signals,phone not working properly and all sorts of basic software problems. If you are having such problems with your phone and want to get back to the newly fresh Moto X like when you bought it, it was shiny and all the software was fresh etc And also you want to get all setup to receive the Lollipop OTA.. you are at the right place mate. Keep reading.
Have a look at this thread also for more useful information about getting ready to take the OTA its for the kitkat ota but still its all the same so this could be very useful! by @KidJoe http://forum.xda-developers.com/moto-x/general/faq-kit-kat-how-to-prepare-carriers-t2536735
or If you have an unlocked bootloader and are rooted, and the only change you did to your phone was replacing recovery to root.. Here is another option to flash Stock Recovery back on your phone to get ready to install the latest OTA -> http://forum.xda-developers.com/moto...ooted-t3027079 credits goes to @KidJoe .
PRECAUTIONS (A MUST READ BEFORE PROCEEDING ANY FURTHER)
I am not responsible if anything happens to your device during this process because I am just explaining here what to do I wont be the one who is applying the instructions on any phone so in no matter or aspect I am the responsible for damage caused to your device. So again do this on your own risk. I wont be responsible for any damage to your phone.
1: NEVER DOWNGRAED FIRMWARE/BOOTLOADER VERSION!
Okay so you want to downgrade to get the advantages of the previous android version of your phone. THE ANSWER IS A BIG NO! if you try to downgrade your phone and mess up with motoboot.img or gpt.bin you will get a hard brick! Never try to downgrade! Refer to this thread http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202 by @KidJoe to know all the facts about downgrading.
2: Downlaod the exact and correct firmrware, before flashing
Flashing another carriers rom on your phone would be a stupidity. MAKE yourself 100% sure that you have downloaded the correct/exact firmware of your phone, never flash some random firmware on your particular moto x. Flashing another carriers rom would give you a hard brick probably.. Never play with different firmwares. (I will be mentioning further in the thread, how to make sure to download the correct firmware.)
3:You must consider of having an Unlocked Bootloader before proceeding any further, Or if you have a locked bootloader this method might work on the locked bootloaders also but, again flashing different carriers firmware on a locked bootloader device will get you more screwed up
This method should also work for the locked bootloaders but be 100% sure that you are flashing the correct signed firmware of your specific carrier. As for the Bootloader Unlock, There are not much of options for now, You can unlock your bootloader either from the motorola official site or use sunshine unlocker to unlock your bootloader. Refer to this thread : http://forum.xda-developers.com/moto-x/general/request-help-exploit-moto-x-bl-t2828471 by @samwathegreat to have an idea about the sunshine unlocking method.
Also refer to this also for info about gaining root and unlocking bootloader http://forum.xda-developers.com/moto-x/general/one-stop-shop-how-root-moto-x-confusion-t2826159 by @KidJoe.
4:You messed up your stock rom and freezed some apps
If you have rooted, put xposed etc. Dont plan to revert back by restoring the freezed apps and Instead just flash the stock firmware from RSD. Restoring back freezed apps etc will cause more problems. But make sure you uninstall all of the frameworks of xposed before proceeding to flash stock firmware.
5:This method will wipe your data completely
As the Title says this method will obviously wipe every single piece of your personal data stored on this phone such as pictures,contacts,videos and pretty much everything. So be sure to backup your data on your pc or anywhere.
Grab Your Phones Its time to start the process. Make sure its charged more than 60%.
Okay enough theory, lets get this over with.
Download and install motorola drivers : https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481 and restart you computer and proceed.
STEP 1: Identifying the correct name or model number of your Moto X
1: If the original motorola back cover is on the phone, there is some very fine/small print at the bottom of the back. It will have the FCC ID, Model number, etc. It could be hard to see, So you might have to tilt/twist the phone so the light shines off it just right and the model no appears. The Model No of your MOTO X should start with XT. Make a note of that. (credits goes to @KidJoe for explaining this in detail.)
2:Another way to find the model is by checking the Settings>About Phone of your X.
3:More ways to find out your model no, Connect the phone with the pc and see what does it shows on the pc when connected on USB MASS STORAGE. It should mention the XT10xx (Model name) of your phone on pc
NOTE:BEFORE you flash away from Stock, on the phone you first go App Drawer -> Settings -> About Phone... Make note of what is listed under System Version, Android Version, and build number. Then visit one (or all) of the sites until that host the leaked SBF files until you find the SBF that matches and down load the file to your PC for use later.. The file name will usually contain parts or all of that info listed under settings, and possibly the carrier name, or acronym for the carrier name (Verizon might be VZW, Rogers Canada might be RCI, etc).
So for example: If your phone model is XT1058 and under about phone it reports...
android version is 4.4.4
system version is 212.44.26. ghost_row.RCI.en.ca
build nunber is KXA21.12-L1.26
That tells me you have a Rogers Canada (RCI) XT1058 with 4.4.4 ROM on it. When you look at the file factory site for your SBF, you want to look for a file that contains some/all of that info, like... XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip
(notice the parts of the "about phone" info and file name which are highlighted in Bold to help illustrate the example)
IF you are already running a CUSTOM or 3Rd party rom, like CM, system version and build number will not match STOCK Moto SBF files. credits goes to @KidJoe for adding this additional info about figuring out what ROM is on your phone.
STEP 2: Identifying and downloading the correct firmware for your model of X
1:So now that you have identified, your Moto X is XT10xx, Now you will be downloading the correct firmware of your phone which should match the System/Build Version of your phone.
For Example: If your phone is from Rogers,ATT,Sprint,T-Mobile,US-CELLULAR,Europe etc. IT should be mentioned in the Settings>About Phone section below build version. Make a note of the whole build version/system version on a piece of paper or anything you like. Because the system/build version is the main key to have the proper knowledge about your phone before flashing any firmware.
Additional Info about bootloaders according to android version(This will give an idea about bootloaders, read it carefully and match the version of you bootloader in order with this dont downgrade):
(Android Version: Bootloader)
4.2.2: 30.70
4.2.2/camera patch OTA: 30.71
4.4: 30.B2
4.4.2: 30.B4
4.4.4: 30.B7
2:Now this part must get hard for the newbie guys but I will try my best to keep everything clear and easy. All The firmwares you need for your X is available at this site: http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=100&page=1
Now start by searching the model no and system version of your moto x. For example: if your phone is from Rogers Canada it must have "XT1058 RCI_CA " in it.. XT1058:Model Name Rci: Rogers CA: Canada. You get this right? on the firmware there should be mentioned a little bit hint or info you need to identify your firmware. Go ahead and download it. Again for the newbie guys I cant explain much easier than i've explained above, Still if you cannot find the correct firmware let me know I will try to find it out. But please first try your best from your own side first, I cant spoonfeed you [emoji14] . ATTENTION: Please download the 4.4.4 Version of your carrier because it will be easy to receive the 5.1 OTA on a 4.4.4 rom.
STEP 3: Getting ready to flash through RSD LITENote: I wont be explaining a method to flash through fastboot as from my opinion I dont like fastboot it can cause you a serious problem if you type anything wrong. If you want to try the fastboot method there is also another similar guide on how to flash through fastboot refer to this thread http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515 by @TechSavvy2
1: Download RSD LITE 6.1.5 (RSD LITE SETUP IS ATTACHED download from there) and install it in your PC Windows. (I dont have a mac dont know anything about mac.)
2:Make a new folder and unzip the firmware zip file in that new folder
3: Open the XML FILE and edit the .XML file and remove any lines with "getvar" written in them, Remove that whole line which has "getvar" in it, and (CTRL+S) save that edited file.
3: RUN RSD LITE IN ADMINISTRATIVE RIGHTS on rsd lite right click and run as administrator, IF you dont run as administrator rsd lite wont flash anything.
4: Now on rsd lite press the three dotted "..." button and select the XML File from the "new folder" you made moments ago.
STEP 4: Getting your phone in fastboot mode
If you are totally fine and running your software normally: Power off your phone, wait for 5 seconds then press and hold the power/lock button and volume down button simultaneously for 5 seconds, then release those buttons after 5 seconds. You will be in the fastboot mode of your phone now plugin your phone on usb cable of your computer make sure the bootloader says "USB CONNECTED." If it doesnt shows usb connected sign, Change the usb cable or try another usb slot.
For the people who have damaged and corrupted the software and having black screens stuck and nothing else or either they did something naive and somehow cant get in the fastboot mode: Hook up your phone to an A/C Charger and wait for about 30mins to atleast recharge it. Then remove your phone from charger and dont press the power button! Do this: Press and hold the power/lock button and volume down button simultaneously for 5 seconds, then release those buttons after 5 seconds,If you are not properly bricked you will be on the fastboot now probably, now plugin your phone on usb cable of your computer make sure the bootloader says "USB CONNECTED." If it doesnt shows usb connected sign, Change the usb cable or try another usb slot.
For the people stuck on bootloop after flashing a 3rd party custom rom or stuck on the motorola logo etc. Do this: Press and hold the Power/lock button, Volume Up Button and Volume Down button, all the three buttons simultaneously for about 15 seconds, when the screen turns off, Quickly press the Power button and volume down button repeatedly (this time dont press and hold! Press both buttons repeatedly!) You will be on the fastboot mode of your phone plugin the phone on usb port and your bootloader should say "USB CONNECTED" AFAIK. If you are not bricked!
STEP 5:Flashing the firmware
On Rsd lite, make sure that your device is showing "Connected" Now, Press the start button on the rsd lite and wait for about maximum 30-40Mins to get your firmware flashed in the phone successfully. ATTENSION: Dont touch or power off your phone or computer during the flashing process untill or unless your device reboots and comes to its homescreen on the factory settings, make sure the usb cable is connected properly not loose. If you mess up anything during flashing process you are risking your whole phone so do this when you are calm enough.
Flashing Process Done Now You Are All Set Up To Receive The Latest OTA OF 5.1!
For the people who have flashed the 5.1 soak test/leak and are stuck at some certain point
So you couldn't wait and flashed the LEAKED test/soak versions of 5.02 and 5.1 and your bootloader is upgraded to 30.BC or 30.BD you are stuck on a bootloop and cant get your phone to work ----> There is nothing you could really do to save your self till now only one thing you can do is wait! DO NOT DOWNGRADE YOUR BOOTLOADER/FIRMWARE as that will risk bricking, but rather WAIT and hope a 5.1 SBF for their model/carrier leaks in the coming weeks/months, then fully flash it to return to stock. credits goes to @KidJoe for adding this info.
Good luck mates!
Thats all I can sum up in one thread, I hope this helps the new people. Peace Out.
whizinc said:
Greetings XDA Members,
I am seeing alot of people repeating this same question again and again like "Hey, I have messed up I flashed this and this and now I want to get all setup to take the official Lollipop OTA of MOTO X, Please help" the same question over and over again in several other threads so I though it might be a good idea to sum up everything in one thread and make this easier for other members to point any person having issue like these to this thread. Now keep in mind that I am not a professional developer, Im just here to tell the basics of flashing a stock firmware, IF I make any mistake please let me know and also this thread will be a long briefly explained one so please read carefully and consider everything before applying anything.
To start off, the point of this thread is to help our new members of XDA to have an idea of what to do and how to do, Now the main topic of this thread is to point our newbie fellows on how to flash a stock firmware on a messed up MOTO X (Any Model), By messed up I mean: Either the user corrupted or damaged or somehow got stuck between anything like bootloops,not getting signals,phone not working properly and all sorts of basic software problems. If you are having such problems with your phone and want to get back to the newly fresh Moto X like when you bought it, it was shiny and all the software was fresh etc And also you want to get all setup to receive the Lollipop OTA.. you are at the right place mate. Keep reading.
Have a look at this thread also for more useful information about getting ready to take the OTA its for the kitkat ota but still its all the same so this could be very useful! by @KidJoe http://forum.xda-developers.com/moto-x/general/faq-kit-kat-how-to-prepare-carriers-t2536735
PRECAUTIONS (A MUST READ BEFORE PROCEEDING ANY FURTHER)
I am not responsible if anything happens to your device during this process because I am just explaining here what to do I wont be the one who is applying the instructions on any phone so in no matter or aspect I am the responsible for damage caused to your device. So again do this on your own risk. I wont be responsible for any damage to your phone.
1: NEVER DOWNGRAED FIRMWARE/BOOTLOADER VERSION!
Okay so you want to downgrade to get the advantages of the previous android version of your phone. THE ANSWER IS A BIG NO! if you try to downgrade your phone and mess up with motoboot.img or gpt.bin you will get a hard brick! Never try to downgrade! Refer to this thread http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202 by @KidJoe to know all the facts about downgrading.
2: Downlaod the exact and correct firmrware, before flashing
Flashing another carriers rom on your phone would be a stupidity. MAKE yourself 100% sure that you have downloaded the correct/exact firmware of your phone, never flash some random firmware on your particular moto x. Flashing another carriers rom would give you a hard brick probably.. Never play with different firmwares. (I will be mentioning further in the thread, how to make sure to download the correct firmware.)
3:You must consider of having an Unlocked Bootloader before proceeding any further
There are not much of options for now, You can unlock your bootloader either from the motorola official site or use sunshine unlocker to unlock your bootloader. Refer to this thread : http://forum.xda-developers.com/moto-x/general/request-help-exploit-moto-x-bl-t2828471 by @samwathegreat to have an idea about the sunshine unlocking method.
Also refer to this also for info about gaining root and unlocking bootloader http://forum.xda-developers.com/moto-x/general/one-stop-shop-how-root-moto-x-confusion-t2826159 by @KidJoe.
3:You messed up your stock rom and freezed some apps
If you have rooted, put xposed etc. Dont plan to revert back by restoring the freezed apps and Instead just flash the stock firmware from RSD. Restoring back apps freezed etc will cause more problems. But make sure you uninstall all of the frameworks of xposed before proceeding to flash stock firmware.
Grab Your Phones Its time to start the process. Make sure its charged more than 60%.
Okay enough theory, lets get this over with.
Download and install motorola drivers : https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481 and restart you computer and proceed.
STEP 1: Identifying the correct name or model number of your Moto X
1: If the original motorola back cover is on the phone, there is some very fine/small print at the bottom of the back. It will have the FCC ID, Model number, etc. It could be hard to see, So you might have to tilt/twist the phone so the light shines off it just right and the model no appears. The Model No of your MOTO X should start with XT. Make a note of that. (credits goes to @KidJoe for explaining this in detail.)
2:Another way to find the model is by checking the Settings>About Phone of your X.
3:More ways to find out your model no, Connect the phone with the pc and see what does it shows on the pc when connected on USB MASS STORAGE. It should mention the XT10xx (Model name) of your phone on pc
STEP 2: Identifying and downloading the correct firmware for your model of X
1:So now that you have identified, your Moto X is XT10xx, Now you will be downloading the correct firmware of your phone which should match the System/Build Version of your phone.
For Example: If your phone is from Rogers,ATT,Sprint,T-Mobile,US-CELLULAR,Europe etc. IT should be mentioned in the Settings>About Phone section below build version. Make a note of the whole build version/system version on a piece of paper or anything you like. Because the system/build version is the main key to have the proper knowledge about your phone before flashing any firmware.
Additional Info about bootloaders according to android version(This will give an idea about bootloaders, read it carefully and match the version of you bootloader in order with this dont downgrade):
(Android Version: Bootloader)
4.2.2: 30.70
4.2.2/camera patch OTA: 30.71
4.4: 30.B2
4.4.2: 30.B4
4.4.4: 30.B7
2:Now this part must get hard for the newbie guys but I will try my best to keep everything clear and easy. All The firmwares you need for your X is available at this site: http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=100&page=1
Now start by searching the model no and system version of your moto x. For example: if your phone is from Rogers Canada it must have "XT1058 RCI_CA " in it.. XT1058:Model Name Rci: Rogers CA: Canada. You get this right? on the firmware there should be mentioned a little bit hint or info you need to identify your firmware. Go ahead and download it. Again for the newbie guys I cant explain much easier than i've explained above, Still if you cannot find the correct firmware let me know I will try to find it out. But please first try your best from your own side first, I cant spoonfeed you [emoji14] . ATTENTION: Please download the 4.4.4 Version of your carrier because it will be easy to receive the 5.1 OTA on a 4.4.4 rom.
STEP 3: Getting ready to flash through RSD LITENote: I wont be explaining a method to flash through fastboot as from my opinion I dont like fastboot it can cause you a serious problem if you type anything wrong. If you want to try the fastboot method there is also another similar guide on how to flash through fastboot refer to this thread http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515 by @TechSavvy2
1: Download RSD LITE 6.1.5 (RSD LITE SETUP IS ATTACHED download from there) and install it in your PC Windows. (I dont have a mac dont know anything about mac.)
2:Make a new folder and unzip the firmware zip file in that new folder
3: Open the XML FILE and edit the .XML file and remove any lines with "getvar" written in them, Remove that whole line which has "getvar" in it, and (CTRL+S) save that edited file.
3: RUN RSD LITE IN ADMINISTRATIVE RIGHTS on rsd lite right click and run as administrator, IF you dont run as administrator rsd lite wont flash anything.
4: Now on rsd lite press the three dotted "..." button and select the XML File from the "new folder" you made moments ago.
STEP 4: Getting your phone in fastboot mode
If you are totally fine and running your software normally: Power off your phone, wait for 5 seconds then press and hold the power/lock button and volume down button simultaneously for 5 seconds, then release those buttons after 5 seconds. You will be in the fastboot mode of your phone now plugin your phone on usb cable of your computer make sure the bootloader says "USB CONNECTED." If it doesnt shows usb connected sign, Change the usb cable or try another usb slot.
For the people who have damaged and corrupted the software and having black screens stuck and nothing else or either they did something naive and somehow cant get in the fastboot mode: Hook up your phone to an A/C Charger and wait for about 30mins to atleast recharge it. Then remove your phone from charger and dont press the power button! Do this: Press and hold the power/lock button and volume down button simultaneously for 5 seconds, then release those buttons after 5 seconds,If you are not properly bricked you will be on the fastboot now probably, now plugin your phone on usb cable of your computer make sure the bootloader says "USB CONNECTED." If it doesnt shows usb connected sign, Change the usb cable or try another usb slot.
For the people stuck on bootloop after flashing a 3rd party custom rom or stuck on the motorola logo etc. Do this: Press and hold the Power/lock button, Volume Up Button and Volume Down button, all the three buttons simultaneously for about 15 seconds, when the screen turns off, Quickly press the Power button and volume down button repeatedly (this time dont press and hold! Press both buttons repeatedly!) You will be on the fastboot mode of your phone plugin the phone on usb port and your bootloader should say "USB CONNECTED" AFAIK. If you are not bricked!
STEP 5:Flashing the firmware
On Rsd lite, make sure that your device is showing "Connected" Now, Press the start button on the rsd lite and wait for about maximum 30-40Mins to get your firmware flashed in the phone successfully. ATTENSION: Dont touch or power off your phone or computer during the flashing process untill or unless your device reboots and comes to its homescreen on the factory settings, make sure the usb cable is connected properly not loose. If you mess up anything during flashing process you are risking your whole phone so do this when you are calm enough.
Flashing Process Done Now You Are All Set Up To Receive The Latest OTA OF 5.1!
Note: Currently please dont and I repeat DONT flash any soak test or any 5.1 leaked release of stock rom. All you will be getting by doing this would be A messed up bootloader,motoboot,gpt etc. Dont be so impatient just wait for the ota to show up on your phone!
Good luck mates!
Thats all I can sum up in one thread, I hope this helps the new people. Peace Out.
Click to expand...
Click to collapse
That's exactly what I did last night to make sure that I can get the OTA of Lollipop 5.1 when it finally comes out. I have a feeling that it will be rolling out here pretty soon.
Mod Edit : HIDE tags added by @Darth ... No need to quote long Opening posts, or use hide tags if you must. Thanks!
cindylike24 said:
That's exactly what I did last night to make sure that I can get the OTA of Lollipop 5.1 when it finally comes out. I have a feeling that it will be rolling out here pretty soon.
Click to expand...
Click to collapse
Yeah its already rolling out in some areas of US.. Good luck
Sent from my ghost using Tapatalk
whizinc said:
Yeah its already rolling out in some areas of US.. Good luck
Sent from my ghost using Tapatalk
Click to expand...
Click to collapse
Not in my area yet.
Cindy
cindylike24 said:
Not in my area yet.
Cindy
Click to expand...
Click to collapse
Not across the river, either! *Waves from Illinois*
hbar98 said:
Not across the river, either! *Waves from Illinois*
Click to expand...
Click to collapse
Where are you from? I'm from Vincennes, Indiana.
Sent from my Samsung Galaxy Tab 4 8" model using Tapatalk
cindylike24 said:
Where are you from? I'm from Vincennes, Indiana.
Sent from my Samsung Galaxy Tab 4 8" model using Tapatalk
Click to expand...
Click to collapse
Now I live around Fairfiled, IL, but I grew up in Keensburg and Mt. Carmel.
hbar98 said:
Now I live around Fairfiled, IL, but I grew up in Keensburg and Mt. Carmel.
Click to expand...
Click to collapse
Cool! Small world, isn't it?!
Sent from my Samsung Galaxy Tab 4 8" model using Tapatalk
cindylike24 said:
Cool! Small world, isn't it?!
Sent from my Samsung Galaxy Tab 4 8" model using Tapatalk
Click to expand...
Click to collapse
Yep! I don't think that 5.1 is rolling out in the states yet... you'd think that whichever carrier rolled it out first would make some noise about it. I'll be ready, though! I really like 5.1.1 on my 2013 Nexus 7.
If you have an unlocked bootloader and are rooted, and the only change you did to your phone was replacing recovery to root.. Here is another option to flash Stock Recovery back on your phone -> http://forum.xda-developers.com/moto-x/general/ref-return-to-stock-recovery-rooted-t3027079
----
@whizinc , Something else to add to the OP on figuring out what ROM is on your phone...
Normally I would suggest BEFORE you flash away from Stock, on the phone you first go App Drawer -> Settings -> About Phone... Make note of what is listed under System Version, Android Version, and build number. Then visit one (or all) of the sites until that host the leaked SBF files until you find the SBF that matches and down load the file to your PC for use later.. The file name will usually contain parts or all of that info listed under settings, and possibly the carrier name, or acronym for the carrier name (Verizon might be VZW, Rogers Canada might be RCI, etc).
So for example: If your phone model is XT1058 and under about phone it reports...
android version is 4.4.4
system version is 212.44.26. ghost_row.RCI.en.ca
build nunber is KXA21.12-L1.26
That tells me you have a Rogers Canada (RCI) XT1058 with 4.4.4 ROM on it. When you look at the file factory site for your SBF, you want to look for a file that contains some/all of that info, like... XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip
(notice the parts of the "about phone" info and file name which are highlighted in Bold to help illustrate the example)
IF you are already running a CUSTOM or 3Rd party rom, like CM, system version and build number will not match STOCK Moto SBF files.
-------
You also might want to add info for those who couldn't wait, and flashed the LEAKED test/soak versions of 5.02 and 5.1 that now have bootloader 30.BC or 30.BD... as they will NOT want to downgrade to 4.4.4 as that will risk bricking, but rather WAIT and hope a 5.1 SBF for their model/carrier leaks in the coming weeks/months, then fully flash it to return to stock.
KidJoe said:
If you have an unlocked bootloader and are rooted, and the only change you did to your phone was replacing recovery to root.. Here is another option to flash Stock Recovery back on your phone -> http://forum.xda-developers.com/moto-x/general/ref-return-to-stock-recovery-rooted-t3027079
----
@whizinc , Something else to add to the OP on figuring out what ROM is on your phone...
Normally I would suggest BEFORE you flash away from Stock, on the phone you first go App Drawer -> Settings -> About Phone... Make note of what is listed under System Version, Android Version, and build number. Then visit one (or all) of the sites until that host the leaked SBF files until you find the SBF that matches and down load the file to your PC for use later.. The file name will usually contain parts or all of that info listed under settings, and possibly the carrier name, or acronym for the carrier name (Verizon might be VZW, Rogers Canada might be RCI, etc).
So for example: If your phone model is XT1058 and under about phone it reports...
android version is 4.4.4
system version is 212.44.26. ghost_row.RCI.en.ca
build nunber is KXA21.12-L1.26
That tells me you have a Rogers Canada (RCI) XT1058 with 4.4.4 ROM on it. When you look at the file factory site for your SBF, you want to look for a file that contains some/all of that info, like... XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip
(notice the parts of the "about phone" info and file name which are highlighted in Bold to help illustrate the example)
IF you are already running a CUSTOM or 3Rd party rom, like CM, system version and build number will not match STOCK Moto SBF files.
-------
You also might want to add info for those who couldn't wait, and flashed the LEAKED test/soak versions of 5.02 and 5.1 that now have bootloader 30.BC or 30.BD... as they will NOT want to downgrade to 4.4.4 as that will risk bricking, but rather WAIT and hope a 5.1 SBF for their model/carrier leaks in the coming weeks/months, then fully flash it to return to stock.
Click to expand...
Click to collapse
All the information that you suggested has been added to the OP. Thank you! :good:
https://docs.google.com/open?id=0B5XNxZ2OcfKtdDROTk5kb21ObU0 for asia retail only XT1052_RETAIL-ASIA_4.4.4_KXA21.12-L1.26_18_cid7_CFC_1FF.xml.zip
miju12 said:
https://docs.google.com/open?id=0B5XNxZ2OcfKtdDROTk5kb21ObU0 for asia retail only XT1052_RETAIL-ASIA_4.4.4_KXA21.12-L1.26_18_cid7_CFC_1FF.xml.zip
Click to expand...
Click to collapse
what do you mean by this?
Sent from my ghost using Tapatalk
whizinc said:
what do you mean by this?
Sent from my ghost using Tapatalk
Click to expand...
Click to collapse
factory image for XT1052. if you download from the file factory site it takes a lot of time.
miju12 said:
factory image for XT1052. if you download from the file factory site it takes a lot of time.
Click to expand...
Click to collapse
file factory is the only site present and online for now which has all the firmwares in it... So that's why i preferred it, ignoring the problem of the download speeds...
Sent from my ghost using Tapatalk
whizinc said:
file factory is the only site present and online for now which has all the firmwares in it... So that's why i preferred it, ignoring the problem of the download speeds...
Sent from my ghost using Tapatalk
Click to expand...
Click to collapse
yeah i know. if someone uploads the file to some other cloud like drive, won't it be easy to others to download? i have posted the link because if someone needs the asia retail factory image, it would be easy and fast to download from this link. and for others the file factory website is there. and the problem from downloading file from file factory is it can't be resume so if there is a network error you have to download the file from begining.
miju12 said:
yeah i know. if someone uploads the file to some other cloud like drive, won't it be easy to others to download? i have posted the link because if someone needs the asia retail factory image, it would be easy and fast to download from this link. and for others the file factory website is there. and the problem from downloading file from file factory is it can't be resume so if there is a network error you have to download the file from begining.
Click to expand...
Click to collapse
I agree with you, But i dont think someone will do that because its not easy to upload such big files on a private drive like clouds etc...
Sent from my ghost using Tapatalk
Do you know the file name for the Verizon Dev Edition?
whizinc said:
I agree with you, But i dont think someone will do that because its not easy to upload such big files on a private drive like clouds etc...
Sent from my ghost using Tapatalk
Click to expand...
Click to collapse
yeah its a pain to upload such big file. but the link i posted someone have uploaded file so its easy for XT1052 asia retail users to download
---------- Post added at 05:24 PM ---------- Previous post was at 05:16 PM ----------
mbush78 said:
Do you know the file name for the Verizon Dev Edition?
Click to expand...
Click to collapse
check this link for the file as it was uploaded in google drive. before flashing confirm it is for your model with the dev http://forum.xda-developers.com/moto-x/development/vzw-4-4-kitkat-fastboot-factory-image-t2537398
check this page of motorola https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
mbush78 said:
Do you know the file name for the Verizon Dev Edition?
Click to expand...
Click to collapse
Follow the link @miju12 suggested that would be the firmware for verizon dev edition... and dont execute the oem lock command... It will relock your bootloader if you have it unlocked.
Sent from my ghost using Tapatalk