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
Related
I haven't been able to find a thread containing this, so forgive me if it's a repeat (the search function on this site isn't the best).
I recently rooted my eris and have tried kaosgingerbreadV8, kaosfroyoV39, and xtrSense. I like xtrSense the best, but I would like to have the same flash support that the factory ROM had and the 360deg rotation like the kaos'. Anybody know where I can get them or a ROM that has them?
Also, is there a way to change all my widgets to transparent at the same time, or do I have to flash each one separately?
ianoob said:
I haven't been able to find a thread containing this, so forgive me if it's a repeat (the search function on this site isn't the best).
I recently rooted my eris and have tried kaosgingerbreadV8, kaosfroyoV39, and xtrSense. I like xtrSense the best, but I would like to have the same flash support that the factory ROM had and the 360deg rotation like the kaos'. Anybody know where I can get them or a ROM that has them?
Also, is there a way to change all my widgets to transparent at the same time, or do I have to flash each one separately?
Click to expand...
Click to collapse
Xtrsense has flash built in. As far as the transparent Widgets. You'd either have to flash them separately or put them together into an all in one flash. I don't know of one out there myself. I could be wrong though. If you want to pm me what ones you want and I'll see what I can do for you.
Sent from hell with my Bad Seed Eris
XtrSense say's that flash is there, but it won't pull up flash sites that work on the base ROM. I made sure that the enable flash is checked in the browser settings, no dice. Do I need to turn it on somewhere else?
ianoob said:
XtrSense say's that flash is there, but it won't pull up flash sites that work on the base ROM. I made sure that the enable flash is checked in the browser settings, no dice. Do I need to turn it on somewhere else?
Click to expand...
Click to collapse
If I remember right the first time you open the browser it doesn't always work and you might need a reboot. With your phone browser go to whatismyflash.com. If it says flash not installed then reboot phone, go to that site again and it should be good.
I seen that when I downloaded the ROM and tried it right away. Just retried, no dice, still said "none (or disabled)". Rechecked a site that works on the base ROM, still says I need to download flash. Any other ideas?
You could try a full wipe and reflash or try skyfire browser or miren browser.
Sent from hell with my Bad Seed Eris
The wipe and reflash didn't work. I've tried Skyfire in the past and didn't like it... has anybody blown apart the sense code and located the file for their flash player? How would a noob try to find it (what would I look for)?
I found Tenzo's xtrRCMix 2.1, seems like they are very similar (Tenzo credits Zach.xtr) and the flash works! Now if I could get the 270deg rotation...
(tried Tenzo2.2.1 but it was laggy. future build maybe?)
CondemnedSoul said:
If I remember right the first time you open the browser it doesn't always work and you might need a reboot. With your phone browser go to whatismyflash.com. If it says flash not installed then reboot phone, go to that site again and it should be good.
Click to expand...
Click to collapse
Yep, this is right. And in my case, Flash showed as working the first time I visited whatismyflash.com so I never had to do the reboot/retry scenario. I didn't flash anything Flash-related (forgive the alliteration) when I installed xtrSENSE, so it must have been baked-in to the ROM as reported.
Hi, it has been awhile since I have posted but I have been reading the forums and trying to keep up with things on my 3D. I have since un-rooted my 3D and have returned it to latest stock OTA updates. I did this because I was planning on maybe going to the next greatest phone
My question is pretty simple and involves the process of updating to the ICS when it becomes available...hopefully soon from what I am hearing. Anyways, Would it be best if I deleted any programs I have installed from the play store now? I mean just in case there are conflicts? Or should the update delete them and not reinstall them?
Please be kind...LOL!!!
If you want to update to ICS right now, by using the unofficial leaks, you'll have to re-root and install it that way. This would wipe all data on the phone when installing the new rom. No need to remove apps or data now or anything, but it's always a good idea to back up things you want to keep, just for safe keeping.
If you want to wait for the official ICS, I'm fairly certain that it will also wipe all data and apps on your phone, as it'll need to install a new firmware, which wipes all data on the phone.
No need to remove any apps and such before updating, as they'll automatically get removed anyways.
When you update, you can just install the apps again.
- Moon
Thanks Moon for the reply to this weak at best question...LOL!!! I can just remember at one time when I was flashing and stuff, that the user installed stuff just re-downloaded and installed on its own. I can;t remember if there was an opt out for that or not. I was just curious and like I said a pretty weak question but a great response. Thanks
Also note, if you use the unofficial ICS that everyone is basing their ROM's off of, you won't be able to go back to GB. you are stuck on ICS, but you can flash other ICS roms, just can't go back to Gingerbread.
felacio said:
Also note, if you use the unofficial ICS that everyone is basing their ROM's off of, you won't be able to go back to GB. you are stuck on ICS, but you can flash other ICS roms, just can't go back to Gingerbread.
Click to expand...
Click to collapse
Odd, because if you have the GSM 3D model then you can go back to gingerbread no problems. Even with the firmware update.
scariola said:
Odd, because if you have the GSM 3D model then you can go back to gingerbread no problems. Even with the firmware update.
Click to expand...
Click to collapse
+ 1 i nand back to 3.0 from time to time, no issue
felacio said:
Also note, if you use the unofficial ICS that everyone is basing their ROM's off of, you won't be able to go back to GB. you are stuck on ICS, but you can flash other ICS roms, just can't go back to Gingerbread.
Click to expand...
Click to collapse
Never heard of this on CDMA either. Maybe if you updated your firmware to the new Virgin Mobile one, but even then,I think you can downgrade to GB.
Sent from my ICS 3VO with Tapatalk 2
If you want to wait for the official ICS, I'm fairly certain that it will also wipe all data and apps on your phone, as it'll need to install a new firmware, which wipes all data on the phone.
Click to expand...
Click to collapse
I've never seen an OTA update wipe everything on the phone.
sitlet said:
I've never seen an OTA update wipe everything on the phone.
Click to expand...
Click to collapse
This has been my experience with OTA's as well. It seems that the user installed programs would automatically re-install and like I said there was an opt out at one time but I was not sure that it still existed.
I have a few odd ball programs mostly to do with fishing and stuff, like fishing status etc. and If I see or read that ICS is in fact ready to drop, I will probably go ahead and delete all user installed programs and return to full stock just in case. I have not heard of any problems with older programs on ICS but then again we don;t have the official so who knows.
Anyways thanks for not bashing me on this...:silly:
evomike77 said:
+ 1 i nand back to 3.0 from time to time, no issue
Click to expand...
Click to collapse
I've relocked my phone and used the RUU to go back GB twice now pretty easily. I think the issue was if you updated your firmware with the ICS leak, not the ROMs based on the leak.
baj24 said:
I've relocked my phone and used the RUU to go back GB twice now pretty easily. I think the issue was if you updated your firmware with the ICS leak, not the ROMs based on the leak.
Click to expand...
Click to collapse
Really?
I haven't actually tried it, but I read a few places that once you go to ICS via a ROM based on the leak, you are stuck on ICS ROM's.
Just to note, I've read this on the CDMA development area. Hmm, I'll have to try going back just to see myself, I like ICS, personally, but having options to go back is never a bad thing.
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
So the other day my S3 gave up the ghost, and developed the hard-brick "QHSUSB_DLOAD" error. I have insurance so I was overnighted a new phone, and am sending the old one away. I believe this was related to a long-term power button issue I was having, perhaps a virus, or something. I had not changed anything to the ROM I was using since about October, and the issue just happened now in May.
At any rate, the new S3 I received is an MJB version, Android 4.3, Knox and all that other good stuff. After several failed attempts, I found a method to root this phone and disable Knox. The Warranty Bit is already tripped, so clearly I'm not sending this phone back until it hard bricks as well. I am trying to install the StockMOD ROM that is very popular, however I am being plagued by problem after problem.
I was able to flash a version of CWM Recovery onto my phone, but it was too old and couldn't mount any of the folders. Using ROM Manager, I was able to flash an update to my Recovery, and now it mounts and views all folders properly. However, when I go to install the StockMOD ROM, I continuously get a Status 7 error, something about "expects 5 args, got 3." I wiped the data, cache, and Dalvik, but kept getting this error. So, I had to recover my backup of stock, which didn't go well either. Once my backup was installed, all of my apps kept crashing. Gapps, ROM Manager, everything kept giving me constant FC errors. I had to wipe my data, cache, and Dalvik again and go back to factory default, and reinitialize the phone. Luckily I haven't installed anything of importance on here yet.
A quick search through here states that I need to use TWRP as my Recovery. I've flashed TWRP several times, first using the 2.6... version and then the most recent 2.7.0.0 version, and neither of these will mount any of my folders. It just gives me a litany of errors trying to mount the various locations. I've done Fix Permissions and everything else, TWRP will just NOT mount anything. Other folks say I need the latest PhilZ Recovery. I've downloaded the latest PhilZ Touch 6 and flashed it via Odin. It is giving me the same errors as regular CWM, Status 7, "expecting 5 args, got 3."
I don't know what else to do. My S3 that ran Android 4.0 was so much easier. I had that thing rooted and running a TW based ROM with Nova launcher in about 30 minutes. This phone has been a disaster since I turned it on. I'm just trying to get a 4.3 TW based ROM. I like the Samsung Camera, Calendar, Clock, Messaging, and Contacts apps far better than AOSP versions. But I also want much more customization to my notification drawer toggles. Stock TW doesn't have the toggles I use frequently like the data toggle as well as the torch toggle.
I don't know what I'm doing wrong, because unlike a lot of folks out there, once I find a ROM I like, I stick with it. I'm not constantly updating, changing, or searching for the newest version of Android. There's nothing wrong with that, it just isn't my cup of tea. So does anyone know what I need to do? At this point, I'm about to just give up and use Nova over top of rooted stock TW and call it a day.
Thanks!
Have you tried to go back stock rom using Odin ? I think it might resolve your recovery problem
nosphor said:
Have you tried to go back stock rom using Odin ? I think it might resolve your recovery problem
Click to expand...
Click to collapse
Everything is stock except the recovery. I'm using CWM 6.0.4.7 with PhilZ Touch 6. I'm still using the stock TW 4.3 ROM that shipped with the phone. The only exception is that I'm rooted now.
I suggest you to go back to a 4.1 official stock rom with odin to be sure to have no more issue.
This can help you : http://forum.xda-developers.com/galaxy-s3/general/restore-to-stock-rom-galaxy-s3-i9300-t2187081
Also, don't forget to backup your apps with titanium backup and all your sms :good:
nosphor said:
I suggest you to go back to a 4.1 official stock rom with odin to be sure to have no more issue.
This can help you : http://forum.xda-developers.com/galaxy-s3/general/restore-to-stock-rom-galaxy-s3-i9300-t2187081
Also, don't forget to backup your apps with titanium backup and all your sms :good:
Click to expand...
Click to collapse
Unfortunately, I've heard that it is not possible to revert to anything prior to 4.3 once a phone comes factory installed with 4.3, due to all of the security enhancements and etc. My kernel, modem, and baseband are all factory stock 4.3 MJB. Everyone else on the boards, under various other topics, warn of immediate and sudden death to the phone if you attempt to install a baseband prior to 4.3 MJB.
I'm very surprised to hear that, because recently i've flash stock 4.3 rom and then go back to 4.1.2 to flash a 4.4 rom without any issue and i've got nothing for issues.
Maybe it depends on which country you are ( i'm from France ) ? For what i know , there is a VERY little chance that this downgrade cause dammage to your phone
nosphor said:
I'm very surprised to hear that, because recently i've flash stock 4.3 rom and then go back to 4.1.2 to flash a 4.4 rom without any issue and i've got nothing for issues.
Maybe it depends on which country you are ( i'm from France ) ? For what i know , there is a VERY little chance that this downgrade cause dammage to your phone
Click to expand...
Click to collapse
I'm in the USA. The security features on the I747 US version are far different. I don't know how everyone else is succeeding. I am completely lost.
You are in the wrong forum, anything you try from here will hard brick your phone.
Sent from my GT-I9300 using Tapatalk
Sorry to tell you that, but what you say is not completely true.
Yes, there is a lot of people that rush to give an answer to the question, but there is also people that really like to help people that are in trouble :good:
Please, don't take most of the case for a generality
http://forum.xda-developers.com/showthread.php?t=1756338
Sent from my GT-I9300 using Tapatalk
Yes, i've read this, i know that, that's why i talk about the difference between country, different phone model
My apologies. Thought this was the 747 board. Go ahead and lock this, I'll repost in the correct forum.
Tried TWRP?
Hey, guys. Searched around this forum for this topic but didn't see anything, apologize if it's a duplicate.
Basically my tablet has been freezing constantly since the nougat update. It wasn't happening all that often to begin with but over time it turned into something like once a day to a few times a day. It doesn't follow any usage patterns as far as I can tell (i.e. I use chrome mostly but if I'm on something like one of the regular google apps it might still happen). Once it freezes I have to force shutdown via power button. Every now and then it will freeze and restart itself without my having to force shutdown.
It's stock ROM, with virtually stock apps (dropbox is the only downloaded app). I read about some solutions which I've already tried, and so I wiped the cache, did a factory reset, have about 5gb free storage space, and the issues are still the same.
Any suggestions? Thanks
nickhx2 said:
Hey, guys. Searched around this forum for this topic but didn't see anything, apologize if it's a duplicate.
Basically my tablet has been freezing constantly since the nougat update. It wasn't happening all that often to begin with but over time it turned into something like once a day to a few times a day. It doesn't follow any usage patterns as far as I can tell (i.e. I use chrome mostly but if I'm on something like one of the regular google apps it might still happen). Once it freezes I have to force shutdown via power button. Every now and then it will freeze and restart itself without my having to force shutdown.
It's stock ROM, with virtually stock apps (dropbox is the only downloaded app). I read about some solutions which I've already tried, and so I wiped the cache, did a factory reset, have about 5gb free storage space, and the issues are still the same.
Any suggestions? Thanks
Click to expand...
Click to collapse
YAY!!! someone else!
Can you try something for me. Flash this kernel FIRE-ICE N K10.5.3 (K10.5.4 seems to be having problems ATM)
i think your problem will be fixed.... please let me know! :highfive:
Hi, thanks for replying. I absolutely can do that but I literally have no experience flashing kernels. I assume it's same as flashing a rom but If you could provide some instructions for me I'd appreciate that. It's been a long time since I've even done that and I'd want to make sure I don't screw anything up.
nickhx2 said:
Hi, thanks for replying. I absolutely can do that but I literally have no experience flashing kernels. I assume it's same as flashing a rom but If you could provide some instructions for me I'd appreciate that. It's been a long time since I've even done that and I'd want to make sure I don't screw anything up.
Click to expand...
Click to collapse
Simply... Flash TWRP
Flash kernel like any other ROM.
Reboot done!
ok, thanks. will let you know how it goes.
do i need necessarily need twrp to flash? or can i just use whatever recovery i currently have on there?
nickhx2 said:
ok, thanks. will let you know how it goes.
do i need necessarily need twrp to flash? or can i just use whatever recovery i currently have on there?
Click to expand...
Click to collapse
Yes TWRP
Question did you unlock your bootloader?
honestly i don't remember. some time ago my n9 got stuck in some weird bootloop. i had to run the RUU (i think that's what it was) to restore everything back to completely normal. so if me having to do that meant i unlocked the bootloader then yes i did. if not, then i wouldn't have done it.