Database Develop

SUCCESS! Wireless tether in AP Mode (NOT ad-hoc) + WPA2 Encryption

UPDATE 8-24:
I decided to update the OP since there seems to be alot of uncertianty and questions in this thread.
Most of the info in this thread is obsolete. If you are running ANY of the latest roms / kernels, SOFTAP is already compiled in, and all you have to do is download the latest version of WIRELESS TETHER FOR ROOT USERS. Download it from the project site, NOT THE MARKET. As of this post, the most recent version in the market does NOT support AP mode / WPA2! You have to get it from the developer's website.
If you are still running a stock 2.1 rom, then the following information might benefit you. Otherwise, head on over to the developers website: http://code.google.com/p/android-wifi-tether/downloads/list?can=2&q=Incredible
and download the latest version. NO android.tether folder needed!!!!!! Install, and enjoy access point mode and WPA2 encryption!
--samwathegreat
OLD POST:
Hello fellow XDA-ers!
As many of you know, the latest version of wireless tether for root users allows you to tether in access-point mode rather than ad-hoc mode.
If you're aware of this, you're probably also aware that the stock HTC incredible kernel doesn't allow for AP mode, so even if you install the latest version, it will still continue to broadcast in ad-hoc mode (yuck!).
I've gone to the trouble of re-compiling the stock kernel with CONFIG_BCM4329_SOFTAP enabled (which allows for AP mode tethering)! My kernel is 100% identical to the stock htc kernel except for this one change to allow for AP mode. No other changes of any kind. No overclock or undervolt.
If you are running a cm6 OR skyraider rom, OR the leaked OTA, this functionality is already built into the respective kernel. Don't use my kernel if you're running one of these roms.
Also, some of the latest hydra kernels have support compiled in. If you are using hydra kernel, check the changelog on the developers website to see if your version has support.
Instructions:
1. NANDROID BACKUP!
2. Download my ap-inc.zip file and extract
3. Copy the tether_ap_kernel_inc-signed.zip AND the wireless tether apk file to your sdcard.
4. Reboot into recovery, and choose "Install zip file from sdcard", and choose the tether_ap_kernel_inc-signed.zip file.
5. Choose "Reboot Now"
6. When booted back up, install (or update) the supplied wireless tether apk file.
DONE! Now, when you use the wireless tether app, your phone will operate in access-point mode instead of ad-hoc! Additionally, instead of using WEP encryption, WPA2 encryption is now supported instead!!!!
Enjoy!!!!
Please note:
Credit for this goes to:
Myself (samwathegreat) - for re-compiling the stock kernel to allow AP mode
"Koush" - for supplying the means and instructions for creating a kernel update.zip file, and signing with test keys
And of course, the developers of wireless tether for root users.
You may NOT re-post or re-distribute these files and instructions without giving credit to the above individuals/groups.
Get the file here: www 4shared.com/file/uSjHGKnd/ap-inc html
EDIT: Forgot to mention:
1. This kernel is ONLY for the HTC Incredible. Don't try it on another device unless you really want a new paperweight.
2. You will still need to have the fw_bcm4329.bin file in the android.tether folder of your sd-card. Most likely, you already copied this file to the appropriate location when you rooted your phone. If someone has problems getting ahold of the fw_bcm4329.bin file, let me know and I'll post it. EDIT: this file is posted on page 2.
3. Once again: DO NOT use this kernel if you are running skyraider, cm6, or the leaked OTA! You don't need it.
EDIT 7-31-2010:
Due to lots of questions surrounding the latest 2.2 Froyo OTA Leaks, I decided to add this info (from page 12) to the OP:
Originally Posted by samwathegreat
This tutorial is ONLY for 2.1 roms BEFORE the 720p / mobile hotspot leaked OTA. If you are running the 2.1 OTA that includes 720p recording and mobile hotspot, this will still work without applying the kernel I posted.
Wireless tether will NOT work in AP mode in ANY of the latest leaked froyo builds. It may appear to work, but it is in fact not broadcasting, so you can't connect. You have a couple of options:
1. Use wireless tether 2.0.2 in ad-hoc mode
2. Modify the settings in the included 3g mobile hotspot such that it works without paying verizon an extra $20 bux a month.
The problem / reason we can't compile a kernel that supports ap mode for these roms is that HTC has not released the source code. The older kernels are incompatible with the latest roms. We will see more development in this area when the source code becomes available.
Click to expand...
Click to collapse

i currently have the 2.0.2 wireless tether working on my htc incredible. could someone explain the benefits of making the latest version of wireless tether, i think it's 2.0.5, run in access point mode rather than ad-hoc mode? i don't really know the advantages/disadvantages of the different modes..

The main advantage is that AP mode will (should...) allow ANY wifi device to connect.
With the old ad-hoc method, many devices such as nintendo ds, ipod touch, etc. could not connect.
Also, I'm not sure how many of you are familiar with dd-wrt and other custom router firmwares and their functions/benefits, but if you have a router running dd-wrt, and are familiar with the client / client bridge / repeater / repeater bridge modes, then you know that these modes will NOT work in ad-hoc mode.
With this new AP functionality, you can set your dd-wrt router to repeat your phone's SSID, OR use a router as a client bridge for your desktop computer or other device.
These are just a couple of benefits of AP mode. Many people probably have no use for much of this, but simply being able to connect almost any device (which was previously impossible with ad-hoc) is a huge benefit in and of itself.
Anyone else, please feel free to post additional benefits of using wireless tether in AP mode.
-samwathegreat

AP mode works with all devices that support wifi. Adhoc typically only works with pc. Also adhoc can do only 1 device at a time. (ap mode can do many)
Sent from my ADR6300 using XDA App

the337: Also forgot to mention that another great benefit is that, with the new kernel, WPA2 encryption is supported instead of WEP. Wireless tether 2.0.2 only uses WEP encryption which is unsecure and easily cracked (go aircrack-ng).
Personally, I haven't had a chance to try WPA2 encryption. Anyone want to test, and confirm if it works?
EDIT: WPA2 works perfectly for me. It's nice to be able to have an access point on my android that the teenage neighbor can't hack into

is there anyway of getting this into the hydra kernal?

junjlo:
You will have to ask the developers of hydra-kernel to add:
CONFIG_BCM4329_SOFTAP=y
to the .config file before compiling the kernel.

This is already in the kernel for cm6 and skyraider. It may even be in the other Hydra kernels. We have been messing with it for a while. And it should work with anyone using the leak.

Excellent! Thanks for the info. First post updated.

I just tried this using the CM6 Test7 Rom. The tethering works fine as described, but the change to the kernel caused the "screen tearing" problem to reoccur. This hasn't happened since the early CM6 Roms. I really like the idea of AP tethering but I can't deal with the screen tearing. Maybe I'll try it again on the next CM6 version.

I guess you missed the Part about how you don't need to use the kernel if you're running cm6 or sky raider???
Cm6's kernel should already support ap mode. Simply install the newest apk for wireless tether.

Yeah, I guess I didn't understand that from the OP. So good, I'll try again and let you know how it goes.

Just fyi:
2.0.5 isn't available in the market. The market still lists version 2.0.2
Either get the new version from my zip file, or download it from the developers website.
Credit: the geniuses of the wireless tether for root users project.

Sweet, works beautifully! It even informs you when someone jumps on (if you're not secured) and gives you the option to kick them off. I love it. Thank you for bringing this to my (and others) attention. It is MUCH better than the Ad-Hoc Wireless Tethering!

You have just sent me into orbit!! This works beautifully! Thank You to the power of 10!!

Glad you guys love it! Keep the comments coming.

If you could please post the bin file, it would be appreciated.
Thanks.
Edit-Nevermind, I found it. Thanks

do you have to pay fot this, since it is ap just like theone in settimgs
Sent from my Incredible using XDA App

Spotmark:
Place the bin file onto the sdcard inside a folder called android.tether
Everyone else:
This is only necessary if you don't already have the fw_bcm4329.bin file inside the folder "android.tether" on your sdcard. Chances are, you already have this file on your sdcard. It is only provided for those that don't already have it.
Enjoy.

jdkoreclipse:
Absolutely not! This comes from the developers of the wireless tether for root users project.
The program is identical to the wireless tether app that we've used for ages. This new version allows you to use it in access-point mode instead of ad-hoc, providing you have a kernel that supports it.
Anyone want to back me up?

[Q] Wifi Tethering broken after JB update. Is rooting a work around?

PDAnet+/Foxfi no longer work and I get the Verizon message.
Open Garden does basic browser stuff but streaming services don't work with it.
Since rooting is considered legal (for now), if I go to the trouble of rooting and installing a custom ROM, will that allow me to work around the loss of Wifi tethering?

Mr. Whippy said:
PDAnet+/Foxfi no longer work and I get the Verizon message.
Open Garden does basic browser stuff but streaming services don't work with it.
Since rooting is considered legal (for now), if I go to the trouble of rooting and installing a custom ROM, will that allow me to work around the loss of Wifi tethering?
Click to expand...
Click to collapse
You can root, and get the stock hotspot working by making a single alteration in your settings database. There isn't a need to flash to a custom ROM to get that working.

http://www.droidforums.net/forum/droid-4-hacks/208266-how-wi-fi-tether-droid-4-a.html

I rooted my brothers Droid 4 after he updated to JB 4.1.2 the other day, and I changed entitlement_check to "0" and tether apps no longer give me the "verizon blocked" blah blah blah Message, and devices can connect to the droid4 hotspot , but no data is actually shared and all devices status bars do not turn blue (they stay white) .... so basically, there is a way to bypass the tether check on droid 4 JB updates BUT not data is actually being shared ..
Anyone else get this far?

I followed the directions from ovelayer's link and have the built in Mobile Hotspot feature working.
About a week ago, I completely wiped my phone and went back to stock Ice Cream Sandwich and then upgraded to Jelly Bean via the Over the Air update. After a few days of playing around with it, I finally rooted my phone today (using the RAZR_Blade method - https://docs.google.com/file/d/0B_nizg6yUZ0NRjVTZlQ0d1hXVVU/edit) and after changing the Entitlement Check setting with SQLite Editor, I can now tether wirelessly with my phone just fine.

I wiped my phone for a fresh JB 4.1.2 install and after rooting and changing the entitlement_check my mobile hotspot gets stuck when trying to turn on. Not sure how to fix it

StevePritchard said:
You can root, and get the stock hotspot working by making a single alteration in your settings database. There isn't a need to flash to a custom ROM to get that working.
Click to expand...
Click to collapse
How?

Cyber-Logic said:
How?
Click to expand...
Click to collapse
need to root, then see [HOW TO] Entitlement check for Unlimited Data VZW M Users written for Razr M but should still work.
---------- Post added at 10:07 PM ---------- Previous post was at 10:02 PM ----------
also see 66 entitlement_check:

[Q] Any ideas about what is next for Bionic

So now that Jelly Bean for Bionic is out and there is a root method that works, what should be kept and discarded as far as apps go such as, ROM Manager, superuser, superuser#, SuperSU, and VoodooOTA Root Keeper, Bootstrap, safestrap.
Obviously I do not know, and many may not also know, which of these apps is essential and which is outdated. Is there a forum that I missed, if so I apologize. I can guess that Voodoo should be kept because Motorola may, as unlikely as it may seem, might update Bionic with a fix or other small software update.
Is there anyone making ROMS that work with Jelly Bean 4.1.2, ? I have been out of the searching for some months and now not knowing where to look for the best answer to these questions.

Well the Liquid Smooth 2.2.1 and the CM10.1 are built on Kexec so they will work on the JB OTA kernel, I'm running both on the OTA rooted .22 build. I'm reading that some odd functionality seems to be happening but they are already being ironed out in the nightly builds. Anything not on a Kexec build i would assume will not work on your JB OTA kernel.
Just keep reading the posts and help out with the nightlies (load new ones and report any bugs or that its all good) b/c that helps them fix the bugs faster and faster to a new stable ROM.
As far as whats what to keep, I'm keeping Titanium Backup, OTA root keeper, Superuser (obviously) I'm on Safestrap v3.11 to flash ROMs
As for ROMs... the JB 4.2.2 ROMs.. Liquid Smooth, CM10.1 and any other JB ROMs i would think would be ported over. Just keep an eye out. People are all giddy over the Bionic again so im sure it will be strong for awhile longer.

Well I know what's next for my Bionic. After I've jumped up an down on it a bunch of times I plan to toss it in my driveway and drive over it...then backup and do it again a few times.
For me it's been a complete disaster and still have never got my lapdock to work right.
Middle of June my contract is up and I'm going for the Galaxy Note II. Depending upon what kind of deal I can get out of VZW I might switch carriers too.

June!? I might be the harbinger of bad news but the Bionic was released in September of 2011 so that means if you got the Bionic at launch, you cant upgrade till September. They used to let you update at the 20 month mark instead of going to the full 24 months. Well 2 weeks ago Verizon announced that they will no longer be letting people upgrade early. Hence you have to go the full 24 months now.
Eric

Eric214 said:
Well the Liquid Smooth 2.2.1 and the CM10.1 are built on Kexec so they will work on the JB OTA kernel, I'm running both on the OTA rooted .22 build. I'm reading that some odd functionality seems to be happening but they are already being ironed out in the nightly builds. Anything not on a Kexec build i would assume will not work on your JB OTA kernel.
Click to expand...
Click to collapse
Someone correct me if I'm wrong, but the fact that a ROM is based off KEXEC means that those ROM's don't care what base kernel you're running, whether you're on the ICS or JB OTA. Those ROMs bring in their own kernel that's booted with KEXEC. Safestrap handles the KEXEC process, and Safestrap works properly on the JB OTA so there's nothing to really worry about.
Also I'm not even sure how you'd ever use ROM Manager on the Bionic. Especially if you have Safestrap installed.

Hey, I just updated and established root with ubuntu method. Now I want to install Liquid (I hate the feel of stock Bionic) but when I reboot, and hit menu for safestrap, it just boots into android... I have deleted TWRP and safestrap folders, uninstalled and reinstalled, but to no avail. any ideas?

Eric214 said:
June!? I might be the harbinger of bad news but the Bionic was released in September of 2011 so that means if you got the Bionic at launch, you cant upgrade till September. They used to let you update at the 20 month mark instead of going to the full 24 months. Well 2 weeks ago Verizon announced that they will no longer be letting people upgrade early. Hence you have to go the full 24 months now.
Eric
Click to expand...
Click to collapse
MyVerizon still says I can upgrade at discount on 6/6/13. I probably won't right away because I want to wait for the Motorola/Google X phone.

Yeah i know and mine still says May 14th but good luck for me getting to update then. My guess is they haven't updated their systems yet. Likely they have instructions to disreguard that and go the full 2 year from start of contract.
If you can update early still then AWSOME! 1 other thing is maybe they are grandfathering in people who are close? like over 16 or 18 months into the contract so they are only 2-4 months from the early update. IDK I just know that 2 weeks or so ago VZ said they are done with allowing ppl to update at 20 months and that you must now go to the full 24 months or just new contracts will get the full 24 months till upgrade?
Eric

Thanks for the info, I am interested in trying some of the Roms you mentioned, so correct me if I am wrong please but I need safestrap, not bootstrap to load a Rom on the side of the JB stock ROM. I am rooted so no problem there.
Thanx in advance

Sqwaller said:
Thanks for the info, I am interested in trying some of the Roms you mentioned, so correct me if I am wrong please but I need safestrap, not bootstrap to load a Rom on the side of the JB stock ROM. I am rooted so no problem there.
Thanx in advance
Click to expand...
Click to collapse
Yes you have to use safestrap and you must install Liquid in the rom-slot 3 or it wont work. Now on the safestrap. I think you also need to have SS v3.11 for Liquid so make sure you have that one. Once you install it make sure you open the Safestrap app and install recovery then reboot. Once it starts to boot up and you see recovery, make sure you're tapping the setting button, not the screen, and just keep tapping it till you feel the vibration then it will enter recovery.
Eric

Eric214 said:
Yes you have to use safestrap and you must install Liquid in the rom-slot 3 or it wont work. Now on the safestrap. I think you also need to have SS v3.11 for Liquid so make sure you have that one. Once you install it make sure you open the Safestrap app and install recovery then reboot. Once it starts to boot up and you see recovery, make sure you're tapping the setting button, not the screen, and just keep tapping it till you feel the vibration then it will enter recovery.
Eric
Click to expand...
Click to collapse
OK sounds good, will work on that this weekend.
Thank You very much I really appreciate the help.!
NewtG

Eric214 said:
Yes you have to use safestrap and you must install Liquid in the rom-slot 3 or it wont work. Now on the safestrap. I think you also need to have SS v3.11 for Liquid so make sure you have that one. Once you install it make sure you open the Safestrap app and install recovery then reboot. Once it starts to boot up and you see recovery, make sure you're tapping the setting button, not the screen, and just keep tapping it till you feel the vibration then it will enter recovery.
Eric
Click to expand...
Click to collapse
I am a little confused about the setting for the 1,2 or 3 GB is this on the external SD or the internal SD that they are asking about. I have a 32 gb card installed but stock JB ROM I have all my usual apps that take up about 3.5 gb of internal space. And can you tell me if the addition of this other ROM slows down my stock ROM games?? no big deal but my son likes to play some multiplayer games with me on his droid x.

You really should go to hashcodes site and read about safe strap. It is asking the amount of space you want to allocate for apps on the phones internal memory. It will show you how much total spacee you have for all 4 room slots.
---------- Post added at 01:22 AM ---------- Previous post was at 01:14 AM ----------
if you use a lot of apps then you would want to use 3 gigabytes if you use few apps then you want to use one gig.for example my Bionic has a 16 gig internal memory which is allocated an unusable for safestrap which leaves me eight gigs to use for my rom slots. it will use roughly one gig for the system and then what you allocate for data space for apps. so since I have eight gigs everyone get partition I use really uses two gigs. hope this helps

projektorboy said:
Someone correct me if I'm wrong, but the fact that a ROM is based off KEXEC means that those ROM's don't care what base kernel you're running, whether you're on the ICS or JB OTA. Those ROMs bring in their own kernel that's booted with KEXEC. Safestrap handles the KEXEC process, and Safestrap works properly on the JB OTA so there's nothing to really worry about.
Also I'm not even sure how you'd ever use ROM Manager on the Bionic. Especially if you have Safestrap installed.
Click to expand...
Click to collapse
KEXEC kicks out the existing (Motorola) kernel after the system is booted, and starts a new boot sequence with a new kernel. The issue with this system is the availability of specific hardware drivers for the custom kernel.
The KEXEC kernel from your custom ROM does not have all the specific hardware drivers needed for, for example, hardware accelerated graphics, because these drivers are generally not available (closed source), and older available drivers are not compatible with newer kernels.
Now that we have a full JB ROM, custom ROM bakers can borrow the drivers and use them in their creations.
This should mean that new revisions of your custom rom can be made fully functional now. Common missing links that can now be completed are: native camera app and hardware accelerated video playback. I also heard Bluetooth may have been a problem but I don't use it.

Hey, I'm having issues getting into safestrap. I have it installed, with root, on OTA, and it boots to the option to go to it, but when I press menu it goes straight to DROID and boots.... Ideas?

Sometimes hitting menu doesn't catch. tap it till you feel the phone vibrate some. I think the spot to hit really is just above the menu key and the actual screen in the black area. Just tap it a few times till you feel it vibrate and it will boot in to the recovery.

Eric214 said:
Sometimes hitting menu doesn't catch. tap it till you feel the phone vibrate some. I think the spot to hit really is just above the menu key and the actual screen in the black area. Just tap it a few times till you feel it vibrate and it will boot in to the recovery.
Click to expand...
Click to collapse
IT does vibrate, that's why im so confused. I used it for cm10.1 before, but I cant even get into SS now!
EDIT: I just noticed it is not creating a safestrap or TWRP folder... I have root... WTH?

Did you try uninstalling it and reinstalling it? Then install recovery. If that doesnt work are you truely rooted and not partially rooted? Have you installed Titanium BAckup and was it granted root?

Eric214 said:
June!? I might be the harbinger of bad news but the Bionic was released in September of 2011 so that means if you got the Bionic at launch, you cant upgrade till September. They used to let you update at the 20 month mark instead of going to the full 24 months. Well 2 weeks ago Verizon announced that they will no longer be letting people upgrade early. Hence you have to go the full 24 months now.
Eric
Click to expand...
Click to collapse
Everyone with an upgrade date prior to 9/1/2013 is being allowed to keep their current date (source is here). So he will be fine in June.

well that is awsome news!

[ROM][GB][2.3.6]...OG Revolution (Stock based rom) formerly OG_ZVB

Well, well, well.
Here we go!
This here is OG Revolution. A light weight rom for the LG Revolution VS910.
What's under the hood:
--Based off the ZVB update
--Debloated
--Deodexed
--SuperSU
--Ultimate Multi-tasking MOD from Zeppelinrox
--Stock ZVB kernel w/ init.d support
--Custom build.prop tweaks
--Super ad blocking host file
--Custom OG theme
--CRT-off (screen off animation)
--Rooted
--Unsecure kernel
--Custom OG tweaks
--Sysctl support/tweaks
--Beats Audio
--Sony Xloud
--1% low batt notification
--Accurate batt mod (1% increments)
--Custom boot animation
--Direct Injection Entropy booster - by Exit_Only
Click to expand...
Click to collapse
Instructions:
1 Download ROM
2 Reboot into recovery
3 Backup device
4 WIPE DATA (before flashing OG)
5 Flash OG (after DATA WIPE)
6 Reboot system
7 Wait. Check out the custom OG Revolution kernel splash
8 Wait some more while watching custom boot animation
9 Proceed with sim activation
10 (android phone will FC on first boot. Otherwise, works fine)
11 Press home key (initial setup will FC)
12 When fully booted, log into play store.
13 Start downloading your apps.
**Swype must be enabled in Settings. LG keyboard is default.
Click to expand...
Click to collapse
****IMPORTANT****
If you do not wipe data, you will run into a lot of quirks.
Also, if you have issues with super user, just download SuperSU http://forum.xda-developers.com/showthread.php?t=1538053 Get the flashable zip.
If, you flash and are not rooted, just re-root the device.
About phone will not show ZVB. It only shows the latest ota/tot you've installed. For proof, check build.prop or check your download speed (wifi or mobile )
Quickboot has been provided for boot options. Power menu is completely stock.
I am not responsible for any damage to your device. Use at your own risk.
Step 3 clearly states to backup device.
If there are any kwirks, like no status bar or missing images within the UI, just reboot. IDK why this happens but it does. Just reboot and things should be OK.
Also, pls be weary of any tweaks or addons you install. Examine the OG Tweaks script in the init.d folder for any conflicts first. If you don't know, ask.
Click to expand...
Click to collapse
Finally 1.0
OK, OK. Enough BS.
DOWNLOAD
OG Revolution 1.0
Click to expand...
Click to collapse
Coming soon: Power menu mod, Porting of themes to OG, and anything else I or anyone else can come up with.
Thank you's:
Zepplinrox
MT
Exit_Only
LDrifta (over @ AF)
PlayfulGod
"I'm sure there are more"
Click to expand...
Click to collapse

I.M.famous XMAN said:
Well, well, well.
Here we go!
This here is OG ZVB. A light weight rom for the LG Revolution VS910.
What's under the hood:
Instructions:
****IMPORTANT****
If you do not wipe data, you will run into a lot of quirks.
Also, if you have issues with super user, just download SuperSU http://forum.xda-developers.com/showthread.php?t=1538053 Get the flashable zip.
If, you flash and are not rooted, just re-root the device. I think it might be the SU 3.2. idk just yet. Next version might have SuperSU instead.
About phone will not show ZVB. It only shows the latest ota/tot you've installed. For proof, check build.prop or check your download speed (wifi or mobile )
You will need to use an app or the power button combo to boot to recovery. Power menu is completely stock.
This is a beta
OK, OK. Enough BS.
DOWNLOAD
Coming soon: OG ZVB Pure
Click to expand...
Click to collapse
Well Done. Downloading it now.

Let me know what you think ppl. Feedback is great.
Next I'm working on adding or trying to add custom boot ani to the zvb stock kernel. Idk maybe I'll try to compile one. We will see.
And thanks to all who have dl'd it and are willing to give it a try. :beer:
<"I aM famous">
Sent from my VS910 4G using xda app-developers app

Sweet. Will have to give it a go.
I just finished getting the Fascinatemtd ported to Ubuntu Touch. Need to complete my repo and get it out there.
Haven't gotten a new phone, yet. Still looking forward to doing something with this little old Revo when I do, though.

Flashed the ROM this morning. I am setting up my phone right now. So far everything seems good. Runs great thus far. I will run it for a few days and post back.

Haxcid said:
Flashed the ROM this morning. I am setting up my phone right now. So far everything seems good. Runs great thus far. I will run it for a few days and post back.
Click to expand...
Click to collapse
Appreciate it.
One thing, my wife's revo prompted her for the zvb update. I believe i forgot to disable the updater. My bad y'all. You can manually fix it or just wait a bit. I will post a patch to disable the verizon updater; makes it simple if you don't know how.

I went from ZVB stock to OG and so far it has been pretty seamless. I have all my apps installed again and everything configured. Everything appears to work great. Nice debloated base ROM with a few tweaks is exactly what I was looking for in a ROM.
Great Work.
My recommendation to those who are still here, Use the TOT and take the phone to ZV9, update to ZVB, root/cwm, back it up, and make the switch from BO...
The problem I fill with BO was there was to much done to it and that between the Kernal and the overclocking it just makes the phone unstable for many. I know I could not run it.
It would be nice if we could get the ZVB TOT and get the firmware ripped out.
Great work I.M.

Good to hear. And about the firmware, I'm working on that. I'm seem to be stuck on v8.
Sent from my Nexus 7 using xda app-developers app

Really dumb question but....what link to I click to download the file from the download site? I clicked download and it brought me to a site that tries to sign me up for Netball???
Edit: Found the link. Buried between a bunch of ads towards the bottom of the page....

Just flashed OG ZVB, looks like you removed the Bing APK because when I hit the search button on the bottom right I get an error message. Any way to rewire that so it launches google search?

Never noticed that. I'll look into it and see what's up.
Sent from my VS910 4G using xda app-developers app

Also, I am having issues with Internet Connectivity. Web browsing seems to be fine but the Play Store is almost completely nonresponsive as well as downloading themes from within Beautiful Widgets. I am not sure why the internet works in one place but not another. Thought I would report this nonetheless however.

dbeauch said:
Also, I am having issues with Internet Connectivity. Web browsing seems to be fine but the Play Store is almost completely nonresponsive as well as downloading themes from within Beautiful Widgets. I am not sure why the internet works in one place but not another. Thought I would report this nonetheless however.
Click to expand...
Click to collapse
the connectivity issue 'could' be caused by the ad blocking host file. There should be 2 host files within the rom. One of them is a backup of the stock host file. Just swap em and reboot. also, vzw dns servers have always seemed a little slow to me. try changing them to google's dns servers. Rom toolbox can do it for you. I'm also gonna check and see if it is something on my end.
And as to the search issue, mine goes to google. Maybe try installing google search from the playstore and let us know.

I.M.famous XMAN said:
the connectivity issue 'could' be caused by the ad blocking host file. There should be 2 host files within the rom. One of them is a backup of the stock host file. Just swap em and reboot. also, vzw dns servers have always seemed a little slow to me. try changing them to google's dns servers. Rom toolbox can do it for you. I'm also gonna check and see if it is something on my end.
And as to the search issue, mine goes to google. Maybe try installing google search from the playstore and let us know.
Click to expand...
Click to collapse
How do I swap the host files?

dbeauch said:
How do I swap the host files?
Click to expand...
Click to collapse
Rename "hosts" to "hosts.bak" or whatever you prefer. Then rename the other host file to just "hosts"
Sent from my Nexus 7 using xda app-developers app

betatest3 said:
Ok well.... bye guys, I will no longer be developing for this phone(publicly).
I built a ZVB ROM based on OG, it flashes, it boots, it is very slow, did not make it into the setup screen, it restarts.
Could it be made not to do this?
If so I will continue making ROMS.
But for now TestROM will just be getting bug fixes, and tweaks no ZVB.
Click to expand...
Click to collapse
Send me a link the your rom. I'll take a look and see if there is something I can do to help.

ok so I have been running this for about a day now. Initially it was very slow and internet connectivity was intermittant. I downloaded a third party ad blocking app and redid the hosts file and that seemed to fix it. But another part of the prob I was having was that it turns out that I DID in fact lose root access. So I rerooted and re-CWMed and now its running flawlessly.
Here are some suggstions for next release:
1) Remove even more bloat (DeskHome for example)
2) Replace Launcher with something better. LG Home sucks!
3) Add in Google Maps, Quick Boot or similar (or mod Power Menu to include same functionality incl screencap feature), and add the latest Swype as default keyboard (LG ZVB preinstalled Swype is terrible).
4) Replace Superuser with SuperSU and fix this whole losing root on flash thing.
5) Update all preinstalled apps with latest version.
6) Update About Phone to include all relevant info for ROM and underlying firmware.
7) update default Browser homepage to Google.com or something (really anything other than the LG default...terrible)
8) enable non market apps and usb debugging by default
9) update with a cool boot ani (like the android peeing on the apple, I love that one!)
OK this is all I can think of for now. Thanks so much for your work here! It's way more than anything I could do! Now that I have fixed the hosts issue and root issue this ROM is working great. Although I am still having intermittant occasional data connectivity issues. I will continue to monitor.

betatest3 said:
OK I will follow your suggestions later, after some stuff gets done.
Thanks guys
Click to expand...
Click to collapse
I'm on the sidelines now since this phone is no longer activated and is a lonely server sitting at home. Going to see if I can get the official OTA to ZVB and try your next release. Great going for keeping some air in this old tire
...not sure if ZVB will OTA to a phone that's not active. Will see.
Edit: Nope. The OTA has to come over the air. Seems obvious, eh? I had to fit the active micro SIM card from the GS4 into the Revo to get the update OTA.

dbeauch said:
ok so I have been running this for about a day now. Initially it was very slow and internet connectivity was intermittant. I downloaded a third party ad blocking app and redid the hosts file and that seemed to fix it. But another part of the prob I was having was that it turns out that I DID in fact lose root access. So I rerooted and re-CWMed and now its running flawlessly.
Here are some suggstions for next release:
1) Remove even more bloat (DeskHome for example)
2) Replace Launcher with something better. LG Home sucks!
3) Add in Google Maps, Quick Boot or similar (or mod Power Menu to include same functionality incl screencap feature), and add the latest Swype as default keyboard (LG ZVB preinstalled Swype is terrible).
4) Replace Superuser with SuperSU and fix this whole losing root on flash thing.
5) Update all preinstalled apps with latest version.
6) Update About Phone to include all relevant info for ROM and underlying firmware.
7) update default Browser homepage to Google.com or something (really anything other than the LG default...terrible)
8) enable non market apps and usb debugging by default
9) update with a cool boot ani (like the android peeing on the apple, I love that one!)
OK this is all I can think of for now. Thanks so much for your work here! It's way more than anything I could do! Now that I have fixed the hosts issue and root issue this ROM is working great. Although I am still having intermittant occasional data connectivity issues. I will continue to monitor.
Click to expand...
Click to collapse
I agree pretty much. I would leave home but convert it to a non system app. I would add another launcher. Home is not normally laggy for me but it is in this rom. Updated swipe would be ok.
I prefer the stock boot animation vs. animations like the android peeing on an apple do no interest me what so ever.
As for overall performance... Today it really seems very very slow. For now I am going to have to restore my back up. It is really really dragging ass.

Ok guys, I've almost got custom boot animations to work with the stock kernel and I think I got the lag figured out. Testing out a few things, so be looking for an update shortly.
Sent from my Nexus 7 using xda app-developers app

[Q] WiFi issue in JB, is there a router setting to change?

I just bought a Droid 4 that came with JB 4.1 from previous owner. Now I'm facing some issue with my home WiFi (I have an US Robotics USR9111 router): when I try to connect, wifi status remains stuck on "connecting.." phase and doesn't change.
I read that this can be a JB issue, so I tried also changing ROMS but got bootloop, so I restored to stock.
From what I understood, it is not possible to move to another Android version unless I unlock the bootloader, right? So all roms with another Android version that I see, will not work on my Droid for now?
I'm wondering if there can be some setting that I can change on my router to get it work with my phone, or at least if there is a way to unlock my bootloader (done some googling, but no luck)
Thank you in advance

Hi,
Have you tried a factory reset first?
The bootloader of OMAP devices cannot be unlocked. But there is a workaround, an application called SafeStrap. It's basically allows you to create multiple ROM partitions and install ROMs on them. Your stock ROM can remain untouched and you can switch between ROMs. You can install any custom ROM for the D4 this way. You can find the Safestrap topic in the development section.
This way you can test it if your issue is a ROM issue or not.
BTW, SafeStrap requires root.
Sent from my DROID4 using XDA Free mobile app

Thank you. I already installed Safestrap, but i come from a Sony device (Xperia Pro) and thought that SS worked like a normal recovery, and i could not install a rom with a different kernel than that on the phone. I'll try it.
Anyway, issue is rom-related and router-related: with the router at work it connects without problems, and i tried another jb rom that also worked with mine at home (came back to stock because it had other bugs).

axxel84 said:
Thank you. I already installed Safestrap, but i come from a Sony device (Xperia Pro) and thought that SS worked like a normal recovery, and i could not install a rom with a different kernel than that on the phone. I'll try it.
Anyway, issue is rom-related and router-related: with the router at work it connects without problems, and i tried another jb rom that also worked with mine at home (came back to stock because it had other bugs).
Click to expand...
Click to collapse
Stupid question, but are you using the same security settings for wireless on your router and your phone?

nagim said:
Stupid question, but are you using the same security settings for wireless on your router and your phone?
Click to expand...
Click to collapse
Sorry for the late reply: of course, I tried first with my WPA password, and then, since I experienced the problem, I've unsecured my network and tried another time setting an open network type on the phone, but same issue