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

cant flash clockworkmod recovery

hey tell me why i cant flash this recover. in the command said cannot load '/path/to/recovery-clockwork-3.0.0.5-passion.img'
whats wrong with me ? thanks

More details of what you are doing, help us help you.

baseballfanz said:
More details of what you are doing, help us help you.
Click to expand...
Click to collapse
yes 1st unlock the bootloader i follow on modacco forum
http://android.modaco.com/topic/299078-how-to-unlock-the-bootloader-on-your-nexus-one/
2nd i wanna flash the custom recovery , i follow on wiki nexus one .
what am i doing wrong ? or step that i take ?
thanks for reply brother

easiest way is to get ROM Manger from market and flash CWM that way.
I would stay away from CWM 3.0 since it's known to cause problems.

baseballfanz said:
easiest way is to get ROM Manger from market and flash CWM that way.
I would stay away from CWM 3.0 since it's known to cause problems.
Click to expand...
Click to collapse
yeah ithink like that ,but it needs root ,and im on stock rom 2.3.4 how to root it?
Sent from my Nexus One using Tapatalk

Oh, all this time I though you were already rooted.
Yeah you can't install custom recovery till you root first.
Read the WIKI on rooting

If you have unlocked your bootloader (I think that is what you said earlier?), then just flash recovery via fastboot like the wiki says...
What part are you struggling with? Are you getting any error messages?

baseballfanz said:
Oh, all this time I though you were already rooted.
Yeah you can't install custom recovery till you root first.
Read the WIKI on rooting
Click to expand...
Click to collapse
yes i see .but how to root 2.3.4 ?wiki just 2.3.3 downgrade?
Sent from my Nexus One using Tapatalk

danger-rat said:
If you have unlocked your bootloader (I think that is what you said earlier?), then just flash recovery via fastboot like the wiki says...
What part are you struggling with? Are you getting any error messages?
Click to expand...
Click to collapse
i got problem on command ,it said cant load recovery-clockwork.whats my problem?
Sent from my Nexus One using Tapatalk

When you boot up your phone, do you see a symbol of a open lock?
Sent from my Transformer TF101 using Tapatalk

baseballfanz said:
When you boot up your phone, do you see a symbol of a open lock?
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
yes i see under symbol X .what should i do?
Sent from my Nexus One using Tapatalk

I think you are just copying the command verbatim.
When it says /path/to/recovery.img it literally means wherever you have saved that file on your computer. In windows, it could very much look like
Code:
fastboot flash recovery "c:\user\john doe\Downloads\clockworkmod\recovery.img"
Keep in mind, if you are using windows, if the location has any spaces in it, it requires quotes around the whole thing.

bassmadrigal said:
I think you are just copying the command verbatim.
When it says /path/to/recovery.img it literally means wherever you have saved that file on your computer. In windows, it could very much look like
Code:
fastboot flash recovery "c:\user\john doe\Downloads\clockworkmod\recovery.img"
Keep in mind, if you are using windows, if the location has any spaces in it, it requires quotes around the whole thing.
Click to expand...
Click to collapse
it workss broo !! thanks youu i love you :* LOL

No problem. Now go enjoy your phone

bassmadrigal said:
No problem. Now go enjoy your phone
Click to expand...
Click to collapse
yes thanks you , actually i got a problem with stock rom 2.3.4 i was alwys rebooting , so i try to flash cwm for cm7 thanks .

I think I broke my O2X...help?

Hello! New member here so please excuse me if I'm posting to the wrong forum or anything like that.
Not to take long of your time, I can't get my phone to boot. It shows the 2 LG logos and won't proceed beyond that. So I need to know if there's a way to flash a ROM and a Recovery with it like that.
Thanks for the help.
Sent from either my Iconia-A500 or my LG-P990, depending.

May.Assem said:
Hello! New member here so please excuse me if I'm posting to the wrong forum or anything like that.
Not to take long of your time, I can't get my phone to boot. It shows the 2 LG logos and won't proceed beyond that. So I need to know if there's a way to flash a ROM and a Recovery with it like that.
Thanks for the help.
Sent from either my Iconia-A500 or my LG-P990, depending.
Click to expand...
Click to collapse
Can you access CWM? Try to pull out the battery, put it in, press power button + volume down at the same time. Wait til the LG logo appears and release it.

mrgian said:
Can you access CWM? Try to pull out the battery, put it in, press power button + volume down at the same time. Wait til the LG logo appears and release it.
Click to expand...
Click to collapse
No. It just freezes at the LG logo.
Sent from either my Iconia-A500 or my LG-P990, depending.

May.Assem said:
No. It just freezes at the LG logo.
Sent from either my Iconia-A500 or my LG-P990, depending.
Click to expand...
Click to collapse
I guess you need to flash the stock ROM by using SmartFlashTool. Its easy to use. There's a thread that has simple instructions.

mrgian said:
I guess you need to flash the stock ROM by using SmartFlashTool. Its easy to use. There's a thread that has simple instructions.
Click to expand...
Click to collapse
As weird as this is, I suddenly can start into recovery. Is SmartFlashTool still the way to go? I ask because I don't want to ruin things any further.
Thanks again for the help.
Sent from either my Iconia-A500 or my LG-P990, depending.

May.Assem said:
As weird as this is, I suddenly can start into recovery. Is SmartFlashTool still the way to go? I ask because I don't want to ruin things any further.
Thanks again for the help.
Sent from either my Iconia-A500 or my LG-P990, depending.
Click to expand...
Click to collapse
if u can go into recovery i would advise djangos last rom or temaseks or misjugedtwats

May.Assem said:
As weird as this is, I suddenly can start into recovery. Is SmartFlashTool still the way to go? I ask because I don't want to ruin things any further.
Thanks again for the help.
Sent from either my Iconia-A500 or my LG-P990, depending.
Click to expand...
Click to collapse
That's a good news then! What version of cmw u got? Do you have sdcard? I would suggest temasek cm7.2 build. 2 thumbs up!

mrgian said:
That's a good news then! What version of cmw u got? Do you have sdcard? I would suggest temasek cm7.2 build. 2 thumbs up!
Click to expand...
Click to collapse
Really?! That's great to know.
Recovery is v5.0.2.7
ETA: I flashed the ROM I had on before all that mess started and now my phone is working again. I'm not sure if things went awry because AOKP's last build was screwed or because I removed the SDcard before flashing in an attempt to force the phone to use the 5GB of internal memory that has been sitting useless since I got the device.
can't I flash the last owaine version I used?

May.Assem said:
Really?! That's great to know.
Recovery is v5.0.2.7
ETA: I flashed the ROM I had on before all that mess started and now my phone is working again. I'm not sure if things went awry because AOKP's last build was screwed or because I removed the SDcard before flashing in an attempt to force the phone to use the 5GB of internal memory that has been sitting useless since I got the device.
can't I flash the last owaine version I used?
Click to expand...
Click to collapse
Your phone working now? Try doing the 3 wipes (factory, cache partition, davlik [advance]).

mrgian said:
Your phone working now? Try doing the 3 wipes (factory, cache partition, davlik [advance]).
Click to expand...
Click to collapse
It is.
I wiped every thing before flashing the ROM and I have a complete copy of all the files I had on the SDcard saved on my PC. As soon as it finishes charging I'll move the TB files back to the SDcard and see if I can restore my apps. Unfortunately, I have to redo my system settings by hand. But I don't really mind.
Thanks a lot for your help. I really appreciate it.
Sent from either my Iconia-A500 or my LG-P990, depending.

May.Assem said:
It is.
I wiped every thing before flashing the ROM and I have a complete copy of all the files I had on the SDcard saved on my PC. As soon as it finishes charging I'll move the TB files back to the SDcard and see if I can restore my apps. Unfortunately, I have to redo my system settings by hand. But I don't really mind.
Thanks a lot for your help. I really appreciate it.
Sent from either my Iconia-A500 or my LG-P990, depending.
Click to expand...
Click to collapse
Your welcome. Glad I helped.

Nexus one with broken power button stuck in bootloop and no unlocked bootloader

Hello,
I think you are my last chance, I have this very specific problem with my Nexus One and can't find any thread on any forum that can help after hours of research:
It's rooted and I have CM7 but after a choc (I thing it's the cause) it reboots and now it's stuck in bootloop.
It happens to me once and i fixed it by flashing with fastboot.exe (i was very lucky this time) but it doesnt work anymore and i don't know why.
My power button is broken so I can't unlock bootloader, I have S-ON and I have read that it can be a problem to use fastboot to flash (I have an error message in the command prompt like this: FAILED: remote not allowed)
If i write "fastboot devices" my Nexus one is recognized so I don't understand why it doesnt work...
If you have any suggestions I take it with pleasure!
(sorry if my english is not perfect)
Thanks.

Gain s off.
Sent from my Energized Amaze 4G
Yes girls know about XDA
you can thank a girl on here

amandez said:
Gain s off.
Sent from my Energized Amaze 4G
Yes girls know about XDA
you can thank a girl on here
Click to expand...
Click to collapse
You go girl !!!!

Easy, just fast boot OEM unlock the device, although I don't know How you have been able to get cm7 and a custom recovery without a unlocked bootloader
Sent from my Nexus One using xda app-developers app

humzaahmed155 said:
Easy, just fast boot OEM unlock the device, although I don't know How you have been able to get cm7 and a custom recovery without a unlocked bootloader
Sent from my Nexus One using xda app-developers app
Click to expand...
Click to collapse
bro you dont need to unlock bootloader to flash custom recovery or cm7. jus rooting is enough...
http://forum.xda-developers.com/wiki/Nexus_One/Guides_&_Tutorials#ADB.2FFastboot.2FBootloader
Sent from my Nexus One using Tapatalk

n1newbie said:
bro you dont need to unlock bootloader to flash custom recovery or cm7. jus rooting is enough...
http://forum.xda-developers.com/wiki/Nexus_One/Guides_&_Tutorials#ADB.2FFastboot.2FBootloader
Sent from my Nexus One using Tapatalk
Click to expand...
Click to collapse
Oooooohhhh right, I thought you needed a unlocked BL for a custom recovery
Sent from my Nexus One using xda app-developers app

I have the same problem, I also tried all the command for Fastboot and got me no where.
My problem started when I install Darktemor(If I spelled it right) A2SDGUI and press something for Dalvik and Cache, my phone reboots and got stuck at bootloop forever. I searched the entire net for tutorials, and I tried almost everything and still no luck.
I always have this error code at Fastboot:
"FAILED <remote: not allowed>"
PLEASE! Someone help me, I want to fix this on my own. 'Cause it'll cost me a lot if I have someone fix it for me. Please, i'm begging. Help me. Huhuhu
I have MIUI Rom Installed on my phone, i'm not sure with the version of it. Sorry!!
Please help me guys! Super thank you in advance.

Thank you all
I had the same problem. i followed the instructions as posted in the link
http://forum.xda-developers.com/wiki/Nexus_One/Guides_&_Tutorials#ADB.2FFastboot.2FBootloader
my device is working again .. thank you all
But my last question, is there a way to restore my data ? like the SMS and the call log? and can I update again to CM7?
THANKS AGAIN FOR EVERYONE

hanitoo said:
I had the same problem. i followed the instructions as posted in the link
http://forum.xda-developers.com/wiki/Nexus_One/Guides_&_Tutorials#ADB.2FFastboot.2FBootloader
my device is working again .. thank you all
But my last question, is there a way to restore my data ? like the SMS and the call log? and can I update again to CM7?
THANKS AGAIN FOR EVERYONE
Click to expand...
Click to collapse
I'm still interested, what method of the link do you use? PASSIMG method?
So i'm stuck in this step: 3.Transfer the provided PASSIMG.ZIP file to the root of your SD card.
How do you go to the root of the sd card if the phone is in bootloop?
Thanks!

Ktt06 said:
I'm still interested, what method of the link do you use? PASSIMG method?
So i'm stuck in this step: 3.Transfer the provided PASSIMG.ZIP file to the root of your SD card.
How do you go to the root of the sd card if the phone is in bootloop?
Thanks!
Click to expand...
Click to collapse
By putting the µSD in another (working) phone and connect it to the computer, or by using a µSD adapter which also must be connected to the computer.

It finaly works, after many month i can finaly use my Nexus One... Now it's my new Desire S that have a problem :laugh:
Thanks for helps, this thread is finaly resolved!

tommert38 said:
By putting the µSD in another (working) phone and connect it to the computer, or by using a µSD adapter which also must be connected to the computer.
Click to expand...
Click to collapse
I have copied the PASSIMG.zip to the SD card, but how can I mount it in bootloader when the power button is broken?

[Q] No OS on phone

So, like an absolute idiot I wiped /system without a proper ROM zip on my device and I'm stuck with no OS on my device. I asked for Drive access to the KK factory image from Motorola, am I heading in the correct path for success? Does someone already have the KK image that they could provide for me? Any help is appreciated. Thanks in advance

Yeah your on the right path I did the same thing once

Once you get the factory image, you'll use fastboot to flash the files with the instructions Moto provides. You'll be fine.

Do u still have a custom recovery installed? You can put the to custom ROM zip on the flash drive or SD card and plug in an otg cable to the phone and you should be able to flash the ROM from there. Or you can do adb sideload from the recovery
Sent from my XT1097 using XDA Free mobile app

you can always download it from this devs website http://www.graffixnyc.com/motox.php

Android.is.better94 said:
Yeah your on the right path I did the same thing once
Click to expand...
Click to collapse
jonny6pak said:
Once you get the factory image, you'll use fastboot to flash the files with the instructions Moto provides. You'll be fine.
Click to expand...
Click to collapse
Thanks guys for the verification :good:
xFuGiToiDx said:
Do u still have a custom recovery installed? You can put the to custom ROM zip on the flash drive or SD card and plug in an otg cable to the phone and you should be able to flash the ROM from there. Or you can do adb sideload from the recovery
Sent from my XT1097 using XDA Free mobile app
Click to expand...
Click to collapse
ewalk4866 said:
you can always download it from this devs website http://www.graffixnyc.com/motox.php
Click to expand...
Click to collapse
Did something very similar to this. Used SolarTrans' guide as Motorola never sent me the factory image. Installed the OTA from the phone itself and then flashed the 5.1 OTA and I'm good to go. You guys are the kind who keep these forums great!

I have the same issue but my bootloader is locked and when I try to unlock it i get error "'Enable OEM Unlock' in developer options"

GreyArmour said:
Thanks guys for the verification :good:
Did something very similar to this. Used SolarTrans' guide as Motorola never sent me the factory image. Installed the OTA from the phone itself and then flashed the 5.1 OTA and I'm good to go. You guys are the kind who keep these forums great!
Click to expand...
Click to collapse
This is exactly what I did to fix the exact same issue. Essentially soft bricked my phone 17 hours after receiving it from Motorola [emoji27] but this got me back on my feet and I've been running lollipop on a rooted XT1095 with no issues for 6 months [emoji106]