Database Users

Remix OS 2.0 on Nexus 9 and 10 is Available to Download

We’re excited to announce that we’ve released Remix OS 2.0 ROMs for Nexus 9 and Nexus 10. The Nexus 9 and Nexus 10 ROMs are now available for download here:
Nexus 9 ROM
http://www.jide.com/remixos/devices/nexus9
Nexus 10 ROM
http://www.jide.com/remixos/devices/nexus10
Flash Tutorial
http://support.jide.com/hc/en-us/articles/218081838
We’ve also been conscious of all the interest that Nexus 9 and 10 users have expressed in being able to experience Remix OS 2.0 on your tablets. And, although we’re still a relatively small team, we definitely heard your comments and are excited to finally have Remix OS 2.0 ready for you.
You can submit your bug report here:
http://bit.ly/1qh2jQq
Cheers

does this work on the lte variant?

Based on Android 5.11? No thanks.

I am not sure if I want to downgrade my nexus 9 to 5.11.
But Android 6.x and N are not good enough for me at least.
I am thinking if any other customize rom can be used.
Also Ubuntu for tablet might be a choice.

Any hopes of being able to load this via TWRP recovery? Or being able to load this via ADB while still keeping TWRP recovery?

Is there a possibility now to use google account and google services or still no?

Woofly said:
Any hopes of being able to load this via TWRP recovery? Or being able to load this via ADB while still keeping TWRP recovery?
Click to expand...
Click to collapse
You can fastboot flash while keeping twrp
maelfilk said:
Is there a possibility now to use google account and google services or still no?
Click to expand...
Click to collapse
It now comes with play store. Overall it's world's better than 1.5.

dictionary said:
You can fastboot flash while keeping twrp
It now comes with play store. Overall it's world's better than 1.5.
Click to expand...
Click to collapse
Sweet. Does it have Google Play Services as well? Are we able to run apps like Gmail and Play Music?

Woofly said:
Sweet. Does it have Google Play Services as well? Are we able to run apps like Gmail and Play Music?
Click to expand...
Click to collapse
Yes sir. Haven't tried play music, but running gmail and hangouts fine. When you fastboot flash things, just don't flash recovery. Also, I had to flash the old 5.1.1 bootloader and vendor first.

Anyone here NOT getting a bootloop after installing? what am i doing wrong here....

th3fallen said:
Anyone here NOT getting a bootloop after installing? what am i doing wrong here....
Click to expand...
Click to collapse
Working fine for me here. Was getting constant reboots and bootlooping before I flashed back to 5.1.1 first though. Bootloader and vendor especially. Then wiped everything but internal in TWRP, then fastboot flashed Remix except for twrp. Booted into TWRP before booting into the system. Worked great after that.

So does it work for LTE variant? Also anyone running custom kernel with it? (afaik FIRE-ICE has special kernel)

Bootloopers
To all those getting bootloop:
* Download latest 5.11 image LMY48T (not 6.x) https://developers.google.com/android/nexus/images#volantis
* In theory you only need to flash bootloader-flounder-3.44.1.0123.img however to be on the safe side I ran the whole ./flash-all.sh
* Now reboot the bootloader (even if you are already there, since we just flashed a different one), then run the following:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cache cache.img
# flashing vendor.img will solve the problem of annoying messages on boot/unstable play services
fastboot flash vendor vendor.img
# there is no userdata.img , so we can wipe userdata like so:
fastboot -w
* Now reboot and it should work great. With my experience so far it seems very stable

dictionary said:
Working fine for me here. Was getting constant reboots and bootlooping before I flashed back to 5.1.1 first though. Bootloader and vendor especially. Then wiped everything but internal in TWRP, then fastboot flashed Remix except for twrp. Booted into TWRP before booting into the system. Worked great after that.
Click to expand...
Click to collapse
Working fine for me here. Was getting constant reboots and bootlooping before I flashed back to 5.1.1 first though. Bootloader and vendor especially. Then wiped everything but internal in TWRP, then fastboot flashed Remix except for twrp. Booted into TWRP before booting into the system. Worked great after that.
Click to expand...
Click to collapse
That was my issue. Thanks

Bootloop on second boot
So after the tablet seemingly working perfectly and no boot loops on install, it is now only bootlooping after rebooting (even after wiping cache) And this is after installing 5.11 factory image before remix os.
Will try factory reset etc.

i am really interrested in this OS
but before i am doing anything i want to ask some questions
1) how far is google play and google play store integrated? can i open every app?
2) can i type without a manual keyboard?
3) is LTE supported in this version?

I will try this as soon as I get home. Can't wait to test it.

Fallon9111 said:
To all those getting bootloop:
* Download latest 5.11 image LMY48T (not 6.x) https://developers.google.com/android/nexus/images#volantis
* In theory you only need to flash bootloader-flounder-3.44.1.0123.img however to be on the safe side I ran the whole ./flash-all.sh
* Now reboot the bootloader (even if you are already there, since we just flashed a different one), then run the following:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cache cache.img
# flashing vendor.img will solve the problem of annoying messages on boot/unstable play services
fastboot flash vendor vendor.img
# there is no userdata.img , so we can wipe userdata like so:
fastboot -w
* Now reboot and it should work great. With my experience so far it seems very stable
Click to expand...
Click to collapse
What I find even easier, is to go into twrp. Do all the usual wipes (data, cache, dalvik, system), then reboot into bootloader. It'll say no OS installed in twrp, but that's fine. Then I fastboot flashed the 5.1.1 image manually, skipping recovery.img . Once done, I reboot recovery. It'll boot into twrp. (Doing this ensures that twrp won't be overwritten upon first boot). Then rebooted into 5.1.1. Just making sure it worked fine. Now reboot into twrp. Wipe the same things again, and this time install RemixOS. Again, reboot into twrp. Now reboot. Should be okay. I just don't like having to constantly reflash twrp. Either way works great though.
th3fallen said:
Working fine for me here. Was getting constant reboots and bootlooping before I flashed back to 5.1.1 first though. Bootloader and vendor especially. Then wiped everything but internal in TWRP, then fastboot flashed Remix except for twrp. Booted into TWRP before booting into the system. Worked great after that.
That was my issue. Thanks
Click to expand...
Click to collapse
No problem.
Fallon9111 said:
So after the tablet seemingly working perfectly and no boot loops on install, it is now only bootlooping after rebooting (even after wiping cache) And this is after installing 5.11 factory image before remix os.
Will try factory reset etc.
Click to expand...
Click to collapse
I've rebooted several times, including changing DPI, and no issues. I know you said you installed 5.1.1 prior, but did you do a complete wipe before flashing RemixOS?
oediv said:
i am really interrested in this OS
but before i am doing anything i want to ask some questions
1) how far is google play and google play store integrated? can i open every app?
2) can i type without a manual keyboard?
3) is LTE supported in this version?
Click to expand...
Click to collapse
1. I haven't tried every single app, nor will I, but gmail, hangouts, drive, Google+, all work fine.
2. You mean, is there an onscreen keyboard? If so, then yes. I haven't connected a hardware keyboard.
3. Not sure. Give it a try and let us know! It won't break LTE, so worst case scenario is you just flash back to whatever you had before.
---------- Post added at 10:11 PM ---------- Previous post was at 10:10 PM ----------
maelfilk said:
So does it work for LTE variant? Also anyone running custom kernel with it? (afaik FIRE-ICE has special kernel)
Click to expand...
Click to collapse
The current 10.2.1 Fire and Ice will cause boot loops and break Wi-Fi. Elemental X for 5.1.1 works fine though. Running it now.

dictionary said:
I've rebooted several times, including changing DPI, and no issues. I know you said you installed 5.1.1 prior, but did you do a complete wipe before flashing RemixOS?
Click to expand...
Click to collapse
Yeah, I did a full factory image thing, and even let it boot once into 5.1.1 before rebooting back to fastboot and installing remix. I'm not sure what caused the boot loop problem, (wiping the caches and even a factory reset from twrp didn't fix this), but after flashing factory images then installing everything a 2nd time, the tablet seems to be working fine. So I'm not really sure why it went wrong (looking back in my terminal history I don't spot any obvious errors)...

Fallon9111 said:
Yeah, I did a full factory image thing, and even let it boot once into 5.1.1 before rebooting back to fastboot and installing remix. I'm not sure what caused the boot loop problem, (wiping the caches and even a factory reset from twrp didn't fix this), but after flashing factory images then installing everything a 2nd time, the tablet seems to be working fine. So I'm not really sure why it went wrong (looking back in my terminal history I don't spot any obvious errors)...
Click to expand...
Click to collapse
Yeah that's odd. After I flashed 5.1.1 and let it boot, I rebooted to TWRP, and wiped data, cache, system, and dalvik. Then rebooted to bootloader, then fastboot, and flashed boot.IMG, system.IMG, cache.IMG and vendor.IMG. Didn't have an issue. Glad it's working now for you though.

Camera not working after root

I first rooted my Nexus 6p that was completely stock using the system less root method. After I flashed the modified boot and twrp and rooted, my camera wasn't working. It just shows the camera icon and a black screen. I looked up the problem and many people said flashing a vendor image would work, but after doing so, it just tells me there was an internal error, so I reflashed the factory images. After doing so, camera still wasn't working. I also saw one person flashed a different modified boot but this only gives me a bootloop. Does anyone know a fix to the camera problem? Thanks!

kwcty6888 said:
I first rooted my Nexus 6p that was completely stock using the system less root method. After I flashed the modified boot and twrp and rooted, my camera wasn't working. It just shows the camera icon and a black screen. I looked up the problem and many people said flashing a vendor image would work, but after doing so, it just tells me there was an internal error, so I reflashed the factory images. After doing so, camera still wasn't working. I also saw one person flashed a different modified boot but this only gives me a bootloop. Does anyone know a fix to the camera problem? Thanks!
Click to expand...
Click to collapse
It's most likely caused by flashing the wrong boot.img, when you flashed the factory images to go back to stock did you flash the boot.img too?

Heisenberg said:
It's most likely caused by flashing the wrong boot.img, when you flashed the factory images to go back to stock did you flash the boot.img too?
Click to expand...
Click to collapse
I think I did.. I can try reflashed the stock boot.img again though. But I'm not sure what I did wrong because I just flashed the modified boot necessary for twrp?

kwcty6888 said:
I think I did.. I can try reflashed the stock boot.img again though. But I'm not sure what I did wrong because I just flashed the modified boot necessary for twrp?
Click to expand...
Click to collapse
TWRP doesn't require a modified boot.img anymore, it hasn't for a long time, unless you're using the Android N dev preview. You also need to ensure that you flash the right boot.img to suit your ROM build. For example, if you flash the MHC19I boot.img on a ROM that's based on MTC19T you'll get problems, like the camera not working.

Heisenberg said:
TWRP doesn't require a modified boot.img anymore, it hasn't for a long time, unless you're using the Android N dev preview. You also need to ensure that you flash the right boot.img to suit your ROM build. For example, if you flash the MHC19I boot.img on a ROM that's based on MTC19T you'll get problems, like the camera not working.
Click to expand...
Click to collapse
Unfortunately I re-flashed the factory boot and recovery (using build MTC19T), and the camera is still not working. Do you have any other thoughts? Thanks for your help!

kwcty6888 said:
Unfortunately I re-flashed the factory boot and recovery (using build MTC19T), and the camera is still not working. Do you have any other thoughts? Thanks for your help!
Click to expand...
Click to collapse
Flash the full factory images (except userdata), then flash the latest TWRP, not boot into TWRP and enter the wipe menu, select advanced wipe, tick the data box and wipe it. Boot up and see if that helps.

I need your help guys. (bricked nexus 6p)

Okay, so I've been reading XDA for a while now to root my devices and install custom ROMs and its been incredibly helpful. However I have a huge issue with my nexus 6p and can't find a way to solve it.
Here goes....
I bought it of eBay a few months ago and unlocked the boot loader and rooted the phone plus i also installed twrp and made a nandroid backup. I then installed pure nexus rom and the phone was working incredibly well.
Fast forward to this week, I decided I wanted to upgrade to cm13, since I missed the cm theme engine. So I Wiped my device clean using twrp. And installed cm 13 and the gapps then rebooted.
The phone booted perfectly but on the optimising apps screen it would reboot and tell me to enter the password that I originally had on the pure nexus ROM. After doing so it would re optimise the apps but would crash and reboot. It was doing this continuously.
Twrp also asked for this password on every boot before it let me see the main recovery menu.
So then I took the logical next step and decided to wipe the phone clean again using twrp. Seeing as my password seemed to not clear the first time.
After the wipe, I decided to use the original nandroid backup to restore my device as the password thing was still showing up. And cm 13 was still not installing. Neither was pure nexus.
Okay this is where it went downhill. I hit restore and had everything checked. The process was going well but instead of the restore completing and twrp saying it was successful. It crashed halfway and rebooted.
Since then its stuck in a bootloop. Its on the google splash screen and then reboots to the google splash screen continuously. And does not boot to the os.
On another note. The bootloader is still unlocked. The recovery works. And so does adb/fastboot. So I wouldn't consider it hard bricked.
Here's what I've tried so far:
I've used the wugfresh root toolkit to flash stock and unroot the phone. With softbrick checked. Still nothing. Phone boots to the splash screen and then reboots to the splash screen.
I then reflashed twrp 3.0.2-1 . which worked And its not asking for my password anymore.
Again I tried restoring from my nandroid and it crashed midway which makes me think the nandroid backup is/was corrupted causing the issue in the first place?
I've also tried to just restore and Flash twrp again and then install pure nexus ROM. And still nothing?
I can also still mount my phone to the PC and copy and remove files.
On another note I find it interesting that although the ROM is installed. And the storage bar on my PC is partially filled showing that it clearly has a ROM installed. The phone does not have the standard android file system. Just the twrp backup folder and that's it.
I would be honoured if you could help me out here. And get my 6p up and running again.
Thank you . [emoji45]

I would suggest you flash the factory stock system image using fastboot to get your 6P back up and running.
If you don't have the factory image they can be downloaded from here
Extract the factory image then use fastboot to flash
Code:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
Check out this guide which has all the information you need, especially around device encryption and flashing roms. Lastly gaining root is as simple as flashing SuperSU or Phh's SuperUser in TWRP.
I hope that helps, let me know if you get stuck.

Yea just flash stock image I had this happen to me before and flashing stock image fixed it.

Thanks guys. I'm going to read the guide and try it out. Then let you know how it all goes. Fingers crossed it all works
Sent from my ONE A2003 using Tapatalk

im_Zak said:
Thanks guys. I'm going to read the guide and try it out. Then let you know how it all goes. Fingers crossed it all works
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
FYI don't backup efs partition with that version of twrp. It's a known issue.

i did not realize that twrp had that issue
And guys, I followed the fastboot process by the letter and although everything worked well. The nexus 6p is still bootlooping on the google splash screen and not going any further. :crying:
What should I do? i've added the cmd window screenshot so you guys can have a look.

Try this thread:
http://forum.xda-developers.com/and...r-bootloop-t3454938/post68872362#post68872362
I worked for me when I was having issues. If it worked for you, please make sure to thank the OP in the thread.

this looks promising. thank you. i'll have a go now. might need your help if i get stuck somewhere though :good:

pctechdroid said:
Try this thread:
http://forum.xda-developers.com/and...r-bootloop-t3454938/post68872362#post68872362
I worked for me when I was having issues. If it worked for you, please make sure to thank the OP in the thread.
Click to expand...
Click to collapse
Thank you so so much dude. After countless hours trying everything to get my nexus 6p up and running to no avail this post did the trick.
Respect!!?✌✌??

im_Zak said:
Thank you so so much dude. After countless hours trying everything to get my nexus 6p up and running to no avail this post did the trick.
Respect!!
Click to expand...
Click to collapse
Upgrade to TWRP 3.0.2-2 real quick. You didn't need that guide(in terms of his nandroid) but I am glad it worked. Just need to wipe efs partition using adb commands.

I see. And I have upgraded to the latest twrp so hopefully it doesn't not happen again
Sent from my ONE A2003 using Tapatalk

im_Zak said:
I see. And I have upgraded to the latest twrp so hopefully it doesn't not happen again
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
Good deal!!! There's a build that's unofficial of 3.0.2-3 that you can also jump onto. The current version 3.0.2-2 has a bug with backups on Android N. There was a comprehensive post that someone made about the issues with the different versions but I cannot find it for the life of me.

Jammol said:
Good deal!!! There's a build that's unofficial of 3.0.2-3 that you can also jump onto. The current version 3.0.2-2 has a bug with backups on Android N. There was a comprehensive post that someone made about the issues with the different versions but I cannot find it for the life of me.
Click to expand...
Click to collapse
Thanks for the heads up!

Moto x pure XT1575 What am i doing wrong?!

I bought this phone used and the person who had it before me it rooted and installed some of different ROMs on it. After getting my used moto x pure 2015 running android 6.0. I booted it up and tested all the functions (including downloading a few apps) Wi-Fi, camera, audio/charging jacks ext. Everything worked fine. So did normal factory reset (not using TWRP) just to make sure everything was clean before using it as my daily. Then, (BUM BUM BUM!) when I tried to start downloading all my apps. None of them would download even though the Wi-Fi was working. Error 492 I think.
I started trying custom ROMs because I was having two big issues (apps not downloading and incoming call not bringing up accept/decline screen) with my stock rom. and wanted to fix those issues with a fresh stock image.
This is all new to me and has not been as easy as anticipated. If anyone knows a clean factory image I could flash or a fail proof fix to error 492 that would be helpful. I really just want to return to fully working Motorola stock android, but the files I have used haven’t fixed the issue. I have searched for a factory image without finding one…
Is there a way to flash the Motorola image through TRWP?
Otherwise, maybe you can help me with my flashing method, and maybe tell me what I am doing wrong. I tried to flash multiple stock images all with the same issue. I have also tried to flash Resurrection Remix, and Brocken OS, both having resulted in a bootloop. I am starting to think I have done something wrong. The steps I have taken so far have been these:
My bootloader is unlocked status code 3.
My phone is not rooted. Do I need root?
First I downloaded adb and fastboot.
Then I flashed TWRP (3.0.2).
I never installed the official Motorola stock image because flashing it from fast boot wouldn’t work and it couldn’t be flashed with TWRP because it is a .gz not a .zip. (I knew a .gz needs to be flashed with fastboot but I knew TWRP was easer so I didn’t fuss with it)
After flashing TWRP to my phone, I downloaded (yes, I checked the md5) the various ROMs to my computer then transfered them to my phone via micro SD card.
Here are the file’s names if that matters:
moto_x_pure_edition_stock_x1575_mphs24.49-18-3_v1-odexed
(booted and Wi-Fi but play store won’t download apps)
moto_x_pure_edition_stock_x1575_mph24.49-18_v1-odexed
(booted but no Wi-Fi)
Broken-v4.9.1-clark-6.0.1-OFFICIAL-20160824 (with Broken_gapps_lp5.1.x_09172015)
(Brocken was the only non-stock that got past boot, but I still couldn’t get past set up without an error and never made it to the system.)
ResurrectionRemix-N-v5.8.0-20161220-clark (7.1 gapps failed to flash but I booted it anyway.)
(boot loop after both of my tries)
I got Wi-Fi working on one of the above stock ROMs (so I KNOW it works) but couldn’t even turn Wi-Fi on in all the others.
The method I used to flash all of the above files in TWRP was:
Wipe
Full wipe (davlik cache, data, system, cache)
(used for RR and Brocken)
Factory reset (using TWRP) (davlik cache, data , cache)
Used for the stock ROMs or even after flashing .zip file I got the error: no OS installed.
Install
Select file of ROM flash (gapps if needed) and flash
I can’t remember which ones but on some of them after flashing I again did a factory reset.
Then I rebooted
Thanks for reading. Sorry it was so long. I tried to add as much useful information as possible. Hopefully someone smarter than me will see my error(s) and help me get my phone into fully working order.

cont.
I really just want to return to fully working Motorola stock android, but the files I have used haven’t fixed the issue. I have searched for a factory image without finding one…
Is there a way to flash the Motorola image through TRWP?
Otherwise maybe you can help me out with my flashing method and maybe tell me what I am doing wrong. I tried to flash multiple stock images all with the same issue. I have also tried to flash Resurrection Remix, and Brocken OS, both having resulted in a bootloop. I am starting to think I have done something wrong. The steps I have taken so far have been these:
My bootloader is unlocked status code 3.
My phone is not rooted. Do I need root?
First I downloaded adb and fastboot.
Then I flashed TWRP (3.0.2).
I never installed the official Motorola stock image because flashing it from fast boot wouldn’t work and it couldn’t be flashed with TWRP because it is a .gz not a .zip. (I knew a .gz needs to be flashed with fastboot but I knew TWRP was easer so I didn’t fuss with it)
After flashing TWRP to my phone, I downloaded (yes, I checked the md5) the various ROMs to my computer then transfered them to my phone via micro SD card.
Here are the file’s names if that matters:
moto_x_pure_edition_stock_x1575_mphs24.49-18-3_v1-odexed
(booted and Wi-Fi but play store won’t download apps)
moto_x_pure_edition_stock_x1575_mph24.49-18_v1-odexed
(booted but no Wi-Fi)
Broken-v4.9.1-clark-6.0.1-OFFICIAL-20160824 (with Broken_gapps_lp5.1.x_09172015)
(Brocken was the only non-stock that got past boot, but I still couldn’t get past set up without an error and never made it to the system.)
ResurrectionRemix-N-v5.8.0-20161220-clark (7.1 gapps failed to flash but I booted it anyway.)
(boot loop after both of my tries)
I got Wi-Fi working on one of the above stock ROMs (so I KNOW it works) but couldn’t even turn Wi-Fi on in all the others.
The method I used to flash all of the above files in TWRP was:
Wipe
Full wipe (davlik cache, data, system, cache)
(used for RR and Brocken)
Factory reset (using TWRP) (davlik cache, data , cache)
Used for the stock ROMs or even after flashing .zip file I got the error: no OS installed.
Install
Select file of ROM flash (gapps if needed) and flash
I can’t remember which ones but on some of them after flashing I again did a factory reset.
Then I rebooted
Thanks for reading. Sorry it was so long. I tried to add as much useful information as possible. Hopefully someone smarter than me will see my error(s) and help me get my phone into fully working order.

I think this thread will help you: https://forum.xda-developers.com/showthread.php?t=3489110
Sent from my XT1572 using Tapatalk

Install stock firmware via fastboot... if that dont fix the issue, install TWRP make a full wipe, FULL, and install the stock firmware again, eventualy that sould fix the issue.

RK2116 said:
Install stock firmware via fastboot... if that dont fix the issue, install TWRP make a full wipe, FULL, and install the stock firmware again, eventualy that sould fix the issue.
Click to expand...
Click to collapse
I'm having a similar issue. Tried the TruPure rom but I want to switch back to stock. If I do a full wipe, would I be able to use the files that Motorola provides on their website and flash those throught fastboot? Or through TWRP? Any chance you have a link to a guide on how to do the latter option (installing through TWRP)? I'm just trying to get my device back to 100% stock so that I can receive OTA.

cdiaz8 said:
I'm having a similar issue. Tried the TruPure rom but I want to switch back to stock. If I do a full wipe, would I be able to use the files that Motorola provides on their website and flash those throught fastboot? Or through TWRP? Any chance you have a link to a guide on how to do the latter option (installing through TWRP)? I'm just trying to get my device back to 100% stock so that I can receive OTA.
Click to expand...
Click to collapse
Odexed one, install with TWRP, full wipe before doing that, no GApps, just ROM, them, install stock recovery vía fastboot. After that you Will be stock with OTAs.
https://forum.xda-developers.com/mo...t/rom-marshmallow-6-0-september-2016-t3536120

RK2116 said:
Odexed one, install with TWRP, full wipe before doing that, no GApps, just ROM, them, install stock recovery vía fastboot. After that you Will be stock with OTAs.
https://forum.xda-developers.com/mo...t/rom-marshmallow-6-0-september-2016-t3536120
Click to expand...
Click to collapse
Thank you for sharing that link. I think I get it but it seems too easy considering what I've tried so far. Just to make sure I get it:
I should download the odexed rom, go to twrp and wipe data, cache and dalvik then flash the odexed rom through the install function? And thats it? I've literally tried a ton of stuff so if this takes care of it, this is great!

cdiaz8 said:
Thank you for sharing that link. I think I get it but it seems too easy considering what I've tried so far. Just to make sure I get it:
I should download the odexed rom, go to twrp and wipe data, cache and dalvik then flash the odexed rom through the install function? And thats it? I've literally tried a ton of stuff so if this takes care of it, this is great!
Click to expand...
Click to collapse
Yes, also wipe system, make a backup before If you want, but remember, for the OTAs support you need yo flash the stock recovery via fastboot. Good luck.

RK2116 said:
Yes, also wipe system, make a backup before If you want, but remember, for the OTAs support you need yo flash the stock recovery via fastboot. Good luck.
Click to expand...
Click to collapse
This got me back to stock! You are the real MVP.
So I remember seeing a recovery.img file in the factory image that motorola posted on its site. Does it have to be a specific stock recovery or do I need a specific one to match with the file I just installed?
thanks again

cdiaz8 said:
This got me back to stock! You are the real MVP.
So I remember seeing a recovery.img file in the factory image that motorola posted on its site. Does it have to be a specific stock recovery or do I need a specific one to match with the file I just installed?
thanks again
Click to expand...
Click to collapse
Just a stock one, if Motorola have one use that.

RK2116 said:
Just a stock one, if Motorola have one use that.
Click to expand...
Click to collapse
So I'm on stock build 49-18-8 and flashed the recovery from 49-18-3. I went into fastboot and selected recovery. I got the android character with an !
I then did the power button and volume up and got into stock android recovery. Am I supposed to see the android character with ! each time I try to reach the recovery menu? Just wondering if I did this correctly.
Thanks again for pointing me to these resources!

cdiaz8 said:
So I'm on stock build 49-18-8 and flashed the recovery from 49-18-3. I went into fastboot and selected recovery. I got the android character with an !
I then did the power button and volume up and got into stock android recovery. Am I supposed to see the android character with ! each time I try to reach the recovery menu? Just wondering if I did this correctly.
Thanks again for pointing me to these resources!
Click to expand...
Click to collapse
Yes.

Stuck in bootloop trying to flash 7.1 custom rom

My phone is android 6.0 and I've been using "TruPureXMM 2.9" ever since it first came out. I have a February 1, 2016 android security patch level and my system version is 24.11.18 clark_retus.retus.en.US retus
I had an older version of twrp so I just updated it to the latest one before attempting this ofc...
I tried flashing the latest RR and AICP and both give me boot loops and I always get this one problem where it says
"mount: failed to mount /dev/block/bootdevice/by-name
/modem at /firmware: Device or resource busy"
I'm not sure if this has anything to do with the bootloop though...
Going to recovery after seeing the bootloop I always get the "keep system read only?" prompt where i swipe to allow modification but i usually just restore back to my backup from there... i dont think allowing it and trying to boot again will get rid of the bootloop...
I followed the process of first doing a full wipe with twrp > flash rom > flash gapps > restart system
no idea what i'm doing wrong..

OppaiHeroStar said:
My phone is android 6.0 and I've been using "TruPureXMM 2.9" ever since it first came out. I have a February 1, 2016 android security patch level and my system version is 24.11.18 clark_retus.retus.en.US retus
...
I followed the process of first doing a full wipe with twrp > flash rom > flash gapps > restart system
no idea what i'm doing wrong..
Click to expand...
Click to collapse
1st - you need twrp 3.x+,
2nd - full wipe - format data, adv.wipe - all without micro sd.
3rd - flash rom, flash gapps(opengapps.org, ≤mini, arm64, 7.1)
Last Rr is for Nougat modem - you are on MM modem.
Flash RR 21.11.2017.
https://forum.xda-developers.com/mo...ial-resurrection-remix-v5-8-3-t3637204/page36

dzidexx said:
1st - you need twrp 3.x+,
2nd - full wipe - format data, adv.wipe - all without micro sd.
3rd - flash rom, flash gapps(opengapps.org, ≤mini, arm64, 7.1)
Last Rr is for Nougat modem - you are on MM modem.
Flash RR 21.11.2017.
https://forum.xda-developers.com/mo...ial-resurrection-remix-v5-8-3-t3637204/page36
Click to expand...
Click to collapse
The first 3 steps I've already done that since the beginning
Where can i get the nougat modem/is it possible to update to it? I guess that's the reason every single 7.1 custom rom I tried in the android development section gave me boot loops...
And could you link the 21.11.2017 version of RR? I'm looking at the download links for RR and I dont see one with that exact date
edit-just saw your edit

Custom roms for MM modem works better.

I fully wiped using TWRP, checked everything I possibly could except my micro SD card and I flashed RR-N-v5.8.5-20171121-clark-Final.zip then gapps arm64, 7.1 nano and it's still giving me boot loops. I'm using TWRP 3.2.1-0
im gonna try using gapps arm64 7.1 mini really quick since you said I should use that one and see if it boot loops... - Edit guess I was too optimistic thinking this would fix it

Bugs probably after flashing december RR.
Change twrp to 3.1.x, reboot twrp, change all partitions to ext4 - adv wipes - One by one - cache, system, data, reboot twrp.
Change back to f2fs - only cache & data, wipe all, flash what I wrote.

dzidexx said:
Bugs probably after flashing december RR.
Change twrp to 3.1.x, reboot twrp, change all partitions to ext4 - adv wipes - One by one - cache, system, data, reboot twrp.
Change back to f2fs - only cache & data, wipe all, flash what I wrote.
Click to expand...
Click to collapse
changed to 3.1.1-0 and did everything you said, still have boot loop...
when flashing this RR i still get this, not sure if it's a problem but thought I would just let you know
"mount: failed to mount /dev/block/bootdevice/by-name
/modem at /firmware: Device or resource busy"

OppaiHeroStar said:
changed to 3.1.1-0 and did everything you said, still have boot loop...
"mount: failed to mount /dev/block/bootdevice/by-name
/modem at /firmware: Device or resource busy"
Click to expand...
Click to collapse
It doesn`t matter.
Try another custom - LOS f.e.
If bootloop still will be - you should flash full stock.
Last MM for RetUs

dzidexx said:
It doesn`t matter.
Try another custom - LOS f.e.
If bootloop still will be - you should flash full stock.
Last MM for RetUs
Click to expand...
Click to collapse
I tried crDroidAndroid-7.1.2-20171119-clark-v3.8.3.zip and it still boot loops :\ I also already tried LineageOS and AICP before we started talking
I went back to my backup and it put me in a bootloop which never happened before but changing cache back to ext4 instead of f2fs fixed it..

OppaiHeroStar said:
when flashing this RR i still get this, not sure if it's a problem but thought I would just let you know
"mount: failed to mount /dev/block/bootdevice/by-name
/modem at /firmware: Device or resource busy"
Click to expand...
Click to collapse
A little late to chime in and this does not help with your current situation, but here's a little advice. I flash a lot of ROMs (how else am I going to test builds right?). This error happens all the time, BUT if you flash a ROM twice it should not show on the 2nd flash.
So flash order goes:
Wipe/Factory reset
Format data x3 (yes I format my data 3 times for every ROM)
Reboot
Wipe/Factory reset
ROM
ROM again
GAPPS
Wipe caches
Reboot
Do the Initial setup
Reboot before use
OPTIONAL Kernel (if its not already build in)
OPTIONAL Magisk (I never flash Magisk on a clean build but heck I'm expecting a NON boot most of the time anyways)

At this point I would flash the stock Nougat image via fastboot to get the device operational again... Then look at TWRP, root, or custom ROM.

acejavelin said:
At this point I would flash the stock Nougat image via fastboot to get the device operational again... Then look at TWRP, root, or custom ROM.
Click to expand...
Click to collapse
so should I just straight up flash the nougat image via fastboot from your thread here? https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142
i dont need to go back to mm stock or something first? I don't really have much knowledge about this.

OppaiHeroStar said:
so should I just straight up flash the nougat image via fastboot from your thread here? https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142
i dont need to go back to mm stock or something first? I don't really have much knowledge about this.
Click to expand...
Click to collapse
Correct... And verify everything is working properly before you flash TWRP, root, or take any OTA update.

acejavelin said:
Correct... And verify everything is working properly before you flash TWRP, root, or take any OTA update.
Click to expand...
Click to collapse
so i finished flashing that nougat firmware and looks like everything is working ok, does that mean I can try flashing custom roms after twrp now?

OppaiHeroStar said:
so i finished flashing that nougat firmware and looks like everything is working ok, does that mean I can try flashing custom roms after twrp now?
Click to expand...
Click to collapse
Boot TWRP (don't flash it) and make a full back, and I would recommend not talking any OTAs either.
Then knock yourself out... You can always get back to this state if things go badly.

acejavelin said:
Boot TWRP (don't flash it) and make a full back, and I would recommend not talking any OTAs either.
Then knock yourself out... You can always get back to this state if things go badly.
Click to expand...
Click to collapse
was finally able to flash a custom rom without bootloops!
thank you and everyone else here for the help I honestly really appreciate it

OppaiHeroStar said:
was finally able to flash a custom rom without bootloops!
thank you and everyone else here for the help I honestly really appreciate it
Click to expand...
Click to collapse
What custom did you flashed?

dzidexx said:
What custom did you flashed?
Click to expand...
Click to collapse
I tried out AICP, AOKP, and RR. All latest versions and they worked but for some reason my data doesn't work on any of those customs.
guess my happiness was short lol. Considering just staying stock now

OppaiHeroStar said:
I tried out AICP, AOKP, and RR. All latest versions and they worked but for some reason my data doesn't work on any of those customs.
guess my happiness was short lol. Considering just staying stock now
Click to expand...
Click to collapse
I'm not sure for others but RR - only 5.8.5-04.12 works with N modem.
Did you check/set access points properly?
All customs for N modem(I think) have problems with notification sound, so you can stay at stock.

dzidexx said:
I'm not sure for others but RR - only 5.8.5-04.12 works with N modem.
Did you check/set access points properly?
All customs for N modem(I think) have problems with notification sound, so you can stay at stock.
Click to expand...
Click to collapse
I'm using t-mobile and I've checked the access points, clicking on the one im using and hitting save doesn't fix it. Always getting a notification telling me to sign in to network. Not sure what else I can do. I'll give it a day since I had this kind of problem before when I switched sim cards and data didn't work until the next day
Edit - just went back to stock and my data doesn't work now either... just going to stay at RR now and hope my data fixes itself because my access point settings for tmobile should be correct since I looked it up on the official website..