Hey guys the official rom is out
http://blogs.att.net/consumerblog/story/a7783602
you have to update your device over kies.
Cheers
Got the message just now
" AT&T Free Msg: Samsung Captivate Glide upgrade to Android 4.0 Ice Cream Sandwich is now available! The OS update supports enhanced performance, user interface and other device improvements. Open the link from your PC (not your phone), and follow the instructions: www.samsung.com/us/attcaptivateglide/update "
Sent from my SAMSUNG-SGH-I927 using xda app-developers app
page was working about an hour and now page not found. Maybe they pulled the update? I haven't tried it yet because of the keyboard backlight issue from other posts...and I have no desire to do any rooting/CWM stuff.
Page worked for me just now. It basically just says download kies and let it upgrade.
Does the official rom have the same version number as the leaked one?
Sent from my SAMSUNG-SGH-I927 using xda app-developers app
strange now the page works again...has anyone applied the official ICS with AT&T yet? wondering if the backlight issue is resolved.
There are no bugs, samsung has fixed it all
Does the official version have CarrierIQ?
Nevermind.
R3D X said:
There are no bugs, samsung has fixed it all
Click to expand...
Click to collapse
Oh? That's not what others have reported - the keyboard backlight is supposedly still broken, unsure about tethering or the other problems.
gnahc79 said:
strange now the page works again...has anyone applied the official ICS with AT&T yet? wondering if the backlight issue is resolved.
Click to expand...
Click to collapse
No backlight on my wife's Glide... She's pissed...
Then root and install the zip
I actually passed on this phone because I was worried it might not get ICS. I'm glad it did all the same. I miss having a hard keyboard.
Sengfeng said:
No backlight on my wife's Glide... She's pissed...
Click to expand...
Click to collapse
thanks for the save!!!! I was downloading the update when I saw your post. my wife would have been VERY upset as well. good luck.
I don't want to mess with rooting, CWM and all that stuff on the wife's phone just to get back a basic function. Doing all of those things to get new functions...maybe.
gnahc79 said:
thanks for the save!!!! I was downloading the update when I saw your post. my wife would have been VERY upset as well. good luck.
I don't want to mess with rooting, CWM and all that stuff on the wife's phone just to get back a basic function. Doing all of those things to get new functions...maybe.
Click to expand...
Click to collapse
Really, it's super-easy to install the backlight fix, and you don't even have to root or muck around all that much. You flash CWM in odin, which takes about 30 seconds, and then boot into CWM and flash a single zip file, which should take at most a minute including the reboot time. Tada, keyboard light is fixed.
bakageta said:
Really, it's super-easy to install the backlight fix, and you don't even have to root or muck around all that much. You flash CWM in odin, which takes about 30 seconds, and then boot into CWM and flash a single zip file, which should take at most a minute including the reboot time. Tada, keyboard light is fixed.
Click to expand...
Click to collapse
Im in the same situation can u do like a step by step how to do that cause i dont want to brick my phone in my trying to figure it out on my own
bakageta said:
Really, it's super-easy to install the backlight fix, and you don't even have to root or muck around all that much. You flash CWM in odin, which takes about 30 seconds, and then boot into CWM and flash a single zip file, which should take at most a minute including the reboot time. Tada, keyboard light is fixed.
Click to expand...
Click to collapse
That requires root access and messing with stock recovery right? Although it can be done quickly, it could mess up any future official ICS update...you know, an official build that has the backlight fix + other fixes. I'd rather not deal with unrooting, getting stock recovery back on, and still have a risk of a soft brick....all for a backlight fix. For my scenario ICS can wait or never be applied on the glide. My wife doesn't care .
gnahc79 said:
That requires root access and messing with stock recovery right? Although it can be done quickly, it could mess up any future official ICS update...you know, an official build that has the backlight fix + other fixes. I'd rather not deal with unrooting, getting stock recovery back on, and still have a risk of a soft brick....all for a backlight fix. For my scenario ICS can wait or never be applied on the glide. My wife doesn't care .
Click to expand...
Click to collapse
It actually doesn't require root access, just a custom recovery, which is flashed from the PC. You can then replace it with a stock recovery, if you prefer.
Anh56 said:
Im in the same situation can u do like a step by step how to do that cause i dont want to brick my phone in my trying to figure it out on my own
Click to expand...
Click to collapse
I made a walkthrough for the entire leak here, but I'll snip it down and just assume you're running some form of ICS now that's completely stock:
bakageta said:
To fix the keyboard backlight bug, you'll need the following:
Odin 1.85
Clockworkmod Recovery
The Keyboard Backlight fix The one labeled LH2 is for the official, the one labeled CWM is for the leak. If you're not sure what you're on, go to About Phone, and check the Baseband Version, if it ends in LH2 you're on the official, if it ends in LG9 it's the leak.
Optionally, SuperUser 3.2 RC3 if you'd like root.
First, make sure you have Kies installed, so that you have the correct USB drivers. Download the 4.0.4 .exe file from here. Power off your phone, hold Volume Up and Power to turn it back on. Keep holding them until you get a screen warning you about custom software, and release, then press volume up again to enter download mode. Hook the phone up to your pc and run Odin 1.85. Uncheck "F. Reset Time" and make sure that the only box checked is Auto Reboot, you shouldn't need to change anything else. Click on the PDA button, and load the clockworkmod .md5 file you downloaded, then press the start button and wait for the device to reboot.
This time you'll reboot into recovery. Power the phone off, hold the volume down and power button to turn the phone one. Keep holding them until you see text about entering recovery in the top left, and release. Use the volume keys to navigate and power to select, and go to Install zip from sdcard. Select the keyboard backlight fix zip. Once that's finished, if you'd like to be rooted, repeat the process to flash a zip, and this time select Choose zip from sdcard, selecting the superuser zip you downloaded earlier. Select Yes, and wait for superuser to flash. If you plan on keeping Clockwork Mod Recovery, you should make a backup now. To do so, select Backup and restore, and backup. This will take a bit, just be patient. When you're finished, select reboot system now, and you should be set.
From here, if you rooted you can install something like Titanium Backup, which will use root access to let you remove the various AT&T bloatware.
Click to expand...
Click to collapse
Yeah backlight isn't working sorry, someone on a blog had said so. Very unprofessional of samsung. A rom cooked with cm9 willl have to include the backlight fix
bakageta said:
It actually doesn't require root access, just a custom recovery, which is flashed from the PC. You can then replace it with a stock recovery, if you prefer.
I made a walkthrough for the entire leak here, but I'll snip it down and just assume you're running some form of ICS now that's completely stock:
Click to expand...
Click to collapse
:good:
Cool, thanks for the info. Good to know root is not required. I'll still hold off on the update but I'm sure others will apply ICS+backlight fix.
I updated last night, and I can report that after ending any call the phone app reports a hard stop rather than just going away, and that resets your cell connection. And I imagine the keyboard backlight will be fixed very soon. But did these issues exist on the leaked rom in its first release and then programmers modified to get them back?
-Ara
Sent from my SGH-I927 using xda app-developers app
Related
Here is the update that everyone has been waiting for At the moment, I'm only providing the modem, and rooted, stock, deodexed version of the ROM. There will be a cleaned up version to go along with all of this in due time, but we're currently working out some problems with it. I would like to note that despite this being the Froyo update, it is not without its own set of problems, and odds are you may never see another update outside of this from anywhere. However, the benefits of getting Froyo will outweigh the problems with it for most people, so have at it.
You will need a few things to get this, first, the downloads list here will be needed (obviously). You'll also need to have CWM setup and know how to use Odin. Heimdall will also work for those of you not on Windows, but I'm not providing any instructions for flashing using Heimdall. Also note that you will want to wipe data or perform a factory reset before booting into Froyo to avoid any problems. While you may get away with not doing it, you could end up with several problems, so my recommendation is to wipe data. Also, you can flash the ROM first, or flash the modem first, which ever you want to do. There isn't really a required order for it, as long as you do both parts.
[size=+1]Instructions[/size]
Download everything you need.
Odin
Froyo Radio
ROM+Kernel
CWM Kernel
CWM update.zip
Put the ROM zip and CWM update.zip on your SD Card
Flash the Radio via Odin in the PDA box
Enter CWM and flash the ROM+Kernel
Wipe Data in CWM before restarting your phone
Restart and enjoy Froyo
[size=+1]Downloads[/size]
Modem
ROM+Kernel
FAQ
How can I donate to you for this?
You can either click the "Donate to me" button above my avatar, or go through this link. Don't feel obligated to donate though, as Verizon should have given this to you (the users) long ago.
Can I still receive updates after flashing this?
You cannot receive updates after flashing this unless you revert back to DL17, which is the latest official software released by Verizon and Samsung.
If I can receive updates on this, how can I restore back to DL17?
I've been sending this to several people already that have had problems with their phones. If you need to revert back to DL17 for any reason, download this. You will need 7-zip or similar to extract it. Once you have the .tar.md5 file, flash it in Odin via PDA like you did for flashing the modem to get Froyo.
Can I return my phone to Verizon for warranty repair/service with this on my phone?
No. If you need any sort of help with your phone from Verizon, you will need to have the stock DL17 ROM on your phone. Anything else and you have voided your warranty and Verizon and/or Samsung will not have to do anything to help you. See the above question for a package to restore your phone to the latest stock software.
Are there any bugs in this release?
Yes there are, just as there is with any software. I do not know what the bugs are though off hand though as I have not been using this update. I also cannot say whether any of the problems you may have will ever get fixed, seeing as you can't even get a straight answer on why the update has been taking so long.
Is xxx modification/theme compatible with this?
Odds are that it isn't. All of the current themes and modifications for DL17 will not work on this package. They will all need to be updated to be able to work. Given that this is a relatively new release, this could take some time, especially given that it is the summer and people are on vacation (I'm looking at you trailblazer ). We will work though to try and get all of the mods ported from DL17 to EC03 so that you don't have to give up anything to upgrade.
Will you release a "clean ROM" based on this?
Yes, and it is already in progress. I have sent it out to a couple people already to ask for feedback and any issues. Once they say it is ok, I'll create a new thread with the cleaned up version. There is currently no ETA on when it will be released though.
Are there any other kernels I can use with this besides the one that comes with it?
At the moment, there isn't. I'm trying to get a custom kernel to work, but it has some problems. At the very least, we can customize the stock kernel some, but I do not know if a full source built kernel will ever be available.
Can I flash this if I am on the voodoo kernel?
No, if you are running the voodoo lagfix kernel, you will want to disable voodoo prior to doing anything. If you don't, you'll be in for some fun times with Odin getting your phone back in a usable state.
Can I get something included in the FAQ?
Yes you can. Just create a post with the following template, and I'll try to keep the FAQ updated. If I don't see it or add it right away, don't worry, I'll try and update it. If it has been a week or two and I still haven't responded, just send me a message with a link to what you want included. Here is the format to use:
Code:
[PLAIN][b]Question goes here?[/b][/PLAIN]
Answer goes here.
I'm getting ready to download it
When I go to flash the radio, Odin says it's an invalid image type
circa881 said:
When I go to flash the radio, Odin says it's an invalid image type
Click to expand...
Click to collapse
It should work You aren't extracting or renaming it at all are you?
Nope, not at all. I even downloaded it again just to make sure the first file wasn't corrupt
circa881 said:
Nope, not at all. I even downloaded it again just to make sure the first file wasn't corrupt
Click to expand...
Click to collapse
Your phone is in download mode when you're attempting to flash via Odin?
XD Now I feel like a ruh-tard. I forgot about that part
Wait, it's still saying invalid image type
I'm in shock... I'm on this forum every day and I missed this?! I'm going to install this and mess around with it. Ill post any bugs I find later this evening..
Kudos @imnuts for the effort!
Took about 7 minutes from download to phone setup. There was a short hang at the Samsung screen (approx. 15 seconds) but other than that it looks like it should. All startup animations are in tact..
I just gotta ask, its killing me... Where did this come from?
jaizero said:
I just gotta ask, its killing me... Where did this come from?
Click to expand...
Click to collapse
Does it really matter?
No... No it doesnt.. Its working perfectly by the way.. But Im sure you already knew that lol..
If jaizero got it to work, why couldn't I?
Sent from my SCH-I400 using XDA Premium App
---------------------------------
Jill plays tricks, Jack plays God
jaizero said:
Took about 7 minutes from download to phone setup. There was a short hang at the Samsung screen (approx. 15 seconds) but other than that it looks like it should. All startup animations are in tact..
I just gotta ask, its killing me... Where did this come from?
Click to expand...
Click to collapse
It came from heaven!!!
Sent from my Mind
^ lolololol
Sent from my SCH-I400 using XDA Premium App
FROYO
i think i love you (no homo)
I successfully loaded the ROM.
It hang a bit longer than usual on the verizon logo but after that no issues.
Thanks imnuts and anyone else that worked to make this possible.
Kay, how are people getting this to work when I couldn't get the radio flashed
Sent from my SCH-I400 using XDA Premium App
---------------------------------
Jill plays tricks, Jack plays God
Ok I dl'd both files, I have Odin1.3 both blue n yellow CWM update.zip but what is CWM kernal?
P.S. I totally love you guys and many thanks to nuts for confirming my faith in opensource and saving my phone
Sent from my SCH-I400 using XDA Premium App
We received our Samsung Galaxy II phones a few days ago.
My wife had a Swiftkey and Swiftkey X keyboard apps in her Amazon appstore account. She installed Swiftkey X, and she was presented with an "update" that showed Swiftkey (not the X; apparently this is an issue with Amazon appstore based on Swiftkey site). Thinking that it was an update to the Swiftkey X, she apparently applied it, and immediately there were number of FC notices (she remembers seeing TWLauncher among them) and a spontaneous reboot of the phone. Then, she couldn't get online either through WiFi or 4G. At that point she gave the phone to me to fix it
Comparing her phone side by side with mine it is very clear that there's an issue with network connectivity. While mine flies through the pages, market downloads, etc. either on WiFi or 4G, hers get stock for 3-5 seconds before opening pages or sometimes just displays a "webpage cannot be found" or "connection error".
I went ahead and did a factory restore, but that seems to only delete user account, personal files, etc. if I understand it correctly. Moreover, the issue is still there after the restore. So, is there a way to restore the system files to stock as well? Can it be done without rooting, or does it require loading a fresh ROM?
Sorry for the lengthy message and thanks in advance!
http://forum.xda-developers.com/showthread.php?p=27322
that's a full factory reset.
Sent from my SGH-T989 using Tapatalk
mikeyinid said:
http://forum.xda-developers.com/showthread.php?p=27322
that's a full factory reset.
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Thanks for your reply. Could you double check the link? I get "No Thread specified. If you followed a valid link, please notify the administrator".
Thanks again!
tenderidol said:
Thanks for your reply. Could you double check the link? I get "No Thread specified. If you followed a valid link, please notify the administrator".
Thanks again!
Click to expand...
Click to collapse
if you look at the sticky threads at the top of this forum there is one called index by AllGamer. Its at the bottom of the first post. Make sure you grab the Tmobile one and not the telus one
Sent from my SGH-T989 using Tapatalk
Here: http://forum.xda-developers.com/showthread.php?t=1323878
Everything goes back to stock.
You need to either:
1. Root
2. Install CWM through ROM Manager
3. Flash this
Or:
1. ODIN flash CWM
2. Flash this
513263337 said:
Here: http://forum.xda-developers.com/showthread.php?t=1323878
Everything goes back to stock.
You need to either:
1. Root
2. Install CWM through ROM Manager
3. Flash this
Or:
1. ODIN flash CWM
2. Flash this
Click to expand...
Click to collapse
Dude. That's a half ass way, it doesn't take you to stock. First of all its deodexed.. Just a sec
This is the only proper way to go back to stock THIS IS IT RIGHT HERE
Sent from my SGH-T989 using Tapatalk
Thanks again for the replies. So, I'm going to have to root it and put a stock image back I gues... I was hoping that SII had a fail safe similar to Nook Color where you can easily go back to stock if something was not right.
tenderidol said:
Thanks again for the replies. So, I'm going to have to root it and put a stock image back I gues... I was hoping that SII had a fail safe similar to Nook Color where you can easily go back to stock if something was not right.
Click to expand...
Click to collapse
you dont have to root it to run the odin package
mikeyinid said:
you dont have to root it to run the odin package
Click to expand...
Click to collapse
Oh, sorry about that. I'm a newbie for the SII rooting/modding (did quite a bit with Nook Color), and I need to do some reading first.
Smart man!
Sent from my SGH-T989 using Tapatalk
voidthedroid said:
Smart man!
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Alright, I'm halfway through. The rooting process for the SII is little different than NC, but the principles are the same.
By the way, is it safe to assume that some conflict between SwiftKey and SwiftKey X caused the problem on her phone? The reason I ask is because I'd like to put SwiftKey X on my SII (it has multi-language support) and I dont want to deal with the same issue if it was the culprit.
I believe I did enough reading at this point
Since this doesn't involve rooting (now I understand it), I'd like to get an "OK" from the guru before proceeding with the following "as newbie as it gets" steps:
1. Install Odin (v1.85)
2. Install Kies for the recent GSII drivers
3. Make sure Windows recognizes the phone in ODIN (seeing <ID:0/004> Added!! in the message box)
4. Turn off the phone
5. Turn on the phone by holding both the Vol-up and Vol-down buttons and plug the USB cable in while still holding both buttons
6. Select volume up button to proceed to download mode
7. Start Odin
8. Check the PDA button in Odin and browse to “T989UVKID_HOME_SGH-T989user_CL594724_REV00.tar.md5” file
9. Click Start in Odin and let it flash
10. Once it completes and reboots…..
Is that it? At Step 10, it should boot into a 100% T-Mo stock, right? Just to be sure, I’ll perform a factory reset after that point and start all over with the user files, apps, etc.
Thanks in advance!
Sounds good. But if you look in the stickied threads top of this forum the drivers for our phone are posted. No need to install kies but that does work also
Sent from my SGH-T989 using Tapatalk
tenderidol said:
Thanks again for the replies. So, I'm going to have to root it and put a stock image back I gues... I was hoping that SII had a fail safe similar to Nook Color where you can easily go back to stock if something was not right.
Click to expand...
Click to collapse
The "factory reset" you used IS the fail safe. The parts that "factory reset" doesn't remove is the part that won't be messed up unless you are rooted. So I don't even know how you touched /system etc without rooting...
mikeyinid said:
Sounds good. But if you look in the stickied threads top of this forum the drivers for our phone are posted. No need to install kies but that does work also
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Thanks a lot!
Just finished flashing the stock image and everything worked as expected. This was also a good practice to learn how to restore it to stock in case something goes bad.
513263337 said:
The "factory reset" you used IS the fail safe. The parts that "factory reset" doesn't remove is the part that won't be messed up unless you are rooted. So I don't even know how you touched /system etc without rooting...
Click to expand...
Click to collapse
The issue was created after installing a 3rd party keyboard and -by accident- applying an update that was supposed to be for a slightly different version, which resulted in numerous force closes and random reboots immediately. I might be wrong here, but that indicates that more than just the user files were affected, since deleting just user files via factory reset didn't help the network problem. However, flashing the stock image -without rooting- took care of the problem.
I'm completely new to flashing and modifying my phone in any way. But the improvements I see people talking about from flashing to new ROMs are compelling me to try it out.
I was sceptical about flashing my nexus a couple months ago when some ROMs had been released but from what I'm reading now people are pretty confident with how stable they are.
I'm looking for any of the following:
Smoother/More responsive OS
Improved Battery Life
4.0.3 fixes
I'm okay with slight modifications such as the removal of the Google search bar on home screen
Thanks, and if possible could someone link me to anything that would help/guide me through flashing my nexus.
AOKP
Hey,
I was sceptoical too but rooting was the best thing I could have done.
Check out AOKP BUild 15 on these forums for a really good rom and very customised. It is stable and has been working for me perfectly. Way better than stock!
Good luck.
jd1001 said:
Hey,
I was sceptoical too but rooting was the best thing I could have done.
Check out AOKP BUild 15 on these forums for a really good rom and very customised. It is stable and has been working for me perfectly. Way better than stock!
Good luck.
Click to expand...
Click to collapse
How does it compare to CM and could you tell me about some new features that build would give me?
Also, do I still receive updates from google if I used modified ROMs? If I flash to AOKP Build 15 will I be able to update to 4.0.4 later and continue to 4.0.5 etc
edit: Is this what you are talking about? http://forum.xda-developers.com/showthread.php?t=1432408
edit 2: seems that 'AOKP' isn't mutually exclusive with 'CM', kinda shows how much I know lol
edit 3: the thread says 'Compatibility:' with i9020 and i9023 which google tells me are Nexus S phones, will it still work with my Galaxy Nexus?
Get Android Revolution HD. Stock UI with performance tweaks
Sent from my Galaxy Nexus using xda premium
Hey
Cythreill said:
How does it compare to CM and could you tell me about some new features that build would give me?
Also, do I still receive updates from google if I used modified ROMs? If I flash to AOKP Build 15 will I be able to update to 4.0.4 later and continue to 4.0.5 etc
edit: Is this what you are talking about? http://forum.xda-developers.com/showthread.php?t=1432408
edit 2: seems that 'AOKP' isn't mutually exclusive with 'CM', kinda shows how much I know lol
edit 3: the thread says 'Compatibility:' with i9020 and i9023 which google tells me are Nexus S phones, will it still work with my Galaxy Nexus?
Click to expand...
Click to collapse
This is the one I am using and it's brilliant.
http://forum.xda-developers.com/showthread.php?t=1402341
There are cool features like putting data off when you switch the screen off, saves battery. Also you can add notification toggles which are very handy.
In terms of getting future updates from Google, the devs on here always have the latest source code and modify it so when 4.0.5. is out you will have a rom on here that you can flash.
Seriously root it dude and have fun. It just gives the phone something extra and generally makes things faster.
How exactly do I put that ROM on my phone lol
I have no idea what '4. Wipe Dalvik cache.' would require me doing.
Hey
Cythreill said:
How exactly do I put that ROM on my phone lol
I have no idea what '4. Wipe Dalvik cache.' would require me doing.
Click to expand...
Click to collapse
Ok you need to look at the rooting and modding guides on here. Wiping the davlik cache is something you do when you have the phone in recovery mode. It is very easy to do and the instructions are very well written. Out the guides here:
http://forum.xda-developers.com/showthread.php?t=1392310
Good luck and if all goes well I bet you won't regret it.
jd1001 said:
This is the one I am using and it's brilliant.
http://forum.xda-developers.com/showthread.php?t=1402341
There are cool features like putting data off when you switch the screen off, saves battery. Also you can add notification toggles which are very handy.
In terms of getting future updates from Google, the devs on here always have the latest source code and modify it so when 4.0.5. is out you will have a rom on here that you can flash.
Seriously root it dude and have fun. It just gives the phone something extra and generally makes things faster.
Click to expand...
Click to collapse
So no automatic updates? I guess I can deal with that.
Also, I shall read those guides now, thank you very much for your help I'll get on rooting it right away.
Hey
Cythreill said:
So no automatic updates? I guess I can deal with that.
Also, I shall read those guides now, thank you very much for your help I'll get on rooting it right away.
Click to expand...
Click to collapse
No probs, no automatic updates but generally you will have the latest Android OS because the devs on here do such a great job at releasing them.
Have fun!
So I'm at this part of the guide
'b. Enter CWM Recovery by first entering the Fastboot mode Screen (Disconnect the usb cable (if you have one plugged in), then shut down your phone. Keep holding the 'Volume Up' and 'Volume Down' buttons and press the 'Power' button to boot the phone into FastBoot Mode), then select 'Recovery mode' by pressing the 'Volume Down' button and then press the 'Power' button to enter CMW Recovery.'
But after I select Recovery Mode, I get an android on the floor with a red triangle sign with a ! in it over the android.
What's this mean?
Also what should I use 'MSKIPS' GALAXY NEXUS TOOLKIT' for?
One of the steps under that part of the guide is 'After you have finished you can either boot straight into CWM Recovery to flash a Custom Rom (if you have already downloaded one and copied it to the root of your Internal Memory on your phone)', should I proceed with that? I have the KANGY2Pack on the root of my internal storage.
Cythreill said:
So I'm at this part of the guide
'b. Enter CWM Recovery by first entering the Fastboot mode Screen (Disconnect the usb cable (if you have one plugged in), then shut down your phone. Keep holding the 'Volume Up' and 'Volume Down' buttons and press the 'Power' button to boot the phone into FastBoot Mode), then select 'Recovery mode' by pressing the 'Volume Down' button and then press the 'Power' button to enter CMW Recovery.'
But after I select Recovery Mode, I get an android on the floor with a red triangle sign with a ! in it over the android.
What's this mean?
Also what should I use 'MSKIPS' GALAXY NEXUS TOOLKIT' for?
One of the steps under that part of the guide is 'After you have finished you can either boot straight into CWM Recovery to flash a Custom Rom (if you have already downloaded one and copied it to the root of your Internal Memory on your phone)', should I proceed with that? I have the KANGY2Pack on the root of my internal storage.
Click to expand...
Click to collapse
Yeah if you can enter recovery mode you should be able to apply a rom.
Did you root it successfully?
jd1001 said:
Yeah if you can enter recovery mode you should be able to apply a rom.
Did you root it successfully?
Click to expand...
Click to collapse
Don't think so,
http://imgur.com/WLKAu
After I went through this process, it appears my phone is just as it would be if I did a factory reset.
Ok, like I said on the PM, just start over. You are very close to having it rooted.
And get this kernel: http://forum.xda-developers.com/showthread.php?p=19794530
Will give you an extra boost (especially the appdrawer).
Don't install any 4.0.1/4.0.2 based roms like ARHD. 4.0.3 based roms like Bigxie's rom or openkang are much faster!
Gesendet von meinem Galaxy Nexus mit Tapatalk
Every time I try to install the Kangy2 zip file from within CWM Recovery I get 'installation aborted', what would cause this?
deezid said:
And get this kernel: http://forum.xda-developers.com/showthread.php?p=19794530
Will give you an extra boost (especially the appdrawer).
Don't install any 4.0.1/4.0.2 based roms like ARHD. 4.0.3 based roms like Bigxie's rom or openkang are much faster!
Gesendet von meinem Galaxy Nexus mit Tapatalk
Click to expand...
Click to collapse
How do I install a kernel? I think I know how to flash a rom (just install the zip from root storage via CWM Recovery after you've rooted/unlocked bootloader).
What different changes does a different kernel give vs different ROM?
Cythreill said:
How do I install a kernel? I think I know how to flash a rom (just install the zip from root storage via CWM Recovery after you've rooted/unlocked bootloader).
What different changes does a different kernel give vs different ROM?
Click to expand...
Click to collapse
Woo hoo! Glad you got sorted after all the private messages. Flashing the kernel ios the same as flashing a rom, the same method I mean.
Kernels vary so I would recommend Apex build five kernel, that's not to say any of the other ones are bad but just the one I am using and it works well.
Glad you got all sorted anyway dude.
So I recently cut ties with my rooted OG evo :'( and have switched to a sprint galaxy s2, aka the epic 4g touch fi27. The first thing I did was head over to these forums because of course my first thought was let's open this bad boy up. But after reading how to, how not to, how to avoid, etc etc it seems that either: a. I am over complicating it, or b. it would be easier, albeit not as much fun, if I just stayed stock due to the overwhelming ways to brick such a (from what I can tell) fragile device. Now I am in no ways new to rooting and all this jazz but it just seems like the risk might overweigh the outcome of rooting and hard bricking my epic 4g touch device?
so this is where I turn to you, the veteran users of the epic 4g touch. What are your thoughts, tips, tricks, advice, or kicks in the right direction?
any help is much appreciated
Just root the phone already
Read the directions and most of a thread before flashing a new rom and you will have very minimal risk.
root it.
I also came from the OG Evo and was hesitant at first, just do a lot of reading and also get to know PC Odin. Also, if you haven't updated to the latest OTA you could just install that root exploit app to obtain root. Probably the easiest way to root unless you took the new OTA update.
Just read as much as you can before you flash anything and always read the instructions in the OP.
evathaevo said:
So I recently cut ties with my rooted OG evo :'( and have switched to a sprint galaxy s2, aka the epic 4g touch fi27. The first thing I did was head over to these forums because of course my first thought was let's open this bad boy up. But after reading how to, how not to, how to avoid, etc etc it seems that either: a. I am over complicating it, or b. it would be easier, albeit not as much fun, if I just stayed stock due to the overwhelming ways to brick such a (from what I can tell) fragile device. Now I am in no ways new to rooting and all this jazz but it just seems like the risk might overweigh the outcome of rooting and hard bricking my epic 4g touch device?
so this is where I turn to you, the veteran users of the epic 4g touch. What are your thoughts, tips, tricks, advice, or kicks in the right direction?
any help is much appreciated
Click to expand...
Click to collapse
You could always just go stock rooted. It's really not that hard to not brick the device, just follow directions and don't skip any steps trying to save time.
I like to break stuff!
Raistlin1 said:
I also came from the OG Evo and was hesitant at first, just do a lot of reading and also get to know PC Odin. Also, if you haven't updated to the latest OTA you could just install that root exploit app to obtain root. Probably the easiest way to root unless you took the new OTA update.
Just read as much as you can before you flash anything and always read the instructions in the OP.
Click to expand...
Click to collapse
From what I understand sprint pushes ota's when you activate a new phone so unfortunately I'm stuck on fi27 even if I didn't want to. does that make a difference?
evathaevo said:
From what I understand sprint pushes ota's when you activate a new phone so unfortunately I'm stuck on fi27 even if I didn't want to. does that make a difference?
Click to expand...
Click to collapse
Actually FI27 is the version right before the new OTA, the newest version is FL24 that has just been released and just being pushed out now. My wife's phone just received that OTA but mine has not yet.
Raistlin1 said:
Actually FI27 is the version right before the new OTA, the newest version is FL24 that has just been released and just being pushed out now. My wife's phone just received that OTA but mine has not yet.
Click to expand...
Click to collapse
so root exploit would be the way to go?
evathaevo said:
so root exploit would be the way to go?
Click to expand...
Click to collapse
You can either oneclick to root or use exynos abuse apk to root on fi27 if you want to stay stock rooted for now I'd just use the exynos abuse method and then if you decide you want to flash something later use mobile odin or mobile odin pro to flash a kernel+recovery without increasing your flash counter
I like to break stuff!
Rooting in and of itself doesn't present a risk as far as the bricking you're referring to goes. It's when you start messing around with unsafe kernels/recoveries that it becomes an issue, but all of the modern kernels/recoveries are safe.
Thanks for all the input guys. I really appreciate it. After much research I've realized that all I'm looking for is jelly bean on my e4gt because that's what i had running on my OG Evo and I've come across a confusing issue. It seems that it is possible to flash jb through Odin without having root. Now coming from my evo this sounds too good to be true but is it?
Sent from my SPH-D710 using xda app-developers app
Yeah, you can definitely flash stock ROM images through Odin without having root. Samsung devices have a download mode for emergency recovery that allows you to do such things in Odin. However, I believe it's limited to the stock images (and the stock images can be pre-rooted), so if you want an AOSP-based ROM instead of TouchWiz, you'll still need to flash it through custom recovery after you're rooted. Also, be aware that flashing ROM images with Odin will completely wipe your device, so back up anything you want to save before you do it.
evathaevo said:
Thanks for all the input guys. I really appreciate it. After much research I've realized that all I'm looking for is jelly bean on my e4gt because that's what i had running on my OG Evo and I've come across a confusing issue. It seems that it is possible to flash jb through Odin without having root. Now coming from my evo this sounds too good to be true but is it?
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
if you want cm or aokp you'll need to odin a custom safe recovery then flash those roms.
I know how you feel about all of this. I'm pretty sure I posted something awhile back about this when I first got the phone. It definitely seems like a lot when you don't know how to do much. It's actually quite simple, as as stated above, as long as you follow directions you will be good to go! :good:
Let me see if I can give you some guide on how I learned how to do things to kind of just get in the groove of it.
First things first, you are going to want to check out this page:
http://forum.xda-developers.com/showthread.php?t=1416477
On that page you will be able to download the PC ODIN for stock rooted Gingerbread. You will run that in download mode on your phone (Vol Down + Power.) Make sure you have the Samsung drivers installed on your computer which you can also get from that link. Just follow the instructions to get that installed and you should be good to go. When it is done you can go to Settings > About Phone and make sure that you are running Android 2.3.6 or Gingerbread and you are now rooted at this point (look for the superuser icon.)
After that is done go ahead and check out this page:
http://forum.xda-developers.com/showthread.php?t=1342728
This is the auto root package that will give you the custom recovery that you will want to use for flashing. There is a file in the rar that is called "RUNFIRST" which, obviously, you will run first. It will bring up a Command Prompt for you to type in selections. Since you are running EL26 at this point you will want to hit "C." This next selection page is your recovery selection.
Look down for EL26 and we recommend Chris41g's recovery. The other is Rogue which you can't do too much with. You will want to make sure you go into Settings > Applications and check the box for USB Debugging. Plug the phone back in, and hit "I" <==-- Capital EYE to avoid confusion, and let it do it's work. It will restart the phone, and if all was successful you will now be rooted with a recovery that you can flash from. EL26 recovery is the most recommended recovery to flash from for any ROM. Power down, and use Vol Up + Power to enter your recovery mode.
Using the volume rocker you can hit up + down + up + down to activate the power button selection and from here you can now flash a ROM zip of your choice. If you are looking for a Jelly Bean ROM, might I recommend Sniper's PACman JB ROM that you can find here:
http://forum.xda-developers.com/showthread.php?t=2050948
Good luck!
Be sure to also check out this link:
http://forum.xda-developers.com/showthread.php?t=1525495
That will help you get an idea of things you can do to prevent bricking in the future.
crkdslider said:
I know how you feel about all of this. I'm pretty sure I posted something awhile back about this when I first got the phone. It definitely seems like a lot when you don't know how to do much. It's actually quite simple, as as stated above, as long as you follow directions you will be good to go! :good:
Let me see if I can give you some guide on how I learned how to do things to kind of just get in the groove of it.
First things first, you are going to want to check out this page:
http://forum.xda-developers.com/showthread.php?t=1416477
On that page you will be able to download the PC ODIN for stock rooted Gingerbread. You will run that in download mode on your phone (Vol Down + Power.) Make sure you have the Samsung drivers installed on your computer which you can also get from that link. Just follow the instructions to get that installed and you should be good to go. When it is done you can go to Settings > About Phone and make sure that you are running Android 2.3.6 or Gingerbread and you are now rooted at this point (look for the superuser icon.)
After that is done go ahead and check out this page:
http://forum.xda-developers.com/showthread.php?t=1342728
This is the auto root package that will give you the custom recovery that you will want to use for flashing. There is a file in the rar that is called "RUNFIRST" which, obviously, you will run first. It will bring up a Command Prompt for you to type in selections. Since you are running EL26 at this point you will want to hit "C." This next selection page is your recovery selection.
Look down for EL26 and we recommend Chris41g's recovery. The other is Rogue which you can't do too much with. You will want to make sure you go into Settings > Applications and check the box for USB Debugging. Plug the phone back in, and hit "I" <==-- Capital EYE to avoid confusion, and let it do it's work. It will restart the phone, and if all was successful you will now be rooted with a recovery that you can flash from. EL26 recovery is the most recommended recovery to flash from for any ROM. Power down, and use Vol Up + Power to enter your recovery mode.
Using the volume rocker you can hit up + down + up + down to activate the power button selection and from here you can now flash a ROM zip of your choice. If you are looking for a Jelly Bean ROM, might I recommend Sniper's PACman JB ROM that you can find here:
http://forum.xda-developers.com/showthread.php?t=2050948
Good luck!
Be sure to also check out this link:
http://forum.xda-developers.com/showthread.php?t=1525495
That will help you get an idea of things you can do to prevent bricking in the future.
Click to expand...
Click to collapse
VERY informative and VERY helpful. thank you so much. I wish I could click thanks twice
evathaevo said:
VERY informative and VERY helpful. thank you so much. I wish I could click thanks twice
Click to expand...
Click to collapse
You are welcome!
Sent from my Galaxy SII Epic 4G Touch via Tapatalk.
crkdslider said:
I know how you feel about all of this. I'm pretty sure I posted something awhile back about this when I first got the phone. It definitely seems like a lot when you don't know how to do much. It's actually quite simple, as as stated above, as long as you follow directions you will be good to go! :good:
Let me see if I can give you some guide on how I learned how to do things to kind of just get in the groove of it.
First things first, you are going to want to check out this page:
http://forum.xda-developers.com/showthread.php?t=1416477
On that page you will be able to download the PC ODIN for stock rooted Gingerbread. You will run that in download mode on your phone (Vol Down + Power.) Make sure you have the Samsung drivers installed on your computer which you can also get from that link. Just follow the instructions to get that installed and you should be good to go. When it is done you can go to Settings > About Phone and make sure that you are running Android 2.3.6 or Gingerbread and you are now rooted at this point (look for the superuser icon.)
After that is done go ahead and check out this page:
http://forum.xda-developers.com/showthread.php?t=1342728
This is the auto root package that will give you the custom recovery that you will want to use for flashing. There is a file in the rar that is called "RUNFIRST" which, obviously, you will run first. It will bring up a Command Prompt for you to type in selections. Since you are running EL26 at this point you will want to hit "C." This next selection page is your recovery selection.
Look down for EL26 and we recommend Chris41g's recovery. The other is Rogue which you can't do too much with. You will want to make sure you go into Settings > Applications and check the box for USB Debugging. Plug the phone back in, and hit "I" <==-- Capital EYE to avoid confusion, and let it do it's work. It will restart the phone, and if all was successful you will now be rooted with a recovery that you can flash from. EL26 recovery is the most recommended recovery to flash from for any ROM. Power down, and use Vol Up + Power to enter your recovery mode.
Using the volume rocker you can hit up + down + up + down to activate the power button selection and from here you can now flash a ROM zip of your choice. If you are looking for a Jelly Bean ROM, might I recommend Sniper's PACman JB ROM that you can find here:
http://forum.xda-developers.com/showthread.php?t=2050948
Good luck!
Be sure to also check out this link:
http://forum.xda-developers.com/showthread.php?t=1525495
That will help you get an idea of things you can do to prevent bricking in the future.
Click to expand...
Click to collapse
Thanks for the recommendation. I still think the exynos abuse app would be easier
Turn on outside sources, install the app, root, install mobile odin and the flash kernel apks, flash the el26 cwm tar, flash PACman from recovery
Sent from my SPH-D710 using Tapatalk
LightWeight ? PACman ? PA
I'm on Sniper's PACman rom, and it's good. I much prefer it to stock TouchWiz. If you like the stock TW interface, but want jellybean, have a look at Rwilco's 1-click packages. They make flashing and rooting a snap, and the ones I've used don't trigger the yellow triangle or increase your flash counter (if that matters to you). I stuck with FK23 for quite a while (almost a month), and then did something stupid, so I flashed to FL04 then later to PACman.
I am new to rooting phones and like you a bit overwhelmed at all the information. I finally found this Youtube video that is VERY good and makes rooting easy if you are looking to stock root your phone.
http://www.youtube.com/watch?v=jyEvJ92to64
tl;dr I have a blue LED showing up in the top left of the phone and nothing showing up on the screen after the SAMSUNG logo appears. I do hear the Sprint 4G LTE music, but that's it. The screen is off.
NOTE: I'm running Sprint's stock 4.1.1 ROM rooted.
Other threads I looked at (neither is the same issue):
http://forum.xda-developers.com/showthread.php?t=581929
http://forum.xda-developers.com/showthread.php?t=1792477
I had my first OTA update appear today. When I ran the update, Clockwork showed up and upon hitting "Yes", it failed. I looked around online and found this guide to reverse my rooting: http://www.epiccm.org/2012/06/sprint-sgs3-stock-restore.html
I was able to successfully flash TeamEpic-RemoveRoot-from-Recovery-signed.zip, but I didn't hit the keys right for the next one and ended up booting into the OS.
After restarting the phone, I hit the right keys and started ODIN. I saw COM show up in blue and put the TeamEpic-Sprint-SGS3-stock-boot-and-recovery.tar.md5 file in the PDA area then hit Start. I got a green PASS and then closed Odin and waited.
The phone had a black screen with that blue LED in the top left. I waited a while and then just powered it off. Took out the battery and tried again, same thing; although, the SAMSUNG logo does show up. It turns off when the Sprint part is supposed to show and at that moment I can hear the audio but the screen turns off. In this mode, the phone gets very very hot.
I can still boot into the stock recovery, but I can't do much else.
I just wanted the OTA . Does anyone know what might be happening?
EDIT: I put Clockwork Recovery back on, and then Advanced Recovered the boot part of a backup I did before this mess. Surprisingly, that worked. Problem is, I still haven't gotten the OTA working.
Ideas?
Just odin the stock tar
Sent from my SPH-L710 using xda app-developers app
CrfEpic4g said:
Just odin the stock tar
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
What do you mean by that? Which stock tar?
I think the latest tar we have is still Lj7 but idk. just flash the lj7 tar in odin and update to the latest ill try and find it for you
Sent from my SPH-L710 using xda app-developers app
---------- Post added at 08:50 AM ---------- Previous post was at 08:47 AM ----------
http://www.hotfile.com/dl/161492098/9fa8372/L710VPALEN_L710SPRALEN_SPR.zip.html
Theres a link to lj7 just download that flash it in odin and youll be back to stock. Then all you have to do is update to mb1.
Sent from my SPH-L710 using xda app-developers app
Saturn2888 said:
tl;dr I have a blue LED showing up in the top left of the phone and nothing showing up on the screen after the SAMSUNG logo appears. I do hear the Sprint 4G LTE music, but that's it. The screen is off.
NOTE: I'm running Sprint's stock 4.1.1 ROM rooted.
Other threads I looked at (neither is the same issue):
http://forum.xda-developers.com/showthread.php?t=581929
http://forum.xda-developers.com/showthread.php?t=1792477
I had my first OTA update appear today. When I ran the update, Clockwork showed up and upon hitting "Yes", it failed. I looked around online and found this guide to reverse my rooting: http://www.epiccm.org/2012/06/sprint-sgs3-stock-restore.html
I was able to successfully flash TeamEpic-RemoveRoot-from-Recovery-signed.zip, but I didn't hit the keys right for the next one and ended up booting into the OS.
After restarting the phone, I hit the right keys and started ODIN. I saw COM show up in blue and put the TeamEpic-Sprint-SGS3-stock-boot-and-recovery.tar.md5 file in the PDA area then hit Start. I got a green PASS and then closed Odin and waited.
The phone had a black screen with that blue LED in the top left. I waited a while and then just powered it off. Took out the battery and tried again, same thing; although, the SAMSUNG logo does show up. It turns off when the Sprint part is supposed to show and at that moment I can hear the audio but the screen turns off. In this mode, the phone gets very very hot.
I can still boot into the stock recovery, but I can't do much else.
I just wanted the OTA . Does anyone know what might be happening?
EDIT: I put Clockwork Recovery back on, and then Advanced Recovered the boot part of a backup I did before this mess. Surprisingly, that worked. Problem is, I still haven't gotten the OTA working.
Ideas?
Click to expand...
Click to collapse
Why are you so intent on taking the OTA? Freeza has a stock rooted ROM over in his thread. And if you want just update the baseband, just flash the "MB1 Firmware/modem/baseband update" file in the aforementioned thread.
If you're already rooted with a custom recovery (which you were/are), there's no reason to unroot just to flash the OTA. Freeza typically has his stock rooted ROM updated with the OTA within a week of it being released. In my area OTAs are kind of late, so he typically gets it out before I even see the notification.
So, in summary. OTAs are not required, XDA (and Freeza in particular) has you covered.
topherk said:
Why are you so intent on taking the OTA? Freeza has a stock rooted ROM over in his thread. And if you want just update the baseband, just flash the "MB1 Firmware/modem/baseband update" file in the aforementioned thread.
If you're already rooted with a custom recovery (which you were/are), there's no reason to unroot just to flash the OTA. Freeza typically has his stock rooted ROM updated with the OTA within a week of it being released. In my area OTAs are kind of late, so he typically gets it out before I even see the notification.
So, in summary. OTAs are not required, XDA (and Freeza in particular) has you covered.
Click to expand...
Click to collapse
I'll go ahead and give it a try then. I haven't ever had a ROM update since I got the phone in October so I figure the upgrade won't work right, and I'll need the full ROM. Currently doing a backup.
Does flashing a ROM affect all app settings? And if so, by that point I'd just wanna have another ROM. The main reason I am fine w/ the stock ROM rooted is bc all my settings and apps are already installed and configured as well as the fact that I know it will work properly. So if this removes my settings, no reason to go stock anymore aside from the fact that I've seen that CyanogenMod doesn't get as good of signal on the S III as stock-based ROMs. Do you know if this still true?
Saturn2888 said:
I'll go ahead and give it a try then. I haven't ever had a ROM update since I got the phone in October so I figure the upgrade won't work right, and I'll need the full ROM. Currently doing a backup.
Does flashing a ROM affect all app settings? And if so, by that point I'd just wanna have another ROM. The main reason I am fine w/ the stock ROM rooted is bc all my settings and apps are already installed and configured as well as the fact that I know it will work properly. So if this removes my settings, no reason to go stock anymore aside from the fact that I've seen that CyanogenMod doesn't get as good of signal on the S III as stock-based ROMs. Do you know if this still true?
Click to expand...
Click to collapse
Strange. I upgraded the ROM by flashing, everything seemed to work as I'm at 4.1.2 now, but the Upgrade notification is still there for some reason. Is there any way to tell the phone it's been upgraded?
Saturn2888 said:
Strange. I upgraded the ROM by flashing, everything seemed to work as I'm at 4.1.2 now, but the Upgrade notification is still there for some reason. Is there any way to tell the phone it's been upgraded?
Click to expand...
Click to collapse
Setting >scroll all the way to the bottom >about phone>read what it say there. If it says your on latest then it should be ok you may have to clear some things and if it doesn't say latest just edit the build prop.
Go to this thread by Cnexus and follow all instructions http://forum.xda-developers.com/showthread.php?p=39627397
Transmitted with a portable device using Xparent Blue Tapatalk 2
Saturn2888 said:
Strange. I upgraded the ROM by flashing, everything seemed to work as I'm at 4.1.2 now, but the Upgrade notification is still there for some reason. Is there any way to tell the phone it's been upgraded?
Click to expand...
Click to collapse
Are you on MB1 or MA6?
Just flash an updated rom, or follow the instructions in my OTA thread for how to get rid of it
Saturn2888 said:
I'll go ahead and give it a try then. I haven't ever had a ROM update since I got the phone in October so I figure the upgrade won't work right, and I'll need the full ROM. Currently doing a backup.
Does flashing a ROM affect all app settings? And if so, by that point I'd just wanna have another ROM. The main reason I am fine w/ the stock ROM rooted is bc all my settings and apps are already installed and configured as well as the fact that I know it will work properly. So if this removes my settings, no reason to go stock anymore aside from the fact that I've seen that CyanogenMod doesn't get as good of signal on the S III as stock-based ROMs. Do you know if this still true?
Click to expand...
Click to collapse
If you dirty flash the rom over whatever you had before, it should not affect any settings
CNexus said:
Are you on MB1 or MA6?
Just flash an updated rom, or follow the instructions in my OTA thread for how to get rid of it
If you dirty flash the rom over whatever you had before, it should not affect any settings
Click to expand...
Click to collapse
MB1 as of now. What do you mean by dirty flash the rom?
edfunkycold said:
Setting >scroll all the way to the bottom >about phone>read what it say there. If it says your on latest then it should be ok you may have to clear some things and if it doesn't say latest just edit the build prop.
Go to this thread by Cnexus and follow all instructions http://forum.xda-developers.com/showthread.php?p=39627397
Transmitted with a portable device using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
I think the message isn't showing up anymore bc it hasn't bugged me at all today. Device Status is and has always been "Modified" anyway.
Thanks!
Saturn2888 said:
MB1 as of now. What do you mean by dirty flash the rom?
I think the message isn't showing up anymore bc it hasn't bugged me at all today. Device Status is and has always been "Modified" anyway.
Thanks!
Click to expand...
Click to collapse
A dirty flash is when you flash without clearing anything, and that's why no data is lost when you do one of those. However it can lead to issues, so i would advise against it when possible
CNexus said:
A dirty flash is when you flash without clearing anything, and that's why no data is lost when you do one of those. However it can lead to issues, so i would advise against it when possible
Click to expand...
Click to collapse
Yeah, last time I did that, the system wouldn't boot.