[Q] exhibit 2 4g hangs on incoming call - Samsung Galaxy Exhibit 4G

Dear all,
i have an old samsung galaxy exhibit 2 4g and decided to install a custom rom. i used below mentioned link for the ROMs.
http://forum.xda-developers.com/wiki/Samsung_Galaxy_Exhibit_4G
i have tried majority of the ROMs after v4 but all of them are giving me same problem
Phone hangs on incoming call and only vibrates no sound. and i have to ultimately pull the battery out.
the issue is not observed on stock ROM.
It is also not observed on REMICS 3.0.1 but only if i disable backup and restore option. disabled this option on other custom rom as well but did not fix the issue on other ROMs.
I would appreciate any help.

wonderwall_85 said:
Dear all,
i have an old samsung galaxy exhibit 2 4g and decided to install a custom rom. i used below mentioned link for the ROMs.
http://forum.xda-developers.com/wiki/Samsung_Galaxy_Exhibit_4G
i have tried majority of the ROMs after v4 but all of them are giving me same problem
Phone hangs on incoming call and only vibrates no sound. and i have to ultimately pull the battery out.
the issue is not observed on stock ROM.
It is also not observed on REMICS 3.0.1 but only if i disable backup and restore option. disabled this option on other custom rom as well but did not fix the issue on other ROMs.
I would appreciate any help.
Click to expand...
Click to collapse
sorry late on this. which cwm or twrp version are you using? jfbs twrp 2.7.1.0 or cwm 6.0.4.8 is the latest which is need on kk roms also cars1198 has cwm6.0.4.9. picking one of these 3 is user preference. for kk roms lastest slimbean 7/7build and dcm 6/20 by jfbs is stable and for cm11 cars1198 6/19 build is pretty stable. any of these 3 should work just fine without any issues with latest recoveries. if you dont know how its just like flashing a rom except when you reboot you want to reboot boot back into recovery then do a fresh install. also on a complete fresh install what ever is on on your internal sdcard that you want to keep move it to external sd or pc. then format /system /data /cache /android secure and /sdcard0. then install rom only, reboot and wait for it to fully boot up. then reboot back into recovery and install gapps. then wipe dalvik-cache and reboot. after you sign into gplay give the phone time to sync your contacts and so forth which will bog down the phone for 1-30mins or longer depending how much needs to be sync. after that you should be ready to go with no or very minor issues. in which you would ask in the appropriate rom op.

TripFX said:
sorry late on this. which cwm or twrp version are you using? jfbs twrp 2.7.1.0 or cwm 6.0.4.8 is the latest which is need on kk roms also cars1198 has cwm6.0.4.9. picking one of these 3 is user preference. for kk roms lastest slimbean 7/7build and dcm 6/20 by jfbs is stable and for cm11 cars1198 6/19 build is pretty stable. any of these 3 should work just fine without any issues with latest recoveries. if you dont know how its just like flashing a rom except when you reboot you want to reboot boot back into recovery then do a fresh install. also on a complete fresh install what ever is on on your internal sdcard that you want to keep move it to external sd or pc. then format /system /data /cache /android secure and /sdcard0. then install rom only, reboot and wait for it to fully boot up. then reboot back into recovery and install gapps. then wipe dalvik-cache and reboot. after you sign into gplay give the phone time to sync your contacts and so forth which will bog down the phone for 1-30mins or longer depending how much needs to be sync. after that you should be ready to go with no or very minor issues. in which you would ask in the appropriate rom op.
Click to expand...
Click to collapse
hey there,
thanks for the reply.
I am using cwm v6.0.1.2.
What i get from your reply is that
flash the latest recovery, reboot in to recovery again
flash your suggested ROM, fresh install
boot in to the OS
boot again in to recovery and install gapps
boot the phone and give it a couple of hours to sych data and update if any and then see if its working or not.
i will give it a try and will let you know. btw i was not facing any issues on any other roms except the mentioned issue and all the roms were running pretty fast.

wonderwall_85 said:
hey there,
thanks for the reply.
I am using cwm v6.0.1.2.
What i get from your reply is that
flash the latest recovery, reboot in to recovery again
flash your suggested ROM, fresh install
boot in to the OS
boot again in to recovery and install gapps
boot the phone and give it a couple of hours to sych data and update if any and then see if its working or not.
i will give it a try and will let you know. btw i was not facing any issues on any other roms except the mentioned issue and all the roms were running pretty fast.
Click to expand...
Click to collapse
everyones had different issues using older recoveries. cwm 6.0.4.4-5 works for anything jb or below. the higher ones are for kk roms which is the most recent and both cars and jfbs kk roms are better then aoip or any of the other roms. Since ion hybrid thanks to adc team and more stable kk roms are out now. imo any of cars is cm roms are good for the everyday people while jfbs slim and dcm are geared more to those who want more features and customization (advance users). i always test both devs roms but personally i like jfbs roms better as far as what i do but any of the 3 are stable for everyday use now. but ya let me know if that helped out.

TripFX said:
everyones had different issues using older recoveries. cwm 6.0.4.4-5 works for anything jb or below. the higher ones are for kk roms which is the most recent and both cars and jfbs kk roms are better then aoip or any of the other roms. Since ion hybrid thanks to adc team and more stable kk roms are out now. imo any of cars is cm roms are good for the everyday people while jfbs slim and dcm are geared more to those who want more features and customization (advance users). i always test both devs roms but personally i like jfbs roms better as far as what i do but any of the 3 are stable for everyday use now. but ya let me know if that helped out.
Click to expand...
Click to collapse
tried cynanogen1, worked smoothly but did not fix the issue
slimkat 4.4.4, faced FC every second. it was almost impossible to even boot the phone.
first i thought there is some hardware issue but the phone is working fine on 2 roms so i guess thats out of the question. let me know if you could suggest something else.

wonderwall_85 said:
tried cynanogen1, worked smoothly but did not fix the issue
slimkat 4.4.4, faced FC every second. it was almost impossible to even boot the phone.
first i thought there is some hardware issue but the phone is working fine on 2 roms so i guess thats out of the question. let me know if you could suggest something else.
Click to expand...
Click to collapse
which cwm or twrp version did you use. I too was facing the fc's on my phone for a while but after using twrp 3.7.1.0 or cwm 6.0.4.8 i dont have that issue anymore. my personal exact order including mods i use.
1. flash twrp 3.7.1.0 < if you already have this or cwm 6.0.4.8 already
2. Format /system then /cache, then /data/ then /internal sd < so everything except /boot and /external sd
3. flash rom < if doing cm11 you can flash oc kernel right after
4. flash supersu < optional its the same as stock superuser but little more options like allow su on boot (on xda)
5. wipe davlik cache and reboot system
6. reboot boot back into recovery
7. flash gapps < if slim get it from slimroms, if dcm or cm11 the gapps from cars1189 mass cm build 1-5-14.
8. flash malive booster < (on xda)
9. wipe dalvik cache and reboot system
10. once full loaded back in install seeder 2.0 (on xda) have a check mark on all 3 with light profile then enable.
11. then finish signing in google account and updating apps. 30mins later its smooth as butter.

TripFX said:
which cwm or twrp version did you use. I too was facing the fc's on my phone for a while but after using twrp 3.7.1.0 or cwm 6.0.4.8 i dont have that issue anymore. my personal exact order including mods i use.
1. flash twrp 3.7.1.0 < if you already have this or cwm 6.0.4.8 already
2. Format /system then /cache, then /data/ then /internal sd < so everything except /boot and /external sd
3. flash rom < if doing cm11 you can flash oc kernel right after
4. flash supersu < optional its the same as stock superuser but little more options like allow su on boot (on xda)
5. wipe davlik cache and reboot system
6. reboot boot back into recovery
7. flash gapps < if slim get it from slimroms, if dcm or cm11 the gapps from cars1189 mass cm build 1-5-14.
8. flash malive booster < (on xda)
9. wipe dalvik cache and reboot system
10. once full loaded back in install seeder 2.0 (on xda) have a check mark on all 3 with light profile then enable.
11. then finish signing in google account and updating apps. 30mins later its smooth as butter.
Click to expand...
Click to collapse
you are the MAN man. from your instructions i deduced that i was not wiping davlik cache after flashing but before. now every rom is working fine, no issue is observed. thanks
Since you know your stuff could you let me know which rom is the best in terms of performance and battery life?
thanks again

wonderwall_85 said:
you are the MAN man. from your instructions i deduced that i was not wiping davlik cache after flashing but before. now every rom is working fine, no issue is observed. thanks
Since you know your stuff could you let me know which rom is the best in terms of performance and battery life?
thanks again
Click to expand...
Click to collapse
Stock wise Slim has better performance over cm11 with slightly less bettery life. to get the best performance to battery life follow my oc guide i posted. you want to keep the voltage equal to or less then stock voltage while having the highest frequency as possible. the lower voltage from stock the higher battery life over stock will be. if you do plan on overclocking and undervolting your self make sure you read my oc entirely before attemping. the oc guide methodology is the same for anything that can overclock including desktop cpus, gpus, and yes some nics. some routers as long as it can support a 3rd party firmware such as ddwrt or openwrt. other phones that have oc and voltage control support. you may also get some extra performance and battery saving by trying different build.prop tweaks or mods or any of the combination. some may help you and not me and vise versa and some may help everyone. its more about find what works best for you for what you do.

Related

[Q][Still not Solved] Nexus one getting buggy with 7.1 mod

Greetings fellowmen!!
Recently i thought of rooting my nexus 1. So i did some research and found out that the easiest way to do it was by unlocking the bootloader installing a custom recovery (I did Amon Ra) and then wiping the data\factory settings and flashing the cm 7.1 zip. So i did all the above and there you go....I had an n1 running cm 7.1 smoothly but then after a few hours it starts to piss me of. The problem is that whenever i lock the homescreen with the power button and wake it up again it just displays the main homescreen and does nothing i cannot navigate to the left or right homescreen cannot open app drawer in short it just hung up there doing nothing. I had to take out the battery atleast 15 times. I rebooted my device and it kept on giving me the same problem.
So then i reflashed cm 7.1 by wiping the data and factory settings and installing it again. But still it gave me the same problem. So then i thought of flashing 7.0.3 version instead and surprisingly that works like a charm. So is it the mod thats buggy or is it my phone.
One more question. I have the stock 2.3.4 gingerbread rom which i got from here!!
Code:
http://forum.xda-developers.com/showthread.php?t=1061648
This one in particular-
GRK39F OTA (stock vanilla - odexed, unrooted):
MD5: 35C8B4B9FD22DD4CA19C5D026E74411D
So to install this rom do i have to install it the same way i did cm by wiping data/factory settings and then installing flash from zip or is there any other way to do it ?
Thanks in advance for taking out valuable time and reading my long problem!!
I am running the latest version of CM 7.1 that was released within the last week or so without any issues. Got it from here. http://download.cyanogenmod.com/?type=stable&device=passion
Before that I was running the RC for 7.1. One thing to try it wiping multiple times before flashing. I assume you are running Amon RA 2.2.1, which is the latest. I have never had a problem with that recovery, however I flashed my ROM with this recovery. So far I think I like it better than Clockwork and Amon.
http://forum.xda-developers.com/showthread.php?t=1291970
As for installing other ROMs yes you do flash them the same way you flashed CM.
So are you saying that it was the recovery that was causing the problem?
Yes I am using the latest Amon Ra 2.2.1 version.
I also got the rom from that link.
And can you explain whats the difference between all these recoveries?
Thanks for replying!
I am not saying it is the recovery, I highly doubt that is the problem. I was just comparing differences. There does not seem to be much difference in the recoveries for what you are trying to do. The recovery I am running is a fairly new one that I just wanted to test out. I do think I like it better than the others.
First thing I would do is wipe 3, 4 or 5 times before flashing. I have had rare occasions where a single wipe would not do it for me. Also have you verified the Checksum of the CM download? Does recovery say it installed successfully? I have also had error installing a ROM in recovery but then had the phone still load the ROM.
Yes i did check the md5 checksums and they match perfectly. Though i did wipe it out only one time so maybe that could be the problem. I think i should get clockworkmod and wipe it through that and then flash cm 7.1. Amon RA doesnt really give us the option of wiping the system partition. right?
Correct Amon Ra does not have an option to format system partition. It's recommend you also wipe system when coming from a different ROM.
Try this file by temasek's, format-signed.zip
http://www.mediafire.com/?8vbd13b440coxx6
just flash it in recovery and it will clean everything, now you can flash CM7.1 again
Are you sure you can't wipe the system with Amon? I remember having that option, but it's been several months since I have used that recovery. Kind of makes me want to flash it to find out.
Before flashing a different ROM I always wipe system, cache and dalvik cache. It is definitely important to wipe the system before flashing a new ROM. I'm sure that is where your problem lies.
No, ClockworkMod has it, but Amon_RA doesn't. Supposedly it is in the works for the next version, but that was a long time ago when I heard that (probably back when v3 for clockworkmod came out).
I did a nandroid backup and flashed the format zip file and then flashed cm 7.1 and its giving me the same problem!!
I had to restore and go back to 7.0.3
Why is this happening
Edit: I also wiped the dalvik cache and factory reset it also but still it just freezes!!
Any advise?
Have you tried downloading the file again maybe form another location I doubt this is the problem but sometimes it's something you don't expect.
You could try from here http://wiki.cyanogenmod.com/index.php?title=Latest_Version
But how does it matter I checked the md5 checksum and it matches!!
Why not stay on CM7.0.3 theres not much difference between the 2
if you dont want to i suggest to try to flash Clockwork recovery and do a full wipe then reflash CM7.1
But still I want to see how 7.1 is!
The main point here is to upgrade and not taking the alternative of staying at the older version!
Please guys any help would be appreciated!!
Doesn't CM7 need clockworkmod 3.x?? Try to flash CWM3.x over Amon if you can get your hands on the flashable zip or if you can get into a working rom, use romManager to switch from amon.
thealphamale05 said:
Doesn't CM7 need clockworkmod 3.x?? Try to flash CWM3.x over Amon if you can get your hands on the flashable zip or if you can get into a working rom, use romManager to switch from amon.
Click to expand...
Click to collapse
Make no different if you use amon Ra or CWM. I would definitely stay away from cwm 3.x or higher if you're using sd-ext
Looks like Ill have to stay with 7.0.3 there doesnt seem to be a solution!!

[Q] Problem installing kernel. Please help.

Before I begin, yes... I did search and look through a few threads with similar titles but did not find my problem.
I am not a phone geek and I am new to all this, but I rooted my Note along with a "Franco kernel", which worked successfully. My phone booted up as it was before (in fact I noticed absolutely no difference in my phone, whatsoever).
The problems begun when I tried to install an "Abyss" kernel via CWM, which apparently installed successfully, but the phone would never get past boot-up (not so successful after all, huh?). I realized that it wasn't going to work, so I though no problem, and went back into CWM and re-installed the Franco kernel that I was using before (which worked). Strangely, this kernel, too, would now no longer boot.
I successfully restored the phone with a GB rom via odin (teriible rom), and proceeded to install the so-called "Hydracore" kernel (love the names) via cwm.... this kernel made things even worse. Once again the installation was supposedly "successful", but the phone doesn't go past boot. This time, it gets stuck on a very dim black screen, which isn't actually black, it is a dark creamy/pink hue that you can only notice in absolute darkness. (WTF?) This screen has random black blotches on it, but again, if you are in a lit up room the screen looks completely black and you cannot tell that it is actually lit. When I say that this kernel made the problems even worse, I say that because when this happens (dim black screen), I cannot even enter CWM recovery at all to try and install a different kernel. From here, I can only access download mode, and have no choice but to restore the phone with the GB rom via odin. I did so, and proceeded to install the latest version of "Hydracore" (v5.4) posted right here on XDA by the member 'chasmodo.' This time, I did the installation of the kernel via odin, which, once again, was supposedly successful... and once again a lie, as the phone just goes into the same black screen, with no option other than download mode.
The sole reason I have wasted hours of my life researching and understanding mobile phone terminology in the past few days is so that I can have jellybean on my Note. It seems that I am unable to do this because the Kernels are not working on my device. I have a very powerful and capable phone, which is currently stuck on this GB rom (which I think has to be the most terrible piece of coding ever made) so any help on this would be immensely appreciated.
Thanks in advance.
can you try go back to stock GB rom.. then upgrade to ICS and root using Dr Ketans method and then install Hydracore
You flashed Hydracore on GB rom? that's the main reason behind your problem, this Kernel is not for GB. Now either flash custom GB kernel or flash stock GB firmware using pc odin and then root it. Check post # 2 in this thread for rooting. (I guess you know how to do this )
Once you have root and cwm recovery, you can flash any custom rom you want.
jeetu1981 said:
You flashed Hydracore on GB rom? that's the main reason behind your problem, this Kernel is not for GB. Now either flash custom GB kernel or flash stock GB firmware using pc odin and then root it. Check post # 2 in this thread for rooting. (I guess you know how to do this )
Once you have root and cwm recovery, you can flash any custom rom you want.
Click to expand...
Click to collapse
Hot damn you guys are quick!
Silly me! :silly:
If I install any GB kernal can I then install CM10?
S-pen said:
Before I begin, yes... I did search and look through a few threads with similar titles but did not find my problem.
I am not a phone geek and I am new to all this, but I rooted my Note along with a "Franco kernel", which worked successfully. My phone booted up as it was before (in fact I noticed absolutely no difference in my phone, whatsoever).
The problems begun when I tried to install an "Abyss" kernel via CWM, which apparently installed successfully, but the phone would never get past boot-up (not so successful after all, huh?). I realized that it wasn't going to work, so I though no problem, and went back into CWM and re-installed the Franco kernel that I was using before (which worked). Strangely, this kernel, too, would now no longer boot.
I successfully restored the phone with a GB rom via odin (teriible rom), and proceeded to install the so-called "Hydracore" kernel (love the names) via cwm.... this kernel made things even worse. Once again the installation was supposedly "successful", but the phone doesn't go past boot. This time, it gets stuck on a very dim black screen, which isn't actually black, it is a dark creamy/pink hue that you can only notice in absolute darkness. (WTF?) This screen has random black blotches on it, but again, if you are in a lit up room the screen looks completely black and you cannot tell that it is actually lit. When I say that this kernel made the problems even worse, I say that because when this happens (dim black screen), I cannot even enter CWM recovery at all to try and install a different kernel. From here, I can only access download mode, and have no choice but to restore the phone with the GB rom via odin. I did so, and proceeded to install the latest version of "Hydracore" (v5.4) posted right here on XDA by the member 'chasmodo.' This time, I did the installation of the kernel via odin, which, once again, was supposedly successful... and once again a lie, as the phone just goes into the same black screen, with no option other than download mode.
The sole reason I have wasted hours of my life researching and understanding mobile phone terminology in the past few days is so that I can have jellybean on my Note. It seems that I am unable to do this because the Kernels are not working on my device. I have a very powerful and capable phone, which is currently stuck on this GB rom (which I think has to be the most terrible piece of coding ever made) so any help on this would be immensely appreciated.
Thanks in advance.
Click to expand...
Click to collapse
Hi there, sorry to hear of your challenges.
One thing to remember before flashing is the nature of safe / unsafe kernels. Equally as important is compatible / non compatible kernels. It's not clear from your post but did you flash Abyss on an ICS ROM? If so, Abyss is a GB kernel. It will install but the ROM wont run due to lack of compatibility.
Abyss is used by many as a Safe kernel, a base to flash a new ROM from . Alternatively, it can be used to "downgrade" to Gingerbread ROMs.
If you are intent on trying a JB ROM, I would suggest a doing a full wipe (use the numerous guides on XDA) and a kernel clean (jBroid Script Cleaner for example). Now, research Chasmodo's excellent Kernel Repository and choose a kernel. Hydracore 4.3 Standard is a good "benchmark" however you could try the Official CM10 kernel from Entropy. Reboot to Recovery and flash your JB ROM of choice.
You will now have "Full Wiped" (including Script Clean), installed a Safe (Compatible) Kernel and flashed a compatible ROM.
For what its worth, I found GB to be an excellent ROM, particularly 2.3.6 and 2.3.7. CheckROM was one of my favorite ROMs on the S2 and they didnt even feel the need (till recently) to make an ICS version.
I hope this helps. Please hit THANKS if it did.
Alba Donzo said:
Hi there, sorry to hear of your challenges.
One thing to remember before flashing is the nature of safe / unsafe kernels. Equally as important is compatible / non compatible kernels. It's not clear from your post but did you flash Abyss on an ICS ROM? If so, Abyss is a GB kernel. It will install but the ROM wont run due to lack of compatibility.
Abyss is used by many as a Safe kernel, a base to flash a new ROM from . Alternatively, it can be used to "downgrade" to Gingerbread ROMs.
If you are intent on trying a JB ROM, I would suggest a doing a full wipe (use the numerous guides on XDA) and a kernel clean (jBroid Script Cleaner for example). Now, research Chasmodo's excellent Kernel Repository and choose a kernel. Hydracore 4.3 Standard is a good "benchmark" however you could try the Official CM10 kernel from Entropy. Reboot to Recovery and flash your JB ROM of choice.
You will now have "Full Wiped" (including Script Clean), installed a Safe (Compatible) Kernel and flashed a compatible ROM.
For what its worth, I found GB to be an excellent ROM, particularly 2.3.6 and 2.3.7. CheckROM was one of my favorite ROMs on the S2 and they didnt even feel the need (till recently) to make an ICS version.
I hope this helps. Please hit THANKS if it did.
Click to expand...
Click to collapse
Yes, I forgot to mention that when I rooted it I was running official 4.0.3 which I got OTA. After I rooted I tried the Abyss kernel. I had read that if you try and install CM10 straight from ICS you can brick, and that you had to downgrade to GB to do this. There must have been a misunderstanding on my part as I though that installing Abyss would downgrade me to GB.
What I don't understand is that I have now installed a GB rom, yet the Abyss gb kernel still does not work.
The two members that posted mentioned that I should root, though I did mention in the OP that it is already rooted... Am I missing something?
Anyway, I want to avoid having to download any more big files. I already have the latest "nightly" build of CM10 in my SD card. Is there any GB kernel that I can install from where I am now that would make it safe to install the CM10 zip?
S-pen said:
Yes, I forgot to mention that when I rooted it I was running official 4.0.3 which I got OTA. After I rooted I tried the Abyss kernel. I had read that if you try and install CM10 straight from ICS you can brick, and that you had to downgrade to GB to do this. There must have been a misunderstanding on my part as I though that installing Abyss would downgrade me to GB.
What I don't understand is that I have now installed a GB rom, yet the Abyss gb kernel still does not work.
The two members that posted mentioned that I should root, though I did mention in the OP that it is already rooted... Am I missing something?
Anyway, I want to avoid having to download any more big files. I already have the latest "nightly" build of CM10 in my SD card. Is there any GB kernel that I can install from where I am now that would make it safe to install the CM10 zip?
Click to expand...
Click to collapse
If I were on a GB ROM and wanted to run CM10 I would Full Wipe (including Cache and Dalvik) then do the following -
Flash Official CM10 kernel.
Reboot to Recovery (do not go straight to ROM flash)
Once back in Recovery, flash the CM10 ROM.
Reboot device.
Alba Donzo said:
If I were on a GB ROM and wanted to run CM10 I would Full Wipe (including Cache and Dalvik) then do the following -
Flash Official CM10 kernel.
Reboot to Recovery (do not go straight to ROM flash)
Once back in Recovery, flash the CM10 ROM.
Reboot device.
Click to expand...
Click to collapse
So the official CM10 kernel is a gb kernel? Because remember that is what I'm currently on.
And just to make sure I got you... wipe everything, install kernel (I don't understand what you mean by "go straight to rom flash"), but then not "reboot system", instead "reboot to recovery", then install CM10 rom?
Also, when you say a "full wipe" do you mean that it will erase everything like a factory reset and delete all my apps and everything else? And is there anyway to install CM10 without doing this or is that the only way?
Cm10 kernel is a jelly bean kernel, so gb rom will not run under it.
Full wipe does mean erasing everything. Coming from gb, there is no other way to install, you need a full wipe, remember, you're updating two full revisions of the os, so it's not surprising a full wipe is needed. If you're worried about your apps, root gb before upgrading and use titanium backup to backup you're apps and then restore them when on cm10.
Sent from my GT-N7000 using xda premium
Alba Donzo said:
If I were on a GB ROM and wanted to run CM10 I would Full Wipe (including Cache and Dalvik) then do the following -
Flash Official CM10 kernel.
Reboot to Recovery (do not go straight to ROM flash)
Once back in Recovery, flash the CM10 ROM.
Reboot device.
Click to expand...
Click to collapse
If you are on rooted GB Rom and want to flash a custom JB or ICS one, this is what you do:
1. drop into recovery
2. do a full wife™ (factory reset, wipe cache and dalvik)
3. flash your JB/ICS Rom
4. reboob
Nothing else is needed, no intermediate steps like flashing another kernel in between, and especially no running Jbroid or Sybr kernel cleaning script.
chasmodo said:
If you are on rooted GB Rom and want to flash a custom JB or ICS one, this is what you do:
1. drop into recovery
2. do a full wife™ (factory reset, wipe cache and dalvik)
3. flash your JB/ICS Rom
4. reboob
Click to expand...
Click to collapse
How original was that....
Sent from my GT-N7000 using xda premium
SpyderTracks said:
If you're worried about your apps, root gb before upgrading and use titanium backup to backup you're apps and then restore them when on cm10.
Click to expand...
Click to collapse
Once again, my phone is already rooted... I have mentioned this several times.
chasmodo said:
If you are on rooted GB Rom and want to flash a custom JB or ICS one, this is what you do:
1. drop into recovery
2. do a full wife™ (factory reset, wipe cache and dalvik)
3. flash your JB/ICS Rom
4. reboob
Nothing else is needed, no intermediate steps like flashing another kernel in between, and especially no running Jbroid or Sybr kernel cleaning script.
Click to expand...
Click to collapse
You telling me that I can safely go straight to JB from my current GB rom and kernel?
I already have a "nightly" JB rom on my SD card, so just to be clear, all I do is go into CWM recovery, do a "full" wipe (how do I do that by the way?) and install the JB rom from zip?
Yes, you can go ahead. Just follow the instructions kindly provided by chasmodo.
But please, do not forget to flash GApps after you flashed the JB "nightly ROM which is on your SD Card". Otherwise you won't have Google account, play store etc yada yada.
Full wipe (aka full-wife™) means wipe data/factory reset. Nothing else.
AA1973 said:
Yes, you can go ahead. Just follow the instructions kindly provided by chasmodo.
But please, do not forget to flash GApps after you flashed the JB "nightly ROM which is on your SD Card". Otherwise you won't have Google account, play store etc yada yada.
Full wipe (aka full-wife™) means wipe data/factory reset. Nothing else.
Click to expand...
Click to collapse
Great! I am downloading the GApps for JB now. How do I install them? I understand that this is also done through CWM recovery, but how do I instal them? do I install the JB rom and reboot to recovery and then just install GApps from zip before rebooting system?
Also, does the full wipe have to be done in CWM recovery, or can I just do the normal wipe on the phone menu before entering recovery?
You flash the ROM by pointing the recovery to the "ROM.zip", the same is valid for "GApps.zip".
So you do the following, no reboot in recovery in between those 2 steps!
Install zip (from where it is located, internal/external SD )
*ROM.zip
*Gapps.zip
*reboot system
Wipe data/factory reset is done (most of the times) in recovery. Just get used to it. Saves you some bad habits on doing it on stock ICS ...
AA1973 said:
You flash the ROM by pointing the recovery to the "ROM.zip", the same is valid for "GApps.zip".
So you do the following, no reboot in recovery in between those 2 steps!
Install zip (from where it is located, internal/external SD )
*ROM.zip
*Gapps.zip
*reboot system
Wipe data/factory reset is done (most of the times) in recovery. Just get used to it. Saves you some bad habits on doing it on stock ICS ...
Click to expand...
Click to collapse
OK install ROM and then install GApps straight away, got it.
Just about the wipe, is it a simple one button wipe that wipes everything, or are there several things that I have to wipe independently? This is the part I'm not too sure about.
Just go into recovery and have a look. I mean, a really close look! Your topic was "need help to install a kernel" not "I don't know how to use recovery and please can someone come over to my place in order to explain me CWM recovery".
Sorry. Everything has been explained. Can't (or rather dont want to) help you further than what has been already mentioned. Period.
AA1973 said:
Just go into recovery and have a look. I mean, a really close look! Your topic was "need help to install a kernel" not "I don't know how to use recovery and please can someone come over to my place in order to explain me CWM recovery".
Sorry. Everything has been explained. Can't (or rather dont want to) help you further than what has been already mentioned. Period.
Click to expand...
Click to collapse
That's fine. I'll go into recovery and have a look. Thanks for the help that you did give anyway.
It worked! I have been messing around with my new Note on Jellybean and looking through all the settings. It doesn't have project butter (or at least the project wasn't very successful), but still miles ahead of Touchwiz.
Just want to extend a big thanks to everyone that has helped me out. Much appreciated.

Need Help!! Did I do the wrong thing?!

hi, currently i have installed cm9.1 stable for note,
using the philz kernel at 1st then wipe and flash cm,
then i realize is not what i want:
1.no video call?
2.can't do apps re-arrangement like samsung ui did
then i want to roll back to the original rom (the samsung ui),
i follow back the steps and install the philz kernel, then i reboot it,
but when i go in to android it say phone process can't open blah blah blah, then i was terrified,
OH MY GOD!!!!! AM I BRICKED!!????!?!?!?!?!:crying:
and i can't go into the phone ui (cm9),
then i quickly take out the battery, using to old vol up+home+power to go in to the recovery by force,
luckyly i saw the CWMR from philz,
and so i'm restoring the old system now,
i'm not sure in future will there be any problem,
but the main thing is, did i do some thing wrong ?
when you went from CM9 back to Samsung TW, did you do a factory reset ? If not, That is probably what caused your issues.
they are both completely different ROMs so more than likely settings from CM transfered over to TW and resulting in tons of FC's
Its normal so dont panic, Wipes are essential when changing ROMs (unless updating the same ROM) just be sure to be on a safe kernel
azzledazzle said:
when you went from CM9 back to Samsung TW, did you do a factory reset ? If not, That is probably what caused your issues.
they are both completely different ROMs so more than likely settings from CM transfered over to TW and resulting in tons of FC's
Its normal so dont panic, Wipes are essential when changing ROMs (unless updating the same ROM) just be sure to be on a safe kernel
Click to expand...
Click to collapse
im back on TW now, phew scare me out of the dead,
anyway, do u mean that every time on changing kernel or rom i need to do a full wipe, even in restoration?
by the way, backing up a nand, does backup the kernel too, right?
side,
im going to try out [JB:CM10:HYBRID][GT-N7000] PARANOIDANDROID [Utacka] [19 NOV] ,
hope it got the things that i want,
but im not sure bout here:
Make sure to run CM9/10 or an AOSP-based ROM : FLASHING FROM STOCK ICS OR ROMS BASED ON STOCK ICS WILL RESULT IN A BRICK! - You're warned!<<<<<<<<<is this mean the kernel? if i already install philz kernel + in stock ics rooted, can i direct start the wipe section and so on without installing cm9 again?
• [GUIDE] Which Kernels are Safe/Unsafe to Wipe and Flash from <- READ THIS IF YOU ARE CONFUSED
•CWM: YOU NEED TO FULLWIPE IF YOU ARE COMING FROM ANOTHER ROM
•CWM: Install Zip: Rom: http://goo.im/devs/Utacka/n7000
•CWM: Install Zip: Gapps: http://goo.im/gapps/ (latest gapps-jb and even when updating to new PA build)
•Reboot and edit your Apps Dpi & Layout under Settings/Paranoid Settings - DO NOT RESTORE YOUR OLD PROPERTIES FOR NOW
•If you want to explore the various phone modes, tap "Configuration," chose an option, wait for it to finish, then do a manual reboot
•Video tutorial: http://www.youtube.com/watch?v=72Ow-YQeex4
thank you
NooBDroidPlayer said:
im back on TW now, phew scare me out of the dead,
anyway, do u mean that every time on changing kernel or rom i need to do a full wipe, even in restoration?
by the way, backing up a nand, does backup the kernel too, right?
side,
im going to try out [JB:CM10:HYBRID][GT-N7000] PARANOIDANDROID [Utacka] [19 NOV] ,
hope it got the things that i want,
but im not sure bout here:
Make sure to run CM9/10 or an AOSP-based ROM : FLASHING FROM STOCK ICS OR ROMS BASED ON STOCK ICS WILL RESULT IN A BRICK! - You're warned!<<<<<<<<<is this mean the kernel? if i already install philz kernel + in stock ics rooted, can i direct start the wipe section and so on without installing cm9 again?
• [GUIDE] Which Kernels are Safe/Unsafe to Wipe and Flash from <- READ THIS IF YOU ARE CONFUSED
•CWM: YOU NEED TO FULLWIPE IF YOU ARE COMING FROM ANOTHER ROM
•CWM: Install Zip: Rom: http://goo.im/devs/Utacka/n7000
•CWM: Install Zip: Gapps: http://goo.im/gapps/ (latest gapps-jb and even when updating to new PA build)
•Reboot and edit your Apps Dpi & Layout under Settings/Paranoid Settings - DO NOT RESTORE YOUR OLD PROPERTIES FOR NOW
•If you want to explore the various phone modes, tap "Configuration," chose an option, wait for it to finish, then do a manual reboot
•Video tutorial: http://www.youtube.com/watch?v=72Ow-YQeex4
thank you
Click to expand...
Click to collapse
The way I see it , you need a CM 9/10 or AOSP Rom before you should flash paranoid ..
You dont need to wipe everytime, For example, Upgrading Paranoid Android version 1 to Paranoid Android version 2 will NOT necessarily require a full wipe.
But changing from Paranoid Android to Rocket ROM (for example) WILL require a full wipe
You can also full wipe then restore a nandroid, if you wish too. The main thing is to keep regular backups incase something unplanned happens !
azzledazzle said:
You dont need to wipe everytime, For example, Upgrading Paranoid Android version 1 to Paranoid Android version 2 will NOT necessarily require a full wipe.
But changing from Paranoid Android to Rocket ROM (for example) WILL require a full wipe
You can also full wipe then restore a nandroid, if you wish too. The main thing is to keep regular backups incase something unplanned happens !
Click to expand...
Click to collapse
oh i see, im abit understand now,
so, the steps goes on like this,
nand(4.0.4) >> wipe >> cm9 or aosp >> wipe >> pA(4.1.2) >> done
if i want to roll back from pA is
pA(4.1.2) >> wipe >> restore(4.0.4)
is it?

[Q] my cwm can't flash .zip file

I got used exhibit from my brother. my exhibit was on gingerbread. when i went to recovery mode , it was already cwm 6.0.4.5 . i downloaded cm 11 and gapps and copied it to my phone. i wiped dalvik cache , system , data , and cache . but when I try to install the .zip package it always suddenly aborted without notification. any suggestions ?
rahadyanharits said:
I got used exhibit from my brother. my exhibit was on gingerbread. when i went to recovery mode , it was already cwm 6.0.4.5 . i downloaded cm 11 and gapps and copied it to my phone. i wiped dalvik cache , system , data , and cache . but when I try to install the .zip package it always suddenly aborted without notification. any suggestions ?
Click to expand...
Click to collapse
Hey there! Unfortunately Cyanogenmod 11 has had a bad reputation on the Galaxy Exhibit 4G. You're not the only one who is experiencing problems getting the ROM to run. If you can't install the ROM via recovery I can only imagine the problems you'll encounter when you do install it; constant FC, random reboots, etc. My suggestion is to try an older version of Android if you're looking for stability. My personal suggestion would be CM 10 with 2.6 kernel. I love that ROM. Anyways, here are a few things you can try.
Install different recovery versions. You can start with these ones and see which one allows you to install the ROM successfully.
CWM 6.0.4.4 http://blownco.com/index.php/doc_download/13661-cwm-6-0-4-4-exhibit
CWM 6.0.4.5 http://d-h.st/aTo
CWM 6.0.4.6 http://d-h.st/owg
CWM 6.0.4.7 http://d-h.st/tSN
TWRP 2.6.3.0 http://d-h.st/kjr
If you're able to successfully install the ROM proceed to the reboot and if you don't get any FC, reboots or whatnot you're one of the lucky ones. If you do run into issues, then wipe everything, install the rom, gapps and then this kernel. http://d-h.st/kha
That's pretty much all you can do now. Development here has waned, so I'm not sure the issues will ever get fixed. Good luck!
You should try out cwm 6.0.4.7. just got released. I got it with no probs. running the kernel jorge007 has posted. Build number 1/23 with stable 1.4ghz oc

Camera stops working often after cwm 6.0.4.8 on aosp roms

I'm not sure if I'm the only one experiencing this but every time I try to flash a custom kernel on CM11 and PA4 with cwm 6...4.8 camera app freezes like usual but then freezes again after 5 secs which is not usual.
Not only does this happen on custom kernals but stock CM11 and PA as well e.g. when I was in the science museum using PA taking pics everything was working well, then phone froze so I did a reboot in fact 5 reboots and camera displayed same symptoms as explained above. Also on CM11 stock kernal I did a regular reboot to apply full theme and bam camera stopped working all AF a sudden.
To fix I had to reflash ROM. I even did a full wipe( including format system) and still had same symptoms.
Pimped kernal just breaks camera straight from reboot no matter how many times I reboot it doesn't fix the problem. Only fix seems to reflash ROM (no need to wipe). Restoring stock/original ROM kernel fixes it but WiFi does not work.
Any way to get custom kernels to work without breaking camera?
..just an advice, do not use CWM, is recommended to flash with TWRP because is more efficient. I had many problems with CWM.
eclyptos said:
..just an advice, do not use CWM, is recommended to flash with TWRP because is more efficient. I had many problems with CWM.
Click to expand...
Click to collapse
Thanks for the reply. I have no option but to use cwm cause all my back ups where done on cwm.
As for the problem I found the solution in this thread:
http://forum.xda-developers.com/showthread.php?t=2505973
yup owns Z1 and stuff.

Categories

Resources