I did the OTA update from M1I to MJ7 and read somewhere that the M1I root method would work. It made my phone unbootable. Obviously the M1I file I have won't work now. I need the MJ7 odin file now or else my phone is a paperweight until then.
Someone else did this 2, you can't use this method because it FLASHES A ROOTED Ml1 Rom....... Odin file still has not been posted yet
Sent From My Hyperdriven S4
ebsk8er06 said:
Someone else did this 2, you can't use this method because it FLASHES A ROOTED Ml1 Rom....... Odin file still has not been posted yet
Sent From My Hyperdriven S4
Click to expand...
Click to collapse
Yeah I thought I read that it would still work. I'll just have to wait for the Odin file
I am in the same boat, my phone is unbootable and I am waiting for the MJ7 odin file or my replacement phone
villainous said:
I am in the same boat, my phone is unbootable and I am waiting for the MJ7 odin file or my replacement phone
Click to expand...
Click to collapse
thankfully i have an iphone i can use for now. surprisingly i went to boot up my phone just now and it went through almost the whole boot process. it's stuck on the verizon splash. last night it would just go straight into odin.
I am not so lucky as to have a backup phone
I should look for a cheap 4g phone to keep in a drawer for such occasions. Hopefully an MJ7 file is made available soon so I can recovery my files before my new phone arrives.
villainous said:
I am not so lucky as to have a backup phone
I should look for a cheap 4g phone to keep in a drawer for such occasions. Hopefully an MJ7 file is made available soon so I can recovery my files before my new phone arrives.
Click to expand...
Click to collapse
I'm sure it will. In a few days. I'm surprised the verizon repair tool doesn't have MJ7.... maybe that'll take a while too.
antisomnic said:
thankfully i have an iphone i can use for now. surprisingly i went to boot up my phone just now and it went through almost the whole boot process. it's stuck on the verizon splash. last night it would just go straight into odin.
Click to expand...
Click to collapse
You might be able to get it into recovery and manually use the update.zip.
It is reported that at least a few people have been able to get out of the state you are in my using a manual update.
tech_head said:
You might be able to get it into recovery and manually use the update.zip.
It is reported that at least a few people have been able to get out of the state you are in my using a manual update.
Click to expand...
Click to collapse
yeah i actually did that and have been using my s4 for a few days
open1your1eyes0 posted [ODIN][TAR] Complete Device Wipe/Repartition and Emergency Recovery for VRUEMJ7 Build in the dev forum.
This is an ODIN factory image similar to the one posted here but this is an emergency recovery image that will help you recover and restore your device from nearly ANY possible soft-brick by entirely wiping, refreshing, and repartitioning your device to out-of-box OEM firmware.
WARNING: Please use this with caution as this will wipe your ENTIRE device with no chance of restoring back old data afterwords!
How to Use
Download file from: http://www.androidfilehost.com/?fid=23203820527944861
Unzip file to your computer (desktop or some location)
Use ODIN v3.09 to flash in AP section once your device is connected
Click to expand...
Click to collapse
And joderme has a VRUEMJ7 no wipe ODIN image available in dev too.
--OctOS Powered VZW GS4 Dev Edition
antisomnic said:
yeah i actually did that and have been using my s4 for a few days
Click to expand...
Click to collapse
So I rooted and updated to MJ7 all went well. Then tried to install twrp not realizing it wont work. Now I'm stuck into download mode and yellow triangle. Is there not a way to odin back to stock since I have this update. Need help.
mickrg123 said:
So I rooted and updated to MJ7 all went well. Then tried to install twrp not realizing it wont work. Now I'm stuck into download mode and yellow triangle. Is there not a way to odin back to stock since I have this update. Need help.
Click to expand...
Click to collapse
Untested, but you can unzip the attached and flash it in ODIN - it's the stock MJ7 recovery. With a bit of luck that'll get you repaired.
If not, flash the no-wipe MJ7 ROM from the Android Development forum, but that'll probably cause you to lose root.
Bait-Fish said:
open1your1eyes0 posted [ODIN][TAR] Complete Device Wipe/Repartition and Emergency Recovery for VRUEMJ7 Build in the dev forum.
And joderme has a VRUEMJ7 no wipe ODIN image available in dev too.
--OctOS Powered VZW GS4 Dev Edition
Click to expand...
Click to collapse
wrong post
Awesome
You know... I don't post much if at all on xda. Mostly im an intel junkie but I have to say after bricking my 24 hour old MJ7 s4 and fully recovering it using this post you guys are ****ing AWESOME!
FYI The exact steps I took were as follows using windows 8.1 pro x64
downloaded Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0
downloaded Odin3 v3.07
downloaded ALL_I545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low_ship_MULTI_CERT.tar.md5
Install Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0 drivers
Ran odin as administrator, left defaults checked and chose PDA ALL_I545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low_ship_MULTI_CERT.tar.md5
(Windows hangs when trying to first browse the file, WAIT)
plugged phone in and got instant com green and hit start. Waited 20 mins and it all went through successfully.
USERS NOTE:
The first computer I tried just absolutely would not flash this phone. Drivers where correct etc it just seemed like it dropped connection. Tried 3 separate usb ports one even off a powered hub and all failed on the system flash. Changed computers and followed the same setup and went first try. If it fails try and try again. Changing different ports, computers, and or drivers helps if you get failure messages.
Thanks to all of you!
SmOoThEm said:
You know... I don't post much if at all on xda. Mostly im an intel junkie but I have to say after bricking my 24 hour old MJ7 s4 and fully recovering it using this post you guys are ****ing AWESOME!
FYI The exact steps I took were as follows using windows 8.1 pro x64
downloaded Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0
downloaded Odin3 v3.07
downloaded ALL_I545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low_ship_MULTI_CERT.tar.md5
Install Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0 drivers
Ran odin as administrator, left defaults checked and chose PDA ALL_I545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low_ship_MULTI_CERT.tar.md5
(Windows hangs when trying to first browse the file, WAIT)
plugged phone in and got instant com green and hit start. Waited 20 mins and it all went through successfully.
USERS NOTE:
The first computer I tried just absolutely would not flash this phone. Drivers where correct etc it just seemed like it dropped connection. Tried 3 separate usb ports one even off a powered hub and all failed on the system flash. Changed computers and followed the same setup and went first try. If it fails try and try again. Changing different ports, computers, and or drivers helps if you get failure messages.
Thanks to all of you!
Click to expand...
Click to collapse
Where can I grab ALL_I545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low _ship_MULTI_CERT.tar.md5 ??
emtownsend said:
Where can I grab ALL_I545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low _ship_MULTI_CERT.tar.md5 ??
Click to expand...
Click to collapse
http://www.androidfilehost.com/?fid=23203820527944861
Bait-Fish said:
open1your1eyes0 posted [ODIN][TAR] Complete Device Wipe/Repartition and Emergency Recovery for VRUEMJ7 Build in the dev forum.
And joderme has a VRUEMJ7 no wipe ODIN image available in dev too.
--OctOS Powered VZW GS4 Dev Edition
Click to expand...
Click to collapse
antisomnic said:
Yeah I thought I read that it would still work. I'll just have to wait for the Odin file
Click to expand...
Click to collapse
antisomnic said:
I did the OTA update from M1I to MJ7 and read somewhere that the M1I root method would work. It made my phone unbootable. Obviously the M1I file I have won't work now. I need the MJ7 odin file now or else my phone is a paperweight until then.
Click to expand...
Click to collapse
Just an FYI. Whenever you take an OTA from the Carrier it's written so you cannot revert back to an earlier build or a soft and possible hard brick can occur. This has been discussed numerous times in various forums. You were lucky this time.
Related
Alright guys as my title states I pulled a "noob move" and it looks like I've soft bricked my phone (It won't boot past the verizon splash screen). I've done a little research and I'm pretty familiar with Odin and how it works. Seems to be the same concept as jungle flasher and I've modded a few 360's in my time. I've tried, to no avail, to flash my phone back with the stock image numerous times and I figured it was time to consult the experts. What I've done so far: Downloaded the factory stock restore TAR from Rwilco12's site and put that in the PDA file browser of Odin. My phone shows up in Odin when connected in download mode with a light blue com:4 box. I read sometimes this is supposed to be yellow? Other versions of Odin it is yellow. This instance was attempted in 3.07. 1.85 it shows up as yellow. Regardless of either version, they both fail after the "aboot" step. I've tried two computers and have failed miserably all morning. Any help or advice would be much appreciated.
-Be easy on me, it's my first time.
-HerdOn
HerdOn said:
Alright guys as my title states I pulled a "noob move" and it looks like I've soft bricked my phone (It won't boot past the verizon splash screen). I've done a little research and I'm pretty familiar with Odin and how it works. Seems to be the same concept as jungle flasher and I've modded a few 360's in my time. I've tried, to no avail, to flash my phone back with the stock image numerous times and I figured it was time to consult the experts. What I've done so far: Downloaded the factory stock restore TAR from Rwilco12's site and put that in the PDA file browser of Odin. My phone shows up in Odin when connected in download mode with a light blue com:4 box. I read sometimes this is supposed to be yellow? Other versions of Odin it is yellow. This instance was attempted in 3.07. 1.85 it shows up as yellow. Regardless of either version, they both fail after the "aboot" step. I've tried two computers and have failed miserably all morning. Any help or advice would be much appreciated.
-Be easy on me, it's my first time.
-HerdOn
Click to expand...
Click to collapse
Have you tried a different USB cable and/or running odin as an administrator?
BladeRunner said:
Have you tried a different USB cable and/or running odin as an administrator?
Click to expand...
Click to collapse
Yes, I've used the factory samsung and another cable while running as an administrator. Thanks for the thought though!
HerdOn said:
Yes, I've used the factory samsung and another cable while running as an administrator. Thanks for the thought though!
Click to expand...
Click to collapse
which Verizon release are you on VRUAMDK or VRUAME7?
BladeRunner said:
which Verizon release are you on VRUAMDK or ?
Click to expand...
Click to collapse
VRUAME7 is the most recent with the latest OTA update correct? If so that's the one I was on. Now I did root it successfully initially, it got stuck this way after installing SuperSU... I guess I should have said that initially. My apologies.
HerdOn said:
VRUAME7 is the most recent with the latest OTA update correct? If so that's the one I was on. Now I did root it successfully initially, it got stuck this way after installing SuperSU... I guess I should have said that initially. My apologies.
Click to expand...
Click to collapse
ME7 is the current OTA, yes. Are you using the correct .TAR file from here? http://www.androidfilehost.com/?fid=23032113221600748? Also did you try doing a data wipe/factory reset in stock android recovery?
BladeRunner said:
ME7 is the current OTA, yes. Are you using the correct .TAR file from here? Also did you try doing a data wipe/factory reset in stock android recovery?
Click to expand...
Click to collapse
The link you sent was broken, I'm using the rwilco12 factory image. It wont let me post a link because I don't have enough posts.
I have tried doing the data wipe/factory reset but it kept saying error. and now it says Firmware upgrade encountered an issue please select recovery mode in kies and try again. That's when going to the volume up "recovery" mode. Volume down, "download" mode still works fine.
http://www.androidfilehost.com/?fid=23032113221600748
The link BladeRunner posted had an extra question mark. Try that one.
Sent from my SCH-I545 using xda app-developers app
HerdOn said:
The link you sent was broken, I'm using the rwilco12 factory image. It wont let me post a link because I don't have enough posts.
I have tried doing the data wipe/factory reset but it kept saying error. and now it says Firmware upgrade encountered an issue please select recovery mode in kies and try again. That's when going to the volume up "recovery" mode. Volume down, "download" mode still works fine.
Click to expand...
Click to collapse
sorry, here is the link to the Odin files thread: http://forum.xda-developers.com/showthread.php?t=2301259 Download the VRAUME7 factory image. I'm not sure but I think you may have the MDK image from RWILCO and there's no going back to that once you've updated to ME7.
---------- Post added at 02:26 PM ---------- Previous post was at 02:25 PM ----------
Checkm8 said:
http://www.androidfilehost.com/?fid=23032113221600748
The link BladeRunner posted had an extra question mark. Try that one.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Thanks! Don't know where that extra "?" came from
Alright I'm downloading that version now. Its capping my connection so it should be done in 25 mins and we'll try again! Thanks for your help so far bladerunner. Seems like we're getting somewhere...
Bladerunner, you were right my friend! The image is finally going to the phone. After nearly pulling all of my hair out, we're making extreme progress!
Ten minutes later my phone is back to factory flawless condition. Thanks Bladerunner for all your help! It's very much appreciated..
HerdOn said:
Ten minutes later my phone is back to factory flawless condition. Thanks Bladerunner for all your help! It's very much appreciated..
Click to expand...
Click to collapse
Excellent! No problem
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 was originally trying to just go to the new kitkat rom, i believe that was CM11 or something of the sort. But for some reason i cannot do anything with my phone when it comes to installing or changing the recovery. Odin fails every time. One-Click-Root fails every time (which i think is what i used from the beginning to root). I even upgraded ROM manager to pro so i could try the touch based recovery and it will not successfully install a recovery that i can boot into even though it says that it has and shows(ed) the current recovery being the most up-to-date version. And now since ive tried several different today, i have lost root somehow...even thought i just had it and didnt change anything with the root process...just trying to regain even the stock recovery. Basically what happens if i try to boot into recovery mode is it tries for half a second then boots to ODIN mode and in the top left corner it says failed normal boot or something of the sort.
Can someone point me in the right direction? would a factory reset within the android OS help anything? every thing is backed up, so that wont be an issue as far as apps/data and important files goes.
The phone still boots to my "rooted" 4.3 that i have installed, just dont have root privelages any longer...the phone still works as normal...just cant do anything root based...like run titanium backup or supersu, and even ROM manager is NOW giving me an error when trying to install a custom recovery.
I would like to restore to stock MDK so i can start from scratch and install the CM11 KitKat Rom if at all possible...
So you were mdk and loki'd correct...
safestrap powered Hyperdrive 12
decaturbob said:
So you were mdk and loki'd correct...
safestrap powered Hyperdrive 12
Click to expand...
Click to collapse
MDK yes, the loki part im not sure of...but i did try to do that again since having this problem...with no success...
MURD3RD said:
MDK yes, the loki part im not sure of...but i did try to do that again since having this problem...with no success...
Click to expand...
Click to collapse
you would have to to use the loki process to gain root and install the custom recovery at the time. I really can't help as I got into the S4 with ME7 base and been using safestrap.
i also tried following this link
http://forum.xda-developers.com/showthread.php?t=2290798
and it doesnt get past the first ODIN step and gets a fail
attached are some snips of the ODIN screen when it fails
decaturbob said:
you would have to to use the loki process to gain root and install the custom recovery at the time. I really can't help as I got into the S4 with ME7 base and been using safestrap.
Click to expand...
Click to collapse
you got a link to a good working Loki tutorial?
Here's a link to the stock mdk tar file. This will totally wipe your phone. http://www.sxtpdevelopers.com/showthread.php?t=237
Ryno77 said:
Here's a link to the stock mdk tar file. This will totally wipe your phone.
Click to expand...
Click to collapse
i did find that link before and am currently downloading it...but it is taking forever...everything else i download is blazing fast (50Mb D/L speed here at my buddies apartment) but yet this file is only downloading at 50KB/s...and is showing over 9-10 hours for the download to be complete...does anybody have a faster download source?
i know my connection is phenomenal since i downloaded a 9 gig file last night from a different source and it took under an hour...this .tar is less than 2 gigs...shouldnt take that damn long...
i also tried flashing the recovery .tar.md5 from that link...same exact result...
Questions and Help issues go in Q&A and Help section
Thread moved
Thanks
FNSM
kennyglass123 said:
Questions and Help issues go in Q&A and Help section
Thread moved
Thanks
FNSM
Click to expand...
Click to collapse
THANKS!!!
I knew i hadn't put it in the right place...hopefully it'll get more view here...and i can get this thing sorted out
so right now the screen shows (phone)--(yellow triangle)--(computer) and says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
this is after trying to install the stock restore .tar files in the link mentioned above...the device will NO LONGER boot the os and goes to this screen every time. I can still get it into download (Odin) mode though.
MURD3RD said:
i also tried following this link
http://forum.xda-developers.com/showthread.php?t=2290798
and it doesnt get past the first ODIN step and gets a fail
attached are some snips of the ODIN screen when it fails
Click to expand...
Click to collapse
The "fail (auth)" means that you're likely no longer running an MDK bootloader. It's refusing to load the MD2 that's used by Loki.
Do you get the same failure when you try to flash the stock MDK ROM image? What text shows up on your phone when you try to flash the stock?
Since you're stuck at the "Firmware upgrade encountered an issue." it indicates that the bootloader rejected a flash, which means you may have somehow updated to MI1 or later. The message on the phone when the flash fails will tell for sure.
k1mu said:
The "fail (auth)" means that you're likely no longer running an MDK bootloader. It's refusing to load the MD2 that's used by Loki.
Do you get the same failure when you try to flash the stock MDK ROM image? What text shows up on your phone when you try to flash the stock?
Since you're stuck at the "Firmware upgrade encountered an issue." it indicates that the bootloader rejected a flash, which means you may have somehow updated to MI1 or later. The message on the phone when the flash fails will tell for sure.
Click to expand...
Click to collapse
i can't remember what exactly the messages were right now...but currently Kies is trying a recovery "upgrade and initialization"...hopefully this works and my phone can at least be usable again...and THEN ill get back at trying to get the new KitKat, lol
MURD3RD said:
i can't remember what exactly the messages were right now...but currently Kies is trying a recovery "upgrade and initialization"...hopefully this works and my phone can at least be usable again...and THEN ill get back at trying to get the new KitKat, lol
Click to expand...
Click to collapse
You won't be on MDK, so no KitKat.
k1mu said:
You won't be on MDK, so no KitKat.
Click to expand...
Click to collapse
but i have had no problem flashing back to get rooted when i first got the device...even though several threads said it couldnt be done...all i need is to get back to stock and start from scratch...at least i hope this is the case. If it goes ahead and installs the newest 4.3 update...and i truly cant change it due to no exploits yet...then i guess ill have to wait...lol, it could be worse, haha
so kies just finished doing its thing and the phone booted up and is now running 4.3 MK2
MURD3RD said:
so kies just finished doing its thing and the phone booted up and is now running 4.3 MK2
Click to expand...
Click to collapse
That means you lost the mdk bootloader and can only use Safestrap to boot custom rooms :/ you will need to root via saferoot in the development thread first. Then load Safestrap which only has one ROM that currently works (hyper drive 12).
gnubian said:
That means you lost the mdk bootloader and can only use Safestrap to boot custom rooms :/ you will need to root via saferoot in the development thread first. Then load Safestrap which only has one ROM that currently works (hyper drive 12).
Click to expand...
Click to collapse
EDIT: well nevermind...i think i was just crazy to think something different...i am definitely running the latest release of 4.3 from vzw...fml...well at least it can still be rooted. Is there any development for KitKat on the new MK2 software? Ill do some searching around...
i do remember, however, doing something that a tutorial said specifically not to do...and it worked anyway...even though several people responding to the thread said not to do or it would brick the phone...o well i guess...if i find the link ill post it up...
gnubian said:
That means you lost the mdk bootloader and can only use Safestrap to boot custom rooms :/ you will need to root via saferoot in the development thread first. Then load Safestrap which only has one ROM that currently works (hyper drive 12).
Click to expand...
Click to collapse
would you happen to have a link to the safestrap tutorial? i cant seem to locate it...im gunna do some more searching, but if you had a link at the ready, that'd be awesome!!!
EDIT: Found it...no worries
gnubian said:
That means you lost the mdk bootloader and can only use Safestrap to boot custom rooms :/ you will need to root via saferoot in the development thread first. Then load Safestrap which only has one ROM that currently works (hyper drive 12).
Click to expand...
Click to collapse
so i found the thread for this ROM and it doesnt say anything about being able to run on MK2 build...can anyone shed some light on this? it only says MJ7...
I went to upgrade to the new hyperdrive since they sent me the ota. Phone has been acting weird so I was going to do a complete wipe. I took my sd card out which my son took and lost on me and OI can find anywhere. I had another card so d/l new hyperdrive onto other card. I went to wipe cache and install new rom. phone wiped data and now wouldnt install new rom. I dont remember all the build I was on on the phone but I had Hyperdrive 16 before I started this if that helps at all. I am stuck on samsung custom boot screen. I can get into odin recovery and tried recovery but keeps failing. can I get some help I need my phone i have to go to work soon. Thanks
ive tried the rootjunky video with both no wipe and full wipe neither worked. odin failed.
FlipFlop425 said:
ive tried the rootjunky video with both no wipe and full wipe neither worked. odin failed.
Click to expand...
Click to collapse
What files are you trying to flash? Did you use Safestrap to install RLS16?
Sent from my NCC-1701 using Tapatalk.
i had downloaded the new update for hyper drive. Right now my biggest probelm is I cannot get past the splash screen. I can get into download mode though so can we try to figure out how to unbrick me first. Download mode is the only thing I can seem to get into right now
FlipFlop425 said:
i had downloaded the new update for hyper drive. Right now my biggest probelm is I cannot get past the splash screen. I can get into download mode though so can we try to figure out how to unbrick me first. Download mode is the only thing I can seem to get into right now
Click to expand...
Click to collapse
That's why I need to know if you used Safestrap as your recovery. It's very likely you're trying to flash the wrong file with Odin.
If you had Safestrap your build wasn't MDK. If you didn't need Safestrap then your build was MDK.
So I'll ask again, what file are you trying to flash, with Odin, that keeps failing?
riker147 said:
That's why I need to know if you used Safestrap as your recovery. It's very likely you're trying to flash the wrong file with Odin.
If you had Safestrap your build wasn't MDK. If you didn't need Safestrap then your build was MDK.
So I'll ask again, what file are you trying to flash, with Odin, that keeps failing?
Click to expand...
Click to collapse
I used to have to use safestrap. I was trying to flash the mdk file from rootjunky's video on unbricking your phone
FlipFlop425 said:
I used to have to use safestrap. I was trying to flash the mdk file from rootjunky's video on unbricking your phone
Click to expand...
Click to collapse
NO!!! You cannot flash the MDK file, you cannot downgrade the S4! Always ends badly, go to the general section and grab the NC5 full-wipe tar and flash with ODIN.
npjohnson said:
NO!!! You cannot flash the MDK file, you cannot downgrade the S4! Always ends badly, go to the general section and grab the NC5 full-wipe tar and flash with ODIN.
Click to expand...
Click to collapse
I have tried that from SUrge1223. That did not work for me. I cannot get in to my phone to re root it. Is that the right file the one from him?
FlipFlop425 said:
I have tried that from SUrge1223. That did not work for me. I cannot get in to my phone to re root it. Is that the right file the one from him?
Click to expand...
Click to collapse
From here http://forum.xda-developers.com/showthread.php?t=2735172. I would choose the "Full Wipe" version. Make sure you have a good download. Check MD5. Make sure you follow the directions for Odin. If you verify all of that, and it still doesn't work, I'm afraid I won't be any more help. Someone with more knowledge than I have will have to step in. Good luck.
riker147 said:
From here http://forum.xda-developers.com/showthread.php?t=2735172. I would choose the "Full Wipe" version. Make sure you have a good download. Check MD5. Make sure you follow the directions for Odin. If you verify all of that, and it still doesn't work, I'm afraid I won't be any more help. Someone with more knowledge than I have will have to step in. Good luck.
Click to expand...
Click to collapse
I can vouch for the full Version. Saved my bacon.
You have to boot the phone into a special mode that will allow ODIN to funtion
Turn off the SGS4 and boot it into Download/Odin Mode: press and hold the Volume Down, Home and Power buttons simultaneously for a couple of seconds till you see a warning screen. Then press Volume Upkey to enter Download Mode.
I got it!!! Found my Samsung cable and all went well. TY for ALL the help!
FlipFlop425 said:
I got it!!! Found my Samsung cable and all went well. TY for ALL the help!
Click to expand...
Click to collapse
Yeah, it is a really good feeling when that ODIN starts to run like it means it. Nothing beats that first boot up!
I have a S4 i545 for Verizon. It was on 4.2.2 rooted and I upgraded using Fireflash with I545_OC1_Stock_DeOdexed_ROMwNK4_BL.zip. Everything seemed fine so I was using Titanium back up to remove the bloatware and then my battery died. When I charged it and booted up it got to the Verizon screen and hung there. I reset and tried several more times. I tried to use odin and flash a stock 4.2.2 ROM SCH-I545_VZW_1_20140330160240_yni63xq6zh and I also tried a 4.4.2 rom. Odin gave a an error and failed. I then tried going into the boot loader and flash the I545_OC1_Stock_DeOdexed_ROMwNK4_BL.zip also. Not sure if this was foolish or not but when I booted up I got to a black screen and there was a voice talking, maybe some sort of app that was running, but I couldn't do anything.
Right now when I turn on the phone it says firmware upgrade encountered an issue. Please select recovery mode in kies and try again. I tried connecting it to my computer and opening kies but it doesn't find it. If anyone can point me in the right direction on how to unbrick my S4 I would appreciate it. I know I screwed up.
as long as you can access ODIN you can unbrick. since your on 4.4.2 get the original rom and install. re root and install your rom of choice. from there if you have a previous backup in titanium you can restore
Sent from my LG-D415 using Tapatalk
I was on 4.2.2. I tried downloading the original ROM for this but it didn't work in Odin.
Problem is I can't get into download mode now, or recovery mode even. It's just at that screen I mentioned above. So Odin isn't recognizing my phone.
thats outside my knowledge base. sorry. good luck
Sent from my LG-D415 using Tapatalk
bump up
dr0832 said:
Problem is I can't get into download mode now, or recovery mode even. It's just at that screen I mentioned above. So Odin isn't recognizing my phone.
Click to expand...
Click to collapse
so if you hold down VOL- and power it doesn't go into download mode?
It won't be recognized in Odin until you get back to download mode. - in Odin then you'd want to flash the PIT file and the ROM you need.
The only other way to fix would be to get ahold of a copy of Verizon's Software Upgrade Assistant/Software Recovery Assistant, which looks like someone has uploaded here:
http://forum.xda-developers.com/showthread.php?t=2469615
The Software Recovery Assistant should fix it if nothing else does, I have used it before.
No when I turn it on it goes straight to the screen I mention with a yellow triangle and it does the same if I hold all the buttons down like you normally would to get in recovery.
I assume a battery pull didn't help. Since you have MDK, it MIGHT be worth it to get the JTAG dongle, which will boot the phone into download mode. It is about 3 bucks.
I tried installing in windows xp, windows 7 and windows 8 with no luck. I clicked the exe and it does nothing. I then tried installing on a MAC. It installed but when I went to run it the software opened for 1 second and then close with an error software closed unexpectedly. The I updated the software on the MAC and the software opened but the second I plugged in the phone it gave the same error. The MAC did find the phone though but windows did not.
bump
dr0832 said:
bump
Click to expand...
Click to collapse
Just plug the phone (on that screen) into your PC and see if it shows up in Odin.
If not, pull the battery, and hold the volume down and power buttons as you put the battery back in. Then choose Continue.
Did you read my post? I have done that. My phone is hard bricked. I can't get into recovery mode and therefore I can't get into download mode so therefore odin won't find my phone.
dr0832 said:
Did you read my post? I have done that. My phone is hard bricked. I can't get into recovery mode and therefore I can't get into download mode so therefore odin won't find my phone.
Click to expand...
Click to collapse
Which ROM did you flash, link?
Ahhh. The linked version of the Verizon Software Upgrade Assistant doesn't work. Sorry about that.
I just pulled the .iso from my S4 and posted it up, try this one: https://www.androidfilehost.com/?fid=24052804347780563
Per npjohnson advice I was able to get the phone into download mode. I misread your post at first so sorry about that. Now I need to figure out how to fix this. I flashed Lollipop originally so does that mean I can't actually go back to 4.2.2 using a stock ROM? Can someone point me to a ROM I should try to flash since the so called stock ROM's I have tried are failing in Odin.
I tried flashing this one:
http://stockroms.net/file/GalaxyS4/SCH-i545/VRUAMDK_NoWipe.tar.zip
It came from here:
http://galaxys4root.com/galaxy-s4-stock-firmware/
As for the Verizon assistant that was just posted it does not install just like the other. I click it and the screen flashed and then it does nothing.
dr0832 said:
Per npjohnson advice I was able to get the phone into download mode. I misread your post at first so sorry about that. Now I need to figure out how to fix this. I flashed Lollipop originally so does that mean I can't actually go back to 4.2.2 using a stock ROM? Can someone point me to a ROM I should try to flash since the so called stock ROM's I have tried are failing in Odin.
I tried flashing this one:
http://stockroms.net/file/GalaxyS4/SCH-i545/VRUAMDK_NoWipe.tar.zip
It came from here:
http://galaxys4root.com/galaxy-s4-stock-firmware/
As for the Verizon assistant that was just posted it does not install just like the other. I click it and the screen flashed and then it does nothing.
Click to expand...
Click to collapse
What lollipop did you flash originally? OTA?
I was rooted and then I flashed I545_OC1_Stock_DeOdexed_ROMwNK4_BL which I think is android 5.0.1. I used flashfire.
This was the thread I followed:
http://forum.xda-developers.com/gal...-to-update-to-i545oc1-5-0-1-keeproot-t3096558
Did the battery die on you? I think this is where you need the debrick image....
dr0832 said:
I was rooted and then I flashed I545_OC1_Stock_DeOdexed_ROMwNK4_BL which I think is android 5.0.1. I used flashfire.
This was the thread I followed:
http://forum.xda-developers.com/gal...-to-update-to-i545oc1-5-0-1-keeproot-t3096558
Click to expand...
Click to collapse
Probably should try the full factory image linked here: http://forum.xda-developers.com/gal...pment/odin-i545vrugoc1-factory-image-t3160125
That will put you on 5.0.1 OC1 including bootloader. You'll then root with Kingroot, use Super-sume to replace Kingroot with SuperSu and then you can use the NON-MDK ROM with FlashFire. (odex, or deodex if you want to use xposed modules.