[SIZE=+2]This thread has been created
for
Questions & Answers/Troubleshooting[/SIZE][SIZE=+2]Specific to[/SIZE]
Motorola Droid Razr M
[XT905, XT907]
Please feel free to share issues, questions and offer help. Noob questions are welcomed.
It is always best to use the Thanks button , in lieu of simply posting "Thank you".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please keep discussion focused, on questions pertaining to this Device
List of supporters
@sd_shadow
@ATTACK
@xKroniK13x
@RikRong
To those seeking help: Please don't bombard the supporters with PMs asking for help. Instead, ask your question here in the thread so others can benefit from the solution to your problem as well. If you want to be sure someone particular gets notified of your question, put his / her username directly after an @. Also, if you have ROM related questions, post in the relevant ROM Q&A thread (if there is one) or directly in the ROM development thread. If you are not eligible of posting there, you may post here. Thank you!
Supporters: If you want to be put on or off the list, just make a request here in the thread!
ROM developers: Please read this. Consider if you want to have a ROM specific help thread or not, if not, most likely questions about your ROM will be asked here if the users aren't eligible for posting in development section.
Before posting anything, I strongly advise you to read
Forum Rules
[GUIDE] - XDA New User Guide - Getting started on XDA
XDA Tour
[INDEX] Motorola Droid Razr M by sd_shadow
[GUIDE][FAQ][KK] How to Root, Boot Unlock & More by ATTACK
[Index]Motorola Flashing Utilities, Firmware, and more
Please Provide as much as the the following Information that you can, with Your Question
Your bootloader status if applicable
Rom name with complete baseband/date/version
Kernel name
Any Mods you are using
If you are using Custom Rom, your flashing style i.e dirty/clean or you wiped anything else in specific
If you used any guide, link to the guide
Root status
Your exact problem
Any method you tried that failed
Any other detail you think would be necessary
If you do not include the information, it will be the first thing I ask.
Please look for a similar [HELP THREAD] when visiting another device forum.
If you would like to create a similar [Help Thread] please Click Here.
@sd_shadow
I would like to be added to the supporters list.
Sent from my XT1031
ATTACK said:
@sd_shadow
I would like to be added to the supporters list.
Sent from my XT1031
Click to expand...
Click to collapse
Done.
Sent from my XT907 using Tapatalk
Razr m on metro pcs?
Hello there, I'm new here and hoping you could help me with my question. I was wondering if you can use a razr m on metro's new network. They're upgrading from cdma to gsm. If it is possible what would I need to do for it to work? I've gotten many mixed answers on this question and it's created a lot of confusion for me. Thank you.
DraculaSb said:
Hello there, I'm new here and hoping you could help me with my question. I was wondering if you can use a razr m on metro's new network. They're upgrading from cdma to gsm. If it is possible what would I need to do for it to work? I've gotten many mixed answers on this question and it's created a lot of confusion for me. Thank you.
Click to expand...
Click to collapse
see [HowTo] [VZW XT907/926 RAZR M/HD] Unlock US GSM Carriers Using RadioComm by cellzealot
and
[Tutorial] Unlock VZW Razr M/M HD (XT907/XT926) for U.S. Carriers *CDMA WS METHOD* by dragonhart6505
I'm not positive that these options still work
What system version is on the device?
Bootloader locked or unlocked?
@ATTACK may have a better answer
@DraculaSb
First verify that the Razr M supports Metro's new GSM bands. If it does, then unlock them via the links @sd_shadow shared with you.
Sent from my XT1031
Metro PCS is owned by T-mobile now https://en.wikipedia.org/wiki/MetroPCS
so if T-mobile is working for other XT907 owners? should be the same for Metro PCS.
Thanks, I was just researching that. So I use both the links I was sent? Also how do I go about the sim card unlocking, flashing, etc. Is any of that even necessary to get it to the carrier? Or just follow the links I was given? Just trying to clarify things.
DraculaSb said:
Thanks, I was just researching that. So I use both the links I was sent? Also how do I go about the sim card unlocking, flashing, etc. Is any of that even necessary to get it to the carrier? Or just follow the links I was given? Just trying to clarify things.
Click to expand...
Click to collapse
Just use one of the methods
Shouldn't need to sim card unlock
Just the band unlocking.
Sent from my XT907 using Tapatalk
Okay I understand. And that's it?
DraculaSb said:
Okay I understand. And that's it?
Click to expand...
Click to collapse
Should be good.
I would try [Tutorial] Unlock VZW Razr M/M HD (XT907/XT926) for U.S. Carriers *CDMA WS METHOD* by dragonhart6505
@sd_shadow I'm willing to help if you'd like to add me to the support list!
Sent from my Moto X 2014 Pure Edition using Tapatalk
xKroniK13x said:
@sd_shadow I'm willing to help if you'd like to add me to the support list!
Sent from my Moto X 2014 Pure Edition using Tapatalk
Click to expand...
Click to collapse
Done.
Throw me on the list too. I'm not great with some of the technical things sometimes, but that's why you other three are here. Haha
Sent from my Nexus 5
RikRong said:
Throw me on the list too. I'm not great with some of the technical things sometimes, but that's why you other three are here. Haha
Sent from my Nexus 5
Click to expand...
Click to collapse
Done.
Sent from my XT907 using Tapatalk
I've read somewhere that once it's unlocked and the system gets upgraded you can't unlock it again? Also, once I unlock it will it be fully functional on metro pcs? Sorry for all the questions.
DraculaSb said:
I've read somewhere that once it's unlocked and the system gets upgraded you can't unlock it again? Also, once I unlock it will it be fully functional on metro pcs? Sorry for all the questions.
Click to expand...
Click to collapse
There are 3 different types of un/locking
Sim locking: which Motorola stopped doing.
Radio Band locking: which is what you want, Flashing firmware with RSD Lite will relock radio bands.
Bootloader lock: once unlocked it can not be relocked
Sent from my XT907 using Tapatalk
DraculaSb said:
I've read somewhere that once it's unlocked and the system gets upgraded you can't unlock it again? Also, once I unlock it will it be fully functional on metro pcs? Sorry for all the questions.
Click to expand...
Click to collapse
Yes, once you unlock the radios, you will be able to use Metro's service, but...
It's also important to note which bands T-Mobile/Metro uses compared to which bands the Razr M uses and which T-Mobile/Metro bands are supported in your area.
I know T-Mobile bought some band 13 (LTE) from Verizon, which the Droid Razr M uses for LTE, but does your area support T-Mobile's band 13? If not, you may be stuck to 3G or even EDGE.
I haven't looked into it myself but its something to be aware of, because it will dictate your experience.
Sent from my XT1031
hello all.
For starters, I'm typically on sprint/samsung forums.
But my son, aware of my 'hacking' of our phones, alerted his girlfriend that "my dad can probably fix that"...
So here I am.
With a droid RAZR M on Verizon (xt907)
I've done the soft reset (vol down / power for 10 seconds). This gets me to a screen where I can see the battery if I push the vol key (currently 36% charge...)
So - I then go and try to boot the phone.
I get the DROID logo, then the red 'eye' with lightning... but that's been on for the past 10 minutes...
yes, it has a SIM card in it.
Help?
Bigjohn_S said:
hello all.
For starters, I'm typically on sprint/samsung forums.
But my son, aware of my 'hacking' of our phones, alerted his girlfriend that "my dad can probably fix that"...
So here I am.
With a droid RAZR M on Verizon (xt907)
I've done the soft reset (vol down / power for 10 seconds). This gets me to a screen where I can see the battery if I push the vol key (currently 36% charge...)
So - I then go and try to boot the phone.
I get the DROID logo, then the red 'eye' with lightning... but that's been on for the past 10 minutes...
yes, it has a SIM card in it.
Help?
Click to expand...
Click to collapse
Several things can be tried.
Remove sim card, try to boot.
Power the Device Up in Safe Mode - DROID RAZR M by MOTOROLA / LUGE by Motorola
Perform a Factory Data Reset (Device Powered Off) - DROID RAZR M by MOTOROLA / LUGE by Motorola
If those fail, charge the battery to 100% and boot the device to AP Fastboot
To boot to AP Fastboot: power off, hold volume down, press power button for 5 secs then release.
and post complete text on screen here
Related
SM - N9005 test ROOT kernel, are you willing to try
:laugh: 如果您有测试，请回复于我谢谢！
Installation:
Turn off your device
while long press volume down HOME OFF key
blinks odin3.09 robot opens identify your
device selected AP - N9005_Root_su1.60_summer.tar.md5
begin pass through
Looking forward to your test !
summer.peak said:
I'm sorry, I don't have permission to release the connection
Click to expand...
Click to collapse
View attachment 2257464
Did not anyone to test it
I want to say is that I can already post a link , the address has been affixed
summer.peak said:
I want to say is that I can already post a link , the address has been affixed
Click to expand...
Click to collapse
Can you get the Verizon test kernel?
2swizzle said:
Can you get the Verizon test kernel?
Click to expand...
Click to collapse
If you have a N9005 equipment, you can try it, he can't harm your mobile phone
2swizzle said:
Can you get the Verizon test kernel?
Click to expand...
Click to collapse
summer.peak said:
If you have a N9005 equipment, you can try it, he can't harm your mobile phone
Click to expand...
Click to collapse
I just wanted to make this perfectly clear: DO NOT use this kernel on a Verizon variant (almost impossible as it hasn't been officially released). This kernel is not signed and the bootloader will error out. You'll then be soft bricked until you flash a signed kernel in Odin.
Visual proof...first the signed unsecure kernel that allowed first root on the VZN SGS4 (notice the signature at the bottom):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now your boot.img....which is missing the signature:
Again, please folks...do NOT flash this if you don't have an unlocked bootloader and an original kernel backup. Things could get REAL UGLY, REAL FAST.
Confirmed variants for various countries
SM-N9002 Dual Sim variant for Chinese Market
SM-N9005 LTE variant
SM-N900K for KT Telecom South Korea
SM-N900L for LGU+ South Korea
SM-N900S for SK Telecom South Korea
SM-N900A for AT&T United States
SM-N900T for T-Mobile USA
SM-N900V for Verizon Wireless
SM-N900,International variant
SLC22 for KDDI AU Japan
SGH-N075 and SGH-N099 for NTT Docomo Japan
Just in case people want to Note 3 model numbers .........
docnok63 said:
I just wanted to make this perfectly clear: DO NOT use this kernel on a Verizon variant (almost impossible as it hasn't been officially released). This kernel is not signed and the bootloader will error out. You'll then be soft bricked until you flash a signed kernel in Odin.
Visual proof...first the signed unsecure kernel that allowed first root on the VZN SGS4 (notice the signature at the bottom):
Now your boot.img....which is missing the signature:
Again, please folks...do NOT flash this if you don't have an unlocked bootloader and an original kernel backup. Things could get REAL UGLY, REAL FAST.
Click to expand...
Click to collapse
You say that this kernel is not signed ?
No, it's not. No need for it to be. International bootloader is not locked.
Sent from my SCH-I545 using Tapatalk 4
docnok63 said:
I just wanted to make this perfectly clear: DO NOT use this kernel on a Verizon variant (almost impossible as it hasn't been officially released). This kernel is not signed and the bootloader will error out. You'll then be soft bricked until you flash a signed kernel in Odin.
Visual proof...first the signed unsecure kernel that allowed first root on the VZN SGS4 (notice the signature at the bottom):
Now your boot.img....which is missing the signature:
Again, please folks...do NOT flash this if you don't have an unlocked bootloader and an original kernel backup. Things could get REAL UGLY, REAL FAST.
Click to expand...
Click to collapse
docnok63 said:
No, it's not. No need for it to be. International bootloader is not locked.
Sent from my SCH-I545 using Tapatalk 4
Click to expand...
Click to collapse
Is not the leaked version will be the case? Official version would not have been so right?
Sorry, I noted that the test subject, because I do not have this equipment
Thank you for correcting me, I look!
summer.peak said:
Is not the leaked version will be the case? Official version would not have been so right?
Sorry, I noted that the test subject, because I do not have this equipment
Thank you for correcting me, I look!
Click to expand...
Click to collapse
Since it's now VERY obvious you are not the author of this kernel, I will try to explain what I think happened. The person that created this kernel probably (and I say probably because I'm not going to waste the time and bandwidth to download 1.9GB of software I don't need) downloaded the leaked firmware and extracted the boot.img. He then made two minor adjustments that gave root access and repackaged the kernel. This probably took all of two minutes. I haven't looked at the original boot.img, but there's a 99% chance this gives root on a N9005.
There's a 50/50 chance it will work on any other N3 variant that doesn't have a locked bootloader. It depends entirely on how closely the keys match. In the US, this means Sprint, T-mobile, and sometimes AT&T. The S4's bootloader was locked by AT&T and I'm expecting the N3's to be as well. Verizon is almost always locked unless you buy a developer edition phone. A locked bootloader will fail to boot an unsigned kernel and the phone will be soft bricked.
This is one of the reasons unlocking a bootloader is so important to people that enjoy customizing their Android phones. It allows for custom recovery installation, custom kernel (which can then be unsigned), and custom ROM installation. Root can still be achieved with a locked bootloader, but it is much more difficult.
docnok63 said:
Since it's now VERY obvious you are not the author of this kernel, I will try to explain what I think happened. The person that created this kernel probably (and I say probably because I'm not going to waste the time and bandwidth to download 1.9GB of software I don't need) downloaded the leaked firmware and extracted the boot.img. He then made two minor adjustments that gave root access and repackaged the kernel. This probably took all of two minutes. I haven't looked at the original boot.img, but there's a 99% chance this gives root on a N9005.
There's a 50/50 chance it will work on any other N3 variant that doesn't have a locked bootloader. It depends entirely on how closely the keys match. In the US, this means Sprint, T-mobile, and sometimes AT&T. The S4's bootloader was locked by AT&T and I'm expecting the N3's to be as well. Verizon is almost always locked unless you buy a developer edition phone. A locked bootloader will fail to boot an unsigned kernel and the phone will be soft bricked.
This is one of the reasons unlocking a bootloader is so important to people that enjoy customizing their Android phones. It allows for custom recovery installation, custom kernel (which can then be unsigned), and custom ROM installation. Root can still be achieved with a locked bootloader, but it is much more difficult.
Click to expand...
Click to collapse
Night I went to pass the original kernel boot.img hotfile, posted to the address given when you download Yes, this is what I extracted from N9005XXUBMH1 leaked version of boot.img modified, is intended only to test , thank you for your correction and help
2swizzle said:
Can you get the Verizon test kernel?
Click to expand...
Click to collapse
summer.peak said:
Night I went to pass the original kernel boot.img hotfile, posted to the address given when you download Yes, this is what I extracted from N9005XXUBMH1 leaked version of boot.img modified, is intended only to test , thank you for your correction and help
Click to expand...
Click to collapse
http://hotfile.com/dl/245878747/5ea0de2/N9005XXUBMH1-boot.img.zip.html
At this time of the original boot. Img
summer.peak said:
sm - n9005 test root kernel, are you willing to try
:laugh: 如果您有测试，请回复于我谢谢！
installation:
Turn off your device
while long press volume down home off key
blinks odin3.09 robot opens identify your
device selected ap - n9005_root_su1.60_summer.tar.md5
begin pass through
Click to expand...
Click to collapse
我有机器，想测试一下，请给地址！！
Korea Telecom (KT) Anyone?
Has anyone tried rooting the SM-N900K?
Does the galaxy3root dot com method work?
Terrified of trying this for fear that it will brick my device.
I'm trying to figure out why anyone would try this, when Chainfire has done his thing, is this to try and avoid the counters being triggered or something?
Edit: Scratch that.... just noticed the dates.... didn't realise how far down the forum list I'd scrolled in tapatalk haha.
Sent from my SM-N9005 using Tapatalk 4
proxywolf said:
Has anyone tried rooting the SM-N900K?
Does the galaxy3root dot com method work?
Terrified of trying this for fear that it will brick my device.
Click to expand...
Click to collapse
Did you find a method that works for SM-N900K yet? I am looking for the same thing...
kalowinta said:
Did you find a method that works for SM-N900K yet? I am looking for the same thing...
Click to expand...
Click to collapse
Still looking. Doesn't look like many Korean residents use this forum.
Put together a video guide to root your Moto X. If anyone knows of a current way to root the ATT or VZW model, please let me know so I can throw together a video guide for those.
You'll first need to unlock your bootloader which will void your warranty.
How to unlock bootloader:
http://youtu.be/3sxgz7jxRMw
How to root the Moto X:
http://youtu.be/2fzih8xkki0
Free Wifi Tether/Hotspot on the Moto X:
http://www.youtube.com/watch?v=3Y92JR0jlR0
Hope these help.
qbking77 said:
Put together a video guide to root your Moto X. If anyone knows of a current way to root the ATT or VZW model, please let me know so I can throw together a video guide for those.
You'll first need to unlock your bootloader which will void your warranty.
How to unlock bootloader:
http://youtu.be/3sxgz7jxRMw
How to root the Moto X:
http://youtu.be/2fzih8xkki0
Hope these help.
Click to expand...
Click to collapse
First of all THANX!!!! I'm a big fan (I got the Motorola Photon way back when, and you were my source for all the coolness)!!!
Have you checked this thread out? I've done it and I'm rooted without unlocking my bootloader (didn't void any warranties). I can confirm that it works on the Sprint Moto X, but I'm pretty sure that it works on all variants...
In any case, keep up your great work!!!
Added free hotspot video to the OP
http://www.youtube.com/watch?v=3Y92JR0jlR0
Added free hotspot video to the OP
http://www.youtube.com/watch?v=3Y92JR0jlR0
Thank you for your time and effort to make these videos.
It might be worth being a little more specific in your wifi hotspot description though. The Rogers Moto X requires no mods to use wifi/bluetooth or usb hotspot, its 100% based on the provider and pretty much every data plan in Canada can be used any way you please. And it will never be "free", its always tied to the data plan.
what is the difference between this method of rooting compare to the pwnmymoto root?
winn75 said:
what is the difference between this method of rooting compare to the pwnmymoto root?
Click to expand...
Click to collapse
Its way safer to unlock the boot loader and flash a custom recovery, you'll be free to flash Roms and mods without majors issues, pwnmymoto is not a permanent root method. The only draw back is unlocking the boot loader voids your warranty although if you screw up your phone with safestrap, you probably voided your warranty too
Sent on my Moto X
Hi qbking77,
Saw your you-tube videos. Looks great and fairly straight forward. Not very different from my Moto RAZR.
Do you know if there is a way to re-lock the boot loader for warrant etc?
Thanks,
CharlesG70 said:
Hi qbking77,
Saw your you-tube videos. Looks great and fairly straight forward. Not very different from my Moto RAZR.
Do you know if there is a way to re-lock the boot loader for warrant etc?
Thanks,
Click to expand...
Click to collapse
Relocking your boot loader will not make any difference for warranty purposes, Motorola has your info as soon as you unlock through their website
Sent on my Moto X
flashallthetime said:
Relocking your boot loader will not make any difference for warranty purposes, Motorola has your info as soon as you unlock through their website
Sent on my Moto X
Click to expand...
Click to collapse
True, but it is possible to get the code and not use it. It is the act of Unlocking that breaks the warrant, not getting the code.
If there were a way to reset the device and relock the Bootkloader then you could "Say" you go the code but did not use it.
on a purely theoretical side I am still interested in if anyone has been working on this.
I suspect that there is some hidden switch in the hardware that would be triggered if the Bootloader is unlocked so there would be no point but still it is worth asking.
Cheers all
Will this method work on latest camera OTA update?
Sent from my XT1055 using XDA Premium 4 mobile app
I would also like to know whether this will work with latest camera update. Also, if and when we finally get 4.4 will it work for that. I just want to get root, not flash roms. The support here is abysmal. I came from the s4 and there's so much support there you don't know what to do with it. I get that this phone is phenomenal, but a little help would be nice
Sent from my XT1056 using Tapatalk
shloho said:
I would also like to know whether this will work with latest camera update. Also, if and when we finally get 4.4 will it work for that. I just want to get root, not flash roms. The support here is abysmal. I came from the s4 and there's so much support there you don't know what to do with it. I get that this phone is phenomenal, but a little help would be nice
Sent from my XT1056 using Tapatalk
Click to expand...
Click to collapse
Well the S4 needs major help in de-cluttering... but agreed, not a lot of support (not that I know what I am doing...). But tons of Dev Editions have been bought so hopefully that will boost people here!
I got my moto x in late December 13, and it immediately began upgrading the camera issues and upgraded to KitKat. Will this root method work for KitKat devices?
Sent from my Moto X
-B
No Data
After unlocking the bootloader my phone will no longer access data off of wifi. Any suggestions? I have already done the ##SCRTN#, flashed to stock rom, ##RTN#, update profile and prl fail unless on wifi and still no data off wifi.
OK, I just got the notice for my update to 4.4.4, I'm rooted (boot loader unlocked, etc...), general rule of thumb?....thanks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
dmonleo said:
OK, I just got the notice for my update to 4.4.4, I'm rooted (boot loader unlocked, etc...), general rule of thumb?....thanks.
Click to expand...
Click to collapse
You just resurrected a VERY old thread.
The procedure hasn't changed.
The easiest way (in my opinion) is to save anything important to you and then use RSD Lite to flash the entire stock 4.4.2 SBF (this will erase everything).
Then, take the OTA. After you are successfully on 4.4.4, you fastboot flash TWRP recovery, and it offers to root for you. Then you can set everything up as you like.
If you are against erasing everything, you can flash stock recovery back on, un-do any modifications you have made to /system, uninstall Xposed (if installed), then attempt to take the OTA. This method is riskier. You will still have to re-flash TWRP afterwards and re-root.
Good Luck!
samwathegreat said:
You just resurrected a VERY old thread.
The procedure hasn't changed.
The easiest way (in my opinion) is to save anything important to you and then use RSD Lite to flash the entire stock 4.4.2 SBF (this will erase everything).
Then, take the OTA. After you are successfully on 4.4.4, you fastboot flash TWRP recovery, and it offers to root for you. Then you can set everything up as you like.
If you are against erasing everything, you can flash stock recovery back on, un-do any modifications you have made to /system, uninstall Xposed (if installed), then attempt to take the OTA. This method is riskier. You will still have to re-flash TWRP afterwards and re-root.
Good Luck!
Click to expand...
Click to collapse
I'll have to read up on RSD Lite SBF, I rooted using fastboot... I'm familiar with TWRP. Can easily return modifications. Thanks for the response.
Can i unlock and root my moto x xt 1060 (vrz) 2013? It is an unlocked gsm version using in asia. Thanks.
stevedat said:
Can i unlock and root my moto x xt 1060 (vrz) 2013? It is an unlocked gsm version using in asia. Thanks.
Click to expand...
Click to collapse
That doesn't make sense. A Verizon XT 1060 and the unlocked GSM XT 1053 are different models
MOTO E Experimental Root. Not sure if it works. Try on your own risk
This guide helps you to root your Moto E
1) Install Framaroot
2) Use Gandalf exploit to root your device
Wait.... you may have to unlock your boot loader first
Warning : Unlocking bootloader voids your warranty
I am unsure whether this method works or not. But I have seen Framaroot work on other devices running the same specs but you can try. But I think we'll first need permissions from moto to unlock moto E
i think we'll get the answer soon
Wait so you've declared its rooted, then said you don't know whether it will work or not. Please do not mislead users this way.
Sent from my Nexus 7 using Tapatalk
cybojenix said:
Wait so you've declared its rooted, then said you don't know whether it will work or not. Please do not mislead users this way.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I'm not misleading anybody. I am just suggesting if anyone wants to try it they can.
But I'm not as of now a 100% sure this would work.
Since this worked on other devices with same chipset I think it should work here too.
You are. The first words the user reads is [ROOT]Moto E. Which means this is a rooting guide. The next ones they read are a deceleration of "MOTO E ROOTED". Can you please change the wording. Thank you.
Sent from my Nexus 7 using Tapatalk
cybojenix said:
You are. The first words the user reads is [ROOT]Moto E. Which means this is a rooting guide. The next ones they read are a deceleration of "MOTO E ROOTED". Can you please change the wording. Thank you.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
+1
Sent from my C2004 using Tapatalk
Falcon G said:
MOTO E ROOTED
This guide helps you to root your Moto E
1) Install Framaroot
2) Use Gandalf exploit to root your device
Click to expand...
Click to collapse
Please do not mislead others. It would be nice if you can change the heading and the content.
cybojenix said:
You are. The first words the user reads is [ROOT]Moto E. Which means this is a rooting guide. The next ones they read are a deceleration of "MOTO E ROOTED". Can you please change the wording. Thank you.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
SArnab©® said:
+1
Sent from my C2004 using Tapatalk
Click to expand...
Click to collapse
tamilmad said:
Please do not mislead others. It would be nice if you can change the heading and the content.
Click to expand...
Click to collapse
Sorry guys didn't meant to disappoint you. I've changed the title. Thank you. I will be looking forward to try this on my moto E when it comes and will update thereafter. Thank you and sorry again
I would like to remind everyone that XDA is a "USE AT YOUR OWN RISK" site.
The OP now has warnings in it for a reason.
If you are willing to risk the damage to your phone proceed with caution.
I will add that most development starts with a few "bumps" in the road so hold on tightly
If you have further issues in regards to my post, then please PM me
Toledo_JAB said:
I would like to remind everyone that XDA is a "USE AT YOUR OWN RISK" site.
The OP now has warnings in it for a reason.
If you are willing to risk the damage to your phone proceed with caution.
I will add that most development starts with a few "bumps" in the road so hold on tightly
If you have further issues in regards to my post, then please PM me
Click to expand...
Click to collapse
shouldn't this thread be move to development section ?
Half Way
I followed the steps to unlock my bootloader of Moto E first as instructed in official Motorola website. They sent me mail with unlock code by checking my device id. Process was just like Moto G. But after that I installed custom recovery like CWM and TWRP meant for Moto G in fastboot mode. But Every time, when I try to boot into recovery mode after flashing it's showing 'Mismatching Partition Size' and then 'Boot failed'. No custom recovery of Moto G worked and I got the same message. I think we need a specific custom recovery written for Moto E. Even I can revert to my stock recovery too! Can developers please help me ragarding this custom recovery mode issue of Moto E? Assistance appreciated.
noeticdm said:
I followed the steps to unlock my bootloader first today of Moto E as instructed in official Motorola website. They sent me mail with unlock code by checking my device id. Process was just like Moto G. But after that I installed custom recovery like CWM and TWRP meant for Moto G in fastboot mode. But Every time, when I try to boot into recovery mode after flashing it's showing 'Mismatching Partition Size' and then 'Boot failed'. No custom recovery of Moto G worked and I got the same message. I think we need a specific custom recovery written for Moto E. Even I can revert back to my stock recovery too! Can developers please help me ragarding this custom recovery mode issue of Moto E? Assistance appreciated.
Click to expand...
Click to collapse
This couldn't have worked because Moto G has a different CPU.
Until we'll get a flashable stock firmware or someone with root will dump the recovery partition there's no way to fix your phone.
But it's great to hear that unlocking is possible now.
m11kkaa said:
This couldn't have worked because Moto G has a different CPU.
Until we'll get a flashable stock firmware or someone with root will dump the recovery partition there's no way to fix your phone.
But it's great to hear that unlocking is possible now.
Click to expand...
Click to collapse
Yes I unlocked the bootloader successfully. But thing is that I try to root it at any cost. There is no intention of getting the stock one back. I need custom one meant for moto e which will install SU.zip at ease. Actually net 2.21GB internal memory is too low to work on heavy games. Even with this Adreno 302 GPU it is handling games like Asphal8 8 quite well. So root is absolute need!! Developers, please help.
m11kkaa said:
shouldn't this thread be move to development section ?
Click to expand...
Click to collapse
As this is only a share of someone else's work it should stay in the general section for now.
Possibly once the process is a sure thing then maybe it will be moved.
Screenshot where I stuck!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
noeticdm said:
I followed the steps to unlock my bootloader of Moto E first as instructed in official Motorola website. They sent me mail with unlock code by checking my device id. Process was just like Moto G. But after that I installed custom recovery like CWM and TWRP meant for Moto G in fastboot mode. But Every time, when I try to boot into recovery mode after flashing it's showing 'Mismatching Partition Size' and then 'Boot failed'. No custom recovery of Moto G worked and I got the same message. I think we need a specific custom recovery written for Moto E. Even I can revert to my stock recovery too! Can developers please help me ragarding this custom recovery mode issue of Moto E? Assistance appreciated.
Click to expand...
Click to collapse
You can brick your device by flashing a recovery from another device.
Sent from my Nexus 5 using Tapatalk
munchy_cool said:
You can brick your device by flashing a recovery from another device.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yeh I knew. But I just tried to root it desperately. Hope, developers should come with better and proper solution soon for this newly launched device. But my device is not briked. It's working fine in normal boot. Just recovery mode is not booting up. Even as there is no stock firmwire available for Moto E as of now over the web I couldn't get the stock recovery. So I said I am in half way.
Is it like that at no time I can change the state of my present situation of recovery mode even if there is specific custom recovery for Moto E released in future??!!
Toledo_JAB said:
I would like to remind everyone that XDA is a "USE AT YOUR OWN RISK" site.
The OP now has warnings in it for a reason.
If you are willing to risk the damage to your phone proceed with caution.
I will add that most development starts with a few "bumps" in the road so hold on tightly
If you have further issues in regards to my post, then please PM me
Click to expand...
Click to collapse
Thank You Sir.
I do understand the cautions by the users. So I would be soon updating this thread as I will be getting my Moto E.
Also I don't think this method has the potential to brick the device.
Thank You
Falcon G
Guys Please DON'T FLASH ANY MOTO G recovery. They will brick your device. Also those who have the moto E can they confirm whether this method works.
Thank You
Falcon G
Today my friends send this pics to me(find the attachments).
Developers fight hard for us to get root but in China it is easy to get a unlocked BL version of DT.
Of course we can definitely sure that this is not a retail version. 'Some models leaked from factory'.
I can easily buy one for $620.00 from taobao(Chinese ebay).
Now I only hope the developers can fight harder to get us unlocked or fully rooted.
Also, FU VERIZON, GIVE ME 5.1!!!!
Uhhh..... I hope a dev sees this, confirms, and says that "Yeah if that guy can upload something from his phone we can crack this sucker!"
#thedream
I have faith in this. Shenzhen is basically where they make all of our electronics, and I wouldn't be surprised if this is real.
Any chance in hell that this could be applied to ultra/maxx
Sent from my XT1080 using XDA Free mobile app
drmrjake said:
Any chance in hell that this could be applied to ultra/maxx
Sent from my XT1080 using XDA Free mobile app
Click to expand...
Click to collapse
We don't even have anything for the turbo, why on earth would something that doesnt exist yet work on the ultra/maxx. Also this device as far as I read was sold with BL unlock, not something done after the fact.
Flowah said:
Uhhh..... I hope a dev sees this, confirms, and says that "Yeah if that guy can upload something from his phone we can crack this sucker!"
#thedream
Click to expand...
Click to collapse
Nope. :/
r3pwn said:
Nope. :/
Click to expand...
Click to collapse
Why?
ilia3367 said:
Why?
Click to expand...
Click to collapse
1) The bootloader on there is a lower version than what you have on your phone, so flashing it would brick yours.
2) Even if it didn't brick when you flashed it, it would behave like the normal bootloader, as you are still using a production device.
My bad
Sent from my XT1080 using XDA Free mobile app
r3pwn said:
1) The bootloader on there is a lower version than what you have on your phone, so flashing it would brick yours.
2) Even if it didn't brick when you flashed it, it would behave like the normal bootloader, as you are still using a production device.
Click to expand...
Click to collapse
look at this BL version, this is the latest version right?
The seller said they can unlock the bootload, not sure how...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
chrisjenho said:
Today my friends send this pics to me(find the attachments).
Developers fight hard for us to get root but in China it is easy to get a unlocked BL version of DT.
Click to expand...
Click to collapse
Edited: On Motorola devices that are legally shipped (meaning not stolen from the Chinese factory where they are produced), Status Code 0 is the Locked and never been unlocked by the fastboot oem unlock command state.
The phones are manufactured unlocked in the state Status Code 1, and are locked before they leave the factory and so will be Status Code 0 Locked upon receipt. The only way to get a Motorola phone that is Status Code 1 Unlocked is to "take" it from the Chinese factory before it gets locked and put into the state Status Code 0 Locked.
As is clear from that photo, the bootloader status is Status Code 1 Unlocked. AFAIK, this is one of those "factory" devices as they are referred to on Tao Bao. They have not yet been locked before they are "removed" from the factory. I doubt this was accomplished by a "developer". The only way to get a Motorola phone that is Status Code 1 Unlocked is to "remove" it from the factory before the phone is locked for the first time.
Where to buy on taobao
I know that you cannot post a link to the sale item (xda rules). But, can you provide detailed instructions on how someone like me could find it via searching on taobao?
Great find, and thanks in advance.
sd_matto said:
I know that you cannot post a link to the sale item (xda rules). But, can you provide detailed instructions on how someone like me could find it via searching on taobao?
Great find, and thanks in advance.
Click to expand...
Click to collapse
PM sent.
taobao is not that friendly for oversea buyers, payment and shipment...
JulesJam said:
On Motorola devices that are legally shipped (meaning not stolen from the Chinese factory where they are produced), Status Code 1 is the Locked and never been unlocked by the fastboot oem unlock command state. The phones are manufactured unlocked, and are locked before they leave the factory and so will be Status Code 1 Locked upon receipt.
As is clear from that photo, the bootloader status is Status Code 1 Unlocked. AFAIK, this is one of those "factory" devices as they are referred to on Tao Bao. They have not yet been locked before they are removed from the factory. I doubt this was accomplished by a "developer". The only way to get a Motorola phone that is Status Code 1 Unlocked is to remove it from the factory before the phone is locked.
Click to expand...
Click to collapse
I think you might be mistaken. In all of the reverse engineering I've done, status mode 3 is a pre-unlocked engineering device and status 1 is just plain unlocked. Even my Moto 360 (unlocked) shows status 1.
EDIT: Now that I look back at the photo, these devices are more than just "unlocked". They have secure boot off, which means that it would be possible for someone to flash a custom bootloader if they wanted to. Unless, however, I am mistaken, which is entirely possible.
EDIT 2: Oops, looks like 1 and 3 are both unlocked with no distinct difference between the two.
r3pwn said:
I think you might be mistaken. In all of the reverse engineering I've done, status mode 3 is a pre-unlocked engineering device and status 1 is just plain unlocked.
Click to expand...
Click to collapse
Status Code 3 is the unlocked state on both of my Moto X 2013 and my N6. When I relocked my N6, it goes to Status code 2 locked.
However, now that I checked my Verizon Moto X 2014 (which has never been unlocked before) it is Status Code 0 Locked.
So I believe that Status Code 1 is the factory state of unlocked and never been locked before. I will edit my earlier post but the bottom line in all of this is that this was not done by a developer - these devices were "taken" from the factory in China before they were locked.
---------- Post added at 05:10 PM ---------- Previous post was at 05:04 PM ----------
sd_matto said:
I know that you cannot post a link to the sale item (xda rules). But, can you provide detailed instructions on how someone like me could find it via searching on taobao?
Great find, and thanks in advance.
Click to expand...
Click to collapse
Are you sure these phones are not on the global blacklist?
---------- Post added at 05:15 PM ---------- Previous post was at 05:10 PM ----------
r3pwn said:
EDIT: Now that I look back at the photo, these devices are more than just "unlocked". They have secure boot off, which means that it would be possible for someone to flash a custom bootloader if they wanted to. Unless, however, I am mistaken, which is entirely possible.
Click to expand...
Click to collapse
I believe these devices were "taken" from the Chinese factory. They are referred to as factory devices on Tao Bao. I believe they are newly manufactured and have never been locked before and are "taken" from the factory before they are locked down.
r3pwn said:
EDIT 2: Oops, looks like 1 and 3 are both unlocked with no distinct difference between the two.
Click to expand...
Click to collapse
There is a difference b/t Status Code 1 Unlocked and Status Code 3 Unlocked. Status Code 3 Unlocked means the phone was locked at the factory and then you executed the fastboot oem unlock command to unlock it. Status Code 1 Unlocked means that they were never locked at the factory.
Feel free to speculate how these "factory" devices as they are referred to on Tao Bao were removed from the factory
Final verdict: Will this help us verizon usa folks towards the ultimate achievement on unlocking the bootloader?
I mean it would be awesome to get one with an unlocked bootloader but I mean. They were probably "taken" from the factory. Additionally at that point instead of getting another turbo, might as well just buy a phone like the Nexus 6 which has a ton of development for it.
nflwideout86 said:
Final verdict: Will this help us verizon usa folks towards the ultimate achievement on unlocking the bootloader?
Click to expand...
Click to collapse
I don't think so b/c I don't think this was done by someone who found an exploit.
---------- Post added at 06:24 PM ---------- Previous post was at 06:19 PM ----------
Harry44 said:
Additionally at that point instead of getting another turbo, might as well just buy a phone like the Nexus 6 which has a ton of development for it.
Click to expand...
Click to collapse
Well I certainly wouldn't be buying one of these factory devices, but I also found the N6 was really too large for me to use as my daily driver not to mention the issues with the battery life compared to the DT. So there are plenty of reasons to choose the DT over the N6 for many people
The N6 is a nice phone, don't get me wrong, but its size makes it less appealing for many people. I really hate the fact that my Moto X 2014 is so locked down, but it is a much better choice for me to use as my daily driver.
Harry44 said:
I mean it would be awesome to get one with an unlocked bootloader but I mean. They were probably "taken" from the factory. Additionally at that point instead of getting another turbo, might as well just buy a phone like the Nexus 6 which has a ton of development for it.
Click to expand...
Click to collapse
nflwideout86 said:
Final verdict: Will this help us verizon usa folks towards the ultimate achievement on unlocking the bootloader?
Click to expand...
Click to collapse
JulesJam said:
I don't think so b/c I don't think this was done by someone who found an exploit.
---------- Post added at 06:24 PM ---------- Previous post was at 06:19 PM ----------
Well I certainly wouldn't be buying one of these factory devices, but I also found the N6 was really too large for me to use as my daily driver not to mention the issues with the battery life compared to the DT. So there are plenty of reasons to choose the DT over the N6 for many people
The N6 is a nice phone, don't get me wrong, but its size makes it less appealing for many people. I really hate the fact that my Moto X 2014 is so locked down, but it is a much better choice for me to use as my daily driver.
Click to expand...
Click to collapse
(Replying to all)
No, taking the files from one of these devices wouldn't help us at all. The system image may be of interest, but I have one and haven't had a chance to dig through it yet. Stupid Windows won't mount it because it's an EXT4 partition dump.
I would buy one of these. @chrisjenho could you PM me some info on how to find this? I tried searching for Droid Turbo Unlocked, or Bootloader but could not find the item. Thanks
[SIZE=+2]This thread has been created for Questions & Answers/Troubleshooting[/SIZE] [SIZE=+2]Specific to[/SIZE]
Verizon Droid Turbo 2 XT1585
Mexican Moto X Force XT1580
Brasil Moto X Force XT1580
China Moto X Force XT1581
UK Moto X Force XT1580 N
Please feel free to share issues, questions and offer help. Noob questions are welcomed. It is always best to use the Thanks button , in lieu of simply posting "Thank you".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please keep discussion focused, on questions pertaining to this Device
List of supporters... ... ... ...To those seeking help: Please don't bombard the supporters with PMs asking for help. Instead, ask your question here in the thread so others can benefit from the solution to your problem as well. If you want to be sure someone particular gets notified of your question, put his / her username directly after an @. If you have ROM related questions, post in the relevant ROM Q&A thread (if there is one) or directly in the ROM development thread. Thank you! Supporters: If you want to be put on or off the list, just make a request here in the thread! Before posting anything, I strongly advise you to read
Forum Rules
[GUIDE] - XDA New User Guide - Getting started on XDA
XDA Tour
FAQs for Device Thread link
Index for Device Thread Link
Please look for a similar thread when visiting another device forum. If you would like to create a [Help Thread] please Click Here.
save
as you can remove the message the sim is not verizon.
Enviado desde mi XT1585 mediante Tapatalk
Bricked my XT1580 UK N
Hey XDA Developers
I admit i am an idiot!
I tried to root my XT1580 with a tutorial (not able to post link) and of course i bricked my phone big time. Is there a nice developer wich would try to help me flash a stock rom to my phone and hopefully make it boot again?
I used: twrp-2.8.7.0-kinzie.img
And SuperSU v2.65
I now downloaded Stock Marshmallow 6.0.0 /// XT1580_KINZIE_RETMX_DS_6.0_MPK24.78-8_cid12_subsidy-DEFAULT_CFC.xml.zip as i tought this would be the fiting stock rom for this device and region i live (Switzerland) but i am not very shure how to do it and i just dont want to destroy my belved xt1580 more than it allready is.
I am happy for any response.
Best Regards
Luschikofski said:
Hey XDA Developers
I admit i am an idiot!
I tried to root my XT1580 with a tutorial (not able to post link) and of course i bricked my phone big time. Is there a nice developer wich would try to help me flash a stock rom to my phone and hopefully make it boot again?
I used: twrp-2.8.7.0-kinzie.img
And SuperSU v2.65
I now downloaded Stock Marshmallow 6.0.0 /// XT1580_KINZIE_RETMX_DS_6.0_MPK24.78-8_cid12_subsidy-DEFAULT_CFC.xml.zip as i tought this would be the fiting stock rom for this device and region i live (Switzerland) but i am not very shure how to do it and i just dont want to destroy my belved xt1580 more than it allready is.
I am happy for any response.
Best Regards
Click to expand...
Click to collapse
you flashed twrp?
you were able boot twrp?
Sent from my DROID Turbo using XDA Labs
sd_shadow said:
you flashed twrp?
you were able boot twrp?
Sent from my DROID Turbo using XDA Labs
Click to expand...
Click to collapse
Hey sd_Shadow!
Thanks for your reply.
Yes, i was (and still am) able to boot TWRP. But thats not a big deal in my eyes. I am not the first one who have this done. Was easy.
br
Luschikofski said:
Hey sd_Shadow!
Thanks for your reply.
Yes, i was (and still am) able to boot TWRP. But thats not a big deal in my eyes. I am not the first one who have this done. Was easy.
br
Click to expand...
Click to collapse
yes, just trying to understand the nature of the problem
you installed Supersu.zip and then...
Sent from my DROID Turbo using Tapatalk
sd_shadow said:
yes, just trying to understand the nature of the problem
you installed Supersu.zip and then...
Sent from my DROID Turbo using Tapatalk
Click to expand...
Click to collapse
Aaah okay
yes, i then installed SuperSU. Went well, without errors. After that i reboot the phone as described in the tutorial. Now my XT1580 wont boot anymore. it is just stuck on the first boot image (Moto sign)
i tried with the same again and one time more with a difference version of TWRP and SuperSU. still no change
Luschikofski said:
Aaah okay
yes, i then installed SuperSU. Went well, without errors. After that i reboot the phone as described in the tutorial. Now my XT1580 wont boot anymore. it is just stuck on the first boot image (Moto sign)
i tried with the same again and one time more with a difference version of TWRP and SuperSU. still no change
Click to expand...
Click to collapse
I would try wiping the caches in twrp
Sent from my DROID Turbo using Tapatalk
sd_shadow said:
I would try wiping the caches in twrp
Sent from my DROID Turbo using Tapatalk
Click to expand...
Click to collapse
You mean wipe dalvik cache ? Did allready. No change I can try again as soon as i arrive at home
Luschikofski said:
You mean wipe dalvik cache ? Did allready. No change I can try again as soon as i arrive at home
Click to expand...
Click to collapse
http://www.theandroidsoul.com/marsh...ola-moto-x-force-droid-turbo-2-variant-88178/
there is nothing in this guide that should have caused any issues
Sent from my DROID Turbo using XDA Labs
maybe those twrp versions are not compatible?
if not should just be able to reflash stock recovery.img
Sent from my DROID Turbo using XDA Labs
sd_shadow said:
http://www.theandroidsoul.com/marsh...ola-moto-x-force-droid-turbo-2-variant-88178/
there is nothing in this guide that should have caused any issues
Sent from my DROID Turbo using XDA Labs
Click to expand...
Click to collapse
sd_shadow said:
maybe those twrp versions are not compatible?
if not should just be able to reflash stock recovery.img
Sent from my DROID Turbo using XDA Labs
Click to expand...
Click to collapse
i have to be honest. i have no idea about compatibility of twrp but I did a factory reset / Cache wipe in twrp. no change
I would really love to re-flash the stock recovery but i think its already obvious that there is now way i know how to do that Would it be possible for you to write a short step by step tut for this for me? Dont need to very detailed. I am a techie but not enough clue about where to get the right file
i would really appreciate
Luschikofski said:
i have to be honest. i have no idea about compatibility of twrp but I did a factory reset / Cache wipe in twrp. no change
I would really love to re-flash the stock recovery but i think its already obvious that there is now way i know how to do that Would it be possible for you to write a short step by step tut for this for me? Dont need to very detailed. I am a techie but not enough clue about where to get the right file
i would really appreciate
Click to expand...
Click to collapse
stock recovery.img would be flashed same as twrp.img
fastboot flash recovery.img
stock recovery.img is in the stock firmware xml.zip
just unzip
or just flash firmware with RSD Lite, just need to be sure that it's for your model, region and carrier.
I'm not sure how many options are available
Sent from my DROID Turbo using XDA Labs
sd_shadow said:
stock recovery.img would be flashed same as twrp.img
fastboot flash recovery.img
stock recovery.img is in the stock firmware xml.zip
just unzip
or just flash firmware with RSD Lite, just need to be sure that it's for your model, region and carrier.
I'm not sure how many options are available
Sent from my DROID Turbo using XDA Labs
Click to expand...
Click to collapse
Okay. I´ve tried with fastboot with no sucess. With RSD it starts and flashes until 20/29. It stops saying this:
on RSD: Failes flashing proces. 20/29 flash modem "NOH-HLOS.bin" -> Phone returned FAILS
On Phone it says: Image is too large
i was trying to dowload a rom from https://firmware.center:8081/firmware/Motorola/Moto X Force/Stock/XT1580/
but i am not shure wich ne to take. i tryed those with RETEU. Is this wrong? how do i find out wich rom is the right one?
br
Ive installed TWRP 3.0.2.0, then i backed up my stock android, then i installed cm13. And now, when i try to back up my cm13, i get error:
create tar fork error 255
and i cant add my log to post couse im new user(
Hi friends; is it possible to make a moto x force (vodafone), or any phone, no brand? please help me thanks
Hello,
I need some info on the chinese XT1581.
Is the bootloader unlockable? root? Are there any custom roms available for this device?
The only difference is the dual-sim?
Has anybody experience with this device?
Thanks!
I know I'm going to regret this and I probably already do so here goes:
I picked up a Motorola Droid Turbo 2 off craigslist tonight, traded another phone for it (LG Stylo 2 Plus) and everything was working fine during the actual meeting with the previous owner. He checked out the Stylo while I checked out the Turbo 2. Aside from scuffs and scrapes and whatnot I decided it was worth the trade - he said he was moving to Europe and just wouldn't need it anymore and he then showed me his Moto X Force (first time I'd ever seen one in person, verified it with the phone info, etc) and I figured what the hell, I'm good.
So he leaves, and me having not messed with a Verizon device for some time figured "Ok, I know all the Verizon devices are GSM unlocked from the factory since the summer of 2013 because of the FCC frequency auctions, no problem..." and then I power down and remove the T-Mobile nanoSIM from my Moto X 1st gen and power down the Turbo 2, etc, moving the nanoSIM over.
Power the Turbo 2 back up and of course I get the "SIM Card not from Verizon Wireless..." notification which I've seen in the past. I go into Settings and then set it for Global mode and... nothing, still doesn't work. Check the About phone info, it sees the nanoSIM, doesn't pull the APN data from the card so I put it in manually, still nothing. Reboot, still nothing, and so on and so forth.
I do some research and find out that Verizon - since some point in 2015 - now sells their devices technically unlocked for GSM operation but there's some funky network-specific lock on them for at least 1 year after the sale/purchase of the device so they guarantee they get something back on their investment. I called the previous owner, asked him what the deal was, he said he bought it December 1st 2015 and because he was moving that was that and it wasn't his problem anymore.
So yeah, I'm probably screwed on this for use with T-Mobile now but I figured I'd ask here anyway: not looking to rip anybody off but, I don't use Verizon, never have, never will, and I don't even know anyone that uses them either so I'm not sure how to proceed. In the good old days you could do the 4-corner trick and bypass the need to activate the phone with Verizon but obviously nothing is that simple anymore.
Is there any way to get this device up and running with T-Mobile since it should be unlocked? I called Verizon and they said because I'm not the original owner/purchaser (neither is the guy I got it from, apparently he got it used himself earlier this year) they won't provide me whatever info or method is required to make it truly GSM unlocked as it's supposed to be so I'm stuck there.
It's not blacklisted, at least that Verizon would tell me, nor stolen from what I gather - I checked the ESN against several sites like Swappa and CheckESNFree and it shows green/clear/ready for activation and yet it's just not happening.
Any advice or suggestions or straight out method to get past that aspect and make it work properly with T-Mobile is greatly appreciated if anyone can help.
If I end up using it as a Wi-Fi only device, so be it, but that wasn't the idea when I got it - my mistake was not doing research ahead of time on this new device. I've owned several Droid MAXX/Ultra/Mini smartphones - all Verizon devices of course - and never had to deal with this activation BS, I just put my T-Mobile SIM card in them and rebooted and wham, always worked without problems.
I should have known it wouldn't be that simple anymore.
br0adband said:
I know I'm going to regret this and I probably already do so here goes:
I picked up a Motorola Droid Turbo 2 off craigslist tonight, traded another phone for it (LG Stylo 2 Plus) and everything was working fine during the actual meeting with the previous owner. He checked out the Stylo while I checked out the Turbo 2. Aside from scuffs and scrapes and whatnot I decided it was worth the trade - he said he was moving to Europe and just wouldn't need it anymore and he then showed me his Moto X Force (first time I'd ever seen one in person, verified it with the phone info, etc) and I figured what the hell, I'm good.
So he leaves, and me having not messed with a Verizon device for some time figured "Ok, I know all the Verizon devices are GSM unlocked from the factory since the summer of 2013 because of the FCC frequency auctions, no problem..." and then I power down and remove the T-Mobile nanoSIM from my Moto X 1st gen and power down the Turbo 2, etc, moving the nanoSIM over.
Power the Turbo 2 back up and of course I get the "SIM Card not from Verizon Wireless..." notification which I've seen in the past. I go into Settings and then set it for Global mode and... nothing, still doesn't work. Check the About phone info, it sees the nanoSIM, doesn't pull the APN data from the card so I put it in manually, still nothing. Reboot, still nothing, and so on and so forth.
I do some research and find out that Verizon - since some point in 2015 - now sells their devices technically unlocked for GSM operation but there's some funky network-specific lock on them for at least 1 year after the sale/purchase of the device so they guarantee they get something back on their investment. I called the previous owner, asked him what the deal was, he said he bought it December 1st 2015 and because he was moving that was that and it wasn't his problem anymore.
So yeah, I'm probably screwed on this for use with T-Mobile now but I figured I'd ask here anyway: not looking to rip anybody off but, I don't use Verizon, never have, never will, and I don't even know anyone that uses them either so I'm not sure how to proceed. In the good old days you could do the 4-corner trick and bypass the need to activate the phone with Verizon but obviously nothing is that simple anymore.
Is there any way to get this device up and running with T-Mobile since it should be unlocked? I called Verizon and they said because I'm not the original owner/purchaser (neither is the guy I got it from, apparently he got it used himself earlier this year) they won't provide me whatever info or method is required to make it truly GSM unlocked as it's supposed to be so I'm stuck there.
It's not blacklisted, at least that Verizon would tell me, nor stolen from what I gather - I checked the ESN against several sites like Swappa and CheckESNFree and it shows green/clear/ready for activation and yet it's just not happening.
Any advice or suggestions or straight out method to get past that aspect and make it work properly with T-Mobile is greatly appreciated if anyone can help.
If I end up using it as a Wi-Fi only device, so be it, but that wasn't the idea when I got it - my mistake was not doing research ahead of time on this new device. I've owned several Droid MAXX/Ultra/Mini smartphones - all Verizon devices of course - and never had to deal with this activation BS, I just put my T-Mobile SIM card in them and rebooted and wham, always worked without problems.
I should have known it wouldn't be that simple anymore.
Click to expand...
Click to collapse
call Verizon, tell them the situation, worse case you waste some time on the phone
Sent from my sailfish using XDA Labs