Affected models:
Galaxy Tab 8.9" P7300 (confirmed by me) / P7310 (confirmed by whitehart)
Galaxy Tab 7.7" P6810 (confirmed by sebi1964)
Other Galaxy Tab series, including 10.1" (lot's of complaints on XDA, please confirm in this thread)
Symptoms:
No lockscreen, regardless of the setting
"Factory Mode" icon on homescreen, that opens up a calculator
Power button powers off the device instantly: no menu appears
No setup wizard after factory reset
Open Lock icon at boot screen - maybe it's not a related issue (please confirm)
Myth:
Only Samsung repair center can fix it - FALSE!
Workaround:
Type *#7594# in the Factory Mode application and uncheck the box in the Shutdown App that appears after entering the code - Works in some cases, temporarily, till you restart
Fix:
Rooted device
Mounted /efs partition (if in recovery)
Execute the following commands:
Code:
adb shell
su
echo -n ON > /efs/imei/keystr
chown 1001:1001 /efs/imei/keystr
Reboot device
Optionally: factory reset to get rid of the Factory Mode icon (or just delete it from homescreen)
Result:
All of the symptoms mentioned above are gone, except the lock icon at boot screen.
Needs investigation:
The lock at the boot screen may, or may not be related to the issue. It happens on my P7300, but to the following user's P7510 too: http://forum.xda-developers.com/showpost.php?p=18833764&postcount=1
What are the advantages of having a Galaxy Tab with unlocked bootloader? Or disavantages of having a locked one? How to relock?
Reference:
I've adopted Odia's solution for the Galaxy S3, spent some time with reverse engineering to see if it applies to our Tab's, if so, what are the differences, and voila!
Donators:
wojt.eu
RipplingHurst
Donations are always welcome PayPal
*#7594# did not work on my P6810
sebi1964 said:
*#7594# did not work on my P6810
Click to expand...
Click to collapse
7.7" might need different syled commands, try *#*#7594#*#*
tracid said:
7.7" might need different syled commands, try *#*#7594#*#*
Click to expand...
Click to collapse
Same thing. Is something like this "enable shutdown at long press...". It is not checked. But even if is checked or not my lockscreen missing.
sebi1964 said:
Same thing. Is something like this "enable shutdown at long press...". It is not checked. But even if is checked or not my lockscreen missing.
Click to expand...
Click to collapse
If the "enable shutdown at long press" is unchecked, does changing the setting at Settings -> Location and security -> configure lock screen have any effect?
I suppose you have the Factory Mode icon, else you couldn't type in the code, right?
EDIT: I've helped sebi1964 and my fix solved his problem.
Open lock icon on boot screen just means you have a fully unlocked (nvflash is accessible) Tegra device. About half of Tab 10.1s sold were like this, many of them got locked by an update but if you never took the update in question it would remain unlocked.
Some of the other stuff I have seen once - on a special developer device (with socketed eMMC) in the hands of a Samsung engineer. It was an I9100.
Entropy512 said:
Open lock icon on boot screen just means you have a fully unlocked (nvflash is accessible) Tegra device. About half of Tab 10.1s sold were like this, many of them got locked by an update but if you never took the update in question it would remain unlocked.
Some of the other stuff I have seen once - on a special developer device (with socketed eMMC) in the hands of a Samsung engineer. It was an I9100.
Click to expand...
Click to collapse
Yes, I've read about those 10.1". But this is a 8.9". So the only advantage is that I boot into nvflash (APX?) mode without the battery drain trick?
Yeah i got my P7500 in factory mode after had a main-board and screen replacement(under warranty) all the symptoms are correct.
I have to returned it back to Samsung and the technician doesn't even know what to do, after much debate that i want the factory mode gone finally it returned to normal mode. I didn't know what Samsung did, but my guess is that my tab doesn't have imei and board serial number and missinf efs folder, that is why it is entering in factory mode. just a guess though as when i check last time my serial and imei was 0000 and 0000 something.
I wish people acknowledge this problem back then, i felt like an idiot asking in the forum and no one else had it and everyone said that i had done something wrong.
Fortunately samsung fixed the tablet.
My major problem with tablet in "factory mode" is that power button shuts off tablet immediately without menu,
cheers.
tracid said:
Yes, I've read about those 10.1". But this is a 8.9". So the only advantage is that I boot into nvflash (APX?) mode without the battery drain trick?
Click to expand...
Click to collapse
No, the advantage is you can actually USE APX mode - if locked, APX mode requires a key that we don't know.
Tab 10.1 and having the same issue.
I had installed a custom firmware after it returned from repair and had no issues. The issues started after I updated to the official ICS rom. But there is no factory mode app to be seen on the phone. However all the symptoms persist.
I tried to run the adb commands through recovery but it just keeps giving me not found errors.
When I try in debug mode the commands go through by the looks of it. Is it supposed to show me some sort of an output on cmd ?
Either way after the reboot issues still persist. :/ Any ideas?
Try to mount /efs partition from the "Mounts and storage" menu in recovery.
Posting here as it seems more people post here
I have same issue after the device was repaired (new board) I have tried the code with teh device rooted, the only thing that works is the engineers code which is temp, as soon as you reboot it its lost'
Here is my original post (8.9 tablet)
http://forum.xda-developers.com/showthread.php?p=31680609#post31680609
If anyone can help it would be great otherwise it'll have to go back to the repair centre again
thanks in advance
What do the commands return in terminal?
tracid said:
What do the commands return in terminal?
Click to expand...
Click to collapse
managed to get it to work, I did a reset factory data
rebooted now it has the lock screen - soo pleased - I've rebooted it a few times and it seems fine now fingers crossed its fixed
Cheers
Glad you did it. It's a P7300 or P7310?
tracid said:
What do the commands return in terminal?
Click to expand...
Click to collapse
tracid said:
Glad you did it. It's a P7300 or P7310?
Click to expand...
Click to collapse
P7310
i have all 4 first Symptoms on sgs3
and i did the solutions and nothing works please help!!
baster72 said:
and i did the solutions and nothing works please help!!
Click to expand...
Click to collapse
There's a link in the first post to Odia's solution for SGS3... http://forum.xda-developers.com/showpost.php?p=28113616&postcount=14
tracid said:
There's a link in the first post to Odia's solution for SGS3... http://forum.xda-developers.com/showpost.php?p=28113616&postcount=14
Click to expand...
Click to collapse
I've tried this on a Gt-P5113 and it works.
1. Root the device and then download SuperUser first and Terminal Emulator from Google Play store.
2. After that launch SuperUser app and then use Terminal Emulator to type in the following commands:
Code:
su
echo -n ON > /efs/FactoryApp/factorymode
That should solve the issue.
---------- Post added at 07:18 AM ---------- Previous post was at 07:13 AM ----------
One more thing is that for me, I've also tried to flash it back to an original ROM to remove root and I noticed that the edited settings are persistent.
baster72 said:
and i did the solutions and nothing works please help!!
Click to expand...
Click to collapse
me too.I have GS3. Please help us
Related
http://forum.xda-developers.com/showthread.php?p=40782218
In the above thread, does this method work with the stock sony Xperia T firmwares
please can you post your firmware version (stock only, no cm, no aokp or custom roms) and let me know
if it worked.
Basically I want to access my wifes phone and check her messages as she has been acting weird
I tried the service menu trick on her phone but it didn't work which means her phone has more up to date firmware i believe
EDIT found this
http://forum.xda-developers.com/showthread.php?t=2244741
Can someone confirm it works on xperia T?
owen1978 said:
http://forum.xda-developers.com/showthread.php?p=40782218
In the above thread, does this method work with the stock sony Xperia T firmwares
please can you post your firmware version (stock only, no cm, no aokp or custom roms) and let me know
if it worked.
Basically I want to access my wifes phone and check her messages as she has been acting weird
I tried the service menu trick on her phone but it didn't work which means her phone has more up to date firmware i believe
Can someone confirm it works on xperia T?
Click to expand...
Click to collapse
Just tried that for you, it didn't work; the Emergency dial screen wouldn't accept the *#*#73556673#*#* code.
The lock screen WAS disabled whilst the Demo was active but as pressing the power button to wake the screen was immediately rerunning the Demo I'm sure that would get noticed. (Xperia T firmware 9.1.A.1.141).
Might have time to test out the 2nd link you posted later.
BarneyJ said:
Just tried that for you, it didn't work; the Emergency dial screen wouldn't accept the *#*#73556673#*#* code.
The lock screen WAS disabled whilst the Demo was active but as pressing the power button to wake the screen was immediately rerunning the Demo I'm sure that would get noticed. (Xperia T firmware 9.1.A.1.141).
Might have time to test out the 2nd link you posted later.
Click to expand...
Click to collapse
1) Did the demo run?
2) Did you then press home button to go to the home screen?
3) Did you then bring up dialer and type in the demo code again to disable the demo?
http://www.youtube.com/watch?v=gRelLSb0vgw&feature=youtu.be
In the video when the demo is running he taps it to bring up the home button, did this work on yours?
Thanks v much
owen1978 said:
1) Did the demo run?
2) Did you then press home button to go to the home screen?
3) Did you then bring up dialer and type in the demo code again to disable the demo?
http://www.youtube.com/watch?v=gRelLSb0vgw&feature=youtu.be
In the video when the demo is running he taps it to bring up the home button, did this work on yours?
Thanks v much
Click to expand...
Click to collapse
1) The Demo ran when the phone was already unlocked and I typed in the code from the dialer - on first run it even prompts you that it will change the screen unlock password.
2) Yes pressing the home button went to the Home screen (at this point if you switch the screen off then back on the Demo reruns).
3) Yes I did.
The code doesn't seem to work at the Emergency Call screen on my Xperia T, or perhaps the phone he's using in the Video doesn't have the most current firmware.
BarneyJ said:
1) The Demo ran when the phone was already unlocked and I typed in the code from the dialer - on first run it even prompts you that it will change the screen unlock password.
2) Yes pressing the home button went to the Home screen (at this point if you switch the screen off then back on the Demo reruns).
3) Yes I did.
The code doesn't seem to work at the Emergency Call screen on my Xperia T, or perhaps the phone he's using in the Video doesn't have the most current firmware.
Click to expand...
Click to collapse
It is possible you can test the zip file method?
I'm on my way to work now, I'll try the 2nd thread a little later. I'll have to try Method B in that thread because I don't currenty have CWM recovery on my phone which is required for Method A using the Zip file.
BarneyJ said:
I'm on my way to work now, I'll try the 2nd thread a little later. I'll have to try Method B in that thread because I don't currenty have CWM recovery on my phone which is required for Method A using the Zip file.
Click to expand...
Click to collapse
ahh ok, neither does her phone so that wont work.... never mind thanks for your help
Had a thought what if I flash an older version of firmware which has the service menu security hole?
Would just have simply plug her phone in, flash it, and then let it restart (wiping only cache and dalvik, if they are available in stock recovery)
So she won't lose any of her data and won't be any wiser?
hmmm....
BarneyJ said:
I'm on my way to work now, I'll try the 2nd thread a little later. I'll have to try Method B in that thread because I don't currenty have CWM recovery on my phone which is required for Method A using the Zip file.
Click to expand...
Click to collapse
Ahh was reading too quickly method b doesnt require CWM... ok, if you can give this a try and get back to me it would be much appreciated
owen1978 said:
EDIT found this
http://forum.xda-developers.com/showthread.php?t=2244741
Can someone confirm it works on xperia T?
Click to expand...
Click to collapse
I've tested a similar method on windows that worked on my T on JB.
all it needed was a
adb shell
su
rm /data/system/gesture.key
Click to expand...
Click to collapse
This of course has limitations, the device needs to be rooted and usb debugging must be enabled
owen1978 said:
Ahh was reading too quickly method b doesnt require CWM... ok, if you can give this a try and get back to me it would be much appreciated
Click to expand...
Click to collapse
matt4321 said:
I've tested a similar method on windows that worked on my T on JB.
all it needed was a
adb shell
su
rm /data/system/gesture.key
Click to expand...
Click to collapse
This of course has limitations, the device needs to be rooted and usb debugging must be enabled
Click to expand...
Click to collapse
Well I suspected that USB debugging would need to be enabled to use the B Method in that thread you linked and what Matt has said Tally's with this; I've now had time to try and can confirm this.
Matt's commands worked when I substituted 'password.key' instead of 'gesture.key' in the 3rd line (I had a PIN lock set) - 'gesture.key' seems to be for when a pattern lock is set, and 'password.key' for PIN lock.
Method B in that thread is missing the 'su' line that Matt has above, so failed with 'Permission Denied' when trying to delete the .key files - works once you add the su command.
What's up guys, I purchased a Nexus 6 during the black friday deal on Amazon for $200.
I tried unlocking my Nexus 6 via WugFresh's RootToolkit. Unfortunately it doesn't seem to be working properly, the adb and fastboot both connect and everything works as it should (prompt wise) but when I received the option to confirm whether I want to unlock my bootloader, after clicking yes it goes through the reboot but nothing happens. I'm back to where I started (nothing wiped, all apps still there, nada).
USB Debugging is enabled, app verification is off (tried it with both on and off) and enable OEM unlock is also enabled.
Drivers are properly configured and any other discrepancies have been removed via the RootToolkit. Not quite sure what the issue is, I'd appreciate any help on the matter!
Also the bootloader status is displayed like this: Bootloader - Locked [Status Code: 2]
Other info:
Currently on 6.0
Build number: MRA58N
Android Security Patch level: November 1st, 2015
Thanks in advance guys.
Necrodox said:
What's up guys, I purchased a Nexus 6 during the black friday deal on Amazon for $200.
I tried unlocking my Nexus 6 via WugFresh's RootToolkit. Unfortunately it doesn't seem to be working properly, the adb and fastboot both connect and everything works as it should (prompt wise) but when I received the option to confirm whether I want to unlock my bootloader, after clicking yes it goes through the reboot but nothing happens. I'm back to where I started (nothing wiped, all apps still there, nada).
USB Debugging is enabled, app verification is off (tried it with both on and off) and enable OEM unlock is also enabled.
Drivers are properly configured and any other discrepancies have been removed via the RootToolkit. Not quite sure what the issue is, I'd appreciate any help on the matter!
Also the bootloader status is displayed like this: Bootloader - Locked [Status Code: 2]
Other info:
Currently on 6.0
Build number: MRA58N
Android Security Patch level: November 1st, 2015
Thanks in advance guys.
Click to expand...
Click to collapse
Stop using root kits and learn to do things properly. It is as simple as changing a setting and then doing one command prompt imput. A search will show you what you need to know.
zelendel said:
Stop using root kits and learn to do things properly. It is as simple as changing a setting and then doing one command prompt imput. A search will show you what you need to know.
Click to expand...
Click to collapse
Already tried running from the terminal, no luck.
Necrodox said:
Already tried running from the terminal, no luck.
Click to expand...
Click to collapse
Did you change the setting in developer settings to allow bootloader unlocking?
zelendel said:
Did you change the setting in developer settings to allow bootloader unlocking?
Click to expand...
Click to collapse
Yup, mentioned that in my original post.
I'm going to uninstall all the drivers and reconfigure everything, maybe that'll help.
Necrodox said:
Yup, mentioned that in my original post.
I'm going to uninstall all the drivers and reconfigure everything, maybe that'll help.
Click to expand...
Click to collapse
What was the error the command prompt gave you?
zelendel said:
Did you change the setting in developer settings to allow bootloader unlocking?
Click to expand...
Click to collapse
zelendel said:
What was the error the command prompt gave you?
Click to expand...
Click to collapse
No error, but I just figured out what I've been doing wrong. Had such a herp derp moment. One of the guides I read explained that volume up was the button to press for continuing the bootloader unlock, upon checking the phone screen both volume down and up will cancel the operation. I should have double checked instead of trusting a guide so mindlessly.
I wasn't receiving any error codes and it was rebooting as if it was completing the operation so I assumed everything was working as it should and something else was the problem. Lol that's what I get for not touching the android terminal for two years.
Thanks for the replies!
Hello XDA, I hope that you could help me troubleshoot my Note 8 (N950F).
So it's been 7 days and oem unlock toggle has finally appeared.. The only issue is it is greyed out and unselectable.
When I got this device I wasn't able to see developer options by pressing build number (though I got the notification that it was enabled), I was only able to access the setting by downloading an app short cut for it via the play store and on initial launch it said developer options are disabled. But then second launch it worked. Idk if this is significant but maybe the country this is meant for disabled it? Regardless of the sim card being in/out the phone, it is still greyed out. Also, I was able to factory reset the phone through the settings after downloading an OTA (I did this in hopes of developer options being enabled about a week ago.)
I tried to boot into download mode but it seems I can't boot into it (following the steps only lead to a normal reboot, and when I select that option from the stock recovery or through adb, it only boots the phone up normally. I purchased the phone off of swappa, in brand new/like new condition. Any ideas? Thank you for your help.
Edit: added screenshots.
SM-N950F / DS here running Taiwan software BRI and I have the option maybe if you flash this firmware you'll get it.
Eddygraphic said:
SM-N950F / DS here running Taiwan software BRI and I have the option maybe if you flash this firmware you'll get it.
Click to expand...
Click to collapse
Thanks for the answer! However, I don't think I can flash firmware because I can not go into download mode, which is needed for odin to flash firmware
Negroid said:
Thanks for the answer! However, I don't think I can flash firmware because I can not go into download mode, which is needed for odin to flash firmware
Click to expand...
Click to collapse
That's weird I've never seen a Galaxy that can't enter download mode.
Eddygraphic said:
That's weird I've never seen a Galaxy that can't enter download mode.
Click to expand...
Click to collapse
Exactly. That's why I'm so concerned.
Have you logout your Samsung Account and Google account？sorry for my poor English.:crying:
Do you use any of the KNOX stuff? Did you do any factory reset?
Can you "clear data" on "settings" app? this would make the "developer option" menu hidden again. Then re-show it by tapping build number numerous time again. Hoping that OEM is now editable.
Hi, could you solve this problem? My Note 8 has the same problem and I have not found any solution :llorando:.
I would appreciate it if you can help me.
Using Odin files to update a Samsung AT&T model will almost always result in a factory reset being performed, and I've also seen the same thing happen when trying to update via OTA zip in Recovery. I'm providing this package for anyone still using the S5, to be able to update software without needing to do a factory reset. I have personally verified that these files will perform the update without wiping any data. These files will update you to the Build/Baseband ending in QD1, Android 6.0.
My zips are compressed extra small for space and bandwidth savings. The default Windows extractor can't handle it, so you'll need a 3rd party tool like 7zip, WinRAR, etc.
Happy flashing!
https://www.androidfilehost.com/?fid=1899786940962576350
Worked great..Thanks! But....
You are theman for this! I have a 900A AT&T and have struggled for days to get it unlocked, upgraded and working without tripping the secure software alert. I started with a 4.X maintenance OS, then rooted, SafeStrapped then pushed this update via ODIN and it worked. Now, the only issue i am having is apps crashing continuously. Started with google play and play services now spreading. I ASSUME this is due to apps not getting updated in the update to 6.X. Correct me if I am wrong. I have updated those via APKs along with others to new versions yet it still happens. Now its also Chrome, File manager etc. Is this maybe a code bug, or am I missing something here? Thanks again
3rdRockfromSun said:
You are theman for this! I have a 900A AT&T and have struggled for days to get it unlocked, upgraded and working without tripping the secure software alert. I started with a 4.X maintenance OS, then rooted, SafeStrapped then pushed this update via ODIN and it worked. Now, the only issue i am having is apps crashing continuously. Started with google play and play services now spreading. I ASSUME this is due to apps not getting updated in the update to 6.X. Correct me if I am wrong. I have updated those via APKs along with others to new versions yet it still happens. Now its also Chrome, File manager etc. Is this maybe a code bug, or am I missing something here? Thanks again
Click to expand...
Click to collapse
No idea. Can't really diagnose app crashes - too many possibilities.
Also: hopefully you're now aware that you're not rooted any longer and (probably) can't ever root it again
iBowToAndroid said:
No idea. Can't really diagnose app crashes - too many possibilities.
Also: hopefully you're now aware that you're not rooted any longer and (probably) can't ever root it again
Click to expand...
Click to collapse
Yeah I saw that, but thats ok. My biggest objective is to get it unlocked from AT&T so I can use it (this whole venture has just turned into a learning/fun toy to play with now) on my carrier. That is yet TBD. Any thoughts on that?
3rdRockfromSun said:
Yeah I saw that, but thats ok. My biggest objective is to get it unlocked from AT&T so I can use it (this whole venture has just turned into a learning/fun toy to play with now) on my carrier. That is yet TBD. Any thoughts on that?
Click to expand...
Click to collapse
https://www.att.com/deviceunlock/
Thanks in advance for any help, short version at top, details below.
-- Short version:
Please help me recover my data, and phone if possible.
I need the data, esp texts and notes, for both personal (some family members have passed on) and business.
I have a new Galaxy S21 and / or PC Smart Switch ready to receive data backup if we can evacuate it from the S5.
ODIN flash seems to pass but has 'Resizing Data' fail, and phone still won't boot past AT&T logo screen.
All web searches seem to say Factory Reset is my last option, but I don't want to lose the data.
Please share ANY advice on how I can recover the data.
-- More details:
Phone = SM-G900A Samsung Galaxy S5 AT&T
Use = pristine, never rooted, modded, or unfortunately backed up
Status = will not boot, passes screen 1 'Galaxy S5', screen 2 'Samsung script', then stops on screen 3 'AT&T globe logo'
More details = Used clean for ~7 years, then on day x, saw phone automatically complete a system update (green screen, sprockets, "your phone is updating"), which was surprising as it's years after it is no longer supported by AT&T. After that update, I continued to use the phone that day, but it then rebooted automatically and stuck on the AT&T globe logo.
Attempts to fix = soft reset, battery pull, can't get into SAFE MODE, can get into and out of recovery mode, found this firmware (THANKS @iBowToAndroid), used multiple ODIN (Odin3 v3.13.3_3B_PatcheD, Odin3 v3.14.1_3B_PatcheD) to flash it (my first Android flashing experience). On flashing process, ODIN on PC shows 'PASS' and log shows "<OSM> All threads completed. (succeed 1 / failed 0)", but phone shows 'Resizing Data' failed:
"
Supported API: 3
-- Installing package...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Successfully installed package.
-- Resizing Data...
Can't open dir '/data/user/0/com.sec.knox.bluetooth' (Permission denied)
E:failed the resizing-data
"
PFA screen shots
Martin2019 said:
Thanks in advance for any help, short version at top, details below.
Click to expand...
Click to collapse
Trying the "wipe cache partition" is the only thing I can think of
iBowToAndroid said:
Trying the "wipe cache partition" is the only thing I can think of
Click to expand...
Click to collapse
Short version:
THANKS for the quick reply, very much appreciate your help.
Am I really left with only a Factory Reset and then trying to use Data Recovery software to get ‘some’ data back?
I really don't want to give up on the data, so I'm still trying anything I can think of in research and repeated attempts.
More details:
I have tried the recovery mode 'Wipe cache partition' option before and after using ODIN.
I've tried doing it 'twice' per recommendation of some of the web advice I've read in trying to research this.
I've noticed that sometimes the colored highlight of the 'Reboot to bootloader' option then turns background green instead of usual blue, but I don't know why, or if that matters.
Still, the ODIN flash effort always returns the permission error, and the boot always sticks on the AT&T logo.
The string seems to indicate a 'user data' permission error?
Is there any way to debug the logic of the firmware or slog through the 'Recovery Logs' to determine and resolve the cause of the permission error?
When the problem began, I had an SD card and SIM card loaded.
I've since removed both in trying to address this, also per 'web advice'.
Any chance putting them back in helps somehow?
Any other options available via apply update from SD card or ADB?
Any way to setup the Android OS as a secondary drive to another machine to pull data out that way?
I've done similar things with Windows OS in PC environment, but I'm not seeing anyone trying that with Android.
If I am really stuck with factory reset, are there any data recovery programs I could try afterward that work with the G900A?
So far I've looked at Dr Fone, Tenorshare, EaseUS, FonePaw, and D-Back, and none seem to work with the AT&T model variant.
Maybe that's just because they don't have access to AT&T firmware available to install, but if I clear the stuck boot via FR, they then might be able to get some of my data back via drive scan - whatever data is not truly overwritten by the FR?
Martin2019 said:
Short version:
THANKS for the quick reply, very much appreciate your help.
Am I really left with only a Factory Reset and then trying to use Data Recovery software to get ‘some’ data back?
I really don't want to give up on the data, so I'm still trying anything I can think of in research and repeated attempts.
More details:
I have tried the recovery mode 'Wipe cache partition' option before and after using ODIN.
I've tried doing it 'twice' per recommendation of some of the web advice I've read in trying to research this.
I've noticed that sometimes the colored highlight of the 'Reboot to bootloader' option then turns background green instead of usual blue, but I don't know why, or if that matters.
Still, the ODIN flash effort always returns the permission error, and the boot always sticks on the AT&T logo.
Click to expand...
Click to collapse
I own and run a business that performs SIM unlocking and other software-related services for mobile devices, so we see situations like yours quite a bit. And I don't know of anything else that you can do. From reports, we've heard that none of those "recovery services" actually work to recover any data, after a reset
iBowToAndroid said:
I own and run a business that performs SIM unlocking and other software-related services for mobile devices, so we see situations like yours quite a bit. And I don't know of anything else that you can do. From reports, we've heard that none of those "recovery services" actually work to recover any data, after a reset
Click to expand...
Click to collapse
Disappointing to hear bad news, but appreciate your effort and insight in providing it, thanks.
I've learned alot in researching it.
I just wish I'd known it before the problem, which I'm sure you also hear quite a bit.
Please let me know if you think of anything else I can try.
Martin2019 said:
Disappointing to hear bad news, but appreciate your effort and insight in providing it, thanks.
I've learned alot in researching it.
I just wish I'd known it before the problem, which I'm sure you also hear quite a bit.
Please let me know if you think of anything else I can try.
Click to expand...
Click to collapse
You can never trust a mobile device 100%, especially not one that's 7 years old. That's why anything that's that important needs to be backed up at all times
iBowToAndroid said:
You can never trust a mobile device 100%, especially not one that's 7 years old. That's why anything that's that important needs to be backed up at all times
Click to expand...
Click to collapse
Totally agree, and totally on me for not having a backup.
I was just foolish enough to not know yet how easy it is to back up.
Give me 10 minutes of life again now in this phone, I use Smart Switch to backup, and I'm off to a new phone, or even FR on this one and reload.
Now where did I put my Delorean...
iBowToAndroid said:
You can never trust a mobile device 100%, especially not one that's 7 years old. That's why anything that's that important needs to be backed up at all times
Click to expand...
Click to collapse
Have you ever tried a 'combination key' approach to get data access?
As in...
Smart Switch on PC won't connect, but ODIN does show 'Added'.
I don't understand the granular details, but hoping you might...
Could we use both Smart Switch and ODIN in some combination sequence that would allow Smart Switch to pull the data off to a Smart Switch PC backup that I could then throw onto a new phone?
When it's in Downloading (firmware flashing) mode, a modem port is used. The modem port is also there when the device is booted up in Normal mode, but that's not useful for extracting any data off of it. I don't know what Smart Switch uses, but I would assume File Transfer (MTP) and/or ADB. And those aren't fully functional until the device fully boots up.
Do you have a screen lock on the device?
iBowToAndroid said:
When it's in Downloading (firmware flashing) mode, a modem port is used. The modem port is also there when the device is booted up in Normal mode, but that's not useful for extracting any data off of it. I don't know what Smart Switch uses, but I would assume File Transfer (MTP) and/or ADB. And those aren't fully functional until the device fully boots up.
Do you have a screen lock on the device?
Click to expand...
Click to collapse
No lock on device, just swipe to go from 'lock screen' to home screen, prior to this boot problem obv.
One of the data recovery sw that I tried (EaseUS I think) did reach a screen asking me to enable USB debugging to continue, but I don't think I can do that without booting up.
I 'think' I remember that screen saying something like 'MTP device' connected, when it asked me to do that.
Any way to sneak into MTP mode from that?
Martin2019 said:
No lock on device, just swipe to go from 'lock screen' to home screen, prior to this boot problem obv.
One of the data recovery sw that I tried (EaseUS I think) did reach a screen asking me to enable USB debugging to continue, but I don't think I can do that without booting up.
I 'think' I remember that screen saying something like 'MTP device' connected, when it asked me to do that.
Any way to sneak into MTP mode from that?
Click to expand...
Click to collapse
Any 3rd party software will require ADB to be enabled. Smart Switch is the only one that *might* work just over MTP, but I'm pretty sure MTP doesn't fully load until the device is booted. Even if it did, you would likely need to allow on the popup message. Does the phone show up as a device/drive when it's plugged in while sitting on the AT&T logo?
I think you're asking "does the phone show up as a device/drive" in something like a windows file explorer, and the answer is unfortunately no, or at least not that I've found yet - I've tried several times now, and I'm still trying any combinations I can.
For now...
I can get EaseUS to show 'MTP USB device' per the pic attached in my last, but can't really get it to connect past that point, as it asks for USB Debugging, which it appears I can't do due to stuck in boot loop.
Smart Switch seems to try to connect for awhile, then says it failed to connect, so I think I'm then left with 'Samsung Smart Switch Emergency Software Recovery' (PFA).
Do you have experience using it?
Do you know if it could work to reload the firmware / OS without wiping the data?
AT&T Advanced Technical Support guy says it gives you an option to choose whether or not using it resets the phone (wipes your data), so he thinks (hopes) that would work, but he didn't sound certain at all.
I understand your point on the pop up message user prompt for File Transfer Mode. I used that mode many times in the past, so I'm hoping it might default on the phone so we wouldn't need to answer the pop up prompt to reach that status , but I'm obv not sure about that.
Per the speculation in my last, do you know of any combination approach we might use to get the desired result, like maybe... use ADB somehow to change 1 parm value to reach MTP mode, then use that progress step to enable Smart Switch to connect so we could offload the data?
Thanks again for your help
1. MTP is the same as File Transfer. So when the phone is turning on, it starts loading that connection. You might see "MTP USB Device" or something similar in your Windows Device Manager
2. But if the phone never shows up as a device/drive (would show up under "Portable Devices" in Windows Dev Man), then it's not loading fully - and it normally doesn't do that until it boots past the carrier splash screen.
3. Even if it did boot fully and showed up as a device/drive, the MTP pop-up prompt shows up every single time you connect the device. There's no way around that. So the device would show as empty, with no files or folders, until you tapped "Allow" on the popup.
4. No, there's nothing else you can do to turn on any other connection modes
iBowToAndroid said:
1. MTP is the same as File Transfer. So when the phone is turning on, it starts loading that connection. You might see "MTP USB Device" or something similar in your Windows Device Manager
Click to expand...
Click to collapse
Device Manager does show an entry for the phone connected via USB cable:
Under 'Disk Drives' as
SAMSUNG MZMTE256HMHP-000MV
Under 'Universal Serial Bus Controllers' as
SAMSUNG Mobile USB Composite Device
Please tell me that helps us somehow?
Dear Friend,
I am having issue with S21 Ultra which i purchase just 2 months ago.
I decide to make my device root able , then i have notice that there is no OEM Lock option (Missing) in developer mode.
After searching XDA forum and Google all the setups mention there i have tried to visible OEM Unlocker option but OEM lock option never visible. Even flash stock rom again and again and wait for 168H but still its not visible.
When i go in download mode and try to flash TWRP or any custom rom it show below mention msg.
"Cause
No sign info: (Recovery)
Custom Binary (Recovery) due to remaining installment balance"
Can any one guide me what is the issue, i had purchase this product with Full payment then why it is behaving so strange.
google is best friend please add him to your friend list
reboot to download mode(connected phone to pc, reboot and hold vol+ and vol-) and read first screen options:
EDIT: sorry if you cant see these option list, there could be something different in your case.
Very srtange situation. I have exact same model.
vlubosh said:
google is best friend please add him to your friend list
reboot to download mode(connected phone to pc, reboot and hold vol+ and vol-) and read first screen options:
View attachment 5580147
EDIT: sorry if you cant see these option list, there could be something different in your case.
Click to expand...
Click to collapse
Thanks brother for your prompt response , i tried this but issue remain same
Samaly01 said:
Thanks brother for your prompt response , i tried this but issue remain same
Click to expand...
Click to collapse
Can you boot the phone? Try fastboot oem device-info to check what state od BL is.
vlubosh said:
Can you boot the phone? Try fastboot oem device-info to check what state od BL is.
Click to expand...
Click to collapse
Phone is booting ...no issue in that ....Fastboot not working in s21 Ultra g998b....
Samaly01 said:
Phone is booting ...no issue in that ....Fastboot not working in s21 Ultra g998b....
Click to expand...
Click to collapse
Allow usb debugging in dev.settings
vlubosh said:
Allow usb debugging in dev.settings
Click to expand...
Click to collapse
USB debuggin already allowed ....ADB command work but not fastboot
Samaly01 said:
USB debuggin already allowed ....ADB command work but not fastboot
Click to expand...
Click to collapse
I think you need to have a SIM card in there and to have internet access to see the OEM unlock toggle. Do both of these things apply to you?
Macusercom said:
I think you need to have a SIM card in there and to have internet access to see the OEM unlock toggle. Do both of these things apply to you?
Click to expand...
Click to collapse
SIM Card is installed both WIFI and Data is working but issue remain same.
Samaly01 said:
SIM Card is installed both WIFI and Data is working but issue remain same.
Click to expand...
Click to collapse
Try disabling the automatic date and time and set the date to a day at least one week from now
I have observe a very strange thing, when ever I reboot the device and visit develope option Oem Locker appear then again revisit to developer option it disappear again. Only rebooting device option bring oem option just for few minutes.
so then, when you see unlock option reboot right to DL mode and look if you see device unlock
vlubosh said:
so then, when you see unlock option reboot right to DL mode and look if you see device unlock
Click to expand...
Click to collapse
Still same issue
"Cause
No sign info: (Recovery)
Custom Binary (Recovery) due to remaining installment balance"
Someone suggested to use Samsung combination file, after searching on google there are only 3 Combination files available U1, U2, U3.
Latest file available is COMBINATION_FAC_FAR0_G998BXXU3AUD3
( I think this not usable on Android 12 version (U4)
Please suggest what option i have left to resolve above mention issue.
Could you try to flash latest Stock rom(Via odin) and try again?
Latest Firmware (SM-G998B_BTU_G998BXXU4CVC4) Flash via Odin...Result same
Found this, maybe your case
Custom binary blocked due to remaining installment balance galaxy
Hi, I recieved my S21 Ultra yesterday and sucessfully rooted it using the guide/youtube tutorial. Today, I restarted the device and upon restarting it would go into a bootloop with a small message on top saying: 'Custom binary blocked due to...
forum.xda-developers.com
vlubosh said:
Found this, maybe your case
Custom binary blocked due to remaining installment balance galaxy
Hi, I recieved my S21 Ultra yesterday and sucessfully rooted it using the guide/youtube tutorial. Today, I restarted the device and upon restarting it would go into a bootloop with a small message on top saying: 'Custom binary blocked due to...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks Brother, but issue is same mine.... no solution
checke my stats in DL mode:
KG state checking
FRP lock off
OEM lock OFF(u)
Warranty void 1
HDM status none
I think you problem is in KG state.
Maybe try to change date as in this tutorial: