Related
Hello all, I come asking for help. I recently had an issue with my note 3. I tried to update my twrp with the twrp manager, I had safestrap 3.75 and then used the twrp manager to try and flash the new 3.8.4.0 twrp, but after it flashed I went to recovery and tried to install cm12 but kept getting the error "this build is for hltevzw, you have a ." When trying to install. So I went full stock, flashed the new stock stuff via odin. Then rerooted with towelroot, installed superSU, then the safestrap 3.75. Now I can get to safestrap recovery, but if I try to install cm12, I will follow directions, flash rom, flash gapps, then I've tried flashing superSU as some have suggested, and tried not flashing superSU, but then my phone reboots, goes past the splash screen showing the unlock and says custom, sits at a black screen for a while, then reboots. Only when it reboots, at the splash screen it says loafing recovery in red at the top, then I get a screen saying that custom software has been detected and I need to take the phone in to Verizon or something like that. The only way to get out of it is to shut down, boot into download, and then hit volume down to cancel. It just keeps doing that same thing over and over. I was able to get eclipse rom installed, but cm12 always does the same thing. I've also gone into the safestrap 3.75 recovery and flashed the twrp 3.8.4.0, it says it was successful, but then I'll reboot, get to the safestrap screen, hit recovery, and it is still the older one with safestrap 3.75, not the updated one I just flashed. If I try to shut down my phone and power on using volume up, home, and power, I get the stock recovery saying that it has detected custom software and blah blah blah. So, I have a bunch of problems and honestly I am not sure what is going on. I have scoured the Web for 3 days now trying to find instructions on updating the recovery, every single one is the same as I described above with the same outcome. I've also been searching for how to install cm12, with the same results. Can anyone help me, I am so annoyed, lost, confused, and just.... please help. Thank you.
Tldr; recovery stuck on safestrap 3.75 regardless of flashing the newer twrp 3.8.4.0, and when trying to reboot into recovery using volume up, home, and power, I get the stock recovery with a message saying custom software detected. Please help.... please. I am on hltevzw with nc4. Rooted with towelroot, and safestrap 3.75.
you have a retail note 3 cm12 is for the dev edition the retail bootloader will only load samsung based firmware note 3 or 4 or the s5 are possible but all with touchwiz running the samsung kernel.
if you had a dev note 3 it has an unlockable bootloader and you needed to unlock that first.
If you had a dev unit and updated it via kies you just turned it into a retail unit permanently...
mirrin said:
you have a retail note 3 cm12 is for the dev edition the retail bootloader will only load samsung based firmware note 3 or 4 or the s5 are possible but all with touchwiz running the samsung kernel.
if you had a dev note 3 it has an unlockable bootloader and you needed to unlock that first.
If you had a dev unit and updated it via kies you just turned it into a retail unit permanently...
Click to expand...
Click to collapse
I do have the Verizon version, so no dev ed here, but tamasek has put out a version of cm12 that works on the verizon, sprint, and t-mobile versions of the note 3. I realize it's unofficial and we aren't supposed to post about problems with unofficial builds, but my problem covers more than just cm12 not working. I never knew that tidbit about upgrading via kies ruins dev edition though, that's a trip.
danwguy said:
I do have the Verizon version, so no dev ed here, but tamasek has put out a version of cm12 that works on the verizon, sprint, and t-mobile versions of the note 3. I realize it's unofficial and we aren't supposed to post about problems with unofficial builds, but my problem covers more than just cm12 not working. I never knew that tidbit about upgrading via kies ruins dev edition though, that's a trip.
Click to expand...
Click to collapse
Yep kies loads the retail bootloader and since it is the exact same hardware with the exception of an unlock able bootloader and a dev bit flipped the retail bootloader will load to it and flip the dev bit off... it may work or hard brick the unit i can't remember i want to say the unit worked and was for all intents a retail unit after that.
I can't find any thing on a version of cm12 for the retail version also sprint and t-mobile don't count those devices don't have locked bootloader I was looking to confirm but I know the t-mobile one was unlocked looking at the sprint section that one seems like it too.
only att and Verizon locked them... and Verizon has the $ 700 dev units in which all that was done is a bit was flipped and an unlock able bootloader installed.
just found his thread on it yes his cm12 is for dev units on Verizon only...
mirrin said:
Yep kies loads the retail bootloader and since it is the exact same hardware with the exception of an unlock able bootloader and a dev bit flipped the retail bootloader will load to it and flip the dev bit off... it may work or hard brick the unit i can't remember i want to say the unit worked and was for all intents a retail unit after that.
I can't find any thing on a version of cm12 for the retail version also sprint and t-mobile don't count those devices don't have locked bootloader I was looking to confirm but I know the t-mobile one was unlocked looking at the sprint section that one seems like it too.
only att and Verizon locked them... and Verizon has the $ 700 dev units in which all that was done is a bit was flipped and an unlock able bootloader installed.
just found his thread on it yes his cm12 is for dev units on Verizon only...
Click to expand...
Click to collapse
The one I was trying to load up was from here https://s.basketbuild.com/devs/temasek/Samsung Galaxy Note 3 - HLTEVZW/CM12/Old
it's for dev editions only? That is a huge disappointment, I was really hoping to get some android Learn on my phone
Do you have any idea why, after I flash the twrp 3.8.4.0 recovery from safestrap recovery, after I reboot I am still showing safestrap and the older twrp. It's like the new version flashes, but then just disappears and the old version loads up.
Thank you for all your help man, I really appreciate it.
danwguy said:
The one I was trying to load up was from here https://s.basketbuild.com/devs/temasek/Samsung Galaxy Note 3 - HLTEVZW/CM12/Old
it's for dev editions only? That is a huge disappointment, I was really hoping to get some android Learn on my phone
Do you have any idea why, after I flash the twrp 3.8.4.0 recovery from safestrap recovery, after I reboot I am still showing safestrap and the older twrp. It's like the new version flashes, but then just disappears and the old version loads up.
Thank you for all your help man, I really appreciate it.
Click to expand...
Click to collapse
Because TWRP doesn't work on the Verizon Note 3...that is why SafeStrap exists. Safestrap is based on TWRP but is not TWRP.
Sent from my Note 3 via Tapatalk
donc113 said:
Because TWRP doesn't work on the Verizon Note 3...that is why SafeStrap exists. Safestrap is based on TWRP but is not TWRP.
Sent from my Note 3 via Tapatalk
Click to expand...
Click to collapse
They exist in different areas of memory safe strap essentially hijacks the boot process before the phone can boot and tells it to instead boot this way if you want to update the version of twrp it us using you need to update safestrap it is what is holding us back from 4.4.4 and it will be what slows 5.0 unless someone updates safestrap or comes up with something new. All I know is I'm going to get a nexus next time I'm done with this locked bootloader bull****.
Thank you guys both for your help. I completely understand what you guys are saying. I guess I got confused because I found an official twrp 3.8.4.0 for hltevzw, so I thought it should work. I'm wondering how hard it would actually be to put the newer version of twrp into safestrap. I know the person that was building it is no longer developing it, so does that mean that we are pretty much not getting 5.0 unless we wait for Verizon to push it?
danwguy said:
Thank you guys both for your help. I completely understand what you guys are saying. I guess I got confused because I found an official twrp 3.8.4.0 for hltevzw, so I thought it should work. I'm wondering how hard it would actually be to put the newer version of twrp into safestrap. I know the person that was building it is no longer developing it, so does that mean that we are pretty much not getting 5.0 unless we wait for Verizon to push it?
Click to expand...
Click to collapse
Not necessarily the developers working on jasmine have been claiming to be working on a replacement for safestrap.
Verizon will eventually push out 5.0 but I doubt it will be anytime soon even then if I don't have root I don't want so I am not sure what I'll end up doing I'll try to wait it out maybe a mistake will happen and 5.0 will have some thing that leads to a bl unlock. If only they would make root an option like the dev menu...
and my prediction for when verizon will put out 5.0 I would say October is not out of range. Also it will likely be the note 3's last update that Verizon gives.
Hello there,
So, I have a Samsung Galaxy S5 G900R4 with U.S. Cellular. I've heard of rooting your phone, and I decided I'd give it a try. Now, the rooting went fine, and the phone was working like a charm, until I started to have some issues. SuperSU needed to update its binary, and I allowed it to try, but it continued to tell me that it could not update it. Hence, I let it reboot when it offered. Now, for whatever reason, the phone won't boot past the U.S. Cellular 4G logo that appears, it just sits there on that screen.
Now so far, I haven't been able to find anyone that has encountered this specific problem, as most people say their soft-bricks are bootlooping and whatnot. I'm not sure if my specific case is technically a soft brick, or something else, but I wanted to just return it to stock format. I loaded up Odin again, downloaded the 1.5g firmware file, and I got the SW REV CHECK FAIL error.
I did some research, and I searched EVERYWHERE, and the closest I could find to a solution was http://forum.xda-developers.com/showthread.php?t=2798396 <-- this thread. Which makes sense, when I read it. I'm guessing the bootloader is locked on my phone, or something. The problem is that this thread is for the Galaxy S5 G900AU, and I don't have that phone.
Maybe I'm just not searching on the web enough, or I didn't search the site well enough, but I have not been able to locate a similar set of AP, CP and CSC files for my specific model.
I would really appreciate it if someone could point me in the right direction or, if the issue I'm actually having with my phone is NOT a soft-brick and there is another solution, suggest another way for me to fix the phone.
Thank you.
First off, I'd try clearing the caches from recovery
If that fails, factory reset from recovery
If that fails, (And I'm not sure about stock firmwares with ODIN & locked bootloaders) I'd try flashing stock from ODIN also
Grab stock ROMs from here
sammobile . com / firmwares / database /SM-G900R4/
Can't link it here, as SM links are not allowed - just remove the spaces
*Detection* said:
First off, I'd try clearing the caches from recovery
If that fails, factory reset from recovery
If that fails, (And I'm not sure about stock firmwares with ODIN & locked bootloaders) I'd try flashing stock from ODIN also
Grab stock ROMs from here
sammobile . com / firmwares / database /SM-G900R4/
Can't link it here, as SM links are not allowed - just remove the spaces
Click to expand...
Click to collapse
Well last night I went ahead and used recovery to clear cache, and then I did a factory reset. I just did it again, now, but I guess I'll have to download the file from SM to try. I already have a stock ROM, but I can't remember where I downloaded it from, so it may actually be a 4.4.2 ROM or something, which would explain why it won't work. I'll wait for the 5.0 ROM to download and give it a try, should take a little more than an hour and a half, then I'll report back.
Xeretius said:
Well last night I went ahead and used recovery to clear cache, and then I did a factory reset. I just did it again, now, but I guess I'll have to download the file from SM to try. I already have a stock ROM, but I can't remember where I downloaded it from, so it may actually be a 4.4.2 ROM or something, which would explain why it won't work. I'll wait for the 5.0 ROM to download and give it a try, should take a little more than an hour and a half, then I'll report back.
Click to expand...
Click to collapse
Try this link, if it works, it won't work for long
Code:
http://am4-r1f4-stor08.uploaded.net/dl/800e713b-624b-4a91-a57c-1639c6b5071e
*Detection* said:
Try this link, if it works, it won't work for long
Click to expand...
Click to collapse
It worked, it's downloading now, just have to give it some time.
nice one
*Detection* said:
nice one
Click to expand...
Click to collapse
I really hope this works, when it finishes >.>
Any idea what's happening with the phone to cause it to stay at the U.S. Cellular screen?
I never let SuperSU reboot when I let it update the binaries
Could be a number of things, possibly just corrupted a file necessary for boot, but as SuperSU has root, it could be anything
I don't know the ins and outs of how SuperSU works, but I know a few carrier specific US S5s have a locked bootloader, Verizon, AT&T etc - not sure if rebooting to allow the binary update requires an unlocked bootloader, maybe that bricked it, half assed attempt at a root process failed maybe
*Detection* said:
I never let SuperSU reboot when I let it update the binaries
Could be a number of things, possibly just corrupted a file necessary for boot, but as SuperSU has root, it could be anything
I don't know the ins and outs of how SuperSU works, but I know a few carrier specific US S5s have a locked bootloader, Verizon, AT&T etc - not sure if rebooting to allow the binary update requires an unlocked bootloader, maybe that bricked it, half assed attempt at a root process failed maybe
Click to expand...
Click to collapse
As far as I know, though, U.S. Cellular has confirmed that this device has an unlocked bootloader. And besides that, if it were locked, wouldn't that have come up as an issue when I rooted the device? I used the CWM custom recovery tool.
On a similar note, I'm not even sure if the problem was a locked bootloader. It's just that, from what I've read with other people having the same issue, they solved it by excluding the BL file from the flash and instead only using the AP, CP and CSC files.
Xeretius said:
As far as I know, though, U.S. Cellular has confirmed that this device has an unlocked bootloader. And besides that, if it were locked, wouldn't that have come up as an issue when I rooted the device? I used the CWM custom recovery tool.
On a similar note, I'm not even sure if the problem was a locked bootloader. It's just that, from what I've read with other people having the same issue, they solved it by excluding the BL file from the flash and instead only using the AP, CP and CSC files.
Click to expand...
Click to collapse
If you can flash anything custom from ODIN, bootloader is unlocked, afaik, locked bootloaders require a right mess on to get anything flashed to them
To root with a locked bootloader, is easily possible if you're on a certain KitKat ROM, and use Towelroot - other than that, (From what I've read), you need to use specific tools, so it sounds like your bootloader is indeed unlocked - which makes this next ROM flash, much more likely to work using only ODIN
Use ODIN 3.10.6 though
My experience with the S5 is with an unlocked bootloader (G900F), so I can only quote what I know about locked from what I've read, but it sounds like that doesn't matter in your case
*Detection* said:
If you can flash anything custom from ODIN, bootloader is unlocked, afaik, locked bootloaders require a right mess on to get anything flashed to them
To root with a locked bootloader, is easily possible if you're on a certain KitKat ROM, and use Towelroot - other than that, (From what I've read), you need to use specific tools, so it sounds like your bootloader is indeed unlocked - which makes this next ROM flash, much more likely to work using only ODIN
Use ODIN 3.10.6 though
My experience with the S5 is with an unlocked bootloader (G900F), so I can only quote what I know about locked from what I've read, but it sounds like that doesn't matter in your case
Click to expand...
Click to collapse
It worked! Thank you so much for the help, I really appreciate it.
Well, my warranty is now void. Is there a safer way to root the phone, or should I just leave it be?
Xeretius said:
It worked! Thank you so much for the help, I really appreciate it.
Well, my warranty is now void. Is there a safer way to root the phone, or should I just leave it be?
Click to expand...
Click to collapse
Great
Flashing a stock ROM won't void your warranty, but if it is indeed void (KNOX 0x1), then just flash this with ODIN
http://download.chainfire.eu/404/CF-Root1/CF-Auto-Root-klteusc-klteusc-smg900r4.zip
Tripping KNOX only happens when you flash something not signed by Samsung, IE: A custom recovery, ROM or Kernel etc
I have the same issue, same phone I ended up flashing a custom ROM because I luckily flashed twrp before it bricked on the us cellular screen.. How did you fix this I just want to get back to stock remove my root completely
My Verizon Samsung Note 3 is rooted and I placed the original Jasmine rom on it using safestrap a couple of years ago.
Here's the situation, I wasn't going to change any rom because I intended to get another phone, but when the Note 7 originally came out, the intent was to purchase it. Well that all went south, so I decided to install the Darklord rom, which would turn the 3 into a 7, but my safestrap no longer worked and all the, recovery such as twrp, didn't work, stating phone not recognized.
What I have is just a rooted phone. Any suggestions?
Try the Verizon forum .
Bluedio777 said:
My Verizon Samsung Note 3 is rooted and I placed the original Jasmine rom on it using safestrap a couple of years ago.
Here's the situation, I wasn't going to change any rom because I intended to get another phone, but when the Note 7 originally came out, the intent was to purchase it. Well that all went south, so I decided to install the Darklord rom, which would turn the 3 into a 7, but my safestrap no longer worked and all the, recovery such as twrp, didn't work, stating phone not recognized.
What I have is just a rooted phone. Any suggestions?
Click to expand...
Click to collapse
You can unlock your bootloader (read carefully this thread)
Then flash TWRP using Flashfire. This way, you'll have a full functional custom recovery and the ability to use any custom rom.
Well the title says alot... let me explain..
I've got a note 5 and LG g5. This note 3 is an extra phone. So I figured I would root and rom it.
I started on 4.4.2 and it wouldn't boot...
Ran Odin 3.09 and loaded pl1...couldn't root.
Ran Odin 3.09 again with ob6. Root success.
I then followed instructions for unlock_n3 for the bootloader and also installed twrp.
Last night I went on a spree with roms trying to find a working rom with data... no success... I felt like I was doing something wrong so I went back to Odin and ran ob6 again which is where I'm at now.
In the process I dev'd my phone... and now I cannot get root and lost twrp in the process.
Did I eff up?
What's next from here? I don't care about Knox and like I said I've got 2 other phones both working and paid off. This is my "car phone". I use it for music and that's about it. That being said I would rather have working data instead of using my note 5 with Hotspot mode.
My device is now hlte... not hltevzw... I think I did something very wrong. Please halp.
If it helps I did take pictures along the way when running the unlock_n3 over adb. I've got the original emmc ID but I'm not sure if this step is reversable.
I also made a backup with twrp... but it seems my SD card was wiped at some point last night.
Please don't flame... I admit this was my stupidity and I'm sure I'm not the only one who makes mistakes. At this point I'll be happy with anything 5.0 and root. As I said above if Knox is a concern I don't really care. Phones paid off... and I've got a note 5 and when that dies I'll get a 7. Also have LG g5 as a backup.
What are my options now oh wise xda gods?
Edit: I ran arabictool again, and got a 5.0 not found error. Decided to try kingoroot, and it says succeeded, however upon running root checker, it says "Sorry! Root access is not properly installed on this device"
Edit2: After trying edit 1... im now im a bootloop, and I check vol+, home, and power and twrp is indeed gone.
When I get home I plan to Odin OB6 again, as it worked, and since i've already done it once I assume I cant do any further damage :\
Edit3: I've successfully flash back to OB6, and as expected, ive finally tripped knox. Damn near 5 years with a note 3, and JUST tripped it. Not bad if I do say so my self... although, theres still more work to be done :\
GGRRRR, I wont give up so easily! But I could use some advice
tbonedude said:
Well the title says alot... let me explain..
I've got a note 5 and LG g5. This note 3 is an extra phone. So I figured I would root and rom it.
I started on 4.4.2 and it wouldn't boot...
Ran Odin 3.09 and loaded pl1...couldn't root.
Ran Odin 3.09 again with ob6. Root success.
I then followed instructions for unlock_n3 for the bootloader and also installed twrp.
Last night I went on a spree with roms trying to find a working rom with data... no success... I felt like I was doing something wrong so I went back to Odin and ran ob6 again which is where I'm at now.
In the process I dev'd my phone... and now I cannot get root and lost twrp in the process.
Did I eff up?
What's next from here? I don't care about Knox and like I said I've got 2 other phones both working and paid off. This is my "car phone". I use it for music and that's about it. That being said I would rather have working data instead of using my note 5 with Hotspot mode.
My device is now hlte... not hltevzw... I think I did something very wrong. Please halp.
If it helps I did take pictures along the way when running the unlock_n3 over adb. I've got the original emmc ID but I'm not sure if this step is reversable.
I also made a backup with twrp... but it seems my SD card was wiped at some point last night.
Please don't flame... I admit this was my stupidity and I'm sure I'm not the only one who makes mistakes. At this point I'll be happy with anything 5.0 and root. As I said above if Knox is a concern I don't really care. Phones paid off... and I've got a note 5 and when that dies I'll get a 7. Also have LG g5 as a backup.
What are my options now oh wise xda gods?
Edit: I ran arabictool again, and got a 5.0 not found error. Decided to try kingoroot, and it says succeeded, however upon running root checker, it says "Sorry! Root access is not properly installed on this device"
Edit2: After trying edit 1... im now im a bootloop, and I check vol+, home, and power and twrp is indeed gone.
When I get home I plan to Odin OB6 again, as it worked, and since i've already done it once I assume I cant do any further damage :\
Edit3: I've successfully flash back to OB6, and as expected, ive finally tripped knox. Damn near 5 years with a note 3, and JUST tripped it. Not bad if I do say so my self... although, theres still more work to be done :\
GGRRRR, I wont give up so easily! But I could use some advice
Click to expand...
Click to collapse
You need to go thru your original steps again, root, unlock and then TWRP make sure it is the hltevzw version,
Sent from my SM-N900V using Tapatalk
donc113 said:
You need to go thru your original steps again, root, unlock and then TWRP make sure it is the hltevzw version,
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply, as of edit 3, I am back on OB6, and cannot seem to get root. Are my chances better with OF1?
Ive tried yemen tools (says 5.0 not found)
I've tried kingo root (says successful, never reboots, and shows "this phone root isnt properly setup" when checking with root checker from joey kilm (think thats his name)
Does it matter my emmc ID is ending with 43100?
https://cdn.discordapp.com/attachments/221482708063223809/378367914388094981/image.png <- image from unlock_n3 after success, emmc checker shows same value AFTER odin ob6 (this held, nothing else did)
Edit: After taking donc's recommendation of OF1, I am now able to run yemen tools. As a side note, I seem to have more bars of service with OF1... coincidence?
Edit2: I HAVE ROOT! on OF1 using yemen tools (downgraded from PL1 to OB6 finally to OB1 and it worked.) Now to re-unlock bootloader. Thanks guys for the support thus far, this is a journey and having qualified accomplices makes this SOOOO much easier.
So heres where im at now.. as a recap for personal use, and anyone else who may be on a similar path.
Start to finish, this is what I did, where im at now, and where I want to be by tonight
Got phone, 4.4.2 with bootloop, couldn't find 4.4.2 firmware online
Flashed 5.0 (PL1), no root available.
Flashed 5.0 (OB6) rooted, unlocked boot loader, twrp, played with roms, got frustrated, re-flashed OB6 and couldn't root again (seems flimsy)
Flashed 5.0 (OF1) rooted, unlocked boot loader, verified several times root is working. Installed SuperSu and busybox.
This is where im at now, about to install twrp since i've done this already with ob6, and was working fine (though, I would prefer to have philz, and multi rom slots)
This entire process i've been using Odin 3.09, Twrp 3.0.2-1. My note 3 has been changed to a dev ID ending in 3100 (see above posts) this seems to have held through entire process with multiple recoveries.
I am going to make a full backup (again...) and unlike last time... store this copy onto my PC instead of SDcard alone... this was my mistake, and I need to learn from it.
For the @dev's out there, is there anything I can provide to help this overall process and community in general? I'm fairly literate in adb/linux and have no issues running commands, uploading files, or anything similar.
Shout out to @donc113 above for stating the obvious (since i failed to search and find the proper methods) as well as giving me the kick in the pants I needed to push onwards and succeed. Thanks brotha. :good:
tbonedude said:
So heres where im at now.. as a recap for personal use, and anyone else who may be on a similar path.
Start to finish, this is what I did, where im at now, and where I want to be by tonight
Got phone, 4.4.2 with bootloop, couldn't find 4.4.2 firmware online
Flashed 5.0 (PL1), no root available.
Flashed 5.0 (OB6) rooted, unlocked boot loader, twrp, played with roms, got frustrated, re-flashed OB6 and couldn't root again (seems flimsy)
Flashed 5.0 (OF1) rooted, unlocked boot loader, verified several times root is working. Installed SuperSu and busybox.
This is where im at now, about to install twrp since i've done this already with ob6, and was working fine (though, I would prefer to have philz, and multi rom slots)
This entire process i've been using Odin 3.09, Twrp 3.0.2-1. My note 3 has been changed to a dev ID ending in 3100 (see above posts) this seems to have held through entire process with multiple recoveries.
I am going to make a full backup (again...) and unlike last time... store this copy onto my PC instead of SDcard alone... this was my mistake, and I need to learn from it.
For the @dev's out there, is there anything I can provide to help this overall process and community in general? I'm fairly literate in adb/linux and have no issues running commands, uploading files, or anything similar.
Shout out to @donc113 above for stating the obvious (since i failed to search and find the proper methods) as well as giving me the kick in the pants I needed to push onwards and succeed. Thanks brotha. :good:
Click to expand...
Click to collapse
You're welcome. Just an FYI, the ending of the CID doesn't matter, it's the first 2 numbers that count, and they MUST be 15
I used Flashify (available on Google Play) to load TWRP... worked great (but you must have root and busybox installed to use it to flash TWRP)
Sent from my SM-N900V using Tapatalk
Ok, I have rooted Galaxy S4s and 5s, usually the T-Mobile versions. I just ordered a used SM-G950F off ebay. It did not say if it was Nougat or Oreo.
Been searching, and have not found my answer, so I hope someone might be able to send me a link or advise me.
Want a rooted S8. Stock rom would be ok, but I would prefer custom down the road.
This is how I have been rooting the S4s and 5s
Put SuperSU zip on phone.
Then flash TWRP from Oden and not let it reboot. Do a battery pull, and then start the phone to recovery, then flash the SuperSU from TWRP.
Can I do this with the S8 ? (SM-G950F)
Thanks!
Come on you gurus, just take 1 minute and help me out ..... ffs
or maybe I posted the question in the wrong place, or your bored with the question.
I was a mod on another type of forum, I posted a sticky ... you dumb asses
ctbale said:
Ok, I have rooted Galaxy S4s and 5s, usually the T-Mobile versions. I just ordered a used SM-G950F off ebay. It did not say if it was Nougat or Oreo.
Been searching, and have not found my answer, so I hope someone might be able to send me a link or advise me.
Want a rooted S8. Stock rom would be ok, but I would prefer custom down the road.
This is how I have been rooting the S4s and 5s
Put SuperSU zip on phone.
Then flash TWRP from Oden and not let it reboot. Do a battery pull, and then start the phone to recovery, then flash the SuperSU from TWRP.
Can I do this with the S8 ? (SM-G950F)
Thanks!
Click to expand...
Click to collapse
There's literally dozens of guides on how to root the G950F. Come on you guru, do a Google search for one minute and help yourself out.
DAViiD__ said:
There's literally dozens of guides on how to root the G950F. Come on you guru, do a Google search for one minute and help yourself out.
Click to expand...
Click to collapse
I think I just set the hook ......
ctbale said:
I think I just set the hook ......
Click to expand...
Click to collapse
But seriously, I heard about a bootloader, (version 2?) that if I try to flash twrp might brick my phone. Have not actually pulled the trigger on buying a SM-G950F yet, but want to know if I can attain root on this device if its on android V8.0
I did try searching, but it just sits there with no results no matter what I put in the field. Might be because I am in Alaska and my internet SUCKS!
I am at the point I would pay someone like $20 via paypal if they know what they are doing and they want to give me Tech Support
ctbale said:
But seriously, I heard about a bootloader, (version 2?) that if I try to flash twrp might brick my phone. Have not actually pulled the trigger on buying a SM-G950F yet, but want to know if I can attain root on this device if its on android V8.0
I did try searching, but it just sits there with no results no matter what I put in the field. Might be because I am in Alaska and my internet SUCKS!
I am at the point I would pay someone like $20 via paypal if they know what they are doing and they want to give me Tech Support
Click to expand...
Click to collapse
The process I've followed is as follows.
Now please take into account that I flash twrp and part of that process is that data partition needs to be formatted, so make sure anything that's needed back it up.
Have a look at some roms, download one to your memory card.
Flash twrp via Odin, you will need to wipe data in twrp and return to twrp.
Flash the Rom in twrp as normal.
Now if you want just root, flashing cf-autoroot via Odin is the of other choice, flashing magisk or supersu will involve twrp so like I said earlier you'll end up wiping data.
Hope this helps in some sort of way
Thanks! I have been searching for hours in my free time to see if I can do this. I just read in a few threads that if the phone is on Oreo it would have a locked bootloader. I went thru that helping my buddy root his ATT 337 S4. Almost bricked his phone.
I will be starting with a new phone, dont care about tripping knox. Just want root so I can use titanium backup to freeze/uninstall any of the bloat. I would get a costom rom after root eventually.
I will get a SH-G950F ordered. I just didnt want to get the phone and not be able to root. Almost ordered The SH-G950U and its got snapdragon, and I read thats not the best version if I have a choice.
I love my rooted S4 but its kind a turtle so need to move forward.
Thanks So much for your help sofir786 !!!!!
sofir786 said:
The process I've followed is as follows.
Now please take into account that I flash twrp and part of that process is that data partition needs to be formatted, so make sure anything that's needed back it up.
Have a look at some roms, download one to your memory card.
Flash twrp via Odin, you will need to wipe data in twrp and return to twrp.
Flash the Rom in twrp as normal.
Now if you want just root, flashing cf-autoroot via Odin is the of other choice, flashing magisk or supersu will involve twrp so like I said earlier you'll end up wiping data.
Hope this helps in some sort of way
Click to expand...
Click to collapse
Mrmezz
I rooted my s8 G950F on oreo with twrp magisk and dm verity. If u dont wipe data and flash dm verity after twrp your phone will boot sayin we cannot verify the integrity of this device please restart. I cant mind the ecact process i followed but it was onli them 3 i flashed