When I turn on my phone, the AOKP loading screen appears for about one or two minutes, then the screen shows an android notification saying, that there's 0% battery and immediately, after let's say half a second, the phone switches itself off again. This way it can't be booted and I'm 100% sure, that the battery is above 90% when doing this, I even tried to re-charge it for a couple of hours, but it's still the same. What should I do now? I'm using the kernel included in the AOKP zip.
Ondwak said:
When I turn on my phone, the AOKP loading screen appears for about one or two minutes, then the screen shows an android notification saying, that there's 0% battery and immediately, after let's say half a second, the phone switches itself off again. This way it can't be booted and I'm 100% sure, that the battery is above 90% when doing this, I even tried to re-charge it for a couple of hours, but it's still the same. What should I do now? I'm using the kernel included in the AOKP zip.
Click to expand...
Click to collapse
Try full wipe and flash ROM again. But before reboot, clear data, cache and dalvik cache. If it don't help, flash kernel RECOMENDED IN ROM'S OP, not that from zip.
AND NEVER AGAIN FLASH KERNEL FROM ANY ZIP!
parkourz said:
Try full wipe and flash ROM again. But before reboot, clear data, cache and dalvik cache. If it don't help, flash kernel RECOMENDED IN ROM'S OP, not that from zip.
AND NEVER AGAIN FLASH KERNEL FROM ANY ZIP!
Click to expand...
Click to collapse
The first step didn't help, same result. Could you please recomend me some kernel that would work with AOKP? I've been trying to find one for a couple of hours by now and I'm hopeless... A direct link would really help me.
Ondwak said:
The first step didn't help, same result. Could you please recomend me some kernel that would work with AOKP? I've been trying to find one for a couple of hours by now and I'm hopeless... A direct link would really help me.
Click to expand...
Click to collapse
all kernels are found here for AOSP
if AOKP is android 4.1.2 (im sure it is) DOWNLOAD the KERNEL LABELED CM10 (Latest one[im assuming u can find the latest one by looking at the upload date xD])
http://www.mediafire.com/?lo2ctaplonbdh
Well, thanks alot! It worked with the TK kernel for CM10, although the ROM itself had some minor bugs so I switched back to Sense based ROMs... problem solved!
Related
What Rom is Better in Terms of Battery Life Myn's Rom RLS 3 or 4?
i tried running RLS 4 with Netarchy's 4.2.1 Nohavs and Collin's Tweak but no luck in battery life,it was horrible.
4. it is newer, which sort of spells out better. netarchys is not very good. it only works for a select few. i would ditch battery tweak and go with htc 17 or ziggy made for rls4. both are good.
Does the battery tweak work for those kernels?
Why ditch it? I thought it suppose to increase it. Battery life for me is bad.
Sent From My HTC EVO
just try ditching it. it doesnt work on htc 17 (not sure about ziggy) but just run a week without on one of the kernels i suggested. just make sure you give the kernel enough time to settle, and that you calibrated your battery correctly. i would flash a kernel with a fresh install of myns.
dkdude36 said:
just try ditching it. it doesnt work on htc 17 (not sure about ziggy) but just run a week without on one of the kernels i suggested. just make sure you give the kernel enough time to settle, and that you calibrated your battery correctly. i would flash a kernel with a fresh install of myns.
Click to expand...
Click to collapse
How do I callibrate my battery before I run it? How long would it take to settle in? What do you mean flash a kernel with a fresh install of myns? How would I properly flash a kernel?
Sent From My HTC EVO
you would flash a kernel through recovery. i mean fresh install as in wipe and reinstall myns first. it comes with htc 17 so try that first. google on the calibrating stuff
RL 4 .. but I used ziggy's beta kernel with it.. awesome battery..
tenniech said:
RL 4 .. but I used ziggy's beta kernel with it.. awesome battery..
Click to expand...
Click to collapse
How's the battery life?
Sent From My HTC EVO
dkdude36 said:
you would flash a kernel through recovery. i mean fresh install as in wipe and reinstall myns first. it comes with htc 17 so try that first. google on the calibrating stuff
Click to expand...
Click to collapse
Yeah I know how to flash a kernel but do I wipe everything? Reinstall the same rom over it?wouldn't that brick me or not make me get passed my boot animation. Really? Can you just tell me how to calibrate it please?
Sent From My HTC EVO
you would need to flash the rom, boot up, go through setting up google, then flash kernel. to calibrate, charge to 100%, unplug and replug a few times to make sure its full, then go into recovery and wipe battery stats. then reboot phone and let it sit until battery goes all the way down until phone shuts off. then while still off, charge until light turns green. then unplug/replug to make sure its full, and reboot. takes a while but you will be happy. well worth it.
dkdude36 said:
you would need to flash the rom, boot up, go through setting up google, then flash kernel. to calibrate, charge to 100%, unplug and replug a few times to make sure its full, then go into recovery and wipe battery stats. then reboot phone and let it sit until battery goes all the way down until phone shuts off. then while still off, charge until light turns green. then unplug/replug to make sure its full, and reboot. takes a while but you will be happy. well worth it.
Click to expand...
Click to collapse
But if I flash a new kernel do I just wipe dalvik cache? When do o callibrate the battery? Before flashing a new rom and a new kernel?
Sent From My HTC EVO
after flashing. it helps a lot. i would reccomend doing it every couple of months. when you flash a kernel, wipe cache and dalvik cache.
dkdude36 said:
after flashing. it helps a lot. i would reccomend doing it every couple of months. when you flash a kernel, wipe cache and dalvik cache.
Click to expand...
Click to collapse
Soyour not suppose to do everytime you flash right? Because I e been doing that this whole time..
How do you calibrate it after flashing and flashing what?
Sent From My HTC EVO
I've been trying to flash CM 7.2.0 and every time I do it, it either A) freezes on the kernel or B) freezes on the boot animation. My bootloader is unlocked. Here are the steps that I've tried.
1. Flash R800x_3.0.1.E.0.88_Verizon.ftf
2. Activated phone, wifi, and whatnot. Play around with it for a few minutes.
3. Flashed the kernel that came with FXP CM7.2.0 zeusc.
4. Boot up into recovery. Wipe user data, cache, dalvik cache.
5. Flash CM7.2.0 zeusc zip.
6. Reboot and the boot animation freezes. I've waited up to 30 minutes and no change. Pulled the battery out, turned on, still freezes on boot animation.
I've done the same thing with R800x_4.0.2.E.57_Verizon.ftf and still no luck. Any ideas?
game_guy said:
I've been trying to flash CM 7.2.0 and every time I do it, it either A) freezes on the kernel or B) freezes on the boot animation. My bootloader is unlocked. Here are the steps that I've tried.
1. Flash R800x_3.0.1.E.0.88_Verizon.ftf
2. Activated phone, wifi, and whatnot. Play around with it for a few minutes.
3. Flashed the kernel that came with FXP CM7.2.0 zeusc.
4. Boot up into recovery. Wipe user data, cache, dalvik cache.
5. Flash CM7.2.0 zeusc zip.
6. Reboot and the boot animation freezes. I've waited up to 30 minutes and no change. Pulled the battery out, turned on, still freezes on boot animation.
I've done the same thing with R800x_4.0.2.E.57_Verizon.ftf and still no luck. Any ideas?
Click to expand...
Click to collapse
have you ever flashed a rom and kernel before? also are you till in stock rom?
x1rocket said:
have you ever flashed a rom and kernel before? also are you till in stock rom?
Click to expand...
Click to collapse
Yes I've flashed a ROM before. Following these same steps, I was able to boot CM9. I've also managed to get AokPlay, Paranoid Android and a few other ROMs running on my device. I always flash back to stock before attempting to flash a new ROM.
game_guy said:
Yes I've flashed a ROM before. Following these same steps, I was able to boot CM9. I've also managed to get AokPlay, Paranoid Android and a few other ROMs running on my device. I always flash back to stock before attempting to flash a new ROM.
Click to expand...
Click to collapse
on the thread you have downloaded the file are the users facing the same problems or just you? must be not supported by your model or the compiled file was not a success to let you boot... if you do check, make sure you read all the pages on that thread...
x1rocket said:
on the thread you have downloaded the file are the users facing the same problems or just you? must be not supported by your model or the compiled file was not a success to let you boot... if you do check, make sure you read all the pages on that thread...
Click to expand...
Click to collapse
It's definitely compatible with my device, it even says it is. I read through the thread and it looks like one or two people are having the same issues.
game_guy said:
It's definitely compatible with my device, it even says it is. I read through the thread and it looks like one or two people are having the same issues.
Click to expand...
Click to collapse
wait a couple of days and see if those users have a fix for it... as no one else posted on this thread they wouldn't know the problem the same as I don't know...
at least I tried to help
game_guy said:
I've been trying to flash CM 7.2.0 and every time I do it, it either A) freezes on the kernel or B) freezes on the boot animation. My bootloader is unlocked. Here are the steps that I've tried.
1. Flash R800x_3.0.1.E.0.88_Verizon.ftf
2. Activated phone, wifi, and whatnot. Play around with it for a few minutes.
3. Flashed the kernel that came with FXP CM7.2.0 zeusc.
4. Boot up into recovery. Wipe user data, cache, dalvik cache.
5. Flash CM7.2.0 zeusc zip.
6. Reboot and the boot animation freezes. I've waited up to 30 minutes and no change. Pulled the battery out, turned on, still freezes on boot animation.
I've done the same thing with R800x_4.0.2.E.57_Verizon.ftf and still no luck. Any ideas?
Click to expand...
Click to collapse
If you are still having trouble flashing CM7, I would suggest downloading from zeusc section of http://get.cm
Or, you can try one of the many CDMA optimized ICS/JB ROMs.
You may have to wipe everything a few times. Of course you can always use my modified cm7 which has autorotation unlike any other cm7 for zeusc lol
Leraeniesh said:
If you are still having trouble flashing CM7, I would suggest downloading from zeusc section of get.cm
Or, you can try one of the many CDMA optimized ICS/JB ROMs.
Click to expand...
Click to collapse
I might switch back to CM9 or Paranoid. I've tried the JB ports. One has working data but no sound, and the other CDMA has everything working except I couldn't get data to work.Thanks for that URL, which one would you recommend? RC1, 2, 3 or stable?
agraceful said:
You may have to wipe everything a few times. Of course you can always use my modified cm7 which has autorotation unlike any other cm7 for zeusc lol
Click to expand...
Click to collapse
If the get.cm doesn't work either, I'll go ahead and try the one in your signature. If all else fails, I'll probably go back to CM9 or Paranoid.
Thanks for all of the help you guys, this is a pretty nice community. :3
Sorry to double post, but I tried the ones from get.cm and the modified one from agraceful, but both froze on the boot animation then crashed and froze on the kernel. I think I'm just gonna give up on this particular ROM.
Check what kind of kernel you using.
I had simillar problem whed used kernel from XDA downloaded file. When used from file downloaded from CM project site it runs with no problems.
I have no idea why that happen, maybe on XDA forum is different modificated version for 800x or 800i etc. and not working with all phones.
So I wanted to flash the FNV AoSP ROM on my Galaxy Nexus GSM. First off al I flashed the 4.2 takyu version and rooted it with SuperSU. After that I flashed the recovery with Clockwork 6.0.1.5 after that I did the following things:
- Wipe data/factory reset
- Mounts and storage > Format /system
- Wipe cache
- Wipe dalvik
- Flashed ROM fnv_20121119_003_maguro.zip
- Flash 4.2 gapps
Am I doing something wrong?
When you say, won't work what do you mean?
Does the recovery not flash the file? If so, what error does it say?
Does it not boot after what seems to be a successful flash in recovery? Do you see the bootanimation?
cupfulloflol said:
When you say, won't work what do you mean?
Does the recovery not flash the file? If so, what error does it say?
Does it not boot after what seems to be a successful flash in recovery? Do you see the bootanimation?
Click to expand...
Click to collapse
It flashs the files and all but it gets into a bootloop. I see the costum bootanimation of the ROM, but it keeps playing and it won't start up. After some time the screen goes black, but it's not off, because if I hold down power it won't turn on so I have to pull battery.
CheesieOnion said:
It flashs the files and all but it gets into a bootloop. I see the costum bootanimation of the ROM, but it keeps playing and it won't start up. After some time the screen goes black, but it's not off, because if I hold down power it won't turn on so I have to pull battery.
Click to expand...
Click to collapse
Your ROM name seems to show that it is a recent build. A quick search around, the last official FNV ROM I see was uploaded in September. The Gerrit, Github, Twitter, and threads here and on another site seem to have been untouched for quite some time.
Of course I am a little out of the loop, so perhaps I am missing something. As devs often post things in IRC, or in other non-official channels. Did you get this ROM from a trusted spot?
That said, it could be a ROM issue perhaps.
CheesieOnion said:
So I wanted to flash the FNV AoSP ROM on my Galaxy Nexus GSM. First off al I flashed the 4.2 takyu version and rooted it with SuperSU. After that I flashed the recovery with Clockwork 6.0.1.5 after that I did the following things:
- Wipe data/factory reset
- Mounts and storage > Format /system
- Wipe cache
- Wipe dalvik
- Flashed ROM fnv_20121119_003_maguro.zip
- Flash 4.2 gapps
Am I doing something wrong?
Click to expand...
Click to collapse
it probably doesnt need the gapps. try reflashing, but without the gapps. don't wipe anything.
cupfulloflol said:
Your ROM name seems to show that it is a recent build. A quick search around, the last official FNV ROM I see was uploaded in September. The Gerrit, Github, Twitter, and threads here and on another site seem to have been untouched for quite some time.
Of course I am a little out of the loop, so perhaps I am missing something. As devs often post things in IRC, or in other non-official channels. Did you get this ROM from a trusted spot?
That said, it could be a ROM issue perhaps.
Click to expand...
Click to collapse
I got the rom from the topic here on XDA. It is the build from 19 november.
simms22 said:
it probably doesnt need the gapps. try reflashing, but without the gapps. don't wipe anything.
Click to expand...
Click to collapse
In the instuctions in the ROM-topic it says it needs them and I also need them to use.
CheesieOnion said:
I got the rom from the topic here on XDA. It is the build from 19 november.
In the instuctions in the ROM-topic it says it needs them and I also need them to use.
Click to expand...
Click to collapse
install the gapps from the play store. you can flash without them, besides the ones that you cant get from the play store are included. you can try it, or just stay in your bootloop, its your call.
CheesieOnion said:
I got the rom from the topic here on XDA. It is the build from 19 november.
Click to expand...
Click to collapse
Ah, my bad I didn't realize it was picked up by someone else, I see that now (which I thank you for the heads up that it is back in production). I was just making sure you weren't flashing something that wasn't ready for public use, and that it was a real ROM.
Being new to Android I succeeded in rooting, installing TWRP to my Tmobile SII..
Then I went ahead and backed up my current stock ROM..
Then went and downloaded CM10 from their website since it's stable.
I erased the old ROM and installed CM10 as the guide suggests.
After booting, however, I had a problem. The phone was very laggy and trebuchet was constantly crashing.. I then decided that this ROM must not be stable and looked for more stable ROMS..
GalaxySbean_V13.5
MIUI.us_hercules_v4.1_2.12.28_Eng_Deo_ZipA_Signed_0xD34D
rootbox_hercules_unofficial_Feb-20-13
.. and couple more.. All running very slowly.. and crashing constantly..
What am I missing?
Is it a problem that I didn't format the internal memory?
If it makes a difference.. TWRP is version 2.4.1.0
Thank you!
I am hoping I can find something faster.. I'm sick of the stock Samsung.. :crying:
What was your flashing method or steps you took to flash? Also, update to the latest TWRP 2.4.3.0 and get the latest version of the ROM you want to flash. Also, CM10 is not as smooth as 10.1 so you might want to give the latest nightly a go.
EDIT:
A good setup would be:
-CM10.1 latest nightly
-Cerux Kernel ASDK (They both are good)
-Latest gapps (3-1-13 I think)
-Crossbreeder mod
batezippi said:
Being new to Android I succeeded in rooting, installing TWRP to my Tmobile SII..
Then I went ahead and backed up my current stock ROM..
Then went and downloaded CM10 from their website since it's stable.
I erased the old ROM and installed CM10 as the guide suggests.
After booting, however, I had a problem. The phone was very laggy and trebuchet was constantly crashing.. I then decided that this ROM must not be stable and looked for more stable ROMS..
GalaxySbean_V13.5
MIUI.us_hercules_v4.1_2.12.28_Eng_Deo_ZipA_Signed_0xD34D
rootbox_hercules_unofficial_Feb-20-13
.. and couple more.. All running very slowly.. and crashing constantly..
What am I missing?
Is it a problem that I didn't format the internal memory?
If it makes a difference.. TWRP is version 2.4.1.0
Thank you!
I am hoping I can find something faster.. I'm sick of the stock Samsung.. :crying:
Click to expand...
Click to collapse
Basically wipe factory defaults and go into mounts and format system. Flash the rom of your choice. I use a custom kernel which supports overclocking and custom governors which may help with the problem. Also you should run fix_permissions to fix the pesky FC's. I run Liquid Smooth with All Star Kernel and it is very fast and smooth. Stay away from anything 4.2 as it isn't stable yet.
batezippi said:
...After booting, however, I had a problem. The phone was very laggy and trebuchet was constantly crashing.. I then decided that this ROM must not be stable and looked for more stable ROMS...
Click to expand...
Click to collapse
I'm not an expert, but I noticed that every ROM post suggests leaving the phone alone for 10 minutes or so after first boot. Did you give CM time to settle after the flash? The ROMs all seem to need time to settle according to the forum posts. I'm running ptmr3's Jedi CM Build 2, which is android 4.2.2. It seems quite stable to me at the moment, but it also seems better after having used it for a few days and rebooted a couple times.
treefrog321 said:
I'm not an expert, but I noticed that every ROM post suggests leaving the phone alone for 10 minutes or so after first boot. Did you give CM time to settle after the flash? The ROMs all seem to need time to settle according to the forum posts. I'm running ptmr3's Jedi CM Build 2, which is android 4.2.2. It seems quite stable to me at the moment, but it also seems better after having used it for a few days and rebooted a couple times.
Click to expand...
Click to collapse
Hmm.. To be hones.. I didn't!
I am going to update TWRP and then I am going to go for this one
http://forum.xda-developers.com/showthread.php?t=1885619
EDIT*
Did that:
TEAMWIN Recovery (TWRP) 2.3.3.0 or later
Wipe
Cache
Dalvik cache
Factory Reset
System
Flash Rom
Reboot
Wait a few minutes
Reboot
Done with flash procedure
Phone is still laggy and very unresponsive.. Unusable! What am I doing wrong?
I'm very new to ROMs and phone tweaking in general, having only flashed less than a dozen ROMs and various tweaks in the last month, but I've never encountered any issues.
My steps:
I use CWM
Nandroid backup
Wipe data
Wipe cache
Darkside Super Wipe
Flash ROM
Flash GAPPS
Wipe dalvik
Fix permissions
Reboot
Wait at least 10 minutes, never less(if you only waited literally a few minutes that might be an issue?)
Reboot, set up Google, etc.
Done.
Never encountered any issues in my young flashing life.
Try this rom
Wanna good fast stable rom? Then try All Star v7....
You might wanna try wiping cache/dalvik factory reset and system a couple of times before flashing. Sometimes that helps
I have downloaded the G2 V3 update.zip to my phone and have tried installing the zip via CWM. I followed instructions stating factory default first, then flash the update.zip, install the SU add-on 1, then factory default. When I reboot my phone I get the LG boot screen, afterwards my indicator lights both flash on, my phone vibrates and the backlight stays on but I get a blank screen. I left it like this for 20 minutes but it never continues. I have tried rebooting but it does the same thing. I have loaded my previous CM 10.2 Rom since. Tried repeating this process, get same results. Adding to this, when I load the add-on it does say there was a problem with Loki at the end.
Please help.
Are you coming from stock or were you on CM?
I always return to stock before changing roms,, I've heard of people having trouble going from CM to V3....
_________________
Beavers & Ducks!
Always wipe system, cache and dalvik-cache before flashing. I'd also suggest wiping the internal sd card as well. Always gives me the best results. I've jumped from ROM to ROM this way with no problems. :3
Sent from my LG-E988 using XDA Premium 4 mobile app
That has to be what it is, I am going from CM10.2 to this mod. I am going to try to go to stock and then message again my results. Thank you for replying to my message.
tobias87 said:
That has to be what it is, I am going from CM10.2 to this mod. I am going to try to go to stock and then message again my results. Thank you for replying to my message.
Click to expand...
Click to collapse
Yup, that is the issue. Those ROMs do not have stock kernel bundled and hence they do not boot when you come from CM or Carbon or Vanir to V3.
You have to go back to stock and then flash that.
Or there might be another way which might work and will spare you hassles of going back to stock and rerooting. Give it a go.
1. Download this kernel : http://forum.xda-developers.com/showthread.php?t=2363330
This kernel is for stock based ROMs.
2. Install V3 by following the procedure. After second factory reset, before rebooting, flash this kernel. And then reboot.
See if that is successful. It should be. (it will still take 4-5 minutes for first boot )
If not , you can always go back to CM and then go through whole going back to stock thing.
Got The thing to work by flashing the CWM recovery files in three parts. Then updated to V4 and SU. The only thing I can't seem to get working is the wireless reefer devices can connect but the receive no data.
Funkym0nkey said:
Yup, that is the issue. Those ROMs do not have stock kernel bundled and hence they do not boot when you come from CM or Carbon or Vanir to V3.
You have to go back to stock and then flash that.
Or there might be another way which might work and will spare you hassles of going back to stock and rerooting. Give it a go.
1. Download this kernel : http://forum.xda-developers.com/showthread.php?t=2363330
This kernel is for stock based ROMs.
2. Install V3 by following the procedure. After second factory reset, before rebooting, flash this kernel. And then reboot.
See if that is successful. It should be. (it will still take 4-5 minutes for first boot )
If not , you can always go back to CM and then go through whole going back to stock thing.
Click to expand...
Click to collapse
Swype decided to fill in an odd word for what I meant sorry. I meant wireless tether.
tobias87 said:
Got The thing to work by flashing the CWM recovery files in three parts. Then updated to V4 and SU. The only thing I can't seem to get working is the wireless reefer devices can connect but the receive no data.
Click to expand...
Click to collapse