Related
Good Afternoon,
I want to install cyanogenmod 10.1 on my xperia arc S. tried to follow a tutorial, but when it came to the part of booting the device in recovery mode I found that my bootloader was locked. Apparently, on the Rooting Status it says: bootloader unlock allowed: NO. So, my question is, what should I do in order to unlock the bootloader and install the cyanogenmod. thank you vm for your time.
Bernardo.
BernardoCalhanas said:
Good Afternoon,
I want to install cyanogenmod 10.1 on my xperia arc S. tried to follow a tutorial, but when it came to the part of booting the device in recovery mode I found that my bootloader was locked. Apparently, on the Rooting Status it says: bootloader unlock allowed: NO. So, my question is, what should I do in order to unlock the bootloader and install the cyanogenmod. thank you vm for your time.
Bernardo.
Click to expand...
Click to collapse
Try this http://forum.xda-developers.com/showthread.php?t=1034087
izida said:
Try this http://forum.xda-developers.com/showthread.php?t=1034087
Click to expand...
Click to collapse
I'm having problems downloading the -32/64bit drivers
izida said:
Try this http://forum.xda-developers.com/showthread.php?t=1034087
Click to expand...
Click to collapse
http://www.theandroidsoul.com/how-to-unlock-bootloader-xperia-arc-play-neo-pro/
found this, but cannot get into fastboot
I'm pretty sure that if you are not allowed to unlock it, there is no way to unlock it.
Edit: Ok maybe i was wrong. Take a look at this Thread -> http://forum.xda-developers.com/showthread.php?t=2102783
Edit2: Found a guide...but looks like you have to pay to unlock it. http://forum.xda-developers.com/showthread.php?t=1896553
Keksdroid said:
I'm pretty sure that if you are not allowed to unlock it, there is no way to unlock it.
Edit: Ok maybe i was wrong. Take a look at this Thread -> http://forum.xda-developers.com/showthread.php?t=2102783
Edit2: Found a guide...but looks like you have to pay to unlock it. http://forum.xda-developers.com/showthread.php?t=1896553
Click to expand...
Click to collapse
then there is no free way of doing this?
Cant Unlock Bootloader
Dear Sir
i Have Done all Instructions But It shows failed pls find below details.. please hellp me as soon as possible
Dear syed h done all what you mentioned but it shows error.. please find bellow.. and please reply me as soon as possible...
Microsoft Windows XP [Version 5.1.2600]
C:\Documents and Settings\ssubramanian>cd desktop
C:\Documents and Settings\ssubramanian\Desktop>cd flash boot
C:\Documents and Settings\ssubramanian\Desktop\flash boot>cd fast boot
C:\Documents and Settings\ssubramanian\Desktop\flash boot\fast boot>cd fastboot
C:\Documents and Settings\ssubramanian\Desktop\flash boot\fast boot\fastboot>fas
tboot.exe -i 0x0fce getvar version
version: 0.3
finished. total time: -0.000s
C:\Documents and Settings\ssubramanian\Desktop\flash boot\fast boot\fastboot>fas
tboot.exe -i 0x0fce oem unlock 0xDDA4329E6C449072
(bootloader) Unlock phone requested
FAILED (remote: oem unlock failed!)
finished. total time: 0.016s
Check if you wrote the code correctly.
I too have a Sony Ericsson (pro) with bootloader unlock allowed: NO. I've scoured the Web and only come up with this site http://www.wotanserver.com/en/sony-ericsson/xperia-pro-mk16/unlock-tool/debranding-flash
Which claims that if I pay 7.99 euros I'll be able to unlock my bootloader. My question is what am I paying 7.99 for? What does this service give that can't be found out for free?
engmex said:
I too have a Sony Ericsson (pro) with bootloader unlock allowed: NO. I've scoured the Web and only come up with this site http://www.wotanserver.com/en/sony-ericsson/xperia-pro-mk16/unlock-tool/debranding-flash
Which claims that if I pay 7.99 euros I'll be able to unlock my bootloader. My question is what am I paying 7.99 for? What does this service give that I can't be found out for free?
Click to expand...
Click to collapse
It works only if your phone is manufactured before 12W11. Check it under the battery.
your phone it is simlock ? you ned unlocked the be able to unlock the bootloader
http://forum.xda-developers.com/show....php?t=2102783
I am having problems in unlocking my xperia arc s lt18i boot loader. I have tried every sungle method of unlocking bootloader. my phone shows Boot loader allowed: yes and it is not sim locked as well. I am using the correct IMEI code and I have got correct unlock code from sony and still I am getting error remote: oem unlock failed. Help!! Help!! Help!! Please!!!
shehrozlt18i said:
I am having problems in unlocking my xperia arc s lt18i boot loader. I have tried every sungle method of unlocking bootloader. my phone shows Boot loader allowed: yes and it is not sim locked as well. I am using the correct IMEI code and I have got correct unlock code from sony and still I am getting error remote: oem unlock failed. Help!! Help!! Help!! Please!!!
Click to expand...
Click to collapse
okay this problem have many other of my friends. in 99.9 % i requested a new code from sony website & it all worked :good:
also check in the cmd window if the divice is connected before trying to unlock!
bejunk said:
okay this problem have many other of my friends. in 99.9 % i requested a new code from sony website & it all worked :good:
also check in the cmd window if the divice is connected before trying to unlock!
Click to expand...
Click to collapse
Actually I have tried every single thing and everytime I ask for a new code I get the same code as before from sony and I have installed proper drivers as well because it states that my device is connected
shehrozlt18i said:
Actually I have tried every single thing and everytime I ask for a new code I get the same code as before from sony and I have installed proper drivers as well because it states that my device is connected
Click to expand...
Click to collapse
i dont be rude bro, but i had this situatzion atleast over 20 times here with friends or others from my country (then i done the job over teamviewer lol, what a pain in ass)
theres a simple calcultion which allways was right for me:
- service menu says: bootloader unlocked allowed: YES [x] (check:good
- installed all the drivers & stuff properly
(you say that cmd tells you device is connetced, so [x](check:good
if its then still not working, ITS 100%:
a human (your) fault.
- maybe request wrong code (99%)
- ???
i say that because i have friends which telled me same thing. they said "i read it thrice & requested code more than 5 times...... bla bla" - & those a were mostly smart people. (no n00bs)
guess what, after triyng help them for hours (!) over internet, i go to them next day & unlocked phone in 5 mins. lol
i dont know what they doing wrong. or why its not working. i only know if you do it carefully,patiently, read all & DO IT EXACTLY like stated it allways works. because its my way & it allways worked (even they say they done it same.)
but keep in mind that maybe your carrier locked it in some way. here in my country its not allowed for carriers. but idk how its in yr country
BernardoCalhanas said:
then there is no free way of doing this?
Click to expand...
Click to collapse
I know not
As of March 2015 is there any free way to unlock the bootloader if it is not allowed?
arpcpro said:
As of March 2015 is there any free way to unlock the bootloader if it is not allowed?
Click to expand...
Click to collapse
no. sorry
BernardoCalhanas said:
then there is no free way of doing this?
Click to expand...
Click to collapse
I really hope you found a way to unlock your bootloader. If not, go on this site, just provide your email, confirm email, type your emai number and they give you the code instantly: https://developer.sonymobile.com/unlockbootloader/
I did worked for my xperia arc. Good luck
---------- Post added at 09:45 ---------- Previous post was at 09:30 ----------
arpcpro said:
As of March 2015 is there any free way to unlock the bootloader if it is not allowed?
Click to expand...
Click to collapse
I really hope you found a way to unlock your bootloader. If not, go on this site, just provide your email, confirm email, type your emai number and they give you the code instantly: https://developer.sonymobile.com/unlockbootloader/
I did worked for my xperia arc. Good luck
EDIT: Resolved: While the OS had said it was up-to-date when I originally checked. It was not. After a bit of time it alerted me that an update was available. After updating the OS the OEM Unlocking option was no longer disabled.
I purchased a Pixel XL specifically from Google Store because I wanted to receive either an bootloader unlocked or bootloader unlockable phone without resorting to any hacks that may not work in the future. It just arrived and I enabled Developer Options and enabled USB Debugging. However, the OEM Unlocking option is off and disabled (greyed).
I booted into the bootloader, it shows as locked. If I try to unlock it I get:
>fastboot flashing unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.051s
If I try to flash it with the temporary TWRP boot up image:
>fastboot boot <path-to>\twrp-3.0.2-0-alpha2-fastboot-marlin.img"
downloading 'boot.img'...
OKAY [ 0.874s]
booting...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.975s
I'd appreciate any suggestions for proceeding. Thank you.
Gregyski said:
(Since this isn't specifically about alternate firmware, I believe this is the correct forum and not the dev forum.)
I purchased a Pixel XL specifically from Google Store because I wanted to receive either an bootloader unlocked or bootloader unlockable phone without resorting to any hacks that may not work in the future. It just arrived and I enabled Developer Options and enabled USB Debugging. However, the OEM Unlocking option is off and disabled (greyed).
I booted into the bootloader, it shows as locked. If I try to unlock it I get:
>fastboot flashing unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.051s
If I try to flash it with the temporary TWRP boot up image:
>fastboot boot <path-to>\twrp-3.0.2-0-alpha2-fastboot-marlin.img"
downloading 'boot.img'...
OKAY [ 0.874s]
booting...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.975s
I'd appreciate any suggestions for proceeding. Thank you.
Click to expand...
Click to collapse
The command should be fastboot oem unlock
ilatimer1 said:
The command should be fastboot oem unlock
Click to expand...
Click to collapse
Unfortunately, that is also disallowed:
>fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.046s
Gregyski said:
Unfortunately, that is also disallowed:
>fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.046s
Click to expand...
Click to collapse
Did you go into Developer options is Settings and enable OEM unlocking first? If you don't have Developer Options in settings go to Settings/About Phone and then tap Build Number a bunch of times to enable it.
ilatimer1 said:
Did you go into Developer options is Settings and enable OEM unlocking first? If you don't have Developer Options in settings go to Settings/About Phone and then tap Build Number a bunch of times to enable it.
Click to expand...
Click to collapse
Thanks for your help ilatimer1, but I have resolved it now. I had edited the original post to indicate this but probably should have followed up at the end for your sake. I was just trying to avoid bumping it. At the time I asked the question, I mentioned that that option was disabled.
When I originally setup the phone I didn't enter WiFi data since I knew a factory reset would occur when I unlocked the bootloader. However, as a result of this, I didn't get alerted to the presence of an OS update. Ultimately, I setup WiFi and discovered the availability of an update. I proceeded to update and the OEM Unlocking feature then became enabled. Thanks again.
I unwapped and went stright to fastboot. didn't know update needed. thanks
Same issue unresolved
When I go into developer options OEM unlocking is still greyed out even after I downloaded the software update. Any leads on what to do?
[email protected] said:
When I go into developer options OEM unlocking is still greyed out even after I downloaded the software update. Any leads on what to do?
Click to expand...
Click to collapse
Where did you buy your Pixel?
Mr. Orange 645 said:
Where did you buy your Pixel?
Click to expand...
Click to collapse
verizon store
[email protected] said:
verizon store
Click to expand...
Click to collapse
The Pixels purchased from Verizon do not have unlockable bootloaders, so the switch will stay greyed out. If it is still on 7.0, you can use dPixel8 to bypass and unlock the bootloader. If you updated to 7.1.1, you are stuck with a locked bootloader.
Mr. Orange 645 said:
The Pixels purchased from Verizon do not have unlockable bootloaders, so the switch will stay greyed out. If it is still on 7.0, you can use dPixel8 to bypass and unlock the bootloader. If you updated to 7.1.1, you are stuck with a locked bootloader.
Click to expand...
Click to collapse
so there is no solution if Ive already updated to 7.1.1?
any chance a solution will open up in the future?
No there no solution right now. I wouldn't say there's absolutely no chance of finding another exploit, this is XDA after all, but I wouldn't count on it.
Mr. Orange 645 said:
No there no solution right now. I wouldn't say there's absolutely no chance of finding another exploit, this is XDA after all, but I wouldn't count on it.
Click to expand...
Click to collapse
so this toolkit isnt gonna work: http://www.wugfresh.com/nrt/
?
[email protected] said:
so this toolkit isnt gonna work: http://www.wugfresh.com/nrt/
?
Click to expand...
Click to collapse
No. That's for Nexus devices not Pixels anyway.
Mine is in off position but once selected, it asks for pin. Bought through google and on at&t. Only thing I can think of is that I put sim that was still on contract from my Nexus 6. Maybe contact at&t?
integraGSR said:
Mine is in off position but once selected, it asks for pin. Bought through google and on at&t. Only thing I can think of is that I put sim that was still on contract from my Nexus 6. Maybe contact at&t?
Click to expand...
Click to collapse
Im on Verizon
integraGSR said:
Mine is in off position but once selected, it asks for pin. Bought through google and on at&t. Only thing I can think of is that I put sim that was still on contract from my Nexus 6. Maybe contact at&t?
Click to expand...
Click to collapse
The Allow OEM Unlocking switch asks for a PIN? Do you have a PIN set up for the lockscreen? I'm guessing that's what it's asking for. Your contract status with ATT has nothing to do with the bootloader status. If you think so, just try it without your SIM card in it.
Mr. Orange 645 said:
The Allow OEM Unlocking switch asks for a PIN? Do you have a PIN set up for the lockscreen? I'm guessing that's what it's asking for. Your contract status with ATT has nothing to do with the bootloader status. If you think so, just try it without your SIM card in it.
Click to expand...
Click to collapse
LoL that was it. Sometimes it's back to the basics, think outside the box. Didn't think about lockscreen pin as I use fingerprint scanner all the time. Thanks.
integraGSR said:
LoL that was it. Sometimes it's back to the basics, think outside the box. Didn't think about lockscreen pin as I use fingerprint scanner all the time. Thanks.
Click to expand...
Click to collapse
LOL! Glad I could help!
Mr. Orange 645 said:
The Pixels purchased from Verizon do not have unlockable bootloaders, so the switch will stay greyed out. If it is still on 7.0, you can use dPixel8 to bypass and unlock the bootloader. If you updated to 7.1.1, you are stuck with a locked bootloader.
Click to expand...
Click to collapse
But pixels purchased at Google store with 7.1.1 are still unlockable correct?
Sent from my Pixel XL using Tapatalk
Hi guys need some help right now.
OnePlus 5T. Had it rooted and SuperSu installed. Ended up deciding not to have it rooted so used the Full Clean SuperSu unroot. This was successfuly, and after a few days Iwanted to lock the bootloader as well, so went into fastboot and used the fastboot oem lock.
After that, I ended up getting a loop of:
"Your device is corrupt. it can't be trusted and will not boot. Visit this link on another device"
From research, I can see that flashing would be the best option. However, trying to flash through fastboot results in an error:
"OKAY [ 0.442s]
writing 'boot'...
FAILED (remote: Flashing is not allowed in Lock State)"
Any suggestions please?
Are you able to fastboot unlock it again?
rickysidhu_ said:
Are you able to fastboot unlock it again?
Click to expand...
Click to collapse
no, it doesnt allow it through fastboot. I assume it is because when it locked the bootloader, it refreshed the OEM Unlock option from developer options.
Did you see this thread?
[GUIDE] Restore to complete stock and relock bootloader. Easiest step by step guide.
The order is very important. You must restore to complete stock before re-locking the bootloader. That includes recovery. When this is all over, google "what is bootloader?" to see what it does.
Also, questions do not belong in the How-To section. Another moderator will be along shortly to move it into the Help/Q&A section.
yousufx said:
Hi guys need some help right now.
OnePlus 5T. Had it rooted and SuperSu installed. Ended up deciding not to have it rooted so used the Full Clean SuperSu unroot. This was successfuly, and after a few days Iwanted to lock the bootloader as well, so went into fastboot and used the fastboot oem lock.
After that, I ended up getting a loop of:
"Your device is corrupt. it can't be trusted and will not boot. Visit this link on another device"
From research, I can see that flashing would be the best option. However, trying to flash through fastboot results in an error:
"OKAY [ 0.442s]
writing 'boot'...
FAILED (remote: Flashing is not allowed in Lock State)"
Any suggestions please?
Click to expand...
Click to collapse
Call oneplus and have them fix ya
yes, call oneplus.
I have had the same problem and they solved it via remote connection.
Or read here: https://forum.xda-developers.com/oneplus-5t/help/please-help-hardbricked-oneplus-5t-t3716057
Is it too soon to start a bounty for a bootloader unlock? Do we even have any devs using this device(Lm-G710TM)? Im good for $100+.
It's not soon for USA unlocked (G710ULM) because 11th July was the release, till now why there's no bootloader for this unlocked variant! Already European variant enjoying root.
I usually give it like two months before I expect activity to pick up for new phones; even when owning Nexus phones. But, it's very discouraging to see how dead this place is, especially for any US variants. If there's no encouraging development for this phone by the time the Pixel 3 drops, I might just ditch this phone for that instead. This is a solid phone, but it could be absolutely great with a custom ROM/kernel.
totally agree, this is a great and solid phone. Could use a few tweaks and it'll be even better!
Alcolawl said:
I usually give it like two months before I expect activity to pick up for new phones; even when owning Nexus phones. But, it's very discouraging to see how dead this place is, especially for any US variants. If there's no encouraging development for this phone by the time the Pixel 3 drops, I might just ditch this phone for that instead. This is a solid phone, but it could be absolutely great with a custom ROM/kernel.
Click to expand...
Click to collapse
Now that I took care of the H932 V30 getting root, it is time to move on to you guys....
So, since I don't own this phone, I need some details if you guys would like me to help you get it rooted.
1 - Did T-Mobile pull fastboot oem unlock, or can you still at least unlock your bootloader?
2 - If they did pull the ability, how do other G7s unlock their bootloader?
3 - Can someone provide me with a dump of laf? Maybe there is a KDZ around here that I missed, but it is early, and I am not going searching just yet.
-- Brian
runningnak3d said:
Now that I took care of the H932 V30 getting root, it is time to move on to you guys....
So, since I don't own this phone, I need some details if you guys would like me to help you get it rooted.
1 - Did T-Mobile pull fastboot oem unlock, or can you still at least unlock your bootloader?
2 - If they did pull the ability, how do other G7s unlock their bootloader?
3 - Can someone provide me with a dump of laf? Maybe there is a KDZ around here that I missed, but it is early, and I am not going searching just yet.
-- Brian
Click to expand...
Click to collapse
I know VZW it's all locked The OEM switch is missing also. I'm assuming for at least Verizon there needs to be an exploit if ever found.
For now, I am just talking about the TMO version.
-- Brian
runningnak3d said:
Now that I took care of the H932 V30 getting root, it is time to move on to you guys....
So, since I don't own this phone, I need some details if you guys would like me to help you get it rooted.
1 - Did T-Mobile pull fastboot oem unlock, or can you still at least unlock your bootloader?
2 - If they did pull the ability, how do other G7s unlock their bootloader?
3 - Can someone provide me with a dump of laf? Maybe there is a KDZ around here that I missed, but it is early, and I am not going searching just yet.
-- Brian
Click to expand...
Click to collapse
https://forum.xda-developers.com/lg-g7-thinq/help/t-mobile-oem-unlock-t3833156
runningnak3d said:
For now, I am just talking about the TMO version.
-- Brian
Click to expand...
Click to collapse
Welcome aboard mate, been looking for your presence here but was doubting it as you don't have this device as of yet. I'm happy to see you and say that I was wrong, can't thank you enough for the work you have done on other devices.
Will be more than willing to help anyway I can, although I am currently on the sprint variant for the moment.
Hey @ps3hacker3 Long time no speak
Yea, I have learned enough that it is getting a lot easier even if I don't have the phone. However, I am going to need some info from people that DO have the G710TM.
-- Brian
runningnak3d said:
Hey @ps3hacker3 Long time no speak
Yea, I have learned enough that it is getting a lot easier even if I don't have the phone. However, I am going to need some info from people that DO have the G710TM.
-- Brian
Click to expand...
Click to collapse
LG G710ULM owner here. I know it's not specifically a T-Mobile version but it does allow OEM unlocking by default. I could be wrong, but I'm guessing the differences between the G710TM and G710ULM aren't that big (if any at all). If you need any info from my end, let me know. I'd love to get the ball rolling on bootloader unlocks for this phone. Lots of untapped potential here.
So you have the slider in developer options for "Allow OEM Unlocking" .. do you have fastboot oem unlock?
-- Brian
runningnak3d said:
So you have the slider in developer options for "Allow OEM Unlocking" .. do you have fastboot oem unlock?
-- Brian
Click to expand...
Click to collapse
Upon rebooting into Bootloader I'm presented with a quick guide for unlocking the phone:
1) Read Device ID
:fastboot oem device-id
2) Write Unlock Key
:fastboot flash unlock unlock.bin
3)Check bootloader is unlocked
:fastboot getvar unlocked
fastboot oem unlock results in a FAILED (remote: 'unknown command') message. Screenshot attached. My first attempt didn't work because I guess I didn't have the right bootloader drivers installed.
So it looks like even the unlocked models are in the same boat as everyone else, except Europe.
runningnak3d said:
So you have the slider in developer options for "Allow OEM Unlocking" .. do you have fastboot oem unlock?
-- Brian
Click to expand...
Click to collapse
The T-Mobile version has the oem unlock slider.
Edit: if I run the fastboot oem unlock command, nothing happens. The phone when using reboot bootloader, gives me 3 options. Get ID, check unlock, I forget the wording on the other, but it's basically to input your unlock file I think.
20degrees said:
The T-Mobile version has the oem unlock slider.
Edit: if I run the fastboot oem unlock command, nothing happens. The phone when using reboot bootloader, gives me 3 options. Get ID, check unlock, I forget the wording on the other, but it's basically to input your unlock file I think.
Click to expand...
Click to collapse
On my Windows 10 machine, when this phone is in Bootloader and plugged in via USB, Device Manager showed it as just "Android" with a warning symbol next to it. Had to grab the latest Google ADB and Fastboot drivers and force install the drivers (Choose from list, Have Disk..., Android Bootloader Interface, etc.) in order for the computer to actually recognize the phone properly when in the Bootloader. Otherwise issuing Fastboot commands just resulted in <waiting for any device> or whatever. Strange, because I haven't touched this OS install in probably a year and I had no problems issuing commands to my Pixel XL in Bootloader this spring.
Anyways, looks like until LG decides they want to support unlocking other variants, we're dead in the water.
Alcolawl said:
On my Windows 10 machine, when this phone is in Bootloader and plugged in via USB, Device Manager showed it as just "Android" with a warning symbol next to it. Had to grab the latest Google ADB and Fastboot drivers and force install the drivers (Choose from list, Have Disk..., Android Bootloader Interface, etc.) in order for the computer to actually recognize the phone properly when in the Bootloader. Otherwise issuing Fastboot commands just resulted in <waiting for any device> or whatever. Strange, because I haven't touched this OS install in probably a year and I had no problems issuing commands to my Pixel XL in Bootloader this spring.
Anyways, looks like until LG decides they want to support unlocking other variants, we're dead in the water.
Click to expand...
Click to collapse
Be forewarned, I've noticed that fastboot doesn't always work, despite latest drivers. As of late, the Pixel has been known to hang on these same commands at times as well. My Moto Z2 Force suffers from this error as well.
---------- Post added at 04:11 AM ---------- Previous post was at 04:04 AM ----------
runningnak3d said:
Now that I took care of the H932 V30 getting root, it is time to move on to you guys....
So, since I don't own this phone, I need some details if you guys would like me to help you get it rooted.
1 - Did T-Mobile pull fastboot oem unlock, or can you still at least unlock your bootloader?
2 - If they did pull the ability, how do other G7s unlock their bootloader?
3 - Can someone provide me with a dump of laf? Maybe there is a KDZ around here that I missed, but it is early, and I am not going searching just yet.
-- Brian
Click to expand...
Click to collapse
I hope you know many are INCREDIBLY excited to have you on board! I'm not advanced, but once I receive my computer back, I'll definitely be available to help with providing info and helping test, as I have a TMO variant (I may or may not work for TMO as well, so yeah... )
runningnak3d said:
So you have the slider in developer options for "Allow OEM Unlocking" .. do you have fastboot oem unlock?
-- Brian
Click to expand...
Click to collapse
Own a TMobile variant, oem unlocking option is there, fastboot commands do not work (or are extremely limited)
getprop | grep unlock (if it means anything)
[Ro.oem_unlock_supported]: [1]
[Sys.oem_unlock_allowed]: [1]
I know I probably didn't help out much, if you have any other questions feel free to ask I'll help out as much as I can. thank you for contributions and congrats on the V30 root.
runningnak3d said:
Now that I took care of the H932 V30 getting root, it is time to move on to you guys....
So, since I don't own this phone, I need some details if you guys would like me to help you get it rooted.
1 - Did T-Mobile pull fastboot oem unlock, or can you still at least unlock your bootloader?
2 - If they did pull the ability, how do other G7s unlock their bootloader?
3 - Can someone provide me with a dump of laf? Maybe there is a KDZ around here that I missed, but it is early, and I am not going searching just yet.
-- Brian
Click to expand...
Click to collapse
I have the tmobile variant. Let me know what you might need.
Unlock Slider is present in developer settings and is not greyed out. Unlock command just hangs.
runningnak3d said:
So you have the slider in developer options for "Allow OEM Unlocking" .. do you have fastboot oem unlock?
-- Brian
Click to expand...
Click to collapse
Sprint variant also has "Allow OEM unlocking" available and it is changeable
So you can issue fastboot flashing unlock_critical but not fastboot flashing unlock -- that is just weird.
If you issue the unlock_critical, do you get the warning that your phone is possibly corrupt, but will continue to boot?
-- Brian
I bought a xiomi redmi note 5 ai which contains a fake rom( 9.5.13.0.0 OEIMIFA). In developers option it shows me that my device is unlocked but in fastboot it is actually locked. I tried to unlock it but couldn't get succeed. I also tried xiaomitool, xiaomi flash, some adb and edl proccess but couldn't get any success. In forum I saw test point twice method for whyred but I couldn't active edl by doing this hardware functionality because my device is new and I am also a noob in those matter. My mi id also unauthorised. Is there any chance that I can flash Official China stable rom and get the official update??? I am so disappointed with this. Experts, please help me to flash official rom on note 5 ai. give e some solutions.
Yeah I wanna know about this topic too. Many sellers are sending unsealed products and bootloader saying unlocked.
I'm in this situation too! So sad
This is really weird....In dev options phone says "Unlocked" but when you reboot there is no "Unlocked" sign under Mi logo...WTF?????
You will need to give some more detailed information for people to help you. Go on the guides section, find one of the many bootloader unlock guides and follow it step by step: at which point does it not work, and what kind of error do you get?
You also mention your account not being authorized: if that is the case, then you absolutely need to get it authorized first, there's no way around that (short of finding someone with an authorized account to help you, I guess).
By the way, I would not focus too much on the fact that Developer options report the device as unlocked, if the ROM is unofficial, that is easy to fake. Whoever flashed the u unauthorized ROM must have then relocked the bootloader after flash.
this is why xiaomi has changed the way bootloader unlocks to prevent sellers from doing this.
raptorddd said:
this is why xiaomi has changed the way bootloader unlocks to prevent sellers from doing this.
Click to expand...
Click to collapse
To my knowledge, the new unlock policy just adds more time before unlock and makes it harder to use the same account for multiple unlocks. I would say it discourages sellers from doing this, but the more resourceful ones will keep doing what they always did, while us users have to endure the whole thing.
I got my redmi note 5 ai, it was already unlocked. can someone point out if it's good? In developer options says unlocked. I turned on usb debugging but OEM unlock is greyed out. Verity mode: true, device unlocked: true and device critical unlocked: true
My first R5+ came with an unlocked bootloader but the unlock process made it for the seller can corrupt eventually some partition or even unsuccesfull, they are not intend to unlock but change a chinese rom for a global and through the process device could get unlocked (time before, I guess not actually).
The most indisputable way without a doubt to know this is simply going to fastboot mode and typing
Code:
fastboot oem device-info
so fastboot reads at a low level directly in the right partition. There are some discussion on where is place this condition, some thinks that is in bootloader itself but others believe that it is in persist partition.
That's what I did. What do you think?
https://imgur.com/a/JO4lNy7
Remig83 said:
That's what I did. What do you think?
https://imgur.com/a/JO4lNy7
Click to expand...
Click to collapse
It's unlocked
SubwayChamp said:
It's unlocked
Click to expand...
Click to collapse
Thanks for the confirm. Still can't figure out how to turn on OEM unlock. Maybe cause I haven't done a mi account yet.
Remig83 said:
Thanks for the confirm. Still can't figure out how to turn on OEM unlock. Maybe cause I haven't done a mi account yet.
Click to expand...
Click to collapse
You mean unlock OEM in developer options? turn off USB debugging and then turn on again and now enable OEM unlock
SubwayChamp said:
You mean unlock OEM in developer options? turn off USB debugging and then turn on again and now enable OEM unlock
Click to expand...
Click to collapse
Yes that's what I meant. Done what you said, still didn't turn on.
Remig83 said:
Yes that's what I meant. Done what you said, still didn't turn on.
Click to expand...
Click to collapse
If it is in a greyish, as unmarked so you can touch the toggle but is in positive OEM unlock? then don´t worry about that.
Just look at it before and after to do some update.
SubwayChamp said:
If it is in a greyish, as unmarked so you can touch the toggle but is in positive OEM unlock? then don´t worry about that.
Just look at it before and after to do some update.
Click to expand...
Click to collapse
It is greyish yes, on negative as in off. I will try and make a mi account, see if it helps.