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
Related
Hey guys, as you may tell I'm newly registered, but have been looking for a solution for my problem for a while now.
I have the Sprint Galaxy S3 16GB and flashed CyanogenMod 10.0 along with the Ktoonsez kernel. Everything works perfectly, but when I open the camera, it says "Can't connect to the camera". The camera works when I re-flash the stock rom, so it's not a hardware issue.
I've followed this thread but my firmware is ZHFJ02 whick isn't any of the download options.
Thanks in advance for any answers.
kj4pvf said:
Hey guys, as you may tell I'm newly registered, but have been looking for a solution for my problem for a while now.
I have the Sprint Galaxy S3 16GB and flashed CyanogenMod 10.0 along with the Ktoonsez kernel. Everything works perfectly, but when I open the camera, it says "Can't connect to the camera". The camera works when I re-flash the stock rom, so it's not a hardware issue.
I've followed this thread but my firmware is ZHFJ02 whick isn't any of the download options.
Thanks in advance for any answers.
Click to expand...
Click to collapse
I would suggest to try to flash an M snapshot of CM10.1 and try to use the camera on that. I use CM10.1 as a daily ROM, its battery life for me has been just about the same as CM10 and I haven't found any bugs that concern me. It may be worth a shot just to see if the camera work on CM10.1. Good luck!
LakeSoccer2 said:
I would suggest to try to flash an M snapshot of CM10.1 and try to use the camera on that. I use CM10.1 as a daily ROM, its battery life for me has been just about the same as CM10 and I haven't found any bugs that concern me. It may be worth a shot just to see if the camera work on CM10.1. Good luck!
Click to expand...
Click to collapse
What snapshot do you use
Sent From My Rooted, S-OFF'd Blackberry Curve using the iOS XDA Application for Android.
LakeSoccer2 said:
I would suggest to try to flash an M snapshot of CM10.1 and try to use the camera on that. I use CM10.1 as a daily ROM, its battery life for me has been just about the same as CM10 and I haven't found any bugs that concern me. It may be worth a shot just to see if the camera work on CM10.1. Good luck!
Click to expand...
Click to collapse
I have flashed 10.1 snapshot, but no dice. I think it's more of a lack of firmware than the rom itself.
Whiplashh said:
What snapshot do you use
Sent From My Rooted, S-OFF'd Blackberry Curve using the iOS XDA Application for Android.
Click to expand...
Click to collapse
I am running the latest M snapshot which can be found here. Its date added is: 2013-01-21 02:18:19 and it is 163.46 MB.
kj4pvf said:
I have flashed 10.1 snapshot, but no dice. I think it's more of a lack of firmware than the rom itself.
Click to expand...
Click to collapse
Were you on Ktoonsez kernel? Also, what gapps are you flashing?
LakeSoccer2 said:
Were you on Ktoonsez kernel? Also, what gapps are you flashing?
Click to expand...
Click to collapse
I was on Ktoonsez for 10.1 as I am now, and I flashed the correct kernel for 4.2 because I triple checked before I flashed.
When I installed 10.1 I flashed the 20121212 gapps.
Right now, on 10.0, I'm using 20121011.
I got the gapps from roozwiki
I'm running the nightly cm10.1 with the stock kernel, and the camera is lovely.
sent from a secret underground bunker
kj4pvf said:
Hey guys, as you may tell I'm newly registered, but have been looking for a solution for my problem for a while now.
I have the Sprint Galaxy S3 16GB and flashed CyanogenMod 10.0 along with the Ktoonsez kernel. Everything works perfectly, but when I open the camera, it says "Can't connect to the camera". The camera works when I re-flash the stock rom, so it's not a hardware issue.
I've followed this thread but my firmware is ZHFJ02 whick isn't any of the download options.
Thanks in advance for any answers.
Click to expand...
Click to collapse
Per other suggestions, and not trying to browbeat you, but flashing to a newer better version of CM (10.1 M version) is a not too burdensome final solution to your problem.
But if you are loathe to do it for some unstated reason... nm.
HTH
Sconnie
Thanks guys. I will upgrade to 10.1 just with stock kernel to see if that fixes the problem. Just one more quick question, can I use the built in CM upgrade to upgrade directly or do I need to re-flash with the new gapps?
All help is greatly appreciated
Sent from my SPH-L710 using Tapatalk 2
I'm unfamiliar with the cm updater.
I use ROM manager to download and install updates, and I install the gapps every time.
ROM manager notifies me when a new nightly is available.
sent from a secret underground bunker
mjben said:
I'm unfamiliar with the cm updater.
I use ROM manager to download and install updates, and I install the gapps every time.
ROM manager notifies me when a new nightly is available.
sent from a secret underground bunker
Click to expand...
Click to collapse
I'm having the same issue but it's happens on other rooms as well.
Any suggestions
Well I updated to 10.1 experimental but the camera still isn't working. MMS isn't working either. thanks for all the support in advance.
Sent from my SPH-L710 using Tapatalk 2
kj4pvf said:
Well I updated to 10.1 experimental but the camera still isn't working. MMS isn't working either. thanks for all the support in advance.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
How are you at wiping partitions and flashing zips?
Personally, I would mount and format the system partition, then install the cm zip and gapps. Wipe you're caches and then I would expect everything to work fine.
Remember, always make a nandroid backup!
sent from a secret underground bunker
Well what I've been doing is:
1. Go into clockwork and wipe data and cache partition
2. Wipe cache partition just to be safe
3. Wipe dalvik
4. Flash rom then gapps and restart.
That's how I've been doing it this whole time
Sent from my SPH-L710 using Tapatalk 2
Ok, that sounds basically OK. You probly don't need to wipe your data, at least not right away.
Before flashing the ROM and gapps, go to mounts and storage, then mount system, format system, then flash ROM and gapps.
I wouldn't bother wiping data unless I had more problems afterwards.
sent from a secret underground bunker
I did what you recommended but it still didn't work. As an interesting side note, the partitioning is a little odd. All my personal info and downloads are in a sub folder called /0/ Just wondering if that's normal
Sent from my SPH-L710 using Tapatalk 2
kj4pvf said:
I did what you recommended but it still didn't work. As an interesting side note, the partitioning is a little odd. All my personal info and downloads are in a sub folder called /0/ Just wondering if that's normal
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
The 0 folder is normal, from JB and up all data is stored there (why, I dont know)
Sent from my PG06100
mjben said:
Ok, that sounds basically OK. You probly don't need to wipe your data, at least not right away.
Before flashing the ROM and gapps, go to mounts and storage, then mount system, format system, then flash ROM and gapps.
I wouldn't bother wiping data unless I had more problems afterwards.
sent from a secret underground bunker
Click to expand...
Click to collapse
I've tried all suggestions listed on this to fix the same issue on any ROM's I use. Would there be a mod or something out there that I could flash to replace it. All I get is a failed to connect to camera.
I dunno man. You may consider going 100% stock and cleaning up any signs of root and flashing and then, if the camera still isn't working, take then phone back to Sprint and see about exchanging it.
sent from a secret underground bunker
mjben said:
I dunno man. You may consider going 100% stock and cleaning up any signs of root and flashing and then, if the camera still isn't working, take then phone back to Sprint and see about exchanging it.
sent from a secret underground bunker
Click to expand...
Click to collapse
The camera works 100% in stock, even when rooted and with a custom kernel, the camera works with the stock rom.
Must be a firmware issue.
Hey guys between this two builds i want to know what's the difference?? Cause i really don't see it. Maybe some tweaks or settings?
Can you guys explain to me which one is better and why?
daworship said:
Hey guys between this two builds i want to know what's the difference?? Cause i really don't see it. Maybe some tweaks or settings?
Can you guys explain to me which one is better and why?
Click to expand...
Click to collapse
Whichever one works better for you. There are different customizations for each ROM, but it's up to you to decide which one works better for your needs.
Sent from my Samsung SGH-T989D using xda premium
I keep getting stuck in a boot loop with all the updates of 10.1 Nightly, the only one I didn't get looped in was the original. I even did a full wipe and everything, help anyone?
kvarug01 said:
I keep getting stuck in a boot loop with all the updates of 10.1 Nightly, the only one I didn't get looped in was the original. I even did a full wipe and everything, help anyone?
Click to expand...
Click to collapse
I never have that issue even with dirty flash. Have you tried to wipe system, data, everything? I think you can try to Odin back to stock, then root it and start everything fresh. Sometimes the old files are still left over and mess up your phone.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Alarmmy said:
I never have that issue even with dirty flash. Have you tried to wipe system, data, everything? I think you can try to Odin back to stock, then root it and start everything fresh. Sometimes the old files are still left over and mess up your phone.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
The sad thing is, that's all I've been doing. Using Odin and keep going back to stock, update to ICS with Kies, and then hope to try and run another version of the ROM, and still no luck. It's quite frustrating. And yeah, I wiped system, data, everything. Did a full on wipe.
Also, has anyone have been getting call issues? Like you sound muzzled to your callers?
kvarug01 said:
Also, has anyone have been getting call issues? Like you sound muzzled to your callers?
Click to expand...
Click to collapse
Here is solution for your issue:
1. Upgrade recovery, or switch to TWRP.
2. Clean flash rom again.
3. Flash the newest radio UVLI4, or LI1.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Download darkside super wipe.zip ...flash it and then flash your rom+gapps... Hit thanks
Sent from my SGH-I897 using xda premium
sam.balia1012 said:
Download darkside super wipe.zip ...flash it and then flash your rom+gapps... Hit thanks
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
DO NOT do that if you are on the latest TWRP or CWM 6.+ cause Darkside super wipe was discontinued. For AOKP and CM 10.1 Nightly I just did a data/partition wipe and flash gapps.
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.
Ok guys, these are modded versions of TDJ's tools to add the preload partition. This should allow you to wipe cache and dalvik without jacking up the symlinks. Also for you guys having issues installing a ROM, the superwipe should fix that. First flash the ROM and reboot (important), then if you are having issues flash the super wipe and then the ROM again. Reboot and you should be good.
Thanks again TDJ!!! You rock bro.
Note to other developers: Feel free to link here from your thread, just don't re-upload them please. Thanks
Everyone else: if you see these uploaded anywhere else please let me know. I have no problem with others linking to these but do not want them uploaded anywhere else.Thanks
Saved. . . . . . .
One more. . . . . .
I'm awesome
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
thx for this, i was annoyed by the preload problem.
Is this for CWM recovery or TWRP as well?
Sent from my SGH-T989 using xda app-developers app
Will work for both.
Thanks Jamison this will solve alot of headaches!
So whenever we want to wipe cache/dalvik use zip file instead of built in twrp??
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
euklid said:
So whenever we want to wipe cache/dalvik use zip file instead of built in twrp??
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
If on a TMo based 4.1.2 ROM, yes.
Whats the difference between the two downloads?
inpherknow said:
Whats the difference between the two downloads?
Click to expand...
Click to collapse
One is cache/dalvik, superwipe is data/factory reset.
Well before using the scripts ROM would not boot but after super wipe no problems, TWRP 2.5.0.0 :thumbup:
Sent from my SGH-T989 using xda premium
Jamison-does the cache wipe also fix permissions?
Sent from my SGH-T989 using xda app-developers app
Yes it does.
Sent from my dark hole called an office.
I used these scripts installing a ROM and I am having very serious issues. I was using Clockwork and when I rebooted I got stuck in a boot loop. I booted back into recovery but I was not getting fully back into recovery. I tried several times. I finally ODINed back to stock but I can't get the ****ing phone to boot up. It gets toa popup that says ""unfortunatley google partner setup has stopped" and then if I clear that "Google account manager has stopped", "google calender storage has stopped""unfortuantely the process com. android.phone has stopped". ****. I have tried ODIN to 3.5 stock and 4.0.3 both having similar issues.
Anyone have any idea, may have absolutley nothing to do with these scripts but any ideas would be very much appreciated.
What are you running and what are you trying to flash? Wouldn't be the scripts as they only wipe, format, align the partitions.
Sent from my dark hole called an office.
Jamison904 said:
What are you running and what are you trying to flash? Wouldn't be the scripts as they only wipe, format, align the partitions.
Sent from my dark hole called an office.
Click to expand...
Click to collapse
I was running CWM 6.0.2.9 touch and trying to flash the StockWalk ROM. I don't know if you have seen something like this before but it seems like I am totally unable to install any GAPPS even when flashing stock ROM in ODIN. I had flashed the same ROM before attempting to use the scripts, the reason was that I was unable to add my google account (may be a defect in the ROM but others are saying they have not had issue).
*when I say install GAPPS I am just refering to the ones that install on TW ROMS, I am not flashing a GAPPS file of any kind
ArcticFish said:
thx for this, i was annoyed by the preload problem.
Click to expand...
Click to collapse
blackangst said:
If on a TMo based 4.1.2 ROM, yes.
Click to expand...
Click to collapse
OK so I thought I knew enough to not feel like a noob, but here I am with three questions.
First question is what is a "preload problem"?
Second question is this will only work on 4.1.2, and not 4.2.2 (CM 10.1)?
And the third question is will using the original DS wipes mess something up?
T mobiles 4.1.2 loads a preboot partition. Wiping cache with anything but these scripts also wipes these partitions. This script is modified to not do that. No preboot partition = boot loop.
Thus, if you're on anything BUT Tmobiles 4.1.2 you don't need this script and there's no advantage to using it.
Sent from my SGH-T989 using xda app-developers app
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.