Alright, I have a verizon galaxy s4 that I got recently, and I rooted my device and got safestrap. I tried to clear my data to make enough space for a custom rom slot and I coudent make the space to make a custom rom slot. By the way I was trying to make a rom slot for hyperdrive..
On reboot it was on the samsung screen for atleast 20/30 minutes before I took out the battery and put it back in, and now I have it on next to me. It is still on the samsung screen. Any ideas? I have a sch I545. Thanks in advance. I do have insurance and I think I might have to get my phone replaced due to this, which would suck but if that is what this comes down to I have to.
Incaendium said:
Alright, I have a verizon galaxy s4 that I got recently, and I rooted my device and got safestrap. I tried to clear my data to make enough space for a custom rom slot and I coudent make the space to make a custom rom slot. By the way I was trying to make a rom slot for hyperdrive..
On reboot it was on the samsung screen for atleast 20/30 minutes before I took out the battery and put it back in, and now I have it on next to me. It is still on the samsung screen. Any ideas? I have a sch I545. Thanks in advance. I do have insurance and I think I might have to get my phone replaced due to this, which would suck but if that is what this comes down to I have to.
Click to expand...
Click to collapse
There should be no need to get your phone replaced; users doing that is a large part of the reason why bootloaders are locked.
Follow directions here to enter ODIN/Download mode: http://forum.xda-developers.com/showthread.php?t=2290771
Download ODIN and the either the Full-Wipe or No-Wipe image here: http://forum.xda-developers.com/showthread.php?t=2578209
(If the no-wipe doesn't work, you'll need the full-wipe, so it may be easier to simply start with that one.)
Follow the directions in the thread to flash the .tar.md5 and your phone should be fully restored to normal working condition.
You are like literally my new favorite person. I love you.
I cannot flash anything because my phone will not be recognized by my computer when I plug it in via USB. I know this because I tried to unroot and see if that worked but it could not recognize my phone.
Incaendium said:
I cannot flash anything because my phone will not be recognized by my computer when I plug it in via USB. I know this because I tried to unroot and see if that worked but it could not recognize my phone.
Click to expand...
Click to collapse
Are you able to get the S4 booted into Download mode?
(Assuming yes)
Do you have the Samsung USB Driver installed? http://org.downloadcenter.samsung.c...ng_USB_Driver_for_Mobile_Phones_v1.5.14.0.exe
Have you tried using the USB cable it came with, or a different cable/port?
Related
Hi everyone. I have a samsung galaxy s vibrant on android 2.2. I am a total noob with any modifications but am going overseas next month and wanted to unlock my phone. After looking into rooting etc. I downloaded odin and darky's ROM resurrection edition. I followed the prompts to go into recovery and wipe etc. and remove battery and turn back on. After using odin and restarting my phone now just flashes the start screen showing galaxy s GT-I9000. I can't enter recovery mode just download mode. I'm unsure what to do and even tried mounting another recovery file on odin which lead me to the same point. Any help would be greatly appreciated.
Try re-flashing it and see if that works, sometimes that's all it takes. It's possible you just had a bad flash.
I've tried about 5 times now and it seems to keep failing to boot after flash and sticking on the initial boot screen and flashing on and off. Is there a way to download and flash an original ROM and mount on odin to start over?
Try getting into download mode. Hold and continue to hold up & down volume controls while holding in the power button. When the Vibrant logo comes up release only the power button. If you do get into recovery that way scroll down to install zip from sd card and install whatever rom you've got on there that you want to use. Let me know if that works or not.
I can still only get into download mode. I've tried flashing again with both ROMs I have and they both are doing the same thing. Holy frustrating lol
Spike84 said:
I can still only get into download mode. I've tried flashing again with both ROMs I have and they both are doing the same thing. Holy frustrating lol
Click to expand...
Click to collapse
Look for a hard surface... concrete for example.. now take your phone and throw it as hard as you can... Just kidding don't do that, that's a permanent reboot. I know the frustration, I've been there many times. You may want to go back and read through the noob guide, I'm not sure what else to suggest. Hopefully someone else will read this and have a better suggestion. Good luck.
haha yeah the thought crossed my mind. I appreciate your help. I'm still reading through the forum. Most instructions seem to require me to reach recovery mode or usb debugging. My phone is no longer being recognized on the computer but odin is obviously still recognizing so I'm going to try a fresh 2.2 on odin and see if that works.
Good luck, I'm rooting for ya. If that does not work and your close to a T-mobile store I'd just run it in and have them check it out, they may have to replace it.
Thanks again. I'm actually in Canada and using a sub provider from bell "virgin mobile".
I installed SafeStrap 3.70 and tried to install RLS12 (on MK2). Things did not go so well. It booted to a black screen. Figured I would just ODIN back to stock and now my phone is really unhappy.
I tried flashing both of the firmwares from here (full did not work so I tried no-wipe):
http://forum.xda-developers.com/showthread.php?t=2578209&highlight=mk2
I can boot into download mode but not recovery. When I first flash a ROM via ODIN the phone will show the Samsung logo and even get to the Verizon splash screen. Problem is it will power off after a minute or so. If the phone is connected via the USB cable the charging battery screen appears. If I try to go into recovery it just powers off (verified by plugging in USB cable and getting charging screen).
One thing I have noticed is that even after flashing with Odin the Samsung custom splash screen still shows up. Usually that goes away.
I am open to any and all suggestions. My last two things to try is going through Kies Revovery. Next it to try downloading a firmware from sammobile.com.
diaftia said:
I installed SafeStrap 3.70 and tried to install RLS12 (on MK2). Things did not go so well. It booted to a black screen. Figured I would just ODIN back to stock and now my phone is really unhappy.
I tried flashing both of the firmwares from here (full did not work so I tried no-wipe):
http://forum.xda-developers.com/showthread.php?t=2578209&highlight=mk2
I can boot into download mode but not recovery. When I first flash a ROM via ODIN the phone will show the Samsung logo and even get to the Verizon splash screen. Problem is it will power off after a minute or so. If the phone is connected via the USB cable the charging battery screen appears. If I try to go into recovery it just powers off (verified by plugging in USB cable and getting charging screen).
One thing I have noticed is that even after flashing with Odin the Samsung custom splash screen still shows up. Usually that goes away.
I am open to any and all suggestions. My last two things to try is going through Kies Revovery. Next it to try downloading a firmware from sammobile.com.
Click to expand...
Click to collapse
I've seen someone else with this problem..
Think they took the battery out for like 5-10 minutes then they were able to boot into recovery then did a factory reset and cleared Cache then that either fixed it or they Odin back. Have you tried that? Sounds like you know what you're doing. I had to do that with my s4 as well after running into some issues
Edit:
Is this all on your stock slot or is hd12 on a rom slot???
Reason I ask is I had this happen to me and even after full Wipe in Odin my s4 was doing same thing as yours it sounds and mine was all on stock slot. My phone was really pissed at me.
Verizon Galaxy S4
Safestrap 3.7
HYPERDRIVE 11
Mistertac said:
I've seen someone else with this problem..
Think they took the battery out for like 5-10 minutes then they were able to boot into recovery then did a factory reset and cleared Cache then that either fixed it or they Odin back. Have you tried that? Sounds like you know what you're doing. I had to do that with my s4 as well after running into some issues
Edit:
Is this all on your stock slot or is hd12 on a rom slot???
Reason I ask is I had this happen to me and even after full Wipe in Odin my s4 was doing same thing as yours it sounds and mine was all on stock slot. My phone was really pissed at me.
Verizon Galaxy S4
Safestrap 3.7
HYPERDRIVE 11
Click to expand...
Click to collapse
Yes, this is in the stock slot. I had been running in the stock slot since RLS8(9?) without any problems but something has definitely changed.
Some good news! I went to bed at around 12:30 with Kies left running. It had stated the download process of the restore. When I checked on it this morning I had a red light on the phone which I had not had before (charging indicator). I unplugged the phone and powered it on. Low and behold I got a setup wizard. Looks like Keis does something that Odin does not. So when in doubt restore the stock image with Keis if you are stuck. BTW, when doing that I did the "Firmware Upgrade and Initialization" method. It asks for the model # and it is case sensitive for some reason. It took "SCH-I545" but was not taking "sch-i545".
diaftia said:
Yes, this is in the stock slot. I had been running in the stock slot since RLS8(9?) without any problems but something has definitely changed.
Some good news! I went to bed at around 12:30 with Kies left running. It had stated the download process of the restore. When I checked on it this morning I had a red light on the phone which I had not had before (charging indicator). I unplugged the phone and powered it on. Low and behold I got a setup wizard. Looks like Keis does something that Odin does not. So when in doubt restore the stock image with Keis if you are stuck. BTW, when doing that I did the "Firmware Upgrade and Initialization" method. It asks for the model # and it is case sensitive for some reason. It took "SCH-I545" but was not taking "sch-i545".
Click to expand...
Click to collapse
Well that's good news. Yea like I said that happened to me as well... I just didn't use kies. But looks like you're back up and running so you're good.
Verizon Galaxy S4
Safestrap 3.7
HYPERDRIVE 11
Hi All,
I've had my original VRUAMDK S4 running Cyanogen since the day I got it, I never took an update and have always had a custom recovery. However, the phone's compass sensor has been wacky and I really need to flash back to a Samsung ROM for a few minutes to fix the compass.
However, I've just tried to use one of the "VRUAMDK No-Wipe" ROMs and bricked my phone, odin died almost immediately with a "Failed". I've seen that perhaps the no-wipe ROM is not going to work with a phone that already has custom recovery.. Problem is, I can't find a "true" image to actually restore VRUAMDK load.
Does anyone have a "full" image of the original Samsung Verizon S4 VRUAMDK they could post, that I can flash in Odin?
Update, I found the "SCH-I545_MDK_562219_Stock_Restore.tar.md5" which I'm hoping is right. It definitely gets further than before, but now every Odin flash fails at persdata.img.ext4.
Screen shows "stat [224,1440]".
Thoughts?
This will wipe out your phone entirely. It will be as if you bought a brand new MDK phone from Verizon that nobody has ever used. Please keep that in mind. Everything you've ever had on this phone will be wiped away and you will have no pictures, text messages, videos, emails, notes, programs, etc.
I downloaded it and double-checked that it's exactly the same one that I have, by file hash. You'll have to unzip it at least twice, maybe three times. I use 7zip for all of that.
SCH-I545_MDK_562219_Stock_Restore.tar.md5.gz
SCH-I545_MDK_562219_Stock_Restore.exe
Remember, you'll have a completely wiped phone. This is beyond a "factory reset". This is the closest thing to Samsung building a phone in the factory and then installing the operating system...you'll have nothing of yours on it. Whenever I've done this, I've taken out my microSD card. I don't think it touches it, but I do it anyway out of paranoia.
https://www.androidfilehost.com/?fid=22979706399755579
Here are some quick and dirty instructions I wrote for myself:
Jon8RFC's notes said:
1) Run SCH-I545_MDK_562219_Stock_Restore.exe with the s4 in "download mode" (reboot while holding the 'volume down' button, then press 'volume up' when prompted to continue)
This takes 17 minutes from start until initial phone setup is ready
2) Boot into the phone, sign into a google account
3) Go into settings and enable developer mode, then enable USB debugging
4) Run the RUN_ME.bat file in the ALL-IN-ONE folder
Click to expand...
Click to collapse
Steps 3 and 4 are if you want to re-root and unlock the bootloader with Loki. You'll need this:
http://forum.xda-developers.com/showthread.php?t=2301720
If you use TWRP, I suggest replacing the openrecovery.img with a more recent one, like TWRP 2.8.4.0 (2.8.5.0 for the i545 is no good), and rename it openrecovery.img in the folder where all of the files unzip to, in the same folder as the RUN_ME.bat. I think the one it comes with is 2.6.0.2 or something, because the tool is very old. I've swapped in 2.8.4.0 without a hitch, and then you're able to do a NANDROID backup of your MDK install and future installs...you can't NANDROID restore a 2.6.0.2 backup with 2.8.4.0, unfortunately. So, do it the updated way from the start.
http://dl.twrp.me/jfltevzw/
I'm not sure of the exact process you're following--files, programs, buttons pushed, etc. The ODIN I posted is a pretty simple set it and forget it kind of thing. Make sure your phone has enough of a charge since it likely will drain faster than your computer's USB port can output. I don't know what happens if an ODIN fails in the middle due to a power failure or USB disconnect...maybe nothing at all, but maybe a hard brick. Don't risk it, and charge up!
As for the error, that's a new one to me that I've never seen. I'm no expert. I did a quick search and some people suggested that using non-Samsung USB cables were the culprit for this particular error. Strange as it may be, my dinky, thin Samsung cable can deliver full power from the charger and a shorter, thicker gauge monoprice cable cannot. So, it's worth a shot if you have it, or try another cable.
Jon8RFC said:
It will be as if you bought a brand new MDK phone from Verizon that nobody has ever used. Please keep that in mind.
Click to expand...
Click to collapse
These are really great notes. And yep, that was absolutely my intent - get back to the original MDK status.
It was a 2-part problem. First, apparently Odin only half-works when you run it inside VMWare. I had to switch to a native Windows machine. Second, the USB cable.
Invisiblek posted a commit to CM that has fixed the compass issue. It's so nice to see the compass properly work again!!
Hello. I'm new to the mdk bootloader and want to preserve it. I'd like to know that I could Odin back to stock mdk rom with unlocked BL if I ever screw it up. Is the stock tar link and info still relevant to me? Would I also need jftlevxz mdk pit files for the partition?
Thanks much.
Hello Everyone,
So recently I got a new S4 and I decided to root and mess around with it a little bit... Didn't go so well.
First KNOX was pissed that I tried that because I had given SU power to SuperSU (I didnt want to use KingUser) so when that happened, SuperSU failed to set itself as the primary SuperUser app. So I decided to install recovery (TWRP) to do it the recover way, scripts and all that. After that, I went ahead and removed KNOX, via the settings menu on the app.
Now I fail to boot into RECOVERY, and I also fail to boot into normal Android mode. When I attempt to boot normally, the SAMSUNG logo comes up then verizon, Okay fine its booting. 5 miutes later, the phone gets hot, and still wont boot.
I cannot charge the normal way, or even use the charging port. I have to take the battery out and put it in a dock. So ODIN is out of the choice.
My Phone Specs:
Samsung Galaxy S4 i545 (Verizon)
1GB SD Card
No recovery or ODIN.
Please help...
If you can't get into download mode then you have a problem.
Without it there isn't much you can do. You also need the pc to recognize your phone.
I'd say flash a custom ROM because new update which I received on stock firmware of I9500 added some security and an app called smart manager which is causing instability. Connect your dead phone to charger and then flash TWRP 2-3 times and don't forget to untick F.rest time and auto reboot. Normally it is ticked, and manually boot to download mode each time I hope you know how to do that. Then try your luck. That's how I did it. And use latest recovery available on the web.
Hit thanks
I believe the Verizon s4 has a locked bootloader (http://forum.xda-developers.com/showthread.php?t=2681316); therefore, you cannot flash a custom ROM or custom recovery.
You may get more replies if you post your question here: http://forum.xda-developers.com/galaxy-s4-verizon/help
Read before posting!
THe thing is though, If I could use Download mode, i would. But because of damage in the port, it fails to work So this is why I am confused on what to do...
---Edit will go here if needed.
thedarkness523 said:
THe thing is though, If I could use Download mode, i would. But because of damage in the port, it fails to work So this is why I am confused on what to do...
---Edit will go here if needed.
Click to expand...
Click to collapse
if the port is physically damaged then you need to
get the port replaced
there is absolutely nothing you can do until you have the usb port repaired
. secondly hold power down while inserting the battery if that doesn't get it into download mode then congratulations you now have a 200.00 dollar brick
the i545 does not support custom recoveries or custom roms outside of modded stock roms attempting to flash one will result in a permabrick as you just found out
Once the usb is repaired if you are still unable to access download mode then you have a big problem. When the port is repaired see if the comouter recognizes the phone as QHUSB_dload, if so, you need jtag, if the computer doesnt recognize the phone then it is most likely damaged beyond repair.
Hey all,
First i'd like to tell my phone was 'working' as it was able to go to download mode.
Im not really an expert, but when I used Google to find a solution for my error I read about using Odin.
(In case you need the error, I will try to edit the thread and add this asap!)
I followed a tutorial about using Odin and tried to get my phone up back and running.
I downloaded the following file for my Samsung J5:
sammobile.com/firmwares/galaxy-j5/SM-J500FN/PHN/download/J500FNXXS1BQG3/181971/
After using the Odin software it somehow got interrupted while installing. (cable came loose I guess, I heard the connect/disconnect sound shortly after each other)
Also I noticed there was a small red text on the screen complaining about the available size on the phone.
Even though the phone installation was interrupted, the phone was still able to get into download mode.
Next up, I decided to place a micro SD card to get extra storage space and retried the Odin process. The final result was a "PASS" (see screenshot)
i.imgur.com/WzFJLaQ.jpg
After the update was done 'succesfully' the phone screen immediately turned to black.
There were no signs of life anymore, not even accessing boot mode / recovery mode no nothing.
I've bought an USB JIG, but sadly also with the JIG I had no luck.
Is there any way to get my phone back and running? or can anyone give me some advice?
I really hope someone can help me out!
Sounds like a hard brick ?
This happens when you try to upgrade or downgrade, some devices don´t allow this or the firmware is not matching.
Pull out battery if it is removable for some minutes then try normal method, if not....
Here the correct method to do a jig by your own or maybe it´s better to buy one (it´s not expensive) to made sure that is correctly made http://www.instructables.com/id/USB-JIG-to-give-life-to-your-Bricked-mobile/
Also you can try with Smart Switch https://youtu.be/y8AZyalTf5Y
Sands207 said:
Sounds like a hard brick ?
Click to expand...
Click to collapse
Can you check your pm's?