Hey guys, i've been trying to unlock bootloader in realme gt Neo 2 using deep test app, but it just didn't work, just once I run the app, it appears like this, and I don't know what to do tbh. What ways to unlock the bootloader exist besides this one? thank you so much guys
RMX3370_11_A.09 UI 2.0 Android 11
Hi, I followed this guide
Steps 11 and 12 from it are important, this app alone will not unlock bootloader.
lightchess said:
Hi, I followed this guide
Steps 11 and 12 from it are important, this app alone will not unlock bootloader.
Click to expand...
Click to collapse
Thanks for replying, i know just using deep test it's not enough, gotta follow next steps, but i got a problem, deep test does not work for my device so i cannot follow next steps. I've been considering use ADB Fastboot method, but im not sure tbh
alexwhitney845 said:
Thanks for replying, i know just using deep test it's not enough, gotta follow next steps, but i got a problem, deep test does not work for my device so i cannot follow next steps. I've been considering use ADB Fastboot method, but im not sure tbh
Click to expand...
Click to collapse
This app shows the same message for me, but I already unlocked the bootloader.
In your case, maybe approval is not required. I would check "Developer options" in settings, make sure "OEM unlock" and "USB debugging" are both enabled.
If "OEM unlock" was disabled, you can enable it and proceed with step 7 from the guide.
Thank you so much dude.
Related
Hello,
I've read quite a bit about rooting on the new Oreo firmware and having to wait a week before you can enable the OEM unlock, meaning you wont be able to flash anything yet.
However, when I went into developer options RIGHT after I flashed the CRAP build, OEM unlock was already enabled (as shown in the screenshot). Would this indicate that I can go ahead and flash TWRP/magisk to root already?
Thanks in advance,
Cyborg.
cyborgium said:
Hello,
I've read quite a bit about rooting on the new Oreo firmware and having to wait a week before you can enable the OEM unlock, meaning you wont be able to flash anything yet.
However, when I went into developer options RIGHT after I flashed the CRAP build, OEM unlock was already enabled (as shown in the screenshot). Would this indicate that I can go ahead and flash TWRP/magisk to root already?
Thanks in advance,
Cyborg.
Click to expand...
Click to collapse
You should be fine. If you go into download mode and see RMM State Prenormal then you've been locked out from flashing anything.
xxxrichievxxx said:
You should be fine. If you go into download mode and see RMM State Prenormal then you've been locked out from flashing anything.
Click to expand...
Click to collapse
Yeah I didn't see anything like that in download mode so I just went F it and I managed to flash TWRP and magisk. Just to be sure though, I did flash the RMM state fix.
I still don't quite get why my OEM was unlocked when all the other people's got theirs locked. Any ideas?
cyborgium said:
Hello,
I've read quite a bit about rooting on the new Oreo firmware and having to wait a week before you can enable the OEM unlock, meaning you wont be able to flash anything yet.
However, when I went into developer options RIGHT after I flashed the CRAP build, OEM unlock was already enabled (as shown in the screenshot). Would this indicate that I can go ahead and flash TWRP/magisk to root already?
Thanks in advance,
Cyborg.
Click to expand...
Click to collapse
what Oreo firmware did you put
After 212 Hours..... and nothing happened, OEM unlock don't appear in developer option :crying:
WalterSilverio said:
After 212 Hours..... and nothing happened, OEM unlock don't appear in developer option :crying:
Click to expand...
Click to collapse
It doesn't appear you are in developer options but, rather, About Phone, Status.
I know I'm not in the developer option, the screenshot is so you can see that it's already 7 days (168 hours) and even in the developer option it does not show me the oem unlock option
I show you
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
Hi guys I got stolen my oneplus 6, I need advice to try to recover it.
The lock screen is protected with pattern and fingerprint and I read on Internet that from android 8.1 they will be unable to use the phone even if they do factory reset. Is it true?
The bootloader in unlocked but to flash from fastboot you need to enable "OEM unlocking" in developer settings isn't it?
I'm trying to locate with the Google find device tool but it says "can't reach device".
I send the imei numbers to my provider to put in the Black list.
What else I should do?
Are they will able to use the phone?
Are my data safe?
Sent from my H8324 using Tapatalk
Hank87 said:
Hi guys I got stolen my oneplus 6, I need advice to try to recover it.
The lock screen is protected with pattern and fingerprint and I read on Internet that from android 8.1 they will be unable to use the phone even if they do factory reset. Is it true?
The bootloader in unlocked but to flash from fastboot you need to enable "OEM unlocking" in developer settings isn't it?
I'm trying to locate with the Google find device tool but it says "can't reach device".
I send the imei numbers to my provider to put in the Black list.
What else I should do?
Are they will able to use the phone?
Are my data safe?
Sent from my H8324 using Tapatalk
Click to expand...
Click to collapse
the fact that The bootloader is unlocked makes the point need to enable "OEM unlocking" moot. then they could use the debrick method to have a working phone. Last but not least, then just change imei number and have a working OP6. this is just a run down of how it could be done. I'm guessing that the debrick tool might be doing a complete wipe and write operation that might bypass FRP.
MrSteelX said:
the fact that The bootloader is unlocked makes the point need to enable "OEM unlocking" moot. then they could use the debrick method to have a working phone. Last but not least, then just change imei number and have a working OP6. this is just a run down of how it could be done. I'm guessing that the debrick tool might be doing a complete wipe and write operation that might bypass FRP.
Click to expand...
Click to collapse
I know, I'll think twice before unlock the bootloader next time.
But still I think they will not be able to flash from fastboot without enable "OEM unlocking" can someone confirm this?
Is it so easy to change imei? I thought was almost impossible. I don't think that they are so clever and own a debrick tool for oneplus, they're just pickpocket thieves.
Sent from my H8324 using Tapatalk
if your bootloader is unlocked, they don't have to enable "OEM unlocking", it is already enabled and the bootloader already unlocked, they can flash a recovery or kernel or what ever they want, about the paterns and pin i don't know , but sure with the debrick tool they can reflash everything
Hank87 said:
I know, I'll think twice before unlock the bootloader next time.
But still I think they will not be able to flash from fastboot without enable "OEM unlocking" can someone confirm this?
Is it so easy to change imei? I thought was almost impossible. I don't think that they are so clever and own a debrick tool for oneplus, they're just pickpocket thieves.
Sent from my H8324 using Tapatalk
Click to expand...
Click to collapse
Smart or not,when they find out its more job that they anticipated they will just sell it so someone and screw them over aswell. Win + win.. Rarely thieves keep things themselves,they wanna get rid of the evidence.
I'm just imaging the thief browsing this thread taking tips on how to make his new phone usable... ?
That's awful, I bough it not even 1 month ago, I can't believe.
I hope they cannot unlock the phone and leave somewhere so I can recover it.
Sent from my H8324 using Tapatalk
Ok I'm at my end with this convert to global I just can't get it done without error or crashdump. I've been flashing since g1 but this is wuppin my ass. This phone (in2017) is literally unusable on anything except T-Mobile. I've tried it on mint mobile and google Fi and it's the same every time. What I'm offering is $50 to whomever can successfuly remote flash and convert my device to the global software. It's extreme I guess but I need a working device. Thanks all
No need for the money. This is what I did because it didn't work for me after A11 upgraded on TMO. Here's what I do
1. MSM back to stock (I have the 10.5.7 TMO version).
2. No wifi, no sign and no mobile data. Just skip until you get normal screen.
3. In developer options toggle on oem unlock, usb debugging ( I assume you know how to get developer options).
4. In fastboot type command fastboot flash cust-unlock unlock_code.bin (This should say okay and then okay once hit return)
5. Then type fastboot oem unlock (on your phone verify unlock)
6. When the phone boots run through set up (no wifi, no e-mail, no mobile data.
7. Developer options - usb debugging
8. Download the firmware from the global thread. (Do the one with global (i have the 10.5.10 global [ this one is the 15.O.19 global one]))
9. Put your phone in bootloader mode
10. Unzip the firware and run the fashall.bat file.
BOOMSHAKALAKA! Happy modding!
Nathan.7118391 said:
No need for the money. This is what I did because it didn't work for me after A11 upgraded on TMO. Here's what I do
1. MSM back to stock (I have the 10.5.7 TMO version).
2. No wifi, no sign and no mobile data. Just skip until you get normal screen.
3. In developer options toggle on oem unlock, usb debugging ( I assume you know how to get developer options).
4. In fastboot type command fastboot flash cust-unlock unlock_code.bin (This should say okay and then okay once hit return)
5. Then type fastboot oem unlock (on your phone verify unlock)
6. When the phone boots run through set up (no wifi, no e-mail, no mobile data.
7. Developer options - usb debugging
8. Download the firmware from the global thread. (Do the one with global (i have the 10.5.10 global [ this one is the 15.O.19 global one]))
9. Put your phone in bootloader mode
10. Unzip the firware and run the fashall.bat file.
BOOMSHAKALAKA! Happy modding!
Click to expand...
Click to collapse
Cool thanks man. I'm gonna give it a go one more time and see what happens. Also when its in bootloader mode what exactly should it show up as in device manager? Depending on the driver I've seen Kedacom or LeMobile, also Google Inc or IN2017. **** one time it showed as IN2023 not sure why. It needs to show specifically as ____?
Justin credible said:
Cool thanks man. I'm gonna give it a go one more time and see what happens. Also when its in bootloader mode what exactly should it show up as in device manager? Depending on the driver I've seen Kedacom or LeMobile, also Google Inc or IN2017. **** one time it showed as IN2023 not sure why. It needs to show specifically as ____?
Click to expand...
Click to collapse
You know what, I never checked device manager. Follow the MSM thread and then follow the upgrade to global thread and you'll be fine. Just remember to use the A10 firmware. For some reason the A11 didn't work for me. Happy modding!
Nathan.7118391 said:
You know what, I never checked device manager. Follow the MSM thread and then follow the upgrade to global thread and you'll be fine. Just remember to use the A10 firmware. For some reason the A11 didn't work for me. Happy modding!
Click to expand...
Click to collapse
Hey man i wanted to say thank you and i very much mean it. The instructions you put up top should be written again and stickied in the guides section because this is what finally got the in2017 converted. my phone actually rings when people call and i can even dial out now. thanks again bro!!!
ps. now if i can figure out how to root it ill be winning for sure!
Justin credible said:
Hey man i wanted to say thank you and i very much mean it. The instructions you put up top should be written again and stickied in the guides section because this is what finally got the in2017 converted. my phone actually rings when people call and i can even dial out now. thanks again bro!!!
ps. now if i can figure out how to root it ill be winning for sure!
Click to expand...
Click to collapse
Hey bro, diss you get it rooted yet?
Nathan.7118391 said:
Hey bro, diss you get it rooted yet?
Click to expand...
Click to collapse
I surely did and all is working and good to go. Thanks for everything!
Nathan.7118391 said:
You know what, I never checked device manager. Follow the MSM thread and then follow the upgrade to global thread and you'll be fine. Just remember to use the A10 firmware. For some reason the A11 didn't work for me. Happy modding!
Click to expand...
Click to collapse
Hi, i am using A11(11.0.4.6 IN55CB ) could you tell me how to rollback to A10 ?. cuz i know how to do the process and everything but not how to rollback.
I'm looking to purchase this tablet, but want to be sure I can root it before doing so.
The one I'm looking at has the MediaTek Kompanio 1300T processor
I just want to be sure i can remove any factory installed apps, and can install magisk (or similar for tablet) and adblock.
i don't necessarily care about a custom ROM, but lineageOS or AOSP would be a good option, if available.
Thanks
JustinChase said:
I'm looking to purchase this tablet, but want to be sure I can root it before doing so.
The one I'm looking at has the MediaTek Kompanio 1300T processor
I just want to be sure i can remove any factory installed apps, and can install magisk (or similar for tablet) and adblock.
i don't necessarily care about a custom ROM, but lineageOS or AOSP would be a good option, if available.
Thanks
Click to expand...
Click to collapse
The second response on the FAQ for this model has some good information about rooting. The process should be the same if you have the Official global version.
TB132FU - FAQ and How to's
Read carefully: This is a dedicated post for general questions only. If you need technical support about flashing or restoring your device, please use the general topic for TB132FU. Please search for your question below before asking. NEW: How...
forum.xda-developers.com
als_bvg said:
The second response on the FAQ for this model has some good information about rooting. The process should be the same if you have the Official global version.
TB132FU - FAQ and How to's
Read carefully: This is a dedicated post for general questions only. If you need technical support about flashing or restoring your device, please use the general topic for TB132FU. Please search for your question below before asking. NEW: How...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you, that was very helpful. I ordered one from Lenovo directly.
Hello,
My is arrived today how about rooting and instruction for it ?
Turns out, it wasn't possible. I returned mine for this reason
jacobobbo said:
Hello,
My is arrived today how about rooting and instruction for it ?
Click to expand...
Click to collapse
Don't worry about OEM unlocking
Just go ahead and go to bootloader and enter
Code:
fastboot flashing unlock
and you're greeted with a bootloader unlock warning
mingkee said:
Don't worry about OEM unlocking
Just go ahead and go to bootloader and enter
Code:
fastboot flashing unlock
and you're greeted with a bootloader unlock warning
Click to expand...
Click to collapse
Not in my case. Without the ability to toggle OEM unlocking in settings, all efforts to unlock via fastboot (and everything else I tried) were unsuccessful.
i gave up and returned it.
Hopefully @jacobobbo has better luck than I did.
JustinChase said:
Not in my case. Without the ability to toggle OEM unlocking in settings, all efforts to unlock via fastboot (and everything else I tried) were unsuccessful.
i gave up and returned it.
Hopefully @jacobobbo has better luck than I did.
Click to expand...
Click to collapse
I'd use P11 Pro OG if you want to root it because I did it on mine to fix cable content stuttering problem
I don't care L1/L3 because I don't play Netflix on it
JustinChase said:
Not in my case. Without the ability to toggle OEM unlocking in settings, all efforts to unlock via fastboot (and everything else I tried) were unsuccessful.
i gave up and returned it.
Hopefully @jacobobbo has better luck than I did.
Click to expand...
Click to collapse
Are you sure ? I don't wanna brick my device
jacobobbo said:
Are you sure ? I don't wanna brick my device
Click to expand...
Click to collapse
Yes, I tried several times. Nothing happened. It just doesn't unlock the bootloader.
There is another thread I've posted to about this with more stories from others.
I don't think there is much risk of bricking your device, but it is just unlikely to get rooted.
But, maybe you find something I did not and you will be successful.
I really liked the tablet, but refuse to be crippled by a manufacturer that pretends to be protecting me from ... I'm not sure what.
I rooted mine and it was a mistake.
I do not really gain anything out of it and now I cannot update my device anymore.
Do not do it.