Database Develop

Unable to change ROM

Hi,
I am using the stock gingerbread rom from CSL running the utterchaos kernel by doomlord & Napster.
I tried changing rom's to CM7 found at http://forum.xda-developers.com/showthread.php?t=1333503
I did everything as described, wiped data/factory reset and then flashed the rom.
It said success but when I rebooted phone it shows
"booting UtterChaos Kernel by Doomlord & Napster" screen and nothing happens further. The screen goes dark and again the same boot screen shows.
I guess its going into bootloop.
How do I fix this?????
Thanks

U should root ur device...flash clockwork mod and then flash rom
Sent from my GT-S5570 using xda premium

How do you think I flashed the rom in the first place?
Device rooted, latest version of CWM.

innocuous76 said:
Hi,
I am using the stock gingerbread rom from CSL running the utterchaos kernel by doomlord & Napster.
I tried changing rom's to CM7 found at http://forum.xda-developers.com/showthread.php?t=1333503
I did everything as described, wiped data/factory reset and then flashed the rom.
It said success but when I rebooted phone it shows
"booting UtterChaos Kernel by Doomlord & Napster" screen and nothing happens further. The screen goes dark and again the same boot screen shows.
I guess its going into bootloop.
How do I fix this?????
Thanks
Click to expand...
Click to collapse
hi
use SUTL and flash stock rom then get the CWM and install the CM7 via CWM it should work

this CM7 is on .35 based kernel and utterchaos kernel is .32 , that is creating the problem .....
So, if you want to try this rom, first install TJ's RC3 rom than install this rom .....
if u dontt want to try this now (as u have bricked ur phone once ) ....
just install stock GB rom via SUT ....

innocuous76 said:
Hi,
I am using the stock gingerbread rom from CSL running the utterchaos kernel by doomlord & Napster.
I tried changing rom's to CM7 found at http://forum.xda-developers.com/showthread.php?t=1333503
I did everything as described, wiped data/factory reset and then flashed the rom.
It said success but when I rebooted phone it shows
"booting UtterChaos Kernel by Doomlord & Napster" screen and nothing happens further. The screen goes dark and again the same boot screen shows.
I guess its going into bootloop.
How do I fix this?????
Thanks
Click to expand...
Click to collapse
dude since edowar's latest cm7 is Based on a new kernel 2.6.35.7, u have to flash stock sharp rom through SUT. then use tj's cwm recovery for latest kernal and flash cm7 27-3-2012
else you can flash UPDATE ROM 31-12 directly it is also good rom

So basically I have to flash 2 roms!
Can't I just flash a .35 kernel instead of the .32 one and then flash the CM7 rom?

innocuous76 said:
So basically I have to flash 2 roms!
Can't I just flash a .35 kernel instead of the .32 one and then flash the CM7 rom?
Click to expand...
Click to collapse
No u cant. But if you're from stock GB you could flash older CM7 based on the. 32 kernel instead
Sent from my CSL-MI410 using XDA

[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] Helppppp!!!

I sincerely hope some of you can help me out with this! So I have the GT N7000, it came on GB, after the release of stock ICS I upgraded it, and then after the emmc issues, I went back to GB, rooted that, installed CM9 and after that installed StunnerICS(old version). Now I realised that I am still on a bad kernel, so I installed the CM9 kernel(after reading that it was safe) yesterday using PC Odin, and now after that, my wifi isnt working, my camera isnt working, my phone always memory full(well, this has been there since before, even though I cant figure out where all the space has gone), and still if I use the chainfire gotbrickbug app, it still says dangerous chip.
I am scared to format my phone so that I dont hard brick it, I cant install any another ROM for the very same fear of bricking it during the wipe and factory reset. I just want to go back to a decent ROM, preferably CM 9/10 or even a stock ROM and live peacefully with it ever after!
Hope you can help me sort this out!

boot into download mode and install a stock prerooted GB rom first..
http://forum.xda-developers.com/showthread.php?t=1424997

nokiamodeln91 said:
boot into download mode and install a stock prerooted GB rom first..
http://forum.xda-developers.com/showthread.php?t=1424997
Click to expand...
Click to collapse
And after that, install CM 10? I am assuming there wont be any issues with this method?

GB is a safe rom .. so there is no brick bug .. you will have CWM when you flash a prerooted GB rom.. so you can flash cm.
The emmc check app will always say you have a insane chip thats because you have.. only thing you can do is to be on a safe kernel always.

And also, am I safe to flash a ROM directly from CWMR or not? Considering I had flashed a CM kernel yesterday.
Kernel Version:
3.0.30-CM-ga62d2f7
[email protected] #1
SMP PREEMPT Thu May 17 blah blah

prerooted GB will have CWM so.. you can directly flash the rom from there.

nokiamodeln91 said:
prerooted GB will have CWM so.. you can directly flash the rom from there.
Click to expand...
Click to collapse
Thank you! I understand that this is a safe way, but it seems long. Will it be okay to flash the CM 10 nightly right now given the kernel I am on?

if you have access to recovery then go ahead.. but i mentioned going back to GB because of the storage issue you reported. but firs try flashing the CM rom first

thank you for your help! i flashed the cm10 nightly, all issues have resolved!!

[Q] Help (Rooting/Brick issue)

I will try to be as detailed as possible. I have been long time user here, but this is the first time I'm posting. I usually read the instructions and posts and that usually suffices my needs. I was on a rooted galaxy note running chasmodo's assylum rom for quite some time now. For Flashing a new rom, I used to go to recovery mode, flash abbysnote kernel (v 3.9) and install a new rom. A few days ago i tried to flash Ezaechiel XXLT6 KM edition - V2.1. I guess I should have checked md5 of the downloaded rom coz after flashing it, my phone refused to boot up. It always took me to the recovery mode screen where i tried to install abyssnote kernel and reinstall assylum. but it didn't work. So I went to dr. ketan's post and tried to flash a pre rooted rom (SGN_XX_OXA_KJ1_FACTORYFS.zip) using pc odin. Now my phone works fine but i'm on ginger bread. I tried to flash new roms using recovery mode (abbyssnote kernel method) but no new rom can be installed. Everytime I try to install a new rom i face boot loop or get stuck on the setup screen. So I follow the PC odin method to flash the same pre rooted rom (SGN_XX_OXA_KJ1_FACTORYFS.zip) to get my phone working again. I would like to go back to assylumrom because i got used to aosp jellybean so much now. Anybody who has faced a similar problem in the past, please help

Use one of PhilZ kernels and then in his recovery prepare your device for a clean install (there is an option that does more than only "factory reset". With the old ones you didn't clean /preload.
Then follow the instructions to install your preferred Rom.

Thanks
ThaiDai said:
Use one of PhilZ kernels and then in his recovery prepare your device for a clean install (there is an option that does more than only "factory reset". With the old ones you didn't clean /preload.
Then follow the instructions to install your preferred Rom.
Click to expand...
Click to collapse
Thanks for the quick reply thaidai. I will try the method and get back to you I used to do a clean wipe every time.

Mate first upgrade your stock ROM to ICS or JB. The ROMs like Asylum aren't supposed to be installed in GB, so first upgrade, then root and do a full wipe (data,cache,preload,dalvik) and get back to flash the ROM. No need to flash the Abyssnote every time, why do you do that?

Varad297 said:
Mate first upgrade your stock ROM to ICS or JB. The ROMs like Asylum aren't supposed to be installed in GB, so first upgrade, then root and do a full wipe (data,cache,preload,dalvik) and get back to flash the ROM. No need to flash the Abyssnote every time, why do you do that?
Click to expand...
Click to collapse
I tried installing Cassies Xtraliterom XLC1 after the PC odin method. Got boot loop. What I'm basically saying is, after trying the PC odin method to rescue the device, I can't seem to install any other rom on it using the recovery mode route. Not even other GB roms. What am I to do??

Varad297 said:
Mate first upgrade your stock ROM to ICS or JB. The ROMs like Asylum aren't supposed to be installed in GB, so first upgrade, then root and do a full wipe (data,cache,preload,dalvik) and get back to flash the ROM. No need to flash the Abyssnote every time, why do you do that?
Click to expand...
Click to collapse
I started using abyssnote kernel to install new roms after the "brick scare" of last year after which a lot of developers started recommending the method. I used to change between GB, ICS and JB roms easily using the abyssnote kernel. Don't know why it's not working anymore.

How can i turn back from kitkat

Hello,
I have installed Mackay rom 4.2.3 but i wana turn back too gamerz rom... How can i do this?
Today i have tryed with the classic wipe solution but i cant instal gaerzrom..Failed...
Why?
Thank u

bartalisattila said:
Hello,
I have installed Mackay rom 4.2.3 but i wana turn back too gamerz rom... How can i do this?
Today i have tryed with the classic wipe solution but i cant instal gaerzrom..Failed...
Why?
Thank u
Click to expand...
Click to collapse
The only way I was able to go back from a KK Rom was to go to back to GB 2.3.6 first and then up from there.
I dont know if you did the same as me when installing a KK but I loaded up CM10.2 (or CM11) fist so as to upgrade the CWM and increase the partition as they recommend. I guess this has to be undone, and the best way is with ODIN and 2.3.6. I re-rooted and everything afterwards. Hope it works for you its only another 10 mins.

Actually there is a quicker way because I had to go back to JB from KK and doing this worked.
Simply flash a JB kernel first then your corresponding Rom and gapps.
List of compatible kernels in the second post of this
http://forum.xda-developers.com/showthread.php?t=2557608

I usually go back to a stock rom before trying something new - and most of the time I run into less problems. If you want to stay rooted and continue using custom roms, you might go with this:
http://forum.xda-developers.com/showthread.php?t=1583026

i agree i always flash back to stock then flast dbdata file to sort out errors with partitions. then flash any other rom i require afterwards:laugh: