Hey guys,
So I went to do a factory reset on my phone on Saturday just gone (and several more times on the Sunday), since apps started randomly not working properly. Anyway, I figured since I'm doing a reset I might as well re-attempt installing RenICE since the last time I tried, the support for gs8+ was still very early.
So I reset the phone and go to flash TWRP (tried 3.14 and 3.2x), using Odin.
I have developer options enabled and USB debugging, but there was no OEM unlock button.
So I tried the following tricks:
- disable all auto-updates (not the one inside Google Play)
- disable automatic time set
- set time to 7 days before the current date
Apparently doing this and resetting enables OEM unlock, however the time just reset to a variance between the current date (when wifi or network was enabled) and 24 hours prior the fac reset (with sim removed and wifi turned off)
I have my gmail account put into the device. I also tried wiping the cache, which succeeded but still did not affect the current known date and no OEM unlock.
I did some digging and this can happen when the BL is already unlocked... so I put it into recovery mode and it says "OEM LOCK: 1" or something to the effect that it is still in fact locked.
I even tried re-flashing an XSA rom and that didn't change anything either.
Anyway, I've just found a potential solution to this problem and I just want to share it with the community in case anyone is facing the same problem.
It now seems very obvious, but I literally just tried it again as I was writing this post asking for help and now OEM unlock is enabled.
Solution: disable updates in Google Play Store then reset with wifi off and sim removed. (not sure about the combination here, the only thing I did different was Google Play. So it could be needing all three at once, might just be that last update setting needed switching off. Who knows, not gonna risk it again coz I want RenICE today haha)
If anyone is having this issue, or there are some hackers around with some spare time. Give it a whirl and lemme know how you go.
Some sys info:
Model: SM-G955F
Android: 8
Baseband: G955FXXU4CRI1
Kernel: 4.4.111-14315050-QB19732162
Build#: R16NW.G955FXXU4CRI1
Knox: 3.0
TIMA: 3.3.0
One question. You say turn off auto update play store then reset with wifi off and sim removed. My question is reset what? The wifi or auto update play store. A bit confused
Quick Steps to get OEM after flash a stock firmware
Nice to see your message, but I facing that trouble on the night and I notice this
Flashing stock firmware and doing the setup normally, I can't pass the 7 days going back then I do this; going to stock recovery and I do format data and cache and wiping cache, then do the setup normally and you can pass the 7 days going back to get OEM
santiago013 said:
Nice to see your message, but I facing that trouble on the night and I notice this
Flashing stock firmware and doing the setup normally, I can't pass the 7 days going back then I do this; going to stock recovery and I do format data and cache and wiping cache, then do the setup normally and you can pass the 7 days going back to get OEM
Click to expand...
Click to collapse
I also tried that and it didn't work for me... forgot to mention
Related
Hello everyone,
So here's my story: I got a 6P short after release and it's been amazing. After switching from a S6 I couldn't be happier until 3 days ago.
I was playing around with my phone (checking for updates on the play store if I recall correctly) and I was going to switch from 4g to wifi. I went ahead and pulled down my notification shade and went to press WiFi but misclicked and hit Hotspot which was below it. My phone suddenly froze big time and this is for the first time ever since purchase.
At first I thought I'd wait it out since the device was completely unresponsive, home button didn't work and neither did anything on screen. Buttons didn't make a difference either. 10 minutes went by and I ended up force restarting by holding down power + volume up. First part of my bootup went fine but when it got to the android boot animation after I put in my pin to allow the device to start it dropped from the smooth usual framerate down to 1 frame every 10-15 seconds and it slowed down further until it came to a complete halt around the time the android letters appear.
My first thought was corrupt rom so I went ahead and wiped data from the stock recovery. I was running completely stock with no modifications whatsoever. That didn't do anything. Phone still froze in the same boot phase. Desperate I unlocked bootloader to flash a clean fresh image to try to fix it and to my surprise that didn't change a thing.
As I was getting pretty desperate already I had one more idea and that was to flash up to the Dev preview. To my huge surprise it booted and I jumped from excitement. So I started setting up my phone again. I got past the prompt to insert sim card and I was now at the screen to choose a wifi network. As soon as I clicked into that the phone froze up again and at that point I lost all hope.
I wiped data in stock recovery and shut the phone down for the night. On day 3, today I woke up and tried starting the phone and it worked as if nothing had happened. I went through the setup and set up my phone on the N preview. At a certain point I was planning to go back to the latest official build but for now I was happy my phone was back from the dead. Later today I tried to restart my phone to clear all running apps etc and it froze up on boot.
I'm losing all hope that I'll be resolving this myself so I'm reaching out to the community to see if anyone's had this happen to them before and hopefuly for a solution. It's still under warranty so I can eventually send it back to the retailer but I'd rather not have a phone for 3 weeks.
Any and all help is appreciated.
Thank you for reading through my long and probably pretty boring story!
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
To the OP, is there any reason you did not flash to release version 6 instead of Dev preview ?
Also, any reason you can not simply do the "unenroll" from https://www.google.com/android/beta ?
It will require you to setup certain settings again as you will be back to a "factory reset".
DJBhardwaj said:
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
Click to expand...
Click to collapse
DJBhardwaj, i haven't specifically erased those partitions. I was under the impression wipe userdata along with reflashing did that. I will try that tonight when I get home!
Xdafly, I only updated up to N as a last resort because at first I had a locked BL. I was planning to unenrol but that would've been too late as it self bricked after a restart.
DJBhardwaj said:
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
Click to expand...
Click to collapse
Well I just did the erase thingy and my phone booted but wifi won't turn on. Enabling hotspot doesn't brick anymore but I now suspect WiFi might've been the issue. Any tips on how to find out what it could be and possibly fix it?
Edit: 2 restarts and a factory reset later I'm back to bricked same way as before.
try safe mode
mr.dj26 said:
try safe mode
Click to expand...
Click to collapse
That was my first thought, that was the restart that bricked it again. Safe mode shouldn't have made a difference since I hadn't even logged into Google account for apps.
After reading the very first post; sounds like bad WiFi hardware.
All the hanging has been related to WiFi or Hotspot.
I think you should get a replacement
Sent from my Purified NexusixP
If Someone Helped You Then Dont Just say Thanks...Hit The Thanks Button!
Is your phone rooted and did you install Xposed?
Over the weekend I shutdown my 6p (stock rooted with April security patch, Xposed v80) and charged it. When it turned it back up I kept getting "Unfortunately, nfc service has stopped". Long story short: I ended up factory reset my phone and reinstalled EVERYTHING and I still got into bootloop. Then I came across
https://github.com/rovo89/Xposed/issues/113
https://github.com/rovo89/android_art/issues/28
At the end of the second post rovo89 (developer of Xposed) fixed the bug in V83. I wiped my 6p once more and installed everything with v83. Problem solved.
Good luck!
Well this is my 1st post so first of all hey everyone
I just spent a week in Amsterdam and my phone restarted twice, different times different days and I dont remember what I was doing with it back then.
But as I landed back home I put the phone back from "Airplane Mode" and went on to toggle "Cellular Data" on.
The second I pressed the cellular data shortcut on my the phone restarted itself but this time whenever it would finish the screen would be on but fully black and sometimes it'll show battery precentage at the top but then will restart again in an infinite loop.
Sometimes it'll pop up the "Optimizing Apps" window and will go through all 24, upon finishing it will restart once more and do the same.
I tried using the bootloader and it worked (the bootloader that is) but the phone would do the same thing even after Rebooting from there or shutting down from there and then turning back on.
I contacted tech support on chat but they couldnt help past telling me to go to bootloader and reboot, said I should factory wipe when it failed.
Also tried wiping cache but to no avail.
I have no backup of my phone (wanted to do one before the flight but got lazy and I suck for not doing one sooner) since probably October and google doesnt backup my contacts properly for some unknown reason.
I already downloaded Android Studio with everything included for me to try using adb to sideload stock without wiping but its my first time and I couldnt get it to do anything at all...
I already got the official stock .gz file from the motorola website.
Anyway here are the specs to my phone:
XT1575
Everything is stock. didn't root or change recovery once in my life.
Was fully updated and had plenty of drive space (I have almost 128GB with the 64GB version + 64GB SD)
I'm really lost here so help will be very appreciated.
Thanks in advance,
-Noam
Start with a full wipe and if that doesn't work flash the stock image. Not sure what your question is though as you never really say. Once fixed I would unlock and make a backup so you don't have to deal with this again.
lafester said:
Start with a full wipe and if that doesn't work flash the stock image. Not sure what your question is though as you never really say. Once fixed I would unlock and make a backup so you don't have to deal with this again.
Click to expand...
Click to collapse
The thing I pretty much want to know is if theres a way to either backup the phone now with it connected to the computer while in bootloader or recovery. or a way to flash the stock rom without wiping which I read someone did with his tablet. I cant post source normally because I'm a new user so here it is but change spaces to dots: schnouki net/posts/2014/08/13/flashing-a-stock-android-image-without-wiping-user-data/
Also while in recovery I noticed 2 options under wipe: 1. userdata only. 2. userdata+(insert something I dont remember here) and I was wondering what gets deleted in both? if I delete only userdata what data will remain? something helpful?
Sure you can try flashing without wiping data but being locked I personally wouldn't risk it. No idea about backing up in your state... somewhere I remember a thread on backing up without root try searching in q&a.
lafester said:
Sure you can try flashing without wiping data but being locked I personally wouldn't risk it. No idea about backing up in your state... somewhere I remember a thread on backing up without root try searching in q&a.
Click to expand...
Click to collapse
Out of curiosity why shouldnt I try flashing with no wipe if ill lose the data anyway? worst case wont I just have to wipe after it fails and flash again?
And I will try thank you
Do you have any knowledge about the 2 wipe options?
Thanks in advance
Well I tried turning the phone on and it took a couple of minutes before loading to a fresh start. It apparently wiped itself on its own. Managed to restore almost everything.
Anyhow the phone takes too long to boot now. Was even stuck at boot and I had to restart it.
Anyway to fix my software? Or at least check for corruption?
Sent from my XT1575 using XDA-Developers mobile app
Last night, my wifi just stopped working, it won't enable. When I go to advanced I am sometimes able to turn on the wifi, but it just continuously says turning on but won't enable, and sometimes it's just totally greyed out. I also had some problems today connecting to mobile data services as well, and I don't know if that's related.
I've tried a hard reboot (but it just comes up saying no command...), I've tried restarting it a million times... The only thing I haven't tried is a factory reset, because I am abroad using google fi and I am worried that I will have to set up my project fi again and I can't connect to a tower in the USA. (I am not sure if that will even happen, but I won't be back in the USA for a good few months so I don't want to risk it)
My phone says it updated yesterday, which I assume has caused this wifi problem (or a really big coincidence), but I can't find any information online about it.
I run the stock rom, it's not rooted, I have had no problems with any other things besides this.
Is anyone else experiencing this, or has experienced this before? Do you have any suggestions on how to resolve it?
It sounds like you are experiencing the same problem as everyone who forgot to update their vendor image after flashing the OTA. Had you been rooted, the simple fix would have been to flash the the MTC19X vendor image. With unrooted phone, I got nothing. The only possible solution would be a factory reset and to download and install the OTA again.
kyzn said:
It sounds like you are experiencing the same problem as everyone who forgot to update their vendor image after flashing the OTA. Had you been rooted, the simple fix would have been to flash the the MTC19X vendor image. With unrooted phone, I got nothing. The only possible solution would be a factory reset and to download and install the OTA again.
Click to expand...
Click to collapse
I don't touch anything or mod anything on my phones. The phone updates itself and as long as I am not running any custom roms I don't see why they wouldn't have a complete update that basically just spoon feeds my phone. Do you know if factory reset would reset my project fi?
RoseBunny87 said:
I don't touch anything or mod anything on my phones. The phone updates itself and as long as I am not running any custom roms I don't see why they wouldn't have a complete update that basically just spoon feeds my phone. Do you know if factory reset would reset my project fi?
Click to expand...
Click to collapse
I believe factory resets wipe the /data and /cache partitions of the device. All apps installed in /data are deleted, while apps in /system like project fi will have all its setting reset.
It's easy to resolve the iasue if your rooted, but since you aren't the next to last step you may try would be doing a network settings reset. Go to Settings>Backup and Reset>Network Settings reset. Just make sure that you are aware of your cellular data settings so you can set thing back up after the reset.
Hey all, been a while since I've been on - longest I've ever had a stock phone for . Hoping somebody can offer some advice as I'm stumped...
NOTE: If possible, I'm trying to avoid a factory reset!
Last night my stock UK Note 4 (SM-N910F) died (possibly during an OTA update but I wasn't using the phone and have been told it didn't so not sure) and when turned back on would just sit at the pulsing Samsung logo with no apparent restarting or anything. Clearing the cache didn't make a difference.
Recovery reported my ROM to be N910FXXS1DQE9 (region BTU). After waiting ages for the download, I first tried BTU-N910FXXU1BOC5 which produced the exact same problem with a different Samsung animation. I then tried BTU-N910FXXU1DQHC which seemed to sort of work - it would now boot but gave me a "Unfortunately, System UI has stopped" error with a black screen. I then flashed BTU-N910FXXU1DQH3 which is what I have running currently but this does the same thing. I did also try wiping cache in combination with the above (is this actually needed after flashing a new ROM?). I have also tried safemode - would let me open the power menu but otherwise did exactly the same thing.
I'm currently downloading the original ROM that wouldn't boot (N910FXXS1DQE9) from samsung-firmware but it's taking ages at ~50KBps. What are the chances of this working compared with the others, I assume probably not much? If likely, I'll pay up for an account and a quick download.
I've also tried flashing TWRP but I have reactivation lock on - does anybody know a way to disable / bypass this without access to the phone (research tells me probably not but there are a lot of smarter people than me here that I hope could tell me otherwise ). I can get into stock recovery but that only gives me ADB in sideload mode and I can also enter download mode fine obviously. Does anyone have any suggestions on recovering data from the phone before I factory reset?
Simply put, have I lost everything on the phone or is there a way I can retrieve some of it?
Also, I do have a load of server space I can offer with decent bandwidth - I have those ROM images above so I can offer these for download at a decent speed without a cost if anybody here on XDA needs - just send me a PM for a link
Hi, Today I was using my phone and in mid day I realised my phone is not accepting my pin code but finger print is working fine.
I tried many time but pin didnt work and I used my pin code unlock few hours ago. Long story short I have reset my phone from recovery and setup my phone again.
BUT when I try to put a pin lock or password or any other security, my phone gives me error that is "Screen lock was already changed. Try again with the new screen lock." Screenshot attached
Any solution to this?
My phone is G975F on Android Q beta 2 DBT (VAU).
I have done factory reset , installed new firmware but it is not working.
kazim.asghar said:
Hi, Today I was using my phone and in mid day I realised my phone is not accepting my pin code but finger print is working fine.
I tried many time but pin didnt work and I used my pin code unlock few hours ago. Long story short I have reset my phone from recovery and setup my phone again.
BUT when I try to put a pin lock or password or any other security, my phone gives me error that is "Screen lock was already changed. Try again with the new screen lock." Screenshot attached
Any solution to this?
My phone is G975F on Android Q beta 2 DBT (VAU).
I have done factory reset , installed new firmware but it is not working.
Click to expand...
Click to collapse
Same issue with me as well. Can anyone help..
kazim.asghar said:
Hi, Today I was using my phone and in mid day I realised my phone is not accepting my pin code but finger print is working fine.
I tried many time but pin didnt work and I used my pin code unlock few hours ago. Long story short I have reset my phone from recovery and setup my phone again.
BUT when I try to put a pin lock or password or any other security, my phone gives me error that is "Screen lock was already changed. Try again with the new screen lock." Screenshot attached
Any solution to this?
My phone is G975F on Android Q beta 2 DBT (VAU).
I have done factory reset , installed new firmware but it is not working.
Click to expand...
Click to collapse
Was this right after installing the beta 2? When you installed Beta 1 did you leave the system as it was or did you factory reset it? if so can you quantify how many times you unlocked your phone before went south? Was you stuck after rebooting from realizing your pin is not working? Meaning, after the issue and you restarted the phone was you able to enter your pin and proceed, then afterward it stopped?
[edit] The reason why I ask about the factory reset is in one of the other Beta threads people was having a lot of issues and after a factory reset it became near flawless. As of right now I''m monitoring my phone to see if this will happen to me, however after Beta 1 I did a factory reset, so I'm not sure it's a symptom of lingering files. I usally after applying an update to a beta ROM, I factory reset and out of all the times I did it, Android Q was the most buggy and was the only Beta i reverted, but the phone was a Pxiel..
mykenyc said:
Was this right after installing the beta 2? When you installed Beta 1 did you leave the system as it was or did you factory reset it? if so can you quantify how many times you unlocked your phone before went south? Was you stuck after rebooting from realizing your pin is not working? Meaning, after the issue and you restarted the phone was you able to enter your pin and proceed, then afterward it stopped?
[edit] The reason why I ask about the factory reset is in one of the other Beta threads people was having a lot of issues and after a factory reset it became near flawless. As of right now I''m monitoring my phone to see if this will happen to me, however after Beta 1 I did a factory reset, so I'm not sure it's a symptom of lingering files. I usally after applying an update to a beta ROM, I factory reset and out of all the times I did it, Android Q was the most buggy and was the only Beta i reverted, but the phone was a Pxiel..
Click to expand...
Click to collapse
I intalled beta 2. Everything was working fine. But when I restarted my phone, it stopped accepting my 4 digit pin. Then i hard reset the phone and factory reset. But after that it not accepting any new Pin or Pattern to register.
What should I do know as there is no screen lock on my phone
mykenyc said:
Was this right after installing the beta 2? When you installed Beta 1 did you leave the system as it was or did you factory reset it? if so can you quantify how many times you unlocked your phone before went south? Was you stuck after rebooting from realizing your pin is not working? Meaning, after the issue and you restarted the phone was you able to enter your pin and proceed, then afterward it stopped?
[edit] The reason why I ask about the factory reset is in one of the other Beta threads people was having a lot of issues and after a factory reset it became near flawless. As of right now I''m monitoring my phone to see if this will happen to me, however after Beta 1 I did a factory reset, so I'm not sure it's a symptom of lingering files. I usally after applying an update to a beta ROM, I factory reset and out of all the times I did it, Android Q was the most buggy and was the only Beta i reverted, but the phone was a Pxiel..
Click to expand...
Click to collapse
I did a clean install fresh firmware for beta 1, clear cache for beta 2.
I am not sure how many unlocks but i took few days after beta 2. My phone was waorking fine in morning as I unlock my phone in car using pin. But in after noon when I used the pin it showed me wrong pin. Every thing related to security wont work. Cant register finger print or face. But if you do same in secure folder everything will work fine.
Okay if it happens to me I will try to track down how it happened.
You did something and screwed up. A lot of people are using beta 2 already and have not encountered this issue, myself in it. I have done a lot of restarts and I have changed my pin successfully.
NickosD said:
You did something and screwed up. A lot of people are using beta 2 already and have not encountered this issue, myself in it. I have done a lot of restarts and I have changed my pin successfully.
Click to expand...
Click to collapse
What about other people who are affected by it? Read comments in Android 10 beta thread on page after 135. You will find people reporting this issue.
I didnt do anything with my phone just updating with beta.
I'm another that's been affected, had to do a factory reset via bootloader.
Currently stuck on Beta 2, Smart switch won't downgrade.
No security options available and an extremely buggy phone.
A new update has been pushed out. I just received it on my phone. Will be performing a factory reset once the update is installed and will setup the phone from scratch.
ashwinrajsr said:
A new update has been pushed out. I just received it on my phone. Will be performing a factory reset once the update is installed and will setup the phone from scratch.
Click to expand...
Click to collapse
Update me if it has fixed the security issue.
i installed *emergency update* , no wipe,no reset ,things go back to normal
Everything is cool as the phone has not been blocked. Otherwise there is no way to upload the update.
I wonder why they can't release the patch to upload it via ODIN, that would solve the problem.
Wait what !?!?, the same thing happened to me
Even worse - i rolled back to P, where i was able to add a pin but it would always forget it. I ended up going to a samsung center where they changed the board (in warranty), they said my unique device key was corrupted - likely due to internal storage error
So it is a beta problem then
Please provide feedback in the samsung members app. Those that cant, send feedback in the official thread at samsung forums.
Beta 2 is Terrible, having all kinds of Problems with it. Beta 1 was Much Better. Hope another Update comes out soon or will just go back to PIE. G975U S10+
I do have the same problem on my Zenfone 6z. After I relocked my bootloader I couldn't set up a pin. Asus still haven't rolled out an update.