First: Yes i've tried Odin flashing stock rom, recovery and all the other things!
So from the beginning:
My phone unlocked itself in my pocket and some weird things happend (i don't know what).
When I took it out it said that my sd-card could be safely removed
Then it said it was coruppted (I checked it on my laptop and it wasn't)
Then it started to reboot, and suddenly got stuck in bootloop!
When I pulled out the battery and put that in again. it booted black screen with text in the left uppercorner with some things about not being able to boot because there's no XXXX partition and some other things I cant remember.
So I thought, let's try and flash stock rom on it, and did that. Flash failed with error (size) or something.
Then I thought, let's reboot into recovery (How dumb that I haven't thought of that before) When I tried it it just bootlooped trying to get into recovery everytime.
Flashed new recovery, Still the same problem.
Flashed stock rom of another country, It worked but after odin finished and rebooted my phone it tries to boot itself into recovery (bootloop)
So nothing worked...
Download mode says this:
Current binary: Samsung official
system status: custom
Reactivation lock(kk): off
knox warranty void 0x1 (4)
qualcomm secureboot: ENABLE (CSB)
rp swrev: s1, t1, r1, a1, p1
udc start
I really don't know what to do, can you guys please help me?
Thanks in advance.
Donovan Nice
PMed you my Skype. Contact me if needed
Try to repartition your S5 with a pit file in Odin, maybe the filesystem is corrupt.
http://forum.xda-developers.com/showpost.php?p=52329647&postcount=2
Download the pit fole for a G900F, load it as PIT in Odin, tick "Re-Partition", and start.
v3rtex said:
Try to repartition your S5 with a pit file in Odin, maybe the filesystem is corrupt.
http://forum.xda-developers.com/showpost.php?p=52329647&postcount=2
Download the pit fole for a G900F, load it as PIT in Odin, tick "Re-Partition", and start.
Click to expand...
Click to collapse
Must it be pit only? I tried pit file together with stock ROM but that didn't work
I would try it step by step, so pit only first.
Is there any error message in odin?
Flashed pit file, succesfull. No errors. Phone still stuck in bootloop
Try to flash pit file with your pda stock firmware, check repartition, and uncheck Auto reboot.
Start, wait until it says pass, unplug your phone, remove your battery, wait a minute or so, put it back in, and try to boot into recovery with vol up/home/power.
Important is, try to wipe your cache and do a factory reset then.
v3rtex said:
Try to flash pit file with your pda stock firmware, check repartition, and uncheck Auto reboot.
Start, wait until it says pass, unplug your phone, remove your battery, wait a minute or so, put it back in, and try to boot into recovery with vol up/home/power.
Important is, try to wipe your cache and do a factory reset then.
Click to expand...
Click to collapse
This time I got a fail.. @hidden.img.ext4 "FAIL (size)"
F. Reset Time was checked but that shouldn't do anything right
donoboy97 said:
This time I got a fail.. @hidden.img.ext4 "FAIL (size)"
F. Reset Time was checked but that shouldn't do anything right
Click to expand...
Click to collapse
Have you tried the same with your recovery file?
If that fails again, the only idea i have at least is to check "nand erase all" checkbox in odin while flashing stock fw or recovery, try with and without pit and "re-partition", and without "autoreboot"
In some situations this fixed bootloops and steck bootloader issues.
At least you have nothing to loose...
v3rtex said:
Have you tried the same with your recovery file?
If that fails again, the only idea i have at least is to check "nand erase all" checkbox in odin while flashing stock fw or recovery, try with and without pit and "re-partition", and without "autoreboot"
In some situations this fixed bootloops and steck bootloader issues.
At least you have nothing to loose...
Click to expand...
Click to collapse
Recovery + pit works, pulled out the battery, waited a minute or so. Booted in recovery, get's the blue message.. and then bootloops again...
Gonna try nand erase, as you said I have nothing to lose. Wish me luck I guess?
long shot but check md5's on your downloads.. my first guess was the pit file but u said that didnt work
elliwigy said:
long shot but check md5's on your downloads.. my first guess was the pit file but u said that didnt work
Click to expand...
Click to collapse
md5's match!
v3rtex said:
Have you tried the same with your recovery file?
If that fails again, the only idea i have at least is to check "nand erase all" checkbox in odin while flashing stock fw or recovery, try with and without pit and "re-partition", and without "autoreboot"
In some situations this fixed bootloops and steck bootloader issues.
At least you have nothing to loose...
Click to expand...
Click to collapse
NAND-erase / Flashed stock rom: Did not work. NAND-erase /Flashed recovery: Did work, booted up in recovery... Bootloop. My phone is broken hard
donoboy97 said:
NAND-erase / Flashed stock rom: Did not work. NAND-erase /Flashed recovery: Did work, booted up in recovery... Bootloop. My phone is broken hard
Click to expand...
Click to collapse
when u say boots to recovery and bootloops, what do you mean exactly? like goes to recovery and immediately reboots?
can you screenshot exact error of odin when you use the pit and stock tar? also, i assume you have usb drivers and the right odin installed? try different usb ports/cables?
---------- Post added at 05:25 PM ---------- Previous post was at 05:25 PM ----------
if it boots at all then its not a hard brick so there is still hope
elliwigy said:
when u say boots to recovery and bootloops, what do you mean exactly? like goes to recovery and immediately reboots?
can you screenshot exact error of odin when you use the pit and stock tar? also, i assume you have usb drivers and the right odin installed? try different usb ports/cables?
---------- Post added at 05:25 PM ---------- Previous post was at 05:25 PM ----------
if it boots at all then its not a hard brick so there is still hope
Click to expand...
Click to collapse
it goes to recovery for 5 secs and then reboots, exact error is when it's flashing "hidden.img.ext4" and then it says "FAIL! (size)" Yes I have USB drivers and I'm using Odin v3.10 but I just checked on some threads, and they all say v3.09 soo.. could that be the problem?
I also tried different ports and cables but i'm mainly using the official cable!
donoboy97 said:
it goes to recovery for 5 secs and then reboots, exact error is when it's flashing "hidden.img.ext4" and then it says "FAIL! (size)" Yes I have USB drivers and I'm using Odin v3.10 but I just checked on some threads, and they all say v3.09 soo.. could that be the problem?
I also tried different ports and cables but i'm mainly using the official cable!
Click to expand...
Click to collapse
try odin 3.09 and report back.. i know its wonky sometimes with certain odin versions.. normally there is a hidden.img.ext4 in the tar file.. have you tried other odin tars? different or older odin tars? it almost seems like something wrong with the tar file or odin version
it's taking a while, please hold
elliwigy said:
try odin 3.09 and report back.. i know its wonky sometimes with certain odin versions.. normally there is a hidden.img.ext4 in the tar file.. have you tried other odin tars? different or older odin tars? it almost seems like something wrong with the tar file or odin version
Click to expand...
Click to collapse
Nope v3.09 did not work, tried redownloaded stock rom, stock rom from another country, and all of them with pit file..
did u dl tar from sammobile or elsewhere?
Related
I managed to be get rooted by following this.
For some reason, I am have been completely unable to do anything via Odin, but the above method ended up working for some reason (I had to execute the .jar from my C:\ drive though).
In a moment of idiocy, I chose the "Advanced Wipe" option under "Wipe" from the homescreen menu in TWRP and wiped my System directory. I think that this effectively wiped my OS, so I have nothing to boot into (it gets stuck at the "Samsung Galaxy S4" logo).
I have and can still access TWRP recovery, I can send ADB commands--but I do not believe that TWRP allows me to 'push' anything and I have not had any success with 'sideloading'. Some ADB commands leave me hanging at "< waiting for device >". I attempted to install custom ROMs by putting the install .zips onto my external SD and having TWRP install them, but I keep getting failures. I can access download mode, but Odin (v. 1.85, 3.04, 3.07) doesn't want to cooperate with me and all it says is a write failure. No PIT errors, I unchecked everything except " Auto Reboot", PDA mode, I tried all combinations of installing and re-installing Kies with drivers and rebooting my PC, plugging and unplugging my device into front and rear USB ports with different OEM cables, killing Kies/ADB processes via task manager and starting Odin at various points in the process (before and after I plug in my device or press up on the volume rocker to enter download mode). Please let me know if there's any more Odin hocus-pocus I haven't tried.
I was hoping that Kies->Tools->Firmware Upgrade and Initialization would work, but when I entered my S/N it said that initialization was not available for my device.
I'm at my wit's end, at this point; I would welcome someone telling me that I haven't completely bricked my device beyond all repair. I want to blame TWRP for not being able to install a ROM from a .zip. I have attached a recovery log from TWRP.
It seems you have problem in partition table. Did you flash pit file with the firmware in odin?
Sent from my Galaxy using xda premium
I had the same problem when I once had my S3 and I assume it'll be the same. In TWRP mount your storage and move a random rom on to your phone.
samersh72 said:
It seems you have problem in partition table. Did you flash pit file with the firmware in odin?
Sent from my Galaxy using xda premium
Click to expand...
Click to collapse
I think you are right about the partition problem, because that is what TWRP is telling me. I didn't flash a pit file in Odin with firmware. Am I supposed to?
Shivammcool said:
I had the same problem when I once had my S3 and I assume it'll be the same. In TWRP mount your storage and move a random rom on to your phone.
Click to expand...
Click to collapse
I was hoping that this would be the solution, but TWRP gives me a partition error. I will definitely re-attempt this once I can resolve that issue.
ncovey said:
I think you are right about the partition problem, because that is what TWRP is telling me. I didn't flash a pit file in Odin with firmware. Am I supposed to?
Click to expand...
Click to collapse
ya, flash the appropriate pit file WITH the firmware, check F.reset, auto reboot, and re-partition (they will be ticked by default).
see my sig for pit file if you dont have it
---------- Post added at 09:34 PM ---------- Previous post was at 09:03 PM ----------
wait.... you have the I9505 or the I545 (verizon)???
if I545 then here is the pit http://forum.xda-developers.com/showthread.php?t=2290859
Edit: i check pit files.... they are the same :good:
samersh72 said:
ya, flash the appropriate pit file WITH the firmware, check F.reset, auto reboot, and re-partition (they will be ticked by default).
see my sig for pit file if you dont have it
---------- Post added at 09:34 PM ---------- Previous post was at 09:03 PM ----------
wait.... you have the I9505 or the I545 (verizon)???
if I545 then here is the pit http://forum.xda-developers.com/showthread.php?t=2290859
Edit: i check pit files.... they are the same :good:
Click to expand...
Click to collapse
I am downloading one of the official firmwares. Is it possible to install it through my SD card if I can't get ODIN to flash it?
I tried installing the pit file, but I get the "SECURE CHECK FAIL : PIT" error on my S4's display.
I am worried that even though I managed to get rooted through Loki's exploit (I think that's what CASUAL or motochopper uses) the exploit that was pushed to my phone was wiped from it. I have the AT&T GT-I9505, so it definitely has a locked bootloader. I'm not giving up yet though.
Now it's definitely bricked.
Well, I couldn't do any of the methods described above because no manner of Odin'ing got me anywhere except "SECURE CHECK FAIL : " for recovery, boot, kernel, pit, etc.
so i attempted to do adb commands to see the extent of what i could do:
Code:
dd if=i9505-cwm-recovery-6.0.3.2-4.tar of=/dev/block/mmcblk0p21
from here
I should have known that you cannot install a .tar instead of a .img... :crying:
So now there is no recovery. And it only boots into download mode with a message at the top that says: "Could not do normal boot."
Unfortunately under "CURRENT BINARY:" it says "Custom" so I'm fairly certain that AT&T will not do a warranty replacement.
Hooray for popping my brick cherry!
EDIT: since the only way I was able to ADB before was in recovery mode... now that I've fubar'd my recovery... no ADB
EDIT 2: I've only had this phone for ~55 hours, so I think I can still have it exchanged for a restocking fee from AT&T. According to this and this
EDIT 3: I went to the AT&T store, and I was naive to think that they wouldn't turn it on. When the salesperson saw the "unauthorized software" message, she asked if I had attempted to "jail-break" my phone lol. She wanted to factory reset it from recovery mode, but obviously that didn't work. She said, "I am not sure we can accept this, and my inventory manager would kill me if we got back a device like this." She ended asking me to come in tomorrow to talk to the manager. I am very, very certain this will NOT result in me getting a new device.
Also, I realize that in this post whenever I've said "brick" I was not using the term correctly, as I can still turn it on. My mistake.
can you tell me the exact product number (i337 or i9505....) and what is the firmware that you are trying to install?
Hi,
I'm from Singapore and I believe I have the international s5 (SM-G900F), at least that's what it says in download mode. My phone was running CM13 nightly and till last night it was working fine. Last night when I charged it, I woke up this morning and my battery was incredibly overheated. I changed my battery and tried booting, but now it gets stuck in a bootloop. I flashed stock 5.0 lollipop from sammobile via odin, but it still is stuck. I can boot perfectly into download mode with the android logo. Here are the details:
PRODUCT NAME: SM-G900F
CURRENT BINARY: Custom
System Status: Custom
Reactivation Lock (KK): OFF
KNOX WARRANTY LOCK: 0x1 (04)
QUALCOMM SECUREBOOT: ENABLE(CSB)
RP SWERV: S1, T1, R1, A1, P1
SECURE DOWNLOAD: ENABLE
UDC START
I would really appreciate any help. Thanks!
Boot into recovery and factory reset, then try booting again
Sounds like the DATA partition got corrupted, or something installed to it did, flashing with ODIN doesn't wipe anything, so you'll still be bootlooped unless you wipe DATA / Factory Reset
When you go from cyanogenmod back to stock samsung firmware, a wipe data / factory reset is required in recovery or else the phone will be stuck in a boot loop or not boot up.
Hi, the problem is I cant access the recovery any more. Every time I hold power, volume up and the home button, it says recovery booting, warranty bit:kernel, kernel is not se android enforcing (the usual) but doesn't actually enter recovery.
imbtrthanu said:
Hi, the problem is I cant access the recovery any more. Every time I hold power, volume up and the home button, it says recovery booting, warranty bit:kernel, kernel is not se android enforcing (the usual) but doesn't actually enter recovery.
Click to expand...
Click to collapse
Flash TWRP 3.0.0.0 with ODIN and wipe from there, then flash stock again
https://dl.twrp.me/klte/twrp-3.0.0-0-klte-klte.img.tar.html
Hi I tried flashing twrp but that didn't work. It doesnt enter recovery, it still just restarts.
Is there any other way I can do a wipe? Through adb or something? Or should I select a specific option in Odin (3.09) ? Like bootloader update, etc or something?
imbtrthanu said:
Hi I tried flashing twrp but that didn't work. It doesnt enter recovery, it still just restarts.
Click to expand...
Click to collapse
Uncheck "Auto Reboot" in ODIN, flash TWRP again, when it completes, disconnect USB and pull the battery to power off the phone
Replace the battery, and boot immediately into recovery with Vol Up & Home & Power
Hi that's not working as well. Should I reflash stock and then flash twrp in the way you suggested?
Try, but something seems wrong because you should be able to flash TWRP with ODIN
Have you got the drivers installed and does ODIN give you a COM port at the top when the phone is in download mode?
You are putting the phone in download mode to flash TWRP right?
Vol Down & Home & Power
Yes I'm using Odin 3.09. I'm flashing via the AP slot. I only have F Reset time checked. My S5 is definitely in downloading mode. Looks similar to this:
http://cdn.androidblog.gs/wp-content/uploads/2014/12/Samsung-Galaxy-S5-Stuck-In-Download-Mode.png
Also, I think the drivers may be the issue here. Could you advise me on how to check and how to fix it? Thanks so much! Also, yes, the COM port lights up
imbtrthanu said:
Yes I'm using Odin 3.09. I'm flashing via the AP slot. I only have F Reset time checked. My S5 is definitely in downloading mode. Looks similar to this:
http://cdn.androidblog.gs/wp-content/uploads/2014/12/Samsung-Galaxy-S5-Stuck-In-Download-Mode.png
Also, I think the drivers may be the issue here. Could you advise me on how to check and how to fix it? Thanks so much! Also, yes, the COM port lights up
Click to expand...
Click to collapse
If the COM port lights up, the drivers are installed and working
Try ODIN 3.10.7, that's the latest version
Code:
https://mega.nz/#!vcIGmBTQ!Yr00OrGvUslQouU9E-zPf4SmpyVwL7mwIjeSG-0EAZg
Hi, that also didn't work. Any other advice?
Use a different PC / USB lead, everything you have tried should have worked fine on a G900F
Hi, I tried using a different PC and USB cable. Still nothing. Could it be because I flashed a different PIT file previously? There was a thread where someone suggested flashing a pit file, so
imbtrthanu said:
Hi, I tried using a different PC and USB cable. Still nothing. Could it be because I flashed a different PIT file previously? There was a thread where someone suggested flashing a pit file, so
Click to expand...
Click to collapse
Didn't you flash the G900F PIT?
Flash this in the PIT section of ODIN along with the stock ROM
http://forum.xda-developers.com/attachment.php?attachmentid=2721101&d=1399024091
Extract to .pit first
Hi, I tried flashing the stock rom with the PIT you gave me but it gave me the following response:
<ID:0/005> FAIL! (Size)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas what I should do now? Also, which stock rom should I be flashing? KK or Lollipop?
I don't know what you've done to your phone, and from your main post, it is definitely a G900F if that is what it says in download mode
Which PIT did you flash the first time? And did it flash successfully?
Any stock ROM should work, but might as well go for Lollipop, I know 100% this one works
Code:
https://mega.nz/#!fVhhzRBC!A79uC8Fgg1mGCZOaujQCzBxcUUN9z_ctVVkigD8ffVM
The only thing I can think of for now is to tell KIES3 to perform a firmware recovery
Code:
http://www.samsung.com/uk/support/usefulsoftware/KIES/
If you already have KIES installed, remove it and try ODIN again, people have reported it interferes with ODIN
If not, install KIES3, go to the firmware recovery setting and see if it can fix your phone
Other than that, it looks like it's going to need someone with knowledge of manual partitioning via adb shell or something, if the phone can enter a mode the PC can use that with
EDIT - You are using a native PC running Windows 7 or later right? Not a mac running Windows? Macs don't install the drivers properly and fail
Yup I'm running Windows 10. I'll try KIES and see if that works!
Which PIT did you originally flash? And did it actually flash?
Summary: My tablet is soft-brick now. Can only access to Download (ODIN) mode. I have tried 2,3 different firmwares, tried 3 versions of ODIN. But it doesn't work.
Here is the story:
I bought this tablet from bestbuy (USA)
I only wanted to root my tab A 7.0 SM-T280.
I enabled the OEN unlock from the developer mode.
Then I tried to flash the TWRP by the tutorial from this topic by @ashyx :
To install TWRP:
1. Flash with ODIN 3.10.7 in the AP slot.
Uncheck Auto reboot.
2. Load the respective file below into the AP slot and hit start.
3. After flashing when ODIN says PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding the other buttons.
You should now see TWRP recovery.
TWRP_3.0.2-1_SM-T280_261016
Click to expand...
Click to collapse
After flashing, on the download mode it showed: "SECURE CHECK FAIL: (RECOVERY)", then I reboot into recovery mode to access the TWRP but it said: "RECOVERY IS NOT SEANDROID FORCEFUL (although in ashyx topic said the SECURE FAIL is fine).
I still was able to reboot into the system this time.
And then I thought I should try another way. And then I came up with the TINKER ROM.
I tried to flash the Rom (v5) but somehow ODIN said FAIL.
I COULD NOT access the system since then.
Bu @zenful 's advices, I tried some different stock firmwares and different versions of ODIN just to get back to normal, but it never works.
Every time I flash, it always has the same problem:
- First try, ODIN fails at:
sboot.img
sboot2.img
complete (write) failed... (I don't remember though)
And in the download mode screen (from the phone) said:
SECURE CHECK FAIL (SBOOT)
SECURE CHECK FAIL (SBOOT2)
- Second try, ODIN fails at:
boot.img
system.img
Complete (write) fail...
And in the screen said:
SECURE CHECK FAIL (BOOT)
SECURE CHECK FAIL (RECOVERY)
I also tried emergency recovery mode in smart switch but it didn't solved the problem. One good thing (after I entered the tablet model and serial number) is that it showed "PHONE: QA4 CSC: PH3 (XAR)"
______________
I'm pretty sure that the problem doesn't come from fw nor from ODIN since I downloaded the fws from sammobile and updato and downloaded ODIN from xda (the latest version from samsungodin.com)
I'm seriously need a help right now. I just wanna have a rooted tablet so I can play game with my ps4 controller.
I have experienced with these flashing business. I rooted my galaxy s2, HTC desire c, HTC evo, etc. and so on, but have never done rooting in the last 1 year. I can attach some snapshots if you guys request
ngvhoang96 said:
Summary: My tablet is soft-brick now. Can only access to Download (ODIN) mode. I have tried 2,3 different firmwares, tried 3 versions of ODIN. But it doesn't work.
Here is the story:
I bought this tablet from bestbuy (USA)
I only wanted to root my tab A 7.0 SM-T280.
I enabled the OEN unlock from the developer mode.
Then I tried to flash the TWRP by the tutorial from this topic by @ashyx :
After flashing, on the download mode it showed: "SECURE CHECK FAIL: (RECOVERY)", then I reboot into recovery mode to access the TWRP but it said: "RECOVERY IS NOT SEANDROID FORCEFUL (although in ashyx topic said the SECURE FAIL is fine).
I still was able to reboot into the system this time.
And then I thought I should try another way. And then I came up with the TINKER ROM.
I tried to flash the Rom (v5) but somehow ODIN said FAIL.
I COULD NOT access the system since then.
Bu @zenful 's advices, I tried some different stock firmwares and different versions of ODIN just to get back to normal, but it never works.
Every time I flash, it always has the same problem:
- First try, ODIN fails at:
sboot.img
sboot2.img
complete (write) failed... (I don't remember though)
And in the download mode screen (from the phone) said:
SECURE CHECK FAIL (SBOOT)
SECURE CHECK FAIL (SBOOT2)
- Second try, ODIN fails at:
boot.img
system.img
Complete (write) fail...
And in the screen said:
SECURE CHECK FAIL (BOOT)
SECURE CHECK FAIL (RECOVERY)
I also tried emergency recovery mode in smart switch but it didn't solved the problem. One good thing (after I entered the tablet model and serial number) is that it showed "PHONE: QA4 CSC: PH3 (XAR)"
______________
I'm pretty sure that the problem doesn't come from fw nor from ODIN since I downloaded the fws from sammobile and updato and downloaded ODIN from xda (the latest version from samsungodin.com)
I'm seriously need a help right now. I just wanna have a rooted tablet so I can play game with my ps4 controller.
I have experienced with these flashing business. I rooted my galaxy s2, HTC desire c, HTC evo, etc. and so on, but have never done rooting in the last 1 year. I can attach some snapshots if you guys request
Click to expand...
Click to collapse
Try this: download your desire firmware via samfirm (BL+AP+CP+CSC when extracted) plus you need a pit file for your model with the same region as firmware and then flash (with 4 firmware files incl pit) via odin autoreboot+repartition+nand erase+f.reset time. At least you will get working stock tablet. It worked on my note 4 soft bricked.
Stixas said:
Try this: download your desire firmware via samfirm (BL+AP+CP+CSC when extracted) plus you need a pit file for your model with the same region as firmware and then flash (with 4 firmware files incl pit) via odin autoreboot+repartition+nand erase+f.reset time. At least you will get working stock tablet. It worked on my note 4 soft bricked.
Click to expand...
Click to collapse
Last time I tried download fw by using samfirm was last week and it didnt work. Can you test yours again?
And whre can I found the pit file? I dont think there is one in the internet right now.
Hello everyone,
I have a N9005 that only goes into download mode. It doesn't go into recovery mode. When I try to put it in recovery mode, just vibrates, the screen is black and continues to restart itself, vibrating.
If I try to turn it on normaly, Samsung Galaxy Note 3 N9005 logo comes on, stayes like this for 30, seconds, restarts, vibrates twice and keeps on doing this on and on
If I take it to download mode and try to flash a new rom, Odin tells me that there is no PIT partition. I even added the PIT file, but the same, no luck
When I try to flash a rom, on the download mode screen give me different red messages
UDC START-red color
MMC reading error
I even tryed to do emergency recovery with keys, but no luck as well
Any advice?
Regards!
Install Firmware from Sammobile...
albrecht1977 said:
Install Firmware from Sammobile...
Click to expand...
Click to collapse
I will let you know how it works/if it works
You cannot install roms via download mode .
Only official firmware.
If you have flashed official firmware via Odin then try flashing TWRP recovery via Odin .
Are you flashing the correct firmware as a TAR file ??
MMC reading error is probable damaged Nand .
Posted reported to mods for moving to correct Q&A section .
JJEgan said:
You cannot install roms via download mode .
Only official firmware.
If you have flashed official firmware via Odin then try flashing TWRP recovery via Odin .
Are you flashing the correct firmware as a TAR file ??
MMC reading error is probable damaged Nand .
Posted reported to mods for moving to correct Q&A section .
Click to expand...
Click to collapse
Yes, I am flashing the correct firmware from sammobile.
It is tar.md5
Now the phone shows me ODIN: flash read failure.
What can I do in this situation? If it is as you wrote, damaged Nand?
JJEgan said:
You cannot install roms via download mode .
Only official firmware.
If you have flashed official firmware via Odin then try flashing TWRP recovery via Odin .
Are you flashing the correct firmware as a TAR file ??
MMC reading error is probable damaged Nand .
Posted reported to mods for moving to correct Q&A section .
Click to expand...
Click to collapse
When I try to flaah the TWRP recovery, "there is no PIT partition"
Find 4 part firmware and flash correct PIT file /
Suggest a search on NAND fail / Nand Write fail on XDA .
JJEgan said:
Find 4 part firmware and flash correct PIT file /
Suggest a search on NAND fail / Nand Write fail on XDA .
Click to expand...
Click to collapse
Do you have any ideea where I can find the 4 part firmware?
Thanks
Sammobile /updato/samsung -updates. Alldot comms
Search this forum search google.
Have you tried using different USB cables and USB ports?
Odin will sometimes give the "PIT" error when you don't use an OEM cable.
audit13 said:
Have you tried using different USB cables and USB ports?
Odin will sometimes give the "PIT" error when you don't use an OEM cable.
Click to expand...
Click to collapse
Hey guys. Did anyone ever find the solution for this? I have the exact same problem like as in literally exactly. And I've tried the 4part repair firmware, with the pit, as wel as the combination firmware as well as the stock firmware and even tried cf auto root, boot images, twrp flashes.. Nothing! Just also keeps giving the pit error.
Reads as NAND fail , if you have followed all the advice .
My tablet does not start and shows this message: An error has occurred during device update. Please use the Emergency recovery Function in the Smart Switch PC Software
I tried downloading Smart Switch and opening the Device emergency recovery menu but nothing shows up in the device list.
Then I tried downloading Odin and a firmware, the device was recognized, I imported all the files (including the PIT FILE), checked Nand Erase and Repartition, started the flash but soon after it fails at Complete Write operation Failed.
How can I restore functionality of my tablet?
RobyGuizzo said:
My tablet does not start and shows this message: An error has occurred during device update. Please use the Emergency recovery Function in the Smart Switch PC Software
I tried downloading Smart Switch and opening the Device emergency recovery menu but nothing shows up in the device list.
Then I tried downloading Odin and a firmware, the device was recognized, I imported all the files (including the PIT FILE), checked Nand Erase and Repartition, started the flash but soon after it fails at Complete Write operation Failed.
How can I restore functionality of my tablet?
Click to expand...
Click to collapse
Try flashing with Odin but do not select nand erase or repartition. Also don't select the PIT file it will pull pit from csc if it needs it. Check settings and make sure only reboot and f.reset time are selected. It should go normally, if not may need to look at country change.
tek3195 said:
Try flashing with Odin but do not select nand erase or repartition. Also don't select the PIT file it will pull pit from csc if it needs it. Check settings and make sure only reboot and f.reset time are selected. It should go normally, if not may need to look at country change.
Click to expand...
Click to collapse
It doesn’t work and it gives this error:
RobyGuizzo said:
It doesn’t work and it gives this error:
Click to expand...
Click to collapse
Try flashing BL only. I'm confused by five sections that you're flashing. But just try them one at a time starting with BL then CSC then AP. Un-tick auto reboot for BL and CSC let it auto reboot after AP. You will have to manually reboot download mode after each.
Home_CSC keeps /data and CSC performs factory reset wiping /data. You don't flash both.
If that doesn't work look at this video
You may need to download a different firmware.
tek3195 said:
Try flashing BL only. I'm confused by five sections that you're flashing. But just try them one at a time starting with BL then CSC then AP. Un-tick auto reboot for BL and CSC let it auto reboot after AP. You will have to manually reboot download mode after each.
Home_CSC keeps /data and CSC performs factory reset wiping /data. You don't flash both.
If that doesn't work look at this video
You may need to download a different firmware.
Click to expand...
Click to collapse
I flashed BL, it failed at the end, then I tried to flash CSC and it gives Re Partition operation failed. I tried the others but says that there isn’t any PIT PARTITION. Now it doesn’t go into download mode and the screen flickers.
RobyGuizzo said:
I flashed BL, it failed at the end, then I tried to flash CSC and it gives Re Partition operation failed. I tried the others but says that there isn’t any PIT PARTITION. Now it doesn’t go into download mode and the screen flickers.
Click to expand...
Click to collapse
If not download mode then what does it go into ? What is flickering on screen ? Have you tried a different firmware ?
tek3195 said:
If not download mode then what does it go into ? What is flickering on screen ? Have you tried a different firmware ?
Click to expand...
Click to collapse
Where can I download the right firmware?
It goes into the emergency recovery screen.
RobyGuizzo said:
Where can I download the right firmware?
It goes into the emergency recovery screen.
Click to expand...
Click to collapse
go to easy-firmware and find the one you think to be most suited for your tablet and let me know and I will grab it for you on my account
RobyGuizzo said:
Where can I download the right firmware?
It goes into the emergency recovery screen.
Click to expand...
Click to collapse
I found a UK version on Sammobile. I think the problem is that you are flashing way too much. Try flashing just AP and BL. They are the ones that get messed up.
lewmur said:
I found a UK version on Sammobile. I think the problem is that you are flashing way too much. Try flashing just AP and BL. They are the ones that get messed up.
Click to expand...
Click to collapse
I had mentioned Easy-firmware so he could select from 40 different versions. Have to agree, flashing too much. I had the same error one time years ago and had to flash firmware from a different region to clear it then flashed correct region. I got that solution off youtube but didn't see it when I looked for this now. Know anything about that ?
tek3195 said:
I had mentioned Easy-firmware so he could select from 40 different versions. Have to agree, flashing too much. I had the same error one time years ago and had to flash firmware from a different region to clear it then flashed correct region. I got that solution off youtube but didn't see it when I looked for this now. Know anything about that ?
Click to expand...
Click to collapse
It's been a couple of years since I ugraded my last 2016 to a 2020, but I recall having problems when flashing CSC back then. And there was no USERDATA.
lewmur said:
It's been a couple of years since I ugraded my last 2016 to a 2020, but I recall having problems when flashing CSC back then. And there was no USERDATA.
Click to expand...
Click to collapse
Exactly, BL, AP, CP and CSC or HOME-CSC is it for this tablet as well. There is no USERDATA. @RobyGuizzo flashing anything in the userdata section of odin could be a bad thing.
tek3195 said:
Exactly, BL, AP, CP and CSC or HOME-CSC is it for this tablet as well. There is no USERDATA. @RobyGuizzo flashing anything in the userdata section of odin could be a bad thing.
Click to expand...
Click to collapse
To me the first rule of diognostics is to isolate the elements. We know AP and BL are essential. So which one of the others are the problem?
lewmur said:
To me the first rule of diognostics is to isolate the elements. We know AP and BL are essential. So which one of the others are the problem?
Click to expand...
Click to collapse
I don't know, but that error seems to lock it in some way. I know frp hijacker software is reported to allow flashing with that error. As did different region when I had it before. It's not just a corrupt partition but a lock of some kind.