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
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
Tried posting this as a reply in a similar thread but I think the thread died so forgive me for double posting.
I rooted my stock S4 and installed the proper TWRP.
Heres where my situation is a bit different from anything I have seen on the forum threads. All attempts—both hard and soft—to reboot into recovery, all direct the reboot to Odin Mode. Just to clarify I have not flashed any rom custom or stock, the only thing I have flashed has been TWRP and CWM recovery. And I only flashed CWM AFTER the Failings of TWRP.
When I attempt to boot into recovery, it flashes the blue characters then sends me into a Odin Mode loop until I hard-key the "download mode" and select restart to boot the os normally.
my phone works fine other than not being able to flash custom roms, which is a pain in the arse especially with all the s4 Bloatware.
Here's what I have done so far to help myself:
• install CWM recovery
• tried hard-key reboot recovery (power off/ press home/volume up/power)
• soft reboot recovery through both Goo, CWM and ROM Toolbox pro
• removed my sd card and tried reboot recovery
• removed battery and reboot recovery
• emulator reboot recovery
• reboot recovery both with and without usb cable
I looked into flashing stock with Odin but all tutorials i could find were of an older version and I didnt want to guess what I needed to get that to work,
Please let me know if theres anything I can do.
(Verizon) Samsung Galaxy S4 jfltevzw
filthysanches said:
Tried posting this as a reply in a similar thread but I think the thread died so forgive me for double posting.
I rooted my stock S4 and installed the proper TWRP.
Heres where my situation is a bit different from anything I have seen on the forum threads. All attempts—both hard and soft—to reboot into recovery, all direct the reboot to Odin Mode. Just to clarify I have not flashed any rom custom or stock, the only thing I have flashed has been TWRP and CWM recovery. And I only flashed CWM AFTER the Failings of TWRP.
When I attempt to boot into recovery, it flashes the blue characters then sends me into a Odin Mode loop until I hard-key the "download mode" and select restart to boot the os normally.
my phone works fine other than not being able to flash custom roms, which is a pain in the arse especially with all the s4 Bloatware.
Here's what I have done so far to help myself:
• install CWM recovery
• tried hard-key reboot recovery (power off/ press home/volume up/power)
• soft reboot recovery through both Goo, CWM and ROM Toolbox pro
• removed my sd card and tried reboot recovery
• removed battery and reboot recovery
• emulator reboot recovery
• reboot recovery both with and without usb cable
I looked into flashing stock with Odin but all tutorials i could find were of an older version and I didnt want to guess what I needed to get that to work,
Please let me know if theres anything I can do.
(Verizon) Samsung Galaxy S4 jfltevzw
Click to expand...
Click to collapse
you are probably on the ME7 build, which means no recovery is available,
Youre on me7 and you cant install custom recovery or custom roms while on me7, if you were reading other threads I dont know how you missed it because its been posted about a hundred times. You can use the buttom combo to boot into download mode and then cancel and your phone should boot normally. Everytime you try to go into recovery youre going to get put into download mode so eventually youre going to have to flash the me7 stock image or flash stock recovery, recovery I dont have a link for but the stock images are posted in the dev section.
Sent from my SCH-I545 using Tapatalk 2
JaeKay said:
you are probably on the ME7 build, which means no recovery is available,
Click to expand...
Click to collapse
Thanks you are very right, I wasn't aware that was a thing. Hopefully someone is working on it.
filthysanches said:
Thanks you are very right, I wasn't aware that was a thing. Hopefully someone is working on it.
Click to expand...
Click to collapse
People are check out the bounty and safestrap threads in the general section.
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
Youre on me7 and you cant install custom recovery or custom roms while on me7, if you were reading other threads I dont know how you missed it because its been posted about a hundred times. You can use the buttom combo to boot into download mode and then cancel and your phone should boot normally. Everytime you try to go into recovery youre going to get put into download mode so eventually youre going to have to flash the me7 stock image or flash stock recovery, recovery I dont have a link for but the stock images are posted in the dev section.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
I missed it because I didn't think it would be a build version issue I thought it was user error (which I guess it is) but my searches were conducted with that ignorance, we all have to start somewhere.
So If I understand you correctly now that I have installed a custom recovery (that doesn't work with ME7), I will now have to find and flash the stock recovery in order to flash a custom recovery if and when one is available for ME7?
filthysanches said:
I missed it because I didn't think it would be a build version issue I thought it was user error (which I guess it is) but my searches were conducted with that ignorance, we all have to start somewhere.
So If I understand you correctly now that I have installed a custom recovery (that doesn't work with ME7), I will now have to find and flash the stock recovery in order to flash a custom recovery if and when one is available for ME7?
Click to expand...
Click to collapse
Youre right we all have to start somewhere, chalk it up as a learning experience. When I say flashing the stock recovery im just saying it so youll have a recovery period. When one comes out for me7 tho having a stock recovery prior shouldnt be mandatory. I do recommend having the stock recovery tho
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
Youre right we all have to start somewhere, chalk it up as a learning experience. When I say flashing the stock recovery im just saying it so youll have a recovery period. When one comes out for me7 tho having a stock recovery prior shouldnt be mandatory. I do recommend having the stock recovery tho
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Yeah not having a stock recovery is a bit sketch, Ill have to find and flash it soon.
If you cant find it and have apps/data u dont want to lose there is a no wipe me7 stock image you can flash to get it back as well. I did see the stock recoveries posted before but I for the life of me cant find them again.
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
If you cant find it and have apps/data u dont want to lose there is a no wipe me7 stock image you can flash to get it back as well. I did see the stock recoveries posted before but I for the life of me cant find them again.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
I saw somewhere the other day with a Me7 stock image I'll see if I can hunt it down. If I find it, I'll reference it here. Thanks for the help, I'd would have been clueless otherwise.
Same issue
Yes please post a link to the stock recovery if you find it I just did the exact same thing and missed the fact that the VRUME7 won't work with custom recoveries. Didn't help that I was trying a post that said it would from GalaxyS4Root.com and when it didn't work I tried a workaround using adb to force it. I'm new to this like you and now I know better too, well at least I hope. Also once any of us finds an image of the stock recovery would I just use ODIN to flash it from my pc or would I have to use some other method? I know I know most likely a stupid question but I rather get a chuckle on here then screw this up even more. I will post a link too if I find a stock recovery image. Thanks again.
---------- Post added at 10:46 AM ---------- Previous post was at 10:36 AM ----------
Tos83 said:
Yes please post a link to the stock recovery if you find it I just did the exact same thing and missed the fact that the VRUME7 won't work with custom recoveries. Didn't help that I was trying a post that said it would from GalaxyS4Root.com and when it didn't work I tried a workaround using adb to force it. I'm new to this like you and now I know better too, well at least I hope. Also once any of us finds an image of the stock recovery would I just use ODIN to flash it from my pc or would I have to use some other method? I know I know most likely a stupid question but I rather get a chuckle on here then screw this up even more. I will post a link too if I find a stock recovery image. Thanks again.
Click to expand...
Click to collapse
I'm not certain if this helps at all but I just found this thread about safestrap for VRUAME7 and it's only a few days old as well as being older than your last posts. Not sure if you need the original stock recovery in place first and I haven't had time to do a full read of this post yet but maybe it can help get both of us further along. Anyway here is the link, check it out.
http://forum.xda-developers.com/showthread.php?t=2441441&styleid=18
Hi I tried to root my phone using this method ( http://forum.xda-developers.com/showthread.php?t=1504218 ) and it left my phone stuck on the reboot. I then tried to flash the stock kernel via odin, and when that didn't work I flashed cwm via odin and then a rogers kernel through cwm and it is still stuck on the rogers logo.......?
could someone help me......?
AirForce 1 said:
Hi I tried to root my phone using this method ( http://forum.xda-developers.com/showthread.php?t=1504218 ) and it left my phone stuck on the reboot. I then tried to flash the stock kernel via odin, and when that didn't work I flashed cwm via odin and then a rogers kernel through cwm and it is still stuck on the rogers logo.......?
could someone help me......?
Click to expand...
Click to collapse
I see your post count and realize you cannot post in the development section yet. that should not however stop you from reading. maybe you have but you may not have read the whole thread. i know that may seem like a daunting task, it is for me. so what I o is go to the most recent post or last page and start reading backwards. that way I get the most up to date information even on an older thread as you are referring to.
if you did that you would have seen a post from AGOATTAMER.
http://rootgalaxynote.com/galaxy-note-i717-roms/how-to-root-att-galaxy-note-sgh-i717-icsgingerbreadeasiest-method/
this is also the method I used. believe me, if I can pull it off, anybody can.
more tips..............
make sure you have all the files you need
rehearse the process
I know it sounds crazy, but these phones aint cheap and if you mess it up, can be pretty screwed.
so what is more valuable???? your phone or acting crazy and talking to yourself for a few minutes.
if you can still get download mode, your good, no brick
good luck
You flashed an older incompatible kernel with a newer ROM, but I guess you know that now. Flash the stock ROM found here using odin.
http://www.hotfile.com/dl/213010140/75bf7e2/I717RUXMD1_I717RRWCMD1_RWC.zip.html
Go into recovery after install and do a factory reset. Then start over. Many have used the link that captemo has mentioned. There are newer versions of recovery than the one listed on that site but it will get you rooted. Look at this thread also. Since you are installing the stock ROM via odin you will not have to deal with the script mentioned here.
http://forum.xda-developers.com/showthread.php?t=2485336
Just flash twrp with Odin, don't reboot into android, not directly into recovery after the flash finishes...
In recovery wipe data/factory reset.
When you go to boot it'll see you're not rooted and ask if you want to.
The easiest method to root.
Edit: note to self
Self,
check links before posting to avoid repeating yourself
studacris said:
Edit: note to self
Self,
check links before posting to avoid repeating yourself
Click to expand...
Click to collapse
Good advice is always worth repeating.
Sent from my Big Ass Outlaw Phone.
Hey guys --
I just was messing around with my S4 trying to get custom recovery on there (now I realize I can't), but I tried to install TWRP using TWRP manager. After it installed, I tried to boot into recovery and it says "cannot do normal boot" and gets stuck in download mode.
I then have to shut the phone off, boot into download mode, and choose cancel or else I'll get stuck in a download mode loop.
I just want to get back to stock recovery now; I'm not opposed to flashing back to stock.
Also, could I flash to safestrap? Or should I go to stock and then to safestrap? Can I use safestrap to flash to one of the custom 4.4 roms?
Thanks for your help.
amantonas said:
Hey guys --
I just was messing around with my S4 trying to get custom recovery on there (now I realize I can't), but I tried to install TWRP using TWRP manager. After it installed, I tried to boot into recovery and it says "cannot do normal boot" and gets stuck in download mode.
I then have to shut the phone off, boot into download mode, and choose cancel or else I'll get stuck in a download mode loop.
I just want to get back to stock recovery now; I'm not opposed to flashing back to stock.
Also, could I flash to safestrap? Or should I go to stock and then to safestrap? Can I use safestrap to flash to one of the custom 4.4 roms?
Thanks for your help.
Click to expand...
Click to collapse
You will need to tell us more about your phone. What version, etc.
Sent from my Hyperdriven Dev Edition Vzw SCH-I545 with KT kernel using Tapatalk 4
wtherrell said:
You will need to tell us more about your phone. What version, etc.
Sent from my Hyperdriven Dev Edition Vzw SCH-I545 with KT kernel using Tapatalk 4
Click to expand...
Click to collapse
I've got the verizon version, 4.3 on build VRUEMJ7. I've come to realize that this build is very prohibitive; is there any easy way to downgrade and then install a custom rom from there?
amantonas said:
I've got the verizon version, 4.3 on build VRUEMJ7. I've come to realize that this build is very prohibitive; is there any easy way to downgrade and then install a custom rom from there?
Click to expand...
Click to collapse
Unfortunately you can't downgrade firmware at all. There's no custom recovery for MJ7 right now, although Hashcode is working on Safestrap for it. If he can get it working, you can only run builds based on MJ7, so you won't be able to get a 4.4 ROM either.
joshm.1219 said:
Unfortunately you can't downgrade firmware at all. There's no custom recovery for MJ7 right now, although Hashcode is working on Safestrap for it. If he can get it working, you can only run builds based on MJ7, so you won't be able to get a 4.4 ROM either.
Click to expand...
Click to collapse
You're right joshm there should be a sticky somewhere addressing all these MJ7 questions. I don't mind answering and helping out but it just seems like it's everyday.
Maybe that'd help.
Verizon Galaxy S4
# MJ7 #
ALL Knoxed Up!
Mistertac said:
You're right joshm there should be a sticky somewhere addressing all these MJ7 questions. I don't mind answering and helping out but it just seems like it's everyday.
Maybe that'd help.
Verizon Galaxy S4
# MJ7 #
ALL Knoxed Up!
Click to expand...
Click to collapse
Yeah, I'm sorry to be a bother, but it seems like this usually is posted in some consolidated way and I can come across the information easily. This time, I realized the answers to my questions as I was asking them. But I still have one question:
Whatever it is that I did, when I try to boot into recovery mode, I can't. It says "can't do normal boot" and puts me in a download mode loop. Is there anyway to restore my stock recovery using odin or something like that?
amantonas said:
Yeah, I'm sorry to be a bother, but it seems like this usually is posted in some consolidated way and I can come across the information easily. This time, I realized the answers to my questions as I was asking them. But I still have one question:
Whatever it is that I did, when I try to boot into recovery mode, I can't. It says "can't do normal boot" and puts me in a download mode loop. Is there anyway to restore my stock recovery using odin or something like that?
Click to expand...
Click to collapse
Hey you're not a bother no problem..
Here is a link to a no Wipe mj7 file
http://forum.xda-developers.com/showthread.php?t=2507217
There's also a link in that thread to a full wipe, so up to you.
I'm not entirely sure what's going on with your phone but if you can get into download mode that'd probably be you're best bet.
Verizon Galaxy S4
# MJ7 #
ALL Knoxed Up!
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...