Long story short, tether doesn't work.
I was running rooted 6.11.181 and had edited the entitlement check and was using the Wireless Tether app.
Was impatient for OTA so tried to manually push the file. It failed miserably several times. I downloaded the Droid Razr 1.6 utility, and pushed my phone back to factory.
I then factory reset my phone, ran the Droid Razr 1.7 utility. The upgrade worked fine. Rerooted my phone.
Now, when I go into SQL Lite editor I can't find the entitlement check anywhere and my Wireless Tether app isn't work. Anyone know how to fix?
Try FoxFi app. I like our better than the built in tether app. I've never had problems with it.
Sent from my DROID RAZR using xda premium
trypadelik said:
Long story short, tether doesn't work.
I was running rooted 6.11.181 and had edited the entitlement check and was using the Wireless Tether app.
Was impatient for OTA so tried to manually push the file. It failed miserably several times. I downloaded the Droid Razr 1.6 utility, and pushed my phone back to factory.
I then factory reset my phone, ran the Droid Razr 1.7 utility. The upgrade worked fine. Rerooted my phone.
Now, when I go into SQL Lite editor I can't find the entitlement check anywhere and my Wireless Tether app isn't work. Anyone know how to fix?
Click to expand...
Click to collapse
Go back to SQL Lite and check entitlement on number 79. Edit that like you did before and you'll be set!
I did exactly what the video showed to do on gb, and it worked. At least I'm not getting any notifications of a $30 charge.... Mine was number 150
texbuck
I tried to do what the video said but the options just don't exist.
There is no way possible to go back to .181 and try to redo this is there?
Make sure you went to the Moto settings and not the other one.
Sent from my iPad using Tapatalk HD
I have the .211 update on my Razr as of today. Rooted and with SQL_ite the entitlement check is number 79. On .181 is was number 150. So if you have updated to ICS you will find the entitlement check on #79.
Goes like this on ICS for the Razr .211
1 SQlite from Market (have to be rooted)
2 Settings Storage (hammer and crescent wrench)
3 settings.db
4 settings
5 #79 press and hold until edit comes up
6 edit record
7 change value to 0
8 Save
9 Home screen
10 Reboot
11 Profit and you will have tether
It has worked all day for me
How strange, I don't even have #79. It goes from #78 restriction lock to #84 dialup_modem_restriction. My entitlement check was still #150. And yes I'm really on 4.04 ics. Go figure....
texbuck
Astrobrewer said:
Try FoxFi app. I like our better than the built in tether app. I've never had problems with it.
Sent from my DROID RAZR using xda premium
Click to expand...
Click to collapse
^This
Seriously, FoxFi just plain works. No need to do ANYTHING other than setting your password.
sRDennyCrane said:
^This
Seriously, FoxFi just plain works. No need to do ANYTHING other than setting your password.
Click to expand...
Click to collapse
+1
I use FoxFi every day since I got it without issue. You don't even need to set a password if you don't want to. I just hit a button on the widget, select tether and away I go.
Well, setting a password is a good precaution against ANYONE just hopping onto your wifi hotspot.
I just updated to ICS and now my WifiTether app doesn't work. I got FoxFi and it tethered to my laptop with no problem. However, it won't connect to Xbox Live on my 360. It shows it has a network and internet, but won't connect to Xbox Live. My other tether app never had issues connecting.
abowlofsoda said:
+1
I use FoxFi every day since I got it without issue. You don't even need to set a password if you don't want to. I just hit a button on the widget, select tether and away I go.
Click to expand...
Click to collapse
Ok, I'm a beleiver. I'm using FoxFi right now and it works great. No more hotspot hacks for now. Forget my resent posts. :good:
Moved To Q&A
Please Post questions in the Q&A section
I had to do a bit of work to get the entitlement_check sorted out, so I figured I'd post here in case anyone else is having problems. I force fed the OTA to my RAZR Maxx and rooted without much problem. When I tried to update the entitlement_check field in the sqlite DB, I get errors about being unable to write. I even tried chmoding the file to 666 (-rw-rw-rw-), via adb, and it didn't work. These are the steps I used and now I'm in business.
NOTE: I'm using a Linux box. A similar process will probably work on Windows or Mac OS but I don't know.
You'll need to install the SDK and the platform-tools, if you don't already have them.
Code:
$ cd /path/to/platform-tools
$ sudo ./adb kill-server
$ sudo ./adb root
$ ./adb devices (Make sure your device is listed correctly.)
$ ./adb shell
Now you'll be in the android shell.
Code:
$ su -
# id (Make sure "uid=0(root)")
# cp /data/data/com.motorola.android.providers.settings/databases/settings.db /tmp
# chmod 666 /tmp/settings.db
# exit
$ exit
Now you're back at your Linux terminal.
Code:
$ ./adb pull /tmp/settings.db
$ sqlite3 settings.db (If you don't have sqlite3 installed, you can use the binary in the SDK tools dir.)
Now you're in the sqlite db shell.
Code:
sqlite> UPDATE settings SET value=0 WHERE name="entitlement_check";
sqlite> SELECT * FROM settings WHERE name="entitlement_check";
(This should show "79|entitlement_check|0" now.)
sqlite> .quit
Back at Linux terminal.
Code:
$ ./adb push ./settings.db /tmp/settings.db
$ ./adb shell
Back at android shell.
Code:
$ su -
# id (Check for "uid=0(root)" again.)
# cp /tmp/settings.db /data/data/com.motorola.android.providers.settings/databases/settings.db
# exit
$ exit
Now go ahead and reboot you phone and check tethering. Should be good to go.
You should probably make a backup copy of db.settings, after you adb pull it off your phone. It's a small change and easy to fix but Safety Second and all that. (Fun should always come before Safety, in my book.)
Related
Hi everyone,
I'm really baffled by this error im getting now. Just re-did the root on my X10a and everything is working great. SU is advising me when things request root access and it sets to UID 0. FINE. But when i go into terminal and hit whoami i get unknown command. Last time i had this i did ttxdragon (i think is his name) method and it fixed it but now nothing gets it to work. When i hit su i get the # and am able to mount the os in adb and in terminal, also to delete system apps using #6 in the root guide but the whoami command comes up as unknown command. This is driving me nuts because everything seems ot be configured properly and i have proper root access from what i can see. Please someone help if you know what i might be doing wrong.
Also i just re-rooted using the new 5 Step method for X10a.
Your help is much appreciated.
Edit: Also wanted to mention i got the busybox app from the market also and it installed fine as uid0.
Regards.
theMaDHakkeR said:
Hi everyone,
I'm really baffled by this error im getting now. Just re-did the root on my X10a and everything is working great. SU is advising me when things request root access and it sets to UID 0. FINE. But when i go into terminal and hit whoami i get unknown command. Last time i had this i did ttxdragon (i think is his name) method and it fixed it but now nothing gets it to work. When i hit su i get the # and am able to mount the os in adb and in terminal, also to delete system apps using #6 in the root guide but the whoami command comes up as unknown command. This is driving me nuts because everything seems ot be configured properly and i have proper root access from what i can see. Please someone help if you know what i might be doing wrong.
Also i just re-rooted using the new 5 Step method for X10a.
Your help is much appreciated.
Edit: Also wanted to mention i got the busybox app from the market also and it installed fine as uid0.
Regards.
Click to expand...
Click to collapse
Easy, instead of running simply:
# whoami
Run:
# busybox whoami
Done!
By the way, you can simply type
# id
too
Haha! Thank you your a saint! I'm still learning everyday
Thanks again.
Sent from my X10a using XDA App
biktor_gj said:
Easy, instead of running simply:
# whoami
Run:
# busybox whoami
Done!
By the way, you can simply type
# id
too
Click to expand...
Click to collapse
Simple, amazing solution. Thanks !
Great news everyone! </farnsworth>
ADHOC Wifi Support for Nook Color (stock)!
[EDIT] There appears to be an issue reconnecting when wifi sleeps and comes back on. Researching a permanent fix, in the meantime go to settings -> Wireless and toggle wifi off/on to correct it
This fix will allow you to connect to ADHOC wireless networks ( such as to a laptop or with wifi-tether on an android phone )
Like most other fixes, this requires your nook to be rooted and usb adb working, please follow the guides here and/or at the nook dev wiki first!:
Rooting: http://nookdevs.com/NookColor_Rooting
USB-ADB: http://nookdevs.com/NookColor_USB_ADB
HOWTO enable ADHOC tethering:
1. Download and unzip the attached zip file below, this should give you a wpa_supplicant-adhocfix file
2. *DISABLE WIFI ON YOUR NC*
3. Make a backup of your current wpa_supplicant:
Code:
adb pull /system/bin/wpa_supplicant wpa_supplicant.backup
4. Remount the /system partition RW:
Code:
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
5. Push the new wpa_supplicant:
Code:
adb push wpa_supplicant.adhocfix /system/bin/wpa_supplicant
6. Fix permissions:
Code:
adb shell chmod 755 /system/bin/wpa_supplicant
7. Remount the /system partition RO:
Code:
adb shell mount -o remount,ro /dev/block/mmcblk0p5 /system
8. Enable WIFI on your NC, you should now be able to see ADHOC networks in the list! ( they'll be displayed with a (*) prefix )
[edit] Credit where credit's due, this was taken from a wpa_supplicant IBSS patch I found via a Google search, if anyone knows the party responsible, let me know so I can credit them properly!
http://szym.net/android/
This is compiled against TI's Omapedia Eclair sources ( http://omappedia.org ) - since this is a different framework than the B&N stock build, I can't guarantee this will work, won't brick your device, etc. Use at your own risk!
If you encounter any problems, please use this thread to let us all know.
That's all there is to it, enjoy!
I can confirm that this will allow you to connect you Nook Color to an adhoc network created by a Jailbroken iPhone 4 and MyWi.
Works great! Thanks!
WHOEVER made this fix....THANK YOU! This was the biggest thing I was missing on my NC! Works great!
Cool you figured this out! For some reason, I've been able to use the adhoc network on my Androidized HTC Leo (HD2) since the first time I tried, even before rooting.
Sent from my Rooted Nook Color using XDA App and iPhone MyWi adhoc connection.
You guys ROCK!!!!!!!!!!
Works great with my Droid now. Thanks!
Confirmed working with Mobile Wi-Fi Router on my VZW Touch Pro2.
Many thanks! Another big step!
Work perfectly on my motorola droid 1 using Wireless tether or Barnacle. Thanks for sharing this with us
Works great with AT&T Samsung Captivate and android-wifi-tether ver. 2.0.5-pre15.
Thank you very much!
My NC is stuck at trying to obtain an IP address from my Droid 1. I'm using Barnacle.
Any ideas?
*edit*
It took several attempts but it finally connected. Being able to get connected anywhere is awesome. Thanks for posting this!
Working great from my epic 4g.
Pro Tip: If you want a quick way to toggle wifi (and a few other settings) tap the clock in the nook's notification bar for a quick settings dialog.
Thanks for this. I can now use my nook at work tethered to my phone. You may want to edit the typo in step 7 as we all caught it but someone may not.
Philosophy757 said:
Thanks for this. I can now use my nook at work tethered to my phone. You may want to edit the typo in step 7 as we all caught it but someone may not.
Click to expand...
Click to collapse
Thanks for noticing, corrected the extra 'o'
As noted in the OP, this is based on TI's omap eclair reference sources, and there *is* a pretty glaring bug.
Basically, if your screen goes to sleep, waking it back up triggers a wifi-reconnect which fails to reinitialize the network properly. Your wifi settings will show 'Connected, no internet' when this happens.
Toggle Wifi off/on to fix this, I'm working on a permanent fix right now and will update when it's working.
Thanks everyone for testing and boosting the ol' ego a little
Some random tips so folks don't repeat the same mistakes I made while doing installing the ad hoc feature.
Don't choose to "forget" a wireless access point because then it doesn't appear again even if the device sees it. You'll have to manually enter the SSID, encryption type, and password to get it to work properly.
While mounting and remounting using adb, if you get a device busy error, disconnect the nook from the computer and come back to it later. Then reconnect and try again. For good measure I also powered down the nook. Not sure what happens if you leave the system folder mounted as RW, but I suspect bad things could happen.
Oh and the fix works like a charm. This is one really nice device.
Works perfect on my NC tethered to my MyTouch 3G ( rooted with CyanogenMod-6.1 )
Many many thanks to the dev. !!
Nice work, and thank you. Working fine with another rooted droid (running CM6.1).
I had the "device busy" error and went ahead and unplugged, then reset to ro with Root Explorer- no problems.
This reminds me of when the Droid first got rooted- took a little while to make progress but every few days that would be another BIG, popular advance.
Thanks so much!!!! Droid1 still has life! Yeah.
Thanks. This works great. One question. Does anyone know where I can get the original wpa_supplicant file? I misspelled it so I don't have a good backup. Thanks.
Original nook wpa_supplicant
Here ya go...
OK. Maybe I can't upload files.
I was enjoying the beauty of having a rooted device, but now that I have received an update from Motorola (which I thought was ICS) I have lost root access.
I have a Photon 4g running 2.3.5, and I did my root using a OCR when I was on 2.3.4. I have tried that OCR again among others and torpedo photon and no luck. Every app I try says that it was denied superuser access (which is still installed). The only exception to this is Play Movies, which says that "This app currently does not support root access, and your device is rooted" I do not know where else to turn. I just want to be part of the cool kids again. Please someone help me.
I have had success with the photon torpedo method on 2.3.5. I recommend trying it again being extra careful to follow the steps exactly.
Sent from my MB855 using XDA
Shad0wguy said:
I have had success with the photon torpedo method on 2.3.5. I recommend trying it again being extra careful to follow the steps exactly.
Sent from my MB855 using XDA
Click to expand...
Click to collapse
Photon torpedo was what worked for me, except that I had to push it from the command prompt on my windows 7 laptop. For some reason, I couldn't get it to work with Terminal emulator. Good luck!
I used Motorola DROID 3 one click. Worked great.
Sent from my MB855 using XDA
Thank you, I will try the Droid 3 OCR, and if that does not work, see if I can get Torpedo to work, and if that does not work I will send it in to Motorola.
Use torpedo thru terminal emulator on your phone as I did
Sent from my Motorola Electrify using XDA
What worked for me was to use the command prompt on windows 7 instead of terminal emulator. For some reason, TE could not see the photon-torpedo file in the phone after i had transferred it there. Command prompt did.
Sent from my MB855 using xda premium
Also remember to reboot after!
I got the OTA update to 2.3.5 yesterday, and photon-torpedo is NOT working for me. After running photon-torpedo.sh, I get the error message, but my prompt doesn't change to # or root. Trying to run install-su.sh doesn't work since I'm not root and gives me permissions errors. Has anybody gotten photon-torpedo to work after yesterday's OTA update?
UPDATE:
I figured out the issue and a fix:
http://forum.xda-developers.com/showpost.php?p=28669160&postcount=363
JohnH4 said:
Photon torpedo was what worked for me, except that I had to push it from the command prompt on my windows 7 laptop. For some reason, I couldn't get it to work with Terminal emulator. Good luck!
Click to expand...
Click to collapse
what commands do I have to enter to get my Windows 7 CP to do things on the Photon? Also, I tried making a data folder in my internal storage, then a tmp, and put the winrar photon torpedo into it and tried following the steps and it didn't work. I'm on 2.3.5 too. What could I be doing wrong?
can someone please help me with my post above?
For those who successfully rooted w/Photon Torpedo... is your 2.3.5 from the May Soak, was it re-soaked last week, or was it 2.3.5'ed for the first time this week?
God, I'm glad I told Moto to fsck off & swore I'd never install another Moto update (soak, push, or otherwise) again. Refusing last week's soak just might have enabled me to grudgingly endure my final 50 days with this miserable excuse for an Android phone.
Sent from my MB855 using Tapatalk 2
bitbang3r said:
For those who successfully rooted w/Photon Torpedo... is your 2.3.5 from the May Soak, was it re-soaked last week, or was it 2.3.5'ed for the first time this week?
God, I'm glad I told Moto to fsck off & swore I'd never install another Moto update (soak, push, or otherwise) again. Refusing last week's soak just might have enabled me to grudgingly endure my final 50 days with this miserable excuse for an Android phone.
Sent from my MB855 using Tapatalk 2
Click to expand...
Click to collapse
here's an easy way to do Photon Torpedo: http://www.groovypost.com/howto/motorola-photon-4-g-how-to-root-your-phone/
DiamondJay20 said:
what commands do I have to enter to get my Windows 7 CP to do things on the Photon? Also, I tried making a data folder in my internal storage, then a tmp, and put the winrar photon torpedo into it and tried following the steps and it didn't work. I'm on 2.3.5 too. What could I be doing wrong?
Click to expand...
Click to collapse
You don't need to create /data/tmp in your phone's internal storage. That folder already exists inside the system partitions. Use ADB to push it in. Follow the instructions in the Photon Torpedo thread.
Sent from my MB855 using xda app-developers app
I didn't have my phone Rooted before the update to Android 2.3.5 but after trying several different methods I found one that worked with ADB and torpedo program/files with a step by step that actually says to have 2.3.5 I followed the instructions and it worked for me, only problem I had was I unzipped the photon-torpedo.tar file by mistake... it doesn't have to be unzipped into the folder just place the whole file in the folder.
Hears a link to the walk through from gamerguy13
instructables.com/id/How-to-get-root-access-on-your-Motorola-PhotonEle/?ALLSTEPS
Good luck everyone else trying to root or re-root.
DiamondJay20 said:
what commands do I have to enter to get my Windows 7 CP to do things on the Photon? Also, I tried making a data folder in my internal storage, then a tmp, and put the winrar photon torpedo into it and tried following the steps and it didn't work. I'm on 2.3.5 too. What could I be doing wrong?
Click to expand...
Click to collapse
The MoPho I rooted is fairly unique, so I can't promise anything, but this is what worked for me. All credit goes to edgan. I didn't develop anything.
Photon Root Instructions
1. Create a folder in the C:/ drive on your Windows 7 machine called Photon root. (You can call it anything you want, but that’s what I called mine and will use for the purpose of this post).
2. Download and install the adb package from here and install them into C:/Photon root.
3. Download photon-torpedo.tar from here and copy it to C:/Photon root in your windows machine. Do not unzip it.
4. On your phone, go to Settings > Applications > Development and select USB Debugging.
5. Plug your phone to your computer and on your phone, set it to USB Mass Storage.
6. Copy photon-torpedo.tar from C:/Photon Root to your phone’s internal storage using Windows 7. Don’t put it in any folder, and leave it zipped.
7. Install Superuser from the Market. (This is absolutely necessary to do before you get started or it won’t work)
8. Open the command prompt (Start >> run “cmd” >> enter)
9. Type the following commands – don’t worry about the errors, it will be all right
• cd C:/photon root
• adb push photon-torpedo.tar /data/tmp
• adb shell
• cd /data/tmp
• /bin/tar xf /data/tmp/photon-torpedo.tar
• /data/tmp/photon-torpedo.sh
• /data/tmp/install-su.sh
10. That's it. Reboot and enjoy.
Hey Mopho's - I'm currently running a rooted (via shabby's AIO) stock sprint v 2.3.4 .... System Version : (45.3.6.MB855.Sprint.en.US) / Build number : 4.5.1A-1_SUN-198_6
I've tried downloading the OTA 2.3.5 via wifi, and installation was going ... but upon reboot - it says update failed. Tried this 2x - I didn't see many commenting on going back to an original stock rom before, getting the OTA update, and that rather - rooted devices would be unrooted after 2.3.5 OTA. I've never installed any other ROM besides what came with the phone...
Was there something I needed to do to "unroot" or revert without wiping/losing my current settings / apps ? Basically, what can I do to get this done
rooted apps installed : AdAway / Superuser free / Root Basic Check free / LBE Privacy Guard / Wifitether
Thanks in advance for the info. I realize Shabby's AIO will not re-root my phone, so will need to see the ADB/Torpedo methods posted here after. I just need to get the OTA update working first.
I would think twice before taking that ota update. Currently, under 2.34, your bootloader should be unlockable. The main effect of the 2.35 update is to lock the bootloader.
Sent from my MB855 using xda premium
Worked for me
JohnH4 said:
The MoPho I rooted is fairly unique, so I can't promise anything, but this is what worked for me. All credit goes to edgan. I didn't develop anything.
Photon Root Instructions
1. Create a folder in the C:/ drive on your Windows 7 machine called Photon root. (You can call it anything you want, but that’s what I called mine and will use for the purpose of this post).
2. Download and install the adb package from here and install them into C:/Photon root.
3. Download photon-torpedo.tar from here and copy it to C:/Photon root in your windows machine. Do not unzip it.
4. On your phone, go to Settings > Applications > Development and select USB Debugging.
5. Plug your phone to your computer and on your phone, set it to USB Mass Storage.
6. Copy photon-torpedo.tar from C:/Photon Root to your phone’s internal storage using Windows 7. Don’t put it in any folder, and leave it zipped.
7. Install Superuser from the Market. (This is absolutely necessary to do before you get started or it won’t work)
8. Open the command prompt (Start >> run “cmd” >> enter)
9. Type the following commands – don’t worry about the errors, it will be all right
• cd C:/photon root
• adb push photon-torpedo.tar /data/tmp
• adb shell
• cd /data/tmp
• /bin/tar xf /data/tmp/photon-torpedo.tar
• /data/tmp/photon-torpedo.sh
• /data/tmp/install-su.sh
10. That's it. Reboot and enjoy.
Click to expand...
Click to collapse
John was right, just ignore the errors. This method by edgan worked for me.
---------- Post added at 07:28 PM ---------- Previous post was at 07:16 PM ----------
bitbang3r said:
For those who successfully rooted w/Photon Torpedo... is your 2.3.5 from the May Soak, was it re-soaked last week, or was it 2.3.5'ed for the first time this week?
God, I'm glad I told Moto to fsck off & swore I'd never install another Moto update (soak, push, or otherwise) again. Refusing last week's soak just might have enabled me to grudgingly endure my final 50 days with this miserable excuse for an Android phone.
Sent from my MB855 using Tapatalk 2
Click to expand...
Click to collapse
I agree with bitbang, I've had enough of this bullsh*t from Motorola. It's time for me to shop around. Unfortunately for me, I have a little more than a year on my contract! I've heard that Sprint had some kind of buy back or release program where they let you trade in your phone for something new (for a "small" fee, of course). It just might be worth it to get away from Moto. This smartphone technology changes way too fast for 2 year contracts anyway.
It's a shame. When I can get this phone to work properly, it is awesome, I'm sure bitbang even agrees with that but it is definately time to move on. The Samsung Galaxy 3 looks pretty cool!
amlodipine said:
Hey Mopho's - I'm currently running a rooted (via shabby's AIO) stock sprint v 2.3.4 .... System Version : (45.3.6.MB855.Sprint.en.US) / Build number : 4.5.1A-1_SUN-198_6
I've tried downloading the OTA 2.3.5 via wifi, and installation was going ... but upon reboot - it says update failed. Tried this 2x - I didn't see many commenting on going back to an original stock rom before, getting the OTA update, and that rather - rooted devices would be unrooted after 2.3.5 OTA. I've never installed any other ROM besides what came with the phone...
Was there something I needed to do to "unroot" or revert without wiping/losing my current settings / apps ? Basically, what can I do to get this done
rooted apps installed : AdAway / Superuser free / Root Basic Check free / LBE Privacy Guard / Wifitether
Thanks in advance for the info. I realize Shabby's AIO will not re-root my phone, so will need to see the ADB/Torpedo methods posted here after. I just need to get the OTA update working first.
Click to expand...
Click to collapse
When the update fails and you see the Android guy with the "!", press and hold both volume up and down. This will show you on the screen why it failed. Common causes for failure are mods to the build.prop file or removal of core apps.
So while I am quite satisfied with the factory firmware on the XT925/926 as-is, the email client is rather clunky and I prefer the AOSP version. Good news guys, the factory firmware can use the AOSP Email.apk!
Credit goes to kabadisha for the original, easy to follow instructions.
Before You Start...
[MANDATORY] First and foremost, the phone needs to be rooted. If you haven't done so, check out this thread: http://forum.xda-developers.com/showthread.php?t=1943851
[MANDATORY] ADB on your computer or Terminal Emulator app on the phone. If you want ADB, the email-policy-patch in this thread has the file in the 'lib' folder: http://forum.xda-developers.com/showthread.php?t=1117452
[RECOMMENDED] Titanium Backup for backing up and removing the stock Motorola Email client. If you want to save these files, do this before proceeding to the instructions below. The APK files you need to backup/remove are MotoEmail.apk and MotoEmailConfig.apk.
Instruction for ADB Users
Connect the phone to the computer.
Download the corresponding Email.apk and Exchange.apk in the attachment section at the end of this post. Get the ones with the prefix 'ICS_' if you are on 4.04 Ice Cream Sandwich firmware, OR 'JB_' if you are on the 4.1.2 Jellybean firmware. DO NOT mix them or use the wrong ones, as they may not work correctly. Rename them to Email.apk and Exchange.apk respectively and place them in the root directory of your phone's internal SD card.
Go to the directory where you put your ADB executable. Hold SHIFT key, right-click anywhere in the window in this directory and select 'Open Command Prompt Here'.
Type the following in the command prompt and press Enter:
Code:
adb shell
If the Motorola driver is installed correctly and the phone is plugged to the PC, it should change the prompt to '[email protected]'. Type the following and press Enter, and the prompt should change to '[email protected]':
Code:
su
Now you're ready to actually do the work of getting the AOSP Email client on the phone. First, we need to set the /system partition to allow us to read/write to that directory, and remount it to make sure the permissions are updated. Type the following and press Enter:
Code:
mount -o rw,remount /system
...Let's change the current active directory to where all of the phone's installed apps are kept. Type the following in the command prompt and press Enter:
Code:
cd /system/app
Type the following in the command prompt and press Enter to copy the Email.apk that you downloaded earlier into this directory:
Code:
cp /sdcard/Email.apk /system/app/Email.apk
Type the following in the command prompt and press Enter to copy the Exchange.apk that you downloaded earlier into this directory:
Code:
cp /sdcard/Exchange.apk /system/app/Exchange.apk
Almost there! The last thing we need to do is change the permissions of these copied files so the OS can handle them properly. Type the following and press enter:
Code:
chmod 744 Email.apk
Code:
chmod 744 Exchange.apk
*Thanks to vrus1 for pointing this out*
Code:
Go to Settings > Manage App > Email and select 'Clear Data'.
Reboot the phone. Do this the ol' fashion way by directly interfacing with the device or enter the following in the prompt:
Code:
exit
Code:
exit
Code:
adb reboot
Click to expand...
Click to collapse
Instruction for Terminal Emulator Users
Connect the phone to the computer.
Download the corresponding Email.apk and Exchange.apk in the attachment section at the end of this post. Get the ones with the prefix 'ICS_' if you are on 4.04 Ice Cream Sandwich firmware, OR 'JB_' if you are on the 4.1.2 Jellybean firmware. DO NOT mix them or use the wrong ones, as they may not work correctly. Rename them to Email.apk and Exchange.apk respectively and place them in the root directory of your phone's internal SD card.
Open the Terminal Emulator app. Type the following in the command prompt and press Enter:
Code:
su
Now you're ready to actually do the work of getting the AOSP Email client on the phone. First, we need to set the /system partition to allow us to read/write to that directory, and remount it to make sure the permissions are updated. Type the following and press Enter:
Code:
mount -o rw,remount /system
...Let's change the current active directory to where all of the phone's installed apps are kept. Type the following in the command prompt and press Enter:
Code:
cd /system/app
Type the following in the command prompt and press Enter to copy the Email.apk that you downloaded earlier into this directory:
Code:
cp /sdcard/Email.apk /system/app/Email.apk
Type the following in the command prompt and press Enter to copy the Exchange.apk that you downloaded earlier into this directory:
Code:
cp /sdcard/Exchange.apk /system/app/Exchange.apk
Almost there! The last thing we need to do is change the permissions of these copied files so the OS can handle them properly. Type the following and press enter:
Code:
chmod 744 Email.apk
Code:
chmod 744 Exchange.apk
*Thanks to vrus1 for pointing this out*
Code:
Go to Settings > Manage App > Email and select 'Clear Data'.
Reboot the phone.
Click to expand...
Click to collapse
Once the phone has been rebooted, you should now have the AOSP Email Client in the application menu. Set it up as normal and you should be ready to roll. So far I have not run into any sync issues or anything out of the ordinary. If you are experiencing otherwise, please let us know!
Closing Notes
If you encounter any issues following these steps, please let me know so I can correct it.
Other Motorola ICS/JB device users: This should work for your devices as well as the firmwares between our devices are nearly identical.
Using the AOSP Email client will now allow you to use the Exchange Security Policy Bypass script that is not compatible with the Motorola client. Please be aware that by doing this, you may be violating your company's security policies which may place you under severe disciplinary actions or job termination at your company's discretion. Others that have provided the tools and instructions to perform this, including myself, cannot be held responsible if the worse case scenario occurs. You have been warned.
Sorry to bother.
Could these files be used for ICS 4.0.4 Samsung Galaxy SIII?
I've been trying like crazy to get the AOSP Email apk working.
Thanks for any feedback or recommendation.
Sent from my Nexus 7 using Tapatalk 2
Hobbes2099 said:
Sorry to bother.
Could these files be used for ICS 4.0.4 Samsung Galaxy SIII?
I've been trying like crazy to get the AOSP Email apk working.
Thanks for any feedback or recommendation.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
No guarantees. While this method uses generic Unix commands that all Android devices will understand, it all depends on how the manufacturer has their firmware setup since some may have the Email client integrated into their launcher framework for notification counters, widgets, etc. You can attempt this and see if it works, and worst case scenario, simply delete the two files from \system\app to reverse the process.
For the Galaxy S III, I believe your Email client is SecEmail.apk and Exchange.apk. Backup and remove those before using the files in the attachment.
Worked great on my Droid Razr Maxx - thanks!
Thankss
Anybody try this on the RAZR Max HD with vrz
Sent from my DROID RAZR HD using Tapatalk 2
This is awesome. Thanks for posting this info. Works great on Bionic ICS.
Is this the black version?
Sent from my XT910 using xda app-developers app
Does this disable the exchange security?
mikeymax said:
Anybody try this on the RAZR Max HD with vrz
Sent from my DROID RAZR HD using Tapatalk 2
Click to expand...
Click to collapse
Yes, this procedure was done successfully on a RAZR MAXX HD.
zhzaen said:
Does this disable the exchange security?
Click to expand...
Click to collapse
No, it takes you halfway there -- getting the AOSP Email client on your phone, which is compatible with the email-policy-patch script that can modify these APKs. You cannot disable the exchange security on the stock Email that comes on your Motorola phones because it is custom.
anyone able to get these or actual AOSP JB Email apks to work with the JB leak?
Ive tried these ICS apk and some JB apks I found. No luck on either.
I assume we could just use root explorer to do this as well right?
Gave this a go to see if it can see folders within my inbox of my corporate exchange account.. nope. back to stock for now.
Apparently the 4.0.4 version doesnt work properly in this regard and the 4.1.x can do it..
Thank you anyway.
Doesn't work on mine.. FC as soon as you try to open Email app.
I am running stock 4.0.4 Razr HD LTE from Rogers. I followed instructions to a "T". Everything worked as expected but it just wont run.
Ok.. Got it working... Before removing/renaming old Email client, go into Manage Apps, Email, CLEAR DATA.
Then rename old files and push new ones.
Reboot.
Go back into Manage Apps, Email, CLEAR DATA.
Reboot.
Works great and thank you for sharing!!! I hate the stock app because it doesnt synchronize Email Reply/Forward status and drove me crazy.
Jelly Bean Official. Now Let's Do This.
OK. So now that JB is pushed out, I really need to get working on this. If anyone has any direction or ideas, please share. The blur email is awful, plus I really want to disable Exchange security policy.
Other than the email app, the HD Maxx is the best phone out there. I went back to it from a HTC DNA.
AOSP FTW.
vrus1 said:
Ok.. Got it working... Before removing/renaming old Email client, go into Manage Apps, Email, CLEAR DATA.
Then rename old files and push new ones.
Reboot.
Go back into Manage Apps, Email, CLEAR DATA.
Reboot.
Works great and thank you for sharing!!! I hate the stock app because it doesnt synchronize Email Reply/Forward status and drove me crazy.
Click to expand...
Click to collapse
Following this procedure got it working for me. Thanks for the Clear Data tip. I think users should note, you MUST reboot after clearing data. Simply clearing data and relaunching the app does not work.
My setup is rooted OTA JB. I used rootkeeper to retain root through the OTA update. After following the OP directions, I kept getting force closes and crashes. I simply thought it was because of JB and it may have been. However after reading through the rest of the post, user VRUS1's tip got it working. This step should be added to the OP.
Thanks to both of you. I couldn't stand the MotoEmail.apk...
Thanks for this!! This was a life saver for me!!
Thank you for the feedback guys. I disappeared for a bit and now have a XT925 RAZR HD and I'm running JB firmware with AOSP Email client right now. I will update the original post with the comments and Jellybean APKs tonight.
It's been updated with Jellybean APKs and revised instructions. As usual, please provide feedback if something is off in the instructions or you experience abnormal issues.
So I bricked my Kinde Fire HDX by changing the build.prop and not fixing permissions. I have adb access but no root (I don't know why :S). Would a factory reset work? If not, how can I get to fix the build.prop or replace it with the old one? thank very much, I've been a couple hours looking for solution but I couldn't find any.
No, a factory reset would only break it further. It would remove your adb access and not fix anything. What makes you think you lost root? Have you tried "adb shell" then "su"?
Sent from my Amazon Tate using Tapatalk
r3pwn said:
No, a factory reset would only break it further. It would remove your adb access and not fix anything. What makes you think you lost root? Have you tried "adb shell" then "su"?
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
I used the HDX ToolKit v0.92 to check the root access, and it said "Please grant root on your device"
I've also tried "adb shell", and then "su", but it just returns "su" again. I am new with adb commands so I don't really know what it should show.
Thank you very much for your help
May I ask what version you were on before you bricked?
Sent from my Amazon Tate using Tapatalk
14.3.2.3.2, last update I think.
?
peter_b93 said:
14.3.2.3.2, last update I think.
Click to expand...
Click to collapse
Fixed?
jimyv said:
Fixed?
Click to expand...
Click to collapse
Nope, I couldn't find any way to get root acces again. But nevermind, my new kindle fire will be here in two days. I am surprised how well amazon costumer service works. Even though I bought my kindle in the US and now I am in Spain (not going back), they called me from the US for free, and they are paying all the shipping costs and sending it by priority shipping.
I am still interested if anyone knows how to fix it, just for fun
well
peter_b93 said:
Nope, I couldn't find any way to get root acces again. But nevermind, my new kindle fire will be here in two days. I am surprised how well amazon costumer service works. Even though I bought my kindle in the US and now I am in Spain (not going back), they called me from the US for free, and they are paying all the shipping costs and sending it by priority shipping.
I am still interested if anyone knows how to fix it, just for fun
Click to expand...
Click to collapse
It sounds like to me that you still root access you just were not mounted RW in other words it would not boot up completely so you could hit allow to the adb Shell. So you will have to mount system rw manually Try last 3 pages of this thread http://forum.xda-developers.com/showthread.php?t=2588608. He can fix you most likely if you can comprehend and follow directions.. or if ur understanding adb is fair you'll be able to probably extract your repair from the thread as is.
jimyv said:
It sounds like to me that you still root access you just were not mounted RW in other words it would not boot up completely so you could hit allow to the adb Shell. So you will have to mount system rw manually Try last 3 pages of this thread http://forum.xda-developers.com/showthread.php?t=2588608. He can fix you most likely if you can comprehend and follow directions.. or if ur understanding adb is fair you'll be able to probably extract your repair from the thread as is.
Click to expand...
Click to collapse
I've tried what it is said in the other thread. However, the problem there is that the guy cannot get his device to be recognized.
I've tried this:
adb root
adb shell
su
mount -o rw,remount /system *****- if this fails, try: mount -o remount /system
chmod 644 /system/build.prop
chown root.root /system/build.prop
reboot
But adb root gives me this error:
adbd cannot run as root in production builds
On the other hand if I skip the "adb root" step I cannot go further than "su" since I don't get the "[email protected]:/ #" line.
well
peter_b93 said:
I've tried what it is said in the other thread. However, the problem there is that the guy cannot get his device to be recognized.
I've tried this:
adb root
adb shell
su
mount -o rw,remount /system *****- if this fails, try: mount -o remount /system
chmod 644 /system/build.prop
chown root.root /system/build.prop
reboot
But adb root gives me this error:
adbd cannot run as root in production builds
On the other hand if I skip the "adb root" step I cannot go further than "su" since I don't get the "[email protected]:/ #" line.
Click to expand...
Click to collapse
Well since you do have ADB connectivity why can't you hook a bruting utility and push root ? Romaster_3.4.3.7593_Setup use as describe back in the roll back thread and the rooting thread 4 the new yes I kno wat is in chinese but this is the 1 that you must use sent you cannot install the apk install software plugin your tablet look at the upper right corner you will see an gear icon tap that then second row down second icon over "root"
jimyv said:
Well since you do have ADB connectivity why can't you hook a bruting utility and push root ? Romaster_3.4.3.7593_Setup use as describe back in the roll back thread and the rooting thread 4 the new yes I kno wat is in chinese but this is the 1 that you must use sent you cannot install the apk install software plugin your tablet look at the upper right corner you will see an gear icon tap that then second row down second icon over "root"
Click to expand...
Click to collapse
FIXED!!!!!
The chinese software worked! Thank you very much! As I first rooted with towelroot I wasn't aware that it was possible to root without booting into android! I think I won't edit the build.prop again lol.
peter_b93 said:
FIXED!!!!!
The chinese software worked! Thank you very much! As I first rooted with towelroot I wasn't aware that it was possible to root without booting into android! I think I won't edit the build.prop again lol.
Click to expand...
Click to collapse
Ok now use this http://forum.xda-developers.com/showthread.php?t=2532818 and uninstall romanager from pc...and reboot... And BTW modifying your build prop is alot easier useing build prop editing app. It takes care of permissions anyway as long as you entrys are correct..
jimyv said:
Ok now use this http://forum.xda-developers.com/showthread.php?t=2532818 and uninstall romanager from pc...and reboot... And BTW modifying your build prop is alot easier useing build prop editing app. It takes care of permissions anyway as long as you entrys are correct..
Click to expand...
Click to collapse
Good call on RomMaster. I have no idea what it is doing since I haven't had any time to look at it, but I'd figured it was an app like TR. At any rate, nicely done. :good:
sweet
GSLEON3 said:
Good call on RomMaster. I have no idea what it is doing since I haven't had any time to look at it, but I'd figured it was an app like TR. At any rate, nicely done. :good:
Click to expand...
Click to collapse
I'm not sure either that's why when I used it I was on a blacklisted unit and I kept the PC and the tablet and airplane mode at all times. Until I was certain I got all the files off of both before I let them go to Wi-Fi Chinese files that is.. But one thing I was very curious about is if you open that tool up the Chinese tool that is an you go to the same page you would hit the anchor to root to your device just below that it says fastboot I'm wondering if they have a fastboot working for also too bad nobody here know Chinese..