Database Users

[Q] Getting Lollipop on rooted Nexus 4 with custom recovery - guide for fools?

I want Lollipop and my Nexus 4 won't shut up about the OTA update. Naturally, it failed, and i have since tried to find a fool-proof guide to uptade it WITHOUT LOOSING DATA. Not been so lucky. Theres talk about fastbooting (?) and going back to stock, but not much in the way of step-by-step guides. I think most people with nexus 4 and root are like me - did it because it was easy, not knowing a lot about it...
I have rooted with towelroot, installed TWRP custom recovery with flashify, unlocked bootlocker with Bootunlock, installed Xposed framework and SuperSU. Never used ADB or any commands. Can't be the only one in this exact situation
What excactly do i need to do to get Lollipop without loosing any data (like a regular OTA update)?

Maybe user Titanium Backup or some kinda backup software to backup files and stuff then just go for a fresh installation? Most of the basic settings should be saved to your google account.
This post should help you with setting up ADB in your computer and to get you up to speed with using ADB and Fastbooot

KishanW said:
Maybe user Titanium Backup or some kinda backup software to backup files and stuff then just go for a fresh installation? Most of the basic settings should be saved to your google account.
This post should help you with setting up ADB in your computer and to get you up to speed with using ADB and Fastbooot
Click to expand...
Click to collapse
Thanks for the quick reply! But i was hoping for a solution that DIDN'T wipe my phone. I just wanna undo all the rooting business, so i can do the OTA...

605
tommyhj said:
Thanks for the quick reply! But i was hoping for a solution that DIDN'T wipe my phone. I just wanna undo all the rooting business, so i can do the OTA...
Click to expand...
Click to collapse
That would be interesting if someone has an answer for your question. I can use it too
Sorry that I couldn't help you.

tommyhj said:
I want Lollipop and my Nexus 4 won't shut up about the OTA update. Naturally, it failed, and i have since tried to find a fool-proof guide to uptade it WITHOUT LOOSING DATA. Not been so lucky. Theres talk about fastbooting (?) and going back to stock, but not much in the way of step-by-step guides. I think most people with nexus 4 and root are like me - did it because it was easy, not knowing a lot about it...
I have rooted with towelroot, installed TWRP custom recovery with flashify, unlocked bootlocker with Bootunlock, installed Xposed framework and SuperSU. Never used ADB or any commands. Can't be the only one in this exact situation
What excactly do i need to do to get Lollipop without loosing any data (like a regular OTA update)?
Click to expand...
Click to collapse
Hey,
Follow these instructions http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312.
there are a few things to note:
1. You do not need to unlock the bootloader, you will have done that when you rooted
2. Download the 5.0 image instead of the original stock image when you do this.
3. DO NOT flash userdata.img. That will wipe your data.
Those are the steps I followed to flash over to 5.0 without losing data.
But I would absolutely do a backup anyway, just in case something goes wrong.

gardn227 said:
Hey,
Follow these instructions http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312.
there are a few things to note:
1. You do not need to unlock the bootloader, you will have done that when you rooted
2. Download the 5.0 image instead of the original stock image when you do this.
3. DO NOT flash userdata.img. That will wipe your data.
Those are the steps I followed to flash over to 5.0 without losing data.
But I would absolutely do a backup anyway, just in case something goes wrong.
Click to expand...
Click to collapse
Ok, cool. So you're saying to towel-root my device, unlock bootloader with bootunlocker app, remove root by installing SuperSU and using the clean-up funtion. And then adb fastboot flash boot/recovery/system from the FACTORY img? Why not sideload the OTA instead? Because it wont work unless i reflash stock 4.4.4 completely?

[HOW-TO] [GUIDE] [MM] Encrypt device with custom rom, knox 1, twrp installed, rooted

This Guide will work on S7 and S7 Edge Variants, probably also on other Samsung Phones. It doesn't matter if you have xposed and/or supersu installed
I did lately try to encrypt my device after installing my rom. So I tried to search on xda but I couldn't find anything useful until now.
After quit some time I finally managed it to get a working encryption, even with custom rom installed (which contains root and xposed). I will present the following steps here to help you folks to get an encrypted device.
Root will work as always after encryption :highfive:
Attention, TWRP can't read /data partition after this guide, that's because twrp doesn't support samsungs encryption at all
Pre requests:
- A working pc with adb installed
- Enough battery (at least 80%)
- Charger in your near field
- Working internet connection
Steps:
1. Go to SuperSU application on your device
2. Head over to the settings Tab
3. Scroll down and hit Full unroot
4. Click continue, when it asks you to install stock boot.img say NO, also NO on restoring stock recovery
5. SuperSU app should disappear
6. Make one full reboot
7. Head over to settings, lock screen and security, set a password
8. Plug in your charger and start encryption
9. Wait until your phone has fully encrypted (this can take quit some time)
10. After your device has successfully encrypted, we want to gain root access again
11. Boot into TWRP recovery
12. You now need a pc with working adb connection
13. Click adb sideload on twrp
14. Download latest super su to your PC, you can get that from here: Beta Thread
15. Open a terminal on your PC
16. Put the supersu.zip in the same direction as your terminal is opened (example: user/home)
17. Type into terminal: adb sideload *supersu_name*.zip
18. Reboot your phone and you have a working, encrypted phone with root installed!
If this guide helped you, please share it and hit thanks as well! :good:

Tkkg1994 said:
After quite some time I finally managed it to get a working encryption, even with custom rom installed (which contains root and xposed). I will present the following steps here to help you folks to get an encrypted device.
Root will work as always after encryption :highfive:
Click to expand...
Click to collapse
:highfive:
Reverting/decrypting data would require a data wipe from TWRP, correct?

lost_ said:
:highfive:
Reverting/decrypting data would require a data wipe from TWRP, correct?
Click to expand...
Click to collapse
Exactly, with twrp or stock recovery

With TWRP not being abled to access /data partition, would it still be possible to make a complete nandroid? Second, what about updates of the custom ROM? Isn't the complete phone encrypted after the process, like /system and external sd as well?
Swyped via Tapatalk

what about systemless posed. would it work with the encryption, or it must be uninstalled.
I would like to try and encrypt my phone but I have systemless xposed installed and I would like to keep it. any information on that regards ?

Unfortunately it didnt worked for me. After i starting the encryption the phone does make a usual restart and i dont see any encryption process.
It just reboots. I am running cfw "S7 extreme debloated".
Any ideas?
btw: how safe is a rooted and encrypted phone, if you can replace any time the custom recovery?
are the encrypted partitions /data and /sdcard really safe?
Thanks...

@Tkkg1994 : Hi, I tried this method while using your Superman ROM, but unfortunatly it didn't work for me. After un-root the encryption application behaved as before: It started, saying "Encrypting...", but after some minutes it just rebooted with doing anything. So the device is still not encrypted. I read somewhere else, that in order to get the encryption working, the stock boot.img needs to be flashed. But that instruction have been for a different device, I guess dealing with a standard android encryption (as far as I now, Samsung uses a different one).
I'm just wondering, what would happen when I choose 'Yes' for replacing boot.img in step 4?

bruzzy said:
@Tkkg1994 : Hi, I tried this method while using your Superman ROM, but unfortunatly it didn't work for me. After un-root the encryption application behaved as before: It started, saying "Encrypting...", but after some minutes it just rebooted with doing anything. So the device is still not encrypted. I read somewhere else, that in order to get the encryption working, the stock boot.img needs to be flashed. But that instruction have been for a different device, I guess dealing with a standard android encryption (as far as I now, Samsung uses a different one).
I'm just wondering, what would happen when I choose 'Yes' for replacing boot.img in step 4?
Click to expand...
Click to collapse
That step 4 actually means you should restore your boot.img.
I did it exactly this way and it worked back then when I tested it. Many things have changed since then. So it may needs some adaptions
Sent from my Hydra powered SM-N930F

OK, I tried the other option as well (i. e. saying 'yes' on the question about testoring the boot.img). What about the kernel, do you know which one you used at that time? I'm currently on the Superstock Kernel. So curious, whether this might have any effect as well...
Sent from my SM-G930F using XDA-Developers mobile app

@Tkkg1994: Sorry for pushing, but do you remember, which kernel you've used? And can you also tell me, what exactly is the difference between the Stock and the Superstock kernel in your Superman ROM? Thanks!

bruzzy said:
@Tkkg1994: Sorry for pushing, but do you remember, which kernel you've used? And can you also tell me, what exactly is the difference between the Stock and the Superstock kernel in your Superman ROM? Thanks!
Click to expand...
Click to collapse
Back then it was stock.
Stock is signed properly by samsung and can be used with trusted UI on while custom kernels have to disable real time kernel protection to even boot the phone

tefole said:
Unfortunately it didnt worked for me. After i starting the encryption the phone does make a usual restart and i dont see any encryption process.
It just reboots. I am running cfw "S7 extreme debloated".
Any ideas?
btw: how safe is a rooted and encrypted phone, if you can replace any time the custom recovery?
are the encrypted partitions /data and /sdcard really safe?
Thanks...
Click to expand...
Click to collapse
I managed to encrypt by choosing full unroot in supersu app (say no to image restore questions).
Sadly, with a bootloader open, encryption will be as good as a password used. It's only entered once upon boot if you use fingerprints.
After encrypting root can be installed by flashing the zip again from sdcard or adb sideload.

Does not work for me. After I sideload SuperSU the phone does boot but my password is not recognised anymore.

hav0c said:
Does not work for me. After I sideload SuperSU the phone does boot but my password is not recognised anymore.
Click to expand...
Click to collapse
Hi hav0c, Which version did you upload? I used this: CF-Auto-Root-herolte-heroltexx-smg930f.zip.

Hi,
Does anyone have experience encrypting s7 nougat superstock rom? Wondering if it is the same. Because nougat has file-based encryption.

gnowak84 said:
Hi hav0c, Which version did you upload? I used this: CF-Auto-Root-herolte-heroltexx-smg930f.zip.
Click to expand...
Click to collapse
I have used https://download.chainfire.eu/supersu

So this doesn't work if we are using a non-stock kernel?

Tkkg1994 said:
Back then it was stock.
Stock is signed properly by samsung and can be used with trusted UI on while custom kernels have to disable real time kernel protection to even boot the phone
Click to expand...
Click to collapse
Hi Tkkg1994,
Wanted to know if you have any tip on the encrypt? Your work is really great and thanks for that but due to work i need to get the phone encrypt.
So wanted to know if you can help out as i dont want to go on stock firmware
Thank you

I tried following the guide using SuperStock 2.6, but after encryption finishes I get "Verification failed"

I have the same fault, any idea´s to fix same.

[GUIDE][osprey][merlin]How to root ANY Moto G 2015 model on Marshmallow

This guide covers ALL Moto G 2015 models (including the G Turbo) that can be bootloader unlocked and have TWRP available, it doesn't matter if it is the XT1540, XT1541, XT1543, etc., the method is identical. In fact, this method will work on all 2015 and 2016 series Moto phones running Marshmallow, including the Moto E, X, G3, G4, and Z.
Please read completely and make sure you understand each step and how to do it, if you don't get something search the thread or ask an open question.
tl;dr version for advanced users: Skip to "How to do it" section
I am writing this tutorial because there are still lots of failed root attempts using older "standard" methods that do not work on this device. I also do not like the "one click" root methods, because they can and do fail (KingoRoot will brick a Moto G3, regardless of what it's web page says), and when they do people have no idea how to fix it. The manual way is not difficult, and it teaches you how to work on, fix, and use your device on a level above that of the average smartphone user.
I will only cover the details of rooting, the prerequisites are covered elsewhere in detail and I will link to reliable sources for the information. Specifics of the prerequisites are outside of the scope of this tutorial, but are open for discussion in this thread.
Prerequisites:
1) Device must have an unlocked bootloader. See Moto - Unlocking the Bootloader for more info.
NOTE: Performing this prerequisite will give you all the tools (fastboot) and drivers needed to continue, and wipe your device, meaning erase all your information and programs. Make sure to backup any important data first. This step will also permanently void your warranty once an unlock code has been issued by Moto, it doesn't matter if you even use it, your warranty is done.
2) You need to have TWRP installed or one-time booted via fastboot. CWM and other recoveries will NOT work at this time. See TWRP for the Moto G 2015 or TWRP for Moto G Turbo.
3) You need a copy of the latest STABLE SuperSU ZIP from Chainfire's site on the internal storage or SD card of your device.
4) Reboot and start TWRP recovery, the method you use to do this doesn't matter (boot or flash).
How to do it:
Now, the procedure is the same whether you are trying to root the first time, or you did it the old way just flashing SuperSU and are now not able to boot...
In TWRP, go to Advanced and open the Terminal, in the terminal type this EXACTLY as shown:
Code:
echo SYSTEMLESS=true>>/data/.supersu
Now press enter (there is no confirmation returned), then exit and press the Home key. Go to Install and select the SuperSU zip file you downloaded from Prerequisite #3 and swipe to flash it and reboot. No need to clear caches or anything else but you are welcome to if you wish. You can install SuperSU updates normally through the app going forward (as of this posting).
Why do I have to do this???
For whatever reason, the install script for SuperSU does not recognize that this device (like many others) requires a systemless root installation. By creating /data/.supersu in the TWRP recovery environment, the SuperSU install script parses the file and sees "SYSTEMLESS=true" and ignores what it auto-detects and forces a systemless root installation.
Hope this is helpful to someone!
As always, if this is the first time you have booted TWRP or attempted root... BACKUP IN TWRP FIRST!!! Once the system is modified, it cannot be undone (easily) and you will always have a known good starting place if the worst happens.
DISCLAIMER: I am not responsible for anything that happens... Your device, your responsibility, no matter what happens... Although all the information here has been tested and is known to work with no issues except where noted, things occasionally can and do go wrong and we cannot foresee every possible scenario or circumstance.
If you need assistance, we need detailed information about what what's going on and what you have tried to do... Please provide details including:
1) Device model number and Android version
2) TWRP version
3) SuperSU version
4) Output of 'cat /data/.supersu' from TWRP terminal
And a copy of recovery.log if possible, and any other pertinent information you can think of. Without specific information there is nothing that I can do to assist you and request for help may be ignored.
Photos added showing what a proper command and flash should look like. Note that in picture 1 the exit command is not needed, you can just back out. In pictures 2 and 3 a proper flash of SuperSU is shown, note that system-less mode is specified and the boot image is patched, this is what should occur. It is normal for it to loop once or twice, but that is it, first boot could take 10 minutes plus.
EDIT: I no longer own or use this device, but will keep this thread open and will check it periodically for assisting the few people left out there who haven't rooted their Moto G 2015 yet.

Alternate Method
Some users have noted that the above method doesn't seem to work, we don't know why as it seems inconsistent but we can't pin it down specifically to user error, certain model number or build, or anything else, as it works 95% of the time...
But if the above method fails, the alternative is to download and copy to SD card or internal storage SuperSU 2.62-3 ßeta version available here and flash it through TWRP like normal.
After this is complete and boot is verified, update the SuperSU app via the Play Store to the current version, then open the SuperSU app and it should prompt you to update the su binary, go ahead and do that via the "Normal" process and reboot when complete.

can confirm, a simple flash won't work, phone stays on the splash screen, had to type op's command for root to work
Sent from my Nexus 6 using Tapatalk

After successful flashing super su it is not showing in app drawer , should I flash it again

25vikasp said:
After successful flashing super su it is not showing in app drawer , should I flash it again
Click to expand...
Click to collapse
SuperSU should show up in the app drawer after a successful flash.
Make sure you enabled changes to system, did the terminal command, and when you flash the zip for SuperSU watch the recovery log, it should say something about "systemless". If not, please attach a copy of recovery.log file

acejavelin said:
SuperSU should show up in the app drawer after a successful flash.
Make sure you enabled changes to system, did the terminal command, and when you flash the zip for SuperSU watch the recovery log, it should say something about "systemless". If not, please attach a copy of recovery.log file
Click to expand...
Click to collapse
[/QUOTE]
See this.i don't know

25vikasp said:
See this.i don't know
Click to expand...
Click to collapse
Hmm... looks like it patched the boot.img successfully. Try installing the SuperSU app from the Play Store and see if it says the binary is properly installed.
I haven't tried this with the 2.77beta yet, I know it had some changes specifically for the Note 7 because Samsung tried to make it unrootable (but failed), I have been using the latest stable build of 2.76

acejavelin said:
See this.i don't know
Hmm... looks like it patched the boot.img successfully. Try installing the SuperSU app from the Play Store and see if it says the binary is properly installed.
I haven't tried this with the 2.77beta yet, I know it had some changes specifically for the Note 7 because Samsung tried to make it unrootable (but failed), I have been using the latest stable build of 2.76
Click to expand...
Click to collapse
At last solved.that latest super su has some bugs so I just tried below version and now it is showing.thanks mate
Click to expand...
Click to collapse

25vikasp said:
At last solved.that latest super su has some bugs so I just tried below version and now it is showing.thanks mate
Click to expand...
Click to collapse
Thank you... I will update the OP to show that 2.77beta is not compatible.

stuck in Boot screen after flashing SU in My MOTO g TE 6.0.1
Pls help Me

krisbeowolf said:
stuck in Boot screen after flashing SU in My MOTO g TE 6.0.1
Pls help Me
Click to expand...
Click to collapse
Stuck on boot screen is classic case of not being a systemless install. Review your SuperSU version and make sure you entering the terminal command EXACTLY as shown in OP. If entered correctly the SuperSU script will "fix" a standard flash with a systemless one.
Otherwise, please give me more information... What version of SuperSU and TWRP, and recovery.log or a snapshot/pic of the recovery terminal screen after flashing SuperSU.
Sent from my Motorola XT1575 using XDA Labs

acejavelin said:
Stuck on boot screen is classic case of not being a systemless install. Review your SuperSU version and make sure you entering the terminal command EXACTLY as shown in OP. If entered correctly the SuperSU script will "fix" a standard flash with a systemless one.
Otherwise, please give me more information... What version of SuperSU and TWRP, and recovery.log or a snapshot/pic of the recovery terminal screen after flashing SuperSU.
Sent from my Motorola XT1575 using XDA Labs
Click to expand...
Click to collapse
Latest version of twrp 3.0.0 r2 and super SuperSU version v2.62-3 recommended one...

krisbeowolf said:
Latest version of twrp 3.0.0 r2 and super SuperSU version v2.62-3 recommended one...
Click to expand...
Click to collapse
Please read the first post in this thread again and get the current stable version. No where do I recommend that version with my procedure, current stable release is 2.76
Sent from my Motorola XT1575 using XDA Labs

acejavelin said:
Please read the first post in this thread again and get the current stable version. No where do I recommend that version with my procedure, current stable release is 2.76
Sent from my Motorola XT1575 using XDA Labs
Click to expand...
Click to collapse
can you give me the link

krisbeowolf said:
can you give me the link
Click to expand...
Click to collapse
Read the first post of this thread, completely, paying attention to prerequisite #3!!! If you are using SuperSU v2.62-3 Beta you are NOT following my instructions for rooting, are you sure you are posting in the correct thread?
acejavelin said:
3) You need a copy of the latest STABLE SuperSU ZIP from Chainfire's site on the internal storage or SD card of your device. As of this posting UPDATE-SuperSU-v2.76-20160630161323.zip is the current stable version.
NOTE: Version 2.77 BETA is intended specifically for the Note 7 and should not be used for rooting Moto devices, in testing it doesn't brick or stop boot, it just doesn't show up or work.
Click to expand...
Click to collapse

How to make backup before unlocking bootloader?
@acejavelin,
I am not rooted, bootloader is not unlocked. I am planning to root my phone. But do you know of anything that can be used to backup my data before unlocking bootloader? If you do know, please tell me about it or maybe provide the link.
Thanks in advance.

sanchith.hegde said:
@acejavelin,
I am not rooted, bootloader is not unlocked. I am planning to root my phone. But do you know of anything that can be used to backup my data before unlocking bootloader? If you do know, please tell me about it or maybe provide the link.
Thanks in advance.
Click to expand...
Click to collapse
Backup photos and videos with Google Photo app, and SMS with SMS Backup & Restore app. All system information should be stored in your Google account along with apps you have installed. You can also use ADB with this method http://www.technipages.com/how-to-backup-your-entire-android-device
Sent from my Motorola XT1575 using XDA Labs

acejavelin said:
Backup photos and videos with Google Photo app, and SMS with SMS Backup & Restore app. All system information should be stored in your Google account along with apps you have installed. You can also use ADB with this method http://www.technipages.com/how-to-backup-your-entire-android-device
Click to expand...
Click to collapse
Thanks man for your help.
By the way, will ADB work without root?

sanchith.hegde said:
Thanks man for your help.
By the way, will ADB work without root?
Click to expand...
Click to collapse
Yes, just enable it in Developer options.

I absolutely can not get Super User Root, I followed this OP to the letter, I have tried to root, in TWRP Recovery, using the linked SuperSu from both storages ie.. internal storage, and one I placed on my adaptive/portable/ExtSdcard. Went to advanced, terminal typed the "echo.....etc", then flashed, and it says while flashing the Super Su file it's installing "systemless" and looks fine, goes through the whole process tells me to reboot, and then just loads right up no wait, BUT NO Super Su file, tried downloading SuperSu apk from playstore manually, after boot up and it doesn't recognize any root[emoji30]
I have tried this on both allowing the changes at the beginning of recovery, and also not allowing the changes, at the beginning of the recovery, lucky I backed up at first boot of TWRP, which I went into immediately after flashing it via adb/fastboot
I am at a loss, and completely frustrated at this point, any assistance would be so so thankful, thanks
Sent from my MotoG3 using XDA-Developers mobile app

[HELP] Rooted Partially - Want to Unroot back

Hi Everyone,
I might have a problem now after tried to root my Axon 7 A2017 B27 (using the instruction http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204). Unfortunately, the phone seems rooted partially after that.
Root Checker told me it's unrooted. But when i tried to upgrade to B29 package today, after downloaded and rebooted, it went to TWRP and couldn't be installed itself. The system indicated my phone has been rooted.
Now i'd like to unroot it back. Anyone could help and provide the detail step i should do? Thank you very much!

liuyiji said:
Hi Everyone,
I might have a problem now after tried to root my Axon 7 A2017 B27 (using the instruction http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204). Unfortunately, the phone seems rooted partially after that.
Root Checker told me it's unrooted. But when i tried to upgrade to B29 package today, after downloaded and rebooted, it went to TWRP and couldn't be installed itself. The system indicated my phone has been rooted.
Now i'd like to unroot it back. Anyone could help and provide the detail step i should do? Thank you very much!
Click to expand...
Click to collapse
2 choices.
1. http://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484 best option. Use TWRP to install the B29 bootstack and B29 system. It worked for me.
2. Use the backups you made from the axon7backup.exe - move the files to the same folder you have the axon7root.exe, delete the boot and recovery files there, rename your backup files accordingly, and the axon7root.exe program will flash those files when you run the axon7root.exe program.
I really recommend using option 1. Much easier and quite frankly DrakenFX made it idiotproof.

tabletalker7 said:
2 choices.
1. http://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484 best option. Use TWRP to install the B29 bootstack and B29 system. It worked for me.
2. Use the backups you made from the axon7backup.exe - move the files to the same folder you have the axon7root.exe, delete the boot and recovery files there, rename your backup files accordingly, and the axon7root.exe program will flash those files when you run the axon7root.exe program.
I really recommend using option 1. Much easier and quite frankly DrakenFX made it idiotproof.
Click to expand...
Click to collapse
Thanks so much @tabletalker7. I just noticed this new post. Will try the option 1 for sure. When you did that, did all the data wipe out? If so, would you mind tell me which tool you use to backup the apps? Thanks again.

You do have to wipe data so I assume you lose everything - I have nothing important on the phone storage so I can wipe my phone all I want all I need is my sd card. Don't know of any way to not lose apps, but google did restore everything when I set up the phone on B29.

tabletalker7 said:
You do have to wipe data so I assume you lose everything - I have nothing important on the phone storage so I can wipe my phone all I want all I need is my sd card. Don't know of any way to not lose apps, but google did restore everything when I set up the phone on B29.
Click to expand...
Click to collapse
Thanks, will try some way to backup first then

liuyiji said:
Hi Everyone,
I might have a problem now after tried to root my Axon 7 A2017 B27 (using the instruction http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204). Unfortunately, the phone seems rooted partially after that.
Root Checker told me it's unrooted. But when i tried to upgrade to B29 package today, after downloaded and rebooted, it went to TWRP and couldn't be installed itself. The system indicated my phone has been rooted.
Now i'd like to unroot it back. Anyone could help and provide the detail step i should do? Thank you very much!
Click to expand...
Click to collapse
Something to keep in mind for next time: you cannot apply official OTA updates if you have a modified boot.img (systemless root), modified recovery.img (TWRP), or have modified the /system partition (some root apps do this). You need to be completely stock (sans unlocked bootloader) in order to apply official OTA updates.

xtermmin said:
Something to keep in mind for next time: you cannot apply official OTA updates if you have a modified boot.img (systemless root), modified recovery.img (TWRP), or have modified the /system partition (some root apps do this). You need to be completely stock (sans unlocked bootloader) in order to apply official OTA updates.
Click to expand...
Click to collapse
Thx, @xtermmin. I'm just switching from iphone to android, need more time to study. Seems it would not easy for me to get the phone unrooted as well, lol

How could I reset everything, update to 10.3.0 and then reinstall TWRP+Magisk?

Heya everyone,
I've got my 6T with Android 10 rooted that it's giving me some troubles. I made some mistakes when I updated to android 10 so now I would like someone to help me doing these steps the proper way.
I would like to:
Reset the whole phone with a fresh install of Android like factory, if possibile already updated to the Android 10.3.0 (i've already downloaded the full OTA and Ive got ADB installed and working),
then I'll want to install TWRP and Magisk from scratch too and at the end I'll install apps and I'll restore datas (only those needed like pictures or google drive/whatsapp backups).
I'm not sure which steps do I have to follow to do this without breaking something during the process.
Thanks

All is written here and still valid, read first posts carefully.
Use latest .30 twrp version and latest Magisk zip
https://forum.xda-developers.com/oneplus-6t/how-to/guide-oneplus-6t-unlock-bootloader-t3851789

Striatum_bdr said:
All is written here and still valid, read first posts carefully.
Use latest .30 twrp version and latest Magisk zip
https://forum.xda-developers.com/oneplus-6t/how-to/guide-oneplus-6t-unlock-bootloader-t3851789
Click to expand...
Click to collapse
Thanks. I'll follow the guide.
Before rooting how could I factory reset everything and update the phone. I would like to be sure that everything done in the past will be cleared.
Thanks
Sent from my ONEPLUS A6013 using Tapatalk

RikiBez said:
Thanks. I'll follow the guide.
Before rooting how could I factory reset everything and update the phone. I would like to be sure that everything done in the past will be cleared.
Thanks
Click to expand...
Click to collapse
Unlocking the bootloader is a factory reset. If already done, reboot in recovery and do it from there

Striatum_bdr said:
Unlocking the bootloader is a factory reset. If already done, reboot in recovery and do it from there
Click to expand...
Click to collapse
Do you mean from the TWRP recovery? I checked it but I don't know from which menu to do it.
Or is it possible and better to do it from ADB? If yes which command do I need to use?

RikiBez said:
Do you mean from the TWRP recovery? I checked it but I don't know from which menu to do it.
Or is it possible and better to do it from ADB? If yes which command do I need to use?
Click to expand...
Click to collapse
There is a factory reset function in phone settings > system
If not enough
https://twrp.me/faq/whattowipe.html
Please use Google that's exactly what I do to answer you

Striatum_bdr said:
There is a factory reset function in phone settings > system
If not enough
https://twrp.me/faq/whattowipe.html
Please use Google that's exactly what I do to answer you
Click to expand...
Click to collapse
I used Google and searched the forum. I read some guides but I made the thread cause I would like to have an help from someone that knows what I need to do step by step cause I don't want to fail.
Sent from my ONEPLUS A6013 using Tapatalk

[deleted]

Follow this thread to rollback to pie..
This will wipe your data and do the reset that you want..
From there you can update to latest 10.3.0 and install twrp and magisk afterwards...
https://forum.xda-developers.com/on...owngrade-oos-android-10-t4000645/post80843523

An important question is. Do you need TWRP? Because you don't need TWRP for root. If you want root, i suggest just flashing the patched boot.img.
You can factory reset from any recovery by wiping everything.

bokkoman said:
An important question is. Do you need TWRP? Because you don't need TWRP for root. If you want root, i suggest just flashing the patched boot.img.
You can factory reset from any recovery by wiping everything.
Click to expand...
Click to collapse
I'm not really sure for what I need TWRP but I always used to install it with Magisk.
Sent from my ONEPLUS A6013 using Tapatalk

Steps that I followed to solve
I would like to thanks @Striatum_bdr and @cultofluna for their tips.
I solved doing this:
I saved camera pictures, downloads folder and anything else I need by dragging and dropping from phone to PC. I also made backups of Whatsapp, Nova Launcher and other tools I would to restore.
I downloaded the rollback and folloed the instructions from here: https://forum.xda-developers.com/on...owngrade-oos-android-10-t4000645/post80843523
After that I started the phone skipping most of the requests
Updated it a couple of times until I was on Android 10.3.0
Then I followed the standard rooting guide for the OnePlus 6T: https://forum.xda-developers.com/oneplus-6t/how-to/guide-oneplus-6t-unlock-bootloader-t3851789 using files from this new post related to Android 10: https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
When I finished I had a fully rooted Android 10.3.0 with TWRP on both slots.
At the end I made a factory reset from the system setting to clear the my answers to the questions that I skipped at the beginning and I configured it as I wish.
I downloaded apps and restored files and backups from PC and cloud drives
List of files that I've used:
https://drive.google.com/file/d/1L7EZGx5mgeQYXO19Vsp9FWu9GXhF45Qs/view (PC)
https://drive.google.com/file/d/1-uWQn-oHu_ROuDVCzIyrExoRbsSBYTtU/view (PC)
https://www.androidfilehost.com/?fid=4349826312261677894 (PC)
https://www.androidfilehost.com/?fid=4349826312261677893 (Phone)
https://github.com/topjohnwu/Magisk/releases/download/v20.1/Magisk-v20.1.zip (Phone)
https://github.com/topjohnwu/Magisk/releases/download/manager-v7.4.0/MagiskManager-v7.4.0.apk (Phone)

I guess the easiest way would to just go to recovery, wipe everything (after backup first of course).
Then adb sideload your ROM (in this example OOS 10.3.0) in recovery and let it install.
Reboot your phone and go thru first steps.
Go to fastboot and flash patched boot.img (magisk patched, look for the boot corresponding to your ROM) to gain root and reboot again.
Now you're all set.
No need for TWRP or anything. Just update the normal way and install magisk through magisk manager to inactive slot before you reboot after update.