Database Develop

No Custom roms are able to install after Axura 2.0

Every single one of them are failing @ System.
I have flashed many roms and have yet to see this issue.
I have even tried to install a nandroid and they say system.img not found, skipping restore of System
my quadrant before doing anything was ~950 so im assuming no lagfix was present.

did you flash back to stock with odin1click??

ed116 said:
did you flash back to stock with odin1click??
Click to expand...
Click to collapse
no, i typically never do.
i have a stock eclair rooted nandroid but eh.
trying to avoid using odin right this minute...

iamamp3pimp said:
no, i typically never do.
i have a stock eclair rooted nandroid but eh.
trying to avoid using odin right this minute...
Click to expand...
Click to collapse
Going back to stock is the only safe way to install a rom imo.
Do a proper stock install and watch all the roms work.

im sure it will.
im just trying to learn why. it all started when i went to install SetiroNs 1.4.6 cwm

ccdoggy said:
Going back to stock is the only safe way to install a rom imo.
Do a proper stock install and watch all the roms work.
Click to expand...
Click to collapse
+100000000

iamamp3pimp said:
im sure it will.
im just trying to learn why. it all started when i went to install SetiroNs 1.4.6 cwm
Click to expand...
Click to collapse
Because it is the phone...not the rom or kernel...unless you had a bad flash to begin with.
This is why it is recommended when switching to different roms...and even sometimes flashing updates to certain roms ...that it is the most prudent thing to do, to head off these types of issues that come up sometimes. It is also recommended to do a master clear as well...and I usually go one step further and wipe and format the drives and do a factory reset. Sometimes doing it more than just once too. It may be a royal PITA...but...the alternative is what you are experiencing it seems...
Mac

is there a way to tell which filesystem is being used?
i have CWM 2.5.1.2
my Axura restore did work.......so i at least have a phone for the moment

[Q] Why go back to stock 2.1 before each flash?

Hey all. Just joined the forums a few minutes ago and I have a burning question on why it is necessary to flash back to stock with odin before you try different roms. Why can you not just boot into clockwork, factory wipe, wipe cache, wipe d cache and then simply load the new rom from sd? The reason I ask is because I have been bouncing between cognition and paragon for about 2 weeks now NOT using the method of flashing back to stock 2.1 without a single problem. I'm sure there is a good reason flashing back to 2.1 before trying new roms, I would just like to know why. I was able to preform a stock wipe using odin3 one time last week (just did it to make sure the phone would do it) it just seems like a really long process, but I'll start doing it that way to avoid a brick.
Thanks

to be safe, and some roms mod files that others dont, some roms depend on apps and files in the stock rom that might be different or not there at all in other roms.
long process? extra 5 minutes when you get used to it. if you are ATT use ODIN ONE CLICK to restore stock 2.1 (hint: it takes one click)

For the most part, you don't really need to flash back to stock. It used to be a bigger deal to flash back to stock because some of the Roms would intervene with each other and mess things up. It is still recommened for a clean flash, but I rarely do it and my flashes work great.
EDIT: @Trusselo: damn it! Second time someone beat me to the answer tonight!

HAHA
and forget ODIN ONE CLICK !!
i keep forgetting about this
http://forum.xda-developers.com/showthread.php?t=944418
ALL IN ONE CAPTIVATE TOOLBOX

I have been trying roms weekly since November and have only needed to flash to stock twice, after failed flashes caused by my lack of patience. YMMV of course

jayjr1105 said:
Hey all. Just joined the forums a few minutes ago and I have a burning question on why it is necessary to flash back to stock with odin before you try different roms. Why can you not just boot into clockwork, factory wipe, wipe cache, wipe d cache and then simply load the new rom from sd?
Click to expand...
Click to collapse
It's not necessary and not even a good idea. Also, why wipe cache and d-cache when the install script does that?

Trusselo said:
to be safe, and some roms mod files that others dont, some roms depend on apps and files in the stock rom that might be different or not there at all in other roms.
Click to expand...
Click to collapse
ROMs don't mod or use any files which are on the phone prior to installing them. All the files on your phone after the install were in the CWM flashable zip file. Any ROM cook would be stupid to do otherwise. The exception would be no-wipe ROMs, but you would never flash to stock before using one of those.

Ive also wondered this as well and talking to guys like opcow, and a couple other Devs such as MikeyMike and a lot of guys at the Andromeda IRC they all agree that you should be perfectly fine now as long as you wipe everything before you flash.
I may try with Andromeda when I get home because I have my PC and Jig there just in case but still may try now. But also tlaking to a lot of users that they dont even do it anymore now because of the install scripts and as Opcow said if you think logically its technically safer.

Trusselo said:
long process? extra 5 minutes when you get used to it. if you are ATT use ODIN ONE CLICK to restore stock 2.1 (hint: it takes one click)
Click to expand...
Click to collapse
Actually thats not true at all.
If your a build 1009 and under you can use the one click. Although the build 1008 sometimes have problems.
But for the Build 1010's and up (like me) you have to use Odin3 and take a good 30-40 minutes just to get to JH7 because half of the time I lose my 3 buttons then have to push the 3 button fix over via ADB. I have gotten use it and its a pain in the ass.
And the time I listened to someone that says ALL ATT people can use the one click it completely ****ed my phone and if I didnt have a jig my phone would have been completely screwed up.
Im not trying to be rude im just saying I saw a post very similar to that a couple weeks ago and it came very close to completely bricking my phone and reading posts here now saying they have the same problem and if they dont have a jig they just got a 200 dollar paper weight.
Sorry for getting off topic back to topic today Im going to flash Andromeda over Darkyy 9.3 and wipe data cache and d cache in CWM and see how it goes although everyone and even the devs and a lot of users now a days say it should work perfectly.

Dlev7 said:
Actually thats not true at all.
If your a build 1009 and under you can use the one click. Although the build 1008 sometimes have problems.
But for the Build 1010's and up (like me) you have to use Odin3 and take a good 30-40 minutes just to get to JH7 because half of the time I lose my 3 buttons then have to push the 3 button fix over via ADB. I have gotten use it and its a pain in the ass.
And the time I listened to someone that says ALL ATT people can use the one click it completely ****ed my phone and if I didnt have a jig my phone would have been completely screwed up.
Im not trying to be rude im just saying I saw a post very similar to that a couple weeks ago and it came very close to completely bricking my phone and reading posts here now saying they have the same problem and if they dont have a jig they just got a 200 dollar paper weight.
Sorry for getting off topic back to topic today Im going to flash Andromeda over Darkyy 9.3 and wipe data cache and d cache in CWM and see how it goes although everyone and even the devs and a lot of users now a days say it should work perfectly.
Click to expand...
Click to collapse
+1 Guys if you don't know exactly what to do/suggest please don't say it. I'm not trying to start a war, but a wrong suggestion can easily soft or hard brick someones phone. This is a forum, so no one can stop you from saying things, but think about if it happened to you? You would be pissed!
Anyways back on topic, what model phone do you have, because having a 1009 model phone makes flashing and going back to stock (usually) so much easier. But then again, I rarely use odin because all the roms are compatible for the most part.
Sent from my SGH-I897 using XDA App

I've never used ODIN because I haven't wanted to try to run it from GNU/Linux in a virtual box.
I just wipe and flash from clockwork like the op. Been flashing roms for a couple months now, never had a single problem. (except when I noobed it up by trying to flash back to a nandroid backup via Rom Manager. Even then, didn't need Odin to sort it out).
If I ever run into a problem, then I'll try Odin, but I'm waiting to cross that bridge till I come to it.

To prevent exceptions or troubles from the version you already have... so everybody comes from the same rom, understand?

I flash to jf6 because that's what I have been conditioned to do for a while. However, the few times I was impatient and didn't....no problems either.
From all the reading I've done here, the only reason to do it is for the placebo effect.

There was once a time when all the new roms were built on the unofficial froyo and it only had 3e recovery. The quickest way to get around that was to flash stock. Also the lag fixes were tricky and easily fixed by flashing stock. Now recovery is in the kernel. As long as you insure the kernal lag fix in rom A understands the kernal lag fix in rom B flash away. Nandroid backups are kind of useless they don't backup the kernal or the modem. Save odin for when things go really wrong(;~ )
Sent from my i897 using XDA App

I have done it both ways, and there its no difference going back to stock and or flashing over other roms. I flash often, have not got stick in boot loop in months

I like to go back to stock since I KNOW that everything has been defaulted back to normal. Just a security blanket step for me.

I flashed andromeda over darkyy 9.3 just wiping data cache and d cache. Nothing wrong. Everything worked perfect so I got to believe that if you just wipe everything it should work perfectly.
Just for safety I got a jig and odin but for now I'm saving a good 45 minutes to not flash back to stock
Sent from my SGH-I897 using XDA App

[Q] Stuck in bootloop - What should I do?

Good evening guys!
So I'm stuck in a bootloop, and it doesn't look that I will come out of it. I'm running ROCKET ROM V22, and the Abyss3.9 kernel.
So what do you recomend me to do?
I'll now over the night keep my phone on, to try to get out of the bootloop. But I would need som advice what I shall do.
The problem is that the phone won't mount as a storage device in the computer. And I have no backup in my phone, only on the computer, so I can't restore it easy.
Help me! *said with panic on my voice*
Best regards MinnesotaVikings1961

Hi there,
Bootloops happen every now and then, if something collides or is misconfigured.
In my very own experience most boot loops happen to be script related.
This is why you should´t worry too much.
You still can enter CWM?
If so enter CWM and wipe completely (factory, cache, dalvik) and after that (NO REBOOT!!!) just reflash the ROM which just didn´t happen to work properly.
If it still is in boot loop there might be something wrong with the ROM.
> Rom is guarantied completet? No broken Download?
> Rom is really for the exact telephone model you got? (Galaxy S for example has several submodels which slightly differ from original)
In case you do not have a rooted device without CWM only thing you can do, is to begin from scratch by flashing an official ROM from Samsung via odin.
With that you should flash a kernel with CWM next time, cause it much easier to recover your device including you´ll keep all your private stuff.
Flashing the Samsung-Rom via odin will kill anything saved but the external SD.
hope this helps
# Rodger #

DJ-Tumor said:
Hi there,
Bootloops happen every now and then, is somethine collides or is misconfigured.
In my very own experience most boot loops happen to be skript related.
This is why you should´t worry too much.
You still can enter CWM?
If so Enter CWM, wipe completely (factory, cache, dalvik) and after that (NO REBOOT!!!) just reflash the ROM which just didn´t happen to work properly.
If ist still is in bootloop there might be something wrong with the ROM.
> Rom is guarantied completet? No broken Download?
> Rom is really for the exact telephone model you got? (Galaxy S for example has several submodel which slightly differ from originall)
In case do not have a rooted device without CWM only thing you can do, is to begin from scrath by flashing an official ROM from Samsung via odin.
With that you should flash a kernel with CWM next time, cause it much easier to recover your device incl. you keep all your private stuff.
Flashing the Sasmung-Rom via odin will kill anything saved but the external SD.
hope this helps
# Rodger #
Click to expand...
Click to collapse
Have done as you said, but still problems.
One of the problems maybe can be that it isn't CWM but RedPill.
Yes, I did download the whole file, so no strange abort of the download.
And this is the correct ROM for the Galaxy Note.
If I still have this problems in 24 hours I will contact my store and let them know what I think. I want my money back. I can also add that I'm studying law, so I let the lawbook speek for itself.
But thanks for a fast answer!

Well sad to hear that. Laws have to be different from those in germany
You´re obviously trying to flash inofficial stuff on your own. There is no way the shop could be made resposible for.
So take my advice and reflash official ROM before you return the device.
That will help enormously.
But before runnign too fast, try to give some more information to us here:
What ROM are you trying to flash?
What ROM is installed before trying to flash?
What Kernel is used to flash?
Are you using mobile Odin?
Try to answer questiones I just dind´t think of

DJ-Tumor said:
Well sad to hear that. Laws have to be different from those in germany
You´re obviously trying to flash inofficial stuff on your own. There is no way the shop could be made resposible for.
So take my advice and reflash official ROM before you return the device.
That will help enormously.
But before runnign too fast, try to give some more information to us here:
What ROM are you trying to flash?
What ROM is installed before trying to flash?
What Kernel is used to flash?
Are you using mobile Odin?
Try to answer questiones I just dind´t think of
Click to expand...
Click to collapse
The laws are maybe a little bit diffrent. For example, the first 6 months, the seller or shop needs to prove that the product was working when the sold it. Something that they have very hard to prove.
I'm trying to install the ROCKET ROM V22 for SGN.
I had the MidNote V2.0
The Abyss3.9 kernel (I think that it's the correct way of spelling it).
No, I'm not using mobile Odin.
Edit: Can I install a stocket ROM, with my phone in bootloop, and non mountin as a drive in the computer?

MinnesotaVikings1961 said:
Good evening guys!
So I'm stuck in a bootloop, and it doesn't look that I will come out of it. I'm running ROCKET ROM V22, and the Abyss3.9 kernel.
So what do you recomend me to do?
I'll now over the night keep my phone on, to try to get out of the bootloop. But I would need som advice what I shall do.
The problem is that the phone won't mount as a storage device in the computer. And I have no backup in my phone, only on the computer, so I can't restore it easy.
Help me! *said with panic on my voice*
Best regards MinnesotaVikings1961
Click to expand...
Click to collapse
You need to flash rocket rom v20 before v22 that i belive is or problem if u can mount sdcard to computer u may have to take sdcard out of your phone and put in something else to load the program on the card then put back on phone and then flash v20 of rocket rom and then see if it boots up if it dose then u can flash v22
Sent from my GT-N7000 using XDA Premium HD app

Edit: Can I install a stocket ROM, with my phone in bootloop, and non mountin as a drive in the computer?[/QUOTE]
U could in download mode with odin pc
Sent from my GT-N7000 using XDA Premium HD app

Quick google search shows boot loops are pretty well known with this rom.
No you only can flash original rom with odin.
If there are important data on the device connect it cia usb and boot into cwm.
Now wath what happens. If you´re lucky mass storage mode is enables in the kernel and you got your storage mounted automated.
If not it´s time to cross fingers and search for an option to mount by hand.
I´m completely new to NOTE - all my knowledge comes from my i9000 which is a mega active community compared to the one of the NOTE
There is have the choice between 5 different ICS kernels alone
Each one has it´s abilities, so does one have the option to mount storage by hand.
This option can be found in "advanced". Hope this menu option is present in your rom
good luck!
# Rodger #

MinnesotaVikings1961 said:
The laws are maybe a little bit diffrent. For example, the first 6 months, the seller or shop needs to prove that the product was working when the sold it. Something that they have very hard to prove.
I'm trying to install the ROCKET ROM V22 for SGN.
I had the MidNote V2.0
The Abyss3.9 kernel (I think that it's the correct way of spelling it).
No, I'm not using mobile Odin.
Edit: Can I install a stocket ROM, with my phone in bootloop, and non mountin as a drive in the computer?
Click to expand...
Click to collapse
Yeah you can. Just go to this thread. Get a rootable rom downloaded. Just follow the instructions to the word of how to flash via odin. And you will have stock rom. And you can again root and install custom rom!! No need to run back to store !
Links-
Roms and guide- http://forum.xda-developers.com/showthread.php?t=1424997
Rooting and odin - http://forum.xda-developers.com/showthread.php?t=1329360

Midnote 2, as in ICS Midnote? You couldn't have been on AbyssNote 3.9, because it's a gingerbread kernel.
Perhaps it was Angelom's stock ICS rooted kernel?
Or did you flash AbyssNote 3.9 from Recovery, trying to go back to GB?

chasmodo said:
Midnote 2, as in ICS Midnote? You couldn't have been on AbyssNote 3.9, because it's a gingerbread kernel.
Perhaps it was Angelom's stock ICS rooted kernel?
Or did you flash AbyssNote 3.9 from Recovery, trying to go back to GB?
Click to expand...
Click to collapse
Well, I had been using ICS MidNote for a short time, due to a friend mine wanted to see ICS for the Note.
Now I tried to get back to my regular GB ROM.
/ Jimmy

You have me utterly confused here...What is the latest rom you were on before this bootloop? Midnote 2 or RR 22?
If Midnote 2 (ICS) with Angelom's kernel, and you did a factory reset at some point, there's hardly anything you can do except take your phone to Samsung service. If you had CF--Root ICS kernel, then try to follow this little set of instructions:
http://forum.xda-developers.com/showpost.php?p=22758543&postcount=6

chasmodo said:
You have me utterly confused here...What is the latest rom you were on before this bootloop? Midnote 2 or RR 22?
If Midnote 2 (ICS) with Angelom's kernel, and you did a factory reset at some point, there's hardly anything you can do except take your phone to Samsung service. If you had CF--Root ICS kernel, then try to follow this little set of instructions:
http://forum.xda-developers.com/showpost.php?p=22758543&postcount=6
Click to expand...
Click to collapse
Sorry for being confusing you!
Before this bootloop I was running MidNote V2.0, ICS. I then tried to flash ROCKET ROM, V22. And when I started up, this bootloop came up, and isn't solved in writing moment, very many hours later.
/ Jimmy

Case closed
I can now say that the case is closed. What I did is very simple. In fact, so simple I never thinked about it. The only thing I did was to unroot my phone using Odin.
But thanks for all tips and support!
/ Jimmy

What did I do wrong? N7000 bricked.

Good evening!
I've around with Androids for quite some time, and today, I finally got my N7000 to replace my I9100.
I've played around quite a lot with my I9100 and was happy with the CM9 nightlies for it.
I got my N7000 today and did the following:
1. Rooted it with this method: http://forum.xda-developers.com/showthread.php?t=1501719t=1501719
2. Decided to install the latest CM9 nightly. I booted the same CWM from the tutorial above, chose install zip from SD card and... It hang. I left it for about 5 minutes and nada, nothing. I decided to shut if off and...
3. Nada. Black screen, no recovery, no battery charging, no download mode, no nada, nothing. Dead!
I'll take it this week to the nearest Samsung repair center and check how much it's gonna cost to get it fixed (if they can get it fixed at all). I don't intend to use any warranty whatsoever since I know even tough I have not voided the warranty flashing a different kernel, I did messing with it.
I just wish to know what was my mistake, so I do not do it again in the future. AFAIK I did not mess with the bootloader, so I was supposed to be safe, right?
Do I have ANY hope of getting it resurrected?
Any opinion helps!
Thanks!

marcelo.ellmann said:
Good evening!
I've around with Androids for quite some time, and today, I finally got my N7000 to replace my I9100.
I've played around quite a lot with my I9100 and was happy with the CM9 nightlies for it.
I got my N7000 today and did the following:
1. Rooted it with this method: http://forum.xda-developers.com/showthread.php?t=1501719t=1501719
2. Decided to install the latest CM9 nightly. I booted the same CWM from the tutorial above, chose install zip from SD card and... It hang. I left it for about 5 minutes and nada, nothing. I decided to shut if off and...
3. Nada. Black screen, no recovery, no battery charging, no download mode, no nada, nothing. Dead!
I'll take it this week to the nearest Samsung repair center and check how much it's gonna cost to get it fixed (if they can get it fixed at all). I don't intend to use any warranty whatsoever since I know even tough I have not voided the warranty flashing a different kernel, I did messing with it.
I just wish to know what was my mistake, so I do not do it again in the future. AFAIK I did not mess with the bootloader, so I was supposed to be safe, right?
Do I have ANY hope of getting it resurrected?
Any opinion helps!
Thanks!
Click to expand...
Click to collapse
ALWAYS flash a GB Kernel or ROM BEFORE flashing a CUSTOM ICS ROM.

Okay. Lesson learned, trust me.
Now here's the part where I feel very stupid: what's a GB kernel? Why is that a requirement for ICS ROMs? Was it not for Gingergread ROMs?
And now here's the second part where I feel even stupidier: doesn't the kernel reside on the ROM/OS part of Android? Why would the kernel, which comes AFTER the bootloader, affect the boot of the Android? Wouldn't it just screw my phone, but wouldn't it still give me the chance of flashing another ROM?
Thanks for the help.

marcelo.ellmann said:
Okay. Lesson learned, trust me.
Now here's the part where I feel very stupid: what's a GB kernel? Why is that a requirement for ICS ROMs? Was it not for Gingergread ROMs?
And now here's the second part where I feel even stupidier: doesn't the kernel reside on the ROM/OS part of Android? Why would the kernel, which comes AFTER the bootloader, affect the boot of the Android? Wouldn't it just screw my phone, but wouldn't it still give me the chance of flashing another ROM?
Thanks for the help.
Click to expand...
Click to collapse
Because of an eMMC brick bug!
Anyways to round up, my way of flashing ROMS is flashing a GB Kernel called Abyss 4.2 and then reboot recovery, from then I wipe everything then flash any custom ICS Roms. I've had my Note for almost a week now and found no problems in flashing! But it did take me 2hrs to root doing heavy research but it paid off!
The guide I followed is from here take a few moments to read and understand then you will have no troubles in rooting/flashing again!

hing98 said:
Because ICS has not been officially released on the Galaxy Notes therefore we use a GB Kernel or ROM before we flash any custom ICS ROM.
Yes it was confusing at the start but to avoid bricking you must alwaysfollow the guides given by the Developer!
Anyways to round up, my way of flashing ROMS is flashing a GB Kernel called Abyss 4.2 and then reboot recovery, from then I wipe everything then flash any custom ICS Roms. I've had my Note for almost a week now and found no problems in flashing! But it did take me 2hrs to root doing heavy research but it paid off!
Click to expand...
Click to collapse
You may want to recheck your facts....ICS has actually been officially released in many countries......
Sent from my GT-N7000 using xda premium

stoney73 said:
You may want to recheck your facts....ICS has actually been officially released in many countries......
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Sorry was reading from another guide. Your right
---------- Post added at 01:12 PM ---------- Previous post was at 12:23 PM ----------
hing98 said:
Sorry was reading from another guide. Your right
Click to expand...
Click to collapse
Anyways its a bug that bricks your device,
you can find more information here
Cheers

I had a galaxy S where flashing process was different Wen u flash CM9 roms and if you want to get back to GB roms only way out was PC Odin and moreover you can wipe on ICS roms and install other roms. But wen i got the note the procedure was slightly different Brickin problems and moreover wen you are in ICS you can get back to GB with GB kernel only no need for PC odin. Just keep a copy of Abyss kernel 4.2 in your sd card and be sure to flash it when changing roms.....

Doesn't Franco rev3+ solve the brick bug?
Hi all,
since you're saying we have *always* to flash a GB kernel before having a factory reset, are you talking about those having the CF/Stock kernel?
I'll make it clear: as far as I know, Franco made a kernel that should avoid the brickage since its 3rd version (thread here --> http://forum.xda-developers.com/showthread.php?t=1491428). Who installed this kernel could just wipe from ICS and install any ICS ROM. Am I wrong? If so, please explain the whys.

UNBRICKED!
I too bricked my phone but after reading this guide (ABD wouldn't recognise my device so I couldn't follow it) I understood the partitions had become messed up.
I read somewhere about the PIT files.
I ODINed the ABYSS Kernal and PIT (Q1_20110914_16GB-patched) for my 16gb n7000 ticked the repartition box. It booted into CWM recovery and I used the restore and bingo.

Urgent - Only professionals answer please!

Before you start reading, please make sure, you are 100% sure of ur answers, and that you have TIME to answer them ALL with clarification
Really thanks for ur time and help!
So i got a samsung galaxy ace, it's rooted and with b84 CF-Root kernel.
1) The thing is sometimes, I press Wi-Fi button or Bluetooth, and in the Wifi it says Error and on bluetooth just won't conect. I don't know what the problem is, and the only solution is to reboot the phone. Is this a problem? Can it be fixed? If It can, how? If not, please read point number 2.
2) If its not fixable, what ROM you advice me to reinstall? I have s5830XWKS2, some people say the DDxxx8(or something like that) is better don't know why I'm no programmer...
2.1) If I really have to have to reinstall it in order to fix it, how can I do it? Can you point out the thread for it?
3) I run a small business, and I use Tasker for all my stuff. together with other 60+ apps I need to keep, i'm using SD card with ext partition with Link2SD. And the thing i'm most afraid of, is loosing all the data. I came from a Nokia 5800XM, and I flashed it some times, backups are easy to do. Now here on Android becomes a bit complicated. Maybe never someone cleared me enough about it. So what can I do to sucessfully restore all data on the new ROM? I got Titanium backups, and CWM..Will that backup even my dictionary saved words?
4) Thanks, and please, again, make notice that I can't loose anything due to my business, but I can't work with phone needing to reboot at random times cause of wifi or bluetooh beeing bricked.

First of all. There is no such things as urgent situation here. You should remember that.
Second thing. You should post questions in Q&A sub-section. General is for sharing and discussions.
Third thing. There is a adb logcat thingie, which allows to understand a root of your problem more than 'Help me. Something doesn't work'
I remain this thread open but move to correct section.

NunoPitbull said:
Before you start reading, please make sure, you are 100% sure of ur answers, and that you have TIME to answer them ALL with clarification
Really thanks for ur time and help!
So i got a samsung galaxy ace, it's rooted and with b84 CF-Root kernel.
1) The thing is sometimes, I press Wi-Fi button or Bluetooth, and in the Wifi it says Error and on bluetooth just won't conect. I don't know what the problem is, and the only solution is to reboot the phone. Is this a problem? Can it be fixed? If It can, how? If not, please read point number 2.
2) If its not fixable, what ROM you advice me to reinstall? I have s5830XWKS2, some people say the DDxxx8(or something like that) is better don't know why I'm no programmer...
2.1) If I really have to have to reinstall it in order to fix it, how can I do it? Can you point out the thread for it?
3) I run a small business, and I use Tasker for all my stuff. together with other 60+ apps I need to keep, i'm using SD card with ext partition with Link2SD. And the thing i'm most afraid of, is loosing all the data. I came from a Nokia 5800XM, and I flashed it some times, backups are easy to do. Now here on Android becomes a bit complicated. Maybe never someone cleared me enough about it. So what can I do to sucessfully restore all data on the new ROM? I got Titanium backups, and CWM..Will that backup even my dictionary saved words?
4) Thanks, and please, again, make notice that I can't loose anything due to my business, but I can't work with phone needing to reboot at random times cause of wifi or bluetooh beeing bricked.
Click to expand...
Click to collapse
Yes I experienced the same problem,could be software bugs problem so I think you can reinstall your software for the better.
I prefer cm mod7/8 for ace as it is much faster so you can try Google cyanogenmod for ace. They have all the tutorial you need.
As for your Apps, titanium backup will do fine. Its the best backup so far. Your dictionary words is the default system one? I recommend you smart keyboard pro as it has the function to backup all your words
So in short, backup your EVERYTHING with titanium backup, rmb your contacts too, and install cyannogen mod 7 or 8 whichever you prefer! Hope this helps!
Sent from my LG-P705 using xda premium

spaz1201 said:
Yes I experienced the same problem,could be software bugs problem so I think you can reinstall your software for the better.
I prefer cm mod7/8 for ace as it is much faster so you can try Google cyanogenmod for ace. They have all the tutorial you need.
As for your Apps, titanium backup will do fine. Its the best backup so far. Your dictionary words is the default system one? I recommend you smart keyboard pro as it has the function to backup all your words
So in short, backup your EVERYTHING with titanium backup, rmb your contacts too, and install cyannogen mod 7 or 8 whichever you prefer! Hope this helps!
Sent from my LG-P705 using xda premium
Click to expand...
Click to collapse
There's no such thing as cyanogen mod 8...only unofficial cm 7.1 kang and official cm 7.2...
Nunopitbull, wifi & bluetooth problems that you experience are caused by the kernel, not the firmware or rom...so my suggestion is to use a kernel that is not based on cf root or use a stock kernel (the one that came with your phone)...just root your phone with the update zip method will do, and for cwm flash the zip for it...the newest version for sga is 5.0.2.6...there's no need to flash a custom kernel...
About cwm backups, it backups your whole system and data partition and also your boot.img (kernel related)...so yes, it is quite safe to say that your whole phone is backup-ed...but keep in mind that stock roms use .rfs format for the partitions...new custom roms use .ext4 format...so to flash a backup of a stock rom, first flash a fresh stock firmware with ODIN and the cooper.pit file...then re-root and re-flash cwm to restore your phone...
And fyi, link2sd uses a second partition right? The apps inside the second partition can be relinked if you reset the phone...as long as you don't format the second partition...but personally I suggest you to use DTa2sd or amarulzz script as it saves more internal space...check it out...
Hope that all the above helps...

So you're saying my problem of wi-fi/bluetooth is because of kernel? Can you help me by PM how to get it working again? I wanted a custom kernel don't remember already why, but I think was for the custom speeds of CPU, so I could have low ones..
Just want this bug to disapear of bluetooth and wifi!
Ryuinferno said:
There's no such thing as cyanogen mod 8...only unofficial cm 7.1 kang and official cm 7.2...
Nunopitbull, wifi & bluetooth problems that you experience are caused by the kernel, not the firmware or rom...so my suggestion is to use a kernel that is not based on cf root or use a stock kernel (the one that came with your phone)...just root your phone with the update zip method will do, and for cwm flash the zip for it...the newest version for sga is 5.0.2.6...there's no need to flash a custom kernel...
About cwm backups, it backups your whole system and data partition and also your boot.img (kernel related)...so yes, it is quite safe to say that your whole phone is backup-ed...but keep in mind that stock roms use .rfs format for the partitions...new custom roms use .ext4 format...so to flash a backup of a stock rom, first flash a fresh stock firmware with ODIN and the cooper.pit file...then re-root and re-flash cwm to restore your phone...
And fyi, link2sd uses a second partition right? The apps inside the second partition can be relinked if you reset the phone...as long as you don't format the second partition...but personally I suggest you to use DTa2sd or amarulzz script as it saves more internal space...check it out...
Hope that all the above helps...
Click to expand...
Click to collapse

So far I haven't seen a custom kernel for sga that works flawlessly...especially the ones with oc function...only stock kernels work with the least problems...since you want to underclock, just use the stock kernel and set it to the lowest value with an app like set cpu...it shall do you fine...

Ryuinferno said:
So far I haven't seen a custom kernel for sga that works flawlessly...especially the ones with oc function...only stock kernels work with the least problems...since you want to underclock, just use the stock kernel and set it to the lowest value with an app like set cpu...it shall do you fine...
Click to expand...
Click to collapse
What are the other advntages with the CF Root kernel? I can't remmeber why I puted it, but I think they were another reason behind it...
Where I can get teh stock kernel? Or which one you advise?

Chill please...don't shoot questions in here...if you want quick answers, please search about it (e.g. go to the cf-root thread and read about the features, I don't memorise them, but I believe you want the overclock and a2sd features)...If you want direct answers, you will have to wait...
I understand that you need your phone for your business, it's very important to you...I'm trying my best to help out here ok? To get a stock kernel, just flash a stock firmware via ODIN...but you will have to re-root and re-flash cwm...any stock kernel will do, as long as it is with the firmware you flashed...

Ryuinferno said:
Chill please...don't shoot questions in here...if you want quick answers, please search about it (e.g. go to the cf-root thread and read about the features, I don't memorise them, but I believe you want the overclock and a2sd features)...If you want direct answers, you will have to wait...
I understand that you need your phone for your business, it's very important to you...I'm trying my best to help out here ok? To get a stock kernel, just flash a stock firmware via ODIN...but you will have to re-root and re-flash cwm...any stock kernel will do, as long as it is with the firmware you flashed...
Click to expand...
Click to collapse
Chill what? I'm not in a hurry for answers You answer when you can. I jsut reply when I can, if it was fast, I didn't noticed
I remember to put this kernel i did something from CWM reboot, your saying i need to reinstall a full ROM to get the stock kernel?:S And what's ODIN
Reply when u can, im in no hurry ;D

NunoPitbull said:
Chill what? I'm not in a hurry for answers You answer when you can. I jsut reply when I can, if it was fast, I didn't noticed
I remember to put this kernel i did something from CWM reboot, your saying i need to reinstall a full ROM to get the stock kernel?:S And what's ODIN
Reply when u can, im in no hurry ;D
Click to expand...
Click to collapse
Yea...a full stock samsung rom..you might wanna look at this
http://forum.xda-developers.com/showthread.php?p=12874680

Is your Samsung Galaxy Ace a GT-S5830 or a GT-S5830i ??
Sent from my GT-S5830i using xda app-developers app

If you want only professionals to answer your questions, take your phone to the Samsung Engineers....
Sent from my GT-S5830 using Tapatalk 2

NunoPitbull said:
Before you start reading, please make sure, you are 100% sure of ur answers, and that you have TIME to answer them ALL with clarification
Really thanks for ur time and help!
So i got a samsung galaxy ace, it's rooted and with b84 CF-Root kernel.
1) The thing is sometimes, I press Wi-Fi button or Bluetooth, and in the Wifi it says Error and on bluetooth just won't conect. I don't know what the problem is, and the only solution is to reboot the phone. Is this a problem? Can it be fixed? If It can, how? If not, please read point number 2.
Click to expand...
Click to collapse
Try flashing a new kernel, this is NOT a rom issue, just a kernel issue.