|
Welcome to the GSM-Forum forums. You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. Only registered members may post questions, contact other members or search our database of over 8 million posts. Registration is fast, simple and absolutely free so please - Click to REGISTER! If you have any problems with the registration process or your account login, please contact contact us . |
|
Register | FAQ | Donate | Forum Rules | Root any Device | ★iPhone Unlock★ | ★ Direct Codes ★ | Direct Unlock Source |
| LinkBack | Thread Tools | Display Modes |
02-05-2018, 06:19 | #1 (permalink) |
No Life Poster Join Date: Jan 2018
Posts: 574
Member: 2802156 Status: Offline Thanks Meter: 173 | About bypassing Secure Startup (not lockscreen) in Samsung S7 and other mod This is a request to start a discussion about this in general; but for a specific instance - G935t BQL1 7.0 Unsecured ADB is on via eng root for this model, however not much what can be done through it. Getting into the phone's internal sdcard is not possible - shows up as empty. As do the other areas, such as android/data etc. If the commands to remove lockscreen passcode are run then doing so merely removes the passcode for general lockscreen, though not the secure startup..not possible to get past the secure startup "lockscreen" which appear when booting up the phone from off state. Furthermore, the secure startup screen has emergency dialer, and phone gives a com port for modem; in GCPRO attempting to bypass lockscreen via emergency dialer method gives the phone's information accurately, such as IMEI, Build number, model, etc, but doesn't actually do any change to the phone. Perhaps flashing some parts of combination, or full combination without system/userdata (to preserve data obviously) will bypass this SS? I have not seen this being discussed anywhere on the forums or even clangsm, or the russian gsmhosting equivalents; anyone please advise thanks br Last edited by gsm_service4u; 02-05-2018 at 06:21. Reason: error in title, phrasing |
Bookmarks |
| |
|