SuperSU Binary Update Failed! - Nexus 6 Q&A, Help & Troubleshooting

I have a Nexus 6, Marshmallow (Build MMB29K). I rooted it using the NRT which installed SuperSU version v2.46. Apparently from the NRT dialogs, the last step of rooting is configuring SuperSU properly.
I get a message that I must update to the latest binaries; but every attempt fails.
I am new at this. Can someone please help?

m_albert69 said:
I have a Nexus 6, Marshmallow (Build MMB29K). I rooted it using the NRT which installed SuperSU version v2.46. Apparently from the NRT dialogs, the last step of rooting is configuring SuperSU properly.
I get a message that I must update to the latest binaries; but every attempt fails.
I am new at this. Can someone please help?
Click to expand...
Click to collapse
stop using toolkits, do it the freaking right way. its MUCH easier the right way. use google, search for the latest supersu, download it, flash it in twrp recovery, then reboot. btw, the toolkits version is VERY old. and you trust the toolkit?
---------- Post added at 09:38 PM ---------- Previous post was at 09:04 PM ----------
latest btw http://download.chainfire.eu/752/SuperSU/BETA-SuperSU-v2.65-20151226141550.zip

simms22 said:
stop using toolkits, do it the freaking right way. its MUCH easier the right way. use google, search for the latest supersu, download it, flash it in twrp recovery, then reboot. btw, the toolkits version is VERY old. and you trust the toolkit?
---------- Post added at 09:38 PM ---------- Previous post was at 09:04 PM ----------
latest btw ...
Click to expand...
Click to collapse
Thank you for the info. Your link fixed it. But please, go a bit easier on me. I'm new to all this.

simms22 said:
.....btw, the toolkits version is VERY old. and you trust the toolkit?
Click to expand...
Click to collapse
lies, all lies.
wug just updated it last week to work on froyo
---------- Post added at 09:06 PM ---------- Previous post was at 09:05 PM ----------
yea simms, take it ez on the noobs geez, not everyone knows it all like you

bweN diorD said:
lies, all lies.
wug just updated it last week to work on froyo
Click to expand...
Click to collapse
I THINK the problem was that TWRP asked if I wanted to install ITS version of SuperSU. I wasn't supposed to allow that; but I did.
EDIT: When I'm nervous, I tend not to read everything carefully.

m_albert69 said:
I THINK the problem was that TWRP asked if I wanted to install ITS version of SuperSU. I wasn't supposed to allow that; but I did.
Click to expand...
Click to collapse
yea, you dont want to do that ever.

bweN diorD said:
yea, you dont want to do that ever.
Click to expand...
Click to collapse
I'm sure that's what happened. I thought it was weird that I had to "swipe to install" twice.

m_albert69 said:
I'm sure that's what happened. I thought it was weird that I had to "swipe to install" twice.
Click to expand...
Click to collapse
another thing, im thinking you should have been using su zip 2.52 also, not 2.4whatever. i could be mistaken, but i always use 2.5*.
---------- Post added at 09:17 PM ---------- Previous post was at 09:13 PM ----------
m_albert69 said:
I'm sure that's what happened. I thought it was weird that I had to "swipe to install" twice.
Click to expand...
Click to collapse
i just noticed simms linked you to 2.65, i wouldnt recommend you use that unless you need it, its systemless and still working out the kinks.

Looking back on my NRT logs, it DID install 2.64. But as I said, during the TWRP recovery I nervously allowed it to do everything it asked of me. That included installing its own version of SuperSU, which must have immediately overwritten NRT's version.

m_albert69 said:
Looking back on my NRT logs, it DID install 2.64. But as I said, during the TWRP recovery I nervously allowed it to do everything it asked of me. That included installing its own version of SuperSU, which must have immediately overwritten NRT's version.
Click to expand...
Click to collapse
actually it more likely made some sort of conflict. 2.64 installs in the kernel, twrp put it in the system, but in all the years i have had a smart phone, i have never used twrps root once.

m_albert69 said:
Thank you for the info. Your link fixed it. But please, go a bit easier on me. I'm new to all this.
Click to expand...
Click to collapse
im sorry for sounding/being so rough on you.. really i am. but stuff like flashing supersu is part of the most very basic knowledge needed. and i mean very basic. i was just trying to get that point across. im normally an extremely nice person :angel:
---------- Post added at 11:04 PM ---------- Previous post was at 11:01 PM ----------
bweN diorD said:
actually it more likely made some sort of conflict. 2.64 installs in the kernel, twrp put it in the system, but in all the years i have had a smart phone, i have never used twrps root once.
Click to expand...
Click to collapse
twrps root, never. its always a very old version, so stay away :good:

Hi
i recently had this problem and overcome it by doing the following
open up settings > click on applications > Application Manager > scroll across to all > scroll down to Supersu and click it (should come up with application info) > click remove installed updates
once that is completed i rebooted (may not be need but better to be safe) the opened up supersu again, and installed the binary with the normal procedure and all updated ok
this was done on my Samsung Galaxy S6 Edge running 3.10.61-S6_UniBase_BOG8_v2, Android Version 5.1.1
i hope this helps someone
regards
Dennis

Related

[Q] XT1053 Need help with Root

I have the dev edition of the moto x 2013. I've unlocked the bootloader successfully. I flashed the Recovery img with this command
Code:
mfastboot flash recovery openrecovery-twrp-2.8.3.0-ghost.img
and flashed the SuperSU.zip (UPDATE-SuperSU-v2.40) through the Recovery successfully. But when I checked to see if it was rooted with Root Checker Basic, it said the Device wasn't.
I'm sure that I've done all the steps right in this guide Guide on "Rooting Unlocked Bootloader". Please Help
PS: I'm new to all this rooting and stuff. Sorry if there is a post out there that covers this. I couldn't find any posts that say this guide didn't work.
Did you download SuperSU from the play store? ?
---------- Post added at 12:38 AM ---------- Previous post was at 12:35 AM ----------
Here is a video guide also... To see if you missed anything,
http://forum.xda-developers.com/showthread.php?t=2487635
Thanks for the video guide! I'll check into it later, as it is kind of late here...
No I did not install SuperSU from the play store. I got it from the link the guide provided me. and sorry I can't post a url since i'm new to this forum
You still at need to install SuperSU. You've flashed the binaries in recovery, but need the app if it isn't in your app drawer.
---------- Post added at 12:51 AM ---------- Previous post was at 12:51 AM ----------
If it is in your app drawer already, open it... See what it says.
Okay. I installed it, updated the binaries, and it flashed for me... It works now. I see why the app is needed. Thank you!!!!
Eh, Quick question, does it matter what android version i need to do a nandroid backup and is it easy?
Android version is irrelevant to make a backup. Yes it's easy... Just go to backup in your recovery, click.... Done. ?

Process - Band 12 OTA Update with root?

Surprised that I haven't seen a post on XDA yet showing us peeps that have rooted and removed ads how to apply this new update. I still think it's fictitious! haha
Seriously though, what would be the proper procedure here, revert to 100% stock then take the OTA or does anyone have hiding the .img file to flash via fastboot or whatnot? Are we able to even get root back after the B12 update? If not, I'd rather leave the phone as it is with root. It's been a long time since I've even messed with this phone because of lack of B12. I just impulse bought it because I wanted a decent spare phone.
Thanks!
http://forum.xda-developers.com/r1-hd/development/prime-stock-rom-6-5-flashed-via-twrp-t3455532/
ytsejam1138 said:
http://forum.xda-developers.com/r1-hd/development/prime-stock-rom-6-5-flashed-via-twrp-t3455532/
Click to expand...
Click to collapse
Your answer was extremely vague, but after reading the OP in that post several times, I took the plunge with 7.4.2 and worked perfectly. Thank you!
So for those that were confused like I was, here's the skinny:
Anyone with a R1 HD running build 6.6 or 6.8 can do what I did:
1. download the 7.4.2 shown in the post above to your SD card
2. boot into twrp (I used whatever version I already had - back when it first came out to rid me of ads)
3. full wipe (I tried dirty flashing, and magical unicorns reached out from my screen and slapped me in the face)
4. booted and waited about 5 minutes.
5. LTE Discovery shows the use of Band 12 without modification (I'm in a burb of Dayton, OH which is fringe Band 4 and excellent Band 12 coverage)
6. VoLTE is shown in Settings --> More --> Cellular Networks --> "Enhanced 4G LTE Mode"
Your answer was extremely vague, but after reading the OP in that post several times, I took the plunge with 7.4.2 and worked perfectly. Thank you!
Yes its not very clear
The last time I flashed something from that page it reset everything I did not care I had my apps backup.
So I have to do a full wipe? then restore with android titanium backup
then root once more from twrp?
Im not sure why I would want to flash this this is has updater enabled. I would lost root if they pushed a new update. I could just disable it like before.
its a good hour to do that. I have to back up the current rom. get a good back up with titanium backup, install the room root it set up the account then restore with titanium backup. Im using tmobel is it worh it? Im on wifi most of the time.
Modified_rom_R1HD_7.4.2.zip (Modified_rom is stock 7.4.2 rom minus the preloader_p6601.bin, lk.bin, logo.bin, secro.img, trustzone.bin, uboot.img from 7.4.2, as well as amazon apps, no ads, updater enabled, so this rom is safe to use.)
https://www.androidfilehost.com/?fid=313042859668275704
Modified_rom_R1HD_7.4.2.zip (Modified_rom is stock 7.4.2 rom minus the preloader_p6601.bin, lk.bin, logo.bin, secro.img, trustzone.bin, uboot.img from 7.4.2, as well as amazon apps, no ads, updater enabled, so this rom is safe to use.)
https://www.androidfilehost.com/?fid=313042859668275704
I dirty flashed, no problems. didn't lose any apps. You will lose root but then you just flash supersu and you're rooted again. It's really no problem at all to do.
joesee said:
Your answer was extremely vague, but after reading the OP in that post several times, I took the plunge with 7.4.2 and worked perfectly. Thank you!
So for those that were confused like I was, here's the skinny:
Anyone with a R1 HD running build 6.6 or 6.8 can do what I did:
1. download the 7.4.2 shown in the post above to your SD card
2. boot into twrp (I used whatever version I already had - back when it first came out to rid me of ads)
3. full wipe (I tried dirty flashing, and magical unicorns reached out from my screen and slapped me in the face)
4. booted and waited about 5 minutes.
5. LTE Discovery shows the use of Band 12 without modification (I'm in a burb of Dayton, OH which is fringe Band 4 and excellent Band 12 coverage)
6. VoLTE is shown in Settings --> More --> Cellular Networks --> "Enhanced 4G LTE Mode"
Click to expand...
Click to collapse
I'm still slightly confused. What if we are on the V12 non-Prime (dated 6/27/2016)? Is there an update to the V12?
parkerlreed said:
I'm still slightly confused. What if we are on the V12 non-Prime (dated 6/27/2016)? Is there an update to the V12?
Click to expand...
Click to collapse
The update is Prime only. There are no updates for v12.
cyanix-tech said:
The update is Prime only. There are no updates for v12.
Click to expand...
Click to collapse
So as long as I do a clean flash I can use Modified_rom_R1HD_7.4.2.zip?
parkerlreed said:
So as long as I do a clean flash I can use Modified_rom_R1HD_7.4.2.zip?
Click to expand...
Click to collapse
Yep, dirty works too.
cyanix-tech said:
Yep, dirty works too.
Click to expand...
Click to collapse
Sweet, opted for the clean flash over V12 and it's already booted up and restoring applications. Thanks.
---------- Post added at 10:59 PM ---------- Previous post was at 10:49 PM ----------
raven.warsong said:
Im not sure why I would want to flash this this is has updater enabled. I would lost root if they pushed a new update. I could just disable it like before.
Click to expand...
Click to collapse
This enables Blu's wireless update, not Amazon's. Also the modified stock feels pretty much like the V12 did. No traces of Amazon at all.
parkerlreed said:
Sweet, opted for the clean flash over V12 and it's already booted up and restoring applications. Thanks.
---------- Post added at 10:59 PM ---------- Previous post was at 10:49 PM ----------
This enables Blu's wireless update, not Amazon's. Also the modified stock feels pretty much like the V12 did. No traces of Amazon at all.
Click to expand...
Click to collapse
ya thanks it work great but I dont really want blu wireless update enabled do it? if I update that way I can lose recovery or root right?
raven.warsong said:
ya thanks it work great but I dont really want blu wireless update enabled do it? if I update that way I can lose recovery or root right?
Click to expand...
Click to collapse
I'm not sure.
parkerlreed said:
Sweet, opted for the clean flash over V12 and it's already booted up and restoring applications. Thanks.
---------- Post added at 10:59 PM ---------- Previous post was at 10:49 PM ----------
This enables Blu's wireless update, not Amazon's. Also the modified stock feels pretty much like the V12 did. No traces of Amazon at all.
Click to expand...
Click to collapse
its been my understanding it can so I just have to remember how to turn it off there is a file or a command you have to do. its been a few months. Any one know?
raven.warsong said:
its been my understanding it can so I just have to remember how to turn it off there is a file or a command you have to do. its been a few months. Any one know?
Click to expand...
Click to collapse
Settings > About device > Wireless Update > 3-dot menu > Settings > Check weekly/uncheck auto download
thanks

Has anyone installed Galaxy Note 8 One UI Beta? Link with instructions included.

Has anyone tested the latest beta leaks for the Note 8 One UI N950USQU5DRL5, DRL6, or DRL7. Here is a LINK to Androidsage with instructions. I am tempted to install however I have a Gear S2 watch and Gear VR. If I read correctly DRL6 and 7 work with the gear wearable. Here is another LINK that I found that you should look at before installing the latest beta leaks.
madmangunradio said:
Has anyone tested the latest beta leaks for the Note 8 One UI N950USQU5DRL5, DRL6, or DRL7. Here is a LINK to Androidsage with instructions. I am tempted to install however I have a Gear S2 watch and Gear VR. If I read correctly DRL6 and 7 work with the gear wearable. Here is another LINK that I found that you should look at before installing the latest beta leaks.
Click to expand...
Click to collapse
A little search would have helped you out here.. https://forum.xda-developers.com/verizon-galaxy-note-8/help/update-to-pie-announced-t3881335
I've installed N950USQU5DRL7 and both my Gear S2 watch and my Gear VR are working without any problems. So far so good. I changed my theme back to default theme to set the night mode for dark ui and it's working. I'll update this thread if I find any problems.
Only thing I see missing on drl7 is super slow-mo
---------- Post added at 09:04 AM ---------- Previous post was at 09:03 AM ----------
Will we be able to get ota's if we manually flashed the drl7 update?
gabesir said:
Only thing I see missing on drl7 is super slow-mo
---------- Post added at 09:04 AM ---------- Previous post was at 09:03 AM ----------
Will we be able to get ota's if we manually flashed the drl7 update?
Click to expand...
Click to collapse
No.. Have to flash back to CRK1.
I wanted DRL7 after having done the DRL5 update...........so had to Odin back to CRK1.......................phone was in a bootloop for several hours before I was able to get into Recovery mode................so not looking forward to doing again to get the official Pie update, but will have to at some point.
anyone have a CRK1 spr file to DL please
.........with very detailed instructions would be helpful, don't want to get into a bootloop.
ycats said:
.........with very detailed instructions would be helpful, don't want to get into a bootloop.
Click to expand...
Click to collapse
did you flash CRK1? whats the issue?
ycats said:
I wanted DRL7 after having done the DRL5 update...........so had to Odin back to CRK1.......................phone was in a bootloop for several hours before I was able to get into Recovery mode................so not looking forward to doing again to get the official Pie update, but will have to at some point.
Click to expand...
Click to collapse
You just need to make sure you hold the buttons down securely so they don't come up a little bit and it's a lot harder to keep them held down with a case on the phone.. You need to hold all 3 buttons for up to 2 minutes sometimes and if you don't that's why you get stuck in a boot loop..
gabesir said:
did you flash CRK1? whats the issue?
Click to expand...
Click to collapse
I did the Odin back to CRK1 and after it "passed" and rebooted, got into a continuous bootloop for several hours.
---------- Post added at 02:40 PM ---------- Previous post was at 02:39 PM ----------
MrMike2182 said:
You just need to make sure you hold the buttons down securely so they don't come up a little bit and it's a lot harder to keep them held down with a case on the phone.. You need to hold all 3 buttons for up to 2 minutes sometimes and if you don't that's why you get stuck in a boot loop..
Click to expand...
Click to collapse
I had removed the case and held the three buttons for five minutes.
ycats said:
I did the Odin back to CRK1 and after it "passed" and rebooted, got into a continuous bootloop for several hours.
---------- Post added at 02:40 PM ---------- Previous post was at 02:39 PM ----------
I had removed the case and held the three buttons for five minutes.
Click to expand...
Click to collapse
I read that another user said they had to hold it for over 7 minutes?? That seems excessive but idk I've never had that problem yet.
ycats said:
I did the Odin back to CRK1 and after it "passed" and rebooted, got into a continuous bootloop for several hours.
---------- Post added at 02:40 PM ---------- Previous post was at 02:39 PM ----------
I had removed the case and held the three buttons for five minutes.
Click to expand...
Click to collapse
I just remembered something.. If it ever does that to you again open a command prompt or terminal and send the reboot recovery through ADB. I know you know how to use adb but to those of you who don't know just type "adb shell reboot recovery" without the quotes obviously and wait for the phone to do it.. It may work and it may not..
Well, might have to see if it does................I know CRK1 was the update for December, isn't there a newer one for Oreo for January?
Im aware that the one ui android pie update will be dropping soon but im interested in trying this method for testing it before the official release. My question is are you all using sprint carrier locked devices or unlocked devices?

October 2019 Security update for Mi A2 broke my phone

How can I remove the October update on my phone or fix? I install and the phone does not turn on :crying::crying::crying:
https://c.mi.com/thread-2533551-1-0.html same here, fastboot continue worked for me
and reposted here too: https://c.mi.com/thread-2533525-1-0.html - becasue feedbacks they are responding to faster.
I had the same problem, i fixed it by just connecting the device to my laptop using the usb cable.Just restart it once to twice and it worked.
Now when it boots up it says that the update has failed, but when i again update the phone, it shuts down the phone at next login, but when i restart the device again the device was updated to october verson
laviniu_c said:
https://c.mi.com/thread-2533551-1-0.html same here, fastboot continue worked for me
and reposted here too: https://c.mi.com/thread-2533525-1-0.html - becasue feedbacks they are responding to faster.
Click to expand...
Click to collapse
Thanks for fast reply, you safe my ass :victory: the Mi a2 work
Did you guys have any mod installed? Because my phone is just running fine with October patch, updated right now without problems (full stock and locked device)
Labestiajaker said:
Thanks for fast reply, you safe my ass :victory: the Mi a2 work
Click to expand...
Click to collapse
no problem! glad it worked! did you use wifi to download or mobile data?
---------- Post added at 05:25 PM ---------- Previous post was at 05:24 PM ----------
N1ck474 said:
Did you guys have any mod installed? Because my phone is just running fine with October patch, updated right now without problems (full stock and locked device)
Click to expand...
Click to collapse
nope, no root, no changes, not unlocked BL, and not the first ota i did either.
laviniu_c said:
no problem! glad it worked! did you use wifi to download or mobile data?
---------- Post added at 05:25 PM ---------- Previous post was at 05:24 PM ----------
nope, no root, no changes, not unlocked BL, and not the first ota i did either.
Click to expand...
Click to collapse
Wow, that's weird, but it can't be Xiaomi fault, cause the OTA is ok and working fine
laviniu_c said:
no problem! glad it worked! did you use wifi to download or mobile data?
---------- Post added at 05:25 PM ---------- Previous post was at 05:24 PM ----------
nope, no root, no changes, not unlocked BL, and not the first ota i did either.
Click to expand...
Click to collapse
Wifi
N1ck474 said:
Wow, that's weird, but it can't be Xiaomi fault, cause the OTA is ok and working fine
Click to expand...
Click to collapse
i disagree. they are at fault. no ota should brick stock phones. ever. this has happend before on other phones too (mi 9se being the latest one i've seen). some users would update properly and some would just end up with nice and expensive paperweights. via ota. if i was a betting man, i would assume this is related to the version of the bootloader on the phone. and sometime they miss something on the ota update. causing certain versions of the bootloaders to reject the update. but i dont have any expertise here, im just an average joe with a phone that failed an OTA miserably. perhaps just restarting it a couple of times also is enough, but i resurrected mine with the fastboot continue i had found earlier.
laviniu_c said:
i disagree. they are at fault. no ota should brick phones. ever. this has happend before on other phones too (mi 9se being the latest one i've seen). some users would update properly and some would just end up with nice and expensive paperweights. via ota. if i was a betting man, i would assume this is related to the version of the bootloader on the phone. and sometime they miss something on the ota update. causing certain versions of the bootloaders to reject the update. but i dont have any expertise here, im just an average joe with a phone that failed an OTA miserably. perhaps just restarting it a couple of times also is enough, but i resurrected mine with the fastboot continue i had found earlier.
Click to expand...
Click to collapse
I can understand but, if my untouched phone just got an OTA and successfully installed it, the update should be ok, idk why some phones have this type of problem but it's not normal, maybe an old mod? A restored partition after a ROM install? Idk, but i can say that: the OTA is ok on my stock phone, the problem should be something else...
N1ck474 said:
I can understand but, if my untouched phone just got an OTA and successfully installed it, the update should be ok, idk why some phones have this type of problem but it's not normal, maybe an old mod? A restored partition after a ROM install? Idk, but i can say that: the OTA is ok on my stock phone, the problem should be something else...
Click to expand...
Click to collapse
My phone has never been cleaned and modified, September 2019 and other work, but this update brick my phone.
maybe an old mod? A restored partition after a ROM install? Idk, but i can say that: the OTA is ok on my stock phone, the problem should be something else...
nope... nothing new interesting/installed since the previous sept ota. never unlocked, never restored, never rooted it. it is/was plain stock...
Then retry the update, take a backup First, if the OTA brick the phone again ask for a complete refund
Same here, completely stock. Turned off after the Android One screen, restarted and booted again but with an Update Failed notification. Tried it a second time, same thing. First time I have issues with an OTA so far.
My phone is Global Version, I inform if the brick is in this model
N1ck474 said:
Then retry the update, take a backup First, if the OTA brick the phone again ask for a complete refund
Click to expand...
Click to collapse
it's funny, it just got out of warranty. 1y old this month
---------- Post added at 06:09 PM ---------- Previous post was at 06:09 PM ----------
global too
laviniu_c said:
it's funny, it just got out of warranty. 1y old this month
---------- Post added at 06:09 PM ---------- Previous post was at 06:09 PM ----------
global too
Click to expand...
Click to collapse
It doesn't have 2 years of warranty? Btw mine Is Global too, i think(?), it's from Germany
Those who "soft-bricked with OTA" : Just keep trying to reboot many times with external power on and pauses. Sooner or later phone is to reboot to now (after OTA) inactive slot (read about A/B structure if you do not know what i mean) with the previous bootable version (10.0.14.0 ? or any which was there before OTA), - as such behavior is specified in AndroidOne requirements.
N1ck474 said:
It doesn't have 2 years of warranty? Btw mine Is Global too, i think(?), it's from Germany
Click to expand...
Click to collapse
yep you're right 2 years indeed! gonna have fun with the seller )
yep they're all global, there was never a mi a2 for china ( that one is the mi 6x). there is a version for india but i doubt it was ever sold outside india since it has fewer lte bands.
N1ck474 said:
It doesn't have 2 years of warranty? Btw mine Is Global too, i think(?), it's from Germany
Click to expand...
Click to collapse
Mine is from Spain Amazon

Complete coloros 6 rooting guide (no issues at all, everything works)

Guys , The UPDATE Version RMX1921EX_11_A.16 fixed all issues relating to unlocking and rooting.
Fingerprint works, no lock screen pin error, no magisk installation error (fix for core only mode is below) , safetyNEt bypass also works.
.
Here is the step by step guide.
1- Update to firmware version RMX1921EX_11_A.16. link available in reame website (fingerprint fix is fixed from updates here after)
2- Unlock bootloader
3- Flash twrp by thesprintster, https://forum.xda-developers.com/realme-xt/development/recovery-unofficial-twrp-realme-5-pro-t3985459
4 -flash magisk
5- Flash magisk Core-only fix (this fix is for 5 pro, however i have tried and it works for xt https://drive.google.com/file/d/108eV7pOuX50wQeO84kxmW-wQbZVdx0DZ/view
6-Reboot
Done.
If magisk shows core-only mode, go to settings and untick coreonly mode, enable magisk hide and reboot.
everything should be working now.
when you boot back to recovery the second time, twrp might be lost. flash it again. it will work perfectly from there after. worked for me at least.
This is how i rooted my phone today. I'm not a expert or anything. I took a leap of faith and moved forward.
For those who are going to it, I won't take responsibility if your phone breaks, so try it on your own risk.
Comment your result below, so others can try it out.
Share magisk link
---------- Post added at 07:15 AM ---------- Previous post was at 07:05 AM ----------
Did you install custom rom on top it and verify if fp is working?
akashavel said:
Share magisk link
---------- Post added at 07:15 AM ---------- Previous post was at 07:05 AM ----------
Did you install custom rom on top it and verify if fp is working?
Click to expand...
Click to collapse
download official magisk.
no i haven't tried custom rom. but it works in stock rom after bt unlock
I have checked firmware version on my device. The last update was RMX1921EX_11_A.14 not RMX1921EX_11_A.16
Can i apply this guide on my phone for rooting it, or this will get me in trouble?
---------- Post added at 02:31 PM ---------- Previous post was at 02:14 PM ----------
where i got "Unlock boatloader" option in step 2?
i checked developer option but nothing there
Mustafa_Khattab said:
I have checked firmware version on my device. The last update was RMX1921EX_11_A.14 not RMX1921EX_11_A.16
Can i apply this guide on my phone for rooting it, or this will get me in trouble?
---------- Post added at 02:31 PM ---------- Previous post was at 02:14 PM ----------
where i got "Unlock boatloader" option in step 2?
i checked developer option but nothing there
Click to expand...
Click to collapse
You can choose to download the update from link
https://www.realme.com/in/support/software-update
Once done , Flash custom recovery/magisk and reboot once..and also you may need to update build prop to have Sdk version updated in file or there is forum to flashable zip ..Once done Magisk works like a charm
happy enjoying systemless root method with V4A ,JDSP and lots of modules working withoutr a hiss
Regards,
Diaz Michael
How to update build prop to have updated sdk version?
diazneoones82 said:
You can choose to download the update from link
https://www.realme.com/in/support/software-update
Once done , Flash custom recovery/magisk and reboot once..and also you may need to update build prop to have Sdk version updated in file or there is forum to flashable zip ..Once done Magisk works like a charm
happy enjoying systemless root method with V4A ,JDSP and lots of modules working withoutr a hiss
Regards,
Diaz Michael
Click to expand...
Click to collapse
Thanks, I have downloaded it and had tried to download Fix core-only for Magisk, but gives me message "It's deleted by the owner", Can u help me?
evil_one-droid said:
How to update build prop to have updated sdk version?
Click to expand...
Click to collapse
I need a reply to this too, what's build prop that I have to update?

Categories

Resources