Database Users

[GUIDE] How to install ColorOs with OTA update

Hi everyone, just in case someone wanna try ColorOs (default OS for chinese OnePlus one).
There's some zip files flashable with twrp but, after that, you can't use OTA update and have to manually download the upgrade and flash it.
For me is annoying so I've flashed the rom, with gapps without installing a recovery.
First download ColorOs from here:
https://mega.co.nz/#!BkpwyYSB!rkYSkFI28vFGuhtsIli-vyDdsb4ZZp1-MX1cLLtaiRo
Download Gapps from cyano (select the 10.2):
http://wiki.cyanogenmod.org/w/Google_Apps
Download Twrp (we will use it but we will not install it)
http://teamw.in/project/twrp2/231
Remember, this process will wipe everything on your phone, so MAKE A BACKUP!!
Extract color.zip and boot the phone in fastboot mode (volume up + power), connect it to you computer.
Important if you have a 16gb phone, the second command is
Code:
fastboot flash userdata userdata.img
Code:
fastboot flash boot boot.img
fastboot flash userdata userdata_64g.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot reboot
After that, fastboot reboot will reboot your phone. You have to wait a bit the first time. Now, select english (ColorOs support only chinese and english). go to system > update a make the system update (I had to do two consecutive updates), don't worry, it's really slow.
Now, the phone is up to date but has no Google app and, the ColorOs recovery isn't able to flash them so, connect the phone and copy the gapps into the phone, after that reboot it in fastboot mode (volume up + power).
Code:
fastboot boot <twrp_image.img>
This will boot temporary the twrp recovery, go to install zip from sd card and flash the gapps, after that, you can reboot the phone and enjoy ColorOs with google apps.
Hope this could help.
EDIT:
If someone want to root it, have to install (using TWRP) this
http://d-h.st/zJ8
I've NOT tried this file.

THX!

Could I go back to a other ROM like mahdi ROM whenever I want by just flashing a back up? And is this color OS 2.0.11 or 1.2?

AndroidInsanity said:
Could I go back to a other ROM like mahdi ROM whenever I want by just flashing a back up? And is this color OS 2.0.11 or 1.2?
Click to expand...
Click to collapse
Yes, you obviously can but, if you use this method, first you have to flash twrp or another recovery.
You can backup the phone, save the backup folder to your pc.
If you want to rollback, copy the folder that you have saved into your pc, flash twrp and restore everything.
I used this method becouse, in this way you have ota updates with no problems.
And this method, after the system update, will give you 2.0.11

MultiRom?

mojna37 said:
MultiRom?
Click to expand...
Click to collapse
I tried colorOS version 2.0.11 using multirom but it doesn't boot up.
MIUI boots and works flawlessly on multirom.

Miui works fine to me to. ColorOS faild on install.
Sent from my OnePlus One using Taptalk

mojna37 said:
Miui works fine to me to. ColorOS faild on install.
Sent from my OnePlus One using Taptalk
Click to expand...
Click to collapse
Following this guide?
ColorOs has a lot of problems with twrp flashable zips.
I preferred to share a guide that uses fastboot. I've tried all of this command and, now I'm testing ColorOs, no issues at all.
ColorOs is a really good rom, smooth, nice with battery, full of functionality and, the best camera, other rom seems to use different hardware.
The rom is really too similar to Ios and I don't like ios clones but, I think that it's a rom that deserves a try.

Castore said:
Following this guide?
ColorOs has a lot of problems with twrp flashable zips.
I preferred to share a guide that uses fastboot. I've tried all of this command and, now I'm testing ColorOs, no issues at all.
ColorOs is a really good rom, smooth, nice with battery, full of functionality and, the best camera, other rom seems to usa different hardware.
The rom is really too similar to Ios and I don't like ios clones but, I think that it's a rom that deserves a try.
Click to expand...
Click to collapse
I mean to install with MultiRom. I will try it using fastboot soon.
Sent from my OnePlus One using Taptalk

Castore said:
Yes, you obviously can but, if you use this method, first you have to flash twrp or another recovery.
You can backup the phone, save the backup folder to your pc.
If you want to rollback, copy the folder that you have saved into your pc, flash twrp and restore everything.
I used this method becouse, in this way you have ota updates with no problems.
And this method, after the system update, will give you 2.0.11
Click to expand...
Click to collapse
Thanks. Will follow instructions and let you know if I succeed later (Y) thanks for the help

I get a fail when flashing system
C:\adb>fastboot flash system system.img
sending 'system' (890182 KB)... FAILED (remote: data too large)
finished. total time: 0.003s
EDIT: just updated my fastboot. SEEMS to be ok now
SUCCESS! thanks ! really like it. although I wish it had the 50MP photo option, someone on the oneplus forum said it did :S

By the way. is their a method to root color OS?

@AndroidInsanity
How did you solved the problem with fastboot dimension exceed?
I had the same problem with cyano 11s and Fedora.
I've edited the first post with a link that root the rom.
I've not tried to root the rom.

Can someone extract the modem image from this please? It won't complete download for me.
Sent from my A0001 using Tapatalk

Hello Bro, from your understanding, will there be any problem on the 3G and 4G network after flashing to Color? Thanks

Castore said:
@AndroidInsanity
How did you solved the problem with fastboot dimension exceed?
I had the same problem with cyano 11s and Fedora.
I've edited the first post with a link that root the rom.
I've not tried to root the rom.
Click to expand...
Click to collapse
Grab the latest android SDK and download platform tools from it then replace your current fastboot.exe with the one in the latest SDK.

etlok said:
Hello Bro, from your understanding, will there be any problem on the 3G and 4G network after flashing to Color? Thanks
Click to expand...
Click to collapse
I've no 4g connection in my data plan.
With 3g there's no problem at all.

Could I boot twrp and restore I backup of Mahdi ROM without issues?

AndroidInsanity said:
Could I boot twrp and restore I backup of Mahdi ROM without issues?
Click to expand...
Click to collapse
I've restored today the backup of Cyano 11 with no problem at all.

Anyone having issues with GPS lock for the stock weather app? When I try to get my location it stays at searching forever then eventually tells me it can't find my location, yet when I use the Chronic widget it finds my location easily.
Any patches to apply for the Colors weather? Would love to use it and some of the awesome animated lockscreens as well.

Manual OTA Update process step-by-step (Stock/Rooted/Xposed)

For stock rooted/TWRP users, this is a step-by-step process of manually updating your Moto involving flashing stock firmware, updating, and restoring TWRP, root, and apps afterwards.
Benefits:
**It's really simple- once you get familiar with this process, you can do it fairly quickly.
**Take the time to read through and get everything set up and you'll be set for future updates.
**No begging the internet for flashable zips.
Preface:
So my situation is i'm running stock, bootloader unlocked, rooted, and xposed on my US XT1540 2GB Moto G. I went through the process this morning of updating to the new 23.46.4 update. Thought I'd share what I did for anyone out there wanting to update with questions ; hopefully some can be answered here. I'm familiar with flashing firmware files from my previous Moto X's '13 & '14 so trust me it's not a big deal to flash back stock firmware to update. This process should be applicable to any variant of the Moto G and and to any future updates as well, not just the one mentioned here as of 09/19/15. Just be mindful of your phone's version and use the appropriate firmware.
1) BACKUP
First, make sure everything worth keeping is on your microSD. Flashing stock firmware will wipe your phones internal memory so pictures, music, downloads, SMS, etc need to migrate. Also make sure you have SuperSU and Xposed on your microSD for re-installation. This might be obvious for some and you might have everything going to your microSD (sdcard1, EXTsdcard) already, but one thing you might miss is Titanium Backup...
Save apps in Titanium to microSD: Menu>Preferences>Backup folder location>Click to change>Ext. SD card>Create a new folder>Use current folder
Nandroid in TWRP to microSD: toward the bottom click on "Storage: Internal storage" and choose "Micro SDcard"
If you're super smart, after making that backup you'll copy that to your pc.
2) DOWNLOADS
Get the most recent firmware for your device from lost101's firmware thread (thank him threads like this are so helpful)- http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
Download and install the drivers for you phone, I believe the generic android driver will work but you can also get them from Motorola Device Manager: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Download mini-sdk.zip, attached to the the bottom of this post. Useful light weight sdk containing adb & fastboot which should cover all your flashing needs. If you're not developing apps, full blown android sdk is bloatware
3) SETTING UP ADB/FASTBOOT
Enable USB debugging in Developer options
Extract mini-sdk.zip to a folder. Extract and add the contents of your firmware to that folder.
Open a cmd prompt on the mini-sdk folder (shift + right click, "Open Command Window Here")
Let's verify that adb sees the device:
Code:
adb devices
Should see "XXserial#XX device". If you get "offline", be sure to check your phone for the adb authorization dialog.
We're ready to flash firmware so reboot into fastboot:
Code:
adb reboot bootloader
4) STOCK FIRMWARE INSTALLATION
Once phone is in fastboot, enter the following commands in the cmd prompt (open on the mini-sdk folder containing the firmware files) one at a time. Let the current flash command finish before entering the next, especially at the img_sparsechunck steps because they take a 10-15 sec each. Also make sure all of the filenames match what you have; substitute accordingly.
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
5) UPDATE
When you reboot, if you don't get prompted for update check for it- About phone>System updates
Download & install update
When update is finished and phone boots back up, enable Android debugging in developer options.
6) FLASH BACK TWRP/ROOT/XPOSED
Place TWRP img file in mini-sdk folder. Boot back into fastboot and flash TWRP.
Code:
adb reboot bootloader
Code:
fastboot flash recovery twrp-osprey-2.8.7-test1.img
Vol up/down in bootloader to boot recovery.
Once in recovery flash Supersu & xposed (optional of course) from your microSD and reboot.
Install Titanium from play store, go back into preferences and point to backup folder on the microSD and restore apps.
When xposed and modules are reinstalled through Titanium, you will need to reboot to enable. After that you'll need to tweak your preferences in system options like notifications or display, but any settings in modules (like gravity box) will be restored as long as you backed up app+data in TB. Easier than a custom rom clean flash in that aspect.
So that's it, with that you should be back up and running. Let me know if I missed some steps or if you have questions about the process.
*****
BTW, Installing xposed from scratch for those confused on what files to do what with: http://forum.xda-developers.com/show....php?t=3034811
Flash this one in recovery: xposed-v74-sdk22-arm.zip (or most current)
Install this apk after you reboot: XposedInstaller_3.0_alpha4.apk (or most current)

Please Delete

agleroy said:
Thanks for the guide. Still gonna wait for a flashable zip though.
Click to expand...
Click to collapse
You're better than that. Trying to empower you here...

Please Delete

Hey, could you use normal/dark colors? Reading light yellow and blue is difficult, even when highlighting it with a cursor. Thanks!

a.cid said:
Hey, could you use normal/dark colors? Reading light yellow and blue is difficult, even when highlighting it with a cursor. Thanks!
Click to expand...
Click to collapse
I took all the color out and tweaked it a bit. I was using the dark theme and everything looked pretty good, but when I switched to the light theme... yeah annoying.

I'm still trying to decide if I want/need to root, and/or install a custom ROM on this phone. I have always done so on past phones, but this phone runs so well I don't want to mess it up, and I'm not sure the few features I'm missing warrant messing with things.
Thank you the tutorial though. I will certainly keep it for reference.
Sent from my MotoG3 using XDA Free mobile app

Why does every single guide say to erase the userdata partition??? This is totally unnecessary. Instead, boot into twrp and wipe your userdata. The difference is in your internal storage. If you follow the guide you wipe your internal storage in the very last command. My way, you just do a factory reset on the data partition which doesn't wipe the storage
Also, flashing stock recovery is an unnecessary step when it's being immediately replaced by twrp again.
Selmak said:
I'm still trying to decide if I want/need to root, and/or install a custom ROM on this phone. I have always done so on past phones, but this phone runs so well I don't want to mess it up, and I'm not sure the few features I'm missing warrant messing with things.
Thank you the tutorial though. I will certainly keep it for reference.
Sent from my MotoG3 using XDA Free mobile app
Click to expand...
Click to collapse
This isn't a custom rom...it's the official motorola firmware update

Thanks for this guide , it's good to know, but I would have to wait for a flasheable UPDATE.zip because my phone's configuration (XT1543, dual sim, 16gb storage, 1gb ram) doesn't have a stock firmware download link in the main thread... and also I don't want to reinstall my apps , haha.

If it works like the other 2 generations of moto g, and at least with the first moto x (all from my personal experience) just skip the erase userdata part and you'll keep your personnal data.
Ota update will go smoothly, no need to restore anything afterwards except root and recovery, indeed.
A backup is always a good thing, sure just in case, but i never used mine on all the ota's I installed on those 3 phones (moto g 2013 16gb, moto g 2014 and moto x 2013)
I don't own a moto g 2015 but my gf does, a 16gb/2gb ram one, she just got it so she installed the update before rooting. If nobody tries it before I'll try it with the next update .

cannot access filehost to get xt1541 5.1.1 any alternative link?

after I updated to 6.0 my computer is not recognising the device? any solutions?

Please add "fastboot flash system system.img_sparsechunk.6" to the top post. This could prevent idiots from sitting in a boot loop for an hour, while they try furiously to find a way out, an error in the download, revert to a previous firmware... Yeah, that was stressful.

Is this the same for the XT1548 virgin mobile 1G of ram and 8G of memory. I understand that it's probably not the same file I just don't really want to wait for the flashable .Zip. But I also don't want to mess up my only device as of now.

Hey i need help....my xt1550 is unlocked and running on stock 6.0 right now......i have installed custom ROMs and rooted the device before.....but now its unrooted and running stock but iam still not able to recieve ota updates.......why?

csumanth16 said:
Hey i need help....my xt1550 is unlocked and running on stock 6.0 right now......i have installed custom ROMs and rooted the device before.....but now its unrooted and running stock but iam still not able to recieve ota updates.......why?
Click to expand...
Click to collapse
If you have stock recovery and an update touched /boot and /system partition, you can take an OTA update. If you have TWRP, root, or other modification in the mentioned areas you cannot take an OTA update.
Having an unlocked bootloader only is not relevant.

What if you unrooted, a rooted stock recovery device, is it safe to take an OTA?
acejavelin said:
If you have stock recovery and an update touched /boot and /system partition, you can take an OTA update. If you have TWRP, root, or other modification in the mentioned areas you cannot take an OTA update.
Having an unlocked bootloader only is not relevant.
Click to expand...
Click to collapse

MrTooPhone said:
What if you unrooted, a rooted stock recovery device, is it safe to take an OTA?
Click to expand...
Click to collapse
No... If your rooted the /boot partition has been modified.

acejavelin said:
No... If your rooted the /boot partition has been modified.
Click to expand...
Click to collapse
And does it remain notably changed even after going through a full unroot via SuperSU?

MrTooPhone said:
And does it remain notably changed even after going through a full unroot via SuperSU?
Click to expand...
Click to collapse
No, doing a full unroot will return the original /boot partition, but be aware this will not undo any changes you made to /system with root access (such as debloating or Xposed modules), and even if you undo those changes, the Android system has already marked the /system partition as tampered so a check will fail.

Help with soft brick

Hi guys,
I got the ASUS Zenfone 3 Zoom and started playing with it. Unfortunately I managed to soft brick it and somehow I can't go back to stock. Here are all the things I did. I would be happy to get any ideas what to try next:
1. unlocked the bootloader - using asus's official unlock tool
2. flashed twrp recovery - twrp-3.2.1-0-Z01H-20180304.img, using:
adb reboot bootloader
fastboot flash recovery twrp.img
3. updated asus's firmware to the latest official one:
copying UL-Z01H-WW-71.60.139.30.zip onto internal memory
android detects the update and applying it using android
4. Enabling lock pattern at boot (from android settings). Correct pattern required even when booting into recovery
5. Installing supersu via twrp:
adb reboot recovery
installing supersu
wiping caches (the cache partition cannot be wiped)
6. SuperSu working (tested via android)
7. Reading about Magisk. Trying to install magisk via twrp. Magisk's installer complained that the system is not vanilla (due to SuperSu modifications). Have to uninstall SuperSu to return to previous state.
8. Tried uninstalling SuperSu from the program itself (in android). The uninstaller got stuck. The phone become unresponsive and had to reboot.
9. Found a script packaged as an executable zip (to be installed via twrp) that will uninstall SuperSu and return system to pristine state (SuperSu makes a backup of the files it changes before installation) - UPDATE-unSU-signed.zip. Uninstallation worked.
10. Magisk installation still complained about the bootloader. Then things started to go wrong. I unpacked the latest firware UL-Z01H-WW-71.60.139.30.zip, took out boot.img and tried to flash just the bootloader
fastboot flash boot boot.img
11. Upon reboot the phone got stuck at the ASUS logo. Reboot into recovery and into fastboot still works (soft brick). Still shows unlock pattern at boot.
12. I tried flashing the original firmware using TWRP (install a zip). However the installation threw some errors. Unsuccessful.
13. I've tried flashing the system.img from the original firware using fastboot but still it's stuck at the ASUS logo at boot.
fastboot flash system system.img
Here I am stuck. I've read that TWRP cannot install properly the ASUS official firmware but if you flash the original recovery, it can probably flash it properly. Another thing that I think might explain why I cannot get out of the soft brick is that I've enabled the lock pattern at boot, which effectively encrypted some parts of the phone and I have a strong feeling this interferes with the boot process. I will look for a script/installable zip (via twrp) that can remove the lock.
I really need ideas/suggestions before I make something that will turn my phone into a hard brick. Thanks.

What you need to do is flash stock MM recovery from bootloader using "fastboot flash recovery recovery.img"
Since it came with MM preloaded you'll have to install the ROM using stock recovery via adb. It'll take a while, but after that you should upgrade to the latest MM update.
After that, update to any Nougat patch update you wish to receive, because I still haven't figured out yet how to apply them all with @shakalaca's recovery images.
Once you're done, you can install twrp again and flash magisk.
Good luck and hope this helped you

Thanks
+)KEV1N(+ said:
What you need to do is flash stock MM recovery from bootloader using "fastboot flash recovery recovery.img"
Since it came with MM preloaded you'll have to install the ROM using stock recovery via adb. It'll take a while, but after that you should upgrade to the latest MM update.
After that, update to any Nougat patch update you wish to receive, because I still haven't figured out yet how to apply them all with @shakalaca's recovery images.
Once you're done, you can install twrp again and flash magisk.
Good luck and hope this helped you
Click to expand...
Click to collapse
Thanks,
I tried to find a stock recovery images but unsuccessful. Can you tell me where to get it from?

Here's a link to Shakalaca's recovery images.
In the Old folder you'll find MM stock recoveries.
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w!I89QgZpK
Flash 11.40.86.75 recovery
Boot into recovery
Flash 11.40.86.75 stock rom via adb (it'll take a while)
Once it's done, boot into Android.
Download your respective region's latest MM rom.
Send it to your micro sd.
Install it once Android detects the update file.
(It won't work with custom recovery. I tried every recovery Shakalaca has and only those two seem to work)
Once on the latest MM rom install any nougat patch update you wish to apply, because once you have a nougat rom, you can't boot stock recovery. (As far as my testings went)
So if I were you, I'd go for any update after the zenui 4.0 update since it's a bit better looking imo.
After that final update you can flash TWRP to root your phone. I prefer using magisk, since it doesn't modify the system files.
All you need to do is flash magisk and that's it. No need for SuperSU or anything else. And by any means, do NOT wipe your cache partition once you flash TWRP, otherwise you'll get stuck on the Asus logo during boot.
If you wish to retain the "certified" status in google play store's device certification, do NOT go into the play store before installing magisk. Also, don't delete play store data, otherwise you'll lose your previous purchases.
This post was longer than I initially thought it'd be, but I guess this sums it up pretty well.
Good luck

+)KEV1N(+ said:
Here's a link to Shakalaca's recovery images.
In the Old folder you'll find MM stock recoveries.
-- [link] removed due to XDA regulations
Flash 11.40.86.75 recovery
Boot into recovery
Flash 11.40.86.75 stock rom via adb (it'll take a while)
Once it's done, boot into Android.
Download your respective region's latest MM rom.
Send it to your micro sd.
Install it once Android detects the update file.
(It won't work with custom recovery. I tried every recovery Shakalaca has and only those two seem to work)
Once on the latest MM rom install any nougat patch update you wish to apply, because once you have a nougat rom, you can't boot stock recovery. (As far as my testings went)
So if I were you, I'd go for any update after the zenui 4.0 update since it's a bit better looking imo.
After that final update you can flash TWRP to root your phone. I prefer using magisk, since it doesn't modify the system files.
All you need to do is flash magisk and that's it. No need for SuperSU or anything else. And by any means, do NOT wipe your cache partition once you flash TWRP, otherwise you'll get stuck on the Asus logo during boot.
If you wish to retain the "certified" status in google play store's device certification, do NOT go into the play store before installing magisk. Also, don't delete play store data, otherwise you'll lose your previous purchases.
This post was longer than I initially thought it'd be, but I guess this sums it up pretty well.
Good luck
Click to expand...
Click to collapse
Thanks, I managed to flash 11.40.86.75 and stock ROM using your instructions. I will look now into updating and applying magisk. Just a final question. You mentioned to install Nougat patch update and not a full firmware, but my phone came preloaded with Nougat. Will this be a problem? I installed stock 71.60.139.30 and it worked fine (i was able to boot into twrp).

mollonado said:
Thanks, I managed to flash 11.40.86.75 and stock ROM using your instructions. I will look now into updating and applying magisk. Just a final question. You mentioned to install Nougat patch update and not a full firmware, but my phone came preloaded with Nougat. Will this be a problem? I installed stock 71.60.139.30 and it worked fine (i was able to boot into twrp).
Click to expand...
Click to collapse
Sorry I misread your comment. I'm updating to the latest ROM and installing TWRP. Thanks for the help.

mollonado said:
Sorry I misread your comment. I'm updating to the latest ROM and installing TWRP. Thanks for the help.
Click to expand...
Click to collapse
Glad to help!
---------- Post added at 01:33 PM ---------- Previous post was at 01:30 PM ----------
mollonado said:
Thanks, I managed to flash 11.40.86.75 and stock ROM using your instructions. I will look now into updating and applying magisk. Just a final question. You mentioned to install Nougat patch update and not a full firmware, but my phone came preloaded with Nougat. Will this be a problem? I installed stock 71.60.139.30 and it worked fine (i was able to boot into twrp).
Click to expand...
Click to collapse
It came preloaded with Nougat? Interesting.

+)KEV1N(+ said:
Glad to help!
---------- Post added at 01:33 PM ---------- Previous post was at 01:30 PM ----------
It came preloaded with Nougat? Interesting.
Click to expand...
Click to collapse
Hi I managed to flash stock ROM - 71.60.139.30, but after that I can't flash twrp - twrp-3.2.1-0-Z01H-20180304.img. I tried with:
adb reboot bootloader
fastboot flash recovery twrp.img
but when I try to boot into recovery with:
adb reboot recovery
it goes into the stock recovery. Is there something I missed? Do I need to downgrade to flash TWRP?

mollonado said:
Hi I managed to flash stock ROM - 71.60.139.30, but after that I can't flash twrp - twrp-3.2.1-0-Z01H-20180304.img. I tried with:
adb reboot bootloader
fastboot flash recovery twrp.img
but when I try to boot into recovery with:
adb reboot recovery
it goes into the stock recovery. Is there something I missed? Do I need to downgrade to flash TWRP?
Click to expand...
Click to collapse
Quick question: which of these warnings do you get when you boot?
https://www.androidauthority.com/go...rrupted-and-modified-android-software-629180/
Also, did you try power cycling to get it to boot?
And since the version number made such a large jump, I believe they must have changed something internally with the latest update and that it's probably going to be one of the last Nougat updates before Oreo (which was delayed until June).
I still need to update to that version to check it out, but I might reset soon since I was waiting for Oreo to reset.

+)KEV1N(+ said:
Quick question: which of these warnings do you get when you boot?
https://www.androidauthority.com/go...rrupted-and-modified-android-software-629180/
Also, did you try power cycling to get it to boot?
And since the version number made such a large jump, I believe they must have changed something internally with the latest update and that it's probably going to be one of the last Nougat updates before Oreo (which was delayed until June).
I still need to update to that version to check it out, but I might reset soon since I was waiting for Oreo to reset.
Click to expand...
Click to collapse
I have the Orange warning. It looks a bit different but the wording is the same. Yes, i tried powercycling and still I boot into the stock recovery. What can I do now? Is it possible to downgrade? I am not sure if I boot into stock recovery if it will let me flash an older stock ROM.

mollonado said:
I have the Orange warning. It looks a bit different but the wording is the same. Yes, i tried powercycling and still I boot into the stock recovery. What can I do now? Is it possible to downgrade? I am not sure if I boot into stock recovery if it will let me flash an older stock ROM.
Click to expand...
Click to collapse
I read here - https://android.gadgethacks.com/how-to/twrp-101-install-best-custom-recovery-for-android-0179547/
that once you flash twrp Android upon next reboot might overwrite it with the stock recovery. Is that possible?

mollonado said:
I read here - https://android.gadgethacks.com/how-to/twrp-101-install-best-custom-recovery-for-android-0179547/
that once you flash twrp Android upon next reboot might overwrite it with the stock recovery. Is that possible?
Click to expand...
Click to collapse
So, how did you flash TWRP exactly? Using that guide? Or flashed through bootloader?
And to answer your question: yes, it happens sometimes.

+)KEV1N(+ said:
So, how did you flash TWRP exactly? Using that guide? Or flashed through bootloader?
And to answer your question: yes, it happens sometimes.
Click to expand...
Click to collapse
Hi, I managed to get around it by directly booting into TWRP from fastboot. Yes, apparently unless I flash some TWRP files to the system partition upon next reboot, the recovery will return to stock. Anyway, I managed to install Magisk and Exposed framework and have been poking with those two for the last couple of days.
The youtube vanced app is great, but I found something that worries me. I can't login to facebook/twitter. I checked and the reason is I can't connect to the facebook.com or twitter.com https sites (even over chrome). I think either:
- I've installed some module which is messing with that
- my rooted phone is hacked
I've installed a module that is meant as ad blocker, that updates the hosts file. However I removed all modules and the problem remains. I really don't wanna start all over again just to check. And even if I reflash and it works, I will not know what caused it and how to fix it myself next time. Do you have any ideas on how to figure out what the problem is?
Regards,

mollonado said:
Hi, I managed to get around it by directly booting into TWRP from fastboot. Yes, apparently unless I flash some TWRP files to the system partition upon next reboot, the recovery will return to stock. Anyway, I managed to install Magisk and Exposed framework and have been poking with those two for the last couple of days.
The youtube vanced app is great, but I found something that worries me. I can't login to facebook/twitter. I checked and the reason is I can't connect to the facebook.com or twitter.com https sites (even over chrome). I think either:
- I've installed some module which is messing with that
- my rooted phone is hacked
I've installed a module that is meant as ad blocker, that updates the hosts file. However I removed all modules and the problem remains. I really don't wanna start all over again just to check. And even if I reflash and it works, I will not know what caused it and how to fix it myself next time. Do you have any ideas on how to figure out what the problem is?
Regards,
Click to expand...
Click to collapse
First off, my apologies for this late reply (Been superbusy with school and internship assignments)
Secondly, and that is why I only use magisk. Because once you mess with the host file, depending on what module you install, it can range from tripping safetynet to bootlooping.
So quick question, is it still in this state right now since 9 days ago?
Greetings,
Kevin

+)KEV1N(+ said:
Here's a link to Shakalaca's recovery images.
In the Old folder you'll find MM stock recoveries.
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w!I89QgZpK
Flash 11.40.86.75 recovery
Boot into recovery
Flash 11.40.86.75 stock rom via adb (it'll take a while)
Once it's done, boot into Android.
Download your respective region's latest MM rom.
Send it to your micro sd.
Install it once Android detects the update file.
(It won't work with custom recovery. I tried every recovery Shakalaca has and only those two seem to work)
Once on the latest MM rom install any nougat patch update you wish to apply, because once you have a nougat rom, you can't boot stock recovery. (As far as my testings went)
So if I were you, I'd go for any update after the zenui 4.0 update since it's a bit better looking imo.
After that final update you can flash TWRP to root your phone. I prefer using magisk, since it doesn't modify the system files.
All you need to do is flash magisk and that's it. No need for SuperSU or anything else. And by any means, do NOT wipe your cache partition once you flash TWRP, otherwise you'll get stuck on the Asus logo during boot.
If you wish to retain the "certified" status in google play store's device certification, do NOT go into the play store before installing magisk. Also, don't delete play store data, otherwise you'll lose your previous purchases.
This post was longer than I initially thought it'd be, but I guess this sums it up pretty well.
Good luck
Click to expand...
Click to collapse
I made a mistake and could not install recovery stock, I followed what you wrote in the beginning install MM recovery and so I did a hard reset and I was able to install the most current recovery stock and installed ROM Oreo, Thanks. Sorry, I'm on google translator.

Patched Boot from latest OTA 10.0.3.0

Hello everyone
Someone in the russian forum (4pda) shared this patched boot from january ota
I flashed it and the device booted correctly without facing any problem, now magisk works again
Link to download : https://mega.nz/#!R5NAgQKJ!yfm886jSAA_x1raUzxRlq-t53AFjaFvU7Q_AH-fXRlY

Tested and it works. Thanks

help
guyz my adb cant load the patched boot img even when it is in the same folder any help plss

veddeomi said:
guyz my adb cant load the patched boot img even when it is in the same folder any help plss
Click to expand...
Click to collapse
Put the patched boot in adb folder
Reboot your phone into fastboot mode
Then open cmd : fastboot flash boot patched_boot_3.0.img

you can save ur time by using the below toolkit
https://forum.xda-developers.com/mi-a2/development/tool-mi-a2-xtrem-toolkit-t3879660
and just download Magisk from XDA and use the tool to install it using the ADB Sideload.
that is what i did and worked perfectly on Pie after Jan Update.

Does it work with v10.2 ?
Or i must update to v10.3 to flash this patch ?

beny ms said:
Does it work with v10.2 ?
Or i must update to v10.3 to flash this patch ?
Click to expand...
Click to collapse
U have to update first

Abrilabr said:
U have to update first
Click to expand...
Click to collapse
Okay ,thanks mate

i flashed it successfully but i get bootloop. this patch not working my phone

Oline1032 said:
i flashed it successfully but i get bootloop. this patch not working my phone
Click to expand...
Click to collapse
You should unlock your phone's bootloader first
And update to 10.0.3.0

medkim said:
You should unlock your phone's bootloader first
And update to 10.0.3.0
Click to expand...
Click to collapse
dude bootloader is unlocked

Oline1032 said:
dude bootloader is unlocked
Click to expand...
Click to collapse
are you in january patch ?
it's weird, your phone should boot normally, maybe you missed something

i was on 10.0.2.0.PDIMIFJ with unlocked bootloader and patched boot.img. when OTA update is avaiable, i restored boot.img using Magisk and installed the update, then patched boot.img again using Magisk.
After reboot, phone keeps restarting while showing Android One screen.
Then I flashed this patched 10.0.3.0, but phone is stuck at Android One screen (there should be moving color bar)
Now I'm trying to downgrade to 10.0.2.0.PDIMIFJ using MiFlash without erasing user data
Edit: still boot loop at Android One screen after flashing 10.0.2.0.PDIMIFJ without erasing user data. Phone shows the Android recovery screen with error message "can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device"

HRSE said:
i was on 10.0.2.0.PDIMIFJ with unlocked bootloader and patched boot.img. when OTA update is avaiable, i restored boot.img using Magisk and installed the update, then patched boot.img again using Magisk.
After reboot, phone keeps restarting while showing Android One screen.
Then I flashed this patched 10.0.3.0, but phone is stuck at Android One screen (there should be moving color bar)
Now I'm trying to downgrade to 10.0.2.0.PDIMIFJ using MiFlash without erasing user data
Click to expand...
Click to collapse
I have encountered the same problem.
It seems like there is something wrong with the encryption of the phone because I need to format the userdata partition to stop the bootloop.

Fulva said:
I have encountered the same problem.
It seems like there is something wrong with the encryption of the phone because I need to format the userdata partition to stop the bootloop.
Click to expand...
Click to collapse
Good for you that you are still on 10.0.3.0
Now my phone is wiped, and back to 10.0.2.0. I gained nothing and lost too much.

HRSE said:
i was on 10.0.2.0.PDIMIFJ... Edit: still boot loop at Android One screen after flashing 10.0.2.0.PDIMIFJ...
Click to expand...
Click to collapse
My jasmine 6/128 was on 10.0.2.0.PDIMIFJ, unlocked, rooted - Magisk with Modules, /system partition changed, automatic .Updates disabled
Thus, checking for January OTA and seeing that it is ready, I made these steps:
1. downloaded stock 10.0.2.0.PDIMIFJ http://en.miui.com/download-353.html (actually, I made it much earlier);
2. flashed it in fastboot preserving /data (there is "flash_all_except_data.bat" in unpacked ROM directory);
3. rebooted, downloaded OTA 10.0.3.0, installed OTA, rebooted without bootloop;
4. used phone for a while (root gone, all user applications, except for 1 rather specific, working - including Nova, phone calls, SMS, etc, OK);
5. Took patched boot image from 4pda, and booted it into phone in fastboot ("fastboot boot pached_boot.img"); NOTE: not flashed, but booted for safety!
6, As phone was working OK with booted patch, I started Magisk and "installed" it; thus Magisk patched my stock 10.0.3.0 boot in phone, and saved original stock in /data partition.
7. after reboot I had everything restored - Magisk modules and su, root permitions for applications, etc.
P.S. Seems like 10.0.3.0 PDIMIXM OTA is withdrawn by Xiaomi due to numerous bootloops in stock phones.
So if you already updated to this OTA, use these attachments at your own risk, or better wait for 10.0.4.0

Aerobatic said:
My jasmine 6/128 was on 10.0.2.0.PDIMIFJ, unlocked, rooted - Magisk with Modules, /system partition changed, automatic .Updates disabled
Thus, checking for January OTA and seeing that it is ready, I made these steps:
1. downloaded stock 10.0.2.0.PDIMIFJ http://en.miui.com/download-353.html (actually, I made it much earlier);
2. flashed it in fastboot preserving /data (there is "flash_all_except_data.bat" in unpacked ROM directory);
3. rebooted, downloaded OTA 10.0.3.0, installed OTA, rebooted without bootloop;
4. used phone for a while (root gone, all user applications, except for 1 rather specific, working - including Nova, phone calls, SMS, etc, OK);
5. Took patched boot image from 4pda, and booted it into phone in fastboot ("fastboot boot pached_boot.img"); NOTE: not flashed, but booted for safety!
6, As phone was working OK with booted patch, I started Magisk and "installed" it; thus Magisk patched my stock 10.0.3.0 boot in phone, and saved original stock in /data partition.
7. after reboot I had everything restored - Magisk modules and su, root permitions for applications, etc.
Click to expand...
Click to collapse
somehow my phone doesn't show the january OTA update anymore (it was still there a few hours ago!)

Hey guys if i root using patched boot image will i still be able to install updates?

one08 said:
Hey guys if i root using patched boot image will i still be able to install updates?
Click to expand...
Click to collapse
No you should restore stock boot first

one08 said:
Hey guys if i root using patched boot image will i still be able to install updates?
Click to expand...
Click to collapse
Yes you can receive updates, but only if you did not made any changes to system files !

Razer 2 Global MR2 Sept 2019 Release Magisk Root & Arter97 Kernel / TWRP ?

Can someone confirm these steps will work..
MR1 that has Arter97 Kernel with TWRP and is rooted with Magisks
----------------------------------------------------------------------------------
1. Flash back to factory P-MR1-RC003-RZR-190305.3110 using instructions on Razer Develope Portal
https://developer.razer.com/razer-phone-dev-tools/factory-images/
2. Lock the Bootloader Critical Partitions
command: fastboot flashing lock_critical
3. Locking the Bootloader
command: fastboot flashing lock
4. Reboot phone and let it setup
5. Enable OEM locking
6. Wait/Take OTA for MR2
Re-Root MR2
----------------
1. FLash MR2 rooted image via FASTBOOT
https://forum.xda-developers.com/showpost.php?p=80553681&postcount=57
2. Flash Arter97 Kernel & TWRP via FASTBOOT
3. Reboot
??????????????????????????????????
Is the above the best way? Can we just flash the factory MR1 bootloader and recovery and take the OTA, then install Arter97/TWRP and then install Magisks?
Please advise...
Thanks,
RJR

I'm in the same boat, waiting for confirmation before installing September update.
I need root, and if we can't root the new September release, then I rather stay in the current version.

1. install factory images
2. update
3. flash arter and root
if you notice any bootloop i recommend u use gsi because i had once bootloop for no reason on stock but gsi is just fine

RKBD said:
1. install factory images
2. update
3. flash arter and root
if you notice any bootloop i recommend u use gsi because i had once bootloop for no reason on stock but gsi is just fine
Click to expand...
Click to collapse
Sorry but I have seen in another thread that to get root on latest September update, we had to flash the modded boot provided. So if we root after arter, we will loose arter?
Sorry if it's a noob question but rooting last update isn't clear to me.

This Works I've done it on my razor phone 2 Global
This does work
rrusek said:
Can someone confirm these steps will work..
MR1 that has Arter97 Kernel with TWRP and is rooted with Magisks
----------------------------------------------------------------------------------
1. Flash back to factory P-MR1-RC003-RZR-190305.3110 using instructions on Razer Develope Portal
https://developer.razer.com/razer-phone-dev-tools/factory-images/
2. Lock the Bootloader Critical Partitions
command: fastboot flashing lock_critical
3. Locking the Bootloader
command: fastboot flashing lock
4. Reboot phone and let it setup
5. Enable OEM locking
6. Wait/Take OTA for MR2
Re-Root MR2
----------------
1. FLash MR2 rooted image via FASTBOOT
https://forum.xda-developers.com/showpost.php?p=80553681&postcount=57
2. Flash Arter97 Kernel & TWRP via FASTBOOT
3. Reboot
??????????????????????????????????
Is the above the best way? Can we just flash the factory MR1 bootloader and recovery and take the OTA, then install Arter97/TWRP and then install Magisks?
Please advise...
Thanks,
RJR
Click to expand...
Click to collapse

macjunkie said:
This does work
Click to expand...
Click to collapse
OK thanks I'll do that!
But the download link doesn't work anymore...

http://arter97.com/browse/aura/kernel/ latest 12r kernel won't bootloop so.
1. flash untouched RP2 mr1 firmware (latest for now in razer factory images)
2. update it to mr2
3. fastboot flash boot [arter r12 kernel]
4. then root or whatever you want

RKBD said:
http://arter97.com/browse/aura/kernel/ latest 12r kernel won't bootloop so.
1. flash untouched RP2 mr1 firmware (latest for now in razer factory images)
2. update it to mr2
3. fastboot flash boot [arter r12 kernel]
4. then root or whatever you want
Click to expand...
Click to collapse
Root before flashing GSI or after?

EMJI79 said:
Root before flashing GSI or after?
Click to expand...
Click to collapse
after.
it doesn't matter tho because it's on boot partition not system. but you won't need to reboot twice if you install it after flashing gsi.

RKBD said:
http://arter97.com/browse/aura/kernel/ latest 12r kernel won't bootloop so.
1. flash untouched RP2 mr1 firmware (latest for now in razer factory images)
2. update it to mr2
3. fastboot flash boot [arter r12 kernel]
4. then root or whatever you want
Click to expand...
Click to collapse
Well bad luck for me: it says device is corrupt after flashing mr1.
Maybe it has to do with I didn't unlock critical Bootloader. Will try.

EMJI79 said:
Well bad luck for me: it says device is corrupt after flashing mr1.
Click to expand...
Click to collapse
don't worry it's because you are on A/B device and you installed it on B partition instead of A
fastboot set_active a
then flash mr1 again

RKBD said:
don't worry it's because you are on A/B device and you installed it on B partition instead of A
fastboot set_active a
then flash mr1 again
Click to expand...
Click to collapse
Off topic: you said you wanted to have gestures, there's even better than Q gestures, with the app fluid navigation gestures you can set gestures to whatever you want. For example you could get close to Oxygen OS gestures which are great.

EMJI79 said:
Off topic: you said you wanted to have gestures, there's even better than Q gestures, with the app fluid navigation gestures you can set gestures to whatever you want. For example you could get close to Oxygen OS gestures which are great.
Click to expand...
Click to collapse
i know that app. but they're not that smooth and integrated with system

so no flawless alternative rom here?
Resurection get some issue with bluetooth audio(car audio HFP), and some trouble with fingerprint (works some times)
and havoc 2.9 GSI same issue
i don't know, leave original one?
now i've rolled back the MR1, but get persistent error upgrading MR1 (all restored to original one, boot and system )

igiolo said:
so no flawless alternative rom here?
Resurection get some issue with bluetooth audio(car audio HFP), and some trouble with fingerprint (works some times)
and havoc 2.9 GSI same issue
i don't know, leave original one?
now i've rolled back the MR1, but get persistent error upgrading MR1 (all restored to original one, boot and system )
Click to expand...
Click to collapse
Nope, no solid alternative. Unfortunately, development for the RP2 (and most Android phones these days) has been almost non-existent. Our options are either stay stock, or use one of the GSI's that all have issues of various kinds with our phone.

Hey everyone,
Apologies on the redundancy - but for someone who just scored this phone from Razer for 299 and took the MR2 update the minute it got on wifi, would these steps work to just get root/magisk going?
Enable OEM unlock
reboot to the bootloader
use fastboot command to unlock bootloader
flash mr2 rooted image via fastboot
flash arter97 and twrp via fastboot
reboot
profit?
I'm just looking to get root/magisk, no ROMS or anything.
Thanks all

shokxdauser said:
Hey everyone,
Apologies on the redundancy - but for someone who just scored this phone from Razer for 299 and took the MR2 update the minute it got on wifi, would these steps work to just get root/magisk going?
Enable OEM unlock
reboot to the bootloader
use fastboot command to unlock bootloader
flash mr2 rooted image via fastboot
flash arter97 and twrp via fastboot
reboot
profit?
I'm just looking to get root/magisk, no ROMS or anything.
Thanks all
Click to expand...
Click to collapse
1 enable oem unlock
2 reboot to bootloader via power down and click bootloader unlock
3 flash kernel via fastboot (twrp is inside kernel)
4 flash magisk

RKBD said:
1 enable oem unlock
2 reboot to bootloader via power down and click bootloader unlock
3 flash kernel via fastboot (twrp is inside kernel)
4 flash magisk
Click to expand...
Click to collapse
As always, much appreciated.

shokxdauser said:
As always, much appreciated.
Click to expand...
Click to collapse
Hmm. I thought maybe using the fastboot flash boot_a command would help but I am still getting this error when I try to flash the kernel when I try this full command:
fastboot flash boot_a arter97.img
gets me -
error: failed to identify current slot
I'm guessing I missed something obvious..?
---------- Post added at 11:49 PM ---------- Previous post was at 11:23 PM ----------
Just to note from my previous post about the error - failed to identify current slot -
I am able to see the device when I type fastboot devices. Still trying to figure out why it's saying failed to identify current slot..

shokxdauser said:
Hmm. I thought maybe using the fastboot flash boot_a command would help but I am still getting this error when I try to flash the kernel when I try this full command:
fastboot flash boot_a arter97.img
gets me -
error: failed to identify current slot
I'm guessing I missed something obvious..?
---------- Post added at 11:49 PM ---------- Previous post was at 11:23 PM ----------
Just to note from my previous post about the error - failed to identify current slot -
I am able to see the device when I type fastboot devices. Still trying to figure out why it's saying failed to identify current slot..
Click to expand...
Click to collapse
Let us know if you get it. I have this phone coming to me and want only TWRP/Magisk.
Thanks.