Related
I started with a “refurb” phone from our insurance company, glass got broke on my first S4 that accidentally got updated to ME7. Came with MDK happily.
First step for me was to put the phone in Airplane Mode after I went through setup. This step was to ensure that the ME7 OTA didn’t come in without me noticing. After in Airplane mode, I set up my Wi-Fi to get Titanium Backup on the phone. At this point, the OTA attempted to load anyway, I stopped it from downloading by turning off Wi-Fi, this caused the download to fail and not flash ME7. I have Premium TBU so I was able to freeze both SDM and SEAndroid. This stopped the update from coming in at all. There is another free App that does the same thing, if anyone wants to enlighten me I’ll just add the name here.
Start rooting by visiting this stickied post in the Android Development Section. This walks you through root and has all the files and instructions needed to do so. BIG thanks to open1your1eyes0 for such a thorough walkthrough. http://forum.xda-developers.com/showthread.php?t=2381382. Just a FYI when rooting MDK and then flashing the MD2 kernel, it doesn’t change in the About Phone settings area, still reads MDK. Running motochopper as per the instructions will work. The phone will then NAG you about the fact that it’s rooted unless you froze SEAndroid.
You then can flash custom recovery, this can be done easily by downloading Rom Manager for CWM or Goo Manager for TWRP from Play Store. I used Goo Manager and flashed the newest TWRP. The thing I noticed was that TWRP was extremely slow loading up. After flashing Hyperdrive and a few reboots, it seems to have settled down.
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.
Hello. I have done quite a bit of searching, just can't find a similar enough post to tag on some questions. Sorry if this has been asked...but I did look over a month of posts, and google searching.
I have a Note 3 from September, rooted in October...not sure how I got it done...but I jumped the gun and unrooted it with SU thinking I would be able to OTA to 4.4.2. Nope!
So, I am stuck on 4.3.
My big question is how can I get to 4.4.2 with OUT starting over on the phone.
I guess this is a backup question. I have some settings turned on that indicate that a back up is going somewhere, but I can't confirm, and I don't know what all is backed up.
Pictures are backed up, but I would hate to lose them. They are on SD card anyway...so I realize I could take the card out, but something I read suggested I might lose even the micro-simm card contents. Not sure how that would be possible.
But what about things like Quick Notes, and S Note, and Contacts, and all of my apps that I have installed, and settings for those apps.
When I rooted back in October, it worked with out disrupting anything.
How can I get that to happen now WITH an upgrade to 4.4.2 AND getting it rerooted?
If I can't upgrade with out wiping it clean, I am probably going to stay put. So, then what is the best way to root to get "Wifi Tether Router" back working...as it is the only thing I need the phone rooted for.
Finally, what is the difference between NC5 and NC5D. I saw a recent post of somebody else asking it...but none of the replies gave an answer.
Thanks for any feedback.
I don't know if this will help, but you can give it a try. First, you might want to consider that you are where most of us are trying to get back to ( i.e. 4.3 with no KNOX !!! ). Ok, I would go to Samsung Firmware, and download the latest version of 4.4.2 NC5 to your PC. I would backup that copy of 4.3 on your device to your sdcard then if have an ext sdcard copy it there, or copy that backup to your pc. Most of your Pics and data should be in that backup, that you can copy back later with a file explorer like Root Explorer. Now do a factory wipe. Then take the NC5 zip you got from sammie and extract it to a file on your desktop this will change it to a .tar file. Find a copy of Odin v1.85 don't use the 3.09 version on the Samsung website if possible. Cool, reboot your device into download mode, start odin, plug in your device to your PC. Now, load that extracted file on your desktop into PDA odin, and click start. It will take minute to read Md5 then start installing. You will lose root and recovery !!! Your new bootloader will have KNOX 0x0. So, you will have to start over with the root process, but isn't that half the FUN !!! Chainfires v1.94 supersu will root NC5. As for the difference between NC5 and NC5D, It is my understanding they are the same. The D stands for a version of NC5 that was used by Samsung employees ( i.e. programmers and developers ) in the development of NC5. :fingers-crossed::fingers-crossed:
Lokerd, I see you have read my response. Great!!! I would add the you can root 4.4.2 NC5 several ways. As I said above Chainfires v1.94 SuperSu, and One click autoroot, and Towelroot for 4.4.2. All should root your device without tripping KNOX. However, as soon as you flash a new custom recovery like TWRP or Philz CWM ( my favorite ) it will trip KNOX. If you are out of warranty no biggie, besides you need a custom recovery if you want to get back to your 4.3 backup. ( By the way remember you need the same recovery (i.e. TWRP or CWM ) that you made the 4.3 backup with, now on NC5 just a newer version. This will make it easier to recover the 4.3 backup later. They say the most popular recoveries will recover each others backups, but that is rarely the case.
jimzweb1 said:
First, you might want to consider that you are where most of us are trying to get back to ( i.e. 4.3 with no KNOX !!! ).
Click to expand...
Click to collapse
Thanks for taking the time to reply! And to reply with such a nice well though out steps.
So...I should NOT being trying to upgrade? I can do that...just reroot and be done with this. I really don't want to risk having to lose info I have put on the phone, etc. A few new features is not going to be worth it. But, reading about improved 4g and wifi performance. Wifi calling is not important to me. But it would be nice to have the camera on the lock screen...but I bet I could find something that would do that the rooted phone I had.
So, let me ask this. If I do not care about KNOX, is the process you outlined above any easier?
Thanks!
Drew
lokerd said:
Thanks for taking the time to reply! And to reply with such a nice well though out steps.
So...I should NOT being trying to upgrade? I can do that...just reroot and be done with this. I really don't want to risk having to lose info I have put on the phone, etc. A few new features is not going to be worth it. But, reading about improved 4g and wifi performance. Wifi calling is not important to me. But it would be nice to have the camera on the lock screen...but I bet I could find something that would do that the rooted phone I had.
So, let me ask this. If I do not care about KNOX, is the process you outlined above any easier?
Thanks!
Drew
Click to expand...
Click to collapse
Well, if you are out of warranty, and you don't care about KNOX go ahead and upgrade. But, consider this: One, so where clear the only reason for the 4.3 backup is to get to your pics and data at a later time. Here is a link about trying to go back http://forum.xda-developers.com/showthread.php?t=2630514 Once you install 4.4.2 NC5 ( this will include a new kernel, bootloader, baseband, and OS ) you CANNOT go to back to 4.3. If you try to install the 4.3 backup after you have upgraded to NC5 you will soft brick your phone. Then, there's KNOX what is KNOX, KNOX is security software written by the NSA for Samsung. Now I'm not saying its spyware, but Samsung is !!! You can go to Samsung's website and all the info about KNOX you need is there.
To answer your last question, no. You have to go through all the motions.
If it was me, knowing what I know now. I would stay at 4.3, install an engineering bootloader (read up on bootloaders they are not forgiving if you mess up ) then try to upgrade basebands. Here is a link for NAB engineering bootloader which should be 4.3, http://forum.xda-developers.com/showthread.php?t=2655674 Here is the link for a NC5 baseband, http://forum.xda-developers.com/showthread.php?t=2701837 I believe this will improve your 4G lte.
Last, what I'm running. I run Note 3 "Sprint" 4.4.2 NC5 ( no choice bought the device new with that OS, voided my warranty the second day I owned it ). Rooted with Philz CWM recovery ( hltespr v 6.12.9 ) KNOX disabled and removed. I definitely like 4.4.2 NC5 a lot better than 4.3 my daughters Note 3 had 4.3 before I upgraded to 4.4.2 and rooted it. Here is my XDA website http://forum.xda-developers.com/showthread.php?t=2770729 so if you do upgrade this is a good place to start.
Ok. Sorry for more noob questions.
Ok, the only thing I want to ensure is that I don't lose things like S Note, Action Memo, Contacts, Pictures, apps installed. I just don't want to redo everything. Basically, I just want to upgrade the operating system and have everything up and running like it was...just new OS. Is that possible? I understand what you are saying about not being able to use the back up. I guess I just don't understand if I can upgrade this phone with out having to start back over with everything.
I am not out of warranty (purchased October 2013), but I don't see that it would be a problem. I normally don't break or drop my phone...although I did drop it and picked up a nick a few weeks ago. It was unusual circumstances. Point is...I guess I will worry about warranty issues if that comes up. On the other hand, the home button is a getting a little finicky, so I avoid it...using swipe down, and a notification toggle to go to Home whenever possible.
I don't understand the difference between bootloader vs. flashing vs. upgrading basebands vs. rooting as opposed to those other things. it doesn't help that there are multiple ways to do each of the above.
I think I am in over myhead.
Can you help me figure out what I had done before...as it was working pretty good. I Rooted it to get root access, but not sure how I did it. It was easy, and it didn't erase anything. I think I simply used Odin. Attached is a screenshot of a folder of stuff that I might have used. Can you tell what root method I used?
I think I am just going to go back to what I had...and still with 4.3. I actually looked at my wife's identical phone that is on 4.4.2 and other than wifi calling, I don't see the camera on lock screen, so I don't really think I should be messing with stuff I can't wrap my mind around trying to get to 4.4.2.
lokerd said:
Ok. Sorry for more noob questions.
Ok, the only thing I want to ensure is that I don't lose things like S Note, Action Memo, Contacts, Pictures, apps installed. I just don't want to redo everything. Basically, I just want to upgrade the operating system and have everything up and running like it was...just new OS. Is that possible? I understand what you are saying about not being able to use the back up. I guess I just don't understand if I can upgrade this phone with out having to start back over with everything.
I am not out of warranty (purchased October 2013), but I don't see that it would be a problem. I normally don't break or drop my phone...although I did drop it and picked up a nick a few weeks ago. It was unusual circumstances. Point is...I guess I will worry about warranty issues if that comes up. On the other hand, the home button is a getting a little finicky, so I avoid it...using swipe down, and a notification toggle to go to Home whenever possible.
I don't understand the difference between bootloader vs. flashing vs. upgrading basebands vs. rooting as opposed to those other things. it doesn't help that there are multiple ways to do each of the above.
I think I am in over myhead.
Can you help me figure out what I had done before...as it was working pretty good. I Rooted it to get root access, but not sure how I did it. It was easy, and it didn't erase anything. I think I simply used Odin. Attached is a screenshot of a folder of stuff that I might have used. Can you tell what root method I used?
I think I am just going to go back to what I had...and still with 4.3. I actually looked at my wife's identical phone that is on 4.4.2 and other than wifi calling, I don't see the camera on lock screen, so I don't really think I should be messing with stuff I can't wrap my mind around trying to get to 4.4.2.
Click to expand...
Click to collapse
Cool, your version of 4.3 should be NAB and no KNOX. If this is the case then you should be able to root, and return back to stock, if you have say a hardware issue with your device and have to return it under warranty. So, according to your last post image on 10/24/2013 you used CF Autoroot, if you want to read up here is the link to that http://forum.xda-developers.com/showthread.php?t=2466423
Now to get to the latest version of CF Autoroot you need to go to ChainFires ( CF ) repository here is the link http://autoroot.chainfire.eu/ just find the model of your phone and click on File to download. Put that file on your desktop, now go to your android downloads copy and paste Odin v1.85 to your desktop. Click on Odin extract, and open it, now click on PDA a box will open, now select desktop and click on CF Auotroot. It should come up in Odin next to PDA. Now boot your device into download mode, then connect to your PC. In the upper left hand box will light up COMM: with some number in green, blue, or yellow doesn't matter just telling you that a connection was made. Now click start on the bottom of Odin, sit back and watch the magic!
When it says pass your done. Now reboot your phone if doesn't do it by itself go to your app drawer and see if SuperSu is there. To install the Recovery just follow the same steps just substitute the recovery .tar file in place of CF Autroot. I see you have ChainFires v1.65 SuperSu the latest version is v2.01 here is the link http://forum.xda-developers.com/showthread.php?t=1538053. If you use CF Autoroot it will probably install the latest version of SuperSu automatically.
I see on 10/25/2013 you downloaded CWM recovery for hltespr ( sprint ) here is the link for Philz CWM http://forum.xda-developers.com/showthread.php?t=2596001 the latest version for sprint is 6.12.9 I don't use his unified all in one recovery version, I use the sprint version, but the choice is yours. :fingers-crossed:
jimzweb1 said:
Cool, your version of 4.3 should be NAB and no KNOX.
Odin v1.85 to your desktop.
Click to expand...
Click to collapse
Thanks for the continued help. Just about ready to reroot the thing.
So, you mention using 1.85...is that only because that is what I have? The latest CF-Auto-Root came with 3.07 but I had already downloaded 3.09 a couple of days ago trying to figure stuff out. I also saw a warning about using the latest Odin...but I think it applied to trying to do the Kindle Fire, which I determined was 3.3 and not able to be rooted with out a special cable, which I have ordered.
Anyway, does it matter if I use the 3.07 that came with the latest version of CF-A-R? Should I use 3.09? Or def stick with 1.85.
EDIT #5: I end up using 1.85 and the original Root, then the new ROOT. So, does it matter that I used the Root from October vs the newest one or older Odin vs. newer? I have it up now, so it is just a matter of tryingt o figure this out.
BTW, I thought I had bricked my phone...went back and read YOUR instruction again, and got it restarted. The instructions on the main CF-A-R thread do not make it very clear.
Thanks a bundle!
Great !!! It doesn't matter which version of Odin you use, as long as it gets the job done. As for CF Autoroot, after your done rooting and boot the device back up. It my take awhile but you will automatically be asked update your apps, and SuperSu will update binarys at that time.
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.
I don't mean to beat a dead horse, as I'm sure it's been brought up. But every search I've done just brings up how to update to OC1 without losing root. All the way back to the original Motorola Droid, I've always rooted and added a custom recovery and ROM to every phone I've had. I was running Hyperdrive RLS20 and loved it. I've been using Hyperdrive since my Galaxy S3. Then I saw Hyperdrive RLS21 came out and decided I wanted to give it a shot. And although I've flashed over a few hundred ROMs no problem, this time really screwed my phone. I could only get into DL mode. I tried about 25 different ways until I had Kies fix it, which put it on 5.0.1. Can I revert down with Odin? Or is there anything I can do to get root and SU back. Any help would be much, MUCH appreciated
Nope, by taking the latest OTA (or in this case Kies) you've locked yourself into the latest version, for which there is currently no Root
That sucks. No way to use Odin in order to downgrade or anything? This is the first time since I've ever owned an android phone that I've been stuck without root
52brandon said:
That sucks. No way to use Odin in order to downgrade or anything? This is the first time since I've ever owned an android phone that I've been stuck without root
Click to expand...
Click to collapse
Nope. Locked Bootloader sucks.
Every single time there is an update these individuals always end up in this situation! !! No matter how many times they're told to wait and just not update!!!
Charlie115 said:
Every single time there is an update these individuals always end up in this situation! !! No matter how many times they're told to wait and just not update!!!
Click to expand...
Click to collapse
Don't lump me In with that crowd. I had no intention on going to 5.0.1. If you read my original post, I was upgrading to Hyperdrive KK21 from KK20 (and yes, I followed every single instruction to the T. My only guess is that the USB connection got messed up and only flashed a portion causing the problems) and it **** the bed mid-update. I couldn't get into SS recovery or even stock recovery, only DL mode. I spent 2 days without a working phone trying to flash every single Odin file that retained root and they all failed. So I used Kies to try to repair it and ended up ****ed on 5.0.1. The one solution I didn't want. I've NEVER had an android since the D1 that wasn't rooted running a custom ROM. Which is why I'm so desperately trying to get back to rooted. While 5.0.1 is actually a very nice OS, not having all the root options is killing me. And since its now 2 generations old, my hopes that a root exploit will be found, or that people even care enough to try to find one are extremely low. But, I sure hope I'm wrong, and that an exploit for one of the newer generations Galaxies will work on this one too. I'm OCD about having root and this is killing me
52brandon said:
I couldn't get into SS recovery or even stock recovery, only DL mode. I spent 2 days without a working phone trying to flash every single Odin file that retained root and they all failed.
Click to expand...
Click to collapse
If you're ever in this situation again, give up on retaining your current root, flash back to true stock (with a re-partition .pit file as well), and re-root. If you had flashed the nc5 full-wipe with the .pit file and just restored root from a clean system, you would have been fine.
52brandon said:
Don't lump me In with that crowd. I had no intention on going to 5.0.1. If you read my original post, I was upgrading to Hyperdrive KK21 from KK20 (and yes, I followed every single instruction to the T. My only guess is that the USB connection got messed up and only flashed a portion causing the problems) and it **** the bed mid-update. I couldn't get into SS recovery or even stock recovery, only DL mode. I spent 2 days without a working phone trying to flash every single Odin file that retained root and they all failed. So I used Kies to try to repair it and ended up ****ed on 5.0.1. The one solution I didn't want. I've NEVER had an android since the D1 that wasn't rooted running a custom ROM. Which is why I'm so desperately trying to get back to rooted. While 5.0.1 is actually a very nice OS, not having all the root options is killing me. And since its now 2 generations old, my hopes that a root exploit will be found, or that people even care enough to try to find one are extremely low. But, I sure hope I'm wrong, and that an exploit for one of the newer generations Galaxies will work on this one too. I'm OCD about having root and this is killing me
Click to expand...
Click to collapse
Well, you should have known better than to use kies...
Sent from my SCH-I545 using XDA Free mobile app
Honestly I don't even think that devlopers will make much effort to even find out how to root this version as its says that this is one of two updates before getting lollypop.
Development Forums are for developers to share their work and post their Roms and Mods.
Questions belong in the Q&A section.
Thread has been moved to correct section, please pay attention to XDA rules.
Root
52brandon said:
I don't mean to beat a dead horse, as I'm sure it's been brought up. But every search I've done just brings up how to update to OC1 without losing root. All the way back to the original Motorola Droid, I've always rooted and added a custom recovery and ROM to every phone I've had. I was running Hyperdrive RLS20 and loved it. I've been using Hyperdrive since my Galaxy S3. Then I saw Hyperdrive RLS21 came out and decided I wanted to give it a shot. And although I've flashed over a few hundred ROMs no problem, this time really screwed my phone. I could only get into DL mode. I tried about 25 different ways until I had Kies fix it, which put it on 5.0.1. Can I revert down with Odin? Or is there anything I can do to get root and SU back. Any help would be much, MUCH appreciated
Click to expand...
Click to collapse
KingRoot 4.1 rooted my galaxy s4 on oc1....and try flashing an nc5 tar in flashfire
You cannot flash anything with flashfire. If you flash that tar, you WILL brick.
Question
Just wondering, i have rooted my OC1 with Kingroot 4.1, now, can someone make a guide showing how to downgrade from OC1?
PD:. Sorry for my horrible english.
Epiphany^ said:
Just wondering, i have rooted my OC1 with Kingroot 4.1, now, can someone make a guide showing how to downgrade from OC1?
PD:. Sorry for my horrible english.
Click to expand...
Click to collapse
You can't downgrade from OC1.
Downgrade isn't a root issue, it is a bootloader issue. Unless the bootloader gets unlocked, we're stuck on OC1
kingroot does work
I had done the dumb thing and was impatient and did the oc1 update to later find out you can not downgrade and im on Verizon Samsung galaxy s4 (sch-i545) which even on kit kat is very limited to rooting it.. but on a whim I seen a post about king root and it mentioned that and I did see this myself but it will say not supported like it did on mine. but I figured what the hell.. whats the worst that could happen... well im rooted now and only tried because I had seen others make that comment.. well kingroot works for s4 Verizon with locked bootloader.. no need to downgrade from oc1.. just get the app and click... took less than 10 mins if I rememner right.. and I have had no pronlems in 3 days.. it oddly even fixed some of the bugs I was having with oc1 like incoming calls not ringing
Munk3ybones said:
I had done the dumb thing and was impatient and did the oc1 update to later find out you can not downgrade and im on Verizon Samsung galaxy s4 (sch-i545) which even on kit kat is very limited to rooting it.. but on a whim I seen a post about king root and it mentioned that and I did see this myself but it will say not supported like it did on mine. but I figured what the hell.. whats the worst that could happen... well im rooted now and only tried because I had seen others make that comment.. well kingroot works for s4 Verizon with locked bootloader.. no need to downgrade from oc1.. just get the app and click... took less than 10 mins if I rememner right.. and I have had no pronlems in 3 days.. it oddly even fixed some of the bugs I was having with oc1 like incoming calls not ringing
Click to expand...
Click to collapse
You have root. But you have a much lower chance of getting an unlocked Bootloader than anyone on NC5/NK1/NK4. They have root, module loading, and a potential for kexec to run custom kernels.
Don't upgrade to OC1 via OTA if you haven't already everyone! Use Muniz_ri's keeproot upgrade method!
Sent from my Nexus 6 using Tapatalk
---------- Post added at 12:53 AM ---------- Previous post was at 12:53 AM ----------
bigg6987 said:
Downgrade isn't a root issue, it is a bootloader issue. Unless the bootloader gets unlocked, we're stuck on OC1
Click to expand...
Click to collapse
Even then you're stuck. Rollback has little to do with the BL. Rollback is set at a much lower level (physically).
Sent from my Nexus 6 using Tapatalk