Yesterday i bougth my MI A1 and it's a really amazing device, i just want to install the gcam but i don't know if for the May Update the gcam doesn't install, I am using a tool from here in XDA thah allow to install it without root but it just wiped my phone and doesn't install the cam, any sugestion? Should I install it with root?
Sorry for my bad english
Are you able to read and do just a little research that doesn't take as much as 5 minutes? There is something written in big red letters right at the top of that thread, you should read it before making new thread. Flash ROM with April Security patch, install Gcam and update to May Security patch.
Don't get me wrong, I don't mean to offend you, but at least do some research before posting a question that is answered million times in last few days, especially in that thread where you found tool for Gcam without root.
MaCls98 said:
Yesterday i bougth my MI A1 and it's a really amazing device, i just want to install the gcam but i don't know if for the May Update the gcam doesn't install, I am using a tool from here in XDA thah allow to install it without root but it just wiped my phone and doesn't install the cam, any sugestion? Should I install it with root?
Sorry for my bad english
Click to expand...
Click to collapse
You can use my tool.
You can enable Camera2 Api without relocking bootloader.
It also pushes TWRP configuration files so that system is mounted read-only to preserve OTAs.
With unlocked bootloader you can receive OTAs normally. (and you can boot temporary TWRP to backup your data)
TOOL
sipollo said:
You can use my tool.
You can enable Camera2 Api without relocking bootloader.
It also pushes TWRP configuration files so that system is mounted read-only to preserve OTAs.
With unlocked bootloader you can receive OTAs normally. (and you can boot temporary TWRP to backup your data)
TOOL
Click to expand...
Click to collapse
hello just opened that download that application and is the same procedure?
TheMartinexX said:
hello just opened that download that application and is the same procedure?
Click to expand...
Click to collapse
First select 0-Install drivers (if not already done).
If you have a locked bootloader:
Select 1 (Phone will reboot to fastboot mode).
Then 2 (If your bootloader is locked) Phone will be rebooted.
Then 3 (phone will boot temporary TWRP mounting system read-only).
When TWRP has booted select option 4: Phone will be rebooted.
Done.
You will have Camera2 Api enabled and bootloader unlocked (OTAs will work fine)
Unlocked bootloader:
If you have already unlocked the bootloader you can choose option 3 (boot TWRP) with phone connected with USB debug ON (no fastboot).
When TWRP has booted select option 4.
Done
WARNING:
Use option 5 (relock bootloader) ONLY IF you are on April firmware (or older) AND you have an unmodified system.
sipollo said:
You can use my tool.
You can enable Camera2 Api without relocking bootloader.
It also pushes TWRP configuration files so that system is mounted read-only to preserve OTAs.
With unlocked bootloader you can receive OTAs normally. (and you can boot temporary TWRP to backup your data)
TOOL
Click to expand...
Click to collapse
Thanks men! It works really great, it was little tricky with the language but nothing than google translate doesn't fix, just one question, with that recovery can i install magisk and the OTAs will still working? Great job with this, thanks
MaCls98 said:
Thanks men! It works really great, it was little tricky with the language but nothing than google translate doesn't fix, just one question, with that recovery can i install magisk and the OTAs will still working? Great job with this, thanks
Click to expand...
Click to collapse
Sorry, I linked ita version...
ENG version
https://1drv.ms/u/s!AnNVEh3KeCSVj9dKhn2Zpx-DRI0Esw
You can install Magisk with that booted recovery but you will have to uninstall it before install OTAs.
Don't mount system read-write and don't alter system files or OTAs will fail.
sipollo said:
First select 0-Install drivers (if not already done).
If you have a locked bootloader:
Select 1 (Phone will reboot to fastboot mode).
Then 2 (If your bootloader is locked) Phone will be rebooted.
Then 3 (phone will boot temporary TWRP mounting system read-only).
When TWRP has booted select option 4: Phone will be rebooted.
Done.
You will have Camera2 Api enabled and bootloader unlocked (OTAs will work fine)
Unlocked bootloader:
If you have already unlocked the bootloader you can choose option 3 (boot TWRP) with phone connected with USB debug ON (no fastboot).
When TWRP has booted select option 4.
Done
WARNING:
Use option 5 (relock bootloader) ONLY IF you are on April firmware (or older) AND you have an unmodified system.
Click to expand...
Click to collapse
Doing these steps would install the gcam or the tool does not come the apk
TheMartinexX said:
Doing these steps would install the gcam or the tool does not come the apk
Click to expand...
Click to collapse
It enables camera2 API, then you can install the apk you want.
Here you can find (almost) all versions.
https://www.celsoazevedo.com/files/android/google-camera/
sipollo said:
It enables camera2 API, then you can install the apk you want.
Here you can find (almost) all versions.
https://www.celsoazevedo.com/files/android/google-camera/
Click to expand...
Click to collapse
what would be the best version for xiaomi mi a1 any recommendation?
TheMartinexX said:
what would be the best version for xiaomi mi a1 any recommendation?
Click to expand...
Click to collapse
https://www.celsoazevedo.com/files/...f/GoogleCamera-Pixel2Mod-Arnova8G2-V7.9.5.apk
HPRG said:
https://www.celsoazevedo.com/files/...f/GoogleCamera-Pixel2Mod-Arnova8G2-V7.9.5.apk
Click to expand...
Click to collapse
One last question I do not have to do option 5 or I have to use it if or if
TheMartinexX said:
One last question I do not have to do option 5 or I have to use it if or if
Click to expand...
Click to collapse
Ad I said you can relock bootloader only if you haven't already installed May update and you haven't modified system partition.
Relocked bootloader
After installing gcam can we relock the bootloader???
Will it wipe data after may security patch???
TheMartinexX said:
what would be the best version for xiaomi mi a1 any recommendation?
Click to expand...
Click to collapse
for me >>> https://www.celsoazevedo.com/files/...f/GoogleCamera-Pixel2Mod-Arnova8G2-V7.9.7.apk
farzeenzack said:
After installing gcam can we relock the bootloader???
Will it wipe data after may security patch???
Click to expand...
Click to collapse
If you relock bootloader data will be wiped after May update.
You can:
downgrade to April (or older) firmware, enable API, relock THEN do OTAs
or
enable API and leave unlocked bootloader (OTA will work)
Question regarding may seruity patch
sipollo said:
You can use my tool.
You can enable Camera2 Api without relocking bootloader.
It also pushes TWRP configuration files so that system is mounted read-only to preserve OTAs.
With unlocked bootloader you can receive OTAs normally. (and you can boot temporary TWRP to backup your data)
So I have read that if i try to install GCam with May security patch, it would wipe away my data. Does this happen through this method?
Click to expand...
Click to collapse
Mruthyu said:
sipollo said:
You can use my tool.
You can enable Camera2 Api without relocking bootloader.
It also pushes TWRP configuration files so that system is mounted read-only to preserve OTAs.
With unlocked bootloader you can receive OTAs normally. (and you can boot temporary TWRP to backup your data)
So I have read that if i try to install GCam with May security patch, it would wipe away my data. Does this happen through this method?
Click to expand...
Click to collapse
If you have a locked bootloader you can't enable Camera2Api without losing data.
If it's already unlocked you can use my tool to enable Camera2Api without locking the bootloader.
Click to expand...
Click to collapse
Please guys I need your help, have been on April security patch for awhile now and have received May security patch but it's not installing. I went on YouTube and found out that if I'm too install may security patch through miflash tool by flashing the ROM I won't be able to install gcam. So i did factory reset on my April security patch, installed gcam through the gcam tool and then tried to update it again, but it's still giving me the same error. So I then downloaded the full April security patch so I could flash it through miflash tool,but I noticed when I open the app on my PC and connect my phone through fastboot it connects, but when I click flash the app says "success" so quick and it force closes, my phone remains on fastboot,nothing happens. Please guys I don't know what to do anymore. Need your help.
chuckychux said:
Please guys I need your help, have been on April security patch for awhile now and have received May security patch but it's not installing. I went on YouTube and found out that if I'm too install may security patch through miflash tool by flashing the ROM I won't be able to install gcam. So i did factory reset on my April security patch, installed gcam through the gcam tool and then tried to update it again, but it's still giving me the same error. So I then downloaded the full April security patch so I could flash it through miflash tool,but I noticed when I open the app on my PC and connect my phone through fastboot it connects, but when I click flash the app says "success" so quick and it force closes, my phone remains on fastboot,nothing happens. Please guys I don't know what to do anymore. Need your help.
Click to expand...
Click to collapse
Probably you have wrong/corrupted adb drivers.
Try reinstalling them or use another version.
Related
This guide is for update within versions if you are rooted, if not, simply download and install de ota or with FF.
If you update to B394 from any version, downloading the last complete packet in update system, it locks the bootloader !!! be advised
If you update to B399 or B401, B402 from B394, downloading the last complete packet in update system, DO NOT LOCK the bootloader !!! good news
My first problem was when I was in B380 and rooted , the b389 ota arrived...then I unroot, put stock recovery and unistalled busybox, but ota failed at 8%
The solution to this :
1 - flash stock recovery from version you have
2 - download the last complete packet in update system , for me 2.41 Gb, not the ota
3 - (optional but useful for future) connect to pc and copy the 3 files downloaded the update in HWOUC to pc
4 - make the normal update in update system
7 - copy supersu 2.82.zip original file or Magisk to SD
8 - Flash last twrp recovery twrp-3.1.1-1-frd , enter in twrp recovery and:
9 - Tick the option "Keep vendor partition mounted" inside OpenKirin in Settings (last option in settings) for me is ticked as default
10 - Make a backup of boot (for future) if you want
11- flash supersu 2.82 original or Magisk
12 - reboot and it's done!!!!!!!!
Update to B394
if you have done all the process and you want now to update to b394, you can uninstall first supersu within options menu saying yes to all questions when uninstalling and without errors or bad uninstallation; then, delete binaries of busybox, flash stock recovery and try to install ota...for me the ota not installed and done with errors.
Then I installed b394 full and locked my bootloader, forcing me to format all because i unlocked the bootloader (remember to activate oem bootloader unlock on and usb depuration on).
After installing the same twrp recovery, I tested the magisk v14 and works perfect, but with an inconvenient, you have to disable the option of magisk manager "magisk hide" to work with fingerprint ,At version 15.3 I didn't see this error.
B394 to B399
Tried the uninstaller of magisk flashed with twrp to unroot and then put the stock recovery and failed, then I flashed stock boot and failed ....finally it worked downloading the last complete packet in update system.Then the habitual, flash twrp recovery, magisk v15.3 from twrp and magisk manager v5.5 in android...and worked perfect
B399 to B401
This time I only unistalled binaries from busybox and flashed stock recovery; then launched Full update (2.41 Gb) without problems.Then flashed twrp, magisk 15.3 from twrp as usual and nothing more...magisk manager detected all ok and I have a rooted device again.
B401 to B402
Simplified the process, now only flash the stock recovery 401 and make the full update packet (2.41Gb). Then flash twrp, enter in twrp, flash magisk 16.0, reboot and that's all. Install busybox script, adaway hosts and done.
Notes:
1 - If the system downloaded automatically the small ota update. you must to try to update with an obvious error, then you can download the full update packet.
1 - the installation of magisk is simple, in twrp flash the magisk.zip , reboot and install magisk manager to control all. This is another app to root and don't need supersu. The advantages to make this is magisk hide, it permits to work with apps that can't work if your phone is rooted.
Wow awsome guide. Thanks alot bro .+1
gopinaidu77 said:
Wow awsome guide. Thanks alot bro .+1
Click to expand...
Click to collapse
happy to help!
9 - Tick the option "Keep vendor partition mounted" inside OpenKirin in Settings (last option in settings) for me is ticked as default
pla can y help for this option
warindo said:
9 - Tick the option "Keep vendor partition mounted" inside OpenKirin in Settings (last option in settings) for me is ticked as default
pla can y help for this option
Click to expand...
Click to collapse
in the options of the twrp, last tab , there's a thick that says this
deadko said:
in the options of the twrp, last tab , there's a thick that says this
Click to expand...
Click to collapse
Bro , y u should mount vendor?
warindo said:
9 - Tick the option "Keep vendor partition mounted" inside OpenKirin in Settings (last option in settings) for me is ticked as default
pla can y help for this option
Click to expand...
Click to collapse
gopinaidu77 said:
Bro , y u should mount vendor?
Click to expand...
Click to collapse
to root correctly with supersu original version
deadko said:
to root correctly with supersu original version
Click to expand...
Click to collapse
But i dont think modifying vendor part is good .
gopinaidu77 said:
But i dont think modifying vendor part is good .
Click to expand...
Click to collapse
I didn't say nothing to modify nothing, I said thick this option on, and in my case, I did nothing because is marked by default.
deadko said:
I did nothing to modify nothing, I said thick this option on, and in my case, I do nothing because is marked by default.
Click to expand...
Click to collapse
Oh ,but i request u to remove that point. Since ticking that mean no sense as it allows to modify vendor part
gopinaidu77 said:
But i dont think modifying vendor part is good .
Click to expand...
Click to collapse
gopinaidu77 said:
Oh ,but i request u to remove that point. Since ticking that mean no sense as it allows to modify vendor part
Click to expand...
Click to collapse
I didn't invent that part myself, is the rooting instructions I read in twrp 3.1.1-1 (you can go to the post I linked, and read it) , and only knows that it works
deadko said:
I didn't invent that part myself, is the rooting instructions I read in twrp 3.1.1-1 (you can go to the post I linked, and read it) , and only knows that it works
Click to expand...
Click to collapse
Ok , thanks though
On point 4 - download complete package - but where? On update app there offer only ota update package not full.
Nortonko said:
On point 4 - download complete package - but where? On update app there offer only ota update package not full.
Click to expand...
Click to collapse
at the tab up to the right in update system
Nortonko said:
On point 4 - download complete package - but where? On update app there offer only ota update package not full.
Click to expand...
Click to collapse
Click on 3 dots on the top right corner . U will see the option.
deadko said:
4 - download the last complete packet in update system , for me 2.41 Gb, not the ota
Click to expand...
Click to collapse
My option is greyed out, what should i do?
Nortonko said:
On point 4 - download complete package - but where? On update app there offer only ota update package not full.
Click to expand...
Click to collapse
fabh2o said:
My option is greyed out, what should i do?
Click to expand...
Click to collapse
the ota is avaliable for you?
deadko said:
the ota is avaliable for you?
Click to expand...
Click to collapse
Yes i'm downloading it right now
Edit: i'm downloading the 2,41 gb update, thanks for the support.
I had B381, TWRP & Root and I just used points from guide - 2.2,3,6,7,8,9,11,12. I had to remove SuperSU in the app - complete unroot option. Flashed stock recovery.img (and recovery2.img) in fastboot mode, which I extracted from my firmware version update.app. Restarted the device and did a full OTA update to B389, hard reset, flashed latest TWRP 3.1.1-1 in fastboot mode, than installed modified SuperSU for EMUI 5.0 from XDA and all is done.
Snowjack said:
I had B381, TWRP & Root and I just used points from guide - 2.2,3,6,7,8,9,11,12. I had to remove SuperSU in the app - complete unroot option. Flashed stock recovery.img (and recovery2.img) in fastboot mode, which I extracted from my firmware version update.app. Restarted the device and did a full OTA update to B389, hard reset, flashed latest TWRP 3.1.1-1 in fastboot mode, than installed modified SuperSU for EMUI 5.0 from XDA and all is done.
Click to expand...
Click to collapse
very large process, but you make a hard reset, and my process is to preserve data and use original supersu not the modified , thanks for info
There are probably already a couple guides up, but I wanted to post about how I went about doing this and have everything working. It may not work for everyone, but for me, it worked the first time.
0: Yep, there is a step zero here. :good: BACKUP YOUR PHONES INTERNAL STORAGE! IT WILL NEED TO BE WIPED FOR THIS TO WORK!
1: Flash factory image of 8.1 WITH the "-w" (wipe) command (LINK HERE)
2: Allow the system to boot. (optional: complete setup wizard and update apps)
3: Connect the phone to a PC and copy the TWRP 3.1.1-1 ZIP installer to internal storage (or download it via browser) (LINK HERE)
4: Download Magisk 14.3 using a PC or the phones browser, to internal storage (LINK HERE)
5: Reboot into bootloader (using the POWER + VOL-DOWN combo)
6: Fastboot BOOT TWRP 3.1.1-1 (LINK HERE)
Code:
fastboot boot twrp-3.1.1-1-fastboot-marlin.img
7: Once TWRP has booted up, flash the TWRP ZIP installer from step 3 (do NOT reboot to the OS yet)
8: Reboot directly to RECOVERY
9: Flash Magisk v14.3 from step 4
10: Reboot to Android and you're done!
Working TWRP and fully working root!
Only issue I'm having so far with TWRP is that MTP doesn't work. I can't transfer files to/from the phone while connected to a PC. That's why the file transfers have to happen while booted into Android. A TWRP update will likely fix this.
Hello, I followed these steps and all is working great, now I have activated fingerprint lock on my device and pin code, TWRP tells me that the pin is wrong when I go in to the recovery ? Any ideas, I did the procedre twice from stock and twrp tells me that the pin is wrong every time
Known issue on 8.1. Twrp is not working properly.
Just don't use pin or pattern at all.
mikaole said:
Known issue on 8.1. Twrp is not working properly.
Just don't use pin or pattern at all.
Click to expand...
Click to collapse
I need security on my phone, I would rather just wait for the TWRP update and/or actual 8.1
kingbri said:
I need security on my phone, I would rather just wait for the TWRP update and/or actual 8.1
Click to expand...
Click to collapse
At the rate TWRP gets updated, you'd have to wait till December for that. And sometime in December, 8.1 Final is supposed to be out.
Not sure if it works, but you could try disabling security, use TWRP for whatever you need, then enable security again when you're done.
So when you say flash with wipe command. You mean flash the flash all with -w tacked on the end?
Mckillagorilla said:
So when you say flash with wipe command. You mean flash the flash all with -w tacked on the end?
Click to expand...
Click to collapse
Yes, in other words: do not edit flash-all.sh.
Mckillagorilla said:
So when you say flash with wipe command. You mean flash the flash all with -w tacked on the end?
Click to expand...
Click to collapse
? No to editing file. The file flash-all.bat already has the -
w command in it. (use Flash-all.sh if you use Apple).
The reason post #1 instructs to wipe with the -w command is because some are used to removing the -w to preserve user data when flashing. For this root solution that won't work.
Born<ICs said:
? No to editing file. The file flash-all.bat already has the -
w command in it. (use Flash-all.sh if you use Apple).
The reason post #1 instructs to wipe with the -w command is because some are used to removing the -w to preserve user data when flashing. For this root solution that won't work.
Click to expand...
Click to collapse
worked perfectly for me ... no errors so far.
Let me rephrase. I wiped the phone, went back to 7.1.2, took 8.1 OTA now I want to root without wiping. Is this possible?
The second try, I hate the scrolling that is within apps. Looks like I might be going back to Nougat.
Scottay5150 said:
Can I root the OTA developer preview after a complete flash/wipe?
Click to expand...
Click to collapse
Yes, I am rooted and on it. Same procedure.
Working for me on Pixel non XL swapped the file for sailfish versions
I forget if I install TWRP to does this wipe the whole device?
TonikJDK said:
Yes, I am rooted and on it. Same procedure.
Click to expand...
Click to collapse
Thanks.
I mention that this method also works on Pixel Sailfish, except that it has to use twrp img and zip for Sailfish.
Any reason why I shouldn't just sideload the zips in TWRP? I did it just to test and things seem to be working so far without wiping the device.
Here's a stupid question- does the bootloader need to be unlocked? I'm carrier locked and want to be rooted with TWRP.
hooks024 said:
Here's a stupid question- does the bootloader need to be unlocked? I'm carrier locked and want to be rooted with TWRP.
Click to expand...
Click to collapse
On the Pixels yes you need to be bootloader unlocked to root.
mikaole said:
Known issue on 8.1. Twrp is not working properly.
Just don't use pin or pattern at all.
Click to expand...
Click to collapse
having same problem (says wrong pin), why do almost all guides that for Pixels you need to set up a pin in order to flash TWRP/root properly? Confused.
eddi0 said:
having same problem (says wrong pin), why do almost all guides that for Pixels you need to set up a pin in order to flash TWRP/root properly? Confused.
Click to expand...
Click to collapse
The phone is encrypted, it needs a PIN to authenticate to the OS to decrypt.
I actually had to factory reset it and NOT use a pin for it to work properly (after factory reset go into settings>security>none for screen lock). I know in the past a pin was required but as the second post states Magisk 14.3 is not playing nice with 8.1 beta.
Now that a new OTA is available, and like many others like myself have rooted the A1 with Magisk, I am looking for a foolproof way to update.
Remembering the last (March) OTA, when a lot of people complained about difficult, I wonder if someone has found a good way.
I remember 2 approaches:
1) follow the flow from here: https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
or
2) uninstall Magisk completely, maybe even re-lock the phone, and start from the beginning as outlined here: https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654
What is your experience or recommendation?
Tiemichael said:
Now that a new OTA is available, and like many others like myself have rooted the A1 with Magisk, I am looking for a foolproof way to update.
Remembering the last (March) OTA, when a lot of people complained about difficult, I wonder if someone has found a good way.
I remember 2 approaches:
1) follow the flow from here: https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
or
2) uninstall Magisk completely, maybe even re-lock the phone, and start from the beginning as outlined here: https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654
What is your experience or recommendation?
Click to expand...
Click to collapse
Hey!
Following the official Magisk procedure works, at least for me.
You just have to be careful to restore backup image before starting the OTA download and installing to second slot (After OTA) before rebooting.
Reading this thread:
https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654
I found there’s a lot of confusion (I was confused also and made a few mistakes), but my conclusions are:
- That method is to be used just ONCE in order to gain root, and not every month.
- Always try to use your own patched image if you have the opportunity
- You have to use “fastboot BOOT” and not “fastboot FLASH” when first rooting, otherwise you won’t be able to restore boot image and OTA will fail
- Follow official procedure as a cooking recipe
If you don’t want to root using a patched boot image, you can also use latest TWRP (As of now latest is recovery-3.2.1-2-oreo.img)
https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-1-1-0-touch-recovery-t3688472
And boot to TWRP image in order to install Magisk ZIP (did this yesterday and also worked), but the update via OTA method should be the same.
Best regards.
Personally I just did this:
1) Uninstall magisk (remember to save modules you want to save etc.)
2) Reflash stock boot.img (march update) via fastboot (in the correct booting partition)
3) Relock bootloader
4) Update
5) Unlock bootloader
5) Booting in new april patched_boot.img
6) install Magisk.
official magisk method didn't work for me
Keeping phone to stock and not rooting for only one OTA in more than a month? I think its not worth it!!
I always root my phone and when OTA arrives i just flash twrp version of it and root it again ?
Siebenmik said:
Personally I just did this:
1) Uninstall magisk (remember to save modules you want to save etc.)
2) Reflash stock boot.img (march update) via fastboot (in the correct booting partition)
3) Relock bootloader
4) Update
5) Unlock bootloader
5) Booting in new april patched_boot.img
6) install Magisk.
official magisk method didn't work for me
Click to expand...
Click to collapse
Just wondering "2) Reflash stock boot.img (march update) via fastboot (in the correct booting partition) " should be identical to "Restore Images" in Magisk Uninstall
I think updating can be done without "locking bootloader " and "un-locking bootloader"
What do you think?
I'm following the very simple Magisk OTA update guide and I have been able to update system via OTA for several months already. No rocket science there, as long as you don't mess with system partition (e.g. do NOT allow system modification in TWRP), you are good to go. I even used it successfully with custom kernel (Franco kernel)..
_mysiak_ said:
I'm following the very simple Magisk OTA update guide and I have been able to update system via OTA for several months already. No rocket science there, as long as you don't mess with system partition (e.g. do NOT allow system modification in TWRP), you are good to go. I even used it successfully with custom kernel (Franco kernel)..
Click to expand...
Click to collapse
Are you referring to this guide https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips?
Tiemichael said:
Are you referring to this guide https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips?
Click to expand...
Click to collapse
Yes, exactly. I didn't have any issue with OTA installation yet.
Tiemichael said:
Just wondering "2) Reflash stock boot.img (march update) via fastboot (in the correct booting partition) " should be identical to "Restore Images" in Magisk Uninstall
I think updating can be done without "locking bootloader " and "un-locking bootloader"
What do you think?
Click to expand...
Click to collapse
I forgot saying that using restore image in magisk didn't work. Even though I didn't flash the patched boot.
https://github.com/topjohnwu/Magisk/...tallation-tips
This process works every time if you have enabled secured startup.. If secured startup is disabled then you will get bootloop..
coolkoushik07 said:
https://github.com/topjohnwu/Magisk/...tallation-tips
This process works every time if you have enabled secured startup.. If secured startup is disabled then you will get bootloop..
Click to expand...
Click to collapse
Where to enable secured startup?
Skeuomorphic said:
Where to enable secured startup?
Click to expand...
Click to collapse
create a pattern from security setting and it will prompt to enable secure startup.. just press yes..
coolkoushik07 said:
https://github.com/topjohnwu/Magisk/...tallation-tips
This process works every time if you have enabled secured startup.. If secured startup is disabled then you will get bootloop..
Click to expand...
Click to collapse
Finally a different answer, I have secure boot disabled maybe this is the reason ending into bootloop for past 3 montly security updates. Will try this for May update.
coolkoushik07 said:
https://github.com/topjohnwu/Magisk/...tallation-tips
This process works every time if you have enabled secured startup.. If secured startup is disabled then you will get bootloop..
Click to expand...
Click to collapse
Where can I find 'secured startup' ?
Sorry, for the maybe stupid question ....
Tiemichael said:
Where can I find 'secured startup' ?
Sorry, for the maybe stupid question ....
Click to expand...
Click to collapse
Settings->Security & Location->Screen lock->Pattern
This what was working for me just now:
Detailed steps performed 20.4.2018:
Backup Titanium
Backup Magisk Modules
Switch on Secured Booting (e.g. Pin) => not same a normal pin!
Open Magisk
Uninstall Magisk
Restore Images
Start OTA update
Downlowd
Step1
Step2
Go Back to Magisk
Install to 2nd slot
Reboot
It was working ... very easy!
I can confirm that topjohnwu's official ota tips do work with the Mi A1, but you must have secure booting enabled.
I didn't update my phone for a very long time, then I decided to finally go for the latest MIUI on my Mi Max and basically I flashed full new ROM via fastboot & MiPhone.
You can see detailed description here: https://forum.xda-developers.com/showpost.php?p=78050983&postcount=41
I think it should work with other Xiaomi phones too but please correct me if I'm wrong
The only difference is that I had SuperSu before, but maybe with Magisk it's the same to do - also correct me if i'm wrong
quetzalcoatl2435 said:
I can confirm that topjohnwu's official ota tips do work with the Mi A1, but you must have secure booting enabled.
Click to expand...
Click to collapse
THERE IS AN ALTERNATIVE WAY.
Advantages:
-100% working. Absolutely no problem with unrooting.
-secure booting doesn't have to be enabled.
Disadvantages:
-Installed modules will be lost. I don't know how to back them up.
H.A.L. 9000 said:
---------------------HOW TO UPDATE-----------------------------------------------------------------------------------------------------
When you will receive the update the only thing you need to do is boot twrp, flash magisk unistaller (that you can find here ) and update.
1. type this to boot your recovery (REMEMBER TO COPY THE RECOVERY IMG INTO THE FASTBOOT FOLDER)
Code:
fastboot boot recovery-3.2.1-2-oreo.img
2. flash magisk unistaller from recovey
3. Update your system
4. Repeat the same procedure to root again your device.
If you are italian and you need any help you can find it here, the serious telegram community.
https://t.me/XiaomiMiA1Italia
Special thanks to @samuele94 and @TheRealajeje from the telegram group.
Click to expand...
Click to collapse
freekarol said:
THERE IS AN ALTERNATIVE WAY.
Advantages:
-100% working. Absolutely no problem with unrooting.
-secure booting doesn't have to be enabled.
Disadvantages:
-Installed modules will be lost. I don't know how to back them up.
---------------------HOW TO UPDATE-----------------------------------------------------------------------------------------------------
When you will receive the update the only thing you need to do is boot twrp, flash magisk unistaller (that you can find here ) and update.
1. type this to boot your recovery (REMEMBER TO COPY THE RECOVERY IMG INTO THE FASTBOOT FOLDER)
Click to expand...
Click to collapse
Yeah, but you need a PC for this. If I need access to a PC every time there's an OTA update, might as well download and flash a full ROM. ?
Official Magisk OTA guide works anytime anywhere, no PC needed.
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 !
I have PPW29.116-20 update installed on my G6 Plus. On that same update, I followed the instructions from the other thread to unlock bootloader and install Magisk for root. Now, I am trying to figure out how to install latest OTA security update that started showing up few days ago. I couldn't find any clear instructions around here, as most of them are either from Oreo times, or not very clear. Hopefully, someone has run into this issue on Pie already and knows how to deal with it. Any help would be greatly appreciated.
mrh45Zed said:
I have PPW29.116-20 update installed on my G6 Plus. On that same update, I followed the instructions from the other thread to unlock bootloader and install Magisk for root. Now, I am trying to figure out how to install latest OTA security update that started showing up few days ago. I couldn't find any clear instructions around here, as most of them are either from Oreo times, or not very clear. Hopefully, someone has run into this issue on Pie already and knows how to deal with it. Any help would be greatly appreciated.
Click to expand...
Click to collapse
As far as I know, You can't. You have to be on stock ROM, re-lock the bootloader, take the OTA. There are some risks in re-locking, you can't have any modifications active or you might brick. But if you know what you're doing, it's safe.
weazie said:
As far as I know, You can't. You have to be on stock ROM, re-lock the bootloader, take the OTA. There are some risks in re-locking, you can't have any modifications active or you might brick. But if you know what you're doing, it's safe.
Click to expand...
Click to collapse
Does locking need to be in the original stock or the latest version also works?
dangelfire said:
Does locking need to be in the original stock or the latest version also works?
Click to expand...
Click to collapse
Latest also works. That way you get the newest one and the OTA update is not needed until the next possible update.
You have to uninstall root, if you had a custom.bootlogo you have to replace it with original bootlogo and you can take the OTA.
Or you can just download full fastboot firmware and flash it
https://mirrors.lolinet.com/firmware/moto/evert/official/
Select your channel (don't know what's your channel? Go to settings> about phone and software channel)
If your channel don't have the lastest build version download from retail folder
Sent from my Motorola Moto G6 Plus using XDA Labs
I tried to relock my bootloader, and while it was successfully relocked, I am still unable to get updates.
I unlocked it back on Oreo, but never made any other software changes.
The device boots up with the 'different OS has been installed' message and the updater tells me the system integrity is compromised. The device is also decertified from Google play.
Has anyone got any tips?
awdAvenger said:
I tried to relock my bootloader, and while it was successfully relocked, I am still unable to get updates.
I unlocked it back on Oreo, but never made any other software changes.
The device boots up with the 'different OS has been installed' message and the updater tells me the system integrity is compromised. The device is also decertified from Google play.
Has anyone got any tips?
Click to expand...
Click to collapse
Maybe get the latest version for your channel and flash it using fastboot (as in, full wipe OS reinstall). But wait to see if anyone here has a better idea.
awdAvenger said:
I tried to relock my bootloader, and while it was successfully relocked, I am still unable to get updates.
I unlocked it back on Oreo, but never made any other software changes.
The device boots up with the 'different OS has been installed' message and the updater tells me the system integrity is compromised. The device is also decertified from Google play.
Has anyone got any tips?
Click to expand...
Click to collapse
for now there`s no a perfect way to re lock bootloader, if you want to hide the "different OS has been installed" warn only flash this zip before you re lock your bootloader, dont forget that in stock will still show that system is compromised if you try to search for updates. (so my recommendation is dont relock bootloader! flash full stock rom with fastboot commands if you dont want to loose your apps just erase "fastboot erase userdata" from fastboot commands)
https://drive.google.com/open?id=1VE0kaUxmUbbhhNo075MCaW6VxaOTiDL6
For get certified playstore you need to verify that you can install Netflix if you can only wipe app data and playstore will show as certified device.
if you cant install netflix you need to change device fingerprint with a magisk module Safety Net Patch or with Magisk hide props.
ETA: never mind, figured it out.