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
Related
DISCLAIMER: I'm not responsible for anything that happens to your device. Use the steps below at your own risk . Be mindful of the facts unlocking bootloader voids your warranty and also hard resets your device - ALL YOUR DATA, SETTINGS, FILES AND APPS WILL BE DELETED. These steps worked for me - I own Chinese version of 8.4" LTE model. I do not know if they will work for any other models of M5, including European versions, WiFi only version and 10" models.
To execute the steps below you will need to obtain unlock code, specific to bootloader of your device. There is a slow, painful and free way to get it, and there is a quick and easy way to get the code instantly, which will cost you 4 euros. The slow way is to create Huawei ID, register on Huawei website and request the unlock code directly from Huawei, through dedicated link they provide. I do not use this method, so I don't have the link - do not ask. You will have to provide justification why you need it, such as being a developer and you bought the device to develop and make a living off of it - something Huawei support would find reasonable. In most cases they will not agree to unlock bootloader if you just tell them you want to install some roms. In this guide I will be describing the other method to get it done, which costs 4 euros.
Follow these steps.
1. Go to DC Unlocker website, register for an account (or login, if you already have one)
2. Buy 4 credits (cost is 4 euro) using the Buy link
3. Download the latest DC Unlocker client (pictures 1,2 below)
4. Open the DC Unlocker client, click "server" tab on the right (picture 1) , enter your website login you created in step 1 and click "Check Login"
5. Select "Huawei phones" from "Select manufacturer" dropdown
6. On your M5, go to Dialer app, and type in *#*#2846579#*#* to open Project Menu
7. Click Background Settings->USB Port Settings->Manufacture Mode
8. Connect your M5 to PC via USB cable and return to DC Unlocker client
9. Click the Search button to detect your device. It should be detected as "Huawei HiSilicon Kirin Android" (picture 1)
10. Click "Unlocking" tab
11. Click "Read Bootloader Code"(picture 2). It may not work on the first try, but don't worry - unsuccessful bootloader code reads do not spend your credits. Give it a few seconds, disconnect/reconnect USB cable and try again
12. Copy and save generated bootloader code
13. Download Huawei Multi Tool from the bottom of this page and install it
14. Boot into download mode by powering off your M5, then holding Vol Down + Power keys simultaneously for a few seconds and then plugging in USB cable while still holding these 2 keys
15. Open Multi Tool v8 and paste the code you got from DC Unlocker into "Get Unlock Key" input field
16 Click "Use your key" button next to it (picture 3)
17. On the bottom right click the green "Unlock bootloader" button
18. You will get a bunch of warnings on your M5 screen about unlocking bootloader - press Vol Up key and then Power key
19. At this point your bootloader will be unlocked and M5 will factory reset itself
Note: using Multi Tool is optional. Instead, if you have ADB tools with fastboot installed on your PC, then after step 14 you can just use fastboot to unlock your bootloader, by typing "fastboot oem unlock <code>"
Note 2: I don't do tech support via PM, so don't PM me for help or with questions. Use the thread instead, and some other XDA members or myself will probably help you. Good luck!
Now I'm hoping some dev takes a shine to our phablet, and compiles TWRP build for it. It can certainly be installed now that we managed to unlock the bootloader
To enter Project Mode on Wifi only tablets, open calculator and enter () () 2,846,579 () (). On 10.8" tablet, it will need to be in landscape mode to get all the calculator symbols to show.
Am I right that warranty is still intact, as Huawei does not know what we are doing?
as long as we relock it when we are done ?
Apo11on said:
2. Buy 4 credits (cost is 4 euro) using the Buy link
Click to expand...
Click to collapse
Why do we have to pay for it? I bet there's an easy way to unlock it without to pay, isn't it?
This Page describe an unlock process for huawei devices that's likely the prozess for Google or Motorola devices.
Isn't it working on the M5, too?
Marcopoloy13 said:
Why do we have to pay for it? I bet there's an easy way to unlock it without to pay, isn't it?
This Page describe an unlock process for huawei devices that's likely the prozess for Google or Motorola devices.
Isn't it working on the M5, too?
Click to expand...
Click to collapse
I think an answer for using the "unofficial" way would be that officially having an unlocked bootloader may void your warranty and I do not know how nice Huawei plays with that, so that the "official" way is not the best option to many people ...
If the device is halfway bricked, however, and you cannot restore the locked bootloader, they still know and are not too friendly either, because one did not use the proper method ...
kev1807 said:
I think an answer for using the "unofficial" way would be that officially having an unlocked bootloader may void your warranty and I do not know how nice Huawei plays with that, so that the "official" way is not the best option to many people ...
If the device is halfway bricked, however, and you cannot restore the locked bootloader, they still know and are not too friendly either, because one did not use the proper method ...
Click to expand...
Click to collapse
Your assumptions are incorrect. Warranty is voided no matter whichever way you use to unlock. The correct answer to Marcopoloy13' post is that (1) he doesn't "have to" do anything, and (2) the site he linked, simply echoes what I already said in the OP - that you can contact Huawei to request the unlock code.
Was just guessing
Apo11on said:
Your assumptions are incorrect. Warranty is voided no matter whichever way you use to unlock. The correct answer to Marcopoloy13' post is that (1) he doesn't "have to" do anything, and (2) the site he linked, simply echoes what I already said in the OP - that you can contact Huawei to request the unlock code.
Click to expand...
Click to collapse
I requested the unlock code via email. They were quick in replying but none of the codes they sent worked. They sent me 4 different codes and one was even my tablets serial number! Gave up asking in the end and will just use dc unlocker.
If you have been successful unlocking your M5 bootloader using the steps provided - please share your experience here, including any kind of problems you've encountered and how did you solve them. This will help others.
Worked for me with no issues. Quick and easy.
magnumlove said:
Worked for me with no issues. Quick and easy.
Click to expand...
Click to collapse
Which Model do you use? And congrats for unlocking.
florian-m19 said:
Which Model do you use? And congrats for unlocking.
Click to expand...
Click to collapse
CMR-W09 (10.8" wifi)
after you successful unlock youre device, is it possible to root it without twrp ?
florian-m19 said:
after you successful unlock youre device, is it possible to root it without twrp ?
Click to expand...
Click to collapse
You could have a look at this thread from the Huawei Mate 9 forum and give it a try but with relevant Mediapad M5 firmware! https://forum.xda-developers.com/mate-9/how-to/guide-install-magisk-mate-9-running-t3773878
magnumlove said:
You could have a look at this thread from the Huawei Mate 9 forum and give it a try but with relevant Mediapad M5 firmware! https://forum.xda-developers.com/mate-9/how-to/guide-install-magisk-mate-9-running-t3773878
Click to expand...
Click to collapse
Is there a way back if it does not work?
I also have the CMR-w09 how ever DC can not find the device i have it fully installed on my windows 10 maybe it is because of HI(hiwai sync)?
---------- Post added at 03:58 PM ---------- Previous post was at 03:53 PM ----------
Marcopoloy13 said:
Why do we have to pay for it? I bet there's an easy way to unlock it without to pay, isn't it?
[new user can not post url"]This Page[/XXX] describe an unlock process for huawei devices that's likely the prozess for Google or Motorola devices.
Isn't it working on the M5, too?
Click to expand...
Click to collapse
I tried this but the link does not open to register for unlock? also i am based in Uk and there is no option to give a UK number
---------- Post added at 04:19 PM ---------- Previous post was at 03:58 PM ----------
m5mediapad said:
I also have the CMR-w09 how ever DC can not find the device i have it fully installed on my windows 10 maybe it is because of HI(hiwai sync)?
---------- Post added at 03:58 PM ---------- Previous post was at 03:53 PM ----------
I tried this but the link does not open to register for unlock? also i am based in Uk and there is no option to give a UK number
Click to expand...
Click to collapse
I am trying yo get debian9 with xfce fully installed on this tablet with NO andriod system running such as linux deploy or VNC....
Am I the only one who couldn't get these instructions to work?
I can't get the device to install cleanly on either or my two Windows PCs. Perhaps I need drivers?
Perhaps as a result, DC Unlocker won't find my phone via automatic detection.
I might be able to get a code elsewhere - but I also can't get this thing to boot into Download mode.
Am I supposed to enable anything in Developer Options?
When I hook up to my PC, I get asked whether I want to charge only or xfer files or photos. Does it matter what I select?
Manufacture mode tends to revert back to Hisuite mode after I disconnect the USB cable.
Thanks...
(ETA - I figured out DL mode - the instructions say "power keyS" not "power key" - my bad)
(ETA - I got my key from DC. Got the following error message from Multi-Tool - 'Error! Unable to execute command, check the status of Bootloader and FRP (Phone Finder).' I'll figure this out.)
(ETA - turns out you have to enable OEM unlocking, who'd a thunk it. For the record, I'm not that Android illiterate, this is simply the first device I have bought in years, the first device I've bought within days of first root, and I'm used to everything being spelled out. Big thanks to the OP nonetheless!)
thref23 said:
Am I the only one who couldn't get these instructions to work?
I can't get the device to install cleanly on either or my two Windows PCs. Perhaps I need drivers?
Perhaps as a result, DC Unlocker won't find my phone via automatic detection.
I might be able to get a code elsewhere - but I also can't get this thing to boot into Download mode.
Am I supposed to enable anything in Developer Options?
When I hook up to my PC, I get asked whether I want to charge only or xfer files or photos. Does it matter what I select?
Manufacture mode tends to revert back to Hisuite mode after I disconnect the USB cable.
Thanks...
(ETA - I figured out DL mode - the instructions say "power keyS" not "power key" - my bad)
(ETA - I got my key from DC. Got the following error message from Multi-Tool - 'Error! Unable to execute command, check the status of Bootloader and FRP (Phone Finder).' I'll figure this out.)
(ETA - turns out you have to enable OEM unlocking, who'd a thunk it. For the record, I'm not that Android illiterate, this is simply the first device I have bought in years, the first device I've bought within days of first root, and I'm used to everything being spelled out. Big thanks to the OP nonetheless!)
Click to expand...
Click to collapse
How'd you fix the device not being detected? I've tried everything to get drivers installed, but none of them work. I'm stuck at finding the phone via automatic detection.
PewPewK said:
How'd you fix the device not being detected? I've tried everything to get drivers installed, but none of them work. I'm stuck at finding the phone via automatic detection.
Click to expand...
Click to collapse
I'm not 100% sure, but three things:
Make sure to enable USB debugging via Developer Options.
Make sure you are still in Manufacturer mode, and have not been reverted back to Hisuite mode, before hooking it up to your PC .
I installed and opened Multi-Tool before I successfully generated a code; I forget if I did anything in particular, but it prompted me to download a Huawei_Drivers zip file that I might or might not have needed.
thref23 said:
I'm not 100% sure, but three things:
Make sure to enable USB debugging via Developer Options.
Make sure you are still in Manufacturer mode, and have not been reverted back to Hisuite mode, before hooking it up to your PC .
I installed and opened Multi-Tool before I successfully generated a code; I forget if I did anything in particular, but it prompted me to download a Huawei_Drivers zip file that I might or might not have needed.
Click to expand...
Click to collapse
I managed to fix it, but I'm also not clear on what I did that caused it to work for others who might be running into the problem.
The last thing I did before it worked was install and update the latest HiSuite from Huawei's website. Otherwise I also was trying to install the Huawei drivers from Multi-Tool. Either one of those is likely the culprit for it finally working.
So I got this phone recently and I want to root it, but can't find any method with enough information and walk through.
It says "Your device is unlocked" under UICC Unlock. Also the OEM unlocking in the developer option is grayed out. So where do I go from here in order to unlock bootloader and then root? help please!
Zenith_39 said:
So I got this phone recently and I want to root it, but can't find any method with enough information and walk through.
It says "Your device is unlocked" under UICC Unlock. Also the OEM unlocking in the developer option is grayed out. So where do I go from here in order to unlock bootloader and then root? help please!
Click to expand...
Click to collapse
Same here just got my new phone today, but i cant even get the developer options to activate i keep pressing the build number but nothing happens.
machetie said:
Same here just got my new phone today, but i cant even get the developer options to activate i keep pressing the build number but nothing happens.
Click to expand...
Click to collapse
you need to tap on the software version
Cool, I finally figured out. OEM is greyed out in dev tools. Found an xda sprint bootloader unlock thread, but still no luck. Waiting to download now debrand conversion sprint OnePlus 7 pro 5g to european FW file. Not sure if you want to do that, but that's my next step. https://forum.xda-developers.com/oneplus-7-pro/how-to/discussion-oneplus-7-pro-5g-rom-gsi-t4042583
The same here. I have my 7 pro 5G sprint for 15 days and I still haven't been able to root it. Above all, my English is not very good and I don't want to be wrong. If anyone makes progress, please share..
jip said:
The same here. I have my 7 pro 5G sprint for 15 days and I still haven't been able to root it. Above all, my English is not very good and I don't want to be wrong. If anyone makes progress, please share..
Click to expand...
Click to collapse
If you find anything let me know please.
How to root Sprint Oneplus 7 pro 5g GM1925
Here are the steps that I found, from trial and error, to root Sprint Oneplus 7 pro 5g GM1925:
Disclaimer: I'm new to this. I did it on Windows 10. Maybe there is a simpler, shorter, and efficient way to do it, but I don't know it.
Some errors I did:
1. Unlocking the bootloader in Android 10. I could have done the procedure wrong, but when I tried unlocking the bootloader in Android 10 it didn't work. Yes, I could unlock it, but the phone wouldn't boot to "normal" and the recovery didn't work too; it just stood in a fastboot (if that is what is call) even when selecting start. Meaning I brick my device, but no worries I'm writing this because I manage a way to do it.
2. Updating the phone early in the steps to Android 10.
Steps:
1. Go to https://www.xda-developers.com/what-is-adb/ read and follow. You'll need this later. TIP Remember to select the "Default USB configuration" to "Transferring files" in developer options.
2. Power off your device. Connect the charging cable to the computer but NOT to the phone. On your computer right-click on the windows logo (the logo in the bottom left if you have the taskbar in the bottom). From there select "Device Manager". Hold both volume buttons (+ and -), and connect the charging cable to the phone. While holding the volume buttons, in Device Manager you should see that your phone is registered by a driver with a yellow exclamation mark. Update that driver. Disconnect the phone from the charging cable.
3. Go to https://forum.xda-developers.com/oneplus-7-pro/how-to/sprint-msmdownloadtool-unbrick-t3989841 and follow the steps. In summary, download the file provided and use it. This will format the phone. When it is done do a quick setup, the next step is going to format it again. This step will put the device in Android 9, but do NOT update. Remember to set up the phone for ADB.
4. Go to https://forum.xda-developers.com/on...otloader-unlock-sprint-oneplus-7-pro-t4042145 and follow the steps. In summary download, the file provided and use it. This step will unlock the bootloader. Do NOT update. After boot, remember to set up the phone for ADB. TIP The moment the application screen says is done (the download bar is green) rapidly hold both volume buttons (+ and -).
5. Finally, go to https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-bootloader-unlock-twrp-install-t3940368 and follow the steps/links starting from the part of installing TWRP (the bootloader is already unlocked in step 4). In the link I provided, they'll be a link (the last one) that will let you update the phone, follow the steps layout there.
I hope this helps and works.
So basically what I learned is you have to flash a developer preview of 10. Unlock the bootloader then downgrade back to a stable international and then update and root. Fastboot commands where broken or not recognize in the dev preview so you had to switch up. But the dev prev allowed the oem unlock to be checked
TheMadScientist said:
So basically what I learned is you have to flash a developer preview of 10. Unlock the bootloader then downgrade back to a stable international and then update and root. Fastboot commands where broken or not recognize in the dev preview so you had to switch up. But the dev prev allowed the oem unlock to be checked
Click to expand...
Click to collapse
I didn't understand some parts if not all of what you wrote, a bit lost with the terms like developer preview of 10, dev preview, and international (what does it mean in Android). I'm new to this. But what I can certainly affirm is, in an overview and in some way, I downgraded, did everything there: unlock the bootloader and root, and finally update.
wint1014 said:
I didn't understand some parts if not all of what you wrote, a bit lost with the terms like developer preview of 10, dev preview, and international (what does it mean in Android). I'm new to this. But what I can certainly affirm is, in an overview and in some way, I downgraded, did everything there: unlock the bootloader and root, and finally update.
Click to expand...
Click to collapse
Im new here, today i bought this phone in the sprint variant, but i have a big question, is possible to use a dual sim in this phone?, i saw the tutorial to the T Mobile version, but i cant find anything about this version, thanks.
ilooooy said:
Im new here, today i bought this phone in the sprint variant, but i have a big question, is possible to use a dual sim in this phone?, i saw the tutorial to the T Mobile version, but i cant find anything about this version, thanks.
Click to expand...
Click to collapse
Sorry to say, the answer is no. I have the Sprint model too, GM1925. No Dual SIM. (And now, thanks to Sprint AND T-Mobile, no 5G for us anymore EITHER! I'm pissed. But off topic...) See here, quote from Whoareyou, comment #18:
https://forum.xda-developers.com/oneplus-7-pro/help/5g-version-dual-sim-t3938677/page2/
This is incorrect, there is no way to enable dual SIM on the GM1920 or GM1925. This would require a modem.img with the SDX50 dsds configs, which we don't have.
you can however the flash the European 10 update on to the Sprint model, there are issues with Sprint data, but non Sprint carriers work fine.
Click to expand...
Click to collapse
/d3viant/ said:
Sorry to say, the answer is no. I have the Sprint model too, GM1925. No Dual SIM. (And now, thanks to Sprint AND T-Mobile, no 5G for us anymore EITHER! I'm pissed. But off topic...) See here, quote from Whoareyou, comment #18:
https://forum.xda-developers.com/oneplus-7-pro/help/5g-version-dual-sim-t3938677/page2/
Click to expand...
Click to collapse
Mmm, its terrible, i bought the phone recently is amazing but i come from using xiaomi devices and by me is necessary to used the dual sim. well, let me check if i can buy this version and buy a the international version. In conclusion, i cant unlock the dual version nor changing it to the international rom?
Thanks.
wint1014 said:
How to root Sprint Oneplus 7 pro 5g GM1925
Here are the steps that I found, from trial and error, to root Sprint Oneplus 7 pro 5g GM1925:
Disclaimer: I'm new to this. I did it on Windows 10. Maybe there is a simpler, shorter, and efficient way to do it, but I don't know it.
Some errors I did:
1. Unlocking the bootloader in Android 10. I could have done the procedure wrong, but when I tried unlocking the bootloader in Android 10 it didn't work. Yes, I could unlock it, but the phone wouldn't boot to "normal" and the recovery didn't work too; it just stood in a fastboot (if that is what is call) even when selecting start. Meaning I brick my device, but no worries I'm writing this because I manage a way to do it.
2. Updating the phone early in the steps to Android 10.
Steps:
1. Go to https://www.xda-developers.com/what-is-adb/ read and follow. You'll need this later. TIP Remember to select the "Default USB configuration" to "Transferring files" in developer options.
2. Power off your device. Connect the charging cable to the computer but NOT to the phone. On your computer right-click on the windows logo (the logo in the bottom left if you have the taskbar in the bottom). From there select "Device Manager". Hold both volume buttons (+ and -), and connect the charging cable to the phone. While holding the volume buttons, in Device Manager you should see that your phone is registered by a driver with a yellow exclamation mark. Update that driver. Disconnect the phone from the charging cable.
3. Go to https://forum.xda-developers.com/oneplus-7-pro/how-to/sprint-msmdownloadtool-unbrick-t3989841 and follow the steps. In summary, download the file provided and use it. This will format the phone. When it is done do a quick setup, the next step is going to restore it again. This step will put the device in Android 9, but do NOT update. Remember to set up the phone for ADB.
4. Go to https://forum.xda-developers.com/on...otloader-unlock-sprint-oneplus-7-pro-t4042145 and follow the steps. In summary download, the file provided and use it. This step will unlock the bootloader. Do NOT update. After boot, remember to set up the phone for ADB. TIP The moment the application screen says is done (the download bar is green) rapidly hold both volume buttons (+ and -).
5. Finally, go to https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-bootloader-unlock-twrp-install-t3940368 and follow the steps/links starting from the part of installing TWRP (the bootloader is already unlocked in step 4). In the link I provided, they'll be a link (the last one) that will let you update the phone, follow the steps layout there.
I hope this helps and works.
Click to expand...
Click to collapse
I tried doing this but #2 isnt working, nothing pops up on the device manager screen and my pc keeps making the sound when you connect and disconnect a device to the pc.
Zenith_39 said:
I tried doing this but #2 isnt working, nothing pops up on the device manager screen and my pc keeps making the sound when you connect and disconnect a device to the pc.
Click to expand...
Click to collapse
Hello man. I know it has been a long time and I haven't responded to or help you, but here I am.
In Step 2 you are updating/installing the driver so the Phone can be recognized on your PC. What I can infer from this message is that you already have the driver; that means that you can continue to the next step. If that is not the case -you don't have the driver install- then selected one of the following two links to download the driver: Link #1 https://www.driverarchives.com/pc/hp/bm388aa-abm/231997/qualcomm-hs-usb-qdloader-9008-com4-.html Link #2 https://gsmusbdrivers.com/download/android-qualcomm-usb-driver/
I recommend Link #2. In both, you'll need a program that unzips the file -I recommend 7-zip (https://www.7-zip.org)-. Then run the executable file where you'll install the driver. And definitely after that, you can continue to the next step.
I hope this helps and works.
I can't find anything definitive about whether it's rootable or not
Same here i tried every root app possible and failed.
just unlock bootloader and flash twrp
after that flash latest magisk zip hope it will work
Bhanu8082 said:
just unlock bootloader and flash twrp
after that flash latest magisk zip hope it will work
Click to expand...
Click to collapse
No need to flash TWRP: Booting into it is sufficient.
Bhanu8082 said:
just unlock bootloader and flash twrp
after that flash latest magisk zip hope it will work
Click to expand...
Click to collapse
How did you unlock the bootloader?
sCriptKittY1987 said:
How did you unlock the bootloader?
Click to expand...
Click to collapse
simple , go to about phone and try to find build number,
after you find build number tap on it until it says you are in developer mode
after that head on to developer option (it may be inside about phone section or above about phone section) turn on the option which says allow oem unlock. then,
just reboot to recovery mode either by pressing volume up or volume down key with power button.
after you enter recovery connect usb cable and open command prompt in pc and make sure that lg device drivers are installed on your pc also make sure you have adb and fastboot installed.
ok, after all this type command
adb devices
if any thing shows us then you have successfully connected your device.
after it type
adb reboot bootloader
then your mobile should restart and show fastboot mode in screen
type command
fastboot oem unlock
and done your bootloader is unlocked.
Bhanu8082 said:
just unlock bootloader and flash twrp
after that flash latest magisk zip hope it will work
Click to expand...
Click to collapse
Where did you find a tarp img for the LG k51?
sCriptKittY1987 said:
Where did you find a tarp img for the LG k51?
Click to expand...
Click to collapse
tarp image????? just follow the tutorial.
I meant TWRP recovery . After you've unlocked the bootloader where did you get a custom recovery to flash for the LG k51. From what I saw on Team Wins website, there isn't one.
Bhanu8082 said:
simple , go to about phone and try to find build number,
after you find build number tap on it until it says you are in developer mode
after that head on to developer option (it may be inside about phone section or above about phone section) turn on the option which says allow oem unlock. then,
just reboot to recovery mode either by pressing volume up or volume down key with power button.
after you enter recovery connect usb cable and open command prompt in pc and make sure that lg device drivers are installed on your pc also make sure you have adb and fastboot installed.
ok, after all this type command
adb devices
if any thing shows us then you have successfully connected your device.
after it type
adb reboot bootloader
then your mobile should restart and show fastboot mode in screen
type command
fastboot oem unlock
and done your bootloader is unlocked.
Click to expand...
Click to collapse
When I typed fastboot oem unlock I get a reply saying <waiting for any device>
sCriptKittY1987 said:
When I typed fastboot oem unlock I get a reply saying <waiting for any device>
Click to expand...
Click to collapse
I doubt that's going to work, but let me know if it does. Carriers and manufacturers use a variety of sophisticated security schemes like requiring lengthy codes that only they can provide, etc to purposely make it very difficult to unlock bootloaders. Tmobile gave me a K51 for free. They apparently feel the have to pay for it by spying on me. I bought a moto g7 plus unlocked for $117 directly from Moto and put Lineage on it, no gapps Would love to use thie k51 though if anyone figures it out because it's more waterproof and bigger battery.
mgsgta3 said:
I can't find anything definitive about whether it's rootable or not
Click to expand...
Click to collapse
Whether device's bootloader is unlockable / device's Android is root-able or not you easily can find out by means of ABB:
Code:
adb shell "getprop ro.oem_unlock_supported"
If returned value is 1, then it's supported otherwise it's not.
sCriptKittY1987 said:
Where did you find a tarp img for the LG k51?
Click to expand...
Click to collapse
and let me guess my doofus luck im guessing no way to unlock it with out a P.C. like nuttin at all?
Absolutely no of the crap above works at all in any capacity especially sprint. Generic postings like hold volume down and power also doesn't work to go into fastboot so if you guys are following the advice of some of these guys don't because you'll drop more money on a new phone then you will unlocking it some variants verizon is one I think you have to call LG I know I spent 6 hrs on the phone with "tech support" aka "jokes with a screen to read from" to FINALLY get into touch with an engineer who told me the only way "NOW" to unlocked the bootloader is in his office which means it has to be depot to be unlocked which as of this moment lg is not doing that WILL change in the future that was 12/03/2020. Even running external adb with kali linux to hack it broke the bootloader and sends you into an infinite reboot loop
jwoegerbauer said:
Whether device's bootloader is unlockable / device's Android is root-able or not you easily can find out by means of ABB:
Code:
adb shell "getprop ro.oem_unlock_supported"
If returned value is 1, then it's supported otherwise it's not.
Click to expand...
Click to collapse
This returns no value on a locked bootloader because even with Dev. Opt. Enables its still read only until bootloader is unlocked this is verified on two carriers k51's sprint and att. However it is unlockable we haven't found it and/or LG has not added this service to their site which is where you will get the info needed for the unlocked.
Oh my. You know you need to do all this from a computer, right? Can't do it in an Android terminal because fastboot commands are only valid in a phone's bootloader environment. And if you didnt know that then rooting and all of the dangers that come with it just isnt for you. But yes, it's rootable. So here you go anyway.
Reboot the phone to download mode.
Install LG's K51 usb drivers, and install adb and fastboot, on your computer.
Open a command prompt and type: fastboot oem unlock
If it does anything other than pat you on the back and tell you it's proud of you and how well you follow instructions, then go back and follow the effing instructions.
Otherwise, type: fastboot reboot.
Download magisk manager.
Do the magisk manager.
Use the LG flash tool on your computer to flash what you just did when you did the magisk manager.
And presto, you're rooted. Or I successfully left out enough info and you dont know how to use Google, leaving your device still not rooted. And thank god for that.
Ive been learning from xda for some time now. Bricked a few phones in my learning curve and tonight i had my first success with my g7, and wrighting this on my new k51. This is my first post and I think that was pretty rude of you to say. This is supposed to be a place to learn, share knowledge, and help those who are less educated. Not look down on people and say crap like that. If he wants to learn even if it takes a couple bricked phones to do it, let him. Either give him the proper procedures or dont say nothing at all. How long did it take you? How many phones? Its taking me quit a while but i am finaly getting somewhere. Keep with it guy. Dont let this dude, or any one else for that matter, bring you down.
Kenwoodquality69 said:
Ive been learning from xda for some time now. Bricked a few phones in my learning curve and tonight i had my first success with my g7, and wrighting this on my new k51. This is my first post and I think that was pretty rude of you to say. This is supposed to be a place to learn, share knowledge, and help those who are less educated. Not look down on people and say crap like that. If he wants to learn even if it takes a couple bricked phones to do it, let him. Either give him the proper procedures or dont say nothing at all. How long did it take you? How many phones? Its taking me quit a while but i am finaly getting somewhere. Keep with it guy. Dont let this dude, or any one else for that matter, bring you down.
Click to expand...
Click to collapse
Yo Ken,
So your K51 rooted?
If so, maybe you could provide a step by step?
I haven't done this yet but is it verified working? I did a google search came across the method to do the unlocking but it showed it was a failed project?
TexasPride said:
I haven't done this yet but is it verified working? I did a google search came across the method to do the unlocking but it showed it was a failed project?
Click to expand...
Click to collapse
O lord i hope this isnt true
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.