Hi I recently upgraded my phone earlier this week to lollipop 5.0 second update. Software version BOD3. I used cf auto root and soft bricked my phone. Is there any way to root this version of lollipop for my phone. Thank you
Oh I forgot I have the sprint Samsung Galaxy s5 G900P
garbage30 said:
Hi I recently upgraded my phone earlier this week to lollipop 5.0 second update. Software version BOD3. I used cf auto root and soft bricked my phone. Is there any way to root this version of lollipop for my phone. Thank you
Click to expand...
Click to collapse
You need to be reading/checking the Android Development thread. Read the OP's the the roms you're interested in. If they say they are pre-rooted, then all you have to do is use Odin to install a custom recovery first. Plan in advance, you'll need to have the rom you choose copied to your phone first. Then, in Odin un-check auto-reboot. When it finishes installing, unplug your phone, pull the battery. Reinstall battery and immediately go into recovery (Home, Volume UP, Power) and flash your rom. Again, I can't stress enough, "read" about the rom you're interested in. I can give you a couple of rom's that I know will work with OD3, but the decision is yours:
MOAR 6.2. This one has a strong user community for support, more features (and growing) then you know what to do with!
Stock De-odexed Very new, but if you want stock and rooted without any bells and whistles, this would be the one.
Hey can u help me again i downloaded the stock rom and wiped everything in recovery. Then i updated in recovery.everything loaded fine but it is telling me that it is.not rooted. Su say cant get binary and.root checker tells me.no root. I tried to reboot the.phone but its telling me.no root. I thought the.rom was rooted. Am i doing something wrong.thanks
I got this s6 back in march or april and it was on 5.0.2 and well now that iv've updated to the OTAS 5.1.1 OFE i was curious about root and i continued with a thread about rooting it and etc
( i kinda regret that now, i shouldve stayed on 5.0.2)
but the main reason i rooted was to recover files and welli did but i installed dr fone on my computer it asked for my phones root permissions so i went ahead and rooted it but after a bit i noticed it started to freeze my phone and after a bit it just stopped working.
i turn it on and restart it i see a blue led cycling and i see the sprint spark screen but it does nothing from there.
and so i stupidly went to to stock recovery, wiped cache, and factory resetting it and now idk what to do
there isnt an OFE stock tar yet so i cant fix this on my own, im just thinking if i flash twrp right now and then flash a custom rom will that work?? for my OFE build
am i able to or should i just download the stock tar 5.0.2 to reflash it or will that just basically brick me completely??
also i did have insurance for this and i thnink i just blew that one too :/
ive noticed mine said this
G920PVPU2BOFE
and not G920PVPU2BOF7
so does that mean im able to use the stock firmware from the website and reflash it or like what do i do...
SO what i did countless of researching
i ended up having the
custom binary blocked by FRP lock, by forgetting to unlock oem before updating the Twisted Projects SuperSu or User since it asked me to updated i ovbiously just went ahead of myself and that happened thus into this Boot Loop Soft
and im flashing with ODIN the stock 5.1.1 OF7 tar its surprisingly working. ( i was originally on the OFE OTA tho.)
unlike the Twisted Project custom roms, kernel and or twrp setup, i couldnt boot into the twrp or even past the android screen, and well the only option i had was just Download Mode.
And this basically saved me.
Very Informative
Hi folks,
just posting this writeup thinking maybe it might be of help to some people.
Started with a clean S6 Edge straight from Samsung repair for broken screen. Factory wipe, KNOX reset. It had the PD2 update. Tried using Skipsoft's Toolkit and ponied up a donation to get the Pro version with the S6 Edge 6.0.1 update, but it didn't work: it got stuck at the "SEANDROID NOT ENFORCING" screen after flashing TWRP 3.0.2. I know there are issues with 3.0.2, but it's what's optioned in Toolkit now.
Flashing TWRP 2.8.7.0 results in normal boot, but I could not enter recovery mode for some reason. 3.0.0-0 didn't work, either.
What I ended up doing is forcing phone into download mode (Power+Volume Down+Home), ODINing TWRP 3.0.2-1. This resulted in a bootloop (somewhat expected). But I could get into recovery easily. From recovery, I flashed Renegade's PD2-Aroma V3.0 Full ROM via ADB sideload. After a very long first boot, everything works 100%! Root, SuperSU, etc., all taken care of. Hotspot works.
Notes and tips:
- While I didn't use Skipsoft's Toolkit in the end, it's still worth supporting. Might work smoothly using 3.0.2-1 instead of 3.0.2.0, but I'm comfortable with adb/fastboot/etc. so just ended up using that. If you don't already have Android SDK and tools/platform-tools, Skipsoft conveniently includes those commands in its directory under C:\Unified_Android_Toolkit (they're named adb-toolkit and fastboot-toolkit. You can copy and rename them as "adb" and "fastboot" for convenience).
- Make sure you get the right TWRP 3.0.2-1 device version. You want to use twrp-3.0.2-1-zeroltespr.tar.md5 for Sprint S6 Edge. Remove the .md5 part and set it to use the .tar extension (stupid Windows asks you to confirm file extension type change).
- In TWRP you can either push your custom ROM or sideload it. To push a file, move the custom ROM into the same directory you've got adb/fastboot for convenience. Open a terminal window in that directory, and either "adb push customromfilenamehere.zip /sdcard/" or in TWRP, click Advanced/ADB Sideload, and enter "adb sideload customromfilenamehere.zip".
- If you're sideloading it, it's gonna take a while, and will start flashing even while the transfer percentage is creeping up. Example: at around 9%, it started AROMA, around 14%, it went through some of the installation options. It was done flashing everything and ready for reboot even though the terminal window said only 76% was transferred. That's ok. Click "finish" in AROMA on phone, reboot. Unplug phone. Wait a long time for first boot (this took around 20 minutes for me). ENJOY.
Remember: all is not lost as long as you can get into download mode! Power-Volume Down-Home until you get to screen prompting to get to download mode. Volume up to select that mode. You can ODIN from here.
Additionally: if you find yourself for whatever reason stuck at the initial S6 Edge boot screen with "SEANDROID NOT ENFORCING," you might be in some kinda of boot limbo. I was able to issue some adb commands here, even with recovery was borked and the phone didn't boot all the way. Doing an "adb reboot-bootloader" would let me do a complete boot to ROM while I was trying to get the different TWRP versions working (until 3.0.2-1).
Hope this helps someone.
tl;dr: For PD2/6.0.1 Sprint S6 Edge, manual flash TWRP 3.0.2-1. Push custom ROM through Recovery. Reboot, wait a long time. Success!
Just to Clarify (and mostly for myself), I think this is the simplest and most foolproof way to get yourself fully update and on a custom rom with root.
1. ODIN Stock PD2 Image. Reboot, make sure dev options + USB debugging is enabled.
2. ODIN latest TWRP 3.0.2.1 - HERE.
3. Obtain root by going into TWRP immediately after you install it and flashing the root kernel Ram did for this device - HERE
4. Then after wiping cache, dalvik and data in TWRP, flash Renegade ROM 3.0 PD2.
Using CFauto root method is known to cause issues. This is the type of approach I took and it was flawless. The initial boot of the Renegade ROM can seriously take like 20min though, I thought I was looping for a second.
If anyone disagrees with this method or sees where it can be done better, please advise. This seems to prevent the instance of any loops or issues. The Renegade ROM has a rooted kernel so flashing the root kernel is likely a redundant step. You could omit Step 3 if you are flashing a custom ROM, probably, but it seems to prevent any hangups. But if you plan to stay stock, you still have to flash a rooted kernel after TWRP.
Alpine- said:
Just to Clarify (and mostly for myself), I think this is the simplest and most foolproof way to get yourself fully update and on a custom rom with root.
1. ODIN Stock PD2 Image. Reboot, make sure dev options + USB debugging is enabled.
2. ODIN Ram's TWRP 3.0.2 - HERE I'm assuming the other guy's 3.0.2 works fine too, I am not sure why you hung and had to revert to a 2.x TWRP build.
3. Obtain root by going into TWRP immediately after you install it and flashing the root kernel Ram did for this device - HERE
4. Then after wiping cache, dalvik and data in TWRP, flash Renegade ROM 3.0 PD2.
Using CFauto root method is known to cause issues. This is the type of approach I took and it was flawless. The initial boot of the Renegade ROM can seriously take like 20min though, I thought I was looping for a second.
If anyone disagrees with this method or sees where it can be done better, please advise. This seems to prevent the instance of any loops or issues. The Renegade ROM has a rooted kernel so flashing the root kernel is likely a redundant step. You could omit Step 3 if you are flashing a custom ROM, probably, but it seems to prevent any hangups. But if you plan to stay stock, you still have to flash a rooted kernel after TWRP.
Click to expand...
Click to collapse
I noticed chainfire now has a CF-autoroot for the 925P 6.01 and people were having success using the one for the 925F. Any verification on this? Haven't seen anyone on this forum say anything about it. I just bought a new S6 edge for sprint. I always am about year behind on phones because of the high cost of the latest and greatest. I picked the edge because my wife has had one a year and it gets a lot better reception than my N5. But, I gots to have root and don't wanna screw up a new phone. I know the first thing I need to do is check which software it's running. Should I do this before I activate it or can i stop any system upgrades before they install?
baknblack said:
I noticed chainfire now has a CF-autoroot for the 925P 6.01 and people were having success using the one for the 925F. Any verification on this? Haven't seen anyone on this forum say anything about it. I just bought a new S6 edge for sprint. I always am about year behind on phones because of the high cost of the latest and greatest. I picked the edge because my wife has had one a year and it gets a lot better reception than my N5. But, I gots to have root and don't wanna screw up a new phone. I know the first thing I need to do is check which software it's running. Should I do this before I activate it or can i stop any system upgrades before they install?
Click to expand...
Click to collapse
I have not attempted to use CF-autoroot just because of reported issues and the general recommendation being to use the standard method. It may work fine now that its been updated, but I have not personally tested it.
Alpine- said:
I have not attempted to use CF-autoroot just because of reported issues and the general recommendation being to use the standard method. It may work fine now that its been updated, but I have not personally tested it.
Click to expand...
Click to collapse
I just bought my phone new off ebay it updated to PF4 just as soon as I activated it. I couldn't stop it. Anyway I used the CF autoroot on it and it worked perfectly. I tried to do it manually a couple times first and never could get TWRP to flash. It would say it was successful but, stock recovery stayed. Anyways, I got er done and running Renegade wich btw is an awesome ROM. This is my first samsung device and had I done a bit more research I'd of known the majority of development is on the regular S6. I just picked the edge because my wife has one and it worked so much better in the boonies than my N5 did.
baknblack said:
I just bought my phone new off ebay it updated to PF4 just as soon as I activated it. I couldn't stop it. Anyway I used the CF autoroot on it and it worked perfectly. I tried to do it manually a couple times first and never could get TWRP to flash. It would say it was successful but, stock recovery stayed. Anyways, I got er done and running Renegade wich btw is an awesome ROM. This is my first samsung device and had I done a bit more research I'd of known the majority of development is on the regular S6. I just picked the edge because my wife has one and it worked so much better in the boonies than my N5 did.
Click to expand...
Click to collapse
Edge is better imo, certainly looks better. All you need is Renegade rom anyway. May be a few more roms in active dev for s6 but nothing better per se. Renegade rom dev is alive and well.
Would these root methods trip knox?
chen69chuck said:
Would these root methods trip knox?
Click to expand...
Click to collapse
Yes
Thanks.
Working for g920v 6.0.1?
freaking thank you been struggling with twrp on and off for two days trying to bring this phone back from the dead! YOU the man
Hey guy's I've owned all Galaxy S models up until the S7. (except for S3 when I had a Note2). I've always flashed all my phones with custom firmware except when the S6 came along. This was the first phone that worked pretty well out of the box and because of device encryption not working with custom firmwares and kernels I didn't want to go off stock. Recently I wanted to give my S6 a refreshment and I replaced most parts. Midframe, camera, screenglass, rearglass, charger board and obviously the annoyingly small 2550mah battery that was pretty much useless after 2 years of extensive use. (max 2h SOT). I replaced it with de 3600mah S7 Edge battery and obviously ran into calibration issues. There is a new kernel that can solve this issue. So I decided to flash it.
Previously I tried some custom software but got into trouble because of device encryption. When I flashed TWRP I couldn't access the internal memory with it. But when I turned of encryption it would work. But Nougat 7.0 doesn't seem to be able to turn off device encryption.. I can't find the option anywhere!
I flashed the latest (correct version) of TWRP with Odin and got it too boot into recovery.. Again can't access the internal memory to flash anything else. When I try to reboot it keeps bootlooping. I've read I need to flash the SuperSU root to fix this issue but I don't want to root the device... I just want to install the custom kernel. And anyway I CAN'T even flash the root file because I can't access the memory.. I flashed the other root file with Odin.. this made the phone boot up again but come back with a warning that the data couldn't be verified (obviously being related to encryption).
I don't know how to turn off encryption in Nougat 7.0. It just doesn't seem to have the option.. But als TWRP is useless right now..
Maybe useful to know, I've upgrade android 6.1 to 7.0 with OTA. Never did a factory reset in between these versions. So it copied the encryption settings from the 6.1 version.. I've read encryption in Nougat 7.0 is always one but works differently? I'm a little confused
I'm kind of stuck... I reflashed original firmware to get back into my phone again. Any ideas?
So first off I would say I am average in the world of modifications, I know the basics. I used to run a stock Nougat rom with Magisk.
Being the clumsy fool that I am, I dropped my phone and the screen broke. I went to a Samsung service center and deposited my phone there for screen replacement and they decided to update my phone for no reason...
As my phone was rooted, after forcing an update on my phone a soft brick happened and they had to flash a new firmware which meant that I lost everything. Now I am running latest stock Oreo 8.0.
I tried these things to root my phone again:
(The first thing I did was flashing twrp through odin)
#1: Downloaded Magisk and a decryptor for getting past the locked bootloader... flashed them both using recovery (twrp works 100%), and my phone got stuck on the Samsung S7 - powered by android after a reboot from recovery. Waited for a long time. Tried a lot of alternatives on this method but got stuck..
#2 After I gave up on rooting the firmware I was given, I decided to go back on my old Nougat firmware which used to work flawlessly... so I had the nougat firmware on my computer but this time Odin gave me an error along with some red text on top right in download mode. I looked up the error and it basically meant that I cannot revert back to Nougat anymore (which is surprising as I could easily swap between Nougat and Marshmallow but I can't do the same with Oreo and Nougat)
Quote from a person on the internet: ''SW REV CK FAIL usually means that you are not flashing the most current released firmware version. Most Samsung devices will not let you downgrade. You have to flash what was previously installed or higher Android version.''
#3 I was frustrated. I tried using a last resort.. downloaded a custom rom which has root included called ''Galaxy Project''... Flashed it using twrp and got a bootloop for 2 hours. To get past the bootloop I had to download Oreo stock rom and flashed it using Odin. That worked.. I'm back on stock Oreo again... back to square one.
Please help out a stumped Android enthusiast... I have spent 2 days on this... but no solution works. My phone is not in danger of a hard brick as I can always revert to stock Oreo using Odin but having root would be nice.
I am having average experience, I know just the basics... please help me out and tell me what to do in a step by step manner.. I will try everything and report the findings till I finally come across a method which works.
EDIT: My phone model is G930FD
Devansh_Droidgeek! said:
So first off I would say I am average in the world of modifications, I know the basics. I used to run a stock Nougat rom with Magisk.
Being the clumsy fool that I am, I dropped my phone and the screen broke. I went to a Samsung service center and deposited my phone there for screen replacement and they decided to update my phone for no reason...
As my phone was rooted, after forcing an update on my phone a soft brick happened and they had to flash a new firmware which meant that I lost everything. Now I am running latest stock Oreo 8.0.
I tried these things to root my phone again:
(The first thing I did was flashing twrp through odin)
#1: Downloaded Magisk and a decryptor for getting past the locked bootloader... flashed them both using recovery (twrp works 100%), and my phone got stuck on the Samsung S7 - powered by android after a reboot from recovery. Waited for a long time. Tried a lot of alternatives on this method but got stuck..
#2 After I gave up on rooting the firmware I was given, I decided to go back on my old Nougat firmware which used to work flawlessly... so I had the nougat firmware on my computer but this time Odin gave me an error along with some red text on top right in download mode. I looked up the error and it basically meant that I cannot revert back to Nougat anymore (which is surprising as I could easily swap between Nougat and Marshmallow but I can't do the same with Oreo and Nougat)
Quote from a person on the internet: ''SW REV CK FAIL usually means that you are not flashing the most current released firmware version. Most Samsung devices will not let you downgrade. You have to flash what was previously installed or higher Android version.''
#3 I was frustrated. I tried using a last resort.. downloaded a custom rom which has root included called ''Galaxy Project''... Flashed it using twrp and got a bootloop for 2 hours. To get past the bootloop I had to download Oreo stock rom and flashed it using Odin. That worked.. I'm back on stock Oreo again... back to square one.
Please help out a stumped Android enthusiast... I have spent 2 days on this... but no solution works. My phone is not in danger of a hard brick as I can always revert to stock Oreo using Odin but having root would be nice.
I am having average experience, I know just the basics... please help me out and tell me what to do in a step by step manner.. I will try everything and report the findings till I finally come across a method which works.
EDIT: My phone model is G930FD
Click to expand...
Click to collapse
OEM unlocked???
cooltt said:
OEM unlocked???
Click to expand...
Click to collapse
through developer settings? yes
Devansh_Droidgeek! said:
through developer settings? yes
Click to expand...
Click to collapse
follow this guide here