Bootloop with SM-T817T; Frp Lock? - Galaxy Tab S2 Q&A, Help & Troubleshooting

Hello! I've got two tablets that are driving me up the wall, as I'm quite stubborn. I wanna start off by saying these tablets were brought to me by another individual, so I have no real background knowledge aside from how the tablets are behaving.
Both tablets are model SM-T817T.
One is just FRP locked and I cannot find a combination file to it, nor can I find any workarounds for the lock. Is it possible to port an existing combination file to a similar model? Because I have found one for the T817J model.
The other tablet is more complicated. It's stuck in a bootloop (flashes the Samsung Galaxy Tab S2 logo when plugged up to power or a PC). I cannot bring up the recovery menu, but I can bring up the download mode. I've tried to flash it with the latest firmware, but despite the successful flash through Odin, I get the same bootloop on restart. I have also tried draining the battery as well as charging it to 100%. I'm thinking the partitions are corrupted, but I'm not certain about what I should do to resolve the issue. I'm reading that I need a PIT file to repartition in Odin, but I can't find one. It might also be worth noting that Download mode displays "FRP Lock: On."
I thought, perhaps I could unlock the former and use it to create a backup image for the latter...?
Thanks for your time. :victory: I hope you understand I'm a little new to this Android business, but I'm an aspiring programmer and would love to learn more about mobile software.
[Edit] So, I've finally found my own workaround and removed the FRP lock from the working tablet. I flashed Marshmallow, then used the hotspot trick to put a pattern lock on the screen. On the unlock screen, I pressed the user icon in the top right corner and added a new account, then used the QuickShortcutMaker trick to do the rest. I've also rooted the tablet.
Now, I extracted the PIT file from the working tablet to pair with the same stock ROM to revive the bootlooping tablet via repartition flash. When I attempted to flash the bootlooping tablet, the PIT check failed. I suppose I'm missing something here... Any ideas? Thanks again!!

Related

HARD BRICKED Note 5

completely lost and its been a week of em trying to get this phone to accept sp,ething form odin and still noluck ive been glued to this computer and learned alot but nothing that has been able to fix my issue, any help would be appreciated please and thankyou
jpres1991 said:
completely lost and its been a week of em trying to get this phone to accept sp,ething form odin and still noluck ive been glued to this computer and learned alot but nothing that has been able to fix my issue, any help would be appreciated please and thankyou
Click to expand...
Click to collapse
Can you please elaborate. .what exactly the issue...what you did?
manishvy said:
Can you please elaborate. .what exactly the issue...what you did?
Click to expand...
Click to collapse
i have had my device rooted since the week i got it in october successfully, no issues. when i got the phone it was on the oi6 firmware, rooted it and put MOAR rom on it, no issues. then on the 23rd the day before i was going to go out of town i changed my primary google account password on my device, and for some reason i couldnt tell you why other than it didnt seem that it would be of any significance that OEM UNLOCK option was enabled so i turned it off not thinking anything of it, and right after i reboot the phone i found myself in a bootloop. only going to samsung galaxy note 5 powered by android with little red writing at top that says custom binary blocked by FRP lock. so i did some research and it became obvious what my issue was that the oem unlock should never had been touched. from what i figure, but that didnt validate why i was never given the chance to actually verify my account being that the device hasnt booted back into the os or any screen other than the splash screen i mentioned and download mode. thats the only two things i can access my download screen reads this
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME: SM-N920P
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
FRP LOCK: ON
Secure Download: Enabled
KNOX WARRANTY VOID: 1 (0x0500)
AP SWREV: B:2 K:0 S:0
i have tried flashing stock oi6, ive tried PIT file for oi6 ive gotten errors starting from couldnt open com port ehich seems to vary from the different versions of odin more or less, ive gotten complete write fail error, ive gotten COULDNT GET PIT FOR MAPPING as well as THERE IS NO PIT, and so i tried flashing one andit failed or just wouldnt go through, i mean ive just about ran the well dry as far as what ive read to do. Odin recognozes the device, i just cant get it to flash anything. as for all i know the device is wiped. my assumption.
http://forum.xda-developers.com/showthread.php?t=3191927
FRP LOCK ON Can't ODIN firmware... Lord help me.
---------- Post added at 08:31 PM ---------- Previous post was at 08:31 PM ----------
Seems this guy got his working
Try use Samsung KIES (or Samsung Smart Switch) on Windows PC to flash/restore your firmware. I've never had to this way though.
And BTW. This is not a "hard brick", so your thread title is misleading. It's "soft"...
jpres1991 said:
i have had my device rooted since the week i got it in october successfully, no issues. when i got the phone it was on the oi6 firmware, rooted it and put MOAR rom on it, no issues. then on the 23rd the day before i was going to go out of town i changed my primary google account password on my device, and for some reason i couldnt tell you why other than it didnt seem that it would be of any significance that OEM UNLOCK option was enabled so i turned it off not thinking anything of it, and right after i reboot the phone i found myself in a bootloop. only going to samsung galaxy note 5 powered by android with little red writing at top that says custom binary blocked by FRP lock. so i did some research and it became obvious what my issue was that the oem unlock should never had been touched. from what i figure, but that didnt validate why i was never given the chance to actually verify my account being that the device hasnt booted back into the os or any screen other than the splash screen i mentioned and download mode. thats the only two things i can access my download screen reads this
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME: SM-N920P
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
FRP LOCK: ON
Secure Download: Enabled
KNOX WARRANTY VOID: 1 (0x0500)
AP SWREV: B:2 K:0 S:0
i have tried flashing stock oi6, ive tried PIT file for oi6 ive gotten errors starting from couldnt open com port ehich seems to vary from the different versions of odin more or less, ive gotten complete write fail error, ive gotten COULDNT GET PIT FOR MAPPING as well as THERE IS NO PIT, and so i tried flashing one andit failed or just wouldnt go through, i mean ive just about ran the well dry as far as what ive read to do. Odin recognozes the device, i just cant get it to flash anything. as for all i know the device is wiped. my assumption.
Click to expand...
Click to collapse
just flash latest stock firmware through odin and your phone will be completely wiped and back to normal.
54NJ41 said:
just flash latest stock firmware through odin and your phone will be completely wiped and back to normal.
Click to expand...
Click to collapse
You can't if OEM UNLOCK is not enabled. ...
UpInTheAir said:
You can't if OEM UNLOCK is not enabled. ...
Click to expand...
Click to collapse
how do you reckon i flash it using kies or smart switch ? i dont have my serial number and the device isnt recognized in kies or smart switch
jpres1991 said:
how do you reckon i flash it using kies or smart switch ? i dont have my serial number and the device isnt recognized in kies or smart switch
Click to expand...
Click to collapse
It's on the box your bought it with. ...
UpInTheAir said:
You can't if OEM UNLOCK is not enabled. ...
Click to expand...
Click to collapse
for me it worked and use latest Odin
UpInTheAir said:
You can't if OEM UNLOCK is not enabled. ...
Click to expand...
Click to collapse
UpInTheAir said:
It's on the box your bought it with. ...
Click to expand...
Click to collapse
im 100 % sure ive tried all the numbers on the box
jpres1991 said:
im 100 % sure ive tried all the numbers on the box
Click to expand...
Click to collapse
I'm sorry, this is where my help ends.
Awfully suspicious if you can't find your serial number.
They all come on the sticker that seals the two halves of the box. This is standard from Samsung.
And you're in the wrong forum. .
UpInTheAir said:
I'm sorry, this is where my help ends.
Awfully suspicious if you can't find your serial number.
They all come on the sticker that seals the two halves of the box. This is standard from Samsung.
And you're in the wrong forum. .
Click to expand...
Click to collapse
WELL THANKYOU for your detective like skills considering i know my imei and meid by heart would you like photographs of my box
fact of the matter is is smart switch DOES NOT recognize the numbers give it a try detective
model number is SM-N920P
MEID_DEC: 256691545905342464
MEID_HEX: 99000583518500
ESN_HEX: 80ED70AD
ESN_DEC: 12815560877
SPC: 970920
jpres1991 said:
i have had my device rooted since the week i got it in october successfully, no issues. when i got the phone it was on the oi6 firmware, rooted it and put MOAR rom on it, no issues. then on the 23rd the day before i was going to go out of town i changed my primary google account password on my device, and for some reason i couldnt tell you why other than it didnt seem that it would be of any significance that OEM UNLOCK option was enabled so i turned it off not thinking anything of it, and right after i reboot the phone i found myself in a bootloop. only going to samsung galaxy note 5 powered by android with little red writing at top that says custom binary blocked by FRP lock. so i did some research and it became obvious what my issue was that the oem unlock should never had been touched. from what i figure, but that didnt validate why i was never given the chance to actually verify my account being that the device hasnt booted back into the os or any screen other than the splash screen i mentioned and download mode. thats the only two things i can access my download screen reads this
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME: SM-N920P
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
FRP LOCK: ON
Secure Download: Enabled
KNOX WARRANTY VOID: 1 (0x0500)
AP SWREV: B:2 K:0 S:0
i have tried flashing stock oi6, ive tried PIT file for oi6 ive gotten errors starting from couldnt open com port ehich seems to vary from the different versions of odin more or less, ive gotten complete write fail error, ive gotten COULDNT GET PIT FOR MAPPING as well as THERE IS NO PIT, and so i tried flashing one andit failed or just wouldnt go through, i mean ive just about ran the well dry as far as what ive read to do. Odin recognozes the device, i just cant get it to flash anything. as for all i know the device is wiped. my assumption.
Click to expand...
Click to collapse
mate, its really nothing to worry about, it isnt hard bricked,
i had the exam same issue, that oem lock can be a real pain in the arse,
all you need to do is download the firmware, and i mean not just the same android version, but the same, as in oc1 ok1, what ever version you were rocking,
in my case it was the latest firmware available on sammobile,
and flash it via odin,
after that you must wipe cache, data, and factory reset to be a able to use your phone,
once booted,
you can login with you google account, enable oem unlock from dev mode, and install custom recovery and do what you do from there.
cheers
UpInTheAir said:
I'm sorry, this is where my help ends.
Awfully suspicious if you can't find your serial number.
They all come on the sticker that seals the two halves of the box. This is standard from Samsung.
And you're in the wrong forum. .
Click to expand...
Click to collapse
urmother93 said:
mate, its really nothing to worry about, it isnt hard bricked,
i had the exam same issue, that oem lock can be a real pain in the arse,
all you need to do is download the firmware, and i mean not just the same android version, but the same, as in oc1 ok1, what ever version you were rocking,
in my case it was the latest firmware available on sammobile,
and flash it via odin,
after that you must wipe cache, data, and factory reset to be a able to use your phone,
once booted,
you can login with you google account, enable oem unlock from dev mode, and install custom recovery and do what you do from there.
cheers
Click to expand...
Click to collapse
SO dont do the ok3 if thats not what i was on prior to this happening?
my phone isnt recgonized in odin now for some reason. it has been up until now
I can solve your problem with Fap Lock On
hoangps said:
I can solve your problem with Fap Lock On
Click to expand...
Click to collapse
ALL EARS
So long as you are using genuine Samsung firmware or smart switch you do not need OEM unlocked.
If Odin is not recognizing your phone something has gone wrong with either your drivers or your phone is in a bad state.
Power down your phone, if you have to because it is restarting, catch it so you get back into download mode.
Then follow these steps exactly as they are laid out.
Open Smart Switch, click MORE, click Emergency software recovery and initialization, click device initialization, type in your model number using caps and dashes such as SM-N9200 or whatever your device is, then input your serial number again using caps for all the letters in your SN, finally connect your phone to your PC and continue with the prompts from Smart Switch.
The problem is since you have a carrier version, smart switch may not work. There was a guy who said it would not work for an AT&T phone.
Good luck.
Edit: I checked in smart switch using the sprint model number and it took it so you should be good to go.
CodeNameRedNeck said:
So long as you are using genuine Samsung firmware or smart switch you do not need OEM unlocked.
If Odin is not recognizing your phone something has gone wrong with either your drivers or your phone is in a bad state.
Power down your phone, if you have to because it is restarting, catch it so you get back into download mode.
Then follow these steps exactly as they are laid out.
Open Smart Switch, click MORE, click Emergency software recovery and initialization, click device initialization, type in your model number using caps and dashes such as SM-N9200 or whatever your device is, then input your serial number again using caps for all the letters in your SN, finally connect your phone to your PC and continue with the prompts from Smart Switch.
The problem is since you have a carrier version, smart switch may not work. There was a guy who said it would not work for an AT&T phone.
Good luck.
Edit: I checked in smart switch using the sprint model number and it took it so you should be good to go.
Click to expand...
Click to collapse
yes i can get it in download mode ive installed the drivers from samsung website for the note 5, and installed them. is there other drivers i should install fgor it to recognize it? i also am successful in getting smart switch to recognize the SM-N920P for my phone model but i am unclear on how to obtain the serial number that smart switch wants. ive tried the dec hex the imei esn hex and the spc none of which it accepts. i have the box and it doesnt say serial number anywhere so im lost when i get to that point
jpres1991 said:
i am unclear on how to obtain the serial number that smart switch wants. ive tried the dec hex the imei esn hex and the spc none of which it accepts. i have the box and it doesnt say serial number anywhere so im lost when i get to that point
Click to expand...
Click to collapse
That is a problem then because you need that number. It should be labeled SN and should be a mix of letters and numbers. Perhaps sprint keeps those records on file.
Good luck.

Help remove Retail Mode Samsung Tab S2 SM-T810

Hi to everyone. I have a Samsung Tab S2 SM-T810 with Android 5.1.1 / Kernel 3.10.9 that has retail mode on, it was a demo in a store. Is there anyway to remove this from the device? I already try doing a factory reset with stock firmware and odin and it stills the same. I think it has some kind of software installed on the ROM memory that prevents it to fully restore and wipe the retail mode app. Thanks in advance.
Please do a search this has been covered plenty of times already. There is no need to repeat over.
ashyx said:
Please do a search this has been covered plenty of times already. There is no need to repeat over.
Click to expand...
Click to collapse
I did it. that's why I specified re installing with odin didnt help. I checked all the forum. even this http://forum.xda-developers.com/galaxy-tab-s/help/samsung-galaxy-tab-s-sale-version-t2890171
and it stills the same.
huntejes said:
I did it. that's why I specified re installing with odin didnt help. I checked all the forum. even this http://forum.xda-developers.com/galaxy-tab-s/help/samsung-galaxy-tab-s-sale-version-t2890171
and it stills the same.
Click to expand...
Click to collapse
It's simple, make sure OEM unlock is enabled in developer settings, Install twrp, factory reset with twrp, boot to download then flash stock Firmware.
Done.
ashyx said:
It's simple, make sure OEM unlock is enabled in developer settings, Install twrp, factory reset with twrp, boot to download then flash stock Firmware.
Done.
Click to expand...
Click to collapse
I wouldn't be asking for help if it were that easy. I tried doing that too. All the option in the developer settings tab are gray. I can't change them. The retail app is blocking it.
Any other idea ?
huntejes said:
I wouldn't be asking for help if it were that easy. I tried doing that too. All the option in the developer settings tab are gray. I can't change them. The retail app is blocking it.
Any other idea ?
Click to expand...
Click to collapse
Just go ahead and install twrp and continue with the previous instructions. If you get the FRP block, just flash the stock Firmware.
Also if you carry on with the attitude you're on your own.
ashyx said:
Just go ahead and install twrp and continue with the previous instructions. If you get the FRP block, just flash the stock Firmware.
Also if you carry on with the attitude you're on your own.
Click to expand...
Click to collapse
Excuse me, I didn't mean to offend. I'll try to install twrp right now.
As I expected while I was trying to install twrp it always return an error on Odin so I gave up, then after a couple of hours the table ran out of battery and since it was the first time it went off without the retail app monitoring. I decide to boot it into download mode. and that's it.
After that the twrp finally got installed and I erased everything on the tab. after that that it got stuck on the samsung logo. And I could install the stock firmware with no problem.
All thanks to you.
Ok so ive got the Sm-810 and i was experiencing the same issue of it not letting odin flash to stock OR install twrp etc. etc. and i was going to give up and i **** you not i was trying to get into the recovery to see if i could jostle some solution loose and it fixed itself !! It was booted into download mode and i unplugged the cable and pressed and held power+vol down and as soon as the screen went black i did the same thing again and then i mustve messed up cuz it booted into the os but i repeated the process from there and no kidding after 2 or 3 cycles of power+vol down i got a blue screen with an android on it and it flashed and showed a dead android with the caution! sign and the next screen showed the regular android with the word "erasing" underneath and vio'la no more retail mode. After this Odin worked and let me autoroot and so on an so forth. sorry for my long post i just though i should share
I think the major issue is that OEM is disabled and there is no way to turn it on. So most of the solutions are a no go... So any other suggestions on make this work?
huntejes said:
Excuse me, I didn't mean to offend. I'll try to install twrp right now.
As I expected while I was trying to install twrp it always return an error on Odin so I gave up, then after a couple of hours the table ran out of battery and since it was the first time it went off without the retail app monitoring. I decide to boot it into download mode. and that's it.
After that the twrp finally got installed and I erased everything on the tab. after that that it got stuck on the samsung logo. And I could install the stock firmware with no problem.
All thanks to you.
Click to expand...
Click to collapse
Hi huntejes,
I've a SM-T650NU unit and have the same issue you faced on the Odin step (of course I'm using the specific TWRP file for my unit) just want to know what error showed up. In my case it returned: FAIL! (Auth).
Will let the battery fully drain and after that repeat the TWRP flash. Do you remember (step by step) what you did after the battery drained? I mean charged to 30% then put on download mode? Any feedback will be appreciated.
BR\
My husband and I also ran into the problem of having our Samsung Tablet E nook 2017 model stuck on Retail Mode.. we tried EVERYTHING we could possibly think of after the 5444 password didn't work. We rooted, we downloaded "easy uninstalled" apps, did the hard reset with the 3 button deal.. nothing! Then we finally came across a few passwords we were willing to give a try.. so when you go to the retail mode bar and it prompts you for a password to uninstall try blue. The word BLUE but in lowercase.. and it worked! We were then given tons of options and finally got that crap off our paid for device. I'm 100% sure that any device purchased from Best Buy and stuck in retail mode will use the password blue. A few other passwords we came across that might be worth a shot if blue doesn't work are: galaxy and unlimited. (Each by themselves as one password) Well good luck, we know how frustrating this has been!!
Skapino said:
Hi huntejes,
I've a SM-T650NU unit and have the same issue you faced on the Odin step (of course I'm using the specific TWRP file for my unit) just want to know what error showed up. In my case it returned: FAIL! (Auth).
Will let the battery fully drain and after that repeat the TWRP flash. Do you remember (step by step) what you did after the battery drained? I mean charged to 30% then put on download mode? Any feedback will be appreciated.
BR\
Click to expand...
Click to collapse
Dude, I have a SM-t560nu and I feel your pain. For months I was trying to find a solution and had to deal with obnoxious fools who couldn't get it thru there heads that this was NOT the usual Samsung Retail Mode but a special piece of software that puts the tablet into a rolling cycle of 2-10 minutes, shuts off all developer options, locks frp and basically makes anything you do null and void. I tried every password Imaginable including "BLUE," "5444" and the oft repeated "M729Q16K8546" all to no avail.
Here's the deal: this IS unique software and you'll find it at retailsamsung.com. (I can't post the actual url because of the new user rules, which is kind of funny because I've been a member for about 10 years but I don't think I've ever posted anything.)
Go there, search your device and download 2 items: One will be your installation package (for instance "Samsung_Retailmode_Global_Common _141006.apk") and the other will be called "RetailMedia.main." Download both to na sd card, put the sd card in your device, move the programs from the sd card to the download area ON the device. Now start your device, got to the download area and tap on the first program, the apk. Enter 5444 as your password, follow the instructions. the second password will be "M729Q16K8546." This will remove the Retailmode software and most likely trigger a Samsung lock. Go to Sammobile, download the original firmware and congrats, your new tablet is finally working right.
I was wary of downloading software from such a plain site, especially one I've never heard of but I figured after 6 months of no luck and my new tablet just sitting in a drawer, unusable, what did I have to lose? Well, it works, i'ts awesome and it's like new.
Hope this helps.
Mfb5159, You Are Awesome! A friend entrusted me to remove the Retail Mode from her Samsung Galaxy Tab A 9.7. I tried Everything. The passwords that can be found everywhere online, circumventing the FVP (of course that was useless), downloaded & installed the firmware with Odin in download mode... nothing. Then I ran across this forum. Tried two versions of retail mode from RetailSamsung.com and the second one worked. I had to open the retail app I installed, enter the generic passwords (5444 & the M729Q16K8546), then it gave me the option to factory reset the device. I chose yes & it worked! No sign of Retail Mode on the tablet. It's like a brand new tablet!! The .apk file that worked for me was SamsungRetailMode_GlobalCommon_141006
Thank you So Much for your help.
I hope I'm not posting on a dead thread. I saw a good deal on a T813 in retail mode (will provide link if needed, it's on a very popular and legal south american online store). The thing is, as explained by the vendor, someone attempted to remove the retail app and now is stuck on a countdown in the lock screen. After some time it reboots itself. I've been reading a lot about the topic and the main problem seems to be the OEM unlock off. Now apparently I won't be able to access any feature of the device at all. I thought maybe I could reinstall the retail mode and get back the app or just boldly odin flash twrp and a stock rom risking myself to an FRP lock.
However I thought better ask advice first, so what do you think? Any help is greatly appreciated.
Well, I bought it and first day has been no success. I can access guest user, could log in to my ggl account and downloaded some apps. OEM, third party apps and developers are out of reach and cannot access main account. No sign of retail app.
Flashed new stock rom, FRP asks for a password, tryed 5444 Mz$%"#$%& blue galaxy unlimited with no luck. Attempts to flash twrp via odin fail due qst (?) error. I guess because is OEM locked. Flashed some older rom and still a countdown that doesn't let me in in main account.
So far, this is my progress with it. Any advice to flash twrp, remove frp lock and/or remove retail mode? Thanks in advance
_Iffer_ said:
Mfb5159, You Are Awesome! A friend entrusted me to remove the Retail Mode from her Samsung Galaxy Tab A 9.7. I tried Everything. The passwords that can be found everywhere online, circumventing the FVP (of course that was useless), downloaded & installed the firmware with Odin in download mode... nothing. Then I ran across this forum. Tried two versions of retail mode from RetailSamsung.com and the second one worked. I had to open the retail app I installed, enter the generic passwords (5444 & the M729Q16K8546), then it gave me the option to factory reset the device. I chose yes & it worked! No sign of Retail Mode on the tablet. It's like a brand new tablet!! The .apk file that worked for me was SamsungRetailMode_GlobalCommon_141006
Thank you So Much for your help.
Click to expand...
Click to collapse
Did the same, although I had to use the older ap_SamsungRetailMode_Global_Tab_A_L_v1.0.4_15031100_M15031100_P0.apk with my SM-T550 (Galaxy Tab A (2016) 9.7") - I also had to stop the existing RetailMode Service from running by opening applications, swipe across to Running Applications, and tap on the Retail Mode executables to disable the "Sta" service. Annoyingly if you accidentally get the password wrong then it'll reset itself and delete the newer APK and you have to start the whole process over again
Could anyone at least point me in the right direction please? I can't access the main user of the tablet because there's a lock on the screen saying "Try again in 1440 minutes" which is a day. It self reboots every 5 minutes and each time the 1440 minutes thing resets. I booted in safe mode, now it doesn't reset and countdown is set for the next 4 hours.
Please, any light on the matter will be great. I have 4 days to return and I wouldn't like to do it cause it was extremely cheap unless, but I don't want to end with an expensive brick either.
Huntejes,
I had the same experience as you with my SM T810. The particular version of the Samsung Retail app (com.samsung.sta.retailagent.lite 6.9.20161101) installed on my unit didn't have a 'configuration settings' option; instead an option called 'Store Settings' prompted a password entry - but admin passwords 5444, blue, galaxy, unlimited all failed.
So then I went the Odin/flash stock firmware route. Unfortunately, despite two rounds of that, the Retail Mode application and restrictions remained. However, what did arise from this seemingly pointless process was the ability to enable installation of third party apps under Settings - all other admin access and functions (i.e. factory reset, program uninstallation, etc.) remained under the restricted control of Retail Mode. I went through that process about a year ago, assuming I had failed - the restrictions remained, and I was out of ideas/options.
Two days ago, I decided to revisit the problem, having to reeducate/remember what I had done previously along the way. Eventually, I came up with a novel workaround that hadn't occurred to me before - side-loading an apk file containing a different version of the Retail Mode software. Ironically, this worked. After installing and running the alternative Retail Mode app, using admin password 'blue' I was able to uninstall the original (i.e. problem) Retail Mode app, enable factory restore, and execute a complete wipe, which was successful.
I know this thread has been silent for a while, but it was one of only two threads that I thought took the larger conversation beyond the first basic step and I thought that contributing to it would be a small way to express my thanks.
Cheers.
---------- Post added at 04:56 PM ---------- Previous post was at 04:46 PM ----------
It now seems that others (SeriousEion) have used the approach I mentioned above to successfully bypass Retail Mode in several of the most troublesome cases - it's very interesting to me that this thread only reactivated last month after having gone dark by the time I came across it in 2016.
---------- Post added at 05:08 PM ---------- Previous post was at 04:56 PM ----------
It now seems that others, namely mfb5150's post from 20-07-2017, have used the approach I mentioned above to successfully bypass Retail Mode in several of the most troublesome cases - I can confirm that the approach he outlines also works for the Samsung Galaxy Tab S2 (SM T810) using the apk files available from samsungretail.com
So thank you, mfb5150, for your post - had I seen it earlier you might have saved me an hour or two of trial and error. It's interesting to me that this thread has finally reactivated after having gone dark by the time I came across it back in 2016. I'm not a developer, and have no programming/coding experience, so I hope that this thread continues to be a resource for any others like me out there.
Hi guys,
I have a galaxy tab and sm-t561, which presents the problem of retail mode that you can not remove in any way even with odin, I wanted to ask, how do I install a version of retail mode via apk? I downloaded the new version of retail mode but how do I install it?
whchapma said:
Huntejes,
I had the same experience as you with my SM T810. The particular version of the Samsung Retail app (com.samsung.sta.retailagent.lite 6.9.20161101) installed on my unit didn't have a 'configuration settings' option; instead an option called 'Store Settings' prompted a password entry - but admin passwords 5444, blue, galaxy, unlimited all failed.
So then I went the Odin/flash stock firmware route. Unfortunately, despite two rounds of that, the Retail Mode application and restrictions remained. However, what did arise from this seemingly pointless process was the ability to enable installation of third party apps under Settings - all other admin access and functions (i.e. factory reset, program uninstallation, etc.) remained under the restricted control of Retail Mode. I went through that process about a year ago, assuming I had failed - the restrictions remained, and I was out of ideas/options.
Two days ago, I decided to revisit the problem, having to reeducate/remember what I had done previously along the way. Eventually, I came up with a novel workaround that hadn't occurred to me before - side-loading an apk file containing a different version of the Retail Mode software. Ironically, this worked. After installing and running the alternative Retail Mode app, using admin password 'blue' I was able to uninstall the original (i.e. problem) Retail Mode app, enable factory restore, and execute a complete wipe, which was successful.
I know this thread has been silent for a while, but it was one of only two threads that I thought took the larger conversation beyond the first basic step and I thought that contributing to it would be a small way to express my thanks.
Cheers.
---------- Post added at 04:56 PM ---------- Previous post was at 04:46 PM ----------
It now seems that others (SeriousEion) have used the approach I mentioned above to successfully bypass Retail Mode in several of the most troublesome cases - it's very interesting to me that this thread only reactivated last month after having gone dark by the time I came across it in 2016.
---------- Post added at 05:08 PM ---------- Previous post was at 04:56 PM ----------
It now seems that others, namely mfb5150's post from 20-07-2017, have used the approach I mentioned above to successfully bypass Retail Mode in several of the most troublesome cases - I can confirm that the approach he outlines also works for the Samsung Galaxy Tab S2 (SM T810) using the apk files available from samsungretail.com
So thank you, mfb5150, for your post - had I seen it earlier you might have saved me an hour or two of trial and error. It's interesting to me that this thread has finally reactivated after having gone dark by the time I came across it back in 2016. I'm not a developer, and have no programming/coding experience, so I hope that this thread continues to be a resource for any others like me out there.
Click to expand...
Click to collapse
i just follow your instructions and awesome mine is unlock now and downloading the update to android 7.0 thanks bro

VIE-L09 seems to be totally screwed!

Hey,
So i used the SRK tool to try and root my VIE-L09C40 (P9 Plus)
Something seemed to happended during the rooting procedure and when i entered e-recovery it said it had to Download a new version, but couldnt connect to internet via wifi.
Any ways it seemed to work after a while but now i have no keyboard at all, so i cant literally start my phone.
it starts, boots the EMUI 5.0 logo and goes through the information a terms, i click the ok button and thats fine.
Next it tells me to sign in to my wifi, i select my wifi and when i go to type the password all i have is google voice as a keyboard, ive searched and searched but cannot find a way around it, also the frp has tripped on phone so i cannot log in to my google account without a keyboard.
How can i get around this?
do i have to flash parts of firmware?
any help would be great, i sent it away to hauwei and they say warranty void due to software!, can only assume something wrong was flashed?
Waiting for phone to be returned now, please help
I had the exact same issue last night as well. No keyboard and only an option to enter details with voice.
Ended up with an essentially bricked phone. Couldn't find any info on the problem online, so I have to improvise.
I'm starting from scratch after formatting etc. using stock oeminfo, recovery and rolling back to Marshmallow. (fingers crossed ADB will let me, because it was giving me errors before)
Will let you know if I'm successful and the steps I took.
=====================
tolerant said:
Hey,
So i used the SRK tool to try and root my VIE-L09C40 (P9 Plus)
Something seemed to happended during the rooting procedure and when i entered e-recovery it said it had to Download a new version, but couldnt connect to internet via wifi.
Any ways it seemed to work after a while but now i have no keyboard at all, so i cant literally start my phone.
it starts, boots the EMUI 5.0 logo and goes through the information a terms, i click the ok button and thats fine.
Next it tells me to sign in to my wifi, i select my wifi and when i go to type the password all i have is google voice as a keyboard, ive searched and searched but cannot find a way around it, also the frp has tripped on phone so i cannot log in to my google account without a keyboard.
How can i get around this?
do i have to flash parts of firmware?
any help would be great, i sent it away to hauwei and they say warranty void due to software!, can only assume something wrong was flashed?
Waiting for phone to be returned now, please help
Click to expand...
Click to collapse
dmccort said:
I had the exact same issue last night as well. No keyboard and only an option to enter details with voice.
Ended up with an essentially bricked phone. Couldn't find any info on the problem online, so I have to improvise.
I'm starting from scratch after formatting etc. using stock oeminfo, recovery and rolling back to Marshmallow. (fingers crossed ADB will let me, because it was giving me errors before)
Will let you know if I'm successful and the steps I took.
=====================
Click to expand...
Click to collapse
Good luck, i did read that it might be possible to install the base firmware back to it and then update again.
Im sure we are not the only people this has happened to and if you succesfully do this, maybe consider making a full step by step guide so to help others.
Fingers crossed
:good:
Will do my best.. So far it's been a major. I've managed to flash a working stock ROM and boot up. But there are a few things to smooth out. Such as, I have no IMEI number now and the build is C900, also the bootloader is modified.
To get it to boot I had to use DC- Phoenix to flash a factory firmware(Chinese) which I had to pay for. Then I flashed a stock vie-l09c432b181 ROM over the top.
To repair the IMEI I'll have to use HCU, which I'll have to pay for as well. But that's ok. If I can get my original IMEI back, I can use the original unlock code I got earlier this year, otherwise I'll have to get a new one based on a new IMEI.
I can repair the bootloader and region code using twrp etc. so that's not a problem.
I'm actually using the phone to write his reply, so I can at least use it.
Once I have it all 100% working I'll try to put together a full step by step.
Cheers.
Well, I have a working phone. But, it'snot stable. Having trouble with mobile connection, sms, mms, 4g etc not staying connected. So wont be doing any write-ups just yet.
Not until it's stable.
I'm wanting to return it to complete stock now. And that requires trying to find an oeminfo file for C706 (New Zealand).
Will add more as I get there. Sorry.
I had the same problems. All I did is updated the phone with the firmware you want via Twrp . Be warned that it will replace the recovery back to stock. Also clear the cache and etc.
I had a similar issue with SRK tool, bootlooping, won't flash new firmwares, lost all the stock apps and diagnostic tools.
I'm now stuck on a TEST-KEYS build with no NFC or Bluetooth.
My solution was to throw the piece of junk in a drawer, forget about it and I went and bought a Pixel XL instead - a phone that is properly supported and gets updates quickly.
After much messing and a headache I finally got to c432b370
And everything back to normal
tolerant said:
After much messing and a headache I finally got to c432b370
And everything back to normal
Click to expand...
Click to collapse
How did you succeed?
I am stuck on TEST-KEYS but I am not able to flash other roms on it. When I go to recovery, the update process stops after a while
Sent from my VIE-L09 using Tapatalk

G900A Galaxy S5 Android 6.0 Odin Update Files - Without Wiping!

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?

Galaxy Note 9 stuck at bootloop after update Magisk

I was happily use my Note 9 N960N(Korean set) after I rooted it about a year ago. Few days ago I saw a new ver of Magisk(old ver 17.2 flashed w/TWRP) at Magisk manager and wanted to update but hesitate. I backup a few important file like whatsapp, SMS & contact list before I carry on further. Today I decided to update the Magisk and my fear was right, after it reboot my Note 9 stuck at "Samsung" logo. I let it there initially and after a while it remains at same place. I tried to switch it off by press the power button but no response. It won't switch off after I tried, 10, 20 and 30 seconds. I found out there is a way to reboot it by holding "power + volume down". I successfully got it boot to recovery to TWRP.
I thought it maybe the Magisk was corruptted during update so I download the Magisk zip v19.3. Then I booted to TWRP and installed the Magisk zip. I reboot the Note 9 after Magisk installed. Again I was stuck at Samsung logo. I thought maybe the sequence was not correct; beside the Magisk there maybe need few more so I followed the root sequence(skip root); 1. Magisk 2. no-verity-opt-encrypt-6.0 3. RMM-State_Bypass_Mesa_v2
Same problem, I stuck at Samsung logo. As early problem, I couldn't switch it off by pressed the power switch. I have to reboot to TWRP and use its interface to power off the phone. I have new problem this time; once I pressed the power button to power on the phone, it will goes to TWRP straight away. Tried few times and it remain the same problem. The last action what i did is flashed a new TWRP v3.3.1-0-crownlte and it didn't help either.
My Note 9 has 2 problems;
1. go to TWRP recovery straight after press power button to power up the phone.
2. stuck at samsung logo after user TWRP to reboot.
There is one more thing I didn't pay attention previously, the "mount" in the TWRP what is supposed to mount? It "mount" the SD card when it last to flash zip files.
Appreciated anyone can helps, thanks.
Try to flash different kernel. Then flash magisk again. Although I doubt it could help, but your phone has bricked already, so worth to try.
If it's really brick, I'll consider to flash it "pie" since my one still "oreo". Any chance just reflash it with oreo again with odin but retain data?
user109 said:
If it's really brick, I'll consider to flash it "pie" since my one still "oreo". Any chance just reflash it with oreo again with odin but retain data?
Click to expand...
Click to collapse
Phone will factory reset after flash stock regardless odin or smartswitch. Of course you can still flash oreo. But flashing stock should be the last resort.
Rosli59564 said:
Try to flash different kernel. Then flash magisk again. Although I doubt it could help, but your phone has bricked already, so worth to try.
Click to expand...
Click to collapse
You did mention to flash a different kernel, what will it be the most suitable?
I found a suggested solution to try; flash(with oreo, same ver) with odin and check files except at CSC section choose "home_csc" instead normal "csc". Reflash was succeeded, in a way.. It did break something though.. My note 9 is able to boot normal but was stopped at lock screen(pattern lock) which I was set to lock my phone. Now it's lock screen loop even though I draw the pattern correctly. It just refuses to unlock. I use Samsung "findmymobile" try to unlock it and unsuccessful; the app cannot find the phone. It prompted "offline"! It's strange, I can see my carrier and wifi are working. I can call the preset emergency numbers to call. I used another phone to call and it can receive the call. It can receive whatsapp message. I tried google and it works. The google app is able to find my phone. I have no idea why my samsung account won't work. Now I'm clueless.. :crying:
user109 said:
I found a suggested solution to try; flash(with oreo, same ver) with odin and check files except at CSC section choose "home_csc" instead normal "csc". Reflash was succeeded, in a way.. It did break something though.. My note 9 is able to boot normal but was stopped at lock screen(pattern lock) which I was set to lock my phone. Now it's lock screen loop even though I draw the pattern correctly. It just refuses to unlock. I use Samsung "findmymobile" try to unlock it and unsuccessful; the app cannot find the phone. It prompted "offline"! It's strange, I can see my carrier and wifi are working. I can call the preset emergency numbers to call. I used another phone to call and it can receive the call. It can receive whatsapp message. I tried google and it works. The google app is able to find my phone. I have no idea why my samsung account won't work. Now I'm clueless.. :crying:
Click to expand...
Click to collapse
it's a Samsung stupid lock as your Note 9 has not fully booted you will not be able to find it via my Samsung.. There is a bug even if you draw the correct pattern the phone will not unlock it's a bug this has been covered when the Note first came out as the first or second update caused this issue! i did read somewhere there is a way around it, but this was a year or so ago you need to check Samsung official forums for the pattern bug fix check Samsung forums USA it has been covered in-depth over there!
N1NJATH3ORY said:
it's a Samsung stupid lock as your Note 9 has not fully booted you will not be able to find it via my Samsung.. There is a bug even if you draw the correct pattern the phone will not unlock it's a bug this has been covered when the Note first came out as the first or second update caused this issue! i did read somewhere there is a way around it, but this was a year or so ago you need to check Samsung official forums for the pattern bug fix check Samsung forums USA it has been covered in-depth over there!
Click to expand...
Click to collapse
Hi N1NJATH3ORY, I did google around the screenlock loop problems and most of them done with 1) simple reboot 2) boot to safe mode 3) use "samsung "findmymobile". A most common solution; "wipe". A few issues raised at Samsung forum but not helpful; "call Samsung support".. There was an interesting article which suggested the problem is from google itself. Here is the link; https://www.androidpolice.com/2019/12/12/google-pixel-pin-lock-screen-loop-help/
"If the encryption of the "Synthetic Password Key blob", which needs to be decrypted in order for the unlock process to be resolved, is not able to retrieve a stored decryption key if it was corrupted." from the article. I'm not sure if this is the cause but from logic point of view it's possible. I believe the bloody Samsung knew this problem since day one but because it's not a"common" issue Samsung just swipe under the carpet.
What I did on my note 9 last action was reflash the oreo, if in the process of flashing the "Synthetic Password Key blob" has been wiped out then it may explain this screenlock loop problem, which I hope not to happen. I'll be screwed if it did. :crying:
I'll wait its battery to drain out to see what happen even though I doubt if any change..
As expected, the drained out of battery did not help, my note 9 remains locked. The only way is to try out new method and with high risk which will wipe out my data. Fortunately the new method work! Not only it overwrite the lock screen loop and also disable the google device lock.(One of the method I tried during my lockscreen loop which is useless. It creates an extra problem on top of the problem) I got all my data intact and allow me to do all backup. :highfive:
summary: update Magisk is not a full proof. The risk is 50% it will brick the phone. My advise is to backup every dan internal data before finger press the Magisk "update" especially it remaps the image! Manager APK is okay to update. I learned from the hard way and almost lost the whole dan data in my Note. You have been warned!
Gdhhs

Categories

Resources