Database Users

Unable to detect new OTA updates

Hi guys,
For some strange reason my phone is unable to detect new OTA updates. I'm running I9505XXUGNF1 per the screenshot below and when I try and run an update to I9505XXUGNG2 I get a message saying "The latest updates have already been installed" even though NG2 is available via the OTA server.
Can someone help me please?
In order to upgrade I need to download the 2gb ROM file and install using Odin which is a pain when you're travelling!
Is it something to do with DBT? Is there some way of changing my phone into a DBT phone?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my GT-I9505 using Tapatalk

Does someone know how I can change my CSC? I've seen a few guides but they require root and an earlier ROM version which I can't go back to...
Sent from my GT-I9505 using Tapatalk

Dial *#1234# and attach what appears. You have wrong CSC for sure.
CSC is the country code of ur phone.
- Conect it to Kies 3 for know ur CSC. (pic attached)
- Download the correct firmware for ur device and flash it through ODIN.

I've flashed through ODIN a number of times but my CSC doesn't change... How can I force a CSC change?
Joku1981 said:
Dial *#1234# and attach what appears. You have wrong CSC for sure.
CSC is the country code of ur phone.
- Conect it to Kies 3 for know ur CSC. (pic attached)
- Download the correct firmware for ur device and flash it through ODIN.
Click to expand...
Click to collapse

OK, so I re-downloaded the following file:
DBT-I9505XXUGNF1-20140619102758.zip
and followed the instructions from:
http://forum.xda-developers.com/showpost.php?p=43553707&postcount=14
Make sure you take a backup via Kies if you need personal files
Download the respective stock ROMS from sammobile.com or samsung-updates.com or see thread on Stock Roms on XDA
Extract zip to get tar.md5
Put device into download mode (Vol down+ Home + Power) and Flash using Odin (PDA option)
Wait till device reboots back into Android after completing the flash and recovery
Once device reboots, do a Factory Reset via Settings > Accounts
Once device reboots after Factory Reset/recovery, enter the google account info and restore settings and then turn off the device
Boot device back into download mode (Vol down+ Home + Power)
Re-flash the same downloaded firmware for a second time via Odin
Once the device reboots after the 2nd flash, your CSC should have changed to the CSC of the ROM you downloaded, and Kies also should show that CSC has changed and it should allow future updates via Kies or OTA
And my CSC still says OXA which I think is "open europe" (same as before) and OTA updates are still not available.
Can someone with knowledge of this please help?

Galaxy Tab SCH-I800 Verizon Root and CWM recovery full tutorial

Hi everybody, you probably read many tutorials in how to root and install CWM to you Galaxy Tab and tried many methods and different android apps but none of them worked or you faced a non-common problem.
Here is a full tutorial about rooting and install a custom recovery "CWM" to Galaxy Tab SCH-I800 Verizon Running 2.3.5 android system version without flashing a modified rom.
.: STARTING NOTE :.
1. Platform: Windows 32bit and 64bit
2. Use it at your own risk.
.: ROOTING :.
Files to be downloaded:
1. SCH-I800_Patched_Kernel_FaridAlkorashy.tar Download
2. DooMLoRD_v4_ROOT-zergRush-busybox-su.zip Download
3. Odin3-v1.85.zip Download
Steps:
1. Reboot the Tab into the "Download Mode":
a. Power off the Tab.
b. Hold volume down button + power button at the same time till "Download" screen appears.
2. Connect the Tab to the computer.
3. Extract Odin3-v1.85.zip, and start "Odin3 v185.exe".
4. Flash the SCH-I800_Patched_Kernel_FaridAlkorashy.tar:
a. Place SCH-I800_Patched_Kernel_FaridAlkorashy.tar to PDA in Odin.
b. Click on Start.
5. After rebooting the device, enable debuging mode:
a. Disconnect the device from the computer.
b. Goto Settings -> Applications -> Development.
c. Check USB debugging.
d. Reconnect the device with the computer again.
6. (Recommended) Disable your antivirus till you finish step 7.
7. Extract DooMLoRD_v4_ROOT-zergRush-busybox-su.zip, and start "runme.bat".
NOW you have rooted your Galaxy Tab
.: INSTALLING CWM RECOVERY :.
Files to be downloaded:
1. Flashify-1.1.6.apk Download
2. SCH-I800_Patched_Recovery_FaridAlkorashy.tar Download
3. recovery-clockwork-5.0.2.7-vzwtab.zip Download
Steps:
1. Flash SCH-I800_Patched_Recovery_FaridAlkorashy.tar file using Odin:
a. Place SCH-I800_Patched_Recovery_FaridAlkorashy.tar to PDA in Odin.
b. Click on Start.
2. (Recommended) Do not let the system boot up after flashing the file, just wipe data and catch:
a. (Immediately) after finish flashing file, disconnect the Tab from your computer.
b. Hold volume up button + power till Samsung logo appears then release power button only.
c. When the NEW recovery appears, choose "wipe data/factory reset", then yes...
d. After wiping data, choose "wipe cache partition", then yes...
e. Reboot the tab.
NOW you have CWM Recovery in your Galaxy Tab
(Just in case):
If the CWM recovery didn't show up and the stock recovery showed instead then complete the steps below
3. After rebooting, copy recovery-clockwork-5.0.2.7-vzwtab.zip to the root of your SdCard.
4. Install Flashify-1.1.6.apk to your ROOTED Galaxy Tab.
5. Start "Flashify" application on your Tab and give it root permission.
6. Flash recovery-clockwork-5.0.2.7-vzwtab.zip:
a. Choose Zip file in Flashify.
b. Locate to recovery-clockwork-5.0.2.7-vzwtab.zip.
c. Choose cwm, then touch Yup! button.
d. Choose Reboot Now.
7. If flashing the file stucks leave it for two minutes then force power of the system:
a. Keep holding power button till the screen goes black.
8. (Recommended) Do not let the system boot up after flashing the CWM file, just wipe data and catch:
a. (Immediately) after finish flashing file, disconnect the Tab from your computer.
b. Hold volume up button + power till Samsung logo appears then release power button only.
c. When the new recovery appears, choose "wipe data/factory reset", then yes...
d. After wiping data, choose "wipe cache partition", then yes...
e. Reboot the tab.
NOW you have CWM Recovery in your Galaxy Tab
.: NOTE :.
1. If Odin bricked your system then apply step 3 and 4 in ROOTING to unbrick it.
2. If Flashify app ask you to unlock the limitation of usage, then reset it:
a. Delete this file: /sdcard/Download/logsf
3. Thank you, and good luck.

newbie need help Please
Please tell me what android version when I have finish rooted ?
Thanks

Root Galaxy Tab SCH-I800 Verizon problem
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I got this problem when tried to root . and I tried many time to put it to download mode as hold power button and volume down , but it like a brick . Please help me out .
Please help me solve it
I do appreciate. Thank you

I have the Same issue
liengia said:
I got this problem when tried to root . and I tried many time to put it to download mode as hold power button and volume down , but it like a brick . Please help me out .
Please help me solve it
I do appreciate. Thank you
Click to expand...
Click to collapse
I know this thread is old, but if you happen to see this can you let me know if you figured out a way to fix it? I repeated Step 3 and 4 to no avail.

When i`m goin to instal the CWM recovery, the tab have to be in download mode or what? thanks, already rooted

I got this problem when tried to root . and I tried many time to put it to download mode as hold power button and volume down , but it like a brick . Please help me out .
Please help me solve it
I do appreciate. Thank you
>>>>>>>>>>>>
Hi .
Just install stock recovery again to get the tab in download mode again .
Stock recovery can be found in the stock firmware files , mostly in the ( AP , Code ) file .
Just try to extract file using " 7z '' . There you will find the stock recovery .
Put it in the AP or Code field and flash it using Odin . While the tab in the dead screen.
Regards
---------- Post added at 06:03 AM ---------- Previous post was at 05:59 AM ----------
liengia said:
I got this problem when tried to root . and I tried many time to put it to download mode as hold power button and volume down , but it like a brick . Please help me out .
Please help me solve it
I do appreciate. Thank you
Click to expand...
Click to collapse
Hi .
Just install stock recovery again to get the tab in download mode again .
Stock recovery can be found in the stock firmware files , mostly in the ( AP , Code ) file .
Just try to extract file using " 7z '' . There you will find the stock recovery .
Put it in the AP or Code field and flash it using Odin . While the tab in the dead screen.
Regards

I used Heimdall ; it has a command to close the phone-to-pc screen (in linux terminal > heimdall "close-pc-to-phone-screen" ; heimdall -help to get exact command).

Is this support Odin new versions?
Anybody try this with Odin new version like 3.12.10 or 3.13.1

liengia said:
I got this problem when tried to root . and I tried many time to put it to download mode as hold power button and volume down , but it like a brick . Please help me out .
Please help me solve it
I do appreciate. Thank you
Click to expand...
Click to collapse
been there than that. same soft bricked my sch-p100 sprint same thing as the sch-i800

How to ROOT (SM-G935FD) with latest ota update

Edited
______________________________________________________
Tried with odin
cant find any IMG or any ZIP after selecting AP in browsing
_____________________________________________________
hello
mine is s7 edge model (SM-G935FD) indian variant
with latest security patch i,e (1 dec 2017)
is it the same procedure ?
kinda scared to try old might end up bricking up my phone
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

beinglazy said:
Edited
______________________________________________________
Tried with odin
cant find any IMG or any ZIP after selecting AP in browsing
_____________________________________________________
hello
mine is s7 edge model (SM-G935FD) indian variant
with latest security patch i,e (1 dec 2017)
is it the same procedure ?
kinda scared to try old might end up bricking up my phone View attachment 4386430
Click to expand...
Click to collapse
With AP you need to flash .tar or .tar.md5 files
Same procedure to root as long as your root method hasn't been noted as being outdated

turbolukex5 said:
With AP you need to flash .tar or .tar.md5 files
Same procedure to root as long as your root method hasn't been noted as being outdated
Click to expand...
Click to collapse
i tried this method didnt work
https://www.youtube.com/watchv=GRRX...5rshb2ieiej5kbhq4l5pw03c010c.1515693111002897
twrp = https://dl.twrp.me/hero2lte/twrp-3.2.1-1-hero2lte.img.tar.html
odin says "<OSM> All threads completed. (succeed 1 / failed 0)"
and after auto reboot in lock screen it asked me to reset the device but i didnt
but when it try to go in recovery by prssing vol up+ home + power
it goes to something saying "Installing update" and after few seconds says " no command" and it goes to stock recovery

beinglazy said:
i tried this method didnt work
https://www.youtube.com/watchv=GRRX...5rshb2ieiej5kbhq4l5pw03c010c.1515693111002897
twrp = https://dl.twrp.me/hero2lte/twrp-3.2.1-1-hero2lte.img.tar.html
odin says "<OSM> All threads completed. (succeed 1 / failed 0)"
and after auto reboot in lock screen it asked me to reset the device but i didnt
but when it try to go in recovery by prssing vol up+ home + power
it goes to something saying "Installing update" and after few seconds says " no command" and it goes to stock recovery
Click to expand...
Click to collapse
Follow tutorial in this thread instead
https://www.google.co.uk/amp/s/foru...-official-twrp-hero2lte-3-0-0-0-t3334084/amp/

I'm having the same problem, i've tried all methods I can find including the ones suggested on here but not one will work

Bholwell said:
I'm having the same problem, i've tried all methods I can find including the ones suggested on here but not one will work
Click to expand...
Click to collapse
hey this method worked for me
https://forum.xda-developers.com/showpost.php?p=75169863&postcount=2139

E: failed to mount /efs (invalid argument)

I have a Samsung Galaxy Core 2 (SM-G355M). I received this device from a person close to the family to try to solve a Loop problem in the Samsung logo. I tried to install 5 different Roms with the Odin3 3.10.6 program (Recommended for Android KitKat 4.4.2 systems), but I was unsuccessful after the device was restarted by Odin.
The device's recovery screen practically does not exist. There are no options to access when I enter recovery mode (by pressing the Volume up + Power + Home keys). I tried to install a custom recovery (TWRP and CWM), but I don't have access to them after Odin restarts the device.
As I mentioned before, the device's recovery screen practically does not exist because there are no options on the Hard Reset screen, but it displays a message when I press the volume button up as soon as the Android logo appears. https://ibb.co/FmBtv10 (Error Image). The error '' E: failed to mount / efs (invalid argument) '' appears.
I cannot access the device and retrieve it via ADB using commands because the USB debugging mode cannot be accessed (The phone does not start, so I cannot activate it). I am not aware of the history of this device, I just know that it is accepting any ROM or recovery feature through Odin and presents the error mentioned earlier on the Recovery screen.
I made another topic here in that same FORUM presenting my problem. I followed some steps taken by a FORUM member, but none of the procedures worked. There I explain a little better the procedures that I did and that did not work.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Samsung Galaxy Core 2 (SM-G355M) - Recovery mode does not work.​Helo! I'm new here at FORUM. In a desperate attempt I decided to create an account here and try to solve my problem with a Samsung device. It all started when I received a Samsung Galaxy Core 2 device to fix. It is stuck on the Samsung screen...
forum.xda-developers.com
I researched a little about this error found in recovery mode. Some solutions involved downloading the EFS file. IMG according to the device model and install via Odin. I found only for the model SM-G355H. During the process, Odin had an error loading the files, so I think it didn't work.
Problem summary:
1 - Device does not accept any of the official ROMS (After the cell phone is restarted by Odin it goes back to the Samsung screen).
2 - Cellphone showing error in recovery mode '' E: failed to mount / efs (invalid argument) ''
Some notes: I do not have access to the system using ABD because the debug mode cannot be activated (This ends up limiting things a lot). Options on the recovery screen do not appear and cannot be accessed (Only displays the error message right after pressing the volume button). All basic procedures were done (Download the most updated version of Samsung Drivers - 100% battery - Good quality cable - Odin 3.10.6 to install KitKat Android systems).
All possible solutions are welcome.

Note Fan Edition N935S - Stuck on looping Start Logo Screen

Hello All,
Will try to put all details to be able to get the right advise.
Recently was trying to root my N935s unlocked phone. The "Developer options → OEM unlocking" was enabled and USB bugging was enabled. However the process failed and threw me in an unrecoverable phone state.
Seeking help and advice to get back a working phone.
=========================================
Supporting information screenshots
Screenshots of the phone info "Pre" rooting attempt as is in stock condition.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Current State of Download Mode screens (after the rooting failure and boot loop has occurred)
==============================================================
Chronology of events (starting from an untampered stock phone)
1. Installed TWRP via flashing "AP" only using ODIN and was able to boot in TWRP recovery.
2. Made a complete backup of all partitions (including EFS) on external microSD card. Have it available - however somehow it is not helping.
3. Installed Magisk Apk 25.2 on the phone. Intention was to patch stock boot.img file and re-flash it to gain root by using Magisk,
4. Downloaded the below firmware files using Frija, by inputting the phone model N935S and CSC code as "SKC". Chose the latest file proposed by Frija in Auto mode.
5. Extracted boot.img from the stock AP file (from above screenshot) and transferred to phone for patching. Patched only the boot.img file.
6. After patching flashed the patched boot only (renamed and converted to TAR using 7zip) as "boot.tar" file in AP using ODIN - flashed it along with CP/BL/CSC files as from the above image.
a. This was the mistake point as the instructions were to transfer the whole AP file to the phone - get it patched inside the phone and then flash the whole AP file along with others. Somehow I totally missed it.​​7. Restarted the phone and the phone went in a bootloop or a stuck state of being only on the black Samsung Logo screen.
8. The recovery and download mode is available by using the button combinations.
====================
My attempts to restore
1. I first booted in TWRP recovery and restored from the stock backup I had taken - hoping that it would fix everything back to normal. The restoration was completed successfully - however there is no success to go beyond logo screen.
2. Went into download mode - using ODIN, flashed all the files from above screenshot (point no.4) - the flashing is completed successfully however there problem remains.
Not sure what can I do now to be able to get back a working phone.
Can someone please share a solution to a similar situation where the Magisk installation has rendered a phone bricked.
Thanks.

Was able to find excellent online phone restoration and recovery expert help and guidance - hence I was able to recover the phone.
It is now downgraded to Android 8, have lost the original serial number in he process - which is unrecoverable, however still got a working phone.
Thread closed.