Related
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 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!
I'm a newbie on the forum, so I can't post this in the right thread in the Development forum, so here it is.
As several people have mentioned elsewhere, you can't go back to anything before MJ7 via Odin. I speak from sad experience. Here's my story.
I was on ME7, rooted, using SafeStrap (SS) to use the Hyper ROM. Everything was good.
I decided to get MJ7.
So I got VoodooOTAKeeper and saved my SU.
Then tried to get the OTA update and couldn't.
I uninstalled SS, re-installed the stock Verizon/Samsung stuff (bloatware) that I had removed, unrooted with VoodooOTA, and tried again.
Still no OTA (error).
I read more on the forums and decided that I had to Odin back to stock ME7. I got Odin and the stock ME7 ROM and went back in time.
NOW the OTA worked. BUT it put me on MI1.
Here's where I made my big mistake.
I hadn't read enough and didn't know that I needed to re-root on MI1 and do all the other stuff in the "Upgrade to MJ7 and keep your root" post in the Dev forum. In my defense, it wasn't up yet.
So, I then took the MJ7 OTA.
Now I was on MJ7 OK. I tried to re-root with VoodooOTA. No dice.
I decided to try to go back to ME7 via Odin. BIG MISTAKE.
It failed (won't go back), and then left me in the "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again." mode, which I cannot get out of.
So now I have to either send the phone to Samsung and have it reflashed, or wait till the Odin MJ7 ROM is out and try that, I think.
So, DON'T DO WHAT I DID!
This did not belong in development section. This had been said 1000 times in all these threads the last couple of days. Problem is no one reads before they risk bricking their device.
jogawa said:
I'm a newbie on the forum, so I can't post this in the right thread in the Development forum, so here it is.
As several people have mentioned elsewhere, you can't go back to anything before MJ7 via Odin. I speak from sad experience. Here's my story.
I was on ME7, rooted, using SafeStrap (SS) to use the Hyper ROM. Everything was good.
I decided to get MJ7.
So I got VoodooOTAKeeper and saved my SU.
Then tried to get the OTA update and couldn't.
I uninstalled SS, re-installed the stock Verizon/Samsung stuff (bloatware) that I had removed, unrooted with VoodooOTA, and tried again.
Still no OTA (error).
I read more on the forums and decided that I had to Odin back to stock ME7. I got Odin and the stock ME7 ROM and went back in time.
NOW the OTA worked. BUT it put me on MI1.
Here's where I made my big mistake.
I hadn't read enough and didn't know that I needed to re-root on MI1 and do all the other stuff in the "Upgrade to MJ7 and keep your root" post in the Dev forum. In my defense, it wasn't up yet.
So, I then took the MJ7 OTA.
Now I was on MJ7 OK. I tried to re-root with VoodooOTA. No dice.
I decided to try to go back to ME7 via Odin. BIG MISTAKE.
It failed (won't go back), and then left me in the "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again." mode, which I cannot get out of.
So now I have to either send the phone to Samsung and have it reflashed, or wait till the Odin MJ7 ROM is out and try that, I think.
So, DON'T DO WHAT I DID!
Click to expand...
Click to collapse
There is an update.zip available and some people in your situation have had look booting into recovery and applying the update.zip manually.
Won't get you closer to root, but you do get a working phone.
Travisdroidx2 said:
This did not belong in development section. This had been said 1000 times in all these threads the last couple of days. Problem is no one reads before they risk bricking their device.
Click to expand...
Click to collapse
You're right about which forum. I had READ most of the discussion about going to MJ7 in the Development forum. But it does belong here.
tech_head said:
There is an update.zip available and some people in your situation have had look booting into recovery and applying the update.zip manually.
Won't get you closer to root, but you do get a working phone.
Click to expand...
Click to collapse
Thanks!
I can't seem to get into recovery using the Up+Power+Home method. I keep getting the "Firmware upgrade encountered ..." screen. Any tips?
Is that after a battery pull?
jogawa said:
Thanks!
I can't seem to get into recovery using the Up+Power+Home method. I keep getting the "Firmware upgrade encountered ..." screen. Any tips?
Click to expand...
Click to collapse
I did the same thing and ended up with the failed firmware error. I flashed the file in the second post of this thread in Odin and my phone booted up again: http://forum.xda-developers.com/showthread.php?t=2502591
-Lawless said:
Is that after a battery pull?
Click to expand...
Click to collapse
Yep. Pulled battery. Tried for download mode. Still stuck in the "Firmware upgrade encountered ..." mode.
mmuzzy said:
I did the same thing and ended up with the failed firmware error. I flashed the file in the second post of this thread in Odin and my phone booted up again: http://forum.xda-developers.com/showthread.php?t=2502591
Click to expand...
Click to collapse
YAY!
Thank you!
Worked like a charm.
Un-soft-bricked.
Now I wait for a root procedure for MJ7.
AND, I don't feel quite as dumb if YOU did it too.
Thanks again.
jogawa said:
YAY!
Thank you!
Worked like a charm.
Un-soft-bricked.
Now I wait for a root procedure for MJ7.
AND, I don't feel quite as dumb if YOU did it too.
Thanks again.
Click to expand...
Click to collapse
Good to hear
tech_head said:
There is an update.zip available and some people in your situation have had look booting into recovery and applying the update.zip manually.
Won't get you closer to root, but you do get a working phone.
Click to expand...
Click to collapse
My son is on ME7, and his phone kept trying to update. He gave it to me and I pulled the update.zip and I have it on my computer. Is this the update.zip you are talking about?
mmuzzy said:
I did the same thing and ended up with the failed firmware error. I flashed the file in the second post of this thread in Odin and my phone booted up again: http://forum.xda-developers.com/showthread.php?t=2502591
Click to expand...
Click to collapse
Muzzy! Are you on an s4 now?! I'm a devotee of your rom from my Toro days.
Probably not if he was on ME7. That is probably the MI1. The OTA updates require you take all of them in sequence.
Sent from my SCH-I545 using Tapatalk
tech_head said:
Probably not if he was on ME7. That is probably the MI1. The OTA updates require you take all of them in sequence.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
How long does it normally take to get root on new updates from Verizon?
Depends. It's getting harder each time. It could be tomorrow or next month.
Sent from my SCH-I545 using Tapatalk
ntb81 said:
Muzzy! Are you on an s4 now?! I'm a devotee of your rom from my Toro days.
Click to expand...
Click to collapse
Thanks. I do have an S4 now. I'm settling in as a user these days now that Nexus on VZW is becoming a distant memory. :\
jogawa said:
Yep. Pulled battery. Tried for download mode. Still stuck in the "Firmware upgrade encountered ..." mode.
Click to expand...
Click to collapse
jogawa said:
YAY!
Thank you!
Worked like a charm.
Un-soft-bricked.
Now I wait for a root procedure for MJ7.
AND, I don't feel quite as dumb if YOU did it too.
Thanks again.
Click to expand...
Click to collapse
Out of curiosity, how did you get into Odin mode while every time you tried to enter DL mode you got the same error?
Jsyme222 said:
Out of curiosity, how did you get into Odin mode while every time you tried to enter DL mode you got the same error?
Click to expand...
Click to collapse
When it's displaying that error, it's in download mode - you can plug it in and run ODIN to re-flash.
I found that kind of surprising, but it's understandable since all you can do at that point is to redo the failed flash.
k1mu said:
When it's displaying that error, it's in download mode - you can plug it in and run ODIN to re-flash.
I found that kind of surprising, but it's understandable since all you can do at that point is to redo the failed flash.
Click to expand...
Click to collapse
That's exactly right. It was in download mode all the time, even though it was showing the error. Odin always showed the COM in blue, which suggested to me that it was flashable. No big insight on my part.
jogawa said:
I'm a newbie on the forum, so I can't post this in the right thread in the Development forum, so here it is.
As several people have mentioned elsewhere, you can't go back to anything before MJ7 via Odin. I speak from sad experience. Here's my story.
I was on ME7, rooted, using SafeStrap (SS) to use the Hyper ROM. Everything was good.
I decided to get MJ7.
So I got VoodooOTAKeeper and saved my SU.
Then tried to get the OTA update and couldn't.
I uninstalled SS, re-installed the stock Verizon/Samsung stuff (bloatware) that I had removed, unrooted with VoodooOTA, and tried again.
Still no OTA (error).
I read more on the forums and decided that I had to Odin back to stock ME7. I got Odin and the stock ME7 ROM and went back in time.
NOW the OTA worked. BUT it put me on MI1.
Here's where I made my big mistake.
I hadn't read enough and didn't know that I needed to re-root on MI1 and do all the other stuff in the "Upgrade to MJ7 and keep your root" post in the Dev forum. In my defense, it wasn't up yet.
So, I then took the MJ7 OTA.
Now I was on MJ7 OK. I tried to re-root with VoodooOTA. No dice.
I decided to try to go back to ME7 via Odin. BIG MISTAKE.
It failed (won't go back), and then left me in the "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again." mode, which I cannot get out of.
So now I have to either send the phone to Samsung and have it reflashed, or wait till the Odin MJ7 ROM is out and try that, I think.
So, DON'T DO WHAT I DID!
Click to expand...
Click to collapse
Youll need to completely wipe your phone with the emergency recovery file found here. Flash that with Odin in Download Mode.
Doing this will remove root, but one of these should give it back.
i plugged my phone in today verizon software updater started download an update for my phone i'm already on 4.3 rooted i downloaded MI1 already so i know this is 4.3.. and its full size image tell me what you think would this possibly be an odin image can somebody change the format for use with odin to help people like me who bricked thier device? i cant delete this post i am wrong it downloaded the same restore twice wierd thought i had something sorry folks
todd92578 said:
i plugged my phone in today verizon software updater started download an update for my phone i'm already on 4.3 rooted i downloaded MI1 already so i know this is 4.3.. and its full size image tell me what you think would this possibly be an odin image can somebody change the format for use with odin to help people like me who bricked thier device?
Click to expand...
Click to collapse
Theres already an mj7 odin image available. If your bricked and on ml1 why not use the ml1 factory image.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
thought it would be big news
hexitnow said:
Theres already an mj7 odin image available. If your bricked and on ml1 why not use the ml1 factory image.
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 bricked it on 4.3 trying to see if i can downgrade and i read all over and didnt see the mj7 odin image a couple days ago and like the title said i thought it would be big news thats its available a lot of people has had problems with keeping root and bricking thier device trying to revert back to mi1. you acting like this is old news i was trying to help out and see what i had but i'll leave it to you guys
todd92578 said:
i bricked it on 4.3 trying to see if i can downgrade and i read all over and didnt see the mj7 odin image a couple days ago and like the title said i thought it would be big news thats its available a lot of people has had problems with keeping root and bricking thier device trying to revert back to mi1. you acting like this is old news i was trying to help out and see what i had but i'll leave it to you guys
Click to expand...
Click to collapse
Thanks for the concern and trying thats alwats appreciated. As for acting like it was old news, I wasnt trying to, just stating its already available.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.