hello my friend!!
i have a problem with my OB!!
when i use with zeus 7.06 and diana 2.7 kernel everything works.
but i want to upgrade to ics or JB and when i upgarde to V30B/nesmiss X/cm 10/cm 10.1 it's work but when i connected to wall charger
or to usb is write to me on the lockscreen "low tempratur!! unable to chrge the phone!"
and i use withe zeusgrafitity.. kernel.
what i can to do? just with zeus the charger works o.k
please help me!!
i think that the problem in zeusteawker but i not sure.
thank you very much to all answers.
Needed more info, but it seems you're using a GB kernel on a ICS/JB Rom, as usual try 3 wipes before flashing
what is mean "try 3 wipes before flash" ?
i make one full wipe and than i install a new ics rom and then kernel of ics ( i install [ZeroGravityKernel v 1.0)..
ErnuB said:
Needed more info, but it seems you're using a GB kernel on a ICS/JB Rom, as usual try 3 wipes before flashing
Click to expand...
Click to collapse
You cant use a GB kernel on ICS Well I dont really know, what the problem is, but please try to wipe data, cache and in advanced wipe dalwik cache. Then flash the ROM and try again. Maybe use my ROM, since it is stock with CWM support. zerogravity has got OC and UV and those two features may cause issues.
But I've never seen a battery getting to cool Are you sure it says LOW? And not high?
Related
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??
Hi,
I as of yet, am not going close to any ICS build till the issue gets solved by someone.
so I am experimenting with different gb roms. i was using checkrom v6 but didnt like it, so followed steps to install darkyrom/alliancerom extreme edition. i followed the steps as I was told to install allianceota and flash the rom through there. it didnt work. so instead using cmw i flashed through recovery, it did flash but there no root.
so now, i reflashed a stock la6 rooted rom from here; http://forum.xda-developers.com/showthread.php?t=1535025
this went smoothly with no problems, so i installed allianceota as normal, this time when i try to flash the following messages come up:
Installing Multi-CSC
Can't access to '/system/CSC/KOR/system/'
Successfully applied multi CSC"
and then it gives me the option to reboot, wipe cache and a few other options, not full recovery mode.
shall i just reflash the rom through recovery, or am I doing something wrong? and does the slight error above mean I have a problem with my note?
cheers in advance.
Let me just say that almost every ICS ROM out there now has disabled the MMC_CAP_ERASE code in the kernel that activates the eMMc bug and bricks your phone. If you want stock ICS, you can use SpeedMod or Franco kernels. If you want AOKP, there is that now. If you want CM9, there's a bunch of variations plus the official CM9 nightly. If you read through the OP and stickies, you will be okay.
Are you on stock recovery still? It sounds like it from the error you are getting. Try flashing CWM recovery and installing the GB rom with that. Follow Drketan's thread in Android Development.
hmmm, so would you advise me to use ics? is it much better? i dont want to use cm9 builds as i need the spen apps and so on. i have looked into kingdroid or alba.
I'll have to think hard about this. i may give it a shot soon though..
oh and btw, I fixed the problem, yep it was to do with cwm it wasn't installed with the stock rooted rom. as for allianceota, it still didnt flash the rom, i had to flash the rom through cwm manually.
cheers anyhow.
salespalace said:
hmmm, so would you advise me to use ics? is it much better? i dont want to use cm9 builds as i need the spen apps and so on. i have looked into kingdroid or alba.
I'll have to think hard about this. i may give it a shot soon though..
oh and btw, I fixed the problem, yep it was to do with cwm it wasn't installed with the stock rooted rom. as for allianceota, it still didnt flash the rom, i had to flash the rom through cwm manually.
cheers anyhow.
Click to expand...
Click to collapse
I love ICS a lot more than GB. If you want to use stock ICS, I would just use Franco or Speedmod kernels with it and be safe. Read both of their forums and decide what you want to do.
I had the same problem with rom deodex i had flash with odin 1.85 firmware gingerbread here ; http://www.hotfile.com/dl/152168378/f76281c/N7000XXLC1_N7000OXXLB3_ATO.zip.html... then i made wipe cache and cache dalvick .
I've just flashed AlBa repack latest one on xxlq2, I did it by following the steps,
I thought i had broken my phone, because when the flashing finished and i was rebooting, at the beginning when it welcome to galaxy note n7000 and then goes to the bootup video, it restarted that several times, then after like a few minutes it loaded the homescreen and startup.
salespalace said:
I've just flashed AlBa repack latest one on xxlq2, I did it by following the steps,
I thought i had broken my phone, because when the flashing finished and i was rebooting, at the beginning when it welcome to galaxy note n7000 and then goes to the bootup video, it restarted that several times, then after like a few minutes it loaded the homescreen and startup.
Click to expand...
Click to collapse
-Flash a stock GB rom with pc odin
-Root it
-Go to cwm and wipe all (factory reset,cache and dalvik and then Install the ics rom that you like
-Reboot system and now it should work
Sent from my GT-N7000 using Tapatalk 2
Hi guys, could really do with some help here.
I was on Rocket ROM ICS v3 and tried to update to v5. Wiped cache and dalvik and it installed in seconds which I thought was suspicious. It then restarted and got stuck on the galaxy note splash screen. This has happened when upgrading from 1 to 2 and then 2 to 3. So pretty sick of restoring everything!
I've just done a full reset and tried to install 5, it freezes during the installation and same with v3.
Please help im stranded without my phone
I hope that you didn't full wipe on cf-kernel....
I have no idea.. is that what v3 kernel is?
andypa1 said:
I have no idea.. is that what v3 kernel is?
Click to expand...
Click to collapse
v3 is not a kernel. It is Rom.
Did you make a factory reset in cwm while being on RocketRom?
yes I know mate, but v3 says that it has the speedykernel...
But yes I have done a full reset when the upgrade to v5 didn't work
any idea how to fix it?
andypa1 said:
yes I know mate, but v3 says that it has the speedykernel...
Click to expand...
Click to collapse
I thought you were referring to RR v3
For me you should flash abbys - do a fullwipe - reflash the rom
NEVER DO A FULL WIPE ON ANY ICS UNSAFE KERNELS ! YOU MAY END UP BRICKING YOUR NOTE!
you have been warned
thanks will search for the abyss kernel now and flash it and then try to flash the rom again... fingers crossed but I can still get to recovery so I presume everythings not lost?
This whole thing about not being able to full wipe on ICS, isn't that going to be a problem in the future if you decide to change rom?
andypa1 said:
This whole thing about not being able to full wipe on ICS, isn't that going to be a problem in the future if you decide to change rom?
Click to expand...
Click to collapse
that's not a problem. You can always flash abyss first and wipe. And CM9 kernels are safe to wipe.
REMEMBER - before you flash, follow the dev's instructions on how to do that!
And if you can go into download mode, you are good to go
I had the same problem. What I did was flash a rootable GB (ICS is possible), I rooted this rom. And I flashed as described in the Installation instructions
For me worked fine.
thanks, that explains it! managed to get it back to ICSv3
still a mystery why it's proving so difficult to upgrade without having to full wipe
going to try ICS v6 now without a full wipe, if it fails will try the old abyss trick
Hi all,
I want to expose my problem.. never happened something like that.
I installed on it HP 2x kernel and temasek's ROM.. telephone seemed to be stable and i used this config for about 3 week but yestarday i was at work as normally.. my battery phone was about full (93%).. i went to smoke a cigarette e left telephone on the table.. after 15 min i comed and looked at it but it was VERY hot and black screen.. so i removed battery as fast as i could.. then i let the phone cool and tried to power on.. everything seemed ok but i noticed that date was 2007/1/1.. tried to change date but seems not working. then i noticed that on the battery it was i kind of strange liquid.. i tried to install again rom with no kernel.. and seemed working.. but lots of time apps interrupt and sometimes system was low..then today installed CM9 HD NOVA ROM.. seems more faster but sometimes seems to be slow.. what should i do? how about Garancy? what happened to my phone? Thanks for help and hope someone read this!
EDIT:
Kernel was EtaNa not HP2x!
How can you install HP SuperSonic kernel on Temasek's Rom? Spica's kernels are only for STOCK rom (http://forum.xda-developers.com/showthread.php?t=1295486) or ICS (http://forum.xda-developers.com/showthread.php?t=1560773). It's NOT compatible with CM7 custom Rom. Just be SURE to flash the correct kernel for the custom rom sir.
I just suggest you to:
1. Make a NANDROID BACKUP first (if anything goes wrong).
2. Make a FULL wipe of your phone:
2.1 Wipe Data/Factory Reset and Wipe Cache Partition.
2.2 In Advanced Menu, Wipe Dalvik Cache and Wipe Battery Stat.
2.3 In Mount/Storage Menu, Format System, Format Data and Format Cache.
2.4 DO NOT FORMAT /SDCARD or /EMMC because you will loose all your stuff on your sdcard.
3. Flash a new custom Rom but not kernel yet.
4. Reboot your phone.
5. When that's done, reboot your phone into Recovery
6. Flash the APPROPRIATED kernel.
7. Reboot your phone.
8. Finally, when your phone turn on, reboot again to be sure all tweaks take effect.
Hope that help. Give us feedback.
Thanks for answer.. i typed wrong.. the kernerl i installed is Etana kernerl loc-ds.. shall i do what you told me even if is the correct kernel? what do you think about the hot phone? and liquid that i saw on battery?
IDan1109 said:
Thanks for answer.. i typed wrong.. the kernerl i installed is Etana kernerl loc-ds.. shall i do what you told me even if is the correct kernel? what do you think about the hot phone? and liquid that i saw on battery?
Click to expand...
Click to collapse
Yes, just do what I wrote before. For your battery......hummmm...I think your battery is licking.
Does your battery re-charge when you plug in your cellphone?
Are you under warranty?
If yes, hurry up and try to make a trade with your carrier. But BE SURE that you're on STOCK UNROOTED FIRMWARE
because if they saw that you're under overclockable custom rom...your warranty is void. :silly:
If not, just check in Optimus 2x Accessories threads (http://forum.xda-developers.com/forumdisplay.php?f=1001)
and try to search for an aftermarket battery even on eBay or Amazon or whatever :good: ...because your battery will not keep her charge for long time.
Hope that help.
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.....??