OK so, I don't even know where to start. I got this phone in November and I did the unlocking and rooting following https://forum.xda-developers.com/mi-a3/how-to/guide-how-to-root-mi-a3-magisk-t3958509 that guide. Since then I wasn't able to install any of the OTA updates.
Yesterday I updated to March Security Update using the latest global version I found on this https://forum.xda-developers.com/mi-a3/how-to/rom-xiaomi-mi-a3-laurelsprout-t3962489 thread and while I had lots of issues I though I did it right? Now the WI-FI isn't working (doesn't turn on) and I don't know what to do. PLEASE HELP ME
Reflash whole rom, if you're using patched boot image with Magisk, make sure that it's the very same version as your ROM. The best way is to patch boot.img yourself, don't use ready made images.
Related
I am trying to root my HTC Hero(Orange uk) but i keep running into a problem, im trying to copy the new recovery ROM to the phone but it keeps telling me that remote access isnt allowed. Also i can't use the flash rec method.
I previously had a rooted and custom ROM on here but removed it as some things didnt work then upgraded to the latest official HTC ROM (2.73.xx) and now i can't mdoify the recovery image.
sorry if i have been a bit vauge with my message but does anyone know how to overcome these problems?
Cheers
John
if you flashed the latest RUU update you need to create a goldcard and downgrade. using RUUs is generally the last option if you can't get your phone to work, because if you install the latest version you don't have any security holes that you could use. luckily there is the goldcard method, although it is a PITA (never did it, just read about it...)
not sure how this worked but i reinstalled the latest RUU and then installed flash rec and it worked
would be interesting to know what you did (with version numbers), so that question would be answered...
not gonna try though, don't want to get stuck with a generic rom
It expects "motorola/griffin/griffin:7.1.1/NPLS26.118-20-5/5:user/release-keys" or "motorola/griffin/griffin:7.1.1/NPLS26.118-20-5-3/3:user/release-keys" while the current one is "motorola/griffin/griffin:7.1.1/NPLS26.118-20-1/1:user/release-keys", however, in the OS it shows as "motorola/griffin/griffin:7.1.1/NPLS26.118-20-5/5:user/release-keys", it only shows as "motorola/griffin/griffin:7.1.1/NPLS26.118-20-1/1:user/release-keys" in the recovery.
Running stock ROM, TurboZ Kernel, Magisk, and unlocked bootloader. Just trying to install the October Security Patch. Any idea on how to fix is appreciated.
From my understanding, you need to be completely stock to be able to sideload an OTA update. You're running a custom kernel with root using Magisk so the OTA will fail it's initial checks for installing. I haven't rooted my Z so can't really confirm myself. The last phone I had root on was the Moto X Style and the conditions for pushing an OTA used to be as I outlined. Maybe someone else can clarify.
I have a verizon model SM-G965U (Snapdragon). A few weeks ago, I was able to follow this upgrade sequence to get Pie:
G965USQU3BRI9 to G965USQU3BRJ5
G965USQU3BRJ5 to G965USQU3ZRJ8
So now I am currently stuck on G965USQU3ZRJ8. I am attempting to upgrade it to the latest Pie release which is G965USQU3CRKD (November 19 2008). However, when I try to update the firmware via download mode / adb sideload update.zip, it fails because it expects the BRJ5 model.
So, my only option it seems to sideload the update is to first downgrade back down to BRJ5. How can I downgrade this firmware, or would it be easier to flash the latest updates via odin another way? I am clueless, please help a disgruntled user stuck in the wrong version of Pie.
cmcjacob said:
I have a verizon model SM-G965U (Snapdragon). A few weeks ago, I was able to follow this upgrade sequence to get Pie:
G965USQU3BRI9 to G965USQU3BRJ5
G965USQU3BRJ5 to G965USQU3ZRJ8
So now I am currently stuck on G965USQU3ZRJ8. I am attempting to upgrade it to the latest Pie release which is G965USQU3CRKD (November 19 2008). However, when I try to update the firmware via download mode / adb sideload update.zip, it fails because it expects the BRJ5 model.
So, my only option it seems to sideload the update is to first downgrade back down to BRJ5. How can I downgrade this firmware, or would it be easier to flash the latest updates via odin another way? I am clueless, please help a disgruntled user stuck in the wrong version of Pie.
Click to expand...
Click to collapse
You may install the required Android Oreo build first, and then update using ADB sideload to Pie.
This may help you - Download Galaxy S9 Pie.
itskapil said:
You may install the required Android Oreo build first, and then update using ADB sideload to Pie.
This may help you - Download Galaxy S9 Pie.
Click to expand...
Click to collapse
That does not help at all. It simply repeats the steps I have already taken. If it were as easy as reversing these steps I would not post this topic. It was easy to upgrade, but downgrading is not as simple.
I already have Pie, I don't want vague upgrade instructions. I specifically want to go back to Oreo.
Use Odin to downgrade to Oreo. It's been covered many times in the beta thread. There should be a link in there for a lower version then you'll need to patch to BRJ5 and then the latest Beta.
https://forum.xda-developers.com/showpost.php?p=77970099&postcount=121
I recently bought a 1 year old XT1941-4 which had already been rooted with Magisk on Android Pie with the November PPKS29.68-16-36-11 security patch already installed (RETGB). Main reason was I wanted a rooted phone and did not want to have to mess with doing it myself. Phone is rooted perfectly and no issues. However, I started getting notifications that a new OTA is available for December. Initially I disabled these notifications and now I am getting a full screen nag about them and that the software update is unsuccessful. I decided to try the temp uninstall of Magisk procedure to allow the OTA to complete but when I hit restore images I get 'Back up does not exist'.
I thought one of the advantages of Magisk was that it could be temp installed to allow OTAs to complete. I see that mirrors.lolinet.com has the RETGB Dec update PPKS29.68-16-36-13. Can I use this someway to sort the problem out? I am a complete noob about this and have read several threads to find a solution but still not sure what direction to go. Can anyone explain to me step by step what I need to do?
Hi, my bootloader unlocked with twrp installed lgv30 keeps complaining about a system update, but each time i choose install it just reboots into twrp.
I presume the install process needs the stock recovery for something? I'm unsure how to proceed, and it will not even let me turn off the notifications!
Correct, OTA updates cannot be applied via TWRP and require stock recovery. Fact is, you don't want to apply the OTA, because it will break the OS anyway, so don't do that.
If you want the update, since these phones are old, chances are there is a TWRP version of the update already... and/or a KDZ. Either of those can be used as well. KDZ will wipe the phone, but TWRP can be "dirty flashed" over what you already have.
In order for anyone to help further, you'd have to tell us what you have to begin with.
As for disabling the notification, you can disable the updater app to stop this from popping up at all. This is detailed in many places as well.., and, again, requires us to know what you're running now.
Thanks for the info, mine is a Stock H930DS using the lastest stock Android 9 for Australia.
I'm not that fussed about the update itself, which I believe to be a minor security patch. Disabling the updater would be great.
I have the unlocked bootloader and TWRP installed, but not magisk, I imagine I could install that again via TWRP, but wanted to get back to as original as possible.