Related
Some of the Sprint Note 4 roms are pre rooted. But where are the instructions for installing TWRP recovery for this phones, Thanks
Download flashify from the play store in flashify go 1 recovery image, 2 download twrp, 3 choose twrp 2.8.1.1
Don't download the one that says zip
Sent from my SM-N910P using JellyBombed Tapatalk 2
There aren't any specific instructions for flashing TWRP recovery and CF-auto root. I think it's because most people know how to do this already. Basically since the Sprint Note 4 has an unlocked bootloader you can simply reboot into Download mode and flash these zips using Odin. Another good way to get some better instructions is to do a Google or Youtube search. Just make sure you type "Sprint Note 4 root" or "Sprint note 4 recovery" in your search query so you know you'll get results specific for your device.
tx_dbs_tx said:
There aren't any specific instructions for flashing TWRP recovery and CF-auto root. I think it's because most people know how to do this already. Basically since the Sprint Note 4 has an unlocked bootloader you can simply reboot into Download mode and flash these zips using Odin. Another good way to get some better instructions is to do a Google or Youtube search. Just make sure you type "Sprint Note 4 root" or "Sprint note 4 recovery" in your search query so you know you'll get results specific for your device.
Click to expand...
Click to collapse
Sorry for asking what on the surface would seem simple to some as an easy question one should already know. Over years I have made and released a half dozen roms on different phones. And each one had it's own little quirks for obtaining root or loading a recovery system. And BTW, thanks for not flaming me for again what would appear to be simple method everyone should aldeady know.
When I first got my new Note 4 I had the exact same concerns as you do about rooting and flashing the recovery. From what I read early on, you want to flash the CR-auto root first, then the TWRP recovery. Both using Odin on your PC. But I will give you a heads up. When you root the phone all will be fine, it's not until you flash the custom recovery and flash a stock rooted rom that you will lose the Wi-Fi calling setting and the toggle for it as well as the sprint boot animations. My stock rooted rom has this stuff fixed. Hybrid Edition is my rom focused towards people who want a stock looking rom.
I would like to take this time to ask if you would download my rom and give it a theming overhaul? That would be awesome. That's if you feel like it or even have the time.
Thank you for the additional info, this is one of those little bits of info that u can spend hours reading and still not find. Or after spending those hours the information may not sink in.
At this point i am still on the fence about rooting on this phone. After getting a hard brick on the HTC EVO LTE and having to buying one full price because i couldn't wait the repair down time. I move rather slower this days before I made the root leap. Once I do take the leap, rest assured your rom is the one I will use and theme. I HATE ANDROID GREEN!
Some Links I Used
timberwolf671 said:
Thank you for the additional info, this is one of those little bits of info that u can spend hours reading and still not find. Or after spending those hours the information may not sink in.
At this point i am still on the fence about rooting on this phone. After getting a hard brick on the HTC EVO LTE and having to buying one full price because i couldn't wait the repair down time. I move rather slower this days before I made the root leap. Once I do take the leap, rest assured your rom is the one I will use and theme. I HATE ANDROID GREEN!
Click to expand...
Click to collapse
Here are some links I used, rooted the same day I got the device
root; http://galaxynote4root.com/galaxy-note-4-root/how-to-root-galaxy-note-4/
root: http://forum.xda-developers.com/showpost.php?p=55865442&postcount=3
recovery: http://teamw.in/twrp_view_all_devices
recovery: http://teamw.in/project/twrp2/266
timberwolf671 said:
Thank you for the additional info, this is one of those little bits of info that u can spend hours reading and still not find. Or after spending those hours the information may not sink in.
At this point i am still on the fence about rooting on this phone. After getting a hard brick on the HTC EVO LTE and having to buying one full price because i couldn't wait the repair down time. I move rather slower this days before I made the root leap. Once I do take the leap, rest assured your rom is the one I will use and theme. I HATE ANDROID GREEN!
Click to expand...
Click to collapse
If you decide, an even easier method, is to just Odin the latest TWRP, and flash the SuperSU zip, in via TWRP. Shouldn't take more than 20 or 30 seconds, for everything.
Where can i find the stock recovery to flash?
LMMT said:
If you decide, an even easier method, is to just Odin the latest TWRP, and flash the SuperSU zip, in via TWRP. Shouldn't take more than 20 or 30 seconds, for everything.
Click to expand...
Click to collapse
Does that give root or do you need to Odin cf-autoroot first?
tommy_2q said:
Does that give root or do you need to Odin cf-autoroot first?
Click to expand...
Click to collapse
After you Odin TWRP, boot into TWRP, and flash the latest SuperSU zip, from Chainfire (Google it). You will then be stock, rooted-- no need for CF Autoroot.
Hello everyone!
I just don't get it. Can anyone explain to me what's the difference between flashing a bumped rom and flashing the same rom un-bumped? I just don't get the whole point of it! Sorry, but coming from a Nexus device (why have I ever changed!!!) I'm new to these things.
So, other questions would be: what's the point of bumping? What if I don't do it and just go about the usual way: Unlocking the bootloader, rooting and installing a custom recovery and then proceed to flash the appropriate and preferred rom, kernel, etc?
Hope somebody will bear with me and try to explain these things to a newcomer
Thanks
astrovale said:
Hello everyone!
I just don't get it. Can anyone explain to me what's the difference between flashing a bumped rom and flashing the same rom un-bumped? I just don't get the whole point of it! Sorry, but coming from a Nexus device (why have I ever changed!!!) I'm new to these things.
So, other questions would be: what's the point of bumping? What if I don't do it and just go about the usual way: Unlocking the bootloader, rooting and installing a custom recovery and then proceed to flash the appropriate and preferred rom, kernel, etc?
Hope somebody will bear with me and try to explain these things to a newcomer
Thanks
Click to expand...
Click to collapse
Because
1) Bumping is used to trick the bootloader into thinking that the boot.img is authentic and from Official LG Sources
2) Without bumping you could have to constantly run fastboot boot boot.img (an example of this was CM11 when it first started development)
3) Bootloader cant be unlocked at this time so we rely on a bootloader exploit in order to run custom recovery
4) Its all about the authenticity. If the LG bootloader does its security checks and anything fails then the system doesnt boot
Thanks for the very easy tuo understand explanation. I should have thought that the problem was unlocking the bootloader! Guess I'll have to with the Flow and bump my new phone. I wish I asked my Carrier for an HTC M8
Sent from my Xperia Tablet Z LTE using XDA Free mobile app
simple answer: bump is the only way to unlock g3 bootloader.
all roms are bumped whether displaying [BUMPED] or not.
rhystagram said:
simple answer: bump is the only way to unlock g3 bootloader.
all roms are bumped whether displaying [BUMPED] or not.
Click to expand...
Click to collapse
Ok, so by simple logic, once I have installed, either via bump, flashify or ADB a recovery, I can pretty much flash any rom that is appropriate for my model no, isn't it?
So there is one more question I have: what is the purpose of unlocking the bootloader and then what could be the problems if I don't? If everything I flash for this device (TWRP, roms, kernels, etc) is, by default, bumped, what's the purpose of installing bump at all?
astrovale said:
Ok, so by simple logic, once I have installed, either via bump, flashify or ADB a recovery, I can pretty much flash any rom that is appropriate for my model no, isn't it?
So there is one more question I have: what is the purpose of unlocking the bootloader and then what could be the problems if I don't? If everything I flash for this device (TWRP, roms, kernels, etc) is, by default, bumped, what's the purpose of installing bump at all?
Click to expand...
Click to collapse
You're making it so much harder for yourself dude.. There really is only one way to install custom ROMs and that is by Bumping your phone. That's it.
You go here and read the entire topic. Don't miss a single thing.
Then go here and flash the zip for the latest TWRP.
After that you can install any ROM in the OG and Android Development section.
That's all there is to it. You can read in those topics for more information about what they do.
if you dont bump, then you wont have twrp lol.
you cant flash any roms anyway, you'll potentially brick/soft brick your phone.
roms etc are bumped because they have a patch script implanted to run on the phones correctly.
rhystagram said:
if you dont bump, then you wont have twrp lol.
you cant flash any roms anyway, you'll potentially brick/soft brick your phone.
roms etc are bumped because they have a patch script implanted to run on the phones correctly.
Click to expand...
Click to collapse
OK. Got it! It took a while, but I give up!
Thanks for the help. Coming from the most easy to play with phones (only Nexus so far, but I hate the N6), it isn't easy to have to deal with more stuff than usually needed and hence more complications than usually had.
I thought that, after rooting I could flash TWRP via flashify or rom toolbox and then I would have TWRP without BUMP, but it must be that I'm missing something, if you say I MUST bump my phone to install TWRP.
Thanks and see you around
How to bump lg g3
DevilFan14 said:
How to bump lg g3
Click to expand...
Click to collapse
What exactly do you mean "How to bump"??? Bump and loki are bootloader exploits that allowed us to boot TWRP and all the benefits TWRP offers... On the user side of things you don't "Bump" anything- the Roms, Kernels, and recoveries are "pre-bumped" by the developers and 99.9% of the time they will say whether or not it is "bumped" or "lokied" although loki is really outdated and I doubt you'll encounter it. So in a nutshell we(the user) doesn't "Bump" anything and just make sure to really read before flashing
Sent from my DROID RAZR HD using XDA Labs
I am relatively new to rooting and bought a used sprint note 4 with 5.1.1 cog5 update already installed, and have been waiting around for one of the universal root programs like oneclickroot to drop a root for it, but it never happens. I heard the new security in 5.1.1 is making it impossible? Is there any work arounds? I have seen a couple homebrews show up that seem questionable and limited. Anyone who is knowledgeable is welcome, but please no "newb just read" comments. Those are rarely helpful.
Funny, after owning this phone for about a year I decided to root yesterday being 100% stock and on OG5. First flash TWRP using ODIN, then install beastmode via TWRP to begin. TWRP will ask after to install superSU, install it. So far I'm using xposed and wish I had done this sooner! Sorry for the lack of details but I'm on mobile right now.
mnrivera210 said:
Funny, after owning this phone for about a year I decided to root yesterday being 100% stock and on OG5. First flash TWRP using ODIN, then install beastmode via TWRP to begin. TWRP will ask after to install superSU, install it. So far I'm using xposed and wish I had done this sooner! Sorry for the lack of details but I'm on mobile right now.
Click to expand...
Click to collapse
maybe im just making newb mistakes then? If you could take the time to break these steps in the "for dummies" version, i will have my wife send you dirty photos in my infinite thanks!
[email protected] said:
maybe im just making newb mistakes then? If you could take the time to break these steps in the "for dummies" version, i will have my wife send you dirty photos in my infinite thanks!
Click to expand...
Click to collapse
EDIT: Sorry, having a bit of an issue with the method I mentioned. Will write back when resolved. Sorry for any confusion.
[email protected] said:
maybe im just making newb mistakes then? If you could take the time to break these steps in the "for dummies" version, i will have my wife send you dirty photos in my infinite thanks!
Click to expand...
Click to collapse
Check out these roms buy @tx_dbs_tx they self root upon flashing.
Here:
http://forum.xda-developers.com/showthread.php?t=2956667
Also check out his stock rooted roms here:
http://forum.xda-developers.com/showthread.php?t=3185274
Need to fix post. Will write back later.
Broken
This method does not work due to complications from SELinux and dm-verity. Sorry guys, looks like the Note 4 can't be rooted at this time :/
Feeling generous? PM me an Amazon gift card!
DISCLAIMER:
Code:
Your warranty is now void. I nor XDA is responsible for the effects this may have on your device or your life, whether that be bricking, loss of data, combustion, nuclear war, or the election of businessmen as President (wait what).
Remember, its not root that puts your device in danger, its how you use it.
If you don't know what a locked bootloader is, or think that Chainfire is a new video game, you shouldn't be here, go read a little about Android and the Galaxy Note 4 before continuing
So let's begin:
What You'll Need:
This *experimental* firmware: https://www.androidfilehost.com/?fid=457095661767141025
Kingroot, SuperSume, and FlashFire, all available from this zip: https://www.androidfilehost.com/?fid=673368273298935732
This modified "from-noship" pre-rooted OC6: https://www.androidfilehost.com/?fid=529152257862707318
What To Do:
Step 1: Goin' Wayy Down
Use ODIN to flash the experimental firmware.
MASTER CAUTION: This will wipe ALL data on the device!! Backup your stuff before proceeding. I nor XDA is responsible for loss of your memes!
Simply flash the .TAR.MD5 file in the zip using the AP slot in ODIN, and then wait for the phone to boot (which is literally all of 10 seconds).
Step 2: Our Old Friend
After the OS is installed, go to the file manager and install Flashfire, Kingroot, and SuperSume
Open Kingroot and use it to root, the in-app instructions will guide you through.
After you've gotten root with KingRoot, open SuperSume, grant it root, and press the big blue button, let it do its thing.
When its done, SuperSU will open and ask you to update the binaries, hit continue, then hit "normal". When its done hit "OK", don't reboot (you don't need to).
At this point you've got root! Now, let's get back to the present!
Step 3: Back to the Future!
Open FlashFire, grant it root access, and flash the modified OC6 with these settings:
Mount /system read/write
A wipe isn't required, but it is recommended (if you do wipe, make sure to put that card B E F O R E the flash zip/ota card!)
Hit "flash", let it flash, reboot, and load.
Disclaimer: I have not personally tested this firmware before release, but it should work. However, I make no guarantees!
Guess what? You're done!
I worked to get your phone rooted, I hope now you guys can get some ROMs going!
OC6 Rollback Files
Something go horribly wrong? Get yourself back on something stable
G900AUCU2COC6: https://www.androidfilehost.com/?fid=745425885120712191
Thanks @xdanilva for the firmware
Reserved
Also Reserved
Reserved
One more :3
Does this root work for 6.0.1 PK1? Or do I need to b on 5.1.1 ?
Also I'm tempted to try but it's a definite wait for my because I've had this phone since it came out an I was just at AT&T last night to trade an upgrade. I'm going back next week an upgrading to iPhone 7+ 128gb because there is no Notes devices and I really don't want Galaxy S7 when in a month or 2 the S8 is coming.
Thanks
Sent from my SAMSUNG-SM-N910A using Tapatalk
nemopsp said:
Does this root work for 6.0.1 PK1? Or do I need to b on 5.1.1 ?
Also I'm tempted to try but it's a definite wait for my because I've had this phone since it came out an I was just at AT&T last night to trade an upgrade. I'm going back next week an upgrading to iPhone 7+ 128gb because there is no Notes devices and I really don't want Galaxy S7 when in a month or 2 the S8 is coming.
Thanks
Sent from my SAMSUNG-SM-N910A using Tapatalk
Click to expand...
Click to collapse
The root is universal. No matter what firmware you are on, you still have to flash the experimental firmware with ODIN. That's what's so beautiful about it
Also, please try not to quote the entire OP, it clutters up the thread
-I personally would have gone with a OnePlus 3T, same if not better specs as the iPhone 7+ and at half the price-
AptLogic said:
-I personally would have gone with a OnePlus 3T, same if not better specs as the iPhone 7+ and at half the price-
Click to expand...
Click to collapse
Yea I agree with you but don't have $400 to put down on a phone. A buddy of mine has OnePlus3 got it on release. But personally I don't have to money to buy a phone every couple months. I normally wait like every 2 an half years. iPhone 7 isn't my favorite choice but I do miss iMessage and iPhone seems there always a new jailbreak coming out might have to wait 6 months but I've waited over 2 years for a root on this phone.
Thanks for releasing this root! I'll b checking the forums an see how this is going!
Sent from my SAMSUNG-SM-N910A using Tapatalk
Just a little PSA: If the towelroot I uploaded does not work PLEASE TELL ME because that means I need to upload the newer version and put the use of modstrings in the OP.
Thanks
anyone root successful on 6.0.1 ?
I'm going to give this a go as soon as I get ahold of a PC. I'm excited to see you prove me wrong.
Awesome this looks very promising!
If I use this, what Android version will I end up on?
jboucher614 said:
Awesome this looks very promising!
If I use this, what Android version will I end up on?
Click to expand...
Click to collapse
If you go through the whole guide you should end up on Android 5.0.1
AptLogic said:
If you go through the whole guide you should end up on Android 5.0.1
Click to expand...
Click to collapse
That's pretty good, is there going to be any way to get to Marshmallow rooted?
jboucher614 said:
That's pretty good, is there going to be any way to get to Marshmallow rooted?
Click to expand...
Click to collapse
No, we can't do that because the locked bootloader won't allow a systemless root, which would be necessary for rooting marshmallow. We can, however, make UNrooted marshmallow ROMs.
Hi !
Thank's For This, I Have Tried This Experimental Rom Before, And It's Worked Fine Without Any Problems (We Can Also Back To The Officiel Firmware With Odin), But I Never Tried To Root.
So, I Need To Know If We Could Install An Other Custom Rom ?
Samy_Wutlol said:
Hi !
Thank's For This, I Have Tried This Experimental Rom Before, And It's Worked Fine Without Any Problems (We Can Also Back To The Officiel Firmware With Odin), But I Never Tried To Root.
So, I Need To Know If We Could Install An Other Custom Rom ?
Click to expand...
Click to collapse
We can install custom TouchWiz ROMs, but you would need to install the pre-rooted OC6 in the OP first (if you want to use 5.0). Unfortunately we still can't get AOSP ROMs working because that would need a new Kernel and the locked bootloader doesn't allow it.
Post #2 has been updated with ODIN recovery files.
Nice work!
I seem to be a little lost here, but can we use/make rooted MM ROMs after doing the steps in OP?
boofman said:
Nice work!
I seem to be a little lost here, but can we use/make rooted MM ROMs after doing the steps in OP?
Click to expand...
Click to collapse
No we can't. No rooted MM ROMs, but you can make rooted LP ROMs
AptLogic said:
No we can't. No rooted MM ROMs, but you can make rooted LP ROMs
Click to expand...
Click to collapse
I'm gonna have to do a lot of reading about this first. Thanks for your great work!
boofman said:
I'm gonna have to do a lot of reading about this first. Thanks for your great work!
Click to expand...
Click to collapse
Feel free to take a look at the Galaxy s5 forums, we're in the same boat
Also I may have made a mistake in the OP. I'd like you guys to hold off on trying it until I fix it. Thanks!
i want to buy this phone but cant live without xposed, so is there a 6.0 rom anywhere for this phone? ive looked but havent found anything
ncsuwolfs said:
i want to buy this phone but cant live without xposed, so is there a 6.0 rom anywhere for this phone? ive looked but havent found anything
Click to expand...
Click to collapse
Sultanxda and Arter97 CM MM Roms are still up im sure you can find a few others too
Edit: Opps sorry thought was OP3 thread :laugh:
ncsuwolfs said:
i want to buy this phone but cant live without xposed, so is there a 6.0 rom anywhere for this phone? ive looked but havent found anything
Click to expand...
Click to collapse
This phone launched with nougat. You can't run marshmallow on it.
liam_davenport said:
Sultanxda and Arter97 CM MM Roms are still up im sure you can find a few others too
Click to expand...
Click to collapse
where do i find those? (i have searched but can only find cm14 for pixel?
toknitup420 said:
This phone launched with nougat. You can't run marshmallow on it.
Click to expand...
Click to collapse
this is what i was afraid of....
ncsuwolfs said:
where do i find those? (i have searched but can only find cm14 for pixel?
this is what i was afraid of....
Click to expand...
Click to collapse
They do have magisk for this phone. I haven't used it but from what I've seen it's similar to xposed.
toknitup420 said:
They do have magisk for this phone. I haven't used it but from what I've seen it's similar to xposed.
Click to expand...
Click to collapse
I don't understand how it works but unless I misunderstood if you go to the official Magisk thread the creator claimed he was able to run Xposed with Magisk because his app prevented Xposed from needing to write anything to the system image. I supposed if you can't live without Xposed that would be worth looking into further.
There are no Marshmallow ROM's anywhere for this phone.
Never was, never will be.
Magisk isn't an Xposed replacement.
There is no replacement for Xposed.
Dammit, I miss my ~17 Xposed modules.
Most of which gave me options that you won't find on any custom Nougat ROM.
toknitup420 said:
They do have magisk for this phone. I haven't used it but from what I've seen it's similar to xposed.
Click to expand...
Click to collapse
It's a root option. As in you can run SuperSU or Magisk. Magisk has mods that can accomplish certain things that Xposed did but the majority of them don't work with the pixel so don't count on a suitable replacement.
jhs39 said:
I don't understand how it works but unless I misunderstood if you go to the official Magisk thread the creator claimed he was able to run Xposed with Magisk because his app prevented Xposed from needing to write anything to the system image. I supposed if you can't live without Xposed that would be worth looking into further.
Click to expand...
Click to collapse
The Magisk on pixel is supported by a guy that frequents the RR thread and he modded Magisk to work on the pixel so it's unofficial. Also there is NO Xposed for android n
---------- Post added at 11:55 PM ---------- Previous post was at 11:54 PM ----------
CZ Eddie said:
Magisk isn't an Xposed replacement.
Click to expand...
Click to collapse
This isn't completely true. There are Magisk mods that overlap things that Xposed was capable of. So depending on what you are trying to do and IF mods even worked for the pixel. It could be a replacement for some.
The Magisk on pixel is supported by a guy that frequents the RR thread and he modded Magisk to work on the pixel so it's unofficial. Also there is NO Xposed for android n
---------- Post added at 11:55 PM ---------- Previous post was at 11:54 PM ----------
Well that explains why on the official Magisk page the developer said he didn't know if there would ever be a working version for the Pixel phones but people are using Magisk anyway. Unfortunately Magisk seems to run into the same problems as SU on the Pixel in that it doesn't always install properly or maintain root if it does install--plus most Magisk modules don't work with the Pixel, which makes it much less functional than on other phones.
jhs39 said:
Well that explains why on the official Magisk page the developer said he didn't know if there would ever be a working version for the Pixel phones but people are using Magisk anyway. Unfortunately Magisk seems to run into the same problems as SU on the Pixel in that it doesn't always install properly or maintain root if it does install--plus most Magisk modules don't work with the Pixel, which makes it much less functional than on other phones.
Click to expand...
Click to collapse
I've been running magisk since 11.6 was dropped. I haven't had any issues keeping root or installing. Works every time and I flashing a new rom every 3 or 4 days.
Same with SU.
For magisk people keep leaving busy box in Magisk Manager turned on so it screws up root. It's in the magisk FAQ.
pcriz said:
I've been running magisk since 11.6 was dropped. I haven't had any issues keeping root or installing. Works every time and I flashing a new rom every 3 or 4 days.
Same with SU.
For magisk people keep leaving busy box in Magisk Manager turned on so it screws up root. It's in the magisk FAQ.
Click to expand...
Click to collapse
If you've been running SU for more than a few months on the Pixel then you know Google broke root on it and SU had to rewrite the app to fix the issue. That doesn't happen on other phones and is very likely intentional on the part of Google. At another point SU was suddenly causing problems and SU devs had to add a boot signature file to the flashing process. Again, this kind of thing doesn't happen with other phones. Pretending that SU and Magisk have always worked without problems on the Pixel is extremely misleading.
jhs39 said:
If you've been running SU for more than a few months on the Pixel then you know Google broke root on it and SU had to rewrite the app to fix the issue. That doesn't happen on other phones and is very likely intentional on the part of Google. At another point SU was suddenly causing problems and SU devs had to add a boot signature file to the flashing process. Again, this kind of thing doesn't happen with other phones. Pretending that SU and Magisk have always worked without problems on the Pixel is extremely misleading.
Click to expand...
Click to collapse
Lol why would I lie. I've been on magisk now since Feb. Tell me why I don't lose root?
Maybe you can't get it to work but that doesn't mean it doesn't work.
Also if you are following the evolution of things, signed builds are more secure. Root isn't broken you just have to resign the boot image because of HOW root is attained on the pixels.
Yes it only happens on the pixels because of the partition changes in the pixel. Since they have to be signed now with any bootloader from may and older, users need the verified boot signer.
But if you are paying five minutes worth of attention to all this you would know that all you have to do is flash the April bootloader and there is no longer a requirement for builds to be signed.
I've been through all this a million times. That said I'm still rooted like a champ.
Yeah for the pixel it's pretty straight forward, if you want to root use chainfire's zip it's 2.79 SR3, you're even advised on 2.82 that pixel users will not want to upgrade.
As far as the may bootloader situation, flash the april bootloader and you don't need to bother with the signing zip. Besides, I think dealing with knox was much worse
pcriz said:
Lol why would I lie. I've been on magisk now since Feb. Tell me why I don't lose root?
Maybe you can't get it to work but that doesn't mean it doesn't work.
Also if you are following the evolution of things, signed builds are more secure. Root isn't broken you just have to resign the boot image because of HOW root is attained on the pixels.
Yes it only happens on the pixels because of the partition changes in the pixel. Since they have to be signed now with any bootloader from may and older, users need the verified boot signer.
But if you are paying five minutes worth of attention to all this you would know that all you have to do is flash the April bootloader and there is no longer a requirement for builds to be signed.
I've been through all this a million times. That said I'm still rooted like a champ.
Click to expand...
Click to collapse
I've been paying a lot of attention to it actually. When you have to flash an old bootloader to prevent boot looping (which is what actually happens if you use the up to date bootloader) or you have to flash a boot signature file that wasn't previously needed then the flashing procedure suddenly changes again I wouldn't say it's easy to maintain root on a Pixel. I guess different people have different definitions for what easy is. As for Knox, I used to have many Samsung phones and once a procedure was figured out to get around it and root you were good for as long as you had the phone. With the Pixels Google seems to be actively trying to screw up apps that create root or bypass safety net via its monthly updates. It's a completely different situation in my opinion.
jhs39 said:
I've been paying a lot of attention to it actually. When you have to flash an old bootloader to prevent boot looping (which is what actually happens if you use the up to date bootloader) or you have to flash a boot signature file that wasn't previously needed then the flashing procedure suddenly changes again I wouldn't say it's easy to maintain root on a Pixel. I guess different people have different definitions for what easy is. As for Knox, I used to have many Samsung phones and once a procedure was figured out to get around it and root you were good for as long as you had the phone. With the Pixels Google seems to be actively trying to screw up apps that create root or bypass safety net via its monthly updates. It's a completely different situation in my opinion.
Click to expand...
Click to collapse
You went from saying "Magisk and SuperSU don't install properly or don't keep root" to talking about the changes to boot signing on newer bootloaders.
If you are going to share information at least try to be accurate. There is a whole slew of users in the development section running rooted ROMs just fine but if a new user reads your posts they will assume root is broken and flashing the pixel leads to boot loops.
You don't want to deal with the verified boot signer all you need to do is flash the april bootloader and reboot. It happens once. If that is too difficult then maybe those same people shouldn't bother flashing anything period.
No one said flashing and modding would be easy but flashing a bootloader ain't hard.
You might also want to take a look at the other threads in the Q&A which show people unable to flash TWRP, people boot looping when they flash TWRP, people unable to maintain root or flash custom Roms, etc. Even if you are able to maintain root like a pro there is plenty of very easy to find evidence from other people who don't have the same no problems experience as you.
jhs39 said:
You might also want to take a look at the other threads in the Q&A which show people unable to flash TWRP, people boot looping when they flash TWRP, people unable to maintain root or flash custom Roms, etc. Even if you are able to maintain root like a pro there is plenty of very easy to find evidence from other people who don't have the same no problems experience as you.
Click to expand...
Click to collapse
The only thing that proves is we have a ton of users that don't take the time to research.
You got users coming back from O that don't know they need an Android N bootloader in both slots to flash TWRP again.
You have users that are fastbooting ZIP files
You have users fastboot FLASHING TWRP
I read through those threads and in just about every case if you can't get recovery and root on the april boot loader it's probably user error. Welcome to XDA, it's the same on every device.
I guess all the guys that are rooted must full it. Or wizards or something.
I guess reading step by step directions makes me a wizard.
pcriz said:
I read through those threads and in just about every case if you can't get recovery and root on the april boot loader it's probably user error. QUOTE]
I answer these questions a lot and that is most certainly true.
Click to expand...
Click to collapse
pcriz said:
The only thing that proves is we have a ton of users that don't take the time to research.
You got users coming back from O that don't know they need an Android N bootloader in both slots to flash TWRP again.
You have users that are fastbooting ZIP files
You have users fastboot FLASHING TWRP
I read through those threads and in just about every case if you can't get recovery and root on the april boot loader it's probably user error. Welcome to XDA, it's the same on every device.
I guess all the guys that are rooted must full it. Or wizards or something.
I guess reading step by step directions makes me a wizard.
Click to expand...
Click to collapse
Actually that's absolutely not true. I came from a Nexus 6P. On the XDA threads for that phone there is an accurate, clear, up to date step by step guide on how to flash anything with that phone, including separate instructions for how to root, install a custom recovery, how to install a custom Rom and how to go back to stock. On the Pixels the threads are a complete free for all filled with confusing, contradictory and inaccurate information. I just read posts from earlier today from someone who is getting boot loops when flashing SuperSu. Not a single person responded by suggesting that he use the April bootloader. The suggested solution (which didn't work) was to flash the boot sig zip. How exactly is somebody supposed to research flashing on the Pixel when the XDA threads for this phone are a complete shambles? And since you are supposedly such an expert at flashing on this phone why don't you do something useful and help other people who are having problems instead of wasting everybody's time with your utterly pointless posts about how easy it is to flash on this phone and how people having trouble are idiots who didn't do their own research? You aren't simply part of the problem, dude--you are literally the personification of everything that is wrong with XDA.
jhs39 said:
.
Click to expand...
Click to collapse
This discussion ain't worth reading whatever it is you typed dude. I'm going to agree to disagree.
Sorry stable root is an unattainable unicorn for you. Sorry you're having such a difficult time. Sorry that making excuses for false information is a priority over finding out how it's actually done.
Happy flashing, best of luck to you sport.