Related
Hi!
As Wileyfox issued another OTA today and the last time I had a hard time to find the proper information, I thought I'd start a thread that contains the update information and links for ALL OTAs in one place right at the start.
But first of all: This would not be possible without linuxct and mdosch who delivered this information in a combined effort. I added only a few things, like the new updates and put everything in one place.
1. The official update links from Wileyfox (partially from here, here and myself):
TOS118C (Recovery Image)
TOS163B (Recovery Image) Deleted by Wileyfox
TOS208G (Recovery Image) Deleted by Wileyfox
TOS249H (Recovery Image)
TOS319I (Recovery Image) Deleted by Wileyfox
TOS373J missing
UOS224B missing
UOS273C (Recovery Image)
TOS118C (Fastboot Image) Deleted by Wileyfox
TOS163B (Fastboot Image) Deleted by Wileyfox
TOS208G (Fastboot Image) Deleted by Wileyfox
TOS249H (Fastboot Image)
TOS319I (Fastboot Image)
TOS373J (Fastboot Image)
UOS224B missing
UOS273C missing
TOS089A to TOS118C (OTA Update)
TOS118C to TOS163B (OTA Update)
TOS163B to TOS208G (OTA Update)
TOS208G to TOS249H (OTA Update)
TOS249H to TOS319I (OTA Update)
TOS319I to TOS373J (OTA Update)
TOS373J to UOS224B (OTA Update to OREO 1)
UOS224B to UOS273C (OTA Update)
TOS373J to UOS273C (OTA Update to OREO 2)
2. The instructions how to make the OTA links work (taken from here):
If you directly click it, it will return an Error 404, but that is not true since the file actually exists... But requires a special HTTP header to be visible. Since I wanted to grab the OTA link now that, for once, I finally got an OTA in this phone after always upgrading through fastboot images, I used wireshark to determine the server where it fetches it and the full file route. It turns out the header sends a special UA string as you can see in the picture attached: rsotaua 1.0, which is, most probably, a randomly generated string. Now here's the thing: if you want to switch the UA you'll need an extension to do so. linuxct has used this one and on Firefox I used this one. As soon as it's installed, go to the Options of the extension and add it like here:
Code:
WILEYFOX rsotaua 1.0 Chrome Replace WF
Once the string is inserted, switch to it and hit the URL. The OTA should be downloadable now.
As I just found out: The "User Agent Switcher" for Chrome works just as fine.
3. The instructions how to update a rooted phone (taken from here):
I'll write down what I did to get it finally work, but be aware you might brick your phone. I did this with Windows 7 and 10 successfully with fastboot and adb installed.
3.1. Download and unzip the fastboot image from point 1. Then switch to fastboot mode and flash boot, recovery and system.
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
3.2. Boot to stock recovery and choose "apply update from adb". Then sideload the update.
Code:
adb sideload wf-marmite-aa4d5d86bc-to-8eec3af77b-signed.zip
This is, of course, an EXAMPLE! You have to put in the name of the actual update you want to do.
3.3. After successful install wipe cache and dalvik/arts cache and reboot to system. If you have issues with "dm verity" do it with the following command (I myself didn't need to do it):
Code:
adb reboot "dm-verity enforcing"
3.4. When the update is configured let the phone switched on for a while (I don't know why, but mdosch ended in a bootloop and had to start again when he instantly rebooted, I myself didn't need to wait). Here you can already put the SuperUser ZIP-file onto your phone via USB (or do it later via sideload).
3.5. Then boot to bootloader and BOOT (not flash) TWRP
Code:
fastboot boot twrp-3.1.1-0-marmite.img
3.6. If you have the SuperUser ZIP-file already on the phone flash it, otherwise go to "ADB -> Sideload" and install there
Code:
adb sideload superuser.zip
3.7. Wipe cache and dalvik/arts cache and finally reboot. Again, if you have issues with "dm verity" do it with the following command (I myself didn't need to do it)::
Code:
adb reboot "dm-verity enforcing"
This is how it worked for me in Windows 7 and 10 on my Wileyfox Swift 2 Plus. Neither did I brick my phone, nor did I loose ANY(!) data, neither from storage nor from any app. But as I don't know what you did with yours I won't issue any warranties here...
BTW: If you ever wondered, when you do the OTA the phone saves the zip here: data/data/com.android.providers.downloads/cache
So, linuxct and mdosch thank you very much again and I hope you don't mind about what I did with your input. :fingers-crossed:
And also thanks to image45 and DIMICH666 for getting hold of some more of the image links.
Thanks, wish I had found this 2 hours earlier! I had been downloading the OTA update but it was failing to install. Spent ages searching my phone for the location of the download without success. Eventually connected my phone to my laptop and did 'adb logcat' - found the URL of the OTA File download "http:\/\/ota-files.wf.bsp.ninja\/marmite\/wf-marmite-8eec3af77b-to-0fcf4099d0-signed.zip". Changed 'User Agent' as described, put the URL in the address bar and hit enter and hey presto! Good to have a repository to refer to.
Hi
I'm already on TOS163B. Can I just sideload the TOS208G OTA zip? Without reflashing the boot, recovery and system images from TOS163B?
The images from TOS208G are not available.?
Thanks for this.
I managed to grab the TOD208G OTA. Flashing the zip in TWRP did not work though. I got an unexpected fingerprint error (6.0.1 instead of 7.1.2). I flashed the last available debloater on TOS163B (which worked fine), but that probably has got me in trouble now. Is there any way to fix this easily, without having to root and remove all the debloat stuff manually?
(... I dream about Lineage 14.1)
H2Oxide said:
Thanks for this.
(... I dream about Lineage 14.1)
Click to expand...
Click to collapse
We all do, I tried an unofficial build however no WiFi yet :crying:
Even with an official build we would still have the unlocked bootloader warning screen and the dm-verity screen that threatens to switch your phone off in 30 seconds if power not pressed. I am sure it only gave you 5 seconds then just continue to boot when running on the Cyanogen ROMs
I am sure there is some ADB the resolve this for the oneplusone phones.
After initial boot the ROM got stuck on the white splash screen. After I installed Magisk via TWRP flashable zip it worked so must need dm-verity switch off.
I never updated back at the end of 2016 because I was unsure if it was a good idea but now I've become annoyed by it constantly asking me to (OTA UK). Should I update to cm-marmite 460.6 MB like it's asking me to? And then I suppose it will pick up and ask me to install the updates since? Thanks.
quixoticduck said:
Should I update to cm-marmite 460.6 MB like it's asking me to? And then I suppose it will pick up and ask me to install the updates since? Thanks.
Click to expand...
Click to collapse
It needs to be what you want, I flashed the cm-13.1.4-ZNH2KAS5RM-marmite-signed-5175bd793a.zip then removed the cm updater to stop it prompting me to move to the next update as it would eventually have you on current build if you accept all the updates.
I flashed cm-13.1.4 as I found it the most stable Cyanogen Marshmallow 6.0.1 ROM and I wanted xposed framework.
However like I said at start of post what do you need from your phone/ android version?
image45 said:
It needs to be what you want, I flashed the cm-13.1.4-ZNH2KAS5RM-marmite-signed-5175bd793a.zip then removed the cm updater to stop it prompting me to move to the next update as it would eventually have you on current build if you accept all the updates.
I flashed cm-13.1.4 as I found it the most stable Cyanogen Marshmallow 6.0.1 ROM and I wanted xposed framework.
Click to expand...
Click to collapse
Thanks, I see what you mean, about it being personal preference. The last couple years I've stepped away from rooting and flashing roms, so right now I suppose all I really want is a stable safe version. Back in 2016 I remember people being worried about the OTA update released right after Cyanogenmod's end, with people thinking the new update might be suspicious (why I never updated, and then stopped following things). So if it turned out that the OTA update was fine then I suppose the easiest and safest way to stop it bugging me about the update might just be to update xD as long as there's no risks (besides the basic risk that any update could bring). Probably makes it easier for any further updates too if any appear.
I hadn't heard of the xposed framework, sounds interesting, I'll look into that just in case I want to use it.
quixoticduck said:
I hadn't heard of the xposed framework, sounds interesting, I'll look into that just in case I want to use it.
Click to expand...
Click to collapse
You need an unlocked bootloader and custom recovery to install xposed framework. However I can jump between any of the Swift 2 ROMs when ever I wish of course.
Currently on the update right before that one, with TWRP and Magisk installed. I found the zip as instructed. Has anybody had success with Flashfire for a small OTA update like this or do you absolutely have to use adb sideload?
Don't know whether I can post links to other sites but there are instruction on how to update to 7.1.2 using the OTA file for both rooted and non-rooted devices at
http://www.stechguide.com/install-android-7-1-2-nougat-on-wileyfox-swift-2/
H2Oxide said:
Thanks for this.
I managed to grab the TOD208G OTA. Flashing the zip in TWRP did not work though. I got an unexpected fingerprint error (6.0.1 instead of 7.1.2). I flashed the last available debloater on TOS163B (which worked fine), but that probably has got me in trouble now. Is there any way to fix this easily, without having to root and remove all the debloat stuff manually?
Click to expand...
Click to collapse
Any thoughts on this? Can I force a sideload or would that be unwise...
der_dkw said:
So, linuxct and mdosch thank you very much again and I hope you don't mind about what I did with your input. :fingers-crossed:
Click to expand...
Click to collapse
Sure that's fine.
I really appreciate you collected all the information and created this overview.
Well I finally managed to try the adb sideload and this is what I got.
What's wrong here?
I'm using TOS163B (7.1.2) so I don't know why it says I have 6.0.1 test keys. I'm trying to sideload TOS208G
Any help is much appreciated
Jack3volution said:
What's wrong here?
Click to expand...
Click to collapse
You are using TWRP not stock recovery.
The OTA zips check your device for not being altered (like rooting or using custom recovery) this is why you have to go to a plain stock rom while flashing boot, recovery and system from the fastboot image (not the complete image as it will erase your data as well I assume).
After you have done this boot to stock recovery and adb sideload the first OTA zip then reboot and so on until you are on the latest.
Then you can boot twrp (I recommend booting instead of flashing as for me it complained about my device being altered when I flashed twrp) and root again (as root was lost during this update process).
Thanks! my mistake. Yeah I still have stock recovery
Cheers
mdosch said:
Then you can boot twrp (I recommend booting instead of flashing as for me it complained about my device being altered when I flashed twrp) and root again (as root was lost during this update process).
Click to expand...
Click to collapse
What's the actual different between booting TWRP and flashing please?
image45 said:
What's the actual different between booting TWRP and flashing please?
Click to expand...
Click to collapse
Booting means you boot TWRP temporarily without replacing your stock recovery. Flashing means you replace the stock recovery with TWRP.
mdosch said:
You are using TWRP not stock recovery.
Click to expand...
Click to collapse
Hmm it didn't work in stock recovery either
Jack3volution said:
Hmm it didn't work in stock recovery either
Click to expand...
Click to collapse
Did you apply the OTA zips in the correct order?
Did you alter your devices in any way like rooting or installing magisk?
You are on TOS163B you said. Did you start your device before booting to recovery? For me after sideloading the TOS163B, sideloading of TOS208G failed when I tried to install it instantly so I cleared the cache/dalvik cache booted to Android, then rebooted to (stock) recovery again and successfully sideloaded TOS208G.
Got a second Redmi 7A, I'm 99.99% certain it came with *global* 10.2.5 PCMMIXM (it was what ordered, and saw it too, pretty certain), decided to let it upgrade OTA, it picked 11.0.6 OTA, and it came to:
MIUI Global 11.0.6 PCMEUXM (notice the EU there), which, I'm assuming from this url: https://mirom.ezbox.idv.tw/en/phone/pine/
to be this one:
Code:
Redmi 7A – EEA Stable ROM
Lstest V11.0.6.0.PCMEUXM(History)
MIUI 11
Android 9.0
Update at 2019-10-31 19:05:57
Changelog Expand Official Link
Recovery miui_PINEEEAGlobal_V11.0.6.0.PCMEUXM_bcc90ca1df_9.0.zip
Filesize 1.5G
MD5 bcc90ca1df89a4f3d8cc7b9705a70d83
which is a bit confusing, it says Global, but has "EU" in the name.. in any event, flashed TWRP as per:
https://xiaomifirmware.com/guides-and-tips/how-to-install-twrp-and-magisk-root-on-redmi-7a/
choose the LRTeam version:
Code:
2a3296af05267160cba2891bff446203 TWRP-3.3.1-1003-REDMI7A-CN-wzsx150.img
seemed newest, all is great, it boots into TWRP recovery.. Next, trying to get Magisk on it, got the manager apk installed 7.4 all fine, it says 20.1 needs to be installed so...
unzipped the boot.img from above zip file, it has this md5, this is original , unmodified boot.img:
Code:
036d1b6c5a99e9417f8d3e98d5718368 boot_Global_V1106PCMEUXM.img
following this guide: https://romprovider.com/2019/01/create-pre-rooted-patched-boot-img-magisk/
Magisk successfully patched the boot.img on the same phone (running 11.0.6) and got this file:
Code:
dad219422c9302a460d4d2370adafb4f magisk_patched_Global_V1106PCMEUXM.img
transferred to PC, attempted to flash:
Code:
c:\XiaomiADB\bin>fastboot flash boot magisk_patched_Global_V1106PCMEUXM.img
target reported max download size of 535822336 bytes
sending 'boot' (14914 KB)...
OKAY [ 0.470s]
writing 'boot'...
OKAY [ 0.190s]
finished. total time: 0.665s
c:\XiaomiADB\bin>fastboot reboot
rebooting...
finished. total time: 0.003s
Phone boots fine, however, magisk still says it needs to be installed...
in developer's options, the USB debugging is enabled, and boot loader is definitely unlocked, it says on splash screen and the OEM Unlocking is greyed out and says "bootloader already unlocked".
Also, attempted to flash boot image from within TWRP, selecting the above boot.img file and selecting the boot partition, flashes OK, however, after normal reboot, as if nothing happened, phone boots, but magisk is NOT installed (no root).
Is there anything missing in these steps? does anyone have a correctly patched 11.0.6 image with magisk in it from an 7A phone?
Only thing that appears as an "error" are these family of cmds to unlock boot loader:
Code:
fastboot oem unlock
...
FAILED (remote: Token verification failed, reboot the device)
finished. total time: 0.004s
however, i think that is normal/expected, since the bootloader is already unlocked.. able to flash twrp, etc.
Thanks so much for any ideas...
Stormy.
Forgot to mention that attempted to install Magisk 20.1 zip file downloaded by the app, from within TWRP, attached screenshot of how that looks like all seems okay but after reboot it still says that magisk needs to be installed... Very strange..
Appreciate any thoughts..
Stormy
noticed in above screenshot that it detected a patched boot image so decided to try installing the
v20.1 Magiskk zip file with the stock Boot, the install results in a screenshot, after reboot it still says that magisk has to be installed.!
also attaching screenshots showing the device is unlocked as well as USB debugging and OEM unlocking are all there.
Should this be posted in The magisk forum or is this something specific to the 7A? Or my steps?
How to debug further?
Attempted with the other TWRP image TWRP_v3.3.1-1_all.img, same results also reinstall the magisk manager 7.4 and same results....hmm.. maybe the OTA update took wrong ROM version. (EU and not pure Global)?...
Digging a bit more, found this pretty cool tool: https://www.xiaomitool.com/V2/latest called: "XiaoMiTool V2 ", which basically automated (almost) Everything !! Tried to do TWRP, as well as Magisk, it too followed similar steps I did, all automatically, rebooting, patching, etc. but outcome is still same, when phone boots normally, Magisk Manager says that Magisk 20.1 needs to be installed...
Then tried to flush miui_PINEGlobal_V11.0.4.0.PCMMIXM_674ed79f0b_9.0.zip using that tool, it said all is OK, phone rebooted , wiped all, but it still runs the EU version for some reason.. Now trying to find the path to "downgrade" from 11.0.6 to 11.0.4, or switch from EU to Global.. maybe that's the source of all issues, not sure what else to try
Reporting progress, to keep track of what was attempted. So, decided to WIPE all and start with 11.0.4 Global fresh, from TWRP, wiped everything, to the point it said "no OS installed, are you sure u want to reboot" it rebooted into fastboot, then downloaded the 11.0.4 Global .tgz and flashed, phone booted OK this time into 11.0.4 Flashed TWRP, and then attempted to flash Magisk via both routes, one by patching the boot.img from the .tgz and flashing, all using the Phone (to avoid any PC/driver/adb issues). The flashing worked fine, but upon reboot, Magisk Manager claimed that Magisk is not installed. Second try was to flash the stock boot.img, then flash magisk zip file, did that for v20.1, v19.4 and 19.3, each time from stock boot.img, and reboots to test, none of them showed that magisk is installed...
all this time, usb debugging is enabled despite most work done on the actual redmi 7A phone itself.
Then uninstalled magisk manager 7.4, and tried with 7.2, but that doesn't change much since any action there wants to update to v7.4..
next step will wipe again, and go for the Global 10.2.5... if that doesn't work then I really don't know what can be going on...
If anyone does have a 7A with MIUI 11 with a properly patched boot.img, would love to try it... all my patching attempted booted fine, but none showed that Magisk is installed... finding it hard to think it's a magisk bug, more likely some MIUI 11, lets see how 10 works out...
Stormy
OK, some success! so, wiped ALL again, to the point of no-OS installed; phone only boots into fastboot (brick), using flash_all.sh from 10.2.5 fastboot Global ROM flashed entire phone and it booted OK.
btw, not easy to find 10.2.5 now, as places already updated links to 11.0.x..
Once in 10.2.5, tried to patch Magisk in all possible ways (twrp or patching boot.img on phone the flashing from Windows10/PC) as also described in this thread few weeks ago:
https://forum.xda-developers.com/showpost.php?p=80498891&postcount=179
but it did NOT work, well, the procedure appeared OK, no errors and when booting, it says magisk needs to be installed.
The only thing that works is the provided boot global .img file [size 14.5 MB (15,269,888 bytes)], as soon as this one is flashed, via phone/twrp or PC, then the magisk is correctly detected.
Very mysterious, why only that boot.img is working on my 7A phones.. maybe there's an additional step, to "sign" or fix the boot.img before it can be flashed?
now took a full TWRP backup, and will try to move to 11.0.4 see if magisk is retained, and if not, if possible to re-gain it.. if not, then, will restore from TWRP backup.
Any thoughts welcomed..
Stormy.
Did not manage to get it working with MIUI 11 yet, so backed to MIUI 10.2.5.. all is fine there.
Noticed that TWRP did not "stick", flash but after normal boot, it came back to original recovery. I think this is b/c of Verify Boot in android Pie/9.. so I *think* what helped here is to flash a vbmeta.img from first post of this thread:
https://forum.xda-developers.com/redmi-7a/how-to/custom-gsi-firmware-t3965820
Even after flashing this, and even in 10.2.5, patching the STOCK 10.2.5 from the phone using Magisk 20.1 and installing using TWRP did not work, not sure if this is a bug in magisk or what, but only way to get root was using the provided boot.img as described above. I'll keep using 10.2.5 for now. feel free to add any ideas here , maybe one day will get more time and a spare phone to try MIUI 11
Stormy.
hey , I have the same problem. I noticed you mentioned 'sign', what should I sign what things? and how to sign?
I was going to ask for the same thing : is there any method to root Redmi 7A under MIUI 11?
For my case :
-I can flash and boot to TWRP,
-I can 'flash' (install) Magisk through TWRP,
-However : this has no effect. Still Magisk Manager tells me that Magisk was not found!
The Redmi is unlocked and I can install custom roms (Mokee, LineageOS...). I see no reason why the phone can't be rooted it's probably just some bad configuration.
Thank you very much
depaul9999 said:
I was going to ask for the same thing : is there any method to root Redmi 7A under MIUI 11?
For my case :
-I can flash and boot to TWRP,
-I can 'flash' (install) Magisk through TWRP,
-However : this has no effect. Still Magisk Manager tells me that Magisk was not found!
The Redmi is unlocked and I can install custom roms (Mokee, LineageOS...). I see no reason why the phone can't be rooted it's probably just some bad configuration.
Thank you very much
Click to expand...
Click to collapse
Don't bother rooting Redmi 7A, it just isn't possible, not even with the miui 10 (I've tried). There's no way to flash magisk successfuly, because when you do, magisk is still uninstalled, therefore no root and if you try SU instead, it happens some kind of error. If you try magisk without TWRP and flash a patched recovery it still doesn't work either. Since I can only follow tutorials because I understand nothing about Android I can say that there is no tutorial out there that works and all of them are wrong. I just don't understand why people bother to make tutorials that do not work just to make people waste their time.
KnowTheyself said:
Don't bother rooting Redmi 7A, it just isn't possible.
Click to expand...
Click to collapse
Thanks indeed that's the case for the moment. Hopefully we could soon manage to root the phone successfully.
My biggest motive is to install App2SD and move games to external storage, since with my 16GB version I can barely install one or two games and MIUI only allows installation to internal. (I know I should've bought a phone with bigger storage).
depaul9999 said:
Thanks indeed that's the case for the moment. Hopefully we could soon manage to root the phone successfully.
My biggest motive is to install App2SD and move games to external storage, since with my 16GB version I can barely install one or two games and MIUI only allows installation to internal. (I know I should've bought a phone with bigger storage).
Click to expand...
Click to collapse
I've read that the 16GB version of the Redmi 7A is possible to put a micro SD card and format it as internal storage and that was the reason I've bought it, although I'm not yet sure because I'm waiting to buy a microSD card, it's still on the way.
I want to root it because of privacy reasons and that's the only reason. For now I'm using a VPN to block 99% of the google and xiaomi apps, etc. to the internet this way I got some privacy. I have unlocked the phone too so I did uninstalled several apps from the system using the PC.
KnowTheyself said:
Don't bother rooting Redmi 7A, it just isn't possible, not even with the miui 10 (I've tried). There's no way to flash magisk successfuly, because when you do, magisk is still uninstalled, therefore no root and if you try SU instead, it happens some kind of error. If you try magisk without TWRP and flash a patched recovery it still doesn't work either. Since I can only follow tutorials because I understand nothing about Android I can say that there is no tutorial out there that works and all of them are wrong. I just don't understand why people bother to make tutorials that do not work just to make people waste their time.
Click to expand...
Click to collapse
I don't think that's correct.. I've rooted several 7A, as many others on the forum, just look around, all these posts, many HAVE done based on the topics...
There are few more mysteries, even to experts, so don't feel bad (like how to path boot.img from Magisk, did it for other phones, but not possible for this one for some reason).. agree, there is no current/updated guide that works for everyone, but one can piece things together..
The reason there is no complete guide is not b/c people want to waste your time, they are really trying to SAVE time, however, there are many FACTORS at play, like initial ROM/state of the phone, some Global, some EU, some 10.x other 11.x and so forth, which change over time...
Once the bootloader is unlocked, then one should be able to:
- flash vbmeta.img
- flash twrp (I'm using 3.3.1-1003 'wzsx150').
boot into twrp and flash a properly patched boot.img (that matches your phone), now that's the tricky part, b/c one cannot be re-generated, u'd have to dig through some of the posts, like this: https://forum.xda-developers.com/redmi-7a/how-to/custom-gsi-firmware-t3965820 and find the boot.img that works, it had magisk 19.3 in it, but then update is easily possible.
it's important to flash vbmeta otherwise the "verified boot" will revert things back to a "working state", and you'll lose twrp..
Once my phone got to MIUI 11 it was not possible to root (since there is no boot.img that's patches correctly, and i couldn't do it), so i've flashed the whole phone back to 10.2.5 and from there rooting was pretty easy, the trick is to find the right boot.img.
Good luck.
stormy1777 said:
I don't think that's correct.. I've rooted several 7A, as many others on the forum, just look around, all these posts, many HAVE done based on the topics...
There are few more mysteries, even to experts, so don't feel bad (like how to path boot.img from Magisk, did it for other phones, but not possible for this one for some reason).. agree, there is no current/updated guide that works for everyone, but one can piece things together..
The reason there is no complete guide is not b/c people want to waste your time, they are really trying to SAVE time, however, there are many FACTORS at play, like initial ROM/state of the phone, some Global, some EU, some 10.x other 11.x and so forth, which change over time...
Once the bootloader is unlocked, then one should be able to:
- flash vbmeta.img
- flash twrp (I'm using 3.3.1-1003 'wzsx150').
boot into twrp and flash a properly patched boot.img (that matches your phone), now that's the tricky part, b/c one cannot be re-generated, u'd have to dig through some of the posts, like this: https://forum.xda-developers.com/redmi-7a/how-to/custom-gsi-firmware-t3965820 and find the boot.img that works, it had magisk 19.3 in it, but then update is easily possible.
it's important to flash vbmeta otherwise the "verified boot" will revert things back to a "working state", and you'll lose twrp..
Once my phone got to MIUI 11 it was not possible to root (since there is no boot.img that's patches correctly, and i couldn't do it), so i've flashed the whole phone back to 10.2.5 and from there rooting was pretty easy, the trick is to find the right boot.img.
Good luck.
Click to expand...
Click to collapse
Well, if you say so... If you're right then I got the wrong Redmi 7A model. It came with the EU version of the miui.
I already knew the tutorial in the link you gave, but that seems very complicated and I do not really know what's going on there so it's better I do not try it. And if I followed that tutorial I would have to flash the phone again with the miui 10, because I have the 11 now. I already wasted many hours trying to root the phone and I had to flash the rom about 4 times because the phone became bricked. Anyway the tutorials I've followed were not the one in the link above and all the other ones I've tried did not work and yet they claim it does, specially using magisk only, without TWRP.
I'll wait for an easier method than the one you shared, if that will ever happen. For now I just use a VPN, it's the closest thing to root I have found, to deny system and apps permission to the internet.
Thank you
In case you're not aware, there are scripts to flash the entire phone automatically, I've done that 10's of times BEFORE putting the phone into "production" use, root was a _must-have_,phone's now heavily used, so can't toy with it much, unless forced to (see below), i may get another phone to play with, but not much TIME to justify it...
Was getting tired of typing:
Code:
:/ # pm list packages|grep xyz
followed by:
:/ # pm uninstall -k --user 0 com.google.android.apps.tachyon
Success
Decided to give some "highly-rated" app a try, it claims to be able to remove system apps: "System app remover (root needed)":
https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp&hl=en_US
Took a full TWRP backup, installed, all seems great.. remove, goes to recycle bin, ok.. now, lets REBOOT..
Opps.. phones goes into FASTBOOT... OK!! that's what the backup is for.. go into TWRP, flush SYSTEM, CACHE, DATA, reboot, again, we're in Fastboot, and this time no RECOVERY boot is possible, just goes into FASTBOOT directly.. much like i've described in this thread:
https://forum.xda-developers.com/showpost.php?p=80509823&postcount=111
so, TWRP on phone doesn't help much, took the TWRP backup from SD Card to PC (since phone can only do fastboot at this point), thought it would be easy/possible to fastboot flash all the TWRP into the phone from PC, however, that is NOT simple, since TWRP breaks files, one must concatenate them before flashing..
I was not in the mood, nor did i think a huge change took place, it was just something silly that app did. hmm.. here, i can't exactly explain what took place, but a sequence of flashing of boot.img recovery.img and vbmeta.img all from STOCK and the TWRP backup, was "all it took" to recover the phone fully..
After about 30+ flashes and reboots it came to life much like the last boot, went into that APP again, tried to RESTORE the apps, it failed, and a reboot again, went into FASTBOOT! twrp was there, again, tried recovery, this time only SYSTEM, again, phone lost recovery, and went into, fastboot only... and.. again, sequence of flashing from fastboot, i can tell that vbmeta (Verify Boot) takes a *major* role in this version/device, if something is not right, it just reverts things or decides to go into fastboot.
I saw it work once, so was not going to give up and wipe/start fresh.. kept trying..
I think the app somehow made "direct" modifications to the system partition without proper interface, and thus ruined the "signature" or encryption, otherwise not sure how it could trash the phone so badly..
in any event, after long struggles, flashing the LATEST did _not_ work, it's almost as if the phone had to be taken back to original setting, let it boot into recovery, then reboot again, and flash things in steps, not all at once, at least based on this experience. I know it's silly, b/c in Android 6 I've restored/cloned phones all the time using TWRP directly from phone.. not sure, it does not work on my 7A's...
eventually, phone booted, with 10.2.5 magisk/boot.img (no root, since it did not recognize magisk), then fastboot flashed the canary boot.img, and got root.
anyways, point is, it was pretty ugly, and I'm not complaining, just saying this is pretty complicated stuff, it's a miracle that this even works
keep up the great work everyone, if i can help in any way, let me know...
All this is on Global phone, I don't have an EU/ROM/phone, so can't help u directly, but someone may have a root boot.img EU boot, that's really the key, and the vbmeta.img of course as for MIUI11? so what if that's what you have, it can be flashed, it's a matter of choice, flash to miui 10.2.5 and get root, or try to do it on MIUI11, or, let it be and use w/o root.. which was not an option for me
good luck.
Stormy.
btw, the magisk/patching boot.img did not work for me, and was reported in that same thread:
https://forum.xda-developers.com/showpost.php?p=80560039&postcount=206
MDV106 said that both EU and global boot.img were posted in that thread, and i agree i used one of them, not sure exactly which, but definitely it was the Global, not the EU. and i think it's not goot to mix up.. if u have an EU, stick with it, it might impact Wifi or similar "regional" things..
Same problem, but it works on mokee
Add-on-su on mokee open source ROM works fine, can enable root from developer options only, magisk and supersu don't work.
I have been trying to make them work but it seems impossible, I have looked in system/xbin and found no su files, maybe the problem is in the meta-INF because it doesn't properly know where to install it.
boody shaban said:
Add-on-su on mokee open source ROM works fine, can enable root from developer options only, magisk and supersu don't work.
I have been trying to make them work but it seems impossible, I have looked in system/xbin and found no su files, maybe the problem is in the meta-INF because it doesn't properly know where to install it.
Click to expand...
Click to collapse
Thanks for this data point, yeah, root was/is also possible with MIUI 10.2.5, I'm sure other ROMs can root pretty easily.. the "goal" of this thread is to somehow figure how to do it on MIUI 11 so we can take the security updates and still retain rootness
working root redmi 7a
Working root for Redmi 7a
thank you stormy1777 - it is your tutorial, I only put it together. It is the only tutorial that works
links unavailable due to site rules:
google for: ROM v10.2.5. global V10.2.5.0.PCMMIXM/pine_global_images_V10.2.5.0.PCMMIXM_20190805.0000.00_9.0_global_efb78ff9c3.tgz
google for: patched boot v10.2.5. under: xiaomifirmware (dot) com how-to-install-twrp-and-magisk-root-on-redmi-7a
google for: TWRP: under: androidweblog(dot)com xiaomi-redmi-7a-root-install-twrp-recovery I took the version 3.3.1.-0
google for Magisk: Magisk-v20.1.zip
Install in fastboot mode and with Mi Flash Tool
flash: pine_global_images_V10.2.5.0.PCMMIXM_20190805.0000.00_9.0_global
option: clean all
wait until the mobile phone is fully installed (will reboot automatically)
copy Magisk into the root directory on your phone
restart in fastboot mode (volume down + power button)
on PC:
rename twrp file to recovery.img
rename boot file to boot.img
copy boot.img and recovery.img on the PC in the directory, where adb drivers are
open power shell on the PC in the directory, where adb drivers are
type in the power shell window:
fastboot flash recovery recovery.img
Enter
then type in the power shell window
fastboot flash boot boot.img
Enter
then hold volume up + power button until it 2x starts and vibrates, then wait, it opens in TWRP
type install, find Magisk.zip in the phone root directory a flash
restart into system
done
Hi,
quick files that many of us waiting for
OnePlus 8T, 11.0.1.2 KB05BA KB2003
Newest (20.10.2020) OTA:
https://drive.google.com/file/d/1uKV_j8yIQLPeIRJkf1KIUlJcIaH8BppR/view?usp=sharing
boot.img (stock)
https://drive.google.com/file/d/12VopoB984YmJHUJuqMBA4jyID1Sp_sPQ/view?usp=sharing
boot.img (patched, checked, working)
https://drive.google.com/file/d/1V4esvmJCBkwskq2shfWcylPL53h4dd_2/view?usp=sharing
=======================================
You like it?
paypal.me/widmak
=======================================
Thanks!
Thanks. But where's the guide or howto, that the title says ?
I flashed your patched boot image, but no Magisk is detected in either stable or canary Magisk Manager. There might be an issue.
EDIT: Confirmed that the issue is on your end. Patched the image myself and flashed it, with Magisk being detected by Magisk Manager.
https://drive.google.com/file/d/1yw5Fwgy0_ArPD_itnZ66nmdWA2NapFPg/view
This boot image works.
Any idea to flash the EU rom from India?
felata said:
Any idea to flash the EU rom from India?
Click to expand...
Click to collapse
Download the full OTA zip, keep it in internal storage outside any folders.
Go to System -> System Updates
Click the gear icon, select local upgrade
Then, select the downloaded Full OTA zip.
Install and reboot.
Done.
theincognito said:
Download the full OTA zip, keep it in internal storage outside any folders.
Go to System -> System Updates
Click the gear icon, select local upgrade
Then, select the downloaded Full OTA zip.
Install and reboot.
Done.
Click to expand...
Click to collapse
The system says that it won't allow downgrade
Which magisk did you use please?
Alvincyq said:
The system says that it won't allow downgrade
Click to expand...
Click to collapse
If you updated to the Indian/Global 11.0.1.2 before doing this, you only have 2 options:
1. Wait for the next OOS update, but when the Indian/Global update comes, don't update.
Instead, wait for the full update zip of the EU to be available, and then follow the steps in the previous comment.
2. Unlock bootloader, flash the full OTA zip of any variant via fastboot, and relock the bootloader.
elliottweaver said:
I flashed your patched boot image, but no Magisk is detected in either stable or canary Magisk Manager. There might be an issue.
EDIT: Confirmed that the issue is on your end. Patched the image myself and flashed it, with Magisk being detected by Magisk Manager.
https://drive.google.com/file/d/1yw5Fwgy0_ArPD_itnZ66nmdWA2NapFPg/view
This boot image works.
Click to expand...
Click to collapse
Your file did not work for me but i modified the stock file from the first post myself and that worked. i guess there is something coded into the file by magisk that is depended on the phone.
theincognito said:
Download the full OTA zip, keep it in internal storage outside any folders.
Go to System -> System Updates
Click the gear icon, select local upgrade
Then, select the downloaded Full OTA zip.
Install and reboot.
Done.
Click to expand...
Click to collapse
I'm on Kb2005 and I'm only able to get an incremental update. Can I pull the bin file from that update
Was there an OTA specific to models outside of the U.S.? I see at least two variations are already getting an update but nothing is available yet for my US (KB2005) variant I got today.
MNoisy said:
Was there an OTA specific to models outside of the U.S.? I see at least two variations are already getting an update but nothing is available yet for my US (KB2005) variant I got today.
Click to expand...
Click to collapse
I have KB2005 as well. No updates for me. I tried to just boot the images posted in the other thread with no luck.
northmendo said:
I have KB2005 as well. No updates for me. I tried to just boot the images posted in the other thread with no luck.
Click to expand...
Click to collapse
Unless OnePlus is very different from the other major manufactures, you definitely do not want to use a patched boot image from a different model variation of software/firmware. At best it will cause major issues.. At worst, it will brick it.
If Oneplus is different, I would love some feedback on why and what they do from other users.
MNoisy said:
Unless OnePlus is very different from the other major manufactures, you definitely do not want to use a patched boot image from a different model variation of software/firmware. At best it will cause major issues.. At worst, it will brick it.
If Oneplus is different, I would love some feedback on why and what they do from other users.
Click to expand...
Click to collapse
Correctish, you don't want to flash it. You can just boot the image. If successful it'll just boot the phone. If unsuccessful it will hang and you can just force reboot. No damage can because because it's not writing the boot image to the phones storage. Kinda like booting from a flash drive. The code is
Code:
fastboot boot /path/boot.img
If you boot a patched boot image you will have access to a rooted phone until you reboot. I.E. just enough time to flash magisk on the installed boot image.
Hope that makes sense.
northmendo said:
Correctish, you don't want to flash it. You can just boot the image. If successful it'll just boot the phone. If unsuccessful it will hang and you can just force reboot. No damage can because because it's not writing the boot image to the phones storage. Kinda like booting from a flash drive. The code is
Code:
fastboot boot /path/boot.img
If you boot a patched boot image you will have access to a rooted phone until you reboot. I.E. just enough time to flash magisk on the installed boot image.
Hope that makes sense.
Click to expand...
Click to collapse
I am familiar with how it works but with brands like HTC and Samsung, if we use a boot.img from a different variation, it will not work or even brick it. Thanks for the heads up! It sounds like there is more room for error for testing with OnePlus and modifying the system.
Can someone please provide a link to the Magisk Manager that 's working with this bootimage?
Edit: Found it, got root but it doesn't pass SafetyNet...
epr said:
Can someone please provide a link to the Magisk Manager that 's working with this bootimage?
Edit: Found it, got root but it doesn't pass SafetyNet...
Click to expand...
Click to collapse
Which one was it? My Magisk is not working either. I assumed it was because the kb2005 was only an incremental update. I have the canary version from github. Is there another for oneplus?
MNoisy said:
Which one was it? My Magisk is not working either. I assumed it was because the kb2005 was only an incremental update. I have the canary version from github. Is there another for oneplus?
Click to expand...
Click to collapse
Downloaded it from github: https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/app-debug.apk
epr said:
Downloaded it from github: https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/app-debug.apk
Click to expand...
Click to collapse
Yeah, same one. And it worked on the incremental Ota for kb2005?
Do you mind posting the patched boot.img?
Thank you!
MNoisy said:
Yeah, same one. And it worked on the incremental Ota for kb2005?
Do you mind posting the patched boot.img?
Thank you!
Click to expand...
Click to collapse
Don't know for KB2005, mine is KB2003.
I used stock boot.img from OP and patched it myself, all already patched files didn't work.
Was running older version of Magisk+Manager all 100% fine, trying to update to the new Magisk v22 apk.
reading guide here: https://topjohnwu.github.io/Magisk/install.html
it seems the device does NOT have a randisk (says NO), which means, one takes the *recovery* path (in the steps)
I have the TWRP recovery image used, and patched it using the Magisk that was on the phone, selected 'recovery method', selected the file, and it wrote:
/sdcard/Download/magisk_patched_f7KJH.img
Click to expand...
Click to collapse
so, pulled the file to PC:
adb pull /sdcard/Download/magisk_patched_f7KJH.img
Click to expand...
Click to collapse
then rebooted into FASTBOOT mode, and flashed that recovery image using:
fastboot flash recovery magisk_patched_f7KJH.img
Sending 'recovery' (65536 KB) OKAY [ 2.079s]
Writing 'recovery' OKAY [ 5.316s]
Finished. Total time: 7.408s
Click to expand...
Click to collapse
However, phone boots showing magisk is not installed, well, there is an icon Magisk, but it says v22 needs to be installed, but using that install button does not work, it appears to succeed, but doesn't do anything
Read on that page above , that one can RENAME the magisk v22 .apk to .zip, and FLASH the ZIP file from TWRP!!!
So, did that , renamed Magisk-22.0(22000).apk to .zip, when when booted into TWRP to flash this zip it says:
Checking for Digest file...
Zip file is corrupt!
Error installing zip file '/external_sd/Download/Magisk-22.0(22000).zip
Click to expand...
Click to collapse
So, it's a bit confusing.. Does anyone have steps for Redmi 7a? which does not appear to have ramdisk...
I thought it would imply be to patch the TWRP image file to using Magisk, then flashing the recovery image on to the recovery partition..
Corrections welcomed.
Stormy.
EDIT: ROM MIUI Global 10.2.5 | Stable 10.2.5.0 (PCMMIXM)
The error flashing comes from:
Installation
The Magic Mask for Android
topjohnwu.github.io
Download the Magisk APK
Rename the .apk file extension to .zip, for example: Magisk-v22.0.apk → Magisk-v22.0.zip. If you have trouble renaming the file extension (like on Windows), use a file manager on Android or the one included in TWRP to rename the file.
Flash the zip just like any other ordinary flashable zip.
Click to expand...
Click to collapse
Rename was easy, but flashing the zip from TWRP claimed it is corrupted. also read the "Magisk in recovery", however, trying this gets me to recovery mode (TWRP):
(Recovery Key Combo) → (Splash screen) → (Release all buttons) → (System with Magisk)
Click to expand...
Click to collapse
A bit confusing on how the new magisk works, the over-use of the term 'magisk' causes it to be incredibly hard to understand what is new/old/what/where/how things are laied out. Anythanks, thanks for any tips.
Stormy.
stormy1777 said:
Was running older version of Magisk+Manager all 100% fine, trying to update to the new Magisk v22 apk.
reading guide here: https://topjohnwu.github.io/Magisk/install.html
it seems the device does NOT have a randisk (says NO), which means, one takes the *recovery* path (in the steps)
I have the TWRP recovery image used, and patched it using the Magisk that was on the phone, selected 'recovery method', selected the file, and it wrote:
so, pulled the file to PC:
then rebooted into FASTBOOT mode, and flashed that recovery image using:
However, phone boots showing magisk is not installed, well, there is an icon Magisk, but it says v22 needs to be installed, but using that install button does not work, it appears to succeed, but doesn't do anything
Read on that page above , that one can RENAME the magisk v22 .apk to .zip, and FLASH the ZIP file from TWRP!!!
So, did that , renamed Magisk-22.0(22000).apk to .zip, when when booted into TWRP to flash this zip it says:
So, it's a bit confusing.. Does anyone have steps for Redmi 7a? which does not appear to have ramdisk...
I thought it would imply be to patch the TWRP image file to using Magisk, then flashing the recovery image on to the recovery partition..
Corrections welcomed.
Stormy.
EDIT: ROM MIUI Global 10.2.5 | Stable 10.2.5.0 (PCMMIXM)
Click to expand...
Click to collapse
You need to patch the file: boot.img
VD171 said:
You need to patch the file: boot.img
Click to expand...
Click to collapse
Why do you write that? Reading here:
Installation
The Magic Mask for Android
topjohnwu.github.io
says:
Patching ImagesIf your device has boot ramdisk, you need a copy of the boot.img
If your device does NOT have boot ramdisk, you need a copy of the recovery.img
Click to expand...
Click to collapse
The Redmi 7A says RAMDISK *NO* on the Magisk app, which reads to me as I have to patch the recovery.img, in my case recovery is TWRP, so that is the image I gave it.
Has anyone managed to get Magisk v22 on Redmi 7a? any steps? if not, may have to revert back to the prior set up which worked, until this is sorted out.
Thanks for any specific tips to devices withOUT ramdisk=yes, like Redmi 7A.
Stormy.
Yes, I read.
You can't patch TWRP using magisk.
If you want to apply magisk patched to the recovery, then patch the boot.img and then flash it to recovery.
You can ignore the info about ramdisk, just patch the stock boot.img and then flash it to the boot partition.
Good luck
Thanks, quick update from a "naive-end user" Before your second reply, re-read and noticed using the TWRP recovery image, and not the STOCK/ROM, so, pulled stock recovery.img, patched it, flashed to recovery partition.. all OK..
Now, on normal boot, no Magisk or root; on boot through recovery it goes into stock recovery, even leaving the up-vol key immediately when logo disappears does not do it, it simply boots normally without root/magisk installed
This is how easy one can take a perfectly working env to no root, no TWRP
Now, taking your advise and patch using magisk 22 the stock boot.img, here goes:
cksum:
Code:
4261103684 33554432 boot-stock1025.img
(after patching w/Magisk v22):
Code:
245310758 33554432 magisk_patched_U6lEU.img
flash in fastboot:
Code:
c:> fastboot flash boot magisk_patched_U6lEU.img
target reported max download size of 535822336 bytes
sending 'boot' (32768 KB)...
OKAY [ 1.034s]
writing 'boot'...
OKAY [ 0.886s]
finished. total time: 1.924s
it boots OK, but, magisk v22 says "no magisk installed"
I now recall that no matter which version of Magisk, the self-patching , i.e. on the actual device, NEVER WORKED, I've reported that many times in the past on this forum, but no clear answer. The only way I could root in the first place was to download an already patched boot.img that I use till yesterday.. that was posted on the forum here.
So, does anyone have a dump of boot.img patched to magisk v22 for Redmi 7A?
Or, alternatively, knows why patching of boot.img using v22 does not work?
Thanks.
Stormy.
Searching online, seems others w/Xiamoi devices having similar issues/confusions, this thread claims to RESOLVE:
Invalid - Magisk v22.0 issue [RESOLVED]
hi every one could anyone explain how we could update the latest magisk 22 because the magisk manager is no longer available....i turned the apk to zip file and it didnt want to be installed at all it gives you an error message THE DEVICE IS NOT BOOTING TO SYSTEM IT DIRECTS TO FASTBOOT....any...
xiaomi.eu
but does not say exactly HOW.. I've patched the Magisk uninstaller
https://github.com/topjohnwu/Magisk/releases/download/v21.4/Magisk-uninstaller-20210117.zip
so, no magisk at all, but when renaming magisk 22.img to magisk22.zip and trying to flash in TWRP, it says zip file is corrupted in red and flashing stops.
One more tip found these errors in the magisk patching log!!
Code:
Output file is written to
/storage/emulated/0/Download/magisk_patched_35S0f.img
****************************
cp: can't preserve ownership of 'busybox': Operation not permitted
cp: can't preserve ownership of 'magisk32': Operation not permitted
cp: can't preserve ownership of 'magisk64': Operation not permitted
cp: can't preserve ownership of 'magiskboot': Operation not permitted
cp: can't preserve ownership of 'magiskinit': Operation not permitted
- All done!
don't know how to resolve, found on:
Bootloop on Xiaomi Redmi 9 · Issue #3985 · topjohnwu/Magisk
Hi there, I'm trying to root my Redmi 9, alas it doesn't seem to be working. MIUI version: 12.0.1.0 (QJCEUXM) Android Version 10 QP1A.190711.020 I have unlocked the bootloader (open padlock icon on...
github.com
mention to flash *vbmeta*, so did that as well as patched v22 boot.img, and still it no root, magisk says it is not installed.
After full day downtime, and 50+ attempts most before posting, decided to revert back to Magisk v21.4/manager 8.0.7, installed riru/riru-edxposed within 5 minutes, phone is rooted all is fine. will re-try once someone announces success on Redmi 7A or someone provides a working pre-patched boot.img debug is also possible, more time for that path in 2 weeks.
Thanks Stormy.
@stormy1777
For the Redmi 7A you must have a patched boot.img to install Magisk with TWRP.
The problem is, the boot.img is a 32 bit img with a fake Ramdisk for a 64 bit processor.
Please look here: Install Magisk 22
MOFI69 said:
@stormy1777
For the Redmi 7A you must have a patched boot.img to install Magisk with TWRP.
The problem is, the boot.img is a 32 bit img with a fake Ramdisk for a 64 bit processor.
Please look here: Install Magisk 22
Click to expand...
Click to collapse
Incredible! If i read this right, you seem to say that Magisk can NOT patch the boot.img on the Redmi 7A due to the 32/64 bit issue relating to ramdisk?
I felt that all along, just couldn't prove it, used a pre-existing patched boot.img from day1, and never managed to patch directly on the phone Was that reported to Magisk team? or they can't fix it from a technical perspective?
will find the time (in few days) to play with this patching, if it works will post patched MIUI Global 10.2.5 | Stable 10.2.5.0 (PCMMIXM) image
Thanks.
Completely correct, Xiaomi installed a 32-bit operating system because the smartphone only has 2 GB of RAM. Not enough to work properly with a 64 bit operating system. Topjohnwu published the information on its Github page and criticized Xiaomi very much for this behavior. The original boot.img contains a ramdisk, but only as a placeholder, so when repackaging it is added with 0 MB to the boot.img. Therefore the image is smaller (approx. 15 MB) than the original.
Why don't you update to 12.xx.xx right away?
MOFI69 said:
Completely correct, Xiaomi installed a 32-bit operating system because the smartphone only has 2 GB of RAM. Not enough to work properly with a 64 bit operating system. Topjohnwu published the information on its Github page and criticized Xiaomi very much for this behavior. The original boot.img contains a ramdisk, but only as a placeholder, so when repackaging it is added with 0 MB to the boot.img. Therefore the image is smaller (approx. 15 MB) than the original.
Why don't you update to 12.xx.xx right away?
Click to expand...
Click to collapse
Dear Mofi69 in a small town by Berlin
Thank you SOOO much for such nice explanations, goes a long way to "trickle" down information to lowly people
Not moving to ROM 12, due to lack of time to "play with this", have several phones, and it would mean more time spent on it, for no "visible" significant benefit. I don't work for CIA or have anything secret, phone is not used in public places, mostly home, and wifi, so, security is not really an issue as they make it.. switching ROM sounds too many moving-parts and there are TONS of old apps that are already working, many not from app store we live with it fine. on a new phone, we'll upgrade, I'm certain ...
in next few days will try the magisk patching again (I was selecting "recovery" due to the ramdisk=no confusion), MAYBE they fixed it, and will produce a valid image, I can't think that the magisk binary would not have full control of their output, so as to make it exactly the right size/layout.. if it fails, will try the python patcher. Thanks so much for this info!!
Stormy.
stormy1777 said:
Dear Mofi69 in a small town by Berlin
Click to expand...
Click to collapse
Oh, oh, what kind of garbage did I write there, it comes from when you are not careful in English class ...
Only for you...
there is now the "OLD" boot.img, ready pached with the oss-patcher. Please install Magisk via TWRP (magisk.zip), boot.img from
miui_PINEGlobal_V10.2.5.0.PCMMIXM_7380681456_9.0
Important: I cannot test it! Please let me know if it works.
Best regards
Michael
Thanks friend for the help!!! Spent few more hours, eventually managed to get it, but not sure HOW
Starting point, Magisk 21.4/Manager 8.0.4 (not hidden), rooted, boot into TWRP, and flash:
1) patched boot.img from you
2) flash Magiskv22.zip confirmed md5sum:
Code:
e14132835b4cc0878639fcf645db479c Magisk-v22.0.zip
noticed that this flashing of zip appears to overwrite the boot.img, ignored it for the time being.
booted OK, said Magisk 22 is installed on the TOP part of the app, BUT, on the bottom, it showed Latest v22, and installed 8.0.4, and said, your device needs more updates, it will now download v22 and install, click ok,
rebooting in 5 seconds, and it comes back to the same spot, again, your machine needs more updates , click OK, again, download, rebooting in 5 seconds, and no change. Clicking CANCEL allows pressing the UPDATE button.. that doesn't help either.
Went to TWRP again, flashed your boot-patched.img , it then appear to not have any Magisk installed at all
so, installed v22 APK from the running phone, it then showed app/manager v22, but no magisk installed, so recalling that flashing the ZIP made it appear that magisk v22 IS installed, so flashed the ZIP in TWRP and it booted ok, and appears to have v22 installed on both parts of the app.
I'm thinking the steps should be:
1) Install Magisk v22 APK from phone
2) reboot into TWRP and flash the patched boot.img
3) if does not work, flash magisk v22 from twrp..
Sorry for "reinventing" what is known to all just couldn't find a "guide" with correct order for Redmi 7a...
Stormy.
PS: @MOFI69 , after an hour or so, got a pop up with long hex value and it said to send 1 BTC there to continue using the phone, I did that, then same message appeared on Android TV, did that, now on the Android Dog Collar do you think it has anything to do w/that boot.img u patched
Just kidding friend, have fun!!
Since the phone was already rooted (with a manipulated boot.img unknown to me) it can lead to strange malfunctions.
The best and easiest way is to uninstall Magsik (from the manager); REBOOT TO TWRP; INSTALL THE ORIGINAL boot.img and immediately afterwards my leased and immediately magisk V22, no reboot in between.
Then reboot into the system and install the magisk V22.apk, sometimes it is already there as a "shadow", then just start, it installs itself.
ok, may try that, only thing is that uninstalling magisk mgr, will lose all the "settings", like which app is granted root, and modules installed?
the way i did seems to work (i don't know exactly the steps yet), but it kept all settings/permissions, of all rooted apps...
Strange is that flashing magisk v22 appear to patch the boot.img, so question is why your boot.img is needed if it gets flashed later... not doubting it is, just asking.. ok, will try another phone and see...
S
Yes, the settings of Magisk have to be recreated again, as with a first-time installation. All possibly installed modules must be removed beforehand!
The boot.img is always pached by magisk, which is not possible without a boot.img edited with oss-patcher. The 32 bit ramdisk is missing (the operating system is recognized as this by magisk), so it cannot be installed. The patch only adds an interface so that magisk can install "redirection" for root access.
I think the boot.img you have used so far already contains a permanently installed magisk version, is often done this way on other chinese telephones, it works, but an update of magisk is mostly not possible, hence your problems.
In "my" boot.img there is no magisk preinstalled and updates are possible at any time. Unfortunately, I can't tell you whether your type of installation will work in the long term, you'll notice that with the next update ;-)
Thanks for the GREAT explanation!! yes, current boot.img I could not apply magisk updates smoothly, had to always flash from recovery, and that worked fine.
Manage to update without having to reinstall all modules, all remained, vanced, etc. so far leaving it.. I used to have 5 days to play with such things, now, 5 hours is hard to get, naively I expected it to be 5-min
Also managed to root a totally brand new phone using your boot.img + magisk v22, here one must add vbmeta.img as well as Permissiver_v4.zip, not entirely clear on right order, eventually it worked
Thanks much to @MOFI69
Stormy.
Super that makes me happy!
Then have fun with your Redmi
Best wishes
Hi,
Lost root access after updating my OnePlus 6T to Android 11 a few days back, hence decided to flash magisk_patched image that I had created around 2 months back. Phone didn't like it ofcourse and gave me a QualComm Crash Dump error.
After searching, managed to boot into bootloader, however wondering how do I now boot my phone - I have downloaded and installed latest recovery (3.5.2_9.0-fajita.img) and am able to boot into recovery as well as bootloader/ fastboot.
Have also downloaded the zip file for Android 11 stable version - OnePlus6TOxygen_34.J.60_OTA_0600_all_2108052232_8c516d0cce8795.zip
Question - What do I need to flash this? adb commands don't seem to be working, only fastboot commands seem to. Can I just "push" this zip file in fastboot or is that only for img files?
Any help woud be massively appreciated!
The update to 11 does not agree with Magisk which causes it to either fail to complete the update or to die at early boot depending on how bad things were messed up. You can reapply root once the update to 11 is finished though, so you can still have root.
In your case manually upgrading to 11, letting it finish the upgrade, and then installing Magisk again is your best bet, in which case you would either have to find something that understands the update format or manually extract the updated partitions from the payload, iirc
Extracted boot.img and used fastboot command : fastboot boot boot.img, but this doesn't seem to have worked as well. Just thinking aloud what else can be done?
Edit - It now tries to boot, but then seems to go into OnePlus Recovery (from the chinese characters displayed along with an option to choose English language)
sam_htc_touch said:
Have also downloaded the zip file for Android 11 stable version - OnePlus6TOxygen_34.J.60_OTA_0600_all_2108052232_8c516d0cce8795.zip
Question - What do I need to flash this? adb commands don't seem to be working, only fastboot commands seem to. Can I just "push" this zip file in fastboot or is that only for img files?
Click to expand...
Click to collapse
Masamune3210 said:
The update to 11 does not agree with Magisk which causes it to either fail to complete the update or to die at early boot depending on how bad things were messed up. You can reapply root once the update to 11 is finished though, so you can still have root.
In your case manually upgrading to 11, letting it finish the upgrade, and then installing Magisk again is your best bet, in which case you would either have to find something that understands the update format or manually extract the updated partitions from the payload, iirc
Click to expand...
Click to collapse
Hi, thanks for responding. I am not even concerned about root right now, just want my phone to boot up first Any suggestions on what can I try?
sam_htc_touch said:
Hi, thanks for responding. I am not even concerned about root right now, just want my phone to boot up first Any suggestions on what can I try?
Click to expand...
Click to collapse
For the benefit of others, all sorted finally y'day evening. Plenty of helpful tips in this thread
(Well I was able to boot into Android 11.1.1.1 - no root as yet, but I will perhaps look into that later, can't stand those annoying ads :-D )