ME7 to MD5 - Verizon Samsung Galaxy S 4

If I flashed a ROM that uses ME7 and I want to ODIN back to stock, is it possible?
Or will I brick my phone? Reason I want to go back to stock is no matter what ROM I flash; every time I reboot my phone gets stuck on the samsung logo.
Answered my own question:
It does not matter...

If you are not on the ME7 OTA update then you should be fine odin'ing back to mdk
If you are on the OTA, then you are stuck with me7

Exodus885 said:
If I flashed a ROM that uses ME7 and I want to ODIN back to stock, is it possible?
Or will I brick my phone? Reason I want to go back to stock is no matter what ROM I flash; every time I reboot my phone gets stuck on the samsung logo.
Answered my own question:
It does not matter...
Click to expand...
Click to collapse
The post above really answered your question. But just in case you need to be reassured:
On our device (at the moment), as long as you didn't accept the VRUAME7 OTA, then your okay.
I actually have a couple of questions for you (if you have the time).
Can you help me out by giving me a little more information about how your getting stuck at the boot logo?
I suppose you started out clean (with VRUAMDK) and then rooted your device and installed a custom recovery.
Did you root with SuperUser (new cwm opensource) or SuperSU?
Which recovery did you install and how did you install it (which method)?
Which VRAUME7 ROM did you flash that you think started your boot issues?
Did you install the VRUAME7 radio/modem as well?
If so, which method did you use for updating your radio/modem and which files were used in your method (and where were they from)?
Click to expand...
Click to collapse
-h311sdr0id
Sent from my SCH-I605 using Tapatalk 4

h311sdr0id said:
The post above really answered your question. But just in case you need to be reassured:
On our device (at the moment), as long as you didn't accept the VRUAME7 OTA, then your okay.
I actually have a couple of questions for you (if you have the time).
-h311sdr0id
Sent from my SCH-I605 using Tapatalk 4
Click to expand...
Click to collapse
Can you help me out by giving me a little more information about how your getting stuck at the boot logo?
Anytime I installed a ROM(any ROM), I would test to see if I still had this problem and I would reboot my phone. Upon rebooting my phone, it never got passed the samsung logo. ODIN-ing back to stock helped fix this problem and now it works. However now I have an issue where facebook and instagram does not show any photos.....any ideas?
I suppose you started out clean (with VRUAMDK) and then rooted your device and installed a custom recovery.
Correct, I ODIN-ed back to MDK.
Did you root with SuperUser (new cwm opensource) or SuperSU?
SuperSU (motochopper SU script)
Which recovery did you install and how did you install it (which method)?
TWRP 2.6 using Goo manager then reverted back to 2.5.0.2
Which VRAUME7 ROM did you flash that you think started your boot issues?
Honestly, hard to say could be the nightly of CM10.2 (8/21)
Did you install the VRUAME7 radio/modem as well?
No I did not, do I need to update the radio/modem???
If so, which method did you use for updating your radio/modem and which files were used in your method (and where were they from)?
See previous answer.
Hope this helps

Related

[Q] Can't get my phone to update

I've been on stock rooted ROM (MDK) for longest time w/ CWM recovery. I decided I wanted to get back on the update track after this recent update came out and is already rooted. I defrosted all apps, unrooted the device with Voodoo OTA rootkeeper, and uninstalled SuperSU. I then flashed stock firmware with Odin as explained here: http://forum.xda-developers.com/showthread.php?t=2301259
This didn't work. I get an error during install every time. After this I noticed when going into recovery (now stock) it would have an error immediately but then went into recovery. It would not let me clear the cache (after searching this seems to be common.) So I then did factory reset multiple times (didn't help) and next flashed a stock firmware that wipes my data. This had the same results as before. Do I have a corrupt recovery of some kind? Shouldn't flashing the stock firmware fix this? Do I need to get a new phone? Help!
zregnier said:
I've been on stock rooted ROM (MDK) for longest time w/ CWM recovery. I decided I wanted to get back on the update track after this recent update came out and is already rooted. I defrosted all apps, unrooted the device with Voodoo OTA rootkeeper, and uninstalled SuperSU. I then flashed stock firmware with Odin as explained here: http://forum.xda-developers.com/showthread.php?t=2301259
This didn't work. I get an error during install every time. After this I noticed when going into recovery (now stock) it would have an error immediately but then went into recovery. It would not let me clear the cache (after searching this seems to be common.) So I then did factory reset multiple times (didn't help) and next flashed a stock firmware that wipes my data. This had the same results as before. Do I have a corrupt recovery of some kind? Shouldn't flashing the stock firmware fix this? Do I need to get a new phone? Help!
Click to expand...
Click to collapse
i dont think you can update with an unlocked recovery... if you have cwm you have an unlocked recovery and i dont think you can relock it.
also you dont need to update if you have cwm then all you need to do is flash a MI1 rom (once they come out) and youre good. there is NO reason you would need to ACTUALLY update. you can flash pretty much everything whilst still keeping unlocked recovery under actual MDK firmware but with MI1 (or ME7) rom kernel and radios.
zregnier said:
I've been on stock rooted ROM (MDK) for longest time w/ CWM recovery. I decided I wanted to get back on the update track after this recent update came out and is already rooted. I defrosted all apps, unrooted the device with Voodoo OTA rootkeeper, and uninstalled SuperSU. I then flashed stock firmware with Odin as explained here: http://forum.xda-developers.com/showthread.php?t=2301259
This didn't work. I get an error during install every time. After this I noticed when going into recovery (now stock) it would have an error immediately but then went into recovery. It would not let me clear the cache (after searching this seems to be common.) So I then did factory reset multiple times (didn't help) and next flashed a stock firmware that wipes my data. This had the same results as before. Do I have a corrupt recovery of some kind? Shouldn't flashing the stock firmware fix this? Do I need to get a new phone? Help!
Click to expand...
Click to collapse
I would try using the me7 factory image that wipes everything and then try the upgrade.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
---------- Post added at 09:21 PM ---------- Previous post was at 09:19 PM ----------
reinaldistic said:
i dont think you can update with an unlocked recovery... if you have cwm you have an unlocked recovery and i dont think you can relock it.
also you dont need to update if you have cwm then all you need to do is flash a MI1 rom (once they come out) and youre good. there is NO reason you would need to ACTUALLY update. you can flash pretty much everything whilst still keeping unlocked recovery under actual MDK firmware but with MI1 (or ME7) rom kernel and radios.
Click to expand...
Click to collapse
There is no unlocked bootloader on the s4 what allows the installation of custom recovery is the loki exploit and its reversible.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
hexitnow said:
[/COLOR]
There is no unlocked bootloader on the s4 what allows the installation of custom recovery is the loki exploit and its reversible.
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
Thus the word think but thanks for the info...
hook the guy up with the link for reversing loki then
reinaldistic said:
Thus the word think but thanks for the info...
hook the guy up with the link for reversing loki then
Click to expand...
Click to collapse
There is no link or post on it really. Its a patched recovery and boot image so when you odin back to a factory image they get replaced with the non patched versions
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
zregnier said:
I've been on stock rooted ROM (MDK) for longest time w/ CWM recovery. I decided I wanted to get back on the update track after this recent update came out and is already rooted. I defrosted all apps, unrooted the device with Voodoo OTA rootkeeper, and uninstalled SuperSU. I then flashed stock firmware with Odin as explained here: http://forum.xda-developers.com/showthread.php?t=2301259
This didn't work. I get an error during install every time. After this I noticed when going into recovery (now stock) it would have an error immediately but then went into recovery. It would not let me clear the cache (after searching this seems to be common.) So I then did factory reset multiple times (didn't help) and next flashed a stock firmware that wipes my data. This had the same results as before. Do I have a corrupt recovery of some kind? Shouldn't flashing the stock firmware fix this? Do I need to get a new phone? Help!
Click to expand...
Click to collapse
I to am having same exact problem but im on me7 and was safstrapped????????
The advice from @hexitnow worked! I downloaded ME7 image here http://forum.xda-developers.com/showthread.php?t=2357235
It worked fine then I took the latest OTA. Thanks guys!:good:
Quick Qestion
I have a quick question, and i dont want to make a who new thread about it. But since we already talkin about it on here, is it worth it to do this Verizon update?? I just did a Verizon update 2 days ago. And now to me i think it just aggitated me. My Email are different now. My delete button moved and it added more buttons. And my task manager seems a lil different. Cant seem to put my finger on it.. But its weird. What else has changed? Was it even worth doing an update?

[Q] Can't boot into any recovery, phone still works

After looking through some of the threads, I think I have a slightly unique situation.
I got my S4 through swappa, and it was already on MK2. I rooted using motochopper and installed safe strap, and that worked (when booting, I could get into the options screen mess with stuff, etc). I didn't install any ROMS since there weren't any I was interested in besides cyanogenmod
In my attempt to install cyanogen mod, I tried installing another recovery, I think TWRP. That earned me the unlocked symbol when booting, and I was stuck in a weird boot loop for a while. I started researching flashing a clean ROM onto my phone, but lo and behold, it actually fixed it's own boot loop and started up again.
That was a month or two ago, before the NC5 4.4.2 update. I decided since it had resurrected itself I would just wait for a bit and see what other tools came out.
After the 4.4.2 update came out, I ignored it for a bit. I tried installing the OTA update once and it went through it's song and dance and after it rebooted it said it couldn't complete the update so nothing was changed. I assume that is because it's rooted? I didn't really force uninstall any apps, I just disabled them through the included app manager.
So where I'm at now is I'm still on MK2, I can't install the OTA update, everytime I reboot my phone I get the unlock symbol and it says "Recovery Booting..." in blue letters at the top, but it never boots into any sort of recovery.
I have tried installing safe strap again and the safe strap app says "State: Installed" but when I reboot it says that recovery booting thing, and then just boots into the regular phone. I don't see the safe strap logo or button options at all.
Where can I go from here? Ideally I'd like to get on a custom ROM that's on the rootgalaxys4 website (it won't let me post links) but I don't know if I have the MDK bootloader, or even what my recovery situation is.
If anyone could help shed some light on this, it would be much appreciated!
Install phone info from play store. ..If you have mk2...bootloader and firmware I have no idea how you got a cm base rom loaded....As for taking an OTA. ..you have to be 100% stock...no root..nothing frozen.
sent by bajarom v2.2 kitkat
decaturbob said:
Install phone info from play store. ..If you have mk2...bootloader and firmware I have no idea how you got a cm base rom loaded....As for taking an OTA. ..you have to be 100% stock...no root..nothing frozen.
sent by bajarom v2.2 kitkat
Click to expand...
Click to collapse
I actually don't have a CM base rom loaded, sorry if I made it sound like that. I am still on 4.3 stock w/ root. I wanted a CM ROM, and it seemed like I couldn't do it through safe strap so I tried to put TWRP recovery on there and I got boot-looped (which ended up fixing itself). Now I am trying to figure out how to get a recovery on there, and what my ROM options are (if I can get to 4.4.2 rooted, I would be happy).
I got the phone info program, is there any specific info you wanted off of there?
It says bootloader version I545VRUEMK2, baseband is same
apefist said:
I actually don't have a CM base rom loaded, sorry if I made it sound like that. I am still on 4.3 stock w/ root. I wanted a CM ROM, and it seemed like I couldn't do it through safe strap so I tried to put TWRP recovery on there and I got boot-looped (which ended up fixing itself). Now I am trying to figure out how to get a recovery on there, and what my ROM options are (if I can get to 4.4.2 rooted, I would be happy).
I got the phone info program, is there any specific info you wanted off of there?
It says bootloader version I545VRUEMK2, baseband is same
Click to expand...
Click to collapse
Your ONLY option for recovery is Safestrap. You can ONLY install Touchwiz based Roms.
There are a lot of threads in the General and Development sections you should check out before you go any further. I would link them for you, but I'm on my way out. Good luck.
riker147 said:
Your ONLY option for recovery is Safestrap. You can ONLY install Touchwiz based Roms.
There are a lot of threads in the General and Development sections you should check out before you go any further. I would link them for you, but I'm on my way out. Good luck.
Click to expand...
Click to collapse
OK, well then my current problem is even though I have the safestrap app installed, and the program reports safestrap recovery as being installed, I can't access it. There is no safe strap screen while booting or button options, and even if I do the forced boot into recovery (press power+vol up+home at the same time and hold until you see the "Recovery Booting" message) it just boots to the normal phone every time.
Also worth noting is for every boot, no matter how i start it, it says "Recovery booting" at the top, but never boots into recovery. I have tried uninstalling safe strap recovery through the safe strap app and re-installing but it is the same thing.
apefist said:
After looking through some of the threads, I think I have a slightly unique situation.
I got my S4 through swappa, and it was already on MK2. I rooted using motochopper and installed safe strap, and that worked (when booting, I could get into the options screen mess with stuff, etc). I didn't install any ROMS since there weren't any I was interested in besides cyanogenmod
In my attempt to install cyanogen mod, I tried installing another recovery, I think TWRP. That earned me the unlocked symbol when booting, and I was stuck in a weird boot loop for a while. I started researching flashing a clean ROM onto my phone, but lo and behold, it actually fixed it's own boot loop and started up again.
That was a month or two ago, before the NC5 4.4.2 update. I decided since it had resurrected itself I would just wait for a bit and see what other tools came out.
After the 4.4.2 update came out, I ignored it for a bit. I tried installing the OTA update once and it went through it's song and dance and after it rebooted it said it couldn't complete the update so nothing was changed. I assume that is because it's rooted? I didn't really force uninstall any apps, I just disabled them through the included app manager.
So where I'm at now is I'm still on MK2, I can't install the OTA update, everytime I reboot my phone I get the unlock symbol and it says "Recovery Booting..." in blue letters at the top, but it never boots into any sort of recovery.
I have tried installing safe strap again and the safe strap app says "State: Installed" but when I reboot it says that recovery booting thing, and then just boots into the regular phone. I don't see the safe strap logo or button options at all.
Where can I go from here? Ideally I'd like to get on a custom ROM that's on the rootgalaxys4 website (it won't let me post links) but I don't know if I have the MDK bootloader, or even what my recovery situation is.
If anyone could help shed some light on this, it would be much appreciated!
Click to expand...
Click to collapse
This is really hard to follow.
You can't root MK2 with motochopper, only MDK. Try installing the "Phone INFO *Samsung*" app from the app store to figure out what bootloader and baseband you actually have.
You can't install an OTA update if critical system files are modified, so you'll need to re-flash to a stock ROM to do that. But if it's really MDK, you do not want to allow any OTAs to upgrade your bootloader.
k1mu said:
This is really hard to follow.
You can't root MK2 with motochopper, only MDK. Try installing the "Phone INFO *Samsung*" app from the app store to figure out what bootloader and baseband you actually have.
You can't install an OTA update if critical system files are modified, so you'll need to re-flash to a stock ROM to do that. But if it's really MDK, you do not want to allow any OTAs to upgrade your bootloader.
Click to expand...
Click to collapse
Ah, ok, I did the root a while ago, so I think I mixed up which one I had used, I believe it was SafeRoot via this thread:
http://forum.xda-developers.com/showthread.php?t=2565758
Someone earlier suggested installing the phone info app above, so I checked it and it says I545VRUEMK2 for both bootloader and baseband.
The OTA update thing was just me trying to provide as much info as possible, I don't really want to do the OTA update because it seems like it removes root, and there is no good way to get it back on NC5.
At this point I would like to install some kind of rooted ROM, but I can't get into any sort of recovery. Safe Strap says it is installed but I can't boot into it.
Would the next step be to reflash a stock recovery? Is there some way to do that?
apefist said:
Ah, ok, I did the root a while ago, so I think I mixed up which one I had used, I believe it was SafeRoot via this thread:
http://forum.xda-developers.com/showthread.php?t=2565758
Someone earlier suggested installing the phone info app above, so I checked it and it says I545VRUEMK2 for both bootloader and baseband.
The OTA update thing was just me trying to provide as much info as possible, I don't really want to do the OTA update because it seems like it removes root, and there is no good way to get it back on NC5.
At this point I would like to install some kind of rooted ROM, but I can't get into any sort of recovery. Safe Strap says it is installed but I can't boot into it.
Would the next step be to reflash a stock recovery? Is there some way to do that?
Click to expand...
Click to collapse
Installing safestrap is a 2 step process. Did u do both steps?
sent by bajarom v2.2 kitkat
decaturbob said:
Installing safestrap is a 2 step process. Did u do both steps?
sent by bajarom v2.2 kitkat
Click to expand...
Click to collapse
If the two steps are:
1: Install the safestrap app (v3.71)
2: Go into the app and install the recovery.
In the app the recovery is listed as "Installed"
apefist said:
If the two steps are:
1: Install the safestrap app (v3.71)
2: Go into the app and install the recovery.
In the app the recovery is listed as "Installed"
Click to expand...
Click to collapse
ok buddy you want to upgrade i take it?
click on the thread in my signature and download the 1st file listed called the COMPLETE PACKAGE it has everything you need.
you'll start tho by reflashing MK2 system through Odin then rerooting via Saferoot then reinstall Safestrap. Then the 4.4.2 ROM you want to use then reboot to Odin/Download mode and flash any of my NC2/NC5 1 File Upgrade packages. This is the easiest and most simplistic way to help you get to where you want to go. This will also keep your bootloaders at MK2 and your KNOX intact at 0x0! THE COMPLETE PACKAGE has all the modules, safestrap, supersu ect then if you have any questions the guys or me in the thread will help u. altho if you really do have CM running on your phone take screenshots I've tried porting to work with 4.3 and altho i can get two AOSP roms working I've never gotten close with CM it needs a custom kernel which is something we cannot use with our locked bootloader. only AOSP/GE Roms that will work for 4.4.2 or 4.3 are ones that are compatible with the stock 4.3 or 4.4.2 kernels theres a thread in the development section for that subject as well.

[Q] Installing TWRP on jfltevzw 4.4.2 (NC5)

I was one of the idiots that accidentally upgraded to the newest firmware when it first came out. My device is totally rooted, but I've been reading that I'm required to use things such as SafeStrap or Loki to install custom roms. I'm not sure if this is still the case as its been months since this was discovered. I've been trying to search the forums extensively for a fix, but I've been unable to find one. One thing I came across: here seems to be a very simple way to install TWRP on the Galaxy S4, however, I don't wan to run the risk of bricking my phone and being SOL because I have ****ty firmware and no way to custom recover my phone.
Point blank, would I be able to install TWRP manager via GooManager given that I've updated to NC5? Or even if not, what are my options for custom recovery/roms? End game, I want to walk away with 5.0.1 GPE or Cyanogenmod 12. Hopefully.
I'd really appreciate any and all help. Attached is a screenshot of my phone information.
zQueal said:
I was one of the idiots that accidentally upgraded to the newest firmware when it first came out. My device is totally rooted, but I've been reading that I'm required to use things such as SafeStrap or Loki to install custom roms. I'm not sure if this is still the case as its been months since this was discovered. I've been trying to search the forums extensively for a fix, but I've been unable to find one. One thing I came across: here seems to be a very simple way to install TWRP on the Galaxy S4, however, I don't wan to run the risk of bricking my phone and being SOL because I have ****ty firmware and no way to custom recover my phone.
Point blank, would I be able to install TWRP manager via GooManager given that I've updated to NC5? Or even if not, what are my options for custom recovery/roms? End game, I want to walk away with 5.0.1 GPE or Cyanogenmod 12. Hopefully.
I'd really appreciate any and all help. Attached is a screenshot of my phone information.
Click to expand...
Click to collapse
Once you updated to anything past MDK there's no going back . Safestrap is the only option to install Touchwiz ROMS.
scrillakev said:
Once you updated to anything past MDK there's no going back . Safestrap is the only option to install Touchwiz ROMS.
Click to expand...
Click to collapse
Damn! That's what I figured. I followed [this guide](https://www.youtube.com/watch?v=BLHZfPwLkPM) and installed the SafeStrap APK, but stopped at the "install recovery" step. I've been reading that this can soft brick your phone. Do you have any input? Is it safe to do? If it does brick my phone will I be able to factory reset with Odin?
Sorry for the barrage of questions, I'm a bit of a noob.
-----------------------------------------------------------------------
EDIT:
Well, I decided to go ahead with it. It worked fine. I rebooted to SafeStrap and went right to do a backup. It failed. I tried to reboot into my stock rom, and it was 0MB. I really might blow up Verizon HQ.
zQueal said:
Damn! That's what I figured. I followed [this guide](https://www.youtube.com/watch?v=BLHZfPwLkPM) and installed the SafeStrap APK, but stopped at the "install recovery" step. I've been reading that this can soft brick your phone. Do you have any input? Is it safe to do? If it does brick my phone will I be able to factory reset with Odin?
Sorry for the barrage of questions, I'm a bit of a noob.
-----------------------------------------------------------------------
EDIT:
Well, I decided to go ahead with it. It worked fine. I rebooted to SafeStrap and went right to do a backup. It failed. I tried to reboot into my stock rom, and it was 0MB. I really might blow up Verizon HQ.
Click to expand...
Click to collapse
I never used SafeStrap so I doubt I will be much help. But once you rebooted your stock ROM is no longer there? Might have to just flash a stock image via ODIN and try again. Verizon isn't going to help you either with modding your phone, XDA is the place to be.
Has there been anything new since this thread was posted or is it impossible still?
mcbeat257 said:
Has there been anything new since this thread was posted or is it impossible still?
Click to expand...
Click to collapse
Sorry buddy you're SOL
Sent from my SCH-I545 using XDA Free mobile app
If you are rooted use a terminal editor app and type:
getprop ro.bootloader
If it says anything other than I545VRUAMDK your only choice is SafeStrap.
That means if you bought an S4 and it came with MK1, NC5, NK1, or anything other than MDK you cannot flash a custom recovery. The same applies if you took an OTA from VZW. This has been stated 1000's of times here.
Hint:
Look on the box that your S4 came in and read the last three characters where it says what build the phone has.
mcbeat257 said:
Has there been anything new since this thread was posted or is it impossible still?
Click to expand...
Click to collapse
Keep checking up on SS they are working on the ability to also use custom kernels on top which would make it essentially as efficient as a custom recovery, with some storage loss.
safestrap version
Well, I decided to go ahead with it. It worked fine. I rebooted to SafeStrap and went right to do a backup. It failed. I tried to reboot into my stock rom, and it was 0MB. I really might blow up Verizon HQ.[/QUOTE]
***Make sure you are using the correct version of safestrap for your current baseband
another good app from the google play store to download is samsung info
I have used safestrap in the past as I was in the same scenario as you. I currently now have a MDK phone
Illogi.xbone said:
Keep checking up on SS they are working on the ability to also use custom kernels on top which would make it essentially as efficient as a custom recovery, with some storage loss.
Click to expand...
Click to collapse
How come they haven't been able to unlock the bootloader when only the build version is changing......
There should have been an exploit awhile ago....and why haven't they made an odin option for MDK yet?
mcbeat257 said:
How come they haven't been able to unlock the bootloader when only the build version is changing......
There should have been an exploit awhile ago....and why haven't they made an odin option for MDK yet?
Click to expand...
Click to collapse
The exploit was weeded out after MDK
Sent from my SCH-I545 using XDA Free mobile app
The bootloader was never "unlocked" on MDK, there was just an exploit available that allowed the installation of a custom recovery. That exploit was closed in the first update from MDK and a new one has not been discovered. The bootloader itself has some pretty strong encryption so it may never be unlocked.

[FIXED] Help: HDX 7 broken stock recovery

EDIT: with Davey126's stock recovery file, my problem is solved. Thanks!!
Hi xda!
Long time follower here. Wanna thank all the people here for the great work and help to the android community.
On to my issue, I can't get into stock recovery now. If I flash safestrap, I can boot to recovery, but not when I uninstall safestrap.
This is what happened: I was on Thor 13.3.2.5 rooted. I downgraded to 13.3.1.0 then 13.3.2.3.2 rooted (backed up), then left OTA on. When I came back to it, it was in a boot loop. I powered off and back on holding power button, now it boots to 13.3.2.5! And when I check version, it says 13.4.1.1 available. But the update always fails because the HDX never goes into stock recovery.
I then reinstalled safestrap and restored. Now I am running 13.3.2.3.2 but can't boot to stock recovery.
Question: 1) where and how do I get the recovery image? 2) can I use the recovery image for Apollo?
Thanks very much in advance.
ssrtist
ssrtist said:
Hi xda!
Long time follower here. Wanna thank all the people here for the great work and help to the android community.
On to my issue, I can't get into stock recovery now. If I flash safestrap, I can boot to recovery, but not when I uninstall safestrap.
This is what happened: I was on Thor 13.3.2.5 rooted. I downgraded to 13.3.1.0 then 13.3.2.3.2 rooted (backed up), then left OTA on. When I came back to it, it was in a boot loop. I powered off and back on holding power button, now it boots to 13.3.2.5! And when I check version, it says 13.4.1.1 available. But the update always fails because the HDX never goes into stock recovery.
I then reinstalled safestrap and restored. Now I am running 13.3.2.3.2 but can't boot to stock recovery.
Question: 1) where and how do I get the recovery image? 2) can I use the recovery image for Apollo?
Thanks very much in advance.
ssrtist
Click to expand...
Click to collapse
Don't use an Apollo recovery. While I have no direct evidence it won't work the risk seems unacceptable given you only have partial control of your device and (probably) a locked bootloader.
Stock 13.3.2.6 recovery here. I have been told there were no changes from 3.2.5. You can use flashify to install it.
Obviously there is risk associated with this approach. Might want to wait a day or two for additional responses to see what others think.
Thanks! So I don't actually need to go to 13.3.2.3.2? Also, did I downgrade the recovery when I downgraded the stock rom?
Sent from my Nexus 7 using XDA Free mobile app
ssrtist said:
Thanks! So I don't actually need to go to 13.3.2.3.2? Also, did I downgrade the recovery when I downgraded the stock rom?
Click to expand...
Click to collapse
A previous post suggested you are already at 3.2.3. Bit confused regarding your question. Not sure what happened to your recovery during the previous rollbacks/upgrades. I have seen something similar happen to folks who have installed twrp then upgrade past 3.2.3.
What's your objective? Are you looking to run CM11/12 or stick with rooted stock? If the former you'll need to rollback again (if not already on 3.2.3), block OTA and then install native twrp. Once you have a working recovery you should uninstall safestrap before beginning the rollback process. Safestrap isn't part of the equation going forward.
Davey126 said:
Not sure what happened to your recovery during the previous rollbacks/upgrades. I have seen something similar happen to folks who have installed twrp then upgrade past 3.2.3.
Click to expand...
Click to collapse
I think that's what I did ?
My goal is to try both cm12 and rooted 4.5.2. (Separately). Is flashing 3.2.6 recovery the way to go?
Thanks?
ssrtist said:
I think that's what I did
My goal is to try both cm12 and rooted 4.5.2. (Separately). Is flashing 3.2.6 recovery the way to go?
Thanks?
Click to expand...
Click to collapse
Depends where you are now. If on rooted 13.3.2.3 then you should be able to flash twrp directly after getting rid of SafeStrap. Note there is now a recommendation to unlock your bootloader before installing twrp but that seems to be optional (bootloader unlocking is not for the faint of heart). You can then install CM11/12.
If currently above 3.2.3 then you need to get a working recover before taking next steps. Flashing 3.2.6 recovery seems to be a reasonable choice but as previously noted there is risk associated with this approach. Assuming it works you then need to start the rollback process all over again.
4.5.2 is an entirely different beast. Still need to get a working recovery before upgrading unless you flash it directly via adb which is risky.
Without an unlocked bootloader anything you do can lead to an unrecoverable brick. Make sure you think ahead and read up on others experiences before proceeding.
Thanks Davey!! Your answers are very informative! I will read a bit more before i tackling the bootloader...
Sent from my Nexus 7 using XDA Free mobile app

[Q] Help, I think I bricked my phone

I rooted my s4 and installed twrp a long time ago used the phone for a little while then stashed it away. It had the following rom installed I545VRVFNC5 stock root oder I believe it was 4.4.2. The other night I installed flash fire and attempted to flash I545_OC1_Stock_rooted_rom mdk. It flashed ok but now I'm getting the verizon warning message and I can't bypass. I can no longer boot into twrp. I think the bootloader is still unlocked, padlock is unlocked upon boot. How do I get myself out of this message?
looneyk said:
I rooted my s4 and installed twrp a long time ago used the phone for a little while then stashed it away. It had the following rom installed I545VRVFNC5 stock root oder I believe it was 4.4.2. The other night I installed flash fire and attempted to flash I545_OC1_Stock_rooted_rom mdk. It flashed ok but now I'm getting the verizon warning message and I can't bypass. I can no longer boot into twrp. I think the bootloader is still unlocked, padlock is unlocked upon boot. How do I get myself out of this message?
Click to expand...
Click to collapse
Try to Odin back to MDK, if you had TWRP... If that doesn't work, nc5. You can't do custom ROM's like Cynanogenmod, but you have a limited amount of freedom with safestrap.
looneyk said:
I rooted my s4 and installed twrp a long time ago used the phone for a little while then stashed it away. It had the following rom installed I545VRVFNC5 stock root oder I believe it was 4.4.2. The other night I installed flash fire and attempted to flash I545_OC1_Stock_rooted_rom mdk. It flashed ok but now I'm getting the verizon warning message and I can't bypass. I can no longer boot into twrp. I think the bootloader is still unlocked, padlock is unlocked upon boot. How do I get myself out of this message?
Click to expand...
Click to collapse
The open padlock means the firmware you have installed is custom and not stock, doesn't mean your boot loader is unlocked. I would simply boot into download mode and re-image your device back to MDK, if that's where you were. What's your current boot loader version?
looneyk said:
I rooted my s4 and installed twrp a long time ago used the phone for a little while then stashed it away. It had the following rom installed I545VRVFNC5 stock root oder I believe it was 4.4.2. The other night I installed flash fire and attempted to flash I545_OC1_Stock_rooted_rom mdk. It flashed ok but now I'm getting the verizon warning message and I can't bypass. I can no longer boot into twrp. I think the bootloader is still unlocked, padlock is unlocked upon boot. How do I get myself out of this message?
Click to expand...
Click to collapse
Sent from my SCH-I545
SnyderGuy said:
The open padlock means the firmware you have installed is custom and not stock, doesn't mean your boot loader is unlocked. I would simply boot into download mode and re-image your device back to MDK, if that's where you were. What's your current boot loader version?
Sent from my SCH-I545
Click to expand...
Click to collapse
I am using an MDK S4.
I can bit to room, but cannot reboot to recovery.
Corrupted recovery after update via TWRP app.
How exactly, do I re-image my device back to MDK?
Do I use this stock MDK ROM? http://forum.xda-developers.com/gal...ment/rom-i545oc1-5-0-1-100-stock-mdk-t3097902
Do I put it in the BL or AP box in ODIN?
No, that is a ROM. You need the stock official software.
http://forum.xda-developers.com/showthread.php?t=2289325
SHOULD be that one...
Put that in AP
XxD34THxX said:
No, that is a ROM. You need the stock official software.
http://forum.xda-developers.com/showthread.php?t=2289325
SHOULD be that one...
Put that in AP
Click to expand...
Click to collapse
I just read it all. Looks like fun!
I sure would like to know what I did wrong. I only used the TWRP app to update TWRP.
pizza_pablo said:
I just read it all. Looks like fun!
I sure would like to know what I did wrong. I only used the TWRP app to update TWRP.
Click to expand...
Click to collapse
That I cannot answer since I do not have MDK. My assumption is a corrupted download of TWRP or a partial install that was interrupted for some reason.
XxD34THxX said:
That I cannot answer since I do not have MDK. My assumption is a corrupted download of TWRP or a partial install that was interrupted for some reason.
Click to expand...
Click to collapse
That may have been the case, since my connection was weak.
I'm just about to do the deed and I checked phone info and the bootloader is now I545VRUFNK4, vice MDK.
Here I go....
Well....I tried these to .tar files with no luck:
http://www.rwilco12.com/downloads.p...Galaxy S4 (Verizon) (SCH-I545)/Stock ROMs/TAR
https://www.androidfilehost.com/?fid=22979706399752783
I did get the "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
Now, I no longer have the option to cancel Download Mode and bot ROM.
I didn't want to do anything in Kies, for fear of taking an OTA.
Do I have any options?
Even just taking an OTA and selling a former MDK treasure?
This seems to be happening a lot. A LOT. Before you try kies, go into device manager and uninstall the Samsung USB drivers. Then download the DRIVERS ONLY from Sammobile/Samsung. THEN use Odin with a full wipe and repartition of MDK. If you get the same message again, then you have lost the MDK bootloader, and will have to repeat the process with an nc5 tar, which will loose custom ROMs, but you will have root and safestrap.
XxD34THxX said:
This seems to be happening a lot. A LOT. Before you try kies, go into device manager and uninstall the Samsung USB drivers. Then download the DRIVERS ONLY from Sammobile/Samsung. THEN use Odin with a full wipe and repartition of MDK. If you get the same message again, then you have lost the MDK bootloader, and will have to repeat the process with an nc5 tar, which will loose custom ROMs, but you will have root and safestrap.
Click to expand...
Click to collapse
OK. So I am going to uninstall Kies, just for safety sake. Uninstall the Samsung PC drivers. Reinstall the PC drivers.
Use ODIN to flash this http://www.rwilco12.com/downloads.php?dir=Files/Devices/Samsung%20Galaxy%20S4%20%28Verizon%29%20%28SCH-I545%29/Stock%20ROMs/TAR in the AP box. Sacrifice a chicken and dance with snakes.
What do you think may have caused the bootloader to change?
At this point I guess any use of the phone will be a positive and somehow retaining MDK will be a miracle.
Thanks, for your assistance, as I am at a loss, at this point!
that is a .gz, so make sure to unip it/ delete that extension so Odin can use it.
My assumption is you may have accidently flashed the entire nk4, not just one with the MDK stuff still in.
XxD34THxX said:
that is a .gz, so make sure to unip it/ delete that extension so Odin can use it.
My assumption is you may have accidently flashed the entire nk4, not just one with the MDK stuff still in.
Click to expand...
Click to collapse
I used the link file, from my last post.
After I unzip it, delete the " .gz "
Got it. Thanks, again!
XxD34THxX said:
that is a .gz, so make sure to unip it/ delete that extension so Odin can use it.
My assumption is you may have accidently flashed the entire nk4, not just one with the MDK stuff still in.
Click to expand...
Click to collapse
So I just looked at the computer file and there was no .gz extention on the file I flashed thru ODIN.
It was not zipped, either.
On the xda page that you link, there was another choice on thier link. It was titled "one click". It is an .exe, titled "SCH-I545_MDK_562219_Stock_Restore.exe" .
What could ODIN do with this?
The other file I found, that I tried, but no change, was titled "VRUAMDK_NoWipe.tar.md5" .
Do you have any other suggestions,please?
Use the Full wipe in this thread:
http://forum.xda-developers.com/showthread.php?t=2301259
If that does not fix anything you have either
A)Hard Brick(unlikely since the device is semi-working)
B) lost MDK.
XxD34THxX said:
Use the Full wipe in this thread:
http://forum.xda-developers.com/showthread.php?t=2301259
If that does not fix anything you have either
A)Hard Brick(unlikely since the device is semi-working)
B) lost MDK.
Click to expand...
Click to collapse
I used this one, the other night, with no change, but this time I will delete Kies and phone drivers, then reinstall phone drivers, before ODIN.
You're a champ!
XxD34THxX said:
Use the Full wipe in this thread:
http://forum.xda-developers.com/showthread.php?t=2301259
If that does not fix anything you have either
A)Hard Brick(unlikely since the device is semi-working)
B) lost MDK.
Click to expand...
Click to collapse
Do I remove the .md5 extension as well as the .gz and just leave the .tar on the end?
ETA: Well, I tried removing both extensions and ODIN would not take it. Received error pop up.
I tried, with no success, ODIN flashing the full wipe and no wipe tars, with no success.
Giving up for the night.
XxD34THxX said:
This seems to be happening a lot. A LOT. Before you try kies, go into device manager and uninstall the Samsung USB drivers. Then download the DRIVERS ONLY from Sammobile/Samsung. THEN use Odin with a full wipe and repartition of MDK. If you get the same message again, then you have lost the MDK bootloader, and will have to repeat the process with an nc5 tar, which will loose custom ROMs, but you will have root and safestrap.
Click to expand...
Click to collapse
I woke up in the middle of the night and something popped into my head and I couldn't get back to sleep, so here we go....
The phone was on Echoe v49 which is Lollipop and I didn't like it. So I decided to go to the last Echoe version that was KitKat, v34.
I flashed this https://www.androidfilehost.com/?fid=95747613655044521 Which apparently is T-Mobile based, and the v20 international patch.
What popped into my head was that maybe my phone was thinking it was a T-Mobile S4, because I picked the wrong kernel. At the time everything seemed to work, except sending SMS. I could make phone calls and receive SMS.
This is was got me out of bed. I went to my notes for the Aroma install, to see what kernel I chose. I recalled picking the stock kernel, which may have been T-Mobile, but my notes say that I picked KTOONES kerenel in Aroma and in the Patcher, picked ADD VZW FILES AND BUILD PROP and NO KERNEL.
I was thinking that I had put a VZW version of TWRP onto a "T-Mobile" S4, getting me stuck to bootup in Download mode only, but still able to cancel Download and boot to system. Then I ODINed the VZW MDK stock firmware and am now with either Download mode or the yellow PC connected to phone screen, with the "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I woke up thinking that maybe I had a T=mobile kernel and when I lost TWRP and only had stock recovery, downloaded the VZW version of TWRP on top of T=Mobile install. But the note makes it look like I would have been OK as far as the phone thinking it was a VZW S4.
Sorry if rambling, just trying to pass as many details and thoughts as possible.
Do I have any options, now?
I downloaded the stuff to do Heimdall One Click and was thinking about trying that route, with a file named "SCH-I545_MDK_562219_Stock_Restore.exe"
I have a 32GB MDK VZW SCH-i545 S4 that is running fine on ECHOE v29. Can I copy anything from that phone and flash in ODIN to recover the 16GB (was MDK) VZW SCH-i545 that is stuck on Download mode only?
Is there any way to flash a NANDROID via ODIN or some other program from a PC thru ODIN?
hmmm.. The Ktoonez kernal works on any s4. But if you flashed T mobile Files, which I don't think was the case since you flashed the Verizon stuff... I have never used Heimdall, so I can't comment on that. I don't know what to say. There might be a way to make a debrick image... Someone more experienced will have to help, sorry.
XxD34THxX said:
hmmm.. The Ktoonez kernal works on any s4. But if you flashed T mobile Files, which I don't think was the case since you flashed the Verizon stuff... I have never used Heimdall, so I can't comment on that. I don't know what to say. There might be a way to make a debrick image... Someone more experienced will have to help, sorry.
Click to expand...
Click to collapse
No need to apologize! You have helped all you can. I appreciate it greatly!
I just want to ensure that I exhaust ALL possibilities of recovering the MDK, before I throw in the Kies upgrade towel.
I wonder if I'll get in hot water for starting a new thread.....

Categories

Resources