SOLVED: Root Issue - AT&T Galaxy Note 3 Q&A, Help & Troubleshooting

I tried to reset to factory from within the device but its still broken. Please help!
SOLVED:
For other that might have similar problems, what I did NOT do was do the OneClick.exe step. The directions made it seem like we could choose to do method 1 OR method 2. So I skipped the oneclick and went straight to .tar step which for me at least broke the wifi. When followed both methods together it worked.
Thanks!

It'd be a good idea to change the title of this thread to something less slanderous. You're not sure why your wifi stopped working, and the title comes across as blaming the dev of root de la vega to me. Perhaps something along the lines of "Wifi stopped working after rooting" would be more appropriate.

i downgraded via DG's leaked firmware and it actually fixed a few things believe it or not and i dont even get that your wifi is unstable message anymore.
try re downloading the files maybe you got a bad download. then reflash

WIFI works for me after root. Even WIFI tethering works with FoxFi.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app

I agree I have never seen root break wifi I don't think designgears would have released it. I've used his work for years and yet to have any major complaints
Sent from my SAMSUNG-SM-N900A using Tapatalk 4

User error.

JoJo2211 said:
I tried to reset to factory from within the device but its still broken. Please help!
Click to expand...
Click to collapse
Like others have said I would definitely change that title. You probably broke your own Wifi by not checking MD5's or not following instructions.
Sent from my SAMSUNG-SM-N900A using Tapatalk 5

JoJo2211 said:
I tried to reset to factory from within the device but its still broken. Please help!
Click to expand...
Click to collapse
With your current title the way it is your likely to get little to no help around here...
It clearly says "Flash at your own risk!"
"You" seem to be the only one with WiFi Issues, so what is it that "you" are doing wrong?

He skipped the one click Odin step in the instructions which is why his wifi is not working. He was still on ml9 and didn't downgrade to ml1.
Sent from my SAMSUNG-SM-N900A using Tapatalk 4

Oh so it wasn't the De La vega root that broke your wifi, it was you then. I don't think just adding solved to the title changes the fact that you accused the rooting method of the phone for your wifi issue. I think you should take that out of the title to show a little respect to the guy (DG) who busted his a$$ to get us root.
Sent from my SAMSUNG-SM-N900A using xda app-developers app

Sam3gX said:
He skipped the one click Odin step in the instructions which is why his wifi is not working. He was still on ml9 and didn't downgrade to ml1.
Sent from my SAMSUNG-SM-N900A using Tapatalk 4
Click to expand...
Click to collapse
agent929 said:
Like others have said I would definitely change that title. You probably broke your own Wifi by not checking MD5's or not following instructions.
Sent from my SAMSUNG-SM-N900A using Tapatalk 5
Click to expand...
Click to collapse
Hi Guys,
Can you please advice where I might have gone wrong? My wifi is not working.
My device is flashed with the below CSC, CP and AP:
CSC - N9005OXABMI6_CSC.tar.md5
CP: N9005XXUBMI6
AP - N9005XXUBMI7_VEGA
Does these combination of CSC and AP looks correct?
I have not tripped my KNOX flags. Rooted using de la vega method.
Thanks in advance

Related

[Q] Help with unroot and removing "Custom" and unlocked padlock

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.

Has anyone else gotten this while rooting?

Hey guys. I ran into some trouble trying to root my note 3 and got this message. Now the phone won't turn on our connect to kies to try to repair it. I have the Samsung drivers installed and I believe I followed the directions closely. Can any of you tell me how to get back to factory settings or all the way through the root process. I'm stuck at this screen for now. Any help would be awesome.
Sent from my Nexus 7 using xda app-developers
Try using the one click oding to get back to the stock firmware. Put the phone in download mode and flash the first step of the root procedure and then stop and make sure your phone will work in stock form first before you try rooting it again.
Quickvic30 said:
Try using the one click oding to get back to the stock firmware. Put the phone in download mode and flash the first step of the root procedure and then stop and make sure your phone will work in stock form first before you try rooting it again.
Click to expand...
Click to collapse
Instead of Pass in a green box, I get Failed in a red box and the progress bar on the phone stops
That's not good, maybe try a new download. Which firmware are you flashing? MI1 or MI9?
That's actually what happened when I tried to root. It would sit forever and fail due to a timeout. What I did is after the failure..I left the phone in dl mode and connected and closed the odin..then relaunched odin and it worked the second time. That's my experience and your mileage may vary..
Same thing!
xavier6303 said:
That's actually what happened when I tried to root. It would sit forever and fail due to a timeout. What I did is after the failure..I left the phone in dl mode and connected and closed the odin..then relaunched odin and it worked the second time. That's my experience and your mileage may vary..
Click to expand...
Click to collapse
The exact same thing happened to me... I tried to install Kies 3 and add the drivers but to no avail. So from there on I just closed everything. Disconnected my note 3, reconnected it, and ran odin once more. It immeadiately passed and rooted my phone.
I have seen that in the past it is the sign of a brick you definitely have to Odin back to stock to fix that
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Yes it happened to me too. I just figured it was my crappy computer so I continued to try and after the 4th try I was able to achieve root status. Like a previous commenter suggested, it's a timed out issue.
Yea. I must have tried a dozen times a dozen different ways and I was stuck. I just said eff it and got a new phone. Debating if I want to try again, but I don't feel like potentially going thru the same heart ache. Really the only reason I care to root this phone is to get rid of those damn bloat ware apps; especially My Magazine.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
alpinesun said:
Instead of Pass in a green box, I get Failed in a red box and the progress bar on the phone stops
Click to expand...
Click to collapse
It was MI9
Sent from my SAMSUNG-SM-N900A using xda app-developers app
alpinesun said:
It was MI9
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
Just went thru this on my Note 3 - chances are youre using a vm on a mac arent you?
Make sure you use a dedicated *windows* machine and not a vm (or at lest not a fusion VM) That was my issue, I havent tried parallels. I grabbed a dedicated win 7 machine and it works perfectly.
I was going to return it of that failed, which luckily it didnt.
Cheers

[q] help help help

So I tried rooting my Samsung Galaxy Note 3 SM-N900A with Odin but it went wrong somewhere along the way and now the phone won't start up. When I try to start up, the screen says "firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" But when I tried to recover in Kies, it always gets to the end and then says that the PC can't recognize my mobile device. I can still access download mode but that's about it. I have tried looking EVERYWHERE and there is no solution! someone please help! D:
Also, I found something online that says that I can recover through Odin and I went through the whole process but when I start flashing, it says FAIL so that didn't work for me either
Did you use RDLV on MJ5 to root? If so, that's probably what bricked you.
Sent from my SM-N9005 using Xparent Red Tapatalk 2
U will prolly need to flash from scratch using the pit file
Sent from my SAMSUNG-SM-N900A using Tapatalk 4
antiguangenius said:
U will prolly need to flash from scratch using the pit file
Sent from my SAMSUNG-SM-N900A using Tapatalk 4
Click to expand...
Click to collapse
What's the pit file?
becky0251 said:
What's the pit file?
Click to expand...
Click to collapse
That just showed off why your phone got bricked. Rooting a phone got some responsibility. Let this be a lesson for you and read before you root. You will need to download the stock firmware and flash this through Odin. I guess you still can enter Download mode?
Wi-Fi Issues
I also need some help here... I did successfully root my note 3, however whenever I install a custom rom such as knoxraid or azure, my wi-fi will not work at all.
The wi-fi will be on from a clean flash, but once I try to connect to any network (I've only tried those with passwords), the wi-fi grays out and I can no longer turn it on or off. I haven't encountered anyone else with the same problem, and I have tried deleting the rom partitions and recreating them.
Disclaimer: I don't have enough posts to post in the dev forums, so that's why I'm posting here. Sorry about that.
Dearest Becky, im so sorry girl..
butchya may be fuct for a lil while let me tell ya why..
This same thing happened to me!!
I looked everywhere for an easy solution BUT THERE IS NONE !! Yet.
The reason why is because there are no easy "Odin back to stock files" yet is because at&t is a fn a-hole and locked the bootloader !!
I brikt my shıt about 4 days after I brought it home from costco.
I combed through the interwebs for the 48 hrs straight like a mad tweaker!! because of course this is our 800 dollar babies we're talking about !!
I kept getting the same error message as you are mentioning about the kies update connect your pc blah and so I tool it back to costco and played dumb and said that I got a notification to update and clicked ok and it did some stuff and "now its stuck on this screen with some error??" .. the lady at the kiosk looked it up and down and said someone else had come in last week with the same error message . LoL !!
I walked out of there with a brand new baby !!
Maybe you can do the same thing? Just hoping you are within your return timeframe.
your last but definitely not last worst case scenerio option is to stick your sim card in another phone and wait till someone from our awesome family here finds away around/through that damn bootloader and drops the beautiful Odin+files to give new birth to your 5.7 beast of an angel !!
Hope this helped in any sort of way. Good luck dear Sister!!
Please let us know how it goes. I think there are many brothers and sisters desperate as F and in ypur same predicament.
This is your best bet.
If you can get into download mode or should work
http://forum.xda-developers.com/showthread.php?p=48243768
Sent from my SAMSUNG-SM-N900A using xda app-developers app
mrkhigh said:
This is your best bet.
If you can get into download mode or should work
http://forum.xda-developers.com/showthread.php?p=48243768
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
THANK YOU SO MUCH! this worked :good:
all i did is using kingo, it work perfect.
来自我的 SM-N9005 上的 Tapatalk
Glad it worked
For anyone Reading this thread for similar issues
What probably happened is she attempted to root de LA Vega method while she was on firmware mj5 rdlv method is based on mi9 and die to this it will soft brick your device.
Unfortunately att diff not release an Odin file for mj5 or even put it on kies.
One of or members figured out how to fiddle with the files we have access to to flash a hybrid of mi9 and mj5
Making it possible to more or less recover from an mj5 brick.
Follow his steps completely and you will wind up with a stock rooted os.
But since this is such an odd way to recover I chose to use kingo to root.
Xda doesn't support kingo dir to hour closed they are in their methods and the fact it is not apparent how they are funding themselves. so you'll have to Google it. It was one of the easiest root methods I've done on a device it installs chainfires su. It is completely removable and I personally believe it is the lest chance of a brick method.
Sent from my GT-P3110 using xda app-developers app

Help with root etc... need some expert advise

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

[Q] Help Re-Rooting after OTA Update

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.

Categories

Resources