just flashed newest updates to both. screen rotate is inverted anyone have any solutions?
anon997 said:
just flashed newest updates to both. screen rotate is inverted anyone have any solutions?
Click to expand...
Click to collapse
Need more info on your exact installation procedure, including anything you did before rebooting to recovery.
Sent from my Nexus 4 using xda premium
LuigiBull23 said:
Need more info on your exact installation procedure, including anything you did before rebooting to recovery.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
1)booted to recovery
2)cleared cache
3) installed cm 10.1 update
4) flashed kernel
5) rebooted
everything else works great except for screen rotate
anon997 said:
1)booted to recovery
2)cleared cache
3) installed cm 10.1 update
4) flashed kernel
5) rebooted
everything else works great except for screen rotate
Click to expand...
Click to collapse
Well based on this it sounds like a dirty flash to me. You should try a clean install of the ROM and gapps, reboot, then go back to recovery and flash the kernel, wipe cache/dalvik once again, fix permissions, then finally reboot, and see if that fixes the issue.
Sent from my Nexus 4 using xda premium
Inverted screen is a sure sign that somethings wrong with the kernel. Either download it again and flash, or switch to another kernel.
LuigiBull23 said:
Well based on this it sounds like a dirty flash to me. You should try a clean install of the ROM and gapps, reboot, then go back to recovery and flash the kernel, wipe cache/dalvik once again, fix permissions, then finally reboot, and see if that fixes the issue.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
didnt work. i thought it would have been the gapps i had since i was still using 4.2.1 so i updated that to 4.2.2 and still inverted.
anon997 said:
didnt work. i thought it would have been the gapps i had since i was still using 4.2.1 so i updated that to 4.2.2 and still inverted.
Click to expand...
Click to collapse
What ROM and kernel were you running before attempting to update?
Sent from my Nexus 4 using xda premium
Inverted screen is a kernel issue. Did Ktoonsez compile using a different kernel source? Sprint's variant handles screen rotation differently than the other three carriers. You sure you downloaded a Sprint version of Ktoonsez kernel, and not an ATT or other variants?
Overstew said:
Inverted screen is a kernel issue. Did Ktoonsez compile using a different kernel source? Sprint's variant handles screen rotation differently than the other three carriers. You sure you downloaded a Sprint version of Ktoonsez kernel, and not an ATT or other variants?
Click to expand...
Click to collapse
No and as he said, everything else works fine. If he were to flash Ktoonsez' ATT kernel he most definitely would have winded up in a brick. CDMA and GSM don't play nice at all together..
Sent from my Nexus 4 using xda premium
i pmed ktoonsez and he said exact same thing overstew said to check to make sure i downloaded correct carrier for kernal. im on sprint. i looked at the download i had it it was ATT. so once i flash the sprint kernel it should be fixed. i need to pay attention to which part of the forum i download from from now on.
Related
I have been looking all over and my eyes are about ready to have a critical meltdown.
I have a T-Mo T-989 (Hercules) and have been looking for a JB ROM all night and found some shady threads or ROMs that don't work. I dunno, maybe I've installed something wrong, little help here?
Generally the ones that will install get hung up during the initial boot, wtf? Have run across some that wouldn't even install and would abort.
I should say I am using CWM 5.0.2.6... I think, its been so long since I have done anything to this phone so I forget but I know its ither Odin or CWM (or are they both one in the same? x.x ) I've been using Darkside Evolution ICS ROM all this time and would be nice to move up to JB if there is a stable one out there
Have you tried vincom's cm build? http://forum.xda-developers.com/showthread.php?t=1886009 its very stable. Been using it for 9 days now without a single SOD or RR. To get the best results I recommend using TWRP. Just head over to the play store and download GooManager. Open, grant superuser, hit menu, then click on "install open recovery script". Go through the prompts and it will download and install TWRP. The method I use for flashing was: Darkside superwipe, ROM, gapps. (I did not use the super light gapps because the home button doesn't work when I do and it doesn't auto restore my apps)
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
iburnhearts said:
Have you tried vincom's cm build? http://forum.xda-developers.com/showthread.php?t=1886009 its very stable. Been using it for 9 days now without a single SOD or RR. To get the best results I recommend using TWRP. Just head over to the play store and download GooManager. Open, grant superuser, hit menu, then click on "install open recovery script". Go through the prompts and it will download and install TWRP. The method I use for flashing was: Darkside superwipe, ROM, gapps. (I did not use the super light gapps because the home button doesn't work when I do and it doesn't auto restore my apps)
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Hmm, well I got goo manager and its now stuck on the TWRP's boot screen and just reboots after so long of sitting there :/ and its already deleted the rom, so I guess I have to go through the CWM rooting proceeders again?
Well I have managed to get CWM5 back on it and got a working ROM for now but it seems when I do the method you imply it flukes and freezes at the TWRP boot screen. I followed ye the best way possible, maybe there is an alternative way?
I have tried installed Vincom's JB all versions and it comes back as error then aborts install or it installs but sits at initial boot for more than 25min and does nothing I've found that while the warning say give it 10min to boot is generally just a 'just in case' scenario since the T989's processors are considerably powerful.
I have tried to get the ROM onto the phone's internal memory and install from there like Vincom said but the computer won't read the phone for some reason >.<
i would say, to use twrp and download the latest cm10 Here.
i recommend twrp for stable flashing cause there's bugs in latest cwm...
PorscheHusky said:
Well I have managed to get CWM5 back on it and got a working ROM for now but it seems when I do the method you imply it flukes and freezes at the TWRP boot screen. I followed ye the best way possible, maybe there is an alternative way?
I have tried installed Vincom's JB all versions and it comes back as error then aborts install or it installs but sits at initial boot for more than 25min and does nothing I've found that while the warning say give it 10min to boot is generally just a 'just in case' scenario since the T989's processors are considerably powerful.
I have tried to get the ROM onto the phone's internal memory and install from there like Vincom said but the computer won't read the phone for some reason >.<
Click to expand...
Click to collapse
Flash this. Its a flashable TWRP 2.3.1.1 zip.
http://db.tt/gu2PDvZI
Restart recovery, your good!! You need the newer recoveries, like TWRP or CWM 6 to flash JB ROMs
Sent from my SGH-T989 using xda premium
LoopDoGG79 said:
Flash this. Its a flashable TWRP 2.3.1.1 zip.
http://db.tt/gu2PDvZI
Restart recovery, your good!! You need the newer recoveries, like TWRP or CWM 6 to flash JB ROMs
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Not entirely true. Contrary to what everyone has been saying, and im not trolling just saying from personal experience - cwr 5.0.2.7 and dark side wipes have yet to give me problems I was on the majority if not all jb roms with no issues other than rr/sod which was before the kernel fix.
I'm a noob and expect that 90% of the people here kno more than I do but I wish someone could explain to me why the scripts and cwr 5027 are suddenly so bad.
::
Sent from my SGH-T989 using xda app-developers app
John imilitym
bzlik88 said:
Not entirely true. Contrary to what everyone has been saying, and im not trolling just saying from personal experience - cwr 5.0.2.7 and dark side wipes have yet to give me problems I was on the majority if not all jb roms with no issues other than rr/sod which was before the kernel fix.
I'm a noob and expect that 90% of the people here kno more than I do but I wish someone could explain to me why the scripts and cwr 5027 are suddenly so bad.
::
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
CWR 5027 isn't bad at all it's just that using darkside scripts with certain new recoveries has caused some people boot loops and also with the newer recoveries they aren't required since the built in wipe options work just fine.Personally I use the recovery here http://forum.xda-developers.com/showthread.php?t=1844637
and have had zero issues with it plus it has the darkside scripts built in
Galaxy S Bean ROM! 4.1.2 almost everything stable from Camera to Phone Calls
Sent from my SGH-T989 using xda app-developers app
arthurgreeeen said:
Galaxy S Bean ROM! 4.1.2 almost everything stable from Camera to Phone Calls
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
+1. You can't go wrong with that Rom! I been running it for over a week now with zero complaints
Sent from my SGH-T989 using xda app-developers app
With the v3 sbean I couldn't get my home button to work when I ask tmo twice he didn't respond to my question. I'm looking at slimbean next we'll see how that goes
Sent from my SGH-T989 using xda app-developers app
I would recommend trying either AOKP OFFICIAL Build 5 (not sure if by time you read this if theres a newer one) or a CM10 Nightly. I've tried tons of different JB roms from 4.1 to 4.1.2 and those work good. Decent battery life without changing too many settings (I'm afraid to change too many things because I've hard bricked my phone before but barely got it replaced under the 20 day full exchange warranty). No random reboots or force closes for me so far. Highly recommend trying them out, very simple to flash.
Been on the official aokp and its amazingly stable better then anything jb rom I tried on the s2 battery is excellent too
Sent from my SGH-T989 using xda app-developers app
duckied said:
Been on the official aokp and its amazingly stable better then anything jb rom I tried on the s2 battery is excellent too
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
And I haven't had anything go majorly wrong with cm10 since the nightlies went official. I'm on the 10/24 nightly right now.
Sent from my A100 using Tapatalk HD
Nice nice... I wanna test out CMX maybe I'll make a nand backup and check it out
Sent from my SGH-T989 using xda app-developers app
LoopDoGG79 said:
Flash this. Its a flashable TWRP 2.3.1.1 zip.
http://db.tt/gu2PDvZI
Restart recovery, your good!! You need the newer recoveries, like TWRP or CWM 6 to flash JB ROMs
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Actually... I have CMW6 now the touch one. Does that have something to do with it? The main issue I have with SBean and CM9's JB is eveyrone complains that they can't hear me, that I sound like a robot and the call is badly broken up or that I'm not speaking up like my mic isn't picking up on my voice very well.
Is this a ROM error or a kernel error? rather annoying frankly @[email protected]
Go to your phone app then settings and check noise suppression
Sent from my SGH-T989 using xda premium
duckied said:
Go to your phone app then settings and check noise suppression
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
This is a sure fix then? This would make me the happiest Porsche Husky on Earth if I could go back to Sbean
The customization features of it are to die for
Ooooo, wait a tic... I feel like such n00b now...
I kept downloading V1 thinking it was the newest one xD I think the V6 at the way bottom is the newest one. I'll try that for a few days then report back.
Edit: QUESTION - my screen is flickering (just installed SBEAN V6)... is that a bad install or did I have to fix permissions?
That pretty common in most JB rom but it usually goes away after few mins for me. You can go to settings and then developer options then disable hw overlay but you would need to do it on every boot because it won't stick after a reboot.
Btw you should check out official aokp-milestone-1 it not on here but Google aokp and download the one for our phone. Its pretty sick and stable.
Sent from my SGH-T989 using xda premium
Sorry for the noob question. I searched but i couldn't find the answer I'm looking for. Here's the deal...i have had alot of rooted phones but i just rooted my own phone for the first time,obviously the GNex. I used the toolkit i found on here and it went great. I am using TWRP recovery cause it was recommended by AOKP and when i flashed there new Jb ROM i noticed how twrp is set up a lot different then CWM. I found out that i had to factory wipe before flashing. So getting to my question. When i flash the update do i do that same wipe or do i wipe cache,davlik and/or system? Also i gotta do a back up first right? Then with gapps is it the same steps as flashing the update? If someone can show me the way that would be great. Thanks.
Sent from my Galaxy Nexus using xda app-developers app
1. Backup current ROM
2. Wipe
3. Flash new ROM
4. Flash GAPPs (if required)
5. Reboot
Well, for updating purpose you've only to wipe cache and dalvik (but i think it's not mandatory for all the rom) then you straight flash the rom and gapps (everytime both) then you reboot and you're good to go! And backup is always welcome!
[email protected] said:
Well, for updating purpose you've only to wipe cache and dalvik (but i think it's not mandatory for all the rom) then you straight flash the rom and gapps (everytime both) then you reboot and you're good to go! And backup is always welcome!
Click to expand...
Click to collapse
Thank you. I wasn't sure exactly what to wipe........my ass i know, but still learning this stuff.
Sent from my Galaxy Nexus using xda app-developers app
EddyOS said:
1. Backup current ROM
2. Wipe
3. Flash new ROM
4. Flash GAPPs (if required)
5. Reboot
Click to expand...
Click to collapse
If you're staying on the same rom with just an update you probably don't have to wipe unless you have issues upon reboot but otherwise you probably always should.
so i got an update notification from goo saying my rom and gapps have an update (aokp jb 4.2 mr1 build 2) so i flashed em and i got my stock reboot screen then every google app foreclosing over and over but rom still there. what the hell????
This is for sprint ain't it?!!?
Sent from my Galaxy Nexus using xda app-developers app
elliot2112 said:
This is for sprint ain't it?!!?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Toro would be Verizon.
sent from my Google Galaxy Nexus
bk201doesntexist said:
Toro would be Verizon.
sent from my Google Galaxy Nexus
Click to expand...
Click to collapse
well what happened here then? i looked on aokp and its not there. its the one i have now build 1. im really confused. the new gapps update is 20120429. it must be wrong if everything google was foreclosing. so what did goo.im give me?
ok it is build 2 on aokp. so gapps must be the same one i have been using? because this new one everything was foreclosing.
Better off doing updates manually and not using an app to do it for you
elliot2112 said:
well what happened here then? i looked on aokp and its not there. its the one i have now build 1. im really confused. the new gapps update is 20120429. it must be wrong if everything google was foreclosing. so what did goo.im give me?
Click to expand...
Click to collapse
From the date I think you flashed a gapps for jb 4.1 on a 4.2 ROM. Pretty sure that the 4.2 gapps is dated 12/12/12.
EddyOS said:
Better off doing updates manually and not using an app to do it for you
Click to expand...
Click to collapse
ya thats what im about to do now.
i went and downloaded build 2 straight from aokp and flashed that with same gapps for build 1 cause that hasnt changed on there site. my boot animation is the stock nexus logo instead of that pink unicorn with the gears. i figured it still wasnt working but everything seems to be running normal.....actually really fricken smooth and snappier. thanks for all your input everybody!
Hello everyone,
After trying to install JellyBAM v7.0.0, my phone would not boot. This was extremely frustrating, as jellybam is one of my favorite ROMS. The issue was with the kernel that came in the zip with the ROM.
This issue can be fixed one of two ways:
1. Dirty flash from v6.7.0
Have v6.7.0 already installed
-Wipe Cache
-Wipe Dalvik
Install from zip v7.0.0
2. Clean flash with different kernel
-Wipe Data
-Wipe Cache
-Wipe Dalvik
-Format System
-Install from zip v7.0.0
-Install your favorite kernel
I am currently running BMS kernel and it is working fine, but any kernel for 4.2.2 will do
Enjoy!
bump
Pretty sure jellybam ROMs are banned...
Sent From My Rooted, S-OFF'd Blackberry Curve using the iOS XDA Application for Android.
This didn't work for me. What worked was restoring just the BOOT from my previous 6.7.0. install (via advanced restore from CWM). Thanks though,
asaa said:
This didn't work for me. What worked was restoring just the BOOT from my previous 6.7.0. install (via advanced restore from CWM). Thanks though,
Click to expand...
Click to collapse
No reason this shouldn't work for you..
just tried flashing 7.0 and it failed might try downloading again later
Sent from my SCH-R530U using Tapatalk 2
trvbone said:
just tried flashing 7.0 and it failed might try downloading again later
Sent from my SCH-R530U using Tapatalk 2
Click to expand...
Click to collapse
Did you try one of the methods in the OP?
asaa said:
This didn't work for me. What worked was restoring just the BOOT from my previous 6.7.0. install (via advanced restore from CWM). Thanks though,
Click to expand...
Click to collapse
The only thing that wouldve changed it from the previous boot.img is the kernel
Maybe they changed the kernel between versions and it got messed up on v7
CNexus said:
The only thing that wouldve changed it from the previous boot.img is the kernel
Maybe they changed the kernel between versions and it got messed up on v7
Click to expand...
Click to collapse
You are correct. Its not that people are needing to redownload or something, the kernel that comes with the ROM is just broken. The dirty flash will keep the kernel from 6.7 and the clean flash with a seperate kernel will both solve this issue.
I'm on us cellular S3 I can't find 6.70 for my phone, I couldn't get it to even start flashing the zip. So option number 2 is not an option Lol
Sent from my SCH-R530U using Tapatalk 2
Amizzly said:
You are correct. Its not that people are needing to redownload or something, the kernel that comes with the ROM is just broken. The dirty flash will keep the kernel from 6.7 and the clean flash with a seperate kernel will both solve this issue.
Click to expand...
Click to collapse
I know, I was just posting that for his/her benefit because he/she seemed to have misunderstood it
I used the dirty flash version and it worked perfectly. Only one problem. It started out with my WiFi working. Then it stopped. I am in a place with free WiFi and i can not even turn WiFi on. Am i doing something wrong or is there an easy fix? I do appreciate everything that is shared here. Also thanks for the fix to get JellyBam 7.0 to work.
I am on a Galaxy S3 i747 AT&T phone.
Thanks in advance,
Jason
ja50nd4vi5 said:
I used the dirty flash version and it worked perfectly. Only one problem. It started out with my WiFi working. Then it stopped. I am in a place with free WiFi and i can not even turn WiFi on. Am i doing something wrong or is there an easy fix? I do appreciate everything that is shared here. Also thanks for the fix to get JellyBam 7.0 to work.
I am on a Galaxy S3 i747 AT&T phone.
Thanks in advance,
Jason
Click to expand...
Click to collapse
A clean flash always causes the least issues, see if that fixes your problem
Sent from my PG06100 using xda premium
I tried the clean flash and didn't have any luck. I'm not quite sure about the whole "kernel" thing. I don't know where to go for kernels or how to pick one.
OK, and again thank you for your time and info on this thread. I did the clean flash and used the kernel that the person starting the thread spoke about. The 3252013 kernel 3.0 worked and WiFi is on and working. So far this seems to be the winner. I didn't have success with 3.4, just so others reading know.
Thanks again.
The 3.4 kernels are still being debugged and tested IIRC
I'm using TWRP and can't seem to flash the .zip.
Anyone using TWRP with success?
Update: Was able to flash latest 7.1.
An issue I've been noticing with ROMs including PA, is that animations are very choppy.
Anyone else notice this?
Jellybam roms are banned from XDA for using other people's work without giving credit or getting permission from other developers. Also the reason the v7 flash doesn't work is because the developer forgot to include a kernel in the zip you need to pull one from another thread and place it in the zip. Also might need the meta folder from a cm Rom, can't really remember
Sent from my Nexus 7
BigMan0nCampus said:
Jellybam roms are banned from XDA for using other people's work without giving credit or getting permission from other developers. Also the reason the v7 flash doesn't work is because the developer forgot to include a kernel in the zip you need to pull one from another thread and place it in the zip. Also might need the meta folder from a cm Rom, can't really remember
Sent from my Nexus 7
Click to expand...
Click to collapse
There's a new release that works.
Have any one of you tried the AxisM ROM, it was previously called GalaxyMOD I believe. I usually don't flash Universal ROMs, the only one I tried before this was Hyperdrive which I kinda liked but wanted to wait until the bugs are ironed out but I did give this ROM a try because I saw one of our dev (the awesome grue) on the team members list (team synergy).
The issue is the ROM doesn't boot at all, it's not stuck at samsung logo or anything, I see the samsung logo and it goes blank, nothing happens. Please let me know if any of you guys got it to work. Would be awesome if Grue can make it work for us since he is on their team as well.
Here is the link to the ROM.
http://forum.xda-developers.com/showthread.php?t=2089821
Try flashing a Sprint s3 kernel with it on your next flash, make sure you wipe everything (system, data, cache and dalvik).
Sent from my SPH-L710 using xda premium
I tried using the same rom but had no success getting it to boot and when It did boot I had all kinds of fc everywhere so I just nandroid back to my regular setup.
Sent from my SPH-L710 using Tapatalk 2
Vfan23 said:
Try flashing a Sprint s3 kernel with it on your next flash, make sure you wipe everything (system, data, cache and dalvik).
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Am I giving a shot at your suggestion (not that I mind, will try that now) or did you get it working that way?
Westcoastking said:
I tried using the same rom but had no success getting it to boot and when It did boot I had all kinds of fc everywhere so I just nandroid back to my regular setup.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
What kernel did you flash, if you did flash?
Invincible Madness said:
Am I giving a shot at your suggestion (not that I mind, will try that now) or did you get it working that way?
Click to expand...
Click to collapse
I just figured it wouldn't hurt to try. I haven't tried it but being it is Verizon branded but universal I figured flashing a kernel might help too. Never hurts to try though, just nandroid back if need be.
Sent from my SPH-L710 using xda premium
Vfan23 said:
I just figured it wouldn't hurt to try. I haven't tried it but being it is Verizon branded but universal I figured flashing a kernel might help too. Never hurts to try though, just nandroid back if need be.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Downloaded KT747 and now back to flashing again. I have a slimbean backedup anyway. Will report back if I get it working.
On a sidenote, if I do get it booting but like the other user said have FC's, what other good kernels for TW do we have as alternatives? Agat & Lean Kernel 2.9?
I guess I could try freeza's optimized stock kernel as well.
EDIT: Ok, Flashed AxisM zip, Selected Sprint option and the dev picks option for apps, unchecked reboot option, flashed KT747 latest (4-11 I think) and it booted fine. No FC's until now. Phone and data working, data is a bit slow than usual though. Haven't tested anything esle but it looks pretty sweet.
Glad you got it buddy.
Sent from my SPH-L710 using xda premium
Vfan23 said:
Glad you got it buddy.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
And right when I was almost high on AxisM listening to Deftones Tempest, SystemUI started FC'ing.
I'm gonna try few other kernel options over the day and see if anything works better.
Invincible Madness said:
And right when I was almost high on AxisM listening to Deftones Tempest, SystemUI started FC'ing.
I'm gonna try few other kernel options over the day and see if anything works better.
Click to expand...
Click to collapse
Damn. So close too.
Sent from my SPH-L710 using xda premium
What kernel did you flash, if you did flash?[/QUOTE]
I did what the other user did flashed latest KT kernel.
Sent from my SPH-L710 using Tapatalk 2
Westcoastking said:
What kernel did you flash, if you did flash?
Click to expand...
Click to collapse
I did what the other user did flashed latest KT kernel.
Sent from my SPH-L710 using Tapatalk 2[/QUOTE]
Yup, the latest KT. Do you have your headset mic working? People on the other end can't seem to hear me. Weird
You flashed an att rom here, anything is possible....but wouldnt it brick phone?
Forever Justice said:
You flashed an att rom here, anything is possible....but wouldnt it brick phone?
Click to expand...
Click to collapse
It's not an at&t only ROM. It's a universal ROM, like Hyperdrive that you can see on our forums. And I've been running it since yesterday morning and it's running pretty well. There is an another one called Synergy ROM, so 3 roms AFAIK that you can flash on any carrier S3.
Hello everyone, I've recently been given a T989D as a gift and have found limited amount of roms compatible. I have tried to flash AOKP MR1 and CM 10 with no luck. Device will boot up but setup and framework keep foreclosing. I have flashed these via TWRP 2.5 w/ a full wipe thanks to Infamous's Superwipe/cache. I prefer AOSP roms, so if anybody could give me some suggestions, it would be greatly appreciated. Currently on Northern lights.
Aphex33 said:
Hello everyone, I've recently been given a T989D as a gift and have found limited amount of roms compatible. I have tried to flash AOKP MR1 and CM 10 with no luck. Device will boot up but setup and framework keep foreclosing. I have flashed these via TWRP 2.5 w/ a full wipe thanks to Infamous's Superwipe/cache. I prefer AOSP roms, so if anybody could give me some suggestions, it would be greatly appreciated. Currently on Northern lights.
Click to expand...
Click to collapse
Have you tried just performing a full wipe from within TWRP? Not sure if it'll make a difference or not.
Otherwise, you could try redownloading the files, or when the settings are force closing, reboot to recovery, wipe caches and reboot.
Sent from my Samsung SGH-T989D using xda premium
skadude66 said:
Have you tried just performing a full wipe from within TWRP? Not sure if it'll make a difference or not.
Otherwise, you could try redownloading the files, or when the settings are force closing, reboot to recovery, wipe caches and reboot.
Sent from my Samsung SGH-T989D using xda premium
Click to expand...
Click to collapse
Yes, full wipe via TWRP, and have tried the superwipe method as well. So, CM10/AOKP is compatible with a T989D???
I've used Koodo roms on my T989, so I don't see why the reverse wouldn't work, at least with TouchWiz based roms. Not sure about aosp roms. I never used the scripts, don't think they are needed.
Sent from XDA app
Aphex33 said:
Yes, full wipe via TWRP, and have tried the superwipe method as well. So, CM10/AOKP is compatible with a T989D???
Click to expand...
Click to collapse
Yes they are definitely compatible, I've been on cm10/10.1 since the beginning. Try doing a cache win after installing and booting up one of those roms.
Sent from my Samsung SGH-T989D using xda premium
skadude66 said:
Yes they are definitely compatible, I've been on cm10/10.1 since the beginning. Try doing a cache win after installing and booting up one of those roms.
Sent from my Samsung SGH-T989D using xda premium
Click to expand...
Click to collapse
Thanks for the tips bro...I found it to be a gapps issue. I flashed a slimmed down gapps package and it booted up fine. :good:
Aphex33 said:
Thanks for the tips bro...I found it to be a gapps issue. I flashed a slimmed down gapps package and it booted up fine. :good:
Click to expand...
Click to collapse
Awesome. Enjoy AOSP!!
Sent from my Samsung SGH-T989D using xda premium