Database Users

[Q] 0.0.1.XT907-continuous.Verizon.en.US and BL Status 1

Hi guys,
Have this RAZR M that i bought used, it has a firmware on it which I couldn't find anywhere. System Version says
"0.0.1.XT907-continuous.Verizon.en.US"
Also the back of the phone says XT905, while the firmware is of XT907
What's up with this firmware?
Also Fastboot shows bootloader unlocked Status 1.
Tried to unlock bootloader again (to get status 3) with motopocalypse but failed. I have already rooted it with motofail2go, and tried to flash twrp2.4 via fastboot (showed success). Now whenever i try to go into recovery it reboots and goes to normal boot byitself :S?
Do I need to have bootloader unlocked Status 3? How do i get that?
Also going through all this to be able to flash a XT905 Retail JB ROM, please help

I'm thinking it's an electrify for sprint or was at least. I'm not sure how compatible the current roms are with it.
Sent from my XT907 using Tapatalk 2

Can't be an electrify, looks exactly like international razr m, and works on gsm, i've tested it working on gsm.
What about the bootloader status 1 and the recovery problem?

droid.dessert said:
Hi guys,
Have this RAZR M that i bought used, it has a firmware on it which I couldn't find anywhere. System Version says
"0.0.1.XT907-continuous.Verizon.en.US"
Also the back of the phone says XT905, while the firmware is of XT907
What's up with this firmware?
Click to expand...
Click to collapse
No idea... It looks like an official Verizon one... Maybe a prerelease? What android version is it?
droid.dessert said:
Also Fastboot shows bootloader unlocked Status 1.
Tried to unlock bootloader again (to get status 3) with motopocalypse but failed. I have already rooted it with motofail2go, and tried to flash twrp2.4 via fastboot (showed success). Now whenever i try to go into recovery it reboots and goes to normal boot byitself :S?
Click to expand...
Click to collapse
If you're unlocked, there's no need to run motopocalypse. Sounds like you either flashed a bad recovery or your recovery flash failed.
droid.dessert said:
Do I need to have bootloader unlocked Status 3? How do i get that?
Click to expand...
Click to collapse
Nope - shouldn't need to. If it didn't complain on flashing recovery you're unlocked
droid.dessert said:
Also going through all this to be able to flash a XT905 Retail JB ROM, please help
Click to expand...
Click to collapse
You could try an xt-907 ROM since that's what the phone thinks it is
Sent from my XT907 on CM10.1 using Tapatalk 4 beta

sloosecannon said:
No idea... It looks like an official Verizon one... Maybe a prerelease? What android version is it?
If you're unlocked, there's no need to run motopocalypse. Sounds like you either flashed a bad recovery or your recovery flash failed.
Nope - shouldn't need to. If it didn't complain on flashing recovery you're unlocked
You could try an xt-907 ROM since that's what the phone thinks it is
Sent from my XT907 on CM10.1 using Tapatalk 4 beta
Click to expand...
Click to collapse
It's 4.0.4
Flashed both cwm and twrp recovery through the razr m utility v1.2 and through fastboot. Always shows completed and rebooting to recovery, fails to boot to recovery and reboots to normal.
How do I flash the rom now, as i can't go into recovery?
rsd lite v6.14 just shows phone connected, when clicked on it shows all details as N/A, safe to flash with it?

droid.dessert said:
It's 4.0.4
Flashed both cwm and twrp recovery through the razr m utility v1.2 and through fastboot. Always shows completed and rebooting to recovery, fails to boot to recovery and reboots to normal.
How do I flash the rom now, as i can't go into recovery?
rsd lite v6.14 just shows phone connected, when clicked on it shows all details as N/A, safe to flash with it?
Click to expand...
Click to collapse
Can't really say if it's safe or not, but when my phone is in Fastboot, RSDLite says N/A for all the parts of my phone as well, but flashes fine
Just one man's experience.

Coronado is dead said:
Can't really say if it's safe or not, but when my phone is in Fastboot, RSDLite says N/A for all the parts of my phone as well, but flashes fine
Just one man's experience.
Click to expand...
Click to collapse
If i do it via rsd lite, will it flash the recovery and modem and kernel aswell? or just recovery?
btw i have removed the var, getvar and oem lines from the xml file (read better success that way)
and i'll be trying to flash the aussie retail xt905 retail rom, as the the back of the phone says xt905

droid.dessert said:
If i do it via rsd lite, will it flash the recovery and modem and kernel aswell? or just recovery?
btw i have removed the var, getvar and oem lines from the xml file (read better success that way)
and i'll be trying to flash the aussie retail xt905 retail rom, as the the back of the phone says xt905
Click to expand...
Click to collapse
Well, when I flash it flashes the radio and system files, and recovery. Last time I did it all my data was still there oddly.
But yes, all 3 of those will be flashed.

Coronado is dead said:
Well, when I flash it flashes the radio and system files, and recovery. Last time I did it all my data was still there oddly.
But yes, all 3 of those will be flashed.
Click to expand...
Click to collapse
RSD doesn't remove userdata. It just flashes system
Sent from my Nexus 7 using Tapatalk HD

sloosecannon said:
RSD doesn't remove userdata. It just flashes system
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
@Coronado is dead
flashed the xt905 au retail 4.1.2 via rsd lite and it wasn't picking up my sim anymore, so i thought maybe that rom was sim locked.
and i know verizon software isn't sim locked, flashed the team firmware verizon 4.1.2 through rsd and it isn't picking up the sim too.
the sim works fine on my mb886!
help? how can i disable sim lock? do i need to flash modem of some other version?
btw i am NOT using a US GSM SIM. Which don't work. I am using an international sim which worked fine before flashing.

droid.dessert said:
@Coronado is dead
flashed the xt905 au retail 4.1.2 via rsd lite and it wasn't picking up my sim anymore, so i thought maybe that rom was sim locked.
and i know verizon software isn't sim locked, flashed the team firmware verizon 4.1.2 through rsd and it isn't picking up the sim too.
the sim works fine on my mb886!
help? how can i disable sim lock? do i need to flash modem of some other version?
btw i am NOT using a US GSM SIM. Which don't work. I am using an international sim which worked fine before flashing.
Click to expand...
Click to collapse
Someone else will have to chime in as I honestly have no clue. My phone is still locked and a Verizon US phone, so what you are dealing with (aside from the actual act of flashing) is beyond my knowledge.

okay, got it working with a XT905 telstra rom. did a factory wipe everytime i flashed a new rom through rsd and deleted the var getvar oem parts from the xml file. all roms flashed fine. XT905 Telstra unlocked the SIM

droid.dessert said:
okay, got it working with a XT905 telstra rom. did a factory wipe everytime i flashed a new rom through rsd and deleted the var getvar oem parts from the xml file. all roms flashed fine. XT905 Telstra unlocked the SIM
Click to expand...
Click to collapse
Hmm. Interesting. Glad to hear you fixed it
Sent from my XT907 using Tapatalk 4 Beta

I know, I know, I'm stupid before you even read. Please help me with THIS brick...

I'm a total moron, I'll just start there. Was running KOT49H【4.4.2】Google Edition and wanted to go back to vision x since your latest update. Full wipe in twrp, installed vision x, icy theme, went to install ktoonsez kernel and it failed. Somehow between people distracting me, I decided it didn't fail. Reboot, and now bricked. Flashed stock firmware 4.2.2 mdl in odin, but no dice on the reboot. It's because I'm still on a 4.4.2 kernel, isn't it...
Now what do I do? Let kies fix me? Can kies even fix me with 4.4.2 not even being released yet? Kicking myself for being so dumb!!!

First, you're not on 4.4.2. Sounds like you're on 4.3. See if this helps you http://forum.xda-developers.com/showthread.php?p=48557730
This is for the i337

jd1639 said:
First, you're not on 4.4.2. Sounds like you're on 4.3. See if this helps you http://forum.xda-developers.com/showthread.php?p=48557730
This is for the i337
Click to expand...
Click to collapse
ok, I'm just saying, it wasn't booting after I put vision x 4.3 rom on without flashing the loki'd ktoonsez 4.3 kernel. Will updating flash the 4.3 kernel too?

xjimmy said:
ok, I'm just saying, it wasn't booting after I put vision x 4.3 rom on without flashing the loki'd ktoonsez 4.3 kernel. Will updating flash the 4.3 kernel too?
Click to expand...
Click to collapse
What bootloader are you one ? It seems to me you are on MDL and I can't see why you would need to flash the MK2. You are just stuck in recovery correct ? If you can get in recovery just flash the vision x rom again.
You didn't state if you can get into recovery or not. Everytime to flash a rom you flash a kernel so even KT's kernel failed you still have a kernel. You might need to explain some more
EDIT: your other post said you cant get into recovery. When you say no dice on the reboot does that mean it's in a bootloop and all you get is the sammy slash screen ? Can you try ODIN again and flash the MDL firmware. I'm not sure but back in the S3 days if you flashed older firmware you had a bootloop after but then had to just do a factory reset in stock 3e recovery and it would boot

hednik said:
What bootloader are you one ? It seems to me you are on MDL and I can't see why you would need to flash the MK2. You are just stuck in recovery correct ? If you can get in recovery just flash the vision x rom again.
You didn't state if you can get into recovery or not. Everytime to flash a rom you flash a kernel so even KT's kernel failed you still have a kernel. You might need to explain some more
EDIT: your other post said you cant get into recovery. When you say no dice on the reboot does that mean it's in a bootloop and all you get is the sammy slash screen ? Can you try ODIN again and flash the MDL firmware. I'm not sure but back in the S3 days if you flashed older firmware you had a bootloop after but then had to just do a factory reset in stock 3e recovery and it would boot
Click to expand...
Click to collapse
I did an emergency formware recovery via kies. It reset everything stock on 4.2.2 mdl! I thought for sure it would've bumped me to 4.3 that way. Thank you for taking the time to respond and try to help. I will be much more careful moving forward and am considering this luck for my crazy mistakes. Yay!!

help flashing Kit Kat, locked bootloader

I get a failed msg when I try the OTA update.
my phone is a xt907 currently rooted and system version is 98.30.1XT907, no bloatware removed
I know how to use RSD lite. which and where can I get the right files to flash back to stock
I've been searching this site and with unlocked bootloaders and lock bootloaders I don't know which files to use to flash back to stock

TwoBuells said:
I get a failed msg when I try the OTA update.
my phone is a xt907 currently rooted and system version is 98.30.1XT907, no bloatware removed
I know how to use RSD lite. which and where can I get the right files to flash back to stock
I've been searching this site and with unlocked bootloaders and lock bootloaders I don't know which files to use to flash back to stock
Click to expand...
Click to collapse
You can actually just flash the OTA with RSD. You need to remove all the getvar and oem lines from the .xml file once unpacked then flash. Worked for me first try after many fails. you loose root etc and user/app data etc.

I've been flashing roms since my Droid 1 but that might be a little advanced for me.
I'd really just like the correct file to flash back to stock so then I can upgrade to KK

I used a script generator from another site, flashed back to stock and was able to take the OTA update.
Now I'm running KK, now I'll just have to wait like everyone else for root access again,

Return to stock unrooted 4.4.4 KXE21.187-42 for XT1095

This is a nand that I created with twrp. It is completely stock and unrooted. By restoring this, flashing the stock At&t modem and flashing stock KXE21.187-42 recovery, you will be left with a complete stock unrooted kitkat Moto X XT1095 capable of taking the ota.
Nand bu KXE21.187-42
MD5-e9ce965a3a0370a47effa5005d5a07db
https://mega.co.nz/#!HQUlBKJa!VHsKA4miBIquiHGFVMxz8uxgAAyV0UFCVBWlK-uwDLQ
Stock KXE21.187-42 Recovery
MD5-a5673547c4a78b255cce3c64aa854a2b
https://mega.co.nz/#!SMcxwSbQ!jN2Y8EtryTlKXWgUPYg8Xi7pQihX9TsXd-PjJ6EPfSA
Modem
MD5-d1c083abf3ad22aa53c8a0346a0bf8fc
https://mega.co.nz/#!HAtRiBBC!Q7LmNt2NvPYmhGl8sA7yE3wA1Fdm71B4Kc-Z4Zss-YA
1. Place nand in the backups of your twrp recovery
2. Restore with twrp
3. Factory data/reset
4. Flash At&t modem (fastboot flash modem NON-HLOS.img)
5. Reboot to fastboot mode
6. Flash stock recovery (fastboot flash recovery recovery_victara_KXE21.187-42.img).
7. Reboot
If you want the OTA.... adb sideload (you can find the OTA file on another thread).
IF you follow the directions as I have laid out, you will have a completely stock, unrooted-fresh install of kitkat. You now should be able to safely take the ota using adb sideload.
This has been tried by myself multiple times successfully. This is only for the XT1095 variant. If you are crazy enough to try it on another variant, please post your results.
I am not responsible for anything that happens to your device. I will try and answer any questions as long as I have the time. Hit "thanks" if this helps.

Is it required to flash the att modem if i use tmobile?

Directions are not clear - especially regarding radio

expertzero1 said:
Is it required to flash the att modem if i use tmobile?
Click to expand...
Click to collapse
Yes, it's basically a prerequsite for the ota to flash. If you have no plan on flashing the ota, then you can use the radio of your choice.

Sdobron said:
Directions are not clear - especially regarding radio
Click to expand...
Click to collapse
Not to sure what you are saying.
fastboot flash modem NON-HLOS.img
That's pretty clear to me. Im guessing if you can flash a recovery, you can flash the modem, performed by fastboot.

rsa 329 said:
Not to sure what you are saying.
fastboot flash modem NON-HLOS.img
That's pretty clear to me. Im guessing if you can flash a recovery, you can flash the modem, performed by fastboot.
Click to expand...
Click to collapse
My pure edition, XT1095 came out of the box with T Mobile baseband / modem. Not sure why the ota would need AT&T (also had no issues sideloading the lollipop update)

I am pretty sure it is only required if you used the multitool which has a different modem included. This modem is not compatible with the 5.0 OTA.

nineismine said:
I am pretty sure it is only required if you used the multitool which has a different modem included. This modem is not compatible with the 5.0 OTA.
Click to expand...
Click to collapse
Which modem? The modem I have posted here? If thats what you are talking about you havent any idea what you are talking about.
I have done exactly what ive posted here multiple times. Use any other modem other than this one and the ota will fail.
As far as why people are calling it the att modem confuses me as well.
The multi tool flashes a 55R while this modem flashes 57R.

Sdobron said:
My pure edition, XT1095 came out of the box with T Mobile baseband / modem. Not sure why the ota would need AT&T (also had no issues sideloading the lollipop update)
Click to expand...
Click to collapse
I started this thread to return your XT1095 to stock unrooted, hence the title.
Since there are no factory images at the moment, I posted what worked for me.
Dont comment if you dont agree, but i assure you this method works just fine.

rsa 329 said:
Which modem? The modem I have posted here? If thats what you are talking about you havent any idea what you are talking about.
I have done exactly what ive posted here multiple times. Use any other modem other than this one and the ota will fail.
As far as why people are calling it the att modem confuses me as well.
The multi tool flashes a 55R while this modem flashes 57R.
Click to expand...
Click to collapse
The modem included in the Multitool as I inferred. If you flashed back to stock or used the image from the multitool you get the invalid modem b00 error. After which you have to use the AT&T modem in order for the OTA to complete successfully.

the radio point is mute since graffixnyc posted the stock pure edition modem on his site. The modem image he posted is a direct backup from his brand new Pure Edition

nineismine said:
The modem included in the Multitool as I inferred. If you flashed back to stock or used the image from the multitool you get the invalid modem b00 error. After which you have to use the AT&T modem in order for the OTA to complete successfully.
Click to expand...
Click to collapse
Correct, the modem I have linked was directly from graffix.

holy cow downloads from Mega are crawling for me. I heard a rumor from a friend of a friend that a certain OTA from an un-said company for an un-said device is going out 'very soon' and I want to be 100% stock before it goes out. Just in case it's for the moto X.
can I ask how you got back to 100% stock? In your previous thread (TWRP Backup of Lollipop) you mentioned that you couldn't do a backup of stock. I guess I just want to know that your stock backup of 4.4.4 isn't an un-rooted 4.4.4. I'm looking for never-been-rooted 4.4.4.

got this to work last night.
working great! sideloaded the ota!
flashed the modem after sideloading the ota.

Official factory image is now available from Motorola! https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images

edit: deleted, nevermind

holtenc said:
holy cow downloads from Mega are crawling for me. I heard a rumor from a friend of a friend that a certain OTA from an un-said company for an un-said device is going out 'very soon' and I want to be 100% stock before it goes out. Just in case it's for the moto X.
can I ask how you got back to 100% stock? In your previous thread (TWRP Backup of Lollipop) you mentioned that you couldn't do a backup of stock. I guess I just want to know that your stock backup of 4.4.4 isn't an un-rooted 4.4.4. I'm looking for never-been-rooted 4.4.4.
Click to expand...
Click to collapse
My 4.4.4 was rooted, and I just experimented with all the info that everyone was posting the day the 5.0 went live. I was able to unroot and flash a file that 0.0 had posted in the thread that graffix had started. Anyway long story short between that and experimenting with the recovery and modems I was able to get my 4.4.4 to take the OTA with no problems. Since the OTA checks file structure and recovery, modem, etc....I am assuming it is unrooted stock. The way I look at it, If the OTA will flash with my experiment, so should the actual release. That is just my logic anyway.

Thank you for putting this guide together. Everything worked flawlessly. Thank you.

Upgrading to 6.0 on I337

I have been trying to upgrade my 4.4.2 s4 I337 to 6.0 marshmellow and am having many problems. Also I am EXTREMELY new to anything android or flashing or anything like this at all, I learned everything I know just today.
I rooted my phone using the towelroot method because it was the easiest for my phone. I am also using safestrap recovery because I think my phone is bootloader locked? I was having a lot of problems trying to install twrp so I just assumed it was that. I'm using usb debugging and I am using the 6.0 pico gapps.
I have tried multiple roms using safestrap and making sure that the rom is specifically for my phone, at&t and I337 but each time the rom shows it was successful and I reboot it goes to recovery booting and says I don't have an OS and I have to recover back to stock firmware using odin, beccause I did a full wipe before each install of the roms.
If there is any other info I might have missed or have anything to help me I would greatly appreciated it, and again I basically have no idea what I am doing and am just going off of trial and error and googling what every term means. Thank you
Edit: My bootloader is NB1 if that matters also.
Edit: Doing a little more searching is it even possible for me to get 6.0 with my phone?

The bootloader on your phone is locked and cannot run any custom ROMs unless it is a rom that is based on a stock Samsung ROM; therefore, a 6.0 ROM or higher is not possible. Also, Lineage, RR, etc. is not possible.

audit13 said:
The bootloader on your phone is locked and cannot run any custom ROMs unless it is a rom that is based on a stock Samsung ROM; therefore, a 6.0 ROM or higher is not possible. Also, Lineage, RR, etc. is not possible.
Click to expand...
Click to collapse
Thank you for the reply! After a lot more researching and doing very stupid stuff (it was all for fun and learning mostly anyway) I did brick my phone saying firmware upgrade encountered an issue I can only get to download mode I tried flashing the original firmware I had using the stock 4.4 nb1 file but that is also now failing in odin, do you have any suggestions that could work?
Edit: I tried flashing to mk2 and thats how it bricked, but shouldn't I be able to go back to my stock firmware even if I bricked my phone like this? Both the towelrootable stock nb1 4.4 and the normal stock nb1 4.4 isnt working when I try to flash them in odin

You should flash the same or newer ROM to the phone. Even though the phone says it encountered an error, you can still flash the phone with Odin with this message in the screen.
Hopefully, this thread will help: https://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642

audit13 said:
You should flash the same or newer ROM to the phone. Even though the phone says it encountered an error, you can still flash the phone with Odin with this message in the screen.
Hopefully, this thread will help: https://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642
Click to expand...
Click to collapse
I'm probably jinxing it by typing while its still working but I switched my usb cable and so far it hasn't failed when before it would fail immediatly, thank you for all the help!

Only the MDL bootloader can run non touchwiz ROMs. All other bootloaders can only run touch wiz based ROMs.