Related
Hello!
Im wondering about JellyTime, Is it good or bad/very buggy?
Since im very intrested about it i want others opinion.
Also im new to this rooting and new ROM installs.
Thanks!
Well, it is a beta Rom, so it will have bugs. I use it as my main rom knowing it has some minor flaws. If you need a full running device you might want to read the thread a little before flashing this. Most of us flashing this are "Flashaholics" and don't mind flashing a new version everyday if needed. I'd say flash it to see what it's like, and then make your own decision. Only you will know if you like it. This goes for any Rom.
Edit:
Welcome to the forum!
TheJokah said:
Well, it is a beta Rom, so it will have bugs. I use it as my main rom knowing it has some minor flaws. If you need a full running device you might want to read the thread a little before flashing this. Most of us flashing this are "Flashaholics" and don't mind flashing a new version everyday if needed. I'd say flash it to see what it's like, and then make your own decision. Only you will know if you like it. This goes for any Rom.
Edit:
Welcome to the forum!
Click to expand...
Click to collapse
Ohhh okay ^^ is it possible to install the rom at the sametime as i root? sorreh im newb at this :3:highfive:
After you root, make a backup of your rom. Before flashing (download rom to sd card-remember where it was stored), reboot in recovery.
Wipe data/factory reset.
Wipe dalvik.
Format all partitions (except sd card).
Install from sd card.
Flash rom (search for the download)
Reboot.
The above is sorta the correct way of doing it afterwards. Most of us don't do it.
Wait 5-10 minutes.
Reboot.
Configure all you need to configure.
Install your apps.
Reboot.
If you want to know the issues of a rom, read the op(first page) and read the last 5-10 pages.
All ics - jb roms have bugs. Won't be long till they are fixed.
Gb roms are stable on the most part.
Search for 4ext touch recovery, it's the prefered one.
Sent from a dream.
TheJokah said:
Well, it is a beta Rom, so it will have bugs. I use it as my main rom knowing it has some minor flaws. If you need a full running device you might want to read the thread a little before flashing this. Most of us flashing this are "Flashaholics" and don't mind flashing a new version everyday if needed. I'd say flash it to see what it's like, and then make your own decision. Only you will know if you like it. This goes for any Rom.
Edit:
Welcome to the forum!
Click to expand...
Click to collapse
Teichopsia said:
After you root, make a backup of your rom. Before flashing (download rom to sd card-remember where it was stored), reboot in recovery.
Wipe data/factory reset.
Wipe dalvik.
Format all partitions (except sd card).
Install from sd card.
Flash rom (search for the download)
Reboot.
The above is sorta the correct way of doing it afterwards. Most of us don't do it.
Wait 5-10 minutes.
Reboot.
Configure all you need to configure.
Install your apps.
Reboot.
If you want to know the issues of a rom, read the op(first page) and read the last 5-10 pages.
All ics - jb roms have bugs. Won't be long till they are fixed.
Gb roms are stable on the most part.
Search for 4ext touch recovery, it's the prefered one.
Sent from a dream.
Click to expand...
Click to collapse
Ive installed JellyTime but when ive installed the rom it just says loading and is keeping to load. nothing happens for 20 mins.
any idéa what can cause this?
Valentia007 said:
Ive installed JellyTime but when ive installed the rom it just says loading and is keeping to load. nothing happens for 20 mins.
any idéa what can cause this?
Click to expand...
Click to collapse
Either a bad download or a bad wipe procedure.
Sent from a dream.
Teichopsia said:
Either a bad download or a bad wipe procedure.
Sent from a dream.
Click to expand...
Click to collapse
I got it to work now, BUT how do i get google play? <.< ive downloaded it but it dont work.. so how do i get to my Paid apps?
Edit: Also IF i want to have my old HTC Rom do i just use the Root program again? or do i have to download it from their site?
Valentia007 said:
I got it to work now, BUT how do i get google play? <.< ive downloaded it but it dont work.. so how do i get to my Paid apps?
Click to expand...
Click to collapse
Alright buddy, last one. After this you nees to start reading and searching for your own answers. Almost anything you can think of has already been posted.
It's called gapps. It's a zip file with several google apps. Flash the same as when you flash a rom. No wipe necessary.
Sent from a dream.
Teichopsia said:
Alright buddy, last one. After this you nees to start reading and searching for your own answers. Almost anything you can think of has already been posted.
It's called gapps. It's a zip file with several google apps. Flash the same as when you flash a rom. No wipe necessary.
Sent from a dream.
Click to expand...
Click to collapse
Okay thanks for all the help man! appreciate it
I tried to install it the same tho but it says the Zip file dont exists. But ill figure this one out
Valentia007 said:
Okay thanks for all the help man! appreciate it
I tried to install it the same tho but it says the Zip file dont exists. But ill figure this one out
Click to expand...
Click to collapse
If you have problems just pm (private message) me.
Sent from a dream.
Teichopsia said:
If you have problems just pm (private message) me.
Sent from a dream.
Click to expand...
Click to collapse
Thanks man ive sorted it out tho :3 thanks for all the help ^^
jellytime is moving very fast towards stability...
Even now its beta 110 could be used as a daily driver if you ignore some minor things..Bluetooth is the only major problem in it..other than that,it is smooth and really good
TOTAL NOOB here been reading for months now [in the background] and just joined as i think ive finally worked up the courage to brick my HD. :laugh:
I did see a question asking about "best roms" am after an easy stable and fully working combination tho, would love jellybean and fully understand its still in beta. I think more noobs would attempt stuff if it wasnt so damn confusing with regards options and bolt ons.
Ive been Useing JellyTime since yesterday and i love it, the only complaint i have at this moment is that when i lock the screen and unlock it after more than 5 min it takes up to 5-10 seconds for it to start. Maby fixed in new Beta 10. ill try install it later today or tomorrow.
Jimpy0 said:
TOTAL NOOB here been reading for months now [in the background] and just joined as i think ive finally worked up the courage to brick my HD. :laugh:
I did see a question asking about "best roms" am after an easy stable and fully working combination tho, would love jellybean and fully understand its still in beta. I think more noobs would attempt stuff if it wasnt so damn confusing with regards options and bolt ons.
Click to expand...
Click to collapse
The Desire HD/Inspire 4G are virtually un-brickable as long as you are not ENG-OFF. Once you start flashing roms it all will become like second nature. Everything will start to get easier(more confidence comes too ) Just keep doing what you are doing (reading the threads). I wish some people did this more before posting.
Valentia007 said:
Ive been Useing JellyTime since yesterday and i love it, the only complaint i have at this moment is that when i lock the screen and unlock it after more than 5 min it takes up to 5-10 seconds for it to start. Maby fixed in new Beta 10. ill try install it later today or tomorrow.
Click to expand...
Click to collapse
This is kernel related issue..also found in virtuous infinity sense 4 rom..
Bluetooth also is broken in beta 10..I still miss the smoothness of beta 7..that kinnda smoothness is yet to be seen on this new kernel
saeedyasir91 said:
This is kernel related issue..also found in virtuous infinity sense 4 rom..
Bluetooth also is broken in beta 10..I still miss the smoothness of beta 7..that kinnda smoothness is yet to be seen on this new kernel
Click to expand...
Click to collapse
One of the fun things tho is that when i have my headset in my phone the "lock screen" is opening as soon i press the button, and without the headset it takes 5-10 seconds like i posted earlier :3
1st step grabbed h/kit - more reading :cyclops:
just a quickie as well do i need to do the catchpa thing everytime i post ?
Jimpy0 said:
1st step grabbed h/kit - more reading :cyclops:
just a quickie as well do i need to do the catchpa thing everytime i post ?
Click to expand...
Click to collapse
You need to use catchpa for about the first 10 posts. then it should disapear.
This ROM is outstanding. I started with Beta 8 and it was great–at least for the first few days before Beta 9 came out. And now that Beta 10 is out, I'm going to flash that ASAP.
Then great thing about this ROM is that Randomblame just can't seem to give himself any downtime, although he does find time to spend with his family. As long as the ROM works and he isn't going crazy from it, that's alright with me.
Sent using Jelly Time: Sweet, Sugary Goodness!
The whole process is pretty simple on what I have done. I will explain my situation here and my question that has got be baffled.
So it all started about two weeks ago, where I was flashing LiquidSmooth on my phone. I had a Touch-type CWM. It isn't mega old but it's pretty old for CWM, I haven't updated in a while (as i've seen there are updates to recent ones).
Anywho, I did a complete wipe, used the darkside wipe, alongside with the darkside cache wipe.
I think this was my fault, so please correct me anyone if I am wrong here. I accidentally hit "reboot phone" instead of "reboot bootloader"
I got a permabrick from this whole ordeal. It was a permabrick because It said QHSUSB_DLOAD in the device manager, looking this up further confirmed my reasoning. I didn't want to jtag because that invovles removing the phone to pieces and soldering on wires etc. etc.
So I resorted to send it out to Samsung.
All is well when it came back. I made sure this time the whole phone was setup properly.
So I use Odin install for CWM and SU was installed via CWM. I install an older version of CWM (non-touch, i believe 1st revision as i've posted in one of the threads).
I kept stock ROM, everything was working okay and suddenly, KERPLUNK, it went back into permanent brick after I deleted cache partition, dalvik cache, and battery cache wipe. I didn't do fix permissions or anything, just hit reboot afterwards.
This is a super head scratcher here..... Anyone know where I went wrong?
Any insight here is greatly appreciated! :good:
P.S. I am now sending in my phone TWICE to Samsung for repairs.
If you are on the most up to date CWM, do not use the scripts. They are no longer needed, and will cause problems( hard brick though, never heard of) The second time, im stumped. I suggest go to TWRP and ditch the scripts. Latest TWRP does not need it
LoopDoGG79 said:
If you are on the most up to date CWM, do not use the scripts. They are no longer needed, and will cause problems( hard brick though, never heard of) The second time, im stumped. I suggest go to TWRP and ditch the scripts. Latest TWRP does not need it
Click to expand...
Click to collapse
I finally jumped in the water and flashed twrp! Yay!
Sent from my SAMSUNG-SGH-T989 using xda premium
All the steps you say you did don't point to a brick. But one thing caught my eye! You said you were flashing liquidsmooth? What File did you flash? Did it have Hercules in the name? Because if it didn't then it's not for our phone.. I only ask because a lot of other people made that mistake
Sent from my SGH-T989 using xda premium
rymanh said:
All the steps you say you did don't point to a brick. But one thing caught my eye! You said you were flashing liquidsmooth? What File did you flash? Did it have Hercules in the name? Because if it didn't then it's not for our phone.. I only ask because a lot of other people made that mistake
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
great call on that I had to educate a few users that the d2tmo is not for our phone but indeed the S3. Good catch on your part and it sounds like user error as well
LoopDoGG79 said:
If you are on the most up to date CWM, do not use the scripts. They are no longer needed, and will cause problems( hard brick though, never heard of) The second time, im stumped. I suggest go to TWRP and ditch the scripts. Latest TWRP does not need it
Click to expand...
Click to collapse
Could you please educate me with a link referring to what TWRP is? Sorry, i'm still fairly new to the scene and all i've ever been educated upon is CWM.
suaverc118 said:
I finally jumped in the water and flashed twrp! Yay!
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Nice! What is TWRP and how is it like?
rymanh said:
All the steps you say you did don't point to a brick. But one thing caught my eye! You said you were flashing liquidsmooth? What File did you flash? Did it have Hercules in the name? Because if it didn't then it's not for our phone.. I only ask because a lot of other people made that mistake
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
I've flashed the hercules ROM. I know this for sure because Liquidsmooth was working, it was extremely glitchy (playing games gave me pixelated actions sometimes, and using something like gameCIH/Game Guardian was unworkable). So i decided to ditch it and was getting ready to flash Jedi Mind Trick.
After the whole hard bricking ordeal, I decided to stick to stock rom, and even on that, I just flashed CWM and SU ONLY. Rebooted, and deleted the cache's (like i've posted to you) with absolutely no success. It baffled me that I bricked the phone AGAIN too!
playya said:
great call on that I had to educate a few users that the d2tmo is not for our phone but indeed the S3. Good catch on your part and it sounds like user error as well
Click to expand...
Click to collapse
Yes..... there is something wrong, i feel it is a user error also, but i'm very unsure where to even start
Once again, all of your insight is well appreciated! I just do not want to hardbrick my phone AGAIN and have to send it to Samsung. I am not allowed to even think of a replacement because this was a b-day present a year or two ago from my fiance.
You say that it is bricked again. Do you mean by that, that you cannot get into recovery?
Sent from my SAMSUNG-SGH-T989 using xda premium
XxGoKoUxX said:
Could you please educate me with a link referring to what TWRP is? Sorry, i'm still fairly new to the scene and all i've ever been educated upon is CWM.
Nice! What is TWRP and how is it like?
I've flashed the hercules ROM. I know this for sure because Liquidsmooth was working, it was extremely glitchy (playing games gave me pixelated actions sometimes, and using something like gameCIH/Game Guardian was unworkable). So i decided to ditch it and was getting ready to flash Jedi Mind Trick.
After the whole hard bricking ordeal, I decided to stick to stock rom, and even on that, I just flashed CWM and SU ONLY. Rebooted, and deleted the cache's (like i've posted to you) with absolutely no success. It baffled me that I bricked the phone AGAIN too!
Yes..... there is something wrong, i feel it is a user error also, but i'm very unsure where to even start
Once again, all of your insight is well appreciated! I just do not want to hardbrick my phone AGAIN and have to send it to Samsung. I am not allowed to even think of a replacement because this was a b-day present a year or two ago from my fiance.
Click to expand...
Click to collapse
Flash this in recovery, reboot recovery, and you will have TWRP!!
TWRP 2.3.1.1
DM_Sledge said:
You say that it is bricked again. Do you mean by that, that you cannot get into recovery?
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Yes, it is perma-bricked, meaning the only method of fixing the brick is jtagg'ing
Upon plugging it into device manager, I get the prompt "QHSUSB_DLOAD" and phone doesn't even boot on no matter what combinations I make.
LoopDoGG79 said:
Flash this in recovery, reboot recovery, and you will have TWRP!!
TWRP 2.3.1.1
Click to expand...
Click to collapse
Thank you LoopDo, I will do this after I get my phone home again.
I have this phone, and none of the steps you listed would brick the device. Even with no ROM on the phone, you should still be able to get into recovery.
Is there something you aren't telling us?
Sent from my Galaxy Nexus using xda premium
Nope, wouldn't be a reason why I would lie because then the problem will never be resolved.... I'm kind of nervous on reflashing ONE more time after the phone comes home again....
The phone has been fixed once AGAIN, and it is in the process of being shipped back to me.
Phone will be home Wednesday and I will give it ONE more try
Wish me luck!
P.S. my PC has been glitchy lately, so that MAY or MAY NOT contribute to the permabrick, then again the brick doesn't happen until I flash stuff via CWM.
P.S.S. I've since re-installed Win 7 again, it hasn't been glitchy since
XxGoKoUxX said:
Nope, wouldn't be a reason why I would lie because then the problem will never be resolved.... I'm kind of nervous on reflashing ONE more time after the phone comes home again....
The phone has been fixed once AGAIN, and it is in the process of being shipped back to me.
Phone will be home Wednesday and I will give it ONE more try
Wish me luck!
P.S. my PC has been glitchy lately, so that MAY or MAY NOT contribute to the permabrick, then again the brick doesn't happen until I flash stuff via CWM.
P.S.S. I've since re-installed Win 7 again, it hasn't been glitchy since
Click to expand...
Click to collapse
You most likely flashed the Wrong Liquidsmooth ROM (incompatible Kernel), and it hard bricked the phone. It happened to me the same way, and I had to send it in for JTAG.
I have bricked my phone installing the Liquidsmooth ROM too. I downloaded the wrong ROM, though. The thread should have a big ****in warning to double check the ROM you are about to download, otherwise your phone is a toast. There were more people who bricked their phones by installing the Liquidsmooth.
Well, I got it back from the warranty and the phone looks good. Installed that Liquidsmooth again and played for a day. Tried other JB ROMs. Most of them are OK in terms of battery life and smoothness, but there is something wrong with the signal. People always say my voice isn't clear. I got tired of all this BS and testing new ROMs and went to back to ICS and won't look back, not anytime.
Don't use darkside scripts, btw. You don't need that anymore.
I'd like to say thank you for everyone's patience. All of your insight is more than helpful!
DroidDonX said:
You most likely flashed the Wrong Liquidsmooth ROM (incompatible Kernel), and it hard bricked the phone. It happened to me the same way, and I had to send it in for JTAG.
Click to expand...
Click to collapse
I might have, but the one i downloaded (which is still on the phone's memory card) is a hercules ROM. Either way on my second try there was a hard brick also, in return of which I had to resend it in. The second try was just simply: Odin---->CWM---->Root---->SU---->wipe cache partition+fix permissions+wipe dalvik cache via CWM (not the super scripts).
cipsaz said:
I have bricked my phone installing the Liquidsmooth ROM too. I downloaded the wrong ROM, though. The thread should have a big ****in warning to double check the ROM you are about to download, otherwise your phone is a toast. There were more people who bricked their phones by installing the Liquidsmooth.
Well, I got it back from the warranty and the phone looks good. Installed that Liquidsmooth again and played for a day. Tried other JB ROMs. Most of them are OK in terms of battery life and smoothness, but there is something wrong with the signal. People always say my voice isn't clear. I got tired of all this BS and testing new ROMs and went to back to ICS and won't look back, not anytime.
Don't use darkside scripts, btw. You don't need that anymore.
Click to expand...
Click to collapse
Thanks again for your insight I think i'm done with flashing for a little bit for now.... I kind of want as factory of a JB Rom as possible. :good:
If anyone has any idea where I can get that, please let me know as my Stock ICS is a bit laggy at times, with the facial recognition system, it lags even worse!
rymanh said:
All the steps you say you did don't point to a brick. But one thing caught my eye! You said you were flashing liquidsmooth? What File did you flash? Did it have Hercules in the name? Because if it didn't then it's not for our phone.. I only ask because a lot of other people made that mistake
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
that just happened to me today with liquid smooth. i had to unroot, flash stock, and start over. im pretty sure i got it from goo.im under hercules. unfortunate mislabeling? oh yeah, and if your phone shows anything other than nothing, youre not hard bricked. thats why its called Hercules, i think. ive been soft bricked so many times from dumb **** like. ****ing with the governors and all that **** cm gives you the option to do when there aint even a 1080p camera that works fully = / lol <3 Cm I Love Yew!! But yeah, odin will set you free!!!
I'm making this thread for anybody running the Slim Bean rom in an attempt to keep Ktempelton's rom thread clean. Please post and answer respectfully.OK guys and gals.... I want to give you this link to Rwilco's app. I'm not going into what it is, you can read the OP. But it's Rwilco, enough said...right..Head on over..its a great app. Don't forget to hit the thanks button over there at his OP...Thanks..:good:..http://forum.xda-developers.com/showthread.php?t=2297401
sheezy69
I need more info. Did you do a clean install;wipe data, cache, and dalvik? Is the speaker working for other apps?What, if any, mods did you flash after initial rom flash. I haven't had this problem on this rom, but all phones are different it seems. So I need as much info as possible.
Gil81 said:
I need more info. Did you do a clean install;wipe data, cache, and dalvik? Is the speaker working for other apps?What, if any, mods did you flash after initial rom flash. I haven't had this problem on this rom, but all phones are different it seems. So I need as much info as possible.
Click to expand...
Click to collapse
Yes, clean install;wipe data, cache, and dalvik no mods or tweaks-
The speaker is fine, I can hear them no problem. The microphone when the phone is on speaker phone does not work however. People say they can barely hear me at all and I've tried calling myself and can confirm that it sounds very low and crackly. When I reinstall a TW rom..it works flawlessly.
Does it have anything to do going from JB to Slim? When I reinstall JB rom i use the 2x wipe. I ran out of things to try so I went back to TW but would rather be on slim + zap kernal
shezzy69 said:
Yes, clean install;wipe data, cache, and dalvik no mods or tweaks-
The speaker is fine, I can hear them no problem. The microphone when the phone is on speaker phone does not work however. People say they can barely hear me at all and I've tried calling myself and can confirm that it sounds very low and crackly. When I reinstall a TW rom..it works flawlessly.
Does it have anything to do going from JB to Slim? When I reinstall JB rom i use the 2x wipe. I ran out of things to try so I went back to TW but would rather be on slim + zap kernal
Click to expand...
Click to collapse
I would try another clean install, wipe data,cache,dalvik,like three times.Just to make sure nothing is left behind and flash rom from the eL29 direct boot kernel. I have seen this issue in other roms,now that I did a little research,and it seems phone specific. I myself have never had a mic problem. I will keep looking, so keep an eye on this thread. Also, did you go to JB correctly. Using the one - click full restore....this partitions you're phone correctly. Could have nothing to do with you're problem,but wanted to ask..I think the full restore is the one you want, just grab the one that wipes you're internal memory. Yep....back-up time.
Gil81 said:
I would try another clean install, wipe data,cache,dalvik,like three times.Just to make sure nothing is left behind and flash rom from the eL29 direct boot kernel. I have seen this issue in other roms,now that I did a little research,and it seems phone specific. I myself have never had a mic problem. I will keep looking, so keep an eye on this thread. Also, did you go to JB correctly. Using the one - click no data....this partitions you're phone correctly. Could have nothing to do with you're problem,but wanted to ask..
Click to expand...
Click to collapse
My first flash since I bought it was a one click, however, I went to other TW roms and used the 2x wipe zip since then. When I went to slim ( and even black bean ) and I used the el29 direct boot. I noticed it happens only on AOSP roms..maybe it is just my device.
shezzy69 said:
My first flash since I bought it was a one click, however, I went to other TW roms and used the 2x wipe zip since then. When I went to slim ( and even black bean ) and I used the el29 direct boot. I noticed it happens only on AOSP roms..maybe it is just my device.
Click to expand...
Click to collapse
Yep, it could be you're device. I'll keep looking and hit you up if I find anything. But this phone is wonky that way. I can't run Dirty Unicorn. It flashes fine and runs great, for about a day. Then the grimlin's come out. Still trying to figure that one out... Hey, if you like slim bean. You'll love Dirty Unicorn.. Give it a go. I would run it, but slim just flies on my phone. Sorry I couldn't be more help... And Im not sure if you uderstood what I meant by one-click. There is a one - click that you need to flash before the first time you go to JB from ICS... It partions you're phone correctly.
Gil81 said:
Yep, it could be you're device. I'll keep looking and hit you up if I find anything. But this phone is wonky that way. I can't run Dirty Unicorn. It flashes fine and runs great, for about a day. Then the grimlin's come out. Still trying to figure that one out... Hey, if you like slim bean. You'll love Dirty Unicorn.. Give it a go. I would run it, but slim just flies on my phone. Sorry I couldn't be more help... And Im not sure if you uderstood what I meant by one-click. There is a one - click that you need to flash before the first time you go to JB from ICS... It partions you're phone correctly.
Click to expand...
Click to collapse
Isn't dirty unicorn AOSP? All AOSP roms have had this same problem for me
Can you link that one - click? I thought you ment the one click installers for like gb08 or w/o.. The only thing I've ever used that handled partitions is the 2x JB data eraser that Tough by S4 suggests
sheezy69
NEWBIES, STOP AND READ THIS FIRST!!! http://forum.xda-developers.com/showthread.php?p=35539014#post35539014 read through this and it will give you some good info...the link you want to read is down the page a little. It will start by saying, new to jb read this..
Gil81 said:
NEWBIES, STOP AND READ THIS FIRST!!! http://forum.xda-developers.com/showthread.php?p=35539014#post35539014 read through this and it will give you some good info...the link you want to read is down the page a little. It will start by saying, new to jb read this..
Click to expand...
Click to collapse
When I first went from ics to JB I used a one click install FULL WIPE (GB10 I think it was at the time) version ( which is what this post tells you to do) so yes I have done this step when I went from ICS to JB. Besides, I'm sure if I didn't do it correctly then any version of JB would not work on my phone and it does
Other then using a ics modem, Is there any special step ( not already mentioned ) to go back to AOSP from JB?
shezzy69 said:
When I first went from ics to JB I used a one click install FULL WIPE version ( which is what this post tells you to do) so yes I have done this step when I went from ICS to JB. Besides, I'm sure if I didn't do it correctly then any version of JB would not work on my phone and it does
Click to expand...
Click to collapse
Ok...just wanted to make sure...good going..and yes they will work,but you'll run into issues down the line. Thats why I was so persistent. Well, I guess I'm out of ideas,but I'll keep looking...Sorry. If you're staying with tw. I always thought jellyverse was awesome and there is a trial/beta version 4 out for it.Good Luck..
honestly, I'm more interested in the LZ kernal then anything else and I'm pretty sure thats AOSP only.. oh well
shezzy69 said:
honestly, I'm more interested in the LZ kernal then anything else and I'm pretty sure thats AOSP only.. oh well
Click to expand...
Click to collapse
yep aosp only.. but I just had an idea.. What modem do you use with aosp. Im on fl24.. I don't know how it would matter, but thats all I got...lol. Sometimes these roms can be wonky, case in point. When I first flashed slim build 7 I couldn't get my hotspot to work. I jumped back to build 6 and was fine. After a couple days I gave 7 another try and now it works....Both times I did the exact samething to flash...gremlins...lol.
Gil81 said:
yep aosp only.. but I just had an idea.. What modem do you use with aosp. Im on fl24.. I don't know how it would matter, but thats all I got...lol. Sometimes these roms can be wonky, case in point. When I first flashed slim build 7 I couldn't get my hotspot to work. I jumped back to build 6 and was fine. After a couple days I gave 7 another try and now it works....Both times I did the exact samething to flash...gremlins...lol.
Click to expand...
Click to collapse
pretty sure I used the last released modem which is fl24 right?
shezzy69 said:
pretty sure I used the last released modem which is fl24 right?
Click to expand...
Click to collapse
yep,that is the latest ics modem..damn man sorry i couldn't figure it out...Well good luck.. see ya in the tw forums I guess.
Gil81 said:
Yep, it could be you're device. I'll keep looking and hit you up if I find anything. But this phone is wonky that way. I can't run Dirty Unicorn. It flashes fine and runs great, for about a day. Then the grimlin's come out. Still trying to figure that one out... Hey, if you like slim bean. You'll love Dirty Unicorn.. Give it a go. I would run it, but slim just flies on my phone. Sorry I couldn't be more help... And Im not sure if you uderstood what I meant by one-click. There is a one - click that you need to flash before the first time you go to JB from ICS... It partions you're phone correctly.
Click to expand...
Click to collapse
That's hilarious, I have the same issue, I love slim and kinda really liked dirty unicorn, my phone loves slim, didn't play well with dirty unicorn lol, strange how this phone can be so different from one to another
Sent from my SPH-D710 using xda premium
Yep...if I've learned one thing on XDA, its that one person's fix might not work for you and another that does won't work for them...I think thats why I'm such a believer in the search button..
I'm having gps issues here!! I clean flashed everything. I flashed to stock touchwiz got a gps fix then flashed back to slim build 7, and gps was working fine then it's stops working again. I need a fix cause gps is very important with my job. Ty
Sent from my Galaxy [S2]
jordan0314 said:
I'm having gps issues here!! I clean flashed everything. I flashed to stock touchwiz got a gps fix then flashed back to slim build 7, and gps was working fine then it's stops working again. I need a fix cause gps is very important with my job. Ty
Sent from my Galaxy [S2]
Click to expand...
Click to collapse
Do you have any tweaks flashed. I seen where nos tweaks(some of them)can mess with gps. Read through this post,looks like a promising fix.I dont no of any that work by experience because I always have had good luck with gps.The one to read is post 96. http://forum.xda-developers.com/showthread.php?t=1853671&page=10
Gil81 said:
Do you have any tweaks flashed. I seen where nos tweaks(some of them)can mess with gps.
Click to expand...
Click to collapse
All I got is crossbreeder and LZ 4
Sent from my Galaxy [S2]
I would also read through this if I was you. Looks like a couple different possible gps fixes..Don't forget to have a backup,I know....I know. You know this, just saying.Good Luck. Please report back which fix worked for you(if any).Thx... http://forum.xda-developers.com/showthread.php?t=2084482
Lately I have been getting random reboots and random black screens. The phone will either reboot itself show the galaxy s3 screen then go to complete darkness or vibrate and go straight to complete darkness. This seems to be random and usually starts happening a week or so after flashing a rom or kernel. Right now I am using my own TW rom (in dev section) with kt kernel and team kernalizer scripts. But the kernel doesn't seem to matter as this happens regardless. Does anyone know whats going on? Also this started happening after I ran aokp 4.2.2 for awhile, then odin back to stock and issues started. I've also been having less battery life since then.
Someone please help
anyone?
aamir123 said:
anyone?
Click to expand...
Click to collapse
Running stock Odin may be an option, but here is what I would do first.
Flash the LJC firmware from the second firmware link in my signature. It's in the OP, but isn't immediately obvious. Just scroll a bit and you will see it.
Stop using KT and tkmod for now. These, simply put, are variables that you don't need to deal with right now. There is also a good chance it's a bug in your ROM.
Aerowinder said:
Running stock Odin may be an option, but here is what I would do first.
Flash the LJC firmware from the second firmware link in my signature. It's in the OP, but isn't immediately obvious. Just scroll a bit and you will see it.
Stop using KT and tkmod for now. These, simply put, are variables that you don't need to deal with right now. There is also a good chance it's a bug in your ROM.
Click to expand...
Click to collapse
Before I went to aokp I was using my rom very stably for a good while and others have been using it without problems, but I agree going to least common denominator (stock rom/kernel) sounds like a very good idea. I'll also flash the ljc firmware even though I haven't really had any problems with the 4.1.2 one.
Btw why ljc and not md5?
aamir123 said:
Before I went to aokp I was using my rom very stably for a good while and others have been using it without problems, but I agree going to least common denominator (stock rom/kernel) sounds like a very good idea. I'll also flash the ljc firmware even though I haven't really had any problems with the 4.1.2 one.
Btw why ljc and not md5?
Click to expand...
Click to collapse
Because it's somewhat likely the MD5 firmware is causing your problems. I can't use it on my phone, just kills battery. Maybe your phone has a more severe reaction to it.
Aerowinder said:
Because it's somewhat likely the MD5 firmware is causing your problems. I can't use it on my phone, just kills battery. Maybe your phone has a more severe reaction to it.
Click to expand...
Click to collapse
ok I guess I'll go back but I don't see why the md5 firmware would be a problem now after I was using it with no problem for a while.
Unless you are running 100% md5, it has been known to cause some issues. Seems a lot was done on that update from 4.1.1 - 4.1.2, and it doesn't always like to be mixed with older fw.
Sent from my SGH-T999L using XDA Premium 4 mobile app
DocHoliday77 said:
Unless you are running 100% md5, it has been known to cause some issues. Seems a lot was done on that update from 4.1.1 - 4.1.2, and it doesn't always like to be mixed with older fw.
Sent from my SGH-T999L using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well I flashed the LJC fw and so far it's been pretty stable, only having trouble with excess heat but will probably get better with time. Also I'm having trouble getting a logcat app running (catlog etc). The app opens I give it root permissions, then I get a black screen with loading ring. No log whatsoever, is that normal? tried on both fw btw.
just got another random reboot on ljc fw. any other ideas?
aamir123 said:
just got another random reboot on ljc fw. any other ideas?
Click to expand...
Click to collapse
Just a heads up, my phone was doing this for about 3 days, and then completely crashed. Check out my thread. Stock Rom, but rooted. Hope it doesn't happen to you.
cboss718 said:
Just a heads up, my phone was doing this for about 3 days, and then completely crashed. Check out my thread. Stock Rom, but rooted. Hope it doesn't happen to you.
Click to expand...
Click to collapse
Idk what the issue is I'm gonna go stock for a while without recovering and see if that will fix anything, if not maybe tmobile is the way to go. Btw I tried taking a log cat but get error saying that dev/log/main doesn't exist.
Ok I was doing good for a few hours after flashing stock and not restoring Google account until I got a random reboot just now. I was able to get a log cat tho so I'd anyone can look at it and help.
Sent from my SGH-T999 using xda app-developers app
anybody? Does anyonehave any ideas?
aamir123 said:
anybody? Does anyonehave any ideas?
Click to expand...
Click to collapse
That logcat contains 30 seconds of information. Looks like you pulled it after the device rebooted. It's probably going to be the kernel dmesg that we need. You get that one after the device reboots, but not the logcat.
Aerowinder said:
That logcat contains 30 seconds of information. Looks like you pulled it after the device rebooted. It's probably going to be the kernel dmesg that we need. You get that one after the device reboots, but not the logcat.
Click to expand...
Click to collapse
ok I will try to get that the next time it reboots. Hopefully it's a simple fix, but just not sure what the problem could be.
So I went all these days without a random reboot and finally got one today, but was unable to pull a dmesg as it said does not exist. What can I try to get a dmesg now?
Also the phone feels like it never shuts down, even when I choose to shutdown in the menu it ends up restarting itself then bootlooping or just restarting. I've also noticed that holding home and power to turn phone on works most of the time to get it back to the os only to have it crash shortly after. I press home and power until I see the white splashscreen then let power button go. but staying in os for more than a few mins right now is impossible.
Well I've been running cm11 builds for t0lte on my t0lteatt (technically t0ltecan but same thing) for months with no issues. Until the dreaded March 4th nightly dropped. There were over a hundred commits that night, and something broke compatibility with my device. It keeps getting signal, then phone force closes and signal is lost. Then it gets signal, etcetera in an eternal loop. I'm wondering what I could do about this? Could a modem fix this issue? Is there anybody else out there who has been running this ROM on a t0lteatt?
I'm only asking because my device isn't supported by CM11, so I was very happy to find I could run the international build just fine. Now what do I do for CM love??? Aaaagh! Help would be awesome guys, who knows a possible solution?
Sent from my thumbs to your face.
mertin said:
Well I've been running cm11 builds for t0lte on my t0lteatt (technically t0ltecan but same thing) for months with no issues. Until the dreaded March 4th nightly dropped. There were over a hundred commits that night, and something broke compatibility with my device. It keeps getting signal, then phone force closes and signal is lost. Then it gets signal, etcetera in an eternal loop. I'm wondering what I could do about this? Could a modem fix this issue? Is there anybody else out there who has been running this ROM on a t0lteatt?
I'm only asking because my device isn't supported by CM11, so I was very happy to find I could run the international build just fine. Now what do I do for CM love??? Aaaagh! Help would be awesome guys, who knows a possible solution?
Sent from my thumbs to your face.
Click to expand...
Click to collapse
Have you tried flashing the latest drop? cm-11-20140306-NIGHTLY-t0lte.zip
Maybe stuff is unscrewed now. Nightly's are crap shoots.
Only stable releases I see are 10.X. There's a reason for that......
Have you tried any of the hybrid ROMs, like OmniROM or Dirty Unicorns. You can't swing a dead cat without hitting a killer option on those.
Yes I've tried all the newer nightlies too. It is working fine for t0lte users (which makes sense, because it's made for them) which leads me to believe it's just people like me running it on a variant device who are missing out. It works as intended on the proper device, so I don't see why they would change it back. Other ROMs just don't seem as polished and I'm OCD so rough edges are a dealbreaker. Cm11 has bugs, but none that affect my personal usage so that's why it is my daily driver. Thanks for the tip tho I'm still investigating!
Sent from my thumbs to your face.
mertin said:
Yes I've tried all the newer nightlies too. It is working fine for t0lte users (which makes sense, because it's made for them) which leads me to believe it's just people like me running it on a variant device who are missing out. It works as intended on the proper device, so I don't see why they would change it back. Other ROMs just don't seem as polished and I'm OCD so rough edges are a dealbreaker. Cm11 has bugs, but none that affect my personal usage so that's why it is my daily driver. Thanks for the tip tho I'm still investigating!
Sent from my thumbs to your face.
Click to expand...
Click to collapse
Well, it's not really different.....
[Q] difference between t0lte and t0lteatt
http://forum.xda-developers.com/showpost.php?p=42038043&postcount=5
Credit T-Macgnolia
dicksteele said:
Well, it's not really different.....
[Q] difference between t0lte and t0lteatt
http://forum.xda-developers.com/showpost.php?p=42038043&postcount=5
Credit T-Macgnolia
Click to expand...
Click to collapse
I also have a t0lteatt running the CM11 nightly for t0lte. I also installed the nightly that resulted in not being able to boot, to solve it I rebooted my phone manually to recovery and installed the previous days back over the top and I fixed it. Then I wait a couple days and tried the next nightly which worked. I am currently running yesterdays (030632014) without issue.
TDLR: the nightly from the 4th left me broken, none of the nightly's before that point ever broke my phone, also none since then have broken my phone.
Good Luck!
Mazamuda said:
I also have a t0lteatt running the CM11 nightly for t0lte. I also installed the nightly that resulted in not being able to boot, to solve it I rebooted my phone manually to recovery and installed the previous days back over the top and I fixed it. Then I wait a couple days and tried the next nightly which worked. I am currently running yesterdays (030632014) without issue.
TDLR: the nightly from the 4th left me broken, none of the nightly's before that point ever broke my phone, also none since then have broken my phone.
Good Luck!
Click to expand...
Click to collapse
Thanks for the help, but it's still broken on my end. (Just tried the same nightly) This is getting really weird. It's happening right away, clean install. Can't get the popup to go away long enough to do anything. Any suggestions what I could try? It's making me mental!
Sent from my thumbs to your face.
mertin said:
Thanks for the help, but it's still broken on my end. (Just tried the same nightly) This is getting really weird. It's happening right away, clean install. Can't get the popup to go away long enough to do anything. Any suggestions what I could try? It's making me mental!
Sent from my thumbs to your face.
Click to expand...
Click to collapse
I am not sure I understand the symptoms, are you saying that it boots up just fine but the phone keeps getting and losing signal? Or is it booting up just fine then rebooting after the phone gets and loses signal?
Welll no matter I would take a full backup of your system and then wipe it clean and install the known working 10.2, just to see if it is indeed a hardware problem. If 10.2 works then maybe take a nother backup of that you can at least swap back and forth while you work on the issue.
Mazamuda said:
I am not sure I understand the symptoms, are you saying that it boots up just fine but the phone keeps getting and losing signal? Or is it booting up just fine then rebooting after the phone gets and loses signal?
Welll no matter I would take a full backup of your system and then wipe it clean and install the known working 10.2, just to see if it is indeed a hardware problem. If 10.2 works then maybe take a nother backup of that you can at least swap back and forth while you work on the issue.
Click to expand...
Click to collapse
Hey thanks for working through this with me, I really appreciate it! What's happening is it boots just fine. But I get the error popup "com.android.phone has stopped". When I hit okay it immediately comes up again. Forever. I also just had a scary missing imei problem happen just now and spent the last couple hours getting THAT sorted out. But now I'm back on the march 1 nightly and everything is just fine. I just can't run anything newer than that and I don't get why.
Sent from my thumbs to your face.
They just posted an M4, maybe that will work?
Sent from my GT-N7105 using xda app-developers app
Mazamuda said:
They just posted an M4, maybe that will work?
Sent from my GT-N7105 using xda app-developers app
Click to expand...
Click to collapse
They did? I don't see it on get.cm?
Sent from my thumbs to your face.
Its on the cyanogenmod.org blog.
Sent from my GT-N7105 using xda app-developers app
Wooooooo I got today's nightly running (march 8th)!! I had a sudden urge to try a different recovery just to make sure I had tried everything. Installed philz touch, then installed CM. This time it finally worked! I wonder if it was twrp giving me problems all this time. Just so bizarre I had zero issues updating every day for months and then suddenly just couldn't get it working at all.
In any case it seems good for now. Thanks for all the advice!
Sent from my thumbs to your face.
mertin said:
Wooooooo I got today's nightly running (march 8th)!! I had a sudden urge to try a different recovery just to make sure I had tried everything. Installed philz touch, then installed CM. This time it finally worked! I wonder if it was twrp giving me problems all this time. Just so bizarre I had zero issues updating every day for months and then suddenly just couldn't get it working at all.
In any case it seems good for now. Thanks for all the advice!
Sent from my thumbs to your face.
Click to expand...
Click to collapse
Excellent.
Was it TWRP 2.6.3.1 ?? I think that's the one that works with newer ROM builds. At least for me.....
Or ....... Was it the March 8th build ...... Did you flash that in TWRP ?
Also, keep a copy of each on your phone. If one doesn't work just flash the other, then you can reboot to recovery to the other one.
mertin said:
Wooooooo I got today's nightly running (march 8th)!! I had a sudden urge to try a different recovery just to make sure I had tried everything. Installed philz touch, then installed CM. This time it finally worked! I wonder if it was twrp giving me problems all this time. Just so bizarre I had zero issues updating every day for months and then suddenly just couldn't get it working at all.
In any case it seems good for now. Thanks for all the advice!
Sent from my thumbs to your face.
Click to expand...
Click to collapse
That was going to be my next question. I have heard lots of reports of people running CM11 and having problems with TWRP, I use CWM and it has always been rock solid.
Glad your back up and running, enjoy the crack-flashing!
dicksteele said:
Excellent.
Was it TWRP 2.6.3.1 ?? I think that's the one that works with newer ROM builds. At least for me.....
Or ....... Was it the March 8th build ...... Did you flash that in TWRP ?
Also, keep a copy of each on your phone. If one doesn't work just flash the other, then you can reboot to recovery to the other one.
Click to expand...
Click to collapse
It was 2.6.3.1 and I even tried the newer 2.6.3.7 for t0lte and it didn't work. But all good with cwm. There must have been some tiny change that twrp wasn't flashing properly. Whatever it was, just glad to have that behind me!
Sent from my thumbs to your face.
mertin said:
It was 2.6.3.1 and I even tried the newer 2.6.3.7 for t0lte and it didn't work. But all good with cwm. There must have been some tiny change that twrp wasn't flashing properly. Whatever it was, just glad to have that behind me!
Sent from my thumbs to your face.
Click to expand...
Click to collapse
Most excellent. Congrats