I've got Flash 10.2 installed on Calkulin's ROM, but whenever I got to a page with Flash elements, I get the missing plug-in icon where the content should be. I uninstalled and reinstalled, but still no luck. Anyone else had this happen? My last resort is starting all over again, but hopefully there's an easier solution.
I'd like to know, too ... I gave up and went back to 10.1 for now.
I wiped and re-installed the ROM, and Flash worked for a day. Today, it's back to the missing plug-in icon. I'm about ready to throw in the towel on this tablet, it's gotten to be too much work to keep it functioning properly.
Related
I found the solution to the problem described below. It was ROM Manager that was sabotaging me, for whatever reason. I went into CWM manually, wiped everything obsessively 3 times like I've seen other people describe, installed 1.6, and it worked perfectly. Too early to say how it actually runs for me but I least I've got it fully installed!
PROBLEM:
I started from stock rooted S-off ROM and installed Das BAMF 1.5, wiping everything as recommended. Under Settings/About Phone/Software information, the baseband, kernel, build number etc were all correct. Things ran OK, although battery life was pretty bad. But there were a number of anomalies. The Verizon bloatware still seems to be present. The location reticule is still present in the notification area. Etc.
Today I installed 1.6 over 1.5, again wiping everything even though it is said not to be essential. I did the install through ROM Manager. Everything proceeded as expected, the boot animation screen shows BAMF 1.6, all the About Phone information is correct for 1.6. But again, the location reticule is still present; signal strength indicator is 4 bars instead of 6, Verizon bloatware still present.
I know the real action is in the development thread but I still need a few more posts before reaching that exalted status. Anybody else seen/solved an issue like this? Any help is appreciated and if some kind moderator feels led to move this to the other thread, all the better!
[EDIT] A couple other anomalies are the extended Power Options and Reboot menu options shown in the 3rd and 4th screenshots at the beginning of the Das BAMF 1.6.1 development thread-- I don't have those. On the other hand, I do have BAMF Toolbox, Call Recorder, and other expected apps included with the ROM.
Thanks very much.
I'm having the exact same results. Frustrating!
Are you installing with ROM Manager, or directly from CWM?
Having the exact same issue and I installed with ROM manager. Should I reinstall 1.6 manually in CWR? I JUST rooted my phone a week ago and I think I may have flashed it 20X already, lol! I also have weird caller ID issues, it says CDMA call waiting when I miss a call, and Call waiting when I have a voicmail. If flashing it manually will fix these issues, I'll do it again!
Here's the thing I don't get. What's the fricking point of wiping 3 times?
If wiping == formatting a partition, then what good does it do to do it 3 times? None that I can imagine.
If wiping == deleting everything in a directory tree, then again, what point is it to wipe 3 times? What is accomplished on the second and third time that isn't on the first?
Just my opinion. I've never had a problem with wiping just once.
johnkc1975 said:
Having the exact same issue and I installed with ROM manager. Should I reinstall 1.6 manually in CWR? I JUST rooted my phone a week ago and I think I may have flashed it 20X already, lol! I also have weird caller ID issues, it says CDMA call waiting when I miss a call, and Call waiting when I have a voicmail. If flashing it manually will fix these issues, I'll do it again!
Click to expand...
Click to collapse
I would try hbooting the unsigned stock RUU. Then try flashing the rom of your choice through Cwm not rom manager. This should start you back at scratch with s off along with clearing up any bugs you can't seem to get rid of.
I had the same problem. Don't use Rom Manager for this Rom. Do it manually and everything will be like it should.
Ditto to that. All my unfruitful efforts were due to initiating the process via ROM Manager. Doing it all via CWR did the trick.
Hey All,
Here's the rundown. Got the tab new with version 1.2. NVFlashed to 1.1 via directions from 'Gtab for dummies' website and installed installed CWMod just fine (thanks to the Gtab for dummies web page, great work). Partitioned fine. I decided to try Vegan 5.0 and 5.1.1 Supplimental first (though, it never loaded Gingerbread Keyboard for me). Then I went back into CWMod, cleared the 3 caches, then installed the stable version of Vegan Gingerbread 7.0. Booted in ok, waited, restarted, waited. All was ok. Shut down and into CWMod and ran backup then restarted, but it looped to the dev screen and back out into CWMod. I tried reloading the backup but it seems to have failed. So I cleared out all the caches again, then reinstalled. I got it working again, backed up and was able to restart this time, but this is where it gets weird. It's running Gingerbread, but is displaying the Vegan 5.1.1 desktop. I restarted and it started back into Gbread desktop but I shut it down for the night and in the morning it was back to 5.1.1. Kind of a bummer at the moment. Everything else seems fine but I really liked the Gbread desktop with the sidebars, etc (as an aside, when it is on the 5.1.1 desktop I can't add certain widgets like the google search bar and it gives an error that "no space on this homescreen" or on any other for that matter. Any ideas? I have backed up via titanium apps+data to external sdcard, and correct me if I'm wrong, but if I had to reinstall again, would that save me the hastle of reloading all the apps? I can live with it as is though I'm a stickler for the details.
Thanks for the advice/ideas.
TB will restore all apps and data so your good there. When you reflash you just need to side load TB and then batch restore all user apps and data.
At this point I would nvflash back to stock using the stock image with cwm installed and pop in vegan7 again.
I was fearing that. I got this for the wife. She's been hastling me for an ipad for months so I got her this (or maybe for me, who's to say really?). Anyhow, she's like a hawk and I've had to sneak away to try and get it working and had to ask her to reload her apps etc. Then I had to suffer the "what do you mean it's hacked? why didn't you just get the ipad?" etc, etc, etc. I'll try your advice next time she's out and leaves it behind. Fingers crossed she doesn't find out or it will be all kinds of Wrath of Khan up in here...
I finally broke down and did the relock/ruu/OTA routine yesterday.
I had a terrible time getting Amon Ra to reflash from fastboot, it kept giving me a "mainver is older error" and the install failed. I finally got that working (I'm not even sure how, I tried like 10 different versions).
I reflashed an AR BU I made on Friday of the setup in my sig and everything seemed to be working perfect, but I hadn't noticed that WiFi was giving an error because I almost never use WiFi.
Then it occurred to me that WiFi tethering was not going to work and I do use that once in a great while so I decided to reflash the dsb kernel as I knew that would fix it.
When I went to fastboot to do that, I get the same mainver error and the kernel refused to reinstall. Now, I'm like WTF I never should have messed with this thing, it ran perfect and I should have just left it alone..............
At that point, not sure what to do next I decided to try a different kernel even though I was 99% sure it would error out again.
I grabbed a copy of the latest incredikernel as I had been planning on trying that anyway (I really wanted the fast charge from any source feature) and went to fastboot once again.
Much to my surprise, THAT kernel flashed just fine and everything including WiFi etc works perfectly.
Does anybody know why some installs give the mainver error and others don't??
At this point, I am 100% done flashing for a while. The phone flies, doesn't boot loop and all my apps and themes work perfectly. I may not flash again until I get a new phone (my Wife says "fat chance of that")
I NEED HELP!
Backstory: I was on Abberation rom 1.2 and it had worked perfectly. When I installed version 1.0 it used the AROMA installer and allowed me to pick a launcher. I chose Apex launcher but I didn't install any other launchers. Superuser worked fine and it had run buttery smooth. Aberration runs Siyah kernel.
The issue: Alright, so today I was listening to music and suddenly my phone turns off. I literally was listening to music and that's it. I rebooted it and it told said "please wait android is updating" and that only happens when I flash a new kernel...which is impossible since I don't even have mobile odin installed. Then, Then it said "unfortunately, apex launcher has closed" and it would keep repeating that message, meaning I had no actual launcher to run anything from. I installed launcher pro over the air via the play store desktop version from my computer. It downloaded but wouldn't run. I got a text from my friend and the messaging app worked fine, I could text him and everything so there was nothing wrong there. Then I get home and let it charge (since it was dead). I return later and see that the battery icon that pops up when its charging and the phone is off has a loading icon on it, but it doesn't actually show the battery level. I tried to boot up, but it wouldn't. It would show a blank screen and then go back to the battery icon with a loading symbol on it. Eventually I tried to go to CWM via the three button combo and I ended up with the stock 3E recovery. I am utterly confused and need some serious help from you guys. I didn't do anything so is it the ROM's fault?
Note: I have had experience in flashing ROMs and I have done extensive research on trying to fix this. I've never seen this happen before. Did it somehow revert back to the stock kernel while it ran Aberration?
Thanks for any support or instructions you can give me. I was thinking about using creepyncrawly's instruction to unroot to stock, but it only works for gingerbread and I'm on ice cream sandwich.
shadowskorch said:
I NEED HELP!
Backstory: I was on Abberation rom 1.2 and it had worked perfectly. When I installed version 1.0 it used the AROMA installer and allowed me to pick a launcher. I chose Apex launcher but I didn't install any other launchers. Superuser worked fine and it had run buttery smooth. Aberration runs Siyah kernel.
The issue: Alright, so today I was listening to music and suddenly my phone turns off. I literally was listening to music and that's it. I rebooted it and it told said "please wait android is updating" and that only happens when I flash a new kernel...which is impossible since I don't even have mobile odin installed. Then, Then it said "unfortunately, apex launcher has closed" and it would keep repeating that message, meaning I had no actual launcher to run anything from. I installed launcher pro over the air via the play store desktop version from my computer. It downloaded but wouldn't run. I got a text from my friend and the messaging app worked fine, I could text him and everything so there was nothing wrong there. Then I get home and let it charge (since it was dead). I return later and see that the battery icon that pops up when its charging and the phone is off has a loading icon on it, but it doesn't actually show the battery level. I tried to boot up, but it wouldn't. It would show a blank screen and then go back to the battery icon with a loading symbol on it. Eventually I tried to go to CWM via the three button combo and I ended up with the stock 3E recovery. I am utterly confused and need some serious help from you guys. I didn't do anything so is it the ROM's fault?
Note: I have had experience in flashing ROMs and I have done extensive research on trying to fix this. I've never seen this happen before. Did it somehow revert back to the stock kernel while it ran Aberration?
Thanks for any support or instructions you can give me. I was thinking about using creepyncrawly's instruction to unroot to stock, but it only works for gingerbread and I'm on ice cream sandwich.
Click to expand...
Click to collapse
If you have 3e recovery, then I suppose you have the stock kernel. I have no clue how you would have 3e recovery any other way.
I would suggest you flash back to stock and start over. It doesn't matter that you flash back to Gingerbread, because you will install a custom Gingerbread kernel and then flash whatever you want. I would suggest that you use UCKH7 plus root, and then put a Gingerbread kernel on it. Oh, and just in case, do the wipe data/factory reset in 3e recovery after you flash UCKH7, just in case, you know.
I purchased an AT&T SGH-i717 and was told everything worked. When I checked it out, everything seemed fine too. After using it for a couple hours I realized it just seemed to reboot at random. I rebooted into recovery and did a factory reset and wiped the cache. After rebooting it...it would get stuck at the AT&T screen. I then installed the latest stock rom 4.4.2 using Odin and it booted up fine but I got the no sim card error. I put in an AT&T sim card and rebooted but got a sim not provisioned error. I then tried a T-Mobile card and I didn't get the error and it showed signal bars but when I tried to dial it said emergency calls only. I tried a Verizon sim card just to see what kind of error I would get but it was just the same as the T-Mobile sim. I thought it might a corrupted rom so I tried installing the latest nightly CyanogenMod using CWM but got error status 7. I then tried various custom and stock roms including AOKP, BeanStalk, and several different versions of CyanogenMod but always got the same error status 7 msg. I then came across a forum posts stating that CWM no longer works for the SGH-i717. I downloaded the latest TWRP touch recovery and was able install the latest stable CyanogenMod but it would not boot past the animated CyanogenMod logo even after sitting for over an hour. At that point I gave up and decided to just go back to the stock rom. I rebooted into TWRP and the slide to unlock would not work anymore. I had to install CWM using Odin which allowed me to flash back to the stock 4.4.2 rom. After doing another factory reset and wiping the cache then rebooting...the touch screen stopped working. I then flashed it back to the stock 4.0.4 rom but the touch screen still does not work. While trying to figure out what happened I realized the pen still works and touch screen buttons on the bottom but thats it. Also the pen only works on the screen and not on the touch screen buttons. I've been messing with this for 3 days and will probably just sell it for parts but wanted to post this problem so if anyone else had this problem they would know what I've already tried. I did also take apart the phone and clean the connections but that didn't help either.
If anyone has a suggestion for something I haven't tried...please let me know. My last attempt will be install the Padawan JB rom from this post:
http://forum.xda-developers.com/showthread.php?t=1907203
Thanks
Right out of tge gate, there is no stock 4.4.2 for this device. Not official anyway. 4.1.2 is official OS.
Status 7 means your recovery needs updating.
CWM does work and the newest CWM touch is just dandy.
I would try going all the way back. You need to be totally clean.
Factory
Cache
Davlik
Format
Go to Kies and go with emergency firmware recovery.
Get back to stock and see what is working.
Clean clean clean, the best way for anyone to help you. You would be at the best starting point.
Maybe do a little reading as many of your issues have been documented and solved. None of them are major.
Start from scratch and folks can get you running again.
Sent from my SAMSUNG-SGH-I527 using xda app-developers app
captemo said:
Right out of tge gate, there is no stock 4.4.2 for this device. Not official anyway. 4.1.2 is official OS.
Status 7 means your recovery needs updating.
CWM does work and the newest CWM touch is just dandy.
I would try going all the way back. You need to be totally clean.
Factory
Cache
Davlik
Format
Go to Kies and go with emergency firmware recovery.
Get back to stock and see what is working.
Clean clean clean, the best way for anyone to help you. You would be at the best starting point.
Maybe do a little reading as many of your issues have been documented and solved. None of them are major.
Start from scratch and folks can get you running again.
Sent from my SAMSUNG-SGH-I527 using xda app-developers app
Click to expand...
Click to collapse
Thanks for replying...I hadn't used Kies in awhile becuase it never seemed to work right. I downloaded the latest version and it looks like they made a lot of improvements. I did the factory restore and wiped the cache then installed the latest firmware thru Kies. Everything seemed to work fine but after rebooting the touch screen doesn't work at all, not even with the pen. The touch screen buttons seem to still work but its stuck at the AT&T Ready2go screen because I can't hit cancel or get started buttons.
Thanks
cycloneus said:
Thanks for replying...I hadn't used Kies in awhile becuase it never seemed to work right. I downloaded the latest version and it looks like they made a lot of improvements. I did the factory restore and wiped the cache then installed the latest firmware thru Kies. Everything seemed to work fine but after rebooting the touch screen doesn't work at all, not even with the pen. The touch screen buttons seem to still work but its stuck at the AT&T Ready2go screen because I can't hit cancel or get started buttons.
Thanks
Click to expand...
Click to collapse
well my friend, you had the phone apart once already, I am no expert, but my guess is this is no software issue. maybe some connections came loose. in my time here, I have not come across this issue. I do not have the brain pan nor the courage to take my phone apart.
good luck to you.
maybe someone else will mosey on by.
cycloneus said:
Thanks for replying...I hadn't used Kies in awhile becuase it never seemed to work right. I downloaded the latest version and it looks like they made a lot of improvements. I did the factory restore and wiped the cache then installed the latest firmware thru Kies. Everything seemed to work fine but after rebooting the touch screen doesn't work at all, not even with the pen. The touch screen buttons seem to still work but its stuck at the AT&T Ready2go screen because I can't hit cancel or get started buttons.
Thanks
Click to expand...
Click to collapse
My guess is the digitizer has gone bad if odin &/or kies can't fix the issue at hand.