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?
Related
Just got to know that Pantech has released the much awaited Jelly Bean 4.1 for the Flex through OTA AT&T software update.
Like many others, I'm using the flex outside US, therefore, cannot update my flex.
Would request someone to upload the OTA JB zip file.
Can't wait to see Jelly Bean on the Flex.
PS: Check out the Pantech website for this great news
This is good news. I wish I wasn't rooted with CWMR so I could get this. Tried flashing stock recovery.img and boot.img files but get NOT SUPPORT.
Anyone know a way to get this phone back to complete stock so we can get the Jell Bean goodness?
I managed to unroot and restore stock recovery.
Got prompted for the update, it downloaded and installed fine!
This little Flex seems quite a bit better with Jelly Bean. Wish it had been 4.2 but 4.1 is fine.
Tersanyus said:
I managed to unroot and restore stock recovery.
Got prompted for the update, it downloaded and installed fine!
This little Flex seems quite a bit better with Jelly Bean. Wish it had been 4.2 but 4.1 is fine.
Click to expand...
Click to collapse
Can you upload the update file?
How did you unroot?
Sent from my PantechP8010 using xda app-developers app
Not rooted anymore so probably can't get the update file. It was like 264MB or something.
Not planning to root this phone again.
Interesting that the Pantech diag menu shows still rooted and tampered, it's definitely not rooted.
It should be 100% stock.
If you know of a way to get the file off the phone I can look for it.
---------- Post added at 01:09 PM ---------- Previous post was at 12:52 PM ----------
I knew from experience I had to go to stock recovery and unroot to update.
I flashed a stock rooted nandroid backup I had made after rooting initially.
To unroot I think I went into the SuperUser app and choose option to unroot.
Stock recovery file is posted in a thread here somewhere, had recovery.img and boot.img.
Tried flashing those in fastboot but only got NOT SUPPORT mesage.
I took a flashable zip file that had CWM recovery.img file in it and replaced it with the stock recovery.img and flashed it in CWM.
Once stock recovery was on the phone when I tried to use it I only got a little android symbol lying on its back with a red exclamation point.
Phone booted fine and worked ok
Couldn't get it to see the AT&T update until this morning.
Things I have noticed in this new Jelly Bean build for our little Flex:
Of the stock AT&T apps only 3 I could disable (ugh), why no Disable button
good news
Tersanyus said:
Not rooted anymore so probably can't get the update file. It was like 264MB or something.
Not planning to root this phone again.
Interesting that the Pantech diag menu shows still rooted and tampered, it's definitely not rooted.
It should be 100% stock.
If you know of a way to get the file off the phone I can look for it.
Click to expand...
Click to collapse
Basically you will find the update in the /cache folder.
I'm not sure if you you can access this folder without being rooted. You can give it a try using the ES File Explorer.
Let me know if you get the update.
ES File Manager did see the cache folder and all the other system folders. It was empty. I'm sorry, I factory reset the phone last night from stock recovery since it was not updating built in apps properly. Never seen stock recovery on this phone before. It has an option for root. I selected it. Downloaded a few root checker apps, not rooted.
I'm sorry if I hadn't reset it last night I might have found the file. I'm sure it will turn up somewhere. This little Flex doesn't have much in the way of development but someone here at XDA will get it sooner or later.
Tersanyus said:
ES File Manager did see the cache folder and all the other system folders. It was empty. I'm sorry, I factory reset the phone last night from stock recovery since it was not updating built in apps properly. Never seen stock recovery on this phone before. It has an option for root. I selected it. Downloaded a few root checker apps, not rooted.
I'm sorry if I hadn't reset it last night I might have found the file. I'm sure it will turn up somewhere. This little Flex doesn't have much in the way of development but someone here at XDA will get it sooner or later.
Click to expand...
Click to collapse
Oh that's bad!
Actually, there's another way. If you can share your system nandroid backup, maybe that can help.
Try Rooting
Tersanyus said:
ES File Manager did see the cache folder and all the other system folders. It was empty. I'm sorry, I factory reset the phone last night from stock recovery since it was not updating built in apps properly. Never seen stock recovery on this phone before. It has an option for root. I selected it. Downloaded a few root checker apps, not rooted.
I'm sorry if I hadn't reset it last night I might have found the file. I'm sure it will turn up somewhere. This little Flex doesn't have much in the way of development but someone here at XDA will get it sooner or later.
Click to expand...
Click to collapse
Why dont you try to root with this method http://forum.xda-developers.com/showthread.php?t=1886460 ,its the same you used to root 4.0.4 I guess, should work, pull out the update and then unroot the phone as you dont want it rooted.
It happened to me, even rooted I wanst able to see /data content with ES File Blablabla, then tried with root explorer and worked fine.
I'm not going to root this Flex. It's not a primary phone for me (never was). It is used as a spare now and can be used by novice users in my family and friends. Don't want them to have a rooted phone. I'd been wanting to get this phone back to complete stock for a while but hasn't really put much effort into it.
When I saw that Pantech released JB for Flex a few days ago that was my motivation to get it back to stock. Frankly I was surprised I was able to get it back to stock and not brick the phone!
I'm uploading the stock rooted rom I have. Luckily I saved that on my computer. It's uploading to Dropbox now so it will take a while.
Thanks for your help
Tersanyus said:
I'm not going to root this Flex. It's not a primary phone for me (never was). It is used as a spare now and can be used by novice users in my family and friends. Don't want them to have a rooted phone. I'd been wanting to get this phone back to complete stock for a while but hasn't really put much effort into it.
When I saw that Pantech released JB for Flex a few days ago that was my motivation to get it back to stock. Frankly I was surprised I was able to get it back to stock and not brick the phone!
I'm uploading the stock rooted rom I have. Luckily I saved that on my computer. It's uploading to Dropbox now so it will take a while.
Click to expand...
Click to collapse
Well, thanks for the file, I'm outside US and even on stock, update notification doesn't prompt.
I got mine back to Stock, but when I hit check for upgrade it says..."Previous session is running. Please Try Later"
I have wiped it several times. any ideas?
Wait...
kneemeister said:
I got mine back to Stock, but when I hit check for upgrade it says..."Previous session is running. Please Try Later"
I have wiped it several times. any ideas?
Click to expand...
Click to collapse
I can see ATT's software updater sucks, we just can wait for our friend's upload.
Here it is: Link removed, Dropbox suspended it.
That should be a stock but rooted rom. Nothing else done to it at all. At least. I had that on the phone for a while as a backup when I was playing with roms for the flex.
Probably only going to leave this link up for a day. I'd make your own nandroid backup first. You'll probably get an md5 error in CWMR but there are instructions for fixing that around. I think it was ADB commands that had to fix it. I know the instructions for clearing the md5 error are in one of the flex rom threads, not that there were many of those. The standard disclaimer applies, if this nandroid backup bricks your phone, I can't help you.
I got the same previous session message too. Then it said no update after wiping. I think the best thing is just wipe and don't check for updates. Leave phone on, wifi on and wait for the phone to check on it's own. I got the prompt in a few hours.
Hope this helps you.
So, need to flash stock recovery after restoring nandroid correct?
Sent from my PantechP8010 using xda app-developers app
Likely if you do not flash stock recovery in CWMR the update will fail. I tried to take the update before flashing stock recovery, it failed each time. I had already unrooted though. Pretty much what I have learned from flashing various phones over the years is that if you are not stock completely any OTA updates from the carrier will fail or soft brick your device.
I think the Flex was one where I had just that issue. There was some AT&T update a few months back, I said to apply it and I got stuck in recovery. Every time I rebooted the phone it just booted to recovery. Found out if I went into the diag screen on the Flex and choose reboot from there I could boot normally. Eventually I figured out I had the wrong boot.img on the phone. Once that was fixed the phone booted fine. But the update never worked.
You can try to take the update with CWMR but I doubt it will work and could brick or soft brick. I've learned to never take an OTA update from the carrier if you are not completely stock.
Still waiting
Tersanyus said:
Likely if you do not flash stock recovery in CWMR the update will fail. I tried to take the update before flashing stock recovery, it failed each time. I had already unrooted though. Pretty much what I have learned from flashing various phones over the years is that if you are not stock completely any OTA updates from the carrier will fail or soft brick your device.
I think the Flex was one where I had just that issue. There was some AT&T update a few months back, I said to apply it and I got stuck in recovery. Every time I rebooted the phone it just booted to recovery. Found out if I went into the diag screen on the Flex and choose reboot from there I could boot normally. Eventually I figured out I had the wrong boot.img on the phone. Once that was fixed the phone booted fine. But the update never worked.
You can try to take the update with CWMR but I doubt it will work and could brick or soft brick. I've learned to never take an OTA update from the carrier if you are not completely stock.
Click to expand...
Click to collapse
Im on stock and I cant update, no root, stock recovery, Ive been waiting for the update and nothing.
I dont know if is because Im outside US
I got mine back to stock and unrooted, but the upgrade still fails at about 25% and reboots. If I clear cache and wipe, it will download again, then fail again. Even after flashing back to stock, recovery still says rooted and so does the software upload screen. But I have confirmed that I am no longer rooted. I am about to give up.
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
Hi All,
I picked up an MI1 GS4 a month ago and after a few nights of scrolling through the forums I was able to get HD 10.2 loaded onto my phone via Safestrap. During the root process, I got a little bit a head of myself and flashed a custom recovery. After some research (and a presumed brick scare) I found that there is no way to get CWM recovery on the phone. While it's a major disappointment, it is what it is. So I have two questions:
So right now, my phone doesnt have a recovery and if I try to boot into it, it will go into Odin mode and give me some sort of an error. I assume I need to flash a new recovery through Odin, but am wondering if someone could point me in the direction of the correct file.
Is MJ7 the latest OTA from VZW? Should I wipe my device completely, go back to stock, and take the latest OTA? From what I am gathering, safestap is now working on MJ7, but I want to be sure that is what I will get to if I take the OTA. If I do want to take the OTA, how would I go about doing this and is the problem listed above an issue?
Thanks!
madtomatoes said:
Hi All,
I picked up an MI1 GS4 a month ago and after a few nights of scrolling through the forums I was able to get HD 10.2 loaded onto my phone via Safestrap. During the root process, I got a little bit a head of myself and flashed a custom recovery. After some research (and a presumed brick scare) I found that there is no way to get CWM recovery on the phone. While it's a major disappointment, it is what it is. So I have two questions:
So right now, my phone doesnt have a recovery and if I try to boot into it, it will go into Odin mode and give me some sort of an error. I assume I need to flash a new recovery through Odin, but am wondering if someone could point me in the direction of the correct file.
Is MJ7 the latest OTA from VZW? Should I wipe my device completely, go back to stock, and take the latest OTA? From what I am gathering, safestap is now working on MJ7, but I want to be sure that is what I will get to if I take the OTA. If I do want to take the OTA, how would I go about doing this and is the problem listed above an issue?
Thanks!
Click to expand...
Click to collapse
safestrap is a recovery of sorts, so what you are saying, you rooted, installed safestrap, installed HD10.2 than installed a recovery on top of that like CWM? So you soft bricked your phone?
Your only recourse is odin the full wipe stock image back and start over.
I suggest a thorough reading of the forum threads here first so you know better what to do.
I have a guide in the general forum here that lists steps to go from ME7 to MJ7 and root, install safestrap 3.65 and HD11....I'm not sure how it would play with your MI1 base phone so proceed at your own risk
decaturbob said:
safestrap is a recovery of sorts, so what you are saying, you rooted, installed safestrap, installed HD10.2 than installed a recovery on top of that like CWM? So you soft bricked your phone?
Click to expand...
Click to collapse
The other way around. I first rooted and attempted to install CWM. After that failed, I read further and discoved that only MDK roms are truly unlocked. From that point, I installed safestrap and HD. My phone is functional right now, I just have no way of getting into the stock recovery.
It's my understanding that I will need to use Odin to flash the stock MI1 image. I just want to confirm what happens from there. After flashing the stock image, I will be stock MI1, unrooted, with the opportunity to OTA to MJ7 (?). From that point, I'll take the OTA, re-root, reinstall safestrap, and finally HD11/12. Is all of this correct?
Thanks
madtomatoes said:
The other way around. I first rooted and attempted to install CWM. After that failed, I read further and discoved that only MDK roms are truly unlocked. From that point, I installed safestrap and HD. My phone is functional right now, I just have no way of getting into the stock recovery.
It's my understanding that I will need to use Odin to flash the stock MI1 image. I just want to confirm what happens from there. After flashing the stock image, I will be stock MI1, unrooted, with the opportunity to OTA to MJ7 (?). From that point, I'll take the OTA, re-root, reinstall safestrap, and finally HD11/12. Is all of this correct?
Thanks
Click to expand...
Click to collapse
that sounds about right. When you do HD12, be sure you have the safestrap version....
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.
I've had this pending on my phone for quite awhile, I haven't done it because I'm rooted. I decided one day to try it, my phone rebooted to TWRP and nothing happened. Which is exactly what I thought would happen. So I pulled the stock recovery from the stock rom and successfully flashed it. Tried the update again and I am getting a bit error from the stock recovery. The phone goes into "wtf just happened" mode and I have to do a battery pull and reboot. Which works fine. I don't really want to backup everything and re-root and reinstall everything, so does anyone know what my bootloader isn't seeing, but needs to see in order to push the update through?
Also, my phone isn't reading my brand new 64gb SanDisk evo suddenly. Was reading it fine last week... And ideas?
I'm on stock rooted ZV8 with sprint naval kernel.
Sent from my Sprint LG G3 sexiness via tapatalk
partitions may be zv4/zv6 on your phone? that may be why you cant do the OTA. what about dirty flashing stock rooted ZVA(not recommended, but works great for me)? there is a navel kernel for it also. Make a backup and if you dont like it, flash back? what connectivity fix does the ZVA update claim? I thought the only (LISTED) update was they added factory reset protection?
He can't take the OTA cause he has TWRP installed. OTA will only install with stock recovery. Probably will need to use the flashtool to go to complete stock if you want to receive the OTA.
Sent from my SM-G920P
Arjohns said:
He can't take the OTA cause he has TWRP installed. OTA will only install with stock recovery. Probably will need to use the flashtool to go to complete stock if you want to receive the OTA.
Sent from my SM-G920P
Click to expand...
Click to collapse
He said he put stock recovery back on, but yes he would probably need to flash completely stock to do the ota
Sent from my LGLS990 using XDA Free mobile app
Guess I should have read that better, sorry. As stated, try the rooted ZVA. OTA can be stopped due to edited build prop, debloating, etc. So complete stock through flashtool or flashing a rooted ZVA would be the only way to get to the new version.
Sent from my SM-G920P