I can't root my Oneplus 2 A2001 - OnePlus 2 General

Who can help me, I can not unlock my OnePlus 2 A2001. ADB is installed, they see my phone, but if I want to unlock, nothing happens. I do not know how to continue. I use Windows 10
Regards,
Harry

hrvw said:
Who can help me, I can not unlock my OnePlus 2 A2001. ADB is installed, they see my phone, but if I want to unlock, nothing happens. I do not know how to continue. I use Windows 10
Regards,
Harry
Click to expand...
Click to collapse
Did you enable developer settings and enable the option to unlock bootloader?
Sent from my ONE A2005 using XDA-Developers mobile app

hrvw said:
Who can help me, I can not unlock my OnePlus 2 A2001. ADB is installed, they see my phone, but if I want to unlock, nothing happens. I do not know how to continue. I use Windows 10
Regards,
Harry
Click to expand...
Click to collapse
Follow this guide, It will work https://forums.oneplus.net/threads/...wrp-root-nandroid-efs-backup-and-more.345478/

Hello again,
I have followed these steps but it did not work. When I started my OnePlus 2 in bootloder and then you have entered the code fastboot devices and my phone is seen. The Code fastboot devices is also still good but if I fastboot oem unlock code entry, nothing happens I can not choose between one and two I saw hebop an explanation on youtube. Everything just stays the same and my phone is not fully datawiped and all files are still there just. The Code fastboot reboot my phone restarts. what can I do about this?

As I understand you have follow that guide and now you have
enabled in settings, developer options,
OEM unlocking.
Then in fastboot mode device is discovered by "fastboot devices" that means drivers are properly installed.
Whenever your try to execute "fastboot OEM unlock" your device restart but don't unlock the bootloader.
What I would do is different things first to factory reset and try to unlock again.
Try on different computer.
Flash latest official signed rom and try the unlocking procedure again
Sent from my ONE A2005 using Tapatalk

hrvw said:
Hello again,
I have followed these steps but it did not work. When I started my OnePlus 2 in bootloder and then you have entered the code fastboot devices and my phone is seen. The Code fastboot devices is also still good but if I fastboot oem unlock code entry, nothing happens I can not choose between one and two I saw hebop an explanation on youtube. Everything just stays the same and my phone is not fully datawiped and all files are still there just. The Code fastboot reboot my phone restarts. what can I do about this?
Click to expand...
Click to collapse
Hello, have you managed to fix your issue about root as described above? Because I have the same problem and I've tried many tricks without a positive result. Any help, please?
Thanks.

abenguru said:
Hello, have you managed to fix your issue about root as described above? Because I have the same problem and I've tried many tricks without a positive result. Any help, please?
Thanks.
Click to expand...
Click to collapse
I have not tried yet, but go do it within short and then I'll let you know if it worked.

This did not work. do you have any more tips?

Related

No "Enable OEM unlock" options in developer settings

Hey guys, I just tried to unlock my bootloader. I have obtained the unlock code and everything. I try to execute this command
Code:
fastboot oem unlock XXXX
, I always get stuck at
Code:
waiting for devices
1. I have updated my device drivers.
2. For some odd reason, the toggle for "Enable OEM unlock" is not present in the developer options.
3. Now, I have updated my KIW-L22 to B340 version recently. Maybe the toggle is removed in the recent update. Is there not any way to bring back that toggle so that I can unlock my bootloader?
Please guys, I need your help with this, if anyone has ever encountered this before, please tell me how to bring it back.
narangkunal said:
Hey guys, I just tried to unlock my bootloader. I have obtained the unlock code and everything. I try to execute this command
Code:
fastboot oem unlock XXXX
, I always get stuck at
Code:
waiting for devices
1. I have updated my device drivers.
2. For some odd reason, the toggle for "Enable OEM unlock" is not present in the developer options.
3. Now, I have updated my KIW-L22 to B340 version recently. Maybe the toggle is removed in the recent update. Is there not any way to bring back that toggle so that I can unlock my bootloader?
Please guys, I need your help with this, if anyone has ever encountered this before, please tell me how to bring it back.
Click to expand...
Click to collapse
I had the same issue you don't need to toggle the option on marshmallow. The error looks like you need to do a sudo fastboot if your using linux.
The only other thing to remember is you need to remove the factory reset protection (frp) see here http://forum.xda-developers.com/honor-5x/help/unlock-bootloader-issues-kiw-t3411032
narangkunal said:
Hey guys, I just tried to unlock my bootloader. I have obtained the unlock code and everything. I try to execute this command
Code:
fastboot oem unlock XXXX
, I always get stuck at
Code:
waiting for devices
1. I have updated my device drivers.
2. For some odd reason, the toggle for "Enable OEM unlock" is not present in the developer options.
3. Now, I have updated my KIW-L22 to B340 version recently. Maybe the toggle is removed in the recent update. Is there not any way to bring back that toggle so that I can unlock my bootloader?
Please guys, I need your help with this, if anyone has ever encountered this before, please tell me how to bring it back.
Click to expand...
Click to collapse
Just because that option is not available does not mean your bootloader is locked, plus you can unlock using ADB.
Just enable usb debug only
Sent from my KIW-L24 using XDA-Developers mobile app
narangkunal said:
Hey guys, I just tried to unlock my bootloader. I have obtained the unlock code and everything. I try to execute this command
Code:
fastboot oem unlock XXXX
, I always get stuck at
Code:
waiting for devices
1. I have updated my device drivers.
2. For some odd reason, the toggle for "Enable OEM unlock" is not present in the developer options.
3. Now, I have updated my KIW-L22 to B340 version recently. Maybe the toggle is removed in the recent update. Is there not any way to bring back that toggle so that I can unlock my bootloader?
Please guys, I need your help with this, if anyone has ever encountered this before, please tell me how to bring it back.
Click to expand...
Click to collapse
This option is not there in Marshmallow. not sure if there is still a way to unlock as this option itself is not there...try enabling USB debugging couple of times and see if it prompt you for authorisation. if it does, you can still do the required things.
did u unlocked bootloder???
did u unlocked bootloder???
i m having same problem
princereshim said:
did u unlocked bootloder???
i m having same problem
Click to expand...
Click to collapse
What problem?
no oem unlock option
no oem unlock option
in developer option
princereshim said:
no oem unlock option
in developer option
Click to expand...
Click to collapse
If you are in lollipop it will be there but if u r on marshmallow then it wont be there. Just enable usb debugging and you r good to proceed.
narangkunal said:
Hey guys, I just tried to unlock my bootloader. I have obtained the unlock code and everything. I try to execute this command
Code:
fastboot oem unlock XXXX
, I always get stuck at
Code:
waiting for devices
1. I have updated my device drivers.
2. For some odd reason, the toggle for "Enable OEM unlock" is not present in the developer options.
3. Now, I have updated my KIW-L22 to B340 version recently. Maybe the toggle is removed in the recent update. Is there not any way to bring back that toggle so that I can unlock my bootloader?
Please guys, I need your help with this, if anyone has ever encountered this before, please tell me how to bring it back.
Click to expand...
Click to collapse
How did u get the unlock code on KIW-L22 model because i have tried i dont know how many time but the emui website return me error that either model number is wrong or the verification code
Harsh007agrawal said:
, I always get stuck at
1. I have updated my device drivers.
2. For some odd reason, the toggle for "Enable OEM unlock" is not present in the developer options.
3. Now, I have updated my KIW-L22 to B340 version recently. Maybe the toggle is removed in the recent update. Is there not any way to bring back that toggle so that I can unlock my bootloader?
Please guys, I need your help with this, if anyone has ever encountered this before, please tell me how to bring it back.
How did u get the unlock code on KIW-L22 model because i have tried i dont know how many time but the emui website return me error that either model number is wrong or the verification code
Click to expand...
Click to collapse
Try Chinese site to get same.
And which rom are u sing could you give me link to latest twrp and rooting files needed
Harsh007agrawal said:
And which rom are u sing could you give me link to latest twrp and rooting files needed
Click to expand...
Click to collapse
See the pinned post in the guides tab... It has all the information and links
Sent from my KIW-L21 using Tapatalk
im also getting the same problem. it does not recognize device.. im on stock marshmallow and there is no option of oem unlock
Harris Aamir said:
im also getting the same problem. it does not recognize device.. im on stock marshmallow and there is no option of oem unlock
Click to expand...
Click to collapse
Just enable the usb debugging if you r on stock mm. Try changing the usb port amd see if it work
seams rolling back is the only solution ! .
Romiui said:
seams rolling back is the only solution ! .
Click to expand...
Click to collapse
Why what happened?
narangkunal said:
Hey guys, I just tried to unlock my bootloader. I have obtained the unlock code and everything. I try to execute this command
Code:
fastboot oem unlock XXXX
, I always get stuck at
Code:
waiting for devices
1. I have updated my device drivers.
2. For some odd reason, the toggle for "Enable OEM unlock" is not present in the developer options.
3. Now, I have updated my KIW-L22 to B340 version recently. Maybe the toggle is removed in the recent update. Is there not any way to bring back that toggle so that I can unlock my bootloader?
Please guys, I need your help with this, if anyone has ever encountered this before, please tell me how to bring it back.
Click to expand...
Click to collapse
I cant find mine either, but i have a suspicion that they just removed/edited the files to just have one state of locked and no controls or commands to unlock it.
Find out the file name and path for the "OEM unlock" setting in the developer options.
then search for it using the ADB, if the files aren't there then you might need to put the phone in to download mode and "sideload" the the full files back on to it.. if it's possible.
it might be more complicated than that. that's what i would've done as a Carrier if i wanted to keep modders and phone thieves out.
also on my Carrier phone when i put it into Download mode it seems to run like there own unlock before it does anything else, might need to run that first to unlock the lock so you can unlock it...
this is kind of a BS response, but at least it's an idea to look into. Sorry.
also you could try loading PDANet to see if the device will recognise.
Tamoghna Chowdhury from Android.stackexchange TOO NEW CAN'T POST LINKS said:
To unlock the boot loader you need to have the ADT with all the packages installed and configured.
Later once the configuration is done properly then you can connect your device and enable USB Debugging under the options.
Download Modaco’s Superboot files and save them to your computer.
Once downloaded, extract it by right clicking and extract all.
On your phone, click on Settings > Developer Options > Turn USB Debugging On.
Plug the device in to your computer via USB cable.
Open the superboot folder that we just extracted (until you see the folder with fastboot-windows inside it), then hold the shift key down on your computer and right click any blank area.
Now, select open command window here.
In the command prompt, type the following with hitting enter at the end of each line.
adb-windows reboot bootloader (and wait for the device to reboot)
fastboot-windows oem unlock
(If it gets stuck at waiting for device here, download and install PDANet on your computer, once installed, unplug then plug the device back in and see if that fixes it)
Once it runs the device should display a screen asking you if you are sure. Click yes using the volume buttons. The device will go back to the bootloader screen but say unlocked at the bottom.
Click to expand...
Click to collapse
Leftcatcher said:
I cant find mine either, but i have a suspicion that they just removed/edited the files to just have one state of locked and no controls or commands to unlock it.
Find out the file name and path for the "OEM unlock" setting in the developer options.
then search for it using the ADB, if the files aren't there then you might need to put the phone in to download mode and "sideload" the the full files back on to it.. if it's possible.
it might be more complicated than that. that's what i would've done as a Carrier if i wanted to keep modders and phone thieves out.
also on my Carrier phone when i put it into Download mode it seems to run like there own unlock before it does anything else, might need to run that first to unlock the lock so you can unlock it...
this is kind of a BS response, but at least it's an idea to look into. Sorry.
also you could try loading PDANet to see if the device will recognise.
Click to expand...
Click to collapse
Never mind, I did unlock my bootloader. Thanks for your help though.
Fixed !!!
narangkunal said:
Hey guys, I just tried to unlock my bootloader. I have obtained the unlock code and everything. I try to execute this command
Code:
fastboot oem unlock XXXX
, I always get stuck at
Code:
waiting for devices
1. I have updated my device drivers.
2. For some odd reason, the toggle for "Enable OEM unlock" is not present in the developer options.
3. Now, I have updated my KIW-L22 to B340 version recently. Maybe the toggle is removed in the recent update. Is there not any way to bring back that toggle so that I can unlock my bootloader?
Please guys, I need your help with this, if anyone has ever encountered this before, please tell me how to bring it back.
Click to expand...
Click to collapse
It's Ok,In Adb Write "adb enable oem unlocking"
I Learned That From A Video
Called:
"How To Unlock Bootloader-Huawei GR5 & Honor 5X EMUI 4.0"
From The Channel Called:"NoNDrOiD"

Kenzo Error Fix {Failed (remote: token verification failed, reboot the device)}.

Can any developer please please help me out quickly? i'm out of time seriously I need help but quick.
I'm trying to unlock my device Redmi Note 3 Snapdragon varient. All the other commands like
* adb devices
* adb reboot edl
* fastboot devices
* fastboot oem device-info
everyone of it is working fine but when I write
* fastboot oem unlock-go
I get the above mentioned error.
Does anybody know the solution to it? Before answering please consider that other commands are working except this one, I didn't found any proper solution that's why posted the problem here and I already did revoke USB debugging permissions and turned it on again but that didn't helped.
So please give me a working solution as quick as possible or else any help is appreciable.
enable oem unlock in developer options
Enable OEM Unlock option in Developer Options.
caesar13th said:
enable oem unlock in developer options
Click to expand...
Click to collapse
It's already enabled, I don't know what's causing the problem. Please help me with another solution. Ask everything at once, I will answer. But I really need a solution.
superboy123 said:
Enable OEM Unlock option in Developer Options.
Click to expand...
Click to collapse
It's already enabled, I don't know what's causing the problem. Please help me with another solution. Ask everything at once, I will answer. But I really need a solution.
Gurkirat_Singh said:
It's already enabled, I don't know what's causing the problem. Please help me with another solution. Ask everything at once, I will answer. But I really need a solution.
Click to expand...
Click to collapse
That fastboot oem unlock-go command won't work.
OK, follow these steps:-
a) Reboot to Fastboot mode by pressing Power and Vol down buttons for 10 seconds.
b) Download the MiUnlock tool and enter your credentials first. It will check whether your Mi account has permission to unlock (you must have permission from Xiaomi to unlock).
c) It will detect your phone as Mi Phone and proceed to unlock.
d) It will verify whether the Mi account in your phone and the credentials of the Mi account you entered on the PC are the same.
e) It will unlock your device for sure!
If it says some sort of verification error aka. the famous stuck at 50%, wait for some days like for a week and try again, it may work even in 2 days! Keep trying!
Good Luck!:good::highfive:
Thank you!
superboy123 said:
That fastboot oem unlock-go command won't work.
OK, follow these steps:-
a) Reboot to Fastboot mode by pressing Power and Vol down buttons for 10 seconds.
b) Download the MiUnlock tool and enter your credentials first. It will check whether your Mi account has permission to unlock (you must have permission from Xiaomi to unlock).
c) It will detect your phone as Mi Phone and proceed to unlock.
d) It will verify whether the Mi account in your phone and the credentials of the Mi account you entered on the PC are the same.
e) It will unlock your device for sure!
If it says some sort of verification error aka. the famous stuck at 50%, wait for some days like for a week and try again, it may work even in 2 days! Keep trying!
Good Luck!:good::highfive:
Thank you!
Click to expand...
Click to collapse
Thanks for the help but I don't even want to try that method first it's very problematic, it takes a lot of time and it's not even sure if it works. So if you can help me with the problem I'm having that would very very very appreciable :good:.
And why the command will not work, can you please tell me? Also this command gives the same error "fastboot OEM unlock bootloader". Hope you can help .
Gurkirat_Singh said:
Thanks for the help but I don't even want to try that method first it's very problematic, it takes a lot of time and it's not even sure if it works. So if you can help me with the problem I'm having that would very very very appreciable :good:.
And why the command will not work, can you please tell me? Also this command gives the same error "fastboot OEM unlock bootloader". Hope you can help .
Click to expand...
Click to collapse
It's not that problematic, actually it is the easiest way to unlock bootloader!
Unofficial bootloader is the very "problematic" method.
Anyhow, Are you looking for unofficial bootloader unlock? Then go here and follow the steps correctly, dont skip any step.
And for your second question, Xiaomi has complicated the bootloader unlock process by heavy encryption. That's why you couldn't unlock Redmi Note 3 as any Moto device!
superboy123 said:
It's not that problematic, actually it is the easiest way to unlock bootloader!
Unofficial bootloader is the very "problematic" method.
Anyhow, Are you looking for unofficial bootloader unlock? Then go here and follow the steps correctly, dont skip any step.
And for your second question, Xiaomi has complicated the bootloader unlock process by heavy encryption. That's why you couldn't unlock Redmi Note 3 as any Moto device!
Click to expand...
Click to collapse
OK that's why I'm having so much problem to unlock it. I just want to ask do you know any other way to fix the problem I'm having with this error. Cause the post you gave me tells how to unlock the RN3 temporary :crying: but the thread I followed helps to unlock it permanently :good: (how I know cause I used similar commands on my Canvas A1) and I followed almost every step properly.
I don't understand why companies emerged as custom ROMs stops supporting customisation, at least don't make it hard. I just wanted to flash my RN3 with a Custom ROM like CM13 cause MIUI is not supporting 4G networks properly of multiple operators that's why, for which I needed a custom recovery and for which I needed unlocked bootloader.
I just don't understand , all this so that no one could copy their ROM or I don't know for what . It's just makes things difficult for normal people and no one else. Locks can't keep a thief away. If anyone wants to break into their system than one will, if he/she uses right tools properly. Why make normal people lives' difficult?
ALSO I WANT TO ASK MORE THING, if in first case, I get into fastboot mode just after the ROM flash & before very first ROM boot and run this command and if in second case, the room gets booted and then I go into fastboot mode & run the command, DOES IT CREATES ANY CHANCE OF NON-OCCURRENCE OF THAT ERROR IN FIRST CASE?.
Gurkirat_Singh said:
OK that's why I'm having so much problem to unlock it. I just want to ask do you know any other way to fix the problem I'm having with this error. Cause the post you gave me tells how to unlock the RN3 temporary :crying: but the thread I followed helps to unlock it permanently :good: (how I know cause I used similar commands on my Canvas A1) and I followed almost every step properly.
I don't understand why companies emerged as custom ROMs stops supporting customisation, at least don't make it hard. I just wanted to flash my RN3 with a Custom ROM like CM13 cause MIUI is not supporting 4G networks properly of multiple operators that's why, for which I needed a custom recovery and for which I needed unlocked bootloader.
I just don't understand , all this so that no one could copy their ROM or I don't know for what . It's just makes things difficult for normal people and no one else. Locks can't keep a thief away. If anyone wants to break into their system than one will, if he/she uses right tools properly. Why make normal people lives' difficult?
ALSO I WANT TO ASK MORE THING, if in first case, I get into fastboot mode just after the ROM flash & before very first ROM boot and run this command and if in second case, the room gets booted and then I go into fastboot mode & run the command, DOES IT CREATES ANY CHANCE OF NON-OCCURRENCE OF THAT ERROR IN FIRST CASE?.
Click to expand...
Click to collapse
The thread I gave you was not temporary, it is permanent and it is temporary till you get the official unlock permission. Actually it's a permanent 'safe' solution.
Xiaomi did it for security of data, not to stop customising. If it had to stop users from customising, xiaomi wouldn't have given you warranty even if you root or it may not even have given you an option to unlock bootloader!
superboy123 said:
The thread I gave you was not temporary, it is permanent and it is temporary till you get the official unlock permission. Actually it's a permanent 'safe' solution.
Xiaomi did it for security of data, not to stop customising. If it had to stop users from customising, xiaomi wouldn't have given you warranty even if you root or it may not even have given you an option to unlock bootloader!
Click to expand...
Click to collapse
Thanks for all the support and help you gave me.
I got this error too but i forgot how to fix it.
Something about the 'disable driver signature' or the modified rom that you flash before you trying to unlock.
caesar13th said:
I got this error too but i forgot how to fix it.
Something about the 'disable driver signature' or the modified rom that you flash before you trying to unlock.
Click to expand...
Click to collapse
I unlocked the bootloader and also flashed the ROM successfully but still I'm not able to use the 4g service.
superboy123 said:
The thread I gave you was not temporary, it is permanent and it is temporary till you get the official unlock permission. Actually it's a permanent 'safe' solution.
Xiaomi did it for security of data, not to stop customising. If it had to stop users from customising, xiaomi wouldn't have given you warranty even if you root or it may not even have given you an option to unlock bootloader!
Click to expand...
Click to collapse
I unlocked the bootloader and also flashed the ROM successfully but still I'm not able to use the 4g service.
Gurkirat_Singh said:
I unlocked the bootloader and also flashed the ROM successfully but still I'm not able to use the 4g service.
Click to expand...
Click to collapse
By your name, I think you are an Indian, so which Sim you are using? You need to do a 4G pack recharge first to use LTE, VoLTE won't work in custom ROMs right now.
Edit: you could see this thread but this is a bit complicated: http://en.miui.com/thread-335643-1-1.html
superboy123 said:
By your name, I think you are an Indian, so which Sim you are using? You need to do a 4G pack recharge first to use LTE, VoLTE won't work in custom ROMs right now.
Edit: you could see this thread but this is a bit complicated: http://en.miui.com/thread-335643-1-1.html
Click to expand...
Click to collapse
I appreciate your help but the post you gave me is for non-asian countries so it will not work for me. As you already know I'm an Indian so that's why. Are you an Indian, only asking cause in that way you may already faced the problems i'm having.
I'm only familiar with only 2 4G networks for now. One is Airtel 4G, what they say have FDD LTE network, I don't what that is, but that's why it's not working on my phone, I contacted them and they said that my phone doesn't support it, I don't know why cause it support much more LTE Bands other than any smartphone in that price range. Second is Jio 4G, my sim gets detected, shows network in manual selection but doesn't get registered on them. I see only the message of 'No Service' or 'Emergency calls only' when I insert it.
@Gurkirat_Singh
It worked for me.
I had the same problem!
superboy123 said:
@Gurkirat_Singh
It worked for me.
I had the same problem!
Click to expand...
Click to collapse
What worked for you and how? Can you please answer/clarify my questions/doubts please also?
I tried that fix that I gave you and 4G started working for me. You cannot use jio on second sim slot. 2nd sim only connects to 2g.
superboy123 said:
I tried that fix that I gave you and 4G started working for me. You cannot use jio on second sim slot. 2nd sim only connects to 2g.
Click to expand...
Click to collapse
OK I'll try when got time and will update you with the result.

Deleted Mi account linked to phone

Hi there,
as the thread title suggests, my phone is linked to a non-existing Mi account.
As my (100% correct) password didnt work, the Xiaomi support told me to try and delete the Mi account, which was linked to the phone. Bad idea!
And now, as the shop shipped out the device with an unofficially unlocked bootloader, my bootloader has been relocked and I can only flash ROMs via fastboot. But this seems not to work in terms of deleting the MI account from the phone. No matter what ROM I flashed, there still is the login screen with the prompt to enter the password for the non-existing account.
I have tried many guides on how to remove the Mi account from the phone, but no luck this far.
Can anyone please provide a solution?
Thanks in advance!
AtzeOnAcid said:
Hi there,
as the thread title suggests, my phone is linked to a non-existing Mi account.
As my (100% correct) password didnt work, the Xiaomi support told me to try and delete the Mi account, which was linked to the phone. Bad idea!
And now, as the shop shipped out the device with an unofficially unlocked bootloader, my bootloader has been relocked and I can only flash ROMs via fastboot. But this seems not to work in terms of deleting the MI account from the phone. No matter what ROM I flashed, there still is the login screen with the prompt to enter the password for the non-existing account.
I have tried many guides on how to remove the Mi account from the phone, but no luck this far.
Can anyone please provide a solution?
Thanks in advance!
Click to expand...
Click to collapse
Is this snapdragon n or mediatek
Used or new
Btw if u are using snapdragon then u can install custom rom sand recovery even with the bootloader locked search for that in the xda redmi note 3 section and also answer the questions I asked
Androbots said:
Is this snapdragon n or mediatek
Used or new
Click to expand...
Click to collapse
Oops, sorry, forgot about the two different models for a minute.
I'm on Snapdragon (kenzo) and the phone was ordered as new (but with some inofficial store ROM).
I tried a lot of different ROMs and yes, I could flash them in spite of the locked bootloader,
but no luck still with the account login screen...
After deleting MI account, flash any ROM stable/developer ROM without SIM card inserted in EDL mode and try again. That login to MI only comes in first boot if SIM card was inserted, without SIM card atleast I don't get that login screen. Then create MI ACCOUNT in mobile itself on Wi-Fi, not with SIM inserted. Hope this helps a bit
AtzeOnAcid said:
Oops, sorry, forgot about the two different models for a minute.
I'm on Snapdragon (kenzo) and the phone was ordered as new (but with some inofficial store ROM).
I tried a lot of different ROMs and yes, I could flash them in spite of the locked bootloader,
but no luck still with the account login screen...
Click to expand...
Click to collapse
Well then you can flash any AOSP ROM via TWRP (I recommend ZCX TWRP recovery).Go for lineage os or slim7 both are quite good Roms.
For the non existent account issue login through a computer and then try forgot password and other things see if u can succeed.
Androbots said:
Well then you can flash any AOSP ROM via TWRP (I recommend ZCX TWRP recovery).Go for lineage os or slim7 both are quite good Roms.
For the non existent account issue login through a computer and then try forgot password and other things see if u can succeed.
Click to expand...
Click to collapse
Sorry, but due to the locked bootloader, I couldn't manage to flash TWRP so far. But after I had another look at the respective forums, I understand that there is a new possibility to flash recovery with a locked bootloader. I will try this tomorrow evening and report back.
Thanks so far!
About the use the computer suggestion: I have tried everything in this matter, believe me
Couldn't even make it work with the help of Xiaomi support...
Dr. Joy Das said:
After deleting MI account, flash any ROM stable/developer ROM without SIM card inserted in EDL mode and try again. That login to MI only comes in first boot if SIM card was inserted, without SIM card atleast I don't get that login screen. Then create MI ACCOUNT in mobile itself on Wi-Fi, not with SIM inserted. Hope this helps a bit
Click to expand...
Click to collapse
Thanks for your reply, but I have tried that to no luck. I don't understand how Xiaomi can check my account without a Wi-Fi or GSM connection, but they still manage anyhow...
Androbots said:
Well then you can flash any AOSP ROM via TWRP (I recommend ZCX TWRP recovery).Go for lineage os or slim7 both are quite good Roms.
For the non existent account issue login through a computer and then try forgot password and other things see if u can succeed.
Click to expand...
Click to collapse
Ok report back via private message i am keen to listen the outcome.
Okay, I have tried to flash TWRP over the locked bootloader by replacing the recovery.img in the developer ROM.
The MiFlash process was successful,but when I tried to enter recovery by pressing power and volume up, I always ended up with the picture of an USB-cable and a PC. So it seems like there was no recovery installed.
So, I couldn't flash any other ROMs unfortunately...
Anybody has any suggestions how to get lineage or any other ROM on my Note 3?
contact mi service,then follow instruction from mi service need 2-3 days to unlock mi account from server.
btxsamurai said:
contact mi service,then follow instruction from mi service need 2-3 days to unlock mi account from server.
Click to expand...
Click to collapse
Mi Service couldn't help me at all since the respective account has already been deleted.
They more or less told me that there is nothing they can do for me...
reflash kernel and choose another fingerprint driver from aroma installer
nikolas60 said:
reflash kernel and choose another fingerprint driver from aroma installer
Click to expand...
Click to collapse
Thanks for the tip, but how can I flash a new kernel with locked bootloader and without a custom recovery?
Fixed using this
I had the same problem and took me 2 days to find a good solution and here it is... There is a software called RBSoft Mobile Tool (used v1.4 for RMN3). It's commercial but you can find it online if that's not a problem
adb shell
su
setprop sys.usb.config diag,adb
...and it will show you the port you have to use and just press Remove Mi account. It takes couple of seconds. Reboot, and whoila
Good luck
Edit: This has to be done in EDL mode but it's noted in application. Phone has to be rooted, too
AtzeOnAcid said:
Okay, I have tried to flash TWRP over the locked bootloader by replacing the recovery.img in the developer ROM.
The MiFlash process was successful,but when I tried to enter recovery by pressing power and volume up, I always ended up with the picture of an USB-cable and a PC. So it seems like there was no recovery installed.
So, I couldn't flash any other ROMs unfortunately...
Anybody has any suggestions how to get lineage or any other ROM on my Note 3?
Click to expand...
Click to collapse
You please unlock bootloader by this thread https://forum.xda-developers.com/redmi-note-3/how-to/guide-rn3-pro-se-t3565172
And then install recovery.
Let me know if it helps
himanshux said:
You please unlock bootloader by this thread https://forum.xda-developers.com/redmi-note-3/how-to/guide-rn3-pro-se-t3565172
And then install recovery.
Let me know if it helps
Click to expand...
Click to collapse
Thanks for your help.
I have managed to open the bootloader, but no success yet with flashing TWRP - MiFlash shows a success, but when I try to enter recovery by the button combination, the phone does simply nothing (sometimes it will boot normally when I release the keys).
Rebooting to recovery via ADB doesn't work for the fact, that the phone is only recognized in fastboot mode. This may either come from the fact, that I can't get into the phone in order to activate USB debugging or from my driver chaos, since I have installed every Xiaomi driver in existance, I guess
I'll try different versions of TWRP over the weekend and let you know how this works out...
what is your current rom?
AtzeOnAcid said:
Thanks for your help.
I have managed to open the bootloader, but no success yet with flashing TWRP - MiFlash shows a success, but when I try to enter recovery by the button combination, the phone does simply nothing (sometimes it will boot normally when I release the keys).
Rebooting to recovery via ADB doesn't work for the fact, that the phone is only recognized in fastboot mode. This may either come from the fact, that I can't get into the phone in order to activate USB debugging or from my driver chaos, since I have installed every Xiaomi driver in existance, I guess
Click to expand...
Click to collapse
Hey I think you are doing something wrong.
After following steps of unlocking bootloader, did you reboot in fastboot mode and then run following code in command prompt?
fastboot oem unlock-go
Try above code (this will be the final nail in the coffin for unlocking bootloader)
After this you follow below link to install recovery
https://forum.xda-developers.com/redmi-note-3/how-to/zcx-twrp-install-twrp-flash-supersu-t3462448
I installed recovery by this thread, excellent one, no hassles
Let me know if it helped you.
himanshux said:
Hey I think you are doing something wrong.
After following steps of unlocking bootloader, did you reboot in fastboot mode and then run following code in command prompt?
fastboot oem unlock-go
Try above code (this will be the final nail in the coffin for unlocking bootloader)
After this you follow below link to install recovery
https://forum.xda-developers.com/redmi-note-3/how-to/zcx-twrp-install-twrp-flash-supersu-t3462448
I installed recovery by this thread, excellent one, no hassles
Let me know if it helped you.
Click to expand...
Click to collapse
Of course I was doing something wrong...
But no luck with the "fastboot oem unlock-go" either.
It shows that the oem unlock is not allowed...
Is there any kind of workaround for that?

Lenovo K10 Note "Enabled OEM Unlock" not working!!!!!!

Hey there, I have a question, that has been bugging my head for 2 days now. So i tried unlocking the bootloader of my Lenovo K10 Note, but it just didn't work properly. So i started with enabling the option for oem unlock and usb debugging. Then i installed Android SDK and followed the common steps. Keep in mind that oem unlock is enabled. So I then proceed with fastboot flash unlock and pasting the img that Lenovo sent me. The command goes through, then it types sending unlock and then... it freezes. I then go to restart the bootloader from the phone and the flash unlock fails, pointing out a variety of errors(out of links, ect.). So my question is, what do i do know? Thanks in advance!
m3chan1zed said:
Hey there, I have a question, that has been bugging my head for 2 days now. So i tried unlocking the bootloader of my Lenovo K10 Note, but it just didn't work properly. So i started with enabling the option for oem unlock and usb debugging. Then i installed Android SDK and followed the common steps. Keep in mind that oem unlock is enabled. So I then proceed with fastboot flash unlock and pasting the img that Lenovo sent me. The command goes through, then it types sending unlock and then... it freezes. I then go to restart the bootloader from the phone and the flash unlock fails, pointing out a variety of errors(out of links, ect.). So my question is, what do i do know? Thanks in advance!
Click to expand...
Click to collapse
Which serial number you used my phone settings serial number and bootloader serial number was different I used bootloader serial number and it worked

{CLOSED} delete

ahsvanz
try
C:\ADB >fastboot devices
C:\ADB >fastboot OEM device-info
etc
replacing
C:\ADB with where ever you fastboot file is located
I too am having the same issue.
I recently wanted to try Android 12, I took a chinnese version of it and my phone is unusable, literally all chinnese.
I want to downgrade, I enabled Debugging and Oeam Unlock in Dev options but I get the ''remote: 'Flashing Unlock is not allowed"" when I try to fastboot oem unlock, I tried different USB ports, I keep updating all my drivers for ADB but nothing is working. I'm panicking a bit cause I don't have a phone to use, and not many people work with ONEPLUS in my country.
If someone has an answer, please save me lol
slimmynine said:
I too am having the same issue.
I recently wanted to try Android 12, I took a chinnese version of it and my phone is unusable, literally all chinnese.
I want to downgrade, I enabled Debugging and Oeam Unlock in Dev options but I get the ''remote: 'Flashing Unlock is not allowed"" when I try to fastboot oem unlock, I tried different USB ports, I keep updating all my drivers for ADB but nothing is working. I'm panicking a bit cause I don't have a phone to use, and not many people work with ONEPLUS in my country.
If someone has an answer, please save me lol
Click to expand...
Click to collapse
have you tried the code above ??
cant you just download the official original firmware and flash that ? im not familiar with the oneplus flashing techniques, ive always had samsungs except for the htc evo 3d back in the day
I tried them all, nothing seems to work
I'm stuck at 'Flashing unlock is not allowed'. I've set up everything I need to in Developer Options, I made sure they're all enabled.
It's really weird, could it potentially be a software issue? The software itself will not allow me to unlock OEM even though the check is turned on?
slimmynine said:
I tried them all, nothing seems to work
I'm stuck at 'Flashing unlock is not allowed'. I've set up everything I need to in Developer Options, I made sure they're all enabled.
It's really weird, could it potentially be a software issue? The software itself will not allow me to unlock OEM even though the check is turned on?
Click to expand...
Click to collapse
how does the one plus flash firmware ? for samsung we use a tool called odin, do you not have a similar tool for your device ?
I don't recall having any toolkit like that, but in order for the toolkit to work.. do you need to have an unlocked bootloader?
Cause the main issue is that I can't unlock it.
i dont think so, if your flashing an official firmware, but for your device i cant be sure of that
?
did you try running your commands as an su , is your device rooted ? you could try sideloading an update.zip maybe
what does it say when you flash this command ? true, true false ?
C:\ADB>fastboot OEM device-info
maybe this will help https://forum.xda-developers.com/t/...us-2-back-to-stock-100.3269543/#post-64279667
slimmynine said:
I too am having the same issue.
I recently wanted to try Android 12, I took a chinnese version of it and my phone is unusable, literally all chinnese.
I want to downgrade, I enabled Debugging and Oeam Unlock in Dev options but I get the ''remote: 'Flashing Unlock is not allowed"" when I try to fastboot oem unlock, I tried different USB ports, I keep updating all my drivers for ADB but nothing is working. I'm panicking a bit cause I don't have a phone to use, and not many people work with ONEPLUS in my country.
If someone has an answer, please save me lol
Click to expand...
Click to collapse
yeah i think some phone makers lock down the bootloader, like its unlocked but when i try to flash a gsi it says device locked state
jamsandpeabug said:
alcatel has a program to download and install firmware but the device is not listed, cannot find fw on the net
Click to expand...
Click to collapse
OK try
c:\adb
Adb fastboot oem device-info
Replacing
C:\adb
With where ever your fastboot is located
Just to check if your device is showing is oem locked or unlocked, it will display with a true or false option. I can't really advise to much as I don't have experience with that device
You could also try
fastboot oem unlock_critical
Not sure if that will work for your device though
Idk what else to recommend, are you stuck at boot ? Can u boot into recovery mode ? Do u have an ext sd card slot
OT-6025D | GSMSERVERPRO
gsmserverpro.com
Is that your firmware
Alcatel 1s Flash File Download [Stock ROM or Firmware
You can Download latest flash file and flash tools for Alcatel 1s phone here. Original stock ROM or Firmware available for free.
mobilereset99.com
Have youlooked at that
if you can confirm your phone has a mtk chipset use mtkclient to bootloader unlock it https://github.com/bkerler/mtkclient
otherwise youre out of luck
But
jamsandpeabug said:
im not stuck at boot, i want to flash gsi but it says device is in locked state even with oem unlocked in dev options, adb debugging enabled etc , and just wont let me flash.. its starts flashing and then fails due to locked state
Click to expand...
Click to collapse
If the flashing starts, and fails, the os would be overwritten and you wouldn't be able to boot. So what you mean is the process trys to start but fails, right yh then I don't know what else I can say to try and help, let's hope mtkclient is an avenue you can pursue
MOD ACTION:
Thread closed since OP has no content.

Categories

Resources