http://get.cm/?device=d2att
JB 4.3 CyanogenMod 10.2
Sent from my SAMSUNG-SGH-I747 using xda premium
oriveradel said:
http://get.cm/?device=d2att
JB 4.3 CyanogenMod 10.2
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Going to flash this weekend.
I found I had to flash a new gapps to get the play store working. I also had to uninstall and reinstall several apps that were force closing or not loading. But otherwise it seems to be as stable as 10.1.x for me.
I could not successfully flash back to any 10.1.x version (at least without doing a factory wipe) and I had actually flashed to 10.2 by accident (thinking it was a 10.1 nightly). So make sure to backup before you go ahead.
I'm also sad to see I'm still getting a runaway usb_otg process after disconnecting from a computer USB port requiring a reboot. Hopefully this will be fixed soon. The connected to USB notification also remains active sometimes after disconnecting.
tmagritte said:
I found I had to flash a new gapps to get the play store working. I also had to uninstall and reinstall several apps that were force closing or not loading. But otherwise it seems to be as stable as 10.1.x for me.
I could not successfully flash back to any 10.1.x version (at least without doing a factory wipe) and I had actually flashed to 10.2 by accident (thinking it was a 10.1 nightly). So make sure to backup before you go ahead.
I'm also sad to see I'm still getting a runaway usb_otg process after disconnecting from a computer USB port requiring a reboot. Hopefully this will be fixed soon. The connected to USB notification also remains active sometimes after disconnecting.
Click to expand...
Click to collapse
If you make clean flashing a religion you wouldn't run into any problems.... clean flashed every nightly and never experienced 98 percent of problems others have had.
Whats the main difference between 4.2 and 4.3?
---------- Post added at 11:21 PM ---------- Previous post was at 11:13 PM ----------
I mean is it worth going through it and dealing with the bugs if we have a 4.2 thats working great?
I flash this yesterday but keyboard dosnt work :/
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
woot! 4.3!
Yay for new versions...time for yet another full wipe and flash...
Anyone know yet how stable this is?
Installed the first Nightly from the 14th.
I had similar issues with GAPPS. Had to upgrade to most recent.
Overall, its a nice build. I am still having issues with phone reboots every so often. Only seems to happen when I am using GPS and BlueTooth
i.e. on my commute home. But the reboots are so fast, they may occur at other times when I don't have the phone up in my view.
Happy that I upgraded none the less.
Nice cant wait to try it out. I heard there are problems with the camera though.
Sent from my SGH-I747 using xda app-developers app
DexedrineXR said:
If you make clean flashing a religion you wouldn't run into any problems.... clean flashed every nightly and never experienced 98 percent of problems others have had.
Click to expand...
Click to collapse
you clean flash every nightly? what a huge pain in the ass. at most i clean flash once a month or so, anything more defeats the purpose of customizing your setup since you have to keep redoing everything.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
dLo GSR said:
you clean flash every nightly? what a huge pain in the ass. at most i clean flash once a month or so, anything more defeats the purpose of customizing your setup since you have to keep redoing everything.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
If you make a backup of your data partition, you can clean flash, restore your data partition, and be fully up and running in 10 minutes.
tokuzumi said:
If you make a backup of your data partition, you can clean flash, restore your data partition, and be fully up and running in 10 minutes.
Click to expand...
Click to collapse
Except that ain't really a clean flash. :silly:
polobunny said:
Except that ain't really a clean flash. :silly:
Click to expand...
Click to collapse
He's not talking about system data, he's probably talking about just your apps. I'd rather take an extra five minutes to make sure I have no problems than run into problems.
Related
Hello all. I wish I could post this in the actual thread, but I am a new user with less than 10 posts haha! But I am having an issue with Paranoid Android ROM booting. I have tried like every way imaginable. Here is the logcat form my phone: h t t p :// pastebin.com/mukxdDDM. So does anyone have any sort of idea as to what is goin on? I'm starting to learn my way around Android code and I still don't have much of a clue. Thanks for your help!
Flash cm9 sign in the works.. I then wipe everything format system and flash are u on mtd or what?
Sent from my SPH-D700 using xda premium
I'm having the same problem, friend.
I am. I have been on cm9 for a long time. I tried flashing cm9 clean first and flashing PA but to no avail.
I had this problem when I tried restoring to the paranoid. I fixed it by clean installing aokp with nyan v5, then clean installing paranoid and Google apps nothing else in twrp recovery and it booted. It should work in cwm also but I have not used cwm for a while because twrp is easier although a bit buggier.
My recommendation would be odin back to stock and then odin cwm and flash
I got it to boot once, but it was missing the notification bar. I redownloaded it, but now it gets stuck at the boot animation, and the phone gets warm to the touch.
Edit: Tried CM9 first twice after fully wiping. I hope to get this working, because it looked pretty cool...
WBaumgartner said:
I got it to boot once, but it was missing the notification bar. I redownloaded it, but now it gets stuck at the boot animation, and the phone gets warm to the touch.
Edit: Tried CM9 first twice after fully wiping. I hope to get this working, because it looked pretty cool...
Click to expand...
Click to collapse
Not sure why there are so many problems just to get it to boot. If one way works for the majority of people, shouldn't it work for everyone if the steps are followed exactly?
Sent from my SPH-D700 using xda app-developers app
Nope...too many variables. Every phone is different, bad downloads, bad flashes. If everyone Odin'd to FC09 stock then rooted with cwm 5.0.2.7 then flashed CM9 98% would be fine but still 2% would have trouble.
Sent from my SPH-D700 using xda premium
Ah ok. Thats a bit disappointing haha.
Sent from my SPH-D700 using xda app-developers app
Just in case anyone stumbles upon this thread, the booting issue for this ROM has been solved by the ROM porter. Anything passed the June 30 build has this issue resolved.
Also, anyone willing to help me with another issue? Or should I start a new thread? I want to post all these in the main thread, but I can't for 5 more posts. My issue is that I can get this whole ROM running, but I have no statusbar at all. I am not sure why. Can anyone be of assistance?
JustKojack said:
Also, anyone willing to help me with another issue? Or should I start a new thread? I want to post all these in the main thread, but I can't for 5 more posts. My issue is that I can get this whole ROM running, but I have no statusbar at all. I am not sure why. Can anyone be of assistance?
Click to expand...
Click to collapse
Just keep posting here and you'll have the post you'll need
Sent from my SPH-D700 using XDA Premium App
Thanks! But I have no statusbar while running the Paranoid Android ROM. And I'm not really sure why. Any help?
JustKojack said:
Thanks! But I have no statusbar while running the Paranoid Android ROM. And I'm not really sure why. Any help?
Click to expand...
Click to collapse
Which one of the updates did you flash? Most likely you got a bad download.
Sent from my SPH-D700 using XDA Premium App
masaidjet said:
Which one of the updates did you flash? Most likely you got a bad download.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
I got the June 30 download. I now flashed cm9 and then PA and I have statusbar. Not sure why.
JustKojack said:
I got the June 30 download. I now flashed cm9 and then PA and I have statusbar. Not sure why.
Click to expand...
Click to collapse
Did you do a clean wipe ? Sometimes when wipes aren't performed things like no statusbar happen. And until the dev work out the kinks I would stay away from the rom. I really like Paranoid Android myself
sent via brain
masaidjet said:
Did you do a clean wipe ? Sometimes when wipes aren't performed things like no statusbar happen. And until the dev work out the kinks I would stay away from the rom. I really like Paranoid Android myself
sent via brain
Click to expand...
Click to collapse
I just did a full wipe, installed june 30th build and no status bar for me either, I will try installing over cm9 and see what happends.
Jshugzda said:
I just did a full wipe, installed june 30th build and no status bar for me either, I will try installing over cm9 and see what happends.
Click to expand...
Click to collapse
The way I did it was full wipe including wiping /system, then I installed cm9 and correct gapps, then did not install any extra apps, then installed PA and correct gapps, and all went well!
masaidjet said:
Did you do a clean wipe ? Sometimes when wipes aren't performed things like no statusbar happen. And until the dev work out the kinks I would stay away from the rom. I really like Paranoid Android myself
sent via brain
Click to expand...
Click to collapse
I did and full wipe and no statusbar, but then i did cm9 and it worked! haha! I am loving PA though! And once you get it to be a stable booting rom it so far is working well.
I'm running [ROM][28 Aug] [UVALH2 v37] XquiziT TMO ONLY!...
Whenever I turn on my phone, I get: Android is Upgrading... Starting Applications.
Although I don't think it affects the phones performance... it started happening after flashing Wildchild's ROM.
Of course, I have Wiped data, Dalvik, cache... and re-downloading, reflashing.
I also tried Wildchild's Superwipe [wipes EVERYTHING].
Some see it completely normal [SEE THIS POST], while others think it's not normal.
Any enlightening will be appreciated.
could it be updating your apps and checking for ota, abd that why it says that a boot up?
Why does it bother people so much? It isn't a big deal and it isn't affecting performance save boot up time but honestly how often does your phone boot?
Sent from my SGH-T999
is your dalvik\cache being wiped before rebooting?
Cobra281 said:
is your dalvik\cache being wiped before rebooting?
Click to expand...
Click to collapse
Same thing was happening to me on that Rom, but only after odexing.. never hurt anything but was annoying
Sent from my SGH-T999 using Tapatalk 2
joshnichols189 said:
Why does it bother people so much? It isn't a big deal and it isn't affecting performance save boot up time but honestly how often does your phone boot?
Sent from my SGH-T999
Click to expand...
Click to collapse
I know itd bug the hell outa me! Even if it were running great, I'd still know that underneath it all, something was wrong! I just cant stand that personally.
Not sure whats causing this for some folks. Ill try to help out more a bit later.
Sent from my SGH-T999 using xda app-developers app
It sounds like its wiping dalvik on every boot for some reason. I would try reflashing and if that doesn't work try flashing a different rom.
DocHoliday77 said:
I know itd bug the hell outa me! Even if it were running great, I'd still know that underneath it all, something was wrong! I just cant stand that personally.
Not sure whats causing this for some folks. Ill try to help out more a bit later.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
What? Nothing is wrong.
Well, its not exactly behaving the way that it should. Its rebuilding dalvik every boot. Not supposed to do that, so if its not acting right.......
Additionally, (and I know this isnt a very big deal, but to others it is) thats a lot of extra writing that is totally unnecessary.
Sent from my SGH-T999 using xda app-developers app
Cobra281 said:
is your dalvik\cache being wiped before rebooting?
Click to expand...
Click to collapse
It's not... I don't think it is. No apps are being updated: 1 out of 85
It just says "Starting Applications"
nothing else.
DocHoliday77 said:
I know itd bug the hell outa me! Even if it were running great, I'd still know that underneath it all, something was wrong! I just cant stand that personally.
Not sure whats causing this for some folks. Ill try to help out more a bit later.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Thanks! And like the post I linked... some people have experienced it since they got the phone out of the box. Weird.
Slurpee7600 said:
It sounds like its wiping dalvik on every boot for some reason. I would try reflashing and if that doesn't work try flashing a different rom.
Click to expand...
Click to collapse
I flashed and reflashed with triple wipe [internal SD/system/etc]
I guess I'll try a diff ROM. I'm just happy with the current ROM though.
Have you flashed any mods or themes?
Just a shot in the dark, but heres a couple things you could try.
Install the deodexed UVALH2 rom, see if it still happens. If it does try to use Odin to flash the pure stock (will lose root). If it still happens I would try a different release at that point, just to narrow it down.
If it stops happening try flashing xquizit over top of the full version and see if it starts again.
Something else to try is use a different recovery. If you're still up for troubleshooting at that point!
How did you update to UVALH2 in the first place? Did you flash one of the rooted versions, or did you update with the full firmware or ota via Odin?
Like I said, its a shot in the dark, but im just wondering if something happened or got left behind when you updated.
Sent from my SGH-T999 using xda app-developers app
---------- Post added at 09:31 AM ---------- Previous post was at 09:25 AM ----------
HG! said:
It's not... I don't think it is. No apps are being updated: 1 out of 85
It just says "Starting Applications"
nothing else.
Sorry, missed that a minute ago. Can you get a logcat? Youll have to conect to your computer and run it at boot. Dont want to try to guide you through that from memory but there should be some good guides here on xda if you dont know how.
I flashed and reflashed with triple wipe [internal SD/system/etc]
I guess I'll try a diff ROM. I'm just happy with the current ROM though.
Click to expand...
Click to collapse
Did you try using Wilds Superwipe?
Sorry I know its a lot but wanted to throw out any ideas before going back to work. Hope some of this helps!
Sent from my SGH-T999 using xda app-developers app
Dalvik?
This happened to me after I did a Dalvik wipe while in recovery. That is the only time it happened. For a minute, I thought I lost root. Have reboot many times and have not seen it. Mine goes to 205 applications though.
IrieBro said:
This happened to me after I did a Dalvik wipe while in recovery. That is the only time it happened. For a minute, I thought I lost root. Have reboot many times and have not seen it. Mine goes to 205 applications though.
Click to expand...
Click to collapse
Because it happens when the phone is rebuilding caches and goes by the number of apps you yourself have installed..
Sent from my SGH-T999
same thing happens to me, im using v50 and used childs superwipe.. i also tried installing a battery theme and it's been doing that since then..
it's annoying and i really wanna remove it too but i rarely reboots..
DocHoliday77 said:
Have you flashed any mods or themes?
Just a shot in the dark, but heres a couple things you could try.
Install the deodexed UVALH2 rom, see if it still happens. If it does try to use Odin to flash the pure stock (will lose root). If it still happens I would try a different release at that point, just to narrow it down.
If it stops happening try flashing xquizit over top of the full version and see if it starts again.
Something else to try is use a different recovery. If you're still up for troubleshooting at that point!
How did you update to UVALH2 in the first place? Did you flash one of the rooted versions, or did you update with the full firmware or ota via Odin?
Like I said, its a shot in the dark, but im just wondering if something happened or got left behind when you updated.
Sent from my SGH-T999 using xda app-developers app
---------- Post added at 09:31 AM ---------- Previous post was at 09:25 AM ----------
Did you try using Wilds Superwipe?
Sorry I know its a lot but wanted to throw out any ideas before going back to work. Hope some of this helps!
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Yeah... I did the Superwipe.
:crying:
Its also happen to me and i dont find a fix for it yet, its annoying that i see it everytime i reboot my phone,
HG! said:
I'm running [ROM][28 Aug] [UVALH2 v37] XquiziT TMO ONLY!...
Whenever I turn on my phone, I get: Android is Upgrading... Starting Applications.
Although I don't think it affects the phones performance... it started happening after flashing Wildchild's ROM.
Of course, I have Wiped data, Dalvik, cache... and re-downloading, reflashing.
I also tried Wildchild's Superwipe [wipes EVERYTHING].
Some see it completely normal [SEE THIS POST], while others think it's not normal.
Any enlightening will be appreciated.
Click to expand...
Click to collapse
pretty sure wild child's builds have the ROM fix perms each time you boot. this is the cause of this message. don't worry, you are fine.
Mine just came back to normal and i dont see it anymore. Also i think my phone boot faster than the normal.
Sent from my GT-I9300 using xda premium
It's usually from an odex file being put into a deodexed Rom find that file and delete it and you should be fine.
Sent from my SGH-T999
Hi there!
I have had an s3 for a few days now and love it!.
Any TW rom and my camera works just fantastic.
Any cm10/aokp/miui/etc rom and I just cant use the camera no matter what app I use to try it, whether it be the built in app or camera360/etc.
Driving me nuts and would love someone to help me. Anyway research I have done hasnt told me what I'm doing wrong.
I wipe cache/dalvik/factory reset/system before each rom. I have tried different kernels but nothing has helped.
Any gurus out there have any ideas on what I can do to fix this?
Your install process would be and please link the files you are flashing... I'll try and help you. I've seen a few people mention this the past couple days.
The most recent I tried to flash was Illusion v1.1.18 - (d2tmo, d2att & d2vzw) - 1|18|13 from this thread:
http://forum.xda-developers.com/showthread.php?t=2037028
I downloaded Illusion-v1.1.18-d2tmo.zip and gapps-jb-20121212-signed.zip.
I went into recovery which is twrp and the most recent version. I installed it with the goo.im app.
When in recovery I did:
1) Factory Wipe
2) Wipe Cache
3) Wipe Dalvik
4) Wipe System
I would then click Install and select the rom file, and after it succesfully flashed I would then flash the gapps file. All were successful.
I would then reboot and the rom would boot up fine. I setup my google account and all that then for the heck of it I would reboot.
I then would try the camera app and it would complain that it couldnt connect to the camera basically. I went into the play store and tried a free version of camera 360, puddle camera, etc and all would not work.
I went back into recovery, wiped cache and dalvik again, hopped on one foot, faced east, and clicked my heels together. Upon reboot the camera does not work.
I have wiped all that and tried to install [Kernel][JB] Leankernel: Minimalistic Kernel for D2TMO/D2ATT (AOSP) v2.3 [1/17/13] which flashed fine. Upon reboot I could change voltages to undervolt, mess with governors but cameras still do not work.
I have a backup of two TW roms (one stock) and both of the those roms work beautifully with whatever camera I try, including the built in/stock camera.
I hoped I didn't leave out something. If there is something I missed than I'm an idiot because it seems like I am really missing something.
Thanks for your help.
I don't see any reason your steps lead to that, the exact steps I take every time to flash. I'm researching but in the mean time, go to app manager and wipe cache and data from gallery... Are you using the same Gapps over and over on each try? Might wanna try a different set.
mt3g said:
I don't see any reason your steps lead to that, the exact steps I take every time to flash. I'm researching but in the mean time, go to app manager and wipe cache and data from gallery.
Click to expand...
Click to collapse
I did that earlier with no luck.
I just force stopped on gallery, wiped cache/data, rebooted, and I tried the camera only to get the same message.
Thank you for that tip but I will continue my research also.
Just because I looked at about phone.
Model of phone is SGH-T999 (just in case someone thinks I'm in the wrong forum"
Baseband version is T999UVDLJA
Kernel is of course 3.0.59-leanKernel
AOKP Version is Illusion v1.1.18 d2tmo
Build number is aokp-d2tmo-userdebug 4.2.1 (I truncated the rest)
mt3g said:
Are you using the same Gapps over and over on each try? Might wanna try a different set.
Click to expand...
Click to collapse
I have downloaded this gapps twice for the last rom http://goo.im/devs/itsmikeramsay/gapps-jb-20121212-signed.zip.
For the miui rom there was a gapps that was specific to miui and had miui in the name. The miui rom's camera didnt work.
I'll look for a different gapps if that might be the problem but since I have tried a couple roms and a few different gapps I feel that might not be the issue.
I still will give it another try though. Just have to find another gapps to try.
try these just in case they're corrupted. http://d-h.st/dtk these are the ones I use
mt3g said:
try these just in case they're corrupted. http://d-h.st/dtk these are the ones I use
Click to expand...
Click to collapse
I redid the entire install process from scratch using that gapps and the camera is still not working.
Ugh. Thanks for the link.
WIll keep trying :/
run a log cat and post it. Other then that maybe bad firmware...
did you update your phone to stock JellyBean via Over the Air or Odin? it updates the partitions which could be the issue, mmayyybbeee???!?!? Shots in the dark right now, just trying to help as I've never seen this issue before solved.
mt3g said:
run a log cat and post it. Other then that maybe bad firmware...
did you update your phone to stock JellyBean via Over the Air or Odin? it updates the partitions which could be the issue, mmayyybbeee???!?!?
Click to expand...
Click to collapse
It had JB on it when I got it almost 2 days ago. I tried to do an OTA when I got it but it said I was up to date.
Let me do a restore to stock and see what version it is.
Edit: Restored stock. Says android version 4.1.1, Kernel 3.0.31-370274se.infra, Build number JR003L.T999UVDLJA
Was it already rooted?
Sent from my SGH-T999 using xda premium
mt3g said:
Was it already rooted?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
It was new, out of the box. I watched the guy unrap it. It is one of the newer grey metal color looking ones. It was not rooted. I did that. Should I do an Odin to bring the device back to complete stock and start from scratch?
Will take a while since I have no idea where to start with all that
Thats the best suggestion I have. Maybe someone else will step in with an idea.
Sent from my SGH-T999 using xda premium
mt3g said:
Thats the best suggestion I have. Maybe someone else will step in with an idea.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
You have been helpful. In a bit ill reflash a cm/aokp rom and logcat it.
This is happening a couple of threads above you haha http://forum.xda-developers.com/showthread.php?p=36899130
Sent from my SGH-T999 using xda premium
mt3g said:
This is happening a couple of threads above you haha http://forum.xda-developers.com/showthread.php?p=36899130
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Hey thanks again for your help. I ended up falling asleep but installed Wicked V6 (tw based rom) and liking it enough that I will wait on a aokp/cm10.x rom until I get up the motivation to try again.
I'm sure I'll get an itch for a different rom in about a week though
dccoh said:
Hey thanks again for your help. I ended up falling asleep but installed Wicked V6 (tw based rom) and liking it enough that I will wait on a aokp/cm10.x rom until I get up the motivation to try again.
I'm sure I'll get an itch for a different rom in about a week though
Click to expand...
Click to collapse
All good, just hope the thread I pointed to will work out once you do want to give it another go.
Sent from my SGH-T999 using xda premium
mt3g said:
All good, just hope the thread I pointed to will work out once you do want to give it another go.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I backed up Wicked and loaded up my original rom that I wanted to try.
The fix in the said thread fixed me right up, camera works fine.
All this trouble because of one 350ish kb file
Thanks for checking on my issue.
dccoh said:
I backed up Wicked and loaded up my original rom that I wanted to try.
The fix in the said thread fixed me right up, camera works fine.
All this trouble because of one 350ish kb file
Thanks for checking on my issue.
Click to expand...
Click to collapse
Most definitely sir. I don't understand why that file was getting screwed over. Glad it all got worked out for you.
Sent from my SGH-T999 using xda premium
Well, I don't know if this is how I'm supposed to go about doing this, but I've been having issues recently with Quantum rom, and was planning on posting them in the actual Quantum thread, but I need 10 posts to do that because 10 posts mean something important.
Anyways, Ive been fine previously just doing
1. Wipe Dalvik, cache, and system,
2. flashing rom and gapps
3. the wipe option you get after you flash (TWRP)
Ive been doing that since i started basically, until 1.9. Anything after 1.9, it either constantly crashes, has processes constantly stopping, or on one of the versions (2.1 i think) the screen would constantly flicker (which someone else mentioned happening in the thread). So i figured I should try a clean flash, so I try wiping everything and flashing, and doing the default factory reset option and flashing, neither of which helped. In fact, after doing the clean flash it made 1.9 stop working too, so I had to restore my 1.9 backup to get it working again.
Anywho, if anyone has any advice that could help me get the newer versions working that would be great, Thanks!
EDIT: I might try flashing a different rom, to see if the issues persist elsewhere, but firstly Id like to stay on Quantum, and secondly, iirc I tried one a different rom when 4.3 first started showing up in roms, and I kept having problems, to which I just went back to Quantum.
It sounds to me you have a bad download. Have you tried re-downloading the ROM? I run the Quantum ROM and I have had no issues whatsoever.
I'm also looking forward to your reply about flashing another ROM.
Sent from my SAMSUNG-SGH-I497 using Tapatalk
codemonkey98 said:
It sounds to me you have a bad download. Have you tried re-downloading the ROM? I run the Quantum ROM and I have had no issues whatsoever.
I'm also looking forward to your reply about flashing another ROM.
Sent from my SAMSUNG-SGH-I497 using Tapatalk
Click to expand...
Click to collapse
Well, I've tried flashing every version including and after 2.0, up to the current version, and have the same problems for each one. So i somewhat doubt that that's the problem. Ill probably try to flash somethign else some time tomorrow
DanCardin said:
Well, I've tried flashing every version including and after 2.0, up to the current version, and have the same problems for each one. So i somewhat doubt that that's the problem. Ill probably try to flash somethign else some time tomorrow
Click to expand...
Click to collapse
Could be your recovery too. I believe the Quantum ROM developer recommends CWM than TWRP.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
If you do decide to change to CWM, make sure you revert to your TouchWiz backup first since TWRP and CWM backups aren't compatible. My best recommendation is to re-download the newest version (2.35 as of 11/7/13), and wipe data/factory reset, wipe /cache, wipe system, wipe dalvik cache, then install ROM and Gapps, wipe cache and dalvik again, and reboot.
iirc, i noticed a fair enough number of people on TWRP that I would prefer to stay on it (since it *should* work). I did, however just update it, tried again. For 2.31, i just get constant for closes on phone and SystemUI, and others iirc. Im trying carbonRom right now, and its working perfectly fine.
EDIT: I did get one SystemUI force close, on it, but its literally constant on quantum sadly.
also tried a couple random other roms, all work, but no Quantum rom will work after 1.9. I also tried just flashing it and not gapps, and i end up with the same thing. Now its just constant force closes though. I don't think i remember seeing any flickery screens like i was getting around 2.1X i think it was.
What bootloader and firmware are you using with the later quantum ROMs.... I believe that the more recent ones need the dmg2 or emj2 boot and firmware to run properly.... Also what were your settings in trickster did you disable mp-dec and UV... Were you OC using stock quantum kernel etc.
Sent from my SGH-I747 using XDA Premium 4 mobile app
android_geek_0507 said:
What bootloader and firmware are you using with the later quantum ROMs.... I believe that the more recent ones need the dmg2 or emj2 boot and firmware to run properly.... Also what were your settings in trickster did you disable mp-dec and UV... Were you OC using stock quantum kernel etc.
Sent from my SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I think that the leaked 4.3 bootloader (whatever end code they gave it) isn't necessary yet, since it hasn't been officially released by AT&T. I'm personally holding off on flashing any 4.4 rom until they're a bit more mature and don't have as many hiccups (although pwncake's work is superb). The UV depends on your device and how it handles it, usually, mine needs +25 than stock but it doesn't seem to shorten battery life. All throughout 4.3, it was best to keep MP-Decision off since he built one into the rom. In the case of 4.4, IIRC from Quantum v3 beta3 and forward, he removed his own MP- Decision, so you could keep it switched on.
android_geek_0507 said:
What bootloader and firmware are you using with the later quantum ROMs.... I believe that the more recent ones need the dmg2 or emj2 boot and firmware to run properly.... Also what were your settings in trickster did you disable mp-dec and UV... Were you OC using stock quantum kernel etc.
Sent from my SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just flash the ROM and boot. If I should be flashing a seperate firmware slash bootloader, I'm not (and never have to my knowledge). I couldnt have gotten to the trickster settings if i wanted to due to the constant force closes.
Would anyone know why when I enable ART mode on Quantum 4.4 Beta3 Rom, my phone continually has pop up messages with unexpected errors? -Such as calendar storage issues or the google keyboard(This should probably be in the ROM section but I can't write there.)
DanCardin said:
I just flash the ROM and boot. If I should be flashing a seperate firmware slash bootloader, I'm not (and never have to my knowledge). I couldnt have gotten to the trickster settings if i wanted to due to the constant force closes.
Click to expand...
Click to collapse
Can't run Quantum either. Same boat. I think it's an issue with the Core kernel and Rev0 processors.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I tried flashing the new beta 8 of v3, and it worked with the odd restart and FC on the side. But the restarts were starting to get a bit annoying so I tried reflashing, and now I just get infinite boot animations no matter what I do. And if I try to restore my nandroid backup, there's this flash every 2 or 3 seconds around the boot animation. Sigh
EDIT: actually, completely reflashing works, but still ends up with the random reboots when doing random things
DanCardin said:
I tried flashing the new beta 8 of v3, and it worked with the odd restart and FC on the side. But the restarts were starting to get a bit annoying so I tried reflashing, and now I just get infinite boot animations no matter what I do. And if I try to restore my nandroid backup, there's this flash every 2 or 3 seconds around the boot animation. Sigh
EDIT: actually, completely reflashing works, but still ends up with the random reboots when doing random things
Click to expand...
Click to collapse
I get the same thing...
supahdaniel said:
I get the same thing...
Click to expand...
Click to collapse
sorry to hear of your problems. it is not the rom. enough folks are running it and I have had flawless installs. Read the OP and follow the directions, it works.
there is a new TWRP (from their site) that I downloaded as a .tar file and flashed with odin. flashes 4.4 roms now so you might try that rout.
my suggestion, in its limited knowledge is this:
put the rom, superuser, and the gapps on your SD card.
Reboot into the new TWRP and format the system- your phone is now blank.
install rom zip
install superuser zip
reboot.
first boot may take a bit, but not forever. Set up CM stuff and go from there
---------- Post added at 12:29 PM ---------- Previous post was at 12:17 PM ----------
Demminex said:
Would anyone know why when I enable ART mode on Quantum 4.4 Beta3 Rom, my phone continually has pop up messages with unexpected errors? -Such as calendar storage issues or the google keyboard(This should probably be in the ROM section but I can't write there.)
Click to expand...
Click to collapse
search the quantum thread about google settings. you have to turn on google now and disable notifications. also, I've been using the swift keyboard and don't have to deal with the google or android keyboard. that seems to have helped.
enable art after loading apps and be prepared for a wait for android to upgrade.
If I boot into recovery, wipe cache and dalvik (I fix permissions too, although this probably isn't necessary), then it boots right up like nothing is wrong with no fanfare.
If I'm lucky, this will even persist for an additional reboot. Otherwise on subsequent reboots it just bootloops forever until I go back to recovery and wipe cache/dalvik again, and then it boots right up again. Once into the ROM, everything runs fine, no issues at all.
I've tried rolling back a nightly or two but it doesn't seem to make a difference. Was there some major change in the last few weeks that I missed? How far do I need to roll back to get this to work?
It's my gf's tablet so I don't really want to wipe data if I can avoid it. Was even thinking of dirty flashing up to CM11.
Any insight is appreciated.
With my phone this problem ended up being using the wrong baseband version for the ROM/kernel that I was using. I was able to fix it by resetting it back to stock using ODIN (tool which can be used to recover Samsung devices) but from the sounds of it you have no such luxury.
Do you have any backups of when everything worked? If not try to find a way to get back to stock however you can. Aside from that make sure that you are using the correct ROM for your hardware.
Good luck and keep us updated.
czahrien said:
With my phone this problem ended up being using the wrong baseband version for the ROM/kernel that I was using. I was able to fix it by resetting it back to stock using ODIN (tool which can be used to recover Samsung devices) but from the sounds of it you have no such luxury.
Do you have any backups of when everything worked? If not try to find a way to get back to stock however you can. Aside from that make sure that you are using the correct ROM for your hardware.
Good luck and keep us updated.
Click to expand...
Click to collapse
The kindle is wifi only, so I don't think there are any baseband issues. Will update when/if I fix it.
Restoring to stock is a good idea. It's been over a year since this thing was stock, so it's quite possible we missed a firmware update or something.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Mine does this after I installed the new sgt7 4.4.2 rom. Did you end up fixing yours?
whatever100 said:
Mine does this after I installed the new sgt7 4.4.2 rom. Did you end up fixing yours?
Click to expand...
Click to collapse
Not yet, but I think it worked fine on cm10.2 for awhile.
Sent from my Nexus 5 using XDA Premium 4 mobile app
UPDATE - I dirty flashed cm11 and gapps as if I were updating any other nightly, and the issue appears to be gone. So freaking annoying, lol.