Database Develop

Asking for your input on whether I should root

Hi all,
I am supposed to receive my nexus 7 tomorrow.
I just cant decide on whether I should root or no.
I can say for sure that I do not plan to change roms, I only want to root in order to use storage via usb-otg (also not sure I will use it eventually).
I do know that I want to receive OTA updates and that's why I don't like the idea of rooting.
Any suggestions?
Thanks a lot!
Asaf

Yes you should root it if you want to use usb-otg. I decided not to root mine on day one and now I'm looking for a method that won't erase everthing on my device. So if you see yourself needing that in the future do it now rather than later .

shemsha said:
Hi all,
I am supposed to receive my nexus 7 tomorrow.
I just cant decide on whether I should root or no.
I can say for sure that I do not plan to change roms, I only want to root in order to use storage via usb-otg (also not sure I will use it eventually).
I do know that I want to receive OTA updates and that's why I don't like the idea of rooting.
Any suggestions?
Thanks a lot!
Asaf
Click to expand...
Click to collapse
This is a Nexus device which makes to easy to root and unroot..
If an OTA comes out you can be unrooted and back stock in a matter of minutes..
Oddly, I have had no reason or desire to root my N7 and I even put my GNex back stock...

If you do root, do it before you install all kinds of stuff. You have to reset to root. Not sure how the Google credit works, but you might want to register the device, get the credit, then root. Just in case.
Sent from my Nexus 7 using Tapatalk 2

I was reluctant to root or not. CM10 is only a preview, other roms not much better than stock, I don't need OTG, so why root? For one crucial app: TITANIUM BACKUP. When you unlock and root everything is wiped!

My suggestion is unlock the bootloader right away since that part wipes data, then root when (and if) you decide to download an app that needs root access.

Easier to Root now rather than later. Rooting requires you to wipe losing all apps and settings.
Sent from my Nexus 7 using Tapatalk 2

Yes. First thing I always do on a Nexus device is unlock and root. It's just as easy to lock it again and flash the stock rom if ever needed.

I would unlock the bootloader at a minimum, before you set anything up, as that action will wipe data. If you decide to root later on you'll be in great shape.
Sent from my ADR6400L using Tapatalk 2

Might be better to wait and see if any problems arise with the device first?

I rooted mine using the One click root tool, very easy.
Got to be worth it to install ad block and sixaxis.

Like others have said, at the very minimum, unlock the bootloader (a prerequisite for rooting) right away. If you decide to unlock it later you'll have to wipe the device.

Absolutely. Just make sure you bookmark (in the cloud) how to unroot before you root (including restoring stock bootloader). It would also be smart to read what issues other folks have had, and what they did to solve their problems. (In short, always have a concrete, detailed exit plan before you start something.)
Sent from my ThinkPad Tablet using Tapatalk 2

shaneydroid said:
Might be better to wait and see if any problems arise with the device first?
Click to expand...
Click to collapse
That is an excellent point I am very anzy ( think I killed that word) to unlock and root but I want to give it atleast a week to make sure there are no kinks, dead pixels or anything that would require me to return it but so far so good on my first day. I bought Titu with the $25 credit forgetting that it requires root lol but it's all good becuase now I have it for my Vivid but to use six axis you need root as well.

shaneydroid said:
Might be better to wait and see if any problems arise with the device first?
Click to expand...
Click to collapse
clago87 said:
That is an excellent point I anzy ( think I killed that word) to unlock and root but I want to give it atleast a week to make sure there are no kinks, dead pixels or anything that would require me to return it but so far so good on my first day. I bought Titu with the $25 credit forgetting that it requires root lol but it's all good becuase now I have it for my Vivid but to use six axis you need root as well.
Click to expand...
Click to collapse
Other than checking out the basic functions, I wouldn't bother waiting. The device is designed to be unlocked so it is not a hardware warranty issue and that is what you would be returning the device for. If you plan on having root, you need root to test the things you will be using it for.
Plus, it then allows you to back up the device so that if you do have to get another one, it is a very simple process to restore your backup and be back up and running (one of the primary reasons for root)

krelvinaz said:
Other than checking out the basic functions, I wouldn't bother waiting. The device is designed to be unlocked so it is not a hardware warranty issue and that is what you would be returning the device for. If you plan on having root, you need root to test the things you will be using it for.
Plus, it then allows you to back up the device so that if you do have to get another one, it is a very simple process to restore your backup and be back up and running (one of the primary reasons for root)
Click to expand...
Click to collapse
I am actually glad to be at work for once. I am very easily swayed and am ready to unlock and root lol. I have read all the info on it and it does not seem too much of a burden compared to my atrix

I'm kind of confused, do I unlocked the bootlocker first or install 4.1.1 updates?
If I install then unlock, would the updates be gone?
Would I be able to update even after unlock and root?

i rooted even though i had already installed apps etc... its very handy to be able to use external storage and apps like titanium backup.. i dont really intend installing customs roms.. but the otg support was enough to warrant rooting for me

You can backup and restore your device with ADB. Backup, unlock, restore. You don't have to lose everything to root it later on.

hydroxyde said:
You can backup and restore your device with ADB. Backup, unlock, restore. You don't have to lose everything to root it later on.
Click to expand...
Click to collapse
Yep was just about to say this, picked this method up in the OneX forums, life saver
Sent from my Nexus 7 using xda premium

[Q] Boot Issues

Ever since I've rooted my Moto G 2nd Gen (Consumer Cellular) with Kingroot it has been starting to take a full 5-7 minutes just to boot up. The weird part of it is that the device reboots itself automatically 3 times just to finally boot to the OS. I have no clue of what's going on at the moment, but this is an incredibly irritating issue. Any thoughts? Any help will obviously be appreciated.

Who did you tell to use some rooting tool like Kingroot or whatever?
To root your Moto G you have to unlock your bootloader on Motorola page,flash or boot into custom recovery (TWRP) and then flash latest super SU from there.
Or after unlocking use chainfires autoroot.
All this you can read here:
http://forum.xda-developers.com/moto-g-2014/general/xt1063-t3018818
http://forum.xda-developers.com/moto-g-2014/general/guide-root-moto-g-2014-flash-custom-t2955243
Never use some rooting tool when it´s not recommended...

Wolfcity said:
Who did you tell to use some rooting tool like Kingroot or whatever?
To root your Moto G you have to unlock your bootloader on Motorola page,flash or boot into custom recovery (TWRP) and then flash latest super SU from there.
Or after unlocking use chainfires autoroot.
All this you can read here:
http://forum.xda-developers.com/moto-g-2014/general/xt1063-t3018818
http://forum.xda-developers.com/moto-g-2014/general/guide-root-moto-g-2014-flash-custom-t2955243
Never use some rooting tool when it´s not recommended...
Click to expand...
Click to collapse
Thanks.

I have the same problem anyone know what causes this long boot time? The kingroot works great in every other way and no need for unlocking boot loader or even the need for a pc making it a very easy option. Any experience of this root method from anyone here?

xs1m0nx said:
I have the same problem anyone know what causes this long boot time? The kingroot works great in every other way and no need for unlocking boot loader or even the need for a pc making it a very easy option. Any experience of this root method from anyone here?
Click to expand...
Click to collapse
That's an awful way to root and frankly almost if not impossible to do. This phone needs to be unlocked to root and anything other than that way is bound to fail.

Well that's not the case it does not fail it works great with just a small issue of longer boot time. Far from being an awful way it's actually a brilliant way as it makes it so easy for people with minimum fuss. What I'm really looking for is some constructive information from someone who has good knowledge of this root method. The boot time is not really a big deal I'm just interested to know why it does this.

xs1m0nx said:
Well that's not the case it does not fail it works great with just a small issue of longer boot time. Far from being an awful way it's actually a brilliant way as it makes it so easy for people with minimum fuss. What I'm really looking for is some constructive information from someone who has good knowledge of this root method. The boot time is not really a big deal I'm just interested to know why it does this.
Click to expand...
Click to collapse
Well have at it. It's obviously a poor choice as you'll eventually discover. Some people just look for ways to fail.

I think it's more people look for new ways and that's not a bad thing. Everything moves on and what was not possible to do becomes possible. Yes it maybe true that there can be problems but there are few that can't be overcome. Every method was unknown and risky as some point but that's just how it will always be. You got to admit kingroot have done what everyone said was impossible so that's pretty clever of them. Hopefully someone a lot more clever than me will work out about the little side effect in time.

Update: Tel864 is quite right although this does root your phone it causes problems with boot that just get worse over time. I've flashed stock back on mine I'll probably re root but with the recommended method so yes I retract all the above!

What scares me about Kingroot is the fact that it's just a collection of exploits that forces changes to the bootloader. It sort of goes against the very thing that makes Android safer.
Sent from my GT-P5210 using Tapatalk

Yes your right and I imagine eventually may brick the phone. I have rooted the proper way now and installed a custom ROM so ended up with a much better situation.
Sent from my Moto G 2014 using Tapatalk

I just bought the Nexus 6, should I root it immediately?

Hi, long time lurker here. I want to start by saying how great and informative this site is. Anyway, my nexus 6 came in from the mail like 5 hours ago, did all the updates from 5.0 to 6.0 and it's now running Marshmallow mra58n. Question is should I root it immediately and if so, are there any guides I can follow? Much love to you all, I'm not exactly pro at this kind of things but I can follow instructions since I have competently rooted my past phones which were an HTC M7, M8 and a Samsung Galaxy Note 10.1 tablet.
Thank you.
Edit: Phone is also unlocked, I currently have no SIM card

start here..
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481

At the least unlock the bootloader right away. Doing so will completely wipe the phone so it's the first thing I do.
Sent from my Nexus 6 using Tapatalk

razortaz18 said:
At the least unlock the bootloader right away. Doing so will completely wipe the phone so it's the first thing I do.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I've been looking at the Nexus Root Toolkit since I am kind of confused on how to proceed with anything at all, is that ill advised since I've read that there are problems with the USB cable disconnecting during reboot?
Also, thank you for the reply.

I used the NRT without issue. Just follow the guide step by step.
Sent from my Nexus 6 using Tapatalk

and, dont touch the usb cable while the phone is processing your commands!
j/k, never even heard of the USB cable "problem"

I just used the toolkit today to unlock and root my N6.
Sent from my Nexus 6 using Tapatalk

I rooted last night initially using manual method described in the first link provided, however after some driver issues ultimately used the 2.1.0 rootkit to uninstall and reinstall all drivers. That too alone saved me tons of time and either method is simple if you can follow instructions.
Totally recommend rooting and then experimenting with custom roms, its like getting a new phone everyone you install a new rom.
Have fun!

Kristine,
In answer specifically to your question "Should I...?" my answer is "No". It really depends on what you think you'll get from it - why do you want to do it? What specific benefits do you want?
The reason that I say "no" is that I've been rooted on all my several phones for years, and I've decided that for me the annoyance of having to manually flash ROMs outweighs the benefits - particularly now that Google are releasing frequent security updates. The moment you root your device the OTA (over the air) updates no longer work.
For me the major reason for rooting was to have a firewall. The other things (wakelock detection, double tap to wake, auto-hibernation...) were great but not showstoppers. Now that there is a non-root firewall (Netguard) I'm happy to leave my phone unrooted. I haven't had an OTA to apply yet, so if I have any problems then I might change my mind, but my advice would be to think hard about why you want root before you buy yourself into a world of tinkering...

razortaz18 said:
At the least unlock the bootloader right away. Doing so will completely wipe the phone so it's the first thing I do.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Dammit, are you kidding me? I just downloaded and setup everything, figured I'd do all everything else tomorrow... Oh, well I can do it again I suppose.

Kristine-N said:
Question is should I root it immediately....
Click to expand...
Click to collapse
Because I don't want a white interface, rooting is necessary. Google forces to many things, like forced encryption, useless apps and a white interface (battery drain). When rooting was impossible I would not have bought a Nexus.

Short answer: No!
Long answer: Well, it's sill no, but you can or even should do a couple of things.
First if all, allow OEM Unlocking in development settings. There are gazillion how-tos to switch developer mode on, and tick that switch. Google has borked OTAs already, and if your phone doesn't boot, and the switch is off, then you're boned, you can send it for repair. But if you can unlock you bootloader, then you can flash a custom recovery and make your phone working again.
Second, if you do plan to root your phone in the near future, you should unlock the bootloader now, while it's still new, because it will erase everything (IMHO this would be sufficient as a security measure, the Enable OEM Unlocking is overkill).
As for the main question if you don't have any specific ideas what you want the root for, then don't root your phone. It's a clear and present security risk, and you're just one too many "Allow" taps from letting someone acquire your passwords, clone your IMEI, and download your personal stuff. My motto is, if you don't know what exactly root is, what it does, then you don't know how to prevent exploits that need it to run.
Also if you modify your phone in any way, and that includes rooting, you won't receive the monthly OTAs, and will have to flash it manually.
And finally, don't use toolkits on a Nexus. Spend another hour reading about the matter and you will find out typing adb and fastboot commands is a easy as clicking buttons on toolkits. There is nothing extra in them, they just download the images to flash, and "type" these commands for you.

Unlock bootloader and don't root it for now. After some time, if you feel like you're missing some features that you can obtain only with root, then go ahead. But for now I would strongly recommend to stay stock and see how it goes...

Vulnerability to open S5 (Verizon) bootloader released

the guy who unlocked the bootloader on Verizon's s5 variant has released a document detailing what I believe is the procedure. Could this open the door for ATT's variant to be unlocked?
https://twitter.com/firewaterdevs/status/713906161834192896
http://theroot.ninja/disclosures/SAMDUNK_1.0-03262016.pdf

sensei22 said:
the guy who unlocked the bootloader on Verizon's s5 variant has released a document detailing what I believe is the procedure. Could this open the door for ATT's variant to be unlocked?
https://twitter.com/firewaterdevs/status/713906161834192896
http://theroot.ninja/disclosures/SAMDUNK_1.0-03262016.pdf
Click to expand...
Click to collapse
Possibly, based on what I read from it though it needs the string from the dev-edition device, they have that with the Verizon version so it's easy to get, we only have the one, so I think(speculation) it would be trivial at best to repeat this in our model since we don't even know what to set the CID to to make it reflect that of the 'dev edition', I don't think we're getting a towelroot from this at least[emoji14]
Sent from my SAMSUNG-SM-G900A using Tapatalk

I'm going to take a guess that the Verizon and AT&T phones are both unlockable via the same method. I don't even know how to run Samdunk.. Phone or PC? (Can't be Phone if we have no root access :/)

this really seems promising, i still love my s5 and would like to have the bootloader unlocked at some point.

I wouldn't get your hopes up. That unlock requires root which means anyone on 5.0 or above already is SOL, even IF that method worked on AT&T.

You cant root 5.1.1 on atnt because root modifys the system partition.You can still gain hardware access if theres an exploit you just cant modify the system partition(or the device wont turn on again after a full power-down) because it is checksumed on every boot. (and you cant remove this because it is in the kernel that is signature checked on every boot(and the user and system partitions aren't mounted yet so you cant run a hack to get around it))
This does not mess with the system partition so you could run a kernel exploit and this right after with out rooting.
For the cid use the tmobile s5 cid it is bootloader unlocked right from the store and has the same hardware(gsm modem).
Although my atnt device has 11 toshiba memory and all atnt devices might.

Guicrith said:
You cant root 5.1.1 on atnt because root modifys the system partition.You can still gain hardware access if theres an exploit you just cant modify the system partition(or the device wont turn on again after a full power-down) because it is checksumed on every boot. (and you cant remove this because it is in the kernel that is signature checked on every boot(and the user and system partitions aren't mounted yet so you cant run a hack to get around it))
This does not mess with the system partition so you could run a kernel exploit and this right after with out rooting.
For the cid use the tmobile s5 cid it is bootloader unlocked right from the store and has the same hardware(gsm modem).
Although my atnt device has 11 toshiba memory and all atnt devices might.
Click to expand...
Click to collapse
My att s5 has 15 for the first 2 digits of the Cid.

Guicrith said:
You cant root 5.1.1 on atnt because root modifys the system partition.You can still gain hardware access if theres an exploit you just cant modify the system partition(or the device wont turn on again after a full power-down) because it is checksumed on every boot. (and you cant remove this because it is in the kernel that is signature checked on every boot(and the user and system partitions aren't mounted yet so you cant run a hack to get around it))
This does not mess with the system partition so you could run a kernel exploit and this right after with out rooting.
For the cid use the tmobile s5 cid it is bootloader unlocked right from the store and has the same hardware(gsm modem).
Although my atnt device has 11 toshiba memory and all atnt devices might.
Click to expand...
Click to collapse
Mine is 15, I may be willing to be the guinea pig for this as long as it's not a 100% brick. I'm not entirely sure about the tmo s5 simply having the same hardware will make it work, if something like that was the case why did Verizon folks have to wait for someone with the dev Verizon s5 to upload their aboot?
Sent from my SAMSUNG-SM-G900A using Tapatalk

Anyone here willing to risk bricking their device with a 15 series chip pm me!

I saw on a thread maybe the Verizon s5 bootloader unlocking thread a post about copying your original boot chain to an SD card so incase you brick you can still boot the original boot chain off of your SD. Apparently your SD has to be class 10. Just more food for thought.

How do I check my cid? I'm tempted to test as I have the S7 now. But if this works, I may very well return the S7 due to locked bootloader.

TehPirate_ said:
How do I check my cid? I'm tempted to test as I have the S7 now. But if this works, I may very well return the S7 due to locked bootloader.
Click to expand...
Click to collapse
Brickbug emmc from play store. Still not clear if we can make it work, it should and can, but I think we're missing the att 'dev edition'(maybe factory has it with this?) aboot as just using the Verizon one doesn't seem to work.
Sent from my SAMSUNG-SM-G900A using Tapatalk

Rakuu said:
Brickbug emmc from play store. Still not clear if we can make it work, it should and can, but I think we're missing the att 'dev edition'(maybe factory has it with this?) aboot as just using the Verizon one doesn't seem to work.
Sent from my SAMSUNG-SM-G900A using Tapatalk
Click to expand...
Click to collapse
Shame, mines Toshiba (11)

I just want to let everyone know that I've been involved with the thread over at Verizon and guinea pigged for us. I do have an active, however that shouldn't matter. At the moment, you can run both methods and it will appear to be successful, even changing the Cid, but it doesn't unlock the bootloader.
So for now, we're out of luck.

N4styN1ghtm4r3 said:
I just want to let everyone know that I've been involved with the thread over at Verizon and guinea pigged for us. I do have an active, however that shouldn't matter. At the moment, you can run both methods and it will appear to be successful, even changing the Cid, but it doesn't unlock the bootloader.
So for now, we're out of luck.
Click to expand...
Click to collapse
Damn, I was hoping this would pan out as I have a CID that starts with 15. Checked yesterday when advised in the TMS5 3.0 thread. I got this s5 from Samsung insights so I was hoping that'd help but it's At&t branded with locked bootloader. Waiting patiently for an option to unlock bootloader as I don't plan to get a new phone anytime soon.
~TMS5-3.0-TMBUILD on G900A with Blue Ice Theme

joshua14 said:
Damn, I was hoping this would pan out as I have a CID that starts with 15. Checked yesterday when advised in the TMS5 3.0 thread. I got this s5 from Samsung insights so I was hoping that'd help but it's At&t branded with locked bootloader. Waiting patiently for an option to unlock bootloader as I don't plan to get a new phone anytime soon.
~TMS5-3.0-TMBUILD on G900A with Blue Ice Theme
Click to expand...
Click to collapse
If you're comfortable doing this kind of stuff, then you can try without risking anything. Nobody with an original s5 has tried it, only me, but again, mine is an active. That may or may not be the reason it didn't work for me, but if somebody with an original s5 wants to try, that would give us a definitive answer.
I did both methods and everything went fine, with no errors. It simply didn't unlock. So feel free to give it a shot, you'll just have to restore your old Cid if it fails, which is no big deal. The only thing I'd give a heads up on, is both methods erase your SD card, so use a spare SD card or back up your files from it somewhere else.
Good luck if you try!!

N4styN1ghtm4r3 said:
If you're comfortable doing this kind of stuff, then you can try without risking anything. Nobody with an original s5 has tried it, only me, but again, mine is an active. That may or may not be the reason it didn't work for me, but if somebody with an original s5 wants to try, that would give us a definitive answer.
I did both methods and everything went fine, with no errors. It simply didn't unlock. So feel free to give it a shot, you'll just have to restore your old Cid if it fails, which is no big deal. The only thing I'd give a heads up on, is both methods erase your SD card, so use a spare SD card or back up your files from it somewhere else.
Good luck if you try!!
Click to expand...
Click to collapse
This will be something to try for the weekend. I have backups for both SS and FF so as long as I don't risk full bricking then I'm game. I have a few spare sd cards too. I never took any OTA updates, the first one that tried getting pushed on me while still within the 6 month insights program I rooted with TowelRoot and froze with TB. Other than that I didn't do much else until more recently to go to Muniz_ri 5.0 keeproot and then to TMS5-3.0-TMBUILD. I was hoping of convincing At&t to unlock the bootloader along with the sim unlock since they don't have any rights to this phone. I still have my Next plan s5 thru them so I can toy with this one, just don't want to end up completely bricking either. I have 2 S3 that I put full custom CM builds on for the kids to play with, just turned off root. Lol
~TMS5-3.0-TMBUILD on G900A with Blue Ice Theme

joshua14 said:
This will be something to try for the weekend. I have backups for both SS and FF so as long as I don't risk full bricking then I'm game. I have a few spare sd cards too. I never took any OTA updates, the first one that tried getting pushed on me while still within the 6 month insights program I rooted with TowelRoot and froze with TB. Other than that I didn't do much else until more recently to go to Muniz_ri 5.0 keeproot and then to TMS5-3.0-TMBUILD. I was hoping of convincing At&t to unlock the bootloader along with the sim unlock since they don't have any rights to this phone. I still have my Next plan s5 thru them so I can toy with this one, just don't want to end up completely bricking either. I have 2 S3 that I put full custom CM builds on for the kids to play with, just turned off root. Lol
~TMS5-3.0-TMBUILD on G900A with Blue Ice Theme
Click to expand...
Click to collapse
Yea like I said, as long as you follow the steps closely, there isn't a chance of bricking, it just won't unlock. Let us know when you give it a shot!

Still don't work as of yet...maybe never. The main thread on this is here:
http://forum.xda-developers.com/ver...locking-galaxys-s5-bootloader-t3337909/page77

samccfl99 said:
Still don't work as of yet...maybe never. The main thread on this is here:
http://forum.xda-developers.com/ver...locking-galaxys-s5-bootloader-t3337909/page77
Click to expand...
Click to collapse
It's likely to be never unless we get the proper CID, which as about a needle in a haystack to guess as the bootloader key.
Sent from my SAMSUNG-SM-G900A using Tapatalk

Canadian P20 Pro version CLT-L04, Questions about Magisk and bootloader unlock

Hi! I picked up my Canadian P20 Pro last week and couldn't be happier. It's been many years since I've owned a rootable device though and a lot has changed! I've done my best to read through all the guides for rooting the P20 Pro and it's only lead to further confusion as there seem to be many recent advancements. There seem to be a lot of different versions of this phone too. So I have some questions I'm hoping someone can answer easily! Let's assume my bootloader is already unlocked....
1) there's a really great guide on rooting the P20 Pro using All In One tool. But that requires flashing TWRP to achieve root using Magisk. I do not require TWRP as I only want root and do not wish to flash any roms.
a) is there a way to root with Magisk and NOT flash TWRP? I can't seem to find a straight answer on this...
b) failing that, can TWRP safely be removed and keep root afterward?
2) after unlocking the bootloader I was welcomed by a terrifyingly orange warning about my now 'unsafe' phone. I've read mixed things on hiding this. Is there currently a way to hide it?
3) how does the process work for OTA updates on an unlocked bootloader assuming there is no TWRP? I've read differing opinions on the necessity of flashing a no_check.img to the ramdisk and have no understanding of the new security checks on these phones. Can I run risk of bricking my phone through an automated update?
Ultimately I'm scared of forgetting TWRP is on my phone and accepting an update that'll brick it. Any information is welcome as are similar questions!

I am also curious if there is a good root process for this phone. Find anything yet?

djparent said:
Hi! I picked up my Canadian P20 Pro last week and couldn't be happier. It's been many years since I've owned a rootable device though and a lot has changed! I've done my best to read through all the guides for rooting the P20 Pro and it's only lead to further confusion as there seem to be many recent advancements. There seem to be a lot of different versions of this phone too. So I have some questions I'm hoping someone can answer easily! Let's assume my bootloader is already unlocked....
1) there's a really great guide on rooting the P20 Pro using All In One tool. But that requires flashing TWRP to achieve root using Magisk. I do not require TWRP as I only want root and do not wish to flash any roms.
a) is there a way to root with Magisk and NOT flash TWRP? I can't seem to find a straight answer on this...
b) failing that, can TWRP safely be removed and keep root afterward?
2) after unlocking the bootloader I was welcomed by a terrifyingly orange warning about my now 'unsafe' phone. I've read mixed things on hiding this. Is there currently a way to hide it?
3) how does the process work for OTA updates on an unlocked bootloader assuming there is no TWRP? I've read differing opinions on the necessity of flashing a no_check.img to the ramdisk and have no understanding of the new security checks on these phones. Can I run risk of bricking my phone through an automated update?
Ultimately I'm scared of forgetting TWRP is on my phone and accepting an update that'll brick it. Any information is welcome as are similar questions!
Click to expand...
Click to collapse
I have a Canadian CLT-L04 that i rebranded and rooted to CLT-L29 with the guide on here.
https://forum.xda-developers.com/hu...de-how-to-root-debrand-remove-retail-t3788326
if you want better firmware compared to version 109 thats still on clt-l04 you can follow this guide, it worked well for me. (don't wait canadian OTA it'll take too long)
1) quite sure that TWRP is the easiest and safest way to root. Currently unaware of a better way to root the phone.
b) if you remove TWRP by flashing a stock recovery_ramdisk, root is kept. If you do an OTA though you might lose root.
2) thats here to stay i believe. Cannot find a way to hide it currently.
3)In this guide under the "install an OTA Stock Update: PC Method" you will find all the information you need.
cheers

I finally found the info I needed in this thread:
https://forum.xda-developers.com/hu...ide-getting-started-unlock-twrp-root-t3806180
Overall it was a very simple process and took less than an hour including reading. Once you've got your bootloader unlock code the all in one tool handles it from there. Unlock the bootloader, flash TWRP, reboot into TWRP, flash Magisk and you're done. You can flash the no_check file over TWRP if you want to be ready for updates but I decided to leave TWRP on for now. Loving having root on this phone so far!

On a different note, has anyone discovered any ROMs for this phone yet that can handle the notch? I almost tried Lineage until I found out there is no notch support. I've grown strangely fond of the thing for some reason lol

rhinogator said:
I have a Canadian CLT-L04 that i rebranded and rooted to CLT-L29 with the guide on here.
https://forum.xda-developers.com/hu...de-how-to-root-debrand-remove-retail-t3788326
if you want better firmware compared to version 109 thats still on clt-l04 you can follow this guide, it worked well for me. (don't wait canadian OTA it'll take too long)
1) quite sure that TWRP is the easiest and safest way to root. Currently unaware of a better way to root the phone.
b) if you remove TWRP by flashing a stock recovery_ramdisk, root is kept. If you do an OTA though you might lose root.
2) thats here to stay i believe. Cannot find a way to hide it currently.
3)In this guide under the "install an OTA Stock Update: PC Method" you will find all the information you need.
cheers
Click to expand...
Click to collapse
Did you by any chance find a way to go back to CLT-L04 by any chance?

mrnovanova said:
Did you by any chance find a way to go back to CLT-L04 by any chance?
Click to expand...
Click to collapse
unfortunately no

mrnovanova said:
Did you by any chance find a way to go back to CLT-L04 by any chance?
Click to expand...
Click to collapse
If you do a full backup of the L04 in TWRP before rebranding you should be able to go back to it easily at any time, just remember to save it somewhere safe other than the phone itself. If you've already flashed and are looking to go back you may find someone willing to share a stock backup if you ask around. But always best to do your own backup first, then you can go back whenever you like!

djparent said:
If you do a full backup of the L04 in TWRP before rebranding you should be able to go back to it easily at any time, just remember to save it somewhere safe other than the phone itself. If you've already flashed and are looking to go back you may find someone willing to share a stock backup if you ask around. But always best to do your own backup first, then you can go back whenever you like!
Click to expand...
Click to collapse
I never thought of backing up my L04. ??? I guess I'm stuck with L29. Oh well... Thanks for the reply.

help with rebranding tutorial
mrnovanova said:
I never thought of backing up my L04. I guess I'm stuck with L29. Oh well... Thanks for the reply.
Click to expand...
Click to collapse
bro did u use the same files as the main tutorial that you share? cause I have the L04 but the mexican one, and I want to rebrand it
but i'm a noob in this things, hope you can help me.:good:

Search for dladz's tutorial.
ON THIS THREAD : https://forum.xda-developers.com/hu...to-root-debrand-remove-retail-t3788326/page46
Page 16
Sent from my Google Pixel 2 XL using XDA Labs

Anyone unlocked bootloader and rooted recently for the L04 model with 120(C792) Sept-2018 update?
Im scared to update before unlocking and rooting as the update might do something to fastboot etc. (this has happened to LG)
If not, then Ill update but if so, Ill just not update and unlock it as it is.

JF-GINO said:
Anyone unlocked bootloader and rooted recently for the L04 model with 120(C792) Sept-2018 update?
Im scared to update before unlocking and rooting as the update might do something to fastboot etc. (this has happened to LG)
If not, then Ill update but if so, Ill just not update and unlock it as it is.
Click to expand...
Click to collapse
It's really easy to update once you've unlocked, I would suggest unlocking first if you have concerns. I have an L04 as well and just updated to 120 with no problems.

djparent said:
It's really easy to update once you've unlocked, I would suggest unlocking first if you have concerns. I have an L04 as well and just updated to 120 with no problems.
Click to expand...
Click to collapse
Hey, Thanks djparent, I unlocked and updated as you suggested.
Everything working properly, just need to root/twrp etc. now.
Thnaks again

No problem, glad it worked for you. I've soft bricked and recovered my phone a few times now experimenting so if you run into any problems I'm happy to help! Lots to learn with the P20.

I have a CLT-L04 8.1.0.136 C69 with October security patch from Mexico I want to rebrand it to CLT- L29 to get wifi calling and get rid of all the bloatware. Could I use this tutorial from dladz's tutorial:
ON THIS THREAD : https://forum.xda-developers.com/hua...3788326/page46
Page 16
One of the notes mentions the following: I) ]NOTE*** If you are on a later firmware than 120, please do not attempt this guide!!
I have only rooted one phone before in my life so I am no expert. I do no want to mess up my phone becuse it is the only one that I have. Also If I unlock the boot loader and rebrand can i get OTAs and the upcoming Pie release? Thanks for the help!

LineageOS 15.1 on L04
I installed LineageOS 15.1 on my L04 with out any issue. Some things to consider. USB-C will only charge the device, Titanium Backup will install but doesn't get root access and you'll miss the camera application.

Vedrick said:
I installed LineageOS 15.1 on my L04 with out any issue. Some things to consider. USB-C will only charge the device, Titanium Backup will install but doesn't get root access and you'll miss the camera application.
Click to expand...
Click to collapse
Did you install it with a locked bootloader ? I really dont feel like paying for an unlock code. Would like to try Lineage though.

matever said:
Did you install it with a locked bootloader ? I really dont feel like paying for an unlock code. Would like to try Lineage though.
Click to expand...
Click to collapse
I do have an unlocked bootloader. Truth is i'm addicted to Rom's lol. That in mind I have tried every Rom, kernel, flash-able zip within this Forum and I can't brick this thing. L04 Canadian. Lineage is the best Rom for our device.
Roms that work:
- Lineage - Hauwei camera can be installed and works, dark mode works well.
------- Doesn't work: USB-C audio, NFC, RAW Option in the camera, Second ear piece as speaker, main speaker works well.
- First Ever Android 9 - Being the first build it works well. (Note: When I installed this rom I never installed the RemoveEncryption-P20Pro.zip) Seemed to work just fine without it. I did run it just because I wanted to see if it would brick my phone. It didn't.
-------Doesn't work: Dark mode, NFC, RAW Option in camera, Second ear piece as speaker, main speaker works well, seems to kill TWRP. eRecovery needed to get TWRP to function.
- AOSP 9 - Berkeley-Flex - Do Not Use...not ready.

Vedrick said:
I do have an unlocked bootloader. Truth is i'm addicted to Rom's lol. That in mind I have tried every Rom, kernel, flash-able zip within this Forum and I can't brick this thing. L04 Canadian. Lineage is the best Rom for our device.
Roms that work:
- Lineage - Hauwei camera can be installed and works, dark mode works well.
------- Doesn't work: USB-C audio, NFC, RAW Option in the camera, Second ear piece as speaker, main speaker works well.
- First Ever Android 9 - Being the first build it works well. (Note: When I installed this rom I never installed the RemoveEncryption-P20Pro.zip) Seemed to work just fine without it. I did run it just because I wanted to see if it would brick my phone. It didn't.
-------Doesn't work: Dark mode, NFC, RAW Option in camera, Second ear piece as speaker, main speaker works well, seems to kill TWRP. eRecovery needed to get TWRP to function.
- AOSP 9 - Berkeley-Flex - Do Not Use...not ready.
Click to expand...
Click to collapse
What did you use to unlock your bootloader ? Funky ? Also I know what you mean I am addicted to Roms as well :laugh: Thanks for all the info I really appreciate it.