Related
Got this From Our Friends Over At Droidmodderx
First Post.
1. Download .902 FXZ zip and extract to desktop here
2. Install the Motorola Mobile Drivers here
3. Install RSD Lite 5.6. here.
4. Make sure your Motorola Droid Bionic is powered on and backed up.
5. Plug your Motorola Droid Bionic into a back USB port on your computer.
6. Open the zip and copy EVERYTHING inside to the desktop(inside the zip there is a folder, you can either put the folder on the desktop it Everything inside it your choice)
7. Run “RSD Lite” on your computer
8. Press the “. . .” button next to the box labeled “Filename”
9. Browse and open the FXZ file
10. Wait for the program to read the file, then choose “Uncompress And Start Flashing”
11. Now, the device will slowly flash the FXZ file.
12. When flashing completes, the device will reboot into recovery and install the two radio images.
13. Congratulations! You’ve restored your Motorola Droid Bionic.
downside..... wipes INTERNAL Sdcard
So save the stuff you want to keep on your PC
Did you not realize that this was released here by daywalker04 first and that everyone else got it here? Just saying...give credit where due and understand how and where valuable files like the full xml.zips come from.
cellzealot said:
Did you not realize that this was released here by daywalker04 first and that everyone else got it here? Just saying...give credit where due and understand how and where valuable files like the full xml.zips come from.
Click to expand...
Click to collapse
Well...(sarcastically) as you can see I don't have a problem giving due credit. I assumed that the people at Droidmodderx released this first. If I knew daywalker04 released this first I would have initially gave him credit.
Sent from my DROID BIONIC using Tapatalk
iNsAnEmOd said:
Well...(sarcastically) as you can see I don't have a problem giving due credit. I assumed that the people at Droidmodderx released this first. If I knew daywalker04 released this first I would have initially gave him credit.
Sent from my DROID BIONIC using Tapatalk
Click to expand...
Click to collapse
Not to mention, the search function shows devices that are not even close... Great post, thank you for the refresh
SMILE It's Not Illegal Yet
get to .902 stock from what?
is this from anything?
I am at 901 rooted. with Ecliplse 2.1. (nice!)
If as and when I want to get to 902 stock, unrooted, I use this FXZ, right?
theoretically, wherever you are, rooted, unrooted, from 886 all the way up, this FXZ process will bring you to stock 902?
thanks
Very nice, thanks.
idivorceyou said:
is this from anything?
I am at 901 rooted. with Ecliplse 2.1. (nice!)
If as and when I want to get to 902 stock, unrooted, I use this FXZ, right?
theoretically, wherever you are, rooted, unrooted, from 886 all the way up, this FXZ process will bring you to stock 902?
thanks
Click to expand...
Click to collapse
good question i'll try it out
Yep i just went to stock 5.8.886 and then used this FXZ and now I'm on .902.!!! Super Easy!! No CDT Failure or any thing. I didnt even have to flash those updates!!
Very nice I will try this now, I am currently on Eclipse V2.0 and looking to update to either 2.1 or ICS so this will be a good start.
Failed. I have never been able to get fxz to work for me. did a fresh driver install and everything. I actually thought it was going to work too. it failed at 5/12 that seems to be the spot all of them fail for me. Oh well guess i will have to try something else. Thanks for the file though
likwidsoul said:
Failed. I have never been able to get fxz to work for me. did a fresh driver install and everything. I actually thought it was going to work too. it failed at 5/12 that seems to be the spot all of them fail for me. Oh well guess i will have to try something else. Thanks for the file though
Click to expand...
Click to collapse
Did you extract the zip?
Sent from my XT875 using Tapatalk
i let rsd uncompress and flash. i will try uncompressing and flashing the xml
likwidsoul said:
i let rsd uncompress and flash. i will try uncompressing and flashing the xml
Click to expand...
Click to collapse
You have to open the zip and place that folder to the desktop
Sent from my XT875 using Tapatalk
got stuck in boot loop afterwards. it said it 'PASS'ed but it didn't.. idk i've never had problems with FXZ'ing my Bionic until now
---------- Post added at 08:51 PM ---------- Previous post was at 08:36 PM ----------
RSD Lite would not recognize anything in the unzipped folder, it recognized my original download file and when flashing that file it makes it all the way through the steps and says PASS, but then a bootloop
---------- Post added at 08:57 PM ---------- Previous post was at 08:51 PM ----------
it finally worked, and booted up fine, but it is saying that I am on 5.5.886, while the file that I flashed is the one that I downloaded from this thread...im going to re-download it and try again, maybe something went wrong in my system. do you have an md5 i can get please?
this is the md5 i have: 96e10ae9b00b696e8efed0e076632a53
Question
Alright, I must be missing something really obvious, because this has not been discussed:
I have installed Moto Drivers, installed RSD Lite 5.6, downloaded the .902 filed mentioned in the OP. Phone is on, working just fine, has USB debugging on, etc. I plug the phone in, and start-up RSD. When I try to find the FXZ file, I cannot find anything with FXZ, I have no idea what I am looking for.
Once I have downloaded the .902 file- I have tried to install with just the file, and then tried to find this "FXZ" file after extracting it with WINRAR.
I reviewed the video instructions by Droidmodderx that was listed in the OP. But the video just makes it seem like I am finding one file called "FXZ". I can never find any right file like that when I am running RSD. When when I try to use the un-extracted file in RSD, it does not give me the option of uncompressing and install, it only allows me to uncompress.
I cannot find the right file.
I know I am missing something very obvious, but I just can't find it.
Thanks for your help
Dukeuni said:
Alright, I must be missing something really obvious, because this has not been discussed:
I have installed Moto Drivers, installed RSD Lite 5.6, downloaded the .902 filed mentioned in the OP. Phone is on, working just fine, has USB debugging on, etc. I plug the phone in, and start-up RSD. When I try to find the FXZ file, I cannot find anything with FXZ, I have no idea what I am looking for.
Once I have downloaded the .902 file- I have tried to install with just the file, and then tried to find this "FXZ" file after extracting it with WINRAR.
I reviewed the video instructions by Droidmodderx that was listed in the OP. But the video just makes it seem like I am finding one file called "FXZ". I can never find any right file like that when I am running RSD. When when I try to use the un-extracted file in RSD, it does not give me the option of uncompressing and install, it only allows me to uncompress.
I cannot find the right file.
I know I am missing something very obvious, but I just can't find it.
Thanks for your help
Click to expand...
Click to collapse
xml file is what your looking for...
put phone on Ap Fastboot
FXZ is a made up abbreviation of Full XML Zip that started on XDA when the Droid 3 was released and we first saw this new file format come into use with fastboot bootloader support for the dual core Motorolas.
People still often wrongly refer to them as SBF files because that was the common firmware file format for prior generations of Motorola devices.
The XML.zip format and fastboot is a far more versatile, flexible and safer flash interface so it is an important distinction to make to understand how these files work and what they are.
These files are a set of signed partition images with an XML file that runs them in sequence in RSD Lite.
They can also be flashed with the fastboot.exe in command line as individual files, giving a much more finite control over the flashing process and the ability to selectively fix or change only what is needed rather than completely flash the entire device.
The XML files themselves are scripts that can be modified to perform certain operations like wiping user data or not.
They are very powerful tools and the ability to use them effectively to restore your phone is critical if you want to be able to have fun and mod your device safely.
Ugh
Well, looks like this will be a great learning experience- I not have a "bricked" phone.
I finally was able to get RSD to recognize the phone- I did not have the phone set to "PC Mode", it was only set to "Mass Storage". Once RSD saw the phone I started the process as described in the video- clicked the .tar file, clicked on uncompres and install, and let it go. The uncompress took some time, but once it was done it start the install process-
Bam- fail. Does not seem like it installed a single thing, just automatic fail. The status bar reads:
"Failed flashing process. Failed flashing process. 1/15 flash cdt.bin "cdt.bin" -> Phone returned FAIL.; phone connected"
I disconnect my phone, turn it off, and then try to turn it back on. I am forced to do the fastboot (Power button and volume down). I try it again, same result. I uncompress the file myself with WINRAR, and then select just the XML File- "default_flash_targe"- same result.
Well, what do I do now? my phone is dead, but I am excited to finally learn some more about this phone and how to deal with this type of stuff.
---------- Post added at 12:55 AM ---------- Previous post was at 12:14 AM ----------
Not sure if it makes a difference, but I am not sure which version I was on prior to attempting to do the fxz. I am looking at downloading the .893 stock and going from there. See if that will work at all.
Well I figured out why everyone using this thread is having difficulty.
THE OP HAS THE WRONG XML.zip LINKED!!! PLEASE EDIT THIS POST IMMEDIATELY WITH THE CORRECT LINK!
cellzealot said:
Well I figured out why everyone using this thread is having difficulty.
THE OP HAS THE WRONG XML.zip LINKED!!! PLEASE EDIT THIS POST IMMEDIATELY WITH THE CORRECT LINK!
Click to expand...
Click to collapse
THERE IS SOMETHING WRONG..... NONE OF YOU GUYS ARE EXTRACTING THE ZIP.(or Tar). INSIDE THE TAR, THERE IS ANOTHER ONE. EXTRACT THAT TOO. INSIDE THAT THERE IS A FOLDER LABELED "p2d_targa_cdma_targa-user-2.3.4-5.5.1_84_DBN-55-110814-release-keys-Verizon-US". PUT EVERYTHING INSIDE THAT FOLDER ON THE DESKTOP AND RUN RSD.
That is the wrong file. That is the original stock release xml.zip
That is why everyone is hosing their using this file. You can't flash back to the original firmware with the original cdt.bin anymore.
Look at the error in Dukeuni's post above!
What is wrong is that you are posting the wrong files and people with even less experience than yourself are unaware and getting stuck.
So I tried to install JB from recovery and it said successful but then it was stuck in a bootloop at the droid eye. I cleaned the cache and some other things and it still didn't work. Then I made it worse by trying a second time to install JB from my SD card and it failed. Now I just get a black screen after the moto symbol. So I am trying to use RSD lite 6.1.4(Newest version?) and the JB FXZ from "h ttp://sbf.droid-developers.org/cdma_targa/list.php" to flash it but it is failing and saying "Failed flashing process. 5/24 oem fb_mode_set -> Phone returned FAIL" Any ideas of how to get past this? Thanks!
Dirtdawg57 said:
So I tried to install JB from recovery and it said successful but then it was stuck in a bootloop at the droid eye. I cleaned the cache and some other things and it still didn't work. Then I made it worse by trying a second time to install JB from my SD card and it failed. Now I just get a black screen after the moto symbol. So I am trying to use RSD lite 6.1.4(Newest version?) and the JB FXZ from "h ttp://sbf.droid-developers.org/cdma_targa/list.php" to flash it but it is failing and saying "Failed flashing process. 5/24 oem fb_mode_set -> Phone returned FAIL" Any ideas of how to get past this? Thanks!
Click to expand...
Click to collapse
Take the CDT file and the BOOT.IMG from the JB FXZ and overwrite the same files in an ICS (246) FXZ. It probably won't work, but you should be able to reach your recovery. If you have the JB update on your SD card just install it from there and you should be good to go.
Dirtdawg57 said:
So I tried to install JB from recovery and it said successful but then it was stuck in a bootloop at the droid eye. I cleaned the cache and some other things and it still didn't work. Then I made it worse by trying a second time to install JB from my SD card and it failed. Now I just get a black screen after the moto symbol. So I am trying to use RSD lite 6.1.4(Newest version?) and the JB FXZ from "h ttp://sbf.droid-developers.org/cdma_targa/list.php" to flash it but it is failing and saying "Failed flashing process. 5/24 oem fb_mode_set -> Phone returned FAIL" Any ideas of how to get past this? Thanks!
Click to expand...
Click to collapse
1. open the file : cdma_targa_9.8.2O-72_VZW-22_cfc
2. remove the line : <step operation="oem" var="fb_mode_set" /> AND <step operation="oem" var="fb_mode_clear" />
3. Save
4. Try flash use RSD
mc_akiong said:
1. open the file : cdma_targa_9.8.2O-72_VZW-22_cfc
2. remove the line : <step operation="oem" var="fb_mode_set" /> AND <step operation="oem" var="fb_mode_clear" />
3. Save
4. Try flash use RSD
Click to expand...
Click to collapse
I found this method last night on a RAZR forum. I just opened the file up in notepad and removed those 2 lines and RSD worked great! I was so excited because I had just had it up at Verizon and they had said the phone was dead. Thanks for your responses!
Dirtdawg57 said:
I found this method last night on a RAZR forum. I just opened the file up in notepad and removed those 2 lines and RSD worked great! I was so excited because I had just had it up at Verizon and they had said the phone was dead. Thanks for your responses!
Click to expand...
Click to collapse
Yeah always go to the HoB for this stuff Samuri will have your back
Sent from my SCH-I605 using Xparent Skyblue Tapatalk 2
Obsidian... said:
Yeah always go to the HoB for this stuff Samuri will have your back
Sent from my SCH-I605 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
Sir i did this exactly as stated, and still i get the fail at 5... am I to remove from the first to the second part?
saved my life(bionic)
mc_akiong said:
1. open the file : cdma_targa_9.8.2O-72_VZW-22_cfc
2. remove the line : <step operation="oem" var="fb_mode_set" /> AND <step operation="oem" var="fb_mode_clear" />
3. Save
4. Try flash use RSD
Click to expand...
Click to collapse
i've never had problems using an FXZ until i was trying to unlock my bionic for use on ATT/TMO and things went awry, and this just save my bionic from being a tinker toy....
Here's another person that had the same issue with the boot loop after sbf_flash update. He resolved the issue after wiping the data and cache in recovery. Hope that helps...someone; even if it may come a little late for you
facelessuser said:
A note to people who try and do the SBF. Wipe your data and cache in recovery if you have a boot loop after flashing. I have verified this method works, but I had to wipe my data and cache afterwards to get past an infinite boot loop.
Click to expand...
Click to collapse
Thanks
mc_akiong said:
1. open the file : cdma_targa_9.8.2O-72_VZW-22_cfc
2. remove the line : <step operation="oem" var="fb_mode_set" /> AND <step operation="oem" var="fb_mode_clear" />
3. Save
4. Try flash use RSD
Click to expand...
Click to collapse
Led me down the right path. Ended up having to decompress, edit file then create new zip. Never would have thought of it if i hadn't seen your post.
im having the same issue i believe but the sbf goes through but the phone still is stuck in some boot loop.
Dirtdawg57 said:
So I tried to install JB from recovery and it said successful but then it was stuck in a bootloop at the droid eye. I cleaned the cache and some other things and it still didn't work. Then I made it worse by trying a second time to install JB from my SD card and it failed. Now I just get a black screen after the moto symbol. So I am trying to use RSD lite 6.1.4(Newest version?) and the JB FXZ from "h ttp://sbf.droid-developers.org/cdma_targa/list.php" to flash it but it is failing and saying "Failed flashing process. 5/24 oem fb_mode_set -> Phone returned FAIL" Any ideas of how to get past this? Thanks!
Click to expand...
Click to collapse
mc_akiong said:
1. open the file : cdma_targa_9.8.2O-72_VZW-22_cfc
2. remove the line : <step operation="oem" var="fb_mode_set" /> AND <step operation="oem" var="fb_mode_clear" />
3. Save
4. Try flash use RSD
Click to expand...
Click to collapse
I know this is a pretty old thread and the last post was somewhere around two years ago, but I just thought I post something that I been pulling my hair about for a few days. I live in Cambodia located in the southeast part of Asia. But that isn't relevant to what I'm am gonna talk about. I tried many different sites looking for ways to flash my xt975. and every post was different. The gem problem that I had facing with the flash was that there were errors that would occurred when I had flashed them. One of them being steps 5/24 oem fb_mode_set -> Phone returned FAIL. This was solved by a suggestion by mc_akiong who have further the steps for my process or unbricking my phone via RSD Lite. It successfully pass that part until steps 10/21 where an error occurred that "10/22 flash lbl "lbl" -> Phone returned FAIL.. I searched everywhere on the net to figure out how to fix this problem and could not find a solution after countless hours of reading threads that didn't help pertaining to the issue I was facing. Then It had occurred to me that maybe if I try and edit the cdma_targa_9.8.2O-72_VZW-22_cfc file and edit it's properties like mc_akiong had suggest this may bypass the error. It was try this or search and waste more hours than I needed. I edit the file using wordpad since it aligns all the text properly in the manner their were scripted. I search for the line "<step operation="flash" partition="lbl" filename="lbl" MD5="60377be478e282124139a07d86ae2b80" />" and completely delete it from the script. After doing this I save it and ran RSD Lite. With fingers crossed it work and now my phone is fully operational. I have also left a image of the line that highlight what you should edit, but remember if you have problems with step 5/24 do the edit suggested above by mc_akiong and also edit this if you are facing this problem with the lbl error. I hope that this is helpful...BTW this is also my first post :highfive:
SPheDaGhost said:
I know this is a pretty old thread and the last post was somewhere around two years ago, but I just thought I post something that I been pulling my hair about for a few days. I live in Cambodia located in the southeast part of Asia. But that isn't relevant to what I'm am gonna talk about. I tried many different sites looking for ways to flash my xt975. and every post was different. The gem problem that I had facing with the flash was that there were errors that would occurred when I had flashed them. One of them being steps 5/24 oem fb_mode_set -> Phone returned FAIL. This was solved by a suggestion by mc_akiong who have further the steps for my process or unbricking my phone via RSD Lite. It successfully pass that part until steps 10/21 where an error occurred that "10/22 flash lbl "lbl" -> Phone returned FAIL.. I searched everywhere on the net to figure out how to fix this problem and could not find a solution after countless hours of reading threads that didn't help pertaining to the issue I was facing. Then It had occurred to me that maybe if I try and edit the cdma_targa_9.8.2O-72_VZW-22_cfc file and edit it's properties like mc_akiong had suggest this may bypass the error. It was try this or search and waste more hours than I needed. I edit the file using wordpad since it aligns all the text properly in the manner their were scripted. I search for the line "<step operation="flash" partition="lbl" filename="lbl" MD5="60377be478e282124139a07d86ae2b80" />" and completely delete it from the script. After doing this I save it and ran RSD Lite. With fingers crossed it work and now my phone is fully operational. I have also left a image of the line that highlight what you should edit, but remember if you have problems with step 5/24 do the edit suggested above by mc_akiong and also edit this if you are facing this problem with the lbl error. I hope that this is helpful...BTW this is also my first post :highfive:
Click to expand...
Click to collapse
Thank you so much for taking the time to note this. I ran into the same issue and solved it because of you. Just know that what info you took your time to give and learn many of us wouldn't have had the patience or time to get that ourselves. Again....thank you!!!
DROID BIONIC bricked after root and bootstrap.apk
droid bionic bricked after bootstap. now i am installing j.b firmware via rsd lite 6.1.6 its keep flashing system.img about 1:.30m mins somebody tell me how long does it take to finish complete setup??????????????
john-ammu said:
droid bionic bricked after bootstap. now i am installing j.b firmware via rsd lite 6.1.6 its keep flashing system.img about 1:.30m mins somebody tell me how long does it take to finish complete setup??????????????
Click to expand...
Click to collapse
Three years to reply back, but I didn't take me that long to flash probably 5-10 mins probably less it was so long ago ?
---------- Post added at 09:53 PM ---------- Previous post was at 09:51 PM ----------
Deeshizzle said:
Thank you so much for taking the time to note this. I ran into the same issue and solved it because of you. Just know that what info you took your time to give and learn many of us wouldn't have had the patience or time to get that ourselves. Again....thank you!!!
Click to expand...
Click to collapse
No problem, I'm glad I could help someone with the issue, and address it as clearly as I could.
guys!
Just saw at SBf Developers that hey have uploaded some new updates there.
The Brazilian new one is: http://sbfdownload.droid-developers...LCX-35-36-release-keys-cid12-Brasil-BR.tar.gz
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!
xpc21 said:
guys!
Just saw at SBf Developers that hey have uploaded some new updates there.
The Brazilian new one is: http://sbfdownload.droid-developers...LCX-35-36-release-keys-cid12-Brasil-BR.tar.gz
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!
Click to expand...
Click to collapse
I could be wrong so wait until someone else chimes in who knows for sure or you can research what Im about to say to see if it is right.
I think they are still rsd lite compatible they just don't run things like erase/cache and data but that part might be wrong. I think they are just larger packages that you don't actually need if you have the smaller xml.zip file. I think you can stil run them in RSDlight but if not you might run a command in fastboot to run the fastboot.bat file in there and follow the instructions from there. Do a little searching if I were you but thats all my small brain knows or thinks it knows.
jayboyyy,thanks your kinda atention!
Thats what i thought when i opened the XML file.
The inside script is just like a normal firmware but i never run one like this is RSD so i have to be sure that this maybe its hit the case.
Enviado de meu XT1058 usando o Tapatalk
xpc21 said:
jayboyyy,thanks your kinda atention!
Thats what i thought when i opened the XML file.
The inside script is just like a normal firmware but i never run one like this is RSD so i have to be sure that this maybe its hit the case.
Enviado de meu XT1058 usando o Tapatalk
Click to expand...
Click to collapse
don't post the same question in two different places. I see your other thread got moved out of the dev sub forum. People won't want to help you in the future if you post the same thing in two places. Especially in appropriately in another sub forum. Just bump your thread every 24 hours if no one has responded.
also someone in your other thread also said you could rsd that file.
If I'm recalling correctly, the .tar.gz is just a packaged file that contains all the normal things flashed with RSD. Some FXZ downloads are still in .tar.gz format (maybe because of whatever source it comes from or something), and some are just packaged in .rar format, which we have to extract. RSD should be able to extract the .tar.gz on its own and then process whatever is in the XML file.
Alternatively, you could extract the files then flash through the command prompt. RSD is just the GUI version of command prompt fastboot flashing, anyway.
Hello,
Guys i have got Moto X XT1052 from a friend for few days. To mainly fix it. Actually, whenever i turn phone on. It keeps on crashing all apps, like Unfortunately, Launcher has stopped, calender and so on. It's not allowing me to touch anywhere else. So i would like to restore it. I checked all threads and found fine solution for flashing. I can do it. But those who uploaded ROMs on filefactory, it's kinda old. And downloading speed is really slow. Even when my net speed is double of it. I should get 300 KB/s some. But i am getting 50KB/s from their site. So i need help on this. If anyone can upload that ROM(XT1052_RETAIL-ASIA_4.4.4_KXA21.12-L1.26_18_cid7_CFC_1FF.xml.zip) on any other site like mediafire, Google files or torrent. I will really appreciate it. Please i urgently need it. Let me know if anything else to be done too. Because on current bootloader showing Device is Lock. And i saw youtube videos, most of them had Device is unlock. I am using this method, please take a look and let me know. Thanks. http://forum.gsmhosting.com/vbb/f78...to-x-2nd-gen-firmware-flashing-guide-1877668/
You can try to look here:
https://cloud.mail.ru/public/a083d0bb5e97/Motorola/XT1052/
https://cloud.mail.ru/public/64a43f0fcc1e/Moto_X/XT1052/
+
4.4.4 Retail GB (XT1052_RETAIL-GB_4.4.4_KXA21.12-L1.26_56_cid7_CFC_1FF.xml.zip)
4.4.4 Retail DE (XT1052_RETAIL-DE_4.4.4_KXA21.12-L1.26_54_cid7_CFC_1FF.xml.zip)
4.4.4 Retail EU (XT1052_RETAIL-EU_4.4.4_KXA21.12-L1.26_54_cid7_CFC_1FF.xml.zip)
http://forum.xda-developers.com/showthread.php?t=2976596
Here you go - https://mega.co.nz/#!U8NkgQqA!2yUsrJlNp0j_8ttzjJmHS4C4hh9cQ__vXtNKfmlm8cg
Sent from my Moto X using XDA Free mobile app
Guys, stuck in mid. Can you tell me, that do i need to unlock device first to get back to stock ROM? I tried manual flashing and RSD method too. But both failed to do anything. All apps still crashing. :l Please help me on this? New for Moto X. :l Thanks.
DarKrypton said:
Guys, stuck in mid. Can you tell me, that do i need to unlock device first to get back to stock ROM? I tried manual flashing and RSD method too. But both failed to do anything. All apps still crashing. :l Please help me on this? New for Moto X. :l Thanks.
Click to expand...
Click to collapse
First you dont need to unlock or lock your bootloader. Have you already tried to just go into recovery mode and factory reset the phone? How did the error start? What did your friend try to do, when he got the error first? What is the EXACT error message you get, while flashing?
Sent from my XT1052 using XDA Free mobile app
N00BY0815 said:
First you dont need to unlock or lock your bootloader. Have you already tried to just go into recovery mode and factory reset the phone? How did the error start? What did your friend try to do, when he got the error first? What is the EXACT error message you get, while flashing?
Sent from my XT1052 using XDA Free mobile app
Click to expand...
Click to collapse
When i do factory option in recovery mode, it just boot up phone normally. And then it shows "Unfortunately, the process com.google.process.gapps has stopped". Then it keeps poping up with more crashes, like launcher, google play services. It hardly let me touch somewhere else. And if i tap "Ok" quickly, phone just shut down. Even in recovery mode, i tried selecting "Recovery" option, and it shown me "Boot up failed". And actually my friend don't know much about phones and all this. He said it just started happening. :l Maybe he installed some weird app. And i don't get any error while flashing. Everything went fine. But when i check phone it doesn't change anything else. Same as old. Even when i erased all user data. Will just erasing data will fix it? Then after that i can do full stock ROM flashing.
Why i am not getting back to stock guys. Everything going fine. Just i checked a thread, where a guy said he is getting that "Variable not supported" something. I am getting same thing. So what can i do? :l Please help me to get back to stock ROM. I really need to fix it. Thanks.
Try motofirmware.center to try and see if they have the ROM you're looking for. I went to this site for the stock ROM for my XT1060 Developer Edition and was able to find it there. It saved me when I messed up my phone earlier this week. When you flash the stock ROM using the RSDLite program, it will do a wipe on your phone as it flashes it to your phone. When you boot up the phone after flashing the stock ROM, your programs should reinstall just fine on the phone once you log on to your Google Play account.
Cindy
DarKrypton said:
So.. i am confused with all this. Maybe you can help me with this. Thanks. I hope you don't mind.
Click to expand...
Click to collapse
We don't know what your doing, what you tried, or why it didn't work, because we can't see you or what your doing.
You need to post in a coherent straight forward manor.
I would use the manual version, so you can see what errors occur more easily.
Make sure you have the right files for your version, and understand this:
http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202
copy and paste the terminal output here using code tags.
Click to expand...
Click to collapse
You have been asked multiple times for the exact error messages. We don't know why your computer wont work... But your computer pretty much tells you each time with a specific message. You need to give us those messages.
Consider the fact that there MAY be someone here who doesn't care about you or your phone, but knows the answer. If you make it easy that person MAY help you. If you post paragraph after paragraph of text describing the error message, rather then the 1 line error message they probably wont read. Be as direct as possible, show us what you have done (I didn't really flow many of you links, why should we have to chase down this information to give you free tech support?)
Like this:
I am trying to fix a phone for a friend. Upon boot I get continuous force closes from a variety of different apps. I am left with a crashed an unusable system.
I have tried to flash _____ rom using _____ tool, but recivied the following error message
Code:
word for word error message
I found this thread: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515 on returning to stock using RDS light, and used
RETAIL-US_4.4.4_KXA21.12-L1.29.1_2_cid9_CFC_1FF.xml.zip from http://motofirmware.center/files/category/9-ghost/
There was an error durring fasboot, and there seem to be no changes to the phone.
Code:
130 [email protected] ~ % fastboot oem fb_mode_set :(
< waiting for device >
^C
130 [email protected] ~ %
Click to expand...
Click to collapse
Someone can drop in, and with out much work tell what I have done, and see that it is not working because fastboot cannot find the device.
scryan said:
We don't know what your doing, what you tried, or why it didn't work, because we can't see you or what your doing.
You need to post in a coherent straight forward manor.
I am not sure why you follow other peoples tutorials, then ask US about them. For help with your tutorial, ask the people who wrote that tutorial. If you want help here, try first with OUR tutorials. I don't say this to be mean, but we are unfamiliar with other tutorials and can only really support ours.... It gives us a standard to reference back to.
From the first page, "Returning to 100% stock with RDS or manual"
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
I would use the manual version, so you can see what errors occur more easily.
Make sure you have the right files for your version, and understand this:
http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202 about downgrading, shouldn't be an issue but not a bad idea to double check what bootloader you have.
Also make SURE you have the right firmware.
Read those threads, and if you still have an issue copy and paste the terminal output here using code tags.
Rather then downloading it from random websites, you know Moto hosts the official firmwares, at least for DE phones on their website so you can get the most recent, verified version direct from the official source rather then going through random unofficial mirrors...
Click to expand...
Click to collapse
Actually mate, i have been using that link only. But when that didn't worked. I tried others. :l But they failed too. This link shown perfect method. But i have no idea why it's keep happening. This seems more confusing that flashing ROMs on my Canvas HD. It was easy. But this is getting crazy. Please help me with this. I tried from fresh. But it's still same. Maybe you could help me with team viewer or something? Plus one thing i would like to tell you. On most tutorials they said, delete a line "<step operation="getvar" var="max-download-size" />" even it's written in that link too, which you posted. But thing is that, i extracted my firmware, and it's already not in XML file. So.. i am confused with all this. Maybe you can help me with this. Thanks. I hope you don't mind.
You have a locked bootloader, your not just flashing a rom, you need to use fastboot, a standard android tool, to restore your phone.
Your not going to flash a rom, you will be downloading that SBF you have been linked to, unzipping it and flashing each partition, AS STATED IN THE RSD THREAD.
DarKrypton said:
So.. i am confused with all this. Maybe you can help me with this. Thanks. I hope you don't mind.
Click to expand...
Click to collapse
We don't know what your doing, what you tried, or why it didn't work, because we can't see you or what your doing.
You need to post in a coherent straight forward manor.
I would use the manual version, so you can see what errors occur more easily.
Make sure you have the right files for your version, and understand this:
http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202
copy and paste the terminal output here using code tags.
Click to expand...
Click to collapse
You have been asked multiple times for the exact error messages. We don't know why your computer wont work... But your computer pretty much tells you each time with a specific message. You need to give us those messages.
Consider the fact that there MAY be someone here who doesn't care about you or your phone, but knows the answer. If you make it easy that person MAY help you. If you post paragraph after paragraph of text describing the error message, rather then the 1 line error message they probably wont read. Be as direct as possible, show us what you have done (I didn't really flow many of you links, why should we have to chase down this information to give you free tech support?)
Like this:
I am trying to fix a phone for a friend. Upon boot I get continuous force closes from a variety of different apps. I am left with a crashed an unusable system.
I have tried to flash _____ rom using _____ tool, but recivied the following error message
Code:
word for word error message
I found this thread: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515 on returning to stock using RDS light, and used
RETAIL-US_4.4.4_KXA21.12-L1.29.1_2_cid9_CFC_1FF.xml.zip from http://motofirmware.center/files/category/9-ghost/
There was an error durring fasboot, and there seem to be no changes to the phone.
Code:
130 [email protected] ~ % fastboot oem fb_mode_set :(
< waiting for device >
^C
130 [email protected] ~ %
Click to expand...
Click to collapse
Someone can drop in, and with out much work tell what I have done, and see that it is not working because fastboot cannot find the device.
Ok, let me clear everything to you.
I am trying to fix a phone for a friend. Upon boot I get continuous force closes from a variety of different apps. I am left with a crashed an unusable system.
I have tried to flash Moto X XT1052 (XT1052_RETAIL-ASIA_4.4.4_KXA21.12-L1.26_18_cid7_CFC_1FF.xml) rom posted above by "athulele" using "fastboot" tool, but recivied the following error message. This is first error, with fresh installing. Trying with first command. "fastboot oem fb_mode_set"
Code:
"fastboot" is not recognized as an internal or external command, operable program or batch file.
It's obviously because "fastboot" and ADB are not present in ROM folder. So i guess i need to copy all files from a software i installed "Minimal ADB and Fastboot" as per other tutorials. Which made me more confused. So i want to go with your tutorial.
Second thing, if i make copy of files in ROM folder. It starts taking commands, but with another error. Which is :
Code:
C:\Users\(Username)\Desktop\XT1052_RETAIL-ASIA_4.4.4_KXA21.12-L1.26_18_cid7_CFC_1FF.x
ml>fastboot flash partition fpt.bin
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
error: cannot load 'fpt.bin': No error
After that, i think i should not continue. After this maybe please take a look. Let me know where i am doing wrong. Must be totally wrong where i copied those files in ROM folder. I couldn't continue without them. Because of that error. Let me know if i am missing any driver. Because as fasr i know i installed all latest drivers. Let me know. Thanks.
Click to expand...
Click to collapse
DarKrypton said:
Ok, let me clear everything to you.
Click to expand...
Click to collapse
Try the commands without "fastboot OEM mode set". Also if your friend had completely stock system, you can try flashing only system.img, boot.img, recovery.IMG
After you flash this, erase data by " fastboot erase userdata" this will erase everything including sdcard .
After that "fastboot erase modemst1" and "fastboot erase modemst2" to clear modem cache. Then try rebooting into system.
Also, you had typed fpt instead of gpt. That's why you got the error
Sent from my Moto X using XDA Free mobile app
athulele said:
Try the commands without "fastboot OEM mode set". Also if your friend had completely stock system, you can try flashing only system.img, boot.img, recovery.IMG
After you flash this, erase data by " fastboot erase userdata" this will erase everything including sdcard .
After that "fastboot erase modemst1" and "fastboot erase modemst2" to clear modem cache. Then try rebooting into system.
Also, you had typed fpt instead of gpt. That's why you got the error
Sent from my Moto X using XDA Free mobile app
Click to expand...
Click to collapse
No no, sorry my bad. Typing mistake here. I did gpt.bin. This time i did mistake, that's why got "error: cannot load 'fpt.bin'". Otherwise it's only "(bootloader) Variable not supported!" And status at end "OKAY" then next command. And i can't take risk for flashing few files only. Because my friend have no idea on this. It's all on me, what can be done. I need to flash full ROM to match up future OTA updates. It's somewhere wrong in copying files in ROM folder. I tried those commands, as per tutorial. So it didn't worked. :l
DarKrypton said:
No no, sorry my bad. Typing mistake here. I did gpt.bin. This time i did mistake, that's why got "error: cannot load 'fpt.bin'". Otherwise it's only "(bootloader) Variable not supported!" And status at end "OKAY" then next command. And i can't take risk for flashing few files only. Because my friend have no idea on this. It's all on me, what can be done. I need to flash full ROM to match up future OTA updates. It's somewhere wrong in copying files in ROM folder. I tried those commands, as per tutorial. So it didn't worked. :l
Click to expand...
Click to collapse
I don't exactly know whether you need an unlocked bootloader to flash via fastboot. But if you don't want to, then you can try factory reset from stock recovery or from the bootloader. There's plenty of guides all around for stock recovery.
Sent from my Moto X using XDA Free mobile app
athulele said:
I don't exactly know whether you need an unlocked bootloader to flash via fastboot. But if you don't want to, then you can try factory reset from stock recovery or from the bootloader. There's plenty of guides all around for stock recovery.
Sent from my Moto X using XDA Free mobile app
Click to expand...
Click to collapse
Naw, fastboot works with locked boot loader. It should be able to reflash on locked as long as the files are signed.
athulele, I think he said he tried factory reset...
Dark, your correct that you need to be in the same directory as that fastboot command (note there is also a mfastboot command. Motorola modified the stock android fastboot tool so it could flash larger partitions, at least from my understanding). If your not in the directory that executable is your OS will not be able to find it (unless you add it to your systems path, but if you don't know how or what that is easier to just make sure the EXE is in the folder your working out of)
The second time you tried to run it it looked like it worked perfectly right? but the correct command is
Code:
fastboot flash partition gpt.bin
Note the syntax is
fastboot [operation] [partition name] [file], so when you gave it the wrong file it correctly said it can't do it. Everything fine here.
again MAKE SURE your flashing the right files, double check your typing the command correctly (Copy and paste is good, but make sure you don't copy any extra characters at the begining or end of the line before you press enter to run the command)
About the worry over only flashing some paritions: You right to worry, you don't want to do this. HOWEVER, if you have the right files they should work. Go through that list of commands one by one. Figure out why any one command fails and get it to work before moving on... But if your flashing the same thing as is already on the phone, your not going to miss match partitions because your flashing the same version of each partition back over itself just trying to fix what ever one is messed up...
But yeah, make sure you got those files, run through those fastboot commands and post the output here. Copying too much of the console output is probably better then too little.
scryan said:
Naw, fastboot works with locked boot loader. It should be able to reflash on locked as long as the files are signed.
athulele, I think he said he tried factory reset...
Dark, your correct that you need to be in the same directory as that fastboot command (note there is also a mfastboot command. Motorola modified the stock android fastboot tool so it could flash larger partitions, at least from my understanding). If your not in the directory that executable is your OS will not be able to find it (unless you add it to your systems path, but if you don't know how or what that is easier to just make sure the EXE is in the folder your working out of)
The second time you tried to run it it looked like it worked perfectly right? but the correct command is
Code:
fastboot flash partition gpt.bin
Note the syntax is
fastboot [operation] [partition name] [file], so when you gave it the wrong file it correctly said it can't do it. Everything fine here.
again MAKE SURE your flashing the right files, double check your typing the command correctly (Copy and paste is good, but make sure you don't copy any extra characters at the begining or end of the line before you press enter to run the command)
About the worry over only flashing some paritions: You right to worry, you don't want to do this. HOWEVER, if you have the right files they should work. Go through that list of commands one by one. Figure out why any one command fails and get it to work before moving on... But if your flashing the same thing as is already on the phone, your not going to miss match partitions because your flashing the same version of each partition back over itself just trying to fix what ever one is messed up...
But yeah, make sure you got those files, run through those fastboot commands and post the output here. Copying too much of the console output is probably better then too little.
Click to expand...
Click to collapse
One thing i would like to ask mate. I am gonna start fresh installation. From laptop now. I noticed one thing, that on
Code:
"fastboot erase modemst1" and
"fastboot erase modemst2"
commands. On boot screen, it just keep showing
Code:
"erasing modemst1..."
for a long time. Does it take that long, or it gets "done" text in a sec? Let me know. I am starting now. Thanks.
Not sure how long it should take tbh. I would let it run, and give it a good while before worrying about it. Maybe open up some kind of system resource monitor on the side (on your computer) so you can see that things are still happening?
There are definitely times that these types of tools will look like its just sitting there though... It should go through eventually, give 10+ minutes before assuming it is not working.
scryan said:
Not sure how long it should take tbh. I would let it run, and give it a good while before worrying about it. Maybe open up some kind of system resource monitor on the side (on your computer) so you can see that things are still happening?
There are definitely times that these types of tools will look like its just sitting there though... It should go through eventually, give 10+ minutes before assuming it is not working.
Click to expand...
Click to collapse
Alright, i am on that command. I am gonna paste whole console commands. Because i think this time it won't work too. :l After every command it's showing
Code:
<bootloader> Variable not supported!
then "OKAY" like it went correct. Plus can you tell me what exactly my variant name is? I can't figure out, as for that OP, it was VZW. But for me, it must be different. I need it for second last command. Thanks.
EDIT : 25 minutes passed. Still same.
Hi guys,
I have been hacking around with this thing and reading the forums for days and I'm officially beaten.
I was on EVA-L09C43B140 - Optus Australia.
Attempted to flash to L09C636 using this guide.
As L09C636 isn't a popular choice, it took a lot of looking to eventually find the C636 oeminfo.
On top of that, when viewing the 'verlist.img' file, there were only two lines: EVA_C900B000 and EVA_Global.
Changed the files, and force flashed the UPDATE.APP file, and needless to say, it was unsuccessful and i got a cross-flash C900 version with broken themes.
So I decided to go back, and restored my oeminfo and custom.bin and flashed the original UPDATE.APP - and now I'm reading the correct version number, but still broken themes.
@fibblesan says here that you need to ensure you flash update_data_dt_default.app", "update_data_hw_eu.app" and "update_data_hw_normal.app" to fix the broken file system - but WHERE CAN I GET THESE FILES?! I have manged to get the ZIP files for "update_data_full_optus_au", and the rest that correspond to the firmware from the Warehouse post, but can't find any mention of these files as .APP files.
I'm sure I have all the files and tools I need, but I have no idea how to fix this and no one else seems to have experience with the C636/C43 firmware.
Any help would be very, very much appreciated. I just need my phone to work now.
Thanks in advance, and keep up the good work everyone.
halliday77 said:
Hi guys,
I have been hacking around with this thing and reading the forums for days and I'm officially beaten.
I was on EVA-L09C43B140 - Optus Australia.
Attempted to flash to L09C636 using this guide.
As L09C636 isn't a popular choice, it took a lot of looking to eventually find the C636 oeminfo.
On top of that, when viewing the 'verlist.img' file, there were only two lines: EVA_C900B000 and EVA_Global.
Changed the files, and force flashed the UPDATE.APP file, and needless to say, it was unsuccessful and i got a cross-flash C900 version with broken themes.
So I decided to go back, and restored my oeminfo and custom.bin and flashed the original UPDATE.APP - and now I'm reading the correct version number, but still broken themes.
@fibblesan says here that you need to ensure you flash update_data_dt_default.app", "update_data_hw_eu.app" and "update_data_hw_normal.app" to fix the broken file system - but WHERE CAN I GET THESE FILES?! I have manged to get the ZIP files for "update_data_full_optus_au", and the rest that correspond to the firmware from the Warehouse post, but can't find any mention of these files as .APP files.
I'm sure I have all the files and tools I need, but I have no idea how to fix this and no one else seems to have experience with the C636/C43 firmware.
Any help would be very, very much appreciated. I just need my phone to work now.
Thanks in advance, and keep up the good work everyone.
Click to expand...
Click to collapse
Try to delete data in recovery again. I fixed a P8 Lite doing so.
Broken /cust partition.
Marsou77 said:
Try to delete data in recovery again. I fixed a P8 Lite doing so.
Click to expand...
Click to collapse
Unfortunately no amount of wiping data/cache will do the trick.
From what I've read, it's a broken /cust partition.
I'm looking for more specific information to fix this, or avoid it breaking during flash, so I can finally flash the stock firmware I wanted, or return to original operator firmware.
Thanks.
FIXED Rollback
So, i solved this using TWRP to flash the two ZIP files that came with the Firmware.
'update_data_full_optus_au.zip'
and 'update_data_full_hw_normal.zip'
It was not obvious from the [WAREHOUSE] post that these files were required, or even obvious to download.
It might be because of amateur knowledge, but only closer inspection of the file list and manually entering the sub directory and extensions yielded these files. I might post some clearer instructions for the other noobs.
Now that I know I can restore, I'm going to attempt to try the debrand again another day.