Database Users

How To Hard Reset Phone Via Physical Keys

I installed Modaco ROM and cleared data via recovery.. as soon as I booted up I had many force closes... so I am trying to install modaco again but I can't get to recovery via adb because of the force closes (doesn't allow me to get to settings menu) and
Power+home+volume up -> takes you to recovery mode does not work for me....
what should I do now?
Edit: I have managed to get to recovery via physical keys and I'll see if problem has gone away...
Still getting the many many force closes and they keep looping. I can't access the phone at all. I tried to cle3ar data and install modaco again from recovery but this keeps happening..
I am worried now.. can anyone help?
thanks

jUsT2eXy said:
I installed Modaco ROM and cleared data via recovery.. as soon as I booted up I had many force closes... so I am trying to install modaco again but I can't get to recovery via adb because of the force closes (doesn't allow me to get to settings menu) and
Power+home+volume up -> takes you to recovery mode does not work for me....
what should I do now?
Edit: I have managed to get to recovery via physical keys and I'll see if problem has gone away...
Still getting the many many force closes and they keep looping. I can't access the phone at all. I tried to cle3ar data and install modaco again from recovery but this keeps happening..
I am worried now.. can anyone help?
thanks
Click to expand...
Click to collapse
I think it should be volume down, not up
there's another way to factory reset: *2767*3855#
In your situation, I think factory reset doesn't work. You should try Odin instead

Volume down gives me "downloading..do not turn off target" ... any ideas?
How would I use Odin?
I can't access the 'settings menu' or use the phone without a pop up force close message
So i cant get to usb debugging...
also cant use dialer to enter that number
any other ideas?
thanks for your reply.
Edit: I can use odin by doing this right because when I sued odin last time it installed drivers meaning the phone was accessible.. let me try and Ill post back thanks

hi i have tried odin but it is stuck on the same thing... nothing is happening
<ID:0/009> Added!!
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> factoryfs.rfs
thats it.. nothing is moving etc
what now
shall I try another firmware JF3 instead of 5?
JF3 came with my phone

When I had that problem I ticked the repartition box in odin and it then flew through.Not sure what the function of repartition is but worked for me first time.

hey. I did try repartition enabled before I posted this but it was also stuck...
How long did it take you.. the very first time I used odin it done it quickly.. but this time none of the bars work.
dOh

Just try another firmware
Check list:
- take sdcard and SIM out
- take the battery out and put in again.
- firmware JFB
- re-partition checked
- include CODE, MODEM, CSC tar files.

I restarted my pc and odin has started working again... I hope my phone is ok after this.. I will tr modaco again without clearing data... phew...
I have not ticked repartition..
shall I run odin again with it checked?

with re-partition checked, it will just clear your external sd card.
If it's ok now, stay with it

nice one my friend.
thank you very much for your help. its people like you that make XDA the best community !
many thanks once again

[Info]FIXING A BRICKED PHONE

People asked me Hey TechnoCrat,
Rooting my Android phone went well, but I've tried to flash a custom ROM and now I think I've bricked my phone. Is there anything I can do?
…
First of all, lets get something straight. Most people use the term "bricked" improperly. A bricked phone means one thing: your phone won't turn on in any way, shape or form, and there's nothing you can do to fix it. It is, for all intents and purposes, as useful as a brick. A phone stuck in a boot loop is not bricked, nor is a phone that boots straight into recovery mode. These are things you can usually fix, and they're a lot more common than a truly bricked phone. If your phone is actually bricked, you won't be able to fix it yourself (but there are things you can do—see the end of this article). For those other problems, you have a few options.
If Your Phone Keeps Rebooting: Wipe Your Data and Cache
How Do I Fix My Bricked Android Phone?
If you've flashed a ROM and your phone won't boot into the home screen, it's probably because you forgot to wipe your data and/or cache. It's trying to boot into the ROM, but some leftover data from your last ROM is causing it to error out, and it'll reboot itself over and over again. If your phone's eating a big bowl of boot loops, your first course of action should be to wipe its data and cache, which you can do from recovery mode. This method assumes you're using ClockworkMod Recovery, like the majority of Android users, but if your particular phone uses a different third-party recovery (like AmonRA), you should still be able to find these options in the interface. They might just be in a different place. To wipe your data and cache:
Power down your phone. Turn it back on and boot into Recovery mode. This is a bit different for every phone, so you'll have to Google how to do it for your specific model. Usually it involves holding down another button, like Volume Down, as you turn your phone on. HTC phones will have to then select "Recovery" from a menu, while other phones will boot directly into ClockworkMod. You'll know you're in ClockworkMod by the words "ClockworkMod Recovery" at the top of the screen.
Use your volume keys to navigate the menus, and your power button to select menu items. Scroll down to Advanced, and choose "Wipe Dalvik Cache". When that's finished, go back to the main screen and choose "Wipe Cache Partition". Lastly, head to "Wipe Data/Factory Reset". This will delete all your settings and apps, but you should still be using the correct ROM.
Reboot your phone.
Click to expand...
Click to collapse
With any luck, it should boot right into your ROM. If that didn't work, try the below method with the same ROM (or with a different ROM) and see if you get different results.
If Your Phone Boots Straight Into Recovery: Flash a New ROM
How Do I Fix My Bricked Android Phone?
If, when you boot up your phone, it goes straight into ClockworkMod, then there's likely an issue with the ROM you flashed. Note that some ROMs boot into recovery mode automatically after flashing, so reboot your phone once from recovery mode to make sure you're having a problem. HTC users: if you boot up your phone, it might go straight into the bootloader—check to see whether you can choose "Recovery" from the list before continuing to the next step. HTC phones usually don't boot straight into recovery.
In this case, you'll want to reflash the ROM from scratch. Try again with the ROM that messed up your phone, if you so choose, but if that doesn't work, try an entirely different ROM. The best way to do this is to download a ROM from somewhere on the net and putting it on your SD card. You'll need to take the SD card out of your phone, and you'll need an SD card reader that you can plug into your computer. Here's how it works:
Plug the SD card into your computer. Drag the ROM's ZIP file to your SD card, and wait for it to copy.
When it's done copying, eject the SD card and put it back in your phone. Reboot into Recovery mode. This is a bit different for every phone, so you'll have to Google how to do it for your specific model. Usually it involves holding down another button, like Volume Down, as you turn your phone on. HTC phones will have to then select "Recovery" from a menu, while other phones will boot directly into ClockworkMod. You'll know you're in ClockworkMod by the words "ClockworkMod Recovery" at the top of the screen.
Use your volume keys to navigate the menus, and your power button to select menu items. Scroll down to "Install ZIP From SD Card" and navigate to the ZIP file you just copied over. Give it time to flash the ROM.
When it's done, reboot your phone.
Hopefully, your phone should successfully boot into the new ROM. From there, you can probably assume that the previous ROM that messed up your phone isn't going to work, and you'll have to find another ROM for now—or find another copy of that ROM that isn't corrupted. Remember to make backups of your working ROMs so you don't lose all your data!
Click to expand...
Click to collapse
If Your Phone Boots Straight Into its Bootloader: Restore From a Stock ROM
If you're really having trouble, one of the most surefire ways to get your phone working again is to restore from the original ROM your phone came with—unrooted, stock, stable goodness. Each manufacturer and phone has a different method for doing this, and we can't go into too much detail here, but we can steer you in the right direction.Like Samsung has odin.
Note that this will unroot your phone, and return it to exactly how it was when you bought it from the store. You'll lose all your apps, settings, ClockworkMod recovery, you'll get over-the-air updates again, and you'll even have to re-activate your phone if you're on a CDMA provider like Verizon or Sprint.
For Samsung Phones: If you're using a Samsung Galaxy phone, you can use a tool called Odin to reflash an OPS file, which is a stock ROM that will return your phone to factory settings. You'll need a Windows machine and a copy of Odin, which you can find by Googling around the net (as its not an official tool). Check out the video to the left to see an example of Odin, and check out The Unlockr's guide to using Odin to familiarize yourself. You may need to Google around for your specific device's OPS file and instructions.
Click to expand...
Click to collapse
If You Get Errors with Any of The Above Methods: Reformat Your SD Card and Don't Give Up
This is less likely, but it's a problem I and a few others have run into on occasion: sometimes your SD card just gets corrupted, which makes the above methods useless (since they rely on your SD card to work). Take your SD card out of your phone, put it into your computer using an SD card reader, and format it. It's very important that you format it through an SD card reader directly and not by plugging in your phone in USB mode—I learned this the hard way. Format it as FAT32 and try the above methods again.
Other errors, like during the ROM flashing process, might give you a hint as to what's wrong. Try heading to the XDA Developers forums and asking for help, as your phone could have one of a million specific problems we can't address here today. Remember, if your phone turns on, there's still a good chance you can recover from whatever error you're experiencing, so don't give up just yet!
Click to expand...
Click to collapse
If Your Phone Is Truly Bricked: Take It Into the Store and Play Dumb
If your phone is actually bricked—that is, it won't turn on at all, no matter how hard you try—it's time to give up and move on. The first thing you can do in this situation is try to take it back to your carrier's store and play dumb—just say something like "I don't know what happened, but my phone won't turn on anymore" (don't tell them you rooted it, obviously). Most carriers don't have time to deal with such issues and they'll just give you a new phone. Sure, it's a tad evil, but it should work most of the time.
If they're wise to your act, though, you can try another store or just sell your bricked phone for a few bucks on Craigslist. Sadly, if no one will replace your phone, you'll have to buy an entirely new one. Such are the dangers of rooting, but don't be discouraged! Bricking your phone is pretty rare, so I wouldn't worry about it being a common occurrence. As always, though, when you void your warranty, only do so if you're ready to replace that device completely, since you never know what can happen.
Click to expand...
Click to collapse
Source::Lifehacker

Bump
Sent from my GT-I9103 using xda app-developers app

So you're bumping a thread full of info you lifted from another site word for word ? Classy.
(That you've gave credit is irrelevant, you could just as easily have posted a link somewhere, and this stuff has been posted here thousands of times before already)

MistahBungle said:
So you're bumping a thread full of info you lifted from another site word for word ? Classy.
(That you've gave credit is irrelevant, you could just as easily have posted a link somewhere, and this stuff has been posted here thousands of times before already)
Click to expand...
Click to collapse
Wouldn't that be irrelevant? I start a thread and just post links?
Sent from my GT-I9103 using xda app-developers app

Please delete.

What if it boost into CWM recovery but none of the options work? And Odin won't recognize the device because of driver issues?
Tha TechnoCrat said:
People asked me Hey TechnoCrat,
Rooting my Android phone went well, but I've tried to flash a custom ROM and now I think I've bricked my phone. Is there anything I can do?
…
First of all, lets get something straight. Most people use the term "bricked" improperly. A bricked phone means one thing: your phone won't turn on in any way, shape or form, and there's nothing you can do to fix it. It is, for all intents and purposes, as useful as a brick. A phone stuck in a boot loop is not bricked, nor is a phone that boots straight into recovery mode. These are things you can usually fix, and they're a lot more common than a truly bricked phone. If your phone is actually bricked, you won't be able to fix it yourself (but there are things you can do—see the end of this article). For those other problems, you have a few options.
If Your Phone Keeps Rebooting: Wipe Your Data and Cache
How Do I Fix My Bricked Android Phone?
With any luck, it should boot right into your ROM. If that didn't work, try the below method with the same ROM (or with a different ROM) and see if you get different results.
If Your Phone Boots Straight Into Recovery: Flash a New ROM
How Do I Fix My Bricked Android Phone?
If Your Phone Boots Straight Into its Bootloader: Restore From a Stock ROM
If You Get Errors with Any of The Above Methods: Reformat Your SD Card and Don't Give Up
If Your Phone Is Truly Bricked: Take It Into the Store and Play Dumb
Source::Lifehacker
Click to expand...
Click to collapse

keltaurn said:
What if it boost into CWM recovery but none of the options work? And Odin won't recognize the device because of driver issues?
Click to expand...
Click to collapse
yeah, i have the same problem
http://forum.xda-developers.com/showthread.php?p=51582800 is my thread related to this (NEED HELP)

keltaurn said:
What if it boost into CWM recovery but none of the options work? And Odin won't recognize the device because of driver issues?
Click to expand...
Click to collapse
I got it fixed long ago, just try other computer and different cable (just in case)
Hope this helps
Hit thanks if I helped you sent from my SM-T211 using XDA Free mobile app

boot loop, no boot logo.
the phone keeps rebooting but no boot logo. just the "Samsung Galaxy S4 GT-i9500"
i was just sending an SMS, and suddenly my phone rebooted.
whenever i put my battery back. the phone turns on automatically and wont stop looping.
tried to boot into recovery and DL mode, but nothing, just keeps looping.
i have CM 11 (4.4.2)

lasmaty07 said:
the phone keeps rebooting but no boot logo. just the "Samsung Galaxy S4 GT-i9500"
i was just sending an SMS, and suddenly my phone rebooted.
whenever i put my battery back. the phone turns on automatically and wont stop looping.
tried to boot into recovery and DL mode, but nothing, just keeps looping.
i have CM 11 (4.4.2)
Click to expand...
Click to collapse
It's not rom related. It's a phisical problem, problably it's a broke power button, or faulty battery.

misterG33 said:
It's not rom related. It's a phisical problem, problably it's a broke power button, or faulty battery.
Click to expand...
Click to collapse
thanks for the answer.
luckily it was still under warranty, (despite having CM 11, they do not check those thing here in argentina) took it to my carrier and they changed the POWER button.

Tha TechnoCrat said:
Bump
Sent from my GT-I9103 using xda app-developers app
Click to expand...
Click to collapse
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
i tried flashing the pit file but failed
gt i9505(TCL) plz help!!!!!!!!!!!!

I bricked my rca 4.1 android phone shaped like a galaxy s3 i cant seem to get off the logo screen please help thank you
Sent from my LGL86C using XDA Free mobile app

Softbricked Samsung galaxy grand prime SM-G530R4
Can some one plz plz plzzz help me.
i softbricked my phone and Kies 3, and smart switch is not working i tried odin
but it always gets stuck on NON-HLOS.bin
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G530R4TYU1AOF5_G530R4USC1AOF5_G530R4TYU1AOF5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> hyp.mbn
<ID:0/003> NON-HLOS.bin

Hello, I have a MediaTek device (Android 9, Lenovo Tab M8 FHD) I had it updated to Android 10 and in the process of trying to downgrade it to 9, I bricked it..badly....The indicator still responds to power buttons and plugging it in, but I cannot access recovery or fastboot. Is this tablet a goner or is there any fix?

I was stuck in a bootloop after flashing AOSP rom. So I decided to power off and use SPFlashTool to flash the stock rom. But both SP and Techno flash tools give the following error:
ERROR : STATUS_BROM_CMD_STARTCMD_FAIL (-1073348607) , MSP ERROE CODE : 0x00.
The phone doesn't respond to any button presses however whenever I connected it with my PC, the charging indicator glows and even windows can detect it, and the device is listed in ports.
Can anyone please help.
Device is Infinix Hot 8.
TIA.

i have a cricket Dream 5G phone nd it went brick it literaly says ´´your device is corrupted and is not trusted and may not work properly please visit link 9.co/ABH on another device

My phone is stuck in bootloop after I flashed an unofficial twrp img on my phone. I`ve tried a couple of things; factory data resetting adb fastboot through command [fastboot -w] I also relocked my bootloader and when I tried re-booting it showed a message; your device has failed verification and may not work properly. Whilst also asking me to install the correct boot img file for the phone, of course I`d already done that. after a sometime while I was trying multiple things a command failed due to low battery. Is there any way to fix this? My device of course is very unpopular; Ulefone note 7p, Kindly help.

Problem with Samsung Galaxy S4 - Help please

Hello,
I have a Samsung S4 locked to the T-Mobile/EE network in the UK.
The phone has suddenly stopped working.
When I do manage to switch it on, the phone vibrates and then the Samsung logo comes up but the background screen is all jumbled up, like its scrambled. I have tried getting the phone into Safe Mode, but it didn't work. I have also tried recovery mode, but some blue text comes on the top left of the screen and it just stays there.
I got these details from the stick in the back of the Phone if it helps.
MODEL: GT-I9505
FCC ID: A3LGTI9505
SSN:I9505GSMH
I hope somebody here can help me.
I am not that technically minded, but if steps are shown I can work it out, if there is a fix.
Thank you.

You may have to reflash the Samsung rom using Odin.
You can download the stock rom from sammobile.com.

boom247 said:
Hello,
I have a Samsung S4 locked to the T-Mobile/EE network in the UK.
The phone has suddenly stopped working.
When I do manage to switch it on, the phone vibrates and then the Samsung logo comes up but the background screen is all jumbled up, like its scrambled. I have tried getting the phone into Safe Mode, but it didn't work. I have also tried recovery mode, but some blue text comes on the top left of the screen and it just stays there.
I got these details from the stick in the back of the Phone if it helps.
MODEL: GT-I9505
FCC ID: A3LGTI9505
SSN:I9505GSMH
I hope somebody here can help me.
I am not that technically minded, but if steps are shown I can work it out, if there is a fix.
Thank you.
Click to expand...
Click to collapse
Hey there,
Unfortunately those stickers don't always represent the reality, because the sticker can be changed.
For the time being you will have to try and flash a stock rom.
Head over to sammobile.com, input your phone model, choose your country and carrier then download the latest firmware. Beware of very slow download speeds. You might want to give SamFirm tool a shot.
Afterwards get Odin (3.09 always worked well for me). Make sure you have the Samsung drivers installed.
Extract the firmware zip/rar you got and you should end up with a tar file.
Put the phone into download mode (volume down + power button), run odin, connect the phone to the PC (odin should display added!)
Put the tar file into the the AP slot (I think), uncheck every option in Odin except F.Reset time and hit start. Wait for it to complete.

GDReaper said:
Hey there,
Unfortunately those stickers don't always represent the reality, because the sticker can be changed.
For the time being you will have to try and flash a stock rom.
Head over to sammobile.com, input your phone model, choose your country and carrier then download the latest firmware. Beware of very slow download speeds. You might want to give SamFirm tool a shot.
Afterwards get Odin (3.09 always worked well for me). Make sure you have the Samsung drivers installed.
Extract the firmware zip/rar you got and you should end up with a tar file.
Put the phone into download mode (volume down + power button), run odin, connect the phone to the PC (odin should display added!)
Put the tar file into the the AP slot (I think), uncheck every option in Odin except F.Reset time and hit start. Wait for it to complete.
Click to expand...
Click to collapse
Thanks I will try that. File is downloading as I type.

GDReaper said:
Hey there,
Unfortunately those stickers don't always represent the reality, because the sticker can be changed.
For the time being you will have to try and flash a stock rom.
Head over to sammobile.com, input your phone model, choose your country and carrier then download the latest firmware. Beware of very slow download speeds. You might want to give SamFirm tool a shot.
Afterwards get Odin (3.09 always worked well for me). Make sure you have the Samsung drivers installed.
Extract the firmware zip/rar you got and you should end up with a tar file.
Put the phone into download mode (volume down + power button), run odin, connect the phone to the PC (odin should display added!)
Put the tar file into the the AP slot (I think), uncheck every option in Odin except F.Reset time and hit start. Wait for it to complete.
Click to expand...
Click to collapse
I done that, it shows a green coloured PASS in the top left square.
The phone is still showing Downloading.... Do not turn off.
This is what was shown in the message screen
What do I do now with the phone?
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUHOD7_I9505EVRHOD1_I9505XXUHOD7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> modem.bin
<ID:0/003> NON-HLOS.bin
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse

boom247 said:
I done that, it shows a green coloured PASS in the top left square.
The phone is still showing Downloading.... Do not turn off.
This is what was shown in the message screen
What do I do now with the phone?
Click to expand...
Click to collapse
You turn the phone off and unplug it. Then power it on. Hopefully it will boot. If not, try booting into recovery and then doing a factory reset. Reboot.

GDReaper said:
You turn the phone off and unplug it. Then power it on. Hopefully it will boot. If not, try booting into recovery and then doing a factory reset. Reboot.
Click to expand...
Click to collapse
ok. it doesn't turn on now. oh boy...

boom247 said:
ok. it doesn't turn on now. oh boy...
Click to expand...
Click to collapse
Then jump start it by plugging it in.

GDReaper said:
Then jump start it by plugging it in.
Click to expand...
Click to collapse
I've already tried that. It's not turning on at all.

boom247 said:
I've already tried that. It's not turning on at all.
Click to expand...
Click to collapse
Try a different battery.

GDReaper said:
Try a different battery.
Click to expand...
Click to collapse
Ok, so after leaving it for a few hours with the battery out. I managed to turn it on. plugged in the charger and it came up with the following message
Firmware upgrade encountered an issue. please select recovery mode in kies and try again.
(tried keis and its rubbish)

boom247 said:
Ok, so after leaving it for a few hours with the battery out. I managed to turn it on. plugged in the charger and it came up with the following message
Firmware upgrade encountered an issue. please select recovery mode in kies and try again.
(tried keis and its rubbish)
Click to expand...
Click to collapse
It may be possible that it did not flash right. For now I'd say to flash the firmware once more and hopefully it won't die again.

Problem with Samsung Galaxy S4 - Help please - UPDATE
Hello,
Ok, so after numerious times flashing, turning on off, etc etc. My Samsung S4 is still not working.
I've managed to take some photos of what I saw when I was flashing the phone using odin.
As you will see the screen does scamble sometimes, but when I tap it slightly it clears up again.
If anyone can help me, let me know, would like some experienced users for their suggestions.

Did you get any errors when flashing in Odin?
If the screen clears up when you touch it in download/Odin mode, sounds like there may be hardware damage.

audit13 said:
Did you get any errors when flashing in Odin?
If the screen clears up when you touch it in download/Odin mode, sounds like there may be hardware damage.
Click to expand...
Click to collapse
When I found the correct OS to flash I didn't get any errors. So, No, no errors.
I think it might be hardware failure.
But the recovery to flash the phone works. However anything else doesn't.
When I turn it on, it just hangs on the logo screen.

Are you performing a factory wipe in stock recovery right after flashing and before booting the phone for the first time?

audit13 said:
Are you performing a factory wipe in stock recovery right after flashing and before booting the phone for the first time?
Click to expand...
Click to collapse
To be honest, I am following instructions I found on-line. These are instructions on how to flash with ODIN
I remember I showed my phone to a IT guy at work, who wiped the cache, but after that Ive never been able to go into that menu again.
I would appreciate any further help and suggestions.
Thank you for your reply

To get into recovery, are you holding down the home button, volume up, and power?

audit13 said:
To get into recovery, are you holding down the home button, volume up, and power?
Click to expand...
Click to collapse
Yes I did try that. It comes up with the blue recovery text on the top left of the screen and just stays there

Try this: open Odin, uncheck auto reboot, flash the phone with the stock ROM, when you see the word reset in the status window, remove the USB cable from the phone, remove battery, replace battery, press and hold all three buttons. It may take a while but keep holding the buttons to see what happens.

Galaxy S8 G950FD Stuck at Logo after Flash

I have a G950FD, which I changed CSC on (from SIN to XEU), and this worked fine. Wifi calling was not available, so I decided to just flash the BTU firmware instead. I followed instructions on sammobile website (I specified the AP file, but not the others, as per instructions and did NOT select Re-partition), using odin 3.12.7 and the flash went through. However after reboot, it is stuck at the boot screen (just shows Samsung Galaxy S8 in white text, with Powered by android on bottom in white too). I tried to reboot into recovery mode to do a wipe and format but I cannot boot into recovery.
- I am unable to turn the phone off (holding power in does not force it to shut down)
- I am unable to boot into Recovery (holding VolUp + Bixby + Power does nothing, no matter what is showing on screen)
- I AM able to reboot phone with VolDown + Power
- I AM able to boot into Download mode with VolDown + Bixby + Power
- Phone is NOT rooted and KNOX is 0x0
- Phone had standard firmware and boot and recovery on it when I flashed BTU firmware
I tried to reflash again, and it reports following and then reboots -
<ID:0/005> Odin engine v(ID:3.1207)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> FAIL! (DeviceInfo)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!​
I have tried holding various button combinations when I click start in Odin, but the same result every time (error as above, and reboot, and stuck at boot screen)
I tried to use Smart Switch and it's emergency initialization option but this goes through the motions of asking for model and serial and then downloading the Firmware, and then it starts the process of writing the firmware, but after showing no progress on progress bar, the phone reboots (and gets stuck boot screen) and Smart Switch reports a failure, telling me to try again.
Am I correct that this phone seems to no longer have a Recovery partition ? All instructions keep telling me to switch off the phone and then go into download / recovery / whatever, but I am unable to shutdown the phone, I can ONLY reboot it or reboot into Download mode.
Is this phone now a useless brick ?

I have your exact same issue, I think the issue originated because we did not flash csc/bl/cp the second time, not sure. The issue seems specific to the S8, unable to find anything online.
The first time I brick a device and it had to be my s8, FeelsBadMan.
Were you able to figure out anything?

I left the phone overnight to drain and turn off, which it did. As soon as I plugged in charger, it went straight back to boot screen without me even touching the power button.
Still no luck in doing anything other down going to boot screen or Download mode.
Anyone got any bright ideas ? I'm pretty much willing to try ANYTHING to get this phone working again. I don;t care about the data on the phone, just want it working.

Just realized that the AP I flashed with Odin was earlier than what was on there, as the phone updated itself to AQG5 when it was set to CSC of XEU. I'm going to download the XEU AQG5 firmware and try to flash that to see if it helps.

Nope - same problem.

Hello,
I had flashed AQG5 firmware and was having the same issue for last 4 days. i.e. Stuck on boot screen showing Galaxy S8 screen. Unable to boot into recovery as well.
I just now flashed AQF7 via odin and now it working fine
I flashed AP, BL, CP, & CSC files

priyank500 said:
Hello,
I had flashed AQG5 firmware and was having the same issue for last 4 days. i.e. Stuck on boot screen showing Galaxy S8 screen. Unable to boot into recovery as well.
I just now flashed AQF7 via odin and now it working fine
I flashed AP, BL, CP, & CSC files
Click to expand...
Click to collapse
Which version of ODIN did you use ? Also, did you flash CSC or HOME_CSC ?
- EDIT - I just noticed that the FW I flashed that got me into this mess WAS AQF7 already. Reflashing it does nothing

I flashed CSC.

To avoid that FAIL issue in Odin just hold bixby+volume down+power buttons right after clicking start(you should be fast ) and release them when the "BOOT" stage is complete(it's one of the first stages so you won't have to to perform that fingers trick for long). If you hold buttons too long it will fail again.
And also leave the default settings in Odin. And use all files, not just AP but also BL and others(can't remember them all) and use CSC, not HOME_CSC. It will wipe all your data but in your case I recommend doing so.
As long as you are able to boot into recovery or download mode your phone is not bricked. So don't worry, there's always a way to bring the phone back to life.

nikonazaroff said:
To avoid that FAIL issue in Odin just hold bixby+volume down+power buttons right after clicking start(you should be fast ) and release them when the "BOOT" stage is complete(it's one of the first stages so you won't have to to perform that fingers trick for long). If you hold buttons too long it will fail again.
And also leave the default settings in Odin. And use all files, not just AP but also BL and others(can't remember them all) and use CSC, not HOME_CSC. It will wipe all your data but in your case I recommend doing so.
As long as you are able to boot into recovery or download mode your phone is not bricked. So don't worry, there's always a way to bring the phone back to life.
Click to expand...
Click to collapse
Must I hold the buttons and then click Start, or click start and then hold the buttons ? When you say " release them when the "BOOT" stage is complete" what do you mean? as soon as I click Start, it shows the following and then reboots the phone and goes immediately to the Samsung logo and stays there -
<ID:0/005> Odin engine v(ID:3.1207)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> FAIL! (DeviceInfo)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!​
Also, I assume that you are saying I must go into download mode (bixby+volume down+power) connect to pc and load odin and then select all the files. then click Start and then very quickly press "bixby+volume down+power" AGAIN to go back into download mode ? Is this BEFORE the phone restarts, or after ?

OK. Had this same problem and got it to work. Here is what I did:
- Odin 3.12.5
- Image: G950FDXXU1AQE5_OXM1AQE5_India_7.0
1 - Went into Download mode with the Power+Bixby+VDown
2 - Selected BL+AP+CP+CSC (pretty much replace all) in Odin
3 - before I hit start, press the Power+Bixby+VDown and continued to hold.
4 - Press Start - and I get the same error and phone reboots - keep holding down.
5 - Comes back up in Download mode, let go and select download mode again.
6 - once in download, press down and hold the Power+Bixby+VDown and hit start on Odin again (yes ,same as above).
7 - it should start loading the image. Once it starts, let go of the buttons or the phone will reboot again and kill it.
Basically, it fails once then imaged on the second time. If you let it get to the samsung screen between download screens, you just have to start over.
After that, it was fine. Had quiet a scare on this one.

dmcnall said:
OK. Had this same problem and got it to work. Here is what I did:
- Odin 3.12.5
- Image: G950FDXXU1AQE5_OXM1AQE5_India_7.0
1 - Went into Download mode with the Power+Bixby+VDown
2 - Selected BL+AP+CP+CSC (pretty much replace all) in Odin
3 - before I hit start, press the Power+Bixby+VDown and continued to hold.
4 - Press Start - and I get the same error and phone reboots - keep holding down.
5 - Comes back up in Download mode, let go and select download mode again.
6 - once in download, press down and hold the Power+Bixby+VDown and hit start on Odin again (yes ,same as above).
7 - it should start loading the image. Once it starts, let go of the buttons or the phone will reboot again and kill it.
Basically, it fails once then imaged on the second time. If you let it get to the samsung screen between download screens, you just have to start over.
After that, it was fine. Had quiet a scare on this one.
Click to expand...
Click to collapse
Progress sort of......
Before doing this, I reinstalled Device drivers in Smart Sqitch
I then did the steps above, up to and including click Start for first time. It loaded firmware without fail message. Surprised, I let go of the buttons and let if finish. It reported the following -
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)​The phone then rebooted and continued with post FW write procedure (I THINK it showed something about formatting or partitioniong)
It then rebooted and comes up with Installing System Update. This then goes to Error at about 6% and reboots and keep on showing Installing System Update.... 6% and Error and reboot
ARGH
Could this be because the battery is empty, and that when it is performing system update it does not charge, even though it is plugged into PC still ?
If I reboot into Download mode 'part 1' (but do NOT press VolUp when prompted, so do not go into actual download mode) and leave it connected to the charger that came with the phone, will this charge it ?

More progress !!
I plugged phone into charger while in Download Stage 1 mode, and then clicked VolDown to boot. It went to Installing System Update and then failed immediately, showing Error. Progress bar went up to 10% and it then went into Recoveyr mode. It is sat in Recovery mode at this time and I am leaving it there till I get some guidance.
What should I do ?
Wipe cache and format and reboot?
Leave it in recovery for an hour to charge and then go back into Download and reflash? If I do this, is it ok to leave phone connectedto PC when ODIN finished flashing and it reboots, or should I disconnect as soon as it reboots after flash (and then maybe plug into floor charger just to be safe) ?

The information on the bottom of recovery screen show the following (as per picture below)
Support SINGLE-SKU
Supported API: 3
-- Installing package...
Finding update package...
Opening update package...
E:failed to map file
-- meminfo...
Installation aborted. #2
-- omc_binary_download...
-- Deleting selective files
Successfully deleted files selectively
-- Deleting RSU selective file
Successfully deleted RSU selective file
-- omc-app-link...
[amazon_link] mismattached carrierID(-1015403757)​

FINALLY got the phone to work. I wiped cache and formatted in recovery mode and then rebooted. Phone started as if I had just done a Factory reset. Strangely, the firmware on the phone is AQF7 and CSC's report as XEU/XEU/XSP. It seems like the entire firmware flash process has not happened and all that happened is a Factory reset...
I'm not complaining... at least the phone is working now. What I will do is leave it as is and only try going a CSC change using *#272*IMEI# (as this is how I got it into XEU) to get it to BTU CSC. If wifi calling still doesn;t work, then I'm leaving phone as is. I've been flashing galaxy phones for years now and this is the first time I have 'near bricked' my phone, so I'm going to leave it as is !!
Thanks for all the help everyone

nikonazaroff said:
To avoid that FAIL issue in Odin just hold bixby+volume down+power buttons right after clicking start(you should be fast ) and release them when the "BOOT" stage is complete(it's one of the first stages so you won't have to to perform that fingers trick for long). If you hold buttons too long it will fail again.
And also leave the default settings in Odin. And use all files, not just AP but also BL and others(can't remember them all) and use CSC, not HOME_CSC. It will wipe all your data but in your case I recommend doing so.
As long as you are able to boot into recovery or download mode your phone is not bricked. So don't worry, there's always a way to bring the phone back to life.
Click to expand...
Click to collapse
Thanks a bunch, any idea why this error occurs? Seems really weird...

uberNoobZA said:
Must I hold the buttons and then click Start, or click start and then hold the buttons ? When you say " release them when the "BOOT" stage is complete" what do you mean? as soon as I click Start, it shows the following and then reboots the phone and goes immediately to the Samsung logo and stays there -
<ID:0/005> Odin engine v(ID:3.1207)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> FAIL! (DeviceInfo)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!​
Also, I assume that you are saying I must go into download mode (bixby+volume down+power) connect to pc and load odin and then select all the files. then click Start and then very quickly press "bixby+volume down+power" AGAIN to go back into download mode ? Is this BEFORE the phone restarts, or after ?
Click to expand...
Click to collapse
You should start holding the buttons just right after you press START in Odin(you should be already in download mode of course), really you should start holding those buttons right in the next moment after you click START in Odin, so you must do it really fast. It should avoid that FAIL issue in Odin and proceed to further installation of the firmware. As soon as it finishes flashing BOOT, release those buttons(as I said BOOT is one of the first stages so you will have to release the buttons after a second or two), if you keep holding them it will fail again and it will also fail if you start holding them before you press START or if you start holding them too late. Yes, we are using this combination to go to the download mode but in this case it won't do that, it should allow you to avoid that FAIL at the start of flashing process.
Hope this will help you.

nikonazaroff said:
You should start holding the buttons just right after you press START in Odin(you should be already in download mode of course), really you should start holding those buttons right in the next moment after you click START in Odin, so you must do it really fast. It should avoid that FAIL issue in Odin and proceed to further installation of the firmware. As soon as it finishes flashing BOOT, release those buttons(as I said BOOT is one of the first stages so you will have to release the buttons after a second or two), if you keep holding them it will fail again and it will also fail if you start holding them before you press START or if you start holding them too late. Yes, we are using this combination to go to the download mode but in this case it won't do that, it should allow you to avoid that FAIL at the start of flashing process.
Hope this will help you.
Click to expand...
Click to collapse
What do you mean by BOOT, I don't see anything that says BOOT
---------- Post added at 07:26 PM ---------- Previous post was at 06:57 PM ----------
uberNoobZA said:
Progress sort of......
Before doing this, I reinstalled Device drivers in Smart Sqitch
I then did the steps above, up to and including click Start for first time. It loaded firmware without fail message. Surprised, I let go of the buttons and let if finish. It reported the following -
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)​The phone then rebooted and continued with post FW write procedure (I THINK it showed something about formatting or partitioniong)
It then rebooted and comes up with Installing System Update. This then goes to Error at about 6% and reboots and keep on showing Installing System Update.... 6% and Error and reboot
ARGH
Could this be because the battery is empty, and that when it is performing system update it does not charge, even though it is plugged into PC still ?
If I reboot into Download mode 'part 1' (but do NOT press VolUp when prompted, so do not go into actual download mode) and leave it connected to the charger that came with the phone, will this charge it ?
Click to expand...
Click to collapse
I can see to get this to work...what magic did you do? I cant seem to follow the second part of the restart because the SW_REV_CHECK_FAIL is on the phone's screen and so the Start button on Odin won't click and start.

UberNoobZA how did you go on recovery mode? After SUCCESSFULLY flashing it with CRI5, my device is stuck on Samsung Logo SM-G950F and i can go to download mode, but i CANNOT go to recovery mode (VolUP+Bixby+Power)

From what I can remember, I followed information in post 17 above by nikonazaroff

Galaxy S4 (sgh-1337M) soft bricked, help required

So I am fairly technically savvy, but I'm very new to this aspect, and have been browsing this forum, reddit, and every other site looking for any possible solution. I'll try to be as detailed as possible:
My girlfriend's old Samsung Galaxy S4 (SGH-1337M) soft bricked last year. It got stuck in a boot loop and when she removed the battery, she got the "Firmware error: select recover in Kies" message. She has since gotten a new phone, but I want to use this old phone as a game/music player, since it has better storage and battery life than my phone. It was originally a Koodo phone.
I have Odin v3.12, and the info of the firmware I am trying to flash (from their site):
Download I337MVLUGOH1 OYAGOH1 5.0.1Repair Firmware 4Files ( KDO Canada (Koodo Mobile) )
Download Samsung Repair Firmware Full Flash
Model: Samsung GALAXY S4 SGH-I337M
OS Version: Android Lollipop V5.0.1
PDA/AP Version: I337MVLUGOH1
CSC Version: I337MOYAGOH1
MODEM/CP Version: I337MVLUGOH1
Region: KDO Canada (Koodo Mobile)
Security Patch Level: N/A
--------------------
Content Of File:
AP_I337MVLUGOH1_CL4508315_QB6089219_REV06_user_low_ship_MULTI_CERT.tar.md5
BL_I337MVLUGOH1_CL4508315_QB6089219_REV06_user_low_ship_MULTI_CERT.tar.md5
CP_I337MVLUGOH1_CL4508315_QB6089219_REV06_user_low_ship_MULTI_CERT.tar.md5
CSC_OYA_I337MOYAGOH1_CL4508315_QB6089219_REV06_user_low_ship_MULTI_CERT.tar.md5
info.txt
JFLTE_CAN_OPEN.pit
Click to expand...
Click to collapse
Odin does recognize the phone, I have it plugged in to a usb port on the back of my tower, and the flash gives me the green PASS! prompt when I flash the 4 files (I tried the .pit file as well, same end result). I have tried with the reboot and f. reset time options checked, I have tried with the re-partition option checked, I have tried taking the battery out after booting up the phone and running Odin without the battery in, I have let the battery charge to 100%, I have let the battery fully drain. I have tried Sasktel and Koodo firmware, I have tried the 4-5 CP/AP/BL/CSC files, and I have tried the single AP file.
No matter what I have tried, the phone will not boot past the Samsung Galaxy S4 screen. It either hangs on that screen, or goes back into the boot loop. The first time I tried this, I tried it with the single AP file for Sasktel, and it actually worked for about an hour before powering down by itself and going back to the boot loop. Since then, I have purchased a new battery (same model number, identical to the one it replaced), but I am making less progress. On occasion, the phone will actually get past the Samsung logo and open up the recovery options, but that will either pause and reset at the android icon (the progress bar with the android mascot with his belly open) or will skip directly to the mascot on its back, open the recovery menu, then immediately reboot.
Sometimes, now, when the phone is charging, it just shows the grey battery icon, but will not show the green progress bar or the little sparkles to indicate it is charging. Sometimes when it does this, the sparkles and bar will appear, but will immediately freeze and the phone will reboot.
Is there something painfully obvious that I am missing? Am I using a bad version, am I skipping an important step, or is my phone beyond my repair? If anyone has any suggestions for the exact steps and the exact firmware I should be using, I'd greatly appreciate the help. I'm about ready to just throw the damned thing in the garbage and cut my losses. As I said before, I don't want the phone to really be used as a phone, I just want it to play a few games and listen to music without cutting into my phone's terrible battery life.

Use Odin 3.07, do not check anything except f reset time. Flash in the AP box, download the latest stock ROM from sammobile.com. Unzip the sammobile file once to create a tar.md5 file. Do not unzip any further before flashing. When you see the word "reset" in the status window, remove the USB cable from the phone, remove the battery, replace the battery, boot directly into recovery mode, perform a factory wipe/reset, and reboot.
The sgh-i337m is the same model used by all Canadian carriers so it doesn't matter which carrier firmware is flashed.

audit13 said:
Use Odin 3.07, do not check anything except f reset time. Flash in the AP box, download the latest stock ROM from sammobile.com. Unzip the sammobile file once to create a tar.md5 file. Do not unzip any further before flashing. When you see the word "reset" in the status window, remove the USB cable from the phone, remove the battery, replace the battery, boot directly into recovery mode, perform a factory wipe/reset, and reboot.
The sgh-i337m is the same model used by all Canadian carriers so it doesn't matter which carrier firmware is flashed.
Click to expand...
Click to collapse
I'm using Odin 3.07 now, I have unchecked everything but f reset time, I flashed the most recent stock rom from sammobile in the "PDA" section. Odin gets to this point:
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLSGQB1_I337MOYAGQB1_I337MVLSGQB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> aboot.mbn
<ID:0/012> NAND Write Start!!
<ID:0/012> sbl1.mbn
<ID:0/012> sbl2.mbn
<ID:0/012> sbl3.mbn
<ID:0/012> rpm.mbn
<ID:0/012> tz.mbn
<ID:0/012> boot.img
<ID:0/012> recovery.img
<ID:0/012> system.img.ext4
Click to expand...
Click to collapse
and now the top left corner of my phone says:
ODIN MODE
PRODUCT NAME: SGH-1337M
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMAC BURST MODE enabled
START [224, 1440]
BAR [248, 1440]
Set Warranty Bit: system
And Odin has been stalled out for about half an hour on this. The USB cable I am using for this one is brand new out of package. The USB 2.0 port I am using is one of the two closest to the top of the back of the tower.
Edit: Same ****. Recovery Booting... shows in the top left corner, but the phone stalls on that screen and does not continue.

When flashing with Odin, the phone will have a blue progress bar. It may look like it stalled because the system image take time to copy over and install.
Right after flashing, you pulled the battery and used the button combination to try and recovery? To get into recovery, you release the power button once the phone vibrates and then keep holding volume up and home.

audit13 said:
When flashing with Odin, the phone will have a blue progress bar. It may look like it stalled because the system image take time to copy over and install.
Right after flashing, you pulled the battery and used the button combination to try and recovery? To get into recovery, you release the power button once the phone vibrates and then keep holding volume up and home.
Click to expand...
Click to collapse
I pulled that battery, replaced it, pressed and held volume up+power until the phone started loading, held volume up until the blue "recovery booting" prompt showed, but the phone either hangs on that screen until the battery dies, or goes into a bootloop regardless.
Edit: Now when I try to get into the boot menu, the Samsung logo screen has a bunch of grey horizontal lines going across it. I think the phone may just be totally bricked.

Very strange. Try flashing TWRP using Odin 3.07 in the PDA slot. You'll need to uncheck everything, and do the battery pull after seeing "reset" in the status window. Replace the battery and try to boot into recovery.
https://twrp.me/samsung/samsunggalaxys4internationalqualcomm.html

audit13 said:
Very strange. Try flashing TWRP using Odin 3.07 in the PDA slot. You'll need to uncheck everything, and do the battery pull after seeing "reset" in the status window. Replace the battery and try to boot into recovery.
https://twrp.me/samsung/samsunggalaxys4internationalqualcomm.html
Click to expand...
Click to collapse
Downloaded the latest .img.tar file from the link you posted, TWRP v3.2.2, flashed it on the PDA slot, unplugged my phone ,replaced the battery, booted up with safe mode keys, same thing except now under the blue "recovery" prompt, there is a yellow line that says "Set Warranty Bit: recovery", and it's hanging on this screen again. Odin says the file flashed though, so that's maybe a good sign.
Edit: and now it's boot looping but it keeps trying to open up recovery with or without me holding home+volume up, and the new corner prompt says "recovery booting" then "recovery is not something enforcing" ( can't read the word before enforcing, it is too small) and then "set warranty bit: recovery" below that. Also, the battery is now incredibly hot so I took it out completely and am going to just leave it out until your response, don't want to risk a Hooli.

It says that about the warranty bit because you flashed a custom recovery.
The only thing left to try world be flashing the stock ROM with a pit file.

audit13 said:
It says that about the warranty bit because you flashed a custom recovery.
The only thing left to try world be flashing the stock ROM with a pit file.
Click to expand...
Click to collapse
Alright, so, as I said in my first post, the files that I originally did try to flash contained a pit file, how exactly should I set that up to maximize my chances of it actually working? Options checked, unchecked, battery, etc.
If it doesn't work, thanks for at least offering to help. The thing might just be bricked. I'll follow up either way to let you know the result.

Did you check re-partition and flash as a single file in PDA?
If that doesn't work, you may have to go to a cell shop and have them flash it via JTAG.

audit13 said:
Did you check re-partition and flash as a single file in PDA?
If that doesn't work, you may have to go to a cell shop and have them flash it via JTAG.
Click to expand...
Click to collapse
I tried every possible variable since I last updated here. Different USB slots, different cables, different versions of Odin and the firmware. It's still booting and still allows me into download mode, and Odin still recognizes it, but it's still just stuck in the boot loop. I'm going to have to take it to a repair shop.
Thanks for all your help, but it looks like this one is beyond us. There is an electronics repair store about 10 minutes walking from me, so I guess I'll be making that trip here soon. Didn't want to spend too much money fixing it up, so if they can't do it on the cheap, I'm gonna just toss the thing and cut my losses.

DinkyP said:
I tried every possible variable since I last updated here. Different USB slots, different cables, different versions of Odin and the firmware. It's still booting and still allows me into download mode, and Odin still recognizes it, but it's still just stuck in the boot loop. I'm going to have to take it to a repair shop.
Thanks for all your help, but it looks like this one is beyond us. There is an electronics repair store about 10 minutes walking from me, so I guess I'll be making that trip here soon. Didn't want to spend too much money fixing it up, so if they can't do it on the cheap, I'm gonna just toss the thing and cut my losses.
Click to expand...
Click to collapse
Sounds like the internal memory chip may be damaged.
Don't toss it, use it for a trade in when companies like Bell or Koodo offer a credit towards a new phone. This is what I did with a few phones that wouldn't even turn on.