[Q] Bricking a Nook Color - Nook Color General

Is it possible to "brick" a nook color? I just got mine yesterday, rooted, and decided I didn't like the stock ROM so used CWM to install nookie-froyo. Had some issues with that, and was able to revert back with CWM.
I'd like to tinker more, but I'm a total noob with Android and I don't want to be doing anything that is irreversible. Does installing through CWM do anything that I couldn't fix if I screwed up?
I just want to make sure I don't ruin my new toy only a day after getting it. I'm ready to try froyo again and look into using an OC'd kernel.

With the NC having boot priority on the SD slot the chances of any kind of software induced brick is very very low. You always run the risk of something crazy happening , but it's not a worry I personally have.

miemens said:
With the NC having boot priority on the SD slot the chances of any kind of software induced brick is very very low. You always run the risk of something crazy happening , but it's not a worry I personally have.
Click to expand...
Click to collapse
Agreed. Short of trying to mess up the boot order or disintegrating the sdcard... it would be tough for a real brick.

Ah, so in other words, if I screw up the on board flash, I can always throw an img on my SD card slot, and do the same process as autonooter?
Good to know, thanks.

claudius753 said:
Ah, so in other words, if I screw up the on board flash, I can always throw an img on my SD card slot, and do the same process as autonooter?
Good to know, thanks.
Click to expand...
Click to collapse
More or less that's correct. As far as I see, something physical would have to be damaged in order for you to fully brick. With that in mind, it's not out of the realm of possibility for a severely over aggressive overclock or something of that nature to cause physical damage over time, but all of the OC kernels available here seem well below the level required to fry anything.

claudius753 said:
Is it possible to "brick" a nook color? I just got mine yesterday, rooted, and decided I didn't like the stock ROM so used CWM to install nookie-froyo. Had some issues with that, and was able to revert back with CWM.
I'd like to tinker more, but I'm a total noob with Android and I don't want to be doing anything that is irreversible. Does installing through CWM do anything that I couldn't fix if I screwed up?
I just want to make sure I don't ruin my new toy only a day after getting it. I'm ready to try froyo again and look into using an OC'd kernel.
Click to expand...
Click to collapse
There shouldn't be issues with the OC kernel but you do always run the risk of burning out your processor, which is basically bricking your device if you take bricking to mean turning into a brick.

claudius753 said:
Is it possible to "brick" a nook color? I just got mine yesterday, rooted, and decided I didn't like the stock ROM so used CWM to install nookie-froyo. Had some issues with that, and was able to revert back with CWM.
I'd like to tinker more, but I'm a total noob with Android and I don't want to be doing anything that is irreversible. Does installing through CWM do anything that I couldn't fix if I screwed up?
I just want to make sure I don't ruin my new toy only a day after getting it. I'm ready to try froyo again and look into using an OC'd kernel.
Click to expand...
Click to collapse
Thanks to the Nook Colors characteristic of booting from the SDcard before the internal, it is very near impossible to brick your nook. Your always able to boot into a Clockwork Mod Recovery sd card even at the worst of times, and from there you can flash a backup, custom ROM, etc.

I take bricking as "Something where it won't boot and isn't recoverable." I know that an OC can do physical harm, I just was wondering that if I flashed a ROM and it went horribly wrong, is it able to be recovered or not. It seems that, yes, it very well is. Which means that I am much more comfortable with trying different roms and kernels, etc.
Thanks again, everyone.

Related

[Q] Multiple questions on the same subjects, Please forgive the noobness guys.

Is there a thread that shows the users marginal picks of the best combo's of mods, roms, hardware, and apps? I tried to search for it but didn't seem to find it.
(Please keep in mind most of the stuff I have found is dated from 2009 and CM6 was released yesterday)
Basically, I am interested in rooting my G1 and updating it to CM6.??? But the radio (danger/death.spk) scare has a hold of me. I want to make sure that I can go back to factory without problems. (In case I sell the phone)
What about running apps from SD? Is it effective on a 8GB class 2 card? And if so what are the advantages of it? (Speed increase, load times, ect.) Can this be done without flashing/rooting?
Is there a way to transfer files over bluetooth or Wi-Fi without having to root?
There are quite a few things other than this but, these are the most important that I can think of. And since I have never messed with rooting or ROMS I have no idea if it is even possible to install apps after flashing with a new ROM.
Once again, forgive me in my wonderment of noobness! I am another droid that has seen the fading light of win-mo and has crossed over!
Thank you to all in advance for their help!
Ragewerx said:
Is there a thread that shows the users marginal picks of the best combo's of mods, roms, hardware, and apps? I tried to search for it but didn't seem to find it.
(Please keep in mind most of the stuff I have found is dated from 2009 and CM6 was released yesterday)
Basically, I am interested in rooting my G1 and updating it to CM6.??? But the radio (danger/death.spk) scare has a hold of me. I want to make sure that I can go back to factory without problems. (In case I sell the phone)
What about running apps from SD? Is it effective on a 8GB class 2 card? And if so what are the advantages of it? (Speed increase, load times, ect.) Can this be done without flashing/rooting?
Is there a way to transfer files over bluetooth or Wi-Fi without having to root?
There are quite a few things other than this but, these are the most important that I can think of. And since I have never messed with rooting or ROMS I have no idea if it is even possible to install apps after flashing with a new ROM.
Once again, forgive me in my wonderment of noobness! I am another droid that has seen the fading light of win-mo and has crossed over!
Thank you to all in advance for their help!
Click to expand...
Click to collapse
Don't believe there is a thread of that nature.
You don't need the danger spl anymore. Do a search for firerat's mtd patch and that will work for you. As long as you read and do follow the instructions there is no fear involved even with danger spl. Just dont make a mistake. You can always go back with the dreaming.nbh file. Always a way to unroot. You will want to get amonra 1.7.0 for recovery. And for your sake nandroid.
If you're not running out of internal memory i dont believe there is a real advantage to using a2sd but the new roms have a new method implemented. I dont think you can use a2sd with stock.
Do a search for blue tooth file transfer in the market. Don't believe you need root access to use it.
You can always install apps after rooting and flashing a custom rom. You will still have market and everything. Just makes your phone better/faster. Just keep reading and you will find a huge amount of info here in these threads.
Good luck.
Firerats mtd hack can fake your spl for you. So you don't have to worry about flashing danger spl and bricking. Its just what all of us old guys run. Because when we first started. There wasn't any other way for us. So read up on rooting and firerats hack and you should be good. No need for 1.33.2005 death anymore.
sent from my superfroyo dream

need help with the 1.1.0

i have rooted and flashed the hero many many times, but this one makes me more nervous I dont have much time to read as it is a birthday gift, but i keep reading about problems with youtube and gmail.. do they have to be linked before rooting.. whats the best rom with 1.1.0..
i just dont want to miss any vitally important steps and screw this up.. any help? Is there a step by step guide.. thanks much
I would start here http://forum.xda-developers.com/showthread.php?t=872003
After rooting your device you can decide to stay on the stock rom and just have more functionality or you can move to a variety or other roms running Andoid Eclair,Froyo,Gingerbread, or Honeycomb.
Each of these ROM has their own ups and downs. If this is a gift for a non-techy person I would suggest just using a rooted stock with some tweaks or rooting and installing Eclair as these seem to be the most stable options at the moment.
Because the Nooks has priority on SDcard booting you can run any of these roms off the SDcard as well while leaving your stock Nook OS in place. This is a great option if you just want to give a bunch of different ROMs a test. Also the boot priority of the SDcard makes 'bricking' the nook nearly impossible. So while you can still screw up your Nook you will most surely be able to fix it.
Thanks for your help.. I rooted it and left it stock for now.. if he wants something different i will change it to Eclair.. its **Beautiful** I am impressed.. might have to pick one up for myself.. Thanks

Absolute best/easiest way to completely back up EVERYTHING stock, then dual boot?

To begin, I have a basic knowledge of Android and how it works. I've rooted, bricked, and unbricked my fair share of Android phones, but the NC is a bit of a different animal to me... Phones are pretty consistent in their methods, the NC kind of caught me off guard.
I've perused quite a bit of threads in both the general and dev forums, and found multiple ways of doing multiple things which got a bit confusing, compounded by the fact that Froyo and Eclair methods vary quite a bit on some subjects.
I have a 1.2.0 "blue dot" NC. Things I know to be true:
Have to use latest CWM SD and replace the boot and ramdisk in order to root with manualnooter.
Have to use the correct 2/4/8GB image for my MicroSD (although the size-agnostic SD image threw me for a bit of a loop, but I'll stick with what I know works).
Here are my goals:
I want a complete backup of stock nook in case I have to start over for some reason. Boot, system, ROM, permissions, everything. What is the easiest and/or most complete way of doing so?
I'd like to dual boot stock and CM7 nightlies off of eMMC and use SD strictly for storage (and use a separate SD for recovery). If that's not possible, I'd like CM7 to be on eMMC and stock to be on SD.
If you've got the time and want to write me up a handheld walkthrough, that would be nice, but I don't expect or really need that. All I'm looking for is links to threads that will give me the information I need to figure out for myself what the best way of doing this is. There are a lot of threads for older versions of things, and some of the discrepancies between here and Nookdevs have confused me at times.
Thanks in advance for any help you can offer.
There is a thread HERE , less than 5 posts under this one that explains exactly what you want done.
RussianMenace said:
There is a thread HERE , less than 5 posts under this one that explains exactly what you want done.
Click to expand...
Click to collapse
I saw that thread and deduced that it was probably the best one. My only question left is, how do I make a complete 100 percent backup of stock in case I bugger something up and need to start over?
stankcheeze said:
I saw that thread and deduced that it was probably the best one. My only question left is, how do I make a complete 100 percent backup of stock in case I bugger something up and need to start over?
Click to expand...
Click to collapse
After you flash clockwork recovery, you can use it to make a nandroid (1:1) backup of your stock setup.
To get a backup: boot into CWM (whether from an sdcard or from emmc) and make a backup - just make sure you have a big enough card.
Then start flashing the zips!
That was my #1 question, I suppose. Nandroid works the same on NC as it does all other devices? I had just read conflicting reports about people fooling with the /system and /data and having trouble restoring from there even after the 8-boot "trick".
Yup, it does. I have needed to flash to stock and to make a bootable nook sd card.
Thanks for all the help, guys! Time to dig into this thing!

CWM on eMMC or SD?

So I've been on the Android rooting scene for almost two years now (Original Droid owner), but just recently acquired a Nook. I am running CM7 from eMMC, and want to flash clockwork to make updating nightlies easier. I have been running Clockwork from an SD card. Are there any downsides to running Clockwork from eMMC? Can't I always just remove clockwork and have the stock recovery on there?
I never ran CWM from SD, but I find it very convenient having it on eMMC, particularly as I do shuffle my ROMs and partitions periodically just for experimentation's sake.
What you lose is the ability to use eight failed boots to trigger stock recovery. There are situations where that would come in handy--such as hardware faults in the SD slot or screen that make it difficult to use CWM to flash a stock zip, assuming you have a warranty and want to make a claim on those hardware faults.
Taosaur said:
I never ran CWM from SD, but I find it very convenient having it on eMMC, particularly as I do shuffle my ROMs and partitions periodically just for experimentation's sake.
What you lose is the ability to use eight failed boots to trigger stock recovery. There are situations where that would come in handy--such as hardware faults in the SD slot or screen that make it difficult to use CWM to flash a stock zip, assuming you have a warranty and want to make a claim on those hardware faults.
Click to expand...
Click to collapse
Thanks for the info, I just got this and its refurbished, so I think I may give it a few weeks before making the transition just in case there are any hardware issues.

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