Related
Good evening gentlemen.
The Galaxy S and all its variants have an unlock tool, working on a simple method of fetching the code from one of the files on the phone.
I have also seen that some folks who couldn't quite get the easy method to work would actually change some things in their nv_data.bin, which also allowed them to unlock their phones.
I was hoping that some kindly dev, with far too much time on his hands, would figure out a way to unlock the Galaxy Tab in the same way (seeing as both machiens are so similar).
I will help out with whatever I can - files, adb commands, logs, etc - because I want to give my Tab as a gift to a friend, but the damn thing is locked up tight to Vodafone
Galaxy TAB unlock
I tested variant unlock process from Samsung Galaxy S by generating unlock code but didn't work. Process is based on sgux.exe tool that extract code from nv_data.bin file.
I am waiting for an alternate method to get unlock code for this exciting device.
Thanks in advance
there is a person at android.modaco.com who will get the unlock code for your device if you send him the IMEi no. (he tells you how) and your carrier and location... for a fee... 19 UK... fyi
It's in the sticky post at the top of their Galaxy Tab forum
Is there a free way to do it?
Sent from my SGH-T849 using XDA App
Try this; it worked for me.
http://forum.xda-developers.com/showpost.php?p=8942669&postcount=94
I just think I unlocked mine using a similar method to posted above.
Will post instructions shortly when can confirm. Exciting!
Edit: I wrote up a short guide of what I did here: http://forum.xda-developers.com/showthread.php?t=838424
smithdc said:
I just think I unlocked mine using a similar method to posted above.
Will post instructions shortly when can confirm. Exciting!
Edit: I wrote up a short guide of what I did here: http://forum.xda-developers.com/showthread.php?t=838424
Click to expand...
Click to collapse
I prefer to use a confirmed procedure for using with TAB because I tried some working methods for SGS without results at TAB device.
Thanks
I can confirm that this unlock method works, see the link posted above (I even included some screenshots).
I confirmed this method works fine, my Galaxy tab (SFR reunion island) unlock great, thanks again
Yep, it works, I have my tab unlocked a few weeks ago that way but the serial number of the device on the about turn s into 00000000 .. Only problem I have found. Been using it without any glitch so far but I'm still looking for a way that does not mess the device serial number..
smithdc said:
I can confirm that this unlock method works, see the link posted above (I even included some screenshots).
Click to expand...
Click to collapse
Hi smithdc,
Sorry to do not be confident on your procedure, I purchased device two days ago and really worry about an error may brick it. I follow procedure and can confirm you, it works.
Many thanks
Hi Just got a US T Mobile Tab but if I cant unlock I will have to bring it back
This unlock method works!
smithdc said:
I can confirm that this unlock method works, see the link posted above (I even included some screenshots).
Click to expand...
Click to collapse
Thanks smithdc and helroz! This method worked great for me on portuguese GT! And it's really easy too...
Especially smithdc's guide is very easy to follow!
One thing though: don't bother to buy Root Explorer just to move/copy/delete files. A little linux command line knowledge (easy things like "cd, cp, rm" or even "mkdir" - google it if U don't know what I'm talking about) will do the trick using terminal emulator (check out at market). Also I'm using an amazing little proggie called WiFiKeyboard (market again) to use my keyboard to write out the commands on the GT!
If U want your GT rooted and unlocked this is the way to go! Thanks to all the people who have worked on this!! Cheers!
It unlocked mine but I cant get it to work right wit ATT.
Sent from my Nexus One using XDA App
clausnymark said:
Thanks smithdc and helroz! This method worked great for me on portuguese GT! And it's really easy too...
Especially smithdc's guide is very easy to follow!
One thing though: don't bother to buy Root Explorer just to move/copy/delete files. A little linux command line knowledge (easy things like "cd, cp, rm" or even "mkdir" - google it if U don't know what I'm talking about) will do the trick using terminal emulator (check out at market). Also I'm using an amazing little proggie called WiFiKeyboard (market again) to use my keyboard to write out the commands on the GT!
If U want your GT rooted and unlocked this is the way to go! Thanks to all the people who have worked on this!! Cheers!
Click to expand...
Click to collapse
did it change the serial no. to all zeroes as reported above?
thx.
xexes said:
did it change the serial no. to all zeroes as reported above?
thx.
Click to expand...
Click to collapse
Yes, I does change the serial numbers to all zeroes.
You could probably just roll back your nv_data.bin file/you have the serial on the back of your Tab and there should be a way to just edit it back in, in the future.
And the drawbacks to having all zaros for a temporary serial # would be??
I get the warranty issues but I just wanna make sure im not missing something
Sent from my badass SGH-T849 using XDA App
TainT said:
And the drawbacks to having all zaros for a temporary serial # would be??
I get the warranty issues but I just wanna make sure im not missing something
Sent from my badass SGH-T849 using XDA App
Click to expand...
Click to collapse
Well none so far, or that I can think of.
Even with warranty you could just restore the original files. Or if you had broken it so badly that they couldn't load it up then it wouldn't matter anyway.
Tis what I thought....preciate ya bro!!
And all your work.
Hi All,
First I would like to say that I really like this community, everyone helps one another! Now on to my concern.....
I have the Sony Xperia S and now I would like to flash custom roms onto it. I have done this before with my previous phone which was an HTC Wildfire S, so I know a bit about unlocking/s-off. I know that we need to unlock the bootloader to do so and I have read the guides on this forum. (specifically DooMLoRD's guide) I followed it to the letter and I still have not succeeded.
I believe the problem lies in my IMEI code which when I go to the sony unlockbootloader website gives you the unlock code for your phone. I have been trying to unlock this phone for 2 days now!
Sony's website says that we need to input the first 14 numbers of the IMEI code in order to receive the unlock key. Well my code is 16 numbers long. I have tried entering different numbers in order to get different codes (i know this doesnt help much since the codes are specific to the phone but I am desperate now ) and all of them still give me the same error
(bootloader) Unlock phone requested
FAILED (remote: oem unlock failed!)
finished. total time: 0.020s
I have read that this is mainly due to an incorrect key. I have read around the forums and no one seems to give a definitive answer other than "try entering your IMEI again and get another code". Well that wont work with me since the code given to me is always the same.
Can anyone help resolve this?
P.S.
I have all the drivers, software, etc. Even the one click programs such as SE Bootloader_Unlocking_Relocking_1.6. All give the same oem error. I also rooted my phone successfully using Eroot1014, found it on a different website and was scared at first since it was in chinese or korean but it worked anyway.
Tread3r said:
Hi All,
First I would like to say that I really like this community, everyone helps one another! Now on to my concern.....
I have the Sony Xperia S and now I would like to flash custom roms onto it. I have done this before with my previous phone which was an HTC Wildfire S, so I know a bit about unlocking/s-off. I know that we need to unlock the bootloader to do so and I have read the guides on this forum. (specifically DooMLoRD's guide) I followed it to the letter and I still have not succeeded.
I believe the problem lies in my IMEI code which when I go to the sony unlockbootloader website gives you the unlock code for your phone. For purposes of convenience and time (I have been trying to unlock this phone for 2 days now!) I will post my IMEI code here ( 3529000059203526 ) and the unlock code given to me by sony through email (61CAA387DC11C4CF).
I hope this doesnt break any rules or anything.
I am doing this to see if anyone here can help me. Sony's website says that we need to input the first 14 numbers of the IMEI code in order to receive the unlock key. Well as you can see my code is 16 numbers long, so in effect I only entered up to number "5". I would like to know if anyone is willing to test my IMEI and see if they get the same code. I have tried entering different numbers in order to get different codes (i know this doesnt help much since the codes are specific to the phone but I am desperate now ) and all of them still give me the same error
(bootloader) Unlock phone requested
FAILED (remote: oem unlock failed!)
finished. total time: 0.020s
I have read that this is mainly due to an incorrect key, this is why I am posting. I have read around the forums and no one seems to give a definitive answer other than "try entering your IMEI again and get another code". Well that wont work with me since the code given to me is always the same (as above).
Can anyone help resolve this?
P.S.
I have all the drivers, software, etc. Even the one click programs such as SE Bootloader_Unlocking_Relocking_1.6. All give the same oem error. I also rooted my phone successfully using Eroot1014, found it on a different website and was scared at first since it was in chinese or korean but it worked anyway.
Click to expand...
Click to collapse
One line of advice "PLEASE DO NOT POST YOUR IMEIs" anywhere on the web!!! It is very risky and all xda members will agree with me.
The unlock code which sony gave you isn't the one which will help you unlock your phone. The unlock codes are only numbers and there are 4 level codes like SPCK, NCK. NSCK, CCK. Please check your PM for more details.
abhishek1234321 said:
One line of advice "PLEASE DO NOT POST YOUR IMEIs" anywhere on the web!!! It is very risky and all xda members will agree with me.
The unlock code which sony gave you isn't the one which will help you unlock your phone. The unlock codes are only numbers and there are 4 level codes like SPCK, NCK. NSCK, CCK. Please check your PM for more details.
Click to expand...
Click to collapse
Thanks for the advice, I will edit it ASAP.
abhishek1234321 said:
One line of advice "PLEASE DO NOT POST YOUR IMEIs" anywhere on the web!!! It is very risky and all xda members will agree with me.
The unlock code which sony gave you isn't the one which will help you unlock your phone. The unlock codes are only numbers and there are 4 level codes like SPCK, NCK. NSCK, CCK. Please check your PM for more details.
Click to expand...
Click to collapse
Hey he removed the imei number from his original message but that's pointless unless u remove it from your quote
Sent from my Xperia S using xda app-developers app
I've got nearly the same problem, expect that my bootloader was unlocked for a small time.
Did you already get the problem solved? Because you wrote something with PN...
My other Thread: http://forum.xda-developers.com/showthread.php?t=2198967
Chriszo said:
I've got nearly the same problem, expect that my bootloader was unlocked for a small time.
Did you already get the problem solved? Because you wrote something with PN...
My other Thread: http://forum.xda-developers.com/showthread.php?t=2198967
Click to expand...
Click to collapse
Glad to hear im not alone . No I still haven't found a way to unlock it. Sorry for asking but what does "PN" mean? Just so we are clear.
Ok thanks for your answer. No problem, but its just a mistake. Correctly it should be "PM" for personal message. I thought you would write on this way so I cant read any reasults
UPDATE:
I have tried other processes that all have the same steps, be it they were simplified programs with GUI's. I have come to the conclusion that my fastboot driver was installed incorrectly, because the first time I installed it on my phone I was able to see the S1 bootloader icon on device manager and I was able to click on it fast enough to enable it to install the driver. And correct me if im wrong but when we press UP on the volume rocker on our XS's and connect it to the USB we should see a blue right light? Well that is what happens when I do it so I assume I installed it correctly then.
Now after these first few failed attempts at unlocking I got frustrated and just factory reset my phone, completely ( I made back ups of course). This time however I used a program which is suppose to install all the drivers and simplify the whole unlocking process, I dont remember what program exactly, i'll check my files and get back to you guys on that.
Again it failed, showing the FAILED ("oem" error message) so I checked the steps from Doomlords guide and re checked my device manager. This time when I connect my phone it doesnt show the S1 bootloader icon on Dev manager, instead it shows "android phone ADB Interface". BUT I still get the blue LED when I connect my phone via USB, so does that mean I have fastboot on my phone again? ( I assume I do because the program I used says it did install it correctly and it even showed the "install anyway" window)
I am almost loosing all hope to unlock my XS , maybe I got a lemon phone or did something wrong again. I am willing to do another factory reset and restart the whole process again. This time I will follow every single step on the official website and see what happens.
But before I do that I want to ask, does anyone know of any news or whereabouts for an unofficial unlock bootloader process? I know its a long shot because we already have an official way but as from recent experience it doesnt work 100% of the time.
Really nice discription from you, thanks a lot for that
I think your precess that to tried to unlock was nearly the same as mine, but I didn't recognize any other info in the device manager. It's just this "ADB device installed" or something, but I dont know whether it was the same before the whole problem. I didnt really checked it because my first time unlocking the device was secceeded
Maybe thats one of our problems but how should it work correctly? The summary of the sdk driver program was "installation succeeded"...
Is it possible, that the kernel of the last andoid version (AOKP) i flashed is still "in" my device and just cant answer because the bootloader is closed??? Just an idea :/
Chriszo said:
Really nice discription from you, thanks a lot for that
I think your precess that to tried to unlock was nearly the same as mine, but I didn't recognize any other info in the device manager. It's just this "ADB device installed" or something, but I dont know whether it was the same before the whole problem. I didnt really checked it because my first time unlocking the device was secceeded
Maybe thats one of our problems but how should it work correctly? The summary of the sdk driver program was "installation succeeded"...
Is it possible, that the kernel of the last andoid version (AOKP) i flashed is still "in" my device and just cant answer because the bootloader is closed??? Just an idea :/
Click to expand...
Click to collapse
Thanks for the input. Glad to hear your unlocking succeeded, as to the idea that the AOKP or is it AOSP? Well whatever the acronym is, if the kernel of my phone is a reason for my errors, then I would look into that further, because what I did in my first go was simply follow the guide of Doomlord and when that failed I looked elsewhere.
That was when I tried rooting my phone even with a locked bootloader and it worked. I had to update my kernel to .55 from .45 and used a program that did the rest. That COULD be a cause but if its just a kernel it shouldn't disable my bootloader unlocking process since its just a part of the ROM right? That's my understanding of it. Correct me if im wrong.
Tread3r said:
Thanks for the input. Glad to hear your unlocking succeeded, as to the idea that the AOKP or is it AOSP? Well whatever the acronym is, if the kernel of my phone is a reason for my errors, then I would look into that further, because what I did in my first go was simply follow the guide of Doomlord and when that failed I looked elsewhere.
That was when I tried rooting my phone even with a locked bootloader and it worked. I had to update my kernel to .55 from .45 and used a program that did the rest. That COULD be a cause but if its just a kernel it shouldn't disable my bootloader unlocking process since its just a part of the ROM right? That's my understanding of it. Correct me if im wrong.
Click to expand...
Click to collapse
First off, if you're using Windows 7, chances are that your drivers are at fault. If you have the latest Flashtool, you can use those drivers (C:\Flashtool\drivers or C:\Program Files\Flashtool\drivers). If the drivers are correct, then when you boot into fastboot mode, the blue LED is supposed to stay on with a black screen until you unplug and restart your phone (or whatever the guide says).
It was AOKP, the advanced project for this device.
I think your right, but in how far is the bootloader linked to the needed kernel? And why cant the bootloader be unlocked several times...?
Of course the kernel is a main part of the rom, but without an unlocked bootloader even the kernel would not be accepted by the bootloader. Thats the problem with other firmwares/ roms why you have to unlock it
I remember that there was another way to root the stock rom with a little windows batch file that works like a little restore file for the phone.
You can find the link in this forum or here... http://forum.xda-developers.com/showthread.php?t=1886460
For this tool you just need one of the supported firmwares, then you start it and choose your option for the device like 1 for "normal".
The phone will ask you to restore the data that appears on the touchscreen. If it works the batch file will show you the result, otherwise the programm will run "forever". And of course it doesnt work with my device, but what is such wrong the original stock? Does it also has to do with the bootloader??? Or do I just have the wrong firmware (6.1.A.2.55) ?
razormc said:
First off, if you're using Windows 7, chances are that your drivers are at fault. If you have the latest Flashtool, you can use those drivers (C:\Flashtool\drivers or C:\Program Files\Flashtool\drivers). If the drivers are correct, then when you boot into fastboot mode, the blue LED is supposed to stay on with a black screen until you unplug and restart your phone (or whatever the guide says).
Click to expand...
Click to collapse
I am using Windows 7 and I have used flashtool. I believe the drivers are correct because,as you said, the blue LED does show and stay while I fastboot my phone. Same goes for the green LED when I go to flashboot.
Chriszo said:
I remember that there was another way to root the stock rom with a little windows batch file that works like a little restore file for the phone.
You can find the link in this forum or here... http://forum.xda-developers.com/showthread.php?t=1886460
For this tool you just need one of the supported firmwares, then you start it and choose your option for the device like 1 for "normal".
The phone will ask you to restore the data that appears on the touchscreen. If it works the batch file will show you the result, otherwise the programm will run "forever". And of course it doesnt work with my device, but what is such wrong the original stock? Does it also has to do with the bootloader??? Or do I just have the wrong firmware (6.1.A.2.55) ?
Click to expand...
Click to collapse
I have rooted my phone. But since I factory reset it, I unrooted it to start fresh. Everything on my phone is stock again because I want to eliminate any variables that would otherwise mess up the bootloader unlocking process. which I still have yet to achieve
Tread3r said:
I have rooted my phone. But since I factory reset it, I unrooted it to start fresh. Everything on my phone is stock again because I want to eliminate any variables that would otherwise mess up the bootloader unlocking process. which I still have yet to achieve
Click to expand...
Click to collapse
First, unlock your bl. Then root. I done that on my old Arc S and it works great.
Sent from my LT26i using xda developers-app
@ Tread3r:
Yes the drivers are installed correctly, because the phone starts into fastboot and flashboot with each the right light.
Thats the great problem with our devices. I did it nearly the same way and Ive got a similar problem, as the first answers describe in this post. Actual the original stock rom is installed on my Sony and all works correctly, but its just a short-term workaround
The bootloader unlockind process still end in an error message and that is my problem.
@ Vatih:
Nice try, but this is our problem... :/
---------- Post added at 11:41 AM ---------- Previous post was at 10:57 AM ----------
I cant believe it myself, but the alternative way works, althought I cant read anythink in the tool because of the language...
I've got the superuser app and root permissions and all works.
This link helped me: http://forum.xda-developers.com/showthread.php?p=39498268
It's the tool for the "new" firmware, .55, the latest from sony.
Hope, its also succesfully with your devices
I solved our problem. My bootloader is now open
I did it with the unlock, flashtool tool of this forum that helps you to open the bootloader and flash kernels and roms.
http://forum.xda-developers.com/showthread.php?t=2087337
Seems like just the code was wrong.
It worked with the first try
But be careful, although its just the bootloader, all data will be deleted. My phone is empty again :/ Of course I've got some backups...
Hi there, happens to be my first post here. Have installed succesfully Cyanogen Mod succesfully but now my p350 doesnt detect my sim card, dont know exactly why and cant figure it out, I am new to android, would aprreciate any sugestions, thanks there in advance.
Flash Any other stable rom...
and please tell link of the Cynogen Mod ROM which you installed....
theprakhar said:
Flash Any other stable rom...
and please tell link of the Cynogen Mod ROM which you installed....
Click to expand...
Click to collapse
Hi there, thanks for the response.
I have installed this Cynogen Mod ROM: http://forum.xda-developers.com/showthread.php?t=2263963
And also this one: http://forum.xda-developers.com/showthread.php?t=1971158, which has recognized the sim card but still cant use my network.
Been reading a few things and now I feel inclined to try sim unlocking it, but dont know very well which road to take:
# Baseband: I suppose no, that handles radio and gps, no?
# Firmware: I think maybe that can work, but not sure, some info link?
# Editing files like build.prop?
# What about permissions?
Is there a way? Some guy has done it here apparently: http://forum.xda-developers.com/showthread.php?t=1365486, but wasnt kind enough to say how.
Thanks again
Follow this video https://www.youtube.com/watch?v=nRTJ0OG0Hzk&list=UULaB0FBE-vYUKyb8qr35D5A ...it MIGHT work..
It actually worked, I was able to change the firmware more than once, but I was able to chan it to official firwares which actually remains locked, changes only the company of use. Now, I suppose the sim to be locked or not to be will depend of the .kdz file of use. Can recommend one that will do the unlocking? Thanks, you have been very helpful.
juancamisani said:
It actually worked, I was able to change the firmware more than once, but I was able to chan it to official firwares which actually remains locked, changes only the company of use. Now, I suppose the sim to be locked or not to be will depend of the .kdz file of use. Can recommend one that will do the unlocking? Thanks, you have been very helpful.
Click to expand...
Click to collapse
Bro, I think to unlock network ,
ROOT and install a ROM ...It might work ...
Best of luck..:good:
P.S.-if u want funky rom ...check mine http://forum.xda-developers.com/showthread.php?t=2045150 and don't forget to replace the original build.prop with this http://www.mediafire.com/download/91e4ds0x1pc0p19/build.prop[its not for unlocking but for increasing performance]...
theprakhar said:
, I think to unlock network ,
ROOT and install a ROM ...It mighr the work ...
Best of luck..:good:
P.S.-if u want funky rom ...check mine http://forum.xda-developers.com/showthread.php?t=2045150 and don't forget to replace the original build.prop with this http://www.mediafire.com/download/91e4ds0x1pc0p19/build.prop[its not for unlocking but for increasing performance]...
Click to expand...
Click to collapse
Ok, will continue to try some differents roms. Thanks for the links, the roms looks cool. I am just trying to find a certain way to unlock it, maybe there isn't an "unlocked" firmware, maybe itsn't possible. That variant that maybe unlocks it has to have a background. Anyway, the lock code for the IMEI unlock seems to be hackeable somehow, if there is a code to introduce that unlocks it, there is a rainbow table that holds it, no? Will continue trying and update if success. Thanks theprakhar for all the answers, good day gentlemens.
You can now unlock the bootloader with FunkyHuawei for a fee of $55, or 30 Euros with Ministry of Solutions (cheaper but FunkyHuawei is more certain)
As most of you already know, Huawei stopped giving away bootloader unlock codes. So it is up to us, to hack our way to root and custom ROMs.
Following, are a few things we could try,
Also, I own a Nova 3i currently. There are always the possibility that something working for me won't work for you, because of different chipsets, but I guess that this forum is also for the development of Nova 3i.
NOTE THAT SOME OF THE FOLLOWING ARE PAID SERVICES. I'M NOT RELATED WITH ANY OF THEM.
+DC-Unlocker:
I tried the latest version, got an unknown error 375. (This error also goes for the latest versions of P20 Pro, Mate 10, etc.). And the developers said that they won't support any new Huawei phones, and that they'll leave new Huawei phones for HCU-Client, because the two services are related.
+HCU-Client:
You can't try this without buying credits. If you feel generous, go on and try this. They released a couple of new versions in this week.
+Bootloader exploiting:
I really don't know anything about this, feel free to contribute.
+Secret Fastboot backdoors:
There can be a LOT of these, considering that there are a family of commands under <fastboot oem backdoor>. And I discovered quite a lot of secret commands, almost every one of them sounding like that they could seriously brick the device. For example, consider what <fastboot oem djtagtosd> sounds like. (Search Google for JTAG) If you would like to test some of the less-dangerous looking ones, please PM me, even an old Huawei device is okay as long as it has a Kirin chipsets.
Please check this link from P20 Pro Forum - we may have a chance to be supported if many of us do the request. I have done mine. - https://forum.xda-developers.com/hu...ol-tool-one-driversunlocktwrpfactory-t3779080
waltermsalomon said:
Please check this link from P20 Pro Forum - we may have a chance to be supported if many of us do the request. I have done mine. - https://forum.xda-developers.com/hu...ol-tool-one-driversunlocktwrpfactory-t3779080
Click to expand...
Click to collapse
Sorry, did not see this. So, this tool installs TWRP without unlock codes? Still we need to get TWRP compiled.
Huawei nova 3i rom
Dears I need stock firmware and flash tool officially for Huawei Nova 3i ine-lx1
cant EU do anything about this bootloader unlocking situation? I mean, isn't it our right to do whatever we want with our bought device? Im actually not from any EU country btw.
jioleight said:
cant EU do anything about this bootloader unlocking situation? I mean, isn't it our right to do whatever we want with our bought device? Im actually not from any EU country btw.
Click to expand...
Click to collapse
Maybe there is some legislation about that, actually the issue of locked bootloaders runs more than 6/7 years (I think) and they had plenty of time if they wanted to do that... but we can hope, considering things like GDPR.
At least one of things they MUST do is releasing the kernel sources, because by using Android they agree to some license (I don't remember the name) that mandates releasing kernel source..
BTW you can now unlock the bootloader with FunkyHuawei for a fee of $55, or 30 Euros with Ministry of Solutions (they are cheaper, but they look more shady, and I can't help noticing that there website looks just like one of those poorly done scam sites :laugh
Supersonic27543 said:
Maybe there is some legislation about that, actually the issue of locked bootloaders runs more than 6/7 years (I think) and they had plenty of time if they wanted to do that... but we can hope, considering things like GDPR.
At least one of things they MUST do is releasing the kernel sources, because by using Android they agree to some license (I don't remember the name) that mandates releasing kernel source..
BTW you can now unlock the bootloader with FunkyHuawei for a fee of $55, or 30 Euros with Ministry of Solutions (they are cheaper, but they look more shady, and I can't help noticing that there website looks just like one of those poorly done scam sites :laugh
Click to expand...
Click to collapse
mandated but no one is enforcing it so huawei will just delay the relase of the kernel source until the insterest has died out.
nope, not gonna take that risk :laugh:. $55 seems cheaper until it's converted to my country's currency. haha.
Supersonic27543 said:
Maybe there is some legislation about that, actually the issue of locked bootloaders runs more than 6/7 years (I think) and they had plenty of time if they wanted to do that... but we can hope, considering things like GDPR.
At least one of things they MUST do is releasing the kernel sources, because by using Android they agree to some license (I don't remember the name) that mandates releasing kernel source..
BTW you can now unlock the bootloader with FunkyHuawei for a fee of $55, or 30 Euros with Ministry of Solutions (they are cheaper, but they look more shady, and I can't help noticing that there website looks just like one of those poorly done scam sites :laugh
Click to expand...
Click to collapse
Another one source to unlock bootloader - $22
This method has already been tested on 4pda. Working TWRP can be taken from here
And HCU doesn't have NOVA 3 support yet to read the unlock code now
OEM Unlock option
Is it enought to enable "OEM Unlock" in "Developer Options" from the phone settings to unlock the bootloader and I can simply install TWRP afterthat? (the option "OEM Unlock" is not greyed out, and can be easily enabled, at least in the devices that are sold in my country).
Or do I still have to unlock it using unlock key from Huawei Website (or other sources)?
Jan oatcoal said:
Do I still have to unlock it using unlock key from Huawei Website (or other sources)?
Click to expand...
Click to collapse
Yep. It is like this when you issue the command in fastboot to unlock:
Without code and without enabling the toggle: Gives and error telling to turn on the toggle.
With code and without enabling the toggle: Same as above
Without code and toggle enabled: Error wrong password
With both: Success
I think we are lucky on that side, I think that the toggle is also disabled on Mate 20 series. So we can unlock the bootloader. with external sources for now, so it may be a good idea to block OTA updates.
Ine-lx2 8.2.0.131(c636)
*update*
so i checked using fastboot oem get-bootinfo. lo and behold it's really unlocked.
jioleight said:
does Phone Unlocked mean the bootloader or just the GSM part that is unlocked?
Click to expand...
Click to collapse
I did this then installed titanium backup and it said it wasn't rooted.
meekspace said:
I did this then installed titanium backup and it said it wasn't rooted.
Click to expand...
Click to collapse
you have to root first by installing magisk or supersu. and it needs twrp to root. in case of nova 3i there isnt any existing twrp. only on nova 3 since it has the same soc as p20pro.
was about to test it on my nova 3i. good thing i checked the specs of nova 3 first before proceeding.
Unfortunately, cant flash patched ramdisk since fastboot fail. Remote command not allowed. So close yet so far away.
jioleight said:
Unfortunately, cant flash patched ramdisk since fastboot fail. Remote command not allowed. So close yet so far away.
Click to expand...
Click to collapse
Let's try flashing the stock boot.img. If that works, I will patch the boot image to manually disable dm-verity and add Magisk.
Supersonic27543 said:
Let's try flashing the stock boot.img. If that works, I will patch the boot image to manually disable dm-verity and add Magisk.
Click to expand...
Click to collapse
"fastboot flash ramdisk patched_boot.img". That's what entered in cmd. Also after magisk patched the ramdisk the patched ramdisk is only 5mb. The original was around 25mb.
What should be patched anyway? I patched ramdisk.img via magisk ang since the partitioning is different with phones released with oreo. What is your method?
*update*
well, this sux. based on what i have read on other huawei device flashing via fastboot is not always the best way. the phone may display that the bootloader is unlock but it wont still allow any modifications. why cant this be straight forward like samsung/oneplus. this is frustrating.
jioleight said:
"fastboot flash ramdisk patched_boot.img". That's what entered in cmd. Also after magisk patched the ramdisk the patched ramdisk is only 5mb. The original was around 25mb.
What should be patched anyway? I patched ramdisk.img via magisk ang since the partitioning is different with phones released with oreo. What is your method?
*update*
well, this sux. based on what i have read on other huawei device flashing via fastboot is not always the best way. the phone may display that the bootloader is unlock but it wont still allow any modifications. why cant this be straight forward like samsung/oneplus. this is frustrating.
Click to expand...
Click to collapse
What if we try obtaining a code by one of the third party methods and try that? Maybe they just forgot or didn't care to set the variables you saw there as this is a new chipset. I think it is not really unlocked, if it was the phone will display the "Your device has been unlocked and cannot be trusted" message on boot.
Looks like what I said before is true. fastboot oem lock-state info returns USER Locked.
Has anyone tried this?
https://www.techdroidtips.com/unloc...i/#How_to_Unlock_Bootloader_on_Huawei_Nova_3i
stevefwt said:
Has anyone tried this?
https://www.techdroidtips.com/unloc...i/#How_to_Unlock_Bootloader_on_Huawei_Nova_3i
Click to expand...
Click to collapse
They are just copy pastes and no longer works as of Huawei stopping providing codes.
Google should try to remove them from coming at top of Google searches, IDK.
I can't seem to find a consistent guide on this. Any help to to get me rooted and using an unlocked bootloader is greatly appreciated. If anyone knows a great, recent guide or knows how to do this, please link it.
Blaze Uchiha said:
I can't seem to find a consistent guide on this. Any help to to get me rooted and using an unlocked bootloader is greatly appreciated. If anyone knows a great, recent guide or knows how to do this, please link it.
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-j2/help/j2-core-sm-j260g-help-t3921806
2nd comment which is my comment. It should work.
Unlocking bootloader for Samsung device seems to be only turn on OEM unlocking
Prove N. said:
https://forum.xda-developers.com/galaxy-j2/help/j2-core-sm-j260g-help-t3921806
2nd comment which is my comment. It should work.
Unlocking bootloader for Samsung device seems to be only turn on OEM unlocking
Click to expand...
Click to collapse
There's no OEM unlocking option in my developer's options. I thought it was weird but this phone is brand new as I just got it today
Blaze Uchiha said:
There's no OEM unlocking option in my developer's options. I thought it was weird but this phone is brand new as I just got it today
Click to expand...
Click to collapse
So its your carrier's problem then. TMobile to be exact. Are you on a contract or anything? Can you issue an unlock request if no contract?
(I dont know much how US-locked phone works~)
So I've got mine unlocked, almost absolutely 0 information on the product. Researched about 3 hrs now and still only got the info obtained from devcheck. Will provide anything required. Looking to root magisk, wanna try out lineage. I'll be a tester, i am a noob.
Model- sm-j260t1
Device- j2corepltemtr
2019
Build-M1ajq.j260t1uvu1asa3
Made 1-10-2019
8.1.0 os
build-13.18.14-15262773
If instructed how to back up I'd be happy to share kernel/firmware.
Tia
Snip
Snippititgood said:
So I've got mine unlocked, almost absolutely 0 information on the product. Researched about 3 hrs now and still only got the info obtained from devcheck. Will provide anything required. Looking to root magisk, wanna try out lineage. I'll be a tester, i am a noob.
Model- sm-j260t1
Device- j2corepltemtr
2019
Build-M1ajq.j260t1uvu1asa3
Made 1-10-2019
8.1.0 os
build-13.18.14-15262773
If instructed how to back up I'd be happy to share kernel/firmware.
Tia
Snip
Click to expand...
Click to collapse
Help me man lol
Sent from my SM-J260T1 using XDA Labs
Snippititgood said:
So I've got mine unlocked, almost absolutely 0 information on the product. Researched about 3 hrs now and still only got the info obtained from devcheck. Will provide anything required. Looking to root magisk, wanna try out lineage. I'll be a tester, i am a noob.
Model- sm-j260t1
Device- j2corepltemtr
2019
Build-M1ajq.j260t1uvu1asa3
Made 1-10-2019
8.1.0 os
build-13.18.14-15262773
If instructed how to back up I'd be happy to share kernel/firmware.
Tia
Snip
Click to expand...
Click to collapse
Yes did anything ever come of this? Also when you unlock it, does it you to root it?
So is there a way to get the OEM option to appear in the dev options or a way to install a bootloader without OEM?
I'm having the same exact problem with my phone. Same model and everything and I also do not have the unlocking option In my dev options. I've tried every exploit known to me and have no luck. I tried flashing TWRP theough Odin without the OEM unlocking and I get a fail because of a secure check fail which I'm not sure is related to the bootloader not being unlocked or something else. I'd love to get an answer to this so I can get lineageos on here
Has anyone found anything yet on how to unlock or enable OEM unlocking
As I understand it the OEM unlock setting is only available after owning the device for 160 days.
Samsung Galaxy J2 (Metro PCS) [SM-J260T1]
Sircrysalotz said:
Has anyone found anything yet on how to unlock or enable OEM unlocking
Click to expand...
Click to collapse
Firmware info of Samsung Galaxy J2 (Metro PCS) [SM-J260T1]
Android version - 8.1.0 (Oreo)
Build # M1AJQ.J260T1UVS6ATG2
There is no OEM unlock option in the dev options for this phone.
The most I could do is to get in to go into download mode, no bootloader came up.
I Used ADB Command: adb reboot bootloader
Another PC app I seen on xda forums is called "ADBAppControl".
There is an option reboot your phone with adb built in to do it too.
---------- Post added at 05:45 AM ---------- Previous post was at 05:17 AM ----------
Blaze Uchiha said:
So is there a way to get the OEM option to appear in the dev options or a way to install a bootloader without OEM?
Click to expand...
Click to collapse
My J2 is new and No at this Point, One Reply in here said after 160 days of owning it the option opens up, so I will have wait for the 160 days are up to check again.
Update, it been Over 160 Days and still do not see anything in the dev options. I bought the phone 4-12-2020. So i guess it lockout code that releases the option i suppose. or it just not available with this phone.
Was thinking of flashing my old stock 4.1 on it. cause 4.1 i had no trouble rooting it.
Yes,I'm new to the forum. I also have the same model phone unlocked from the carrier(Metro PCS). I've tried several ways to root this device but I don't have access to a PC I also get the security error code to pop up when I tried to install custom OS. I can't seem to get the recovery backup or to actually Flash the proper image to the bootloader I've also tried kingroot, kingoroot, l root, and some other one click root options. My understanding of using team Win Recovery Project without PC is limited I'm also trying to use magisk with it.In A novice in understanding...Does anyone have any advice..
Better find a friend with a computer to help you . Apps are crappier than Microsoft.