[SOLVED] I just flashed the latest version of SuperSU and everything went back to normal. Both the sim cards were detected.
I currently have Resurrection Remix-N-5.8.5 on my device.
I was not able to get root access in apps so I flashed SR1-Super-SU-v2.78 using TWPR.
The flash was successful but after my device booted up, both the sim card were not detected.
SuperSU was installed and is working fine. My WIFI is also working fine, it just that sim cards are not detected.
My phone is displaying Baseband version.
SIM 1 status : SIM not inserted
SIM 2 status : SIM not inserted
In IMEI information, it is showing IMEI (Slot 1) and IMEI SV (Slot 1) but IMEI and IMEI SV for (Slot 2) are Unknown.
I have a nandroid backup of the stage before I updated my ROM. Will restore using nandroid fix this issue?
How can I fix this? Please help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
nitanshu.vzard said:
I currently have Resurrection Remix-N-5.8.5 on my device.
I was not able to get root access in apps so I flashed SR1-Super-SU-v2.78 using TWPR.
The flash was successful but after my device booted up, both the sim card were not detected.
SuperSU was installed and is working fine. My WIFI is also working fine, it just that sim cards are not detected.
My phone is displaying Baseband version.
SIM 1 status : SIM not inserted
SIM 2 status : SIM not inserted
In IMEI information, it is showing IMEI (Slot 1) and IMEI SV (Slot 1) but IMEI and IMEI SV for (Slot 2) are Unknown.
I have a nandroid backup of the stage before I updated my ROM. Will restore using nandroid fix this issue?
How can I fix this? Please help.
https://prnt.sc/guxx80[IMG][/QUOTE]
How exactly did you install ressurection remix and which version? Did you tried flashing it clean again? How did you uninstall magisk before installing supersu? For sure it's not a rom problem.
Click to expand...
Click to collapse
I updated my RR a week ago. I dirty flashed it. No I did not tried to flashing it clean again. Yes I know it is not a ROM problem, everything was working fine before I flashed the SuperSU-v2.78 zip file. No I did not unistalled magisk before installing SuperSU.
nitanshu.vzard said:
I updated my RR a week ago. I dirty flashed it. No I did not tried to flashing it clean again. Yes I know it is not a ROM problem, everything was working fine before I flashed the SuperSU-v2.78 zip file. No I did not unistalled magisk before installing SuperSU.
Click to expand...
Click to collapse
AFAIK SuperSU had problems of modem after November security update, and it was 2.78 version of SuperSU.
Install latest SuperSU, but before remove older and also uninstall magisk (get uninstaller zip from its forum) and see if you get your IMEI back. Otherwise restore older backups or clean flash. Then go for latest zip.
strongst said:
How exactly did you install ressurection remix and which version? Did you tried flashing it clean again? How did you uninstall magisk before installing supersu? For sure it's not a rom problem.
Click to expand...
Click to collapse
____Mdd said:
AFAIK SuperSU had problems of modem after November security update, and it was 2.78 version of SuperSU.
Install latest SuperSU, but before remove older and also uninstall magisk (get uninstaller zip from its forum) and see if you get your IMEI back. Otherwise restore older backups or clean flash. Then go for latest zip.
Click to expand...
Click to collapse
I flashed the latest version of SuperSU without removing the older version and everything is working just fine now. I got my IMEI back but I did not uninstalled magisk yet.
nitanshu.vzard said:
I flashed the latest version of SuperSU without removing the older version and everything is working just fine now. I got my IMEI back but I did not uninstalled magisk yet.
Click to expand...
Click to collapse
You need to uninstall magisk over the manager app before installing supersu.
I am doing a clean flash now.
I'll fully wipe my phone. Flash Resurrection Remix. Then Flash GApps. Then Wipe Cache/Dalvik.
Now do I need to install magisk or remove magisk ? or install SuperSU.
Sorry I am confused.
nitanshu.vzard said:
I am doing a clean flash now.
I'll fully wipe my phone. Flash Resurrection Remix. Then Flash GApps. Then Wipe Cache/Dalvik.
Now do I need to install magisk or remove magisk ? or install SuperSU.
Sorry I am confused.
Click to expand...
Click to collapse
ROM comes with pre rooted mode (magisk modules).So u dont have to install it separately. If you want to try supersu instead of magisk.
Go to magisk manager tap on uninstall and confirm.Device will reboot.
Then go to twrp and install supersu.
NOTE : Uninstalling magisk if using supersu is mandatory (if you want your phone working properly)
Related
I just unlocked my bootloader on my new Axon 7 and wanted to go Systemless in regards to root, etc.
I've installed Magisk, Magisk's Xposed, and tried to install the Magisk provided PHH Superuser. Everything seemed to flash correctly and rebooting my phone and installing the companion apps shows that Magisk is working, and so is Xposed. But there's no sign of Root working except for the Magisk Manager saying Root is mounted. None of the options in Magisk Manager work either, I presume because the app doesn't have its needed root access.
Any ideas?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my ZTE A2017U using Tapatalk
interessting, seems you are further than i am (2017G B03), which firmware version are you using? Want to try to use that boot.img
when i tried magisk it didn't mount root, nor where the toggles activated
Starvirus said:
interessting, seems you are further than i am (2017G B03), which firmware version are you using? Want to try to use that boot.img
when i tried magisk it didn't mount root, nor where the toggles activated
Click to expand...
Click to collapse
I'm on 2017U B27. Bootloader unlocked.
Sent from my ZTE A2017U using Tapatalk
So yeah, I've given up on Magisk for now. Tried to install SuperSU instead of PHH, and TWRP would crash when trying to flash it.
I tried installing SuperSU outside of Magisk, ie: normal method, and it kind of worked, but for some reason Magisk Xposed would cause the SuperSU app to freeze whenever the framework was enabled.
So without being able to get them to work together I've just given up on Magisk for now. I uninstalled Magisk Xposed, and then Uninstalled Magisk itself. Finally I restored my bootloader backup so I could start off fresh, and then installed SuperSU and Xposed normally.
I'll just have to give up on Android Pay again. Seriously wish someone would just come up with an Xposed module to bypass that stupid Safetynet api already.
Sent from my ZTE A2017U using Tapatalk
Delete...
@Oogar you deleted your post does it mean it didn't work for you? i couldn't get it to work only got as far as the OP (with a modified hybrid boot.img from EU b03 and US b27 rom) on my A2017G
Starvirus said:
@Oogar you deleted your post does it mean it didn't work for you? i couldn't get it to work only got as far as the OP (with a modified hybrid boot.img from EU b03 and US b27 rom) on my A2017G
Click to expand...
Click to collapse
Yeah I thought it was all good, but in reality things were not working. Pokémon GO is the app I was using to test. I am able to toggle root but it doesn't seem to actually do anything.
Tried going to Suhide route with SuperSU 2.65 in systemless mode, then upgrade to 2.78(SR1) but still no luck that way either. A little bit lost at this point.
Reverted back to SuperSU + Regular xposed for the time being.
@Oogar can you check if you have a magisk.log or magisk_last.log in /cache/ if so could you upload it?
Starvirus said:
@Oogar can you check if you have a magisk.log or magisk_last.log in /cache/ if so could you upload it?
Click to expand...
Click to collapse
No log at this point...restored a TWRP backup which was captured right after B27 upgrade
I am encountering the same issue and there is no magisk.log or magisk_last.log created in /cache/
Hi,
i have a 910f (german, snapdragon) with latest stock MM Android 6.0 update from 02/2017.
Now i want to root. I found some tutorials with su and cf-root but i wonder, whats the difference between this methods? Are there any benefits if i choose one or another? Can i install xposed with both of them?
I want to flash latest twrp 3.0.2.0 with odin and afterwards flash the root with twrp.
Can i use titanium backup, when i flash root this way?
Yes.
1st, install TWRP with Odin.
Next, install supersu from twrp.
Next, the sky is the limit
Sent from this galaxy
And titanium backup is working with twrp recovery?
In another thread there was written, titanium backup only works with stock recovery?
Ok, i can answer my question for myself:
I installed TWRP 3.0.2.0 with Odin 3.11.1. Afterwards i installed latest SUperSU v2.79-SR3 with TWRP.
Titanium Backup does work, i can freeze or uninstall all the bloatware.
Can someone help me with Xposed? There should be a problem with samsung smartphones with the regular version? Which xposed version does work with latest MM 6.0.1 Update of Note4?
I think, xposed only works when flashed with twrp? Simple apk-install isn´t possible?
Bib_x said:
Ok, i can answer my question for myself:
I installed TWRP 3.0.2.0 with Odin 3.11.1. Afterwards i installed latest SUperSU v2.79-SR3 with TWRP.
Titanium Backup does work, i can freeze or uninstall all the bloatware.
Can someone help me with Xposed? There should be a problem with samsung smartphones with the regular version? Which xposed version does work with latest MM 6.0.1 Update of Note4?
I think, xposed only works when flashed with twrp? Simple apk-install isn´t possible?
Click to expand...
Click to collapse
Hi Bib.
I'm not really sure which version works with your model but i guess all snapdragon variants can flash this one. Not going to lie didn't not try it yet..
But i can explain to you how it can be safe flashed through twrp.
1st flash alt-sdk23 arm via twrp
2nd reboot your system and install the xposed apk normally.
3rd in xposed thread you will find xposed unistaller simply if anything goes wrong you can just flash the unistaller through twrp.
*Please do your backup before flashing xposed.
* also make sure you're rooted..
Cheers
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can confirm that special xposed from wanam is working with my latest Stock MM Rom 02/2017 (rooted).
v85.1-alt-sdk23-arm
I did reboot after each step. No problem at all. Flashed with twrp 3.0.2.0.
Will xposed work with CF auto root or this will cause any problem?
Final Edit: I reverted back to supersu. Magisk still had issues with remembering which apps already had requested root after each reboot. After so many attempts to get everything working i got tired and rolled back to using supersu.
Edit:My mistake. It turns out my data partition was f2fs instead of ext4 the whole time (checked with the app diskinfo). Now my problem is fixed. I flashed the f2fs loopback bug workaround module through twrp and now magisk works as it should. I'm sorry for the inconvenience
OK. so i keep getting into more and more issues with magisk. so i decided to overhaul this thread completely (no replies so far except my own so i think its unnecessary to open up a new one)
just switched to latest stock rom through clean flash (1.2.0 B10) and installed magisk (16.4). it works and safetynet passes. the problem i got now is that the greenify module (or any other one) fails to install in magisk (see screenshot)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After googling about the issue i saw that many ppl say it has to do with f2fs loopback which doesnt really help since my phone is using ext4
I also tried flashing the module in twrp. it flashed successfully but doesnt show up in magisk
And for some reason magisk doesn't remember which apps have requested root after a reboot. everytime i reboot i get a prompt to allow root access to all my root apps (like greenify). idk why this is happening. i mean, root itself is working as it should. i already uninstalled bloatware and disabled/freezed things like the powermanagement (and yes i checked. those apps are really uninstalled and frozen)
Edit: just tried to install busybox module through magisk. it flashed successfully but after reboot its gone
Edited op. Forgot to mention that the bootloader is unlocked and i have twrp (duh xD)
Sent from my ZTE A2017G running V1.2.0B08 using XDA Labs
Edit: completely changed topic and thread to the current issue. since i was the only one so far to reply i thought opening a new thread again was unnecessary as i just opened this thread yesterday
Issues seem similar to what someone else has/had in another unrelated thread (Moto with permissions problem). Was also going to mention that it was probably f2fs related until you mentioned you're using ext4. Hmm.
Could you try the busybox zip instead via recovery. Both the module and zip are from the same dev. The zip will detect Magisk and install as a module. If/when it fails you can save a recovery log that might have more details on what happens.
See this conversation starting with I think the following post. Maybe it gives some ideas.
http://forum.xda-developers.com/showthread.php?p=76451850
Also, the busybox zip is in the OP of that thread.
ZTE Axon 7 A2017U, AospExtended v5.4 ROM, HELLSGATE Kernel, Multiboot, Tapatalk 4.9.3
GodOfPsychos said:
EDIT:My mistake. It turns out my data partition was f2fs instead of ext4 the whole time (checked with the app diskinfo). Now my problem is fixed. I flashed the f2fs loopback bug workaround module through twrp and now magisk works as it should. I'm sorry for the inconvenience
OK. so i keep getting into more and more issues with magisk. so i decided to overhaul this thread completely (no replies so far except my own so i think its unnecessary to open up a new one)
just switched to latest stock rom through clean flash (1.2.0 B10) and installed magisk (16.4). it works and safetynet passes. the problem i got now is that the greenify module (or any other one) fails to install in magisk (see screenshot)
View attachment 4496088
After googling about the issue i saw that many ppl say it has to do with f2fs loopback which doesnt really help since my phone is using ext4
I also tried flashing the module in twrp. it flashed successfully but doesnt show up in magisk
And for some reason magisk doesn't remember which apps have requested root after a reboot. everytime i reboot i get a prompt to allow root access to all my root apps (like greenify). idk why this is happening. i mean, root itself is working as it should. i already uninstalled bloatware and disabled/freezed things like the powermanagement (and yes i checked. those apps are really uninstalled and frozen)
Edit: just tried to install busybox module through magisk. it flashed successfully but after reboot its gone
Click to expand...
Click to collapse
edit: problem solved by flashing latest f2fs loopback module
Final Edit: i reverted back to using supersu because of too many issues with magisk
What was the other issue?
bluenote73 said:
What was the other issue?
Click to expand...
Click to collapse
It's in the top of OP.
Remember that this all was happening to me on stock 1.2.0 B10.
It might work much better in custom roms as Resurrection remix or AOSP extended etc
Magisk works fine for me. 16.4
Pinch me, I may be dreaming, but I think the final 9.0.0 build has been released! Correct me if this is some kind of beta/DP.
From https://developers.google.com/android/images:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yes
Magisk 16.7 & TWRP 3.2.2-0 working fine. Unable to decrypt data in TWRP though. Any suggestions?
https://arstechnica.com/gadgets/2018/08/google-finalizes-android-p-as-android-9-pie-launching-today/
m0h1t said:
Magisk 16.7 & TWRP 3.2.2-0 working fine. Unable to decrypt data in TWRP though. Any suggestions?
Click to expand...
Click to collapse
Remove your PIN/Passcode password in Android, reboot in TWRP and do what you have to do.
Re-configure the PIN/Passcode in Android.
With PP5 running as DD did a edit of -W for PPR1 and survived the update from PP5 to PPR1 with my data intact. Great!!
Was running PP5 with twrp 3.2.1-2 and Magisk 16.4 when updated. No security or PIN. Found Magisk 16.4 on reinstall from overwrite not
working didn't get past first G screen. Rewrote over with -W still and found Magisk 16.7 worked fine... FOR NOW....ymmv
kkjb said:
With PP5 running as DD did a edit of -W for PPR1 and survived the update from PP5 to PPR1 with my data intact. Great!!
Was running PP5 with twrp 3.2.1-2 and Magisk 16.4 when updated. No security or PIN. Found Magisk 16.4 on reinstall from overwrite not
working didn't get past first G screen. Rewrote over with -W still and found Magisk 16.7 worked fine... FOR NOW....ymmv
Click to expand...
Click to collapse
How do you do -w? Does this mean I can install Android p over most recent development preview and keep root and TWRP?
Xdevillived666 said:
How do you do -w? Does this mean I can install Android p over most recent development preview and keep root and TWRP?
Click to expand...
Click to collapse
Yes, you can install stable over beta, following this guide I made, which looks like still working.
Just pick latest zips such as magisk and twrp and you're good.
I also recommend disable magisk modules before the flash, so you won't face any possible issue, just as a precaution.
I just installed Lineage OS 15.1 and got that all working... now this drops. I think I'll wait a while before I go to this.
I had no issues installing the 9.0 factory image over the 8.1 July update without the data wipe option. I reinstalled TWRP 3.2.2.0 using its install procedure. I needed to upgrade Magisk 16 to the beta version 16.7 in order to get the SafetyNet check to work properly.
So far no issues to report although Pie is not as zippy as it was running on Oreo.
Sent from my SHT-AL09 using Tapatalk
Currently running Stock Oreo with TWRP and Magisk root, AM i good to accept the auto update?
dantexaiver said:
Currently running Stock Oreo with TWRP and Magisk root, AM i good to accept the auto update?
Click to expand...
Click to collapse
I was also surprise to see that the OTA is available, even if I'm also rooted with Magisk, have unlocked bootloader and TWRP installed. So same question here, is it safe to let the auto-install do the job? Or do we need to download the OTA and install it from a computer using fastboot / adb sideload ? I'm new with this device and I read lots of story of people hardbricking there phone! I don't wan't to mess with it.
Milous98 said:
I was also surprise to see that the OTA is available, even if I'm also rooted with Magisk, have unlocked bootloader and TWRP installed. So same question here, is it safe to let the auto-install do the job? Or do we need to download the OTA and install it from a computer using fastboot / adb sideload ? I'm new with this device and I read lots of story of people hardbricking there phone! I don't wan't to mess with it.
Click to expand...
Click to collapse
I bit the bullet and did the ota update , root was broken so had to boot back into TWRP and flash Magisk but other than that things went smooth
dantexaiver said:
I bit the bullet and did the ota update , root was broken so had to boot back into TWRP and flash Magisk but other than that things went smooth
Click to expand...
Click to collapse
Ok so no problem with the modified boot.img from Magisk ? I'll wait for the latest stable for Magisk and I'll do the update via OTA if everything is fine!
Milous98 said:
Ok so no problem with the modified boot.img from Magisk ? I'll wait for the latest stable for Magisk and I'll do the update via OTA if everything is fine!
Click to expand...
Click to collapse
I ran Magisk 16.7 beta and EX kernel with no issues
dantexaiver said:
I ran Magisk 16.7 beta and EX kernel with no issues
Click to expand...
Click to collapse
Did Magisk pass safetynet with 16.7 beta?
queerquirks said:
Did Magisk pass safetynet with 16.7 beta?
Click to expand...
Click to collapse
For me it did not.
Alaadragonfire said:
For me it did not.
Click to expand...
Click to collapse
There's a 1674 version available but for pixel 2 xl. You could test that version?
queerquirks said:
Did Magisk pass safetynet with 16.7 beta?
Click to expand...
Click to collapse
With Flying Colors
I used magisk 1671, no issues, safetynet passes.
I asked in their forums, 1674 is only for pixel 2/xl
Is There any Other Way To Update Magisk?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
prawinraj8045 said:
Is There any Other Way To Update Magisk?
Click to expand...
Click to collapse
i am also faced same problem while updating to magisk 17
I haven't updated magisk but what method did you use to update? Via recovery or by patching the boot image?
patching the boot image failed, then tried to update via recovery, then became boot loop. can't even flash magisk v16 after this procedure in twrp. my device became rootless. i need to do full wipe and start from beginning again
Before flashing magisk 17 , I'll suggest removing 16 by flashing magisk uninstaller from twrp, after this , flash magisk 17.
Lucky me
Not happened to me, just flash via twrp and wipe devlik cache
Reboot and pray
100% working solution to upgrade Magisk to 17.00 without BootLoop
Please follow the below Steps to update Magisk without getting into a bootloop.
1. Uninstall the Magisk by using the uninstall .zip
2. Now flash the ver 17.00 and it will work just fine.
This will work 100%
I faced same issue.
Just uninstall with uninstaller and re install it will fix issues
I had just updated by patching the boot image then flashing through fastboot. It worked with no bootloops for me.
Update to v17.1
vitcp said:
patching the boot image failed, then tried to update via recovery, then became boot loop. can't even flash magisk v16 after this procedure in twrp. my device became rootless. i need to do full wipe and start from beginning again
Click to expand...
Click to collapse
You just need to use Magisk Uninstaller in TWRP before updating! Nd then install Magisk 17.1 which is latest as of today
rocky29b4u said:
Please follow the below Steps to update Magisk without getting into a bootloop.
1. Uninstall the Magisk by using the uninstall .zip
2. Now flash the ver 17.00 and it will work just fine.
This will work 100%
Click to expand...
Click to collapse
I have downloaded the uninstaller and tried running it but failed. Error 1. Says something about unable to mount partition. I even run the decrypt first but it still fail. Should I run the uninstalled from within Magisk? Appreciate any advice.
abubin said:
I have downloaded the uninstaller and tried running it but failed. Error 1. Says something about unable to mount partition. I even run the decrypt first but it still fail. Should I run the uninstalled from within Magisk? Appreciate any advice.
Click to expand...
Click to collapse
Your system partition cannot be mounted due to encryption. If possible, try uninstalling from Magisk itself
abubin said:
I have downloaded the uninstaller and tried running it but failed. Error 1. Says something about unable to mount partition. I even run the decrypt first but it still fail. Should I run the uninstalled from within Magisk? Appreciate any advice.
Click to expand...
Click to collapse
Which partition does it say about not being able to mount ?
rocky29b4u said:
Which partition does it say about not being able to mount ?
Click to expand...
Click to collapse
The uninstaller.zip that is not working with Error 1 and unable to remove magisk.
I already tried running decrypt first then run the uninstaller but still doesn't work.
Edit: Nevermind, I flashed with latest firmware, decypt, magisk 17.1, camera2api and all working fine. Rebooted to firmware 326 now with magisk 17.1. All seems to be working fine and fingerprint is faster! Will see how it goes because the fingerprint scanner usually goes back to being sloppy after a week of update.