Hi there,
Friend of mine using Lenovo A6000+, Doesn't have google account in that phone. It was secured with the pattern lock. But unfortunately he forgot the unlock pattern. Since he have a lot of contacts in that phone, there is no way to reset it. Its full stock version. Just a basic user., so no root access or anything. In this scenario any other way to unlock the phone without doing a factory reset? The google answers are helpful only if the usb debugging is enabled. Since it is not rooted and basically a very common user used that phone, i don't think usb debugging is enabled. Any help appreciated.
By the way, i'm also thinking of flashing a custom recovery into the phone. Will that be of any help? Would it cause the phone to lose data? Will that need usb debugging enabled to do it?
:angel::highfive::angel:
lava_owner said:
Hi there,
Friend of mine using Lenovo A6000+, Doesn't have google account in that phone. It was secured with the pattern lock. But unfortunately he forgot the unlock pattern. Since he have a lot of contacts in that phone, there is no way to reset it. Its full stock version. Just a basic user., so no root access or anything. In this scenario any other way to unlock the phone without doing a factory reset? The google answers are helpful only if the usb debugging is enabled. Since it is not rooted and basically a very common user used that phone, i don't think usb debugging is enabled. Any help appreciated.
By the way, i'm also thinking of flashing a custom recovery into the phone. Will that be of any help? Would it cause the phone to lose data? Will that need usb debugging enabled to do it?
Click to expand...
Click to collapse
I dont think, there's anything you can do about it. Ask him first, if he had ever connected to pc and authorized it for usb debugging. Otherwise, the only option left is to factory reset.
Edit: Brother, I'm working on something to change the pattern, which obviously I'll tell you. I'll make a flashable zip which you can flash through twrp. Lets see how this goes.
I'm not sure, if I'll be able to do it. But if it does, it would be very helpful for everyone.
:silly:
Edit 2: Finally I got it working!!! hurray!!
Just flash this zip below and the next time your phone boots, you can enter any "more than 3-dot" pattern and the phone will accept. Later, you can set new pattern or anything.
:angel: :silly:
P.S. I used CWM recovery on stock KK to flash it. Don't know why but I couldn't manage to flash twrp. Who cares anyway, if our job gets done. :silly:
Hi, I'm trying to get my phone back. I lost my phones password that is used to unlock the phone.
I dont know my google account im using on the phone either. Yes this is my phone.
I dont want to get locked out with google frp either
If i put twrp on and do a factory wipe, will i still need the pin?
Also, my phone doesn't need the pin to boot. thanks in advance
nebula37 said:
Hi, I'm trying to get my phone back. I lost my phones password that is used to unlock the phone.
I dont know my google account im using on the phone either. Yes this is my phone.
I dont want to get locked out with google frp either
If i put twrp on and do a factory wipe, will i still need the pin?
Also, my phone doesn't need the pin to boot. thanks in advance
Click to expand...
Click to collapse
No you won't need a pin in twrp if you have not encrypted the device..no you won't need pin to boot, but frp might get you..not sure how that works, I also feel like there are files you can delete through twrp to remove lock code, someone else will have to confirm this though, just something I heard
thanks but its not a concern now. I was on latest official ota update, flashed twrp but cant get lineage, or any custom rom to fully boot. It just gets to the logo screen and wont go any further. I have not used my moto a while.
nebula37 said:
Hi, I'm trying to get my phone back. I lost my phones password that is used to unlock the phone.
I dont know my google account im using on the phone either. Yes this is my phone.
I dont want to get locked out with google frp either
If i put twrp on and do a factory wipe, will i still need the pin?
Click to expand...
Click to collapse
FRP is disabled on unlocked bootloader.
PIN can be deleted with twrp's file manager.
LOS - you flashed wrong build. You need custom rom for N Modem. LOS by Hashbang works on N modem.
Excellent news and a solution i havent found anywhere else yet!
Follow up from - https://forum.xda-developers.com/galaxy-s8/help/restore-imei-attempt-stock-rom-flash-t3802527
TL;DR attempted to re-root as soon as the bootloader unlocked. It all seemed to stick again, and got the big red message of doom again.
"Official Binaries Only" - Last time i was able to restore to at least switch on the phone to run down the rmm state timer to zero to flash again.
Tried the several methods of flashing through a locked bootloader (old BL file, quickly restart download mode and spam start on odin, etc) - literally nothing would allow me to flash anything that included the BL file. IMEI and baseband remained unknown. Phone went in drawer for a few days.
Just went and downloaded the latest XSA (Australia, Unbranded) build - https://www.sammobile.com/firmwares/galaxy-s8/SM-G950F/XSA/ and guess what boys and girls?
This sucker flashes straight away with Odin 3.13.1
It has completely restored my IMEI and baseband, i now have full Cell connectivity again, and its all back and working again. OEM unlock is still disabled, Samsung Pay still locked out which is fine, but otherwise, i have gone from brick to fully working Exynos S8 again.
TL;DR IF YOU HAVE ISSUES WITH A BRICKED PHONE BECAUSE IT WONT LET YOU FLASH ANY STOCK ROMS TRY THAT ONE.
Thanks for the replies to my other threads trying to help out with this. Much appreciated.
Peace out.
For heads up for other after this, how to get OEM unlock to pop up again.
Go-to date and time, change the date to 8 days prior, disable automatic update of time.
Reboot phone and it may take a few tries, but OEM unlock should pop up again in developer settings.
Just went through all this without any help and it sucked lol. Thanks for making this thread for everyone.
kratosjohn said:
For heads up for other after this, how to get OEM unlock to pop up again.
Go-to date and time, change the date to 8 days prior, disable automatic update of time.
Reboot phone and it may take a few tries, but OEM unlock should pop up again in developer settings.
Just went through all this without any help and it sucked lol. Thanks for making this thread for everyone.
Click to expand...
Click to collapse
Ive had a few cracks at this now but the date keeps resetting itself when you reset the phone despite having the automatic update option switched off.
Thanks for the info tho ill keep trying.
kratosjohn said:
For heads up for other after this, how to get OEM unlock to pop up again.
Go-to date and time, change the date to 8 days prior, disable automatic update of time.
Reboot phone and it may take a few tries, but OEM unlock should pop up again in developer settings.
Just went through all this without any help and it sucked lol. Thanks for making this thread for everyone.
Click to expand...
Click to collapse
Sunuva....
I havent been inside since i replied to you before. Gave up trying to fix that and was doing other things. Just reset both the s8 and s8+ to look at download mode... noticed the rmm flag was GONE rebooted and sure enough OEM Unlock is done.
You genius.
So - Anyone actuallly reading this -
Lost root, reflashed and cant install TWRP etc, "OFFICIAL BINARIES ONLY" crash, cant replace bootloader, missing IMEI/Unknown baseband -
TRY FLASHING XXU2CRED stock rom from 18/6/18 or later. This will flash despite a locked bootloader.
Once up and running set up the phone for use. Reboot as normal. Then turn off automatic time and date set date to 8 days prior, reset phone a couple of times. Get annoyed because you keep having to reset the date backwards. Reboot phone again and set automatic tin me and date again. Reboot. Bamf unlocked and completely restored SN-G950F.
Courtesy of Funkmonkey and @kratosjohn (the little legend)
Ah I should have also mentioned I also did the same, flashed the same firmware when I was desperate and after some bit I also noticed prenormal change to official in download mode (the tell tale). I had OEM unlock on always, just was stuck in prenormal mode and couldn't flash anything.
To speed up the OEM unlock trial and error process do this as well:
1. After setting time/date back 8 days (and auto update time off). Go-to updates in settings, select manual update and check the server (it will error probably but that sets a check on their server to allow the RMM state to change next time it's connected properly).
2. Do this quite a few times, with reboot and constantly fighting the date auto update.
3. Flash the CRED firmware mentioned, boot it and setup once. Then reboot and go-to download mode.
4. You should see official as the RMM state now and you can happily OEM and flash away!
kratosjohn said:
Ah I should have also mentioned I also did the same, flashed the same firmware when I was desperate and after some bit I also noticed prenormal change to official in download mode (the tell tale). I had OEM unlock on always, just was stuck in prenormal mode and couldn't flash anything.
To speed up the OEM unlock trial and error process do this as well:
1. After setting time/date back 8 days (and auto update time off). Go-to updates in settings, select manual update and check the server (it will error probably but that sets a check on their server to allow the RMM state to change next time it's connected properly).
2. Do this quite a few times, with reboot and constantly fighting the date auto update.
3. Flash the CRED firmware mentioned, and reboot and go-to download mode.
4. You should see official as the RMM state now and you can happily OEM and flash away!
Click to expand...
Click to collapse
Have just flashed TWRP, used the Comsy version to be safe (3.13.1 fine for the stock rom flash) - I used comsy as it is mentioned in hte post OREO S8 update. It allows TWRP to be flashed but maybe thats whats breaking everything else. Ill try magisk next.
Fire up TWRP and enable system changes. FIRST - Advanced wipe and format system (Im 99% sure this is what screwed my last couple of roots), hit yes and do it. Reboot into recovery again.
Flash no-verity, then SuperSU (or your preferred root, i use Aroma installer first, THEN you have to flash the SuperSU binary with that)
Wipe dalvik etc. Reboot into system. As i type this its now in the 'Welcome' screen. Gimme a minute and ill check all is good.
UPDATE - Everything restored installed titanium backup root held. Rebooted phone aaaaaaaaand - "Only official released binaries are allowed to be flashed" - Back to square one. Will attempt same reflash now, but the root procedure kills everything. Back in download mode again. RMM State: Prenormal returned.
It is now succesfully flashing the stock rom in Odin 3.13.1 - Accidentally started it with Comsy and it DID NOT WORK. You MUST use the normal version to flash the rom im using.
Looks like we def have a stable way to refire up the phone again, and get around RMM state prenormal nice and quickly, so ill go ahead now and try and find whats going on with things breaking afterwards!
Thanks again guys.
Did nearly the same as you, dejavu.
I use magisk though. Be sure to flash a rom or kernel with RMM state fixed lol, or you'll be back here soon.
Funkmonkey said:
Have just flashed TWRP, used the Comsy version to be safe (3.13.1 fine for the stock rom flash)
Fire up TWRP and enable system changes. FIRST - Advanced wipe and format system (Im 99% sure this is what screwed my last couple of roots), hit yes and do it. Reboot into recovery again.
Flash no-verity, then SuperSU (or your preferred root, i use Aroma installer first, THEN you have to flash the SuperSU binary with that)
Wipe dalvik etc. Reboot into system. As i type this its now in the 'Welcome' screen. Gimme a minute and ill check all is good.
Click to expand...
Click to collapse
Someone should clean this up and get it stickied.
I imagine there are alot of users here with this same issue, after the CRED update we can't downgrade our bootloader, and in a panic you can get stuck here.
kratosjohn said:
Did nearly the same as you, dejavu.
I use magisk though. Be sure to flash a rom or kernel with RMM state fixed lol, or you'll be back here soon.
Looks like that wont be an issue any more to be honest this phone is now a backup thankfully so i can play around with it to my little hearts desire.
Im about to try the magisk install. SuperSU/Aroma definately breaking something somewhere. Or verity. I dont know but rooting the phone at the moment is killing it again.
Also, i have NOT lost IMEI or baseband this time. At the very least for Australian SN-G950F phones, this is a 100% flashable stock rom regardless of your RMM or phone status. I cannot say this for any other model in any other country on any other carrier, but this is all working for a carrier free Exynos S8.
Maybe y'all better archive the actual stock somewhere before someone realises theyve made a mistake somewhere and it gets pulled. Im definantly backing it up.
I just got that oem unlock trick to happen in 2 shutdown/restarts NOT reboots. BUT. I did NOT enable developer mode until i had disabled automatic time updates and turned the date back 8 days. The option came up instantly. Is something comparing a hardware clock deep in the system to a software clock in the os to and developer mode comparing something in between? Either way, on to reflash TWRP again now. This is a good day.
Click to expand...
Click to collapse
Hokay so - From a factory refresh, to the OEM unlock trick -
Flashing TWRP with 3.13.1 and allowing the phone to reboot - Phone will reboot as normal, TWRP doesnt stick. Shutdown and reboot into recovery gives you stock recovery.
Flashing but ensuring phone reboots directly into recovery gives you TWRP. A format data and reboot directly into twrp again lets me install no-verity.
- AFTER DOING THIS I AM GETTING THE RED LINE OF DEATH - Something in the system isnt letting the modifications stick.
Reflashing with the Home_CSC still seems to work as normal and i havent had to go through the welcome stuff this time...
Funkmonkey said:
Hokay so - From a factory refresh, to the OEM unlock trick -
Flashing TWRP with 3.13.1 and allowing the phone to reboot - Phone will reboot as normal, TWRP doesnt stick. Shutdown and reboot into recovery gives you stock recovery.
Flashing but ensuring phone reboots directly into recovery gives you TWRP. A format data and reboot directly into twrp again lets me install no-verity.
- AFTER DOING THIS I AM GETTING THE RED LINE OF DEATH - Something in the system isnt letting the modifications stick.
Reflashing with the Home_CSC still seems to work as normal and i havent had to go through the welcome stuff this time...
Click to expand...
Click to collapse
Have you found and used this after getting your phone setup right (w/twrp)?
I think you should flash magisk, then this after.
After I had this "panic" I flashed the custom rom I was aiming for (once RMM: Official). That rom has a kernel with the RMM state fixed/locked.
Maybe look for a custom kernel if you want root, I believe this is the fight we have to put up even on stock w/root.
Download the Australian stock rom and install it but do not recover IMEI or coverage. I think it's because my G950F (singlesim) cell phone thinks it's G950FD (double sim). This causes the cell phone to get confused and not recognize any imei or sim. Does anyone know how to fix it?
Funkmonkey said:
Sunuva....
I havent been inside since i replied to you before. Gave up trying to fix that and was doing other things. Just reset both the s8 and s8+ to look at download mode... noticed the rmm flag was GONE rebooted and sure enough OEM Unlock is done.
You genius.
So - Anyone actuallly reading this -
Lost root, reflashed and cant install TWRP etc, "OFFICIAL BINARIES ONLY" crash, cant replace bootloader, missing IMEI/Unknown baseband -
TRY FLASHING XXU2CRED stock rom from 18/6/18 or later. This will flash despite a locked bootloader.
Once up and running set up the phone for use. Reboot as normal. Then turn off automatic time and date set date to 8 days prior, reset phone a couple of times. Get annoyed because you keep having to reset the date backwards. Reboot phone again and set automatic tin me and date again. Reboot. Bamf unlocked and completely restored SN-G950F.
Courtesy of Funkmonkey and @kratosjohn (the little legend)
Click to expand...
Click to collapse
Do we need to factory rest or just reboot phone after we change date?
Funkmonkey said:
Sunuva....
I havent been inside since i replied to you before. Gave up trying to fix that and was doing other things. Just reset both the s8 and s8+ to look at download mode... noticed the rmm flag was GONE rebooted and sure enough OEM Unlock is done.
You genius.
So - Anyone actuallly reading this -
Lost root, reflashed and cant install TWRP etc, "OFFICIAL BINARIES ONLY" crash, cant replace bootloader, missing IMEI/Unknown baseband -
TRY FLASHING XXU2CRED stock rom from 18/6/18 or later. This will flash despite a locked bootloader.
Once up and running set up the phone for use. Reboot as normal. Then turn off automatic time and date set date to 8 days prior, reset phone a couple of times. Get annoyed because you keep having to reset the date backwards. Reboot phone again and set automatic tin me and date again. Reboot. Bamf unlocked and completely restored SN-G950F.
Courtesy of Funkmonkey and @kratosjohn (the little legend)
Click to expand...
Click to collapse
Can you please help me? so when you say reset phone you are talking about restarting it? I have tried this a few times and not working for me. My oem has always been unlocked, but still have prenormal
Smartphones13 said:
Can you please help me? so when you say reset phone you are talking about restarting it? I have tried this a few times and not working for me. My oem has always been unlocked, but still have prenormal
Click to expand...
Click to collapse
I was stuck here too, flash the latest CRED firmware he linked.
Then boot it one time (setup til you see launcher).
Do the OEM unlock method.
You can follow the steps after if you want root.
I suggest magisk and a custom ROM, that had RMM state fixed (so you won't get locked again).
Good luck!
Smartphones13 said:
Can you please help me? so when you say reset phone you are talking about restarting it? I have tried this a few times and not working for me. My oem has always been unlocked, but still have prenormal
Click to expand...
Click to collapse
Sorry i missed your reply i hope you got it fixed if not post again and ill see if i can help. Ive definantly gotten that oem unlock trick working which is awesome but its fiddly. I dont think it works if you turn on flight mode and you have to let the phone fight you between 'no automatic date and time' and the network forcing the time.
Of course now i cant get the oem unlock trick working...
RE the dual sim issue... i think you would need the stock rom specific to your model try sammobile, see if there is a CRED release for your model. I cant guarantee it will work tho.
kratosjohn said:
I was stuck here too, flash the latest CRED firmware he linked.
Then boot it one time (setup til you see launcher).
Do the OEM unlock method.
You can follow the steps after if you want root.
I suggest magisk and a custom ROM, that had RMM state fixed (so you won't get locked again).
Good luck!
Click to expand...
Click to collapse
Thank you for your help, I am on the latest firmware now and into my Google and Samsung accounts. I am a little confused on the wording in the oem steps. I have tried it a bunch of times. Prenormal is still there, I already have the OEM unblocked, I can toggle OEM on and off but it doesn't change my rmm status. I am not sure what I am doing wrong.
Smartphones13 said:
Thank you for your help, I am on the latest firmware now and into my Google and Samsung accounts. I am a little confused on the wording in the oem steps. I have tried it a bunch of times. Prenormal is still there, I already have the OEM unblocked, I can toggle OEM on and off but it doesn't change my rmm status. I am not sure what I am doing wrong.
Click to expand...
Click to collapse
Thats exactly what im now struggling with. It absolutely did work twice but i cant get it to go now.
Heres the thing - both times i did it before, i would turn off automatic time and date and set the date backwards, then reboot the phone, when it reboots, automatic time and date were rechecked, and the date reset to now (hence the 'fighting with the date' comments) ... i think thats important, because now when i try it, automatic time and date stay OFF, the date does not reset, and i cant get the trick to work anymore. No amount of wifi/airplane/mobile data on/off seems to change owt.
If anyone reading has any ideas it would help.
Funkmonkey said:
Thats exactly what im now struggling with. It absolutely did work twice but i cant get it to go now.
Heres the thing - both times i did it before, i would turn off automatic time and date and set the date backwards, then reboot the phone, when it reboots, automatic time and date were rechecked, and the date reset to now (hence the 'fighting with the date' comments) ... i think thats important, because now when i try it, automatic time and date stay OFF, the date does not reset, and i cant get the trick to work anymore. No amount of wifi/airplane/mobile data on/off seems to change owt.
If anyone reading has any ideas it would help.
Click to expand...
Click to collapse
I see, so you suppose to set date back 8 days and turn off auto time and date and restart phone? When it comes back on to and set the date back to 8 days again? I thought you have to check the software? And then do those steps? So after I change the date back after that first restart, then what? Do I just turn OEM lock on and check download mode to see what the status is? I am not trying to be a pain o am just confused a little on the steps. Thank you for all your help
Smartphones13 said:
I see, so you suppose to set date back 8 days and turn off auto time and date and restart phone? When it comes back on to and set the date back to 8 days again? I thought you have to check the software? And then do those steps? So after I change the date back after that first restart, then what? Do I just turn OEM lock on and check download mode to see what the status is? I am not trying to be a pain o am just confused a little on the steps. Thank you for all your help
Click to expand...
Click to collapse
I think we might be looking at different issues.
This is to fix a semi bricked phone that has locked up its bootloader. In the past to resurrect a samsung all you had to do was flash twrp and your new rom but since Oreo some funkiness has been added to the system which only lets you flash a stock rom, (i.e. restoring a phone to factory settings and software) via ODIN/HEIMDALL then it locks up the bootloader for a week so you CANNOT flash anything into the phone that modifies the bootloader (i.e. TWRP OR *any* rom) until its timer runs out. This is most likely an anti theft feature esp with samsung and google pay use as it means there is no way to easily break into a stolen phone and use it as normal, and reflashing breaks all of the security features of the phone (e-fuse) - no knox no samsung or google pay no samsung pass as your device is insecure and could spoof false banking details etc.
The rom i linked to is important as it is a new AUSTRALIAN unbranded STOCK rom, that for some reason you can flash OVER a locked bootloader, meaning you can resurrect (australian at the very least) SN-G950F phones (exynos)
If you already have a working phone and can get to your developer settings then most of this thread is irrelevant to you.
Now - OEM unlock - You just bought a brand new galaxy from samsung (or youre me and you bought a MINT second hand one from cash converters for $700 less) - your phone is factory standard and schmicky. THE BOOTLOADER IS LOCKED. THE RMM STATE SHOULD NOT be triggered. If right now you went to flash something it would fail.
So you go to about phone - software information and you tap 'build number' seven times to unlock developer mode. Hit back twice and developer mode will be at the bottom of settings.
Click into this and you should see without swiping down 'OEM UNLOCK' - If you enable this, you can then reboot straight into download mode (power vol down and bixby) and flash twrp or whatever rom.
If you dont see this option, you either have a snapdragon model (youre **** outta luck permanently) or RMM is PRENORMAL and you either have to try the unlock trick(s) or leave your phone SWITCHED ON for 1 week and it will unlock itself.
The biggest issue at the moment is that i keep breaking something after i attempt to root so not sure whats happening there so use major caution.
Now as i said the trick posted above to unlock without having to wait a week (which i think youre asking about) im now not sure how it works because i cant get it to work any more.
Automatic time and date off, set date back 8 days, reset the phone. Do this a couple of times, then turn on automatic date and time again. HERE THERE BE ISSUES. When i first did it - i switch off time and date and change then reset, when the phone came on, auto date and time was on again. Turn off, change date, reset. Again, its back on. Turn off, change date, reset. Its back on. I give up and leave it, and notice later the option was available, so it worked. I broke the phone, reflashed again, did the trick in ONE reboot. Fcked something again, reflashed, now auto time and date stays off and the trick wont work so i cant help you with that until someone comes up with more info im sorry! Its a bit zarbis.
Im not going too nuts trying to fix it as i now have a fully working stock backup phone that sits on DeX plugged into my bedroom tv full time and im not into custom roms, root keeps breaking the phone, and ive sonce replaced it with a mint S8+ that im not even THINKING about considering rooting until its replaced maybe next year. Its not as easy to get around anymore and thankfully a) picasa and hangouts are no longer stock apps and can be banished and b) you can now disable all the other built in apps natively so its now a lot more bearable with a totally stock phone.
Does anyone know if it is possible to re-lock the bootloader on the Galaxy Tab A T510? If so, would I begin with flashing back to stock firmware then disabling OEM unlock in developer options or following different steps? I certainly want to avoid bricking the device. I've searched for a solution but can't seem to find anything. Thanks!
dlehmanusa said:
Does anyone know if it is possible to re-lock the bootloader on the Galaxy Tab A T510? If so, would I begin with flashing back to stock firmware then disabling OEM unlock in developer options or following different steps? I certainly want to avoid bricking the device. I've searched for a solution but can't seem to find anything. Thanks!
Click to expand...
Click to collapse
You need to download the latest stock firmware either from Samsung or Sammobile and use Odin to flash it. DO NOT DISABLE OEM!!!! That has nothing to do with locking the bootloader. Flashing the stock ROM will do that. The OEM enable only disables the FRP lock which makes you login with the same google account used BEFORE a factory reset. If you are sure you know that account login and password, the FRP lock isn't a problem.
edit: The problem with the FRP lock is that people will often create a new google account login and password when first setting up their tablet. And because you only have to do that once, they tend to forget one or the other. Then, if they do a factory reset without the OEM enabled, they are locked out of the tablet.
Thanks for the detailed information and clarification. Your help is much appreciated!
The T510 doesn't have a locked bootloader.
ashyx said:
The T510 doesn't have a locked bootloader.
Click to expand...
Click to collapse
No, but it does "lock" the tablet from getting OTA updates.
I have reflashed the stock firmware however I'm still receiving the following message during boot..."The bootloader is unlocked and the software on this device cannot be verified". Is there a way to remove this message? I am planning to return the device and I want to reset everything. Thanks!