It seems after I flashed supernova anytime I go into rom manager and try to reboot to recovery I get this whole update media deal and than it says fail and i get stuck on the captivates regular recovery.I can't click reboot or anything it only lets me scroll. The only way I have been able to solve this is by pulling the battery then it'll boot into recovery. Anyone else experiancing this.
Sent from my Supernova laced Captivate using XDA App
1meanrex said:
It seems after I flashed supernova anytime I go into rom manager and try to reboot to recovery I get this whole update media deal and than it says fail and i get stuck on the captivates regular recovery.I can't click reboot or anything it only lets me scroll. The only way I have been able to solve this is by pulling the battery then it'll boot into recovery. Anyone else experiancing this.
Sent from my Supernova laced Captivate using XDA App
Click to expand...
Click to collapse
yeah....i fixed mine by not using ROM manager.....
1meanrex said:
It seems after I flashed supernova anytime I go into rom manager and try to reboot to recovery I get this whole update media deal and than it says fail and i get stuck on the captivates regular recovery.I can't click reboot or anything it only lets me scroll. The only way I have been able to solve this is by pulling the battery then it'll boot into recovery. Anyone else experiancing this.
Sent from my Supernova laced Captivate using XDA App
Click to expand...
Click to collapse
This is more than likely due to the lagfix which changes the file system from rfs to ext4, currently ROM Manager cannot see ext4 properly.
Just adding my two cents but you really should never use rom manager for anything. It is outdated and pointless now. Hold down the power button and select recovery to get into recovery mode or use the button method.
Sent from my SGH-I897 using XDA App
Same thing happened to me after flashing from Cog 3.04 to Serendipity.
After a little searching I came accross this link in the Serendipity thread for resolution if you need to boot into recovery mode from Rom Manager:
http://forum.xda-developers.com/showthread.php?t=909213
As others have mentioned, when I select Recovery mode from the Power menu I get into Clockwork Recovery without a battery pull.
Hello,
I've got a new captivate something like a week ago.
I got it with preception 10.4 rom and speed mod kernel and android 2.2.1.
The phone works very fast and I'm satisfied with the speed but the battery is draining very fast.
for example, yesterday I charged the battery and went to a friend, I pictured some photos, filmed a short video (1 minute), played a little game and after 5 hours the battery was 70%, I went to sleep and after something like 9-10 hours when I woke up the battery was 27%! Without using the phone!!
Is it normal?
And for my other questions:
1. How can I know if I have the lagfix enabled?
2. Is it good to upgrade to the official version of AT&T 2.2? Some people told that this is faster.
3. If I will change the rom should I be worried of the sim free unlock (that it will lock again)?
4. What are the best rom and kernel that will be fast and will have battery saving?
Thanks!
Elad92 said:
Hello,
I've got a new captivate something like a week ago.
I got it with preception 10.4 rom and speed mod kernel and android 2.2.1.
The phone works very fast and I'm satisfied with the speed but the battery is draining very fast.
for example, yesterday I charged the battery and went to a friend, I pictured some photos, filmed a short video (1 minute), played a little game and after 5 hours the battery was 70%, I went to sleep and after something like 9-10 hours when I woke up the battery was 27%! Without using the phone!!
Is it normal?
And for my other questions:
1. How can I know if I have the lagfix enabled?
2. Is it good to upgrade to the official version of AT&T 2.2? Some people told that this is faster.
3. If I will change the rom should I be worried of the sim free unlock (that it will lock again)?
4. What are the best rom and kernel that will be fast and will have battery saving?
Thanks!
Click to expand...
Click to collapse
I'm not too familiar with the Cognition ROM's. But I might take a look at WiFi, or you may have a app thats running in the background causing the drain. Do you have wifi or gps on all the time?
1. It was probably enabled by default. A really easy way is open File Explorer, go to your "Voodoo" folder, open it if there is a folder named "disable-lagfix", then your lagfix is not enabled. If you want to enable it, delete the "disable-lagfix" folder and reboot
2. I wouldn't waste my time with stock 2.2. Most all of the modded ROM's here are going to be better
3. I'm not familiar with that issue, never had it happen for myself
4. That is a hard question to answer, most of the Captivate devices are going to respond to a ROM/Kernel, a little bit differently. For example, my device LOVES Supernova JS5, where as your device might not run quite right on it. So my advice is to try it, if it works for you, use it. Read the threads, find a ROM that you think has really great support, so if you run into issues you can find help. Zelendel has posted in the Q&A section, threads for some of the more popular ROM's for the newer folks who get stuck
Voltage control App/RC6 and 1400 Kernel
I am currently running RC6 on my captivate with the 1300 kernel. I have no issues using and adjusting voltage control app with this set up. However, as soon as I try SGS kernel flasher and flash 1344 kernel or the 1400 kernel voltage control app begins to force close. I have removed and added back in with the same result. I am very happy with my set up, but would like to benchmark the other two. Any help would be appreciated. Thanks.
kangi26 said:
I'm not too familiar with the Cognition ROM's. But I might take a look at WiFi, or you may have a app thats running in the background causing the drain. Do you have wifi or gps on all the time?
1. It was probably enabled by default. A really easy way is open File Explorer, go to your "Voodoo" folder, open it if there is a folder named "disable-lagfix", then your lagfix is not enabled. If you want to enable it, delete the "disable-lagfix" folder and reboot
2. I wouldn't waste my time with stock 2.2. Most all of the modded ROM's here are going to be better
3. I'm not familiar with that issue, never had it happen for myself
4. That is a hard question to answer, most of the Captivate devices are going to respond to a ROM/Kernel, a little bit differently. For example, my device LOVES Supernova JS5, where as your device might not run quite right on it. So my advice is to try it, if it works for you, use it. Read the threads, find a ROM that you think has really great support, so if you run into issues you can find help. Zelendel has posted in the Q&A section, threads for some of the more popular ROM's for the newer folks who get stuck
Click to expand...
Click to collapse
Thank you very much!
I enabled the lag fix, not seeing a big improvement.
I will try to find a new rom because I can't continue with this battery.. draining like water!
1. Another questions, does a rom comes with a kernel or should I need to flash kernel too?
2. What mode does the phone need to be when I connecting it to computer to flash a rom?
3. What are this JXX all about?
4.If I am flashin to stock rom, how will it know to flash to 2.2 or it doesn't matter because the new rom is 2.2?
5. Does flashing to stock rom unroot my phone?
6. Do I need to disable lagfix before flashing new rom? If so how do I do it? just copying the disable-lagfix file back to the Voodo folder?
lol a lot a questions, but I'm sure you'll forgive me
Elad92 said:
Thank you very much!
I enabled the lag fix, not seeing a big improvement.
I will try to find a new rom because I can't continue with this battery.. draining like water!
1. Another questions, does a rom comes with a kernel or should I need to flash kernel too?
2. What mode does the phone need to be when I connecting it to computer to flash a rom?
3. What are this JXX all about?
4.If I am flashin to stock rom, how will it know to flash to 2.2 or it doesn't matter because the new rom is 2.2?
5. Does flashing to stock rom unroot my phone?
6. Do I need to disable lagfix before flashing new rom? If so how do I do it? just copying the disable-lagfix file back to the Voodo folder?
lol a lot a questions, but I'm sure you'll forgive me
Click to expand...
Click to collapse
Ok, here we go.
1. All of the ROM's come with modems and kernels
2. I would be flashing back to stock 2.1 and Master Clear before flashing a new ROM. After that is done, to flash to a custom ROM, you will be in Recovery Mode
3. The J** is, for lack of a better term, the build number. The farther down the alphabet you go the newer the release. The newest at this time is JS5.
4. When you flash to stock you'll use Odin which has stock 2.1 JF6 built in. You can get it here: http://www.mediafire.com/?0w2y31maz8mdom4 If you're going to a custom ROM, I wouldnt mess with the new Stock 2.2
5. Yes
6. I would. All you need to do(for Voodoo lagfix) is, open a File Explorer, go to your Voodoo folder and create a folder named disable-lagfix then reboot the phone
There is no reason to flash back to stock and master clear. It used to be a bigger deal but now they are all compatable. The only thing you might want to do is clear the dalvik cache in the advanced cmw menu in the recovery mode. I havent done any of this for about a month and after flashing over 10 roms im still seeing no problems.
Sent from my SAMSUNG-SGH-I897 using XDA App
Dupontrocks11 said:
There is no reason to flash back to stock and master clear. It used to be a bigger deal but now they are all compatable. The only thing you might want to do is clear the dalvik cache in the advanced cmw menu in the recovery mode. I havent done any of this for about a month and after flashing over 10 roms im still seeing no problems.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Thats probably true for you, but for the beginner it's the safest route to take. It is THE safest way to do it. The chances of things getting messed up are lessened
Elad, Check your PM
kangi26 said:
Ok, here we go.
1. All of the ROM's come with modems and kernels
2. I would be flashing back to stock 2.1 and Master Clear before flashing a new ROM. After that is done, to flash to a custom ROM, you will be in Recovery Mode
3. The J** is, for lack of a better term, the build number. The farther down the alphabet you go the newer the release. The newest at this time is JS5.
4. When you flash to stock you'll use Odin which has stock 2.1 JF6 built in. You can get it here: http://www.mediafire.com/?0w2y31maz8mdom4 If you're going to a custom ROM, I wouldnt mess with the new Stock 2.2
5. Yes
6. I would. All you need to do(for Voodoo lagfix) is, open a File Explorer, go to your Voodoo folder and create a folder named disable-lagfix then reboot the phone
Click to expand...
Click to collapse
Thank you, you're great.
About the mode I meant USB debugging or something like this.
How do I do this master clear?
About odin and all of this, when I will flash my rom I will use the captivate toolbox (http://forum.xda-developers.com/showthread.php?t=944418) so I think it will do it automatically. I want to do everything safe and I think this program is a great way to start.
Especially after I tried to backup my current rom using rom manager and it got me to recovery mode but the ok key button wasn't working, so I had to pull out the battery :S
Elad92 said:
Thank you, you're great.
About the mode I meant USB debugging or something like this.
How do I do this master clear?
About odin and all of this, when I will flash my rom I will use the captivate toolbox (http://forum.xda-developers.com/showthread.php?t=944418) so I think it will do it automatically. I want to do everything safe and I think this program is a great way to start.
Especially after I tried to backup my current rom using rom manager and it got me to recovery mode but the ok key button wasn't working, so I had to pull out the battery :S
Click to expand...
Click to collapse
I have never used the Captivate Toolbox, so I can't give you any advice on it
Take a look at you PM, see if that'll work for you
Elad92 said:
Thank you, you're great.
About the mode I meant USB debugging or something like this.
How do I do this master clear?
About odin and all of this, when I will flash my rom I will use the captivate toolbox (http://forum.xda-developers.com/showthread.php?t=944418) so I think it will do it automatically. I want to do everything safe and I think this program is a great way to start.
Especially after I tried to backup my current rom using rom manager and it got me to recovery mode but the ok key button wasn't working, so I had to pull out the battery :S
Click to expand...
Click to collapse
In recovery, the power/lock button is the ok button.
Sent from my CM7 powered captivate
sixstringsg said:
In recovery, the power/lock button is the ok button.
Sent from my CM7 powered captivate
Click to expand...
Click to collapse
I successfully installed serendipity rom with the help of kangi!
But I have a problem, when I want to enter CWM with rom manager I press "Reboot into Recovery" in the rom manager app and it reboots my phone and get me to the phone recovery (3e) and says that something was faild and I can't use the ok button because it doesn't working.
I have to pull out my battery and then turn the phone on again and then it gets me to CWM.
What is the problem? there's another way?
I don't think that pulling the battery like this is very healthy for my phone.
Elad92 said:
Thank you, you're great.
About the mode I meant USB debugging or something like this.
How do I do this master clear?
About odin and all of this, when I will flash my rom I will use the captivate toolbox (http://forum.xda-developers.com/showthread.php?t=944418) so I think it will do it automatically. I want to do everything safe and I think this program is a great way to start.
Especially after I tried to backup my current rom using rom manager and it got me to recovery mode but the ok key button wasn't working, so I had to pull out the battery :S
Click to expand...
Click to collapse
The captivate toolbox is an awsome program.
When you use it to flash a rom, it will push clockwork recovery onto the phone for you. just follow the instructions and you will be fine.
A few notes on the toolbox and Odin3,
you must have the samsung drivers installed on your computer, they take forever to install on my computer.
generally speaking, you will not need to use the 3button unless you flash someting like darky's extreme, and his instructions are very clear.
turn on debugging mode in settings/applications/development.
plug in the phone
click "flash to stock," use the one click and follow in the instructions.
let the phone fully reboot and go into sync mode, a minute later, the blue odin box will turn green and say "PASS."
Unplug the phone, turn debugging mode on again
plug in the phone, and when odin sees the phone (window will turn yellow) hit "master clear."
let the phone fully reboot again into sync mode
turn debugging mode on again
click root phone and follow the directions
If you want to open odin3, just click flash to stock with your phone unplugged and click which ever odin3 you want and it will open. This is very usefull if you want to use odin3 without the tool box.
After you flash the ROM, reboot in recovery and if you dig arround in the menus, you should see stuff about lagfix options and lagfix tweaks. make sure lagfix is enabled, if your not sure enable it and reboot into recovery. many roms install with lagfix not enabled, so yuo should always do this. once it changes the file system and reboots into recovery, go into tweaks and enable everything that has an (R) next to it. reboot and enjoy
Elad92 said:
I successfully installed serendipity rom with the help of kangi!
But I have a problem, when I want to enter CWM with rom manager I press "Reboot into Recovery" in the rom manager app and it reboots my phone and get me to the phone recovery (3e) and says that something was faild and I can't use the ok button because it doesn't working.
I have to pull out my battery and then turn the phone on again and then it gets me to CWM.
What is the problem? there's another way?
I don't think that pulling the battery like this is very healthy for my phone.
Click to expand...
Click to collapse
lol pulling the battery isnt the greatest thing to do.. but it shouldn't hurt it as long as its at one of those type of screens. If you were to pull it say.. doing a restore - that would be a fatal no-no.
Um.. if you have ROM MANAGER on your phone already it should have an "update.zip" that has all of the recovery advanced options in it.
Especially with Serendipity if you want to get into Recovery just hit the power button and click on Recovery - it will put you into the CWM recovery mode.
Elad92 said:
I successfully installed serendipity rom with the help of kangi!
But I have a problem, when I want to enter CWM with rom manager I press "Reboot into Recovery" in the rom manager app and it reboots my phone and get me to the phone recovery (3e) and says that something was faild and I can't use the ok button because it doesn't working.
I have to pull out my battery and then turn the phone on again and then it gets me to CWM.
What is the problem? there's another way?
I don't think that pulling the battery like this is very healthy for my phone.
Click to expand...
Click to collapse
With a custom ROM installed, most of the newer ones have a Extended power menu, press and hold the power button for a couple of seconds, let it go and it'll give the option for Recovery. Personally, after stock JF6, I dont have any need for ROM Manager anymore
Try to enter Recovery that way first, don't use ROM Manager, if that doesn't work, I would put the "update.zip" back on your phone, and try to re-install it again. Something may have hosed on you
Got it. Thanks everybody
FROYO4ME;11871783 as soon as I try SGS kernel flasher and flash 1344 kernel or the 1400 kernel voltage control app begins to force close. I have removed and added back in with the same result. [/QUOTE said:
BUMP - same issue here, but with Serendipity 6.2 ROM and paragon6-1400-100hz-0215-2245-cwm.zip kernel
Click to expand...
Click to collapse
I was wondering about updating to stock 2.2 but it wouldn't make sense, all the Roms here have got it already and they work good and have had all the bugs fixed (well most).
Sent from my SAMSUNG-SGH-I897 using XDA App
FIXED: Voltage Control app force close FC on Paragon RC6 1400 kernel
RashaMatt said:
BUMP - same issue here, but with Serendipity 6.2 ROM and paragon6-1400-100hz-0215-2245-cwm.zip kernel
Click to expand...
Click to collapse
ISSUE: Voltage Control app FC's on start in Paragon RC6 1400 kernel.
This is related to having previously installed the Paragon 1300 kernel (and the VC app was working there). I forgot to delete the OC/UV settings before flashing the 1400 kernel
FIXED: These steps may not ALL be necessary, but this is what I did, and it fixed the issue for me:
Uninstall Voltage Control app with TiBu
Delete /etc/init.d/S_volt_scheduler and /etc/init.d/S90scheduler (use Root Explorer or adb shell su)
Boot to CWM recovery
Delete cache and Dalvik cache
Re-flash Paragon RC6 1400 kernel ONLY (not the ROM) - paragon6-1400-100hz-0215-2245-cwm.zip
BTW I'm running Serendipity 6.2 ROM, and it's a beeautiful ride with this kernel
HTH
I have searched around and have found anyone with quite my same problem.
Here's my issue, my girlfriends Captivate wont enable USB Debugging in Download Mode. It works fine when the phone is booted into the OS but the AIO toolbox wont recognize USB debugging in Download Mode.
The phone is currently running fine with Precision. It's is just having some force close issues. But currently I am stuck on this ROM because of the lack of Debugging in download mode.
I have tried two different W7 computers. One is 32bit Professional and one is 64bit Ultimate.
I have tried uninstalling and reinstalling the USB drivers but to no avail.
Debugging mode had nothing to do with dl mode, what are you trying to do?
Edit: ok reading your comments again, are you having problems getting odin to recognize your phone?
CM7
Flash back to stock, but it never completes. Do I need to flash back to stock in order to flash a new rom? Because that seems to be what I have picked up.
No you do not have to flash stock. You are on precision, what kernel? What are you looking to flash?
CM7
finakechi said:
Flash back to stock, but it never completes. Do I need to flash back to stock in order to flash a new rom? Because that seems to be what I have picked up.
Click to expand...
Click to collapse
In my knowledge, flashing back to stock is best way to flash new rom..to avoid any complications...but you flash new rom without going back to stock as well
I think you should use ODIN3 V1.7 or v1.3 to flash back to stock...Its better and tested way to flash back to stock...
I used AIO and i bricked my phone...but the developer of AIO said u should use version 2.5 as its more reliable then version 3.0
I am using the SuckerPunch #50 100HZ Kernel (which come with 3.5). And I haven't quite decided which ROM I will use yet now. I was going to try cognition.
About the whole flashing back to stock thing, I just noticed a lot of the directions for the ROMs mention it.
Flashing back to stock is largely an old need that still its used by many. When custom kernels with built in lag fixes started coming about you where advised to either disable lag fix before switching roms, or flashing stock. This was because the recovery in the kernel could not under stand the ext 4 partition the lag fix was using. Most of the built in recoveries in the roms out there today now can understand the partition, because of this flashing stock is not necessarily needed. That being said I am not sure what kernel cognition uses and if this would hold true.
There are more threads of people soft bricking their phone using odin than there are any other issues. All that being said I would not be flashing roms if you can not get your arms around odin. God forbid something does go wrong you need to be able to recover.
CM7
No I am not worried about flashing in Odin. i have a Fascinate and have never had any real issues (save for one). I just never saw any of the "flash back to stock" issue in the Fascinate forums. Is this lag fix the same as the Voodoo lagfix I use on my Fascinate?
Yes I understand they are different phones so I wont be trying to flash one ROM from one phone to another. i just meant the concept behind it.
Cognition uses stock KB1 kernel with voodoo lagfix and CWM
Sent from my Captivate using XDA Premium
I you use Odin 1 click to stock. Never had any issues in over 100 flashes to stock. I rarely use it now because most roms install scripts remove any of the old rom fragments. Odin is a useful tool if something goes wrong during a flash and your getting fc's all the time. Simply hold volume and plug it in and go. I strayed away fro AIO toolbox due to multiple reports from it bricking their phone.
If the toolbox doesn't work just use Odin and all will be will. Its the easiest version of Odin there is (in my opinion)
Sent from my Captivate using XDA Premium
You can also boot in recovery and re flash the rom. Wipe the dalvik cache and fix permissions if your getting FC's.
Sent from my Captivate using XDA Premium
finakechi said:
No I am not worried about flashing in Odin. i have a Fascinate and have never had any real issues (save for one). I just never saw any of the "flash back to stock" issue in the Fascinate forums. Is this lag fix the same as the Voodoo lagfix I use on my Fascinate?
Yes I understand they are different phones so I wont be trying to flash one ROM from one phone to another. i just meant the concept behind it.
Click to expand...
Click to collapse
Lag fix doesn't affect USB debugging.
Sent from my Captivate using XDA Premium
If I am following you, it sounds like odin does not see the phone in debugging mode.
I had am issue where odin would only see the phone in sync mode, and I could not get my computer to see the folders on the phone in mass storage mode.
I reinstalled the drivers and everything was fine after that.
So I found someone posted how to get our phones into SAFE MODE yesterday. Basically wondering what does this entail? What can it be used for? Is it pretty much the same as SAFE MODE on a PC for fixing issues? Anyone know any REAL DETAILS. If you can spell them out here. I am wondering if it can be used in cases where we did something like flashing a theme, kernel, etc. And wound up in a bootloop if we can go into safe mode and make changes or fixes to what we did? Is it to be able to recover from a crash? Is it for fixing wifi issues? What else would it be included for? Any thoughts? Or input please. I may play around with it a bit to figure out more.
I have tried this on CM7 and on Continuum 5.5 so I am not sure if it only a Gingerbread thing or not. If you are on froyo or eclair try it out and see if it does go into safe mode also.
HOW TO:
1) REBOOT YOUR PHONE
2) ONCE THE BOOTSCREEN COMES UP HOLD DOWN THE MENU BUTTON AND KEEP HOLDING IT UNTIL IT IS FULLY BOOTED.
3)Boom You are in Safe Mode.
DO NOT BE WORRIED IF YOUR HOME SCREEN APPS AND SUCH ARE NOT THERE. IT IS SAFE MODE. TO GET OUT OF IT JUST REBOOT PHONE AND LET IT BOOT UP NORMALLY.
Sent from My KickAss Captivated CM7 OC'd 1.55Ghz/Undervolted
Well it is volume up, menu, power button, then at&t release power. Then at galaxy s screen release menu then rehold for safe mode on froyo...i didn't discover this or take credit for it..... Here is link for those who want to see sight from were it came from.....http://forum.androidcentral.com/t-captivate/37245-any-way-enter-safe-mode-captivate.html
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
What? it works the same on froyo and gb. Hold the menu button when the boot animation starts. No touching of any if the hard buttons.
This question is probably stemming from my comment In the talon thread yesterday...
no it can't be used to fix a bootloop from a bad theme or incompatible kernel, those are still system processes that are loaded in safe mode. What it's for is if you have some user app that's running amok...say you have an app that is constantly force closing, so much so that you can't get into uninstall it, or the app caused it to loop, boot into safe mode and it won't be loaded so you can easily navigate to where it's installed and delete it.
studacris said:
What? it works the same on froyo and gb. Hold the menu button when the boot animation starts. No touching of any if the hard buttons.
This question is probably stemming from my comment In the talon thread yesterday...
no it can't be used to fix a bootloop from a bad theme or incompatible kernel, those are still system processes that are loaded in safe mode. What it's for is if you have some user app that's running amok...say you have an app that is constantly force closing, so much so that you can't get into uninstall it, or the app caused it to loop, boot into safe mode and it won't be loaded so you can easily navigate to where it's installed and delete it.
Click to expand...
Click to collapse
I'm on cognition 5.1 and couldn't get it to work with just menu
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Weird...not much of a cog fan but on every I9000 rom it does it with the menu button...could be a kb1 thing? I never tried kb1.
studacris said:
What? it works the same on froyo and gb. Hold the menu button when the boot animation starts. No touching of any if the hard buttons.
This question is probably stemming from my comment In the talon thread yesterday...
no it can't be used to fix a bootloop from a bad theme or incompatible kernel, those are still system processes that are loaded in safe mode. What it's for is if you have some user app that's running amok...say you have an app that is constantly force closing, so much so that you can't get into uninstall it, or the app caused it to loop, boot into safe mode and it won't be loaded so you can easily navigate to where it's installed and delete it.
Click to expand...
Click to collapse
Thanks for the explanation. It was probably your post I had seen, tried it out on Continuum and then on CM7. Then I was more curious as to what it would be used for. Thanks again
Sent from My KickAss Captivated CM7 OC'd 1.55Ghz/Undervolted
studacris said:
Weird...not much of a cog fan but on every I9000 rom it does it with the menu button...could be a kb1 thing? I never tried kb1.
Click to expand...
Click to collapse
I can get into safe mode by only pressing the menu button on Fusion. Tho I was pressing it from before the boot animation started, if that somehow makes any difference.
P.S. I think it killed my widgets... since they are wiped off the home screens, and the only thing I did was reboot into safe mode and reboot back out.
DaNaRkI said:
P.S. I think it killed my widgets... since they are wiped off the home screens, and the only thing I did was reboot into safe mode and reboot back out.
Click to expand...
Click to collapse
Oh yeah that'll happen...those are apps that aren't loaded, and you have to reset them after normal reboot from safe mode. It's kind of like when you restore your launcher with tibu after a flash, the widgets will either be gone or won't load.
I recently rooted my Galaxy Exhibit 4G and installed the unofficial CM10 ROM. After a while I realized how slow everything was working, so I decided to turn back. However, when I tried to recover my previous backup (rooted stock) it gave me the stupid md5 error. followed directions on how to fix it, but then I had problems recovering the system and data. I then turned to Odin, but it didn't help, and my phone now tries to start up, reaches the Galaxy Exhibit 4G logo, and then fails to load, and tries over again. I can still access odin mode, but recovery won't boot and just reboots the whole system.
Can anybody please help me? What can I do? I tried to follow directions on the forums, and on the wiki, but everything just got worse. I have nowhere else to turn
Why not install a flavor of Gingerbread like Peach Sunrise or...gosh, I forget our GB days!
Honestly, look at Slimbean and an OC kernel. They've given me personally the best performance I've seen on this phone, but even they will slow down after a while. I do a fresh install every few months when the lag gets atrocious, keeps the phone spic and span.
There's only so much you can do on 300 Mb of ram- even on Gingerbread.
Sounds like you will have to flash a recovery using Odin. Once in recovery then you can flash a rom. The reason your phone won't boot up is probably because it has nothing to boot into. Try cm7. I have been running it while waiting for my Lumia 521 to get here and it is amazingly fast. Fastest my phone has ever been.
Sent from my SGH-T679 using xda app-developers app
BrandonCormier said:
Sounds like you will have to flash a recovery using Odin. Once in recovery then you can flash a rom. The reason your phone won't boot up is probably because it has nothing to boot into. Try cm7. I have been running it while waiting for my Lumia 521 to get here and it is amazingly fast. Fastest my phone has ever been.
Sent from my SGH-T679 using xda app-developers app
Click to expand...
Click to collapse
i used odin but i now have no access to recovery mode on my phone. every time i try to access i see the recovery logo but then it just reboots. i have factory phpne now which is already an improvement from the most brick my phone was beforre
danikvsn said:
i used odin but i now have no access to recovery mode on my phone. every time i try to access i see the recovery logo but then it just reboots. i have factory phpne now which is already an improvement from the most brick my phone was beforre
Click to expand...
Click to collapse
If you are using stock recovery then when you see the recovery screen hit the menu key. It should make the screen dim a bit. You should reboot into recovery then where you can flash cwm.
Sent from my SGH-T679 using xda app-developers app