Related
I just wanted to let you guys know a couple things from what I've been playing around with.
1. The Amazon G6 I bought had an unlockable bootloader. Just went through the normal request procedure and it was given to me.
2. You can install normal G6 firmware on it. Software channel will still say AMZ but you won't have the bloat apps or an Amazon option in your settings.
3. No Magisk support (which appears to be the same as unlocked version).
4. Project Treble works but I haven't figured it out yet. Spent some time to get the correct drivers installed to be able to flash on it. Couldn't get a 64-bit GSI to work (I don't think our phone supports it?) but got a 32-bit one to work. Going to double check on 64-bit because I had to restart the 32-bit one a couple times to get it to work.
When I started the Treble rom it said I had a password to enter, which I didn't, so I had to factory reset again. Also couldn't get Google Play Services to work. I registered my number with Google but it didn't change anything. Also kept getting toast notifications about apps not working right because update channel was null or something like that. Not sure if that is because of Google Play or something else.
Anyway, I haven't seen much discussion about any of this so figured I'd just post what I know.
gpgorbosjr said:
I just wanted to let you guys know a couple things from what I've been playing around with.
1. The Amazon G6 I bought had an unlockable bootloader. Just went through the normal request procedure and it was given to me.
2. You can install normal G6 firmware on it. Software channel will still say AMZ but you won't have the bloat apps or an Amazon option in your settings.
3. No Magisk support (which appears to be the same as unlocked version).
4. Project Treble works but I haven't figured it out yet. Spent some time to get the correct drivers installed to be able to flash on it. Couldn't get a 64-bit GSI to work (I don't think our phone supports it?) but got a 32-bit one to work. Going to double check on 64-bit because I had to restart the 32-bit one a couple times to get it to work.
When I started the Treble rom it said I had a password to enter, which I didn't, so I had to factory reset again. Also couldn't get Google Play Services to work. I registered my number with Google but it didn't change anything. Also kept getting toast notifications about apps not working right because update channel was null or something like that. Not sure if that is because of Google Play or something else.
Anyway, I haven't seen much discussion about any of this so figured I'd just post what I know.
Click to expand...
Click to collapse
FYI G6's SOC is arm (32bits) so you better stop flashing 64bit builds before you brick your device
CreasingMass Dev said:
FYI G6's SOC is arm (32bits) so you better stop flashing 64bit builds before you brick your device
Click to expand...
Click to collapse
Well actually the SOC is 64 bit. But I guess Motorola used 32 bit software because ......Motorola.
Thanks for the warning but I'm not worried. It just won't load the os if it's an issue and you can flash the stock one back easily enough.
I'm assuming we will be able to get 64 bit roms on this phone when twrp and all that come. The SOC itself is 64-bit.
Consult Here
But I think I just may use this as a backup play around with phone anyway since we couldn't get the G6+ in US.
gpgorbosjr said:
Well actually the SOC is 64 bit. But I guess Motorola used 32 bit software because ......Motorola.
Thanks for the warning but I'm not worried. It just won't load the os if it's an issue and you can flash the stock one back easily enough.
Click to expand...
Click to collapse
Yea i just read the actual SOC "supports" 64bit, anyway stuff on the G6 is 32bit so yea
CreasingMass Dev said:
FYI G6's SOC is arm (32bits) so you better stop flashing 64bit builds before you brick your device
Click to expand...
Click to collapse
CreasingMass Dev said:
Yea i just read the actual SOC "supports" 64bit, anyway stuff on the G6 is 32bit so yea
Click to expand...
Click to collapse
Yep. I was editing my post as you replied but like I said I'm sure this phone will get 64-bit ROMS at the end of the day when stuff is sorted out.
And I definitely would've been more careful flashing but I knew the stock firmware restore worked and I've done a lot of crazy stuff to phones in my days and never messed one up so bad I couldn't get to bootloader.
I am getting my g6 from Amazon tommorow....I m out of the phone flashing hobby for a while...not completely sure if I understand the o.p. here ,
Can I install stock g6 on this device removing Amazon stuff? I guess yes ...can. Someone post the link ? ..does this void warranty?
How do I root or install magiks ?
Super helpful post -- thanks!
Just got an "exclusive" G6 from amazon.
Alas bootloader is not unlockable. What's worse, I only realized that after I've attempted to flash stock G6 image.
Now I can only boot in fastboot mode.
Does anybody know if there are stock images for amazon G6?
Or if there's any other way to unbrick amazon phone using stock G6 image.
zzyxy said:
Just got an "exclusive" G6 from amazon.
Alas bootloader is not unlockable. What's worse, I only realized that after I've attempted to flash stock G6 image.
Now I can only boot in fastboot mode.
Does anybody know if there are stock images for amazon G6?
Or if there's any other way to unbrick amazon phone using stock G6 image.
Click to expand...
Click to collapse
you didn't go to Motorola's site did you? easily unlock your bootloader there.
supergear said:
you didn't go to Motorola's site did you? easily unlock your bootloader there.
Click to expand...
Click to collapse
I did, and it the page gave me a popup that said that my phone is not eligible and the button to request the code never showed up. I did get unlock code for another G6 (i.e. no amazon prime special), so I'm pretty sure I didn't mess up the process.
Can also confirm I'm not able to unlock the bootloader. So either something's wrong with the system on Motorola's end or you got extremely lucky getting an unlock code. Double checked everything and used the data scrub tool. No luck.
I have an Amazon G6. I was able to enter developer mode and toggle "Unlocked Bootloader", so I assume my is unlocked. Regarding OP's message:
> 1. The Amazon G6 I bought had an unlockable bootloader. Just went through the normal request procedure and it was given to me.
> 2. You can install normal G6 firmware on it. Software channel will still say AMZ but you won't have the bloat apps or an Amazon option in your settings.
What do you mean "went through the normal request procedure and it was given to me."? And where do I get a "normal G6 firmware" for it? I am already sick of the Amazon apps and I want a clean phone. Can OP possibly write up a more detailed guide?
You have to go to the Motorola bootloader unlock page and request a code. The toggle just allows you to unlock the bootloader if an unlock key is granted through fastboot. So far I've only seen one person that successfully received an unlock key. Everyone else gets the device not eligible message.
Also unable to unlock
I received the 64GB version, today, and get the message from the Motorola website that my device is ineligible to be unlocked. Darn the luck, I bought it hoping for the best. Should I try again, later?
CreasingMass Dev said:
Yea i just read the actual SOC "supports" 64bit, anyway stuff on the G6 is 32bit so yea
Click to expand...
Click to collapse
The G6's SOC is 64 bit like the guy said, no supporting, it IS 64 bit, if you were to look in any CPU app it will show 64 bit architecture running in 32 bit mode, so there ya go
So do people recommend paying the extra money to buy a non-exclusive version?
Same here. Very disappointed with Amazon!
Meep70 said:
I received the 64GB version, today, and get the message from the Motorola website that my device is ineligible to be unlocked. Darn the luck, I bought it hoping for the best. Should I try again, later?
Click to expand...
Click to collapse
Chatted with Motorola, they can't help. They said just keep reading forums.....
That's what I figured. I'm quietly watching, and I occasionally try to see if something changes on Motorola's side.
Just got a Nokia 3.1 to use a testing tool and other fun stuff, and therefore would like to root it. Does anyone of you know of a working root of the 3.1?
So this phone is a no go for root and custom roms I guess.
kaslopis said:
So this phone is a no go for root and custom roms I guess.
Click to expand...
Click to collapse
Why do you think so? Bootloader can be unlocked via Developer settings, and I think there is no special magic preventing this device from rooting.
I would try rooting it by flashing some SuperSU zips or something like that, but I didn't try it yet
Has anyone checked this out? I haven't purchased a Nokia 3.1 but am considering it. I went so far as to create a Nokia account and there is a bootloader unlock apk, as well as an unlock.key that can be downloaded, and there are clear instructions on the Nokia page itself.. Since I don't have the phone, I did not attempt to proceed. However, if the 3.1 qualifies (I don't see why it wouldn't) then getting root should be as easy as following Magisk instructions.
There is even a page for the open source releases.
If I were to get the 3.1, my main objective would likely be to just obtain root. Looks like it should be doable.
Edit - well over 100 views since I posted this but no one has tried to unlock and/or root. I thought that was the purpose of this thread.
Unfortunately that app always crashes
VidarPT said:
Unfortunately that app always crashes
Click to expand...
Click to collapse
That is unfortunate! Perhaps, does activating Developer Options allow to select OEM Unlocking and USB Debuging, then running the Unlocking App? To run step 5 of 5 (see NOKIA INSTRUCTIONS below) you would need to have USB Debugging enabled anyway. Nowhere in the instructions is that mentioned.
FYI - Activate Developer Options: Go to Settings>About Phone and tap Build Number 7 times. Back out to access Developer Options.
Also, I do not have this phone but am interested in it. I cannot confirm if any of the advice I am giving will work, but it is what I would try.
NOKIA INSTRUCTIONS
Introduction
Firstly, we need to validate that the phone you would like to unlock is operated by you. There are a few steps to this, so we ask that you carefully follow all instructions. Let’s get started.
To participate, simply complete the following steps:
1. Please download the Nokia Bootloader Unlocker app. You can download the apk from this link and install the apk on your device. If you don’t understand how to install an apk on your device, please do not unlock the bootloader on your device. Doing so will void your phone's warranty and may cause irreparable damage.
2. Launch the Nokia Bootloader Unlocker app and fill your email information and click “Submit”.
3. The app will display a code. Please enter this in the form below along with your email address. Then press "Request to Unlock"
Your bootloader can now be unlocked. Follow the instructions below:
Step 1/5
Check the email you entered during registration. You should receive an email with a message as follows:
Hi, Thanks for requesting the unlocking bootloader. Please download your unlock key from the following link. xxxxxxxxxxxxxxxxxxxxxxxxxx
Download the unlock key and save it as “unlock.key”.
Step 2/5
Power off your device. Once powered off, press and hold the Volume Down button.
Step 3/5
While keeping the Volume Down button pressed, connect the device to the computer via USB cable. The device will boot into “Download mode”. If you have difficulty, try powering up normally, power off the device again and start back from Step 1.
Step 4/5
Download the following fastboot binary for your OS here.
Step 5/5
Open a command prompt:
Windows: Start > cmd
Mac: Applications > Utilities > Terminal.app
Linux: Terminal
Navigate to the directory where the previously downloaded unlock.key file is saved. Then enter the following commands:
fastboot flash unlock unlock.key
fastboot oem unlock
If successful, you should see the below message:
Unlock success!
Then reboot the device by entering the following command:
fastboot reboot
You are done!
It doesn't work either way. I tried with both those options enabled and disabled but the program always crashes. It's interesting to note that the app itself fails to install through chrome or "Files" app. Gives an error saying "Can't open app". I only managed to install it through ES File Explorer. Could it be because of I bought the phone on a Vodafone store? I can't find the original stock rom to flash, sadly.
VidarPT said:
It doesn't work either way. I tried with both those options enabled and disabled but the program always crashes. It's interesting to note that the app itself fails to install through chrome or "Files" app. Gives an error saying "Can't open app". I only managed to install it through ES File Explorer. Could it be because of I bought the phone on a Vodafone store? I can't find the original stock rom to flash, sadly.
Click to expand...
Click to collapse
I have been researching this and have found that, as of this writing, only the Nokia 8 qualifies for bootloader unlocking. See here. The only thing holding me back from jumping on this Nokia 3.1 is the inability to unlock the bootloader (and maybe the lack of fingerprint sensor.) Hopefully it gets "approved soon".
Currently the oem unlock using the Nokia bootloader unlock only works for Nokia 8
is there a way to root the 3.1 yet successfully? im a noob at this stuff and don't want to screw my phone.
snarfydog said:
is there a way to root the 3.1 yet successfully? im a noob at this stuff and don't want to screw my phone.
Click to expand...
Click to collapse
No, not until Nokia decides to allow users to unlock bootloader.
What about the 3.1 plus. I've already unlocked OEM. I just started looking, thought I'd start here first.
XSHADOW3 said:
What about the 3.1 plus. I've already unlocked OEM. I just started looking, thought I'd start here first.
Click to expand...
Click to collapse
It doesn't matter if you have enabled "OEM unlocking" option in Developer settings, currently Nokia doesn't allow unlocking of bootloader and thus rooting device, unless you are Nokia 8 user. You can try this, but it will crash almost for sure.
As far as I can tell, my bootloader is unlocked. I am a noob of course, but I have been researching this topic for a couple of months now. I could be mistaken in thinking "upload" mode is it, but I can't seem to figure out the difference. Otherwise, I don't know what to do next.
Nightseer said:
As far as I can tell, my bootloader is unlocked. I am a noob of course, but I have been researching this topic for a couple of months now. I could be mistaken in thinking "upload" mode is it, but I can't seem to figure out the difference. Otherwise, I don't know what to do next.
Click to expand...
Click to collapse
Can you please tell what did you do exactly?
MilesSeventh said:
Can you please tell what did you do exactly?
Click to expand...
Click to collapse
To get to "Upload" mode? Assuming it's the same for the 3.1 Plus-maybe I should have specified that-holding power button and volume up during startup will open "Upload" mode.
You can also use adb with the command "reboot bootloader." For that reason, I think it's the bootloader, but I could be wrong.
Sorry if I was a bit misleading and it is totally different on the Nokia 3.1, I was just some kinda hopeful to actually see people talk about it.
Let's get her done
Nightseer said:
To get to "Upload" mode? Assuming it's the same for the 3.1 Plus-maybe I should have specified that-holding power button and volume up during startup will open "Upload" mode.
You can also use adb with the command "reboot bootloader." For that reason, I think it's the bootloader, but I could be wrong.
Sorry if I was a bit misleading and it is totally different on the Nokia 3.1, I was just some kinda hopeful to actually see people talk about it.
Click to expand...
Click to collapse
I'm not bringing any sizable programming skills to the table unless somebody wants to teach me real fast.
Hopefully, I bring tidings of great joy. So I got two these Nokia's and they're both locked. to the carrier, Cricket. I suspect they are at least unlawfully locked. . My understanding is you can't lock to used phone especially if it's been sold as a prepaid phone. I believe this falls under the reseller flex policy. I bought it off of eBay from a guy that sells nothing but phones and he's been extremely cagey about what he'll admit to, so I called the carrier. I literally waited an hour and a half on the phone because I am falling asleep and I was on a computer speaker phone so it kept on the time of the call. I only held that long because I had fallen asleep. Anyway since I'm not in a cricket or AT&T customer then don't plan to eitherbe they could care less about me it actually told me they didn't have any information on the phone after I gave them the IMEI number.
My guess is the fcc's not going to do much because it's a trump Administration. So I spent about 45 minutes on the phone with Nokia and well at least they're interesting I think Microsoft paid between 7 and 12 billion to acquire them I recently sold them off for like a box of jujyfruits. Anyway they're committed to customer service so I figure my predicament might give me an in there.
So those unlock codes that it was a link earlier in the post for that's just to unlock the bootloader, right? You know this is a pretty decent phone for a low-end guy I got the newer 3.1 C it's got Cricket's bootloader in bloatware on it,
takes up a ton of space.
I mean it probably won't happen but if Nokia ever goes public again - I think the acquiring companies. Their eye on the prize and they're going to kick some ass. So I'm all in on this let's get this done. If you want I can see what I can do about asking Nokia 4 whatever it's going to take just to keep me a satisfied customer since they know Cricket/ATT isn't following the Obama regs.
Oof... It would be beautiful if Nokia customer support could guide us onto rooting this phone.
its so simple to unlock oem on nokia 3.1 plus. no third app needed. after developer option on -> go to developer option setting -> there is toggle button to on/off developer option , just use that toggle to off it and on it -> press yes for on dev options -> and select oem unlock. that all
It is pretty straightforward once you have unlocked bootloader (not by Nokia). If you want, you can simply dump boot_a or boot_b with SPflash tool, patch in Magisk app, and reflash.
Otherwise you can use my TWRP (NO TOUCH, and has disabled dm-verity). Please note it's only working on build v3.180, updates not supported - as it was only needed for my project.
https://forum.xda-developers.com/no...m-kali-nethunter-nokia-3-1-android-9-t4157681
[S8+] Purchased a stock AT&T S8+ in a lot. It has latest bootloader and bad IMEI....
First off, I'm an engineering scientist with years of development experience developing both hardware and software for all sorts of phones and companies. So I feel I'm pretty familiar with Android and every conceivable (and off-the-wall) way to get this phone unlocked, rooted, and/or just flat out usable. And I have failed which is why I am finally giving this to the multiverse in hopes there is someone with some solution I have yet to attempt.
I have been searching and trying every possible option for a week and counting. I'm also aware of how close to impossible it is to work with locked Snapdragon CPUs. But not entirely impossible. There has to be a way of reviving this phone!
So I recently purchased a lot full of untested and "for parts" electronics. In there was an AT&T S8+ with a cracked screen. It was also stuck in a boot loop, so I can safely hazard a guess that someone tried to update the ROM, bricked it, and didn't realize they could reflash stock firmware and fix it. Well, upon further examination, I discovered they had attempted flashing a V7 bootloader. Yes, version 7. So that basically robbed me of any options I may have had, as well as all the bugs I could have used to root the device. All I could do was install Pie with a V7 bootloader. Voila! The phone boots up. But it gets better....
Now that the phone was working, I did some examining, one part of which was the IMEI as I wanted to unlock it if possible. I check the IMEI, and it is frakking blacklisted! So that blew ever being able to use this phone on a network. I even sat on hold for 46 minutes to speak with someone at AT&T to see if they could remove it off the blacklist. They promptly said "sure!", then transferred me to someone else to fix it and the guy said "no".. So it's stuck locked to AT&T, which sucks because I checked with several other networks who all said the phone could be used on their networks. But that's not an option if it is carrier locked and impossible to unlock. :silly:
Furthermore, OEM Unlock is 110% unavailable, and no bugs work or exist to force it to appear on Android 9 Pie like you can with 8 Oreo and 7 Nougat; and I tried for days. So the bootloader is permanently locked. If it wasn't, I could root the phone, fix the IMEI, unlock it, and get the phone functional again. Alas, I cannot, at least any time soon, if ever.
I've tried every possible thing out there to root this, unlock the bootloader, and/or try to roll back Pie to Oreo, Nougat, or some stock ROM with bugs that are still active. At the very least just to change the IMEI and get the phone working again. But there is no version of Oreo/Nougat that can be installed with a V7 bootloader.
Also, there is absolutely no Engineering Mode (NOT Developer Mode) available under this stock Android 9 Pie, either by code or by app/settings. Does anybody know of an exact Android 9 Pie stock ROM with an accessible no-root Engineering Mode?
And I've tried every way out there to force OEM Unlock to appear, but the bugs that work in Oreo and Nougat have all been patched and none of them work on Android 9 Pie. So I'm stuck with this ROM and bootloader
So I'm here today with these issues in hopes someone may have solutions for:
A way to force OEM Unlock to appear under Android 9 Pie (as no Oreo/Nougat hacks work under Pie)
A way to bypass KG state under stock Android 9 Pie (as no Oreo/Nougat hacks work under Pie)
A way to install Android 8 Oreo or Android 7 Nougat with a V7 bootloader
A stock ROM with Engineering Mode available
A way to change the IMEI without root
A way to modify the V7 stock ROM so it installs a Nougat/Oreo ROM instead of Pie
Another option to keep this phone from just being a fancy, pretty paperweight
Any solution we or I may discover, I will clean it up and make a guide to help others with these same issues as there is not much info yet V7 on bootloaders. So this is a group activity that could help many, many people; help me help us all!
Thank you all in advance for anything you can offer to help!
-DL
EDIT 1: I forgot to mention that the KG State is stuck on "Checking...." so I couldn't get "OEM Unlock" even by waiting
I used this video to figure out how to get the OEM Unlock option.
(input this after youtube url) watch?v=zhNhyT4F3e8&t=133s
Hopefully this helps.
domiluci said:
First off, I'm an engineering scientist with years of development experience developing both hardware and software for all sorts of phones and companies. So I feel I'm pretty familiar with Android and every conceivable (and off-the-wall) way to get this phone unlocked, rooted, and/or just flat out usable. And I have failed which is why I am finally giving this to the multiverse in hopes there is someone with some solution I have yet to attempt.
I have been searching and trying every possible option for a week and counting. I'm also aware of how close to impossible it is to work with locked Snapdragon CPUs. But not entirely impossible. There has to be a way of reviving this phone!
So I recently purchased a lot full of untested and "for parts" electronics. In there was an AT&T S8+ with a cracked screen. It was also stuck in a boot loop, so I can safely hazard a guess that someone tried to update the ROM, bricked it, and didn't realize they could reflash stock firmware and fix it. Well, upon further examination, I discovered they had attempted flashing a V7 bootloader. Yes, version 7. So that basically robbed me of any options I may have had, as well as all the bugs I could have used to root the device. All I could do was install Pie with a V7 bootloader. Voila! The phone boots up. But it gets better....
Now that the phone was working, I did some examining, one part of which was the IMEI as I wanted to unlock it if possible. I check the IMEI, and it is frakking blacklisted! So that blew ever being able to use this phone on a network. I even sat on hold for 46 minutes to speak with someone at AT&T to see if they could remove it off the blacklist. They promptly said "sure!", then transferred me to someone else to fix it and the guy said "no".. So it's stuck locked to AT&T, which sucks because I checked with several other networks who all said the phone could be used on their networks. But that's not an option if it is carrier locked and impossible to unlock. :silly:
Furthermore, OEM Unlock is 110% unavailable, and no bugs work or exist to force it to appear on Android 9 Pie like you can with 8 Oreo and 7 Nougat; and I tried for days. So the bootloader is permanently locked. If it wasn't, I could root the phone, fix the IMEI, unlock it, and get the phone functional again. Alas, I cannot, at least any time soon, if ever.
I've tried every possible thing out there to root this, unlock the bootloader, and/or try to roll back Pie to Oreo, Nougat, or some stock ROM with bugs that are still active. At the very least just to change the IMEI and get the phone working again. But there is no version of Oreo/Nougat that can be installed with a V7 bootloader.
Also, there is absolutely no Engineering Mode (NOT Developer Mode) available under this stock Android 9 Pie, either by code or by app/settings. Does anybody know of an exact Android 9 Pie stock ROM with an accessible no-root Engineering Mode?
And I've tried every way out there to force OEM Unlock to appear, but the bugs that work in Oreo and Nougat have all been patched and none of them work on Android 9 Pie. So I'm stuck with this ROM and bootloader
So I'm here today with these issues in hopes someone may have solutions for:
A way to force OEM Unlock to appear under Android 9 Pie (as no Oreo/Nougat hacks work under Pie)
A way to bypass KG state under stock Android 9 Pie (as no Oreo/Nougat hacks work under Pie)
A way to install Android 8 Oreo or Android 7 Nougat with a V7 bootloader
A stock ROM with Engineering Mode available
A way to change the IMEI without root
A way to modify the V7 stock ROM so it installs a Nougat/Oreo ROM instead of Pie
Another option to keep this phone from just being a fancy, pretty paperweight
Any solution we or I may discover, I will clean it up and make a guide to help others with these same issues as there is not much info yet V7 on bootloaders. So this is a group activity that could help many, many people; help me help us all!
Thank you all in advance for anything you can offer to help!
-DL
EDIT 1: I forgot to mention that the KG State is stuck on "Checking...." so I couldn't get "OEM Unlock" even by waiting
Click to expand...
Click to collapse
There is no OEM unlock on us snap dragon devices. Locked boot loader. Closest you will get is the combination firmware. But the OEM unlock in that does not work trust me on this. The imei is cert coded to the hardware. And can't be discussed on xda how to change. It's possible. But not by just anyone. The combination files are nougat. But their not going to help you out in this situation
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.
After further testing (well actually I mean bricking my device a few times) it turned out that rebranding is not needed for the update from mm to nougat, although your device will boot into a "test" system instead (This is likely due to the vendor information being mismatched). Your p9 would still work with HWOTA7.
The original post has not been changed.
I got hold of an EVA-AL10 model from China. However it was still stuck on emui 4.1 Android 6.
Spoiler
After some research, I found out that Chinese internet was ridiculously unreliable and riddled with useless information, and the fact that most Chinese are tech-illiterate does not help either. Then I turned to good old XDA and found out a few (pretty obsolete posts) that had similar problems and got them solved. However, they all (unsurprisingly) involved the European model (EVA-L0X), which had different firmware.
I then got in contact with a former Chinese colleague. With his help, I managed to send an email to Huawei China and get a representative. After giving him his phone number and all information in the about section of the phone (IMEI and stuff) they took an entire day only to phone him back saying he needs to go to a repair shop. They told him that the oldest version of EMUI available for update was for emui 8 (Android 8) so that was a dead end.
After more searching, I stumbled across a thread about rebranding an European model into the one I got to get to, ironically, emui 8.
Spoiler
According to a Chinese nationalist blogger, it turns out that Huawei severely displeased our international community due to halting the provision of bootloader unlock codes, and they dicided to get us back by not updating us to emui 8. Although there might be more reasons than that, the fact is clear that they had to change their model.
Luckily, XDA is the perfect platform to find help.
Spoiler
Although the in-house search engine is relatively good at dealing with the Chinese e-thefts which take the hard work of this community and sell it shamelessly in China,
a fair amount of time was taken to Google search, however it was definitely worth the effort. Soon, I drew out a simple flowchart to update my p9:
1. Unlock bootloader
2. Rebrand the phone to European model
3. Update to Android 7
4. Rebrand back
5. update to Android 8
(6. Do cool stuff)
Unlocking the bootloader is now a hard part for some. (make sure you have backed up your data on the phone because it will do a factory reset)
Spoiler
While unlocking services here are mostly genuine, it is 75% scam in China. My friend maaged to get my bootloader unlocked from a (crazy) shopping site in China named Taobao, which is well-known for selling fake sneakers and even Uranium. It only costed me two dollars.
Make sure to keep the unlock code. You need it later. If you forgot your unlock code but have it unlocked, no worriess. You can root your phone (I used good old supersu) follow this guide (the commands are the important part, I personally have not verified this method though)
You can also try this tool:
Huawei Nova 2 Plus Bootloader Unlock (Solution)
Hello Developers! I have found an easy way to unlock the bootloader of our Huawei Nova 2 Plus. No need to use Testpoint or pay for software to unlock. it is an Python Script which would brute force the code through the IMEI number you have...
forum.xda-developers.com
However it was intended for another device so your luck may vary.
After that, I used SRKtool to rebrand the phone, although the software of the phone itself has not changed. Keep in mind after the rebrand not to reboot into the system, as it will cause an error. (see below post) If you do manage to get into the system unfortunately, it will ask you for your password (bootloader unlock code) Do not enter the code, shut down your phone and get into fastboot by holding down power and volume down WHILE cable is attached to computer.
After trying hard to get into TWRP, I used this guide to boot into it (turns out I was not quick enough)
I then used this file to update it to the European android 7, which worked perfectly. You do need to enter the unlock code again though, and you need an SDcard or an USB disk that supports OTG(so the device can recognise it in twrp).
After that, you can follow this guide to get it to Android 7 Chinese version(399). I got my friend to set up a vpn connecting to China, where the Chinese system recognized that it could update to android 8. If yours does not, follow the guide to update it to android 8. It already contains the firmware, so do not download other firmware (unless you prefer). If you already got the firmware, use the androidfilehost link he provided and find in the older versions V1.1, which did not have the firmware to save time (and possibly bandwidth)
You will have your bootloader locked at this stage. If you want to stay on the Chinese firmware (Which has a lot of bloatware and needs you to manually sideload playstore apk) do not unlock it. If you do want to go further and install a custom treble GSI, go ahead and unlock the bootloader, and follow the instructions,
Error after force rebranding location with SRKtool:
After using SRKtool to rebrand, your system boot warning will turn from unlocked to unverified (text color orange to red)
If you continue to boot, it will go to a screen where you have to enter a password (the bootloader unlock code) you should not enter the code.
If you still proceed to enter the code, you will be "greeted" with a message telling you that the data on your phone is corrupt and you have to factory reset. after you boot into the OS, you will see this "mix" of the classic nexus 2012 style wallpaper with some android app icons (such as settings) in the aosp style, with everything else that are Huawei-branded seen in 2012-style icons. This has to do with a theme engine bug.
In the about page you might also notice that the system version has been slightly changed. the "al10" part has been deleted but the c00 still remains. The page where the CE and FCC stuff are displayed (forgot precise wording) now lists the phone as "eva-l09"
Go into settings and developer options as usual. You should now see that there is an oem unlock opion that has been toggled off. turn it on.
Reboot into fastboot again. You would see that most commands you would usually use such as flash recovery and erase would not work anymore(returns command not allowed) This has to do with the bootloader locked although it technically unlocked. Unlock it as you would normally do. If this does not work, reboot and turn off oem unlock, go to fastboot and enter the unlock command (it would obviously not work but it registers that wants to be unlocked), reboot and turn on oem unlock again and reboot into fastboot, then you should unlock the bootloader and flash recovery again.