I just traded my i717 note for the n7000. After reading random forums on here, i'm a bit flustered but hanging in there.
Just a question, I currently have this set up on my phone:
Android Version: 2.3.6
Baseband Version: N7000XXLP1
Kernel Version: 2.6.35.14-FM-2.0-g399c932 [email protected])
Build: Gingerbread.XXLA6
My questions are:
1) Is XXLP1 an ICS modem?
2) I want to revert this phone back to a good stock image. I was thinking a German image. What do you think? (so I can update to ICS stock/root)
Your help would be appreciated.
Basically I just wanted to know if it's safe for me to flash stock rom/kernel without worrying about bricking my device and can I flash traingleway by chainfire to remove yellow triangle and reset counter without bricking my device. Please. Help
Stock is completely fine. Just the recoveries are giving people problems. Also LP modems are ICS
whatsaqazza said:
Stock is completely fine. Just the recoveries are giving people problems. Also LP modems are ICS
Click to expand...
Click to collapse
Stock is completely safe my hairy arse. Even large file deletion can cause a hard-brick.
Stick to:
CM9
Asylum
ParanoidAndroid or
MIUI.
These Roms contain a safe kernel. Everything else carries the risk of a hard-brick.
Be warned.
Alright, so if I flash stock rom and kernel, will it flash the baseband back to stock? Also which stock would you recommend?
ps. There is currently CWM on my phone, should I flash a factory recovery or just leave it as is?
chasmodo said:
Stock is completely safe my hairy arse. Even large file deletion can cause a hard-brick.
Stick to:
CM9
Asylum
ParanoidAndroid or
MIUI.
These Roms contain a safe kernel. Everything else carries the risk of a hard-brick.
Be warned.
Click to expand...
Click to collapse
So that means I traded for a messed up phone? CRAP!!!
But all that is ICS is the baseband (modem), the kernel and rom are stock gb, right?
adv1sory said:
So that means I traded for a messed up phone? CRAP!!!
Click to expand...
Click to collapse
Yep, Sammy did a crap job of official updates. All of them can mess up your EMMC.
However, you have an option to flash any of the CM9-based Roms, and you will be fine (those mentioned in the previous post).
........................
I chose Asylum, but one of the requirements is that recovery has to be:
on a proper working recovery, (DAFUQ, CM9 or a GB recovery ONLY)
The phone currently has CWM 5.0.2.7.
chasmodo said:
Stock is completely safe my hairy arse. Even large file deletion can cause a hard-brick.
Stick to:
CM9
Asylum
ParanoidAndroid or
MIUI.
These Roms contain a safe kernel. Everything else carries the risk of a hard-brick.
Be warned.
Click to expand...
Click to collapse
I thought complete stock, without recovery or anything flashed through odin was. Sorry if I'm wrong
adv1sory said:
I chose Asylum, but one of the requirements is that recovery has to be:
on a proper working recovery, (DAFUQ, CM9 or a GB recovery ONLY)
The phone currently has CWM 5.0.2.7.
Click to expand...
Click to collapse
You can flash it directly if you are on any Gingerbread rooted Rom.
whatsaqazza said:
I thought complete stock, without recovery or anything flashed through odin was. Sorry if I'm wrong
Click to expand...
Click to collapse
Steer clear of any official ICS Roms for now.
whatsaqazza said:
I thought complete stock, without recovery or anything flashed through odin was. Sorry if I'm wrong
Click to expand...
Click to collapse
I'm confused.
If I currently have a gb rom and kernel, shouldnt it be okay to flash stock gb? Or because I have an ICS baseband it makes it a problem?
If I were to follow the instructions posted here,
http://forum.xda-developers.com/showpost.php?p=23052721&postcount=10
Couldn't I be worry free about bricking?
adv1sory said:
I'm confused.
If I currently have a gb rom and kernel, shouldnt it be okay to flash stock gb? Or because I have an ICS baseband it makes it a problem?
Click to expand...
Click to collapse
Flashing on GB is completely ok, don't worry about modems. Sorry for the confusion. Just steer clear of any of the ICS roms that weren't mentioned as safe... All GB ROMs are safe as far as I know
whatsaqazza said:
Flashing on GB is completely ok, don't worry about modems. Sorry for the confusion. Just steer clear of any of the ICS roms that weren't mentioned as safe... All GB ROMs are safe as far as I know
Click to expand...
Click to collapse
PERFECT! So I didn't buy that much of a crappy phone. All I have to do is flash a stock GB rom and kernel. Then I'm able to install any gb custom rom, but should steer clear of any ICS roms that are deemed unsafe. Cool!
Taking the plunge!
I feel my heart racing ....
UPDATE: ALL FINE!!!! I don't have to worry about hardbricking my device. Currently running Open Europe stock rooted rom.
Can't be happier. Thank you all for your help! I greatly appreciate the quick responses I received on this thread!!
Related
Samsung fixed my captivate after the mini USB port broke and I intentionally bricked it with an Odin flash pull because they would have known it was modded/custom rommed. So they fixed it and sent it back and everything works(Thanks Samsung!) but the problem is that they flashed the new 2.3 update which is sooo slow/laggy and featureless compared to Cyanogenmod7 181 nightly that I used to have on my phone. What I want to ask is if I can Odin-one-click back to JF6 stock 2.1 from 2.3(ATT GB bootloaders I think?) and then go about rooting and such from there to get Cyanogenmod back onto my phone.
Thanks,
kind3rgarten.
Yes you can....but that's more work than it's worth.
Just flash a custom kernel with Odin...boot into recovery with button combos and flash whatever ROM you want. easy as pie
studacris said:
Yes you can....but that's more work than it's worth.
Just flash a custom kernel with Odin...boot into recovery with button combos and flash whatever ROM you want. easy as pie
Click to expand...
Click to collapse
Thank you for the answer, but I am more familiar with flashing the rom this way. Are you sure I could do it this way? There wouldn't be a problem with the bootloaders or anything?
this way == odin1click back to JF6 then root then CWM then flash CM7 and gapps
also, would there be any difference in performance/battery life or anything if I were to go your route?
If you used it before it's still ok, just like i said that's a much longer process than what's needed, and by flashing bootloaders when you don't need you're taking an unnecessary brick risk to downgrade to obsolete bootloaders. Gingerbread boots are backward compatible, so they will work with ANYTHING. so why go back and then if you wanna use a tw gingerbread ROM you'd have to update to the new ones anyway.
your process:
Flash to 2.1
Root
Get cwm
Flash ROM
And that includes bootloaders so if it disconnects you could brick.
best way
Flash kernel to get cwm
Flash ROM
2 steps and no bootloaders so at the very very worst case scenario, you get stuck in a bootloop which is much easier to fix than a hard brick.
That being said you're way will work, so whatever floats your boat...
studacris said:
If you used it before it's still ok, just like i said that's a much longer process than what's needed, and by flashing bootloaders when you don't need you're taking as brick risk.
Click to expand...
Click to collapse
Plus, if you ever decide to try a Gingerbread ROM, you'll have to reflash the bootloaders again anyway, again risking a brick.
If you really want to go back to 2.1, I would still use a bootloader free package.
^^^Lmfao... I always hit the submit post button before i finish my thought, i just added in that bit you mentioned while you were posting that lol
studacris said:
If you used it before it's still ok, just like i said that's a much longer process than what's needed, and by flashing bootloaders when you don't need you're taking an unnecessary brick risk to downgrade to obsolete bootloaders. Gingerbread boots are backward compatible, so they will work with ANYTHING. so why go back and then if you wanna use a tw gingerbread ROM you'd have to update to the new ones anyway.
your process:
Flash to 2.1
Root
Get cwm
Flash ROM
And that includes bootloaders so if it disconnects you could brick.
best way
Flash kernel to get cwm
Flash ROM
2 steps and no bootloaders so at the very very worst case scenario, you get stuck in a bootloop which is much easier to fix than a hard brick.
That being said you're way will work, so whatever floats your boat...
Click to expand...
Click to collapse
So would I just flash a kernel that already has root/CWM? Then flash CM7/gapps on top of that?
I would post a link, but I don't post here too often.
Like this?
androidforums[DOT]com/captivate-all-things-root/483646-guide-root-official-2-3-5-guide.html
apbthe3 said:
Plus, if you ever decide to try a Gingerbread ROM, you'll have to reflash the bootloaders again anyway, again risking a brick.
If you really want to go back to 2.1, I would still use a bootloader free package.
Click to expand...
Click to collapse
Yeah, I see what you mean, thanks. Can bootloaders effect battery life, because I remember that I didn't get the best battery life in CM7?
Cm7 is aosp based it doesn't have all the closed source hardware drivers of touch wiz, so the battery life will be worse.
As for the kernel, any will work. It's not a kernel you're going to be running it's just a transitory kernel used only for it's recovery. Any ROM you flash will include a compatible kernel and be rooted.
Hold on I'll find you a kk4 kernel so it won't bootloop even though you don't need it to boot all the way anyway... Brb
Edit: kk4 corn kernel grab the Odin flashable version of corse.
studacris said:
Cm7 is aosp based it doesn't have all the closed source hardware drivers of touch wiz, so the battery life will be worse.
As for the kernel, any will work. It's not a kernel you're going to be running it's just a transitory kernel used only for it's recovery. Any ROM you flash will include a compatible kernel and be rooted.
Hold on I'll find you a kk4 kernel so it won't bootloop even though you don't need it to boot all the way anyway... Brb
Edit: kk4 corn kernel grab the Odin flashable version of corse.
Click to expand...
Click to collapse
Thanks for all the help. So I just flash this and then get into CWM and flash whatever rom I want to?
Sweet!
You got it chief
kind3rgarten said:
Thanks for all the help. So I just flash this and then get into CWM and flash whatever rom I want to?
Sweet!
Click to expand...
Click to collapse
Correct. If you remember to put CM7 and GAPPS on the SD card before you flash it, you won't even have to boot it. Just flash it, three finger salute into recovery, and flash cm7.
studacris said:
You got it chief
Click to expand...
Click to collapse
Wow, I really expected someone to just call me a noob or tell me to read the FAQ or something. Thanks a lot, both of you.
I downloaded the corn kernel, but I've never really flashed a kernel through odin before, always just the method I had stated, does it go in PDA?
kind3rgarten said:
Wow, I really expected someone to just call me a noob or tell me to read the FAQ or something. Thanks a lot, both of you.
I downloaded the corn kernel, but I've never really flashed a kernel through odin before, always just the method I had stated, does it go in PDA?
Click to expand...
Click to collapse
You got it, just leave the others blank. You shouldn't have to play with the check boxes.
After reading the frankly scary things that the leaked ICS kernels can do to the Note, I want to go back to Gingerbread.
I'm currently on ICS Stunner 1.4.19. What is the safest way to go back to Gingerbread without bricking my phone?
Flash any stock gb rom via pc odin.
Pls look here if you dont know how:
http://forum.xda-developers.com/showthread.php?t=1424997
wtwo2 said:
Flash any stock gb rom via pc odin. Like LB2
Click to expand...
Click to collapse
Can I flash something like the KJ1 stock gingerbread ROM then? Or only LB2?
Stanley Richards said:
After reading the frankly scary things that the leaked ICS kernels can do to the Note, I want to go back to Gingerbread.
I'm currently on ICS Stunner 1.4.19. What is the safest way to go back to Gingerbread without bricking my phone?
Click to expand...
Click to collapse
Sorry mate, but the easiest answer will be: use the search function! not because I´m a douche, but more because there are a BUNCH of other threads with even the same title
brooon said:
Sorry mate, but the easiest answer will be: use the search function! not because I´m a douche, but more because there are a BUNCH of other threads with even the same title
Click to expand...
Click to collapse
Thank you for such a helpful and re-assuring comment. I'm sure you know your stuff.
Stanley Richards said:
Can I flash something like the KJ1 stock gingerbread ROM then? Or only LB2?
Click to expand...
Click to collapse
You can choose one.what you prefer.
I was on Stunner too. then disregarded the warnings and flashed Alba using the leaked kernel. I was lucky and no brick. to be safe, i installed Dafuq kernel (I think you really should, NOW).
then i decided enough of all these testing ROMs, i went back to recovery, installed abyss4.2redpill original logo kernel and flashed Rocketromv22 then v23. now i'm back to GB, safely.
so either you install the abyssnote4.2 kernel and flash your GB firmware, or if you really want to be on the SAFEST ROUTE, pc odin the stock GB and start from that.
Download AbyssNote 4.2, open the zip file and extract the zImage file. Put this on your Note and flash it with Mobile Odin. To my knowledge Mobile Odin uses it's own kernel to flash so there's no risk of bricking.
When Abyss is flashed, reboot into recovery, wipe data/cache/Dalvik and you're all set to flash any custom GB rom.
Lol me2 i scared when i see this post " ics leak brick phone " :S
and im do all that step to brick phone :S wipe in CWM when i was in ice cream sandwitch but im lucky and my phone not brick but it's always freeze :S and i want to know if my phone got damage .. the phone will complatly dead ? or got some issue or nothing ?
Stanley Richards said:
Thank you for such a helpful and re-assuring comment. I'm sure you know your stuff.
Click to expand...
Click to collapse
Yeah, sure, and I learned my stuff right here --> click
(SCNR )
Perhaps it´s my lack of language skills...but as I said: It wasn´t my intention to play the douchemaster here...sorry if it was the case (not including the link above, it´s not meant that serious!)
But mate, just check this out:
detailed steps for reverting to GB from ICS
[Q] Returning to stock GB from ICS Stunner - stuck at CWMR
[Q] ICS Stunner to gb
[Q] How do I safely revert to GB from ICS without bricking
Possible brick going from ICS back to GB
Reverting from ICS leak back to GB
how to go back to Stock GB from CM9?
Going back to Stock GB.
etc. etc. etc.......and realize that none of these threads is older than a few weeks...
Of course, what I am doing here is just ridiculous...posting an answer to your question that doesn´t bring you anything instead of just answering your question. It IS like the old frustrated man yelling at someone who´s stepping on his grass.
But mate, believe me...a few months or years later from now...YOU will be the one, writing similar posts like mine to other newbies
Stanley Richards said:
Thank you for such a helpful and re-assuring comment. I'm sure you know your stuff.
Click to expand...
Click to collapse
its a fair point tbh, there are numerous threads about reverting, it doesnt take long to either search or click a few pages into a topic
I recently upgraded my Note to official ICS (OTA) and I'm not liking it AT ALL! Now I really want to get far away from this update as possible and I'd like to switch to a CM9 nightly Rom. I've that now that I have upgraded to the official ICS Rom, I run the risk of super bricking my device. So now I ask you to help me make sure the following is correct so that I may move on from this wretched update:
DO NOT perform wipes if you are on original Samsung ICS
DO NOT perform wipes if you are on a original Samsung kernel??
Flash back to original Gingerbread Rom using odin BEFORE flashing to CM9
Flash to different kernel??
I've flashed millions of Roms but this one is scary and I just want to make sure haven't missed anything... Have I?
Thanks for you help!!
John J
Just flash a stock directly rootable GB rom, root and put CM9 on it. Then do a factory reset and you're good to go. Went that way few times already.
Akiainavas said:
Just flash a stock directly rootable GB rom, root and put CM9 on it. Then do a factory reset and you're good to go. Went that way few times already.
Click to expand...
Click to collapse
Thanks a lot man!! This is pretty much what I thought but I wanted to make ABSOLUTE sure! Cheers!
John J
So is the super-brick BUG on the official ICS OTA?? OMG
And yeah go back to gingerbrear via odin, get root then flash any CM9 tru CWM no problems...
I'd like to do something similar to what the OP wants to do however I have rooted and installed CWM on an official/stock ICS rom. So if I wanted to flash back to a stock gingerbread rom would I need to remove CWM and/or un-root?
darkmuck said:
I'd like to do something similar to what the OP wants to do however I have rooted and installed CWM on an official/stock ICS rom. So if I wanted to flash back to a stock gingerbread rom would I need to remove CWM and/or un-root?
Click to expand...
Click to collapse
There is no need to unroot first. You can flash stock GB rom directly via Odin.
I've now flashed to GB but before I move on to a CM9 nightly, do you recommend I flash the CM9 kernel as well? Seems like it is not a prerequisite but I would like to make sure. Thanks.
John J
afaik, when flashing a CM9 Nightly, the eligible kernel is built in, so no need to flash anything but the ROM.
i'm on one of imilkas first CM9 port and it says [email protected] #1 under Kernel version in settings.
Yes. The correct kernel is included in the nightly.
Hello.
I got a GNote International version today and it came with ICS already installed.
I have my basic share of experience on Rooting and Flashing CWM and ROMS on some WiFi-Only Samsung devices, but after 6 or 7 hours of reading different posts and guides, I still cannot understand some things.
I already Rooted my GNote, but CWM disappeared, which I see is normal.
My Main question is, coming from a Stock ICS ROM and Kernel, what in the world should I do to safely flash AOKP Build 38 and retain CWM?.
My current Android version is 4.0.3
Baseband: N7000XXLPT
Kernel: 3.0.15-N7000XXLPY-CL474507
I see I can't flash Franco's Kernel and then use AOKP, so that's out of the question.
What ROMs I can flash if I first install Abyss kernel v4.2?.
What is a binary counter?
I'm really lost here, and I don't want to brick my device, so please help me out with some answers.
Thank you in advance.
Which ROM do you want to flash?
I recommend you to play with you're device for sometime until you understand everything beneath it.
After that decide which ROM you want to flash.... than stick with that ROMs installation instructions.
Download everything you need before flashing...
Before flashing custom ROMs you need to flash Stock GB first .
Stock ICS is not safe for all this things.
If you want to stay safe in stock ICS than don't perform Data wipe/factory reset...
Flash a safe kernel like Hardcore Speedmod...
Here is the link
http://forum.xda-developers.com/showthread.php?t=1673072
And Most important don't forget to press THANKS for anyone who is trying to help...
I appreciate your help.
I would like to flash Kang's AOKP.
Flashing stock GB first is what's I didn't know.
Sent from my YP-G70
chintamanijaipuri said:
Which ROM do you want to flash?
I recommend you to play with you're device for sometime until you understand everything beneath it.
After that decide which ROM you want to flash.... than stick with that ROMs installation instructions.
Download everything you need before flashing...
Before flashing custom ROMs you need to flash Stock GB first .
Stock ICS is not safe for all this things.
If you want to stay safe in stock ICS than don't perform Data wipe/factory reset...
Flash a safe kernel like Hardcore Speedmod...
Here is the link
http://forum.xda-developers.com/showthread.php?t=1673072
And Most important don't forget to press THANKS for anyone who is trying to help...
Click to expand...
Click to collapse
Please, let me know if what I'm understanding is correct.
In order to flash anything safely, I need to go back to a Stock Gingerbread ROM.
Once there, I can flash kernels and ICS custom ROMs.
The following thread shows stock GB ROMs, but which one should I download if I got my GNote on the US with ICS preloaded:
http://forum.xda-developers.com/showthread.php?t=1424997
Thank you.
You can flash pretty much any stock gingerbread rom using pc odin. However, there have been some bricks doing this, so I strongly suggest to wait until samsung releases a patch (http://forum.xda-developers.com/showthread.php?t=1698977). Now, if you want to flash a gb rom anyway, be sure that you don't wipe while being on an ics kernel.
oscarsalgar said:
You can flash pretty much any stock gingerbread rom using pc odin. However, there have been some bricks doing this, so I strongly suggest to wait until samsung releases a patch (http://forum.xda-developers.com/showthread.php?t=1698977). Now, if you want to flash a gb rom anyway, be sure that you don't wipe while being on an ics kernel.
Click to expand...
Click to collapse
I did Factory Resets a couple of times already inside ICS with no problems, so I'm guessing that doing a Wipe from Stock Recovery is what causes a hardbrick, right?
As far as I've read, any erase command could trigger the emmc bug. I'm not an expert though, but I guess a factory reset from settings could be as dangerous as a factory reset in stock recovery
oscarsalgar said:
As far as I've read, any erase command could trigger the emmc bug. I'm not an expert though, but I guess a factory reset from settings could be as dangerous as a factory reset in stock recovery
Click to expand...
Click to collapse
I better wait for a official fix then. This damn phone cost me an arm and a leg.
Muchas gracias por su apoyo, lo aprecio mucho.
SirRhor said:
I better wait for a official fix then. This damn phone cost me an arm and a leg.
Muchas gracias por su apoyo, lo aprecio mucho.
Click to expand...
Click to collapse
The Stock interface is so freaking ugly, that it's better not to wait till the OFFICIAL FIX.
Even if they do that, the interface would still be ugly.
Just follow the safe steps which don't even imply adding triangle:
1)flash the rooted GB (by bovias) (you will find the link inside below link, follow the instructions from there, flash with PC odin)
2)Then CWM via mobile(!!!) odin
follow the first part from here:
http://forum.xda-developers.com/show....php?t=1659768
3)And then go to C9 Nightlies thread in General and flash it, it looks so beautiful and accurate and has so many features, has secure kernel and is 4.0.4
*Please read carefully the instructions from the above mentioned 2 threads before flashing anything and you can be sure that everythin will be non-risky and smooth
It's great
klukiyan said:
The Stock interface is so freaking ugly, that it's better not to wait till the OFFICIAL FIX.
Even if they do that, the interface would still be ugly.
Just follow the safe steps which don't even imply adding triangle:
1)flash the rooted GB (by bovias) (you will find the link inside below link, follow the instructions from there, flash with PC odin)
2)Then CWM via mobile(!!!) odin
follow the first part from here:
http://forum.xda-developers.com/show....php?t=1659768
3)And then go to C9 Nightlies thread in General and flash it, it looks so beautiful and accurate and has so many features, has secure kernel and is 4.0.4
*Please read carefully the instructions from the above mentioned 2 threads before flashing anything and you can be sure that everythin will be non-risky and smooth
It's great
Click to expand...
Click to collapse
Thank you for the info. I already flashed custom ROMs. It was a pain to do it with all the risk involved.
So far I tried LiquidSmooth 2.2 and KingDroid 3.
Now I would like to see how I can install Kang's AOKP.
I've been lucky so far, no issues until today.
I appreciate your support.
Sent from my YP-G70
Hi, I have an international varient of the Galaxy Note GT N7000 which using Chainfire's Got Brick App v1.1 says:
eMMC Chip
Type: VYL00M
Revision: 0x19
Verdict: Danger! This eMMC chip is "Known" to have the brick bug!
I once had installed a custom Kingdroid ROM v3 and wiped it but it had resulted in a Hardbrick/Superbrick so i had to take it Samsung Service Center to get it fixed. They have repaired it and given me back the handset with the Stock ICS ROM. Here are the details:
Model Number: GT-N7000
Android Version: 4.0.3
Baseband Version: N7000XXLPT
Kernel Version: 3.0.15-N7000JPLPD-CL643396
[email protected]#3
SMP PREEMPT Thu May 31...
Build Number: IM74K.JPLPD
Now i have done some researched and found that this bug is only triggered with kernels (ICS stock & leaked) which have the eMMC_Erase function/command. GB kernels are not known to have this erase function so they are safe.. Also the two safe kernels are franco r3 and speedmod k3 (Correct me if im wrong). Can anyone please guide me on the following:
1) Should I flash Stock Gingerbread OR ICS Kernel(franco/speedmod)?
2) Should I use Recover or ODIN?
3) Plz Provide the links for the Kernels - Franco R3 & Speedmod K3 which are safe?
4) Will the above Kernels provide root access?
5) Is abyss kernel safe (because it supports GPU overclock)?
6) Can i flash an ICS kernel over a Gingerbread ROM?
For answering please answer in a similar numbered way so that it is easy to read and understand for me as well as future audience! Thanking everyone who takes time to read and answer!
I use Speedmod kernel and i confirm that it is safe (for me at least anyway) Im using CleaNote ICS ROM, So I would suggest you also use speedmod kernel,
You Flash it in Odin, It will give you CWM and Root too !
Ive attached the kernel to the post for you.
Abyss kernel is safe, But its for GB ROMs only, You are on ICS so it wont work.
I dont know if you can flash ICS kernel over GB ROM, However, Your are on ICS so you shouldnt need to worry about that.
don't really want to hijack your thread an i dont really want to make a whole new thread for a simple question.
as a noob, im just wanting to know, if i update my stock gb to stock ics via software update, are there still chances of this emmc bug/brick thats going on?
and the battery drain issues, do they only exist in custom roms or does it exist in stock roms too?
cheers.
azzledazzle said:
I use Speedmod kernel and i confirm that it is safe (for me at least anyway) Im using CleaNote ICS ROM, So I would suggest you also use speedmod kernel,
Click to expand...
Click to collapse
Thanks for the confirmation mate, one more thing to ask you: Is the speedmod kernel faster than the stock ICS kernel? Is there any flaws such as battery drain/WIFI problem with it? Also does it support GPU OC? Thanks once again for your help!
little-vince said:
don't really want to hijack your thread an i dont really want to make a whole new thread for a simple question.
as a noob, im just wanting to know, if i update my stock gb to stock ics via software update, are there still chances of this emmc bug/brick thats going on?
and the battery drain issues, do they only exist in custom roms or does it exist in stock roms too?
cheers.
Click to expand...
Click to collapse
Firstly get your Galaxy Note checked using Chainfires App (Gotbrick v1.1). If the verdict says "Danger" only then does your device have this problem. My Galaxy Note (Rev 0x19) had this problem and came with GB out of the box and i upgraded it to ICS through Samsung Kies and it worked fine. So i do not think that while updating to ICS via Kies will cause this problem. As of what i know it is triggered when a command eMMC errase is triggered when either doing a factory reset or wipe through recovery. The update as such did not brick my device, however this does not mean it cannot brick yours. I am no expert on this so be a little cautious while updating. I would suggest stick to GB until Samsung Releases a safe stock ICS ROM with a safe Kernel. Cheers!
really easy
1: (optional ) in GB do factory reset (after you have made a backup with TB)
2: put phone in Download mode.
3: use PC odin flash STOCK ICS rom
4: reboot device let it load
5: put device back into download mode
6: use PC ODIN flash Speedmod k3-3
7: reboot
8: launch CWM and tell it to reboot in cwm recovery
9: load your custom rom of your choice
i HIGHLY recommend doing ONLY THE FACTORY RESET WIPE data and cache in GB before you start anything.
ONCE you are in ICS and have successfully loaded speedmod or franco's kernel then it is safe to do a factory wipe if you want. but ONLY after one of those 2 Kernels are on your device.
EMMC BUG. is affected in all N7000 Devices only . only the devices sent to the USA have the revision the non 0x19 bug .
rp4k said:
EMMC BUG. is affected in all N7000 Devices only . only the devices sent to the USA have the revision the non 0x19 bug .
Click to expand...
Click to collapse
okay...
truth is i haven't actually bought the note yet.
just doing substantial amounts of research beforehand.
im pretty sure only the n7000 model is out in australia.
but it's all okay if i dont factory reset/wipe/anything-risky-in-general right?
little-vince said:
okay...
truth is i haven't actually bought the note yet.
just doing substantial amounts of research beforehand.
im pretty sure only the n7000 model is out in australia.
but it's all okay if i dont factory reset/wipe/anything-risky-in-general right?
Click to expand...
Click to collapse
Yes, this bug is known to trigger usually when you do a wipe using the recovery. However there have been some cases when doing a factory reset via the settings has also resulted in a brick. However if you stay away from recovery and do not intend to doing flashing/wipes then i guess you should be ok. And it is a matter of time before Samsung Comes up with a solution. They are said to be working on this bug already. I have the N7000 which i bricked once while flashing and then wiping but i got it repaired since i had warranty. Since then i have stayed away from wiping or installing any custom roms so the device has not given any problems. Hope this info helps! Cheers!
Rom doesnt load during boot
Dear Developers
I rooted my galaxy note and soon as that i got gained super user access for chain fire app, then i flashed CWM and installed crisello rom with abbysys kernel , it installed all the files correctly and soon after that the phone rebooted .After reboot the phone went inside the boot menu ( the world of galaxy UI boot menu ) and it frozen since then
i tired flashing various custom or stock roms and still the same problem i face
If someone could help me out on what the problem is and how i could get a fix to it
cuteglen said:
Dear Developers
I rooted my galaxy note and soon as that i got gained super user access for chain fire app, then i flashed CWM and installed crisello rom with abbysys kernel , it installed all the files correctly and soon after that the phone rebooted .After reboot the phone went inside the boot menu ( the world of galaxy UI boot menu ) and it frozen since then
i tired flashing various custom or stock roms and still the same problem i face
If someone could help me out on what the problem is and how i could get a fix to it
Click to expand...
Click to collapse
What rom are you on? Have you performed any wipes or factory resets?
Sent from my GT-N7000 using xda premium
Hi everybody
I have three questions if You can help me
1- Are speedmode and franco Kernels the only safe kernels for stock ICS?
2- Can I flash CM9 from stock ICS or it is safer to do it from GB rom?
3- Can I flash CM9 kernel for stock rom?
Thanx in advance
iraqi4ever80 said:
Hi everybody
I have three questions if You can help me
1- Are speedmode and franco Kernels the only safe kernels for stock ICS?
2- Can I flash CM9 from stock ICS or it is safer to do it from GB rom?
3- Can I flash CM9 kernel for stock rom?
Thanx in advance
Click to expand...
Click to collapse
1. Afaik yes
2. NO, you'll brick, flash from GB kernel, I know some have done from abyss.
3. No. CM based not compatible with Touchwiz framework.
Sent from my GT-N7000 using xda premium
I have a quick ( hopefully) question about the brick bug. I already asked but I think a mod must have deleted the whole thread, even though the thread was about the brick bug and I think I might have been bringing a new way ( well for some anyway) to flash safely to new ROMs.
So anyway, I have a 'safe' kernel ( speedmod), and I want to try out 4.0.4 stock ROM. I have extracted the stock ROM zip and the tar file inside. In there is the Zimage.
Do I just delete the Zimage then re-zip and flash from CWM?
OR Do I have to replace the Zimage with another, 'safe', Zimage ( for example just put the zimage in there from speedmod because I want to keep that for now). Does there NEED to be A Zimage there, or will it work fine without one. I don't want to start flashing the ROM and it get stuck half way through.
If it will work this way then this might be a fairly easy way for anybody to flash any new ROM they want. They'll just need to get a safe kernel on there in the first place.
SpyderTracks said:
1. Afaik yes
2. NO, you'll brick, flash from GB kernel, I know some have done from abyss.
3. No. CM based not compatible with Touchwiz framework.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
thank you for your response
just to be sure you said that it is unsafe to flash CM9 from stock ICS?
can we flash CM9 from stock ICS rom with safe kernel such as franco or speedmod
sorry for bothering you and thank you again
iraqi4ever80 said:
thank you for your response
just to be sure you said that it is unsafe to flash CM9 from stock ICS?
can we flash CM9 from stock ICS rom with safe kernel such as franco or speedmod
sorry for bothering you and thank you again
Click to expand...
Click to collapse
Only from GB kernel such as abyss. If you flash from ics kernel you WILL brick. This goes for all cm based roms.
Sent from my GT-N7000 using xda premium
kyllerbuzcut said:
I have a quick ( hopefully) question about the brick bug. I already asked but I think a mod must have deleted the whole thread, even though the thread was about the brick bug and I think I might have been bringing a new way ( well for some anyway) to flash safely to new ROMs.
So anyway, I have a 'safe' kernel ( speedmod), and I want to try out 4.0.4 stock ROM. I have extracted the stock ROM zip and the tar file inside. In there is the Zimage.
Do I just delete the Zimage then re-zip and flash from CWM?
OR Do I have to replace the Zimage with another, 'safe', Zimage ( for example just put the zimage in there from speedmod because I want to keep that for now). Does there NEED to be A Zimage there, or will it work fine without one. I don't want to start flashing the ROM and it get stuck half way through.
If it will work this way then this might be a fairly easy way for anybody to flash any new ROM they want. They'll just need to get a safe kernel on there in the first place.
Click to expand...
Click to collapse
Hiya, yep, you can just delete the zimage file, no need to replace, it will just skip writing that partition.
Sent from my GT-N7000 using xda premium
Gave that a go last night and I must not be doing something right. Either I need to re-zip it differently or I need to use something other than CWM (mobile odin?) because it's just aborting before it actually starts flashing anything.
Suppose I could always flash the separate elements on pc odin?
kyllerbuzcut said:
Gave that a go last night and I must not be doing something right. Either I need to re-zip it differently or I need to use something other than CWM (mobile odin?) because it's just aborting before it actually starts flashing anything.
Suppose I could always flash the separate elements on pc odin?
Click to expand...
Click to collapse
Try mobile odin. If you point to the tar, it should load all the components. You can then review which components are being flashed.
Sent from my GT-N7000 using xda premium
iraqi4ever80 said:
Hi everybody
I have three questions if You can help me
1- Are speedmode and franco Kernels the only safe kernels for stock ICS?
2- Can I flash CM9 from stock ICS or it is safer to do it from GB rom?
3- Can I flash CM9 kernel for stock rom?
Thanx in advance
Click to expand...
Click to collapse
1. Add goku, dafuq, gl-notecore and abyss42 (GB) to your list.
2. Only do it from a GB firmware or at least a GB kernel like abyss42. SPECIFIC instructions per firmware is listed for a reason. Follow those instructions to the letter.
3. No.
Sent from my GT-N7000 using xda app-developers app
kyllerbuzcut said:
Gave that a go last night and I must not be doing something right. Either I need to re-zip it differently or I need to use something other than CWM (mobile odin?) because it's just aborting before it actually starts flashing anything.
Suppose I could always flash the separate elements on pc odin?
Click to expand...
Click to collapse
Stock rom in a zip? Are you sure you are nit flashing a custom rom? Point us to the file/thread please.
If it is a custom rom, the it is meant to be via CWM.
1. Flash abyss42
2. Reboot recovery
3. Do your wipes
4. Flash.
Im sure there is a specific instruction on where you got that file. Or better yet, go to dr. Ketans thread and get your stock rom from there.
Sent from my GT-N7000 using xda app-developers app
It's just the standard rom file from sammobile.It does come as a zip you know. If you unzip it, then use rar on it you can see all the bits. I thought if I just put a different zimage in there it would just go ahead and use that, but didn't seem to like it after I zipped it all back up again.
Tonight I've ended up getting chainfires excellent CF-Root kernel.Flashed that through odin, over my speedmod kernel.
Put just the factoryfs part of the stock rom zip onto the SD card and flashed that using the cwm app that CF-Root installs for you.. Now have CF-Root kernel and 4.0.4 firmware.
If you don't already have a "safe" kernel then I dunno what the brick chances would be, but since I had a safe one already I thought it couldn't hurt to try it out.
The reason I haven't flashed the hidden, cache, model and sbl parts of the zip is that simply they wouldn't fit on my SD card If it behaves funny or I can make space then I'll try the rest too. And the reason I didn't flash the zimage from the zip should be fairly obvious. Because I don't want a brick
EDIT: I managed to clear some space on the SD and flashed the rest of it. Seems to be working ok, so far anyway. I'm hoping the battery issues from 4.0.3 will be a little better. This is a really good way of doing it all as you can just swap out a potentially bad kernel for one that has been 'protected' by having te emmc cap erase turned off.