Hi all.
I have to send my phone to RMA because of bad screen and or video chip. Can anyone help me to get the original rom of it?
Thanks.
FedericoUY said:
Hi all.
I have to send my phone to RMA because of bad screen and or video chip. Can anyone help me to get the original rom of it?
Thanks.
Click to expand...
Click to collapse
original ? you can download stock firmwares on developers.google.com/android and below look for nexus factory images.
then follow the fastboot method which is very easy.
Hehe, thank you for your fast answer. I already did that, and I doubt about some codes near the links:
.....
6.0.1 (MOB30O)
6.0.1 (MMB30R)
6.0.1 (MOB30W)
.....
I really don't know what are those codes.
FedericoUY said:
Hehe, thank you for your fast answer. I already did that, and I doubt about some codes near the links:
.....
6.0.1 (MOB30O)
6.0.1 (MMB30R)
6.0.1 (MOB30W)
.....
I really don't know what are those codes.
Click to expand...
Click to collapse
6.0.1 (MOB30W) is the latest release, that's the one you will want to download and install.
I again. I get an error when i execute the flash-all.bat from windows. Is there a way to flash all via twrp without using adb? I uncompressed image there, flashed ok bootloader, radio, but system always get an error...
Please help. Thanks.
Execute the commands manually. flash-all.bat is notorious for being flaky. However, why are we stressing here? This is a developer's device and nobody is going to care that you are rooted or that you are running a custom ROM. In short, I have yet to hear of anyone being refused warranty service because of an unlocked bootloader and custom ROM.
FedericoUY said:
I again. I get an error when i execute the flash-all.bat from windows. Is there a way to flash all via twrp without using adb? I uncompressed image there, flashed ok bootloader, radio, but system always get an error...
Please help. Thanks.
Click to expand...
Click to collapse
Download FASTBOOT and ADB ZIP , Install Drivers from 15 seconds ADB installer and then move all the extracted factory images to the fastboot containing folder and double click flash-all.bat and it'll do the job.
Links:
1. FASTBOOT & ADB..
2. 15 Sec ADB Installer[contains fastboot too].
3.Latest fastboot Images [MOB30W][6.0.1]
I ended up doing it via manual fastboot. My screen phone after being splitting screen for a long time, ended up getting a completly blurry screen. Could not find anyone that happened this same issue. Will have to send the phone to warranty. Thanks
Related
Hi all,
prior to any comment, yes, i know there are already posts on this issue, however looking through them didn't help at all unfortunately.
I have a Moto Milestone, origin is Israel.
somewhere along the way i've updated the bootloader to 90.78 and since then - the phone is stuck in the notorious loop and cannot restart the OS.
Tried already to reflash the phone without luck using RSD Lite (downloaded the SBF through http://and-developers.com/sbf:milestone - the 'official' Cellcom IL SBF that was there...)
anyway - i can still access the bootloader which tells me the phone is not fully bricked, however i can't seem to find any proper SBF so it'll reflash itself back to an operative state.
One major problem here - the phone won't get into recovery mode (i've tried all the combinations i know and that have worked before)
i've also read about wiping the cache and user data however - as far as i know, this can only be done by entering the recovery mode, right?
one last resort i've tried - trying to split the SBF and reconstructing it - still no joy.
does anyone here have any advice or solution o this issue? what kind of SBF do i need? how to manually reconstruct the SBF with proper files? etc.
Thanks in advance,
Tomer
Have you tried loooking into fastboot?
Sometimes a phone wont respond to to adb commands and the recovery is corrupted, but you can still flash partitions using fastboot. I "saved" a Moto dext in this fashion once. Cant remember the exact commands, but it was similar to the adb flash commands. I reflashed the recovery partition and then used recovery to flash a ROM in update.zip format. For some reason RSD lite was failing on this phone.
Just something you may want to look into if you are desperate about saving your MS.
Sent from my Milestone using XDA App
Caz666 said:
Have you tried loooking into fastboot?
Sometimes a phone wont respond to to adb commands and the recovery is corrupted, but you can still flash partitions using fastboot. I "saved" a Moto dext in this fashion once. Cant remember the exact commands, but it was similar to the adb flash commands. I reflashed the recovery partition and then used recovery to flash a ROM in update.zip format. For some reason RSD lite was failing on this phone.
Just something you may want to look into if you are desperate about saving your MS.
Sent from my Milestone using XDA App
Click to expand...
Click to collapse
Hi Caz666,
well, thought this might actually work, but had no luck.
when i try to flash my phone it does nothing other than showing me 'downloading boot.img' and thats it.
is there anything else to do in order to save my phone? i really like it
I'm also willing to donate through PayPal to anyone who can describe any working method or that can point me to any valid working process...
thanks again.
barvaz_t said:
Hi Caz666,
well, thought this might actually work, but had no luck.
when i try to flash my phone it does nothing other than showing me 'downloading boot.img' and thats it.
is there anything else to do in order to save my phone? i really like it
I'm also willing to donate through PayPal to anyone who can describe any working method or that can point me to any valid working process...
thanks again.
Click to expand...
Click to collapse
are you sure your drivers for the phone are installed properly? what RSD lite version are you using? What system? windows 32 or 64 bits?
vladstercr said:
are you sure your drivers for the phone are installed properly? what RSD lite version are you using? What system? windows 32 or 64 bits?
Click to expand...
Click to collapse
I'm quite sure they're installed properly as i managed to upgrade my bootloader version using the RSDlite.
my system is 32 bits and the drivers are the ones i installed throught the Motorola website. I've first used RSDlite 4.6 but after reading a bit I understood there are some differences between versions hence upgraded to 4.9.
barvaz_t said:
I'm quite sure they're installed properly as i managed to upgrade my bootloader version using the RSDlite.
my system is 32 bits and the drivers are the ones i installed throught the Motorola website. I've first used RSDlite 4.6 but after reading a bit I understood there are some differences between versions hence upgraded to 4.9.
Click to expand...
Click to collapse
Try the 90.78ch bootloader from http://and-developers.com/sbf:milestone ...
"XT702 variant of the 90.78 bootloader (notes from 90.78 apply here too).
It's reported to work on the A853 too. "
You've got nothing to loose on trying this. Let me know!
vladstercr said:
Try the 90.78ch bootloader from http://and-developers.com/sbf:milestone ...
"XT702 variant of the 90.78 bootloader (notes from 90.78 apply here too).
It's reported to work on the A853 too. "
You've got nothing to loose on trying this. Let me know!
Click to expand...
Click to collapse
*** [update]
I'm now on 90.78ch and see no difference whatsoever.
I've now started investigating how to re-compile an older SBF file so it'll contain the new RAMDL
(I want to flash the Brazilian version however it contains only 90.74 RAMDL)
I've compiled a new file, however the checksum is incorrect.
How it is possible to recompile this properly?
Already tried the website, the mirror there is no leading to the bootloader itself but to a wiki site.
i've tried searching almost anywhere i know, but this bootloader is non available to download.
if there's another mirror site such as rapidshare or megaupload - i'd be happy to be pointed towards it..
Hi barvaz_t!
barvaz_t said:
...
somewhere along the way i've updated the bootloader to 90.78 and since then - the phone is stuck in the notorious loop and cannot restart the OS.
...
Click to expand...
Click to collapse
Why did you upgrade the bootloader
barvaz_t said:
...
i've also read about wiping the cache and user data however - as far as i know, this can only be done by entering the recovery mode, right?
...
Click to expand...
Click to collapse
Right, is it possible to boot into recovery on your device by holding 'X' button?
barvaz_t said:
*** [update]
I'm now on 90.78ch and see no difference whatsoever.
I've now started investigating how to re-compile an older SBF file so it'll contain the new RAMDL
(I want to flash the Brazilian version however it contains only 90.74 RAMDL)
I've compiled a new file, however the checksum is incorrect.
How it is possible to recompile this properly?
Click to expand...
Click to collapse
You locked yourself out by upgrading the bootloader to the latest one.
Neither downgrade of bootloader would be possible, nor flashing older firmware SBF's.
Apart from that the milestone uses signature check on certain parts of the firmware. I really doubt that it's possible to tweak/recompile a complete SBF.
Something worth to try, is to flash vulnerable recovery SBF from within bootloader mode using RSDlite.
Here's the link to gitorious: http://gitorious.org/droid/openrecovery/blobs/master/zips/SHOLS/vulnerable_recovery.sbf
If the link does not work for you, there are also some mirrors of this file floating around. Just search!
I guess this should work, because the recovery SBF is using RAMLDR 90.78 (do know about the sign check during flash, but i guess checksum should be O.K.).
With vulnerable recovery properly installed, you might then use OpenRecovery to check your system and restore to some working state.
Good luck!
scholbert
scholbert said:
Hi barvaz_t!
Why did you upgrade the bootloader
Right, is it possible to boot into recovery on your device by holding 'X' button?
You locked yourself out by upgrading the bootloader to the latest one.
Neither downgrade of bootloader would be possible, nor flashing older firmware SBF's.
Apart from that the milestone uses signature check on certain parts of the firmware. I really doubt that it's possible to tweak/recompile a complete SBF.
Something worth to try, is to flash vulnerable recovery SBF from within bootloader mode using RSDlite.
Here's the link to gitorious: http://gitorious.org/droid/openrecovery/blobs/master/zips/SHOLS/vulnerable_recovery.sbf
If the link does not work for you, there are also some mirrors of this file floating around. Just search!
I guess this should work, because the recovery SBF is using RAMLDR 90.78 (do know about the sign check during flash, but i guess checksum should be O.K.).
With vulnerable recovery properly installed, you might then use OpenRecovery to check your system and restore to some working state.
Good luck!
scholbert
Click to expand...
Click to collapse
Thanks Scholbert for the detailed answer.
the link you gave directs to an image the RSDlite cannot flash (=error validating image).
If your interntion was that I'm supposed to flash the vulnerable recovery only, than bad news - It's already 'installed' on my device (and it shows no error whatsoever during this installation..)
Well, thanks again for trying to help, I think I'm officially out of suggestions or options here unless anyone can give further advice...
barvaz_t said:
...
If your interntion was that I'm supposed to flash the vulnerable recovery only, than bad news - It's already 'installed' on my device (and it shows no error whatsoever during this installation..)
...
Click to expand...
Click to collapse
So can you still enter recovery?
Regards,
scholbert
No, never did (since the upgrade)
If I had access to the recovery i would have at least managed to install OpenRecovery or something and manage to reflash the device
barvaz_t said:
Hi Caz666,
well, thought this might actually work, but had no luck.
when i try to flash my phone it does nothing other than showing me 'downloading boot.img' and thats it.
is there anything else to do in order to save my phone? i really like it
I'm also willing to donate through PayPal to anyone who can describe any working method or that can point me to any valid working process...
thanks again.
Click to expand...
Click to collapse
Did you try to fastboot flash only the boot.img? What about recovery? I seem to remember flashing a recovery.img on the dext...but this was last year. I may be wrong but i believe i flashed only a recovery image and then was able to access the recovery (which would allow all sorts of additional goodies).
I find it strange that fastboot reports only downloading. I seem to remember some error messages and timeouts?
Sent from my Milestone using XDA App
Caz666 said:
Did you try to fastboot flash only the boot.img? What about recovery? I seem to remember flashing a recovery.img on the dext...but this was last year. I may be wrong but i believe i flashed only a recovery image and then was able to access the recovery (which would allow all sorts of additional goodies).
I find it strange that fastboot reports only downloading. I seem to remember some error messages and timeouts?
Sent from my Milestone using XDA App
Click to expand...
Click to collapse
Nope.
trying to flash the recovery / boot images only results in the message 'downloading...' and nothing (waited for like 3 hours..)
when I terminate the action by Ctrl+C and then trying again - the message is instantly 'FAILED..' along with specification that the action of sending the command has failed.
I'm literaly out of ideas, don't know what to do..
Sent from my Milestone using XDA App
I am starting to think that there is something wrong with your device (like broken hardware).
In all my experimenting with rsd/fastboot, i did not once get a "hang". I would get checksum/signature errors, size errors, etc...but i always got some type of error code or status.
This is on 3 different Mot devices that run Android.
Sorry
Sent from my Milestone using XDA App
Caz666 said:
I am starting to think that there is something wrong with your device (like broken hardware).
In all my experimenting with rsd/fastboot, i did not once get a "hang". I would get checksum/signature errors, size errors, etc...but i always got some type of error code or status.
This is on 3 different Mot devices that run Android.
Sorry
Sent from my Milestone using XDA App
Click to expand...
Click to collapse
The device was working fine before upgrading the bootloader, so it seems that this is not a hardware issue.
Either way - guess i'll be taking it to a lab and let them figure this out..
idea
is the milestone n droid from usa same sbf file used if so i have the right sbf file i found i had couple times i had to reinstall to stock if u want to try it i can email it it work for me saved me from bricks its rooted phone just fyi
streetracer89101 said:
is the milestone n droid from usa same sbf file used if so i have the right sbf file i found i had couple times i had to reinstall to stock if u want to try it i can email it it work for me saved me from bricks its rooted phone just fyi
Click to expand...
Click to collapse
@streetracer89101 - no, as far as i know Droid and Milestone use different firmware so it won't help unfortunately. Not that it would matter if I did flash my device - it's not like I can use it anyway..
Thanks again for trying to help out
Tomer
90.78ch bootloader
Hello, I really need the bootloader 90.78ch maybe you can me it someone give Many Thanks
300zxtt said:
Hello, I really need the bootloader 90.78ch maybe you can me it someone give Many Thanks
Click to expand...
Click to collapse
Attached. Enjoy
"FIRMWARE TEAM" Presents:
AT&T ICS 4.0.4
7.7.1Q-144_MB886_MR1-22_SIGNED_CFC.xml.zip
Upload by Skrilax_CZ, Download Coming Soon in http://sbf.droid-developers.org/dinara/list.php
Upload by daywalker04, Download Coming Soon in http://forum.xda-developers.com/showthread.php?t=1853522
Live: http://sbf.droid-developers.org/dinara/list.php
Just got my first Motorola with this phone, but think I borked it by messing with the radio bands. How does one flash these .xml or .sbf files to restore to original stock?
failed flashing process..unknown fastboot comand
I'm grabbing this for my friend, he can't get the update because he needs Wi-Fi and the phone won't connect to our University's Wi-Fi network. This won't break OTA for him though will it?
It's just as same as if you have applied OTA.
what is the update process?
Skrilax_CZ said:
It's just as same as if you have applied OTA.
Click to expand...
Click to collapse
so what exactly is the update procedure?
Here's what my phone is showing me.
system version: 77.1.7.MB886.ATT.en.US
android version: 4.0.3
Will this update change anything with the bootloader or anything like that?
aerohp said:
so what exactly is the update procedure?
Here's what my phone is showing me.
system version: 77.1.7.MB886.ATT.en.US
android version: 4.0.3
Will this update change anything with the bootloader or anything like that?
Click to expand...
Click to collapse
If you got 4.0.3 we need a copy of your OS before you upgrade. 4.0.3 has vulnerabilities that we need to get root. Sorry I don't know the procedure, but I am sure some dev will be more than willing to tell you.
Skrilax_CZ said:
It's just as same as if you have applied OTA.
Click to expand...
Click to collapse
popfan said:
If you got 4.0.3 we need a copy of your OS before you upgrade. 4.0.3 has vulnerabilities that we need to get root. Sorry I don't know the procedure, but I am sure some dev will be more than willing to tell you.
Click to expand...
Click to collapse
are there any specifics to the vulnerabilities?
anyways, if someone lets me know how make a copy of the OS, i'd be more than willing to do so.
aerohp said:
are there any specifics to the vulnerabilities?
anyways, if someone lets me know how make a copy of the OS, i'd be more than willing to do so.
Click to expand...
Click to collapse
Just saw this and need to let you know not to do any soft of fastboot or updating without backing up your files. The worry is you flash a retail bootloader and possibly cannot go back if you use these.
mattlgroff said:
Just saw this and need to let you know not to do any soft of fastboot or updating without backing up your files. The worry is you flash a retail bootloader and possibly cannot go back if you use these.
Click to expand...
Click to collapse
yeah, that's why i'm holding out... battery life sucks on the 4.0.3. it barely gets me 8-9 hours with moderate use. i've noticed there are huge drops in the battery level every now and then. i guess i'll just deal with it until we get the root thing sorted out.
is there a way to just mount the system.img.ext4? i've tried ext2explore and i've tried to mount it with Linux Reader. thanks
mrvirginia said:
is there a way to just mount the system.img.ext4? i've tried ext2explore and i've tried to mount it with Linux Reader. thanks
Click to expand...
Click to collapse
i'm wondering the same thing...i'm not flashing this on my phone but a friend of mine has a retail 4.0.4 and can't get the OTA. i;m not really sure how to flash this. i was hoping for it to be an sbf but thats not the case. can someone point the way please?
aerohp said:
i'm wondering the same thing...i'm not flashing this on my phone but a friend of mine has a retail 4.0.4 and can't get the OTA. i;m not really sure how to flash this. i was hoping for it to be an sbf but thats not the case. can someone point the way please?
Click to expand...
Click to collapse
just use fastboot oem fb_mode_set
then fastboot flash .......
cmvienneau said:
just use fastboot oem fb_mode_set
then fastboot flash .......
Click to expand...
Click to collapse
Flash what exactly? I've been trying this for the past hour and rsdlite won't work, moto-fastboot doesn't give any hints. I've tried MR1-22 and FFW-14.
darknessrise1234 said:
Flash what exactly? I've been trying this for the past hour and rsdlite won't work, moto-fastboot doesn't give any hints. I've tried MR1-22 and FFW-14.
Click to expand...
Click to collapse
Edit the XML file within the ZIP. Remove the two lines that contain "GETVAR". then flash the zip
mandrsn1 said:
Edit the XML file within the ZIP. Remove the two lines that contain "GETVAR". then flash the zip
Click to expand...
Click to collapse
After removing that, the modem lines and the oem_mode_set one... It still fails on the system.img.ext4.
EDIT: Out of thoughts. Stuck with a fastboot loop. Won't even allow me to turn it off.
I installed beats installer and my phone will not reboot. Any Ideas?
tried the same thing, now stuck at the boot animation. I have tried factory reset as well as downloading the firmware and trying to update from the sd card in recovery. No luck. It is now a brick unless someone can help...
Av8tor86 said:
tried the same thing, now stuck at the boot animation. I have tried factory reset as well as downloading the firmware and trying to update from the sd card in recovery. No luck. It is now a brick unless someone can help...
Click to expand...
Click to collapse
This sucks, I have no idea what could have happened. I really hope someone can help!!
I'm currently rooted and am running only Xposed Mods with a few root apps. How can I unroot my phone and get the stock recovery back onto my Moto X so that I can take OTA's again without wiping all of my data? What files do I need to download/flash and how do I do it? I've searched around, but it just got me even more confused.
bd1212 said:
I'm currently rooted and am running only Xposed Mods with a few root apps. How can I unroot my phone and get the stock recovery back onto my Moto X so that I can take OTA's again without wiping all of my data? What files do I need to download/flash and how do I do it? I've searched around, but it just got me even more confused.
Click to expand...
Click to collapse
Someone correct me if I'm wrong, but I believe that flashing the stock system will remove all the changes you've made with root/xposed modules, and flashing the stock recovery should essentially get rid of root (I think).
I don't know precisely where to get all the files, but if you find them around, you can push them using ADB.
If you're like me and are okay with losing everything on the phone, go ahead and use RSDLite (it requires ADB). It's easy-ish to use, and there's even a video tutorial that covers everything after installation of all the files.
You need to use fastboot to push system.img and recovery.img from the version of the OS you're currently running. See here for a list of OS images:
http://sbf.droid-developers.org/ghost_rcica/list.php
See this thread for a link to a fastboot.exe that'll work:
http://forum.xda-developers.com/showthread.php?t=2527287
See this thread for a quick overview and link to more detailed info:
http://forum.xda-developers.com/showthread.php?t=2525495&page=4
jonnythan said:
You need to use fastboot to push system.img and recovery.img from the version of the OS you're currently running. See here for a list of OS images:
http://sbf.droid-developers.org/ghost_rcica/list.php
See this thread for a link to a fastboot.exe that'll work:
http://forum.xda-developers.com/showthread.php?t=2527287
See this thread for a quick overview and link to more detailed info:
http://forum.xda-developers.com/showthread.php?t=2525495&page=4
Click to expand...
Click to collapse
Thanks for the info and links. I'm currently downloading the OS that I'm currently running (VZW OTA update in my case), but I have one question: How do I use fastboot? When I double click that .exe nothing happens.
bd1212 said:
Thanks for the info and links. I'm currently downloading the OS that I'm currently running (VZW OTA update in my case), but I have one question: How do I use fastboot? When I double click that .exe nothing happens.
Click to expand...
Click to collapse
You need to install the Android SDK and the platform tools, then boot your phone into fastboot mode. You need to run a command line to flash the IMGs. It's explained in the links.
meant2live218 said:
Someone correct me if I'm wrong, but I believe that flashing the stock system will remove all the changes you've made with root/xposed modules, and flashing the stock recovery should essentially get rid of root (I think).
I don't know precisely where to get all the files, but if you find them around, you can push them using ADB.
If you're like me and are okay with losing everything on the phone, go ahead and use RSDLite (it requires ADB). It's easy-ish to use, and there's even a video tutorial that covers everything after installation of all the files.
Click to expand...
Click to collapse
I was under the impression that we cannot do a factory reset or we won't get the soak test OTA pushed to our phones. That's what the soak test post said atleast. Something along the lines of "DO NOT FACTORY RESET or you will not receive the OTA"... don't want to quote it directly since I'm under an NDA, but it was something like that. Did I misunderstand? If I use the Moto X toolkit or RSDLite to revert back to stock is that different than a factory reset?
jonnythan said:
You need to install the Android SDK and the platform tools, then boot your phone into fastboot mode. You need to run a command line to flash the IMGs. It's explained in the links.
Click to expand...
Click to collapse
I've got the Android SDK install and ADB is setup. I'm pretty familiar with ADB. I moved the motorola fastboot.exe into platform-tools and I know how to put the phone into fastboot mode. What I don't understand is what I need to do once I've got the system.img file and the recovery.img file. I'm still reading all of the links so I might not have gotten to the part where it explains what to do, so forgive me for that.
bd1212 said:
I've got the Android SDK install and ADB is setup. I'm pretty familiar with ADB. I moved the motorola fastboot.exe into platform-tools and I know how to put the phone into fastboot mode. What I don't understand is what I need to do once I've got the system.img file and the recovery.img file.
Click to expand...
Click to collapse
Right from my third link:
Next, you need to put the phone into "fastboot mode" as described above, also make sure usb debugging is enabled in the developer menu settings. Then download the FW for your phone found (follow what i said in regards to the other persons post below), then unzip that, put the system and recovery image in the same directory that your fastboot and adb is in, then run these commands from the cmd prompt
fastboot flash system system.img
fastboot flash recovery recovery.img
then your done, you can type
fastboot reboot
Click to expand...
Click to collapse
jonnythan said:
Right from my third link:
Click to expand...
Click to collapse
Yep, just got to that part lol. Having some trouble downloading the VZW file. My current download just stopped with a network error and the website that is hosting the files keeps saying service unavailable and to contact the website administrator. Weird. I'm blaming it on my college's ****ty wireless network.
Edit: Yup, for some reason the wifi at the school decided it need me to input my credentials to re-login for the 6th time today to verify who I am and allow me internet access.
Edit 2: The things I'd do to have a stable connection... Once again, the download failed halfway through because the damn connection at this college sucks. This is infuriating.
jonnythan said:
Right from my third link:
Click to expand...
Click to collapse
Is there anyway you (or someone else) could upload the VZW OTA update file to Google Drive or Dropbox for me? This download is going way to slow to the point where I can't even finish it before my connection craps out. Or can you (or someone else) just upload the system.img and recovery.img files for me?
bd1212 said:
Is there anyway you (or someone else) could upload the VZW OTA update file to Google Drive or Dropbox for me? This download is going way to slow to the point where I can't even finish it before my connection craps out. Or can you (or someone else) just upload the system.img and recovery.img files for me?
Click to expand...
Click to collapse
Uploading now, but it'll take a bit. Big file.
jonnythan said:
Uploading now, but it'll take a bit. Big file.
Click to expand...
Click to collapse
Thanks man. You don't even know how much I appreciate this.
Which one of the two is the camera update for vzw?
Where do you get stock recovery?
EDIT: Sorry, Nevermind. I probably extract it from the zip.
Sent from my XT1060 using xda app-developers app
This scripted tool (Windows Only!) I have written and packaged will allow you to return back to the stock OTA path from ANY single ROM (stock or custom) you might be running or even if your device is soft bricked at the moment (without even requiring RSD Lite).
Download the zip file: http://www.androidfilehost.com/?fid=23487008491965516
Unpack the zip file to your PC
Install Motorola Drivers First!
Then run the TOOL file and follow the instructions to guide you
I have also included some screenshots and an Emergency Fix in case you are stuck in Fastboot for whatever reason and need to restore back to stock and then continue the tool (automatically continues from the fix).
WARNING THIS WILL COMPLETELY WIPE ALL DATA INCLUDING YOUR INTERNAL STORAGE!
MAKE SURE TO BACKUP EVERYTHING YOU NEED BEFORE USING THE TOOL OR THE EMERGENCY FIX!
The emergency utility was able to get me out of my soft brick. Thank you sir!
xt925
Does it works on xt925 ?
Thanks.
morcego.surf said:
Does it works on xt925 ?
Thanks.
Click to expand...
Click to collapse
It does, the emergency will flash an XT926 firmware, might have to change internal files I guess. It did got me out of a flash failure then could get back into fastboot and then flash my Telcel firmware for my XT925.
Is this for XT925?! Is this the first thing i have to do to get Kit Kat official leaked last week?
andreluigo said:
Is this for XT925?! Is this the first thing i have to do to get Kit Kat official leaked last week?
Click to expand...
Click to collapse
i have seen some lazy people, but i must say you take the cake.
this thread was 4 hole post long before you posted. 2 of which, asked and answered your exact first question.
no self respecting person is going to help you, when you cant even read a 4 post long thread before asking a question in it.
open1your1eyes0 said:
This scripted tool (Windows Only!) I have written and packaged will allow you to return back to the stock OTA path from ANY single ROM (stock or custom) you might be running or even if your device is soft bricked at the moment (without even requiring RSD Lite).
Download the zip file: http://www.androidfilehost.com/?fid=23487008491965516
Unpack the zip file to your PC
Install Motorola Drivers First!
Then run the TOOL file and follow the instructions to guide you
I have also included some screenshots and an Emergency Fix in case you are stuck in Fastboot for whatever reason and need to restore back to stock and then continue the tool (automatically continues from the fix).
WARNING THIS WILL COMPLETELY WIPE ALL DATA INCLUDING YOUR INTERNAL STORAGE!
MAKE SURE TO BACKUP EVERYTHING YOU NEED BEFORE USING THE TOOL OR THE EMERGENCY FIX!
Click to expand...
Click to collapse
Just wanted to thank you for creating this tool, man. The Emergency Fix really saved my skin from a soft brick.
Pretty sure this utility has bricked my phone. I was on 4.1.2 and was rooted and tried using the utility to return to stock. After the utility completed it gets stuck on the AP fastboot menu and it says Boot Failure. Any ideas to fix it?
Nice to know it.
open1your1eyes0 said:
This scripted tool (Windows Only!) I have written and packaged will allow you to return back to the stock OTA path from ANY single ROM (stock or custom) you might be running or even if your device is soft bricked at the moment (without even requiring RSD Lite).
Download the zip file: http://www.androidfilehost.com/?fid=23487008491965516
Unpack the zip file to your PC
Install Motorola Drivers First!
Then run the TOOL file and follow the instructions to guide you
I have also included some screenshots and an Emergency Fix in case you are stuck in Fastboot for whatever reason and need to restore back to stock and then continue the tool (automatically continues from the fix).
WARNING THIS WILL COMPLETELY WIPE ALL DATA INCLUDING YOUR INTERNAL STORAGE!
MAKE SURE TO BACKUP EVERYTHING YOU NEED BEFORE USING THE TOOL OR THE EMERGENCY FIX!
Click to expand...
Click to collapse
Hello,
Could you please write in big red letters in the beginning of your post : "ONLY FOR XT926, Do not use it for XT925" ?
Thank you
yoderz said:
Pretty sure this utility has bricked my phone. I was on 4.1.2 and was rooted and tried using the utility to return to stock. After the utility completed it gets stuck on the AP fastboot menu and it says Boot Failure. Any ideas to fix it?
Click to expand...
Click to collapse
Were you able to fix?
for OP, I have similar situation as yoderz on verizon, I get "Software Update Failed" and no OTA. Stuck on 9.18.XT926.Verizon.en.US
150kwh said:
Were you able to fix?
for OP, I have similar situation as yoderz on verizon, I get "Software Update Failed" and no OTA. Stuck on 9.18.XT926.Verizon.en.US
Click to expand...
Click to collapse
Took me over 6 hours to fix it. I finally found this post and it worked. I had to sign up for their forum, but it was worth it.
http://www.droidrzr.com/index.php/topic/45494-fxz-442-1834610/
Good luck!
yoderz said:
Took me over 6 hours to fix it. I finally found this post and it worked. I had to sign up for their forum, but it was worth it.
http://www.droidrzr.com/index.php/topic/45494-fxz-442-1834610/
Good luck!
Click to expand...
Click to collapse
Thanks, worked for me now. Super happy to luck out on timing so I could get unlocked & root, wish I had seen this earlier.
..Now, if only their forum would validate me. (Maybe a week timeout??)
yoderz said:
Took me over 6 hours to fix it. I finally found this post and it worked. I had to sign up for their forum, but it was worth it.
http://www.droidrzr.com/index.php/topic/45494-fxz-442-1834610/
Good luck!
Click to expand...
Click to collapse
so you have XT925 and this link helped you fix the install, and you're now on the official KK? does LTE and GSM work for you?
I need the stock recovery image (from 23.16.3.victara_retca.retca.en.CA) so I can flash the 6.0 update since it won't work with TWRP.
Any help? Google isn't providing me with much.
Does it have to be from the Canadian variant (not sure if the recovery images are different between variants)?
Tried looking here for the correct zip, which should contain the recovery image?
ellisbodds said:
Does it have to be from the Canadian variant (not sure if the recovery images are different between variants)?
Tried looking here for the correct zip, which should contain the recovery image?
Click to expand...
Click to collapse
I have no clue. I doubt it would have to be the retCA version. I'm sure everything besides radio and system will be the same.
This is from the latest RETCA XT1097 5.1 firmware:
VICTARA_RETCA_XT1097_5.1_LPE23.32-48.3_cid14_CFC.xml.zip
ellisbodds said:
Does it have to be from the Canadian variant (not sure if the recovery images are different between variants)?
Tried looking here for the correct zip, which should contain the recovery image?
Click to expand...
Click to collapse
Gus.Ottawa said:
This is from the latest RETCA XT1097 5.1 firmware:
VICTARA_RETCA_XT1097_5.1_LPE23.32-48.3_cid14_CFC.xml.zip
Click to expand...
Click to collapse
Thank you both! I'll play around with these files and make it work
DonDizzurp said:
Thank you both! I'll play around with these files and make it work
Click to expand...
Click to collapse
Any update on whether this worked for you? I'm in the same boat
jullyfush said:
Any update on whether this worked for you? I'm in the same boat
Click to expand...
Click to collapse
Worked perfectly.
My process
- Flash stock 5.1 using fastboot (Steps can be found on Motorola's site or somewhere on XDA)
- Install Marshmallow OTA
- Flash cracked boot.img for Marshmallow. This step is needed in order for TWRP to stick and for you to root without getting stuck on the warning screen. (I'll find the link for you if you can't. It's somewhere on XDA.)
- Flash TWRP
- Create backup so I don't have to go through this process next time haha
DonDizzurp said:
Worked perfectly.
My process
- Flash stock 5.1 using fastboot (Steps can be found on Motorola's site or somewhere on XDA)
- Install Marshmallow OTA
- Flash cracked boot.img for Marshmallow. This step is needed in order for TWRP to stick and for you to root without getting stuck on the warning screen. (I'll find the link for you if you can't. It's somewhere on XDA.)
- Flash TWRP
- Create backup so I don't have to go through this process next time haha
Click to expand...
Click to collapse
Awesome! Thanks for the tip. I got as far as the 6.0 OTA (RETCA), and am now trying to get root back again. Where did you find the cracked boot.img?
Cheers!
jullyfush said:
Awesome! Thanks for the tip. I got as far as the 6.0 OTA (RETCA), and am now trying to get root back again. Where did you find the cracked boot.img?
Cheers!
Click to expand...
Click to collapse
Grab it from here
http://forum.xda-developers.com/moto-x-2014/development/root-root-moto-x-2014-android-t3249105
DonDizzurp said:
Grab it from here
http://forum.xda-developers.com/moto-x-2014/development/root-root-moto-x-2014-android-t3249105
Click to expand...
Click to collapse
Something odd has happened since upgrading to 6.0.
'adb devices' still sees my phone, but 'fastboot devices' no longer sees anything, and making a desktop back-up with adb now creates a file containing 0 bytes.
Everything else seems fine. Are there some new permissions I need to give before this will work?
Thanks again.
Edit: I managed to get fastboot working, however now I've run into a new problem.
To confirm, when you say flash the cracked boot.img for Marshmallow, I should execute 'fastboot flash boot boot.img' for the cracked boot.img?
I'm getting the error: mismatched partition size (boot)
I can still enter TWRP with fastboot, but it's not permanent without the cracked boot.img
Am I missing a step?
Edit #2: Finally got TWRP to stick another way and have root now. Thanks for everything!