Related
I'm been searching the Nexus One Q&A section for an answer to my problems, but I couldn't find a solution. I'm running a stock version of 2.3.3 on my phone. It's never been rooted, and I have never rooted a device as well. I'm entirely new to this and have no idea what I'm doing. My device has no warranty but I'm still concerned about it. Again, I have no experience at all.
Also, I don't know if I would want to unlock the bootloader as I could lose everything. If there is a way to retain everything reliably (I don't know if those back-up applications are the most effective) that would be convenient.
So, can anyone help me root my virgin Nexus One?
Thanks for your time,
Tread Fox
Mybackup pro backs up apps and data. After you root you can use titanium backup. Also smsbackup and restore for your SMS :]
Alright, that's re-assuring. But what about actually rooting the phone?
Hmm I can't help with rooting because I have an Evo, just sharing some backup knowledge :/
You can use this threads wiki for the N1 and the stickies here:
http://www.nexusoneforum.net/forum/nexus-one-development-hacking/
You need to read several guides until you get a good idea of what you are doing and why.
Use the apps mentioned above to back up your phone info, once rooted you can do a complete and immediate phone backup of everything, like a full image pc backup.
If you do the one-click method, make sure it is for you OS, you will be limited in some things you can do, like fastboot commands and will be unrooted if you dl OTA's.
Read, Read, Read!!!
Before you flash a rom read the op page carefully and the last 20 pages for tips, info, issues etc.
Ken
This works for 2.3.3?
EDIT: So my only options are to unlock the bootloader or roll back? Which do you recommend?
You probably saw this in XDA wiki for N1:
http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Guides_&_Tutorials#Root
I would unlock, more options as you get more into flashing and you can't be unrooted by Google OTA's.
This is good guide for the S, but you can glean steps and maybe better understanding for the process. At the bottom in related posts is a root guide. I like the steps, but things like the fastboot and superuser may not be for the N1. However you can find them online. Just an easy to understand guide.
http://jaxov.com/2011/02/install-android-2-3-3-gingerbread-on-nexus-one-manually/
TreadFox said:
This works for 2.3.3?
EDIT: So my only options are to unlock the bootloader or roll back? Which do you recommend?
Click to expand...
Click to collapse
Sorry man, just got your message (phone died on me, and I've been playing with my other toys anyway...)
Yes, your options are to unlock the bootloader or roll back.
Both options will lose all date, so you need to backup either way.
My preference is to unlock the bootloader, but I can understand why people may not want to. Unlocking the bootloader can effect any warranty that's remaining on the phone (the phone has a 1 year warranty, no matter who owns it).
Thanks for all your help guys. Does anyone have a specific guide for rolling back? I don't need or want a custom rom, just setcpu...
Read my signature, execute PASSIMG method with FRG33. if it doesn't work (and sometimes it doesn't) - you're out of luck.
TreadFox said:
Thanks for all your help guys. Does anyone have a specific guide for rolling back? I don't need or want a custom rom, just setcpu...
Click to expand...
Click to collapse
This is how to go back to FRG33: http://forum.xda-developers.com/showpost.php?p=11745519&postcount=21
But if I were you, I would just unlock your bootloader. Makes life easier.
I'll unlock the bootloader. I saw a guide on the nexusoneforums on how to do this. But it's about a year old. Is there anything that's changed?
I'm sorry I'm being indecisive, I'm trying to take suggestions from anybody!
TreadFox said:
I'll unlock the bootloader. I saw a guide on the nexusoneforums on how to do this. But it's about a year old. Is there anything that's changed?
I'm sorry I'm being indecisive, I'm trying to take suggestions from anybody!
Click to expand...
Click to collapse
No, nothing has changed. You need to have the Android SDK set up properly. Then just boot into the bootloader by holding down the trackball while pushing the power button. Then open a command prompt in the directory where the fastboot.exe file is (probably C:\Program Files\Android\android-sdk-windows\tools) then just type: fastboot oem unlock
Follow this to set up the, it's easier (just the first post):
http://www.nexusoneforum.net/forum/...mple-sdk-setup-manual-root-guide-windows.html
Sent from my Nexus One using XDA Premium App
I don't know what I'm doing. This is confusing. When I hook up the phone to the pc it says its found new hardware. I'm running XP. What do I do? I think I'm going over my head with this. Also, how do I make sure mybackup will work? I don't want to lose my stuff!
TreadFox said:
I don't know what I'm doing. This is confusing. When I hook up the phone to the pc it says its found new hardware. I'm running XP. What do I do? I think I'm going over my head with this. Also, how do I make sure mybackup will work? I don't want to lose my stuff!
Click to expand...
Click to collapse
If you feel like you are in over your head, you probably are, and have not done enough reading. I just looked at danger-rat's post in the link he provided, and it seems quite straight forward, no? He even tells you how to install the drivers. "Step #3" under "To install the drivers" in the first post TELLS you that windows will detect new hardware and will ask you to install a driver. What seems to be the problem?
I did, and nothing happened. At all. I asked for it to download files from usb driver. Nothing happened at all. Is it something I'm doing wrong?
I have the SDK file on my desktop, I have all of the files inside that are needed. When the computer asks me to download the drivers, I re-direct to the usb driver folder located in the SDK which is located on my desktop. The computer claimed installation was successful, but nothing happened. When I try clicking the fastboot.exe in the tools file, it immediately forcecloses. Is it my pc? Is it the file? Is it the phone? I did read the material and so far nothing has helped.
TreadFox said:
I did, and nothing happened. At all. I asked for it to download files from usb driver. Nothing happened at all. Is it something I'm doing wrong?
I have the SDK file on my desktop, I have all of the files inside that are needed. When the computer asks me to download the drivers, I re-direct to the usb driver folder located in the SDK which is located on my desktop. The computer claimed installation was successful, but nothing happened. When I try clicking the fastboot.exe in the tools file, it immediately forcecloses. Is it my pc? Is it the file? Is it the phone? I did read the material and so far nothing has helped.
Click to expand...
Click to collapse
Well, after you have installed the driver that the computer asked you to install. That's just the driver needed to sync your file and stuff on your sd card. The other driver and adb setup is needed to actually access your phone.
So I asked for it to install the wrong files? What files do I install? Because from that guide it said point to usb driver. I'm only following the guide like you all asked, and nothing happened.
You don't launch fastboot by clicking on it windows.
Sent from my Nexus One using XDA App
Hello Everyone
I have noticed in a few threads there is alot of talk that people cannot root the new GB firmware from LG I fiddled with all the current versions out there and have now rooted them all. Thanks to Ilko and alot of stuffing around..
Firstly IM NOT RESPONSIBLE FOR BRICK OR VOID WARRANTY THIS IS INFORMATION ONLY Ok now the formalitys are over and done with.
If you already have the latest of Ilko's Upgrade kit good for you if not I suggest you get it now if you dont know where it is here is a link http://forum.xda-developers.com/showthread.php?t=1111771 now you have the neccessary tools to root your phone (theres also plenty of other awesome stuff in there too) we will start.
STEP 1. Go to the UPK file you created while installing Ilko's kit and Install all the drivers in the kit (even if your sure you have them it wont hurt to re-install) make sure your phone is unplugged at this time. Keep your UPK file open.
STEP 2. On your phone Goto Settings>Development and check USB Debugging
STEP 3. Now plug your phone into your computer DONOT mount USB Mass Storage
STEP 4. Go back to the UPK window and select SuperOneClick and open it.You may get a administrator rights popup make sure you allow or click ok whatever it says.
STEP 5. You need to make sure you do this in the right corner of the window of SOC (Superoneclick) there is a drop down that says exploit take it from auto and select gingerbreak because auto uses PSnueter and it has been patched in most cases and will not work.
STEP 6. Your phone should still be plugged in to your PC now is the good stuff make sure you read this carefully now cos you may brick your phone I havent done it personally but my brother has but he is pretty stupid.
STEP 7. Click ROOT in SOC and wait if it pops up with your device is already rooted would you like to continue click yes (this pops up if you have rooted your device before and also if theres a temp root on your device) now it will get to Rooting step 6 and hang maybe even it will stop responding at this point goto the UPK and open SRP and allow it to run your phone will reset and SOC will continue and say your phone is rooted do the test although it not necerssarry and it will confirm.
FINALE. Go to the apps and you should see Superuser (little skull thingy as the icon) Please thank me if I helped you also thank Ilko and Chains both great guys
Any questions please post I will reply and help as I can
Thanks Cuzzo-
Well if this method works, ur the big king from now on
-edit- And you are sure you dont have Redy's repack installed?
But it sounds quite much like the way it might have happend to me, but since I tried to many different things, I couldnt tell which combination it was...
Oh and whats SRP? and which version of SOC do u use?
N00BY0815 said:
Well if this method works, ur the big king from now on
Click to expand...
Click to collapse
LOL! just trying to help
N00BY0815 said:
-edit- And you are sure you dont have Redy's repack installed?
But it sounds quite much like the way it might have happend to me, but since I tried to many different things, I couldnt tell which combination it was...
Oh and whats SRP? and which version of SOC do u use?
Click to expand...
Click to collapse
SRP is a Shell root process in Ilko's Upgrade kit. I have used redy's repack but I have also flashed v20a and the Europe open v20n and tryed same method it works no problems.
The only reason you use the SRP is it refreshes the ADB and stops SOC from querying it at root step 6 so that the process continues Im using SOC v2.1.1
Could you share SRP.exe ? It is no more in UPK.
Cuzzo- said:
Hello Everyone
I have noticed in a few threads there is alot of talk that people cannot root the new GB firmware from LG I fiddled with all the current versions out there and have now rooted them all. Thanks to Ilko and alot of stuffing around..
Firstly IM NOT RESPONSIBLE FOR BRICK OR VOID WARRANTY THIS IS INFORMATION ONLY Ok now the formalitys are over and done with.
If you already have the latest of Ilko's Upgrade kit good for you if not I suggest you get it now if you dont know where it is here is a link http://forum.xda-developers.com/showthread.php?t=1111771 now you have the neccessary tools to root your phone (theres also plenty of other awesome stuff in there too) we will start.
STEP 1. Go to the UPK file you created while installing Ilko's kit and Install all the drivers in the kit (even if your sure you have them it wont hurt to re-install) make sure your phone is unplugged at this time. Keep your UPK file open.
STEP 2. On your phone Goto Settings>Development and check USB Debugging
STEP 3. Now plug your phone into your computer DONOT mount USB Mass Storage
STEP 4. Go back to the UPK window and select SuperOneClick and open it.You may get a administrator rights popup make sure you allow or click ok whatever it says.
STEP 5. You need to make sure you do this in the right corner of the window of SOC (Superoneclick) there is a drop down that says exploit take it from auto and select gingerbreak because auto uses PSnueter and it has been patched in most cases and will not work.
STEP 6. Your phone should still be plugged in to your PC now is the good stuff make sure you read this carefully now cos you may brick your phone I havent done it personally but my brother has but he is pretty stupid.
STEP 7. Click ROOT in SOC and wait if it pops up with your device is already rooted would you like to continue click yes (this pops up if you have rooted your device before and also if theres a temp root on your device) now it will get to Rooting step 6 and hang maybe even it will stop responding at this point goto the UPK and open SRP and allow it to run your phone will reset and SOC will continue and say your phone is rooted do the test although it not necerssarry and it will confirm.
FINALE. Go to the apps and you should see Superuser (little skull thingy as the icon) Please thank me if I helped you also thank Ilko and Chains both great guys
Any questions please post I will reply and help as I can
Thanks Cuzzo-
Click to expand...
Click to collapse
does anyone try ?
I could not find "gingerbreak" on SOC, just 'auto' 'psneuter' & 'zergrush' in the drop down.
WHY? do I get a wrong version, it's 2.3.3.
protozoa001 said:
I could not find "gingerbreak" on SOC, just 'auto' 'psneuter' & 'zergrush' in the drop down.
WHY? do I get a wrong version, it's 2.3.3.
Click to expand...
Click to collapse
I cannot find SRP in UPK! please help
In UPK 3.6 there is not SOC and SRP.
kdo_vi said:
In UPK 3.6 there is not SOC and SRP.
Click to expand...
Click to collapse
soc can download here:
http://shortfuse.org/?cat=4
but what is SRP ?
super root permission? No idea, have it appeared before?
can anyone upload srp?? i cannot find it anywhere! thanks
fail+ed! it is not feasible!
exe127 said:
fail+ed! it is not feasible!
Click to expand...
Click to collapse
have u tryed?
psneuter - patched
Gingerbreak - patched
zergRush - patched
So, what kind of exploit does SuperOneClick use?
wild_one_ro said:
have u tryed?
Click to expand...
Click to collapse
Yes, just try.
I am using super 1 click 2.3.3, because it hasn't the choice gingerbread to me, so I choose zergRush.
Then I start to root, everything is just follow the instruction till the SOC hangs.
Then, I open UPZ, there is no SPR exists, so I open BlackJack and it reboot my P970. After reboot, super1click back to normal but my p970 still unroot.
exe127 said:
Yes, just try.
I am using super 1 click 2.3.3, because it hasn't the choice gingerbread to me, so I choose zergRush.
Then I start to root, everything is just follow the instruction till the SOC hangs.
Then, I open UPZ, there is no SPR exists, so I open BlackJack and it reboot my P970. After reboot, super1click back to normal but my p970 still unroot.
Click to expand...
Click to collapse
maybe we need srp.exe!
Does op even verified? There's no SRP or SOC in the latest upgrade kit yet he asked us to dl the latest version.
Sent from my LG-P970 using XDA App
wild_one_ro said:
maybe we need srp.exe!
Click to expand...
Click to collapse
where can I find it, can you provide a think to me?
In other word, the pack UPZ is totally useless
exe127 said:
where can I find it, can you provide a think to me?
In other word, the pack UPZ is totally useless
Click to expand...
Click to collapse
if i had it, i'd share it
wild_one_ro said:
if i had it, i'd share it
Click to expand...
Click to collapse
thanks in advanced
lol... guys, SRP was my first release in order to follow the first method of getting root where SOC 1.9.5 was stuck. In fact, psneuter can't restart adb by itself, that's why SOC couldn't continue. Since it is totally obsolete, I don't recommend its using.
If you just need to kill adb server, create a new text file in an adb directory, paste the following then save it as KillADB.cmd :
Code:
@echo off
title Killing ADB server
echo Killing server
echo --------------
echo.
adb kill-server
echo.
echo.
timeout 5
run it to kill adb, so SOC will continue by running daemon again with its next command
(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
Hello fellow XDA'ers,
With the release of a stable CM9 candidate for the SGH-T849, I wanted to move away from the stock firmware and use a open-source/less-bloatware/pixiedust/unicornmagic firmware. Just like the fat kid squeezing his way into a candy emporium, I ran at the chance to install CM9.
I loaded the page that I had bookmarked for this very purpose:
*I can't post URLs since I am new to XDA, but it is an internal address*
Code:
wiki[dot]cyanogenmod[dot]com/wiki/Samsung_Galaxy_Tab_(GSM):_Full_Update_Guide
I followed the guide for Windows machines. I did not perform any pre-flashing backups, as all data was already backed-up. Furthermore, I'd like to fully format the internal and external SD cards for use with the tablet.
I installed all necessary drivers, and installed Technomancer's ClockworkMod onto the tablet through Heimdall (via download mode). The flash was deemed a success in the command prompt, and the tablet was rebooted by the computer. The blue bar zipped across the tab to show transfer of zImage.
However, after reboot, the tablet is stuck at the T-Mobile loading screen. I force shut down the device by holding the power button, and after shutdown unplug it from the computer.
I turn the tablet back on, and I get the same T-Mobile loading screen. By now, the tablet is looking at me like I'm stupid, which it's fully right in doing. I turn off the tablet by holding the power button, and the tablet turns off.
I try to see the battery level when plugged in via USB-AC power, but I am greeted with a battery icon that has a loading logo.
Before starting this adventure, I made sure the tablet was fully charged.
I can still enter into download mode when connected to the computer. I have only tried Heimdall, and have yet to read up on ODIN.
Relevant device information:
The device was rooted (SuperUser/BusyBox installed)
Model Number: SGH-T849
Firmware Version: 2.2
Baseband version: T849UVJJB
Kernel Version: 2.6.32.9
[email protected] #1
Build Number: FROYO.UVJJB
This is the first time that I have ever tried to flash a firmware onto an Android device. I have successfully flashed my two Nokia N8's with firmwares and have dealt with iPod touch 2Gs jailbreaks, so I am not *completely* computer incompetent. :silly:
I have tried to find the original firmware for the SGH-T849, but all the download links that I have tried to find are either dead or removed. Since only the zImage was replaced, I was hoping to simply re-flash with the factory zImage. Since I can't find the original factory firmware, I have yet to try this option.
I'm not sure what bricked state the tab is in. I'd like to hope it's soft-bricked, but that's probably not the case.
If I need to perform diagnostics on the device (or if any extra informaiton needs to be provided), I can edit this original posting with updated information. I have easy access to a Windows machine, but I may be able to get access to Ubuntu via disk image on another computer.
I don't want to be the jerk who states that "I solved it!" and leaves everyone in the dust: I'll post everything and anything that happens with this problem for future reference.
Other "stuck at loading screen posts" seem very similar to this, but solutions seem to be very divergent. Therefore, I am hoping for some clarity. Considering that the wiki post was designed for the SGH-T849, I think this thread should act as an appendix to the above wiki page for flashing this device.
Thanks,
willing_to_cooperate
Use overcome method.
T849 is the same as P1000 only with different modem.
http://www.teamovercome.net
Read the guide,
Missing pictures can be seen here.
http://forum.xda-developers.com/showthread.php?p=20974872
Follow the picture step by step.
missing files at
http://tabfirmware.com/2012/01/romk...e-7-series-v4-1-0-♫-overcome-kernel-v4-0-0-♫/
Sent from my GT-P1000 using xda app-developers app
dropbox *.png image link is 404'd
Hi Priyana,
The missing pictures provided through the Dropbox link at the thread provided is giving a 404 error. Knowing this, there aren't any pictures to follow.
Does anyone have a link to the pictures that *isn't* dead? Perhaps hosting on imgur or bayimg would sove this issue for future users.
I don't want to move on the Overcome method until I have the pictures.
Thanks,
willing_to_cooperate
priyana said:
Use overcome method.
T849 is the same as P1000 only with different modem.
http://www.teamovercome.net
Read the guide,
Missing pictures can be seen here.
http://forum.xda-developers.com/showthread.php?p=20974872
Follow the picture step by step.
missing files at
http://tabfirmware.com/2012/01/romk...e-7-series-v4-1-0-♫-overcome-kernel-v4-0-0-♫/
Sent from my GT-P1000 using xda app-developers app
Click to expand...
Click to collapse
Hmm.. others can see it, it shouldn't be a drop box.
Here I reattach
Sent from my GT-P1000 using xda app-developers app
Image too blurry
Hi priyana,
The picture looks really tiny with unreadable text. Specifically, it's only 315px wide.
Do you have a better resolution?
Thanks,
willing_to_cooperate
priyana said:
Hmm.. others can see it, it shouldn't be a drop box.
Here I reattach
Sent from my GT-P1000 using xda app-developers app
Click to expand...
Click to collapse
If you search overcome thread you should be able to find.
Nevertheless
http://forum.xda-developers.com/showpost.php?p=25971078&postcount=1316
Sent from my GT-P1000 using xda app-developers app
Hi priyana,
I followed the guide posted, and downloaded all the necessary files (some of the links in the original thread were missing).
Regardless, I downloaded similar files, and cross-checked the SHA-1 hash against what was listed on the Overcome website.
Flashed once (to Samsung factory reset), followed with a second flash to Overcome. Yahoo! :victory:
Thanks again for your guidance, even when I seemed to be a bit of an annoyance.
Again, for those looking to flashing a similar device, I should be holding the files on my computer (just in case). Just in case I need to return the favor.
Cheers!
willing_to_cooperate
priyana said:
If you search overcome thread you should be able to find.
Nevertheless
http://forum.xda-developers.com/showpost.php?p=25971078&postcount=1316
Sent from my GT-P1000 using xda app-developers app
Click to expand...
Click to collapse
Update on my GT-P1000/SGH-T849: T-Mobile to Overcome to CyanogenMod9/CM9
For reference:
Some people may be confused on how to move from Overcome to CyanogenMod.
The Overcome guide gives directions for wiping caches before installing the Overcome ROM. However, in the PDF guide, this is crossed out, as it is handled by a script in the Overcome ROM.
CM9 for the GT-P1000 doesn't seem to have that built in, which would cause a boot loop if the cache isn't cleared before installing CM9 for the GT-P1000. Since you can't pop the battery, force-shut-down the tablet by holding the power key until the tab shuts down.
After this, follow the Overcome guide to the point where the section of clearing caches is crossed-out. At this point, it's probably best to re-stock your tab (as priyana always suggests ad nauseum). Read between the crossed-out lines to clear caches, and install CM9 for the GT-P1000. It would be a good idea to install GApps at the same time using the same install procedure.
Hope this helps someone,
willing_to_cooperate
willing_to_cooperate
I'm going to give your username willing_to_cooperate the test
Unbelievably, I have *exactly to the letter* the same problem you had a few months ago. Like you I have a SGH-T849, and like you was trying to breathe some life into it by flashing it with Cyanogenmod. And sadly, like you I "soft bricked" it, so now all I get is a stuck T-Mobile screen on boot.
I've been trying to follow your lead and use Overcome + Odin to make things boot again, but I'm unable to get most of the files necessary. Anything that links to a multiupload.com address right now are broken links. Does anyone have other ways to access the files needed for the Overcome process?
If you have any insight on the specific step of getting the Tab out of its current bricked state, I'd much appreciate it.
Also, SGH-T849 has been mentioned as needing a "different modem". What/where is the correct file to use for that step?
Thanks,
Ben
It is right there in general section.
Or follow my signature.
Sent from my GT-P1000 using xda app-developers app
Completing a request.
Hello bklass!
I will do one better. In this case, I will deliver. As I type, the RAR package is uploading.
I will PM you a link to the file when I have uploaded the necessary package. The link that I will provide to your account will be valid for no more than 72 hours from the time I send you the link to the RAR package via PM, NOT from the time of this public post.
I do not want to post a public link, as people will blindly download it, hoping something works. Better to reply to this thread to get the required package. That way, there's a sense of order for this device.
The size of the package is ~1.23GB.
There are some extra files there, as I was trying to make a full copy of all possible files (to possibly help other users). Please don't be scared with the different modems, just make sure to PICK THE RIGHT MODEM.... or you may screw up your tablet (which you want to avoid).
There is a PDF guide of the steps required for using the different files. I would print this off/have it open on another computer, and read through it SEVERAL times to understand what you are doing. I am not saying it's hard, it is just very technically detailed. Make sure to have an afternoon free for the entire procedure. There is a point in the guide which I labelled as "start here," as I took a break, and didn't want to lose my specific spot. If you want to break up the procedure over two sessions, that'd be a good place to stop.
I am 99.99% sure that all the files are present in the RAR'd directory. However, if by some clerical error I forgot to include a specific file (which may be in another directory on my laptop), please let me know of the exact filename so it can be added to an updated archive I upload and send to interested users.
Simply referring to a post (that may be outdated, littered with dead links, and people thanking in-reply instead of properly using a button) does NOT help potential users/customers entering the Android family.
All I ask is that you publicly reply to this message (when you get the file and go through the steps) if: (1) the package sent to you is complete, and; (2) the package provided actually works.
If you leave this thread empty with no reply, you're not cooperating...which is against my spirit of "willing to cooperate".
If you would like to install CyanogenMod, there is a highlighted step with a red note, and a red box pointing to the red note. I did that, as it is a VERY important step (specifically, making sure you delete the cache to install CyanogenMod properly, as CM packages do not clear caches from previous installations automatically: it must be done manually by the user).
For reference, I am successful in running CyanogenMod 9.0 (stable).
Happy Flashing!
willing_to_cooperate
bklaas said:
willing_to_cooperate
I'm going to give your username willing_to_cooperate the test
Unbelievably, I have *exactly to the letter* the same problem you had a few months ago. Like you I have a SGH-T849, and like you was trying to breathe some life into it by flashing it with Cyanogenmod. And sadly, like you I "soft bricked" it, so now all I get is a stuck T-Mobile screen on boot.
I've been trying to follow your lead and use Overcome + Odin to make things boot again, but I'm unable to get most of the files necessary. Anything that links to a multiupload.com address right now are broken links. Does anyone have other ways to access the files needed for the Overcome process?
If you have any insight on the specific step of getting the Tab out of its current bricked state, I'd much appreciate it.
Also, SGH-T849 has been mentioned as needing a "different modem". What/where is the correct file to use for that step?
Thanks,
Ben
Click to expand...
Click to collapse
Thanks, got the files.
I will post back to the thread when I have gone through the overcome guide and report how it went. (next week at the earliest)
cheers
priyana said:
It is right there in general section.
Or follow my signature.
Sent from my GT-P1000 using xda app-developers app
Click to expand...
Click to collapse
I'm pleased to say that I've successfully unbricked and flashed the Overcome kernel and 4.1 ROM.
My next step is going all the way to CM9...I'm confused on a few aspects-- First, is it correct to assume that I need to flash to a CM9 kernel before flashing the CM9 ROM?
willing_to_cooperate: if that's the case, that might be the file you forgot to include in your excellent rar archive you sent my way. You really went the extra mile on the instructions btw.
Second, there was a mention earlier in the thread it would be a good idea to go back to stock before moving to CM9. If that's the case, why did I install the Overcome ROM in the first place? Was that a wasted step, considering my end goal was CM9?
cheers,
#!/ben
bklaas said:
Thanks, got the files.
I will post back to the thread when I have gone through the overcome guide and report how it went. (next week at the earliest)
cheers
Click to expand...
Click to collapse
bklaas said:
I'm pleased to say that I've successfully unbricked and flashed the Overcome kernel and 4.1 ROM.
My next step is going all the way to CM9...I'm confused on a few aspects-- First, is it correct to assume that I need to flash to a CM9 kernel before flashing the CM9 ROM?
willing_to_cooperate: if that's the case, that might be the file you forgot to include in your excellent rar archive you sent my way. You really went the extra mile on the instructions btw.
Second, there was a mention earlier in the thread it would be a good idea to go back to stock before moving to CM9. If that's the case, why did I install the Overcome ROM in the first place? Was that a wasted step, considering my end goal was CM9?
cheers,
#!/ben
Click to expand...
Click to collapse
The guide was overcome, that is why overcome ROM was flashed using CWM.
But, actually you don't need that.
You only need to Odin flash the Overcome kernel.
That is it. You don't even need to wait for the robotic voice to complete its thing.
Just force it off.
Then boot to recovery.
use that recovery to flash CM9, twice.
You are kind of right, you need CM9 kernel, but it is done by the first flash
(spot the CWM is different from overcome one, after first flash).
Second flash will install CM9.
Then you flash gapps and reboot.
If you reboot after CM9 without gapps, you can still flash gapps later, but you won't get the setup wizard (the one that ask you to set up wifi, put gmail id, choose to use gmail to backup, bla bla)
So just remember, in the future, restock means Odin flash GB-stock-safe.
Then you will want to Odin flash the Overcome kernel because that is the easiest way to install CWM.
From there it is flashing from CWM.
Full success thanks to this thread
I am 100% up and running with CM9 on my SGH-T849 (T-Mobile branded original 7" Galaxy Tab), thanks to the excellent help from willing_to_cooperate and priyana.
FYI, 2 biggest roadblocks to getting this completed were:
1. Inability to find the necessary files because of broken links, downloads found on sites blocked as malware, etc. [SOLVED] by willing_to_cooperate and him putting together an awesome .rar archive of all necessary files, including a critical annotation in the Overcome guide PDF that told me about the necessary step of wiping cache when flashing CM9
2. Inability to find well-written or even correct information about what to do. As a gadget hobbyist, I have been doing Linux stuff for almost a decade. That community tends to be very sharp and focused to task. The android mod community is quite a bit different I'm finding out-- for every thread with good discussion points there are 25 that say "How do I tweak teh andrd better so I can show everyone how kewl I am". I will concede that this just comes with the territory. Someone tweaking their stock T-mobile phone is quite a bit different than someone installing Ubuntu on a laptop. Nevertheless, [SOLVED] again by willing_to_cooperate and priyana on this thread. Kudos to both of you.
For the record, though I jumped through a few more hoops than was required, these were the steps from getting to "soft-bricked" Galaxy Tab SGH-T849 to fully running CM9 w/gapps.
1. Follow Overcome guide documentation to restock stable Gingerbread
2. Follow Overcome guide to flash Overcome kernel 4.0.0 using Odin
3. Boot and connect Tab as USB storage device
4. Copy CM9 and gapps zip files to mounted Tab (which is the internal SD card)
5. Boot into recovery mode (clockwork mod, which was installed in step 2)
6. Wipe flash/cache through Clockwork Mod
7. Install CM9 and gapps through Clockwork Mod
8. Boot and rejoice in the CM9 awesomeness
cheers,
#!/ben
For the record (as you already have CM9 working on your tablet), I did not include CyanogenMod (CM) releases in the package that I sent to you.
The reason I didn't do that is that the CM ROMs are always updating, and it is easier for the user to find the correct and safest location to download the plain CM ROM files.
For those wondering what address I'm referring to:
http://get.cm/?device=p1 "p1" is the code name for the device.
To clarify, the package that I sent is what I used to get my tablet out of stock (T-Mobile) via Overcome, then updating to CM9.0.
You can select stable, release candidate (RC) or nightly from the menu on the left-hand side. If you are just starting, I would strongly suggest you use the most recent stable ROM for your device (that way, you minimize the risk of using a ROM that may still have bugs).
Good to hear of success relating to your device.
To other people that need the package that I sent to bklass (as you cannot find all the files required due to possible broken links that may happen now or in the future), please PM me and refer to this thread.
I will try to re-write the Overcome guide on a long-term "to-do list" that will clearly delimit what point is restocking, and what point is flashing with another ROM. That, or updating the relevant CM wiki page with proper steps. That way, there is no need to search for a PDF or picture file with relevant steps, just refer to the proper steps in the CM wiki link.
When I rewrite the guide, I'll make sure to include files that are required, with relevant MD5 hashes appended.
Regards,
willing_to_cooperate.
bklaas said:
I'm pleased to say that I've successfully unbricked and flashed the Overcome kernel and 4.1 ROM.
My next step is going all the way to CM9...I'm confused on a few aspects-- First, is it correct to assume that I need to flash to a CM9 kernel before flashing the CM9 ROM?
willing_to_cooperate: if that's the case, that might be the file you forgot to include in your excellent rar archive you sent my way. You really went the extra mile on the instructions btw.
Second, there was a mention earlier in the thread it would be a good idea to go back to stock before moving to CM9. If that's the case, why did I install the Overcome ROM in the first place? Was that a wasted step, considering my end goal was CM9?
cheers,
#!/ben
Click to expand...
Click to collapse
> I will do one better. In this case, I will deliver. As I type, the RAR package is uploading.
Hi! Do you still have that RAR file? I followed the steps at the cyanogenmod site and ended up with the same t-mobile image.
I can still connect to my phone typing "adb shell" on the terminal, and execute commands there, but I do not know how to bring it back to life.
Thanks!
If you're using terminology like shell, I'll assume your on a *nix system.
In short, the files are Windows-based, and should have all components.
PM me and I'll send you the link, as I don't want the RAR file publicly posted (I have limited hosting space via Drop box that I don't want slammed by the XDA community).
Cheers!
willing_to_cooperate
Sent from my GT-P1000 using xda app-developers app
I'm having a difficult time getting mine off the boot screen. Odin doesn't recognize it thus the Overcome steps don't work. Any thoughts?
Thanks,
Holy
Holyloktar said:
I'm having a difficult time getting mine off the boot screen. Odin doesn't recognize it thus the Overcome steps don't work. Any thoughts?
Thanks,
Holy
Click to expand...
Click to collapse
Hi Holykotar,
Hmm... Let me troubleshoot. I'll be approaching your problem from a "cross-examination/troubleshooting" perspective. Please answer all the questions below:
1) Are you having a bootloop? That is, tablet boots up, goes to a logo, then repeats until you get bored?
If you can, it may be wise to enter recovery, delete all caches, and re-start the tablet.
The first time I tried going through the steps, I had a bootloop as the caches were incompatible with the ROM. This may be your case, but it is difficult to determine with the limited information that you have provided me.
Therefore, as stated, I would start off by going into recovery, and deleting all caches. If that works, let me know.
2) What version of ODIN are you using?
Later versions may be incompatible. I used Odin3 v1.7 with success on Windows 7 Ultimate. Also, it could be an issue of not starting ODIN with administrative privileges.
3) What OS are you using?
This may seem silly, but good information for people reading this thread. As stated, I used Windows 7 Ultimate.
4) Have you installed the required computer drivers so the tablet is successfully recognized by the computer?
This would fix some interface issues. If the software (ODIN) can't communicate with the tablet (GT-P1000), then it may be a driver issue.
5) What guide are you using? Better yet, do you have all the required files?
If you are using the guide entitled: "The Overcome Experience" (I have it as a PDF), then there shouldn't be any problems. However, if you are having issues with a proper guide, PM me and I will send you a link to download all necessary files to flash the GT-P1000 (T-Mobile version) without any problems. I request that you PM me for the files, as I don't want the download link distributed (as my bandwidth is fast but limited).
Happy Flashing :laugh:
willing_to_cooperate
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