[HELP] JB 4.1.1_Unofficial CM10 Kernel flash - Galaxy S I9000 Q&A, Help & Troubleshooting

Ok, I'm on a I9000, I flashed the latest (V4) rom unofficial CM10; nothing really magical, it works. The problem is that when I flash the latest Semaphore 2a, reboot the phone (I always do before a fix permissions), and it hangs on the logo of the kernel and I have to re-flash the rom.
My complete procedure:
- 3 full wipe (factory reset, data, datadata, and Dalvik Cache)
- Flash ROM,
- Apps
- Fix
- Reboot,
- Back in CWM
- Flash Kernel + Fix
- Reboot
= Hang!
Any ideas?
Thanks! :fingers-crossed:

Others have had this to. I don't think that semaphore is made for jb yet. I know that devil kernel supports jb and works really good, settings stick and its super stable. Your choice though
Sent from my GT-I9000 using xda app-developers app

Ok, I'll wait for a stable release! Thank you!

Related

[Q] TeamHackSung ROM build 15 match with custom Kernel

Hi Everyone,
actually i got a question here, is the Icy Glitch V14 is usable under TeamHackSung ICS ROM Build 15?
currently i using the latest Devil Kernel, but just want to try to play with other kernel as well.
and also, i not sure my step is correct or wrong when i flash from stock kernel to devil kernel.
The step i using is :
1) reboot in recovery mode
2) wipe partition cache
3) wipe kelvik cache
4) install zip from SD card (install devil kerner)
5) reboot phone once install successfully.
its working fine but just want to know more about this
Yes, that is correct (apart from it's actually cache partition and dalvik cache). Personally, I find Devil kernel 14.2 led the best, reflashed back down after using 15. Much more snappy and responsive.
argh...now i found out that my WIFI will ON and OFF for non stop after i turn on WIFI by using devil kernel build 15.
i flashed to glitch V14 now and seem work fine. but i feel like my phone is going become lagger and lagger after i keep on changing and flash the kernel...
I've flashed the latest devil kernel (Devil_15.1_LED2.zip) and after the Modded framework-res.apk for build 15. Apparently it seems that all works, but looking to settings in telephone info I can't read devil kernel nowhere, as you can see from the attached image. Something was wrong in the flash operation?
Yes devil seems the best for me, i got only bootlops with glitch when i tried..
devils works for me, but pawit works well as well

Most effective update?

I am about to update RemICS 1.2 to RemICS 1.3. This is actually my first update within the same rom to a newer version. Lately, I have been switching around between multiple rom's but the RemICS is definitely my favorite atm.
Ok, I know I'll have to back up (Titanium)
But then:
- Full wipe and new install
or
- Just flash 1.3 over 1.2 without wiping anything?
Rom is running fine at the moment, no issues at all.
Ok, should have searched a bit harder before posting....
http://androidforums.com/galaxy-s2-...l-wipe-whats-big-deal-steps-take-15-mins.html
A full wipe is always the best option, to get a bug free and super fast rom
Just flash over, its very unlikely you'll get a bug but to be sure wipe cache and dalvik, if you get any bugs just wipe and reflash
Sent from my GT-I9000 running remICS-UX using XDA premium
Flash kernel cleaning script from lippo
Wipe cache
Wipe dalvik
Flash the rom
Reboot and enjoy....
-----------------
I9000 powered by RemICS-UX

abyss kernel question

i wanted to do data factory reset
im on paranoid android v0.5 having some probs with it
so i decided to hav a fresh install of th same rom with all 3 wipes
so vich version out of the 4 abyss kernel shd i use?
1)AbyssNote kernel 4.2 Final CW Touch Custom Logo
2)AbyssNote kernel 4.2 Final CW Touch Original Logo:
3)AbyssNote kernel 4.2 Final RedPill Touch Custom Logo:
4)AbyssNote kernel 4.2 Final RedPill Touch Original Logo:
People tend to use RedPill so you see the difference when you've rebooted into recovery therefore you know you're on a safe kernel....
I tended to use: AbyssNotekernel42CWTouchOriginalLogo
Although now for uber safety (And paranoia) I tend to downgrade to GB and do all my wipes and FR's in there, Then approach things afresh...
No need to use abyss. Since cm9 is a safe kernel.
Sent from my GT - N7000 using XDA Premium
1) install paranoid v0.5
2) install gapps
3) wipe data factory reset
4) wipe cache partion
3) wipe dalvik cache
is this th way i can go? js asking to b sure
I too use: AbyssNotekernel42CWTouchOriginalLogo, have not run into any issues.
I have run with issues . In the abyss recovery ext SD card doesn't show up. I was struck on the recovery luckily I had nandroid backup so I restored it . I don't know what would have happened if there was no ROM to flash and I finished all three wipes . It was awkward. Luckily I came out of the situation. But cm9 and speed mod is safe to make three wipes. But are they safe to flash cm10 ?
Sent from my GT-N7000 using xda app-developers app
I hear that SpeedMod is a safe kernel to wipe on - Although as mentioned earlier I have not tried, despite running SpeedMod
chillteddy said:
1) install paranoid v0.5
2) install gapps
3) wipe data factory reset
4) wipe cache partion
3) wipe dalvik cache
is this th way i can go? js asking to b sure
Click to expand...
Click to collapse
Reboot into recovery
Full wipe(be sure you are on cm9 before you wipe)
Flash rom paranoid android
Flash gapps
Now again full wipe
Reboot system
Done.
Sent from my GT-N7000 using Xparent ICS Tapatalk 2
Vishal_Pratap singh said:
I have run with issues . In the abyss recovery ext SD card doesn't show up. I was struck on the recovery luckily I had nandroid backup so I restored it . I don't know what would have happened if there was no ROM to flash and I finished all three wipes . It was awkward. Luckily I came out of the situation. But cm9 and speed mod is safe to make three wipes. But are they safe to flash cm10 ?
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Yes CM9 is safe to install CM10 but not Speed Mod
Question
Does have a difference between come back to 2.3.5 and then install rom or just make the wipes (data/cache/dalvik) in a safe kernel and install rom too?
Tks!

RR V10 won't boot after crash ???

Hi there, as stated ICS RR V10 is installed with notecore v14 std kernel, the system crashed after trying to connect to the bluetooth headset: the screen switched to full brightness and because nothing was responding i pulled the battery. Since then no boot was sucessful (only until the android logo), cwm (5.5.0.4) was kind of slow when i booted into recovery, cache and dalvik cache got wiped - the flash of RR v10 itself was successful again but still the system doesn't boot (same behaviour, back get's prettry warm).
Before i do something stupid, i ask you guys what to do next:
-flash abyss 4.2 and try flashing again? ( + full wipe ?)
-flash notecore v14 and flash again?
Thanks for your input.
tempobaer said:
Hi there, as stated ICS RR V10 is installed with notecore v14 std kernel, the system crashed after trying to connect to the bluetooth headset: the screen switched to full brightness and because nothing was responding i pulled the battery. Since then no boot was sucessful (only until the android logo), cwm (5.5.0.4) was kind of slow when i booted into recovery, cache and dalvik cache got wiped - the flash of RR v10 itself was successful again but still the system doesn't boot (same behaviour, back get's prettry warm).
Before i do something stupid, i ask you guys what to do next:
-flash abyss 4.2 and try flashing again? ( + full wipe ?)
-flash notecore v14 and flash again?
Thanks for your input.
Click to expand...
Click to collapse
No need to flash Abyss kernel, you are already on safe kernel, try flashing some different kernel, Speedmod or different version of STD Notecore.
If that too doesn't help flash rom again.
its issue with your kernel, Notecore version 14. fix is coming, in meanwhile try speedmod indeed.
Sent from my GT-N7000 using Tapatalk 2
thanks for the input: tried notecore 13 std and speedcore k3-13 separatly, installed the rom and kernel again, situation didn't change, still hanging at the kernels boot animation (android/samsung logo + no sound ?)
out of despair i just redownload rr v10 and give the new file a shot.
tempobaer said:
thanks for the input: tried notecore 13 std and speedcore k3-13 separatly, installed the rom and kernel again, situation didn't change, still hanging at the kernels boot animation (android/samsung logo + no sound ?)
out of despair i just redownload rr v10 and give the new file a shot.
Click to expand...
Click to collapse
Now, do not try anything, just download pre-rooted GB rom from dr.ketan's thread and flash using pc odin.
jeetu1981 said:
Now, do not try anything, just download pre-rooted GB rom from dr.ketan's thread and flash using pc odin.
Click to expand...
Click to collapse
is this the right thread : http://forum.xda-developers.com/showthread.php?t=1424997 - cause these aren't prerooted and i didn't anotherone
Edit: (5 minute delay...)
found the link: NEW 20 Aug2012 - subchapter 3. ...
and in your signature
tempobaer said:
is this the right thread : http://forum.xda-developers.com/showthread.php?t=1424997 - cause these aren't prerooted and i didn't anotherone
Edit: (5 minute delay...)
found the link: NEW 20 Aug2012 - subchapter 3. ...
and in your signature
Click to expand...
Click to collapse
Updated in my signature, download it.
ok then I dont know, how a system crash is preventing bootup. Others had issue on v14. Maybe instal was not vlean to start with. Maybe emmc is corrupt, many maybes.
first, on safe kernel wipe cache and dalvik cache. Also fix permissions, Reboot. Fixed it? No continue:
perhaps starting new, cleanly could solve it. Like above you can start from gb, Just to check you dont get stuck at flashing it.
or you can start from save kernel recovery, On notecore or on speedmod. The install of rocketrom went good first time right? if not, then redownload rocketrom as instal file could be corrupt. Check md5s if it doesnt install.
You can format system from mounts, then data from mounts, then wipe cache and dalvik. Then install rocketrom, then instal kernel of choice, wipe cache and dalvik for fun again and reboot. All of course from safe kernel kernel recovery.
If this didnt fix it, start new from pc odin and flashing a gb rom. For this to succesfully boot, it maybe needed to format system/data before flashing from pc.
Sent from my GT-N7000 using Tapatalk 2
solved (partly - data lost)
problem got solved by installing the pre-rooted gb rom (dr. ketan) via odin 1.85, afterwards i installed abyss 4.2 (probably not necessary), rebooted into recovery (advanced), wiped cache data and dalvik and installed rr v10 again. Of course i lost all data, but at least the phone is up and running again.
thanks to dr. ketan for his effort and jeetu1981 for personal help

[Q] Question about upgrading a Galaxy Note GT-N7000 from CM9 to CM10

I just saw it's a while that CM10 for the GT-7000 (intl) is around. Currently I have CM9 on my Gnote. If I want to update to CM10, is there anything I should be careful with? Or can I just do it like for any other CM9 over CM9 update, i.e.
- reboot into recovery
- full rom backup
- flash new zip file
- select rom update zip file
- flash
- reboot
Thanks!
- Adriano
Flash a safe kernel like hydracore and then you can directly flash cm10 through cwm
You don't need to flash an alternate kernel, you're fine to flash over cm9 kernel straight off. I'd recommend doing a clean install and do full wipes after flashing gapps as dirty installs can cause fc's as well as other lingering problems.
So:
Reboot into recovery, flash paranoid 2.16.
Flash gapps.
Wipe dalvik, cache and data.
Reboot.
Sent from my GT-N7000 using xda app-developers app
SpyderTracks said:
You don't need to flash an alternate kernel, you're fine to flash over cm9 kernel straight off. I'd recommend doing a clean install and do full wipes after flashing gapps as dirty installs can cause fc's as well as other lingering problems.
So:
Reboot into recovery, flash paranoid 2.16.
Flash gapps.
Wipe dalvik, cache and data.
Reboot.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Thank you both for your suggestions
Flashed CM10, gapps, didn't do a full wipe yet, so far so good though.
- Adriano

Categories

Resources