So, was working on flashing a custom ROM on my wife's phone (I've flashed phones countless times, even plenty with Odin), but after an issue flashing the Recovery, the phone wouldn't boot and would go straight to the Download every time. I've tried flashing a couple ROMs via Odin, but kept getting an odd message until I applied a PIT file. The phone booted back to how it was successfully.
Seems the Recovery is messed up though, so I need to try and fix that.
I tried to use Odin to apply a factory image, but it failed (see phone screenshot attached and Odin log below)
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_I545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low_ship_MULTI_CERT.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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<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> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Went to reboot back into the OS, but now it goes to "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." I tried this last night, but it said my phone was unsupported...
Ugh, finally convinced my wife to get a smart phone and now all of this...
You're trying to flash an MJ7 build. Is that the build you had when you started? I'm thinking you'll need to try the NC5 full wipe tar file with Odin.
The Verizon S4 is pretty locked down. Unless you have a phone with an MDK build, you will be extremely limited as to what you can do. Best to do a little research before you brick your phone permanently.
Sent from my NCC-1701 using Tapatalk.
I was able to get it to boot back to the prior running version after applying a .pit file (I thought that would have wiped everything)... Determined that it is FNC5 and flashed with that. It apparently didn't wipe the data, but I did a factory reset afterwards. I noticed though that now WIFI won't turn on... Really need to get this working well one way or another...
Interestingly enough, I have another of the same model phone that I haven't had any issues really with...
If I could just get a working recovery on it, I have a feeling I would be fine (I could just flash the same ROM as I have on my other phone AND make sure things are actually wiped!).
If I try to push about any recovery console via several methods, they all fail. Is it possible that the partition or something is messed up? Any sure fire way of fixing it (or a good route in the right direction)? I would LOVE to take this phone even back to 100% new phone, wiping out everything...
@riker147 MDK build? I don't see a version that had MDK in the version for my phone... SCH-I545 (Verizon)
MDK was a very early build.It was the only one that could have a custom recovery because of an exploit that was found. A later update fixed that exploit. (No, you can't revert to an earlier build) Now our only option for any type of recovery is Safestrap. Just be aware, Safestrap is very limited. Like I said earlier, best to do some research.
Sent from my NCC-1701 using Tapatalk.
Related
HI.
I had installed Odin and flashed the touch CWM 6 to my phone then I installed PureHD custom rom.
I noticed that the phone would reboot on its own every now and then.
But when it reboots, it just goes into a boot loop up to the logo , then reboots again.
Till I take out the battery, wait a little while , then re-insert the batter.
After that the phone will boot "normally" and would be functional for some time again.
I decided to change the Firmware, so i downloaded the cm-10.1-20130701-crDroid-build5-i9300.zip and install it.
That loaded fine for the most part.
I say that because when i try to use the sms application i noticed 2x since last night.
It does the same thing. It just reboots and get stuck at the logo once again.
Also I cannot copy items to my phone when its connected to my computer via the usb cable.
It tells me "cannot copy to device, either the device has either stopped responding or has been disconnected.
All this is very frustrating.
I am thinking about trying to load a stock rom via Odin to see if that will help.
Any ideas will be greatly appreciated.
Thanks..
Protorianbz
[READ THlS FlRST] POST QUESTIONS IN THE Q&A SECTION AND NOT HERE!!!!
Wipe phone and flash stock rom.
jje
I tried that.
I tried to isntall the STock rom.
It was installed via Odin successfully.
I saw the green Android man for a split second.
And phone just reboots, and now is stuck in the boot loop to the logo..
then reboots again..
This is the output form Odin 3.07
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXEMC3_I9300NEEEMC1_I9300XXEMB6_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> tz.img
<ID:0/003> NAND Write Start!!
<ID:0/003> sboot.bin
<ID:0/003> system.img
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> modem.bin
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
have you tried a hard reset? format data , cache and dalvik in recovery? after you successfully flashed stock rom? hope that helps
Try using MegaWipe from here: http://forum.xda-developers.com/showthread.php?t=1832326&page=31
and then flash a ROM.
Just don't forget to backup the Important stuff.
Just wipe phone and install stock rom
Sent from my GT-I9300 using xda premium
Thread moved to proper forum.
DiDA™ said:
Try using MegaWipe from here: http://forum.xda-developers.com/showthread.php?t=1832326&page=31
and then flash a ROM.
Just don't forget to backup the Important stuff.
Click to expand...
Click to collapse
^^ What s/he said...
You don't mention the word wipe so I figure you didn't do that. If you can't get into the phone you should do your battery-removal thing and let the phone get into the OS, then connect USB and copy out the files you need to save. If you've got a backup to your extSDcard that would be helpful - you can always restore data from an advanced CWM Restore setting.
Copy the ROM you want across to the estSDcard using USB
Download megawipe, copy it to estSDcard and flash it in CWM.
Flash your ROM and restart phone, Set it up and once done, then start adding apps and restoring data, THEN make a full backup.
As a rule, the only time you do not do a full wipe of your phone is when you are flashing a point upgrade. i.e. going from AbcROM 7.1 to AbcROM 7.2 - if you are changing ROMs or doing a full step upgrade (AbcROM 7.x to AbcROM8.x) you need to do a full wipe to avoid problems.
So I think I may have bricked my Samsung GS4. This is what I did.
I had previously been rooted with TWRP custom recovery partition. I did the new update (I know, I know). Surprise surprise my root access was gone ans so was the recovery partition. Now I have none at all. I wanted to flash the new Google play edition ROM onto the S4 so I went about re-rooting using the root exploit method and a microsd card.
The root went fine and I gained access again. Here is where I messed up though. I tried to re-install the TWRP recovery partition using goo manager. The install went fine, but when I rebooted the phone I got an error message and was sent straight into Odin mode. ****. Phone won't boot at all except into this mode.
I then went to my PC and attempted to re-install the MDK tar file to re-flash. Didn't work. I got a firmware error upgrade error message and advice to recovery using Kies. I tried this. Kies could not locate my device on the USB drive. (I'm using the stock cable mind you). I then did some searching on here and found out that I needed to use the ME7 tar file in odin. You can't flash back. I did this. I got an error:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> COMBINATION_I545VRUAME7_I545VZWAME7_690088_REV06_user_low_ship_MULTI_CERT.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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Can't open the specified file. (Line: 1949)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
The highlighted in red is where things went wrong I suspect but I didn't know what to do after that. I went on to try the "OneClick unbrick" method from there.
I put into odin mode and using the soft unbrick and I got an error claiming my device has not been plugged in. Now I have all the device drivers so I'm not sure what the problem could be is. Any help or suggestions? I called verizon and they're sending me another S4 but I'll be phone less until tuesday. In the mean time if I can figure out how to fix this I would much rather do that then deal with possibly be found out of voiding my warranty.
Thanks,
Dolph
Dolphlungegrin said:
So I think I may have bricked my Samsung GS4. This is what I did.
I had previously been rooted with TWRP custom recovery partition. I did the new update (I know, I know). Surprise surprise my root access was gone ans so was the recovery partition. Now I have none at all. I wanted to flash the new Google play edition ROM onto the S4 so I went about re-rooting using the root exploit method and a microsd card.
The root went fine and I gained access again. Here is where I messed up though. I tried to re-install the TWRP recovery partition using goo manager. The install went fine, but when I rebooted the phone I got an error message and was sent straight into Odin mode. ****. Phone won't boot at all except into this mode.
I then went to my PC and attempted to re-install the MDK tar file to re-flash. Didn't work. I got a firmware error upgrade error message and advice to recovery using Kies. I tried this. Kies could not locate my device on the USB drive. (I'm using the stock cable mind you). I then did some searching on here and found out that I needed to use the ME7 tar file in odin. You can't flash back. I did this. I got an error:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> COMBINATION_I545VRUAME7_I545VZWAME7_690088_REV06_user_low_ship_MULTI_CERT.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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Can't open the specified file. (Line: 1949)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
The highlighted in red is where things went wrong I suspect but I didn't know what to do after that. I went on to try the "OneClick unbrick" method from there.
I put into odin mode and using the soft unbrick and I got an error claiming my device has not been plugged in. Now I have all the device drivers so I'm not sure what the problem could be is. Any help or suggestions? I called verizon and they're sending me another S4 but I'll be phone less until tuesday. In the mean time if I can figure out how to fix this I would much rather do that then deal with possibly be found out of voiding my warranty.
Thanks,
Dolph
Click to expand...
Click to collapse
Solved.
Fix:
Resinstalled Odin (wouldn't let me run as administrator before. Reinstalled Me7 from zip (extracted). Booted up Odin. Unchecked repartion. and voila. It re-flashed successfully.
Question:
Is there a way to install custom ROMs on this with the ME7 bootloader? I want to install the Google Play edition port, but everything I see suggest using TWRP or the Clockwork Recovery Mod. Since these can't be loaded onto Me7. How does one do this? Via a .tar in Odin?
i had the same problem. if your just trying to get unbricked i can help. (warning i am extremely new at all this). so i did the update and ever since had been trying to get root access and flash a custom ROM. i too tried to install twrp through goo manager. i kept bricking my device by trying to boot into recovery. i found out that if do a battery pull, and hold the volume down and power button (booting into recovery) but dont let go until a warning page comes up. it should warn you about installing custom roms and give you the option of continuing by pressing the volume up button, or pressing the volume down to reboot. choose to reboot and you should be back to nromal. hopes this helps and was what you where looking for.
Dolphlungegrin said:
Solved.
Question:
Is there a way to install custom ROMs on this with the ME7 bootloader? I want to install the Google Play edition port, but everything I see suggest using TWRP or the Clockwork Recovery Mod. Since these can't be loaded onto Me7. How does one do this? Via a .tar in Odin?
Click to expand...
Click to collapse
There is currently no way to install a different rom after taking the ME7 update. You cannot go back to MDK either.
Sent from my SCH-I545 using Xparent Skyblue Tapatalk 2
Yo Guys! I think my bootloader was already updated, and I tried to flash back to original 4.3 or 4.1.2, but nothing of it worked.
When I try to flash f.e. the
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXEMR2_I9300VFREMA3_I9300BUEMA1_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> tz.img
<ID:0/003> NAND Write Start!!
<ID:0/003> sboot.bin
<ID:0/003> system.img
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can someone please help me I was on CM 10.2/CM11 and wanted to restore factory images, because my Audio Plug-In didnt work properly anymore and my screen had some pixel errors.
I tried to flash a CWM touch recovery, but that did work only once - then flashed the bootloader downgrade Restore_Bootloader_XXBLFB.zip, but
I still couldnt flash any factory firmware
I also tried this here:
http://forum.xda-developers.com/showthread.php?t=2083860
Tried method 2 of that one, didnt get me in position to install the stock firmware.
Does anyone have any advice?
I still can enter CWM (or install it) and can enter Download Mode
I tried 4.3, 4.1.2 and 4.0.4 , nothing worked
Update #1 I could reflash cyangenmod over cwm again and my cell works too. *phew*
How do I get back to stock rom? Meanwhile I'll try mobile odin
update #2
mobile odin worked, got back to stock. just letting u know.
Have you tried another version of ODIN? I used to have some issue with version 3.0 and above. So it seems that version 1.8.5 is more stable that the new ones... try redownload your ROM, maybe it has some issues too.
Finally, use SAMSUNG SG3 TOOLKIT, I have used that too and without any issue.
Good Luck
:cyclops:
froycard said:
Have you tried another version of ODIN? I used to have some issue with version 3.0 and above. So it seems that version 1.8.5 is more stable that the new ones... try redownload your ROM, maybe it has some issues too.
Finally, use SAMSUNG SG3 TOOLKIT, I have used that too and without any issue.
Good Luck
:cyclops:
Click to expand...
Click to collapse
Read post above you
I tried Version 1.85 and 3.09, both didn't work. But thanks to Chainfire for developing this awesome tool :laugh::good:
mobile odin got my phone finally flashed
Hey everyone,
I tried updating my Verizon Galaxy S4 to Lollipop via Samsung Kies. The update process produced an error message (at app. 10%) and offered me to start the recovery process, which failed subsequently. Needless to say, Android OS does not work, however I can still boot into download/recovery mode.
I've been trying to flash various stock ROMs via Odin 3.10 with no success. The build numbers of the ROMs I've been trying to flash contained the I545VRUFNC5 number, since I tried preserving compatibility with the previous (Stock) ROM that had the same build number. Prior to flashing Lollipop via Kies, I made the made a screenshot (attached below) in case I ran into some kind of trouble. It contains the Model/Build of my S4.
I've also tried using a PIT file during the flashing process with no success.
The error message Odin gives me always reads:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUFNC5_I545VZWFNC5_I545VRUFNC5_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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<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> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
The main question is whether I need to stick to build I545VRUFNC5 to reflash. If not, which Stock ROM am I able to Install via Odin without bricking the phone further
For exact phone model/specs pls open the screenshot below. I would also be very grateful if someone could provide me a stock ROM (name/link/version) that I could flash via Odin to resolve the mess Kies and I created.
Any help is much appreciated.
Thanks in advance.
Make sure to get FULL WIPE AND REPARTITION. All data will be lost..
XxD34THxX said:
Make sure to get FULL WIPE AND REPARTITION. All data will be lost..
Click to expand...
Click to collapse
Thanks for the reply. Sadly, I don't have a custom recovery flashed on my phone. I already tried flashing TWRP and the process resulted in a similar error message as described above (auth fail/error). I've already performed a factory reset via the stock recovery, so the data is already gone
intel.fan said:
Thanks for the reply. Sadly, I don't have a custom recovery flashed on my phone. I already tried flashing TWRP and the process resulted in a similar error message as described above (auth fail/error). I've already performed a factory reset via the stock recovery, so the data is already gone
Click to expand...
Click to collapse
Bad mistake to do TWRP. With reading, you would have known that TWRP is restricted to MDK... Safestrap(@hashcode) is what you have to use. Or Flashfire(@chainfire) or the New Multisystem tool by @hsbadr... Use Odin, get the zip, and flash it in the PDA( or AP) slot. I fixed my friend's when he did that, but he got lucky...
XxD34THxX said:
Bad mistake to do TWRP. With reading, you would have known that TWRP is restricted to MDK... Safestrap(@hashcode) is what you have to use. Or Flashfire(@chainfire) or the New Multisystem tool by @hsbadr... Use Odin, get the zip, and flash it in the PDA( or AP) slot. I fixed my friend's when he did that, but he got lucky...
Click to expand...
Click to collapse
No mate, since the bootloader seems to be locked. It simply didn't flash TWRP - the stock bootloader is still present and running. Trying to flash TWRP was kind of a desparate measure, since I don't have OS access to flash/install any of the above. Also, my phone was 100% stock Kitkat 4.4.2 with no root access
Resolved the issue! =)
The problem was in that the Lollipop update process had already been started (unsuccessfully), Odin was "seeing" the flash process as a downgrade - so it wouldn't allow it.
I tried flashing a stock Lollipop ROM via Odin and it worked like a charm
Thanks for your support.
@mods: Please close/archive this thread.
Hi guys. I have a galaxy s6 that I tried to flash with official firmware 5.1.1 via odin. I was rooted before that. The flash failed and now it says to use Verizon's software utility to restore the phone. That utility doesn't work and the reps at the store had never heard of it.I literally can't fix the thing. No amount of flashing in download mode helps. It always fails.
Anyway, I went to Verizon and they are sending me a replacement in two days. In download mode it still says that the firmware is official. However it also says samsung custom. (Assuming the root) I don't know if Verizon will backcharge me for this. Is there any way to get rid of the custom status? When I put it in the box to return it I'll leave it on the System Software Update Failed screen.
Remember I can't flash via odin, that just fails. Samsung smartswitch doesn't recognize the device. Recovery mode is a no go.
Thanks for the help!
What's the error message in Odin?
Official 5.1.1? It's possible you were trying to flash a lower build....on 5.1.1, you've got to try flashing the same build or higher, it's possible verizon added a downgrade lock
es0tericcha0s said:
What's the error message in Odin?
Click to expand...
Click to collapse
in seems to always fail. I can go back to download mode or be instructed to restore via Verizon's software assistant. Here is what odin has to say. It fails at the system.img Verizon G920V
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> cm.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
mrao said:
Official 5.1.1? It's possible you were trying to flash a lower build....on 5.1.1, you've got to try flashing the same build or higher, it's possible verizon added a downgrade lock
Click to expand...
Click to collapse
I was not on 5.1.1 at the time. I downloaded 5.1.1 from sammobile or one of the other firmware hosting sites. I also tried 5.0.2 but that gives me a nand error.
Would perhaps flashing a pit file work? The problem is the the one firmware I originally tried to flash (5.1.1) doesn't have a pit file. The other firmware 5.0.2 does have one but it's only 4kb. I'm not sure if that's right.
Just in case anyone finds this in the future. I figured out how to fix this. I had have a working phone to install verizon's upgrade assitant. It would not work from the exe I found on the internet. From there I had to install it in a virtual machine because it did not like Win 10. From there I simply plugged in my device and it restored it. Use this method if odin doesn't work. I WILL NEVER ROOT AGAIN!
So because you had an issue with your computer, you won't root again? Not sure I understand that, but glad you got it fixed.
es0tericcha0s said:
So because you had an issue with your computer, you won't root again? Not sure I understand that, but glad you got it fixed.
Click to expand...
Click to collapse
Odin failed a flash and I could not reflash with odin again. I don't ever want to have that happen again. It wasn't the firmware I triple verified it before I flashed it. It was the correct firmware.