Any way to get past fingerprint lock/backup password lock? - G2 Q&A, Help & Troubleshooting

I bought my phone used off of Swappa. The phone was initially a stock rooted phone. I did a factory reset, then flashed to NK4 stock then rooted. For some reason it seems to have retained the previous owners fingerprints and backup password so I cannot change them. Is there any way around this? I'm assuming I probably have to go into recovery and do a full wipe, but I'm hoping to avoid that. The seller isn't responding so seems like that isn't an option either.

That ore a kdz flash with total wipe

Related

[Q] Unable to remove custom padlock stock lolipop

I have tried everything I can possibly think of in a short period of time, and need an answer in a hurry. The phone (Verizon Samsung Galaxy Note 3 N-900V) was rooted back when kitkat was the main OS using geohot's towelroot (or possibly kingo root I can't remember which i used after I got the phone and upgraded from ICS). I have 2 of these exact same phones, used the exact same rooting method, and unrooted by uninstalling the superuser app, rebooted, and installed the OTA update to lolipop. My phone works fine, (the one I'm typing from) however, my other phone decided to take a dump. It's a software bug between the samsung firmware and the new lolipop OS. It was working for several months, then all the sudden it wouldn't recognize/register the APN. Now it doesn't see anything just about with the phone. Not even the IMEI from the phones serial number. The sim card has been replaced twice and has worked for a matter of a few hours, however, upon restarting the phone, it goes back to no service, and nothing is registered or recognized. I reflashed the phone with the stock 5.0 Lolipop using Odin several times to no avail. My phone (one I'm using now) once did this months ago, and I was able to access the service menu and reregister the SIM card and phone has worked fine since. With this other phone, I can't get into the service menu at all because nothing is registering. So, after reflashing 4 or 5 times, factory reseting from both the OS and from recovery booting, it still has the same issue. Here is my question. It used to be when I reflashed, the custom padlock would disappear. I'm getting a new phone tomorrow, and I need to get rid of the custom padlock before I return the old phone. I can use Odin, or whatever but it has to be something, I can do while it stays stock. The knox counter has not been tripped, and the flash counter is not tripped nor showing anything on the download mode. Everything lools, and feels stock, except that custom padlock. Is there a way to get rid of that custom padlock unrooted, by reflashing? I even used a pit file to repartition, but that didn't work either. Need help A.S.A.P.!
I would just hard brick the phone just before returning it...they will just throw it out at that point and your secret will be safe.
Hard Brick
xxperrin said:
I would just hard brick the phone just before returning it...they will just throw it out at that point and your secret will be safe.
Click to expand...
Click to collapse
You thinking maybe a NAND erase?
Hard Brick
I've thought about flashing the wrong rom too but dunno if that will work 100%. I either need to fix it, or make it 100% unrecoverable. Any advice?

Is my Note 4 entirely dead? Phone dies after 60 seconds

Hi Guys.
I bought a second hand Note 4, which is already a mistake. after a week it started giving me problems of no reception which only rom flashing helped (flashed the stock rom 5.0.1)
another week and it worked then suddenly lost reception, asked for "sim card pin number" and then crashed (after i clicked discard to the pin code message)
since then it restart itself every time after something like 60 seconds it's on.
recovery works, and nothing that i do helps. tried to re-flash it, wiped everything before and after flashing, tried to install CM 12.1 and some other roms
All going to the same basic result - no matter what, after 1-2 minutes the phone just crashes and resets
Anyone has any idea what could it possibly be? :|
i just suggested the same to another member, might help you aswell
1) Flash twrp recovery , go to wipe option hit "format data" then go to advanced wipe check dalvik cache, system, data and cache. Swipe to wipe
2) your phone will have no ROM at this point, go to sammobile download stock 5.0.1 firmware. Flash it.
3) This could be because some second hand phones are still on contract, people sell them overseas and get a new phone by claiming the previous one as stolen. So after sometime the carrier (Tmobile verizon etc) may blacklist the phone and then these phones start getting reception issues. Is your phone carrier branded ?
I suggest going for 5.1.1 and not 5.0.1 after you done what dork suggested above.
Ps. Remember to get the correct bootloader and modem for the desired firmware.
in my opinion you ve bought a Chinese device(fake) ( my mom also got scammed).

[PROBLEM] Rooted > Flashed to U Firmware > Soft Brick > Flashed back to Verizon FW

[PROBLEM] Rooted > Flashed to U Firmware > Soft Brick > Flashed back to Verizon FW
Hi, relatively new to this, so sorry in advance if I made some obvious mistakes, but my phone is now soft bricked and I can't find a solution.
1) I was on Nougat
2) Rooted with Odin to remove Verizon bloat
3) Didn't really change much, still had MMS issues etc
4) Did a the deep verizon debloat. Started getting an endless message 'IMS Service has stopped'
5) Decided to flash U Firmware to get a non-Verizon, unrooted starting point. Used HOME_CSC to keep data
6) Soft bricked phone (didn't finish install and was stuck on a boot menu with the message 'dm-verity verification failed' )
7) Flashed back to a previous version of Verizon firmware, again, HOME_CSC - (G935VVRS4APH1_CL8875708_QB10880117_REV02_user_low_ship_MULTI_CERT.zip). (Did this twice now, once with PrinceCosmy Odin)
8) Install went well, Verizon logo on boot.
9) Soft brick #2 - I'm being asked for a password to decrypt storage...I set no password for this. So I'm stuck.
Thanks in advance, any support is much appreciated!
The PH1 firmware is very old. You might have better luck flashing to QF2. Honestly, your best bet is to boot into recovery to do a factory reset, then start over completely. That will clear the decryption issue. Then look at the QF2 ROM in this forum.
CVertigo1 said:
The PH1 firmware is very old. You might have better luck flashing to QF2. Honestly, your best bet is to boot into recovery to do a factory reset, then start over completely. That will clear the decryption issue. Then look at the QF2 ROM in this forum.
Click to expand...
Click to collapse
Thanks! I was hoping to not have to reset, but have recently backed it won't be a big deal.
I have two other questions though
a) how do I know which firmware is QF2? (the device was originally on MM but through smart switch I upgraded to Nougat)
b) what's the process for the factory reset? I'm trying via the recovery menu and it isn't working (the MM 6.0.1/ G935UUES4AQC1 install)
Thanks
(UPDATE - OK so I went back to the U firmware, and from that boot menu selected 'Wipe Partition/Cache'. Also did a factory reset which looked like it failed. Still couldn't boot phone though. However I went back to the verizon firmware and there was no passcode prompt now. Phone is factory reset to 6.0.1.
Should I go to QF2 now?
How can I get to a non-verizon firmware?)
OK, I've solved everything I mentioned above by doing as suggested,
I think I had a partition of something somewhere that was no good.
1 - Factory Reset from boot menu (after wiping partition/cache)
2 - Flashed PH1
3 - Verizon bloatware reinstalled and was loading phone properly
4 - Did a factory reset from here via settings
5 - After factory reset, Flashed QC1 w/out HOME_CSC
6 - Now booting properly with a clean(ish), non-Verizon firmware.
I'm still interested in removing as much bloat as possible from Samsung, and am constantly being harassed notified that my Nougat update is downloaded and ready to install!
Hope that helps someone!

Decrypting loop after OTA update

Hello fellow people of XDA!
Today I got an OTA update for my S7 edge (SM-G935F). The update has installed fairly fast (after the first reboot). But then, it got stuck on a decrypting loop. I have enabled prior the full phone encryption, and set it to ask for a password at each start. I entered the password correctly, as it said Starting Android... after, and since then, only the rotating padlock is showing. Every like 5 minutes the soft buttons are lighting up for a second, but then nothing is happening. After a while it even gets hot, but still nothing. I had this issue at the previous update too, but it started after like 30-40 minutes. Now 90 minutes have passed and still nothing.
I can reboot to the recovery and bootloader screens, and everything is fine. Knox not tripped, not rooted, everything official. In the recovery screen it says that my CSC is ECT (but according to sammobile it should be CNX).
Some additional info: samsung/hero2ltexx/hero2lte
7.0/NRD90M/G935FXXU2DRAG
I will try to flash a stock rom (PDA: G935FXXS2DRAA, CSC: G935FROM1DQJ3). If that doesn't work, I'll flash today's rom (PDA: same, CSC: G935FVFG1DQI1).
Any tips/help would be greately appreciated! Would not want to fall to the wipe data method, because I don't want to lose everything... But then again, I guess that would remove the boot password...
Thanks!
Update: After waiting for like 10+ hours, nothing has changed. Maybe I shouldn't have forced a reboot after an hour of the ota update? Going to try flashing the firmware now.
Update 2: I flashed the firmware, now the buttons seem to light up less often. But after an hour of decrypting, I guess the ultimate soultion would be to do a factory reset, since no one is helping...
jaszfalvi.tamas said:
Hello fellow people of XDA!
Today I got an OTA update for my S7 edge (SM-G935F). The update has installed fairly fast (after the first reboot). But then, it got stuck on a decrypting loop. I have enabled prior the full phone encryption, and set it to ask for a password at each start. I entered the password correctly, as it said Starting Android... after, and since then, only the rotating padlock is showing. Every like 5 minutes the soft buttons are lighting up for a second, but then nothing is happening. After a while it even gets hot, but still nothing. I had this issue at the previous update too, but it started after like 30-40 minutes. Now 90 minutes have passed and still nothing.
I can reboot to the recovery and bootloader screens, and everything is fine. Knox not tripped, not rooted, everything official. In the recovery screen it says that my CSC is ECT (but according to sammobile it should be CNX).
Some additional info: samsung/hero2ltexx/hero2lte
7.0/NRD90M/G935FXXU2DRAG
I will try to flash a stock rom (PDA: G935FXXS2DRAA, CSC: G935FROM1DQJ3). If that doesn't work, I'll flash today's rom (PDA: same, CSC: G935FVFG1DQI1).
Any tips/help would be greately appreciated! Would not want to fall to the wipe data method, because I don't want to lose everything... But then again, I guess that would remove the boot password...
Thanks!
Update: After waiting for like 10+ hours, nothing has changed. Maybe I shouldn't have forced a reboot after an hour of the ota update? Going to try flashing the firmware now.
Update 2: I flashed the firmware, now the buttons seem to light up less often. But after an hour of decrypting, I guess the ultimate soultion would be to do a factory reset, since no one is helping...
Click to expand...
Click to collapse
Wait, i dont get it, it is prompting you for a password even you didnt set it?
Sent from my S7 Edge using XDA Labs
shah22 said:
Wait, i dont get it, it is prompting you for a password even you didnt set it?
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
I set a password when I enabled Secure Startup.
jaszfalvi.tamas said:
I set a password when I enabled Secure Startup.
Click to expand...
Click to collapse
Then use that same password, i think there is confusion, there is a password when you enable fingerprint and then a password when you enable secure startup. Be sure not to confuse them. If it still happens, then I guess there's got something wrong with the update, and only way is a factory reset. Btw, i also updated and i normally entered secure boot password and it started okay. Don't know what caused this for you.
Sent from my S7 Edge using XDA Labs
shah22 said:
Then use that same password, i think there is confusion, there is a password when you enable fingerprint and then a password when you enable secure startup. Be sure not to remember them. If it still happens, then I guess there got something wrong with the update, and only way is a factory reset. Btw, i also updated and i normally entered secure boot password and it started okay. Don't know what caused this for you.
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
I entered the password correctly, as it stated "Starting Android..." then the rotating padlock took forever. More than 10 hours even. But in the end, a factory reset helped me. But rip my photos and memories...
Don't use device encryption anymore and leave OEM unlocking enabled in developer options.
Those two settings cause more hassle if you want to keep data, and make backups from time to time using Samsung Smart switch on computer. Use a microSD card to store and take all your photos from camera.
benjamen50 said:
Don't use device encryption anymore and leave OEM unlocking enabled in developer options.
Those two settings cause more hassle if you want to keep data, and make backups from time to time using Samsung Smart switch on computer. Use a microSD card to store and take all your photos from camera.
Click to expand...
Click to collapse
Right, but i use encryption and i could update without any problem, don't know what caused this issue with him. But one should backup all data BEFORE updating, as i did to save yourself from such hassle.
Sent from my S7 Edge using XDA Labs
benjamen50 said:
Don't use device encryption anymore and leave OEM unlocking enabled in developer options.
Those two settings cause more hassle if you want to keep data, and make backups from time to time using Samsung Smart switch on computer. Use a microSD card to store and take all your photos from camera.
Click to expand...
Click to collapse
Yeah, it's a sure thing I won't turn on Secure Stratup anymore. I don't know what OEM unlock does or does not, but right now, I don't have dev options enabled. If I had a microSD then I couldn't care less about resetting my phone, but since I don't have, because I have two SIM cards and a memory card has no place left, I feel bad.
Still, I don't know caused this issue. I had OTA updates before with full device encryption enabled and I had no issues before. I kinda used the same disk space at every OTA, so it should have took the same time... And I have to mention, that I did not tamper with the software. No root, no custom rom, and software only from the play store.
To enable developer options you click Build number 7 times which is located in the Software information tab in settings.
OEM unlock allows you to flash and boot the phone with custom binaries (Custom Recovery, Kernels, Roms). You can leave OEM unlock disabled if you don't want people that may steal your phone and use it for themselves.
With OEM unlock disabled and a google account signed in, it will block anyone from using the phone after a factory reset on stock Samsung firmware as it will prompt the user to enter the google account that was associated with that device.
Unfortunately there are rare cases that a OTA update may fail. Reflashing correct stock firmware usually fixes it but in worse case scenarios a factory reset will be required.
benjamen50 said:
To enable developer options you click Build number 7 times which is located in the Software information tab in settings.
OEM unlock allows you to flash and boot the phone with custom binaries (Custom Recovery, Kernels, Roms). You can leave OEM unlock disabled if you don't want people that may steal your phone and use it for themselves.
With OEM unlock disabled and a google account signed in, it will block anyone from using the phone after a factory reset on stock Samsung firmware as it will prompt the user to enter the google account that was associated with that device.
Unfortunately there are rare cases that a OTA update may fail. Reflashing correct stock firmware usually fixes it but in worse case scenarios a factory reset will be required.
Click to expand...
Click to collapse
Never had OEM unlock enabled, because I didn't know what is does, so thanks for the info. I reflashed the correct stock firmware, but that didn't help either, so I had to resort to wiping the data... Regarding this, do you know by any chance a good software for recovering data without root?
I don't know of any unfortunately, if anyone has any good paid ones that actually work please post here.

How to backup stock firmware & recovery?

Hi, recently I accidentally bricked my Galaxy Tab A 10.1 with Spen (SM-P580) by accidentally disabling "OEM Unlock" in the developer settings while I had TWRP and a custom ROM installed. I was only able to get into download mode due to the factory reset protection lock, so I tried downloading the stock firmware online and then flashing it to bring the device back to fully stock firmware so I could get past the lock and not have a brick. Unfortunately, when I flashed the firmware, despite it seemingly being for my specific device (and matching my build number), I was no longer able to boot the device at all. It would turn on and would seem to immediately lose power, charging would turn on the flash and cause it to heat up, and no amount of charging would fix the issue. It was completely bricked and there was no way for me to go back into download mode to try flashing again or try flashing a different firmware. Thankfully, I contacted Samsung and because it's still under warranty they were nice enough to fix it for free, and did so by completely replacing the motherboard according to the repair slip, which is not something I would have been able to do.
My question is: How do I make a full backup of the stock firmware and recovery so if this somehow ever happens again where the FRP lock kills my device, I can reflash in download mode the original firmware that I know is 100% going to work with it and is correct? I don't want to gamble with potentially using the wrong firmware again, seeing as that gamble killed the thing.
The Model is SM-P580NZKAXAR. Based on the last part (XAR) and the fact that other non-sammobile sites listed the US wifi only firmware as XAR, I assumed "Cellular south (XAR)" was the correct firmware I needed which was obviously incorrect as it completely bricked the device. For this reason, I'm wondering if there's a way with software on windows or something to completely backup the existing stock firmware before I do anything, because I doubt Samsung would be so nice a second time, and I'd really rather not go through all this again. Obviously these websites get the original firmware that's flashable via download mode somehow, so I'd like to know how or if that's possible. Also before I went and downloaded the firmware I checked the Samsung desktop app that allows you to fix firmware issues but it said my device wasn't supported so it wasn't much help. I'd like to avoid installing any custom recoveries ahead of time as if something gets messed up there will be no way for me to actually boot into recovery as far as I'm aware, and the FRP lock will block me from reflashing the custom recovery or anything else that isn't stock. It goes without saying that if this is possible I'd like to do it without installing a custom recovery or rooting as I'd like to have a proper fully stock backup that isn't going to trip the FRP lock.
Also the way I accidentally disabled OEM Unlock was I simply toggled the developer options off and then back on in a slimmed down version of the stock rom, but in doing so it also reset the OEM unlock setting and I completely forgot to make sure it was still enabled. Next thing I know I go to reboot (was trying to figure out an issue with a usb device) and then the thing was FRP locked. Needless to say, it was something extremely simple and easy to do by accident. I also just checked the device and the build number matches the firmware that I downloaded, so I don't know if it was mislabeled or what but something was not correct.

Categories

Resources