Related
Hey guys, I'm wondering if anyone has done this, or knows if it's possible to (after unlocking bootloader) flash the Google stock Pixel system image instead of the Verizon one? I'm assuming the hardware and firmware are identical, but am not sure and am not skilled enough (or at all) in code to know if its possible. I bought my phone through Verizon, only because nowhere else had stock. I use it on T-Mobile, but fear there may be some behind the scenes Verizon stuff going on that may hinder my phone on T-Mobile. I haven't experienced any issues yet, but with the Nov security update mentioning a specific fix for wifi calling in New Mexico only on the Verizon pixels, it makes me weary that there is more happening beneath the surface than I am aware of. Thanks for any and all help! Appreciate it.
newbienic said:
Hey guys, I'm wondering if anyone has done this, or knows if it's possible to (after unlocking bootloader) flash the Google stock Pixel system image instead of the Verizon one? I'm assuming the hardware and firmware are identical, but am not sure and am not skilled enough (or at all) in code to know if its possible. I bought my phone through Verizon, only because nowhere else had stock. I use it on T-Mobile, but fear there may be some behind the scenes Verizon stuff going on that may hinder my phone on T-Mobile. I haven't experienced any issues yet, but with the Nov security update mentioning a specific fix for wifi calling in New Mexico only on the Verizon pixels, it makes me weary that there is more happening beneath the surface than I am aware of. Thanks for any and all help! Appreciate it.
Click to expand...
Click to collapse
I did yesterday, bought mine from Best Buy and I unlock the BL. Sideload the OTA yesterday and I used NDE63V that comes with new radio. oh I'm also on Tmobile
jay661972 said:
I did yesterday, bought mine from Best Buy and I unlock the BL. Sideload the OTA yesterday and I used NDE63V that comes with new radio. oh I'm also on Tmobile
Click to expand...
Click to collapse
Awesome! Thanks for the info... Really glad to know I can convert if need be. Thanks again!
jay661972 said:
I did yesterday, bought mine from Best Buy and I unlock the BL. Sideload the OTA yesterday and I used NDE63V that comes with new radio. oh I'm also on Tmobile
Click to expand...
Click to collapse
Interesting side note on this...
I went ahead and unlocked my bootloader and flashed Google's stock Pixel image. All went well, no problems... Until I tried to use Android Pay. It's telling me my software can't be verified. And I out of curiosity checked, and the "allow OEM unlocking" in developer options is still greyed out, and not selectable, even though my BL is unlocked. Hoping this doesn't mean that we can't take an OTA. Weird, I guess we'll have to wait and see when next month's security update comes out...
newbienic said:
Interesting side note on this...
I went ahead and unlocked my bootloader and flashed Google's stock Pixel image. All went well, no problems... Until I tried to use Android Pay. It's telling me my software can't be verified. And I out of curiosity checked, and the "allow OEM unlocking" in developer options is still greyed out, and not selectable, even though my BL is unlocked. Hoping this doesn't mean that we can't take an OTA. Weird, I guess we'll have to wait and see when next month's security update comes out...
Click to expand...
Click to collapse
Just having an unlocked bootloader trips SafetyNet now and you can't use Android Pay without a custom kernel.
ITGuy11 said:
Just having an unlocked bootloader trips SafetyNet now and you can't use Android Pay without a custom kernel.
Click to expand...
Click to collapse
And the OEM unlock option appears to be dependent on device ID (imeid? Ccid?), And not the software. So don't relock it, and you're fine
Sent from my Pixel using Tapatalk
danaff37 said:
And the OEM unlock option appears to be dependent on device ID (imeid? Ccid?), And not the software. So don't relock it, and you're fine
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
One thing I just realized, is in Developer Options, its greyed out like I mentioned, but also says "Bootloader is already unlocked". Which I actually remember seeing on my Nexus 5x when the bootloader was unlocked. It's got me really curious about re locking the bootloader. Mainly cause I actually use Android Pay. Had no idea bootloader unlocks are actually tripping safety net now. Major bummer. If anyone has gone through this process with a Verizon pixel and has actually relocked their bootloader with no issues I'd certainly appreciate any info you have. Otherwise, I may have to dive in blind and hope for the best.
If you want to use Android pay, flash a custom kernel but don't root. Works for me.
Don't relock if you ever want to have it rooted, custom, etc. The unlock method isn't going to survive another security update.
Sent from my Pixel using Tapatalk
danaff37 said:
If you want to use Android pay, flash a custom kernel but don't root. Works for me.
Don't relock if you ever want to have it rooted, custom, etc. The unlock method isn't going to survive another security update.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Hypathetically, if I didn't want root or anything custom at all, do you think that relocking the bootloader could cause an issue while using the Stock Google image on a Verizon Pixel? I wish I had more knowledge on this, but I'm pretty in the dark on this stuff as of late... Thanks for your help!
Should be fine if all stock I think, just know that you may not be able to unlock later.
Sent from my Pixel using Tapatalk
newbienic said:
One thing I just realized, is in Developer Options, its greyed out like I mentioned, but also says "Bootloader is already unlocked". Which I actually remember seeing on my Nexus 5x when the bootloader was unlocked. It's got me really curious about re locking the bootloader. Mainly cause I actually use Android Pay. Had no idea bootloader unlocks are actually tripping safety net now. Major bummer. If anyone has gone through this process with a Verizon pixel and has actually relocked their bootloader with no issues I'd certainly appreciate any info you have. Otherwise, I may have to dive in blind and hope for the best.
Click to expand...
Click to collapse
Contrary to what people are saying. You CAN relock your bootloader and then unlock it again later. However, keep in mind that at some point there will likely be an update that blocks the use of dePixel8 and you will no longer be able to unlock the bootloader unless someone writes another exploit.
I would like to find a way to permanently unlock VZW Pixels but until I get one from the Google Store to compare with my Verizon one I don't think I will make much progress.
Relocking your bootloader is as simple as running the "fastboot oem lock" command from the terminal window.
Lastly. If you want to relock the bootloader, make sure your phone is 100% stock image or you risk bricking the phone
If I were to buy the Verizon pixel and flash the unlocked (non European) image. How do you think updates would work? Would I get seamless updates from Google or would I need to flash every Ota manually. Might be too early to tell
b316kane said:
If I were to buy the Verizon pixel and flash the unlocked (non European) image. How do you think updates would work? Would I get seamless updates from Google or would I need to flash every Ota manually. Might be too early to tell
Click to expand...
Click to collapse
This is exactly what I did, and I am curious as well... We'll see next month I guess, but I'm guessing it will take the OTA just fine. My wife has a Pixel from the Google store, and mine is from Verizon. I've compared everything (including booloaders) since flashing the Google store Pixel image, and every informational detail is identical. Not sure if there is some other place hidden to me that might indicate a difference, but I'm thinking that Verizon's Pixel is only different in its official software image... And, that may be it. Please don't take my word for it, I'm no developer, and know very little about any of this, but in my comparisons, they are identical now since flashing Googles official (Non Verizon, Non European) image.
Sidenote, I have yet to try this, but I'm thinking that since I am on Googles image, that if I re-lock my bootloader, that I WILL be able to unlock again after locking. I think Verizon used Googles "Allow OEM Unlocking" software toggle in developer options as the only method to actually keep people from unlocking the bootloader (again speculative), and now that I'm on Googles image, that software "block" should no longer be present, so I should in theory, be free to lock/unlock the same as Pixels purchased from the Google store... Again, I've got no proof, or actual skill to back this up, but it's a theory I have, and if I end up locking my BL again, I'll post what I find...
newbienic said:
I have yet to try this, but I'm thinking that since I am on Googles image, that if I re-lock my bootloader, that I WILL be able to unlock again after locking.
Click to expand...
Click to collapse
In the Verizon unlocking threads the people that tried relocking reported that they were unable to unlock again without depixel8, which is the same as how the Verizon phone typically works. Some people seem to have gotten into situations that could have been corrected with an unlocked bootloader, but because they had a locked bootloader that couldn't be unlocked using depixel8 they had no easy solution to get their phone working again at this time.
http://forum.xda-developers.com/pixel-xl/how-to/psa-read-relocking-bootloader-t3494615
alluringreality said:
In the Verizon unlocking threads the people that tried relocking reported that they were unable to unlock again without depixel8, which is the same as how the Verizon phone typically works. Some people seem to have gotten into situations that could have been corrected with an unlocked bootloader, but because they had a locked bootloader that couldn't be unlocked using depixel8 they had no easy solution to get their phone working again at this time.
http://forum.xda-developers.com/pixel-xl/how-to/psa-read-relocking-bootloader-t3494615
Click to expand...
Click to collapse
Thanks for the heads up!!! Like I said, I really know nothing, just speculating. Appreciate you looking out.
newbienic said:
Thanks for the heads up!!! Like I said, I really know nothing, just speculating. Appreciate you looking out.
Click to expand...
Click to collapse
I forget where, but I saw written or implied that the "checking for updates" screen about third of way through initial setup of first boot uses WiFi AND sim carrier data to install Verizon custom restrictions and settings that among other effects make depixel8 required.
Even on "non Verizon phones" (which you are saying use the same build images byte to byte?)... You have to either use a SIM card or wifi and google account to allow the developer options to enable OEM unlock.
My theory: In other words, if you don't allow via SIM and a network wifi or data connect, for Verizon to mark your phone, or another carrier, then the phone can not be unlocked. So carrier models may indeed be differentiated from current factory images AFTER boot and setup.
There is a post in Q&A of someone trying to unlock bootloader without loading into the device, not having luck. This is why oem unlock toggle is so important and why people are bricking from locked bootloaders that won't unlock (so no wipe and factory images cannot be flashed.)
Another thing to consider: SIM network lock will not be flashed over.
Sent from my sailfish using XDA Labs
Hi guys,
first of all, thank you all for your amazing work! Its great to have such nice guys working on android.
I saw a thead in the "rom" section but since im new in the forum i cant ask in the thread there :/
Do i need to unlock the bootloader in order to flash twrp for full root?
What about the OTA updates? I guess i cant updates after i unlocked the bootloader?
I read about the funkyhuwei method but it seems to be quite costly. One time or maybe even per month ok but 1 credit for 10$?? Wow..
Thanks guys!
Yes. You need unlock bootloader to do other things like flashing twrp.
And you can receive ota updates.
unlocked bootloader and warning messages
5[Strogino] said:
Yes. You need unlock bootloader to do other things like flashing twrp.
And you can receive ota updates.
Click to expand...
Click to collapse
Hi, I unlocked my bootloader, but every time I boot I see these messages that my phone has been unlocked and can't be trusted. I understand this is normal, but is there any way to NOT see this warning?
Also, does this affect any encryption, AndroidPay, fingerprint phone lock, security setting,.... basically, what does that mean "phone cannot be trusted"?
mat_919 said:
Hi, I unlocked my bootloader, but every time I boot I see these messages that my phone has been unlocked and can't be trusted. I understand this is normal, but is there any way to NOT see this warning?
Also, does this affect any encryption, AndroidPay, fingerprint phone lock, security setting,.... basically, what does that mean "phone cannot be trusted"?
Click to expand...
Click to collapse
It can't be removed without locking bootloader again.
Not until someone figures out how to flash TWRP without unlocking bootloader, OR flash official firmware but keep recovery untouched.
And it doesn't affect them (afaik anyway, it works great with Magisk and I don't think it hides unlocked bootloader).
Some sites say that it is possible, but they don't look trustworthy. I have the U11+ not the U11.
The U11+ does not show up on this page: htcdev.com/bootloader/
Only the U11 does.
So can I use the U11 option or does there have to be another way?
Yes you can. Just select 'other device' or whatever when you get to the drop-down box where it asks which phone you want to unlock.
I unlocked mine about a month ago.
Just remember it's gonna wipe your phone's data when you do it, so make sure everything is backed up.
When I try to unlock bootloader then I get this warning from HTC:
Legal Terms
In order to continue, please read and accept the following legal terms:
I acknowledge that use of the unlock bootloader may void all or parts of my warranty device and my device may not function as intended by HTC.
I acknowledge that, if my device requires repairs, HTC may charge for additional costs due to the unlocked bootloader.
Click to expand...
Click to collapse
Why my device may not function as intended by HTC after bootloader unlock?
Which HTC functions exactly are lost after bootloader unlock?
how can I prevent this loss of HTC functionality when doing bootloader unlock?
how to gain temp root and backup the entire internal storage partition before proceeding with unlocking the bootloader?
any hints anyone?
You will lose updates over the air feature, but you can still update manually after root with signed update + rom or return to stock. Anyway all apps and settings from htc will stay after unlocking bootloader but be aware it will wipe your own files in the internal memory, backup to sd or pc 1st
Thank you for the answer.
yes I am aware that the bootloader unlock procedure will inevitably format the entire internal storage.
i was just wondering which HTC features I would lose when performing the bootloader unlock.
If it's only the FOTA I guess I can live with that.
Hopefully I won't lose any special and unique device specific keys that are hidden deep inside the internal storage partition.
Some phone manufacturers such as Sony will do that to you.
So you got the Edge S and want GApps? Basically you unlock your bootloader, root with Magisk, then install MagiskGApps.
DISCLAIMER: UNLOCKING YOUR BOOTLOADER MAY VOID YOUR WARRANTY, AND DOING ALL THESE THINGS IN THIS GUIDE MAY RESULT IN DAMAGE/BRICKING YOUR PHONE. I AM NOT RESPONSIBLE FOR ANYTHING YOU DO TO YOUR PHONE. PROCEED AT YOUR OWN RISK.
1. Unlock the bootloader: that should be doable with their global bootloader unlock website here.
2. Download Lenovo Motoroa Smart Assistant (Rescue and Smart Assistant), and follow its instructions to "rescue" your device. It will lead you to boot into bootloader mode and download the firmware. Find the firmware file via the LMSA's downloads (should have a "show folder" button). You'll need the boot.img file for Magisk.
3. Download Magisk, then follow its instructions. You'll have to copy the boot.img to your device, then use Magisk to patch the boot file, then copy the modified one to your PC.
4. You'll need fastboot. If you don't have it already, you can download the Android SDK platform tools here. Then go into the folder, Shift+Right Click the folder, then "Open Command Prompt" or "Open PowerShell," you should have something close to one of those two. Copy your Magisk modified .img file to that folder, then you'll want to input:
fastboot flash boot [modified .img file]
Once that completes, you should see in large text, "Start" on your phone next to the power button. Press the power button, and it should boot, and you should have root now.
5. Download MagiskGApps to your phone, open Magisk on your phone, click the button that looks like a puzzle piece at the bottom of the screen, "Modules." Click "Install from storage," locate the MagiskGApps file, and install it. After that it will ask you to restart your phone, do that, then you'll just have to be patient as it takes time once its restarted to load everything. You also may need to update some or all of the apps, then you should be able to use the notification to finish setting up the phone with Google Setup.
Thanks to Motorola for making it easy to unlock their bootloaders
Thanks to the whole Magisk team for making an easy, awesome root (and more!)
Thanks to Wacko1805 (and team?) for making MagiskGApps. This is really awesome.
unlock the BL and get root is will make some apps fingerprint and face ID fail?
kimker said:
unlock the BL and get root is will make some apps fingerprint and face ID fail?
Click to expand...
Click to collapse
Magisk has a "Magisk Hide" which will allow it to pass SafetyNet, and most things which check on device security will think the device is secure. But unlocking BL and rooting does make the device less secure, and therefore incurs its own risks apart from bricking or damaging the device.
HopelesRomantc91 said:
Magisk has a "Magisk Hide" which will allow it to pass SafetyNet, and most things which check on device security will think the device is secure. But unlocking BL and rooting does make the device less secure, and therefore incurs its own risks apart from bricking or damaging the device.
Click to expand...
Click to collapse
yes, i knew the unlock and root will take risk.. but not sure is Payment business apps using fingerprint will work normal.
kimker said:
yes, i knew the unlock and root will take risk.. but not sure is Payment business apps using fingerprint will work normal.
Click to expand...
Click to collapse
Google Pay works. But according to the Motorola website you should be able to relock the bootloader if yours doesn't work. But there's never any guarantee. If you need your device secure, recommend don't unlock bl or root, or wait to see if there's a root option without bootloader unlock that can be easily undone.
HopelesRomantc91 said:
Google Pay works. But according to the Motorola website you should be able to relock the bootloader if yours doesn't work. But there's never any guarantee. If you need your device secure, recommend don't unlock bl or root, or wait to see if there's a root option without bootloader unlock that can be easily undone.
Click to expand...
Click to collapse
I saw that someone’s edge s had unlocked the BL and Flash G100 firmware and everything worked normally, and then tried to lock the BL again, but it was unsuccessful and the system could not start. The flashing tool does not recognize the machine.
kimker said:
I saw that someone’s edge s had unlocked the BL and Flash G100 firmware and everything worked normally, and then tried to lock the BL again, but it was unsuccessful and the system could not start. The flashing tool does not recognize the machine.
Click to expand...
Click to collapse
That's not good. Hopefully they can restore it back somehow. With this guide to unlock and flash gapps why would you need to flash G100 though? This seems to be itright now without one of rom developer's releases to get root & apps. For me this is all i would look for. Titanium backup on it and restore.. done until PE rom comes out.
kimker said:
I saw that someone’s edge s had unlocked the BL and Flash G100 firmware and everything worked normally, and then tried to lock the BL again, but it was unsuccessful and the system could not start. The flashing tool does not recognize the machine.
Click to expand...
Click to collapse
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
HopelesRomantc91 said:
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
Click to expand...
Click to collapse
thank you. They did not ask for help. It seems that the lock BL is a self-verification switch, and then performs a verification system integrity.
HopelesRomantc91 said:
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
Click to expand...
Click to collapse
I'm curious,If you unlock and flash other firmware and then flash back to the original firmware, can it be locked again?
Mine doesn't let me unlock its BL. I've got unlock code from moto and did a factory reset with SIM card in slot 1. After enabling developer mode and debugging the switch still is greyed out. So no chance to unlock it.
Has anyone got an idea what to try now?
Moto support answered yesterday to my request but also no solution since I told them that it doesn't work
Device is not branded. I got it from Amazon so no provider branding.
If this won't be able to be unlocked and rooted I'll have to return it and switch to a Google Pixel.
kischde said:
Mine doesn't let me unlock its BL. I've got unlock code from moto and did a factory reset with SIM card in slot 1. After enabling developer mode and debugging the switch still is greyed out. So no chance to unlock it.
Has anyone got an idea what to try now?
Moto support answered yesterday to my request but also no solution since I told them that it doesn't work
Device is not branded. I got it from Amazon so no provider branding.
If this won't be able to be unlocked and rooted I'll have to return it and switch to a Google Pixel.
Click to expand...
Click to collapse
I had the same issue, you need to factory reset WITH your sim card in the phone, this will let you open the OEM unlock slide thing in the dev mode.
Then once its done you can fastboot and unlock the bootloader.
I did so, maybe I explained not so well. SIM was inserted and then I did factory reset by starting it from settings. After restart it's still the same - switch / unlock slider greyed out.
kischde said:
I did so, maybe I explained not so well. SIM was inserted and then I did factory reset by starting it from settings. After restart it's still the same - switch / unlock slider greyed out.
Click to expand...
Click to collapse
On my OG Pixel XL, I had to wait 7 days for the slider to become normal. By the time I got around to do it on the Edge S it was about the same time.... could be related
Now as you said that I remember that thingy with another device. Maybe a Xiaomi I think... With that I had to wait several days until the unlock code was delivered.
But there was a message, too, when trying to get it sooner, which said you needed to wait some more time.
Not sure if it's the the same for Moto devices? Then again, when thinking that you experienced the same with a Pixel, too...
Did anyone else make such an experience with his/her g100?
kischde said:
Now as you said that I remember that thingy with another device. Maybe a Xiaomi I think... With that I had to wait several days until the unlock code was delivered.
But there was a message, too, when trying to get it sooner, which said you needed to wait some more time.
Not sure if it's the the same for Moto devices? Then again, when thinking that you experienced the same with a Pixel, too...
Did anyone else make such an experience with his/her g100?
Click to expand...
Click to collapse
Make sure your on the latest OTA, Lenovo made a mistake on previous versions with the OEM Unlocking function not being enabled. They fixed it in latest ota.
RSA tool said the file I uploaded yesterday is the latest one available (and it's exactly the same as the installed version).
The device was released just a few days ago in Europe. Perhaps they fixed the unlock switch in other regions and still need to fix it in Europe..
Will wait until weekend if they come up with a solution. If not I'm afraid I have to return the device as I need it personally AND professionally, too - I'm field agent, so.... :/
HopelesRomantc91 said:
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
Click to expand...
Click to collapse
The poor guy whose phone turned bricks went to the after-sales department of moto, and the answer was that he needed to replace the phone motherboard. .
kimker said:
The poor guy whose phone turned bricks went to the after-sales department of moto, and the answer was that he needed to replace the phone motherboard. .
Click to expand...
Click to collapse
Ouch...
kimker said:
I'm curious,If you unlock and flash other firmware and then flash back to the original firmware, can it be locked again?
Click to expand...
Click to collapse
I would assume so, but I don't really know why anyone would want to relock.
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.