Hi everyone. Not sure anyone will be able to help me, but I figured I'd chance it. I also hope that I'm asking this in the right area. If not I apologize. So I got a Note 3 (AT&T) today. IN LOVE! After doing some reading I used Kingo to root. Everything went great and my phone is now rooted. To confirm this I downloaded root checker from the play store and it confirmed that my phone is definitely rooted.
After some more research I came across safestrap. For the last 2-3 hours I have been trying to install it with zero luck. Basically, after I download the 3.71 apk, installed the apk, followed the prompts and completed the installation safestrap says that the installation was complete. Unfortunately, the state: still shows not installed and I am unable to choose reboot to recovery. It's greyed out and can't be selected. Any chance that anyone knows why this is happening? I have tried just about everything that I can think of and the result has been the same every time. Sorry so long, but this is driving me crazy and I wanted to be thorough with my explanation. Thanks in advance for any help or fixes that you come up with.
thynis said:
Hi everyone. Not sure anyone will be able to help me, but I figured I'd chance it. I also hope that I'm asking this in the right area. If not I apologize. So I got a Note 3 (AT&T) today. IN LOVE! After doing some reading I used Kingo to root. Everything went great and my phone is now rooted. To confirm this I downloaded root checker from the play store and it confirmed that my phone is definitely rooted.
After some more research I came across safestrap. For the last 2-3 hours I have been trying to install it with zero luck. Basically, after I download the 3.71 apk, installed the apk, followed the prompts and completed the installation safestrap says that the installation was complete. Unfortunately, the state: still shows not installed and I am unable to choose reboot to recovery. It's greyed out and can't be selected. Any chance that anyone knows why this is happening? I have tried just about everything that I can think of and the result has been the same every time. Sorry so long, but this is driving me crazy and I wanted to be thorough with my explanation. Thanks in advance for any help or fixes that you come up with.
Click to expand...
Click to collapse
click on safestrap in your app drawer then click install recovery
Vsideo of the issue.
jerrycoffman45 said:
click on safestrap in your app drawer then click install recovery
Click to expand...
Click to collapse
I made a screen recording of what's going on. Not sure sure why I didn't I didn't do this earlier.
youtu.be/FkuiYcFFk2E
thynis said:
I made a screen recording of what's going on. Not sure sure why I didn't I didn't do this earlier.
youtu.be/FkuiYcFFk2E
Click to expand...
Click to collapse
try disabling lookout first
Same result.
Uninstalled Safestrap, Disabled and turned off lookout, and rebooted. After reboot I reinstalled safestrap and tried again. The result was the same. No install and not reboot to recovery after a supposed successful install. Would re-rooting possibly make a difference?
thynis said:
Uninstalled Safestrap, Disabled and turned off lookout, and rebooted. After reboot I reinstalled safestrap and tried again. The result was the same. No install and not reboot to recovery after a supposed successful install. Would re-rooting possibly make a difference?
Click to expand...
Click to collapse
it could lookout has been known to cause problems for kingo try unrooting and start over
Unroot, Re-root, Retry
jerrycoffman45 said:
it could lookout has been known to cause problems for kingo try unrooting and start over
Click to expand...
Click to collapse
So I unrooted using Kingo, re-rooted, reinstalled safestrap, and it is still a no go. Still the same result as the video above. Now I really don't know what to do.
I am at a loss
Sent from my SM-N9005 using Tapatalk
jerrycoffman45 said:
I am at a loss
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
Let me go ahead and make it weirder. I just rooted AND installed safestrap on my wife's note 3. It worked perfectly and without any problems. The only difference between our phones, that I'm aware of, is the color. She has white and I have black.
The model number, Android version, baseband version, kernel, and build number are all the same. I would be lying if I said that it isn't making me want to cry.
Mines black and no problems
Sent from my SM-N9005 using Tapatalk
jerrycoffman45 said:
Mines black and no problems
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
I'm doing a complete erase of the device now. After it's finish going to root and then *HOPEFULLY* safestrap.
thynis said:
I'm doing a complete erase of the device now. After it's finish going to root and then *HOPEFULLY* safestrap.
Click to expand...
Click to collapse
And now it seems to be stuck at the AT&T loading screen....
I can't win today.
thynis said:
And now it seems to be stuck at the AT&T loading screen....
I can't win today.
Click to expand...
Click to collapse
I booted into Odin, wiped data & caches, rebooted, installed nova launcher, rooted the phone, checked to see if it was rooted (it was), rebooted, installed safestrap.apk, opened safestrap and installed, and..... same thing..... I am now completely out of ideas. It would seem like I am destined to have no custom rom installations.
Maybe a bad download of safestrap other than that I am out of ideas
Sent from my SM-N9005 using Tapatalk
jerrycoffman45 said:
Maybe a bad download of safestrap other than that I am out of ideas
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
I actually used the same download that I used on my wife's. I also downloaded earlier versions of safestrap and tried them. Much like you I am out of ideas. Is it possible to use something other then safestrap? Maybe clockwork mod and then install roms manually like I do for my nexus 7? Or is safestrap the only only option due to Knox? Also, Thank you for the help. If for some reason
I stumble upon an answer I'll let you and others know. Pretty clueless at this point though. Thanks again.
jerrycoffman45 said:
Maybe a bad download of safestrap other than that I am out of ideas
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
I actually used the same download that I used on my wife's. I also downloaded earlier versions of safestrap and tried them. Much like you I am out of ideas. Is it possible to use something other then safestrap? Maybe clockwork mod and then install roms manually like I do for my nexus 7? Or is safestrap the only only option due to Knox? Also, Thank you for the help. If for some reason
I stumble upon an answer I'll let you and others know. Pretty clueless at this point though. Thanks again.
dude, my wife just got a black N3. this is not very encouraging.
good luck, hope you get it working.
It is the only way because of the locked bootloader there is a way with Odin but it is only one rom Knox raid kit kat version
Sent from my SM-N9005 using Tapatalk
smokarz said:
dude, my wife just got a black N3. this is not very encouraging.
good luck, hope you get it working.
Click to expand...
Click to collapse
I wouldn't be concerned. Whatever it is it seems that it's only my phone. I'm 99.9% positive that it has nothing to do with the color or with the black note being different.
jerrycoffman45 said:
It is the only way because of the locked bootloader there is a way with Odin but it is only one rom Knox raid kit kat version
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
That's what I figured. No biggie though. I am pretty satisfied with root and xposed framework. I've managed to delete and/or disable most of the apps that I don't use our want. I'll try to figure it out again if/when a new version of safestrap is released. Granted, I really don't think that it'll make a difference. My phone seems to have a grudge against safestrap. Oh well. Thanks again!
Related
I don't know why this is happening when trying to install apps..Some install fine but most like this XDA Premium app does not install..Any ideas?
EDIT: Just for giggles i tried installing the free version of xda and it installs but when the paid version is attempted to install i get the could not install message
BrianBaker said:
I don't know why this is happening when trying to install apps..Some install fine but most like this XDA Premium app does not install..Any ideas?
EDIT: Just for giggles i tried installing the free version of xda and it installs but when the paid version is attempted to install i get the could not install message
Click to expand...
Click to collapse
Do you have one of the odex/deodex roms or viperrom installed? thats your issue.
youkosnake said:
Do you have one of the odex/deodex roms or viperrom installed? thats your issue.
Click to expand...
Click to collapse
I think its more to do with the root method but either way im in need of the stock ruu
BrianBaker said:
I think its more to do with the root method but either way im in need of the stock ruu
Click to expand...
Click to collapse
There is no stock RUU released yet. and my One has root and works fine, so I don't think it can be the root method.
youkosnake said:
There is no stock RUU released yet. and my One has root and works fine, so I don't think it can be the root method.
Click to expand...
Click to collapse
well..im screwed since it seems during wiping..Ive lost my nandroid back up..
Anyone happen to have a nandroid with out all user data entered yet? Hell i don't even know if that would work
BrianBaker said:
well..im screwed since it seems during wiping..Ive lost my nandroid back up..
Anyone happen to have a nandroid with out all user data entered yet? Hell i don't even know if that would work
Click to expand...
Click to collapse
I'd say just use one of the roms, sideload apps you use daily and wait it out. nandroiding to a different device is bad news, my friend.
I also am having the same issue with not being able to install to sdcard, you're not alone.
Onyoursix said:
I also am having the same issue with not being able to install to sdcard, you're not alone.
Click to expand...
Click to collapse
Same here. Luckily my TiBackup seems to be installing everything fine, just have to wait out a fix and sideload in the meantime.
Edited... Always read the entire ROM thread before posting... quick fix is listed in there.
I've been having the problem since I installed ViperROM last night. Viper is working on finding a fix. For now, I copied my TiBu files over from my Evo LTE and restored them that way.
Same problem
Running viper
I purchased the AT&T version of the Galaxy Note 3 a little less than a week ago and, to be honest, I'm not really keen on it. There are a number of reasons, but what it boils down to is that I just don't think I like it all that much. I've already sold my Galaxy Note 2, so I'll have to figure out what I'm going to do about a cell phone, but that's something beyond the scope of this particular posting. What I need help with is how to unroot this device. I used the Root De La Vega procedure very shortly after it came out and it worked like a charm. I noted that when the phone boots up, there is the word "Custom" and an unlocked padlock. How do I get this AT&T model of the Galaxy Note 3 back to the condition, more or less, of when I bought it about a week ago so that I won't have any issues getting the refund processed? I've heard some people requesting help with unrooting and they've been told to use the unroot in SuperUser. Will this get rid of the "Custom" wording on boot-up AND the unlocked padlock? If not, is there a way to get this back to the way it was or am I just out of luck since I only have about another week to return this device. Obviously, if I'm stuck, I'm stuck and I'll find a way to live with it. Who knows...I might actually get to liking it down the road when some of the quirks have been worked out. However, if there's a way to sort all of this out in a timely manner where there's no muss or fuss, that would be the ideal solution. Any help would be greatly appreciated.
KennyXL said:
I purchased the AT&T version of the Galaxy Note 3 a little less than a week ago and, to be honest, I'm not really keen on it. There are a number of reasons, but what it boils down to is that I just don't think I like it all that much. I've already sold my Galaxy Note 2, so I'll have to figure out what I'm going to do about a cell phone, but that's something beyond the scope of this particular posting. What I need help with is how to unroot this device. I used the Root De La Vega procedure very shortly after it came out and it worked like a charm. I noted that when the phone boots up, there is the word "Custom" and an unlocked padlock. How do I get this AT&T model of the Galaxy Note 3 back to the condition, more or less, of when I bought it about a week ago so that I won't have any issues getting the refund processed? I've heard some people requesting help with unrooting and they've been told to use the unroot in SuperUser. Will this get rid of the "Custom" wording on boot-up AND the unlocked padlock? If not, is there a way to get this back to the way it was or am I just out of luck since I only have about another week to return this device. Obviously, if I'm stuck, I'm stuck and I'll find a way to live with it. Who knows...I might actually get to liking it down the road when some of the quirks have been worked out. However, if there's a way to sort all of this out in a timely manner where there's no muss or fuss, that would be the ideal solution. Any help would be greatly appreciated.
Click to expand...
Click to collapse
I'm not super familiar with the unrooting process, but try to unroot using SuperSU and reboot a couple of times to see if it goes away. If that doesn't work then flash the original firmware with odin and that should do it. Pretty easy to do from what I understand.
agent929 said:
I'm not super familiar with the unrooting process, but try to unroot using SuperSU and reboot a couple of times to see if it goes away. If that doesn't work then flash the original firmware with odin and that should do it. Pretty easy to do from what I understand.
Click to expand...
Click to collapse
Perhaps this is showing my ignorance, but since the AT&T Galaxy Note 3 has a locked bootloader (which, as of yet, has not been unlocked), would that prevent Odin from flashing a new image? If I don't need an unlocked bootloader to flash with Odin, do you know where I might find the original image that came with my phone from AT&T in a format that Odin can flash? I haven't tried the SuperSU yet since I want all my options readily available so that if one fails, I can move on to the next one.
KennyXL said:
Perhaps this is showing my ignorance, but since the AT&T Galaxy Note 3 has a locked bootloader (which, as of yet, has not been unlocked), would that prevent Odin from flashing a new image? If I don't need an unlocked bootloader to flash with Odin, do you know where I might find the original image that came with my phone from AT&T in a format that Odin can flash? I haven't tried the SuperSU yet since I want all my options readily available so that if one fails, I can move on to the next one.
Click to expand...
Click to collapse
To my understanding you can flash anything with Odin on a locked bootloader phone that is "signed". If you give me a few minutes I'll help you look for the original odin file to flash.
agent929 said:
I'm not super familiar with the unrooting process, but try to unroot using SuperSU and reboot a couple of times to see if it goes away. If that doesn't work then flash the original firmware with odin and that should do it. Pretty easy to do from what I understand.
Click to expand...
Click to collapse
agent929 said:
To my understanding you can flash anything with Odin on a locked bootloader phone that is "signed". If you give me a few minutes I'll help you look for the original odin file to flash.
Click to expand...
Click to collapse
I really appreciate your help. Every time I've used Odin in the past has involved a phone with a non-locked bootloader (as far as I know) so this is new territory for me.
KennyXL said:
I really appreciate your help. Every time I've used Odin in the past has involved a phone with a non-locked bootloader (as far as I know) so this is new territory for me.
Click to expand...
Click to collapse
Not a problem. I've been looking for that odin file with no luck. I would PM designgears and ask him if he can provide a link for it because you couldn't find it.
agent929 said:
Not a problem. I've been looking for that odin file with no luck. I would PM designgears and ask him if he can provide a link for it because you couldn't find it.
Click to expand...
Click to collapse
Thanks. I'll give that a try.
Use the same file that u used to root. The one with the one click. After it pass, you're back to stock. i just did it yesterday.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
If you looked at the root thread you'd see directions to unroot right there.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
panday74 said:
Use the same file that u used to root. The one with the one click. After it pass, you're back to stock. i just did it yesterday.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Zach Alt said:
If you looked at the root thread you'd see directions to unroot right there.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
What they said
Sent from my SAMSUNG-SGH-I467 using Tapatalk 4
panday74 said:
Use the same file that u used to root. The one with the one click. After it pass, you're back to stock. i just did it yesterday.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried the SuperSU full unroot method - didn't remove the padlock, flashed the one click - didn't remove it, and just flashed the second (for funsies) and that didn't help (probably shouldn't have expected it to).
I'm returning my note and can't get rid of the lock. Will PM Designgears I guess
Did you restart it a few times? Also a factory reset?
Sent from my SAMSUNG-SM-N900A using Tapatalk 5
seanu13 said:
I tried the SuperSU full unroot method - didn't remove the padlock, flashed the one click - didn't remove it, and just flashed the second (for funsies) and that didn't help (probably shouldn't have expected it to).
I'm returning my note and can't get rid of the lock. Will PM Designgears I guess
Click to expand...
Click to collapse
I was kinda wondering how to remove the padlock also. I have read that some people that haven't even rooted have the padlock on boot up also??? I read somewhere about triangle away working, have you tried that?
agent929 said:
Did you restart it a few times? Also a factory reset?
Sent from my SAMSUNG-SM-N900A using Tapatalk 5
Click to expand...
Click to collapse
yes to both (restarted 5 times). since i was already so far into the root process, I added the files to the sdcards that are in the root steps, and the lock went away. Then I finished rooting.
went back and did one click again and still had the lock after rebooting 5 times. Thought about how it went away after adding the files so I skipped through the phone setup, enabled USB debugging again and added a dummy file to the sd card (a .csv I had on my desktop) and then removed it. Rebooted, and the lock was gone.
I'd use the padlock hack in Wanum and hide the root apps via Nova Launcher just to stick it to ATT and return it rooted.
Sent from my SAMSUNG-SM-N900A using xda premium
Omg, just reflash the stock rom from the package. Says so in the instructions.
READ!
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Jammol said:
Omg, just reflash the stock rom from the package. Says so in the instructions.
READ!
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you READ, you will see he already did that.
agent929 said:
If you READ, you will see he already did that.
Click to expand...
Click to collapse
The last post that was here when I posted was yours. That's why I posted for him to Read the instructions.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Ok well here's what I did and the padlock is gone.
Factory reset on the phone
Phone rebooted and I removed the super su app using the setting in the su app.
Then flashed the one click 9 tar
phone reboots on its own after flashing, icon was still there
rebooted the phone twice and the padlock was gone
Not sure if I just got lucky or what lol
Jammol said:
The last post that was here when I posted was yours. That's why I posted for him to Read the instructions.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Got ya..tapatalk has been mean to me too lol
---------- Post added at 10:26 AM ---------- Previous post was at 10:25 AM ----------
Quickvic30 said:
Ok well here's what I did and the padlock is gone.
Factory reset on the phone
Phone rebooted and I removed the super su app using the setting in the su app.
Then flashed the one click 9 tar
phone reboots on its own after flashing, icon was still there
rebooted the phone twice and the padlock was gone
Not sure if I just got lucky or what lol
Click to expand...
Click to collapse
I know you have to reboot a few times to set the status somehow, iB4STiD explained it in one of his post before.
OK so I have this great ATT note 3. I have it rooted (mj5). I haven't done much with it because as far as I know I can't get a custom recovery yet Correct??
I am having issues with a few things and I'm a little concerned with the phone. For 1 I have a hard time starting up my phone some times. It seems to keep restarting and I have to keep taking the battery out and it will work after a few times. 2nd the volume sometimes gets messed up with things I do.
I've been rooting for maybe close to 1 year now and by no means a expert here but I've never failed doing it.
So here is my question, I would like to know if there is anything I can do now to get a custom recovery now that some time has gone by. I see a lot of things going on but it's all things I've never seen or read about before. I'm just looking to get pointed in the right direction from the point I'm at right blessed which is rooted with Mj5.
Or do I unroot and if so how?
also any of these options am I going to lose everything on my phone? Any help is greatly appreciated.
Thanks!!
Sent from my SAMSUNG-SM-N900A using XDA Premium HD app
Look at the safestrap thread. It is our version of recovery for locked bootloaders
Sent from my SM-N900V using XDA Premium 4 mobile app
itmaster85 said:
Look at the safestrap thread. It is our version of recovery for locked bootloaders
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Would you be able to send me a link to the one your using? I just want to make sure I'm looking on the right thread.
Sent from my SAMSUNG-SM-N900A using XDA Premium HD app
enzosly said:
Would you be able to send me a link to the one your using? I just want to make sure I'm looking on the right thread.
Sent from my SAMSUNG-SM-N900A using XDA Premium HD app
Click to expand...
Click to collapse
At the top of this page if you just click where it says AT&T Samsung Galaxy Note 3 you will see all our sections. Click on the Android Development link then search around there for safestrap by hashcode.
enzosly said:
OK so I have this great ATT note 3. I have it rooted (mj5). I haven't done much with it because as far as I know I can't get a custom recovery yet Correct??
I am having issues with a few things and I'm a little concerned with the phone. For 1 I have a hard time starting up my phone some times. It seems to keep restarting and I have to keep taking the battery out and it will work after a few times. 2nd the volume sometimes gets messed up with things I do.
I've been rooting for maybe close to 1 year now and by no means a expert here but I've never failed doing it.
So here is my question, I would like to know if there is anything I can do now to get a custom recovery now that some time has gone by. I see a lot of things going on but it's all things I've never seen or read about before. I'm just looking to get pointed in the right direction from the point I'm at right blessed which is rooted with Mj5.
Or do I unroot and if so how?
also any of these options am I going to lose everything on my phone? Any help is greatly appreciated.
Thanks!!
Sent from my SAMSUNG-SM-N900A using XDA Premium HD app
Click to expand...
Click to collapse
I had rooted myself on SM-N900A on MJ5 using Kingo and also used kingo to unroot too. No issues / No Knox tripping.
Rooting
So I have the ATT N900A and have tried rooting it or at least looked into it so far but when the forums say only certain version available I never find one that actually says N900A. I have seen others, but to be honest I am freshly new to all of this and I am learning it all slowly but surely. Can I get some help any one?
enzosly said:
OK so I have this great ATT note 3. I have it rooted (mj5). I haven't done much with it because as far as I know I can't get a custom recovery yet Correct??
I am having issues with a few things and I'm a little concerned with the phone. For 1 I have a hard time starting up my phone some times. It seems to keep restarting and I have to keep taking the battery out and it will work after a few times. 2nd the volume sometimes gets messed up with things I do.
I've been rooting for maybe close to 1 year now and by no means a expert here but I've never failed doing it.
So here is my question, I would like to know if there is anything I can do now to get a custom recovery now that some time has gone by. I see a lot of things going on but it's all things I've never seen or read about before. I'm just looking to get pointed in the right direction from the point I'm at right blessed which is rooted with Mj5.
Or do I unroot and if so how?
also any of these options am I going to lose everything on my phone? Any help is greatly appreciated.
Click to expand...
Click to collapse
Those are not normal issues to have on your phone, and I don't think they are related to the rooting; I think they are indicative of larger issues with the phone. I would unroot it so it looks stock, and assuming the problems persist, take it back to AT&T.
If unrooting fixes it, ofc, reroot and do it right this time (I don't know what method you used, or what might have gone wrong)
Do that BEFORE messing around with our poor-substitute for a custom recovery (safestrap) and custom ROM's.
DrAzzy said:
Those are not normal issues to have on your phone, and I don't think they are related to the rooting; I think they are indicative of larger issues with the phone. I would unroot it so it looks stock, and assuming the problems persist, take it back to AT&T.
If unrooting fixes it, ofc, reroot and do it right this time (I don't know what method you used, or what might have gone wrong)
Do that BEFORE messing around with our poor-substitute for a custom recovery (safestrap) and custom ROM's.
Click to expand...
Click to collapse
Well its funny because I did root my phone using the Vega root files but lol I just looked last night and I'm not rooted anymore... Maybe I took a update with out realizing it?? Ok so now that I'm not rooted what do I do?
If I just do a restart from stock what thread should I look at?
Or do I root again using the kingo .com thing? Wow I'm so lost with this phone. I have the s4 HTC one, nexus 5 and never have had these issues. Just when I start to think I'm getting g good at this
Sent from my Nexus 5 using XDA Premium HD app
enzosly said:
Well its funny because I did root my phone using the Vega root files but lol I just looked last night and I'm not rooted anymore... Maybe I took a update with out realizing it?? Ok so now that I'm not rooted what do I do?
If I just do a restart from stock what thread should I look at?
Or do I root again using the kingo .com thing? Wow I'm so lost with this phone. I have the s4 HTC one, nexus 5 and never have had these issues. Just when I start to think I'm getting g good at this
Sent from my Nexus 5 using XDA Premium HD app
Click to expand...
Click to collapse
Sigh - always, first thing after rooting, always freeze OTA updates, and wait to upgrade before people here say it works and there's a root available!
Since you're having suspicious issues, I would want to put on clean MJ5 firmware before continuing - get the system into a known state before continuing.
http://forum.xda-developers.com/showthread.php?t=2559715
This will erase everything on your phone.
I would hold off on rooting and first check if the issues you mentioned in the OP are fixed, and if they are, then you can chalk it up to a software problem (pin the blame on the OTA update), and follow the instructions in that thread to get root.
DrAzzy said:
Sigh - always, first thing after rooting, always freeze OTA updates, and wait to upgrade before people here say it works and there's a root available!
Since you're having suspicious issues, I would want to put on clean MJ5 firmware before continuing - get the system into a known state before continuing.
http://forum.xda-developers.com/showthread.php?t=2559715
This will erase everything on your phone.
I would hold off on rooting and first check if the issues you mentioned in the OP are fixed, and if they are, then you can chalk it up to a software problem (pin the blame on the OTA update), and follow the instructions in that thread to get root.
Click to expand...
Click to collapse
That's what I will do.
Sent from my Nexus 5 using XDA Premium HD app
Kind of stuck here.
I have VZW developer edition. Rooted, 4.4 with TWRP
Foolishly I accepted the OTA update to 4.4.2, this failed of course but now my phone is constantly rebooting. It stays up for a few minutes then powers back to recovery.
Help !!!
Thanks.
Its a Dev phone just fxz and re-root
Sent from my XT1080 using xda app-developers app
bigv5150 said:
Its a Dev phone just fxz and re-root
Sent from my XT1080 using xda app-developers app
Click to expand...
Click to collapse
If only I had a clue what that meant
homemadehitshow said:
Kind of stuck here.
I have VZW developer edition. Rooted, 4.4 with TWRP
Foolishly I accepted the OTA update to 4.4.2, this failed of course but now my phone is constantly rebooting. It stays up for a few minutes then powers back to recovery.
Help !!!
Thanks.
Click to expand...
Click to collapse
Can you get into the bootloader (hold power + volume down)? If so, you'll probably need to reflash the stock recovery before the update will install.
Thanks, after I stopped panicking and calmed down I was able to flash Stock Recovery and then the next reboot caused the standard update to work. Kind of surprised really, still rooted etc.
Right now phone is working but Wi-Fi indicator is not lit, even though it is using the wi-fi.
Clear cache and dalvik cache?
Sent from my XT1060 using Tapatalk
homemadehitshow said:
Thanks, after I stopped panicking and calmed down I was able to flash Stock Recovery and then the next reboot caused the standard update to work. Kind of surprised really, still rooted etc.
Right now phone is working but Wi-Fi indicator is not lit, even though it is using the wi-fi.
Click to expand...
Click to collapse
Well you have the dev edition, they aren't going to take root from you. Don't know what's up with your wifi, though. When I updated I ended up having to restore a backup and updating again because of several extremely strange problems.
homemadehitshow said:
Thanks, after I stopped panicking and calmed down I was able to flash Stock Recovery and then the next reboot caused the standard update to work. Kind of surprised really, still rooted etc.
Right now phone is working but Wi-Fi indicator is not lit, even though it is using the wi-fi.
Click to expand...
Click to collapse
Disable WiFi and turn it back on right after.
Sent from my Moto X DE
Yep, everything seems to be working again now.
I have blindly followed instructions for flashing etc. using Fasboot but I think I'm finally getting a better feel for what is going on with it.
homemadehitshow said:
Yep, everything seems to be working again now.
I have blindly followed instructions for flashing etc. using Fasboot but I think I'm finally getting a better feel for what is going on with it.
Click to expand...
Click to collapse
Good job taking some initiative. Not as difficult as you thought it'd be right?
the verizon 4.4.2 SBF file is out so any issues anyone is having they can just flash the whole SBF file and be complety stock 4.4.2
enjoy
http://sbf.droid-developers.org/download.php?device=0&file=841
hey guys i tried searching for answers. but had no success. i have a note 3 that was rooted with kingo. AT&T automatically installed an OTA update and of course it un rooted my phone. i still get the custom boot screen as well as still have safestrap on my device. my question is how do i reroot my device? ive tried kingo again and it fails after rebootong the phone 5 or 6 times. im still running 4.3 build is JSS15J.N900AUCUBNB4
i know a little on some things but im not as technical as most of you. but any help would be greatly appreciated.
Survivor058 said:
hey guys i tried searching for answers. but had no success. i have a note 3 that was rooted with kingo. AT&T automatically installed an OTA update and of course it un rooted my phone. i still get the custom boot screen as well as still have safestrap on my device. my question is how do i reroot my device? ive tried kingo again and it fails after rebootong the phone 5 or 6 times. im still running 4.3 build is JSS15J.N900AUCUBNB4
i know a little on some things but im not as technical as most of you. but any help would be greatly appreciated.
Click to expand...
Click to collapse
What version of Kingo did you try? Use 1.1.5 or 1.1.8. People have had success with that. 1.1.8 worked for me. Just Google around and you will find the download on the net somewhere.
theorioles33 said:
What version of Kingo did you try? Use 1.1.5 or 1.1.8. People have had success with that. 1.1.8 worked for me. Just Google around and you will find the download on the net somewhere.
Click to expand...
Click to collapse
it was 1.2.0 ill try an older version
In case you have trouble finding a copy
https://mega.co.nz/#!AxdHUCCQ!86DzctSWlXK4VfbInPYBgC_4QYAM2wUR8cewrflAyk0
theorioles33 said:
In case you have trouble finding a copy
unfortunately that did not work. the root failed. that was version 1.1.5, last night i tried 1.1.8 failed and tried the latest 1.2.0 with no success. would you recommend something else? i did try theese root methods with the sd card inserted im not sure if that is a no no or not
Click to expand...
Click to collapse
I'm at a loss. I had my SD card in by the way. Maybe someone else will have some ideas.
Sent from my SAMSUNG-SM-N900A using Tapatalk
theorioles33 said:
I'm at a loss. I had my SD card in by the way. Maybe someone else will have some ideas.
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
that sucks. factory reset? ill most likely still have the issue but maybe not. isnt there a way to completely wipe the phone from the boot screen? id rather not if i dont have to.
You can try a factory reset and then root. If not there is a thread in the general section to go back to stock. Works great. I used it.
Sent from my SAMSUNG-SM-N900A using Tapatalk
theorioles33 said:
You can try a factory reset and then root. If not there is a thread in the general section to go back to stock. Works great. I used it.
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
but arent i technically back to stock? since i dont have root access? this is very confusing to me. if my carrier didnt push that update i wouldnt be in this boat
You are but we can't figure out why you can't root when others in your situation can. There is Kingo thread you can check out. Maybe you can find some answers there.
Sent from my SAMSUNG-SM-N900A using Tapatalk
anyone have any suggestions?? 139 views in less than an hour someone has got to know something lol
Survivor058 said:
anyone have any suggestions?? 139 views in less than an hour someone has got to know something lol
Click to expand...
Click to collapse
Factory Reset after the update to NB4, also go to recovery wipe cache, then try the 1.18, during the rooting process, look your phone screen, you need to click accept something twice,
I don't know how it all works terribly well but you said you still have Safestrap? Can you still install ROMs and can they have root?
Also, for when you eventually do get it working again. I recommend freezing the ATT updater. It can be awful when it eventually FORCES an update.
I got a free app called App Quarantine and froze "AT&T Software Update".
coolmingli said:
Factory Reset after the update to NB4, also go to recovery wipe cache, then try the 1.18, during the rooting process, look your phone screen, you need to click accept something twice,
Click to expand...
Click to collapse
ok yea this is all french to me. you want me to factory reset? im not sure what the NB4 is?. and i thing i know how to wipe the cache.
Gary3 said:
I don't know how it all works terribly well but you said you still have Safestrap? Can you still install ROMs and can they have root?
Also, for when you eventually do get it working again. I recommend freezing the ATT updater. It can be awful when it eventually FORCES an update.
I got a free app called App Quarantine and froze "AT&T Software Update".
Click to expand...
Click to collapse
safestrap is on my phone but it cant be removed and just says that the phone isnt properly rooted. so no i cannot install roms and i will make sure that once i resolve this ill freezr that app
sorry for the delay guys im back at this again. i do very much appreciate all who are trying to offer assistance
ok guys so ive wiped the cache. and have done the factory reset. kingo 1.1.5 and 1.1.8 both have failed...... what is going on here maybe someone can skype with me the steps to completely flash my phone to the day i got it i see the thread but im scared ****less to try it lol
You will just have to follow the restore to MJ5 thread. The instructions are simple and very easy to follow. Go slow and follow them to the T.
What they do not mention however is do not use a 3.0 USB port. Only 2.0 will work.
Just follow that.
It is literally impossible to brick this phone to the point of it being unrecoverable. There is a tutorial to restore from hard bricks without J-Tag.
Sent from my SM-N9005A using XDA Premium 4 mobile app
graydiggy said:
You will just have to follow the restore to MJ5 thread. The instructions are simple and very easy to follow. Go slow and follow them to the T.
What they do not mention however is do not use a 3.0 USB port. Only 2.0 will work.
Just follow that.
It is literally impossible to brick this phone to the point of it being unrecoverable. There is a tutorial to restore from hard bricks without J-Tag.
Sent from my SM-N9005A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hey graydiggy, I did the restore back to MJ5, but can't seem to get the last step for rooting to work. I tried every way with putting the rdlv on internal...unzipped and zipped. I even tried doing the same on the external sd as well. When I reboot supersu doesn't do anything. Any suggestion on how to get the last step to work?
Thanks in advance for your help.
chrispyutec said:
Hey graydiggy, I did the restore back to MJ5, but can't seem to get the last step for rooting to work. I tried every way with putting the rdlv on internal...unzipped and zipped. I even tried doing the same on the external sd as well. When I reboot supersu doesn't do anything. Any suggestion on how to get the last step to work?
Thanks in advance for your help.
Click to expand...
Click to collapse
It has to be unzipped and on the internal. You have to reboot a few times for it to activate. After the first reboot, let the phone sit for a few minutes and then reboot again. You should be good to go after that.
Sent from my SM-N9005A using XDA Premium 4 mobile app
graydiggy said:
It has to be unzipped and on the internal. You have to reboot a few times for it to activate. After the first reboot, let the phone sit for a few minutes and then reboot again. You should be good to go after that.
Sent from my SM-N9005A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Wow that did the trick!!! Thanks for holding my hand lol. I hit your thanks and I appreciate your help.