This walks through the process of rooting a Motorola Milestone X2 running 2.3.6. First off I DID NOT come up with this solution nor did I initially post this in this thread. Many many MANY thanks to all those helped make this a reality (which seem to be Brandon15811, the2dcour, and eval-!) and to Sippi4x4man who posted this information here along with DarkFalconX who posted an addendum to help get it working, and to Tiso who made me aware someone had posted this in the thread. See the bottom for the original links that were posted.
This is the process I used it is slightly different than Dark's and the original link. The standard warning applies here, NEITHER MYSELF NOR ANYONE ELSE IS RESPONSIBLE IF YOU BRICK YOUR PHONE DOING THIS!
PREREQUISITES
You MUST have the ADB drivers for your phone installed which are obtained as part of the Android SDK.
You MUST have USB Debugging enabled on your phone.
You MUST have Superuser installed, which can be found on the Market.
PROCESS
Download the following file (atrix-4g-moto-fastboot-win32.zip): LINK
Extract the zip file to a location that is easy to get to, the original instructions suggested making a Root folder in C:\, however it is really up to you. Just make sure all the files are extracted to the same folder.
Get your phone into Fastboot mode, to do this:
Shut the phone off.
Hold down the Volume Down Button while pressing the Power Button.
After the phone turns on you should see Fastboot at the top of the screen.
Press the Volume Up Button to enter Fastboot mode. Your computer may need to install drivers if this is the first time you entered Fastboot mode, so let this happen BEFORE proceeding.
Start a command prompt on your computer.
Type the following commands:
cd \<DIRECTORY> where <DIRECTORY> is the folder you created. If you created the Root folder in C:\ it would be cd \root.
moto-fastboot flash preinstall preinstall.img
moto-fastboot reboot
Wait for the phone to reboot, once it does so execute the following commands (in the command prompt you should still have open):
adb shell
/preinstall/su
On your phone you should see a prompt to Allow or Deny Superuser access, allow this. Then execute the following commands (in the command prompt you should still have open)
mount -o rw,remount -t ext3 /dev/block/mmcblk0p12 /system
cp /preinstall/su /system/bin/su
chmod 6755 /system/bin/su
Initial links Posted by Sippi4x4man
http://www.xda-developers.com/androi...orola-atrix-2/
http://briefmobile.com/motorola-atrix-4g-root
Closing
I have to again thank everyone who created this process and who made people aware of this. I take ZERO credit I am simply reposting information others have already posted. Have fun!
UPDATES
09/04/2012 - The links for the files were broken, the files needed to root the Atrix 4G are the same as we need so I have updated the link to those used for that, along with tweaking the instructions a bit to match. Thanks to Carl Parker and this post here for the working link. Do not worry that the files are labeled "for" the Atrix 4G, the files do in fact work for rooting the Milestone X2 I just used them successfully.
09/05/2012 - I modified the instructions to flash preinstall.img versus root.img, thanks to aldude999 and sd_shadow for pointing out the error as well as sd_shadow for the new link.
I also need to make sure I give credit where credit is due, skwoodwiva and mastafunk have been extremely helpful in trying to figure out a solution for my phone. I can't thank you guys enough, I apologize in the fact that I didn't see the personal messages before I let my phone update OTA to 2.3.6. If anything I hope if I can provide the OTA update I can help the community figure some stuff out as frankly I don't have the knowledge. Thanks again guys.
HELP!!!
The same thing happened to my provider. I got a 2.3.6 up date and I was thinking as it was downloading.... crap I am not going to have root access. I have tried several ways. I have tried Superoneclick, the zerg method and I have also tried some other odd ways. PLEASE HELP US FIGURE THIS OUT!!!!! Maybe this will help with other problems with some of the roms I also wanted to add that I have the SBF and I tried to go back to 2.3.5 and it fails. Which means I am stuck with 2.3.6 >.< ANGRY MOOGLE.... ANGGGEERRRR Motorola unlock your bootloader!!!
Sorry for the bad news. I do wish voodoo rootkeeper was was given more credit in this forum as it may have saved you in spite of it's (TO BE NOTED) problems with one custom rom, eclipse. Thanks for the recognition
---------- Post added at 10:33 PM ---------- Previous post was at 09:56 PM ----------
Did the ud negotiation give an option to dl only? tw... where did you get the sbf? Care to post it? Also give details about the rsd failure I assume you used rsd mode down rocker up rocker...
---------- Post added at 11:16 PM ---------- Previous post was at 10:33 PM ----------
Clcrawl so you saved the ota while still on 235. Drama! Man. Post it or send it to me. Change the .zip to mp3 if you have trouble on phone, boat and es file expl used to work w/ multiupload. My last ota ul would not w/ those so I opera'ed a mp3.
i can not post the sbg . It is from ntelos. It has the 2.3.5 build from Daytona. Bassically what happens the phone I phone freezes when I try to reload the sbf. Then rsd fails. I do put the phone in RSd mode and then connect it. Is there something I am missing?
Development forum top sticky sbf tutorial
The problem with OTA root keeper it's that apparently it doesn't place superuser apk back into system properly. So when we all tried to flash eclipse it couldn't set permission correctly inn superuser apk.
it wasn't allowing the system to write to the root files of the ROM.
so basically it blocked itself.
((ooh....and I didn't figure this out lol....me an nitro had a conversation bout it....he figured out I believe while trying to mess with three razr and it's OTA update)
Which roms are effected?
skwoodwiva said:
Which roms are effected?
Click to expand...
Click to collapse
Pretty sure all of them.
Since don't they all include superuser apk and binaries in the updater scripts?
A work around would be to remove superuser things from the script and then after ROM install use root keeper again to restore superuser.
Easier to just use zergrush IMO
That is at least until we run of ways to obtain root on OTA lol
Whoa....... wait.. there is a X2 2.3.6 OTA dropping down?!?
lordforex said:
Whoa....... wait.. there is a X2 2.3.6 OTA dropping down?!?
Click to expand...
Click to collapse
Milestone x2
Not our x2
ashclepdia said:
Milestone x2
Not our x2
Click to expand...
Click to collapse
Ouch... missed that part. lol
Motorola Milestone X2 OTA 2.3.6 Link
For those interested, here is a link to the Motorola Milestone X2 2.3.6 OTA Update:
http://www.multiupload.com/6L3UU9P28J
Many thanks if anyone can help me get root back, at the very least I was able to Freeze Apps to make the phone far more responsive. This is what happens when you get drunk and are playing with your phone, you let an OTA update get applied ;-).
I am in the same boat with my Milestone X2 (Bluegrass Cellular). Had root at 2.3.5 with a variant of zergrush. Lost it with an OTA I let slip through (2.3.6). No method has had any luck fixing it (Hellion blue flames message on zergrush). If anyone comes up with a fix, please post it. Thanks.
I have a Milestone X2 on Ntelos. Seen some people rooting with 2.3.5, any ideas on how? Read posts on one way that had worked with others but could never get it to work with mine.
Manula Root Method
Scroll to the bottom of the OP and look for the Manual Root Method stated there. Have you guys tried this?
Has anyone tried the D3 1 click rather than zerg rush. It's older but I havent heard of it breaking yet.
This did not work. I tried the commands by hand the point where you do the following you are getting permission denied so I presume the exploit is supposed to happen before it when you are creating a symlink (ln -s):
$ mv /data/local.prop /data/local.prop.bak
mv /data/local.prop /data/local.prop.bak
failed on '/data/local.prop' - Permission denied
$
After that is is all fail. So I guess previously moving the 12m file or whatever it is, removing it and then moving it back created the exploit?
aceoyame said:
Has anyone tried the D3 1 click rather than zerg rush. It's older but I havent heard of it breaking yet.
Click to expand...
Click to collapse
Pete's fails to give you temp root unfortunately so it fails. Which is effectively what the manual instructions are from what I can tell. We just need some exploit to offer temp root via ADB and then you can get su in place and it is over. It appears the only thing that worked in 2.3.5 was Zerg and the "fixed" that. If anyone knows how the developer of Zerg is I would love to talk to them to see what exactly was being exploited.
Peperm1nt said:
Manula Root Method
Scroll to the bottom of the OP and look for the Manual Root Method stated there. Have you guys tried this?
Click to expand...
Click to collapse
I'd like to sign this petition too...
I'm glad to see some people talking about this! Just moved to this phone from an HTC desire and while I love the screen size & internal memory it has been quite a blow to move from cyanogenmod 7 to the slow jerky OS that this appears to have - after all it was touted as being faster! And there is no way for me to get root because right from the store I got 2.3.6. I've tried a couple of exploits including the zergrush one, and doing it manually via adb as mentioned already in this thread. I'd lover to get some help with this!
Also, what is the difference between the Droid x2 and the milestone x2? I have searched but have not found... Other than that updates get rolled out at different times perhaps.
- Jon
Related
I used doomloords zergrush root method on my DX2 on 2.3.4. It ran through the steps seemingly well and rebooted like it should. Upon boot there was no super user and It tested negative for root? So I tried runnin the program again, and when I "press any key" all of the steps show up instantly like it was just showing what had already been done. Then I thought I would just try runnin the unroot and all the steps were there popped up instantly too. Every time I run through the root method nothing happens now, and I don't have superuser? Uhhhh...i need to get rooted soon!!!
xCaptivateRx said:
I used doomloords zergrush root method on my DX2 on 2.3.4. It ran through the steps seemingly well and rebooted like it should. Upon boot there was no super user and It tested negative for root? So I tried runnin the program again, and when I "press any key" all of the steps show up instantly like it was just showing what had already been done. Then I thought I would just try runnin the unroot and all the steps were there popped up instantly too. Every time I run through the root method nothing happens now, and I don't have superuser? Uhhhh...i need to get rooted soon!!!
Click to expand...
Click to collapse
Try Petes Motorola root tool worked for me with 2.3.4. I also had problems with zergrush. Same problems as you everything said it was good to go but it wasnt
kevinv20 said:
Try Petes Motorola root tool worked for me with 2.3.4. I also had problems with zergrush. Same problems as you everything said it was good to go but it wasnt
Click to expand...
Click to collapse
Thanks...wanna link me?
http://forum.xda-developers.com/showthread.php?t=1198857&page=482
Read page 482 to help troubleshoot zergrush. It works great only one reboot I use it all the time. Good luck I think these tips from Ash will vet you there.
I highly doubt it makes a difference but, I used Zergrush on 2.3.5 and it worked flawlessly. On 2.3.4 I used Motorola One Click Root and it worked fine. If it gives you a hard time still and you want to try what I did, let me know. I think I still have the files saved somewhere.
tallyforeman said:
I highly doubt it makes a difference but, I used Zergrush on 2.3.5 and it worked flawlessly. On 2.3.4 I used Motorola One Click Root and it worked fine. If it gives you a hard time still and you want to try what I did, let me know. I think I still have the files saved somewhere.
Click to expand...
Click to collapse
I use it on 2.3.4 everytime with no issues.
Travisdroidx2 said:
I use it on 2.3.4 everytime with no issues.
Click to expand...
Click to collapse
Kewl. I didn't think it did. It was really easy. Never heard of any problems with it until now.
in windows 7, zerg fails everytime, for me
but in linux (ezSBF) works fine
Sent from my DROID X2 using xda premium
Must of gave myself bad luck. Last night is first time I had problems with zergrush. Had to use Pete's one click. I have used zergeush over 10 times with no issues. And I ran out of time to troubleshoot the problem.
tallyforeman said:
I highly doubt it makes a difference but, I used Zergrush on 2.3.5 and it worked flawlessly. On 2.3.4 I used Motorola One Click Root and it worked fine. If it gives you a hard time still and you want to try what I did, let me know. I think I still have the files saved somewhere.
Click to expand...
Click to collapse
Would you send me the motorola one click root? Since I'm still on 2.3.4 and zergrush continues to fail...is there an OTA 2.3.5?! When did that come out because it's still not available on my phone..
HowTo: Root your Motorola Droid X2
http://forum.xda-developers.com/showthread.php?t=1315711
2.3.5 update leak file
http://rootzwiki.com/topic/18181-235-update-leak-file/
edit: motorola one click root is same as Pete's root tools, and droid 3 one click
I've been using [TOOL] ezSBF DX2 with zergrush
http://www.droidxforums.com/forum/droid-x2-hacks/41697-tool-ezsbf-dx2.html
let's see if I can work magic again
zergrush works perfectly well with rooting,2.3.4 AS WELL AS 2.3.5
so since you got thru the whole script and it didn't error on ya, I'm thinking you may have forgot to check the unknown sources box in settings>applications on you x2
try this
first turn it on(while your in there, might as well give the debugging setting a toggle off/on, make sure debugging is ON before exiting and starting zergrush)
try the script again
if it hits through the script with no errors but you still don't see superuser
then go into the play store, install superuser , AND get a busybox installer and see if you can manually install that way
then reboot and see if you can use a root capable app
let me know if this works if you try it please
ashclepdia said:
let's see if I can work magic again
zergrush works perfectly well with rooting,2.3.4 AS WELL AS 2.3.5
so since you got thru the whole script and it didn't error on ya, I'm thinking you may have forgot to check the unknown sources box in settings>applications on you x2
try this
first turn it on(while your in there, might as well give the debugging setting a toggle off/on, make sure debugging is ON before exiting and starting zergrush)
try the script again
if it hits through the script with no errors but you still don't see superuser
then go into the play store, install superuser , AND get a busybox installer and see if you can manually install that way
then reboot and see if you can use a root capable app
let me know if this works if you try it please
Click to expand...
Click to collapse
It doesn't even run through the script. The entire script just pops up from my previous try. I'll try the busy box installer...
you did unzip the zergrush package before running the script correct?
you should have done a right click extract all/decompress here (depending on what zip tool used)
D'UHHHHHHH
ashclepdia said:
you did unzip the zergrush package before running the script correct?
you should have done a right click extract all/decompress here (depending on what zip tool used)
Click to expand...
Click to collapse
How did i forget to try that?
Lol, I GOT ROOOTTTTEEEEEED!!!
But i noticed during the root script (by the way i used zergrush v4) is said something along the lines of:
not enough space in /system/
freeing up space in /system/ by removing google maps
and upon reboot, i still had my icon but when i clicked on it is just kept saying loading for an extremely long time... so i started deleting all the apps i never use. then i got a notification that said "updated to newest version" so did zergrush just remove the updates for it to make room? then when i had freed up space i got it back? because i dont want to get into removing bloatware...or anything that could cause bricking. because i bricked my LG ally (no dev for those phones) and cant afford to lose my droid. lol, just rooted for wifi tethering! thanks ash, travis, and everyone else! but do you recommend i install CWM for safety??
xCaptivateRx said:
How did i forget to try that?
Lol, I GOT ROOOTTTTEEEEEED!!!
But i noticed during the root script (by the way i used zergrush v4) is said something along the lines of:
not enough space in /system/
freeing up space in /system/ by removing google maps
and upon reboot, i still had my icon but when i clicked on it is just kept saying loading for an extremely long time... so i started deleting all the apps i never use. then i got a notification that said "updated to newest version" so did zergrush just remove the updates for it to make room? then when i had freed up space i got it back? because i dont want to get into removing bloatware...or anything that could cause bricking. because i bricked my LG ally (no dev for those phones) and cant afford to lose my droid. lol, just rooted for wifi tethering! thanks ash, travis, and everyone else! but do you recommend i install CWM for safety??
Click to expand...
Click to collapse
you are fine
I recommend installing our BSR, don't install,cwm from,ROM manager or anything
there is links floating inn or forum, check the sticky made by booked or moonshadow for correct apk
then make,a nandroid backup.
and don't worry
if you remove any bloatware apks that won't be enough to hard brick ya, if anything dies wrong from removing boat apps all you need to do is flash an,sbf and you will be back in the game
I, have yet to see a hard bricked Droid x2(vzw)
milestone x2 might be a different story tho not sure lol
but having a, nandroid backup of stock rooted will make everything even easier for ya if something goes wrong you can just restore nandroid and PRESTO you will have EVERYTHING back to EXACTLY how it was when you created said nandroid trust me on that one, you wont regret having a nandroid backup available
---------- Post added at 07:21 PM ---------- Previous post was at 07:19 PM ----------
follow this http://forum.xda-developers.com/showthread.php?t=1318083
for installing bootstrap recovery (our "cwm") and making yourself a nandroid backup
After searching for an answer here, I noticed Sprint is saying that the 2.3.5 update is available. I know there was some issues with it "leaking" out after the soak test but has anyone acquired the file to manually update their photon? Ive not seen an sbf or even an update.zip, and both Sprint and Motorola say the update should be available for all. I've gone back to completely stock, and still no update. Sprint of course says its there, but neither anyone on the phone or at the stores can help me get it. I am comfortable enough doing it myself if I had the requisite files, but I don/t Is there anyone out there in photon land who might have the file I am searching for? Its PHOTON 4G_MR5 (4.5.1A-1_SUN-254_12.Sprint.en.US) (45.4.12.MB855.Sprint.en.US). If anyone has it or if this has been answered I apologize, but I have searched without success, and as usual both the carrier and manufacturer are useless.... I know what the update brings and no I don't care about the boot loader. I just want the update and the 1080p recording!!
Thank you!
If you have the file, please PM me, and let me know. Otherwise, I will check back and hopefully someone will have an answer for me. I am not going to post my email or anything, so please PM me about it!
If you go and upgrade to 2.3.5 you wont be able to unlock the bootloader anymore
Thanks but
Modo-mopho said:
If you go and upgrade to 2.3.5 you wont be able to unlock the bootloader anymore
Click to expand...
Click to collapse
IF you re-read my original question, I am NOT concerned with that, I simply want the file. Anyone else?
If the software update menu doesn't work for you, look into this. I haven't used this file, I don't know for sure but others have stated that they think that's the official one.
It would be a mistake on all counts.. Don't people realize that you can get 'everything' that the 2.3.5 update entails including 1080p without crippling your poor phone? Its like buying a Ferrari so you can drive 35mph around town..
And there's no need to go all CAPS LOCK on him, he was just trying to be informative.
[email protected] said:
IF you re-read my original question, I am NOT concerned with that, I simply want the file. Anyone else?
Click to expand...
Click to collapse
Check the Imperium Website downloads section. You need to be on 198_6 prior to flashing.
Things to keep in mind before you flash it:
Every single fix or improvement has already been done by the devs here without the drawbacks
The devs here have already improved upon this release so custom ROM's are faster and offer more features
If you don't like=You have to buy a new phone
If it breaks something=You have to buy a new phone
If you change your mind=You have to buy a new phone
If you want GSM support in the US=You have to buy a new phone
YOU CANNOT DOWNGRADE, UNLOCK OR REVERT THE CHANGES MADE BY THIS UPDATE
the source code was just added earlier today to sourceforge.net check it out it might help...
http :// sourceforge. net/projects/photon4g.motorola/files/
Thank you all, I think lokifish made up my mind for me. And I do apologize about the caps, it was just a very unhelpful post. Not their fault I realize, but just wasnt helping my situation. I will look into the custom roms a little further I think.
Sent from my MB855 using XDA
Well I just got a Warranty replacement from my local Sprint store and my Photon states system version 45.3.6.MB855.Sprint.en.US and Android version 2.3.4. I don't have any system updates and I tried flashing the sbf to unlock the bootloader and it fails. I do believe the version I have won't allow me to unlock but if the Android version is suppose to be 2.3.5 on this system version I wonder how the hell I have 2.3.4. Anyone with an idea???
jmsdahutt said:
Well I just got a Warranty replacement from my local Sprint store and my Photon states system version 45.3.6.MB855.Sprint.en.US and Android version 2.3.4. I don't have any system updates and I tried flashing the sbf to unlock the bootloader and it fails. I do believe the version I have won't allow me to unlock but if the Android version is suppose to be 2.3.5 on this system version I wonder how the hell I have 2.3.4. Anyone with an idea???
Click to expand...
Click to collapse
To unlock you want 2.3.4. What guide did you follow to attempt unlock?
I myself got a replacement photon less than a month ago and was able to succesfully unlock my bootloader. However I did struggle a bit. I will look for all the files I used and see if I can send you on the right path.
Lokifish Marz said:
To unlock you want 2.3.4. What guide did you follow to attempt unlock?
Click to expand...
Click to collapse
I used the pudding guide with bootloader unlock method.
http://forum.xda-developers.com/showthread.php?t=1216143
mquezada21 said:
I myself got a replacement photon less than a month ago and was able to succesfully unlock my bootloader. However I did struggle a bit. I will look for all the files I used and see if I can send you on the right path.
Click to expand...
Click to collapse
Thanks, but not necessary as I'm the root-unlock-relock guy that hosts all the files and maintains the Photon Compendium.
jmsdahutt said:
I used the pudding guide with bootloader unlock method.
http://forum.xda-developers.com/showthread.php?t=1216143
Click to expand...
Click to collapse
I hope you didn't flash the 2.3.5 pudding. That thread is out of date and not maintained. For all the files and guide, why not use the updated and maintained Photon Compendium?
mquezada21 said:
I myself got a replacement photon less than a month ago and was able to succesfully unlock my bootloader. However I did struggle a bit. I will look for all the files I used and see if I can send you on the right path.
Click to expand...
Click to collapse
Cool! I would appreciate that! I'm fairly good at figuring things out but I'm still new to the photon stuff. I left mine stock after I got it then my girlfriend broke her phone so I didnt have it for a while. LOL! I finally have it back now. Now I like to learn more about development on different devices to contribute more to the community. Just taking it step by step now LOL!
---------- Post added at 02:44 PM ---------- Previous post was at 02:39 PM ----------
Lokifish Marz said:
Thanks, but not necessary as I'm the root-unlock-relock guy that hosts all the files and maintains the Photon Compendium.
I hope you didn't flash the 2.3.5 pudding. That thread is out of date and not maintained. For all the files and guide, why not use the updated and maintained Photon Compendium?
Click to expand...
Click to collapse
For some reason the derpunlock.sbf file when I flash fails. I've tried redownloading the file and tried again with the same results. My phone is in usb debub mode charge only and all needed drivers installed. Is that normal????
jmsdahutt said:
Cool! I would appreciate that! I'm fairly good at figuring things out but I'm still new to the photon stuff. I left mine stock after I got it then my girlfriend broke her phone so I didnt have it for a while. LOL! I finally have it back now. Now I like to learn more about development on different devices to contribute more to the community. Just taking it step by step now LOL!
---------- Post added at 02:44 PM ---------- Previous post was at 02:39 PM ----------
For some reason the derpunlock.sbf file when I flash fails. I've tried redownloading the file and tried again with the same results. My phone is in usb debub mode charge only and all needed drivers installed. Is that normal????
Click to expand...
Click to collapse
DO NOT DOWNLOAD FROM THE PUDDING THREAD!!! PEOPLE HAVE PERMANENTLY LOCKED THEIR PHONE BY FLASHING THE WRONG FILE!!!
DOWNLOAD THE ROOT-UNLOCK-RELOCK PACK!!!
You have to follow the steps!!! If you are in USB debug then your are not in RSD mode which means you can't flash ANY SBF. Straight from the Compendium;
Start RSD Lite on your computer
Reboot phone into RSD mode: VOL down/Power. Use VOL down to scroll though options til you see "RSD" then VOL up to enable.
Connect phone to computer.
Flash derpunlock.sbf.
Close RSD Lite and disconnect phone.
Reboot phone into fastboot mode (same process as getting to RSD mode) and connect phone to computer
Double click "Command Prompt" shortcut in the "Unlock" folder.
In the Command Prompt window type moto-fastboot oem unlock
Look for the UNIQUE ID number and copy it.
Type moto-fastboot oem unlock YOUR_UNIQUE_ID_THAT_YOU_JUST_COPIED (fastboot should reply <bootloader> Device is now unlocked )
Lokifish Marz said:
Thanks, but not necessary as I'm the root-unlock-relock guy that hosts all the files and maintains the Photon Compendium.
Click to expand...
Click to collapse
There is no need to be like that, thats pretty mest up I'm just trying to help the guy.... -__-'
Lokifish Marz said:
Thanks, but not necessary as I'm the root-unlock-relock guy that hosts all the files and maintains the Photon Compendium.
I hope you didn't flash the 2.3.5 pudding. That thread is out of date and not maintained. For all the files and guide, why not use the updated and maintained Photon Compendium?
Click to expand...
Click to collapse
I flashed from photon compendium
---------- Post added at 03:02 PM ---------- Previous post was at 02:49 PM ----------
Lokifish Marz said:
DO NOT DOWNLOAD FROM THE PUDDING THREAD!!! PEOPLE HAVE PERMANENTLY LOCKED THEIR PHONE BY FLASHING THE WRONG FILE!!!
DOWNLOAD THE ROOT-UNLOCK-RELOCK PACK!!!
You have to follow the steps!!! If you are in USB debug then your are not in RSD mode which means you can't flash ANY SBF. Straight from the Compendium;
Start RSD Lite on your computer
Reboot phone into RSD mode: VOL down/Power. Use VOL down to scroll though options til you see "RSD" then VOL up to enable.
Connect phone to computer.
Flash derpunlock.sbf.
Close RSD Lite and disconnect phone.
Reboot phone into fastboot mode (same process as getting to RSD mode) and connect phone to computer
Double click "Command Prompt" shortcut in the "Unlock" folder.
In the Command Prompt window type moto-fastboot oem unlock
Look for the UNIQUE ID number and copy it.
Type moto-fastboot oem unlock YOUR_UNIQUE_ID_THAT_YOU_JUST_COPIED (fastboot should reply <bootloader> Device is now unlocked )
Click to expand...
Click to collapse
I'll try again and return with the results! I appreciate the help!
[email protected] said:
After searching for an answer here, I noticed Sprint is saying that the 2.3.5 update is available. I know there was some issues with it "leaking" out after the soak test but has anyone acquired the file to manually update their photon? Ive not seen an sbf or even an update.zip, and both Sprint and Motorola say the update should be available for all. I've gone back to completely stock, and still no update. Sprint of course says its there, but neither anyone on the phone or at the stores can help me get it. I am comfortable enough doing it myself if I had the requisite files, but I don/t Is there anyone out there in photon land who might have the file I am searching for? Its PHOTON 4G_MR5 (4.5.1A-1_SUN-254_12.Sprint.en.US) (45.4.12.MB855.Sprint.en.US).
Click to expand...
Click to collapse
IMHO this update is totally not worth it. I (admittedly) totally screwed up and took this update. My phone is rooted but on stock. I hadn't had any other problems with other updates but I guess I was just playing with fire before and got lucky then. Well, 12 hours and a lot of yelling later, I have my phone back. I won't accept the update, not worth the headache again.
In all of my research to fix the phone, I found this YouTube video... (my new membership won't let me post links,). Anyway, search on YouTube for "How to unroot / unbrick the Motorola Photon 4G to stock Android" by QBKing77. The video should come right up. LOTS OF HELP! I'm a visual learner and like to see others run through the process first before I try so I know what to expect. Just make sure you have the latest files before you begin the whole process.
Lots of luck!
Agree that this update is not worth it in terms of functionality. I'm honestly not sure why Moto is bothering with it, but it speaks well of their commitment to support.
But, since (after endless ROM cooking & flashing in the the WinMo days), I've decided to stay stock Android, I did this during the soak test so that perhaps I can get a peak at stock ICS a bit early in the ICS soak.
BUT - anyone who likes custom ROMs needs to totally ignore 2.3.5 and its locked bootloader.
Wow.....
I have know a lot more
:good::good::good:
This is the recent thread I posted on Android Forums maybe someone here could help me.
thanks
Keljoe2804
New Member
Thread Author (OP)
Join Date: Aug 2012
Posts: 3
Device(s):
Thanks: 1
Thanked 0 Times in 0 Posts Photon unique issue
--------------------------------------------------------------------------------
Hey guys, sorry if this is a repeat, but i cant find anyone else with this problem.
a while back i tried to root my phone a few different ways. I tried the torpedo, one click and some other way. I think i got a partial root some how cause i have access to all my root files through file manager, but no apps recognize root. There is no su binary, no busy box and no sudo is what my root checker says. Ive tried rsd lite 5.6 but there is a re-enumeration issue. I cant get back to stock. Everything works fine except normal wear and tear things. Ive tried different usb ports, i made sure the file im flashing is in the root of my c drive. Not sure what to do. Any help would be great.
Thanks in advance.
Sponsors
August 10th, 2012, 11:42 AM #2 (permalink)
Citizen Coyote
Member
Join Date: Aug 2011
Location: Austin, TX
Posts: 422
Device(s): Motorola Photon 4G (rooted), HTC Evo 4G (sold)
Thanks: 131
Thanked 170 Times in 109 Posts
--------------------------------------------------------------------------------
What software version are you running? What were you running when you tried to root your phone the first time? If you had 2.3.4, Shabby's AIO should have worked assuming you followed the directions. If you're on 2.3.5 now, you can try Mof's new Photon-Torpedo Direct.
Good luck!
The Following User Says Thank You to Citizen Coyote For This Useful Post: Keljoe2804 (August 10th, 2012)
August 10th, 2012, 12:18 PM #3 (permalink)
Keljoe2804
New Member
Thread Author (OP)
Join Date: Aug 2012
Posts: 3
Device(s):
Thanks: 1
Thanked 0 Times in 0 Posts
--------------------------------------------------------------------------------
Awesome I'll give it a try thanks.
August 10th, 2012, 02:19 PM #4 (permalink)
Keljoe2804
New Member
Thread Author (OP)
Join Date: Aug 2012
Posts: 3
Device(s):
Thanks: 1
Thanked 0 Times in 0 Posts
--------------------------------------------------------------------------------
I wasn't successful. It gave me the error like it said but no # it went back to the $.
What about installing SuperUser? Did you think of that point?
yairku said:
What about installing SuperUser? Did you think of that point?
Click to expand...
Click to collapse
yeah, I've tried it installed and uninstalled.
To gain root access, you must have this app, and when you try to use an app that requires root access and you see a popup, select "allow".
If you uninstalled it, you can't have root access. You should root your Photon and install Super User.
yairku said:
To gain root access, you must have this app, and when you try to use an app that requires root access and you see a popup, select "allow".
If you uninstalled it, you can't have root access. You should root your Photon and install Super User.
Click to expand...
Click to collapse
thats the problem, not sure whether I'm rooted or not, lol. cause I can't root or unroot my phone, I'm trying to get back to stock so I can either send in for warranty or reroot.
yairku said:
To gain root access, you must have this app, and when you try to use an app that requires root access and you see a popup, select "allow".
If you uninstalled it, you can't have root access. You should root your Photon and install Super User.
Click to expand...
Click to collapse
The other thing is I did the OTA to 2.3.5. which should've knocked out my root access if I was rooted in the first place, but I run into different errors while trying to root, I don't have su binary, I get errors like permission denied on certain files when trying to the root through command prompt either the photon-torpedo or the one click stuff. Not sure what I'm going to do, need to get a new phone under warranty so I can start over on this whole thing, but just can't get back to stock. Is there a way that I can completely wipe my phone to where I can reload everything so there would be no trace of defective files?
I don't think you should reload everything.. There's no point in doing that unless you're sure you have a big problem.
Now that you have 2.3.5, you can't unlock the bootloader and flash custom ROM, unless you use bootstrap, that gives you the ability to flash a little amount of ROMs.
Just try to root your Photon using the old method. My favorite guide of rooting, (used it after every SBF) is here. It even prevents the permission denied problem!!
Please try this guide, I'm pretty sure that it'll solve the problem.
Does your 4g work?
The above methods won't work. The phone won't take shell commands. There is no /lib directory. I've seen this before actually I'm there myself now I had to use the ota update files to get out of a boot loop while starting a new ROM. Bit even though I have the insurance I'm going to try and figure out what's going on. The phone appears to by symlinked in a bazaar way. Give me a few days.
mof9336 said:
Does your 4g work?
The above methods won't work. The phone won't take shell commands. There is no /lib directory. I've seen this before actually I'm there myself now I had to use the ota update files to get out of a boot loop while starting a new ROM. Bit even though I have the insurance I'm going to try and figure out what's going on. The phone appears to by symlinked in a bazaar way. Give me a few days.
Click to expand...
Click to collapse
I'm in CA and I don't get 4g where I'm at, but I was in the Merced area a couple of weeks ago and I got it for a little bit of time, pretty sure it still works. And yes you're right the Torpedo root process doesn't work for me either, althought I haven't tried it the the dock.
Anyone still having issues rooting PM me I may have found a work around.
Ok, figured out that I only had to change libphoton-torpedo.sh to libphoton-torpedo2.sh and also in the script everything worked flawlessly.
Thanks
1) I restored my nandroid backup thru CWM and reverted back to 2.2.2 stock rom I had at the first place when I got my atrix.
It works fine but the device randomly shuts down and the only way to turn it back on is pulling out the battery. How do I fix that?
2) I heard the only way to get rid of the bootloader logo is to flash an official SBF file.
Is it possible to revert to froyo 2.2.2 using SBF? plus I didnt manage to find the 2.2.2 sbf file over the web, does it exist out there?
Right now I'm on 2.2.2 (restored from nandroid) but the bootloader still appears so I basicly want to go from 2.2.2 to 2.2.2, just this time using SBF
Ultrasagol said:
1) I restored my nandroid backup thru CWM and reverted back to 2.2.2 stock rom I had at the first place when I got my atrix.
It works fine but the device randomly shuts down and the only way to turn it back on is pulling out the battery. How do I fix that?
2) I heard the only way to get rid of the bootloader logo is to flash an official SBF file.
Is it possible to revert to froyo 2.2.2 using SBF? plus I didnt manage to find the 2.2.2 sbf file over the web, does it exist out there?
Right now I'm on 2.2.2 (restored from nandroid) but the bootloader still appears so I basicly want to go from 2.2.2 to 2.2.2, just this time using SBF
Click to expand...
Click to collapse
1) It sounds like your backup is corrupt.
2) You won't get much help around here with sbf files. Too many users were bricking devices, so the sbf files were removed from the forum. The best and safest option to return to stock is to flash a Froyo fruit cake. Otherwise flash a custom ROM.
Atrix Reboot Project
Froyo 2.2.2 fruit cake
upndwn4par said:
1) It sounds like your backup is corrupt.
2) You won't get much help around here with sbf files. Too many users were bricking devices, so the sbf files were removed from the forum. The best and safest option to return to stock is to flash a Froyo fruit cake. Otherwise flash a custom ROM.
Atrix Reboot Project
Froyo 2.2.2 fruit cake
Click to expand...
Click to collapse
Ok. and what about the bootloader? is there a way to hide it somehow?
my warrant ends real soon and Ive got to make a use out of it or my digitizer will stay unfuctional
Ultrasagol said:
Ok. and what about the bootloader? is there a way to hide it somehow?
my warrant ends real soon and Ive got to make a use out of it or my digitizer will stay unfuctional
Click to expand...
Click to collapse
If I remember correctly, the only way to remove the "unlocked" is to flash the Froyo 183 sbf. I do not recommend doing this.
Also, many device owners that have sent their Atrix in for service get it back with an unlockable bootloader. You may want to consider replacing the digitizer yourself.
upndwn4par said:
If I remember correctly, the only way to remove the "unlocked" is to flash the Froyo 183 sbf. I do not recommend doing this.
Also, many device owners that have sent their Atrix in for service get it back with an unlockable bootloader. You may want to consider replacing the digitizer yourself.
Click to expand...
Click to collapse
There has to be a way to hide the Unlocked , maybe flashing white bootlogo? Idk...
Ultrasagol said:
There has to be a way to hide the Unlocked , maybe flashing white bootlogo? Idk...
Click to expand...
Click to collapse
If there was any way to do this, don't you think someone would come up with it already? I gave it a shot myself, no luck.
The white logo doesn't help at all sine the text has black background.
Trust me, this has been made specifically with the intention that it cannot be removed or concealed. There is just no way. Just deal with it.
ravilov said:
If there was any way to do this, don't you think someone would come up with it already? I gave it a shot myself, no luck.
The white logo doesn't help at all sine the text has black background.
Trust me, this has been made specifically with the intention that it cannot be removed or concealed. There is just no way. Just deal with it.
Click to expand...
Click to collapse
Damn.
that really sucks. Hope theyre dumb as much as I think they are and they won't notice that.
Do you know if there's a way to hide the Superuser application? I tried unrooting but the application still exists, I also can't uninstall it for some reason. Any suggestions?
Steps to Unroot
Ultrasagol said:
Damn.
that really sucks. Hope theyre dumb as much as I think they are and they won't notice that.
Do you know if there's a way to hide the Superuser application? I tried unrooting but the application still exists, I also can't uninstall it for some reason. Any suggestions?
Click to expand...
Click to collapse
When you rooted your phone, Superuser.apk was installed as a system app to prevent it from being removed.
I found manual steps to unroot that you can try, but I have not confirmed them working. This assumes you used the preinstall method described in that post, but I think it should work regardless. Here's the steps from this post from Atrix Forums:
You must still have full root access to accomplish this. This will remove root access and also erase the traces (most) of root access from your phone. There may still be evidence on log files, but that's something I cannot help with.
First, start by downloading Android Terminal Emulator from the Market
This will only apply to the /preinstall root method posted above as different root methods place files in different locations, but if you know where they are located you can use the same methods to remove them.
I'm going to use the Terminal to delete everything, but you can also accomplish the same thing using Root Explorer or another root file manager.
Un-root Steps:
1. Open Android Terminal Emulator (see download link above)
2. Type in the following commands, hitting ENTER after each line of code: (after typing 'su' below, look for the Superuser request and approve it, you can only continue if you get the # prompt.
Code:
su
mount -o rw,remount /dev/block/mmcblk0p12 /system
mount -o rw,remount /dev/block/mmcblk0p17 /preinstall
rm /system/bin/su
rm /preinstall/sqlite3
rm /preinstall/dosu
rm /preinstall/Superuser.apk
rm /preinstall/su
reboot
3. Let the phone reboot fully and then go into Settings > Applications > Manage Applications > find Superuser and uninstall it just like any other app.
4. You're un-rooted and all files that /preinstall put on your phone have been removed.
Click to expand...
Click to collapse
Ultrasagol said:
Damn.
that really sucks. Hope theyre dumb as much as I think they are and they won't notice that.
Do you know if there's a way to hide the Superuser application? I tried unrooting but the application still exists, I also can't uninstall it for some reason. Any suggestions?
Click to expand...
Click to collapse
Go to Manage Applications and uninstall su updates. Then use a root level file explorer to go to /system/app and delete su. Might not work if you successfully unrooted. Might have to re-root.
Can someone give me some straight directions on how to flash an official 2.3.4 SBF on my international atrix?
Im taking full responsibility for this in case anything happen I take all charges. I might have a low posts count but I'm not newbie I'm into all of this for a long time, I just don't post a lot. I mostly read and learn.
Bump.
Someone?
SBFs are dangerous, I guess most people have learned to avoid them. That's why you're not getting any responses.
Ultrasagol said:
Can someone give me some straight directions on how to flash an official 2.3.4 SBF on my international atrix?
Im taking full responsibility for this in case anything happen I take all charges. I might have a low posts count but I'm not newbie I'm into all of this for a long time, I just don't post a lot. I mostly read and learn.
Click to expand...
Click to collapse
Thats why I mentioned Im taking full responsibility for that.
My atrix digitizer is barely functional I gotta take it the company to have a fix under warranty and thats why I need to flash this SBF so bad - I need the "Unlocked" in boot to disappear
My apologies for taking so long, life is hectic. This is a "root path" for the 4.4 update, and in this case you will retain your stock recovery so features like remote wipe will continue to work. It requires you downgrading to 4.2.2 or already be on 4.2.2 before updating to 4.4. Unlike hte MotoX, you can not downgrade. This Must be preformed while on 4.2.2 before updating to 4.4
First you must use MotoWPNoMo, if you haven't then you will need to. Use RockMyMoto to gain root, then use MotoWPNoMo, and then restore to the 4.2.2 Camera update.
Step1)
Unzip SlapMyMoto-1,0.zip and push the jar file to your internal storage
Code:
adb push SlapMyMoto.jar /sdcard/SlapMyMoto.jar
Step2)
Use http://www.cydiaimpactor.com/ to open up a telnet session as system user on port 2222. We covered how to use Impactor and telnet in the RockMyMoto root, I won't be covering it again since this post is going to be long enough already, see here -> http://forum.xda-developers.com/showthread.php?t=2509590 or http://rootzwiki.com/topic/107098-root-rockmymoto-yes-even-the-first-ota/
Connecting over telnet, and run Stage1 with this command:
Code:
dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto
When the device tells you to reboot, do this manually with "adb reboot" or your power button. It will not auto reboot on this step
Step3)
Once the device has rebooted, run Impactor again and connect over telnet just like in the previous step, then run the same command
Code:
dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto
Once the device has rebooted, please take the 4.4 OTA.
Step4)
Now that we are on 4.4, we can finish the process with adb shell:
Code:
adb shell
cp /sdcard/install.sh /data/local/tmp/install.sh
chmod 755 /data/local/tmp/install.sh
echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
Then either wait, or toggle your bluetooth. Once the device reboots, you will have root.
So, if I have a root that I've gained with RockMyMoto I just need to take an OTA and start from the step 4 ?)
Sent from my XT1080 using Tapatalk
I was going to say what if we used voodoo un root then take the update when it comes hopefully restore with it? I know voodoo doesn't support 4.3+ but what if we achieved root on 4.2.2?
Sent from my XT1080 using Tapatalk
No....make sure you have write protection off with the MotoWPNoMo procedure jcase linked, then start at step 1. It's my understanding that if you start from step 4 nothing will work because 4.4 can't currently be rooted, so you go through all these other steps to maintain a root via 4.2.2. Besides that, with the 4.2.2 root, there's no recovery so if you tried to take it right away you'd just boot loop your phone. Someone correct me if I'm wrong.
Has this been verified? I saw people in another thread getting a "security version downgraded" error but could not figure out exactly what they did
Sent from my XT1080 using XDA Premium 4 mobile app
Another question I got root through rockmynoto. When I got my maxx I took the update to 12.15.15 do I still have to do all the steps?
Sent from my XT1080 using Tapatalk
Well, upon flashing back to 4.2.2, my phone says I don't need the update. It can't be polled, so I have no idea when it'll prompt me to do it again.
With my luck I'll have to wait until after the push window closes and it becomes a freeforall.
jcase said:
God-like abilities
Click to expand...
Click to collapse
Does anyone have the update.zip?
EDIT:
MAXX Camera Update: http://sbf.droid-developers.org/download.php?device=4&file=1
Mini Camera Update: http://sbf.droid-developers.org/download.php?device=2&file=6
Ultra Camera Update: http://sbf.droid-developers.org/download.php?device=1&file=8
i really dont feel like going back to 4.2.2 to root lol.. battery life is great.. think ill stick with 4.4 /4.1/.2 until there's an exploit for it.
shouldnt there be an "adb push su /sdcard/" somewhere
TheWhiteChallenger said:
shouldnt there be an "adb push su /sdcard/" somewhere
Click to expand...
Click to collapse
Nope
Sent from my HTC Two
digitaloutsider said:
Well, upon flashing back to 4.2.2, my phone says I don't need the update. It can't be polled, so I have no idea when it'll prompt me to do it again.
With my luck I'll have to wait until after the push window closes and it becomes a freeforall.
Click to expand...
Click to collapse
That's what I'm afraid of..I'm going to wait.
ok so im having major issues, idk if its the root method or the fact that i push the ota via adb, so ima keep that conversation here: http://forum.xda-developers.com/showthread.php?p=48656238&posted=1#post48656238 for now in an effort not to clutter this thread needlessly
but i would really appreciate any help, especially if jcase would like to take a peek and see if he know wtf i did wrong.
on the lighter side can someone whos done this tell me if we were suposed to get the new dialer or did our kitkat get shorted out of that?
Just verifying for everyone that I run a Droid Maxx and I am part of the soak test and This did work I am on 4.4 with Root and Hotspot active used another mod on here for that and Also google wallet working with touch 2 pay !!!
Thanks Jcase As you know I think you are the best !!!!
jcase said:
My apologies for taking so long, life is hectic. This is a "root path" for the 4.4 update, and in this case you will retain your stock recovery so features like remote wipe will continue to work. It requires you downgrading to 4.2.2 or already be on 4.2.2 before updating to 4.4.
First you must use MotoWPNoMo, if you haven't then you will need to. Use RockMyMoto to gain root, then use MotoWPNoMo, and then restore to the 4.2.2 Camera update.
SlapMyMoto requires you to be on the 4.2.2 Camera update, you can find the firmware for your device below:
<someone please post the appropriate firmware links below, I dont have the droid devices here>
Step1)
Unzip SlapMyMoto-1,0.zip and push the jar file to your internal storage
Code:
adb push SlapMyMoto.jar /sdcard/SlapMyMoto.jar
Step2)
Use http://www.cydiaimpactor.com/ to open up a telnet session as system user on port 2222. We covered how to use Impactor and telnet in the RockMyMoto root, I won't be covering it again since this post is going to be long enough already, see here -> http://forum.xda-developers.com/showthread.php?t=2509590 or http://rootzwiki.com/topic/107098-root-rockmymoto-yes-even-the-first-ota/
Connecting over telnet, and run Stage1 with this command:
Code:
dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto
When the device tells you to reboot, do this manually with "adb reboot" or your power button. It will not auto reboot on this step
Step3)
Once the device has rebooted, run Impactor again and connect over telnet just like in the previous step, then run the same command
Code:
dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto
Once the device has rebooted, please take the 4.4 OTA.
Step4)
Now that we are on 4.4, we can finish the process with adb shell:
Code:
adb shell
cp /sdcard/install.sh /data/local/tmp/install.sh
chmod 755 /data/local/tmp/install.sh
echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
Then either wait, or toggle your bluetooth. Once the device reboots, you will have root.
Click to expand...
Click to collapse
---------- Post added at 11:14 PM ---------- Previous post was at 11:09 PM ----------
My Dialer looks the same !!
TheWhiteChallenger said:
ok so im having major issues, idk if its the root method or the fact that i push the ota via adb, so ima keep that conversation here: http://forum.xda-developers.com/showthread.php?p=48656238&posted=1#post48656238 for now in an effort not to clutter this thread needlessly
but i would really appreciate any help, especially if jcase would like to take a peek and see if he know wtf i did wrong.
on the lighter side can someone whos done this tell me if we were suposed to get the new dialer or did our kitkat get shorted out of that?
Click to expand...
Click to collapse
jcase said:
Nope
Sent from my HTC Two
Click to expand...
Click to collapse
I cannot downgrade. I get an error that the bootloader noticed it was a downgrade....
Oh well, I guess I'll wait for something else.
dtreth said:
I cannot downgrade. I get an error that the bootloader noticed it was a downgrade....
Oh well, I guess I'll wait for something else.
Click to expand...
Click to collapse
What was the exact erro, what were you downgrading to, and what specific device?
I did not confirm downgrade was possible, so it may only apply to those that already were on 4.2.2
jcase said:
What was the exact erro, what were you downgrading to, and what specific device?
I did not confirm downgrade was possible, so it may only apply to those that already were on 4.2.2
Click to expand...
Click to collapse
I took the OTA 4.4, tried to downgrade to the link I provided earlier in the thread, I have a Droid MAXX. I don't remember exactly what it said but it was the same error I got when I tried to FXZ my Razr MAXX HD to 4.1.2 unlockable after I took 4.1.2 locked forever. I don't really want to do it again but I will for exact text.
EDIT:
I did it again, it said
"downgraded security version
update gpt_main version failed
preflash validation failed for GPT"
I DID do MotoWpNoMo and it survived the OTA even without root or anything, so I'd be willing to test any methods you cook up to remedy this, if you do indeed attempt anything (and I'd also probably try to hug you through the computer somehow)
jcase said:
It requires you downgrading to 4.2.2 or already be on 4.2.2 before updating to 4.4.
Click to expand...
Click to collapse
Correct me if if I'm wrong, but this looks like I need to be on STOCK 4.2.2, correct?
I'm currently rooted with WP off on 4.2.2 (XT1080M, MAXX). When I run SlapMyMoto, it says rooted devices are not supported. If I'm understanding these steps correctly, I need only go back to stock 4.2.2 and then complete all of these steps. Can anyone that has completed these steps confirm this?
j.bruha said:
Correct me if if I'm wrong, but this looks like I need to be on STOCK 4.2.2, correct?
I'm currently rooted with WP off on 4.2.2 (XT1080M, MAXX). When I run SlapMyMoto, it says rooted devices are not supported. If I'm understanding these steps correctly, I need only go back to stock 4.2.2 and then complete all of these steps. Can anyone that has completed these steps confirm this?
Click to expand...
Click to collapse
I suggest doing a FXZ (w/ Keep Data) with House of Moto to get back to 4.2.2 stock without root. Be sure to flash the 12.15.15 firmware. You will not lose "WP off". Then proceed with the SlapMyMoto steps.
UPDATE: Success! Followed jcase's steps exactly and had no issues. One exception is that I installed the update from internal storage instead of an OTA.
A few other things I've noticed:
1. Recovery is now true recovery and is no longer the normal boot with "write protection off" (like it was with RockMyMoto). Now you see the Android with the red exclamation point like stock recovery.
2. MotoWpNoMo survives the 4.4 OTA!!!
3. Google hotword detection ("OK Google") in the GEL and GoogleNow isn't working. Moto X users on KitKat are seeing the same thing, so hopefully a fix is coming soon. Of course, Moto's Touchless Controls ("OK Google Now") still works like a charm.
Question...
Currently I'm on 4.2.2 no root, no WP off...fresh from the box...
I am not yet able to pull the update from the servers...should I wait till I get notification that there is an update to take? Or can I preemptively do steps 1-3 and then take the OTA whenever it comes and finish the process?
Sent from my XT1080 using Tapatalk