Related
Hi all, I hope you're not all tired of another noob posting up how-to questions. I come from a pretty solid background of writing modified firmware packages Motorola and Blackberry units, and writing custom themes for them both, so I am a bit familiar with the processes involved in rooting. Android is an entirely new beast though. I love it already, but I've also identified some things I'd love to be able to change. I've been reading everything I can in these forums for the past week, and I think I might be nearly ready to start diving into the root world. Yes, I've used the search a LOT Before I do root though, I wonder if you all might be able to add some insight into a few questions I haven't found the answers to thus far:
My rooting goals: remove the AT&T bloatware, possibly do a lag fix, and above all, do it the safest way possible. Baby steps first for me.
1) Rooting methods: Should I do the manual way, I found in that pdf guide on this site, the "GalaxyS_One-Click_Root_All_Models.zip" method, the mystery "update.zip" folder method, or the "one click root lag fix" method? Which is the safest and most tried and true for Stock 2.1 f/w, Baseband I897UCJH7? Also, what would be the best method to use if I wanted later to unroot?
2) Lag fixes: I've read that lag fixes can cause major problems when trying to undo them later on. Is there a lag fix that works well that is safer than others to load that can be removed easily? Are lag fixes even worth it?
3) Odin3: Am I correct in assuming that since I have JH7 that the most recent version of Odin is not capable of fully restoring my phone back to stock? I've been seeing posts from many people say that even using Odin, their phones get stuck during the revert process and cannot get back to stock. This is probably my biggest concern of all, in case I brick my phone. I've done that a LOT of times with Motorolas, and it's not a bit of fun trying to restore them.
Thanks very much in advance. Best wishes to all
The first piece of advice I have is make sure you have a cappi that you can get into recovery and download modes via the button combinations - if you can do this then you will be able to recover to a working configuration from just about any situation.
second, make sure you want to do this, because as you can get back to a "stock configuration" once you begin applying lag fixes or custom roms you will not likely be ever able to get back to your own stock configuration.
As for which rooting method - I have used and update zip and ryanza OCLF to root. Both of these methods are easy to unroot - at least until you begin applying lag fixes and/or custom roms.
If you are sure you want to move forward and root the very first thing you should do after rooting before you do any lag fixes or remove any bloat is get clockwork rom manager. Learn how to use rom manager and make a full nandroid backup of your phone before you do anything. If you have a good nandroid backup saved in a safe location then you can use this to get back as close as possible as you can to your own stock configuration later on.
Oden3 will get you back to a stock jf6 configuration. This will not be your stock configuration, but it is a working stock configuration.
Lag fixes do improve the lag in the file system some. However, before you play with any of them educate yourself as much as you can about the particular one you are going to try and use. I have applied both OCLF and voodoo and have been able to remove both of them. But if you don't follow the steps correctly you can have problems - after all with the lag fixes you are reformatting part or all of your data partition where the os is residing which is inherently risky. You can easily lose data and even soft brick your phone forcing you to use Oden3 to get back to a working state.
Lastly, I am running Cognition 2.2 beta 5 very successfully - and I do recommend it for anyone that has entered the rabbit hole of modifying this phone. And with my current config my phone is running so well that the lag fix is not needed for me anyway. My phone is running smooth and fast.
P.S. Just make sure you are not going to have any major regrets if things go wrong before you do anything at all, because any and all of these steps have some amount of risk associated with them. Make sure you are prepared for dealing with voiding your warranty and even though it is hard to brick this phone, it could still happen so be ready for that too should it happen.
i would agree, go with cognition 2.2. i only had my captivate for a day, and found it very easy to get it installed without any hassle.
Thanks for the info all. I've read about Cognition a fair bit and was wondering if I ought to go for it. What are the differences between it and the standrd Froyo leak?
A more pressing question: If I went to Cognition 2.2, would I be able to easily get the official release OTA and install it normally when/if it becomes available? Are there step-by-step guides out there for getting that release onto and off of the phone? I'd hate to get Cognition on there and find out that i couldn't easily get it back to a state where I could get the full deal on there. I've read some horror stories about just that lately...
charging rhinos said:
Thanks for the info all. I've read about Cognition a fair bit and was wondering if I ought to go for it. What are the differences between it and the standrd Froyo leak?
A more pressing question: If I went to Cognition 2.2, would I be able to easily get the official release OTA and install it normally when/if it becomes available? Are there step-by-step guides out there for getting that release onto and off of the phone? I'd hate to get Cognition on there and find out that i couldn't easily get it back to a state where I could get the full deal on there. I've read some horror stories about just that lately...
Click to expand...
Click to collapse
If you are wanting to get OTA updates then I wouldn't even root your phone - while it is possible to still get OTA's after rooting, once you begin modding (lag fix, or custom rom) you oare increasing making your phone less and les compatible with any OTA available.
NOTE: I personally will not ever apply an OTA myself - but rather will wait for someone else to create a custom mod of any OTA feature I like - them donate that dev a few dollars and use their mod.
Im getting my cap this Friday, I was going to post the same thing OP. Looks like cog 2.2 is the way to go when i get it.
I have heard a lot of talk about an emmc bug affecting stock Ice Cream Sandwich builds realeased by Samsung. THe general consensus seems to be that it is not safe to wipe/factory reset the stock Samsung ICS roms.
The question I have is do we know if the recent UK region ICS update (XXXLQ2) is affected by the emmc bug?
Can anyone confirm that if they factory reset after upgrading to LQ2 ICS that they bricked their phone or that it was a successfull wipe?
I can confirm that i have factory reset my phone successfullu after installing LQ2 update although my phone has problems caused by this update - random reboots, crashes to the homescreen, screen going black and buttons not responding etc. Could these problems be caused by the emmc bug?
I look forward to your replies, i know there are geniuses on this forum who can enlighten us.
We wont know if its affected until someone reports a brick.
But I would guess its still affected by the emmc bug.
As Entropy says in his PSA:
"All ICS official releases for the Samsung Galaxy Note (GT-N7000) as of late May 2012 - This includes XXLPY, ZSLPF, and DXLP9, and future kernels should be assumed affected until further notice."
So the bug is in offical releases?
SO this bug is in the official releases that you can install via kies?
Will Samsung patch this bug?
Surely they must be aware of it since the number of bricks going to the service centers must be rising astronomically. If we are aware of it how can they not be when they have tested many devices at factory?
Better hold on to gb then rushing to ics with emmc bug. Wait for awhile until some one found a solution. Or else you will stuck like me with no gb backup to revert back.
Sent from my GT-N7000 using XDA
This is a XXLQ2 Brick I Guess.
Lol thats a total facepalm. But whats the cause of his brick? I couldnt read it all cause I laughed so hard that I got tears in my eyes.
JazonX said:
This is a XXLQ2 Brick I Guess.
Click to expand...
Click to collapse
No, that brick was not caused by the LQ2 kernel; it happened because the guy had used an ancient updater script for his Rom.
http://forum.xda-developers.com/showpost.php?p=26951708&postcount=3
chasmodo said:
No, that brick was not caused by the LQ2 kernel; it happened because the guy had used an ancient updater script for his Rom.
http://forum.xda-developers.com/showpost.php?p=26951708&postcount=3
Click to expand...
Click to collapse
Yeah thats exactly what I thought. As I said, couldnt read it all.
Contrary to beliefs I have had no issues on my Indian ROM ICS.
I believe it may have something more to do with custom kernels, etc rather than Stock firmware?
I too have the LQ2 update and would also like to know if this is also affected by the brickbug i have not done a factory reset and currently have no issues with my phone. I do not intend on doing a factory reset until i know that Samsung have fixed the issue.
Well, you might aswell count on beeing affected. But if you dont need to factory reset then everytging is fine.
Belfia said:
Well, you might aswell count on beeing affected. But if you dont need to factory reset then everytging is fine.
Click to expand...
Click to collapse
Cheers just hope i don't need to factory reset before a fix is sorted. Don't really want to go about changing roms as i like tw and like to keep my phones standard.
volvo940seturbo said:
I too have the LQ2 update and would also like to know if this is also affected by the brickbug i have not done a factory reset and currently have no issues with my phone. I do not intend on doing a factory reset until i know that Samsung have fixed the issue.
Click to expand...
Click to collapse
Run the "GotBrickBug" app by Chainfire under the Themes/Apps section and see what firmware you have.
More than likely the LQ2 ROM still has the faulty MMC_CAP_ERASE code because Samsung hasn't admitted to the problem at all yet.
dbreloaded said:
......my phone has problems caused by this update - random reboots, crashes to the homescreen, screen going black and buttons not responding etc. Could these problems be caused by the emmc bug?
Click to expand...
Click to collapse
I initially update by Kies to LQ2 and had random homescreen force close, black screen,green dots on the screen, apps freezing...etc. Done a factory reset, then downgraded to GB UK, factory reset again, downloaded the LQ2 Firmware via Check FUS PC version and flashed ICS LQ2 using ODIN PC and everything is running smooth. No bugs to report after more than 1 week.
rdosti said:
Contrary to beliefs I have had no issues on my Indian ROM ICS.
I believe it may have something more to do with custom kernels, etc rather than Stock firmware?
Click to expand...
Click to collapse
I'm afraid this is not correct! Its a bug in stock ICS kernels (or other ICS based kernels that are not specifically modified) that enable the eMMC erase command.
Some custom ICS based kernels now have this command disabled. But as for now, it is considered unsafe to flash or specifically full (data) wipe from any stock ICS ROM (some ICS ROMs do a full wipe when flashed!). It is still statistically a rare event, but the only way to be 100% sure safe is to flash from a GB based kernel, such as Abyss 4.2 kernel.
Samsung is working on a "fix" for the faulty firmware in the emmc chips but what this fix will be is unknown.
It has been reported that, unrooted, on a Stock ICS ROMS (and hence stock kernel) has super-bricked after doing a factory reset.
You may be able to do a full wipe/reset/custom ICS kernel ROM and not suffer any immediate ill effects but the bug can manifest itself at a later date.
If you really want to get the bug, the best way would be to fill up your internal memory, then do a factory wipe, rinse and repeat!
GB kernels don't use the erase command, so are totally safe.
So to summarise, it is not safe to factory reset on LQ2 UK rom! Samsung have not yet issued a fix!
EDIT: Wow, its even more complicated than above lol!
See here for updates and the first sign of a fix!
http://forum.xda-developers.com/showthread.php?t=1698977&page=14
I am currently waiting for JB to be released in the UK, but getting increasingly frustrated to may go down the route of installing the leaked version.
When I moved to ICS I remember that the initial installation was poor with reliability issues and alarming battery consumption. The solution was to do a factory reset, which then required for all of the apps to be reinstalled.
I would rather avoid reinstalling all of my apps (only about 60) but would this be required for a stable install using the leaked official rom?
Also - I dont think my Note is currently rooted so as far as I am aware I think that I would lose by Text Messages also - is this the case? Or is there a way that I can back these up?
Thanks for your help.
yeah ultra clean is needed for leak and official, best to follow the route of safe way as well, just wait for official your country, or get get yur hands dirty woiding yer warrantee at own risk
ridgmont61 said:
I am currently waiting for JB to be released in the UK, but getting increasingly frustrated to may go down the route of installing the leaked version.
When I moved to ICS I remember that the initial installation was poor with reliability issues and alarming battery consumption. The solution was to do a factory reset, which then required for all of the apps to be reinstalled.
I would rather avoid reinstalling all of my apps (only about 60) but would this be required for a stable install using the leaked official rom?
Also - I dont think my Note is currently rooted so as far as I am aware I think that I would lose by Text Messages also - is this the case? Or is there a way that I can back these up?
Thanks for your help.
Click to expand...
Click to collapse
LSZ install using PC Odin does not wipe your apps and data. If you want to root it afterwards boot to recovery and install Philz kernel.
Do eeeeeeet..there are lots of custom roms ( maybe even better than official versions ) in the android development section for the note. I kid you not you will be addicted to it.but read instructions carefully so that you won't brick us phablet.
U could back up your apps using titanium backup but most devs don't recommend restoring with titanium.but it works for me everytime.you could try it too.even contacts can be backed up
Sent from my GT-N7000 using XDA Premium App
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
Hey guys, the thing is I tracked down a Note 1 running 4.0.4 unroot, but is running terribly at this point. I think it is due to so many apps install and present on the homescreen. It is available for 'bout $200 (all my budget, in South East Asian it's pretty big, so bear with me). If I get it, I'd definitely flash it to 4.1 or newer, as I can't bear the lag on 4.0 now.
So, any advice on whether I should get it? Is the thing flashable? I mean, I have an Galaxy tab 10.1 so I'm kinda familiar to flashing, but as the newcomer, I'd like to ask is there any difficulty flashing this thing, anything I should be aware of before bricking it?
Thanks in advance guys! All advice is greatly appreciated!
Yes, it very easy to flash Note
Jacko2410 said:
Hey guys, the thing is I tracked down a Note 1 running 4.0.4 unroot, but is running terribly at this point. I think it is due to so many apps install and present on the homescreen. It is available for 'bout $200 (all my budget, in South East Asian it's pretty big, so bear with me). If I get it, I'd definitely flash it to 4.1 or newer, as I can't bear the lag on 4.0 now.
So, any advice on whether I should get it? Is the thing flashable? I mean, I have an Galaxy tab 10.1 so I'm kinda familiar to flashing, but as the newcomer, I'd like to ask is there any difficulty flashing this thing, anything I should be aware of before bricking it?
Thanks in advance guys! All advice is greatly appreciated!
Click to expand...
Click to collapse
It's very very easy to flash Note..... Just buy it....:good: :highfive:
thanks! Well, done a little reading today. And I got something about the "super brick bug" which seems rather dangerous. Anyone cares to elaborate on this for me please?
Jacko2410 said:
thanks! Well, done a little reading today. And I got something about the "super brick bug" which seems rather dangerous. Anyone cares to elaborate on this for me please?
Click to expand...
Click to collapse
If you follow the ''HOW TOO's'' then you should not get any brick or issues. I flashed so many Rom- and Kernel's and i never got a brick.
Alwas be on a Safe Kernel. More information is on the General N7000 Forum: http://forum.xda-developers.com/forumdisplay.php?f=1347
The previous owner is a 10th grader I tutored, I doubt he knows anything 'bout root or flashing so I think that's not the trouble here. One thing on my mind is that in my country there's still no JB 4.1 OTA yet, at least not until some weeks ago. So, after some basic reading, I got something planned out:
_ Never factory reset while on stock ICS => I should push stock JB through Odin =>safe kernel => push CWM through Odin =>root =>flash some CM goodness
Hell, if stock JB is smooth, I might even stop at rooting.
Basically, that's the right order of this, right?
Somebody better stop me before I mess up something. Haha :laugh:
Oh, I'm late to the party so what rom can you guys recommend, help me save some time shopping here.
Jacko2410 said:
The previous owner is a 10th grader I tutored, I doubt he knows anything 'bout root or flashing so I think that's not the trouble here. One thing on my mind is that in my country there's still no JB 4.1 OTA yet, at least not until some weeks ago. So, after some basic reading, I got something planned out:
_ Never factory reset while on stock ICS => I should push stock JB through Odin =>safe kernel => push CWM through Odin =>root =>flash some CM goodness
Hell, if stock JB is smooth, I might even stop at rooting.
Basically, that's the right order of this, right?
Somebody better stop me before I mess up something. Haha :laugh:
Oh, I'm late to the party so what rom can you guys recommend, help me save some time shopping here.
Click to expand...
Click to collapse
I'd say don't take your chances by going the short way. To be sure you could flash a safe kernel through Odin and then use it's CWM to wipe and flash your stuff. That's what I've done when I got my note and never even got close to the brick bug.
If you really don't understand bullocks of android, just follow carefully the instructions on Dr. Ketans guide thread and you should be fine
Feel free to PM me if you need help
Sent from my GT-N7000 using Tapatalk 4
By "bricking", you meant soft brick or boot loop, didn't you? Couldn't imagine a device bricked twice in its life.
Well, let's just presume I'm on stock ICS unroot with unsafe kernel. First I can flash Philz's kernel and CWM (all in one zip file) in stock recovery. That means with that I'm rooted + safe kernel +CWM, then free to factory reset, wipe or flash anything, right?
Couldn't find back which thread says "Never factory reset on stock ICS", I swear I saw it somewhere in these N7000 box.
Oh, and I'm from Vietnam, but I don't understand what my location has anything to do with this, as most Android devices in Vietnam use US firmware.
Jacko2410 said:
By "bricking", you meant soft brick or boot loop, didn't you? Couldn't imagine a device bricked twice in its life.
Well, let's just presume I'm on stock ICS unroot with unsafe kernel. First I can flash Philz's kernel and CWM (all in one zip file) in stock recovery. That means with that I'm rooted + safe kernel +CWM, then free to factory reset, wipe or flash anything, right?
Couldn't find back which thread says "Never factory reset on stock ICS", I swear I saw it somewhere in these N7000 box.
Oh, and I'm from Vietnam, but I don't understand what my location has anything to do with this, as most Android devices in Vietnam use US firmware.
Click to expand...
Click to collapse
Yup. That's a safe procedure. It's important you don't wipe anything while you are at your stock kernel. Only after you flashed the safe kernel AND REBOOTED TO THE NEW RECOVERY
Sent from my GT-N7000 using Tapatalk 4
there is no us version rom for international n7000 cause its not the snapdragon att version
Sent from my GT-N7000 using Tapatalk 2