Related
I was hesitant in posting this, however for whatever reason I am unable to find this information anywhere on these forums. It seems like the SpeedMod Kernel is draining my battery big time. Ex – I was at 75% when I went to bed, I just woke up (8hrs of sleep) and battery is at 16%.
These are the tweaks/features that I have turned on/off:
Tweak Options:
Enabled options
IOSCHED
KERNELVM
MISC
CIFS
BLN is disabled
Not sure if there is anything else I should be looking for, turning off/on. I was unable to find any tutorial for SpeedMod but from my understanding it’s supposed to slightly increase battery life.
Thanks in advance for the help!
1. Enable only the 'recommended' tweaks in CWM.
2. Uninstall and delete inactive apk folders to clean up the system.
3. Turn all GPS off
Lower brightness or use auto
Disable auto updating of apps
4. Once you CLEAN your phone up & start with a clean slate, you'll be able to diagnose what the problem is easier
5. The speedmod kernel which you are using is NOT the cause for the drastic battery drain you're experiencing.
Also, what ROM are you using?
MIUI
Thanks for the reply. I have already been doing most of that, screen brightness has always been set to low, GPS was always off, I also turned off Background Data so I think that would take care of auto updates?
Running the stock 2.2 ROM, I did however had to reflash this stock ROM last week due to instability and my aps crashing.
I followed your advise and disabled CIFS.
2. Uninstall and delete inactive apk folders to clean up the system.
Click to expand...
Click to collapse
Do you mean delete Aps that I'm not using? Or is APK something else?
If you flashed this kernel by itself after flashing a rom that did not included as part of the rom, you need to wipe cache partition and the dalvik cache from recovery then reboot your phone. The first boot may take a while but it's just rebuilding the cache. This some times clears up the problem you're describing.
Sent from my phone on vacation
alright, ive also heard alot of complaints from people I talk to on the phone - background static (white noise) + echo.. is it possible this is related to the kernel ?
That is a modem issue. Look for the modem thread stickied in development they will tell you to flash another modem but they got all the download links. The most popular one is the jk4.
Sent from my phone on vacation
Thanks! I just reset the cache and dalvik cache, seems to be draining at same rate.. i think.. anything else that could be draining my batt?
Im trying to flash the modem using odin but for whatever reason the pdf is not recognizing the file, is it because its .Zip? Then ill just change it to a .Rar.. Or is there another way i should be flashing the modem?
Sent from my SAMSUNG-SGH-I896 using XDA App
flash the modem in recovery
Sent from my phone on vacation
What rom are you using?
Sent from my phone on vacation
not using any rom! running 2.2
Thanks for the help 1tontomato! I think the issue with my modem has been fixed, I phoned my self and there was no echo. Now on a side note, do you think the battery could have been getting drained quickly because of my old modem? For example if it has to struggle to get/keep network coverage?
If your running stock froyo 2.2 uckb1 when you switched to the speed mod kernel becomes incompatible with the stock modem this is the reason for the poor call quality. It sounds like you are new to flashing roms you should try and read up on what the differences are between the stock i897 US i896 Candian and the i9000 european phones. All the firmware for these phones can be made to work on the captivate if you just understand what is compatible, and learn all the acronyms for the firmware. Happy reading(;~}
Sent from my phone on vacation
just an update - did a recalibrate on my battery last night, went to sleep with 100% batt life, woke up with 89% remaining. Awesome! Reminds me of my crackberry days
Glad you got this ironed out.
Rule of thumb: i9000 kernels with i9000 modems, same with cappy kernels & cappy modems.
When I said delete inactive apk, I mean any apps you don't use, or need, get rid of. You can download super manager, enable root function in settings, browse to system folder, and delete apks you don't use, like email.apk, mptapplication.apk, stuff like that.(just an example)
MIUI
Assuming this app can delete apps i wouldn't otherwise be able to, such as kobo? Would i need to purchase the full version to have access to this feature? I can't find it on the free version.
Sent from my SAMSUNG-SGH-I896 using XDA App
Hi. i tried almost all the custom roms. all were well. when i shift to cyanogen and miui and ics roms, i always get sleep of death issue or random reboot issue. Any fix for this ? is this because of Bootloader ? how should i get the info about my current boot loader. means whether i have froyo boot loader or ginger ?
majidshahab091 said:
Hi. i tried almost all the custom roms. all were well. when i shift to cyanogen and miui and ics roms, i always get sleep of death issue or random reboot issue. Any fix for this ? is this because of Bootloader ? how should i get the info about my current boot loader. means whether i have froyo boot loader or ginger ?
Click to expand...
Click to collapse
cant find this but you can flash gb bootloader it is backwardly compatible with froyo also
This is interesting... I've had sleep deaths on all of the ICS roms I've tried, coming from CM7 before that...
I have had no idea what bootloader I've been on, so I went ahead and loaded bootloaders from KF1. Couldn't even find KK4 anything... (most of the links in the forums are dead now)
I hope this fixes it up, otherwise I'm going to have to go back to GB ... (and I really don't want to...
Anyone come across a remedy for this?
I've had issues with the SOD, but, I've ONLY had it when I have been on GB bootloaders. My usual procedure for flashing ROM's is to FTS/MC to JF6(Eclair) then flash my ROM. So with ICS, I have never had it. I've run every THS, and ICSSGS ROM, WiUI, Doc's Master V5, and Fusion. Now with Fusion, it recommends GB loaders, so when I recently loaded it, along with the GB boots, I decided to stay with GB loaders when I switched to Doc's Master V5, I got a SOD 2 nights ago.
I also have to say that I did have SOD issues with EVERY GB Rom I ran, so i can say with a high level of confidence that it really has nothing to do with the ROM's themselves, and in my experience, has more to do with the bootloaders than anything else. I'm no bootloader expert by any means, but it's just my experience.
sleep death from poppies - yay
See OP of my ROM to avoid sleep death - it has settings.
Wow, The bootloaders have solved all my problems...
If anyone stumbles upon this in search of sleep death or charge death, (in my case both, would die after being charged over 90% and taken off the charger untill it got to around 80%)... GO HERE
Use the KF1 bootloaders with ANY rom...
It not only solved my charging / dieing issues but fixed my lag issues aswell. I can actually use my phone's browser again! (without wanting to throw it in the pool out of frustration)
What about people on CM9 based ROMS. The thread you liked to says CM users stay away in bold
ADDED:
MadGoat said:
A bit of an update,
After the bootloader update my phone acted fine for over 48 hrs..
HOWEVER, it is now back to its full charge, sleep death shinanigains.
The Bootloader's obviously did not solve the issue, however my phone (when its on) is quite a bit quicker and more responsive in all tasks.
I'm beginning to think that it might be a battery related issue, the phone (and battery) are now over 2 years old now.
The search continues...
Click to expand...
Click to collapse
Assuming your running a i897 bootloader now, (which means you DO see the AT&T when you boot and you DON'T see "galaxy s i9000" during boot)...
You can use this. I give no guarantee and I'm not responsible for anyone's outcome...
However, I can tell you I simply flashed this from the computer once I had done a cwm backup and pulled a copy to my desktop.
After it flashed,
I ran CWM,
flashed Icy glitch kernel (so I could reflash slim ICS),
rebooted to CWM again,
flashed my slimICS,
rebooted to cwm again,
cleared Caches and formatted all but the sdcard ... and restored my backup...
To help this process i would suggest creating a "Flash Folder" on your Internal SD. Categorize your rom / kernel / modem... what have you, will make life much easier.
Took a couple minutes to solve what I have been dealing with for a month...
All this being said, be sure you have the correct drivers for odin to see your phone. I needed to use Nexus S drivers, I assume because my rom (and subsequently the kernel) are nexus s AOSP...
I'm running dark knight 2 and have had no problems. I am also on GB bootloaders.
Sent from my SGH-I897 using XDA Premium App
Why 2? 3 is out and has so much customization now
i tried 3 and have had issues with signal that clear up as soon as i put 2 back on it. i have three stored on my phone to swap to at any point though. now that there are new nexus modems out i may try again but i am currently very happy with two. with the kf1 modem i have five bars all the time.
Sent from my SGH-I897 using XDA Premium App
UPDATE
A bit of an update,
After the bootloader update my phone acted fine for over 48 hrs..
HOWEVER, it is now back to its full charge, sleep death shinanigains.
The Bootloader's obviously did not solve the issue, however my phone (when its on) is quite a bit quicker and more responsive in all tasks.
I'm beginning to think that it might be a battery related issue, the phone (and battery) are now over 2 years old now.
The search continues...
yeah im been having a lot of issues with ICS ROMs on my captivate too. I just went back to GB today, cuz i cant take having so many deaths during the day....i wish there was a fix.
MadGoat said:
ADDED:
Assuming your running a i897 bootloader now, (which means you DO see the AT&T when you boot and you DON'T see "galaxy s i9000" during boot)...
Click to expand...
Click to collapse
Is this the definitive way to tell what bootloader you are running?
I think it's worthwhile to note that I have run a few ICS ROMs on my Captivate, usually charge it at night, and have never experienced SOD. Lots of people posting that they *do* experience it. I think the fact that some don't would be useful to whoever is debugging this issue.
I am currently running Docs Master ICS V5 Final w/ Glitch v14 B5 kernel.
I heard it has something to do with the CPU frequency setting. Once u raise the lower one, the DOS should be fixed.
My wife's cappy has does once in a while. She's only run cm7 with glitch. So I also will try raising min freq. From 200 to 400mhz. We will see what happens.
tommyguns818 said:
My wife's cappy has does once in a while. She's only run cm7 with glitch. So I also will try raising min freq. From 200 to 400mhz. We will see what happens.
Click to expand...
Click to collapse
How to do that? SetCPU or any other free one?
[email protected] said:
Is this the definitive way to tell what bootloader you are running?
I think it's worthwhile to note that I have run a few ICS ROMs on my Captivate, usually charge it at night, and have never experienced SOD. Lots of people posting that they *do* experience it. I think the fact that some don't would be useful to whoever is debugging this issue.
I am currently running Docs Master ICS V5 Final w/ Glitch v14 B5 kernel.
Click to expand...
Click to collapse
What was ur process of installing ur ROM. Maybe thats the trick. Mind sharing?
I usually do this:
1) Flash JF6 Eclair Odin
2) Master Clear
3) Flash GB UCKJ3 Bootloaders
4) Flash boog_KJ3_kernal3.tar using Odin3 v1.85
5) Flash CM9 (Goes into bootloop)
6) Re-Flash CM9
7) Reboot into Recovery and Flash selected ICS ROM.
After I posted about never getting an SOD on ICS ROM
argus1185 said:
What was ur process of installing ur ROM. Maybe thats the trick. Mind sharing?
Click to expand...
Click to collapse
Funny, I'm still new enough that I followed the directions on the OP for Doc's Master ROM:
"Installation:
-Firstly you must have rooted + CWM installed (you can flash over any rom)
-GB Bootloaders recommended...
-If lagfix enabled then disable it.
-Recommended removing external sd before flashing also.
-Copy rom to internal SD and Reboot into Recovery
-Wipe Data + Cache + Dalvik Cache
-Go "Mount and Storage" and format system
-Flash rom and reboot. At least 5 minute wait for first opening.
----if you get bootloop(probably you are coming a sasmsung based rom),remove battery, reboot into recovery using 3 button combo and reflash rom!
-When first opened let it at least 10 minute settle then reboot again...
-After second opening Enjoy your new rom..."
[email protected] said:
After I posted about never getting an SOD on ICS ROM
Funny, I'm still new enough that I followed the directions on the OP for Doc's Master ROM:
"Installation:
-Firstly you must have rooted + CWM installed (you can flash over any rom)
-GB Bootloaders recommended...
-If lagfix enabled then disable it.
-Recommended removing external sd before flashing also.
-Copy rom to internal SD and Reboot into Recovery
-Wipe Data + Cache + Dalvik Cache
-Go "Mount and Storage" and format system
-Flash rom and reboot. At least 5 minute wait for first opening.
----if you get bootloop(probably you are coming a sasmsung based rom),remove battery, reboot into recovery using 3 button combo and reflash rom!
-When first opened let it at least 10 minute settle then reboot again...
-After second opening Enjoy your new rom..."
Click to expand...
Click to collapse
Which GB Bootloader are you using?
Like many others, I'm having trouble with battery drain on DXLP9. I did the battery pull to no avail, the wakelock kept reappearing. Then I followed someone's suggestion to force stopping all of the cached process and, but unsure whether it's just placebo or not. Okay, questions:
Since the official update is non wipe, is it possible for "leftover" cached processes from GB still drains the battery in ICS? I.e. new bin, but old .conf and .tmp and got confused kinda thing. Again, is it possible?
If screen lock could cause problem, can it be eliminated by simply disabling it?
Pardon my stupid questions.
Yes there can be leftover trash from gb. Thats why it is recommended to do a factory reset before upgrading to ics. Wich will give you a clean system.
But what about the mmc erase bug? Factory reset via Settings can trigger it, am I right?
Yes it can trigger the emmc bug on ics kernels. Thats why I recommend doing the factory reset while still on GB.
yeah, wipe data/factory reset on GB BEFORE you flash the stock ICS rom and you should be good to go.
Hi,
I have recently updated my galaxy note's firmware to 4.1.2. Eversince the upgrade, the phone hangs several times a day and has slowed down drastically.
There is a huge lag even in simple things like typing on whatsapp, clicking a photo, watching a video, playing music files.
I have seen that there are a few others who have experienced similar problem in Note II.
Can someone please suggest me a way to fix this? I am having to restart the phone atleast 6 times everyday.
Thanks
bkgrc
How did you upgrade?
bkgrc said:
Hi,
I have recently updated my galaxy note's firmware to 4.1.2. Eversince the upgrade, the phone hangs several times a day and has slowed down drastically.
There is a huge lag even in simple things like typing on whatsapp, clicking a photo, watching a video, playing music files.
I have seen that there are a few others who have experienced similar problem in Note II.
Can someone please suggest me a way to fix this? I am having to restart the phone atleast 6 times everyday.
Thanks
bkgrc
Click to expand...
Click to collapse
Hi
i have been having the same problem have you found the solution if yes please share it,
i upgraded my galaxy note in February and i have my galaxy note is really slow many time and i have to restart it many times a day...And it gets really hot too.....
Note 1 hangs after upgrade
Hi baz77,
I did the upgrade via samsung kies, connect phone to my PC. few weeks ago.
Thx
system is too heavy on a stock JB rom.. root it and remove some unused apps like chaton , google plus etc etc..
Note 1 hangs after 4.1.2 upgrade
@ nokiamodeln91 - thnanks for your response. I am not completely aware of the process of rooting the phone.
Is rooting very complex? Could there be any warranty issues?
Thx
bkgrc said:
@ nokiamodeln91 - thnanks for your response. I am not completely aware of the process of rooting the phone.
Is rooting very complex? Could there be any warranty issues?
Thx
Click to expand...
Click to collapse
Rooting does void your warranty but the process is relatively simple. Follow 1a method in this guide.
the link rcheung28 has provided is the perfect way / safe way
bkgrc said:
@ nokiamodeln91 - thnanks for your response. I am not completely aware of the process of rooting the phone.
Is rooting very complex? Could there be any warranty issues?
Thx
Click to expand...
Click to collapse
If ever you have to return your phone to the service center, simply flash an official wipe ROM through PC Odin (that will remove the root and restore the phone to its "original" state). That's what I did when I had to replace mine (I flashed a Gingerbread ROM, made sure the phone booted fine and I was good to go).
nokiamodeln91 said:
system is too heavy on a stock JB rom.. root it and remove some unused apps like chaton , google plus etc etc..
Click to expand...
Click to collapse
What if I just disable the app instead of root delete? Any idea which app can be disabled without affecting phone normal operation? Thanks
i wonder if restoring factory settings will result to improvements..
and if it is safe now using the JB kernel?..
jaycm1130 said:
i wonder if restoring factory settings will result to improvements..
and if it is safe now using the JB kernel?..
Click to expand...
Click to collapse
Iam on JB DXLSE. Using Philz kernel DXLSE. Done factory reset but problem is still there. Batt drain quite fast with apps that hang once in a while. Slightly more laggy than ICS. Not the fault of kernel since Philz use stock kernel. Seems to be the problem of Rom. Media service seems to be running too often. But cant disable that app.
Anyone have any problem solving solution?:crying:
devll said:
Iam on JB DXLSE. Using Philz kernel DXLSE. Done factory reset but problem is still there. Batt drain quite fast with apps that hang once in a while. Slightly more laggy than ICS. Not the fault of kernel since Philz use stock kernel. Seems to be the problem of Rom. Media service seems to be running too often. But cant disable that app.
Anyone have any problem solving solution?:crying:
Click to expand...
Click to collapse
I haven't used a stock ROM for while, not because of battery drain (which is mostly app-related and can be checked with BBS), but because it was sluggish compared to CM.
As for the media scanner issue, you can try this app.
devll said:
Iam on JB DXLSE. Using Philz kernel DXLSE. Done factory reset but problem is still there. Batt drain quite fast with apps that hang once in a while. Slightly more laggy than ICS. Not the fault of kernel since Philz use stock kernel. Seems to be the problem of Rom. Media service seems to be running too often. But cant disable that app.
Anyone have any problem solving solution?:crying:
Click to expand...
Click to collapse
did you tried stock kernel?
what is your feedback to it?..
i was wondering if the stock kernel for DXLSE was safe to do factory reset..
jaycm1130 said:
did you tried stock kernel?
what is your feedback to it?..
i was wondering if the stock kernel for DXLSE was safe to do factory reset..
Click to expand...
Click to collapse
Was on stock when I did the factory reset before flashing Philz. Nothing happen to my phone but I cant confirm that nothing is wrong. Maybe its because I got away with it. But I can only let you know that I did the reset on stock JB DXLSE Rom and kernel.
Even after doing the reset. Can still notice the batt drain and sometimes some apps can hang. Theres some laggy interface. Isnt as smooth as when I was on ICS 4.04.
devll said:
Was on stock when I did the factory reset before flashing Philz. Nothing happen to my phone but I cant confirm that nothing is wrong. Maybe its because I got away with it. But I can only let you know that I did the reset on stock JB DXLSE Rom and kernel.
Even after doing the reset. Can still notice the batt drain and sometimes some apps can hang. Theres some laggy interface. Isnt as smooth as when I was on ICS 4.04.
Click to expand...
Click to collapse
maybe the custom kernel that you installed eats a lot of battery and/or the apps that you installed consumes resource even on the background..
try all stock kernel and rom.. let it settle for a week..
try also to replace the battery..
now if you insist in custom kernels, due to the fact that they are proven safe and has working CWM..
try tweaking with the settings.. through its governors,,
try debloating your rom by removing unnecessary bloatwares..
see if either any of this make sense to your device..
jaycm1130 said:
maybe the custom kernel that you installed eats a lot of battery and/or the apps that you installed consumes resource even on the background..
try all stock kernel and rom.. let it settle for a week..
try also to replace the battery..
now if you insist in custom kernels, due to the fact that they are proven safe and has working CWM..
try tweaking with the settings.. through its governors,,
try debloating your rom by removing unnecessary bloatwares..
see if either any of this make sense to your device..
Click to expand...
Click to collapse
Philz kernel is stock kernel with brink bug removed. So basically its a stock one.
For settings. I managed to set it as the same when Iam on ICS 4.04. For bloatware, all are disabled. Practically I set it as the same when Iam on ICS 4.04. Thats why Iam sure the batt drain and slight lag is there.
Hopefully someone here have a solution to it. :fingers-crossed:
devll said:
Philz kernel is stock kernel with brink bug removed. So basically its a stock one.
For settings. I managed to set it as the same when Iam on ICS 4.04. For bloatware, all are disabled. Practically I set it as the same when Iam on ICS 4.04. Thats why Iam sure the batt drain and slight lag is there.
Hopefully someone here have a solution to it. :fingers-crossed:
Click to expand...
Click to collapse
Philz kernel is stock based kernel not a stock one..
try this app: https://play.google.com/store/apps/details?id=com.asksven.betterbatterystats&hl=en
devll said:
Iam on JB DXLSE. Using Philz kernel DXLSE. Done factory reset but problem is still there. Batt drain quite fast with apps that hang once in a while. Slightly more laggy than ICS. Not the fault of kernel since Philz use stock kernel. Seems to be the problem of Rom. Media service seems to be running too often. But cant disable that app.
Anyone have any problem solving solution?:crying:
Click to expand...
Click to collapse
One thing that I've noticed that I haven't heard people talk about (maybe because it's stupid and non-applicable) is to go into your DCIM folders, both on your SD and in the phone and delete the entire .thumbnails directory. Mine somehow managed to accumulate a good GB or so of thumbs and that appeared to be bogging down media searching.
Even after that, phone has been really laggy lately. Going into running apps, I noticed a "Software Update" process running, even though I know this phone will not OTA update. Killed that process and things were ok again. YMMV.
Hi All,
Just curious how serious the eMMC bug is, and whether the N7000 is still worth getting??
1) Is the bug only present in ICS Roms, with unsafe kernels?
2) Is the phone safe using any of the GB or JB Roms, assuming it is only ICS thats at fault with the chip?
3) I've heard CWM is also dangerous to use, is there a certain one/version to use? (namely, Philz?)
4) How do you prepare the phone from ROM flash? All other Android devices I use to do Factory Reset Wipe in CWM, followed by wiping System and the Cache section. What can I do now, or cant I do... for fear of bricking?
5) Is this App [GalaxSim Unlock, by spocky] ok to unlock, does it work or can it be dangerous in light of eMMC? Or should I get a carrier unlock?
6) If using this phone normally, normal Apps... Is there a risk to bricking if the App write to write to the internal storage?? (such as saving files/settings) or is only if you attempt to wipe it?
7) Whats the absolute do's and DONT's with this device, like to stay away from....
I'm really keen to buy it, but dont want to end up with a BRICK through a silly mistake....
- sorry for all the questions, just really confused by whats ok and whats not...
Thanks, Lister
Emmc brick bug was there in ICS for sure but it is not worth trying on JB as it is no fun to see if the device gets bricked or not.
You can use GB (which has safe kernel) you can do the wipes. ICS and JB there are many custom kernel which are brick bug safe, meaning that it would not brick your phone if you have these kernel (say Philz for example) which also give you CWM and you can do wipes as many times you want without the risk of getting bricked. Philz kernel is available for all the versions.
For how to flash stock rom and list of stock roms use this:
http://forum.xda-developers.com/showthread.php?t=1424997
i dont have any idea about unlock, you may wait for someone to respond to that.
when using the phone normally there is no risk of brick.
Dont wipe the device on stock recovery and you are safe, to be safer always use Philz kernel. if you want to claim warranty at any time you can always flash stock rom again.
Own a note for 5 months now and this device is as good as any for the flashing of ROMs and kernels. So this is surely a safe buy. The PhilZ kernel is not particularly what i am fond of as it caused problems for the flashing of certain ROMs as the recovery is CWM based and not CWM recovery. And i do not have any info about the unlock app
Hi Treacherous_Hawk and Varad297,
Thank you both for your comments and suggestions, all this info I am picking up is very useful for me... As I may of said above, but have certainly said in other places across this board (and other sites). I'm fairly ok/confidant when it comes to Android, and the other Android hardware in my collection. (ZTE Blade, HP Touchpad, and MK802-II) Dont suffer from any kinda serious bug, and are brick free, they will never die... But I must admit, I am a little scared of this eMMC bug in N7000.
So thanks for putting my mind at rest....
If / When I do get this phone (through a mate of a mate), in October when her contract runs out. Will be locked to Vodafone UK, and I am T-Mobile UK, and I believe its currently running on Android 4.1.2 JB Stock.
However I want to flash the P.A.C. Rom to it straight away, as I have this on my ZTE Blade and HP Touchpad and love it...
So whats the best way to do it...??
1) Download Philz Recovery (and which version would I need, being that the rom its on is 4.1.2, and the rom I'll be taking it too is 4.2.2)
- I assume I copy this to SD Card, and flash in Stock Recovery, via going to Download Mode
2) What steps would I follow to clear of current rom? What wipes are safe, or are they all safe with Philz? Normally I do Factory Data wipe, and then System and Cache...
- Are these fine under Philz recovery? As from above two comments... First reply says its safe to do so, second reply says its dangerous... Just really scared about this bug, cant believe Sammy released a device like that...
3) I assume I flash it in Philz CWM, rather than ODIN? Do I need to re-flash a kernel straight after or is the one in P.A.C. (4.2.2) safe from bug?
4) I think the ROM is pre-rooted, but what should I do in case its not? Use ODIN or is there an easier method?
I assume flashing the above rom, via the above method (Philz CWM) will then result in the Yellow Triangle, and bump the count upto 1? So do I just use Triangle Away to clear and reset this, and this is again safe of bricking???
Thanks, Lister
Dude dont panic.
P.A.C. Rom is rooted and does not trigger the emmc bug.
Safe way from stock is as follows:
1.
!DO NOT WIPE ANYTHING ON STOCK!
2.
Get philz kernel for your stock version.
there are packages for flashing with either ODIN which involves connectiong a Computer or with Stock Recovery, which does not involve a computer.
The latter, which is simpler is simply a file on SD you can flash through stock recovery (when off press power+home+volup), it wont even void your warranty.
That provides you with a CWM like recovery from which you can wipe or flash other roms WITHOUT triggering the brickbug.
3.
Get your favourite Rom and flash it through cwm recovery.
BTW: Almost everyone who releases for N7000 puts something in the description that says if the rom is bricksafe.
All newer AOSP/CM based roms should be bricksafe.
Most of the customized Touchwiz Roms are also bricksafe, but watch their thread to be sure.
hjsdfbglsmhjc8we
EDIT:
IMO if you get the Note 1 for free or cheap its well worth getting. If you plan to buy one rather look for the Note 2 because I feel that it is better supported and has better customisation diversity.
Or if I ask myself what my next phone will be... dunno. Maybe a Nexus or Xperia Z or HTC? I cant seem to find the perfectly blended device. Might go with Jolla Sailfish device if it proves usable.
EDIT 2:
I think someone should sticky this as a simple guide for this. Also the existing stickies really need a cleanup to not confuse people with too much information out of differing times.
Does XDA pay moderators? I'd happily clean stickies and test stuff all day. (I'd also assume a neutral persona/state of mind for such activity.)
Hi Illidan Pornrage,
Thank you so much for going into great detail of the steps I need to follow, I'm starting to feel more comfortable at doing and using this now... So any ROM that says they are Brick free means there is no way to trigger it?? Not that I have ever done this, maybe when I first got my Android back in 2010 just to see what it was like... If I did Factory Data Reset in P.A.C. Rom it wont trigger the eMMC bug? (not that Im likely to ever use it... just making sure).
And with Philz CWM Recovery, I can use the Wipe Data/Factory Reset and then goto other screen and wipe the System partition, and the Cache and Davlik Cache with it all being ok... its 100% safe in Philz Recovery to not brick it??
I am so use to CWM on other devices, I am scared of using the wrong selection on the famous N7000 eMMC brick bug... lol
But with the other steps, thank you so much, such a HUGE HELP!!! and I am sure that will put other new (to N7000) users minds at rest...
-- So useful that ya know the above ROM too, as it makes it even easier/safer for me knowing all is gonna be ok with it...
Cant wait to get ROMing now... Just gotta wait till October... b*gger!! lol
Cheers, Lister
If I did Factory Data Reset in P.A.C. Rom it wont trigger the eMMC bug? Yes as often as you like. I flash cm nightlies, so I wipe very often.
And my window manager somehow always loses focus of the textbox. So I write half posts and have to edit 346243 times. Sorry.
And with Philz CWM Recovery, I can use the Wipe Data/Factory Reset and then goto other screen and wipe the System partition, and the Cache and Davlik Cache with it all being ok... its 100% safe in Philz Recovery to not brick it??
Also yes.
As for 100%. I cant assure you that nothing obscure that only happens 1 in a million times happens. But the menchanism that triggers the great evil bug is removed from philz and the mentioned roms.
Phewwww..... so this eMMC bug is no big deal then....
Only an issue if you stay on stock firmwares really, esp that of ICS??
Well thats made me feel a whole lot safer and more determined to want to get it. Had my hopes set on getting it, and then when I heard about the eMMC bug, thought is this gonna be a wise purchase or will I be spending the best part of £150 (dont know the final price yet) on a very large and heavy paper weight!! lol
Thanks so much for putting my mind at rest, great help...
Hi Illidan Pornrage,
I've only just seen/noticed your updates to my original questions, thanks for the updates.... Re: Why am I going for just the Note 1 rather than the Note 2. Is that someone a know (mate of a mate) will be upgrading her phone (she prolly gonna go back to Apple... boooo) and so hopefully she will be parting with her Note (and cheaply I hope, esp re the bug... a-haaaa)
- and couldnt agree more about tidying up the Stickies, as yes a lot of it is out of date, hence my asking and checking... To which you fully re-assured me of the steps, so think this would be useful to all...
Just to add to this, which Philz Kernel would I need??
Phone: Galaxy Note 1 / N7000
Network: Vodafone UK
Current OS: Android 4.1.2 JB Stock
Planned OS to update Too: P.A.C. 22:30 (Android 4.2.2)
So not sure what Kernel I would need from the below link, and if so, can you explain why I need THIS one? What do I need to look for in a kernel?
http://forum.xda-developers.com/showthread.php?t=1901191
Also, can anyone confirm if they have a UK Note 1 on contract (esp Vodafone) as I am hearing the contract ones are unlocked by default. Its only PAYG that are locked down....
thanks, Lister
Hi Illidan Pornrage / Guys,
As per my above post, any idea what Kernel I need based on the above details...??
Thanks, Lister