Related
So I was attempting to flash the rom eugene posted today, went into clockwork, after i hit wipe user data, the phone hung forever on the wiping data screen(approx a half hour), so I pulled the battery and rebooted the phone. At that point it will not boot past the vibrant screen, so I am attempting to flash back to stock using JAC's ODIN method, and it seems to be hanging on the "file analysis" step. I have the phone in download mode, and istalled the samsung drivers using PDAnet. Anyone have any suggestions? Is my phone(hopefully not) bricked??? HELP!
Edit:I was able to finally get this to work, didn't realize for one that I had to remove my sim and memory card(had read this in another post, durr). I did have some issues with it hanging at the cache step. Just had to remove the battery and start process again about 5 or 6 times before it finally took. Just make 100% sure you never remove the battery while the little blue status bar is running, as apparently this is the only way anyone has found to permanently brick this phone.
the same thing happend today i was trying to flash eugene's new rom, and now it hangs in oden right here is as far as it goes:
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> cache.rfs
it doesn't move past that.
pm if you find a solution please.
cache.rfs
Was stuck at cache.rfs ... tried reinnstalling drivers... checked xp to make sure driver signing was ignored... I had no f8 option.. I tried again and again ... I had dl all 3 rar'ed from this thread
[ROM] OFFICIAL T-Mo Vibrant JFD ODIN/Nandroid Backup Images 7/29/10 (Tested/Working)
I was still stuck at cache.rfs after many many attempts..
then I downloaded just pit file from above thread and replaced old pit file with new one... both 1744 bytes ? maybe corrupted?...
I tried again and it worked )
basically following this
1. Put your phone in download mode by plugging it in and then holding Vol Up+Down and Power. As SOON as the screen goes black release power but NOT Vol Up+Down.
2. Launch Odin
3. Unplug your phone.
4. Load the pit and pda files into odin.
5. Plug your phone back in. You should now see one of the small blocks turn yellow and show you the com port. If not, something is wrong with your drivers.
6. Click start.
intructions after step 6 would not work
very scary but phone now back in operation
fb_hexedit said:
Was stuck at cache.rfs ... tried reinnstalling drivers... checked xp to make sure driver signing was ignored... I had no f8 option.. I tried again and again ... I had dl all 3 rar'ed from this thread
[ROM] OFFICIAL T-Mo Vibrant JFD ODIN/Nandroid Backup Images 7/29/10 (Tested/Working)
I was still stuck at cache.rfs after many many attempts..
then I downloaded just pit file from above thread and replaced old pit file with new one... both 1744 bytes ? maybe corrupted?...
I tried again and it worked )
basically following this
1. Put your phone in download mode by plugging it in and then holding Vol Up+Down and Power. As SOON as the screen goes black release power but NOT Vol Up+Down.
2. Launch Odin
3. Unplug your phone.
4. Load the pit and pda files into odin.
5. Plug your phone back in. You should now see one of the small blocks turn yellow and show you the com port. If not, something is wrong with your drivers.
6. Click start.
intructions after step 6 would not work
very scary but phone now back in operation
Click to expand...
Click to collapse
I can say this worked for me.
Thanks
Hi,
all day i used phone for messaging, listen music, but suddenly i got call from friend, and i answer phone freeze, i call him back, phone again freezen, i put battery out, and now phone don't boot, display show GALAXY S GT-I9000 - SAMSUNG.. but stay there.. I can't get to recovery, but i can access download mode.. What to do?
EDIT #1: when i put phone to charge, it display circle, but it doesn't start to charging battery.. at morning i used battery calibrate from google market.. but till now phone was working great.. but now don't even start:S..
Try factory reset on the recovery mode
DsMobile said:
Try factory reset on the recovery mode
Click to expand...
Click to collapse
i can't access recovery mode, cause it stuck on GALAXY S GT-I9000 image.. this first logo :S
If you are unable to use recovery mode, but can still use download mode you will have to flash a new firmware using ODIN or Heimdall.
Alternatively you could send it in for repairs if you feel like going the official route.
Remove battery replace battery and boot phone .
Remove battery go to three button recovery mode holding down buttons quickly insert battery and release buttons .
jje
JJEgan said:
Remove battery replace battery and boot phone .
Remove battery go to three button recovery mode holding down buttons quickly insert battery and release buttons .
jje
Click to expand...
Click to collapse
don't work.. did it almose 20 times..
Shanakin said:
If you are unable to use recovery mode, but can still use download mode you will have to flash a new firmware using ODIN or Heimdall.
Alternatively you could send it in for repairs if you feel like going the official route.
Click to expand...
Click to collapse
now i have installed XWJVK 2.3.3, now i will try to flash new rom xwjvb and will se if it's works
in odin i got only to this
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
then don't go nowhere
EDIT #1:
ok, in version odin v1.7 it move forward.. now we wait and see if it will work
solved with flash new rom
Help
I have the same problem with my galaxy S. can you tell me from point to point how can i solve this problem? thanks and wich program etc..
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.
I'm hoping someone can help me. I'm stuck travelling and my phone just crapped out. I'm not sure if it something to do with the ROM, but I was recording video and then all of a sudden the phone just rebooted and got stuck on the first screen. When I would normally reboot, i'd see a lock and it'd boot into the OS, but now it just says Samsung Galaxy s5 and its stuck.
I'm hoping someone can point me to the first step I need to do to recover it. I can't even get into recovery mode using the home key, power and volumen button. It just says Recovery Booting... and is just sitting there.
So I was able to get into Maintenace Mode. Not sure what to do from here to to recover or do a fresh install.
I REALLLLYY appreciate any help you guys can provide!!
Not sure if it matters, but i'm on the latest MOAR ROM (OC4)
If it's really that urgent, you might have to take it to the Verizon store #shudder#
Verizon won't do anything..I bought this off of craigslist.
So I've been successful at getting to the 'Downloading...' screen to make Odin work. I've so far flashed the NK2 Kernel successfully, but when I try to flash the NK2.tar I consistently fail:
<OSM> ALL_VZW_G900VVRU1ANCG_G900VVZW1ANCG_964333_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl1.mbn
<ID:0/007> rpm.mbn
<ID:0/007> tz.mbn
<ID:0/007> sdi.mbn
<ID:0/007> NON-HLOS.bin
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img.ext4
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I can't get past it, even after trying to flash different NXX .tars. I've tried two different computers, and different cables. I've tried Odin 3.10, 3.09 and 3.07
Suggestions please????
flashhsalf said:
Verizon won't do anything..I bought this off of craigslist.
Click to expand...
Click to collapse
That doesn't matter, if your service is through them, they can fix it.
I get the impression that it wasn't as urgent as you led to believe, since your initial post was days ago. You REALLY just wanted people to help you immediately...
ldeveraux said:
That doesn't matter, if your service is through them, they can fix it.
I get the impression that it wasn't as urgent as you led to believe, since your initial post was days ago. You REALLY just wanted people to help you immediately...
Click to expand...
Click to collapse
It was urgent at the time when I asked for help, but I got by using email to contact people that I needed because I had no choice.
I wasn't trying to dupe anyone to help me, I was in panic because I had no idea where to start while waiting for my flight. I didn't sit on my ass waiting for help either. I went and scoured the web for instructions on how to restore the phone and the last post is as far as I've gotten.
Thanks for your help btw.
flashhsalf said:
It was urgent at the time when I asked for help, but I got by using email to contact people that I needed because I had no choice.
I wasn't trying to dupe anyone to help me, I was in panic because I had no idea where to start while waiting for my flight. I didn't sit on my ass waiting for help either. I went and scoured the web for instructions on how to restore the phone and the last post is as far as I've gotten.
Thanks for your help btw.
Click to expand...
Click to collapse
Can you get to download mode to ODIN a ROM?
ldeveraux said:
Can you get to download mode to ODIN a ROM?
Click to expand...
Click to collapse
Yes, that is what i've been trying with Power+Vol Down+Home Key, I leave everything default and then add the .tar in the AP field. Few posts about other Samsung phones mention that i need to add some files in the BL, CP, CSC, field, but not sure if that applies to our S5.??
i've downloaded almost all of the Stock_Restore.tar files from this thread: (http://forum.xda-developers.com/showthread.php?t=2784880) and I've also tried the Stock_Retail.tar but they all fail at with the error in ODIN. After the error, I reboot but I can't get to the Samsung S5 screen. I get bootlooped into the ODIN screen saying firmware got corrupted, so with another attempts to reset, battery pull etc, I get to the normal ODIN screen and If I flash a Firmware, only then do I get to the Samsung S5 screen, but then nothing.
What I am not clear about is do I need to install the Retail Firmware or the Modem or the Kernel individually? Or do I just flash the Stock_Restore.tar as it has all of those files in it already.
Few times I was able to get ODIN to flash the rom tar without any errors not sure what changes I made, but it would then just sit on the Samsung Galaxy screen and not do anything.
Second time, I got Recovery Booting on the top left of the screen and then it'd just sit there. I tried to get into the Recovery Menu, but nothing would happen.
So I've just been trying to flash differnt combination of Firmware and stock Rom.tar files hoping something would stick, but i feel like i'm running in circles.
I've tried to get Kies 3 to work, but why samsung doesn't list the serial number on the S5 and then ask for it in their software is beyond me. I've tried Smart Switch, but it doesn't support our phone and i get stuck with the same are where I need the Serial Number. :/
You're in over your head, and for some reason, you refuse to go to the source to get this fixed. If you won't listen to advice on where to get help, I'm afraid I can't help you.
Which build were you running before the phone crashed? This may be applicable to you but you must have been on a build before BOC4.
Flash this. Unzip the file and you'll find a large file that ends in tar.md5
Open Odin (Doesn't matter which verion as long as it's higher than 3.09)
Click the button that says 'AP' and flash it.
Wait for the com-slot to go first blue then green and eventually say "PASS!!".
You should now have Stock NCG KitKat running on your SM-G900V
Quigly said:
Which build were you running before the phone crashed? This may be applicable to you but you must have been on a build before BOC4.
Flash this. Unzip the file and you'll find a large file that ends in tar.md5
Open Odin (Doesn't matter which verion as long as it's higher than 3.09)
Click the button that says 'AP' and flash it.
Wait for the com-slot to go first blue then green and eventually say "PASS!!".
You should now have Stock NCG KitKat running on your SM-G900V
Click to expand...
Click to collapse
I was on MOAR's OC4 ROM and i've tried what you have suggested and after I get the 'PASS!" and the system reboots, it never leaves the 'Samsung S5' screen. It'll stay there for hours. I then try to enter Recovery and I'll get the Recovery Booting on the top left of the screen in blue ..... and then it'll just stay there as well. I think something got corrupted and can't be overwritten with ODIN.
Where is the recover image located? In the bootloader? The menu which you see after you hit the Power + Vol UP+ Home?
Thanks for your suggestions, i do appreciate you trying.
ldeveraux said:
You're in over your head, and for some reason, you refuse to go to the source to get this fixed. If you won't listen to advice on where to get help, I'm afraid I can't help you.
Click to expand...
Click to collapse
Isn't everyone in over their head when they try to fix their phone for the first time with so much information scattered all over web forums and then multitude of exception about which rom and which firmware to install? Needless to say I took your advice and went to the Verizon store and they said what I excepted, Its not their problem, I need to take it to Samsung. I then found a Samsung support place at Best Buy and he pretty much said, because it said System Status: Custom , he can't plug it into his computer. So yea, not much help there, but thanks for your suggestions.
flashhsalf said:
Where is the recover image located? In the bootloader? The menu which you see after you hit the Power + Vol UP+ Home?
Thanks for your suggestions, i do appreciate you trying.
Click to expand...
Click to collapse
The recovery and boot.img files are in the ROM and/or tar.md5 package when you flash them.
Have you tried flashing the stock OC4 roms or just the firmware maybe?
When you flash a full tar.md5 with the MULTI CERT (bootloader FW) that should take care of your problem because that should overwrite any file system in place.
flashhsalf said:
I was on MOAR's OC4 ROM and i've tried what you have suggested and after I get the 'PASS!" and the system reboots, it never leaves the 'Samsung S5' screen. It'll stay there for hours. I then try to enter Recovery and I'll get the Recovery Booting on the top left of the screen in blue ..... and then it'll just stay there as well. I think something got corrupted and can't be overwritten with ODIN.
Where is the recover image located? In the bootloader? The menu which you see after you hit the Power + Vol UP+ Home?
Thanks for your suggestions, i do appreciate you trying.
Click to expand...
Click to collapse
Have you been able to resolve this issue or are you still stuck? I posted again to your questions just above this post. Basically what I'm saying is that you have a corrupt file that you're trying to flash or you have the incomplete version of the one you really need. This post http://forum.xda-developers.com/showthread.php?t=2784880 should steer you in the right direction if you still have quetions or you just PM me.
Make sure you're not trying to downgrade the bootloader. If you had BOE1 or later, an attempted flash of anything earlier than that will always fail because the bootloader was irrevocably locked.
You do not need to flash all of the components (modem, etc) in any combination. Just grab a full stock recovery image, and it contains everything you need. You can tweak with different modem versions later, but for right now focus on getting your phone working.
Make sure you're checking the md5 of the image you downloaded. A corrupted download will always fail to flash.
After successfully flashing with Odin, boot into stock recovery and clear the cache. If that doesn't work, boot back into stock recovery and also do "factory reset" to wipe out any remnants. (I wouldn't think this would do anything since flashing is supposed to wipe out everything, but it's worked for me on several occasions when stuck on the logo screen).
Read this to get yourself up to speed: http://forum.xda-developers.com/verizon-galaxy-s5/general/guide-painiacs-essential-guide-to-t3319848
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.