Related
My girlfriend's HW003 Nova EVO is in a state of random reboot. I have run out of ideas.
It is not OS dependent, meaning I have gone through 3 different ROMS including stock rooted.
There are 6 log files below. They are logcat files right before the phone kills the connection.
Knowing that the ROM is not the cause, I am down to Radio, WIMAX, GPS, WIFI, or CPU/MoBo.
I executed the gpsclrx command and it had no effect on the random reboots.
Is anyone else having the same issue? Have you exchanged your phone at a Sprint location? What have you done?
http://www.andrewdefilippis.com/uploads/Documents/Restart_1.txt
http://www.andrewdefilippis.com/uploads/Documents/Restart_2.txt
http://www.andrewdefilippis.com/uploads/Documents/Restart_3.txt
http://www.andrewdefilippis.com/uploads/Documents/Restart_4.txt
http://www.andrewdefilippis.com/uploads/Documents/Restart_5.txt
http://www.andrewdefilippis.com/uploads/Documents/Restart_6.txt
Sent from my HTC EVO via XDA App
003 / Nova
I have some random reboots as well, thought it was related to temp but after a while that seems to not be the case. Happens on every ROM and seems to happen 9/10 times when browsing. Stock Browser / Dolphin HD. Reason I thought it was a temp thing was I started noticing a light spot on the screen, evidently above the processor, and so I figured something had to be happening with it all.
Have been meaning to start calling around about it and see if it's something Sprint can replace or not. Am more than prepared to pay the deductible, but I haven't really made steps to get to the bottom of it.
It's strange because when I think I realize what is doing it, it ends up not really seeming to be the case. It all started happening when I had a bad wipe / flash (clockwork) and it started happening then. Lost my RSA Certs (not a huge thing, obviously something I'll need to address at some point but currently using CM6 so I'm not really "missing it." But that's when it all started happening. So I guess in that regard, the WiMax shouldn't necessarily be an issue ... or so I would think. Happens when on WiFi and off, happens whether GPS has even been turned on at any point or not so I figured it had to be some CPU issue but not necessarily due to heat.
Know this probably doesn't help, but I thought I'd post.
have you tried seeing if it reboots with out apps installed? not sure if she uses setcpu or other similar type apps that could cause issues. I used to get random reboots too especially when i would run certain apps while i was over clocked.
and this may be a stupid question if so sorry but you are wiping between roms and you are NOT restoring system settings from a back up after you do correct?
Exchange the phone?
Sent from my PC36100 using XDA App
Right, naturally that'd be the next step.
Have tried nearly all ROMs without app restoring or even downloading, including not restoring system data.
sent from my SUPASONIC
just curious what recovery are you using? Maybe u should try to wipe with a different recovery and flash a new rom.
conqu1stador said:
Right, naturally that'd be the next step.
Have tried nearly all ROMs without app restoring or even downloading, including not restoring system data.
sent from my SUPASONIC
Click to expand...
Click to collapse
If you have setcpu installed, I need you to go to the info tab, scroll down and tell me what value is next to memtotal. It should be 425000.
Let me know what yours is.
Sent from my HTC EVO via XDA App
omegasun18 said:
have you tried seeing if it reboots with out apps installed? not sure if she uses setcpu or other similar type apps that could cause issues. I used to get random reboots too especially when i would run certain apps while i was over clocked.
and this may be a stupid question if so sorry but you are wiping between roms and you are NOT restoring system settings from a back up after you do correct?
Click to expand...
Click to collapse
This issue is ROM/APP independent. There is no connection to 3rd party software or os.
Sent from my HTC EVO via XDA App
No setcpu, and I've never used it. :embarrassedface:
Have never used a log cat but I could always try and see what happens...?
sent from my SUPASONIC
lgevo said:
just curious what recovery are you using? Maybe u should try to wipe with a different recovery and flash a new rom.
Click to expand...
Click to collapse
Gah, just saw this sorry for double post. Issues all starred after bad flash after bad wipe with clockwork. Using amon now, 1.7. Have yet to update to 1.8.
sent from my SUPASONIC
conqu1stador said:
No setcpu, and I've never used it. :embarrassedface:
Have never used a log cat but I could always try and see what happens...?
sent from my SUPASONIC
Click to expand...
Click to collapse
The reason why I was asking you to check the info tab for the memtotal value, is because on my phone, currently I am not having a problem and the value is 425000kB , but on my girlfriend's phone, it registers only 424840kB.
Sent from my HTC EVO via XDA App
Alright, will look for the one on these boards.
Hate to even go here, but I really never used a logcat before; but my phone just rebooted and I went immediately into the logcat and just like when I launched it at first there is just a wealth of information. I see it says ;
D/alogcat ( 521): stopping ...
D/alogcat ( 521): resumed
Might sound dumb, but am I to assume that's the point the log stopped and began again, due to the reboot? Would think it is .... on to that setcpu I guess.
edit: seeing that stopping and resuming in multiple spaces, guess that's not it. =/
setCPU - memtotal; 424828 kB
conqu1stador said:
setCPU - memtotal; 424828 kB
Click to expand...
Click to collapse
Alright. I need more people with HW003 Nova EVOs to check the same, and say if they are having reboots. This could be corrupted or bad memory.
Sent from my HTC EVO via XDA App
i have hw 02 but my memtotal is 424832... does that matter?
????
i have hw 02 but my memtotal is 424832... does that matter?
I think this may be a HARDWARE issue...
Hello xda folks,
Long time reader, first time posting...
I'll try and condense this down, everytime I try to post something xda says I'm not logged in, so I'm keeping it short out of re-writing frustration.
I'm HW003, I lack setcpu, so I can't really check my memtotal, but I believe that in short the flash mem/nand memory may be getting damaged or corrupted by flashaholics like myself. I'm curious to see in any non-root users have experienced the completely random reboots like some of us here.
Let me be clear about one thing, I'm describing random rebooting, not consistent bootloops, at least they weren't at first.
Initially, I thought this problem was a byproduct of OC'ing, or overheating the unit, but I have flashed every combination of rom, kernel, OC/stock, hboot ver, etc, virtually anything I have some control over, and the phone still reboots. Ive even rolled back to stock unrooted, and tried bone stock 2.2 but the phone keeps throwing a fit.
Everything on this phone hardware wise screams "I was manufactured on the cheap, and put out to stores on the quick", so it stands to reason there is some kind of failure taking place.
I'm no expert, but I've flashed this thing A LOT. Probably around 100 times.
It also seems to be getting worse, as it often sticks in bootloops now, not just random reboots. Causing me to have to flash it on an even more arbitrary basis!
Next step for me, is rolling back to stock 2.2{Again}, and sending this bad boy back to where it came from, and wait for my POS replacement and its new set of shenanigans. I will root the new one once, pick one rom, and flash it once...
It will be difficult, but I will be attending Flashaholics Anonymous.
We can do this together.
Anyone have a more logical answer?
I have seached and find reference to this pattern in multiple posts, but never an answer to what it means. Ever since ec05 my phone randomly does the pattern sometimes with no apparent problems or sometimes it happens while loading an app and then it force closes.
Thanks!
Sent from my SPH-D700 using XDA App
try re-flashing and that should solve your problem
Thanks, I will. I was just thinking there must be a meaning to the pattern. I seem to remember my moment did that once in a while also.
Sent from my SPH-D700 using XDA App
DexterDawg said:
Thanks, I will. I was just thinking there must be a meaning to the pattern. I seem to remember my moment did that once in a while also.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Any update if re-flashing fixed it? I'm having that problem as well, so odin again back to DI18 then flash using the update.zip again?
I have been busy all weekend and haven't had time. Will post results tomorrow. I just think there must be a description of what that means since I have had it happen on another android device also.
I think ultimately it may be a bad flash though because randomly I lose my signal and it doesn't come back until a reset. This happens when I am in a low signal area.
DQ
Sent from my SPH-D700 using XDA App
I get this too. Usually when an app is force closing.
younggangsta_s said:
when an app is force closing.
Click to expand...
Click to collapse
This
Sent from my SPH-D700 using Tapatalk
for what its worth, i wend to eb13 with the samsung tool then to ec05 with the update.zip and its still happening though not as frequent, can't even use my phone as my alarm as it will crash with that vibrate pattern and i'll have to pull the battery, looks like may need to take it to sprint again...
jojo08 said:
for what its worth, i wend to eb13 with the samsung tool then to ec05 with the update.zip and its still happening though not as frequent, can't even use my phone as my alarm as it will crash with that vibrate pattern and i'll have to pull the battery, looks like may need to take it to sprint again...
Click to expand...
Click to collapse
Did you root/remove apps? If so please list what you removed.
Sent from my SPH-D700 using Tapatalk
lafronz said:
Did you root/remove apps? If so please list what you removed.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
I have rooted before but when I was having problems with stability wanted to make sure I was on stock so both times I upgraded to ec05 its been stock once upgraded from di18 (odined back to it) and currently from eb13 (using samsung exe)
Sent from my SPH-D700 using XDA App
Sorry it took so long to get back here.
I finally had time yesterday to go back to DI18. I couldn't remember the hard reset recommendations so I did that before and after running Odin. I was going to run the update.zip, but got sidetracked. When I got back to my phone it had d/l the OTA. I ran that then did another hard reset and cleared the cache. Then I ran 2.5.5 one click, and I may have even did one more hard reset at that time. (I know a little anal)
I also formatted my SD card (I think I read somewhere that this can be an issue also)
Since then I restored user apps and data through titanium and I have not had a single problem with the vibrate error.
The only thing I haven't tried on my phone is Sprint ID.
I'm thinking there are four possibilities, my flash to di18 may have been bad, the update.zip I used was slightly corrupted or didn't install properly, the SD card had issues now solved by the format, or it's Sprint ID.
DQ
You can view files in data/tombstones/ to find out which app is FCing.
can you elaborate on the hard reset?
jojo08 said:
can you elaborate on the hard reset?
Click to expand...
Click to collapse
vol down, camera, power. wipe date option
sorry maybe "hard reset" isn't used anymore, from the WinMO days.
if this happens to you check and see if you have the whoisit app installed this is what caused it on my epic just uninstall it
The 1-3 vibrate thing means an app has force-closed. If you are getting a lot of this after flashing a new rom and restoring apps and data, it probably means that the data is corrupted or not in a format that the new rom can deal with.
The only time this has happened to me is after I have gone from a rom based on eclair to a rom based on froyo, and even then it was the phone data, not the app data.
DexterDawg said:
I have seached and find reference to this pattern in multiple posts, but never an answer to what it means. Ever since ec05 my phone randomly does the pattern sometimes with no apparent problems or sometimes it happens while loading an app and then it force closes.
Thanks!
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
This mean that there is some corrupt data and that you need to do a system restore from a previous backup or reflash to fix this problem. Usually this happens when your phone turns off randomly or when you forget to wipe the partition or dalvik cache when flashing a Rom or a system file such as stock browser or keyboard through clockwork mode.
First off, i always do a nandroid backup before flashing a theme or ROM.. which usually saves me.
I've noticed recently that, pretty much every time I clear the cache 3 times, then clear Dalvik 3 times, (in clockwork 3), after flashing anything, upon reboot, i get the boot animation, then vibrate, then double vibrate > bootloop.
This seems to happen even if I don't flash anything following the cache clear. Has anyone else had this experience? I'm more interested in the cause of this. I've since restored everything manually, but I'm a total flash/pushaholic, and looking for ways to avoid this situation. Any help is appreciated.
Sent from my SPH-D700 using Tapatalk
Did you properly shut your phone down prior to the cache wipe? As in power off then wait for the vibrate to signal it shut off.
decalex said:
First off, i always do a nandroid backup before flashing a theme or ROM.. which usually saves me.
I've noticed recently that, pretty much every time I clear the cache 3 times, then clear Dalvik 3 times, (in clockwork 3), after flashing anything, upon reboot, i get the boot animation, then vibrate, then double vibrate > bootloop.
This seems to happen even if I don't flash anything following the cache clear. Has anyone else had this experience? I'm more interested in the cause of this. I've since restored everything manually, but I'm a total flash/pushaholic, and looking for ways to avoid this situation. Any help is appreciated.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Why are you clearing cache and dalvik 3 times after flashing? Once should be plenty sufficient..
As for the cause, I would assume its the dalvik clearing.. cache is its own partition, where the dalvik is is on the system partition, and you are probably corrupting it with excessive writes..
Sent from my SPH-D700 using XDA App
Also remember that the version of CWM 3 we run on the Epic currently is not official. It can be a PITA sometimes. Dameon has done an awesome job porting it so we can have ext4, but I'm hoping some of these issues get cleaned up when we have the official version.
063_XOBX said:
Did you properly shut your phone down prior to the cache wipe? As in power off then wait for the vibrate to signal it shut off.
Click to expand...
Click to collapse
Hm, I almost never do that, but I will start. I usually do the death grip, then reverse death grip into recovery. (Can i trademark that name?)
@Mattalica: also good to know I'm not totally alone on this. I hadn't considered that. Thk God for nandroid + unyaffs
@Chris41g: i was trying the cache wipes on their own just to try to isolate the issue.
Thx everyone for feedback.
Hm, I almost never do that, but I will start. I usually do the death grip, then reverse death grip into recovery. (Can i trademark that name?)
Click to expand...
Click to collapse
If your phone is running a "no-journaling" Rom that will cause corruption.
063_XOBX said:
If your phone is running a "no-journaling" Rom that will cause corruption.
Click to expand...
Click to collapse
Gotchya, yes, i remember reading that- I'm running bonsai 4.01 with twilight 1.1 kernel - i forget off-hand if journaling is enabled , but I'll research.
Sent from my SPH-D700 using Tapatalk
063_XOBX said:
If your phone is running a "no-journaling" Rom that will cause corruption.
Click to expand...
Click to collapse
No journaling alone will not corrupt data. You have to shut down improperly or have a lockup caused by an unstable App (like beta wireless tether) or an unstable overclock/undervolt.
Sent from my SPH-D700 using Tapatalk
mattallica76 said:
No journaling alone will not corrupt data. You have to shut down improperly or have a lockup caused by an unstable App (like beta wireless tether) or an unstable overclock/undervolt.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
And that was what he did, I quote:
Hm, I almost never do that, but I will start. I usually do the death grip, then reverse death grip into recovery. (Can i trademark that name?)
Click to expand...
Click to collapse
063_XOBX said:
And that was what he did, I quote:
Click to expand...
Click to collapse
Yep, I know you know what your talkin about. I just didn't want decalex to take your response out of context, as some have been stating that the lack of journaling by itself causes corruption.
Is the vibrate, then double vibrate during the boot animation (then loop) indicative of "data corruption" ?
Next time it happens, I'll try to logcat.. I'm curious what is actually happening .. unless one of you already knows.
Sent from my SPH-D700 using Tapatalk
This has been happening on my Epic 4G for awhile now and it's really frustrating. I'm pretty sure this hasn't been happening the whole time I've owned the phone, but at this point it's hard to really remmber.
Basically, when I make or receive a call, within a couple\few minutes of the phone call the caller suddenly can't hear me - this happens whether it's using the phone normally, in speakerphone mode, or even a headset. As soon as it happens and the other caller starts the "Hello? Are you still there?" I can fix it by toggling the speaker on and off (or off and on) and it fixes it - but it can suddenly start again at anytime...couple of minutes later, five minutes later, etc.
Right now I'm slowly removing apps from my phone after every call this happens on - my goal is to determine if a particualr app is confusing my phone. I don't think it's the ROM or modem I'm using (Frozen 1.2, EC05) as I did a stock flash and flashed to those just recently and others aren't having the same problem. I DID restore some data so if I can't narrow down an app that's causing it, not restoring any data is my next option (but even more time consuming to figure out specifically which data is causing issues).
I'm pretty sure the phone hasn't always done this so I don't want to exchange the phone considering I don't have any other issues and I think this is software, not hardware related. Has anyone experienced anything similar to this?
Have you tried switching Roms, I have this same problem on EC05 when I moved to gingerbread it stopped happening.......
Do you voodoo installed?
Sent from my SPH-D700 using XDA App
I was having the same problem with EF02 and the EF02/EF10 modems. I switched back to the EC05 modem and haven't had the problem since (knocking on wood)...
Sent from my Transformer TF101 using Tapatalk
Try ee03 modem..
Sent from my SPH-D700 using Tapatalk
masaidjet said:
Have you tried switching Roms, I have this same problem on EC05 when I moved to gingerbread it stopped happening.......
Do you voodoo installed?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I do have Voodoo installed (since it comes with Frozen 1.2). I haven't tried switching ROMs yet but I have started looking again (I was pretty content with Frozen but if no one had a similar issue and changing the modem doesn't work then a ROM switch is my next try).
Thanks to others who suggested changing modems - I'm going to do that now and see if EE03 fixes this....*crosses fingers*
evancg said:
I do have Voodoo installed (since it comes with Frozen 1.2). I haven't tried switching ROMs yet but I have started looking again (I was pretty content with Frozen but if no one had a similar issue and changing the modem doesn't work then a ROM switch is my next try).
Thanks to others who suggested changing modems - I'm going to do that now and see if EE03 fixes this....*crosses fingers*
Click to expand...
Click to collapse
Go into you Voodoo sound settings and change recording setting to Original. Shoul fix your issue.
Sent from my SPH-D700 using XDA App
Sure you are not hitting the mute button by accident? Sounds dumb but I've done that before.
Blankrubber said:
Go into you Voodoo sound settings and change recording setting to Original. Shoul fix your issue.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I have the SAME EXACT PROBLEM and just like the OP it hasn't always been like that, did this work for you?
Sent from my rooted, suited, & booted Epic 4G kno dat!
I was having the same issues so I just applied this. People couldn't hear me on speakerphone at all...seriously. hopefully this helps. Thanks for the tip
Sent from my SPH-D700 using XDA App
evancg said:
Basically, when I make or receive a call, within a couple\few minutes of the phone call the caller suddenly can't hear me - this happens whether it's using the phone normally, in speakerphone mode, or even a headset. As soon as it happens and the other caller starts the "Hello? Are you still there?" I can fix it by toggling the speaker on and off (or off and on) and it fixes it - but it can suddenly start again at anytime...couple of minutes later, five minutes later, etc.
Click to expand...
Click to collapse
Yes! Mine started doing this a couple months ago, and I resolve it exactly the same way (though I have to hit the volume button once, either up or down, then toggle speaker on then off). It's definitely not the ROM because I've had it with both Froyo and GB ROMs. Unfortunately, I haven't found any other solution, yet. I'm hoping it will go away with official GB, but I have no real reason to think it will work. I'm going to play around with the Voodoo sound.
edonnelly said:
Yes! Mine started doing this a couple months ago, and I resolve it exactly the same way (though I have to hit the volume button once, either up or down, then toggle speaker on then off). It's definitely not the ROM because I've had it with both Froyo and GB ROMs. Unfortunately, I haven't found any other solution, yet. I'm hoping it will go away with official GB, but I have no real reason to think it will work. I'm going to play around with the Voodoo sound.
Click to expand...
Click to collapse
you guys shouldn't be having this problem make a backup then odin to ec05 stock and check if you still have the issue if you do just take it to sprint and show the tech your problem they should fix it or get you a replacement phone.
I have the same issue. I am completely stock. It usually happens 10 to 15 minutes into a phone call. I've already called sprint, taken it to a store but only reflashed the os, and I just recently spoke to someone on chat, who said the problem has been solved. If it happens again should I get a replacement phone?
Blankrubbers fix actually worked for me
Sent from my SPH-D700 using XDA App
steviee7 said:
you guys shouldn't be having this problem make a backup then odin to ec05 stock and check if you still have the issue if you do just take it to sprint and show the tech your problem they should fix it or get you a replacement phone.
Click to expand...
Click to collapse
I had this problem as well. I odinned stock and problem solved. Now I'm back on bonsai with no problems.
Edit: I just noticed that I don't have voodoo sound installed, I know that I used to, maybe deleting that solved my problem and not odinning back to stock.
Sent from my SPH-D700 using Tapatalk
evancg said:
This has been happening on my Epic 4G for awhile now and it's really frustrating. I'm pretty sure this hasn't been happening the whole time I've owned the phone, but at this point it's hard to really remmber.
Basically, when I make or receive a call, within a couple\few minutes of the phone call the caller suddenly can't hear me - this happens whether it's using the phone normally, in speakerphone mode, or even a headset. As soon as it happens and the other caller starts the "Hello? Are you still there?" I can fix it by toggling the speaker on and off (or off and on) and it fixes it - but it can suddenly start again at anytime...couple of minutes later, five minutes later, etc.
Right now I'm slowly removing apps from my phone after every call this happens on - my goal is to determine if a particualr app is confusing my phone. I don't think it's the ROM or modem I'm using (Frozen 1.2, EC05) as I did a stock flash and flashed to those just recently and others aren't having the same problem. I DID restore some data so if I can't narrow down an app that's causing it, not restoring any data is my next option (but even more time consuming to figure out specifically which data is causing issues).
I'm pretty sure the phone hasn't always done this so I don't want to exchange the phone considering I don't have any other issues and I think this is software, not hardware related. Has anyone experienced anything similar to this?
Click to expand...
Click to collapse
speak up i can't hear you
Sadly even after changing modems and making the adjustment in Voodoo Control I still have the same problem. Going to uninstall Voodoo all together and see if that resolves anything.
I just discovered that I'm having the same problem after I Odin'd back to stock EC05 for a different reason. So, EC05 and EC05 modem, and I'm having a problem that I didn't think I was having before I tried EF02.
Could something have been changed that going back to EC05/EC05 modem didn't resolve?
Sent from my Transformer TF101 using Tapatalk
evancg said:
Sadly even after changing modems and making the adjustment in Voodoo Control I still have the same problem. Going to uninstall Voodoo all together and see if that resolves anything.
Click to expand...
Click to collapse
This problem is not generated by Voodoo. I have a stock Epic (rooted) and have never had Voodoo installed on my device and I have intermittently had this problem in the past (haven't seen it for a while, though). My friend has an Epic (never rooted) and also has this problem.
About the only thing I've heard that people have said fixes this is to wipe cache and dalvik and then flash something using Odin. Stock or custom I don't think matters.
As others have noted, uninstalling Voodoo didn't fix it for me. I think what must be causing this is everytime I wipe and install a clean ROM I restore some data through TiBackup and SOMETHING I'm restoring is causing this. Guess I'll just have to wipe and be very careful about what I'm restoring.
This might be completely random, but by chance did other people that experience this problem happen to install NZBAir?
Hello xda community. I have a pretty large issue that affects my Epic. I recently had my Epic broken by blunt impact to the screen. So I sent it in and they sent a replacement in less than a day. I had Frozen 1.2 on my old Epic, and I had zero issues. But since I got my replacement, its been nothing but a hassle.
It doesnt get nearly as good battery life, it randomly reboots to the ACS logo, then endlessly cycles until the battery is pulled. Then when its turned back on, everything force closes, rendering the phone un-usable. The only remedy is to go to Clockwork and repair permissions. This will fix it for half the day.
Any advice?
bbecker42 said:
Hello xda community. I have a pretty large issue that affects my Epic. I recently had my Epic broken by blunt impact to the screen. So I sent it in and they sent a replacement in less than a day. I had Frozen 1.2 on my old Epic, and I had zero issues. But since I got my replacement, its been nothing but a hassle.
It doesnt get nearly as good battery life, it randomly reboots to the ACS logo, then endlessly cycles until the battery is pulled. Then when its turned back on, everything force closes, rendering the phone un-usable. The only remedy is to go to Clockwork and repair permissions. This will fix it for half the day.
Any advice?
Click to expand...
Click to collapse
The force closing is probably due to not having Journaling on.
I believe in the SRF 1.2 OP, there is a JournalingOn.zip, flash that (no wipes) and that should stop the force closing.
If it still is unstable for you, I recommend just reflashing the ROM.
Hope this helps.
Follow Acer's directions. If for some reason you still have an issue, then I'd recommend redownloading the rom.
You may also want to try a different kernel.
nikon120 said:
Follow Acer's directions. If for some reason you still have an issue, then I'd recommend redownloading the rom.
You may also want to try a different kernel.
Click to expand...
Click to collapse
Exactly right
Sent from my SPH-D700 using XDA Premium App
I had friend who had the same issue. He went back to SFR1.1.1
then installed ACS updater and flashed SFR 1.2. That fixed his problem. I did it that way too and have not had any issues. Calibrate battery after flashing.
Sent from my SPH-D700 using XDA App
That sort of worked. It made it take longer for things to get hosed over again.So I tried resetting it to stock then flashing EG22, but each time I flash EG22, it doesnt do anything.The version stays at 2.2.1. What am I doing wrong?
What did you flash that is EG22?
Sent from my SPH-D700 using XDA Premium App
In order to better assist you, can you give us a step-by-step listing of everything you are doing? The files you are using with version #'s and your computer OS (with bit version).
I would recommend a full wipe of the phone, to remove any corrupted data
then do a clean install of SRF 1.2
then install the zip to turn on journaling
note: DO NOT use the reboot option until AFTER you have turned on journaling
What I did last night was returned it to factory stock EC05.
Im working with Windows 7 Home x64 on a Mac Pro, because for some reason neither Epic I've ever had will work with my custom built computer.
I flashed the EG22modem.bin with Odin 1.61. That didnt seem to do anything.
So later today, I am going to try this
http://forum.xda-developers.com/showthread.php?t=1184134
The modem only changes the baseband..
regardless, imo it sounds like the problems you are having are due to restoring backups.. is that the case?
I installed this
http://forum.xda-developers.com/showthread.php?t=1205024
and everything is hunky dory in the hood. Thanks for all the help