[Edit: this was an issue with cm11m8 problem resolved in update to m9]
When I try to power off phone and recharge the battery sign will pop up on screen and then phone will attempt to boot but freezes on the first screen. I can get out of this by going into download mode then exiting. Without going into download mode no mater how many times you try to restart it will at that point freeze at that screen. Screen will just sit there lit.
I am running cm11 the most recent stable on the att i747. Before install i wiped cache and davik. then wiped again after install. I was able to charge the phone while off on cm10. the only thing that has changed since then is that i updated from the jb firmware to the latest kitkat firmware the UFNE i think it is. after the baseband update i continued to run cm10 for about a week but cant recall if I tried to charge while powered off.
Does anyone have a fix for this or can lead me in the right direction?
if so thanks in advance. I did some searching here and all over the web but cant find anything phone specific or able to help.
oh also annother note.. i am running a different battery.. its the 7000 mah nolemon but i remember charging this battery while phone off when i got it so I don't think it is the battery or the phone. I could be wrong though. maybe its something different with cm11 or possibly the firmware
No one have this issue? Or no a fix?
Try a different kernel.
I just installed the snapshot. I'm newb with kernel. Which kernel?
there's many choices in the att s3 original development thread to choose from.
just make sure its the right one for your android version.
err on the side of kindness
I can't tell you about individual kernels. I don't use cm/aosp roms.
I do know the same thing happens with the sprint TW kernel though.
I'm not completely new to this. Done about 3 devices now I guess.. This s3 has been a pain compared to my nook HD.
Cyanogen is the only ROM I have ever used. And clockworkmod is the only recovery I have tried.
It seems to me from what I have seen on here most people are using the twrp ROMs... Where as on the other devices it seemed cm was the pick of choice?
Would I be better off ditching cm and using something else? I have just stuck with cm cause I am familiar with it. If I was going to go to a twrp ROM what would be the best option for kitkat. I really don't want nothing that's experimental. I want something tried and true and supported. I just don't have any experience with anything other than cm.
Back to the issue is there anyone out there running cm11 on ur i747 that's having same issues on the kk firmware also?
If someone just said "not having that issue" it would at least let me know the problem is not cm11 related and something else
might could read/ ask on the cm11 nightly thread. also some of the custom ROMs are based on cm anyway.
http://forum.xda-developers.com/showthread.php?t=2682905
err on the side of kindness
You should give one of the stock builds a fair chance. Kk ones are still under development, but there are some very good, completed roms based on 4.3 firmware.
Not a big fan of the stock att. I hate the interface and lack of options. Cm is fine and I could go back to 10.2.1 easy enough I just was wondering if anyone else has experienced this problem that I am having.
I was thinking someone a bit more knowledgeable with this could tell me why when phone is off it tries to boot when charger inserted. At least this is what it seems like its doing.. And then it freezes
Also when it freezes its before the spinning splash screen. Its on the screen that says Samsung galaxy s3 but has the lil cm android guy at the bottom. It won't make it to the spinning screen. Maybe my problem is with this screen and if there is a way to disable it I could test that
google???
err on the side of kindness
Are you saying I should Google instead of ask for the help....
Google can only get you so far on certain issues and rest assured I have googled the hell out of my issue.. This issue has prolly had at least 4 hours or more of "google" time...
If Google could answer all there would be no need in this section
hopefully as you posted earlier, someone with some sort of experience with this will chime in.
googling was just a suggestion as i did not know if you had searched yet.
no offense intended.
err on the side of kindness
Oh none taken sir
Thank you and the others for all the help provided
delete
err on the side of kindness
99.99999% chance it is not a problem with thr display. Never heard of one like that, but have seen your situation hundreds of times at least.
It seems to be with the kernel/bootloader combo... I had the issue with kt747 when using mjb but not any longer now that I'm on ne4. Mine didn't freeze but it wouldn't stay off when the charger was plugged in, and the recovery button combo wouldn't work with it charging either.
Sent from my SAMSUNG-SGH-I747 running TMS3KK-2.0
I am on the ne4 firmware, cm11 July snapshot, latest cwm recovery
What kernal would fix this?
I am having no other issues besides this. Did a wipe before and after baseband/ firmware update. I mean it
What you are describing is how it does the phone won't stay powered off when plugged in
Gets stuck on the boot logo that says galaxy s3 with the cm android guy at bottom. The one before the spinning splash.
How did you fix yours?
My situation is reversed as your problem started with ne4 and mine just went away with ne4, but I'm on a touchwiz 4.4.2 rom with kt747 tw kernel.
I can't speak for aosp kernels, but I've heard kt747 aosp doesn't currently work with wifi on latest cm builds. You may just have to try different kernels or wait till the kernels catch up with the firmware as downgrading from ne4 is NOT an option.
Sent from my SAMSUNG-SGH-I747 running TMS3KK-2.0
Do you like the touchwiz ROM that you are on now?
How would u say it stacks up against cm?
Gimme the name of the ROM and I may try it with that kernel
Related
I have searched via various keywords for days and have not found an answer to my problem yet. I have only run across one other post (on another forum) that describes exactly my issue and they are asking the exact same question I have with no response.
I am using the AT&T Samsung Galaxy S3. I have downloaded CM 10.0.0 stable d2att on several occasions (different computers even), verified the md5, and installed on my phone. I have used CWM, CWM Touch, and TWRP to install hoping it was an issue there. Regardless of what I have done, I have the same issue addressed below:
I make or receive a phone call. No problems answering a phone call when it comes in. However when I hang up, the screen immediately goes back to sleep (which seems to be normal for the Nexus after researching). However, if I press the power button after the call is ended, the screen does not turn on at all. The hardware buttons (menu and back) do light up however and they remain lit. Regardless of what I do my phone stays stuck in this mode unless I hold the power button for about 10 seconds or so and force it to reboot, at which point it operates normal with no issues until my next phone call.
Has anyone experienced this issue and if so did you find a way to resolve it that does not require rebooting the phone? Right now this is the only thing keeping me from using the ROM as my daily driver.
Imo, AOSP-based ROMs run best when coming from stock. I flash back to touchwiz the before flashing them. Not sure if you've tried this.
Also, I had some small issues with the exact same rom that kept me from making it my daily driver. If you want stability, I can vouch for AOKP 4.1.2. I'm in no hurry for 4.2 with this rom running so well with no bugs or glitches
xBeerdroiDx said:
Imo, AOSP-based ROMs run best when coming from stock. I flash back to touchwiz the before flashing them. Not sure if you've tried this.
Also, I had some small issues with the exact same rom that kept me from making it my daily driver. If you want stability, I can vouch for AOKP 4.1.2. I'm in no hurry for 4.2 with this rom running so well with no bugs or glitches
Click to expand...
Click to collapse
Thanks. Seems that it was destined not to work. Oh well. I was on TW nearly everytime. I will give AOKP a shot. Should like it equally as well because I prefer AOSP roms. I am assuming you restore nandroid stock...or do you odin flash?
aybarrap1 said:
Thanks. Seems that it was destined not to work. Oh well. I was on TW nearly everytime. I will give AOKP a shot. Should like it equally as well because I prefer AOSP roms. I am assuming you restore nandroid stock...or do you odin flash?
Click to expand...
Click to collapse
I don't think it matters but I usually restore my tw/stock nandroid because it's right there and I don't lose root.
When I flashed the rom im currently running, I formatted /system /data and battery. Not sure if you care or need that info, just passing it on as this device has run really well for me on this OS.
I also flashed the Nexus 4 camera/gallery and the TW clock. The aokp camera is lame-o, and controlling the alarms is easier on the TW clock.
If you can't find them on the forum here (where I got them), PM me your email and I will send you the zips if you are interested. I believe I flashed them both in cwm, wiped cache/dalvik and then adjusted permissions in root browser to rw-r-r
AOKP's 4.1.2 jellybean milestone 1 is still on goo.im
xBeerdroiDx said:
I don't think it matters but I usually restore my tw/stock nandroid because it's right there and I don't lose root.
When I flashed the rom im currently running, I formatted /system /data and battery. Not sure if you care or need that info, just passing it on as this device has run really well for me on this OS.
I also flashed the Nexus 4 camera/gallery and the TW clock. The aokp camera is lame-o, and controlling the alarms is easier on the TW clock.
If you can't find them on the forum here (where I got them), PM me your email and I will send you the zips if you are interested. I believe I flashed them both in cwm, wiped cache/dalvik and then adjusted permissions in root browser to rw-r-r
AOKP's 4.1.2 jellybean milestone 1 is still on goo.im
Click to expand...
Click to collapse
I actually downloaded the camera/gallery apk for 4.2 as well as the keyboard. Already installed and running. Prefer both over the 4.1.2 versions installed on AOKP and CM10. Thanks for the info.
Hey all -
I have a T-Mobile Galaxy SIII with TWRP, AOKP JB Milestone 5 and GooManager. I got a pop-up for AOKP JB Milestone 6 this morning, so I downloaded it and added that file, Lean Kernel 2.9 and gapps (latest that could be downloaded) to the flash list. I set my Dalvik cache to clear before flashing anything, then rebooted the phone to flash everything. Immediately after the flash, the phone seemed to reboot, but with a blank screen. After a while, the capacitive buttons on the front started working and when I plugged the phone into my computer the file transfer program popped up.
However ... at no point can I ever get anything to display on the screen. I've tried rebooting into recovery (volume up, home button, power button) and nothing. I don't really care about the data on my phone, I have proper backups of everything. But what I can't seem to do is get it to a point where I can recover it. What are my options here if rebooting into recovery doesn't work?
Thanks!
As an addendum, the phone is clearly booted into the OS. I have a blinking notification LED that indicates a new e-mail, and calls placed to the phone cause it to ring. I just can't see .... anything on it.
I was able to get into TWRP, somehow. I took out my T-Mobile SIM card and had it plugged into USB. I held down the recovery combo and then it booted up into recovery. It also displayed the Galaxy SIII white splash screen for the first time since the bad flash. What the hell.
chuffykow said:
I was able to get into TWRP, somehow. I took out my T-Mobile SIM card and had it plugged into USB. I held down the recovery combo and then it booted up into recovery. It also displayed the Galaxy SIII white splash screen for the first time since the bad flash. What the hell.
Click to expand...
Click to collapse
so was you able to use your phone again i say go back to a nandroid you have or flash a rom that you know works good on your phone without that white screen and trouble shoot from there that it very strange indeed if you get success with the other just try posting in the ROM thread that you flashed you could possibly get more help where it happened :good:
I went back to AOKP Milestone 5 after doing a full wipe. I saw a number of graphics changes in the Milestone 6 code review, so it's possible that had something to do with it. In any case, I'm no longer panicing
Does mr6 use the 3.4 kernel? If yes, then you were using the wrong version of leankernel.
Ya its all kernel related and user error.
Aerowinder said:
Does mr6 use the 3.4 kernel? If yes, then you were using the wrong version of leankernel.
Click to expand...
Click to collapse
mt3g said:
Ya its all kernel related and user error.
Click to expand...
Click to collapse
I assumed it was user error. I just wanted to lay out the steps I took, so I could get some help on a recovery path. I thought that a JB based ROM would work with any kernel that supports JB. Looks like I was wrong.
chuffykow said:
I assumed it was user error. I just wanted to lay out the steps I took, so I could get some help on a recovery path. I thought that a JB based ROM would work with any kernel that supports JB. Looks like I was wrong.
Click to expand...
Click to collapse
Nope, JB can be AOSP, TouchWiz, 4.1, 4.2, 4.2.2, 3.0 kernel, 3.4 kernel. Just need to read and make sure you know what you're doing before just doing it. That's why I frown at people being lazy (not just you) and not reading the forums and such, and just using apps to update and flash.
mt3g said:
Nope, JB can be AOSP, TouchWiz, 4.1, 4.2, 4.2.2, 3.0 kernel, 3.4 kernel. Just need to read and make sure you know what you're doing before just doing it. That's why I frown at people being lazy (not just you) and not reading the forums and such, and just using apps to update and flash.
Click to expand...
Click to collapse
Thank's for the condescension, I appreciate being called lazy. I might not have an encyclopedic knowledge of Everything Android, but between the knowledge I do have and the details I read on the AOKP release page, I saw nothing that indicated I _couldn't_ run LeanKernel, especially when it was only a point release on the same ROM I was previously using.
I had a look at the changelog that's available on their page. It's pretty lame. http://gerrit.sudoservers.com/#/q/status:merged,n,z that one will probably have the kernel info. A good rule of thumb is when you flash a new rom, wait until the kernel is up to date (release date). For instance, don't flash a 3/01 kernel on a 4/24 rom - wait for kernel update.
I don't recommend flashing anything with the 3.4 kernel right now. Even if you manage to pull off stability, it's still laggy and eating about 3x the battery it should. This goes for the custom kernels, too. I'll put up with stability issues, but can't deal with bad battery. Already bad enough as it is. Need my phone during the day and not near a charger.
chuffykow said:
Thank's for the condescension, I appreciate being called lazy. I might not have an encyclopedic knowledge of Everything Android, but between the knowledge I do have and the details I read on the AOKP release page, I saw nothing that indicated I _couldn't_ run LeanKernel, especially when it was only a point release on the same ROM I was previously using.
Click to expand...
Click to collapse
calm down lol, you could have read up any of the kernel threads that there are some compatible issues with kernels and roms right now.
Aerowinder said:
I had a look at the changelog that's available on their page. It's pretty lame. http://gerrit.sudoservers.com/#/q/status:merged,n,z that one will probably have the kernel info. A good rule of thumb is when you flash a new rom, wait until the kernel is up to date (release date). For instance, don't flash a 3/01 kernel on a 4/24 rom - wait for kernel update.
I don't recommend flashing anything with the 3.4 kernel right now. Even if you manage to pull off stability, it's still laggy and eating about 3x the battery it should. This goes for the custom kernels, too. I'll put up with stability issues, but can't deal with bad battery. Already bad enough as it is. Need my phone during the day and not near a charger.
Click to expand...
Click to collapse
Thanks for the tip! I appreciate it.
I tried to post this on cyanogen mods website but I was not allowed to post
I bought a AT&T Galaxy S III for my wife this weekend and ran into several problems installing cyanogenmod 10 on it.
Installing:
First the Heimdall program failed to "initialize interface" and no matter what I tried it failed to connect.
I managed to get it installed by using the ODIN to flash different clockwork mod (but that errored out on the when I went to flash cyanogenmod 10 )
So I used that to root it then installed cyanogenmod via rom manager by having that install the right clockwork mod then cyanogen 10.
It would be nice if they provided a ODIN Image for cyanogenmod
VoiceMail:
voicemail was missing its number after I installed cyanogen mod.
It took me forever to get this correct. Found out that you just forward to your mobile number. In the phone settings. or dial **004*PhoneNumber#
Also Google voice failed to setup correctly as well and had to use the **004 path.
Skype:
downloading via google play kept returning "package file invalid" (I cleared /cache and dalvik cache still failed) I ended up downloading it via the androiddrawer website and it installed (sideload?).
The problem with this is when using the voice or video chat the other side just hears very load static. Found someone claiming these problems came from cyanogenmod 10 not using the correct mics all the time. This is still an issue.
My questions are these issues fixed in the most recent version of Cyanogen the M releases? And if not are they known and someone working on them?
And does anyone have a fix for the static issue in skype?
JonoPorter said:
I tried to post this on cyanogen mods website but I was not allowed to post
I bought a AT&T Galaxy S III for my wife this weekend and ran into several problems installing cyanogenmod 10 on it.
Installing:
First the Heimdall program failed to "initialize interface" and no matter what I tried it failed to connect.
I managed to get it installed by using the ODIN to flash different clockwork mod (but that errored out on the when I went to flash cyanogenmod 10 )
So I used that to root it then installed cyanogenmod via rom manager by having that install the right clockwork mod then cyanogen 10.
It would be nice if they provided a ODIN Image for cyanogenmod
VoiceMail:
voicemail was missing its number after I installed cyanogen mod.
It took me forever to get this correct. Found out that you just forward to your mobile number. In the phone settings. or dial **004*PhoneNumber#
Also Google voice failed to setup correctly as well and had to use the **004 path.
Skype:
downloading via google play kept returning "package file invalid" (I cleared /cache and dalvik cache still failed) I ended up downloading it via the androiddrawer website and it installed (sideload?).
The problem with this is when using the voice or video chat the other side just hears very load static. Found someone claiming these problems came from cyanogenmod 10 not using the correct mics all the time. This is still an issue.
My questions are these issues fixed in the most recent version of Cyanogen the M releases? And if not are they known and someone working on them?
And does anyone have a fix for the static issue in skype?
Click to expand...
Click to collapse
Unless your wife can troubleshoot issues why install a custom ROM on her phone. My wife would kill me since she has no clue but I digress.
Why not flash 10.1 on the phone and download the gapps from the goo.im site and see if hat helps your issues. Maybe you got a bad flash and/or download. For the short amount of time I tried it I didn't have any of these issues you do. Those don't seem to be any bugs in the known bugs beyond maybe the static. Task's AOKP is another one to try if you want a custom stable rom.
Try another ROM or maybe a fairly stock rooted rom and see if that clears up any issues.
Are you using a Mac or a PC ? You mentioned Odin (for windows PC's) and heimdall (for all others). Honestly the best way is to flash a stock rooted ROM from the no tripping flash counter Rooting thread in Development and then flashing CWM in rom manager. Limiting having to flash in odin is the far better option. I've never ha d a bad flash in a custom recovery but everytime I have to use Odin I get extremely nervous.
Read Beerdroid's guide and you can't go wrong
hednik said:
Unless your wife can troubleshoot issues why install a custom ROM on her phone. My wife would kill me since she has no clue but I digress.
Why not flash 10.1 on the phone and download the gapps from the goo.im site and see if hat helps your issues. Maybe you got a bad flash and/or download. For the short amount of time I tried it I didn't have any of these issues you do. Those don't seem to be any bugs in the known bugs beyond maybe the static. Task's AOKP is another one to try if you want a custom stable rom.
Try another ROM or maybe a fairly stock rooted rom and see if that clears up any issues.
Are you using a Mac or a PC ? You mentioned Odin (for windows PC's) and heimdall (for all others). Honestly the best way is to flash a stock rooted ROM from the no tripping flash counter Rooting thread in Development and then flashing CWM in rom manager. Limiting having to flash in odin is the far better option. I've never ha d abad flahs in a custom recovery but everytime I have to use Odin I get extremely nervous.
Click to expand...
Click to collapse
agreed.
there are a couple good and stable stock/touchwiz custom roms as well as AOSP-based roms on this forum. i would steer clear of nightlies and super-custom roms that are always posting new updates. these are less stable imo.
put something on her phone thats solid and be sure to use the proper wiping and flashing procedures when you do so. wiping/flashing correctly makes ALL the difference on the software's performance while it's running on a device
xBeerdroiDx said:
agreed.
there are a couple good and stable stock/touchwiz custom roms as well as AOSP-based roms on this forum. i would steer clear of nightlies and super-custom roms that are always posting new updates. these are less stable imo.
put something on her phone thats solid and be sure to use the proper wiping and flashing procedures when you do so. wiping/flashing correctly makes ALL the difference on the software's performance while it's running on a device
Click to expand...
Click to collapse
Well I went with Cyanogen because I used it on my old droid incredible and its was great. I also want a stock like rom because I personally use a stock Nexus 4 and want my wifes phone to be similar and wanted to remove all the retarded extra apps atnt and samsung threw on.
So no idea if the 10.1 would fix the static issue then?
JonoPorter said:
Well I went with Cyanogen because I used it on my old droid incredible and its was great. I also want a stock like rom because I personally use a stock Nexus 4 and want my wifes phone to be similar and wanted to remove all the retarded extra apps atnt and samsung threw on.
So no idea if the 10.1 would fix the static issue then?
Click to expand...
Click to collapse
I can't say for sure but download and see if it works out of you. Thing with bugs is that they aren't always reproducible. I don;t see your issue as a known bug on 4.2.2. There are a few other ROM like super nexus in the dev section that are a practically stock nexus feel. Why not give that one a try ? Give AOKP a try as well.
Here's super nexus:
http://forum.xda-developers.com/showthread.php?t=2219944
hednik said:
I can't say for sure but download and see if it works out of you. Thing with bugs is that they aren't always reproducible. I don;t see your issue as a known bug on 4.2.2. There are a few other ROM like super nexus in the dev section that are a practically stock nexus feel. Why not give that one a try ? Give AOKP a try as well.
Here's super nexus:
http://forum.xda-developers.com/showthread.php?t=2219944
Click to expand...
Click to collapse
i'm an advocate of AOKP, but thats just my 2 cents. there is a very solid 4.1.2 milestone out and their 4.2.2 milestone will be released very soon.
although faryaab is a great kid and puts some good stuff together, remember that supernexus is a port and you could experience bugs (as i did). again, just my opinion
Alright, so I am having this weird issue. I thought I found the fix for it several times, however, NO dice.
I've researched for a few hours now, I just don't know if I have over looked it or what. If it has been answered, I apologize.
I looked at the modified recoveries thread for newer s3 devices, but it doesn't seem to fit my area of error.
The Details:
I've been really curious to try some 4.3 roms. Of course, they are for D2SPR. I get them to flash correctly, after a full wipe. The issue happens right after I set everything up in the phone, and reboot. When I reboot I get hung at the splash screen. I have tried to reflash the rom muliple times only to fall flat on the splash screen again. Now, I don't have an SD Card in the phone, except, I left a TW rom in a folder. I use twrp, forgot to mention that. I rewiped the phone and installed that touchwiz rom, and still it wouldn't allow me to get past splash into that tw rom.
So the only way that I could think of to get out of this hole was to flash the rooted LJ7 tar file I have through ODIN. After getting the S3 into download mode, Odin successfully push LJ7 into my phone. Now again, I had an issue getting it to boot. I read somewhere that when this happens, I need to check the Erase NAND option in Odin. So I tried that out and forced LJ7 back on. After successfully flashing, it boots but gets stuck on the boot animation; the fix to that is booting into stock recovery and wiping once more. Then you are able to get into the OS.
I let the phone sit and take the OTAs till I get from LJ7 to MD4 so I re-root the phone using Odin and Chain Fire's root method. Now I am able to flash the recovery (TWRP) using OpenScript through Goo Manager.
I've only tried flashing Illusion and Carbon's 4.3 rom. The second time I used Carbon's rom. Same results. So I have no Idea what the heck is going on. Can anyone explain this to me better or point me into the direction that I need to go?
Thanks much!
your not the only one that has this problem i have the same thing have tried everything and most of the 4.3 roms same thing. no one on xda seems to know at least i havent gotten any help or responses i have just given u on 4.3. good luck finding any ideas.
Set it up I'm sure you restored some apps and data which may no longer be compatible. Or data which is corrupting the 4.3 rom. Try just flashing the rom setting up your Google account and don't add any apps. See if it does it.
Either way this seems to be a common issue across different devices and 4.3 seems it's part of using roms built on leaks and ports. None are bug free. Very similar to all gb leaks back in the day that would go into bootlooping.
Have a great day!
bbrita said:
your not the only one that has this problem i have the same thing have tried everything and most of the 4.3 roms same thing. no one on xda seems to know at least i havent gotten any help or responses i have just given u on 4.3. good luck finding any ideas.
Click to expand...
Click to collapse
Well, it's good to know that I'm not the only one, however, it's horrible that it's happening to others. I appreciate you spreading the info!
edfunkycold said:
Set it up I'm sure you restored some apps and data which may no longer be compatible. Or data which is corrupting the 4.3 rom. Try just flashing the rom setting up your Google account and don't add any apps. See if it does it.
Either way this seems to be a common issue across different devices and 4.3 seems it's part of using roms built on leaks and ports. None are bug free. Very similar to all gb leaks back in the day that would go into bootlooping.
Have a great day!
Click to expand...
Click to collapse
When I go to set up, I just install about 15 apps, I don't restore. I just download them fresh. I had a habit of doing that and it just stuck. I don't restore anything with Titanium or and root backup/restore app. Could one of those apps not be updated then that causes the partitions to get locked up, or just corrupt /data in general? If that's whats happening.
I just find it extremely odd that I (maybe others), can't wipe, and then re flash another rom; actually I can, it just gets stuck at the splash and never goes forward, that is what had me confused most. If I had an sd card, and formatted data itself, would that fly?
thanks Ed i have tried this after the first 2 tries . i dont have any problems installing 4.3 its just after rebooting it gets stuck. Like you said there are always bugs Im fine with using other roms for now. Hopefully when an official 4.3 drops problems will go away
Hi guys, i swear i searched! for like days! i still haven't found out how to solve this issue. problem started when i tried hellybean a few weeks back, and then i heard someone on the thread said to try and use the latest beta uber kernel at the time, and i did. What end up happening was that my hardware keys are dead, the lights still works but very dim, i think this is because of the swipe to wake thing where it leaves your hardware keys on 24/7 as long as the phone is on, which is not that bad because i'm now used to using the nav bar. but the real problem is that now every time I install a rom that is not JB 4.1 (haven't tried 4.2 though) i.e. 4.3, 4.3.1, it gets stuck at the app optimization screen, it would go about half way through optimizing the apps, and then just reboots itself, and it'll do that over and over, like boot loop but it can actually go into the rom. So i think this is not as bad as a situation as soft bricking or hard brick, but i just really don't know what the heck is going on to even try and fix it. I've tried odin, thinking that there may be something wrong in the boot file, nada, factory reset, nada, the only thing that worked was installing the 4.1 roms, i think it is because the 4.1 roms don't require app optimization.
If anything maybe anyone out there can help me find a way to disable app optimization? maybe that'll let me get into the rom.
btw, i dont really mind using 4.1, but i really want to try the jedi rom, but having my hardware buttons dead and jedi rom being TW and it doesn't seem to have a nav bar make it impossible for me to use the rom, so i've only been able to use cyanogen 4.1, which are great but they are pretty outdated, so if there are anyway to fix that, lmk too.
Anyways, any help would be appreciated thanks a ton guys! sry for essay!
have you used the infamous cache wipe? http://forum.xda-developers.com/showthread.php?t=2235141 try this and it should fix your issues its because your going from AOSP/AOKP to TW they dont like each other lol follow those instructions and you should be good. also what recovery are you using to flash these?
krazierokz said:
have you used the infamous cache wipe? http://forum.xda-developers.com/showthread.php?t=2235141 try this and it should fix your issues its because your going from AOSP/AOKP to TW they dont like each other lol follow those instructions and you should be good. also what recovery are you using to flash these?
Click to expand...
Click to collapse
Lol actually the problem started when I was on 4.3, and then upgraded to 4.3.1 helly bean, in which i tried to use the beta uber kernel, that was when the problem started. So the only roms that allows me to get pass the optimization screen were the 4.1.2 roms, which were TW, pananroid, like i tried a bunch, like super old ones, they all worked, just that when i try to get any rom higher than 4.1.2, it keep going back to that. And yeah when i tried to upgrade from jedi to aosp, to tried using infamous cache and it didnt work :/ because i've heard that's what would fix it... and lastly, Im using twrp 6.1 i think, not the latest one.
Thanks alot for the reply!
PS. I see you running slimbean 4.2.2, how is it? any probs? maybe i can try a 4.2.2 if this doesn't work out, i havn't been able to get any 4.2.2 roms cause the links are all dead, so idk if i'll have problems with 4.2.2. if there's anyway you can link it for me that'll be great! thanks!
PSS: also i've tried odin, but idk if that actually wipes everything, i'm having a feeling that it might be a script problem or something because it goes into the rom once, but it just refused to work and after like 10 seconds it reboots.
quick question are you trying to restore 4.1/4.2 apps on your 4.3 ? apps dont play nice like that sometimes .. also your not restoring any system apps are you? Personally i love all the ROMs/Mods the devs put out for us but im one who likes it really stable with very few bugs so i like to stick with stable ROM's so thats why im still on 4.2.2 its nearly perfect no issues here brother . When you flash the rom what are your actual steps in detail please from the time you boot into recovery until you finish so i can get a better idea here
krazierokz said:
quick question are you trying to restore 4.1/4.2 apps on your 4.3 ? apps dont play nice like that sometimes .. also your not restoring any system apps are you? Personally i love all the ROMs/Mods the devs put out for us but im one who likes it really stable with very few bugs so i like to stick with stable ROM's so thats why im still on 4.2.2 its nearly perfect no issues here brother . When you flash the rom what are your actual steps in detail please from the time you boot into recovery until you finish so i can get a better idea here
Click to expand...
Click to collapse
Ey thanks for the reply, ok so first, I did not try to restore any apps or system apps, I even odin so everything were wiped cleaned. So really dont know whats going on. After I updated to a newer hellybean, not newest by now, and a beta uber kernel, this happens. I see two other people having the same problem too. Also I tried to use 4.2.2 roms, did not work
Anyways any insight would be apreciated!
Thanks!
One more thing, I tried twrp 2.6.1.0 to flash as reccomended by all devs and still no results. :/
Damn sorry brother that's pretty frustrating try dirty flashing helly bean and just wipe dalvik and cache and see if using the stock kernel helps first then see what happens :banghead:
sent from my t mobile S4
krazierokz said:
Damn sorry brother that's pretty frustrating try dirty flashing helly bean and just wipe dalvik and cache and see if using the stock kernel helps first then see what happens :banghead:
sent from my t mobile S4
Click to expand...
Click to collapse
oh well, thanks for the reply then, im trying 4.4, hopefully it'll help... somehow... lmao idk haha