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.
Related
Hello,
I've a Samsung Galaxy Tab 2 10.1 that I've had for more than a year.
Recently, in the last few weeks, it's developed a boot loop. In my many attempts to fix this, I've tried to put the samsung factory fresh ROM in it (P5113XACCLK7_XAC) that didn't work using ODIN 1.85, Heimdall, and never could get a good connection with Kies. I've tried to install different recovery utilities (Philz, CWM, recovery-clockwork, etc). When it boots into recovery mode, it shows the android robot and then an 'installing package' message briefly followed by a dead-android robot with a red warning sign with a 'command not found' error.
In the Android System Recovery <3e> mode, when I clear cache partition .. I get the same dead-robot error graphic with 'Error' as the message and the tablet goes back into boot-loop. When I select 'wipe data/factory reset' .. I get the same dead-robot error with the 'No Command' error message and it goes back into the Android System Recovery menu.
This tablet is behaving as if it has an unwritable file system..
Right now, I'd do just about anything to get this back to normal ROM.
Suggestions?
Thanks a lot
Tyler
tylerbud said:
Hello,
I've a Samsung Galaxy Tab 2 10.1 that I've had for more than a year.
Recently, in the last few weeks, it's developed a boot loop. In my many attempts to fix this, I've tried to put the samsung factory fresh ROM in it (P5113XACCLK7_XAC) that didn't work using ODIN 1.85, Heimdall, and never could get a good connection with Kies. I've tried to install different recovery utilities (Philz, CWM, recovery-clockwork, etc). When it boots into recovery mode, it shows the android robot and then an 'installing package' message briefly followed by a dead-android robot with a red warning sign with a 'command not found' error.
In the Android System Recovery <3e> mode, when I clear cache partition .. I get the same dead-robot error graphic with 'Error' as the message and the tablet goes back into boot-loop. When I select 'wipe data/factory reset' .. I get the same dead-robot error with the 'No Command' error message and it goes back into the Android System Recovery menu.
This tablet is behaving as if it has an unwritable file system..
Right now, I'd do just about anything to get this back to normal ROM.
Suggestions?
Thanks a lot
Tyler
Click to expand...
Click to collapse
I am not sure if this will work for you but Odin v1.85 never worked for my P5110. I had to use Odin v3.07.
cwyman said:
I am not sure if this will work for you but Odin v1.85 never worked for my P5110. I had to use Odin v3.07.
Click to expand...
Click to collapse
Alright.. I've got that version as well.. let me give it a whirl...
Output of ODIN 3.07
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P5113UECLK7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> recovery.img
<ID:0/005> system.img
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
any other suggestions?
Is your tab wifi or is it through a carrier?
Sent from my SCH-I545 using XDA Premium 4 mobile app
tylerbud said:
Hello,
I've a Samsung Galaxy Tab 2 10.1 that I've had for more than a year.
Recently, in the last few weeks, it's developed a boot loop. In my many attempts to fix this, I've tried to put the samsung factory fresh ROM in it (P5113XACCLK7_XAC) that didn't work using ODIN 1.85, Heimdall, and never could get a good connection with Kies. I've tried to install different recovery utilities (Philz, CWM, recovery-clockwork, etc). When it boots into recovery mode, it shows the android robot and then an 'installing package' message briefly followed by a dead-android robot with a red warning sign with a 'command not found' error.
In the Android System Recovery <3e> mode, when I clear cache partition .. I get the same dead-robot error graphic with 'Error' as the message and the tablet goes back into boot-loop. When I select 'wipe data/factory reset' .. I get the same dead-robot error with the 'No Command' error message and it goes back into the Android System Recovery menu.
This tablet is behaving as if it has an unwritable file system..
Right now, I'd do just about anything to get this back to normal ROM.
Suggestions?
Thanks a lot
Tyler
Click to expand...
Click to collapse
im having the same issue.. did you ever find a solution?
The French Tickl3r said:
im having the same issue.. did you ever find a solution?
Click to expand...
Click to collapse
Not as of yet
tylerbud said:
Hello,
I've a Samsung Galaxy Tab 2 10.1 that I've had for more than a year.
Recently, in the last few weeks, it's developed a boot loop. In my many attempts to fix this, I've tried to put the samsung factory fresh ROM in it (P5113XACCLK7_XAC) that didn't work using ODIN 1.85, Heimdall, and never could get a good connection with Kies. I've tried to install different recovery utilities (Philz, CWM, recovery-clockwork, etc). When it boots into recovery mode, it shows the android robot and then an 'installing package' message briefly followed by a dead-android robot with a red warning sign with a 'command not found' error.
In the Android System Recovery <3e> mode, when I clear cache partition .. I get the same dead-robot error graphic with 'Error' as the message and the tablet goes back into boot-loop. When I select 'wipe data/factory reset' .. I get the same dead-robot error with the 'No Command' error message and it goes back into the Android System Recovery menu.
This tablet is behaving as if it has an unwritable file system..
Right now, I'd do just about anything to get this back to normal ROM.
Suggestions?
Thanks a lot
Tyler
Click to expand...
Click to collapse
Tyler, I see that your last post was back in April, and although I'm fairly certain what your answer will be, I'd be remiss if I didn't ask anyway. Were you able to resolve this problem? If so, would you mind sharing the steps you took in your process? I have a Samsung Galaxy Tab 2 10.1 (P5113), and out of nowhere it performed a reboot and it has been looping ever since.
This has happened a couple times in the past two years I've owned the device and with my very limited knowledge regarding ROMs, flashing or rooting, I found my way to the System Recover Menu and was able to select the option to reset the tablet to factory settings. The system began the process of erasing the data and once it was complete I was able to reboot the tablet and everything worked just like new.
The process I just described has been successful for me twice before. So, yesterday when the tablet began it's reboot loop I attempted to perform the same steps as I had done in the past. This time, however, when I tried to enter the System Recovery Menu, "No Command" appeared beneath an unhealthy looking green android fellow. Whenever I attempt to select and run one of the options in the Recovery menu the command will fail and give an error.
I've been searching and reading threads all day trying to understand what is happening. Your OP has been the only one I've come across so far that resembles what I'm experiencing. Keeping my fingers crossed you may be able to provide some insight at least.
Thanks so much!
Joel
Boot loop
After I installed v4.2.2 shortly after release, I didn't like a few things (including some instability), so I went back to v4.1.1 using Odin, which at that time did the job. A few months later I reinstalled v4.2.2, and shortly after that, I noticed that Samsung pushed a significant sized patch to v4.2.2, and the instability stopped.
Sometime later, I tried again to go back to v4.1.1. Odin installed the prior version successfully, but then I entered a boot loop. I used Odin to reinstall v4.2.2, and all was well again.
No matter how many times I've tried to go back to v4.1.1, I now can't; I get the boot loop. However, I can always reinstall v4.2.2 with success. I suspect that the Samsung v4.2.2 patch changed something that now prevents going back to v4.1.1.
I don't know if this helps, but I thought I'd throw it out.
I have tried 7 different methods to fix from safe mode to factory resetting Google
Please help.
I have the exact same issue and have tried (safe mode. Uninstalling most of apps and factory reset play store.)
I can use my partners hot spot and never reboots.
WHY?
Please some1 who can help me with this exact problem please help.
Samsung galaxy tab2 10.1
tylerbud said:
Hello,
I've a Samsung Galaxy Tab 2 10.1 that I've had for more than a year.
Recently, in the last few weeks, it's developed a boot loop. In my many attempts to fix this, I've tried to put the samsung factory fresh ROM in it (P5113XACCLK7_XAC) that didn't work using ODIN 1.85, Heimdall, and never could get a good connection with Kies. I've tried to install different recovery utilities (Philz, CWM, recovery-clockwork, etc). When it boots into recovery mode, it shows the android robot and then an 'installing package' message briefly followed by a dead-android robot with a red warning sign with a 'command not found' error.
In the Android System Recovery <3e> mode, when I clear cache partition .. I get the same dead-robot error graphic with 'Error' as the message and the tablet goes back into boot-loop. When I select 'wipe data/factory reset' .. I get the same dead-robot error with the 'No Command' error message and it goes back into the Android System Recovery menu.
This tablet is behaving as if it has an unwritable file system..
Right now, I'd do just about anything to get this back to normal ROM.
Suggestions?
Thanks a lot
Tyler
Click to expand...
Click to collapse
Update: The only version of Odin that would work for my phone is 3.11.1 which finally got my phone booting again!
Yes, I know I am an idiot. I realize now that clicking on things that I dont know what they do is a very stupid thing. So anyways, long story short; I was playing around with my new Note 5 phone and rebooted into recovery mode and selected Apply update from adb to see if I could extract and modify an apk file. I did not know I could do an adb sideload with the phone on and I should not be in this screen (I am new to such a thing because I am used to direct access with root but there is no root for this particular phone). So I exit out of the screen with a power button combo to reset it but it kept booting over and over. So I booted into recovery mode and see "dm-verity verification failed..." so I did a wipe data/factory reset then a wipe cache partition and reset the phone but now instead of booting over and over it just boots once to show the android screen then shuts off. I tried using every possible version of Odin to flash the phone but most Odin versions say Failed and the others hang on NAND Write Start!! I have also downloaded the stock firmware from multiple sources because maybe the file I was trying to use was corrupted.
Could anyone help me unbrick my device? I just bought this phone and was absolutely in love with it until this problem. How could such a simple mistake as selecting the wrong option brick my phone?!
5.1.1 oj3 firmware
frp lock: off
RP SWREV: B:2 K:0 S:0
synterror said:
Update: The only version of Odin that would work for my phone is 3.11.1 which finally got my phone booting again!
Yes, I know I am an idiot. I realize now that clicking on things that I dont know what they do is a very stupid thing. So anyways, long story short; I was playing around with my new Note 5 phone and rebooted into recovery mode and selected Apply update from adb to see if I could extract and modify an apk file. I did not know I could do an adb sideload with the phone on and I should not be in this screen (I am new to such a thing because I am used to direct access with root but there is no root for this particular phone). So I exit out of the screen with a power button combo to reset it but it kept booting over and over. So I booted into recovery mode and see "dm-verity verification failed..." so I did a wipe data/factory reset then a wipe cache partition and reset the phone but now instead of booting over and over it just boots once to show the android screen then shuts off. I tried using every possible version of Odin to flash the phone but most Odin versions say Failed and the others hang on NAND Write Start!! I have also downloaded the stock firmware from multiple sources because maybe the file I was trying to use was corrupted.
Could anyone help me unbrick my device? I just bought this phone and was absolutely in love with it until this problem. How could such a simple mistake as selecting the wrong option brick my phone?!
5.1.1 oj3 firmware
frp lock: off
RP SWREV: B:2 K:0 S:0
Click to expand...
Click to collapse
Follow this guide and follow it to a T (link below).. skip down and start at number 6 since you can't get into the phone anyway.. Make sure you use the correct firmware for your phone.
http://forum.xda-developers.com/ver.../downgrade-to-lollipop-5-1-1-verizon-t3368250
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
About a month ago I updated my phone to Oreo and after that it’s been stuck in a boot loop. I tried factory resetting, wiping cache and flashing it with the stock rom, it was successful every time but no fix.
The phone also won’t charge but it shows a charging icon. Phone also turns off after no command and never turns back on.
I also received errors in red every 10 times when turning it on
BOTA: bota read partition fail
Secure check fail: invalid pit or no pit
The phone also won’t go in maintenance boot mode
And started in download mode with Samsung logo and recovery starting all at once
Can someone please give me something
IexorionI said:
About a month ago I updated my phone to Oreo and after that it’s been stuck in a boot loop. I tried factory resetting, wiping cache and flashing it with the stock rom, it was successful every time but no fix.
The phone also won’t charge but it shows a charging icon. Phone also turns off after no command and never turns back on.
I also received errors in red every 10 times when turning it on
BOTA: bota read partition fail
Secure check fail: invalid pit or no pit
The phone also won’t go in maintenance boot mode
And started in download mode with Samsung logo and recovery starting all at once
Can someone please give me something
Click to expand...
Click to collapse
First of all you must ensure you have the CORRECT firmware for your device. Check that you have.
Then flash with Odin but check "Nand Erase" in options before flash.
cooltt said:
First of all you must ensure you have the CORRECT firmware for your device. Check that you have.
Then flash with Odin but check "Nand Erase" in options before flash.
Click to expand...
Click to collapse
And what if this doesn’t work?
At the moment going into recovery mode has a lot of errors such as failed to mount /system as read-write or device is busy
IexorionI said:
And what if this doesn’t work?
At the moment going into recovery mode has a lot of errors such as failed to mount /system as read-write or device is busy
Click to expand...
Click to collapse
OK start with the easy option. Extract the PIT file from your firmware and check "re-partiton" in Odin before you start. There is a separate tab for the PIT file.
Invalid PIT means exactly that, its not the correct firmware for your device and missing PIT is also self explanatory. A genuine firmware will always have the correct PIT file for your device.
You can do the above and it'll either fix the phone or do nothing in which case you'll move to Nand Erase.
Hello,
I need help unbricking a SM-G390F but without losing the data.
My mother gave me the phone bc it was stuck in a boot loop and the local repair men said the data will get lost when fixing it.
She said that she had this issue before and just waited and after some time it booted normally. She said that this is getting more frequently and takes longer evrytime. And then came the point when the bootloop didn't end at all.
Here is everything that happend in a list:
Infinite Bootloop
"soft reset" (vol. down key + off key)
Trying to open Recovery, didn't work
But Download Mode does work
connecting via usb with Windows 10 PC (adb, drivers and smart switch installed)
adb doesnt recognize it "No devices found"
Trying to Flash lastest TWRP using Odin 3.14 (downloaded from https://odindownloader.com/), fails with Error "FRP Lock"
"soft reset" (vol. down key + off key)
System Update screen shows up
Weird Screen with text shows up #fail to open recovery_cause(No such file or directory)#, see https://pastebin.com/7tTP7Xh3
waiting overnight
Recovery is open at the next day
Wipe Cache using Recovery
System Update Screen
"soft reset" (vol. down key + off key)
booting into Download mode by pressing Vol. Down + off + home
Trying to Flash DBT stock firmware (sammobile.com) using Odin 3.14 HOME_CSC, BL, AP, CP Fails
"soft reset" (vol. down key + off key)
softbrick screen "An error has occured while updating the device software. Use the Emergency recovery function in the Smart Switch PC Software"
"soft reset" (vol. down key + off key)
Trying to Flash DBT stock firmware (sammobile.com) using Odin 3.14 HOME_CSC, BL, AP, CP Fails "Flash Lock" enabled in the Odin settings
"soft reset" (vol. down key + off key)
softbrick screen "An error has occured while updating the device software. Use the Emergency recovery function in the Smart Switch PC Software"
I don't need everything restored, the contacs are the most important thing. (And that the phone is usable again of course)
THANK YOU really much for your help!!!
hxr404
PS: Sorry for my bad English, I'm German
I forgot to say:
The phone was running completly on Stock Firmware, no modifications, not even installed a single APK
and it also didn't drop.
Maybe try flashing only BL and CP (bootloader and modem)?
Also try using this website as an alternative: https://samfw.com
Try using Heimdall instead of Odin since it may have more success with Heimdall rather than Odin.
Heimdall | Glass Echidna
There might be a fix, and there might NOT, reasons:
Phone was running completely on stock, which means it was not modified before, cause it is your Mom's. It is very likely to assume that bootloader is LOCKED, and by flashing TWRP, you made it worst, you triggered FRP.
If your stock recovery is unreachable, you could've tried to flash a stock recovery instead of TWRP.
Your phone will not boot unless you fix FRP thing by flashing the same firmware on the phone again, or any other guide you might follow.
It is very likely that you'll lose data, but you may be able to recover them if there was any cloud backup account syncing with the phone, or possibly any app that syncs contacts, Facebook is an example.
Before you jiggle with firmware stuff, you could've simply tried common ways, as such as wiping cache (step 2), trying to boot into safe mode (search and learn), flashing stock firmware without CSC, etc ...
Anyway, to fix your current condition, search for "S7 FRP Fix" on YouTube, and try the ones with firmware flashing, not boxes.
Sorry about your phone.
ok. Thanks for your help!!!
riojosepha said:
Try using Heimdall instead of Odin since it may have more success with Heimdall rather than Odin.
Click to expand...
Click to collapse
I get this error:
Code:
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -12
And
Mohamedkam000
yeah I was stupid trying to flash TWRP without checking FRP lock.....
The tutorial I found all require having a bootable phone or involves wiping all the data
Update:
I managed to restore some of the Data. So now I'm just trying to fix the phone, no matters if all Data get lost.
And I don't want to download any untrusted 3rd Party Software if possible.
Thanks for your help
hxr404 said:
Update:
I managed to restore some of the Data. So now I'm just trying to fix the phone, no matters if all Data get lost.
And I don't want to download any untrusted 3rd Party Software if possible.
Thanks for your help
Click to expand...
Click to collapse
Last week I fixed a FRP-Locked Note 5, It was just about three things:
Flash a combination file of the same binary level as your phone.
When you boot into the combination firmware, enable OEM-Unlock (bootloader unlock).
Reboot to Odin and flash a firmware of (possibly) the same level.
Once the phone booted, it did not ask about any account, was a normal setup and everything went good.
Since bootloader was unlocked on step 2, you may install TWRP and flash any custom ROM if you want, or you can continue with stock, whatever you choose may work.
There are many YouTube videos that can help you in such matters, always look for the most recent, and those which consists of flashing official firmware (Odin, combination, stock, ...).
I tried flashing stock and I tried a combination file consisting of
boot.img.lz4
system.img.lz4
sboot.bin.lz4
and also other combinations of the files
but everything fails with the error "Complete(Write) operation failed."
Code:
<ID:0/007> Added!!
<ID:0/007> Odin engine v(ID:3.1303)..
<ID:0/007> File analysis..
<ID:0/007> Total Binary size: 3898 M
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> NAND Write Start!!
<ID:0/007> SingleDownload.
<ID:0/007> boot.img
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I also tried different Versions of Odin:
the lastest one
v3.13
the "3B" patched Versions
Many Tutorials say that I need to enable USB Debugging to use Odin, but thats not true, right?
Is there anything I can do, or is it a Hardware Error?
and what Hardware Issue is it?
Update:
I tried flashing the PIT File extracted from AP
(and of course the other Stock FW Files)
It also failed with the same Error.
I also tried a NAND Erase, wich also failed with the same error.
Then I tried flashing the combination file again I got the error "Can't open the serial(COM) port."
I unplugged the devices and connected it again and then I tried to flash the combination file again. Now the COM port error is gone, but
the "Complete(Write) operation failed." Error is back
HELLO EVERYONE
I HAVE PROBLEM WITH MY PHONE S7 G930F I HAD CUSTOM ROM IN IT AND THEN I TRIED TO INSTALL STOCK ROM WHICH I DOWNLOAD IT FOR SAM I USED ODIN AND IT SAYS PASS BUT WHEN THE PHONE TRIED TO START IT STUCK ON ERASING AND THEN SHOWED ERROR AND I CANT EVEN GO TO RECOVERY MODE IT SAYYD RECOVERY CAUSE UNKNOWN FRP LOCK IS ALSO ON
@VINCE123412 I don't think you're gonna get help this way...
Make your own thread and stop using CAPS