My phone locks up almost daily and I have to remove the battery and then put it back in to get it going again.
This cant be normal...
I have TeamWin loaded onto it and have installed LiquidSmooth using this. I wiped the Cache, Dalvik, System at least three times before installing LiquidSmooth. I have tried installing it a few times with the same result.
Still, the phone locks up and it generally locks up while I am on a call. It generally doesnt lock up while using an app or browsing.
I am getting kind of sick and tired of removing the back cover and pulling the battery daily....
Any thoughts ?? Help !
INFO:
Phone: Samsung Galaxy S3, AT&T, SGH -I747
Android version 4.2.2
LiquidSmooth: liquid_d2att-userdebug 4.2.2 JDQ39 eng.liquid.20130403.222500 test-keys
LiquidSmooth Version Liquid - JB-v2.1-OFFICIAL
Kernel version: [email protected] #167
(I did try installing AOKP as well, and that gives me an error installing, so I couldnt even get that going - maybe these problems are related??)
Shane24 said:
My phone locks up almost daily and I have to remove the battery and then put it back in to get it going again.
This cant be normal...
I have TeamWin loaded onto it and have installed LiquidSmooth using this. I wiped the Cache, Dalvik, System at least three times before installing LiquidSmooth. I have tried installing it a few times with the same result.
Still, the phone locks up and it generally locks up while I am on a call. It generally doesnt lock up while using an app or browsing.
I am getting kind of sick and tired of removing the back cover and pulling the battery daily....
Any thoughts ?? Help !
INFO:
Phone: Samsung Galaxy S3, AT&T, SGH -I747
Android version 4.2.2
LiquidSmooth: liquid_d2att-userdebug 4.2.2 JDQ39 eng.liquid.20130403.222500 test-keys
LiquidSmooth Version Liquid - JB-v2.1-OFFICIAL
Kernel version: [email protected] #167
(I did try installing AOKP as well, and that gives me an error installing, so I couldnt even get that going - maybe these problems are related??)
Click to expand...
Click to collapse
Hey man,
My suggestion is to use Odin to flash the stock image back to stock and see if the problem persists. If it does, I'd take it back to at&t for a new phone (if you've had it less than a year or you have some sort of insurance plan.)
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
---------- Post added at 02:23 AM ---------- Previous post was at 02:18 AM ----------
If flashing back to stock fixes it, its user error. Make sure you're up to date on everything, I.e boot loader, recovery, everything. If that does nothing for you maybe try flashing the new version of CWM and see if it'll flash right that way.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Is it just me or is your lean kernel like years old? Isn't the newest version 7.2?
Same with your rom.. 2.9 is out?
Sent from my SGH-I747 using xda premium
Yes, the kernel could be old. I have never updated it... I hate to admit, but I have no idea what the kernel does actually or how to flash a new one.
I have installed the ROM, but not the kernel obviously....
Any info on what a kernel does? Can I flash it easily with TeamWin ?
I can definitely upgrade the ROM to the latest version of liquidSmooth
Shane24 said:
Yes, the kernel could be old. I have never updated it... I hate to admit, but I have no idea what the kernel does actually or how to flash a new one.
I have installed the ROM, but not the kernel obviously....
Any info on what a kernel does? Can I flash it easily with TeamWin ?
I can definitely upgrade the ROM to the latest version of liquidSmooth
Click to expand...
Click to collapse
Hey man,
If you're going to be flashing custom ROMs you should probably learn what a kernel is. Use the search feature or simply use google. In fact, the xda TV channel just put out a video on kernels this week on YouTube.
Anyways, as I said previously, make sure EVERYTHING is up to date. Including the ROM version. Dont worry about flashing kernels until you have a solid understanding of what they are. I'm almost positive that you are just flashing out of order. Just start from scratch, make sure EVERYTHING is up to date. Good luck.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
yup, I got up to speed on kernels. (Thanks for the suggestions as I didnt know about Kernels, but now I do...)
So, the plan is to
- wipe: dalvic, cache, etc... (3X)
- install the Bionic Sheep 4.2.2 Kernel
- install ROM (I'll try Hyperdrive and DeadlyVenom and LiquidSmooth again)
- install Google Apps...
I have TeamWin installed obviously.
Hopefully this will get my phone back on track...
Shane24 said:
yup, I got up to speed on kernels. (Thanks for the suggestions as I didnt know about Kernels, but now I do...)
So, the plan is to
- wipe: dalvic, cache, etc... (3X)
- install the Bionic Sheep 4.2.2 Kernel
- install ROM (I'll try Hyperdrive and DeadlyVenom and LiquidSmooth again)
- install Google Apps...
I have TeamWin installed obviously.
Hopefully this will get my phone back on track...
Click to expand...
Click to collapse
Hyperdrive and Deadly venom are touchwiz ROMs, u can't flash bionic sheep with them!!! And u don't need to flash gapps with tw ROMs either!!
Also, u need to flash a kernel after u flash the ROM, otherwise it will be overwritten by the stock kernel for whatever particular ROM u are flashing. I would suggest sticking with the stock kernel for a bit and see how it runs!
Shane24 said:
yup, I got up to speed on kernels. (Thanks for the suggestions as I didnt know about Kernels, but now I do...)
So, the plan is to
- wipe: dalvic, cache, etc... (3X)
- install the Bionic Sheep 4.2.2 Kernel
- install ROM (I'll try Hyperdrive and DeadlyVenom and LiquidSmooth again)
- install Google Apps...
I have TeamWin installed obviously.
Hopefully this will get my phone back on track...
Click to expand...
Click to collapse
What the guy above me said about TW roms is correct. Flashing the wrong kernel is not a good idea. Here's what I do on every flash
- wipe system, data, caches, etc.
- flash rom( and gapps if necessary)
- boot up rom and let it settle for 5 min, then boot back into recovery
-flash correct kernel for the rom's version(check kernel number in about device and custom kernels op), then wipe both caches and fix permissions.
-reboot and enjoy:laugh:
DMF1977 said:
Hyperdrive and Deadly venom are touchwiz ROMs, u can't flash bionic sheep with them!!! And u don't need to flash gapps with tw ROMs either!!
Also, u need to flash a kernel after u flash the ROM, otherwise it will be overwritten by the stock kernel for whatever particular ROM u are flashing. I would suggest sticking with the stock kernel for a bit and see how it runs!
Click to expand...
Click to collapse
Which Kernel would I need to use then for Touchwiz ROM's ???
And which kernel for LiquidSmooth and AOKP ??
Shane24 said:
Which Kernel would I need to use then for Touchwiz ROM's ???
And which kernel for LiquidSmooth and AOKP ??
Click to expand...
Click to collapse
Like I said, I would suggest sticking with the packaged kernel that comes with whatever ROM that you are going to flash, run it for a few days, after that if u still feel the need for something more, go with a custom kernel! Ktoonsez makes an excellent kernel, one for tw, and one for aosp, u just have to pick the right one according to which ROM you're running!! Good luck...
DMF1977 said:
Like I said, I would suggest sticking with the packaged kernel that comes with whatever ROM that you are going to flash, run it for a few days, after that if u still feel the need for something more, go with a custom kernel! Ktoonsez makes an excellent kernel, one for tw, and one for aosp, u just have to pick the right one according to which ROM you're running!! Good luck...
Click to expand...
Click to collapse
I did try flashing AOKP with TouchWiz, and it gives me an error that it cant flash.
Is the kernel that Ktoonsez all part of the ROM and just one file ?
Ultimately, I would like to flash AOKP, but my Galaxy S3 wont allow it...
Shane24 said:
I did try flashing AOKP with TouchWiz, and it gives me an error that it cant flash.
Is the kernel that Ktoonsez all part of the ROM and just one file ?
Ultimately, I would like to flash AOKP, but my Galaxy S3 wont allow it...
Click to expand...
Click to collapse
What?
What DMF1977 was saying is just flash the ROM you desire to have on your device and just run the kernel that comes with the ROM. After running the ROM you chose for awhile, if you feel the need to flash a new kernel then and only then flash the correct version of Ktoonsez kernel. And its not surprising that if you tried to flash anything AOKP related with TW you got an error.
Just flash an AOKP ROM and Dont worry about flashing an additional kernel.
Goodluck
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Related
I'm using the stock Gingerbread "Leak" rom version 4.12.651.1 that was leaked recently and I played around with it at first. Took several pictures and videos and enjoyed getting back to having Sense on my phone.
I used Kernel Manager Lite to download and install the Netarchy Toastmod-cfs-havs-more-sbc kernel and at now everytime I open up the camera it shows a white screen and I can't take a picture or video anymore.
Is there a why to uninstall or undo this kernel without having to reflash my Evo? I'd like to go back to just the stock kernel i guess. I even tried to use the Kernal Manager Lite to download and install a different Netarchy Toastmod kernel but it wouldn't install it over a previous kernel and when I clicked on the kernel I already have installed it won't give me an option to uninstall it...
Thanks for any help you guys can give me.
Find the stock kernel for that ROM and flash in recovery after wiping cache and dalvik cache.I will try to find stock kernel for that ROM.
Yeah there's no way to undo once u flash a kernel.....may I make a suggestions for ya foe the future.....Ive been doing this for a while......flash the ROM and make a backup once yur all setup...this way u can tinker with the rom and kernels and themes and what not.......and if those tweaks don't work for ya......u got a backup of a fully stock rom......
Sent from my PC36100 using XDA Premium App
Thanks guys for the awesome advice!
Reverepats, it's funny you said that because that's the first thing that I thought about after this happened and I'm still kicking myself for not backing it up before flashing the kernel LOL It'll be a lesson learned I guess
Ianmb, that would be AWESOME if someone had this. I'll keep looking for this too but if I have to I guess my only recourse would be to wipe it all and reflash all over again... /sigh
There is a post for a working kernel for that ROM on the second page if the ROM is the stock 4.xxx. Stock kernel 15 I think, can't upload file from my phone?
ianmb, thanks for looking but I can't find any stock kernel #15 out there. not even google can help me =/
So it's possible to reflash a kernel over an already installed kernel? If i find the stock kernel how do I go about installing it? Via recovery?
Forgive me if I'm wrong...but if you just reflashed the rom without wiping, I believe it would install the stock kernel that came with the rom
Sent from my nightly EVO
TwhiT said:
ianmb, thanks for looking but I can't find any stock kernel #15 out there. not even google can help me =/
So it's possible to reflash a kernel over an already installed kernel? If i find the stock kernel how do I go about installing it? Via recovery?
Click to expand...
Click to collapse
Yes you can flash a new kernel over an installed kernel...just wipe cache and dalvik prior to flashing
Sent from my nightly EVO
Hi all,
Since installing cwm a week ago i started experimenting with different kernels and mods. However i noticed that my phone is somehow rejecting some mods/kernels. I run stock jb yakju image with cwm 6.1.1.0 and at the moment fugumod kernel 505 stable. I succeeded at running Franco and trinity 1420-535 previously but that's about it. Airkernel, tuna kernel, even the same version of trinity but with lower clock speeds was rejected. I always get a Google splash screen bootloop. Only way to get rid of it is flash another kernel over it or restore a nandroid. I always wipe the cache and the dalvik cache prior to install. Is there a way to make my phone accept that kernels? And is it my phone fault out the kernels. I'm using a gsm international version.
Thanks in advance!
Sent from my Galaxy Nexus using xda app-developers app
dont wipe anything when flashing kernels.. not your cache, nor your dalvik. if it wont pass the splash screen, i suggest that you reflash your rom and the kernel together then try to boot. sometimes if its not booting, taking your battery out for a minute then putting it back in and booting up works. also, sometimes you have to be a little more patient, giving it more time to boot. if you are flashing any kernel after flashing franco kernel, you have to flash your rom with the next kernel(for the first flash), because franco kernel uses its own ramdisk. most other kernels use anykernel which grabs the available ramdisk, you want it to grab your roms ramdisk. thats where franco kernel keeps franco kernel tweaks which would interfere with other kernels.
I indeed started with the franco kernel. So you are basically telling me that next time i should wipe nothing, reflash my Rom, then reflash my kernel hand reboot. But how do i flash a stock Rom? Is the Google image flashable? And do i get to keep all my stuff etc on my device?
Sent from my Galaxy Nexus using xda app-developers app
tobitronics said:
I indeed started with the franco kernel. So you are basically telling me that next time i should wipe nothing, reflash my Rom, then reflash my kernel hand reboot. But how do i flash a stock Rom? Is the Google image flashable? And do i get to keep all my stuff etc on my device?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
there are a few stock plus root roms floating around, you can flash those over stock. yea, im telling you to wipe nothing. wiping cach/dalvik is like buying your child a swing set when preparing to fill your cars gas tank up. they have nothing to do with each other. btw, thats only with frano kernel, all the other kernels you can just flash on top of each otger and not worry about it. none of your stuff will get lost unless you wipe data/factory reset, and theres no need for that.
maybe that explains why trinity gave me battery drain after installing it after franco?
and to respond to OP no phone is built the same. Your phone won't accept EVERY kernel. Its just something you have to accept (from my experience)
For example every android phone i've owned has reacted poorly to undervolting but for those kernel devs who do it don't have a problem with it. U never know how your phone might react
I was on paranoid android, i flashed ak kernel and my Phone started to have sod and reboot without passing for the Google logo.
I dirty flashed pa again to come back to stock kernel, same reboot.
So i made a full wipe and flashed slim bean + ak kernel but the problem remains. Another full wipe and flashed only slim bean w/o a kernel. And again reboot.
I don't know What to do. The only thing is to flash stock image and root again but it's a bit annoying.
Someone has a better idea?
Il_Tene said:
I was on paranoid android, i flashed ak kernel and my Phone started to have sod and reboot without passing for the Google logo.
I dirty flashed pa again to come back to stock kernel, same reboot.
So i made a full wipe and flashed slim bean + ak kernel but the problem remains. Another full wipe and flashed only slim bean w/o a kernel. And again reboot.
I don't know What to do. The only thing is to flash stock image and root again but it's a bit annoying.
Someone has a better idea?
Click to expand...
Click to collapse
Try using AK's kernel revert (back to stock kernel.)
It works for some people and for others, it doesn't though. I also had reboot problems with AK so I don't use it anymore, and also it sucks that I had to revert to stock when it happens. Hope it works for you, goodluck man.
4.2.2 - http://d-h.st/R7y
4.2.1 - http://d-h.st/2w6
From AK's thread
I didn't use that "script" because i thaught it is needed only if you want to go back to stock kernel without reflashing the rom. If I reflash the rom the kernel will be overwritten, isn't it?
However now i'm no more with ak kernel so i don't think ak's kernel revert could do something.
Il_Tene said:
I didn't use that "script" because i thaught it is needed only if you want to go back to stock kernel without reflashing the rom. If I reflash the rom the kernel will be overwritten, isn't it?
However now i'm no more with ak kernel so i don't think ak's kernel revert could do something.
Click to expand...
Click to collapse
Yes. The kernel id's overwritten whenever you flash a rom.
Sent from my Nexus 7 using Tapatalk HD
Hello! I have managed to root my phone, but I got the set up wizard message and the gapps error. After a google search it told me I had the wrong version of gapps. However, when I go to the official gapps page, the download for cm 10.1 only works with 4.2.2 and not 4.1.2. The one for cm 10.0 is for 4.1.2, but on the hercules downloads page, the 10.1 stable release is already out (that's the one I used!). Does this mean I have to run 10.1 without gapps, or downgrade to 10.0 if I want gapps?
Trust me, I have searched for this. Any help would be appreciated.
if you are on 10.1 grab the first one on the page http://goo.im/gapps also double check make sure you have no market installed if you do then you dont need any gapps install everything from the market
Alright
Ok, I'm gonna try that. +1 thanks for you. Man, I'm such a noob. :crying: :crying:
Bro all good we (I) was all there gotta start some where :thumbup:
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Roulette
krazierokz said:
Bro all good we (I) was all there gotta start some where :thumbup:
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
It's circling now...it's been at it for about 5 minutes now...the wait is unbearable!
Circling
It appears to have no end to the blue circling boot screen. I tried clearing cache and factory reset using CWM, no cigar still. Any fixes for this?
The CM version is the 10.1 stable release for hercules.
The gapps version is the 20130301 version.
which link did you flash for the CM what thread point in the right direction where you flashed from ? if you booted up the first flash and gapps were incorrect it shouldnt matter when you update the gapps it wipes the old files just make sure to wipe dalvik/cache and reboot
My Idiocy
I am retarded. I decided to go and unroot the phone and flash a stock rom and try again. I then flashed twrp via odin (which I prefer now) with no problems. But for some reason, no matter how many times I clear everything and try different kernels, the device will just not root. I have tried the superuser zips from the official site, I have tried the superuser from CWM's site, nothing works. Gah. Now what? Am I stuck stock forever?
Babbalabba said:
? Am I stuck stock forever?
Click to expand...
Click to collapse
Just use TWRP to flash whatever (Hercules) ROM you want. Make sure you wipe dalvik, cache, system and data.
Alright, I will try a wipe again, and then flash a custom ROM. If it doesn't root me I will report back with the situation. Thank you for all your help!
Um, just another question before I proceed with wipe and rom...if the ROM is based off of JB 4.2.2, such as Cyanogen mod, will my phone just run 4.2.2 as part of the rom, or will it be incompatible?
EDIT: Never mind...
I love you all forever. It works, and I have gapps running and root access. Thank you so much...I really don't know what to say.
I don't know if someone already posted this, but searched and couldn't find the answer. I get stuck at boot screen all on AOSP 4.2.2 roms that I tried, but with any TW roms are fine (no problem at all). Can anyone help? I want to run AOSP rom. Thanks.
I think you may be using a touch wiz kernel
You can find some aosp kernels in the original development thread
Sent from my SAMSUNG-SGH-I317 using Tapatalk 4 Beta
jinxzn said:
I don't know if someone already posted this, but searched and couldn't find the answer. I get stuck at boot screen all on AOSP 4.2.2 roms that I tried, but with any TW roms are fine (no problem at all). Can anyone help? I want to run AOSP rom. Thanks.
Click to expand...
Click to collapse
which rom did you flash, and what did you flash?
the rom only?
the rom and GAAPS?
The rom and kernel?
you need to provide more details if you want to be helped..
Zachinater said:
I think you may be using a touch wiz kernel
You can find some aosp kernels in the original development thread
Sent from my SAMSUNG-SGH-I317 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I did flashed SOAPKernel along with aosp roms.
wase4711 said:
which rom did you flash, and what did you flash?
the rom only?
the rom and GAAPS?
The rom and kernel?
you need to provide more details if you want to be helped..
Click to expand...
Click to collapse
I flashed BeanStalk, SlimBean, CyanogenMod 10.1 official nightlies, FSC rom, and IllusionRom.
I have CWM Philz_Touch 5.07.1. Every time install a new rom, I wiped Caches + Data / Factory Reset 2x.
I flashed rom only, then flashed rom and GAPPS, those 2 didn't work, I even tried rom w/ SOAPKernel and still didn't work.
ok, you should try switching to TWRP, since most of the time people have zero issues flashing AOSP roms with TWRP.
Also, after all your wipes, flash the rom and GAAPS in the same session, and reboot..
I've done this exact procedure for years, and it works for me 99.98% of the time..
wase4711 said:
ok, you should try switching to TWRP, since most of the time people have zero issues flashing AOSP roms with TWRP.
Also, after all your wipes, flash the rom and GAAPS in the same session, and reboot..
I've done this exact procedure for years, and it works for me 99.98% of the time..
Click to expand...
Click to collapse
Switched to TWRP, and did all the wipes, install rom and GAAPS. Same thing.
Planning to flash stock rom, and redo all the root/recovery procedures all over again. Do you think I should do that?
it couldnt hurt...
some phones are just tempremental; do you have an SD card in your phone?
are you installing from the sd card or internal memory?
try installing from one or the other to see if that helps; sometimes it does...
wase4711 said:
it couldnt hurt...
some phones are just tempremental; do you have an SD card in your phone?
are you installing from the sd card or internal memory?
try installing from one or the other to see if that helps; sometimes it does...
Click to expand...
Click to collapse
I did try both, none work for me.
Thank you so much for your help thou. I'll now just install stock rom and re-root it, see how it goes.
jinxzn said:
I did try both, none work for me.
Thank you so much for your help thou. I'll now just install stock rom and re-root it, see how it goes.
Click to expand...
Click to collapse
good luck, and post back if you get it working properly
flashed stock rom and rooted and installed boot recovery, after all that, it's still not let me install any AOSP roms. Really don't why I can only flash TW roms but not AOSP roms.