Android Oreo Boot Animation [Magisk] [Systemless] - Xiaomi Redmi Note 3 Themes, Apps, and Mods

Well it is the Android Oreo Boot Animation, nothing else nothing much, kinda experimental really and it is systemless.
Requires Magisk obviously.
Download:
https://drive.google.com/folderview?id=0BwSiTW1njfcoc1VIUUJLX0hUNDg

thank you for the animation, could you tell me how to install using magisk?
thanks in advance

Ginkaw said:
thank you for the animation, could you tell me how to install using magisk?
thanks in advance
Click to expand...
Click to collapse
1. open Magisk Manager
2. choose Module
3. tap icon + and then choose .zip (bootanimation oreo)
4. reboot

LukeyWolf said:
Well it is the Android Oreo Boot Animation, nothing else nothing much, kinda experimental really and it is systemless.
Requires Magisk obviously.
Download:
https://drive.google.com/folderview?id=0BwSiTW1njfcoc1VIUUJLX0hUNDg
Click to expand...
Click to collapse
bootloop problem?

Avez Khan said:
bootloop problem?
Click to expand...
Click to collapse
Are you getting a bootloop? If so make sure you have Magisk and flash it via Magisk Manager > Modules > + and select the zip file

Related

Grab Flashable 7.0 OFFICIAL OTA from Here

http://www.pocketables.com/2016/08/official-android-nougat-released.html
Pulled directly from my device and uploaded to my AFH site.
https://drive.google.com/open?id=0B0OpOqUNqeKkb19UbGxBV2NPc28
Stock, decrypted boot image, w. Verity disabled.
What version of android where you coming from?
spunks3 said:
What version of android where you coming from?
Click to expand...
Click to collapse
I had the MM version installed. However, this has system.transfer.list and vendor.transfer.list - meaning - it *should* be the FULL ROM.
digitalhigh said:
I had the MM version installed. However, this has system.transfer.list and vendor.transfer.list - meaning - it *should* be the FULL ROM.
Click to expand...
Click to collapse
So we should be good to wipe all in twrp, flash the update zip, then seperately flash the boot.img and maybe supersu?
Deadlights said:
So we should be good to wipe all in twrp, flash the update zip, then seperately flash the boot.img and maybe supersu?
Click to expand...
Click to collapse
All of the above worked for me!!
Also, Magisk Manager confirmed and working with PHH Root for AndroidPay+root.
digitalhigh said:
All of the above worked for me!!
Also, Magisk Manager confirmed and working with PHH Root for AndroidPay+root.
Click to expand...
Click to collapse
What steps did you follow to get TWRP and root ?
So how is OTA different from full image?
digitalhigh said:
All of the above worked for me!!
Also, Magisk Manager confirmed and working with PHH Root for AndroidPay+root.
Click to expand...
Click to collapse
Nice! Thanks man :good:.. I guess it'll handle vendor for us?
MRL3GS said:
What steps did you follow to get TWRP and root ?
Click to expand...
Click to collapse
It should go something like this:
1. Flash OTA. I used TWRP.
2. Reboot to bootloader. Reflash TWRP. Flash unlocked boot image.
3. Fastboot format cache and fastboot format userdata if coming from an ROM that was encrypted.
4. Reboot to TWRP.
5. Flash magisk, phh superSU.
6. Reboot.
7. ????
8. PROFIT.
kolyan said:
So how is OTA different from full image?
Click to expand...
Click to collapse
It is one and the same. It is the OTA image I received by enrolling my 6.0.1 device in the beta, and downloaded.
Deadlights said:
Nice! Thanks man :good:.. I guess it'll handle vendor for us?
Click to expand...
Click to collapse
Yep, /vendor is included, as well as updates to bootloader, etc.
kolyan said:
So how is OTA different from full image?
Click to expand...
Click to collapse
It does not encrypt if you were not previously encrypted, this is the biggest difference
digitalhigh said:
It should go something like this:
1. Flash OTA. I used TWRP.
2. Reboot to bootloader. Reflash TWRP. Flash unlocked boot image.
3. Fastboot format cache and fastboot format userdata if coming from an ROM that was encrypted.
4. Reboot to TWRP.
5. Flash magisk, phh superSU.
6. Reboot.
7. ????
8. PROFIT.
It is one and the same. It is the OTA image I received by enrolling my 6.0.1 device in the beta, and downloaded.
Click to expand...
Click to collapse
When i try to setup pay I get "android pay cant be used" :S
MRL3GS said:
When i try to setup pay I get "android pay cant be used" :S
Click to expand...
Click to collapse
Ahaha! Sorry. Magisk requires you have Magisk manager installed, and then you use the manager to disable root when you want to use Pay. My bad.
http://forum.xda-developers.com/devdb/project/dl/?id=19924&task=get
digitalhigh said:
Ahaha! Sorry. Magisk requires you have Magisk manager installed, and then you use the manager to disable root when you want to use Pay. My bad.
http://forum.xda-developers.com/devdb/project/dl/?id=19924&task=get
Click to expand...
Click to collapse
Thanks all working now
digitalhigh said:
It should go something like this:
1. Flash OTA. I used TWRP.
2. Reboot to bootloader. Reflash TWRP. Flash unlocked boot image.
3. Fastboot format cache and fastboot format userdata if coming from an ROM that was encrypted.
4. Reboot to TWRP.
5. Flash magisk, phh superSU.
6. Reboot.
7. ????
8. PROFIT.
It is one and the same. It is the OTA image I received by enrolling my 6.0.1 device in the beta, and downloaded.
Click to expand...
Click to collapse
Working great for me! Thanks again man!
Working great thanks !
Just to confirm for others :
1. Flash ROM don't reboot system !
2. Flash TWRP don't reboot system !
3. Flash the modified boot image, now reboot system !
4. Let it boot fully and make any app updates
5. Reboot into recovery
6. Flash SU
7. Wipe caches
8. Reboot and away you go !
I came from the latest MM security update and dirty flashed so be warned mileage may vary !
Worked for me Thank you!!!! Still kept super su and twrp!!!
Is anyone getting E:unknown command for patching system and vendor when flashing
Is that normal
hutzdani said:
Working great thanks !
Just to confirm for others :
1. Flash ROM don't reboot system !
2. Flash TWRP don't reboot system !
3. Flash the modified boot image, now reboot system !
4. Let it boot fully and make any app updates
5. Reboot into recovery
6. Flash SU
7. Wipe caches
8. Reboot and away you go !
I came from the latest MM security update and dirty flashed so be warned mileage may vary !
Click to expand...
Click to collapse
Flash the TWRP image file from TWRP? And what is the modified boot image?
Sent from my Nexus 6P using Tapatalk
Batfink33 said:
Is anyone getting E:unknown command for patching system and vendor when flashing
Is that normal
Click to expand...
Click to collapse
Me everything works fine tho just i cant get root to wrk the app keeps freezing on me can't grant root?
Sent from my Nexus 6P using Tapatalk

[MOD] Oreo Emoji flashable Zip for you Nougat ROM at Moto X2 2014 VICTARA

Hey Guys,
Here have a really awesome Emoji Oreo pack and guide for all of you,
REQUIREMENTS:
1: Unlocked Bootloader as always
2: Custom Recovery
3: No root Required
4: A zip attached in Thread
Let's do it:
1: Download Zip below attached
2: Place in internal Storage or SD card or OTG USB
3: Reboot to recovery
4: Select storage and find the zip you placed
5: Just flash and Reboot System
HERE YOU GO!!!
Enjoy
Hit thanks if you like!
See Ya
#Anybody can contact me if Device is hard brick or soft brick or dead boot, this is my hobby to do so not a business!
As always Screenshots below: i am running lineage official 14.1 final addition:
Works as a charm, no issues found. Thanks
Works really nice
How to uninstall this zip file after flashing and where to find it because its now showing in my root explorer
Anmol Saini said:
How to uninstall this zip file after flashing and where to find it because its now showing in my root explorer
Click to expand...
Click to collapse
Go to TWRP recovery and just flash it and reboot Phone..
zahidm said:
Go to TWRP recovery and just flash it and reboot Phone..
Click to expand...
Click to collapse
No, see he said UNINSTALL. How do you UNINSTALL. And flash what?
I'm pretty sure flashing this caused my device to be stuck booting the the logo unless I boot into recevery and the reboot from there
legojoe8 said:
No, see he said UNINSTALL. How do you UNINSTALL. And flash what?
I'm pretty sure flashing this caused my device to be stuck booting the the logo unless I boot into recevery and the reboot from there
Click to expand...
Click to collapse
Never, i flashed 100s of times and it never happened, and I don't know how to remove because i like these new emojis
zahidm said:
Never, i flashed 100s of times and it never happened, and I don't know how to remove because i like these new emojis
Click to expand...
Click to collapse
Huh. Well I just flashed a different zip of stock 7.1.1 emojis and that seems to have solved the booting issue
Can I flash it on S5 g900h los 14.1?
Ha_Dua_O said:
Can I flash it on S5 g900h los 14.1?
Click to expand...
Click to collapse
Yes it works... I've tested on many devices...
@zahidm
hi
do you have nougat emojis ?!
Ahmad.S9675 said:
@zahidm
hi
do you have nougat emojis ?!
Click to expand...
Click to collapse
The default emojis in ROM are nougat!

SM-G5520 G5520ZCU1CRK1 Root with Magisk

Dear Friends,
I am here to update Root package for SM-G5520 G5520ZCU1CRK1 8.1.0
1. Download & Flash this file. Link
2. Reset your phone
3. setup your phone
4. Done
Your Phone is rooted now.
Note: this root may work for "Flashfire" to flash GApps, because it's update root of magisk 18.0.
I have not tested it yet for GApps but it work 100% for root
Problem
hi pls say me work this package in G5528 Oreo
If it Don't Work,What Should i do??
hossein_vlz1 said:
hi pls say me work this package in G5528 Oreo
If it Don't Work,What Should i do??
Click to expand...
Click to collapse
1. Download your device boot.img
2. Move to your phone SD Card
3. Install magisk apk
4. now setup you magisk output format as .img.tar
5. now click on install
6. click on patched boot image
7. Now browse you boot.img
8. now wait for success
9. now find "patched_boot.img.tar" and move to your pc
10. reboot your phone into download mode
11. now flash patched boot img with odin
12. now your phone will restart. if it shows reset button on bottom of screen than reset your phone
Done.
OK
and
How i do changing IMG file to TAR??
I can not flash by img file
hossein_vlz1 said:
OK
and
How i do changing IMG file to TAR??
I can not flash by img file
Click to expand...
Click to collapse
install magisk
open it and goto settings
there you see "Patched Boot Output Format" click on it
Now tick .img.tar
thats it now install magisk with patched boot img
alien.baba said:
Dear Friends,
I am here to update Root package for SM-G5520 G5520ZCU1CRK1 8.1.0
1. Download & Flash this file. Link
2. Reset your phone
3. setup your phone
4. Done
Your Phone is rooted now.
Note: this root may work for "Flashfire" to flash GApps, because it's update root of magisk 18.0.
I have not tested it yet for GApps but it work 100% for root
Click to expand...
Click to collapse
Flashfire not working.
He says install Magisk 18 again. However, Magisk 18 is not installed again.
alien.baba said:
install magisk
open it and goto settings
there you see "Patched Boot Output Format" click on it
Now tick .img.tar
thats it now install magisk with patched boot img
Click to expand...
Click to collapse
Bro My phobe later asked me to reset factory and i do
but magisc isn't installed
and apeared yellow tirangle on the boot
pls help me more
hossein_vlz1 said:
Bro My phobe later asked me to reset factory and i do
but magisc isn't installed
and apeared yellow tirangle on the boot
pls help me more
Click to expand...
Click to collapse
now install magisk manually with apk.
your root will done.
Note: you should connected with internet & Yellow triangle will show in boot.
Need Help
I have rooted samsung galaxy on5 g5520 using above method
but magisk is unable to flash magisk modules .
error is that magisk is unable to extract zip file .
and flashfire is not also openning
hi
imranhussain12 said:
I have rooted samsung galaxy on5 g5520 using above method
but magisk is unable to flash magisk modules .
error is that magisk is unable to extract zip file .
and flashfire is not also openning
Click to expand...
Click to collapse
I think
flash twrp via odin. then use twrp to install magisk
hey i have a sm-g5520 on5 2016 and i want to update it to 8.1.0 and root it for get gapps, but idk how to do it. can you tell me step by step for an older guy? i really want to do it
barinbektas said:
hey i have a sm-g5520 on5 2016 and i want to update it to 8.1.0 and root it for get gapps, but idk how to do it. can you tell me step by step for an older guy? i really want to do it
Click to expand...
Click to collapse
Biraz daha sabredin. Yakında birşeyler olacak.
Help with Magisk Installation
alien.baba said:
Dear Friends,
I am here to update Root package for SM-G5520 G5520ZCU1CRK1 8.1.0
1. Download & Flash this file. Link
2. Reset your phone
3. setup your phone
4. Done
Your Phone is rooted now.
Note: this root may work for "Flashfire" to flash GApps, because it's update root of magisk 18.0.
I have not tested it yet for GApps but it work 100% for root
Click to expand...
Click to collapse
I am trying to apply the above steps. But what do you mean by "flash" ?
Flash using ODIN or Magisk? If Magisk, how to install Magisk as it needs to go to fastboot mode? (as our device seems to be unable of going to fastboot mode)
smt_best said:
I am trying to apply the above steps. But what do you mean by "flash" ?
Flash using ODIN or Magisk? If Magisk, how to install Magisk as it needs to go to fastboot mode? (as our device seems to be unable of going to fastboot mode)
Click to expand...
Click to collapse
flash using Odin. it's petched_boot.img.tar file. you don't need to fo to fastboot go to download mode by pressing Volume Down+Home Button+Power On Key.

[GUIDE] How I got Viper4Android working on rooted Xiaomi.eu rom

After a few failed attempts (using Audio Modification module etc.) I found a way to get Viper working on the Mi 9. installed on the rooted Xiaomi.eu rom via TWRP and Magisk.
1. Download the Viper4Android_FX-v3.4.2.zip via Magisk but don't install it via Magisk
2. Boot to TWRP and flash the Viper zip and then adhere to the following:
- Press a volume button when prompted to do so
- Volume down (to choose vol key installation method)
- Vol up (for new 2.5.0.5)
- Vol up (for material, if preferred)
- Vol up (for system app)
- Vol up (for lib workaround to be installed)
3. Reboot
4. Via Magisk find and install "Init.d injector" and then reboot
Viper4Android should now be processing your audio!
Rommco05 said:
Installation from Magisk doesn't work? Just curious
Click to expand...
Click to collapse
Not the usual way. On my Pixel 2 XL, either the magisk module would work out of the box or using the Audio Modification Library module would make it work. I tried both of these ways, with no success the driver just wouldn't install. Tried the XDA labs apk, along with the Audio Modification Library, didn't work. Was even waiting a few minutes after boot as I know sometimes/some roms it takes a few minutes to initialise.
After lots of playing around of different versions, I tried that additional installation step of the lib workaround, which states that init.d support is needed too. With the use of that extra init.d module, it works!
I spent some time doing this and figured I'd help out others when they come to do it too!
I managed to install via Magisk?? Maybe due to a Magisk update?
*justintime* said:
I managed to install via Magisk?? Maybe due to a Magisk update?
Click to expand...
Click to collapse
Ahh yeah that's fair enough! Probably flashing via TWRP isn't necessary, so long as the additional init module is there too
Rommco05 said:
Installed init and after Viper4 from Magsik and didn't work, need flash ot trough twrp, today...
Click to expand...
Click to collapse
Ah tgats handy to know! My initial istructions remain valid then
Rommco05 said:
Installed init and after Viper4 from Magsik and didn't work, need flash ot trough twrp, today...
Click to expand...
Click to collapse
Funny with twrp it wasn't working for me...... Magisk had an update. "Check updates canary build' in manager.
And it was a straight away. Flash.... Only no equalizer in usb/dock out though for Android auto
Rommco05 said:
btw after last Magisk update I was able install Viper4 over manager. I also installed that last option (fix)
Click to expand...
Click to collapse
Thanks, that's handy to know!
I simply couldn't get viper4android to work and didn't have much luck with the init.d injector... I ended up following your steps and installed a custom kernel and emulated init.d via the kernel auditor app.... Now its working perfectly!
Have any of you tried the ainur sauron mod on the mi 9?
hi is it possible to get viper4android work with magisk flash? because i don't want twrp and loosing encryption.
when i flash trough magisk viper4android app doesn't appear?
thank you
(sorry for bad english)
dffhgg said:
hi is it possible to get viper4android work with magisk flash? because i don't want twrp and loosing encryption.
when i flash trough magisk viper4android app doesn't appear?
thank you
(sorry for bad english)
Click to expand...
Click to collapse
Possibly...
Have you tried rebooting? Otherwise I'm unsure I'm afraid....
cd993 said:
Possibly...
Have you tried rebooting? Otherwise I'm unsure I'm afraid....
Click to expand...
Click to collapse
yes for sure i rebooted many times but no success..
always viper4android doesn't appear
i also tried install via apk download viper4android then install there also not work, after reboot it reask to install driver.
dffhgg said:
yes for sure i rebooted many times but no success..
always viper4android doesn't appear
i also tried install via apk download viper4android then install there also not work, after reboot it reask to install driver.
Click to expand...
Click to collapse
And this is with the init d module as well?
with init.d injector module from magisk? yes i installed it alredy
dffhgg said:
with init.d injector module from magisk? yes i installed it alredy
Click to expand...
Click to collapse
And you're on the latest eu rom?
Hmm all I can suggest is to remove fully uninstall viper, the init d module and make sure no other audio mods are installed, reboot, then install viper again (ensuring to choose yes to the lib workaround) and the init d module.
If that doesn't work, then unfortunately I'm out of ideas as I tried lots 9f things and this was the only method that worked for me.
Good luck
yes i'm on 10.2.17
i will give it a try and let you know.
hope will work thank you
dffhgg said:
yes i'm on 10.2.17
i will give it a try and let you know.
hope will work thank you
Click to expand...
Click to collapse
I'm on the latest weekly 9.4.11, if that makes any difference
can i flash this version whithout data loss?
i tried reinstall everything but no succes
hi guys my problem is solved!
what i did:
change selinux to permissive with this tool: Kernel SEPolicy patcher https://zackptg5.com/android.php
now viper4android is detect driver its full work!
dffhgg said:
hi guys my problem is solved!
what i did:
change selinux to permissive with this tool: Kernel SEPolicy patcher https://zackptg5.com/android.php
now viper4android is detect driver its full work!
Click to expand...
Click to collapse
Great! I'll save that just in case I ever need it
keep getting the following error
Checking for Digest files
Skipping Digest check: no digest file found
on twrp 3.3.0 b8 and latest EU rom

[Guide]Magisk Modules Disabler for booting into Magisk core-only Mode

Tools needed: boot.img extractor. I recommend the one created by osm0sis from this thread:
https://forum.xda-developers.com/sho....php?t=2073775
The first method was developed by osm0sis and removes magisk and all modules.
1. Unpack magisk_patched.img
2. Unzip overlay.dremove1.zip and place overlay.d folder in ramdisk folder.
3. Repack IMG
4. fastboot boot image-new.img created by repacking 8mg
This method is an offshoot of osm0sis version but boots core-only mode. Afterwards, remove the .disable-magisk file from the /cache folder for modules to work. Dot files are hidden files so if your root explorer can't see hidden files, run the "Remove disable_magisk" bat file in ADB.
1. Same as above but use the overlay.dcoreonly1.zip
For both methods you must be rooted for it to work. These are not cure all's for all bootloops.
Remove .disable_magisk bat file
https://www.androidfilehost.com/?fid=4349826312261684994
****************************************
Here is a fastboot bootable image to boot you into Magisk core-only mode in case you bootloop due to flashing a bad module and TWRP is not enough.
Once in fastboot:
fastboot boot image-newpixel3.img
You will boot with root but modules disabled. After you remove the offending module you will need to go to /cache folder and delete the .disable_magisk file before your modules will work.
fastboot boot image-newpixel3Remove.img
This one should remove magisk and all modules, then reboot and magisk should reinstall itself (ask to install necessary binaries). This is what osm0sis uses to recover from failed flashes. See this post:
https://forum.xda-developers.com/pi...odules-disabler-booting-magisk-t3976625/page2
Images are in this common folder. Pick the appropriate image for your phone.
6-4-20
https://www.androidfilehost.com/?w=files&flid=313291
Amazing! Thanks
I can confirm this worked on Android 10/Q. I can't use the canary patch method for magisk because I forgot to remove the modules before upgrading to Android 10. This method works like a charm, it removed the incompatible modules allowed me to by pass the bootloop.
Thank you so much for sharing!
For those who are wondering, these are the steps:
adb reboot bootloader
fastboot flash boot image-new.img
fastboot reboot
Done!
wao20 said:
For those who are wondering, these are the steps:
adb reboot bootloader
fastboot flash boot image-new.img
fastboot reboot
Done!
Click to expand...
Click to collapse
Second step should be:
fastboot boot image-new.img
Tulsadiver said:
Here is a fastboot bootable image to boot you into Magisk core-only mode. If you bootloop due to flashing a bad module, in fastboot:
fastboot boot image-new.img
You will boot with root but modules disabled.
Tested by me and @123SIT whom contributed on the project.
Made from Pixel 3 XL but should work on the Pixel 3 also.
Image
https://mega.nz/#!NE5yGaBA!0HLSWvdD4x4cOmo35HrDGrGNxTAUGW4LpkpVv1ygwVI
Thanks to @ApeironTsuka for his guide and everyone on the Magisk support thread like @jcmm11 for their patience and help.
Click to expand...
Click to collapse
Any idea if this works on the Pixel 2 and 2XL?
Sent from my Pixel C using Tapatalk
Alxoom33 said:
Any idea if this works on the Pixel 2 and 2XL?
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
No, but you have TWRP. You don't need it.
P3 doesn't have TWRP? Wow!!! I knew I didn't like that phone.
Sent from my Pixel 2 XL using Tapatalk
Alxoom33 said:
P3 doesn't have TWRP? Wow!!! I knew I didn't like that phone.
Click to expand...
Click to collapse
Only since the update to android 10
Alxoom33 said:
P3 doesn't have TWRP? Wow!!! I knew I didn't like that phone.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I just came across a time when I couldn't even boot TWRP on my Pixel 2. Here is a boot with root, core-mode Magisk image for Pixel 2 XL.
https://www.androidfilehost.com/?fid=1899786940962594367
Tulsadiver said:
I just came across a time when I couldn't even boot TWRP on my Pixel 2. Here is a boot with root, core-mode Magisk image for Pixel 2 XL.
https://www.androidfilehost.com/?fid=1899786940962594367
Click to expand...
Click to collapse
Yeah, I remember those days. Thanks for the image. Can it be flashed in TWRP or strictly adb/fastboot?
Sent from my Pixel 2 XL using Tapatalk
Alxoom33 said:
Yeah, I remember those days. Thanks for the image. Can it be flashed in TWRP or strictly adb/fastboot?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I've only used fastboot.
Tulsadiver said:
Here is a fastboot bootable image to boot you into Magisk core-only mode. If you bootloop due to flashing a bad module, in fastboot:
fastboot boot image-new.img
You will boot with root but modules disabled.
Tested by me and @123SIT whom contributed on the project.
Made from Pixel 3 XL but should work on the Pixel 3 also.
Image
https://mega.nz/#!NE5yGaBA!0HLSWvdD4x4cOmo35HrDGrGNxTAUGW4LpkpVv1ygwVI
Thanks to @ApeironTsuka for his guide and everyone on the Magisk support thread like @jcmm11 for their patience and help.
Click to expand...
Click to collapse
can't reach the mega link, can you guys please upload it somewhere else please? I am stuck on bootloop as I 'm typing...
FcukBloat said:
can't reach the mega link, can you guys please upload it somewhere else please? I am stuck on bootloop as I 'm typing...
Click to expand...
Click to collapse
Here is a link to it on my GDrive. Can you please let me know when you've got it so I can delete it?
https://drive.google.com/file/d/1rg5wENhILz8ah8jSdLne2OtaLYGOhdBI/view?usp=sharing
sliding_billy said:
Here is a link to it on my GDrive. Can you please let me know when you've got it so I can delete it?
https://drive.google.com/file/d/1rg5wENhILz8ah8jSdLne2OtaLYGOhdBI/view?usp=sharing
Click to expand...
Click to collapse
got it! thanks this time too!
FcukBloat said:
got it! thanks this time too!
Click to expand...
Click to collapse
No problem. It's good to be a pack rat. I hope it worked.
FcukBloat said:
can't reach the mega link, can you guys please upload it somewhere else please? I am stuck on bootloop as I 'm typing...
Click to expand...
Click to collapse
Mega link seems to be working. Open with chrome, not mega app.
Edit: I've added a AFH download link.
i tried with chromium based browser (vivaldi) from both phone and pc and link didn't work, probably it was a WiFi problem, thanks for adding alternative link though. and your core mode image worked like a charme! and thanks again also to sliding billy for initial mirror support
Just what I needed. Thank you
How did you create it? I want to make sure I have one of these images on hand in the future when I need to fix things
Simply works, thank you!
Holy cow, thanks man. I can't believe @topjohnwu let this slide through. Without TWRP wtf are you supposed to do, reflash the whole OTA/factory image?!
EDIT: Wait, now I can boot and apparently have root but I can't access any of my rooted apps. It says "waiting for root". Magisk Manager gives me an "app not installed" error but it is installed on the device. When I click it it says "upgrade to full Magisk Manager" and does nothing. How am I supposed to delete the module folder?
EDIT: Can't access terminal, can't do anything. Permission denied via ADB as well.
EDIT: DO NOT DELETE MAGISK MANAGER OR ALTER IT IN ANY WAY WHEN USING CORE MODE. You will be stuck like me. I had to nuke my phone and reflash everything. PIA

Categories

Resources