I posted this to the wrong board, sorry for those who have seen my question before.
I bought the SGS 4G over a year ago now, and I sucessfully rooted and unlocked the phone for use in Korea. During that time i kies'd my way up to Gingerbread which made me lose root, but it was still unlocked. I recently upgraded phones and was looking to sell my current Galaxy 4G. Since I didn't want my google account attached to the phone I stupidly reset the phone back to factory default. It told me that it wouldn't revert back to froyo so I thought I would be safe.
Is the phone now re-locked back to the Canadian telecom company it was originally bought from? Could a Korean use their SIM just like I have been doing? Since my new phone has micro-SIM I can't test this myself.
Also, if indeed it IS re-locked is it possible to unlock it without using my google account to redownload the unlocking app I used.
Thanks everyone.
Aannon said:
I posted this to the wrong board, sorry for those who have seen my question before.
I bought the SGS 4G over a year ago now, and I sucessfully rooted and unlocked the phone for use in Korea. During that time i kies'd my way up to Gingerbread which made me lose root, but it was still unlocked. I recently upgraded phones and was looking to sell my current Galaxy 4G. Since I didn't want my google account attached to the phone I stupidly reset the phone back to factory default. It told me that it wouldn't revert back to froyo so I thought I would be safe.
Is the phone now re-locked back to the Canadian telecom company it was originally bought from? Could a Korean use their SIM just like I have been doing? Since my new phone has micro-SIM I can't test this myself.
Also, if indeed it IS re-locked is it possible to unlock it without using my google account to redownload the unlocking app I used.
Thanks everyone.
Click to expand...
Click to collapse
I'm pretty sure once unlocked, always unlocked. There is a phone number command to type to see the status, you can google to find it, I can't remember.
getochkn said:
I'm pretty sure once unlocked, always unlocked. There is a phone number command to type to see the status, you can google to find it, I can't remember.
Click to expand...
Click to collapse
From my unlocker thread:
FBis251 said:
You can now use the unlock code when you put in the non-T-Mobile sim into your phone and unlock your phone. You can check the unlock status by dialling *#7465625#. All the locks should say "OFF".
Click to expand...
Click to collapse
You'll need to be on a stock BML rom to be able to check since I haven't ever been able to check using an MTD rom.
Recently, I messed up real bad and I accidentally installed the firmware of a Verizon GS3 on a T-Mobile GS3. Now it is a Verizon phone :c I already rooted it so I can replace the firmware with a T-Mobile TouchWiz Stock ROM. All I need is the last step: to unlock the bootloader. Can someone (or anyone) please help me remove it? I am currently mentally constipated by the problem and I just have only a couple steps until I return it back into a T-Mobile Galaxy S3. Now that's the question. Here's the story of how it is what it is right now.
So one day, I was rooting my phone to install CyanogenMod because I wanted something similar to 4.2.1 Jellybean. I did everything except I didn't delete the Dalvhik Cache. So when everything was loaded, I see that my phone cannot open the PlayStore. In my mind, I reflect back a couple minutes in the past just to remember I didn't clear what I needed to. Idiotic me goes off and attempts to erase CyanogenMod 10 and I get stuck in a boot loop. I am in a state in which I call "mental constipation". I then accidentally and foolishly install the Verizon GS3 ROM and BOOM. I am in a worse situation. Fast forward today, I root the phone but as a Verizon Galaxy S3. I am almost done but I need to just unlock the bootloader and I am set to return it back into a T-Mobile GS3. So, can someone please tell me how to unlock the Verizon GS3's bootloader?
tl;dr turned T-Mobile GS3 into a Verizon GS3 and I need to unlock boot loader
Hi,
I just got a gs3 a few days ago with verizon and read up about what I could do with it.
I have root with supersu, busybox, terminal emulator and safestrap.
I wanted to flash cm 11 onto it, but with the new OTA Update from Samsung earlier this year I found out it was impossible with Knox and Verizon locking it down.
However, whenever I attempt to run roms flashed using Safestrap such as eclipse the boot sequence goes Press power button -> Vibrate once -> Release power -> Vibrate -> Samsung Galaxy SIII screen -> Safestrap -> Black Screen.
I don't know what I'm doing wrong, but nothing is working at all, is there a rom I can use? (preferably with an UI similar to that of CyanogenMod's KK) or am I stuck with Samsung's UI and Verizon's bloatware?
I also saw a lot of TW but I don't know what the people in the forums are talking about when they mention this.
Also, forgive my ignorance on the matter of programming and such but, is there a way to unlock the bootloader?
I hear it's encrypted and locked by Verizon. Is it possible to write a new firmware over the Encrypted Verizon one and use that instead?
Thanks for even reading this, A reply would mean a lot to me!
GeneralKwai said:
Hi,
I just got a gs3 a few days ago with verizon and read up about what I could do with it.
I have root with supersu, busybox, terminal emulator and safestrap.
I wanted to flash cm 11 onto it, but with the new OTA Update from Samsung earlier this year I found out it was impossible with Knox and Verizon locking it down.
However, whenever I attempt to run roms flashed using Safestrap such as eclipse the boot sequence goes Press power button -> Vibrate once -> Release power -> Vibrate -> Samsung Galaxy SIII screen -> Safestrap -> Black Screen.
I don't know what I'm doing wrong, but nothing is working at all, is there a rom I can use? (preferably with an UI similar to that of CyanogenMod's KK) or am I stuck with Samsung's UI and Verizon's bloatware?
I also saw a lot of TW but I don't know what the people in the forums are talking about when they mention this.
Also, forgive my ignorance on the matter of programming and such but, is there a way to unlock the bootloader?
I hear it's encrypted and locked by Verizon. Is it possible to write a new firmware over the Encrypted Verizon one and use that instead?
Thanks for even reading this, A reply would mean a lot to me!
Click to expand...
Click to collapse
Its now bootloader locked and no you can't unlock it. Your stuck with a permanent locked bootloader. You can however flash BL(bootloader locked) roms via safestrap
And no you cannot run a new firmware other than the safestrap bootloader locked ones
From my CM11 S3
So I have received a "Certified Pre-Owned" Nexus 5 from T-Mobile just a couple days ago. Within the first few hours, I rooted it. At this point I could no longer install (but still received) OTAs, and IIRC that is because the system partition has been altered. I eventually did unroot, but I still could not install OTAs. Now, there is a hardware issue with the phone: it will not vibrate properly anymore. And I have tried those solutions like pressing on the back. So will need to return this phone for a replacement or repair. I have read somewhere that T-Mobile runs a diagnostic tool to check the phone software. My phone is not rooted, and I have not unlocked it or altered the ROM in any way, but will T-Mobile know that my system partition is different? Am I still covered under warranty?
You could just flash the latest entire factory image and relock the bootloader - not sure how Tmobile would be able to tell anything different especially since the nexus 5 isn't a carrier locked device.
janjanrex said:
You could just flash the latest entire factory image and relock the bootloader - not sure how Tmobile would be able to tell anything different especially since the nexus 5 isn't a carrier locked device.
Click to expand...
Click to collapse
I don't plan to unlock my bootloader at all for a while. I unrooted with KingRoot, and now my phone is identical to stock except for a couple of files in the system partition that are traces of the root. I know this because OTA installations will result in an error. But that is the only thing that differs from a stock device. Will T-Mobile be able to access the system partition or somehow force an OTA upon it and find that it was once rooted? This is what I fear. What exactly does T-Mobile do when it receives the phone to make sure it had warranty?
Actually, what I would like to know for my peace of mind is...
Is there any way that T-Mobile can find out that I rooted?
janjanrex said:
You could just flash the latest entire factory image and relock the bootloader - not sure how Tmobile would be able to tell anything different especially since the nexus 5 isn't a carrier locked device.
Click to expand...
Click to collapse
I used the Nexus Root Toolkit to unlock, flash stock, unroot, lock, set tamper to false, etc. I can install OTAs now, and there is no way that I can think that my phone can be seen as altered. Just to confirm:
Is there any way now that T-Mobile will know that I did anything?
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.