Samsung Galaxy A5 - Boot Error - General Questions and Answers

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

Related

[Q] [i9003] Bootloop after flashing

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:

Help with Galaxy Note 10.1 that won't boot into recovery

Ok, so I'm stuck. I can boot into download mode, but am unable to get into recovery mode. Had a system crash, and reimaged before system backup by mistake. So now just trying to resurrect this tablet... I've tried both stock firmware and rooted firmware through ODIN - it passes the flashing process, but on reboot just is stuck on the logo screen. This is a n8013 wifi only Note 10.1... I've also tried installing CWM (both highonandroid and darkman versions) to no avail. If I keep pressing up and power at boot and hold them down it will go black and boot a second time, but releasing power either before or after does not get me into recovery. I know dangerous but considering a PIT repartition at this point. Anyone gone through this or have any ideas at this point? Here's the two images I've tried - both pass but do not boot past the logo.
N8013UEALH2_XARALH2 Cellular South Android 4.04 - stock firmware I believe, not working though (just contains a single tar.md5 file)
UEALH2_rooted system - this contains a boot.img, cache.img, hidden.img, recovery.img, and system.img in the archive
Anyone have any thoughts?
I've the same Problem with my n8000.
Today I called Samsung Support and he said that it is possible to repartition, but he can't say how to do it...
Please help anyone!!!
jblazer said:
Ok, so I'm stuck. I can boot into download mode, but am unable to get into recovery mode. Had a system crash, and reimaged before system backup by mistake. So now just trying to resurrect this tablet... I've tried both stock firmware and rooted firmware through ODIN - it passes the flashing process, but on reboot just is stuck on the logo screen. This is a n8013 wifi only Note 10.1... I've also tried installing CWM (both highonandroid and darkman versions) to no avail. If I keep pressing up and power at boot and hold them down it will go black and boot a second time, but releasing power either before or after does not get me into recovery. I know dangerous but considering a PIT repartition at this point. Anyone gone through this or have any ideas at this point? Here's the two images I've tried - both pass but do not boot past the logo.
N8013UEALH2_XARALH2 Cellular South Android 4.04 - stock firmware I believe, not working though (just contains a single tar.md5 file)
UEALH2_rooted system - this contains a boot.img, cache.img, hidden.img, recovery.img, and system.img in the archive
Anyone have any thoughts?
Click to expand...
Click to collapse
I had a similar issue. If you are able to boot the device properly at least, try installing "Goo Manager" and then use the option there to reboot into recovery.
If not though, I don't have any other idea..
Pit file is the only way to repartition BUT you need to make sure it is the right pit file and isn't corrupt... If it is your tablet will be a real brick...
in S3 flashing the stock recovery solved the problem, give it a try
Couldn't hurt, you should find a link in here - http://rootgalaxynote.com/galaxy-no...t-galaxy-note-10-1-easiest-methodcwmmethod-2/
Thanks go to Zedomax for this... I believe it is the ODIN flashable tar file...
Just remember though that if the partition table is fubar then only the pit file will work...

tried to install a 6.0.1 rom and ****ed up my phone so bad.

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.

Trying to unroot Samsung Galaxy S7 manually with Odin

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)...

[PROBLEM] Getting stuck at "Getting PIT file for mapping"

Hi there!
I wanted to install a new recovery form this guide: https://forum.xda-developers.com/showthread.php?t=2663834
The phone has a stock ROM and stock recovery. I can easily go to download mode, boot it even after Odin fails to flash.
The thing is when I flash the recovery, Odin gets stuck at "Getting PIT file for mapping" or something like that and aborts flashing. No bars at phone screen while flashing (it's in the downloading mode), just nothing.
I tried flashing on different computer, different usb port/cable, different recovery and the result is still the same. Sometimes I recieve "Cannot open the COM port." error.
What can I do?
Would you flash custom recovery and root your phone?
First of all upgrade Odin version.
Which extension have cwm recovery file?
Uncheck "Re-Partition" box before the flashing.
Yea, i would to flash some ROM and root my phone
Odin 3.12.3
Tried also with older verisons
File ext: .tar.md5
everything is unchecked during the process
Do you use original samsung cable?
Restart the pc and the device. Try again to flash. If fails just put stock pit file in PIT section, tick Re-Partitions and flash it with recovery in PDA section.
Most of this issue fixes are "I solved it by plugging the cord into another port and letting windows rediscover the phone".
I used original samsung cable, didnt work.
Also adb doesnt see the device when its in downloading mode but I think thats normal.
Where can I get the stock PIT file and is it more risky when i use it?
I'll try with another port and will let know
Ive found some thread here with .pit file:
https://forum.xda-developers.com/showthread.php?t=2428753
is it the pit file that i should use?
foralost said:
I used original samsung cable, didnt work.
Also adb doesnt see the device when its in downloading mode but I think thats normal.
Where can I get the stock PIT file and is it more risky when i use it?
I'll try with another port and will let know
Ive found some thread here with .pit file:
https://forum.xda-developers.com/showthread.php?t=2428753
is it the pit file that i should use?
Click to expand...
Click to collapse
Yes, it is. Choose the right version: i9105P (NFC) - i9105 (no-NFC)
Just before flashing I have a question.
Does the flashing now with .pit file will re-create every partition on the phone causing ALL data to be erased? It would be a problem if after repartitioning odin would be still unable to flash the recovery, wouldn't it?
foralost said:
Just before flashing I have a question.
Does the flashing now with .pit file will re-create every partition on the phone causing ALL data to be erased? It would be a problem if after repartitioning odin would be still unable to flash the recovery, wouldn't it?
Click to expand...
Click to collapse
Pit erases all your partition and removes all datas. Recovery hasn't problem with stock pit file.
Went like a charm without using PIT file (unchecked Re-Partition). It went by using different USB Port and I don't know, maybe the fact that I put the pit file also with the recovery image in the same folder.
Damn, this Odin-issue can be very annoying, I tried like over ten times and nothing and now it just went all straight forward for the first time. Thanks for replying!
foralost said:
Went like a charm without using PIT file (unchecked Re-Partition). It went by using different USB Port and I don't know, maybe the fact that I put the pit file also with the recovery image in the same folder.
Damn, this Odin-issue can be very annoying, I tried like over ten times and nothing and now it just went all straight forward for the first time. Thanks for replying!
Click to expand...
Click to collapse
Good news. You're welcome!

Categories

Resources