Hi guys,
I have a big issue with my Samsung Galaxy A21s. I set up a password for the lock screen a couple of days ago. Everything was working fine, but yesterday my phone randomly decided to lock itself for 1440 minutes (24 hours) after typing in my correct password once. I waited those 24 hours and tried again and it got locked for another day again. The password is 100% correct.
Or course I tried restarting the phone and booting it in safe mode, without success. I tried unlocking it on my computer via Google find my phone (I don't have a samsung account set up), but it appeared as offline, even though it is connected to wifi. I have to mention that it has airplane mode on which I can't turn off and NordVPN is installed. The phone has very few apps installed, such as Telegram, NordVPN and Instagram, no malicious third party applications...
I don't want to hardware reset the phone because it has very important things on it. Sending it to Samsung isn't possible as well, I don't have a bill for the product.
Please help
Do you have bootloader open ?
If so you can flash a file than break through the password
Gotiplex said:
Do you have bootloader open ?
If so you can flash a file than break through the password
Click to expand...
Click to collapse
what file should I flash? It's very important for me to keep the data.
hum I have it on my other computer so I have to go get it, but can you flash a file now ?
PS : I used this file when the password did not work on my Samsung J5, and it just delete the password
Gotiplex said:
hum I have it on my other computer so I have to go get it, but can you flash a file now ?
PS : I used this file when the password did not work on my Samsung J5, and it just delete the password
Click to expand...
Click to collapse
I wont flash a random file by a random user on the internet. Send me the original download link to the file or something...
Yes of course, i needed to find the file to remember its name...
It s called Lockscreen_FIXER, and it s a126 ko zip file.
I don t have the source, but check this on internet
[zip]Lock screen fixer
A flashable zip which can be used if lock screen code or pattern was forgotten:D It will remove the lockscreen
forum.xda-developers.com
Gotiplex said:
[zip]Lock screen fixer
A flashable zip which can be used if lock screen code or pattern was forgotten:D It will remove the lockscreen
forum.xda-developers.com
Click to expand...
Click to collapse
thanks, I would like to try this, although my phone is like 6 years newer than the post... how do I flash it without using my phone? Should I use bootloader or something, can you explain?
That IS why I asked you if you could flash a file.
Did you ever unlocked your bootloader ?
If so, you have to put twrp on your phone (there is many tutorial for each phone in the forum), and then flash the file with your sd card.
If your bootloader IS locked, I don t know how install TWRP recovery, but maybe there is a way on the net.
What is your phone model ?
Ah okay thank you... Model is Samsung Galaxy A21s
Gotiplex said:
That IS why I asked you if you could flash a file.
Did you ever unlocked your bootloader ?
If so, you have to put twrp on your phone (there is many tutorial for each phone in the forum), and then flash the file with your sd card.
If your bootloader IS locked, I don t know how install TWRP recovery, but maybe there is a way on the net.
What is your phone model ?
Click to expand...
Click to collapse
I dont have bootloader set up and if I understood correctly, setting up bootloader and twrp will erase all data...
Absolutly not, I don t know how to unlock bootloader other than via the parameters, but I doesn t erase any data, same for TWRP.
Find a way to unlock the bootloader, then just install TWRP with Odin, and then you just have to flash the file.
Related
I have my old Nvidia shield tablet and i have WiFi off and powered off.
I've been reading you can stop the kill switch from i guess changing the boot loader or operating system?
I new to this stuff.
Could someone just give me some directions on how to go threw this process please.
I don't know if it's to late cause i have the most recent update? but like i said it's turned off and WiFi is off and i heard that the kill switch is sent over the internet to your device and you don't have to confirm it.
So i hope my system is safe until i can do what ever you guys advise me to do.
Thank you...
treat your old tablet before connecting the new one to internet
Hello. You have to delete a folder (/system/apps/TegraOTA if you are on last firmware, with OTA 3.1) but to do this, you need root as folders in /system are not visible for the normal (unrooted) user. Or you flash a custom firmware, and flash nomoreOTA.zip that you'll find in the same forum : http://forum.xda-developers.com/shield-tablet/general/kill-kill-switch-shield-tablet-xx-t3179489
Be sure to act before you use your new tablet, and ideally do the same to the new one before connecting it to internet. Then the kill switch maybe will not even be sent to you/your old tablet.
:fingers-crossed:
edit : do a search here for 'root shield tablet lollipop' if you need info to get root or flash custom recovery : http://forum.xda-developers.com/shi...t-root-nvidia-shield-tablet-lollipop-t2972316
Note also that if you choose to (and succeed to) flash another (custom) ROM, such as Blisspop, you'll be safe as those custom roms avoid the kill switch (no /system/apps/TegraOTA folder in them)
If your new tablet is never activated then in theory the killswitch should never be sent out. So as far as I can see flashing a custom rom on the new device before letting it boot into android or connect to the internet should prevent device from showing as having been activated.
Also blocking Nvidia's OTA servers on the network level (you'll need custom firmware on your router) should do the trick as well.
Block all of these:
Code:
23.32.163.186
e886.g.akamaiedge.net
ota.nvidia.com.edgekey.net
ota.nvidia.com
Also it might be worth looking into whether flashing nomoreOTA.zip on the new tablet works to the same effect.
I used my new tablet and the both were working for the day, both have no problems so far.
I've been reading that they are sending out kill switches in 4 segments, by using the last 2 digits of the serial numbers system.
So mine hasn't gone threw yet i don't think.
So i need to root it?
Then delete the OTA file?
Then flash a custom firmware?
Thanks guys...
Just root it, do a full wipe=factory reset in TWRP and flash a custom Rom like Bliss and you will be OK.
Jarocks said:
If your new tablet is never activated then in theory the killswitch should never be sent out. So as far as I can see flashing a custom rom on the new device before letting it boot into android or connect to the internet should prevent device from showing as having been activated.
Also blocking Nvidia's OTA servers on the network level (you'll need custom firmware on your router) should do the trick as well.
Block all of these:
Code:
23.32.163.186
e886.g.akamaiedge.net
ota.nvidia.com.edgekey.net
ota.nvidia.com
Also it might be worth looking into whether flashing nomoreOTA.zip on the new tablet works to the same effect.
Click to expand...
Click to collapse
Just for info, I found out today that, even if my new tablet was also flashed with nomoreOTA.zip, and even if I did it before there was any internet connexion from it, my old tablet is now flagged and an urgent OTA (in fact the kill switch) is waiting to be sent to it. Of course it still works, thanks to nomoreOTA.zip. But Nvidia did flag the old tablet after 10 days use of the new one (maybe they check serial numbers of tablets connected to grid or to another Nvidia server). Both my old and my new tablets are still working.
Snah001 said:
Just root it, do a full wipe=factory reset in TWRP and flash a custom Rom like Bliss and you will be OK.
Click to expand...
Click to collapse
I see lots of root programs, is there a best one?
Can you flash with TWRP?
And someone said all i have to do is...
"Full Process
1) Unlock Bootloader.
2) Flash TWRP Recovery.
3) Get the no more OTA.zip from XDA and flash it via TWRP
4) Check if the update option is removed from Settings, if not flash it again.
Done! "
Is that ok also?
Thank you...
You need to root to flash twrp?
EowynCarter said:
You need to root to flash twrp?
Click to expand...
Click to collapse
No, but you do need an unlocked bootloader to fastboot flash anything.
amartolos said:
No, but you do need an unlocked bootloader to fastboot flash anything.
Click to expand...
Click to collapse
Yeah, that the conclusion i reached.
Flash done, now runing bliss pop. First start got me loads of errors. I went until i realized i had forgotten to wipe. It's been a while since i last played with custom roms.
oliwek said:
Just for info, I found out today that, even if my new tablet was also flashed with nomoreOTA.zip, and even if I did it before there was any internet connexion from it, my old tablet is now flagged and an urgent OTA (in fact the kill switch) is waiting to be sent to it. Of course it still works, thanks to nomoreOTA.zip. But Nvidia did flag the old tablet after 10 days use of the new one (maybe they check serial numbers of tablets connected to grid or to another Nvidia server). Both my old and my new tablets are still working.
Click to expand...
Click to collapse
Well, that's disappointing
oleg77 said:
Hello. You have to delete a folder (/system/apps/TegraOTA if you are on last firmware, with OTA 3.1) but to do this, you need root as folders in /system are not visible for the normal (unrooted) user. Or you flash a custom firmware, and flash nomoreOTA.zip that you'll find in the same forum : http://forum.xda-developers.com/shield-tablet/general/kill-kill-switch-shield-tablet-xx-t3179489
Be sure to act before you use your new tablet, and ideally do the same to the new one before connecting it to internet. Then the kill switch maybe will not even be sent to you/your old tablet.
:fingers-crossed:
edit : do a search here for 'root shield tablet lollipop' if you need info to get root or flash custom recovery : http://forum.xda-developers.com/shi...t-root-nvidia-shield-tablet-lollipop-t2972316
Note also that if you choose to (and succeed to) flash another (custom) ROM, such as Blisspop, you'll be safe as those custom roms avoid the kill switch (no /system/apps/TegraOTA folder in them)
Click to expand...
Click to collapse
Ok i followed the http://forum.xda-developers.com/shi...t-root-nvidia-shield-tablet-lollipop-t2972316
I got to "On the tablet, select "recovery reboot"
But i didn't see it so i selected reboot, i rebooted and was on stock i think?
1) I can see that a few more steps and i'm rooted.
But i'm nervous to try this again from that point.
Should i just start at unlocking the boot loader?
2) Is rooting the device permanently unlocking the boot loader?
3) can i just no OTA from unlocking the boot loader part?
Ok i got to side loader and in the command it says error can't find device and there's an android guy on his back with a red statement mark.
So I'm in developer USB.
I have unlocked the boot loader
I'm flashing the recovery
And i get to restart in recovery.
Then i get the menus to side load the supersu.zip
I renamed it with out caps, i even made a folder in C:\Program Files\Minimal ADB and Fastboot.
Cause it installed at C:\Program Files (x86)\Minimal ADB and Fastboot.
just to avoid the (x86)
when i try and leave the menu to reset it asked me to root, but i had the error so don't want to brick it if rooting with an error on side loading supersu.zip
What do i do?
Thank you...
says
loading: 'supersu.zip'
error: device '(null)' not found
And no android guy on his back this time.
A hat with a refresh orange symbol.
l337g0g0 said:
says
loading: 'supersu.zip'
error: device '(null)' not found
And no android guy on his back this time.
A hat with a refresh orange symbol.
Click to expand...
Click to collapse
You have unlocked bootloder and installed cwm recovery so yay! Download the SuperSU file on your tablet. Make sure you know where it downloaded to. Boot your tablet o to fastboot menu using the power/vol down. Select recovery mode using volume then power to select. Chose install zip then from sdcard (not the sdcard1) chose 0/ then search for where you put SuperSU and select it. Install. Then navigate to reboot. If asked to fix root pick yes
Sent from my Nexus 5 using Tapatalk
frenziedfemale said:
You have unlocked bootloder and installed cwm recovery so yay! Download the SuperSU file on your tablet. Make sure you know where it downloaded to. Boot your tablet o to fastboot menu using the power/vol down. Select recovery mode using volume then power to select. Chose install zip then from sdcard (not the sdcard1) chose 0/ then search for where you put SuperSU and select it. Install. Then navigate to reboot. If asked to fix root pick yes
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I don't have an SD card ATM. LOL
Why is the command with ADB not working?
l337g0g0 said:
I don't have an SD card ATM. LOL
Why is the command with ADB not working?
Click to expand...
Click to collapse
You don't need a card the sdcard referee to is your internal memory on your tablet. Not sure why ADB isn't working but I had a similar issue with cwm once.
frenziedfemale said:
You don't need a card the sdcard referee to is your internal memory on your tablet. Not sure why ADB isn't working but I had a similar issue with cwm once.
Click to expand...
Click to collapse
Ok that installed it.
WOW thank for that.
I guess I'm rooted, how do i test it and what does being rooted do for me?
Thank you....
Did you go back and flash the nomoreOTA zip? That is the most important part!
Sent from my Nexus 5 using Tapatalk
frenziedfemale said:
Did you go back and flash the nomoreOTA zip? That is the most important part!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Ok i just flashed nomoreOTA.zip.
It said the file was deleted and was a success.
I guess i can use the internet now?
I'm so nervous to turn the internet on and have the thing reset...
Did i need to run supersu to keep it rooted or always rooted until i use supersu to full unroot.
Thank you...
Just yesterday night when i came home, I plugged in my phone to the charger and i noticed that this FRP lock notification appeared.
https://cdn-images.xda-developers.com/direct/3/4/0/9/7/0/1/IMAG0008.jpg
It looks like that. I attempted to flash a stock firmware on my phone because apparently that would be a solution to this problem. When I attempt to flash it to the stock rom, this message appeared " can't open the serial(com) port". I do not have kies installed so that isn't one of the problem. I have some important data saved on this phone, and I can't lose it. Is there a way to resolve this issue without having to factory reset?
Frankie_Xenon said:
Just yesterday night when i came home, I plugged in my phone to the charger and i noticed that this FRP lock notification appeared.
https://cdn-images.xda-developers.com/direct/3/4/0/9/7/0/1/IMAG0008.jpg
It looks like that. I attempted to flash a stock firmware on my phone because apparently that would be a solution to this problem. When I attempt to flash it to the stock rom, this message appeared " can't open the serial(com) port". I do not have kies installed so that isn't one of the problem. I have some important data saved on this phone, and I can't lose it. Is there a way to resolve this issue without having to factory reset?
Click to expand...
Click to collapse
Can I download the pattern in the state Wipe out the FRP
If you want to make sure that phone no flash any firmware or to restore the factory Settings
china chenli said:
Can I download the pattern in the state Wipe out the FRP
If you want to make sure that phone no flash any firmware or to restore the factory Settings
Click to expand...
Click to collapse
Sorry, I dont understand you
Frankie_Xenon said:
Sorry, I dont understand you
Click to expand...
Click to collapse
I can wipe out the FRP
But can't guarantee your mobile data is not lost
china chenli said:
I can wipe out the FRP
But can't guarantee your mobile data is not lost
Click to expand...
Click to collapse
Do you or anybody else know if one of these 2 option would work?
http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
http://forum.xda-developers.com/tmobile-galaxy-s6-edge/help/how-to-to-5-0-2-t3142945
Frankie_Xenon said:
Do you or anybody else know if one of these 2 option would work?
http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
http://forum.xda-developers.com/tmobile-galaxy-s6-edge/help/how-to-to-5-0-2-t3142945
Click to expand...
Click to collapse
i wiped system cache and now this is appearing
http://i.imgur.com/PlMpjDq.png
In the first post, in the Odin Mode product name appears as SM-G920P but in Odin you try to flash G920T firmware.
install the stock rom with odin. I had same problem and fixed.
sent from n920c via tapatalk
What happened when you just restarted the phone? All I see in the first picture is the phone is in ODIN Mode, the phone has been rooted, and one of the 2 Factory Reset Protection modes is on.
return99 said:
install the stock rom with odin. I had same problem and fixed.
sent from n920c via tapatalk
Click to expand...
Click to collapse
I agree with this post. As I had the same problem on the Note 5. U must flash the version tar that is on the phone or u will get a failed error. I worked for 2 days and this the only thing that worked. I hope u have a TWRP backup saved to your PC or to an OTG sdcard. Because u are going to lose everything.
Sent from my SM-N920P using Tapatalk
It surprises me that no one has offered a real solution to this as of yet. It seeems like no one cares enough to follow up on their work. So here I am about to tackle another Custome Binary Blocked by FRP issue. Some of these FRP lock are quite difficult as you may see with this one I'm going to invite to the forum. I'll introduce Brookland and ask for an explaination of their issue so far.
Casper Young said:
It surprises me that no one has offered a real solution to this as of yet. It seeems like no one cares enough to follow up on their work. So here I am about to tackle another Custome Binary Blocked by FRP issue. Some of these FRP lock are quite difficult as you may see with this one I'm going to invite to the forum. I'll introduce Brookland and ask for an explaination of their issue so far.
Click to expand...
Click to collapse
Hi i dont know what aspecially you want to do...
would you just flash the stock rom? Then the frp Lock is no problem. You just need the right Firmware for your device. sm-g920F or 920T or 920P or 920W..........
to download samsung firmware just use:
samfirm
https://forum.xda-developers.com/attachment.php?attachmentid=3803841&d=1467715462
or use frija
https://forum.xda-developers.com/attachment.php?attachmentid=4886005&d=1574653611
booth of them doing the same....to download the choosen firmware in a fast way.
then flash the firmware with odin und it will work.
or
would you remove the frp lock to flash costum rom on a device you found in the gras or on the beach a device you didnt know the google account login data.
its possible but....
btw your picture upload in the first thread isnt availlable any more
solong
speedson
speedson said:
Hi i dont know what aspecially you want to do...
would you just flash the stock rom? Then the frp Lock is no problem. You just need the right Firmware for your device. sm-g920F or 920T or 920P or 920W.
Click to expand...
Click to collapse
If it were that simple I would have been over this a month ago. I'm not talking about the FRP lock that is related to the google account sign in. It's "Custom Binaries are Blocked by FRP Lock". That's sometimes a lot more difficult to fix than your standard FRP lock. Like this time. This ones not in my hands or I would've been done with it by now.
I'm trying to assist someone who has their S6 Plus locked up and I've already supplied them with the Stock, Combination and Repair Files with no positive results. So unless you have another method I haven't heard of this one will be number 2 of devices out of 47 that I couldn't return to operational status. Thanks for trying to help.
Ok pls tell me...what kind of s6 it is.
First you need to flash the stock Rom from Samsung.
I have a Idea...do you have Teamviewer? Then i could try remote Control to Support you.
But you need first to flash the stock Rom. Even Stock Firmware is flash on the device. You need wait for first start. During startup you must enter the Google Login data. This Google Login data is the Key to Open the device and after this. To remove the frp Lock. Then you can flash any othrr Rom you like to.
Lol
I have an S7 (SM-G930F) that I'd rooted using the chainfire method. All was good, but I unchecked oem unlock in developer settings without realising that it would put me into a FRP bootloop. :crying:
I've been reading around, but not getting very far - just want to get my data recovered. So far I've tried using Odin to flash the AP (just took the AP file out of the tar) of a stock ROM. This kind of allows the phone to boot now, however I get a message saying "Encryption failed. Unable to start up your device. The encryption process was interrupted. You need to reset your device to factory default settings. This will erase all your data."
Ideally I would like to gain access to my data. I'm able to boot into the default recovery, but can't flash twrp because its still FRP locked. All I can do is adb sideload - so if there's something I can use to at least transfer files to an sd card?
Help, ideas most welcome.
turbo_255 said:
I have an S7 (SM-G930F) that I'd rooted using the chainfire method. All was good, but I unchecked oem unlock in developer settings without realising that it would put me into a FRP bootloop. :crying:
I've been reading around, but not getting very far - just want to get my data recovered. So far I've tried using Odin to flash the AP (just took the AP file out of the tar) of a stock ROM. This kind of allows the phone to boot now, however I get a message saying "Encryption failed. Unable to start up your device. The encryption process was interrupted. You need to reset your device to factory default settings. This will erase all your data."
Ideally I would like to gain access to my data. I'm able to boot into the default recovery, but can't flash twrp because its still FRP locked. All I can do is adb sideload - so if there's something I can use to at least transfer files to an sd card?
Help, ideas most welcome.
Click to expand...
Click to collapse
When facing frp lock, hard reset (reflash stock, all files) is your only friend. Sad to say i dont think you can recover your data anymore, not unless you utilize samsung's autobackup feature using samsung cloud. (Or titanium backup with its cloud feature).
iOrpheus06 said:
When facing frp lock, hard reset (reflash stock, all files) is your only friend. Sad to say i dont think you can recover your data anymore, not unless you utilize samsung's autobackup feature using samsung cloud. (Or titanium backup with its cloud feature).
Click to expand...
Click to collapse
Sad, but I think that's what I expected to hear. I've gone ahead and reflashed stock.
turbo_255 said:
Sad, but I think that's what I expected to hear. I've gone ahead and reflashed stock.
Click to expand...
Click to collapse
I have the same but can't flash. Odin3 can't write to the phone. I thought it had to do with the FRP lock but something else is going on.
Blu_Life said:
I have the same but can't flash. Odin3 can't write to the phone. I thought it had to do with the FRP lock but something else is going on.
Click to expand...
Click to collapse
Is that the modified Odin? What does it say when you try and flash?
---------- Post added at 05:53 PM ---------- Previous post was at 05:48 PM ----------
Blu_Life said:
I have the same but can't flash. Odin3 can't write to the phone. I thought it had to do with the FRP lock but something else is going on.
Click to expand...
Click to collapse
Is that the modified Odin? What does it say when you try and flash?
hey guys, i got a issue about TWRP. I'm using android 7.1.1 NOF27B, and i want use custom TWRP. so i download firmware from google, flash-all. then reboot to system, copy twrp-pixel-installer-sailfish-3.2.2-0.zip to internal storage, then reboot to bootloader, using fastboot boot twrp-3.2.2-0-sailfish.img first to enter temporary twrp, then flash twrp-pixel-installer-sailfish-3.2.2-0.zip. the question is when i reboot to bootloader and enter to recovery, it does not show the password i need to enter, so i can not decrypt the data. i just want to have custom ESP backup to use different CDMA CHANNEL in CHINA. does anybody help me?
I ran into this issue as well, a workaround i found if you can get into your phone, is to shut off the pin or password in Security,then it should let you. Im not sure what the permanent fix is for this, but thats what I got to do on mine.
MrMeek said:
I ran into this issue as well, a workaround i found if you can get into your phone, is to shut off the pin or password in Security,then it should let you. Im not sure what the permanent fix is for this, but thats what I got to do on mine.
Click to expand...
Click to collapse
i will try if it helps. One more thing if I use temporarily TWRP by fastboot then no issues at all.it will ask to enter password, then perfect. But if renter same issues come out. So sad
I have a Samsung S20 Ultra that went black screen randomly, thought it was a bad screen and had it investigated by a local repair shop, HW seems all fine and they attribute it to a SW problem as the screen won't unlock. It seems permanently stuck at the lock screen. Enter the wrong password it will say wrong password, enter the right password to unlock it tries to unlock but goes nowhere. Multiple hard reboots tried and still no luck bypassing the permanent locked screen.
Flashing the phone obviously would solve the problem however there is data on the phone (pictures and videos) that I don't want to lose.
Is an update through the micro SD card slot possible as when I try to unlock after so many times I do get into the recovery/safe mode screen.
Thanks,
In the future backup all critical data to the SD card; use it as a data drive. On a 1tb card there's plenty of room if a .5tb card doesn't cut it.
I can do a full reload, apps, everything from my SD card. Only the DCIM folder (backup regularly to the SD card, and Do Not use "DCIM" for backup folder name), apps, Download folder and non-critical data go on internal memory.
The SD card is then backed up regularly and redundantly to at least 2 hdds.
Use a V30 rated card. I just ordered a 1tb Sandisk Extreme for my N10+, I outgrew my .5tb card.
As for the screen lock, I never use one. This is exactly why I don't; any failure be it software, firmware or your own memory can hopelessly lock you out. If there had been no lock set the chances of retaining access be a lot better.
Device security should always be more physical than software/hardware. When you set a bios/device password or encrypt a backup drive... you are the one most likely to get locked out. Security becomes worthless if it deprives you of access.
If you get it in safe mode get all the critical data off at once... you may only get one shot.
not 100% sure but see if you can connect the phone to your PC and update using smartswitch. I haven't done it personally so I don't know how to do step by step but i'm sure someone has put up and instruction online to follow. Hope this helps
I think OP might be better served inquiring about this in the correct S20 Ultra forum.
TheNewGuy92 said:
not 100% sure but see if you can connect the phone to your PC and update using smartswitch. I haven't done it personally so I don't know how to do step by step but i'm sure someone has put up and instruction online to follow. Hope this helps
Click to expand...
Click to collapse
You would have to allow the phone to be unlocked to allow this transfer.
WilliamSAndroid said:
I have a Samsung S20 Ultra that went black screen randomly, thought it was a bad screen and had it investigated by a local repair shop, HW seems all fine and they attribute it to a SW problem as the screen won't unlock. It seems permanently stuck at the lock screen. Enter the wrong password it will say wrong password, enter the right password to unlock it tries to unlock but goes nowhere. Multiple hard reboots tried and still no luck bypassing the permanent locked screen.
Flashing the phone obviously would solve the problem however there is data on the phone (pictures and videos) that I don't want to lose.
Is an update through the micro SD card slot possible as when I try to unlock after so many times I do get into the recovery/safe mode screen.
Thanks,
Click to expand...
Click to collapse
So try flashing firmware without doing a factory reset
iBowToAndroid said:
So try flashing firmware without doing a factory reset
Click to expand...
Click to collapse
Any instructions for this anywhere?
Thanks,
WilliamSAndroid said:
You would have to allow the phone to be unlocked to allow this transfer.
Click to expand...
Click to collapse
yes, I do recall this is part of the steps in connecting to a PC... but I was hoping that the OP had given permission before and the comp/phone recognizes each other without this step.
WilliamSAndroid said:
Any instructions for this anywhere?
Thanks,
Click to expand...
Click to collapse
There are hundreds of posts all over XDA with instructions for flashing Samsung firmware
iBowToAndroid said:
There are hundreds of posts all over XDA with instructions for flashing Samsung firmware
Click to expand...
Click to collapse
So this won't erase the data stored on the device?
WilliamSAndroid said:
So this won't erase the data stored on the device?
Click to expand...
Click to collapse
Will it go into safe mode? Try repeatedly.
Anything on internal memory I always consider expendable*. There are no guarantees with a crash in progress or if you start playing with the firmware.
If the /data partition is corrupted (the most likely cause) you be boned if you can't get in with safe mode.
* I got lucky twice and was able to get into safe mode. I don't push my luck anymore and modified how I do my critical data backup.
WilliamSAndroid said:
So this won't erase the data stored on the device?
Click to expand...
Click to collapse
As long as you flash the correct CSC, no
iBowToAndroid said:
As long as you flash the correct CSC, no
Click to expand...
Click to collapse
I am hoping to give this a try, I will try to search around for instructions.
Not getting any responses in another thread so thought I would post back in this one.
I have gotten a copy of the firmware by using Bifrost, I would like to side load through an SD card, the resultant file after Bifrost ran is xxxxx.zip.enc4 do I rename this to update.zip copy to SD and boot into recovery mode and select Apply update from SD card?
Thanks,
WilliamSAndroid said:
Not getting any responses in another thread so thought I would post back in this one.
I have gotten a copy of the firmware by using Bifrost, I would like to side load through an SD card, the resultant file after Bifrost ran is xxxxx.zip.enc4 do I rename this to update.zip copy to SD and boot into recovery mode and select Apply update from SD card?
Thanks,
Click to expand...
Click to collapse
Nope. No idea what "bifrost" is but it's not much use if it won't decrypt the file for you. The file needs to be decrypted into a zip. Just use Frija
iBowToAndroid said:
Nope. No idea what "bifrost" is but it's not much use if it won't decrypt the file for you. The file needs to be decrypted into a zip. Just use Frija
Click to expand...
Click to collapse
I followed these instructions.
How to update your Samsung Galaxy smartphone and install official firmware
Follow these instructions to manually install Android updates through recovery and full firmware using Odin on Samsung Galaxy smartphones.
www.xda-developers.com
I used samloader and it said it decrypted it.
The resulant file is xxxxx.zip.enc4
WilliamSAndroid said:
I followed these instructions.
How to update your Samsung Galaxy smartphone and install official firmware
Follow these instructions to manually install Android updates through recovery and full firmware using Odin on Samsung Galaxy smartphones.
www.xda-developers.com
I used samloader and it said it decrypted it.
The resulant file is xxxxx.zip.enc4
Click to expand...
Click to collapse
Then if you have issues, you need to either talk to the person who wrote the instructions (the developer) or find a different way to do it, like I suggested