Related
DO NOT FLASH THE VOODOO LAGFIX WITH THIS ROM!
Download: http://www.multiupload.com/SXWLND5AKI
That file contains ODIN, the 512 pit file, the original firmware and the new leaked firmware!
To use ODIN you need the samsung drivers installed. You can get them here: http://forum.xda-developers.com/showthread.php?t=728929
How to flash the update using odin.
Power phone off
Plug USB to computer but not phone
Open Odin.exe
Plug the USB into your phone while holding down the volume keys (Don't touch power!)
One of the fields will turn yellow in ODIN
Click PIT and select the 512.pit file
Click PDA and select the Update.tar file if you want to try the leaked rom or Original.tar if you want the stock rom
Click start
Odin will do it's thing and then the phone should reboot. It will take a few minutes for it to reboot the first time.
DO NOT CLICK RE-PARTITION WHEN USING Update.tar! The leaked rom does not include dbdata.rfs
If you already did that, you will need to flash back to the original rom included in the download first and then flash this new one... The original rom does include dbdata.rfs which will will repartition the phone correctly.
As always, I am not responsible for anything you do... ever...
P.S. Please don't trash talk in this thread.
Nandroid of a clean install: http://www.multiupload.com/FLX6P17XDP
I flashed back to the original rom and tried to use this nandroid to upgrade and it didn't work. Just sat at the Vibrant screen.
What it is:
Leaked rom from samfirmware.com
Android 2.1 (Eclair)
Good things:
New battery full notification
HD Camcorder (Same thing just new name)
Media Hub
Samsung Task Manager (Also available when holding home)
New Swype with the audio input!
Old Root method still works (verified)
Phone is usable during media scanning
YouTube can be set to HD
Cosmetic updates to music player
New and re-arranged browser settings
I tested GPS while driving, at 3 destinations in 3 different cities and all of them locked on within seconds! I also rebooted and tested at each location just to make sure and it grabbed immediately. I did notice while testing at home it was much faster in the Maps app then most other apps that use GPS.
Bad Things:
Can't flash JAC's kernel without modifications
Many apps missing from market There is a fix below...
Slide to unlock screen takes a way bigger slide
The lag is coming back. I'm going to pull the apps I like and go back to the stock rom worth voodoo.
Linpack (1st run) 8.13
Quadrant (1st run) 894
The only thing I DON'T like about this rom is that apps are missing from market.
I have tested on 2 different phones. 1 was normal with lagfixes, etc installed and after flashing there were weird problems with the camcorder, etc. We then flashed it back to stock using the old samsung release in odin and flashed the update, now everything is working great. You might want to revert your lagfixes or something before running this. Maybe it's because it doesn't include dbdata.rfs?
TO FIX THE MARKET:
Use something like Root Explorer to mount the system as r/w and then edit /system/build.prop
The 2 lines to update currently show
ro.build.description=SGH-T959-user 2.1-update1 ECLAIR UVJI2 release-keys
ro.build.fingerprint=Samsung/SGH-T959/SGH-T959/SGH-T959:2.1-update1/ECLAIR/UVJI2:user/release-keys
Click to expand...
Click to collapse
Update UVJI2 to UVJFD in both lines like below
ro.build.description=SGH-T959-user 2.1-update1 ECLAIR UVJFD release-keys
ro.build.fingerprint=Samsung/SGH-T959/SGH-T959/SGH-T959:2.1-update1/ECLAIR/UVJFD:user/release-keys
Click to expand...
Click to collapse
After you download a few apps the market will refresh and it will work again.
awesome!
I'll bet the gps fix also! this is a nice base before voodoo. thanks!
I'm going to do some tests.
Simple question...
Does ODIN work with Mac, or is it still just PC?
As far as I know, only on PC.
Which means I have to wait til I'm at work monday unless an awesome person makes a version we can flash from recovery.
Damn! Ok, I'll just bust out my PC laptop for this one. Can someone post a link to which ver of ODIN I need to downlown for this? Or is it already added in the link above?
Thanks!
Anyone have a mirror of the download? Also.. what is the leak? is it Froyo 2.2?
I have added a link to multiupload which should distribute it to several sites very quickly.
does this odin works for new hardware locked vibrants? i have mine stuck at triangle screen . and i have tried all the combinations nothing works. what do i do
flameinthefire said:
does this odin works for new hardware locked vibrants? i have mine stuck at triangle screen . and i have tried all the combinations nothing works. what do i do
Click to expand...
Click to collapse
This is the same odin. Try following my instructions. If they don't work for you, you are either doing them wrong or are out of luck.
youneek said:
This is the same odin. Try following my instructions. If they don't work for you, you are either doing them wrong or are out of luck.
Click to expand...
Click to collapse
i guess i m out of luck.
Has anyone with root and lag fix tried this?
Sent from my SGH-T959 using XDA App
I just did this and it worked flawless i then used the multi tool to reroot and it worked but when i tried to change the boot screen with multi tool it aborted for some reason so i then flashed new boot screen thru cw and work perfect .... now to explore and see whats new...
youneek said:
What it is:
Leaked rom from samfirmware.com
Android 2.1 (Eclair)
Good things:
New battery full notification
HD Camcorder (Same thing just new name)
Media Hub
Samsung Task Manager
New Swype with the audio input!
Old Root method still works (verified)
Phone is usable during media scanning
Bad Things:
Still not lag free but better!
Many apps missing from market
Linpack (1st run) 8.13
Quadrant (1st run) 894
The only thing I really like about this rom is the new Swype. I haven't been able to test GPS yet...
Click to expand...
Click to collapse
Add to the good things that the Youtube app now allows you to specify HD as the preferred stream method...Samsung Media Hub working as well....though I could care less about that..
quick question boys and girls...
i'm running Win7 x64. i have read on another site that ODIN doesn't play well with x64 environments. is that why it's not detecting my phone on the com channel?
It's Fine
I was Rooted, highly modded, JAC's OCv4 lag fix ext4. many UI mods etc. everything worked flawless and all my mods are going back on without a hitch
luckyduck69 said:
quick question boys and girls...
i'm running Win7 x64. i have read on another site that ODIN doesn't play well with x64 environments. is that why it's not detecting my phone on the com channel?
Click to expand...
Click to collapse
Yeah probably. I dual booted 32-bit just so I could play with my phones without problems (I also have an N900)
Sent from my SGH-T959 using XDA App
gravis86 said:
Yeah probably. I dual booted 32-bit just so I could play with my phones without problems (I also have an N900)
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Where can I find what bit my pc is?
luckyduck69 said:
quick question boys and girls...
i'm running Win7 x64. i have read on another site that ODIN doesn't play well with x64 environments. is that why it's not detecting my phone on the com channel?
Click to expand...
Click to collapse
Wrong. Windows 7 x64 + Odin works fine for me, they're probably using the WRONG drivers.
I have solved this problem for me I am not sure if this will work for everyone.
I have used pieces from other users so I can't take credit for anything, just helping the community.
I realize there are others out there that claim to do the same thing however after spending 1/2 a day doing it those ways, none worked till I did this, that is why i posted this guide, for people coming from bionix 1.31 or similar roms and using one of those guides causing a soft brick issue, this is what flashed mine back to 2.2 official firmware from a bricked state.
this will also work to flash a phone back to stock to send back for warranty if it is rooted and voodoo'ed.
Please follow this guide exactly. If a step doesn't work try again from the start then do not continue as this won't work for you.
1. your phone looks like this
Uploaded with ImageShack.us
2. in this mode your phone will be seen by this version of odin here: http://forum.xda-developers.com/attachment.php?attachmentid=478059&d=1293895557
3. dl and install the odin program works on win 7 64 bit no issues.
4. dl this ka6 update (this is a factory flash for odin) http://www.multiupload.com/GZT6ZYFX46
5. extract the ka6 zip to your desktop and rename the (.tar.mp5) file to (.tar) change the extension only DO NOT CHANGE THE NAME! < this is the trick it will not flash any other way once this is done it will flash right through.
6. open the odin program.
7. connect the phone get it to the screen like the pic in step 1.
8. the 1st ID:com box will turn yellow and have some id numbers in it.
9. click the pda button under files select the .tar file you made in step 5.
10. it will display the link to the file on your desktop in the pda text box.
11. DO NOT CLICK ANYTHING OR RE_PARTITION THIS MAY NOT WORK>
12. CLICK THE START BUTTON ONLY>
13. DO NOT UNPLUG ANYTHING YOUR WILL BRICK YOUR PHONE>
14. THE PHONE AND ODIN WILL STRAT TO DISPLAY LINES THAT MOVE LEAVE THE PHONE TILL THE FIRST BLOCK ON THE TOP OF ODIN SAYS PASS IN GREEN!
15 your phone will reboot and everything will be back to stock 2.2
16. you may need to wipe your phone through the factory privacy menu reset again then all is stock.
Thanks to all the link I used.
If this works for you please click my tanks button and let me know.
Ian
Lmao where is the guide?
Edit: There it is!
And more threads beating the same old horse to death
Sent from my SGH-T959 using XDA App
sorry was finishing the links
Stefan your being a *****, stop being a f***ing loser and do something with your life, instead of wasting your time bashing all these forums.
Sent from my T-Mobile myTouch 3G Slide using XDA App
ameedi600 said:
Stefan your being a *****, stop being a f***ing loser and do something with your life, instead of wasting your time bashing all these forums.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
Seems my lack of appreciation seems to make it look like im trying to "TROLL"
Let me start by saying thanks OP for this guide, now that's out the way, there are dozens of guides for this problem, this one provides no new information hence same horse being beaten to death
Sent from my SGH-T959 using XDA App
I had no idea you were actually being appreciative but you would have to forgive me because of the way you are bashing other forums for helping the android community.
Sent from my T-Mobile myTouch 3G Slide using XDA App
there are lots of new people every day that come join xda and when you slam them they find other places and get comfortable there.some of you learn alot then become big headed thanks for allllll these helpful post i love to learn every possible way to beat a brick,thanks for the post
stefan.buddle said:
Seems my lack of appreciation seems to make it look like im trying to "TROLL"
Let me start by saying thanks OP for this guide, now that's out the way, there are dozens of guides for this problem, this one provides no new information hence same horse being beaten to death
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
you have a point, the OP's post somewhat redundant and probably not needed.
But you know what's more unwanted in this forum? A trash talker like you who's relentlessly being a jackass.
Please Mod, ban this dude.
This thread should be moved to General, no disrespect. It's simply in the wrong category.
Sent from my SGH-T959 using XDA Premium App
I fixed this a little differently and without having to wipe my device. Figured this out after a bad kernel flash through odin. My vibrant had this screen and would not be recognized in any windows os on multiple computers with all kinds of drivers and many versions of odin.
You'll need a pc running linux. If you don't have one, temporarily boot ubuntu off a cd or usb (google it).
Install heimdall either from a binary package if your on 64 bit or compile from source like I did if you have a x86 system. We don't need the gui just the cmd application.
If you compile make sure you compile the libusb that comes with heimdall first. Also if your on ubuntu or a debian variant you will need to install build-essentials from apt or synaptic.
Now type the following command in a terminal window do not press enter:
heimdall close-pc-screen
Pull the battery from the phone put it back in and plug in the usb. Now turn the phone on and hit enter to run your command when the phone starts to turn on.
You may see the script start to run and fail or not work at all. There is a sweet spot to hit enter and run that full cmd. if it didn't work try again. Took me like five tries.
When successful your phone will just boot back into your rom as you had it. Though you may want to reinstall now since something clearly went wrong.
Hope this helps.
Sent from my SGH-T959 using XDA App
ewidtfeldt said:
I fixed this a little differently and without having to wipe my device. My vibrant had this screen and would not be recognized in any windows os on multiple computers with all kinds of drivers and many versions of odin.
You'll need a pc running linux. If you don't have one, temporarily boot ubuntu off a cd or usb (google it).
Install heimdall either from a binary package if your on 64 bit or compile from source like I did if you have a x86 system. We don't need the gui just the cmd application.
If you compile make sure you compile the libusb that comes with heimdall first. Also if your on ubuntu or a debian variant you will need to install build-essentials from apt or synaptic.
Now type the following command in a terminal window do not press enter:
heimdall close-pc-screen
Pull the battery from the phone put it back in and plug in the usb. Now turn the phone on and hit enter to run your command when the phone starts to turn on.
You may see the script start to run and fail or not work at all. There is a sweet spot to hit enter and run that full cmd. if it didn't work try again. Took me like five tries.
When successful your phone will just boot back into your rom as you had it. Though you may want to reinstall now since something clearly went wrong.
Hope this helps.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
My phone had the PHONE!PC screen and I could ODIN it back to stock, in windows. Just search for PHONE!PC and there are PLENTY of guides to this. You've got to make sure you've got NO driver/device problems in windows for this to work.
Trust me its possible to put your phone in a state that windows will not recognize it. My post was meant to help those individuals. Thanks for your input though also.
Sent from my SGH-T959 using XDA App
It should be mentioned that you can only flash from that screen with one of the newer SBL already on the device. Otherwise you will have to get into Download Mode to ODIN. I can speak from experience when I bumped the spacebar trying to get my device into Download Mode and ODIN began to flash away. Left me with an almost completely unresponsive device. If you are unsure whether you have flashed a ROM containing the newer SBL, then you are much safer getting into Download Mode as usual and going from there. Whether it be 3-button or a JIG.
I couldn't even jig. I solder for a living and made my own. No luck.
Sent from my SGH-T959 using XDA App
I have had my phone at this screen before, I simply rebooted holding the keys, went into download mode and used Odin...
ewidtfeldt said:
Trust me its possible to put your phone in a state that windows will not recognize it. My post was meant to help those individuals. Thanks for your input though also.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
not if it's at that screen. Samsung Gadget drivers are your friend.
@ ianandamy
This guide applicable for other android phones by Samsung ?
we are using modified cable to get boot mode. hope we dont ve to use that modified cable anymore.
B/R
Subrata.mobi
I can't answer that although I would assume if you use the official update for your galaxy phone and remove the .mp5 extention it should.
subratamm said:
@ ianandamy
This guide applicable for other android phones by Samsung ?
we are using modified cable to get boot mode. hope we dont ve to use that modified cable anymore.
B/R
Subrata.mobi
Click to expand...
Click to collapse
I think all Samsung phones running android can use Odin. You will need the correct .tar and .PDA files for the phone you are using as the vibrant ones will not work on any other phone. Don't quote me on this though, its just my guess.
~EDT \m/~
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
This is my first post and I'm going to try my best to not break a rule. If I do, I apologize in advance.
Thread thread is a sort of, "This is how I updated my phone from 4.2.2 to 4.4.2 and rooted it but your mileage may vary."
First, thanks goes to Sunderwear for his directions on how to push KitKat to the Samsung S4 Active as well as ROOT it. I rooted my 4.2.2 phone a few months ago and didn't realize doing so would prevent OTA updates. I went to the AT&T store to have them put 4.4.2 on the phone only to be told that the store didn't have the image (or whatever they said) and couldn't put it on my phone. Instead, they put 4.3, which turned out to be great because the directions pretty much have you going back to 4.3 in order to root.
BTW, if you are uninitiated, you may want to read this glossary page.
After having root in 4.2, I knew I wanted it in 4.4.2!
For the most part, I've been hesitant to flash the phone. I tried like hell to flash my first Android (Samsung S2 Skyrocket) only to brick it. (FWIW, if you can tell me how to fix it, I'd be gracious! It buzzes once and then twice and repeats.)
Anyway, I started in the thread above only to find that I now needed to download Odin. This, surprisingly, was difficult. I found this site (http://odindownload.com/) which I am convinced is some sort of hacked version of Odin because when I tried to install from there, my Symantic warned me. When I disabled it, the file tried to install a bunch of bloatware/spyware. It EVENTUALLY gave me Odin.
FYI, this thread was of no use. No download links.
Later on, after searching for something unrelated, I got to a "better" site. Unlike the link above, this site has a zip file compared to the bloat-ridden executable.
I learned that I had to use Odin 3.07 and NOT Odin 3.09. Odin 3.09 did not have the PDA button that would be central to me flashing the ROM to the phone.
I started my journey on the thread for the Stock AT&T Firmware Collection. I learned that the thread uses the last three characters of the build name to identify the build. For example, 4.3's build name is I537UCUBML2 but was referred to as "ML2". This was a bit confusing but I got the hang of it. I then went over to the 4.4.2 rooting thread. It was there that I read Sunderwear says that you need to downgrade to 4.3 to root 4.4. I was grateful that AT&T only updated me to 4.3!
Sunderwear's second post described how to root 4.4.2 if you had a rooted 4.3. Since I hadn't done that yet, I proceeded back to the firmware collection and found the thread to root my 4.3 phone.
I downloaded the files and loaded up the first file to flash. I made the mistake of keeping my phone plugged in while trying to put it in download mode. It was when I stumbled upon this page that gave me the clue that my phone had to be disconnected first before going into download mode.
Once done, I clicked Start and Odin flashed my phone! It took about 2-3 minutes.
The next step was to do saferoot. The thread didn't link it so here it is.
SafeRoot requires your phone to be in USB debugging mode. Directions were found by googling. You go to Settings, About Device, and click Build Number until you get a message saying you have enabled developer mode. Then go back out one screen and go into Debugging options and enable USB debugging.
One installed I rebooted the phone and everything worked...except for wifi and "some other stuff". The thread warned you about this so I didn't worry. I flashed the next file and rebooted. Updated SuperSU and everything worked!!
I verified that I had root by installing Root Checker.
All was great with 4.3! Now for what turned out to be the more agonizing part: Upgrading to 4.4.2.
Going back to the 4.4.2 rooting thread, I learned that all I needed to do was install SafeTrap to update to KitKat and then flash a couple more files. I downloaded pwnedkitkat.zip (link in the thread) and then installed SafeTrap. I presume that SafeTrap is some sort of bootstraping method of updating the firmware.
I copied the SafeTrap apk file, along with pwnedkitkat and the updated superSU zip files to my external SD card. Once everything was copied, I installed SafeTrap and then opened it. SafeTrap then offered me the option to install Recovery Mode. Once done, I restarted my phone.
I noticed a new splash screen after the Samsung splashscreen. I clicked the Menu button (left of home) to start the recovery process. I clicked "Install" and pointed it to the pwnedkitkat.zip file. This took the longest. Probably took 15 minutes but felt like an eternity. I wasn't sure if my phone bricked when the screen turned off! But upon turning it back on, it was still going.
The bar moved very slowly. But remained patient. After a long 15-20 minutes, it updated! SafeTrap gave me the option to reboot there but I followed the directions and installed SuperSU from the SD card. It was a quick install.
I restarted the phone! I was done!! Right?
My phone got stuck on the AT&T splash screen! I started to panic! What did I do wrong?!
I missed Sunderwear's step five:
5.Put your phone in download mode and flash the 4.4.2 stock boot.tar.md5 kernel and your phone will boot after a few minutes with root access enabled.
Click to expand...
Click to collapse
Goes to show you to read everything. I missed it due to the line break. I downloaded the boot.tar.md5 file and put the phone back into download mode and push it via PDA in Odin (I presume PDA. It wasn't explicit.)
After a few hours of chewing my nails and wondering if I bricked it:
http://imgur.com/a/UFg6u#F5qFTdq
So thanks to everyone! Now if I could only unbrick my Skyrocket!
Outstanding instructions! Thank you for this. I wish all the instructions were as clear and detailed as this is.
:good:
I tried like hell to flash my first Android (Samsung S2 Skyrocket) only to brick it. (FWIW, if you can tell me how to fix it, I'd be gracious! It buzzes once and then twice and repeats.)
Click to expand...
Click to collapse
do you mean it vibrates every 2 seconds and doesn't turn on?
:good:
Great instructions and great story. Sounds like what most people like me go through every time we try to do something like this.
jimmietilt said:
do you mean it vibrates every 2 seconds and doesn't turn on?
Click to expand...
Click to collapse
Yup. The last time I looked into this was almost two years ago. It just sits in my drawer now.
dajabec said:
Great instructions and great story. Sounds like what most people like me go through every time we try to do something like this.
Click to expand...
Click to collapse
I think what got me was all the new terminology and unfamiliarity of flashing. Jailbreaking an iPhone (which I've done before I had an Android) is pretty simple. It's pretty much point and click. But ROMs, flashing...these all have definitions which can be a bit overwhelming, even to a technical person such as myself. I've compiled Linux kernels from scratch!
But there's something about making your phone unusable. Something that I cannot live without, especially as I'm searching for a job.
It's nerve-wracking and I especially got nervous when I was putting KitKat on since it took so long. But overall, I'm glad I did it.
Mike, I wish everyone's instructions were like yours. I am in a similar boat as you, currently on 4.2.2 rooted and unable to do an OTA. I am not really sure what to do as I do not want my phone to be wiped. Did you bring your phone to an ATT store or a Device Support Center? And when they flashed 4.3 did your phone lose anything?
Agent. said:
Mike, I wish everyone's instructions were like yours. I am in a similar boat as you, currently on 4.2.2 rooted and unable to do an OTA. I am not really sure what to do as I do not want my phone to be wiped. Did you bring your phone to an ATT store or a Device Support Center? And when they flashed 4.3 did your phone lose anything?
Click to expand...
Click to collapse
Backup using Samsung kies and go find the 4.3 Odin package. Hell I just use the Google backup feature which is good enough for me.
Sent from my SAMSUNG-SGH-I537 using XDA Premium 4 mobile app
rdh28 said:
Backup using Samsung kies and go find the 4.3 Odin package. Hell I just use the Google backup feature which is good enough for me.
Sent from my SAMSUNG-SGH-I537 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I don't want to go through all of the trouble of reconfiguring all of my settings, restoring all of my app specific stuff, and just getting everything back the way I had it. Does Kies backup every little thing or just app data and contacts etc?
Agent. said:
I don't want to go through all of the trouble of reconfiguring all of my settings, restoring all of my app specific stuff, and just getting everything back the way I had it. Does Kies backup every little thing or just app data and contacts etc?
Click to expand...
Click to collapse
Not sure but if you really want to upgrade it's worth the thirty minutes it takes to reconfigure
Sent from my SAMSUNG-SGH-I537 using XDA Premium 4 mobile app
Agent. said:
I don't want to go through all of the trouble of reconfiguring all of my settings, restoring all of my app specific stuff, and just getting everything back the way I had it. Does Kies backup every little thing or just app data and contacts etc?
Click to expand...
Click to collapse
Use Titanium Backup. Just make sure you don't restore system apps and you'll be fine.
rdh28 said:
Not sure but if you really want to upgrade it's worth the thirty minutes it takes to reconfigure
Sent from my SAMSUNG-SGH-I537 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I know, I will probably do it this summer, I'm just really busy right now and can't afford to risk anything happen to my phone
Devo7v said:
Use Titanium Backup. Just make sure you don't restore system apps and you'll be fine.
Click to expand...
Click to collapse
The system apps are one of the primary issues as that is what needs to be reconfigured, other apps can be backed up and restored easily.
Agent. said:
I am not really sure what to do as I do not want my phone to be wiped. Did you bring your phone to an ATT store or a Device Support Center? And when they flashed 4.3 did your phone lose anything?
Click to expand...
Click to collapse
I took mine to the AT&T device support center. I called before going in and they pretty much told me it was going to be destructive. I had previously wiped my phone earlier that day in the hopes that it would receive the OTA update.
I'm not going to lie: it's nerve-wracking, but straight forward. I know sometimes it helps to have someone hold your hand while you do it. And for me, it was definitely in the camp of, "What am I going to do if my phone craps out on me?"
But like what someone else said: you can back up your settings within Keis. I didn't. I just did a wipe. I backed up my photos but that's about it. Everything else was in the cloud. The one thing I should have done was transfer my Authenticator keys to another device because I couldn't log into AWS (which does not give out backup codes like Google). I did end up switching to Authy (I can't link to it since I'm such a new user but you can find it in the Play Store) which allows you to have more than one device. It shares your secret key between devices so it's technically less secure. But I needed the flexibility in case my phone crapped out on me again.
Pro Tip: to install all your apps again, go to the Google play store on your device and click "My Apps". Long hold one of the apps and then select the check boxes of the apps you want to install.
And hey if you run into anything there's plenty of people who check this forum regularly. I've managed to root 4.2.2 , 4.3, and 4.4.2 while retaining full functionality, just from this forum...the information is out there good luck!!
Sent from my SAMSUNG-SGH-I537 using XDA Premium 4 mobile app
Agent. said:
I know, I will probably do it this summer, I'm just really busy right now and can't afford to risk anything happen to my phone
The system apps are one of the primary issues as that is what needs to be reconfigured, other apps can be backed up and restored easily.
Click to expand...
Click to collapse
What system apps need to be reconfigured? I can't really see that many that it would take you more than 15 to 20 minutes.
Thank you guys, I need to get my phone serviced anyway as there is a yellow dot in the top left of the screen that won't go away. So if AT&T sends me a new phone I can do all of the dirty work and then transfer everything side by side from the old device. If they won't for whatever reason I will do what you guys suggested. So just to be clear I should follow the instructions to Odin to 4.3, root, then follow the upgrade/root instructions to 4.4.2?
Agent. said:
So just to be clear I should follow the instructions to Odin to 4.3, root, then follow the upgrade/root instructions to 4.4.2?
Click to expand...
Click to collapse
I personally thing this is better since if you have 4.4.2 already, you have to downgrade to 4.3, root it and then put 4.4.2 on it.