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
Related
I was wondering now that djrbliss has released the vulnerability for AT&T SGS4 do we have to wait for devs to do something with it? For Loki tools it seems as if you have to have a recovery already made. Will a current one work?
https://github.com/djrbliss/loki
this seems more like a user made htc dev, not what true s-off "bootloader unlocked" would be. non the less it should work fine. this probably wont touch the write enabled protection on the device. the only issues i see is until we are truly unlocked we will always have that "samsung custom" on out bootscreens.
spyz88 said:
I was wondering now that djrbliss has released the vulnerability for AT&T SGS4 do we have to wait for devs to do something with it? For Loki tools it seems as if you have to have a recovery already made. Will a current one work?
https://github.com/djrbliss/loki
Click to expand...
Click to collapse
He released his source code and such so we need to have someone compile it into a .bat or .exe so we can flash a custom recovery/rom
its linux only, and devs need to use/make teh loki_patch.
someone could make a windows/android app to interface with loki_flash for end users though...
shabbypenguin said:
its linux only, and devs need to use/make teh loki_patch.
someone could make a windows/android app to interface with loki_flash for end users though...
Click to expand...
Click to collapse
well i cant use it as i don't use linux lol.
Everyone - if you don't know what to do with those files without asking, don't try it yourself. There's already one in process in the development thread, and there will be cleaner and simpler ones out within just a few hours, I'm sure - with complete instructions.
Until you can nandroid the phone, this is not something to screw around with
fix-this! said:
well i cant use it as i don't use linux lol.
Click to expand...
Click to collapse
well if you dont use linux you cant make kernels or recoveries
luckily the loki_flash utility that is used to actually put the patched img onto the device works on android so it doenst matter what kind of computer you have
alacrify said:
Everyone - if you don't know what to do with those files without asking, don't try it yourself. There's already one in process in the development thread, and there will be cleaner and simpler ones out within just a few hours, I'm sure - with complete instructions.
Until you can nandroid the phone, this is not something to screw around with
Click to expand...
Click to collapse
A mod should put that up as a temp announcement in these forums. Seriously. Can't wait for the noobs to start crying in the Q&A area.... haha.
just means soon we will have bootloader unlocked.... patience
lorijuan1024 said:
just means soon we will have bootloader unlocked.... patience
Click to expand...
Click to collapse
i thought that's what this tool did. maybe this is why adam is still working on a bootloader unlock thats permanent. this should tide us over though.
Bjray said:
A mod should put that up as a temp announcement in these forums. Seriously. Can't wait for the noobs to start crying in the Q&A area.... haha.
Click to expand...
Click to collapse
Exactly, I have one phone booting to recovery now, no issues. YET! better know what you are doing, or you will have a serious paperweight.
I re-booted out of successful, so will see.
Update: nand backup was successful. Good start for us, just need the perm fix, but for now, it rocks, it was so nice to see the recovery screen. SWEET
TheAxman said:
Exactly, I have one phone booting to recovery now, no issues. YET! better know what you are doing, or you will have a serious paperweight.
I re-booted out of successful, so will see.
Click to expand...
Click to collapse
im not going to try the method yet, at least for a few days. i also see alot of soft bricked devices tonight.
fix-this! said:
i thought that's what this tool did. maybe this is why adam is still working on a bootloader unlock thats permanent. this should tide us over though.
Click to expand...
Click to collapse
what i meant was a tool that us people that aren't good with the programming language can use.
fix-this! said:
im not going to try the method yet, at least for a few days. i also see alot of soft bricked devices tonight.
Click to expand...
Click to collapse
Agreed, but I do have a jtag box here in hand, and there is no fix for that either, I might have one phone down soon..:
Incoming update from Samsung in 3....2....1.....
I flashed what shabbypenguin provided in his recovery thread and now have a working recovery on my ATT i337!!! :laugh::good::highfive::fingers-crossed:
Thanks to djrbliss for his awesome work!
mr_blanket said:
Incoming update from Samsung in 3....2....1.....
Click to expand...
Click to collapse
simple solution is to not take the OTA. but yes, i see one coming to.
fix-this! said:
simple solution is to not take the OTA. but yes, i see one coming to.
Click to expand...
Click to collapse
Yes, everyone needs to keep the OTA .apk's frozen from now on. Or use a custom rom that doesn't have them.
mattdm said:
Yes, everyone needs to keep the OTA .apk's frozen from now on. Or use a custom rom that doesn't have them.
Click to expand...
Click to collapse
hopefully adam can get us a more permanent solution. but props to dan for his tool.
Couldn't be happier after I get home from watching the hangover I get to unlock this bad boy
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
All,
I'm currently rooted with towelroot. From all that I read, towelroot is the only option that won't take the update. So far, is my only option to unroot, wipe and reflash back to stock? Or there any other other options? I would like to update my radio don't seem like its available to flash yet.
Thanks for any opinion and suggestions.
Nutzzer said:
All,
I'm currently rooted with towelroot. From all that I read, towelroot is the only option that won't take the update. So far, is my only option to unroot, wipe and reflash back to stock? Or there any other other options? I would like to update my radio don't seem like its available to flash yet.
Thanks for any opinion and suggestions.
Click to expand...
Click to collapse
No words.....
If a newer radio (which offers no promise of improved performance) outweighs the desire to have root and bump, then you should use the recovery tool to get your phone back to bone stock and then take the update. There are plenty of threads that talk about how to do this - usually from people that have taken the update and want to get back to where they were. Maybe that should be a sign for you. If you do take the update, don't come back here crying when you realize what you are missing out on....... Good luck.
sic0048 said:
No words.....
If a newer radio (which offers no promise of improved performance) outweighs the desire to have root and bump, then you should use the recovery tool to get your phone back to bone stock and then take the update. There are plenty of threads that talk about how to do this - usually from people that have taken the update and want to get back to where they were. Maybe that should be a sign for you. If you do take the update, don't come back here crying when you realize what you are missing out on....... Good luck.
Click to expand...
Click to collapse
you can get root and bump after the upgrade just use stump root
Thank you all! Will wait it out for a couple more days to see what I will do.
jerrycoffman45 said:
you can get root and bump after the upgrade just use stump root
Click to expand...
Click to collapse
This time, but what about next time? There is no guarantee that root and or bump will ever survive a OTA update.
That is correct from what I have read lolipop will be harder to root and we might not get root
or you could just flash this
http://forum.xda-developers.com/att-lg-g3/development/rom-stock-rooted-att-odexed-d85010f-t2945873
Wickidmasshole said:
or you could just flash this
http://forum.xda-developers.com/att-lg-g3/development/rom-stock-rooted-att-odexed-d85010f-t2945873
Click to expand...
Click to collapse
Arrrghhh! Where was that last night when my laptop and phone were fighting with flash tool over download mode and firmware install? lol.
KennyG123 said:
Arrrghhh! Where was that last night when my laptop and phone were fighting with flash tool over download mode and firmware install? lol.
Click to expand...
Click to collapse
there wouldn't of been a fight if you had waited until 6:46am!!
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!
I know root is achieved with a tot file for the G5 but will there be a one script method like for the g3? I haven't rooted my phone yet because I dont want to risk bricking my phone.
RicardoSal24 said:
I know root is achieved with a tot file for the G5 but will there be a one script method like for the g3? I haven't rooted my phone yet because I dont want to risk bricking my phone.
Click to expand...
Click to collapse
there won't be a script for this as there are no instructions for the bootloader to flash any file. The reason they are using the TOT method is because we have no other way to write to the device. ADB is enabled but the actual command needed to copy everything over was left out.
fatapia said:
there won't be a script for this as there are no instructions for the bootloader to flash any file. The reason they are using the TOT method is because we have no other way to write to the device. ADB is enabled but the actual command needed to copy everything over was left out.
Click to expand...
Click to collapse
Is rooting the phone ASAP worth the time or is it best to wait awhile after a software update?
RicardoSal24 said:
Is rooting the phone ASAP worth the time or is it best to wait awhile after a software update?
Click to expand...
Click to collapse
if you haven't taken that 10d update I would just root now. Not sure if you've seen the thread where they are discussing the possibility of using the TOT method with the new 10d file, but once you update it trips something (qfuse I believe, Autoprime is the one who discovered this AFAIK) that prevents you from using the existing TOT on the forum and from downgrading.
once you root, you can update to 10d and as long as you flash supersu you will still have access to TWRP and root on the latest update. I recommend waiting updating to 10d even after rooting until they iron out all the issues though.
edit: have you done the OEM unlock through dev options yet? it will wipe your phone in the process FYI so make sure you have everything backed up.
Come on. It wasn't that hard to root it. Just follow the directions. Easy!
How do I know if I have the 10d update? I unlocked the bootloader, rooted it, then thought I had a quality control issue with the pain on the frame. So I flashed stock and locked the bootloader to prepare for a warranty exchange. Turns out the paint wasn't bubbling. It was the protective plastic adhesive I had never taken off. I'm stupid, I know, lol. Now I want to root again but I don't know about the 10d update.
rebelde80 said:
How do I know if I have the 10d update? I unlocked the bootloader, rooted it, then thought I had a quality control issue with the pain on the frame. So I flashed stock and locked the bootloader to prepare for a warranty exchange. Turns out the paint wasn't bubbling. It was the protective plastic adhesive I had never taken off. I'm stupid, I know, lol. Now I want to root again but I don't know about the 10d update.
Click to expand...
Click to collapse
about phone/software version
fatapia said:
if you haven't taken that 10d update I would just root now. Not sure if you've seen the thread where they are discussing the possibility of using the TOT method with the new 10d file, but once you update it trips something (qfuse I believe, Autoprime is the one who discovered this AFAIK) that prevents you from using the existing TOT on the forum and from downgrading.
once you root, you can update to 10d and as long as you flash supersu you will still have access to TWRP and root on the latest update. I recommend waiting updating to 10d even after rooting until they iron out all the issues though.
edit: have you done the OEM unlock through dev options yet? it will wipe your phone in the process FYI so make sure you have everything backed up.
Click to expand...
Click to collapse
I've had an understanding that updating android versions while being rooted may cause the phone to be bricked
i have software version 10a that is rootable right thats not 10d or are they similar.
RicardoSal24 said:
I've had an understanding that updating android versions while being rooted may cause the phone to be bricked
Click to expand...
Click to collapse
that may have been true at some point especially with OEM FW, but as far as custom I rooted then updated for my GS4, G3, and v10. Just because it worked for me doesn't mean it will for anyone else. I had the variants that once they were rooted you held on to it like dear life
fatapia said:
that may have been true at some point especially with OEM FW, but as far as custom I rooted then updated for my GS4, G3, and v10. Just because it worked for me doesn't mean it will for anyone else. I had the variants that once they were rooted you held on to it like dear life
Click to expand...
Click to collapse
So then its best to wait until something is done with the update?
RicardoSal24 said:
So then its best to wait until something is done with the update?
Click to expand...
Click to collapse
from what I've read the method is established now and there is "zero" risk as long as you follow the instructions, I haven't updated because I haven't experienced the issues others are having
fatapia said:
from what I've read the method is established now and there is "zero" risk as long as you follow the instructions, I haven't updated because I haven't experienced the issues others are having
Click to expand...
Click to collapse
I think I'll play it safe until its 100% or wait for a new android version with a root method
RicardoSal24 said:
I think I'll play it safe until its 100% or wait for a new android version with a root method
Click to expand...
Click to collapse
it's never 100% safe, hence the quotation marks. there's always a risk of something going wrong such as a power outage, or bad file download. As long as you verify the md5sum of your files you shouldn't have a problem with rooting, the only problems I've seen are people trying to use the wrong files on their device. up to you tho man, good luck with which ever you decide
This root method (compared to my old EVO 3D which needed juopunutbear and a wire)....ez pz.
lordodin912 said:
This root method (compared to my old EVO 3D which needed juopunutbear and a wire)....ez pz.
Click to expand...
Click to collapse
That sounds like fun, if you ask me. What was the wire for, if you don't mind me asking? Bypassing a fuse?
xanderin said:
That sounds like fun, if you ask me. What was the wire for, if you don't mind me asking? Bypassing a fuse?
Click to expand...
Click to collapse
It was needed for s-off, so not tech for root (if i remember correctly) but for being able to flash custom roms and such. Theres youtube videos about it.
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