So I'm using androman's pre-rooted firmware for my G-361f, and have been able to install the fixed twrp. (Thanks guys!) I have oem-unlocked and adb-debugging selected in developer options, and have toyed with the seandroid-permissive boot.img from the androman thread. If I put my device into download-mode, it says frp-unlocked. However, if I register a gmail account to access google-play, then turn my device off, it will not boot because the 'custom binary frp-lock' is back again. (even though settings were unchanged)
No problem-flash stock rom with odin and start from the beginning, but to get the twrp recovery to work requires a factory reset, and so it's inconvenient to have to keep repeating the process.
My solution has been to delete my gmail account from the phone immediately every-time, as soon as I have whatever I need from google-play, but it seems like a cumbersome solution. I havn't found any other mention of this issue, so I'm wondering if I've missed something obvious? Is there a more permanent fix?
Thanks
Related
If a moderator can remove this thread, please go ahead!
I dug deeper into fallingup's recovery thread. It never occurred to me that it might make a difference to clear cache and factory reset AFTER doing an update. I did that, which seemed to clear up my FC loop. I fell into a page that asked me what language I was speaking, and was prompted to set up my google account -- which failed. Couldn't connect to data services, not even WIFI. So *228 and Activated my phone (again). Google still wouldn't log in. Went to Settings/Privacy/Factory reset. Selected English, google logged in this time. My phone appears to be completely back to its original stock state. Root is gone. Even bing is back, lovely. Thanks angel12!
... now if I could just figure out why that update.zip paired with the modem.tar that started all this wouldn't sing for me in recovery mode.
>>>>>>>>>>>>>>>>>>
First off, I apologize for cluttering this forum, but I'm at a bit of a loss here. I also failed to find the server for IRC. I'd really appreciate a small push.
Here goes: I got into download mode from the command line. I flashed over my modem with Odin, got a PASS, rebooted fully (shouldn't have done this) with no errors. Next, I popped into recovery mode. From there, I decided to factory reset _and_ wipe my cache -- it seemed like a good idea at the time. It seems like a bad idea now. Finally, I told recovery to apply update.zip from my sdcard. It flat out refused! Complained that the .zip wasn't signed. So, I rebooted.
I then experienced my first FC loop! The culprit is TouchWiz launcher, which just repeatedly closes unexpectedly.
So then I restored the DI01 modem, which didn't change a thing. Next, I ran Stock-i500-VZW-System.tar.md5 through Odin. It updated with no problems.
However, I still have my Force Close Loop, which I expected going to stock would fix.
What I think is really going on is I'd been using ADW Launcher, coupled with an app that switched it to being the 'default'. Something somewhere, must be giving TWiz a hard time.
The good news is I still have adb shell access and root.
* Is there anything I can do to make that homescreen switcher app run on my phone without using a launcher (from shell, for instance)?
* Is there some important point I'm missing about my recovery (I've flashed back everything I changed, at least in my mind)
* Perhaps I could flash something else from Recovery, and that would clear this up?
* It would be great to know what I did that messed this up.
EDIT:
I meant DI01, not "Di05". Nice catch!
It turned out in my case that data wipes were crucial - the factory wipe in system, and the data/factory reset &or cache partition in recovery mode.
http://forum.xda-developers.com/showthread.php?t=782204
Follow this to the letter. Been there, done that. Home Switcher isn't what went wrong. You'll be fine in 10 minutes.
Wait. DI05??? Do you mean DI01 or DJ05? You need to make sure you flash the modem that matches your ROM. Either easy is fine, and probably didn't have anything to do with your force close loop, but make sure they match or you won't be able to text.
And PDA in Odin.
Hi Folks,
So, something weird is happening to my phone--every time I attempt to enter the "Security" settings in my phone, the Settings app crashes.
Observations:
1. This happened when I attempted to add my company e-mail via the Email app.
2. Initial sync failed, so I removed the account and added it again.
3. Tried to add it again, success! It asked my to enter a 4-digit lock screen pin (for security).
4. Removed it again, but still can't open "Security".
This results in me not able to set (a) a new lock screen pattern (stuck with "Slide"), and (b) I cannot modify "Device Administrators".
Tried wiping data/cache/davlik cache, still no dice
I'm running stock everything. Rooted. 4.2.2.
Any help would be greatly appreciated. Thanks!
gamercado said:
Hi Folks,
So, something weird is happening to my phone--every time I attempt to enter the "Security" settings in my phone, the Settings app crashes.
Observations:
1. This happened when I attempted to add my company e-mail via the Email app.
2. Initial sync failed, so I removed the account and added it again.
3. Tried to add it again, success! It asked my to enter a 4-digit lock screen pin (for security).
4. Removed it again, but still can't open "Security".
This results in me not able to set (a) a new lock screen pattern (stuck with "Slide"), and (b) I cannot modify "Device Administrators".
Tried wiping data/cache/davlik cache, still no dice
I'm running stock everything. Rooted. 4.2.2.
Any help would be greatly appreciated. Thanks!
Click to expand...
Click to collapse
So were you rooted when you did the 4.2.2 ota update and used OTA rootkeeper?
You need to flash system.img and reroot.
There is a thread already about the security not working after OTA
DXM31 said:
So were you rooted when you did the 4.2.2 ota update and used OTA rootkeeper?
You need to flash system.img and reroot.
There is a thread already about the security not working after OTA
Click to expand...
Click to collapse
Yup i was rooted before flashing 4.2.2.
After flashing 4.2.2 I added my corporate e-mail, then removed it again.
Was stuck at the PIN lockscreen. Couldn't change it so i had to wipe data.
So I will flash system.img of 4.2.2 right?
Creating a duplicate thread won't improve your chances of getting the answer.
Closed.
There's a whole complicated series of events, but here's the current issue:
I just did a factory reset, and now when I go to 'Add Accounts' in settings, neither Google nor Samsung work. Google doesn't even ask for login credentials, just skips straight to 'checking info' and then fails. For Samsung, it takes my credentials and stops on a blank screen titled 'legal information,' and a non-functional 'next' arrow on the bottom. I've tried wiping the cache and a full reset, but no luck.
Now, the longer story: I just got the phone, and was trying to install TWRP etc. I got it to work once, but then realized I hadn't done the OEM unlock. Somehow ended up in a bootloop and ended up re-installing stock firmware. Tried again with OEM unlocked and got TWRP installed, but then after flashing no-verity-opt-encrypt 6.0, it went into a bootloop again. Reinstalled stock firmware again, but now I can't get the OEM unlock to show up, the date won't stick where I manually set it, and the Samsung/Google accounts won't work. Tried to install TWRP again anyway, but the install failed. Factory reset AGAIN to see if it would fix the accounts issue, but nothing changed.
I've tried googling the issues but couldn't find anything exactly like this, so I have come to kneel and beg the android gods for help. ANY assistance or suggestions on what to try would me most appreciated.
Here's the specs:
Galaxy S8 SM-G950F
Android 8.0
Used Odin3-v3.13.1 (didn't read about Prince Comsy ver. until after all this...)
Used twrp-3.2.3-2-dreamlte.img.tar
Used stock G950FXXS4CRLB_G950FOXM4CRL1_BTU
No SIM
If anymore info is needed, please let me know. Thank you.
So I rooted my phone following information on this site/a video guide from youtube (I dunno if I'm able to post links but I can PM if you need to see what it had me do etc) so I did a fresh root with TWRP, RMM bypass, no-verify encryption, magisk. All worked great the phone was rooted etc, I then stupidly removed google play services to try get an early date APK which caused issues so I thought a wipe with TWRP would fix the issue but the startup wizard wouldn't work, so I then removed startup wizard via TWRP got back into the phone and put the new version of play services on, yet still had issues so I got the default firmware for my model at samsmobile and put it on via odin - all worked great phone booted fine etc but some apps said a boot was detected, so I made sure to go into developer options and make sure the OEM was locked, did a wipe via the default options when holding power>bixy>up however some apps still say the phone is rooted.. I checked with a rootchecker and I pass the safety and it says no boot detected. So I dunno what the problem is? The only thing I did see was when I did the wipe this came up
"remove failed dir '/system/carrier/ATT/priv-app/AttIqi_ATT' (no such file or diectory)
e:[libfs_mgr] is_dt_compatible(): firmware info was not valid: '/proc/device-tree/firmware/android/compatible: no such file or directory"
Really dunno what to do from here.
bump
mrberta said:
So I rooted my phone following information on this site/a video guide from youtube (I dunno if I'm able to post links but I can PM if you need to see what it had me do etc) so I did a fresh root with TWRP, RMM bypass, no-verify encryption, magisk. All worked great the phone was rooted etc, I then stupidly removed google play services to try get an early date APK which caused issues so I thought a wipe with TWRP would fix the issue but the startup wizard wouldn't work, so I then removed startup wizard via TWRP got back into the phone and put the new version of play services on, yet still had issues so I got the default firmware for my model at samsmobile and put it on via odin - all worked great phone booted fine etc but some apps said a boot was detected, so I made sure to go into developer options and make sure the OEM was locked, did a wipe via the default options when holding power>bixy>up however some apps still say the phone is rooted.. I checked with a rootchecker and I pass the safety and it says no boot detected. So I dunno what the problem is? The only thing I did see was when I did the wipe this came up
"remove failed dir '/system/carrier/ATT/priv-app/AttIqi_ATT' (no such file or diectory)
e:[libfs_mgr] is_dt_compatible(): firmware info was not valid: '/proc/device-tree/firmware/android/compatible: no such file or directory"
Really dunno what to do from here.
Click to expand...
Click to collapse
BUMPITY BUMP BUMP, plz help my fwiend!
Hi everyone,
so in my immense stupidity, I actually managed to set my phone password wrongly, and now I can't get in. Spent a day trying passwords to find the typo but that was unsuccessful.
I have crDroid Android 11, bootloader unlocked, rooted with magisk, and TWRP 3.5.0.
How can get my phone back? I would love to save the internal storage since I have important stuff, but you know, if wiping it is the only way I have to go for it.
Thanks in advance.
Use this method. I have seen many people online suggesting it works.
Remove /Bypass Lockscreen With Recovery
Recently when i restored my data using TWRP i faced a problem at lock screen. I was not able to unlock my phone with the pin i set Earlier..So after so many attempts i was able to find a solution for that problem.(works with pattern,pin etc)...
forum.xda-developers.com
You are essentially removing lockscreen settings completely and should work as you still have TWRP access.
madman said:
Use this method. I have seen many people online suggesting it works.
Remove /Bypass Lockscreen With Recovery
Recently when i restored my data using TWRP i faced a problem at lock screen. I was not able to unlock my phone with the pin i set Earlier..So after so many attempts i was able to find a solution for that problem.(works with pattern,pin etc)...
forum.xda-developers.com
You are essentially removing lockscreen settings completely and should work as you still have TWRP access.
Click to expand...
Click to collapse
Thanks for the responce, but unfortunately that didn't work.
I deleted the files as explained in the thread you linked but now the lockscreen doesn't work at all, it's just a black screen. The power menu appears if I hold the power button, but nothing else. I tried swiping in some direction on the black screen but it doesn't unlock.
Also tried to sideload the rom again (dirty and clean flash), and magisk, still no luck.
Read the entire thread but nothing helpful.
DarkLudo77 said:
Thanks for the responce, but unfortunately that didn't work.
I deleted the files as explained in the thread you linked but now the lockscreen doesn't work at all, it's just a black screen. The power menu appears if I hold the power button, but nothing else. I tried swiping in some direction on the black screen but it doesn't unlock.
Also tried to sideload the rom again (dirty and clean flash), and magisk, still no luck.
Read the entire thread but nothing helpful.
Click to expand...
Click to collapse
Is TWRP able to decrypt the data? I'm guessing that's a no as the password is not accepted by the lockscreen. If TWRP was magically OK with the password, you could have adb pulled the files.
But apart from reseting the lockscreen using TWRP, I don't know a way to fetch the files.
madman said:
Is TWRP able to decrypt the data? I'm guessing that's a no as the password is not accepted by the lockscreen. If TWRP was magically OK with the password, you could have adb pulled the files.
But apart from reseting the lockscreen using TWRP, I don't know a way to fetch the files.
Click to expand...
Click to collapse
TWRP can decrypt if the correct passoword is provided. Tried pulling with adb the files anyway, even if they are encrypted, but the phone doesn't allow that either.
Thanks anyway