Bootloader or oem unlock not working - Lenovo P2 Questions & Answers

HELLO
I want to unlock my lenovo p2 and install twrp in it but in oem unlock option if i was pressing it was showing LENOVO ID WITHOUT PERMISSION and not going forward.help me to root my phone

yasaswi2509 said:
HELLO
I want to unlock my lenovo p2 and install twrp in it but in oem unlock option if i was pressing it was showing LENOVO ID WITHOUT PERMISSION and not going forward.help me to root my phone
Click to expand...
Click to collapse
You will need to verify you Lenovo account, an e-mail will be sent to the address you used to set up your account. Once verified go back to OEM/Bootloader unlock to start the 14day wait.
Hope that helps.

I have verified the link that i got and it states success but iam not able to unlock its saying network unavailable even if i was connected to net

I have the same issue. Did you fix this already?

If you aren't on global release over the world version you can't unlock BL. Send a screenshot of about phone or build number.
Sent from my Lenovo P2a42 using Tapatalk

yasaswi2509 said:
HELLO
I want to unlock my lenovo p2 and install twrp in it but in oem unlock option if i was pressing it was showing LENOVO ID WITHOUT PERMISSION and not going forward.help me to root my phone
Click to expand...
Click to collapse
Did you find any solution for this. I am also facing the same issue.

Same issue here.
I thinks it started after the july security update for nogat!

QUAD_FOXX said:
I thinks it started after the july security update for nogat!
Click to expand...
Click to collapse
No. The July security update came on August. The first post on this thread came in July. So, this has nothing to with the new security patch. I checked two days ago and it synced correctly. It was only yesterday that I started experiencing this issue. I just hope it's a temporary problem.

medwatt said:
No. The July security update came on August. The first post on this thread came in July. So, this has nothing to with the new security patch. I checked two days ago and it synced correctly. It was only yesterday that I started experiencing this issue. I just hope it's a temporary problem.
Click to expand...
Click to collapse
oh.. i hope the same

QUAD_FOXX said:
oh.. i hope the same
Click to expand...
Click to collapse
1. When did you start observing the issue ?
2. Do you have the 32 GB model out of 64GB model?

Ive EU version. What I did was to log out from the Lenovo account when I tried to check how many days it was left of the 14 days "saftey".
edit: lol, tried it now and nope same error as you guys.

Same problem here and I have no clue what I could do so far now.
Is there no solution out there? Probaply not a good choice of smartphone?

maggy2011 said:
Same problem here and I have no clue what I could do so far now.
Is there no solution out there? Probaply not a good choice of smartphone?
Click to expand...
Click to collapse
I think we have proof now that is not an isolated issue. A lot of us are experiencing it at the same time. There was a similar issue last week for OTA updates, but after some pressure in the Lenovo forum, the servers were back online. I don't know if this is a temporary problem and the servers will be online soon, or OEM unlock service is down for good.

medwatt said:
1. When did you start observing the issue ?
2. Do you have the 32 GB model out of 64GB model?
Click to expand...
Click to collapse
yesterday. it was the first time checking after the update.
---------- Post added at 02:06 AM ---------- Previous post was at 02:06 AM ----------
QUAD_FOXX said:
yesterday. it was the first time checking after the update.
Click to expand...
Click to collapse
yea 32gb model

medwatt said:
I think we have proof now that is not an isolated issue. A lot of us are experiencing it at the same time. There was a similar issue last week for OTA updates, but after some pressure in the Lenovo forum, the servers were back online. I don't know if this is a temporary problem and the servers will be online soon, or OEM unlock service is down for good.
Click to expand...
Click to collapse
After have tried Lenovos "support" before I will not send a bug report to them. Hopefully someone else will do it thou

Does a factory reset help (do I need to wait another 14days?) ?

I could run the oem unlock command in fastboot
No reset needed, just ignore the message ( LENOVO ID WITHOUT PERMISSION)

robuser007 said:
I could run the oem unlock command in fastboot
No reset needed, just ignore the message ( LENOVO ID WITHOUT PERMISSION)
Click to expand...
Click to collapse
Could you be kimd to post the command you used?

robuser007 said:
I could run the oem unlock command in fastboot
No reset needed, just ignore the message ( LENOVO ID WITHOUT PERMISSION)
Click to expand...
Click to collapse
I am having the LenovoID without permission issue but this is happening when trying to turn on allow OEM bootloader unlocking in the developer options and I believe this has to be turned on before the fastboot command will work.
When I try the fastboot command of fastboot OEM get_unlock_data to get the code I need to convert for the unlock code, it returns Not Found for all values.
I contacted sorry about this but they want talk about it because they don't 'support it', I sent them the link for getting the code converted (https://motorola-global-en-uk.custhelp.com/app/standalone/bootloader/unlock-your-device-b) and said if you don't support it why do you offer the service? And they said yes we provide the service but don't support it. . Asked who could give support on this and they said they don't know...
---------- Post added at 08:22 PM ---------- Previous post was at 07:47 PM ----------
I've just seen in another thread that the OTA servers are down because there is a new update coming so maybe these are on the same server and it will be up again soon.

AGAWhitty said:
I contacted sorry about this but they want talk about it because they don't 'support it', I sent them the link for getting the code converted (https://motorola-global-en-uk.custhelp.com/app/standalone/bootloader/unlock-your-device-b) and said if you don't support it why do you offer the service? And they said yes we provide the service but don't support it. . Asked who could give support on this and they said they don't know...
Click to expand...
Click to collapse
Sorry, but this is so funny. Because its sooo typical Lenovo service

Related

Device State - locked

I know there are other threads regarding this but those included someone having TWRP already flashed and in this case I do not.
I sadly took a chance and bought a Nexus 5X off someone on Kijiji and it looks like I got got scammed.
I've own other Nexus phones in the past but was unaware of the OEM Lock on the latest devices and it is in a locked state and I do not know the google account to unlock it (as it wasn't my phone prior to this)
None of the fastboot/adb commands work as it is locked.
I just wanted to know if there was any other way I could fix this or if I have brick on my hands here. Any assistance would be amazing as this would mean I just blew my money away.
N
sniperIT said:
I know there are other threads regarding this but those included someone having TWRP already flashed and in this case I do not.
I sadly took a chance and bought a Nexus 5X off someone on Kijiji and it looks like I got got scammed.
I've own other Nexus phones in the past but was unaware of the OEM Lock on the latest devices and it is in a locked state and I do not know the google account to unlock it (as it wasn't my phone prior to this)
None of the fastboot/adb commands work as it is locked.
I just wanted to know if there was any other way I could fix this or if I have brick on my hands here. Any assistance would be amazing as this would mean I just blew my money away.
N
Click to expand...
Click to collapse
So you purchased a 5X that wasn't factory reset? Have you tried asking the previous owner for assistance? They might be able to remotely wipe the phone using Android Device Manager.
metpage said:
So you purchased a 5X that wasn't factory reset? Have you tried asking the previous owner for assistance? They might be able to remotely wipe the phone using Android Device Manager.
Click to expand...
Click to collapse
It was reset and required login of the previous account to unlock it. Unfortunately, the previous owner is nowhere to be found...
The build number is MHC19J and I've been told that I am screwed to unlock it.
Nick
sniperIT said:
It was reset and required login of the previous account to unlock it. Unfortunately, the previous owner is nowhere to be found...
The build number is MHC19J and I've been told that I am screwed to unlock it.
Nick
Click to expand...
Click to collapse
I would try and get your money back, chances are you could have brought a stolen phone.
Darke5tShad0w said:
I would try and get your money back, chances are you could have brought a stolen phone.
Click to expand...
Click to collapse
Sadly you may be right, but like any good thief he seems to be unreachable, so I unfortunately can't get the money back. I have checked the IMEI and it is clean so i should be able to activate it.
I just need a way to bypass the FRP (Factory Reset Protection). I've seen posts on this on XDA but they are for patches up to the March 1st Patch. I build I have is the March Patch and I can't seem to find any workarounds for this patch level.
In the event that someone has found a way please let me know as it would save me a lot of grief.
Thank you for your responses.
N
sniperIT said:
Sadly you may be right, but like any good thief he seems to be unreachable, so I unfortunately can't get the money back. I have checked the IMEI and it is clean so i should be able to activate it.
I just need a way to bypass the FRP (Factory Reset Protection). I've seen posts on this on XDA but they are for patches up to the March 1st Patch. I build I have is the March Patch and I can't seem to find any workarounds for this patch level.
In the event that someone has found a way please let me know as it would save me a lot of grief.
Thank you for your responses.
N
Click to expand...
Click to collapse
I don't know if will help, but the N preview may not include or may reset FRP. Usually OTAs only include the changed files but since the N preview was bricking locked phones, Google released full OTAs that contained everything. You could try flashing it with ADB while in the stock recovery.
Sent from my Nexus 5X using Tapatalk
PiousInquisitor said:
I don't know if will help, but the N preview may not include or may reset FRP. Usually OTAs only include the changed files but since the N preview was bricking locked phones, Google released full OTAs that contained everything. You could try flashing it with ADB while in the stock recovery.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I was thinking the same thing but I don't want to make the situation worse than it already is. I have seen vids from RootJunky showing that the N preview is bypassable and it can be done with a reset.
Will the OTA wipe all the data on the device?
Just to be clear are these the OTA's you are referring too? http://developer.android.com/preview/download-ota.html
Thank you for your advice.
N
sniperIT said:
I was thinking the same thing but I don't want to make the situation worse than it already is. I have seen vids from RootJunky showing that the N preview is bypassable and it can be done with a reset.
Will the OTA wipe all the data on the device?
Just to be clear are these the OTA's you are referring too? http://developer.android.com/preview/download-ota.html
Thank you for your advice.
N
Click to expand...
Click to collapse
Those are the files. That is what I would do.
Sent from my Nexus 5X using Tapatalk
PiousInquisitor said:
Those are the files. That is what I would do.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Ok thank you very much I am in the process, will update once it is complete.
N
sniperIT said:
Ok thank you very much I am in the process, will update once it is complete.
N
Click to expand...
Click to collapse
Looks like it is still a no go. The FRP seems to still be in place and the reset idea didn't work.
I may need to see if i can get this phone completely blanked.
N
sniperIT said:
Looks like it is still a no go. The FRP seems to still be in place and the reset idea didn't work.
I may need to see if i can get this phone completely blanked.
N
Click to expand...
Click to collapse
I've got on last idea. Is it a 32 gig model?
Sent from my Nexus 5X using Tapatalk
PiousInquisitor said:
I've got on last idea. Is it a 32 gig model?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
16GB unfortunately.
sniperIT said:
16GB unfortunately.
Click to expand...
Click to collapse
Bummer. I was going to suggest THIS. But there isnt a 16 TOT file.
So you were able to successfully flash N from the stock recovery? And you simply couldnt get past the login screen? FRP is a *****. I had no idea what it was when I sold my Moto X Pure Edition last year. I ended up giving the guy I sold it to my password so he could unlock it. That was after about a day of searching for a workaround. Then my sis bought a G4 and when it arrived it was locked with FRP. We ended up finding a tool to wipe it out. Such a pain. Lol. Good luck finding a solution. Let us know if you get it working some other way.
---------- Post added at 10:41 PM ---------- Previous post was at 10:30 PM ----------
sniperIT said:
16GB unfortunately.
Click to expand...
Click to collapse
Have you tried this? EDIT: Looks like its been patched already...
https://www.youtube.com/watch?v=ocC7ruFCqOI
PiousInquisitor said:
Bummer. I was going to suggest THIS. But there isnt a 16 TOT file.
So you were able to successfully flash N from the stock recovery? And you simply couldnt get past the login screen? FRP is a *****. I had no idea what it was when I sold my Moto X Pure Edition last year. I ended up giving the guy I sold it to my password so he could unlock it. That was after about a day of searching for a workaround. Then my sis bought a G4 and when it arrived it was locked with FRP. We ended up finding a tool to wipe it out. Such a pain. Lol. Good luck finding a solution. Let us know if you get it working some other way.
---------- Post added at 10:41 PM ---------- Previous post was at 10:30 PM ----------
Have you tried this? EDIT: Looks like its been patched already...
https://www.youtube.com/watch?v=ocC7ruFCqOI
Click to expand...
Click to collapse
Man is it ever. The last thing I was thinking was that they say there is a 72 hour lock on this and I only first started the phone on Sat night. maybe I need to wait until tomorrow and see what happens.
I will check out the Youtube video.
Thank you for all your help once again.
N
sniperIT said:
Man is it ever. The last thing I was thinking was that they say there is a 72 hour lock on this and I only first started the phone on Sat night. maybe I need to wait until tomorrow and see what happens.
I will check out the Youtube video.
Thank you for all your help once again.
N
Click to expand...
Click to collapse
So were you able to reset the phone on N, like in the rootjunky video?
https://www.youtube.com/watch?v=nOymYg3lswI
PiousInquisitor said:
So were you able to reset the phone on N, like in the rootjunky video?
https://www.youtube.com/watch?v=nOymYg3lswI
Click to expand...
Click to collapse
I unfortunately don't have a sim to test with. The one in my current is a micro not a nano. I am going to contact a repair store tomorrow to see if they can assist and I will try it out.
Sorry yes I did exactly as he suggested and it didn't work.
It gives me the option during setup to setup like it was a new phone but then as soon as I connect to my WiFi it performs a check and states the same reset message.
Which is why I might be thinking that it is the 72 hour lock on and maybe it will go away once it is complete.
N
sniperIT said:
I unfortunately don't have a sim to test with. The one in my current is a micro not a nano. I am going to contact a repair store tomorrow to see if they can assist and I will try it out.
Sorry yes I did exactly as he suggested and it didn't work.
It gives me the option during setup to setup like it was a new phone but then as soon as I connect to my WiFi it performs a check and states the same reset message.
Which is why I might be thinking that it is the 72 hour lock on and maybe it will go away once it is complete.
N
Click to expand...
Click to collapse
I would try it again. If you factory reset from within android, it should disable FRP, including the need to wait 72 hrs.
I wouldn't bother with the repair shop. The latest and greatest info is going to be on the internet and probably from rootjunky.
PiousInquisitor said:
I would try it again. If you factory reset from within android, it should disable FRP, including the need to wait 72 hrs.
I wouldn't bother with the repair shop. The latest and greatest info is going to be on the internet and probably from rootjunky.
Click to expand...
Click to collapse
I tried several times with no luck.
It just seems like once it phones home to Google it blocks me.
I'm going to try to contact rootjunky directly
sniperIT said:
I tried several times with no luck.
It just seems like once it phones home to Google it blocks me.
I'm going to try to contact rootjunky directly
Click to expand...
Click to collapse
Bummer. Im out of ideas.
What message do you exactly get when trying to execute something via fastboot?

Do I really have to wait 7 days for OEM unlock to appear?

I just got this S9+ today and I cannot find OEM unlock under Developer Options. I read that the only way is to wait 7 days and then it will appear. Is that true?
Yes as long as it is a Exynos S9, Snapdragon will never appear
Sick of Qualcomms locked bootloaders. I had to deal with this on the S7, S8, and S9. Think I may be finished with the Galaxy.
zzEvilGeniuszz said:
Sick of Qualcomms locked bootloaders. I had to deal with this on the S7, S8, and S9. Think I may be finished with the Galaxy.
Click to expand...
Click to collapse
Buy Exynos instead?
2 things:
1) there absolutely are unlockable Snapdragons. Only the US and Canada have perm locked ones. Don't believe the hype.
2) you might be able to skip ahead on the lock, but it doesn't always work and I think later firmware blocks it. It worked for me once but not the second time. It's a lot more likely to work if you don't have RMM status: Prenormal. Search xda to find out what that means if you don't know.
As for skipping the wait, there was an xda article about it this week or last week, should be easy to find. Also, if you have RMM status: normal (you see nothing about RMM in download mode) you can just flash the combination rom for your device and it's oem unlock it's always there. Doesn't work with Prenormal though
@partcyborg Unfortunately, mine says pre-normal so I am forced to wait the 7 days. I came back to Liverpool two days ago and I had over 60 hours of uptime by then, but as soon as I inserted my Three UK sim card, I got a notification and was basically forced to reboot my device. I tried everything I can to try and dismiss that pop-up but I couldn't. The uptime was reset and now I have 22 hours which is extremely frustrating. Do you think the reboot messed things up or could it actually be counting from the 60+ hours it already had?
There is a thread on the forums that says you can change the date or something like that to "trick" it into thinking you have had it the 7 days... I don't know for sure if it works because I have a US T-mobile version, just figured I'd share what I came across...
TarekElsakka said:
@partcyborg Unfortunately, mine says pre-normal so I am forced to wait the 7 days. I came back to Liverpool two days ago and I had over 60 hours of uptime by then, but as soon as I inserted my Three UK sim card, I got a notification and was basically forced to reboot my device. I tried everything I can to try and dismiss that pop-up but I couldn't. The uptime was reset and now I have 22 hours which is extremely frustrating. Do you think the reboot messed things up or could it actually be counting from the 60+ hours it already had?
Click to expand...
Click to collapse
Rebooting does not reset the 7d counter. All reports of that being a thing are fake news. You are fine
jflow36 said:
There is a thread on the forums that says you can change the date or something like that to "trick" it into thinking you have had it the 7 days... I don't know for sure if it works because I have a US T-mobile version, just figured I'd share what I came across...
Click to expand...
Click to collapse
This worked for me one time but not the second. Definitely worth trying
partcyborg said:
Rebooting does not reset the 7d counter. All reports of that being a thing are fake news. You are fine
Click to expand...
Click to collapse
You were right. Someone on reddit also told me the same thing when I first purchased the phone and although the uptime was reset after I rebooted the device, OEM unlock showed up exactly 7 days later regardless so that was great!
partcyborg said:
2 things:
1) there absolutely are unlockable Snapdragons. Only the US and Canada have perm locked ones. Don't believe the hype.
2) you might be able to skip ahead on the lock, but it doesn't always work and I think later firmware blocks it. It worked for me once but not the second time. It's a lot more likely to work if you don't have RMM status: Prenormal. Search xda to find out what that means if you don't know.
As for skipping the wait, there was an xda article about it this week or last week, should be easy to find. Also, if you have RMM status: normal (you see nothing about RMM in download mode) you can just flash the combination rom for your device and it's oem unlock it's always there. Doesn't work with Prenormal though
Click to expand...
Click to collapse
How Do I can see my status if its normal or prrnormal?
Regikitten said:
How Do I can see my status if its normal or prrnormal?
Click to expand...
Click to collapse
Does oem unlock show up in developer options?
Regikitten said:
How Do I can see my status if its normal or prrnormal?
Click to expand...
Click to collapse
Download mode
partcyborg said:
Does oem unlock show up in developer options?
Click to expand...
Click to collapse
No
---------- Post added at 10:10 AM ---------- Previous post was at 10:08 AM ----------
*Detection* said:
Download mode
Click to expand...
Click to collapse
And if I try to do it How I get out of download mode
Ps: Sorry my English, I'm Brasilian
Regikitten said:
No
---------- Post added at 10:10 AM ---------- Previous post was at 10:08 AM ----------
And if I try to do it How I get out of download mode
Ps: Sorry my English, I'm Brasilian
Click to expand...
Click to collapse
Then it's prenormal
Regikitten said:
No
---------- Post added at 10:10 AM ---------- Previous post was at 10:08 AM ----------
And if I try to do it How I get out of download mode
Ps: Sorry my English, I'm Brasilian
Click to expand...
Click to collapse
Hold volume down & power
partcyborg said:
Rebooting does not reset the 7d counter. All reports of that being a thing are fake news. You are fine
Click to expand...
Click to collapse
@partcyborg, what about SIM card, is that required, or another myth?
Just got a SM-G9600 (TPA/Panama). I don't have any SIM in it, and waiting for 7 days to get out of prenormal. Had to take the August RH4, which must have included BL update as I couldn't odin back to July RF4.
Btw, the date bypass trick didn't work for me, either before the update or afterward. I'm curious how Samsung keeps track of the 7 days. If it's solely on the phone, then the date trick would have worked; they probably moved it to server side somehow (I watched my network traffic when doing the manual update, but should have done it earlier when enabling the dev options).

Current Account Can not unlock this device error

Hey I am getting this error Current Account Cannot unlock this device everytime i try to unlock my Redmi 5A. I have tried every method mentioned on internet but still the same result. I contacted customer care and they said they had no solution. Someone please help me. Any method will do. I just want to unlock my phone at all costs. I'm even willing to pay for unlocking my device's bootloader. For the love of god someone plz help cause I'm at my wit's end now.
P.S. Don't try to tell me to follow method by @xcaanz because i dont know low lev prog language and there is no clear tutorial for that.
Device Specs: Redmi 5A -2, 16. Current Rom- MIUI 10 beta( 8.9.20) but i've tried to unlock on MIUI global stable 9.5 as well as 9.6.
I'm sorry it's xaacnz not xcaanz.
You have to register your xiaomi account for unlocking at http://en.miui.com/unlock/. The error you are getting means you are not registered.
oddhap said:
You have to register your xiaomi account for unlocking at http://en.miui.com/unlock/. The error you are getting means you are not registered.
Click to expand...
Click to collapse
I have already done that. No matter what i try i get the same error.
just stupid questions... i have read all of your posts and see you have read everything and tried everything. but its not absolutely clear... did you receive SMS confirmation? did you click on Find device and located your phone? did you solve the previous error 86012 cannot bind account? did you check the driver is shown as Xiaomi Corp? have you tried another usb cable or switched the port? tried with older version of Mi unlock tool? Developer options OEM unlocking box still greyed out at any time?
(just answer with yes, yes, yes)
---------- Post added at 22:27 ---------- Previous post was at 22:09 ----------
just some google results.. some of this (more ore less) claims there is a waiting period (hours .. days ..) which will increase.
https://forum.xda-developers.com/showthread.php?t=3565459
https://forum.xda-developers.com/showthread.php?t=3608650
http://en.miui.com/thread-1394024-1-1.html
http://xiaomitips.com/guide/how-to-fix-couldnt-verify-device-error-during-bootloader-unlock-process
https://www.allaboutxiaomi.com/unlock-bootloader-redmi-xiaomi-device
aIecxs said:
just stupid questions... i have read all of your posts and see you have read everything and tried everything. but its not absolutely clear... did you receive SMS confirmation? did you click on Find device and located your phone? did you solve the previous error 86012 cannot bind account? did you check the driver is shown as Xiaomi Corp? have you tried another usb cable or switched the port? tried with older version of Mi unlock tool? Developer options OEM unlocking box still greyed out at any time?
(just answer with yes, yes, yes)
---------- Post added at 22:27 ---------- Previous post was at 22:09 ----------
just some google results.. some of this (more ore less) claims there is a waiting period (hours .. days ..) which will increase.
https://forum.xda-developers.com/showthread.php?t=3565459
https://forum.xda-developers.com/showthread.php?t=3608650
http://en.miui.com/thread-1394024-1-1.html
http://xiaomitips.com/guide/how-to-fix-couldnt-verify-device-error-during-bootloader-unlock-process
https://www.allaboutxiaomi.com/unlock-bootloader-redmi-xiaomi-device
Click to expand...
Click to collapse
First- The process to apply is now simplified, so we no longer have to give a reason for unlocking on mi.com/unlock and it doesn't send u an SMS confirmation now. U just get the waiting time on mi unlock tool. Here is the thread-
http://en.miui.com/thread-246705-1-1.html
I get directed to download page directly after filling in my login credentials.
Yes, i clicked on find device and my device was located.
As for the error 86012, i have tried Plex VPN and many other VPNs and set the server to Hong Kong/ China but it did not work. Later i read on XDA that u can unlock even with error 86012.
Yes indeed. Checked that just now and the driver is shown as Xiaomi Corp.
No, I haven't tried another USB cable.
When i try with older version of Xiaomi unlock i can not login as it gives network error everytime.
No OEM unlock is not greyed out.
Hope u can help me now.
Thank you for this information, this link is the most useful from all the stuff i have read so far. Didn't know that no sms confirmation is required.
So, what happens if you enable OEM unlocking in Developer Options and then unlock in fastboot mode?
Code:
fastboot oem unlock
aIecxs said:
Thank you for this information, this link is the most useful from all the stuff i have read so far. Didn't know that no sms confirmation is required.
So, what happens if you enable OEM unlocking in Developer Options and then unlock in fastboot mode?
Code:
fastboot oem unlock
Click to expand...
Click to collapse
I'll give it a shot but i have read that it gives some sort of error.
Anyways thnx for ur time
In your Link, they mentioned a logfile /sdcard/MIUI/debug_log/*.zip, can you share this? see ...
Steps to reproduce the error: iv. Once the error message is shown, head towards dialer and dial *#*#284#*#*
Found a comment on this Video, maybe thats the reason for not working?
http://www.youtube.com/watch?v=AE4JhUbZ_LQ
"You need the original firmware that your phone is supposed to be shipped with to unlock the bootloader. If your device is a Chinese model it needs the China ROM, if it's the Global model it needs the Global ROM." (ChinaMobileMag)
aIecxs said:
Found a comment on this Video, maybe thats the reason for not working?
http://www.youtube.com/watch?v=AE4JhUbZ_LQ
"You need the original firmware that your phone is supposed to be shipped with to unlock the bootloader. If your device is a Chinese model it needs the China ROM, if it's the Global model it needs the Global ROM." (ChinaMobileMag)
Click to expand...
Click to collapse
My device is global version and i have MIUI 10 Global dev at present but I also tried unlocking at MIUI 9.5 which is the version Riva was shipped with. The result was still the same. Seriously idk what to do anymore. And yeah regarding that bug report, i gave not tried unlocking after i got the error Couldn't verify. I'll try once again to check if i'm getting some other error this time on unlock tool. But at present i don't have my Laptop so it might take a day or two. If u need the bug reoprt sooner do tell me. I'll upload it right away( I guess there's no point clinging to a small ray of hope now). Anyways thanks mate!!
aIecxs said:
In your Link, they mentioned a logfile /sdcard/MIUI/debug_log/*.zip, can you share this? see ...
Steps to reproduce the error: iv. Once the error message is shown, head towards dialer and dial *#*#284#*#*
Click to expand...
Click to collapse
Here's the bug report. I tried using command fastboot oem unlock again but it didn't work.
the logfile says CloudDeviceStatus stateCode 200 "ok" which means it has a successful connection to server, but then gives error device not found code 86012 description "设备不存在".
this may have different reasons (but i am not that expert):
a) the data on server is deleted - server fault?
b) access denied - account fault?
c) the device-id (or whatever they submit) election is empty or invalid - rom issue?
d) account is not binded to device?
Is this phone brand-new, do you still remember all accounts used from this device? Log-in to every single account and delete all binded devices, then use the very first account only. For my understanding only one account can be granted permission. Just try over and over again after 15 days - sorry i can not help
aIecxs said:
the logfile says CloudDeviceStatus stateCode 200 "ok" which means it has a successful connection to server, but then gives error device not found code 86012 description "设备不存在".
this may have different reasons (but i am not that expert):
a) the data on server is deleted - server fault?
b) access denied - account fault?
c) the device-id (or whatever they submit) election is empty or invalid - rom issue?
d) account is not binded to device?
Is this phone brand-new, do you still remember all accounts used from this device? Log-in to every single account and delete all binded devices, then use the very first account only. For my understanding only one account can be granted permission. Just try over and over again after 15 days - sorry i can not help
Click to expand...
Click to collapse
Bought the phone in August 2018. The account that im trying to unlock with is the acc. I created in this phone.
Thnx mate for ur help. I can not thank u enough for what u have done. Prior to this also i had created threads in MI community, asked for help in via posts in XDA thread but no one gave a damn about my problem. Thnx again for at least digging this deep in the problem.
You can send a email to customer support with subject unlocking: 设备不存在 and attach the filtered log file from my post - or even post this error again. You are clearly not the only one, this is a common problem. You can search in chinese forums, too. Please keep this thread updated, it will be helpful for others. I am facing this problem too, my son has Redmi 5a and i failed unlocking bootloader so the phone never was rooted, therefore has no TWRP and in case the screen will brake i don't know how to rescue data... at the moment for him best solution is "never touch a running system" and @xaacnz 's method is high risk for bricking we should better not try with daily driver
edit: post it on youtube channel too, or send a private message with invitation to your xda thread
http://www.youtube.com/watch?v=CiciDJfzlB8
aIecxs said:
You can send a email to customer support with subject unlocking: 设备不存在 and attach the filtered log file from my post - or even post this error again. You are clearly not the only one, this is a common problem. You can search in chinese forums, too. Please keep this thread updated, it will be helpful for others. I am facing this problem too, my son has Redmi 5a and i failed unlocking bootloader so the phone never was rooted, therefore has no TWRP and in case the screen will brake i don't know how to rescue data... at the moment for him best solution is "never touch a running system" and @xaacnz 's method is high risk for bricking we should better not try with daily driver
edit: post it on youtube channel too, or send a private message with invitation to your xda thread
http://www.youtube.com/watch?v=CiciDJfzlB8
Click to expand...
Click to collapse
Ok I will. Btw bout that yt channel, I just have to add a comment right? I'll create another thread on Mi forums about this problem. It really sucks not being able to unlock bootloader. TBH the only reason i bought this phone was because on searching the forums I found that this was the only device in my budget that had this many cusroms and other mods. I really am disappointed at how it turned out.
Hope we can find a solution soon!
aIecxs said:
Found a comment on this Video, maybe thats the reason for not working?
http://www.youtube.com/watch?v=AE4JhUbZ_LQ
"You need the original firmware that your phone is supposed to be shipped with to unlock the bootloader. If your device is a Chinese model it needs the China ROM, if it's the Global model it needs the Global ROM." (ChinaMobileMag)
Click to expand...
Click to collapse
"avoid flashing any firmware or any MIUI ROM which is older than what you're using now otherwise you'll brick your device"
[FAQ][Anti-Rollback] All your questions are answered here
aIecxs said:
"avoid flashing any firmware or any MIUI ROM which is older than what you're using now otherwise you'll brick your device"
[FAQ][Anti-Rollback] All your questions are answered here
Click to expand...
Click to collapse
Anti rollback is not related to this error. But i have tried with latest version of MIUI beta -8.9.20. It did not work. Also tried it on the latest global stable. Still no result.
Just heard that Riva has started receiving Oreo in china devepoper which means it will come to global very soon. I can only hope that this issue of "Current........this device" gets resolved after this major update. Fingers crossed.:fingers-crossed:
adityam0338 said:
Just heard that Riva has started receiving Oreo in china devepoper which means it will come to global very soon. I can only hope that this issue of "Current........this device" gets resolved after this major update. Fingers crossed.:fingers-crossed:
Click to expand...
Click to collapse
I strongly believe that you need to wait for a month at least before you can unlock your Redmi 5A again(unless you have done something that Xiaomi decided to lock it for good). I accidentally locked my bootloader after doing a"flash and lock" on the MIUI DEV rom, then unlocked 2nd time after 32+ days, while on the DEV Rom

How do I root my device? (Galaxy J2 SM-J260T1)

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.

10.0.4 T-Mobile update incoming......

Looks like T-Mobile released 10.0.4 Today ??
KMHartford said:
Looks like T-Mobile released 10.0.4 Today ??
Click to expand...
Click to collapse
Nice!! Updating Now
STOP!
DONT TAKE THE UPDATE BEFORE DOING THIS.
I ****ed up and forgot to do a logcat! That will get us the link address for the software update.
Please do these steps before taking that update
So the link won't let me post from thecustom Droid
https://www.cyanogenmods.org/how-to-capture-ota-android-update-url/
Long story sort. Install termux or Android terminal. Type in logcat. Go back to system updates and click install. Wait a few seconds and then click airplane mode or cancel to stop download. Go back to the terminal and find what url the OTA was coming from
Are you guys rooted? My OTA keeps failing , won't even download.
Josh McGrath said:
Are you guys rooted? My OTA keeps failing , won't even download.
Click to expand...
Click to collapse
No root here, can't do anything until the Tool is ready for the T-Mobile 7T or I'm able pay it off then T-Mobile Twitter will unlock, then I can proceed with the unlock token process from OnePlus.... I was able to download the ota and install, no issues.....
zeusofyork said:
STOP!
DONT TAKE THE UPDATE BEFORE DOING THIS.
I ****ed up and forgot to do a logcat! That will get us the link address for the software update.
Please do these steps before taking that update
So the link won't let me post from thecustom Droid
https://www.cyanogenmods.org/how-to-capture-ota-android-update-url/
Long story sort. Install termux or Android terminal. Type in logcat. Go back to system updates and click install. Wait a few seconds and then click airplane mode or cancel to stop download. Go back to the terminal and find what url the OTA was coming from
Click to expand...
Click to collapse
Damn too bad I didn't see this I would've done it, but I already updated ?
augoza said:
Damn too bad I didn't see this I would've done it, but I already updated ?
Click to expand...
Click to collapse
No worries another person snagged it
Does anyone have a stock or modified boot img for our model? I am bricked at bootloader unlock screen and just spent two hours yelling at those idiots at OnePlus cause they are inept and no help. It's like they don't acknowledge our device exists and the software created itself.
same here I had my modem mismatched no signal and data, wifi too, but it boots. They tried to remote fix it, but they don't have the tmobile firmware yet, only O2 and india.
---------- Post added at 07:24 AM ---------- Previous post was at 07:23 AM ----------
can anyone maybe sent us the modem image or boot image on the 10.0.3? if there's any
imna357 said:
same here I had my modem mismatched no signal and data, wifi too, but it boots. They tried to remote fix it, but they don't have the tmobile firmware yet, only O2 and india.
---------- Post added at 07:24 AM ---------- Previous post was at 07:23 AM ----------
can anyone maybe sent us the modem image or boot image on the 10.0.3? if there's any
Click to expand...
Click to collapse
You can fastboot boot the x.3 and the x.4 I found out while trying to fix my phone. But WiFi doesn't work and who knows what else.
I have the OTA and tried pulling the boot img but it was 6am and I wanted to go to sleep.
Honestly just call and exchange your tmo 7t, just bite the bullet cause one plus is worthless.
I do highly recommend you call and be very angry about them not having the software. We all need to complain enough so they get their ass in gear
Josh McGrath said:
You can fastboot boot the x.3 and the x.4 I found out while trying to fix my phone. But WiFi doesn't work and who knows what else.
I have the OTA and tried pulling the boot img but it was 6am and I wanted to go to sleep.
Honestly just call and exchange your tmo 7t, just bite the bullet cause one plus is worthless.
I do highly recommend you call and be very angry about them not having the software. We all need to complain enough so they get their ass in gear
Click to expand...
Click to collapse
Exchanging it is easy, but having it sim unlock is hard, I did call 4 times and chatted can't count just to have the phone sim unlock, well I just have to wait for the conversion if there's any if not maybe a month from now I'll just have to claim an insurance=):laugh:
imna357 said:
Exchanging it is easy, but having it sim unlock is hard, I did call 4 times and chatted can't count just to have the phone sim unlock, well I just have to wait for the conversion if there's any if not maybe a month from now I'll just have to claim an insurance=):laugh:
Click to expand...
Click to collapse
Man that is crazy cause they sim unlocked mine after 2 days.
You just reminded me that I have to fricking wait a week for the unlock token again .
I might have to start working on the msm tool out of spite cause I'm so pissed at OP right now
Maybe if there was MSM thats patched maybe this phone will boot up, tried pressing all the buttons, but nothing, bootloader will not show up. Tried the MSM tool for international and the phone gets recognized, when I press start its a mismatched=)
I am back, got the replacement last night and chatted with CSR, now I am SIM UNLOCK again, will wait next wednesday for unlock.bin=)
imna357 said:
I am back, got the replacement last night and chatted with CSR, now I am SIM UNLOCK again, will wait next wednesday for unlock.bin=)
Click to expand...
Click to collapse
Exact same story here and probably just as pissed that we have to wait another 7 days
OnePlus has "escalated" my customer service complaint about them not having the software, which of course we all know means absolutely nothing.
Josh McGrath said:
Exact same story here and probably just as pissed that we have to wait another 7 days
OnePlus has "escalated" my customer service complaint about them not having the software, which of course we all know means absolutely nothing.
Click to expand...
Click to collapse
Cool will wait for it, before messing with my phone again
imna357 said:
Cool will wait for it, before messing with my phone again
Click to expand...
Click to collapse
You'd be alright if you just root and not flash anything else lol
Mine died thanks to magisk while trying to unroot ?
Josh McGrath said:
You'd be alright if you just root and not flash anything else lol
Mine died thanks to magisk while trying to unroot ?
Click to expand...
Click to collapse
Just being adventurous, I got warranty no fee courtesy of my FILIPINO call agents?

Categories

Resources