I'm interested in rooting my new Galaxy S4 but I also would like the original stock rom in case if I ever need to go back to it. Would anyone by any chance have the original stock ROM?
Model: SCH-I545
Android Version: 4.2.2
*If any other details are needed, let me know.
This is a Verizon phone fyi.
Also, could someone please link me to a tutorial/guide for rooting the S4 and some other links that have ROMs that are a "must-get".
Thanks,
Hydra
Read the development forums. The stock image is ready enough to find, as are step by step root instructions. As to your last question, that is the type of thing that gets a thread locked. Read the dev forums, pick a few roms that pique your interest, and give them a test drive.
Sent from my Nexus 7 using Tapatalk HD
najaboy said:
Read the development forums. The stock image is ready enough to find, as are step by step root instructions. As to your last question, that is the type of thing that gets a thread locked. Read the dev forums, pick a few roms that pique your interest, and give them a test drive.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I'm new here so tried my best to find the correct section, and did search for guides.
I'm currently using this guide, http://forum.xda-developers.com/showthread.php?t=2290798 , but upon flashing the prerelease kernal, it failed.
http://i.imgur.com/MjbRPrK.png
Also, in case of anything, how can I leave ODIN mode on the phone? Do I just power it off and reboot?
CM10.1 has been treating me pretty well. Haven't had any crashes or anything and runs fast and stable.
The only issue I noticed is you can't get a GPS lock while Network & Wireless location is on. Once you disable it GPS locks right in.
Sent from my SCH-I545 using Tapatalk 2
I now have a huge problem. I'm at the screen: Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. Need to resolve this as soon as possible.
HydraS4 said:
I now have a huge problem. I'm at the screen: Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. Need to resolve this as soon as possible.
Click to expand...
Click to collapse
Go to this guide and download the .tar image to be used in Odin http://forum.xda-developers.com/showthread.php?t=2301259. Boot into Odin mode following this guide http://forum.xda-developers.com/showthread.php?t=2290771. Follow all the instructions exactly and ask questions here if you have any.
Ryno77 said:
Go to this guide and download the .tar image to be used in Odin http://forum.xda-developers.com/showthread.php?t=2301259. Boot into Odin mode following this guide http://forum.xda-developers.com/showthread.php?t=2290771. Follow all the instructions exactly and ask questions here if you have any.
Click to expand...
Click to collapse
The tar file is 1.8 Gbs, is this the only method? I have horrible download speed and going to take 3 hours to download it.
Btw, can someone educate me on what just happened? Did I brick my phone? Will I lose any data?
Thanks,
Hydra
HydraS4 said:
The tar file is 1.8 Gbs, is this the only method? I have horrible download speed and going to take 3 hours to download it.
Btw, can someone educate me on what just happened? Did I brick my phone? Will I lose any data?
Thanks,
Hydra
Click to expand...
Click to collapse
Can you get into regular android recovery?
Ryno77 said:
Can you get into regular android recovery?
Click to expand...
Click to collapse
Nope, I'm working on trying Samsung Kies, maybe that will do it but I tried to get into recovery mode thru the phone but takes me to that same window.
I'm also downloading the stock firmware.
Did you try just flashing the stock kernel back using Odin? Everything you've done is listed in this thread, right? Technically if you tried to flash the pre release kernel and it failed nothing should have happened.
Ryno77 said:
Did you try just flashing the stock kernel back using Odin? Everything you've done is listed in this thread, right?
Click to expand...
Click to collapse
No, I haven't. Is that the one in the guide? If so, I'll do it soon. I have to go out, and now without a phone so going to be a problem for me.
Thanks for the quick support btw, appreciate it.
HydraS4 said:
No, I haven't. Is that the one in the guide? If so, I'll do it soon. I have to go out, and now without a phone so going to be a problem for me.
Thanks for the quick support btw, appreciate it.
Click to expand...
Click to collapse
I don't know if it will work but it's worth trying. The stock Odin should definitely fix your problem though. Yes it's in the thread.
Ryno77 said:
I don't know if it will work but it's worth trying. The stock Odin should definitely fix your problem though. Yes it's in the thread.
Click to expand...
Click to collapse
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SCH-I545_MDK_562219_Kernel.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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
Is what I get upon flashing kernel to the stock kernel. I am downloading the stock ROM as I type this. 1 Hour left to download it. Btw, does it matter what type of ROM I download?
Is there a difference from, http://www.rwilco12.com/downloads.p...Galaxy S4 (Verizon) (SCH-I545)/Stock ROMs/TAR and http://forum.xda-developers.com/showthread.php?t=2301259 ?
I'm guessing it's the No Wipe feature?
And what's the worst case scenario with rooting the phone? Anything permanent? If this stock ROM fixes the current problem, then I'll attempt to root once more.
Thanks,
Hydra
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> VRUAMDK_NoWipe.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Removed!!
<ID:0/003> Added!!
<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> Removed!!
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Added!!
What is the PIT partition? Is that my internal storage?
Are you using the factory charging cable to connect to the computer? I don't know why everything keeps failing.... Odin has never failed for me. Do you have another computer you can try this on? Stock charging cable, different usb port or another computer are the things I would try next. I don't know anything about pit files.
Sent from my SCH-I545 using xda premium
Ryno77 said:
Are you using the factory charging cable to connect to the computer? I don't know why everything keeps failing.... Odin has never failed for me. Do you have another computer you can try this on? Stock charging cable, different usb port or another computer are the things I would try next. I don't know anything about pit files.
Sent from my SCH-I545 using xda premium
Click to expand...
Click to collapse
Tried two types of cables, a generic one and factory/original one. I tried two different computers with 2 different OS. Tried 3 different ports per computer.
Don't know what else I can do.
Since you're able to boot into Odin mode I think this can be fixed but it may require a pit file. Since I know nothing about pit files or why Odin kept failing for you I'm going to let someone else try and help you. I do not think your phone is beyond hope at this point. Good luck.... I hope someone chimes in with the help you need.
Sent from my SCH-I545 using xda premium
Ryno77 said:
Since you're able to boot into Odin mode I think this can be fixed but it may require a pit file. Since I know nothing about pit files or why Odin kept failing for you I'm going to let someone else try and help you. I do not think your phone is beyond hope at this point. Good luck.... I hope someone chimes in with the help you need.
Sent from my SCH-I545 using xda premium
Click to expand...
Click to collapse
Alright, I appreciate all the help. Thanks!
Hopefully someone can help me out before I head over to Verizon later today.
HydraS4 said:
Alright, I appreciate all the help. Thanks!
Hopefully someone can help me out before I head over to Verizon later today.
Click to expand...
Click to collapse
Yeah, no problem. I'm sorry nothing worked for you.
Sent from my SCH-I545 using xda premium
Does anyone know if Verizon will replace it if it isn't my fault? There is no proof of rooting just a messed up system.
Related
Hey guys,
First up, this is what I was running.
-Samsung Galaxy S3 GT-I9300
-FCC ID: A3LGTI9300A
-SSN: -I9300GSMH
-RootBox v3.8
So I installed RootBox v3.8 a few weeks ago and the update for v3.9 appeared on my phone along with the GAPPS update. I made the mistake of ONLY flashing the first update. So when my phone rebooted it kept on giving me the error 'Android.process.acore has stopped unexpectedly'. I was forced to then revert back to v3.8 and everything seemed peachy. Up until the other night where I turned on my phone and it showed, 'Firmware upgrade encountered an issue. Please select recovery mode in kies and try again'. I accessed 'Download Mode' and tried to flash my stock rom back on but it failed in ODIN and gave me this error.
'<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXEMA2_I9300OPSEMA1_I9300XXELLA_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> boot.img
<ID:0/007> NAND Write Start!!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<ID:0/007> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/007> Removed!!'
Also if I switch on my phone, this is what appears, I can still access 'Download Mode'. Any help would be greatly appreciated.
AW: [Q] [HELP] Soft-Bricked Galaxy S3-I9300
Baraa01 said:
Hey guys,
First up, this is what I was running.
-Samsung Galaxy S3 GT-I9300
-FCC ID: A3LGTI9300A
-SSN: -I9300GSMH
-RootBox v3.8
So I installed RootBox v3.8 a few weeks ago and the update for v3.9 appeared on my phone along with the GAPPS update. I made the mistake of ONLY flashing the first update. So when my phone rebooted it kept on giving me the error 'Android.process.acore has stopped unexpectedly'. I was forced to then revert back to v3.8 and everything seemed peachy. Up until the other night where I turned on my phone and it showed, 'Firmware upgrade encountered an issue. Please select recovery mode in kies and try again'. I accessed 'Download Mode' and tried to flash my stock rom back on but it failed in ODIN and gave me this error.
' Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
I9300XXEMA2_I9300OPSEMA1_I9300XXELLA_HOME.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin v.3 engine (ID:7)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
boot.img
NAND Write Start!!
Complete(Write) operation failed.
Added!!
All threads completed. (succeed 0 / failed 1)
Removed!!'
Also if I switch on my phone, this is what appears, I can still access 'Download Mode'. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Heya!
Your SIII looks bad with this stripes!
Have you flashed your StockROM via Odin while you were in DownloadMode? If it don't be in DownloadMode, it also can't be flashed.
Try to download a firmware from samfirmware.com and to flash it via Odin in the PDA field while your device is in DownloadMode!
And when you have finished, go to Recovery and Wipe your Data&Cache!
Greetings...
Sent from my GT-I9300 using xda app-developers app
Of course I used ODIN to flash stock rom, it didn't work.
AW: [Q] [HELP] Soft-Bricked Galaxy S3-I9300
Of course I used ODIN to flash stock rom, it didn't work.
Click to expand...
Click to collapse
Sorry that I ask, but have you flashed it in Downloadmode?
Sent from my GT-I9300 using xda app-developers app
TheRealFelix0212 said:
Sorry that I ask, but have you flashed it in Downloadmode?
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
If you read my first post, yes, I did flash it in Download Mode via ODIN.
Well, it obviously had a problem writing the rom into the phone (nand write failed). You may have a hardware fault. Do you have the nand chip that suffers from sds?
Sent from my GT-I9300 using xda premium
I've had similar issues before, not that exact screen, but issues with Odin. It worked eventually.
Try Odin3 v.1.85 from here (CF-Auto-Root thread).
Next, be sure you got a valid file, those from sammobile (Choose your country for).
Next, use only PDA button, nothing else, make sure it's the same settings as in root thread above.
Also make sure all Kies processes are closed.
Now, try until it works. It might take a few tries. This is what worked for me, hope it does for you too.
ratatattata said:
I've had similar issues before, not that exact screen, but issues with Odin. It worked eventually.
Try Odin3 v.1.85 from here (CF-Auto-Root thread).
Next, be sure you got a valid file, those from sammobile (Choose your country for).
Next, use only PDA button, nothing else, make sure it's the same settings as in root thread above.
Also make sure all Kies processes are closed.
Now, try until it works. It might take a few tries. This is what worked for me, hope it does for you too.
Click to expand...
Click to collapse
Still failed in ODIN. You reckon the eMMC chip is damaged?
Baraa01 said:
Still failed in ODIN. You reckon the eMMC chip is damaged?
Click to expand...
Click to collapse
That's what it sounds like keep trying to flash, try a different usb cable and computer if you can. Also remove any sim or sd card.
Also maybe the partition table is messed up but emmc is Ok?
Sent from my GT-I9300 using xda premium
jmpmjmpm said:
That's what it sounds like keep trying to flash, try a different usb cable and computer if you can. Also remove any sim or sd card.
Also maybe the partition table is messed up but emmc is Ok?
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Same isssue here, same screen and everything.... I tried for over a month and nothing... got an expensive door steep. If you have any lights about this... let me know!!
try flashing recovery only and then flash 3.8 again through recovery.
try flashing the resurrection rom from the checkrom site through odin in download mode..
galaxys3lover said:
try flashing the resurrection rom from the checkrom site through odin in download mode..
Click to expand...
Click to collapse
Been there, done that. Nothing happens. Same error, Re-Partition failed.
please help?
-Samsung Galaxy S3 GT-I9300
-FCC ID: A3LGTI9300A
-SSN: -I9300GSMH
I hope I've not ended up with this phone mentioned in this thread....purchased a phone from ebay and the seller said its stuck on Android SIII logo...I can get into download mode but before I attempt anything can someone tell me if this is a UK phone so I can apply the correct ROM (if it works!).
Also, currently the phone does not charge, battery is fine as i've tried the battery from own s3 and vice versa...both batteries are fine but the phone does not appear to charge...I'm hoping this is ROM related....
Any help will be much appreciated otherwise its an expensive gamble!
BTW...In the download mode the product bit is blank and does not say Samsung galaxy s3 like my own working phone does...
My verizon note 2 is stuck in the boot screen that shows SAMSUNG GALAXY NOTE II. It just keeps FLASHING every 2-3 seconds.
Odin keeps failing, Ive already done the root yesterday and installed a rom and than i got a samsung update and it downloaded and went into installing it which all went well. But when it restarted I got stuck as mentioned above.
Please advice me on what to do. I'm not new to odin and I have flashed the gn2 yesterday to original formware but today it just fails????
Please help with ideas. THANKS
How about a batttery pull. Then hold power home and up key and see if u have custom recovery and if so then do a restore of your back up. Or just flash another rom.
Sent from my SCH-I605 using xda premium
Sent from my SCH-I605 using xda premium
highwaybandit said:
How about a batttery pull. Then hold power home and up key and see if u have custom recovery and if so then do a restore of your back up. Or just flash another rom.
Sent from my SCH-I605 using xda premium
Sent from my SCH-I605 using xda premium
Click to expand...
Click to collapse
As i do that the logo keeps flashing every 2-3 seconds and nothing ever happens.
I this because of the logo words are flashing nothing works when I try to do the normal/usual restore tricks.
If the logo words would stay still/freeze in place I would be golden. But as they just keep flashing I cant do nothing.
This is one serious problem Im thinking. Anyone that gets me out of this is a GENIUS, PURE GENIUS!!
JasjarMan said:
My verizon note 2 is stuck in the boot screen that shows SAMSUNG GALAXY NOTE II. It just keeps FLASHING every 2-3 seconds.
Odin keeps failing, Ive already done the root yesterday and installed a rom and than i got a samsung update and it downloaded and went into installing it which all went well. But when it restarted I got stuck as mentioned above.
Please advice me on what to do. I'm not new to odin and I have flashed the gn2 yesterday to original formware but today it just fails????
Please help with ideas. THANKS
Click to expand...
Click to collapse
Can you boot into download mode (power, home, vol. down), then flash a new rom through your computer? I'd start with rom, then if that doesn't work try flash a new recovery.
AndroidSurman said:
Can you boot into download mode (power, home, vol. down), then flash a new rom through your computer? I'd start with rom, then if that doesn't work try flash a new recovery.
Click to expand...
Click to collapse
I can but like I mentioned odin fails. Heres what I get:
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
JasjarMan said:
I can but like I mentioned odin fails. How do I flash a RECOVERY?
Click to expand...
Click to collapse
Download a custom recovery zip from TWRP, If you used odin, just boot into download, and flash through odin.
Edit: I didn't realize odin was failing. Scratch that.
Three things we need more info about how Odin is failing, but I have a guess it says sboot then fails. So in that case go here
http://forum.xda-developers.com/showthread.php?p=35265728
Get the alternate restore and use that in Odin. Or you could try the pit file, some day that fixes them up. Second had you read at all or looked in the stickies you would have got that answer in 10 seconds. Third, and finally never post in development until you develop something. Especially when you're getting help here, that's spam and can get you banned, plus normally I and others will not help you for that.
Sent from my SGH-T889 using xda app-developers app
kintwofan said:
Three things we need more info about how Odin is failing, but I have a guess it says sboot then fails. So in that case go here
http://forum.xda-developers.com/showthread.php?p=35265728
Get the alternate restore and use that in Odin. Or you could try the pit file, some day that fixes them up. Second had you read at all or looked in the stickies you would have got that answer in 10 seconds. Third, and finally never post in development until you develop something. Especially when you're getting help here, that's spam and can get you banned, plus normally I and others will not help you for that.
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
- I tried the pit no go.
- who said I did not look at the stickies?Maybe I should have mentioned that I did.
I did do as what was said in that link the first day I but my phone and it DID work.
Now it does not work and thats why I was asking her for help.
- I cant believe posting here is SPAM but ok I should have know better.
- Glad I got help regardless, thanks to everyone.
But I still have the issue.
JasjarMan said:
- I tried the pit no go.
- who said I did not look at the stickies?Maybe I should have mentioned that I did.
I did do as what was said in that link the first day I but my phone and it DID work.
Now it does not work and thats why I was asking her for help.
- I cant believe posting here is SPAM but ok I should have know better.
- Glad I got help regardless, thanks to everyone.
But I still have the issue.
Click to expand...
Click to collapse
No posting the same question in multiple spots is spam. You still haven't said what Odin says when it fails. Saying it fails helps no one help you
Sent from my SGH-T889 using xda app-developers app
kintwofan said:
No posting the same question in multiple spots is spam. You still haven't said what Odin says when it fails. Saying it fails helps no one help you
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
post #5 I pasted this:
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
And this:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW-Rev0406_low_ship_user.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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
JasjarMan said:
And this:
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW-Rev0406_low_ship_user.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin v.3 engine (ID:3)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
boot.img
NAND Write Start!!
Complete(Write) operation failed.
Added!!
All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Much better, but it looks like you still didn't do what I said and you didn't read the stickies so...
Sent from my SGH-T889 using xda app-developers app
Try that out and see if it works, I'm going to bed so post your results
Sent from my SGH-T889 using xda app-developers app
kintwofan said:
Try that out and see if it works, I'm going to bed so post your results
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Will do. THANKS!
JasjarMan said:
Will do. THANKS!
Click to expand...
Click to collapse
So since you're not posting a bunch I'm assuming this fixed you? You can at least stop in to say it worked and thank the people who spent there time helping you
Sent from my SGH-T889 using xda app-developers app
Hello,
I have a problem unrooting/unbricking my Galaxy S4 for Verizon. I followed step-by-step processes and it seems to not work properly for me. I downloaded "Odin3 v.1.85" and the stock firmware, "GalaxyS4/SCH-i545/VRUAMDK_NoWipe.tar.zip" and "SCH-I545_MDK_562219_Stock_Restore.tar.md5" for Verizon. I put my phone into the Download Mode and began the process of unrooting using Odin. I made sure that my device was connected. I clicked PDA and chose the stock firmware for my phone. I clicked Start and it begins. As soon is it begins, it says it is not responding, but I wait a few seconds and it responds. After that, it continues where it left off for the unrooting process. The process turned out to be a fail. Here's the message:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> VRUAMDK_NoWipe.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NON-HLOS.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> aboot.mbn
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
It has failed and when I attempt to reboot my phone, it gives me a message that says, "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." I attempted the Kies process, and it would not connect my device to Kies. Please help. I feel as if I were the only user with this problem. Thank you.
sounds like you were already on v7 baseband try getting that stock image and go through odin.
because you cant go back to the original baseband (which is the md5 you listed) but I had similiar issues.
goosedaddy said:
sounds like you were already on v7 baseband try getting that stock image and go through odin.
because you cant go back to the original baseband (which is the md5 you listed) but I had similiar issues.
Click to expand...
Click to collapse
Seems like it's tough luck for me. What do you suggest I do? Did you resolve any of your similar issues?
yep. I only wanted to make sure you did install the update or otherwise some of the 32gb s4 come with it preinstalled.
just saying this because updating to me7 is irreversible you wont be able to flash roms right now only apply a root
download the me7 md5 this time and do all the same steps I followed this guide
http://forum.xda-developers.com/showthread.php?t=2301259
hope this helps
goosedaddy said:
yep. I only wanted to make sure you did install the update or otherwise some of the 32gb s4 come with it preinstalled.
just saying this because updating to me7 is irreversible you wont be able to flash roms right now only apply a root
download the me7 md5 this time and do all the same steps I followed this guide
http://forum.xda-developers.com/showthread.php?t=2301259
hope this helps
Click to expand...
Click to collapse
Alright. I'll follow these steps and I'll get back to here and let you know. Thank you.
I'm in the process of downloading the ME7 you told me about, but isn't this rooting my phone? I want to reformat my phone and have everything wiped out.
MattLife said:
I'm in the process of downloading the ME7 you told me about, but isn't this rooting my phone? I want to reformat my phone and have everything wiped out.
Click to expand...
Click to collapse
nope its a stock image so everything will be like when you first got it. not sure if some data will be there but you will not be rooted.
the root process is here http://forum.xda-developers.com/showthread.php?t=2381382
goosedaddy said:
nope its a stock image so everything will be like when you first got it. not sure if some data will be there but you will not be rooted.
the root process is here http://forum.xda-developers.com/showthread.php?t=2381382
Click to expand...
Click to collapse
This really helped me! Thank you so much! It's been fixed.
MattLife said:
This really helped me! Thank you so much! It's been fixed.
Click to expand...
Click to collapse
Awesome! Glad it all worked out.
help
Trying to unroot and revert to stock and I have soft bricked my galaxy s4! The charging port is gone so I cannot use a computer to fix this...I have searched everywhere for help and am stuck! Anyone have any suggestions???
gregorykbrownjr said:
Trying to unroot and revert to stock and I have soft bricked my galaxy s4! The charging port is gone so I cannot use a computer to fix this...I have searched everywhere for help and am stuck! Anyone have any suggestions???
Click to expand...
Click to collapse
if you can't get the usb port (charging port) to work with communicating to your computer then there really isn't much you can do. Have you tried cleaning the contacts off inside the port? Are you sure its NOT the cable?
This has been talked about somewhere else here in this forum
Same problem
goosedaddy said:
sounds like you were already on v7 baseband try getting that stock image and go through odin.
because you cant go back to the original baseband (which is the md5 you listed) but I had similiar issues.
Click to expand...
Click to collapse
Hey I have the exact same issue but with the international LTE galaxy s4 do you have any idea what i can do i have put the GPE rom on this and i found that flashing TWRP when it gave me the kies error bought me back to my GPE rom i'm going to sell this phone and i need to return to stock firmware should i try a new computer or something else please help me i've been really scared, i would appreciate it if you can help me in any way.
I tried to flash SCH-I545_MD2_423399_Kernel.tar onto my Galaxy S4, and it said boot.img Fail. I have a SCH I545 and I have been looking everywhere for a fix but this is sort of a last resort. Does anyone know what do to? Thanks in advance.
Incaendium said:
I tried to flash SCH-I545_MD2_423399_Kernel.tar onto my Galaxy S4, and it said boot.img Fail. I have a SCH I545 and I have been looking everywhere for a fix but this is sort of a last resort. Does anyone know what do to? Thanks in advance.
Click to expand...
Click to collapse
Was your S4 on the MDK bootloader/release before you tried flashing the MD2 kernel with Odin?
If it was NOT on MDK, then you can't root using that method; you'll need to flash the MK2 Odin tar from here: http://forum.xda-developers.com/showthread.php?t=2578209
And then root using saferoot: http://forum.xda-developers.com/showthread.php?t=2565758
You will not be able to install TWRP/CWM on a non-MDK S4.
bleh
I have already rooted, the problem is that I can't flash and custom ROM's, This is exactly what happens whenever I try to flash anything onto my device.
I will put it in PDA or its specified placement, and make sure everything that is needed to be checked is checked, then I will press start.
Odin will proceed to fail at boot.img, and I will then get frustrated.I can't send you a link to a screenshot yet, so if you want one I might be able to send you it in a private message, just let me know.
Along with the full message that Odin gives me <ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SCH-I545_MDK_562219_Kernel.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
I had to use a different MD5, but this is exactly what happens with everything.
When and where did you buy your S4?
I bought it at Verizon about a month or two ago
You can't flash a custom recovery on it at all then, only the first S4s bought around when it was released and then never updated can have custom recoveries.
If your phone won't boot (now or in the future), you'll need to flash the MK2 Odin tar from the thread I linked to restore it to stock.
Your only option for flashing roms will be safestrap, and only TouchWiz-based roms will work.
Safestrap: http://forum.xda-developers.com/showthread.php?t=2441441
Compatible roms: http://forum.xda-developers.com/showthread.php?t=2634408
Any reccomendations? I have never seen these.
Incaendium said:
Any reccomendations? I have never seen these.
Click to expand...
Click to collapse
If you want AOSP, Eclipse is probably the closest (themed) you can get to it: http://forum.xda-developers.com/showthread.php?t=2351840
Otherwise maybe try Bonestock, BajaROM, Hyperdrive... find whatever you like best.
Nevermind again, how do I install a rom using safestrap
Alright so I did a data wipe atempting to open up a rom slot, but I couldent get enough storage open so I just rebooted. Now my phone is stuck on the samsung custom screen that you get after you try to reboot. Did I just brick my phone?
Incaendium said:
Alright so I did a data wipe atempting to open up a rom slot, but I couldent get enough storage open so I just rebooted. Now my phone is stuck on the samsung custom screen that you get after you try to reboot. Did I just brick my phone?
Click to expand...
Click to collapse
You may or may not have bricked it. To me though it sounds like you may just want to start fresh and Odin MK2 back on your phone.. Use Saferoot, then install SafeStrap.
I'd suggest saving anything you don't want to lose and use the full wipe Odin image.
A fresh start sometimes is just the way to go. You can of course fiddle with things and see if that's not needed... But that's what I would do
Sent from my SCH-I545 using Xparent Blue Tapatalk 2
Hi everyone. I've been meaning to sell my old S4 for awhile now and I haven't been keeping up with the root scene, so clearly I might have screwed something up. I was originally running my S4 rooted with Hyperdrive S15 (Android 4.3) with TWRP + Safestrap 3.71. I deleted the hyperdrive slot and booted into the stock ROM. After that, I used TWRP to wipe everything (dalvik cache/cache/data/factory reset) then after rebooting the phone, it just stays loads up the "Samsung" Screen with the custom symbol under it. I've tried looking at guides online to try to unbrick/fix this phone, but still have no idea what to do. I've tried booting it into download mode, but for some reason, it only goes into recovery mode (I do Vol Up + Home + Power, then as soon as it vibrates, I don't press the power button anymore). I was trying to use Odin but I can't get it to go into download mode, so when I plug it in, Odin doesn't see it. Can anyone give me some ideas/info on how to fix this?
EDIT: Here are the things I have tried doing:
1. I have used both Odin v1.85 and 3.09 to try and flash the VRUEMK2 firmware and the absolute newest firmware (4.4.2 NK2). Here's the log:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUFNK1_I545VZWFNK1_I545VRUFNK1_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> aboot.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> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> modem.bin
<ID:0/003> NON-HLOS.bin
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Fails on both old and new Odins.....hmmmm...
2. Kies 2.6 and Kies 3 do not seem to be able to find the device when I load them.
Download mode is Power + Vol Down + Home. Press and hold all 3 until you see a warning on phones screen. Once you are at warning screen simply press Vol up once. If this doesn't work you may have to get a download mode jig. I had to buy one for my old S2, they can be found on ebay pretty cheap so you know.
Hope this helps!
Sent from my A0001 using XDA Free mobile app
Klown80 said:
Download mode is Power + Vol Down + Home. Press and hold all 3 until you see a warning on phones screen. Once you are at warning screen simply press Vol up once. If this doesn't work you may have to get a download mode jig. I had to buy one for my old S2, they can be found on ebay pretty cheap so you know.
Hope this helps!
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Wow I feel dumb now....thanks! It's in download mode now. I'll try to do the rest from here!
Hmmm..how long does it normally take for Odin to do it's thing? I'm following this guide:
http://www.androidrootz.com/2013/06/how-to-unroot-unbrick-galaxy-s4.html
It's been in the "downloading" screen for quite awhile.
EDIT: It says "failed". Hmmm. Figured I should have paid attention to when the article was written. I was previously on VRUEMK2 so I'm going to try this guide:
http://forum.xda-developers.com/showthread.php?t=2578209
Would these be the correct files?
ma70ent said:
Hmmm..how long does it normally take for Odin to do it's thing? I'm following this guide:
http://www.androidrootz.com/2013/06/how-to-unroot-unbrick-galaxy-s4.html
It's been in the "downloading" screen for quite awhile.
EDIT: It says "failed". Hmmm.
Click to expand...
Click to collapse
Sent from my A0001 using XDA Free mobile app
Looking at that link it shows 4.2.2 firmware for your VZW S4, going by your first post you were on a stock based 4.3 rom since you are using safestrap recovery. If that is correct then your issue is that you need a 4.3 or higher firmware, Samsung made it so you cannot downgrade most firmwares now. If I remember correctly, xda doesn't want us posting links to Samsung Web pages so please Google "sammobile" this will pull up Samsung mobile firmware download page as first result. Click on that link and then enter you model number in search box in top right of page. Enter model number and hit enter. This will pull up a list of firmwares for your model, make sure you choose 4.3 or higher firmware (4.3, 4.4, 4.4.2, or 4.4.4) and download it. Once downloaded please try Odin again.
You will have to make an acct on Samsung site to download firmware but it only takes a few mins and it's free.
Hope this helps, good luck!
Sent from my A0001 using XDA Free mobile app
Klown80 said:
Sent from my A0001 using XDA Free mobile app
Looking at that link it shows 4.2.2 firmware for your VZW S4, going by your first post you were on a stock based 4.3 rom since you are using safestrap recovery. If that is correct then your issue is that you need a 4.3 or higher firmware, Samsung made it so you cannot downgrade most firmwares now. If I remember correctly, xda doesn't want us posting links to Samsung Web pages so please Google "sammobile" this will pull up Samsung mobile firmware download page as first result. Click on that link and then enter you model number in search box in top right of page. Enter model number and hit enter. This will pull up a list of firmwares for your model, make sure you choose 4.3 or higher firmware (4.3, 4.4, 4.4.2, or 4.4.4) and download it. Once downloaded please try Odin again.
You will have to make an acct on Samsung site to download firmware but it only takes a few mins and it's free.
Hope this helps, good luck!
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Went to sammobile, registered, and downloaded the VRUEMK2 firmware (android 4.3). I tried using Odin 3.09 for this and it failed again. Should I try to flash 4.4 firmware on it? I'm only selecting the "AP" option. Should I use any other options other than f.reset, auto reboot, and AP?
Also, when I try to turn it on normally or even try recovery mode (vol up + home + power) it says "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
ma70ent said:
Went to sammobile, registered, and downloaded the VRUEMK2 firmware (android 4.3). I tried using Odin 3.09 for this and it failed again. Should I try to flash 4.4 firmware on it? I'm only selecting the "AP" option. Should I use any other options other than f.reset, auto reboot, and AP?
Also, when I try to turn it on normally or even try recovery mode (vol up + home + power) it says "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
Click to expand...
Click to collapse
You could try the 4.4, or you could just download Kies and see if it will restore it for you. Yes you are using correct space (AP) and right things checked. Another though would be to try a lower version of Odin and use the PDA slot to flash it, I vaguely remember someone having trouble on here using newest version to restore phone, he had to use older version.
Sent from my A0001 using XDA Free mobile app
Klown80 said:
You could try the 4.4, or you could just download Kies and see if it will restore it for you. Yes you are using correct space (AP) and right things checked. Another though would be to try a lower version of Odin and use the PDA slot to flash it, I vaguely remember someone having trouble on here using newest version to restore phone, he had to use older version.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Yup. Tried Kies 3 and it says device wasn't compatible, but Kies 2.6 seems to be "Connecting" forever. I'll just wait until my 4.4 firmware finishes downloading and I'll try both the new Odin and the old Odin.
Klown80 said:
You could try the 4.4, or you could just download Kies and see if it will restore it for you. Yes you are using correct space (AP) and right things checked. Another though would be to try a lower version of Odin and use the PDA slot to flash it, I vaguely remember someone having trouble on here using newest version to restore phone, he had to use older version.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Okay I just went at it again. Quick question, if Odin runs through but fails right at the end (literally write as the thing is almost over, it says "Complete Write Operation Failed"), should I just keep trying?
ma70ent said:
Okay I just went at it again. Quick question, if Odin runs through but fails right at the end (literally write as the thing is almost over, it says "Complete Write Operation Failed"), should I just keep trying?
Click to expand...
Click to collapse
What part is it failing on, system? That is strange that it's still failing since you are trying to flash the newest firmware available for your device. You can try it again but if it failed once it will most likely keep failing. You might want to check md5 sums on the downloads to be sure your not getting a corrupt download.
Sent from my A0001 using XDA Free mobile app
Klown80 said:
What part is it failing on, system? That is strange that it's still failing since you are trying to flash the newest firmware available for your device. You can try it again but if it failed once it will most likely keep failing. You might want to check md5 sums on the downloads to be sure your not getting a corrupt download.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Here's the log:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUFNK1_I545VZWFNK1_I545VRUFNK1_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> aboot.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> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> modem.bin
<ID:0/003> NON-HLOS.bin
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Fails on both Odins.....hmmmm...
Klown80 said:
What part is it failing on, system? That is strange that it's still failing since you are trying to flash the newest firmware available for your device. You can try it again but if it failed once it will most likely keep failing. You might want to check md5 sums on the downloads to be sure your not getting a corrupt download.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Alright. Actually, I did a lot of online searching and actually switched the usb port that I was using. After switching USB ports, I tried Odin again, flashed it, and it actually worked. Wow.
Anyways, I've thanked all of your posts, and of course, I thank you for spending the entire day with my problem.
ma70ent said:
Alright. Actually, I did a lot of online searching and actually switched the usb port that I was using. After switching USB ports, I tried Odin again, flashed it, and it actually worked. Wow.
Anyways, I've thanked all of your posts, and of course, I thank you for spending the entire day with my problem.
Click to expand...
Click to collapse
Sweet! Glad to hear you got it fixed! That was going to be my next suggestion. We're you by chance using a USB3 port? (it is blue if you look inside the USB port if it's usb3). For some reason most Android programming needs USB2 ports as they don't play very well with USB3.
Either way, Congratz on fixing your device, I may have given you a few pointers or helpful hints but you fixed it all on your own!
Sent from my SGH-I337 using XDA Free mobile app
Klown80 said:
Sweet! Glad to hear you got it fixed! That was going to be my next suggestion. We're you by chance using a USB3 port? (it is blue if you look inside the USB port if it's usb3). For some reason most Android programming needs USB2 ports as they don't play very well with USB3.
Either way, Congratz on fixing your device, I may have given you a few pointers or helpful hints but you fixed it all on your own!
Sent from my SGH-I337 using XDA Free mobile app
Click to expand...
Click to collapse
Actually my desktop has usb ports in the front (which aren't a direct connection to the mobo as far as I know) and of course, there are the normal usb ports in the back of it. I switched from the front one to the back one and all was well.
ma70ent said:
Actually my desktop has usb ports in the front (which aren't a direct connection to the mobo as far as I know) and of course, there are the normal usb ports in the back of it. I switched from the front one to the back one and all was well.
Click to expand...
Click to collapse
Yep it is usually best to connect directly to mobo instead any type of a USB hub, Android doesn't play very nice with those either!
Sent from my SGH-I337 using XDA Free mobile app
Klown80 said:
Yep it is usually best to connect directly to mobo instead any type of a USB hub, Android doesn't play very nice with those either!
Sent from my SGH-I337 using XDA Free mobile app
Click to expand...
Click to collapse
Hopefully this thread will help those in the future who make the same dumb mistakes I have. Haha...