Related
[SIZE=+3]FlashBack21 v2 - Return to Factory 2.1 Stock - March 2011 OTA[/SIZE]
Note1: This ROM supersedes the (former) "FlashBack15" ROM as of 2010/10/20. This step was taken because it appears that VZW/Google are no longer providing Cupcake->Eclair OTA downloads for the Eris.
Note2: The V2 FlashBack21 ROM installs the stock HTC software corresponding to the March 2011 OTA version V2.41.605.6. The V1 FlashBack21 ROM installs the stock HTC software corresponding to the July 2010 OTA - version V2.37.605.4
[SIZE=+2]Last Updated: March 06 2011[/SIZE]
This ROM is intended for reverting a rooted Eris with a custom recovery to the HTC stock software: March 2011 2.1 OTA ROM - v 2.41.605.6. There are many other ways to do this; but this way uses Amon_RA for the installation as a convenience for less experienced rooters. (And only Amon_RA v1.6.2 - the installer will refuse to work with any other recovery.)
Two versions are provided: one which flashes the radio firmware version 2.42.01.04.27, and one which does not flash the radio; other than this difference, they are identical. (The same radio firmware - v2.42.01.04.27 - was used in both the July 2010 & March 2011 OTA releases.) Choose the ROM which best fits your needs. If you already have the most recent radio installed (2.42.01.04.27), there is no need to reflash the radio.
File name: "FlashBack21_v2.zip" (download link and md5 sigs below).
File name: "FlashBack21_v2_noRadioFlash.zip" (download link and md5 sigs below).
Derived from the Eris "March 2011 OTA" (2.41.605.6) release, this ROM repackages the last official 2.1 ("Eclair") release for the Eris from HTC/VZW so that it can be installed with Amon_RA recovery - you flash it just like any other dev ROM. There are essentially no customizations, and no built-in root or extra tools; it is 99.99% stock, with the following difference:
- This ROM also performs jcase's "Flash Any RUU" patch to the misc partition during the flashing process.
This step is performed so that the Eris responds well to flashing operations involving the use of any PB00IMG.zip file (via HBOOT), or application of any RUU utility for the Eris. So, even though this is an "unrooting" ROM, pains are taken to make sure that it is easy as possible to re-root or manipulate with existing methods.
This ROM does not touch the bootloader (or "Hboot" or "IPL/SPL"). If you want to install a different bootloader, do it first before applying this ROM.
[SIZE=+1]Please Note: THE RECOVERY BOOT PARTITION IS REPLACED BY THE MATCHING VERSION OF THE STOCK RECOVERY PARTITION (V2: March 2011 OTA; V1: July 2010 OTA) in this ROM. This means that you will need to re-root your phone if you use this ROM, should you later decide that you want to restore a different ROM.[/SIZE]
[SIZE=+1]Please Note 2: ONE OF THESE ROMs FLASHES A RADIO. This is different than nearly 99% of all Eris dev ROMs. You will see some activity at the conclusion of your Amon_RA recovery session as a result of this - if you choose to use the ROM version that flashes the radio firmware.[/SIZE]
[SIZE=+2]Instructions[/SIZE]
- Read this whole post all the way through before you begin
- Charge your phone completely
- Download the .zip file you need to the top-most folder of your SD card
- Verify the length and/or MD5 checksums (of the copy of the ROM file on the SD card)
- Boot into the Amon_RA recovery, Wipe, and then flash the FlashBack21 ROM (of your choosing)
IF YOU ARE FLASHING THE RADIO:
- When flashing is complete, you will see the message at the bottom of the screen:
"Reboot via vol-up+vol-down or menu to complete installation"
- Make sure to exit Amon_RA after the ROM has finished flashing by selecting the "Reboot now" top-level menu item. Don't do something stupid like pulling the battery.
- You will see two successive splash screens that you do not normally see when using Amon_RA - these indicate that the factory recovery boot is performing the radio flashing operation. Do not interrupt - the phone will reboot on it is own when this step completes.
[SIZE=+2]Acknowledgments[/SIZE]
- Amon_RA for his recovery boot
- jcase for his disclosure to the Eris community of the misc partition "main version number" patch
- hundreds of others on XDA and AF too numerous to mention
- doogald for re-hosting the ROMs (2/15/2012)
[SIZE=+2]Downloads - V2 - March 2011 OTA - v 2.41.605.6[/SIZE]
(Thanks to XDA user doogald for hosting these downloads!)
[SIZE=+1]Flashes Radio !!!![/SIZE]
FlashBack21_v2.zip ( 109,245,758 Bytes; MD5: 3c770473e18e539afe5d090b4a5462ca )
[SIZE=+1]Same ROM, but does NOT flash Radio[/SIZE]
FlashBack21_v2_noRadioFlash.zip ( 102,181,672 Bytes; MD5: d0137efb10dd714cf3770e5ff7b842f5 )
[SIZE=+2]Downloads - V1 - July 2010 OTA - v 2.37.605.4[/SIZE]
(Thanks to XDA user doogald for hosting these downloads!)
[SIZE=+1]Flashes Radio !!!![/SIZE]
FlashBack21_v1.zip ( 108,784,952 Bytes; MD5: 416a92afe52d87beccbef29380a2009f )
[SIZE=+1]Same ROM, but does NOT flash Radio[/SIZE]
FlashBack21_v1_noRadioFlash.zip ( 108,784,967 Bytes; MD5: 44bff966290bb02c0b70ae06ef95d719 )
(Note that both V1 ROM files include the radio image, even though the latter does not flash this firmware - that is why the file sizes are nearly identical.)
OBSOLETE & DEPRECATED - Flashback15_v1
Thanks to XDA user doogald for hosting this download!
- This is here for historical purposes only.
- Note this now ONLY provides a Cupcake (Android 1.5) Factory roll-back for the Eris, as VZW/Google are no longer providing OTAs for the Eris.
- Do not use unless you specifically want a stock "Cupcake" (Android 1.5) Eris
- Note this ROM also UNROOTS YOUR PHONE by replacing the custom recovery with the stock recovery
FlashBack15_v1.zip ( 94,011,341 Bytes; MD5: e5e7ab9f3bc3314f28543fd88ae296fd )
bftb0
Thanks, sounds like this could come in handy!
Yep thanks .... will make it easy when I send this phone back for my 5th eris
This should be stickied up to...Good work!
Nice. Agree this should be sticky
Very nice thank you!
Sent from my Eris using XDA App
Awesome work
Awesome. I agree - lets make this a sticky.
Sent from my nonsensikal froyo using XDA App
Just used this... Worked like a charm. Excellent work and thanks.
This is gonna help out alot of people.
ill be using this in the next few days, got to return my eris cuz trackball is going out :/
TopazAaron said:
ill be using this in the next few days, got to return my eris cuz trackball is going out :/
Click to expand...
Click to collapse
Note that this ROM does not replace the bootloader - so, if you have the engineering bootloader on your phone, you might just want to flash the MR2 RUU (or the corresponding PB00IMG.zip) immediately after booting this (no point in doing the OTA twice). Or, for folks that know their way around fastboot, if they have the S-OFF bootloader, there is always the option to put an S-ON bootloader back onto the phone thusly[SIZE=+1]**[/SIZE]:
Code:
fastboot flash hboot hboot_7501a_1.47.0000_091023.nb0
I did things this way (no replacement of the bootloader) because most of the folks that did their Eris rooting the "old school" way - and have the Engineering bootloader on their phone (1.49.2000 S-OFF) are comfortable using adb or fastboot, et cetera - and probably have enough knowledge to manually replace their bootloader; whereas the late-comers to the rooting party (leakers and others) that are not familiar with these methods probably used "one click" or similar, so they probably don't have the S-OFF bootloader on their phone anyway.
If I was going to return a phone to VZW, and was concerned that a computer forensics expert was going to examine my phone (I'm 99.999% confident that this does NOT happen), I would apply the MR2 and then take the OTA after that.
Here are the reasons why (these are really only motivations for the ultra-paranoid):
- None of the dev ROMs have ever touched the "NVRAM" area of the phone, whereas the "leak" PB00IMG.zip ROMs did manipulate that. So, phones that went through a leak-flash install still have evidence (in NVRAM) that they have been flashed with unofficial software releases (from HTC), even if the so-called "ROM" has been replaced. The only way to over-write that is to re-write the NVRAM using a VZW-sponsored RUU (or corresponding PB00IMG.zip file). In my mind, that is the MR2, not the "Official" ( == Leak-V3) RUU.
- The same thing is true of the "misc" partition - evidence of fooling around with HBOOT+PB00IMG.zip files persists in the misc partition if you do not take steps to overwrite it. (I flashed and rooted my phone an absurd number of times yesterday (for testing), and right now my misc partition reports "2.19.605.1" because the last thing that I did was install the S-OFF bootloader using HBOOT and the battery-pull trick).
- Forensic evidence in the form of directory or file timestamps probably can determine if a phone has a non-factory, or non-RUU software on it. The same thing is probably true of very low-level (yaffs2) filesystem storage order - there is no reason to believe that the file storage order (relative to the linear page layout of flash memory) will be preserved with a non-stock installer.
But, as I said, the above considerations are for the truly paranoid. VZW doesn't look at phones that carefully, and probably can not for economic reasons - and all the things I mentioned above can not be determined easily (for instance by a retail clerk looking at the booted phone)
But in a way, it doesn't matter anyway - because of the "checkin" process that happens every time the phone boots up, and the pattern of phone activations or market history, Google and VZW have enough information available (between them) in the form of user activity that they could identify every rooted Android user on the VZW network - if they cared enough to do so.
As I said, if I were going to return a phone, I would do the "misc" partition hack, install the MR2 RUU (or matching PB00IMG.zip file), and then take the OTA - and then finally perform a factory reset. But even that is probably far more effort than is necessary.
bftb0
[SIZE=+1]**[/SIZE] Flashing the bootloader is the single most dangerous operation you can perform. Make damn sure the file you are planning on flashing has the correct MD5 signature, as "fastboot" does not check a single thing - it will allow you to flash total garbage to the phone.
I'm shipping back an Eris which I used this method on to remove root, but don't have time to do the 2. 1 update, do you think VZW cares that its running 1. 5?
Sent from my FroyoEris using Tapatalk
eriscentro said:
I'm shipping back an Eris which I used this method on to remove root, but don't have time to do the 2. 1 update, do you think VZW cares that its running 1. 5?
Click to expand...
Click to collapse
Doubt it matters. It takes about 20 minutes for the full OTA 2.1 update, but once you kick it off, the entire process requires no interaction - go do something else for 20 minutes.
You might also want to do a factory reset using the the phone's menu - that will clear the activation status of the phone.
ok... I read bftb0's post... but not sure I'm following
I did the universal one click root method to root my phone and I'm not sure if I need to go to the trouble of flashing something to fix the bootloader or w/e...(not sure if I even messed with the bootloader, maybe I did but this is the noob coming out in me)
If I wanted to send my eris back today to verizon, wouldn't flashing this new zip fix everything I need it to fix and make it comepletely back to its original stock settings??
NPH- said:
ok... I read bftb0's post... but not sure I'm following
I did the universal one click root method to root my phone and I'm not sure if I need to go to the trouble of flashing something to fix the bootloader or w/e...(not sure if I even messed with the bootloader, maybe I did but this is the noob coming out in me)
If I wanted to send my eris back today to verizon, wouldn't flashing this new zip fix everything I need it to fix and make it comepletely back to its original stock settings??
Click to expand...
Click to collapse
Except the bootloader and radio.
Sent from my xtrSENSE Eris using XDA App
NPH- said:
ok... I read bftb0's post... but not sure I'm following
I did the universal one click root method to root my phone and I'm not sure if I need to go to the trouble of flashing something to fix the bootloader or w/e...(not sure if I even messed with the bootloader, maybe I did but this is the noob coming out in me)
If I wanted to send my eris back today to verizon, wouldn't flashing this new zip fix everything I need it to fix and make it comepletely back to its original stock settings??
Click to expand...
Click to collapse
You will be fine. The radio gets flashed by the 2.1 OTA, and you never replaced your bootloader with the one-click method, so that is already stock.
If it happens that you were one of the "leakers", then you have the 1.49.0000 S-ON bootloader, and VZW has shipped phones with that, too.
Be happy.
bftb0
I found that I couldnt re-root the phone with this flashback. I ended up using the PB00IMG.zip file on the SD card and let the phone do itself over. No luck on this one.
Used this today, walked into Verizon store. They looked at it. Sending me a new one as we speak. THANK YOU!!!
on my 5th
rvpartsguy said:
Yep thanks .... will make it easy when I send this phone back for my 5th eris
Click to expand...
Click to collapse
This will make it easier when i get my 6th..
Just received my 5th...lol
Heard as stock runs low for replacements, in certain areas, they are receiving a Droid 2... Can anyone confirm????
Looking to get the latest updates from HTC faster than the International LTE, GSM and American Carriers AT&T and T-Mobile variants, well here is a guide to help you convert your HTC One into a developer edition. I can confirm that it works with the European HSPA and LTE bands. Doing this will also update you directly to 5.0.2 Lollipop
Read This First:
You must be S-OFF
You must be HTCDev Unlocked
You must have CWM or TWRP recovery installed
You must charge your phone to AT LEAST 50%
You must know how to use ADB and Fastboot
You must have any KitKat or Lollipop firmware installed
Your SD Card will be WIPED, so make a backup of your files
This WILL NOT work on the CDMA HTC One
Even though this is 100% safe, I am not responsible if you break your phone
Part 1: Changing your CID and MID (Model ID)
Reboot into bootloader
Enter fastboot mode
Open a CMD window and type (without quotes) "fastboot oem writecid BS_US001
Then type (without quotes) "fastboot reboot-bootloader"
To confirm you have the above CID type in (without quotes) "fastboot getvar cid" or "fastboot oem readcid"
If it shows "cid: BS_US001" then you are ready to continue to the next step
Now you have to change your Model ID (MID) (Skip this if you have the AT&T or GPE variant), you now have to download this: MID Change tool
Now boot into Android and place the MID Change tool on your SD Card
Now reboot into recovery
Then find and flash the MID Change Tool
Once inside Aroma Installer you have to select the MID PN0712000
Then tap next and your MID will be changed
Part 2: Downloading and running the RUU
Firstly, download the RUU from here: RUU_M7_UL_L50_SENSE60_MR_BrightstarUS_WWE_7.17.1540.7_Radio_4T.35.3218.16_10.33Q.1718.01L_release_420191_signed_2.exe
Now open the RUU file
Follow the steps in the RUU, accepting any agreements. Meanwhile make sure your phone is in Fastboot mode
Now let the RUU do its work and about 4-10 minuites later you will have a full Developer Edition HTC One (M7)
Please press the thanks button if this helped you
Thanks! But what's the difference? I mean the normal edition and this?
alomex21 said:
Thanks! But what's the difference? I mean the normal edition and this?
Click to expand...
Click to collapse
Well by normal, you mean the International version and the developer edition gets updates before anyone else
Heres how the updates go to variants from first to last
1. HTC One GPE > 2. HTC One Developer Edition/Unlocked Edition > 3. International HTC One > 4. Carrier Variants (Like EE in UK and Verizon in US)
Since the Lollipop Sense update is imminent, I have updated the thread with the latest RUU, the 4.4.3 Sense 6 RUU.
dd98 said:
Since the Lollipop Sense update is imminent, I have updated the thread with the latest RUU, the 4.4.3 Sense 6 RUU.
Click to expand...
Click to collapse
:good:
I wasn't aware they had released a signed RUU for 6.07.1540.2. Not even able to find it on HTCDev.com...
alray said:
:good:
I wasn't aware they had released a signed RUU for 6.07.1540.2. Not even able to find it on HTCDev.com...
Click to expand...
Click to collapse
its on their actual website but i only found it yesterday
alray said:
:good:
I wasn't aware they had released a signed RUU for 6.07.1540.2. Not even able to find it on HTCDev.com...
Click to expand...
Click to collapse
dd98 said:
its on their actual website but i only found it yesterday
Click to expand...
Click to collapse
Yeah it's crazy the M8 DE Lollipop RUU is already out also
it's here in case you need the link
http://dl3.htc.com/application/RUU_...G_20.68.4196.01_F_release_411207_signed_2.exe
clsA said:
Yeah it's crazy the M8 DE Lollipop RUU is already out also
it's here in case you need the link
http://dl3.htc.com/application/RUU_...G_20.68.4196.01_F_release_411207_signed_2.exe
Click to expand...
Click to collapse
Thanks, but I WANT LOLLIPOP SOON!!!
dd98 said:
Thanks, but I WANT LOLLIPOP SOON!!!
Click to expand...
Click to collapse
lol, well I bet theirs an M8 right down the street with your name on it
clsA said:
lol, well I bet theirs an M8 right down the street with your name on it
Click to expand...
Click to collapse
I cant, I love beats too much
dd98 said:
I cant, I love beats too much
Click to expand...
Click to collapse
The M8 has BOOMsound, I never noticed a difference between it and my m7
Hi there & thanks for the write-up! Thought I´d share my experience from following your guide.
At first try I thought I had bricked my device. It all started off good, but when I ran "fastboot reboot-bootloader" prior to executing the RUU, my device didn´t boot. No LED, no display, nothing. It was dead!
During the last year I´ve been going back & forth between different firmwares (GPE, Sense etc) and today I had apparently hit a dead end. The device showed typical symptoms of being hard bricked. After trying all kind of imagenable key combinations & gooling, I found dexter93´s [UNBRICK][BETA] HTC Unbricking Project http://forum.xda-developers.com/showthread.php?t=2770684
Ran the unbricking tool which recorgnized my device and started processing. When done I tried to power on the device without success. At this time I had givven up. But for some unknown reason I tried to get into fastboot mode once again. And to my surpise it worked!
Now I knew that it was possible to restore the device to some operation state. With that in mind, I went for a second try of converting it to dev edition. The procedure went fine until I started the RUU which abruptly crashed. I´m running Windows 8.1 x64. Turned out I needed to install Microsoft Visual C++ 2008 Redistributable Package (x86) http://www.microsoft.com/en-us/download/details.aspx?id=29 to be able to successfully run the RUU.
After the RUU I rebooted into the new installation only to find out that my mobile network didn´t work! It suprised me since OP wrote that the release was supposed to work in Europe. After some more depressing thoughts of failure I realized the I had removed (as instructed) the SIM when running the HTC Unbrick Project tool. Reinserted the SIM and I was able to connect to my cellular network provider.
The guide well structured and easy to follow. One minor suggestion for improvement could be to alter step #5 in the second part from:
5. Then type (without quotes) "fastboot flash zip firmware.zip"
to:
5. Then type (without quotes) "fastboot flash zip 5.11.1540.9.zip"
Just a minor note. Thanks for the guide & keep up the good work!
gechu said:
Hi there & thanks for the write-up! Thought I´d share my experience from following your guide.
At first try I thought I had bricked my device. It all started off good, but when I ran "fastboot reboot-bootloader" prior to executing the RUU, my device didn´t boot. No LED, no display, nothing. It was dead!
During the last year I´ve been going back & forth between different firmwares (GPE, Sense etc) and today I had apparently hit a dead end. The device showed typical symptoms of being hard bricked. After trying all kind of imagenable key combinations & gooling, I found dexter93´s [UNBRICK][BETA] HTC Unbricking Project http://forum.xda-developers.com/showthread.php?t=2770684
Ran the unbricking tool which recorgnized my device and started processing. When done I tried to power on the device without success. At this time I had givven up. But for some unknown reason I tried to get into fastboot mode once again. And to my surpise it worked!
Now I knew that it was possible to restore the device to some operation state. With that in mind, I went for a second try of converting it to dev edition. The procedure went fine until I started the RUU which abruptly crashed. I´m running Windows 8.1 x64. Turned out I needed to install Microsoft Visual C++ 2008 Redistributable Package (x86) http://www.microsoft.com/en-us/download/details.aspx?id=29 to be able to successfully run the RUU.
After the RUU I rebooted into the new installation only to find out that my mobile network didn´t work! It suprised me since OP wrote that the release was supposed to work in Europe. After some more depressing thoughts of failure I realized the I had removed (as instructed) the SIM when running the HTC Unbrick Project tool. Reinserted the SIM and I was able to connect to my cellular network provider.
The guide well structured and easy to follow. One minor suggestion for improvement could be to alter step #5 in the second part from:
5. Then type (without quotes) "fastboot flash zip firmware.zip"
to:
5. Then type (without quotes) "fastboot flash zip 5.11.1540.9.zip"
Just a minor note. Thanks for the guide & keep up the good work!
Click to expand...
Click to collapse
Thanks, i forgot to change it after updating the RUU and firmware, but I just realized that flashing the 5.11.1540.9 firmware causes problems for users on lollipop firmware, Im going to re-write the guide soon!
Instructions re-written to ensure people on Lollipop firmwares don't get bricked in QHSUSB_DLOAD mode
dd98 said:
Instructions re-written to ensure people on Lollipop firmwares don't get bricked in QHSUSB_DLOAD mode
Click to expand...
Click to collapse
Thanks for your Work
Did you see these >> http://forum.xda-developers.com/showpost.php?p=58224092&postcount=6780
http://forum.xda-developers.com/showpost.php?p=58224358&postcount=6782
It's almost here !!
I'm guessing ii don't need to run the change MID if my MID is already PN0712000? Or should I run it anyway?
Working for me. Thanks!
I can confirm that I came from GPE Lollipop and got the device recognized as QHSUSB_DLOAD.
gechu said:
I can confirm that I came from GPE Lollipop and got the device recognized as QHSUSB_DLOAD.
Click to expand...
Click to collapse
Was this before or after I posted the new guide, because with the new guide I came from GPE 5.11.1700.3 down to the developer edition 6.07.1540.2 without any problem, twice. Try this to unbrick your phone, use Ubuntu 14.04 and it should work without problems
I used the initial guide, and brought the device back to life using the tool you referenced.
gechu said:
I used the initial guide, and brought the device back to life using the tool you referenced.
Click to expand...
Click to collapse
Ok well now in future, you should not get bricked using this guide
Virgin Mobile USA Users Only!
I've been working on a folder that has all of the files I've collected and saved on my pc since I welcomed the Virgin Mobile HTC Desire 816 into my home. I've heard of people (especially noobs) who've bricked their phones and couldn't find or deleted their backups, so I'm posting them here. I've made a backup of the stock rom on both ClockworkMod Recovery and TWRP (I've never used Phil's Recovery, but I'm sure someone else has made one for it), so both versions will be accessible to you if you decide to change recoveries. After flashing, please wipe/factory reset before rebooting system. Anyways, here's the link to the folder. Happy flashing
Link: https://drive.google.com/folderview?id=0ByabtAsA5CmscUU1M0JmcFNaNEk&usp=sharing
Edit: If you want to go back to the stock Virgin Mobile Rom WITHOUT ROOT, here's the link to HTC's Rom: http://www.htc.com/us/support/htc-desire-816-virgin-mobile/news/
Good, but
The TWRP back up failed for me, but the CWM worked. And you might want to remove your accounts dude. Just saying, thats not good.
Thanks.
deleted
Remove Sprint SIM Lock
hi,
I want to use your files to remove the simlock from sprint, which of all files that you got should use to flash the desire 816 without the simlock?
Thanks.
JP.
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
I'm in desperate need of a stock rom if anyone can help me out, was fiddling with root access and ended up losing my entire notification drawer and home button and whatever you call the square button. I have twrp installed but no rom.
Also this is a general LG LEON LTE thread because there seems to be almost no support for the phone.
Hey I know there are others or there looking for the same thing, any help would be appreciated.
seriously there are other people out there looking for the same thing someone give us a back up image.
HEY
jeremiah.m.gustafson said:
seriously there are other people out there looking for the same thing someone give us a back up image.
Click to expand...
Click to collapse
will a nandroid backup do for you? If so i can definitely help you out
i was looking for a link or two
I recently just got back into carrier devices an havent bothered with moddin devices in about two years i own two nexus devices an have sideloaded them for years with corporate emails an only have gone as far as tweakin boot images an on my older droids flashing custom mods daily... My only question remains with these newer junky devices how does one gain su if needed safely for things like otg access. It seems to me almost every carrier device is worth rooting an modding nowadays, an nexus devices are still the only ones that have a program thats stable an universal for all manufactuers as far as updating an management of a os whether it be stock or the user decides to go third party.
With that said.. Thats why awhile ago i stopped modding phones, using a windows tablet (for a full version of msdos) an since i had mastered my PB9110 version of my nexus one, i would flash my images via adb and sideload images with command line, in time ive sampled nexus after nexus, never using (play) an now back to a carrier device with no program support except 3rd party mods... Which in reality is great once you do have a nandroid backup an a stock rom... Thus the ability with the nexus factory image. Where are the steps and how tos my friends????
T-Mobile LG Leon H345 LTE 5.1.1 Version 10f Root
T-Mobile LG Leon H345 LTE 5.1.1 Version 10f Root. method worked for me. Not responsible if u brick ur phone.
I am not the author of this file.All the credits to the guys in below link
androidforums.com/threads/leon-one-click-root-works-on-10d-10e-ms345-h345-no-kingroot.938062
1) Install the latest LG USB drivers
2) USB debugging should be enabled, go to Settings to allow it.
3) Enable OEM Unlock in developer options
4) Download the attached files and extract into a folder
wxx.androidforums.com/attachments/lg_leon_ocr_v2-zip.93091/
5) Go to the folder, hold the Shift Button on the Keyboard and Right-Click on the Folder
6) Click on the ‘Open Command Window Here’ Option
4) Connect LG Leon to computer and set it to MTP.
5) Type root.bat in command window
6) Just wait until everything is finished and check for root
7) Download TWRP recovery image
wxx://dl.twrp.me/c50/twrp-2.8.7.0-c50.img
8) Use flashify app to install the recovery image and Quick boot app to boot into recovery
Flashify (Google App Store App) OEM Backups
jeremiah.m.gustafson said:
I'm in desperate need of a stock rom if anyone can help me out, was fiddling with root access and ended up losing my entire notification drawer and home button and whatever you call the square button. I have twrp installed but no rom.
Also this is a general LG LEON LTE thread because there seems to be almost no support for the phone.
Click to expand...
Click to collapse
Hey! I just used a program called Flashify (Found on Google Play Store) to back up both my Kernel (Boot) and System (Recovery) for my LG LEON LTE. I haven't attempted to reinstall these backups using Flashify as of yet, since I just rooted my phone and installed TWRP bootloader so I can try out a ROM... so, I have no idea how it works or if you can use it with any other bootloader app. However, I am attempting to offer you some kind of OEM Backup. I'm pretty new at some of this. I haven't posted enough to add links yet, but I'm going to try.
I have a LG Leon LTE for T-Mobile. My OEM details are as follows:
Android Version: 5.1.1 Lollipop
Baseband Version: MPSS.DPM.2.0.c11-00021-M8936FAAAANUZM-1.19638.1.19833.1
Kernel: 3.10.49
Build: LMY47V
Software Version: H34510f
These downloads are only available until 11/26/2015 due my only having a free account on the hosts site. I hope they help!
Kernel (Boot): OEM 3.10.49 @ http: //sabercathost. com/5Y7 (60 second wait for free download)
System (Recovery): OEM @ http: //sabercathost. com/5Y8 (60 second wait for free download)
Again.. I used Flashify (for root users) free from Google Play Store to create these backups. I have no clue if they can be used by any other programs for recovery. If you have/or can get Flashify, I'd like to believe they can be used for your STOCK recovery.
I may try and make a more common backup of these using ROM Toolbox Pro and see if I can host the files elsewhere that isn't limited to 7 days before paying for premium. If I do, I'll come back and update you or anyone else in need with the new locations.
Wish you luck!
Could u please post that I need a nandroid of that desperately
Aurey24 said:
will a nandroid backup do for you? If so i can definitely help you out
Click to expand...
Click to collapse
Messed up my phone and lossy original backup if u could post that nandroid I would really appreciate it. Thanks