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
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.
Hello, since i bought a Dev edition i noticed that there's no helpfull links to start with, so i though on making this thread to make other peoples life Easier.
Don't Forget to Thank All People of XDA on the Links on This Post, they deserve recognition for their help
Jaocagomez said:
First: Unlocking Bootloader
{
"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"
}
Once you got your Developer Edition Droid Maxx You'll have to unlock the Bootloader so you can flash recoveries, roms, themes and some other stuff. Remember that only in Dev edition you Don't lose your warranty if you unlock your bootloader.
Be careful, the process of unlocking your bootloader ERASES ALL YOUR DATA, so the first thing i recommend you to do is unlock your cellphone bootloader then use it.
To enter in fastboot mode with your phone off, press Power + Vol Down
Here's the Link to Unlock Your Bootloader: https://motorola-global-portal.cust...e/bootloader/unlock-your-device-a/action/auth
To get Fastboot on your pc you can Download Minimal Adb and Fastboot which is lighter and faster than downloading full android SDK.
Also a Tip, when copying your device id, paste each line on the field one after another, and dont put spaces, sometimes when you copy-paste your device id you left a space and it shows as error.
If everything went ok, you are now fully unlocked and ready for the party.
Click to expand...
Click to collapse
Jaocagomez said:
Second: Get a Custom Recovery
Custom Recoveries remplace the stock android recovery and the main use of this is to flash roms, themes, backup, restore and some other things, Flashable Roms are always a .Zip Format
Theres lots of recoveries and they have different advantages and fails, but most of them can do the work.
To install you'll need just one line on fastboot.
Here's a List of Recoveries That work on our Device:
TWRP. (its Moto x Forum, dont Worry)
Safestrap
Philz Touch (based on CWM advanced 6)
The most user friendly i know and the one i use is TWRP
Now, if you want to stay on stock Rom i Recommend installing Xposed and Gravity Box
Click to expand...
Click to collapse
Jaocagomez said:
Third: Root in TWRP
For me the fastest Metod to root is Entering TWRP your first time, then Just exit
and before you exit TWRP will ask to install SU, swype to your right to install and then boot your phone again.
update the app, and thats all you are rooted.
There are other metods but the one i post here for me is faster and easier. you can look on the forums for more metods.
Click to expand...
Click to collapse
Jaocagomez said:
Optional: Installing Xposed And Gravity Box
Xposed its an app that modifies the look and actions of your stock rom (or any rom) without the need to be flashing things, just by overriding on boot the stock files. Its pretty useful and Great for customization.
You can learn more about it Here and Here
iB4STiD from the Moto x Forum has a Flashable Xposed and Gravity Box Module, which is the easiest way to install it.
Just Download it and flash it on your recovery. after that, update the app and install the framework and reboot again, it should be working.
Click to expand...
Click to collapse
Jaocagomez said:
Fourth: Flashing Moto X Firmware.
Here comes the interesting Part, you can flash the Moto x Firmware and work with it.
the upside down? if you have a verizon sim card and flash a moto x tmobile firmware it will not work and so on, they are sim locked as it were a retail at&t/tmob/verizon device, so you are pretty much limited to flash the moto x verizon firmware and/or the sim card your carrier is. i currently dont know how to change that but i believe its posible.
the list of all the Moto x Firmware is here: http://sbf.droid-developers.org/phone.php?device=0
in order to flash these firmware you have to put all the contents of the firmware in the minimal adb folder and copy paste this commands to flash:
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot
just copy the code and paste it on the fastboot command line on your pc and you are all set.
it will boot as a moto x.
When you Install Moto X Firmware, soft keys will stop to work and you'll have on-screen keys just like moto x, in order to fix this you can flash this fixed framework-res by Skrilax_CZ and uploaded by Gundabolu SC on your recovery and you'll have a moto x firmware and soft keys working, that framework only works on android 4.4.
To come back to Droid Maxx Stock Verizon 4.4, download the Droid maxx firmware here: http://sbf.droid-developers.org/phone.php?device=4
put your phone on fastboot mode and
and run the flash_all.bat inside the .zip file, it will boot up again as a normal droid maxx.
If you do something wrong, your phone force closes, or you screw up, remember that you can always flash firmware back to Droid Maxx Stock Rom, so Dont worry.
Click to expand...
Click to collapse
Jaocagomez said:
Five: Installing Moto X Roms
You can install Moto X Roms, from moto x forum, just flash the required Moto X firmware, install a recovery then download the Rom .zip and finally to flash the rom on the recovery, and you are all set to enjoy a custom rom. oh dont forget the capacitive keys fix if you want your keys working.
Currently there is Kangakat, PAC, Eclipse, CM11, Gummy, Liquid smooth kitkat and some others, you can check them out here:
http://forum.xda-developers.com/moto-x/development
Click to expand...
Click to collapse
Jaocagomez said:
Six: Staying on Stock Verizon Rom
If you decided to stay on verizon's 4.4 stock rom, i recommend you to install Gravity box, change your status bar to white and install this moded Sistemui.apk by erishasnobattery so you stay as close as AOSP as you can.
you can also install the google now launcher located HERE for a closer look to a nexus 5
Or you can install my Debloated stock rom here: http://forum.xda-developers.com/showthread.php?t=2716824
Click to expand...
Click to collapse
Don't Forget to Thank All People of XDA on the Links on This Post, they deserve recognition for their help
Edit1:
Changed Thread name to accomodate Moto x, mini, ultra
Edit2:
Added Quotes to the steps to make reading easier.
Reserved
Thank you for this, i actually just finished going through all of this a few days ago and have gravity box and xposed going on the stock 4.4 Verizon Rom...
Do you have twrp and Safestrap going at the same time?
spiral777 said:
Thank you for this, i actually just finished going through all of this a few days ago and have gravity box and xposed going on the stock 4.4 Verizon Rom...
Do you have twrp and Safestrap going at the same time?
Click to expand...
Click to collapse
no, i dont use safestrap
SafeStrap is for "Locked" bootloader only..TWRP is for "UnLocked" bootloader..
sent by my 4.2.2_12.15.15
XT1080MDEV (aka) Droid Maxx DE
Please donate to: jcase & Hashcode (if you can)
My current setup with the modes system ui, Google now launcher and gravity box.
Sent from my XT1080 using Xparent BlueTapatalk 2
BladeRunner said:
My current setup with the modes system ui, Google now launcher and gravity box.
View attachment 2588597
Sent from my XT1080 using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Sweet setup.!!
sent by my 4.2.2_12.15.15
XT1080MDEV (aka) Droid Maxx DE
Please donate to: jcase & Hashcode (if you can)
BladeRunner said:
My current setup with the modes system ui, Google now launcher and gravity box.
View attachment 2588597
Sent from my XT1080 using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
thats the look!
ignore
Is anyone having issues with 4.4? i have read on the forums that it's better to stay with 4.2.2 camera fix. and that you can't downgrade after 4.4 ota.
I am looking for a do's and dont's from experienced DE users.
thanks
xkwwwx said:
Is anyone having issues with 4.4? i have read on the forums that it's better to stay with 4.2.2 camera fix. and that you can't downgrade after 4.4 ota.
I am looking for a do's and dont's from experienced DE users.
thanks
Click to expand...
Click to collapse
I, personally, haven't had any issues on 4.4 yet. You can downgrade the boot, system and recovery images as well as the modem, but the bootloader and gpt.bin stays on 4.4. If you DO decide to downgrade I would highly recommend freezing the OTA as there is a possibility of bricking the device if you take an OTA. If you downgrade to 12.7.7, the pre camera update, and try to take an update to 12.15.15 you WILL hard brick. I am unsure of what happens if you downgrade to 12.15.15 and update to KitKat.
Why is it saying my device does not qualify for device unlock?? this is really pissing me off
AshyKnuttz said:
Why is it saying my device does not qualify for device unlock?? this is really pissing me off
Click to expand...
Click to collapse
Sir..be absolutely sure there are no spaces in the line after you paste to the box..
sent by my 4.2.2_12.15.15
XT1080MDEV (aka) Droid Maxx DE
Please donate to: jcase & Hashcode (if you can)
NWKENT said:
Sir..be absolutely sure there are no spaces in the line after you paste to the box..
sent by my 4.2.2_12.15.15
XT1080MDEV (aka) Droid Maxx DE
Please donate to: jcase & Hashcode (if you can)
Click to expand...
Click to collapse
i did, i even copied and pasted one line at the time to make sure there were no spaces
AshyKnuttz said:
i did, i even copied and pasted one line at the time to make sure there were no spaces
Click to expand...
Click to collapse
Be sure there is no space in the very front of the line also..
Also..is your device new out of the box.? Maybe you will need to call Motorola.?
sent by my 4.2.2_12.15.15
XT1080MDEV (aka) Droid Maxx DE
Please donate to: jcase & Hashcode (if you can)
AshyKnuttz said:
i did, i even copied and pasted one line at the time to make sure there were no spaces
Click to expand...
Click to collapse
double check that, happened to me too try to write it over
NWKENT said:
Be sure there is no space in the very front of the line also..
Also..is your device new out of the box.? Maybe you will need to call Motorola.?
sent by my 4.2.2_12.15.15
XT1080MDEV (aka) Droid Maxx DE
Please donate to: jcase & Hashcode (if you can)
Click to expand...
Click to collapse
I just typed it out number/letter by number/letter so its not spaces. it is fresh out of the box, i just got it earlier today
AshyKnuttz said:
I just typed it out number/letter by number/letter so its not spaces. it is fresh out of the box, i just got it earlier today
Click to expand...
Click to collapse
Sir..did you manage "Unlock".. what has been your path, results.?
I found that copy/paste worked really well..then after paste, go to the box and carefully delete any space..even in front, delete that space also..
I mention this eventhow you may have yours Unlocked..So others will see the correct procedure when pasting to the site box..and avoid troubles (possibly)..
sent by my 4.3_14.14.14
XT1028 (aka) Moto-G
Please donate to: jcase & Hashcode (if you can)
NWKENT said:
Sir..did you manage "Unlock".. what has been your path, results.?
I found that copy/paste worked really well..then after paste, go to the box and carefully delete any space..even in front, delete that space also..
I mention this eventhow you may have yours Unlocked..So others will see the correct procedure when pasting to the site box..and avoid troubles (possibly)..
sent by my 4.3_14.14.14
XT1028 (aka) Moto-G
Please donate to: jcase & Hashcode (if you can)
Click to expand...
Click to collapse
yes sir --right where i want to be thanks to you jcase and hashcode! thanks to all!!
NWKENT said:
Sir..did you manage "Unlock".. what has been your path, results.?
I found that copy/paste worked really well..then after paste, go to the box and carefully delete any space..even in front, delete that space also..
I mention this eventhow you may have yours Unlocked..So others will see the correct procedure when pasting to the site box..and avoid troubles (possibly)..
sent by my 4.3_14.14.14
XT1028 (aka) Moto-G
Please donate to: jcase & Hashcode (if you can)
Click to expand...
Click to collapse
I talked to online costumer support Thursday night, and they set me up with a ticket for the "level 2" technicians. I was going to call yesterday but couldn't because of work. Then, just now this morning, I tried again, same key, just copy and paste, and it worked. I can only assume it didn't work at first because I had just received and activated the phone earlier that day, it must take some time before it registers in their system or something.
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
[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
HI,
While in the process of resetting my phone, I checked for update and was informed of a new download. After installing it, the software version is now L720VPSGPL1. I googled this but nothing came up. Anyone else getting this update? I'm in the U.S. if that makes any difference.
Thanks
L720vpsgpl1
JHXDA said:
HI,
While in the process of resetting my phone, I checked for update and was informed of a new download. After installing it, the software version is now L720VPSGPL1. I googled this but nothing came up. Anyone else getting this update? I'm in the U.S. if that makes any difference.
Thanks
Click to expand...
Click to collapse
HI,
I'm from Russia, I also received an update to version L720VPSGPL1
Sorry for my English
Found a link through Bing but not sure who operates this site:
http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=SPH-L720
I received it too last week and posted in the rdf forum. I too haven't been able to find any info about it with. Sprint hasn't posted a change log either.
Update is available, but the update failed because apparently something changed my build.prop. Anyone know where to find unmodified files from the original version?
Is this version rootable? If updating a rooted phone, does it unroot?
GnatGoSplat said:
Update is available, but the update failed because apparently something changed my build.prop. Anyone know where to find unmodified files from the original version?
Is this version rootable? If updating a rooted phone, does it unroot?
Click to expand...
Click to collapse
It will fail and possibly brick your phone if you try to update with a modified system (root, custom recovery, etc). Download the OK3 tar from www.sammobile.com and flash with Odin. Then you can update to PL1. From what I've seen it's only a security update.
{
"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"
}
bilgerryan said:
It will fail and possibly brick your phone if you try to update with a modified system (root, custom recovery, etc). Download the OK3 tar from www.sammobile.com and flash with Odin. Then you can update to PL1. From what I've seen it's only a security update.
Click to expand...
Click to collapse
Will I be able to re-root? Anyone try it?
GnatGoSplat said:
Will I be able to re-root? Anyone try it?
Click to expand...
Click to collapse
Yes. Same root method as previous versions.
I've been searching around a bit, anyone know off top of head what the newest (available) modem is to download standalone?
bilgerryan said:
It will fail and possibly brick your phone if you try to update with a modified system (root, custom recovery, etc). Download the OK3 tar from www.sammobile.com and flash with Odin. Then you can update to PL1. From what I've seen it's only a security update.
Click to expand...
Click to collapse
Managed to dump an unmodified build.prop from stock ROM. Did a hex compare to mine, only difference is 2 hex bytes appended, 0A 0A. I guess some app that needed root modified my build.prop and when I uninstalled it, it changed it back but not cleanly. Anyway, copied clean build.prop to /system, then let the phone update and it succeeded. Figured it wouldn't hurt anything as I could re-flash with Odin if it bricked. Lucked out and phone update succeeded. Now on PL1 and didn't even lose root.
My wife is traveling to Russia in about 2 weeks. Wanted to UNLOCK the phone so she can buy a local SIM card and use her phone while visiting. Called Sprint and they said they unlocked phone, but not sure how to tell what (if anything) changed.
Is there a method to SIM unlock (and/or carrier unlock) with the PL1 baseband software?
1BadBoy said:
My wife is traveling to Russia in about 2 weeks. Wanted to UNLOCK the phone so she can buy a local SIM card and use her phone while visiting. Called Sprint and they said they unlocked phone, but not sure how to tell what (if anything) changed.
Is there a method to SIM unlock (and/or carrier unlock) with the PL1 baseband software?
Click to expand...
Click to collapse
There is a program called GTUpdate2_v3.1.8.apk that can unlock PL1 on a rooted phone. I think it's not a free software, but someone posted a link to it on the forums once.
I think without root, the program should at least tell you if the phone is unlocked.
GnatGoSplat said:
There is a program called GTUpdate2_v3.1.8.apk that can unlock PL1 on a rooted phone. I think it's not a free software, but someone posted a link to it on the forums once.
I think without root, the program should at least tell you if the phone is unlocked.
Click to expand...
Click to collapse
It might be hard to find as the developer has asked all links to it be taken down.
Got root using cf auto root and confirmed it with root checker and busy box. Also installed twrp through the twrp app and no brick yet. Don't know which rom I can install yet. It's been a while since I've rooted and romed a phone. Kinda forgot how that works, well not the flashing the rom part but if this Pl1 firmware will cause problems with a rom I flash lol . Any help is appreciated. Thanks in advance
schemppjr37 said:
Got root using cf auto root and confirmed it with root checker and busy box. Also installed twrp through the twrp app and no brick yet. Don't know which rom I can install yet. It's been a while since I've rooted and romed a phone. Kinda forgot how that works, well not the flashing the rom part but if this Pl1 firmware will cause problems with a rom I flash lol . Any help is appreciated. Thanks in advance
Click to expand...
Click to collapse
The only ROM I know for sure that works with PL1 is mine... Wicked X.
bilgerryan said:
The only ROM I know for sure that works with PL1 is mine... Wicked X.
Click to expand...
Click to collapse
I could not find the application, and when my wife got there, she's getting an "Invalid SIM" message on her phone. So she's going to buy a phone to use while there. Thanks for all the help in this thread!
Can anyone tell me where I can find current instructions to ROOT my Sprint Galaxy S4? It currently has the updated software (L720VPSGPL1). What I've found seems to be outdated.
I would also like to ROM using the Wicked. Sounds like it's clean and fast.
1BadBoy said:
I could not find the application, and when my wife got there, she's getting an "Invalid SIM" message on her phone. So she's going to buy a phone to use while there. Thanks for all the help in this thread!
Can anyone tell me where I can find current instructions to ROOT my Sprint Galaxy S4? It currently has the updated software (L720VPSGPL1). What I've found seems to be outdated.
I would also like to ROM using the Wicked. Sounds like it's clean and fast.
Click to expand...
Click to collapse
Odin TWRP .tar file for L720 from https://twrp.me then flash ROM or SuperSU zip from Chainfire's website (ROM is already rooted) in TWRP recovery.
bilgerryan said:
The only ROM I know for sure that works with PL1 is mine... Wicked X.
Click to expand...
Click to collapse
I did try your rom 1st and I got bootlooped. Have been running resection 6.0 rom and haven't had any issues yet. I will try yours again. Not sure if I saw 2 versions of it or not, but if I did which one should I try. I like switching things up from time to time, but I used to like having at least 2 properly functioning roms saved to my phone incase. TIA
schemppjr37 said:
I did try your rom 1st and I got bootlooped. Have been running resection 6.0 rom and haven't had any issues yet. I will try yours again. Not sure if I saw 2 versions of it or not, but if I did which one should I try. I like switching things up from time to time, but I used to like having at least 2 properly functioning roms saved to my phone incase. TIA
Click to expand...
Click to collapse
v11.0 is just a small update, so you have to flash the full ROM first which is V10.9. There is also the Bare Bones version which is just super debloated.
I'm confused on the versioning. Alphabetically, VPS comes before VPU, so I was thinking that "VPSGPL1" was older. Obviously versioning rules come fast & loose, but I'm curious what the VPS indicates that is different from VPU.
So then is this the correct order for different modems?
Code:
L720VPUFNAE
L720VPUGOD2
L720VPUGOK3
L720VPSGPL1