Hey Team, anyone got Stock lollipop via odin?
Having the most difficult time ever flashing via recovery. Always gets "error executing updater binary". Anyways... I appreciate it (ahead of time).
thank you.
The updater error often happens if the rom is not made for a particular phone.
All stock firmware is at sammobile.com.
Use Samsung smart switch, emergency software recovery and initialization and select device initialization enter model name of your device and serial number it will download everything and reset the device latest what ever available.
Related
Attempted to unroot to attempt and solve a radio problem (unable to connect to any Sprint service following nightly update). Odin gives me an error every time I attempt to load the stock rom at the sboot.bin. Additionally, the phone (in ODIN mode) will say Unsupported Version. Please help!
Hey guys,
I've been searching the web, including this forum, trying to get help but after trying everything with no luck, I decided to ask for your help/guidance.
This is the problem:
I have a Samsung Galaxy Note 10.1 (2014 Edition) SM-P600 Wifi with P600XXUBMK1 Android 4.3 11.11.2013 1710482 stock. (PDA:MK1 / CSC: MK1 (TUR)) No root or anything else. It was working fine.
I decided to upgrade to Kitkat 4.4.2 and downloaded following from samsung-updates.
Below you will find all available download mirrors for P600KXUCOA2 firmware version for Galaxy Note 10.1 2014 (Wi-Fi) (SM-P600) from region KOO!
Firmware Version Info
(PDA: P600KXUCOA2 CSC: P600KOOCOA2 CHANGELIST: 3872460 BUILD DATE: 21.01.2015)
I installed Odin 3.09 (Also 1.85 and 3.07 just in case based on suggestions from other forum posts) and followed the instructions I found on a website, unfortunately, step by step instructions skipped the very important part: enabling USB debug before starting. That means I didn't enable USB debug.
I entered the download mode, started the Odin, added MD5 file to AP field and followed the instructions, but after a while, it showed failed message. I unplugged the tablet, tried to restart but it gave me the "firmware update encountered an issue. Please select recovery mode in Kies & try again." message. I tried to entered the recovery mode but it kept coming back to that message. I then tried the download mode, but it became Korean, and in Odin Mode product name changed from SM-P600 to SM-P600-KOR. I tried Odin again but kept failing. At this point Download Mode and the Error screen is all I can do.
Then, I tried Kies 2 and Kies 3 but they didn't recognize the tablet, so I tried Kies on Mac, it didn't recognize the tablet but I was able to enter the model and serial number to start the recovery, after a few hours, process failed and this message showed on the screen:
SW REV. CHECK FAIL. DEVICE:3, BINARY:2
I repeated the process on both Mac and WIndows PC several times but got the same error message. Emergency recovery doesn't even recognize the tablet, it asks for a code from another computer but I don't have any code.
I looked online and it was suggested that downloading Korean Android 4.3 firmware will solve the problem, so, I downloaded P600KXUANB1_P600KOOANB1_HOME.tar.md5 and tried to install using all 3 versions of Odin, but I kept getting FAIL and SW REV. CHECK FAIL. DEVICE:3, BINARY:2 message on the screen.
Then, I found another suggestion online saying the stock firmware will fix everything so I downloaded
"Below you will find all available download mirrors for P600XXUBMK1 firmware version for Galaxy Note 10.1 2014 (Wi-Fi) (SM-P600) from region TUR!
Firmware Version Info
(PDA: CSC: CHANGELIST: 1710482 BUILD DATE: 11.11.2013)"
from samsung-updates.
Again, I tried to install using all 3 versions of Odin, but I kept getting FAIL and SW REV. CHECK FAIL. DEVICE:3, BINARY:2 message on the screen.
At this point I am completely stuck.
1. Is my tablet bricked? If so, how bad is it? Soft-bricked with a chance of fixing or hard-bricked as in a paper weight?
2. What should I do next?
3. What does SW REV. CHECK FAIL. DEVICE:3, BINARY:2 mean?
4. Is there anyway to change SM-P600-KOR back to SM-P600?
5. I tried every combination I could find online to enter the recovery mode but download mode is the only mode I can enter. Is there a hard reset file or something or anything that I can do to enter the recovery mode?
I really appreciate your patience reading my post and I hope you can help me to fix this tablet.
Thanks.
Install the PIT file from the below link for the p600 through Odin, this should re-partion your device & bring it alive.
http://forum.xda-developers.com/galaxy-note-10-2014/help/pit-stock-pit-file-thread-t2989266
lsherif said:
Install the PIT file from the below link for the p600 through Odin, this should re-partion your device & bring it alive.
http://forum.xda-developers.com/galaxy-note-10-2014/help/pit-stock-pit-file-thread-t2989266
Click to expand...
Click to collapse
Thanks for the reply lsherif. I was able to bring back to Samsung Logo and recovery option but that's about it. Samsung logo flashes and the screen goes dark and nothing happens. I waited over 30 minutes to see if it restarts but screens is lit but dark. I did "wipe data/factory reset" and "wipe cache partition" but nothing happened except I lost the recovery partition again, so, I used the PIT file again and tried to install the original 4.4.2 file PDA: P600KXUCOA2 CSC: P600KOOCOA2 CHANGELIST: 3872460 BUILD DATE: 21.01.2015 since the recovery screen was showing the KOT49H. P600KXUCOA2. (I assume when I originally tried to update using P600KXUCOA2 it probably overwrote the recovery partition only.) This time I was able to go further in the Odin, but it failed again. I tried using Korean 4.3 and stock 4.3 P600XXUBMK1 however I keep getting the SW REV. CHECK FAIL. DEVICE:3, BINARY:2 message.
I tried Kies again but no avail. At the moment, Samsung Logo shows up when I restart and I am able to enter the recovery and download mode but that's it. Right now, tablet is plugged in and I am hoping it may start by itself but I am not hopeful.
So, what is my next step? What should I/can Ido? Waiting for reply.
Thanks.
Ok guys, I was able to download and install US 4.4.2 firmware and that fixed all the problems. I set up tablet, had about 3 additional OTA android updates after that and now everything is running very smoothly. It seems to charge slower but we'll see if that's the case after a while.
I'd like to thank lsherif for saving me from that uncertainty.
Thanks y'all!
Could you please post a link to the firmware you said fixed the problem for anyone with the same issue
Seymour2884 said:
Could you please post a link to the firmware you said fixed the problem for anyone with the same issue
Click to expand...
Click to collapse
Here is the thread I downloaded the firmware from:
http://forum.xda-developers.com/showthread.php?t=2719750
and this is the firmware I downloaded:
http://click.xda-developers.com/api...mega.co.nz/#!H4hT1QQb!nidMcJ...J-aURaD1WiaU0I
I have the same error!
And what's weird is everything that happened to you can be traced to what's happening to me. (Even the serial code is same) thank god I wasn't the only one with this issue.
I hope the method you told works else I'm literally screwed. Btw does this fulfill the original goal (update to 4.4.2?)
Hi guys,
I am coming with same issue but maybe even worse, I tried to flash TWRP on stock rom to be able to instal custom rom, after that I got same issue with Error message about try recoery with Kies.
I made same steps as you and I tried to flash PIT file but it does nothing, but my tablet is straght from Korea, even error mesage about kies is in Korean so I think it is maybe the issue.
One more quesiton, PIT file must be flashed together with AP or rom file? When I try just flash PIT I get error about re-partition operation failed and nothing more.
If anybody out there still remeber how you fixed your issue I would appreciate it very much. Thanks
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try agai
Last letter didn't have space in the title.
Ok, so I have a p605 rooted on cnf2. I wanted to unroot the tablet and bring it back to the original factory state, so I downloaded the latest firmware and tried to flash it through Odin.
I initially looked on sammobile and went with P605XXUDOE2, which is the latest Netherlands version. I wanted to install Netherlands because I know it usually receives the first updates for Europe (at least that's how it is on my note3).
But I think the tablet previously had DBT CSC (for Germany).
I wanted to download the firmware from sammobile but the speed was very low, it would have taken aproximatily 2 hours. So I copy-pasted the firmware code and looked for another download link on Google.
I eventually found this: http://samsung-firmware.org/Galaxy-Note-10.1-2014-LTE/7n66-P605XXUDOE2/
It was downloading much faster so I went it.
So I downloaded it, opened Odin 3.09, opened the firmware in the AP tab, connected the tablet in download mode and pressed start.
The flashing process finished but at the end it said FAILED with red color. I don't have a screenshot, it had an error message which I forgot what exactly was saying, it was something about ext4.
I googled the error message and it says I should've had a PIT file to include in the flashing process, and check re-partition.
I searched on Google how to get the PIT file and I found a guide where it shows you how to get it via terminal emulator, with some commands.
I tried to restart the tablet (thinking that Odin didn't actually flash anything because it said FAILED) to try and get the PIT file, but now the tablet doesn't boot and it's stuck at the screen that I attached.
1. My first question and most important one: is it dead or it can be brought back to life?
2. Why did this happen? Is it because I chose a firmware with a different CSC then the one I previously had?
3. If it can be fixed, how?
Edit: it seems that the device is booting in download mode and is recognized by the computer. Can I just retry starting all over?
Can anyone tell me what firmware should I be flashing this time? I don't remember all the details of the firmware it had before, but I posted a screenshot on this thread with the previous information:
http://forum.xda-developers.com/gal.../how-unroot-tablet-bring-to-original-t3165171
Anyone?
HELP -SM-T805 (807A for AT&T) failed ODIN CF-AutoRoot now won't boot, can't recovery
Hello Team,
I have 2 Devices, SM-T807A (AT&T USA) running Marshmallow.
I have downloaded the newest CF-AutoRoot and Odin V3.10.6 as instructed.
I attempted to flash the devices using CF-Autoroot.tar by clicking the "AP", I made Sure I only selected "Auto-Reboot" and "F Reset Time".
It loaded the image, started the process and gave me an error, "NAND Write Fail".
I tried the second device now, different cable, different CF auto-root download, same options, same result.
The device rebooted and now I am stuck at the screen asking me to connected to Kies to recover the device.
I connected to Kies and Smart Switch to do an "Emergency Recovery", and both devices cannot be seen to be restored. I used 4 different cables, all ports on a Mac and Windows device.
What I have attempted:
- To refresh a stock firmware, Tried the germany vodafone version and the swisscom, both failed
- Attempted to reflash CF auto root several times with many different ODIN versions, same result
- Attempted to flash TWRP to use a different recovery method, fails as well
What happens now?
- Device won't boot normally
- Recovery mode brings me to the Samsung error screen (Power+Home+Up)
- Download is still working but that's just about it
- Knox has not been tripped
- Device info shows that Official Samsung boot loader and image are both installed
This is not my first rooting, but I am completely out of ideas on what to do to fix this? Any thoughts?
Molokinhu said:
Hello Team,
I have 2 Devices, SM-T807A (AT&T USA) running Marshmallow.
I have downloaded the newest CF-AutoRoot and Odin V3.10.6 as instructed.
I attempted to flash the devices using CF-Autoroot.tar by clicking the "AP", I made Sure I only selected "Auto-Reboot" and "F Reset Time".
It loaded the image, started the process and gave me an error, "NAND Write Fail".
I tried the second device now, different cable, different CF auto-root download, same options, same result.
The device rebooted and now I am stuck at the screen asking me to connected to Kies to recover the device.
I connected to Kies and Smart Switch to do an "Emergency Recovery", and both devices cannot be seen to be restored. I used 4 different cables, all ports on a Mac and Windows device.
What I have attempted:
- To refresh a stock firmware, Tried the germany vodafone version and the swisscom, both failed
- Attempted to reflash CF auto root several times with many different ODIN versions, same result
- Attempted to flash TWRP to use a different recovery method, fails as well
What happens now?
- Device won't boot normally
- Recovery mode brings me to the Samsung error screen (Power+Home+Up)
- Download is still working but that's just about it
- Knox has not been tripped
- Device info shows that Official Samsung boot loader and image are both installed
This is not my first rooting, but I am completely out of ideas on what to do to fix this? Any thoughts?
Click to expand...
Click to collapse
Unfortunately the bootloader is locked on that device, so it can't be rooted with traditional tools.
It's simple enough to recover from this error.
The firmware is available on the forum.
I rooted my device, everything was fine until then but i wanted a custom rom so i tried to install twrp via odin, this didn´t work and the phone would not boot (recovery error validating footer) so i downloaded the stock firmware in the forum, when i tried to flash it odin got stuck at "setup connection" for like 30 minutes so i restarted the phone and instead of going to the download screen it displayed "an error has ocurred while updating the software, use the emergency recovery function in smart switch"
Smart switch didn't work so i came back to odin, now when i try to flash the stock firmware it tells me "sw rev check fail bootloader device* binary 1" i can´t tell what binary the phone has because the notch is hiding it but i can tell that the problem is that i cant downgrade the bootloader, where can i get a newer firmware? or can i just force the downgrade somehow?
now i´m stuck with a phone that won´t boot :crying:
Xplow said:
I rooted my device, ...
now i´m stuck with a phone that won´t boot :crying:
Click to expand...
Click to collapse
"ReiBoot for Android" (free demo ) helped me to enable download mode
odin could then flash stock firmware A105FNXXU3ATA1,
i had no lock to enable root or magisk "Error verifying vbmeta image"
but i can use the phone...
stoessel said:
"ReiBoot for Android" (free demo ) helped me to enable download mode
odin could then flash stock firmware A105FNXXU3ATA1,
i had no lock to enable root or magisk "Error verifying vbmeta image"
but i can use the phone...
Click to expand...
Click to collapse
not sure what reiboot android is but his problem has nothin to do with that.. he just needs to dl n flash latest rev firmware..
theres frija, firmware halabtech n many other sites u can dl firmware at.
i have the same problem!!!!!
when i connect to my laptop the phone connect and 1 sec letter disconnect
anyone can help?!?
:crying: