[Q] irritating ~ Note getting slower - Galaxy Note GT-N7000 Q&A, Help & Troubleshooting

I had posted a similar thread earlier, but it had a different reason and a different solution, yea, KL7 was the solution..but its been a week since I upgraded and now unfortunately my note is becoming slower!!!
what could be the reason. Im on stock kl7 meant for DBT. i had s2 earlier (nw its with my wife) and i really miss the superspeed s2. i have a iphone 4 with me (secondary phone) and now due to timesaving efforts im using more of iphone 4 eventhough i hate the small size. (pls dont call me a iphone fan!!!). i need note's display and size and s2's speed!!
any latest stock rom's??? (non wipe versions???)

khan.dharvesh said:
I had posted a similar thread earlier, but it had a different reason and a different solution, yea, KL7 was the solution..but its been a week since I upgraded and now unfortunately my note is becoming slower!!!
what could be the reason. Im on stock kl7 meant for DBT. i had s2 earlier (nw its with my wife) and i really miss the superspeed s2. i have a iphone 4 with me (secondary phone) and now due to timesaving efforts im using more of iphone 4 eventhough i hate the small size. (pls dont call me a iphone fan!!!). i need note's display and size and s2's speed!!
any latest stock rom's??? (non wipe versions???)
Click to expand...
Click to collapse
Why don't you use Custom ROM??

ranjan.alva said:
Why don't you use Custom ROM??
Click to expand...
Click to collapse
ive never used custom rom in any of my android devices..ive following 'fears'
1. will it affect any major aspect of the phone (ive seen many threads like battery issues,wifi issues etc etc..)
2.if later i want to update latest firmware via kies, wil that be a problem>?
3.will i wipe out my data/apps etc?
4.which is the best custom rom available?>

khan.dharvesh said:
ive never used custom rom in any of my android devices..ive following 'fears'
1. will it affect any major aspect of the phone (ive seen many threads like battery issues,wifi issues etc etc..)
2.if later i want to update latest firmware via kies, wil that be a problem>?
3.will i wipe out my data/apps etc?
4.which is the best custom rom available?>
Click to expand...
Click to collapse
1. Possibly. Possibly not. Depends on the ROM. Usually the ROM developer will provide detailed information about what's working, what's working better, what's working worse, and what's not working at all. It's up to you to find the best overall fit.
2. You'll have to do a CWM backup and flash back to stock in order to use Kies. Then again, that's kind of a moot point if you're using a custom ROM anyway. Usually dev's will bake in the latest/best working firmware into their ROM's anyway, so Kies really isn't that big of an issue. I've personally never had a need for Kies; I've always just used Odin. It's way better anyway.
3. Depends on the ROM again. However, coming from stock to a custom ROM, it's highly recommended that A) you do a backup of your stuff and B) you perform a full wipe (keep your backup data in tact obviously).
4. That's up to you really. What may be the best ROM for me might not be well suited for you. Have a look in the dev section and see what's out there!

Jade Eyed Wolf said:
1. Possibly. Possibly not. Depends on the ROM. Usually the ROM developer will provide detailed information about what's working, what's working better, what's working worse, and what's not working at all. It's up to you to find the best overall fit.
2. You'll have to do a CWM backup and flash back to stock in order to use Kies. Then again, that's kind of a moot point if you're using a custom ROM anyway. Usually dev's will bake in the latest/best working firmware into their ROM's anyway, so Kies really isn't that big of an issue. I've personally never had a need for Kies; I've always just used Odin. It's way better anyway.
3. Depends on the ROM again. However, coming from stock to a custom ROM, it's highly recommended that A) you do a backup of your stuff and B) you perform a full wipe (keep your backup data in tact obviously).
4. That's up to you really. What may be the best ROM for me might not be well suited for you. Have a look in the dev section and see what's out there!
Click to expand...
Click to collapse
thanks, so custom rom is one solution which i would definitely look into. and it was seriously helpful reply.

khan.dharvesh said:
ive never used custom rom in any of my android devices..ive following 'fears'
1. will it affect any major aspect of the phone (ive seen many threads like battery issues,wifi issues etc etc..)
2.if later i want to update latest firmware via kies, wil that be a problem>?
3.will i wipe out my data/apps etc?
4.which is the best custom rom available?>
Click to expand...
Click to collapse
yeah you got some points ter, even me too still in Stock rom coz am waiting for CM9.

Related

[Q] Totally confused about kernel/ROM/lagfix

I have been trying to find answers for a week now and have found a lot of info. The problem is most of the info is contradictory and I'm not really sure which is good and which is not. I currently have an AT&T Samsung Captivate, firmware ver 2.2, kernel ver. 2.6.32.9 build# FROYO.UCKB1. I believe that is the stock At&t froyo build. It is rooted, I do have SGS tools (which I don't really understand what all it can do for me) and Titanium backup (which I've not tried to use yet for fear of breaking my phone). I run 91PandaHome and a bunch of apps I like.
My problem is that the phone sometimes is just really sluggish, certain programs really kill it. For example, I have PlantVsZombies which mostly runs ok, but sometimes slows down and worse 3 out of 5 times I play will not close. I have to power/volume up reboot to get out of the game. Other programs occasionally do this to me, but not as often.
I've been reading up and see that there are lagfixes, and understand that samsung apparently chose a ****ty file system, but I don't understand android well enough to know what's safe. What I want to know is what is as of today the safest, easiest way to fix the lag. I think I am going to be told something that changes the file system to ext4 is what I want, but I really don't understand what will be safe to use for that. I thought I wanted OneClickLagFix, then I found that maybe Voodoo was what I wanted, and now it seems that neither is currently being developed. Reliability, ease of transition and ease of putting it back to stock are important factors for me.
Suggestions, links and general help will be greatly appreciated.
Try going to a custom rom where all of that is done for you. Since you are new to this, I suggest you go look up the rom Serendipity 6.4, it's very easy to install and has it's own thread in the development section.
fianor said:
I have been trying to find answers for a week now and have found a lot of info. The problem is most of the info is contradictory and I'm not really sure which is good and which is not. I currently have an AT&T Samsung Captivate, firmware ver 2.2, kernel ver. 2.6.32.9 build# FROYO.UCKB1. I believe that is the stock At&t froyo build. It is rooted, I do have SGS tools (which I don't really understand what all it can do for me) and Titanium backup (which I've not tried to use yet for fear of breaking my phone). I run 91PandaHome and a bunch of apps I like.
My problem is that the phone sometimes is just really sluggish, certain programs really kill it. For example, I have PlantVsZombies which mostly runs ok, but sometimes slows down and worse 3 out of 5 times I play will not close. I have to power/volume up reboot to get out of the game. Other programs occasionally do this to me, but not as often.
I've been reading up and see that there are lagfixes, and understand that samsung apparently chose a ****ty file system, but I don't understand android well enough to know what's safe. What I want to know is what is as of today the safest, easiest way to fix the lag. I think I am going to be told something that changes the file system to ext4 is what I want, but I really don't understand what will be safe to use for that. I thought I wanted OneClickLagFix, then I found that maybe Voodoo was what I wanted, and now it seems that neither is currently being developed. Reliability, ease of transition and ease of putting it back to stock are important factors for me.
Suggestions, links and general help will be greatly appreciated.
Click to expand...
Click to collapse
Just a few quick things:
Titanium backup is a good friend to have on your phone. It won't break it - it will just take snapshots (for lack of a better phrase) of your apps so that you can restore them later if you need to.
Most lagfixes are cooked into kernels, so using lagfix will most likely go hand-in-hand with flashing to a custom rom. Not that you can't lagfix stock, but statistically speaking, lagfix will be done with a new kernel via the Clockworkmod Recovery Menu.
As for general fixing of lagginess... (READ UP FIRST) Flash a custom Rom (READ MORE). Most of the problems you're experiencing (ARE YOU READING UP ON FLASHING?) should be fixed by flashing (DO MORE READING) a custom rom. Do some research on roms and pick one that you think you'll like. (Note - don't post questions asking which one to do, it tends to be a bit of a touchy subject on the forum.) If you're wanting to be cautious, it would be safer to stay with a Froyo-based rom, as they're more tested and there's less danger involved (specifically, you don't have to flash bootloaders, which is the area where you can get a real brick).
Oh, and (shameless self plug) if you need to know what different terminology and items on the forum mean, just click the link in my signature.
jmtheiss said:
Just a few quick things:
Titanium backup is a good friend to have on your phone. It won't break it -
Click to expand...
Click to collapse
Actually, it CAN break your phone if you don't know how to use it. Backing up is safe, but never, ever restore system data with TiBu when changing ROMs and only restore app data you know is safe.
I would recommend staying away from any Gingerbread-based ROMs until you have a better understanding of the phone and the process. Andromeda 3 is a good choice for a Froyo-based ROM and is very easy to flash, but do your research on the process before you attempt it. Almost any custom ROM will have a lagfix in the kernel and performance will be noticeably better than stock. You will likely have to redo your root after installing a new ROM, so read up on that process, too.
jmtheiss said:
As for general fixing of lagginess... (READ UP FIRST) Flash a custom Rom (READ MORE). Most of the problems you're experiencing (ARE YOU READING UP ON FLASHING?) should be fixed by flashing (DO MORE READING) a custom rom.
Click to expand...
Click to collapse
I lol'd at the "()" parts
To build on jmtheiss post. For "reliability" look for a KB1 based ROM as this is what your phone is currently running, and is the newest version of firmware written specifically for the AT&T captivate. You won't come across any major issues that make the phone unusable, nor any "annoying" bugs. Then if your feeling more adventurous, and have gotten a solid understanding of the process of flashing ROMs, look to I9000 based 2.2.x ROMs, and lastly 2.3.x based ROMs.
For "ease of transition" start by getting the SGS Kernel Flasher or Heimdall to change the kernel. From there you can get past 3e recovery and you'll be free to make other changes.
For "ease of putting it back to stock" first find out what is your stock. Since this phone technically has 3 different "stock" firmwares. Then get a copy of that firmware (and steps on how to flash it) and keep it on your computer, in a location you'll be able to find easily in case of problems. Depending on how far "to the dark side" you go, will effect just how much of the "stock" files you'll need to keep as backups.
Personally I'd suggest this ROM as it's whats currently on my phone. Many have started off with Cognition and it's still a crowd fav. Both are KB1 based ROMs

First time using Android, please give some advices!

Hi all, in a couple of days time I will be receiving my first ever Android device, the Motorola Milestone. I've already done some research on the phone as well as on Android itself, and understood most of the necessary basics. However, there are still many things I don't understand quite yet, and would like some help with clarifying them.
My first question is regarding the custom roms. I myself have been a long time user of Windows Mobile so I know most of the stuff that is relevant to Android as well. From what I know, the bootloader on the Milestone is still locked, but people have found ways to load custom roms on it. Can someone link me to the guide on how to do this? Now before someone tell me to search on the forum or on Google (which I already have), I just want to point out that the ones I found seemed to be outdated, and that they're for older Android versions??
My 2nd question is, do custom roms like IceandFire or Froyomod come with their own custom kernels? Because I want to be able to overclock my phone, and if it comes installed with its own kernel then I don't want to risk bricking it by flashing another kernel on top of it......I hope that makes sense??
3rd question is, which rom is the best for speed and battery? I'm guessing it's IceandFire and it builds upon the latest CM7?
And lastly, are there any crucial apps that you guys recommend I should install, or any tweaks etc I should use?
chaoscreater said:
Hi all, in a couple of days time I will be receiving my first ever Android device, the Motorola Milestone. I've already done some research on the phone as well as on Android itself, and understood most of the necessary basics. However, there are still many things I don't understand quite yet, and would like some help with clarifying them.
My first question is regarding the custom roms. I myself have been a long time user of Windows Mobile so I know most of the stuff that is relevant to Android as well. From what I know, the bootloader on the Milestone is still locked, but people have found ways to load custom roms on it. Can someone link me to the guide on how to do this? Now before someone tell me to search on the forum or on Google (which I already have), I just want to point out that the ones I found seemed to be outdated, and that they're for older Android versions??
My 2nd question is, do custom roms like IceandFire or Froyomod come with their own custom kernels? Because I want to be able to overclock my phone, and if it comes installed with its own kernel then I don't want to risk bricking it by flashing another kernel on top of it......I hope that makes sense??
3rd question is, which rom is the best for speed and battery? I'm guessing it's IceandFire and it builds upon the latest CM7?
And lastly, are there any crucial apps that you guys recommend I should install, or any tweaks etc I should use?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=983516
This is still the best way to get a custom ROM loaded up onto your phone. What you want to start with is flashing the vulnerable recovery from http://android.doshaska.net/rootable by using RSD Lite. To do so, you need to put the phone into Bootloader mode (power+Dpad-up) You can google RSD Lite, make sure you use the latest version along with the latest USB Driver version from Motorola.
RSD Lite is a very finicky program, if you have any errors flashing, your best bet would be to try this post: http://androidforums.com/droid-all-...hing-process-0x7100-rsd-lite.html#post1274587
Once you flash the VR (vulnerable recovery), you will want to put OpenRecovery on your SD Card. I recommend using OR 1.46 and placing FuFu's minimod on the SD Card as well. It will overwrite existing files in OR (look for it in Milestone Development). From here you can root the phone in OR (by using power+x, then camera+volume up) and reboot, backup all data you want saved, before flashing a ROM.
Once that is done, get the custom ROM that you want (I find speed + battery can be Cronos, CM7 or FroyoMOD for a Froyo ROM) and place it in OpenRecovery/updates. You will also want the most up-to-date version of Google Apps for Cronos or any Gingerbread ROM (except MIUI).
Gapps: http://goo-inside.me/gapps/gapps-gb-20110613-signed.zip
Now, turn the phone off, and put it into recovery mode (power+x, then camera+volume up), select apply update.zip and you are now into OpenRecovery.
Here is where you will flash your custom ROM and Gapps. Wipe both cache partition and dalvik cache, then wipe all data. Select Apply Update under Miscellaneous Menu and select the ROM you want. Once it is done, wipe both caches (not data) and flash Gapps. Wipe caches again. Finally, change the baseband to your country and reboot.
The first reboot will take a while, as the ROM is configuring itself for first time use.
That is how to flash a custom ROM and get started.
2- Custom kernels are not available for Milestone, as our bootloader is locked. Overclocking the phone is done through the 10overclock file in system/etc/init.d . All ROMs that I know of are overclock, most to 1GHz (from 550MHz). You will not be able to flash any kernels, and DO NOT try ROM Manager, it will temporarily brick your phone.
Crucial apps, I would say are Root Explorer, TitaniumBackup. Those are the two that are very useful for root users, if you flash multiple ROMs or need to access system files.
Hope this helped.
awesome, thanks for the reply mate!
Hmm 2 things i'm confused with. Isn't there an app called "Milestone Overclock" that lets u overclock without installing custom kernels?
Also, from what I know you need to have the bootloader unlocked in order to install custom roms. I already know that Motorola is still keeping the bootloader locked and that as of now, there isn't a way to unlock it. Then how come we can install custom roms?
Also, since you mentioned ROM Manager, I did a quick search and it seems to be able to manage multiple custom rom installs that you have. But then you said don't try it or it will brick the phone, so I don't understand whether I can install it or not?? Personally, I love testing out different roms as well as new builds. It would be nice to dual boot or choose between different roms to use. But i'm not sure whether I want to go forward with this since your comment implies to me that I shouldn't install Rom Manager?
Lastly, this is the part I found most confusing with Android (or with Windows Mobile as well). I found some guides that tells you to install Clockwork Recovery Mod or something like that. Some of them even mentioned using Nandroid or something. There seems to be different methods & tools/softwares for different devices (or even the same device) and it can be confusing to keep up with them. My question is, are there major differences between them? Which one is better and should I keep them up to date?
chaoscreater said:
awesome, thanks for the reply mate!
Hmm 2 things i'm confused with. Isn't there an app called "Milestone Overclock" that lets u overclock without installing custom kernels?
Also, from what I know you need to have the bootloader unlocked in order to install custom roms. I already know that Motorola is still keeping the bootloader locked and that as of now, there isn't a way to unlock it. Then how come we can install custom roms?
Also, since you mentioned ROM Manager, I did a quick search and it seems to be able to manage multiple custom rom installs that you have. But then you said don't try it or it will brick the phone, so I don't understand whether I can install it or not?? Personally, I love testing out different roms as well as new builds. It would be nice to dual boot or choose between different roms to use. But i'm not sure whether I want to go forward with this since your comment implies to me that I shouldn't install Rom Manager?
Lastly, this is the part I found most confusing with Android (or with Windows Mobile as well). I found some guides that tells you to install Clockwork Recovery Mod or something like that. Some of them even mentioned using Nandroid or something. There seems to be different methods & tools/softwares for different devices (or even the same device) and it can be confusing to keep up with them. My question is, are there major differences between them? Which one is better and should I keep them up to date?
Click to expand...
Click to collapse
I have tried Milestone Overclock, but I never really used it to overclock the phone. I prefer changing the voltages and speeds with the 10overclock file. If you read the description of Milestone overclock, it "tricks" the kernel into thinking it's supposed to run at a certain speed.
ROM Manager and Clockwork Recovery Mod do not work on Milestone. The only recovery that works with the Milestone is OpenRecovery or Androidiani OpenRecovery. Unfortunately, the only way to flash the ROMs is through OR or AOR, so you will have to repeat the processes every single time. I have gotten used to where all of the options are for FuFu's Minimod, so I am able to do it quite efficiently
The best way to backup a ROM, system data and the such is by Nandroid backup. That is the only sort of backup that you can do. It is recommended to do one every time you flash a custom ROM, but I only did it after I rooted and before I flashed my first custom ROM. You can do it through OR. That is the only way that will work. CWM and ROM Manager will just temp brick the phone and you will have to reflash a stock SBF all over again.
i see.....in that case there's no way to install 2 different roms to allow dual booting then? What about the app "Boot Manager", will that work? I found it on this site here:
http://www.androidpolice.com/2011/0...ted-user-should-know-about-part-4-apps-26-33/
One last question, I came across this popular app that is recommended by many Android users, called Apps2SD. My understanding to this is that by default, any apps/games that you install on your device will install to the internal memory, and that this Apps2SD app basically lets you install to your memory card? So my question is, does this lag the phone somehow? I like to have many apps and especially games installed on my phone, would doing this affect the performance or something? I know this is the case for Windows Mobile, but not sure about Android.....
chaoscreater said:
i see.....in that case there's no way to install 2 different roms to allow dual booting then? What about the app "Boot Manager", will that work? I found it on this site here:
http://www.androidpolice.com/2011/0...ted-user-should-know-about-part-4-apps-26-33/
One last question, I came across this popular app that is recommended by many Android users, called Apps2SD. My understanding to this is that by default, any apps/games that you install on your device will install to the internal memory, and that this Apps2SD app basically lets you install to your memory card? So my question is, does this lag the phone somehow? I like to have many apps and especially games installed on my phone, would doing this affect the performance or something? I know this is the case for Windows Mobile, but not sure about Android.....
Click to expand...
Click to collapse
I follow AndroidPolice as well. I don't know about Boot Manager, I heard about it, but I haven't heard any reviews of it yet.
Two things when it comes to phone storage and apps on the Milestone: Old hardware makes for a lot of games to not work at all, and low phone storage space.
Almost every ROM comes with apps2ext support, which is a more advanced version of Apps2SD. You can follow this tutorial here: http://forum.xda-developers.com/showpost.php?p=10994672&postcount=226
Apps2ext will trick your phone into thinking space on the SD Card (the ext partition) is actually part of the phone's internal memory. You will be able to get a lot more apps on the phone this way.
Ahh cool, that saves me the trouble of me having to install an extra tweak.
Hmm I know Milestone is old, but not that old is it?? I don't know of any games now days that require heavy hardware specs or anything......i'm just hoping that emulators will work fine on it. I mean, my iPod Touch 3rd Gen only has about 120MB of free RAM, and the CPU is crap as hell and yet I could run GBA games like Pokemon or Golden Sun fine no problem (with sound of course). I'm hoping it'll at least work smoothly on the Milestone since I'll be attempting to overclock it to 1Ghz, which should run it significantly faster in theory.
BTW I found this great tweak for the CM7, here's the link:
http://chromloop.com/2011/07/how-to-make-cyanogenmod-7-for-milestone-a853-lighter-and-faster/
are there any ones similar to this? I'm a tweak junkie addict, I like to make my device run as smooth and as fast as possible. When I still had my HTC Touch Pro and Xperia X1, and even Nokia N900 (which uses Maemo 5), I tweaked the crap out of them and got more juice and power and made its performance so much better. I'm hoping I can at least do the same for the Milestone, except I couldn't seem to find many tweaks...
Oh lastly, I know one of the big problems with Android is fragmentation. There're already some apps out there in the Android market that are exclusive to certain Android versions. The same app has a version for Froyo (v2.2) and Gingerbread (v2.3). This is true for some of the mods or tweaks on XDA. So my question is, are custom roms like CM7 using Gingerbread? I'm guessing yes since it says 2.3.5? In that case, would I be able to simply install the latest mod/tweak or apps/games from XDA or the Android market? Or must I find the versions that is identical to mine?
E.g. if I install CM7, can I still install a mod that is for Froyo?
chaoscreater said:
Ahh cool, that saves me the trouble of me having to install an extra tweak.
Hmm I know Milestone is old, but not that old is it?? I don't know of any games now days that require heavy hardware specs or anything......i'm just hoping that emulators will work fine on it. I mean, my iPod Touch 3rd Gen only has about 120MB of free RAM, and the CPU is crap as hell and yet I could run GBA games like Pokemon or Golden Sun fine no problem (with sound of course). I'm hoping it'll at least work smoothly on the Milestone since I'll be attempting to overclock it to 1Ghz, which should run it significantly faster in theory.
BTW I found this great tweak for the CM7, here's the link:
http://chromloop.com/2011/07/how-to-make-cyanogenmod-7-for-milestone-a853-lighter-and-faster/
are there any ones similar to this? I'm a tweak junkie addict, I like to make my device run as smooth and as fast as possible. When I still had my HTC Touch Pro and Xperia X1, and even Nokia N900 (which uses Maemo 5), I tweaked the crap out of them and got more juice and power and made its performance so much better. I'm hoping I can at least do the same for the Milestone, except I couldn't seem to find many tweaks...
Oh lastly, I know one of the big problems with Android is fragmentation. There're already some apps out there in the Android market that are exclusive to certain Android versions. The same app has a version for Froyo (v2.2) and Gingerbread (v2.3). This is true for some of the mods or tweaks on XDA. So my question is, are custom roms like CM7 using Gingerbread? I'm guessing yes since it says 2.3.5? In that case, would I be able to simply install the latest mod/tweak or apps/games from XDA or the Android market? Or must I find the versions that is identical to mine?
E.g. if I install CM7, can I still install a mod that is for Froyo?
Click to expand...
Click to collapse
Of course you still can. The best tweak for Milestone is under Android Hacking, it's zeppelinrox's supercharger script, which you run through Script Manager. That's the best you can get.
Sent from my Milestone using XDA Premium App
I thought custom roms like CM7 or IceandFire come with the supercharger script included?
chaoscreater said:
I thought custom roms like CM7 or IceandFire come with the supercharger script included?
Click to expand...
Click to collapse
Some do, such as HO!NO!, but not all of them do.
Sent from my Milestone using XDA Premium App
Ok so I finally got my Milestone today!
I'm about to start rooting it and install CM7 on it. But before I do that, I have one important question. I know for Windows Mobile, almost all of the device requires you to do a hard reset after flashing a custom rom. I was wondering if the same needs to be applied to Android custom roms? Because it doesn't seem like it, I did a quick Google search and found this:
http://androidforums.com/optimus-v-...4-do-not-factory-reset-your-rooted-phone.html
So ya I'm not sure....
UPDATE:
Ok so I got my Milestone rooted, and installed CM7 on it. I came across a weird problem while doing it though. First of all, I'm using a 8GB Kingston microSD class 2, and it's brand new and hasn't been used before, so it obviously has nothing stored on it as it's empty to begin with. Ok, so as I followed the instructions, the first step is obviously rooting the Milestone, so I simply copied OpenRecovery to the memory card while my Milestone was connected to my PC. The weird thing is, when I opened "My Computer", I didn't see my memory card. Instead, I see "Milestone", so I opened it and then I see my memory card "Removeable Storage". I opened it again and here's the actual weird part, there're 2 files stored in it, called:
DevIcon
DevLogo
At first, I didn't think it was a problem because I thought they were just some dummy file or something. Also, the memory card is empty other than those 2 files. So after copying OpenRecovery to it and rooting it successfully, I then proceed to copy the CM7 custom rom file to the memory card. But this time, I still see the same thing. I don't see my OpenRecovery folder on it at all, there're no other files other than those 2 files on it. I tried Unmount and Mount in the SD Card settings, also unplugging my USB cable and re-plugging back in but it's the same. In fact, after 'Unmounting' the memory card, I couldn't even access it on "My Computer", as nothing shows up after I open "Milestone". Only 'Mounting' works, but again I only see those 2 files and nothing else.
HOWEVER, I then tried to take out the memory card and use my own microSD card reader, and bam I can see all the files on it, such as OpenRecovery and even the nanDroid backup that I made while following the instructions on that guide. So this is weird, why can't I access or see the contents on my memory card while the phone is connected to the PC??
I don't wanna create another topic for this since it's unnecessary, so here's my final question. In case something goes wrong in the future, what's the best way for me to revert back to stock?
I know I can use nandroid for this, but here's what i'm confused about. Nandroid makes a backup of the complete system, including the settings and apps installed correct? But what if you flash a custom rom, and then use a nandroid backup of the stock rom, will that still work? Or would you have to install the stock rom first for you to be able to use the nandroid backup?
Lastly, if the nandroid backup works regardless of whether you're using a different rom than the rom that the nandroid backup was made, then which option is better:
use nandroid to revert to stock, or using this guide here:
http://forum.xda-developers.com/showpost.php?p=11902513&postcount=7
Now I understand that for Milestone, custom roms are not actually flashed since the bootloader is locked. So would using nandroid be good enough?
chaoscreater said:
I don't wanna create another topic for this since it's unnecessary, so here's my final question. In case something goes wrong in the future, what's the best way for me to revert back to stock?
I know I can use nandroid for this, but here's what i'm confused about. Nandroid makes a backup of the complete system, including the settings and apps installed correct? But what if you flash a custom rom, and then use a nandroid backup of the stock rom, will that still work? Or would you have to install the stock rom first for you to be able to use the nandroid backup?
Lastly, if the nandroid backup works regardless of whether you're using a different rom than the rom that the nandroid backup was made, then which option is better:
use nandroid to revert to stock, or using this guide here:
http://forum.xda-developers.com/showpost.php?p=11902513&postcount=7
Now I understand that for Milestone, custom roms are not actually flashed since the bootloader is locked. So would using nandroid be good enough?
Click to expand...
Click to collapse
The best way to revert to stock will be to flash an sbf for your region that will wipe everything. They have those sbf's on and-developers.
Sent from my Milestone using XDA Premium App
Ahh I see, so in what situations will we be using nandroid to restore from the backup?
Also, the SBF file i'm using is from the guide that you linked me in your 2nd post. I'm using the EUROPE one because apparently it covers most of the countries around Europe, which includes New Zealand (where I live). I've had no problems with it, but just then I checked out the AND-Developers site like you suggested, and found this here:
http://and-developers.com/sbf:milestone221
It doesn't seem to have New Zealand but it does have Australia, which is like a neighbour to us. Will it be better if I flash the SBF to that instead?
Also, will flashing a SBF change the radio? Or does only changing the baseband change the radio? Because i'm getting weak signals from 2G/3G sometimes, and my Wifi has problems sometimes not being able to connect properly. Either that, or it shows that i'm connected but i'm not getting any data, apparently a lot of people have problems like this after I did some searching around.
chaoscreater said:
Ahh I see, so in what situations will we be using nandroid to restore from the backup?
Also, the SBF file i'm using is from the guide that you linked me in your 2nd post. I'm using the EUROPE one because apparently it covers most of the countries around Europe, which includes New Zealand (where I live). I've had no problems with it, but just then I checked out the AND-Developers site like you suggested, and found this here:
http://and-developers.com/sbf:milestone221
It doesn't seem to have New Zealand but it does have Australia, which is like a neighbour to us. Will it be better if I flash the SBF to that instead?
Also, will flashing a SBF change the radio? Or does only changing the baseband change the radio? Because i'm getting weak signals from 2G/3G sometimes, and my Wifi has problems sometimes not being able to connect properly. Either that, or it shows that i'm connected but i'm not getting any data, apparently a lot of people have problems like this after I did some searching around.
Click to expand...
Click to collapse
1. when you're phone will not start anymore, it's good to have one before every new flash cause you never now what's gonna happen.
2. funny thing is i know where New Zealand is (not near Europe) . about the baseband ... yes every sbf has the region specific baseband 's (you cant flash a radio only change baseband 's).
baseband can be found on dexter's (http://dext3r.komodin.org/) page but they are already included in OR (not sure about fufu's). i can't be very precise because i don't remember.
custom rom's don't think they change baseband 's, (the .zip ones)
Ya ur right, NZ is not anywhere near Europe lol
but I did do some research on which SBF I needed before I flashed it, and I found out that the Europe SBF works for NZ as well, it was mentioned somewhere I can't remember.
About the baseband, I'm still a little bit confused. First off, I already know that you can change the baseband under OpenRecovery. The thing is, there are no options to change the baseband to New Zealand, so which one should I pick? Also, here's the part I'm confused about. You said that the baseband are region specific, and yet we can choose the baseband we want in OpenRecovery.
So since I flashed the SBF for Europe, what will happen if I then change the baseband to say Argentina (one of the options under OpenRecovery)? Will it crash or something?? I don't even know what baseband i'm using right now, I haven't changed anything, I only flashed the SBF for Europe and that's it. I can still go online using 2G/3G and txt no problem, but I'm just not sure if the baseband i'm using is suppose to be correct for New Zealand or not...
BTW just another side question (sorry I'm really new to the Android scene!):
I've found a few custom roms that doesn't use the current kernel we have for Milestone. As far as I know, the bootloader for Milestone is locked, therefore we can't properly flash a custom rom onto it, as well as replacing the kernel as well. So what I'm confused with is, if some of these custom roms don't use the current kernel on the system, then how does it work? Does it use its own kernel, and if so then shouldn't that replace the system's own kernel before it can be used??
Here's one of the custom rom topic where I read from, in case ur wondering:
This is the Froyo FRG22 image for our Milestone. but as this is not using the kernel, there are some limit to functions based on kernel requirement. But its close, and works great and is alot faster.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=734802
The same goes for the custom roms. I don't understand how they can run on Milestone even though it's not properly flashed. Like some others have mentioned, the so-called "custom roms" that we have now are just a layer of image or skin on top of the stock rom. The weird thing is, it runs faster and most of the pre-installed stock apps that came with the stock rom are removed, thus giving us more space for internal storage. But how does this work if the custom roms haven't actually flashed onto our phone? Or did it overwrite/modify the files on the stock rom? If so, then isn't that just flashing onto the phone then?
chaoscreater said:
About the baseband
Click to expand...
Click to collapse
changing baseband's that are not supported by your network op will lead to no signal whatsoever.. i don't remember if there is a problem with only data. try other baseband, in theory it will not crash anything, so do a nandroid backup before
http://forum.xda-developers.com/showthread.php?t=734802
Click to expand...
Click to collapse
that is an old post from "25th July 2010, 05:52 AM" moto started to leak kernel from January 2011 give or take a month, so back then froyo was used with the eclair kernel. kernel from milestone was never changed to other than moto signed, only modules loaded at an early stage, thanks to kabaldan/nadlabak and other if exists
custom roms =
moto kernel
kernel modules (this helps on overclock , app2ext ... others)
mods to system files, apps
hope you understand cause i don't know if i make it clear at the end of the post
edit:
The same goes for the custom roms. I don't understand how they can run on Milestone even though it's not properly flashed. Like some others have mentioned, the so-called "custom roms" that we have now are just a layer of image or skin on top of the stock rom. The weird thing is, it runs faster and most of the pre-installed stock apps that came with the stock rom are removed, thus giving us more space for internal storage. But how does this work if the custom roms haven't actually flashed onto our phone? Or did it overwrite/modify the files on the stock rom? If so, then isn't that just flashing onto the phone then?
Click to expand...
Click to collapse
i doesn't make any sense, you will end up with no memory , only kernel remains, other things gets rewritten.
Code:
http://www.vodafone.co.nz/roaming/welcome-to-nz.jsp
this get out of what i know. with the frequencies,
basebands/frequency i have 900/1800
for data check if there is a problem with your apn settings
I see, thanks for your thorough explanation
Ya I know that changing my baseband will probably give me better signals, but I'm asking which one is best for Vodafone NZ because there isn't a baseband for New Zealand.
For the data part, were you talking about my wifi problem, and suggesting I check the APN settings? Don't worry that's been solved already. I flashed to the New Zealand v2.1 SBF and now it's working very stable. But like I said, after flashing to that I now have problems with connecting to my operator whenever I switch to 2G. However, 3G works fine so there's no problem with that.
BTW, I have another problem. After flashing to the New Zealand v2.1 SBF, I couldn't access my OpenRecovery anymore. I didn't delete or change any files on my memory card, so if I could access OpenRecovery and root my device as well as flash a custom rom when I was still on Froyo, then why can't I do it again when I flash to Eclair?
I *think* I know the reason, is it because it patched the vulnerable recovery or something? I think this is what I need to do to fix this:
http://android.doshaska.net/rootable
I haven't done it yet coz i'm busy these days, but i just need a confirmation so I know that it is indeed the case.
I *think* I know the reason, is it because it patched the vulnerable recovery or something? I think this is what I need to do to fix this:
http://android.doshaska.net/rootable
I haven't done it yet coz i'm busy these days, but i just need a confirmatio
Click to expand...
Click to collapse
true story . it should say something about eocd marker and fail.
http://forum.xda-developers.com/showthread.php?t=698059
For the data part, were you talking about my wifi problem, and suggesting I check the APN settings?
Click to expand...
Click to collapse
sorry... i don't know, last night i thought i read something else, about working 3g and 2g not ..must be the skittles... to much rainbow
i suggest finding out what country baseband are similar to New Zealand and flash/apply that one )

Anyone else paranoid about flashing ics?

With so many horror stories being posted, I don't know what to believe. When will it be relatively safe for us to update to ics?
I came from an HD2, and that was a treasure for flashing different roms. But it seems like the note is so easy to brick.
Edit: All I've done so far is root my note using Dr. Ketan's method.
It's mainly horror stories. Dozens, if not more already flashed to ICS without any problems. Of course there is occasionaly someone with bad luck, but that is also on the OTA updates. Every now and again something goes wrong, but it's a small chance and usually you are still able to fix it afterwards.
So just stick closely to the manual, don't cut corners and you'll probably be okay.
Otherwise, just wait for the OTAs. That's what I'm doing, but that is mainly because I'm a little lazy. However when I got the ICS kernel I'll put vanilla ICS over it.
I've flashed dozends of ROMs on my old HTC desire including ICS. At the end it worked always fine.
1. Backup
2. Wait after flashing - some roms need their time. After 10 min I've sometimes put out the battery to restart...
3. Enjoy
So don't fear!
I'm waiting for ICS OTA also. There have been lots of mixed reports with the previously leaked ICS ROMS - some bricked and some not. I've had a great run with flashing GB ROMs and Kernels but will wait for more official versions.
BTW - A colleague has a Note about four weeks old bought via the web. It turned out to be a German handset and he was successfully able to flash via KIES. I'm jealous - my Note 6 months old and I am still waiting for official ICS !
If you dont have any crazy combination of rom with custom kernel and cwm then is fine
Just dont wipe before flashing
And wipe after flashing
Sent from my iPad using Tapatalk
The fact that we have had ANY bricks at all suggests to me that this is not safe to flash, and even though I have been able to successfully flash LPY and run it, (not without problems), the bit that concerns me is the bricking due to large file copying which has been mentioned by various people.
Since I regularly copy large files to and from the device, I do not plan to subject my device to testing the theory.
I flashed ics yesterday and everything went fine, Iam always paranoid when comes to flashing but research before actual flash is vital! SEARCH button overheats and Iam ALWAYS following instructions!
Dont know what would I do without xda and those so capaple devs!
Galaxy Note!!!
I have flashed LPY a total of 3 times so far without any problems. I have wiped/deleted cache etc etc. The Bricks are all related to modified kernels and CWM. If you you use the stock LPY kernel then all will be fine.
I have also flashed CM9 several times and had no issues what so ever.
If you need root on LPY best method is to flash a GB rom and get root, then use mobile odin with the everoot option to flash LPY.
DO NOT flash the CF Root kernel, This is where problems may start. Keep it Stock and all should be fine.
nandihno said:
Just dont wipe before flashing
And wipe after flashing
Click to expand...
Click to collapse
Why is it safe to wipe after flashing and not before? I thought it was the other way around?
neos_83 said:
Why is it safe to wipe after flashing and not before? I thought it was the other way around?
Click to expand...
Click to collapse
It is the other way around.
Anyway, I fear this might be another superbrick in the making...
http://forum.xda-developers.com/showthread.php?t=1653290
And another one...
http://forum.xda-developers.com/showthread.php?t=1649982
vetchems said:
I have flashed LPY a total of 3 times so far without any problems. I have wiped/deleted cache etc etc. The Bricks are all related to modified kernels and CWM. If you you use the stock LPY kernel then all will be fine.
I have also flashed CM9 several times and had no issues what so ever.
If you need root on LPY best method is to flash a GB rom and get root, then use mobile odin with the everoot option to flash LPY.
DO NOT flash the CF Root kernel, This is where problems may start. Keep it Stock and all should be fine.
Click to expand...
Click to collapse
This is exactly what I did...
Mobile Odin Pro inject SuperSU and everroot......NO CF ROOT had a good GB ROM and Kernel. Only wipe done was done by Mobile Odin Pro
No I am 100% stock IPY with root...The fun will start when I begin flashing custom ROMS. Will need to flash CWR for that.
to answer the original question... no... because i thoroughly read as much as i can find before i flash anything...even google it to see if there are problems ... hence i have ics rumming and running without any strange issues...
tbong777 said:
This is exactly what I did...
Mobile Odin Pro inject SuperSU and everroot......NO CF ROOT had a good GB ROM and Kernel. Only wipe done was done by Mobile Odin Pro
No I am 100% stock IPY with root...The fun will start when I begin flashing custom ROMS. Will need to flash CWR for that.
Click to expand...
Click to collapse
I decided I did not want to "tip toe" around my normal processes with this device and went ahead and flashed CF Root with CWM. Going to need CWM to flash Roms and the LPY kernel has nt proven to be all that safe either. There is at least one case of a Superbrick wiping from Stock Recovery.
I bought these devices to mess with. I have a back up S2 and the s3 is out....Worst that can happen is I sell for parts.
well i am lucky so far as i dint have any issue with my note even after flashing lpy somany times from cwm may b me lucky till now
I'm terrified of flashing any roms on now after all the horror stories. I honestly don't even really care if I have ICS. I just hate how slow the stock ROM is. I would be very very happy with CM7 with SPen functionality.
This kind of sucks coming from an LG G2X which had so many stable roms and kernals to choose from
I thought a Samsung phone would have had even more but I guess not.
Probably like everyone else, I read Entropy's thread and became SUPER paranoid. He said there's no way to tell if you're slowly degrading the emmc or not unless you're on a 100% safe kernel / rom. I'm confused about the rest of the details. Apparently cm9 is 100% safe, but even the official ics can brick our note if we still have reminants of a leaked ics rom / kernel?
People alot more knowledgable than me have been bricking their note, so I will wait for an idiot proof method.
I would luv to see a step by step guide on video.
Also still dont grasp the fact that even if we put an official ics from Germany will won't get upgrades.
Sent from my GT-N7000 using XDA
I've been using lpy since release, and although I've had no problems so far, don't have cwm just root, but the more posts IM reading about people experiencing bricks from many different methods is definitively scaring me.
Chasmodo is a very reputable developer as is Entropy. I heed their words and will flash back to GB today, it's just not worth the risk.
Sent from my GT-N7000 using xda premium
Thijsvr said:
It's mainly horror stories. Dozens, if not more already flashed to ICS without any problems. Of course there is occasionaly someone with bad luck, but that is also on the OTA updates. Every now and again something goes wrong, but it's a small chance and usually you are still able to fix it afterwards.
So just stick closely to the manual, don't cut corners and you'll probably be okay.
Otherwise, just wait for the OTAs. That's what I'm doing, but that is mainly because I'm a little lazy. However when I got the ICS kernel I'll put vanilla ICS over it.
Click to expand...
Click to collapse
I also initially thought it was all speculation and anecdotal evidence. However, it appears that at least one user who has upgraded a brand new Note via Kies to LPY and wiped immediately thereafter has bricked his device.
That being said, I updated via PC Odin, rooted with temp CWM and full wiped from stock recovery thereafter without any issues (so far, been 3-4 days now). The performance improvements that ICS brings are significant, IMHO.
Basically, update if you really want to and refrain from wiping if possible (i.e. if you are not facing any FCs etc).

Flashing ROM's with mobile odin, what am I in for ?

I've read up several threads on this an I think what I want to do is a bit unique but I am not completely sure. I rooted my phone with Odin a week ago going from official gingerbread and used the stock Kernel. Root went off without a hitch but wasn't able to get into CWM recovery so I did some searching and just now flashed to the Corn Kernel 7.05. Works Perfect !
I want to now use mobile Odin to try out a few new roms as I can upgrade my phone now but want to give this a shot to breath some new life into my nearly 2 year old cappy. Flashing the kernel with mobile odin was s snap but I guess after reading the how and developers page I am lost on what types of ROM's I use with it. I'm new to all of this so judging stages of stability if not something I am sure about. I want some I wont have to compromise much with but will broaden my horizons some. I am so new cyanogen and maybe doc's ICS mod are the only ones I really know about but I don't know if those work with Odin or if I need to use CMW.
So final questions are these:
- Mod that will be stable and I can flash using only mobile odin or CMW (not using a PC) ?
- Does creating a backup of the ROM in CMW allow me to fix a bad ROM flash ?
- Is there an ICS build for cappy that will work for my situation ?
Thanks again ! ( I promise I used the search function and even the mobile odin thread but couldn't find what I was looking for)
1. Mod that will be stable and I can flash using only mobile odin or CMW (not using a PC) ?
2. Does creating a backup of the ROM in CMW allow me to fix a bad ROM flash ?
3. Is there an ICS build for cappy that will work for my situation ?
Click to expand...
Click to collapse
1. You can basically flash almost anything that isn't stock through CWM; you don't really need mobile odin too much. There are a lot of things considered "stable" that may not be stable for you. I considered alpha CM9 "stable," but others may disagree. It is up to you to find a ROM that suits you the best.
Keep in mind, you can only use Mobile Odin on Samsung-based BML ROMs.
2. To fix a "bad" ROM flash, you'd probably just flash the ROM again. But you can use the backup to restore your phone to its exact state at time of backup (with few exceptions).
3. What exactly is your situation? No matter what, I recommend CM9 nightlies but there certainly are other things out there to try that could work for you. Everything is CWM flashable, no Odin.
Just wondering, why can't you use a computer at all? You may need one in case you screw something up down the road.
korockinout13 said:
1. You can basically flash almost anything that isn't stock through CWM; you don't really need mobile odin too much. There are a lot of things considered "stable" that may not be stable for you. I considered alpha CM9 "stable," but others may disagree. It is up to you to find a ROM that suits you the best.
Keep in mind, you can only use Mobile Odin on Samsung-based BML ROMs.
2. To fix a "bad" ROM flash, you'd probably just flash the ROM again. But you can use the backup to restore your phone to its exact state at time of backup (with few exceptions).
3. What exactly is your situation? No matter what, I recommend CM9 nightlies but there certainly are other things out there to try that could work for you. Everything is CWM flashable, no Odin.
Just wondering, why can't you use a computer at all? You may need one in case you screw something up down the road.
Click to expand...
Click to collapse
1. Thank for clearing that up. I was using mobile odin at first because I wasn't able to boot into recovery with CWM but with the corn kernel that fixed everything and I've been getting myself more accustomed to working in there. Mobile odin seemed good for me to flash the new kernel easily and care free.
2. I was worried about a bad flash because I've read that using nandroid backups can be iffy (That's what CWM uses from what I have seen). Should I trust these backups ? I backed up everything in TiBu. I looked at the Wiki for cyanogen mod and it seems odd that the steps to flash the ROM's in CWM are very few so having few steps makes me think they have left something out or there is a step that is somehow understood I am missing)
3. I live in the boonies and my internet is even slower even though it's *cringe* 1.5 DSL haha. As far as my situation I mean something that would allow me to mess around with my phone some while knowing its stable because with 3 kids and having to have my phone I didn't want to be out of pocket for an extended period of time. I've been reading that ICS requires you to go back to stock to flash another ICS ROM but in my mind that doesn't seem too inconvenient.
I come from the desktop world and work well with hardware, not so much with software knowledge so trying to teach myself some new stuff since mobile seems to be here to stay. Making just a rudimentary app is a goal of mine even if no one cares so starting at the beginning trying to learn. Don't want to be one of those guys the noob video is made for who just begs for the way to root a phone and never contributes haha.
Thanks for your help !

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