I had a epic4g that updated to ec05 ok, ran ok, then I got brave and wanted to try gb, so I loaded up eh17. That went fairly ok, until I decided I wanted to go back to ec05 in prep for the final release of gb and because certain apps weren't working yet because it was a gb release. Thing is, I tried 3 different ec05 roms, including the supposed stock ec05 release and none of them would take. I eventually had to use cwm and restore a nandroid backup I had made before the attempt to get the phone to even work right. I'm feeling daring again and still want to go back to stock ec05, although I will stay rooted. Thing is, there are alot of ec05 roms out there from Bonzai to Syndicate and I'm not sure which one would be the most stable and most likely to give me the least hassle. I know I have to use Odin to first re-flash the ec05 modem, I had no problems with that last time. It was a matter of which pit file to use, which ROM and which cable/usb port would work and even that took about literally 50 tries before it worked right... the couple of times I was able to flash back to ec05 ok, the phone just fc'd like mad, even trying to make a basic phone call... and that was after using cwm 3.1.0.1 to do a cache/data/factory wipe 3x's each. Is there a particularly good stock ec05 ROM I should focus on this time? At work, I have a decent internet connection and can download a 200mb ROM in minutes... at home, where I'll have time to undertake this, my internet is pretty much non-existant, so I need to download whatever ROM I'm going to use now because I won't be able to download a different one tomorrow.
Thanks.
~Mark/Zeoran
I've played around with most EC05 roms listed here on XDA, and currently my daily driver is RandomRom 2.2 Phoenix. The ERA roms are super fast and slim (with the fat free or reduced fat versions) SFR 1.2 is also good and stable. It's really personal preference. I'd say grab 2-3 and flash em, play with em for a couple days a piece, see which one works best on your phone (different phones, different results) and go from there.
Ok, so i did a full nandroid backup, grabbed a few rom's while I was at work and tried to install one of them today. First, I backed everything up, then I odin'd a stock ec05 modem, then I went into cwm3.1.0.1 and first did a factory wipe 3x's, wipe cache 3x's, then wipe davlik 3x's, then installed the sfr1.2 latest rom, then installed the genocide 1.1 final kernal, which was suggested by the gbking77 video. It ran ok for a bit, but kept randomly rebooting alot, the same problem I had with EH17. So I went back into cwm and tried a different kernal. This time it was worse. I've tried going back to the genocide kernal, but it's not booting up worth a damn...it boots, shows me the lock screen and stays locked until it reboots anywhere from 1-3 minutes later... WHAT THE HELL IS GOING ON????
Did you just Odin the modem, if so I found I would do this.
http://forum.xda-developers.com/showthread.php?t=1052813
This will make it completely stock EC05. Not just the modem.
Related
I flashed to the newest SyndicateFrozen and it worked great until I started using the Browser. It locked up and I had to pull the battery. Same results with Dolphin Mini, DolphinHD, and the new Firefox. Anybody know if I missed something on the Syndicate page? Right now I'm going back to the Samsung distributed EB13 until I can find more information about this.
atomiksnowman said:
I flashed to the newest SyndicateFrozen and it worked great until I started using the Browser. It locked up and I had to pull the battery. Same results with Dolphin Mini, DolphinHD, and the new Firefox. Anybody know if I missed something on the Syndicate page? Right now I'm going back to the Samsung distributed EB13 until I can find more information about this.
Click to expand...
Click to collapse
That happend to me like 3 times... but not on dolphin browser HD.
Sent from my SPH-D700 using XDA App
atomiksnowman said:
I flashed to the newest SyndicateFrozen and it worked great until I started using the Browser. It locked up and I had to pull the battery. Same results with Dolphin Mini, DolphinHD, and the new Firefox. Anybody know if I missed something on the Syndicate page? Right now I'm going back to the Samsung distributed EB13 until I can find more information about this.
Click to expand...
Click to collapse
Have you tried clearing your cache, sometimes doing this helps. If not redoing the odin to EC05 has worked for me with other issues like force close.
deano0714 said:
That happend to me like 3 times... but not on dolphin browser HD.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I ended up using Samsung's EB13 update to get back to stock Froyo. Then installed CWM 2.5 with oneclick and restored my backup from after I had installed Syndicate Frozen (it's been a very slow day at work, I have time to mess around) and it seems to work with all browsers now. Essentially the only difference is I kept it from upgrading to EXT4.
I ran some benchmarks, which were quite underwhelming (seeing as when I was running DK28 they were well over this)
Quadrant: 1032
Linpack: 13.92
Smartbench 2010: 1093/2462 (also well under the 1ghz for stock Epic 4g 2.2)
If you get freezes regularly in anything at all, read the message that has been posted many times about using an alternate kernel. You can also try VisionKernel in lieu of the one linked clearly throughout the thread and in the second post under Changelog.
I should have included in the original post that I did a lot of searching throughout the thread and tried loading the Twilight_Zone kernel as recommended. After that my phone wouldn't load. I tried reloading the original modem with ODIN and nothing. I tried restoring to various backup points and just decided a fresh start was fine with me.
I hadn't seen anything about Visor Kernal. I'll give that a shot another day, but for today I'm wiped out on monkeying with this thing. I'm just glad I have a stable phone at the end of the day.
I should also note what I've done since.
I used Samsung's tool to get back to stock Froyo. Then used one click root to get CWM 2.5 back on there and restored the backup that I had made AFTER installing the Syndicate Frozen ROM. That was on accident, I had a lot of backups on there and wasn't sure which one was which. It loaded up perfectly fine. So I'm running Syndicate Frozen, but without CWM3 (and I suppose without EXT4 filesystem). And it works fine right now.
atomiksnowman said:
I should also note what I've done since.
I used Samsung's tool to get back to stock Froyo. Then used one click root to get CWM 2.5 back on there and restored the backup that I had made AFTER installing the Syndicate Frozen ROM. That was on accident, I had a lot of backups on there and wasn't sure which one was which. It loaded up perfectly fine. So I'm running Syndicate Frozen, but without CWM3 (and I suppose without EXT4 filesystem). And it works fine right now.
Click to expand...
Click to collapse
That's not a recommended configuration in the slightest.
I had the same problems even with the other kernel. I finally went to Bonsai 4.0 with EC05 and I have not had my phone freeze.
Its nice.
for me it happened in dolphin hd hasnt yet in stock browser
atomiksnowman said:
I should also note what I've done since.
I used Samsung's tool to get back to stock Froyo. Then used one click root to get CWM 2.5 back on there and restored the backup that I had made AFTER installing the Syndicate Frozen ROM. That was on accident, I had a lot of backups on there and wasn't sure which one was which. It loaded up perfectly fine. So I'm running Syndicate Frozen, but without CWM3 (and I suppose without EXT4 filesystem). And it works fine right now.
Click to expand...
Click to collapse
So.. A eb13 modem and a ext4 backup running on stock file system...
I predict big problems on the horizon
tmspyder said:
So.. A eb13 modem and a ext4 backup running on stock file system...
I predict big problems on the horizon
Click to expand...
Click to collapse
Everything worked perfectly until I tried to pair Bluetooth. Then she froze. I couldn't get it to fail any other way than with bluetooth. Fun experiment, though. I though I had a backup from before using CWM to convert to EXT4, but that isn't the case. I'm now running EB13 on CWM3 (which converted to EXT4, but no problems in the 12 hours I've given it).
My main reason for starting this Q&A post was to point out that I had tried the ROM and its recommend fixes that I could find in what I consider a reasonable amount of time/searching so that the developer might catch it and look into it if he/she so desired.
I want to note that I don't feel entitled to anyone's hard work other than my own. I'm perfectly happy following all instructions and finding that for me it didn't work. I might get a little miffed if I brick the phone but Samsung has made a product that remains quite resilient after all the modding real developers do, and the torture we tinkerers do. So to k0nane especially, thanks for the hard work. I'll keep reading through the forum and maybe try what Badbeats suggested with Bonsai 4.0 some time next week when I'm not so busy at work.
Seriously, you developers are amazing.
I had flashed SRF 1.1.0 and was running it with no issues. I tried the Vision kernel and got random lockups mostly after being plugged in and unused for awhile (maybe an hour or so). I flashed back to the Twighlight Kernel and it's been solid as a rock.
Being that I've only owned the phone a few weeks and have flashed/restored it at least a dozen times, I feel confident that it's running stable at this point. Once you mess it up a few times, you'll learn pretty quickly
Has anyone had a similar issue? Know a fix?
I got this phone, activated, ran the stock EC05 rom for a day or so, and decided to root and flash a custom rom. I used syndicate frozen 1.1 with the voodoo kernel and clockworkmod 2.xxx (don't recall now) for the flash. This was following the guide posted in on youtube for syndicate 1.1.0 found in said thread. This tutorial was basically one click root-> wipe the junk 3x-> flash rom-> flash kernel-> wipe junk again-> reboot. First thing I got loading up was a force lose on setup wizard. No options, just a black screen with a task bar. I fought with it, and found that if I removed setup wizard from the rom, it would boot, but no unlock screen, no search button, and no home button among other things. This was done twice to check the installation and re-downloaded in between for integrity.
Now I odin back to stock EC05 with the tutorial for restoring an almost bricked epic, and wipe everything by doing so. The phone boots normal and all is well stock and boring.
Next I decided to upgrade to new software. Flash Clockworkmod purple (newest version), Boot into recovery, wipe junk 3x (Data Cache Delvik) then Syndicate Frozen 1.2-> TwilightZone 1.1.1 (just so I had a different kernel for comparison)-> wipe junk 3x-> reboot. Still force closing on setup wizard.
Final straw: Blow it all away with odin back to stock EC05. All boots and works well. Install 1 click root, boot into recovery with stock rom and wipe data/cache/delvik and wipe the junk. Reboot and BAM, setup wizard force close. It seems as though something is getting trashed by clockworkmod on both versions I tried. I'm not new to debugging, but I've been using the Touch Pro 2 for the last year and a half. This thing is a different animal with the same 1 year learning curve. It's been 5 days. Still getting used to all this. I only followed the tutorials to be sure it was done correctly.
Can anyone report something similar or even a fix for this? I've searched my butt off, but the search terms used to find such a problem are going to throw you insane results no matter what. Coming out of the shadows is my only option.
I tried to keep it short. Sorry.
BoominSVX said:
Has anyone had a similar issue? Know a fix?
I got this phone, activated, ran the stock EC05 rom for a day or so, and decided to root and flash a custom rom. I used syndicate frozen 1.1 with the voodoo kernel and clockworkmod 2.xxx (don't recall now) for the flash. This was following the guide posted in on youtube for syndicate 1.1.0 found in said thread. This tutorial was basically one click root-> wipe the junk 3x-> flash rom-> flash kernel-> wipe junk again-> reboot. First thing I got loading up was a force lose on setup wizard. No options, just a black screen with a task bar. I fought with it, and found that if I removed setup wizard from the rom, it would boot, but no unlock screen, no search button, and no home button among other things. This was done twice to check the installation and re-downloaded in between for integrity.
Now I odin back to stock EC05 with the tutorial for restoring an almost bricked epic, and wipe everything by doing so. The phone boots normal and all is well stock and boring.
Next I decided to upgrade to new software. Flash Clockworkmod purple (newest version), Boot into recovery, wipe junk 3x (Data Cache Delvik) then Syndicate Frozen 1.2-> TwilightZone 1.1.1 (just so I had a different kernel for comparison)-> wipe junk 3x-> reboot. Still force closing on setup wizard.
Final straw: Blow it all away with odin back to stock EC05. All boots and works well. Install 1 click root, boot into recovery with stock rom and wipe data/cache/delvik and wipe the junk. Reboot and BAM, setup wizard force close. It seems as though something is getting trashed by clockworkmod on both versions I tried. I'm not new to debugging, but I've been using the Touch Pro 2 for the last year and a half. This thing is a different animal with the same 1 year learning curve. It's been 5 days. Still getting used to all this. I only followed the tutorials to be sure it was done correctly.
Can anyone report something similar or even a fix for this? I've searched my butt off, but the search terms used to find such a problem are going to throw you insane results no matter what. Coming out of the shadows is my only option.
I tried to keep it short. Sorry.
Click to expand...
Click to collapse
Only wipe 3x before flashing, not after! Wiping after flashing just removes everything you did! Odin to stock ec05, one click root, wipe data/cache/dalvik 3x, flash srf 1.2, flash kernel immediately after, then turn on the phone.
Please click both links below and vote: http://picketfenceblogs.com/vote/3616
http://apps.facebook.com/gerberphotosearch/entry/935/amber.aspx
HAHAHA!!! And the dumbass award goes tooo......
I'm not going to edit though. Just incase someone else goes newb for a minute or 5 days. lol. Nice job on the quick answer though. Thanks
BoominSVX said:
HAHAHA!!! And the dumbass award goes tooo......
I'm not going to edit though. Just incase someone else goes newb for a minute or 5 days. lol. Nice job on the quick answer though. Thanks
Click to expand...
Click to collapse
No problem. The exclamation points were only for emphasis. Don't worry about it, I was the same way just a couple of months ago, just ask around lol.
Please click both links below and vote: http://picketfenceblogs.com/vote/3616
http://apps.facebook.com/gerberphotosearch/entry/935/amber.aspx
I tried to downgrade from EH17 to EC05 stock through Odin. I used the official tar first and then tried the plus tar. Neither would complete in odin and just hung; no error or fail. My Epic display however did turn blue on 2 occasions. I used the 1.6 and 1.8 odins and neither worked.
I then tried to flash back to the EH17 stock with root and that didn't work until like the 3rd try. Anybody have issues with going back to EC05 and is it worth the effort? I'm just bored and didn't have any issues whatsoever on the GB builds so based off of that....am I missing anything?
Gorguts said:
I tried to downgrade from EH17 to EC05 stock through Odin. I used the official tar first and then tried the plus tar. Neither would complete in odin and just hung; no error or fail. My Epic display however did turn blue on 2 occasions. I used the 1.6 and 1.8 odins and neither worked.
I then tried to flash back to the EH17 stock with root and that didn't work until like the 3rd try. Anybody have issues with going back to EC05 and is it worth the effort? I'm just bored and didn't have any issues whatsoever on the GB builds so based off of that....am I missing anything?
Click to expand...
Click to collapse
Sounds like your cable is going bad. Time for a heavy duty cable. I am using the one from my Palm Pre and works perfect everytime.
I moved to GB and never looked back. EH17 rebooted at least 2 times a day after the 4th day so ended up going back to EG22. The only issues that has is stock browser won't download from dropbox links so got another browser and alarm wouldn't play in silent mode so got Extreme Alarm. Don't know what advantage going back to EC05 would give you. Many go back because of the reboot issue and can't get decent GPS to work. I can still get 5 out 10 locks so will do for now. If you use GPS constantly for directions then EC05 was way superior.
Odin is Version 1.81, have had no issues with since I have been flashing!
Link for Odin:
http://www.multiupload.com/I6GVRDL0VK
Link for ECO5:
Froyo EC05 (do not extract this file)
---------- Post added at 10:20 AM ---------- Previous post was at 10:17 AM ----------
Here is link for EC05 file. It is part way down in Green Square, if you cannot see you have to sign up to download. Become a Member.
http://forums.androidcentral.com/ep...68-how-factory-restore-fix-bricked-phone.html
---------- Post added at 10:23 AM ---------- Previous post was at 10:20 AM ----------
If you still want to downgrade, you might have to go down to DI18 or EB13 then update to EC05.
That is another Way to do it.
Need Help, Repost we can get you links if you cannot find them.
Gorguts said:
I tried to downgrade from EH17 to EC05 stock through Odin. I used the official tar first and then tried the plus tar. Neither would complete in odin and just hung; no error or fail. My Epic display however did turn blue on 2 occasions. I used the 1.6 and 1.8 odins and neither worked.
I then tried to flash back to the EH17 stock with root and that didn't work until like the 3rd try. Anybody have issues with going back to EC05 and is it worth the effort? I'm just bored and didn't have any issues whatsoever on the GB builds so based off of that....am I missing anything?
Click to expand...
Click to collapse
Flashing the sfr zip right over your gb leak (and also a kernel) works just fine. Ive done it on several occasions. Only issue I had was restoring data from a nandroid. Doing so would lock my epic into an upside down landscape view, so I had to rebuild from a clean install and just used some titanium backup restores sparingly.
Sent from a secret underground bunker
You know what's weird I had some issues going from EH17 to EC05 also... but I traced it down(hopefully) to a bad .tar (even though I succesfully odin'd at least 5 times with that same tar with all 5 previously being successful.
Sent from my SPH-D700
If you wanted to do a clean install and you were already on EC05, would a factory reset (settings/Factory reset) be just as good or would you want to reinstall either the EC05 or original stock DI07 file and do OTAs? What's the advantage of one over the other?
rando991 said:
If you wanted to do a clean install and you were already on EC05, would a factory reset (settings/Factory reset) be just as good or would you want to reinstall either the EC05 or original stock DI07 file and do OTAs? What's the advantage of one over the other?
Click to expand...
Click to collapse
You know, there are two different schools of thought on this. Some always go back and use the OTA updates and some never do. I used to go back to EB13 and take the OTA but now I just go straight to what I want. A custom ROM is going to replace everything anyway
Sent from my SPH-D710 using xda premium
Yeah, I have been using the Factory Data reset a lot more. Then restore only apps, no data except what you must have. Phone always seems faster and smoother for awhile.
kennyglass123 said:
Yeah, I have been using the Factory Data reset a lot more. Then restore only apps, no data except what you must have. Phone always seems faster and smoother for awhile.
Click to expand...
Click to collapse
Thanks, another question, Factory Reset won't remove root or CWM will it?
Ive never had a problem going from EH17 or any other GB leak to EC05 but i have occasionally had issues with a bad USB cord or bad tar. Also going straight to whatever build you want might be better that OTA updates. As i recall there can be issues with OTA updates which can cause problems down the road. Of course thats just my personal opinion
Well my cable was bad but that did not help with flashing ROMS. I have been dloading from the device though so I will get fresh dloads from the PC.
On a side note, I used the SW tool and flashed back to EB13 then took the upgrade prompt back too EC05. Been rollin' stock just for kicks and I noticed that the stock ROM runs faster then it use to but the graphics in the GUI get a little stuttery here and there. The scrolling and gallery interface are where it is most noticable.
I can't wait till they start letting employees get the Epic touch.....
Gorguts said:
Well my cable was bad but that did not help with flashing ROMS. I have been dloading from the device though so I will get fresh dloads from the PC.
On a side note, I used the SW tool and flashed back to EB13 then took the upgrade prompt back too EC05. Been rollin' stock just for kicks and I noticed that the stock ROM runs faster then it use to but the graphics in the GUI get a little stuttery here and there. The scrolling and gallery interface are where it is most noticable.
I can't wait till they start letting employees get the Epic touch.....
Click to expand...
Click to collapse
Did you do Data&Dalvik wipe three times prior to going into EC05?
Ok, so I've decided to pop my cherry and go to custom ROMs. I'm going to try Blazer first. I'm currently on Stock EK02 everything from the OTA. I rooted using Auto Root. No problems before or after rooting. Needed some advice on the order of operations. I'm thinking of allowing the EL29 OTA update to take place to update the modem and kernel. I'm assuming that the OTA will go through even though I'm rooted. Then, I was going to to flash Blazer. Are the Stock EL29 modem and kernel a good match for Blazer or is there a generally accepted better combination? I was thinking that Stock modem and kernel might be better optimized and tested by Sprint to work better on the network. Thanks!
U can download blazer it has a kernel with the ROM....all you have to do is flash the modem and then the ROM and your good no need to do the update and then have to root again and install clockwork which if you already have then will cause the update to fail....just more steps that can get messed up if you don't read
Sent from my SPH-D710 using xda premium
The ota won't work. Manually flash the modem with cwm. I like the gunslinger kernel. The odex a deodexed cwm flash script improves performance also.
My personal setup is cal's 2.8.1 with gunslinger kernel and the odex script. I also am using a gingerbread launcher. I also went in and disabled the unneeded apks in /system/apps. I am running the EL26 modem because the phone was pissing me off while using streaming radio. It would fall back to 1x and not come back out. Oh yeah, I also did the tweaks for 4g quicker locking and connect with lower signal. On the 3g side, I zeroed out the multimedia addresses and proxies. I'm not over clocked. That may not be the best setup for everyone but its working good for me so far.
Thanks guys. I'm now thinking that since my call quality doesn't have any problems, I might just leave the modem as is on EK02. I'll just flash Blazer with the included kernel. Having EK02 modem won't cause a conflict right? Having not done this before, I should install CWM, then from CWM install "Calkulin's Format All" then install "Blazer". Do I need to reboot or clear any caches in between those two?
Going to test out Blazer for a bit and then Calk's and see which one I like better. Thanks.
frankquattrone said:
Thanks guys. I'm now thinking that since my call quality doesn't have any problems, I might just leave the modem as is on EK02. I'll just flash Blazer with the included kernel. Having EK02 modem won't cause a conflict right? Having not done this before, I should install CWM, then from CWM install "Calkulin's Format All" then install "Blazer". Do I need to reboot or clear any caches in between those two?
Going to test out Blazer for a bit and then Calk's and see which one I like better. Thanks.
Click to expand...
Click to collapse
Hey Frank, once you have CWM installed make sure to do a BACKUP before you go flashing other roms. Trust me that this is a very important step! Also, since you are already rooted I would advise making a backup of your apps via Titanium Backup? This is not required but useful for restoring apps when flashing ROMs. In answer to your other question, it is not necessary to use Calk's format all, but is recommended. Otherwise, just use CWM to wipe data, cache, and dalvik-cache. Then choose install zip from sd card and flash away.
Calks format all will clear all caches for you... Make sure to go thank the man
Sent from my SPH-D710 using XDA App
I was just in your shoes recently. I was on stock EK02 + root. Decided to use blazerROM as my choice of ROM. I didn't get the OTA update yet, so I went ahead and ODIN the pre-rooted EL29 stock update. I just wanted to see if EL29 had any issues. I ran it for half a day and decided to stick with it. I backed up my contacts and SMS messages and Titanium backup of all my apps. I added CWM via the auto-root script from sfhub. From there, I made a nandroid back up (it saves to your external SD if you have one) and went ahead and flashed calks format all. then flashed blazer right after (stayed in the same menu). Everything is running great so far with no major issues. Once everything was running properly, I just restored my user apps (not system!) via titanium backup, my SMS messages, and contact list.
I also did the same steps for my wife's phone, but put calks rom on hers.
You won't regret flashing. Better battery life, more features, bloatware removed, ect. I don't think i'll be on stock anymore since we get the updates here on XDA faster than sprint pushes them out anyway.
s9amme said:
I was just in your shoes recently. I was on stock EK02 + root. Decided to use blazerROM as my choice of ROM. I didn't get the OTA update yet, so I went ahead and ODIN the pre-rooted EL29 stock update. I just wanted to see if EL29 had any issues. I ran it for half a day and decided to stick with it. I backed up my contacts and SMS messages and Titanium backup of all my apps. I added CWM via the auto-root script from sfhub. From there, I made a nandroid back up (it saves to your external SD if you have one) and went ahead and flashed calks format all. then flashed blazer right after (stayed in the same menu). Everything is running great so far with no major issues. Once everything was running properly, I just restored my user apps (not system!) via titanium backup, my SMS messages, and contact list.
I also did the same steps for my wife's phone, but put calks rom on hers.
You won't regret flashing. Better battery life, more features, bloatware removed, ect. I don't think i'll be on stock anymore since we get the updates here on XDA faster than sprint pushes them out anyway.
Click to expand...
Click to collapse
Thanks. I saw another one of your posts and was going to ask you to compare Blazer and Calks but I didn't want to be that guy! I'm just going to try them myself. That said, did you update your modem to EL29 before you moved to Blazer? I'm thinking of keeping EK02 since it works well for me and I've seen others say EL29 had problems.
@jasone4gt Thanks for the reminder on the back up. I've installed CWM, done the back up. Getting ready to flash Blazer now.
You can jump back and forth with modems, so no biggie. If you're satisfied without then you know what they say, if it ain't broke....
Sent from my Blazing ET4G
tkemack said:
You can jump back and forth with modems, so no biggie. If you're satisfied without then you know what they say, if it ain't broke....
Sent from my Blazing ET4G
Click to expand...
Click to collapse
Thanks everyone. Took the plunge and everything is great. Didn't update the modem. Installed CWM, did Nandroid and Titanium backups, flashed Calk's Erase All then flashed Blazer. Everything works great so far. It all looks great too. One minor thing. The signal strength indicator is grey color instead of blue like everything else. It's also blue in the screen cap in the second post. Is it supposed to be grey and do I have to flash a theme? Also, does anyone know what the screen density is? It looks a lot better than Stock.
Looking to do this as well. Can you tell me more about auto root? Completely new to the whole root and flash shindig.
Sent from my SPH-D710 using XDA App
SuperSwagSauce said:
Looking to do this as well. Can you tell me more about auto root? Completely new to the whole root and flash shindig.
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
It's actually pretty easy. Just follow the instructions in the first thread in development to Auto root. Do step 1, download the e4gtauto-sfx.exe file and then run that. Select A to Root then C to install CWM. I'm not sure if you need to reboot your phone between A & C but to be safe, you might want to. Download the Blazer ROM and Calk's Erase All and copy that to your phone. Then boot into CWM by holding Up volume and Power while turning the phone on. Do the Nandroid back up in CWM. Then install Calk's then Blazer. That's it. You're done. There are a bunch of videos to help if you need it http://forum.xda-developers.com/showthread.php?t=1268548
It depends on what version he's on.
EL13 and up, he'll have to use the Odin package, also by sfhub. Then he would use the package you mentioned to run option C for CWM
Sent from my Blazing ET4G
tkemack said:
It depends on what version he's on.
EL13 and up, he'll have to use the Odin package, also by sfhub. Then he would use the package you mentioned tobrun option C for CWM
Sent from my Blazing ET4G
Click to expand...
Click to collapse
Yup, I thought I mentioned that in my post but getting old I guess. If you're on EK02 or earlier, then you follow my instructions. If you're on EL13 or later, you have to do Odin. I don't know how to do that though since I've never done it as I was on EK02.
Ok, run into a little problem. The hotspot hack worked fine right after flashing Blazer. I then did my restore from Titanium back up. Since that, the hot spot doesn't work. It says I'm not authorized. Did I restore something that undid the hack and is there a way to fix it besides doing a reset? Also, my signal strength indicator varied between grey and blue. Is that normal? And what is AOSP email? I installed it but it doesn't look any different than the Stock email. Thanks.
frankquattrone said:
Yup, I thought I mentioned that in my post but getting old I guess. If you're on EK02 or earlier, then you follow my instructions. If you're on EL13 or later, you have to do Odin. I don't know how to do that though since I've never done it as I was on EK02.
Click to expand...
Click to collapse
Im on EL 29. Gonna use this how-to I think.
http:// epic4gtouchroot .com/epic-4g-touch-root/how-to-root-galaxy-s2-epic-4g-touch-newsph-d710/
Well, don't know if anyone cares but here are my thoughts on my experience. First off, I think Blazer looks a lot nicer than stock. I suppose you have to like blue. I still have no idea why but my signal strength indicator occasionally turns white. I think it's when either 4G or Wifi is on but it's minor. Sprint tethering works with both 4G and 3G. It seems like 4G disconnects every once in awhile. Sometimes it's the 4G (meaning Internet on the phone doesn't work either) and sometimes the PC hooked up loses Internet access. I mentioned in another thread, the tethering worked right after flashing but after I did a Titanium restore, it stopped working and I got an authorization error. Turns out turning off and on fixed that. I found out after reflashing that you can avoid this problem if you don't restore the data for Wifi Sharing and Wifi Sharing Manager apps. No problems with GPS (used maps and nav) or any other connectivity. Before reflashing, I tried out Madoggin's 13 homescreen from 12/4. I didn't use it long but it seemed to work fine. I just didn't like it because it installs a different theme (didn't like the notification icons) and it replaces the scrolling toggles on the status bar. In case you haven't discovered it, I found out that holding the toggles in Blazer will open up the settings page for that item, e.g. tap Wifi turns it on and off but hold Wifi and it'll open up Wifi settings. I still have no idea what AOSP email is. I installed it and it looked exactly like Stock. After reflashing, I didn't install AOSP email and it still didn't look any different. I guess the difference could be the notification because the one that comes with Blazer has a different envelope icon for new emails. Performance-wise, I haven't noticed anything really different. I thought Stock was a really smooth experience and Blazer seems no better or worse. Battery-wise, I have one data point. I have really bad signal at my office and I would lose 10% battery for every hour on Stock but with Blazer it was half that. Last thing which isn't related to Blazer per se but I had been looking forever for a music player widget. There was another post that mentioned that there is an app in the market called Galaxy S Music Widget that gives you the widget to control the default music player and it is awesome. I also tried Music Mod which I used with my old Streak. It seemed to work ok even though it says it's for Froyo only but it is a separate music player and doesn't work with the Samsung widget thingys on the lockscreen and the notification area. The upside is that it has a lot of different sized widgets. Hope that helps someone. In summary, Blazer's very cool and works great.
frankquattrone said:
Well, don't know if anyone cares but here are my thoughts on my experience. First off, I think Blazer looks a lot nicer than stock. I suppose you have to like blue. I still have no idea why but my signal strength indicator occasionally turns white. I think it's when either 4G or Wifi is on but it's minor.
Click to expand...
Click to collapse
Blazer v3.8 fixes this.
Sent from my Super Sexy Epic touch.
So I I've had 2 different recoveries so far that have worked fine.. both came from Rogue though. One was from the 1.5 kernel (Hitman) which installed CWM Touch recovery, the other came with the normal recoveries based off CW 5.0.2.7. They were working fine until I installed Calkulin's Rom(2.8.1). Not sure if they're just incompatible or what, but when I go to recovery it shows the background image of the recovery but none of the options show up. It shows for about half a second and then it goes back to the original boot screen, then to the 2nd screen and turns on. So it basically skips right through the recovery and reboots. Do I need a new Rom or can I fix this? I really like the battery life and visuals of Calkulin's Rom and would love to be able to keep it.
EDIT: One more thing.. Since I installed the ROM, I've been getting market error 492. It doesn't allow me to install anything in the market..
I haven't tried a full wipe yet, so I guess I'll try that and then see how that works with the recovery and Rom..
I did the same thing to my phone this week, and I'm running Blazer, so i'm sure it has nothing to do with either ROM.
Not sure how I caused it but with so many folks running both without this error, I'm guessing that your issue (like mine was) was probably some how self induced.
I flashed back to stock and started over, and things have been working great. Might be worth a shot flashing back, or restore a backup and start fresh.
Haven't seen the market error before. I'm sure someone here has
Good Luck
If you got it off here, could you show me which stock you flashed..?
Everything you need is in the Epic 4G Touch Android Development section
Here is the post I used from Sfhub
http://forum.xda-developers.com/showthread.php?t=1433101
Watch the videos by Qbking77 They walk you thru everything step by step. (I hear his video intro rif every time I close my eyes now so you've been warned) Makes it super easy.
I would read everything you can and watch the videos before you get in too deep. I've had this phone since December, and just flashed my 1st ROM this week cause I've been reading up, and learning all I could before I jumped in the pool.
Well I've done all this with 2 phones before but I've never had this happen.. normally I just get the Rom and I'm good to go..
I think I must've gone wrong somewhere when I originally rooted through a stock rom.. It already seems to be more respondful.
premo1 said:
I think I must've gone wrong somewhere when I originally rooted through a stock rom.. It already seems to be more respondful.
Click to expand...
Click to collapse
Try booting while holding the volume up and power button.
If that does not work, flash recovery from rom manager, and that should get you into recovery to flash whatever kernel/recovery u want.
I've done all that.. None of it works.. I'm currently ODIN'ing Factory Stock Rom with root. Hopefully after that I can redo all of these and eventually end up with a working, corresponding Rom and kernel..
premo1 said:
I've done all that.. None of it works.. I'm currently ODIN'ing Factory Stock Rom with root. Hopefully after that I can redo all of these and eventually end up with a working, corresponding Rom and kernel..
Click to expand...
Click to collapse
Good Luck.
Recovery and market are now working Thank you Adanorm!
Glad your back up and running