Related
I'm having an issue with my t989 that has persisted since I stopped using Kang's ROMs and the Bullet Kernel.
After going from the Juggernaut ROM to Darkside's ICS when it came out, my phone started to not be recognized by any computer, be it OSX or Windows. I've tried everything on the PC software side, from clearing Kies and the Samsung Drivers, as well as clearing registry information and re-installing both separately, and this has not helped at all. The windows error is:
Windows has stopped this device because it has reported problems. (Code 43)
I don't use antivirus, and I don't use a firewall, suffice to say I'm a programmer and have plenty of experience in doodling with phones, and I'm stumped. I've come to the conclusion that the Bullet Kernel installed from my Juggernaut days is the cause of the issue, as I repeated the process on a friend's device and he has the exact same symptoms.
With this situation, I'm not able to access ODIN to return to complete stock, so I can't flash over the Bullet Kernel. Alongside the USB device not recognized problem, I also was not able to get into ODIN / download mode until I made my own USB Jig to get around it.
Is there any way to get back to the stock kernel without ODIN? Would Mobile Odin Pro work if Chainfire added support for our device? It's really pissing me off as I'm a software developer and can't use my own device to build to.
EDIT: As a note, when moving from Juggernaut / Bullet to Darkside, I flashed the appropriate ICS radio and kernel, but when returning to 2.3.5 stock from Samsung, somehow the Bullet kernel managed to persist.
edit: nvm you answered my question.
Im not aware of a way to unroot without Odin Can you get into recovery?
Hey, not sure if this will help, but there's links to flashable stock zips in this thread:
http://forum.xda-developers.com/showthread.php?t=1869082
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
blackangst said:
edit: nvm you answered my question.
Im not aware of a way to unroot without Odin Can you get into recovery?
Click to expand...
Click to collapse
There is still a way to get back to the Stock ROM ( 2.3.5 ) and Recovery, but the kernel flash was not included with the package:
http://galaxys2root.com/t-mobile-galaxy-s2/how-to-unroot-t-mobile-galaxy-s2-sgh-t989/
This is apparently the "Zedomax" unroot that does not need the ability to hook up to Odin, so needless to say, it's not unrooting that I need, it's getting back to the stock kernel that is the problem.
Obviously now that I'm unrooted, there really isn't a way for me to install Mobile Odin Pro even if I had it. I've been looking how to contact him to request it, because I don't want to be rude and PM him the request when I'm sure that's not the way that respected XDA members would want.
Can I ask why you think the kernel alone isn't being overwritten? That seems odd to me, since every ROM packs its own kernel, and flashing a kernel specifically only replaces the kernel. So if you flash an ICS ROM you're getting an ICS kernel, GB you get a GB kernel, etc. It wouldn't work otherwise. If you haven't done it already, you might want to try Darkside super and cache wipes.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
RTFOP said:
Can I ask why you think the kernel alone isn't being overwritten? That seems odd to me, since every ROM packs its own kernel, and flashing a kernel specifically only replaces the kernel. So if you flash an ICS ROM you're getting an ICS kernel, GB you get a GB kernel, etc. It wouldn't work otherwise. If you haven't done it already, you might want to try Darkside super and cache wipes.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Well, for one, I get a Bullet loading screen... Apparently reading through other threads, it's a known issue that Zedomax's Stock ROM method doesn't include the kernel, which basically means I may have f'ed myself permanently seeing as how I can't get ODIN access. Unfortunately, galaxys2root.com didn't tell people on their site that it didn't include the kernel, so needless to say, I'm never going to that site again and I would advise people not to follow any of their stuff either.
Although it's a small omission, their lack of providing information has just caused me to possibly lose a moddable phone.
EDIT: the threads that I've been reading through are the ones you supplied, RTFOP
So can you not get into download mode or get your computer to recognize your phone in recovery? If you're willing to tinker some you can back track and root and reinstall and overwrite that kernel and then circle back.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
RTFOP said:
So can you not get into download mode or get your computer to recognize your phone in recovery? If you're willing to tinker some you can back track and root and reinstall and overwrite that kernel and then circle back.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Well, to re-hash over what I've said already for clarification's sake:
1. I can get into download / ODIN mode
2. I still CANNOT get my phone to recognize in recovery. I know it's not my PCs, it's the phone, and I suspect the Bullet Kernel as it was not reverted back to the stock kernel when I flash Zedomax.
With that said, I don't see how it's possible for me to root and get CWM seeing as how I'm on stock Recovery (3e), and I can't ODIN. Unless there is a untethered way to root the t989, I think i'm up ****'s creek.
At what point did you lose root access though?
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
RTFOP said:
At what point did you lose root access though?
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
The whole point of flashing Zedomax's .zip is to unroot and go back to stock Samsung 2.3.5.
Just to verify, I downloaded root checker and it states I do not have root access.
So if you can get into Odin with your jig workaround, why can't you load a custom recovery and super user and then run Darkside wipes and install whatever ROM you want?
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
RTFOP said:
So if you can get into Odin with your jig workaround, why can't you load a custom recovery and super user and then run Darkside wipes and install whatever ROM you want?
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
I think there's a fundamental misunderstanding between you and I. When I say I can get into download / Odin MODE, that means I can force the phone itself into ODIN Mode, but since my computer does not recognize my t989, the ODIN application on my windows box does not recognize the phone, and the ID box does not 'turn yellow' as it should if my phone were recognized by my PC.
So even though my phone is waiting for the ODIN application on my windows to send it commands, I can't send it commands because the application won't recognize the phone.
Thus is my quandary.
Yeah, sorry, I didn't get that. Have you tried plugging it in without the sd card in? It's kind of a long shot, but errors on there might be keeping your computer from communicating with the device, since it seems to be working otherwise. Maybe the jtag repair service through mobile tech videos?
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
RTFOP said:
Yeah, sorry, I didn't get that. Have you tried plugging it in without the sd card in? It's kind of a long shot, but errors on there might be keeping your computer from communicating with the device, since it seems to be working otherwise. Maybe the jtag repair service through mobile tech videos?
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
As you suggested, I tried taking out the SD card and that didn't help.
I'm trying to do as much as possible before I try and repair it. I may consider trying for a warranty replacement and take the risk, but I'd like to try everything I can before I take that step, I don't like not being able to fix something =p.
Thanks for the help btw.
IM sorry all you are passing through , I couldn't use my phone for two week when I messed up, . Well let's try get root with this apps
http://forum.xda-developers.com/showthread.php?t=833953
If the permanent root doesn't work try the temporary
Sent from my SGH-T989 using xda app-developers app
Hello,
So I've been rooted for a while now, i was going to install a custom rom but decided not to a few months ago. Tonight, i decided to install aokp, however my phone would not go into cwm, only stock recover. I could have sworn it was installed, but fine, so i installed it once again with auto reboot in odin checked, and it still wouldnt enter cwm. I then tried to install it again with auto reboot checked off so i could see if i could enter it without the reboot. I ended up getting into it, but then when i was taking a NANDROID, it just froze on one of the first steps. Fine, reboot, try to enter cwm again. Nope, just stock android recovery. I am sure im installing it correctly and pressing the right button combos. I am at a total loss for what is stopping me from being able to enter cwm. I hope you guys know/help me find whats going on.
Thanks!!!
Zay
maybe you didn't actually "root" your phone to begin with lol
are you sure you have "superuser" or "superSU" app?
anyways to get CWM or TWRP recovery you need
find a up-to-date CWM or TWRP (if i spell teamwin recovery correctly)
download it
put your phone in ODIN Mode (download mode) by power + vol down + home
flash the recovery
i personally think twrp is better
they just released a new version which support ExFat
and all you need is just use terminal on your phone to install it.
pcshano said:
maybe you didn't actually "root" your phone to begin with lol
are you sure you have "superuser" or "superSU" app?
anyways to get CWM or TWRP recovery you need
find a up-to-date CWM or TWRP (if i spell teamwin recovery correctly)
download it
put your phone in ODIN Mode (download mode) by power + vol down + home
flash the recovery
i personally think twrp is better
they just released a new version which support ExFat
and all you need is just use terminal on your phone to install it.
Click to expand...
Click to collapse
Yes my phones rooted.
If you actually read my post, you'd know that that is EXACTLY what I am doing.
Thanks anyways though..
Zay48 said:
If you actually read my post, you'd know that that is EXACTLY what I am doing.
Thanks anyways though..
Click to expand...
Click to collapse
i have no idea how i missed that odin part on your part... i read everything but somehow i just missed that part alone 0_0
anyways
try install twrp recovery instead then
by using terminal emulator
can get it here https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
latest twrp can be found here http://forum.xda-developers.com/showthread.php?t=2074951
pcshano said:
i have no idea how i missed that odin part on your part... i read everything but somehow i just missed that part alone 0_0
anyways
try install twrp recovery instead then
by using terminal emulator
can get it here https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
latest twrp can be found here http://forum.xda-developers.com/showthread.php?t=2074951
Click to expand...
Click to collapse
Aha its alright
I'd like to stick with cwm though, its what im familiar with. If nobody else has an answer i'll try it tomorrow though.
Thanks
Zay48 said:
Aha its alright
I'd like to stick with cwm though, its what im familiar with. If nobody else has an answer i'll try it tomorrow though.
Thanks
Click to expand...
Click to collapse
if you still want cwm then i guess you can try flash stock rom and root it again and see
since you're going to flash a custom rom which will delete all your data anyways
Zay48 said:
Aha its alright
I'd like to stick with cwm though, its what im familiar with. If nobody else has an answer i'll try it tomorrow though.
Thanks
Click to expand...
Click to collapse
Stock ROM has a built in script that reloads standard android recovery when it boots. The only way to keep it is to keep Odin auto reboot unchecked, boot directly in and make your nandroid/flash custom. Once you are on a custom ROM CWM will stick.
On a side note TWRP is a very nice recovery and many people find it much easier to use. If you insist on CWM, make sure you have the latest version. You might need to flash CWM again if you had a bad flash. It shouldn't freeze up on a nandroid.
Many people never experienced this because they flashed during early ICS when the device was released. The change was an update just before JB was released which caused this little annoying script to appear.
Sent from my SGH-I747 using xda app-developers app
RPelham said:
Stock ROM has a built in script that reloads standard android recovery when it boots. The only way to keep it is to keep Odin auto reboot unchecked, boot directly in and make your nandroid/flash custom. Once you are on a custom ROM CWM will stick.
On a side note TWRP is a very nice recovery and many people find it much easier to use. If you insist on CWM, make sure you have the latest version. You might need to flash CWM again if you had a bad flash. It shouldn't freeze up on a nandroid.
Many people never experienced this because they flashed during early ICS when the device was released. The change was an update just before JB was released which caused this little annoying script to appear.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thankyou!! That makes sense ;p. When I did get to start making a nandroid last night but it froze, right before it froze it said the free space on my sdcard was 1612 mb (or something like that) This is wrong, I have the 16gb i747 so I have 11.95 gb of usable storage for apps and such, after deleting some big apps I have 4.93 gb available, my sdcard is a 16 gb sdcard which has 12.06 gb available. Do the math and I have enough room on my sdcard for a nandroid, so what could be causing cwm to freeze and report false information?
Zay48 said:
Thankyou!! That makes sense ;p. When I did get to start making a nandroid last night but it froze, right before it froze it said the free space on my sdcard was 1612 mb (or something like that) This is wrong, I have the 16gb i747 so I have 11.95 gb of usable storage for apps and such, after deleting some big apps I have 4.93 gb available, my sdcard is a 16 gb sdcard which has 12.06 gb available. Do the math and I have enough room on my sdcard for a nandroid, so what could be causing cwm to freeze and report false information?
Click to expand...
Click to collapse
Bump
what version of CWM are you currently running?
you could always try to download GooManager or ROM Manager from the Play Store.
then from one of those, install the custom recovery, GooManager for TWRP or ROM Manager for CWM.
xBeerdroiDx said:
what version of CWM are you currently running?
Click to expand...
Click to collapse
3.0.7
Zay48 said:
3.0.7
Click to expand...
Click to collapse
That is a very out dated version as they are now up to version 6.0.2.3. I would try getting an updated CWM. that could very well fix your freezing/reporting problems...
Sent from my SGH-I747 using xda app-developers app
CWM is very very funny and one of the reasons I switched to TWRP was for stability
In my experience errors come up on restoring images when 1) you don't use the same version you backed up the image with 2) you don't get to CWM through the same method you used while making the image (ie through ROM manager with your phone on).
zetsui said:
CWM is very very funny and one of the reasons I switched to TWRP was for stability
In my experience errors come up on restoring images when 1) you don't use the same version you backed up the image with 2) you don't get to CWM through the same method you used while making the image (ie through ROM manager with your phone on).
Click to expand...
Click to collapse
He's not having a problem restoring images, he's having a problem making his first nandroid.
Sent from my SGH-I747 using xda app-developers app
Zay48 said:
3.0.7
Click to expand...
Click to collapse
Holy hell! CWM 3.0 is still around? Like RP said, you're recovery is severely outdated.
RPelham said:
That is a very out dated version as they are now up to version 6.0.2.3. I would try getting an updated CWM. that could very well fix your freezing/reporting problems...
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
This.
Also, I was a long time CWM touch user on my old NS. After using TWRP on this phone, I will never look back at CWM. TWRP is much more user friendly. Give it a shot OP unless you're adamant in using CWM. Again, update your recovery.
Download rom manager and update your cwm and then try making a nandroid again.
Sent from my SGH-I747 using xda app-developers app
CrackerTeg said:
Holy hell! CWM 3.0 is still around? Like RP said, you're recovery is severely outdated.
This.
Also, I was a long time CWM touch user on my old NS. After using TWRP on this phone, I will never look back at CWM. TWRP is much more user friendly. Give it a shot OP unless you're adamant in using CWM. Again, update your recovery.
Click to expand...
Click to collapse
I was also a CWM user, but after I got my s3 and my first flash of CWM on the s3 hard bricked my phone, I decided to use TWRP. Little did I know I was missing out on what TWRP had to offer. I won't ever turn back to CWM again lol.
That said... If you insist in CWM, this is the guide I followed to get a successful CWM flash. (This was the CWM I was running successfully for the brief time TWRP disbanded.)
http://wiki.cyanogenmod.org/w/Install_CM_for_d2att
The above is for the ATT variant only. If you have a different variant and can't find the link, post back and I'll find it for you
Sent from my SGH-I747 using xda app-developers app
CrackerTeg said:
Holy hell! CWM 3.0 is still around? Like RP said, you're recovery is severely outdated.
This.
Also, I was a long time CWM touch user on my old NS. After using TWRP on this phone, I will never look back at CWM. TWRP is much more user friendly. Give it a shot OP unless you're adamant in using CWM. Again, update your recovery.
Click to expand...
Click to collapse
apparently it's still around because new android users who want to root use those guides with outdated files
RPelham said:
I was also a CWM user, but after I got my s3 and my first flash of CWM on the s3 hard bricked my phone, I decided to use TWRP. Little did I know I was missing out on what TWRP had to offer. I won't ever turn back to CWM again lol.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Preach brother!
Looking into rooting? Maybe try this foreign ROM thing? (Not talking about ethnicities here) Here is the place to be.
First of all, make sure you have a T-Mobile Galaxy S3. (Aka t999 or d2tmo)
If you follow instructions here for any other device, even for galaxy s3's of another carrier you are extremely likely to regret it and end up having to unbrick your device because you installed an incompatible file.
You can take your battery out to make sure it says t999 under if you are not absolutely sure.
Rooting is a similar idea to jail breaking an iPhone. It removes what restrictions there are with android devices. Yes, it is perfectly legal.
Which leads me to my disclaimer:
I take no credit for what's posted here.
The only work here that's mine is the organization. Please donate to the rightful people who spent quality time developing.
Also I am not responsible for any damage done to your device.
It is vital that you follow instructions in every exact detail.
Firstly, rooting.
1. Install drivers for your device onto your PC. To do this, you can install Samsung Kies or there are downloads that will install the drivers solely(recommended link for drivers http://d-h.st/zya)(thanks DocHoliday77). If you get to the point where you can exchange files to phone from the computer and vice-versa then you're set for drivers.
2. Do a backup (using Kies or a program of your choice)
3.Uninstall Kies. Kies doesn't play nicely with the program used to root called Odin. So uninstall Kies so Odin can work unhindered. Your drivers should stay. But make sure you can still copy files between your phone and computer before proceeding.
4.Follow these instructions put together by OfficialPhoneRebel(aka EverythingApplePro):
http://www.youtube.com/watch?v=fKwhAVj5Feg Outdated. try CF-Auto-Root
Yes, I used this method and it did work for me.
5.After you are rooted, the first thing you wanna do is either install ROM manager (on play store). Open ROM manager. (Yes, give it superuser rights) and install the latest clockworkmod recovery, or use GooManager to get TWRP recovery, both work, but sometimes one is suggested for the installation of a specific ROM.
6.Now install busybox(also in play store)
7.You're all done!
If you've made it this far, kudos. Now you're gonna wanna get the app called titanium backup and do a full backup of your phone. Also boot into recovery (home+volume up then press power until it vibrates all while holding home+volume up buttons) do a backup through these menus. If your feeling like an over achiever and wanna be super safe then go ahead and back up to both your internal sdcard and your external sdcard. Also it now would be wise to back up your IMEI nv (basically your phone's identity), instructions for that can be found here (thanks to daxecutioner24)
Now you have reached a possible stopping point. Stop here and enjoy root privileges. Continue to read how to install a custom ROM.
Installing a custom ROM(operating system):
GooManager (on play store) is a pretty good directory for ROMs. And is a great place to download them and gapps. Now since not every ROM installs this way it is important to check the main page associated with that page to see if any special instructions are required.
But this is what you generally do.
http://forum.xda-developers.com/showthread.php?t=1946701
Roms:
Gapps can be found either on the ROM's page or through goo manager make sure the firmware versions match up (like android 4.1 and 4.1 jelly bean gapps)
For a pure android ROM I would suggest CyanogenMod 10.1 (the one I am currently on)
For an inverted stock ROM stuffed with fun features I would suggest DaRTHSTALKER S3
For a full list of roms and descriptions or if your just addicted to flashing, then here's the stockpile of almost every rom made for the galaxy s3 t999
http://forum.xda-developers.com/showthread.php?t=2088179
Backups are your friend. Especially through recovery mode. They have saved my butt several times when flashing a ROM went wrong.
And yes it is possible to sim unlock (make it so you can use it on any GSM network(such as at&t or US cellular)) your phone:
http://forum.xda-developers.com/showthread.php?t=2037390
Problem happened and you can no longer boot correctly? This is actually very common.
If you can boot into recovery:
Boot into recovery (Hold home button and volume up then press power till it vibrates all while holding volume up and home)
Restore backup (easiest method)
If that falls through then install a rom by following the instructions mentioned earlier.
If you can't boot into recovery or if those methods didn't work:
You must odin to stock. Follow the instructions here under using odin. Odin and Driver files are at the top of the post. Firmware files (what you put in PDA) are located here
If this didn't work, you may be out of luck, try again and if you are still stuck browse the forums and possible post something under Q and A if worst comes to worse, make sure to describe the entire situation including error messages you may have received so the problem can be pinpointed.
And finally, everyone be nice seeing as I am welcoming very new people to this thread.
Also if any suggestions to improve this post let me know.
Sent from my SGH-T999 using xda app-developers app
Good job
I like this post, would save those useless threads how do I root even though it's sticky all over. Also it would be really helpful if you include how to back up your IMEI nv maybe link the thread before they start flashing roms. This is probably one of the most important thing as when you start flashing stuff the IMEI might get lost and without that there is no phone. Everything else looks good.
Here's the link
http://forum.xda-developers.com/showthread.php?p=29514187
Sent from my SGH-T999 using xda app-developers app
daxecutioner24 said:
I like this post, would save those useless threads how do I root even though it's sticky all over. Also it would be really helpful if you include how to back up your IMEI nv maybe link the thread before they start flashing roms. This is probably one of the most important thing as when you start flashing stuff the IMEI might get lost and without that there is no phone. Everything else looks good.
Here's the link
http://forum.xda-developers.com/showthread.php?p=29514187
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Thank you!! I implemented that into my instructions. The goal of this thread is to be the thread that everyone can direct newbies here and not have a thousand different threads on the same thing. Also this way people can get their answers faster seeing as their questions will be in the same known place not in some obscure oddly-titled thread in the wrong section. Thanks!
ignorethis
will this work on my T-Mobile Galaxy S3 4.1.2?
Sent from my SGH-T999 using xda premium
Will this work on a 4.1.2 version and yes I do have the galaxy s3 t-999 T-Mobile please respond back asap thank you
Sent from my SGH-T999 using xda premium
It should work fine.
I suggest either CF AutoRoot or root66 (see firmware link in my sig) as the best ways too root. Imo.
Sent from my SGH-T999 using xda premium
Yes this works for that all you needed to do is click on the CF-Auto-Root method during the process and that would've been explained to you. I have used CF-Auto-Root atleast twice on two different galaxy s3's running jellybean 4.1.2 and it worked more than flawlessly
Sent from my SPH-L300 using xda app-developers app
Just fyi, though, CF Autoroot aparently does not work fot the new T999L.
Sent from my SGH-T999L using xda premium
Thanks for the info, make sure to read read read, about any changes you are going to do to your phone and always backup! Cheers!
Sent from my SGH-T999 using xda app-developers app
So after I root with this method can I still install a custom recovery and install Roms
Sent from my SCH-I605 using Tapatalk
timmyd463229 said:
So after I root with this method can I still install a custom recovery and install Roms
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
What android version are you running
I have a lg g flex tmobile. Can i install custom recovery and install roms?with this method?
raygozao said:
I have a lg g flex tmobile. Can i install custom recovery and install roms?with this method?
Click to expand...
Click to collapse
No
What about kernels? What exactly are they and how should you flash them (do you even need to)?
Can you still use Galaxy S3 motion activated features after flashing a custom ROM?
Squishy Crayons said:
What about kernels? What exactly are they and how should you flash them (do you even need to)?
Can you still use Galaxy S3 motion activated features after flashing a custom ROM?
Click to expand...
Click to collapse
kernel is when hardware need something like you bluetooth or need to adjust screen brightness it send a request to kernel bla bla bla.
you can only flash a kernel that is compatible to your rom by rebooting to recovery
Squishy Crayons said:
What about kernels? What exactly are they and how should you flash them (do you even need to)?
Can you still use Galaxy S3 motion activated features after flashing a custom ROM?
Click to expand...
Click to collapse
The way I understand it is the kernel is the bridge between your input and the devices output. Like the bridge between software and hardware... Sorta.. Ya you don't need to flash one sometimes custom kernels can add features and maybe improve GPS/battery life but I don't use custom kernels much. But that's just me some people are in to that stuff.
And yeah it just depends on the specific ROM for the specific features. I don't know if this is still a think its been a while since I've had some Samsung action but check our hyperdrive they had some good stuff going on when I used em.
Best bet is Google. Everything you could ever want to know about kernels and more! If you want to know about custom ones, read the OP's of the many available ones.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Hi. I have a new GS4 arriving in a few days and wanted to find out what needs to be done in order to use titanium backup and to do a nandroid.
I have read conflicting stories that it needs to be fully rooted, that it only needs the bootloader unlocked, and that the bootloader comes already unlocked on the T-Mobile version. Can someone please clarify for me? I don't need to flash a custom ROM or kernel or anything like that. The phone is for my son, so all I want is to be able to do full backups for him. Thanks.
Sent from my Nexus 7 using xda premium
You need to be rooted.
-Titanium BU will backup your app plus app data
-For a nandroid backup you'll need to have a custom recovery (ie CWM, TWRP)
I used this for root (it will install SU binary and app, plus stock recovery)
http://forum.xda-developers.com/showthread.php?t=2294005
To install custom recovery you can use Odin to flash the tar version or use ROM manager, GOO ect depending on the recovery you want.
Everything baseballfanz posted.
The M919 Bootloader comes Unlocked outta the box.
For years, I've used Titanium Backup with the Pro key. Excellentsand theGGold Standard. Does everything except pour your coffee
I also use My Backup Pro as a redundancy. I primarily use it to backup & restore my Call Logs, MMS, SMS, etc . It also backs up & restores Apps and Data. I set it to back on a schedule.
For a Custom Recovery, I use TWRP 2.5.0.2.
https://hotfile.com/dl/230303459/7ce1553/openrecovery-twrp-2.5.0.2-jfltexx.tar.html
If you decide to flash TWRP, don't flash with Goo Manager as it will install TWRP 2.6.0.0 of which known issues have been reported. TWRP 2.5.0.2 has very little issues if any. I've been using it for months without any issues. Working flawlessly. TWRP also gets installed with ODIN. If you need the steps, let me know and I'll post them.
For Rooting, I also use CF-AUTO-ROOT by Chainfire installed with ODIN. Easy as pie, or however that saying goes.
Any questions, post away
Thanks to both of you. I'm already familiar with Titanium as I use the pro version on my tmo MT4G, rooted with cwm and running cyanogen. At least for now. I'll be getting myself the GS4 as well soon. So I know the virtues of using TB.
However, my son wants to stick with stock and get ota updates and I want him to be able to remove bloatware, backup everything, and be able to tweak a few things like the whole YouTube link issue(if it's still an issue) so we're looking for a reasonable compromise.
I also currently use cwm ROM manager app, droidwall, and spare parts+ which I would like to put on his phone if they will work.
Biker1... When you say bootloader comes unlocked, that's for the tmo one we will be getting?
Sent from my Nexus 7 using xda premium
Yes the T-mobile version M919 come with an unlocked bootloader.
OK thx good to know. So what will be my first step when unboxing it in order to be able to use the aforementioned apps? I also have root explorer, mybackup root, s2e, and superuser on the MT4G if they will be useful on the GS4.
Sent from my Nexus 7 using xda premium
Sorraia3 said:
OK thx good to know. So what will be my first step when unboxing it in order to be able to use the aforementioned apps? I also have root explorer, mybackup root, s2e, and superuser on the MT4G if they will be useful on the GS4.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Charge the battery fully!
Make sure you have a good known working usb cable. You should as it will be a new one.
You wanna have enough juice to do your installations and if things run a little long, you don't wanna get stuck in the middle
You have those Rooted apps so you can root the S4 using:
CF-AUTO-ROOT by Chainfire using ODIN. I'll post a link soon.
http://forum.xda-developers.com/showthread.php?t=2294005
In addition, install a Custom Recovery. There are a few good ones.
Personally, I use TWRP 2.5.0.2
Don't use Goo Manager as that will install version 2.6.0.0 which has known issues. Been using 2.5.0.2 for months without issue, but you can use a custom recovery of your choice of course.
So:
Charge battery
Have a good usb cable
ODIN CF-AUTO-ROOT
Boot
ODIN Custom Recovery
Boot
Check you S4 to make sure you're good to go.
Make a Nandroid
Install your Apps
When ready, download and Flash a ROM and Enjoy
OK it seems he really wants a chance to play with it out of the box. So, once its charged, it's his for now. I'm wondering though, if the bootloader is unlocked already does that mean if we choose to root it at a later date it won't need to be wiped or will it still lose anything not on the sd card?
I already went through this with one son who got a new phone and ended up losing everything on the old one because he wouldn't let me root it from the start and back things up. But that phone would've required a full wipe when I unlocked the bootloader.
If this guy starts setting things up and installing apps and data and such, and then wants me to root it for TB, will he lose everything?
Sent from my Nexus 7 using xda premium
Sorraia3 said:
OK it seems he really wants a chance to play with it out of the box. So, once its charged, it's his for now. I'm wondering though, if the bootloader is unlocked already does that mean if we choose to root it at a later date it won't need to be wiped or will it still lose anything not on the sd card?
I already went through this with one son who got a new phone and ended up losing everything on the old one because he wouldn't let me root it from the start and back things up. But that phone would've required a full wipe when I unlocked the bootloader.
If this guy starts setting things up and installing apps and data and such, and then wants me to root it for TB, will he lose everything?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
No. You can Root ltr on and not lose anything.
Rooting via CF-AUTO-ROOT via ODIN will not cause you to have to Wipe anything.
He can always back up his files every once in a while to his pc, which you would do whether you're gonna Root or not, for that 'Just in case' moment. You know, Murphy's Law
I don't do that as often as I should.
If there's a time when you have to Wipe device memory, you'd just transfer the files to the pc and/or SD card.
If everything's good to go, and you're ready to Root, But things go wrong (Murphy's Law again) and you have to wipe Internal but you didn't save the files, you'll be outta luck, but that can happen anytime. So just back up once in a while. Better safe than sorry........
What will most likely happen:
- your son will dl files, games, etc.
- later on, days, weeks, months, he'll want to Root
- you'll ODIN CF-AUTO -ROOT by Chainfire and you'll be good to go.
- after installing Recovery and TiBu, you'll back up the data on the device,and that's it.
OK... That's exactly what I wanted to know. Thanks so much!
Alrighty so, Odin is the program I will use to access the adb commands on the pc, correct? And I get that from where?
And the cf root file? Is there a handy link? Steps to follow, a guide perhaps?
After that's done I assume I have to flash the recovery? I prefer cwm. Or is that part of the cf/odin process?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Sorraia3 said:
OK... That's exactly what I wanted to know. Thanks so much!
Alrighty so, Odin is the program I will use to access the adb commands on the pc, correct? And I get that from where?
And the cf root file? Is there a handy link? Steps to follow, a guide perhaps?
After that's done I assume I have to flash the recovery? I prefer cwm. Or is that part of the cf/odin process?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The CF-AUTO-ROOT link is posted previously. You install with ODIN.
I'll get you a link to ODIN so you can see what it's about.
You dl ODIN on your pc. You need drivers installed on your pc to recognize your S4.
You put tar files in the appropriate ODIN boxes
Tar files can be extracted from zip files.
You have to follow ODIN instructions exactly.
I'm briefly going through the basics as you really need to read the associated threads so you get an idea how the process works, then you'll probably have some questions which we can answer.
I'm not sure if CWM Recovery is installed via ODIN.
TWRP is. I use Version 2.5.0.2. But you can use CWM. There's a thread to show you howttoiinstall.
Root with CF-AUTO-ROOT via ODIN 3.07
Install Recovery (method depends on choice of Recovery)
Make a Nandroid backup
Then you can install, flash, etc. etc.....
Ok so he decided it was easy and quick enough to let me do it now. I'm following the thread instructions. I have the cf root and odin files. I run odin, check pda and pick the cf root file. I turn off phone, go into download mode and get the green android that says downloading do not turn off target. Now what?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Sorraia3 said:
Ok so he decided it was easy and quick enough to let me do it now. I'm following the thread instructions. I have the cf root and odin files. I run odin, check pda and pick the cf root file. I turn off phone, go into download mode and get the green android that says downloading do not turn off target. Now what?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Connect to pc usb port to:
- a known working port
- with a known working usb cable. Stock cable should be fine.
HOLD ON
WAIT!
Sorraia3 said:
Ok so he decided it was easy and quick enough to let me do it now. I'm following the thread instructions. I have the cf root and odin files. I run odin, check pda and pick the cf root file. I turn off phone, go into download mode and get the green android that says downloading do not turn off target. Now what?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
-Plug phone into USB cord attached to pc
-It might need to install drivers just wait till that's done
-Click on START button on Odin
Everything you need to know is posted in the CF, auto root post.
Post=2 http://forum.xda-developers.com/showthread.php?p=41797153
Nothing happens. Its just me and the little green android sitting here staring at each other.
Sent from my Nexus 7 using XDA Premium 4 mobile app
You're doing it backwards.
Open up ODIN
After you have s4 in dl mode
Plug into usb on pc
Wait for phone to be recognized via COM Port
THEN put tar files in PDA slot and check appropriate boxes
AsiI explained previously, learning the process is extremely important, and without being there, so to speak, things can go wrong, Fast....
It found the phone, said had the samsung drivers then nothing. It's not showing up under ID:COM and I still have my little green friend again.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Sorraia3 said:
It found the phone, said had the samsung drivers then nothing. It's not showing up under ID:COM and I still have my little green friend again.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Is the COM Port showing
COM 1 or another number and showing in Blue or Green
No
Its not the usb port, I don't think anyway. Mouse works in both.
Of course I am on a crappy vista laptop... Think I'd have better luck using the xp desktop?
Sent from my Nexus 7 using XDA Premium 4 mobile app
pm sent
- For android 4.3, there has been a lot of talk on the developer section, and from what I can see, the major bugs/issues have been fixed. Like the ROM not rebooting correctly. For those using 4.3, is this true?
- Also, from what I understand, this was due to the recoveries not being ready for 4.3, however CM released their own bare bone recovery to fix that issue. And then I've read that the TW recovery has also been updated to solve this problem.
-There is a lot of information in the development forums, but I have not seen any post on the steps on what to do in order to upgrade from 4.2 to 4.3.
-Right now I have CWM 5 recovery, because that's been working for me, and I never bothered changing (bad experience with trying to upgrade/change a recovery). Now from what I understand, I should be able to flash the newest touch recovery (via the goo app?), and then wipe and flash any 4.3 ROM. Any detail instructions would be a help, or if someone can create a tutorial post, that would be great.
Thanks in advance.
Here is a post I made yesterday about how I switched from 4.2 to 4.3
I hope it helps. I have been on hellybean 4.3 for two days and everything is running great.
http://forum.xda-developers.com/showpost.php?p=45021060&postcount=632
You could just install ROM Manager and update from there. It's super-easy (you need ROOT, but I presume you have that since you're flashing ROMs anyway). :good:
Sicily1918 said:
You could just install ROM Manager and update from there. It's super-easy (you need ROOT, but I presume you have that since you're flashing ROMs anyway). :good:
Click to expand...
Click to collapse
Many people have had bad experiences with ROM Manager. Especially in the Gingerbread days when its use was more common for this sort of thing.
Just my 2 cents.
monkeybuttons said:
Many people have had bad experiences with ROM Manager. Especially in the Gingerbread days when its use was more common for this sort of thing.
Just my 2 cents.
Click to expand...
Click to collapse
Interesting -- always been good to me, although I only use it to update the recovery; for the ROM itself I use Cyanogen's update util. I also use CWM, not TWRP, so there's that...
bobiscool07 said:
- For android 4.3, there has been a lot of talk on the developer section, and from what I can see, the major bugs/issues have been fixed. Like the ROM not rebooting correctly. For those using 4.3, is this true?
- Also, from what I understand, this was due to the recoveries not being ready for 4.3, however CM released their own bare bone recovery to fix that issue. And then I've read that the TW recovery has also been updated to solve this problem.
-There is a lot of information in the development forums, but I have not seen any post on the steps on what to do in order to upgrade from 4.2 to 4.3.
-Right now I have CWM 5 recovery, because that's been working for me, and I never bothered changing (bad experience with trying to upgrade/change a recovery). Now from what I understand, I should be able to flash the newest touch recovery (via the goo app?), and then wipe and flash any 4.3 ROM. Any detail instructions would be a help, or if someone can create a tutorial post, that would be great.
Thanks in advance.
Click to expand...
Click to collapse
Ur best and safest approach would be to DL Odin and the drivers for ur phone, then go to techerrata.com/browse/twrp2/hercules and DL twrp2.6.0.4, this is the 4.3 compatible version, then put ur device in DL mode and connect to odin, load the tar file in PDA and click start, 30 sec and u have the latest and greatest twrp recovery, now go get hellybean 4.3 or beanstalk4.3 and flash it, watch the beauty take place...
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
I updated my rom today like I usually do from the CMUpdater and it updated from 4.2 to 4.3. I didn't mean or want to do that, but it didn't tell me otherwise. Now I'm having issues left and right......the one time I don't back it up...grrr.
I'm having the most issues with Gapps. I downloaded the new one and installed it and Google Music and Youtube keeps crashing. I guess I'll be doing the full wipe now.
Did u update to 4 3 gapps? It won't do it automatically, even if u updated through goo it just looks at what version is installed and updates that version, 4.3 gapps can be found in any 4.3 thread
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
soupysoup said:
Ur best and safest approach would be to DL Odin and the drivers for ur phone, then go to techerrata.com/browse/twrp2/hercules and DL twrp2.6.0.4, this is the 4.3 compatible version, then put ur device in DL mode and connect to odin, load the tar file in PDA and click start, 30 sec and u have the latest and greatest twrp recovery, now go get hellybean 4.3 or beanstalk4.3 and flash it, watch the beauty take place...
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Why do some of those files say hercules, and others sgh-t989? Aren't they the same phone?