Related
Why new Custom Rom doesn't work for my i9003 when everytime i install it?
However, after i install themes such as ICS-9lock on my device keep stucking at "samsung" logo and never boot into main screen. Can someone please help me?
This is how i did:
1) Put the "ICS-10lock-XWKPG_22.11.11" file into SDcard
2) go to Rom Manager > Flash into recovery mode (i choose i9000)
3) do nandroid backup & titanium backup
4) boot into recovery mode, select install zip. from SDcard.
5) choose zip from SDcard then install
After that the message show bellow>
Finding update package...
Verifing update package...
E.Failed to verify the whole-file sygnature
E:signature verification failed
Instalation aborted.
Then i choose
toggle signature verification
change from "enable" to "disable"
install zip. again message shown installation completed
wide dalvik cache in recovery mode,
After that, reboot system.
Once i reboot, i found out that my phone stuck in the "Samsung" logo... God, please help me !!
Currently my phone have been restart many time and flash so many time, i just want to get simple custom rom only. Amen...
thomas4147 said:
Why new Custom Rom doesn't work for my i9003 when everytime i install it?
However, after i install themes such as ICS-9lock on my device keep stucking at "samsung" logo and never boot into main screen. Can someone please help me?
This is how i did:
1) Put the "ICS-10lock-XWKPG_22.11.11" file into SDcard
2) go to Rom Manager > Flash into recovery mode (i choose i9000)
3) do nandroid backup & titanium backup
4) boot into recovery mode, select install zip. from SDcard.
5) choose zip from SDcard then install
After that the message show bellow>
Finding update package...
Verifing update package...
E.Failed to verify the whole-file sygnature
E:signature verification failed
Instalation aborted.
Then i choose
toggle signature verification
change from "enable" to "disable"
install zip. again message shown installation completed
wide dalvik cache in recovery mode,
After that, reboot system.
Once i reboot, i found out that my phone stuck in the "Samsung" logo... God, please help me !!
Currently my phone have been restart many time and flash so many time, i just want to get simple custom rom only. Amen...
Click to expand...
Click to collapse
I don't read every thread, and I don't know where you got this from. was it stated that this is in the format required for i9003, or did you just pick it up from somewhere else and try to install it?
if it's not for the i9003, then you have to re-flash some stock rom to fix your problem.
if it's for i9003, did you ensure you're using the same fw as was designated for the ics port? for example, is it for kpq and you're using kpq? if not, then you have to restore the backup you made before attempting this. if you forgot to do that, then you have to flash a stock rom to fix your problem. if they were matching and you're having problems, why not ask for help in the thread where you got it from?
supergaijin said:
I don't read every thread, and I don't know where you got this from. was it stated that this is in the format required for i9003, or did you just pick it up from somewhere else and try to install it?
if it's not for the i9003, then you have to re-flash some stock rom to fix your problem.
if it's for i9003, did you ensure you're using the same fw as was designated for the ics port? for example, is it for kpq and you're using kpq? if not, then you have to restore the backup you made before attempting this. if you forgot to do that, then you have to flash a stock rom to fix your problem. if they were matching and you're having problems, why not ask for help in the thread where you got it from?
Click to expand...
Click to collapse
Thanks for you review and comment.
First of all, i would like to stated that i have fully meet the requirement of flashing a custom rom. I'm user of KPQ of course i will find a custom rom for my i9003 KPQ. The purpose of this tread is to mention why every time i flashing a new custom would have the same problem occur whereby my device always stuck at the booting logo or reboot over and over again. This has make me troublesome to reflash back to stock rom when every time i failed to do that.
First, i root.
2nd, install rom manager
3rd, Flash CWM recovery
4th, do nandroid backup (use rom manager)
5th, application & data backup (use titanium)
6th, then istall .zip (custom rom)
Is't i missed any step before i flash a new custom rom??
What about deodex ?? it's necessary for us to deodex before we proceed to update our device?
However, i have fully meet all the requirement but why every time i flash different custom rom also failed.
Thanks again for your kindly advice
thomas4147 said:
Thanks for you review and comment.
First of all, i would like to stated that i have fully meet the requirement of flashing a custom rom. I'm user of KPQ of course i will find a custom rom for my i9003 KPQ. The purpose of this tread is to mention why every time i flashing a new custom would have the same problem occur whereby my device always stuck at the booting logo or reboot over and over again. This has make me troublesome to reflash back to stock rom when every time i failed to do that.
First, i root.
2nd, install rom manager
3rd, Flash CWM recovery
4th, do nandroid backup (use rom manager)
5th, application & data backup (use titanium)
6th, then istall .zip (custom rom)
Is't i missed any step before i flash a new custom rom??
What about deodex ?? it's necessary for us to deodex before we proceed to update our device?
However, i have fully meet all the requirement but why every time i flash different custom rom also failed.
Thanks again for your kindly advice
Click to expand...
Click to collapse
oops, first, I misread 9lock as clock
then, when flashing a custom ROM, in general, you must be deodexed first. if it's required, I would expect the dev to mention it in their thread. after flashing custom rom, you must also wipe dalvik cache. I don't know if it's necessary, but I do both dalvik and "plain" cache after flashing. have you done these two steps?
then, if you're installing the alpha ics release from the other thread, as stated, it's alpha, so not bug free. in general, custom ROMs will have at least one or two bugs, due to not every potential possible combination of operations can be performed without extensive testing and correction, and especially on our phone, the testing isn't so extensive since there aren't so many users.
edit: I found the thread you're referring to. it's "RC2", which means not necessarily stable (Release Candidate 2). go ask tripin for some help
Thank you for your advice.
Now i can taste my new themes with having a few tiny bugs. I'm so impress you can solve my problem. By the way, i will post up a new thread which guide other people to install custom rom for detail step. TQ
thomas4147 said:
Thank you for your advice.
Now i can taste my new themes with having a few tiny bugs. I'm so impress you can solve my problem. By the way, i will post up a new thread which guide other people to install custom rom for detail step. TQ
Click to expand...
Click to collapse
glad I could help
I can't say for sure, but I think your thread would go under "general", with [TUTORIAL] as the tag in the title, to save time. you can alwaysask a mod for confirmation
can someone please describe the whole procedure to install custom rom(galaxyv5) just after flashing xxkpq
please
(everything deox. if required,cf root if required and how to do this)
please help I know nothing about installing custom roms reply as soon possible
a big thanks to the reply
Sent from my GT-I9003 using xda premium
manishnraj said:
can someone please describe the whole procedure to install custom rom(galaxyv5) just after flashing xxkpq
please
(everything deox. if required,cf root if required and how to do this)
please help I know nothing about installing custom roms reply as soon possible
a big thanks to the reply
Sent from my GT-I9003 using xda premium
Click to expand...
Click to collapse
ask kishen in his thread instead of hijacking a thread that is totally unrelated
supergaijin said:
ask kishen in his thread instead of hijacking a thread that is totally unrelated
Click to expand...
Click to collapse
have you read the title ,if not
it is about how to install custom roms
so if you know reply
otherwise only read
Sent from my GT-I9003 using xda premium
manishnraj said:
have you read the title ,if not
it is about how to install custom roms
so if you know reply
otherwise only read
Sent from my GT-I9003 using xda premium
Click to expand...
Click to collapse
oops, my bad. as you can see, I was conversing with the OP, and this thread was actually for another specific problem, but since the title is a generality, here goes:
first, follow these steps: http://forum.xda-developers.com/showpost.php?p=19663863&postcount=754
then install cwm, put kishen's rom on your sd card, and flash and wipe normal and dalvik cache
supergaijin said:
oops, my bad. as you can see, I was conversing with the OP, and this thread was actually for another specific problem, but since the title is a generality, here goes:
first, follow these steps: http://forum.xda-developers.com/showpost.php?p=19663863&postcount=754
then install cwm, put kishen's rom on your sd card, and flash and wipe normal and dalvik cache
Click to expand...
Click to collapse
now that's an answer
thanks
Sent from my GT-I9003 using xda premium
pls help me
would you please just suggest me any custom rom for i9003 with loop device support.i want a custom rom for it.please suggest me any good one in which i get stock rom features or ics build features.i dont want anyone else.please help me.i am raedy to click any thanks meter if you help me.thanks in advance
thomas4147 said:
Why new Custom Rom doesn't work for my i9003 when everytime i install it?
However, after i install themes such as ICS-9lock on my device keep stucking at "samsung" logo and never boot into main screen. Can someone please help me?
This is how i did:
1) Put the "ICS-10lock-XWKPG_22.11.11" file into SDcard
2) go to Rom Manager > Flash into recovery mode (i choose i9000)
3) do nandroid backup & titanium backup
4) boot into recovery mode, select install zip. from SDcard.
5) choose zip from SDcard then install
After that the message show bellow>
Finding update package...
Verifing update package...
E.Failed to verify the whole-file sygnature
E:signature verification failed
Instalation aborted.
Then i choose
toggle signature verification
change from "enable" to "disable"
install zip. again message shown installation completed
wide dalvik cache in recovery mode,
After that, reboot system.
Once i reboot, i found out that my phone stuck in the "Samsung" logo... God, please help me !!
Currently my phone have been restart many time and flash so many time, i just want to get simple custom rom only. Amen...
Click to expand...
Click to collapse
hello
I got the same message when flashing rom...
Finding update package...
Verifing update package...
E.Failed to verify the whole-file sygnature
E:signature verification failed
Instalation aborted.
I tried to toggle signature verification
change from "enable" to "disable"...But cannot solve the problem Any other idea man? A help would be great....
I notice pretty much all the roms I run from the nexus s 4 g development work on the nexus 4g, pretty much a given, my concern is when I take a combination someone suggests and attempt to flash it on the s 4g, the installation gets aborted, I've had this problem so far with the pixel rom lite touch, the cyberGR mod and the air kernal 3.6 when trying to flash with codename android 1.5.5 (bootloop) any suggestions, I know how to flash roms PROPERLY so please don't suggest that (Wipe Data/Factory Reset,Wipe Cache Partition,Wipe Dalvik Cache)
Here is exactly what clockwork mod recovery 5.0.2 tells me when I try flashing air kernel 3.6 voodoo colors no animation:
-- Installing: /sdcard/download/air_kernal_v3.6_voodoo_colors-03142012-noani.zip
Finding update package...
Opening update package...
E:Can't open /sdcard/download/air_kernal_v3.6_voodoo_colors-0314212-noani.zip
(bad)
Installation aborted.
Same here. Did you ever find a fix?
No experience with that rom or kernel but I would redownload the zip. Maybe it is corrupted. Would look in the dev thread for the kernel to see if others have the issue.
well the 3.5 version of voodoo worked and flashed fine for me but 3.6 was a whole other story, so I just stuck with what is working for me the best (check sig)
yep pt.2 people meaning i already had this problem before and have been solved!
but now this time it's more persistent than before because the only ROM that's been only working for me is the new FITDroid 3.5 (5-2-12) and the other ROM is just going to be stuck at the splash screen or something (where the ROM name or title will be displayed) or be on a bootloop I already tried wiping data, cache and dalvik cache and still it doesn't work.
Working ROMs so far:
Fitdroid 3.5 by Vishwanathptl
Creed's Revolution 3.1 by pratyush.creed w/ boot.zip patch for FitDroid 3.5 by Vishwanathptl
RazoDroiD 4.0 by rajrocks w/ boot.zip patch for Fitdroid 3.5 by Vishwanathptl
ChocoBread 3.0.0 by parudthz w/ boot.zip patch for Fitdroid 3.5 by Vishwanathptl
P.S. "boot.zip" patch for Fitdroid 3.5 can be found HERE or HERE if you can't find it.. (p.s. that's not a mirror it is still Vishwanathptl's original link)
and here are the ROMs i've tried so far and the problems...
CM:
CM7.2 RC1 by Vishwanathptl - stuck on android screen
CM7.2 RC1 by TJ - stuck on android screen
CyanMobile by Squadzone - stuck on android screen
Miracle ROM (base on CM) by DQiB -stuck on android screen
Non-CM ROM:
Creed's ROM 3.1 by pratyush.creed - stuck on splash or title screen
RazoDroid 4.0 by rajrocks - stuck on splash or title screen
Chocobread 3.0.0 by parudthz - stuck on splash or title screen
Stock and Deodexed ROM:
XXKPP - Bootloop
XXKPL deodexed by Vishwanathptl - Bootloop
DXKT7 - Bootloop
XWKTI - Bootloop
DDKT3 - Bootloop
And yes I did wipe everything data, cache and dalvik cache and still those problems are still coming up.
So does anyone know what's the problem here
edit new info: I think there's something wrong with the "data" because CWM even on the stock recovery it's saying "cannot mount data".
edit new info 2: something weird just happened some of the ROM that i've tested started to work and some of these ROM is RazoDroiD 4.0 so this is what happened..
I flashed RazodroiD 4.0 on CWM and then i flashed Vish. "Boot.zip" patch for Fitdroid 3.5 which is here -> http://forum.xda-developers.com/showpost.php?p=17874689&postcount=2 and it started to work!
weird thing is that when i go to settings>about phone>kernel version it looked like this ---> "2.6.35.7-perf-CL260130 [email protected] #2" and the Build Number is RazoDroiD v4.0 by rishee. This is the samething that I have been seeing on the other ROM.
remove the sim card and start without it
AND format system...
Typed on a small touchscreen
samo_gf said:
remove the sim card and start without it
Click to expand...
Click to collapse
a.cid said:
AND format system...
Typed on a small touchscreen
Click to expand...
Click to collapse
nope didn't work i even tried formating everything on CWM but still stuck on title screen or bootloop...
now this time it's showing some errors sometimes i can see in the CWM "error can't mount data" when i flash some ROM and when i tried to wipe the data i see this "E: format_volume: make_extf4fs fail(????) on /dev/block/stl13". and now i can't wipe dalvik cache because it's not showing the yes & no wipe dalvik cache.
P.S still on FITDroid 3.5 because that's the only ROM that have been working for me.
The stock rom that you tried flashing, did they have bootloaders removed??
Typed on a small touchscreen
a.cid said:
The stock rom that you tried flashing, did they have bootloaders removed??
Typed on a small touchscreen
Click to expand...
Click to collapse
I think these two the DXKT7 and XWKTI i got it from annson08's thread but the XXKPP i don't know?
raizen101 said:
nope didn't work i even tried formating everything on CWM but still stuck on title screen or bootloop...
now this time it's showing some errors sometimes i can see in the CWM "error can't mount data" when i flash some ROM and when i tried to wipe the data i see this "E: format_volume: make_extf4fs fail(????) on /dev/block/stl13". and now i can't wipe dalvik cache because it's not showing the yes & no wipe dalvik cache.
P.S still on FITDroid 3.5 because that's the only ROM that have been working for me.
Click to expand...
Click to collapse
r u using cwm by tj_style .. ??
flash the stock rom ddkt3
flash the stock rom ddkt3 and then root it.. it will work
avilove4u said:
r u using cwm by tj_style .. ??
Click to expand...
Click to collapse
tejkumarvusirikala said:
flash the stock rom ddkt3 and then root it.. it will work
Click to expand...
Click to collapse
yep using tj_style's CWM
and nope dude DDKT3+root didn't work
another info: I think there's something wrong with the "data" because even on the stock recovery it's saying "cannot mount data".
Annson's thread has the bootloaders removed...
So now try this...
Download latest firmware for your region from samfirmware and flash it...
Root it, and then install cwm by tj style...
And then try flashing any stock based (not cm based) custom rom (obviously except fitdroid, since it already works)...
Also, format system (from cwm) and remove sim card before flashing custom rom...
Typed on a small touchscreen
Do tell us the result...
Typed on a small touchscreen
a.cid said:
Annson's thread has the bootloaders removed...
So now try this...
Download latest firmware for your region from samfirmware and flash it...
Root it, and then install cwm by tj style...
And then try flashing any stock based (not cm based) custom rom (obviously except fitdroid, since it already works)...
Also, format system (from cwm) and remove sim card before flashing custom rom...
Typed on a small touchscreen
Click to expand...
Click to collapse
hmm gonna try that later i'ts 11:00pm here and I need to sleep wait for the result in about 8-10 hours lol
anyway something weird just happened some of the ROM that i've tested started to work and some of these ROM is RazoDroiD 4.0 so this is what happened..
I flashed RazodroiD 4.0 on CWM and then i flashed Vish. "Boot.zip" patch for Fitdroid 3.5 which is here -> http://forum.xda-developers.com/showpost.php?p=17874689&postcount=2 and it started to work!
weird thing is that when i go to settings>about phone>kernel version it looked like this ---> "2.6.35.7-perf-CL260130 [email protected] #2" and the Build Number is RazoDroiD v4.0 by rishee. This is the same thing that I have been seeing on the other ROMs too.
a.cid said:
Do tell us the result...
Typed on a small touchscreen
Click to expand...
Click to collapse
okay I guest you don't need to wait 8-10 hours for the result because i have it and here it is! *drumroll*....................... it....................... didn't worked... it's still stuck on the splash/title screen. oh well I guest i just try that random solution that i just discover then. thanks anyway! and if have you any more idea how to fix this problem please do tell me .
Okay, do you actually wait for the bootanim to go?
Coz it takes time, won't boot up in 10secs...
And the while the bootanim is running, if the phone vibrates just a little, and then the screen dims somewhat, then the rom is successfully flashed...
Typed on a small touchscreen
Have you tried to flash the Full package Stock Rom.???
I mean not the one package Stock Rom..
Sent from my Galaxy Fit
a.cid said:
Okay, do you actually wait for the bootanim to go?
Coz it takes time, won't boot up in 10secs...
And the while the bootanim is running, if the phone vibrates just a little, and then the screen dims somewhat, then the rom is successfully flashed...
Typed on a small touchscreen
Click to expand...
Click to collapse
yep i waited somewhere around 10-15 min. on every ROM I've flashed (including stock rom which usually takes around under 5 min. i think?) and still stuck on splash/title screen or bootloop.
cygnus39 said:
Have you tried to flash the Full package Stock Rom.???
I mean not the one package Stock Rom..
Sent from my Galaxy Fit
Click to expand...
Click to collapse
nope and where can i get a full package stock ROM? all i can see is one package.
raizen101 said:
nope and where can i get a full package stock ROM? all i can see is one package.
Click to expand...
Click to collapse
gingerbread's first version has four files .. !!
XWKTI has 4 files and it's the latest European one
Sent from my GT-S5670 using xda premium
avilove4u said:
gingerbread's first version has four files .. !!
Click to expand...
Click to collapse
samo_gf said:
XWKTI has 4 files and it's the latest European one
Sent from my GT-S5670 using xda premium
Click to expand...
Click to collapse
where can I get it though? all i can see is one package stock ROMs
am trying to flash overclock kernel, am using cmw7.1...while flashing its says error installation aborted...plz help am dying to overclock my galaxy fit
make sure that your overclock kernel you flash , its a file.zip not file.md5
ya its a zip file am using....going into recovery mode....mount/system..then flashing still no luck...
I apologize, I posted an off base response. Read it wrong. Trying to delete comment.
Hi,
I tried several kernels for JB. Air, Matrix. None of them worked for me. After flashing it, it won't boot the system and turn off the device. I currently use JellyBelly 1.5. Any idea? Is it ROM bug? Thanks!
devcager said:
Hi,
I tried several kernels for JB. Air, Matrix. None of them worked for me. After flashing it, it won't boot the system and turn off the device. I currently use JellyBelly 1.5. Any idea? Is it ROM bug? Thanks!
Click to expand...
Click to collapse
I can't use Adam's Jelly Belly rom, as I have a NS4g, but I do follow his work. I believe that his rom comes with Thalamus kernel, and if you want to flash a different kernel, there is a file which needs to be deleted before doing so. There was quite a discussion about all this in his thread in the development forum. That's where you can figure it out ... good luck!
same for me
Hey i also tried to flash thalamus kernel but my phone didnt start it was hanged up on the boot screen. I am using Nexus S i9023 SCLD version stock rom 4.1.1 build JRO03E and it is rooted.
Can anyone please help me and also which other kernels are supported on stock rom.
There's a script you must delete in the init.d to use another kernel in Jelly Belly 0.1.5
Otherwise, your phone will poweroff
panks_4ever said:
Hey i also tried to flash thalamus kernel but my phone didnt start it was hanged up on the boot screen. I am using Nexus S i9023 SCLD version stock rom 4.1.1 build JRO03E and it is rooted.
Can anyone please help me and also which other kernels are supported on stock rom.
Click to expand...
Click to collapse
i have also a i9023 and i have allredy flashed bedalus kernel, thalamus and air kernel also matrix and vta2 worked for me..
i use JRO03E DX stock ROM..never had a problem
S.R.
(I use stock JB with Air #153, and got i9023. No OC, no NSTools, yet. I have no problem.)
On stock:
Try to do a factory reset/wipe data, or reflash the OS from scratch using factory images. And right after flashing the rom, flash the kernel. Even before installing any apps.
On JBelly:
For this, I think the Thalamus kernel is the best, the rom is come with it, so they made for each other If this kernel works with it, i think it is unnecessary to switch to another kernel right now.
Because JB kernels are not final yet, are "immature", there can be compatibility issues, collisions between (certain functions of) roms and kernels.
After a 2 or 3 releases, both on rom and kernel side, there will be more complete and stable versions.
Have you tried to fix permissions ?
Go to /etc/init.d/ folder and delete a file called 'kernel'. You can read it first if you want.
This is basically a hack that AdamG added to avoid everyone changing kernels and reporting problems about the ROM. He only allows thalamus kernel.
Can please provide me detailed steps of how to flash a thalamus kernel on stock jb because i think the procedure is wrong. I did the following steps:
1. Reboot into recovery( I am using Clockwork Mod recovery touch 6.0.1.0)
2. Wipe Cache partition
3. Wipe Dalvik cache
4. Install the kernel zip file
And after i tried restarting my phone but it hanged up on the boot screen.
Please someone advise me the correct steps if this is wrong
. Thanks in advance
Sent from my Nexus S using xda app-developers app
panks_4ever said:
1. Reboot into recovery( I am using Clockwork Mod recovery touch 6.0.1.0)
2. Wipe Cache partition
3. Wipe Dalvik cache
4. Install the kernel zip file
Click to expand...
Click to collapse
I think the cache partition wipe is your problem. You shouldn't have to wipe anything if you're flashing _thalamus' kernel on stock JB. Just flash and reboot. I've done it plenty of times without problems.
devcager said:
Hi,
I tried several kernels for JB. Air, Matrix. None of them worked for me. After flashing it, it won't boot the system and turn off the device. I currently use JellyBelly 1.5. Any idea? Is it ROM bug? Thanks!
Click to expand...
Click to collapse
To not have to deal with third party kernel support there is /system/etc/init.d/00kernel that simply powers off your phone if you flash another kernel.
Flash the rom to boot it, delete the file, then flash any kernel you want as you usually would.
charchuck said:
I think the cache partition wipe is your problem. You shouldn't have to wipe anything if you're flashing _thalamus' kernel on stock JB. Just flash and reboot. I've done it plenty of times without problems.
Click to expand...
Click to collapse
wipe is not needed...
but fix permissions should be done...but I´m not sure thats required for all kernel.
S.R.
so this are the final steps...
shivasrage said:
wipe is not needed...
but fix permissions should be done...but I´m not sure thats required for all kernel.
S.R.
Click to expand...
Click to collapse
Firstly, thanks for replying. I need to do the folloing steps (just to confirm because its better to do so and also i dont want to again restore a backup)
1. Reboot into recovery
2. Wipe Dalvik Cache
3. Install the kernel zip file
4. Fix Permissions
or 3. Fix Permissions, and then
4. Install kernel zip file
Please advise the correct steps and thanks in advance.
(I know i am getting a bit more concerned because i had it twice and i am not able to flash the same. So, I am trying to get a correct way and this the best place to ask. XDA rocksssssss<3<3<3)
panks_4ever said:
Firstly, thanks for replying. I need to do the folloing steps (just to confirm because its better to do so and also i dont want to again restore a backup)
1. Reboot into recovery
2. Wipe Dalvik Cache
3. Install the kernel zip file
4. Fix Permissions
or 3. Fix Permissions, and then
4. Install kernel zip file
Please advise the correct steps and thanks in advance.
(I know i am getting a bit more concerned because i had it twice and i am not able to flash the same. So, I am trying to get a correct way and this the best place to ask. XDA rocksssssss<3<3<3)
Click to expand...
Click to collapse
There's no need for all that... flash jellybelly latest version, boot with the original kernel and delete /system/etc/init.d/00kernel with Rom Toolbox or Root explorer. After that you can flash the kernel that you want. Mind that this will only work for version 0.1.5.1, versions after that one will probably have a framework check to prevent flashing 3rd party kernels because the dev of jellybelly doesn't want to be disturbed with bugs caused by other kernels then not the Thalamus one.
---------- Post added at 08:55 AM ---------- Previous post was at 08:34 AM ----------
Checked. Version 1.0.0 only allows Thalamus kernel to be flashed. A framework check doesn't allow 3rd party kernels to be fixed so either you stick to the stock kernel of jellybelly or get another ROM so you can use other Kernels.
Panks_4ever
What I always do.. (phone i9023 X-JB Stock).
1. flash kernel zip
2. wipe cache
3. wipe dalvik
4. fix permissions
i only know that thalamus kernel don´t need any wipe...also i don´t know if this procedure is right or not
and i don´t won´t discuss about i only can report what worked for me so try it or not its your decision....
S.R.
thank you
shivasrage said:
Panks_4ever
What I always do.. (phone i9023 X-JB Stock).
1. flash kernel zip
2. wipe cache
3. wipe dalvik
4. fix permissions
i only know that thalamus kernel don´t need any wipe...also i don´t know if this procedure is right or not
and i don´t won´t discuss about i only can report what worked for me so try it or not its your decision....
S.R.
Click to expand...
Click to collapse
DeuXGod said:
There's no need for all that... flash jellybelly latest version, boot with the original kernel and delete /system/etc/init.d/00kernel with Rom Toolbox or Root explorer. After that you can flash the kernel that you want. Mind that this will only work for version 0.1.5.1, versions after that one will probably have a framework check to prevent flashing 3rd party kernels because the dev of jellybelly doesn't want to be disturbed with bugs caused by other kernels then not the Thalamus one.
---------- Post added at 08:55 AM ---------- Previous post was at 08:34 AM ----------
Checked. Version 1.0.0 only allows Thalamus kernel to be flashed. A framework check doesn't allow 3rd party kernels to be fixed so either you stick to the stock kernel of jellybelly or get another ROM so you can use other Kernels.
Click to expand...
Click to collapse
Thank you shivasrage and DeuXGod. I am surely goona try out this, i am being eagerly waiting to flash a custom kernel because as compared to ICS i feel JB is eating up more battery. Thank you so much:good: