Can only enter download mode in odin flashing pda files has no effect however succeed every time, probably have corrupt files in every partition right now, have just repartitioned, what is the next step?
My GT-N8000 became stuck on the white text on black background boot screen spontaneously. I tried all variations of attempting to boot.
I was unable to enter recovery mode.(Holding power+up resulted in nothing)
I could enter Odin download mode.
I tried to flash a custom recovery to come back from nothing.
This flash succeeded in odin however nothing changed on the tablet.
I attempted to start from scratch and repartition which succeeded however after flashing a stock rom attempting to boot normally gives me a completely white screen.
Attempting to enter recovery gives me a white screen with ****ed up pixels.
I am still able to enter odin download
What do i do from here?
I can repartition again, what is the next step to come back from there?
isaac m said:
Can only enter download mode in odin flashing pda files has no effect however succeed every time, probably have corrupt files in every partition right now, have just repartitioned, what is the next step?
My GT-N8000 became stuck on the white text on black background boot screen spontaneously. I tried all variations of attempting to boot.
I was unable to enter recovery mode.(Holding power+up resulted in nothing)
I could enter Odin download mode.
I tried to flash a custom recovery to come back from nothing.
This flash succeeded in odin however nothing changed on the tablet.
I attempted to start from scratch and repartition which succeeded however after flashing a stock rom attempting to boot normally gives me a completely white screen.
Attempting to enter recovery gives me a white screen with ****ed up pixels.
I am still able to enter odin download
What do i do from here?
I can repartition again, what is the next step to come back from there?
Click to expand...
Click to collapse
how do you guys brick your tabs ???????????????????????????
as long as you can enter Odin mode so there is still hope.
According to my knowledge about other phones OS there are more than one file to revive the phone. Stock firmware usually have most of them. try in this direction to find the other OS files, I know there is a PIT file that restores something about partitions files system.
Maybe try another stock firmware.
I hope that would help to revive your tablet.
---------- Post added at 10:41 AM ---------- Previous post was at 09:50 AM ----------
try this post.
http://forum.xda-developers.com/showthread.php?t=2363703
Jtag brick repair
isaac m said:
Can only enter download mode in odin flashing pda files has no effect however succeed every time, probably have corrupt files in every partition right now, have just repartitioned, what is the next step?
My GT-N8000 became stuck on the white text on black background boot screen spontaneously. I tried all variations of attempting to boot.
I was unable to enter recovery mode.(Holding power+up resulted in nothing)
I could enter Odin download mode.
I tried to flash a custom recovery to come back from nothing.
This flash succeeded in odin however nothing changed on the tablet.
I attempted to start from scratch and repartition which succeeded however after flashing a stock rom attempting to boot normally gives me a completely white screen.
Attempting to enter recovery gives me a white screen with ****ed up pixels.
I am still able to enter odin download
What do i do from here?
I can repartition again, what is the next step to come back from there?
Click to expand...
Click to collapse
Here is a service that may be able to help you for $50, Check out some of there video's on YouTube.
http://forum.xda-developers.com/showthread.php?t=2599294
the post above has the solution that worked for me just follow those directions with the firmware for your device
Good luck
Hello guys,
I was trying to install twrp in this S8+ sm-g955u1 and it wasn't working. Every time I tried to flash the TWRP img.tar file it was says something like : "NAND Write fail" or something like that.
Unfortunately I went to the options tab and there was an option called NAND Erase..... So I checked it, and my phone went bootloop never to leave it. I tried several times got it to recovery mode, but the blue android saying Installing system update and after No command logo appears... After pressing volume Up+ Power for a while, I fount a lot of folders couldn't be mounted, or doesn't exists, etc.
I've tried to repartition in Odin, it was okay, but Every time I try to flash the rest of the files, (AP+BL+CSC+CP) I end up getting Complete(Write) Failed after Setup Connection..
Ps.: I've tried already different img versions, and different odin versions, and I even tried to
Did I just lost my hone with NAND Erase ?,Can't I recover the phone?
Flash stock there is no TWRP for u models we have locked bootloaders
My Galaxy A5 failed during a OTA update. I currently have an error stating that:
An error has occurred while updating the device software. Use the Emergency Recovery function in the Smart Switch PC software.
Smart Switch doesn't do anything.
I've tried to download the latest update from sammobile and load it via Odin 3.13 but that just sits on the system.img and doesn't complete. Left it overnight and didn't go on. Whats my best way to get the stock firmware loaded onto my device again?
Tyler
vtyler said:
My Galaxy A5 failed during a OTA update. I currently have an error stating that:
An error has occurred while updating the device software. Use the Emergency Recovery function in the Smart Switch PC software.
Smart Switch doesn't do anything.
I've tried to download the latest update from sammobile and load it via Odin 3.13 but that just sits on the system.img and doesn't complete. Left it overnight and didn't go on. Whats my best way to get the stock firmware loaded onto my device again?
Tyler
Click to expand...
Click to collapse
Did you have your device rooted before you tried the OTA update? If so, that is where you went wrong, typically, you can't flash OTA updates on rooted devices or devices that have a custom recovery(CWM or TWRP) because the system has been modified, when the update flashes, it checks the system partition to verify whether it has been modified, if it finds a modified system partition or if it finds TWRP instead of stock recovery, the update will fail.
This issue typically happens when flashing via Odin and the flashing process gets interrupted.
Boot the device into stock recovery then choose the "factory reset" option in recovery to factory reset the device, then use the "wipe cache partition" option in recovery to wipe cache.
Then try flashing the firmware again.
Sent from my LGL84VL using Tapatalk
No the device was not rooted prior to the OTA update.
I suspect somehow it got interrupted during the update.
To get into the Stock Recovery that is Volume Up + Home + Power at the same time right?
When I'm in my error screen it never does anything when I hold those buttons.
If I try the Power + Volume Down to reset and quickly switch I also can't get into the stock recovery just keeps going to the same error screen.
vtyler said:
No the device was not rooted prior to the OTA update.
I suspect somehow it got interrupted during the update.
To get into the Stock Recovery that is Volume Up + Home + Power at the same time right?
When I'm in my error screen it never does anything when I hold those buttons.
If I try the Power + Volume Down to reset and quickly switch I also can't get into the stock recovery just keeps going to the same error screen.
Click to expand...
Click to collapse
It should flash the firmware via Odin while in the error screen. If it isn't allowing the flash to be successful, try finding the PIT file for your specific model number, you might be able to find it in the firmware file, if it's there, Try extracting it from the firmware, then try flashing the firmware via Odin. Place the firmware file(s) in the appropriate slot in Odin then select the PIT tab in Odin, place the PIT file in the PIT slot, then go back to the main tab in Odin and select the re-partition and f.reset time options then click start and see if it flashes. If it flashes successfully but still bootloops, try booting into recovery then factory reset and wipe cache then reboot, sometimes this fixes the bootloop after flashing.
Sent from my LGL84VL using Tapatalk
Do I need to tar the CSC file up again without the PIT File in it? and then use that tar file for the CSC?
I removed the PIT file from the CSC file and then used the original CSC file as part of the firmware.
Everything still stalls during the system.img step. Gets about 5% of the way and then just sits there.
vtyler said:
Do I need to tar the CSC file up again without the PIT File in it? and then use that tar file for the CSC?
I removed the PIT file from the CSC file and then used the original CSC file as part of the firmware.
Everything still stalls during the system.img step. Gets about 5% of the way and then just sits there.
Click to expand...
Click to collapse
Let me think about this for a little bit and see if I can figure out what is going on. It is rare that this happens.
Sent from my LGL84VL using Tapatalk
Curious if you've had any further thoughts on this yet?
Do you think it's possible to just root the phone completely first instead of loading the Samsung Firmware?
Tyler
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 and does not start the system. I first tried to install the original ROM of the device with the correct binary through the Sammobile website using the Odin3 program. I tested about 4 different ROMS, but none of them worked.
After unsuccessfully trying to install the ROM I decided to restore the device using Hard Reset mode by pressing the correct key combination. And this is where I came across a very worrying problem. The correct options would be to show the Recovery options on the device's screen, but on this device they do not appear. The only thing that appears is the Android symbol with a red exclamation symbol. This screen appears for 3 seconds only ... after that the system restarts and returns to the Samsung screen again.
I've been trying to find a solution to this problem for a week and so far I haven't found anything.
I installed several features through Download Mode, but none of them were recognized by the system (All features were compatible with the model). Some of these features were Custom Recovery ... TWRP ... CWM .. Custom ROMS ... etc. I installed all of them through Odin3, but after the process was over and the phone restarted it didn't install because it jumped straight to the Samsung screen again.
Since no option on the Hard Reset screen was showing up, I decided to press a few keys at random to try to access an option. After a few attempts I finally managed to see some information. Now I come across written information: '' E: failed to mount / efs (invalid argument) '' https://ibb.co/FmBtv10 (Error Image).
And this is where it gets worse, because I don't know what that means. The only things I have left on the device is that message and nothing more. There are no more options to access.
I hope this device has a solution. I would be very grateful if someone could help me with this. Thanks for reading.
UserCroft said:
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 and does not start the system. I first tried to install the original ROM of the device with the correct binary through the Sammobile website using the Odin3 program. I tested about 4 different ROMS, but none of them worked.
After unsuccessfully trying to install the ROM I decided to restore the device using Hard Reset mode by pressing the correct key combination. And this is where I came across a very worrying problem. The correct options would be to show the Recovery options on the device's screen, but on this device they do not appear. The only thing that appears is the Android symbol with a red exclamation symbol. This screen appears for 3 seconds only ... after that the system restarts and returns to the Samsung screen again.
I've been trying to find a solution to this problem for a week and so far I haven't found anything.
I installed several features through Download Mode, but none of them were recognized by the system (All features were compatible with the model). Some of these features were Custom Recovery ... TWRP ... CWM .. Custom ROMS ... etc. I installed all of them through Odin3, but after the process was over and the phone restarted it didn't install because it jumped straight to the Samsung screen again.
Since no option on the Hard Reset screen was showing up, I decided to press a few keys at random to try to access an option. After a few attempts I finally managed to see some information. Now I come across written information: '' E: failed to mount / efs (invalid argument) '' https://ibb.co/FmBtv10 (Error Image).
And this is where it gets worse, because I don't know what that means. The only things I have left on the device is that message and nothing more. There are no more options to access.
I hope this device has a solution. I would be very grateful if someone could help me with this. Thanks for reading.
Click to expand...
Click to collapse
When flashing your firmware using odin, try ticking nand erase. Nand erase erases boot
kernel
recovery
system
data
cache
.android_secure
datadata
wimax
efs
preload.
This should solve your mounting problem
Tab E said:
When flashing your firmware using odin, try ticking nand erase. Nand erase erases boot
kernel
recovery
system
data
cache
.android_secure
datadata
wimax
efs
preload.
This should solve your mounting problem
Click to expand...
Click to collapse
Thank you for your attention in answering my question.
I checked the box that says '' Nand Erase All ''. After the Firmware was installed the phone restarted to the Samsung screen again .... so I think it didn't work. Correct would be to restart with the Android logo, correct?
I tried to mark the other options as well ... such as '' Phone Bootloader Update '' ... '' Phone EFS Clear '', but none of them worked. The biggest problem is the reboot, because the files are not being loaded by the system to be installed .... when Odin restarts the cell phone it goes straight to the Samsung screen and from there it keeps loading forever.
Am I using the wrong USB cable or is a PC feature missing? I use a Samsung cable and the Drivers are installed on Windows. Samsung driver version is 1.5.61.0.
I'll be waiting for another suggestion.
Tab E said:
When flashing your firmware using odin, try ticking nand erase
Click to expand...
Click to collapse
UserCroft said:
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 and does not start the system. I first tried to install the original ROM of the device with the correct binary through the Sammobile website using the Odin3 program. I tested about 4 different ROMS, but none of them worked.
After unsuccessfully trying to install the ROM I decided to restore the device using Hard Reset mode by pressing the correct key combination. And this is where I came across a very worrying problem. The correct options would be to show the Recovery options on the device's screen, but on this device they do not appear. The only thing that appears is the Android symbol with a red exclamation symbol. This screen appears for 3 seconds only ... after that the system restarts and returns to the Samsung screen again.
I've been trying to find a solution to this problem for a week and so far I haven't found anything.
I installed several features through Download Mode, but none of them were recognized by the system (All features were compatible with the model). Some of these features were Custom Recovery ... TWRP ... CWM .. Custom ROMS ... etc. I installed all of them through Odin3, but after the process was over and the phone restarted it didn't install because it jumped straight to the Samsung screen again.
Since no option on the Hard Reset screen was showing up, I decided to press a few keys at random to try to access an option. After a few attempts I finally managed to see some information. Now I come across written information: '' E: failed to mount / efs (invalid argument) '' https://ibb.co/FmBtv10 (Error Image).
And this is where it gets worse, because I don't know what that means. The only things I have left on the device is that message and nothing more. There are no more options to access.
I hope this device has a solution. I would be very grateful if someone could help me with this. Thanks for reading.
Click to expand...
Click to collapse
When flashing TWRP through odin, untick auto reboot, hold power Volume down and home button. You will see a black screen. Then immediately press power volume up home button. Then flash a custom rom. You ticked the bootloader update option, but Samsung core 2 doesn't have bootloader. Hope the nand erase fixed the mounting
Tab E said:
When flashing TWRP through odin, untick auto reboot, hold power Volume down and home button. You will see a black screen. Then immediately press power volume up home button. Then flash a custom rom. You ticked the bootloader update option, but Samsung core 2 doesn't have bootloader. Hope the nand erase fixed the mounting
Click to expand...
Click to collapse
Before I do this procedure I need to ask a few questions. Do I need any requirements to install TWRP? This phone has no ROOT and no other modifications.
Does the ROM that I am going to install need to be compatible with TWRP? I am trying to install an official Samsung ROM without modification.
I will try to use the version for the SM-G355H. The TWRP for this model is hard to find.
Just remembering that my recovery screen is dead, so I don't have access to anything in the device's Recovery options. I look forward to new answers so I can continue.
1. You need no requirements to flash twrp
2. Every rom for your device is compatible.
Just a few questions,
After nand erase and firmware flash, do you still have a corrupted recovery?
Does the firmware that you are flashing, and the model number in Odin mode match?
Tab E said:
When flashing TWRP through odin, untick auto reboot, hold power Volume down and home button. You will see a black screen. Then immediately press power volume up home button. Then flash a custom rom. You ticked the bootloader update option, but Samsung core 2 doesn't have bootloader. Hope the nand erase fixed the mounting
Click to expand...
Click to collapse
I followed those instructions you sent me. I used a TWRP file for the model SM-G355H (I hope it is compatible with this model). The file is called '' recovery.tar.md5 ''. I opened Odin Version 3.0.9 and deactivated the '' Auto Reboot '' option. I passed the TWRP file to the cell phone and did the commands you sent me. The phone restarts with a brief Android screen for 3 seconds and disappears. There are no commands to do. It goes to the Samsung screen again. So I think it didn't work for me.
I hit the keys the same way you told me to (I hope Lol)
You told me to install the custom rom. Is this done after installing TWRP and the phone restarts?
Tab E said:
1. You need no requirements to flash twrp
2. Every rom for your device is compatible.
Just a few questions,
After nand erase and firmware flash, do you still have a corrupted recovery?
Does the firmware that you are flashing, and the model number in Odin mode match?
Click to expand...
Click to collapse
Answering your first question: If you are referring to the error '' E: failed to mount / efs (invalid argument) '' yes. It appears after I press the volume button up or down as soon as the android screen appears (The recovery screen that appears only the symbol of the android lying with a red sign). I wish I could access this screen for a longer time, but it disappears quickly.
Answering your second question: I am using an official 4-part ROM. It corresponds to my country. SM-G355M G355MUBU0AQB1 ZTO G355MZTO0AQB1 OPEN BR ANDROID 4.4.2 FULL FLASH. The version of my Odin is 3.0.9. I heard that this version is the best for installing Android 4.4.2 KitKat systems, so I decided to use it.
Just one more question. Does the Cell Phone have to be 100% charged for this to work? I think I was at 60% when I tried the procedure.
Sorry for asking so many questions. I have little knowledge of the subject. If you can send me a tutorial on the internet in video or written so I can save your time feel free to send me. Thanks!
Sorry, I was busy for some days,
No, you don't need to fully charge your phone
Just found this on youtube, you can check it out
Your phone is g355hm, so I don't know if this recovery will work. If it works, then you can easily solve the problem with your mount points. I'll help you with that after you get twrp
TWRP Recovery 2.8.4.0 & 2.8.5.0 for Samsung Galaxy Core 2 SM-G355H/G355HN
Visit galaxynroms.blogspot.com. Disclaimer: I/XDA/is not responsible for any kind of damage to your device, or in case it explodes, etc. Please use it at your own risk! Whatever you do with your phone it's your own choice! Requirement: 1...
forum.xda-developers.com
Use the Odin tutorial
Tab E said:
Sorry, I was busy for some days,
No, you don't need to fully charge your phone
Just found this on youtube, you can check it out
Your phone is g355hm, so I don't know if this recovery will work. If it works, then you can easily solve the problem with your mount points. I'll help you with that after you get twrp
TWRP Recovery 2.8.4.0 & 2.8.5.0 for Samsung Galaxy Core 2 SM-G355H/G355HN
Visit galaxynroms.blogspot.com. Disclaimer: I/XDA/is not responsible for any kind of damage to your device, or in case it explodes, etc. Please use it at your own risk! Whatever you do with your phone it's your own choice! Requirement: 1...
forum.xda-developers.com
Use the Odin tutorial
Click to expand...
Click to collapse
Thank you for taking the time out of your day to help me. I figured you were busy these days, so I left a message for you to see and remember POST.
I had seen this video on Youtube before, but I saw it again and followed all the steps. I used the two versions of the TWRP for the model SM-G355HN and G355H through the link you sent me, but neither of them is being recognized by the device. I tested other different CWM versions like:
philz_touch_5.15.0-n7100.tar
philz_touch_6.09.6-n8020.tar
philz_touch_6.57.9-ghost
All of them were not recognized and loaded in recovery mode.
I was confused by a specific part of the video. After the STOCK ROM was sent by Odin, the phone restarts. (At that moment there was a cut in the video). I couldn't see what he did, but I decided it was just to turn the device off and on again in download mode to pass the CWM/TWRP.
Is it possible that the system is blocking the files that I am sending? Maybe an FRP lock? I don't know much about the android system, but I suspect that the device's BIOS does not accept any features via download mode. FRP Lock is for Android from 5.0, correct? My Android is 4.4.2 KitKat.
I have already used the main versions of Odin, including the modified versions. I used about 5 different STOCK ROMS and about 10 different versions of TWRP and CWM. Nothing works! I'm getting upset. : (
I'm running out of options. If you have any more suggestions feel free to answer me. Don't be in a hurry ... answer when you can.
Thanks!
One this is certain, FRP can't make any difference. In the video, after the flashing is complete, he immediately turned the phone back in download mode and flashed the custom recovery. As no reocvey works, extract your recovery.img from your firmware and use this one click TWRP porting tool. You will have mount pint issues, but just follow the above video if you are able to successfully able to boot the twrp you ported with this tool https://firmwarecare.com/spreadtrum-auto-twrp-recovery-porter-v1-2
Tab E said:
One this is certain, FRP can't make any difference. In the video, after the flashing is complete, he immediately turned the phone back in download mode and flashed the custom recovery. As no reocvey works, extract your recovery.img from your firmware and use this one click TWRP porting tool. You will have mount pint issues, but just follow the above video if you are able to successfully able to boot the twrp you ported with this tool https://firmwarecare.com/spreadtrum-auto-twrp-recovery-porter-v1-2
Click to expand...
Click to collapse
Thank you for sending the tool. This version does not support Android 4 KitKat. I downloaded version 1.0 (Version 1.0 supports Android 4). I used 3 Recovery.img files from 3 different STOCK ROMS and came across this error on Odin:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The versions used were 3.06 - 3.09 - 3.10.6 - 3.11.1 - 3.14.1 3B Patched. I converted Recovery to .tar and .md5, but none of them work. I even tried to use Recovery Original to ensure that the problem was not the conversion, but the original file did not give errors by Odin, so I ruled out the possibility of being the conversion.
I would like to mention something from the video above: His screen in Download mode describes the ROM as Custom. After he passes the FIRMWARE through Odin the information changes to Samsung Official. My information is not Custom ... it is Samsung Official, so I wouldn't know if the transfer was successful or not.
Would it work if I switched to Custom and then went back to Official again? (I'm just speculating. I don't know if that is valid or not.)
Could you answer some questions? There are doubts about the device and the recovery mode.
1 - Why doesn't my recovery screen give me options to access it ? (Just the error message)
2 - Why when I pass any FIRMWARE through Odin and the phone restarts, no process is done for the ROM to be installed normally?
3 - The recovery screen appears for 5 seconds only ... after that the phone restarts again. This is normal ?
4 - Is there any possibility that the system is blocking by default any modification made by Odin by installing FIRMARES or customized recoveries? (This would explain why the phone does not install anything.)
5 - Is it possible to correct the error '' E: failed to mount / efs (invalid argument) '' by passing the original Efs..tar.md5 file?
6 - What is the best version of Odin to install Android 4.4.2 KitKat systems?
Grateful!
Tab E said:
One this is certain, FRP can't make any difference. In the video, after the flashing is complete, he immediately turned the phone back in download mode and flashed the custom recovery
Click to expand...
Click to collapse
UserCroft said:
Thank you for sending the tool. This version does not support Android 4 KitKat. I downloaded version 1.0 (Version 1.0 supports Android 4). I used 3 Recovery.img files from 3 different STOCK ROMS and came across this error on Odin:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The versions used were 3.06 - 3.09 - 3.10.6 - 3.11.1 - 3.14.1 3B Patched. I converted Recovery to .tar and .md5, but none of them work. I even tried to use Recovery Original to ensure that the problem was not the conversion, but the original file did not give errors by Odin, so I ruled out the possibility of being the conversion.
I would like to mention something from the video above: His screen in Download mode describes the ROM as Custom. After he passes the FIRMWARE through Odin the information changes to Samsung Official. My information is not Custom ... it is Samsung Official, so I wouldn't know if the transfer was successful or not.
Would it work if I switched to Custom and then went back to Official again? (I'm just speculating. I don't know if that is valid or not.)
Could you answer some questions? There are doubts about the device and the recovery mode.
1 - Why doesn't my recovery screen give me options to access it ? (Just the error message)
2 - Why when I pass any FIRMWARE through Odin and the phone restarts, no process is done for the ROM to be installed normally?
3 - The recovery screen appears for 5 seconds only ... after that the phone restarts again. This is normal ?
4 - Is there any possibility that the system is blocking by default any modification made by Odin by installing FIRMARES or customized recoveries? (This would explain why the phone does not install anything.)
5 - Is it possible to correct the error '' E: failed to mount / efs (invalid argument) '' by passing the original Efs..tar.md5 file?
6 - What is the best version of Odin to install Android 4.4.2 KitKat systems?
Grateful!
Click to expand...
Click to collapse
Try switching to custom and then official.
1) actually, if there is something wrong with just the /efs partition, it shouldn't affect the recovery
2) looks like many partitions are corrupted
4) core 2 has no bootloader or any such protection to stop flashing
5) the efs file is included in the firmware, so it is flashed with the firmware.
Conclusion - looks like multiple partions are corrupted. Try to verify this by flashing any custom recovery or rom and check the status in Odin. Even after flashing a custom recovery, the status is stock, then there are definitely many corrupted partitions. If it's so, fixing it will be very tough
Tab E said:
Try switching to custom and then official.
1) actually, if there is something wrong with just the /efs partition, it shouldn't affect the recovery
2) looks like many partitions are corrupted
4) core 2 has no bootloader or any such protection to stop flashing
5) the efs file is included in the firmware, so it is flashed with the firmware.
Conclusion - looks like multiple partions are corrupted. Try to verify this by flashing any custom recovery or rom and check the status in Odin. Even after flashing a custom recovery, the status is stock, then there are definitely many corrupted partitions. If it's so, fixing it will be very tough
Click to expand...
Click to collapse
I will do as much as I can. Tomorrow I will contact you to say if something worked. If nothing goes well I will need to take the device for specialized maintenance. Thanks for the help, buddy. If I ever manage to solve this problem I will make a guide in FORUM showing how to fix it and give you the credits.
Tab E said:
Try switching to custom and then official.
1) actually, if there is something wrong with just the /efs partition, it shouldn't affect the recovery
2) looks like many partitions are corrupted
4) core 2 has no bootloader or any such protection to stop flashing
5) the efs file is included in the firmware, so it is flashed with the firmware.
Conclusion - looks like multiple partions are corrupted. Try to verify this by flashing any custom recovery or rom and check the status in Odin. Even after flashing a custom recovery, the status is stock, then there are definitely many corrupted partitions. If it's so, fixing it will be very tough
Click to expand...
Click to collapse
Unfortunately nothing went right, friend. I tested everything I could. I have no other options left. All the procedures were done, I followed all your suggestions, but nothing works. There is no doubt that all partitions are corrupted. You told me it would be very difficult to fix it, so I'm not even going to try. I did as much as I could with this device. I am not qualified for this, I am just a lay person who is trying to solve a complex problem.
If you think I can do this from home with some tool, tell me. If it’s too complex I’ll take it to a maintenance specialist.
Just one more question: I don't know which ROM has been installed on this device previously and which Binary of FIRMWARE. Will the Device only accept a FIRMWARE that has exactly the '' Same '' binary? For example ... I have a ROM with the PDA binary G355MUBS0AQC2 .... Will the System only accept exactly this value so that it can be installed?
I forgot to ask this at the beginning.
Sorry, I have no knowledge of using tools or fixing a device by repairing the hardware. Using the wrong binary doesn't make a difference on these older devices.
Tab E said:
Sorry, I have no knowledge of using tools or fixing a device by repairing the hardware. Using the wrong binary doesn't make a difference on these older devices.
Click to expand...
Click to collapse
I'm greatfull for your help.
Bye, buddy.