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.

Constant FC's on most ROM installations..

Hey guys, I ran into a rather odd issue yesterday and can't for the life of me figure out how to get my phone back to normal..
I upgraded TWRP to 3.0.2-0, wiped data, system, dalvik/cache, and attempted to install AOSiP 4.1 + Banks 4/08 Gapps, but after the boot, I get "Unfortunately SetupWizard has stopped", and after getting through the setup, "Unfortunately Theme Provider has stopped", if I click the Theme app it FC's.
This happens on EVERY single ROM I try to install, except Resurrection Remix. (The ROM I was on before flashing AOSiP.) I have tried going back to stock MHC19Q and starting fresh, but I still get FC's. I have also tried every recent TWRP, and MultiROM TWRP. Nothing is working.
Please help...
Edit: @big nu has the same issue..
https://tapatalk.com/shareLink?url=...share_tid=3357511&share_fid=3793&share_type=t

Are you fastbooting the factory images or trying to flash the stock firmware through twrp? If you haven't, fastboot the images including the recovery.

Eric214 said:
Are you fastbooting the factory images or trying to flash the stock firmware through twrp? If you haven't, fastboot the images including the recovery.
Click to expand...
Click to collapse
I fastboot everything. I flashed the stock image from my PC but still no luck...

Perhaps any layers installed?
If so, try removing them from inside TWPR and see if it boots then without FCs.

Casmo said:
Perhaps any layers installed?
If so, try removing them from inside TWPR and see if it boots then without FCs.
Click to expand...
Click to collapse
No Layers were previously installed at all. I was last on a CMTE ROM. I checked /Vendor, just to be sure..

adzcache said:
No Layers were previously installed at all. I was last on a CMTE ROM. I checked /Vendor, just to be sure..
Click to expand...
Click to collapse
So you fastbooted back to stock and booted into the stock system? And you get those issues in the stock firmware?
Sent from my Nexus 6P

jesssiii said:
So you fastbooted back to stock and booted into the stock system? And you get those issues in the stock firmware?
Sent from my Nexus 6P
Click to expand...
Click to collapse
Yes, exactly. I don't understand how this is even possible,
especially after wiping and going back to stock many times.
Literally every ROM installation ends the same.

adzcache said:
Yes, exactly. I don't understand how this is even possible,
especially after wiping and going back to stock many times.
Literally every ROM installation ends the same.
Click to expand...
Click to collapse
1) When you fastboot flash back to stock after a custom rom, what is your process? Do you perform a factory reset in TWRP prior to using fastboot?
2) Are you verifying the MD5 of the factory image prior to flashing?
3) What is the file name of the factory image you are using?
4) Are you able to reproduce this issue with different gapps packages, say Open gapps or an older/newer version of Banks gapps?
4) Are you downloading each of these files over WiFi or Mobile Data onto your phone?
5) Are you also checking the MD5 of each zip prior to flashing?
Based on your post, it looks like you are using one gapps zip and experiencing this issue on every rom. This sounds like a corrupt gapps zip.
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
1) When you fastboot flash back to stock after a custom rom, what is your process? Do you perform a factory reset in TWRP prior to using fastboot?
2) Are you verifying the MD5 of the factory image prior to flashing?
3) What is the file name of the factory image you are using?
4) Are you able to reproduce this issue with different gapps packages, say Open gapps or an older/newer version of Banks gapps?
4) Are you downloading each of these files over WiFi or Mobile Data onto your phone?
5) Are you also checking the MD5 of each zip prior to flashing?
Based on your post, it looks like you are using one gapps zip and experiencing this issue on every rom. This sounds like a corrupt gapps zip.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
1. Yes, before flashing the stock image I boot into TWRP and factory reset, I have also tried wiping everything including internal storage in my many attempts to save this phone.
2. No, in all my years on an Android I have never had to check an MD5 and to be perfectly honest I don't really understand how to check MD5's.
3. angler-mhc19q-factory-f5a4e7a1.tgz
4. Yes every Gapps package causes the same outcome. I have tried Slim Gapps, OpenGapps, and Banks Gapps, I have tried downloading them first on my phone, then tried downloading everything fresh from my PC and moving them to my internal storage.
5. Again, not to sure on how to verify these MD5's..
I have tried multiple ROMs, and multiple Gapps. All flashes end the same. I also tried every newer version of TWRP and gone back to stock over 6 times in the past 2 days.
Edit: I'm starting to think that this issue could be related to my Google Account and restoring my device through the Setup, because I have flashed a ROM (DU 04/08) and made it through the setup with no FC's, so long as I don't sign into my Google Account. If I sign in FC's galore and occasional random reboots. I am also experiencing very slow download speeds on LTE and WiFi when downloading Gapps or a different ROM.

adzcache said:
1. Yes, before flashing the stock image I boot into TWRP and factory reset, I have also tried wiping everything including internal storage in my many attempts to save this phone.
2. No, in all my years on an Android I have never had to check an MD5 and to be perfectly honest I don't really understand how to check MD5's.
3. angler-mhc19q-factory-f5a4e7a1.tgz
4. Yes every Gapps package causes the same outcome. I have tried Slim Gapps, OpenGapps, and Banks Gapps, I have tried downloading them first on my phone, then tried downloading everything fresh from my PC and moving them to my internal storage.
5. Again, not to sure on how to verify these MD5's..
I have tried multiple ROMs, and multiple Gapps. All flashes end the same. I also tried every newer version of TWRP and gone back to stock over 6 times in the past 2 days.
Edit: I'm starting to think that this issue could be related to my Google Account and restoring my device through the Setup, because I have flashed a ROM (DU 04/08) and made it through the setup with no FC's, so long as I don't sign into my Google Account. If I sign in FC's galore and occasional random reboots. I am also experiencing very slow download speeds on LTE and WiFi when downloading Gapps or a different ROM.
Click to expand...
Click to collapse
Did you figure out any way to get around the FCs when signing into your account?
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
Did you figure out any way to get around the FCs when signing into your account?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Yes sir, I found a more or less, temporary fix to get around the FC's. I wiped my phone completely, several times, and flashed the stock MHC19Q image a few times and used TWRP 3.0.2-0 to flash DU 04/08, Nano OpenGapps 04/14, and totally avoided signing into my Google Account. After rebooting I signed into Google. No FC's!!! Yay! Then waited 3 hours for my contacts to be synced. (App data was also gone from Settings>Accounts for some reason for 3+ hours) after 3 hours of waiting, everything seems to be working again... For the time being. I'm now scared to flash a ROM other then DU, and my Restorations on 3.0.2-0 have taken over 300+ seconds, but before (3.0.0-1) a restoration was just over 60 seconds...
Weird stuff going on here for sure but at least I got DU! ?

adzcache said:
Yes sir, I found a more or less, temporary fix to get around the FC's. I wiped my phone completely, several times, and flashed the stock MHC19Q image a few times and used TWRP 3.0.2-0 to flash DU 04/08, Nano OpenGapps 04/14, and totally avoided signing into my Google Account. After rebooting I signed into Google. No FC's!!! Yay! Then waited 3 hours for my contacts to be synced. (App data was also gone from Settings>Accounts for some reason for 3+ hours) after 3 hours of waiting, everything seems to be working again... For the time being. I'm now scared to flash a ROM other then DU, and my Restorations on 3.0.2-0 have taken over 300+ seconds, but before (3.0.0-1) a restoration was just over 60 seconds...
Weird stuff going on here for sure but at least I got DU!
Click to expand...
Click to collapse
I had a problem like that. What I did was
Boot into Recover - TWRP 2.8 something
Did the Wipe Data / Factor Reset
Flashed The Rom - For me it was Pure Nexus - April 7, 2016
Flashed The Kernel - For Me Element X
Then wiped Davlik/Cache
Then after that I rebooted let it do what it had to do to boot up. Then rebooted to recovery
Then flashed the GAPPS - for me i used BaNkS-Dynamic-GApps-6.x.x-10-20-15
Then wiped DAvlik/Cache
Then rebooted and let it do its thing again. - I did not get any system startup failed.
Maybe you can not flash the GAPPS all together because the phone is a smart phone but it can still be DUMB.. LOL
Then I did not do a restore of apps from the automatic thing when it asks I just went to pla stoer and let it download what I needed from the my app section.

I'm still facing issues, but at least there are painfully long fixes to make everything work normally... Just pissed, every other android phone I have had, never faced such a persistent issue with rooting and flashing custom ROMs. Especially after restoring to stock..

Sorry to bump this thread, just hoping someone may have a suggestion that may fix up this rather odd issue I've been plagued with?

Quick fix for anyone else facing this:
Downgrade to MHC19I and when flashing recovery, flash TWRP 3.0.0-1, then format userdata in fastboot, copy your files over via PC and flash ROM + Gapps.

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.

How can I revert to factory state in my Leeco Le s3 (x522 US variant)

Hi friends! I really feel frustrated with this phone.
I began by using fastboot to flash TWRP (twrp-3.1.1-1-s2), used it to flash Lineageos 13.0, but IR BLASTER doesn't work, then I flashed 14.1 and IR blaster, Sim detection, flashlight and camera don't work correctly, I tried Resurrection remix and MIUI8 too but I gave up, neither of those Custom Roms works as I wanted them to.
So I went back to EUI and all was well until I wanted to update OTA, it gave me an error every time, tried to do it with update.zip but nothing, using stock recovery and nothing. I used TWRP and wipe everything again, now this thing won't start it just bootloops, I tried everything for two days and every time I use a stock ROM (5.8.020s) it gives me an error, or tells me it can't be read. When I factory reset and format everything it tells me I dont have an OS installed, so I'm completely lost I don't know what else to do and I can't return the phone because I'm overseas right now.
I really need to have it as when I got it the first time because at least it was functional but I just can't get it to work
I could really use some help right now :crying: thanks in advance guys!

Nikodominiko said:
Hi friends! I really feel frustrated with this phone.
I began by using fastboot to flash TWRP (twrp-3.1.1-1-s2), used it to flash Lineageos 13.0, but IR BLASTER doesn't work, then I flashed 14.1 and IR blaster, Sim detection, flashlight and camera don't work correctly, I tried Resurrection remix and MIUI8 too but I gave up, neither of those Custom Roms works as I wanted them to.
So I went back to EUI and all was well until I wanted to update OTA, it gave me an error every time, tried to do it with update.zip but nothing, using stock recovery and nothing. I used TWRP and wipe everything again, now this thing won't start it just bootloops, I tried everything for two days and every time I use a stock ROM (5.8.020s) it gives me an error, or tells me it can't be read. When I factory reset and format everything it tells me I dont have an OS installed, so I'm completely lost I don't know what else to do and I can't return the phone because I'm overseas right now.
I really need to have it as when I got it the first time because at least it was functional but I just can't get it to work
I could really use some help right now :crying: thanks in advance guys!
Click to expand...
Click to collapse
So I managed to fix the problem. When you root this phone or in fact just flash a custom recovery like TWRP, it changes the model of the phone, If you unroot the phone you won't be able to receive OTAs anymore even if you are on stock ROM, you'll always get an error at the end of the update even if you do it manually, if you are dumb like me and didn't make a backup of your stock system, you won't find any help on the internet more than to install a custom ROM and learn to live with the errors and bugs. I did not want that so to be able to get the phone to its factory state, what I did was this:
1. Download: stock recovery image for Le s3 x522 (official, you can find it anywhere), LeEco_X522_5.8.019S_OTA.zip, bootloader-20S-s2.zip, twrp_s3.img (the chinese TWRP recovery) and S2_X522-NA-OP-IFXNAOP5802102141S-5.8.021S.zip
2. Save those zips to the root of the phone, obviously the .img files you are going to flash them through your PC
3. Put the phone in bootloader mode. command: fastboot flash recovery recovery.img (the official recovery)
4. fastboot boot twrp (the chinese one)
5. From this step what I did was pure luck
6. wipe cache and dalvik and install LeEco_X522_5.8.019S_OTA.zip
7. wipe cache and dalvik and install bootloader-20S-s2.zip
8. wipe cache and dalvik and install S2_X522-NA-OP-IFXNAOP5802102141S-5.8.021S.zip
9. Reboot
How and Why did this worked I don't know, I am a noob but please try if you find yourself in the same situation as I was, you don't lose anything with trying, if this doesn't work don't blame me, this worked for my phone.
Greetings friends!

Thanks for putting this guide together, I am in a similar situation in that I reverted to stock everything (1. Installed YDSS chinese twrp, 2. Installed S2_X522-NA-OP-IFXNAOP5802012141S-5.8.020S.zip. This flash was supposed to have installed the stock recovery and overriden the ydss twrp, but didn't, I had to manually flash that after. Everything came back smooth but my updates also failed at recovery.
I am wondering where you got the LeEco_X522_5.8.019S_OTA.zip, bootloader-20S-s2.zip & twrp_s3.img from?

Nice to hear you finally got it to work ! Aren't the X520 and the X522 the same phone ? Why official ROMs are not compatible ?

wiped cache in TWRP now no root

A little background first, I have had my galaxy (sm-g975F exynos) rooted for some time now with magisk. I wanted to update the firmware, reroot and install TWRP in the process. Took me a few hours and only one mistake but at the end I was successful. This was 2 days ago and Ive been working on customizing ever since.
Now onto the problem, I noticed the camera app didn't work any more when I boot into magisk mode. When I boot in standard mode the camera works fine. I tried force quitting, rebooting, reverting to original settings, etc... and no change. I started reinstalling system apps I removed with debloat thinking I may have removed a system app that had an effect but again no change. I read somewhere that clearing/wiping cache may help so I booted into TWRP, went into advanced wipe and only wiped "cache". Now when I reboot into standard mode the phone works fine, but if I boot into magisk mode I cant get past the lock screen. Basically magisk mode boots fine but when I enter my pin it just goes back to lock screen. So I rebooted into standard mode and made it so there was no lock screen(no pin, no fingerprints, etc...) then I tried rebooting in magisk mode to see if this will get me past the lock screen and now it just bootloops in magisk mode only.
So my first problem is getting my phone back into magisk mode, my second problem is the camera. is there a safe way to reflash with TWRP or am I going to have to redo the whole process with odin?
Thank you in advance for any help, I have searched online but haven't found anyone that has had issues wiping cache with TWRP

update, tried downloading magisk zip from magisk manager, rebooted into TWRP and tried installing the zip, no change. wiped dalvik cache for kicks, no change.
update #2, also tried uninstalling or disabling root privilege apps such as novalauncher, liveboot and buttonmapper but I was only able to do this in non-magisk mode, again no change.

Update #... what # am I on?
So I started fresh, reinstalled stock firmware, reinstalled magisk and reinstalled TWRP. Phone is working fine except for the fact the camera doesnt work in magisk mode. I am now 100% positive this is due to magisk or TWRP. I will try and install another camera app to see if it works, but would still like to figure out how to get samsungs camera app to work in magisk mode.

So I decided to enter into safe mode which ultimately broke my magisk install. Same scenario as before, I can boot into non-magisk mode now but if I try and boot into magisk mode I cant get past lock screen. However while in safe mode and now non-magisk mode, the camera actually does work. So as it stands I can either have my phone rooted and not be able to use the camera or not have it rooted and be able to use the camera. If anyone has any suggested work arounds, please feel free to chime in. In the mean time I will start over again.

another update.
I reflashed stock firmware along with magisk. I now have root as well as a working camera, and yes the camera works in magisk mode and non-magisk mode. I am now looking to blame TWRP or multidisabler in breaking the camera. I know that having TWRP on a galaxy S10+ is fairly new to the market but I am surprised that I cannot find a single other report of someone elses camera not working after installing TWRP. I feel like I should keep trying things but I also have reflashed firmware, magisk, TWRP 3 times in the past 5 days and I just want a working phone with root. The only other ideas I had was to either give the camera root access or make the camera a system app. I dont see why I would/should need to do that though.
Moderator can you please change the title of this thread to "Camera not working after installing TWRP" please and thank you if it is possible.