I really need some help here. I have an MDK S4 that I sold. Need to mail it out tomorrow. It has TWRP installed and was stock rooted. I tried to wipe all my info, so I went into TWRP, did a factory resent, and wiped data. Now the phone won't boot passed the "Samsung Galaxy S4 screen". I really need some help with this. I promised this person I would ship the phone out tomorrow and take that very seriously. Any help is extremely appreciated.
pyro6128 said:
I really need some help here. I have an MDK S4 that I sold. Need to mail it out tomorrow. It has TWRP installed and was stock rooted. I tried to wipe all my info, so I went into TWRP, did a factory resent, and wiped data. Now the phone won't boot passed the "Samsung Galaxy S4 screen". I really need some help with this. I promised this person I would ship the phone out tomorrow and take that very seriously. Any help is extremely appreciated.
Click to expand...
Click to collapse
I would try putting it into download mode and then flash the stock mdk images.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk. now Free
hexitnow said:
I would try putting it into download mode and then flash the stock mdk images.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk. now Free
Click to expand...
Click to collapse
Can I flash the stock rooted MDK file found here http://forum.xda-developers.com/showthread.php?t=2292707 through TWRP? I should mention, I can still boot into TWRP fine, I just can't get the phone to boot normally.
pyro6128 said:
Can I flash the stock rooted MDK file found here http://forum.xda-developers.com/showthread.php?t=2292707 through TWRP? I should mention, I can still boot into TWRP fine, I just can't get the phone to boot normally.
Click to expand...
Click to collapse
Using Odin to flash the stock image is pretty much the best way to get it to stock so I wouldn't even bother with TWRP honestly
Crawshayi said:
Using Odin to flash the stock image is pretty much the best way to get it to stock so I wouldn't even bother with TWRP honestly
Click to expand...
Click to collapse
Can I use Odin to get back to stock rooted though? Can I flash the image I linked to above through odin?
pyro6128 said:
Can I use Odin to get back to stock rooted though? Can I flash the image I linked to above through odin?
Click to expand...
Click to collapse
If youre selling it i wouldnt worry about keeping it rooted unless that was one of the selling.points. yes you can also use the stock rooted mdk rom as well but it cant be flashed via odin it has to be flashed via recovery. But once again I would odin to return it to out of the box software.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk. now Free
hexitnow said:
If youre selling it i wouldnt worry about keeping it rooted unless that was one of the selling.points. yes you can also use the stock rooted mdk rom as well but it cant be flashed via odin it has to be flashed via recovery. But once again I would odin to return it to out of the box software.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk. now Free
Click to expand...
Click to collapse
Yea, it was one of the selling points, the fact that it was MDK and already rooted. Anyway, I just tried flashing the stock rooted file through TWRP and it didn't work. Still won't boot passed the samsung galaxy s4 splash screen. Guess its time to try Odin. Should I be concerned about the phone updating on its own? MDK is the big selling point.
pyro6128 said:
Yea, it was one of the selling points, the fact that it was MDK and already rooted. Anyway, I just tried flashing the stock rooted file through TWRP and it didn't work. Still won't boot passed the samsung galaxy s4 splash screen. Guess its time to try Odin. Should I be concerned about the phone updating on its own? MDK is the big selling point.
Click to expand...
Click to collapse
have you tried to use it through ODIN? going through TWRP is not the same.
Are you using twrp 2.5.0.2?
Here is a flashable version 2.5.0.2 I did not make this but got it from the twrp thread and many have used it. Just flash in recovery.https://db.tt/YeZ3cp4c
Twrp 2.6+ is known to have issue's.
pyro6128 said:
Yea, it was one of the selling points, the fact that it was MDK and already rooted. Anyway, I just tried flashing the stock rooted file through TWRP and it didn't work. Still won't boot passed the samsung galaxy s4 splash screen. Guess its time to try Odin. Should I be concerned about the phone updating on its own? MDK is the big selling point.
Click to expand...
Click to collapse
If you have to resort to using odin put it in airplane mode, root, disable airplane mode and update binaries then remove sdm.apk or rename it and the ota update wont hastle you anymore.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk. now Free
hexitnow said:
If you have to resort to using odin put it in airplane mode, root, disable airplane mode and update binaries then remove sdm.apk or rename it and the ota update wont hastle you anymore.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk. now Free
Click to expand...
Click to collapse
Using Odin to restore it right now. I'll throw it in airplane mode once its done. Thanks for the assistance. This thing is killing me and I have work in the morning, but I need to get this done or it'll bother me all night haha.
Edit: Just odin'ed using this guide http://forum.xda-developers.com/showthread.php?t=2301259 and it still won't boot past the Galaxy s4 screen
http://forum.xda-developers.com/showthread.php?t=2289325
Original full stock images. Will also wipe data.
Did the Odin process pass the first time you tried and then stock froze at splash screen? How long you letting sit on the first boot? That first boot can take a while sometimes.
Travisdroidx2 said:
http://forum.xda-developers.com/showthread.php?t=2289325
Original full stock images. Will also wipe data.
Did the Odin process pass the first time you tried and then stock froze at splash screen? How long you letting sit on the first boot? That first boot can take a while sometimes.
Click to expand...
Click to collapse
^^ this
Yes sometimes up to 10 min for some ROMs but I've never have had it take more then 4 or 5 min on a fresh flash.
Travisdroidx2 said:
http://forum.xda-developers.com/showthread.php?t=2289325
Original full stock images. Will also wipe data.
Did the Odin process pass the first time you tried and then stock froze at splash screen? How long you letting sit on the first boot? That first boot can take a while sometimes.
Click to expand...
Click to collapse
I did a battery pull, then booted into the regular recovery, did another factory reset, and was finally able to boot back into android. Then I was able to follow all of the root/recovery steps. Finally got it sorted out!!!!! Thanks to everyone who helped me, its silly, but it helped that I didn't feel stranded with this thing. XDA is the best!
Related
Good evening,
Thanks for taking the time to read this.
I rooted and unlocked my phone and then tried installing a wrong CM10. Then I installed the stock ROM again so that it would at least work. That succeeded.
However, a popup came offering a OTA update and I hit yes without thinking. It rebooted and stayed at boot loop.
Now when I try using ODIN to reflash the stock ROM it does so, reboots, and stays at the boot screen where the LTE and moving stuff shows up after the Samsung Galaxy Note 2 in white text screen. Please, I need this fixed urgently as that's my work phone.
I've tried flashing the rooted stock rom and that doesn't work either. When I try to re-root/unlock it says "Firmware problem please connect to Klies" or something along those lines. I can't boot into recovery mode either. The android shows up and a bar and then it reboots when it's close to finishing the boot into recovery.
bump
I'm confused, where is your phone now. Boot loop, the firmware upgrade problem or other?
Sent from my SCH-I605 using Tapatalk 2
Really basic question here, how long have you let it sit on the boot animation screen? Sometimes it takes a very long time for first boot, especially if davlik was wiped.
fbernar said:
bump
Click to expand...
Click to collapse
I just read a post about someone in the same situation that said after about 30 attempts!! with Odin it did finally work.
Also, I have no affiliation with these guys but they seem to know what they are doing and doing it for a reasonable price: http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-note-2-jtag-brick-repair/
Good luck.
Geezer Squid said:
I just read a post about someone in the same situation that said after about 30 attempts!! with Odin it did finally work.
Also, I have no affiliation with these guys but they seem to know what they are doing and doing it for a reasonable price: http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-note-2-jtag-brick-repair/
Good luck.
Click to expand...
Click to collapse
They're the people to use if needed
Sent from my SCH-I605 using Tapatalk 2
jacampb2 said:
Really basic question here, how long have you let it sit on the boot animation screen? Sometimes it takes a very long time for first boot, especially if davlik was wiped.
Click to expand...
Click to collapse
I've let it sit for like an hour in a boot loop.
kintwofan said:
I'm confused, where is your phone now. Boot loop, the firmware upgrade problem or other?
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Boot loop if I try to go to stock ROM. Firmware warning if I try to use boot unlocker/root ROM.
I can't get into recovery under either. When I try to get into recovery under the boot unlock/root ROM I get the firmware problem.
fbernar said:
Boot loop if I try to go to stock ROM. Firmware warning if I try to use boot unlocker/root ROM.
I can't get into recovery under either. When I try to get into recovery under the boot unlock/root ROM I get the firmware problem.
Click to expand...
Click to collapse
Your phone had to boot up to unlock so again are you boot looping now? I'm thinking you need to use the alternate restore file. It sounds like your boot loader is still locked. If that's the case that's the only image that will actually flash in Odin.
Sent from my SCH-I605 using Tapatalk 2
here is your problem:
1) NEVER ACCEPT OTA'S
2) You didnt research before flashing
3) Since you accepted the ota, the bootloader from the original vraljb odin file is black listed. meaning you cant ever use that file again.
4) To fix your problem follow section 1b of my guide, make sure to use the alternate restore link as it does not contain a bootloader in the file. it will revert you back to vraljb firmwqre while maintaining the L4 bootloader.
droidstyle said:
here is your problem:
1) NEVER ACCEPT OTA'S
2) You didnt research before flashing
3) Since you accepted the ota, the bootloader from the original vraljb odin file is black listed. meaning you cant ever use that file again.
4) To fix your problem follow section 1b of my guide, make sure to use the alternate restore link as it does not contain a bootloader in the file. it will revert you back to vraljb firmwqre while maintaining the L4 bootloader.
Click to expand...
Click to collapse
`^^^ all of this
Sent from my SCH-I605 using Tapatalk 2
I accidentally tried to install a custom recovery on my galaxy s4. Its running me7 and it got bricked. I can reboot it and everything works fine but if I try to factory reset the phone in the settings it gets stuck in download mode. Is there anyway around this?
Kwc0055 said:
I accidentally tried to install a custom recovery on my galaxy s4. Its running me7 and it got bricked. I can reboot it and everything works fine but if I try to factory reset the phone in the settings it gets stuck in download mode. Is there anyway around this?
Click to expand...
Click to collapse
First off your phone isnt bricked, its not even soft bricked. Your phone cant boot to stock recovery because you attempted to overwrite it with a custom version. Youll have to flash the stock me7 image via odin to get back your stock recovery. All the stock images can be found in the dev section. There is also a no wipe version if you apps/data you dont want to be wiped during the process.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
hexitnow said:
First off your phone isnt bricked, its not even soft bricked. Your phone cant boot to stock recovery because you attempted to overwrite it with a custom version. Youll have to flash the stock me7 image via odin to get back your stock recovery. All the stock images can be found in the dev section. There is also a no wipe version if you apps/data you dont want to be wiped during the process.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
Click to expand...
Click to collapse
I did try to odin it over after the fact thinking I did brick it i found a youtube guide on how to unbrick it via odin, sadly odin kept giving me failure messages. I think the me7 update blocks any kind of flashing.
Kwc0055 said:
I did try to odin it over after the fact thinking I did brick it i found a youtube guide on how to unbrick it via odin, sadly odin kept giving me failure messages. I think the me7 update blocks any kind of flashing.
Click to expand...
Click to collapse
If it failed after flashing aboot you were trying to flash mdk which you cant do. Prior firmwares are blocked. Me7 doesnt block odin flashing you just have to flash the me7 stock file.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
hexitnow said:
If it failed after flashing aboot you were trying to flash mdk which you cant do. Prior firmwares are blocked. Me7 doesnt block odin flashing you just have to flash the me7 stock file.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
Click to expand...
Click to collapse
I think I tried both honestly but I'm redownloading the me7 as we speak and I'll try it out again. I'll post again after and let u know if it works. I appreciate you taking the time to help me.
Kwc0055 said:
I think I tried both honestly but I'm redownloading the me7 as we speak and I'll try it out again. I'll post again after and let u know if it works. I appreciate you taking the time to help me.
Click to expand...
Click to collapse
Not a problem, yeah just make sure its the me7 image or it wont flash. Also when flashing me7 if youre still getting errors it could be a corrupted download so verifying the md5 after the download is suggested.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
it worked! thank you so much! many thanks
Kwc0055 said:
it worked! thank you so much! many thanks
Click to expand...
Click to collapse
No problem, glad you got it sorted out.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
I get this error when I start my S4. "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon wireless store for help. Any idea how to fix this?
androidguy91 said:
I get this error when I start my S4. "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon wireless store for help. Any idea how to fix this?
Click to expand...
Click to collapse
Sounds like the bootloader got locked.
Probably should provide more details like MDK vs. ME7, Locked bootloader or not, what recovery, etc. but the best fix is to Odin back to stock and start over.
Also what was the last thing you tried to do like maybe installing a recovery or a ROM
NilsP said:
Sounds like the bootloader got locked.
Probably should provide more details like MDK vs. ME7, Locked bootloader or not, what recovery, etc. but the best fix is to Odin back to stock and start over.
Also what was the last thing you tried to do like maybe installing a recovery or a ROM
Click to expand...
Click to collapse
I was trying to install the stock android ROM. The phone is ME7 and I think a locked bootloader.
You cant unlock the bootloader on the s4, just a heads up. Only bypass it via loki but that only works on mdk. Anyhow like nil said I wold odin and start over. If you were on me7 you cant flash mdk and itll error when it gets to flashing aboot so you can always try if you want. Flashing the me7 stock image via odin should get rid of it tho.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
hexitnow said:
You cant unlock the bootloader on the s4, just a heads up. Only bypass it via loki but that only works on mdk. Anyhow like nil said I wold odin and start over. If you were on me7 you cant flash mdk and itll error when it gets to flashing aboot so you can always try if you want. Flashing the me7 stock image via odin should get rid of it tho.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
Click to expand...
Click to collapse
Know of any good places to get the stock ROM for ME7?
androidguy91 said:
Know of any good places to get the stock ROM for ME7?
Click to expand...
Click to collapse
Its posted in the development section.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
hexitnow said:
Its posted in the development section.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
Click to expand...
Click to collapse
I looked there any links?
androidguy91 said:
I looked there any links?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=43420116
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
I want to update from MDK to ME7.
When I plug the phone into the computer it mounts as a media device.
How do I get the Upgrade assistant?
You don't want to update
Luke
lukesdiesel said:
You don't want to update
Luke
Click to expand...
Click to collapse
Surprised at how many psychics are on this forum. If you upgrade to me7 you lose the exploitable bootloader and cant flash custom recovery. Me7 still has root and safestrap so you can still get custom roms that route. If youre still interested you could always try taking the ota or download the stock me7 image and flash via odin. When it comes to the upgrade assistant ive never used that so sorry cant help on that front.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
hexitnow said:
Surprised at how many psychics are on this forum. If you upgrade to me7 you lose the exploitable bootloader and cant flash custom recovery. Me7 still has root and safestrap so you can still get custom roms that route. If youre still interested you could always try taking the ota or download the stock me7 image and flash via odin. When it comes to the upgrade assistant ive never used that so sorry cant help on that front.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
Click to expand...
Click to collapse
Thanks I upgraded using kies and it worked like a charm but then i tried to do a backup using twrp and got stuck in a odin bootloop but thanks to this site I was able to get out of that boot loop with vol down and power. thank God. I thought I bricked it.
pego99 said:
Thanks I upgraded using kies and it worked like a charm but then i tried to do a backup using twrp and got stuck in a odin bootloop but thanks to this site I was able to get out of that boot loop with vol down and power. thank God. I thought I bricked it.
Click to expand...
Click to collapse
Like I was saying you cant flash a custom recovery on me7. Safestrap is your only option if youre looking to rom.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
OK, made a dumb mistake. Not a frequent poster so I had to post here rather than in the thread where it belongs:
http://forum.xda-developers.com/showthread.php?t=2643031&page=266
[ROM]KOT49H【4.4.4】AOSP Official Google Edition 【Verizon!】06-25-2014
Basically, I didn't re-flash loki-doki. I had 4.4.2 running and had re-flashed 4.4.3 but somehow thought that I could reboot and then re-enter recovery to re-flash loki rather than doing it all at once. Dumb move. So now I have a perfectly good 4.4.3 load, but I can't enter recovery to do anything else. I want to flash the 4.4.4 image, but anytime I try to get into recovery I get the "System software not authorized by Verizon Wireless / Yellow Triangle" message.
I know I can Odin back to a stock image, but is there an easy way to force into recovery to flash loki-doki? Tried Flashify per another users post but that doesn't get me anywhere. Have not tried Triangle Away, because I didn't think that would cure my issue. The answer may be to re-flash, but I wanted to see if there was an easy way first. Running MDK btw....
Chad
Chad52 said:
OK, made a dumb mistake. Not a frequent poster so I had to post here rather than in the thread where it belongs:
http://forum.xda-developers.com/showthread.php?t=2643031&page=266
[ROM]KOT49H【4.4.4】AOSP Official Google Edition 【Verizon!】06-25-2014
Basically, I didn't re-flash loki-doki. I had 4.4.2 running and had re-flashed 4.4.3 but somehow thought that I could reboot and then re-enter recovery to re-flash loki rather than doing it all at once. Dumb move. So now I have a perfectly good 4.4.3 load, but I can't enter recovery to do anything else. I want to flash the 4.4.4 image, but anytime I try to get into recovery I get the "System software not authorized by Verizon Wireless / Yellow Triangle" message.
I know I can Odin back to a stock image, but is there an easy way to force into recovery to flash loki-doki? Tried Flashify per another users post but that doesn't get me anywhere. Have not tried Triangle Away, because I didn't think that would cure my issue. The answer may be to re-flash, but I wanted to see if there was an easy way first. Running MDK btw....
Chad
Click to expand...
Click to collapse
I am far from an expert but I think you are on the right track with having to do Odin.
I haven't used loki-doki before but after doing some reading the requirement is a working custom recovery.
This may be a dumb question but did you try to re-install something like CWM?
(CM11 jflte MDK baseband)
Chad52 said:
OK, made a dumb mistake. Not a frequent poster so I had to post here rather than in the thread where it belongs:
http://forum.xda-developers.com/showthread.php?t=2643031&page=266
[ROM]KOT49H【4.4.4】AOSP Official Google Edition 【Verizon!】06-25-2014
Basically, I didn't re-flash loki-doki. I had 4.4.2 running and had re-flashed 4.4.3 but somehow thought that I could reboot and then re-enter recovery to re-flash loki rather than doing it all at once. Dumb move. So now I have a perfectly good 4.4.3 load, but I can't enter recovery to do anything else. I want to flash the 4.4.4 image, but anytime I try to get into recovery I get the "System software not authorized by Verizon Wireless / Yellow Triangle" message.
I know I can Odin back to a stock image, but is there an easy way to force into recovery to flash loki-doki? Tried Flashify per another users post but that doesn't get me anywhere. Have not tried Triangle Away, because I didn't think that would cure my issue. The answer may be to re-flash, but I wanted to see if there was an easy way first. Running MDK btw....
Chad
Click to expand...
Click to collapse
Try unzipping whatever recovery it is you want to use and then use Flashify to " flash recovery image " and locate the Recovery. IMG you got from unzipping earlier.
Also I would run Tri Angle Away too.
If using that method to get you're recovery back doesn't help... Then yes Odin it is.
Sent from my SCH-I545 using Tapatalk
Thanks all. I use twrp, and have tried reflashing it, but nothing let's me reboot into recovery without the situation described above. My fault, so looks like back to square one I go...
Sent from my GT-I9505G using Tapatalk
Chad52 said:
Thanks all. I use twrp, and have tried reflashing it, but nothing let's me reboot into recovery without the situation described above. My fault, so looks like back to square one I go...
Sent from my GT-I9505G using Tapatalk
Click to expand...
Click to collapse
Are you just trying to get into recovery from the ROM? Or from a battery pull and phone off? Sometimes getting into it from the ROM can get borked but the other method works in which case flashing the ROM again should fix that. Again I'd also use Tri Angle Away
Sent from my SCH-I545 using Tapatalk
Trying from inside the ROM. I've got a fully functioning 4.4.3, but I'm locked out of getting into Recovery....
Chad
Flashify can't even get me into Recovery...
Thanks all, I ODIN'd back to stock and worked it all the way back forward to 4.4.4. Appreciate the help.
Chad
I hate digging up old threads especially when Hijacking them. But I wanted to say thanks for the information you provided. It helped a lot and got me back into recovery (TWRP 2.8.1.1). Now the real fun begins. I have not had this phone in my possession for quite some time (November 2013). Anyway, I was tasked with bringing it up to date and I might need some further assistance. If so, I'll start my own topic in this sub forum.
Thanks again @Mistertac.
Mistertac said:
Try unzipping whatever recovery it is you want to use and then use Flashify to " flash recovery image " and locate the Recovery. IMG you got from unzipping earlier.
Also I would run Tri Angle Away too.
If using that method to get you're recovery back doesn't help... Then yes Odin it is.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse