Database Develop

Returning rooted phone

As a quick FYI, I've returned two rooted Revolutions to Verizon with clockwork and both went through just fine. Anyone been charged for returning a rooted phone?
Sent from my VS910 4G using XDA App

returned my bricked rooted+rom'd LG ally without a problem.

Does anyone have the bloatware that came with this device? I will be shipping back my revo to Verizon in exchange for another phone, and I'm back on the stock room, but I'm missing bloatware. Also, how can I get the stock boot image back? I think they'll realize I was rooted when they see the Droid boot animation lol .

Samsuck said:
Does anyone have the bloatware that came with this device? I will be shipping back my revo to Verizon in exchange for another phone, and I'm back on the stock room, but I'm missing bloatware. Also, how can I get the stock boot image back? I think they'll realize I was rooted when they see the Droid boot animation lol .
Click to expand...
Click to collapse
If you have a back up from when you first rooted it should give you the stock boot.img. Then flash the stock rom found in the dev section. Then using revotoolkit.apk reinstall stock recovery. Then gingerbreak to unroot. Then update to zv6 from the about phone area and you should be good to go.
Sent from my VS910 4G using xda premium

crap...
I formatted my SD card recently, and kept my latest backup , but not my original
Is there anything I can do in regards to the boot.img?
Could someone be kind of enough to make a CWR zip file for me?
I'll even pay you $5 bucks or whatever sounds good.

Samsuck said:
crap...
I formatted my SD card recently, and kept my latest backup , but not my original
Is there anything I can do in regards to the boot.img?
Could someone be kind of enough to make a CWR zip file for me?
I'll even pay you $5 bucks or whatever sounds good.
Click to expand...
Click to collapse
My recommendation would be to flash this: http://forum.xda-developers.com/showthread.php?t=1129117
If it gives you the option to update, perhaps you should try that, and it may unroot your phone.
As far as CWM, I doubt the clerks are going to play with recovery... (that's not a guarantee, however).
If you are really desperate and scared, you should use the VZW tool for reflashing the phone, but I AM NOT RECOMMENDING IT. The tool has been known to do bad things to phones that need expert help to undo if not done properly (not only that, it's a pain in the arse).

Can I flash the boot image from that nandroid?
I was going to use the tool to run the downgrade again but I keep getting errors that I was not getting when I first rooted the phone. Mostly .msi installer package errors when selecting the .tot file.

If its in there it should be fine. If not i can make a zip of the stock boot.img when i get home but it will be about 7 central time.
Sent from my VS910 4G using xda premium

Samsuck said:
Can I flash the boot image from that nandroid?
I was going to use the tool to run the downgrade again but I keep getting errors that I was not getting when I first rooted the phone. Mostly .msi installer package errors when selecting the .tot file.
Click to expand...
Click to collapse
I don't think the boot image was included with the earlier ROMs. I *probably* have a few boot images from when I was working with Cubed on CWR, but I don't know which is which, and some of those actually can cause bricks. Boot image was p8? I don't even remember now.
As far as selecting the .tot file, it requires the support files... They come with the LGNPST Store & Lab... they would look like:
LGNPST_GenericModels_Ver_3_0_17_0.msi
I'm not positive which one is the right one as it's been a long time. Sorry this is vague, but I went through the process once, and then never again.
The person whose phone we recovered through this method had an issue after the flash where everything looked kosher, but the data would no longer work (no 3g, 4g, etc), and required Cubed's intervention to repair. So I haven't touched it since.

-mtmichaelson, thanks man, i'll just wait for you to be safe! I can wait. I'll buy you some brewski's.
-Majorpay: Yeah, I'm not too sure I want to play around with that program lol. It worked perfectly when I first rooted the phone, although I had to manually register the .dll but now it doesn't work at all.
Thanks again for all the help guys! ****, you guys have great support for this small Revo community.

Samsuck said:
-mtmichaelson, thanks man, i'll just wait for you to be safe! I can wait. I'll buy you some brewski's.
-Majorpay: Yeah, I'm not too sure I want to play around with that program lol. It worked perfectly when I first rooted the phone, although I had to manually register the .dll but now it doesn't work at all.
Thanks again for all the help guys! ****, you guys have great support for this small Revo community.
Click to expand...
Click to collapse
Alright, here you go! Let me know if there are any problems!
http://www.multiupload.com/X1DIJDNPCV

thanks man! worked perfectly. sent some money your way.

Samsuck said:
thanks man! worked perfectly. sent some money your way.
Click to expand...
Click to collapse
Thank you kind sir!
Sent from my VS910 4G using xda premium

[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.

[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

T Mobile phone to Cricket

I purchased a T-mobile Note 4 and connected it to Cricket. I have no issues using the phone but I have a pop up for Tmobile software update that keeps popping up. The update will not download, I assume because Im not on Tmobiles network. I would love to find a way to remove all Tmobile settings and have Cricket updates come to my phone. Is this even possible?

cuballboy said:
I purchased a T-mobile Note 4 and connected it to Cricket. I have no issues using the phone but I have a pop up for Tmobile software update that keeps popping up. The update will not download, I assume because Im not on Tmobiles network. I would love to find a way to remove all Tmobile settings and have Cricket updates come to my phone. Is this even possible?
Click to expand...
Click to collapse
Cricket can't give you updates for a phone it didn't sell. You can use Odin to update your device if you want to. If you're willing to root your device, then you can get rid of the nagging.
Sent from my SM-N910T using Tapatalk

I have a tmobile note 4 on Cricket too. I was able to download the 5.1.1 ota update without issue.
Sent from my SM-N910T3 using Tapatalk

Chocu1a said:
I have a tmobile note 4 on Cricket too. I was able to download the 5.1.1 ota update without issue.
Sent from my SM-N910T3 using Tapatalk
Click to expand...
Click to collapse
I have 5.1.1 but for some reason that annoying box keeps coming back. Ive tried to just take the download to make it go away but the download always fails. I want to root but Im afraid of bricking it.

cuballboy said:
I have 5.1.1 but for some reason that annoying box keeps coming back. Ive tried to just take the download to make it go away but the download always fails. I want to root but Im afraid of bricking it.
Click to expand...
Click to collapse
It's pretty hard to brick (as in I haven't heard of anyone not being able to recover) because you can just use Odin to go back to stock. Just use Odin to root/add TWRP. I think if you're on 5.1.1 you have to also use a different kernel. Instructions should be with the root thread. Just follow the directions and you will be fine.
Sent from my SM-N910T using Tapatalk

cuballboy said:
I have 5.1.1 but for some reason that annoying box keeps coming back. Ive tried to just take the download to make it go away but the download always fails. I want to root but Im afraid of bricking it.
Click to expand...
Click to collapse
Pick_A_Name said:
It's pretty hard to brick (as in I haven't heard of anyone not being able to recover) because you can just use Odin to go back to stock. Just use Odin to root/add TWRP. I think if you're on 5.1.1 you have to also use a different kernel. Instructions should be with the root thread. Just follow the directions and you will be fine.
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
There is a system-less root method available that does not require a custom kernel. Don't know why you keep getting the update message, as 5.1.1 is the current version. Root is very easy on this phone, plus you can enable tethering on Cricket. As said above, it is almost impossible(almost) to actually brick this phone.

cuballboy said:
I have 5.1.1 but for some reason that annoying box keeps coming back. Ive tried to just take the download to make it go away but the download always fails. I want to root but Im afraid of bricking it.
Click to expand...
Click to collapse
Google Zedomax. . He has a YouTube channel that will explain it very well.. he's the man.. stay high in android everyday
Chocu1a said:
There is a system-less root method available that does not require a custom kernel. Don't know why you keep getting the update message, as 5.1.1 is the current version. Root is very easy on this phone, plus you can enable tethering on Cricket. As said above, it is almost impossible(almost) to actually brick this phone.
Click to expand...
Click to collapse
Sent from my SM-N910T using Tapatalk