Return to Android 11 stock - OnePlus 6 Questions & Answers

I currently have android 11 which about 2 years ago I unlocked, installed TWRP and rooted. I later allowed the phone to update but didn't realize I should have re-flashed TWRP and root before I rebooted the phone so I lost the use of TWRP and root. Now I want to reflash android 11 but wont unlock and root the phone again but want TWRP. How do I go about doing this (I am not strong with what I need to do and have usually caused a problem before by using the wrong enchilada file, the last one that worked was twrp-3.3.1-18-enchilada-Q-mauronofrio I think) and which files should I use?

you can't flash anything on a locked phone so at the very least you can have it unlocked + twrp and no root if you wish
otherwise no twrp

croperas said:
you can't flash anything on a locked phone so at the very least you can have it unlocked + twrp and no root if you wish
otherwise no twrp
Click to expand...
Click to collapse
That's what I want to do, sorry for any misunderstanding, I want to lock the phone so I can use financial apps and also have TWRP. What process and enchilada shall I use? I already downloaded OnePlus6TOxygen_34.J.62.

Westindieman said:
That's what I want to do, sorry for any misunderstanding, I want to lock the phone so I can use financial apps and also have TWRP. What process and enchilada shall I use? I already downloaded OnePlus6TOxygen_34.J.62.
Click to expand...
Click to collapse
That's what i was saying, this is not possible, locking or unlocking requires full wipe which nullifies any custom things you do.
You can have a phone that's not rooted which should be good enough for most checks but if it checks the bootloader there's nothing you can do about it besides not use it or use stock

croperas said:
That's what i was saying, this is not possible, locking or unlocking requires full wipe which nullifies any custom things you do.
You can have a phone that's not rooted which should be good enough for most checks but if it checks the bootloader there's nothing you can do about it besides not use it or use stock
Click to expand...
Click to collapse
I understand now thanks for your patience. What process should I follow then to return from here to stock and locked considering I don't have TWRP?

Westindieman said:
I understand now thanks for your patience. What process should I follow then to return from here to stock and locked considering I don't have TWRP?
Click to expand...
Click to collapse
Backup what you need
Relock the bootloader
Flash stock rom using fastboot

I have relocked and am now trying to work out how to flash the new rom

All sorted now, didn't need to flash a new ROM

Awesome, Enjoy the phone

Related

[Q] Signed ROM possible?

Can I have locked boot loader and be able to flash a custom ROM? It would need to be signed by who, Google, LG?
MAXGEN said:
Can I have locked boot loader and be able to flash a custom ROM? It would need to be signed by who, Google, LG?
Click to expand...
Click to collapse
Sure just send it to Google and haven them rebuild and sign it as a factory image (just kidding off course). No, that`s off course not possible.
-Edit- Read the first 4-5 threads in this section before you do anything
MAXGEN said:
Can I have locked boot loader and be able to flash a custom ROM? It would need to be signed by who, Google, LG?
Click to expand...
Click to collapse
With a locked bootloader, you cannot flash anything using fastboot.
However, if you unlocked bootloader, installed custom recovery, then relocked bootloader (pointless), you can still install stuff from recovery.
But fastboot cannot be used to flash anything (even stock Google factory image).
You sound like you come from a HTC (or similar) device where you would need to relock bootloader to flash a stock RUU, a Nexus is totally different than a HTC device. :good:
Edit: Be warned that unlocking the bootloader using "fastboot oem unlock" wipes EVERYTHING except the OS on the phone.
Thanks for the quick response.
How do ROM updates (ex. 4.0 to 4.1 ) get pushed from either the manufacturer like LG or Samsung or Google for there devices then? You have to unlock you phone to update? Typically on Samsung I downloaded through TouchWiz and then it restarted on its own and installed on its own without user unlocking anything.
So how do updates then get pushed? They must be signed and get around the lock boot loader some how? I guess the signed ROM is able to unlock it to install is that purpose then?
MAXGEN said:
Thanks for the quick response.
How do ROM updates (ex. 4.0 to 4.1 ) get pushed from either the manufacturer like LG or Samsung or Google for there devices then? You have to unlock you phone to update? Typically on Samsung I downloaded through TouchWiz and then it restarted on its own and installed on its own without user unlocking anything.
So how do updates then get pushed? They must be signed and get around the lock boot loader some how? I guess the signed ROM is able to unlock it to install is that purpose then?
Click to expand...
Click to collapse
For Google updates there is no need to be unlocked, you talked about flashing a custom rom. Updates get downloaded and installed automaticaly in fastboot.
MAXGEN said:
So how do updates then get pushed? They must be signed and get around the lock boot loader some how? I guess the signed ROM is able to unlock it to install is that purpose then?
Click to expand...
Click to collapse
Flashing /system has nothing to do with the bootloader. OTA updates flash to /system via stock recovery.
A locked bootloader prevents you fastboot flashing. You could unlock the bootloader, fastboot flash a custom recovery then lock the bootloader again. You would still be able to flash /system with custom roms. Bootloader doesn't prevent flashing. It just prevents fastboot flashing
Sent from my Nexus 5 using Tapatalk
rootSU said:
Flashing /system has nothing to do with the bootloader. OTA updates flash to /system via stock recovery.
A locked bootloader prevents you fastboot flashing. You could unlock the bootloader, fastboot flash a custom recovery then lock the bootloader again. You would still be able to flash /system with custom roms. Bootloader doesn't prevent flashing. It just prevents fastboot flashing
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
What stops custom roms being flash through stock recovery?
What stops custom ROM be a OTA so it can be flash stock recovery?
MAXGEN said:
What stops custom roms being flash through stock recovery?
What stops custom ROM be a OTA so it can be flash stock recovery?
Click to expand...
Click to collapse
googles signature
simms22 said:
googles signature
Click to expand...
Click to collapse
BK in the house! Anyways.
Just to clear things up for me.
If I keep my stock recovery and keep boot loader lock, then I can't flash my ROM unless I have Google keys. Okay I got that but mentioned earlier that you can flash to the /system, OTA (Over the Air) package, does that have to be signed for that? What is the mechanism to flash OTA, stock recovery or something else?
Ultimately, something like CM is doing, if I make a ROM, I could make my own recovery and with my own keys and call it verified and safe and push OTA packages for updates??
Everything official is signed. Nothing unofficial can be signed. Nothing unsigned can be flashed without either a custom recovery or unlocked bootloader.
Hope this clears everything up for you.
Sent from my Nexus 5 using Tapatalk
Could you replace the
/system/etc/security/otacerts.zip
or
/META-INF/com/android/otacert file
with your own??
Lets cut to the chase. What is your ultimate aim here?
Sent from my Nexus 5 using Tapatalk
rootSU said:
Lets cut to the chase. What is your ultimate aim here?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
LOL
Just trying to get an direction so I continue to do further research. Mostly my aim is more in depth understanding.
I want to build my own ROM and I'm starting that journey. Definitely a newbie but not a newbie to technology and programing and by no means an expert. Just a senior college student that with enough information to be "dangerous".
I would like to have ROM that doesn't need to have unlock boot loader or have custom recovery? Is that possible? i feel a lot ppl I meet don't like to use Custom ROMs b/c of these hurdles. I guess I would have to have root access to change out the CERTS either way.
You can't even flash a full official rom without unlocking the bootloader. It isn't possible on this device
Sent from my Nexus 5 using Tapatalk
MAXGEN said:
LOL
Just trying to get an direction so I continue to do further research. Mostly my aim is more in depth understanding.
I want to build my own ROM and I'm starting that journey. Definitely a newbie but not a newbie to technology and programing and by no means an expert. Just a senior college student that with enough information to be "dangerous".
I would like to have ROM that doesn't need to have unlock boot loader or have custom recovery? Is that possible? i feel a lot ppl I meet don't like to use Custom ROMs b/c of these hurdles. I guess I would have to have root access to change out the CERTS either way.
Click to expand...
Click to collapse
I think if it was possible, it would have been done already. But its not that big of a hurdle to unlock and root. Its actually a lot more easier than it seems. It usually takes about 5 minutes to do after getting all the necessary files. All you need is a general understanding and the ability to follow directions well.
You can't even flash a full official rom without unlocking the bootloader. It isn't possible on this device
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
No i went right to a custom, unlock, root, custom Recovery, Custom Rom
jsgraphicart said:
I think if it was possible, it would have been done already. But its not that big of a hurdle to unlock and root. Its actually a lot more easier than it seems. It usually takes about 5 minutes to do after getting all the necessary files. All you need is a general understanding and the ability to follow directions well.
Click to expand...
Click to collapse
On Samsung pushed OTA and reboot and install...DONE.
So it is possible!
It isn't as easy as you think because more people would have it. I walk into any CS class less then 10% are rooted or Custom. Most of them probably are on iphones but that's different. My point is that you would think some what intelligent geeks would take the time to do so but they don't. IMO there are still hurdles and CM are trying to breach these inconveniences except Google doesn't like it.
MAXGEN said:
No i went right to a custom, unlock, root, custom Recovery, Custom Rom
On Samsung pushed OTA and reboot and install...DONE.
So it is possible!
It isn't as easy as you think because more people would have it. I walk into any CS class less then 10% are rooted or Custom. Most of them probably are on iphones but that's different. My point is that you would think some what intelligent geeks would take the time to do so but they don't. IMO there are still hurdles and CM are trying to breach these inconveniences except Google doesn't like it.
Click to expand...
Click to collapse
on samsung, samsung signs the roms, not google. so of course its possible for them.
simms22 said:
on samsung, samsung signs the roms, not google. so of course its possible for them.
Click to expand...
Click to collapse
So essentially you just need to replace the certs to push your own OTAs through your device. Which at some point you would need access to those CERTs so you would need root access.
MAXGEN said:
No i went right to a custom, unlock, root, custom Recovery, Custom Rom
Click to expand...
Click to collapse
I wasn't asking a question. I was telling you it is not even possible to flash official nexus 5 full rom from Google without unlocking the bootloader.
MAXGEN said:
On Samsung pushed OTA and reboot and install...DONE.
So it is possible!
Click to expand...
Click to collapse
As mentioned, because they signed the update and it matched what their rom and their recovery expected.
You cannot simply "guess" a signature. You cannot reverse engineer a signature. All you can do is remove whatever is validating the signature and this cannot be done without unlocking the bootloader
Sent from my Nexus 5 using Tapatalk
MAXGEN said:
On Samsung pushed OTA and reboot and install...DONE.
So it is possible!
It isn't as easy as you think because more people would have it. I walk into any CS class less then 10% are rooted or Custom. Most of them probably are on iphones but that's different. My point is that you would think some what intelligent geeks would take the time to do so but they don't. IMO there are still hurdles and CM are trying to breach these inconveniences except Google doesn't like it.
Click to expand...
Click to collapse
Are you talking about an OTA from Samsung or a custom ROM OTA without unlocking the phone. If its from Samsung then yeah, they have all the stuff to put into the OTA to bypass the locked bootloader. But anything like that probably has to come from the manufacturer because they are the only ones who have the "keys". I have never owned a Samsung device (other than the Galaxy Nexus but that was more Google). So if I'm just not understanding that, then I apologize. I think around XDA, everyone here just finds it easier to unlock, root and be on their way. But if you find a workaround, I'm sure people would be interested.

Root Without BL unlock

Hello guys
im looking to root my OPO, but i dont want to unlock the Bootloader or install a custom recovery, just want a method to root so i can install Xposed on the stock CM11S rom, is this actually possible?
Why not just unlock the bootloader? Your warranty isn't affected by it. You lose nothing by unlocking it, and you gain nothing by leaving it locked.
Transmitted via Bacon
Jaocagomez said:
Hello guys
im looking to root my OPO, but i dont want to unlock the Bootloader or install a custom recovery, just want a method to root so i can install Xposed on the stock CM11S rom, is this actually possible?
Click to expand...
Click to collapse
timmaaa said:
Why not just unlock the bootloader? Your warranty isn't affected by it. You lose nothing by unlocking it, and you gain nothing by leaving it locked.
Transmitted via Bacon
Click to expand...
Click to collapse
Like @timmaaa mentioned, you lose nothing when you unlock bootloader. Not only that, it is the recommended and futureproof approach to do so. Unlocking the bootloader wipes your phone completly clean. Suppose somewhere down the road you want to try different ROMs, you'd realize you cannot do so without losing your data. So you'r much better off unlocaking your bootlaoder right now.
But to answer your question, no. It is not possible at a simpler level. Unlocking the bootlaoder give you access to all the partitions on the phone. What you need access to specifically is the recovery partition so you could flash a custom recovery and install the SU binaries onto your system. through that recovery.
What others have said, unlock the bootloader there's no problem with leaving it unlocked.
You're given the key to unlock the bootloader using a command. Use it and make your life simple. It's like saying you have the key to your house but you want to get inside the house without unlocking the door. Just use the key and make it simple.
Sent from my One A0001 using Tapatalk
Jaocagomez said:
Hello guys
im looking to root my OPO, but i dont want to unlock the Bootloader or install a custom recovery, just want a method to root so i can install Xposed on the stock CM11S rom, is this actually possible?
Click to expand...
Click to collapse
Perhaps you felt like I did, worried that you are ruining your phone or your ota ability.
Unlocking the Bootloader is painless aside from having to reinstall all your programs. Everyone says it wipes the os, but what they don't tell you is that you don't have to dig around looking for the proper version to reinstall. You just type a code, and the phone reboots fresh like a factory reset, ready to go. And installing the custom recovery is easy, and it works perfectly with ota updates.
Sent via quantum entanglement, focused through my OnePlus One.

[Q] Error message while installing android lollipop on Nexus 5

Im trying to install Android Lollipop on my Nexus 5, but once it downloads I try to install it and it gets about halfway through the install before an error message appears and my phone restarts. My phone is unlocked and has been rooted before, but it isn't at the moment. Any help would be great, Thanks!
eatcyanide said:
Im trying to install Android Lollipop on my Nexus 5, but once it downloads I try to install it and it gets about halfway through the install before an error message appears and my phone restarts. My phone is unlocked and has been rooted before, but it isn't at the moment. Any help would be great, Thanks!
Click to expand...
Click to collapse
Do you have a custom recovery or flashed a kernel? You must be 100% stock
Sent from my Nexus 5 using XDA Free mobile app
I'm on stock android. The only thing I have changed is rooting it and unlocking it
Sent from my Nexus 5
eatcyanide said:
I'm on stock android. The only thing I have changed is rooting it and unlocking it
Sent from my Nexus 5
Click to expand...
Click to collapse
I am stuck in the same situation. Tried it twice with no luck.
I too rooted my phone with towelroot and unrooted it with superSu.
Did you find any solution? Please do share. Thanks.
eatcyanide said:
Im trying to install Android Lollipop on my Nexus 5, but once it downloads I try to install it and it gets about halfway through the install before an error message appears and my phone restarts. My phone is unlocked and has been rooted before, but it isn't at the moment. Any help would be great, Thanks!
Click to expand...
Click to collapse
rahul9five said:
I am stuck in the same situation. Tried it twice with no luck.
I too rooted my phone with towelroot and unrooted it with superSu.
Did you find any solution? Please do share. Thanks.
Click to expand...
Click to collapse
You either have a modified system file or a file left over from being rooted. The easiest and fastest solution would be to fastboot flash the system image. You could of course flash the factory image.
wantabe said:
You either have a modified system file or a file left over from being rooted. The easiest and fastest solution would be to fastboot flash the system image. You could of course flash the factory image.
Click to expand...
Click to collapse
Well now i remember changing the mixer_path.xml ... Will i have to unlock my bootloader to flash the factory image as i had rooted my phone with towelroot so i didnt have to do it earlier..
Also is it possible to replace the mixer path file with the original one from the internet
rahul9five said:
Well now i remember changing the mixer_path.xml ... Will i have to unlock my bootloader to flash the factory image as i had rooted my phone with towelroot so i didnt have to do it earlier..
Also is it possible to replace the mixer path file with the original one from the internet
Click to expand...
Click to collapse
That sucks! ; ) I've always used the sdk so I don't know a whole lot about towelroot. Your bootloader will have to be unlocked to flash the factory image. If you can reroot you could then use the app BootUnlocker.
I just looked and I don't have the stock mixer_paths.xml anymore or I would link to it.
wantabe said:
That sucks! ; ) I've always used the sdk so I don't know a whole lot about towelroot. Your bootloader will have to be unlocked to flash the factory image. If you can reroot you could then use the app BootUnlocker.
I just looked and I don't have the stock mixer_paths.xml anymore or I would link to it.
Click to expand...
Click to collapse
Thankyou for your efforts and advise. I guess i will just rerrot with towelroot, unclock the bootloader with the app you suggestee and flash factory image..
Btw. Will flashing the factory image unroot my phone and lock the bootloader or is there some procedure that needs to be done to do that?
rahul9five said:
Thankyou for your efforts and advise. I guess i will just rerrot with towelroot, unclock the bootloader with the app you suggestee and flash factory image..
Btw. Will flashing the factory image unroot my phone and lock the bootloader or is there some procedure that needs to be done to do that?
Click to expand...
Click to collapse
Flashing the factory image or a system image will always unroot your device. Lock the bootloader using the sdk. The command is fastboot oem lock.
Is there a reason why OP needs locked bootloader? Just leave it unlocked, unless you have a really strong reason to. It will spare you hassles in the future.
That said, after unlocking bootloader, you can (at least, we could in the past) flash the update file through twrp (you just need to fastboot boot twrp.img and then flash the update), that will tell you exactly what file(s) doesn't match. Those are the ones you need to replace back to stock.
Edit: read also http://forum.xda-developers.com/showthread.php?t=2949987. Maybe new selinux stuff is playing funny?
beekay201 said:
Is there a reason why OP needs locked bootloader? Just leave it unlocked, unless you have a really strong reason to. It will spare you hassles in the future.
That said, after unlocking bootloader, you can (at least, we could in the past) flash the update file through twrp (you just need to fastboot boot twrp.img and then flash the update), that will tell you exactly what file(s) doesn't match. Those are the ones you need to replace back to stock.
Edit: read also http://forum.xda-developers.com/showthread.php?t=2949987. Maybe new selinux stuff is playing funny?
Click to expand...
Click to collapse
Yea, you can't flash the ota through a custom recovery anymore
Sent from my Nexus 9 using XDA Free mobile app
beekay201 said:
Is there a reason why OP needs locked bootloader? Just leave it unlocked, unless you have a really strong reason to. It will spare you hassles in the future.
That said, after unlocking bootloader, you can (at least, we could in the past) flash the update file through twrp (you just need to fastboot boot twrp.img and then flash the update), that will tell you exactly what file(s) doesn't match. Those are the ones you need to replace back to stock.
Edit: read also http://forum.xda-developers.com/showthread.php?t=2949987. Maybe new selinux stuff is playing funny?
Click to expand...
Click to collapse
Thankyou.. I am more of a soft modder. Like playing with rooted apps and xposed mainly. I dont see myself flashing a custom rom. Love the stock on my nexus 5. So i dont see the need to leave the bootloader unlocked.
rahul9five said:
Thankyou.. I am more of a soft modder. Like playing with rooted apps and xposed mainly. I dont see myself flashing a custom rom. Love the stock on my nexus 5. So i dont see the need to leave the bootloader unlocked.
Click to expand...
Click to collapse
Err... I didn't suggest that you flash a custom ROM. Read what I said.

Unlock bootloader then rooting method?

Hey everyone, I've been lurking around for about two months, from when I picked up this phone. It's still completely stock. Unrooted, S-ON, all that. Well, after the update to Nougat, I've been searching for a way to unlock the bootloader & root. Is it safe for me to use WinDroid Toolkit for the process? Just need a guide for the process, for the most part. I appreciate any help that anyone is willing to offer.
acesavant00 said:
Is it safe for me to use WinDroid Toolkit for the process? Just need a guide for the process, for the most part. I appreciate any help that anyone is willing to offer.
Click to expand...
Click to collapse
Go to http://htcdev.com and make an account, then follow the steps and unlock your bootloader from there. After that you fastboot flash TWRP using ADB, and then use TWRP to flash a root solution. I prefer Magisk.
Alright, just unlocked the bootloader, going through the process of setting up my phone once again. Do you have a link to the Magisk & TWRP programs that I can use? Also, should I put the TWRP file in the same folder as the fastboot files?
I greatly appreciate the assistance you've given me so far, I'm deeply grateful man.
Okay, so I flashed twrp, then the seSuperuser zip that was linked to in CaptainThrowback's thread. Now my phone is stuck in a bootloop, it won't go past the HTC logo with the red warning letters. What do I do now?
acesavant00 said:
Okay, so I flashed twrp, then the seSuperuser zip that was linked to in CaptainThrowback's thread. Now my phone is stuck in a bootloop, it won't go past the HTC logo with the red warning letters. What do I do now?
Click to expand...
Click to collapse
try this step by step.. :good:
1.Flash TWRP 3.0.3-8 via Fastboot.. Do not reboot into system, enter into recovery..
2.Do a factory Reset via TWRP.. Do not reboot into system
3.Now flash SuperSU 2.79 SR3.. Reboot into system..
couple of bootloops are common, do not give up for at least 3 bootloops..
It will take a long time to boot as you have done a factory reset..
So be patient and wait for at least half hour..
acesavant00 said:
Okay, so I flashed twrp, then the seSuperuser zip that was linked to in CaptainThrowback's thread. Now my phone is stuck in a bootloop, it won't go past the HTC logo with the red warning letters. What do I do now?
Click to expand...
Click to collapse
Sorry about this - I updated the TWRP thread with the current/preferred root method: MagiskSU.
You need to flash a stock boot.img and then flash the Magisk zip from the linked thread.
Captain_Throwback said:
Sorry about this - I updated the TWRP thread with the current/preferred root method: MagiskSU.
You need to flash a stock boot.img and then flash the Magisk zip from the linked thread.
Click to expand...
Click to collapse
Aw crap, I wish I would have seen this yesterday. I tried to format data & flash one of the stock rooted roms for marshmallow roms for my sprint one a9... now it just hangs at the HTC One logo. I'm gonna assume that I'm screwed until a stock rooted Nougat rom is released for sprint.
acesavant00 said:
Aw crap, I wish I would have seen this yesterday. I tried to format data & flash one of the stock rooted roms for marshmallow roms for my sprint one a9... now it just hangs at the HTC One logo. I'm gonna assume that I'm screwed until a stock rooted Nougat rom is released for sprint.
Click to expand...
Click to collapse
Can't you just flash the Nougat RUU?
Captain_Throwback said:
Can't you just flash the Nougat RUU?
Click to expand...
Click to collapse
I found the post about the Nougat RUU, but the program won't recognize my phone cause it won't boot. I'm gonna try & flash the firmware through TWRP.
acesavant00 said:
I found the post about the Nougat RUU, but the program won't recognize my phone cause it won't boot. I'm gonna try & flash the firmware through TWRP.
Click to expand...
Click to collapse
You don't flash firmware with TWRP. But you can use the SD card method to flash the RUU, which doesn't require a computer.
Captain_Throwback said:
You don't flash firmware with TWRP. But you can use the SD card method to flash the RUU, which doesn't require a computer.
Click to expand...
Click to collapse
Sorry to bother you again, but you wouldn't happen to know a method of extracting the rom.zip from the exe file, would you?
acesavant00 said:
Sorry to bother you again, but you wouldn't happen to know a method of extracting the rom.zip from the exe file, would you?
Click to expand...
Click to collapse
[TOOL][LINUX|WIN|MAC][64bit][29-SEP-2016]Universal HTC RUU/ROM Decryption Tool 3.1.0
Run the tool with the -z flag to output a zip to the "OUT" folder.
Captain_Throwback said:
[TOOL][LINUX|WIN|MAC][64bit][29-SEP-2016]Universal HTC RUU/ROM Decryption Tool 3.1.0
Run the tool with the -z flag to output a zip to the "OUT" folder.
Click to expand...
Click to collapse
Thank you so much, man. The zip is prepped, just gotta charge my phone again to 30%. But afterwards, will I have to go through the unlock bootloader process? If I do, I don't wanna mess up on the rooting process.
acesavant00 said:
Thank you so much, man. The zip is prepped, just gotta charge my phone again to 30%. But afterwards, will I have to go through the unlock bootloader process? If I do, I don't wanna mess up on the rooting process.
Click to expand...
Click to collapse
Your bootloader will stay unlocked.
Captain_Throwback said:
Your bootloader will stay unlocked.
Click to expand...
Click to collapse
Awesome, I appreciate all of the help, man. Sorry again if I annoyed you with all of my incessant questions. Just didn't wanna mess up my phone even further.
Hello Guys,
I Have an HTC one a9 with 7.0, s-off, bootloader locked
I have some concerns before I root my phone
If I unlock the bootloader and root the phone, Will I have the option of phone encryption as it used to be ?
If I unlock the bootloader with HTCDev and flash the TWRP with SuperSu and boot file, it is a MUST to do a data factory reset? or I`m able to do all the process without loosing my data?
Thank you in advance
rilley said:
Hello Guys,
I Have an HTC one a9 with 7.0, s-off, bootloader locked
I have some concerns before I root my phone
If I unlock the bootloader and root the phone, Will I have the option of phone encryption as it used to be ?
If I unlock the bootloader with HTCDev and flash the TWRP with SuperSu and boot file, it is a MUST to do a data factory reset? or I`m able to do all the process without loosing my data?
Thank you in advance
Click to expand...
Click to collapse
Unlocking your bootloader will wipe the device.
Hi all, I've been lurking and reading for 2 months, preparing to root my device. So this title fits my mood.
One A9, "factory unlocked version", S-on, running 1.57.617.60
Just did the actual unlock from htcdev so now data is erased. I'm re-reading the threads I saved to prepare, now that it's time to actually finalize what ROM I want to run, but now have a few questions before completing the plunge.
In past threads I read the newer MM and N security prevented rooting, and reverting to Lollipop was necessary. From what I read here that is no longer the case?
If I want to debloat the system I am already running, can I do that without finding a custom ROM to run?
Thank you
sandreas said:
Hi all, I've been lurking and reading for 2 months, preparing to root my device. So this title fits my mood.
One A9, "factory unlocked version", S-on, running 1.57.617.60
Just did the actual unlock from htcdev so now data is erased. I'm re-reading the threads I saved to prepare, now that it's time to actually finalize what ROM I want to run, but now have a few questions before completing the plunge.
In past threads I read the newer MM and N security prevented rooting, and reverting to Lollipop was necessary. From what I read here that is no longer the case?
If I want to debloat the system I am already running, can I do that without finding a custom ROM to run?
Thank you
Click to expand...
Click to collapse
+1 I`m interested on this question, I have Nougat installed
sandreas said:
Hi all, I've been lurking and reading for 2 months, preparing to root my device. So this title fits my mood.
One A9, "factory unlocked version", S-on, running 1.57.617.60
Just did the actual unlock from htcdev so now data is erased. I'm re-reading the threads I saved to prepare, now that it's time to actually finalize what ROM I want to run, but now have a few questions before completing the plunge.
In past threads I read the newer MM and N security prevented rooting, and reverting to Lollipop was necessary. From what I read here that is no longer the case?
If I want to debloat the system I am already running, can I do that without finding a custom ROM to run?
Thank you
Click to expand...
Click to collapse
rilley said:
+1 I`m interested on this question, I have Nougat installed
Click to expand...
Click to collapse
Yes, you can root and debloat Nougat. Though you should make a stock system image backup first of you ever want to receive an OTA again. The TWRP thread FAQ has a lot of information about this.

Some Android newbie questions

Will be an apple to android convert when my zenfone comes. Been reading around to educate myself but have some questions that could use some insight.
1. Once you unlock the bootloader and root your phone, can you still get monthly/yearly or new android version updates in system updates in settings and update from there? If not, do you have to pretty much reset everything to factory defaults and then update it like that? And root all over again? Or is there any other way?
2. Will the phone be pretty much be "stock" after the factory reset?Working OTA updates and all? (Minus the unlocked bootloader)
3 Which up to date rooting method seems best? There's 2 methods that I can see but I can't tell which one is better.
a) https://forum.xda-developers.com/ze...uide-how-to-root-asus-zenfone-6-twrp-t3940168
b) https://forum.xda-developers.com/zenfone-6-2019/how-to/simple-guide-to-root-device-twrp-t3956784
4. Is TWRP needed?
Thanks!
midnight3ow said:
Will be an apple to android convert when my zenfone comes. Been reading around to educate myself but have some questions that could use some insight.
1. Once you unlock the bootloader and root your phone, can you still get monthly/yearly or new android version updates in system updates in settings and update from there? If not, do you have to pretty much reset everything to factory defaults and then update it like that? And root all over again? Or is there any other way?
2. Will the phone be pretty much be "stock" after the factory reset?Working OTA updates and all? (Minus the unlocked bootloader)
3 Which up to date rooting method seems best? There's 2 methods that I can see but I can't tell which one is better.
a) https://forum.xda-developers.com/ze...uide-how-to-root-asus-zenfone-6-twrp-t3940168
b) https://forum.xda-developers.com/zenfone-6-2019/how-to/simple-guide-to-root-device-twrp-t3956784
4. Is TWRP needed?
Thanks!
Click to expand...
Click to collapse
1) No, once unlocked, no more OTAS. You can flash the update manually, no wipe needed, but you also need to flash Root and custom recovery again (2 minutes extra, no big deal).
2) Stock, no OTAS
3) They are pretty much the same, but the easiest (and safest) way is just to get a custom recovery and then flash the Magisk Zip
4) For normal method yes, for the ones you posted in 3), no.
papete said:
1) No, once unlocked, no more OTAS. You can flash the update manually, no wipe needed, but you also need to flash Root and custom recovery again (2 minutes extra, no big deal).
2) Stock, no OTAS
3) They are pretty much the same, but the easiest (and safest) way is just to get a custom recovery and then flash the Magisk Zip
4) For normal method yes, for the ones you posted in 3), no.
Click to expand...
Click to collapse
Thank you for your reply, but I need some clarification on a couple things.
1. I suppose I'll figure out once I get the phone but I'm anxious and don't know when the phone will arrive but how do you flash the update manually? I understand having to flashing root again but what do you mean flashing custom recovery again?
2. Where do you get a hold of the update for the phone? Is updating manually pretty much the same as resetting your phone to factory settings?
3. I can't seem to find the method you mention that is the easiest and safest way to root. Could you kindly lead me to that guide??
midnight3ow said:
Thank you for your reply, but I need some clarification on a couple things.
1. I suppose I'll figure out once I get the phone but I'm anxious and don't know when the phone will arrive but how do you flash the update manually? I understand having to flashing root again but what do you mean flashing custom recovery again?
2. Where do you get a hold of the update for the phone? Is updating manually pretty much the same as resetting your phone to factory settings?
3. I can't seem to find the method you mention that is the easiest and safest way to root. Could you kindly lead me to that guide??
Click to expand...
Click to collapse
1) To flash manually you download the firmware from the Asus site, and use a recovery (stock or custom) to flash it. If you want root, you need a custom recovery to flash it, as stock recovery only flashes Asus Firmware. Whenever you flash a stock firmware, it "overwrites" the custom recovery with the stock recovery, so if you want/need a custom recovery, you need to flash it again. The same with root, stock flashed boot partition again, so you need to flash Magisk zip again so it can make the patch to boot to make root work.
2) I personally don't update that much, but you can check every once in a while https://www.asus.com/Phone/ZenFone-6-ZS630KL/HelpDesk_Download/
You can update without factory reset, just flash the new firmware (+root if needed) and you are done, it is just like an OTA but done by yourself.
3) Follow this: https://forum.xda-developers.com/ze...covery-unofficial-twrp-recovery-asus-t3937844
papete said:
1) To flash manually you download the firmware from the Asus site, and use a recovery (stock or custom) to flash it. If you want root, you need a custom recovery to flash it, as stock recovery only flashes Asus Firmware. Whenever you flash a stock firmware, it "overwrites" the custom recovery with the stock recovery, so if you want/need a custom recovery, you need to flash it again. The same with root, stock flashed boot partition again, so you need to flash Magisk zip again so it can make the patch to boot to make root work.
2) I personally don't update that much, but you can check every once in a while https://www.asus.com/Phone/ZenFone-6-ZS630KL/HelpDesk_Download/
You can update without factory reset, just flash the new firmware (+root if needed) and you are done, it is just like an OTA but done by yourself.
3) Follow this: https://forum.xda-developers.com/ze...covery-unofficial-twrp-recovery-asus-t3937844
Click to expand...
Click to collapse
I'm grateful for all your thoughtful and clear responses.
When do you normally decide to update?
Do you lose any data from updating security update/firmware or rooting and installing custom recovery?
Also, I've been looking through that link you posted, and also seen another thread about another newer "official" TWRP version? What's the difference?Which one should I use?
https://forum.xda-developers.com/ze...nt/tool-utility-twrp-3-3-1-0-teamwin-t3963876
midnight3ow said:
Will be an apple to android convert when my zenfone comes.
Click to expand...
Click to collapse
So ZF6 will be your first Android phone ever?
_jis_ said:
So ZF6 will be your first Android phone ever?
Click to expand...
Click to collapse
Yes it will be! Excited and anxious at the same time.
midnight3ow said:
Yes it will be! Excited and anxious at the same time.
Click to expand...
Click to collapse
Then please do yourself a favor and forgot about unlocking the bootloader and rooting your new phone.
Just learn how to use nearly stock Android with lightweight Android skin in its user-friendly and widely configurable form called ZenUI.
Trust me, there is no need for tinkering with root as an Android newbie when using ZF6.
_jis_ said:
Then please do yourself a favor and forgot about unlocking the bootloader and rooting your new phone.
Just learn how to use nearly stock Android with lightweight Android skin in its user-friendly and widely configurable form called ZenUI.
Trust me, there is no need for tinkering with root as an Android newbie when using ZF6.
Click to expand...
Click to collapse
I agree with this, unless you want to achieve something specific that can only be done rooted, stay completely stock.
papete said:
unless you want to achieve something specific that can only be done rooted
Click to expand...
Click to collapse
But this hypothetical condition is impossible because Android newbie cannot even achieve basic Android tasks which doesn't require root at all so why complicate his upcoming long journey of gaining experience and knowledge yet by the rooting his device from the very beginning?

Categories

Resources