Related
Just tried rooting the phone for the first time. Not too familiar with rooting. Only done a few phones before.
Unlocked boot loader on dev site. Installed TWRP just fine. Installing root package went fine, but I was unable to install busybox. It would either fail to install, or crash the phone and reboot. I found a root + busybox zip, flashed that, and then SuperSU said I wasn't rooted at all! Tried flashing the old SuperSU root package again, but I'm still not rooted anymore. Can someone give me a quick fix for this please?
Thanks.
Is there anyone that can give me some advice? It would be MUCH appreciated!
hi friend ..
i'm also new about rooting hTC (1st time).i'd like to help, but not good enough on explanation ..i root my hTC One on day 2nd bought it.Might some help from youtube and xda topics about unlock bootloader, s-off & rooting.
after u done unlock bootloader, just download twrp zip or cwm zip..extract it copy twrp file (img) on fastboot folder (on pc drive with fastboot files for unlock bootloader process).
right click img file to open as cmd.Then type "fastboot flash recovery recovery.img" then press enter..if u see word just like okay u can go back to bootloader mode, select recovery if u see word on top of screen while htc booting mode that's mean u already done flashing recovery.wait just 2 second, twrp should appear..u should download superSU or super user early put on ur sd then u flash it use twrp..check ur root status use root checker or titanium backup.lastly u tap on superSU or super user icon to update binary (for this method i'm not sure u need to update or not) might somebody got any best answer..
sorry for bad english & too simple methods.
Sent from my HTC One using xda app-developers app
Panduhz said:
Is there anyone that can give me some advice? It would be MUCH appreciated!
Click to expand...
Click to collapse
do you have the superuser app installed?
zaphodbeeb said:
do you have the superuser app installed?
Click to expand...
Click to collapse
I did, but when I opened it, it says I wasn't rooted as if I just installed it from the play store without a root.
Panduhz said:
Just tried rooting the phone for the first time. Not too familiar with rooting. Only done a few phones before.
Unlocked boot loader on dev site. Installed TWRP just fine. Installing root package went fine, but I was unable to install busybox. It would either fail to install, or crash the phone and reboot. I found a root + busybox zip, flashed that, and then SuperSU said I wasn't rooted at all! Tried flashing the old SuperSU root package again, but I'm still not rooted anymore. Can someone give me a quick fix for this please?
Thanks.
Click to expand...
Click to collapse
for complete guide :
http://forum.xda-developers.com/showthread.php?t=2265618
---------- Post added at 07:11 AM ---------- Previous post was at 07:11 AM ----------
Panduhz said:
Just tried rooting the phone for the first time. Not too familiar with rooting. Only done a few phones before.
Unlocked boot loader on dev site. Installed TWRP just fine. Installing root package went fine, but I was unable to install busybox. It would either fail to install, or crash the phone and reboot. I found a root + busybox zip, flashed that, and then SuperSU said I wasn't rooted at all! Tried flashing the old SuperSU root package again, but I'm still not rooted anymore. Can someone give me a quick fix for this please?
Thanks.
Click to expand...
Click to collapse
for complete guide :
http://forum.xda-developers.com/showthread.php?t=2265618
I am looking for an easy way to be able to receive OTA updates after rooting with the 'systemless' root method, the steps I mention below assume that the system partition remains untouched after rooting. I have searched and not found a clear answer on this.
Would I be correct in assuming that this procedure should work to receive an OTA update and keep stock recovery after rooting?
Start with completely stock Android 6.0
fastboot boot twrp-recovery.img (boot TWRP, NOT flash, to maintain stock recovery after rooting)
Flash systemless root with TWRP
OTA arrives (Android 6.0.1 for example)
fastboot flash boot boot.img (with stock 6.0 kernel, root lost)
Accept & install OTA update
Success?
So unless I am missing something, this method would leave the system in a stock, unrooted state after the OTA is installed, and could be repeated for future updates. Anybody have any experience with this yet?
Sounds like it will work, but why mess with the ota? More work and risk honestly.
Since you're already using fastboot just flash the newest boot and system.img. Then flash/boot twrp and flash su like you'd need to do anyway. Done. You don't lose anything flashing system.
yosmokinman said:
Sounds like it will work, but why mess with the ota? More work and risk honestly.
Since you're already using fastboot just flash the newest boot and system.img. Then flash/boot twrp and flash su like you'd need to do anyway. Done. You don't lose anything flashing system.
Click to expand...
Click to collapse
That is true, kind of just wondering/gathering information. It just seemed like with the new root method, OTA would be possible and less risky than before.
Sent from my MotoG3 using Tapatalk
@quakeaz there is one step missing on your guide. After boot.img you also have to flash stock recovery.img. From Lollipop, Google is also checking installed recovery, and for successful OTA, it has to be stock as well.
Otherwise, your guide should work, I've done same thing with my Nexus 5 and 7 for like last 3 months.
Srandista said:
@quakeaz there is one step missing on your guide. After boot.img you also have to flash stock recovery.img. From Lollipop, Google is also checking installed recovery, and for successful OTA, it has to be stock as well.
Otherwise, your guide should work, I've done same thing with my Nexus 5 and 7 for like last 3 months.
Click to expand...
Click to collapse
Thanks for your reply, but I intentionally left that step out, due to step 2 in my list. By only booting TWRP, instead of flashing, I assume stock recovery will remain after rooting.
Sent from my MotoG3 using Tapatalk
quakeaz said:
Thanks for your reply, but I intentionally left that step out, due to step 2 in my list. By only booting TWRP, instead of flashing, I assume stock recovery will remain after rooting.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Ah, sorry, I overlooked that.
Since I have flashed TWRP instead of stock recovery, I'm going by same process as you write, just reflash stock recovery. And can confirm, that the process is indeed working (no need to install system.img, as with previous system-based SuperSU).
Sounds good!
Sent from my MotoG3 using Tapatalk
quakeaz said:
I am looking for an easy way to be able to receive OTA updates after rooting with the 'systemless' root method, the steps I mention below assume that the system partition remains untouched after rooting. I have searched and not found a clear answer on this.
Would I be correct in assuming that this procedure should work to receive an OTA update and keep stock recovery after rooting?
Start with completely stock Android 6.0
fastboot boot twrp-recovery.img (boot TWRP, NOT flash, to maintain stock recovery after rooting)
Flash systemless root with TWRP
OTA arrives (Android 6.0.1 for example)
fastboot flash boot boot.img (with stock 6.0 kernel, root lost)
Accept & install OTA update
Success?
So unless I am missing something, this method would leave the system in a stock, unrooted state after the OTA is installed, and could be repeated for future updates. Anybody have any experience with this yet?
Click to expand...
Click to collapse
Instead of fastboot flashing boot.img, you can use "Settings --> Full Unroot" in SuperSU. During SuperSU systemless flash, your old boot image is backed up. Among other things, the full unroot option will restore the backup, assuming it hasn't been lost due to a factory reset and whatnot.
On many firmwares, this procedure also restores stock recovery. This requires that both the firmware supports recreating the recovery from the boot image plus a patch file (most do), and that TWRP did not remove said patch file (which some versions do).
That being said, if you're using fastboot anyway, flashing boot, recovery, system and vendor manually is always the safest thing before an OTA.
Thanks for the info. So I take it while using systemless root, installing ota without unrooting is a big nono? The January ota just downloaded and is asking me to install, should I do it manually?
Chainfire said:
Instead of fastboot flashing boot.img, you can use "Settings --> Full Unroot" in SuperSU. During SuperSU systemless flash, your old boot image is backed up. Among other things, the full unroot option will restore the backup, assuming it hasn't been lost due to a factory reset and whatnot.
On many firmwares, this procedure also restores stock recovery. This requires that both the firmware supports recreating the recovery from the boot image plus a patch file (most do), and that TWRP did not remove said patch file (which some versions do).
That being said, if you're using fastboot anyway, flashing boot, recovery, system and vendor manually is always the safest thing before an OTA.
Click to expand...
Click to collapse
Thank you for this thread and the procedure. I tried myself to avoid as much as possible to use a computer for super easy OTA update. But there is always one obligatory step: to root the phone.
Phone systemless rooted (2.66) - TWRP installed - OTA arrives.
In SuperSu app : Fully unroot
Install OTA - success
Fastboot boot (or install) TWRP
Flash superSu 2.66.zip
And that's it!
My question is the following: Does it exist a possibility to load on step 3. something that could flash superSu.zip from within the phone, no computer required?
Maybe FlashFire? I guess not, for it needs root and the point is to flash a rooting zip... You see the loop there...
Would it be theoreticaly possible at all?
Judim said:
Maybe FlashFire? I guess not, for it needs root and the point is to flash a rooting zip... You see the loop there...
Would it be theoreticaly possible at all?
Click to expand...
Click to collapse
Yes, this is one of the use-cases of FlashFire. I just haven't finished updating it to 6.0 yet.
Oh nice!
I didn't know it cause I never had the chance to try out FlashFire.
Thanks so much for everything you do for the Android community!
Cheers!
Srandista said:
Ah, sorry, I overlooked that.
Since I have flashed TWRP instead of stock recovery, I'm going by same process as you write, just reflash stock recovery. And can confirm, that the process is indeed working (no need to install system.img, as with previous system-based SuperSU).
Click to expand...
Click to collapse
mine fail here. i previously got systemless root 2.62, blu spark kernel and twrp. fastboot flash stock boot and recovery. reboot to update and it fail. any idea why?
ShanxRoux said:
mine fail here. i previously got systemless root 2.62, blu spark kernel and twrp. fastboot flash stock boot and recovery. reboot to update and it fail. any idea why?
Click to expand...
Click to collapse
Did you modify system?
Try flashing system, boot, and recovery.
Then try again.
Hi, I have a Oneplus One and today has been released an OTA, so I tried the method. I have COS13 JK (latest full rom) firmware, with systemless 2.84beta supersu and twrp.
The only apps that have root access are AdAway and Greenify (without mods to system apps). No Busybox installed.
I reverted via fastboot to original JK boot.img and recovery.img, and restored, via Adaway, the original hosts file, then I applied the OTA via stock Cyano Recovery, but update failed ("system partition has unexpected contents" error).
Why?
Thanks.
you have to unroot first from the app.Revert to original boot. and then flash
Sent from my ASUS_Z00LD using Tapatalk
caldent said:
you have to unroot first from the app.Revert to original boot. and then flash
Sent from my ASUS_Z00LD using Tapatalk
Click to expand...
Click to collapse
I tried: no way to install OTA, I had to wait for the full rom, and dirty flashed it via TWRP without a problem.
Then I rerooted.
Bye!
ok i seem to be getting the run around on where i need to be to ask my question(s)
i am very interested in systemless root....
that being said i am clueless and all info i am findingis just super confusing me.
if someone could humor a noob to systemless rooting that would be greatly appreciated!!
i recently bought 2 new phone for my household, both are the lg tribute hd (also called lg x style)
one click root and pc method of kingoroot etc dont work... i cant locate a twrp or a cwm for this model easily by searching so i am assuming there isnt one (maybe someone could located or help to build one?)- or maybe im not tech smart enough and i can use any?(i dont think so)
model is lg ls675,android 6.0.1, kernel version 3.10.49, build # MXB48T, software is ls676zv3
main reason at the moment for trying to get root is to remove bloatware and to be able to wifi tether without limitations buy the provider, on ther phone that i have obtained root on i used an app called WIFI Tether Router which works beautifully but requires root...
please help as this is how we use our computer with internet and its beneficial all the way around especially to get rid of bloatware and keep device running smoothly...
thanks again for any help. greatly appreciated.
if im not in the right thread please kindly direct me to the correct one. thanks
Hi ppl. I jus rooted my le 2 using root toolkit last week.. Then i received an ota update. So i flashed stock recovery from this link,, http://forum.xda-developers.com/le-2/development/leeco-le-2-x526-stock-recovery-t3449208 . Using the flashify app. Thn i unrooted my phone using full permanent unroot option in supersu app.. Now i cant flash the ota update, its showing installation aborted... Thn even i tried flashing the full stock rom zip (1.7gb), still same error... Someone give solution please...
Scarer Rocker said:
Hi ppl. I jus rooted my le 2 using root toolkit last week.. Then i received an ota update. So i flashed stock recovery from this link,, http://forum.xda-developers.com/le-2/development/leeco-le-2-x526-stock-recovery-t3449208 . Using the flashify app. Thn i unrooted my phone using full permanent unroot option in supersu app.. Now i cant flash the ota update, its showing installation aborted... Thn even i tried flashing the full stock rom zip (1.7gb), still same error... Someone give solution please...
Click to expand...
Click to collapse
Same thing happened to me.
I flashed TWRP and then flashed new EUI ROM.
Alok Bajaj said:
Same thing happened to me.
I flashed TWRP and then flashed new EUI ROM.
Click to expand...
Click to collapse
Now, can you do the ota updates?
Scarer Rocker said:
Now, can you do the ota updates?
Click to expand...
Click to collapse
OTA updates are literally waste of data, no noticeable improvements at all. I'm on EUI 19s BTW
Scarer Rocker said:
Now, can you do the ota updates?
Click to expand...
Click to collapse
I flashed the latest version from TWRP. Haven't tried flashing anything from EUI recovery. I already have the latest EUI.
Scarer Rocker said:
Hi ppl. I jus rooted my le 2 using root toolkit last week.. Then i received an ota update. So i flashed stock recovery from this link,, http://forum.xda-developers.com/le-2/development/leeco-le-2-x526-stock-recovery-t3449208 . Using the flashify app. Thn i unrooted my phone using full permanent unroot option in supersu app.. Now i cant flash the ota update, its showing installation aborted... Thn even i tried flashing the full stock rom zip (1.7gb), still same error... Someone give solution please...
Click to expand...
Click to collapse
According to me you don't have to unroot and install stock recovery just to install ota update there is a way to install update for same kind of rom i.e. stock rom update on stock rom or Custom rom update on custom rom without losing any user data. (Note:- This method is worked for me to apply ota update. You can do it on your own risk but if you had any problem you can ask me anytime.
Following are steps :-
1) Download the latest ota update it should be located here (internal storage/data/com.letv.android.ota/files/otaUpdates) folder.
2) There should be a zip file just cut and paste it in root folder for easy process.
3) Now boot to TWRP recovery and flash zip file which is pasted in root folder.
4) Now format dalvik cache and if you want root, then root again because due to flashingnew rom root access and all other changes you have done in system will lost but all your data will be safe... (This method is usefull for same type of rom i.e. from stock rom to stock rom or custom rom to custom rom).
5) Just for your knowledge 5.8.0.19s update file is full rom file but if you want other versions such as 5.8.0.16s then use offline update packages which are full size i.e. around 1.7 gb.
Also you can flash root since twrp comes with inbuild root tools just locate it in twrp recovery in advanced/tools/root.
Also you can install stock rom just after flashing stock rom in place of any custom rom just wipe data and factory reset and then apply root and reboot normally.
Scarer Rocker said:
Hi ppl. I jus rooted my le 2 using root toolkit last week.. Then i received an ota update. So i flashed stock recovery from this link,, http://forum.xda-developers.com/le-2/development/leeco-le-2-x526-stock-recovery-t3449208 . Using the flashify app. Thn i unrooted my phone using full permanent unroot option in supersu app.. Now i cant flash the ota update, its showing installation aborted... Thn even i tried flashing the full stock rom zip (1.7gb), still same error... Someone give solution please...
Click to expand...
Click to collapse
OTA will not install if you are ROOTED.
only way to unroot is unroot from app and flash stock kernel.
download full rom LEECO website and flash it from twrp
Alok Bajaj said:
Same thing happened to me.
I flashed TWRP and then flashed new EUI ROM.
Click to expand...
Click to collapse
could you please write step by step procedure you have followed to flash 19s from twrp. i have twrp of codeworkx's in my phone and runing lineage 8 Jan build. because as i know twrp will not allow flashing eui.
Use this TWRP
https://drive.google.com/file/d/0B4w7ufa1_mS2RDlwdGhPeTN1Y28/view?usp=drivesdk
Use the CMD to flash it
Use the code
fastboot flash recovery twrp.img
Kr1shna55 said:
Use this TWRP
https://drive.google.com/file/d/0B4w7ufa1_mS2RDlwdGhPeTN1Y28/view?usp=drivesdk
Use the CMD to flash it
Use the code
fastboot flash recovery twrp.img
Click to expand...
Click to collapse
Don't I need to make changes in updater script?
nadeem_naddy said:
Don't I need to make changes in updater script?
Click to expand...
Click to collapse
No
Use the Chinese Developer's TWRP...
It will let you flash official Update also will replace recovery, root, basebend, firmware everything.
So you will have a new, untouched mobile... and can receive and install future updates...
---------- Post added at 06:31 AM ---------- Previous post was at 06:23 AM ----------
You can search on google for that recovery...
Bjoy2012 said:
Use the Chinese Developer's TWRP...
It will let you flash official Update also will replace recovery, root, basebend, firmware everything.
So you will have a new, untouched mobile... and can receive and install future updates...
---------- Post added at 06:31 AM ---------- Previous post was at 06:23 AM ----------
You can search on google for that recovery...
Click to expand...
Click to collapse
Agreed with you bud. I have done the same, i.e. through chinese ydss twrp recovery, and i am now back on stock eui 5.8.019s
Hi,
While trying to restore stock ROM my mobile got hanged. After that only stock recovery menu is showing it's neither loading the stock ROM neither ADB is detecting. I am unable to flash TWRP since ADB shows waiting for device. If by anyway ADB or fastboot will detect my device then I can copy the stock ROM Zip file along with TWRP recovery.
Thanks in Advance
Tapas
i am flashing with qfil in leeco le 2 x526 ,but now it was hangs in logo ....plz help me
Tried to root OP3T with 7.0 . Not sure what happened but the phone is stuck in bootloop.
What do I need to do to get rid of boot loop ? Do I need different version of SU which works with 7.0 ?
What version of SuperSU are you using? Older versions will cause you to get stuck on the boot animation.
Try v2.79. It should reboot once or twice during first boot after flashing.
Alternatively, you can also root by flashing Magisk v11.1.
sguy156 said:
Tried to root OP3T with 7.0 . Not sure what happened but the phone is stuck in bootloop.
What do I need to do to get rid of boot loop ? Do I need different version of SU which works with 7.0 ?
Click to expand...
Click to collapse
First, reflash OS to get a stable starting point. Then use the unofficial beta release of twrp to flash. I have heard of success with a fork ( blu something) but basically he merged the same patches.
Check the dm-verity thread for more details
Sent from my ONEPLUS A3000 using Tapatalk
sguy156 said:
Tried to root OP3T with 7.0 . Not sure what happened but the phone is stuck in bootloop.
What do I need to do to get rid of boot loop ? Do I need different version of SU which works with 7.0 ?
Click to expand...
Click to collapse
Follow this guide:
https://www.youtube.com/watch?v=wwd31NU7VC0&t=4s
I used SU version 2.79 and how do I get rid of this boot screen now. Video is using same version of SU I used which caused bootloop.
Is there another version of SU which doesn't cause bootloop ?
sguy156 said:
I used SU version 2.79 and how do I get rid of this boot screen now. Video is using same version of SU I used which caused bootloop.
Is there another version of SU which doesn't cause bootloop ?
Click to expand...
Click to collapse
U can't get rid of this msg.
Navi44 said:
U can't get rid of this msg.
Click to expand...
Click to collapse
He can, by doing as it says. To keep root, Use a SYSTEM version of SuperSU then relock the bootloader. This wipes data but SuperSU is then part of the OS so will survive the lock. Obviously, all user data gets wiped In the process.
damiensturdy said:
He can, by doing as it says. To keep root, Use a SYSTEM version of SuperSU then relock the bootloader. This wipes data but SuperSU is then part of the OS so will survive the lock. Obviously, all user data gets wiped In the process.
Click to expand...
Click to collapse
Have you tried that personally?
Which version of SU is the system version 2.79 ? First thing is to get the phone to boot first
Navi44 said:
Have you tried that personally?
Click to expand...
Click to collapse
I did this with OxygenOS 3.5.(4?) in order to pass safetynet before the bootloader patched kernels were created.
damiensturdy said:
I did this with OxygenOS 3.5.(4?) in order to pass safetynet before the bootloader patched kernels were created.
Click to expand...
Click to collapse
Thank you for telling this.
This was a normal thing in rn3 thread.
Where even we flashed roms with locked bootloader. And whatever we can do through recovery we did with locked bootloader.
Didn't try it here though.
So after rooting 7.0 I can then lock the phone and rooting will still work. Not sure how will that happen as phone will be wiped
sguy156 said:
So after rooting 7.0 I can then lock the phone and rooting will still work. Not sure how will that happen as phone will be wiped
Click to expand...
Click to collapse
Someone said to use system root.
And then lock the bootloader. Since the su is in system, it won't be wiped.
Haven't tried it but should work THEORETICALLY
What exactly is system root is that a flashable zip or regular SU in rom when rom gets rooted .
sguy156 said:
What exactly is system root is that a flashable zip or regular SU in rom when rom gets rooted .
Click to expand...
Click to collapse
Regular su.
Earlier su used to be system root.
The systemless root started quite recently.
So do I need to use seamless root or SU for 7.0
On using systemless root it will be deleted when you lock bootloader.
You need to use system root for naught
Keep in mind that if you update OOS after locking the bootloader,you'll lose root. Afterwards, you'll have to unlocked the bootloader again - and wiping your device in the process - to reroot.
Wow no need for custom recovery...
http://www.androidpolice.com/2017/0...hout-root-installing-without-custom-recovery/
@ultramag69 Maybe he doesn't follow Magisk closely? I know I don't. Magisk is only on used my stepmom's OP3T H2OS (which I update but don't look at the change log since it's only there in case I need it in the future), the other 2 phones I support don't use Magisk they use LOS su add-on. Not everyone who uses root cares about all the bloated/"nifty" features that come out, some just want plain old root.
I only use for root too but every so often I open magisk manager as it updates both the manager app and magisk itself....
It's done that for ages... The only one I found that didn't was 13.1, that one needed TWRP.
I'm letting people know that with 14 they can keep stock recovery and take OTAs
ultramag69 said:
I only use for root too but every so often I open magisk manager as it updates both the manager app and magisk itself....
It's done that for ages... The only one I found that didn't was 13.1, that one needed TWRP.
Click to expand...
Click to collapse
Before you flame someone you should read the link. FOR THE FIRST TIME YOU CAN KEEP STOCK RECOVERY SO YOU CAN TAKE OTAS
lollyjay said:
Before you flame someone you should read the link. FOR THE FIRST TIME YOU CAN KEEP STOCK RECOVERY SO YOU CAN TAKE OTAS
Click to expand...
Click to collapse
I have had stock recovery on more than one without having to reflash recovery with custom one .
If you use fastboot to flash the recovery, Instead of replacing with TWRP, you can use the command "fastboot boot TWRP.img" (TWRP.img being the name of the TWRP image you have such as twrp-3.1.1-0-oneplus5.img) , this will just boot you into TWRP where you can flash SuperSU or Magisk as you please but will revert back to stock recovery once you boot again while retaining root.
ultramag69 said:
I have had stock recovery on more than one without having to reflash recovery with custom one .
If you use fastboot to flash the recovery, Instead of replacing with TWRP, you can use the command "fastboot boot TWRP.img" (TWRP.img being the name of the TWRP image you have such as twrp-3.1.1-0-oneplus5.img) , this will just boot you into TWRP where you can flash SuperSU or Magisk as you please but will revert back to stock recovery once you boot again while retaining root.
Click to expand...
Click to collapse
No need to do that now
Honestly, who roots a phone without flashing a custom recovery the very second after? Unless they are forced to use Flashfire without BL unlock, I guess.
lollyjay said:
No need to do that now
Click to expand...
Click to collapse
Yeah, but using magisk to root my Axon 7 with unlocked bootloader didn't work...
There's still problems with some phones...
ultramag69 said:
Yeah, but using magisk to root my Axon 7 with unlocked bootloader didn't work...
There's still problems with some phones...
Click to expand...
Click to collapse
No problems at all with my OP5
Magisk 14.0 breaks XPosed so had to go back to Magisk 13.3
Now where can we obtain a copy of the stock boot.img?
almostthere said:
Now where can we obtain a copy of the stock boot.img?
Click to expand...
Click to collapse
What you're supposed to do is make a backup of your boot partition any time you update your rom. So if you didn't do that then you can dirty flash your current Rom and that would give you the stock boot.img and again, go into recovery and make a backup of your boot partition. then if you want to flash a custom kernel you can.
Help the noobs
Would any of you more experienced guys please post a step-by-step of how to do it?
From what Eric214 wrote I still don't understand where (or how) to get a copy of the stock_boot.img.
If you get the copy of the stock boot image, is it possible to do it without unlocking the bootloader?
I already installed everything before reading how to root - stupid me, and don't want to reinstall everything.
s_ofer said:
Would any of you more experienced guys please post a step-by-step of how to do it?
From what Eric214 wrote I still don't understand where (or how) to get a copy of the stock_boot.img.
If you get the copy of the stock boot image, is it possible to do it without unlocking the bootloader?
I already installed everything before reading how to root - stupid me, and don't want to reinstall everything.
Click to expand...
Click to collapse
I have the stock 4.5.10 boot.img for download here:
https://drive.google.com/file/d/0B3gcDbDvV4Mkbm5EMEZ4dnpSbk0/view?usp=drivesdk
Sent from my OnePlus5 using XDA Labs
Thanks.
Do any of you think it is possible to FLASH anything without unlocking the bootloader?
There is a thread somewhere for OP3T that shows somehow that is possible to load TWRP on the phone without unlocking the bootloader or wiping data.
I only use for root too but every so often I open magisk manager as it updates also both the manager app and magisk itself. But using magisk to root my Axon 7 with unlocked bootloader.