Galaxy A3 (SM-A300FU) Odin Recovery Problems - Galaxy A3, A5, A7, A8, A9 Q&A, Help & Troubleshoot

So basically how this all started was I was trying to flash a custom ROM onto the phone (Lineage 14.1 for SM-A300FU). However after flashing the ROM, the phone would start up onto the Android splash screen, but would then power off. I plugged the phone into a charger and checked in recovery mode that the phone was charged, which showed me it was around 80%. I tried to go into the GUI Installer of the ROM which allowed me to "Fix Boot (Replace boot.img)". I did that but that didn't work, so I decided to just attempt to go back to TouchWiz. But when in Odin (V3.12.15), the process would start, but then stop midway through the system.img.ext4 part in the log. I know it'd stopped because I left it overnight and whilst I was at school and the process was at the same point throughout. I unplugged the phone after this which made Odin say "Write process failed", so I plugged the phone back into Odin and tried again and the same thing happened. I just want to go back to the stock ROM.
EVERYTHING I'VE TRIED:
-Various Odin versions (V3.07-3.10)
-Unplugging and replugging phone into Odin
-Downloading Samsung USB Drivers
-Plugging phone into USB 3.0 and USB 2.0 ports
-Uninstalling Samsung Kies
-Using Kies' Emergency Recovery (Which couldn't read my device)
-Rebooting phone (Which shows the Firmware Update failed error)

Have you managed to solve this yet?
If oding can see your phone, then it's not with Odin, the usb ports or the drivers.
It could be that the firmware file you're trying to flash is broken/corrupted somehow. If this is the case, it shouldn't pass odin's md5 check, but maybe it did anyway.
Some firmware filesalso contain huge hidden.img files. These are carrier specific and filled with lots of bloat. If your phone is unbranded, the hidden partition will not be big enough and odin will stop halfway.
In both cases, best bet is to try downloading a different firmware file from sammobile and flash that. Unbranded ones for your country are usually good.

Related

[FIX] Bricked I9500 while flashing

Hey,
I wanted to flash the new stock I9500XWUBMG1,
I have quite a bit of experience doing it so I plugged my phone and odin wouldn't recognize it.
Tried a few things, and found out that it was recognized while not using download mode (but just having the phone on).
So I connected it to odin while it was on and then turned it off and put it to download mode, at this point the phone was recognized but appeared twice (the COM of the turned on phone and the one of the download mode).
I proceeded to try and flash it, and got an error quite qucikly.
After that error I can still get into download mode but no recovery or anything.
Tried flashing stock ROM again with/without PIT file, tried flashing CWM recovery with/without PIT file.
Right now I'm basically lost with nothing to do.
Is there a way to fix this that I haven't tried? What are the chances that hardware went bad and in need for replacement?
You could try...
Maybe it is just a soft brick that has occurred and nothing wrong with your actual phone hardware. Have you tried a different usb port? The only other thing I can think of is maybe having a look at http://forum.xda-developers.com/showthread.php?p=41072426
Using a different USB port I was able to repartition while flashing only a recovery (Philz touch),
Still I'm getting errors trying to flash the entire ROM.
I am now thinking of trying to flash a custom ROM (wanamlite) from the recovery mode.
What do you guys think?
EDIT: That did it, running on wanamlite.

Stuck on Samsung Logo Odin and Wipe done

Hi, I recently became a Galaxy S6 Edge+ as a gift, which is stuck on the Samsung Logo (blinking). I am not new to flashing Firmware and Roms (came from the HTC HD2 and Dell Streak 5), but everything I do, I can not come through this. Now I need your help, since it's my first Samsung device. Maybe I have something forgotten?
My device:
SM-G928F with Regional Code AUT (free Switzerland firmware) --> Also Samsung Smart Switch shows me this AUT Version (but it wont recognize it, shows it after typing in the serial)
What have I done:
Samsung Smart Switch does not recognize it.
The last 24 hours I have downloaded the firmware through SamFirm 4 times, I have flashed the phone via Odin about 8 times, after the flashs I have wiped the cache and resettet data (full wipe) through the recovery. One time, the phone came to the android optimatization, but it was stuck on the last app (was 30 minutes on this), after reboot it was stuck on the Samsung logo.
Now I need your help. What can I do further? Do I missed something? Any ideas?
Something strange I noticed: When the phone is off and I plug it in to the wall, the battery drains. I have to put the phone to Download-Mode to charge it. Is it linked to the firmware problem? The charger is original Samsung.
So, I flashed TWRP, the Note7 Deodexed Rom and SkyHigh kernel, but it's the same... any sugestions?
I read about a pit file, what is that? May be this the solution?
What I did the last 3 houers was to test Smart Switch With the mac version, the rescue function did not work, the hole program crashed each time. On the windows version it suceed, but my phone is showing just the blinking Samsung logo. Every now and then it vibrates, but nothing happens, so I am at the start of the problem again. Any ideas?
Next update: I flashed the original firmware with a pit file 3 minutes ago. I learned a lot, learnt that the pit files are the partition-files. Now I'm hoping, that with the new partitions it will boot properly :good: . Stay tuned!
Still the same issue. Please help me
Whenever I start the Recovery, it says "installing system update" and then there is a dead Android, does this matter?
A 4 part firmware with pit file did not help. I downloaded another Firmware from another source, also the same. Now I will do a downgrade and look, if this helps. Pleeeeease, help me!
Infos from the download mode:
Produkt Name: SM-G928F
CA_Type: CA_3
Current Binary: Samsung Official
System status: Custom
Secure Download: Enabled
Know warrenty void: 1 (0x0203)
RP SWREV: B:3 K:0 S:1
Maybe the TWRP Log helps: There are errors in writing, is there something missing? It is the original firmware, with the newest TWRP and SuperSU installed. Still stuck on Samsung (animated) logo.
Listen do you have windows on ur mac i use parallels
but do you have windows anyhoe
Sent from my SM-N920G using Tapatalk
Same here
Hello,
I'm quite new here, but not with flashing.
My son got an S6 Edge plus too, with almost the same problem.
I tried also almost anything, the last few days.
ADB sideload, Odin several versions.
It started out with FRP lock.
After I tried al I could find I think it bricked.
And now it is in the state as described above.
Only first screen and draining the battery if not in download mode.
And when I put it on USB cable it says: "An error has occured while updating the device software. Use the Emergency recovery function in the Smart Switch PC software."
But Smart Switch doesn't recognise the phone!
I can however get the phone in download mode by pushing vol. down, power and home and then vol up.
But in Odin only works: Pit, CP and CSC.
With AP and BL I get errors and fails.
Please help?
For me AP and BL works with Odin. I am a step furhter now. First I flashed with the option: Erase All Nand. Then I installed TWRP and a made a repair for the System and the Caches partitions. With SuperSU installed, and the caches wiped (manual, dalvik and normal caches), it says "Android is starting, Optimizing Apps" and then "Androis is starting, Starting Apps" on a blue screen and when it loads to the end, it is stuck there.
.You get only the first Samsung S6 Edge+ Screen? Then the system files are missing, there is no OS to start (flashed with AP in Odin). Your flash problem sound quite strange. Did you test another cable?
If you want to do it with Smart Switch, the phone should be in download mode. I also had to try it several times. Did you installed the drivers?
@ KatariaMax: I have Windows and Mac PCs, no Parallels. Does it work with Parallels?
So, one problem less. With the Audax rom and kernel, the phone charges normally (but not with Quickcharge), so I don't have to put the phone to download mode. But here is the same problem, after "starting apps" it is stuck. I will do a log from the install, maybe this helps.
@ HugoGroot: Maybe the second post could be the solution for you: http://forum.xda-developers.com/galaxy-s6/help/s6-bricked-t3497687
I read about Sony devices, which are in a bootloop because of the battery. Could this be possible also for Samsung devices? I have bought a battery, just to be sure. Any other suggestions?
I found the problem here: https://talk.sonymobile.com/t5/Xperia-Z3-Compact/Continuous-Restart-and-Optimizing-Apps/td-p/1020656

S5 SM-900A (AT&T) Bootloop & Fails 4.4.2 Flash

Hi all,
I've been looking through your other questions/answers in the forum and have found hugely helpful stuff, but now I am stuck and can't find anything. After the last AT&T software update (about a month ago?) my S5 started restarting randomly, and it progressed to get worse and worse (even in Safe Mode) to the point it is stuck in a bootloop. I did some research and have been using complete 4.4.2 Firmware files in Odin (using a Windows 7 laptop) to basically reset everything in a hope that it will solve the problem. I have no issues connecting to Odin with the right driver, and I have the correct settings in Odin set, and I have the right firmware files in the right AP/CP/CSC slots. However, when I hit "Start", Odin goes through its thing for about 10 seconds before it gets to system.img.ext4 and then comes up with a "Fail" message. From what I've read this shouldn't be happening at all. Odin recognizes the phone in download mode, and there aren't any connection issues with the USB cable so far as I can tell.
Any suggestions?

Possible bricked S7 edge please help

I have an S7 edge running the latest BTU firmware DQG1.
I have tried to flash it via Odin to EVR which failed. The phone is stuck on an error has occurred while updating the device.
It is not detectable via Samsung Smart.
I have tried to reflash it with DQG1 and it starts and then half way through fails.
Have I killed it? Please help I've only had it a week.
Here is what you can do, if it fails, then yes you have bricked your device... If not, hurray!
1. Charge your phone to 80%
2. Put your phone in download mode.
3. Uninstall, redownload and reinstall the driver for your phone. You can use the device manager in Windows for this.
4. Get the stock firmware with BTU CSC which is the default.
5. Use a new USB cable to connect the phone to the PC, this will eliminate the error IF its cable related.
6. Flash the new software
7. Pray
8. If all goes well, you'll have a working phone....
I tried again last night with a different USB cable and the latest BTU and it is now back up and running.
Next question is how do I get it on EVR firmware ?

S6 lite malfunctioned and now does nothing.

History:
I have a samsung tab S6 lite LTE version. The tablet freezed out of nowhere when I was working and restarted but stuck in bootloader. After a while, and after removing the sd card, the tablet functioned properly. The tablet had more 80% of battery charge.
I thought the new update might fix the issue. I installed the update. it restarted and stuck in bootloader again. Power and Volume Down buttons will restart the tab, but it never went past the bootloop.
Left it for 12 hours without charging, and then the tablet went into recovery mode. I wiped the cache and when figuring out the other options in recovery it switched off and did nothing. When connected to a charger, a circle with lighting icon showed up. No combination of buttons worked.
Took it to the service center, and was told the motherboard needs to be replaced. I knew it was a software problem so I came home without replacing the motherboard.
I put the tablet on charge for a while and pressed volume up and down button and connected it to the computer. The tablet went into download mode. I immediately downloaded Odin and stock firmware and tried to flash only the BL file to the tablet. It failed few times, maybe because of faulty cable. I used another working cable and tried to flash the full firmware and the tablet disconnected again from the pc.
But now the tablet showed "an error occured while updating and use smart switch for emergency recovery". Smart switch on pc did not detect the tablet, but Odin did. The device manager detected the device as samsung mobile usb composite device. I used a new usb cable and flashed the stock firmware using Odin. The process was success but the tablet died.
It does nothing when connected to a charger or pc. No display and no buttons worked.
I opened the tablet by removing the display, and disconnected the battery physically. But nothing happened.
I tried several times to connect to pc, and for once it was detected by the pc.
This time I flashed the stock firmware using odin with nand erase and repartition. extracted the pit from csc file and added it to Odin.
The flash was a success but the tablet remains unresponsive. I checked the display to see if I had cracked or damaged it while opening, but it is good.
Now Sometimes, the tablet gets detected by pc as samsung mobile usb composite device and I could even flash the firmware with success. But the tablet displays nothing and is unresponsive.
Can Anybody advice What I can do now?
PS. I used the correct firmware meant for s6 lite LTE version every time I flashed.
Disconnect devices from PC USB port & uninstall official Samsung USB drivers. Reboot & re-install drivers. Connect to another USB port preferably at the rear PC.
Flashed latest Android 10 instead of the latest Android 11 stock firmware (AP *super.img.tar file ONLY) using Odin (I used official Odin3_v3.14.4) with Auto-Reboot, Nand Erase and Re-Partition. Input *.pit file. Flashing process might take 'years' but be patient until it ended & auto boot up successfully. Try another USB port if it failed. Therafter, flash the rest of stock WITHOUT Nand Erase & ONLY Re-Partition, Auto Reboot & F. Reset Time.
Once it successfully got flashed & auto reboot, wait patiently as it might also take a longer time than normal to boot up. Charge the device to optimal. Done!
Optional (Remove Knox Guard)
Connect to the internet. Login to your Google & Samsung account to update everything & reboot upon further updates. Thereafter, boot to Download Mode & flashed AP (Magisk Patched *boot.img, blank *vbmeta.img & patched *vbmeta_samsung.img) + BL (Blank *vbmeta.img) WITHOUT Nand Erase & Re-Partition. After successful boot up, reboot back to Download Mode & ensure there's no 'KG State' on the list before deleting('root delete' not ADB) Knox Guard or app named Payment Service as in Android 10.
Thanks. I will try.
7GHz said:
Disconnect devices from PC USB port & uninstall official Samsung USB drivers. Reboot & re-install drivers. Connect to another USB port preferably at the rear PC.
Flashed latest Android 10 instead of the latest Android 11 stock firmware (AP *super.img.tar file ONLY) using Odin (I used official Odin3_v3.14.4) with Auto-Reboot, Nand Erase and Re-Partition. Input *.pit file. Flashing process might take 'years' but be patient until it ended & auto boot up successfully. Try another USB port if it failed. Therafter, flash the rest of stock WITHOUT Nand Erase & ONLY Re-Partition, Auto Reboot & F. Reset Time.
Once it successfully got flashed & auto reboot, wait patiently as it might also take a longer time than normal to boot up. Charge the device to optimal. Done!
Optional (Remove Knox Guard)
Connect to the internet. Login to your Google & Samsung account to update everything & reboot upon further updates. Thereafter, boot to Download Mode & flashed AP (Magisk Patched *boot.img, blank *vbmeta.img & patched *vbmeta_samsung.img) + BL (Blank *vbmeta.img) WITHOUT Nand Erase & Re-Partition. After successful boot up, reboot back to Download Mode & ensure there's no 'KG State' on the list before deleting('root delete' not ADB) Knox Guard or app named Payment Service as in Android 10.
Click to expand...
Click to collapse
By chance is it going to work for KG:Locked status device? I'm on F62, i bought this (second hand) few days ago from another city. Tapping on build number doesn't give any response, When i try to flash any firmware I'm getting response "All binaries are not allowed to be flashed" I'm pretty much confused what's happening here
Rolith Rtw said:
By chance is it going to work for KG:Locked status device? I'm on F62, i bought this (second hand) few days ago from another city. Tapping on build number doesn't give any response, When i try to flash any firmware I'm getting response "All binaries are not allowed to be flashed" I'm pretty much confused what's happening here
Click to expand...
Click to collapse
Did you solved it?

Categories

Resources