Hello everyone!
I had some stability issues on my Samsung GT-I9003, so I flashed it . And, as the title says it, I'm stuck in a bootloop. I've tried 3 or 4 flashings with different packages. Some where "One packages", with one unique PDA, or I tried the XXKPE with everything. And I'm lost. I never get past the first boot screen.
[EDIT]
I found a way to boot it, but the touchscreen isn't working, so I'm now stuck on the language selection page...
Is it my ROM who doesn't fit?
[/EDIT]
Thanks!
Before going to download mode try wiping everything, then flash xxkpe TWICE then wipe again. Make sure you flash it correctly. And odin shows PASS. Try flashing the latona.pit included in xxkpe.
Press thanks if it helped..
Sent from my GT-I9003 using XDA
Thanks for the answer!
Problem is it didn't work!
I got a little deeper in the problem. In order to boot to android, I need to flash the bagaria root file. It contains the normalboot image. So I assume that the boot is corrupted. I'd add that after the rooting, the android recovery boots and wipes everything, but he says that the CSC wasn't installed, because "[...]/stl11" is not there. Is it the .pit?
I'm lost, again...
Thanks a lot for your help!
jonasdu91 said:
Thanks for the answer!
Problem is it didn't work!
I got a little deeper in the problem. In order to boot to android, I need to flash the bagaria root file. It contains the normalboot image. So I assume that the boot is corrupted. I'd add that after the rooting, the android recovery boots and wipes everything, but he says that the CSC wasn't installed, because "[...]/stl11" is not there. Is it the .pit?
I'm lost, again...
Thanks a lot for your help!
Click to expand...
Click to collapse
so weird. Where did you download your xxkpe. Try here
http://forum.xda-developers.com/showthread.php?t=1004647
then follow the guide here
http://forum.xda-developers.com/showthread.php?p=14933114
I think you just fail a step on flashing a rom.
---------- Post added at 09:16 PM ---------- Previous post was at 09:14 PM ----------
Flashing bagaria root is done after flashing a stock rom for it to be rooted. You failed to put CSC file in odin maybe. Follow the guide above perfectly then everything will be fine.
You start the procedure on Step 3 if your done downloading XXKPE here
http://forum.xda-developers.com/showthread.php?t=1004647
jonasdu91 said:
Thanks for the answer!
Problem is it didn't work!
I got a little deeper in the problem. In order to boot to android, I need to flash the bagaria root file. It contains the normalboot image. So I assume that the boot is corrupted. I'd add that after the rooting, the android recovery boots and wipes everything, but he says that the CSC wasn't installed, because "[...]/stl11" is not there. Is it the .pit?
I'm lost, again...
Thanks a lot for your help!
Click to expand...
Click to collapse
/stl11 is the /cache partition.
look like you fail to flash pit file, or u flash "one package .tar file" with partition ticked in odin.
see below for the samsung recommend setup
flash pit file with all the firmware one short.
if you flash from Froyo to GB, i recommend to flash the bootloader update.
however, flash on you own risk.
100% Work!
Hi.
Flash this Chinese rom, with Odin 1.85.
latona_open_china_20101222_r01.pit---------------->PIT
I9003ZCKC1-REV08-ALL-low-CL961866------------>PDA
MODEM_I9003ZCKC1_REV_00_CL866730------->PHONE
I9003-CSC-MULTI-OZH961866------------------------->CSC
Enjoy.
100% Works for me.
For those who are struck in boot loop or Softbrick their mobile do the following things exactly as they had mentioned. I followed them and boom my phone is back to normal.
For bringing your phone back to download mode (Recovering from Softbrick)
http://forum.xda-developers.com/showthread.php?t=1411768
After entering into download mode (reinstall Ginger bread )
http://forum.xda-developers.com/showthread.php?t=1133787
Note: This step deletes your user data, so be sure what you are doing
Definitely your phone should be back to normal if you follow these steps exactly.....
Million Thanks to all those who helped me in bringing back my mobile to normal function....
Hi, I am facing the same issue with a GT-I9003 as jonasdu91. I tried all the solutions mentioned above, tried all sort of firmwares. The only time the phone responded was when I flashed the bagaria file. That too ended up with a non-responsive touchscreen at the language selection screen.
Could anyone suggest what more could I do to get the phone to upgrade?
ghassir said:
Hi.
Flash this Chinese rom, with Odin 1.85.
latona_open_china_20101222_r01.pit---------------->PIT
I9003ZCKC1-REV08-ALL-low-CL961866------------>PDA
MODEM_I9003ZCKC1_REV_00_CL866730------->PHONE
I9003-CSC-MULTI-OZH961866------------------------->CSC
Enjoy.
100% Works for me.
Click to expand...
Click to collapse
Worked for me too!!! You saved my life! Thanks!
ghassir said:
Hi.
Flash this Chinese rom, with Odin 1.85.
latona_open_china_20101222_r01.pit---------------->PIT
I9003ZCKC1-REV08-ALL-low-CL961866------------>PDA
MODEM_I9003ZCKC1_REV_00_CL866730------->PHONE
I9003-CSC-MULTI-OZH961866------------------------->CSC
Enjoy.
100% Works for me.
Click to expand...
Click to collapse
Good!
ghassir said:
Hi.
Flash this Chinese rom, with Odin 1.85.
latona_open_china_20101222_r01.pit---------------->PIT
I9003ZCKC1-REV08-ALL-low-CL961866------------>PDA
MODEM_I9003ZCKC1_REV_00_CL866730------->PHONE
I9003-CSC-MULTI-OZH961866------------------------->CSC
Enjoy.
100% Works for me.
Click to expand...
Click to collapse
How do I flash other stock rom after that? I've tried to flash XXLE4 rom, and received boot error and unmounted FS
Hello everyone, an acquaintance of mine, had initially given his Galaxy SL device to a friend of his, asking him, to 'update' the software on the device. The device had come with Android 2.2.1, pre-installed on it (PDA: I9003DDKB2; PHONE: I9003DDKA5; CSC: I9003ODDKA6).
Apparently, my acquaintance's friend flashed the I9003DDMF1 stock Gingerbread firmware via PC ODIN, and after my acquaintance gave me the device, I noticed, it did not boot to a home screen. It would boot loop at the Samsung boot animation.
The device boots into Download Mode, but does not get into the stock Recovery Mode. So, I attempted numerous remedial procedures. I used PC ODIN3 v1.85 for all flashing instances.
Keeping Misledz's guide, http://forum.xda-developers.com/showthread.php?t=1133787, as a reference, I flashed the I9003XXKPE firmware package, followed by the I9003XXKPQ_I9003SERKPQ_SER firmware.
After PC ODIN gave a PASS for the I9003XXKPE firmware package flashing instance, the device rebooted, and I observed a process, looking like the stock Recovery Mode, continuing on the device. There were a couple of strings, displayed in red colour. The device rebooted again to the Samsung logo, and I had to pull the battery out, to continue with the I9003XXKPQ_I9003SERKPQ_SER firmware flashing instance. After PC ODIN displayed the PASS sign and the device rebooted, I unplugged the USB cable, but the boot loop at Samsung boot animation persisted.
Since the above mentioned procedure did not solve the boot loop issue, I decided to take the device back to a stock Froyo firmware, and if successful, reattempt to 'update' the device to stock Gingerbread (2.3.6), by following Misledz's guide. I flashed the I9003_XXKB1 stock Froyo firmware, but this time, the device would not go beyond the Samsung logo.
As a momentary last attempt, before seeking help here, I flashed the I9003ZCKC1 firmware package, but yet, the device does not go beyond the Samsung logo.
All the flashing instances completed successfully on PC ODIN.
Is it possible to revive the device, such that it boots to a home screen and is functional again? I desperately need help.
YLNdroid said:
Hello everyone, an acquaintance of mine, had initially given his Galaxy SL device to a friend of his, asking him, to 'update' the software on the device. The device had come with Android 2.2.1, pre-installed on it (PDA: I9003DDKB2; PHONE: I9003DDKA5; CSC: I9003ODDKA6).
Apparently, my acquaintance's friend flashed the I9003DDMF1 stock Gingerbread firmware via PC ODIN, and after my acquaintance gave me the device, I noticed, it did not boot to a home screen. It would boot loop at the Samsung boot animation.
The device boots into Download Mode, but does not get into the stock Recovery Mode. So, I attempted numerous remedial procedures. I used PC ODIN3 v1.85 for all flashing instances.
Keeping Misledz's guide, http://forum.xda-developers.com/showthread.php?t=1133787, as a reference, I flashed the I9003XXKPE firmware package, followed by the I9003XXKPQ_I9003SERKPQ_SER firmware.
After PC ODIN gave a PASS for the I9003XXKPE firmware package flashing instance, the device rebooted, and I observed a process, looking like the stock Recovery Mode, continuing on the device. There were a couple of strings, displayed in red colour. The device rebooted again to the Samsung logo, and I had to pull the battery out, to continue with the I9003XXKPQ_I9003SERKPQ_SER firmware flashing instance. After PC ODIN displayed the PASS sign and the device rebooted, I unplugged the USB cable, but the boot loop at Samsung boot animation persisted.
Since the above mentioned procedure did not solve the boot loop issue, I decided to take the device back to a stock Froyo firmware, and if successful, reattempt to 'update' the device to stock Gingerbread (2.3.6), by following Misledz's guide. I flashed the I9003_XXKB1 stock Froyo firmware, but this time, the device would not go beyond the Samsung logo.
As a momentary last attempt, before seeking help here, I flashed the I9003ZCKC1 firmware package, but yet, the device does not go beyond the Samsung logo.
All the flashing instances completed successfully on PC ODIN.
Is it possible to revive the device, such that it boots to a home screen and is functional again? I desperately need help.
Click to expand...
Click to collapse
Firstm download this XXKPE: https://disk.yandex.ru/public/?hash=mTOUkkpPv4WgFtvIpy07S2CwUoU5gUcna1FTdjKHc90=
and flash it.
Put the files like this:
PIT - latona_20110114.pit
PDA - I9003XXKC1-REV08-PDA-low-CL964212.tar.md5
PHONE - MODEM_I9003XXKC1_REV_00_CL964949.tar.md5
CSC - GT-I9003-CSC-SERKC1.tar.md5
Click to expand...
Click to collapse
It contains all 5 files needed to boot your phone. This will repartition your phone and make it alive, after that, you may flash any 2.3.x ROM you like.
xumix said:
Firstm download this XXKPE: https://disk.yandex.ru/public/?hash=mTOUkkpPv4WgFtvIpy07S2CwUoU5gUcna1FTdjKHc90=
and flash it.
It contains all 5 files needed to boot your phone. This will repartition your phone and make it alive, after that, you may flash any 2.3.x ROM you like.
Click to expand...
Click to collapse
xumix, thank you very much for your response.
I believe, the 5 files contained within the I9003XXKPE_Odin3_1.8.5.zip package, would correspond to the options available in PC ODIN3 v1.85, as follows -
PIT > latona_20110114.pit
BOOTLOADER > APBOOT_I9003XXKPE_CL409735_REV08_user_low_ship.tar.md5
PDA > CODE_I9003XXKPE_CL409735_REV08_user_low_ship.tar.md5
PHONE > MODEM_I9003XXKPE_REV_00_CL1041909.tar.md5
CSC > GT-I9003-CSC-MULTI-OXAKPE.tar.md5
Click to expand...
Click to collapse
Am I right?
:silly:
YLNdroid said:
Am I right?
:silly:
Click to expand...
Click to collapse
You are right
xumix said:
You are right
Click to expand...
Click to collapse
xumix, I flashed the I9003XXKPE_Odin3_1.8.5.zip firmware package using PC ODIN3 v1.85, but to no avail. The boot loop on the Samsung boot animation continues to persist.
EDIT
I have noticed there is a u1_02_20110310_emmc_EXT4.pit, contained within the Odin3-v1.85 folder. What is this, PIT file for?
I re-flashed the I9003XXKPE_Odin3_1.8.5.zip firmware package using PC ODIN3 v1.85, and the process completed successfully. But, since the boot loop at the Samsung boot animation persisted, I pulled the battery out, and booted into Recovery Mode, not once, but on two separate instances. I was able to perform a wipe data/factory reset, on the second instance. I also performed a wipe cache partition and rebooted the device. But, the boot loop issue still continues.
I have attached images of both instances, I clicked using another device, to this post.
If dont mind. Try my step below.
In download mode
Flash pit file alone. Make sure repartition is ticked.
Phone will black screen, you pull out battery and put back.
Download mode again. Flash xxkpe without pit file.
BTW, you error show properly is emmc chip broken, hope it is not.
Sent from my GT-I9003 using Tapatalk
chongns said:
If dont mind. Try my step below.
In download mode
Flash pit file alone. Make sure repartition is ticked.
Phone will black screen, you pull out battery and put back.
Download mode again. Flash xxkpe without pit file.
BTW, you error show properly is emmc chip broken, hope it is not.
Click to expand...
Click to collapse
chongns, I followed your stepwise suggestions, to the word, but unfortunately, the boot loop issue still persists. One distinct error under the stock recovery is, E:format_volume: rfs format failed on /dev/block/mmcblk0p3. Am I correct to believe this error strongly indicates, or rather confirms, the internal SD is damaged?
Also, what are the possible causes (physical, and or, logical) that would damage the internal SD? Is it worth sending the device to an authorised Samsung service centre, for an appropriate repair process?
YLNdroid said:
chongns, I followed your stepwise suggestions, to the word, but unfortunately, the boot loop issue still persists. One distinct error under the stock recovery is, E:format_volume: rfs format failed on /dev/block/mmcblk0p3. Am I correct to believe this error strongly indicates, or rather confirms, the internal SD is damaged?
Also, what are the possible causes (physical, and or, logical) that would damage the internal SD? Is it worth sending the device to an authorised Samsung service centre, for an appropriate repair process?
Click to expand...
Click to collapse
Friends, I still await your expertise.
:fingers-crossed:
I am completley stumped. I am trying to help out a friend who messed up his phone trying to install a rom, and I just want to install CWM or TWRP via odin.
When i open any version of odin, and browse to the .tar.md5 files (i have gotten a couple different ones) odin doesnt see any of them. In the bottom right of the "open" window it says it is looking for .tar and .md5 files, but it just doesnt see them...
I feel like i am missing something simple. The phone boots into download mode, (odin mode) and odin recgonizes it, if i could just get a recovery onto it, i could flash a rom for him, but im stumped. Is there a way to flash a rom onto the phone without a custom recovery if it wont boot?
Thank you so much in advance.
Jay
whereismyhat said:
I am completley stumped. I am trying to help out a friend who messed up his phone trying to install a rom, and I just want to install CWM or TWRP via odin.
When i open any version of odin, and browse to the .tar.md5 files (i have gotten a couple different ones) odin doesnt see any of them. In the bottom right of the "open" window it says it is looking for .tar and .md5 files, but it just doesnt see them...
I feel like i am missing something simple. The phone boots into download mode, (odin mode) and odin recgonizes it, if i could just get a recovery onto it, i could flash a rom for him, but im stumped. Is there a way to flash a rom onto the phone without a custom recovery if it wont boot?
Thank you so much in advance.
Jay
Click to expand...
Click to collapse
Which phone, and which version of Odin? Please be specific.
It recgonizes the cf-autoroot md5 file just fine - http://prntscr.com/7x7ity
But im not getting it to recgonize any of the recovery files - http://prntscr.com/7x7jsl
why is windows thinking it is an application, is it something with how i extracted it?
Edit - it is a samsung mega i9205, I have tried multiple versions of odin, 3.07 3.09 and one other one. I am trying to follow one of these threads
http://forum.xda-developers.com/showthread.php?t=2369998
there are others like it i was trying but all produce the same results
whereismyhat said:
It recgonizes the cf-autoroot md5 file just fine - http://prntscr.com/7x7ity
But im not getting it to recgonize any of the recovery files - http://prntscr.com/7x7jsl
why is windows thinking it is an application, is it something with how i extracted it?
Edit - it is a samsung mega i9205, I have tried multiple versions of odin, 3.07 3.09 and one other one. I am trying to follow one of these threads
http://forum.xda-developers.com/showthread.php?t=2369998
there are others like it i was trying but all produce the same results
Click to expand...
Click to collapse
Have you tried asking for help here:
http://forum.xda-developers.com/showthread.php?t=2329215
I havent asked there, it doesnt seem like a problem specific to the mega, odin doesnt recgonize the files before i even plug the phone in, i could be putting a recovery onto any phone, see what im saying?
But i will cross post to there also.
I flashed a bootloader and modem from one of the roms here and after that my S6 will no longer get past the Samsung Galaxy S6 screen, it just repeats from there. I can't get into recovery mode, only download mode.
I tried flashing stock firmware from sammobile but it still doesn't work, won't get past sboot.bin before failing.
HELP
I wouldn't worry too much. I brick my phone all the time Which rom was loaded. What are you trying to do?
Sent from my SM-G920F using Tapatalk
Try THIS firmware, it will work;
http://www.sammobile.com/firmwares/download/66009/G920FXXU3DPBG_G920FOXE3DPAD_SER/
Delete everything from .tar file except system.img and boot.img(You can also leave sboot.bin if it works) and reflash Your phone. If that doesn't work try reflashing with .pit file. Aaand if it still doesn't work. Boot into recovery->factory reset->odin reflash of system.img+boot.img with .pit file.
Small guide:
1. Boot into recovery mode.
1a. Do a factory reset
2. Reflash the stock rom using only system.img and boot.img files(optionally sboot.bin too).
3. If still nothing works. Google "pit file g920f" and download it.
4. Flash like in step 3 but including .pit file.
If You have any other questions. I would appreciate a odin flash log .
ProtoDeVNan0 said:
Delete everything from .tar file except system.img and boot.img(You can also leave sboot.bin if it works) and reflash Your phone. If that doesn't work try reflashing with .pit file. Aaand if it still doesn't work. Boot into recovery->factory reset->odin reflash of system.img+boot.img with .pit file.
Small guide:
1. Boot into recovery mode.
1a. Do a factory reset
2. Reflash the stock rom using only system.img and boot.img files(optionally sboot.bin too).
3. If still nothing works. Google "pit file g920f" and download it.
4. Flash like in step 3 but including .pit file.
If You have any other questions. I would appreciate a odin flash log .
Click to expand...
Click to collapse
as I've said, I can't go into recovery mode
Then ignore step 1 and 1a. Or You could try and boot into odin mode. And where You have options to reboot or go into downloading mode. Just press the vol down to reboot and immediately hold vol down+home+power and it should boot too.
Try going into recovery mode again then wait at least 3 to 5 minutes after the droid falls over. That should take you to stock recovery mode. From there you can do a factory reset.
Sent from my SM-G920F using Tapatalk
protodevnan0 said:
delete everything from .tar file except system.img and boot.img(you can also leave sboot.bin if it works) and reflash your phone. If that doesn't work try reflashing with .pit file. Aaand if it still doesn't work. Boot into recovery->factory reset->odin reflash of system.img+boot.img with .pit file.
Small guide:
1. Boot into recovery mode.
1a. Do a factory reset
2. Reflash the stock rom using only system.img and boot.img files(optionally sboot.bin too).
3. If still nothing works. Google "pit file g920f" and download it.
4. Flash like in step 3 but including .pit file.
If you have any other questions. I would appreciate a odin flash log .
Click to expand...
Click to collapse
forumber2 said:
try this firmware, it will work;
http://www.sammobile.com/firmwares/download/66009/g920fxxu3dpbg_g920foxe3dpad_ser/
Click to expand...
Click to collapse
dear god man, i ****ing love you!!!!!!!!!!!!!!!!!!
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
Hello everyone,
I'm in a loop, I've been trying to solve it for five days, any help will be apreciate.
I have an SM-g930F in boot loop and I need to save the data that I have on it.
I'm trying to install TWRP through Odin, but when I try to do it, the Blocked by FAP message appears. (On the S7 screen)
I don't have access to developer options, because the phone is in a boot loop, I can only enter in Download Mode (Odin Mode), Recovery doesn't work either.
All this happened after uninstalling the secure folder, the phone freeze and it didn't start up correctly again, it stayed in a boot loop trying to start up in recovery. (#fail to open recovery_cause)
I tried to flash the latest firmware with ODIN but it gave me FAIL with hidden.img
After that, the mobile only started in Emergency recovery and in Download Mode (Odin Mode). Also after this, the phone was discharged and the battery stopped charging. I can only use it if it is connected to the wall or via USB.
At this moment I have found the solution to the FAIL of the hidden.img in firmware (it seems to be the .lz4 format) but I am afraid of flashing in Odin without having a battery.
I have also tried with a wireless charger and it still does not charge.
Could I install the firmware via USB while charging with the wireless charger? Or is it very risky?
My idea was to restore the recovery with TWRP through Odin, to be able to charge the battery and then install all the firmware again with Odin, but as I have mentioned the problem is that in the development options I do not have the OEM enabled (Also I have looked for how to enable it through ADB, but I think it is not possible because the device needs to be running).
Another possibility, although it doesn't make me very happy, would be to change the battery, and try to install the firmware in Odin. (But sometimes the new ones also come with little charge)
Finally there is the possibility to use Smart Switch PC to restore it to factory, but that would erase all the data.
Does anyone know what I can do to fix this? Any help would be appreciated.
Thank you
I think the problem with the hidden.img is that some files are corrupted.
Use the following tool do Download the firmware straight from Samsung Servers :
Releases · zacharee/SamloaderKotlin
Contribute to zacharee/SamloaderKotlin development by creating an account on GitHub.
github.com
Than go to download mode and let the phone plugged. Flash the files with odin.
Try at first with the home csc and see if you can boot to safe your data.
If not you have to use normal csc which will erase your data and bring the phone to factory state. Unfortunately i see no other solution for you.
Thats why you should always do a backup of your files. I had to learn it the hard way too.
USB power should be enough to run and flash the firmware through odin. Just dont disconnect the phone while flashing.
Edit: make sure to use always the latest version of odin which is if remember correctly 13.14.1:
Samsung Odin - Root Android download page for one click root
Samsung odin download - Root android and oneclickroot for flash / install custom ROM with one click root method
odindownload.com
Thank you very much for your answer.
Is it really safe to do the flashing without any battery? I have always read somewhere that you have to have a minimum of 50%. I'm afraid that later I won't be able to flash again.
On the other hand, I had an idea, but I don't know if it's possible or if it's safe to do it. Could I just install the straight firmware recovery.img from Samsung Servers? That is, extract the recovery.img from AP and then flash only the recovery.img in Odin on AP? (I don't know if it could be a problem to flash a stock recovery from another different stock firmware)
In recovery mode the phone should charge and I imagine that installing recovery.img will be faster in Odin.
Thanks again
Logeate said:
Thank you very much for your answer.
Is it really safe to do the flashing without any battery? I have always read somewhere that you have to have a minimum of 50%. I'm afraid that later I won't be able to flash again.
On the other hand, I had an idea, but I don't know if it's possible or if it's safe to do it. Could I just install the straight firmware recovery.img from Samsung Servers? That is, extract the recovery.img from AP and then flash only the recovery.img in Odin on AP? (I don't know if it could be a problem to flash a stock recovery from another different stock firmware)
In recovery mode the phone should charge and I imagine that installing recovery.img will be faster in Odin.
Thanks again
Click to expand...
Click to collapse
It is risky but unless you diconnect the phone during odin flash it should not turn off normally.
You need a .tar file to install a recovery through odin.
All right.
But from what I've read it would be possible to unzip the AP (and in this case remove the rest of the files leaving only the recovery.img), then compress again with 7zip and flash with Odin. It is right?
Although what scares me the most is that there is a problem flashing only the recovery.img of two different firmwares, could that create a conflict?
Thank you very much.
Logeate said:
All right.
But from what I've read it would be possible to unzip the AP (and in this case remove the rest of the files leaving only the recovery.img), then compress again with 7zip and flash with Odin. It is right?
Although what scares me the most is that there is a problem flashing only the recovery.img of two different firmwares, could that create a conflict?
Thank you very much.
Click to expand...
Click to collapse
I did not try it and cant tell you if it will work. Guess you have too try and see what happens.
All right, I'll see what i do.
Thank you very much.
Well, here's the update.
I managed to solve it, the mobile already works.
I share the solution in case someone else can use it as a reference.
It has worked for me, that does not mean that it will work for you, because using Odin with low battery is risky.
The solution was reinstall the recovery.img that I had previously extracted from the stock firmware.
After that, the device has restarted and automatically started charging the battery, which was effectively completely discharged.
All the problem came for a failure in the recovery.
So, installing the recovery.img needs 4 seconds, so although it is risky to flash with zero battery, it is very fast and so it is a good solution.
After the phone updated Android (also the applications) started keeping all the applications and data, which was what I wanted.
In brief:
Download the official firmware from Samsung of your device, from Sammobile, Frija, etc. (Make sure it is the exact version of your phone)
Unzip the AP with Winrar
Open the folder and copy recovery.img
Compress the recovery.img file in .tar format with the 7-Zip compressor
Download the latest version of Odin.
Connect the phone via USB and put it in Odin mode. Make sure the phone is stable and can last for a long time with the USB cable.
Flash recovery.tar in the AP tab
It only takes 4 seconds.
That's all, the phone recharges the battery in recovery mode. When turned on, it updates and restarts itself.
In my case it was not necessary to do anything else, the phone worked fine. You can also (of course after charging the battery) flash all firmware (or install TWRP) in Odin as usual.
That's all, thanks for your help aarem, Regards.