[Q] So...what to do with the LP5 kernel? - Galaxy Note GT-N7000 Q&A, Help & Troubleshooting

I've been reading a lot of different opinions on the "Bricked by Stunner ROM thread", but I didn't really see any developer's opinion and to be honest I didn't get much of a conclusion from it...
It just got me confused...
So!!!!! If I'm running imilka's CM9 (which is I'm pretty sure based on LP5 kernel):
- WILL THIS degrade my emmc and if yes...
- IS THERE any safe way to keep the current ICS Rom?
And lastly... If I have a backup made with Abyss Kernel 4.0 of a GB Rom, can I go back to GB by:
- Flashing Abyss 4.2 Redpill
- Restoring backup?
Thanks to anyone who will take the time to answer, I'm asking these because I really got confused by everyone's opinion in that thread and I'd like to know something for sure, for my own personal case.
Again, many thanks to anyone who answers.

eug3n91 said:
I've been reading a lot of different opinions on the "Bricked by Stunner ROM thread", but I didn't really see any developer's opinion and to be honest I didn't get much of a conclusion from it...
It just got me confused...
So!!!!! If I'm running imilka's CM9 (which is I'm pretty sure based on LP5 kernel):
- WILL THIS degrade my emmc and if yes...
- IS THERE any safe way to keep the current ICS Rom?
And lastly... If I have a backup made with Abyss Kernel 4.0 of a GB Rom, can I go back to GB by:
- Flashing Abyss 4.2 Redpill
- Restoring backup?
Thanks to anyone who will take the time to answer, I'm asking these because I really got confused by everyone's opinion in that thread and I'd like to know something for sure, for my own personal case.
Again, many thanks to anyone who answers.
Click to expand...
Click to collapse
I am not a developer at all but this is what I understand from Entropy's posts in that thread (and he is a REAL developer)
- The degradation occurs when you constantly flash ROMs or restore backups, i.e. anything that includes wiping and writing to the system partition
- I think having the ROM as it is will not do any harm, the danger is when you try to flash using the faulted kernels
- Yes you can go back by flashing Abyss 4.2, rebooting in recovery and then restoring your backup, but to be 100% safe use PC Odin and flash one of the pre rooted ROMs, flash CF Root then restore your backup normally
Then again, take my words with a grain of salt but that's what I think is the case

matius44 said:
I am not a developer at all but this is what I understand from Entropy's posts in that thread (and he is a REAL developer)
- The degradation occurs when you constantly flash ROMs or restore backups, i.e. anything that includes wiping and writing to the system partition
- I think having the ROM as it is will not do any harm, the danger is when you try to flash using the faulted kernels
- Yes you can go back by flashing Abyss 4.2, rebooting in recovery and then restoring your backup, but to be 100% safe use PC Odin and flash one of the pre rooted ROMs, flash CF Root then restore your backup normally
Then again, take my words with a grain of salt but that's what I think is the case
Click to expand...
Click to collapse
A million thanks mate!! You've answered my questions before! You really made things clearer for me. Someone in the Bricked by Stunner Thread even suggested that updatng apps and manipulating "large files" on the internal memory degrade the emmc...
Again, thanks a lot for putting that into perspective. I love flashing but I'm ashamed to admit I don't know many of the things that developers know...

eug3n91 said:
A million thanks mate!! You've answered my questions before! You really made things clearer for me. Someone in the Bricked by Stunner Thread even suggested that updatng apps and manipulating "large files" on the internal memory degrade the emmc...
Again, thanks a lot for putting that into perspective. I love flashing but I'm ashamed to admit I don't know many of the things that developers know...
Click to expand...
Click to collapse
Am not 100% sure about the large files transfer but I personally doubt it, before the bricked wave of Stunner users everyone was using the same kernel and nothing happened, and I personally been flashing and testing various mods with no issues so far (knocks on wood )
Still, I can be wrong of course

matius44 said:
Am not 100% sure about the large files transfer but I personally doubt it, before the bricked wave of Stunner users everyone was using the same kernel and nothing happened, and I personally been flashing and testing various mods with no issues so far (knocks on wood )
Still, I can be wrong of course
Click to expand...
Click to collapse
So far as ICS I only flashed the Chainfire Repack and 3 versions of CM9. I think I'll be sticking with the current version (which I'm really in love with...wouldn't want to go back to GB now really...) until the official CM9 comes out
Thanks again for taking the time to answer my questions and getting me on track with these things
LE: And Reloaded and themes several times

matius44 said:
)
Click to expand...
Click to collapse
This was to take you to 600!!

geo.samuel said:
This was to take you to 600!!
Click to expand...
Click to collapse
Thanks sam matey
Nice new avatar btw

matius44 said:
Thanks sam matey
Nice new avatar btw
Click to expand...
Click to collapse
This picture was taken few days back!!
However I like the Title "Recognized Contributor" you earned every bit of it!!

geo.samuel said:
This picture was taken few days back!!
However I like the Title "Recognized Contributor" you earned every bit of it!!
Click to expand...
Click to collapse
Hehe just noticed it a while ago
Thanks a lot mate

From my understanding, it's not degradation at all...but more of a chance you take each and everytime you wipe/flash a ROM. It's an instant short circuit of an emmc sector. At least that's my understanding anyway. It either happens or it doesn't. It doesn't build up the likelihood of it happening over time. I've been using 4.2 Abyss to do all my wiping and flashing, so I'm hoping that will safeguard my Note.

smalmagal said:
I've been using 4.2 Abyss to do all my wiping and flashing, so I'm hoping that will safeguard my Note.
Click to expand...
Click to collapse
True, but point is, how are you getting to Abyss Kernel in the first place? That's a /system wipe/write as well when you flash Abyss kernel unless of course you use Odin for that..

matius44 said:
Am not 100% sure about the large files transfer but I personally doubt it, before the bricked wave of Stunner users everyone was using the same kernel and nothing happened, and I personally been flashing and testing various mods with no issues so far (knocks on wood )
Still, I can be wrong of course
Click to expand...
Click to collapse
Entropy also mentioned that when the I9100 forums were using an affected kernel, several users ended up with corrupt/unusable data partitions. This brings me to believe that any operation in which the kernel is writing to the emmc, regardless of which partition it is writing to, brings risk of permanent damage to your emmc. The result of this is that if it damages your system partition you get a hardbrick, and if it damages your data partition you've got yourself a very difficult to use android install.
EDIT: this all depends, of course, on there being a bug or a hiccup in the script operating the kernel to write to the emmc. Without such a bug these operations are harmless.

chill392 said:
Entropy also mentioned that when the I9100 forums were using an affected kernel, several users ended up with corrupt/unusable data partitions. This brings me to believe that any operation in which the kernel is writing to the emmc, regardless of which partition it is writing to, brings risk of permanent damage to your emmc. The result of this is that if it damages your system partition you get a hardbrick, and if it damages your data partition you've got yourself a very difficult to use android install.
EDIT: this all depends, of course, on there being a bug or a hiccup in the script operating the kernel to write to the emmc. Without such a bug these operations are harmless.
Click to expand...
Click to collapse
So...in lame terms...just using the ROM is dangerous then...??

matius44 said:
Hehe just noticed it a while ago
Thanks a lot mate
Click to expand...
Click to collapse
Congrats to Rec Contributor. You have deserved it a thousand times over.

Related

Possible issue with LPY - CLOSED - read updated sticky post instead

UPDATE: this thread is closed as Entropy512 has already updated his post and confimed the problem
**moderators, pls remove this post if you want to, since it has been added in the sticky post
thx for those who chose to read this and decided on thier own what to do next
thx for those who kept silent, either like or dislike this post
thx for those claimed they have reformatted the device so many times but still running, but pls report if it failed one day. i am not hoping that ur phone will be bricked, instead, just to inform us what caused it
thx for those against this post with spams, even with possible personal attacks. i learnt a lot of english words
lastly, after the experience this time, it further urges me that this is not the place for me
good luck to u all
FROM THE MODERATOR : This news is not new, and YES you should all take great care when flashing. DO YOUR RESEARCH......... do not flash custom roms without the proper knowledge to do it safely (duh)......
Very few people have had any issue with bricking (I only know of 2)......
BUT do Your Homework........ Oka1 Moderator
FWD: by chainfire:
WARNING: I have just been informed that LPY *does* suffer from the I/O bug. Do *not* use any CWM functions ! They are dangerous and may hardbrick your flash memory !
Deleting large files while fully booted may also cause problems with your flash memory.
Also see: http://forum.xda-developers.com/showthread.php?t=1633943
Say tuned for further information.
original post by chainfire: http://forum.xda-developers.com/showpost.php?p=19030788&postcount=6 --- This is 6 months old hardly current information....... food for thought- oka1
incorrect link used above. the correct one should be
http://forum.xda-developers.com/showthread.php?p=25966147#post25966147
EDIT: some ppl in the general thread talked about even OTA upgrade is affected. can someone pls confirm this to other ppls here?
EDIT2: for the sake of safety, i suggest NOT upgrading to LPY until the problem is solved and confirmed
EDIT3: so???
what does it mean?
- you risk bricking your phone if u use the LPY rom
- at this time, the exact problem areas are to be determined
- no evidence so far if this is due to cwm or cfroot's, or it could be the stock rom
- if you r still using gb (android 2.3.6), it is suggested to stick with it at the moment
- it is "assumed" that it was due to formatting the partitions in the recovery
- wipe is NOT safe as well. i checked the source and found that a wipe will call the format_volume function, ie to do a format
is it safe to go back to gb?
- all i can say is, gb should be safe. but the problem is, how to get back to gb safely
can i flash a gb via pc odin?
- yes, you can. but again, no guarantee
is it safe to upgrade via pc odin or OTA?
- no one can assure u it is safe
- some ppl reported the phone bricked via OTA upgrade. maybe he was using a leaked one before but yet to confirm
it's only 5-10% failures so why should we concern about this?
- it's simple. u will only realize u r a victum after your phone bricked
- what we know is the number of ppl suffered. what we will know is the number of ppl who suffered avoidable issues after reading this post. but what we dono is how many lives we saved
my phone is working fine with LPY now. i cant see any problem
- as i said, u wont know what's next. perhaps u r lucky and i am lucky too, for now
what to do then?
- sorry, i want to know too. just wait and see what happen
so r u bxllshxting?
- i dont and wont mind if you think so. this is JUST A WARNING. you certainly have the final say whether to be alerted or simply ignore this post
* to moderators
even i will be banned, i will still post this to let ppl be aware about this
but its ok to use on its own....LPY
Will we ever get rid of this hardbricking issues, well how unlucky we are with this, this is getting ridiculous...
vinokirk said:
but its ok to use on its own....LPY
Click to expand...
Click to collapse
ppl in the gerenal section mentioned even OTA has this problem, although i cant proof it
ICS for Note seems to be star-crossed....
I just went back from Stock ICS by flashing Abyss first, though I wiped from with-in CF-LPY kernel no issues, restored a nandroid of Stunner. Everything seems to be working fine.
Also this shouldn't be in Development. IMHO.
OK then I "say tuned for further information"
This is a officiele kernel so no bugs, problem is ower cwm and the things that we do with the phone that a normale person not do with a phone. Xda devs are not fully understanding ics and they tread it like a gb. See all ics threads that post this rom have problems.
Ok so now im.on alba ics with lpy kernel. How do i get back to gb. Use pc odin and flash the gb firmware that doesnt cause triangle and increase cojnter??
Sent from my GT-N7000 using Tapatalk 2
robertberma said:
This is a officiele kernel so no bugs, problem is ower cwm and the things that we do with the phone that a normale person not do with a phone. Xda devs are not fully understanding ics and they tread it like a gb. See all ics threads that post this rom have problems.
Click to expand...
Click to collapse
ppl claimed OTA is affected
also, official rom doesnt mean bugs free
huzz said:
Also this shouldn't be in Development. IMHO.
Click to expand...
Click to collapse
9 out of 10 ppl came here just for download roms. i don care if it's not for development
if we don inform ppl about this, we are not a responsible developer
****in ****, was waiting so long for official ics and now it seems to cause bricks, damn. But thnx for the info, wont be using cwm recovery
so if i flash stock rom via pc odin and dont root it will all be good?
i dont need root just want ics
DNK13 said:
so if i flash stock rom via pc odin and dont root it will all be good?
i dont need root just want ics
Click to expand...
Click to collapse
I think so, yes.
I am using the official ICS and I have flashed CWM. No issues. I used CWM for full backup nandroid. Nothing is strange.
Sent via Galaxy Note
EdgaBimbam said:
****in ****, was waiting so long for official ics and now it seems to cause bricks, damn. But thnx for the info, wont be using cwm recovery
Click to expand...
Click to collapse
Feel the same too...waited so long!! Yeah it seems its not a problem with the ICS kernel per se, but an incompatability with CWM. So we could technically still use the roms as long as we don't use CWM functions/recovery at all. Anyone confirm?
Yesterday, I was afraid to brick my GNote after installing ALBA LPY directly from Kingdroid V7.
First boot and Blocked in Home without any choice to remove battery.
Second boot, same... I installed it without fullwipe.
So Fullwipe from CWM and format /system partition... hanged... and hard reboot
Formatting /system was impossible...
Restore my nandroid backup... Hanged on /system... ouch...
Boot with CWM (franco.Kernel now)... Restore OK...
iT iS Me said:
I am using the official ICS and I have flashed CWM. No issues. I used CWM for full backup nandroid. Nothing is strange.
Sent via Galaxy Note
Click to expand...
Click to collapse
i have no problems too, but i was a victum before and hard bricked my note
Maybe the main reason of bricks LPY is flashing from leaked ics roms? I cant believe about what is happening :O
ykk_five said:
ppl claimed OTA is affected
also, official rom doesnt mean bugs free
9 out of 10 ppl came here just for download roms. i don care if it's not for development
if we don inform ppl about this, we are not a responsible developer
Click to expand...
Click to collapse
you don't need to justify yourself - you did the right thing to open this thread imho!
ykk_five said:
FWD: by chainfire:
WARNING: I have just been informed that LPY *does* suffer from the I/O bug. Do *not* use any CWM functions ! They are dangerous and may hardbrick your flash memory !
Deleting large files while fully booted may also cause problems with your flash memory.
Also see: http://forum.xda-developers.com/showthread.php?t=1633943
Say tuned for further information.
original post by chainfire: http://forum.xda-developers.com/showpost.php?p=19030788&postcount=6
EDIT: some ppl in the general thread talked about even OTA upgrade is affected. can someone pls confirm this to other ppls here?
EDIT2: for the sake of safety, i suggest NOT upgrading to LPY until the problem is solved and confirmed
* to moderators
even i will be banned, i will still post this to let ppl be aware about this
Click to expand...
Click to collapse
so do you mean that flashing the whole CUSTOM rom with no root and cwm from xda or sammobile is not dangerous? is this what u mean pls reply so that all can know

LPY ICS ---> ALC1 GB Difficulty

Greetings to all,
I am new to these forums as well as the curious world of rooting, flashing ROMS, etc, it is all very interesting to me. After simply scouring and reading for many months I have chosen to do a bit of tinkering with my new N7000. A few days ago I followed Dr. Ketan's guide here ----> http://forum.xda-developers.com/showthread.php?t=1424997 and used Odin to flash LPY (Open Germany). Everything was fine, however after reading a few posts about hardbricking, specifically this one by Entropy512 ----> http://forum.xda-developers.com/showthread.php?t=1633943 I realized that LPY was unsafe and heeded the warning to switch off of that version. Using the same steps I used before in Dr Ketan's guide I used Odin to go back to GB, specifically version N7000XEULA1 (Europe) which to my knowledge is the version my Note would have come with out of box living in Ireland.
After reverting back to GB I have been getting this warning "The process android.process.acore has stopped unexpectedly" with the option to Force Close. My instincts tell me to do a factory reset but I have read many posts about not doing any factory resets from recovery. Here lies my question: What is my next move if I wish to revert back to the currently available version of GB that would be available to me before I started tinkering? I realize now that maybe I need to do a little bit more research before venturing down the dark path of flashing ROMs as I have no interest in bricking my phone...eeek!
I am in Ireland running on the Meteor network. Current Kernal version is [email protected]#2 I never rooted my phone throughout this process to my knowledge.
Any assistance would be very appreciated and certainly rewarded with a "Thanks"
Good to wipe now you're on GB.
Cheers
Thanks for the response Towserspvm2000, much appriciated. I did as you suggested and all looks fine. I guess it is only dangerous to wipe from recovery while on ICS ROMs then? Are you only at risk of hardbricking if you are rooted and using LPY ICS or is unrooted LPY ICS dangerous as well? I went the unrooted route because I thought it was safer and more simple as I am new to this and trying to learn something. I appreciate what all you guys do. Thanks again.
Justinbuckley said:
Are you only at risk of hardbricking if you are rooted and using LPY ICS or is unrooted LPY ICS dangerous as well?
Click to expand...
Click to collapse
That is the 64,000 dollar question. Just don't wipe from any of the ICS roms. If i'm on ICS and something goes wrong, I always PC Odin back to GB before doing anything else. I've always had root too.
I much preferred ICS to GB, but I'm sticking to GB for now, until the delvelopers on here and/or samsung know where the problem lies exactly.
Yeah I much prefer ICS as well. I was on the HTC One X (a beast of a phone when it works, very powerful) which comes with ICS out of box but after having to return 2 of them because of hardware issues I came over to the Note. I love it but the lack of ICS is killing me, it's just a superior OS and the few days I had it on the Note were great but can't risk breaking such an expensive device. I'm with you on waiting until a more stable version is out so I'll cheer from the sidelines until I learn more. The amount of info on these forums is great but for a noobie like me it's a bit overload and no matter how much you read you still have questions (and I even work in IT so I'm not 100% lost)
@Justinbuckley I read somewhere in the forum a signature line which basically inspired me to venture into 'dark world of roms'.. The line was "Its not important which phone you have, what matters is how much you can mod it"
And ya, I think since you are on GB, you should go ahead and do a flashing again for any custom stable rom of GB first. I would suggest Rocket ROM or Check ROM.
This android.process.... Problem should get solved first
Thanks for the encouraging words. I didn't mean to suggest that I was put off of flashing ROMs and learning more about development, I just realized that maybe I bit off a bit more than I can chew initially. I will continue to read and learn from the big guys but maybe stick with GB based ROMs for now as they seem to be more safe. I will do some more scouring and perhaps try Rocket but isn't that also an LPY kernal which is what we have been advised to stay away from? Is it valid to say that ROM flashing while unrooted is generally "safer" than flashing ROMs you need to be rooted for? Or are you limited to what you can flash if you are not rooted? Learning more by the day!
I will reply soon when I wake up.. and its alright. :beer:
Sent from my GT-N7000 using xda premium
Justinbuckley said:
Thanks for the encouraging words. I didn't mean to suggest that I was put off of flashing ROMs and learning more about development, I just realized that maybe I bit off a bit more than I can chew initially. I will continue to read and learn from the big guys but maybe stick with GB based ROMs for now as they seem to be more safe. I will do some more scouring and perhaps try Rocket but isn't that also an LPY kernal which is what we have been advised to stay away from? Is it valid to say that ROM flashing while unrooted is generally "safer" than flashing ROMs you need to be rooted for? Or are you limited to what you can flash if you are not rooted? Learning more by the day!
Click to expand...
Click to collapse
Alright. Here is the ROCKETROM GINGERBREAD version(which I was talking about ):
http://forum.xda-developers.com/showthread.php?t=1380284
The GB version is pretty stable and good working. I always keep it as a backup GB ROM whenever I revert from ICS to GB.
Well, I would say that there are two types of ICS ROMs which I found and was quite ambiguous at the first time when I was a beginner. Here are the both:
1. RocketROM ICS V2: Based on LPY ROM. (Recommended*)
Link: http://forum.xda-developers.com/showthread.php?t=1654838
2. TeamRocket : which I believe is based on chinese leak.
http://forum.xda-developers.com/showthread.php?t=1507265
*If you want desperately the TouchWIZ based rom then go for RocketROM than TeamRocket.
Aye, RocketROM is ICS based on LPY (Boooo ! ) kernel. And it is risky. All LPY, LPF kernels are risky at the moment.
So if you want to move to ICS safely and also desperate to get the 'so far' best features out of your Note, then go for AOSP based roms. They are not cooked in a kitchen. They are properly developed. I suggest you should go for Asylum ICS or ParanoidAndroid or MIUI 2.0 etc. All these are based on CM9 Build which is safe.
About: Is it valid to say that ROM flashing while unrooted is generally "safer" than flashing ROMs you need to be rooted for?
Ahh, see rooting doesn't have any effect on bricking as far as I believe. Its the bootloader which is acts as the bomb. And that slacky emmc bug in ICS is the trigger to make that bomb go off. So more than rooting and unrooting, the technique of install should be precise to what the Dev has prescribed. They surely know a gazillion more info than what any of us know
About: Or are you limited to what you can flash if you are not rooted?
I guess PC Odin should do its job for flashing phone without root. If you want to know more, refer to Dr. Ketan's Guide on how to flash the firmwares using Odin.
So, this is give you the crux of what's happening in the sea! xD
Always, think twice & read thrice before flashing any ROM.
Also remember, samsung knows how many flashes you have made till now
Good luck!
---------- Post added at 09:17 AM ---------- Previous post was at 09:16 AM ----------
badjaguar007 said:
Alright. Here is the ROCKETROM GINGERBREAD version(which I was talking about ):
http://forum.xda-developers.com/showthread.php?t=1380284
The GB version is pretty stable and good working. I always keep it as a backup GB ROM whenever I revert from ICS to GB.
Well, I would say that there are two types of ICS ROMs which I found and was quite ambiguous at the first time when I was a beginner. Here are the both:
1. RocketROM ICS V2: Based on LPY ROM. (Recommended*)
Link: http://forum.xda-developers.com/showthread.php?t=1654838
2. TeamRocket : which I believe is based on chinese leak.
http://forum.xda-developers.com/showthread.php?t=1507265
*If you want desperately the TouchWIZ based rom then go for RocketROM than TeamRocket.
Aye, RocketROM is ICS based on LPY (Boooo ! ) kernel. And it is risky. All LPY, LPF kernels are risky at the moment.
So if you want to move to ICS safely and also desperate to get the 'so far' best features out of your Note, then go for AOSP based roms. They are not cooked in a kitchen. They are properly developed. I suggest you should go for Asylum ICS or ParanoidAndroid or MIUI 2.0 etc. All these are based on CM9 Build which is safe.
About: Is it valid to say that ROM flashing while unrooted is generally "safer" than flashing ROMs you need to be rooted for?
Ahh, see rooting doesn't have any effect on bricking as far as I believe. Its the bootloader which is acts as the bomb. And that slacky emmc bug in ICS is the trigger to make that bomb go off. So more than rooting and unrooting, the technique of install should be precise to what the Dev has prescribed. They surely know a gazillion more info than what any of us know
About: Or are you limited to what you can flash if you are not rooted?
I guess PC Odin should do its job for flashing phone without root. If you want to know more, refer to Dr. Ketan's Guide on how to flash the firmwares using Odin.
So, this is give you the crux of what's happening in the sea! xD
Always, think twice & read thrice before flashing any ROM.
Also remember, samsung knows how many flashes you have made till now
Good luck!
Click to expand...
Click to collapse
And ya I woke up
Thanks
Just a great post, I think I am going to go for one of the CM9 build ROMs as I think I should stay away from LPY for now. I know many of the ICS roms don't have s-pen capability which is really a deal breaker for me, I'll do some more research now to se if the CM9's do. ICS was promised in Q2 (and in Q1) so that should be by today if I'm not mistaken. What's the deal with Samsung? Sheesh!
Seems that there really is no added danger in rooting your phone and that there is a lot to gain from doing it. I may have to do this.
Glad you woke up from your beer coma! lol
i did the same thing
in my brothers phone we went from LPY TO ALC1
follow these instructions... there are for safely change any rom , go in ICS and back etc
the files you need are in a rar in my public drop box.. you have there ANYTHING you need without reading post after post and getting confused..
http://dl.dropbox.com/u/43609376/Steps for a Rooted GB/Steps for a safe rooted rom.exe
1. i connect the phone to the pc (while i have ticked in my phone
the "usb debuging " option ) you find it in "applications" -> development -> usb debuging
i wait for the pc to install the phone drivers
and i open Odin 1.85
thourgh odin i use the files of the folder
"Rooted_Stock_Odex_N7000XXLC1"
with the order showed in the pic "odin file order"
i press start .
the phone is now rooted and i just need CWM
2.
i choose in the folder
"CF-Root-SGN_XX_OXA_LC1-v5.3-CWM5"
the file "already-rooted.bat"
i follow the pc screen instructions and let the program do it's thing. when it's finished
it will tell me to reboot ...
now i have a safe rooted phone with CWM , (the program i need to have in my boot menu for endless custom roms)
NOW
3. for ANY custom rom .. GB or ICS ,that i want to install
I FOLLOW THESE GOLDEN RULES and i am safe...
Four steps to installing any rom for galaxy note
a. put the file abyss 4.2 into your phone reboot to recovery
choose install zip and then choose the file... now you have Abyss kernel.
b. press reboot to recovery ( just to be sure )
c.chose wipe Data, cache and in advanced the dalvike cache wipe
d. if you want to be extra cool reboot to recovery one more and
chose the custom rom of your choise (the one you have downloaded allready and placed inside the phone waiting
as a zip file..
YOU ARE DONE..
This is the universal instructions for any ics rom installation.
No brick and maintain root.
Justinbuckley said:
Just a great post, I think I am going to go for one of the CM9 build ROMs as I think I should stay away from LPY for now. I know many of the ICS roms don't have s-pen capability which is really a deal breaker for me, I'll do some more research now to se if the CM9's do. ICS was promised in Q2 (and in Q1) so that should be by today if I'm not mistaken. What's the deal with Samsung? Sheesh!
Seems that there really is no added danger in rooting your phone and that there is a lot to gain from doing it. I may have to do this.
Glad you woke up from your beer coma! lol
Click to expand...
Click to collapse
Haha. Chuckles! And ya I would say one more thing. Always before wiping and switching to any ICS, I made a policy to revert back to stable GB. Even though I don't expect you to follow that (I know its a tiresome process), but at the times of flashing risky kernel make sure you do go back to a GB
CM9
Must I be rooted to flash a CM9 ROM like Paranoidandroid?
Also, just to be clear, is this installation process different than when I flashed LPY using ODIN because that is the only kind I have done thus far. Haven't done the flash from the sd card yet.
Visit the Thread of Asylum ICS or ParanoidAndroid. I guess you should use search button. You will get it. And ya make sure you find the ROM under your phone's development section only Else many have wrongly flashed Samsung S2 ROMs
Search
I really have been using the search button, and have scoured that thread, I find the instructions for install to not be very beginner friendly which is why I asked. The fact many have flashed the SGS2 ROM is probably evidence of that I'd say. I'll keep looking though.

[Q] Flashing ICS/JB on an XXJVU i9000?

Hello guys, it's me (nay, not Mario :laugh again. Another question.
Got a new battery which seems to hold charge well so I thought I might flash something in the likes of CM9 or CM10(.1).
I'm starting this thread because I would like to be totally sure what should I do (although I know I will never be 100% sure I'm doing it right). The reason I'm starting this thread is fear from bricking my phone (now troll me).
A little background (might be TLTR so freely skip it):
A year or so ago, I had a LG GT540 in my possession. Spoiled by the painlessness (is this a word?) of flashing Huaweis I fearlessly dared to flash fastboot on it in order to flash custom ROMs and stuff. The installation instructions seemed dead simple. Battery was full. Followed the procedure from letter to letter. Despite the fact that I followed the whole tutorial, in the end I got a hard brick. One hour later I thought it ought to be either finished or terminated due to an error of some kind. But no. It just stuck. Unplugged it and tried to turn it on. Fail, bootloop. Tried to reflash it, in all the modes I knew of. There were two or so modes: emergency and some über-emergency mode thingy. Fail. Then I tried with the official LG update tool. Final fail. That was the worst idea one could ever get, it got hard bricked, with no signs of life at all. RIP.
Back to the question.
As a proof that I used that damned search feature (at least tried to) here goes the procedure as I've understood it (while searching):
do a Nandroid and TB backup (optional, but you might really regret it if you don't do so)
back up your EFS folder
wipe data/factory reset
flash the ROM thru recovery
reboot
if it bootloops, reboot to recovery manually
flash the ROM again to finalize the procedure
eventually flash GApps
So,
did I leave out something?
what's the most reliable procedure/app to backup EFS?
is there a way to verify if EFS is properly backed up?
what's the proper, ahem, primer ROM to flash first and make stuff glue together nicely?
Semaphore's recovery tends to blink when browsing through using the capacitive menu button instead of volume buttons, is that a problem?
is Semaphore's recovery itself, regardless of the before mentioned issue, appropriate for flashing ICS/JB (or should I flash some other kernel/recovery before flashing)?
will I survive on XDA with that much questions at once?
It's SIM unlocked (don't know how, second hand phone, most likely with Helroz's unlock application), other details are in the signature.
Thanks in advance!
EDIT: See last post (#7 if the discussion goes on) for more details and answers to my questions.
http://www.youtube.com/watch?v=2DLySUtI8vo
http://www.youtube.com/watch?v=iRnH13sRAIc
http://www.youtube.com/watch?v=1RoZU5ZPMS4
http://www.youtube.com/watch?v=PwHVm90HO1w
check out these and you wont brick your phone happy flashing
I have already flashed a rooted kernel with CWM (CF-Root and later Semaphore).
Please, I know my English ain't perfect, but try to skim through my post. At least the second half of it.
your english is fine i read your post all of it i was just giving you a bit of direction incase you soft bricked your sgs,and as for what the best rom is they are all good roms the devs spend alot of time developing them its just a matter of what set up you like so try them all till you find one you like darkyrom v11 ,is pretty smooth its ics and stable cm 9 is good also ,remics jb 4.2.2 is good also .sgs i9000 is almost impossible to brick just read or watch the info two or three times just to be sure goodluck
TIGER 123 said:
your english is fine
Click to expand...
Click to collapse
Aw, thank you! Sorry for me being kinda needlessly rude.
TIGER 123 said:
and as for what the best rom is they are all good roms the devs spend alot of time developing them its just a matter of what set up you like so try them all till you find one you like darkyrom v11 ,is pretty smooth its ics and stable cm 9 is good also ,remics jb 4.2.2 is good also .
Click to expand...
Click to collapse
You meant this?
moorkai said:
what's the proper, ahem, primer ROM to flash first and make stuff glue together nicely?
Click to expand...
Click to collapse
In fact I wanted to know (along with the doubts from post #1) what do I need to flash prior to playing with ICS and/or JB because I thought that there are some ROMs (e.g. CM9) that do the necessary repartition process(es) as there are some partition layout differences between stock Gingerbread and the newer ICS and JB ROMs... and that failing to do so might lead to soft/hard bricks.
I know that asking questions like "What's the best ROM for my phone?" might lead to subjective and conflicting answers as some prefer lightweightness over functionality and vice versa, thus I don't prefer to do so, neither I did so in my first post. Sorry if you understood me otherwise.
Hope that I made some things more understandable now.
Okay, solved this doubt:
moorkai said:
what's the most reliable procedure/app to backup EFS? Tar zcvf contents of the /efs folder in terminal.
Click to expand...
Click to collapse
However, in one of the videos you posted here CWM 2.5.1.2 was used and thus it additionally stresses the following question:
moorkai said:
is Semaphore's recovery itself, regardless of the before mentioned issue, appropriate for flashing ICS/JB (or should I flash some other kernel/recovery before flashing)?
Click to expand...
Click to collapse
Help me!
I finally dared to flash CM10.1! Everything went silky smooth. Here are my conclusions for further reference (maybe someone can find them useful). These might be inaccurate, but I didn't brick my phone. After all, don't hesitate to correct me if I'm wrong.
How I flashed CM10.1:
do a Nandroid and TB backup (optional, but you might really regret it if you don't do so)
back up your EFS folder
wipe data/factory reset, wipe cache partition, advanced > wipe dalvik cache
flash the ROM through recovery (install zip from sdcard > choose zip from sdcard)
now it will reboot and finalize the flashing if everything is OK
eventually flash GApps
Questions from the first post and ...answers:
Q: Did I leave out something?
A: Most likely, not.
Q: What's the most reliable procedure/app to backup EFS?
A: Type the following stuff in Terminal Emulator or adb shell (root privileges necessary):
Code:
su
tar zcvf /sdcard/efs-backup.tar.gz /efs
# some users suggest that backing this up can also help if IMEI goes belly up
cat /dev/block/stl3 > /sdcard/efs_dev-block-stl3.img
Q: Is there a way to verify if EFS is properly backed up?
A: Dual File Manager is quite useful for testing archive integrity.
Q: What's the proper, ahem, primer ROM to flash first and make stuff glue together nicely?
A: CM10.1, I guess.
Q: Semaphore's recovery tends to blink when browsing through using the capacitive menu button instead of volume buttons, does that mean it will cause ROM installation to fail?
A: I don't know, maybe, so flash CM10.1 with CF-Root kernel installed instead.
Q: Is Semaphore's recovery itself, regardless of the before mentioned
issue, appropriate for flashing ICS/JB (or should I flash some other kernel/recovery before flashing)?
A: See previous answer.

[Q] In light of the eMMC bug, is the N7000 still worth getting?

Hi All,
Just curious how serious the eMMC bug is, and whether the N7000 is still worth getting??
1) Is the bug only present in ICS Roms, with unsafe kernels?
2) Is the phone safe using any of the GB or JB Roms, assuming it is only ICS thats at fault with the chip?
3) I've heard CWM is also dangerous to use, is there a certain one/version to use? (namely, Philz?)
4) How do you prepare the phone from ROM flash? All other Android devices I use to do Factory Reset Wipe in CWM, followed by wiping System and the Cache section. What can I do now, or cant I do... for fear of bricking?
5) Is this App [GalaxSim Unlock, by spocky] ok to unlock, does it work or can it be dangerous in light of eMMC? Or should I get a carrier unlock?
6) If using this phone normally, normal Apps... Is there a risk to bricking if the App write to write to the internal storage?? (such as saving files/settings) or is only if you attempt to wipe it?
7) Whats the absolute do's and DONT's with this device, like to stay away from....
I'm really keen to buy it, but dont want to end up with a BRICK through a silly mistake....
- sorry for all the questions, just really confused by whats ok and whats not...
Thanks, Lister
Emmc brick bug was there in ICS for sure but it is not worth trying on JB as it is no fun to see if the device gets bricked or not.
You can use GB (which has safe kernel) you can do the wipes. ICS and JB there are many custom kernel which are brick bug safe, meaning that it would not brick your phone if you have these kernel (say Philz for example) which also give you CWM and you can do wipes as many times you want without the risk of getting bricked. Philz kernel is available for all the versions.
For how to flash stock rom and list of stock roms use this:
http://forum.xda-developers.com/showthread.php?t=1424997
i dont have any idea about unlock, you may wait for someone to respond to that.
when using the phone normally there is no risk of brick.
Dont wipe the device on stock recovery and you are safe, to be safer always use Philz kernel. if you want to claim warranty at any time you can always flash stock rom again.
Own a note for 5 months now and this device is as good as any for the flashing of ROMs and kernels. So this is surely a safe buy. The PhilZ kernel is not particularly what i am fond of as it caused problems for the flashing of certain ROMs as the recovery is CWM based and not CWM recovery. And i do not have any info about the unlock app
Hi Treacherous_Hawk and Varad297,
Thank you both for your comments and suggestions, all this info I am picking up is very useful for me... As I may of said above, but have certainly said in other places across this board (and other sites). I'm fairly ok/confidant when it comes to Android, and the other Android hardware in my collection. (ZTE Blade, HP Touchpad, and MK802-II) Dont suffer from any kinda serious bug, and are brick free, they will never die... But I must admit, I am a little scared of this eMMC bug in N7000.
So thanks for putting my mind at rest....
If / When I do get this phone (through a mate of a mate), in October when her contract runs out. Will be locked to Vodafone UK, and I am T-Mobile UK, and I believe its currently running on Android 4.1.2 JB Stock.
However I want to flash the P.A.C. Rom to it straight away, as I have this on my ZTE Blade and HP Touchpad and love it...
So whats the best way to do it...??
1) Download Philz Recovery (and which version would I need, being that the rom its on is 4.1.2, and the rom I'll be taking it too is 4.2.2)
- I assume I copy this to SD Card, and flash in Stock Recovery, via going to Download Mode
2) What steps would I follow to clear of current rom? What wipes are safe, or are they all safe with Philz? Normally I do Factory Data wipe, and then System and Cache...
- Are these fine under Philz recovery? As from above two comments... First reply says its safe to do so, second reply says its dangerous... Just really scared about this bug, cant believe Sammy released a device like that...
3) I assume I flash it in Philz CWM, rather than ODIN? Do I need to re-flash a kernel straight after or is the one in P.A.C. (4.2.2) safe from bug?
4) I think the ROM is pre-rooted, but what should I do in case its not? Use ODIN or is there an easier method?
I assume flashing the above rom, via the above method (Philz CWM) will then result in the Yellow Triangle, and bump the count upto 1? So do I just use Triangle Away to clear and reset this, and this is again safe of bricking???
Thanks, Lister
Dude dont panic.
P.A.C. Rom is rooted and does not trigger the emmc bug.
Safe way from stock is as follows:
1.
!DO NOT WIPE ANYTHING ON STOCK!
2.
Get philz kernel for your stock version.
there are packages for flashing with either ODIN which involves connectiong a Computer or with Stock Recovery, which does not involve a computer.
The latter, which is simpler is simply a file on SD you can flash through stock recovery (when off press power+home+volup), it wont even void your warranty.
That provides you with a CWM like recovery from which you can wipe or flash other roms WITHOUT triggering the brickbug.
3.
Get your favourite Rom and flash it through cwm recovery.
BTW: Almost everyone who releases for N7000 puts something in the description that says if the rom is bricksafe.
All newer AOSP/CM based roms should be bricksafe.
Most of the customized Touchwiz Roms are also bricksafe, but watch their thread to be sure.
hjsdfbglsmhjc8we
EDIT:
IMO if you get the Note 1 for free or cheap its well worth getting. If you plan to buy one rather look for the Note 2 because I feel that it is better supported and has better customisation diversity.
Or if I ask myself what my next phone will be... dunno. Maybe a Nexus or Xperia Z or HTC? I cant seem to find the perfectly blended device. Might go with Jolla Sailfish device if it proves usable.
EDIT 2:
I think someone should sticky this as a simple guide for this. Also the existing stickies really need a cleanup to not confuse people with too much information out of differing times.
Does XDA pay moderators? I'd happily clean stickies and test stuff all day. (I'd also assume a neutral persona/state of mind for such activity.)
Hi Illidan Pornrage,
Thank you so much for going into great detail of the steps I need to follow, I'm starting to feel more comfortable at doing and using this now... So any ROM that says they are Brick free means there is no way to trigger it?? Not that I have ever done this, maybe when I first got my Android back in 2010 just to see what it was like... If I did Factory Data Reset in P.A.C. Rom it wont trigger the eMMC bug? (not that Im likely to ever use it... just making sure).
And with Philz CWM Recovery, I can use the Wipe Data/Factory Reset and then goto other screen and wipe the System partition, and the Cache and Davlik Cache with it all being ok... its 100% safe in Philz Recovery to not brick it??
I am so use to CWM on other devices, I am scared of using the wrong selection on the famous N7000 eMMC brick bug... lol
But with the other steps, thank you so much, such a HUGE HELP!!! and I am sure that will put other new (to N7000) users minds at rest...
-- So useful that ya know the above ROM too, as it makes it even easier/safer for me knowing all is gonna be ok with it...
Cant wait to get ROMing now... Just gotta wait till October... b*gger!! lol
Cheers, Lister
If I did Factory Data Reset in P.A.C. Rom it wont trigger the eMMC bug? Yes as often as you like. I flash cm nightlies, so I wipe very often.
And my window manager somehow always loses focus of the textbox. So I write half posts and have to edit 346243 times. Sorry.
And with Philz CWM Recovery, I can use the Wipe Data/Factory Reset and then goto other screen and wipe the System partition, and the Cache and Davlik Cache with it all being ok... its 100% safe in Philz Recovery to not brick it??
Also yes.
As for 100%. I cant assure you that nothing obscure that only happens 1 in a million times happens. But the menchanism that triggers the great evil bug is removed from philz and the mentioned roms.
Phewwww..... so this eMMC bug is no big deal then....
Only an issue if you stay on stock firmwares really, esp that of ICS??
Well thats made me feel a whole lot safer and more determined to want to get it. Had my hopes set on getting it, and then when I heard about the eMMC bug, thought is this gonna be a wise purchase or will I be spending the best part of £150 (dont know the final price yet) on a very large and heavy paper weight!! lol
Thanks so much for putting my mind at rest, great help...
Hi Illidan Pornrage,
I've only just seen/noticed your updates to my original questions, thanks for the updates.... Re: Why am I going for just the Note 1 rather than the Note 2. Is that someone a know (mate of a mate) will be upgrading her phone (she prolly gonna go back to Apple... boooo) and so hopefully she will be parting with her Note (and cheaply I hope, esp re the bug... a-haaaa)
- and couldnt agree more about tidying up the Stickies, as yes a lot of it is out of date, hence my asking and checking... To which you fully re-assured me of the steps, so think this would be useful to all...
Just to add to this, which Philz Kernel would I need??
Phone: Galaxy Note 1 / N7000
Network: Vodafone UK
Current OS: Android 4.1.2 JB Stock
Planned OS to update Too: P.A.C. 22:30 (Android 4.2.2)
So not sure what Kernel I would need from the below link, and if so, can you explain why I need THIS one? What do I need to look for in a kernel?
http://forum.xda-developers.com/showthread.php?t=1901191
Also, can anyone confirm if they have a UK Note 1 on contract (esp Vodafone) as I am hearing the contract ones are unlocked by default. Its only PAYG that are locked down....
thanks, Lister
Hi Illidan Pornrage / Guys,
As per my above post, any idea what Kernel I need based on the above details...??
Thanks, Lister

UK Vodafone N7000, suggestions?

Hi All,
I've waited some months now, until the person I know is finally about to upgrade their phone and sell me their old N7000. It is a UK Vodafone Contract N7000, so hopefully from what Ive read about the internet, it should already be unlocked...
However, is this still worth getting as a phone? And what would be an ideal/good price to pay for it...?? Apparently it is in mint condition, with no scratches on case or screen, except for a couple of scuffs near the charging socket.
1) The person wants £150 for it... Does that seem fair, or do you think I'm being ripped off, based on its age?? And could any of it likely to fail anytime soon...??
2) Are the batteries easy to swap/replace yourself, does the back cover just pop off, or do you have to break a seal?
3) Are there any signs/faults I should look for...??
4) Just before the person is about to sell it, they took it to VodaFone to be repaired. Vodafone returned it back, unrepaired... with a sticker saying "Faulty/Unrepaired" however a go-between friend, has actually tested it, and says it runs fine... Is there anyway to check if it is faulty, whether it is the brick bug? The original owner has sent it in once before for repair (claiming brick bug) but turns out to be user error, to do with Apps. So just need to make sure the device is working like normal or if there is anything wrong with it...
5) What is better, to get the old N7000 second hand with out warranty, or buy a new ZTE Blade V that is newer has warranty but hardware not as good, and as yet has no Dev support...?
Cheers, Lister
Hi guys,
Any opinions please, as i maybe getting this tomorrow.... And don't really want it to be another phone i sell within a week of having it...
Thanks, Lister
1) The person wants £150 for it... Does that seem fair, or do you think I'm being ripped off, based on its age?? And could any of it likely to fail anytime soon...??
Click to expand...
Click to collapse
Too much for a out of warranty and possibly defective device.
2) Are the batteries easy to swap/replace yourself, does the back cover just pop off, or do you have to break a seal?
Click to expand...
Click to collapse
No, no seals to brake, you have to remove back cover and battery to insert SIM card and SD card.
3) Are there any signs/faults I should look for...??
Click to expand...
Click to collapse
Reboot, check for a Yellow triange. It's presence means the original owner has flashed unsuported roms. Not a defect though.
Check every button, check back cover for damaged pins, check chromed frame. Check if the device charges well (usb plug working ok) and if the headphones work (headphone plug working ok). Test all buttons.
4) Just before the person is about to sell it, they took it to VodaFone to be repaired. Vodafone returned it back, unrepaired... with a sticker saying "Faulty/Unrepaired" however a go-between friend, has actually tested it, and says it runs fine... Is there anyway to check if it is faulty, whether it is the brick bug? The original owner has sent it in once before for repair (claiming brick bug) but turns out to be user error, to do with Apps. So just need to make sure the device is working like normal or if there is anything wrong with it...
Click to expand...
Click to collapse
Whitout knowing what was wrong, it's very difficult. Test it like you would test a device, see if every thing works, from phone, camera, net, buttons...
5) What is better, to get the old N7000 second hand with out warranty, or buy a new ZTE Blade V that is newer has warranty but hardware not as good, and as yet has no Dev support...?
Click to expand...
Click to collapse
Though the quality of the ZTE Blade V is not on par to a previously flagship phone, it's not to disconsider. It's a Qualcomm quadcore, better processor. Screen and camera are inferior, but for screen size it's resolution should sufice (cannot quote on color reprodution). Read this
Still, considering question 1), every other question is pointless. IMHO of course.
Hi Daedric,
Thank you for coming back to me with your very useful and helpful Answers.... All of that makes sense, and feel a lot better for the backup opinion....
I'm fairly OK when it comes to Android, but based on this models (not this specific phone i am to buy) past history of risk to brick bug, thought I'd see if its worth it.
My original was the first ZTE Blade, so anything is a plus.. although it Dev community has been amazing. I got a G300 when the Blade died. I only had the G300 a week from new, wasn't overly impressed.
Always had my eye on this, as i know the person selling it through a friend. The original owner wouldn't have a clue how to ROM it, she barely knew how to use it really... And so don't know what previous faults were as she didn't know herself.
I'd like to check if all the phones storage is available and no faulty eMMC blocks found, can i do it through that App in the play store... And assume its a non destructive check, as the device wont have Philz recovery when i view it, although may have too just to get root
Thanks regarding batteries, not seen this device up close... I wondered if they copied Apple by forcing you into an expensive battery replacement. Also due to being a year old, might look to get spare battery if itndoesnt hold well... Although there is no indication i know of that it does hold its charge...
As for price, what would you think is fair price based on age, potential risk of bug... But despite its in great condition?
I was thinking ZTE Blade V as its new, quad core and will have a year warranty... Otherwise features of N7000 and big dev support make it a winner for me...
Thanks again for all your help though, will certainly test it....
Lister
Always had my eye on this, as i know the person selling it through a friend. The original owner wouldn't have a clue how to ROM it, she barely knew how to use it really... And so don't know what previous faults were as she didn't know herself.
Click to expand...
Click to collapse
Red flag there. The polish in their nails ruins smartphones. Also cars. Now i'm being sexist, apologies ladies
Since she's the regular type of user, any damage that may have happened came either from factory defect, or miss use. Maybe she dropped it.
I'd like to check if all the phones storage is available and no faulty eMMC blocks found, can i do it through that App in the play store... And assume its a non destructive check, as the device wont have Philz recovery when i view it, although may have too just to get root
Click to expand...
Click to collapse
Faulty eMMC blocks are irrelevant. I bet every phone has them, and the eMMC controller just remaps them to backup blocks, withouth the user even knowing. It's not going to be easy to find out if the eMMC has any bad blocks, the controller prevents it. Still, 30 or 40 badblocks is not a concern, 4000 would That would be noticable, either the device wouldn't boot, or the storage would be very small (like, from 16 gb to 10 or something) Don't trouble yourself with this, the eMMC brick bug is a entire different issue.
Apparently (i haven't tried myself for obvious reasons) the stock ICS kernel as a bug that when running certain eMMC commands (namely, the famous SSD TRIM command of Android 4.3) would completely brick the eMMC, rendering the device a brick. It's a bug on the eMMC controller.
If you buy the Note, and it's running ICS, under no circumstances will you wipe/factory restore in CWM. You can only do that AFTER flashing a "no brick bug" kernel, such as PhilZ. There's a app that can check if you have the problematic eMMC, but it isn't worth the risk. Just follow procedures, flash SAFE kernels, and be happy.
Thanks regarding batteries, not seen this device up close... I wondered if they copied Apple by forcing you into an expensive battery replacement. Also due to being a year old, might look to get spare battery if itndoesnt hold well... Although there is no indication i know of that it does hold its charge...
Click to expand...
Click to collapse
Batteries are reasily replacable, just don't enter the bandwagon of the 5000mah battery stock size. It doesn't happen. It most someone might get 3000mah instead of 2500mah. When in doubt, buy genuine.
As for price, what would you think is fair price based on age, potential risk of bug... But despite its in great condition?
I have a note, vodafone PT, a small dent on the chrome frame near the headphone hole, two tiny marks on the screen. I don't have the invoice, and even if i had it it's out of warranty (2y in PT). No one will give me 150€ for this. So... Try to drop it to 100£ Haggle
LOL, the sexiest in you... :good: he he he.... But true though, apparently it has been sent off twice for faults. One of which was not found, the other I dont know about yet (but will find out tomorrow when meet my mate, not the one selling it, but the go-between). Plus she has reported other things not working in the past, when they were fine... lol Yeah, she's just the "regular type of user" lol
Oh, ok... I think I got confused somewhere with this eMMC bug, and that if ya get it... obviously the first tell tell sign is non-booting... But I wondered if she (may not even know) or if Vodafone returned it saying Not Repaired, if it was missing storage. So I know its a 16Gb model, but was wondering if I get it and I only see like 10Gb storage or summit?? lol
Yeah, I am aware of the ICS danger wipes... (which do scare me...) And so the first thing I will do, if I do get it... Is put Philz Kernel on straight away... I am a little confused as to which one I will need, but I am sure that will make sense when I have the thing in front of me...
Only couple of things now...
1) If I install Philz Kernel via Download Mode (so no Yellow Triangle), when I flash a new ROM, does it wipe Philz Kernel, or does it stay there? Do I have to keep Flashing it after a ROM?
2) Now you got me worried about Android 4.3 (as if ICS wasnt bad enough). So if I install a Android 4.3 based ROM, is there a chance I could possible brick it with CM10.2, or does Philz Kernel take care of that too...??
Makes me wonder how Samsung managed to sell that many Note, Note II, S2, S3 and S4 devices that all have faulty components, one way or another... Starting to think the ZTE may be a safer bet...
That said, someone told me as long as I use Philz Kernel, I have nothing to worry about.. and can go about Flashing ROMs like I would any other phone...
So can running this: https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check&hl=en be dangerous for the device thing? Is the media check, destructive? or does it run in a read-mode only...??
I tried the above App on my HP Touchpad, because as far as I am aware it doesnt suffer the eMMC bug of any kind, and just wanted to see what it would do... It said my 32GB passed fine... Yippie... lol
Ah cool about the batteries, its only in case it dont hold out... But I would imagine it would still be ok... I had my Blade 1 for about 3 years before the Touchscreen went, and yet the battery was as good as the day I got it...
As for price, yeah thats exactly what I was thinking too, around the £100... at a push, I'd say £125... meet half way. But certainly not £150. As never know it could die on me at any time, esp if she sent it to Voda twice....
Thanks again, much appreciated...
1) If I install Philz Kernel via Download Mode (so no Yellow Triangle), when I flash a new ROM, does it wipe Philz Kernel, or does it stay there? Do I have to keep Flashing it after a ROM?
Click to expand...
Click to collapse
If you install via download mode + Odin, you'll get the Yellow triangle. The best bet, is to put the kernel in the sdcard, reboot to recovery, and flash it through there. After that, you get the CWM or other recovery and can flash at will. No yellow triangle for you
2) Now you got me worried about Android 4.3 (as if ICS wasnt bad enough). So if I install a Android 4.3 based ROM, is there a chance I could possible brick it with CM10.2, or does Philz Kernel take care of that too...??
Click to expand...
Click to collapse
The kernel devs have disabled/disarmed the bug in 4.3/CM102 kernels as well, you won't have the TRIM effects of 4.3, but you won't have bricks either.
Makes me wonder how Samsung managed to sell that many Note, Note II, S2, S3 and S4 devices that all have faulty components, one way or another... Starting to think the ZTE may be a safer bet...
Click to expand...
Click to collapse
I'm not sure if all this devices share the bug, and S4 only has it if it's a exynos, the Qualcomm one probably hasn't.
That said, someone told me as long as I use Philz Kernel, I have nothing to worry about.. and can go about Flashing ROMs like I would any other phone...
Click to expand...
Click to collapse
True, but most kernels state on OP that it has the buggy code disabled. Remember, PhilZ's kernel is a TW rom kernel, not a AOSP/CM kernel.
So can running this: https://play.google.com/store/apps/d...mc_check&hl=en be dangerous for the device thing? Is the media check, destructive? or does it run in a read-mode only...??
Click to expand...
Click to collapse
Running it no, it just reads the ID of the eMMC controler and reports if it has been confirmed or not to be faulty, TRUSTING it is dangerous. Stay on SAFE kernels.
I tried the above App on my HP Touchpad, because as far as I am aware it doesnt suffer the eMMC bug of any kind, and just wanted to see what it would do... It said my 32GB passed fine... Yippie... lol
Click to expand...
Click to collapse
Of course, it's not using Samsung NAND Still, the TP does not support TRIM yet...
Ah cool about the batteries, its only in case it dont hold out... But I would imagine it would still be ok... I had my Blade 1 for about 3 years before the Touchscreen went, and yet the battery was as good as the day I got it...
As for price, yeah thats exactly what I was thinking too, around the £100... at a push, I'd say £125... meet half way. But certainly not £150. As never know it could die on me at any time, esp if she sent it to Voda twice....
Thanks again, much appreciated...
Click to expand...
Click to collapse
Stay safe, if the device seems weird, ask for a time. Like, give half and the other half next week. Gives you time to check it. Of course the seller might not be up to it.
If you install via download mode + Odin, you'll get the Yellow triangle. The best bet, is to put the kernel in the sdcard, reboot to recovery, and flash it through there. After that, you get the CWM or other recovery and can flash at will. No yellow triangle for you
Click to expand...
Click to collapse
My mistake, I got confused between Download Mode and Recovery Mode... God, I am doomed to SamsungHell, before I even get this device.. lol
The kernel devs have disabled/disarmed the bug in 4.3/CM102 kernels as well, you won't have the TRIM effects of 4.3, but you won't have bricks either.
Click to expand...
Click to collapse
Thats cools, I had a feeling the Devs of each rom, would remove any iffy/dangerous code before releasing... However, I am a Noob to 4.3... What does it mean by "wont have TRIM effects"? Is this a useful feature, on a safe device?
I'm not sure if all this devices share the bug, and S4 only has it if it's a exynos, the Qualcomm one probably hasn't.
Click to expand...
Click to collapse
Fair play, just seen Apps in Store that fix Freeze, eMMC, and Sudden Death, and makes me wonder how reliable Samsung is.. Think I'll stick to Qualcomm again after this device.. lol
True, but most kernels state on OP that it has the buggy code disabled. Remember, PhilZ's kernel is a TW rom kernel, not a AOSP/CM kernel.
Click to expand...
Click to collapse
I'm confused now, so if I install Philz, I cant then use it to wipe and install ROMs, such as PAC Rom (4.3 based) as that has CM base in it... So will that rom, do something to Philz, if I flash it??
Running it no, it just reads the ID of the eMMC controler and reports if it has been confirmed or not to be faulty, TRUSTING it is dangerous. Stay on SAFE kernels.
Click to expand...
Click to collapse
I'm still very new to this N7000 m'larky.... and so think its prolly best I stick to just Philz, if thats the correct thing to say/do...??
Of course, it's not using Samsung NAND Still, the TP does not support TRIM yet...
Click to expand...
Click to collapse
So the TP could support TRIM (whatever that is??) in future, and so need to be cautious there too...??
Stay safe, if the device seems weird, ask for a time. Like, give half and the other half next week. Gives you time to check it. Of course the seller might not be up to it.
Click to expand...
Click to collapse
Your right, she prolly wont agree to that... However, I think she is ok... So she will prolly let me just use it first before taking money... Or if summit does go wrong, providing I didnt cause it (hopefully) I am sure she would take it back, and refund... She got the device on Contract, and so she has already paid the money for it, what I give her is just extra cash for what she'd prolly just leave in the draw when she gets her new phone... I am seeing my mate (not the seller, the go-between person) tomorrow, who I get on very well with... We are going for drinks, so will get chance to have a good play/feel with it tomorrow, and see what its like...
Sorry for all the Noob questions, on any other device I am ok, as I feel safe with those, and can tweak and flash to my hearts content... Just, hearing so many danger stories with this... and once you Brick it, there is no going back... No switch off, count to 10, and reboot and all is fine... Its dud with this if all goes wrong... So thank you for being so patient and helpful to me with this...
Hi Daedric,
Ok, I saw the phone today... and it is in MINT condition... No scratches or scuffs anywhere over screen, or rest of body of phone... Except for tiny tiny scuff near charging socket, but that is all...
Phone appears to be fine.... played around on net, downloaded Apps, opened camera... I didnt take any pictures as it didnt have an SD Card in it, and didnt want the flash to go off in a pub... Although I was expecting the LED to turn on when I selected it in the camera. It does on the Huawei G300 when its too dark. But still, Im sure this will work...
I downloaded AndroSensor and they all seemed to be working....
I ran the eMMC Bug checker app, and of course it has the chip as expected. I couldnt test the media, as it wasnt Rooted, and didnt really want to Root as it's not mine yet... So not fair on seller to make changes.
All seems good... However....
1) When I went into Storage, Total Available Storage, I think USB showed up as 11Gb. Is this normal, as its a 16Gb model... Has the other 5GB been alocated towards ROM, and various other partitions...?? Or is there space missing...???
2) Although I didnt see it when I used it, apparently the phone Freezes from time to time in certain Apps. And this is why it has been sent for repair... Although the first time, apparently Vodafone put it down to the type of Apps she had on, and that there was too many. Second time, they didnt repair it... They just returned it as Faulty / Not repaired. And then on further inspection, the fault appears to be Battery. As the battery has a sticker on it saying Faulty.... Even though it seemed to be holding its charge ok.
2a) So, are the freezes normal, under stock JB 4.1.2? If I installed a custom rom, will this ease/fix the freezes. Or if I even did all the wipes and reflashed any rom, is it likely to fix it?? ie: bad stock rom install ??
2b) Could battery have any likely hood it freezing or acting odd?? (even though I didnt see this myself) I could just buy a new battery for it...
So, not sure what kinda price to go for.... She has quoted £150, its in MINT condition with box and everything with it.... Only ever spoke to her online, as she is a friend of a friend. Do I go for the £150, or do you think its not really worth that, in case of issues... (ie: sent to Vodafone twice, even though they didnt fix anything) and for the chances it could 'only assuming' break outside warranty?
Thanks for any input....
Cheers, Lister
My mistake, I got confused between Download Mode and Recovery Mode... God, I am doomed to SamsungHell, before I even get this device.. lol
Fair play, just seen Apps in Store that fix Freeze, eMMC, and Sudden Death, and makes me wonder how reliable Samsung is.. Think I'll stick to Qualcomm again after this device.. lol
Click to expand...
Click to collapse
Be advised, from someone that comes form Qualcomm and HTC. On Samsung, RECOVERY IS INSIDE THE BOOT. It's not on a separate partition. Flashing a kernel, flashes a recovery. Yeah.. SamSungHell.
Thats cools, I had a feeling the Devs of each rom, would remove any iffy/dangerous code before releasing... However, I am a Noob to 4.3... What does it mean by "wont have TRIM effects"? Is this a useful feature, on a safe device?
Click to expand...
Click to collapse
TRIM is something that speeds up eMMC and SSDs, specially with erases/deletes. Go read about TRIM, it's better than explaining it. No, since we don't have already, you won't miss it on 4.3.
I'm confused now, so if I install Philz, I cant then use it to wipe and install ROMs, such as PAC Rom (4.3 based) as that has CM base in it... So will that rom, do something to Philz, if I flash it??
Click to expand...
Click to collapse
PhilZ kernel is a TW kernel, so it only works with Samsung's Touchwiz based roms. You can use TW kernel to flash AOSP/CM, and CM kernel to flash Touchwiz. Samsung and HTC tweak Android so much that kernel tweaks are also necessary. Still, don't sweat it, just remember, if your running a TW rom, either official or custom, flash ONLY touchwiz kernels. If running AOSP based roms (AOSP, CM, PAC, AOKP etc) flash AOSP/CM kernel. Carefull with versions though.
So the TP could support TRIM (whatever that is??) in future, and so need to be cautious there too...??
Click to expand...
Click to collapse
*OFFTOPIC* Yes, there's a dev trying to enable it. Has it stands, the kernels don't support trim (try running on a terminal the fstrim app, same thing.)
Phone appears to be fine.... played around on net, downloaded Apps, opened camera... I didnt take any pictures as it didnt have an SD Card in it, and didnt want the flash to go off in a pub... Although I was expecting the LED to turn on when I selected it in the camera. It does on the Huawei G300 when its too dark. But still, Im sure this will work...
Click to expand...
Click to collapse
RED FLAG! In the absense of a sd card, the camera will use its internal storage. Also, when flash set to ON (instead of Auto or off), it will always fire. There's a widget to enable it also. Carefull there, a flash led should be easy to replace, circuitry for it not so much.
When I went into Storage, Total Available Storage, I think USB showed up as 11Gb. Is this normal, as its a 16Gb model... Has the other 5GB been alocated towards ROM, and various other partitions...?? Or is there space missing...???
Click to expand...
Click to collapse
Normal, the device as 16GB total, take the standard Android partitions and you get 11GB.
Although I didnt see it when I used it, apparently the phone Freezes from time to time in certain Apps. And this is why it has been sent for repair... Although the first time, apparently Vodafone put it down to the type of Apps she had on, and that there was too many. Second time, they didnt repair it... They just returned it as Faulty / Not repaired. And then on further inspection, the fault appears to be Battery. As the battery has a sticker on it saying Faulty.... Even though it seemed to be holding its charge ok.
Click to expand...
Click to collapse
Theoretically normal, could be the Vodafone UK rom and their BLOATWARE, could also be the battery. Maybe it charges OK, and it lasts fine, but when the devices ramps up both CPU and GPU, the batery cannot keep up the amperage. That lack of power usually is enough to produce micro errors, the type that can be caught and fixed in time, but causing a error on a process and ence, slowdowns.
So, are the freezes normal, under stock JB 4.1.2? If I installed a custom rom, will this ease/fix the freezes. Or if I even did all the wipes and reflashed any rom, is it likely to fix it?? ie: bad stock rom install ??
Click to expand...
Click to collapse
Yeah, TW is quite heavy, the standard apps are a pain in the ass.
2b) Could battery have any likely hood it freezing or acting odd?? (even though I didnt see this myself) I could just buy a new battery for it...
Click to expand...
Click to collapse
Yeap, just like on a computer, on a faulty PSU can cause the weirdest of issues, like BSOD from nothing, RAM not detected or partially detected, won't reset properly even though it cold boots fine, or perhaps that one where under load the mobo just reboots/turns off due to the lack of stable power. With eletronics, power stability is a must, energy fluctuations are it's biggest enemy.
Sorry for all the Noob questions, on any other device I am ok, as I feel safe with those, and can tweak and flash to my hearts content... Just, hearing so many danger stories with this... and once you Brick it, there is no going back... No switch off, count to 10, and reboot and all is fine... Its dud with this if all goes wrong... So thank you for being so patient and helpful to me with this...
So, not sure what kinda price to go for.... She has quoted £150, its in MINT condition with box and everything with it.... Only ever spoke to her online, as she is a friend of a friend. Do I go for the £150, or do you think its not really worth that, in case of issues... (ie: sent to Vodafone twice, even though they didnt fix anything) and for the chances it could 'only assuming' break outside warranty?
Thanks for any input....
Cheers, Lister
Click to expand...
Click to collapse
Test the flash led, i don't want you to buy it on my advice. The battery can easily be replaced, the rest not so. If the flash led works, if the camera snaps pictures, if everything is on the box, oh well, welcome to the club. Remember, it might be 150£ + 15£ for the battery.
Be advised, from someone that comes form Qualcomm and HTC. On Samsung, RECOVERY IS INSIDE THE BOOT. It's not on a separate partition. Flashing a kernel, flashes a recovery. Yeah.. SamSungHell.
Click to expand...
Click to collapse
This is starting to sound a little confusing now... Never owned a device like this before... Had the ZTE Blade, HP Touchpad running Android, and some other random chinese device.... Managed to mess around with those in safety, knowing that I cant do it no harm... I'm sure this will be ok once I get use too it. But I just fear certain Apps could kill it, unintentionally..
TRIM is something that speeds up eMMC and SSDs, specially with erases/deletes. Go read about TRIM, it's better than explaining it. No, since we don't have already, you won't miss it on 4.3.
Click to expand...
Click to collapse
Okie dokies, I shall have a read up about that.... As you say, prolly to much to explain about in a short Answer. First I heard about it was on Samsung and that it could kill certain devices, then I heard it was a feature of Android 4.3...
PhilZ kernel is a TW kernel, so it only works with Samsung's Touchwiz based roms. You can use TW kernel to flash AOSP/CM, and CM kernel to flash Touchwiz. Samsung and HTC tweak Android so much that kernel tweaks are also necessary. Still, don't sweat it, just remember, if your running a TW rom, either official or custom, flash ONLY touchwiz kernels. If running AOSP based roms (AOSP, CM, PAC, AOKP etc) flash AOSP/CM kernel. Carefull with versions though.
Click to expand...
Click to collapse
Sorry to be such a Noob, and clueless with this device. All other devices, it was simple... We just needed one Recovery.... CWM! However, now it seems I need different ones for different ROMs. I mainly plan to use PAC 4.3... However, of course this toy will be new to me, so I would like to try various ROMs, inc CM, PAC and STOCK (based on GB, ICS only if safe on safe kernel, and JB)... Could I do all of this in the latest Philz? Or do I need to use a different one (and which others, I only know of Philz). Also regarding Philz, do I use the 5.11.02 (heard that has heat related issues) or do I use 5.08.xx (which people seem to be going back too...?) And also which Philz do I need, apparently my Baseband is N7000XXLT3 (I couldnt see a Philz that matched that...?)
*OFFTOPIC* Yes, there's a dev trying to enable it. Has it stands, the kernels don't support trim (try running on a terminal the fstrim app, same thing.)
Click to expand...
Click to collapse
Oh right, well my current PAC rom on Touchpad is running just fine and dandy at the moment... (Its about two versions behind.... but it has features that are removed in the latest... so I will stick with that. Triple booting WebOS, Android and Ubuntu....
RED FLAG! In the absense of a sd card, the camera will use its internal storage. Also, when flash set to ON (instead of Auto or off), it will always fire. There's a widget to enable it also. Carefull there, a flash led should be easy to replace, circuitry for it not so much.
Click to expand...
Click to collapse
It prolly would of saved on the internal memory... But I was wary of (if the flash did work) that it would go off in a busy pub... Last thing I need is big butch Barry looking over me... lol... But yes I have asked my mate to check the camera and Flash for me... Shall let you know..
Normal, the device as 16GB total, take the standard Android partitions and you get 11GB.
Click to expand...
Click to collapse
Oh ok, thats put my mind at rest... Was starting to think I'm loosing some storage But didnt know how much N7000 puts aside for itself... I bought a 32GB SD for it last weekend...
Theoretically normal, could be the Vodafone UK rom and their BLOATWARE, could also be the battery. Maybe it charges OK, and it lasts fine, but when the devices ramps up both CPU and GPU, the batery cannot keep up the amperage. That lack of power usually is enough to produce micro errors, the type that can be caught and fixed in time, but causing a error on a process and ence, slowdowns.
Click to expand...
Click to collapse
I did wonder if it could be Apps... Im not sure if its still fully fresh STOCK, or whether she has downloaded all kinds of Apps too it... As it seems the same Apps as in store demo of Note II... But I shall start it from clean anyway, will be getting rid of 4.1.2 anyway in favour of PAC 4.3
Yeah, TW is quite heavy, the standard apps are a pain in the ass.
Click to expand...
Click to collapse
As per above, the amount of Apps on there, just made it looked cluttered... so shall start from clean and either remove them, or just remove the OS...
Yeap, just like on a computer, on a faulty PSU can cause the weirdest of issues, like BSOD from nothing, RAM not detected or partially detected, won't reset properly even though it cold boots fine, or perhaps that one where under load the mobo just reboots/turns off due to the lack of stable power. With eletronics, power stability is a must, energy fluctuations are it's biggest enemy.
Click to expand...
Click to collapse
Putting it like that, does make an awful lot of good sense... I work in computers, and have come across the odd iffy PSU, and the random faults it generates because of not hitting the right power ratings... So I shall invest in a new battery just to be on the safe side...
Test the flash led, i don't want you to buy it on my advice. The battery can easily be replaced, the rest not so. If the flash led works, if the camera snaps pictures, if everything is on the box, oh well, welcome to the club. Remember, it might be 150£ + 15£ for the battery.
Click to expand...
Click to collapse
Thats ok mate, I fully fully appreciate all of your advice... You have been a great source of knowledge and support. Really appreciate the lengths and details you have gone into explaining this for/to me... Sorry to be such a pain, and all the (possible pointless questions) you've put my mind at ease. I dare say i have more questions when I get it too, if thats ok...?
Thanks, Lister
Code:
This is starting to sound a little confusing now... Never owned a device like this before... Had the ZTE Blade, HP Touchpad running Android, and some other random chinese device.... Managed to mess around with those in safety, knowing that I cant do it no harm... I'm sure this will be ok once I get use too it. But I just fear certain Apps could kill it, unintentionally..
Sorry to be such a Noob, and clueless with this device. All other devices, it was simple... We just needed one Recovery.... CWM! However, now it seems I need different ones for different ROMs. I mainly plan to use PAC 4.3... However, of course this toy will be new to me, so I would like to try various ROMs, inc CM, PAC and STOCK (based on GB, ICS only if safe on safe kernel, and JB)... Could I do all of this in the latest Philz? Or do I need to use a different one (and which others, I only know of Philz). Also regarding Philz, do I use the 5.11.02 (heard that has heat related issues) or do I use 5.08.xx (which people seem to be going back too...?) And also which Philz do I need, apparently my Baseband is N7000XXLT3 (I couldnt see a Philz that matched that...?)
The Blade, like so many other Android devices, was running AOSP. Maybe a theme, a few custom apps like dialer and contacts, but nothing major. Porting AOSP and CM to it was a "easy" task. Samsung, HTC and a few others, take this customization to a new level. From the lockscreen, notifications, dialer, contacs, everything is custom made. Usually, this requires tweaks to the Android Framework. That makes a few OEM apps incompatible with AOSP (you can't just pick the camera app from TW and expect it to run on AOSP, it won't). To make matters worse, this framework difference is augmented but Linux Kernel tweaks. So, you now have a Android version that requires a custom tailored kernel. Ence the kernel versions of Samsung and HTC.
So, Samsung N7000 has 2 major branches , TW which stopped on 4.1.2 (be it official or custom) and AOSP which is on 4.3 (all custom, there's no official AOSP for the note like the GS4). HTC also has this, there's the Sense branch, and the AOSP branch.
Now, MOST (i almost dare say ALL but one) have the recovery on a separated partition, along with it's micro kernel. Recovery is like a small Linux OS with a small kernel, to do it's tasks. On the Blade any most others, it's on a separated partition, there's /boot for the Android kernel and boot files, and a hidden partition with the Recovery kernel and necessary files. If you press a certain keys while booting, instead of /boot the device uses that partition and Recovery loads.
Now, Samsung like ****ing retards they are, decided to have recovery mixed with the boot partition, and i suspect that it's dependend on the Android kernel. The problem here is, you flash a kernel, you flash a recovery. Your new recovery MIGHT not be able to restore that NAND backup that you did on your old recovery. Worse, you damage that partition, you're left without means to boot android, or recovery to fix it.
So, it's might be a major pain in the ass, but it's not so bad. Just have to pay attention.
Free tip:
Android is based on a few partitions, there's /boot for kernel and such, /system for the Android OS, config files and the very basic, /data for your apps, settings, saves, etc, /cache to keep a fast cache, and lastly sdcard0 and sdcard1 for internal and external storage.
Now, Samsung, like genius they are, decided to add another one to the mixture, /preload. This partition is only used by TW roms (TW does not fit inside /system unless you start cutting alot of standard apps).
Most TW kernel and it's recovery, can backup /preload on a NAND backup. Most AOSP kernels and CWR can't.
Also, by some mysterious reason, ALL TW based recoveries DON'T backup /preload by default, you have to go and set it so.
When and if you get the device, things will start to become clearer
Hi DaedRic,
WOW.... where do I start??? Your knowledge on both Android (as a system) and of this device specifically is impressive, and really interesting to know/hear. Plus you explain it such ways as to go into great detail but not too hard and not to dumbed down either... Really appreciate it, and learning lots by it already.... Didnt know the differences by the two different kinds of ROM sets, or the way that Samsung likes to mix (MESS) things up a bit with the Kernel and Recovery as one... This is gonna take some getting use too, when playing with ROMs...
I think when I get the device, and choose which ROMs to play with, might give you a heads up first, to seek what to use when flashing them. But for a long while/time, I'll just mess with PAC 4.3 for now as it seems complete and feature rich...
I shall learn it, and get use to its special ways...
I am certainly getting this device now, and picking it up on Friday Managed to get it down to £100 too, so makes it even sweater deal
This is gonna be a HUGE upgrade for me, being based on my very first Android phone, ZTE Blade 1...
What Philz Kernel do I need if the baseband is N7000 XXLT3 please, as I couldnt see that one listed... only LT5 and LT10 I think??
Many thanks once again... Lister
What Philz Kernel do I need if the baseband is N7000 XXLT3 please, as I couldnt see that one listed... only LT5 and LT10 I think??
Click to expand...
Click to collapse
Those letters, LT3, XXLT3, LT5, LT10 are Samsung rom version and location (example Vodafone UK JB 4.1.2)
LT3 is the latest baseband/radio for the Note i think, LT10 is the latest ROM. Still, you can use Philz LT10 with a inferior LT rom.
BTW, PAC is AOSP, you're not going to use Philz
Hi DaedRic,
Oh no, I hate to have to do this... but... where do I go / do, now???
With all the above, I was (and am) trying to take it all in... re: TW and ASOP kernels. But from my early research on the boards (other posts) I was led to believe, Philz Kernel was the holy grail of all Kernels/Recoveries...??
However, Philz is now only for TW (TouchWiz?) based ROMs, which can include official Samsung Stock roms. Can that be, GB, ICS and JB Stock Roms...? And is ICS safe now if I keep Philz Kernel on there??? And if I ever had, but not likely too.. the desire to Factory Reset, within Android Settings, Security, Wipe... that the phone is safe?? Also, Philz Kernel supports CM based Roms too??
However, PAC is AOSP based rom.... So which/what Kernel/Recovery do I need for this? And yet this AOSP, also supports CM based roms, much like Philz TW based Kernel...??
<meltdown>
How do I keep flashing/changing these Kernels...?? Can I keep a copy of all the Kernels somewhere on the SD Card, and Flash into them via Stock Recovery?? As i was led to believe you did so with Philz one, as it wouldnt increase Samsungs Counter (another thing I need to get my head around...)
So baring in mind, I am getting this device on Friday... what are my first instructions/steps to do to this device??
Running Stock Vodafone UK firmware, JellyBean 4.1.2 non-rooted.
If only there was a Kernel / Recovery that supported all... Gosh, the days of ZTE were so simple... Just had ClockWorkMod and that was it... lol
Sorry to be such a pain/noob... / Thanks, Lister
With all the above, I was (and am) trying to take it all in... re: TW and ASOP kernels. But from my early research on the boards (other posts) I was led to believe, Philz Kernel was the holy grail of all Kernels/Recoveries...??
Click to expand...
Click to collapse
It is. PhilZ is a Stock TouchWiz kernel, difference is the fact that it's SAFE, and the recovery. PhilZ recovery rocks
However, Philz is now only for TW (TouchWiz?) based ROMs, which can include official Samsung Stock roms. Can that be, GB, ICS and JB Stock Roms...? And is ICS safe now if I keep Philz Kernel on there??? And if I ever had, but not likely too.. the desire to Factory Reset, within Android Settings, Security, Wipe... that the phone is safe?? Also, Philz Kernel supports CM based Roms too??
Click to expand...
Click to collapse
Facts:
Philz Kernel is a Touchwiz ONLY kernel
GB is outdated
So is ICS
Touchwiz ICS is safe if using safe kernels.
If you're using a safe kernel, there's nothing you can do to trigger the bug
PhilZ does not work on AOSP/CM roms.
However, PAC is AOSP based rom.... So which/what Kernel/Recovery do I need for this? And yet this AOSP, also supports CM based roms, much like Philz TW based Kernel...??
Click to expand...
Click to collapse
Well, stock CM kernel is pretty good, there's also the RAW kernel. Both come with standard CWR.
How do I keep flashing/changing these Kernels...?? Can I keep a copy of all the Kernels somewhere on the SD Card, and Flash into them via Stock Recovery?? As i was led to believe you did so with Philz one, as it wouldnt increase Samsungs Counter (another thing I need to get my head around...)
Click to expand...
Click to collapse
Here's how i do, i have a ROMS folder on the sdcard. Inside, 2 folders, TW and CM. Inside touchwiz i keep Touchwiz roms (one per directory) and kernels. Inside CM i keep CM roms, gapps, and mods.
If i'm going to flash for example this: [ROM] Sweet ROM V10.5 LT9 4.1.2 [NEW 12th Sept], i flash the rom and either PhilZ latest, or C.o.H. kernel. No need for GAPPS on TW roms.
If i'm going to flash next CM 10.2, i will boot to recovery, be greeted by Philz recovery, wipe everything, flash rom, flash gapps, flash kernel, flash mod. Simple
Philz recovery can flash CM roms, CWR recovery can flash TW roms. It's the NAND backups that you must be carefull.
So baring in mind, I am getting this device on Friday... what are my first instructions/steps to do to this device??
Running Stock Vodafone UK firmware, JellyBean 4.1.2 non-rooted.
Click to expand...
Click to collapse
First, i would copy PhilZ kernel to the root of the sdcard. Then i would boot to recovery (for now, standard samsung recovery) and flash it.
Reboot, reboot to recovery. Now you have PhilZ recovery and you can flash whatevah you see fit. I would start with a good Touchwiz based rom, see what the device was made to do, but without that carrier crapware. TW camera beats every other option out there. Then i would flash CM10.2, see how fast(er) the device became, see the limitations you get (camera is still good, just not as nice)
To be honest, i'm a CM guy. Touchwiz is SO UGLY, SO unfinishes, so unpolished. After having CM10.2/AOSP4.3, TW feels like a Nokia and Symbian. Unfortunately, camera has a few flaws on CM. I choose CM, sacrificing camera. You choose what best you like
If only there was a Kernel / Recovery that supported all... Gosh, the days of ZTE were so simple... Just had ClockWorkMod and that was it... lol
Click to expand...
Click to collapse
ZTE was simple once you got the grasp of it, the Note will become simple as well, after a while of tinkering with it, you'll get the concept of TW vs AOSP, PhilZ vs CWR, etc etc. With great power comes great responsability
Sorry to be such a pain/noob... / Thanks, Lister
Click to expand...
Click to collapse
Not a pain I was also a noob, and i made a few mistakes. Nothing major, but could be avoided
When you get the device, there's something you MUST backup. First thing you do after having root, is backup the EFS partition.
Inside it, there's a few files that have the device (hardware) config, namely, IMEI. Corrupt it, and you get a Wifi only Note
Hi DaedRic,
Sorry for the delay getting back to you...
It is. PhilZ is a Stock TouchWiz kernel, difference is the fact that it's SAFE, and the recovery. PhilZ recovery rocks
Click to expand...
Click to collapse
It certainly soundED (and still does) it. When I first read about Philz kernel, I thought that was it, one flash of that and job done... Rest can be done in this.... So wished Philz was a Universal Kernel for all ROMs lol Still hats off, it does look rather impressive even still.
Facts:
Philz Kernel is a Touchwiz ONLY kernel
GB is outdated
So is ICS
Touchwiz ICS is safe if using safe kernels.
If you're using a safe kernel, there's nothing you can do to trigger the bug
PhilZ does not work on AOSP/CM roms.
Click to expand...
Click to collapse
1) Ok, so I've got that Philz is only for TW based ROM, thats sunk in... So wished it could do all, simples lol
2) True, it is, but I always love to have a little play, nostalgia (spelling, who knows??) and go back once in a while... Did that with the Blade.
3) Same as 2) always like to tinker, see whats out there...
4) I should be fine providing its a TW rom running on Philz, or alternative kernel for CM/AOSP roms..
5) Phewww.... Well, it looks like there are only 3x kernels to choose from so cant go too wrong...?? lol
6) DARN IT!!! If only it could...
Well, stock CM kernel is pretty good, there's also the RAW kernel. Both come with standard CWR.
Click to expand...
Click to collapse
You threw me when you mentioned CWR, but I assume you mean ClockWork Recovery? (always know it as CWM). I've looked at RAW, COH and NX kernel for anything thats not TW based... Not sure which is the better to use...?? Is there just one of those kernels that will support all GB, ICS, JB roms...?
Here's how i do, i have a ROMS folder on the sdcard. Inside, 2 folders, TW and CM. Inside touchwiz i keep Touchwiz roms (one per directory) and kernels. Inside CM i keep CM roms, gapps, and mods.
If i'm going to flash for example this: [ROM] Sweet ROM V10.5 LT9 4.1.2 [NEW 12th Sept], i flash the rom and either PhilZ latest, or C.o.H. kernel. No need for GAPPS on TW roms.
If i'm going to flash next CM 10.2, i will boot to recovery, be greeted by Philz recovery, wipe everything, flash rom, flash gapps, flash kernel, flash mod. Simple
Philz recovery can flash CM roms, CWR recovery can flash TW roms. It's the NAND backups that you must be carefull.
Click to expand...
Click to collapse
Thats kinda similar to how I did it on the Blade, although obviously not setup for TW and CM based, as they were all CM based.. But had folders for GB, ICS and JB, and then had a Mods folder... So Ive taken note how you've done it, and started to create the folders, and drop as many files as I can in ready. Such as ROMs, Philz Kernel in the TW folder... But still trying to find a good CM/AOSP kernel... Do I need to use a Kernel if I install any of the Cyanogen ROMs? just as CM7, CM9, CM10 (do they come with their own Kernel or still need to find one?)
Which two kernels do you use, or do you test others out?? Is there some kind of (non TW) Universal one that can be applied to ALL other roms?
First, i would copy PhilZ kernel to the root of the sdcard. Then i would boot to recovery (for now, standard samsung recovery) and flash it.
Reboot, reboot to recovery. Now you have PhilZ recovery and you can flash whatevah you see fit. I would start with a good Touchwiz based rom, see what the device was made to do, but without that carrier crapware. TW camera beats every other option out there. Then i would flash CM10.2, see how fast(er) the device became, see the limitations you get (camera is still good, just not as nice)
To be honest, i'm a CM guy. Touchwiz is SO UGLY, SO unfinishes, so unpolished. After having CM10.2/AOSP4.3, TW feels like a Nokia and Symbian. Unfortunately, camera has a few flaws on CM. I choose CM, sacrificing camera. You choose what best you like
Click to expand...
Click to collapse
I will be picking the phone up in a pub (again), so I will have Philz Recovery done in there, just so I know its done and its safe... However I wont flash any ROMS until I am home, so I know I am safe, I have Internet access should anything go wrong... lol... But yes, Prolly play with stock ROM for a little while... I assume if I have Philz Kernel on there anyway (even though its JB based) I can go within Android, Settings, Security, and Reset it... So I loose all the customizations the previous user had, so its like new... So I will play with that for a bit... But then go to PAC ROM after that...
ZTE was simple once you got the grasp of it, the Note will become simple as well, after a while of tinkering with it, you'll get the concept of TW vs AOSP, PhilZ vs CWR, etc etc. With great power comes great responsability
Click to expand...
Click to collapse
I hope so, it doesnt take me long really to get use to how things work... and with most other things, Im not normally as nervous... Touchpad was a breeze to triple-boot. Just worried with this device, after hearing all the horror stories. But as long as i read and follow, I should be safe... should.... lol... Love the Spiderman quote too
Not a pain I was also a noob, and i made a few mistakes. Nothing major, but could be avoided
Click to expand...
Click to collapse
Thank you, you have been really really helpful, certainly gives me confidence to go through the motions that you have so clearly explained... appreciated
When you get the device, there's something you MUST backup. First thing you do after having root, is backup the EFS partition.
Inside it, there's a few files that have the device (hardware) config, namely, IMEI. Corrupt it, and you get a Wifi only Note
Click to expand...
Click to collapse
Oh yes, I did hear about that... and thanks for reminding me!! I shall do that in the pub before i forget anything else. I'll back it up to SD and to Cloud, just in case anything happens... thank you..
FX Explorer is a great File Manager, especially when digging around with Root access...
Thank you once again Im sure it will come clearer once I get it, and play with it more...
You threw me when you mentioned CWR, but I assume you mean ClockWork Recovery? (always know it as CWM). I've looked at RAW, COH and NX kernel for anything thats not TW based... Not sure which is the better to use...?? Is there just one of those kernels that will support all GB, ICS, JB roms...?
Click to expand...
Click to collapse
ClockWorkMod, ClockWork Recovery, same
Regarding kernels:
[KERNEL][AOSP] Raw Kernel r3 -- simple&fast kernel
[KERNEL][TW][LINARO][UV]c.o.h.'s HelloWorld [v1.3.7b][19.MAY.13]
[KERNEL][14/07] NX-Kernel v1.4.2:
STOP! This kernel supports ONLY CM10.1.x, AOKP-4.2.2, PA-4.2.2 ROMs.
It won't work on Samsung Jellybean/ICS, AOSP ICS, CM9 or CM10.
[21.08.2013][PhilZ-cwm6][n7000] v5.11.2 Stock Kernel+CWM6+Root+exFAT+NTFS-LT9
You should always read the thread title, and OP's posts, usually the first 2 or 3.
For Touchwiz roms, either go Stock with Philz (most custom roms already come with it) or go the extra mile with C.o.H. CoH has a few more governors, and things not available in stock, but might prove unstable in the wrong hands.
For CM, either remain stock, or go with NX Kernel for CM 10.1 or Raw V3 for CM10.1 or V3 for CM10.2 (they're differente).
s there just one of those kernels that will support all GB, ICS, JB roms...?
Click to expand...
Click to collapse
That should be impossible, there are a few kernels that claim to support multiple android, but in fact the bundle the differente kernels on the zip and when flashing in CWM detect the correct android version and flash the acording kernel.
Do I need to use a Kernel if I install any of the Cyanogen ROMs? just as CM7, CM9, CM10 (do they come with their own Kernel or still need to find one?)
Which two kernels do you use, or do you test others out?? Is there some kind of (non TW) Universal one that can be applied to ALL other roms?
Click to expand...
Click to collapse
If going Touchwiz, i either use PhilZ or if i'm feeling like tinkering go with CoH. CoH as the Interactive governor, i kind of like it, even though it's not the best governor for Exynos devices. (or so they say..)
If i'm going CM, i either use CM kernel, or flash RAW V3. CM CWM calls internal storage sdcard0 and external sdcard1, RAW calls it internal and external. RAW was compiled with Linaro, should provide a slight boost, but any major effects are probably placebo.
So there you go, TW-> Philz or COH ; CM-> Original or RAW
I will be picking the phone up in a pub (again), so I will have Philz Recovery done in there, just so I know its done and its safe... However I wont flash any ROMS until I am home, so I know I am safe, I have Internet access should anything go wrong... lol... But yes, Prolly play with stock ROM for a little while... I assume if I have Philz Kernel on there anyway (even though its JB based) I can go within Android, Settings, Security, and Reset it... So I loose all the customizations the previous user had, so its like new... So I will play with that for a bit... But then go to PAC ROM after that...
Click to expand...
Click to collapse
Uhm.. should be easy. Go [21.08.2013][PhilZ-cwm6][n7000] v5.11.2 Stock Kernel+CWM6+Root+exFAT+NTFS-LT9, and go to post 3, in this section:
Code:
Recovery (.zip) packages instructions - Will also root your phone * recommanded method *
They come in the form of -signed.zip files that can be flashed in stock recovery 3e: No Yellow Triangle
Find this link : http://d-h.st/users/philz_touch/?fld_id=16061#files
Open folder v5.11.2, download PhilZ-cwm6-XXLT9-ORA-5.11.2-signed.zip, copy it to SD Card root, reboot to stock recovery, and flash it.
Only do this if you're running Official JB 4.1.2, otherwise you need other kernel version.
Thank you once again Im sure it will come clearer once I get it, and play with it more...
Click to expand...
Click to collapse
Yes it will
Hi DaedRic,
Guess what I picked up yesterday, yippie Im now part of the N7000 gang... and I must say, I'm LOVING IT!!!!
ClockWorkMod, ClockWork Recovery, same
Regarding kernels:
[KERNEL][AOSP] Raw Kernel r3 -- simple&fast kernel
[KERNEL][TW][LINARO][UV]c.o.h.'s HelloWorld [v1.3.7b][19.MAY.13]
[KERNEL][14/07] NX-Kernel v1.4.2:
STOP! This kernel supports ONLY CM10.1.x, AOKP-4.2.2, PA-4.2.2 ROMs.
It won't work on Samsung Jellybean/ICS, AOSP ICS, CM9 or CM10.
[21.08.2013][PhilZ-cwm6][n7000] v5.11.2 Stock Kernel+CWM6+Root+exFAT+NTFS-LT9
Click to expand...
Click to collapse
I've downloaded various kernels, and placed them in the relevant folders, so should make it either to use/choose when flashing ROMs... I think Im getting used to which kernel is for which rom... Just a little confused about the PAC (ASOP rom based?). Was using stock CM kernel, but then flashed RAW v3 CM10.2 (as on PAC, with Android 4.3) as I thought it offered more kernels/performance tweaks... But looks the same, still, it works so not complaining... lol
You should always read the thread title, and OP's posts, usually the first 2 or 3.
For Touchwiz roms, either go Stock with Philz (most custom roms already come with it) or go the extra mile with C.o.H. CoH has a few more governors, and things not available in stock, but might prove unstable in the wrong hands.
For CM, either remain stock, or go with NX Kernel for CM 10.1 or Raw V3 for CM10.1 or V3 for CM10.2 (they're differente).
Click to expand...
Click to collapse
Must say, I did love the Philz Kernel / Touch CWR feature, amazing... wished his CWR could be used in all ROMs Gonna try the NX Kernel later...
That should be impossible, there are a few kernels that claim to support multiple android, but in fact the bundle the differente kernels on the zip and when flashing in CWM detect the correct android version and flash the acording kernel.
Click to expand...
Click to collapse
Guess your refering to the Hydra(summit) Kernel as I just saw that mentioned the other day in a different website that claims it works on ALL roms... May have a look at that... Whats the worst that will if I install the wrong kernel for the wrong OS?? I assume all mod/developed kernels here are patched for eMMC, so that shouldnt be an issue... I guess it will just mean the Android will not boot...?? It wont cause any lasting damage will it, and I can simply re-flash...??
If going Touchwiz, i either use PhilZ or if i'm feeling like tinkering go with CoH. CoH as the Interactive governor, i kind of like it, even though it's not the best governor for Exynos devices. (or so they say..)
If i'm going CM, i either use CM kernel, or flash RAW V3. CM CWM calls internal storage sdcard0 and external sdcard1, RAW calls it internal and external. RAW was compiled with Linaro, should provide a slight boost, but any major effects are probably placebo.
So there you go, TW-> Philz or COH ; CM-> Original or RAW
Click to expand...
Click to collapse
I downloaded Philz, and rooted and installed Recovery.... Must admit, I didnt really like the official stock TW Rom... Seemed ugly and slow/laggy.... PAC 4.3 on the other hand, AMAZING!!! LOVING IT!!!! And it brings back features that were in the original PAC, but missed in the Android 4.2 rom (well, for the Blade it did anyway) as loving the weather changes... this is awesome!!!
Uhm.. should be easy. Go [21.08.2013][PhilZ-cwm6][n7000] v5.11.2 Stock Kernel+CWM6+Root+exFAT+NTFS-LT9, and go to post 3, in this section:
Code:
Recovery (.zip) packages instructions - Will also root your phone * recommanded method *
They come in the form of -signed.zip files that can be flashed in stock recovery 3e: No Yellow Triangle
Find this link : http://d-h.st/users/philz_touch/?fld_id=16061#files
Open folder v5.11.2, download PhilZ-cwm6-XXLT9-ORA-5.11.2-signed.zip, copy it to SD Card root, reboot to stock recovery, and flash it.
Only do this if you're running Official JB 4.1.2, otherwise you need other kernel version.
Click to expand...
Click to collapse
Well I got rid of official TW rom now, and running PAC 4.3... All has gone well... I didnt install any Kernel to start with, as I thought/assumed the stock CM one would be ok?? Am I right to think this, or did I need to install a Kernel straight after flashing..? Anyway, I have now installed RAW... and may try NX soon too....
However, when installed PAC 4.3 rom... Its got rid of Philz Recovery, and just has a standard ClockWorkMod recovery... Is this normal and is this safe to do all the normal wipes in...?? Also if I am running Android 4.3, am I safe to do the Factory Reset within this version of Android too??
Can I install Philz Recovery from the current CWM, even if it's just to use for Flashing (I appreciate it will disappear again when installing another rom) But wondered if I could do it in standard CWM or will it introduce the Yellow Triangle...??
I also backed up my EFS straight away, as soon as I got root... Both by navigating to the files directly, and letting Philz Recovery do it too... So I should be safe...
But yes, loving this device....
I do think I have a faulty battery though (like the sticker says on it...) as I was charging it, and the battery was going down whilst plugged in. Still, after installing RAW... The battery/N7000 feels cooler too and is charging normally... But I shall still but an official battery replacement anyway, just to be on the safe side....
Many many thanks for all your help... Im sure I may have some more questions, but you've been a great help... THANK YOU!!!
Darn, can't use NX Kernel as I see it only supports CM10.1 (Android 4.2.x) and now CM10.2 (Android 4.3)
Darn what a pity, as that was starting to sound and look mighty awesome....
Oh well, RAW it it is....
If only there was a way to get the LagFree Governor in, as thats pretty neat....

Categories

Resources