Okay, so I have a T Mobile SGH t999l, a few months back I rooted it, that went smoothly. I then kept it rooted for a couple of months. Later, I wanted to restore my device to factory settings, (and did so very smoothly) but I forgot to uninstall superuser for unrooting it. It still works fine, but when I checked it with root checker (pro), I got error messages saying my phone was not properly rooted. Ever since then, I've been afraid to root my phone again. Someone, please help me get my phone back up, working, and rooted again (and a step-by-step guide, if I have to do it some special way now (if not, please, just tell me so)).
What build are you running? If you have a custom recovery installed, just flash the latest SuperSU from chainfires thread.
Sent from my SM-N900T using Tapatalk
DocHoliday77 said:
What build are you running?
Click to expand...
Click to collapse
I'm running JSS15J.T999LUVUBMK.
PS. On second thought, could you include a detailed step-by-step guide on what to do, because I actually feel a bit uncomfortable doing this on my own.
There are several ways to gain root, all of which are well
documented. Im not going to rewrite another guide on it, just too much when its been done already.
Go to the firmware thread linked in my sig and download the root66 firmware for your device. Flash via odin and you will be rooted. You will find instructions in the same thread, or the root66 thread and many other places via search.
Just backup important data first, just in case.
And check the other sticky threads too for alternatives and more info.
If you have a specific question about any of ill be glad to answer it, theres just no sense in rewriting whats already been done. Dont take it the wrong way.
Two things, stay away from the toolkit if you find it, and most odin instructions are for Odin v3.07. If you use v3.09, the only difference is use AP instead of PDA, they are the same. Youll understand if you run into it.
Sent from my SM-N900T using Tapatalk
DocHoliday77 said:
There are several ways to gain root, all of which are well
documented. Im not going to rewrite another guide on it, just too much when its been done already.
Go to the firmware thread linked in my sig and download the root66 firmware for your device. Flash via odin and you will be rooted. You will find instructions in the same thread, or the root66 thread and many other places via search.
Just backup important data first, just in case.
And check the other sticky threads too for alternatives and more info.
If you have a specific question about any of ill be glad to answer it, theres just no sense in rewriting whats already been done. Dont take it the wrong way.
Two things, stay away from the toolkit if you find it, and most odin instructions are for Odin v3.07. If you use v3.09, the only difference is use AP instead of PDA, they are the same. Youll understand if you run into it.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Are you %100 sure (given my specific predicament) this will work? No offense, but it sounds kind of generic, given one specific set of circumstances.
You can never be 100% when doing anything to your device. But as a general rule, if you are having problems, odin flashing stock firmware and factory resetting is the best chance of fixing stuff. Root66 is pretty much the same thing, only pre rooted, with knox removed. Its as close as you can get to 100% stock rooted on 4.3.
The only real issue is usually if you are still running base firmware build 4.1.2. At this point there is no warranty bit and you can still flash older firmware. Once on 4.3 this changes. So if youre already on 4.3 firmware, theres nothing to really lose by reflashing it or updating to the newer 4.3.
I wouldnt call it generic, as I stated above, this is often the best chance of getting things working the way you want. Its solved countless issues.
In the end its up to you what route you want to go. If youre not comfortable with my recommendation, I suggest you read up on other alternatives and choose what you are comfortable with. Wont hurt my feelings either way. Its your device and your risk, so be comfortable with what you are about to do.
Sent from my SM-N900T using Tapatalk
Try to take risk it never harms, Those who never did a mistake they never tried anything u learn from your mistakes.
Just got the T-mo T999 was on stock 4.3 flashed the cf root with ODIN, Rotted used GO im to flash the recovery BAM DONE. Stock rooted with recovery installed.
Now searching for a ROM.
Thanks
Thankyou for the help you all gave me, it worked!!!
Please, HELP!!!
I was trying to install an Xposed module, but I don't remember which one, and I don't remember anything after that. Now my phone is not working (at least, not like you'd expect it to) anymore. Whenever I try to do much of anything, it starts displaying messages like "Unfortunately, '.............' has stopped", or "Unfortunately, the process '.............' has stopped". The most notable being, "Unfortunately, Google play Services has stopped", and "Unfortunately, the process com.google.processes.gapps has stopped". Please, HELP!!!
I have a problem
Give me a break said:
I was trying to install an Xposed module, but I don't remember which one, and I don't remember anything after that. Now my phone is not working (at least, not like you'd expect it to) anymore. Whenever I try to do much of anything, it starts displaying messages like "Unfortunately, '.............' has stopped", or "Unfortunately, the process '.............' has stopped". The most notable being, "Unfortunately, Google play Services has stopped", and "Unfortunately, the process com.google.processes.gapps has stopped". Please, HELP!!!
Click to expand...
Click to collapse
It works well enough, after I get through all the original errors I can call (and receive calls), and receive texts, but I can't use the keyboard, or any of the apps involving any form of Wireless Data (eg. Wi-Fi, Bluetooth, 3G/4G or any other cellular data) or GPS.
In your op you wanted to just be stock but rooted and stable, correct? Did you ever flash the root66 firmware I originally suggested?
Related
Hi, I recently got ATT note 2. I tried to root it and did the CF root from chainware and also tried galaxynote2root.com root. both didnt work, well it gave me root but I cant install a recoveery. I flashed it multiple times like 10 I think because my binary coutner says 10. idk what to do.Can someone help. plz post links if i need to download something. I do have all the drivers and stuff. its just that no recovery. im running 4.1.2 jelly bean
Not in any way am I trying to be rude or condescending. ...but
You need to stop and read the steps again. ...before you accidentally do damage to the device partitions or worse. ..
Custom recovery images are pushed to the device via Odin when the stock recovery still exists. ...and if done incorrectly. ..you can brick the device.
Please explain the method you are using to attempt the recovery flash. .and we can help correct the problem.
But by all means. ..don't attempt another flash of recovery until the problem is found.
Recovery is essential to do exactly as the term states. ..."recovery"...and without it. ..you will be in trouble with no way back but JTAG service.
Read and read again the recovery steps. ..and go slow here...
Your on the edge at the moment....g
gregsarg said:
Not in any way am I trying to be rude or condescending. ...but
You need to stop and read the steps again. ...before you accidentally do damage to the device partitions or worse. ..
Custom recovery images are pushed to the device via Odin when the stock recovery still exists. ...and if done incorrectly. ..you can brick the device.
Please explain the method you are using to attempt the recovery flash. .and we can help correct the problem.
But by all means. ..don't attempt another flash of recovery until the problem is found.
Recovery is essential to do exactly as the term states. ..."recovery"...and without it. ..you will be in trouble with no way back but JTAG service.
Read and read again the recovery steps. ..and go slow here...
Your on the edge at the moment....g
Click to expand...
Click to collapse
well first i downloaded the galaxynote2root zip file from the website. it gave the odin and a file to flash. then I put phone in download mode and flashed. successfully got root. I think its because I have the latest software. 4.1.2 everyone got root in 4.1.1 and the old one doesnt work anymore. what did u use to root.? I did all the steps exactly what max did. and he got root like that and installed cwm. i followed video and blog post. this is the video : http://www.youtube.com/watch?v=NFHZ535L7is
Is it better to use the toolkit that to use this method? toolkit users have had less problems.
ALSO NOW ITS DOWNLOADING SOME UPDATES WHEN I CONNECT TO WIFI. im already rooted so does that mean im going to brick if i update so im not even using the phone now plzz someone help me
thanks for reply
FIRST thing you need ro do is check and make sure you have a recovery.
Imo the number one reason noobs break there phones is with out realizing it they borked their recovery and try to root , flash a custom rom, OR take an ota.
No recovery = no ota or any other flashing.
Check you recovery by:
Power off> press vol up, menu, and home.
This is done all at once. As soon as you see the text appear in the top right corrner release. It takes a bit of practice but its not a biggie.
Now.. do you see recovery or are you in a boot loop?
If you have a boot loop while trying to get into recovery...it means u no have recovery!!!
Secondly Stop flashing root!!
Lol pick a single root method that has been verified to work by others. And stick to it.
Its sooo important to read.
In fact with some phones one variant of root wont work if you have an update and hence a different android version.
So you need to read.
If you have recovery click factory restore.
You can do this from the os or.. I prefer going into recovery and hitting factory restore. iTS THE SAME.
If you have a boot loop while trying to get into recoveru
Click my signature in web view.
Go do the kies efr thing as I explain it my tut. Get your phone back to a nice clean start.
Kies efr IS THE FASTEST AND SAFEST way for newbs to get back to stock.
Newbs should NOT be using odin unless they are 100% sure they know what they are doing and are comfortable doing so. My efr tutorial in my sig will teach you how to use KIES EFR (Emergency Firmware Recovery)
I prefer to send people the gn2 toolkit.
Its easy and also has plenty of options.
Just remember to uninstall kies first.
There are numerous ways to root.
Pick one. Lol.
sent from my T.A.R.T.I.S
(Time And Relative Tarts In Space)
Freakboy hit it on the head...
I won't try to add more into the responses, as this will just confuse the issue more...
Follow his lead, and his advice.....g
ok thanks a lot, i flashed twrp recovery now running jellybam rom, i was wondering if it supports transparent status bar? not just in one app in all of them.
The answer to that question is found in the respective thread for the rom you are using. .
Check there first. ...
General searches also yield great results. ...g
im going to switch to pac man rom soon, bc xda banned jellybam for not giving credits i think. anyway whats a good kernel to use? now im using the one that came with jellybam. im guessing u experminented a lot and give me some suggestions. i dont wanna overclock just looking for smooth performance.
For pac.....
Use the preloaded kernel ..
It is optimized for the build and you can get support ...
If you change kernels ...you may not get support ...g
Hi. So I'm totally at a loss as to what to do. I've had a Galaxy S3 for a little over a year now, and just recently decided to try and root it. I'm not very experienced with phone software in general, but I've got enough understanding of how Android works to want to try my hand at this.
I followed mrRobinson's really helpful root via Odin guide, found here: http://forum.xda-developers.com/showthread.php?t=1774722
I never got past step 2, however. I got everything downloaded, got my phone plugged in and going, and...it's stuck now. It still says it's in the middle of download, but it's been downloading "cache.img.ext4" for about an hour now. Clearly there's something not right.
Here is a screenshot of what this has looked like: http://i.imgur.com/jy21pHd.jpg
I'd heard that using a third party cable was not advisable, but unfortunately that was something I learned after the download had already begun. As of right now, my phone is still in download mode. What do I do? Is there a way for me to go back to normal and try rooting it again with a stock cord? Or is there something I haven't done that'll finish the download? I'm terrified of unplugging it or messing with it in any way without knowing what the consequences will be.
PS: Please explain this to me as simply as possible. I'm not familiar with a lot of Android jargon, I apologize.
nuclearteacup said:
Hi. So I'm totally at a loss as to what to do. I've had a Galaxy S3 for a little over a year now, and just recently decided to try and root it. I'm not very experienced with phone software in general, but I've got enough understanding of how Android works to want to try my hand at this.
I followed mrRobinson's really helpful root via Odin guide, found here: http://forum.xda-developers.com/showthread.php?t=1774722
I never got past step 2, however. I got everything downloaded, got my phone plugged in and going, and...it's stuck now. It still says it's in the middle of download, but it's been downloading "cache.img.ext4" for about an hour now. Clearly there's something not right.
Here is a screenshot of what this has looked like: http://i.imgur.com/jy21pHd.jpg
I'd heard that using a third party cable was not advisable, but unfortunately that was something I learned after the download had already begun. As of right now, my phone is still in download mode. What do I do? Is there a way for me to go back to normal and try rooting it again with a stock cord? Or is there something I haven't done that'll finish the download? I'm terrified of unplugging it or messing with it in any way without knowing what the consequences will be.
PS: Please explain this to me as simply as possible. I'm not familiar with a lot of Android jargon, I apologize.
Click to expand...
Click to collapse
I don't think its going to work without the stock cord. But I think unplugging it would just result in a failed root I don't think it would brick. Not positive though
Sent from my SPH-L710 using xda app-developers app
nuclearteacup said:
...
PS: Please explain this to me as simply as possible. I'm not familiar with a lot of Android jargon, I apologize.
Click to expand...
Click to collapse
did you unplug the phone yet? how did it go?
Just FYI since it sounds like you are new to this, there are a few different s3 models depending on carrier. Make sure you flash something compatible with your phone.
From your screenshot, looks like everything flashed except the cache partition. Are there any other images in the .tar.md5 file you downloaded?
Ok, first of all, new to rooting and all that follows. However, I'm not new to forums and if this is in the wrong category, or if I overlooked a similar post, I am sorry. Feel free to redirect me to wherever you see fit. I know just too well how similar posts can be annoying, but I feel like I've exhausted Googlesearching and looked everywhere I can think of.
So, I have a Note II. N7100, Android 4.4.2 and I want to root it. Googlesearching has found me a lot of nice looking ROMs, and besides looks the added functions tempt me. Wont be long until I upgrade to a Note 4 or 5 anyway, figure I might as well. For what its worth, I live in Norway, and AT&T does not exist over here, nor does any other major american carrier. USB debugging was on the entire time.
I got the Odin V3.10, and appropriate clockworksmod files, and thought everything was peaches. Into download mode (after backing up ofc), Odin finds it, I upload everything and Odin says "PASS" in nice, green letters. When it reboots, it looks the same as before, but.. "Unfortunately, SuperUser has stopped", Titanium backup does not work since it apparently isnt rooted. Root Checker says the same. However, when checking for updates my phone displays "The operating system on your device has been modified in an unautorized way. Try downloading software updates using Samsung KIES on your PC, or visit a customer service center."
Read alot about devices having to be unlocked from carrier, however all google searches on "how to check for carrier lock on Note 2" yields numbersequences I have to input into the dialler and dial. None of the sequences give anything other than "Connection problem or invalid MMI code". I honestly dont remember if its carrier locked or not.
I came across an article here on XDA saying that with the later versions of android, KNOX has become an issue when trying to root, but someone had found a way around it. I downloaded MJ5BLPatch.tar.md5, uploaded to my phone via Odin, and here it fails, looses connection with the device and cant reconnect. Phone displays something alon the lines of "Invalid magic code" or the similar in red text.
I am the newb here, looking for help, and if I screwed up big somewhere I am cool with a little flaming. I just want to squeeze this for what use I can before upgrading, and probably rooting that too.
Any help as to how I can root it and load custom ROMs? I appreciate any and all help, sincerely.
Forget that MJ5 bootloader related stuff.
Reflash CWM using Odin and untick auto reboot, run through and reboot manually.
After reboot into recovery flash SuperSu.zip, start supersu after reboot system and disable knox by following the advices from app.
Thank you very much. i feel exceedingly stupid, I had been using the guide found on Note2root.com, when I applied step by step from this guide (http://forum.xda-developers.com/showthread.php?t=2143479) everything worked out. hope this may be of help to anyone having the same issues.
Again, thank you very much for your help.
Hello, first timer here. I have never tried rooting or anything, but today I finally decided to... and messed it up.
Verizon Samsung Note 2 SCH-i605 (yes, still.)
Got it on July 2nd, 2013, so I believe it was build 4.1.1 kernel 3.1? Not too sure on the legalities
Completely unrooted and unmodded
I was using kingo root and everything was fine until it hit about 52% on the rooting process when my computer lost connection with my phone. Since, it gave me the "Firmware upgrade encountered an issue" problem. So then I google-fu'd and followed directions of:
http://forum.xda-developers.com/showthread.php?t=2040264
http://forum.xda-developers.com/showthread.php?t=2120726
http://forum.xda-developers.com/showthread.php?t=2582290
http://forum.xda-developers.com/showthread.php?t=2024207
etc.
and used Odin 3.10.7 (and 3.10.0 just in case, both on and off admin mode cause why not) on every single md5 available in all those links and the one from sammobile.com for sch-i605.
And each time, I would either received failure on "sboot.bin" or receive the "System Software Not Authorized" error if succeeded (it was stuck in bootload? too, kept flashing the logo then the error message). The VERY first time, however, it actually brought me to that page where I'm allowed to press things like erase cache, factory reset, or reboot my phone. There, I chose all those options in the order I've listed them. And ever since I haven't seen that screen again.
My issue seems to be every problem I can find put together, and can't seem to resolve it with my skills alone. I honestly don't care about recovering my data (which I believe is impossible now anyway) or rooting my phone. I just want it to turn on again.
Thanks in advance.
p.s. getting a new phone isn't an option currently
-edit-
Checked my verizon wireless software upgrade assistant for some info, and it says "Up to date" and "Version ND3" if that means anything to you pros out there.
jk1982 said:
Hello, first timer here. I have never tried rooting or anything, but today I finally decided to... and messed it up.
Verizon Samsung Note 2 SCH-i605 (yes, still.)
Got it on July 2nd, 2013, so I believe it was build 4.1.1 kernel 3.1? Not too sure on the legalities
Completely unrooted and unmodded
I was using kingo root and everything was fine until it hit about 52% on the rooting process when my computer lost connection with my phone. Since, it gave me the "Firmware upgrade encountered an issue" problem. So then I google-fu'd and followed directions of:
http://forum.xda-developers.com/showthread.php?t=2040264
http://forum.xda-developers.com/showthread.php?t=2120726
http://forum.xda-developers.com/showthread.php?t=2582290
http://forum.xda-developers.com/showthread.php?t=2024207
etc.
and used Odin 3.10.7 (and 3.10.0 just in case, both on and off admin mode cause why not) on every single md5 available in all those links and the one from sammobile.com for sch-i605.
And each time, I would either received failure on "sboot.bin" or receive the "System Software Not Authorized" error if succeeded (it was stuck in bootload? too, kept flashing the logo then the error message). The VERY first time, however, it actually brought me to that page where I'm allowed to press things like erase cache, factory reset, or reboot my phone. There, I chose all those options in the order I've listed them. And ever since I haven't seen that screen again.
My issue seems to be every problem I can find put together, and can't seem to resolve it with my skills alone. I honestly don't care about recovering my data (which I believe is impossible now anyway) or rooting my phone. I just want it to turn on again.
Thanks in advance.
p.s. getting a new phone isn't an option currently
-edit-
Checked my verizon wireless software upgrade assistant for some info, and it says "Up to date" and "Version ND3" if that means anything to you pros out there.
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist. To get you the best possible assistance, I'm going to move this thread to your device's Q&A forum. Good luck!
install kies and try flashing rom. do you have rom from i.e. sammobile? use different odin versions and do not mark repartition
yaro666 said:
install kies and try flashing rom. do you have rom from i.e. sammobile? use different odin versions and do not mark repartition
Click to expand...
Click to collapse
KIES is unable to read my phone (tried the bottom 3 versions of it), and I've tried running Odin 3.07 and unchecked repartition for every stock and restore md5s I had for my phone... the ones that didn't fail sboot.bin are still giving me unauthorized error.
I'll keep trying all the combinations, but it seems moot at this point.
I have a sprint note 4 with the OB7 rooted with odin and I used chainfire a long time ago, over a year and I can't remember
Where do I start to update my phone without having to reflash it?
Sorry I will continue to search and hope to find an answer..
Thank for your help and time.
No PC or just looking for alternate method?
You may persuade Best Buy or Sprint to update it if you claim the camera doesn't focus or Wi-Fi Calling is broken. (I carried my phone to Samsung Experience in BB twice early in its day with those actual complaints and both times they insisted on flashing the firmware. Rather inconvenient for a rooted phone but if you're looking to update, may work to your benefit).
If you're wanting Marshmallow on it, I'd suggest removing your fingerprints and factory reset. May help make the transition less buggy.
If you've never updated beyond OB7, know that doing so will mean that you can't go back to to OB7 or lower with Odin. The bootloader will prevent that once upgraded. Just be aware of that limitation.
Sent from my SM-N910P using Tapatalk
samep said:
No PC or just looking for alternate method?
You may persuade Best Buy or Sprint to update it if you claim the camera doesn't focus or Wi-Fi Calling is broken. (I carried my phone to Samsung Experience in BB twice early in its day with those actual complaints and both times they insisted on flashing the firmware. Rather inconvenient for a rooted phone but if you're looking to update, may work to your benefit).
If you're wanting Marshmallow on it, I'd suggest removing your fingerprints and factory reset. May help make the transition less buggy.
If you've never updated beyond OB7, know that doing so will mean that you can't go back to to OB7 or lower with Odin. The bootloader will prevent that once upgraded. Just be aware of that limitation.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Well, I didn't know there was any updates past the OB7, When I updated with chainfire it kept it from updating through OTA... I also wasn't worried about it because I hate playing games on my phone and flashing all the saves away..
I suppose that is a bit of a clarification on my part... I do want to update the software and not my phone especially since I like the IR blaster and removable battery other options that the Note 7 doesn't have... I almost was going to upgrade to a new Note 7 early but I think I will wait for something new and I am sure I can update the software on the 4 and make it just as good if not better...
You can upgrade fairly easy using Odin. This thread will get you started:
http://forum.xda-developers.com/showthread.php?p=63868221
I did find this post interesting but can't say I've ever tried it. I would at least remove my fingerprints, wipe cache and dalvik-cache before trying this. But I also prefer to also factory reset and wipe internal memory. But that's not required if you're close to stock touchwiz. The dalvik-cache would also get rebuilt, if needed, without bootlooping. So I DON'T doubt it worked, just that I've read posts saying factory reset and fingerprint removal cleared some issues for some users. (Post#24)
http://forum.xda-developers.com/showpost.php?p=68549881&postcount=24
Sent from my SM-N910P using Tapatalk
samep said:
You can upgrade fairly easy using Odin. This thread will get you started:
http://forum.xda-developers.com/showthread.php?p=63868221
I did find this post interesting but can't say I've ever tried it. I would at least remove my fingerprints, wipe cache and dalvik-cache before trying this. But I also prefer to also factory reset and wipe internal memory. But that's not required if you're close to stock touchwiz. The dalvik-cache would also get rebuilt, if needed, without bootlooping. So I DON'T doubt it worked, just that I've read posts saying factory reset and fingerprint removal cleared some issues for some users. (Post#24)
http://forum.xda-developers.com/showpost.php?p=68549881&postcount=24
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Interesting I used chainfire and odin I think to root my phone originally, the really strange part is I used the supersu app from chainfire and used the full unroot option and it says I am unrooted, I originally wanted to do this just so I can continue playing pokemon go, haha, but I cannot automatically update my phone itself, so I am going to look at the thread you posted and see if I can update that way... I might have to attempt to use magisk also so I can root and continue to use the pokemon game...
In reply to your original question, I have a PC and used it to root originally but I don't have that computer anymore so I need to find the correct stuff to download and I would feel more comfortable with a bit of a how-to as a refresher
Curtai said:
Interesting I used chainfire and odin I think to root my phone originally, the really strange part is I used the supersu app from chainfire and used the full unroot option and it says I am unrooted, I originally wanted to do this just so I can continue playing pokemon go, haha, but I cannot automatically update my phone itself, so I am going to look at the thread you posted and see if I can update that way... I might have to attempt to use magisk also so I can root and continue to use the pokemon game...
In reply to your original question, I have a PC and used it to root originally but I don't have that computer anymore so I need to find the correct stuff to download and I would feel more comfortable with a bit of a how-to as a refresher
Click to expand...
Click to collapse
You'll need Odin, stock tar and Samsung USB driver to update with the method I'm familiar with. Make sure that Samsung KIES and Smart Switch applications aren't running when using Odin. You should open Odin in administrator mode but that isn't required for Windows 10. Use your original Samsung USB cable or another cable with data lines included.
The Samsung driver can be downloaded from Samsung support for the Note 4's thread. You'll find all you need in the stock tar thread for a how-to tutorial.
I never used Samsung Switch on my Note 4 so I'm looking for confirmation that it works for upgrading a modified phone to latest OTA update (as posted in that quote).
Sent from my SM-N910P using Tapatalk