Related
Ok, I'm new here and a noob to the phone (only had it two days). I have been trying the SuperOneClick method, followed all directions and suggestions to deal with the looping issue, but no matter what I do or try I cannot get past the RATC loop (and yes, I've read hundreds of posts before asking). My cable and port are good, so I know that's not the issue. I have done the unplug, debug step, re-installed drivers, PDAnet, etc., but no go. The only thing I can think of is that I did a software update on the phone before I tried to root (thru the phone itself). Could that be the problem? Suggestions?? Thanks!
Never tried that method, always used the update.zip method.
Assuming you are on JH7:
1) Grab update below
2) Place on root of SD card
3) Reboot into recovery, either buttons or adb
4) Select reinstall packages
After the phone reboots, if it worked, you should see a superuser icon in your applications.
Good luck!
Thanks for the response.
I just wanted to let you know that I am super grateful for everyone's help! I ended up using the one click method and found a few other handy dandy files here. You guys rock! I'm a computer geek, but these phones mystify me for some reason - maybe it's because I'm so familiar with PC's and can do whatever I want with them. I'm so afraid of bricking my phone! Anyway, THANK YOU!!!!!!!!!!!
Katfish said:
I just wanted to let you know that I am super grateful for everyone's help! I ended up using the one click method and found a few other handy dandy files here. You guys rock! I'm a computer geek, but these phones mystify me for some reason - maybe it's because I'm so familiar with PC's and can do whatever I want with them. I'm so afraid of bricking my phone! Anyway, THANK YOU!!!!!!!!!!!
Click to expand...
Click to collapse
No worries. Most people here are friendly and helpful.
I also wouldn't worry too much about bricking. As long as you can get into download mode you can always use [STOCK ROM] Odin3 One-Click Downloader and Drivers CAPTIVATE ONLY to recover.
Worst part of flashing, restoring settings!
(Obvious Noob warning---) A friend helped me root my Thrill, install ClockworkMod Recovery, and then install CM7 on my Thrill. But I would like to try the LG GB release. Is it necessary to backtrack all the way back to stock to do this (i.e. reinstall the stock ROM, reinstall the stock recovery, unroot, etc.)?
My friend tried using the LG upgrade tool on his LG phone without going back to stock and ended up bricking it. He says that usually within a few days of release, a CMR compatible zip file (usually already rooted) appears here on XDA (I haven't seen it), which makes things easier (but obviously he didn't wait for it himself).
Will a zip be possible for the Thrill GB? (The file seems quite large (420MB), so I'm guessing there is a lot of media included.) Or should I just bite the bullet and backtrack?
Rick
Rick Tillery said:
(Obvious Noob warning---) A friend helped me root my Thrill, install ClockworkMod Recovery, and then install CM7 on my Thrill. But I would like to try the LG GB release. Is it necessary to backtrack all the way back to stock to do this (i.e. reinstall the stock ROM, reinstall the stock recovery, unroot, etc.)?
My friend tried using the LG upgrade tool on his LG phone without going back to stock and ended up bricking it. He says that usually within a few days of release, a CMR compatible zip file (usually already rooted) appears here on XDA (I haven't seen it), which makes things easier (but obviously he didn't wait for it himself).
Will a zip be possible for the Thrill GB? (The file seems quite large (420MB), so I'm guessing there is a lot of media included.) Or should I just bite the bullet and backtrack?
Rick
Click to expand...
Click to collapse
I'm assuming that the official update method was used.
Just use this method after downloading the update. No bricking.
SEE THREAD
The Dark Lestat said:
I'm assuming that the official update method was used.
Just use this method after downloading the update. No bricking.
SEE THREAD
Click to expand...
Click to collapse
Thank you for your help!
Rick
Trojan?
Sorry, but as a noob, I can't post in that other thread.
It seems that the shttp3.exe in the LG Flash Package triggers Symantec's trojan detection. Some searching seems to indicate (assuming I'm reading all the cryptic virus sites correctly) that there is something to this, although it seems that different scanners find different trojans/viruses (can't post the link, but Google for "shttp3.exe" and "trojan"). I also found that the web site for this utility is blocked at work, because it's a "malicious site."
Has anyone seen this? Has anyone been able to verify/refute this?
Rick
There is no virus, Lestat would never do that
Sent from my LG-P925 using XDA
Just my .02 .....Get rid of Symantec !! They are known for scaring people into a virus frenzy.. Yes, it is possible that it is seeing it as a potential virus because shttp is a workaround from the usual porting of windows ip services. ...
Correct me if i'm wrong somebody please !!
Get yourself Comodo and save your money...
Regards,
Dwayne
PS: somebody on here has written a script that just uses shttp temporarily while
your doing the flash procedure, and then reverts your host files back automatically after your done. You should try it.
dwaynedman said:
Just my .02 .....Get rid of Symantec !!
Click to expand...
Click to collapse
Symantec isn't really a choice on work PC.
Get yourself Comodo and save your money...
Click to expand...
Click to collapse
I'm sorry I can't give the link yet, but if you'll Google you'll see Comodo classifies shttp3.exe as "ApplicUnwnt.Win32.ServerWeb.SmallHTTP.~A" or "UnclassifiedMalware" (I guess depending on the version). A number of scanners find issues with shttp3.exe. I'm not saying it is infected, only that it is doing something suspicious.
Rick
Rick Tillery said:
Sorry, but as a noob, I can't post in that other thread.
It seems that the shttp3.exe in the LG Flash Package triggers Symantec's trojan detection. Some searching seems to indicate (assuming I'm reading all the cryptic virus sites correctly) that there is something to this, although it seems that different scanners find different trojans/viruses (can't post the link, but Google for "shttp3.exe" and "trojan"). I also found that the web site for this utility is blocked at work, because it's a "malicious site."
Has anyone seen this? Has anyone been able to verify/refute this?
Rick
Click to expand...
Click to collapse
shttp3.exe is in no way a virus. I've scanned with AVG and MalwareBytes Anti-Malware and they check out good.
Back to square one
OK, I seem to be stuck.
With paranoia in tow, I decided to take the long way back to stock. Unfortunately, when I tried to restore the backup of my stock image I made to SD card after installing CMR, the md5 checksum failed. I'm not sure what I can do about this.
So ok, I tried following the above link. The first step is to ensure the su binary is up-to-date. But when I tried this, I get a failure downloading the manifest. This is true for WiFi and HSPA+. I Googled and found a suggestion to delete the su binary. But that didn't help (I'm not sure how it would have helped anyway).
So back to the original question. Can I use the LG upgrade process to upgrade without going backwards (as you can see above, I can't) without bricking the phone? Can I start at step 3 in the link above and succeed?
Rick
The Dark Lestat said:
shttp3.exe is in no way a virus. I've scanned with AVG and MalwareBytes Anti-Malware and they check out good.
Click to expand...
Click to collapse
Thank you, sir. I hope it didn't seem accusing.
Rick
Rick Tillery said:
Thank you, sir. I hope it didn't seem accusing.
Rick
Click to expand...
Click to collapse
It's cool, my friend.
Sent from my Samsung Galaxy S II w/ CM9
Rick Tillery said:
OK, I seem to be stuck.
With paranoia in tow, I decided to take the long way back to stock. Unfortunately, when I tried to restore the backup of my stock image I made to SD card after installing CMR, the md5 checksum failed. I'm not sure what I can do about this.
So ok, I tried following the above link. The first step is to ensure the su binary is up-to-date. But when I tried this, I get a failure downloading the manifest. This is true for WiFi and HSPA+. I Googled and found a suggestion to delete the su binary. But that didn't help (I'm not sure how it would have helped anyway).
So back to the original question. Can I use the LG upgrade process to upgrade without going backwards (as you can see above, I can't) without bricking the phone? Can I start at step 3 in the link above and succeed?
Rick
Click to expand...
Click to collapse
Is it safe to ignore the su version update?
Short of this, can I override the MD5 checksum? I realize that image could be corrupt, but if I'm just going to replace it with the GB release, does that matter?
Rick
You should just put your phone in recovery mode and update through the tool
with your IMEI #. It will give you the latest update !
If you need some help on that I think Lestat or somebody has a write-up
on doing this.
Good luck,
Dwayne
dwaynedman said:
You should just put your phone in recovery mode and update through the tool
with your IMEI #. It will give you the latest update !
If you need some help on that I think Lestat or somebody has a write-up
on doing this.
Good luck,
Dwayne
Click to expand...
Click to collapse
Can you be a bit more specific?
1. By "recovery mode," do you mean into ClockworkMod Recovery, or I should revert to stock (I made a copy of it after I rooted the stock ROM, but before I installed CMR)?
2. By "the tool," do you mean the official LGMobile Software Update, or the LG Flash Package referenced in the link above?
3. By "latest update," do you mean the file directly from LG, or the copy (v20p) linked from the link above?
4. If the latter in both previous questions, which set of steps do I need to follow from the above link? Can I do only 3 (LG Flash Tool), or do I need to follow 1 (Recovery Manager), 2 (Returning to Stock), and 3?
My friend had a different LG phone, with ClockworkMod Recover and CM7 installed. He reverted the CM7 to stock, but did not replace CMR with the stock recovery. Then he used the official LG upgrade method and bricked his phone. I'm trying to avoid this.
Are you saying I don't have to worry about this on the LG Thrill 4G? Can I go straight from the current CMR+CM7 configuration to the LG GB release using the official LG process?
If you mean I should use a different process, can you point me to it? As I mentioned, I run into dead-ends using the method linked above. And I'm not even sure whether I should be doing steps 1, 2 and 3, or if I should just use step 3.
Any and all help is appreciated, but I guess I don't understand the shorthand you're using here, so if you could be a bit more specific, I wouldn't feel so lost.
Rick
Rick Tillery said:
Can you be a bit more specific?
1. By "recovery mode," do you mean into ClockworkMod Recovery, or I should revert to stock (I made a copy of it after I rooted the stock ROM, but before I installed CMR)?
2. By "the tool," do you mean the official LGMobile Software Update, or the LG Flash Package referenced in the link above?
3. By "latest update," do you mean the file directly from LG, or the copy (v20p) linked from the link above?
4. If the latter in both previous questions, which set of steps do I need to follow from the above link? Can I do only 3 (LG Flash Tool), or do I need to follow 1 (Recovery Manager), 2 (Returning to Stock), and 3?
My friend had a different LG phone, with ClockworkMod Recover and CM7 installed. He reverted the CM7 to stock, but did not replace CMR with the stock recovery. Then he used the official LG upgrade method and bricked his phone. I'm trying to avoid this.
Are you saying I don't have to worry about this on the LG Thrill 4G? Can I go straight from the current CMR+CM7 configuration to the LG GB release using the official LG process?
If you mean I should use a different process, can you point me to it? As I mentioned, I run into dead-ends using the method linked above. And I'm not even sure whether I should be doing steps 1, 2 and 3, or if I should just use step 3.
Any and all help is appreciated, but I guess I don't understand the shorthand you're using here, so if you could be a bit more specific, I wouldn't feel so lost.
Rick
Click to expand...
Click to collapse
Remove your battery and keep the phone unplugged
Launch the mobile updater tool
Hold the volume+ button plug the phone in and keep holding the volume+ till the computer downloads the drivers your phone is now in download mode
Once the phone is picked up go to customer support on the LG updater tool and click on recovery phone put your imie number in click check (make sure its the right model) an let the updater tool do its job. Once its done flashing launch into recovery volume- plus power plus 3D button do a complete wipe and factory reset and reboot your phone ... you'll lose cwm and root and be back to full stock
Sent from my LG-P925 using XDA
Bricked?
No joy. Following the steps, the upgrade stopped at 6%. Trying a number of times, it eventually forced me to exit the program (no more restarts). Rerunning the updater (and downloading the 420 MB image yet again on a VERY slow connection) I tried again and again, with different combinations of battery and plug order with power and volume buttons, but nothing worked. Checking elsewhere I found some issues had been reported with Windows Vista/7, so I tried on an XP machine. Now the "Start Updating" bar is red (it was always gray with W7). But now when I try to restore (or even update for that matter), it asks for my S/N (it never did that before) and then says it is "no longer able to upgrade." Reading around, it seems this is an indication of the device being bricked.
Rick
It sounds like you are very close to getting it working Rick.
My update did the same thing, looped over and over until it
finally kicked me out. Just plugging and unplugging the phone etc....
And when my update stuck at 6% the last time, i took my battery out and then in real quick and that seemed to work.
Does the phone still vibrate when you plug the usb cable into it while holding volume..? If it does then I highly doubt that your phone is bricked, just in a semi flashed state....No worries
Should Rick be trying to run LG Updater as administrator ? I didn't, but it might not hurt.
Regards & Luck,
Dwayne
http://forum.xda-developers.com/showthread.php?p=22417769
Have you tried this yet cause if you can get the LG logo to come up then you can reflash the phone and get it working send a pm to the dark lestat he may be able to team viewer you and help you out
Sent from my ****ty supported LG Thrill
dwaynedman said:
It sounds like you are very close to getting it working Rick.
Click to expand...
Click to collapse
I wouldn't have believed you early this morning, but now maybe...
My update did the same thing, looped over and over until it
finally kicked me out. Just plugging and unplugging the phone etc....
And when my update stuck at 6% the last time, i took my battery out and then in real quick and that seemed to work.
Click to expand...
Click to collapse
I tried a bunch of different combinations...none seemed to make the app happy. I finally punted Windows 7 and moved to an XP machine, only to get the "no longer able to update" message. At that point I assumed I was screwed (effectively bricked).
Does the phone still vibrate when you plug the usb cable into it while holding volume..? If it does then I highly doubt that your phone is bricked, just in a semi flashed state....No worries
Click to expand...
Click to collapse
It never really vibrated, but I was able to get back into CMR. Unfortunately NONE of my backups work at all. They all have MD5 checksum failures. I tried a trick I found online and got past that step, only to have it say a failure restoring /system. So much for CMR.
JReeher said:
http://forum.xda-developers.com/showthread.php?p=22417769
Have you tried this yet cause if you can get the LG logo to come up then you can reflash the phone and get it working send a pm to the dark lestat he may be able to team viewer you and help you out
Click to expand...
Click to collapse
Which step? As I mentioned above, I can't even get the first step of the first section (updating the su binary). And if I start at the 3rd section, Symantec prohibits me from using shttp3.exe (I tried to unquarantine it, but it gives a permission error, even as Administrator, when I try to run it), so I'll have to use a different machine.
I was able to reinstall the CM7 3/15 release, so that's something. I was going to restore the stock recovery backup I made, but even that doesn't seem to work. I'm having issue with backups :-(
Rick
i have never been able to restore a backup. i dont know why... but i have tried several times in several different instances.
---------- Post added at 11:56 AM ---------- Previous post was at 11:50 AM ----------
rick tillery, if you want to get your phone back to alive and well i'd suggest doing this:
http://forum.xda-developers.com/showthread.php?t=1558723&page=3
4th post i think
To start and get it out of the way:
DISCLAIMER: Typical legal stuff. Use this guide at your own risk. Author makes no claim as to guarantee, or warranty any software described in this document. The author cannot be held liable for any damages caused to your device or any other harm as a result of attempting to do anything described in this guide or anything that you choose to do with your device whatsoever. USE THIS GUIDE AT YOUR OWN RISK! MODIFY YOUR DEVICE COMPLETELY AT YOUR OWN RISK!
This is a basic guide for those wanting to root their brand new Galaxy S4 and get it to what I call general working condition. This is specifically written for and tested on the SPRINT Galaxy S4 (sph-L720) preinstalled with and running the MK2 firmware, and the links provided are for the sprint model listed. Although these basic steps may work on other galaxy S4 variants, the software specific for your model of phone will need to be downloaded. The relevant threads do link "main" threads where you can find information and downloads specific to your device model. Again, be careful.
what I call "general" working condition includes:
Root access (using CF-Auto-Root found here)
Advanced recovery (in this case using PhilZ CWM found here)
I know this is all basic stuff, however I have found that the guides so far are either overly complicated or too specific for a certain step. Don't misinterpret this as an attack or insult to the other authors of those guides. They are all very well written and great resources in their own right for their own purposes, and I had referenced many of them myself before taking the steps I chose to take. However I found that many of them are written for older stock ROM versions migrating to MK2 or again very specific for just rooting or just installing CWM. What I was looking for was what to do if you just bought an S4 a week ago preinstalled with the latest MK2 official ROM. I found that the procedure was far simpler than what I was worried about.
First, what you'll need:
samsung usb drivers, I got them directly from samsung's website and you should too. Download here.
When it comes to drivers I am far too paranoid about viruses and such to download them from anybody but the device manufacturer and I highly recommend sticking with official drivers only. Use downloaded drivers from other sources AT YOUR OWN RISK!
Odin (download here)
CF-Auto-Root (found here)
The next ones are optional and are required ONLY if you want a custom recovery installed. Currently I only have instructions for PhilZ CWM however at this point I think TWRP or any other custom recovery should flash just fine assuming they work well for your Galaxy S4.
(optional, required for custom roms, etc)PhilZ CWM found here).
---------------------------------------------------------------------------------
What I used (for reference): AMD A8 on Windows 8.1. Not sure if OS/System type has anything to do with it, but it is conceivable and is there for reference and possible troubleshooting. For example if this doesn't work as well on windows XP systems, we may want to know that. For now until a reason develops, assume this works well on all MODERN versions of windows (I will laugh if you fail on windows 9x/ME, seriously, laugh hard. Don't try to flash your phone on *old* OS's!)
Before you start, verify your phone is on MK2. I got my phone brand new with it preinstalled but if you got it from the store for example, it could've been sitting on a shelf for the last 3 months and not on MK2 yet. Again I wrote this guide and tested it using a phone with MK2 preinstalled and not having even seen a connection to a PC yet, root, custom flash, or anything outside of normal stock usage. This should theoretically work on a completely stock phone upgraded to MK2 however that's not what I tested with. Results may vary with variables changed. To verify your current build version, from your home screen: menu button > settings > more > about device. Look at both "software version" and "build number". if the last 3 characters in both are "MK2" then you're on the latest and greatest and can proceed. Otherwise do a system update and take your chances once your phone is finished doing its stock update. DO NOT TAKE AN OTA UPDATE IF YOUR PHONE HAS BEEN MODIFIED IN ANY WAY WITH ROOT, CUSTOM ROMS, RECOVERIES, OR ANYTHING FLASHED THAT DIDN'T COME OTA FROM SPRINT!!!!!! You may end up with a very expensive paperweight.
FIRST PART, ROOTING:
Now let's get to business. First thing, make sure you downloaded all the files listed above, including PhilZ CWM if you want a custom recovery. Most people who want root also want a custom recovery, and I like it for the backup capabilities but since it's not *absolutely* necessary I listed it as optional.
1. Install the samsung USB drivers. Your computer needs to know how to talk to your phone before we can do anything. I reccommend the official ones from the samsung site as I am incredibly leery of downloading device drivers from anywhere but the manufacturer for ANY hardware ever. Call me paranoid but that's why I don't end up with viruses and malware on my systems either I'm not saying that all of the non-samsung site downloads are bad, I'm sure others have reuploaded the official drivers to other mirrors but like I said I'm paranoid when it comes to "system modifying" type of files like drivers.
1a. reboot your computer. Yes I shoehorned this step in and didn't want to renumber everything. I didn't reboot because I was lazy but you probably should. Really, don't be lazy like me, even though it worked for me. Ok, be lazy, but at your own risk.
1b. Also, at this point if you're at all familiar with ADB and are so inclined (or paranoid) you may want to consider making a backup of your phone, however to be honest I'm not certain how well this works since ADB doesn't get root access by default. I'm sure there's a guide somewhere if you really want to make a backup of your original phone prior to flashing anything. I should do this step myself but I generally opt to wait until I get a custom recovery installed and make a nandriod backup that way because I'm lazy.
2. take a deep breath, it really isn't that scary. Take it from a guy who's now on his 4th rooted samsung device (T-Mobile Galaxy s4, Sprint Samsung Conquer, Sprint Galaxy S3, and now Sprint Galaxy S4). As long as you follow instructions CAREFULLY you should be just fine.
3. Extract the CF-Auto-Root zip file you downloaded. Again use windows explorer for two reasons: it handles zip files just fine, and it also DOESN'T handle .tar.* files so you don't run the risk of accidental double unzipping. Just copy the .tar.md5 file from the zip and place it somewhere you can find it, like your downloads folder. At this point you may want to consider moving all your downloaded and extracted files to a folder just for Galaxy S4 stuff, but that's a suggestion to help manage things easier.
4. Power off your phone if you haven't already. FULL power off, don't reboot. You may want to drop the battery to be absolutely certain, or wait another 15-20 seconds after you think it's off if you don't feel like it because you have an otterbox or something. Once you're 100% certain your phone is off, boot into download mode. This must be done *somewhat* carefully, read the following procedure completely before attempting. it's not hard but you can get frustrated by accidental aborts if you're unfamiliar with this. To boot into download mode: hold down the volume down button and press power until you feel the phone vibrate and the very second the screen lights up. RELEASE BOTH KEYS. You should see a screen come up with a warning about downloading a custom OS and asking you if you want to continue. Press Volume UP on your phone to continue. (volume down aborts and reboots the phone, now you see how this can be frustrating....). In some cases you may see the samsung logo first, but in my case it goes straight to the download screen. If you have problems going into download mode and see the samsung logo when the screen lights up instead, try holding volume down until you see a "recovery booting" or something similar message in tiny letters in the upper left corner of your screen with the samsung logo, then release volume down. DO NOT CONNECT YOUR PHONE TO YOUR COMPUTER YET!
5. Extract and open ODIN (I used odin V 3.07, it seems to work just fine). This should work fine in typical windows explorer. Just open the zip file, copy the ODIN v3.07 folder (not the exe file in that folder) to a directory of your choice. I just slapped it in my downloads folder with the zip because I'm lazy like that.
6. Now that ODIN is open, connect your phone. If you have already connected your phone prior to this, go back to step two and reread that part about following directions CAREFULLY
Assuming everything is going well, you should see a box that sasys ID:COM something light up like 0:[COM3] Don't be alarmed if it's not exactly the same com port, as long as there is one. The important part is that it has a valid com port, which will only happen if it detects your phone properly.
7. Click PDA and select the CF-Auto-Root...tar.md5 file you extracted. By default "auto reboot" and "F. Reset Time" are selected. Leave them checked. MAKE CERTAIN THAT Re-Partition IS NOT CHECKED!!!!!! Also, make sure everything else is unchecked besides PDA, auto reboot, and F. Reset time. Take a deep breath, then click "Start"
At this point your phone will reboot and do some automated stuff. You will see a big box light up in odin, ending up with "PASS!" if everything flashed well. Keep your phone connected until the phone reboots to your normal start screen. If your device goes as smoothly as mine did, it should flash the file, reboot the phone, do it's auto root process, reboot again, then go to the normal start screen. Essentially you end up with your phone exactly as you had it before, but with root. So root is *mostly* installed but we require one additional step to make sure things work smoothly.
8. open your app drawer, and then open the SuperSU app. It will load then it should inform you that KNOX is detected and ask you if you want to disable KNOX. Select yes. If you select NO and try to use root with KNOX enabled, root may not work well if at all, cause the earth to fall out of orbit, and god to punch your favorite cute furry animal. Also, you can disconnect your phone at this point, and should before continuing on.
Now you should be done. That's it. Really simple, You have root. Go forth and try not to destroy your phone with your newfound power, or read on and get a custom recovery installed and really do some stuff.
SECOND PART, INSTALLING PhilZ CWM RECOVERY:
1. READ ALL DIRECTIONS LISTED BELOW THOROUGHLY FIRST BEFORE ACTUALLY DOING ANYTHING!!! Also, this should only be done AFTER all the above steps are completed. Place phone into download mode as described in step 4 above. Quick reference: hold volume down, then press and hold power until the phone vibrates and screen lights up. Press volume up to continue.
2. Close ODIN from your previous flash if you haven't already. Once it's closed re-open it. This is in here to make sure we have a fresh ODIN window and aren't accidentally flashing root again. Once we have a nice and clean ODIN window, connect your phone. You should see the lovely COM box light up.
3. This process should look familiar to what we just did, since it basically is the same thing. This time click PDA and select the philz_touch...tar.md5 file. Also make sure "Auto Reboot" and "F. Reset time" as well as "PDA" are all checked. PDA should automatically get checked when you click the button and select a file. Make sure nothing else is checked ESPECIALLY MAKE SURE RE-PARTITION IS NOT CHECKED!!!
4. Click start. Again ODIN will send the file, and end up with "PASS!" in the big box above the COM:x box. Once it's done the phone will reboot. The original directions say it should go to recovery but my phone rebooted as normal. Disconnect your phone. To get to recovery at this point you should simply just need to power down the phone completely. Then press and hold Volume up and then press and hold power until you see "recovery booting" in tiny letters in the upper left side of the screen with the samsung logo. MAKE SURE you hold volume up before power as this makes booting into recovery MUCH easier. If you see a custom CWM looking recovery (if you have never seen cwm before, the "philz options" menu option in recovery should be a great clue that the flash was successful). If you see a charging icon come up when powering off your phone, disconnect it from your computer.
So now if everything went as smoothly as it did for me, you should have a rooted galaxy S4 with a custom recovery at the ready to help with installing fancy ROMS, firmwares, modems, mods, etc or simply making really good nandroid backups. I HIGHLY suggest that you boot into recovery and make a nandroid backup of your rom before you play around with it too much, preferably saving your backup to your external SD card. Also be sure to follow any additional instructions for any further customizations.
IMPORTANT NOTES: DO NOT take an OTA update once this is done. From what I have read it *may* brick your phone. Typically in the past on other devices it just fails and reboots but other devices didn't have things like KNOX for example. Just don't risk it. However this shouldn't be an issue as your phone should already have the latest MK2 firmware installed as of the date of this article, at least until the next update comes up. it is highly recommended that you disable the "system update" notification, and there are guides available here on XDA on how to do that. Maybe one day I will find and link them, or someone nice may find and link it for me in the replies ;p This will keep you from "accidentally" trying to install an OTA update and bricking your phone.
Any problems? You probably didn't follow a step properly, but it is possible that I forgot something or left something out. I thought I was pretty thorough however I am human and make mistakes. Just reply here and I will do my best to get back when I can, however I do have a full time job and a personal life so no guarantees on how soon replies will come.
THANKS goes to:
The entire XDA community, for all the help, resources, and everything else over the years despite my less patient moments.
Chainfire for his work on the CF-Auto-Root utility and instructions contained therein, which were included here and expanded upon. Also for his work on SuperSU which not only helps manage root access, but is nice enough to have the ability to disable KNOX automagically for us.
Phil3759 (aka PhilZ) for his work on his modified version of CWM for the galaxy S4 and other devices, and instructions (adapted for flashing the S4 specifically)
Spiricore for his reference material. I didn't use much, if any of it, here however it was very helpful in researching the galaxy S4 and rooting options. It is a great resource for those having issues flashing their phone for one reason or another. Some of the steps I *think* may be superfluous however if you REALLY want to make sure things will work, it should help. It's a nice alternative and can be found here.
daerragh for posting the download and info for ODIN, and possibly writing it unless I am misinformed. Otherwise thanks to the author of ODIN as well.
Unknownforce for more reference material, modem firmwares, kernels, and cool GS4 ROMS. Only researched his material for this article much like spiricores work, but worthy of a thanks nonetheless.
runwithme for more reference used for research in rooting for this article and my phone, and for the stock roms.
Anybody else I may have forgotten, or who have contributed to the works described above or used in this article.
reserved for future use
Another guide on how to root your S4!! Yeah!! And way to complicated again. Let me give you my simple guide and easiest method. This method also doesn't trip the knox warranty counter.
1. Turn on usb debugging on your phone.
2. Install Samsung USB drivers. If not already installed.
3. Connect your phone to your Windows PC. (No need to enter download mode, just connect as an MTP device.)
4. Run Safe Root .bat file found here & attached below(unzip the bat file from the zip file): http://www.droidviews.com/root-verizon-galaxy-s4-sch-i545-on-android-4-3-vruemk2/
(This file works on Sprint, Verizon, and AT&T so don't worry about the Verizon reference)
5. Follow instructions on screen and profit.
If you want a custom recovery installed, WHICH WILL TRIP THE KNOX WARRANTY FLAG, download goo manager from the play store and install TWRP.
Now that was easy!
cruise350 said:
Another guide on how to root your S4!! Yeah!! And way to complicated again.
Click to expand...
Click to collapse
Dude cut OP some slack, I got my s4 about a month ago and can honestly say that after reading all I can about rooting an out of box s4 with knox/4.3 and mk2, no mod has set a sticky in place to explain a simple way.
All I hear is all the prior MK2 people whining about how we should read.. Guess what, we do, it's not as clear cut as pre-knox, and I can promise you, if you recently came from another phone, you would be in our boat.
Ive read where your safe root gives all your private info to someone other than nsa. Oh, that sounds like something I want to do.. Is it true? No clue, but I'll pass to be safe
All the countless posts, threads would go away if a mod would simply put a sticky near qb77's, that way we wouldn't be posting and whining to drive you all nuts!
By the way, thank you to the OP for taking your time to do this, it's more than most would do
Sent from my SPH-L720 using Tapatalk
ibcenu said:
Dude cut OP some slack, I got my s4 about a month ago and can honestly say that after reading all I can about rooting an out of box s4 with knox/4.3 and mk2, no mod has set a sticky in place to explain a simple way.
All I hear is all the prior MK2 people whining about how we should read.. Guess what, we do, it's not as clear cut as pre-knox, and I can promise you, if you recently came from another phone, you would be in our boat.
Ive read where your safe root gives all your private info to someone other than nsa. Oh, that sounds like something I want to do.. Is it true? No clue, but I'll pass to be safe
All the countless posts, threads would go away if a mod would simply put a sticky near qb77's, that way we wouldn't be posting and whining to drive you all nuts!
By the way, thank you to the OP for taking your time to do this, it's more than most would do
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
Well now there are 4 threads on the first page of the general section on how to root MK2. Besides the fact that cf autoroot works on all versions of the software and is the reason why the mods haven't stickied another thread since qbkings method is still valid. Safe Root is not the Chinese method and is safe to use. And if this forum didn't need another simple thread that is actually way over complicated. As others have said, a little searching will turn up the answers. I don't mean to rain on anyone's parade but at least when I added my post, I offered a truly simple method to root opposed to the OP.
cruise350 said:
Well now there are 4 threads on the first page of the general section on how to root MK2. Besides the fact that cf autoroot works on all versions of the software
Click to expand...
Click to collapse
Many people have reported issues with chain fire method on newer preloaded 4.3 phones, so how can you say it works on all..
Others have reported safe root, not safe
It's just way to many threads, to many people reporting different issues with (after mk2) newer phones, to say that what's on the 1st page works for everyone
So my 02 cents worth, a sticky of after mk2 newer phones root method would be very helpful.... Ask anyone who has a newer preloaded phone
Sent from my SPH-L720 using Tapatalk
Saferoot and Kingo app are very easy to root. You literally click one button.
Sent from my SPH-L720 using Tapatalk
Safe root is easy, but can I flash a recovery simply by installing goo manager and flashing from inside the app? I've been flashing and rooting since the g1, and honestly this mk2 update is difficult to figure out. There are a lot of mixed answers out there. So I appreciate this post very much. Thank you sir.
Sent from my SPH-L720 using Tapatalk
Installing recovery will trip Knox.
Sent from my SPH-L720 using Tapatalk
princebabyeater said:
Safe root is easy, but can I flash a recovery simply by installing goo manager and flashing from inside the app? I've been flashing and rooting since the g1, and honestly this mk2 update is difficult to figure out. There are a lot of mixed answers out there. So I appreciate this post very much. Thank you sir.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
If this is correct, can I just do this to flash custom rom without having root first? Not really worried about knox, as surely there will be a fix..eventually?
slothicka said:
If this is correct, can I just do this to flash custom rom without having root first? Not really worried about knox, as surely there will be a fix..eventually?
Click to expand...
Click to collapse
Goo manager requires root.
Sent from my icrap 2 using Tapatalk HD
slothicka said:
If this is correct, can I just do this to flash custom rom without having root first? Not really worried about knox, as surely there will be a fix..eventually?
Click to expand...
Click to collapse
No, a custom recovery is still required to flash a different rom. In order to first flash a custom recovery, root is required.
Sent from my SPH-L720 using Tapatalk
So, bought my Note 3 when my contract was up on my Note 2.
Played with it for about a week, then decided to re-root like I did on my Note 2.
Downloaded the Kingo root, as it looked the simplest and then installed safestrap to eventually look at a rom.
Booted Safestrap into recovery, then set my phone next to me and started watching Role Models again. I must have layed on my phone weird or hit some buttons. Because only a Galaxy Note 3 screen is up with a big CUSTOM at the bottom.
Not too sure what I did, but I have tried almost every method of recovery to get the thing working again. So far, we are at hour 12 and I am at a complete loss. Every method either fails or says it worked, all to the same end. My phone will go to either the Download (Odin) screen, Recovery or the GN3 Logo.
Did I (literally) accidentally brick my phone? Or is this fixable?
Was your phone on 4.3 JB or 4.4.2 Latest AT&T KK? Which version of SS did you install? 3.72 or 3.71? Have you tried this http://forum.xda-developers.com/showthread.php?t=2559715 ? Or this
http://forum.xda-developers.com/showthread.php?t=2707555 ?
K-Alzwayed said:
Was your phone on 4.3 JB or 4.4.2 Latest AT&T KK? Which version of SS did you install? 3.72 or 3.71? Have you tried this http://forum.xda-developers.com/showthread.php?t=2559715 ? Or this
http://forum.xda-developers.com/showthread.php?t=2707555 ?
Click to expand...
Click to collapse
Phone was 4.3, Safestrap 3.72. The Hedimall option failed for me dozens of times so I gave up on that. I will try this other method in the morning.
burke9688 said:
Phone was 4.3, Safestrap 3.72. The Hedimall option failed for me dozens of times so I gave up on that. I will try this other method in the morning.
Click to expand...
Click to collapse
There is your problem. "4.3, Safestrap 3.72". it shoulda been 3.71 man. 3.72 is for KK. If the heimdall fails, then you need to reinstall the two packages (86x and 64x) ones and reboot your pc. Same exact thing happened to me and that fixed it. The other method will definitely work(or hopefully) ask op (@mutantblack). He's very helpful. Make sure you use 3.71 SS If you're on 4.3 JB.
Sent from my SM-N900A
K-Alzwayed said:
There is your problem. "4.3, Safestrap 3.72". it shoulda been 3.71 man. 3.72 is for KK. If the heimdall fails, then you need to reinstall the two packages (86x and 64x) ones and reboot your pc. Same exact thing happened to me and that fixed it. The other method will definitely work(or hopefully) ask op (@mutantblack). He's very helpful. Make sure you use 3.71 SS If you're on 4.3 JB.
Sent from my SM-N900A
Click to expand...
Click to collapse
I'm not sure what it means by load everything on to your external SD card. My computer doesn't detect my phone at all.
Use K-Alzawayed's first link. Follow the instructions explicitly. Use a card reader if you can't connect the phone to the computer, but first make sure you've installed the Samsung Driver on your computer.
Once you've done that you'll be on MJ5. Root the phone and turn the AT&T update app off. (You can use Link2SD to freeze it.) Then install Safestrap 3.71 and install some 4.3 ROMs. (Be careful - there are 4.3 and 4.4.2 apps here in the development thread.)
You'll probably also need to reset to MJ5 again (and allow the phone to keep updating) if you ever want the official 4.4.3 update. (I wouldn't take the 4.4.2 - unless you have a specific need for it - too many bugs for my taste, although my wife's N3 doesn't seem to have any problems.)
As far as the Custom lock, Xposed and the Wanam module will fix that - Wanam has a checkbox in the Security hacks section to set the phone back to show that it's stock (even though it's not).
Rukbat said:
Use K-Alzawayed's first link. Follow the instructions explicitly. Use a card reader if you can't connect the phone to the computer, but first make sure you've installed the Samsung Driver on your computer.
Once you've done that you'll be on MJ5. Root the phone and turn the AT&T update app off. (You can use Link2SD to freeze it.) Then install Safestrap 3.71 and install some 4.3 ROMs. (Be careful - there are 4.3 and 4.4.2 apps here in the development thread.)
You'll probably also need to reset to MJ5 again (and allow the phone to keep updating) if you ever want the official 4.4.3 update. (I wouldn't take the 4.4.2 - unless you have a specific need for it - too many bugs for my taste, although my wife's N3 doesn't seem to have any problems.)
As far as the Custom lock, Xposed and the Wanam module will fix that - Wanam has a checkbox in the Security hacks section to set the phone back to show that it's stock (even though it's not).
Click to expand...
Click to collapse
So I've gotta put my MicroSD inside the computer and load everything on there? Then back in phone and try again? I read about 10 pages of that thread and nobody covered it.
burke9688 said:
So I've gotta put my MicroSD inside the computer and load everything on there? Then back in phone and try again? I read about 10 pages of that thread and nobody covered it.
Click to expand...
Click to collapse
Yes, use a card reader to insert your external sd card in then plug into your computer then transfer whatever files you're asked to transfer to the SD card in that thread then after done, put your sd card back into your phone then go ahead with the process. I wish I had some time to chat with you on hangouts to walk you through it. I swear I'd get you back and running.
Sent from my SM-N900A
K-Alzwayed said:
Yes, use a card reader to insert your external sd card in then plug into your computer then transfer whatever files you're asked to transfer to the SD card in that thread then after done, put your sd card back into your phone then go ahead with the process. I wish I had some time to chat with you on hangouts to walk you through it. I swear I'd get you back and running.
Sent from my SM-N900A
Click to expand...
Click to collapse
Everything is done, I haven't posted until now because it's my girlfriend's 21st birthday. Everything is running, I flashed a few roms on separate rom files via that SafeStrap. Turns out I DID have the wrong version. I appreciate the help. I ended up running to Walmart and buying an 8gb Samsung card and loaded everythingo n there then back on to my phone. From there, everything started working perfectly. Though, it did completely wipe my 128gb sd card with almost 20gb of photos and videos from the last two years. But, that's fine. I didn't like half of that stuff anyways.
Thank you again for the help. I purchased the XDA premium app on my phone to try and give back a little to the community.
ALL IS GOOD!!! My Note 3 is ballin' again. I also bought 2 Hard Bricked phones (in the same situation as mine) on Craiglist today for 120 a pop. Got the both of them running and I'm flipping them for 600ea tomorrow. I'll hopefully be able to send some of that back to the website that gave me the means to fix broken phones.
Thank you again man, such simplicity in the fixing but it made all the difference.
burke9688 said:
Everything is done, I haven't posted until now because it's my girlfriend's 21st birthday. Everything is running, I flashed a few roms on separate rom files via that SafeStrap. Turns out I DID have the wrong version. I appreciate the help. I ended up running to Walmart and buying an 8gb Samsung card and loaded everythingo n there then back on to my phone. From there, everything started working perfectly. Though, it did completely wipe my 128gb sd card with almost 20gb of photos and videos from the last two years. But, that's fine. I didn't like half of that stuff anyways.
Thank you again for the help. I purchased the XDA premium app on my phone to try and give back a little to the community.
ALL IS GOOD!!! My Note 3 is ballin' again. I also bought 2 Hard Bricked phones (in the same situation as mine) on Craiglist today for 120 a pop. Got the both of them running and I'm flipping them for 600ea tomorrow. I'll hopefully be able to send some of that back to the website that gave me the means to fix broken phones.
Thank you again man, such simplicity in the fixing but it made all the difference.
Click to expand...
Click to collapse
Man, I'm so glad you're back and running. I know the feelings. It happened to me before and I got helped by @jerrycoffman45 and after swore and promised him that I'll always pass It on to however goes through the same. No problem at all. Again, I'm so glad you're good now. Keep slangin them note 3's off of Craiglist
Sent from my SM-N900A
Questions and help issues belong in Q&A and help sections
Thread moved
Thanks
FNSM
*edited* There was a question here about restoring from a bad brick from mixing up KK and JB files/roms. http://forum.xda-developers.com/showthread.php?t=2701062 saved my ass. Please ignore.
Hi all,
I searched the forums and I'm not finding any information pertaining to my situation (or I'm getting bogged down and skipping over things that would pertain to my situation). I do apologize, but I've been searching for a few hours now and I can't figure this out.
I just rooted my phone this evening. I was following the directions on the cyanogenmod website and things got confusing when it started talking about Clockworkmod and TWRP. Installed clockwork and rebooted into recovery and couldn't figure out how to flash. So I started looking at youtube vids and I saw people using TWRP. So I downloaded it from the play store and that's when things took a turn for the worse.
I opened up the app, I went to Install TWRP, picked my g2vzw and started Install Recovery. The app started downloading the open recovery file and then I got a popup saying "WARNING Ensure the partition listed below is the correct one for your device...etc. and at the bottom it had "/dev/block/platform/msm_sdcc.1/by-name/recovery". I didn't know how to verify and I figured it was right (my idiot mistake), so I hit yes.
After I did that, I looked at clockwork again and saw an option to Install ROM from SD Card. When I hit that, I saw all the directories on my phone, so I figured I could dump the cyanogenmod zip file onto my phone via Android File Transfer and go back into Clockwork and flash the file.
So when I did that the phone rebooted and I got the white text at the top of my screen with Secure Booting Error and then the phone shuts off and I have to press and hold the power button a good while until the phone boots back up.
So is happening as a result of what I did using TWRP? Is there anything I can do to fix this? I would really like to experience different ROMs. I hope all is not lost.
Like I said, I'm using a Mac and I haven't used Terminal in a while. The only reason I was able to root was because the root folder I downloaded had an executable for Terminal that did everything for me.
Thanks in advance for your help!
i did the same i attempted to use ez unlock to unlock bootloader and just twrp manager to flash twrp. after trying to reboot i get no text no logo just a black screen and when holding the buttons it vibrates with an occasional red light can turn on and off just a black screen though shows in pc as bulk drive....on windows.....please help i only had the thing for a couple hrs.
Have either of you tried returning to stock using the kdz or tot method? It might save you...
I'm taking about this:
http://forum.xda-developers.com/showthread.php?t=2448960
---------- Post added at 11:21 PM ---------- Previous post was at 11:18 PM ----------
Me personally, if it's not on xda, I don't use it (concerning root/recovery). Using ioroot25 for root and freedom tool for recovery (or autorec)...
njstein said:
Have either of you tried returning to stock using the kdz or tot method? It might save you...
I'm taking about this:
http://forum.xda-developers.com/showthread.php?t=2448960
---------- Post added at 11:21 PM ---------- Previous post was at 11:18 PM ----------
Me personally, if it's not on xda, I don't use it (concerning root/recovery). Using ioroot25 for root and freedom tool for recovery (or autorec)...
Click to expand...
Click to collapse
Thanks! I tried the KDZ method last night and it didn't work. I'm performing the TOT method as I type (waiting for the ROM to finish downloading). I'll let you know what happens.
shaka411 said:
Thanks! I tried the KDZ method last night and it didn't work. I'm performing the TOT method as I type (waiting for the ROM to finish downloading). I'll let you know what happens.
Click to expand...
Click to collapse
I could never get kdz to work either, aggravates me but the tot method did! Hopefully it works out for you...
njstein said:
I could never get kdz to work either, aggravates me but the tot method did! Hopefully it works out for you...
Click to expand...
Click to collapse
So I was using VMware and it stalled out during step 3 of the thread you linked. So frustrationg, I've been at this all day to end up getting no where. Now I have to get bootcamp installed and retry this whole thing. So much time to do something so little. Ugh.
shaka411 said:
So I was using VMware and it stalled out during step 3 of the thread you linked. So frustrationg, I've been at this all day to end up getting no where. Now I have to get bootcamp installed and retry this whole thing. So much time to do something so little. Ugh.
Click to expand...
Click to collapse
VMware?
njstein said:
VMware?
Click to expand...
Click to collapse
Yes, it's a virtual machine that allows me to use Windows on my Mac's desktop without having to partition my hard drive and use Boot Camp.
shaka411 said:
Yes, it's a virtual machine that allows me to use Windows on my Mac's desktop without having to partition my hard drive and use Boot Camp.
Click to expand...
Click to collapse
Ahhh, yes. Interesting. I'm assuming it'll work. Why not? But if you keep getting that same problem, try a Windows desktop.
njstein said:
Ahhh, yes. Interesting. I'm assuming it'll work. Why not? But if you keep getting that same problem, try a Windows desktop.
Click to expand...
Click to collapse
It worked!!! You are the man!!! Now that I have the phone back to normal and Windows up and running, I would very much like to root and install cyanogenmod the Right way, especially the boot loader part, having to do with the loki master (that I didn't do the first time around), would happen to know a good thread that will help me?
Again, thank you so much. I was nervous that I wouldn't be able to fix this. The TOT method was awesome.
shaka411 said:
It worked!!! You are the man!!! Now that I have the phone back to normal and Windows up and running, I would very much like to root and install cyanogenmod the Right way, especially the boot loader part, having to do with the loki master (that I didn't do the first time around), would happen to know a good thread that will help me?
Again, thank you so much. I was nervous that I wouldn't be able to fix this. The TOT method was awesome.
Click to expand...
Click to collapse
Ya, bro, this thread:
http://forum.xda-developers.com/showthread.php?p=51826092
The OP has a link for ioroot25 (which is the best way to root) and the freedom tool installs twrp. The steps are fairly straightforward but if you have questions, let me know! These are both for kitkat (so if you haven't, update) and you don't even have to worry about the bootloader. Updating to kk also erases some steps if you go the cm route. Also, do not use the "official" cm. It uses 4.2.2 base (crappy builds). Use JackpotCalvin's CM11, from what I've read it's top-notch.
Make sure you have ALL drivers for the phone installed before you start (including the adb drivers and debugging).
Glad you got it fixed, like I said, don't hesitate to ask if you have any doubts (easier to solve of you haven't done anything)!
As far as drivers, since I had to install them so that I could go back to stock, I should be good right?
ioroot25 is great, because it comes with "ioroot.tool" which is one click root for Macs.
njstein said:
Ya, bro, this thread:
http://forum.xda-developers.com/showthread.php?p=51826092
The OP has a link for ioroot25 (which is the best way to root) and the freedom tool installs twrp. The steps are fairly straightforward but if you have questions, let me know! These are both for kitkat (so if you haven't, update) and you don't even have to worry about the bootloader. Updating to kk also erases some steps if you go the cm route. Also, do not use the "official" cm. It uses 4.2.2 base (crappy builds). Use JackpotCalvin's CM11, from what I've read it's top-notch.
Make sure you have ALL drivers for the phone installed before you start (including the adb drivers and debugging).
Glad you got it fixed, like I said, don't hesitate to ask if you have any doubts (easier to solve of you haven't done anything)!
Click to expand...
Click to collapse
I guess I am already confused by the post. I know how to do the root. I can just run ioroot25, but then do I do the Recovery steps? And which link am I clicking the "One Click custom recovery TWRP for 12b ota. If your on 11a, do OTA first. Must have root also." or the "Then flash this in recovery if you wants TWRP 2.7: Thanks MindRocket"?
UPDATE
shaka411 said:
I guess I am already confused by the post. I know how to do the root. I can just run ioroot25, but then do I do the Recovery steps? And which link am I clicking the "One Click custom recovery TWRP for 12b ota. If your on 11a, do OTA first. Must have root also." or the "Then flash this in recovery if you wants TWRP 2.7: Thanks MindRocket"?
Click to expand...
Click to collapse
So I ran ioroot25 on Windows. Do I skip the "Recovery Section" and go straight to the "KITKAT 24A OTA FREEDOM" section? Sorry, I just want to be Really sure of what I'm doing this time, last time I went into this on my own thinking I knew what I was doing and we all know how that ended up.
Thanks!
shaka411 said:
So I ran ioroot25 on Windows. Do I skip the "Recovery Section" and go straight to the "KITKAT 24A OTA FREEDOM" section? Sorry, I just want to be Really sure of what I'm doing this time, last time I went into this on my own thinking I knew what I was doing and we all know how that ended up.
Thanks!
Click to expand...
Click to collapse
Root it with ioroot25, find the proper Autorec for vs980, install the app on your phone and run it to install recovery.
shaka411 said:
I guess I am already confused by the post. I know how to do the root. I can just run ioroot25, but then do I do the Recovery steps? And which link am I clicking the "One Click custom recovery TWRP for 12b ota. If your on 11a, do OTA first. Must have root also." or the "Then flash this in recovery if you wants TWRP 2.7: Thanks MindRocket"?
Click to expand...
Click to collapse
shaka411 said:
So I ran ioroot25 on Windows. Do I skip the "Recovery Section" and go straight to the "KITKAT 24A OTA FREEDOM" section? Sorry, I just want to be Really sure of what I'm doing this time, last time I went into this on my own thinking I knew what I was doing and we all know how that ended up.
Thanks!
Click to expand...
Click to collapse
Correct! Go to 24a ota freedom section. I've used it multiple times and never had an issue. It has the bat extension like ioroot25, just click and follow directions.
Autorec is another option (as mentioned) but I know nothing about it. As always, your choice!
njstein said:
Correct! Go to 24a ota freedom section. I've used it multiple times and never had an issue. It has the bat extension like ioroot25, just click and follow directions.
Autorec is another option (as mentioned) but I know nothing about it. As always, your choice!
Click to expand...
Click to collapse
So I hope I did this right. I started up the KitKat Freedom and pressed enter. And this what the command line said:
* server not running *
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Then my phone was automatically disconnected and then reconnected. Is that it? I figured the process would be longer.
shaka411 said:
So I hope I did this right. I started up the KitKat Freedom and pressed enter. And this what the command line said:
* server not running *
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Then my phone was automatically disconnected and then reconnected. Is that it? I figured the process would be longer.
Click to expand...
Click to collapse
Nevermind, it worked! I don't know what happened, maybe my USB Cable was loose or I didn't wait long enough, but I ran the program and waited and everything worked. I booted into recovery and Teamwin popped up (man we're really making progress!). So now I gotta get cyanogenmod. Should I just do a search for JackpotCalvin's, and once I find it how do I flash it?
shaka411 said:
Nevermind, it worked! I don't know what happened, maybe my USB Cable was loose or I didn't wait long enough, but I ran the program and waited and everything worked. I booted into recovery and Teamwin popped up (man we're really making progress!). So now I gotta get cyanogenmod. Should I just do a search for JackpotCalvin's, and once I find it how do I flash it?
Click to expand...
Click to collapse
So I did some searching and I found this post: http://forum.xda-developers.com/showthread.php?t=2702958
Step 5 makes me nervous (seems like we've come so far, I hate to screw up now), and he saying this is off of Jelly Bean. I thought CM11 was based off of KitKat.
Once again, never mind I already did step 5 by doing KitKat Freedom. Looks like all I really have to do is download Jackpot's build, transfer it to my phone and install using TWRP.
Just backed up everything. I'll let you know how it works out!
shaka411 said:
So I did some searching and I found this post: http://forum.xda-developers.com/showthread.php?t=2702958
Step 5 makes me nervous (seems like we've come so far, I hate to screw up now), and he saying this is off of Jelly Bean. I thought CM11 was based off of KitKat.
Once again, never mind I already did step 5 by doing KitKat Freedom. Looks like all I really have to do is download Jackpot's build, transfer it to my phone and install using TWRP.
Just backed up everything. I'll let you know how it works out!
Click to expand...
Click to collapse
My friend. Everything worked perfectly. I have Jackpot's build running and I got the Google Apps installed and running. Thank you so much for your help. That was quite an experience, I'm glad I had you leading every step of the way.