Unlocked BL succesfully but cannot activate phone after reboot - Xiaomi Redmi Note 7 Pro Questions & Answers

As title, after succesfull BL unlock, after reboot, it is asking for my MI acct password. But it wont accept the correct PW! Why is that and how do I get my phone working?
Thanks.
edit: fixed. apparently wasnt connecting to network properly. All well now.

Related

Tips/Help with Network/SIM Unlock Problem

EDIT: Nevermind, I called ATT to double check and they gave me a different code that worked. Sorry for the post.
I know this gets asked alot, but the information, situations, and answers out there are so many it is difficult to determine what needs to be done, so I am hoping someone can at least point me in the right direction.
I had unlocked my bootloader using htcdev, installed 4ext recovery, and flashed latest Cyanogenmod. I have been wanting to switch to T-mobile (I know about the possibility of not having 4g with that) and come to find out, entering the Network PUK code doesnt work in Cyanogen..
I gleaned that I needed to re-flash stock rom and then try to unlock, but I did this, and it still isnt accepting the code, argh. Do I need to relock my bootloader or do anything special? I got this code straight from ATT. With the ATT SIM in the phone, it doesnt ask for it, I restart phone with my T-mobile SIM in, and it asks for the code, but always says its incorrect. How is it checking this anyway, as it doenst seem to be communicating over the mobile network.
Any ideas would be much appreciated, thanks.

How to check if your Sprint n920p has domestic gsm unlock or not

Greetings,
I have unlocked my Note 5 a while ago and it all worked fine. After some flashing, however, my SIM wont be recognized anymore. Tried everything even reverting to STOCK ROM via Odin but the SIM just wont register. (The APN-Settings are still read correctly though so the Reader should be fine).
I now assume that the SIM Unlock somehow was lost during flashing? Is that possible? How can I check wether or not my device still has the unlock? Should I request unlock service again and if yes, where?
Greetings
Ravensysteam said:
Greetings,
I have unlocked my Note 5 a while ago and it all worked fine. After some flashing, however, my SIM wont be recognized anymore. Tried everything even reverting to STOCK ROM via Odin but the SIM just wont register. (The APN-Settings are still read correctly though so the Reader should be fine).
I now assume that the SIM Unlock somehow was lost during flashing? Is that possible? How can I check wether or not my device still has the unlock? Should I request unlock service again and if yes, where?
Greetings
Click to expand...
Click to collapse
I used idone apps to unlock mine. After flashing a note 7 rom. Mine locked up again. And idone team. Stated that my android id had changed. And they updated there system re applied the unlock and good to go. It has been known that some rom flashes will undo unlock. Idone cost $30 American. Little pricey but worth it
THIS solved the problem https://forum.xda-developers.com/sp...al/fix-signal-update-flash-to-6-0-mm-t3345709
Ravensysteam said:
Greetings,
I have unlocked my Note 5 a while ago and it all worked fine. After some flashing, however, my SIM wont be recognized anymore. Tried everything even reverting to STOCK ROM via Odin but the SIM just wont register. (The APN-Settings are still read correctly though so the Reader should be fine).
I now assume that the SIM Unlock somehow was lost during flashing? Is that possible? How can I check wether or not my device still has the unlock? Should I request unlock service again and if yes, where?
Greetings
Click to expand...
Click to collapse
Was your unlock service made by software or direct unlock via sprint?
Edit:
Nevermind, saw your last post.
Edit2: Cool, that's the thread I made.

Verizon Unlock?

Is there still no method to unlock the Verizon Pixel? Running 7.1.2
mackentosh said:
Is there still no method to unlock the Verizon Pixel? Running 7.1.2
Click to expand...
Click to collapse
NO. Not right now. Probably never.
A lot of people are reporting that the latest VZ Pixel shipments can be unlocked using adb. Search around, consider an RMA.
I literally just got my Pixel today. Ordered it from an authorized retailer here on the NEX in the naval base and it came with 7.1.1
To my surprise, the OEM unlock switch in Developer options wasn't greyed out, so I followed the instructions, unlocked the bootloader, took the update to 7.1.2 (bootloader still unlocked) and flashed TWRP and verifiedsigner (because the new 7.1.2 bootloader requires a signed recovery smh).
I think the new shipments of Pixels from Verizon are all from Google now.
Just had Asurion warranty replace the phone I bought from Verizon. I got my replacement last week (original phone had the hairline crack in the microphone, a known issue). Unfortunately, my phone I received had the 7.1.1 April build AND OEM unlock is greyed out in developer options. So I wasn't lucky enough to get a replacement from Google but from Verizon.
---------- Post added at 02:43 PM ---------- Previous post was at 02:40 PM ----------
w0rdie said:
A lot of people are reporting that the latest VZ Pixel shipments can be unlocked using adb. Search around, consider an RMA.
Click to expand...
Click to collapse
This sounds incorrect. Before the 7.1.1 update from Verizon, yes, you could do this using the dePixel8 utility which works off of adb. You would adb push the file to system, chmod it and execute it.
I just did a search and there's no new adb method that will work if your phone is from Verizon AND has 7.1.x on it.
So here's the deal, remove the sim before you boot it, then update to 7.1.2 without the sim, OEM unlock will not be greyed out then I just ran fastboot OEM unlock command and it unlocked the bl. I work at Verizon and have tried it on 4 phones out of the box. Something with the sim locks the bl permanently
Are you serious?
seshaz said:
So here's the deal, remove the sim before you boot it, then update to 7.1.2 without the sim, OEM unlock will not be greyed out then I just ran fastboot OEM unlock command and it unlocked the bl. I work at Verizon and have tried it on 4 phones out of the box. Something with the sim locks the bl permanently
Click to expand...
Click to collapse
This almost sounds too good to be true. If this is for real then you should start your own thread and shout it from a mountaintop.
I didn't find it, people were talking about it In another thread.
I work for Verizon and have tried it on a few phones, I remove the sim and do the update and every time it let's you OEM unlock
So do you think factory reset, update to newer monthly os/android o while keeping the sim out will do the trick as well?
con4n007 said:
So do you think factory reset, update to newer monthly os/android o while keeping the sim out will do the trick as well?
Click to expand...
Click to collapse
nobody could say it should or shouldn't without trying it. if you have to go back from android o to 7.1.2 though, it will factory reset your phone so consider making a backup.
Really!?!?
I am able to unlock my Pixel XL 32GB from Verizon, below is my fumbling around. Maybe this helps others, maybe I got dumb luck.
Bought phone at Verizon (Had to activate in store with 1 month pre-paid)
Phone powered on at Verizon store with sim in
As soon as the phone made it to the setup screen sim was removed
Fi sim was put in
Rebooted
Accidentally skipped through setup (I didn't know by saying don't use internet connection it would not allow the transfer of files)
Attempted to activate phone with Fi sim
Cannot activate due to v1 of the Fi sim (Error B034)
Factory default (Wanted to copy everything from N6 over)
Copied N6 files over, setup phone (Google account, wifi, apps, etc)
Received 7.1.2 update
Updated phone, rebooted
Tapped to enable dev options
Slider to enable oem unlocking
Checked CID, shows VZW_001
Enabled USB debugging
adb reboot-bootloader
fastboot oem unlock
From here I chose not to click yes to unlock as I just setup the phone, but can later for science if there is doubt. I am currently waiting for my new Fi sim to show.
gubarz said:
I am able to unlock my Pixel XL 32GB from Verizon, below is my fumbling around. Maybe this helps others, maybe I got dumb luck.
Bought phone at Verizon (Had to activate in store with 1 month pre-paid)
Phone powered on at Verizon store with sim in
As soon as the phone made it to the setup screen sim was removed
Fi sim was put in
Rebooted
Accidentally skipped through setup (I didn't know by saying don't use internet connection it would not allow the transfer of files)
Attempted to activate phone with Fi sim
Cannot activate due to v1 of the Fi sim (Error B034)
Factory default (Wanted to copy everything from N6 over)
Copied N6 files over, setup phone (Google account, wifi, apps, etc)
Received 7.1.2 update
Updated phone, rebooted
Tapped to enable dev options
Slider to enable oem unlocking
Checked CID, shows VZW_001
Enabled USB debugging
adb reboot-bootloader
fastboot oem unlock
From here I chose not to click yes to unlock as I just setup the phone, but can later for science if there is doubt. I am currently waiting for my new Fi sim to show.
Click to expand...
Click to collapse
You received the update without the verizon sim in, using wifi I assume?
Yes WiFi was connected
gubarz said:
I am able to unlock my Pixel XL 32GB from Verizon, below is my fumbling around. Maybe this helps others, maybe I got dumb luck.
Bought phone at Verizon (Had to activate in store with 1 month pre-paid)
Phone powered on at Verizon store with sim in
As soon as the phone made it to the setup screen sim was removed
Fi sim was put in
Rebooted
Accidentally skipped through setup (I didn't know by saying don't use internet connection it would not allow the transfer of files)
Attempted to activate phone with Fi sim
Cannot activate due to v1 of the Fi sim (Error B034)
Factory default (Wanted to copy everything from N6 over)
Copied N6 files over, setup phone (Google account, wifi, apps, etc)
Received 7.1.2 update
Updated phone, rebooted
Tapped to enable dev options
Slider to enable oem unlocking
Checked CID, shows VZW_001
Enabled USB debugging
adb reboot-bootloader
fastboot oem unlock
From here I chose not to click yes to unlock as I just setup the phone, but can later for science if there is doubt. I am currently waiting for my new Fi sim to show.
Click to expand...
Click to collapse
Do I need a Fi sim for that, I'm not from US and using a local provider sim. I'm on 7.1.2 and have tried to factory reset it once but still get oem unlock greyed.
So if I just wait for the latest update to come out and then I update via wifi only and no sim I can then unlock the phone? Or does it mean that because I'm on O if I just remove the sim I can unlock or something? This would be amazing. I know I'm probably wrong but still...
cntryby429 said:
This almost sounds too good to be true. If this is for real then you should start your own thread and shout it from a mountaintop.
Click to expand...
Click to collapse
I bought my phone from Verizon and took the SIM out before turning it on. I went through the setup without connecting to WiFi or setting up an account. After that I opened settings and my Verizon device was running 7.1.1 February patch I believe. I enabled developer options and my OEM unlock switch wasn't greyed out. I flipped it and connected my device to my PC and rebooted it to the bootloader through ADB. I issues 'fastboot oem unlock' and the device unlocked without dePixel8 despite being a Verizon device. Its true, the SIM determines its gender.
beez1717 said:
So if I just wait for the latest update to come out and then I update via wifi only and no sim I can then unlock the phone? Or does it mean that because I'm on O if I just remove the sim I can unlock or something? This would be amazing. I know I'm probably wrong but still...
Click to expand...
Click to collapse
Perhaps. Won't know until a new update comes out. Either it will remember what it is and stay grayed out or it will do another check and enable it if not a Verizon sim.
I think it's long shot but let's hope.
This is all assuming that it is the sim that determines the lock status lol

Unlock Samsung Galaxy S6 SM-G920W8

Hello,
I have an issue with my phone. It was previously working fine and it was unlocked. The battery died and when I turned it back on after charging, the phone now seems to be locked. It asks me a SIM unlock PIN. I contacted the original carrier to get the SIM unlock PIN but the code they gave me is not working. I get " Unlock Network request unsuccesful". I did a factory reset and it's not working either.
I don't know what to do...
I saw a post on here talking about using a lite rom but I don't know if it'll work with my s6.
Thank you for your help

Samsung S7 Custom binary blocked by FRP Lock

I got S7 SM-G930L with a port Rom from S8 (https://forum.xda-developers.com/s7-edge/development/rom-s8-port-s7-s7-edge-ambasadii-t3619548). When I power on the phone I get a message: Custom binary blocked by FRP Lock.
I would like to get rid of the FRP Lock without losing my data.
I saw a video https://www.youtube.com/watch?v=VdAhu45UPsU According to the comments 40% lost their data and 60% didn't.
Could you please advise how to make sure that my data won't be lost?
Blackion said:
I got S7 SM-G930L with a port Rom from S8 (https://forum.xda-developers.com/s7-edge/development/rom-s8-port-s7-s7-edge-ambasadii-t3619548). When I power on the phone I get a message: Custom binary blocked by FRP Lock.
I would like to get rid of the FRP Lock without losing my data.
I saw a video https://www.youtube.com/watch?v=VdAhu45UPsU According to the comments 40% lost their data and 60% didn't.
Could you please advise how to make sure that my data won't be lost?
Click to expand...
Click to collapse
If there's an option for OEM Unlock in developer settings enable that to disable FRP
But how do I boot my phone? Now I'm getting a red message: Custom binary blocked by FRP Lock and the phone is not booting past that. It will not even let me in TWRP.
Blackion said:
But how do I boot my phone? Now I'm getting a red message: Custom binary blocked by FRP Lock and the phone is not booting past that. It will not even let me in TWRP.
Click to expand...
Click to collapse
reflash the stock fw using odin
Not sure
I was said that because I'm using a port of S8 on S7, after I'll reflash stock ROM the data might be lost due to differences of memory formats.
Is it true?
Blackion said:
I was said that because I'm using a port of S8 on S7, after I'll reflash stock ROM the data might be lost due to differences of memory formats.
Is it true?
Click to expand...
Click to collapse
If you haven't backed up your data, it will be lost.
When you get yourself back out of this mess, don't touch that OEM unlock toggle again...
Blackion said:
But how do I boot my phone? Now I'm getting a red message: Custom binary blocked by FRP Lock and the phone is not booting past that. It will not even let me in TWRP.
Click to expand...
Click to collapse
(sorry for the english but i'm italian) hi. i have the same problem, can you help me? i root my phone and after i unroot, but now the phone don't boot, it say custom binary blocked by frp, i understand that my bootloader is lock by oem, there is a way to unlock by odin or others method? i can't have access to recovery and the phone don't boot, what can i do?
corvasce03 said:
(sorry for the english but i'm italian) hi. i have the same problem, can you help me? i root my phone and after i unroot, but now the phone don't boot, it say custom binary blocked by frp, i understand that my bootloader is lock by oem, there is a way to unlock by odin or others method? i can't have access to recovery and the phone don't boot, what can i do?
Click to expand...
Click to collapse
I used smartswitch when I encountered frp lock
https://www.blogtechtips.com/2017/06/24/easily-restore-samsung-device-firmware-with-smart-switch/
1eStar said:
If you haven't backed up your data, it will be lost.
When you get yourself back out of this mess, don't touch that OEM unlock toggle again...
Click to expand...
Click to collapse
@1eStar
Firstly I have a question regarding the OEM unlock as I just came out of the FRP Lock. Do I turn on OEM unlock or does it have to be turned off? Last time I had this FRP Lock was a year ago though did it again(the mistake with the OEM unlock) as I had forgotten it(Lots of grey hair)
Just don't know if it has to be on or off?
Secondly I have managed to come out of it(so far , hopefully) without wiping data with this guide
kiwigi said:
@1eStar
Firstly I have a question regarding the OEM unlock as I just came out of the FRP Lock. Do I turn on OEM unlock or does it have to be turned off? Last time I had this FRP Lock was a year ago though did it again(the mistake with the OEM unlock) as I had forgotten it(Lots of grey hair)
Just don't know if it has to be on or off?
Secondly I have managed to come out of it(so far , hopefully) without wiping data with this guide
Click to expand...
Click to collapse
To unlock your device by frp lock you must flash the stock firmware when you are in bootloader mode you see custom binary blocked by frp,if you try to flash a random firmware(always of your device) the operation may not be a good end and device say an error with this:
Knumber) Snumber) Bnumber)
When you go to download the stock firmware you must see the "code" Of the firmware with write the same S or B number
If you Don't understand see the 10th post of this thread
https://forum.xda-developers.com/galaxy-s8+/help/custom-binary-blocked-frp-lock-regular-t3745085
corvasce03 said:
To unlock your device by frp lock you must flash the stock firmware when you are in bootloader mode you see custom binary blocked by frp,if you try to flash a random firmware(always of your device) the operation may not be a good end and device say an error with this:
Knumber) Snumber) Bnumber)
When you go to download the stock firmware you must see the "code" Of the firmware with write the same S or B number
If you Don't understand see the 10th post of this thread
https://forum.xda-developers.com/galaxy-s8+/help/custom-binary-blocked-frp-lock-regular-t3745085
Click to expand...
Click to collapse
@corvasce03
Thanks.
I think I got back allright except this here and I used exactly the same stock(file) as a year ago
Someone Help My Soul!!!
Guys, I'm scared to death on letting my phone reboot, I have been told to never let my phone restart unless my google account has been removed, can someone please explain how this FRP block really works?
Am I at risk at every given point of phone restart for real?
Cirphrank said:
Guys, I'm scared to death on letting my phone reboot, I have been told to never let my phone restart unless my google account has been removed, can someone please explain how this FRP block really works?
Am I at risk at every given point of phone restart for real?
Click to expand...
Click to collapse
It stops someone stealing your phone, wiping it, installing new firmware and using it as if it was new. If you know the gmail and password you put on the phone to access the play store then you just need to re-enter it after the phone restarts. FRP will only kick in if you have flashed new firmware to the phone.
I have a new firmware flashed on the phone.
And I'm using a new gmail with is, not some one July bro used on it.
What am I to do now? I have developer settings OEM unlock toggled on already.
Cirphrank said:
And I'm using a new gmail with is, not some one July bro used on it.
What am I to do now? I have developer settings OEM unlock toggled on already.
Click to expand...
Click to collapse
I'm not sure what you mean. If you have a Google account on the phone that you know the email and password to, then just reboot the phone. FRP lock will only activate if you flash new firmware to the phone without removing the Google account first.
Your device should only have 1 Google account registered on the device which let's you access Play store etc. If there is more than one, you need to delete the ones you don't know the email and password to.
Okay...
Oh, okay, now I am getting the rationale.
Albeit, when I flashed in the new custom firmware, it started give me the undo changes by restarting your phone notification, like it did the first time ever that I got the lock. I didn't click it, activated an app that discarded the notification rather.
Now it makes me doubt if I had really removed my mail before flashing the phone.
hey
i have got the same problem. when i deleted xposed installer, my device rebooted. every time i try to turn it on, it says in top left corner 'custom binary blocked by frp lock'. i tried 3 diff rom to flash, no succes. i tried to acces twrp (my device is rooted) but again no succes. can you guys help me?
i have a G930F
thanks.
stasikkk777 said:
i have got the same problem. when i deleted xposed installer, my device rebooted. every time i try to turn it on, it says in top left corner 'custom binary blocked by frp lock'. i tried 3 diff rom to flash, no succes. i tried to acces twrp (my device is rooted) but again no succes. can you guys help me?
i have a G930F
thanks.
Click to expand...
Click to collapse
Yeah you've messed it up by not signing out of account before unistalling xposed. When you say 3 different rom's do you mean stock or custom?
Even in this state you should be able to flash a stock rom to the device with Odin and it will ask you to type the google email and password after boot.
Always turn off FRP lock before modifying the phone, it's a really annoying feature.

Categories

Resources