Related
i just noticed this last night, i tried to play a game of miniclip (lol dejavu) but the game never loaded,
i then downloaded it to my computer and then passed it to my phone,
i installed SWFPlayer from the market, and tried to run it but it gave me an error message that my phone did not have flash player installed, i went to the market and installed it, and tried it again, it gave me the same message,
i restarted my phone and tried again and it still didn't work, so i restored a NAND backup to test it and it worked this time so the issue is with the rom
I really like this rom is there a fix for this?
*Fixed* here is the same link from post #6 that fixed my issue
*url deleted* use attachment
Download to SD then flash/install through cwm
ferny_dx said:
i just noticed this last night, i tried to play a game of miniclip (lol dejavu) but the game never loaded,
i then downloaded it to my computer and then passed it to my phone,
i installed SWFPlayer from the market, and tried to run it but it gave me an error message that my phone did not have flash player installed, i went to the market and installed it, and tried it again, it gave me the same message,
i restarted my phone and tried again and it still didn't work, so i restored a NAND backup to test it and it worked this time so the issue is with the rom
I really like this rom is there a fix for this?
Click to expand...
Click to collapse
I would suggest asking dwitherell either by pm or in his Tweakstock thread, perhaps something he included (or left out) is causing the issue
anoninja118 said:
I would suggest asking dwitherell either by pm or in his Tweakstock thread, perhaps something he included (or left out) is causing the issue
Click to expand...
Click to collapse
will do i just wasnt sure if i should bother him if someone had already found a fix,
if i get an answer from him i will have it posted here
Try installing Adobe Air?
Sent from my SCH-I510 using xda premium
kvswim said:
Try installing Adobe Air?
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
Installed it tried it, restarted, tried it, and no difference whatsoever
ferny_dx said:
will do i just wasnt sure if i should bother him if someone had already found a fix,
if i get an answer from him i will have it posted here
Click to expand...
Click to collapse
Ok, so I figured it out, i just flashed the stock flash player through cwm after i installed the rom.
Here is the link to those who might need it [URL="Stock Flash Player]http://www.megaupload.com/?d=8QC5X50X[/URL]
I'm having an odd problem, and I'm not sure what to do about it.
This morning when I woke up, I noticed that there was a BusyBox update in my notification bar. Upon trying to update it failed.
So, I uninstall BusyBox, and try to reinstall it, but I'm met with a message that I don't have root access. Upon checking with Root Checker, I DO have root access. But, now all of a sudden, my wifi is not working, when it has worked flawlessly up to this point.
I'm not sure what to do. I don't have a nandroid backup to roll back to, and I need my wifi to work. Would doing a factory reset and flashing a new ROM solve this problem?
lukas_s said:
I'm having an odd problem, and I'm not sure what to do about it.
This morning when I woke up, I noticed that there was a BusyBox update in my notification bar. Upon trying to update it failed.
So, I uninstall BusyBox, and try to reinstall it, but I'm met with a message that I don't have root access. Upon checking with Root Checker, I DO have root access. But, now all of a sudden, my wifi is not working, when it has worked flawlessly up to this point.
I'm not sure what to do. I don't have a nandroid backup to roll back to, and I need my wifi to work. Would doing a factory reset and flashing a new ROM solve this problem?
Click to expand...
Click to collapse
What ROM are you on...Gingerbread or ICS?
you must be on a custom rom or you on stock, rooted?
---------- Post added at 04:48 PM ---------- Previous post was at 04:40 PM ----------
ok need to go into CWM and flash these files, should correct it, I had this issue on a ROM dont recall which one or it might of been on a rooted stock....
but before you do anything.....
download these files and put them on your sd card of the phone, NOT THE EXT memory card, you are gonna flash them like you would a ROM ok, in cwm, you can flash them back to back while you are in CWM...kk
download this file first and flash this file first: FLASH ME FIRST
download this file second and flash it second: FLASH ME SECOND
bigjoe2675 said:
What ROM are you on...Gingerbread or ICS?
you must be on a custom rom or you on stock, rooted?
Click to expand...
Click to collapse
I'm on Gingerbread, MIUI 2.3.9
lukas_s said:
I'm on Gingerbread, MIUI 2.3.9
Click to expand...
Click to collapse
try what I suggested and let us know if it works...kk
Didn't seem to work. Still can't install BusyBox. I'm not sure what kinda bearing that has on my wifi, my wifi just stopped working when the BusyBox update failed this morning.
lukas_s said:
Didn't seem to work. Still can't install BusyBox. I'm not sure what kinda bearing that has on my wifi, my wifi just stopped working when the BusyBox update failed this morning.
Click to expand...
Click to collapse
check the MIUI thread...
http://forum.xda-developers.com/showthread.php?t=1294549
I think MIUI occasionally loses recovery. Possible kernel issue.
Read through the thread to see if you can get some additional info.
I'm not sure if it has any bearing on your wifi..possible.
If you know how, you can try extracting the kernel from MIUI rom and reflashing just the kernel using SGS kernel flasher to retain your data.
qkster said:
check the MIUI thread...
http://forum.xda-developers.com/showthread.php?t=1294549
I think MIUI occasionally loses recovery. Possible kernel issue.
Read through the thread to see if you can get some additional info.
I'm not sure if it has any bearing on your wifi..possible.
If you know how, you can try extracting the kernel from MIUI rom and reflashing just the kernel using SGS kernel flasher to retain your data.
Click to expand...
Click to collapse
I definitely don't know how to do that haha. I'm a noob when it comes to this whole game, although I'm slowly learning.
Do you think doing a factory reset, wiping everything, and then flashing a new ROM might fix my issue? I did want to try out one of the new ICS ROMs, so if that will fix my problem I might as well go ahead and try one of them out.
Flashing Uniporn seemed to have fixed my issue. I first re-flashed MIUI and that didn't solve anything, so I guess the issue was with MIUI? Just odd that the wifi would drop out after using it flawlessly for 4 months.
Oh well, got something new to play with again. Thanks for the help guys!
lukas_s said:
Flashing Uniporn seemed to have fixed my issue. I first re-flashed MIUI and that didn't solve anything, so I guess the issue was with MIUI? Just odd that the wifi would drop out after using it flawlessly for 4 months.
Oh well, got something new to play with again. Thanks for the help guys!
Click to expand...
Click to collapse
that bld of miui, i was reading was not stable, idk...coming from the other miui users, but each user has a their ver of the story...
but glad it worked out, thx qkster...and don't forget to thx Nun for the rom he worked on...Uniporn
I was hoping to try out one of the 4.2 builds tonight, but every time I try to flash one through TWRP it just says "Failed"; I've tried CM10.1 and Eclipse ROM and they both had the same result. Also tried redownloading ROMs and re-copying them to my SD card, still no change. Can anyone tell me what I'm doing wrong here? I've never had a problem flashing any ROM before.
Devilicus said:
I was hoping to try out one of the 4.2 builds tonight, but every time I try to flash one through TWRP it just says "Failed"; I've tried CM10.1 and Eclipse ROM and they both had the same result. Also tried redownloading ROMs and re-copying them to my SD card, still no change. Can anyone tell me what I'm doing wrong here? I've never had a problem flashing any ROM before.
Click to expand...
Click to collapse
What version of TWRP are you running?
If you haven't done it lately, I would suggest updating your twrp to the latest and trying again.
I'm running the newest TWRP (I think), version 2.4.1.0
Devilicus said:
I'm running the newest TWRP (I think), version 2.4.1.0
Click to expand...
Click to collapse
Weird. I am on that same version and have been flashing 4.2 roms for the last few weeks without any issues.
A few things I would try:
-Double check the md5 of the rom you are flashing
-Make sure it is a d2vzw rom
-Wipe caches, delete user data and wipe system
-Put the rom on the internal sdcard before flashing.
Other than that, I got nothing
Relentless D said:
Weird. I am on that same version and have been flashing 4.2 roms for the last few weeks without any issues.
A few things I would try:
-Double check the md5 of the rom you are flashing
-Make sure it is a d2vzw rom
-Wipe caches, delete user data and wipe system
-Put the rom on the internal sdcard before flashing.
Other than that, I got nothing
Click to expand...
Click to collapse
Damn, yeah I can't figure it out; all the ones I've tried were Verizon ones, made sure to wipe everything as usual, tried putting it on the internal SD card and the external, won't work on either one. Very frustrating. But thanks for the help anyway
Ok, I think I figured out the problem (won't be sure until I try it), but I think what happened is I edited my build.prop to the Sprint GS3 to get Google Wallet to work, forgot to change it back, and updated TWRP (which installed the Sprint version, not Verizon), and that's why the flashes are failing. So if any other people are having the same problem, that might be why. Yes I'm an idiot lol. Hopefully this fixes it
Try carbon ROM.
First to work for me.
Sent from my SCH-I535 using xda app-developers app
Devilicus said:
Ok, I think I figured out the problem (won't be sure until I try it), but I think what happened is I edited my build.prop to the Sprint GS3 to get Google Wallet to work, forgot to change it back, and updated TWRP (which installed the Sprint version, not Verizon), and that's why the flashes are failing. So if any other people are having the same problem, that might be why. Yes I'm an idiot lol. Hopefully this fixes it
Click to expand...
Click to collapse
What baseband [modem] do you have installed? ...and some more info if build prop wasn't the issue. Would also be interested if, "but I think what happened is I edited my build.prop", was the issue and you fixed it. Let us know. Goodluck
JohnAreBee said:
What baseband [modem] do you have installed? ...and some more info if build prop wasn't the issue. Would also be interested if, "but I think what happened is I edited my build.prop", was the issue and you fixed it. Let us know. Goodluck
Click to expand...
Click to collapse
Yeah it turns out that was the problem. I edited my build.prop to match the Sprint GS3, so I could download Google Wallet from the Play Store and use it. I just never bothered to change the build.prop back. And when I updated TWRP through GooManager, it assumed I had a Sprint GS3 and installed the wrong recovery. When I flashed the correct Verizon version of TWRP everything worked fine. Thanks for the suggestions everyone
Devilicus said:
Yeah it turns out that was the problem. I edited my build.prop to match the Sprint GS3, so I could download Google Wallet from the Play Store and use it. I just never bothered to change the build.prop back. And when I updated TWRP through GooManager, it assumed I had a Sprint GS3 and installed the wrong recovery. When I flashed the correct Verizon version of TWRP everything worked fine. Thanks for the suggestions everyone
Click to expand...
Click to collapse
Good call. Might be worth mentioning over in the wallet thread. It could save someone the headache you just experienced. Congrats on getting it working.
Sent from my SCH-I535 using Tapatalk 2
Tried different ROMs & kernels, tried wiping everything and re-flashing, tried flashing the latest RUU(including firmware), changed recovery, did everything I can, the dialer still FCs when I try to make a call.
Driving me crazy.
I used different recoveries as well. TWRP & CWM & Stock after RUU flash.
I do remember using CWM recovery though, but it is the official one.
BreatheHT said:
Tried different ROMs & kernels, tried wiping everything and re-flashing, tried flashing the latest RUU(including firmware), changed recovery, did everything I can, the dialer still FCs when I try to make a call.
Driving me crazy.
I used different recoveries as well. TWRP & CWM & Stock after RUU flash.
I do remember using CWM recovery though, but it is the official one.
Click to expand...
Click to collapse
Well, I don't think a kernel could have anything to do with it. I think you need to backup your ROM. Then go into recovery and wipe system. Then flash the stock AT&T rooted ROM with nothing else, then try.
Mister J said:
Well, I don't think a kernel could have anything to do with it. I think you need to backup your ROM. Then go into recovery and wipe system. Then flash the stock AT&T rooted ROM with nothing else, then try.
Click to expand...
Click to collapse
i've tried everything like mentioned in the original post.... EVEN RUU
BUT AOKP roms works fine.
I'm started having the same problem this morning on every single sense ROM that I tried. I finally had to flash CM because I needed to call someone. RUU, wiping everything, different radios and different recoveries, nothing worked.
Sent from my One X using xda app-developers app
tried everything possible -_-
NobodY??????
I'm going to try a few other things when I get a chance, hopefully tomorrow. I would like to get this solved.
Sent from my One X using xda app-developers app
BreatheHT said:
NobodY??????
Click to expand...
Click to collapse
If you ruu and the problem still exists then its hardware related
Sent from my VENOMized HoxL
area51avenger said:
If you ruu and the problem still exists then its hardware related
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
If it's hardware related then why does the dialer work perfectly with CM?
Sent from my One X using xda app-developers app
sweeterman said:
If it's hardware related then why does the dialer work perfectly with CM?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Yep it can't be hardware.
Have you checked HTC for a bug update? I know they have had these problems in the past. Might not hurt to check.
Sent from my HTC One X using xda premium
This sounds a heck of a lot like the issue that cropped up with the old hacked (unofficial) version of CWM, way back last summer. It seemed that going from CM to CleanROM using CWM was the root cause (although I don't think the exact cause was ever discovered), and the oddest thing is that flashing different ROMs and even RUU didn't solve the issue. It was pretty much the event that got most of us to swear off the unofficial CWM, until it finally went official this month.
I think (but this is digging deep in my memory banks) some folks were able to resolve the dialer FC issue by going back to a known good CWM nandroid, then I think going to TWRP after that, and flashing a new ROM. But you might use the search function to find the specifics.
Might be something different going on here. But the persistent dialer FC (even after RUU) combined with CWM and CM10 is looking a bit suspicious.
redpoint73 said:
This sounds a heck of a lot like the issue that cropped up with the old hacked (unofficial) version of CWM, way back last summer. It seemed that going from CM to CleanROM using CWM was the root cause (although I don't think the exact cause was ever discovered), and the oddest thing is that flashing different ROMs and even RUU didn't solve the issue. It was pretty much the event that got most of us to swear off the unofficial CWM, until it finally went official this month.
I think (but this is digging deep in my memory banks) some folks were able to resolve the dialer FC issue by going back to a known good CWM nandroid, then I think going to TWRP after that, and flashing a new ROM. But you might use the search function to find the specifics.
Might be something different going on here. But the persistent dialer FC (even after RUU) combined with CWM and CM10 is looking a bit suspicious.
Click to expand...
Click to collapse
Yeah I've read threads and posts having the same problem.... But I've never used unofficial CWM that's the weird thing... And I don't really have a good backup...
redpoint73 said:
This sounds a heck of a lot like the issue that cropped up with the old hacked (unofficial) version of CWM, way back last summer. It seemed that going from CM to CleanROM using CWM was the root cause (although I don't think the exact cause was ever discovered), and the oddest thing is that flashing different ROMs and even RUU didn't solve the issue. It was pretty much the event that got most of us to swear off the unofficial CWM, until it finally went official this month.
I think (but this is digging deep in my memory banks) some folks were able to resolve the dialer FC issue by going back to a known good CWM nandroid, then I think going to TWRP after that, and flashing a new ROM. But you might use the search function to find the specifics.
Might be something different going on here. But the persistent dialer FC (even after RUU) combined with CWM and CM10 is looking a bit suspicious.
Click to expand...
Click to collapse
Should I flash CWM again? Because last time for some reason CWM Touch(official) stopped working for no reason(cannot get into recovery, screen flashes and reboots) so I flashed TWRP again, and I think that's when the problem began to show.
BreatheHT said:
Should I flash CWM again? Because last time for some reason CWM Touch(official) stopped working for no reason(cannot get into recovery, screen flashes and reboots) so I flashed TWRP again, and I think that's when the problem began to show.
Click to expand...
Click to collapse
Maybe try an older version of TWRP, if youre on one of the newer versions. I've heard a LOT of ppl having issues with the 2.4.x.x versions.
Sent from my now S-Off HTC OneXL
BreatheHT said:
Should I flash CWM again?
Click to expand...
Click to collapse
I'd say it worth a try.
---------- Post added at 10:35 AM ---------- Previous post was at 10:33 AM ----------
BreatheHT said:
Yeah I've read threads and posts having the same problem.... But I've never used unofficial CWM that's the weird thing...
Click to expand...
Click to collapse
I don't think it was ever properly discussed whether whatever caused this bug in ythe "old" hacked CWM was resolved (or not an issue) with the "official" CWM. Not trying to knock CWM, and those that worked hard on it. Its just been a lingering question in my mind since it went official. But I'm also a skeptic by nature.
I installed the latest CWM and flashed the rooted att 3.18 rom the dialer now works now. I don't know if there is a bug that once you use CWM, you can't use TWRP. It seems very odd though.
sweeterman said:
I installed the latest CWM and flashed the rooted att 3.18 rom the dialer now works now. I don't know if there is a bug that once you use CWM, you can't use TWRP. It seems very odd though.
Click to expand...
Click to collapse
Good to know...I was thinkin bout flashing CWM, but I guess if I haven't had issues with TWRP, "don't fix what ain't broken."
Sent from my now S-Off HTC OneXL
redpoint73 said:
I'd say it worth a try.
---------- Post added at 10:35 AM ---------- Previous post was at 10:33 AM ----------
I don't think it was ever properly discussed whether whatever caused this bug in ythe "old" hacked CWM was resolved (or not an issue) with the "official" CWM. Not trying to knock CWM, and those that worked hard on it. Its just been a lingering question in my mind since it went official. But I'm also a skeptic by nature.
Click to expand...
Click to collapse
Thanks bro
sweeterman said:
I installed the latest CWM and flashed the rooted att 3.18 rom the dialer now works now. I don't know if there is a bug that once you use CWM, you can't use TWRP. It seems very odd though.
Click to expand...
Click to collapse
Will try, thanks bro!
elfysrfr said:
Maybe try an older version of TWRP, if youre on one of the newer versions. I've heard a LOT of ppl having issues with the 2.4.x.x versions.
Sent from my now S-Off HTC OneXL
Click to expand...
Click to collapse
I'm using 2.3.x.x haha 2.4.x.x is so bad... Or not compatible...
Had anybody seen a situation where the recovery won't keep the correct date and time? I've flashed TWRP 2.7.1.0, 2.8.0.1, and the latest Philz, and all of them kept changing the time, the timezone, and the date... and they were acting a little buggy in their responsiveness.
Thoughts?
WarAxe said:
Had anybody seen a situation where the recovery won't keep the correct date and time? I've flashed TWRP 2.7.1.0, 2.8.0.1, and the latest Philz, and all of them kept changing the time, the timezone, and the date... and they were acting a little buggy in their responsiveness.
Thoughts?
Click to expand...
Click to collapse
I've experienced the same issue since I got my S5. KT TWRP 2.8.1.0 doesn't have that problem. It also fixes the backup to extSD problem, if you were experiencing that.
Ramer84015 said:
I've experienced the same issue since I got my S5. KT TWRP 2.8.1.0 doesn't have that problem. It also fixes the backup to extSD problem, if you were experiencing that.
Click to expand...
Click to collapse
THANKS! I had KT's downloaded but didn't flash it yet... I certainly will now. And yes, the extSD issue bit me, too.
Nope... date is 1/1/2014 and the time is 3 hours lagging for the timezone.
Let's hope at the very least my nandroid backups won't disappear.
WarAxe said:
Nope... date is 1/1/2014 and the time is 3 hours lagging for the timezone.
Let's hope at the very least my nandroid backups won't disappear.
Click to expand...
Click to collapse
Try this: Using something like Root Explorer, look for the TWRP folder on your internal SD card. There's a file called ".twrps". It's the config file for TWRP. Delete it and then boot back into TWRP. You'll have to redo your setting (timezone, screen timeout etc.). See if that fixes it. If that doesn't do it, not sure what else will.
Ramer84015 said:
Try this: Using something like Root Explorer, look for the TWRP folder on your internal SD card. There's a file called ".twrps". It's the config file for TWRP. Delete it and then boot back into TWRP. You'll have to redo your setting (timezone, screen timeout etc.). See if that fixes it. If that doesn't do it, not sure what else will.
Click to expand...
Click to collapse
I had tried peeking into the file with Notepad++ but nothing jumped out at me. Now I feel silly for not trying what you suggested.
I deleted it and it had no effect. The one I deleted and the one it created had the wrong date/time stamps on them... as did the two backups I created (both in metadata and filename convention).
On the bright side... my two backups are as yet undeleted.
WarAxe said:
I had tried peeking into the file with Notepad++ but nothing jumped out at me. Now I feel silly for not trying what you suggested.
I deleted it and it had no effect. The one I deleted and the one it created had the wrong date/time stamps on them... as did the two backups I created (both in metadata and filename convention).
On the bright side... my two backups are as yet undeleted.
Click to expand...
Click to collapse
Very strange, I was sure that was it. My date/time have been correct since using it. The only other thing I may have done was using KT Kernel as well, but I don't think that was it. If you decide to try KT Kernel and want to go back to stock kernel, here's a link for stock: http://forum.xda-developers.com/showpost.php?p=54632862&postcount=1702
Another thought: What version is your firmware? Should be NE5. If not, here's that link: http://forum.xda-developers.com/showthread.php?t=2798079
Ramer84015 said:
Very strange, I was sure that was it. My date/time have been correct since using it. The only other thing I may have done was using KT Kernel as well, but I don't think that was it. If you decide to try KT Kernel and want to go back to stock kernel, here's a link for stock: http://forum.xda-developers.com/showpost.php?p=54632862&postcount=1702
Another thought: What version is your firmware? Should be NE5. If not, here's that link: http://forum.xda-developers.com/showthread.php?t=2798079
Click to expand...
Click to collapse
Thanks for the links.
I didn't flash the KT Kernel because the post said it needed to be flashed onto a TouchWiz based ROM... and right now I have PacMan (AOKP). I had MOAR (NE5) installed for a bit but I'm not used to stock. Truthfully, MOAR had everything I could want... I may just have to get over my snootiness.
Oh, it's coming back to me... with MOAR I was getting a lot of error popups of processes stopping running. i think "acore" was a common one. I could have troubleshot but didn't.
WarAxe said:
Oh, it's coming back to me... with MOAR I was getting a lot of error popups of processes stopping running. i think "acore" was a common one. I could have troubleshot but didn't.
Click to expand...
Click to collapse
Make sure your backup works and come on over I'm a big supporter of MOAR! Do a clean install though and I bet 99.9% of your problems will be solved
Ramer84015 said:
Make sure your backup works and come on over I'm a big supporter of MOAR! Do a clean install though and I bet 99.9% of your problems will be solved
Click to expand...
Click to collapse
There's the main install 2.1, and the new stuff 1.7, and of course Gapps. Do folks typically flash them all together... Or separately sequentially?
My clean install is usually wiping cache, dalvik, data, and system.
WarAxe said:
There's the main install 2.1, and the new stuff 1.7, and of course Gapps. Do folks typically flash them all together... Or separately sequentially?
My clean install is usually wiping cache, dalvik, data, and system.
Click to expand...
Click to collapse
MOAR is TW, so gapps is included. My FAQ and guide for MOAR may help you get a feel for it.
Ramer84015 said:
MOAR is TW, so gapps is included. My FAQ and guide for MOAR may help you get a feel for it.
Click to expand...
Click to collapse
Okay... MOAR's on there now. I'll read up and tweak to the extent I'm able and see if I have any questions.
WarAxe said:
Okay... MOAR's on there now. I'll read up and tweak to the extent I'm able and see if I have any questions.
Click to expand...
Click to collapse
Feel free to post any questions on the Q&A thread. :good: