Does anyone know if it is possible to use this rom
http://forum.xda-developers.com/showthread.php?t=817703
With the 2.1 reorient kernel?
Just put the zImage file inside the .zip.
V6 should be OK.
Word of advice, the new JPA on the i9000 has a new modem (JPP).
I will not port v7 over until the modem is confirmed to be working on the captivate. I don't have all the resources available to me to test the modem.
killer23d said:
V6 should be OK.
Word of advice, the new JPA on the i9000 has a new modem (JPP).
I will not port v7 over until the modem is confirmed to be working on the captivate. I don't have all the resources available to me to test the modem.
Click to expand...
Click to collapse
its working. im using it now.
hijack thread for my own "if possible"...
there is alot of good developments going on over in the i9000 forums and while roms are one thing alot of these rely on a completly different kernel to be flashed. im pretty sure we cant just flash the reorinent kernel ontop of these and expect it to work and i noticed the super optimized kernel in the i9000 is JUST the zimage so thats just not going to work. is there some crazy ass way to integrate our reorient kernel into some of these optimizations? seeing all this good stuff pass me by is driving my ocfd nuts
bamonkey said:
hijack thread for my own "if possible"...
there is alot of good developments going on over in the i9000 forums and while roms are one thing alot of these rely on a completly different kernel to be flashed. im pretty sure we cant just flash the reorinent kernel ontop of these and expect it to work and i noticed the super optimized kernel in the i9000 is JUST the zimage so thats just not going to work. is there some crazy ass way to integrate our reorient kernel into some of these optimizations? seeing all this good stuff pass me by is driving my ocfd nuts
Click to expand...
Click to collapse
ive seen a lot of those optimizations too and your right you cant just flash the reorient kernel over an i9000 rom and expect things to work exactly like intended for that rom because that roms kernel will be completely wiped when you flash the reorient kernel. the reorient kernel does generally fix all the major problems youd have if you didnt flash it, but then you lose the things that that kernel was built to do. i think the biggest reason a lot of these havent been implemented yet is because there is no source code for our 2.2 kernel yet.
vinunleaded182 said:
Does anyone know if it is possible to use this rom
http://forum.xda-developers.com/showthread.php?t=817703
With the 2.1 reorient kernel?
Click to expand...
Click to collapse
I am surprised this still gets asked??
The re-orient kernal from xcal is exactly there for that reason. It makes it possible so that we ATT captivate users can take advantage of the European i9000 roms from the SGS i9000 forums.
These are the requirements for the i9000 cooked roms to work (this is not the only way to do it but it is the easiest)
1) the i9000 rom needs to be in ZIP format so it can be applied via clockwork recovery (most of them are: Doc/Kalpik, Darky, Tamatuya)
2) your current rom/recovery needs to support 2e recovery and have the latest clockwork recovery installed
3) the re-orient kernal needs to be applied right after the i9000 rom is applied, meaning before you reboot the phone. Otherwise you loose the power button select key in recovery.
The latest version (v7) from Doc has caused FC's on the keyboard, so it is unusable for now. The modem as pointed out above may also not be compatible, so I would stay away from v7 and stick with v6 for now.
anosis said:
I am surprised this still gets asked??
The re-orient kernal from xcal is exactly there for that reason. It makes it possible so that we ATT captivate users can take advantage of the European i9000 roms from the SGS i9000 forums.
These are the requirements for the i9000 cooked roms to work (this is not the only way to do it but it is the easiest)
1) the i9000 rom needs to be in ZIP format so it can be applied via clockwork recovery (most of them are: Doc/Kalpik, Darky, Tamatuya)
2) your current rom/recovery needs to support 2e recovery and have the latest clockwork recovery installed
3) the re-orient kernal needs to be applied right after the i9000 rom is applied, meaning before you reboot the phone. Otherwise you loose the power button select key in recovery.
The latest version (v7) from Doc has caused FC's on the keyboard, so it is unusable for now. The modem as pointed out above may also not be compatible, so I would stay away from v7 and stick with v6 for now.
Click to expand...
Click to collapse
I'm sucessfully using JPP with V7. Using kernal 2.6.32.9 [email protected] #38. Using a lagfix called No RFS advanced ext 4. Using Vlingo keyboard from Samsung. I've been able to correct force closed apps by clearing their data caches. The only real problem I have encountered is the same one I have had with all the I9000 rom's I have tried to date-no audio on videos. Able to install zip's, lagfix and other add ons through ClockworkMod recovery.
So I looked all around and could not find this specific question. I upgraded the wifes cappy to the AT&T Gingerbread KK4 release via Kies the other day. I found a thread to assist in rooting which went fine. But for the life of me i cannot find how to get cwm on this thing without changing the kernel. I used a file based cwm on the sdcard when it was froyo that i would flash for use when needed and it would revert back to stock 3e after rebooting, that exist for KK4? She's insisting I keep hers stock as she's worried about it bricking so I have to follow orders lol!
U can't do the update.zip to get cwm like in eclair days because of the 3e recovery. If u want cwm on kk4 u gotta at least flash a kk4 kernel with cwm baked in. I have been using Corn Kernel version 6.03 and it is excellent.
Why do u want cwm if she wants to keep it Stock ? To flash different modems... U can't flash mods etc. because it is stock and odexed...
Just curious.
Sent by XDA Premium App
So I can flash clock mods and such from the kitchen, unless of course KK4 doesn't allow it. It did allow on stock 2.2 and worked just fine without issue. My thing with flashing a different kernel is I don't want anything that's overclocked or such on her phone.
What you need to do is get a kernel with CWM already baked into it.
So start with this. Flash the Corn 7.03 kernel. I used it for the entire day today with a great experience. It was just released today as well. This kernel has CWM already in it and works great with the stock rom.
I also suggest flashing this rom: http://forum.xda-developers.com/showthread.php?t=1358180 This is Trusselo's: 【stock】【kk4】 rooted deodexed debloated rom. Its basically a stock version of the rom with root already in it. It is missing a few ringtones but who really cares about that. Its also stripped out of the stuff that slows your phone down and paired with the kernel it makes for a much better experience on the captivate.
So if you want stock this is about as stock as it gets with a mix of high performance.
Dear All,
I have Note 2.3.6 stock rom rooted
I started with 2.3.6 KK2 stock rom with root without any lag on contacts screen, then I updated my phone by flashing LA1 stock rom also with no lag problem or battery, but when I flashed CF-Root-SGN_XX_OXA_LA1-v5.0-CWM5 for root with CWM, I noticed the battery consumption is higher (but still ok, or is there a better one?) and the most annoying thing is the contacts screen lag: when I push the contacts icon it lags for exactly 8 seconds to show the contacts
my question is this lag came from the flashed file or not?
Can I flash the original kernel from KK2 stock rom? there were no lag and the battery consumption was perfect
is there any solution 4 that? if u have one then please explain to me why (this solution) and how to do it
I'd try flashing Franco's kernel if I were you. It's fast, stable and very easy on the battery. It is flashed from CWM Recovery, a piece of cake.
I'm using it as a combo on several Roms, and all of them spring contacts almost instantaneously.
Of course, you can always re-flash CF-Root if you don't like it.
thank you chasmodo for your reply,
Does your Franco Kernel will effect the root and the CWM or not?
my question is this lag came from the flashed file or not?
Can I flash the original kernel from KK2 stock rom? there were no lag and the battery consumption was perfect
thermax04 said:
thank you chasmodo for your reply,
Does your Franco Kernel will effect the root and the CWM or not?
my question is this lag came from the flashed file or not?
Can I flash the original kernel from KK2 stock rom? there were no lag and the battery consumption was perfect
Click to expand...
Click to collapse
Franco kernel will not affect your root and CWM in any way. However, flashing stock kernel or Rom will result in losing your root for sure.
chasmodo said:
Franco kernel will not affect your root and CWM in any way. However, flashing stock kernel or Rom will result in losing your root for sure.
Click to expand...
Click to collapse
Iam reading now about the franco kernel (page 5 now) and found a lot of users have a problem with heat and bootloop (u r 1 of them) is this may be in first issues? which version u r using now and how it is regarding over heat since iam using it in a warm country
One of the early version had heat issues (4 I believe), but Franco is now at No 6 (I'm using this one ATM), which is just fine, no problems, great battery life.
chasmodo said:
One of the early version had heat issues (4 I believe), but Franco is now at No 6 (I'm using this one ATM), which is just fine, no problems, great battery life.
Click to expand...
Click to collapse
Is there special settings for this kernel, I read about governer which is very new to me, all what I used to do before is just flash the kernel and thats it.
Does flashing this kernel via the CWM recovery will increase the flashing count (because of warranty)?
If I made a backup (CWM) before flashing this Kernel and did not like, If I restore the backup would I get the old Kernel or I must reflash it?
thermax04 said:
Is there special settings for this kernel, I read about governer which is very new to me, all what I used to do before is just flash the kernel and thats it.
Does flashing this kernel via the CWM recovery will increase the flashing count (because of warranty)?
Click to expand...
Click to collapse
No special settings for the governor at all, don't worry about that, just flash it and you're OK. And it won't increase you binary counter.
chasmodo said:
No special settings for the governor at all, don't worry about that, just flash it and you're OK. And it won't increase you binary counter.
Click to expand...
Click to collapse
Ok , will do
Sorry to ask, should I flash it by choosing flash kernel from CWM app, or by choosing install from zip file from CWM Recovery screen?
Install from zip file, then browse to the file.
Hi, I have an international varient of the Galaxy Note GT N7000 which using Chainfire's Got Brick App v1.1 says:
eMMC Chip
Type: VYL00M
Revision: 0x19
Verdict: Danger! This eMMC chip is "Known" to have the brick bug!
I once had installed a custom Kingdroid ROM v3 and wiped it but it had resulted in a Hardbrick/Superbrick so i had to take it Samsung Service Center to get it fixed. They have repaired it and given me back the handset with the Stock ICS ROM. Here are the details:
Model Number: GT-N7000
Android Version: 4.0.3
Baseband Version: N7000XXLPT
Kernel Version: 3.0.15-N7000JPLPD-CL643396
[email protected]#3
SMP PREEMPT Thu May 31...
Build Number: IM74K.JPLPD
Now i have done some researched and found that this bug is only triggered with kernels (ICS stock & leaked) which have the eMMC_Erase function/command. GB kernels are not known to have this erase function so they are safe.. Also the two safe kernels are franco r3 and speedmod k3 (Correct me if im wrong). Can anyone please guide me on the following:
1) Should I flash Stock Gingerbread OR ICS Kernel(franco/speedmod)?
2) Should I use Recover or ODIN?
3) Plz Provide the links for the Kernels - Franco R3 & Speedmod K3 which are safe?
4) Will the above Kernels provide root access?
5) Is abyss kernel safe (because it supports GPU overclock)?
6) Can i flash an ICS kernel over a Gingerbread ROM?
For answering please answer in a similar numbered way so that it is easy to read and understand for me as well as future audience! Thanking everyone who takes time to read and answer!
I use Speedmod kernel and i confirm that it is safe (for me at least anyway) Im using CleaNote ICS ROM, So I would suggest you also use speedmod kernel,
You Flash it in Odin, It will give you CWM and Root too !
Ive attached the kernel to the post for you.
Abyss kernel is safe, But its for GB ROMs only, You are on ICS so it wont work.
I dont know if you can flash ICS kernel over GB ROM, However, Your are on ICS so you shouldnt need to worry about that.
don't really want to hijack your thread an i dont really want to make a whole new thread for a simple question.
as a noob, im just wanting to know, if i update my stock gb to stock ics via software update, are there still chances of this emmc bug/brick thats going on?
and the battery drain issues, do they only exist in custom roms or does it exist in stock roms too?
cheers.
azzledazzle said:
I use Speedmod kernel and i confirm that it is safe (for me at least anyway) Im using CleaNote ICS ROM, So I would suggest you also use speedmod kernel,
Click to expand...
Click to collapse
Thanks for the confirmation mate, one more thing to ask you: Is the speedmod kernel faster than the stock ICS kernel? Is there any flaws such as battery drain/WIFI problem with it? Also does it support GPU OC? Thanks once again for your help!
little-vince said:
don't really want to hijack your thread an i dont really want to make a whole new thread for a simple question.
as a noob, im just wanting to know, if i update my stock gb to stock ics via software update, are there still chances of this emmc bug/brick thats going on?
and the battery drain issues, do they only exist in custom roms or does it exist in stock roms too?
cheers.
Click to expand...
Click to collapse
Firstly get your Galaxy Note checked using Chainfires App (Gotbrick v1.1). If the verdict says "Danger" only then does your device have this problem. My Galaxy Note (Rev 0x19) had this problem and came with GB out of the box and i upgraded it to ICS through Samsung Kies and it worked fine. So i do not think that while updating to ICS via Kies will cause this problem. As of what i know it is triggered when a command eMMC errase is triggered when either doing a factory reset or wipe through recovery. The update as such did not brick my device, however this does not mean it cannot brick yours. I am no expert on this so be a little cautious while updating. I would suggest stick to GB until Samsung Releases a safe stock ICS ROM with a safe Kernel. Cheers!
really easy
1: (optional ) in GB do factory reset (after you have made a backup with TB)
2: put phone in Download mode.
3: use PC odin flash STOCK ICS rom
4: reboot device let it load
5: put device back into download mode
6: use PC ODIN flash Speedmod k3-3
7: reboot
8: launch CWM and tell it to reboot in cwm recovery
9: load your custom rom of your choice
i HIGHLY recommend doing ONLY THE FACTORY RESET WIPE data and cache in GB before you start anything.
ONCE you are in ICS and have successfully loaded speedmod or franco's kernel then it is safe to do a factory wipe if you want. but ONLY after one of those 2 Kernels are on your device.
EMMC BUG. is affected in all N7000 Devices only . only the devices sent to the USA have the revision the non 0x19 bug .
rp4k said:
EMMC BUG. is affected in all N7000 Devices only . only the devices sent to the USA have the revision the non 0x19 bug .
Click to expand...
Click to collapse
okay...
truth is i haven't actually bought the note yet.
just doing substantial amounts of research beforehand.
im pretty sure only the n7000 model is out in australia.
but it's all okay if i dont factory reset/wipe/anything-risky-in-general right?
little-vince said:
okay...
truth is i haven't actually bought the note yet.
just doing substantial amounts of research beforehand.
im pretty sure only the n7000 model is out in australia.
but it's all okay if i dont factory reset/wipe/anything-risky-in-general right?
Click to expand...
Click to collapse
Yes, this bug is known to trigger usually when you do a wipe using the recovery. However there have been some cases when doing a factory reset via the settings has also resulted in a brick. However if you stay away from recovery and do not intend to doing flashing/wipes then i guess you should be ok. And it is a matter of time before Samsung Comes up with a solution. They are said to be working on this bug already. I have the N7000 which i bricked once while flashing and then wiping but i got it repaired since i had warranty. Since then i have stayed away from wiping or installing any custom roms so the device has not given any problems. Hope this info helps! Cheers!
Rom doesnt load during boot
Dear Developers
I rooted my galaxy note and soon as that i got gained super user access for chain fire app, then i flashed CWM and installed crisello rom with abbysys kernel , it installed all the files correctly and soon after that the phone rebooted .After reboot the phone went inside the boot menu ( the world of galaxy UI boot menu ) and it frozen since then
i tired flashing various custom or stock roms and still the same problem i face
If someone could help me out on what the problem is and how i could get a fix to it
cuteglen said:
Dear Developers
I rooted my galaxy note and soon as that i got gained super user access for chain fire app, then i flashed CWM and installed crisello rom with abbysys kernel , it installed all the files correctly and soon after that the phone rebooted .After reboot the phone went inside the boot menu ( the world of galaxy UI boot menu ) and it frozen since then
i tired flashing various custom or stock roms and still the same problem i face
If someone could help me out on what the problem is and how i could get a fix to it
Click to expand...
Click to collapse
What rom are you on? Have you performed any wipes or factory resets?
Sent from my GT-N7000 using xda premium
Hi everybody
I have three questions if You can help me
1- Are speedmode and franco Kernels the only safe kernels for stock ICS?
2- Can I flash CM9 from stock ICS or it is safer to do it from GB rom?
3- Can I flash CM9 kernel for stock rom?
Thanx in advance
iraqi4ever80 said:
Hi everybody
I have three questions if You can help me
1- Are speedmode and franco Kernels the only safe kernels for stock ICS?
2- Can I flash CM9 from stock ICS or it is safer to do it from GB rom?
3- Can I flash CM9 kernel for stock rom?
Thanx in advance
Click to expand...
Click to collapse
1. Afaik yes
2. NO, you'll brick, flash from GB kernel, I know some have done from abyss.
3. No. CM based not compatible with Touchwiz framework.
Sent from my GT-N7000 using xda premium
I have a quick ( hopefully) question about the brick bug. I already asked but I think a mod must have deleted the whole thread, even though the thread was about the brick bug and I think I might have been bringing a new way ( well for some anyway) to flash safely to new ROMs.
So anyway, I have a 'safe' kernel ( speedmod), and I want to try out 4.0.4 stock ROM. I have extracted the stock ROM zip and the tar file inside. In there is the Zimage.
Do I just delete the Zimage then re-zip and flash from CWM?
OR Do I have to replace the Zimage with another, 'safe', Zimage ( for example just put the zimage in there from speedmod because I want to keep that for now). Does there NEED to be A Zimage there, or will it work fine without one. I don't want to start flashing the ROM and it get stuck half way through.
If it will work this way then this might be a fairly easy way for anybody to flash any new ROM they want. They'll just need to get a safe kernel on there in the first place.
SpyderTracks said:
1. Afaik yes
2. NO, you'll brick, flash from GB kernel, I know some have done from abyss.
3. No. CM based not compatible with Touchwiz framework.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
thank you for your response
just to be sure you said that it is unsafe to flash CM9 from stock ICS?
can we flash CM9 from stock ICS rom with safe kernel such as franco or speedmod
sorry for bothering you and thank you again
iraqi4ever80 said:
thank you for your response
just to be sure you said that it is unsafe to flash CM9 from stock ICS?
can we flash CM9 from stock ICS rom with safe kernel such as franco or speedmod
sorry for bothering you and thank you again
Click to expand...
Click to collapse
Only from GB kernel such as abyss. If you flash from ics kernel you WILL brick. This goes for all cm based roms.
Sent from my GT-N7000 using xda premium
kyllerbuzcut said:
I have a quick ( hopefully) question about the brick bug. I already asked but I think a mod must have deleted the whole thread, even though the thread was about the brick bug and I think I might have been bringing a new way ( well for some anyway) to flash safely to new ROMs.
So anyway, I have a 'safe' kernel ( speedmod), and I want to try out 4.0.4 stock ROM. I have extracted the stock ROM zip and the tar file inside. In there is the Zimage.
Do I just delete the Zimage then re-zip and flash from CWM?
OR Do I have to replace the Zimage with another, 'safe', Zimage ( for example just put the zimage in there from speedmod because I want to keep that for now). Does there NEED to be A Zimage there, or will it work fine without one. I don't want to start flashing the ROM and it get stuck half way through.
If it will work this way then this might be a fairly easy way for anybody to flash any new ROM they want. They'll just need to get a safe kernel on there in the first place.
Click to expand...
Click to collapse
Hiya, yep, you can just delete the zimage file, no need to replace, it will just skip writing that partition.
Sent from my GT-N7000 using xda premium
Gave that a go last night and I must not be doing something right. Either I need to re-zip it differently or I need to use something other than CWM (mobile odin?) because it's just aborting before it actually starts flashing anything.
Suppose I could always flash the separate elements on pc odin?
kyllerbuzcut said:
Gave that a go last night and I must not be doing something right. Either I need to re-zip it differently or I need to use something other than CWM (mobile odin?) because it's just aborting before it actually starts flashing anything.
Suppose I could always flash the separate elements on pc odin?
Click to expand...
Click to collapse
Try mobile odin. If you point to the tar, it should load all the components. You can then review which components are being flashed.
Sent from my GT-N7000 using xda premium
iraqi4ever80 said:
Hi everybody
I have three questions if You can help me
1- Are speedmode and franco Kernels the only safe kernels for stock ICS?
2- Can I flash CM9 from stock ICS or it is safer to do it from GB rom?
3- Can I flash CM9 kernel for stock rom?
Thanx in advance
Click to expand...
Click to collapse
1. Add goku, dafuq, gl-notecore and abyss42 (GB) to your list.
2. Only do it from a GB firmware or at least a GB kernel like abyss42. SPECIFIC instructions per firmware is listed for a reason. Follow those instructions to the letter.
3. No.
Sent from my GT-N7000 using xda app-developers app
kyllerbuzcut said:
Gave that a go last night and I must not be doing something right. Either I need to re-zip it differently or I need to use something other than CWM (mobile odin?) because it's just aborting before it actually starts flashing anything.
Suppose I could always flash the separate elements on pc odin?
Click to expand...
Click to collapse
Stock rom in a zip? Are you sure you are nit flashing a custom rom? Point us to the file/thread please.
If it is a custom rom, the it is meant to be via CWM.
1. Flash abyss42
2. Reboot recovery
3. Do your wipes
4. Flash.
Im sure there is a specific instruction on where you got that file. Or better yet, go to dr. Ketans thread and get your stock rom from there.
Sent from my GT-N7000 using xda app-developers app
It's just the standard rom file from sammobile.It does come as a zip you know. If you unzip it, then use rar on it you can see all the bits. I thought if I just put a different zimage in there it would just go ahead and use that, but didn't seem to like it after I zipped it all back up again.
Tonight I've ended up getting chainfires excellent CF-Root kernel.Flashed that through odin, over my speedmod kernel.
Put just the factoryfs part of the stock rom zip onto the SD card and flashed that using the cwm app that CF-Root installs for you.. Now have CF-Root kernel and 4.0.4 firmware.
If you don't already have a "safe" kernel then I dunno what the brick chances would be, but since I had a safe one already I thought it couldn't hurt to try it out.
The reason I haven't flashed the hidden, cache, model and sbl parts of the zip is that simply they wouldn't fit on my SD card If it behaves funny or I can make space then I'll try the rest too. And the reason I didn't flash the zimage from the zip should be fairly obvious. Because I don't want a brick
EDIT: I managed to clear some space on the SD and flashed the rest of it. Seems to be working ok, so far anyway. I'm hoping the battery issues from 4.0.3 will be a little better. This is a really good way of doing it all as you can just swap out a potentially bad kernel for one that has been 'protected' by having te emmc cap erase turned off.