I have an att s8+ build g55USQU1AQJC, is this still root able without tripping Knox?
Will flashing the Odin files wipe my phone?
Has the 80% battery bug been fixed or is it just visual and not have any impact on battery life?
Last question when the new bootloader gets released on my device will that affect root?
You can't root without tripping Knox.
Yes, you will wipe your phone, probably twice, in the process of installing root.
80% bug has not been fixed. Probably won't be. It does have an impact. How much depends on your usage habits.
Until the devs get a hold of V3, that's hard to say. Most likely it will not be rootable for, at least, a little while. You won't be able to OTA anyway.
Anyone is more than welcome to correct me, if I got any of that incorrect. Been a few since I've combed through all the pertinent threads.
Thanatos355 said:
You can't root without tripping Knox.
Yes, you will wipe your phone, probably twice, in the process of installing root.
80% bug has not been fixed. Probably won't be. It does have an impact. How much depends on your usage habits.
Until the devs get a hold of V3, that's hard to say. Most likely it will not be rootable for, at least, a little while. You won't be able to OTA anyway.
Anyone is more than welcome to correct me, if I got any of that incorrect. Been a few since I've combed through all the pertinent threads.
Click to expand...
Click to collapse
I thought I read somewhere samfail root won't trip Knox.
MysticFTW said:
I thought I read somewhere samfail root won't trip Knox.
Click to expand...
Click to collapse
I have the same model device as you. Straight from AT&T, part of their pre-order deal, fwiw. I've used both methods for root, and can confirm that things that use Knox (e.g. Samsung Pay) both detects root and refuses to function thereafter.
Thanatos355 said:
I have the same model device as you. Straight from AT&T, part of their pre-order deal, fwiw. I've used both methods for root, and can confirm that things that use Knox (e.g. Samsung Pay) both detects root and refuses to function thereafter.
Click to expand...
Click to collapse
What your describing is normal of any root but I'm asking about Knox warranty status.
Can you boot to download mode to check Knox status?
Here is a tutorial if you don't how to check knox
https://www.google.com/amp/s/www.androidexplained.com/galaxy-s8-check-knox/amp/
MysticFTW said:
What your describing is normal of any root but I'm asking about Knox warranty status.
Can you boot to download mode to check Knox status?
Here is a tutorial if you don't how to check knox
https://www.google.com/amp/s/www.androidexplained.com/galaxy-s8-check-knox/amp/
Click to expand...
Click to collapse
My mistake, I thought you meant from a usability standpoint. No, the fuse itself has not been tripped. I just rechecked mine to make sure, 0x0.
Thanatos355 said:
My mistake, I thought you meant from a usability standpoint. No, the fuse itself has not been tripped. I just rechecked mine to make sure, 0x0.
Click to expand...
Click to collapse
Awesome I didn't want to risk if it tripped Knox.
How noticeable is having only 80% battery on a daily basis?
MysticFTW said:
Awesome I didn't want to risk if it tripped Knox.
How noticeable is having only 80% battery on a daily basis?
Click to expand...
Click to collapse
Honestly, not that bad. I almost always still make it through a full day, 7am-11pm or so, of use before I plug it in. I read on it extensively, text and message regularly, and play a few different games on it, that I launch every hour or two.
I did have a problem with battery life, at first, with Pwn, but had zero issues with Fail, and ended up going back to Pwn with no issues at all.
Thanatos355 said:
Honestly, not that bad. I almost always still make it through a full day, 7am-11pm or so, of use before I plug it in. I read on it extensively, text and message regularly, and play a few different games on it, that I launch every hour or two.
I did have a problem with battery life, at first, with Pwn, but had zero issues with Fail, and ended up going back to Pwn with no issues at all.
Click to expand...
Click to collapse
Why did you go back?
Sorry to be asking so many questions I just wanna cover my bases.
Messing around with Substratum late one night, screwed things up (totally on me, I knew the risks), and decided to try Pwn again. I had been wanting to see if the battery issue was a fluke. All in all, I vastly prefer PartyCyborg's rom, but not enough to immediately switch back. I figure when he drops the next release, I'll switch back.
Thanatos355 said:
Messing around with Substratum late one night, screwed things up (totally on me, I knew the risks), and decided to try Pwn again. I had been wanting to see if the battery issue was a fluke. All in all, I vastly prefer PartyCyborg's rom, but not enough to immediately switch back. I figure when he drops the next release, I'll switch back.
Click to expand...
Click to collapse
Ok I plan to substratum as well
Is this rom? https://www.google.com/amp/s/forum....ntroducing-samfail-root-sm-g950-t3685349/amp/
MysticFTW said:
Ok I plan to substratum as well
Is this rom? https://www.google.com/amp/s/forum....ntroducing-samfail-root-sm-g950-t3685349/amp/
Click to expand...
Click to collapse
That one is in the S8 forum. This is the one I used.
https://forum.xda-developers.com/ga...root-partcyborgrom-aqk3-samfail-odin-t3717702
Thanatos355 said:
That one is in the S8 forum. This is the one I used.
https://forum.xda-developers.com/ga...root-partcyborgrom-aqk3-samfail-odin-t3717702
Click to expand...
Click to collapse
Oh ok thanks you just save me trouble.
Which one do I need G955USQU2BQK5 or G955USQU1AQK3
Will it matter that my stock build version is g55USQU1AQJC
MysticFTW said:
Oh ok thanks you just save me trouble.
Which one do I need G955USQU2BQK5 or G955USQU1AQK3
Will it matter that my stock build version is g55USQU1AQJC
Click to expand...
Click to collapse
I'm honestly not sure on that point. Your best bet is to read the entire first post, and if that doesn't answer your questions, search the thread.
Thanatos355 said:
I'm honestly not sure on that point. Your best bet is to read the entire first post, and if that doesn't answer your questions, search the thread.
Click to expand...
Click to collapse
10 pages in Sar far no one has mentioned which file to download
I'm not really sure, man. I know that one was from v2 and one is from v1. I'm still on v1 bootloader and I used the original v1 rom, which was the AQK3 files.
Thanatos355 said:
I'm not really sure, man. I know that one was from v2 and one is from v1. I'm still on v1 bootloader and I used the original v1 rom, which was the AQK3 files.
Click to expand...
Click to collapse
Ok well I posted in the thread hopefully I'll get an answer soon
Thank you for your help ?
Thanatos355 said:
I'm not really sure, man. I know that one was from v2 and one is from v1. I'm still on v1 bootloader and I used the original v1 rom, which was the AQK3 files.
Click to expand...
Click to collapse
How do I know if I'm on v1 bootloader?
is this root bug with all variants uk and us ive got the sm-g955f will i get this 80% bug if i root
Related
Does the Tizen Mod rom make a big difference in functionality?
Does this void my warranty? I'm stupid, so I'll be surfing with the Gear 2 and worried if I ever have to repair it.
Is there a Google Now search hack out? SVoice doesn't seem to work good for word definitions among other things.
Thanks!
kronium said:
Does the Tizen Mod rom make a big difference in functionality?
Does this void my warranty? I'm stupid, so I'll be surfing with the Gear 2 and worried if I ever have to repair it.
Is there a Google Now search hack out? SVoice doesn't seem to work good for word definitions among other things.
Thanks!
Click to expand...
Click to collapse
Tizen Mod offers a lot of custom features you won't find right out of the box. Provides better battery life and a few other hacks. I don't believe this will void warranty as you can go right back to stock via Odin and haven't seen a trip counter, knox, etc.
quickbird144 said:
Tizen Mod offers a lot of custom features you won't find right out of the box. Provides better battery life and a few other hacks. I don't believe this will void warranty as you can go right back to stock via Odin and haven't seen a trip counter, knox, etc.
Click to expand...
Click to collapse
As I've said on the other thread there's definitely a counter of some sort. Whether Samsung pays attention to it or nor is another story.
javispedro said:
As I've said on the other thread there's definitely a counter of some sort. Whether Samsung pays attention to it or nor is another story.
Click to expand...
Click to collapse
How do you know there's a counter?
kronium said:
How do you know there's a counter?
Click to expand...
Click to collapse
strace /usr/bin/cordon_server . I've found it writes to the param partition all while logging scary things such as "device has been ROOTED" (caps included). It also links with OpenSSL.
(And I suspect that there may be some, slightly more hidden 'tricks').
javispedro said:
strace /usr/bin/cordon_server . I've found it writes to the param partition all while logging scary things such as "device has been ROOTED" (caps included). It also links with OpenSSL.
(And I suspect that there may be some, slightly more hidden 'tricks').
Click to expand...
Click to collapse
Interesting. I can no long pair my gear 2 with my s4. Do you have a link to the stock firmware Odin file? I want to revert back to stock to see if I can pair my watch with my phone again.
RJV3 said:
Interesting. I can no long pair my gear 2 with my s4. Do you have a link to the stock firmware Odin file? I want to revert back to stock to see if I can pair my watch with my phone again.
Click to expand...
Click to collapse
I obviously cannot redistribute firmware files. Either way reflashing stock firmware won't reset the counter. But I doubt the counter would be causing pairing issues to begin with.
javispedro said:
I obviously cannot redistribute firmware files. Either way reflashing stock firmware won't reset the counter. But I doubt the counter would be causing pairing issues to begin with.
Click to expand...
Click to collapse
Ok so I was able to download the stock firmware from sammobile. Just needed to sign up to download. But since then I still cannot pair my gear 2 with my phone and have no clue what can be causing this issue.
I have unrooted and reverted back to stock gear 2...no go.
I have uninstalled xposed framework, wiped delvik cache and cache....no go.
I have no idea how to get this up and running again and this watch is only 1 month old.
How can i figure out why the bluetooth pairing is not working anymore. The pairing sequence just hangs and later says" Failed to Connect to your gear via Gear manager. Refer to Manual for more information."
someone please tell me what am I doing wrong or what the hell is going on with this damn device. I am at my wits end with this.
This is offtopic,..
RJV3 said:
Ok so I was able to download the stock firmware from sammobile. Just needed to sign up to download. But since then I still cannot pair my gear 2 with my phone and have no clue what can be causing this issue..
Click to expand...
Click to collapse
If you've reflashed the Gear plus reverted to factory settings, the the answer regarding what is causing your issue is clear: your phone.
javispedro said:
This is offtopic,..
If you've reflashed the Gear plus reverted to factory settings, the the answer regarding what is causing your issue is clear: your phone.
Click to expand...
Click to collapse
I'm reading other users have the same issue. But yes this is off topic and started a thread to troubleshoot.
I made the mistake of installing the most recent system update to change my baseband to G920VVRU2AOF1 and I tried re-rooting using ping-pong root and it won't let me install the su binary. I tried downgrading to OE2 using Odin, but that was a fail. Someone please help!!
deliberate.dev said:
I made the mistake of installing the most recent system update to change my baseband to G920VVRU2AOF1 and I tried re-rooting using ping-pong root and it won't let me install the su binary. I tried downgrading to OE2 using Odin, but that was a fail. Someone please help!!
Click to expand...
Click to collapse
It sounds like Verizon is up to their old tricks and preventing rollback by incrementing the bootloader again. Sadly you are stuck with no way to root if you can not flash back. All you can do is try submitting your info to the pingpong root thread and hope they can root it.
deliberate.dev said:
I made the mistake
Click to expand...
Click to collapse
Not sure why you upgraded??
There is no root for the VZW version of the phone for that or newer versions now.
Pingpong will NEVER work again since its method of exploit was patched.
Most likey, another root method will come up but most likey will trip KNOX.
This is why they have been saying, DON'T UPGRADE OR TAKE A NEW OTA, but some people don't read or follow instructions. It is and has been on the pingpong root first post for some time.
krelvinaz said:
Not sure why you upgraded??
There is no root for the VZW version of the phone for that or newer versions now.
Pingpong will NEVER work again since its method of exploit was patched.
Most likey, another root method will come up but most likey will trip KNOX.
This is why they have been saying, DON'T UPGRADE OR TAKE A NEW OTA, but some people don't read or follow instructions. It is and has been on the pingpong root first post for some time.
Click to expand...
Click to collapse
Plus when the new version is rootable by a custom ROM you still won't be able to downgrade. That leaves the high possibility to loose root when something goes wrong and you have to Odin back to stock. Hopefully 5.1.x will be able to roll back, if not I won't upgrade.
krelvinaz said:
Not sure why you upgraded??
There is no root for the VZW version of the phone for that or newer versions now.
Pingpong will NEVER work again since its method of exploit was patched.
Most likey, another root method will come up but most likey will trip KNOX.
This is why they have been saying, DON'T UPGRADE OR TAKE A NEW OTA, but some people don't read or follow instructions. It is and has been on the pingpong root first post for some time.
Click to expand...
Click to collapse
Not sure why I upgraded either. Didn't research the consequences. It was an impulsive decision. I'm pissed I can't root my damn phone, can't even flash one of my backups.
I skim when I read the threads, and then my terrible memory gets me in situations like this.
Ugh, I need an App dev to make a new rooting app.
Just read the ping pong root thread... I'm a dumbass. :/
Misterxtc said:
Plus when the new version is rootable by a custom ROM you still won't be able to downgrade. That leaves the high possibility to loose root when something goes wrong and you have to Odin back to stock. Hopefully 5.1.x will be able to roll back, if not I won't upgrade.
Click to expand...
Click to collapse
This upgrade s!#t is exactly that, [email protected]#t!! Don't upgrade. If they're not letting us downgrade with this upgrade, they're surely not going to let us downgrade with 5.1.x.
I'm still pissed. My battery is draining because of all the bloat that I can't manipulate if I were rooted. It's bugging the heck out of me not having full control of my phone.
Of course the upgrade wasn't good and why rooted users are not taking it.
You put you in the position you are in now. All the warnings were already there.
krelvinaz said:
Of course the upgrade wasn't good and why rooted users are not taking it.
You put you in the position you are in now. All the warnings were already there.
Click to expand...
Click to collapse
I'm the only one to blame, I'm already aware. Thanks! And I truly mean that.
Rule #1 is never ever take an OTA, just wait. I don't mean to throw salt on the wounds or anything but hopefully you'll save others from making the same mistake and I'm sure you won't make it again.
There's a lot of smart people working on this phone so don't give up hope just yet, you might catch a break. Heck, maybe a sock puppet will leak an unlocked bootloader like what happened with the S3. You never know.
s197 said:
Rule #1 is never ever take an OTA, just wait. I don't mean to throw salt on the wounds or anything but hopefully you'll save others from making the same mistake and I'm sure you won't make it again.
There's a lot of smart people working on this phone so don't give up hope just yet, you might catch a break. Heck, maybe a sock puppet will leak an unlocked bootloader like what happened with the S3. You never know.
Click to expand...
Click to collapse
Thanks, appreciate it. I guess this comes along with being a tester. I've got faith in the other developers who are working on it. I guess I'll just have to be patient.
Stay tuned...
Almost makes me want to cry.
Dont worry
deliberate.dev said:
Stay tuned...
Almost makes me want to cry.
Click to expand...
Click to collapse
Same thing happened to me, I stayed up all night trying to find a quick root, I dont care about messing with KNOX I just want my custom ROM back! But noooo there just isnt much variety I guess. Now I have to suffer because Verizon is lame.
almacd3571 said:
Same thing happened to me, I stayed up all night trying to find a quick root, I dont care about messing with KNOX I just want my custom ROM back! But noooo there just isnt much variety I guess. Now I have to suffer because Verizon is lame.
Click to expand...
Click to collapse
I feel somewhat relieved that I'm not alone on this. I've literally been screwing with my phone, Odin, and whatnot for hours trying to find a way of having somewhat control over this phone... obviously, to no avail. Tired of 'permission DENIED/Failed' prompts.
Same Here
deliberate.dev said:
I feel somewhat relieved that I'm not alone on this. I've literally been screwing with my phone, Odin, and whatnot for hours trying to find a way of having somewhat control over this phone... obviously, to no avail. Tired of 'permission DENIED/Failed' prompts.
Click to expand...
Click to collapse
Yea, Hopefully a fix soon, I looked around for boot unlockers as well, and did not find any. Man it wa easy with a nexus, they make it hard with Samsung!
almacd3571 said:
Yea, Hopefully a fix soon, I looked around for boot unlockers as well, and did not find any. Man it wa easy with a nexus, they make it hard with Samsung!
Click to expand...
Click to collapse
It's not so much Samsung's fault, it's our damn carrier, Verizon that's making phone manipulating harder. I've had the S2, two S3's, and an S4, and I've never had issues with unlocking, rooting, abusing them until I switched to Verizon and got the S6. These damn OTA's are unnecessary.
Your so true
It's not even that, but the lack of control and uselessness of the updates frustrate me, and probably alot of other people. Verizon needs to step it up. I actually work for Verizon. And let me tell you. They are sneaky. So many people come in about bills being overpriced or something. It's awful. Anyways. I have great faith in out moddkng community and their will be a fix soon!
Hi everyone! I just rooted...super excited now! A few questions....
1. How do I disable update prompt?
2. Can I delete bloatware by using Root Explorer app or should I move them to data first then uninstall?
3. I am looking through different threads and it looks like we still can't flash much due to locked bootloader, correct? I am still on 1AOC3 haha afraid to touch anything
Thank you in advance! Loving S6!!!
tats_06 said:
Hi everyone! I just rooted...super excited now! A few questions....
1. How do I disable update prompt?
2. Can I delete bloatware by using Root Explorer app or should I move them to data first then uninstall?
3. I am looking through different threads and it looks like we still can't flash much due to locked bootloader, correct? I am still on 1AOC3 haha afraid to touch anything
Thank you in advance! Loving S6!!!
Click to expand...
Click to collapse
Kinda curious... why did you post this to a thread about a problem "System Update won't let me downgrade or root." do you have that problem or are you just posting where ever feels good.
There are a lot of existing threads which cover what you are asking about.
Absolutely.... I posted because:
1. I searched and couldn't find a relevant thread on what I needed ...
2. I am 7 months pregnant and just love posting around random threads because it feels good.
Gee, thank you for being nice....
krelvinaz said:
Kinda curious... why did you post this to a thread about a problem "System Update won't let me downgrade or root." do you have that problem or are you just posting where ever feels good.
There are a lot of existing threads which cover what you are asking about.
Click to expand...
Click to collapse
Latest DPD1 6.0.1 MM Factory Tar Image
Full System Restore ImagesFully Stock Odin Factory Tar Image (Caution This Will Lock Your Bootloaders And Keep You From Downgrading To KitKat Firmwares)
6.0.1 MM VZW-G900VVRU2DPD1-20160511030450.zip
5.0 KK G900VVRU2BPB1_G900VVZW2BPB1_VZW.zip
5.0 KK G900VVRU2BOK3_G900VVZW2BOK3_VZW.zip
5.0 KK G900VVRU2BOG5_G900VVZW2BOG5_VZW.zip
Full System Restore Images With No Aboot Bootloader For Dev Unlocked Bootloaders
6.0.1 MM PD1_Full_Factory_Restore_No_Aboot.tar.zip
Firmware Only (Bootloader,Modem,Kernel,Recovery)
Modem OnlyVZW_BOK3_MODEM_NONHLOS_ONLY.tar.md5
VZW_BOK3_MODEM_ONLY.tar.md5
Kernel(Boot.img) OnlyVZW_BOK3_KERNEL_ONLY.tar.md5
For Dev. Ed. owners
Here is a full stock tar without the bootloader and without the recovery for Dev. Ed. owners
https://www.androidfilehost.com/?fid=24052804347794573
Just make sure you have SuperSU on your SD card to flash it in recovery after updating to re-root https://download.chainfire.eu/696/SuperSU
This is for Developer Edition owners only
jrkruse said:
BOG5 Factory Tar Images
Fully Stock Odin Factory Tar Image (Caution This Will Lock Your Bootloaders And Keep You From Downgrading To Obtain Root!!)
G900VVRU2BOG5_G900VVZW2BOG5_VZW.zip
Full Stock Odin Factory Tar Image With BOD5 Bootloaders (This Will Allow You To Still Downgrade To Earlier Builds)
VZW_BOG5_RETAIL_FULL_FIRMWARE_WITH_BOD5_BL.tar.zip
Click to expand...
Click to collapse
So if I am on Stock OE1 and flash the second link are you saying I can downgrade to root?
XNO said:
So if I am on Stock OE1 and flash the second link are you saying I can downgrade to root?
Click to expand...
Click to collapse
I'm wondering the same thing. It's been a while since I've heard anything about efforts to downgrade from OE1. I'm unrooted and would so desperately like to root, but unfortunately installed stock OE1 :crying:, and then OG5. I really really hope there will be some method of rooting in my situation. Hating the fact that I bought a device that I can't use the way I'd like because some screwball company thinks people are too stupid to be trusted.
I really appreciate everyone's efforts here. Keep up the wonderful work and keep us updated!
XNO said:
So if I am on Stock OE1 and flash the second link are you saying I can downgrade to root?
Click to expand...
Click to collapse
equazcion said:
I'm wondering the same thing. It's been a while since I've heard anything about efforts to downgrade from OE1. I'm unrooted and would so desperately like to root, but unfortunately installed stock OE1 :crying:, and then OG5. I really really hope there will be some method of rooting in my situation. Hating the fact that I bought a device that I can't use the way I'd like because some screwball company thinks people are too stupid to be trusted.
I really appreciate everyone's efforts here. Keep up the wonderful work and keep us updated!
Click to expand...
Click to collapse
Sorry guys! You can try but Im sure the tar image with the bod5 bootloaders will fail if your already on BOE1 or higher
jrkruse said:
Sorry guys! You can try but Im sure the tar image with the bod5 bootloaders will fail if your already on BOE1 or higher
Click to expand...
Click to collapse
Thanks I found out the hard way LOL. All good now tho.
XNO said:
So if I am on Stock OE1 and flash the second link are you saying I can downgrade to root?
Click to expand...
Click to collapse
I too am interested in this. I lost root and was hoping this version that Verizon installed today would allow me to re-root.
skister77 said:
I too am interested in this. I lost root and was hoping this version that Verizon installed today would allow me to re-root.
Click to expand...
Click to collapse
Oh dear lord, no no no no. Stop asking the same questions repeatedly hoping for a different answer. For the last time, if you are on oe1 and didn't keep the od bootloader, that's it, you're done.
And for the record, why would Verizon release an update that would re-allow to root? Why would that ever happen intentionally?
skister77 said:
I too am interested in this. I lost root and was hoping this version that Verizon installed today would allow me to re-root.
Click to expand...
Click to collapse
ldeveraux said:
Oh dear lord, no no no no. Stop asking the same questions repeatedly hoping for a different answer. For the last time, if you are on oe1 and didn't keep the od bootloader, that's it, you're done.
And for the record, why would Verizon release an update that would re-allow to root? Why would that ever happen intentionally?
Click to expand...
Click to collapse
To add to what ldeveraux wrote, your question was literally answered two posts above yours. Does anyone even bother to read anything anymore? Or is it that reading comprehension is completely a thing of the past?
ldeveraux said:
Oh dear lord, no no no no. Stop asking the same questions repeatedly hoping for a different answer. For the last time, if you are on oe1 and didn't keep the od bootloader, that's it, you're done.
And for the record, why would Verizon release an update that would re-allow to root? Why would that ever happen intentionally?
Click to expand...
Click to collapse
Stuff happens. Maybe somebody made a mistake.
Sent from my SM-G900V using XDA Free mobile app
DraconicSeed said:
Stuff happens. Maybe somebody made a mistake.
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
It's true that mistakes can happen, but once they patch the bootloader to prevent downgrading, they don't actually have to touch it again. So if they don't change anything in it, then the chance of breaking it is slim to none. Not to mention this update didn't do much anyways.
[/COLOR]
ldeveraux said:
Oh dear lord, no no no no. Stop asking the same questions repeatedly hoping for a different answer. For the last time, if you are on oe1 and didn't keep the od bootloader, that's it, you're done.
And for the record, why would Verizon release an update that would re-allow to root? Why would that ever happen intentionally?
Click to expand...
Click to collapse
So just to be clear Ideveraux, because I don't quite understand, are you saying OE1 is not rootable but OG5 has a chance?
Spartan117H3 said:
It's true that mistakes can happen, but once they patch the bootloader to prevent downgrading, they don't actually have to touch it again. So if they don't change anything in it, then the chance of breaking it is slim to none. Not to mention this update didn't do much anyways.
Click to expand...
Click to collapse
It involved a security update so I was hoping maybe someone messed up somewhere :silly: one can hope. I purchased my phone with OE1 already installed so I was kinda screwed from the ground up and going from an S4 rooted running TWRP and a Hyperdrive ROM to a stock unrooted bloated phone rubs me harsh lol
XNO said:
So just to be clear Ideveraux, because I don't quite understand, are you saying OE1 is not rootable but OG5 has a chance?
Click to expand...
Click to collapse
Anything OE1 or higher cannot be rooted. OG5 is higher than OE1, and therefore has the same issues for people who want to root that OE1 has. OE1 has a bootloader that disallows downgrading of firmware which is required to root these phones. The only way you can still downgrade OE1/OG5 is if you came from a rooted phone and did NOT take OTA OE1/OG5, and flashed a firmware that did not change the bootloader.
DraconicSeed said:
It involved a security update so I was hoping maybe someone messed up somewhere :silly: one can hope. I purchased my phone with OE1 already installed so I was kinda screwed from the ground up and going from an S4 rooted running TWRP and a Hyperdrive ROM to a stock unrooted bloated phone rubs me harsh lol
Click to expand...
Click to collapse
The stagefright that was incompletely patched was apparently 4 lines of code somewhere in one of the system files, wouldn't be in the bootloader. I understand the sentiments, I would have returned the phone immediately in your case. I'm already running out of patience even being rooted, with the locked bootloader and whatnot. Trying to patiently wait for the Nexus 6 2015 this year.
Spartan117H3 said:
Anything OE1 or higher cannot be rooted. OG5 is higher than OE1, and therefore has the same issues for people who want to root that OE1 has. OE1 has a bootloader that disallows downgrading of firmware which is required to root these phones. The only way you can still downgrade OE1/OG5 is if you came from a rooted phone and did NOT take OTA OE1/OG5, and flashed a firmware that did not change the bootloader.
The stagefright that was incompletely patched was apparently 4 lines of code somewhere in one of the system files, wouldn't be in the bootloader. I understand the sentiments, I would have returned the phone immediately in your case. I'm already running out of patience even being rooted, with the locked bootloader and whatnot. Trying to patiently wait for the Nexus 6 2015 this year.
Click to expand...
Click to collapse
Thanks Spartan, I'm just messing with ldeveraux because all i ever read from him is negative comments like he is super annoyed at everyone asking questions.
XNO said:
Thanks Spartan, I'm just messing with ldeveraux because all i ever read from him is negative comments like he is super annoyed at everyone REPEATING questions.
Click to expand...
Click to collapse
FTFY
XNO said:
Thanks Spartan, I'm just messing with ldeveraux because all i ever read from him is negative comments like he is super annoyed at everyone asking questions.
Click to expand...
Click to collapse
It has been repeated a million times though, in basically every "recent" thread so I can see why people would be frustrated. The issue is, the more people post the same questions, the more hidden the important questions get, leaving people even less likely to read/search the thread for their answers. Just basic forum etiquette IMO. I'm just a little more patient at times answering questions, that's all.
Verizon s5
Spartan117H3 said:
Anything OE1 or higher cannot be rooted. OG5 is higher than OE1, and therefore has the same issues for people who want to root that OE1 has. OE1 has a bootloader that disallows downgrading of firmware which is required to root these phones. The only way you can still downgrade OE1/OG5 is if you came from a rooted phone and did NOT take OTA OE1/OG5, and flashed a firmware that did not change the bootloader.
The stagefright that was incompletely patched was apparently 4 lines of code somewhere in one of the system files, wouldn't be in the bootloader. I understand the sentiments, I would have returned the phone immediately in your case. I'm already running out of patience even being rooted, with the locked bootloader and whatnot. Trying to patiently wait for the Nexus 6 2015 this year.
Click to expand...
Click to collapse
well it sounds like to me everybody in the computer world cannot find a way to unlock the bootloader that is on OE1 or higher I'm thinking surely there's somebody out there that can figure out a way to do it so I would be able to contain root against
trucker950 said:
well it sounds like to me everybody in the computer world cannot find a way to unlock the bootloader that is on OE1 or higher I'm thinking surely there's somebody out there that can figure out a way to do it so I would be able to contain root against
Click to expand...
Click to collapse
There was an $18,000 bounty for a root method and bootloader unlock before one came out. Geohot used Pinkie Pie's findings of an exploit in all Linux kernels to create his root. He now works for Google's Project Zero and isn't allowed to provide root, and even if he was allowed, he probably doesn't care anymore. That exploit has since been patched, hence the need to downgrade to apply Towelroot. Since then, Verizon has blocked the ability to downgrade.
Notes: Bootloader is still locked despite the length of time this phone has been out. This phone is also "dying" and support is mostly gone considering many of the devs went to other devices/new S6, or devices/carriers that don't have this locked bootloader issue. Look at the Note forum. There's still not even a real root for them, they have a temporary one the last time I checked.
So no. Not only are few people looking if they are at all, but support of this phone from Verizon is probably gone as well. This OG5 is more of a mandatory security patch than a new update. 5.0 is most likely the last version for Verizon's S5 (I'd be surprised if they released 5.1/5.1.1).
Spartan117H3 said:
There was an $18,000 bounty for a root method and bootloader unlock before one came out. Geohot used Pinkie Pie's findings of an exploit in all Linux kernels to create his root. He now works for Google's Project Zero and isn't allowed to provide root, and even if he was allowed, he probably doesn't care anymore. That exploit has since been patched, hence the need to downgrade to apply Towelroot. Since then, Verizon has blocked the ability to downgrade.
Notes: Bootloader is still locked despite the length of time this phone has been out. This phone is also "dying" and support is mostly gone considering many of the devs went to other devices/new S6, or devices/carriers that don't have this locked bootloader issue. Look at the Note forum. There's still not even a real root for them, they have a temporary one the last time I checked.
So no. Not only are few people looking if they are at all, but support of this phone from Verizon is probably gone as well. This OG5 is more of a mandatory security patch than a new update. 5.0 is most likely the last version for Verizon's S5 (I'd be surprised if they released 5.1/5.1.1).
Click to expand...
Click to collapse
You couldn't have summed up the S5 situation any better. Cheers!
Hey everyone, I have the S7 G930V and I was curious if it is possible to root this sucker? Im not afraid of doing a flash root and doing everything manually if I have to, done it before back on the original Droid.
I have tried using Odin and it fails on the first step after starting it.
If anyone has any advice or info on how to root my phone, I would love to hear it.
Thanks
Yes you can root the G930V. Here is how to do it
There is a very very low chance that you will do something bad to your device, such as bricking it. Samsung is great with preventing bricks, especially because the bootloader is locked. I can guarantee you safety.
I have not personally rooted it yet because I'm worried I won't be able to deal with the possible issues. Tell me how your experience goes.
Nobiscis said:
Yes you can root the G930V. Here is how to do it
There is a very very low chance that you will do something bad to your device, such as bricking it. Samsung is great with preventing bricks, especially because the bootloader is locked. I can guarantee you safety.
I have not personally rooted it yet because I'm worried I won't be able to deal with the possible issues. Tell me how your experience goes.
Click to expand...
Click to collapse
Thanks, I will give this a shot when I get home and let you know how it goes.
Nobiscis said:
Yes you can root the G930V. Here is how to do it
There is a very very low chance that you will do something bad to your device, such as bricking it. Samsung is great with preventing bricks, especially because the bootloader is locked. I can guarantee you safety.
I have not personally rooted it yet because I'm worried I won't be able to deal with the possible issues. Tell me how your experience goes.
Click to expand...
Click to collapse
Got it done, worked out just fine. Able to do everything I wanted to do. Although the fix file didn't seem to fix the wifi passwords not being saved. Might try and flash it again and see if I can get it to work.
Naddox said:
Got it done, worked out just fine. Able to do everything I wanted to do. Although the fix file didn't seem to fix the wifi passwords not being saved. Might try and flash it again and see if I can get it to work.
Click to expand...
Click to collapse
Wifi is an easy fix in a buid.prop editor. Get a build.prop editor and find a file called ro.securestorage and set it to false. This will fix the problem.
Did you wipe the phone before you rooted? I didn't and got MAJOR performance problems, regardless of the CPU governor control
Nobiscis said:
Did you wipe the phone before you rooted? I didn't and got MAJOR performance problems, regardless of the CPU governor control
Click to expand...
Click to collapse
Out of curiosity, what type of "wipe" are you referring to here?
WarAxe said:
Out of curiosity, what type of "wipe" are you referring to here?
Click to expand...
Click to collapse
Factory reset, essentially
Nobiscis said:
Factory reset, essentially
Click to expand...
Click to collapse
I didn't do any wipe. Just backed up my data incase of anything and did the root with no issues.
Nobiscis said:
Yes you can root the G930V. Here is how to do it
There is a very very low chance that you will do something bad to your device, such as bricking it. Samsung is great with preventing bricks, especially because the bootloader is locked. I can guarantee you safety.
I have not personally rooted it yet because I'm worried I won't be able to deal with the possible issues. Tell me how your experience goes.
Click to expand...
Click to collapse
Okay... except NOT. LOL. I hope you're giving out better advice these days.
Hi,
I've done a quick search but can't find anything definitive so a quick response on here would be greatly appreciated.
Are there any reasons not to root on a P7P? Like tripping Knox on Samsung devices? Basically, irreversible side effects of unlocking the BL or installing Magisk? I'm rooted on a Doogee S98 Pro, a Xiaomi MiPad 4 and a Samsung Tab S6 at the moment and I don't think I could go back to having no root. It's pretty much my main reason for not buying an S22 Ultra.
Hi
this is one of the major benefits of the P7P in my perspective: you can unlock, root, unroot, relock without any negative side effects. You don't trip any fuse or have other effects that cannot be undone by a simple reflash.
Plus, maybe due to this, the P7P is one of the phones where the dev community is still quite active.....
Sent from my rooted P7P
s3axel said:
Hi
this is one of the major benefits of the P7P in my perspective: you can unlock, root, unroot, relock without any negative side effects. You don't trip any fuse or have other effects that cannot be undone by a simple reflash.
Plus, maybe due to this, the P7P is one of the phones where the dev community is still quite active.....
Sent from my rooted P7P
Click to expand...
Click to collapse
Perfect answer, thanks!
Pretty hard to brick a Pixel.
Just make sure you don't relock your bootloader unless you're fully stock. I've seen a bunch of people doing that throughout these forums here for some reason.
Yup, if you want to unroot once you're rooted, it's absolutely imperative you flash full stock before toggling OEM Unlock and issuing any ADB commands to re-lock the bootloader. Do that without flashing back to factory stock and you end up with a phone that can't boot because the bootloader is locked with a non-stock build, you can't unlock the bootloader because the OEM is toggled, and you can't flash a stock build because the bootloader is locked. Brick time.
Other than that it's a fairly safe phone to play around with.
I strongly recommend Pixel Flasher, it makes the whole process easier, but make sure you read up on it before doing anything.
📳🔥PixelFlasher for Google Pixel 7 Pro Support Thread.
This is the support thread of PixelFlasher (PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/rooting/updating with extra features). Note: This thread is meant for issues and problems faced in...
forum.xda-developers.com
GrapheneOS also supports relocking the bootloader, although I can't think of a reason why you'd want to.
The best reason not to root is that it's not needed in 2022. I can't imagine "needing" to do something with root that cannot be accomplished without root. YMMV
jaseman said:
The best reason not to root is that it's not needed in 2022. I can't imagine "needing" to do something with root that cannot be accomplished without root. YMMV
Click to expand...
Click to collapse
Call recording, full backup and restore, hosts based ad blockers.
Once rooted, it's annoying having to disable all Magisk mods, run updates, then re-root every month. I've also had updates corrupt the A/B Partitions. The warning screen for unlocked bootloader alone is a nuisance. If you're ok with that, go right ahead.
Guyinlaca said:
disable all Magisk mods, run updates, then re-root every month
Click to expand...
Click to collapse
You're adding steps and no indication of why. Just install the update with modified boot.img and call it good.
96carboard said:
Call recording, full backup and restore, hosts based ad blockers.
Click to expand...
Click to collapse
I went 3 days before rooting my P7P since I was unfamiliar with the process. I was able to root OnePlus blindfolded, but the forums made Pixel seem difficult. It was the most miserable 3 days when everything I wanted to use/customize depended on root.
without root I could not even get 5G working. Furthermore the AOSP Mods on the stock ROM... Systemless Hosts AdBlocking, Re-Vanced, .......
I unlocked and rooted the phone before even booted it the first time
Guyinlaca said:
Once rooted, it's annoying having to disable all Magisk mods, run updates, then re-root every month.
Click to expand...
Click to collapse
Updated to November, didn't disable any Magisk mods, no issues.
It's only some mods which cause issues. Not got them installed, you can perform the update without touching Magisk.
Guyinlaca said:
Once rooted, it's annoying having to disable all Magisk mods, run updates, then re-root every month. I've also had updates corrupt the A/B Partitions. The warning screen for unlocked bootloader alone is a nuisance. If you're ok with that, go right ahead.
Click to expand...
Click to collapse
You don't have to disable all your Magisk Mods
K1nsey6 said:
I went 3 days before rooting my P7P since I was unfamiliar with the process. I was able to root OnePlus blindfolded, but the forums made Pixel seem difficult. It was the most miserable 3 days when everything I wanted to use/customize depended on root.
Click to expand...
Click to collapse
And wasn't it funny when you realized that root on Pixel is actually easier than everything else?
Hello , i need help for rooting my p7p. If have a video step by step its be very helpfull. Sorry for my bad english " Salut " from Romania thanks
ZoM4cs said:
Hello , i need help for rooting my p7p. If have a video step by step its be very helpfull. Sorry for my bad english " Salut " from Romania thanks
Click to expand...
Click to collapse
Here is a guide you can follow.
96carboard said:
Call recording, full backup and restore, hosts based ad blockers.
Click to expand...
Click to collapse
Umm that's illegal bro.
chivamex10 said:
Umm that's illegal bro.
Click to expand...
Click to collapse
Maybe where you are, but not here and not in most places. So keep your legal advice to yourself, BRO.
chivamex10 said:
Umm that's illegal bro.
Click to expand...
Click to collapse
Actually in most jurisdictions it's what's called a one party consent requirement wherein one of the parties involved must be aware and consent. In this case the person doing the recording qualifies as the consenting party. In other places two party or more consent is required but not everywhere