downloaded twrp 3, was running 5.1.1 on my phone and rooted it. tried to flash a rom and got stuck in a bootloop, now I cant boot into twrp, or anything for that matter. All i can do is hold volume down and power and home and try to ODIN a new bootloader or such and it just fails. what do i do? but when I try to boot into TWRP it goes into a blueish screen with a White exclamation mark saying "An error has occurred while updating the device software. Use the Emergency recovery function in the smart switch PC software. I tried to do that but it didnt even recognize the device. At this point i dont care about the data, I just need a working device
Okay, so I attempted to unroot and flash the stock 5.0.2 software and I got a error on the download screen. It says SW REV. CHECK FAIL. DEVICE: 3. BINARY: 1.
If you have no knox install MM official then flash this kernel tar file (AP) https://drive.google.com/folderview?id=0B40ItdHKfkyQcTA5bnRPWDg0X28&usp=drive_web#list it will boot to mm 5min :good:
Btw you cann downgrade from 5.1.1 to 5.0.1 you just go up not down
zach616 said:
downloaded twrp 3, was running 5.1.1 on my phone and rooted it. tried to flash a rom and got stuck in a bootloop, now I cant boot into twrp, or anything for that matter. All i can do is hold volume down and power and home and try to ODIN a new bootloader or such and it just fails. what do i do? but when I try to boot into TWRP it goes into a blueish screen with a White exclamation mark saying "An error has occurred while updating the device software. Use the Emergency recovery function in the smart switch PC software. I tried to do that but it didnt even recognize the device. At this point i dont care about the data, I just need a working device
Click to expand...
Click to collapse
Happened to me a lot of times in the past few days trying to get MM, for some weird reason flashing Unikernel always works for me (takes me to recovery screen after, then i select 'reboot now'), and all my data, apps etc are still there
emcardle660 said:
Happened to me a lot of times in the past few days trying to get MM, for some weird reason flashing Unikernel always works for me (takes me to recovery screen after, then i select 'reboot now'), and all my data, apps etc are still there
Click to expand...
Click to collapse
will try and update. thank you. didnt work.
Okay guys so now I need a ROM to flash using ODIN. I tried to download from sammobile but the speeds are too damn slow. What I tried to flash was this file " G920TUVU1AOCG_G920TTMB1AOCG_G920TUVU1AOCG_HOME.tar.md5 " and i got the error 3 to 1.
Download Samfirm from here, XDA itself.
Run samfirm, enter model as G920F and your region code.
It will download from Samsung servers, so high speed.
Now flash using Odin the downloaded file by putting the phone in download mode, (vol down+home+power on).
How did it happen?
Did you try to flash the VOD 6.0.1 and got stuck towards the end at hidden.IMG failing the process?
If yes, then its a two minute job. Just open the 6.0.1 tar archive and look for hidden.IMG extract it anywhere and rename it from "hidden.img" to "hidden.img.tar".
Note flash this hidden.img.tar as AP in download mode, your phone should boot.
Everytime I try to unroot my phone with Odin it says the process failed and Auth failed, someone please help..
Download stock firmware from the primary root guide. Use Odin and select all three the ap and the two below it. This will recover you to stock. Without root. But first do a titanium backup or a nandroid backup of all your apps and contact.
Sent from my SM-G930V using XDA-Developers mobile app
I tried but it still says failed... in Odin I put in all BL AP CP and CSC files, in the left text box it says FAIL! (Auth). I've tried this multiple times but it failed.. am I doing something wrong? Will I not be able to unroot my phone.. it's a SM-930T
Antaru123 said:
I tried but it still says failed... in Odin I put in all BL AP CP and CSC files, in the left text box it says FAIL! (Auth). I've tried this multiple times but it failed.. am I doing something wrong? Will I not be able to unroot my phone.. it's a SM-930T
Click to expand...
Click to collapse
Have you tried going into super su and hitting on permanent unroot also heres a guide goto the bottom and there should be a part that says full unroot. Link: http://forum.xda-developers.com/ver...-to-notes-root-install-xposed-unroot-t3411039 goto page 1 wont goto page 1 even after editing it oh well. Lol
I've done that too and it says FAILED then the SuperSU app disappears from my phone
Antaru123 said:
I've done that too and it says FAILED then the SuperSU app disappears from my phone
Click to expand...
Click to collapse
Try rerooting the phone through ODIN also make sure you are using the lastest ODIN if you need to boot into recovery and do factory reset and cleat cache but BACK YOU STUFF UP!!! Also what is you model number ex: SM-G935x
Edit also make sure u have secure start up off and have you lockscreen password off just in case
Well uh. now my phone is stuck in recovery mode and won't even start up normally.. and it's the SM-G930T
Antaru123 said:
Well uh. now my phone is stuck in recovery mode and won't even start up normally.. and it's the SM-G930T
Click to expand...
Click to collapse
Hate to say this again but just to make sure did you try doing factory reset and clear cache. Also if its still stuck then use odin to flash the s7 engineer root file then go into recovery mode and then clear cache and factory reset it should work fixed my boot loop when my phone was doing it.
I did all this Odin still fails, I've tried all three downloads from XDA for SM-930T which is my phone
Antaru123 said:
I did all this Odin still fails, I've tried all three downloads from XDA for SM-930T which is my phone
Click to expand...
Click to collapse
Well if worst come to it goto best buy and goto the samsung depart ment and belike my phone is stuck in a boot loop and they told me to have you guys reflash it. Thats what i did when my recovery was messed up and had a boot loop. Just tell them that the only thing that works is download mode or if they boot into recovery mode be like the factory reset doesnt do any thing. But i would say do this if its and absolute last option. I would say look around the fourms and mess around with it a bit more and ill do the same since you already tried petty much every thing.
Trying to unroot
Same issue here with 930T. Had rooted and was unsatisfied but I tried flashing TWRP and now I can't even boot into recovery, goes straight into home screen. Now I can't unroot after trying ODIN, SuperSU, Samsung Switch etc. Would love some help.
Make sure you actually try each one of these steps - I actually tried all these steps, and the last step worked for me. Took me 5-6 hours to unroot my phone. I use a Samsung S7 (SM-G930W8).
1. USB Cable matters. Try a different USB cable (best if it is the OEM one, if not one that gives enough power)
2. Plug into a USB 2.0 instead of a USB 3.0
3. Uninstall Kies
4. Re-install your Samsung USB drivers
5. Use a different computer
6. Use a older version of Odin (3.10 did not work for me, when I changed to 3.9 it worked)
Why not just initialize using smart switch.
So I would suggest going to this post here and downloading the ODIN 3.12
http://forum.xda-developers.com/showthread.php?t=2711451
I was trying to unroot for a clean root and this one worked for me the one made by PrinceComsy did not work for the flashing the stock ROM but it did work for flashing the ENG Boot ROM. I used 3 out of the 4 file to flash the stock rom I didn't select the BL file at all but you can if you want.
If you need any further assistance/help please reply to this and I will try to assist you further.
bfixer117 said:
So I would suggest going to this post here and downloading the ODIN 3.12
http://forum.xda-developers.com/showthread.php?t=2711451
I was trying to unroot for a clean root and this one worked for me the one made by PrinceComsy did not work for the flashing the stock ROM but it did work for flashing the ENG Boot ROM. I used 3 out of the 4 file to flash the stock rom I didn't select the BL file at all but you can if you want.
If you need any further assistance/help please reply to this and I will try to assist you further.
Click to expand...
Click to collapse
Could the issue be the stock firmware? I tried to get mine from GalaxyS7R.. and not trying from SamMobi...
I receive the same errors on PC and on device I am receiving SW REV CHECK FAIL: [about]Fused 3> Binary 2
[1] eWWC write fail: aboot
I am able to boot back into my phone but simply cannot restore back to original stock.
spaz2045 said:
Could the issue be the stock firmware? I tried to get mine from GalaxyS7R.. and not trying from SamMobi...
I receive the same errors on PC and on device I am receiving SW REV CHECK FAIL: [about]Fused 3> Binary 2
[1] eWWC write fail: aboot
I am able to boot back into my phone but simply cannot restore back to original stock.
Click to expand...
Click to collapse
Figured this out myself..need to use the correct build (there are 4 or 5 for TMO)...
I rooted last night which was successful but then I tried installing Xposed with Flashfire and after a reboot, it never came back up. I can get into what appears to be recovery mode and download mode but the phone doesn't do anything past that. In recovery, it says
Android Recovery
MMB29M.G930VVRU2APE1
Verizon/heroqltevzw/heroqltevzw
6.0.1/MMB29M/G930VVRU2APE1
user/release-keys
User volume up/down and power.
Reboot system now
Reboot to bootloader
Apply update from ADB
Apply update from SD card
Wipe data/factory reset
Wipe cache partition
Mount /system
View rcovery logs
Power off
(at the bottom)
Support API: 3
dm-verity verification failed...
If I try to flash from ADB or SD card it says "Update from external storage is disabled."
Rebooting just brings it back here.
If I reboot into bootloader, I get a bright teal colored screen with a large arrow facing down and it says, "Downloading... Do not turn off target"
If I try to flash anything from Odin (AP, BL, CP, etc....), it sees the phone and calls out it's com port, but upon flashing it FAILS within a few seconds. After a fail, it displays
SW REV CHECK FAIL : [aboot]Fused 4 > Binary 2
[1] eMMC write fail: aboot
*****************************************************************************
If I power it off and boot directly into the "Downloading..." screen then it displays
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-G930V
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
FAP LOCK: ON
QUALCOMM SECUREBOOT: ENABLE
AP SWREV: B4(2,1,1,1,1) K1 S3
SECURE DOWNLOAD: ENABLE
But it still fails flashing from Odin.
I am using Odin3 v 3.12 but the actual file says Odin PrinceComsy.exe
I'm dead in the water here. Did my phone just become a $600 paperweight?
You've tripped the dm-verity, basically, you've installed TWRP (or another custom recovery) without installing no-verity or removing dm-verity altogether. I believe there is a way to fix it if you look here: https://forum.xda-developers.com/note5/help/how-to-solve-dm-verity-verification-t3293306. I have not personally used this method but most people are saying it works. Just ensure if this does work install no-verity from here:https://build.nethunter.com/android-tools/no-verity-opt-encrypt/ and install in your recovery.
Best of luck
EDIT: Just realized this is Verizon, not sure maybe wait till someone confirms this as I have an Exyons and haven't looked a lot into the snapdragon chip
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.
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.