[Q] Webtop Firefox Help Request - Motorola Droid Bionic

Symptom: Firefox fails to load in Webtop.
Back story:
Ran Liberty (.886) until recently. Webtop/Firefox worked beautifully.
FXZ'ed to stock .902 + .905 OTA
Bootstrapped
Wiped
Flashed Eclipse 3
Reproduce:
Bionic, running Eclipse 3 without Safestrap
Dock using HD Dock
Weptop runs fine EXCEPT Firefox
Oh, and I'm using a wirelesss keyboard/mouse on the HD Dock.
Any ideas? I've attempted additional wipes (yes, Dalvik, too) without success.
Is it possible that something of Safestrap survived the FXZ?
Lastly, I'd have posted this on Nitro's ROM thread, but it's in the Dev and I'm < 10 posts.
Thanks!

Related

[Q] Q: How to update to 1.2?

A friend who's nook is neutered but not updated wants me to update her nook to the latest Barnes and Noble Rom.
On my nook I run the latest CM7 nightly with OC kernel, and have no problem with CWR etc.
On hers, I want to keep it as stock as possible. Just want to update it to the latest stock ROM. And neuter it so she can use market etc.
What's the easiest way to go from a neutered 1.1 to a neutered 1.2 (or whatever is the recent B&N ROM update)? Thanks, and sorry if I got those ROM version numbers wrong.
Will it update itself?
Just wondering if I leave her alone for a week or two will she receive an OTA update automatically? (over wifi I guess?) (even if it's neutered?)
I would wait for a autonooter to come out for 1.2 before doing anything unless you like living on the edge.
I was using a nootered 1.0.1 this morning, had to format my system and Data partitions to restore the nook back to factory. Then i had to manually update to 1.2.
Now I've lost root capability and access to the market. The market that BN does offer is not very impressive.
Will Autonootered nook receive OTA update?
Anyone who Nootered their nook received the latest update? Thanks.
If you rooted your Nook won't update. If you want to update you have to perform a Factory reset. Go to Nookdevs and find the Remove Root page.
http://www.nookdevs.com/Portal:NookColor
____________________________________________________
Sent from NookColor CM7 using Tapatalk
If you are using a rooted 1.1, you will need to
1.) Flash Clockwork 3.0.1.0 (or newer) to a micro SD card (Google 'clockwork bootable' and look for a result from mrm3[dot]net)
2.) Download the compatible 1.2 signed image (plain, not keepcwm) and put it on the micro SD card that you just flashed. LINK
3.) Turn off your nook color, put in the micro SD card, and power it up.
4.) You will need to 'flash zip from SD card'. Choose the 1.2 file and flash it.
5.) Go back to main menu (the power button functions as the back button) and do a factory restore (this will clear cache as well)
6.) Pull the sd card from your nook color, then choose "reboot"
7.?) I got an install error on first boot. I waited until the screen turned off on its own, then powered back up. It properly booted to the initial registration screen
****Note, you need Clockwork 3.0.1.0 to flash the 1.2 image, otherwise you will get stuck at the 'n' screen when you try to boot.
I just got done flashing from a rooted 1.1 to stock 1.2. Now to tackle rooting 1.2
japzone said:
If you rooted your Nook won't update. If you want to update you have to perform a Factory reset. Go to Nookdevs and find the Remove Root page.
http://www.nookdevs.com/Portal:NookColor
____________________________________________________
Sent from NookColor CM7 using Tapatalk
Click to expand...
Click to collapse
I don't think that's the case.
My rooted 1.1 nook has been sitting untouched for about a week. I turned it on today and it looks like I got the OTA update (I am being asked to register when I turn it on as if it was a new nook). As I said, it was rooted and had the 1.1 update only.
japzone said:
If you rooted your Nook won't update. If you want to update you have to perform a Factory reset.
Click to expand...
Click to collapse
Not quite true. There's been anecdotal evidence that a rooted NC with CWM installed in emmc may prevent updates. But as others have mentioned many rooted NC have been updated.
fpga_guy said:
Not quite true. There's been anecdotal evidence that a rooted NC with CWM installed in emmc may prevent updates. But as others have mentioned many rooted NC have been updated.
Click to expand...
Click to collapse
Finished rooting after 1.2 update on my stock backup NC. The MN works just fine. I would suggest backuping up files and flashing back to stock (1.1.0) the rooted NC. Only way I know of to ensure a clean eMMC.
Then load the 1.2 downloaded file from BN and update. Then snag the MN to root.
Side note: Use latest CWR 3.0.2.8 and not 3.0.1.0
Once the 1.2 is rooted you'll probably need to do the "standard gapps" reset (clear cache & FC Apps the Google Framework). Then the entire Market will show.
Note also: some apps will fail to install (for me Angry Birds and Aldiko) Use Root Explorer to download the cut/paste file from downloadnull folder to sys/apps, rename and install using package installer.
Above worked for me earlier today.

How to sideload 1.2 update to a 1.1 rooted NC?

Hey there Guys & Gals,
Searched throughout the forums and couldn't seem to find a straight answer on this.
I originally rooted my wife's 1.0.1 NC using Autonooter. That worked out great and then I was able to sideload the 1.1.0 NC updated using ROM Manager and CWR to apply the pre-rooted update ROM (this is where I got the pre-rooted sideload: http://forum.xda-developers.com/showthread.php?t=932145). After that I used an SQL editor to turn all the software updates to manual. This manual switch has held the 1.2.0 update off and everything is working great.
However, I'm really interested in 1.2.0 and would love to apply another sideloaded, pre-rooted update IF that exists. Does anyone know if this is out there? It sounds like most NC owners are running CM7 now as opposed to going down the stock rooted (no ROM) version of the NC. Is there anyone who was successfully able to load up rooted 1.2 from rooted 1.1 without having to resort to an alternate ROM?
As a side question, has any 1.1 NC owners had success with the Netflix app or does that absolutely require at least 1.2 to work correctly?
Thanks for your help!!!
-Stephen
Wanted to bump this one again in case anyone had any suggestions. If not, I'll let this thread die.
Same boat here. I'm still running 1.1 with updates set to manual but I have CM7 on SD. I would also like to update to 1.2 but as far as I know, the only way to do it is to return to stock, unrooted 1.1 and then apply the 1.2 update from B&N. After that, you have the manual nooter option to root 1.2.
Have not been able to get Netflix to work on either stock 1.1 or CM7 with and edited build.pro file. It doesn't show up in the Market so I haven't even been able to try to get it to work.
I know there's a CWM-compatible stock 1.2 ROM floating around the dev forum, but I don't know about pre-rooted. It would at least save you unrooting 1.1.
Sounds like best option is to use the 1.2 CWM capable update and then autonoot again... hmmmm. Everything is working great now and I don't want to mess anything up, but netflix and flash are both very tempting...

Safestrap, Webtop, Tethering working on Bionic

Hi folks,
Hoping this thread isn't redundant, but through my ROM-flashing journeys I've looked up and come across random issues with regards to being able to tether for free and using webtop. Here are the main two issues I've found:
- "I cannot reliably use Safestrap and Webtop / Lapdock together"
- "I cannot tether with the ICS leaks, even with Fox-Fi"
Some partial combination of the two, or both scenarios, seem to be popping up from random individuals with various custom ROMs.
I am lucky and somehow am able to do both but I have to be running the .223 leak, and I have to be on that unsafe side of the Safestrap install. I can't do either when I'm running on the safe side with my custom ROM. For me, personally, this is no problem. When I'm tethering, I prefer not to be using my phone for anything else anyway because it runs really hot and I'm busy using my computer or tablet instead of my phone, anyway.
If this describes you, then great: All you need to do is make sure you're on the .223 leak, not a later one. Tethering should work for you just fine (as long as you do the SQLite Editor hack: bit.ly SLASH sRRfw2 [I can't post links yet]). IF it doesn't, though, just post here. I have no idea if this is foolproof; I just know it works for me.
As for Webtop, I did NOT remove Safestrap; I just went over to my unsafe side and booted into my stock .223 leak. Connecting the mini-HDMI cable to my TV yielded Webtop mode and it works just fine. I'm not sure if it has to do with the fact that I'm running an earlier leak, if I'm lucky, or if the issues were only for people who tried it on a custom ROM; again I just know it's working for me and hopefully it'll work for you too.
I'm assuming that if you use one of Jester's JMOD Blur ROMs, you can use both of these without issue. I'm trying this out now with his latest Liquid BLUR release. I suppose that makes this thread a bit redundant but hopefully at least this is seen as an "alternative" in case your config doesn't work.
This isn't so much redundant to me, however I wonder..
Would installing a custom ROM on the unsafe side enable webtop & tethering, or does it have to be the stock ROM? I'm sure it does..
Sent from my kitchen toaster.
My wifi tether fix
I'm on ICS 232 leak, using Rag3 2.0 rom.
download the latest beta version (WiFi Tether for Root Users 3.2-beta2 *** BETA ***) of Wifi Tether from google: http://code.google.c.../downloads/list
configure it thusly:
device profile: Generic ICS/JB (wlan1)
Setup method: Netd (Master)
enable routing fix (scroll down the settings menu a bit) this box must be checked
this gave me a 65mb/s connection on my laptop and, because it is not an "ad hoc" network, my Nexus 7 tablet also can log on to the hotspot with all bars.
EDIT: I forgot to mention that when I exit Wifi Tether app now, there is NO reboot of the device!
Hope this helps.
idivorceyou said:
I'm on ICS 232 leak, using Rag3 2.0 rom.
download the latest beta version (WiFi Tether for Root Users 3.2-beta2 *** BETA ***) of Wifi Tether from google: http://code.google.c.../downloads/list
configure it thusly:
device profile: Generic ICS/JB (wlan1)
Setup method: Netd (Master)
enable routing fix (scroll down the settings menu a bit) this box must be checked
this gave me a 65mb/s connection on my laptop and, because it is not an "ad hoc" network, my Nexus 7 tablet also can log on to the hotspot with all bars.
EDIT: I forgot to mention that when I exit Wifi Tether app now, there is NO reboot of the device!
Hope this helps.
Click to expand...
Click to collapse
Awesome--it works! Thanks! Now if only I could get Webtop working on this ROM.
One note: I actually could not get this to work at first so on a whim I chose Generic ICS/JB (wlan0) and it works for me now. My config is .223 on the non-safe side, Liquid ICS 1.5 on the safe side.
There's no 223 ics leak
Only 2231 2233 229 230 232 235 238 242 244
bhp117 said:
There's no 223 ics leak
Only 2231 2233 229 230 232 235 238 242 244
Click to expand...
Click to collapse
My guess is that he meant 232. That's the most commonly used version.
im on 244 stock (though heavily modded), despite that foxfi wifi tether works as well as webtop (and simultaneously, anyone ever get bluetooth tether to work?)
webtop mode (or any HDMI enabled modes for that matter) are very difficult to properly mod in order for them to work "seamlessly" in custom ROMs. this is because most custom ROMs are built from CM9 or AOSP base which *do not* contain the necessary system components to support Motorola's proprietary sw/hw implementations.
the only ROMs that will work with webtop are those that start from a moto blur base (like redhead for example). with kexec now, though, things could change.
.. but doesn't help that moto just canned webtop for good
bhp117 said:
There's no 223 ics leak
Only 2231 2233 229 230 232 235 238 242 244
Click to expand...
Click to collapse
I was referring to 2233. Frankly it doesn't matter--the point is that I wasn't on the version where some folks said tethering stopped working. (There's a thread on here somewhere from a few months ago about someone thinking there was a VZW mole here because of that.)
I flashed LiquidBlur from Jester and I'm typing this from a lapdock now. Shame because I liked Liquid 1.5 but this is a really good variant too.

[Q] Help! I updated Bionic to Stock JB, SafeStrap Slot-1 says 0 bytes available

My Extra Droid Bionic had stock ICS 4.0.4 on it, and SafeStrap 3.0.5. I previously installed HashCode's 4.2.2 Stock JB ROM (March 2013 from Goo.im site) to it, using Slot-1 in SafeStrap.
I never used any of the other slots because Hashcode said not to.
I restored stock boot, and uninstalled SafeStrap.
I updated my to Stock Motorola Droid Bionic Jelly Bean 4.1.2 via OTA. I succeded, but lost Root. I tried OTA keeper, but it didn't work this time. (It previously worked for my primary Droid Bionic).
I flashed JB using the Modified SBF file and RSD Lite (I had to delete two lines from the install instructions to get it to work).
I was able to root again using Easy Root (the VirtualBox method). It was a little challenging, but I figured it out
I confirmed Root access. I re-installed SafeStrap 3.11.
I want to install a different custom ROM using SafeStrap, I backed up my Jelly Bean build in SafeStrap.
I went to create a ROM Slot-1 for the Custom ROM, and it says I have 0 bytes of Free space available.
I am unsure what I need to do to get SafeStrap working. If it matters, I think I forgot to delete the old SLOT-1 ROM before I upgraded using the SBF,
Does anyone knowledgeable have any suggestions on how to move ahead to restore the SLOT-1 functionality in SafeStrap?
Solved!
So I noticed in the normal Jelly Bean environment a small SD card icon in the upper left corner. It indicated my internal memory was not formatted. I think it was the RSDLite wiping everything.
I couldn't read anything on it using Root Explorer, so I gave it a shot.
Problem solved...
I now have CM10.1 (JB 4.2.2) running. Not the smoothest over wifi, but it works...
Now I need to figure out why my GAPPS appear to install in TWRP/SafeStrap, but don't actually appear after the reboot..
Later

[Q] Unable to uninstall 4.1.2 on touchpad

i installed 4.1.2 first time w/ROM GUIDE how to install HP TP the easy way but after used for several days, got error "unfortunately, android kybd stopped".
i followed instruction on this website to uninstall used ACMEUninstaller2(and previous version) but screen displayed hp logo without any lines running up the screen as it supposed to.
i did at least 4-5 times w/same results.
Once i left screen at HP logo till battery drain and TP came back w/ANdroid 4.1.2 still alive but no kybd.
HELP, please!
thank you,
-t
Sorry for the issues you are having.
I used JCSullins TP Toolbox to do my installs. Do you want to keep web OS or install just Android?
gtallmadge said:
Sorry for the issues you are having.
I used JCSullins TP Toolbox to do my installs. Do you want to keep web OS or install just Android?
Click to expand...
Click to collapse
i used CM10 Android 4.1.2 10 JB (20131019)cminstall package Download and follow the guide.
i found lots of replies in forum mentioned about after ACMEUinstaller2, run WEBOSDoctor. i did that and it seemed like the app fixed not only WEBOS(?) but also able to uninstalled after that.
But now I'm trying different packages in easy way guide and wasn't able to install any of them: either after reboot hanged at flash screen till battery drained or some conmponents missing(installed same package you mentioned above).
thanks for your response,
-t
tpham56 said:
i used CM10 Android 4.1.2 10 JB (20131019)cminstall package Download and follow the guide.
i found lots of replies in forum mentioned about after ACMEUinstaller2, run WEBOSDoctor. i did that and it seemed like the app fixed not only WEBOS(?) but also able to uninstalled after that.
But now I'm trying different packages in easy way guide and wasn't able to install any of them: either after reboot hanged at flash screen till battery drained or some conmponents missing(installed same package you mentioned above).
thanks for your response,
-t
Click to expand...
Click to collapse
So, do you want to keep web OS? The advantage of using tptoolbox is that you can really start over, clean cache and and do a complete data reset which wipes previous installs of android and web OS.
For what it is worth, this is what I did as I found web OS to be almost unusable for me. I really liked the OS but the lack of support and available apps made it unsuitable for me. So, installing Android has made the TP relevant again for me and my family. We have Android on three TP's and are not looking back. We do have other Android devices but now the TP is once again our favorite and most versatile device. Kudos to all the developers here for giving life back to the TP.
Here is the link to the easiest install guide for using tptoolbox: http://liliputing.com/2014/06/use-touchpad-toolbox-install-android-erase-webos-hp-touchpad.html
this TP belongs to my sister and she prefers to have both OS. While i was trying to install Android to her TP, i did successfully install 4.2.2 to two other TPs.
i think this troublesome TP is unique!
do you have another way to install android while keeping WebOS?
thx,
-t
tpham56 said:
this TP belongs to my sister and she prefers to have both OS. While i was trying to install Android to her TP, i did successfully install 4.2.2 to two other TPs.
i think this troublesome TP is unique!
do you have another way to install android while keeping WebOS?
thx,
-t
Click to expand...
Click to collapse
I don't want to keep WebOS, because HP touchpad hardware is near the end of life, and WebOS is useless and slow.
I used JCSullins TP Toolbox to help me to install CM11, and currently I stay with the CM11 by JCSullins.
Since CM11 is still under development, I have encountered several CM11 common issues on my HP touchpad, but luckily I found the workarounds for them.
If you don't want to deal with trouble, you should stay with WebOS, CM9 or CM10.
i finally got it to work. i suspected the pkg i downloaded @home missed some bits. i downloaded @work and it worked fine.
i also google checksum app and verified the new pkg.
everything is GREAT!
thank you for all your help.
-t

Categories

Resources