I know this is not the Q&A thread. Don't shoot me. But i figured this was a dev question. Does anybody think or have tried flashing the stock droid ultra ROM to the moto x since they are VERY SIMILAR phones? Is it possible? Can it be done? Has anybody tried? If not and I was to try it do you think I can flash stock moto x IMG files back to normal? Or will i fubar my bootloader. Running Moto x Dev edit Verizon. These are questions that have been running through my head. Just thought I might ask. And is anybody willing to help me look into it? Thank you for taking the time to read and reply.
ryanzurlo88 said:
I know this is not the Q&A thread. Don't shoot me. But i figured this was a dev question. Does anybody think or have tried flashing the stock droid ultra ROM to the moto x since they are VERY SIMILAR phones? Is it possible? Can it be done? Has anybody tried? If not and I was to try it do you think I can flash stock moto x IMG files back to normal? Or will i fubar my bootloader. Running Moto x Dev edit Verizon. These are questions that have been running through my head. Just thought I might ask. And is anybody willing to help me look into it? Thank you for taking the time to read and reply.
Click to expand...
Click to collapse
Very similar is never close enough. Any ROM for a different phone will not work for a different device. Some exploit methods work on multiple devices but never Roms and kernals.
Imacellist said:
Very similar is never close enough. Any ROM for a different phone will not work for a different device. Some exploit methods work on multiple devices but never Roms and kernals.
Click to expand...
Click to collapse
I only asked cause if cm11 pac-rom etc could do it maybe we could. Thanks for answering though. It was worth a shot. I just miss my droid ultra?
They are the same phone in almost every way and yes the builds are compatible, or at least the 4.2.2 and 4.4 builds were last year. When the leaked T-Mobile 4.4 build came out, I was running it perfect on my vzw moto x DE and at least one other person was running it on their droid ultra/maxx with no issues.
So your question for the devs was just answered by non devs. If you KNEW you were posting in the wrong thread, but wanted to make sure you got noticed please follow the rules next time. It's not like you didn't know this does not belong here.
Only try this if you have an unlocked boot loader. If you are locked then you are out of luck. Still recommend finding a build for your phone.
Sent from my XT1060 using XDA Premium 4 mobile app
Travisdroidx2 said:
So your question for the devs was just answered by non devs. If you KNEW you were posting in the wrong thread, but wanted to make sure you got noticed please follow the rules next time. It's not like you didn't know this does not belong here.
Click to expand...
Click to collapse
i posted here thinking maybe devs have already tried it and/or have a workaround for it. i'm not going to start a fight with you over the internet cause thats just petty.
Moved here as this does not belong in the Development Section, OP please read the Forum Rules on posting.
Hello there!
I just created an account and would like to apologize in advance for any rookie mistakes; using the wrong terms/words and expressions, posting in the wrong place etc... I have seen a lot of very helpful threads but I have yet to find an answer to my issues with my phone.
I have an HTC One (I believe it is the M7) and the service provider is Verizon. The phone was rooted when I bought it and has
"NuSenseSIX-KitKat-m7vzw_RC4.2_032914"
I am having problems with using a bluetooth earpiece together with the phone. (You will get a ticket if driving and talking in the state of WA) and it drives me nuts! I have tried 3 different brands/kind of bluetooth devices as well as made sure that they work on other phones.
I am able to connect/pair the devices - no problem. I can listen to audio, both music/sounds on the phone as well as during calls or using Voxer Walkie-Talkie. There was never an issue on my end as far as hearing sound BUT, not once have I been able to be heard on "the other end". All they hear during a call is a "high-pitched crackling, static, robotic, very annoying" noise which makes the device useless for its purpose.
I have tried restarting, repairing and whatever other "simple" troubleshooting steps I could think of.
I did back the phone up and then did 2 or 3 factory resets, I have "un-rooted and re-rooted" the phone using SuperSU (which was already installed). I have tried to do the wipe/reset/recovery procedure a few different ways, one being a complete removal of Dalvik, cache, and whatever else shows up (sorta scary since I don't have very much experience)
Anyways, I am stuck and wonder if there is anyone out there who can possibly help me..? Is there a "fix" that I can install/apply or is there a better ROM I can use? I'm afraid to try "ROM or Kernel-swapping" on my own before I get some feedback on the procedure...
Sorry for the long post but I really need help....
Thanks - Bob the Swede
Bob the Swede said:
Hello there!
I just created an account and would like to apologize in advance for any rookie mistakes; using the wrong terms/words and expressions, posting in the wrong place etc... I have seen a lot of very helpful threads but I have yet to find an answer to my issues with my phone.
I have an HTC One (I believe it is the M7) and the service provider is Verizon. The phone was rooted when I bought it and has
"NuSenseSIX-KitKat-m7vzw_RC4.2_032914"
I am having problems with using a bluetooth earpiece together with the phone. (You will get a ticket if driving and talking in the state of WA) and it drives me nuts! I have tried 3 different brands/kind of bluetooth devices as well as made sure that they work on other phones.
I am able to connect/pair the devices - no problem. I can listen to audio, both music/sounds on the phone as well as during calls or using Voxer Walkie-Talkie. There was never an issue on my end as far as hearing sound BUT, not once have I been able to be heard on "the other end". All they hear during a call is a "high-pitched crackling, static, robotic, very annoying" noise which makes the device useless for its purpose.
I have tried restarting, repairing and whatever other "simple" troubleshooting steps I could think of.
I did back the phone up and then did 2 or 3 factory resets, I have "un-rooted and re-rooted" the phone using SuperSU (which was already installed). I have tried to do the wipe/reset/recovery procedure a few different ways, one being a complete removal of Dalvik, cache, and whatever else shows up (sorta scary since I don't have very much experience)
Anyways, I am stuck and wonder if there is anyone out there who can possibly help me..? Is there a "fix" that I can install/apply or is there a better ROM I can use? I'm afraid to try "ROM or Kernel-swapping" on my own before I get some feedback on the procedure...
Sorry for the long post but I really need help....
Thanks - Bob the Swede
Click to expand...
Click to collapse
Hello Bob, welcome to xda!
Bluetooth call audio was fixed in version 6.01 of NewSenseSIX rom. Your actual version is RC 4.2 which mean "Release Candidate" version 4.2. RC versions are not fully stable, but stable enough for average users to test them. Latest stable version of NewSenseSIX for verizon htc one is 8.0. Updating your rom to latest version should fix your issue.
You might also want to update your firmware to the latest version for more stability. (will be mentioned in the rom thread if required)
You'll have to use twrp recovery version 2.7.0.8 or newer like said in the rom thread
http://forum.xda-developers.com/showthread.php?t=2693502
keep in mind that Verizon variant of the M7 have different partition layout than the internation version(M7_UL), so only use stuff (rom/recovery/tools) that is compatible for Verizon M7 (M7VZW)
---------- Post added at 12:52 AM ---------- Previous post was at 12:50 AM ----------
if you need help how to flash the rom and recovery just ask here and we will help you.
Thank you!
alray said:
Hello Bob, welcome to xda!
Bluetooth call audio was fixed in version 6.01 of NewSenseSIX rom. Your actual version is RC 4.2 which mean "Release Candidate" version 4.2. RC versions are not fully stable, but stable enough for average users to test them. Latest stable version of NewSenseSIX for verizon htc one is 8.0. Updating your rom to latest version should fix your issue.
You might also want to update your firmware to the latest version for more stability. (will be mentioned in the rom thread if required)
You'll have to use twrp recovery version 2.7.0.8 or newer like said in the rom thread
http://forum.xda-developers.com/showthread.php?t=2693502
keep in mind that Verizon variant of the M7 have different partition layout than the internation version(M7_UL), so only use stuff (rom/recovery/tools) that is compatible for Verizon M7 (M7VZW)
---------- Post added at 12:52 AM ---------- Previous post was at 12:50 AM ----------
if you need help how to flash the rom and recovery just ask here and we will help you.
Click to expand...
Click to collapse
Thank you so much! Now I get what is what I might need help finding the right place or thread showing me how to flash the ROM etc. I will look around too of course now that I know what the problem is.
I need help...
I am not confident enough to try this on my own and I don;t want to brick my phone.
Can anyone show me the necessary steps needed to do update from RC 4.2 to 8.0..? I have SuperSU v2.14, and TWRP 2.7.0.1.
Bob the Swede said:
I am not confident enough to try this on my own and I don;t want to brick my phone.
Can anyone show me the necessary steps needed to do update from RC 4.2 to 8.0..? I have SuperSU v2.14, and TWRP 2.7.0.1.
Click to expand...
Click to collapse
The link posted by @alray above comes with the download and instructions for flashing TWRP. And the second link takes you directly to the rom.
The only way it could be easier is if he comes to your house and flashes it all for you
Hahaha, I'm sorry, that's embarrassing.
Bob the Swede said:
Hahaha, I'm sorry, that's embarrassing.
Click to expand...
Click to collapse
just take your time and read a lot ..it's all pretty simple once you get a grasp on whats going on
Bob the Swede said:
I am not confident enough to try this on my own and I don;t want to brick my phone.
Can anyone show me the necessary steps needed to do update from RC 4.2 to 8.0..? I have SuperSU v2.14, and TWRP 2.7.0.1.
Click to expand...
Click to collapse
you will first need to upgrade your firmware like said in the rom thread. Click on the link in that thread "Latest Radios and Firmware are REQUIRED and can be found here"
follow instruction to flash the latest firmware in that thread
then flash twrp 2.8.0.1 (also linked in the rom thread just above "Latest Radios and Firmware..." link.
Code:
fastboot flash recovery name_of_file.img
fastboot erase cache
fastboot reboot-bootloader
then push the rom to your phone (either using adb push/adb sideload/usb otg) and install it using twrp.
like cisa said above, if you follow the instructions in that thread andtake your time, everything will be good.
THANK YOU!!!
I did it! Thanks to you guys! alray and clsA
I am now on RC8.0 and it is AWESOME! BT works great along with all the extra stuff included.
Bob the Swede said:
I did it! Thanks to you guys! alray and clsA
I am now on RC8.0 and it is AWESOME! BT works great along with all the extra stuff included.
Click to expand...
Click to collapse
:highfive:
I know, I know - this is a noob question, guides have already been posted, etc - but information is scattered all over the place, and the internet is littered with "what worked for me" type guides, and I'm just looking for a quick response.
Here's the 2 guides I have found so far:
EDIT: It looks like i can't post outside links, but have found 2 guides. Both are on reddit, and one ends in:
/nexus6/comments/2ywu1m/guide_to_flashing_51_factory_image_without_wiping/
The other:
/nexus6/comments/3028i9/guide_how_to_update_to_51_and_keep_root/
Both of these are very different methods, it seems. My phone is unlocked, rooted, encrypted, and has 5.0.1. It would seem like the easiest thing to do would be to unroot, apply the OTA update, the re-root using CF-Auto-Root - but a forum post said that didn't work, it needs to be re-flashed.
I'm just looking for which of these methods would be best for me at this point. I want to keep root, and not lose my phone's configuration in the simplest way, preferably just using the OTA update, without re-flashing.
Thank you, and I apologize for asking a question that has already been answered. The problem is there are too many different answers, and I'm not sure which one to go with.
EDIT: I've also noticed, that if I have to re-flash, there are 3 different images for nexus 6 5.1: LMY47D, LMY47E, and LMY47I - this is the first time I've seen this when looking to flash a phone. How do I know which is the most up-to-date, and which one to go with?
XDA-Nexus-User said:
I know, I know - this is a noob question, guides have already been posted, etc - but information is scattered all over the place, and the internet is littered with "what worked for me" type guides, and I'm just looking for a quick response.
Here's the 2 guides I have found so far:
EDIT: It looks like i can't post outside links, but have found 2 guides. Both are on reddit, and one ends in:
/nexus6/comments/2ywu1m/guide_to_flashing_51_factory_image_without_wiping/
The other:
/nexus6/comments/3028i9/guide_how_to_update_to_51_and_keep_root/
Both of these are very different methods, it seems. My phone is unlocked, rooted, encrypted, and has 5.0.1. It would seem like the easiest thing to do would be to unroot, apply the OTA update, the re-root using CF-Auto-Root - but a forum post said that didn't work, it needs to be re-flashed.
I'm just looking for which of these methods would be best for me at this point. I want to keep root, and not lose my phone's configuration in the simplest way, preferably just using the OTA update, without re-flashing.
Thank you, and I apologize for asking a question that has already been answered. The problem is there are too many different answers, and I'm not sure which one to go with.
Click to expand...
Click to collapse
Just download the factory image of your choice and use fastboot to flash everything individually except userdata. You won't be wiped and all you'll have to do is re-root. Or just pick a ROM from development forums.
---------- Post added at 05:07 PM ---------- Previous post was at 05:01 PM ----------
Follow the steps in Method 2 here:
http://forum.xda-developers.com/showthread.php?t=2954008
As I said, flash everything except userdata. Also skip the factory reset at the end.
---------- Post added at 05:09 PM ---------- Previous post was at 05:07 PM ----------
LMY47I is the newest AFAIK.
---------- Post added at 05:15 PM ---------- Previous post was at 05:09 PM ----------
Also, questions go in the Q&A forum, not in general. I've asked the mods to move it there.
XDA-Nexus-User said:
EDIT: I've also noticed, that if I have to re-flash, there are 3 different images for nexus 6 5.1: LMY47D, LMY47E, and LMY47I - this is the first time I've seen this when looking to flash a phone. How do I know which is the most up-to-date, and which one to go with?
Click to expand...
Click to collapse
Verizon phones ship with E. AT&T is currently pushing D (and Sprint). T-Mobile is pushing M.
With that said, (unless you're on TMO), I've tried D, E, and I, and I could not really see any difference. E has the 98R radio, which some users have had better results with. All of the others have the 95R radio. You will have to try both and decide which works best for you.
cam30era said:
Verizon phones ship with E. AT&T is currently pushing D (and Sprint). T-Mobile is pushing M.
With that said, (unless you're on TMO), I've tried D, E, and I, and I could not really see any difference. E has the 98R radio, which some users have had better results with. All of the others have the 95R radio. You will have to try both and decide which works best for you.
Click to expand...
Click to collapse
Well I have T-Mobile, so I'd like to stick with what they are pushing, if for no other reason than to conform to thier OTA push and their unique radio frequencies.
However, the options are "E" "D" and "I" on the Google website. However, you mentioned M. Did you mean one of the others, or is there some unique image not available on the developers.google.com website? Which one off that site would be the default for T-Mobile?
XDA-Nexus-User said:
Well I have T-Mobile, so I'd like to stick with what they are pushing, if for no other reason than to conform to thier OTA push and their unique radio frequencies.
However, the options are "E" "D" and "I" on the Google website. However, you mentioned M. Did you mean one of the others, or is there some unique image not available on the developers.google.com website? Which one off that site would be the default for T-Mobile?
Click to expand...
Click to collapse
M was issued as an OTA for T-Mobile users. That being said, @simms22 will confirm that LMY47I works just fine on T-Mobile.
whatever carrier you are on, everything will work regardless of which letter update you chose.
XDA-Nexus-User said:
Well I have T-Mobile, so I'd like to stick with what they are pushing, if for no other reason than to conform to thier OTA push and their unique radio frequencies.
However, the options are "E" "D" and "I" on the Google website. However, you mentioned M. Did you mean one of the others, or is there some unique image not available on the developers.google.com website? Which one off that site would be the default for T-Mobile?
Click to expand...
Click to collapse
Available only via OTA, which means you have to go back to 100% stock first. Here >http://forum.xda-developers.com/nexus-6/general/t-mobile-rolling-lmy47m-5-1-t3059371
im on I, and am on tmobile, with the 95r radio, and everything works, including volte
@simms22: "everything works" is great, but this isn't what I'm looking for, I want to be picky. I'm going to quote @PunishedSnake from @cam30era's link:
PunishedSnake: "M was built 4 days after I so yes it would have all that I has and then tmobile specific stuff"
PunishedSnake: "It's in build.prop
---------- Post added at 09:31 AM ---------- Previous post was at 09:30 AM ----------
M is greater than I..... "
Honestly, I'd rather wait for google to put M up on their developer's site rather than touch anything at this point. Does anyone think this might happen?
XDA-Nexus-User said:
M is greater than I..... "
Honestly, I'd rather wait for google to put M up on their developer's site rather than touch anything at this point. Does anyone think this might happen?
Click to expand...
Click to collapse
Letters don't appear to represent sequential release. I is most recent, and represents r3.
If M was going to be released with a factory image, it would normally have been within 48 hours of the OTA. It's been 3 weeks. You can keep waiting, and waiting.....
XDA-Nexus-User said:
@simms22: "everything works" is great, but this isn't what I'm looking for, I want to be picky. I'm going to quote @PunishedSnake from @cam30era's link:
PunishedSnake: "M was built 4 days after I so yes it would have all that I has and then tmobile specific stuff"
PunishedSnake: "It's in build.prop
---------- Post added at 09:31 AM ---------- Previous post was at 09:30 AM ----------
M is greater than I..... "
Honestly, I'd rather wait for google to put M up on their developer's site rather than touch anything at this point. Does anyone think this might happen?
Click to expand...
Click to collapse
you can do whatever youd like, everyone has their own priorities. me, i did it the easiest way, i dirty flashed 5.1 over 5.0.2, kept all my data, all my setup, and everything else. took about 90 seconds
cam30era said:
Letters don't appear to represent sequential release. I is most recent, and represents r3.
If M was going to be released with a factory image, it would normally have been within 48 hours of the OTA. It's been 3 weeks. You can keep waiting, and waiting.....
Click to expand...
Click to collapse
Ok, wow. Never so much confusion is updating a Nexus device...
Some people say M is newer than I, some say otherwise? Either way, doubtful M will be released on google's site, and doublful it has anything I doesn't, so I'll just proceed with the original "Method 2" described in my original reply.
So all I have to do is follow the steps, except make sure not to type: fastboot flash userdata C:/image-shamu-XXXXXX/userdata.img?
To add fuel to the fire, 5.1.1 is expected soon as well. This will, perhaps, unify all builds into one. This is based on the SDK being updated to 5.1.1 a few days ago.
---------- Post added at 07:09 PM ---------- Previous post was at 07:05 PM ----------
XDA-Nexus-User said:
Ok, wow. Never so much confusion is updating a Nexus device...
Some people say M is newer than I, some say otherwise? Either way, doubtful M will be released on google's site, and doublful it has anything I doesn't, so I'll just proceed with the original "Method 2" described in my original reply.
So all I have to do is follow the steps, except make sure not to type: fastboot flash userdata C:/image-shamu-XXXXXX/userdata.img?
Click to expand...
Click to collapse
Yes, correct.
Thank you everyone! Followed @Evolution_Freak's "Method 2" link, re-rooted, and everything seems good. I'm not good at using forums and this was my first time making a thread or being this confused at the particulars of flashing a nexus, but your explanations and information have been very helpful.
XDA-Nexus-User said:
Thank you everyone! Followed @Evolution_Freak's "Method 2" link, re-rooted, and everything seems good. I'm not good at using forums and this was my first time making a thread or being this confused at the particulars of flashing a nexus, but your explanations and information have been very helpful.
Click to expand...
Click to collapse
Glad you got it sorted and glad to have helped in any way.
Please give an example of a build where for example
A R build was older than an I build.
M is 4 days newer than I although I don't know why google hasn't posted the M build. Hopefully the next update brings all N6 to the same build
simms22 said:
im on I, and am on tmobile, with the 95r radio, and everything works, including volte
Click to expand...
Click to collapse
Hate to break this to you, but the I image has a serious problem for certain people on T-Mobile. It completely breaks group messaging using the default messenger, forcing them to use a different messaging program.
I told a friend to use the I Image as I had been told repeatedly everything would work fine. He uses group messaging heavily for work, while I never use it. I caused him some serious problems.
Not trying to rag on you specifically @simms, but I am just warning people in general that not everything works perfectly on T-Mobile without the M build. I tested this myself.
XDA-Nexus-User said:
Hate to break this to you, but the I image has a serious problem for certain people on T-Mobile. It completely breaks group messaging using the default messenger, forcing them to use a different messaging program.
I told a friend to use the I Image as I had been told repeatedly everything would work fine. He uses group messaging heavily for work, while I never use it. I caused him some serious problems.
Not trying to rag on you specifically @simms, but I am just warning people in general that not everything works perfectly on T-Mobile without the M build. I tested this myself.
Click to expand...
Click to collapse
i use the Google messenger app, and arent having any issues with sms, and group sms. no issues here to report.
simms22 said:
i use the Google messenger app, and arent having any issues with sms, and group sms. no issues here to report.
Click to expand...
Click to collapse
Are you verifying that other people receive the SMS message? It does not give an error of any kind.
When I tested it, was in a room with 4 different people, and the message appeared to go through. However, only 1 person on the list I started the group message with would actually receive it.