Related
Because meanwhile it's hard to find new A2017G images in Drakenfx TWRP thread I decided to open a new thread with the files from me.
Notes:
TWRP used 3.1.0.0
Coming from previous Stock Nougat System try to dirty flash the System and root with Supersu 2.79 (not sr3). After that wipe cache/dalvik.
If it isn't working this way, try formating system partition and flash system again. TWRP will tell you that there is no system installed and the system will for sure not boot if so. Restart into TWRP and flash the System and Supersu again. If this is still not working you have to factory reset your phone.
Keep care for Dragons. Its possible the update will change your data partition to f2fs. In combination with Supersu this is bad. If so you have to format data to ext4.
Using Supersu it's not necessary to install the no-verity patch, it's already included in Supersu.
Be carefull, next dragon ahead. Not installing Supersu after a virgin installation (data wiped/factory reset) will lead to a stock recovery instead of TWRP after the first boot.
[Nougat:]
B04:
I can't believe it. This ROM is up to now fully functional. ZTE finally did it. Cam is working, Dolby, Live Wallpaper also, no Tencent spyware, I wonder where the pittfall is!?!
Bootstack
https://www.androidfilehost.com/?fid=457095661767159296
System
https://www.androidfilehost.com/?fid=745425885120730040
Full Stock Reverter (If you like to revert Fastboot/Aboot/Recovery to Stock version)
https://www.androidfilehost.com/?fid=529152257862724933
B02:
Bootstack
https://www.androidfilehost.com/?fid=817550096634766076
System
https://www.androidfilehost.com/?fid=745425885120728390
Full Stock Reverter (If you like to revert Fastboot/Aboot/Recovery to Stock version)
https://www.androidfilehost.com/?fid=673368273298951352
B01:
Bootstack
https://www.androidfilehost.com/?fid=745425885120713802
System
https://www.androidfilehost.com/?fid=673368273298937254
[Marshmallow]
B09
Bootstack
https://www.androidfilehost.com/?fid=457095661767125769
System
https://www.androidfilehost.com/?fid=673368273298919671
@tron1 tried dirty flashing over b01 was stuck in ugly boot screen
same result after wiping and clean installing b02,
towards end of system.zip file to lines of red error line stating error log generated,and zip successfully flashed.
tuiyaan said:
@tron1 tried dirty flashing over b01 was stuck in ugly boot screen
same result after wiping and clean installing b02,
towards end of system.zip file to lines of red error line stating error log generated,and zip successfully flashed.
Click to expand...
Click to collapse
TWRP version?
tron1 said:
TWRP version?
Click to expand...
Click to collapse
twrp-3.0.3-1-ailsa_ii
tuiyaan said:
twrp-3.0.3-1-ailsa_ii
Click to expand...
Click to collapse
This is ancient. Try it with 3.1.0 or 3.0.4
Thanks alot.
Really handy to have all the files in one place.
Can I flash this ZTE_A2017GV1.2.0B02_Stock_System_by_tron1.zip on my A2017U variant with A2017U boot stack?
khangozzy said:
Can I flash this ZTE_A2017GV1.2.0B02_Stock_System_by_tron1.zip on my A2017U variant with A2017U boot stack?
Click to expand...
Click to collapse
I can only ask you to try and tell us if it is working. The other way it is working. I've been succesfully on BadBoys ROM with A2017G.
I'm on A2017G , LOS 14.1 from the 1st may. Can I dirty flash your B02 bootstack to get it up to date ?
Does the bootstack contains the latest baseband ?
tron1 said:
This is ancient. Try it with 3.1.0 or 3.0.4
Click to expand...
Click to collapse
tried it with 3.0.4 twrp no error but stuck in boot menu
tried with B01 and B02.
back to b10 with twrp zip
tuiyaan said:
tried it with 3.0.4 twrp no error but stuck in boot menu
tried with B01 and B02.
back to b10 with twrp zip
Click to expand...
Click to collapse
Tried flashing Supersu after flashing system? Also flashed Bootstack?
tron1 said:
Tried flashing Supersu after flashing system? Also flashed Bootstack?
Click to expand...
Click to collapse
Danke bro Danke
my device is alive and B02 updated
thank you for your patience
flashing SU did the job
i was missing this step
tron1 said:
I can only ask you to try and tell us if it is working. The other way it is working. I've been succesfully on BadBoys ROM with A2017G.
Click to expand...
Click to collapse
It works well with my lastest A2017U B25 bootstack.
Btw, how can I disable the Mi-POP notification when it turned on?
Sent from my ZTE A2017G using Tapatalk
khangozzy said:
It works well with my lastest A2017U B25 bootstack.
Btw, how can I disable the Mi-POP notification when it turned on?
Click to expand...
Click to collapse
Should be digged somewhere in the settings. Can't tell you exactly because I've removed this piece of crapware.
khangozzy said:
It works well with my lastest A2017U B25 bootstack.
Btw, how can I disable the Mi-POP notification when it turned on?
Sent from my ZTE A2017G using Tapatalk
Click to expand...
Click to collapse
It can't be removed while mipop is active. Hope it'll be fixed in next update
joaste said:
It can't be removed while mipop is active. Hope it'll be fixed in next update
Click to expand...
Click to collapse
It doesn't show on US B19 ROM.
Sent from my ZTE A2017G using Tapatalk
khangozzy said:
It doesn't show on US B19 ROM.
Sent from my ZTE A2017G using Tapatalk
Click to expand...
Click to collapse
Not even when you drag down the notification window?
joaste said:
Not even when you drag down the notification window?
Click to expand...
Click to collapse
Yes
Sent from my ZTE A2017G using Tapatalk
Update!!! B04 is up and running.
I'm on Marshmallow B09 unlocked and twrp. Can I just flash B04 Bootstack and after that B04 System for upgrading to nougat?
And which SuperSU version to flash for root?
and which partitions i need to wipe before/after flashing Nougat?
Thank you!
Stock Kernel + SafetyNet Patch + DRM Fix
Use case for this kernel:
- If you want to stay completely stock, but have an unlocked bootloader, the SafetyNet is tripped which disables features such as Android Pay.
- This kernel is completely stock except for the addition of a patch that removes the SafetyNet check.
- This will not prevent SafetyNet from tripping for other reasons, like rooting.
- Now You can use Android Pay with an unlocked bootloader.
Installation:
- Installation using TWRP
- Installation via the bootloader
Code:
fastboot flash boot boot.img
Downloads: Dropbox; AndroidFileHost
Sourse: 32.3.A.2.33; 32.4.A.0.160; 32.4.A.1.54
I compiled the stock kernel and applied the SafetyNet patch by sultanxda.
DISCLAIMER:
No one is responsible for any damage caused to your device except You. You have been warned.
TWRP 3.1.1 for Xperia Z5, Z5C, Z3+
Vulkan API for Adreno 430
There's a better way than using the boot partition. If you use the ramdisk method, and get it to a recovery partition, you can do almost anything back and forth without having to change boot images. you can just flash over everything and still maintain your recovery partition.
https://forum.xda-developers.com/showthread.php?t=3588365
https://forum.xda-developers.com/showthread.php?t=3609358
@NeoBeum
At me on stock firmware of Magisk, doesn't hide SafetyNet and therefore I compiled this kernel.
grayleshy said:
@NeoBeum
At me on stock firmware of Magisk, doesn't hide SafetyNet and therefore I compiled this kernel.
Click to expand...
Click to collapse
grab the recovery image I made and then flash it to recovery while you're using your kernel, then flash magisk I the fota/recovery partition recovery, then magisk will be able to capture the sepolicy it needs, then you should be able to flash a full ftf excluding FOTAKernel. to test, you'll have 2 recovery working. the one that's in the boot img, and recovery img.
I had this at the start, and once I got recovery to the recovery partition, ive been free to flash anything if I exclude the fotakernel wipe.
I had to add the fstab for the older Android versions. but I haven't included that in the prebuilt recovery.
magisk only needs to capture a pure system and boot image once, and it mirrors it. after that, you can load up modified kernels
IT s nice to see A kernel for nougat..
What about other functions of kernel? All stock?
emosis said:
What about other functions of kernel?
Click to expand...
Click to collapse
In the future, if I have the desire, then I will make a custom kernel with improvements.
The first will be a raised version of the kernel with 3.10.84 to 3.10.105.
emosis said:
All stock?
Click to expand...
Click to collapse
What do You mean?
Can i flash and working with LOS 14.1?
reevdre said:
Can i flash and working with LOS 14.1?
Click to expand...
Click to collapse
The kernel is only for stock firmware!
On other firmware, the stability is not guaranteed.
reevdre said:
Can i flash and working with LOS 14.1?
Click to expand...
Click to collapse
if they haven't made a recovery for LOS, I'll have a recovery twrp port for it after the Z5C gets official support for the Omni base, AOSP is completed, but there's no room on their build server for new AOSP devices
Can you update this for .160? I have the kernel. Thanks!
dlee390 said:
Can you update this for .160? I have the kernel.
Click to expand...
Click to collapse
Sony did not post the kernel sources. dev
oh ok thanks!
also, why doesn't this work with magisk like your other kernels for z5p and z5? thanks!
dlee390 said:
also, why doesn't this work with magisk like your other kernels for z5p and z5? thanks!
Click to expand...
Click to collapse
Use magisk v13.
Upd 32.4.A.0.160
Need update for 32.4.A.1.54 rom
frager45 said:
Need update for 32.4.A.1.54 rom
Click to expand...
Click to collapse
Well, I'll do it!
Upd 32.4.A.1.54.
GreyLeshy said:
Upd 32.4.A.1.54.
Click to expand...
Click to collapse
Thnaks, but wi-fi not opening...
I try press on button but not pressing...
frager45 said:
Thnaks, but wi-fi not opening...
I try press on button but not pressing...
Click to expand...
Click to collapse
Provide a screenshot of the terminal command lsmod.
Stock Kernel + SafetyNet Patch + DRM Fix
Use case for this kernel:
- If you want to stay completely stock, but have an unlocked bootloader, the SafetyNet is tripped which disables features such as Android Pay.
- This kernel is completely stock except for the addition of a patch that removes the SafetyNet check.
- This will not prevent SafetyNet from tripping for other reasons, like rooting.
- Now You can use Android Pay with an unlocked bootloader.
Installation:
- Installation using TWRP
- Installation via the bootloader
Code:
fastboot flash boot boot.img
Downloads: Dropbox (E6633,E6653,E6683)
Current version: 32.3.A.2.33 -perf-g1016077
I compiled the stock kernel and applied the SafetyNet patch by sultanxda.
DISCLAIMER:
No one is responsible for any damage caused to your device except You. You have been warned.
TWRP 3.1.1 for Xperia Z5, Z5C, Z3+
Vulkan API for Adreno 430
please port for E6853
anjelz2012 said:
please port for E6853
Click to expand...
Click to collapse
Try the Zach's Kernel, in it the SafetyNet check is partially disabled.
Great work!
delete
Thank you! SafetyNet check passes without errors
But one question: I want to flash recovery afterwards, so i can use (or at least try to use) the magisk root + magisk hide method along with safetynet passed.
I tried different twrp.img (3.0.2 and 3.1.0) for e6653, but no recovery seems to work.
I tried to flash it via "fastboot flash recovery twrp-x.x.x.img" but it does not boot into recovery ("adb reboot recovery" and hotkeys result in a simple system reboot).
I am not sure though, if i have to flash twrp into a different partition than "recovery"?
Thank you in advance.
rrdna said:
I tried different twrp.img (3.0.2 and 3.1.0) for e6653, but no recovery seems to work.
I tried to flash it via "fastboot flash recovery twrp-x.x.x.img" but it does not boot into recovery ("adb reboot recovery" and hotkeys result in a simple system reboot).
I am not sure though, if i have to flash twrp into a different partition than "recovery"?
Thank you in advance.
Click to expand...
Click to collapse
Try to install TWRP 3.1.1.
grayleshy said:
Try to install TWRP 3.1.1.
Click to expand...
Click to collapse
Thanks, 3.1.1 worked for me
rrdna said:
Thanks, 3.1.1 worked for me
Click to expand...
Click to collapse
It's great that TWRP came up and Magisk hides root.
Thanks for the work!!! Any chance for E6633?
christis said:
Thanks for the work!!! Any chance for E6633?
Click to expand...
Click to collapse
If the kernel don't work for You, give me Kernel.sin, then I will do it for E6633.
Thanks for the work. @grayleshy
SIN Files : https://drive.google.com/drive/folders/0B9v3aNFonkyMWlFMbF9yME5EaTg
Did you use sultanxda safetynet patch?
Added kernel for E6633.
sceryavuz said:
Did you use sultanxda safetynet patch?
Click to expand...
Click to collapse
I will soon lay out the source code. There and see, what patch is applied.
Thanks a lot. Can't wait to see the source code! Do you have an eta?
rrdna said:
Thank you! SafetyNet check passes without errors
But one question: I want to flash recovery afterwards, so i can use (or at least try to use) the magisk root + magisk hide method along with safetynet passed.
I tried different twrp.img (3.0.2 and 3.1.0) for e6653, but no recovery seems to work.
I tried to flash it via "fastboot flash recovery twrp-x.x.x.img" but it does not boot into recovery ("adb reboot recovery" and hotkeys result in a simple system reboot).
I am not sure though, if i have to flash twrp into a different partition than "recovery"?
Thank you in advance.
Click to expand...
Click to collapse
I've the same issue...
MichaMichaMicha said:
Can't wait to see the source code!
Click to expand...
Click to collapse
Patch in kernel from @Sultanxda . Patch of may 23.
Earlier I didn't publish information on a patch as checked this patch.
Looks like you're working on an all in-built kernel ?
If you're making an progress towards in-built MHL please, please let us know
The magic seems to be in the configuration or additional patches (I had it working in the SunKernel Corona source)
but it doesn't seem to work out of the box with Sony's source [or I missed something],
anyway:
Keep up the good fight !
rrdna said:
Thank you! SafetyNet check passes without errors
But one question: I want to flash recovery afterwards, so i can use (or at least try to use) the magisk root + magisk hide method along with safetynet passed.
I tried different twrp.img (3.0.2 and 3.1.0) for e6653, but no recovery seems to work.
I tried to flash it via "fastboot flash recovery twrp-x.x.x.img" but it does not boot into recovery ("adb reboot recovery" and hotkeys result in a simple system reboot).
I am not sure though, if i have to flash twrp into a different partition than "recovery"?
Thank you in advance.
Click to expand...
Click to collapse
When you install magisk is the drmfix still active? The last time I installed magisk I was facing issues where I'd get white noise when taking pictures and no post processing being done
Thank you!
Now I can use OTA updates for my Z5!!
The_Miggs said:
Thank you!
Now I can use OTA updates for my Z5!!
Click to expand...
Click to collapse
This is not about OTA. SafetyNet : https://www.howtogeek.com/241012/sa...y-and-other-apps-dont-work-on-rooted-devices/
6- https://otafsg1.h2os.com/patch/amaz...22_OTA_061_all_1911200429_a3efe64891d2c42.zip
6T- https://otafsg1.h2os.com/patch/amaz..._41_OTA_061_all_1911200419_f2e12518eef8ae.zip
Found this today. File has a date of 11/20/19. I put in root and do manual update thru settings/update.
Magisk patched boot.img for the above 6T ROM.
https://drive.google.com/open?id=1DIoNvGG81IC6FdWiOgSRawG0-eAKUqBF
I had a boatload of bugs with the OB1. I have a 6T converted. Couldnt answer or make calls, reboots, freezes, crashes, WIFI didnt work, no pic messages, etc. I just tested for a second and I could make calls and wifi works. Do not try to install the Magisk patched boot.img. It will give the problems I had with OB1. I tried.
Def works a lot better. No freezes or reboots. My phone was useless on OB1 and I didn't want to flash back to 9 and lose my data. I had to forward my calls to another phone and wait for an updated ROM. But this def fixed a lot of the problems I encountered.
Edit: Still cant flashboot boot twrp.img.(3.3.1-1) Same error as before (failed remote unknown command)
Here's a bonus: Magisk patched boot.img for this OB2. Tested and verified root and no problems. Patched myself. For 6T. Extracted the boot.img from the payload.bin and patched.
https://drive.google.com/open?id=1DIoNvGG81IC6FdWiOgSRawG0-eAKUqBF
shatty said:
Here's a bonus: Magisk patched boot.img for this OB2. Tested and verified root and no problems. Patched myself. For 6T. Extracted the boot.img from the payload.bin and patched.
https://drive.google.com/open?id=1DIoNvGG81IC6FdWiOgSRawG0-eAKUqBF
Click to expand...
Click to collapse
@shatty, thanks.
What did you do to upgrade ? Actually i'm in OB1 Android 10 and Root with patched boot. So you upgrade with OTA or local upgrade ? You loose Root, and you put the new patched in adb? IS it ok?
Thanks
g4seb said:
@shatty, thanks.
What did you do to upgrade ? Actually i'm in OB1 Android 10 and Root with patched boot. So you upgrade with OTA or local upgrade ? You loose Root, and you put the new patched in adb? IS it ok?
Thanks
Click to expand...
Click to collapse
If you're rooted use the same method as always, use local update ( you don't have access to incremental update anyway as you are rooted) and BEFORE rebooting go in Magisk manager and install Magisk again but on other slot. You don't need to play with adb or fastboot.
@Striatum_bdr :
Thanks, so download the update, do local update and after juste install magisk on the other slot.
shatty said:
Here's a bonus: Magisk patched boot.img for this OB2. Tested and verified root and no problems. Patched myself. For 6T. Extracted the boot.img from the payload.bin and patched.
https://drive.google.com/open?id=1DIoNvGG81IC6FdWiOgSRawG0-eAKUqBF
Click to expand...
Click to collapse
wiped my device and flashed A10 beta 2, but every time flash this patched img file from fastboot my not booting. is there any other way to flash this patched img ?
ariyan rana said:
wiped my device and flashed A10 beta 2, but every time flash this patched img file from fastboot my not booting. is there any other way to flash this patched img ?
Click to expand...
Click to collapse
It worked on my 6t converted from tmo. Anyone else try this patched boot.img? Why wipe? Upgrade works fine.
So after hours of using the ob2 I didn't have any freezes or reboots. 1000000x better than my experience on ob1
shatty said:
So after hours of using the ob2 I didn't have any freezes or reboots. 1000000x better than my experience on ob1
Click to expand...
Click to collapse
Same here bud. Thanks.
shatty said:
Def works a lot better. No freezes or reboots. My phone was useless on OB1 and I didn't want to flash back to 9 and lose my data. I had to forward my calls to another phone and wait for an updated ROM. But this def fixed a lot of the problems I encountered.
Edit: Still cant flashboot boot twrp.img.(3.3.1-1) Same error as before (failed remote unknown command)
Click to expand...
Click to collapse
For now the right command is fastboot flash boot twrp mauronofrio.img version and then flash the installer zip through recovery.
It's a Oneplus's problem.
[EDIT 1]
After a few tries it worked! Now I try to install twrp (mauronofio version) and root the phone.
P.s. I'm trying to update (come form OB-1) I removed all magisk's modules, flashed magiks unistaller but the update with update manager keep failing...any idea?
[EDIT2]
ok, now I'm rooted and I've twrp but wifi doesn't work it's turn off automatically!
[EDIT3]
I've fix it! I've talked with mauronofrio and he said that it's due to flashing the twrp in the boot partition, so he suggested me two ways:
1. Root your device and flash the twrp installer using magisk manager
2. After the command fastboot flash boot twrp.img reboot in recovery, flash the stock boot.img flash twrp installer.zip and finally flash magisk.
I choosen the second way and it worked! Now I've OB_2, twrp, magisk and wifi connection.
Thx a lot for the links and Infos.
I have flashed it and it feels definitely smoother and I hope the random reboots are fixed.
From the changelog they should be.
Here is a small how to, how the upgrade from 10 to 10 ob2 went smooth. Also using this on every update.
1. Just use normal systen ota & let it install or Flash full OOS 10 zip via local update . (DO NOT REBOOT)
2a. Flash newest TWRP: fajita twrp 3.3.1-28.zip (or newer) by @mauronofrio via Magisk Manager (DO NOT REBOOT)
or 2b. go into magisk manager, search for a module called "twrp a/b retention script" Install it (DO NOT REBOOT)
3. Flash magisk to 2nd slot via MAgisk Manager (Magisk Manager → Tap on Install → Then select Install to Inactive Slot)
4. Reboot, wait and enjoy
pOpY
Gesendet von meinem ONEPLUS A6013 mit Tapatalk
Be very careful with the patched boot image. It hard-bricked my OP6T! Full details here:
https://forum.xda-developers.com/oneplus-6t/help/spent-6-hours-trying-to-rooted-android-t4012909
It looks like they took FactoryMode away using *#808# when using the dialer... anyone noticed?
Did they fix the extra blank space under navigation keyboard when type? Thanks
nicche said:
For now the right command is fastboot flash boot twrp mauronofrio.img version and then flash the installer zip through recovery.
It's a Oneplus's problem.
[EDIT 1]
After a few tries it worked! Now I try to install twrp (mauronofio version) and root the phone.
P.s. I'm trying to update (come form OB-1) I removed all magisk's modules, flashed magiks unistaller but the update with update manager keep failing...any idea?
[EDIT2]
ok, now I'm rooted and I've twrp but wifi doesn't work it's turn off automatically!
Click to expand...
Click to collapse
same thing happened to me. Have you found the fix sir?
OK just reflash the rom and dont forget to flash twrp and magisk again
anddd boom i got wifi working again
Anyone else having issues like the systems is getting slower animation is choppy and it just lag. I noticed it as well when playing games when that happens and it feels like i dont get as much framerates but a reboot of system fixed it for me. I thought by updating to ob2 it would fix this choppy feeling but its still there
I upgraded from OOS 10 Stable to OOS Beta 2 and all went on okay. No data lost.
Rickydwi said:
Anyone else having issues like the systems is getting slower animation is choppy and it just lag. I noticed it as well when playing games when that happens and it feels like i dont get as much framerates but a reboot of system fixed it for me. I thought by updating to ob2 it would fix this choppy feeling but its still there
Click to expand...
Click to collapse
I don't have this issue, but I do have the Bluetooth not working bug
Hi, i have a 11T (not the Pro version) and i unlocked it yesterday.
I want root it (like i did with my previous 9T), but it goes into bootloop.
My stock miui version is: 12.5.8.0(RKWEUXM). This are the operation i did:
- installed magisk 23 APK from the git page
- copied the boot image from the image of the same version (i also tried to extract the image from the payload)
- patched with magisk
- flashed in fastboot using fastboot flash boot_a patched_image.img and, after, fastboot flash boot_b patched_image.img
- reboot the phone.
If i flash again the original boot.img, of course bootloop disappear!
I also tried to boot in recovery mode for clean the magisk modules without success (but is a fresh install, i don't think that the restore from xiaomi cloud can copy also the magisk modules).
I don't understand why i'm the only one in the web that have this problem. Someone have idea of what i can try to do?
For now, i want try to keep the original recovery for install the OTA update, but if all doesn't work i'll try the twrp installation (i think with this recovery all problem will go away).
Thank you very much
Marco
Marcolo88 said:
Hi, i have a 11T (not the Pro version) and i unlocked it yesterday.
I want root it (like i did with my previous 9T), but it goes into bootloop.
My stock miui version is: 12.5.8.0(RKWEUXM). This are the operation i did:
- installed magisk 23 APK from the git page
- copied the boot image from the image of the same version (i also tried to extract the image from the payload)
- patched with magisk
- flashed in recovery (stock recovery) using fastboot flash boot_a patched_image.img and, after, fastboot flash boot_b patched_image.img
- reboot the phone.
If i flash again the original boot.img, of course bootloop disappear!
I also tried to boot in recovery mode for clean the magisk modules without success (but is a fresh install, i don't think that the restore from xiaomi cloud can copy also the magisk modules).
I don't understand why i'm the only one in the web that have this problem. Someone have idea of what i can try to do?
For now, i want try to keep the original recovery for install the OTA update, but if all doesn't work i'll try the twrp installation (i think with this recovery all problem will go away).
Thank you very much
Marco
Click to expand...
Click to collapse
In My pro version. I renamed the patched boot.img to just boot.img before i flashed it.
Belpek said:
In My pro version. I renamed the patched boot.img to just boot.img before i flashed it.
Click to expand...
Click to collapse
And flash it in fastboot not recovery.
Belpek said:
And flash it in fastboot not recovery.
Click to expand...
Click to collapse
I flashed too in recovery, i wrote wrong (now i edit my message).
I'll try your suggestion to rename the img, but in the previous Xiaomi i never did it and it worked .
Thank you very much
Belpek said:
And flash it in fastboot not recovery.
Click to expand...
Click to collapse
I tried just now and it doesn't work also with the file renamed
Do you unlock bootloader?
zelenko said:
Do you unlock bootloader?
Click to expand...
Click to collapse
Yes i unlocked, and if I watch the status, it says unlocked!.
What I can also do?
Marcolo88 said:
Yes i unlocked, and if I watch the status, it says unlocked!.
What I can also do?
Click to expand...
Click to collapse
Flash in fastboot...
leobak said:
Flash in fastboot...
Click to expand...
Click to collapse
This i did but it goes into boot loop
you need to use the correct boot.img this issue occurs when the boot.img is not correct according to the version of the ROM.
from where are you downloading the patched image?
nousernamesorry said:
you need to use the correct boot.img this issue occurs when the boot.img is not correct according to the version of the ROM.
from where are you downloading the patched image?
Click to expand...
Click to collapse
With magisk canary it works!
I downloaded the image from here: https://xiaomifirmwareupdater.com/miui/agate/stable/V12.5.8.0.RKWEUXM/
is the correct image.
I don't like the new implementations in canary version, but for now it worked only with this version.
I know you got it working already but I flashed mine with XiaomiADBFastbootTools.jar and never done that whole "fastboot flash boot_a patched_image.img and, after, fastboot flash boot_b patched_image.img" thingy in ADB. It works no problem every time I do it after an update. I know you can install directly from Magisk after applying an OTA but I prefer this metod. Zygisk will be needet to get root on A12 though and it doesn't have Magisk hide which means I'll never get those banking apps to work anymore thill someone figures out a better method I'll wait with the A12 update. Just my two cents.
MocnePifko said:
I know you got it working already but I flashed mine with XiaomiADBFastbootTools.jar and never done that whole "fastboot flash boot_a patched_image.img and, after, fastboot flash boot_b patched_image.img" thingy in ADB. It works no problem every time I do it after an update. I know you can install directly from Magisk after applying an OTA but I prefer this metod. Zygisk will be needet to get root on A12 though and it doesn't have Magisk hide which means I'll never get those banking apps to work anymore thill someone figures out a better method I'll wait with the A12 update. Just my two cents.
Click to expand...
Click to collapse
For me, with zygisk, i can make work all application with root checker (like banking apps).
Marcolo88 said:
With magisk canary it works!
I downloaded the image from here: https://xiaomifirmwareupdater.com/miui/agate/stable/V12.5.8.0.RKWEUXM/
is the correct image.
I don't like the new implementations in canary version, but for now it worked only with this version.
Click to expand...
Click to collapse
Hi man, I am wondering can I have the download address about that magisk canary build? I've been bootlooping just like you before.
louiswong2099 said:
Hi man, I am wondering can I have the download address about that magisk canary build? I've been bootlooping just like you before.
Click to expand...
Click to collapse
Hi, the canary build is in the same place of the "normal" build in the official git page.
This is the direct link of the APK:
https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk
The main page is this: https://github.com/topjohnwu/Magisk
Marcolo88 said:
Hi, the canary build is in the same place of the "normal" build in the official git page.
This is the direct link of the APK:
https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk
The main page is this: https://github.com/topjohnwu/Magisk
Click to expand...
Click to collapse
It worked on my Xiaomi 11T(not pro version) with a magisk-canary-patch, now the bootloop has been gone and really appreciated for your kindness help.