There are a lot of people joining xda on daily basis, and there are a lot of repetitive questions being asked which fill up Development threads. Point them here. Feel free to ask or answer questions. Idea of this thread is to get users to help other users with their problems/questions. Please do not spoon feed, but rather point in the direction where that user can find an answer and educate himself
First thing first. I strongly advise you to read THIS thread before posting ANYTHING on XDA.
Then, have a quick look at the names of threads in post no2, you might find what you need right away.
For ROM issues please do mention in your post about:
ROM name
ROM version and base
kernel version and its settings
any mods applied on top of it
flashing "style" aka dirty or clean
something like this
...and be sure you have asked before on the ROM thread unless you have less than 10 posts on XDA
Third. Even if you do get your question answered, please, do come back and read threads in post no2 (coming later as soon as we start getting the guides) to educate yourself. You'll be surprised how much time and frustration it will save you in the future.
ASK ANY QUESTION HERE,adb, drivers, superCID etc...... You will either get an answer or will get pointed in the right direction.
No abuse towards noobs tolerated here! No question is stupid in this thread.
***I feel that a little OT is healthy to the success of this type of thread. The people here who help the most will develop a comradery therefore OT is allowed within reason. Common sense will be applied ***
Credits to @xanthrax who made the original nexus 4 thread where i got inspired! :highfive:
Great idea!!! And well needed! :good::good:
Darth said:
Great idea!!! And well needed! :good::good:
Click to expand...
Click to collapse
Thanks i hope we can fill this up quickly! Just share it!
Enviado desde mi XT1060 mediante Tapatalk
Sorry I am a noob.
Currently i am using kitkat 4.4.4.
I wanted to know if i Root my phone will i get the lollipop update that will be officially launched for the phone ??
4yush said:
Currently i am using kitkat 4.4.4.
I wanted to know if i Root my phone will i get the lollipop update that will be officially launched for the phone ??
Click to expand...
Click to collapse
yes, you will get the update. but the installation fails
I have got tired of waiting for official update and have decided to root my moto x on 4.4.4.
This is what I understood.
1 . unlock bootloader
2. Install twrp
3. Install rom.
I would want to know if I can flash BlissPop directly after the above steps.
Also can kernels be flashed directly from recovery or they have to be flashed using pc like my xperia did
4yush said:
Currently i am using kitkat 4.4.4.
I wanted to know if i Root my phone will i get the lollipop update that will be officially launched for the phone ??
Click to expand...
Click to collapse
To root on 4.4.4 you need an unlocked (or unlockable) bootloader. An unlocked bootloader phone roots by flashing custom recovery.
If you try to take an OTA without stock recovery on your phone, you'll get stuck in a bootloop (fastboot earase cache will get you out of it), and can not apply an OTA. Further, if while rooted you modify /system, certain files, or other parts of the phone too much while rooted, the OTA could fail its pre-flash validation checks, thus preventing it from installing.
Then again, those who use SlapMyMoto/RockMyMoto/PwnMyMoto or other HACKS to root their phone with locked bootloader, could also run into issues with the OTA's pre-flash validation checks causing the OTA Update to fail too. However, those old processes don't work on 4.4.4 as the vulnerabilities they used are patched.
If you have an unlocked bootloader, root your phone by flashing TWRP (or CWM, etc) and installing SuperSU, then flash stock recovery back on, and run rooted with apps installed that use root, like RootExplorer, Wifi Tether for Root, Greenify, etc. You can take the OTA just fine.
Note: If you install something like Xposed, it will cause the Pre-flash vaildations to fail because it does modify things the pre-flash checks look for. You'd have to disable it, which involves having 3rd party recovery, and flashing the disable.zip (on your phone as /SDcard/Android/data/de.robv.android.xposed.installer/files/Xposed-Disable-Recovery.zip), then put stock recovery back on.
adity said:
I have got tired of waiting for official update and have decided to root my moto x on 4.4.4.
This is what I understood.
1 . unlock bootloader
2. Install twrp
3. Install rom.
I would want to know if I can flash BlissPop directly after the above steps.
Also can kernels be flashed directly from recovery or they have to be flashed using pc like my xperia did
Click to expand...
Click to collapse
If BlissPop is a custom ROM then yes after all of those steps you can flash it directly, I'll suggest to make a nandroid backup before. And then to get some gapps for that ROM. And kernels can be flashed directly on recovery too! Good luck!
Enviado desde mi XT1060 mediante Tapatalk
Should this have to be sticky?
Enviado desde mi XT1060 mediante Tapatalk
Using blisspop which is based on cm12 and mobile standby is using abnormal amounts of battery(75%)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
adity said:
Using blisspop which is based on cm12 and mobile standby is using abnormal amounts of battery(75%)
Click to expand...
Click to collapse
I think battery life on custom ROM is very bad compared to stock, I'm back at it because of that and for moto features.
Enviado desde mi XT1060 mediante Tapatalk
Making a bump to everyone can see this post!
Enviado desde mi XT1060 mediante Tapatalk
Moto X - No Signal?
So I got the Verizon XT1060 a couple of days back, put my SIM in and everything was working fine for a couple of days. Made a few calls, texted a bunch. Everything was good.
Never really got a chance to check how data worked since I was always on WiFi but yesterday when I tried making the mobile internet work it just wouldn't . I have a 3G connection, so I thought might as well give it a shot and started putting in the APNs in according to what my provider said. I came across a post that said you can't select just 3G for the XT1060 and you'd have to install this app called PhoneInfo(Ad) to make 3G only work.
So I installed the app. Set it to WCDMA only. And restarted the phone. Ever since then my phone has been on no-signal. Can't make calls/texts. No bars. I can read stuff on the SIM card just fine though. Today I went and got a new SIM Card hoping it'll work. But nothing. Zilch. Factory reset multiple times. Just no signal at all. In About Phone, in status information, the network shows up as unknown.
I don't exactly know what the problem is here. I talked to my provider and they said everything was fine on their end and I should check if my model is compatible. Which it is. At least for EDGE, if not for 3G. If phone was receiving signals and all before, then that definitely means it was compatible, right?
Any way. I'm based in Islamabad, Pakistan. And the phone is a Verizon XT1060 16GB. This is the only phone I have right now and I REALLY need to get this phone working asap.
I'm going to try and flash the stock image onto it. The phone was running stock VZW 4.4.4 and is not the dev edition. So I can't root.
Any suggestions or ideas are welcome.
Thank You.
NadirChaudhry said:
So I got the Verizon XT1060 a couple of days back, put my SIM in and everything was working fine for a couple of days. Made a few calls, texted a bunch. Everything was good.
Never really got a chance to check how data worked since I was always on WiFi but yesterday when I tried making the mobile internet work it just wouldn't . I have a 3G connection, so I thought might as well give it a shot and started putting in the APNs in according to what my provider said. I came across a post that said you can't select just 3G for the XT1060 and you'd have to install this app called PhoneInfo(Ad) to make 3G only work.
So I installed the app. Set it to WCDMA only. And restarted the phone. Ever since then my phone has been on no-signal. Can't make calls/texts. No bars. I can read stuff on the SIM card just fine though. Today I went and got a new SIM Card hoping it'll work. But nothing. Zilch. Factory reset multiple times. Just no signal at all. In About Phone, in status information, the network shows up as unknown.
I don't exactly know what the problem is here. I talked to my provider and they said everything was fine on their end and I should check if my model is compatible. Which it is. At least for EDGE, if not for 3G. If phone was receiving signals and all before, then that definitely means it was compatible, right?
Any way. I'm based in Islamabad, Pakistan. And the phone is a Verizon XT1060 16GB. This is the only phone I have right now and I REALLY need to get this phone working asap.
I'm going to try and flash the stock image onto it. The phone was running stock VZW 4.4.4 and is not the dev edition. So I can't root.
Any suggestions or ideas are welcome.
Thank You.
Click to expand...
Click to collapse
Do you know which exactly are the bands your network uses? And I have stock ROM too and I get the 3G only option without the use of an external app. See here.
Enviado desde mi XT1060 mediante Tapatalk
Used Moto X What to look at.
Hello! (second post after saying hello on the corresponding post).
Please my native language is spanish so forgive my mistakes if any.
Going to the point and abusing the "ask ANY question" theme,
¿What to look in a Used Moto x?
In other words, here in Argentina phone are really expensive, and i have the chance to buy a Moto x really cheap.
Besides the obvious scraches, marks, screen details, and checking battery status and life. What else should i look? Any specific serial, date of production? any data?
Also i ad one more question.
As far as i understood with this post http://forum.xda-developers.com/moto-x/general/one-stop-shop-how-root-moto-x-confusion-t2826159 if i have a 4.4.4 Phone all will be useless since there is no Rooting or bootunlock.
In any other cases there is some way to get root acess and also could get bootunlock (did i understood correctly?)
Also Unlocked boot would give me the chance to install a new operating system (Cyanogen mod or whatever)
Root would only give me the chance to uninstall app and so.
Thanks for all your answers!
Kind Regards!
cabe72000 said:
Besides the obvious scraches, marks, screen details, and checking battery status and life. What else should i look? Any specific serial, date of production? any data?
Click to expand...
Click to collapse
I've seen no evidence that any date range or serial number range is better than another.
One thing i would look for is... If you have the option to find out what ROM and bootloader is on the phone, that is helpful.
ROM: On the phone, go App Drawer -> Settings... Make note of what is listed under System Version, Android Version, and build number.
Bootloader: check by Booting the X into Bootloader/Fastboot mode, and make note of the second line on the screen.
30.70 = original 4.2.2
30.71 = 4.2.2 OTA with camera update
30.B2 = 4.4
30.B4 = 4.4.2
30.B7 = 4.4.4
The android version and bootloader version should match, otherwise it means someone was experimenting when they were flashing, and if you buy that phone you definitely make sure you fully flash the correct SBF onto the phone to bring everything in line. (I would ask the owner to do it BEFORE you buy, so if something goes wrong while flashing, you aren't the one bricking the phone).
cabe72000 said:
As far as i understood with this post http://forum.xda-developers.com/moto-x/general/one-stop-shop-how-root-moto-x-confusion-t2826159 if i have a 4.4.4 Phone all will be useless since there is no Rooting or bootunlock.
In any other cases there is some way to get root acess and also could get bootunlock (did i understood correctly?)
Also Unlocked boot would give me the chance to install a new operating system (Cyanogen mod or whatever)
Root would only give me the chance to uninstall app and so.
Click to expand...
Click to collapse
Read further in that thread... like what I posted -> http://forum.xda-developers.com/mot...w-root-moto-x-confusion-t2826159/post54671918
So when you get your X, try to get the unlock code from Moto's web site. Then.... If you can get the code, and unlock the bootloader, you can root and disable write protection no matter what ROM is on your phone.
Moto gives the bootloader unlock code for most 2013 X's, its only a few carriers they don't give them for.
For Example: While Moto doesn't give out the Unlock Code for the ATT XT1058, they do give out the unlock code for the XT1058 from Rogers in Canada. So if you are buying a used Rogers XT1058 you can unlock the bootloader for free. The same holds true with nearly every XT1052, XT1053, and XT1056 I've seen (moto gives the bootloader unlock code on their web site).
Another thing to keep in mind, IF you get a model from a carrier that Moto doesn't give out the bootloader unlock code for, If the phone and its bootloader are still on 4.4.2/30.B4 or below, you can use Sunshine to unlock the bootloader.
Unlocking the bootloader will allow you to flash 3rd party or custom Recoveries, Roms, parts, etc. (so CM12, etc) With a locked bootloader, you can only flash ROMS/Parts which have been digitally signed by Moto and are for your particular Phone Model and Carrier combo. (The CID comes into play).
Rooting will allow you some access and control over /system and other files that are usually inaccessible to normal users. It doesn't allow you to flash 3rd party roms and pieces,etc. If you have a LOCKED bootloader, you basically need to find and exploit a flaw or vulnerability in the phone, or its software. i.e. Hack It , if you want root. Right now, with 4.4.4 and a locked bootloader, there are no vulnerabilities which can gain root, that is why having an unlocked or unlockable bootloader is so important. For more see -> http://mark.cdmaforums.com/MotoX-Locked.html
KidJoe said:
I've seen no evidence that any date range or serial number range is better than another.
One thing i would look for is... If you have the option to find out what ROM and bootloader is on the phone, that is helpful.
ROM: On the phone, go App Drawer -> Settings... Make note of what is listed under System Version, Android Version, and build number.
Bootloader: check by Booting the X into Bootloader/Fastboot mode, and make note of the second line on the screen.
30.70 = original 4.2.2
30.71 = 4.2.2 OTA with camera update
30.B2 = 4.4
30.B4 = 4.4.2
30.B7 = 4.4.4
The android version and bootloader version should match, otherwise it means someone was experimenting when they were flashing, and if you buy that phone you definitely make sure you fully flash the correct SBF onto the phone to bring everything in line. (I would ask the owner to do it BEFORE you buy, so if something goes wrong while flashing, you aren't the one bricking the phone).
Read further in that thread... like what I posted -> http://forum.xda-developers.com/mot...w-root-moto-x-confusion-t2826159/post54671918
So when you get your X, try to get the unlock code from Moto's web site. Then.... If you can get the code, and unlock the bootloader, you can root and disable write protection no matter what ROM is on your phone.
Moto gives the bootloader unlock code for most 2013 X's, its only a few carriers they don't give them for.
For Example: While Moto doesn't give out the Unlock Code for the ATT XT1058, they do give out the unlock code for the XT1058 from Rogers in Canada. So if you are buying a used Rogers XT1058 you can unlock the bootloader for free. The same holds true with nearly every XT1052, XT1053, and XT1056 I've seen (moto gives the bootloader unlock code on their web site).
Another thing to keep in mind, IF you get a model from a carrier that Moto doesn't give out the bootloader unlock code for, If the phone and its bootloader are still on 4.4.2/30.B4 or below, you can use Sunshine to unlock the bootloader.
Unlocking the bootloader will allow you to flash 3rd party or custom Recoveries, Roms, parts, etc. (so CM12, etc) With a locked bootloader, you can only flash ROMS/Parts which have been digitally signed by Moto and are for your particular Phone Model and Carrier combo. (The CID comes into play).
Rooting will allow you some access and control over /system and other files that are usually inaccessible to normal users. It doesn't allow you to flash 3rd party roms and pieces,etc. If you have a LOCKED bootloader, you basically need to find and exploit a flaw or vulnerability in the phone, or its software. i.e. Hack It , if you want root. Right now, with 4.4.4 and a locked bootloader, there are no vulnerabilities which can gain root, that is why having an unlocked or unlockable bootloader is so important. For more see -> http://mark.cdmaforums.com/MotoX-Locked.html
Click to expand...
Click to collapse
Thanks for your answer!!
Im sure that the actual owner knows nothing about Android, what im trying to say is that he didn't even know how to root or check software updates.
Besides that, what you answered to me is what i was looking for. On monday i have access to the phone so i will check everything you told me.
Tell you the news on Monday.
Muchas gracias!! (Thank you very much)
EDIT: Kidjoe Where do you work to have such a list of phones??? I work on Automotive industry and i drive maybe 5 o 6 cars but your's is incredibly long! hehe (sorry offtopic but i was amazed with the list )
cabe72000 said:
EDIT: Kidjoe Where do you work to have such a list of phones??? I work on Automotive industry and i drive maybe 5 o 6 cars but your's is incredibly long! hehe (sorry offtopic but i was amazed with the list )
Click to expand...
Click to collapse
I've been using cell phones since 1992... There was a period in there, for personal, that I was part of a Verizon Wireless customer "focus group" known as the VerizonWireless Customer Council, so many of my PERSONAL phones were acquired that way (for free).
Long story short... I worked for one global company for just a week shy of 20 yrs. While always a field employee needing mobility to do my job, for about the last 7 or 8 years, my focus was shifted to doing a lot of work in the mobility support space. The current company I'm working for (also global), I've been a part of the Tier 3/4 Mobility Support team, supporting our network, MDM solution, etc for our employees. We also take part in the design... so I have to have all, or as many as I can, of the devices we allow our employees to have. I often times joke that my job is being paid to play with my toys
KidJoe said:
I've been using cell phones since 1992... There was a period in there, for personal, that I was part of a Verizon Wireless customer "focus group" known as the VerizonWireless Customer Council, so many of my PERSONAL phones were acquired that way (for free).
Long story short... I worked for one global company for just a week shy of 20 yrs. While always a field employee needing mobility to do my job, for about the last 7 or 8 years, my focus was shifted to doing a lot of work in the mobility support space. The current company I'm working for (also global), I've been a part of the Tier 3/4 Mobility Support team, supporting our network, MDM solution, etc for our employees. We also take part in the design... so I have to have all, or as many as I can, of the devices we allow our employees to have. I often times joke that my job is being paid to play with my toys
Click to expand...
Click to collapse
My wife has forbid me to get another phone for a couple years.... Lol
Moto X, N5 and M8 in a year. Though, she's in love with the hand me down moto X... It finally got her off her iPhone 4s. So she benefited from my whims.
So I'm stuck for awhile. ?
I did find a solution to the battery problem.
Thing is google keeps data on even when wifi is connected for the handofff feature. So I make sure that I turn off data while at home.
Since then I have been having great battery life.. Even better than stock, more than 4 hours screen time
Related
Why can't those of us who have locked phones just flash the developer's edition OS? By the time I learned of the Developer's edition phone, I had already passed my 14 business days return of my phone. The long root process is a bit much for me... If there is no other way, I'll give it a try though...
I'm not exactly sure how Motorola's bootloader works, but I'm pretty sure the Developer Edition is signed with different keys and will possibly be a different size. Motorola's bootloader I'm sure checks these things and will deny it.
The bootloader is not part of the OS, it's a different thing all on its own.
It really does seem as simple as you said OP but there's been plenty of phones with locked bootloaders, if it was as simple as that, there wouldn't need to be SafeStrap and other bypasses / exploits.
If you haven't looked at JCase's new SlapMyMoto 1.0 root method, it is more simple than the previous versions. It still requires going back to 4.2.2 camera OTA and losing all your data, but some of the ADB/Fastboot steps were removed and simplified, from what I've seen.
OK after a lot of sweat, I was able to get back to 4.2.2. How do I know if I have the camera patch?
jideay said:
OK after a lot of sweat, I was able to get back to 4.2.2. How do I know if I have the camera patch?
Click to expand...
Click to collapse
If you followed the instructions in the root guide and used the proper SBF to get back to 4.2.2, you should have the update. It links directly to the correct SBF for the root process.
http://forum.xda-developers.com/showthread.php?t=2538896
jideay said:
Why can't those of us who have locked phones just flash the developer's edition OS? By the time I learned of the Developer's edition phone, I had already passed my 14 business days return of my phone. The long root process is a bit much for me... If there is no other way, I'll give it a try though...
Click to expand...
Click to collapse
Depending on the model of you phone you can flash the developer edition rom,
XT1060, Verizon Retail, Moto Maker or Developer edition can flash the same Developer Edition recovery images direct from Moto's web site.
XT1053, GSM Developer or T-Mobile USA can use the GSM Developer recovery images direct from Moto's web site.
BUT this won't impact your ability to unlock your phone's bootloader.
(If you don't believe me that the rom is the same, Do a FC /B of all files contained inside the developer edition recovery images requested from Moto's web site with those inside the roms/images downloaded from http://sbf.droid-developers.org/phone.php?device=0 and you will see other than the XML, all files are identical. And the XML just tells RSDLite what to flash. Also when you request the GSM Developer Edition recovery files, you get a file named.. TMO_RETAIL_XT1053_4.4-13.11.1Q2.X-69-3_MR2_1FF.xml.zip )
Well, after a day and half of sweating, and a few hours there where I thought I bricked it, it's rooted on 4.4. I have rooted every android phone I've ever had, and this was by far the hardest... But i'm really happy with it. Got the wifi tether going and life is good. Thanks everyone for your replies...
jideay said:
Well, after a day and half of sweating, and a few hours there where I thought I bricked it, it's rooted on 4.4. I have rooted every android phone I've ever had, and this was by far the hardest... But i'm really happy with it. Got the wifi tether going and life is good. Thanks everyone for your replies...
Click to expand...
Click to collapse
This was surely the most involved root I've done. I think it's partially because I got this phone much close to launch than my previous devices. They all had one click root methods available by the time I tried.
fury683 said:
This was surely the most involved root I've done. I think it's partially because I got this phone much close to launch than my previous devices. They all had one click root methods available by the time I tried.
Click to expand...
Click to collapse
True the X hasn't been out long, and to complicate that more, 3 roms have been there for it... release, first OTA with camera fix, and Kit Kat...
Combine that with newer phones being harder to root... and yeah, one click root method isn't a reality at this point.
Does new phone come with JB? If so should I stay with it and not to accept OTA?
It seems that Kitkat update introduced several issues (problem with email syncing, bluetooth incompatibility wit some cars, etc). Is there anything else? I am fine with not having the latest and greatest.
Also: is it possible to downgrade Moto X DE (GSM) back to JB? I am not 100% sure from reading this forum.
The kit Kat update had issues but nothing on the scale of the Samsung galaxy family's 4.3 update. I haven't noticed any issue on mine nor any on customers. Totally worth upgrading it.
Sent from my Lumia 928
The only issue I am having with mine is that while it says its connected to web (either lte or wifi) it won't actually connect. A reboot fixes the issue until it comes back.
texanman said:
The only issue I am having with mine is that while it says its connected to web (either lte or wifi) it won't actually connect. A reboot fixes the issue until it comes back.
Click to expand...
Click to collapse
Did you have this issue while on JB?
Dont know as mine came with 4.4 which did not have this weird issue. It may be something I installed so a wipe may be in order.
Go to KK, no question
tapped out via XT1053 DE
The only issue I had was Google maps not showing my direct location with high accuracy on. It was hard for me to distinguish if I needed to go right or left then it has a hard time rerouting. Which pissed my wife off lol.
MOTO X Slapped
It will come with KitKat, and good luck not bricking the phone trying to downgrade it.
sent via tapatalk
Don't forget text reflow has been deprecated. Major loss in browsers and reading apps.
Sent from my XT1053 using HoFo mobile app.
---------- Post added at 07:45 AM ---------- Previous post was at 07:36 AM ----------
@rbiter said:
Don't forget text reflow has been deprecated. Major loss in browsers and reading apps. Blink is in web view. Also means invert lost.
Sent from my XT1053 using HoFo mobile app.
Click to expand...
Click to collapse
Sent from my XT1053 using HoFo mobile app.
eksasol said:
It will come with KitKat, and good luck not bricking the phone trying to downgrade it.
sent via tapatalk
Click to expand...
Click to collapse
Mine arrived with 4.2.2 installed, (2 weeks ago) and it took two updates to get to 4.4, 1'st 4.2.2 then 4.4. No regrets on the update for me, but then again I let the updates fly when I turned on the phone.
eksasol said:
It will come with KitKat, and good luck not bricking the phone trying to downgrade it.
sent via tapatalk
Click to expand...
Click to collapse
Just got my vzw DE wednesday, 2/12/2014. Came with 4.2.2 pre-camera update. soon as it booted it took the 4.2.2 camera update, then shortly after that came 4.4. did all the updates then unlocked the bootloader, installed twrp and rooted. happy as a clam!
Teksu said:
Just got my vzw DE wednesday, 2/12/2014. Came with 4.2.2 pre-camera update. soon as it booted it took the 4.2.2 camera update, then shortly after that came 4.4. did all the updates then unlocked the bootloader, installed twrp and rooted. happy as a clam!
Click to expand...
Click to collapse
let me make this blunt before you even get your phone
your phone is a DE so you can root any version
is you come with 4.2.2 camera update or 4.4 you can upgrade and downgrade between thouse two versions only
if your phone comes with 4.4.2 you can not downgrade at all so just root it and enjoy because most people are trying to get there and bricking there phones half the time.
if you have any other question please post or PM me
dray_jr said:
let me make this blunt before you even get your phone
your phone is a DE so you can root any version
is you come with 4.2.2 camera update or 4.4 you can upgrade and downgrade between thouse two versions only
if your phone comes with 4.4.2 you can not downgrade at all so just root it and enjoy because most people are trying to get there and bricking there phones half the time.
if you have any other question please post or PM me
Click to expand...
Click to collapse
That makes it very clear. But can you elaborate on why downgrade from 4.4.2 is not possible? I currently use rooted Droid Incredible on Verizon with CM 7.1 and if I am not mistaken I can flash pretty much any previous ROM I want (I really haven't tinkered with it for last couple of years, so I may be wrong).
JoeSchmoe007 said:
That makes it very clear. But can you elaborate on why downgrade from 4.4.2 is not possible? I currently use rooted Droid Incredible on Verizon with CM 7.1 and if I am not mistaken I can flash pretty much any previous ROM I want (I really haven't tinkered with it for last couple of years, so I may be wrong).
Click to expand...
Click to collapse
Moto changed the bootloader in 4.4.2 and they dont allow you to downgrade
Moto X DE - mine coming soon as well - some questions
dray_jr said:
Moto changed the bootloader in 4.4.2 and they dont allow you to downgrade
Click to expand...
Click to collapse
My VZW Moto X DE is on its way to me, and I've spent a bunch of time on the forums yet still have the following questions and hope you can help. My current phone is an original Droid Incredible, which I rooted, mostly for recovery, backups, tethering, and system monitoring. This site was a great resource back when I did that and I greatly appreciated the information.
RE: the Moto X, I've read the steps for unlocking the bootloader and which paths for upgrading/downgrading are safe given the release shipped with the phone. That information was for the standard Moto X. If the DE is unlocked, can I just go straight to rooting the phone? If the OTA updates won't work with root, is it best to accept the latest OTA pushes once my phone is online and then root? I want to be clear about what I've gained by getting the DE edition. Why go back to 4.4.2 if it ships with a later release?
I have no plans in the near future for changing ROM's. I'd just like to initially install what I am using on the Incredible - the clockworkmod recovery app (or current equivalent), titanium backuip, and a good tethering program. I currently use android wifi tether.
Thanks for any help.
dmm108 said:
My VZW Moto X DE is on its way to me, and I've spent a bunch of time on the forums yet still have the following questions and hope you can help. My current phone is an original Droid Incredible, which I rooted, mostly for recovery, backups, tethering, and system monitoring. This site was a great resource back when I did that and I greatly appreciated the information.
RE: the Moto X, I've read the steps for unlocking the bootloader and which paths for upgrading/downgrading are safe given the release shipped with the phone. That information was for the standard Moto X. If the DE is unlocked, can I just go straight to rooting the phone? If the OTA updates won't work with root, is it best to accept the latest OTA pushes once my phone is online and then root? I want to be clear about what I've gained by getting the DE edition.
I have no plans in the near future for changing ROM's. I'd just like to initially install what I am using on the Incredible - the clockworkmod recovery app (or current equivalent), titanium backuip, and a good tethering program. I currently use android wifi tether.
Thanks for any help.
Click to expand...
Click to collapse
I have a dev ed and keep mine the same way you intend... What I've gleaned so far is that the each update includes a new bootloader version that cannot be downgraded, i.e. if you take 4.4.2 you cannot downgrade to 4.4. At this point the VZW version only has 4.4.
As far as getting the phone to how you want it after you take the upgrades the material in the following two links should get you right where you want to be...
Custom recovery...
http://forum.xda-developers.com/showthread.php?t=2424110
Verizon boot animation and tether hack...
http://forum.xda-developers.com/showthread.php?t=2645343
He kind of muddied it up by adding other cleanup tools that I'm not interested in, if you're like me and only want the tether hack you will need to go to the 140.45.5 folder in his link and download xt1060-140.45.5-vzw-removal-s.zip He also has an undo zip that you might want to download and stash away just in case.
This part is speculative and potentially dangerous so take with a grain of salt and correct me if I'm wrong.
My understanding is that the big issue from the downgrade is that there will be a partition table mismatch if one takes an OTA upgrade and the phone will be bricked, though I can find nothing solid on this. Being that I plan on keeping a custom recovery I don't have to worry about accidentally taking an OTA and for some reason prefer to have the ability to downgrade, when 4.4.2 comes out I'm going to try to flash everything but the bootloader and I believe the partition table, (I need to read more and understand more before I speak with authority) to see if I can get away with it.
Also, on a side note, I found that freezing pre installed apps/bloat destroyed the wonderful battery life I was getting so I would suggest you keep your phone stock for a few days to get a feel for how the phone behaves before you begin freezing bloat.
Enjoy your new toy!
edthesped said:
I have a dev ed and keep mine the same way you intend... What I've gleaned so far is that the each update includes a new bootloader version that cannot be downgraded, i.e. if you take 4.4.2 you cannot downgrade to 4.4. At this point the VZW version only has 4.4.
As far as getting the phone to how you want it after you take the upgrades the material in the following two links should get you right where you want to be...
Custom recovery...
http://forum.xda-developers.com/showthread.php?t=2424110
Verizon boot animation and tether hack...
http://forum.xda-developers.com/showthread.php?t=2645343
He kind of muddied it up by adding other cleanup tools that I'm not interested in, if you're like me and only want the tether hack you will need to go to the 140.45.5 folder in his link and download xt1060-140.45.5-vzw-removal-s.zip He also has an undo zip that you might want to download and stash away just in case.
This part is speculative and potentially dangerous so take with a grain of salt and correct me if I'm wrong.
My understanding is that the big issue from the downgrade is that there will be a partition table mismatch if one takes an OTA upgrade and the phone will be bricked, though I can find nothing solid on this. Being that I plan on keeping a custom recovery I don't have to worry about accidentally taking an OTA and for some reason prefer to have the ability to downgrade, when 4.4.2 comes out I'm going to try to flash everything but the bootloader and I believe the partition table, (I need to read more and understand more before I speak with authority) to see if I can get away with it.
Also, on a side note, I found that freezing pre installed apps/bloat destroyed the wonderful battery life I was getting so I would suggest you keep your phone stock for a few days to get a feel for how the phone behaves before you begin freezing bloat.
Enjoy your new toy!
Click to expand...
Click to collapse
Thanks for that information. The last paragrapht seems counter-intuitive. I froze apps on the incredible so that it would reduce battery drain, why would freezing apps increase battery drain?
dmm108 said:
Thanks for that information. The last paragrapht seems counter-intuitive. I froze apps on the incredible so that it would reduce battery drain, why would freezing apps increase battery drain?
Click to expand...
Click to collapse
No idea, but freezing moto apps killed the battery. I haven't figured out what the culprit is yet as I'll be travelling this week and I don't want to jack up the phone while I'm on the road. I suspect another system app was spending effort looking for a missing app. Had I not ran my phone stock for a week I may have assumed that was just the phone as the high battery use was about the same as what I typically got on my S3. However, once I started freezing apps battery life went way down. Battery is good again after defrosting all Moto stuff that I assumed to be garbage. Once I get off the road I'll start freezing apps one at a time to see if I can isolate the culprit.
My thought is if you run it stock for a week you'll have a pretty good feel as to how the phone performs so you'll know whether your tweaks are helping or hurting you.
edthesped said:
Verizon boot animation and tether hack...
http://forum.xda-developers.com/showthread.php?t=2645343
Click to expand...
Click to collapse
Now that I'm looking at a full size computer I see that you are not getting a VZW version, The link above is not good! Sorry
edthesped said:
Now that I'm looking at a full size computer I see that you are not getting a VZW version, The link above is not good! Sorry
Click to expand...
Click to collapse
Yes, I am getting the Verizon DE. (VZW, 1st post).
I was just Google searching hoping for some good news... And came across this posted yesterday...
http://www.youmobile.org/blogs/entry/Root-Moto-X-KitKat
... Any truth to that? And is it for any carrier, i.e att?
Sent from my XT1058 using Tapatalk
Links to a thread on here.
Yea I saw that, but they are not the same...
Sent from my XT1058 using Tapatalk
They want you to dl this http://www.cydiaimpactor.com/
Anyone know what it is?
Maybe it works for root....but write protection will be enabled. So all root changes will be lost on reboot or power down.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
kj2112 said:
Maybe it works for root....but write protection will be enabled. So all root changes will be lost on reboot or power down.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
Click to expand...
Click to collapse
So here's my "dumb" question? Would apps like Greenify and Ti backup still possibly work since they just need root permissions, where as Xposed and other apps that need a reboot would be basically worthless?
jbaumert said:
So here's my "dumb" question? Would apps like Greenify and Ti backup still possibly work since they just need root permissions, where as Xposed and other apps that need a reboot would be basically worthless?
Click to expand...
Click to collapse
There's other threads where this stuff gets talked about, but im pretty sure for things like that it would probably work. But any actual changes to anything would get reversed.
I've always been unlocked....so I don't have firsthand experience though.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
I'm not too sure about that root method.
Step 11 tells you to downgrade the Bootloader (MOTOBOOT.IMG) and GPT.BIN which is part of the security stuff. Correct me if I'm wrong, but aren't those the main components involved with bricking when trying to downgrade from 4.4.2 to 4.4 and lower?
But again, with a locked bootloader, as @kj2112 said, Write Protection will still be enabled.
KidJoe said:
I'm not too sure about that root method.
Step 11 tells you to downgrade the Bootloader (MOTOBOOT.IMG) and GPT.BIN which is part of the security stuff. Correct me if I'm wrong, but aren't those the main components involved with bricking when trying to downgrade from 4.4.2 to 4.4 and lower?
But again, with a locked bootloader, as @kj2112 said, Write Protection will still be enabled.
Click to expand...
Click to collapse
I've been a bit confused by allusions to rooting without write protection. Everyone says similar stuff to what you guys have said--well, without write protection disabled you'll lose root on reboot. I'd be okay with that, just avoid rebooting my phone and using stuff that requires a reboot to take effect. The only thing I really want root for is to see my partial wakelocks to be able to properly troubleshoot battery issues. I really like the stock Moto X ux. If I could, I'd probably use some Xposed modules too, but all I really really want is to get better insight into my wakelock situation. Elsewhere, though, I read that root is totally impossible on 4.4.2, unless you have an unlocked bootloader (which I obviously don't). So, is it possible to get root, even if it doesn't survive a soft reset?
Jumnhy said:
I've been a bit confused by allusions to rooting without write protection. Everyone says similar stuff to what you guys have said--well, without write protection disabled you'll lose root on reboot. I'd be okay with that, just avoid rebooting my phone and using stuff that requires a reboot to take effect. The only thing I really want root for is to see my partial wakelocks to be able to properly troubleshoot battery issues. I really like the stock Moto X ux. If I could, I'd probably use some Xposed modules too, but all I really really want is to get better insight into my wakelock situation. Elsewhere, though, I read that root is totally impossible on 4.4.2, unless you have an unlocked bootloader (which I obviously don't). So, is it possible to get root, even if it doesn't survive a soft reset?
Click to expand...
Click to collapse
Please see my response to you in the 4.2.2 to 4.4.2 thread.
kj2112 said:
Please see my response to you in the 4.2.2 to 4.4.2 thread.
Click to expand...
Click to collapse
Thanks, didn't realize until afterward it was the same voice in both threads.
Jumnhy said:
I've been a bit confused by allusions to rooting without write protection. Everyone says similar stuff to what you guys have said--well, without write protection disabled you'll lose root on reboot. I'd be okay with that, just avoid rebooting my phone and using stuff that requires a reboot to take effect. The only thing I really want root for is to see my partial wakelocks to be able to properly troubleshoot battery issues. I really like the stock Moto X ux. If I could, I'd probably use some Xposed modules too, but all I really really want is to get better insight into my wakelock situation. Elsewhere, though, I read that root is totally impossible on 4.4.2, unless you have an unlocked bootloader (which I obviously don't). So, is it possible to get root, even if it doesn't survive a soft reset?
Click to expand...
Click to collapse
take a read of -> http://mark.cdmaforums.com/MotoX-LockedRoot.html
Root itself is not lost on reboot, only changes done to the /system folder and other protected places.
But yes, if you already have 4.4.2 on your phone, and can't unlock your bootloader, you won't be able to root.
Jumnhy said:
Thanks, didn't realize until afterward it was the same voice in both threads.
Click to expand...
Click to collapse
Where you found another same threads ?
DANIEL AMBRUSO said:
Where you found another same threads ?
Click to expand...
Click to collapse
It was just kj2112 explaining a similar issue to me. Check it out, but essentially my understanding is that there's no root for 4.4.2 if the phone never had root previously (ie, if you naively took the OTA like me without thnking about implications for root.
---------- Post added at 10:01 PM ---------- Previous post was at 09:56 PM ----------
KidJoe said:
take a read of -> http://mark.cdmaforums.com/MotoX-LockedRoot.html
Root itself is not lost on reboot, only changes done to the /system folder and other protected places.
But yes, if you already have 4.4.2 on your phone, and can't unlock your bootloader, you won't be able to root.
Click to expand...
Click to collapse
Solid, thanks for the concise summary. I'd read jcase's posts a while back about a potential exploit--something about using it in a teaching session at BlackHat? He even says though, that the exploit he has will probably never be useful for the average user insofar as it would be too hard to implement and n00bz like myself would end up bricking our phones. So I'm not holding my breath on that one. Ugh. Sad I missed the window for the Chinese connection. Should have jumped on it.
The Tallest said:
Links to a thread on here.
Click to expand...
Click to collapse
Works with 4.4 and post-camera 4.2.2, but if you take the OTA to 4.-4-.2 it upgrades your bootloader and you lose the ability to turn write protection off ; root is pretty much useless at that point.
I have the Republic Wireless XT1049 and did the upgrade shown here and have 4.4.2 with write protect off.
Do not attempt this if you are already running 4.4.2!!!!!!!!!!!!!!! Your bootloader is already changed and you run a big risk of bricking if you try to downgrade to the 4.2.2 bootloader!!!
http://forum.xda-developers.com/mot...ireless-moto-x-kitkat-4-t2738233/post52348028
As usual, read the instructions carefully.
Then read through the posts! Different rooters had different issues!
AFAIK no one bricked though.
glarepate said:
Works with 4.4 and post-camera 4.2.2, but if you take the OTA to 4.-4-.2 it upgrades your bootloader and you lose the ability to turn write protection off ; root is pretty much useless at that point.
I have the Republic Wireless XT1049 and did the upgrade shown here and have 4.4.2 with write protect off.
Do not attempt this if you are already running 4.4.2!!!!!!!!!!!!!!! Your bootloader is already changed and you run a big risk of bricking if you try to downgrade to the 4.2.2 bootloader!!!
http://forum.xda-developers.com/mot...ireless-moto-x-kitkat-4-t2738233/post52348028
As usual, read the instructions carefully.
Then read through the posts! Different rooters had different issues!
AFAIK no one bricked though.
Click to expand...
Click to collapse
The steps in the thread you link to are how to use use 4.4.2 via Safestrap, which does add a layer of complexity. It is the only option to take 4.4.2 IF you have a locked bootloader and are rooted and write protection disabled. And many do have good luck with it, so it is an option IF your phone is still on 4.4.
If I understand correctly, each safestrap rom is unique for the carrier.. in other words, you can't use the Republic Wireless SS rom if you are on Verizon. You can't use the Verizon SS rom if you are on ATT, etc. (for example, they were waiting on the ATT 4.4.2 SBF to create a SS Rom for the ATT X).
KidJoe said:
The steps in the thread you link to are how to use use 4.4.2 via Safestrap, which does add a layer of complexity. It is the only option to take 4.4.2 IF you have a locked bootloader and are rooted and write protection disabled. And many do have good luck with it, so it is an option IF your phone is still on 4.4.
If I understand correctly, each safestrap rom is unique for the carrier.. in other words, you can't use the Republic Wireless SS rom if you are on Verizon. You can't use the Verizon SS rom if you are on ATT, etc. (for example, they were waiting on the ATT 4.4.2 SBF to create a SS Rom for the ATT X).
Click to expand...
Click to collapse
Yes, if you have already gone to 4.4.2 you are out of luck.
I'm using the T-Mobile SafeStrap Recovery with my RW Moto X. This was done by a Franken-ROM process that uses the 4.4.2 ROM without using the 4.4.2 bootloader and using the SS recovery to flash a zip file with some components of the 4.4.2 ROM and then flashing SuperSU. Whether or not it should be working, it is. Nothing I can, or want to, do about that.
But I am sure you are right that this resultant ROM would not work on phones from other carriers. Versions for other carriers are being developed though. It may simply be a matter of time and interest by motivated individuals until this is available for just about everyone.
Good evening, I've just bought a Motorola Moto X XT1058 here in my country (Colombia) and I would like to know what steps can I take to being able to root and install a tweaked ROM based on the some official ROM (I dont like CM or AOSP, I enjoy a ROM based in a Stock ROM). There are too many ROMs and too many ROOT methods and I do not know which one use for XT1058. Thanks for the help.
1- Unlock the bootloader
2- Flash TWRP via fastboot
3- Flash SuperSU via TWRP
Thats all!
Enviado desde mi SAMSUNG-SGH-I717 mediante Tapatalk
Everything you need to know is here,
The Complete Moto X Guide
And as for ROMs, there aren't many, so read the opening posts in the dev section and see what's for you and stock based.
You can't unlocked the XT1058 bootloader, so you can't root the device. The older Android version was rootable, but not anymore. There is a Chinese guy that sell bootloader unlock codes for 2014 version of the phone, you can read more about it here: http://forum.xda-developers.com/moto-x/general/china-middleman-t2751177
Some news about unlock XT1058?
Hi folks,
I'll try to resurect this thread
I just get a refurbished MotoX, that unfortunatelly was a XT1058 att...
I would like to know if there has been new devlopments about unlocking its bootloader, knowing that I am under Lollipop 5.1 now.
My aim is to root the phone, especially to use apps that automatically cut the data, wifi or any connexions such as lean data. By default here is question 2: is there a way to use such kind of app without rooting?
Thanks a lot,
Smelc
smelc said:
Hi folks,
I'll try to resurect this thread
I just get a refurbished MotoX, that unfortunatelly was a XT1058 att...
I would like to know if there has been new devlopments about unlocking its bootloader, knowing that I am under Lollipop 5.1 now.
My aim is to root the phone, especially to use apps that automatically cut the data, wifi or any connexions such as lean data. By default here is question 2: is there a way to use such kind of app without rooting?
Thanks a lot,
Smelc
Click to expand...
Click to collapse
Juice defender likely does what you want...no root required. But be warned....it usually wastes more battery than it saves. There's no need to disable those things. If battery life is bad....there's likely a reason. Like app wakelocks. Check out Wakelock detector's pc version, no root required to see app wakelocks. Phone battery stat apps need root to show app wakelocks. You need to troubleshoot. Battery saving apps are terrible. Unless MAYBE if your're an extremely light user that barely touches their phone.
Also, as far as I know....unless Sunshine works on 5.1 now, there is no way to unlock your bootloader, or root at this time. Sorry.
Since I first started down this Android path I've always brought my phones direct from big red which, for all the problems it created it did make life simple when it came to identify which ROM to download etc.
This week I broke tradition and dropped some money on Google's lap and picked up a Nexus 6 direct from them - no more locked down to VZW for me if I so choose.
Previously I had a Incredible, then a GS III then finally a M8 - all three rooted and unlocked\S-OFF'd so this isn't my first rodeo.
That said I'm also wanting to tread VERY VERY lightly here because time and time again I read the the biggest reason folk get bricks is because they assumed and didn't ask questions before they flashed.
So, all this aside, here I am with my now Unlocked 5.0 Non branded Nexus 6 with LNX07M with TWRP 2.8 latest as a custom recovery and, as of right now, no root (to help ease any upgrade).
I've found various Stock ROMS out there there would indicate I'd need to be however on 5.0.1 before I could sideload a 5.1.1. Is this true? If so, do I need to blow away TWRP before I do this because when I tried previously to take the update it dropped me into TWRP.
Is there any way I can avoid all this, wipe and flash a Stock 5.1.1 direct? Wiping the phone isn't an issue as there's nowt on it right now. And should I root now, while still on 5.0 or wait until 5.1.1 (because it'll require a factory reset). Would root even survive a 5.1.1 upgrade?
I'm nervous here because I keep seeing lines such as 'T-MOBILE only' and different code letters after the build name seemingly signifying the different vendors. Given that I got mine direct from Google though I'm unsure how I should proceed because I really don't want to be left with an unhappy 6 so soon after delivery.
Thanks in advance!
R
Rachel Ambler said:
Since I first started down this Android path I've always brought my phones direct from big red which, for all the problems it created it did make life simple when it came to identify which ROM to download etc.
This week I broke tradition and dropped some money on Google's lap and picked up a Nexus 6 direct from them - no more locked down to VZW for me if I so choose.
Previously I had a Incredible, then a GS III then finally a M8 - all three rooted and unlocked\S-OFF'd so this isn't my first rodeo.
That said I'm also wanting to tread VERY VERY lightly here because time and time again I read the the biggest reason folk get bricks is because they assumed and didn't ask questions before they flashed.
So, all this aside, here I am with my now Unlocked 5.0 Non branded Nexus 6 with LNX07M with TWRP 2.8 latest as a custom recovery and, as of right now, no root (to help ease any upgrade).
I've found various Stock ROMS out there there would indicate I'd need to be however on 5.0.1 before I could sideload a 5.1.1. Is this true? If so, do I need to blow away TWRP before I do this because when I tried previously to take the update it dropped me into TWRP.
Is there any way I can avoid all this, wipe and flash a Stock 5.1.1 direct? Wiping the phone isn't an issue as there's nowt on it right now. And should I root now, while still on 5.0 or wait until 5.1.1 (because it'll require a factory reset). Would root even survive a 5.1.1 upgrade?
I'm nervous here because I keep seeing lines such as 'T-MOBILE only' and different code letters after the build name seemingly signifying the different vendors. Given that I got mine direct from Google though I'm unsure how I should proceed because I really don't want to be left with an unhappy 6 so soon after delivery.
Thanks in advance!
R
Click to expand...
Click to collapse
The main reason that some users bricked their phone is that they wiped the OS and had a locked bootloader which leaves no possibility ro recover the phone
What carrier do you use?
T-Mobile would be the LYZ28E rom and ATT/USC/International devices would be LMY47Z and Verizon is LMY47E.
Look here http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493 and here http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008.
Unless something is special about the N6 that I'm not aware of, the OS you update FROM only matters if you're sideloading an OTA file. Flashing factory images, you could be coming from a custom ROM(I just took my old N4 from CM12.1 to stock 4.4 on Sunday).
The current build for VZW is 5.1 LMY47E. I think they are updating to 5.1.1 now(LMY47Z, which seems to be universal now except for maybe T-Mo). I flashed mine from E to Z on Saturday because I bought mine unlocked but it had the VZW build, and I'm on an AT&T MVNO.
gee2012 said:
What carrier do you use?
T-Mobile would be the LYZ28E rom and ATT/USC/International devices would be LMY47Z and Verizon is LMY47E.
Look here http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493 and here http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008.
Click to expand...
Click to collapse
Still with VZW for now, but, as I said, I didn't purchase the phone from them, I brought it from Google direct so it's carrier agnostic (well, in the US at least!) hence my confusion. The last thing I want to do is flash a ROM that's carrier specific but I don't know which one to take with this being the case.
As for the order, my M8 needed to go in two stages to jump from my old Venom build due to changes with the radio (I think) - hence my question there.
If you root, you'll.never get an OTA anyway, sonit doesn't matter which rom you flash aa you can flash any other rom.over it
None of the carrier specific roms will restrict anything, or add branding, so go for whichever.
Rachel Ambler said:
Still with VZW for now, but, as I said, I didn't purchase the phone from them, I brought it from Google direct so it's carrier agnostic (well, in the US at least!) hence my confusion. The last thing I want to do is flash a ROM that's carrier specific but I don't know which one to take with this being the case.
As for the order, my M8 needed to go in two stages to jump from my old Venom build due to changes with the radio (I think) - hence my question there.
Click to expand...
Click to collapse
Just flash the LMY47E rom and when its available you get the OTA to update or sideload the OTA from here http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493 when its available.
danarama said:
None of the carrier specific roms will restrict anything, or add branding, so go for whichever.
Click to expand...
Click to collapse
Really? Is there a reason why they exist then? Usually my understanding was that they contained carrier specific items including radios and bloatware.
Rachel Ambler said:
Really? Is there a reason why they exist then? Usually my understanding was that they contained carrier specific items including radios and bloatware.
Click to expand...
Click to collapse
There's no bloatware on these roms.
Verizon rom includes binaries that make VoLTE work properly on their network where as T-mobile adds a kernel fix to allow their wifi calling to work. And that's it...
gee2012 said:
Just flash the LMY47E rom and when its available you get the OTA to update or sideload the OTA from here http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493 when its available.
Click to expand...
Click to collapse
So what would be the benefit of flashing a Verizon ROM is, for example I should suddenly decide to go to T-Mobile next week given that I didn't purchase the phone from them?
Sorry if these are noob questions but this whole carrier agnostic\yet not agnostic thing has me really wanting to make sure my phone stays as agnostic as it was when it left the factory, bar a VZW Sim nestled inside and a VZW APN entry.
danarama said:
There's no bloatware on these roms.
Verizon rom includes binaries that make VoLTE work properly on their network where as T-mobile addsna kernel fix to allow their wifi calling to work. And that's it...
Click to expand...
Click to collapse
Interesting. So this would leave me to believe then that, should I decide one day to jump carriers, I'd be better off flashing a ROM for that carrier at the appropriate time?
This being the case, why would the phone come with no carrier specific software on board from Google? Wouldn't this mean I might get a degraded service?
Rachel Ambler said:
So what would be the benefit of flashing a Verizon ROM is, for example I should suddenly decide to go to T-Mobile next week given that I didn't purchase the phone from them?
Sorry if these are noob questions but this whole carrier agnostic\yet not agnostic thing has me really wanting to make sure my phone stays as agnostic as it was when it left the factory, bar a VZW Sim nestled inside and a VZW APN entry.
Click to expand...
Click to collapse
If you want to use T-Mobile in the future you just flash the LYZ28E rom.
Rachel Ambler said:
So what would be the benefit of flashing a Verizon ROM is, for example I should suddenly decide to go to T-Mobile next week given that I didn't purchase the phone from them?
Sorry if these are noob questions but this whole carrier agnostic\yet not agnostic thing has me really wanting to make sure my phone stays as agnostic as it was when it left the factory, bar a VZW Sim nestled inside and a VZW APN entry.
Click to expand...
Click to collapse
Well all Nexus 6 used to get the same updates but tmob and red, wanted approval on theirs - and now we know why.
Since google are still sending these updates and they update onto generic builds, they can only use your sim card as the identifier.
If you leave root out of it, the only way you can avoid the vzw update is to manually update to something else (something vzw updates won't work on). Each OTA looks for a specific build to flash on and won't flash on anything else.
If you do accept the vzw update, you'll never get away from them unless you manually flash a full factory rom.
Bringing root back into it, OTA will never flash anyway, so you'll have to either manually flash factory or flash rom.zips in TWRP
gee2012 said:
If you want to use T-Mobile in the future you just flash the LYZ28E rom.
Click to expand...
Click to collapse
This is already explaining a lot! So, given that, as I said, I'm not bog standard non-carrier specific 5.0 (and I've yet to even migrate my SIM over) the suggested action would be to download LMY47E 5.1 (as 5.1.1 is not yet out for VZW as they ALWAYS seem to be last to the party) and flash it via TWRP? And I can do that over my LNX07M build?
danarama said:
"Well all Nexus 6 used to get the same updates but tmob and red, ..."
Click to expand...
Click to collapse
Great info, very useful.
Rachel Ambler said:
Interesting. So this would leave me to believe then that, should I decide one day to jump carriers, I'd be better off flashing a ROM for that carrier at the appropriate time?
This being the case, why would the phone come with no carrier specific software on board from Google? Wouldn't this mean I might get a degraded service?
Click to expand...
Click to collapse
There were no carrier specific ROMs when Nexus 6 came out. Using any rom on any Nexus and they will all act the same, except you wont get improved volte or wifi calling on those carriers. Their changes will not prove detrimental on other carriers
danarama said:
Well all Nexus 6 used to get the same updates but tmob and red, wanted approval on theirs - and now we know why.
Since google are still sending these updates and they update onto generic builds, they can only use your sim card as the identifier.
If you leave root out of it, the only way you can avoid the vzw update is to manually update to something else (something vzw updates won't work on). Each OTA looks for a specific build to flash on and won't flash on anything else.
If you do accept the vzw update, you'll never get away from them unless you manually flash a full factory rom.
Bringing root back into it, OTA will never flash anyway, so you'll have to either manually flash factory or flash rom.zips in TWRP
Click to expand...
Click to collapse
Now the murky seas are de-murkyfing!
So go for the VZW build for now with the knowledge and understanding that if I ever decide to bid them a less than fond adieu, I'd be best at that point flash a factory image OR flash another carrier specific ROM once I've chosen the new carrier?
And should I root now, or post the 5.1 flash? I'm guessing post because I'd assuming flashing 5.1 would blow my root away.
I assume I can flash post VZW 5.1 because the boatloader is still all mine and the flash doesn't effect that. Right?
Rachel Ambler said:
This is already explaining a lot! So, given that, as I said, I'm not bog standard non-carrier specific 5.0 (and I've yet to even migrate my SIM over) the suggested action would be to download LMY47E 5.1 (as 5.1.1 is not yet out for VZW as they ALWAYS seem to be last to the party) and flash it via TWRP? And I can do that over my LNX07M build?
Click to expand...
Click to collapse
Depends how you do it.
Google factory images are flashed from a computer using fastboot.
You may be able to find a rom.zip of that version on xda that can be flashed via TWRP.
As long as you aren't flashing an incremental OTA, you can flash over anything. OTA actually patch files not replace them, so they can only be flashed on the rom they are intended for.
Rachel Ambler said:
Now the murky seas are de-murkyfing!
So go for the VZW build for now with the knowledge and understanding that if I ever decide to bid them a less than fond adieu, I'd be best at that point flash a factory image OR flash another carrier specific ROM once I've chosen the new carrier?
And should I root now, or post the 5.1 flash? I'm guessing post because I'd assuming flashing 5.1 would blow my root away.
I assume I can flash post VZW 5.1 because the boatloader is still all mine and the flash doesn't effect that. Right?
Click to expand...
Click to collapse
Why not go with a custom rom like chroma? Get 5.1.1 now and personally it works really well.
danarama said:
Depends how you do it.
Google factory images are flashed from a computer using fastboot.
You may be able to find a rom.zip of that version on sea that can be flashed via TWRP.
As long as you aren't flashing an incremental OTA, you can flash over anything. OTA actually patch files not replace them, so they can only be flashed on the rom they are intended for.
Click to expand...
Click to collapse
I'm sorry if that sudden flash of the light coming on in my head just blinded you, but that's what happens when things start to make sense!
OK, so, this all being the case, and that the OTA's are incremental, then in order to go 5.1 with the build from http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493 then I WOULD need 5.0.1? Would that work though if I'm on a generic build since, if it's expecting to patch existing VZW files, wouldn't it fail because they're not there? Failing that I'd need to find a flashable 5.1 for VZW (if one even exists)?
endlessryan said:
Why not go with a custom rom like chroma? Get 5.1.1 now and personally it works really well.
Click to expand...
Click to collapse
But it wouldn't have the VoLTE improvements, etc, right? Besides, right now I'd like to stay as stock as possible as it's not just my phone I'm working on, both myself and my wife got one at the same time and I know she will most definitely NOT want anything other than stock.