Related
I bought a new KF and it has 6.3 on it. I would like to root via BuritooRoot3 but I need 6.2 to run his app. Is there any way to take a stock 6.3 KF and get it back to a stock 6.2 ???
Thanks !
Thibor69 said:
I bought a new KF and it has 6.3 on it. I would like to root via BuritooRoot3 but I need 6.2 to run his app. Is there any way to take a stock 6.3 KF and get it back to a stock 6.2 ???
Thanks !
Click to expand...
Click to collapse
Flash MoDaCo rom. It's a pre rooted stock with gapps and GFS included.
soupmagnet said:
Flash MoDaCo rom. It's a pre rooted stock with gapps and GFS included.
Click to expand...
Click to collapse
DO you think this is the best way to go ?........ or should I go ahead with the only 6.3 root guide I have seen here on this site. (pooky900 guide or something sorry forgot his name) Or do you think it best to wait for a easier newer 6.3 rooter to show up ?? Just your thoughts .... I am not holding you to anything here :O)
Thanks
Thibor69 said:
DO you think this is the best way to go ?........ or should I go ahead with the only 6.3 root guide I have seen here on this site. (pooky900 guide or something sorry forgot his name) Or do you think it best to wait for a easier newer 6.3 rooter to show up ?? Just your thoughts .... I am not holding you to anything here :O)
Thanks
Click to expand...
Click to collapse
I've tried to explain much of this a couple of times now, so here's my final attempt...
The generally accepted procedure for rooting or installing a ROM:
1) Get to fastboot mode by utilizing either...
a) a factory cable
b) fbmode
2) Install recovery and custom bootloader
3) Either root by installing su and Superuser.apk or flash a custom ROM
To get back to 6.2, you will still have to do #1 & #2 and flash the 6.2 zip package like you would any other ROM. Amazon's software will not allow you to downgrade the software through stock so you can use the BurritoRoot exploit.
It's not likely for someone to come up with a newer/easier method for rooting 6.3 because...
a) It's pretty straightforward as it is
b) No one spends the time to do it when the old way works perfectly well
I've laid out the procedure in excruciating detail here...
http://forum.xda-developers.com/showthread.php?t=1638452
I invite you to keep exploring easier ways to do this, so I can make the how-to above simpler and shorter, but I doubt you will find one. Good luck.
MoDaCo comes with 6.3 pre rooted along with gapps and Google Framework Services preinstalled. It is by far the easiest route to get a rooted stock because the work has already been done for you. All you have to do is flash it in recovery. (Assuming you have recovery installed of course)
Last time I heard, you still have to rename otacerts.zip to prevent any OTA updates screwing up everything but I'm not 100% on that. You should definitely look into it, though. People here are pretty good at staying on top of the latest updates and making flashable versions that won't undo everything you have so far (i.e. break root, uninstall recovery, etc.)
Pokey9000's rooting method is very effective and good if you want to learn but unnecessary IMO if you just want a rooted stock that works well. But I think you should definitely have fbmode on your device if you are using Windows. It could come in very handy when your drivers are being stupid.
It should be noted that I don't use stock and never have so I couldn't tell you much about the differences between MoDaCo and straight rooted, as in whether or not you can watch Prime Video with it, but there are plenty of stock users here that can help you sort it out.
Thibor69 said:
I bought a new KF and it has 6.3 on it. I would like to root via BuritooRoot3 but I need 6.2 to run his app. Is there any way to take a stock 6.3 KF and get it back to a stock 6.2 ???
Thanks !
Click to expand...
Click to collapse
Kindle Fire Utility .95 works easily on 6.3 and while it's not BurritoRoot it is still a simple one click root utility with a lot of features to make the rooting process easy. Any particular reason you want Burrito?
soupmagnet said:
MoDaCo comes with 6.3 pre rooted along with gapps and Google Framework Services preinstalled. It is by far the easiest route to get a rooted stock because the work has already been done for you. All you have to do is flash it in recovery. (Assuming you have recovery installed of course)
Last time I heard, you still have to rename otacerts.zip to prevent any OTA updates screwing up everything but I'm not 100% on that. You should definitely look into it, though. People here are pretty good at staying on top of the latest updates and making flashable versions that won't undo everything you have so far (i.e. break root, uninstall recovery, etc.)
Pokey9000's rooting method is very effective and good if you want to learn but unnecessary IMO if you just want a rooted stock that works well. But I think you should definitely have fbmode on your device if you are using Windows. It could come in very handy when your drivers are being stupid.
It should be noted that I don't use stock and never have so I couldn't tell you much about the differences between MoDaCo and straight rooted, as in whether or not you can watch Prime Video with it, but there are plenty of stock users here that can help you sort it out.
Click to expand...
Click to collapse
Just so everybody is on the same page and because I've done more rooting experiments the last few days than I care to admit.
Thibor69 said in another one of his threads that he wants to go to the Hellfire ROM. He's not interested in rooted stock, as far as I can tell. I agree though... I don't know why someone would take the time to root when MoDaCo seems to have done all the heavy lifting already. MoDaCo users also say that they can use some app (the name escapes me at the moment) that switches root on and off so they can watch videos.
pokey9000 doesn't have a rooting method. He has a fastboot exploit that is being used to root 6.3.x in a guide originally written by jcase. For 6.2.x, the rooting method was to use the BurritoRoot exploit to gain root and then get to fastboot mode by using idme. Amazon closed that hole so BurritoRoot can no longer be used for 6.3.x. Because jcase wasn't interested in building another root exploit, he published that guide as an alternative. The rooting method for 6.3.x is to use pokey9000's fbmode to get to fastboot and then install su privileges through TWRP... so, the process has been reversed... su -> fastboot for 6.2.x and now fastboot -> su for 6.3.x. So, you still have to use pokey9000's fbmode to get to fastboot and install a recovery (and bootloader) if you want to install any ROM.
Laquox said:
Kindle Fire Utility .95 works easily on 6.3 and while it's not BurritoRoot it is still a simple one click root utility with a lot of features to make the rooting process easy. Any particular reason you want Burrito?
Click to expand...
Click to collapse
KFU is broken for whatever reason. It does get you su, but doesn't install the Superuser.apk... I don't know why and I'm not interested in debugging it. I'm not sure if sideloading Superuser.apk is the only thing that needs to be done after its "rooting" process, but it also installs the old versions of FFF and TWRP. That causes headaches all around for people that don't know their way around the bootloader and recovery. Otherwise, it's great!
KFU uses the same fbmode exploit that I've outlined in my guide, so the process is essentially identical. If you follow along with what I have there, you'll get all the current software and a working Superuser. If you use KFU, you can go back and reinstall all the stuff I mentioned above.
kinfauns said:
...
Click to expand...
Click to collapse
Yeah, sorry about that. I was replying to his post and you beat me to the punch.
So, yeah...what kinfauns said
Thibor69 said:
I bought a new KF and it has 6.3 on it. I would like to root via BuritooRoot3 but I need 6.2 to run his app. Is there any way to take a stock 6.3 KF and get it back to a stock 6.2 ???
Thanks !
Click to expand...
Click to collapse
You can use the Kindle Fire Utility 0.9.5
That's what I used to root my Kindle on 6.3
You just have to sideload the superuser.apk file though
kinfauns said:
Thibor69 said in another one of his threads that he wants to go to the Hellfire ROM. He's not interested in rooted stock, as far as I can tell.
Click to expand...
Click to collapse
.....Yes that is what I want to do. I don't care about stock at all.
kinfauns said:
I agree though... I don't know why someone would take the time to root when MoDaCo seems to have done all the heavy lifting already. MoDaCo users also say that they can use some app (the name escapes me at the moment) that switches root on and off so they can watch videos.
Click to expand...
Click to collapse
.....I hear what you are saying. Since I don't care about amazon video's, I see no reason to keep any aspects of stock at all .... so I guess I should skip MoDaCo's method also ... right ?
kinfauns said:
pokey9000 doesn't have a rooting method. He has a fastboot exploit that is being used to root 6.3.x in a guide originally written by jcase. Because jcase wasn't interested in building another root exploit, he published that guide as an alternative. The rooting method for 6.3.x is to use pokey9000's fbmode to get to fastboot and then install su privileges through TWRP... So, you still have to use pokey9000's fbmode to get to fastboot and install a recovery (and bootloader) if you want to install any ROM.
Click to expand...
Click to collapse
.....Ok I understand. My question tho would be after I get to fastboot, you said to install a recovery and bootloader. Isn't TWRP the recovery method ? and which bootloader do I install ? And I do this all from within fastboot ? Also, what about FFF ? were does that come into play.
kinfauns said:
KFU uses the same fbmode exploit that I've outlined in my guide, so the process is essentially identical. If you follow along with what I have there, you'll get all the current software and a working Superuser. If you use KFU, you can go back and reinstall all the stuff I mentioned above.
Click to expand...
Click to collapse
But you mentioned that KFU is broken ... so I guess I should just follow your method.
ONE LAST NOTE: Were are the drivers for Kindle Fire. I plug into PC (win7) and it doesn't find driver for kindle, but I still have access to the internal somehow ..
I am ready to start this process now .... but I want to be 100% sure I have a recovery image in case I soft-brick somehow.
You guys are great ... and thank you for helping me !!!
Cheers
Thibor69 said:
I hear what you are saying. Since I don't care about amazon video's, I see no reason to keep any aspects of stock at all .... so I guess I should skip MoDaCo's method also ... right ?
Click to expand...
Click to collapse
Right, sort of. Any custom rom you flash will be rooted, but you need recovery to flash it.
.....Ok I understand. My question tho would be after I get to fastboot, you said to install a recovery and bootloader. Isn't TWRP the recovery method ? and which bootloader do I install ? And I do this all from within fastboot ? Also, what about FFF ? were does that come into play.
Click to expand...
Click to collapse
TWRP is the preferred recovery. You can install the latest bootloader from within recovery... http://forum.xda-developers.com/showthread.php?p=25598837 ...and use fastboot to change to recovery bootmode
But you mentioned that KFU is broken ... so I guess I should just follow your method.
ONE LAST NOTE: Were are the drivers for Kindle Fire. I plug into PC (win7) and it doesn't find driver for kindle, but I still have access to the internal somehow ..
Click to expand...
Click to collapse
The drivers for the KF can be found in the KFU folder along with an installation batch file.
Ok so to sum it up:
1) install kindle drivers, be sure PC see's Kindle and be sure adb is working
2) install TWRP
3) install latest bootloader (via link below)
4) then flash ROM ?
Cheers
soupmagnet said:
Right, sort of. Any custom rom you flash will be rooted, but you need recovery to flash it.
TWRP is the preferred recovery. You can install the latest bootloader from within recovery... http://forum.xda-developers.com/showthread.php?p=25598837 ...and use fastboot to change to recovery bootmode
The drivers for the KF can be found in the KFU folder along with an installation batch file.
Click to expand...
Click to collapse
Sounds about right. There's a possibility you may need to fix your drivers again at some point in the process. If for some reason you can't get fastboot to connect:
http://forum.xda-developers.com/showthread.php?t=1625356
&
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
soupmagnet said:
Sounds about right. There's a possibility you may need to fix your drivers again at some point in the process. If for some reason you can't get fastboot to connect:
http://forum.xda-developers.com/showthread.php?t=1625356
&
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
Click to expand...
Click to collapse
Many thanks !
I tweeted this a couple week ago before the N1 was publicly out but here you go, nothing fancy, no real ui or output.
Thanks to Saurik and Giantpune for contributing (ie its based on their research)
Install apk, run apk wait 1 minute, install supersu app from market then uninstall with this command
adb uninstall com.qualcomm.privinit
Do you have a link to their research or are their findings private?
Regards,
Mr_Bartek said:
Do you have a link to their research or are their findings private?
Regards,
Click to expand...
Click to collapse
saurik - his analysis of the "second master key vuln"
giantpune for his symlnink attack vuln in property space:
Code:
/system/bin/mv /data/property /data/backupprop
/system/bin/mkdir /data/property
/system/bin/ln -s /sys/kernel/uevent_helper /data/property/.temp
/system/bin/setprop persist.sys.fail /data/pwn.sh
jcase said:
I tweeted this a couple week ago before the N1 was publicly out but here you go, nothing fancy, no real ui or output.
Thanks to Saurik and Giantpune for contributing (ie its based on their research)
Install apk, run apk wait 1 minute, install supersu app from market then uninstall with this command
adb uninstall com.qualcomm.privinit
Click to expand...
Click to collapse
Will this exploit work in any other device. when i try to install the play store warns about the vulnerability. Will this vulnerability be gone after uninstalling oppoown.
coolrevi said:
Will this exploit work in any other device. when i try to install the play store warns about the vulnerability. Will this vulnerability be gone after uninstalling oppoown.
Click to expand...
Click to collapse
Possibly other oppo devices
No it doesnt fix the vuln, just becareful where you install apps from
jcase said:
Possibly other oppo devices
No it doesnt fix the vuln, just becareful where you install apps from
Click to expand...
Click to collapse
a second mater key vulnurability? hmm, so this could might not be patched in 4.4?
great job by the way, i dont have the device but this is interesting!
ricky310711 said:
a second mater key vulnurability? hmm, so this could might not be patched in 4.4?
great job by the way, i dont have the device but this is interesting!
Click to expand...
Click to collapse
It should be patched in 4.4.
But some (read most) OEMs still can't manage to patch their devices up to the latest security updates on release.
Anyway, I tested this root method a week or so ago and it works nicely
pulser_g2 said:
It should be patched in 4.4.
But some (read most) OEMs still can't manage to patch their devices up to the latest security updates on release.
Anyway, I tested this root method a week or so ago and it works nicely
Click to expand...
Click to collapse
so your saying in most devices the master key patch could be a possible vulnurabillity still in 4.3?
interesting...
ricky310711 said:
so your saying in most devices the master key patch could be a possible vulnurabillity still in 4.3?
interesting...
Click to expand...
Click to collapse
It depends on if OEMs backported it, depends on which build OEMs used and depends on the bug. Four or five different zip parser bugs with similar results. This one I used was patched in 4.3, but other exist.
Im trying to figure out why oppown apk will not install in my n1. everytime i try it just. Says app not installed. But on the install screen it says something about being an update to an already installed program. Any clues as to what the issue is? all ive done is update to the latest ota software and im currently located in indonesia if that makes a difference.
trickraca said:
Im trying to figure out why oppown apk will not install in my n1. everytime i try it just. Says app not installed. But on the install screen it says something about being an update to an already installed program. Any clues as to what the issue is? all ive done is update to the latest ota software and im currently located in indonesia if that makes a difference.
Click to expand...
Click to collapse
Possible they patched it by now, if you are on cyanogenmod you are certainly patched
Sent from my HTC Two
jcase said:
Possible they patched it by now, if you are on cyanogenmod you are certainly patched
Sent from my HTC Two
Click to expand...
Click to collapse
So show do you root the cyanogenmod edition n1.. Can you help please.. Does it come rooted or what..
giuliano rigon said:
So show do you root the cyanogenmod edition n1.. Can you help please.. Does it come rooted or what..
Click to expand...
Click to collapse
It should not come rooted, if it comes rooted then no way did it pass CTS. I'm guessing unlocking the bootloader and flashing a recovery? I don't know, I dont have one
giuliano rigon said:
So show do you root the cyanogenmod edition n1.. Can you help please.. Does it come rooted or what..
Click to expand...
Click to collapse
You don't need to root if you aren't staying on stock. There's no lock anywhere on the bootloader or anything.
Simply flash TWRP in fastboot, then flash Omni (or whatever else) through TWRP.
You should be able to just flash a SuperSU zip in TWRP as well if you want to root the stock ColorOS.
Sent from my N1 using Tapatalk
noobish doubts..
Harfainx said:
You don't need to root if you aren't staying on stock. There's no lock anywhere on the bootloader or anything.
Simply flash TWRP in fastboot, then flash Omni (or whatever else) through TWRP.
You should be able to just flash a SuperSU zip in TWRP as well if you want to root the stock ColorOS.
Sent from my N1 using Tapatalk
Click to expand...
Click to collapse
Please i ne ed a walthrough..
1) download twrp
2) put it in root of the telephone robot
3) flash it in recovery?
4) reboot recovery wipe cache and dalvik flash omnirom..
Please correct me..
Thank you
giuliano rigon said:
1) download twrp Yes
2) put it in root of the telephone Yes
Make sure to copy Omnirom to your phone at some point
3) flash it in recovery? No - Flash TWRP in Fastboot if you haven't flashed the recovery already. Use the official Teamwin site for guidance
4) reboot recovery wipe cache and dalvik flash omnirom.. Wipe Cache, Dalvik, System, and Data
Click to expand...
Click to collapse
Updates in Red
This is off-topic for this thread though. Questions/Info for flashing Omnirom should be addressed in the Omnirom thread.
Harfainx said:
You don't need to root if you aren't staying on stock. There's no lock anywhere on the bootloader or anything.
Simply flash TWRP in fastboot, then flash Omni (or whatever else) through TWRP.
You should be able to just flash a SuperSU zip in TWRP as well if you want to root the stock ColorOS.
Sent from my N1 using Tapatalk
Click to expand...
Click to collapse
may you provide to right superSU.zip files
I v got superSU from this link and it doesnt work on first and second CM version
I am not rooted yet ...
thnaks
nowy57 said:
may you provide to right superSU.zip files
I v got superSU from this link and it doesnt work on first and second CM version
I am not rooted yet ...
thnaks
Click to expand...
Click to collapse
That does work. You're likely not removing root, but rather just uninstalling SuperSU.
I answered you in your Q&A thread on root.
not rooted.. confirm i can flash
nowy57 said:
may you provide to right superSU.zip files
I v got superSU from this link and it doesnt work on first and second CM version
I am not rooted yet ...
thnaks
Click to expand...
Click to collapse
I nave tried my damnedest to root .. Fastboot flashing supersu flashing from recovery Direct install from google play complete unroots and reflash letting recovery do it .. No way..
So now i need a last confirmation.. Can i flash omnirom after wipes even if i am unrooted.. And has anyone rooted omnirom or does it come unrooted.. Thanks for the info .. Another idea.. Flashing color OS footing and then flashing omni.. Or is this a late night bad Dream..
---------- Post added at 01:17 AM ---------- Previous post was at 01:05 AM ----------
Harfainx said:
That does work. You're likely not removing root, but rather just uninstalling SuperSU.
I answered you in your Q&A thread on root.
Click to expand...
Click to collapse
Sorry now i got it.. It was in the forums.. Just unchecking the respect cyanogen settings in the super su menu got me roooted and happy.. Sorry for your time.. I flashed super su zip from recovery rebooted and unchecked .. Now i am set..
I were rooted myN1 in yesterday, its really good . thankss
Sent from my N1 using XDA Premium 4 mobile app
when I click on supersu. I get there is no su binary installed and supersu cannot install it. this is a problem. I did all steps just fine until I click on supersu. =(. help
netsfan549 said:
when I click on supersu. I get there is no su binary installed and supersu cannot install it. this is a problem. I did all steps just fine until I click on supersu. =(. help
Click to expand...
Click to collapse
Totally wrong section, you should search and read before doing anything to your phone. Anyways, download chainfire's latest supersu from the internet, flash it in recovery, and you'll have root.
Kratos90 said:
Totally wrong section, you should search and read before doing anything to your phone. Anyways, download chainfire's latest supersu from the internet, flash it in recovery, and you'll have root.
Click to expand...
Click to collapse
I did that and still get the same thing
Did that and still didn't work. Is it because I'm running 5.0?
netsfan549 said:
Did that and still didn't work. Is it because I'm running 5.0?
Click to expand...
Click to collapse
That isn't the reason. Chainfire's SuperSU has supported Lollipop for some time now. What version did you try?
redpoint73 said:
That isn't the reason. Chainfire's SuperSU has supported Lollipop for some time now. What version did you try?
Click to expand...
Click to collapse
V.2.02.
I go to recovery. I hit install that version..says installed and I restart my phone. It Still doesn't work. Could it be because I didn't delete other zip file from my phone?
netsfan549 said:
V.2.02.
Click to expand...
Click to collapse
Dude, there is your problem right there!
The advice was to flash the latest SuperSU. That would be 2.46 (or even the couple versions before that also work with LP). You are 44 versions behind!
http://forum.xda-developers.com/showthread.php?t=1538053
redpoint73 said:
Dude, there is your problem right there!
The advice was to flash the latest SuperSU. That would be 2.46 (or even the couple versions before that also work with LP). You are 44 versions behind!
http://forum.xda-developers.com/showthread.php?t=1538053
Click to expand...
Click to collapse
Thank you, I was following a link that I found on Google. Lol. I would post link here but don't have enough post. I really appreciate it.
I'm trying to root my ZE551ML (WW-2.20.40.198) and install Xposed, but I can't get any of the scripts I've found here to work. I've installed ADB & Fastboot and this driver. MTP works and adb works when I'm in recovery mode, so I'm not sure why the scripts can't contact the device. None of the scripts recognize the device. Also, "adb devices" shows that no device is found.
It seems that all these scripts are using some variation of CWM to do it anyway. So if I could just install CWM in some other way, I guess I could just get root and xposed through CWM. I have used this official ASUS app to unlock the bootloader. So, I wonder if I could just flash a recovery.img of CWM using the command "fastboot flash recovery recovery.img"? Is that all it would take to get CWM installed? And then I could use CWM to get root, etc?
If yes, which recovery.img file should I use and where can I get it?
I think I can get fastboot to work when the device is in the bootloader, so that's what I'm thinking. Also, I can use OS X or Ubuntu then, so I don't have to worry about the Windows scripts.
Fiksdal said:
I'm trying to root my ZE551ML (WW-2.20.40.198) and install Xposed, but I can't get any of the scripts I've found here to work. I've installed ADB & Fastboot and this driver. MTP works and adb works when I'm in recovery mode, so I'm not sure why the scripts can't contact the device. None of the scripts recognize the device. Also, "adb devices" shows that no device is found.
It seems that all these scripts are using some variation of CWM to do it anyway. So if I could just install CWM in some other way, I guess I could just get root and xposed through CWM. I have used this official ASUS app to unlock the bootloader. So, I wonder if I could just flash a recovery.img of CWM using the command "fastboot flash recovery recovery.img"? Is that all it would take to get CWM installed? And then I could use CWM to get root, etc?
If yes, which recovery.img file should I use and where can I get it?
I think I can get fastboot to work when the device is in the bootloader, so that's what I'm thinking. Also, I can use OS X or Ubuntu then, so I don't have to worry about the Windows scripts.
Click to expand...
Click to collapse
Worth checking general section
http://forum.xda-developers.com/zenfone2/general/index-asus-zenfone-2-wip-t3149748
http://forum.xda-developers.com/zenfone2/development/z00az008-zenfone-2-t3265236
Hmmm.. Nevermind, I did it through TWRP. Followed this tutorial. Root works
Fiksdal said:
Hmmm.. Nevermind, I did it through TWRP. Followed this tutorial. Root works
Click to expand...
Click to collapse
Tip
It is always worth googling
and put an XDA on the end
timbernot said:
Tip
It is always worth googling
and put an XDA on the end
Click to expand...
Click to collapse
Haha, you know, I had been struggling with this problem for like 2 days. So many hours on the computer and Google trying to figure it out. I was trying to get the scripts to work, then CWM, then TWRP. I was just really confused and didn't know how to do it since most guides on Google said I had to use the scripts for Windows. Then finally I realized that it was as simple as using fastboot from OS X Anyway, sorry to bother you guys. But Everything is working now, root, Xposed and permanent TWRP. Awesome
Good stuff
There was a script at the beginning in earlier fw versions I think when boot loader was first being hacked.
Remember , if you upgrade to M , unlock boot loader again at .134 with modder tool in general section before updating to .144 and then to .184.
another tip
timbernot said:
Good stuff
There was a script at the beginning in earlier fw versions I think when boot loader was first being hacked.
Remember , if you upgrade to M , unlock boot loader again at .134 with modder tool in general section before updating to .144 and then to .184.
another tip
Click to expand...
Click to collapse
Yeah, I've tried Marshmallow already, but my favorite Xposed modules didn't work, so I've downgraded to Lollipop again
Fiksdal said:
Yeah, I've tried Marshmallow already, but my favorite Xposed modules didn't work, so I've downgraded to Lollipop again
Click to expand...
Click to collapse
You are doing great now :victory:
Hello people!
I have recently bought this phone and I'm now trying to flash TWRP and root it. Sadly (since it's a fairly recent build I guess?) I haven't found any tutorial to do so, and I have only managed to unlock the bootloader by now... Do you guys have any idea?
Thanks in advance!
There's no need for a new guide for Oreo, the procedure is the same for all system versions. You can follow the old guides, just don't use provided links if they're not updated but find new files yourself.
Sent from my OnePlus 3 using Tapatalk
Same here. I managed to unlock bootloader till now but I cannot flash any zip files of supersu
AnonyMouniSs said:
Same here. I managed to unlock bootloader till now but I cannot flash any zip files of supersu
Click to expand...
Click to collapse
Look at any other guide as the previous comment said just use updated files for your device.
The short answer for you is to read up on 'custom recovery'.
Misanful said:
Look at any other guide as the previous comment said just use updated files for your device.
The short answer for you is to read up on 'custom recovery'.
Click to expand...
Click to collapse
I've tried every files of SuperSU. Can you please provide me the link that might get flashed?
Thank you.
AnonyMouniSs said:
I've tried every files of SuperSU. Can you please provide me the link that might get flashed?
Thank you.
Click to expand...
Click to collapse
If you are on Oreo, you have to flash Magisk once you boot into recovery 1st time.
AnonyMouniSs said:
I've tried every files of SuperSU. Can you please provide me the link that might get flashed?
Thank you.
Click to expand...
Click to collapse
SuperSU doesn't seem to be compatible with Oreo. So use Magisk as the previous poster said.
werty733 said:
If you are on Oreo, you have to flash Magisk once you boot into recovery 1st time.
Click to expand...
Click to collapse
I'm on Oreo and I tried flashing Magisk as you said but it too didn't get done. I'm so frustrated with this ****.
AnonyMouniSs said:
I'm on Oreo and I tried flashing Magisk as you said but it too didn't get done. I'm so frustrated with this ****.
Click to expand...
Click to collapse
Which
Firmware you are on now ?
TWRP version ?
Magisk version you have tried to flash?
What procedure you have followed?
werty733 said:
Which
Firmware you are on now ?
TWRP version ?
Magisk version you have tried to flash?
What procedure you have followed?
Click to expand...
Click to collapse
ONEPLUS A3003_16_180517
I'm not sure about the recovery version and it's not even TWRP. I just followed the steps that was given in some website.
Magisk v16
Downloaded magisk. Tried flashing it. Failed.
Maybe I should just try another recovery i.e. TWRP but does recovery of different developer matter?
AnonyMouniSs said:
ONEPLUS A3003_16_180517
I'm not sure about the recovery version and it's not even TWRP. I just followed the steps that was given in some website.
Magisk v16
Downloaded magisk. Tried flashing it. Failed.
Maybe I should just try another recovery i.e. TWRP but does recovery of different developer matter?
Click to expand...
Click to collapse
Recovery does matter. If you are not on TWRP, are you on stock recovery? Then how did you flash Magisk?
Flash eng.stk's TWRP then reboot into TWRP and flash Magisk and then reboot to system.
tnsmani said:
Recovery does matter. If you are not on TWRP, are you on stock recovery? Then how did you flash Magisk?
Flash eng.stk's TWRP then reboot into TWRP and flash Magisk and then reboot to system.
Click to expand...
Click to collapse
Thank you. I found the solution. The TWRP has should be unlocked. I don't know why but TWRP should had been first swiped to use it. And you helped me a lot. Thank you
I found the steps to root my OnePlus 3 on XDA.
I am running on the latest OnePlus Open Beta.
Are the steps any different?
Also, how to root using magisk?
Could you link me to a thread?