So I'm a long time HTC owner and my sister just got an S5 I plan to root tonight.
I'm also thinking of returning my M8 for an S5 after I check out my sisters. But I'm not sure I want to give up the M8 speakers.
Anyway I'm curious for others with experience from both sides about some terminology HTC vs Samsung.
1) Do "leaked" RUU's exist. These are official "Kits" that will basically put a phone back to factory (Firmware, Root Status, Recovery) etc.
It will do everything except remove S-OFF (see below). They are handy to have for warranty work and you botched something.
Often cleanly built ROM's are built from a base RUU rather than a "Dump".
2) Does anything like S-OFF exist. HTC phones can be typically exploited such that you have "S-OFF". This basically means you can install any firmware (radio etc.) beyond Android, Recovery.
3) Once rooted, will you get OTA updates? Will and OTA remove root? Could you loose root access through an OTA update?
With S-OFF none of this matters.
4) Without S-OFF it can be awkward to update the Kernels sometimes. Can the Kernels be easily updated with "Just" Root.
5) Does the phone display "Tampered" or "Unlocked" once rooted. If so how easy is it to remove that and get it back to factory after being rooted.
mswlogo said:
So I'm a long time HTC owner and my sister just got an S5 I plan to root tonight.
I'm also thinking of returning my M8 for an S5 after I check out my sisters. But I'm not sure I want to give up the M8 speakers.
Anyway I'm curious for others with experience from both sides about some terminology HTC vs Samsung.
1) Do "leaked" RUU's exist. These are official "Kits" that will basically put a phone back to factory (Firmware, Root Status, Recovery) etc.
It will do everything except remove S-OFF (see below). They are handy to have for warranty work and you botched something.
Often cleanly built ROM's are built from a base RUU rather than a "Dump".
2) Does anything like S-OFF exist. HTC phones can be typically exploited such that you have "S-OFF". This basically means you can install any firmware (radio etc.) beyond Android, Recovery.
3) Once rooted, will you get OTA updates? Will and OTA remove root? Could you loose root access through an OTA update?
With S-OFF none of this matters.
4) Without S-OFF it can be awkward to update the Kernels sometimes. Can the Kernels be easily updated with "Just" Root.
5) Does the phone display "Tampered" or "Unlocked" once rooted. If so how easy is it to remove that and get it back to factory after being rooted.
Click to expand...
Click to collapse
I will do my best....
1) Yes. Leaked do exist but are minimal for this phone at the moment. Samsung makes the current available for download right from them or is available in this forum. Just flash via Odin and will restore it to factory stock.
2) If I'm not mistaken the Sprint S5 bootloader is not locked. Therefore all you need to do is root and can flash away.
3) If you take an OTA while rooted you will lose root. However, it will not be possible to take the OTA successfully with a custom recovery installed. Best bet is to wait until someone modifies the OTA and re-packages for root users. Usually only takes a few days after official OTA is dropped.
4) Yes. Just a quick flash.
5) Yes. Status will change and cannot go back at this time once it is tripped. Can still go back to factory with stock recovery but status will still not be "Official".
Anyone please someone chime in and correct me on any of these if I am mistaken.
CCallahan said:
I will do my best....
1) Yes. Leaked do exist but are minimal for this phone at the moment. Samsung makes the current available for download right from them or is available in this forum. Just flash via Odin and will restore it to factory stock.
2) If I'm not mistaken the Sprint S5 bootloader is not locked. Therefore all you need to do is root and can flash away.
3) If you take an OTA while rooted you will lose root. However, it will not be possible to take the OTA successfully with a custom recovery installed. Best bet is to wait until someone modifies the OTA and re-packages for root users. Usually only takes a few days after official OTA is dropped.
4) Yes. Just a quick flash.
5) Yes. Status will change and cannot go back at this time once it is tripped. Can still go back to factory with stock recovery but status will still not be "Official".
Anyone please someone chime in and correct me on any of these if I am mistaken.
Click to expand...
Click to collapse
Status will be official (in settings "About Phone"). Just when you boot into download mode, knox counter tripped will be shown (0x1).
lol i remember asking all these questions exactly in reverse when i went from the s3 to the one...thanks goodness i came for the s4
On a more superficial note, you can also get a more htc vibe by installing the blinkfeed app thats been ported over by gakugaku. More info here ->
http://forum.xda-developers.com/showthread.php?t=2735764
Coming over to samsung after 6years with Htc was a little jarring, but this kinda softened the transition.
Thanks guys that was exactly what I needed. My sisters phone rooted just fine.
I did compare her phone to mine briefly and posted here about it.
http://forum.xda-developers.com/showthread.php?t=2749699
To sway me to the S5, I really wanted to like the S5 camera (at least as much), the Cell Reception and live with the speakers.
But that is proving really difficult.
The M8 has me very nervous of failing again especially when I keep seeing reports of owners having the same issue I did (lost 3G).
I think I'm trading my m8 to a guy straight across for the s5. I never had any problems with my s3 and the m8 has been a headache, but not for everyone. I know how you feel mswlogo.
Months ago, before the 4.3 OTA, I attempted to unlock the bootloader and root my wife's Galaxy SIII on vzw. The phone seemed to be bricked, but I was able to recover it using one of the available unbrick utilities. From that point forward, on boot it displays "Custom ROM", but is not rooted and I cannot boot into recovery at all. To make things worse, my wife accepted the 4.3 OTA before I could warn her not to and it has since upgraded to 4.4.2 OTA. Is there any option to still unlock the bootloader, or are we stuck? Also, if I can't unlock and root the phone, I would like to be able to return it to stock, but nothing so far has worked.
Have a samsung galaxy s1 i897 'captivate' from at&t phone.
Phone originally bought outright, didn't use for years, now trying to unlock so that a friend can use it.
First updated to the pacrom custom rom with kitkat 4.4 (is this part of the problem??) to test/be sure it would work before reenabling the phone. Got the unlock code from at&t - copied it exactly and it's FAILED now 3 times in a row, afraid to touch it with two left.
Is being under 4.4 part of the problem/does it have to have factory rom?
Asked some samsung people who suggested it may need to flash back to the original factory rom, but even thats not enough, mentioned "triangle" to "set back the clock" to pretend it's never been rooted or run a newer OS. Suggested it should then unlock. But also suggested certain Samsungs of this era were notorious for just not unlocking even with everything perfect which is why I was asking here before using up my last 2 attempts.
Does this all sound right/can only unlock the phone from the original factory ROM and OS version? Once unlocked when I update to PacRom/kitkat 4.4 I assume it stays unlocked or will it create a problem somehow?
If for some reason the last remaining 2 chances bite it, I assume this is what people normally mean by bricked and hopefully there's a recovery process or does locked to at&t forever really mean that?
Ok, finally after all this time, the AT&T branded Samsung Galaxy Tab 3 7.0 (SM-T217A) can be properly rooted. I have been playing with it since that moment my binaries were finally updated properly. However, several questions remain since i am still learning this stuff.
First, since root it installed, i want to flash a custom recovery, but the problem is that the bootloader is locked, that being the issue that had it unrootable for so long. So a) is there a method using terminal emulator to unlock the bootloader so i can flash a recovery of my choosing or b) is there a way to flash the recovery that bypasses the bootloader.
Second, AT&T decided to make the genius move of also locking the Tab 3's (7.0 variant anyways) native phone and dialer app. The Tab 3 is able to function as a phone, but AT&T really made a mess by locking up, and over bloating the hell out of this device.
Third. I want to install the XFramework, but read that there can be issues with that and locked bootloaders. Help please, i really don't want to shoot brick my tablet. There are more questions, so ill just add to this thread later if anyone else can help me fix these issues
How did you root it ? Do you have instructions ? Also looking for answer to boot loader myself.
Thanks
Steve
First of all:
I'm no Dev...just someone who likes to play lego.
From this point of view everything I post here is taken from somewhere else in the Internet and used by your own risk.
I've read a good startup here.
Hopefully this makes this thread clear enough so that i dont need to describe the whole procedure step by step.
(https://www.naldotech.com/root-samsung-galaxy-z-flip-3-5g-magisk/)
(1.OEM-Unlock,2.BL-Unlock,3.extract boot.img,4.patch boot.img via magisk on the unrooted mobile,5.patch boot.img.tar to AP&BL via Odin, 6.pray)
Anyways...here are maybe small hints to avoid a few traps.
a) Just do the oem-unlock in the dev-options (enabled by tapping buildnumber 5 times) is just half of the rent.
Afterwards i had to go in Download-mode (switch of mobile, press volUp+volDown and connect PC-cable.)
There appears a possibility of choice.
Press VolUp short: get the mobile on standby to flash the rom via odin.
Press VolUp LOONG: get the mobile to the menu where the bootloader can finally get unlocked. (Otherwhise every try to patch a rooted img will be blocked by bootloader-protection.)
Of course this can possibly be done via adb/fastboot commands.
Funny side note: OEM-Unlock-option will completely disappear from Dev-options and waranty is lost. Also the mobile stops to get Updates OTA which means that you have to update manually whenever a new version will appear in the net.
b) patching boot.img via magisk should work as described in many other magisk-rooting-manuals.
Flashing the tar back to the mobile via odin was little bit tricky.
It doesnt reach out just to provide the magisk_patched.tar to Odin just on the AB-line.
I had to patch it to BL too.
Cheers
MikGx
When you boot into bootloader after unlocking, is the message something about "a custom OS can cause critical problems"?
As it stands now, the only reason I have to believe the US bootloader can't be unlocked (or isn't already) was the lack of an OEM unlock button and some cranky kid on the internet saying it hasn't been possible since the S7.
It doesn't make sense why I would have a warning about a custom OS if there is no possible way to install one, though.
@boot into bootloader after unlocking it...:
Yess you are right. Thats exactly the message.
Then you can enter the Device unlock mode again (long press VolUp) to lock bootloader again (then it resets automaticaly to factory-defaults and all work is gone.)
or
continue to flash something (short press VolUp).
Dont know about the US versions. Could be that there is a difference to my EU-models.
But either i rooted nearly every every mobile since the S2
MikGx said:
@boot into bootloader after unlocking it...:
Yess you are right. Thats exactly the message.
Then you can enter the Device unlock mode again (long press VolUp) to lock bootloader again (then it resets automaticaly to factory-defaults and all work is gone.)
or
continue to flash something (short press VolUp).
Dont know about the US versions. Could be that there is a difference to my EU-models.
But either i rooted nearly every every mobile since the S2
Click to expand...
Click to collapse
I think you misunderstood what I was asking, but ended up answering it anyway.
It seems the message about installing custom OS versions may be a boilerplate for the bootloader, not any indication that it's possible.
naldotech.com, the link you provide is pretty clear about the process. What it doesnt say is what to do at the end. When you untick "reboot" in odin, and you finish flashing, your phone will stay in download mode. Then what to do?. Press power and volume down to leave and restart the phone? or, power and volume down, screen goes black imediately power and volume up, enter recovery and restart from there.? please someone ?
Press the power and volume down buttons for about 7 seconds and it will reboot
beanbean50 said:
Press the power and volume down buttons for about 7 seconds and it will reboot
Click to expand...
Click to collapse
I did as you mention but it didnt work. It made me reset the system. But I Fallowed the naldotech.com guide. At the end, being in dawnload mode, I pressed power and volume down, when the screen got black I pressed power and volumen up, I entered recovery mod, cleared cache and re- started the system: Voila my phone is rooted
Hello.
Can someone pleas provide a working link for frija download? The one referring from naldotech seems to be broken (https://www.naldotech.com/download-samsung-galaxy-stock-firmware-frija-tool/)
Update: Found a link via google -> https://technastic.com/odin-download-samsung-latest-all-versions/
twistedumbrella said:
When you boot into bootloader after unlocking, is the message something about "a custom OS can cause critical problems"?
As it stands now, the only reason I have to believe the US bootloader can't be unlocked (or isn't already) was the lack of an OEM unlock button and some cranky kid on the internet saying it hasn't been possible since the S7.
It doesn't make sense why I would have a warning about a custom OS if there is no possible way to install one, though.
Click to expand...
Click to collapse
The USA version (snapdragon soc) can't be rooted as far as I know. There is no way to unlock the bootloader in dev options, at least on Verizon and that holds true even if you bought a unlocked phone. As soon as you insert a Verizon sim and the phone updates it's all over.
I had the same issue with the original Pixel. I bought it unlocked but before rooting it I allowed it to update like a fool. Luckily my son wanted the same phone so I gave him mine then rooted and installed TWRP before putting a Verizon sim in.
Back to Samsung...as far as I know you haven't been able to root the USA version since the note 8. The rest of the planet gets the Exynos SOC but we get the snapdragon and no root method works. My note 9, 10+ and z Flip3 didn't have an unlock bootloader option even before putting a sim in it.
d0x360 said:
The USA version (snapdragon soc) can't be rooted as far as I know. There is no way to unlock the bootloader in dev options, at least on Verizon and that holds true even if you bought a unlocked phone. As soon as you insert a Verizon sim and the phone updates it's all over.
I had the same issue with the original Pixel. I bought it unlocked but before rooting it I allowed it to update like a fool. Luckily my son wanted the same phone so I gave him mine then rooted and installed TWRP before putting a Verizon sim in.
Back to Samsung...as far as I know you haven't been able to root the USA version since the note 8. The rest of the planet gets the Exynos SOC but we get the snapdragon and no root method works. My note 9, 10+ and z Flip3 didn't have an unlock bootloader option even before putting a sim in it.
Click to expand...
Click to collapse
twistedumbrella said:
I think you misunderstood what I was asking, but ended up answering it anyway.
It seems the message about installing custom OS versions may be a boilerplate for the bootloader, not any indication that it's possible.
Click to expand...
Click to collapse
I have to be a little skeptical when my rooted Note 8 came out a year after the S7. There are other reasons, but they tend to make the trolls restless. We'll skip them.
twistedumbrella said:
I have to be a little skeptical when my rooted Note 8 came out a year after the S7. There are other reasons, but they tend to make the trolls restless. We'll skip them.
Click to expand...
Click to collapse
Ok I might be off by a year or 2 but I can say with 100% certainty that the note 9, 10, 10+ and flip3 don't have an unlock bootloader option.
I bought all 4 from Samsung all unlocked and not tied to any carrier. First boot with no sim I checked dev options and there was no option to unlock the bootloader. My note 9 might have had the option in the menu but it was grayed out and I couldn't find anyway to make it work.
A quick Google search for rooting the snapdragon version of any of these devices essentially says "NOPE".
The only way to root one is to buy a non US version. If it has a snapdragon soc you're out of luck.
d0x360 said:
Ok I might be off by a year or 2 but I can say with 100% certainty that the note 9, 10, 10+ and flip3 don't have an unlock bootloader option.
I bought all 4 from Samsung all unlocked and not tied to any carrier. First boot with no sim I checked dev options and there was no option to unlock the bootloader. My note 9 might have had the option in the menu but it was grayed out and I couldn't find anyway to make it work.
A quick Google search for rooting the snapdragon version of any of these devices essentially says "NOPE".
The only way to root one is to buy a non US version. If it has a snapdragon soc you're out of luck.
Click to expand...
Click to collapse
You got where I said "I guess the disclaimer is misleading" right?
twistedumbrella said:
You got where I said "I guess the disclaimer is misleading" right?
Click to expand...
Click to collapse
I didn't see that sentence in any of the posts but perhaps I just missed it.
It doesn't change anything either way. Anything is possible, even you somehow getting a device with this setting. That being said you also seem to be the only person ever to receive a USA device with said option.
It's hard to believe because it would mean the wrong firmware was installed (which makes no sense in itself) but with that firmware the device should have been a brick. The soc is completely different. It would be somewhat like trying to use Nvidia drivers on an AMD GPU... It just wouldn't work.
I dunno... I don't disbelieve you but I don't believe you either. It's just so far fetched for many reasons
d0x360 said:
I didn't see that sentence in any of the posts but perhaps I just missed it.
It doesn't change anything either way. Anything is possible, even you somehow getting a device with this setting. That being said you also seem to be the only person ever to receive a USA device with said option.
It's hard to believe because it would mean the wrong firmware was installed (which makes no sense in itself) but with that firmware the device should have been a brick. The soc is completely different. It would be somewhat like trying to use Nvidia drivers on an AMD GPU... It just wouldn't work.
I dunno... I don't disbelieve you but I don't believe you either. It's just so far fetched for many reasons
Click to expand...
Click to collapse
Lucky? I dunno. Had I known it would cause this much trolling, I wouldn't have bothered to mention it.
I have a general question. I am unfamiliar with rooting/unlocking bootloader on Samsung devices. Is it possible to revert unlocking the bootloader and going back to stock traceless?
david.siebauer said:
I have a general question. I am unfamiliar with rooting/unlocking bootloader on Samsung devices. Is it possible to revert unlocking the bootloader and going back to stock traceless?
Click to expand...
Click to collapse
Partially. I just did that: I have AfWall running on my old phone, tried to unlock the Flip with this manual here in order to use the firewall there, did something wrong - and stumbled upon Netguard while searching what might have happened and decided to give it a try first. (Unless there is a custom ROM for the phone available, I have no other need for root or an unlocked bootloader.)
From what I could find on my Flip 3, you can unlock and relock the bootloader as you like - but as soon as you install a non-genuine bootloader (i.e. one chnaged by Magisk) you will trip Knox - and this cannot be reverted.
In such a case you can still re-lock your bootloader and unlock it later (on my phone, that "7-day-no-switch-indeveloper-options" routine kicked in, but you can circumvent that) - but Knox will stay in its state. From what I read this means some things will not work such as Samsung Pay, but I do not know the details (yet) apart from that it does not bother me ;-), and the nag screen during boot is gone.
Thanks for your reply. Kinda sucks. Never had problems with my former mobiles to get back totally to stock without traces. Guess I disregard rooting for now
david.siebauer said:
Thanks for your reply. Kinda sucks. Never had problems with my former mobiles to get back totally to stock without traces. Guess I disregard rooting for now
Click to expand...
Click to collapse
Well, it's better than my Sony - there it is "once unlocked, always unlocked" with no way back at all
But I have to admit I understand the logic why the manufacturers do that, at least to the degree that they trip a fuse as Samsung does.
By rooting the phone, you shift the responsibility for the software state of the phone from the manufacturer to the user, so I think it is okay to implement something to make it clear to possible future buyers that it is or has been in that state.
(This does not include however all the other stones they put in the way of people wanting to develop or use custom ROMs!)
I remember I also had a Xperia Z3 compact.
Main reason for me for rooting, is the ability to use tools like tasker without non root restrictions or just trying customs roms without bloat, but usefull features. Guess u shouldn't have bought a Samsung lol.
david.siebauer said:
I remember I also had a Xperia Z3 compact.
Main reason for me for rooting, is the ability to use tools like tasker without non root restrictions or just trying customs roms without bloat, but usefull features.
Click to expand...
Click to collapse
Oh, trust me - as soon as I hear there is a custom ROM that works as a daily driver I will root mine as well. I really hope that there will be one for this phone
david.siebauer said:
Guess u shouldn't have bought a Samsung lol.
Click to expand...
Click to collapse
Sadly there is no Fairphone mini or Fairphone Flip - or would it be Fairfliphone? ... Flipfairphone?... - yet (if ever), so the only current alternative would be Motorola. And the price tag for the Razr is simply too much, even if I personally think it looks better than the Samsung. Additionally, I do not know if they are in any way better when it comes to rooting or loading custom ROMs.