Develop Bugs

Why is the sm-n910p with 5.1.1 seem to be root proof?

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.

How to update Leedroid ROM?

This is my first post here, so please bear with me if I'm in the wrong forum or if this question doesn't belong here.
I got my HTC10 a few months ago and decided to try rooting it. It was my first time rooting a phone, and it took lots of research and following guides to make it happen. Anyway, i successfully rooted my phone, and installed LeeDroid's custom ROM. I've been very happy with it. I just realized earlier today that i haven't been updating the ROM, though! I downloaded the latest update .zip, but have no idea how I'm supposed to perform the update. I'm quite a noob at this stuff, and hope someone has the patience to help me pull this off.
Help, please!
Trevor

Frunch said:
This is my first post here, so please bear with me if I'm in the wrong forum or if this question doesn't belong here.
I got my HTC10 a few months ago and decided to try rooting it. It was my first time rooting a phone, and it took lots of research and following guides to make it happen. Anyway, i successfully rooted my phone, and installed LeeDroid's custom ROM. I've been very happy with it. I just realized earlier today that i haven't been updating the ROM, though! I downloaded the latest update .zip, but have no idea how I'm supposed to perform the update. I'm quite a noob at this stuff, and hope someone has the patience to help me pull this off.
Help, please!
Trevor
Click to expand...
Click to collapse
Boot to recovery, tap install, then find the ROM download and swipe the bar right to flash

Frunch said:
This is my first post here, so please bear with me if I'm in the wrong forum or if this question doesn't belong here.
I got my HTC10 a few months ago and decided to try rooting it. It was my first time rooting a phone, and it took lots of research and following guides to make it happen. Anyway, i successfully rooted my phone, and installed LeeDroid's custom ROM. I've been very happy with it. I just realized earlier today that i haven't been updating the ROM, though! I downloaded the latest update .zip, but have no idea how I'm supposed to perform the update. I'm quite a noob at this stuff, and hope someone has the patience to help me pull this off.
Help, please!
Trevor
Click to expand...
Click to collapse
apart from what the above is mentioned you could also try reading through Lee's thread if you are stuck somewhere while updating...
latest nightly for lee's would be r124

Thanks for the responses! Looks like it's easier than i suspected. I'll check out Lee's thread for more info too.
Thanks again!

Frunch said:
Thanks for the responses! Looks like it's easier than i suspected. I'll check out Lee's thread for more info too.
Thanks again!
Click to expand...
Click to collapse
also you could download the standalone nightly zip from there and flash it directly from twrp...
r124 is the latest nightly zip
https://www.androidfilehost.com/?fid=24591000424948510 (mine)
or
http://forum.xda-developers.com/showpost.php?p=67824074&postcount=6471 (sardroid's upload)

any marshmellow roms?

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.

Question Root phone

Is the revvl v+5g rootable

*edit*
[ROOT] [FLASH STOCK]
DISCLAIMER: Please post failures and successes. Keep it relevant, everything else to the DMs please. It makes it easier for others to Q&A. Everyone thanks you for your understanding. ***IF YOU ARE NEW BEWARE!!! BEFORE YOU CHANGE ANYTHING MAKE A...
forum.xda-developers.com
yep. here it is. Unlock bootloader, root and recovery. Sorry, I forgot to update this post earlier.

Sonia Ramirez said:
Yes.
Click to expand...
Click to collapse
Please take this post down. Kingoroot is malware. Also, you cannot install supersu on this phone. First of all, the method described here requires you have a custom recovery and TWRP has yet to be ported to this phone. Even if you did have TWRP you have to root with magisk. I have posted a complete guide on how to root and recover this device.
Either this guy just copy and paste trying to be helpful and not knowing, or this is a deliberate attempt at sabotage.
I urge all readers to disregard this guy's comment as it is totally false.

Question Struggling to root...

Hey all,
Hope someone can offer an insight here...
I've successfully managed to unlock the bootloader and at one point had rooted the October firmware, but I can't work out how to root the latest Nov firmware. I see a few sets of instructions but I'm struggling here...
I'm currently back on stock and so unsure how to update to the latest system update and then root that?
If someone could lead me to some detailed instructions I (and I'm sure many others!) would be highly grateful!

I'm a senior engineer, PC user since Windows 3.11, owned and rooted numerous Android phones over the years, wrote computer programs both for Big Data cloud solutions as well as embedded software for microcontrollers AND xdadevelopers tutorials still baffle me to this day. Unfortunately the way to comprehend what's going on is to:
a) lurk on multiple threads and try to piece it together
b) wait for somebody like you to create a simple step-by-step tutorial that doesn't assume high-degree of inside knowledge
Good luck. I'm receiving my Pixel 6 Pro so I'm in the same situation as you.

cd993 said:
Hey all,
Hope someone can offer an insight here...
I've successfully managed to unlock the bootloader and at one point had rooted the October firmware, but I can't work out how to root the latest Nov firmware. I see a few sets of instructions but I'm struggling here...
I'm currently back on stock and so unsure how to update to the latest system update and then root that?
If someone could lead me to some detailed instructions I (and I'm sure many others!) would be highly grateful!
Click to expand...
Click to collapse
My guide for flashing Safetynet is a bit more foolproof now. For being rooted on Nov firmware, you would need to OTA to the .036 build first and use the unofficial user uploaded boot.img and vbmeta.img mentioned in my post.
Otherwise, you can root on .015 and wait for the .036 factory images to be uploaded, and wait until we work out how to update without wiping.
Working SafetyNet with Pixel 6 Pro Android 12
This is no longer using an Unofficial Magisk app, it's the official Canary and USNF 2.2.0 1. Download the latest Magisk Canary build 2. Patch the boot.img from the Factory Images in Magisk, you'll also need the vbmeta.img if you aren't already...
forum.xda-developers.com

RushPL said:
I'm a senior engineer, PC user since Windows 3.11, owned and rooted numerous Android phones over the years, wrote computer programs both for Big Data cloud solutions as well as embedded software for microcontrollers AND xdadevelopers tutorials still baffle me to this day. Unfortunately the way to comprehend what's going on is to:
a) lurk on multiple threads and try to piece it together
b) wait for somebody like you to create a simple step-by-step tutorial that doesn't assume high-degree of inside knowledge
Good luck. I'm receiving my Pixel 6 Pro so I'm in the same situation as you.
Click to expand...
Click to collapse
Sadly, that's the way XDA developed in the most recent years. A lot of developers have become "impatient", they rarely tolerate questions (which they consider unnecessary for reasons of their own) or consider everything that is not in their concise jargon offtopic and either ignore, flame or delete those.
The basics are not explained anymore, they expect everyone to work naturally with the tools at hand, most often or not "small" steps are left out (like clicking on something, or changing a menu), or they refer to "go look at that guide" - only then - that guide tells you (aswell) "for step 3, go look at that guide", because "everyone should know" - that way the rooting community is quite small and elitist; and it's hard for outsiders to come in (and potentially add something to the pool of stuff) simply because it's not a pleasant experience to "dive" into the world of Android customization. It's a sad development and only very few seem to be intend on breaking it.
Then we also have the problem of manufacturers trying to make this communities life harder, just take a look at Google and the constant war to have safetynet NOT trip, to give people the chance to use banking apps or GPay. It's a constant struggle and many "guides" get out of date pretty quickly - and most often or not, those are not kept up to date, or getting demolished by a mod team, so that also adds to the whole confusion, when people try to work with guides / community fixes that won't even work anymore.

cd993 said:
Hey all,
Hope someone can offer an insight here...
I've successfully managed to unlock the bootloader and at one point had rooted the October firmware, but I can't work out how to root the latest Nov firmware. I see a few sets of instructions but I'm struggling here...
I'm currently back on stock and so unsure how to update to the latest system update and then root that?
If someone could lead me to some detailed instructions I (and I'm sure many others!) would be highly grateful!
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/...irmware-sd1a-210817-036.4353807/post-85857811
I followed the instruction from this post to restore my P6P to preinstalled October firmware, then updated with November firmware OTA, then unlocked bootloader and root again. My phone works much better now.
I made a mistake of flashing the vbmeta and boot imgs of October firmware for rooting after updating November firmware OTA. I experienced some strange issues with my phone until I restored it with Official Google Android Flash Tool and start the whole rooting process again with the correct version of vbmeta and boot imgs.

Pekempy said:
My guide for flashing Safetynet is a bit more foolproof now. For being rooted on Nov firmware, you would need to OTA to the .036 build first and use the unofficial user uploaded boot.img and vbmeta.img mentioned in my post.
Otherwise, you can root on .015 and wait for the .036 factory images to be uploaded, and wait until we work out how to update without wiping.
Working SafetyNet with Pixel 6 Pro Android 12
This is no longer using an Unofficial Magisk app, it's the official Canary and USNF 2.2.0 1. Download the latest Magisk Canary build 2. Patch the boot.img from the Factory Images in Magisk, you'll also need the vbmeta.img if you aren't already...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you so much for helping the poor newbies! With your updates I think I can comprehend what's going on. What's changed from my experience with rooting One Plus 6 is that I never had to patch boot images on the phone itself and this "vbmeta" is completely new to me as well.
Can I buy you a coffee via some donation?

RushPL said:
Thank you so much for helping the poor newbies! With your updates I think I can comprehend what's going on. What's changed from my experience with rooting One Plus 6 is that I never had to patch boot images on the phone itself and this "vbmeta" is completely new to me as well.
Can I buy you a coffee via some donation?
Click to expand...
Click to collapse
No need but thank you for offering.
The vbmeta is also new to me. I want to be clear, I've mostly compiled others' instructions (credited in the post) with my own experience, and tried to make it as easy to follow as I can

I was able to root successfully with working Safety Net! Thank you @Pekempy