Database Develop

[Q] Flashing KitKat on a Moto X with 139.12.35.ghost_row.AmericaMovil.en.PR

Hello!
I'm currently stationed in Singapore and bought a Moto X about a month or so ago from eBay. While I am anxiously waiting for my Moto X to receive the 4.4 update, I realised that the system version (after the previous camera update) is 139.12.35.ghost_row.AmericaMovil.en.PR, which I found to be a Latin America version after some searching on the forums and Googling here and there.
I also found this thread, where OP said that they can be flashed over to either the T-Mobile version. Does this continue to work for the 4.4 updates by T-Mobile or AT&T, and would there be anything else required for flashing? (I saw something about flashing new radios and all, but was quite confused by contradicting explanations and suggestions :/)
Thanks in advance!
// EDIT:
To add on after a bit of searching, I realised that I am allowed to unlock my bootloader, despite claims from the original retailer on eBay that the phone came from AT&T (which is notorious, even here, for their stance on bootloader unlocking). What gives?

I got the same Moto X from a buddy yesterday. I did a lot of searching and also discovered the thread about the phone being flashed to t- mobile.
I fooled the steps on another thread titled " Return to stock 100%" out something like that...
I downloaded the correct Att firmware and with the use of RSDLite, I successfully flashed my Moto X to ATT.... it took less than 10 minutes. And as soon as it booted up, I got hit with the "update available" message ( kit Kat)
Sent from my XT1058 using Tapatalk

Thanks for the information!
I've successfully upgraded my phone to the Verizon version (minus all the bloatware that I hastily blasted off), with root and TWRP. So this is what I did, for future reference:
It seems that AmericaMovil versions are not bound by the AT&T's locked bootloader policies, and other Latin America versions are probably free from the restriction too. So I managed to get my hands on the Motorola Fastboot and unlocked my bootloader. TWRP was installed (remember to use 2.6.3.1 and above for 4.4 support), and then flashed the Verizon system dump available here. Root was installed by TWRP.
After getting on the device and setting things up, I rebooted to recovery to remove lots of bloatware (available in /system/app and /system/priv-app). Had to remove some of them through Titanium Backup as the file names were not always indicative that it came from Verizon. I made the extra step of killing the god-awful boot animation that they had by replacing it with this.
And... that concludes my experience with this, I suppose.

I've been looking through a few threads and I am not comfortable enough to flash the T-Mobile rom over my AmericanMovil one yet.
I can't seem to find step by step instructions on how to do this.. Would anyone like to explain it from the ground up?
My understanding
1) unlock bootloader
2) flash a recovery like twrp or cmw
3) flash the rom that is given in the OG post here http://forum.xda-developers.com/showthread.php?t=2477180
4) this should now give us the t-mobile version of things and we should be able to do the standard OTA from there?
[Q] So can this all be done without ever having to root the phone?

alternetconcept said:
I've been looking through a few threads and I am not comfortable enough to flash the T-Mobile rom over my AmericanMovil one yet.
I can't seem to find step by step instructions on how to do this.. Would anyone like to explain it from the ground up?
My understanding
1) unlock bootloader
2) flash a recovery like twrp or cmw
3) flash the rom that is given in the OG post here http://forum.xda-developers.com/showthread.php?t=2477180
4) this should now give us the t-mobile version of things and we should be able to do the standard OTA from there?
[Q] So can this all be done without ever having to root the phone?
Click to expand...
Click to collapse
I'm not too sure whether flashing via TWRP/CMW will allow you to get OTA, unfortunately. Which is why I went straight for the Verizon system dump. But yes, you can change firmware without ever having to root the phone. Heck, I think there's a guide on restoring mentioned by @plmiller0905 below that will allow you to do it without unlocking the bootloader, even.

RagnaParadise said:
I'm not too sure whether flashing via TWRP/CMW will allow you to get OTA, unfortunately. Which is why I went straight for the Verizon system dump. But yes, you can change firmware without ever having to root the phone. Heck, I think there's a guide on restoring mentioned by @plmiller0905 below that will allow you to do it without unlocking the bootloader, even.
Click to expand...
Click to collapse
I believe the bootloader does have to be unlocked in order to flash a different firmware.
Sent from my XT1058 using Tapatalk

RagnaParadise said:
I'm not too sure whether flashing via TWRP/CMW will allow you to get OTA, unfortunately. Which is why I went straight for the Verizon system dump. But yes, you can change firmware without ever having to root the phone. Heck, I think there's a guide on restoring mentioned by @plmiller0905 below that will allow you to do it without unlocking the bootloader, even.
Click to expand...
Click to collapse
Yeah after doing so more reading.. (at least the way I'm willing to do it) is to just unlock my bootloader and then using RSD Lite (Which i still have no idea what that is / where it is) flash an SBF found here (http://sbf.droid-developers.org/ghost_rcica/list.php)
I guess following this video somewhat http://www.youtube.com/watch?v=Fr0JHSAXJDI#t=15
Does that sound right?
Should I flash the TMO_RETAIL_XT1053_4.2.2-13.9.0Q2.X-116-X-17-57_MR1_CFC.xml.zip
Or just jump straight to the 4.4 version TMO_RETAIL_XT1053_4.4-13.11.1Q2.X-69-3_MR2_CFC.xml.zip
??

As far as I know, the use of RSD Lite doesn't require an unlocked bootloader (at least, that's what it shows in the video you showed me anyway), especially since these are images supposedly signed by Motorola themselves. Let me know if you've found something else?
As for your question on which to flash... I'm not sure, but you'd skip a lot of the hassle if you could flash 4.4 straight, so how about trying that?

RagnaParadise said:
As far as I know, the use of RSD Lite doesn't require an unlocked bootloader (at least, that's what it shows in the video you showed me anyway), especially since these are images supposedly signed by Motorola themselves. Let me know if you've found something else?
As for your question on which to flash... I'm not sure, but you'd skip a lot of the hassle if you could flash 4.4 straight, so how about trying that?
Click to expand...
Click to collapse
Rsdlite is a shell for a flash boot flash supposedly with an XML doing all the steps together. Just makes it easier.
You need unlocked boot loader only to flash an image that doesn't match your current boot loader. So if you have a. At&t phone you can only flash at&t images by rsdlite. But if you unlock your amerimovil phone you can flash any xt1058 image I think. So amerimovil could take say a rogers or at&t or telcel image. Not sure if T-Mobile image will work on a full rsdlite flash as it is an xt1053 image. I think you can flash most of a T-Mobile image by twrp but not by rsdlite not sure

sleepyguy007 said:
Rsdlite is a shell for a flash boot flash supposedly with an XML doing all the steps together. Just makes it easier.
You need unlocked boot loader only to flash an image that doesn't match your current boot loader. So if you have a. At&t phone you can only flash at&t images by rsdlite. But if you unlock your amerimovil phone you can flash any xt1058 image I think. So amerimovil could take say a rogers or at&t or telcel image. Not sure if T-Mobile image will work on a full rsdlite flash as it is an xt1053 image. I think you can flash most of a T-Mobile image by twrp but not by rsdlite not sure
Click to expand...
Click to collapse
So if I flash the at&t image found here (http://sbf.droid-developers.org/ghost_rcica/list.php), would it come pre-loaded with all the bloatware AT&T has even though I'm not using AT&T network?

alternetconcept said:
So if I flash the at&t image found here (http://sbf.droid-developers.org/ghost_rcica/list.php), would it come pre-loaded with all the bloatware AT&T has even though I'm not using AT&T network?
Click to expand...
Click to collapse
yes of course. think about it like if you took a dell windows 7 install CD , and put it on an HP. all the dell customizations would still be there.
obviously since you have unlocked bootloader, once you do the RSDlite you can always flash twrp, and superuser, and delete all that stuff. but then you wouldn't get updates again. i dont think the at&t image is really THAT bad. though i've heard the rogers one is better (though maybe not 4.4 yet)

sleepyguy007 said:
yes of course. think about it like if you took a dell windows 7 install CD , and put it on an HP. all the dell customizations would still be there.
obviously since you have unlocked bootloader, once you do the RSDlite you can always flash twrp, and superuser, and delete all that stuff. but then you wouldn't get updates again. i dont think the at&t image is really THAT bad. though i've heard the rogers one is better (though maybe not 4.4 yet)
Click to expand...
Click to collapse
Yeah unfortunately that's what I thought. Hence why I would of liked to flash the t-mobile image but I'm going to hold off until someone that is a bit more adb savvy then myself tries it out. I wouldn't know what to do if I ended up soft bricking my phone

Well it didn't take long to try it out myself...
It worked out!
I used this thread here http://forum.xda-developers.com/showthread.php?t=2446515
I downloaded the Tmobile 4.4 Image and used RSD.
All you have to do is unlock your BL. (Note: I was completely bone stock with NO root and NO special recovery like CMW or TWRP)
Have all the proper drivers installed, enable USB debugging in developer settings on the phone
Go into Fastboot on the phone
Plug in the phone and just follow the video
I do not take any responsibitliy if you brick your phone. It is fairly easy process and took only a few mins.
Hope this helps!

- deleted because I was sleepy enough not to notice that replies were done on the next page -_- -

alternetconcept said:
I've been looking through a few threads and I am not comfortable enough to flash the T-Mobile rom over my AmericanMovil one yet.
I can't seem to find step by step instructions on how to do this.. Would anyone like to explain it from the ground up?
My understanding
1) unlock bootloader
2) flash a recovery like twrp or cmw
3) flash the rom that is given in the OG post here http://forum.xda-developers.com/showthread.php?t=2477180
4) this should now give us the t-mobile version of things and we should be able to do the standard OTA from there?
[Q] So can this all be done without ever having to root the phone?
Click to expand...
Click to collapse
I've been doing some research on this since yesterday and I've been hesitant on doing it. I saw in your last post that you successfully flashed the TMO 4.4 ROM on your AmericaMovil phone, so I have a few questions for you before I go ahead and do the same:
1. Can you please confirm that your model is XT1058 and not XT1053?
2. Does the TMO ROM have the TMO boot logo and any TMO bloatware?
3. Does the TMO ROM have the Tethering & portable hotspot option under Settings > More?
4. Does the TMO ROM have the Mass Storage option under Settings > Storage > | > USB computer connection?
5. Have you been having any radio problems since you flashed the TMO ROM?
I wonder if I install the ROM in here http://forum.xda-developers.com/showthread.php?t=2477180 using RSDLite, would I get the OTA update to 4.4? The reason I want to install this ROM is because it only flashes system and boot.img without flashing bootloader, modem, logo etc... and I know the XT1058 radio is different from the XT1053 radio, so I've been reluctant to flash a full XT1053 ROM on my XT1058 phone.
But what I also would like to know is if an OTA update would flash a full ROM or not. In other words, if I flash the ROM above and then OTA update to 4.4 and the OTA update flashes the full ROM including the radio, I might as well flash the full 4.4 immediately.
What do you or anyone else think?

I'll answer to the best of my ability. heh
mschumacher69 said:
1. Can you please confirm that your model is XT1058 and not XT1053?
Click to expand...
Click to collapse
Mine was an XT1058, and has been flashed to XT1060. (I didn't notice that T-Mo had a 4.4 ROM on the list, so I went straight for the flashable ZIP for Verizon instead. silly me.)
mschumacher69 said:
2. Does the TMO ROM have the TMO boot logo and any TMO bloatware?
Click to expand...
Click to collapse
At least according to this article, the TMO version shouldn't have any bloatware.
mschumacher69 said:
4. Does the TMO ROM have the Mass Storage option under Settings > Storage > | > USB computer connection?
Click to expand...
Click to collapse
There's no reason why there shouldn't be; I'm seeing it on my Verizon version.
mschumacher69 said:
5. Have you been having any radio problems since you flashed the TMO ROM?
Click to expand...
Click to collapse
I can't say for sure if you'll face any problems, but I flashed the T-Mo radio provided here with my Verizon ROM, and I had no problems connecting to my network in Singapore.
--
I can't answer the rest unfortunately. Sorry. Hope I've helped.

RagnaParadise said:
I can't answer the rest unfortunately. Sorry. Hope I've helped.
Click to expand...
Click to collapse
Thank you for your answers!
Regarding Mass Storage, the reason I'm asking is because I don't have it on my AmericaMovil ROM.

The ROM is basically exactly what you get when you buy the T-Mobile version.
I figured the radios are nearly identical from the AT&T version and the T-Mobile version so my XT1058 is running on the XT1053 radios. There is no bloatware. tethering is there but I'm not sure if t-mobile will allow it. There is NO tmobile logo that comes up on boot. USB connect to computer is there.
As for the radio section again.. I was getting only EDGE in my house before I switched to this ROM (Meaning when I was on the ORIGINAL XT1058 image) and I am still getting only EDGE in my house.. Unfortunately I haven't left my house since yesterday flashing the image but when I'll be back at work in NYC and should see '4G/LTE' over there.
We'll see.

alternetconcept said:
The ROM is basically exactly what you get when you buy the T-Mobile version.
I figured the radios are nearly identical from the AT&T version and the T-Mobile version so my XT1058 is running on the XT1053 radios. There is no bloatware. tethering is there but I'm not sure if t-mobile will allow it. There is NO tmobile logo that comes up on boot. USB connect to computer is there.
As for the radio section again.. I was getting only EDGE in my house before I switched to this ROM (Meaning when I was on the ORIGINAL XT1058 image) and I am still getting only EDGE in my house.. Unfortunately I haven't left my house since yesterday flashing the image but when I'll be back at work in NYC and should see '4G/LTE' over there.
We'll see.
Click to expand...
Click to collapse
Thanks for ur reply! Which network are you on right now?

mschumacher69 said:
Thanks for ur reply! Which network are you on right now?
Click to expand...
Click to collapse
I've always been on T-mobile network. Both when i was on original XT1058 AmericanMovil system version and still on T-mobile when I switched the image to XT1053.
Back on my Nexus 4 though.. I would have HSPA+ in my house.. So I thought it was a bit odd that as soon as I received this phone that I wasn't getting anything other than EDGE..

[Q] Claro chile 4.4.2 update

I just got the 4.4.2 update from claro in chile. But I have not installed it yet. My phone is on 4.2.2 at the moment. The bootloader is unlocked. It is rooted using rockmymoto. What I want to know is what do I need to do to get it ready for the 4.4.2 upgrade? I assume I need to unroot it? Also I have lucky patcher installed and I odexed my system, will this be a problem? Will I be able to get root in 4.4.2?

AGISCI said:
I just got the 4.4.2 update from claro in chile. But I have not installed it yet. My phone is on 4.2.2 at the moment. The bootloader is unlocked. It is rooted using rockmymoto. What I want to know is what do I need to do to get it ready for the 4.4.2 upgrade? I assume I need to unroot it? Also I have lucky patcher installed and I odexed my system, will this be a problem? Will I be able to get root in 4.4.2?
Click to expand...
Click to collapse
There are threads on this in the general folder as well as this folder.
What I don't understand is why you had to root using rockmymoto if your bootloader is unlocked? Why didn't you just flash a custom recovery like TWRP and install SuperSU to root?
Do you have the 4.2.2 post camera update installed?

Cozume said:
There are threads on this in the general folder as well as this folder.
Click to expand...
Click to collapse
I have read various topics in both of the forums on it. But I wanted to be 100% sure of what path I need to follow to be sure I don't brick my phone. 1 thing that had me worried is that I odexed my system with lucky patcher... does this mean I am going to have to flash my firmware back to stock before I can do this?
Cozume said:
What I don't understand is why you had to root using rockmymoto if your bootloader is unlocked? Why didn't you just flash a custom recovery like TWRP and install SuperSU to root?
Click to expand...
Click to collapse
Because I rooted it a month before I unlocked the bootloader.
I still currently have stock recovery though.
Cozume said:
Do you have the 4.2.2 post camera update installed?
Click to expand...
Click to collapse
As far as the post camera update, not sure. My camera version is 3.1.41.2.

AGISCI said:
I have read various topics in both of the forums on it. But I wanted to be 100% sure of what path I need to follow to be sure I don't brick my phone. 1 thing that had me worried is that I odexed my system with lucky patcher... does this mean I am going to have to flash my firmware back to stock before I can do this?
Click to expand...
Click to collapse
That is certainly the safest way to go from all I have read as any system mods could potentially cause a problem. The problem that another poster here had is that the only firmware that is posted for the Claro Chile is the precamera update. He was looking for the postcamera firmware.
http://forum.xda-developers.com/showthread.php?t=2649806
And no one could help him find it. I don't think you can take the OTA if you are on the precamera firmware. Perhaps you can PM the OP in that link and see if he is knowledgeable about Claro chile firmware.

Cozume said:
That is certainly the safest way to go from all I have read as any system mods could potentially cause a problem. The problem that another poster here had is that the only firmware that is posted for the Claro Chile is the precamera update. He was looking for the postcamera firmware.
http://forum.xda-developers.com/showthread.php?t=2649806
And no one could help him find it. I don't think you can take the OTA if you are on the precamera firmware. Perhaps you can PM the OP in that link and see if he is knowledgeable about Claro chile firmware.
Click to expand...
Click to collapse
How can I tell if I am on the pre cam or post cam? Also is there a link that talks about what teh pre cam and post cam does or changed?

AGISCI said:
How can I tell if I am on the pre cam or post cam? Also is there a link that talks about what teh pre cam and post cam does or changed?
Click to expand...
Click to collapse
Go to Settings->About Phone->System Version. What does it say?

139.12.35.ghost_row.AmericaMovil.en.CL
Sent from my Nexus 7 using Tapatalk

AGISCI said:
139.12.35.ghost_row.AmericaMovil.en.CL
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
From the version numbers here:
http://sbf.droid-developers.org/phone.php?device=0
As best I can tell 139.12.35 is the post camera update. The problem is that no one has a copy of the stock firmware posted anywhere that anyone can find.

If that's the case flashing this firmware will not brick me then correct?
Sent from my Nexus 7 using Tapatalk

You say you rooted the phone a month before you unlocked the bootloader. If this is the case then your phone should have been wiped clean as unlocking the bootloader performs a full wipe of the phone.
So something does not add up/make sense.

Steve-x said:
You say you rooted the phone a month before you unlocked the bootloader. If this is the case then your phone should have been wiped clean as unlocking the bootloader performs a full wipe of the phone.
So something does not add up/make sense.
Click to expand...
Click to collapse
I rooted it twice actually. After I unlocked the bootloader it was erased just like you said, and I rooted again using the same method from the first time.

AGISCI said:
If that's the case flashing this firmware will not brick me then correct?
Click to expand...
Click to collapse
Which firmware?
This is from dray_jr on the thread in the Moto X General forum:
the only OTA that can downgrade is 4.4 to 4.2.2 Post Cam
here is what we know right now that might make more sense
4.4 to 4.2.2 Pre Cam will Brick
4.2.2 Post Cam to 4.2.2 Pre Cam will Brick.
4.4.2 to anything will Brick
4.4 to 4.2.2 Post Cam you are ok
http://forum.xda-developers.com/showthread.php?t=2635366&highlight=brick&page=5

You are in quite a unique situation here actually... since there is no stock image that you can go back to. If there was a 4.4 SBF I would have suggested to flash then take the 4.4.2 update. However, it seems as if there was no 4.4 roll out/update for your carrier at all. So this 4.4.2 carrier update would be more than a simple patch from 4.4 to 4.4.2, it would probably end up removing root since you are going from JB to KK.
Your best bet if you want it now is to do the following...
I AM NOT RESPONSIBLE FOR YOUR ACTIONS OR BRICKING YOUR DEVICE
1) Did you make a backup before you messed with anything in the system? If you didn't, then you have to go through the manual process of making sure that it is as clean as a normal stock image.
2) Do you have the original recovery? If not, find a recovery file for your carrier and flash that.
3) Attempt to flash the OTA in the standard recovery.
But honestly, the safest thing to do is to wait until your 4.4.2 SBF is released, that way you can flash it in RSD Lite, preventing a brick as much as possible.

mastarifla said:
But honestly, the safest thing to do is to wait until your 4.4.2 SBF is released, that way you can flash it in RSD Lite, preventing a brick as much as possible.
Click to expand...
Click to collapse
Who releases the sbf? Motorola? Because it looks like the problem is that no one can find the sbf for the 4.2.2 postcamera update for their carrier.

I guess I will have to wait then. I can't afford to brick my phone. I captured the update and pulled it with adb so if anyone needs it I will be able to upload it.
Sent from my Nexus 7 using Tapatalk

Cozume said:
Who releases the sbf? Motorola? Because it looks like the problem is that no one can find the sbf for the 4.2.2 postcamera update for their carrier.
Click to expand...
Click to collapse
Skrilax_CZ maintains the website where the SBF's are stored. Motorola only releases the Developer Edition images to the public, as far as I know. So I believe that this website hosts either his own custom made zips, or he has someone supplying him with insider Moto images (or he works there?).
Personally I think he has a tool to automate this process once he has the firmware loaded onto the phone (if he doesn't have the images already), basically he is adb copying files from the dev partition of his phone and compiling a MD5 hash for each file, then zipping it all up in a nice package to flash with the insider Moto tool RSD Lite (or using manual flash, if you like to live dangerously )

mastarifla said:
Skrilax_CZ maintains the website where the SBF's are stored, as far as I know, Motorola only releases the Dev edition images to the public. So I believe that this website hosts either his own custom made zips, or he has someone supplying him with insider Moto images (or he works there?).
Personally I think he a tool to automate this process once he has the firmware loaded onto the phone (if he doesn't have the images already), basically he is adb copying files from the dev partition of his phone and compiling a MD5 hash for each file, then zipping it all up in a nice package to flash with the insider Moto tool RSD Lite.
Click to expand...
Click to collapse
Thanks! So if you know someone with a stock phone who has never modded or rooted, theoretically you could pull the files from the dev partition of their phone? The trick is getting it into a package that works with RSD Lite?
---------- Post added at 08:56 PM ---------- Previous post was at 08:55 PM ----------
mastarifla said:
Motorola only releases the Developer Edition images to the public, as far as I know.
Click to expand...
Click to collapse
So those of us with Dev Eds should stick to flashing the factory images we get from Motorola directly?

Cozume said:
Thanks! So if you know someone with a stock phone who has never modded or rooted, theoretically you could pull the files from the dev partition of their phone? The trick is getting it into a package that works with RSD Lite?
---------- Post added at 08:56 PM ---------- Previous post was at 08:55 PM ----------
So those of us with Dev Eds should stick to flashing the factory images we get from Motorola directly?
Click to expand...
Click to collapse
Theoretically yes, but in practice it is much harder. Every manufacturer stores their particular data in different partitions on the phone. You have to manually look through the bin files (with a hex editor) in order to determine which are the correct ones. This is even more difficult because most of the information is encrypted. So unless you have insider knowledge or want to compare values in a hex editor, I would strongly suggest you stay away from attempting to make your own files, it can lead to very easy bricks.
I have a XT1053 Unlocked GSM phone (T-Mobile), and the SBF T-Mobile firmwares are the only thing I am going to be flashing, don't flash other regions firmware unless you are certain that it works. IE. let everyone else try it and potentially brick their phone before you end up doing the same thing.
Oh and before I forget, hitting the thanks button works too by the way

mastarifla said:
Theoretically yes, but in practice it is much harder. Every manufacturer stores their particular data in different partitions on the phone. You have to manually look through the bin files (with a hex editor) in order to determine which are the correct ones. This is even more difficult because most of the information is encrypted. So unless you have insider knowledge or want to compare values in a hex editor, I would strongly suggest you stay away from attempting to make your own files, it can lead to very easy bricks.
Click to expand...
Click to collapse
no, I would never try it; I am just trying to understand what the differences are between the various ways for me to brick my device, lol!
mastarifla said:
I have a XT1053 Unlocked GSM phone (T-Mobile), and the SBF T-Mobile firmwares are the only thing I am going to be flashing, don't flash other regions firmware unless you are certain that it works. IE. let everyone else try it and potentially brick their phone before you end up doing the same thing.
Click to expand...
Click to collapse
but if I have a Dev Ed, shouldn't I be flashing the factory images I received from Motorola?
mastarifla said:
Oh and before I forget, hitting the thanks button works too by the way
Click to expand...
Click to collapse
I know I tried but they limit you to 8 thanks a day and I already used mine up for today! I will come back tomorrow and hit the button, promise. I am very good about that. So good that I use up all my thanks quickly. So odd they do that here, but they do.

Cozume said:
but if I have a Dev Ed, shouldn't I be flashing the factory images I received from Motorola?
Click to expand...
Click to collapse
Yes you should, however it is widely known that the T-Mobile version and the Developer Edition have the exact same hardware/firmware (XT1053), actually I think they may have the exact same software build as well, though I am not sure on that one... if they receive the same OTA update that the T-Mobile version receives, that leads me to believe its the same ROM.

[Q] 1.54.651.8 Root

Got my M8 at the Sprint store today and of course they ran the update to 1.54.651.8. Can anyone tell me if this is I can still obtain root with the update using BD619's method?
http://forum.xda-developers.com/showthread.php?t=2698394
Thanks!!!

Yes, you can still root.
Sent from my EVO LTE

FinZ28 said:
Yes, you can still root.
Sent from my EVO LTE
Click to expand...
Click to collapse
Thanks FinZ

Glad to help. Keep in mind that the root method generally doesn't change, but the S-off method may. So far, looks like Firewater works for the original software version that came on the phone, as well as the OTA.
Sent from my EVO LTE

Why would they take it out of the box, much less run an update on it?
We'd be fighting.

Can I ask you fellas a question. I'm still running stock but I'm rooted and s-off. I keep getting the system update and I want to accept the update because it adds the extreme power saver to my Sprint M8. If I do exactly how do reroot. I know I'll stay S-off. Thanks in advance.
One method1911

Why not just flash the stock rooted rom
Sent from my 831C using XDA Premium 4 mobile app

METHOD1911 said:
Can I ask you fellas a question. I'm still running stock but I'm rooted and s-off. I keep getting the system update and I want to accept the update because it adds the extreme power saver to my Sprint M8. If I do exactly how do reroot. I know I'll stay S-off. Thanks in advance.
One method1911
Click to expand...
Click to collapse
I think Captain Throwback has a stock rooted ROM based off the latest OTA. I would flash that, instead. Too much trouble if you choose the other route.
Sent from my EVO LTE

FinZ28 said:
I think Captain Throwback has a stock rooted ROM based off the latest OTA. I would flash that, instead. Too much trouble if you choose the other route.
Sent from my EVO LTE
Click to expand...
Click to collapse
Flash the rom along with the firmware.
But if you wanted to flash the update from sprint it's not that hard. You would need Sprints stock recovery flashed on your device (it's in one of Captains threads) and your software would need to have all of the files the OTA wants to update since it fails if it doesn't find all the files it is changing. Other than that take the update, let it finish and boot up, and then flash twrp (or cwm), flash SU, and you're back to rooted.

henderjr said:
Flash the rom along with the firmware.
But if you wanted to flash the update from sprint it's not that hard. You would need Sprints stock recovery flashed on your device (it's in one of Captains threads) and your software would need to have all of the files the OTA wants to update since it fails if it doesn't find all the files it is changing. Other than that take the update, let it finish and boot up, and then flash twrp (or cwm), flash SU, and you're back to rooted.
Click to expand...
Click to collapse
Yeah, forgot to mention flashing the new firmware. Good looking out:thumbup:
Sent from my EVO LTE

Rookie Mistake!
Just for the record I took the Update. Not realizing that the firmware was going to be updated as well. My bad, now I can't even unlock my bootloader, I get an error message(pwr/vol.dn). I also tried to using cmd(adb) error message cannot 'flash' Now what? I usually root my devices on day one. oh well. Noob I am not.:confused a I am...
Any Ideas?
Sprint HTC M8

Star2dn said:
Just for the record I took the Update. Not realizing that the firmware was going to be updated as well. My bad, now I can't even unlock my bootloader, I get an error message(pwr/vol.dn). I also tried to using cmd(adb) error message cannot 'flash' Now what? I usually root my devices on day one. oh well. Noob I am not.:confused a I am...
Any Ideas?
Sprint HTC M8
Click to expand...
Click to collapse
Shouldn't matter if you took the update
HTC Dev will unlock your bootloader unless Sprint blocked it like what happened to Verizon...they blocked folks from using HTC Dev.

I took the update a couple days ago, and just rooted last night. Htcdev worked fine for me. Followed this video:
Root the Sprint HTC One M8: http://youtu.be/wy8Htj2YL4E
Sent from my 831C using xda app-developers app

Got It
Late last night I tried out Hasoon2000's (EASY) ALL-IN-ONE KIT. It got me rooted. Always did it manually never had any issue before, oh well I'm rooted that's what matter.
Thanks for the feedback
And a big thanks to Hasoon2000's.
Great Work!
lol

Stuck at Firmware update

Hey guys. Was playing around and I think I flashed wrong image to my FLEX (USA-SPRINT-KK).
Now, it shows LG, then flashes green light over and over. I have got it into FIRMWARE UPDATE SCREEN. Do I use ADB, or what to reflash back to stock JB or KK? Thanks

Now you just follow the guide to return to stock
http://forum.xda-developers.com/showthread.php?t=2644083
Sent from my iPhone using Tapatalk

kintwofan said:
Now you just follow the guide to return to stock
http://forum.xda-developers.com/showthread.php?t=2644083
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
OK...Got all the stuff, but I must have flashed wrong firmware to phone at first. Model says D950 (ATT) when it should be D995 (Sprint). So when I attempt to flash, it tells me wrong model.

Stock Unrooted?

Hi all, I just got back from basic training at Fort Jackson, I had rooted my phone before leaving and now I want to go back to stock, looking around I haven't seen anything and the one I did see was taken down due to hard bricking. So is there any way to go back to full stock Unrooted.

H4rryTipp3r said:
Hi all, I just got back from basic training at Fort Jackson, I had rooted my phone before leaving and now I want to go back to stock, looking around I haven't seen anything and the one I did see was taken down due to hard bricking. So is there any way to go back to full stock Unrooted.
Click to expand...
Click to collapse
U Can unroot Your Device By Installling Stock Rom But First U should backup your efs partition and then u are ready for stock process download stock rom from sammobile for your country and make sure that it is for your device and for your country also and then download it then flash it with odin
Sent from my SM-T111 using XDA Forums

I would recommend using the LG flash tool and flashing the 10n kdz.

Vseprz said:
I would recommend using the LG flash tool and flashing the 10n kdz.
Click to expand...
Click to collapse
so I'll be safe to flash that even though I'm on this?

H4rryTipp3r said:
so I'll be safe to flash that even though I'm on this?
Click to expand...
Click to collapse
Yes, you can upgrade from the 10h to 10n, but you should not downgrade from 10n to 10h as there is a rollback flag that will prevent loading the stagefright vulnerable 10h and brick your phone.