Develop Bugs

[rom] basic stock rom

Here's a basic stock rom in case you need it sometime
the only modifications made are the su and flash_image binaries are included and ro.secure has been turned to 0 so you can adb remount.
How to flash download the rom from here
Place rom on sdcard
wipe data and all else
then flash rom
reboot and do what you need to do

Cool, you never know when you might need this.

Thank you! Appreciated.
Sent from my VM670 using XDA App

Asadullah said:
Here's a basic stock rom in case you need it sometime
the only modifications made are the su and flash_image binaries are included and ro.secure has been turned to 0 so you can adb remount.
Click to expand...
Click to collapse
How is this comparable to the rom listed here?
bit ly backslash fBEJnU
I want to have a known working recovery before I make any more changes to my phone. I am not exactly a newbie to this stuff (I have a Pandigital Novel that has been rooted and hacked into a nice tablet) but this is taking things to a whole new level for me and I need my phone. So I'm a bit nervous.
Of course I really wish I'd asked around some before I got to work on removing some of the stuff on it already (mostly known junkware from Virgin Mobile and stupid stuff like weblinks pretending to be native apps) after rooting it with superoneclick and installing root explorer. I need to know if your rom or the one I linked to will be able to allow me to roll back to a default installation that I can revert to if there are any issues down the road. Can you help me?
I apologize if this isn't the right place for this question. Thank you for the many mods I have seen you do already. I look forward to trying them once I have a fallback plan.
--bornagainpenguin
PS: I am a new user here so not allowed to post links. I hope you got the idea of where I was trying to point you to.

bornagainpenguin said:
How is this comparable to the rom listed here?
....................................................................................................
PS: I am a new user here so not allowed to post links. I hope you got the idea of where I was trying to point you to.
Click to expand...
Click to collapse
I'm not actually sure what your talking about but I've posted this on three different sites so far. I do that for the guys that don't go to other forums. There probably isn't any difference in the roms.

Asadullah said:
I'm not actually sure what your talking about but I've posted this on three different sites so far. I do that for the guys that don't go to other forums. There probably isn't any difference in the roms.
Click to expand...
Click to collapse
I'm talking about the one by takehull posted on sdx-developers here.
Yours is not exactly stock since you added su and flash_image binaries--or does that really not matter?
Thanks for the reply.
--bornagainpenguin
PS: I appreciate that you try to post your work as far and wide as possible, it made it easier for me to find it.
PPS: Which forum is best to follw for work relating to the LG Optimus V?

For the record, I like it as is.
Saves me the trouble of having to root all over again.
Sent from my VM670 using XDA App

I'm not sure exactly how his is different since I didn't build it. I'm gonna guess and say his probably doesn't have the binaries in it, I'm not sure exactly how his is different since I didn't build it. I'm gonna guess and say that his doesn't have the binaries in it. I don't know. Honestly the only way to know for sure that it's stock rom is to get someone that hasn't rooted yet flash the recovery and get a backup of system. I've been waiting for someone like that to come along but ... It hasn't happened yet.
I won't tell you which forums to watch but I'm partial to xda cuz I been on here since my first android phone and it doesn't have those flash ads that pop up cover your entire screen until you click the x.

Asadullah said:
I'm not sure exactly how his is different since I didn't build it. I'm gonna guess and say that his doesn't have the binaries in it. I don't know.
Click to expand...
Click to collapse
Well upon further re-reading the other thread I saw this posted:
takehull said:
The only modifications this has are the two binaries that you put into /system/bin when you root. You can remove them by using Superoneclick Root and selecting "unroot."
Click to expand...
Click to collapse
My only excuse is that it was late when I found the thread and I wasn't reading clearly. Going by that statement his rom and your rom basically seem to be the same things.
Asadullah said:
Honestly the only way to know for sure that it's stock rom is to get someone that hasn't rooted yet flash the recovery and get a backup of system. I've been waiting for someone like that to come along but ... It hasn't happened yet.
Click to expand...
Click to collapse
Forgive my ignorance, but isn't rooting actually a requirement of obtaining the backup? Or did I misread the instructions somewhere? It'd be nice if someone at Virgin Mobile were to leak the complete rom somewhere so people had a fall back option besides trying to return the phone as bricked. (If that's even possible?)
Asadullah said:
I won't tell you which forums to watch but I'm partial to xda cuz I been on here since my first android phone and it doesn't have those flash ads that pop up cover your entire screen until you click the x.
Click to expand...
Click to collapse
Sounds like a good reason to pick a forum. Not sure if I'm a member of any places that do that since I run with adblock and noscript enabled most of the time.
Any chance you could link me to written instructions on how to flash the rom you have here? I know you have video tutorials but those are harder to follow for me because I am hard of hearing. Music I can do because it is "beautiful noise" and I can usually find some lyrics to get the words of. Your video HOWTOs are not good for me because I have to strain to hear what is being said.
Thanks again for your time and patience in replying to me.
--bornagainpenguin

Thanks. Dude above me, there is a rom flashing tutorial at prepaidandroids.net. We will help you out there. Its a site that specializes in on the Optimus v itself.
(Optimus V - Contracts Suck)

Thanks for posting this. It just came in handy when I was changing my virgin phone number. Part of the process is dialing ##841446# to bring up the activation menu, but the ## prefix on CM7 does not work, apparently only a stock ROM can do that.

Any way to put it on a phone friendly site? No matter what browser I use on my phone it will not download from google docs.
Sent from my VM670 using Tapatalk

THANKS, this worked perfectly.
It's pretty much as described, a stock Opt V rom, with Super User already set up and installed.
Titanium worked on it no problem as well.

thanks a ton man! i needed to flash back to stock to get my 3G working again. if you flash a custom rom while youre between payments, you know, during down time, you may need to flash back to stock and run the activation app next time you put service on your phone.
worked like a charm. i thought my 3G was broken. im doing a happy dance now!

Anyway I can get a link to the stock rom with all the bloatware removed but not rooted?

DarkLG said:
Anyway I can get a link to the stock rom with all the bloatware removed but not rooted?
Click to expand...
Click to collapse
Tell me what you consider bloatware and ill make it for you.

tvall said:
Tell me what you consider bloatware and ill make it for you.
Click to expand...
Click to collapse
Well those apps that come preinstalled like the virgin radio and such .If you could add in the newest market,g+,music I would greatly appreciate it

DarkLG said:
Well those apps that come preinstalled like the virgin radio and such .If you could add in the newest market,g+,music I would greatly appreciate it
Click to expand...
Click to collapse
Zipping, will flash and test then upload.
Its just de-bloated. Nothing added (yet)
http://db.tt/fsvq1JB6
Haven't tested yet. I'm lazy

tvall said:
Zipping, will flash and test then upload.
Its just de-bloated. Nothing added (yet)
http://db.tt/fsvq1JB6
Haven't tested yet. I'm lazy
Click to expand...
Click to collapse
haha let me know normally I would do it myself the whole making and adding but everything java and android based don't woprk o my pc :/

ES file explorer is a great way to remove bloat from your phone

Am I safe to update to Kitkat?

I Got this phone in the mail off Ebay today. And within the first hour I updated it to 4.3 and rooted it. And now I'm getting another OTA update notification. I'm not new to rooting and stuff but I am new to Samsung. So I'm a little worried if I should do the update or not. I don't wanna get stuck in a bootloop or anything.
I'm rooted
I'm running 4.3
I have Clockwork flashed
Rom is stock
All I'd like to know is if I am safe to update? I heard you are and then I've heard you're not.

not sure but if you can unroot you can allways re root in 4.4

If no one else has done so yet, ive got a modded ota that should allow you to flash via cwm or twrp, and should preserve root.
Its uploading now.

DocHoliday77 said:
If no one else has done so yet, ive got a modded ota that should allow you to flash via cwm or twrp, and should preserve root.
Its uploading now.
Click to expand...
Click to collapse
Alright thanks! let me know when it's up. And are you from Huntsville Alabama too?

Ok, here is the modded OTA!
It should allow you to flash via TWRP or CWM recoveries, and it should also preserve root!
You will still need to be full stock for it to work as it still will go through its checks before flashing. It is not recommended to remove these checks because it could cause problems when patching files. Especially if the files being patched have been modded.
THIS IS UNTESTED! I do not have a working device at the moment, (dont have the I747 anyway), so I am unable to test on my own before releasing. I do not foresee any problems, but there just is no way to be positive until its been tried. If there is an issue, it should still just fail before the flash like it always has been supposed to do.
Please post back ASAP after trying this out so we know if it is working or not.
Modded_OTA_UCUEMJB-UCUFNE4.zip
Hope this proves helpful for some of you!
Doc

DocHoliday77 said:
Ok, here is the modded OTA!
It should allow you to flash via TWRP or CWM recoveries, and it should also preserve root!
You will still need to be full stock for it to work as it still will go through its checks before flashing. It is not recommended to remove these checks because it could cause problems when patching files. Especially if the files being patched have been modded.
THIS IS UNTESTED! I do not have a working device at the moment, (dont have the I747 anyway), so I am unable to test on my own before releasing. I do not foresee any problems, but there just is no way to be positive until its been tried. If there is an issue, it should still just fail before the flash like it always has been supposed to do.
Please post back ASAP after trying this out so we know if it is working or not.
Modded_OTA_UCUEMJB-UCUFNE4.zip
Hope this proves helpful for some of you!
Doc
Click to expand...
Click to collapse
I would test it but I just can't. I'm pretty sure it wouldn't break anything. But I haven't had this phone for 24 hours yet, I just bought it and it's the only one I got. I even paid my bill today too. And I'm looking for another job and you have to have a phone for that lol. Post it up on the forum and let someone who knows more than I do test it because I'm just gonna have to wuss out on this one. I appreciate it though!:good::good:

No sweat. I completely understand! I may go ahead and make a thread for it, but was hoping to verify it works first. Ill post it in the other ota thread for now.
And yes, I am close to Huntsville. Good luck on your job hunt!

Questions and Help issues belong in Q&A and Help section..thanks
Thread moved
FNSM

[Q] T-Mobile/other Snapdragon roms on Verizon DE

I've been considering the DE for a while, and I know a few devs are working on roms for it, but I can't help but drool with jealousy when I see the development going on for other carriers, particularly t-mobile.
Seeing as how the Verizon DE model is basically the same as the other Snapdragon versions aside from the radio, would it be possible to flash those roms onto the DE and then flash the Verizon DE radio over it? If not, is there another viable method?
Sent from my SM-N900V using Tapatalk

jerkface80 said:
I've been considering the DE for a while, and I know a few devs are working on roms for it, but I can't help but drool with jealousy when I see the development going on for other carriers, particularly t-mobile.
Seeing as how the Verizon DE model is basically the same as the other Snapdragon versions aside from the radio, would it be possible to flash those roms onto the DE and then flash the Verizon DE radio over it? If not, is there another viable method?
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
I'm also curious about this , have you found out anything?

Unfortunately not. If I do, I'll be sure to post here.
Sent from my SM-N900V using Tapatalk

The dev for FireKat (T-Mobile) is building his ROM with the Verizon base for us...should be a few more days. If you end up using it be sure to thank/donate...he has done some great stuff so far and his support will be huge for us.

Firekat V7 is available for the VZW Developer Edition
A version of FireKat using the NJ5 Verizon base is now available in the T-mobile forum - http://forum.xda-developers.com/not.../firekatn4v1-4-4-4-tw-anj7-extremely-t2916463
The Dev (Megalomanic14) is very responsive but has been very clear that the ROM will not be cross posted in this forum and that VZW users should not post any VZW related questions in the T-mobile forum to avoid confusion.
He will respond to PMs but to help avoid him being inundated, below are the steps I took which worked perfectly. He recommends clean app installs and not TiBu restores to avoid problems with corrupt data. I selectively restored a few apps from TiBu and it was fine, but do that at your own risk and if you have issues that is probably the culprit.
If you use his ROM be sure to thank and if possible donate as this ROM rocks and his continued support would be great for us, especially for Lollipop someday.
1. Find the link for the VZW version FK7 towards the end of the post 3 in the thread above, download and put it on your External SD
2. Odin the NJ5 base (if you are still on AN1, if not, skip to step 5)
3. Odin TWRP
4. Flash SU in TWRP
5. Wipe cache, dalvik, system and data
6. Flash FK7
7. Wipe cache, dalvik (for good measure)
8. Reboot
9. Be patient
10. Follow instructions in 2nd post in the TMO ROM thread to optimize performance if you want

tfly212 said:
A version of FireKat using the NJ5 Verizon base is now available in the T-mobile forum - http://forum.xda-developers.com/not.../firekatn4v1-4-4-4-tw-anj7-extremely-t2916463
The Dev (Megalomanic14) is very responsive but has been very clear that the ROM will not be cross posted in this forum and that VZW users should not post any VZW related questions in the T-mobile forum to avoid confusion.
He will respond to PMs but to help avoid him being inundated, below are the steps I took which worked perfectly. He recommends clean app installs and not TiBu restores to avoid problems with corrupt data. I selectively restored a few apps from TiBu and it was fine, but do that at your own risk and if you have issues that is probably the culprit.
If you use his ROM be sure to thank and if possible donate as this ROM rocks and his continued support would be great for us, especially for Lollipop someday.
1. Find the link for the VZW version FK7 towards the end of the post 1 in the thread above, download and put it on your External SD
2. Odin the NJ5 base (if you are still on AN1, if not, skip to step 5)
3. Odin TWRP
4. Flash SU in TWRP
5. Wipe cache, dalvik, system and data
6. Flash FK7
7. Wipe cache, dalvik (for good measure)
8. Reboot
9. Be patient
10. Follow instructions in 2nd post in the TMO ROM thread to optimize performance if you want
Click to expand...
Click to collapse
Thanks for your work in guiding the dev to include our phone. One note, the download is actually in post #3 of that thread.

azumandias said:
Thanks for your work in guiding the dev to include our phone. One note, the download is actually in post #3 of that thread.
Click to expand...
Click to collapse
No worries...happy to share the love.
Updated my post to refect that the ROM is in post 3 of the TMO thread. Good catch.

Just a reminder on Firekat...
The developer has requested that no one post Verizon questions in the TMO forum (and of course someone ignored this). There is probably no quicker way to get him to stop supporting a carrier that he doesn't even use so for the sake of the others that want to take advantage of his ROMs, please follow his guidelines.

Is there a risk in upgrading to NJ5? Where did you get this file from?

I followed the instructions from the Defininitve ROM update. You need to use Odin but it was really easy. I also backed up my aboot beforehand just in case.
http://forum.xda-developers.com/showthread.php?t=2975372
Aboot backup - http://forum.xda-developers.com/showthread.php?t=2962911

tfly212 said:
I followed the instructions from the Defininitve ROM update. You need to use Odin but it was really easy. I also backed up my aboot beforehand just in case.
http://forum.xda-developers.com/showthread.php?t=2975372
Aboot backup - http://forum.xda-developers.com/showthread.php?t=2962911
Click to expand...
Click to collapse
I wonder if we could start a thread about the ROM in our general section? Maybe you could check with the or? Regardless, I'll be trying this out tomorrow. Thanks for sharing.
Sent from my SM-N910V using Tapatalk

icon123 said:
I wonder if we could start a thread about the ROM in our general section? Maybe you could check with the or? Regardless, I'll be trying this out tomorrow. Thanks for sharing.
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
I thought about that but felt it might be better just to use this thread as the support is "unofficial". A dedicated thread might make the dev feel like he has to monitor it.
Good luck with the flash...you will dig this ROM. If you have any questions let me know.

Having trouble flashing this ROM
I've followed all of the steps, am on J5, but once it reboots, it just keeps restarting(well not exactly restarting, but the "Samsung GALAXY Note 4" screen keeps restarting. Never encountered that when flashing ROMs on other phones in the past so I don't know if this is what it is supposed to be doing lol). I gave it over thirty minutes twice and still nothing. The MD5 matches and I've tried multiple downloads. Does it just take much longer than fifteen minutes to install? I reflashed the Stock Restore with Odin, then rooted it along with flash the J5 modem and kernel just to be sure, but it still was taking over 30 minutes before I gave up. I have no clue what I'm missing or doing wrong.
EDIT: Nevermind! I'm almost certain that I didn't download the RIGHT one. I feel so idiotic now. Should NEVER try to do stuff like this when you are half asleep at night!!

azumandias said:
Thanks for your work in guiding the dev to include our phone. One note, the download is actually in post #3 of that thread.
Click to expand...
Click to collapse
Wish I'd read this before I initially tried it. Even though I SHOULD have known better (I was half asleep - seriously bad way to be when doing something like this, but it is still humiliating that I made this blunder), I downloaded the T-Mobile version and tried to flash it. I'm incredibly lucky I didn't brick or really screw up my phone. Thankfully, I was able to get back into recovery and restore my previous backup. Now on the VERIZON version of this ROM.

icon123 said:
I wonder if we could start a thread about the ROM in our general section? Maybe you could check with the or? Regardless, I'll be trying this out tomorrow. Thanks for sharing.
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
I messaged the ROM dev last week and he does not want any threads started for his ROM at all.

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.

google pixel xl build #NKG47L

HI,
I purchased a google pixel xl, the bootloader is currently locked I would like to unlock and root if possible. the phone is running android 7.1.2 build NKG47L. Ive searched youtube, and xda for means of rooting, etc but im not having any luck on finding what would help me.. so some help would be greatly appreciated

https://forum.xda-developers.com/pixel-xl/how-to/index-google-pixel-xl-t3466185

Hopefully you don't have the Verizon version of the Pixel XL.. If you do unlocking the bootloader is impossible. If you don't then flashing and rooting the Pixel XL is possible but unusually difficult. The instructions seem to change from month to month and you need to use a specially modified version of Magisk because the official one doesn't work on the Pixel. If you go the SuperSu route they do have an official version for the Pixel. I've been flashing for years and it pretty much took me an entire day to successfully flash a custom recovery, a custom rom, a custom kernel, root with Magisk and get the phone to pass safety net. I've never owned a phone that was such a headache to flash on. Good luck.

jhs39 said:
Hopefully you don't have the Verizon version of the Pixel XL.. If you do unlocking the bootloader is impossible. If you don't then flashing and rooting the Pixel XL is possible but unusually difficult. The instructions seem to change from month to month and you need to use a specially modified version of Magisk because the official one doesn't work on the Pixel. If you go the SuperSu route they do have an official version for the Pixel. I've been flashing for years and it pretty much took me an entire day to successfully flash a custom recovery, a custom rom, a custom kernel, root with Magisk and get the phone to pass safety net. I've never owned a phone that was such a headache to flash on. Good luck.
Click to expand...
Click to collapse
Because you are having a hard time doesn't mean everyone will. Literally every chance you get you have to post the exact same narrative about how hard this is. It's like you are trying to poison other people's experiences because you find this so difficult. Let OP form their own opinion because frankly there are tons of users having zero issues rooting romming and etc..
Good Lord.

pcriz said:
Because you are having a hard time doesn't mean everyone will. Literally every chance you get you have to post the exact same narrative about how hard this is. It's like you are trying to poison other people's experiences because you find this so difficult. Let OP form their own opinion because frankly there are tons of users having zero issues rooting romming and etc..
Good Lord.
Click to expand...
Click to collapse
I think anyone who claims it's easy to flash on this phone is being unrealistic and dishonest. Most posts I read from flashers on XDA involving this phone are from people who had trouble flashing or were unsuccessful and are stuck somewhere and looking for a way to recover. Problems getting TWRP to work are very common. Problems with people who don't realize they can't use a non-modified version of Magisk are very common. It doesn't help that there isn't a good clear up to date flashing guide for the phone anywhere on XDA or that you have to go from thread to thread to find the files you need to flash or that the download shortcuts and discussion for the Pixel XL modified version of Magisk are actually buried in the Resurrection Remix thread where nobody would​ logically think to look for them.
I'm not the one who made it hard to flash on this phone--Google did, and people like you don't help matters. If you are such an expert on flashing on this phone do something more constructive than criticizing me for being honest--create a thread that includes clear and up to date instructions for how to flash on the Pixel XL and which includes shortcuts for all the files a person would typically need. And keep the instructions up to date when a Google security patch changes the flashing procedure or files needed.
You claim its easy to flash on this phone. If it's so easy for you then share your expertise with everybody else. If you are unwilling to do that you are just wasting everybody's time by being wildly dishonest about the difficulties people very frequently face when they try to flash on the Pixel XL.
I have been flashing on Android phones for years and I stand by what I said--I've never encountered a phone that was such a headache to flash on.

jhs39 said:
I think anyone who claims it's easy to flash on this phone is being unrealistic and dishonest. Most posts I read from flashers on XDA involving this phone are from people who had trouble flashing or were unsuccessful and are stuck somewhere and looking for a way to recover. Problems getting TWRP to work are very common. Problems with people who don't realize they can't use a non-modified version of Magisk are very common. It doesn't help that there isn't a good clear up to date flashing guide for the phone anywhere on XDA or that you have to go from thread to thread to find the files you need to flash or that the download shortcuts and discussion for the Pixel XL modified version of Magisk are actually buried in the Resurrection Remix thread where nobody would​ logically think to look for them.
I'm not the one who made it hard to flash on this phone--Google did, and people like you don't help matters. If you are such an expert on flashing on this phone do something more constructive than criticizing me for being honest--create a thread that includes clear and up to date instructions for how to flash on the Pixel XL and which includes shortcuts for all the files a person would typically need. And keep the instructions up to date when a Google security patch changes the flashing procedure or files needed.
You claim its easy to flash on this phone. If it's so easy for you then share your expertise with everybody else. If you are unwilling to do that you are just wasting everybody's time by being wildly dishonest about the difficulties people very frequently face when they try to flash on the Pixel XL.
I have been flashing on Android phones for years and I stand by what I said--I've never encountered a phone that was such a headache to flash on.
Click to expand...
Click to collapse
Not claiming it's easy. Just saying it gets repetitive to see you in how many threads griping about how this is such an insurmountable task.
And of course you see people with issues. Why do I need to comment that I'm not having issues. Heck when someone does comment that they aren't having issues you refute that because you are having a hard time.
You say I should be more constructive, lol please please please read my post history and maybe you will see how many people I have made efforts to help. I've been helping people in the forum, I've been helping people on Reddit, I've been helping people on discord, irc, etc etc. I've turned down money for helping people. How many people have you helped? How have you paid forward any help you have gotten on the pixel? Hell I even told you why you couldn't flash twrp after you downgraded from the O beta. So please don't tell me about being constructive bro.
"Flashing on Android for years" means nil my friend. Maybe if you took the time to understand the device it wouldn't be so difficult.
Do you even know why you couldn't flash twrp? It's because the OTAs flash to the opposite slot so when you got the ota for Android N from O N flashed in the other slot.
TWRP patches both boot.imgs but now your inactive boot.img is incompatible with twrp so it hangs up.
Super simple fix, now that you know there are two slots. You figure out how to swap slots at the bootloader. Then you learn how to flash all and flash all in both slots
Then you get a light that goes off because you took the time to read how twrp works in it's thread and realize you don't even need to flash all. You could simply flash the boot img in both slots. Because if you know what twrp patches then you know exactly what files you need.
I've been flashing for years also but I'm humble enough to know I should read before crying to people that are doing it without issue.
As far as the magisk "issue", well if anyone took the time to go to the magisk thread they would see the device isn't officially supported. Who's fault is it you didn't do that?
What was stopping you from searching the magisk thread before you started? I mean obviously you ignored where it stated it's not supported.
You can lead a horse to water my man. Can't make him drink.

jhs39 said:
I think anyone who claims it's easy to flash on this phone is being unrealistic and dishonest. Most posts I read from flashers on XDA involving this phone are from people who had trouble flashing or were unsuccessful and are stuck somewhere and looking for a way to recover. Problems getting TWRP to work are very common. Problems with people who don't realize they can't use a non-modified version of Magisk are very common. It doesn't help that there isn't a good clear up to date flashing guide for the phone anywhere on XDA or that you have to go from thread to thread to find the files you need to flash or that the download shortcuts and discussion for the Pixel XL modified version of Magisk are actually buried in the Resurrection Remix thread where nobody would​ logically think to look for them.
I'm not the one who made it hard to flash on this phone--Google did, and people like you don't help matters. If you are such an expert on flashing on this phone do something more constructive than criticizing me for being honest--create a thread that includes clear and up to date instructions for how to flash on the Pixel XL and which includes shortcuts for all the files a person would typically need. And keep the instructions up to date when a Google security patch changes the flashing procedure or files needed.
You claim its easy to flash on this phone. If it's so easy for you then share your expertise with everybody else. If you are unwilling to do that you are just wasting everybody's time by being wildly dishonest about the difficulties people very frequently face when they try to flash on the Pixel XL.
I have been flashing on Android phones for years and I stand by what I said--I've never encountered a phone that was such a headache to flash on.
Click to expand...
Click to collapse
It's "extremely easy" to flash on this phone. It's the hacking and deving thats hard. Give me a zip that works and a functioning Twrp, it will be like taking candy from a baby. Yeah, and Google's not helping any of us.

Well THAT escalated quickly...
Sent from my SM-N910V using Tapatalk

Thanks for the help. I have been able to get the phone rooted, etc but I can't get TWRP recovery to stick. But do I have to reflash TWRP recovery after I flash SU files for root?

yamaha_wins said:
Thanks for the help. I have been able to get the phone rooted, etc but I can't get TWRP recovery to stick. But do I have to reflash TWRP recovery after I flash SU files for root?
Click to expand...
Click to collapse
I had to boot into my rom once, go back into fastboot TWRP and then flash the TWRP zip again in order to get it to stick.

@jhs39 and @pcriz, you're both correct in this matter and hopefully you all can just agree to disagree. I agree with you both, if you're a flasher like most of us and I too have been flashing for years. In fact about 90% of the phones I've owned have all been flashed and I average about two phones per year. That said I'm not expert and do find some things harder here and there but I'm techie enough to work through it with help from members of this forum. @pcriz I've used many of your instructions and assistants on this thread so thank you! I too believe flashing on the pixel has been very difficult mainly because the device changed the way things usually worked (slots etc.). I can't remember the last time it took me hours to flash a simple ROM. After I learned a little bit of what was going on with TWRP and the whole slot A/B configurations I was able to at least troubleshoot my own issues and get things working a little better. I would say anyone having issues need to take the time to really read and understand the device because they don't function the say as before. The instructions do change because Google changes things up. Manufactures don't want us flashing any more and with security being a top priority flashing is quickly being discouraged.
I've gotten to the point now where I just want to get my pixel which is no longer my daily driver (my S8 plus is) to stock but even that isn't working. I've tried numerous times to flash an image and it fails every single time. Why????? I have come to love a stock experience even though I still love the customization you get with a custom ROM. If I were to pick right now I'll just stick with stock; if I can ever get the phone to flash the stupid image so I can try Android O lol.