Related
hi guys
I tried to install a custom rom on my HTC One X PLUS. I am new to this and it looks like i kinda screwed up. i used "HTC One X+ AIO Kit By Hasoon2000 v2.3". I have now this "CWM-based Recovery v6.0.2.7" on my phone. i can't boot the normal OS anymore. everytime i reboot, this cwm recovery shows up. when i try to install cyanogenmod (cm-11-20140705-NIGHTLY-enrc2b.zip) by "install zip from sdcard => choose zip from sdcard ==> ..." i just receive:
Code:
set_metadata_recursive: some changes failed
E:Error in /sdcard/0/cm-11-20140705-NIGHTLY-enrc2b.zip
(Status 7)
Installation aborted.
i have no idea what to do. can anyone pls help? is it still possible to reset everything to get my phone working again?
Flash the latest version, older ones can't flash kitkat ROMs
http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.4.8-enrc2b.img
Sent from my One X+ using Tapatalk
Phoenix09 said:
Flash the latest version, older ones can't flash kitkat ROMs
Click to expand...
Click to collapse
How can i do this? i can't put the file on my phone because my phone doesn't have a sd card.
Hutschi93 said:
How can i do this? i can't put the file on my phone because my phone doesn't have a sd card.
Click to expand...
Click to collapse
check this out http://forum.xda-developers.com/showthread.php?t=2066390 read it all, the part you need is adb sideloading, again, read it all at least a few times
leefear said:
check this out http://forum.xda-developers.com/showthread.php?t=2066390 read it all, the part you need is adb sideloading, again, read it all at least a few times
Click to expand...
Click to collapse
i already tried that, but all i get is this error:
Code:
* failed to write data 'protocol fault (no status)' *
my phone is in this "sideload mode" and i changed the filename into one word (that's what i should do if i get an error)
Hutschi93 said:
i already tried that, but all i get is this error:
Code:
* failed to write data 'protocol fault (no status)' *
my phone is in this "sideload mode" and i changed the filename into one word (that's what i should do if i get an error)
Click to expand...
Click to collapse
did you flash the recovery that phoenix suggested?
leefear said:
did you flash the recovery that phoenix suggested?
Click to expand...
Click to collapse
how? i just can open this cwm based recovery mode or this strangely HBOOT mode. but my computer doesn't really recognize it. if i open the device manager i see it under "ADB Interface" as "HTC Bootloader" but if use "adb devices" in command prompt my phone does not get recognized. the toolkit doesn't recongize it either.
OK guys i got my computer to recognize my phone in recovery mode. i can use adb push to transfer files to my phone. do i have to flash a new recovery or can a just put a new rom on my phone and try installing that?
EDIT:
OK GUYS! thanks to that i got my computer to recognize my phone i could flash the recovery phoenix suggested! and i finally could install my rom! thank you sooo much guys! you are my hero and made my day! i would give you a hug if i could but i guess nobody of you lives in switzerland
love you guys! (no homo)
Hutschi93 said:
OK guys i got my computer to recognize my phone in recovery mode. i can use adb push to transfer files to my phone. do i have to flash a new recovery or can a just put a new rom on my phone and try installing that?
EDIT:
OK GUYS! thanks to that i got my computer to recognize my phone i could flash the recovery phoenix suggested! and i finally could install my rom! thank you sooo much guys! you are my hero and made my day! i would give you a hug if i could but i guess nobody of you lives in switzerland
love you guys! (no homo)
Click to expand...
Click to collapse
glad u got it working bud!
Okay xda, I'm in a bit of a pickle here. Last night I tried to flash the Siyah kernel, Siyah-s3-v1.9.1.tar using Odin3 v3.09 on my Galaxy S3 which was currently running Android 4.4.2 on Slimkat, with stock everything else. As soon as I tried this I knew it was completely the wrong thing and knew something was going to go wrong. Sure enough, the Siyah splash screen comes on for a couple of seconds, then goes to a black screen and gets stuck there.
At this point all I can do is watch it do a couple of seconds of the splash screen, put it into Download mode, or put it into recovery mode. The first time I tried recovery mode it was the CWM recovery, but I can no longer get this to happen, so I'm stuck with stock recovery. When just plugged in my phone has a red LED, and the battery status screen you get when you start charging a turned off phone comes up.
I read a guide on here about how to fix a failed flashing with Odin (I forget which one), which led me to flashing I9300XXUGMK6_I9300OXAGMK6_I9300XXUGMK6_HOME.tar.md5 I believe, or if that's not it the stock Samsung firmware. So that goes down, and now I get stuck in the stock Samsung bootloader.
I've since tried to flash a .zip of Stock samsung firmware and Cyanogenmod 11 with another phone's SD card (which I no longer have access to), to no avail. At least that hasn't made it any worse.
What should I do? Ideally I want to get my phone back without losing any data, but I feel a reset may be the only way. Eventually, I want to be able to use it on Cyanogenmod11 with the Boeffla kernel.
Thanks!
Do you get any error messages in stock recovery?
ArkThompson said:
Do you get any error messages in stock recovery?
Click to expand...
Click to collapse
When I first get into it it says on the bottom
# MANUAL MODE #
-- Applying Multi-CSC....
Applied the CSC-code : BIU
Successfully applied multu-CSC.
Which I assume is normal. I can't check again, but I did get an error while flashing CM11 which went very similarly to
Finding update package ...
Opening update package ...
Verifiyng update package ...
E: failed to verify whole-file signature
E: signature verification failed
I can't flash .zip files from External Storage at the moment, so other suggestions would be preferred.
I did try converting .zip files into .tar files with 7z but I don't think it was successful.
Obesidia said:
When I first get into it it says on the bottom
# MANUAL MODE #
-- Applying Multi-CSC....
Applied the CSC-code : BIU
Successfully applied multu-CSC.
Which I assume is normal. I can't check again, but I did get an error while flashing CM11 which went very similarly to
Finding update package ...
Opening update package ...
Verifiyng update package ...
E: failed to verify whole-file signature
E: signature verification failed
I can't flash .zip files from External Storage at the moment, so other suggestions would be preferred.
I did try converting .zip files into .tar files with 7z but I don't think it was successful.
Click to expand...
Click to collapse
You're trying to flash custom ROMs in the stock recovery?
ArkThompson said:
You're trying to flash custom ROMs in the stock recovery?
Click to expand...
Click to collapse
Pretty much, yeah, I was trying anything.
What next?
Obesidia said:
Pretty much, yeah, I was trying anything.
What next?
Click to expand...
Click to collapse
You need a custom recovery to flash custom ROMs. You could try flashing one in Odin and then flashing a stock ROM .zip using the recovery.
ArkThompson said:
You need a custom recovery to flash custom ROMs. You could try flashing one in Odin and then flashing a stock ROM .zip using the recovery.
Click to expand...
Click to collapse
I'll try that, but how do I get the .zip file in the right place to install from SD Card?
Obesidia said:
I'll try that, but how do I get the .zip file in the right place to install from SD Card?
Click to expand...
Click to collapse
Use ADB (USB debugging is enabled by default in custom recoveries).
ArkThompson said:
Use ADB (USB debugging is enabled by default in custom recoveries).
Click to expand...
Click to collapse
Okay thanks! I'll try that and get back.
ArkThompson said:
Use ADB (USB debugging is enabled by default in custom recoveries).
Click to expand...
Click to collapse
First time doing this, and I have discovered I have no idea what to do. I'm using
http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android
as a guide but I don't even know how to open the adb so I can input something into the command line.
Obesidia said:
First time doing this, and I have discovered I have no idea what to do. I'm using
http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android
as a guide but I don't even know how to open the adb so I can input something into the command line.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2141817
You need to use the adb push command to move the file onto your phone. You just use cmd (type cmd into run and press enter).
ArkThompson said:
http://forum.xda-developers.com/showthread.php?t=2141817
You need to use the adb push command to move the file onto your phone. You just use cmd (type cmd into run and press enter).
Click to expand...
Click to collapse
I tried that but I got an error about the file locations. I think it's because there was a space in the one of the folder names, or at least that's what the command line suggested; it basically said "could not push file to '...\Desktop\Fix'" but the folder is called Fix phone.
I was about to rename the folder and move it to C:\ but I just went to reboot the phone in cwm recovery and it said DOES NOT HAVE ROOT ACCESS. ROOT NOW?
I selected yes and it rebooted as normal and got stuck in the samsung boot animation, so no progress there.
I have a backup in CWM recovery from a couple of months ago, I've just found but obviously doing that would lose all my recent pictures and messages. There isn't really a way to get them back by continuing with this method, is there?
Obesidia said:
I tried that but I got an error about the file locations. I think it's because there was a space in the one of the folder names, or at least that's what the command line suggested; it basically said "could not push file to '...\Desktop\Fix'" but the folder is called Fix phone.
I was about to rename the folder and move it to C:\ but I just went to reboot the phone in cwm recovery and it said DOES NOT HAVE ROOT ACCESS. ROOT NOW?
I selected yes and it rebooted as normal and got stuck in the samsung boot animation, so no progress there.
I have a backup in CWM recovery from a couple of months ago, I've just found but obviously doing that would lose all my recent pictures and messages. There isn't really a way to get them back by continuing with this method, is there?
Click to expand...
Click to collapse
I think you probably lost your messages when you flashed a stock ROM with Odin. Your pictures could be ok, check with adb and pull them if they are still there.
Hello all,
yesterday's OTA firmware update to my CAT B15Q (CPU MediaTek MT6582M) showed an error similar to "failed to update metadata symlink" and offered me to reboot... since then the device is stuck in a bootloop and only boots recovery and fastboot.
The recovery console doesn't offer any USB devices, except when choosing "apply update from ADB", upon which adb devices lists it as "0123456789ABCDEF sideload". adb shell however does not work, it gives an "error: closed" message.
Resetting to factory did not help either, current Android version of the device was 4.4.2.
By the looks, the failed update bricked the /system somehow; can I sideload a version of adb onto the recovery to gain shell access?
Thanks!
harddisk_wp said:
Hello all,
yesterday's OTA firmware update to my CAT B15Q (CPU MediaTek MT6582M) showed an error similar to "failed to update metadata symlink" and offered me to reboot... since then the device is stuck in a bootloop and only boots recovery and fastboot.
The recovery console doesn't offer any USB devices, except when choosing "apply update from ADB", upon which adb devices lists it as "0123456789ABCDEF sideload". adb shell however does not work, it gives an "error: closed" message.
Resetting to factory did not help either, current Android version of the device was 4.4.2.
By the looks, the failed update bricked the /system somehow; can I sideload a version of adb onto the recovery to gain shell access?
Thanks!
Click to expand...
Click to collapse
Same thing happened to me!
Thank you in advance.
Please let me know if you found the solution.
Chegger said:
Same thing happened to me!
Thank you in advance.
Please let me know if you found the solution.
Click to expand...
Click to collapse
Not the solution, but maybe a cause... did you root your device?
harddisk_wp said:
Hello all,
yesterday's OTA firmware update to my CAT B15Q (CPU MediaTek MT6582M) showed an error similar to "failed to update metadata symlink" and offered me to reboot... since then the device is stuck in a bootloop and only boots recovery and fastboot.
The recovery console doesn't offer any USB devices, except when choosing "apply update from ADB", upon which adb devices lists it as "0123456789ABCDEF sideload". adb shell however does not work, it gives an "error: closed" message.
Resetting to factory did not help either, current Android version of the device was 4.4.2.
By the looks, the failed update bricked the /system somehow; can I sideload a version of adb onto the recovery to gain shell access?
Thanks!
Click to expand...
Click to collapse
Hey my little brother just had the same problem but I managed to get the fone to boot took the battery out held Down volume down and 3 mins later it booted
harddisk_wp said:
Not the solution, but maybe a cause... did you root your device?
Click to expand...
Click to collapse
Yes I did.
I also thought that was the problem.
delox88 said:
Hey my little brother just had the same problem but I managed to get the fone to boot took the battery out held Down volume down and 3 mins later it booted
Click to expand...
Click to collapse
Can you elaborate?
Do you hold before and while turning on?
Did you hold with the battery Out with charger?
I tried to hold while booting but it just stays in the inicial image forever.
Thanks.
Chegger said:
Can you elaborate?
Do you hold before and while turning on?
Did you hold with the battery Out with charger?
I tried to hold while booting but it just stays in the inicial image forever.
Thanks.
Click to expand...
Click to collapse
Ha, same for me. Even adb comes halfway up (adb device shows up in windows' device manager, but "unauthorized", so no shell/pull/push), but it doesn't progress beyond the loading image.
Can anyone with a working B15Q please execute the command "cat /proc/mtd" in a shell or do a full(!) backup using mtkdroidtool?! I pledge €20 via Paypal to the first one who submits all of the partitions except /data up to Mega or another OCH.
harddisk_wp said:
Ha, same for me. Even adb comes halfway up (adb device shows up in windows' device manager, but "unauthorized", so no shell/pull/push), but it doesn't progress beyond the loading image.
Can anyone with a working B15Q please execute the command "cat /proc/mtd" in a shell or do a full(!) backup using mtkdroidtool?! I pledge €20 via Paypal to the first one who submits all of the partitions except /data up to Mega or another OCH.
Click to expand...
Click to collapse
At least you know this stuff that's half way trough.
I will post this in the original root thread since I already posted the issue there and they are now replying ( I will mention you).
http://forum.xda-developers.com/general/rooting-roms/root-achieved-cat-b15q-t2822015/page11
My phone bricked after updating to 1.1019.000
I was lucky enough to save the whole ROM to a file before updating.
The problem for me was the original recovery.
My solution was to install the new 1.1019.000 recovery on my original ROM and then updated to the new (1.1019.000) firmware.
Give me your mail and i will send you the 1.1019.000 recovery. I have the whole ROM but it´s to large and i am to lazy to upload
bigal1337 said:
My phone bricked after updating to 1.1019.000
I was lucky enough to save the whole ROM to a file before updating.
The problem for me was the original recovery.
My solution was to install the new 1.1019.000 recovery on my original ROM and then updated to the new (1.1019.000) firmware.
Give me your mail and i will send you the 1.1019.000 recovery. I have the whole ROM but it´s to large and i am to lazy to upload
Click to expand...
Click to collapse
I've the same problem - b15q is bricked - device was rooted to be able to use link2sd.
bigal1337 said:
My phone bricked after updating to 1.1019.000
I was lucky enough to save the whole ROM to a file before updating.
The problem for me was the original recovery.
My solution was to install the new 1.1019.000 recovery on my original ROM and then updated to the new (1.1019.000) firmware.
Give me your mail and i will send you the 1.1019.000 recovery. I have the whole ROM but it´s to large and i am to lazy to upload
Click to expand...
Click to collapse
I've witten you a PM - please send me your original ROM - or could you send me a link where i may download it.
huedlrick said:
I've the same problem - b15q is bricked - device was rooted to be able to use link2sd.
Click to expand...
Click to collapse
Another one here! Were you able to use link2sd after rooting the phone? Link2sd gave me a mount error when I tried to mount my sd card's 2nd ext3 partition.
Many ppl wanted the stock rom. So i uploaded it to my google drive. It´s a E01 so beware those of you who has B01 or something else.
Original 1.1010.000 rom in files with scatterfile
1.1019.000 Recovery
Original 1.1019.000 update
Scatter file
To flash the phone you only need the bootimg, recovery,android and scatterfile.
(Edit: I dont have google drive anymore)
bigal1337 said:
Many ppl wanted the stock rom. So i uploaded it to my google drive. It´s a E01 so beware those of you who has B01 or something else.
Original 1.1010.000 rom in files with scatterfile https : // drive . google . com /file/d/0ByVAMsMZdC8bdEIxWlpBeXBHNUE/view?usp=sharing
1.1019.000 Recovery https : // drive . google . com /file/d/0ByVAMsMZdC8bVXU2RzBGalV0S1U/view?usp=sharing
Original 1.1019.000 update https : // drive . google . com /file/d/0ByVAMsMZdC8bbWQ4dmhSZWVxZVE/view?usp=sharing
Scatter file https : // drive . google . com /file/d/0ByVAMsMZdC8bSkRhREEwakNhUWc/view?usp=sharing
To flash the phone you only need the bootimg, recovery,android and scatterfile.
Click to expand...
Click to collapse
Thank you very much - but how can I determine if my phone is E01/B01 without being able to boot it?
So, I can confirm that reflashing your ANDROID/RECOVERY/BOOTIMG unbricked my European B15Q!
harddisk_wp said:
So, I can confirm that reflashing your ANDROID/RECOVERY/BOOTIMG unbricked my European B15Q!
Click to expand...
Click to collapse
Great and congrats.
Could you, please, describe the process and which files did you use.
Thanks.
harddisk_wp said:
So, I can confirm that reflashing your ANDROID/RECOVERY/BOOTIMG unbricked my European B15Q!
Click to expand...
Click to collapse
Can you give some hints how you unbricked it? What tools and commands have to be entered?
Best regards,
Doggy77
Uploads are not done yet. But you can prepare until I'm done... grab the driver package, spFlashTool and the 1.022 RAR from http://forum.xda-developers.com/general/general/stock-rom-cat-b15q-rom-development-t2988774.
You will need a win7 x86 machine for this to work (64-bit systems will need to disable the driver signature enforcement, but this is unreliable), and latest(!) WinRAR for unpacking.
The full backup of your device will take up ~1.5 GB, so you will need at least 3GB free and another 2GB if you also want to backup your userdata (HIGHLY RECOMMENDED).
"PMT changed for the ROM; it must be downloaded"
I'm trying to flash the files of harddisk_wp with his instructions but i keep getting the error "PMT changed for the ROM; it must be downloaded", right after I connect the phone and SP Flash Tool finishes "Download DA". I am trying with the 64bit drivers since I do not have a 32bit system, with digital signature verification disabled.
After some search, I saw in the log files that SP Flash Tool is reading the partition table on the phone and comparing it to the scatter file. There is a mismatch there and throws this exception. Now either the driver is not working correct and does not report the partition table right or there is something else going on. Anybody tried this on a 64bit system? Any ideas?
BTW the scatter file is correct for my phone. I had downloaded it myself also before the bricking and I compared it with harddisk_wp's one. They are identical.
In all other aspects SP Flash Tool works fine, I read the user partition for backup without problems.
walckenaerius said:
In all other aspects SP Flash Tool works fine, I read the user partition for backup without problems.
Click to expand...
Click to collapse
SPFT worked for me good to resurrect the phone with files from 1010 version (first firmware) raw partitions.
Phone came back to last user backup and booted fine.
I applied newer and suggested 1019 update that had bricked the phone even further into the loop of the booting logo stuck and rebooting.
SPFT tool memory scan showed that there is no NAND present. I assume that there is PRELOADER damaged. By trying to flush raw PRELOADER that was a no go area. Connection made red line on 100% and nothing happens after that.
SPFT stopped making connection via USB. Inserting the battery, power on - it didn't came back at all.
Phone is now dead black brick that on Linux shows: as MediaTek Inc. MT6227 phone.
In any case do not try to make the same mistake like me.
I will check if it works on some other Windows machine.
Not being Windows user I cannot tell if it is in USB driver or not.
Used W7 without admin pass, with MTKUsbAll driver.
Eh.
Hello,
I was wondering if some could help me please. I wanted to flash RR Rom 6.0 on my BLA-L09(I think that what's it is) phone.
I was able to unlock my boot loader, and flash TWRP my device but my dumb s*** flashed TWRP to my file system use FLASH SYSTEM instead of FLASH RECOVERY. Now, I can't fix it ?. I know I can use sideload so I'm not panicking just yet however I know I messed up the file system.
Could someone tell me what file system system I should be using (fat, exfat, ext4, etc...) and what to do to get this think to boot backup.?
I've tried and side loading "update_full_BLA-L29_hw_la.zip" stock ROM but no luck... I keep getting this error message:
"check_write_data_to_partition,write data error
Update_huawei_pkg_from_ota_zip: update package from zip failed
Updated process ended with error: 9"
HELP.!!!
me too..... following searching for a solution
Shandroid_94 said:
me too..... following searching for a solution
Click to expand...
Click to collapse
If you find anything, let me know.!
Just boot to fastboot, flash RR to system and TWRP to recovery_ramdisk?
Hi guys, sorry if my post is not in the right place, it is the first time for me and please forgive my english which is not very good.
Yesterday I rooted my phone with magisk and everything went well. I wanted to install Viper4android but each time my phone restarted after installation I was stuck in fastboot mode.
So I went into recovery mode and I reset the phone. having done it several times I wanted to install TWRP via the ADB command to have a "better" recovery mod (yes im silly). I did **** and since I am stuck in fastboot but this time without the possibility of recovery mod, when I try to get there, my phone restarts and brings me back to fastboot.
My pc no longer seems to detect my phone.
Is there a solution where is this the end for me?
Thanks for your advices
EDIT : Ok so i just managed to install TWRP on my phone but when I want to make a wipe I have the following message:
failed to mount '/ sytem' (invalid argument)
failed to mount '/ vendor' (invalid argument)
failed to mount '/ product' (invalid argument)
what can I do ?
Amiral12 said:
Hi guys, sorry if my post is not in the right place, it is the first time for me and please forgive my english which is not very good.
Yesterday I rooted my phone with magisk and everything went well. I wanted to install Viper4android but each time my phone restarted after installation I was stuck in fastboot mode.
So I went into recovery mode and I reset the phone. having done it several times I wanted to install TWRP via the ADB command to have a "better" recovery mod (yes im silly). I did **** and since I am stuck in fastboot but this time without the possibility of recovery mod, when I try to get there, my phone restarts and brings me back to fastboot.
My pc no longer seems to detect my phone.
Is there a solution where is this the end for me?
Thanks for your advices
EDIT : Ok so i just managed to install TWRP on my phone but when I want to make a wipe I have the following message:
failed to mount '/ sytem' (invalid argument)
failed to mount '/ vendor' (invalid argument)
failed to mount '/ product' (invalid argument)
what can I do ?
Click to expand...
Click to collapse
You are complicating everything. Simply download fastboot rom: https://androidfilehost.com/?fid=4349826312261697682
extract it and connect mobile while launching flash.all script from firmware folder
Sorry im noob ^^'
thank u, how and where can i launch ur file ?
Amiral12 said:
Sorry im noob ^^'
thank u, how and where can i launch ur file ?
Click to expand...
Click to collapse
Inside folder named "10.0.5-GLOBAL-OnePlus7TProOxygen_14.O.11_OTA_011_all_1912060100_3029-FASTBOOT". Extract it, and run file "flash-all".
At first, it will ask you if you want to wipe data Y(es) or N(o), tap Y, hit enter and wait until device reboot.
And remember you need to be in fastboot mode all the time.
EugenStanis said:
Inside folder named "10.0.5-GLOBAL-OnePlus7TProOxygen_14.O.11_OTA_011_all_1912060100_3029-FASTBOOT". Extract it, and run file "flash-all".
At first, it will ask you if you want to wipe data Y(es) or N(o), tap Y, hit enter and wait until device reboot.
And remember you need to be in fastboot mode all the time.
Click to expand...
Click to collapse
man i love you so much....
you are the best
Thanks :highfive:
Amiral12 said:
man i love you so much....
you are the best
Thanks :highfive:
Click to expand...
Click to collapse
No problem bruh
EugenStanis said:
No problem bruh
Click to expand...
Click to collapse
If its okay for you could you teach me how to install Viper4android now ? or should i create a new post ?
Or maybe i should just give up and use my phone like a regular person
Amiral12 said:
If its okay for you could you teach me how to install Viper4android now ? or should i create a new post ?
Or maybe i should just give up and use my phone like a regular person
Click to expand...
Click to collapse
Don't use TWRP, I'm just throwing it out there, it's not working.
Check themes section for install viper4android
Sent from my OnePlus7TPro using XDA Labs
Lossyx said:
Don't use TWRP, I'm just throwing it out there, it's not working.
Check themes section for install viper4android
Click to expand...
Click to collapse
I second that. There is no point of TWRP right now. Also, viper may or may not be fully working on this phone either...I have not attempted to install it. There is a guide/post somewhere though that talks about it. Also, from experience when I did use viper on my pixel 2, I would have the same problem and my phone wouldn't boot. To get around that problem, I simply installed magisk again and then it was fine. It was like that for a while until viper was fully compatible.
js042507 said:
I second that. There is no point of TWRP right now. Also, viper may or may not be fully working on this phone either...I have not attempted to install it. There is a guide/post somewhere though that talks about it. Also, from experience when I did use viper on my pixel 2, I would have the same problem and my phone wouldn't boot. To get around that problem, I simply installed magisk again and then it was fine. It was like that for a while until viper was fully compatible.
Click to expand...
Click to collapse
The guide shows how to workaround the bootloop.
It's related to SELinux, which hopefully has now been fixed in the latest magisk update. But it requires a module template update which the viper4android devs are working to update.
It should be working soon without any workaround/tricks.
Sent from my OnePlus7TPro using XDA Labs
Thanks for all ur replies guys,
I think I will just wait for the viper4android update to install it easier