Below is a Mail.apk with exchange pin security disabled for Sense 3.5. This is for those who use exchange support who hate entering a pin every time they want to unlock their phone. Many HTC users use corporate exchanges that don't require a pin, yet HTC does not have an option to shut off the pin security. This is the solution. Also, this is only for Sense 3.5. If you are looking for a Sense 3.0 Mail.apk look here.
DISCLAIMER: If your place of employment's exchange policy requires the use of a pin, please be advised that use of this Mail.apk may be punishable up to termination of employment, as well as other possible legal action. This is only for those whose policy does not require a pin. I have also published a flashable StockMail.zip below which will get you back to stock (which includes pin security) if you run into any issues.
Only the pin security is disabled with this mod. All other EAS security (such as remote wipe, etc) is left fully intact.
INSTRUCTIONS (it's also never a bad idea to make a nandroid backup first):
For the Mail.apk
1) Download the attached Mail.apk
2) Mount the system as R/W (either using Root Explorer or 'adb remount')
3) Copy the new Mail.apk to system/app via root explorer and overwrite the older file when it asks, or push the file to system/app via adb
4) Set permissions as rw-r--r--
5) Reboot
6) After reboot, open up the Mail app and set up your exchange account all the way through naming the account, then hit 'Finish Setup'
7) You will be prompted to enable security policy... this is normal so hit 'OK'
8) You will get to another screen asking you to activate security policies... again, this is normal so select 'Activate'. From here on out you will never be prompted to enter a pin
For the PatchedMail.zip
1) Download the .zip and toss it on your SD card
2) Reboot into recovery
3) Install the .zip then reboot
4) Follow steps 6-8 above
If you have issues, try completely removing all your email accounts before installing. You can also try wiping cache in recovery.
NOTE: This only works with Sense 3.5, it will not work if trying to flash over the Sense 2.0/1 Mail.apk or the Sense 3.0 Mail.apk
Enjoy
Man you are the best. Will this work on any Tbolt...I am running Sense 3.5 but on BAMF 1.03?
parcou said:
Man you are the best. Will this work on any Tbolt...I am running Sense 3.5 but on BAMF 1.03?
Click to expand...
Click to collapse
Sorry got it figured. Lost my color mail icon which is ok but as a newbie anyway for me to add back easily? Does it require framework folder for the icons....I don't know just asking.
What is the patchedmail file for? I'm confused on which one to download.
Sent from my Son of a Bliss
bolt_of_thunder said:
What is the patchedmail file for? I'm confused on which one to download.
Sent from my Son of a Bliss
Click to expand...
Click to collapse
The one I ran....meaning you can run it in recovery mode by selecting that zip file....doing the work for you if you dont have root explorer or something like that...
---------- Post added at 01:49 PM ---------- Previous post was at 01:08 PM ----------
Can someone else try this cannot get it to work....
Meaning I cannot get al my info in to setup, get:
EMAIL
PASSWORD
--> I have to do manual setup but does not matter if I hit manual, next window
EMAIL
PASSWORD
SERVER
DOMAIN
I am missing all the bottom part of the window for my NT username...so when I hit NEXT...it fails because I have no place to enter my username as in the past...my email address is not our username for AD
Feedback....
IGNORE FOLKS...... ITS half the screen I had to force it to scroll...... SO IGNORE my dumbness.....
bolt_of_thunder said:
What is the patchedmail file for? I'm confused on which one to download.
Sent from my Son of a Bliss
Click to expand...
Click to collapse
Mail.apk is for those who want to do it all manually with a root file explorer or adb and set permissions.
The PatchedMail.zip contains the exact same apk, but will do it for you automatically in recovery instead of you having to do it all manually.
The last "stock" file is also a flashable zip you can flash in recovery that will get you back to stock in case you ever want to get rid of the mod.
eschelon this works great and I am not going to change it....
Just curious to know if previously I have a custom icon for the mail that was not the white mail envelope icon (default) in the notification window....then replacing it with your sweet mail.apk file I lost that custom notification icon... where is the break that causes that...?
Just for knowledge I am keeping your file...? Thx my friend
parcou said:
eschelon this works great and I am not going to change it....
Just curious to know if previously I have a custom icon for the mail that was not the white mail envelope icon (default) in the notification window....then replacing it with your sweet mail.apk file I lost that custom notification icon... where is the break that causes that...?
Just for knowledge I am keeping your file...? Thx my friend
Click to expand...
Click to collapse
Thx Esc.....!!!!!
Any chance you can make this for the AOSP Email app? I'm running CM7 and don't think this will work.
With sense 3.5 i get message saying the device does not support encryption when i try to connect to my exchange server. I don't get this with Sense 3.0. Is this something that can be removed too?
I loaded InfectedROM Eternity and noticed it also bypasses the PIN requirement and allowed me to access my company exchange server without any problem. In my case I do not want to bypass the PIN due to our security policy so I loaded your "StockMail.apk" to return to stock however after reboot I get an error when adding the exchange account. I researched and found the following corrected the issue (text from my other thread).
Corrective actions for Exchange email after loading a HTC Sense 3.5 based ROM on an HTC Thunderbolt. I am currently using InfectedROM Eternity (with the stock mail.apk) but had the same issue with other ROMS. This probably is the same for any of the newer ROM's. My IT guy said others within the company had similar problems after buying a Sprint phone with newer ROM. Although there seems to be many reasons different phones will not work with exchange mail our particular problem was related to how the newer email.apk with stronger security integration reacts with exchange server. I noticed once setting up the ROM it would error after setting the PIN. The policy warning "details" read something to the effect "Remote Computer Access" required. I had our IT create a policy for me that included “Allow Internet Sharing from the device” and “Allow Remote desktop from the device”. This corrected the problem and all works fine now. It is likely only "Allow Remote desktop from the device" is required.
As I mentioned before the InfectedROM Eternity has a modified email.apk which does not require a PIN. This version will work (no PIN required) before the changes were made to our exchange server. I want to stay within our security policy so I downloaded a copy of "Stockmail.zip" onto the SD card, booted into recovery and loaded the zip file to overwrite the modified mail.apk file. Once the exchange server policy settings were changed all worked fine. My only concern is the IT guy will start freaking out and want to change me back to the other policy settings. I have searched but cannot find any modified version of the mail.apk that would correct just the remote access issue but leave the PIN requirement in place. Any help to find such a version or guidance on how to modify the mail.apk would be much appreciated.
Related
This is a call to arms for anyone still running 1.5 on their eris. We (developers) need people to capture the update process using wireshark (or an equivalent). This is needed for a new root attempt, but sadly all of the devs have already updated to 2.1 so we can't do this.
First go here and download the RUU:
http://www.pcdphones.com/downloads/Eris%20MR1.zip
Next you need to go to verizon's website and login to your account. Click "Suspend/Resume Service" and suspend your phone. You can resume service on the phone after you are done here with no penalties or charges.
Please follow these directions, taken from the first root thread
bftb0 said:
Steps:
[Binny knows this, but if anyone else is reading, it is the same as a factory reset - you will lose all your settings and apps (but not the contents of the SD card)]
1) Unpack the 1.16.605 RUU - by running it as if you were going to actually do the RUU using the USB cable and your host PC, but stop right before you would apply the update to the phone. Pull the "rom.zip" file out of the temporary area that the RUU installer unpacks.
(Poke around under C:\Documents and Settings\<Username>\??? (I can't remember - you'll see folders with names that look like registry entries). You have to do this while the RUU installer is sitting there waiting for you - if you cancel the install, it will nuke everything it unpacked. I just made copies of the entire subtrees.
2) Cancel the RUU install.
3) Move the ROM.ZIP file to the root folder of your SD card, and rename it PB00IMG.ZIP
4) You can cancel the RUU install session on the PC, and unplug the USB cable if you want (so long as you have a well-charged battery!)
3) Power down the phone, and boot it back up holding the Call and End buttons simultaneously
4) Scroll down (or whatever it asks) to go from Fastboot mode to HBOOT mode
5) The phone will automatically discover the PB00IMG.ZIP file, and unpack it and verify it.
6) It will ask you if you want to install; when you (select and) enter Yes, the phone will reboot, and come up again - appearing as if it is repeating the same thing. This time, however, it won't stop and ask you - it will just begin the install.
7) Wait... Wait... Wait... Wait... and then wait some more. If I recall correctly, it seems to hang a little bit at the HTC splash screen after the reboot. That is normal - just WAIT and let the phone do it's thing.
That's it, except for:
8) You probably will want to dial *228 and choose option 1 to complete the programming of your phone - it will reboot after it completes.
Click to expand...
Click to collapse
After you are done, DO NOT start the OTA update that it prompts you to do.
Now we are going to install wireshark and setup the capture environment:
Download wireshark from http://www.wireshark.org/download.html for your versions of windows
Install it - make sure you also install WinPcap
At this point you should turn off any wireless encryption on your router. I know it's not necessary but it makes it easier to go through the captures.
Setup the wireless on your phone to connect to your wireless router and turn off your mobile data connection.
After you have turned off the wireless security on your router, we are going to start the wireshark capture.
Run wireshark - if you are on vista or windows 7 make sure to run it as an administrator
Click "Capture" then "Interfaces"
Click "options" next to the interface that your computer has an IP for
Make sure to check "Capture packets in promiscuous mode"
In the Capture Filter box, type "host <ip_address>" where <ip_address> is the ip address your router gave your phone
Make sure that "Automatic scrolling in live capture" is checked so you can ensure the capture is working
Click "Start"
At this point, you should browse the web with your phone. You should see lots of stuff scrolling by in the wireshark window.
If there isn't, you messed up something above and should try again.
If there is a lot of stuff scrolling by, continue:
Close the browser
In wireshark, click "Capture" then "Restart"
Reboot your phone
On your phone, go to "Settings" -> "About Phone" -> "Check for Updates" and go through with the OTA update
After the update is done and your phone is rebooted, go to wireshark and click "Capture" -> "Stop"
Then click "File" -> "Save As" and give it a name.
Upload that file to Megaupload, or Mediafire, or some other file sharing site, or any private server that I can get access to.
After you have uploaded the file please message me through the forums with a link to the file.
Thanks a ton.
e-mail me at [email protected] i got my wifes phones todo this to shes still on 1.5
NO need to have a average user do this, guinea pig yourself and roll back down to 1.5 it can and has been done by other devs.
Isn't there a "logcat" line you can run through adb to get the same thing? Like, when the update is available, you can plug your phone into your computer, connect it to terminal using adb and run a logcat to find the address of the update.zip
FireSokar said:
NO need to have a average user do this, guinea pig yourself and roll back down to 1.5 it can and has been done by other devs.
Click to expand...
Click to collapse
You CANNOT downgrade from 2.1 to 1.5.
Videofolife13 said:
Isn't there a "logcat" line you can run through adb to get the same thing? Like, when the update is available, you can plug your phone into your computer, connect it to terminal using adb and run a logcat to find the address of the update.zip
Click to expand...
Click to collapse
We don't need the location of the update file, we need all the extra network traffic that surrounds the OTA process.
Ah. My bad.
We need to know, exactly, how the update process works.
I'm currently working on downgrading 2.1. Will post back a tut if i get it working
Can't we create an AVD to run with a custom rom and use the Eris MR1 ROM to do it?
Scratch that. I don't think AVDs will get OTAs.
zifnab06 said:
Scratch that. I don't think AVDs will get OTAs.
Click to expand...
Click to collapse
Sadly I tried this a while ago when messing around with AVD Skins but wasn't able to figure it out. If anyone can figure it out please let me know how you do it! -_-"
zifnab06 said:
Scratch that. I don't think AVDs will get OTAs.
Click to expand...
Click to collapse
Wait can't you set it to wireless only mode and get the OTA through wireless? (Simulated by your network connection)
nindoja said:
This is a call to arms for anyone still running 1.5 on their eris. We (developers) need people to capture the update process using wireshark (or an equivalent). This is needed for a new root attempt, but sadly all of the devs have already updated to 2.1 so we can't do this.
...
Thanks a ton.
Click to expand...
Click to collapse
No need to go to all that trouble. I've already posted a link to the OTA update (1.16.605.1 -> 1.17.605.1) in this XDA thread a couple of days ago. Just copy n' paste into your browser's URL bar. I'll repeat it here for grins.
https://android.clients.google.com/updates/partner/desirec-ota-104882.7b1e5cca.zip
(You might get a browser security warning as that server uses the wrong (google.com) cert.)
Let me know if the above link no longer works - I suppose I could repeat the OTA thing - I am not on 2.1
The OTA process drops the downloaded zip file into /cache, and somehow during reboot, it's presence is detected. If it "only" needs to be dropped in there, or there are some other hooks that need to be present at the reboot, I am not sure. I say "only" because that implies that root privilege is needed to do that - or perhaps it is possible to use "fastboot update" after rebooting the phone with $ adb '(sync; reboot -n oem-78)' The OTA zip file is not signed the way the RUU "rom.zip" files are; it uses the same signing methods as app (.apk) files - the SDK "jarsigner" method.
You can unpack the zip file and look at what it does - there is a script at
META-INF/com/google/android/update-script
which controls the update... and there is a binary patch executable included in zip which is called upon to do file-by-file binary patching.
cheers
bftb0
Thanks for the info bftb0, but we aren't looking to snag the OTA file. We are actually trying to see what communication goes on between our phones and the verizon update servers.
FYI,
When you roll back to MR1, the phone seems to have already grabbed and downloaded the OTA update... in less time than it takes to hand-configure the phone. If you want to observe the OTA process via wireless, you need to prevent the phone from having Mobile network access, since that comes up by default after a FR or MRx rom burn.
Here's a long shot. Perform the MR1 rollback inside a cell dead zone, and conduct a MIM attack by setting up a server on the wireless net so the phone downloads a different OTA zip. You control DHCP for WiFi, so you also in principle control the DNS and routing the phone sees via WiFi. In principle, it's not possible because https should prevent Man-In-the-Middle... but if that (Google) server isn't correctly configured, maybe the phone is not really being too careful about certificate problems. (Either that or the Google server is tuning its' responses based on UA strings).
bftb0
bftb0 said:
No need to go to all that trouble. I've already posted a link to the OTA update (1.16.605.1 -> 1.17.605.1) in this XDA thread a couple of days ago. Just copy n' paste into your browser's URL bar. I'll repeat it here for grins.
https://android.clients.google.com/updates/partner/desirec-ota-104882.7b1e5cca.zip
(You might get a browser security warning as that server uses the wrong (google.com) cert.)
Let me know if the above link no longer works - I suppose I could repeat the OTA thing - I am not on 2.1
The OTA process drops the downloaded zip file into /cache, and somehow during reboot, it's presence is detected. If it "only" needs to be dropped in there, or there are some other hooks that need to be present at the reboot, I am not sure. I say "only" because that implies that root privilege is needed to do that - or perhaps it is possible to use "fastboot update" after rebooting the phone with $ adb '(sync; reboot -n oem-78)' The OTA zip file is not signed the way the RUU "rom.zip" files are; it uses the same signing methods as app (.apk) files - the SDK "jarsigner" method.
You can unpack the zip file and look at what it does - there is a script at
META-INF/com/google/android/update-script
which controls the update... and there is a binary patch executable included in zip which is called upon to do file-by-file binary patching.
cheers
bftb0
Click to expand...
Click to collapse
bftb06: could you please PM me? I am going to trade my phone this week if you understand what I am getting at.
nindoja said:
Thanks for the info bftb0, but we aren't looking to snag the OTA file. We are actually trying to see what communication goes on between our phones and the verizon update servers.
Click to expand...
Click to collapse
Sorry, my bad. I didn't read carefully enough.
I could probably attempt what you are asking for - I am quite familiar with wireshark (and even hardware sniffing of WiFi, so long as you have the right nic), but the fact that the phone seems to go and look for updates immediately after a FR or MRx update means that the "check for updates" thing may not do anything useful for you if there is already an update on the phone waiting to be installed by the time you start pressing menu buttons. (Thus the idea about "do MR1 in a cell dead zone")
Beyond that, there is a possibility that the update app does not do a wildcard host bind() when it sets up the socket when it inquires about updates with the Verizon servers - for instance, MMS service works exactly that way (it will only use the mobile network interface), and precisely so because of security considerations. Do you know whether or not any of the update conversation actually traverses WiFi if the mobile network is turned off?
bftb0
bftb0 said:
Do you know whether or not any of the update conversation actually traverses WiFi if the mobile network is turned off?
bftb0
Click to expand...
Click to collapse
You can force updates to occur over WiFi if the mobile network is turned off. Do you think this would work:
1. on 1.17 do a factory reset but do not activate the phone.
2. Initiate the downgrade process
2a. while downgrading, turn on packet capture
3. When the phone boots back up and wants you to call a number to activate, hang up
I think if you can skip the activation the phone will not have a mobile data connection, which would allow you to turn on wifi and initiate the update process.
Im still on 1.5 PM me and ill help if needed
Do you guys still need this?
Decided to help out and with the ok from ihtfp69 i wrote up a FAQ page
for everyone who uses Sky Raider Rom 3.3 Final
feel free to add.
zip is 180,304 kb
Sense 3.3 Requires a FULL WIPE
to avoid reboots make sure you have S-Off, Upgrade the radio to the OTA version
Wipe everything:
Factory Reset
Data Cache
Dalvik Cache
then apply SR 3.3
The initial boot animation is only there for the first boot and reverts to the original thereafter.
The fix for Rom Manager for fix permissions requires you to open Rom Manager once and then it will work after a reboot
Q: How to flash the ROM?
A:good info here... http://forum.xda-developers.com/showthread.php?t=709220
Q: Since 3.3 requires a full wipe, due to all the changes, I was wondering if the MM mappings for the rosie launcher are still compatible with this new release.
A: All of the mappings are new so make sure you clear out the old ones and download the new ones.
Q:how to Change your lock screens from adb or terminal shellLock
A: there are 13 different lock screens including the HTC one
You must be on SP1 or higher to use them
Change your lock screens from adb or terminal shell
Type 'tabunlock' or 'rotaryunlock' to get the menu seen below
Please choose from the menu - S-OFF REQUIRED
1) normal
2) normal+menu unlock
3) normal+trackball unlock
4) music buttons
5) music buttons+menu unlock
6) music buttons+trackball unlock
7) restore HTC lock screen
8) get me out of here!
reboot
Q: how do you get a logcat?
A: Run CMD prompt and in while in the root folder sdk/tools/ run the command "adb logcat" copy paste all you see onto pastebin.com and post the link. or download logcat from market
"HTC Mail Mod for EAS Admin Removal" You just go to settings -> security -> remove admin policy
Any chance someone wants to actually put this on the wiki?
http://forum.xda-developers.com/wiki/index.php?title=HTC_Droid_Incredible
There is a ROM section in there and would be a much better location than in a forum post.
What do you guys think?
supagene said:
Any chance someone wants to actually put this on the wiki?
http://forum.xda-developers.com/wiki/index.php?title=HTC_Droid_Incredible
There is a ROM section in there and would be a much better location than in a forum post.
What do you guys think?
Click to expand...
Click to collapse
up to our mod overground
Baseband version 1.00.03.03.06
hi
I am running SkyRaider 3.0 Sense RC3 but I have been unsuccessful in updating the radio. I've tried HBOOT but it doesn't like the image, tried renaming to update.zip, tried running the zip from Recovery.
Please advise.
thanks
Jack
Hello,
I would like to know what is "HTC Mail Mod for EAS Admin Removal". Is this some kind of feature?
I would like to disable the PIN Lock on my phone that is enforced by my companies security policy. I used to use LockPicker on Android 2.1 but that no longer works. Is there another solution for Android 2.2?
Thanks.
Nevermind I found it. You should add this to the FAQ. You just go to settings -> security -> remove admin policy (forgot the actual name since after I removed it, the option is no longer there)
Im having a couple of problems
1) I cant get my Yahoo mail account to set up, I have installed the Mail Mod from ROM manager.
2) I am trying to install an application from the market and i am getting the error saying I dont have enough space to install. I really dont have many apps so i dont think thats accurate. I have cleared the market's cache, data, and restarted the application, problem still persists.
Thanks for the help
surfboard3r said:
2) I am trying to install an application from the market and i am getting the error saying I dont have enough space to install. I really dont have many apps so i dont think thats accurate. I have cleared the market's cache, data, and restarted the application, problem still persists.
Click to expand...
Click to collapse
Check to see how many saved backups you have. Each backup can be upwards of 300mb's. If you have more than three that could be the problem. Happened to me once before. I got rid of a couple unnecessary backup files and freed up over half a gig of space. Apps from the market installed with no problems again afterward.
chrisloveskaos said:
Q: How to enable Tab Lock Screen with Sound Controls?
A: You need to remove the HTC lock screen to get to the underlying stock lock screen, get into Recovery, mount system, I go into adb shell to remove
cmd prompt
Code:
c:/sdk/tools>adb shell
~# (showsup) mkdir /system/app.disabled/
~# mv /system/app HtcLockScreen.apk /system/app.disabled/
~# exit
Click to expand...
Click to collapse
I keep getting stuck in a boot loop...
Stu_Gotti said:
I keep getting stuck in a boot loop...
Click to expand...
Click to collapse
There was a missing / between app and HtcLockScreen.apk
Can I just install SP2, or do I have to do SP1 first? ROM Manager is not pulling up SP1.....
gobluejd said:
Can I just install SP2, or do I have to do SP1 first? ROM Manager is not pulling up SP1.....
Click to expand...
Click to collapse
i thk just 2 is fine
Hi I just loaded skyraider 3.3 a couple days ago and tried out the lock screens, and up til now I've had no trouble loading the service packs or the lock screens thru ROM Manager but after activating a lock screen and rebooting thru terminal, I'm now stuck on the boot animation, batt pulls don't work, and I can get to recovery but I don't know what to do from there. Please HELP!!!!
m89maru said:
Hi I just loaded skyraider 3.3 a couple days ago and tried out the lock screens, and up til now I've had no trouble loading the service packs or the lock screens thru ROM Manager but after activating a lock screen and rebooting thru terminal, I'm now stuck on the boot animation, batt pulls don't work, and I can get to recovery but I don't know what to do from there. Please HELP!!!!
Click to expand...
Click to collapse
You have to let it sit for a good while... mine took like 5 minutes after changing the lock screen.
Is it normal for it to take up to 3 hours to complete? Cuz that's what keeps happening
Sent from my ADR6300 using XDA App
m89maru said:
Is it normal for it to take up to 3 hours to complete? Cuz that's what keeps happening
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
no only 5 mins maybe
Can you update this ROM please? I dont have any bugs that need fixing, but i realllly love this ROM and my A.D.D kicks in if i dont make some sort of change
Already added circle battery and 6bar hehe
Update what exactly though? If you have no bugs then the Rom is fine.
Sent from my ADR6300 using XDA App
m89maru said:
Update what exactly though? If you have no bugs then the Rom is fine.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Yes i know
How about the lockscreen update? I think he asked if there was any interest, i would love it! Basically eliminate the lock screen altogether
rsarno said:
Yes i know
How about the lockscreen update? I think he asked if there was any interest, i would love it! Basically eliminate the lock screen altogether
Click to expand...
Click to collapse
There icons that can b changed through metamorph. I made mods to mine with colored icons like bluetooth, car mode, sms, gmail, email. Two kinds of email- basic email app icon r have one made for me for yahoo. So now when I get a email a yahoo icon pops up in my notification. Ask a themer to make you some. Themes and apps has some. I suggest using sysinterwolf cuz he is the man.
According to the Vibrant forums, Jr33 has fixed and ported the MobileAP (native Infrastructure Wifi Tethering AP) from the Galaxy S i9000 to the Vibrant:
http://forum.xda-developers.com/showthread.php?t=756804
Why this is important and better than the Wifi tethering apps (Barnacle and android-wifi-tether):
This is REAL infrastructure mode. Not the hacked up ad-hoc mode (which android-wifi-tether and barnacle uses) which A LOT of devices (other android phones, ps3, wii, corporate laptops included) cannot connect to.
Because it being infrastructure mode, it supports WPA, a much more secure protection than WEP.
This is natively built into the Galaxy S i9000 phones. But taken out by AT&T and T-mobile. It just works, and works well - because it was MADE for our phones!
android-wifi-tethering hard crashes a lot on start, forcing you to do a battery pull, and may lose connectivity every so often.
Barnacle requires you to change the MTU of your client device, not possible in a lot of cases (consoles, phones, etc), and may cause conflicts when moving to a different wifi AP.
-------------------------------------------------------------------------------------------------------------------------------
Update 8/22:
Designgears has figured out a way to automatically launch the wlp2pservice on boot, therefore, no more manual entry is needed (but requires kernel flashing). Please see:
http://forum.xda-developers.com/showthread.php?p=7785171
The reason why it requires flashing the kernel (while Vibrant did not) can be explained by Jr33:
i know the stock kernel for the vibrant had the iptables included as well as wlp2pservice. what i have been finding is all these different features have just been commented out in different places. the same source was used for all three phones. you can see this when you start decompiling the odex files and comparing files, it is all the same. just needs a little tweaking here and there to activate certain features
Click to expand...
Click to collapse
-------------------------------------------------------------------------------------------------------------------------------
Update 8/20:
With the help of Jr33 (person that did the port to Vibrant), we *kind* of got it working with a few hoops. Jr33 should be given credit as he created and repackaged the captivate MobileAP update.zip; I was merely a test dummy. This thread will be locked when a solution is made and Jr33 will create a new thread with the final version. Go buy him a red bull!
REQUIREMENTS
Update.zip downloaded below
Rom Manager
ClockworkMod Recovery flashed on your phone (using Rom Manager)
Busybox
An Android Terminal App (ex: http://www.appbrain.com/app/jackpal.androidterm)
DOWNLOAD The Captivate mobileAP update.zip:
http://www.mediafire.com/?ownoqzgo6cbtmoj
File is also attached at the end of this post.
INSTRUCTIONS
Rename to update.zip, put it on your INTERNAL SD card root
Boot into ClockworkMod Recovery (using Rom Manager) and reinstall/update packages.
Reboot - note: first time boot after updating this will take a little while.
Now go into an Android terminal app and type the following:
Code:
su
busybox nohup /system/bin/wlp2pservice &
This starts the wlp2pservice. (Props to designgears for finding out this new command)
Old command (just typing in /system/bin/wlp2pservice in terminal (does not require busybox)) works BUT you will need to keep Terminal open during the duration, if force closed, you will have to retype that command in again.
5. Now you can go into Settings -> Wireless and Networks -> Mobile AP Settings to start your Access point.
Note: if you change any of the settings (AP name or WPA password) it may crash wlp2pservice. Use a task manager to force close "MobileAP Settings." Do step 4 again and your settings should be there.
This works until you reboot your phone. If you reboot, you need to go back into terminal and manually start wlp2pservice again (do step 4 again).
If you do not manually launch wlp2pservice, when you open up MobileAP settings, it just sits there on a black screen and if you check logcat, you see the looping message pasted below. We are currently trying to fix the necessity of manually launching wlp2pservice. This is not how it was intended to be.
-----------------
Developers with a Captivate, we need your help:
Upon opening MobileAP settings WITHOUT manually launching wlp2pservice in terminal, yields the following (from logcat):
Code:
I/ServiceManager( 3459): Waiting for service WLP2PService....
It loops until you force close "MobileAP Settings" in your task manager. Something is not calling wlp2pservice to execute.
Also, rebooting the phone or closing/ending terminal (on the pc or phone) requires you to go back into terminal and execute wlp2pservice manually, otherwise opening MobileAP settings yields the same loop above.
I am guessing that wlp2pservice is not launching on boot, or not executing at all when you open up MobileAP settings. I'm not sure which is supposed to happen.
This *seems* like an easy fix, and because Jr33 does not have a Captivate it is hard for him to help troubleshoot this. This is why we need other people to help figure out a way.
According to the front page: Update: This is a mod to add in the Samsung version of Mobile AP intended for the Galaxy S, but was removed by T-Mobile.
It was also removed by ATT, so wonder if it is possible :/
andy2na said:
According to the front page: Update: This is a mod to add in the Samsung version of Mobile AP intended for the Galaxy S, but was removed by T-Mobile.
It was also removed by ATT, so wonder if it is possible :/
Click to expand...
Click to collapse
This would be excellent to be ported over. While the current wireless tether (found in the associated thread) works... it does it in ad-hoc mode. This apparently supports infrastructure mode which would make it even more useful.
Go mods go!
rickgrob said:
This would be excellent to be ported over. While the current wireless tether (found in the associated thread) works... it does it in ad-hoc mode. This apparently supports infrastructure mode which would make it even more useful.
Go mods go!
Click to expand...
Click to collapse
wireless tether and barnacle "work" but still require you to go through hoops.
Wireless tether hard crashes A LOT.
Barnacle requires you to change MTU in your OS.
Please see OP for Update.
andy2na said:
wireless tether and barnacle "work" but still require you to go through hoops.
Wireless tether hard crashes A LOT.
Barnacle requires you to change MTU in your OS.
Click to expand...
Click to collapse
Yeah i changed my mtu (took like 30 seconds) and barnacle works great now. I was able to register for my fall semester from disneyland last weekend
I hope this isn't too far off topic, but would it then be possible to use a similiar techique to restore usb tethering to captivate ROMS in which AT&T has it removed/disabled?
jsmith8858 said:
I hope this isn't too far off topic, but would it then be possible to use a similiar techique to restore usb tethering to captivate ROMS in which AT&T has it removed/disabled?
Click to expand...
Click to collapse
When did it get removed? And i doubt the mobileAP is anywhere near related to the USB tethering samsung includes.
I currently have the stock rom, it has usb tethering. Mobile ap is related since they're both tethering.
Perhaps I can extract the file out of my phone where I to be instructed how.
Sent from my SAMSUNG-SGH-I897 using XDA App
Bowsa2511 said:
I currently have the stock rom, it has usb tethering. Mobile ap is related since they're both tethering.
Perhaps I can extract the file out of my phone where I to be instructed how.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I guess if you want to be completely broad they are both tethering solutions....
But their implementation i would assume is different and dont affect each other.
thanks Andy for bring this to Jr33's notice to get this implemented for Captivate.
was wondering if there is any app which wld start this service on boot or something like Tasker if it can start a system service.
Thnx
when i boot into recovery......theres no update option. I have the reinstall packages but it just says installation aborted.
Does the update.zip need to have lowercase "u"?? i did upercase, maybe ill try lowercase
Nope.......i ran into a problem i guess. I named the file to update and i boot into recovery with rom manager but when i get to recovery, there is no updates buttom (im guessing there never was?) I click reinstall packages and it seems to start installing the update.zip but then it says "Installation aborted"
help??
Edit: removed
pewpewbangbang said:
when i boot into recovery......theres no update option. I have the reinstall packages but it just says installation aborted.
Does the update.zip need to have lowercase "u"?? i did upercase, maybe ill try lowercase
Nope.......i ran into a problem i guess. I named the file to update and i boot into recovery with rom manager but when i get to recovery, there is no updates buttom (im guessing there never was?) I click reinstall packages and it seems to start installing the update.zip but then it says "Installation aborted"
help??
Click to expand...
Click to collapse
It's not a signed .zip bro. You need to download rom manager off the market if you don't have it, then reboot recovery from it and it will put you into clockwork recovery mode and then run the update.zip from that. It also lets you run other .zips even if they aren't named update.zip.
Hope that helps ya!
Sent from my GT-I9000 using Tapatalk
anilkuj said:
thanks Andy for bring this to Jr33's notice to get this implemented for Captivate.
was wondering if there is any app which wld start this service on boot or something like Tasker if it can start a system service.
Thnx
Click to expand...
Click to collapse
I thought about that, but because it has to start your terminal program and execute the wlp2pservice (and leave it running), I'm not sure if it had a large impact on battery life.
I setup Better Terminal Emulator to have a shortcut key to type out "/system/bin/wlp2pservice" for me, so its a few taps and Its ready. The amount of tethering I do right now is not that often that this is a big deal, but would be nice..
pewpewbangbang said:
when i boot into recovery......theres no update option. I have the reinstall packages but it just says installation aborted.
Does the update.zip need to have lowercase "u"?? i did upercase, maybe ill try lowercase
Nope.......i ran into a problem i guess. I named the file to update and i boot into recovery with rom manager but when i get to recovery, there is no updates buttom (im guessing there never was?) I click reinstall packages and it seems to start installing the update.zip but then it says "Installation aborted"
help??
Click to expand...
Click to collapse
My bad, it should be "Reinstall Packages" then after selecting it, it makes you scroll down past all the No's to Yes, install package.
Make sure when you open up when you open up Rom Manager you see:
Current Recovery: ClockworkMod 2.5.0.4, if not tap Flash ClockworkMod Recovery. (maybe reinstall it just incase) Then tap reboot into recovery.
Ahhh yes got it. Thank you, I didn't flash my rom before. Got it to work now. Thanks =)
As a quick note:
Please mod alert the Original Post to get this moved back to the Captivate development forum, so more developers that know what they are doing can see this thread and hopefully chime in.
This *seems* like it would be an easy fix. wlp2pservice just needs to launch at boot.
New problem. When I try to run the command in android terminal is says
/system/bin/wlp2pservice
not found
Ok I ran into the same problem because my clockworkmod was borked, so I had to reflash Clockwormod Recovery. When you tap Flash Clockworkmod recovery, it replaces update.zip in your root of the SDCard, so when you hit reinstall/update packages, it just reinstalled clockworkmod recovery again, no harm done.
So what you need to do is redownload the mobileAP zip and replace the current update.zip with the one found in this thread.
Go back into Rom Manager and reboot into recovery (dont hit flash clockworkmod), then update/reinstall packages, it should work then.
Hi, i want to know if it is possible to pre-define settings like mobile data (off) or account sync (off) or any other before flashing? Is there a file which i could edit?
Oor if this isn't possible, whats about to integrate DroidWall into system? Status should be enabled(requires root permission). Rules aren't important since DW blocks every activity from the start.
The thing is, every time i flash a ROM and type in my PIN, android activates mobile data automaticly and sends some bytes. I simply want to stop android from doing this.
Actually i am using the latest ICS build.
I appreciate any suggestions.
Edit: You also can find the thread here:
http://forum.xda-developers.com/showthread.php?t=1490782
Sent from my HTC HD2
redplate said:
Hi, i want to know if it is possible to pre-define settings like mobile data (off) or account sync (off) or any other before flashing? Is there a file which i could edit?
Oor if this isn't possible, whats about to integrate DroidWall into system? Status should be enabled(requires root permission). Rules aren't important since DW blocks every activity from the start.
The thing is, every time i flash a ROM and type in my PIN, android activates mobile data automaticly and sends some bytes. I simply want to stop android from doing this.
Actually i am using the latest ICS build.
I appreciate any suggestions.
Edit: You also can find the thread here:
http://forum.xda-developers.com/showthread.php?t=1490782
Sent from my HTC HD2
Click to expand...
Click to collapse
Are you wanting to completely turn off mobile data?
kylew1212 said:
Are you wanting to completely turn off mobile data?
Click to expand...
Click to collapse
For example I want to prevent android activating mobile data by typing in my pin after fresh rom install, if you know what i mean. So ofc i should be still able to switch it on if needed.
I just want to set a few system settings before flashing. Like Accounts & Sync off and GPS Satellites off.
Xylograph told me he hasnt seen any option for it yet, but if there is any it might could be stored in /data/data or /data/misc
Sent from my HTC HD2
i did a little research and found following:
for predefining Systemsettings:
/data/data/com.android.providers.settings/databases
there is a settings.db which changes in realtime if i change any systemsettings like bluetooth or wifi or gps. if you open it there are some sub entries. the systemsettings are in settings.db/secure and /system
i ll try to set up my rom now like i want, copy then the file and paste it in a romfile with the same dir location. lets see if this works after flashing. the settings.db file can also be edited.
for DroidWall integration:
also for DroidWall i will create folder for
/data/app/com.googlecode.droidwall.free-1.apk
/data/dalvik-cache/[email protected]@[email protected]
/data/data/com.googlecode.droidwall.free/and all files/folders in it
/data/user/0/com.googlecode.droidwall.free/and all files/folders in it
the only problem i think i will have is the root persmission per superuser. i need a config file for superuser but i havent found any.
i hope the dalvik-cache file will help
[email protected]@[email protected]
EDIT:
Doesnt work. None of the two.
Android just ignores the settings.db after first start and therefore all predefined settings like GPS and so on.
I am thinking about to set the permission for settings.db readonlny, before flashing.
And DroidWall have no Rootpermission. And superuser doesnt ask me for root if i restart DroidWall.
I think to get DW working i need to predefine Superuser. But i dont know how.
cacerts.bks file updated 12-6-20
On May 30, 2020 another certificate in our ancient cacerts.bks file expired. This was one of the certificates used by FBReader to sync with a Google Drive directory of your designation (see books.fbreader.org). I'm assuming at this point that it was the critical certificate in the link because not long ago it was possible to work around login issues as described in my earlier post here: https://forum.xda-developers.com/nook-touch/general/setting-sync-fbreader-t3957311
I was contacted by another XDA member about this issue and noticed in a logcat that the certificate had expired. I have never had any luck updating certificates, despite the description of the process by XDA member @tshoulihane. It took many a year for the basics to penetrate my thick skull and I finally decided to look at it again. I will prepare a post on this topic in a bit so the information won't die with me
Meanwhile, I have updated both certificates in a cacerts file I extracted from a Honeycomb ROM and have been using on all my NST devices. It also includes the updated Amazon certificate so the Kindle app still functions. It contains many more certificates than the file that came with the NST (some expired). At least now I see a way forward.
To update your file, download the zip below and extract the cacerts.bks file. Transfer to the SD card of your NST and then use a file manager with root privelages to copy it into /system/etc/security, overwriting the file that is already there. If you feel queasy about this, first rename the old cacerts.bks file to cacerts.bak, then move the new one in place. File permissions should be rw-r-r
Reboot.
No need for the workaround I wrote about in the earlier post now. I tried this with both Opera Mobile and Opera Mini, signed in on both browsers before starting. Opera Mini failed. Opera Mobile, with the appropriate settings for TLS 1.2 etc. as I have described in another post, balked a little but succeeded. And once you are signed in, you never need to go back to the browser (I think).
Here's what may happen:
1. You may sail through the sign-in process from FBReader (Network Library>FBReader book network) and see your file information appear. Done.
2. More likely than not you will get an "unable to establish a secure connection" or similar. This is a sadly common occurrence in Opera Mobile these days and has been roundly trounced on old Opera discussion boards. There appears to be no fix for it except to access the "Settings" window (from the "O" button). Then go to "Privacy" and then "Clear cache". Now back out of the Settings windows (Back button) and finally hit the "refresh" icon. Voila. This is a general "fix" for pages which don't want to load properly even though you have a valid certificate. I've tried running a script to delete the Opera cache before opening Opera but to no avail. Sometimes you are lucky (especially if you have not encountered any errors in a session before exiting), sometimes you are not. Like I say, once you get past this with FBReader, you should not need to go through it again. Just remember, you want to be signed in with your email, etc. on the Google homepage (the same account for your Google drive you set up with FBReader) before you go through all this.
I tested this with FW 1.2.2, but not 1.2.1
Hello!
Thanks a lot for this information, I was struggling with exactly this yesterday and came here to post this issue, but you already have a solution.
I installed Opera Mini v7.6.4 but couldn't connect to FBReader, so I tried to use the default browser and voilà. Now it's working again.
Thanks again, I really thought it was impossible to fix lol.
I haven't checked if kindle app is working, but it surely does.
Thank you!
How does one install or enable a file manager with root access? I've been googling for hours now and it's such a broad topic that I just can't for the life of me figure it out
xrupa said:
How does one install or enable a file manager with root access? I've been googling for hours now and it's such a broad topic that I just can't for the life of me figure it out
Click to expand...
Click to collapse
If your device is rooted, then you just need a "good" file manager. The version of ES File Explorer I use has an option for enabling root access. Attached.
Ah, that's the release version I have installed, I'll try and find the option, couldn't spot it earlier but that gives me hope
many thanks
Cheers, that's got me on a step or two, I think I just need to disable two step verification next as opera or the standard browser is repeatedly doing the 'failed connection' thing you mention at that stage, lightly infuriating, but at least I'm getting closer to getting my fbreader library back, many thanks!
xrupa said:
Cheers, that's got me on a step or two, I think I just need to disable two step verification next as opera or the standard browser is repeatedly doing the 'failed connection' thing you mention at that stage, lightly infuriating, but at least I'm getting closer to getting my fbreader library back, many thanks!
Click to expand...
Click to collapse
The stock browser is useless. For Opera Mobile don't neglect to make the TLS 1.2 change and, of course, update cacerts.bks
Ah great thanks, I've found that TLS thread, I'll do that and hopefully that'll be it!
nice one @nmyshkin
OMG It's done, im back into the network library on my ancient nook!
thanks so much, months of trying allsorts, nice one, thank you!