Hey guys, basically trying to follow this guide, since I need to wipe - clean and load the new VZW update. Reason being:
3 problems: KNOX Detected in SUPERSU, Can't update, random crashes
SUPERSU has an error Samsung KNOX has been detected. This might limit root capabilities and cause annoying popups. Try to disable KNOX?
edit:I went and downloaded v1.8 and still get the knox error above.
I then went to update and it said "The update was unsuccessful" does this due to me having safe strap installed?
Help info:
My Baseband Version is: N900VVRUBMJ7
Android Version: 4.3
Kernel Version: 3.4.0 [email protected] #1 wed oct 16 18:45:50 KST 2013
Hardware Version N900V.07
On the step by step guide here is what I understand:
1. Download Odin v3.09
2. Question Which download below should I download for my phone????
Official VRUBMJE 4.3- http://www.androidfilehost.com/?fid=23252070760975512(Retail locked N3 only)
Official VRUBMJ7 4.3- http://d-h.st/IEW(Retail Locked N3 ONLY)
Official VRUBMI9 4.3- https://docs.google.com/file/d/0B26p...LWs/edit?pli=1(Retail Locked N3 ONLY)
VZW_32gb.pit- http://www.androidfilehost.com/?fid=23159073880936457
3. Before I install, I went to Titanium Backup and I ran a backup of my apps and SMS data, is there anything else that I should backup?
4. Is it better to wipe my phone first? Right now I experience A LOT of Lag when I open my contacts (10,000) and try to type messages in my sms folder.
Edit:Basically, should I wipe the phone, is there a way to roll it back pre-root so its as if I am intalling root on a fresh device? I have more lag on this phone now than I had when I first had De La Vega (i.e typing lag, sms lag, contact lag)
really appreciate the help!
Best thing is to use Odin. There are many many threads all over on how to use it, so I won't repeat how to. But once you have odin installed, use it to flash an official firmware. Then check for updates in settings on the phone, once booted back up. Make sure it says it is up to date (mje). If not, allow it to update. Then use kingo (check Google) to root. Then install safestrap. If you followed all that, you should be good. If SuperSU gives that Knox message, allow it to disable knox.
My personal opinion, once you've rooted successfully, install a custom rom with safestrap. That way you won't have any knox messages.
♢NoteIII♢
LeftyGR said:
Best thing is to use Odin. There are many many threads all over on how to use it, so I won't repeat how to. But once you have odin installed, use it to flash an official firmware. Then check for updates in settings on the phone, once booted back up. Make sure it says it is up to date (mje). If not, allow it to update. Then use kingo (check Google) to root. Then install safestrap. If you followed all that, you should be good. If SuperSU gives that Knox message, allow it to disable knox.
My personal opinion, once you've rooted successfully, install a custom rom with safestrap. That way you won't have any knox messages.
♢NoteIII♢
Click to expand...
Click to collapse
So I need to do this today, really appreciate the help.
I looked around for the threads, it seems there are a lot of threads discussing how people brick their phones after moving to Odin.
Anyway you or someone else could be a good friend and send me a quick how to? I first did:
1. Rooted with De La Vega,
2. OTA updated last month
3. Kingo Root fix
4. Safestrap to put in SuperSU and get rid of Kingo.
I take it with Odin the process is:
1. Kies / Odin??? Not sure
2. OTA update 1
3. OTA update 2
4. Kingo Root
5. Safe Strap 3.65
6. Look up how to remove Kingo
7. Super SU
Actually the best thing to do is to download the latest .tar file. It's on a thread in the dev section. I'm not sure if it has the matching .pit file with it. But if not, grab that as well. That way there is no worries about being on the current rev.
Then root with kingo, install safestrap, and update SuperSU.
Then you should be golden.
♢NoteIII♢
LeftyGR said:
Actually the best thing to do is to download the latest .tar file. It's on a thread in the dev section. I'm not sure if it has the matching .pit file with it. But if not, grab that as well. That way there is no worries about being on the current rev.
Then root with kingo, install safestrap, and update SuperSU.
Then you should be golden.
♢NoteIII♢
Click to expand...
Click to collapse
I went to the odin step by step thread and they had these from November. I take it I should take the MJ7 file?
N900VVRUBMJ7_N900VVZWMJ7_N900VVRUBMJ7_HOME.tar
From the odin thread.
Official VRUBMJE 4.3- http://www.androidfilehost.com/?fid=23252070760975512(Retail locked N3 only)
Official VRUBMJ7 4.3- http://d-h.st/IEW(Retail Locked N3 ONLY)
Official VRUBMI9 4.3- https://d
Get mje from here
http://forum.xda-developers.com/showthread.php?t=2524572
Up to you how comfy you are with this... but what I did was boot to recovery, deleted all slots, wiped system, data, and cache from stock slot. Then while still in recovery, booted to download mode and and used odin to install the current build.
Booted up as a stock rom with no issues for me, used kingo to root, and installed ss. But like I said, only do this if you feel like you are comfortable doing so. Because you are effectively booting out of recovery to download with no way back but odin.
♢NoteIII♢
---------- Post added at 02:54 PM ---------- Previous post was at 02:45 PM ----------
And you can actually skip the pit file, because the one that we have is from the original build. Just make sure that when you use Odin the repartition check box does not have a check in it.
♢NoteIII♢
LeftyGR said:
Get mje from here
http://forum.xda-developers.com/showthread.php?t=2524572
Up to you how comfy you are with this... but what I did was boot to recovery, deleted all slots, wiped system, data, and cache from stock slot. Then while still in recovery, booted to download mode and and used odin to install the current build.
Booted up as a stock rom with no issues for me, used kingo to root, and installed ss. But like I said, only do this if you feel like you are comfortable doing so. Because you are effectively booting out of recovery to download with no way back but odin.
♢NoteIII♢
---------- Post added at 02:54 PM ---------- Previous post was at 02:45 PM ----------
And you can actually skip the pit file, because the one that we have is from the original build. Just make sure that when you use Odin the repartition check box does not have a check in it.
♢NoteIII♢
Click to expand...
Click to collapse
Thanks! Whats the difference between MJ7 MJE and all of those? Since I know my phone currently says N900VVRUBMJ7 would I still use MJE?
dpoverlord said:
Thanks! Whats the difference between MJ7 MJE and all of those? Since I know my phone currently says N900VVRUBMJ7 would I still use MJE?
Click to expand...
Click to collapse
I know there is a list somewhere of the changes, but it's pretty short except for bug fixes. There is also an update kernel.
♢NoteIII♢
LeftyGR said:
I know there is a list somewhere of the changes, but it's pretty short except for bug fixes. There is also an update kernel.
♢NoteIII♢
Click to expand...
Click to collapse
K Thanks, the only reason I was asking was since the MJ7 download was 2.2GB(N900VVRUBMJ7_N900VVZWMJ7_N900VVRUBMJ7_HOME.tar)
and
MJE was 1.4GB was a big difference in size so I dont want to install and mess it up
So I will install this one which is almost 1.4GB
ALL_N900VVRUBMJE_N900VVZWMJE_2106277_REV03_user_low_ship_MULTI_CERT.tar.md5
Thats correct right?
Would love your input.
Knox is Samsung's new fancy security software. Don't know much about it except it can get a bit wonky.
If all you use is the original ROM with root and safestrap, you got knox, bloatware, and Verizon crap. If you know how to get it "all" out, then that's fine. But a custom ROM will have all that weeded out with other tweaks and mods. This is usually the best way to go. Custom ROM's are in the development thread.
As far as you're phone running slow, I got a few things for you. First reboot to recovery and under wipe/advanced wipe, wipe dalvik cache and cache then reboot. If that doesn't help, you may need factory reset. You will not loose root by doing that.
Click to expand...
Click to collapse
Thanks,
Any specific Roms you recommend? Is the process that much different for the install? I hate the verizon crap, Just need to figure the right way to run everything.
LeftyGR said:
Get mje from here
http://forum.xda-developers.com/showthread.php?t=2524572
Up to you how comfy you are with this... but what I did was boot to recovery, deleted all slots, wiped system, data, and cache from stock slot. Then while still in recovery, booted to download mode and and used odin to install the current build.
Booted up as a stock rom with no issues for me, used kingo to root, and installed ss. But like I said, only do this if you feel like you are comfortable doing so. Because you are effectively booting out of recovery to download with no way back but odin.
♢NoteIII♢
---------- Post added at 02:54 PM ---------- Previous post was at 02:45 PM ----------
And you can actually skip the pit file, because the one that we have is from the original build. Just make sure that when you use Odin the repartition check box does not have a check in it.
♢NoteIII♢
Click to expand...
Click to collapse
For some reason the Re-Partition checkmark was checked. Am I screwed now? Or should I do something else before anything else?
dpoverlord said:
For some reason the Re-Partition checkmark was checked. Am I screwed now? Or should I do something else before anything else?
Click to expand...
Click to collapse
Sent pm. But if your phone booted back up, you're fine. If you didn't use a .pit file I may be mistaken on that.
♢NoteIII♢
Awesome, I actually used the .pit file.... Now I am trying to get Kingo to Root... 3 tries so far no luck..
Edit: it worked it installed kingo going to go into Safestrap. need to look up now how to disable Kingo I forgot how.
Related
Hi i have the following error :
When i try to click on WI-FI button comes up the following
prevention information
the device has detected an application attempting unppermitted actions and has stopped loading.To protect your device it is recomended you reboot.
I have rooted my phone using the topic here
http://forum.xda-developers.com/showthread.php?t=2258633
i had to load the
http://k0nane.info/rom/SGH-M919-UVUAMDB-k0nane.7z
file first cos i was getting an failure when installing the superuser using odin 3.0.7
my recovery is TWRP 2.5.0.0 and i am on wicked v1
Anyone else have this issue?
please delete this thread wrong section
kaniebas said:
Hi i have the following error :
When i try to click on WI-FI button comes up the following
prevention information
the device has detected an application attempting unppermitted actions and has stopped loading.To protect your device it is recomended you reboot.
I have rooted my phone using the topic here
http://forum.xda-developers.com/showthread.php?t=2258633
i had to load the
http://k0nane.info/rom/SGH-M919-UVUAMDB-k0nane.7z
file first cos i was getting an failure when installing the superuser using odin 3.0.7
my recovery is TWRP 2.5.0.0 and i am on wicked v1
Anyone else have this issue?
please delete this thread wrong section
Click to expand...
Click to collapse
I'm having the same problem. There's a fix for t-mobile that I used but since it's a sprint phone my 3g stopped working. Does anybody have a fix for this?
kaniebas said:
Hi i have the following error :
When i try to click on WI-FI button comes up the following
prevention information
the device has detected an application attempting unppermitted actions and has stopped loading.To protect your device it is recomended you reboot.
I have rooted my phone using the topic here
http://forum.xda-developers.com/showthread.php?t=2258633
i had to load the
http://k0nane.info/rom/SGH-M919-UVUAMDB-k0nane.7z
file first cos i was getting an failure when installing the superuser using odin 3.0.7
my recovery is TWRP 2.5.0.0 and i am on wicked v1
Anyone else have this issue?
please delete this thread wrong section
Click to expand...
Click to collapse
weinerwad3000 said:
I'm having the same problem. There's a fix for t-mobile that I used but since it's a sprint phone my 3g stopped working. Does anybody have a fix for this?
Click to expand...
Click to collapse
You both are running custom kernels. You have four options:
(1) Freeze the app called SEAndroid using Titanium Backup or a similar app.
(2) Use Titanium or a similar app to uninstall the KNOX application.
(3) Use Root Explorer or a similar app to browse to /system/app and delete all files beginning with KNOX
(4) Flash the stock kernel.
rawintellect said:
You both are running custom kernels. You have four options:
(1) Freeze the app called SEAndroid using Titanium Backup or a similar app.
(2) Use Titanium or a similar app to uninstall the KNOX application.
(3) Use Root Explorer or a similar app to browse to /system/app and delete all files beginning with KNOX
(4) Flash the stock kernel.
Click to expand...
Click to collapse
Thank you so much for your reply. This has been driving me nuts. I uninstalled seandroid and knox and now the prevention information warning doesnt pop up but I still cant turn on the wifi. Ill install the stock kernel and see if that works.
weinerwad3000 said:
Thank you so much for your reply. This has been driving me nuts. I uninstalled seandroid and knox and now the prevention information warning doesnt pop up but I still cant turn on the wifi. Ill install the stock kernel and see if that works.
Click to expand...
Click to collapse
What kernel are you running? Try a different custom kernel. I can assure you that the messages have nothing to do with your inability to activate wifi. That message is a well known issue.
rawintellect said:
What kernel are you running? Try a different custom kernel. I can assure you that the messages has nothing to do with your inability to activate wifi. That message is a well known issue.
Click to expand...
Click to collapse
kernel version says 3.4.0-529760 [email protected] #1 Sat Apr 27 18:12:21 KST 2013.
my baseband ends in mdc and build number ends in mdl. Would that have any effect on it? I can't flash any other roms in rom manager because my 3g is too slow and an error occurs every time I try to flash it.
weinerwad3000 said:
kernel version says 3.4.0-529760 [email protected] #1 Sat Apr 27 18:12:21 KST 2013.
my baseband ends in mdc and build number ends in mdl. Would that have any effect on it? I can't flash any other roms in rom manager because my 3g is too slow and an error occurs every time I try to flash it.
Click to expand...
Click to collapse
Well it seems you're running an older kernel on a newer rom. without knowing the ROM I'd suggest you run a new kernel. I use this. It should work well for you.
Make sure you download the correct version. Use ASOP if you're running and ASOP ROM like CM. Use Touchwiz if you're running a Touchwiz ROM.
rawintellect said:
Well it seems you're running an older kernel on a newer rom. without knowing the ROM I'd suggest you run a new kernel. I use this. It should work well for you.
Make sure you download the correct version. Use ASOP if you're running and ASOP ROM like CM. Use Touchwiz if you're running a Touchwiz ROM.
Click to expand...
Click to collapse
Thanks. I'll try it out. I'm just running the stock rom. That's the only rom that I'm having wifi problems with.
I'm relatively new to using odin so when I try to flash the kernal i click on pda but the zip file isn't listed. What do?
weinerwad3000 said:
Thanks. I'll try it out. I'm just running the stock rom. That's the only rom that I'm having wifi problems with.
I'm relatively new to using odin so when I try to flash the kernal i click on pda but the zip file isn't listed. What do?
Click to expand...
Click to collapse
Ahhh it's not flashable in ODIN. you'll need to install a custom recovery via ODIN and then flash it. I use TWRP 2.5.0.2. It seems to be the most stable.
1) Click this and download the odin flashable version of TWRP.
2) Open ODIN. Click PDA select the file you downloaded
3) click START.
4) your phone will reboot.
Now you have TWRP installed. To flash a zip file:
1) save it to your sd card.
2) Boot into recovery. (to boot into recovery just reboot your phone. when you feel it vibrate press the volume up button until it boots into recovery)
3) click the INSTALL button.
4) find the zip file on your SDCARD. select it.
5) swipe to flash
6) press the wipe cache/dalvik button.
That's it.
rawintellect said:
Ahhh it's not flashable in ODIN. you'll need to install a custom recovery via ODIN and then flash it. I use TWRP 2.5.0.2. It seems to be the most stable.
1) Click this and download the odin flashable version of TWRP.
2) Open ODIN. Click PDA select the file you downloaded
3) click START.
4) your phone will reboot.
Now you have TWRP installed. To flash a zip file:
1) save it to your sd card.
2) Boot into recovery. (to boot into recovery just reboot your phone. when you feel it vibrate press the volume up button until it boots into recovery)
3) click the INSTALL button.
4) find the zip file on your SDCARD. select it.
5) swipe to flash
6) press the wipe cache/dalvik button.
That's it.
Click to expand...
Click to collapse
okay gotcha. that makes more sense. Didn't think you could install a zip with odin but wasn't sure. When I install different recoveries in odin I can't flash my recoveries and that's why I was trying to get cwm recovery. Thank you for your help. I'll let you know how it goes.
---------- Post added at 09:07 PM ---------- Previous post was at 08:51 PM ----------
Awesome. Thank you soo much. Finally got it working. Now if I could just fix my cm10 rom I'll be set. I'm having issues with several apps in cm10. Can only access google play, facebook, etc. sometimes. They work fine on wifi but with 3g they almost never work.
---------- Post added at 09:11 PM ---------- Previous post was at 09:07 PM ----------
rawintellect said:
Ahhh it's not flashable in ODIN. you'll need to install a custom recovery via ODIN and then flash it. I use TWRP 2.5.0.2. It seems to be the most stable.
1) Click this and download the odin flashable version of TWRP.
2) Open ODIN. Click PDA select the file you downloaded
3) click START.
4) your phone will reboot.
Now you have TWRP installed. To flash a zip file:
1) save it to your sd card.
2) Boot into recovery. (to boot into recovery just reboot your phone. when you feel it vibrate press the volume up button until it boots into recovery)
3) click the INSTALL button.
4) find the zip file on your SDCARD. select it.
5) swipe to flash
6) press the wipe cache/dalvik button.
That's it.
Click to expand...
Click to collapse
Is there anyway to get my cwm recoveries to work in twrp? I don't want to keep switching back and forth to make new recoveries.
nevermind i was looking at the internal sdcard. Got it. Thanks a million
weinerwad3000 said:
okay gotcha. that makes more sense. Didn't think you could install a zip with odin but wasn't sure. When I install different recoveries in odin I can't flash my recoveries and that's why I was trying to get cwm recovery. Thank you for your help. I'll let you know how it goes.
---------- Post added at 09:07 PM ---------- Previous post was at 08:51 PM ----------
Awesome. Thank you soo much. Finally got it working. Now if I could just fix my cm10 rom I'll be set. I'm having issues with several apps in cm10. Can only access google play, facebook, etc. sometimes. They work fine on wifi but with 3g they almost never work.
---------- Post added at 09:11 PM ---------- Previous post was at 09:07 PM ----------
Is there anyway to get my cwm recoveries to work in twrp? I don't want to keep switching back and forth to make new recoveries.
nevermind i was looking at the internal sdcard. Got it. Thanks a million
Click to expand...
Click to collapse
you can take new backups with TWRP.
also CM10 is great but ASOP roms in my opinion are for more experienced users. I'd play around with the stock Touchwiz rom first.
I've been getting this error all day today. I'm on MDL ROM. I restored it from my previous CM10.1 installation. While I was on CM10.1, I flashed the MF9 firmware. Later that day I did a factory reset in recovery and restored my previous NANDROID MDL backup. I started getting this Prevention Information error.
My baseband was MF9 while my build number was MDL. I read that I had to put the MDL firmware back on the phone. I got the MDL firmware from this link here http://forum.xda-developers.com/showthread.php?t=2338919 . After using ODIN to put the firmware back on, I went into TWRP and cleared cache and dalvik and rebooted. I'm still getting the error even though baseband and build number are both MDL.
Any ideas? Thanks!
Sydius08 said:
I've been getting this error all day today. I'm on MDL ROM. I restored it from my previous CM10.1 installation. While I was on CM10.1, I flashed the MF9 firmware. Later that day I did a factory reset in recovery and restored my previous NANDROID MDL backup. I started getting this Prevention Information error.
My baseband was MF9 while my build number was MDL. I read that I had to put the MDL firmware back on the phone. I got the MDL firmware from this link here http://forum.xda-developers.com/showthread.php?t=2338919 . After using ODIN to put the firmware back on, I went into TWRP and cleared cache and dalvik and rebooted. I'm still getting the error even though baseband and build number are both MDL.
Any ideas? Thanks!
Click to expand...
Click to collapse
This has been happening alot if you install bootloader, kernel, firmware, etc seperately. to avoid this odin back to full stock mf9.
Sent from my SPH-L720
rawintellect said:
You both are running custom kernels. You have four options:
(1) Freeze the app called SEAndroid using Titanium Backup or a similar app.
(2) Use Titanium or a similar app to uninstall the KNOX application.
(3) Use Root Explorer or a similar app to browse to /system/app and delete all files beginning with KNOX
(4) Flash the stock kernel.
Click to expand...
Click to collapse
This worked for me.
Prevention Information on Stock rom - how to get rid of it?
I started receiving this error after updating to last stock Vodafone firmware. Does anybody know how to get rid of this on a stock rom? I am not rooted.
David Vlk said:
I started receiving this error after updating to last stock Vodafone firmware. Does anybody know how to get rid of this on a stock rom? I am not rooted.
Click to expand...
Click to collapse
Just odin full mf9 stock tar. This happens because of different firmware versions together or if your rooted and such just use any root file explorer and delete all apps in system that begin with knox
Downgrade
But if I go to an older stock then I receive update notifications again and that is something I see even more annoying than selecting inform me no sooner than in 30 days option offered by Prevention information popup. Correct? Or when flashing stock through Odin again (not downgrade but doing the same thing again but through Odin) the problem dissapears?
David Vlk said:
But if I go to an older stock then I receive update notifications again and that is something I see even more annoying than selecting inform me no sooner than in 30 days option offered by Prevention information popup. Correct? Or when flashing stock through Odin again (not downgrade but doing the same thing again but through Odin) the problem dissapears?
Click to expand...
Click to collapse
If you go to mf9 thats the newest update we have really so you wouldnt get a update notification. But theres three ways to solve your problem. One odin back to stock MDL and accept then accept the update. Or second you can reflash the same firmware you have again thru odin to make sure everythin is where its suppose to be or 3rd use a root file explorer and in system/apps delete every app that begins with knox.
Also i had the same problem after i updated the S4, my problem was with K9-email client i just remove it and all things now are good.
I know I am stupid, but I am trying to just get this phone to work. I did try and search for something that would come close to what I am encountering, but so far I can't find anything that would suggest a possible workaround. So, I hope this is in line with the rules, if not, please let me know and I will remove this myself pronto.
I was on 4.3 (MK2), rooted with TWRP and installed Xposed, all was fine and well, until AT&T decided to attack my phone to "remind" me to update to a newer version. After a few weeks I finally gave in, and knowing that I have somewhat heavily modified this phone, I went ahead and disable and uninstall Xposed, then head on to try and flash NC1 onto this phone via TWRP 3.72.
I was following this post, using post#3, and all was well, expect when I tried to flash AP using Odin, it was late and I failed to catch the fact Odin didn't connect my phone, so I guess the kernel didn't update. Then I went ahead and try booting it up. It got to the AT&T globe logo, only it has orange strips instead of blue. I waited maybe 15 mins for it to boot, and upon thinking it is not working, I pulled the battery and went into recovery and found I had a very early version backup, which I then restored that. It did boot! But the wifi wouldn't turn on, so I went and checked, the baseband was on NC1, but everything else is at MK2 (4.3). At that point, I give up and went to bed.
This morning, after giving it some good thoughts and research, I tried to Odin again, and this time I succeed, Odin recognizes my phone, and it flash the AP as it should. But when I try boot it up, it would only get to "safestrap disabled" and then black screen. After that, I can only get into the custom recovery, but no matter what I try, full/advance wipe, install, it would show something like "E: cannot mount system" so no matter what ROM I downloaded, it would not install, and when I try and re-boot, it would warn me that there is " No System"
So my question now is: since I can still see and access recovery, not all hope is lost, but since this is a work phone, I do need it back up and running, and I need it fast. How should I proceed from here? I tried straight flash a GPE ROM from here, but it would still run into the error of "E: cannot mount system" and trying to wipe/advance wipe would not work either.
If anyone has any idea what kind of problems I am running into, I am all ears to hear and try my best to get my work phone back up and running. Thank you all for taking you time to read, think and maybe help.
iantung329 said:
I know I am stupid, but I am trying to just get this phone to work. I did try and search for something that would come close to what I am encountering, but so far I can't find anything that would suggest a possible workaround. So, I hope this is in line with the rules, if not, please let me know and I will remove this myself pronto.
I was on 4.3 (MK2), rooted with TWRP and installed Xposed, all was fine and well, until AT&T decided to attack my phone to "remind" me to update to a newer version. After a few weeks I finally gave in, and knowing that I have somewhat heavily modified this phone, I went ahead and disable and uninstall Xposed, then head on to try and flash NC1 onto this phone via TWRP 3.72.
I was following this post, using post#3, and all was well, expect when I tried to flash AP using Odin, it was late and I failed to catch the fact Odin didn't connect my phone, so I guess the kernel didn't update. Then I went ahead and try booting it up. It got to the AT&T globe logo, only it has orange strips instead of blue. I waited maybe 15 mins for it to boot, and upon thinking it is not working, I pulled the battery and went into recovery and found I had a very early version backup, which I then restored that. It did boot! But the wifi wouldn't turn on, so I went and checked, the baseband was on NC1, but everything else is at MK2 (4.3). At that point, I give up and went to bed.
This morning, after giving it some good thoughts and research, I tried to Odin again, and this time I succeed, Odin recognizes my phone, and it flash the AP as it should. But when I try boot it up, it would only get to "safestrap disabled" and then black screen. After that, I can only get into the custom recovery, but no matter what I try, full/advance wipe, install, it would show something like "E: cannot mount system" so no matter what ROM I downloaded, it would not install, and when I try and re-boot, it would warn me that there is " No System"
So my question now is: since I can still see and access recovery, not all hope is lost, but since this is a work phone, I do need it back up and running, and I need it fast. How should I proceed from here? I tried straight flash a GPE ROM from here, but it would still run into the error of "E: cannot mount system" and trying to wipe/advance wipe would not work either.
If anyone has any idea what kind of problems I am running into, I am all ears to hear and try my best to get my work phone back up and running. Thank you all for taking you time to read, think and maybe help.
Click to expand...
Click to collapse
Are you sure you have Safestrap 3.72? It should be working if you do. Either way, try flashing the MK2 AP file/kernel from the downgrade thread or the KitKat Toolkit. That should guarantee it mounts and then you can try again. If that doesn't work, you might just have to ODIN NB1 and start from the downgrade.
DeadlySin9 said:
Are you sure you have Safestrap 3.72? It should be working if you do. Either way, try flashing the MK2 AP file/kernel from the downgrade thread or the KitKat Toolkit. That should guarantee it mounts and then you can try again. If that doesn't work, you might just have to ODIN NB1 and start from the downgrade.
Click to expand...
Click to collapse
I am now just trying to boot up the phone to check, and right now it is stuck at the Samsung Custom lock (white). So I guess either Odin NB1 or MK2 and start from there?
The only thing I think its odd is, it keeps telling me that it can't mount the system, and I can't for the live of me figure why that would even happen....
iantung329 said:
I am now just trying to boot up the phone to check, and right now it is stuck at the Samsung Custom lock (white). So I guess either Odin NB1 or MK2 and start from there?
The only thing I think its odd is, it keeps telling me that it can't mount the system, and I can't for the live of me figure why that would even happen....
Click to expand...
Click to collapse
If you had not taken the OTA from AT&T your phone bootloader is still on MK2.
Did you flash NC1 before or after you received OTA from AT&T.
sway8966 said:
If you had not taken the OTA from AT&T your phone bootloader is still on MK2.
Did you flash NC1 before or after you received OTA from AT&T.
Click to expand...
Click to collapse
I was not able to take the OTA from AT&T, due to that it was rooted and Xposed, so somehow the system check would backfire. When I got the phone, it was on MK2, and I only rooted it and installed custom recovery, for I only need to be able to delete some stuff at will, thus, the root access.
Actually, since I can't boot pass the Samsung custom lock, is it still possible to use Odin? I would have thought Odin would not recognize the phone since it is not on.....
iantung329 said:
I was not able to take the OTA from AT&T, due to that it was rooted and Xposed, so somehow the system check would backfire. When I got the phone, it was on MK2, and I only rooted it and installed custom recovery, for I only need to be able to delete some stuff at will, thus, the root access.
Actually, since I can't boot pass the Samsung custom lock, is it still possible to use Odin? I would have thought Odin would not recognize the phone since it is not on.....
Click to expand...
Click to collapse
It will still work, ODIN requires you to hold one of the volume buttons while powering on to go into download mode on the phone which doesn't require booting to system.
DeadlySin9 said:
It will still work, ODIN requires you to hold one of the volume buttons while powering on to go into download mode on the phone which doesn't require booting to system.
Click to expand...
Click to collapse
OK, so just tried Odin it using the files from Deadly Venom Kitkat Magic Tool. Odin caught the phone alright, but after the files are lined up (the mk2 ones), it give me the following:
Get PIT for mapping..
There is no PIT partition
All threads completed. (succeed 0/ failed 1)
And of course, the top also showed FAIL!
Any suggestions? Try going directly to NB1 and downgrade from there?
iantung329 said:
OK, so just tried Odin it using the files from Deadly Venom Kitkat Magic Tool. Odin caught the phone alright, but after the files are lined up (the mk2 ones), it give me the following:
Get PIT for mapping..
There is no PIT partition
All threads completed. (succeed 0/ failed 1)
And of course, the top also showed FAIL!
Any suggestions? Try going directly to NB1 and downgrade from there?
Click to expand...
Click to collapse
So after an all-night, I finally got it back up and running. Here is what I did, in case someone runs into the same problem.
I grabbed the MK2 file here, un-zip it, Odin it to its respective slots, and then flash it. It took over 10 mins, but it did finish the flash, and Odin showed "PASS!"
So, now I have another question, I booted it up like when it first came in the box, so went through and did all the setup. I went into setting, and I see the following:
Android version: 4.3
Baseband: I337-MK2
Kernel: signed Sat Nov 16 14:33:13 KST 2013
Build #: JSS-MK2
So if I want to do this upgrade to 4.4.2/4.4.3 again, would I consider my phone as stock MK2 that has not been tried to upgrade to 4.4.2/4.4.3? I did try and confirmed that I don't have root (obviously), so I guess I have to treat this phone as if it never took any updates/modifications? Then I would ask which route to follow to ensure the best and most confirm result of upgrading to either 4.4.2/4.4.3.
Thanks all for your thoughts on how to de-bug this. :laugh:
iantung329 said:
So after an all-night, I finally got it back up and running. Here is what I did, in case someone runs into the same problem.
I grabbed the MK2 file here, un-zip it, Odin it to its respective slots, and then flash it. It took over 10 mins, but it did finish the flash, and Odin showed "PASS!"
So, now I have another question, I booted it up like when it first came in the box, so went through and did all the setup. I went into setting, and I see the following:
Android version: 4.3
Baseband: I337-MK2
Kernel: signed Sat Nov 16 14:33:13 KST 2013
Build #: JSS-MK2
So if I want to do this upgrade to 4.4.2/4.4.3 again, would I consider my phone as stock MK2 that has not been tried to upgrade to 4.4.2/4.4.3? I did try and confirmed that I don't have root (obviously), so I guess I have to treat this phone as if it never took any updates/modifications? Then I would ask which route to follow to ensure the best and most confirm result of upgrading to either 4.4.2/4.4.3.
Thanks all for your thoughts on how to de-bug this. :laugh:
Click to expand...
Click to collapse
Yes your phone is stock MK2.
I do not know about 4.4.3 but you can find many 4.4.2 custom rom in the developer section.
First you need to root the phone. You can get the required files and instruction from here.
Second, you need to install the custom recovery. Since you are on MK2 you need to use Safestrap version 3.71. You can get the file and instructions here.
Once you have rooted and finish installing the SS (safestrap) you can find the custom rom in the developer section. Find the roms with SS option.
sway8966 said:
Yes your phone is stock MK2.
I do not know about 4.4.3 but you can find many 4.4.2 custom rom in the developer section.
First you need to root the phone. You can get the required files and instruction from here.
Second, you need to install the custom recovery. Since you are on MK2 you need to use Safestrap version 3.71. You can get the file and instructions here.
Once you have rooted and finish installing the SS (safestrap) you can find the custom rom in the developer section. Find the roms with SS option.
Click to expand...
Click to collapse
Sway8966, thank you for saving my behind more than once.
I will be following your instruction as to rooting the phone and also install custom recovery. However, if you see my first post, it seems I need to first install SS 3.71 to root, then SS 3.72 to upgrade to NB1/NC1? I will take a safe bet that I can't just use SS 3.72 to avoid brick. Also, that GPE version ROM, I had trouble finding the kernel, would there be a place to find it? Or is it in the package? I un-zipped it, but can't find the file that looks like the kernel in it.
Thanks again. :laugh:
iantung329 said:
Sway8966, thank you for saving my behind more than once.
I will be following your instruction as to rooting the phone and also install custom recovery. However, if you see my first post, it seems I need to first install SS 3.71 to root, then SS 3.72 to upgrade to NB1/NC1? I will take a safe bet that I can't just use SS 3.72 to avoid brick. Also, that GPE version ROM, I had trouble finding the kernel, would there be a place to find it? Or is it in the package? I un-zipped it, but can't find the file that looks like the kernel in it.
Thanks again. :laugh:
Click to expand...
Click to collapse
iantung329 I am glad to help you out.
You do not need to install SS recovery first to root the phone. Rooting is done by using the adb command to push the super user in the system area.
Since you are in a MK2 firmware/bootloader Safestrap 3.71 is the only one you can use.
Also your bootloader is MK2 so I would not go to install the NB1/NC1 system file on your phone. SS 3.72 is for the NB1/NC1.
To upgrade your phone to 4.4.2 OS you can find the custom rom packages (including the kernel) in here.
Bootloader MK2 and above can not use the custom kernel since there is no exploit for the kernel out so far. So you need to choose the TOUCHWIZ rom with SS version, not AOSP (Android open-source project) rom.
We are not supposed to tell you which rom to choose because people might not have similar taste or expectation in the choice of rom. Read around and choose the rom that you want.
If you'd asked me, I use Golden Eye rom. I am on NC1. You can see that in my signature section.
I will tell you how I installed the Golden eye rom as an example.
I download the package (zip file), my NC1 stock kernel file and superSU file.
Using the safestrap I installed the package zip file. After the installation finished I installed the NC1 kernel file and SuperSU file. Then I reboot my phone. That is. Other roms might have different instructions.
iantung329 said:
Sway8966, thank you for saving my behind more than once.
I will be following your instruction as to rooting the phone and also install custom recovery. However, if you see my first post, it seems I need to first install SS 3.71 to root, then SS 3.72 to upgrade to NB1/NC1? I will take a safe bet that I can't just use SS 3.72 to avoid brick. Also, that GPE version ROM, I had trouble finding the kernel, would there be a place to find it? Or is it in the package? I un-zipped it, but can't find the file that looks like the kernel in it.
Thanks again. :laugh:
Click to expand...
Click to collapse
sway8966 said:
iantung329 I am glad to help you out.
You do not need to install SS recovery first to root the phone. Rooting is done by using the adb command to push the super user in the system area.
Since you are in a MK2 firmware/bootloader Safestrap 3.71 is the only one you can use.
Also your bootloader is MK2 so I would not go to install the NB1/NC1 system file on your phone. SS 3.72 is for the NB1/NC1.
To upgrade your phone to 4.4.2 OS you can find the custom rom packages (including the kernel) in here.
Bootloader MK2 and above can not use the custom kernel since there is no exploit for the kernel out so far. So you need to choose the TOUCHWIZ rom with SS version, not AOSP (Android open-source project) rom.
We are not supposed to tell you which rom to choose because people might not have similar taste or expectation in the choice of rom. Read around and choose the rom that you want.
If you'd asked me, I use Golden Eye rom. I am on NC1. You can see that in my signature section.
I will tell you how I installed the Golden eye rom as an example.
I download the package (zip file), my NC1 stock kernel file and superSU file.
Using the safestrap I installed the package zip file. After the installation finished I installed the NC1 kernel file and SuperSU file. Then I reboot my phone. That is. Other roms might have different instructions.
Click to expand...
Click to collapse
As sway said, you do not need Safestrap to root, you just use Saferoot and you have root. However, you can actually use SS 3.72 and it would be better to use it since you can then mount /system even while on a 4.4.2 kernel. You can also use the single GPE located in the general section. Sway's ROM flashing instructions are correct, but also remember to flash the kernel module zip in Safestrap, and you would be using the MLD set since you have the MK2 bootloader. The kernels and everything you need are included in the KitKat Magic Toolkit.
DeadlySin9 said:
As sway said, you do not need Safestrap to root, you just use Saferoot and you have root. However, you can actually use SS 3.72 and it would be better to use it since you can then mount /system even while on a 4.4.2 kernel. You can also use the single GPE located in the general section. Sway's ROM flashing instructions are correct, but also remember to flash the kernel module zip in Safestrap, and you would be using the MLD set since you have the MK2 bootloader. The kernels and everything you need are included in the KitKat Magic Toolkit.
Click to expand...
Click to collapse
:crying::crying::crying:
Sigh, I will admit, I have done it again, so I am back to flashing the MK2 file from a few post ago.
I think I will either go with stock rooted ROM or the GPE version, I think the only thing I am missing is the kernel, which I found in one of the post I have to Loki it since I am on AT&T, but I can't find the Loki software, or would that be using Odin as well?
The only reason I am looking to root this phone is so that I can tether. Traveling roughly 2-3 weeks a month ain't fun, but not all hotels have free wifi, so having my phone rooted and able to tether is like a life line. Also, after I tried GB, its wonderful! Apart from I can't find a good quiet time option, everything is awesome being able to use GB and AdBlock. Does either Sway or DeadlySin9 have a good recommendation for quiet time app/mod?
As soon as I get the phone back on stock MK2, I will be looking into either stock root ROM or GPE version. Thanks all! :fingers-crossed:
iantung329 said:
:crying::crying::crying:
Sigh, I will admit, I have done it again, so I am back to flashing the MK2 file from a few post ago.
I think I will either go with stock rooted ROM or the GPE version, I think the only thing I am missing is the kernel, which I found in one of the post I have to Loki it since I am on AT&T, but I can't find the Loki software, or would that be using Odin as well?
The only reason I am looking to root this phone is so that I can tether. Traveling roughly 2-3 weeks a month ain't fun, but not all hotels have free wifi, so having my phone rooted and able to tether is like a life line. Also, after I tried GB, its wonderful! Apart from I can't find a good quiet time option, everything is awesome being able to use GB and AdBlock. Does either Sway or DeadlySin9 have a good recommendation for quiet time app/mod?
As soon as I get the phone back on stock MK2, I will be looking into either stock root ROM or GPE version. Thanks all! :fingers-crossed:
Click to expand...
Click to collapse
OK. @DeadlySin9, got the final question (hopefully :fingers-crossed
I am going to flash GPE version (here) and I will be following the direction on that, wipe, flash, kernel then reboot. You mentioned that I should use the MLD kernels, but which one is that in the Kitkat magic tool? AP_MLD, BL_MLD? And now I have SS 3.71 on the phone, would you recommend uninstalling that and install SS 3.72 instead, since I will be flashing GPE version anyway?
Also, what of this ROM (here)? I guess I can't flash this one?
iantung329 said:
OK. @DeadlySin9, got the final question (hopefully :fingers-crossed
I am going to flash GPE version (here) and I will be following the direction on that, wipe, flash, kernel then reboot. You mentioned that I should use the MLD kernels, but which one is that in the Kitkat magic tool? AP_MLD, BL_MLD? And now I have SS 3.71 on the phone, would you recommend uninstalling that and install SS 3.72 instead, since I will be flashing GPE version anyway?
Also, what of this ROM (here)? I guess I can't flash this one?
Click to expand...
Click to collapse
Actually, neither of those work. There's one in the General section, with Safestrap in the thread title. That's the one you need. I do recommend going to 3.72 on Safestrap, and you need to use both the AP and BL files in ODIN.
Sent from my SGH-I337 running GPE
DeadlySin9 said:
Actually, neither of those work. There's one in the General section, with Safestrap in the thread title. That's the one you need. I do recommend going to 3.72 on Safestrap, and you need to use both the AP and BL files in ODIN.
Sent from my SGH-I337 running GPE
Click to expand...
Click to collapse
This is the only one I can find (here)
Also, by the look of it, paid apps wouldn't work in this ROM, that might be a problem.
Here is another one that I was considering from the start (here), but I am not sure if I should follow the first post or second?
iantung329 said:
This is the only one I can find (here)
Also, by the look of it, paid apps wouldn't work in this ROM, that might be a problem.
Here is another one that I was considering from the start (here), but I am not sure if I should follow the first post or second?
Click to expand...
Click to collapse
If you're still on MK2 then you can use the second one. And yeah, you can't download paid apps from the Play Store for some reason.
DeadlySin9 said:
If you're still on MK2 then you can use the second one. And yeah, you can't download paid apps from the Play Store for some reason.
Click to expand...
Click to collapse
@DeadlySin9, thanks for pointing out the correct one to use, and yes, I am still stock on MK2, rooted and have not installed SS, pending the version discussion. I will go ahead and install SS 3.72 and the ROM from the first post and :fingers-crossed: that it will work wonders.
The reason that I am choosing this over the GPE, don't get me wrong, GPE I think is better, but no download paid apps is not going to work for me, some apps like, root explorer and a few others are a must on the phone. So that's a bummer. I wish it works, then I can just flash and be in peace.
Thank you @sway8966 also for helping out on this. I just freaked out when I found out the work phone was dead.....
**You can begin the following process from any Build/ROM but you must already have Root Access**
**Required** FlashFire - Play BETA - PREVIEW
1. Join the G+ community using the same Google account as you're using for Play on your phone/tablet Here.
2. Sign up to receive the BETA versions from Play Here.
- Use the link provided after sign-up to download the app.
**Caution!**The process below is only for the Sprint G900P S5 Variant! Use on any other device may result in a hardbrick.
Download:
- G900P_OA6_Stock_Rooted_ROM (File removed for safety reasons. See here: http://forum.xda-developers.com/showpost.php?p=61362280&postcount=94)
Set your screen timeout setting to 10 mins before beginning!
1. Place the ROM onto your device (use either internal or ext-sdcard).
2. Open the FlashFire app and "Agree" to the Terms and Conditions.
3. Press "(+)" twice to bring up the "Actions" menu.
4. Select "Flash Zip or OTA" and locate and select the ROM. Leave "Auto-mount" unchecked under the "Options" menu and press the checkmark to continue.
5. From the main menu Uncheck all options under "EverRoot" and use default "Reboot" settings.
6. Last, press the lightning bolt then "Ok" to begin the flash .
The screen will turn black then display the contents of your system before beginning the flash. FlashFire will pause for about 1 minute while flashing the "system" partition. Once complete your device will reboot and pause on the Sprint splash screen for about 1 - 2 minutes before completely rebooting. Done!
Tip: for blazing fast speed turn off animations from Developer Options and reboot!
Known Issues:
- None!
Notes:
1. This process will not affect your knox warranty flag.
2. The above process will update your Modem, Non-hlos, System, Kernel, Stock Recovery, and Bootloader to OA6.
3. As of 5/7/2015 no need to wipe prior to flashing! The ROM will automatically perform a factory data reset.
4. If you are currently unrooted and on a non-"Towelroot-able" firmware version you must a)downgrade to NE5 using Odin, b)root using Towelroot then proceed with the above process.
reserved
I'm curious to see if this works...unfortnately, i can't try it right now though.
i may attempt this later today. ive been wanting to put other roms on it. so i guess if it does trip knox, thats ok.
Has anyone done this? Success? Failure? I've always read that you can't flash firmware/modem via mobile Odin.
I am currently 4.4.4 and stock unrooted. I have to downgrade to 4.4.2, use towelroot, install Mobile Odin and then I will be able to try this out.
muniz_ri said:
***I initially put this ROM together for a User in another thread who theorized that you can update to Stock, Rooted, OA6 using Mobile Odin while maintaining your knox warranty flag at 0x0. Unfortunately he inadvertantly flashed TWRP before testing this method and tripped his knox warranty flag. I am putting this out there if anyone else that currently has a knox warranty flag of 0x0 is brave enough to try it***
Prerequisites: You can begin this process from any previous Build/ROM but you must already have root and MobileOdin Pro installed.
1. Place the G900P_OA6_100%_Stock_Rooted_ROM onto your ext-sdcard.
2. Using Mobile Odin select the ROM from the OTA/Zip slot.
3. Uncheck "Everoot", "Inject SuperSu", and "Inject Mobile Odin."
4. Select to Reboot to Download Mode then Flash the ROM.
5. Once the Flash is complete and you are in Download Mode flash the G900P_OA6_Stock_Partitions using Odin's PDA slot (AP in Odin v3.09+). Done!
Notes:
1. The above process will update your Modem, Non-hlos, System, Kernel, Stock Recovery, and Bootloader to OA6.
Click to expand...
Click to collapse
I am willing to give this a try right now. However, I have not rooted since updating to 5.0 What is the best way to establish a Knox trip-free root? Will kernel downgrades and towelrooting still work?
---------- Post added at 10:45 PM ---------- Previous post was at 10:39 PM ----------
Ramer said:
Has anyone done this? Success? Failure? I've always read that you can't flash firmware/modem via mobile Odin.
Click to expand...
Click to collapse
I can actually confirm that flashing stock firmware is possible with Mobile Odin Pro as far back as the Galaxy S3 However, I have honestly never tried a stock firmware flash via Mobile Odin since Samsung's introduction of Knox..
MooreAJr said:
I am willing to give this a try right now. However, I have not rooted since updating to 5.0 What is the best way to establish a Knox trip-free root? Will kernel downgrades and towelrooting still work?
---------- Post added at 10:45 PM ---------- Previous post was at 10:39 PM ----------
I can actually confirm that flashing stock firmware is possible with Mobile Odin Pro as far back as the Galaxy S3 However, I have honestly never tried a stock firmware flash via Mobile Odin since Samsung's introduction of Knox..
Click to expand...
Click to collapse
I'm really interested in knowing your results. With Kitkat on the Sprint S5 it never seemed successful because of the modem. Thanks for "taking one" for the team.
MooreAJr said:
I am willing to give this a try right now. However, I have not rooted since updating to 5.0 What is the best way to establish a Knox trip-free root? Will kernel downgrades and towelrooting still work?
---------- Post added at 10:45 PM ---------- Previous post was at 10:39 PM ----------
I can actually confirm that flashing stock firmware is possible with Mobile Odin Pro as far back as the Galaxy S3 However, I have honestly never tried a stock firmware flash via Mobile Odin since Samsung's introduction of Knox..
Click to expand...
Click to collapse
You will need to Odin flash the previous "towelrootable" firmware, root, install mobile odin then follow the above process.
muniz_ri said:
You will need to Odin flash the previous "towelrootable" firmware, root, install mobile odin then follow the above process.
Click to expand...
Click to collapse
Wait, but I thought flashing an entire previous firmware resulted in hard-bricks because of Knox and its bootloader? I am not willing to try a flash of an old firmware if it risks bricking my device.
MooreAJr said:
Wait, but I thought flashing an entire previous firmware resulted in hard-bricks because of Knox and its bootloader? I am not willing to try a flash of an old firmware if it risks bricking my device.
Click to expand...
Click to collapse
You can flash any stock tar without hard bricking. I've went from 4.4.4 to 5.0 and back prior to running the latest Android version with no problems
MooreAJr said:
Wait, but I thought flashing an entire previous firmware resulted in hard-bricks because of Knox and its bootloader? I am not willing to try a flash of an old firmware if it risks bricking my device.
Click to expand...
Click to collapse
banccalif said:
You can flash any stock tar without hard bricking. I've went from 4.4.4 to 5.0 and back prior to running the latest Android version with no problems
Click to expand...
Click to collapse
Correct, all G900P firmware aboots allow for downgrading to any of them via Odin. As for the above process, even though there is no risk of permanent damage to your device it would help Everyone if someone with enough experience attempt it so that we can get accurate results. There is no point in someone with little experience trying it and doing it incorrectly then reporting back that it did not work.
banccalif said:
You can flash any stock tar without hard bricking. I've went from 4.4.4 to 5.0 and back prior to running the latest Android version with no problems
Click to expand...
Click to collapse
Alright, sounds good then. I'll give it all a go
muniz_ri said:
Correct, all G900P firmware aboots allow for downgrading to any of them via Odin. As for the above process, even though there is no risk of permanent damage to your device it would help Everyone if someone with enough experience attempt it so that we can get accurate results. There is no point in someone with little experience trying it and doing it incorrectly then reporting back that it did not work.
Click to expand...
Click to collapse
I can confirm that you guys method totally works! I always thought the process was simple enough but was worried about downgrading after reading about hard-bricks on the forums. I downgraded to stock firmware version G900PVPU1ANE5 and applied towelroot. I then followed your instructions and I am now rooted on OA6 with a 0x0 Knox counter. System status shows custom of course so no chance of an OTA update, but this method is awesome! Thank you!
Screenshots below...
MooreAJr said:
I can confirm that you guys method totally works! I always thought the process was simple enough but was worried about downgrading after reading about hard-bricks on the forums. I downgraded to stock firmware version G900PVPU1ANE5 and applied towelroot. I then followed your instructions and I am now rooted on OA6 with a 0x0 Knox counter. System status shows custom of course so no chance of an OTA update, but this method is awesome! Thank you!
Screenshots below...
Click to expand...
Click to collapse
Nice! I will find the name of the guy that theorized this would work and give proper kudos. Thx for testing!
No problem, anytime!
Excellent!!! Props to Bryanu and you for taking the risk! Thanks so much!!!
Sprint S5 Stock 4.4.2 ROM(towelroot rootable)
Is Here: http://www.rwilco12.com/Files/Devic...)/Stock ROMs/NE5/Original TAR/SM-G900P_NE5.7z
bads3ctor said:
Is Here: http://www.rwilco12.com/Files/Devic...)/Stock ROMs/NE5/Original TAR/SM-G900P_NE5.7z
Click to expand...
Click to collapse
What does this have to do with this thead?
muniz_ri said:
What does this have to do with this thead?
Click to expand...
Click to collapse
If you are on any Stock ROM above 4.4.2 and are unrooted, the only way to get rooted and still have Knox 0x0 is to downgrade to 4.4.2, root with Towelroot, and then do your flashes.
MooreAJr said:
I can confirm that you guys method totally works! I always thought the process was simple enough but was worried about downgrading after reading about hard-bricks on the forums. I downgraded to stock firmware version G900PVPU1ANE5 and applied towelroot. I then followed your instructions and I am now rooted on OA6 with a 0x0 Knox counter. System status shows custom of course so no chance of an OTA update, but this method is awesome! Thank you!
Click to expand...
Click to collapse
You might want to put this in OP so your thread is not filled with questions about how to go from an unrooted Stock Lollipop to a Knox 0x0 rooted Stock Lollipop.
Edit: I can verify that after downgrading from Stock Lollipop to 4.4.2 using the link in my post above does indeed downgrade with Knox still 0x0 as MooreAJr has stated in his post.
I recently upgraded today from 4.4.2 to 5.0 OC4 and kept root using this method: http://forum.xda-developers.com/ver...0-keeproot-t3068546/post59791648#post59791648
However, I had no Idea it would be so hard (impossible?) to get xposed back. Is there any way in which I could install xposed ARM without having a custom recovery on my verizon G900V running lollipop?
I also read an article on another website that said you can flash safestrap with odin, go into safestrap, install anything necessary, and then reflash current ROM? I am not TOO knowledgable with all of this, however I have found my way around all this enough to ensure myself root and all needed features. Any help or information would be amazing.
Article: http://www.droidforums.net/threads/galaxy-s5-safestrap-after-the-lollipop-update.279867/
I was considering flashing the xposed ARM file with flashfire, however I read someone else was stuck in a bootloop who tried this. Would this not work? Is there any method? I was also looking into flash gordon which lets you flash .zip files without requiring custom recovery. Thanks!
EDIT: Just did some more research and found this thread: http://forum.xda-developers.com/galaxy-s4-att/general/nc1-flasher-odin-to-safestrap-t3082620
It seems as if its possible, however this thread is for the OC3 version, while I flashed the OC4... Anyone out there done anything like this before, or knows how to provide the needed steps? Thanks again.
Go to the xposed thread and read any comment at all. It doesn't work on touchwiz based lollipop architecture. PERIOD. you didn't need a new thread in this forum to learn that...
I see, is there some way that I could downgrade. I've been looking into that for awhile now to go back to my 4.4.2 but there's a ton of methods and I am not sure which is required for my device. I canno't seem to find a specific method for my g900v s5. Thanks for you're reply, and I hope I can downgrade.
synkro1 said:
I see, is there some way that I could downgrade. I've been looking into that for awhile now to go back to my 4.4.2 but there's a ton of methods and I am not sure which is required for my device. I canno't seem to find a specific method for my g900v s5. Thanks for you're reply, and I hope I can downgrade.
Click to expand...
Click to collapse
You can use this guide: http://forum.xda-developers.com/showthread.php?t=3088571 it might need some modification for 4.4.2, however.
synkro1 said:
I see, is there some way that I could downgrade.j I've been looking into that for awhile now to go back to my 4.4.2 but there's a ton of methods and I am not sure which is required for my device. I canno't seem to find a specific method for my g900v s5. Thanks for you're reply, and I hope I can downgrade.
Click to expand...
Click to collapse
You can go up and down as often as you like. I would Odin the NCG tar from the link below and reroot.
You probably still have safestrap. You could try this first. Go to download mode and Odin the NE9 kernel. When your phone starts booting up you should see the safestrap option to boot into recovery. Boot into recovery, install a rooted NE9 ROM of your choice. Boot back into download mode via safestrap and Odin the NE9 firmware. Let your phone boot all the way up and you should be good to go. Use NCG kernels and firmware-roms if you would rather be on NGC.
http://forum.xda-developers.com/ver...ment/stock-collection-kernels-modems-t2842069
If safestrap doesn't show up, Odin the full NCG tar file and reroot your phone.
Thanks so much for your help, the only problem is I never installed safestrap on my phone. So I do not currently have safe strap, or any custom recovery. So i can just use the odin method then, correct?
[PHP[/PHP]
synkro1 said:
Thanks so much for your help, the only problem is I never installed safestrap on my phone. So I do not currently have safe strap, or any custom recovery. So i can just use the odin method then, correct?
Click to expand...
Click to collapse
Yes, sir. That would be correct. Since you are rooted, there is an app called Flashfire you could use that doesn't even require a computer but if you are familiar with Odin that is a good way to go as well.
I have flashfire installed, in fact I used it to upgrade to lollipop. What settings should I use with flashfire to downgrade to lollipop? Do i have to clear cache or anything? And will the file from the notes #4 from here work?: http://forum.xda-developers.com/ver...0-keeproot-t3068546/post59791648#post59791648
synkro1 said:
I have flashfire installed, in factj I used it to upgrade to lollipop. What settings should I use with flashfire to downgrade to lollipop? Do i have to clear cache or anything? And will the file from the notes #4 from here work?: http://forum.xda-developers.com/ver...0-keeproot-t3068546/post59791648#post59791648
Click to expand...
Click to collapse
What ROM do you want to have on your phone?
Just a normal stock 4.4.2 ROM works fine for me.
synkro1 said:
Just a normal stock 4.4.2 ROM works fine for me.
Click to expand...
Click to collapse
Download this ROM onto your SD card. I prefer deodex
http://forum.xda-developers.com/showthread.php?t=2793931
Download the NGC retail firmware from here.
http://forum.xda-developers.com/ver...ment/stock-collection-kernels-modems-t2842069
In Flashfire, select firmware and navigate to your firmware. Just check boot and recovery
Next select zip-ota, navigate to your ROM. Leave auto mount unchecked.
Select firmware again. This time check boot, recovery, modem, and firmware. Flashfire will ask if you want them in separate zips. Click yes
Now select wipe. Check everything but SD card.
Now arrange everything in this order
Wipe
Firmware-boot recovery
Zip-rom
Firmware modem firmware
Firmware-boot recovery
Ever root- inject supersu
Boot normal
That should do it. You should be rooted on 4.4.2
Tulsadiver said:
Download this ROM onto your SD card. I prefer deodex
http://forum.xda-developers.com/showthread.php?t=2793931
Download the NGC retail firmware from here.
http://forum.xda-developers.com/ver...ment/stock-collection-kernels-modems-t2842069
In Flashfire, select firmware and navigate to your firmware. Just check boot and recovery
Next select zip-ota, navigate to your ROM. Leave auto mount unchecked.
Select firmware again. This time check boot, recovery, modem, and firmware. Flashfire will ask if you want them in separate zips. Click yes
Now select wipe. Check everything but SD card.
Now arrange everything in this order
Wipe
Firmware-boot recovery
Zip-rom
Firmware modem firmware
Firmware-boot recovery
Ever root- inject supersu
Boot normal
That should do it. You should be rooted on 4.4.2
Click to expand...
Click to collapse
Ur amazing. I'll try it and let you know. Thanks so much for your help.
Thanks so much! It worked perfectly! I had a problem initially after installing towelroot and xposed and got an error when rebooting the phone called "Process system isn't responding". My phone kept freezing and was super slow because of this. I believe it was due to me restoring contacts from titanium backup. I restored the contacts system app as a whole. I didn't realize that at the time however, and just system restored my phone again, and did everything the same yet didn't restore my contacts, and the message is now gone. I am not running root with xposed on 4.4.2. Your amazing!
Using Flashfire, I installed the zipped file UPDATE-SuperSU-v1.99r4.zip on my Verizon G900V, which is a towelroot rooted Lollipop. My phone ultimately rebooted, but goes no further than the initial screen. It will not fully reboot, it is not recognized via USB by my PC, it cannot be turned off except by removing the battery, and seems totally bricked. I obviously can’t even odin. I have no other data, such as build, etc., about it since it is no longer accessible. What can I do now? Any help will be most appreciated!
Everhopefull said:
Using Flashfire, I installed the zipped file UPDATE-SuperSU-v1.99r4.zip on my Verizon G900V, which is a towelroot rooted Lollipop. My phone ultimately rebooted, but goes no further than the initial screen. It will not fully reboot, it is not recognized via USB by my PC, it cannot be turned off except by removing the battery, and seems totally bricked. I obviously can’t even odin. I have no other data, such as build, etc., about it since it is no longer accessible. What can I do now? Any help will be most appreciated!
Click to expand...
Click to collapse
That is not totally bricked :victory:
You are just softbricked. First, did you have safestrap installed?
If you don't care about any of the internal data and just want the OS fixed, just put it in download mode (Power+Home+VolDown) then Vol Up to confirm, and get the .tar of the stock image. Flash it with Odin- bam done.
Be warned, because you were towelrooted this would ultimately flash the latest LOCKED bootloader- so to stay on your UNLOCKED bootloader you need to find a tar with NO bootloader (there is a PB1 no bootloader stock tar)
If you had safestrap- all you have to do is flash the NK2 kernel and it will boot into safestrap- allowing for recovery of internal data and flashing of a new ROM.
If he's on any of the Firmwares below OD5, he can safely Odin back to NCG and start from scratch using Towelroot. All of our bootloaders are locked no matter which firmware version you're on. It's the versions OE1 and up that are more locked down from rooting
smokerbond said:
That is not totally bricked :victory:
You are just softbricked. First, did you have safestrap installed?
If you don't care about any of the internal data and just want the OS fixed, just put it in download mode (Power+Home+VolDown) then Vol Up to confirm, and get the .tar of the stock image. Flash it with Odin- bam done.
Be warned, because you were towelrooted this would ultimately flash the latest LOCKED bootloader- so to stay on your UNLOCKED bootloader you need to find a tar with NO bootloader (there is a PB1 no bootloader stock tar)
If you had safestrap- all you have to do is flash the NK2 kernel and it will boot into safestrap- allowing for recovery of internal data and flashing of a new ROM.
Click to expand...
Click to collapse
Many thanks, Smokerbond. I do wish I had waited for your reply, but, as usual, I was impatient (and somewhat concerned). I found part of what you knew elsewhere, downloaded from Sammobile, and flashed. Unfortunately, as you noted, that didn’t keep root. My question now is, can I start over? I flashed G900VVRU1BOA8-G900VVZW1BOA8 which, of course, is filled with bloatware. I have all my files I used originally, but no instructions and, as we say at my age, (77), I have slept since then.
You can Odin flash the PB1.tar with no bootloader, then use @jrkruse root method. That is the simplest way. You can also Odin back to NCG and use Towelroot, but it makes it a PITA with enabling advanced calling.
---------- Post added at 01:14 PM ---------- Previous post was at 01:13 PM ----------
Also, I'm not familiar with that SuperSU version. That is probably what caused the bootloop. I'm currently running SuperSU 2.71 on my S5 and it works great, but you can go with the latest stable version if you prefer.
Shouldn't be trying to flash SuperSU from 2014. Here's the latest version once you get everything up and running again.
Thanks for all the suggestions. I am now up and running, using Chainfire's SU 2.65. Since I was familiar with the path, I did go back to NCG and use towelroot, but since I have no need for the advanced calling (with which I was not familiar), I am happy with my setup.