Related
I've searched and couldn't find. My bad if i missed it.
So I flashed MIUI and followed the steps of each MIUI rom thread. Everything works perfectly except for one thing. The GPS. It seems that everyone gets the gps to work except for me o.o. well it worked once but after that each time i load up the gps, the app freezes and my phone keeps vibrating. (i have to set the phone to silent using volume keys to stop it) after i stop it every time i hit my home key it vibrates again, nonstop. then everything i try to start up FCs anyone got a solution for this ?
i tried the privacy>reset phone thing but didnt work either.
i've also tried http://forum.xda-developers.com/show....php?t=1370910
by the way i tested this with other roms. every rom i tried it on worked. the only roms that didnt are the MIUIs (all of em)
and no i did not drop the phone in water nor is there any sort of damages to the phone.
its happening because you didnt post this in the right section
try reflashing. . . . a good rom. . . . like ics or something.
posted in Q and A. not one reply. i tried multiple roms. every miui/cm7 and the ics rom. same problem.
Try to ODIN back to Froyo, then load GB boot loaders via ODIN and flash the ROMs.Might help.
Agreed with above, when in doubt Odin back to stock
Vibrant+MIUI=Happiness
sada23 said:
Try to ODIN back to Froyo, then load GB boot loaders via ODIN and flash the ROMs.Might help.
Click to expand...
Click to collapse
i did ODIN back to froyo. i dont think i tried the bootloader thing though. ill give it a shot. thanks.
I had this same problem for awhile. I used the Yet Another GPS fix and after that I would wipe the GPS data and force it to download new data. This would fix it every time.
THEN today I updated to the new MIUI-112300 and it worked first try without me having to tweak anything.
Good luck!
lams09, please don't re-post the same thread twice but with slightly different names... Anyways, I posted this in the other thread the OP posted asking the exact same question...
"Try flashing MIUI via my guide."
lizeroy said:
I had this same problem for awhile. I used the Yet Another GPS fix and after that I would wipe the GPS data and force it to download new data. This would fix it every time.
THEN today I updated to the new MIUI-112300 and it worked first try without me having to tweak anything.
Good luck!
Click to expand...
Click to collapse
did you use the official MIUI ?
yes. clear your agps data and re download before using gps
I had used the amaze 4g all in one tool kit to unlock my bootloader, install a custom recovery, and then installed a custom rom (bullet proof 2.5) along with the provided kernel to go with it.
The phone worked great for a few days, then I noticed that it was acting like the wireless network radios were turned off in the software. They were still enabled so I rebooted and it fixed the problem for a little while.
Now my phone will only give me the com.android.phone has stopped working error and will not let me turn on the wireless network radios.
I have tried complete wipe of the phone and re-installation of the custom rom. I have tried different, yet still recommend, custom kernels, as well as different recoveries all with the same issue.
Any help would be greatly appreciated. I tried searching with out any good results.
Thanks.
Are you a Tmobile user?
Double0EK said:
Are you a Tmobile user?
Click to expand...
Click to collapse
Yeah. Even tried a new simcard even though I didnt think it would do any good.
toyoter91 said:
I had used the amaze 4g all in one tool kit to unlock my bootloader, install a custom recovery, and then installed a custom rom (bullet proof 2.5) along with the provided kernel to go with it.
The phone worked great for a few days, then I noticed that it was acting like the wireless network radios were turned off in the software. They were still enabled so I rebooted and it fixed the problem for a little while.
Now my phone will only give me the com.android.phone has stopped working error and will not let me turn on the wireless network radios.
I have tried complete wipe of the phone and re-installation of the custom rom. I have tried different, yet still recommend, custom kernels, as well as different recoveries all with the same issue.
Any help would be greatly appreciated. I tried searching with out any good results.
Thanks.
Click to expand...
Click to collapse
are you running joes "one good rom"? dude it says right in the op
Attention 2: on the first start "com.android.phone" process will FC, it is normal.
It's because of Toggle2G app. Just open that app and give it permission to run.
mrmako777 said:
are you running joes "one good rom"? dude it says right in the op
Attention 2: on the first start "com.android.phone" process will FC, it is normal.
It's because of Toggle2G app. Just open that app and give it permission to run.
Click to expand...
Click to collapse
I actually stated in my first post what rom I was running when all this happened.
I have tried Joes "one good rom" and followed all his kernel and set up instructions with no luck. On his rom I don't get the error message, but all of the wireless network options are grayed out. I am starting to think it might be something hardware.
toyoter91 said:
I actually stated in my first post what rom I was running when all this happened.
I have tried Joes "one good rom" and followed all his kernel and set up instructions with no luck. On his rom I don't get the error message, but all of the wireless network options are grayed out. I am starting to think it might be something hardware.
Click to expand...
Click to collapse
doh! shame on me for not seeing that i would say if worse comes to worse, reflash the stock rom and see if youre up and running. if its still not working, then id say maybe send it in for warranty
mrmako777 said:
doh! shame on me for not seeing that i would say if worse comes to worse, reflash the stock rom and see if youre up and running. if its still not working, then id say maybe send it in for warranty
Click to expand...
Click to collapse
No worries. I am actually in the process of finding and flashing the stock rom back onto it, going to try and put everything back to stock and see what happens.
Having a similar problem
toyoter91 said:
No worries. I am actually in the process of finding and flashing the stock rom back onto it, going to try and put everything back to stock and see what happens.
Click to expand...
Click to collapse
Hi. I decided to add to this thread instead of starting a new one since i am having a similar problem. The originator never said if he was able to solve the problem. I was using the Energy ROM (http://forum.xda-developers.com/showthread.php?t=1362759) (ICS, S-ON) and everything was fine. I decided to try the Speed ROM (project "butter" http://forum.xda-developers.com/showthread.php?t=1623184) which is Jellybean based. I did a full wipe, and after installing it I got the same com.android.phone error. I got it to stop, but then started having other issues like Superuser, BusyBox, and Titanium Backup unable to get root access. Unable to find any other solutions, I decided to restore to stock, which went fine (well I had to try a few times as I haven't done it before). After that, and having the phone working fine back at stock ICS I reflashed the Speed ROM. I ended up with the same issue. I wiped again and returned to the Energy ROM and it seems to be working fine. My quesiton is, why is the Speed ROM not working on my phone? When it flashed there were no issues, and I followed the instrucitons exactly.
I would post in the Speed ROM forum but I don't have enough posts yet since I am usually able to find answers by searching.
BillyD325 said:
Hi. I decided to add to this thread instead of starting a new one since i am having a similar problem. The originator never said if he was able to solve the problem. I was using the Energy ROM (http://forum.xda-developers.com/showthread.php?t=1362759) (ICS, S-ON) and everything was fine. I decided to try the Speed ROM (project "butter" http://forum.xda-developers.com/showthread.php?t=1623184) which is Jellybean based. I did a full wipe, and after installing it I got the same com.android.phone error. I got it to stop, but then started having other issues like Superuser, BusyBox, and Titanium Backup unable to get root access. Unable to find any other solutions, I decided to restore to stock, which went fine (well I had to try a few times as I haven't done it before). After that, and having the phone working fine back at stock ICS I reflashed the Speed ROM. I ended up with the same issue. I wiped again and returned to the Energy ROM and it seems to be working fine. My quesiton is, why is the Speed ROM not working on my phone? When it flashed there were no issues, and I followed the instrucitons exactly.
I would post in the Speed ROM forum but I don't have enough posts yet since I am usually able to find answers by searching.
Click to expand...
Click to collapse
That's a common problem with SpeedRom and some other as well. Re-flash the SpeedRom, after it boot-up, go to Google Play store and download SuperSU -not Superuser -, open SuperSU and update binary. After that you can install busy box and run Titanium ....
antiquezip said:
That's a common problem with SpeedRom and some other as well. Re-flash the SpeedRom, after it boot-up, go to Google Play store and download SuperSU -not Superuser -, open SuperSU and update binary. After that you can install busy box and run Titanium ....
Click to expand...
Click to collapse
Thank you! After I posted I ran across somehting in the speed rom thread that made me go back to the original post. Sure enough, there is a download link for SuperSU which it says you need to flash to gain root after installng the ROM. I guess I read the instructions above, scrolled down to the rom download link, and then stopped. I will try this again with what you suggested when I have time in the next day or two.
BillyD325 said:
Thank you! After I posted I ran across somehting in the speed rom thread that made me go back to the original post. Sure enough, there is a download link for SuperSU which it says you need to flash to gain root after installng the ROM. I guess I read the instructions above, scrolled down to the rom download link, and then stopped. I will try this again with what you suggested when I have time in the next day or two.
Click to expand...
Click to collapse
I had this error factory reset stop the error.
This belongs in Q&A.
Thread Moved.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"If you choose not to decide, you still have made a choice"
Sent from my Galaxy Note (i717), using XDA Premium.
Okay, I have gotten so blasted close with getting a custom rom on this phone. I can get them installed now and they are wonderful I tried gummy and aokp but for the life of me I can not get data to work I can not make or recieve phone calls. I am in roaming all the time too. I have gone through all settings and scoured the forum and I can not find an answer anywhere. Am I missing something totally obvious here? Does anyone maybe have any suggestion? Thank you guys for your help. It's just frustrating that I am so close.
debinnv said:
Okay, I have gotten so blasted close with getting a custom rom on this phone. I can get them installed now and they are wonderful I tried gummy and aokp but for the life of me I can not get data to work I can not make or recieve phone calls. I am in roaming all the time too. I have gone through all settings and scoured the forum and I can not find an answer anywhere. Am I missing something totally obvious here? Does anyone maybe have any suggestion? Thank you guys for your help. It's just frustrating that I am so close.
Click to expand...
Click to collapse
What is the status of your Photon currently? Assuming it is rooted and unlocked, running what rom? Please provide info on what rom you are on now, which one you flashed from, and what process you used to get where you are. The more info provided the easier it will be to help.
Well lets see, currently I am back on stock, but here is what I did. I rooted, unlocked, installed CWM 5.0.2.7 I also flashed jokers recoveryv3 ( I follow QB's videos) So then I installed the gummy rom using this process. Format system, format data, format cache, wipe cache then dalvik cache. flash rom, flash rom again ( now I did not reboot into recovery after I flashed the rom the first time) I just went straight to install rom again. flash gapps, fix permissions. Reboot up and good loving it all. Waited 15 min then rebooted again. That's it. So I am at a loss. Thanks for help if you need any other info please let me know.
Oh I am on 2.3.4 with 198_7 also
In your system settings did you have "home only" or "automatic" selected for your roaming settings? For a lot of these roms, "automatic" is forced roam. And then if you didn't have roaming data enabled, that would explain why you were constantly roaming with no data.
Sent from my MB855 using XDA
Thanks so much .
I did have automatic checked but I did have roaming data enabled also. I flipped it around too with home only. I am truly beginning to think my phone is just plain "off " who knows. It's a shame though, I mean not that stock is bad on this phone but the custom roms are so much better imo. This is the first phone I have ever had a problem with. I have been flashing phones for years. Think I started with a HTC Mogul. That was a solid phone LOL
Does CM7 work for you? If it does then I reckon flashing that and setting it up, then instead of doing a full wipe keep your data and flash CM9 based rom over it, fix permissions and take it from there.
I have not tried CM7 but I can, sure can't hurt to try at this point. Thanks, I will give that a try tomorrow.
Have you tried *#*#4636#*#*? Sometimes flashing changes the radio in that menu. Be careful though, changing something can really Bork your phone. It should be on cdma prl I think
sent from my CM7 MoPho
Deb, my photon has never been kind to me with the 'flash twice' method. It always results in no data. Try cm9 again, but this time wipe cache, system, data, and dalvik, install version 3.1 of cm9, boot into it, reboot to recovery, wipe cache and dalv, then install the latest cm9 version. Always works for me. Good luck
Sent from my MB855 using XDA
Morning all, your all are great. Okay so I am ready to start again. I'm at stock right now so I need to get her all set up again. (Yes my phone is a she) Acvice, I am going to try your method first will let you know in a bit.
Looks like joker's site may be down so I need to try and find the 2 cm9 roms
I have this rom saved already on my computer
beta-0.6.9.1-cm-9.0.0-RC0-sunfire-UNOFFICIAL-signed.zip
Wonder if I should try that one or just wait
After I install CWM 5.2.0.7 do I also need to flash joker's v3 recovery?
debinnv said:
After I install CWM 5.2.0.7 do I also need to flash joker's v3 recovery?
Click to expand...
Click to collapse
You don't have to, but I recommend it.
Sent from my MB855 using XDA
I think th3bill has 0.3.1 in his fixes thread
http://www.mediafire.com/?y7no1r460d4o8zf
sent from my CM7 MoPho
Thanks, will also do jokers and thanks for the link bullfrog. dl'ng now
debinnv said:
Thanks, will also do jokers and thanks for the link bullfrog. dl'ng now
Click to expand...
Click to collapse
Glad someone provided you with that 3.1 link. Looking forward to see if it works out for ya.
By the way, you will know it worked if when you boot up in 3.1 you have working data. Flashing the newer version after that will essentially just update everything.
Deb, I take it the flash of 0.3.1 didn't work? Did you have data and then lose it when you flashed 0.6.9.3? What were your exact steps. I just rooted/unlocked and flashed my f-in-law's new photon and it worked just fine. Lemme know what you did and maybe I can help more
sent from my CM7 MoPho
Thanks bullfrog that's nice of you but honestly I'm good now As you know.
I didn't even try to install 0.3.1. I kept thinking about it, seeing I had no luck with 2 others previously so I decided to go the MIUI route and I'm a happy camper with that one. I am a flashaholic for sure, as we all are here. I am thinking though, I am gonna just be happy with where I am at for now. Of course I will most likely decide to give another rom a try at some point.
Of course I am already eyeing a few Samsung Epic touch's on ebay. I hear that one can be a brick just waiting to happen....weeeee I am having way too much fun
I'm glad you made it to MIUI. if you ever want to try cm9 or and of the similar ones (aokp, gummy, paranoid) I would suggest flashing that 0.3.1 first, then updating to the latest cm9, then flashing the variant
sent from my CM7 MoPho
I need some help. I have the latest version of Adobe Flash Player (Version 11.1.115.69) installed on my stock (rooted/unlocked) Verizon Note 2.
On some videos (that are not a mobile version or through the video player) I get this issue where the sound works fine, but the video is completely messed up. It looks like a bunch of colored lines. The lines move as the video goes along. I don't know what to make of it because it only happens on some videos. Also, this has happened with every version of Flash that I have ever tried (which is all of them, as far as I know) with this device. Anyone else have this problem? In any case, can someone on a stock Verizon Note 2 please go to the page below and try and watch the movie? The lines problem has happened every time I have gone to that page and tried to watch the movie, both on the stock browser and with Dolphin Browser. I attached a screenshot of what happens below.
http://viooz.co/movies/19479-monster...sity-2013.html
Any help regarding how to fix this would be most appreciated!
By the way, that movie is an excellent sequel to the first Monsters Inc. and I recommend it.
(And there is no need to freak out about not paying to watch the movie; I am planning to purchase it for my Nephew in the near future.)
nh97103 said:
I need some help. I have the latest version of Adobe Flash Player (Version 11.1.115.69) installed on my stock (rooted/unlocked) Verizon Note 2.
On some videos (that are not a mobile version or through the video player) I get this issue where the sound works fine, but the video is completely messed up. It looks like a bunch of colored lines. The lines move as the video goes along. I don't know what to make of it because it only happens on some videos. Also, this has happened with every version of Flash that I have ever tried (which is all of them, as far as I know) with this device. Anyone else have this problem? In any case, can someone on a stock Verizon Note 2 please go to the page below and try and watch the movie? The lines problem has happened every time I have gone to that page and tried to watch the movie, both on the stock browser and with Dolphin Browser. I attached a screenshot of what happens below.
http://viooz.co/movies/19479-monster...sity-2013.html
Any help regarding how to fix this would be most appreciated!
By the way, that movie is an excellent sequel to the first Monsters Inc. and I recommend it.
(And there is no need to freak out about not paying to watch the movie; I am planning to purchase it for my Nephew in the near future.)
Click to expand...
Click to collapse
I would venture to say that the problem is the site not flash. So far I haven't run across this problem. Try clean wiping and re-flashing. Also what stock rooted ROM are you running?
Hey. Most likely if you are running stock verizon bloated touchwiz, verizon likes to include a file/apk that is hidden that blocks flash player. To get rid of this you generally have to be rooted. After rooted you can either install a custom rom (any will do) OR if you want to stay stock you can use titanium back up and browse through your list off applications. You will noticed a "flash disable" application in red or something like that. Selected it and uninstall it. Once you do that you should have the flash player working properly.
dragonstalker said:
I would venture to say that the problem is the site not flash. So far I haven't run across this problem. Try clean wiping and re-flashing. Also what stock rooted ROM are you running?
Click to expand...
Click to collapse
It has happened to me on far too many sites for it to be their fault. I am on 4.1.1 I605VRALJB. I haven't updated my phone since I bought it in December (bad experiences with updates from Motorola). While this problem is frustrating, I don't think I want to wipe my phone just yet.
monkeyass408 said:
Hey. Most likely if you are running stock verizon bloated touchwiz, verizon likes to include a file/apk that is hidden that blocks flash player. To get rid of this you generally have to be rooted. After rooted you can either install a custom rom (any will do) OR if you want to stay stock you can use titanium back up and browse through your list off applications. You will noticed a "flash disable" application in red or something like that. Selected it and uninstall it. Once you do that you should have the flash player working properly.
Click to expand...
Click to collapse
Hey!
There are two apps that have the world flash in them. I froze them both with My backup Pro and it didn't fix it. Any idea what the name would be if it didn't have the world flash in it?
nh97103 said:
Hey!
There are two apps that have the world flash in them. I froze them both with My backup Pro and it didn't fix it. Any idea what the name would be if it didn't have the world flash in it?
Click to expand...
Click to collapse
What are the names of the apps? you might have frozen the app that runs flash which you want, and then youll have also frozen the app that blocks flash, so over all do you have no flash? (I dont know exacly im just speculating now from what ive read youve done)
edit: maybe try some simple things first, use yet another browser, such as nakedbrowser- its fast and flash works great in it. i would say maybe try unistalling then reinstalling flash, to a newer version http://forum.xda-developers.com/showthread.php?t=2190346 i forget its not on playstore anymore. mines currently at 11.1.115.48
MunkinDrunky said:
What are the names of the apps? you might have frozen the app that runs flash which you want, and then youll have also frozen the app that blocks flash, so over all do you have no flash? (I dont know exacly im just speculating now from what ive read youve done)
edit: maybe try some simple things first, use yet another browser, such as nakedbrowser- its fast and flash works great in it. i would say maybe try unistalling then reinstalling flash, to a newer version http://forum.xda-developers.com/showthread.php?t=2190346 i forget its not on playstore anymore. mines currently at 11.1.115.48
Click to expand...
Click to collapse
The names of the apps are:
com.sec.android.app.FlashBarService (v1.0)
and
FlashAnnotate (v0.8.6) and FlashAnnotateSvc (v0.8.4)
I tried that browser and it still had the problem, both with that version of Flash and the newest one. I think I'll need to re-flash eventually.. I was hoping to avoid it.
nh97103 said:
The names of the apps are:
com.sec.android.app.FlashBarService (v1.0)
and
FlashAnnotate (v0.8.6) and FlashAnnotateSvc (v0.8.4)
I tried that browser and it still had the problem, both with that version of Flash and the newest one. I think I'll need to re-flash eventually.. I was hoping to avoid it.
Click to expand...
Click to collapse
no those are not flash unfreeze them. im sure you already did though. the flashbarservice is for multiwindow and not sure what flashannotatesvc is but its not flash player. since your on 4.1.1 still what version is that flash apk you have now?
MunkinDrunky said:
no those are not flash unfreeze them. im sure you already did though. the flashbarservice is for multiwindow and not sure what flashannotatesvc is but its not flash player. since your on 4.1.1 still what version is that flash apk you have now?
Click to expand...
Click to collapse
Yeah, I unfroze them when it didn't work. I'm on the newest version. 11.1.115.69
Do you know of any glitches/problems with the 4.1.2 update? Is it worth updating to?
nh97103 said:
Yeah, I unfroze them when it didn't work. I'm on the newest version. 11.1.115.69
Do you know of any glitches/problems with the 4.1.2 update? Is it worth updating to?
Click to expand...
Click to collapse
yeah ok well thats where my knowledge really ends as to what might be happening.
I understand your hesitation, but if flash is a thing you really want then that alone could be a reason to update. I have not had or seen any instability, or experienced any glitchyness myself and I have also only stuck to the touchwiz roms (simply personal preference). 4.1.2 on this device, well there isnt anything to fear, no getting burned here. lots o great roms to check out.
edit: oh and one last word if you want to stay as you are. did you try the 115.48 flash version?
MunkinDrunky said:
yeah ok well thats where my knowledge really ends as to what might be happening.
I understand your hesitation, but if flash is a thing you really want then that alone could be a reason to update. I have not had or seen any instability, or experienced any glitchyness myself and I have also only stuck to the touchwiz roms (simply personal preference). 4.1.2 on this device, well there isnt anything to fear, no getting burned here. lots o great roms to check out.
edit: oh and one last word if you want to stay as you are. did you try the 115.48 flash version?
Click to expand...
Click to collapse
Yeah, I have not had good luck with updates. I did try that version just now (and several other versions before now).
4.1.2 has been unlocked and rooted, but is it possible to get back to 4.1.1?
Thank you for trying to help! Really appreciate it!
nh97103 said:
Yeah, I have not had good luck with updates. I did try that version just now (and several other versions before now).
4.1.2 has been unlocked and rooted, but is it possible to get back to 4.1.1?
Thank you for trying to help! Really appreciate it!
Click to expand...
Click to collapse
ok I havent really worried about flash i guess on the custom roms there must be some libraries or plugins or something to have flash fully functional.
Make a full nandroid back up of what your on now. Im not 100% positive but if you want you can then just flash back to 4.1.1. Make sure you restore with the same version of the custom recovery you backed up with if you want to go baack.
You should probably also search that question. I believe it has been answered several times. I might have seen it in passing.
MunkinDrunky said:
ok I havent really worried about flash i guess on the custom roms there must be some libraries or plugins or something to have flash fully functional.
Make a full nandroid back up of what your on now. Im not 100% positive but if you want you can then just flash back to 4.1.1. Make sure you restore with the same version of the custom recovery you backed up with if you want to go baack.
You should probably also search that question. I believe it has been answered several times. I might have seen it in passing.
Click to expand...
Click to collapse
Right, because the backup backups the OS as well as your phone memory. That has always boggled my mind. So I could just restore that and be good.
One last question: When installing this update, I probably don't want to be unlocked, right? I know I can temporarily unroot so no problem there.
nh97103 said:
Right, because the backup backups the OS as well as your phone memory. That has always boggled my mind. So I could just restore that and be good.
One last question: When installing this update, I probably don't want to be unlocked, right? I know I can temporarily unroot so no problem there.
Click to expand...
Click to collapse
yes your nandoid will save the image of your system and data(if thats what you mean by phone memory) so youll restore you to that state.
no if your bootloader unlocked and all that, leave it. I recommend looking over droidstyle guide too, i usually do every now and again just to refresh my mind. You can simply flash a stock 4.1.2 rom check out http://forum.xda-developers.com/showthread.php?t=2387635 so look for one that is basically untouched except for being rooted and unlocked still. You can also try out any 4.1.2 rom too
Nah, jumping between threads is fun!
But seriously, is it completely necessary to factory reset before flashing that?
nh97103 said:
Nah, jumping between threads is fun!
But seriously, is it completely necessary to factory reset before flashing that?
Click to expand...
Click to collapse
Yup. Sorry for late resposnse. So um id suggest if you havent don anything yet. Update to latest recovery proabaly twrp since 8ts easy to use and it seems to be the most versatile (but some customs roms prefer clockwork) then back up efs modem boot system data for a full image of your 4.1.1 so you can be fully backed up. Then do the factory data reset wipe cache and dalvik in recovery after. Af6er wipe then flash rom.
Since you are rooted, you can download the latest version of flash and run it from the stock browser. Chrome has issues with it. I prefer the stock browser as it does exactly what Chrome does but with flash support. And I would suggest atleast upgrading to a 4.1.2 rom. There were alot of bug fixes between the 2.
I'm pleased to report that I flashed that 4.1.2 ROM and the flash player issue is gone.
I was pleasantly surprised to see my sdcard0 remain untouched after I wiped data from custom recovery.
nh97103 said:
I need some help. I have the latest version of Adobe Flash Player (Version 11.1.115.69) installed on my stock (rooted/unlocked) Verizon Note 2.
On some videos (that are not a mobile version or through the video player) I get this issue where the sound works fine, but the video is completely messed up. It looks like a bunch of colored lines. The lines move as the video goes along. I don't know what to make of it because it only happens on some videos. Also, this has happened with every version of Flash that I have ever tried (which is all of them, as far as I know) with this device. Anyone else have this problem? In any case, can someone on a stock Verizon Note 2 please go to the page below and try and watch the movie? The lines problem has happened every time I have gone to that page and tried to watch the movie, both on the stock browser and with Dolphin Browser. I attached a screenshot of what happens below.
Any help regarding how to fix this would be most appreciated!
By the way, that movie is an excellent sequel to the first Monsters Inc. and I recommend it.
(And there is no need to freak out about not paying to watch the movie; I am planning to purchase it for my Nephew in the near future.)
Click to expand...
Click to collapse
It is working for me. There is no problem
vidics4
Flash Player Issue
I think the problem lies with the website. Viooz.co is full of malwares and other viruses. I hate those pop up ads which just pop out on just one click.
There are many websites which you can rely upon :
www.solarmovie.me
www.movie25.ws
www.afdah.com
Hi all,
Long time lurker of XDA and Android user/modder since before Gingerbread. I want to apologize in advance if this post is either in the wrong section, and/or if something similar has already been answered/solved in another thread. I did multiple searches with nothing coming up as a direct hit, or even close for that matter.
I recently purchased an S4 from VZW (Mid-Late July). I rooted and installed TWRP 5.2.0.2 (Forgive me if that's not the exact version...) and flashed AOSP ROMs here and there. After a month or so, I started coming across an issue within all ROMs where I couldn't receive or make calls without my phone either freezing or rebooting. Anything I flashed, or modded, failed to remedy this. I tried different GApps packages, 4.2.2 and 4.3 ROMs, different kernels, and both radios, and absolutely NOTHING solved this. I searched everywhere (Even rootzwiki, forgive me fellow XDA members!), and could not find anyone with the same issue.
I attempted upgrading to TWRP 2.6.0.0 and even tried CWM, and that didn't help either. Eventually, things got so bad that I couldn't boot into ANY ROM, 4.2.2 or 4.3. After nearly 10 hours of trying to unbrick my phone, I finally managed to install Beanstalk 4.3, and while it was working incredibly buggy (Not Beanstalk's fault, the developer is a great developer!) nor could I make calls, I could still send texts and emails. I was able to FINALLY get the Odin3 application to work when I got home from work, and was able to flash the stock MDK image. From there I followed the steps to properly root and install TWRP 2.6.0.0. I installed Slim's Beta 5 4.3 ROM and GApps and everything was working properly! Calling, everything! However, when I made a reboot, it froze. Stuck in the "Samsung Unlocked" screen for over an hour. I pulled the battery, booted into recovery and did a factory reset/cache and dalvik wipe. It still didn't boot. From there I did a full wipe, and data format, installed Beanstalks newest 4.3 ROM and GApps, and everything loaded properly. Then I couldn't make or receive calls without the same issue. I then did the superwipe/format and installed PAC's newest nightly and GApps package, and was able to make calls, but then got stuck when rebooting, even after factory resets and cache/dalvik wipes. After multiple attempts, I gave up and reflashed the stock MDK Samsung image in Odin3 and am leaving it as is until someone here can help me.
I know this post was incredibly wordy, and I apologize for that, but I wanted to give you guys as much information as possible and explain where this all started, as it may lead to why I'm having these problems. I appreciate any and all responses and I will answer any question any of you have to the best of my ability. Please someone save me from the horror that is TouchWiz!
-Travis
First, make a NANDROID if it is working perfect on the stock ROM. This is my first step after root and recovery so that I can always fall back on something to check if there is a hardware problem, or just some sort of (system) file problem. Plus, it'll save you time if you have to go back.
Not sure that it matters, but is the stock ROM odexed, or deodexed?
The calling thing reminds me of when you use the phone overseas but it has yet to be unlocked. When you root, do you check with Root Checker? Do you have SuperSU installed? How about BusyBox? I know some items require BusyBox in order to work, but SuperSU should be installed.
As far as SuperSU, do you update it before switching back to the original kernel? One thing I noted is to be absolutely sure you do so in order to not lose your root when completing the rooting steps. I imagine this could cause other problems too.
I also suggest not using TWRP 2.6, which many people will tell you is quite buggy. Best to use the previous version.
The only other things I can suggest is ALWAYS doing a full wipe of everything before adding a new ROM. I used to do this to be sure I incurred no problems on my SGS3, because if I didn't there would always be something buggy happening.
Hope this helps.
Heatshiver said:
First, make a NANDROID if it is working perfect on the stock ROM. This is my first step after root and recovery so that I can always fall back on something to check if there is a hardware problem, or just some sort of (system) file problem. Plus, it'll save you time if you have to go back.
Not sure that it matters, but is the stock ROM odexed, or deodexed?
The calling thing reminds me of when you use the phone overseas but it has yet to be unlocked. When you root, do you check with Root Checker? Do you have SuperSU installed? How about BusyBox? I know some items require BusyBox in order to work, but SuperSU should be installed.
As far as SuperSU, do you update it before switching back to the original kernel? One thing I noted is to be absolutely sure you do so in order to not lose your root when completing the rooting steps. I imagine this could cause other problems too.
I also suggest not using TWRP 2.6, which many people will tell you is quite buggy. Best to use the previous version.
The only other things I can suggest is ALWAYS doing a full wipe of everything before adding a new ROM. I used to do this to be sure I incurred no problems on my SGS3, because if I didn't there would always be something buggy happening.
Hope this helps.
Click to expand...
Click to collapse
Thank you, Heatshiver!
I always do a full wipe unless I'm doing a dirty flash for a ROM update. I will try reverting back to TWRP 2.5.0.2 (Whichever version that happens to be, I think it's .0.2) tonight and report my results. Also, just to clarify, I always make sure I have the most updated SuperSU/Superuser (Usually the former) and BusyBox.
I appreciate the suggestion.
-Travis
teemunknee said:
Hi all,
Long time lurker of XDA and Android user/modder since before Gingerbread. I want to apologize in advance if this post is either in the wrong section, and/or if something similar has already been answered/solved in another thread. I did multiple searches with nothing coming up as a direct hit, or even close for that matter.
I recently purchased an S4 from VZW (Mid-Late July). I rooted and installed TWRP 5.2.0.2 (Forgive me if that's not the exact version...) and flashed AOSP ROMs here and there. After a month or so, I started coming across an issue within all ROMs where I couldn't receive or make calls without my phone either freezing or rebooting. Anything I flashed, or modded, failed to remedy this. I tried different GApps packages, 4.2.2 and 4.3 ROMs, different kernels, and both radios, and absolutely NOTHING solved this. I searched everywhere (Even rootzwiki, forgive me fellow XDA members!), and could not find anyone with the same issue.
I attempted upgrading to TWRP 2.6.0.0 and even tried CWM, and that didn't help either. Eventually, things got so bad that I couldn't boot into ANY ROM, 4.2.2 or 4.3. After nearly 10 hours of trying to unbrick my phone, I finally managed to install Beanstalk 4.3, and while it was working incredibly buggy (Not Beanstalk's fault, the developer is a great developer!) nor could I make calls, I could still send texts and emails. I was able to FINALLY get the Odin3 application to work when I got home from work, and was able to flash the stock MDK image. From there I followed the steps to properly root and install TWRP 2.6.0.0. I installed Slim's Beta 5 4.3 ROM and GApps and everything was working properly! Calling, everything! However, when I made a reboot, it froze. Stuck in the "Samsung Unlocked" screen for over an hour. I pulled the battery, booted into recovery and did a factory reset/cache and dalvik wipe. It still didn't boot. From there I did a full wipe, and data format, installed Beanstalks newest 4.3 ROM and GApps, and everything loaded properly. Then I couldn't make or receive calls without the same issue. I then did the superwipe/format and installed PAC's newest nightly and GApps package, and was able to make calls, but then got stuck when rebooting, even after factory resets and cache/dalvik wipes. After multiple attempts, I gave up and reflashed the stock MDK Samsung image in Odin3 and am leaving it as is until someone here can help me.
I know this post was incredibly wordy, and I apologize for that, but I wanted to give you guys as much information as possible and explain where this all started, as it may lead to why I'm having these problems. I appreciate any and all responses and I will answer any question any of you have to the best of my ability. Please someone save me from the horror that is TouchWiz!
-Travis
Click to expand...
Click to collapse
sorry for your troubles, but I am always baffled the way people just toss that word "brick" round
Your phone was no anywhere NEAR being a brick...
You simply are playing with fire flashing AOSP ROMs and not knowing how to fix the issues.
AOSP ROMs aren't technically "made" for our phones, the developers do a great job at making it seem like they are, though.
On the SG3 we had an EFS backup that Synergy discovered incase you flash an AOSP and get stuck in roaming which was quite often at first with AOSP, that was easy to fix, but with this phone I would be careful with AOSP ROMs, even myself, with a locked bootloader wouldn't flash anything besides TW, although I am biased as AOSP is my flavor.
I am sorry if this post comes off harsh or any other bad word. It's not meant for that..
Just to kindly ask you to do some research on what a "bricked phone" truly is.
it's a brick.. meaning won't power on, won't get a light when charging, nothing, your phone is just that, a $600 brick. and the only way to bring back to life IIRC is Jtagging the phone.. which requires taking the phone apart and jtagging the motherboard.
I hope you the best my friend.
As much as I love AOSP, I would have to agree with the poster above. I know TW is a pain but there are some pretty good ROMs in that flavor that you shouldn't have any problems with. I've had the no call issue on AOSP, and even though they are nice and free up quite a bit of room it's not worth missing calls over or constantly flashing. Maybe once our bootloader is unlocked things will become different but I'd stick with TW until that happens. I can confirm that TWRP 2.6 is very buggy...you'll have to download the 2.5 version and flash it instead of goomanager they install they latest version everytime I believe.
andybones said:
sorry for your troubles, but I am always baffled the way people just toss that word "brick" round
Your phone was no anywhere NEAR being a brick...
You simply are playing with fire flashing AOSP ROMs and not knowing how to fix the issues.
AOSP ROMs aren't technically "made" for our phones, the developers do a great job at making it seem like they are, though.
On the SG3 we had an EFS backup that Synergy discovered incase you flash an AOSP and get stuck in roaming which was quite often at first with AOSP, that was easy to fix, but with this phone I would be careful with AOSP ROMs, even myself, with a locked bootloader wouldn't flash anything besides TW, although I am biased as AOSP is my flavor.
I am sorry if this post comes off harsh or any other bad word. It's not meant for that..
Just to kindly ask you to do some research on what a "bricked phone" truly is.
it's a brick.. meaning won't power on, won't get a light when charging, nothing, your phone is just that, a $600 brick. and the only way to bring back to life IIRC is Jtagging the phone.. which requires taking the phone apart and jtagging the motherboard.
I hope you the best my friend.
Click to expand...
Click to collapse
Next time, I'll just say "Soft-bricked". Thank you for your reply.
-Travis
You also may want to try CWM recovery if everything else fails. I like TWRP but I kept having the exact problem you have. I switched and haven't had a problem since.
Sent from my SCH-I545
slim6596 said:
You also may want to try CWM recovery if everything else fails. I like TWRP but I kept having the exact problem you have. I switched and haven't had a problem since.
Sent from my SCH-I545
Click to expand...
Click to collapse
Would you mind telling me which version of CWM you're using? I haven't gone back to CWM since I went back to stock two nights ago.
Thank you for the idea!
-Travis
I also forgot to mention that I haven't been able to connect to 4G radios since before I started having issues with AOSP ROMs. Currently I'm on Eclipse's TW (With AOSP Styling) ROM. Everything appears to be working fine, other than 4G.
I've tried the SIM pull and reset, and nothing. I've tried manually setting it to LTE only, at least when I was able to do so when AOSP ROMs would boot for me, and nothing. I have a Galaxy Nexus that I booted up with this SIM in and I get 4G signal. Any Ideas?
Also, when I was on the stock image (MDK) I didn't have 4G either.
Has anyone else run across this issue? (MODS: Let a me know if I should create another thread, or search more intensively. I haven't seen a thread with this exact same situation. Plenty of 4G issue threads, but none with the same issues I've previously had, and I think it may have something to do with my past modding.)
-Travis
teemunknee said:
Would you mind telling me which version of CWM you're using? I haven't gone back to CWM since I went back to stock two nights ago.
Thank you for the idea!
-Travis
Click to expand...
Click to collapse
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
slim6596 said:
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
Click to expand...
Click to collapse
Thanks! I installed CWM 6.0.3.6 Touch and flashed Eclipse's TW/AOSP ROM and everything works well, but it's still no AOSP ROM.
-Travis
Hi all,
I'd like to thank everyone for the suggestions.
An update: Currently I'm on Eclipse's TW v2.0 ROM (TW, with AOSP Styling) and everything works properly. My current recovery is CWM 6.0.3.6 Touch, and I'm not experiencing any booting or calling issues. 4G is the only thing I don't have working.
I'm hoping that someone with my same problem can give me another idea so I can get an AOSP ROM working, preferably with 4G. I'm sure some, if not most, understand my dislike of TouchWiz and strong preference towards stock Android/stock Android based ROMs. Slim6596 said that he uses Philz Modded CWM Recovery and has no issues anymore. Could that really be my solution?
Again, thank you all for your help and ideas. I love XDA for this reason.
-Travis
slim6596 said:
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
Click to expand...
Click to collapse
Hi Slim,
Sorry to bother, but I was curious if you were specifically using the LOKI patched version, or just the regular version?
-Travis
teemunknee said:
Hi Slim,
Sorry to bother, but I was curious if you were specifically using the LOKI patched version, or just the regular version?
-Travis
Click to expand...
Click to collapse
Loki patched, I believe.
Sent from my SCH-I545
slim6596 said:
Loki patched, I believe.
Sent from my SCH-I545
Click to expand...
Click to collapse
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
teemunknee said:
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
Click to expand...
Click to collapse
I have stuck to TW ROMs. Pretty soon I'm probably not going to be flashing anything. Switching to Motorola and giving Vz my MDK S4 back. (Reception and dropped call issues.)
Sent from my SCH-I545 using Tapatalk 2
teemunknee said:
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
Click to expand...
Click to collapse
I believe you have to do the extended phone function. Its a code on the dial pad and select cdma. I have read this but don't recall where.
Sent from my SCH-I545 using Tapatalk 4
egore93 said:
I believe you have to do the extended phone function. Its a code on the dial pad and select cdma. I have read this but don't recall where.
Sent from my SCH-I545 using Tapatalk 4
Click to expand...
Click to collapse
Are you referring to the *#*#4636#*#* dialer code? I didn't even try that because in my settings, everything was set to CDMA, but that's something I can try. I have everything backed up, so I can just wipe, install, and try that. If it doesn't work, I can always revert back.
Thanks for the suggestion!
-Travis
teemunknee said:
Are you referring to the *#*#4636#*#* dialer code? I didn't even try that because in my settings, everything was set to CDMA, but that's something I can try. I have everything backed up, so I can just wipe, install, and try that. If it doesn't work, I can always revert back.
Thanks for the suggestion!
-Travis
Click to expand...
Click to collapse
Yes that's it give it a go.
Sent from my SCH-I545 using Tapatalk 4