Database Develop

[Help needed] Semi-bricked Milestone

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

How to get your BELL ATRIX HD onto At&t Jellybean (4.1.1) - Unlocked bootloader ONLY!

How to get your BELL ATRIX HD onto At&t Jellybean (4.1.1) - Unlocked bootloader ONLY!
I would like to start saying that I’m not responsible for whatever happens to your phone. Thanks to MATTLGROFF who figure out this way of flashing this jellybean leak on my phone.
Having that said THIS IS ONLY FOR BELL ATRIX HD USERS THAT HAVE THEIR BOOTLOADER UNLOCKED. Please read thru and ask any questions before attempting
OK here we go:
1. I assume you’re in stock BELL ICS ROM (77.55.18.MB886.BellMobility.en.CA) … it doesn’t matter if you’re rooted or not. Make sure you have the motorola drivers installed.
2. Enable debugging mode on your phone (settings>development options> enable USB debugging)
3. MAKE SURE YOU HAVE AN UNLOCKED BOOTLOADER. To do this open command prompt and type “adb reboot-bootloader” and check....
a. It should say: "Device is UNLOCKED. Status Code:1"
4. Now double check you’re unlocked.
5. Make sure you have a charged battery (more than 60%) and boot into fastboot. (if you're not already here)
6. Now download the stock ICS zip for At&t.
a. Unzip it
b. Make sure you have the fastboot files in the same folder/path as your fxz files.
c. Flash the boot.img from the at&t zip.
i. Hold the shift key down and right click on the unzipped folder. Now in the dropdown menu click “open command prompt here”
ii. Now type “fastboot flash boot boot.img”
d. Flash the system.img
i. "Fastboot flash system system.img”
ii. you should be in Stock att ICS rom now.
7. Now download the file for the stock at&t Jellybean zip. ( you will be able to go back to ICS --I have gone back to stock 4.0.4 Bell ROM-- bc you’re only flashing boot and system images)
8. Now start back at step 6 but with the jelly bean leak ---- Or you can try just going to settings and checking for updates! (haven't tried this yet - don't know if it will flash something we don't want it to UPDATE: I guess it doesn't work)
9. You should be on AT&T Jellybean now - and you probably(thanks soulja) lost root...
Fastboot link: https://www.dropbox.com/s/rhlcajoerowtpiw/fastboots.zip
Stock ICS link: http://forum.xda-developers.com/showthread.php?t=1853522
Stock JB link: https://www.dropbox.com/s/65ro5ddf5mhdc9f/7.7.1Q-144_MB886_MR1-22_SIGNED_CFC.xml.zip

reserved. IF you have any questions please ask!

gabo_e30 said:
3. MAKE SURE YOU HAVE AN UNLOCKED BOOTLOADER. To do this open command prompt and type “adb reboot-bootloader” and check....
a. It should say: "Device is UNLOCKED. Status Code:1"
4. Now double check you’re unlocked.
5. Make sure you have a charged battery (more than 60%) and boot into fastboot. (if you're not already here)
Click to expand...
Click to collapse
You might want to just clarify that "adb reboot-bootloader" puts the device into fastboot. Took me a few minutes to figure that out.
gabo_e30 said:
9. You should be on Jellybean now - and you prolly lost root...
Click to expand...
Click to collapse
...probably! not "prolly"!
OK, so I think I followed the directions properly, it appears SafeStrap is gone, and I now get new boot animations, a "thumping" Motorola logo and then an AT&T Rethink Possible. But it seems to be stuck after it plays that, with the AT&T logo and "Rethink Possible" message. Help!
UPDATE: After much flailing about, I got it into Recovery mode (could only get there by adb reboot recovery, the vol up/down + pwr only gets me a white texted menu which included "factory" but didn't do anything".) Will see if this works.
UPDATE 2: YES! After the factory reset, I let it boot up again. I was about to give up and try going back to ICS, but then it went past the Rethink Possible logo to a configure phone screen.
UPDATE 3: What... OK so it thinks it's an AT&T phone now, that's OK. It also shows it connected to 4G which it never has (always E, H or H++) But it's still on 4.0.4 ICS even though I did load the JB rom. But I just checked updates and it's got 4.1.1!!
UPDATE 4: Update (98.4.20.en.US) downloaded. Hitting install now...
UPDATE 5: CRAP. After reboot "The software update failed!" I might try reflashing the file from 7.7.1Q-144_MB886_MR1-22_SIGNED_CFC
UPDATE 6: No joy. :/ Any tried flashing Blur_Version.77.12.22.MB886.ATT.en.US.zip? After the above procedure, is my phone now "really" an AT&T phone?
UPDATE 7: I followed the thread about fixing failed update http://forum.xda-developers.com/showthread.php?t=2050416, and then got the OTA update. THIS TIME IT WORKS!!! I did lose root though. Oh well. I tried motofail2go again, but I couldn't get the "bug report" vibrate to happen.

noob problem with adb
3. MAKE SURE YOU HAVE AN UNLOCKED BOOTLOADER. To do this open command prompt and type “adb reboot-bootloader” and check....
a. It should say: "Device is UNLOCKED. Status Code:1"
sorry where in PC or in motorola atrix ? need i another app ? thanks in advance
i just unlocked root with Motofail2Go

w0hnzimmer said:
3. MAKE SURE YOU HAVE AN UNLOCKED BOOTLOADER. To do this open command prompt and type “adb reboot-bootloader” and check....
a. It should say: "Device is UNLOCKED. Status Code:1"
sorry where in PC or in motorola atrix ? need i another app ? thanks in advance
Click to expand...
Click to collapse
First step is actually to get Motorola drivers installed on your PC, as well as adb tools. Sorry I don't have a link handy. Then from PC do the "adb reboot-bootloader".

Can this be done with at&t and why not ?
Seems like you can go jb > ics easily.

souljaboy said:
Can this be done with at&t and why not ?
Seems like you can go jb > ics easily.
Click to expand...
Click to collapse
Step #4 and the title to the thread.
Sent from my MB886 using xda premium

capran said:
First step is actually to get Motorola drivers installed on your PC, as well as adb tools. Sorry I don't have a link handy. Then from PC do the "adb reboot-bootloader".
Click to expand...
Click to collapse
thanks, now i got "Device is LOCKED. Status Code: 0"
any chance to unlock ?
regards

w0hnzimmer said:
thanks, now i got "Device is LOCKED. Status Code: 0"
any chance to unlock ?
regards
Click to expand...
Click to collapse
The title of this threads says "Unlocked bootloader ONLY!" You haven't unlocked it yet. Please go read up on how to do that first.
1. Root. http://forum.xda-developers.com/showthread.php?t=1940594
2. Can't seem to find the bootloader bit...

ATGAdmin said:
Step #4 and the title to the thread.
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
i know...
what unlocked changes is, you can replace the kernel... but the RSDLite can replace it too, i dont quite get it.

capran said:
You might want to just clarify that "adb reboot-bootloader" puts the device into fastboot. Took me a few minutes to figure that out.
...probably! not "prolly"!
OK, so I think I followed the directions properly, it appears SafeStrap is gone, and I now get new boot animations, a "thumping" Motorola logo and then an AT&T Rethink Possible. But it seems to be stuck after it plays that, with the AT&T logo and "Rethink Possible" message. Help!
Click to expand...
Click to collapse
YOu need to do a factory reset! Sorry forgot to include that in the steps! My Bad!
UPDATE: After much flailing about, I got it into Recovery mode (could only get there by adb reboot recovery, the vol up/down + pwr only gets me a white texted menu which included "factory" but didn't do anything".) Will see if this works.
UPDATE 2: YES! After the factory reset, I let it boot up again. I was about to give up and try going back to ICS, but then it went past the Rethink Possible logo to a configure phone screen.
Click to expand...
Click to collapse
YESSS!!! you figured it out!
UPDATE 3: What... OK so it thinks it's an AT&T phone now, that's OK. It also shows it connected to 4G which it never has (always E, H or H++) But it's still on 4.0.4 ICS even though I did load the JB rom. But I just checked updates and it's got 4.1.1!!
Click to expand...
Click to collapse
Yeah 4G is the same as H+, that's just how At&t symbolizes it
UPDATE 4: Update (98.4.20.en.US) downloaded. Hitting install now...
UPDATE 5: CRAP. After reboot "The software update failed!" I might try reflashing the file from 7.7.1Q-144_MB886_MR1-22_SIGNED_CFC
Click to expand...
Click to collapse
I guess it won't work huh?... we were lucky if it did!
UPDATE 6: No joy. :/ Any tried flashing Blur_Version.77.12.22.MB886.ATT.en.US.zip? After the above procedure, is my phone now "really" an AT&T phone?
Click to expand...
Click to collapse
No it's not really an at&t phone... you can flash back the Bell 4.0.4 ROM (I just did it). Remember it will ONLY WORK IF YOU HAVE AN UNLOCKED BOOTLOADER!
UPDATE 7: I followed the thread about fixing failed update http://forum.xda-developers.com/showthread.php?t=2050416, and then got the OTA update. THIS TIME IT WORKS!!! I did lose root though. Oh well. I tried motofail2go again, but I couldn't get the "bug report" vibrate to happen.
Click to expand...
Click to collapse
Cool you found a solution...(?) But it should work with the above Jellybean file. Gonna try it out again myself!

w0hnzimmer said:
3. MAKE SURE YOU HAVE AN UNLOCKED BOOTLOADER. To do this open command prompt and type “adb reboot-bootloader” and check....
a. It should say: "Device is UNLOCKED. Status Code:1"
sorry where in PC or in motorola atrix ? need i another app ? thanks in advance
i just unlocked root with Motofail2Go
Click to expand...
Click to collapse
Ok. SO install the moto drivers first (just google them -Motocast)
Now the fastboot files and put them in the same folder or path of the system and boot.img
Now connect your phone and make sure its in debugging mode
Open command prompt (cmd) in the folder you have the files you want to install. (do this by holding shift and right click on that folder)
Now type adb reboot bootloader IN CMD. You phone should reboot into fastboot! :victory:

capran said:
The title of this threads says "Unlocked bootloader ONLY!" You haven't unlocked it yet. Please go read up on how to do that first.
1. Root. http://forum.xda-developers.com/showthread.php?t=1940594
2. Can't seem to find the bootloader bit...
Click to expand...
Click to collapse
Capran you can't install it following this procedure. It won't work or you will brick.
This si only for unlocked bootloader Atrix HDs. There's only a few of them out there (they all seem to be BELL models, but not all Bell models) I think its the ones that shipped with system version: 77.55.17.MB886.BellMobility.en.CA. TheBootloader version is 10.96 i believe... and the locked one is 10.97 I think...

souljaboy said:
i know...
what unlocked changes is, you can replace the kernel... but the RSDLite can replace it too, i dont quite get it.
Click to expand...
Click to collapse
From what I understand is that RSDlite changes it but after and Only with kernels and files that r signed (by Moto)

gabo_e30 said:
Capran you can't install it following this procedure. It won't work or you will brick.
This si only for unlocked bootloader Atrix HDs. There's only a few of them out there (they all seem to be BELL models, but not all Bell models) I think its the ones that shipped with system version: 77.55.17.MB886.BellMobility.en.CA. TheBootloader version is 10.96 i believe... and the locked one is 10.97 I think...
Click to expand...
Click to collapse
How about the 77.55.18.MB886.BellMobility.en.CA can we flash it to our unlocked Atrix hd? I saw that there's an update to JB 4.1.2. on this version. Thanks
Sent from my MB886 using xda premium

I have an unlocked Bell Atrix HD. It was running 77.55.17 and I tried this method of flashing the AT&T software using fastboot and it didn't work. I could flash the boot.img, but when I went to flash the system.img.ext4 it would tell me that I had exceeded the download buffer. So at this point I had flashed the boot.img already and the phone wouldn't boot. I actually couldn't get any system.img files to flash from fastboot, even the Bell one, always the same exceeded the download buffer error. So I downloaded RSD lite and flashed the 77.55.18 Bell firmware to it via RSD lite and I was back in business again. At this point I just said to heck with it with fastboot and then flashed the stock ICS AT&T firmware via RSD lite only having used the modified XML file that is suggested to use. This worked perfectly fine as well. I was then able to root with motofail and use voodoo to backup my root. Then I just let it do the JB update OTA and that worked perfectly fine as well and then restored my root through voodoo and verified I still had root. Everything looks fine. The funny thing is I'm selling this phone, I have a Galaxy Note II now, but I was worried if I sold it with the Bell firmware nobody would want it since it was still ICS. Should be a bonus to someone that its unlocked, and rooted already hopefully.

ryuben2k said:
How about the 77.55.18.MB886.BellMobility.en.CA can we flash it to our unlocked Atrix hd? I saw that there's an update to JB 4.1.2. on this version. Thanks
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
I used RSDlite (the latest one) to flash the 77.55.18 version on my phone.. now its the one im currently running. SO yeah you can flash it! ( i still don't have an update though) Link for teh FXZ file is in the OP (same place where the ICS at&t ROM is)

BHUGHESVA said:
I have an unlocked Bell Atrix HD. It was running 77.55.17 and I tried this method of flashing the AT&T software using fastboot and it didn't work. I could flash the boot.img, but when I went to flash the system.img.ext4 it would tell me that I had exceeded the download buffer. So at this point I had flashed the boot.img already and the phone wouldn't boot. I actually couldn't get any system.img files to flash from fastboot, even the Bell one, always the same exceeded the download buffer error. So I downloaded RSD lite and flashed the 77.55.18 Bell firmware to it via RSD lite and I was back in business again. At this point I just said to heck with it with fastboot and then flashed the stock ICS AT&T firmware via RSD lite only having used the modified XML file that is suggested to use. This worked perfectly fine as well. I was then able to root with motofail and use voodoo to backup my root. Then I just let it do the JB update OTA and that worked perfectly fine as well and then restored my root through voodoo and verified I still had root. Everything looks fine. The funny thing is I'm selling this phone, I have a Galaxy Note II now, but I was worried if I sold it with the Bell firmware nobody would want it since it was still ICS. Should be a bonus to someone that its unlocked, and rooted already hopefully.
Click to expand...
Click to collapse
Glad you worked it out! The first time I did it was from the 77.55.17 version, then I updated to at&t ICS the to JEllybean and now back to Bell ICS (77.55.18) Not sure what happened, but still glad you worked it out!
That's the great thing about the forums we can all work together in solving issues!

gabo_e30 said:
Glad you worked it out! The first time I did it was from the 77.55.17 version, then I updated to at&t ICS the to JEllybean and now back to Bell ICS (77.55.18) Not sure what happened, but still glad you worked it out!
That's the great thing about the forums we can all work together in solving issues!
Click to expand...
Click to collapse
Indeed, so glad I didn't brick it, lol. Maybe it was something wrong with the fastboot executables I used, I used the same ones I had downloaded a couple weeks ago to flash the HTC One V's that I got my kids for Christmas and not the ones linked to in the original post. It worked fine for for the One V's, not for the Atrix HD for some reason. Oh well, I just like tinkering with this stuff.

gabo_e30 said:
I used RSDlite (the latest one) to flash the 77.55.18 version on my phone.. now its the one im currently running. SO yeah you can flash it! ( i still don't have an update though) Link for teh FXZ file is in the OP (same place where the ICS at&t ROM is)
Click to expand...
Click to collapse
Thanks. Here's the link that i saw from motorola that there's an update for 77.55.18. and if someone from here can prove that they already upgrade to 4.1.2.
Thanks
https://motorola-global-en-usa.custhelp.com/app/answers/detail/a_id/92147
Sent from my MB886 using xda premium

[Q] How can I unroot and revert to stock recovery without wiping all data?

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

[Q] rogers 4.4 update?

any one using the rogers and know when will the update for 4.4?

yghrv said:
any one using the rogers and know when will the update for 4.4?
Click to expand...
Click to collapse
I gave up weeks ago waiting for the rogers(robbers) update, flashed the tmobile sbf 4.4 firmware on my unlocked boot loader moto. The way I see it we're probably last to receive the update, US done , now South Americian carriers, so assume sometime in January
Sent on my Moto X

flashallthetime said:
I gave up weeks ago waiting for the rogers(robbers) update, flashed the tmobile sbf 4.4 firmware on my unlocked boot loader moto. The way I see it we're probably last to receive the update, US done , now South Americian carriers, so assume sometime in January
Sent on my Moto X
Click to expand...
Click to collapse
disappoint about that, the first Moto X was saled with Rogers and then turns out to be the last one to update....

Also running the dev edition/retail firmware - it is totally the way to go. Forget about Rogers. I suspect Motorola already compiled 4.4 for them and they are sitting on it like they did the camera update. The only feature the Rogers firmware will likely offer is LTE on/off in the menu. I can't think of anything else it has going for it.
Running the retail version also gets rid of the carrier name in the upper left which is just silly to have anyway.

Should I unlock my bootloader? What does the warranty cover anyways?

alu0506 said:
Should I unlock my bootloader? What does the warranty cover anyways?
Click to expand...
Click to collapse
Well if the hardware was to fail such as the headphone jack breaking, ram going bad, speaker crapping out etc it would be covered under warranty. Once you request the bootloader unlock key that is gone. I figured since my phone was solid for more then a month and being I bought it used anyway I didn't have much to lose by unlocking the bootloader. For me it was the right move, used phones are getting cheaper on craigslist everyday if it does break and has to be replaced.

Yeah, I just checked. It doesn't cover physical damages so I'm gonna unlock the boot loader and maybe flash the Dev version.
Sent from my XT1058 using Tapatalk

alu0506 said:
Yeah, I just checked. It doesn't cover physical damages so I'm gonna unlock the boot loader and maybe flash the Dev version.
Sent from my XT1058 using Tapatalk
Click to expand...
Click to collapse
Sounds good - any problems or questions let me know!

Steve-x said:
Sounds good - any problems or questions let me know!
Click to expand...
Click to collapse
Got it unlocked! What should I flash.... hmmm....

alu0506 said:
Got it unlocked! What should I flash.... hmmm....
Click to expand...
Click to collapse
Try this first:
http://sbf.droid-developers.org/download.php?device=0&file=2

Works well on my Rogers phone, if you decide to flash one of the kitkat customs roms, you need the kitkat modems
Sent on my Moto X Running Beanstalk 4.4.2

Steve-x said:
Try this first:
http://sbf.droid-developers.org/download.php?device=0&file=2
Click to expand...
Click to collapse
What is it exactly? Is it pre-rooted or should I flash supersu?

alu0506 said:
What is it exactly? Is it pre-rooted or should I flash supersu?
Click to expand...
Click to collapse
It is the retail/dev edition 4.4 kitkat rom. It is 100% stock as released by Motorola, you can root it after installing.

alu0506 said:
What is it exactly? Is it pre-rooted or should I flash supersu?
Click to expand...
Click to collapse
Its not a ROM but the stock firmware, it flashes the boot loader, stock recovery, modems and system files after it boots you can then flash twrp recovery for kitkat and flash supersu
Sent on my Moto X Running Beanstalk 4.4.2

Oh no.... I made have made a little oops.
I flashed everything and then selected normal powerup.
Booted to the warning screen, vibrated and got stuck...
[EDIT 1] GOT IT TO BOOT TO BOOTLOADER WOOT FLASHING AGAIN
[EDIT 2] Reflashed again... is it supposed to be at the warning screen for a long time after first reboot?

If you're in the bootloader I'd flash it again, may have been a failure in the data transfer.

Steve-x said:
If you're in the bootloader I'd flash it again, may have been a failure in the data transfer.
Click to expand...
Click to collapse
I redownloaded it and reflashed and IT BOOTED! YAY! THANK YOU!

process
What's the exact process to flash this file. Do I need custom recovery first? If you could list the steps for me that would be awesome.

gthompson75 said:
What's the exact process to flash this file. Do I need custom recovery first? If you could list the steps for me that would be awesome.
Click to expand...
Click to collapse
Well this is what I did:
Step 1. Download the latest drivers and adb/fastboot
If you already have the android adk installed, go to https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481 and download and install the latest drivers. Otherwise try this http://forum.xda-developers.com/showthread.php?t=2588979. I have never used it before but it looks like it should install both adb/fastboot and their corresponding drivers.
Step 2. Download mfastboot.exe
Go to https://drive.google.com/file/d/0B-SutxHydqfNczVMVXNtRVI4ZW8/edit?usp=sharing and download the file. This is motorola fastboot. You use it in place of the fastboot that came with the android sdk. For some reason, the fastboot that comes with the android SDK seems to not work when flashing some things. Download the file and save it somewhere.
Step 3. Download the Retail/Dev 4.4 rom
Thanks Steve-x for showing me this!
http://sbf.droid-developers.org/download.php?device=0&file=2
Download this file and unzip it.
Step 4. Unlock the bootloader
Go to https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a/action/auth and follow the instructions to have a unlock code mailed to you. Remember, this will void your warranty AND WILL WIPE YOUR DATA. REMEMBER TO DO A BACKUP! I DIDN'T AND IT WAS A REALLY BAD MISTAKE.
Step 5. Flash the Retail/Dev rom
Remember that mfastboot.exe file that you downloaded earlier? Well it’s time to put it to good use. Copy (or move) the file to the directory where the rest of the Retail/Dev 4.4 rom files are located. (The zip that you extracted earlier, the one with the “system.img” in it?)
Now that you've done that, open “TMO_RETAIL_XT1053_4.4-13.11.1Q2.X-69-3_MR2_CFC.bat” with your favorite plain text editor. (Use notepad if you have no favorite) We have to make it so that instead of using the standard android fastboot.exe to flash the files, it uses the mfastboot.exe. So, just edit the first line, “SET fastboot=fastboot.exe”, to “SET fastboot=mfastboot.exe”. Save and close it up.
Now, put your Moto X into bootloader mode if it isn't already. Power it down and then press the power and volume down buttons simultaneously until it powers on. Connect the usb cable to the computer, and wait for the pc to recognize everything. Now double-click on the “TMO_RETAIL_XT1053_4.4-13.11.1Q2.X-69-3_MR2_CFC.bat” and it will start flashing.
After it is complete, turn the phone on by selecting “Normal Powerup” on the device. To navigate around the bootloader, use the volume down arrow key to select the option and the volume up key to execute it. If everything went correctly, your Moto X show powerup and boot into Android 4.4!
I think thats everything. If you need help please do ask!
---------- Post added at 05:17 PM ---------- Previous post was at 05:14 PM ----------
gthompson75 said:
What's the exact process to flash this file. Do I need custom recovery first? If you could list the steps for me that would be awesome.
Click to expand...
Click to collapse
Oh right, if you want a custom recovery and root, this thread explains the process nicely http://forum.xda-developers.com/showthread.php?t=2603358

Thanks,
alu0506 said:
Well this is what I did:
Step 1. Download the latest drivers and adb/fastboot
If you already have the android adk installed, go to https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481 and download and install the latest drivers. Otherwise try this http://forum.xda-developers.com/showthread.php?t=2588979. I have never used it before but it looks like it should install both adb/fastboot and their corresponding drivers.
Step 2. Download mfastboot.exe
Go to https://drive.google.com/file/d/0B-SutxHydqfNczVMVXNtRVI4ZW8/edit?usp=sharing and download the file. This is motorola fastboot. You use it in place of the fastboot that came with the android sdk. For some reason, the fastboot that comes with the android SDK seems to not work when flashing some things. Download the file and save it somewhere.
Step 3. Download the Retail/Dev 4.4 rom
Thanks Steve-x for showing me this!
http://sbf.droid-developers.org/download.php?device=0&file=2
Download this file and unzip it.
Step 4. Unlock the bootloader
Go to https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a/action/auth and follow the instructions to have a unlock code mailed to you. Remember, this will void your warranty AND WILL WIPE YOUR DATA. REMEMBER TO DO A BACKUP! I DIDN'T AND IT WAS A REALLY BAD MISTAKE.
Step 5. Flash the Retail/Dev rom
Remember that mfastboot.exe file that you downloaded earlier? Well it’s time to put it to good use. Copy (or move) the file to the directory where the rest of the Retail/Dev 4.4 rom files are located. (The zip that you extracted earlier, the one with the “system.img” in it?)
Now that you've done that, open “TMO_RETAIL_XT1053_4.4-13.11.1Q2.X-69-3_MR2_CFC.bat” with your favorite plain text editor. (Use notepad if you have no favorite) We have to make it so that instead of using the standard android fastboot.exe to flash the files, it uses the mfastboot.exe. So, just edit the first line, “SET fastboot=fastboot.exe”, to “SET fastboot=mfastboot.exe”. Save and close it up.
Now, put your Moto X into bootloader mode if it isn't already. Power it down and then press the power and volume down buttons simultaneously until it powers on. Connect the usb cable to the computer, and wait for the pc to recognize everything. Now double-click on the “TMO_RETAIL_XT1053_4.4-13.11.1Q2.X-69-3_MR2_CFC.bat” and it will start flashing.
After it is complete, turn the phone on by selecting “Normal Powerup” on the device. To navigate around the bootloader, use the volume down arrow key to select the option and the volume up key to execute it. If everything went correctly, your Moto X show powerup and boot into Android 4.4!
I think thats everything. If you need help please do ask!
---------- Post added at 05:17 PM ---------- Previous post was at 05:14 PM ----------
Oh right, if you want a custom recovery and root, this thread explains the process nicely http://forum.xda-developers.com/showthread.php?t=2603358
Click to expand...
Click to collapse
Thank you for the detailed info. When updates come out will we get them rogers or tmob/retail

Request: Guide convert XT1097/92 into XT1095

Hi all!
Sorry for bothering you. I'm a complete noob and I've bought my XT1097 just 4 days ago. I just want to request to some of the hard core guys here if you can do a noob friendly guide describing the process to transform a XT1097 or XT1092 into a the Pure Edition XT1095. I know there is a tiny explanation in one post, but as I told you, I'm a noob and for what I've read if you don't do the right thing you loose signal.
I just love so much this phone and is brand new, and I don't want to break it
Thanks so much in advance :fingers-crossed:

You have to find it yourself. If you're not able to find guides that already exists then you really shouldn't try to flash your device.

Judge584 said:
You have to find it yourself. If you're not able to find guides that already exists then you really shouldn't try to flash your device.
Click to expand...
Click to collapse
No man, is not that I can not find it. There is none yet...the one that is around there is not clear and "noob friendly", that is why I'm requesting a "noob friendly" one...
Anyways, sorry of my request bothered you, I'm just asking politely for help, that is all.
Cheers man

You don't bother me but all information is already here, it's not that hard. All you have to do is learn, and if you have never flashed a device before it should take no more than a day to figure out how it works.

I will happily try and help you out -- everyone is new at one point or another. Give me about a day or so to try and compile the resources I personally used when I did mine!

justblais said:
I will happily try and help you out -- everyone is new at one point or another. Give me about a day or so to try and compile the resources I personally used when I did mine!
Click to expand...
Click to collapse
Thanks a lot man!!! No rush, take your time. Thanks again!

you could use the multitool
flashing the stock PE xt1095 from there worked for me
however you need to be prepared in case you brick your device by any chance
try downloading android emulator and play around with it first (just a suggestion)

nicromant said:
you could use the multitool
flashing the stock PE xt1095 from there worked for me
however you need to be prepared in case you brick your device by any chance
try downloading android emulator and play around with it first (just a suggestion)
Click to expand...
Click to collapse
Thanks man! you had the XT1097 before converting it with the multi tool?

yes it was a retail latam xt1097 with the tool you can convert it to xt1095 and flash the OTA you just need to be cautious with the modem section of it otherwise you will need to reflash again using fastboot and the std retail image with adequate version for your device

I'm pretty sure this post should do the trick, however make sure you use your correct modem as the one posted there is for the XT1092.
benjamin.j.goodwin said:
I didn't get the OTA through my phone, just flashed it.
I did have a modem issue so lost all signal but I fixed it. If you can live without it for a while then you should be fine.
Here is what I did.
0. Download Multi-Tool, XT1092 Modem, Lollipop OTA
1. Enable USB debugging.
2. Use the Multi-Tool to go back to KK stock, full wipe option. *this will most likely **** up your modem, don't worry*
3. Reboot with the stock, enable USB debugging again.
4. Move the OTA zip to your SD card on your phone.
4. Use a CMD window in the Multi-Tool directory to 'adb reboot recovery' if you use Mac './adb reboot recovery'
5. Once in recovery press volume up for three seconds, then press the power button along with it. A menu should appear.
6. Navigate to 'apply update from zip' or whatever it says, not the ADB option.
7. It should flash. Once it's done, reboot. You won't have signal still but don't worry. All in good time.
8. Factory reset after the first boot, don't sign in or anything.
9. Once you have booted again after the reset enable USB debugging again.
10. Reboot to bootloader so 'adb reboot bootloader' or if Mac './adb reboot bootloader'
11. Let's get our signal back.
12. Unzip the contents of the XT1092 modem zip. You will need to type the following:
Code:
'mfastboot flash modem NON-HLOS.bin'
'mfastboot erase modemst1'
'mfastboot erase modemst2'
'mfastboot flash fsg fsg.mbn'
13. Then 'fastboot reboot'
NB: To do points 12 and 13, you will be best to copy the relevant files from the Multi-Tool into the XT1092 modem unzipped directory.
You should now have Lollipop. Root if you want after. It's essentially official too. I did amend my build.prop after as it does state XT1095 as the device which is wrong.
Click to expand...
Click to collapse

Same steps can be applyed to a XT1097? Just have to extract the correct modem firmware for my device?
Thanks!
Edit: Sorry, just skimmed through the text and didn't saw this was mentioned already.
Another question though, doing this procedure needs an unlocked bootloader? Even if not, this qualifies as a awaranty void?
Thanks any way for the gruide!

danielcbit said:
Same steps can be applyed to a XT1097? Just have to extract the correct modem firmware for my device?
Thanks!
Edit: Sorry, just skimmed through the text and didn't saw this was mentioned already.
Another question though, doing this procedure needs an unlocked bootloader? Even if not, this qualifies as a awaranty void?
Thanks any way for the gruide!
Click to expand...
Click to collapse
you do need an unlocked bootloader as far as I understand... I wanted to try it but backing up my modem files first... at least that required an unlocked bootloader, so I decided not to try it yet...

use TWRP it is better to upgrade to preserve baseband and modem cfg, however you can also use full fastboot flashing and reinstall your modem settings, i used twrp and no major issues so far...