Related
I've the CriskeloROM ICS ZCLP6 and I'm afraid of brick my phone. So I want to go back to GB but I don't know if I'm with i9220 kernel or not or one safe way to go back to GB.
A good tutorial will be good to me and to the others. I know that anything is safe because we don't know the real cause of this, but...
EDIT: There's my phone info:
Model number: GT-N7000
Android Version: 4.0.3
Baseband version: N7000XXLP1
Kernel version:
3.0.15-I9220ZCLP5-CL295568
[email protected] #3
SMP PREEMPT Tue Mar 27 00:15:32 KST 2012
Build number: CriskeloROM ICS ZCLP6
this has been asked and answered about a thousand times recently
flash a gb kernel such as abyss 4.2 and then restore from a backup
Richy99 said:
this has been asked and answered about a thousand times recently
flash a gb kernel such as abyss 4.2 and then restore from a backup
Click to expand...
Click to collapse
Thank you. I search for "back do GB", "restore from i9220 bootloader" and others and dont find anything.
Thank you again.
- dowmload any GB custom rom, copy to your sdcard
- download jBroid Kernel Cleaning, copy to yout sdcard
- download AbyssNote v4.2 kernel, copy to your sdcard
- reboot to CWM recovery
- flash jBroid Kernel Cleaning
- flash AbyssNote v4.2 kernel
- reboot recovery
- flash new GB custom rom
- flash new kernel (if you prefer other than AbyssNote kernel)
- FULL WIPE
- REBOOT
thehackersz said:
- dowmload any GB custom rom, copy to your sdcard
- download jBroid Kernel Cleaning, copy to yout sdcard
- download AbyssNote v4.2 kernel, copy to your sdcard
- reboot to CWM recovery
- flash jBroid Kernel Cleaning
- flash AbyssNote v4.2 kernel
- reboot recovery
- flash new GB custom rom
- flash new kernel (if you prefer other than AbyssNote kernel)
- FULL WIPE
- REBOOT
Click to expand...
Click to collapse
Flash in the "bad" CWM? That script will format partitions without wipe function and without detiorate the eMMC, thats it?
pauloallex24 said:
Flash in the "bad" CWM? That script will format partitions without wipe function and without detiorate the eMMC, thats it?
Click to expand...
Click to collapse
you're on leaked rom CriskeloROM ICS ZCLP6 not LPY ICS rom.
thehackersz said:
you're on leaked rom CriskeloROM ICS ZCLP6 not LPY ICS rom.
Click to expand...
Click to collapse
But this ROM is not based on a REPACK? You are saying that this ROM is safe?
leaked ics rom (REPACK) and official ics LPY rom both are dangerous
thehackersz said:
leaked ics rom (REPACK) and official ics LPY rom both are dangerous
Click to expand...
Click to collapse
So I'm not understanding something. This is a leaked ics, so this is a repack that is dangerous and not recommended to use CWM. So if I flash that ZIP's from CWM don't I'm on the way to brick the phone?
Thanks for the help you are giving to me.
This very detailed video should help: http://www.youtube.com/watch?v=jr3DDEh8vyc&feature=plcp
pauloallex24 said:
So I'm not understanding something. This is a leaked ics, so this is a repack that is dangerous and not recommended to use CWM. So if I flash that ZIP's from CWM don't I'm on the way to brick the phone?
Thanks for the help you are giving to me.
Click to expand...
Click to collapse
you're wrong, CWM problem is for offical LPY ICS rom germany not for the Leaked rom ICS ZCLP6. You can still use CWM to flash kernel, but DON'T WIPE ANYTHING.
Both of this rom are dangerous, and my advise to you is to revert back to GB rom.
jBroid cleaner is new to me. Should i use it, even though i'm already reverted back to GB ROM and flashed speedmod kernel?
send from my sparkling white Galaxy Note, using XDA Premium.
Well, I understant now
Thank you all for the help! I will revert back to GB this night.
[email protected] said:
jBroid cleaner is new to me. Should i use it, even though i'm already reverted back to GB ROM and flashed speedmod kernel?
send from my sparkling white Galaxy Note, using XDA Premium.
Click to expand...
Click to collapse
is not really necessary to flash kernel cleaner but many of us using it before flashing other kernel
Hi. I've done this and I'm on GB now. But now I have a new question. Because I flash the LP1 ROM, when I go to download mode, it says "Binary: Custom". I supose that was because I flash the I9220 Bootloader.
If I want to reset the flash counter with a Jig to sent the phone to warranty (if I need), probably I need to flash the "samsung oficial" bootloader.
Anyone can explay this better ou help me flashing the original bootloader and leave the phone in warranty again, please?
EDIT: If helps, I have a ROM that I copy from Kies when I upgrade the first time the note with a oficial ROM. If when I flash that, it will install the original bootloader, say the ODIN options and I will flash it.
THanks for any help.
My path to hard bricking DO NOT FOLLOW THESE STEPS
Step 1 : updated to ICS(4.0.3 LP8) OTA
Step 2 : Rooted with the help of Dr_Ketans guide (worked perfectly fine - no issues so far)
Step 3 : even after rooting, while entering recovery i used to get, what I feel, was the stock recovery and not CWM (as in drketans guide), so I flashed CWM.zip from stock recovery and from CWM recovery I performed a nandroid backup - till now all izz well.
Step 4 : (It gets bad here)
Now from the CWM recovery i flash asylum rom - and its over. Hard bricked.
Not able to go to recovery
Not able to switch it on normally (duh...)
Not able to enter download mode, not even the blind download mode where nothing is visible on the screen but ODIN detects it....
this is not a complain thread, just wanted to share this so that others do not commit the same mistake
If mods feel this is unnecessary please remove it and add this info to pre-existing threads.
P.S :
Note ICS OTA Update from India
Kernel Version :
3.0.15-N7000DLP8-CL551076
[email protected] #3
SMP PREEMPT Sat May 12 16:05:17 KST 2012
Build number
IML74K.DDLP8
So you actually didn't read this part from the asylum thread about installation:
-be on a proper working recovery, (DAFUQ, CM9 or a GB recovery ONLY)
-DO NOT FLASH FROM I9220 LEAK REPACK ROMS
-DO NOT FLASH FROM LPY BASED ICS ROMS,
-IF YOU ARE UNSURE PLEASE POST A SCREENSHOT AND ASK.
Too bad that you bricked your note though.
If im not mistaken, Asylum is a CM9 based rom and it should not be flashed on a Samsung Based ICS. This would eventually result to Brick. Any CM9 based rom should only be flashed on a GB based rom or another CM9 based. Just my 2 cents on this issue.
jeez thats right he flashed it on an ics based rom.
tol xelir, what rom are you using now.
as Entropy said, CWM operations on LPY/LPF aren't safe
Xnnn!!! said:
as Entropy said, CWM operations on LPY/LPF aren't safe
Click to expand...
Click to collapse
Even the new Poland/Turkey LPF ?
So which one is safe for now, is it LP9 ?
No stock samsung kernel is safe to wipe in. Latest Cf-kernel, franco and speedmod might be safe. But its not yet 100% guaranteed.
Other than that its just the cm9 kernels that are completely safe.
xelir13 said:
If im not mistaken, Asylum is a CM9 based rom and it should not be flashed on a Samsung Based ICS. This would eventually result to Brick. Any CM9 based rom should only be flashed on a GB based rom or another CM9 based. Just my 2 cents on this issue.
Click to expand...
Click to collapse
The issue is w/ the kernel of the stock ICS and has nothing to do w/ CM9 being flashed over the stock ICS. In fact, installation instructions for the rest of the ICS based custom ROMs are now similar to CM9. As mentioned by the devs, it's not safe to wipe or flash another ROM when on an ICS stock kernel.
Gotta love it that people dont read the first post or even a thread
You should be warning people to read to not make same mistake
Sent from my GT-N7000 using Tapatalk 2
One more Joins the party even after warnings all over XDA. Hope Samsung replaces your Mobo under warranty.
Sent from my GT-N7000
yanix said:
The issue is w/ the kernel of the stock ICS and has nothing to do w/ CM9 being flashed over the stock ICS. In fact, installation instructions for the rest of the ICS based custom ROMs are now similar to CM9. As mentioned by the devs, it's not safe to wipe or flash another ROM when on an ICS stock kernel.
Click to expand...
Click to collapse
Its not safe to flash any CM9 based roms on samsung based ICS. If you are willing to read more its indicated in most of the CM9 based roms threads even the CM9 nightlies thread it indicates that its not safe flashing on any samsung ics roms. Its only safe to flash a cm9 based rom on a gb rom or a cm9 rom.
But if your convinced on what you just have said then try flash any cm9 based rom on a samsung based ICS.
Sent from my GT-N7000 using Tapatalk 2
Bricked mine nearly the same way yesterday. no recovery, no download mode. phone goes to samsung for warranty. After the eMMC file structure is corrupt, is there any possibilities for samsung to see what rom caused the brick?!
xelir13 said:
Its not safe to flash any CM9 based roms on samsung based ICS. If you are willing to read more its indicated in most of the CM9 based roms threads even the CM9 nightlies thread it indicates that its not safe flashing on any samsung ics roms. Its only safe to flash a cm9 based rom on a gb rom or a cm9 rom.
But if your convinced on what you just have said then try flash any cm9 based rom on a samsung based ICS.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
I know that but it's not just CM9. It's also not safe to flash other custom roms on top of a samsung based ICS. Regardless on what you flash (CM9 or other ROM) you could brick your device. And why would i flash cm9 on a samsung based rom when i just said in my previous post that "As mentioned by the devs, it's not safe to wipe or flash another ROM when on an ICS stock kernel."
iamendangered said:
Step 3 : even after rooting, while entering recovery i used to get, what I feel, was the stock recovery and not CWM (as in drketans guide)
Click to expand...
Click to collapse
From memory the CWM is not permanent and goes after a reboot, it is purely used to install busybox and su.
saved by SAMSUNG
got back the phone from them,
thank you for all the help.
[UPdated]4.04 LPM danger -> move to LQ5 Kernel [info]& How to screen capture in 4.04
Update: Please install a custom recovery if you are running any of the 4.04 kernels. LPM KERNELS ARE MORE AT RISK!!!
I reverted back to LQ5 yesterday because of the issue with Youtube HD not functioning unless I roll back the Youtube version or swap kernels. Aside from that Chainfire has warned me that he will not be releasing and CF-root for LPM because it has an underlying Kernel *possible* brick problem that cannot be alleviated with just updating to custom recovery via CF-Root.
Custom recovery DOES implement a different means of running the wipe factory data reset that *shouldn't* cause a brick. But as per Chainfire's PM we may still be at risk?
http://download.chainfire.eu/202/CF-Root/SGS2/CF-Root-SGS2_XX_OXA_LQ5-v5.6-CWM5.zip
To check if you are one of these people that may have the eMMC corruption and possible bricking of your S2....check for Chainfires app called Gotbrickbug. Also by chainfire.
Gotbrickbug thread
http://forum.xda-developers.com/showthread.php?t=1693704
Check to see if you are at risk BEFORE flashing anything.
1day 9hours and 11% discharging. 48% is screen so usage is about right seeming we sleep half the time LOL Me a bit more so than most others haha. Damn Narcolepsy
James
Screen capture method for 4.04 ICS Samsung is now long press button then long press home button; and in that order too. Not power and volume down like on 4.03.
Either use these and or wait for my ROM to be released via Darky if you are not confident.
Please give all credits to Chainfire for this, without him XDA would not have Root, so be thankful this guy continues to support us all.
This AWESOMELY INCREDIBLE
Phone: XXLQ5 (Android 4.0.4)
Modem: XXLQ6
Kernel: Stock (unrooted)
Launcher: Apex 1.2.4
..
tariq2kn said:
This AWESOMELY INCREDIBLE
Phone: XXLQ5 (Android 4.0.4)
Modem: XXLQ6
Kernel: Stock (unrooted)
Launcher: Apex 1.2.4
Click to expand...
Click to collapse
You're on LQ5, you may want to ditch the kernel and run with LPM man. Its the wipe script that is in the recovery that will corrupt your eMMC. Not just the stupid .PIT file that it came with + stupid people trying to restore from a custom kernel after the repartition. Both are issues with LQ5.
Attached is the LPM ZImage + CWM apk. Use CWM apk by chainfire to flash the zImage. Then flash this
http://download.chainfire.eu/202/CF-Root/SGS2/CF-Root-SGS2_XX_OXA_LQ5-v5.6-CWM5.zip
That will give you root and recovery too DO NOT WIPE ON THE CURRENT LQ5 KERNEL!!
Attachments now removed as per Chainfires instructions. For future reference please don't redistribute his CWM app, it gets installed with the CF-root flash anyway.
You seem to be saying that LPM has a safe kernel, while in fact it hasn't. There are even reports of people bricking their s2 by using the official recovery (not cwm) under stock lpm kernel.
Any of the newer firmwares than LQ5 seems to be very dangerous! Russian forums reported many people to have hard bricked their devices also whilst wiping data partition on lwm kernel...
So be aware of any leaked firmwares and only use official ones or those confirmed by chain fire for be working...
Sent from my GT-I9100 using xda app-developers app
tylerdurden83 said:
You seem to be saying that LPM has a safe kernel, while in fact it hasn't. There are even reports of people bricking their s2 by using the official recovery (not cwm) under stock lpm kernel.
Click to expand...
Click to collapse
Really?
Hmmm I may have to look into branching siyah sooner than i expected. He has a lot on his plate atm, so will look into this. I have never built a kernel but afaik its relatively simple. Its the extra features that people want that is the time consumer. Well I would recommend that users flash the recovery that I have given the link to and utilise that.
If that is the case they should be able to run the LQ5 kernel and flash that recovery? I have just contacted chainfire first to give cred which I think a lot of us forget that he is a dev and we all use his work on this forum. Just because its mainstream doesn;t mean it should be forgotten about Anyway I have enquired about the recovery and wipe proceedure compared to the standard recovery wipe proceedure and I will report back here when/if I hear back.
Right now I am going to flash back to LQ5 and custom recovery
River99 said:
Any of the newer firmwares than LQ5 seems to be very dangerous! Russian forums reported many people to have hard bricked their devices also whilst wiping data partition on lwm kernel...
So be aware of any leaked firmwares and only use official ones or those confirmed by chain fire for be working...
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
From my understanding its the wipe procedure. So if that is fine on CF-root because of the custom recovery then shouldn't we be encouraging more people to flash CF-root?
Jarmezrocks said:
Your on LQ5, you may want to ditch the kernel and run with LPM man. Its the wipe script that is in the recovery that will corrupt your eMMC. Not just the stupid .PIT file that it came with + stupid people trying to restore from a custom kernel after the repartition. Both are issues with LQ5.
Attached is the LPM ZImage + CWM apk. Use CWM apk by chainfire to flash the zImage. Then flash this
http://download.chainfire.eu/202/CF-Root/SGS2/CF-Root-SGS2_XX_OXA_LQ5-v5.6-CWM5.zip
That will give you root and recovery too DO NOT WIPE ON THE CURRENT LQ5 KERNEL!!
Click to expand...
Click to collapse
Great. But somewhere i still fear after cwm problem with lq5. I am on stock lq5 firmware & kernel. How to safely go about it.
Phone: XXLQ5 (Android 4.0.4)
Modem: XXLQ6
Kernel: Stock (unrooted)
Launcher: Apex 1.2.4
Jarmezrocks said:
Really?
Hmmm I may have to look into branching siyah sooner than i expected. He has a lot on his plate atm, so will look into this. I have never built a kernel but afaik its relatively simple. Its the extra features that people want that is the time consumer. Well I would recommend that users flash the recovery that I have given the link to and utilise that.
If that is the case they should be able to run the LQ5 kernel and flash that recovery? I have just contacted chainfire first to give cred which I think a lot of us forget that he is a dev and we all use his work on this forum. Just because its mainstream doesn;t mean it should be forgotten about Anyway I have enquired about the recovery and wipe proceedure compared to the standard recovery wipe proceedure and I will report back here when/if I hear back.
Right now I am going to flash back to LQ5 and custom recovery
Click to expand...
Click to collapse
Yes some have bricked in lpm too. Have heard this from from russian forum.
Phone: XXLQ5 (Android 4.0.4)
Modem: XXLQ6
Kernel: Stock (unrooted)
Launcher: Apex 1.2.4
I get a solid 2 days from Wanamlite v12 (4.03 LPG) with siyah 3.3.2+ (LP9)
Sent from my Xoom using XDA Premium HD app
tariq2kn said:
Great. But somewhere i still fear after cwm problem with lq5. I am on stock lq5 firmware & kernel. How to safely go about it.
Phone: XXLQ5 (Android 4.0.4)
Modem: XXLQ6
Kernel: Stock (unrooted)
Launcher: Apex 1.2.4
Click to expand...
Click to collapse
Well get off the stock recovery is what I am saying!!! Get off it now!! Your at risk right now. Just cause you flashed it and didn't get the brick doesn't mean you won't. It is when you do a factory data reset that you **could** get a corrupted eMMC. Doesn't mean you will...just means that at the moment you are at risk if you ever do a reset on your phone in recovery.
see the link in my second post to chainfires website. Download that LQ5 CF-root and flash that via Odin.
This adds a custom recovery 5.x to your phone and it should by pass the stock kernel 3e recovery when you boot into it via the CWManager app (this is in the attachment) I will put it in there sepperated now for users like your self that already have LQ5. If you want to boot into recovery you do so via this app only. It will take you to the clockwork recovery console not the standard 3e one that comes with the kernel and firmware.
I hope this all makes sense now?
Rone1986 said:
I get a solid 2 days from Wanamlite v12 (4.03 LPG) with siyah 3.3.2+ (LP9)
Sent from my Xoom using XDA Premium HD app
Click to expand...
Click to collapse
Yeah I know this. It has a lot to do with other factors like the modem and network that you are on also. Wanamlite is a great ROM too btw. This was just for 4.04 as its not really relevant to 4.03
Jarmezrocks said:
See the attached screen capture taken 2 min ago. LPM kernel is working flawlessly with LQ5. Wipes/ backup/ restores etc. Via the root and recovery thanks to Chainfire.
I used the LQ5 updated root flash via Chainfires CWM app to patch the LPM kernel.
ROM will be updated to DarkyROM very soon, so make sure you visit to check it out.
1day 9hours and 11% discharging. 48% is screen so usage is about right seeming we sleep half the time LOL Me a bit more so than most others haha. Damn Narcolepsy
James
Click to expand...
Click to collapse
"1day 9hours and 11% discharging. 48% is screen" dosn't say anything!
I can easily get much more than this if I don't use my phone !!!
Screen on time?
Brightness?
Mittaa said:
dosn't say anything!
I can easily get much more than this if I don't use my phone !!!
Screen on time?
Brightness?
Click to expand...
Click to collapse
Just checked now and my screen brightness was the default 70% as it was when I flashed. I haven't changed it because I am currently working on getting the Jkay Toggles and framework translated over to 4.04. I usually have it set to automatic.
Screen on time: 4hours 29m and 44s
It was more a note for those that are looking how the standard kernel runs. I know custom kernels run a heap better. I would be on siyah kernel if I could run it but I can't. If you compare kernels custom 4.03 to stock 4.04 you aint really comparing apples with apples are you? I hate apples now so I should change my lingo
But you get the jist.
How did I know this was going to turn into critics paradise as per usual? This forum is full of em. I hate CRITICS MORE THAN APPLE!
@ Jarmezrocks
Which modem are you using dear?
Is CWManager App really needed when cfroot 5.6 has already been flashed via odin?
Below is the procedure I think maybe correct:
I) Flash CF-Root LQ5 5.6 via odin in download mode.
II) Flash LPM Kernel via odin in download mode.
No wipe or factory reset shall be done anywhere.
Is it correct?
Phone: XXLQ5 (Android 4.0.4)
Modem: XXLQ6
Kernel: Stock (unrooted)
Launcher: Apex 1.2.4
Jarmezrocks said:
Just checked now and my screen brightness was the default 70% as it was when I flashed. I haven't changed it because I am currently working on getting the Jkay Toggles and framework translated over to 4.04. I usually have it set to automatic.
Screen on time: 4hours 29m and 44s
It was more a note for those that are looking how the standard kernel runs. I know custom kernels run a heap better. I would be on siyah kernel if I could run it but I can't. If you compare kernels custom 4.03 to stock 4.04 you aint really comparing apples with apples are you? I hate apples now so I should change my lingo
But you get the jist.
How did I know this was going to turn into critics paradise as per usual? This forum is full of em. I hate CRITICS MORE THAN APPLE!
Click to expand...
Click to collapse
Thats good :good:
3 hours screen on at 30-50 brightness can last a full day for me on my current firmware (no wifi, no BT, no gaming).
I have rooted the LQ5 with CF-Root LQ5 v5.6 via odin & flashed the attached LPM kernel through CWM Manager.It's working fine.
One thing is that when i opened cwm manager after reboot, it says this version should be used with cf-root 5.0. Some features will be disabled.
I don't think it is going to affect anything as it is about the software features.
Phone: XXLQ5 (Android 4.0.4)
Modem: XXLQ6
Kernel: XWLPM
Root: CF-Root LQ5 v5.6
Launcher: Apex 1.2.4
I am currently running a Nexus 4 with PARANOIDANDROID 2.99b+ (Feb03) flashed with the Franco r53 kernel.
I wanted to try out the Matrix 6.5 kernel on my phone and was wondering if there is any step that I need to perform before flashing the new kernel. I found the following post that includes a cleaner script: http://forum.xda-developers.com/showthread.php?t=2121701
I was wondering if this is required or if we can simply flash the matrix kernel over the franco kernel. Would that be possible?
Also, would it be possible to flash the new PARANOIDANDROID release (assuming it includes a kernel) then flash the matrix kernel over that? Would this cause problems because the cleaner script was not run before flashing the new rom which has its own kernel?
Was not sure how it exactly works and was hoping that someone would be able to help me out and clarify the process.
Currently, I think your safest option is to flash the newest version of the PA rom and gapps and then flash the kernel that you want. Because a lot of the kernel developers are are making changes to things that may not be overwriten when flashing a kernel from a different developer. For example I think that franco makes changes to the ramdisk that some other kernel devs don't touch.
linelock said:
Currently, I think your safest option is to flash the newest version of the PA rom and gapps and then flash the kernel that you want. Because a lot of the kernel developers are are making changes to things that may not be overwriten when flashing a kernel from a different developer. For example I think that franco makes changes to the ramdisk that some other kernel devs don't touch.
Click to expand...
Click to collapse
Cool, so I guess when we flash the rom and gapps it resets any changes that may have been made by Franco's kernel (or any other kernel for that matter). Hence, running any cleaner script is not required. Is this true?
Also, when flashing the kernel I wipe cahce, wipe dalvik, flash kernel, reboot. I read in another post that you should let it run for 10-15 minutes then reboot again to let the kernel "settle in". Is this actually required?
if you are running franco kernel, you want to either reflash your rom then the kernel, or flash the roms boot.img then the kernel. coming from other kernels, just flash the new kernel on top. the reason being that franco kernel uses its own ramdisk(and you want your roms ramdisk).
---------- Post added at 03:57 PM ---------- Previous post was at 03:56 PM ----------
jauwad.arshad said:
Cool, so I guess when we flash the rom and gapps it resets any changes that may have been made by Franco's kernel (or any other kernel for that matter). Hence, running any cleaner script is not required. Is this true?
Also, when flashing the kernel I wipe cahce, wipe dalvik, flash kernel, reboot. I read in another post that you should let it run for 10-15 minutes then reboot again to let the kernel "settle in". Is this actually required?
Click to expand...
Click to collapse
you do not wipe anything when flashing kernels, there is no need. wiping cache or dalvik has nothing to do with kernels, its just a misconception that keeps getting passed along.
simms22 said:
if you are running franco kernel, you want to either reflash your rom then the kernel, or flash the roms boot.img then the kernel. coming from other kernels, just flash the new kernel on top. the reason being that franco kernel uses its own ramdisk(and you want your roms ramdisk).
---------- Post added at 03:57 PM ---------- Previous post was at 03:56 PM ----------
you do not wipe anything when flashing kernels, there is no need. wiping cache or dalvik has nothing to do with kernels, its just a misconception that keeps getting passed along.
Click to expand...
Click to collapse
Awesome, thanks for the info. So I guess it is a safe practice to flash the boot.img (or just update the rom if you were going to anyways) and then flash the kernel.
jauwad.arshad said:
Awesome, thanks for the info. So I guess it is a safe practice to flash the boot.img (or just update the rom if you were going to anyways) and then flash the kernel.
Click to expand...
Click to collapse
yup. i tell people to just reflash their rom(and gapps) with the kernel, then reboot if they were running franco kernel. but its safe to flash the stock or your roms boot.img also, then the kernel.
simms22 said:
then reboot if they were running franco kernel.
Click to expand...
Click to collapse
I am not sure what you meant by that.
What I get out of all of this, is that if I want to try a new kernel this is what I should do in recovery:
Factory reset + wipe cache + dalvik cache
Flash new rom (PA rom in my example)
Flash gapps
Flash custom kernel if desired (Franco's kernel in my example)
Reboot
Is that correct or am I missing a step/doing something extra?
You might notice if you update your ROM (e.g. the next time PA gets updated, or if you switch to CM nightlies) that during the flash, the kernel will be overwritten - no matter which kernel you are using.
For example, flashing CM installs the CM kernel - regardless of if I was running Franco's before that. This is why apps like CyanDelta (which supports incremental updates to the ROM, but also the flashing of zips *after* flashing the ROM) are so handy. Every three days, I flash the latest CM nightly, and then Franco's kernel. If I left Franco's kernel off the CyanDelta list, the phone would be using the latest CM kernel after the flash.
EDIT: Your steps look good, if not a little bit overly protective. For instance, I don't think a full factory reset is required to test out a different kernel, generally speaking. Obviously, it wouldn't hurt to do... just takes time.
twitchcity said:
You might notice if you update your ROM (e.g. the next time PA gets updated, or if you switch to CM nightlies) that during the flash, the kernel will be overwritten - no matter which kernel you are using.
For example, flashing CM installs the CM kernel - regardless of if I was running Franco's before that. This is why apps like CyanDelta (which supports incremental updates to the ROM, but also the flashing of zips *after* flashing the ROM) are so handy. Every three days, I flash the latest CM nightly, and then Franco's kernel. If I left Franco's kernel off the CyanDelta list, the phone would be using the latest CM kernel after the flash.
EDIT: Your steps look good, if not a little bit overly protective. For instance, I don't think a full factory reset is required to test out a different kernel, generally speaking. Obviously, it wouldn't hurt to do... just takes time.
Click to expand...
Click to collapse
That is pretty cool. Would that same app work on the PA rom or is it just for CM nightly builds?
Yeah, I am doing the factory reset because its a new version of the PA rom. I prefer not to simply flash over my current rom.
If you're running the latest PA on a mako, just get their 'contrasty' kernel and no need for your voodoo rituals
I am currently on franco kernel milestone 2 and want to try trinity kernel.
I have taken a 'back-up' of the stock kernel on the franco kernel updater app before i flashed franco.
Can I now restore my phone to stock kernel using this back-up and then flash trinity?
Will this work?
auto freak said:
I am currently on franco kernel milestone 2 and want to try trinity kernel.
I have taken a 'back-up' of the stock kernel on the franco kernel updater app before i flashed franco.
Can I now restore my phone to stock kernel using this back-up and then flash trinity?
Will this work?
Click to expand...
Click to collapse
you can. or you can just reflash your rom and trinity, dont wipe a single thing. just flash the rom, kernel, then reboot.
jauwad.arshad said:
I am not sure what you meant by that.
What I get out of all of this, is that if I want to try a new kernel this is what I should do in recovery:
Factory reset + wipe cache + dalvik cache
Flash new rom (PA rom in my example)
Flash gapps
Flash custom kernel if desired (Franco's kernel in my example)
Reboot
Is that correct or am I missing a step/doing something extra?
Click to expand...
Click to collapse
Only if you have franco now and switch to another kernel. So if you want to flash franco you don't have to wipe anything.
Hi, thanks to this forum finally i have hyperion 9 on baseband DDMD1, kernel 2.6.35.7 DELL227 #1, KST 2013...
i want to change it to CM 11...should i flash the cyanogen 11 file direclty over it? i read the instructions but can not understand it.
i have not flashed any kernel on my device... any help will be much appreciated...
and thanks too much in advanced,, this forum helped me in past.
pappupadan said:
Hi, thanks to this forum finally i have hyperion 9 on baseband DDMD1, kernel 2.6.35.7 DELL227 #1, KST 2013...
i want to change it to CM 11...should i flash the cyanogen 11 file direclty over it? i read the instructions but can not understand it.
i have not flashed any kernel on my device... any help will be much appreciated...
and thanks too much in advanced,, this forum helped me in past.
Click to expand...
Click to collapse
You must first flash the cm11 kernel that contains CWM6 either through cwm5 (if you are on stock kernel and have stock recovery flash a temporary CWM zip) or use the odin version and flash via odin (put it in pda section) - links on rom thread
Once that has been done reboot to recovery and make sure you have cwm6
Then format system data and cache
Mount system data cache
Flash rom zip
marcussmith2626 said:
You must first flash the cm11 kernel that contains CWM6 either through cwm5 (if you are on stock kernel and have stock recovery flash a temporary CWM zip) or use the odin version and flash via odin (put it in pda section) - links on rom thread
Once that has been done reboot to recovery and make sure you have cwm6
Then format system data and cache
Mount system data cache
Flash rom zip
Click to expand...
Click to collapse
you mean i need to flash this one http://forum.xda-developers.com/galaxy-y/development/kernel-getux-kernel-v1-beta-2-t2907168
then CM11 RC11 from here http://download.androidarmv6.org/_builds/totoro/stable/
is there any risk of bricking?
thank you very much...
pappupadan said:
you mean i need to flash this one http://forum.xda-developers.com/galaxy-y/development/kernel-getux-kernel-v1-beta-2-t2907168
then CM11 RC11 from here http://download.androidarmv6.org/_builds/totoro/stable/
is there any risk of bricking?
thank you very much...
Click to expand...
Click to collapse
That kernel is an unofficial kernel not from the dev of cm11 for this phone so no support from
him can be given if you use that one but you can if you want
The official kernel with cmw6 is located here - the zip is for flashing via CWM and the tar is for odin - the choice is yours
https://www.mediafire.com/folder/bj3a19sdm5yre/totoro
The rom is located
http://download.androidarmv6.org/_builds/totoro/
And the rom thread with instructions is located
http://forum.xda-developers.com/showthread.php?t=2766229
If done wrong you can soft brick your phone but can be sorted with a simple flashing of stock rom via odin - link to my firmware thread is in my signature
I install CM11 over H9 directly by first flashing ClockworkMod v6.0.5.3 & then latest full OTA build for totoro (androidarmv6.org)
CM11 have its own kernel.
thank you very very much marcus smith... i installed it yesaterday,,, everything is fine. flashing went successful.
marcussmith2626 said:
That kernel is an unofficial kernel not from the dev of cm11 for this phone so no support from
him can be given if you use that one but you can if you want
The official kernel with cmw6 is located here - the zip is for flashing via CWM and the tar is for odin - the choice is yours
https://www.mediafire.com/folder/bj3a19sdm5yre/totoro
The rom is located
http://download.androidarmv6.org/_builds/totoro/
And the rom thread with instructions is located
http://forum.xda-developers.com/showthread.php?t=2766229
If done wrong you can soft brick your phone but can be sorted with a simple flashing of stock rom via odin - link to my firmware thread is in my signature
Click to expand...
Click to collapse
I have hell fusion kernel with hyperion 9 which is bricked and boots into recovery.how to falsh cm11 now.how to get stock kernel(someone said I should be on kernel for cm11).....please help
–NigthFury– said:
I have hell fusion kernel with hyperion 9 which is bricked and boots into recovery.how to falsh cm11 now.how to get stock kernel(someone said I should be on kernel for cm11).....please help
Click to expand...
Click to collapse
Please don't post the same question multiple times - Iv answered you in another thread & please read the instructions on the cm11 thread - everything is there for you - you only have to read it