Related
Hello people,
First I'd like to thank everyone contributing on this forum, the posts here have made it possible for a beginner like I am to have a rooted phone.
I am posting this after trying in vain to find a solution to an issue I'm having with permissions on my Ascend Y300.
I rooted it and had CM 10.2 running smoothly for over a month while updating to nightly builds. After one of these updates I accidentally did a full advanced wipe in TWRP v2.5.0.1., but re-installed the rom and all seemed well. Then I started having "insufficient space available" notifications when trying to install apps from Google Play, despite having plenty of space available on both the internal and external SD. I reinstalled the rom, wiping only cache and dalvik this time. This time I couldn't download anything due to low space.
Looking into the problem I tried to delete the dump files in \data but when trying to reach that folder, whether via shell or the file manager in CM, I would get denied access due to permissions. I tried through TWRP's file manager and terminal but ran into the same problem.
I did a full system wipe again out of frustration, then tried Fix Permissions in TWRP. Am getting this as a result:
Can't check permissions after Factory Reset.
Please boot rom and try again after you reboot into recovery.
Done.
Failed
Click to expand...
Click to collapse
Then I tried to flash the rom I had before, which failed with the following message:
set_perm: some changes failed
E:Error executing updater binary in zip '/sdcard (truncated)
Error flashing zip '/sdcard/cm-10.2.......
Failed
Click to expand...
Click to collapse
I tried to sideload my rom as well, to no avail (permissions error).
Basically, TWRP is telling me that I need to install a rom to fix permissions, but I need to fix permissions to install a rom.
I tried to restore settings in TWRP: clicking the option freezes the phone. Perhaps I could flash an update to TWRP which has fixed permissions? However I cannot access the Fastboot menu on my Y300: I can either get the recovery menu, the purple screen, or a freeze on the Huawei logo which shows up as "unauthorized device" when checking devices in cmd (the bootloader is unlocked).
All I would like to achieve is having CM running normally, allowing me to download a few apps from the Play Store.
Thank you for reading! Any advice is greatly appreciated, especially as I use this phone for work (luckily all this is happening over my Christmas leave!).
Cheers
Update: through fastboot I managed to update TWRP to the latest version, flash the stock rom for the Y300, and because I have a system installed I was also able to Fix Permissions in TWRP.
When I install supersu I get a "successful" result, however I still get the following error when trying to flash a CM 10.2 rom:
set_perm: some changes failed
E:Error executing updater binary in zip '/sdcard (truncated)
Error flashing zip '/sdcard/cm-10.2.......
Failed
Click to expand...
Click to collapse
Anybody know how to give full permissions to TWRP?
Thanks.
P.S. Merry Christmas!
Hi.
This is my first post, I hope i'm in the correct forum.
I have a friend whom I requested to Root, Flash TWRP and Install LineagOS and GAAP on my OnePlus One phone.
He successfully flashed TWRP and installed LineagOS & GAAP but could not root my OnePlus One using SuperSu. He mentioned permission issue trying to root.
He went back to his country, so I am stuck trying to root my phone.
I would like to root my LineagOS (formally OnePlus One) using SuperSU.
I have downloaded/copied the latest SuperSu zip file into the Phone Sd/Download folder.
I went into custom recovery (TWRP).
Click on the Install button and verified I can see my SuperSu zip file.
Since this is my first time performing a phone root, I did not click SuperSu zip to install, until some experts can assist. me.
Just a few (Q's).
Questions:
a) Should I run any preliminary steps prior to clicking install SuperSu.zip?
b) Since I have LineagOS, GAAP apps already installed, will they be wiped after rooting SuperSu. If (Yes), any software available to backup/restore LineagOS & GAAP prior to the root process?
c) My friend mention “Permission problems with OPO”. Are there some options to open OPO and allow rooting SuperSu?
BTW: I do have the adb & fastboot installed if I need to enter some commands to get this done.
Thanks.
Tom.
a) No.
Download flashable supersu zip and flash it from here and flash it via TWRP https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
b) No.
But you can take nandroid backup through twrp in case something goes wrong.
c) As far as I know there is no problem with "permission" for rooting.
Happy flashing
Hi psxda97.
I did your requested instructions, but still not Rooted.
Here are the steps I did:
1) Downloaded the latest SuperSu zip from XDA and copied to Sd/Download folder on my phone.
2) Went into Custom Recovery TWRP) on my phone.
3) Click Install, selected SuperSu.zip Swipe bar to continue.
Completed 181 seconds did not see errors.
4) Wiped Dalvic & Cache. Reboot the Phone.
When phone restarted I went into Titanium backup apps to test if Root was successful. Received error msg from Titanium "Could not acquire root privileges. This app will not work Verify your Rom is rooted and try again"
Not sure if this makes a difference: in Developers Option I had root access ADP Only enabled & allow Unknown Sources set off.
Since this is the second time running SuperSu should I needed to wipe any files before rooting?
I'll await you reply.
Thanks.
Tom.
tomx2x said:
Hi psxda97.
I did your requested instructions, but still not Rooted.
Here are the steps I did:
1) Downloaded the latest SuperSu zip from XDA and copied to Sd/Download folder on my phone.
2) Went into Custom Recovery TWRP) on my phone.
3) Click Install, selected SuperSu.zip Swipe bar to continue.
Completed 181 seconds did not see errors.
4) Wiped Dalvic & Cache. Reboot the Phone.
When phone restarted I went into Titanium backup apps to test if Root was successful. Received error msg from Titanium "Could not acquire root privileges. This app will not work Verify your Rom is rooted and try again"
Not sure if this makes a difference: in Developers Option I had root access ADP Only enabled & allow Unknown Sources set off.
Since this is the second time running SuperSu should I needed to wipe any files before rooting?
I'll await you reply.
Thanks.
Tom.
Click to expand...
Click to collapse
I think I'm missing something. Did you tried any other method to root? I recommend a clean flash.
1. Download Sultanxda's unofficial lineageOS from here
2. Download Gapps from here. ( ARM-7.1-nano)
3.Download SuperSU from here
4. [Optional] take back up of your apps (No need to back up medias like photo,video,etc)
5.Got Recovery>wipe>advanced wipe
select system,data,cache and dalvik cache (DO NOT SELECT INTERNAL)
6.flash the zips you already downloaded in this order - ROM- Gapps - SuperSU
do not wipe anything after this step
7.Reboot
1st reboot will take some time (10-20 min ). Do not interrupt this process.
PS: I totally recommend Sultan's LineageOS over official LOS. You can actually feel the difference in smoothness and performance. Especially the Camera.
Feel free to check device specific forum for OnePlus One
Happy flashing!
@psxda97.
Thanks for the quick reply.
OK, I'm going to start from scratch as you requested.
When I try to download SuperSu (from your link above) located in Google Play, I get “supersu already installed for your device”.
Did not find SuperSu in Phone Apps settings.
Went into TWRP File Manager \ supersu folder. Deleted all (4) entries.
Rebooted.
Went back into TWRP. The 4 entries reappear.
Google Play continues to gray out my device name. SuperSu is already installed.
I do have a SuperSu zip file on my PC. I installed this on my last attempt. It appears to be the same as Google Play.
Here is the name:
“C:\Users\Tomx\Downloads\SR1-SuperSU-v2.82-SR1-20170608224931.zip\”
Should I go with this?
Tom.
tomx2x said:
@psxda97.
Thanks for the quick reply.
OK, I'm going to start from scratch as you requested.
When I try to download SuperSu (from your link above) located in Google Play, I get “supersu already installed for your device”.
Did not find SuperSu in Phone Apps settings.
Went into TWRP File Manager \ supersu folder. Deleted all (4) entries.
Rebooted.
Went back into TWRP. The 4 entries reappear.
Google Play continues to gray out my device name. SuperSu is already installed.
I do have a SuperSu zip file on my PC. I installed this on my last attempt. It appears to be the same as Google Play.
Here is the name:
“C:\Users\Tomx\Downloads\SR1-SuperSU-v2.82-SR1-20170608224931.zip\”
Should I go with this?
Tom.
Click to expand...
Click to collapse
Yes. Copy all 3 zip (rom,gapps,supersu) to you phone.
Let me know how it goes..
@psxda97
Ok, I followed your steps 1-7.
Instructions completed successfully.
After setting up LineageOS and my Google acct I downloaded Titanium Backup.
Clicked on the app and received same error message stated in my previous post.
Is there another option/app to check if my phone is rooted?
I notice when I logoff from TWRP, I get this message displayed “Your device does not appear to be rooted Install SuperSU now This will root your device?“ There is a button to Install.
XDA put out a notice this is a bogus message and do not install.
“Sometimes, TWRP can’t detect that you already have SuperSU, so it’ll ask to flash its built-in version. But it’s almost always best to flash the latest version of SuperSU yourself “
In TWRP file manager\supersu folder contains 4 files.
99SuperSuDaemon, install-recovery.sh, su, Superuser.apk.
Are these the Built in version of supersu?
If you have other suggestions, let me know – Thanks for your help.
Tom.
tomx2x said:
@psxda97
Ok, I followed your steps 1-7.
Instructions completed successfully.
After setting up LineageOS and my Google acct I downloaded Titanium Backup.
Clicked on the app and received same error message stated in my previous post.
Is there another option/app to check if my phone is rooted?
I notice when I logoff from TWRP, I get this message displayed “Your device does not appear to be rooted Install SuperSU now This will root your device?“ There is a button to Install.
XDA put out a notice this is a bogus message and do not install.
“Sometimes, TWRP can’t detect that you already have SuperSU, so it’ll ask to flash its built-in version. But it’s almost always best to flash the latest version of SuperSU yourself “
In TWRP file manager\supersu folder contains 4 files.
99SuperSuDaemon, install-recovery.sh, su, Superuser.apk.
Are these the Built in version of supersu?
If you have other suggestions, let me know – Thanks for your help.
Tom.
Click to expand...
Click to collapse
Can you send me a screenshot of supersu app?
I'm using the exact settings and I don't have any problem at all.
Do not let TWRP install supersu.
@psxda97
As you know the Supersu is a zip file. When I open/ then extract, the display will show folders & their contents.
I have attached all the folders & contents from supersu extract for your review.
To get a screenshot maybe you can walk me through this step.
The only way I can think of is to find & download the SuperSu apk file (for this version) onto my phone and open it to get a visual screenshot of the app.
Here is the website link where I downloaded SuperSu 2 days ago.
" https://download.chainfire.eu/1114/...r&utm_medium=referral&utm_source=DonanimHaber “
tomx2x said:
To get a screenshot maybe you can walk me through this step.
The only way I can think of is to find & download the SuperSu apk file (for this version) onto my phone and open it to get a visual screenshot of the app.
Click to expand...
Click to collapse
I meant this
Edit : So you've no supersu app on you phone?
@psxda97
Maybe that's my problem. I do not have supersu on my phone application. (see my attached).
Here' what I do.
1. Download supersu zip file from website to my PC.
2. Connect PC to phone.
3. I do not extract the supersu.zip on my PC, I just manually copy the supersu.zip (as is) to Download folder (A0001) of my Phone.
4. Logoff off phone.
5. Get into TWRP. Click Install. Click supersu zip.
6. Reboot, when finish, run Titanium Backup on phone to check for root.
Should supersu app be on my phone after installation/rebooting?
Somehow it's not doing the root, even though it completes successfully in TWRP. Strange.
Tom.
tomx2x said:
[MENTION=7046372]
Should supersu app be on my phone after installation/rebooting?
Tom.
Click to expand...
Click to collapse
Yes.
Go to recover and flash it one more time
Then go to Advanced on twrp and select copy log (without kernel log).
Log will be on root folder of internal. attach the log in your next post
Also send me the screenshot of your about phone settings.
You're still missing something.
tomx2x said:
@psxda97
Maybe that's my problem. I do not have supersu on my phone application. (see my attached).
Here' what I do.
1. Download supersu zip file from website to my PC.
2. Connect PC to phone.
3. I do not extract the supersu.zip on my PC, I just manually copy the supersu.zip (as is) to Download folder (A0001) of my Phone.
4. Logoff off phone.
5. Get into TWRP. Click Install. Click supersu zip.
6. Reboot, when finish, run Titanium Backup on phone to check for root.
Should supersu app be on my phone after installation/rebooting?
Somehow it's not doing the root, even though it completes successfully in TWRP. Strange.
Tom.
Click to expand...
Click to collapse
Go to system settings>developer options>root access and set it to "apps and adb"
If you flash the SuperSU.zip in TWRP on your device then you should have root.
I think you misunderstood from the beginning, did you download the SuperSU.zip and then extract it on PC and then try to install it? If so, that was completely the wrong thing to do. You might have to remove what you've done so far and then try again from a clean start, you might gave to flash your stock firmware to get a clean start.
Have you looked into whether you need normal SuperSU or whether you need systemless SuperSU?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Additional info provided - Anyone with advice.
@psxda97 - No problem about your availability time will put my post in advance reply for others to share their advice. I'm currently in Thailand for awhile, so your PM time is my AM.
@Droidriven.
No I never did an extract of the Supersu zip file. I just raised that as a "Should I".
I have attached screenshots of my About Phone & Developer Options for review.
I found only 1 Recovery log file at the Root. This has been attached.
Normal Supersu or Seamless. Not an expert on this, but the article (see below), implies if you flash supersu it will decide what method to use. I'd prefer seamless if this help. "https://www.howtogeek.com/249162/what-is-systemless-root-on-android-and-why-is-it-better/"
Just curious. What if I ran in this order Supersu, ROM, GAAP.
Would that make any difference?
Tom.
tomx2x said:
@psxda97 - No problem about your availability time will put my post in advance reply for others to share their advice. I'm currently in Thailand for awhile, so your PM time is my AM.
@Droidriven.
No I never did an extract of the Supersu zip file. I just raised that as a "Should I".
I have attached screenshots of my About Phone & Developer Options for review.
I found only 1 Recovery log file at the Root. This has been attached.
Normal Supersu or Seamless. Not an expert on this, but the article (see below), implies if you flash supersu it will decide what method to use. I'd prefer seamless if this help. "https://www.howtogeek.com/249162/what-is-systemless-root-on-android-and-why-is-it-better/"
Just curious. What if I ran in this order Supersu, ROM, GAAP.
Would that make any difference?
Tom.
Click to expand...
Click to collapse
The problem might be in the LineageOS ROM that you're using, I've seen others have this issue on other devices using LineageOS.
I don't recall what some of the solutions were.
@Sam Nakamura is pretty knowledgeable about the OnePlus devices, maybe he has some useful input.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
tomx2x said:
@psxda97 - No problem about your availability time will put my post in advance reply for others to share their advice. I'm currently in Thailand for awhile, so your PM time is my AM.
@Droidriven.
No I never did an extract of the Supersu zip file. I just raised that as a "Should I".
I have attached screenshots of my About Phone & Developer Options for review.
I found only 1 Recovery log file at the Root. This has been attached.
Normal Supersu or Seamless. Not an expert on this, but the article (see below), implies if you flash supersu it will decide what method to use. I'd prefer seamless if this help. "https://www.howtogeek.com/249162/what-is-systemless-root-on-android-and-why-is-it-better/"
Just curious. What if I ran in this order Supersu, ROM, GAAP.
Would that make any difference?
Tom.
Click to expand...
Click to collapse
Sorry, it's early in the morning here and I think I haven't been able to get the question yet...
First of all, lineageOS provides a own method of root, found here:
https://download.lineageos.org/extras
If you instead choose to use supersu the order must be -> rom, (custom kernel), supersu, (or rom, custom kernel, gapps, supersu but for gapps it doesn't matter when to flash them as long as it is in the same session and after the rom, supersu intendes to either patch the kernel (hence systemless) or to write in system (partition of the rom), that's why rom and custom kernel (if you choose to use a custom kernel) needs to be flashed before supersu...
The supersu systemless / system detection does not always work properly, in that case you can force supersu systemlessly by going to the terminal option in twrp before flashing supersu and type this:
"echo SYSTEMLESS=true>>/data/.supersu" no quotes, type "false" instead of "true" in this line to force system mode...
If that doesn't solve your problems please elaborate on this again..
Sent from my OnePlus 2 using XDA Labs
Sam Nakamura said:
Sorry, it's early in the morning here and I think I haven't been able to get the question yet...
First of all, lineageOS provides a own method of root, found here:
https://download.lineageos.org/extras
If you instead choose to use supersu the order must be -> rom, (custom kernel), supersu, (or rom, custom kernel, gapps, supersu but for gapps it doesn't matter when to flash them as long as it is in the same session and after the rom, supersu intendes to either patch the kernel (hence systemless) or to write in system (partition of the rom), that's why rom and custom kernel (if you choose to use a custom kernel) needs to be flashed before supersu...
The supersu systemless / system detection does not always work properly, in that case you can force supersu systemlessly by going to the terminal option in twrp before flashing supersu and type this:
"echo SYSTEMLESS=true>>/data/.supersu" no quotes, type "false" instead of "true" in this line to force system mode...
If that doesn't solve your problems please elaborate on this again..
Sent from my OnePlus 2 using XDA Labs
Click to expand...
Click to collapse
I haven't used LineageOS yet so I'm not familiar with its details, I was pretty sure you'd know though. [emoji106]
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
@Sam Nakamura.
Thanks for the info.
I have previously executed the steps in the order you posted. I was just asking if other sequences to flash these apps were plausible.
With the help of member psxda97, he documented similar steps 1-7 for me. (Please read Post #4 on this thread and my results in Post #7). It's basically a snapshot of what you posted regarding the order seq.
Unfortunately, my phone still did not root after applying the ROM, GAAP & Supersu in this order. I'm not sure why the root is declared successful in TWRP, and the phone remain un-rooted.
Do you suggest I rerun steps1-7 from Post#4 and include your echo statement before installing supersu?
The LineageOS extras, (you mentioned) has a built-in root.
I now have LineagOS from Sultanxda's installed on my phone. It is highly recommended by XDA members over the official LOS, for it's smoothness and camera enhancements. Sultanxda' release is 06/25/2017.
LOS extras has a release date of 06/21/2017. My only issues, whether to choose LOS extras. I will subsequently get the next “Official” LOS release for 6/25 and loose LOS Sultanxda installation.
Tom.
Tried Installing LOS extras 14.1
@Sam Nakamura
I downloaded LOS extras from the link you provided.
Went into TWRP
Did the Install
Then rebooted.
Went back to phone\Developers Option
Root Access is still grayed out.
See screenshot attached.
Any suggestions?
Should I just do a TWRP factory reset and start over?
Tom.
tomx2x said:
@Sam Nakamura
I downloaded LOS extras from the link you provided.
Went into TWRP
Did the Install
Then rebooted.
Went back to phone\Developers Option
Root Access is still grayed out.
See screenshot attached.
Any suggestions?
Should I just do a TWRP factory reset and start over?
Tom.
Click to expand...
Click to collapse
Did you choose the correct arm(32) version of lineageOS su? I'd try the following:
Backup all partitions with twrp so you can return to your set-up later on..
Wipe everything except internal storage
Flash rom, (custom kernel), gapps and su
Boot up and check if it's working now
If not restore your backup and check next point
Alternatively:
Have you tried superSU with forced systemless via twrp terminal (by the way, if done correctly there shouldn't fallow a output with this command line..)
Flash supersu from here:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
I never had issues with the beta but you can also use the stable version, downloads on post 1
Using Magisk as root and root management tool
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Flashable zip via twrp, if successful go to magisk settings, and check superuser and read the rest of Magisk's potential on the linked thread, my preferred method as it allows you to hide root from certain apps which deny service to rooted devices..
Important, it's not a good idea to flash lineageOS su, then supersu, then magisk after each fails, at least restore your clean boot partition from twrp or flash the boot.img from within your rom zip... Best would be clean of course - but as you have a backup of your previous system you can play around and make errors...
Sent from my OnePlus 2 using XDA Labs
Hello all, long time member but never really had a reason to post.
I just received my oneplus6, I wanted IOS style emojis (ridiculous I know... lol) So I unlocked bootloader, flashed the temporary TWRP release and flashed MAGISK.
When I booted my phone the error "There's an internal problem with your device contact your device manufacturer" comes up. Unfortunately I took my nandroid backup AFTER installing MAGISK.
I have no wifi at all, I can't use wifi hotspot either, but cellular works. I wanted to flash back to stock recovery but it seems oneplus hasn't released it. I have tried removing magisk and rebooting (via the magisk app) but then the device wont boot.
I canno't flash a stock copy of OxygenOS as it seems it can only be flashed with stock oxygen oneplus6 recovery (which I cannot get access to.) TWRP simply fails to flash it.
Recently in an attempt to solve my issue I formatted the memory, magisk has gone from my app drawer, but the effects it had are still there (I still have IOS emojis) Now apps wont login (snapchat for example says there is a temporary error) Facebook managed to login after a few reboots, I cannot stream video at all. And as I have formatted memory the original nandroid backup (after magisk flash where apps would login but still gives the internal error message and no wifi) is gone.
I really just want to get the device back to a stable operation, if anyone knows what I should do next or somehow has access to stock oneplus6 recovery, please let me know! Thankyou in advance for all help.
Find post with stock fastboot ROMs, download it and extract, then run flash-all.bat while phone is in fastboot
But data will be gone
DalekExt said:
Find post with stock fastboot ROMs, download it and extract, then run flash-all.bat while phone is in fastboot
But data will be gone
Click to expand...
Click to collapse
you mean this?: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
I just did this and it has bricked the phone lol, it fails when I try to complete it
Bricked
19kylegreer96 said:
you mean this?: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
I just did this and it has bricked the phone lol, it fails when I try to complete it
Click to expand...
Click to collapse
Hi,there is un-brick tool available
I would just like to guide anyone who might be having the same issue as me, to this post:
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
And take note of what I said here about Large address aware ( to make this fix work on 64bit PC):
https://forum.xda-developers.com/showpost.php?p=76658555&postcount=34
Using the BAT file in that post that I have linked and the large address aware fix, my problem is fixed and I have now booted the phone and have working wifi!
If you run into that issue next time, just remember to install the provided boot image within TWRP, along with the other zip files to get TWRP to not lag. I had the exact same issues as you and I realized I missed the step of flashing the boot.img within TWRP.
Once I did that, I had working TWRP and WiFi!
I received the same message after rooting. However, everything is working well (wifi, 4G/LTE/camera, etc) except this message [There's an internal problem with your device. Please contact your adminstrator] during start-up.
Whenever I have seen this I just flash the same version of the original rom over my install and it fixes it.
I also notice that for me, Magisk 6.6 causes this, whereas 6.4 does not.
Was an issue if you use Magisk and stock kernel. Use any other kernel around: They fixed it. @Sultanxda pointed the issue at his GitHub site and kernel devs have included it. Thanks @Sultanxda for this .
MickyFoley said:
Was an issue if you use Magisk and stock kernel. Use any other kernel around: They fixed it. @Sultanxda pointed the issue at his GitHub site and kernel devs have included it. Thanks @Sultanxda for this .
Click to expand...
Click to collapse
Going from memory so I might not have it straight but I want to say this was from installing either twrp on just 1 partition or Magisk on the inactive partition. Making 16.4 and 16.6 works perfectly with stock kernel since already 5.1.6 for me as I've had this phone since launch.
It was all working without a problem - just the message popped up. Altering something in the kernel triggered this to happen. @eng.stk got this issue explained by another user, pointing to the Git from sultanxda. Since then, it was solved. Dunno. Had this in the very beginnings and since then never again. Well... Yeah
Thanks
MickyFoley said:
Was an issue if you use Magisk and stock kernel. Use any other kernel around: They fixed it. @Sultanxda pointed the issue at his GitHub site and kernel devs have included it. Thanks @Sultanxda for this .
Click to expand...
Click to collapse
Thank you. That worked fine. I flashed [KERNEL] [blu_spark r31 OP6] [OOS 5.1.*] and the Error-Message is gone.
Installing a custom kernel fixed the issue for me as well.
Magisk fully working now as well as safetynet.
Might want to to edit the title to *fixed* so people know you resolves your issue.
Q: After flashing Magisk, my device will show a scary popup saying "There's an internal problem with your device. Contact your manufacturer for details"
A: This is caused by dtbo image patched to remove AVB 2.0 of the vendor partition. This is required for allowing you to mount vendor to rw and make modifications
If you never plan to modify the vendor partition, in Magisk Manager, "Uninstall > Restore Images" to restore the images, check "Preserve AVB 2.0/dm-verity" box in Advanced Settings, then reinstall Magisk via the app.
JerryGoyal said:
Q: After flashing Magisk, my device will show a scary popup saying "There's an internal problem with your device. Contact your manufacturer for details"
A: This is caused by dtbo image patched to remove AVB 2.0 of the vendor partition. This is required for allowing you to mount vendor to rw and make modifications
If you never plan to modify the vendor partition, in Magisk Manager, "Uninstall > Restore Images" to restore the images, check "Preserve AVB 2.0/dm-verity" box in Advanced Settings, then reinstall Magisk via the app.
Click to expand...
Click to collapse
Great, it worked!!!! It solved the scary message pop-up and kept the root. Thanks!!!
I installed the latest magisk apk and already flashed the zip file .
My phone is rooted properly but there is some error in safetynet checking it shows that: THE RESPONSE IS INVALID
The reason according to me is the empty payload
I have tried the beta version as well but still the error remains same
I want to play fortnite and use some banking apps but it doesn't allow me
I am using OnePlus 6
Any kind of help will be appreciated
Thanks!
Can someone help me out?
Please!!!
From what I read from the dev himself, Google Apps using the old API won't work so safetynet won't work with those apps anymore. Magisk is one of them. You'll have to wait for the devs to release a new version.
https://twitter.com/topjohnwu/status/1029239685338419200
Try this
I don't get that error message. I am running the stable version(v16.0) of Magisk on my OnePlus 6. I followed this guide to root my phone https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-unlock-bootloader-flash-twrp-t3792643
You should follow this guide from the start.
Or maybe try this module on Magisk first: MagiskHide Props Config
Please use the search function because this was already posted..... i know its hard to use the search but it keeps the forums nice and clean and people hate double posts
I have a Motorola G 4 Plus, rooted SU 2.82, latest TWRP, Havoc 2.9, Android 9 Pie. Arm v7I.
Upon trying to install Youtube Vanced through the Vanced Manager, the app crashes and the install fails with the message "failed for unknown reason blah blah blah please go to the Telegraph Discord group" I can post a log file if needed.
After that ordeal, the Youtube app appears in my app drawer, when I try to open it it says "you don't have Google Play Services" and closes.
I tried this with micro-g installed, I disabled apk signature verification with Lucky Patcher, doesn't make a difference.
I even made sure to allow unknown sources and checked the permissions. No go.
I also tried the apks installer through the SIS installer or whatever its called, SAS, SAI or whatever, no luck.
Feels like my phone can go as far as to root and custom recovery and custom rom and busybox and such but continue to find myself in these annoying situations with no resolution. Other people seem to be able to get it to work though. Perhaps its the phone?
Any help is appreciated, thanks!
Do you have magisk installed or are you using another solution for root? I saw your post about brave not working , may I suggest a rom reinstall? Try it with the microg gapps package.
Edit: grammar.
ThatLatinGuy said:
Do you have magisk installed or are you using another solution for root? I saw your post abou brave not working , may I suggest a rom reinstall? Try it with the microg gapps package
Click to expand...
Click to collapse
Rooted with SU 2.82 flashed via TWRP and use SU app. Not magisk. Perhaps I'll try another ROM. Too bad Havoc seems really good customizable.
I originally forgot to wipe cache and dalvik/art cache after flashing the Havoc ROM so maybe that screwed things up, I'll try re-flashing.
I'd remove SU and use magisk 21.4 (not higher, and never update it ever).
when was 2.82 released ? it must be a long time ago now and I don't think it's recommended for anything anymore.
even without any root Vanced manager would install your microg and vanced just fine.
3mel said:
I'd remove SU and use magisk 21.4 (not higher, and never update it ever).
when was 2.82 released ? it must be a long time ago now and I don't think it's recommended for anything anymore.
even without any root Vanced manager would install your microg and vanced just fine.
Click to expand...
Click to collapse
Super SU was last updated 2020 from my understanding.
big bad brad 31 said:
Super SU was last updated 2020 from my understanding.
Click to expand...
Click to collapse
the last post in chainfire's superSU thread here is from 2018, it says just use magisk
big bad brad 31 said:
Super SU was last updated 2020 from my understanding.
Click to expand...
Click to collapse
this is the last and latest version of SuperSU
SuperSU Download
it was released back in 2017 all other website that has SuperSU for downloads except that site are Unofficial Released
big bad brad 31 said:
I have a Motorola G 4 Plus, rooted SU 2.82, latest TWRP, Havoc 2.9, Android 9 Pie. Arm v7I.
Upon trying to install Youtube Vanced through the Vanced Manager, the app crashes and the install fails with the message "failed for unknown reason blah blah blah please go to the Telegraph Discord group" I can post a log file if needed.
After that ordeal, the Youtube app appears in my app drawer, when I try to open it it says "you don't have Google Play Services" and closes.
I tried this with micro-g installed, I disabled apk signature verification with Lucky Patcher, doesn't make a difference.
I even made sure to allow unknown sources and checked the permissions. No go.
I also tried the apks installer through the SIS installer or whatever its called, SAS, SAI or whatever, no luck.
Feels like my phone can go as far as to root and custom recovery and custom rom and busybox and such but continue to find myself in these annoying situations with no resolution. Other people seem to be able to get it to work though. Perhaps its the phone?
Any help is appreciated, thanks!
Click to expand...
Click to collapse
Try installing a custom rom based on A10 n see if this works out for u, it works perfectly on my g4+ on A10 ...