Related
any time i try to flash to anything dk28 based, i get the same result. the touch screen (almost) randomly stops responding to input. seems to be related to keyboard opening, but not always. example: from sleep, wake > slide unlock > slide notification bar > tap... "damn it..." can't open the notification unless i sleep it and start over. this is not a hardware problem so far as i can tell as it works fine when flashed to stock. it's less than 2 weeks old and no, i did not spill anything on it. am i alone here?
not new to android, nor am i new to flashing roms, hacking portable devices / electronics in general or using forums. i did search and nothing matched my issue. please don't treat me like a noob just bc my account is new.
As of this morning my phone seems to have developed this kind of behavior, out of the blue. I have no idea what caused it, just that it is exceptionally frustrating.
further info:
...this was all using cwm3 one click with conversion to ext4. just installed cwm 2.5 and flashed the zip version of dk28 (from here) and got the same result again... damn it... back to the beginning again...
Flashed Nebula (seven sisters) and got the same... I mean, if it did this on stock fw I would obviously exchange it... but its only when I flash. So either I'm doing something wrong, there is something wrong with my handset or there's something with cwm or dk28 causing this. Not outside the thought of me doing something wrong, but I've tried so many different things at this point... the only thing I have left I think is flashing dk28 as an update. Is there one around?
Sent from my SPH-D700 using XDA App
my epic was doing the same thing after i flashed midnight but then just a soon as it started it stopped and hasnt happened since. ive tried to recreate to solve it but to no avail if you figure anything out please let me know
Odin back to stock = fine.
flash update.zip for here = intermittently unresponsive again.
seriously... no one else is getting this continuously? i mean it's pretty unusable...
I'm still getting it pretty consistently, I haven't flashed back to DI18 to see if that fixes it. (Odin and I have a bitter history) I suppose if I'm going to take it back I need to flash it back though.
yeah, i did something wrong the first time with Odin but i'm pretty comfortable now. don't know what i did before, but it failed and nearly bricked. as i understand it now:
1. remove sd card (i just go ahead and pop out the battery while i'm at it)
2. boot into download mode (boot while holding "1")
3. select victory PIT and DI18 in PDA
4. uncheck everything but restart
5. connect handset and verify that it is seen
6. go.
have done this about 10 times now and haven't had a problem... until i try to do go to DK28...
I think i'm going to have to wait for official FROYO... it's killing me but i don't want to try to walk into sprint like "hey, my rooted phone doesn't work right...". if it still happens on official 2.2, i will swap.
Mine does the exact same thing. I asked about it yesterday because I couldn't find anyone with a similar issue but the only answer I received was to go back to stock and try it again. I did that and I got the same result.
I ended up just taking the phone into a Sprint repair center, they replaced the screen and didn't even mention the DK28 Bonsai 2.0.1. For free, in less than three hours.
I'm a little confused, are u flashing DK28 with Odin?
It doesn't seem to matter how I flash:
tried flashing just DK28 in Odin
tried flashing modem/pit in Odin and ROM in CWM3
tried the same with CWM2.?
tried update.zip from stock recovery
all get the same result. Behavior seems to actually be time based - like when wake from sleep, it responds for a few seconds and then stops. it doesn't come back until i sleep/wake again, then it's fine.
UPDATE
EB13 is out, installed and still causing an issue. I will be going to the Sprint store later. Still don't know why this didn't happen on DI18, but whatever - happens on official release now so a replacement is justified.
Hey All. I have been on a roller coaster with My Samsung Epic.
Recently I Finally from DK28 updated to Froyo for my Samsung Epic and flashed Viper trinity ROM on it. It was cool up until certain apps did not work well such as Tom the talking Cat and Hulu. Furthermore I rely heavily on my Sprint Navigator, which was Removed after the Viper ROM flash.
I tried to factory restore and reset but had no luck, my phone actually never was able to reset as from the Privacy reset through the Phones gui it would freeze, and if I did the -vol, camera, and power it still kept the viper ROM.
With out further reading I watched a youtube video and ended up using Odin 1.6 and reset it back to DG27. I tried to than only update to 2.2 Froyo without adding any fancy Roms but it failed to do so.
Thats when I read it could only be flashed forward if its DK28. Im suck now and cant get back to DK28. Ive tried Odin again with the SPH-D700-DK28-8Gb-Rel.Tar.MD5, and sometimes removing the .MD5 part.. but odin still gives me errors. ive been at this for the last 9 hours and could use some help, guidance and actual Links that are not broken or have a 404 error on them.
-
Problem: Cannot use Odin to get back to DK28 and is stuck on DG27
Solution I want: To be able to take my crappy Samsung Epic and make it Epic with Froyo 2.2 so I can one click root it, installing Flash and Hulu.
-
Thank you all!
You may want to Odin to DI18,and then going to EB13 either by an update.zip,or Samsungs tool,mini kies if I remeber right.Or you can try one of the current FROYO ROMs,EB13 based.
Sent from my MyFrankenstein E=Bee13² ROM using XDAP App...
should be able to ODIN right to EB13. look for that file and follow the steps. ODIN doesnt care about deltas etc... it writes to your phone regardless. then you can one click root and rock your custom ROM to get hulu going.
That would be nice.. but EB13 and DI18 I cannot find.. I have been looking for them and have come up with nothing. I have searched and most of the links are the stupid Gator link with 404page error.. Also the Stock roms are just impossible to find.. Im a hammer stroke away from caliming my phone was dropped and just getting a new one. I hae tried Odin3+V1.61 with Victory PIT and SPH-D700-DK28-8Gb-REL.tar.MD5 and without the MD5 and continue to get an error....
Please, Links and tutorials will be greatly helpful.
NVM. I found it. Took forever to find the right TARs and what not.. now I have to find a way to go from DI18 to DK28.. OTA update doesnt seem to work.. and warning out there, ViperTrinity Rom is slow and laggy.. Trying to watch Hulu is unwatchable and also a simple app like Tom the Talking Cat does not work well.. Laggy as a mother!
Why dk28? You should just go to eb13 anyway, laggy buggy issues are at least somewhat if not entirely because of dk28, it was a very buggy leak. Now that eb13 is out go to that, throw on a custom kernel if nothing else and you should be in much better shape.
I believe ptfdmedic's newest midnight rom has flashable zips to restore whatever stock sprint apps you might want. Ill see if I can find you links to all you'd need.
Edit: you should be able to use this and odin strait to eb13 froyo stock pre-rooted: http://forum.xda-developers.com/showthread.php?t=853209
Still looking to see where it was that I found the sprint apps flashable zip that could be used if you went to a custom rom but wanted nav back.
Edit2: ptfdmedic does have a sprint apps edify zip on his site http://lostandtired.com/ under the android development section which I assume these work with EB13 if you were to go to a custom rom with them removed.
The ROM that I was actually thinking of was ecooce's new frankenstein rom: http://forum.xda-developers.com/showthread.php?t=982415 He has zips with all the removed apps so you can add back what you need.
Sent from my SPH-D700 using XDA App
I've apparently done something to my Epic and I can't figure out how to reverse it. Probably because I don't know what I did and/or when.
Since I got my Epic, every time I first boot it up after installing a ROM (whether it is custom or going back to a stock image), the Setup Wizard fires up, asks the usual questions, gets my google account info, and then automatically syncs my contacts and apps I've downloaded for the market. I've read plenty of posts where folks don't like this and will cancel the process so they can do it manually. Personally, I like that feature but it no longer works no matter what ROM I flash.
I first noticed it when I was on ViperRom 4.0.4. I wanted to upgrade to ViperRom 5, the newest release, and since I was on DK28 based rom, I wanted to first flash the stock EB13. It all went smooth as silk but when EB13 started for the first time, the Wizard didn't start asking me setup the phone for the first time. It just went straight to the stock launcher (TouchWiz I assume). And yes, I did all the custommary wiping of the 3 finger salute before I started. Bottom line, I just took mental note of it but moved on because EB13 was just a stepping stone for what I wanted to do. So, 3-finger salute, lotsa wiping, then flashed Synergy (ViperRom 5.0). Again, absolutely no problems. But again, the Setup Wizard didn't fire up. Hmmm...
So, I re-wipe, re-flash, and still no wizard. Grrrr... Since then, every rom I've installed/flashed has not once had the Setup Wizard fire up! WTH??? LOL. At the moment, I've Odined back to DI18 (just for the hell of it mainly). So I'm on DI18, RFS, not rooted, just like it came out of the box....no wizard?
What did I do? How do I re-enable the SetupWizard.apk (assuming that's what it is). I know the file is there in system/app because with every rom, I could use astro or root explorer and see that it is where it belongs. Of, course if I try to run it from one of the explorer apps, I get an error message, but doing a full wipe/restore to DI18 should have let the apk run, right? Have the permissions been altered to not let it run? Is this something I can correct with ADB?
Any help would be most appreciated and welcome.
The rom dev needs to enable it. It has been disabled by them
Sent from my SPH-D700 using Tapatalk
Yep the ROM devs have to enable it. Otherwise whenever you go to Market or GMail for the first time it will ask you to enter your Google information, (the Android Setup Wizard kicks in...)
I had thought that might be the case, but if they disable it, is it disabled forever?
When I installed ViperRom 4.0.4 (Trinity I believe, the last of their DK28 based roms), it was there and working. The wizard fired up after the first bootup of Trinity and everything went as normal as can be. I used Trinity, and only Trinity, until version 5 (Synergy) was released. I didn't flash/odin a single rom the entire time I was on 4.0.4 as it met all my needs. EB13 was released during this period but I resisted the temptation to try it figuring I'd wait until TPhillips released his next ROM (excellent job btw). So, the next thing I finally flashed (actually it was Odin) was EB13 since the dev's instructions said to be on EB13 before flashing Synergy (ViperRom 5.0). THAT is when it happened. When EB13 fired up for the very first time, no SetupWizard! But it was there for the previous ROM (ViperRom's Trinity 4.0.4) and gone when I went to EB13 a month or so later. So, by that reasoning, it was disabled in EB13 because that is the first time it didn't fire up. And, it hasn't fired up since. I've flashed 3 or 4 times since then, as recently as this morning when I Odined back to DI18, but the last time I saw the SetupWizard was when I installed Trinity (a month and a half ago I guess). I could understand custom rom dev's disabling it, but this happened when I Odined a stock EB13. I can't see Samsung and/or Sprint disabling it. And I know it was there on DI18, but it didn't fire off this morning.
Somewhere, I must have goofed something up, and I do believe I need to change a permission setting somewhere (the file is where it belongs), I'm just not sure what to do or even why it happened. When I odined the stock DI18, i would have thought that would reset every setting/permission/flag there was...but it didn't! So, I have to wonder is there anything else not properly "permissioned" since whatever this is has "stuck" through maybe half a dozen flashes & odin's...plus it started when I flashed a stock recovery.
To me atleast, this is really weird!?!
Thanks for the replies, I thanked you both. But, any other ideas?
Paul627g said:
Yep the ROM devs have to enable it. Otherwise whenever you go to Market or GMail for the first time it will ask you to enter your Google information, (the Android Setup Wizard kicks in...)
Click to expand...
Click to collapse
And for the record, I do know that when I go to the Market or Gmail the first time, I get to enter all my info and everything is fine. But, the ONLY time (that I know of anyway) that all of my previous apps (like 75 of them give or take) will automatically download and install is if I get that setup wizard to fire the very first time the phone starts up after a fresh install. If one cancels (or in my case doesn't get to do it), then I have to go to the market and install the stuff myself. Of course, I have both TitaniumBackup (pro version, I lbelieve in supporting the devs) and MyBackupRoot, so it's not like I'm screwed or anything, I just "LIKE" for it to be all automated...it just feels fresh that way! LOL.
This isn't like a huge problem, I'm just more curious as to what happened than anything else and wondering why odining back to stock (either DI18, DK28, or EB13) doesn't reset things to make this work like it should...
Samsung has it disabled. its been disabled since the phones release. Some devs enabled it for there custom roms for some time.
Sent from my SPH-D700 using Tapatalk
Well, that makes a lot more sense then. Because it was EB13 that was the first time I didn't see it. Just out of curiousity, what would I need to modify to make it work in a rom, or am I just pissing in the wind. For example, can I modify something in a rom (lets say Synergy from Team Viper since thats what I'm using at the moment), perhaps in ADB, before I flash it so that the apk fires up to start. Or, can I take the .apk's of my favorite apps and "drop" them in the rom (I know not to extract a rom from the zip file then re-zip it after making changes) so that they install with the rom when I flash it, like a ViperRom or Syndicate. They would go in the data/app folder, right? Or, just quit my *****ing and deal with it? LOL.
Really, mystery, thanks for your time...
Your just pissing in the wind so why don't you just stfu .
I'm not sure how to enable. I think its something in the build.prop. Your gonna have to ask a rom dev to get a def awnser.
As far as adding your own apps you can just add them to the data/app and they will automatically install when you flash the rom.
If your worried about your apps you can always try syndicate or bonsia. There script backs up the user apps then wipes everything. Once the rom installs it automatically restores your apps and phone to where it was before flashing.
Your welcome
Sent from my SPH-D700 using Tapatalk
SetupWizard was only one part of the process. They removed GoogleBackupTransport (the other part) in EB13. Even if you enable the SetUp Wizard in the build.prop, it won't restore any apps other than the ones you purchased. The googlebackuptransport.apk from DK28 is not compatible with EB13/EC05.
MysteryEmotionz said:
Your just pissing in the wind so why don't you just stfu .
Click to expand...
Click to collapse
LOL! Damn, I can't remember the last time I was b^tch slapped like that! Damn, that's what u get for thanking a guy (or gal) twice in one day!
OK, so I hit the brakes on the SetupWizard and dropped a pile of APK's that I like in the data/app folder. I had read before that one could do that with zip's flashed in CWM. Actually what I read talked about taking stuff out if you didn't want it (like when all the Sprint and/or Samsung apps were rolled into one big zip to flash, the OP had said just take out anything you didn't want), so I had figured the reverse was true and I could drop apk's in. I just wasn't sure about a ROM. Anyway, it worked perfect...
Oh, and Mystery...bite me!
Glad it worked for you and I have been some assistance.
I gladly will
Sent from my SPH-D700 using Tapatalk
mattallica76 said:
SetupWizard was only one part of the process. They removed GoogleBackupTransport (the other part) in EB13. Even if you enable the SetUp Wizard in the build.prop, it won't restore any apps other than the ones you purchased. The googlebackuptransport.apk from DK28 is not compatible with EB13/EC05.
Click to expand...
Click to collapse
You know I asked this question many of times to a few devs and everyone just said change the build.prop from DISABLED to OPTIONAL for SetupWizard. Which I did and I went as far as to decompile the setupwizard.apk to see that the coding was still there for the backup and restore but for the life of me I couldn't get it to function.
You are the first to come up with a different response saying the googlebackuptransport.apk, which makes perfect sense. Why nobody has ever taken the second to explain that further than the build.prop response I have no idea.
Thanks, at least my endless wondering of what happened between DK28 and EB13 now has a answer.
Paul627g said:
You know I asked this question many of times to a few devs and everyone just said change the build.prop from DISABLED to OPTIONAL for SetupWizard. Which I did and I went as far as to decompile the setupwizard.apk to see that the coding was still there for the backup and restore but for the life of me I couldn't get it to function.
You are the first to come up with a different response saying the googlebackuptransport.apk, which makes perfect sense. Why nobody has ever taken the second to explain that further than the build.prop response I have no idea.
Thanks, at least my endless wondering of what happened between DK28 and EB13 now has a answer.
Click to expand...
Click to collapse
No problem.
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
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