10-05-2011 09:59 PM
Anyone with a rooted v1.3 have any "issues" with the new Flash update to Flash 11?
When I started my NC up today (Wednesday) and d/l it, I could not reboot and spent most of the day trying various combinations until I got things going again tonight.
Rooted 1.3 with 4.5.18 only and did not use 4.6.16 to finish off the root as before.
This allowed me to stop the Flash update and Netflicks is doing just fine.
As to why this happened all of a sudden on a very stable rooted NC is beyond me except for the F11 issue.
10-06-2011 01:12 AM
Have you uninstalled the Flash that BN installed?
BN installs flash in /system/app/ which is read only.
The Android market installs flash in /data.
When Flash tries to update and the old Flash from BN is still around, you get into a nasty boot loop. I wish that a system flash uninstaller had been added to the MN file set, but I don't think people had quite realized what a headache it was until after most of MN work was done.
Titanium can reach into /system/app and delete files, so I use it to uninstall flash after I root, then install Flash from the market.
10-06-2011 07:47 AM
10-08-2011 04:17 PM
I had the same issue yesterday morning. I had never bothered to uninstall the BN flash and had never had any trouble with it updating itself until yesterday. If you are stuck in a boot loop there's a CW flashable fix over on xda. Once you do that you can update from the market just fine.
Where can I find the flashable fix on xda? What's the name of it? A search there didn't turn up anything.
10-08-2011 04:59 PM
If you can't find the CWR fix, it shouldn't be too hard to write one. I could pull apart the noshop/nobrowse scripts and make one an
rm /system/app/Flashplayer.apk script, for instance.
But - if your device is bootable as of now - installing Titanium and using it to remove flash is simpler.
Some of the CWR boot modes enable ADB in CWR. So if your device is on its back right now, with luck, if you boot to CWR and try connecting in over ADB, you'll be able to. You can mount partition 5 (/system), cd into the app folder and manually fish out Flashplayer.
I just wish I could give better advice on how it is that ADB can and can't be enabled in CWR - I've never found rhymre or reason to it.
If you have linux around (even in a virtual machine) you can boot an NC from the Simple Touch rooting disk called "noogie," and all of your partitions are visible to linux when you connect the USB cable. That will also let you fish out the file.
10-08-2011 05:34 PM
No guarantees, but this script should work fine:
the file is called removeflash.zip.
copy to your CWR bootable sd card.
Install via the CWR install zip / choose zip mechanism.
Reboot and you should be back in business - the script mounts your /system and /media partitions, makes a copy of the stock flashplayer.apk to /media as FlashPlayer.apk.bak and then removes /system/app/FlashPlayer.apk.
Once it runs, remove your CWR disk and reboot.
I don't have a way to test this, since none of the NCs here still have the file in question....
10-08-2011 10:45 PM
I see roustabout has already addressed the issue, but just in case, the CW flashable fix is posted here:
Mine was stuck in a boot-loop and I was able to boot to a CW recovery micro sd card, flash the fix and that took care of it.
10-08-2011 11:03 PM
My fix is not as thorough as the one from xda - mine just deletes the file from /system, Gabe's also goes through /data and deletes all the Flash components there, then installs flash for you.
I'd be interested to hear if mine does enough of the job to work, but unless someone's already tried it successfuly, the XDA file is a better bet.
10-09-2011 07:57 AM
Thanks to "Roustabout's" memory jogging exercise regarding deleting Flash, I used Titanium Backup tp delete the existing version and then installed Flash 11.
All went as it should and I am "back in business"!
For those who specifically want to keep their "in-store reading" capability, I can only say that doing the MN to v 1.3 works wonderfully well and gives me the most simple form of BN and Android access possible. It just works!
At various times in the past I have had CM7.0.3 and Phiremod 6.3 on either eMMc or sdcard along with running BN 1.2 on an sdcard while having either of the previous internal. Have even toyed with the most recent MIUI on an sdcard (simply do not like Honeycomb and its variants).
For my personal needs (especially maintaining "in-store reading") v 1.3 with MN is the way to go.
Thanks again for the help and I will work on my "memory exercises"!