My Mi A1 is unlocked by MiFlash stock rom and rooted by ghpranav's AIO Tool. It has updated to September patch and with FlashFire + SuperSu.
The followings is my steps update to October patch,
1. Download ravinder0003's CF auto root boot.img and copy it into adb folder.
2. Connect Mi A1 with PC,
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot getvar all
3. Slot b is current active slot in my phone which has September patch and rooted. Slot a is unrooted.
Code:
fastboot set_active a
fastboot reboot
4. Reboot system into slot a. After reboot, system update to October patch, the patch will be updated into slot b.
My update patch is huge size, 1060.5MB. As we konw the patch should be 118MB from September to October, I don't know why my size is so huge. Maybe because I deleted some media file and systme apps after I updated September patch in slot b before.
5. Auto reboot after success update and I got bootloop on Mi logo.
6. Press Volume down + Power buttons to enter fastboot mode.
7. Reboot system into updated slot b.
Code:
fastboot set_active b
fastboot reboot
8. System has updated to October patch. Then get root,
Code:
fastboot boot boot.img
Waiting auto reboot in several minutes, be patience.
Open FlashFire app to confirm whether system get rooted.
That's all and for your reference.
rockice said:
Code:
fastboot getvar all
Click to expand...
Click to collapse
This command is very helpful, thanks! :good:
90180360 said:
This command is very helpful, thanks! :good:
Click to expand...
Click to collapse
what does that command do?
robgee789 said:
what does that command do?
Click to expand...
Click to collapse
You can see which partition is active.
Sent from my Mi A1 using Tapatalk
NITRO_100 said:
You can see which partition is active.
Sent from my Mi A1 using Tapatalk
Click to expand...
Click to collapse
Cheers mate
Sent from my Mi A1 using Tapatalk
Can't turn on wifi to update to october patch
after setting active_x and rebooting updater app says switch to other sim and wifi isn't working.
Can anyone help?
Hey guys if I have partition b set as active can I use fast boot to partition a as active and go back to the September update?
Sent from my Mi A1 using Tapatalk
robgee789 said:
Hey guys if I have partition b set as active can I use fast boot to partition a as active and go back to the September update?
Sent from my Mi A1 using Tapatalk
Click to expand...
Click to collapse
Before I update system, I forgot to check which month's patch in my slot a. So when I update to October patch in slot b, I don't know which patch is in my slot a now.
In your case, if October patch is in your slot b, September patch is in slot a, when you boot to slot a, of coursre you go back to September patch.
Hey I just bought the A1 and installed the October update before doing anything. But now I want to root or flash TWRP, what steps should I take? Can't find anyone with Oct patch to help me.
rodsayd said:
Hey I just bought the A1 and installed the October update before doing anything. But now I want to root or flash TWRP, what steps should I take? Can't find anyone with Oct patch to help me.
Click to expand...
Click to collapse
Unlock your phone first.
And October update patched root image file click here .
Will I need to reflash everything that works on the system partition as well ? (For example, Xposed, Viperaudio, GLTools, etc)
I am stuck in a boot loop. I tried to update from September to October image using miflash. When it was in September build it was rooted and I installed Xposed. I am waiting from 1hr still it's in boot loop. Plz help.
vedkamath said:
I am stuck in a boot loop. I tried to update from September to October image using miflash. When it was in September build it was rooted and I installed Xposed. I am waiting from 1hr still it's in boot loop. Plz help.
Click to expand...
Click to collapse
I suggest you download stock rom from here and MiFlash it with "Save User Data" option.
So you get October build, then unlock and root your system next.
rockice said:
I suggest you download stock rom from here and MiFlash it with "Save User Data" option.
So you get October build, then unlock and root your system next.
Click to expand...
Click to collapse
Thanks a lot for the reply bro. I flashed the October image from official MIUI site which you provided along with latest miflash but still getting bootloop. One thing I observed is that after flashing stock my bootloader automatically getting locked. I unlocked the bootloader and flashed the stock image again, still getting bootloop. Tried in both slot a and b. Technically it should work, don't know why it's not working. Any help would be greatly appreciated.
set_active command is missing from my fastboot.
P4P3RB4G said:
set_active command is missing from my fastboot.
Click to expand...
Click to collapse
Use the latest revision: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
rockice said:
I suggest you download stock rom from here and MiFlash it with "Save User Data" option.
So you get October build, then unlock and root your system next.
Click to expand...
Click to collapse
Does someone have an answer why I had the latest version (rooted) and always asking to update?! [emoji848]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://techintouch.it
Latest Build ist 7.10.30
tidschi said:
Latest Build ist 7.10.30
Click to expand...
Click to collapse
In the Xiaomi site it's the 7.10.14..
http://techintouch.it
Chazy12 said:
In the Xiaomi site it's the 7.10.14..
http://techintouch.it
Click to expand...
Click to collapse
Latest Full ROM it's! OTA is 7.10.30 as told before...
Related
Dear users;
this month I haven't received the March updates yet. Is it a problem with my device or will it not be released this month?
Greetings
IlSaro said:
Dear users;
this month I haven't received the March updates yet. Is it a problem with my device or will it not be released this month?
Greetings
Click to expand...
Click to collapse
see this https://forum.xda-developers.com/mi-a2-lite/help/march-update-t3913167
IlSaro said:
Dear users;
this month I haven't received the March updates yet. Is it a problem with my device or will it not be released this month?
Greetings
Click to expand...
Click to collapse
Dear IlSaro,
No Dear, This Is Not Your Mobile Problem At All. As The March Update Was Released & But Some How Quickly It Was Taken Offline. May Be There Was An Issue Or Bootloop Problem. I Am Assuming That We Will Get March Update Very Soon.
If You Get Please Be Informed Us On Mentioned Below Thread.
https://forum.xda-developers.com/mi-a2-lite/help/march-update-t3913167
Thanks & Have A Nice Day.
Thanks,
MUHAMMAD Asif Qasim
March update is already up. I'm from the Philippines, btw.
Got the March update today!!
I couldnt update. There is an error. I have Magisk root 10. 0.0.4 and unlock bootlader. Is it related to the problem?
dr.bahaeddin said:
I couldnt update. There is an error. I have Magisk root 10. 0.0.4 and unlock bootlader. Is it related to the problem?
Click to expand...
Click to collapse
I Think So It Is Related To Unlock Bootloader & Root. Download Stock Rom From MIUI and Try To Clean Install Then Update.
dr.bahaeddin said:
I couldnt update. There is an error. I have Magisk root 10. 0.0.4 and unlock bootlader. Is it related to the problem?
Click to expand...
Click to collapse
I don't think so. I updated from January to February update successfully. I did lose the root though, but I re-rooted my phone through patched boot image file. I Will wait for the new patched boot image file before updating to March.
Does imei repair block the update by any chance?
Same **** all over again....
i can't update to march update. same thing on feburary and to get to work i have to reflash the rom again.
i dont want to reflash the rom every time i want to update...
it is possible to manualy download te update zip and force install?
masterbyte said:
Same **** all over again....
i can't update to march update. same thing on feburary and to get to work i have to reflash the rom again.
i dont want to reflash the rom every time i want to update...
it is possible to manualy download te update zip and force install?
Click to expand...
Click to collapse
Yes it is. Just wait until the fastboot rom is released (should be within the next few days) and flash that fastboot rom with miflash using the option "save user data"!
Hello!! Here the update arrived today, and everything went well!!
Hugs
Voodoojonny said:
Yes it is. Just wait until the fastboot rom is released (should be within the next few days) and flash that fastboot rom with miflash using the option "save user data"!
Click to expand...
Click to collapse
Thanks! My Daughter have the same phone and she can't update either. And dosen't have Root on the phone.
Voodoojonny said:
Yes it is. Just wait until the fastboot rom is released (should be within the next few days) and flash that fastboot rom with miflash using the option "save user data"!
Click to expand...
Click to collapse
They still haven't released February(10.0.4.0) fastboot rom lol. Not sure if they are going to release March soon.
Update on the way
Got update today its 266.7 MB. From np.
marstonpear said:
They still haven't released February(10.0.4.0) fastboot rom lol. Not sure if they are going to release March soon.
Click to expand...
Click to collapse
They don´t release every rom as fastboot. But since the 10.0.7.0 is the first one that´s stable again, the chances are good...
Voodoojonny said:
They don´t release every rom as fastboot. But since the 10.0.7.0 is the first one that´s stable again, the chances are good...
Click to expand...
Click to collapse
Weird that we can call this one "stable" lol. Nothing has been stable since Oreo imho.
Security patch march
I can't install March security patch,it's completely download but not install it was error,please help me
Kasunkcb said:
I can't install March security patch,it's completely download but not install it was error,please help me
Click to expand...
Click to collapse
Probably you have a modified system or boot image. If you have twrp and/or magisk, probably boot. You'll need to flash a stock boot to get the update to install.
I wrote down the steps I took to update (I had to flash boot due to twrp/magisk install order)
https://forum.xda-developers.com/mi-a2-lite/how-to/10-0-4-0-to-10-0-7-0-ota-keeping-magisk-t3916863
You don't say what you have so you may not be able to follow the same steps.
As you can see ; Stuck at march update downloading... ; and it pause automatically after 1 minuets
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Process to install security updates on rooted Nokia 8
Download the Nokia 8 OTA zip files on your Computer from this link in the OTA folder https://bit.ly/nokia-nb1 (it's usually up to date)
Download the Nokia 8 latest FULL ROM OTA zip file on your Computer from this link in the OTA folder https://bit.ly/nokia-nb1 (usually with size above 1 GB, currently it is: NB1-5150-0-00WW-B03-update.zip 1.52 GB)
Connect the phone to the PC using the USB cable and enable USB debugging (after enabling developer options)
Verify connection and drivers are correct on your computer by using the following ADB/Fastboot command(minimal adb fastboot can be found here https://forum.xda-developers.com/showthread.php?t=2317790):
adb devices
Click to expand...
Click to collapse
If you see your device and ID then all good so far
Use the following adb command on your Computer
adb reboot bootloader
Click to expand...
Click to collapse
Alternative to the previous step, you can select ADB sideload from the stock recovery menu after booting into stock.
when the device reboots into bootloader / or ADB sideload is selected from recovery use this command on your computer:
adb sideload path_to_zip/FULL_ROM_OTA.zip
Click to expand...
Click to collapse
Once loaded, reboot using the command
adb reboot
Click to expand...
Click to collapse
Sideload the OTA updates you have downloaded in step 1 using the same process as before OR Update normally through android system settings. Keep updating and restarting until you have the latest update
Download the latest Nokia 8 Stock boot image file on your phone from this link in the STOCK BOOT folder https://bit.ly/nokia-nb1 (it's usually up to date)
Make sure you have the correct Stock boot image file for the the software version you have. (if you have May update, use May image, June update then use June Image, etc....)
Use magisk manager to root the boot image you just downloaded. Use the second option like in the photo below
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Transfer the patched image file to your computer
Get back to bootloader (download mode) using any method or the below code (USB debugging on)
adb reboot bootloader
Click to expand...
Click to collapse
When in download mode, use the following command on your computer and take note of the result (in case something goes wrong)
fastboot getvar current-slot
Click to expand...
Click to collapse
Use the following command:
fastboot flash boot path_to_zip/patched_boot.img
Click to expand...
Click to collapse
Reboot
Enjoy
Wait one more month
Repeat
Tested scenarios:
Working on TA-1012 to get the Pie May 2019 update from April update
Working on TA-1012 to get the June 2019 update from May update
Working on TA-1012 to get back to latest rom (NB1-5150-0-00WW-B03-update) from April update
Working on TA-1012 to get back to latest rom (NB1-5150-0-00WW-B03-update) from May update
Working on TA-1012 to get back to latest rom (NB1-5150-0-00WW-B03-update) from June update
Screenshot, showing update using system settings to May update, after sideloading full ROM (NB1-5150-0-00WW-B03-update) from a rooted device on May update, proving downgrading works fine.
June files have been updated to the link: https://bit.ly/nokia-nb1
Thanks to Dorian Stoll
Well I got nowhere. The moment I reboot into bootloader, the device isn't visible in adb anymore, but only under "fastboot devices", so "adb sideload path-" fails because it can't find the device. What gives?
VonZigmas said:
Well I got nowhere. The moment I reboot into bootloader, the device isn't visible in adb anymore, but only under "fastboot devices", so "adb sideload path-" fails because it can't find the device. What gives?
Click to expand...
Click to collapse
Boot into recovery and select "apply update from adb" as shown in the photo below (not mine)
Kiwironic said:
Boot into recovery and select "apply update from adb" as shown in the photo below (not mine)
Click to expand...
Click to collapse
I'm still on TWRP at this stage. I can't get past step 7.
Hi guys,
is it necessary to sideload OTA updates? Can I just update the system in settings and then flash a rooted boot image corresponding to the update version?
VonZigmas said:
I'm still on TWRP at this stage. I can't get past step 7.
Click to expand...
Click to collapse
This is for people like me who are not able to run twrp on their phones. If you have twrp you should be able to flash the zip file easy. This guide assumes you have stock recovery
Update: confirmed working for July update as well.
I'm sorry if this seems dumb, but I'm kinda new to all of this. I have TWRP and now I want the July patch, how can I do it?
Update: I gave up and flashed stock recovery.
helscarthe said:
I'm sorry if this seems dumb, but I'm kinda new to all of this. I have TWRP and now I want the July patch, how can I do it?
Update: I gave up and flashed stock recovery.
Click to expand...
Click to collapse
In twrp it should be straight forward to flash a zip file which includes the update. Another option or if this fails, start sideload from twrp like in the following photos
Hi, links no longer working. Does anyone have working links for V5.15D ? I need stock boot image and OTA update to sideload. Thanks.
Unfortunately the phone has been abandoned by the developers. I have got myself a xiaomi 9t.
I'm sorry
Kiwironic said:
Unfortunately the phone has been abandoned by the developers. I have got myself a xiaomi 9t.
I'm sorry
Click to expand...
Click to collapse
It's ok thanks for your work on it!
Kiwironic said:
Unfortunately the phone has been abandoned by the developers. I have got myself a xiaomi 9t.
I'm sorry
Click to expand...
Click to collapse
Oh man, can you still get stock images or whatnot anywhere? I only need the least that will get me back to stock before I turn it in for warranty but not sure where to start.
Sorry man I relied on the other developer's repository so much that I can't offer any tools nor files. I can help you get to stock easy. As Nokia offers the original Rom on their website officially. I believe it can be found here
https://www.nokia.com/phones/en_int/betalabs
Register for beta labs then de register and download the latest firmware they offer you
Kiwironic said:
Sorry man I relied on the other developer's repository so much that I can't offer any tools nor files. I can help you get to stock easy. As Nokia offers the original Rom on their website officially. I believe it can be found here
https://www.nokia.com/phones/en_int/betalabs
Register for beta labs then de register and download the latest firmware they offer you
Click to expand...
Click to collapse
Hey, sorry for the late reply. I attempted to get back to stock via NOST and the 5150 image he provided https://forum.xda-developers.com/no...re-nokia-to-stock-t3867646/page3#post80627823 , but turns out I don't have critical unlocked and seem to have misplaced the unlock key. What can I do next?
VonZigmas said:
Hey, sorry for the late reply. I attempted to get back to stock via NOST and the 5150 image he provided https://forum.xda-developers.com/no...re-nokia-to-stock-t3867646/page3#post80627823 , but turns out I don't have critical unlocked and seem to have misplaced the unlock key. What can I do next?
Click to expand...
Click to collapse
Try unlocking again using the Nokia unlock Web page
Kiwironic said:
Try unlocking again using the Nokia unlock Web page
Click to expand...
Click to collapse
The web page requires a validation code that you get from the unlock app from your phone and as we know the app gives a nice "Device not support" if you try running it on Pie. Tested myself just in case.
Kiwironic said:
Try unlocking again using the Nokia unlock Web page
Click to expand...
Click to collapse
In the end I've decided to just go for it and see what happens. Shouldn't make things worse. Flashed the stock boot image for my security patch right on top of TWRP. The phone booted, but I still couldn't install updates. Tried flashing the next update (May) from both ADB and the SD card - failed with the same download state initialization error. Figured I may as well try the same but with the full .zip of my current OS version (April) and while it took pretty long, it finished with no issues and OTA's started rolling in without a hiccup. Surprisingly I didn't even lose any of my data in the process, which I was preparing for. I guess all that's left is to lock the bootloader?
Anyway thanks for the help!
Updated to Android 11 (clean install) and can't get Magisk patched image to boot.
I'm using manager 8.0.2(307) and the latest Magisk is 21.0
I patched the boot image from the website, flash successfully, but it reboots to the bootloader saying "no valid slot to boot"
Is anyone else having this issue?
I know the unpatched boot image is ok because when I flash it back it boots up fine.
Am I missing anything?
Edit:
Was able to boot without issue with the latest Magisk Canary 04995881 (21002).
Apparently, it's related to these issues:
https://github.com/topjohnwu/Magisk/issues/3277
https://github.com/topjohnwu/Magisk/issues/3271
I'm willing to help anyone else suffering from this issue get their phones booting back up.
nontheoretical said:
Updated to Android 11 (clean install) and can't get Magisk patched image to boot.
I'm using manager 8.0.2(307) and latest Magisk is 21.0
I patched the boot image from the website, flash successfully, but it reboots to the bootloader saying "no valid slot to boot"
Is anyone else having this issue?
I know the unpatched boot image is ok because when I flash it back it boots up fine.
Am I missing anything?
Thanks in advance.
Click to expand...
Click to collapse
Did you disable or remove all modules? See https://github.com/topjohnwu/Magisk/issues/3292#issuecomment-705764812
I have no modules installed, and had no problems with the Sept. update. I have not yet tried October.
dcarvil said:
Did you disable or remove all modules? See https://github.com/topjohnwu/Magisk/issues/3292#issuecomment-705764812
I have no modules installed, and had no problems with the Sept. update. I have not yet tried October.
Click to expand...
Click to collapse
I'm on the Oct update and I don't have any modules installed.
It's a clean install so I haven't even had the chance to install modules yet.
I might downgrade to Sept update if I can't root soon.
Apparently it's related to these issues:
https://github.com/topjohnwu/Magisk/issues/3277
https://github.com/topjohnwu/Magisk/issues/3271
I am also having the "no valid slot to boot" error. I updated ota google play system update and then got an error to factory reset or try again. I have been trying to flash-all without -w to september and october factory images but still keep getting the error and cannot boot into system.
Can anyone help me fix this issue? I'm unable to use the adb magisk remove-module script.
Bubbler4343 said:
I am also having the "no valid slot to boot" error. I updated ota google play system update and then got an error to factory reset or try again. I have been trying to flash-all without -w to september and october factory images but still keep getting the error and cannot boot into system.
Can anyone help me fix this issue? I'm unable to use the adb magisk remove-module script.
Click to expand...
Click to collapse
There are some recent comments on running the remove-module script in the github link in post 2. Hopefully something there will help.
Bubbler4343 said:
I am also having the "no valid slot to boot" error. I updated ota google play system update and then got an error to factory reset or try again. I have been trying to flash-all without -w to september and october factory images but still keep getting the error and cannot boot into system.
Can anyone help me fix this issue? I'm unable to use the adb magisk remove-module script.
Click to expand...
Click to collapse
Not sure about the removing of the modules (maybe try the safe mode trigger built into the new Magisk?)
I was able to successfully boot by flashing the stock boot image, the updating to the latest Magisk Canary 04995881 (21002)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Looks like this was updated recently due to the two issues I listed earlier.
I'm gonna keep my magisk_patched.img for this build of Magisk and try with the latest beta and stable releases as they come out.
I'm happy to help anyone else get their build to boot, provide checksums for sanity checks, etc.
I can confirm that flashing the 11 image in its stock form first, letting Android upgrade your user data, then flashing the image with the patched boot.img file works!
Directly flashing an image over Android 10 with boot.img patched throws it into fastboot
EndlessBliss said:
I can confirm that flashing the 11 image in its stock form first, letting Android upgrade your user data, then flashing the image with the patched boot.img file works!
Directly flashing an image over Android 10 with boot.img patched throws it into fastboot
Click to expand...
Click to collapse
Are you using Canary or Stable?
I had to switch to Canary to get it to boot.
I was coming from a clean install so I had no user data to upgrade.
I'm coming from a very unclean install and it worked perfectly with this method. Switched to Beta in Magisk Manager and running 21.0 (21000) on a Pixel 4 XL
EndlessBliss said:
I'm coming from a very unclean install and it worked perfectly with this method. Switched to Beta in Magisk Manager and running 21.0 (21000) on a Pixel 4 XL
Click to expand...
Click to collapse
It looks like this was only reported by users on pixel 3a and older models.
My phone gave me the update download notification, but somehow cannot download the OTA - get an error each time. Anyone else on global has same problem?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Same problem here.
I have a T-mobile device converted to global & rooted. Could it have anything to do with this?
I'm on T-Mobile but bought from OnePlus directly. Same problem.
you have to uninstall magisk using "restore images", then install the OTA, then reinstall magisk to the inactive slot. it's failing the check on the boot partition if you're rooted
zander21510 said:
you have to uninstall magisk using "restore images", then install the OTA, then reinstall magisk to the inactive slot. it's failing the check on the boot partition if you're rooted
Click to expand...
Click to collapse
Thanks.
I think that the "Restore Images" option shows up when pressing the "Uninstall" in the Manager. Is it so?
Question: After OTA, can I just "Install" Magisk directly from the Magisk Manager?
Or would I need to patch the boot image and then flash it manually.
sjgoel said:
Thanks.
I think that the "Restore Images" option shows up when pressing the "Uninstall" in the Manager. Is it so?
Question: After OTA, can I just "Install" Magisk directly from the Magisk Manager?
Or would I need to patch the boot image and then flash it manually.
Click to expand...
Click to collapse
I tried the whole restore images and it failed so I tried to fastboot boot the unpatched 11.0.2.2. it booted but no wifi for. Whatever reason. I tried to download 11.0.4.4 on cellular but I don't have a stable signal so it kept failing. Can someone please post the 11.0.4.4 download image and post a link. It would be most appreciated. I cannot find any other way to download it.
zander21510 said:
you have to uninstall magisk using "restore images", then install the OTA, then reinstall magisk to the inactive slot. it's failing the check on the boot partition if you're rooted
Click to expand...
Click to collapse
Not that I don't believe you, but OnePlus never did this before for rooted users. It seems odd that they'd start doing this now.
BeardKing said:
Not that I don't believe you, but OnePlus never did this before for rooted users. It seems odd that they'd start doing this now.
Click to expand...
Click to collapse
It seems so. With an unpatched boot I can try to download, but with a patched boot it gives an error. I'm starting to lose my fondness for OnePlus.
BeardKing said:
Not that I don't believe you, but OnePlus never did this before for rooted users. It seems odd that they'd start doing this now.
Click to expand...
Click to collapse
Agree, never experienced this earlier.
It looks like an increment update (593MB) and will not download for rooted devices. I was able to update on an unrooted device but keep getting error message on mine which is rooted.
I guess we have to wait for the full update zip.
aieromon said:
It looks like an increment update (593MB) and will not download for rooted devices. I was able to update on an unrooted device but keep getting error message on mine which is rooted.
I guess we have to wait for the full update zip.
Click to expand...
Click to collapse
Yes, that was it. I had to MSM back to TMobile A10, unlock bootloader, convert to global A10, and then OTA to 11.0.4.4 - and then root.
aieromon said:
It looks like an increment update (593MB) and will not download for rooted devices. I was able to update on an unrooted device but keep getting error message on mine which is rooted.
I guess we have to wait for the full update zip.
Click to expand...
Click to collapse
Will wait for that full update. TY!
Disregard
If you're using the global version you can use these, 11.0.4.4.IN21AA global kernels patched and stock, tested on an IN2010.
Stock: https://www.davesanthology.com/publ....IN21AA/11.0.4.4.IN21AA_boot_stock_IN2010.img
MD5: https://www.davesanthology.com/publ....IN21AA/11.0.4.4.IN21AA_boot_stock_IN2010.md5
Patched: https://www.davesanthology.com/publ...1.0.4.4.IN21AA_boot_magisk_patched_IN2010.img
MD5: https://www.davesanthology.com/publ...1.0.4.4.IN21AA_boot_magisk_patched_IN2010.md5
For any other version you can d/load and install with a rooted device if you temporarily remove root, I've just done it this way. This assumes you have a stock and patched boot.img for your current ROM available (either in Magisk as a backup image or somewhere else). 4.4 wouldn't download whist I had the patched kernel installed, yes a new OP method.
1. Disable (no need to delete) your Magisk modules (to be safe)
2. Flash the stock boot image (for the ROM you're currently using) in fastboot:
Code:
fastboot flash boot <stock_boot>.img
3. Reboot and test, just to be sure (you shouldn't have root)
4. Boot from the patched (root) boot image (for the ROM you're currently using) in fastboot:
Code:
fastboot boot <patched_boot>.img
5. Now you'll have root back but the stock image will still be installed
6. Download the update, if it's taking a long time hit pause them resume a couple of times
7. Install the update and DO NOT REBOOT!
8. Open Magisk and install via direct method and DO NOT REBOOT!
9. Install Magisk again but this time use install to inactive slot method
10. Reboot when prompted
11. Reenable your Magisk modules
Full update is now available for download
aieromon said:
Full update is now available for download
Click to expand...
Click to collapse
Thanks.
Full update link: https://www.oneplus.com/support/softwareupgrade/details?code=PM1586920535300
This thread going to guide you on how you can root Realme GT NEO 2 Device with RUI 3.0 installed.
This boot image is fresh, and it's patched for root access.
Caution: Before flashing, you need to have your bootloader unlocked, for bootloader unlocking, go to this link and follow the procedure to get approval and unlock your device bootloader.
Link: https://forum.xda-developers.com/t/bootloader-unlock-realme-gt-neo-2-rmx3370-all-variants.4391679/
After you get approval, you are ready to root your device!
For this tutorial, I gonna use a windows device.
WARNING!
I am not responsible for anything. proceed at your own risk. Rooting or Unlocking the Bootloader voids the device warranty, keep it in your mind.
STEP - ONE
Only follow this step, if you get approval for the bootloader, and you didn't unlock this device or your flashing environment needs to be configured. You need to visit the following link to set up your environment for flashing a custom boot image.
Link: https://njpsmultimedia.blogspot.com/2022/04/realme-gt-neo-2-bootloader-unlock.html you just need to follow the video tutorial on this website.
STEP - TWOIt's assumed that your environment is properly configured. Let's flash this boot image to root your device.
Download this zip file from here https://drive.google.com/file/d/1Xk1yBp5EDCZbl3i3jMtOhjfaVtTCQqYB/view?usp=sharing and copy the boot.img file to platform-tools folder.
Then open the terminal and cd to the platform-tools folder.
Then, shut down your device and hold the vol up + vol down + power button together to boot this device into fastboot mode.
First, you need to run
Code:
fastboot devices
to check if your device is properly connected to the bootloader interface. If it shows something then your device is properly connected, If not, try to install the device driver, change the cable, or boot into the bootloader mode again.
If your device is connected properly, then you will see a screen like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And then run this command:
Code:
fastboot flash boot boot.img
Then,
Code:
fastboot reboot
You are done! Congratulation.
Note: This method was tested with Realme UI 3.0 android 12 on GT NEO 2. Do not try this method on RUI 2.0 or on other devices.
SCREENSHOTS
Note
If you face NO WIFI, Sound issue on the C04 version, you are advised to flash this alternate version from here: https://forum.xda-developers.com/t/...uide-on-gt-neo-2.4435919/page-2#post-86985433
Do you lose all data ? On the root part the bootloader is already unlocked
theogr91 said:
Do you lose all data ? On the root part the bootlocker is already unlocked
Click to expand...
Click to collapse
- it is necessary to have the bootloader unlocked before flash (instructions on how to unlock the bootloader can be found in the video in the post above or here on the forum)
- after flash just install Magisk manager
no data loss, tested and functional
theogr91 said:
Do you lose all data ? On the root part the bootlocker is already unlocked
Click to expand...
Click to collapse
If your bootloader is already unlocked, no data loss. but If your device bootloader is not unlocked, then unlocking your device data will be erased.
Do we flash magisk or other way of root ?
theogr91 said:
Do we flash magisk or other way of root ?
Click to expand...
Click to collapse
You need not flash anything extra than flashing customized boot.img. Just simply follow this step and your device will be rooted.
Worked like charm thanks. Will the phone be ok after an OTA update ?
Help...After flashing boot image and rebooted , Wifi is not scanning the networks and I am unable to take calls but 4g(internet) is working fine. Please reply me for any fix. I followed the exact steps you mentioned. My Device Realme Gt neo 2 UI 3.0
mahesh.pujala said:
Help...After flashing boot image and rebooted , Wifi is not scanning the networks and I am unable to take calls but 4g(internet) is working fine. Please reply me for any fix. I followed the exact steps you mentioned. My Device Realme Gt neo 2 UI 3.0
Click to expand...
Click to collapse
In my case, all is fine.
You can try backup data and then reset your device through recovery.
theogr91 said:
Worked like charm thanks. Will the phone be ok after an OTA update ?
Click to expand...
Click to collapse
After the OTA update, you may need to flash this boot image again.
Help...After flashing boot image and rebooted , Wifi is not scanning the networks and I am unable to take calls but 4g(internet) is working fine. Please reply me for any fix. I followed the exact steps you mentioned. My Device Realme Gt neo 2 UI 3.0
Nurujjamanpollob said:
In my case, all is fine.
You can try backup data and then reset your device through recovery.
Click to expand...
Click to collapse
Thanks for the reply . Any way I reverted back to previous state by flashing stock boot image and firmeware. Now everthing works fine. I will think about rooting later..
Removed root and updated to RMX3370_11_C.04 is it safe to reflash root image on this version?
theogr91 said:
Removed root and updated to RMX3370_11_C.04 is it safe to reflash root image on this version?
Click to expand...
Click to collapse
I just tried this and it worked for me...
Meanwhile I realised that my wifi and my phone don't work anymore... I have no idea if this boot image is the cause.
Grobie13 said:
Meanwhile I realised that my wifi and my phone don't work anymore... I have no idea if this boot image is the cause.
Click to expand...
Click to collapse
I have no wifi after the flash and i have no twp on RMX3370_11_C.04 any way to fix it ?
theogr91 said:
I have no wifi after the flash and i have no twp on RMX3370_11_C.04 any way to fix it ?
Click to expand...
Click to collapse
No solution so far. I think first everything was fine, after flashing the magisk boot image it's gone worse... But I'm not sure.
I do not recommend updating on RMX3370_11_C.0. After flashing boot image (without Magisk) wifi no longer working.
I flashed clean firmware and lock bl i am done moding this device only adb debloat.. And after clean flash netflix still wont open login screen...
Grobie13 said:
No solution so far. I think first everything was fine, after flashing the magisk boot image it's gone worse... But I'm not sure.
Click to expand...
Click to collapse
What device variant you use? India or global?
Probably I gonna update this boot image today with latest update.
Nurujjamanpollob said:
What device variant you use? India or global?
Probably I gonna update this boot image today with latest update.
Click to expand...
Click to collapse
It's global respectively EU. But I start from scratch yesterday. I flashed twrp, format data and flashed magisk. But other people need your patched boot image. Thanks for providing.