Related
Hi all,
Sot of new to modding, think I screwed up and could use some help. Was doing this one click speed fix: forum.xda-developers.com/showpost.php?p=7587405&postcount=417
It didn't appear to work the first time, as I received a message and exited the application, however the symbol was still in the notification bar. Re-ran it, and it seemed to have worked, mostly, as the phone was blazing fast. Went immediately to run quadrant and check the benchmark, but it force closed every time it hit the i/o section. tried to go to market, foreclose every time. Figured it may need a reboot, powered off, and that's was all she wrote.
I can get into the battery charging screen and have been able to get to recovery, but nothing else. I haven't used adb or ODIN at all yet, but any assistance is greatly appreciated.
The phone was already rooted, and i have titanium back up and nandroid backups, but don't really know how to get to them.
If you did a nandroid backup, just go in recovery screen and restore backup. If not, flash back to stock rom.
well maybe i dont know what im talking about then. I guess I thought i did a nandroid.
When i go into recovery i get four options: reboot system now, reinstall packages, clear all user data, clear cache data.
none of them work
Did you install clock work recovery via Rom manager?
well it has turned on now. removed sim and memory card and hit reinstall packages. ive got the standard twlauncher running but, it repeatedly gives me force close notifications that android.process.media has stopped and i cannot access the menu
s15274n said:
Did you install clock work recovery via Rom manager?
Click to expand...
Click to collapse
yes, i did. i remember doing that precisely as shown in your tips and tricks thread
alright, so i got it into download mode, gonna reflash everything to stock and see where i went wrong as outlined here: http://forum.xda-developers.com/showthread.php?t=734475
Will update with results, but would be nice to figure out where i went wrong so as not to repeat the error.
If you can get into recovery just wipe and reflash eugenes vibrant4.zip.
Alright, back to stock. unrooted also? gonna mess some more and see if i can get my clockword recovery to restore everything.
okay, so my theory is that the lag fix i used installed an update.zip that overwrote the clockword mod one. Now im just trying to restore using titanium backup, but it is telling me that it doesnt have root access. i know im rooted, as i just did it and reinstalled rom manager and drocap. hmmmmm.....
Thats not all thats funny. i cant find the superuser app anywhere on here. also, i cannot install one from the market.
and im having issues with root explorer.
Civil Disobedient said:
okay, so my theory is that the lag fix i used installed an update.zip that overwrote the clockword mod one. Now im just trying to restore using titanium backup, but it is telling me that it doesnt have root access. i know im rooted, as i just did it and reinstalled rom manager and drocap. hmmmmm.....
Click to expand...
Click to collapse
DAKIDD236 said:
If you can get into recovery just wipe and reflash eugenes vibrant4.zip.
Click to expand...
Click to collapse
I would re-root and then follow the flash the ROM mentioned above. There is a thread in the DEV forum.
Civil Disobedient said:
okay, so my theory is that the lag fix i used installed an update.zip that overwrote the clockword mod one. Now im just trying to restore using titanium backup, but it is telling me that it doesnt have root access. i know im rooted, as i just did it and reinstalled rom manager and drocap. hmmmmm.....
Thats not all thats funny. i cant find the superuser app anywhere on here. also, i cannot install one from the market.
and im having issues with root explorer.
Click to expand...
Click to collapse
You need to root again to get the superuser on your phone. As for the one click lag fix, I used to original method and it went pretty well. No problems so far. I also flashed Vibrant4 by Eugene before doing the lag fix. Hope it helps
same thing happened to me. I'm stuck on the galaxy S boot screen. i can get into the samsung recovery screen but not the clockwork recovery. I backed up my nandroid and Rom but don't know how to get into the menu to restore. I only have the update.zip for the lag fix on the internal sd so can't restore that way. Any ideas? Much appreciated.
kwbdc said:
same thing happened to me. I'm stuck on the galaxy S boot screen. i can get into the samsung recovery screen but not the clockwork recovery. I backed up my nandroid and Rom but don't know how to get into the menu to restore. I only have the update.zip for the lag fix on the internal sd so can't restore that way. Any ideas? Much appreciated.
Click to expand...
Click to collapse
There may be other ways around it, but I restored fully to stock, then re-rooted. I'm back up and running no problem now. Had some issues with titanium backup but got around that and its batch restoring as i type.
Civil Disobedient said:
There may be other ways around it, but I restored fully to stock, then re-rooted. I'm back up and running no problem now. Had some issues with titanium backup but got around that and its batch restoring as i type.
Click to expand...
Click to collapse
Would you mind saying how you did that?
I tried wiping and flashing the stock via renaming it update.zip, and I'm still getting FC city. Mostly media, but, calendar, everything. I'm going to post a link to this in that thread, since many, it seems, were left hanging in a boot loop.
Janis said:
Would you mind saying how you did that?
I tried wiping and flashing the stock via renaming it update.zip, and I'm still getting FC city. Mostly media, but, calendar, everything. I'm going to post a link to this in that thread, since many, it seems, were left hanging in a boot loop.
Click to expand...
Click to collapse
Just follow what I did through the thread.
I did this http://forum.xda-developers.com/showthread.php?t=734475 to get back to complete stock, then i had to root it twice. Once did the one click, then the good root here http://forum.xda-developers.com/showpost.php?p=7150299&postcount=1
back up and running. had to research about titanium backup to get it up and running. I want to do the lag fix still, but im nervous from before.
Your nervous? I really would like to do this but i'm scared (cuss)less.
I've read what needs to be done and think that I've figured it out.
(pretty new to droid)... but, have also read the horror stories here
about bricking your phone...which nowadays can happen to any
phone you have....don't get me started on the apple pie!
But, really when it gets a simple as installing an .APK I'll be happy.
Damitu said:
Your nervous? I really would like to do this but i'm scared .......
Click to expand...
Click to collapse
The galaxy s seems pretty hard to brick. I'd say just go for the lag fix. Worse thing that happens is you have to take like 15min to download and use odin to reflash to stock. The lag fix seems pretty safe as long as you stay rooted
Sent from my SGH-T959 using XDA App
Vibrant Recovery Mode HowTo
THIS GUIDE WORKED ON USA T-MOBILE SAMSUNG VIBRANT BUT MAY VERY WELL WORK ON ALL SAMSUNG GALAXYS PHONES
After reading many XDA-Developers Forum Posts to try and figure out how to get into the Recovery Mode / Download Mode without any success, I gave T-Mobile Support a call.
After the usual noop run-down, "did you take the battery out" questions, I simply asked them how to get the Samsung Vibrant into recovery mode.
Unline the many tutorials that claim to require the Up or Down button pressed, along with the Home button then the Power, the true process is as follows:
1. Press the Up and the Down button at the same time (yes both). I too thought that button was a Toggle which only did either Up or Down, but found that in fact it does do both.
2. At the same time, press the power button.
3. As soon as the Samsung / Vibrant logo comes up on the screen, release the power button.
4. Release the Up and Down buttons.
5. PRESTO
Here's a quick rundown. Sunday I rooted, installed cwmrecovery, and installed jt's 1200 voodoo kernal. Through the process, I have downloaded ROM manager, Root explorer, SetCPU, and Titanium backup.
I've done all the basics such as renaming bloatware, installing enhanced google search, ran a full titanium backup, and used SetCPU to OC to 1.2. I'm happy to say everything is running at 100%. Haven't had a single problem since modding everything.
Since doing this, I've read that I should have ran a nandroid backup before flashing voodoo in case anything goes wrong...unfortunately the instructions I followed did not include this. Because everything's working so well for me, I really don't want to screw anything up. I'm pretty sure I know how to do this I just want to list my steps and make sure they're right before attempting.
1. disable lag fix
2. reboot
3. boot into recovery mode from ROM manager
4. create a backup? (not sure what the CWMrecovery command is)
5. reboot
6. undo disable lag fix (re-enable lag fix)
7. reboot and pray everything continues to run smoothly
Does this sound about right?
that sounds right
Let me know how this works for you and exactly how you did it. This is what I was trying to do and when I rebooted after doing the disable/lagfix, everything was gone and i had no Google sign in, no market, and no keyboard. Still trying to figure out where i went wrong......
Sent from my SCH-I500 using XDA App
Your steps look fine.. Make sure #2 is a full reboot.. Don't just disable and then directly reboot into CWM, that won't work.
For some people it works easy as pie, for others, it blows stuff up. Not sure what to tell you.. You're taking your chances either way.. Either something will crash down the line and you'll have no backup, or you disable voodoo and take the risk of that blowing you up, and obviously you have no backup.
I think I would just go ahead and try the uninstall, you should always have at least a basic backup to work from. You might get lucky and just have it work the way it should.
Before you do anything though, I highly recommend installing and running Titanium Root, that will back up your applications, so even if things blow up on you, you can at least do a quick one-touch restore of the apps once your back to stock.
Glad to see I'm not the only one in this boat. I have rooted, cwm, and have OC kernal with 0.2 voodoo. I never backed anything up though...
I may try and follow in your path.
Ok, I felt confident and jumped head first into this because I really wanted to back my phone up with nandroid, so I went for it. After I disabled lagifx, my phone had an emotional breakdown. I attempted to backup with nandroid and I believe it failed, it said "Null" and did nothing. I pulled the battery after about 15 minutes and restarted my phone. Deleted the disable_lagfix file I had created and rebooted my phone. It did the voice and all that fun stuff and froze with the words "Samsung" on the screen. I think I may have made a super boo boo some where along the way.
If anyone knows what I should do now, please help. I'm in over my head for the most part.
Mageta said:
Ok, I felt confident and jumped head first into this because I really wanted to back my phone up with nandroid, so I went for it. After I disabled lagifx, my phone had an emotional breakdown. I attempted to backup with nandroid and I believe it failed, it said "Null" and did nothing. I pulled the battery after about 15 minutes and restarted my phone. Deleted the disable_lagfix file I had created and rebooted my phone. It did the voice and all that fun stuff and froze with the words "Samsung" on the screen. I think I may have made a super boo boo some where along the way.
If anyone knows what I should do now, please help. I'm in over my head for the most part.
Click to expand...
Click to collapse
Can you get into CWM?
Sent from my SCH-I500 using XDA App
Yep, sounds like a pretty standard voodoo uninstall explosion. Happened to me as well.
See the thread "How to completely remove Voodoo". I'd recommend reading it all the way first, then trying it. There's some useful stuff later on.
If you can't get into CWM recovery at all, use odin and re-flash the CWM.tar file in the general CWM recovery thread here. Make sure when using odin you always, always use the "pda" box. Never use the "phone" box or else it's brick city.
Did you boot into recovery as soon as you disabled_lagfix or create the file, reboot, and let the phone completley boot up and then reboot into recovery?
Sent from my SCH-I500 using XDA App
OK, after my phone got stuck on the Samsung start up screen I pulled the battery and restarted. This time it actually restarted wit my the voice and I had my boot animation from the 1200 oc kernal/voodoo lagfix I had installed. It worked fine but I had to go through the set up for my phone and resign into my Google account. All my apps were gone and I've lost root. I tried to re-root but when I open adb I get the # sign instead of $... I tried to use the one click root but it didn't recognized my phone. Adb does recognize my phone though.
I can get into cwm... I just can't re-root my phone. It appears everything is fine beyond that.
Sent from my SCH-I500 using XDA App
EDIT: After a while of trying I finally figured out that I was able to use Adb, I just don't know what I'm doing most of the time. ADB and now I have my root back. The one click root did not work, but manually everything went ok. I still have voodoo and OC kernal, but eh, better than nothing at this point. I wanted to be able to created a nandroid back up... I still have yet to accomplish this, LOL, I may give it another try further down the road.
Thanks to everyone who tried to help me!
Wow...not sure if I want to try this or not now.
Has anyone done this SUCCESSFULLY?
So let's say I decide not to create a nandroid and leave my phone the way it is now...what's the worst that could happen? I have all my apps backed up through titanium backup.
Sent from my SCH-I500 using XDA App
Smitty9803 said:
Wow...not sure if I want to try this or not now.
Has anyone done this SUCCESSFULLY?
So let's say I decide not to create a nandroid and leave my phone the way it is now...what's the worst that could happen? I have all my apps backed up through titanium backup.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
It may work for you. Voodoo is weird from what I've read, for some it's fine and others not so much. I had a flurry of problems after disabling the lagfix and I almost felt like it wasn't worth it. Also, after finally getting my root back my accelerometer stopped working and I had to completely remove Voodoo and then re-flash back to voodoo to get it to work agian. I forgot to backup with nandroid again.... :? If you are going to try it, I would say completely remove voodoo via the uninstaller and then backup, because its hell if voodoo decides to go bipolar on your phone. You may lose all your data and root like I did. Who knows when it comes to voodoo?
I'm leaving mine as is and may backup with nandroid later. If you go for it, good luck.
Smitty9803 said:
what's the worst that could happen? I have all my apps backed up through titanium backup.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Between Titanium Backup and My Backup Pro (seems to handle things like the call log and sms/mms messages a little better, at least for me), I haven't used a Nandroid in a couple of weeks.
It's actually a pretty nice, streamlined process:
-Run the backups
-Do whatever hacky thing I'm doing
-Wipe data
-Sign in to Google and download Titanium from the market
-Restore apps with Titanium, then data with MB Pro.
-Fix any funny widgets
-Enjoy!
Smitty9803 said:
Wow...not sure if I want to try this or not now.
Has anyone done this SUCCESSFULLY?
So let's say I decide not to create a nandroid and leave my phone the way it is now...what's the worst that could happen? I have all my apps backed up through titanium backup.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I just created my nandroid backup! I chose to uninstall Voodoo then re-root my phone instead of just disabling voodoo. I haven't put voodoo back on yet, but I probably will. Not with the OC kernal because none of them are stable enough IMO. When I used the OC lagfix my phone would always freeze up when I did anything extensive. Google Earth for example, would cause it freeze up. Oh well, hopefully someone will come up with a good OC, and I'll be happy to donate to them for their hard work.
Seriously, I think you should just uninstall and create a backup. Then reinstall voodoo for that sweet Quadrant score. LOL
Mageta said:
I just created my nandroid backup! I chose to uninstall Voodoo then re-root my phone instead of just disabling voodoo. I haven't put voodoo back on yet, but I probably will. Not with the OC kernal because none of them are stable enough IMO. When I used the OC lagfix my phone would always freeze up when I did anything extensive. Google Earth for example, would cause it freeze up. Oh well, hopefully someone will come up with a good OC, and I'll be happy to donate to them for their hard work.
Seriously, I think you should just uninstall and create a backup. Then reinstall voodoo for that sweet Quadrant score. LOL
Click to expand...
Click to collapse
Respectfully, the kernels are fine. Different processors handle the same kernels differently. Most kernel threads have several different versions partly because of this. For instance, My GFs phone will run Dirks UC/OC well, without issue, but mine occasionally borked when I tried it, so I use JT's. You will see this effect more pronounced on boards for devices with many different kernels available.
Always a good idea to try each version of each kernel for a bit to see how you do.
Wow, I forgot about removing voodoo before doing nandroid backup / restore. I've done 2 backups and 1 restore without issue. Did I just get lucky? Man there's a lot of stuff to keep track of here!
Zennmaster said:
Between Titanium Backup and My Backup Pro (seems to handle things like the call log and sms/mms messages a little better, at least for me), I haven't used a Nandroid in a couple of weeks.
It's actually a pretty nice, streamlined process:
-Run the backups
-Do whatever hacky thing I'm doing
-Wipe data
-Sign in to Google and download Titanium from the market
-Restore apps with Titanium, then data with MB Pro.
-Fix any funny widgets
-Enjoy!
Click to expand...
Click to collapse
I like the sound of this! But I have a question...I looked into the MBPro and supposedly it backs up all of your apps along with your data/personal settings. If that's the case, why use titanium backup?
Sent from my SCH-I500 using XDA App
I installed Cognition 2.2 beta 9(with voodoo) and got my phone all set up and did a nandroid backup without disabling voodoo. I never thought to disable it and the backup worked fine. Now today I restored the backup and forgot about disabling voodoo and it worked but I didn't have any of my apps or the market, and I realized it was probably because I never disabled voodoo. So I disabled voodoo and restored the backup again and it worked perfectly.
So I don't think you need to disable voodoo to do a nandroid backup; just to restore one.
I haven't re-enabled voodoo yet. Battery needs to charge a bit.
I've done backup and restore without disabling voodoo, because I forgot. It worked fine though. Now that I have read about issues with disabling voodoo I am kinda nervous to to even try it.
What do you think I should do in the future?
Thanx, you guys rock for making our phones faster and better...
Alright, so....
I did a complete voodoo uninstall per Adrenalyns thread, ODIN back to stock, re-root. On either DI01 or DJ05 I have no market download ability, my Gtalk wont open (immediately closes) and nothing I do seems to work. I have ODIN'd about four times now, and no luck so far,
Any ideas?
Wipe data from privacy menu
Sent from my SCH-I500 using XDA App
jt1134 said:
Wipe data from privacy menu
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Lol. I've tried everything I think. This is new to me. Will do this again and pst results.
Edit: No dice. Market says starting download, but never pulls anything down. Try to open Gtalk, and it just immediately closes down. Going to look at steps in next post. I'm really frazzled at this point.
You could also try the three step process here (post 2):
http://forum.xda-developers.com/showthread.php?t=865076
Root explorer is the only file manager I have tried that can do step 2 easily though... And you may not have it installed given your predicament. Also note that titanium backup released a new version today that improves data wiping support for Galaxy S phones.
EDIT: I had run into the same issue with Market myself. Happened when I flashed stock kernel from adrynalyne's completely unvoodoo thread over my existing DJ05 (prerelease) Blackhole 2.2 using CWMR. I have never once installed Voodoo, so it was not related.
I didn't spend time troubleshooting it though. Nandroid restore via rom manager fixed me.
Swyped on XDA App. When in doubt, mumble.
soba49 said:
You could also try the three step process here (post 2):
http://forum.xda-developers.com/showthread.php?t=865076
Root explorer is the only file manager I have tried that can do step 2 easily though... And you may not have it installed given your predicament. Also note that titanium backup released a new version today that improves data wiping support for Galaxy S phones.
EDIT: I had run into the same issue with Market myself. Happened when I flashed stock kernel from adrynalyne's completely unvoodoo thread over my existing DJ05 (prerelease) Blackhole 2.2 using CWMR. I have never once installed Voodoo, so it was not related.
I didn't spend time troubleshooting it though. Nandroid restore via rom manager fixed me.
Swyped on XDA App. When in doubt, mumble.
Click to expand...
Click to collapse
Found an .apk of root explorer and no dice on all the listed steps. I did try a nandroid as well. I don't know what the hell is up. Gah.
Adrynalyne has a sweet Odin package under the development forum. Its called di01package3.tar and its a single flash file of about half a gig. I would link it but I am in a rush. It should be on the second page. Its a great package I've tried to brick my phone and this brings it back all the time. Tell me how it goes.
SCH I500 DJ05 voodoo5 OTB 1200 ghz ul SuperClean v.9
scottxda said:
Adrynalyne has a sweet Odin package under the development forum. Its called di01package3.tar and its a single flash file of about half a gig. I would link it but I am in a rush. It should be on the second page. Its a great package I've tried to brick my phone and this brings it back all the time. Tell me how it goes.
SCH I500 DJ05 voodoo5 OTB 1200 ghz ul SuperClean v.9
Click to expand...
Click to collapse
Found that this morning and flashed it. Also did a standard restore, file by file. whatever the problem is, it's on my phone, and it's not something that is being overwritten with the ODIN files. I even signed in under my finace's login and had the same market issues, otherwise I would assume it was my google profile.
ROFL. So check this, I copied a full nandroid backup from my gf phone to mine, flashed it.....
Still no market. Ha. Fing. Ha.
Lol damn dude that's the ****s :/
SCH-I500 - DJ05/SuperClean .9/Nemesis OTB 1200lv/Voodoo5/Darkstar
Just pointing out that Daswolven is up to exactly 666 posts right now.
He may really have to take it to Verizon now and tell them his phone needs an exorcism. But as stated before, it would be best to figure out what the hell happened... he did nothing wrong, and he tried everything in the playbook. Stumped! *Bump*
Have you wiped data/cache from stock recovery? Thats the only thing I can think of.
Sent from my SCH-I500 using XDA App
Yeah, he exhausted my entire list (Re: post 4), AND did fallingup's backtostock recovery steps, AND did Adrynalyne's all inclusive backtostock MEGA Odin recovery, AND did a stock nandroid recovery. His phone is a scientific mystery at this point.
Mystery it is. I managed to screw something up that is beyond ODIN or backup. lol. I'm sure it's voodoo related. Have some ideas to play with tomorrow though. we'll see.
Just curious, if Odin was used, which destroys voodoo (especially if using my odin file), how can it be a voodoo issue?
Reset your gf's phone and put your account data in. Wouldn't shock me if market failed on her phone.
Sounds like your problem is with your Google account. My bro in law had the exact problem with his fascinate and his was completely stock. His account miraculously started working again out of the blue after like 2 days lol. Good luck.
Just as a side note. I find my life happiest if I refresh all of my titanium backups before a data wipe, ESPECIALLY adw.
I have suspicions that some combination of rejiggered app versions between updates confuses the hell out of some shoddily written code in market so it is always nice to be able to go to the exact setup you recently had for everything you installed before the update. I say the bug is with Google Market.
When it sees this kind of error, it should be smart enough to recognize that no download is happening, and handle it in some way, or throw an error. Sitting there dumb-struck shows a lapse in engineering. And whomever might be in the peanut gallery that wants to bring up the halting problem and Alan Turing... he died of cyanide poisoning. Market is too important to be this fragile... bottom line!
Speaking of that, did you happen to try Titanium Backup's Market Doctor under settings? I doubt it will do anything for you. But hey, why not?
That said... Never seen anything that Odin couldn't save me from.
Swyped w/ XDA App. When in doubt, mumble.
Enter recovery > advanced > format system and everything else in that menu that says format then ODIN.
Sent from my SCH-I500 using XDA App
adrynalyne said:
Just curious, if Odin was used, which destroys voodoo (especially if using my odin file), how can it be a voodoo issue?
Reset your gf's phone and put your account data in. Wouldn't shock me if market failed on her phone.
Click to expand...
Click to collapse
Not only does my market work on her phone, but when I log into mine as her it doesn't. added to the mystery is my verizon app doesn't recognize my number, but tech support was unable to correct.
I did use titanium market doctor. I honestly think I've tried everything. lol.
I am beginning to believe my issue has to be a verizon network problem. There's no way that I can see it being hardware or software at this point. What the hell they would have to do with anything I have no clue.
As for voodoo, I only know that was where the problem started. I was flash happy and tried to flash Superclean 0.9 directly over a stock build straight from rom manager without disabling or using the red CWM. phone wouldn't boot past Sammy logo. Couldn't boot from a restore, and that's where my trips to ODIN started.
But yeah, once there, voodoo shouldn't have anything to do with it. In the end, it was just my not paying attention. lol.
After trying everything in the book, no dice. I did the unthinkable, and called Verizon tech support after reverting completely to stock. They couldn't troubleshoot it, of course, and sent a replacement. Came in today. Logged in, went to market, works fine.
Logged back into my other and no dice.
At this point the issue is a mystery, but at least it's resolved. I hate replacing like that, I always disagree with it, but I did actually try everything. lol.
Glad you have a working phone again Daswolven, sorry it took a trip to vz replacement.
I just blew away my market too. In my case, I was upgrading my blackhole install the lazy way. I narrowed down the cause to be wiping data and then being overzealous with Titanium.
I fixed by (wiping data again and) purging counter-productive backups, particularly:
* deleting my Accounts system data backup (copied gmail password from keypass instead)
* deleting my adw backup (adw has its own means of backing up settings and layout)
* continuing to abuse titanium
Note: this wouldn't have fixed Daswolven's problem.
As a side note, clockwork recovery froze up twice looking for data pre-install. Turned out to be nnd, just a battery pull.
All good now.
Swyped w/ XDA App. When in doubt, mumble.
I've been flashing this thing left and right since November (when I got it, teehee). It's been through over 10 Odins and 100 custom rom/kernel flashes. Even so, Odin has never failed me, nor has the ROMs. But lately, my phone has been freezing non stop, I thought I flashed Syndicate Frozen wrong so I reflashed after wiping and it still froze. I changed the kernel prefixes to 1000/200 instead of 1000/100 to see if it's the 100 scale being stupid, but no dice. I decided to flash MidNIGHT rom to see if that would fix the problem and it worked fine, but now another problem arose. My recovery can't find internal or SD storage anymore...I fixed the problem before by booting the phone up, then going into settings > Privacy > factory reset (although that froze the phone and I had to manually pull the battery) but once I rebooted, all was good...but I Odined back to DI18, automatically updated to EC05, then ran the EXT 4 one click root and it was fine, then I flashed Syndicate 1.1 again, froze on me, restored my working version of midNIGHT rom, now it's giving me that internal storage problem again in recovery.
Is my phone about to die??? I took a picture of the recovery error with my brother's phone.
Those aren't big-deal errors - but I've seen them before when I flashed CWM3 and entered it early (I can't tell you exactly what I did). Just Odin again, flash CWM3, let it convert, and restore the backup. You should be fine. But no, your phone is fine.
And, see the SRF thread. The freeze fix has been posted many times.
Perhaps you should try something other than Syndicate for a while...maybe try an RFS based ROM. Sounds like all your problems start with flashing Syndicate.
Stock EC05 RFS with Genocide 0.5a kernel has been rock solid for me and unbelievable battery life.
I'll give it a try, thanks!
I get those same errors when I use reboot recovery to get to CWM3, but when i use the 3 finger method it works fine.
What method did you use to boot to cwm?
Tortel1210 said:
I get those same errors when I use reboot recovery to get to CWM3, but when i use the 3 finger method it works fine.
What method did you use to boot to cwm?
Click to expand...
Click to collapse
It was Quick Boot app.
Overstew said:
It was Quick Boot app.
Click to expand...
Click to collapse
There's your issue.
k0nane said:
There's your issue.
Click to expand...
Click to collapse
Why would that be the issue? It makes that app obsolete then.
Overstew said:
Why would that be the issue? It makes that app obsolete then.
Click to expand...
Click to collapse
Quick boot is a hard reset. Cause of this it causes data corruption. Use the reboot option built into the rom.
If you wanna reboot into recovery after hitting the reboot 3 finger death grip. It will reboot into recovery
Sent from my SPH-D700 using Tapatalk
Overstew said:
Why would that be the issue? It makes that app obsolete then.
Click to expand...
Click to collapse
MysteryEmotionz said:
Quick boot is a hard reset. Cause of this it causes data corruption. Use the reboot option built into the rom.
If you wanna reboot into recovery after hitting the reboot 3 finger death grip. It will reboot into recovery
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Not only that, but something just doesn't set right when you do it - I can't tell you exactly what, but that's definitely the cause right there.
Had both of these same issues as well on SFR 1.1 and also thought my phone was in trouble. Quickboot caused problems in CWM3 and data corruptions, so had to wipe and reflash. Then, like a number of others, I started having the freezing problems on SFR. Unfortunately, hadn't made it through all the pages of issues in the thread (and freezing issue wasn't yet noted in 2nd post when I downloaded the rom), so ended having to do several battery pulls, which caused more data corruption that required wiping and formatting sd card. Since the posted fix is to flash a kernel that is said to break the camcorder, which I use, I decided to flash back to midnight and all is working again.
I don't want this post to be seen as me knocking SFR. The team at ACS does great work and I'm sure the kernel works for most users. Once the freezing issue is resolved, I'll probably try SFR again, because I like their roms. Just wanted to let you know others are having the same issues.
mis3 said:
I don't want this post to be seen as me knocking SFR. The team at ACS does great work and I'm sure the kernel works for most users. Once the freezing issue is resolved, I'll probably try SFR again, because I like their roms. Just wanted to let you know others are having the same issues.
Click to expand...
Click to collapse
It is resolved. Search the thread. Use the posted kernel.
k0nane said:
It is resolved. Search the thread. Use the posted kernel.
Click to expand...
Click to collapse
I'd totally use that fix if my camera worked with it. :S
any kind of quick reset (quickboot or pulling battery with power on) is bad news on a non-journaled ROM.
Overstew said:
I'd totally use that fix if my camera worked with it. :S
Click to expand...
Click to collapse
Try the camera APK from EB13. The camera works, too - only the camcorder doesn't.
k0nane said:
Try the camera APK from EB13. The camera works, too - only the camcorder doesn't.
Click to expand...
Click to collapse
No camcorder is a deal breaker for me (have a 6 year old that loves home movies). Hoping for a new kernel soon.
Sent from my SPH-D700 using XDA App
mis3 said:
No camcorder is a deal breaker for me (have a 6 year old that loves home movies). Hoping for a new kernel soon.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Try the APK from EB13 before you say that.
I thought everyone knew not to use quickboot that's why the roms have reboot in the power options but I'm scared to even use that and never have.
Sent from my SPH-D700 using XDA App
jbadboy2007 said:
I thought everyone knew not to use quickboot that's why the roms have reboot in the power options but I'm scared to even use that and never have.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
midNIGHT rom came with Quickboot.apk, so I assumed it's okay. I'll ditch it right away, though.
not meaning to hijack the thread butttt
is adb reboot acceptable to use on a non journal rom?
So ever since I started some 2.3.5 ROMs I've been noticing that the ROM runs great for a couple of days. Just when I think all is going great services start crashing. Google Services, Email, Browser, Titanium Backup... etc. I'm really not sure what is happening here. I've noticed it on MIUI ROM so I switched over to NoFrills-AOSP and nope still having the same issue. Does anyone else have this issue?
reboot your phone every no and again, never hurts, also, Q&A.
This has happened to me every now and then, and reboot your phone every couple of days is good for it. Could also be you have flashed a different kernel over kernel and not cleaned stuff out.
LoL Yeah this probably belongs in Q&A but what was there at the time didn't seem to Developer-ish looking haha.
Anyways, yeah I've tried rebooting about 5times already. After every flash I reboot twice before really settling down to put stuff back in. That might have been the case when I was doing the MIUI ROMs but the NoFrills-AOSP ROM I have now was fresh from Stock Odin flash. Should I just try a new Kernel maybe?
also happening to me. i reboot once a day but still it occurs. btw im on MIUI
Over time I've noticed the same thing. Similar to a Linux memory leak... No matter what rom, radio or kernel I use the available ram dwindles to almost inoperable speed. A reboot on my Vibrant is almost daily depending on what I do with my phone. Even with CWM, Overstock and Zendroid all together I still have the same issue's, any viable fixes for this?
Sent from my SGH-T959 using XDA App
i knew it wasn't just me. i just rid did my phone back to stock UVJFD. i'm trying to decided if i should just go back to Bionix or maybe try again with either MIUI or Simply Honey. If stock were 2.2 I'd be fine and just stick with it, but its not so I need to flash something AH!! lol
CharlieBoy808 said:
So ever since I started some 2.3.5 ROMs I've been noticing that the ROM runs great for a couple of days. Just when I think all is going great services start crashing. Google Services, Email, Browser, Titanium Backup... etc. I'm really not sure what is happening here. I've noticed it on MIUI ROM so I switched over to NoFrills-AOSP and nope still having the same issue. Does anyone else have this issue?
Click to expand...
Click to collapse
Stop restoring from titanium backup, and just reinstall your apps from scratch.
I had this same issue, found out it was my titanium backup app restores that were at fault.
Ya alot of people don't realize.. you can't use titanium with miui.. use the miui backup app.. if u come from a a different rom, Use titanium to restore, backup with the miui backup app, then reflash miui after wiping system, then restore using miui restore app.. everything should b alot better
Sent from my T959 using XDA Premium App
CharlieBoy808 said:
i knew it wasn't just me. i just rid did my phone back to stock UVJFD. i'm trying to decided if i should just go back to Bionix or maybe try again with either MIUI or Simply Honey. If stock were 2.2 I'd be fine and just stick with it, but its not so I need to flash something AH!! lol
Click to expand...
Click to collapse
Stock is 2.2
Sent from my T959 using XDA Premium App
i use titanium back up all thie time with miui and it gives me no problem at all and i havent had any crashing at all im runing miui 1.9.16 ss-6 with bail and its giving me no problems at all are u doing a full wipe when u install i always wipe data cache and then format data and system thin install everything hope this helps
ceoesquad said:
i use titanium back up all thie time with miui and it gives me no problem at all and i havent had any crashing at all im runing miui 1.9.16 ss-6 with bail and its giving me no problems at all are u doing a full wipe when u install i always wipe data cache and then format data and system thin install everything hope this helps
Click to expand...
Click to collapse
Well you've just gotten lucky
Sent from my T959 using XDA Premium App
TI backup is not necessarily the issue with this. I've had the same problem for the last few week, and I've been using the MIUI backup exclusively. I might've used TI the first time I restored, but every other time it's been MIUI, mostly because it's WAY better.
Hmm ok well maybe the stock Odin I have is 2.1 because that's what it said in the about phone section. Anyways, TI causing a problem? or not causing a problem.. hmm LoL Oh how I love technology conflicts. Well right now I'm sitting on Simply Honey RC1 and so far no crashes yet. I went from Stock to Light then to Simply Honey as instructed. I did restore using TI, but I might flash back to MIUI from Stock and give it another try.
check your datadata partition and see if it's full. since miui is based off cm7, i'm assuming it uses the same partition scheme. if datadata is full, that may be your problem.