Related
GAH! So how screwed am I? I can't even get into recovery. I'm non-dev, bootloader unlocked and rooted. I was going to restore the tether hack in order to take the new OTA. I accidentally deleted build.prop and rebooted.
I can't get into recover at all holding down volume down + PWR. I only get the unlocked bootloader warning and that is it. Phone shuts down. Since the phone is essentially off, my PC never recognizes it to allow me to use RSD.
Any thoughts, ideas, suggestions?
Thanks!
lkevinl said:
GAH! So how screwed am I? I can't even get into recovery. I'm non-dev, bootloader unlocked and rooted. I was going to restore the tether hack in order to take the new OTA. I accidentally deleted build.prop and rebooted.
I can't get into recover at all holding down volume down + PWR. I only get the unlocked bootloader warning and that is it. Phone shuts down. Since the phone is essentially off, my PC never recognizes it to allow me to use RSD.
Any thoughts, ideas, suggestions?
Thanks!
Click to expand...
Click to collapse
OK, I was able to get into stock recovery. I'm going to look for the 21.11.21 files...
Just reflash the appropriate FXZ making sure to use House of Moto's keep data option
asuhoops8628 said:
Just reflash the appropriate FXZ making sure to use House of Moto's keep data option
Click to expand...
Click to collapse
Wow, I'm an idiot!! Can't believe I did that. So, I downloaded the 4.4.4 21.11.21 ZIP and I used fastboot/mfastboot to flash the boot images and system image. I stopped and didn't erase my data because this is the exact version I'm running, only the build.prop is missing. This did the trick.
In order to help anyone else in a similar jam, I will try to post links to where I downloaded and the forum page with the instructions I followed, but they're on my laptop so I'll have to do it later.
Big sigh of relief... I've never seen an android device of mine in that bad state before!
Thanks for your input!
lkevinl said:
Wow, I'm an idiot!! Can't believe I did that. So, I downloaded the 4.4.4 21.11.21 ZIP and I used fastboot/mfastboot to flash the boot images and system image. I stopped and didn't erase my data because this is the exact version I'm running, only the build.prop is missing. This did the trick.
In order to help anyone else in a similar jam, I will try to post links to where I downloaded and the forum page with the instructions I followed, but they're on my laptop so I'll have to do it later.
Big sigh of relief... I've never seen an android device of mine in that bad state before!
Thanks for your input!
Click to expand...
Click to collapse
That works too! Glad you got it working
hello my phone wont boot past Moto logo. just stays there. how did you get yours into recovery please?
---------- Post added at 07:27 AM ---------- Previous post was at 07:25 AM ----------
lkevinl said:
OK, I was able to get into stock recovery. I'm going to look for the 21.11.21 files...
Click to expand...
Click to collapse
how did get into recovery from a boot loop?
Hello,
On the Nexus, there is https://play.google.com/store/apps/details?id=net.segv11.bootunlocker that allow to lock/unlock on the fly the bootloader. Is there an equivalent app on the OnePlus One ?
Edit: Support of the OPO in the app added on 09/01/2015.
Why? There's no point in having the bootloader locked on this device.
timmaaa said:
Why? There's no point in having the bootloader locked on this device.
Click to expand...
Click to collapse
Well if you want me to justify, I will say it this way : think about what you can do when the device is unlocked, now what if your device is stollen...
If phone is stolen with bootloader locked, the thief can still unlock and do everything as per normal lol. Only thing is your info will be wiped. Which probably doesn't matter to thief anyways. But no I have seen such app for this phone
Sent From Lollipopified Bacon Goodness!
Xoib said:
Well if you want me to justify, I will say it this way : think about what you can do when the device is unlocked, now what if your device is stollen...
Click to expand...
Click to collapse
So take better care of your phone. It's a moot point anyway because anybody who steals your phone who actually knows what to do with an unlocked device will equally know how to unlock that device anyway. They steal the phone, see bootloader is locked, unlock bootloader with a single fastboot command, have their way with your phone. Which brings me back to my initial statement, the only thing you can do is take better care of your device. Honestly, I have no idea how people get their phones stolen, it simply means they're not taking enough care with it.
---------- Post added at 07:50 AM ---------- Previous post was at 07:49 AM ----------
ek69 said:
If phone is stolen with bootloader locked, the thief can still unlock and do everything as per normal lol. Only thing is your info will be wiped. Which probably doesn't matter to thief anyways. But no I have seen such app for this phone
Sent From Lollipopified Bacon Goodness!
Click to expand...
Click to collapse
My point exactly.
Well, I know all that, it's just a "feeling" of counter forensic to know that they will have to oem unlock (so wipe) to put a custom recovery to hope hacking into my datas...
Xoib said:
Well, I know all that, it's just a "feeling" of counter forensic to know that they will have to oem unlock (so wipe) to put a custom recovery to hope hacking into my datas...
Click to expand...
Click to collapse
That's not necessarily true, as after the oneplus has been unlocked once it's possible to unlock it again without wiping userdata - if you have a custom recovery installed any way.
But to provide an answer to your question, the closest I've seen is if you install AK kernel with UKM the kernel settings app (Synapse) has an option to toggle the bootloader lock status as well as the tamper flag status.
Of course that was the scenario if you put back the original recovery.
Thanks for AK Kernel suggestion, I will have a look.
Edit: Found http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
readers here might be interested in this...
The TWRP Password Protection Thread
http://forum.xda-developers.com/android/software-hacking/twrp-password-protection-thread-t2990816
Lanchon said:
readers here might be interested in this...
The TWRP Password Protection Thread
http://forum.xda-developers.com/android/software-hacking/twrp-password-protection-thread-t2990816
Click to expand...
Click to collapse
Hello @Lanchon, the case you describe in your point 2) is exactly what I had on my Nexus 4.
That's what I was looking for a on the fly bootlocker/unlocker in combination of putting only the custom recovery when needing to flash something.
I will also follow your thread.
Rkr87 said:
That's not necessarily true, as after the oneplus has been unlocked once it's possible to unlock it again without wiping userdata - if you have a custom recovery installed any way.
But to provide an answer to your question, the closest I've seen is if you install AK kernel with UKM the kernel settings app (Synapse) has an option to toggle the bootloader lock status as well as the tamper flag status.
Click to expand...
Click to collapse
I just noticed that option I normally just skip over that page lol. Dunno if it actually works though.
See screenshot
Sent From Lollipopified Bacon Goodness!
Rkr87 said:
That's not necessarily true, as after the oneplus has been unlocked once it's possible to unlock it again without wiping userdata - if you have a custom recovery installed any way.
Click to expand...
Click to collapse
Xoib said:
Edit: Found http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Click to expand...
Click to collapse
That script is what I was referring to when I said it's possible to unlock without wiping user data if you have a custom recovery installed
Powered by Bacon
Follow up: Support of the OPO has been aded to BootUnlocker (https://play.google.com/store/apps/details?id=net.segv11.bootunlocker)
I am helping a person try and retrieve photos from a Samsung Galaxy S6 that is stock at the lock screen. The finger print scan is not working and they do not know there back up password. I researched two ways to get around this.
1. Entering in the google account user name and password
2. Signing into Find My Mobile with the samsung account information and unlocking the phone
If both of these options fail due to the owner not remembering there above credentials is there any other way to retrieve photos. How about putting the phone in dfu mode and using a program on a computer to copy photos from the internal storage. Is something like this possible? Appreciate any help on this issue.
Maybe flash a stock ROM with Odin?
That way all the data stays in tact and it may remove lock screen.
Sent from my SM-G920I using XDA Premium HD app
Thanks for the quick response. The lady is paranoid about losing her photos! Therefore flashing with Odin Stock Rom will not remove any data from the phone. Do you have instructions or a link on how to do this.
I also am able to sign into her google account through the web browser, but when I use those credentials to try and unlock the Galaxy S6 it says that the user name or email is wrong. Thanks
Obagleyfreer said:
Maybe flash a stock ROM with Odin?
That way all the data stays in tact and it may remove lock screen.
Sent from my SM-G920I using XDA Premium HD app
Click to expand...
Click to collapse
Sounds like she could be learning a hard lesson. Backup passwords, knowing what accounts you used to setup, photo backups all exist for a reason.
krelvinaz said:
Sounds like she could be learning a hard lesson. Backup passwords, knowing what accounts you used to setup, photo backups all exist for a reason.
Click to expand...
Click to collapse
I totally agree with your assessment! I don't understand how I can log into her Gmail account via the web and then when I enter the same information at the Galaxy S6 Unlock via Google it does not work. Could this have something to do with not being connected to the internet. It is saying that 4G LTE is connected. Doesn't seem to be a way to connect it to WiFi without unlocking home screen.
If this was my phone I would have no trouble trying to flash the Odin stock Rom, but do not want to lose her info incase someone else can retrieve it. Does flashing the Odin stock ROM wipe everything on the phone or does it retain photos and other information. Thanks
I'm in this same situation. Is there anyway to retrieve the pictures? Flashing with Odin does not wipe the phone?
Wasn't life easier when we had removable sd cards...?
Flashing the system partition does not touch the data partition.
Do you know how she managed to break the fingerprint reader, by the way?
My G920F stuck on bootloop because of fail on rooting and I was afraid of losing all my photos. First I flashed TWRP with Odin, booted to recovery mode and pulled photos and videos out with adb. Then I flashed stock firmware with Odin and made a factory reset (not mandatory). Everything is working fine now.
dsimpe said:
My G920F stuck on bootloop because of fail on rooting and I was afraid of losing all my photos. First I flashed TWRP with Odin, booted to recovery mode and pulled photos and videos out with adb. Then I flashed stock firmware with Odin and made a factory reset (not mandatory). Everything is working fine now.
Click to expand...
Click to collapse
I suppose doing this you had USB debugging ENABLED before the boot-fail? Or does it turn on USB debug when flashing TWRP?
---------- Post added at 01:49 PM ---------- Previous post was at 01:43 PM ----------
WahFai said:
Wasn't life easier when we had removable sd cards...?
Flashing the system partition does not touch the data partition.
Do you know how she managed to break the fingerprint reader, by the way?
Click to expand...
Click to collapse
Agree WahFai, much simpeler with SD-card! So you think flashing system partition will do the trick. I'll go read up on that, how to flash the system partition. In my case, afaik, the fingerprint reader did not break. The system failed accepting the unlock code from one day to another and she does not remember the backup code for the reader. Thanks for your reply!
All she wants are the pictures on the phone. She recently got a baby, all the pictures of the delivery are on the phone, so you sense the urgency to not loose the pictures. She'll still feel the effects 18 years from now.
By the way: does flashing the stock rom with odin void the warranty? Because the phone is still on warranty...
Flashing a stock rom via odin will not trip knox but flashing a custom recovery will.
Thanks for clearing that out for me.
WahFai said:
Flashing a stock rom via odin will not trip knox but flashing a custom recovery will.
Click to expand...
Click to collapse
---------- Post added at 03:32 PM ---------- Previous post was at 02:58 PM ----------
EDIT:
So I'm downloading the stock firmware right now. Still a question: I'm not sure which firmware is on the phone right now. Is it a problem if I flash a newer, say the newest available, stock firmware on the phone?
Go on samsung kies and back up the phone and the photos come up
Sent from my SM-N910V using XDA Free mobile app
madchainsawer said:
Go on samsung kies and back up the phone and the photos come up
Sent from my SM-N910V using XDA Free mobile app
Click to expand...
Click to collapse
The phone is locked out, it does not show up on Kies. Actually it does show, but says its locked.
Ok, I now flashed the stock ROM again. It still comes back on the locked screen. HELP!!
bronxboy1 said:
Ok, I now flashed the stock ROM again. It still comes back on the locked screen. HELP!!
Click to expand...
Click to collapse
At this point, it sounds like flashing a custom recovery (TWRP) is your only option.
dsimpe said:
My G920F stuck on bootloop because of fail on rooting and I was afraid of losing all my photos. First I flashed TWRP with Odin, booted to recovery mode and pulled photos and videos out with adb. Then I flashed stock firmware with Odin and made a factory reset (not mandatory). Everything is working fine now.
Click to expand...
Click to collapse
Hey dsimpe, I am willing to try this option, since I cannot acces de mediafiles after flashing the stock ROM. Can you confirm this will trip Knox? And I installed ADB Studio. I cannot find a simple explanation on how to pull de media with adb. Can you help me please?
---------- Post added at 03:22 PM ---------- Previous post was at 03:20 PM ----------
Sevael said:
At this point, it sounds like flashing a custom recovery (TWRP) is your only option.
Click to expand...
Click to collapse
I just saw your post Sevael. I recon this is my only option now. I need to figure this out to pull the media, after that I can do a factory reset or whatever, but I never used ADB before. Thanks for your reply.
bronxboy1 said:
Hey dsimpe, I am willing to try this option, since I cannot acces de mediafiles after flashing the stock ROM. Can you confirm this will trip Knox? And I installed ADB Studio. I cannot find a simple explanation on how to pull de media with adb. Can you help me please?
Click to expand...
Click to collapse
Check droidviews article of "How to Push and Pull Files on Android using the ADB commands".
I'm pretty sure that knox will be tripped.
Also go to my profile and check thread that I've started. I explain there how I did it.
If you've any problems post here or pm me.
I now found the instructions on how to pull files with ADB. I connected the phone to my pc and checked if the device was recognized. This was not the case. Does this mean, that the USB debugging was not enabled?
Edit: Thanks dsimpe. Saw the post too late again. Note to self: need to refresh page before making a reply... I'll go check out your posts. Thanks again.
bronxboy1 said:
I now found the instructions on how to pull files with ADB. I connected the phone to my pc and checked if the device was recognized. This was not the case. Does this mean, that the USB debugging was not enabled?
Edit: Thanks dsimpe. Saw the post too late again. Note to self: need to refresh page before making a reply... I'll go check out your posts. Thanks again.
Click to expand...
Click to collapse
My device wasn't recognized either before I flashed TWRP with Odin and I booted to recovery mode.
Ok, tnx dsimpe. I guess USB debugging must have been turned on before also on the phone? And can you confirm knox will be tripped?
Verstuurd vanaf mijn GT-N7100 met Tapatalk
What should we do? For myself at this moment, I do not need root or custom roms. I have read many people recommending staying on stock for OTAs updates right now. The only reason I want TWPR is for the nandroid backups of the stock rom. Is it even possible to update stock, the OTA updates and reapply the unlock bootloader and TWPR afterwards? I know TWPR is still being working on at this moment. Also, is there even a stock rom [for FRD-AL04???] without root available through TWPR right now?
I believe I have FRD-AL04 which is the US/32 gig phone, right? Is this the correct model? Here is the link to amazon page.
Mine is the US 32gb black Honor 8 and model number is FRD-L04
Edit: Check your model number in the Settings > About Phone screen.
---------- Post added at 04:30 PM ---------- Previous post was at 04:22 PM ----------
On whether to stay stock or not... it's up to you. I unlocked my phone, which wipes it, then installed TWRP and SuperSU for root. Kept the ROM stock. But then I realized I forgot to do OTA updates first. Doing a quick update failed because TWRP didn't know what to do. I then selected a "Full Update" in the menu of the Updater. This actually completely wiped out my unlocked bootloader, recovery and root in one swoop. So now I am back to stock it seems so I'll have to unlock and start over if I want to redo it. But I'm not sure I am going to. I started using Helium made by the team that made ClockworkMod. It isnt able to back up ALL app data, but it does get a nice chunk of it which I think will be good enough for me for now.
Stay on stock until company stops pushing out OTA updates. I do this on all my phones.
tekkitan said:
Mine is the US 32gb black Honor 8 and model number is FRD-L04
Edit: Check your model number in the Settings > About Phone screen.
---------- Post added at 04:30 PM ---------- Previous post was at 04:22 PM ----------
On whether to stay stock or not... it's up to you. I unlocked my phone, which wipes it, then installed TWRP and SuperSU for root. Kept the ROM stock. But then I realized I forgot to do OTA updates first. Doing a quick update failed because TWRP didn't know what to do. I then selected a "Full Update" in the menu of the Updater. This actually completely wiped out my unlocked bootloader, recovery and root in one swoop. So now I am back to stock it seems so I'll have to unlock and start over if I want to redo it. But I'm not sure I am going to. I started using Helium made by the team that made ClockworkMod. It isnt able to back up ALL app data, but it does get a nice chunk of it which I think will be good enough for me for now.
Click to expand...
Click to collapse
Few questions if you don't mind.
1. Are you saying that even with unlocked bootloader and custom recovery you're still able to accept the OTA?
2. How would you restore the apps&data after accepting the OTA and going throu the unlocking/rooting process over again? Does Helium handle this w/o problems?
Thanks.
well, your question is complicated... but it has many type of sollutions
1.if its the nandroid backup is the only thing you want, then try backing up via honorsuit app,,
2.you can unlock the bootloader( dont worry you still be getting updates after this)
install twrp
make a backup
and find if someone did a backup with stock recovery
grab it
restore..
now you have your backup and youl be elligable for ota
3. if theres no one done a backup of stock recovery, dont worry... you can do it
unlock bootloader
now type fastboot devices
fastboot boot recovery twrp.img
this will temperorily boot twrp and you can have your backup
and BTW, you better be on stock, because, there is no stable custom rom yet and you are nearly getting a nougat update..:good:
mimin0 said:
Few questions if you don't mind.
1. Are you saying that even with unlocked bootloader and custom recovery you're still able to accept the OTA?
2. How would you restore the apps&data after accepting the OTA and going throu the unlocking/rooting process over again? Does Helium handle this w/o problems?
Thanks.
Click to expand...
Click to collapse
1. Yes, but only if you select the FULL download update in the menu of the updater (which says it's around 1.6GB). This will wipe out your unlock, TWRP and root though. At least it did for me.
2. I don't know, I didn't re-unlock it because it was going to wipe my phone again. I decided to stay stock for now using Helium backup to backup my apps, SMS, etc.
tekkitan said:
Mine is the US 32gb black Honor 8 and model number is FRD-L04
Edit: Check your model number in the Settings > About Phone screen.
---------- Post added at 04:30 PM ---------- Previous post was at 04:22 PM ----------
I started using Helium made by the team that made ClockworkMod. It isnt able to back up ALL app data, but it does get a nice chunk of it which I think will be good enough for me for now.
Click to expand...
Click to collapse
I can't even get Helium to get past asking me for PTP mode on my H8. Even though I select PTP in the notifications and/or in the dev settings.
scoobydu said:
I can't even get Helium to get past asking me for PTP mode on my H8. Even though I select PTP in the notifications and/or in the dev settings.
Click to expand...
Click to collapse
I also had this problem at first. I ended up having to switch from using their chrome add-on to installing the client for my OS (OS X in my case). So if you're using the chrome add-on try installing one of the clients instead.
tekkitan said:
I also had this problem at first. I ended up having to switch from using their chrome add-on to installing the client for my OS (OS X in my case). So if you're using the chrome add-on try installing one of the clients instead.
Click to expand...
Click to collapse
Ok thanks, but I am already using the OSX app myself. Managed to get it to work just now, had to reboot and now can't get it to work again. Some say to select 'midi' instead of ptp to get it to work, but that doesn't work for me either. Seems its a timing thing and I have't worked it out yet.
Not having a cross platform backup mechanism certainly doesn't help people stay stock without root imho.
The phone was stuck on Logo and wont start. Now i see this :
https://drive.google.com/open?id=0Bxome1ZSCRIaVHg5a0VvU3VqamM
Thanks in advance
diretouch said:
The phone was stuck on Logo and wont start. Now i see this :
https://drive.google.com/open?id=0Bxome1ZSCRIaVHg5a0VvU3VqamM
Thanks in advance
Click to expand...
Click to collapse
Power off the device then try booting to download mode (volume down+home+power, press up when prompted). If you can get to download mode, try flashing the stock firmware.
Sent from my SM-S903VL using Tapatalk
The phone is recognised in Odin.
Can i save my personal data while install firmware?
Here
http://samsung-updates.com/device/?id=GT-i9300
i see 4 BGL version. How to understand which to install ?
I cannot enter recovery. I see the image i showed in first post
There is no a way -that I know of- other than trying to flash twrp, then doing a backup and moving it to the PC this voids warranty
The devices has no warranty.
Then go ahead flash twrp
What is your device model?
---------- Post added at 04:15 PM ---------- Previous post was at 04:11 PM ----------
Forgot to mention that if you didn't enable OEM unlock it won't work and cause a trouble
Gt-i9300.
I am located in eastern Europe - Bulgaria
Thanks
diretouch said:
Gt-i9300.
I am located in eastern Europe - Bulgaria
Thanks
Click to expand...
Click to collapse
Do u have OEM unlock enabled in dev options before now or not?
Can i see that in Odin mode?
The phone is not mine
diretouch said:
The phone is recognised in Odin.
Can i save my personal data while install firmware?
Here
http://samsung-updates.com/device/?id=GT-i9300
i see 4 BGL version. How to understand which to install ?
I cannot enter recovery. I see the image i showed in first post
Click to expand...
Click to collapse
Of the 4 that you found, you need to install the one that works for the mobile carrier that the device is used with.
Sent from my SM-S903VL using Tapatalk
---------- Post added at 01:37 AM ---------- Previous post was at 01:33 AM ----------
-Hope- said:
Then go ahead flash twrp
What is your device model?
---------- Post added at 04:15 PM ---------- Previous post was at 04:11 PM ----------
Forgot to mention that if you didn't enable OEM unlock it won't work and cause a trouble
Click to expand...
Click to collapse
The OEM unlock setting itself has nothing to do with whether TWRP can be flashed. That is just a setting that "allows" you to unlock the bootloader, it doesn't unlock the bootloader, it only puts the device in a state that the bootloader "can" be unlocked if there is a known unlock method.
You can enable OEM unlock as many times as you want, that doesn't mean the bootloader is unlocked. The bootloader has to actually be unlocked using an unlock method.
Sent from my SM-S903VL using Tapatalk
---------- Post added at 01:42 AM ---------- Previous post was at 01:37 AM ----------
diretouch said:
Can i see that in Odin mode?
The phone is not mine
Click to expand...
Click to collapse
No, you can't, that has to be changed in system settings, you can't get to the settings because of your screen.
Forget about TWRP. Just flash the same android version that the device had before the issue started and the data won't get wiped. When it comes to flashing Samsung devices with Odin, the only time it wipes your data is when a firmware is flashed that has an upgraded or downgraded bootloader compared to what was already on the device. Flash the same thing the device already had and you won't lose anything.
Sent from my SM-S903VL using Tapatalk
---------- Post added at 01:45 AM ---------- Previous post was at 01:42 AM ----------
-Hope- said:
Do u have OEM unlock enabled in dev options before now or not?
Click to expand...
Click to collapse
You need to slow down and pay attention to details about what people post when describing their issue. You are so impatient to answer that you are posting irrelevant and confusing information for their circumstances. They can't boot this device or get to settings. If they attempt to flash TWRP while their bootloader is locked, it could make things worse. Consider the consequences of what you suggest and consider that most people don't know what they are doing and don't know the risks involved or how to check that your suggestions are safe before they do them. They could blindly walk into a bigger problem.
In this situation, the bootloader could very well be locked without them being aware that it's locked.
In the future, I wouldn't suggest that they flash TWRP when the bootloader can't be confirmed. Stop making suggestions if you can't confirm anything.
Making suggestions without being certain of the state of their device will at some point lead to you telling them to do something that makes things worse instead of helping them. I know you really want to help, but jumping the gun and making suggestions can lead to causing more harm than helping.
Make suggestions that you are "certain" will work, don't make suggestions that "could" work under the right conditions. In this case, you can't be certain that flashing TWRP will work so you should not have suggested it, understand? If the bootloader is locked and they flash TWRP but it bricks the device because the bootloader is locked, what then? Bricking the device will be your fault because you suggested something without being certain. You should have asked more questions and gotten more information about the exact state of this device and it's bootloader status, then, if everything is correct, suggesting to flash TWRP would be safe.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
Of the 4 that you found, you need to install the one that works for the mobile carrier that the device is used with.
Sent from my SM-S903VL using Tapatalk
---------- Post added at 01:37 AM ---------- Previous post was at 01:33 AM ----------
The OEM unlock setting itself has nothing to do with whether TWRP can be flashed. That is just a setting that "allows" you to unlock the bootloader, it doesn't unlock the bootloader, it only puts the device in a state that the bootloader "can" be unlocked if there is a known unlock method.
You can enable OEM unlock as many times as you want, that doesn't mean the bootloader is unlocked. The bootloader has to actually be unlocked using an unlock method.
Sent from my SM-S903VL using Tapatalk
---------- Post added at 01:42 AM ---------- Previous post was at 01:37 AM ----------
No, you can't, that has to be changed in system settings, you can't get to the settings because of your screen.
Forget about TWRP. Just flash the same android version that the device had before the issue started and the data won't get wiped. When it comes to flashing Samsung devices with Odin, the only time it wipes your data is when a firmware is flashed that has an upgraded or downgraded bootloader compared to what was already on the device. Flash the same thing the device already had and you won't lose anything.
Sent from my SM-S903VL using Tapatalk
---------- Post added at 01:45 AM ---------- Previous post was at 01:42 AM ----------
You need to slow down and pay attention to details about what people post when describing their issue. You are so impatient to answer that you are posting irrelevant and confusing information for their circumstances. They can't boot this device or get to settings. If they attempt to flash TWRP while their bootloader is locked, it could make things worse. Consider the consequences of what you suggest and consider that most people don't know what they are doing and don't know the risks involved or how to check that your suggestions are safe before they do them. They could blindly walk into a bigger problem.
In this situation, the bootloader could very well be locked without them being aware that it's locked.
In the future, I wouldn't suggest that they flash TWRP when the bootloader can't be confirmed. Stop making suggestions if you can't confirm anything.
Making suggestions without being certain of the state of their device will at some point lead to you telling them to do something that makes things worse instead of helping them. I know you really want to help, but jumping the gun and making suggestions can lead to causing more harm than helping.
Make suggestions that you are "certain" will work, don't make suggestions that "could" work under the right conditions. In this case, you can't be certain that flashing TWRP will work so you should not have suggested it, understand? If the bootloader is locked and they flash TWRP but it bricks the device because the bootloader is locked, what then? Bricking the device will be your fault because you suggested something without being certain. You should have asked more questions and gotten more information about the exact state of this device and it's bootloader status, then, if everything is correct, suggesting to flash TWRP would be safe.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Thanks for the advises
i've already asked them if they had it enabled, ik it will cause "custom binary blocked by frp" which means he wouldn't be able to do much but reflashing a system again
it was a question, but yeah i think I've made things complicated sorry
And thanks again