[Q] Safe to flash - Galaxy Note GT-N7000 Q&A, Help & Troubleshooting

Hi guyz, I got a friend you wants me to flash for him his stock n7000 ICS 4.0.4
Considering how risky it is to go custom on an n7000, I was wondering if any of the new JBs are safe to flash coming from a stock 4.0.4 ICS?
Like the nigtlies from CM or the JellyBeer v4.18
He really wants to jump from 4.0.4 to 4.2.2.
Any suggestions?

The safest way is to flash Stock Gingerbread on Odin, root, install CWM, Wipe data/cache, and flash any CM 10.1 based ROMS. I am using JellyBAM since a few months, and its stable with excellent battery life.

aces170 said:
The safest way is to flash Stock Gingerbread on Odin, root, install CWM, Wipe data/cache, and flash any CM 10.1 based ROMS. I am using JellyBAM since a few months, and its stable with excellent battery life.
Click to expand...
Click to collapse
Thanks for the tip. We installed CWM (philz thingy) already and we already made a back-up. Device is already rooted too. Do i still have to flash Gingerbread thru odin? or flash directly CM 10.1?

OMG... since u already got philz safe kernal n backup already done u can just direct flash to the custom rom u want !

alvinhaw said:
OMG... since u already got philz safe kernal n backup already done u can just direct flash to the custom rom u want !
Click to expand...
Click to collapse
Hahahaha, just checking. I wanna make sure his device is ready. Thanks man! Gonna flash later when I get to work.

Related

Going back to GB from the German XXLPY ICS

Hi everyone
I am new to Android. I upgraded my galaxy note GT N7000 to the official ICS German version. everything went smooth but then the battery consumption was terrible. I tried Franco kernel #3 and it didn't help so i restored the other kernel using CWM. everything is fine now but i heard about the risk of phone brick. I want to go back to GB but all the methods i reviewed involve wiping data which is the risky step that might hard brick the phone. Any suggestions? ?
Thank you and forgive my humble English
Sent from my GT-N7000 using XDA
afaik there is no way to downgrade (officially) without wiping everything :/
flash via cwm the abyss kernel, reboot in recovery through this kernel
Wipe & reflash from abyss a GB rom
I did a CMW backup before flashed to German ICS. After that find out that the ori ics is not really fast and stable, so I restore back to GB through CMW..
ckkwang said:
I did a CMW backup before flashed to German ICS. After that find out that the ori ics is not really fast and stable, so I restore back to GB through CMW..
Click to expand...
Click to collapse
unfortunately I didn't back up my GB
Spartagek said:
flash via cwm the abyss kernel, reboot in recovery through this kernel
Wipe & reflash from abyss a GB rom
Click to expand...
Click to collapse
probably I will try that. I was decided to keep the ICS till a solution for the brick comes up but this afternoon the phone screen started to go blank and display like old tv so it seems I have to go back to GB.
Another question please : Is there a risk that the phone will "auto-brick" by itself if I just keep the current ICS without making any changes or the brick happens only while installing or changing something??

[Q] Question about kernals

hey
im currently running rooted ICS 4.0.3 XXLQ2 that i rooted with the CF-Root kernal.
My question is, is there an Abyss kernal that i can flash over that with ODIN so i can use it instead?i hear that abyss is safer than CF and you can actually install custom ROMs from it. Also, I'd usually find this info myself but everything i can find about it is a bit confused so i would like a simple yes or no answer
Cheers
Abyss is a GB kernel. DO NOT use it on ICS!
Abyss Note kernel is not compatible with ICS.
ah right OK, some folk are saying that it was compatible with ICS, so I take it my best bet for using custom ROMs would be to flash back to stock GB then flash Abyss, yeah?
EDIt: i meant to say, are there any safe custom kernals out yet for ICS that are ROM flashable and wipe-safe?
"ROM flashable and wipe-safe?"
???
once you have a rooted rom with a custom recovery like CWM then you can flash most kernels. Some kernels arn't compatable with some roms but the thread will usauly indicate which roms work best with the kernel.
I most cases when you are flashing a new ics rom it is not safe to do a full wipe.
I have just upgraded to rocket rom v6 i did not full wipe when flashing but once the rom was up and running i just go back to cwn and do a full wipe, seems to work for me.
Hope this gives you some info on the matter.
olliesmith6121 said:
"ROM flashable and wipe-safe?"
???
once you have a rooted rom with a custom recovery like CWM then you can flash most kernels. Some kernels arn't compatable with some roms but the thread will usauly indicate which roms work best with the kernel.
I most cases when you are flashing a new ics rom it is not safe to do a full wipe.
I have just upgraded to rocket rom v6 i did not full wipe when flashing but once the rom was up and running i just go back to cwn and do a full wipe, seems to work for me.
Hope this gives you some info on the matter.
Click to expand...
Click to collapse
what i meant by wipe safe and rom flashable is that im not gonna brick the phone by doing a factory data wipe or by flashing a custom rom, from what i have read if you flash from pretty much any ICS kernal to a custom rom its an insta-brick
You had the right idea at first. Some ics kernels (eg Franco, cf and speedmod) are probably safe to wipe with. I say probably because they have had the emmc wipe command removed.
But to be guaranteed, reboot into cwm (assuming you are already rooted) then flash abyss 4.2 GB. I use the red version so I can be sure I am flashing from GB.
Then reboot to recovery. Do not reboot the phone - it will not work - but it will happily boot to recovery. You are now in GB recovery and can wipe with no risk of brick bug at all. Flash any cwm flashable rom. Just make sure you had copied it to your SD card before you started this process!!!
Sent from my GT-N7000 using Tapatalk 2
apd said:
You had the right idea at first. Some ics kernels (eg Franco, cf and speedmod) are probably safe to wipe with. I say probably because they have had the emmc wipe command removed.
But to be guaranteed, reboot into cwm (assuming you are already rooted) then flash abyss 4.2 GB. I use the red version so I can be sure I am flashing from GB.
Then reboot to recovery. Do not reboot the phone - it will not work - but it will happily boot to recovery. You are now in GB recovery and can wipe with no risk of brick bug at all. Flash any cwm flashable rom. Just make sure you had copied it to your SD card before you started this process!!!
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
+1

[Q] Stock ICS -> ParanoidAndroid

I apologize if this has been asked several times before but I want to be 100% sure I'm doing the right thing since my Note currently has brickbug. When I first got ICS via a Kies update, I had to do a stock wipe from Settings because apps were crashing and freezing. As far I can tell there hasn't been any permanent damage. I've since done another OTA update via WiFi.
I want to go from Stock ICS 4.0.4 to ParanoidAndroid JellyBean
Region - Open Germany
Baseband version - N7000XXLRK
Kernel version - 3.0.15-N7000XXLRK-CL811902
Can I simply download the PhilZ-cwm6-XXLRK-XEU-2.7 kernel http://www.mediafire.com/file/269h649de0bch14/PhilZ-cwm6-XXLRK-XEU-2.7-signed.zip onto my microsd card and flash from stock recovery?
Then can I use CWM to flash latest build of JB ParanoidAndroid from http://goo.im/devs/Utacka/n7000?
Also will this cause the Yellow Triangle?
what i did was flash hydracore kernel with mobile odin then flash paranoid android as described in its own thread.
also make a full wipe AFTER flashing hydracore from CWM
kromosto said:
what i did was flash hydracore kernel with mobile odin then flash paranoid android as described in its own thread.
also make a full wipe AFTER flashing hydracore from CWM
Click to expand...
Click to collapse
Flashing the PhilZ kernel via Stock Recovery wouldn't work? That seems to be the most simple method. Does HydraCore have advantages over PhilZ?
it should work too. i just write the method i used and of course it is not the only method to do it.
kromosto said:
it should work too. i just write the method i used and of course it is not the only method to do it.
Click to expand...
Click to collapse
Great, thanks.
dr.ketan said:
yes you can root directly from stock recovery with Phillz kernel (Method 1A) OR with simlpe SuperSU file (method 1B)
read this
http://forum.xda-developers.com/showthread.php?t=1329360
Click to expand...
Click to collapse
I found another recent thread. This was also helpful, thank you!
kromosto said:
it should work too. i just write the method i used and of course it is not the only method to do it.
Click to expand...
Click to collapse
Ok, I have PhilZ on my Note now. But still have stock ICS. The ParanoidAndroid threads say "Make sure to run CM9 or an AOSP-based ROM : FLASHING FROM STOCK ICS OR ROMS BASED ON STOCK ICS WILL RESULT IN A BRICK!"
So does that mean I can't just flash HydraCore and then flash ParanoidAndroid? Do I have to flash a CM9 ROM or other AOSP ROM before ParanoidAndroid? Also is PhilZ kernel compatible with ParanoidAndroid?
orificium said:
Ok, I have PhilZ on my Note now. But still have stock ICS. The ParanoidAndroid threads say "Make sure to run CM9 or an AOSP-based ROM : FLASHING FROM STOCK ICS OR ROMS BASED ON STOCK ICS WILL RESULT IN A BRICK!"
So does that mean I can't just flash HydraCore and then flash ParanoidAndroid? Do I have to flash a CM9 ROM or other AOSP ROM before ParanoidAndroid? Also is PhilZ kernel compatible with ParanoidAndroid?
Click to expand...
Click to collapse
I did exactly the same recently (but I went from stock to another ROM which had the same message, not ParanoidAndroid) - ran philz then the kernel should be safe which means you should be safe to flash to another ROM. That brick message on the thread I assume only applies if you are running a stock ROM with the stock kernel. If you want to be sure check in Settings>About Phone>Kernel Version - see thread here http://forum.xda-developers.com/showthread.php?t=1857556.
orificium said:
I apologize if this has been asked several times before but I want to be 100% sure I'm doing the right thing since my Note currently has brickbug. When I first got ICS via a Kies update, I had to do a stock wipe from Settings because apps were crashing and freezing. As far I can tell there hasn't been any permanent damage. I've since done another OTA update via WiFi.
I want to go from Stock ICS 4.0.4 to ParanoidAndroid JellyBean
Region - Open Germany
Baseband version - N7000XXLRK
Kernel version - 3.0.15-N7000XXLRK-CL811902
Can I simply download the PhilZ-cwm6-XXLRK-XEU-2.7 kernel http://www.mediafire.com/file/269h649de0bch14/PhilZ-cwm6-XXLRK-XEU-2.7-signed.zip onto my microsd card and flash from stock recovery?
Then can I use CWM to flash latest build of JB ParanoidAndroid from http://goo.im/devs/Utacka/n7000?
Also will this cause the Yellow Triangle?
Click to expand...
Click to collapse
My advice is dont use Philz kernel for flashing ICS to JB... becz i read somewhere no unique Philz kernel to supports for ICS and JB
I had done many time ICS to JB (like Kingdroid RAM to Paranoid JB, Paranoid JB to STOCK ICS etc. ) no issues...... because of I used Hydracore 4.3b kernel..
thanks
koosh34 said:
I did exactly the same recently (but I went from stock to another ROM which had the same message, not ParanoidAndroid) - ran philz then the kernel should be safe which means you should be safe to flash to another ROM. That brick message on the thread I assume only applies if you are running a stock ROM with the stock kernel. If you want to be sure check in Settings>About Phone>Kernel Version - see thread here http://forum.xda-developers.com/showthread.php?t=1857556.
Click to expand...
Click to collapse
The Kernel version looks the same to me as it did before I went to PhilZ. I rebooted into recover to make sure CWM is on there, which it is. And I installed a custom boot animation to make sure that worked, and it did.
Sounds like I should go to HydraCore Kernel first since it's compatible with TW ICS and JB then flash ParanoidAndroid ROM.
m_rajaganesh said:
My advice is dont use Philz kernel for flashing ICS to JB... becz i read somewhere no unique Philz kernel to supports for ICS and JB
I had done many time ICS to JB (like Kingdroid RAM to Paranoid JB, Paranoid JB to STOCK ICS etc. ) no issues...... because of I used Hydracore 4.3b kernel..
thanks
Click to expand...
Click to collapse
Thanks, sounds like my best course of action is to flash HydraCore now and that way I can test various ICS/JB ROMs.
Since my original post I have:
Flashed PhilZ-cwm6-XXLRK-XEU-2.7-signed kernel in stock recovery to get original root and safe kernel.
Flashed GL_HYDRACORE_v5-4_STD kernel because I thought that's what I needed for PA.
Flashed pa_n7000-2.51-24OCT2012-192916 and followed instructions from Hydracore thread which said to flash kernel after done flashing new ROM and gapps. However - PA would not boot after that. I also tried pa_n7000-2.52-29OKT2012-101254-Utacka this way. Same problem.
So I decided to flash pa_n7000-2.51-24OCT2012-192916 this time but without changing the kernel. Booted fine this time and my phone flys now! Way faster than Stock ICS 4.0.4. It's nuts that official ROMs, by comparison, are so slow.
So I'm trying to understand how to know which kernels will work with which ROMs. So I've been reading the various stickies and this thread in particular - very carefully. And I see the part about "WARNING: Do NOT use the below listed kernels for any CM10 build dated October 3rd or newer because your system will not boot.". I assume this why I was having issues after flashing Hydracore immediately after PA? And if I'm understanding this right, I could use the new HydraCore v7 with this PA JB ROM I'm on now? Is that because of this new MALI driver?
I did an EFS Backup after I did the original PhilZ kernel install but I never did a Nandroid backup while I had stock ICS. Should I just do that on any functional ROM now to make sure I have a full working copy of something to get my phone restored if something goes haywire? Is that the idea?
Also a lot of people seem to recommend flashing ROMs using PC ODIN. Is this considered safer or less risky than using CWM?
ParanoidAndroid JB imilka build has been great - but I noticed a few annoying issues:
1. WiFi signal seemed a lot better in Stock ICS than it does with PA. My signal is always "Poor" in my bedroom and I'm not very far from the wireless router but when I'm in the living room - it's excellent. Is this to be expected or is there something I can do about that?
2. Audio issues - sometimes I have to play with the volume to get speaker phone working after hitting the on-screen toggle.
3. None of the Voice Input stuff works. It just says "Initializing" and then "I didn't catch that". Also described near the end of the PA thread but haven't seen anyone reply with a fix.
4. No timer/stopwatch built into clock app. Can someone recommend a good app?
5. When I change the Slider shortcuts under Settings->Interface->Lock screen, they don't save. It always go back to default - Camera, Google Search and Unlock options only.
6. Looking for a nicer clock widget. Can someone make a recommendation?
Just wanted to point out that I love that it automatically had the StraightTalk APN configured for me. I know you're probably thinking - yeah so? - but I'm relatively new to android ROMing - just been lurking for awhile - so it was a pleasant surprised.
Any help would be greatly appreciated.
Hi guys,
I am new to this forum and to flashing custom roms in particular. I have read a lot of stuff about the eMMC chipbug and how to avoid it. I want to install pa_n7000-2.53-05NOV2012-125144-Utacka from stock ICS 4.0.4 with this kernel: speedmod-kernel-n7000-ics-k3-15-Odin. Is it safe to flash the PA with the CWM of the speedmod kernel or should I go back to gingerbread as I have read on some other fora?
Thanks in advance!
yes its safe. speedmod is a safe kernel
nokiamodeln91 said:
yes its safe. speedmod is a safe kernel
Click to expand...
Click to collapse
So all I have to do is reboot in cwm recovery, and install PA from sd card, then install Gapps, then wipe/factory reset, wipe cache and wipe Dalvik cache and it should work 'without' risk?
yeah.. first wipe data /factory reset
wipe cache
wipe dalvik
format /system
then install zip from sd
nokiamodeln91 said:
yeah.. first wipe data /factory reset
wipe cache
wipe dalvik
format /system
then install zip from sd
Click to expand...
Click to collapse
And then it should be good to go or should I wipe again?
not until you face any app issues or so
want to be safe before flashing PA
hi guys
i m using rocket rom. now i want to flash PA 2.99
i m concerned about this warning...Make sure to run CM9/10 or an AOSP-based ROM : FLASHING FROM STOCK ICS OR ROMS BASED ON STOCK ICS WILL RESULT IN A BRICK! - You're warned!
what should i do..?
RR version ? It has a safe kernel so you are good to go. You can ignore that warning
nokiamodeln91 said:
RR version ? It has a safe kernel so you are good to go. You can ignore that warning
Click to expand...
Click to collapse
YES it has one of philz safe kernels..
so what i think is its totally safe to flash a new rom if u have a safe kernel. Am i right???
what if i flash a kernel(safe one) which is not compatible with my currrent rom....is it risky or my device will just not boot or anything else.....??

[Q] JB to GB downgrade failure?

So, this is what happened. I first upgraded to the latest official JB 4.1.2 XXLSA firmware. I noticed that it still wasn't as fast as I'd like, and wanted to try a custom ROM instead. I read through the guides in here and get that I have to downgrade to a GB ROM first in order for me not to hardbrick my phone. So, I download "N7000XBKK4 ------ 2.3.6 2011 November------- N7000OXXKK5--------------------- Nordic countries" from that list over stock ROM's in the Q&A root guide here: http://forum.xda-developers.com/showthread.php?t=1424997 . I follow the flashing guide to the letter, puts my phone in download mode, runs the flash via Odin, the phone restarts, and everything goes south. Basically this happens: When I start my phone it get's to the point in the GB initial startup where I'm to touch the Android to start, but then all it does is throw messages at me about this service and that service having stopped responding, untill the phone reboots. So now I have reflashed back to the JB ROM.
So basically, what am I doing wrong, and what can I do to make a proper downgrade so I can get rooted, install CWM and get down and get it on with some custom ROM's?
Thx in advance!
Same happened with me. I flashed GB and was getting force close messages. But not a big problem. Just flash GB rom again. And after flashing just delete all user data from recovery and reboot. U wont get those messages any more.
Sent from my GT-N7000 using XDA Premium HD app
You always need to WIPE data / factory reset after downgrading from JB .. GB is safe to go ahead.. if you choose ICS then first flash a safe kernel and then do wipe
It seems to me that KK5 is non wipe, which explains why you got those messages. The rest is detailed in nokiamodeln91's message BTW, JB is still not official for our Notes. What you installed was a leak with a safe kernel (if it was Philz).
nokiamodeln91 said:
You always need to WIPE data / factory reset after downgrading from JB .. GB is safe to go ahead.. if you choose ICS then first flash a safe kernel and then do wipe
Click to expand...
Click to collapse
Stock GB kernel its safe and Stock ICS Unsafe?
Yiannis75 said:
Stock GB kernel its safe and Stock ICS Unsafe?
Click to expand...
Click to collapse
Exactly.
I had this issue too when downgrading to GB. Wipe Cache and Dalvik and you should be ok from then on.
Wow. A lot of replies in just a single day. You guys are awesome
Now you say that the KK5 is non-wipe. Are there any GB-roms which are wipe, so to speak? Or do I have to do the flash to GB, enter recovery, wipe cache partition and do wipe/factory reset, then reboot into a now working phone, set up for root with USB and so forth, root and install CWM, copy the custom ROM to my SD-card (gonna go for ParanoidAndroid) as well as Google services if I want those, and then install them via CWM/Mobile Odin?
Godofmosquitos said:
Wow. A lot of replies in just a single day. You guys are awesome
Now you say that the KK5 is non-wipe. Are there any GB-roms which are wipe, so to speak? Or do I have to do the flash to GB, enter recovery, wipe cache partition and do wipe/factory reset, then reboot into a now working phone, set up for root with USB and so forth, root and install CWM, copy the custom ROM to my SD-card (gonna go for ParanoidAndroid) as well as Google services if I want those, and then install them via CWM/Mobile Odin?
Click to expand...
Click to collapse
GB LC1 is wipe. But if you want PA (which is an excellent choice) just flash a CM10 kernel in your recovery (if your recovery is safe, like GB for example). Then follow Utacka's instructions for the installation.
But if I want CWM I should do root and install CWM there? And then flash the custom ROM from CWM?
Godofmosquitos said:
But if I want CWM I should do root and install CWM there? And then flash the custom ROM from CWM?
Click to expand...
Click to collapse
The CM10 kernel comes with its own recovery where you can flash from. If you have root issues, just flash CWM-SuperSU-v0.99.zip. In any case don't flash from stock ICS with CMW.zip: if you are on ICS and not rooted flash the relevant Philz kernel (which is safe and will give you root and CWM) then the CM10 kernel.
Edit: what ROM do you have now?
I use the 4.1.2 XXLSA ROM
Btw, anyone knows where I can download the Google Services Framework so I can install it alongside Paranoid Android? I have been led to believe it's not included as per default
Thx for all the replies!!
If you have downloaded the xxlsa rom then it's inside the rom zip file. Path system/app/GoogleServicesFramework
nokiamodeln91 said:
If you have downloaded the xxlsa rom then it's inside the rom zip file. Path system/app/GoogleServicesFramework
Click to expand...
Click to collapse
Hmmm. not that I can see. Even tried unpacking the .tar files. Can't find it :/
Edit: Ah, found it Thx for all the help

Can I restore ICS nandroid over JB rom?

Hi
I want to return my Note to stock. When I first bought it I rooted it and made a nandroid of the stock ICS rom that was on it.
Since then I have installed Alliance Rom on Jellybean. Can I just restore the stock ICS nandroid straight over the JB rom or will this brick my phone? I've read that there's something about ICS stock kernels that can cause bricks so I'm a bit nervous about how to go about it.
I have already downloaded the two files from the unroot thread to remove superuser and binaries, do I just flash these after restoring the ICS nandroid? Also, how do I get back the stock recovery?
Sorry for such basic questions but I'm new to the Note and it's a bit different to flashing things on the One X which I came from.
Thanks x
yes.. you can restore the stock rom nandroid.. but i am not sure as Alliance JB LSZ use TWRP recovery and the backup you made may be using CWM.. so its better to install a CWM kernel on the rom... Like philz and then restore the rom,, for stock recovery you will need to install stock kernel..
but why go into so much trouble ... just install a stock ICS rom using pc odin.. (no wipes after installing stock ICS rom).. make all the wipes while on a safe kernel
nokiamodeln91 said:
yes.. you can restore the stock rom nandroid.. but i am not sure as Alliance JB LSZ use TWRP recovery and the backup you made may be using CWM.. so its better to install a CWM kernel on the rom... Like philz and then restore the rom,, for stock recovery you will need to install stock kernel..
but why go into so much trouble ... just install a stock ICS rom using pc odin.. (no wipes after installing stock ICS rom).. make all the wipes while on a safe kernel
Click to expand...
Click to collapse
Thank you very much for explaining, that's a big help
The Odin way does sound a bit easier, I'll look into it. Thanks for explaining about the ICS wiping problem.
Much appreciated

Categories

Resources