Hi all,
New user here, not much experience rooting or messing with firmware for phones. I was following the guide on how to flash the SM-935U firmware to the verizon model of the Galaxy S7 Edge, and may have bricked my phone. Here's what I did.
Followed the guide to the letter.
Powered off phone, booted to Download mode
Fired up Odin, selected the SM-935U firmware files, and clicked start.
It gave me an Auth error, which research revealed means that I forgot to turn off Reactivation Lock. I figured, "Fine, I'll just disable it. However, I can't get the phone to boot again. Every time I leave download mode, it boots into Android Recovery, where, no matter what I do, it just reboots into Android Recovery. I can't Wipe anything because it can't mount /system - probably due to Reactivation Lock?
I've been research and researching ways around this, and everything I find just points back to flashing it with the stock firmware. But then I read that you can't even do that if Reactivation lock is on, because Odin will still fail with the Auth error. So, I can only get it to boot to recovery mode, and I can't flash it with anything?
I did read somewhere that if I choose to wipe the phone's EFS with Odin that it should override activation lock, but then it clears the phones IMEI, which is an even bigger mess, isn't it?
I feel like I have to be missing something... since it never did the wipe, why is it that I can't get past the recovery mode. Shouldn't I still be able to get into the system somehow?
Does Anyone have any thoughts or suggestions for me? I'd really like to not be stuck with a permanently bricked S7 edge if at all possible....
Solved
Just wanted to post this to help anyone else who might have this issue. Turns out that you can flash the stock firmware, as long as you're flashing at least the same version or newer of the stock firmware as what the phone was running prior to getting stuck in recovery mode. It shows you what version it was running in the recovery mode at the top.
So for me, I googled the exact firmware version that recovery mode said the phone was running, downloaded it, flashed it with ODIN, and it worked just fine. Had to choose to wipe with the recovery mode after I flashed it, but then it booted like normal. - Then I enabled OEM unlocking under the developer menu, and tried flashing the U firmware again with ODIN, and it still failed with the auth error. Huh.
Turns out (maybe I wasn't doing it right or something) that you can't flash older versions of the firmware to the phone. But, as long as OEM unlocking is enabled, you can flash the U (unlocked) version of the current firmware to the phone and it will take just fine. Hint: I was able to determine the "version" number by looking at the last 4-5 characters of the build number... the verizon version I was running for my SM-935V was: VZW-G935VVRU4API3 - So I googled the API3 firmware and found the U (unlocked) version for my carrier (I happen to be using T-Mobile) on this site: https://samsung-firmware.org/model/SM-G935U/ and found the zip file name which was TMB-G935UUEU4API3-20161011161050.zip, googled that, got the rapidgator link, downloaded it, and that flashed just fine to the phone, and now my T-Mobile SIM works perfectly in what was previously the SM-935V, which now identifies as an SM-935U in settings. It's beautiful.
Also, you need the PIT file, but I was able to use the PIT file for the phone model number (again, found at the top of the android recovery menu), which for my phone was: HERO2QLTE_USA_VZW.pit (googled that and got it off androidfilehost) - I was able to use that PIT file for the T-Mobile U version of the firmware and it worked just fine.
Hope this helps someone.
Related
I have been trawling the internet for literally hours.
This is my final hope before I get really desperate with this device.
I bought a Samsung Galaxy Edge+ online as a demo unit so I could use it as a glorified tablet,
since it was a demo unit it had demo software which I tried to remove using the 5444 password
trick on the retail software to no avail. So I decided to root the phone using Odin and the
SM-G928 F/I/C/K/S software as i couldn't find the particular software for this phone anywhere.
This worked but every time I booted the phone it would give me the 'KERNEL IS NOT SEANDROID ENFORCING'
on the top left of the device which I promptly ignored and continued to use the device, I downloaded
root check which said my device was rooted and then I downloaded system app uninstaller to try remove all the trial
software, which unfortunately didn't work. I then attempted a hard reset, which also didn't work and just
rebooted the device, finally i decided to download Flashify and TWRP recovery to try and delete the trial software
from there. At this point I was just messing around with the phone when I noticed a thread that said i needed
titanium backup to fully delete the software, so i rebooted the phone and it has been stuck on the bootup screen
ever since, I have tried several methods to get it to work including re-flashing the software onto it,
(the SM-G928F one I mean) but i simply cannot find the correct one for my device.
Any help would be greatly appreciated :good::good::good::good:
The device is running 5.1.1
I am not sure of the kernel or anything like that as I am quite noobish.
re: phone issues
MeMyPhoneAndI said:
I have been trawling the internet for literally hours.
This is my final hope before I get really desperate with this device.
I bought a Samsung Galaxy Edge+ online as a demo unit so I could use it as a glorified tablet,
since it was a demo unit it had demo software which I tried to remove using the 5444 password
trick on the retail software to no avail. So I decided to root the phone using Odin and the
SM-G928 F/I/C/K/S software as i couldn't find the particular software for this phone anywhere.
This worked but every time I booted the phone it would give me the 'KERNEL IS NOT SEANDROID ENFORCING'
on the top left of the device which I promptly ignored and continued to use the device, I downloaded
root check which said my device was rooted and then I downloaded system app uninstaller to try remove all the trial
software, which unfortunately didn't work. I then attempted a hard reset, which also didn't work and just
rebooted the device, finally i decided to download Flashify and TWRP recovery to try and delete the trial software
from there. At this point I was just messing around with the phone when I noticed a thread that said i needed
titanium backup to fully delete the software, so i rebooted the phone and it has been stuck on the bootup screen
ever since, I have tried several methods to get it to work including re-flashing the software onto it,
(the SM-G928F one I mean) but i simply cannot find the correct one for my device.
Any help would be greatly appreciated :good::good::good::good:
The device is running 5.1.1
I am not sure of the kernel or anything like that as I am quite noobish.
Click to expand...
Click to collapse
First thing to do is to get into STOCK recovery and do a "Factory Data Reset"
or you can boot the phone up and go into "Settings>Backup and Reset" and
select "Factory data reset".
After doing that odin flash the proper S6 Edge+ Lollipop 5.1.1 or the new Marshmallow 6.0 firmware.
You can see the exact model of your G928 phone by going into settings and scroll down to "about"
there you will find the specific model of your phone.
Be sure to ONLY odin flash the correct firmware for your phone's model.
Once you do all the above you will no longer see:
'KERNEL IS NOT SEANDROID ENFORCING'
The only reason you see that is because the phone is rooted.
After odin flashing the proper firmware your phone will no longer be rooted
unless you root the phone again.
Good luck,
Have a great day!
Misterjunky said:
First thing to do is to get into STOCK recovery and do a "Factory Data Reset"
or you can boot the phone up and go into "Settings>Backup and Reset" and
select "Factory data reset".
After doing that odin flash the proper S6 Edge+ Lollipop 5.1.1 or the new Marshmallow 6.0 firmware.
You can see the exact model of your G928 phone by going into settings and scroll down to "about"
there you will find the specific model of your phone.
Be sure to ONLY odin flash the correct firmware for your phone's model.
Once you do all the above you will no longer see:
'KERNEL IS NOT SEANDROID ENFORCING'
The only reason you see that is because the phone is rooted.
After odin flashing the proper firmware your phone will no longer be rooted
unless you root the phone again.
Good luck,
Have a great day!
Click to expand...
Click to collapse
I can't boot the phone up, if I could I would, I can't find the software for this particular model, which is aforementioned SM-G928X,
If you could help me with that, I would appreciate it. The phone is stuck on the Saumsung boot up, it doesn't actually boot up into
the lock screen so I can't do anything with it, if you could help me with link to the SM-G928X firmware that I could use in ODIN
that would be greatly appreciated cause the phone is a paper weight at this point.
I had a moment of madness and decided to do what you said anyway, and I can't factory reset the phone from the recovery menu as it says
its due to security policies or something of that nature, which again I mentioned in the initial thread.
Also to clarify, I can't flash my own firmware because I can't find the firmware anywhere on the internet.
re: firmwares
MeMyPhoneAndI said:
I can't boot the phone up, if I could I would, I can't find the software for this particular model, which is aforementioned SM-G928X,
If you could help me with that, I would appreciate it. The phone is stuck on the Saumsung boot up, it doesn't actually boot up into
the lock screen so I can't do anything with it, if you could help me with link to the SM-G928X firmware that I could use in ODIN
that would be greatly appreciated cause the phone is a paper weight at this point.
I had a moment of madness and decided to do what you said anyway, and I can't factory reset the phone from the recovery menu as it says
its due to security policies or something of that nature, which again I mentioned in the initial thread.
Also to clarify, I can't flash my own firmware because I can't find the firmware anywhere on the internet.
Click to expand...
Click to collapse
I have done a bit of research on your G928X device and I think you are in luck.
Check out this link carefully http://pdadb.net/index.php?m=specs&id=8759&c=samsung_sm-g928x_galaxy_s6_edgeplus_lte-a_samsung_zen
and you will see that the firmware in your phone is identical to many other G928 firmwares as you will see in that link.
Odin flashing any of the ZEN firmwares in that link cannot brick your phone, the worse thing that can happen is that it will not
work. (just like it's not working for you right now).
I would go a head and odin flash the S6 Edge+ G928T firmware which is also the ZEN baseband firmware, there are many S6 Edge+ phones
using the exact same firmware. All Samsung S6 Edge+ firmwares contain the modem but not all of them will be compatible with your
carrier but at least you will be able to boot your phone normally without getting stuck on boot screen or bootlooping to start with.
You can get the G928T firmware from http://sammobile.com OR
https://www.androidfilehost.com/?fid=24499762636004597 (fast download)
Good luck,
Have a great day!
(Soft-)Bricked S7 Edge/G935F with FRP lock & DRK error, but no root/OEM unlock/ADB
Hello guys,
I bought a, what I thought to be, soft bricked S7 Edge (G935F) from the bay. It was listed as having sw issues, so I thought I could easily fix the issue myself. Stupid me, this one really isn't easy to fix. I've tried a lot of different hints that I found meandering around the web, but none of them have proofed working so far. I would appreciate some help because I don't seem to be making any progress.
When I got the phone, it would boot directly into Android Recovery with a dm-verity error on the bottom.
Below is what I have tried already:
1 . First I did the obvious, factory reset and wipe partition. No change.
2. Downloaded the latest firmware with updato (SM-G935F Region DBT) and flashed with Odin. It then booted into a screen with a hazard sign and a DRK error (Device does not have DRK, please install DRK first. press any button). Then returned to Android Recovery with variations of the DRK and dm-verity error messages
3. I flashed the same firmware again. This time the phone booted up to a Samsung error that said to use SmartSwitch's Emergency recovery. I tried but it asks for a recovery code and I don't have one.
4. I used an older version of SmartSwitch which gave me the initialization option where you need to input the device model and SN - SmartSwitch decided not to cooperate and noted that the S7 edge does not support initialization
5. I tried to flash CF-autoroot but it gave an error in Odin and failed because it is "Blocked by FRP Lock". I can't boot normally into android. Any workaround?
6. I used a dm-verity workaround file (G935FXXU1DQC4_FIX_DRK_dm-verity.tar) to actually get the phone booted up- but then it asks for the account information to do away with the FRP lock. And the former owner does not want to give me his login information. In addition, none of the workarounds (bluetooth, modem terminal prompts, etc.) did work.
7. Flashed oldest Android version I could find for the G935F - 5.1.1 - this gave me a prompt right after reboot that looks like the password request for encrypting memory. default_password and variations did not work. I am still stuck with...
No Support SINGLE-SKU
Supported API: 3
dm-verity error...
failed code : 0x02
...in the recovery
8. I flashed the combination file and was able to boot into Factory Binary and used the IMEI recovery option which is supposed to fix also the DRK issue. No luck.
So, this is where I am right now. If anyone out there still has sparks of hope, I would be delighted to hear about them.
Thanks much in advance!
Conversion software and ADB Shell
Small update - I booted into factory mode again using the conversion firmware. This way, I could connect to the device via ADB and use ADB shell. There is a guide (here: https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516) which guides through IMEI recovery using the conversion software and factory mode - that is supposed to also help with DRK issues. Did not work for me.
Another great guide (here: https://forum.xda-developers.com/no...fix-drk-dm-verity-factory-csc-serial-t3422965) used ADB shell to push and repair the DRK with some additional files. Since the device is not rooted, I did not get very far, either.
So, no progress whatsoever.
In summary, I can get the device booted up into factory mode using the conversion firmware, or, by using the dm-verity tweaked firmware, I can end up in the Google Account locked part of the initial start-up settings.
Any ideas?
Have you looked at the process to completely re-do a phone stuck in the Google auth log-in? At least that is how I understand where you are stuck. I have a phone arriving soon that I will need to re-flash to get out of that, via Odin.
JeffDC said:
Have you looked at the process to completely re-do a phone stuck in the Google auth log-in? At east that is how I understand where you are stuck. I have a phone arriving soon that I will need to re-flash to get out of that, via Odin.
Click to expand...
Click to collapse
Hi JeffDC,
Thanks a lot for the reply. How would this process look like? I have flashed the phone with all sorts of variations of Android L, M and N - plus the combination fw and the one with the dm-verity/DRK workaround which at least got the phone booted up. But then I am stuck at the google auth request.
I cannot flash anything custom since the FRP lock is on.
Hence, if there is any other way to re-do the phone as you are saying, I would live to hear about it.
https://forum.xda-developers.com/s7-edge/help/s7-edge-custom-binary-block-frp-lock-t3347688
https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
https://forum.xda-developers.com/no...fix-drk-dm-verity-factory-csc-serial-t3422965
JeffDC said:
https://forum.xda-developers.com/s7-edge/help/s7-edge-custom-binary-block-frp-lock-t3347688
https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
https://forum.xda-developers.com/no...fix-drk-dm-verity-factory-csc-serial-t3422965
Click to expand...
Click to collapse
Hi JeffDC,
Thanks a lot for the links.
Link #1: I can flash the file #1 and get the device visible for ADB by using the combination FW before starting the steps. Unfortunately, step #2 does not work due to lack of permissions. I guess because of missing root.
Links #2 and #3: These are the guides I was already referencing in my post #2 - they both do not work due to, I guess, missing root.
Smart Switch initialization
Update: I got smart switch to do the update and initialization for the device. Workaround was to use a different real serial number than the one of the actual device (I can only assume that it has got to do with country presets).
Cool stuff, all went smooth - but, still the same result. The device ends up in recovery showing the dm-verity error (failed code : 0x02) with FRP lock on and no root.
https://forum.xda-developers.com/ve...-factory-reset-protect-unlock-t3414590/page11
Interesting read, particularly ignoring the trojan squabbling.
Uses script and setup files to get around FRP.
I suggest you to re-try flashing with Odin the Stock Marshmallow Firmware. Then Boot Into Stock Recovery do a Full Wipe.
zzThrain said:
I suggest you to re-try flashing with Odin the Stock Marshmallow Firmware. Then Boot Into Stock Recovery do a Full Wipe.
Click to expand...
Click to collapse
Thanks for the recommendation. Done that (MM downgrade and full wipe) - same result, still DRK error only booting to recovery.
JeffDC said:
https://forum.xda-developers.com/ve...-factory-reset-protect-unlock-t3414590/page11
Interesting read, particularly ignoring the trojan squabbling.
Uses script and setup files to get around FRP.
Click to expand...
Click to collapse
Hi JEffDC, thanks for the follow-up hints. Very interesting read and approach. As commented in the other thread, I think the package download link in the opening post is dead. I am also curious to see 2 more complexities in action:
1. Will this work on a G935F variant (Exynos vs Snapdragon)?
2. The only way for me to get to the Google Account prompt is by using the modded dm-verity version mentioned in my first post - but I am not sure I can get ADB access enabled simultaneously
Good luck.
Deleted
Hey sathiere,
Came across this. It apparently removes the FRP before the system can start it up! Let me know what you think. I'm going to try it on a locked Edge next week or two. Seems to go right after the FRP protection file.
https://forum.xda-developers.com/galaxy-s7/help/how-to-bypass-frp-galaxy-s7-possibly-6-t3622126
and the download link works.
JeffDC said:
Hey sathiere,
Came across this. It apparently removes the FRP before the system can start it up! Let me know what you think. I'm going to try it on a locked Edge next week or two. Seems to go right after the FRP protection file.
https://forum.xda-developers.com/galaxy-s7/help/how-to-bypass-frp-galaxy-s7-possibly-6-t3622126
and the download link works.
Click to expand...
Click to collapse
Hi JeffDC, came across that thread last night - checked it out, but cannot really make sense of it just now. I will be posting directly in this one in the next minutes.
Regarding the link for the other thread - the google drive link for me shows invalid/no content...
sathiere said:
Hi JeffDC, came across that thread last night - checked it out, but cannot really make sense of it just now. I will be posting directly in this one in the next minutes.
Regarding the link for the other thread - the google drive link for me shows invalid/no content...
Click to expand...
Click to collapse
Yes, I am hoping for a response to my post there, near the end, clarifying. I think I get the method, and it's really pretty straight forward, really.
sathiere, I think basically what it does is provide two connections to the phone at the same time, one via Odin, and the other via direct ADB.
Step one is to flash a Universal boot loader, which is unlocked or can be unlocked via ADB. Now with the locked boot loader out of the way, on to getting rid of FRP.
Step two is run the. bat file which deletes the Persistence file, which is the Google encrypted setup file/FRP file. BOOM, FRP gone.
Then either stay on the Universal bootloader, or go back and flash the OEM.
Brilliant!
I have the same problem with a sm930f binary 2 boot loader. Stock Rom doesn't start and frp lock. How you fix it ? Thank you
Try this method
https://forum.xda-developers.com/general/general/solved-bypass-frp-lock-drk-error-t3779082
I have a Samsung Galaxy S7 Edge, I thought I was smart enough to try and root the phone but I was wrong. Now it is in a bootloop. I have tried everything...I did a factory reset, flashed, cleared the cache partition, I have used Kies3, Smart Switch, ADB server, Odin , I tried it all and now I am just needing help if anyone can help me.
I tried to go back to Kies3 but it keeps rejecting my serialnumber for some reason, I even went back to the recovery log in the recovery console to make sure the serial number was right. I also thought maybe I flashed the wrong firmware with Odin? I am not sure I got the right one because I amnot sure what PDA means on the download site, so I am just lost now. The only thing it does is a bootloop and I can get to recovery console, and the bootloader.
If anyone can help I would so appreciate it.
pinkgeek said:
I have a Samsung Galaxy S7 Edge, I thought I was smart enough to try and root the phone but I was wrong. Now it is in a bootloop. I have tried everything...I did a factory reset, flashed, cleared the cache partition, I have used Kies3, Smart Switch, ADB server, Odin , I tried it all and now I am just needing help if anyone can help me.
I tried to go back to Kies3 but it keeps rejecting my serialnumber for some reason, I even went back to the recovery log in the recovery console to make sure the serial number was right. I also thought maybe I flashed the wrong firmware with Odin? I am not sure I got the right one because I amnot sure what PDA means on the download site, so I am just lost now. The only thing it does is a bootloop and I can get to recovery console, and the bootloader.
If anyone can help I would so appreciate it.
Click to expand...
Click to collapse
If you have Bootloader it can be fixed. Download the firmware from sammobile and put the files in the spot it says it is. PDA file will go to PDA etc.
Edit. Sorry forgot that PDA is the old Odin. Download the newer version v3.12 and put the AP files in the AP slot and the same with the CP file and CSC. You might wanna try leaving the BL file out as when I did mine it would only work if I didn't add BL.
I had quite the same thing. I rooted my S7 Edge abd installed Lineage, but I was not satisfied of it, so I decided to come back to stock ROM. This was impossible : flash with Odin, with TWRP, etc... All came to a bootloop or freeze when the phone booted.
And yesterday, after a new attempt, the phone booted and now, it works very well. I don't really understand what changed or what I did more, but it seems that your phone is not bricked. Try another Odin flash with forcing CSC maybe.
Hi, recently I accidentally bricked my Galaxy Tab A 10.1 with Spen (SM-P580) by accidentally disabling "OEM Unlock" in the developer settings while I had TWRP and a custom ROM installed. I was only able to get into download mode due to the factory reset protection lock, so I tried downloading the stock firmware online and then flashing it to bring the device back to fully stock firmware so I could get past the lock and not have a brick. Unfortunately, when I flashed the firmware, despite it seemingly being for my specific device (and matching my build number), I was no longer able to boot the device at all. It would turn on and would seem to immediately lose power, charging would turn on the flash and cause it to heat up, and no amount of charging would fix the issue. It was completely bricked and there was no way for me to go back into download mode to try flashing again or try flashing a different firmware. Thankfully, I contacted Samsung and because it's still under warranty they were nice enough to fix it for free, and did so by completely replacing the motherboard according to the repair slip, which is not something I would have been able to do.
My question is: How do I make a full backup of the stock firmware and recovery so if this somehow ever happens again where the FRP lock kills my device, I can reflash in download mode the original firmware that I know is 100% going to work with it and is correct? I don't want to gamble with potentially using the wrong firmware again, seeing as that gamble killed the thing.
The Model is SM-P580NZKAXAR. Based on the last part (XAR) and the fact that other non-sammobile sites listed the US wifi only firmware as XAR, I assumed "Cellular south (XAR)" was the correct firmware I needed which was obviously incorrect as it completely bricked the device. For this reason, I'm wondering if there's a way with software on windows or something to completely backup the existing stock firmware before I do anything, because I doubt Samsung would be so nice a second time, and I'd really rather not go through all this again. Obviously these websites get the original firmware that's flashable via download mode somehow, so I'd like to know how or if that's possible. Also before I went and downloaded the firmware I checked the Samsung desktop app that allows you to fix firmware issues but it said my device wasn't supported so it wasn't much help. I'd like to avoid installing any custom recoveries ahead of time as if something gets messed up there will be no way for me to actually boot into recovery as far as I'm aware, and the FRP lock will block me from reflashing the custom recovery or anything else that isn't stock. It goes without saying that if this is possible I'd like to do it without installing a custom recovery or rooting as I'd like to have a proper fully stock backup that isn't going to trip the FRP lock.
Also the way I accidentally disabled OEM Unlock was I simply toggled the developer options off and then back on in a slimmed down version of the stock rom, but in doing so it also reset the OEM unlock setting and I completely forgot to make sure it was still enabled. Next thing I know I go to reboot (was trying to figure out an issue with a usb device) and then the thing was FRP locked. Needless to say, it was something extremely simple and easy to do by accident. I also just checked the device and the build number matches the firmware that I downloaded, so I don't know if it was mislabeled or what but something was not correct.
Edit 3: TL;DR: This is appears to be an S8 exclusive error, it's shown in the recovery:
"Product device tree not found, couldn't verify firmware" or something like that. For solutions, please look that up.
So, I bought a bootlooping S8 in the hopes of fixing it.
Since OEM and FRP lock are on, I went with installing Samsung firmware on it, as installing a custom recovery at this point is not possible.
The default recovery wouldn't work, so I wasn't able to know which firmware exactly to flash, because I couldn't find out which model exactly I have bought.
I do not know the carrier of the device either, but it should be from some german provider.
All of the firmwares I tried just bootlooped, but the recovery works again, except for ADB, which is quite unfortunate, and I have no idea why it fails, the device shows up when I'm in the recovery menu, but as soon as I activate ADB, it's gone from the list of connected devices.
Combination firmwares sometimes show some turning gears animations, but then crash with some, thought often memory related, pretty random crash issue.
Another problem I am now facing is that in the process of trying to find a working firmware I now upgraded the devices "binary level"? (forgot what exactly it was called) to 6, so I can't flash any older firmware or combination firmware than 6, since downgrading isn't allowed.
I received the device with either binary level 1 oder 2.
My theory is that I don't have the right firmware, since I keep seeing dm-verity and license errors...
I am happy to provide logs if necessary.
The goal is to have an unlocked bootloader/ custom recovery.
I literally am going INSANE over this FRP blocking me from flashing TWRP and being done with this in under 10 minutes, please help :c
PS: Some random info attached
Edit 1: With the IMEI code i found while opening the phone I now know my model number: SM-G950FZKADBT.
Any tips for finding the PDA code of the originally installed system? Or finding a matching firmware?
Is this even neccesary? Why do official firmwares not work for me? :c
Edit 2: Somewhat solution: I think the only way to recover this device would be to find it's firmware, which is just NOT to be found...
So, until a miracle happens I'm gonna keep reading "Firmware is not valid" errors in the log
Did you look in samfrew.com ? ? ? I just grabbed a fw from there.
The dnld was loooong so I purchased a privilege for faster speed . . .