I've seen a lot of posts of people saying they are using AOKP M6 (last ICS build from the team) on their Notes and it's awesome. Also, saw a couple of YouTube videos, I remember.
Okay... what the hell? I cannot find AOKP M6 for the Note here, on XDA. Only ROMs based on AOKP build 40 (before Milestone 6), with themes / tweaks included & stuff...
Maybe I'm blind, maybe I'm stupid... I want someone to give me a link to a thread where I can find AOKP M6 for the Note! Please
Formhault said:
I've seen a lot of posts of people saying they are using AOKP M6 (last ICS build from the team) on their Notes and it's awesome. Also, saw a couple of YouTube videos, I remember.
Okay... what the hell? I cannot find AOKP M6 for the Note here, on XDA. Only ROMs based on AOKP build 40 (before Milestone 6), with themes / tweaks included & stuff...
Maybe I'm blind, maybe I'm stupid... I want someone to give me a link to a thread where I can find AOKP M6 for the Note! Please
Click to expand...
Click to collapse
http://goo.im/devs/aokp/n7000
there u go..
sahilarora2003 said:
http://goo.im/devs/aokp/n7000
there u go..
Click to expand...
Click to collapse
It's funny, cause I went on the AOKP website and didn't see the Galaxy Note listed :/
What kernel does that ROM use?
Also, how am I supposed to flash it? I'm on RocketROM v7, which has LQ3 kernel. Can I flash Abyss 4.2 then wipe then flash AOKP?
Formhault said:
It's funny, cause I went on the AOKP website and didn't see the Galaxy Note listed :/
What kernel does that ROM use?
Also, how am I supposed to flash it? I'm on RocketROM v7, which has LQ3 kernel. Can I flash Abyss 4.2 then wipe then flash AOKP?
Click to expand...
Click to collapse
First Reboot into recovery.
Flash JBRoid Cleaner.
Flash Abyss 4.2
Reboot Recovery. U'll have Redpill Recovery.
Wipe Cache/Dalvik/Data.
Flash Milestone 6.
Reboot System.
I always use these steps..and worked flawlessly....
sahilarora2003 said:
First Reboot into recovery.
Flash JBRoid Cleaner.
Flash Abyss 4.2
Reboot Recovery. U'll have Redpill Recovery.
Wipe Cache/Dalvik/Data.
Flash Milestone 6.
Reboot System.
I always use these steps..and worked flawlessly....
Click to expand...
Click to collapse
Alright. You're the... I dunno... 5th person who confirms this method to me? I guess I'll make a TiBu backup and do as you said. I really want AOKP. Thanks
Let's just hope I don't get superbricked
Also, any suggestions on what kernel I should flash afterwards? Or should I stick to the one used in AOKP?
Formhault said:
Alright. You're the... I dunno... 5th person who confirms this method to me? I guess I'll make a TiBu backup and do as you said. I really want AOKP. Thanks
Let's just hope I don't get superbricked
Also, any suggestions on what kernel I should flash afterwards? Or should I stick to the one used in AOKP?
Click to expand...
Click to collapse
As many of the members facing reboot issues , I strongly recommend To flash CM9. Im using it with no problems whatsoever.
Don't worry...It is the safest method as Abyss 4.2 uses GB kernel which is safe to flash AOKP....
sahilarora2003 said:
As many of the members facing reboot issues , I strongly recommend To flash CM9. Im using it with no problems whatsoever.
Click to expand...
Click to collapse
I've been using AOKP on the SGS2 and the Nexus, and I grew to love it. Now I want to at least give it a shot on my Note. I like RocketROM, too, but... there are a few things about TouchWiz which turn me off.
If CM9 had ROM Control like AOKP, I'd go for it .
-----
How about Gapps? I believe I need to flash a specific package for 1280x800 resolution? Or... it's not really required, so I can flash any Gapps from the AOKP website...?
sahilarora2003 said:
Don't worry...It is the safest method as Abyss 4.2 uses GB kernel which is safe to flash AOKP....
Click to expand...
Click to collapse
So... only the KERNEL matters when wiping? Then I don't understand why people recommend flashing a whole GB ROM before wiping, even via Odin. It would take much more time than flashing just Abyss...
Formhault said:
I've been using AOKP on the SGS2 and the Nexus, and I grew to love it. Now I want to at least give it a shot on my Note. I like RocketROM, too, but... there are a few things about TouchWiz which turn me off.
If CM9 had ROM Control like AOKP, I'd go for it .
-----
How about Gapps? I believe I need to flash a specific package for 1280x800 resolution? Or... it's not really required, so I can flash any Gapps from the AOKP website...?
So... only the KERNEL matters when wiping? Then I don't understand why people RECCOMEND flashing a whole GB ROM before wiping.
Click to expand...
Click to collapse
My Bad.. U also have to flash Gapps after flashing Rom.. Here is the link... :- http://goo.im/gapps/gapps-ics-20120429-signed.zip
Flashing a GB rom is recommended because it is safe to flash over it as it is proved be safe of bricking your device...
sahilarora2003 said:
Flashing a GB rom is recommended because it is safe to flash over it as it is proved be safe of bricking your device...
Click to expand...
Click to collapse
So... wiping even after flashing the cleaning script + Abyss can be dangerous? :/
sahilarora2003 said:
My Bad.. U also have to flash Gapps after flashing Rom.. Here is the link... :- http://goo.im/gapps/gapps-ics-20120429-signed.zip
Click to expand...
Click to collapse
Hmm... that seems to be the same package I used on the Nexus. So it's not resolution-dependant.
-----
Was hoping XDA would automatically merge these two posts... Oh well...
Formhault said:
So... wiping even after flashing the cleaning script + Abyss can be dangerous? :/
Click to expand...
Click to collapse
No need to Wipe after JBRoid cleaning script as it is already included in the script... But as u asked it is not dangerous..
sahilarora2003 said:
No need to Wipe after JBRoid cleaning script as it is already included in the script... But as u asked it is not dangerous..
Click to expand...
Click to collapse
Yeah, that's what I was asking - whether it's dangerous or not, not if I need to wipe in between...
I'm safe. Hurray! Thanks . I needed 5+ confirmations in order to have the guts to try flashing again, haha.
Okay, so Titanium Backup was finally done backing up and verifying the backup.
-I rebooted into Recovery (a version that wasn't touch-driven - it was flashed automatically with RocketROM, I believe).
-I flashed the cleaning script.
-I flashed Abyss 4.2 kernel.
-I rebooted the recovery. It wasn't RedPill, but a touch-driven version of CWM. I guess the package I had wasn't the one with RedPill Custom Icon or whatever it's called .
-I wiped everything.
-I flashed AOKP and Gapps.
-I rebooted.
IT BOOTED UP ! YAY !
You can't imagine my heart beat rate, lol.
Formhault said:
Yeah, that's what I was asking - whether it's dangerous or not, not if I need to wipe in between...
I'm safe. Hurray! Thanks . I needed 5+ confirmations in order to have the guts to try flashing again, haha.
Okay, so Titanium Backup was finally done backing up and verifying the backup.
-I rebooted into Recovery (a version that wasn't touch-driven - it was flashed automatically with RocketROM, I believe).
-I flashed the cleaning script.
-I flashed Abyss 4.2 kernel.
-I rebooted the recovery. It wasn't RedPill, but a touch-driven version of CWM. I guess the package I had wasn't the one with RedPill Custom Icon or whatever it's called .
-I wiped everything.
-I flashed AOKP and Gapps.
-I rebooted.
IT BOOTED UP ! YAY !
You can't imagine my heart beat rate, lol.
Click to expand...
Click to collapse
Congrats. Welcome to the world of AOKP.. Cheers !!!
lol
shouldnt the flashing of the cleaning script be done from a GB kernel instead of an ICS kernel since it is used before the abyss kernel is installled ?
rraaka said:
shouldnt the flashing of the cleaning script be done from a GB kernel instead of an ICS kernel since it is used before the abyss kernel is installled ?
Click to expand...
Click to collapse
Nah...Cleaning script is to clean the effects that ur previous kernel had on your device...After flashing the script use abyss to have Red Pill Recovery..I use it all the tym before flashing any ROM....No Problems Yet....
thanks sahil, i was just wondering coz the script does some amount of wiping that too on an ics kernel !?
rraaka said:
thanks sahil, i was just wondering coz the script does some amount of wiping that too on an ics kernel !?
Click to expand...
Click to collapse
Ur Welcome!!! Don't do factory reset with ICS kernel as it can be dangerous..
sahilarora2003 said:
Nah...Cleaning script is to clean the effects that ur previous kernel had on your device...After flashing the script use abyss to have Red Pill Recovery..I use it all the tym before flashing any ROM....No Problems Yet....
Click to expand...
Click to collapse
I never got RedPill recovery after flashing Abyss! Wtf?
Sent from my GT-N7000
sahilarora2003 said:
Ur Welcome!!! Don't do factory reset with ICS kernel as it can be dangerous..
Click to expand...
Click to collapse
Not true entirely.
If you factory reset from a *safe* kernel, it cannot* brick your device if the erase_emmc_command is removed. If you're doing it from Official/Stock Samsung ICS Kernel, then yeah you'll brick your device.
You're right that a Clean Install is best.
Though you need to flash Abyss first.
Now its safe, use JBroid to delete the low-level stuff you've accumulated.
You need to Flash Abyss again, otherwise flash a *safe* custom kernel.
Then flash the ROM of your choosing, which will also flash a new kernel (cm9 based).
You can then flash the kernel of your choosing (eg/ ANiDROID, thor etc etc).
I know it gets redundant, but having a nice clean install the first time fixes 80% of bugs.
I'm learning that the HARD way
Kangal said:
Not true entirely.
If you factory reset from a *safe* kernel, it cannot* brick your device if the erase_emmc_command is removed. If you're doing it from Official/Stock Samsung ICS Kernel, then yeah you'll brick your device.
You're right that a Clean Install is best.
Though you need to flash Abyss first.
Now its safe, use JBroid to delete the low-level stuff you've accumulated.
You need to Flash Abyss again, otherwise flash a *safe* custom kernel.
Then flash the ROM of your choosing, which will also flash a new kernel (cm9 based).
You can then flash the kernel of your choosing (eg/ ANiDROID, thor etc etc).
I know it gets redundant, but having a nice clean install the first time fixes 80% of bugs.
I'm learning that the HARD way
Click to expand...
Click to collapse
None of the ICS kernels can 100% gurantee you that it is safe. (My personal Experience).
Related
somewhere in the Note community i read about to dont do anything with the recovery when you are upgraded with the LPY .....Now i can see in the development forum that there is customs roms of the lpy rom??????
i want to flash the custom roms but i want to know if it safe and not to brick my loved NOte in the process
There is always a risk when doing any flashing on your phone.
If you want Rocket Rom v1 for example you can flash over LPY in cwm recovery and just wipe dalvik and cache. I did no problems.
They do advise to flash Abyss 4.2 or 3.9 redpill then flash the new rom from that kernel though. Depends how much risk you want to take. I also ran TeamMid 1.2 with no problems
not-i said:
There is always a risk when doing any flashing on your phone.
If you want Rocket Rom v1 for example you can flash over LPY in cwm recovery and just wipe dalvik and cache. I did no problems.
They do advise to flash Abyss 4.2 or 3.9 redpill then flash the new rom from that kernel though. Depends how much risk you want to take. I also ran TeamMid 1.2 with no problems
Click to expand...
Click to collapse
I wonder, would it be safer if I copy the files from the ROM /system/app and /system/framework into the phone?
lenrek said:
I wonder, would it be safer if I copy the files from the ROM /system/app and /system/framework into the phone?
Click to expand...
Click to collapse
Nope as soon as you start copying frameworks,your phone will reboot and there after,soft reboots....
When you start from /system,You will have lots of FC's and when copying tw,again reboots.
I'm on LPY, pre-rooted oficial version. I got superuser instaled but it isn't working. I don't have CWM instaled too. My question is, can i wipe from STOCK recovery all data and then flash just oficial LPY, without root permisions via ODIN?
krkojzla said:
I'm on LPY, pre-rooted oficial version. I got superuser instaled but it isn't working. I don't have CWM instaled too. My question is, can i wipe from STOCK recovery all data and then flash just oficial LPY, without root permisions via ODIN?
Click to expand...
Click to collapse
You can straight away flash LPY through pc odin.Stock recovery too is dangerous
vijai2011 said:
You can straight away flash LPY through pc odin.Stock recovery too is dangerous
Click to expand...
Click to collapse
And what about wipe? Factory reset? Can't do any?
krkojzla said:
And what about wipe? Factory reset? Can't do any?
Click to expand...
Click to collapse
As I said,stock recovery is also dangerous.so its risky to do wipe.
Ok, i got it. I'm asking this cause i'm not sure what will happen with all my apps? When i flash new stock rom via pcOdin, it gonna delete them or no? I do not need them by the way, but i'm just curious because i remember on my S2 when rom is flashed without wipe it always get some problems
Sent from my GT-N7000
krkojzla said:
Ok, i got it. I'm asking this cause i'm not sure what will happen with all my apps? When i flash new stock rom via pcOdin, it gonna delete them or no? I do not need them by the way, but i'm just curious because i remember on my S2 when rom is flashed without wipe it always get some problems
Sent from my GT-N7000
Click to expand...
Click to collapse
Its not goin to delete your apps....
krkojzla said:
Ok, i got it. I'm asking this cause i'm not sure what will happen with all my apps? When i flash new stock rom via pcOdin, it gonna delete them or no? I do not need them by the way, but i'm just curious because i remember on my S2 when rom is flashed without wipe it always get some problems
Sent from my GT-N7000
Click to expand...
Click to collapse
LPY is a non wipe rom, so it will upgrade and keep your existing apps etc
Now a new full wipe ICS roms has been released.LPF.
I will wait to see results for new rom. And how to wipe when it's too dangerous.
Sent from my GT-N7000
krkojzla said:
I will wait to see results for new rom. And how to wipe when it's too dangerous.
Sent from my GT-N7000
Click to expand...
Click to collapse
No other go than taking risk
hi,
after reading so many post on rooting and secure kernels I am still unsure if I lose root, if I flash abyss kernel after beeing rooted (Super Su Busybox).
As I want to do back ups as well as restores I think I need a secure Kernel after rooting. (I am on stock ICS LPF rooted).
Again I am not installing any MOD or ROMS just a rooted Stock ICS.
RbbCHan said:
hi,
after reading so many post on rooting and secure kernels I am still unsure if I lose root, if I flash abyss kernel after beeing rooted (Super Su Busybox).
As I want to do back ups as well as restores I think I need a secure Kernel after rooting. (I am on stock ICS LPF rooted).
Again I am not installing any MOD or ROMS just a rooted Stock ICS.
Click to expand...
Click to collapse
No you will not lose root if you flash abyss kernel.
RbbCHan said:
hi,
after reading so many post on rooting and secure kernels I am still unsure if I lose root, if I flash abyss kernel after beeing rooted (Super Su Busybox).
As I want to do back ups as well as restores I think I need a secure Kernel after rooting. (I am on stock ICS LPF rooted).
Again I am not installing any MOD or ROMS just a rooted Stock ICS.
Click to expand...
Click to collapse
Do not use abyss as safe kernel for your ics it will not boot up. Use speedmod k3-6 or goku as a safe kernel. Use abyss only for wiping purposes and then flash a custom rom.
thx, that's important info. will try to find those kernels.
If you do have a link just in your hands would be nice if you could copy it for me.
TIA for your efforts
RC
jonpaslim said:
Do not use abyss as safe kernel for your ics it will not boot up. Use speedmod k3-6 or goku as a safe kernel. Use abyss only for wiping purposes and then flash a custom rom.
Click to expand...
Click to collapse
Do you mean to use only stock kernel and use abyss only when trying to install any custom ROMs. Is it not possible to use CWM instead of abyss kernel to flash the custom rom. is abyss kernel is just another method to root the note?
Hi,
I think I have problem here...
I have official ICS 4.0.3 (XXLQ2) and CF-Root,
I just flashed with abyss kernel and phone is not booting....
How can I flash to another kernel? I tried Volume down, Power and home button, but I got in download mode...
and also, which is safe kernel to use?
I flashed CF-root kernel by ODIN and now it boots normally
Basically Abyss is kernel for GB. That is the reason why every one advise when ICS rom, if you flash Abyss, do not leave CWM but reboot (not device) but the recovery. and after wiping flash the custom ICS immediately. I suggest you go back to GB and upgrade to ICS officially, and get rooted. (but remember ICS stock ROMs are not safe for backup, specially restoring, since you mentioned backups)
giokiborg said:
Hi,
I think I have problem here...
I have official ICS 4.0.3 (XXLQ2) and CF-Root,
I just flashed with abyss kernel and phone is not booting....
How can I flash to another kernel? I tried Volume down, Power and home button, but I got in download mode...
and also, which is safe kernel to use?
I flashed CF-root kernel by ODIN and now it boots normally
Click to expand...
Click to collapse
Use speedmod k3-6 for safe ics custom kernel. http://forum.xda-developers.com/showthread.php?t=1673072
Here is goku kernel for ics. http://forum.xda-developers.com/showthread.php?t=1710937
Here is another ics kernel. http://forum.xda-developers.com/showthread.php?t=1749863
Download any ics rom u like,put in into external,after abyss full wipe,then install it from ex.sd.
Sent from my GT-N7000 using xda premium
Well, thanks for the various info, however, my problem is still not solved.
Just to avoid misunderstandings I say it again: I do not want to install a custom kernel or so. Just keep my stock ICS rooted. But.... of course I would like to have the possibility to make backups and restore. As this involves the risk of bricking my device, I want to install a Kernel, which is at least considered to be safe ( I know no guarantee at all).
So the advice from "Jonpaslim" seems to be the answer.
this brings me to another problem........ I am in China, so I can't download from File-sharing services, as they are blocked. i can download from drop box, box or any other server also from xda......but I couldn't find a usable link for the k3-6 or Goku. those files don't seem to be so big ones. I wonder, if it may be possible for s.o. here to upload to a private cloud like dropbox or box or sugar sync etc.. and give me the download link.
I thank you for all your efforts in advance
greetings from China
jonpaslim said:
Use speedmod k3-6 for safe ics custom kernel. http://forum.xda-developers.com/showthread.php?t=1673072
Here is goku kernel for ics. http://forum.xda-developers.com/showthread.php?t=1710937
Here is another ics kernel. http://forum.xda-developers.com/showthread.php?t=1749863
Click to expand...
Click to collapse
Thanks for reply, I already flashed k3-6
And I like it,
But, to be sure, is it prooved to be safe? I mean recovery, factory reset and the wipe is conformed to be safe? Or still use abyss kernel for CWM and wipe?
Sent from my GT-N7000 using xda app-developers app
giokiborg said:
Thanks for reply, I already flashed k3-6
And I like it,
But, to be sure, is it prooved to be safe? I mean recovery, factory reset and the wipe is conformed to be safe? Or still use abyss kernel for CWM and wipe?
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Sir u need to flash abyys just for full wipe not for flashing anything from cwm or cache partition and dalvik cache wipe...
Flash abyys just if u wanna make full wipe...
Sent from my GT-N7000 using xda premium
adamskoc said:
Sir u need to flash abyys just for full wipe not for flashing anything from cwm or cache partition and dalvik cache wipe...
Flash abyys just if u wanna make full wipe...
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Thanks for information,
but as I read SpeedMod kernel is safe for wiping too, but for extra safety I will use abyss kernel
giokiborg said:
Thanks for reply, I already flashed k3-6
And I like it,
But, to be sure, is it prooved to be safe? I mean recovery, factory reset and the wipe is conformed to be safe? Or still use abyss kernel for CWM and wipe?
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
This all i can say about the safety of speedmod, never i once read that somebody brick their phone by wiping on speedmod. I trust speedmod myself.
little help
guys one small but important help
i'm going to buy note in just few days probably tomrw
i will buy it on gb version
so what i want to know exactly
1. if i root the gb version with chainfire method of rooting (is it safe to go and keep the device brick bug free) or any other method should i follow
2. if i want to flash any of ics version first i have to flash abysskernel is it ok (means is it brick proof method)
3.abyss kernel is best for upgrade and downgrade and to do nandriod backup with full wipe and it does not brick the device, as much i have read about all this thing, is my knowledge about note to upgrade, downgrade is ok
4.after upgrading to any ics custom rom from gb version i have to keep rom on speedmod kernel is it totaly safe method, and in future if i want to downgrade from ics to gb again i have to flash abyss or same can be done by speedmod
5.speedmod kernel is safe to do full wipe or to flash any modification not the rom
or lastly should i keep my device on gb version without root and wait for expert dev or team samsung to provide us with best solution to keep our device bug free
plz guys appropriate answer will be appreciated
thanks in advance
tonyking123 said:
guys one small but important help
i'm going to buy note in just few days probably tomrw
i will buy it on gb version
so what i want to know exactly
1. if i root the gb version with chainfire method of rooting (is it safe to go and keep the device brick bug free) or any other method should i follow
2. if i want to flash any of ics version first i have to flash abysskernel is it ok (means is it brick proof method)
3.abyss kernel is best for upgrade and downgrade and to do nandriod backup with full wipe and it does not brick the device, as much i have read about all this thing, is my knowledge about note to upgrade, downgrade is ok
4.after upgrading to any ics custom rom from gb version i have to keep rom on speedmod kernel is it totaly safe method, and in future if i want to downgrade from ics to gb again i have to flash abyss or same can be done by speedmod
5.speedmod kernel is safe to do full wipe or to flash any modification not the rom
or lastly should i keep my device on gb version without root and wait for expert dev or team samsung to provide us with best solution to keep our device bug free
plz guys appropriate answer will be appreciated
thanks in advance
Click to expand...
Click to collapse
1. GB ROM,s are safe,
2. If you are upgrading from GB, you don't need abyss kernel, use it own kernel for wiping
3. You are right, abyss kernel is safest, because its a GB ketnel with its own CWM, but note, abyss does not boots ICS
4. Speedmod kernel is safe, but for extra safety use abyss kernel for up/down grading
5. It shoud be safe because buggy feature is disabled, but still I can not find solid confirmation, that hardbrik does not happened on this kernel after multiple .wipe and cache clearing, but, also, I didn't heard that hardbrik happened, so i will use abyss kernel for wiping before solid confirmation, that speedmod kernel is safe
Sent from my GT-N7000 using xda app-developers app
giokiborg said:
1. GB ROM,s are safe,
2. If you are upgrading from GB, you don't need abyss kernel, use it own kernel for wiping
3. You are right, abyss kernel is safest, because its a GB ketnel with its own CWM, but note, abyss does not boots ICS
4. Speedmod kernel is safe, but for extra safety use abyss kernel for up/down grading
5. It shoud be safe because buggy feature is disabled, but still I can not find solid confirmation, that hardbrik does not happened on this kernel after multiple .wipe and cache clearing, but, also, I didn't heard that hardbrik happened, so i will use abyss kernel for wiping before solid confirmation, that speedmod kernel is safe
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
thanks bro
i think i should keep it on gb
as i know and of course with your help i can upgrade my device but if i forgot by chance any important step i can brick my device as i have habit of upgrading b'coz i was having s2 before so its not so easy for me to stop upgrading note and i can brick it easily too
so gb with or without root is ok with me till i get appropriate solution of brickbug
thnaks for your help ma8
tonyking123 said:
thanks bro
i think i should keep it on gb
as i know and of course with your help i can upgrade my device but if i forgot by chance any important step i can brick my device as i have habit of upgrading b'coz i was having s2 before so its not so easy for me to stop upgrading note and i can brick it easily too
so gb with or without root is ok with me till i get appropriate solution of brickbug
thnaks for your help ma8
Click to expand...
Click to collapse
You welcome,
You can upgrade from GB to ISC with samsung Kies,(as i did) it should be safe, anyway, if something goes wrong, you still have valid warranty.
or, you can use abyss kernel and manually upgrade from cwm. (You can find thread, where all stock ICS rom's are listed,
Also, there are a lot of step-by-step instructions on this forum or you can find also video toutorial on youtube or rootgalaxynote.com, just in case, not to forget anything)
I recomend upgrade to ICS, it's way batter than GB.
But after upgrade, you have to move to safe kernel, like speedmod, (already there are several safe roms for ics for example, last one:http://forum.xda-developers.com/showthread.php?t=1749863)
There are also methods to flush to safe kernel and root without having binary count increased.
Sent from my GT-N7000 using xda app-developers app
giokiborg said:
You welcome,
You can upgrade from GB to ISC with samsung Kies,(as i did) it should be safe, anyway, if something goes wrong, you still have valid warranty.
or, you can use abyss kernel and manually upgrade from cwm. (You can find thread, where all stock ICS rom's are listed,
Also, there are a lot of step-by-step instructions on this forum or you can find also video toutorial on youtube or rootgalaxynote.com, just in case, not to forget anything)
I recomend upgrade to ICS, it's way batter than GB.
But after upgrade, you have to move to safe kernel, like speedmod, (already there are several safe roms for ics for example, last one:http://forum.xda-developers.com/showthread.php?t=1749863)
There are also methods to flush to safe kernel and root without having binary count increased.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
i also love ics far best than gb
my s2 was on ics i never went to gb
i will try to upgrade in safer way
thanks for ur help bro
one thing more did your note have some prob on screen before or after upgrading to ics prob like pixelation, dark image, black or any other dot of different color
as i make my mind to purchase it some new problem stand in front of me and stopped me to buy it
tonyking123 said:
i also love ics far best than gb
my s2 was on ics i never went to gb
i will try to upgrade in safer way
thanks for ur help bro
one thing more did your note have some prob on screen before or after upgrading to ics prob like pixelation, dark image, black or any other dot of different color
as i make my mind to purchase it some new problem stand in front of me and stopped me to buy it
Click to expand...
Click to collapse
:good:
I noticed nothing you mentioned, screen is fine, black and other colors are also fine (at least as i can judge)
Also, I'll recomend GL_NOTECORE, Flash it with ODIN immediately after upgrade to official ICS, you will get root, CWM and MMC_CAP_ERASE disabled, also many extra tweaks and doubled 2D/3D performance
It's been a long time since I was last seen here, I've been busy working and studying, but now that it's vacation I'd very much like to update my ROM.
Currently I'm on Kernel version: 3.0.15-I9220ZCLP5-CL295568
And my ROM is ICS Stunner Beta 5.0 (yes, a pretty old one)
CWM: v5.0.2.7
So, the question is.. How do I get from that ROM, to a new, updated one?
I've been looking around but there are no specific guides on how to do this.. And I rooted mine back when I was on 2.3.4.
Honestly, I have no idea what I should get back to before putting a new ROM over it.
It'd be great if any of you could help me out describing how it's done! I would really appreciate the effort.
Thank you in advance, and hopefully I'll be able to get the best out of my Note again after this!
Use PC Odin to flash a stock gingerbread ROM, then root and install clockworkmod recovery, download and place whatever ROM you'd like to flash on your external sd card or internal memory, lastly boot into recovery (hold volume up + home + power buttons) and factory rest, wipe cache partition and dalvik cache then flash the ROM and reboot.
Sent From An Awesome Jelly Bean Galaxy Note
Can I go directly from a GB ROM to a ICS/JB ROM? Or do I need to flash some ICS update first?
Thank you for the explanation thus far!
Lanarix said:
Can I go directly from a GB ROM to a ICS/JB ROM? Or do I need to flash some ICS update first?
Thank you for the explanation thus far!
Click to expand...
Click to collapse
You can go directly from a rooted GB ROM to a ICS ROM. I wont recommend JB rom as of now as its a preview and not a daily driver.
No flashing of ICS repacks. Forget them. They are now history
Alright thank you.
By the way, I'm on the LP5 Kernel from Stunner ROM, which had alot of bricks when you flashed stuff.
Is this still an issue? If so.. How do I work around it? Because I don't want to brick it obviously.
Bump .
Nobody has an answer for me? Please?
Lanarix said:
Alright thank you.
By the way, I'm on the LP5 Kernel from Stunner ROM, which had alot of bricks when you flashed stuff.
Is this still an issue? If so.. How do I work around it? Because I don't want to brick it obviously.
Click to expand...
Click to collapse
I just explained to you the "100% safe way" to go from a stock ics rom to a custom rom in my last post. Stock gingerbread first through pc odin, root, install clockworkmod recovery, flash custom ics/jb rom of choice.
Lanarix said:
Nobody has an answer for me? Please?
Click to expand...
Click to collapse
Follow these instructions.
If you have CWM installed and your device have full root.
Reboot into CWM Recovery
Install a safe kernel (hardcore, notecore, cf root, franco etc) or flash abyss 4.2 redpill recovery.
Reboot recovery
Now full wipe for a clean install.(cache/dalvik /data)
Flash rom
Reboot system
Done.
Sent from my GT-N7000 using Xparent ICS Tapatalk 2
So I wouldn't even need to go back to GB if I follow your instructions sahilarora2003?
And you install a kernel just by flashing a .zip file right?
+1 I would hold off on the Jelly.....nothing exciting now. Give it a little more time....like another 3-5 updates I flashed CM10 and lasted 10mins before I came back to ICS. :good:
abhisahara said:
You can go directly from a rooted GB ROM to a ICS ROM. I wont recommend JB rom as of now as its a preview and not a daily driver.
No flashing of ICS repacks. Forget them. They are now history
Click to expand...
Click to collapse
Lanarix said:
So I wouldn't even need to go back to GB if I follow your instructions sahilarora2003?
And you install a kernel just by flashing a .zip file right?
Click to expand...
Click to collapse
Yes.
Sent from my GT-N7000 using Xparent ICS Tapatalk 2
Dont use wipe, restore,or factory reset in STOCK ICS kernel with your Recovery
Thank you for moderator make this sticky..
You know that this not new for us.. This problem exist in many samsung devices with ICS, i got this brick on my GT-N7000 and my device had a motherboard replacement because of that, and it seem our beloved tab definitely got this problem too..
im no dev..just an ordinary Windows and Unix User,not Using English as my Native
but I will update and summarize the issues in this thread until we got the fix about it..
If you already in ICS you need to read the whole thread from this to figure out what the problem is..
Emmc bugs is exist.. And if you need to know what kind of EMMC you have and the possibilty of brick, use this app from chainfire
This is suspected kernel and recovery build from ICS source with this bug if you try to wipe on this:
-any boot.img from stock ICS
-any recovery.img from stock ICS
-CWM 6.0.1.2 which is build from ICS source..
-update binary which is build from ICS source..
Click to expand...
Click to collapse
Discussion about this:
CWM 6.0.1.2-Risk of Brick start by fred_be9300 please report your issue about CWM here..
Official CM9 thread by kallt_kaffe , discussion about this start from page 107
Click to expand...
Click to collapse
After you read, this is my advice:
Dont use any wipe operation or something similar with that such as:
command "Format" in Edify script if you plan make a flashable zip
Nandroid Restore in CWM (build from ics source)
Using wipe with stock recovery in stock ICS boot.img(kernel)
Wiping in safe CWM in stock ICS boot.img
using wipe and nandroid restore with CWM from ICS source without mmc erase patch
using update-binary from ICS build..(compiled from ICS source without mmc erase patch)
Click to expand...
Click to collapse
Thanks for entropy512 who figure out this and make all samsung users more aware about flashing in ICS
And chainfire who makes the tools..
This is not about what version of cwm are used.. But what kind of kernel that recovery operates..
If the recovery execute the command in honeycomb kernel maybe its more safe then ICS kernel..
This is quote from chainfire itself
Chainfire said:
..... CWM is just a userspace program, nothing special(!) - so if the problem can happen in CWM, it can happen in Android....
Click to expand...
Click to collapse
this is possible solution if you want to flash, wipe or restore in ICS
First method: use recovery.img and boot.img with MMC_CAP_ERASE disable.. For that you must familiar with compiling kernel from the source..
Second method:Flashing recovery.img and boot.img from honeycomb, after installation done reboot to recovery and flash the ROM you desire..Remember, your ROM package must have boot.img and recovery.img too..
Click to expand...
Click to collapse
PLEASE BE CAREFULL UNTIL SOMEONE WITH MORE KNOWLEDGE SOLVE THIS FOR US..REMEMBER ITS JUST A WARNING! WHATEVER YOU DID, YOU OWN THAT RISK!!!
Some people are able to safely wipe and flash using affected kernels forever. Some people can wipe a few times before problems occur, some people have problems on their first wipe.
The number of people that broken kernels affect may only be 5-10% - but so far, there is no way to definitively determine that you are safe without putting your device at risk.
Click to expand...
Click to collapse
nandroid restore....are you serious?
orlandoxpolice said:
nandroid restore....are you serious?
Click to expand...
Click to collapse
Yep. And some zip file update-binary executables too (the edify format() function in the 'updater-script's).
Specifically those update-binary commands that were statically linked with the ICS version of the ext4 library.
Both of these operations (edify format() and nandroid partition restore) make use of the make_ext4fs() function. That function apparently changed in ICS to add a call to the eMMC erase functionality in the vigilant pursuit of security. However, that functionality is what tickles the eMMC fw bug with the 'bad' kernels (i.e. those that don't have the erase functionality disabled).
Oh what a tangled web we weave ...
Correct me if I'm wrong, but if i understand the problem and various threads correctly, the easiest and safest way to keep flashing ics based custom roms without fear of the emmc bug would be to always flash a #honeycomb kernel# in recovery each time #before# flashing any ics rom, right?
So if we have a flashable zip of galaxy tab 8.9 honeycomb kernel or even a pre-ics cm9 kernel, and keep it in our sdcard to be available to flash everytime, then we could, go into recovery, flash the bugless kernel, reboot in to recovery again, then safely flash an ics rom(even wipe data) , since it'll run according to the bugless k ernel (this is how we got the ics roms on our tabs in the first place, right)!
I'm no developer, so I don't know how to make one, but is there an existing flashable zip of the stock honeycomb kernel or a honeycomb based cm9 kernel in the existing threads(maybe motely's should be fine?) Or can a developer craft one for us?
This should work, right? Or an I mistake somewhere?
Sent from my Galaxy Nexus using xda premium
Jnn1 said:
This should work, right?
Click to expand...
Click to collapse
Unfortunately, no.
The problem isn't what you are flashing onto the device or what you are flashing over the top of. It's what you are flashing WITH. This is done with the recovery image (usually Stock or CWM).
The recovery image has its own kernel which is distinct from 'the kernel' used by the regular system. The recovery image is an entirely self-contained mini-system that is able to manipulate the contents of the device. Other than being able to read and write and format the rest of the device it shares no operational functionality with the rest of the system (well, other than the bootloader, of course ).
So if you had HC installed and wanted to flash JB you could still get bricked if your recovery image was using a 'bad' kernel.
This is why there have been recommendations to use CWM 5.x.y.z or 6.0.0.8 or lower. Someone says that 6.0.1.0 seems to work but KK and a few others have strongly recommended the lower versions.
HTH.
orlandoxpolice said:
nandroid restore....are you serious?
Click to expand...
Click to collapse
Nandroid restore is ONLY unsafe in a recovery that (itself) is built with a buggy ICS kernel. Version 6.0.0.8 and before are safe, because based on earlier GB kernel.
Also, update-binary (a copy of which exists in EVERY flashable zip) is ONLY unsafe IF built against buggy ICS kernel module... and if the updater-script in the same zip does a format()
I don't know if we've already seen dangerous update-binary in the wild... Mostly people don't recompile that, but endlessly reuse older ones. Still, you might want to check that next time you want to flash a zip. Or keep a safe update-binary available to inject into any zip you want to flash...
Disclaimer: this is my interpretation based on careful reading of many posts
This thread needs to be stickied!
I was on 6.0.1.2 but now went back to 6.0.1.0 but it looks like I'll be heading for 6.0.0.8
pseudoheld said:
This thread needs to be stickied!
I was on 6.0.1.2 but now went back to 6.0.1.0 but it looks like I'll be heading for 6.0.0.8
Click to expand...
Click to collapse
6.0.1.2 is the only one I compiled that uses the ICS kernel and I've removed the links to it some days ago. I don't remember compiling a 6.0.1.0 version but I could be wrong.
kallt_kaffe said:
6.0.1.2 is the only one I compiled that uses the ICS kernel and I've removed the links to it some days ago. I don't remember compiling a 6.0.1.0 version but I could be wrong.
Click to expand...
Click to collapse
Haha yeah you did it was in the cm9 thread as a test version. I had it running quite some time without any problems but decided to be on the safe side with 6.0.0.8
It think there was a 6.0.0.8 and a 6.0.0.8_alternate (version in file name) Then someone said one of these was saying 6.0.1.0 in the UI. AFAIR.
fred_be9300 said:
It think there was a 6.0.0.8 and a 6.0.0.8_alternate (version in file name) Then someone said one of these was saying 6.0.1.0 in the UI. AFAIR.
Click to expand...
Click to collapse
Right. The 6.0.0.8 in CM9 thread is 6.0.1.0 according to CWM recovery menu header.
tracid said:
Right. The 6.0.0.8 in CM9 thread is 6.0.1.0 according to CWM recovery menu header.
Click to expand...
Click to collapse
Oh well, then they are safe. I just didn't notice the version number had changed. Only the 6.0.1.2 version has the dangerous kernel.
So again...
1. I have the same eMMC chip revision number known to be brickable as per Chainfire's app.
2. I have been using CWM 5.5.0.4 only and never anything else.
3. I have flashed CM9 and AOSP Jelly Bean without bricking my device using CWM 5.5.0.4
Is it safe to assume that flashing the latest CM9 through CWM 5.5.0.4 will not result in a lifeless brick of a P7300?
Again, I am only asking for an assumption, not a definitive answer. Will hold nobody responsible.
de3pkeeper said:
Is it safe to assume that flashing the latest CM9 through CWM 5.5.0.4 will not result in a lifeless brick of a P7300?
Click to expand...
Click to collapse
should be safe!
it seems like only in conjunction with the newer cwm the brick can happen.
boscorama said:
Unfortunately, no.
The problem isn't what you are flashing onto the device or what you are flashing over the top of. It's what you are flashing WITH. This is done with the recovery image (usually Stock or CWM).
The recovery image has its own kernel which is distinct from 'the kernel' used by the regular system. The recovery image is an entirely self-contained mini-system that is able to manipulate the contents of the device. Other than being able to read and write and format the rest of the device it shares no operational functionality with the rest of the system (well, other than the bootloader, of course ).
So if you had HC installed and wanted to flash JB you could still get bricked if your recovery image was using a 'bad' kernel.
This is why there have been recommendations to use CWM 5.x.y.z or 6.0.0.8 or lower. Someone says that 6.0.1.0 seems to work but KK and a few others have strongly recommended the lower versions.
HTH.
Click to expand...
Click to collapse
Ah ... I see ... the recovery has it's own kernel that is a separate beast from the Rom kernel ... thanks for taking the time to kindly explain! And I'll make sure to stay on cwm 6.0.0.8 or lower!
Sent from my GT-P7310 using xda premium
Jnn1 said:
Correct me if I'm wrong, but if i understand the problem and various threads correctly, the easiest and safest way to keep flashing ics based custom roms without fear of the emmc bug would be to always flash a #honeycomb kernel# in recovery each time #before# flashing any ics rom, right?
So if we have a flashable zip of galaxy tab 8.9 honeycomb kernel or even a pre-ics cm9 kernel, and keep it in our sdcard to be available to flash everytime, then we could, go into recovery, flash the bugless kernel, reboot in to recovery again, then safely flash an ics rom(even wipe data) , since it'll run according to the bugless k ernel (this is how we got the ics roms on our tabs in the first place, right)!
I'm no developer, so I don't know how to make one, but is there an existing flashable zip of the stock honeycomb kernel or a honeycomb based cm9 kernel in the existing threads(maybe motely's should be fine?) Or can a developer craft one for us?
This should work, right? Or an I mistake somewhere?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yes you can..
We dont know from what kernel the bugs appear maybe from boot.img or from recovery.img..
So the safest way is flash the safe boot.img with safe recovery.img in one flashable.zip and then reboot to recovery again and flash the ROM you desire..
It works and tested by me..
There are 2 types of CWM 6.0.0.8 to choose at KK's CM9 thread. One is original and the other is alternate. So which one should we install. I am comfuse. I am currently on CM10 review. Is KK's CM10 kernel safe to use? Thanks
nexus_g said:
There are 2 types of CWM 6.0.0.8 to choose at KK's CM9 thread. One is original and the other is alternate. So which one should we install. I am comfuse. I am currently on CM10 review. Is KK's CM10 kernel safe to use? Thanks
Click to expand...
Click to collapse
The alternate version is for those folks that experience display issues with the regular one. You can use either one.
I don't know what kernel is in the CM10 preview. But as long as you use a 'safe' recovery for your wipes and resets you should be just fine.
boscorama said:
The alternate version is for those folks that experience display issues with the regular one. You can use either one.
I don't know what kernel is in the CM10 preview. But as long as you use a 'safe' recovery for your wipes and resets you should be just fine.
Click to expand...
Click to collapse
No, mine bricked not in recovery. But on first booting of new rom (unofficial cm9) with 3.1.0 kernel.
notz76 said:
No, mine bricked not in recovery. But on first booting of new rom (unofficial cm9) with 3.1.0 kernel.
Click to expand...
Click to collapse
The important thing here is what you used to install CM9.
Hi Guys,
Can someone guide / help me on how to upgrade my N7000 unit to JB and still rooted.
I'm still using GingerBread ROM with AbyssNote Kernel and already Rooted. Also installed with CWM
I want to know the step in upgrading it to Custom JB ROMs (MKalter JB, RocketRom)
Any suggestion will greatly appreciated.
Kindly refer on the images regarding details of my beloved SG Note
Thanks
You can not go from gingerbread to jb.
You need to download an ics rom ,like rocket with root and cwm. Do full wipe. Flash ics rom.
If that's cool download eybees jb
Full wipe and flash that .if root has gone open up SU and update the binary. The app will do this .just press on it .
Do not try skipping the ics . You will brick your phone ! Hope I helped
Sent from the man in Your attic.....
who says you can't go from gb to jb
i was on rooted stock gb and i flashed leaked stock jb over it and everything is working fine..
why do you think that ics has to be flashed ?
infact i did ask here at xda before flashing and nobody told me to flash ics over gb first
itsrijo said:
who says you can't go from gb to jb
i was on rooted stock gb and i flashed leaked stock jb over it and everything is working fine..
why do you think that ics has to be flashed ?
infact i did ask here at xda before flashing and nobody told me to flash ics over gb first
Click to expand...
Click to collapse
Same here. I downgraded to GB yesterday to SIM unlock my phone and went back directly to JB the second it was done.
Safe kernel is the only thing that matters, Rom base has nothing to do with it.
Sent from Nexus 7
You mean guys I can flash directly to any Custom JB ROMs without bricking my beloved Note?
Downloading the RocketRom V1 JB (by Eybee1970 -Thanks!)
Currently, I'm using the AbbysNote 4.2 Kernel I just need to follow this steps below and everything will be fine. Right?
copy ROM on your USB-storage
boot in Recovery
FullWipe (also when coming from other Sammy-JB-ROM!)
Format SYSTEM!!!
flash ROM (it will reboot automatically in most cases)
after initial setup, open Super SU-app and you have to update SU-bin (app will do that for you if necessary!)
*FullWipe - clear cache, clear Dalvik, format system, factory restore?
Thank You..
chasmodo said:
Same here. I downgraded to GB yesterday to SIM unlock my phone and went back directly to JB the second it was done.
Safe kernel is the only thing that matters, Rom base has nothing to do with it.
Sent from Nexus 7
Click to expand...
Click to collapse
Ill dig the quote out
Sent from the man in Your attic.....
howard bamber said:
You can not go from gingerbread to jb..
Click to expand...
Click to collapse
howard bamber said:
Ill dig the quote out
Click to expand...
Click to collapse
No need...its simply not accurate information
Sent from my GT-N7000 using Tapatalk 2
nhivlem said:
You mean guys I can flash directly to any Custom JB ROMs without bricking my beloved Note?
Downloading the RocketRom V1 JB (by Eybee1970 -Thanks!)
Currently, I'm using the AbbysNote 4.2 Kernel I just need to follow this steps below and everything will be fine. Right?
copy ROM on your USB-storage
boot in Recovery
FullWipe (also when coming from other Sammy-JB-ROM!)
Format SYSTEM!!!
flash ROM (it will reboot automatically in most cases)
after initial setup, open Super SU-app and you have to update SU-bin (app will do that for you if necessary!)
*FullWipe - clear cache, clear Dalvik, format system, factory restore?
Thank You..
Click to expand...
Click to collapse
That's correct, all you need is safe kernel.
Sent from my GT-N7000 using xda premium
itsrijo said:
who says you can't go from gb to jb
i was on rooted stock gb and i flashed leaked stock jb over it and everything is working fine..
why do you think that ics has to be flashed ?
infact i did ask here at xda before flashing and nobody told me to flash ics over gb first
Click to expand...
Click to collapse
i agree!! i've done that several times to flash from gb to jb using abyss kernel (just a personal preference); there are other safe kernels to flash from.
Successfully Flashed Custom ROM
From GingerBread 2.3.5 upgrade to Jelly Bean 4.1.1
This is what I've do:
1.Flash Abyss Kernel (Many Thanks to Chasmodo)
2.Reboot CWM Recovery
3. Wipe Data
4. Wipe Cache
5. Mount/System -> Format/System
6. Advance/Wipe Dalvik Cache
7. Wipe Battery Stats
8. Fix Permissions
9. Flash Rom RocketRom V1 - (Many Thanks to Eyebee)
10.Reboot (it will reboot by itself) - wait for at least 2 - 5 mins
Lastly Wait and do the Gangnam style ^_^
Note: you MUST have a safe kernel in performing this.
Many thanks to all the guys who reply to this post
Many thanks to XDA!:good:
Congrats
Back up your EFS now using k-tool
Sent from my GT-N7000 using Tapatalk 2
Thanks for the info - asf58967 :angel:
Backup and verified my EFS done.. :highfive:
flash hydracore kernel with mobile odin or if you can deal with triangle with pc odin and then you can flash whatever you want.
caution. hydracore might not work with this rom
nokiamodeln91 said:
caution. hydracore might not work with this rom
Click to expand...
Click to collapse
Present HydraCore kernels will most certainly NOT work with the JB leak Rom.