Related
I got myself a brand new nexus S and Ive got some questions
Im debating on using a custom ROM or just go stock ICS.
A good reason why people use custom ROMs is because of better battery because of the kernel. so would it be possible to flash a better kernel on stock ICS?
If I am going with Custom,
whats the most Recommended:
way of rooting(1 click or manual, and why)
Custom recovery
best kernel
best ROM
is it possible to save a custom UI(so you could do dual booting through custom UI u made)
WoolyMarmot said:
I got myself a brand new nexus S and Ive got some questions
Im debating on using a custom ROM or just go stock ICS.
A good reason why people use custom ROMs is because of better battery because of the kernel. so would it be possible to flash a better kernel on stock ICS?
If I am going with Custom,
whats the most Recommended:
way of rooting(1 click or manual, and why)
Custom recovery
best kernel
best ROM
is it possible to save a custom UI(so you could do dual booting through custom UI u made)
Click to expand...
Click to collapse
You can flash a stock kernel on stock ICS, this is what i have done in the past and it was great. However I will note that the new ROM modifications that increase usable System RAM make a very noticeable difference with no negatives as far as i see. You also get things like notification power toggles, more lockscreen options and so on with a custom ROM.
Anyway, to answer your questions:
1) Best way of rooting: We have a Nexus device so i would not waste time using one clicks. Unlock the bootloader using fastboot, flash a custom recovery and then either flash superuser.zip or a custom ROM. This allows the most versatility when changing ROMs, mainly if you ever decide to flash or restore a stock ROM. The Nexus S allows you to lock the bootloader if you ever need to so warranty issues based on unlocked bootloaders are minimal.
2) ClockWorkMod is generally the most favorable, compatible and least buggy of the lot. TWRP, although good, has a couple of hidden bugs in it and is no longer being developed. Further, CWM now gives you the option between a Touch based recovery and a button based one. This is up to you as they're both essentially the same, but i still prefer the buttons.
3) There is no best kernel, just the best for you. Find the features you want in a kernel first, and then pick a handful and try them all. If you are using a ROM with fixes for the extra RAM (CM9, Slim, etc), you will need a kernel that supports this.
4) Same with kernels. CyanogenMod is generally a good choice. Although on the surface it looks just like stock it is heavily modified. Others have only minor modifications and additions, practically a stock experience with a couple of extra features. Pick a handful with features you want and try each for a couple of days. Feel free to switch kernels from the one that comes with each ROM.
Custom UI? If you mean bootloader or something like that, not really. There have been one or two devs who have tried to make this possible (not specific to the Nexus S) but i don't think their (working?) attempts have taken off. Don't get your hopes up here though.
Harbb said:
1) Best way of rooting: We have a Nexus device so i would not waste time using one clicks. Unlock the bootloader using fastboot, flash a custom recovery and then either flash superuser.zip or a custom ROM. This allows the most versatility when changing ROMs, mainly if you ever decide to flash or restore a stock ROM. The Nexus S allows you to lock the bootloader if you ever need to so warranty issues based on unlocked bootloaders are minimal.
4) Same with kernels. CyanogenMod is generally a good choice. Although on the surface it looks just like stock it is heavily modified. Others have only minor modifications and additions, practically a stock experience with a couple of extra features. Pick a handful with features you want and try each for a couple of days. Feel free to switch kernels from the one that comes with each ROM.
Click to expand...
Click to collapse
1. Im fairly new to android OS and while I do generally understand what youre saying its best you give me some links. The only root Ive done with a phone so far are 1 clicks
4. can you elaborate more of why cyanogenmod is a good rom. I hear about it alot and people recommend it,but why?
also, what ROM do you use yourself?
WoolyMarmot said:
1. Im fairly new to android OS and while I do generally understand what youre saying its best you give me some links. The only root Ive done with a phone so far are 1 clicks
4. can you elaborate more of why cyanogenmod is a good rom. I hear about it alot and people recommend it,but why?
also, what ROM do you use yourself?
Click to expand...
Click to collapse
It'll all make sense as soon as you do it, I assumed you had a read through some rooting guides for the Nexus S.
The Nexus S uses a little flashing utility called fastboot. fastboot gives us the ability to replace certain parts of our phone with customised versions. For example, you can replace the stock Recovery partition (which only lets you install Google-signed .zip files) with a custom one, such as TWRP or ClockWorkMod (which let you install any correctly-formatted .zip file). To be able to use fastboot, you need to unlock the bootloader. On our phones it is possible to lock it again afterward with no trace, but the phones warranty would technically be voided (<-- scare tactics). So basically, you unlock the bootloader, flash a custom recovery and then you can freely install a .zip file through the recovery which gives you root privileges. Afterward with this new recovery, feel free to install custom ROMs and the such straight through it.
I personally used Zedomax's guide found here. This does exactly what i stated above and gives you all of the tools to do it, as well as a video. Just follow the video to a T and you'll be fine, it is all pretty simply laid out. I personally use CWM recovery though, not TWRP as it is no longer being developed. I'm pretty sure i explained what each of the steps do above.
CyanogenMod, unlike most other ROMs, have a somewhat large team of developers working together. They add many features to many phones which are often ported to other ROMs, whether it be the concept or the code. It is a great ROM once stable with countless features and they generally do a great job making sure everything is just about perfect, and there is plenty of support and a large userbase. This doesn't mean it's the best, it is just one of the most known.
I personally use Slim ICS daily right now. Largest benefit at the moment is compatibility with CMs bigmem mod, the phone loves the extra RAM.
well in that case I dont wanna use cyanogenmod. I was thinking something as close to stock(or just simple) as possible because I plan on using themes and widgets to customize it.
1 more question before I root, does it matter which version of OS it has? For example, this guide: http://forum.xda-developers.com/showthread.php?t=1007782
nvm, phone already rooted
new question: is it possible to dual boot roms? Ive been reading and they say its possible with using particular apps and an SD card, but the nexus S has no sd slot so...
I just want to ask some questions, seems like some of these threads are out of date.
My phone came out of box JB, so I need to restore down to ICS to root, then use a program called VooDoo to protect said root and update back to JB?
Unless my Bootloader is unlocked, What are the pro/cons of that, I heard you dont get OTA updates, but I could live without those, we can just download them ourselves right?
SirRudolph said:
I just want to ask some questions, seems like some of these threads are out of date.
My phone came out of box JB, so I need to restore down to ICS to root, then use a program called VooDoo to protect said root and update back to JB?
Unless my Bootloader is unlocked, What are the pro/cons of that, I heard you dont get OTA updates, but I could live without those, we can just download them ourselves right?
Click to expand...
Click to collapse
There have been a lot of misconceptions about unlocked bootloaders in this forum. Unlocking your bootloader doesn't necessarily mean the phone will not be eligible for updates, rather the updates will not install on a modified system. What is your real reason for root? Most people are always looking for the latest update, but mess up some files on their phone and don't have backup, in which case the update will fail.
With the Rogers/fido fiasco, we had people go back to the wrong Rogers version of software, since it was not posted properly on the Motorola firmware download website.
Another con is that your warranty would be totally void. Personally I haven't find the need yet to root this device and have had it for almost 4 months now!
Sent from my XT925 using Tapatalk 2
I wont agree for some people the modifications other people do seem trivial.
I've already rooted though, turns out I did have to do what I said above, now running 4.1.1 with Root
I root because a few applications I use, for instance SetCPU allows me to underclock the processors in my phone while the screen is locked, that saves a bit of battery life. I wish Motorola allowed a smart action trigger for when the phone screen was off though, this would help it even more so to save battery.
I use another app to change the lockscreen sounds, which requires root as well.
I havent looked at possible ROM's on this phone yet, as far as I know developers arent quite getting into this phone as deep as they usually do? Thusly I dont think i'll need to use a custom ROM. Just my own optimizations.
Greeting, as the title said i just bought a Moto G and i'm happy with it but i'd like to delete all the bloatware and improve it a little bit especially speed, battery usage and the camera. Do you have any advice? I'm thinking of trying a custom rom or a different kernel but i read everywhere that all the stock stuff is better so i wonder if i'm doing the right thing.
Stay with stock for now so you get a clearer idea of how it compares to custom ROMs, if you go that route in the future. With Xposed Framework, you can achieve much of what a custom ROM offers.
I personally run Stock Motorola Firmware and Faux kernel and I'm seeing much better battery life than with stock kernel.
lost101 said:
Stay with stock for now so you get a clearer idea of how it compares to custom ROMs, if you go that route in the future. With Xposed Framework, you can achieve much of what a custom ROM offers.
I personally run Stock Motorola Firmware and Faux kernel and I'm seeing much better battery life than with stock kernel.
Click to expand...
Click to collapse
Thanks for the advice, to be able to delete all those useless apps from motorola and google i have to do the "root" procedure isn't?
Yes that's correct - I'm running stock 4.4.4 rooted, after trying a few custom ROMs I reverted back to stock.
Sent from my BN NookHD+ using XDA Free mobile app
El Niño Gordo said:
Thanks for the advice, to be able to delete all those useless apps from motorola and google i have to do the "root" procedure isn't?
Click to expand...
Click to collapse
You can 'disable' them without root. No need to delete apps unless you really want to save space.
vpnair said:
You can 'disable' them without root. No need to delete apps unless you really want to save space.
Click to expand...
Click to collapse
I have the 8GB version so i could use some extra space and i'm kinda of a neat freak I decided to remain stock but now i have two options.
1) Disable unwanted apps and optimize the settings to improve every possible thing.
2) Unlock the Bootloader + Root + Xposed Framework and Gravity Box
I'm a little afraid of the risks in rooting it but if i can get greater performance i can live with it. What do you recommend?
The benefits of rooting far out way the drawbacks. Check out the Xposed module DS Battery Saver. I'm not even losing a single percent of battery life during the night now.
Only you know for yourself what right is.
If it tingles in your fingers to root your phone then do so.
After rooting you'll have a lot more tuning and themeing capabilities as if you are not rooted.
But what i recommend is that you should wait a certain amount of time, maybe a monoth or something to see that you will not get a hardware failure out of the box.
As long as your Hardware is not faulty in any way and you do not do anything stupid with your phone, there is no reason to be afraid.
Keep in mind that your warrabty might be lost.
In case of any problems nearly all questions, how to's and answers can be found in this forum.
FYI: I am rooted.
lost101 said:
The benefits of rooting far out way the drawbacks.
Click to expand...
Click to collapse
That's what i hoped to hear but why are there so many procedures for rooting? I found like 10+ guides on this forum about how to root the Moto G and i don't know which one is more reliable.
El Niño Gordo said:
That's what i hoped to hear but why are there so many procedures for rooting? I found like 10+ guides on this forum about how to root the Moto G and i don't know which one is more reliable.
Click to expand...
Click to collapse
1) Download UPDATE-SuperSU-v2.02.zip on phone.
2) Flash custom Recovery (i.e Philz touch) via Fastboot.
3) Enter custom Recovery and flash UPDATE-SuperSU-v2.02.zip.
lost101 said:
1) Download UPDATE-SuperSU-v2.02.zip on phone.
2) Flash custom Recovery (i.e Philz touch) via Fastboot.
3) Enter custom Recovery and flash UPDATE-SuperSU-v2.02.zip.
Click to expand...
Click to collapse
Thanks, is it possible to permanently damage the phone or decrease the overall performance after the bootloader+root unlocking? I'm doing this to make it smoother and faster but i read that some applications may not work anymore and I may lose some key functions like telephone, radio, and audio playback.
El Niño Gordo said:
Thanks, is it possible to permanently damage the phone or decrease the overall performance after the bootloader+root unlocking? I'm doing this to make it smoother and faster but i read that some applications may not work anymore and I may lose some key functions like telephone, radio, and audio playback.
Click to expand...
Click to collapse
Read as much as can and ask if still unsure. The only I know that you can really damage your phone is by running the Fastboot command:
fastboot erase all
You will see people on here posting about "lost imei" - or "imei = 0." Those people have accidentally or deliberately run the above command.
As long as you never run this fastboot command, the Moto G is pretty much unbrickable. If experience any major problem you can always flash via fastboot a Motorola stock firmware image and that will cure it.
lost101 said:
Read as much as can and ask if still unsure. The only I know that you can really damage your phone is by running the Fastboot command:
fastboot erase all
You will see people on here posting about "lost imei" - or "imei = 0." Those people have accidentally or deliberately run the above command.
As long as you never run this fastboot command, the Moto G is pretty much unbrickable. If experience any major problem you can always flash via fastboot a Motorola stock firmware image and that will cure it.
Click to expand...
Click to collapse
Thanks, I finally decided to unroot it, last 2 questions:
1) Is it still possibile to receive all the Android updates after the rooting? I read here that many users were unable to do it.
2) What's a GPE Firmware? It is better than my 4.4 Kitkat?
El Niño Gordo said:
Thanks, I finally decided to unroot it, last 2 questions:
1) Is it still possibile to receive all the Android updates after the rooting? I read here that many users were unable to do it.
2) What's a GPE Firmware? It is better than my 4.4 Kitkat?
Click to expand...
Click to collapse
Rooting can prevent OTA (over the air) updates - however it is possible to remove root - also you can always flash the full firmware images (see Development section). You will also see many people have issues after applying an update. My personal view: is avoid it and always start off fresh by flashing the full firmware image. Basically rooting will not stop you from getting the latest version of Android on your phone.
GPE firmware is intended for the Google Play Edition of Moto G, but will work on pretty much any variant. It is essentially the same firmware on the surface as stock Motorolas, minus their apps. There are no benefits and numerous limitations. I can't speak too much from experience, but as far as I am aware you will be unable to use many of the custom kernels or custom ROMs. This is due to the differences in the GPE filesystem and kernel. The reason for it's popularity is that people believed having the GPE model / firmware installed would mean you get the latest OTA updates much more quickly but this has proven to not be the case.
lost101 said:
avoid it and always start off fresh by flashing the full firmware image.
Click to expand...
Click to collapse
Flashing the full Firmware at every update will delete my apps or settings?
lost101 said:
GPE firmware is intended for the Google Play Edition of Moto G, but will work on pretty much any variant. It is essentially the same firmware on the surface as stock Motorolas, minus their apps. There are no benefits and numerous limitations. I can't speak too much from experience, but as far as I am aware you will be unable to use many of the custom kernels or custom ROMs. This is due to the differences in the GPE filesystem and kernel. The reason for it's popularity is that people believed having the GPE model / firmware installed would mean you get the latest OTA updates much more quickly but this has proven to not be the case.
Click to expand...
Click to collapse
I don't intend to use any apps from Motorola is it still better to remain on my Kitkat? I read that the GPE version is more stable and faster but it could be not true.
To avoid potential issues, it's better to completely wipe phone and start new. You will also get the best experience starting fresh. The Motorola apps are small, disable or remove them if you want. The stock ROM is very close to pure Android. GPE is no more stable or faster than the non-GPE firmware.
I agree with lost101.
Root is far more advantageous. As long as your phone has no hardware complaints, go ahead and do it. Unlocking bootloader and rooting itself does make the phone a little quicker. But you will find the stock Moto Rom is already nicely optimised especially if you adding Xposed for customisability, and disabling stock apps will achieve near AOSP experience.
However, if you receive an OTA and are unable to update (happens if you modify the system partition after rooting - .e.g installing xposed, uninstalling apps), all you need to do is to flash the system.img files from the same firmware (or if available - flash same stock firmware via recovery). This will just refresh the system apps and data. None of your files is modified. Then you can update OTA. Another option is to flash the OTA directly in Philz recovery. I would suggest these methods for incremental OTA's like 4.4.3 to 4.4.4. If the base changes e.g. 4.4.4. to 4.5, I would do full wipe to avoid any problems.
good luck.
come on men, moto g is like nexus, they are almost impossible to be bricked forever
gpe rom is the best, motorola rom is way too bloated and annoying full of motorola apps, yes they are light, and yes i know the moto rom is almost stock, but those apps are annoying like hell
about updates, yes gpe took a long time to be updated to 4.4.3 but instead it was super fast to get 4.4.4 unlike motorola rom
so they are the same in the end
i dont care aboout kernels so in the end GPE for me always, the closest to nexus
I'm beginning to think that all these things are too difficult for me, this is my first smartphone and i'm feeling overwhelmed. I just wanted to clean it a bit saving 500+ MB of junk and never wipe it again but unlocking and rooting require a constant maintenance and micromanagement from what I understand and probably i'll not be able to keep up the pace.
EDIT: I did it, basically:
Unlocked the Bootloader
Rooted using TWRP
Fixed the Logo
Flashed Qualcomm optimized bionic/dalvik
Installed Faux123 Kernel
and now i'm looking to install some juicy apps,is everything alright? Have I missed something?
El Niño Gordo said:
EDIT: I did it, basically:
Unlocked the Bootloader
Rooted using TWRP
Fixed the Logo
Flashed Qualcomm optimized bionic/dalvik
Installed Faux123 Kernel
and now i'm looking to install some juicy apps,is everything alright? Have I missed something?
And what's the difference between http://forum.xda-developers.com/nex...ernel-ver-039-mako-kk-4-4-uv-otg-cpu-t2008222 and http://forum.xda-developers.com/showthread.php?t=2582635?
Click to expand...
Click to collapse
I was under the impression that the 'Qualcomm optimized bionic/dalvik' wasn't necessary and made no difference on Moto G. To get the most out of that Kernel look in the thread for recommended settings. Faux has an app, FauxClock, but there is a free alternative, Trickster Mod.
The difference between those Kernels is that one is for Nexus 4, and one is for Moto G.
Hello, this is my first post on XDA forums so take it easy on me. Recently I've started taking interest in rooting my Xperia Z5. However I don't really know much at all about Linux, and I've never rooted an android device before. I am actually a coder, in fact I'm using a laptop with a HEAVILY modded version of Win10, and with several apps of my own. I've only recently, about a few months ago, bought a decent android phone. I got the Xperia Z5 off eBay for a good price, brand new for a couple hundred bucks. I'm interested in slowly learning basic coding and hacking on android, so I figured I'd go with the first major step and getting it rooted so I can actually mod the thing. The operating system is nice, doesn't have much bloatware, but I'd like to flash a new ROM on it. I've dug around a bit, and I've seen a few root and flash methods, but I really don't have any idea which one is trusted, or which would be the most stable option. I figured my best option would be to signup here, and ask for some advice. I saw ROMX here on the forums, and it looked very promising. But since I'm new to all this, I thought it would be wise for me to ask for advice on where to start what what would be a good rom to flash. I have the E6603 Model, Android 6.0.1, with the April 1, 2016 security patch. And yes, I do fully understand the risks and dangers as well as security concerns of rooting, and flashing. But to be honest, I probably do far more dangerous things on a weekly basis. I thank you all for your time, any help is appreciated.
spynathan said:
Hello, this is my first post on XDA forums so take it easy on me. Recently I've started taking interest in rooting my Xperia Z5. However I don't really know much at all about Linux, and I've never rooted an android device before. I am actually a coder, in fact I'm using a laptop with a HEAVILY modded version of Win10, and with several apps of my own. I've only recently, about a few months ago, bought a decent android phone. I got the Xperia Z5 off eBay for a good price, brand new for a couple hundred bucks. I'm interested in slowly learning basic coding and hacking on android, so I figured I'd go with the first major step and getting it rooted so I can actually mod the thing. The operating system is nice, doesn't have much bloatware, but I'd like to flash a new ROM on it. I've dug around a bit, and I've seen a few root and flash methods, but I really don't have any idea which one is trusted, or which would be the most stable option. I figured my best option would be to signup here, and ask for some advice. I saw ROMX here on the forums, and it looked very promising. But since I'm new to all this, I thought it would be wise for me to ask for advice on where to start what what would be a good rom to flash. I have the E6603 Model, Android 6.0.1, with the April 1, 2016 security patch. And yes, I do fully understand the risks and dangers as well as security concerns of rooting, and flashing. But to be honest, I probably do far more dangerous things on a weekly basis. I thank you all for your time, any help is appreciated.
Click to expand...
Click to collapse
http://forum.xda-developers.com/xperia-z5/general/guide-rooting-unlocking-bootloader-t3354307
there is this which i followed to root my Z5 but with marshamall you do have to have a unlocked bootloader so you can use systemless root, it isnt neccisary to downgrade and backup your DRM but it is advised since sony doesnt seemingly like wanting to repair phones with missing DRM
basic how to:
- Download flashtool and a FTF of your choice
- use flashtool the extract the kernel.sin using tools > sin extractor (you will have to open the FTF file in winrar or something like to copy it)
~ you should get a kernel.elf when extracted
you can then use rootkernel to repack the kernel with a recovery menu like twrp and also disable some system verification stuff that will prevent things from working or the phone booting
this is when you need a unlocked bootloader
- from there you can flash your kernel and boot the device and flash superSU systemless (from the recovery menu )unless you havent downloaded that already
~ you can get to the recovery menu by pressing volume up while the yellow LED shows up on the bootsplash
i may have missed some stuff but that guide I linked has everything i explained here ^ this above is how ive rooted my phone and re-rooted when needed
Envious_Data said:
http://forum.xda-developers.com/xperia-z5/general/guide-rooting-unlocking-bootloader-t3354307
there is this which i followed to root my Z5 but with marshamall you do have to have a unlocked bootloader so you can use systemless root, it isnt neccisary to downgrade and backup your DRM but it is advised since sony doesnt seemingly like wanting to repair phones with missing DRM
basic how to:
- Download flashtool and a FTF of your choice
- use flashtool the extract the kernel.sin using tools > sin extractor (you will have to open the FTF file in winrar or something like to copy it)
~ you should get a kernel.elf when extracted
you can then use rootkernel to repack the kernel with a recovery menu like twrp and also disable some system verification stuff that will prevent things from working or the phone booting
this is when you need a unlocked bootloader
- from there you can flash your kernel and boot the device and flash superSU systemless (from the recovery menu )unless you havent downloaded that already
~ you can get to the recovery menu by pressing volume up while the yellow LED shows up on the bootsplash
i may have missed some stuff but that guide I linked has everything i explained here ^ this above is how ive rooted my phone and re-rooted when needed
Click to expand...
Click to collapse
Awesome thanks! I'll try it first thing tomorrow after work.
Ok so I've gotten everything done, backed up my drm unlocked the bootloader, and what not. Got to the last bit and I can't seem to get fastboot to work, it just says waiting for device. I've tried reinstalling all the drivers a few times, but nothing worked. Flashtool recognized the device, just couldn't get fastboot to recognize it. I'm running windows 10, I've made sure all the drivers are there but still no go. Any help would be greatly appreciated, I'm kinda stuck atm. EDIT, I found a fix for my case. Even though the drivers were installed, for some reason they weren't being read. Anyway all working now, thanks again.
spynathan said:
Ok so I've gotten everything done, backed up my drm unlocked the bootloader, and what not. Got to the last bit and I can't seem to get fastboot to work, it just says waiting for device. I've tried reinstalling all the drivers a few times, but nothing worked. Flashtool recognized the device, just couldn't get fastboot to recognize it. I'm running windows 10, I've made sure all the drivers are there but still no go. Any help would be greatly appreciated, I'm kinda stuck atm. EDIT, I found a fix for my case. Even though the drivers were installed, for some reason they weren't being read. Anyway all working now, thanks again.
Click to expand...
Click to collapse
atleast on windows 10 i found that i had to disable driver signature verifacation and sometimes i had to run command prompt in admin
So I finally got a pixel after lurking around for a while and ended up with a Verizon version. Luckily the dePixel8 fix got the BootLoader unlocked as it wasn't updated yet. Now that I've got the bootloader unlocked, I haven't done anything with it yet. I used to root all of my android phones (Nexus 5, 6, 5x...) and do all kinds of cool things, but as of the 5X, everything I used to root to do is now baked into the Pixel, so I haven't touched anything on it. The one thing I would love to use is Android-Pay... DOH
So, I am verizon phone (on t-mobile), bone-stock OS with an unlocked bootloader and no Android Pay due to failing safety-net. The question is, if I re-lock the bootloader, will I ever be able to unlock it again? Like I want to try a ROM etc? Or is my best bet to get the Kernel that patches the Safety-Net process?
My original thought process drug me to the kernel patch, but since I really haven't had a need to mess with my pixel, the whole process seemed far more involved than the simple desire to use Android-Pay... Which led me to thinking about just re-locking the bootloader... So, please help!
TIA!
cmivxx said:
So I finally got a pixel after lurking around for a while and ended up with a Verizon version. Luckily the dePixel8 fix got the BootLoader unlocked as it wasn't updated yet. Now that I've got the bootloader unlocked, I haven't done anything with it yet. I used to root all of my android phones (Nexus 5, 6, 5x...) and do all kinds of cool things, but as of the 5X, everything I used to root to do is now baked into the Pixel, so I haven't touched anything on it. The one thing I would love to use is Android-Pay... DOH
So, I am verizon phone (on t-mobile), bone-stock OS with an unlocked bootloader and no Android Pay due to failing safety-net. The question is, if I re-lock the bootloader, will I ever be able to unlock it again? Like I want to try a ROM etc? Or is my best bet to get the Kernel that patches the Safety-Net process?
My original thought process drug me to the kernel patch, but since I really haven't had a need to mess with my pixel, the whole process seemed far more involved than the simple desire to use Android-Pay... Which led me to thinking about just re-locking the bootloader... So, please help!
TIA!
Click to expand...
Click to collapse
I believe most of kernels have that safety net patch. Really painless to flash. You can just boot TWRP and flash kernel I believe
mac796 said:
I believe most of kernels have that safety net patch. Really painless to flash. You can just boot TWRP and flash kernel I believe
Click to expand...
Click to collapse
Ok, I'll bite... Is there a "preferred" kernel at this point? Digging through some of the threads on the different kernels is about a bunch of people having problems... I just want the safety-net patch, probably won't use the other features.
cmivxx said:
Ok, I'll bite... Is there a "preferred" kernel at this point? Digging through some of the threads on the different kernels is about a bunch of people having problems... I just want the safety-net patch, probably won't use the other features.
Click to expand...
Click to collapse
I usually just use the kernel that comes with the rom im on. And I use magisk. I have used ex kernel. I really like the ex manager app. And I do believe it still passes safety net with just unlocked bootloader. At least it used to. Google updated safety net this month so I don't know if that changes things.
Alright, I did it... TWRP RC2 + Elemental X sorted out my safety-net issues... Just concerned about legit updates to the phone. Guess I'll fgure that out when the time comes.
Thanks for the help!
cmivxx said:
Alright, I did it... TWRP RC2 + Elemental X sorted out my safety-net issues... Just concerned about legit updates to the phone. Guess I'll fgure that out when the time comes.
Thanks for the help!
Click to expand...
Click to collapse
You will probably be able to take the OTA with just a unlocked Bootloader, you will just have to boot TWRP and Flash that kernel every month. There also is a stock kernel someone builds for what you're trying to do
You can flash google's factory-image.
Then you can re-lock your bootloader and you can unlock it too.