(x-post from autoproxy thread) lg optimus one p500h vs. autoproxy - Optimus One, P500, V General

hello --
i recently bought a pre-paid telus lg optimus one to be used with petrocan mobility.
the phone was initially at version 2.2.1 of android; i used the desktop lg tool to upgrade it to android 2.3.3.
i unlocked the phone and subsequently rooted it with superoneclick.
next, i downloaded autoproxy from the android market and configured it to work with petrocan's "unlimited mobile browsing" service -- only port 80 (http) traffic goes through. and it seems to work: youtube, maps, android market, etc.
but when i tried to turn autoproxy off, i got the following error message:
Failed to stop proxy (
[: not found
killall: not found
busybox: not found
rm failed for /data/data/com.mgranja.
autoproxy/files/redsocks.conf, no such
files or directory)
using the adb shell, i've poked around my phone to find busybox & killall, to no avail.
right now i'm stuck with autoproxy in a funky state: it thinks it's connected, even though i now have turned wireless data off.
and i can't tell it to stop.
i've searched all forums high and low for an explanation of what the problem, and could not find anyone with the same problem, which i found surprising.
so, the question: how to i get autoproxy to turn itself off correctly?
thanks in advance!
p.s.: btw, autoproxy does work when activated: i was able to update skype from what came with my phone (or what came with the official telus android 2.3.3 release) and use it, despite petrocan's filtering of non-browser activity. so for that, i am a happy camper. but having to turn off my phone every time i want to turn autoproxy off, whilst a work-around, sort of ruins the picture.

Guess you need to install busybox, you can find an installer in market.
Sent from my LG-P500 using XDA App

success with autoproxy on my optimus one
*** i know most of this has already been mentioned on this website and elsewhere, but this is my attempt to summarize everything in one post.
so i finally got autoproxy to work 100% as expected. all in all, i feel that the pre-requisites were not correctly identified. so here they are below, to avoid anyone else with an lg optimus one p500h wasting time trying to make things work:
* unlock your phone (can't hurt, even if you don't have to)
download the following three windows packages:
* superoneclick (at least v2.3.3.0)
* android sdk (at least r16)
* java jdk (at least v7u3)
for the next two android apps, you will have to get yourself an android marketplace account and set up a payment arrangement with google to be able to purchase autoproxy (it's worth the small amount the dev asks for).
* busybox (from 'stericson' -- at least v7.5.5)
* autoproxy (android app -- at least v0.60)
your optimus one (or any other android device, for that matter) must be rooted to make use of autoproxy.
understand it's also missing busybox by default, this is why you need to download it.
install the windows apps: java jdk, then android sdk.
extract superoneclick from its .zip file.
connect your phone to your windows pc via usb, put it in usb debug mode.
start superoneclick and root your phone.
once you're done, go to the android market and get stericson's busybox.
even though it looks installed (nice little icon in the android gui), you have to start it to be able to install the core software that autoproxy uses. select version 1.19.2.
once busybox says it's fully installed, get autoproxy.
configure as needed.
voilà!

Related

Auto-Nooter 2.12.25 (1.0.1 Only)

This is an automated nooter file to streamline the rooting process for the NookColor. This has been tested by myself and others.
Thanks To: pokey9000 for nooter, Mistar Muffin for Market and GTalk Fix, clockworx for the hacked framework.jar used to get androidID, mastapsi for testing and coding, lewellyn for coding, [mbm] for ABI Fix, Suteru for the new custom Boot Animation,Hotaru for the Gingerbread keyboard, rpollard00 for DroidX keyboard with bigger font, bpk for Soft Keys, Ben74 for NookColor Tools which enables Non Market Installs, Freenode's #nookcolor chat for dealing with my crap and checking my code.
Please Note: If I'm using your app within AutoNooter and you'd like it removed please send me a PM stating so and I will do so for future versions.
DO NOT USE THIS IF YOU ARE 1.0.0
There are a few bugs before I can release 3.x.x that need to be worked out.
This is the only officially supported AutoNooter by those working on AN
Changes:
Added: Gingerbread Keyboard.
Deleted: YouTube.apk from /system/app
Update: Busybox has whoami
Update: Installs Soft Keys 3.0.0
What it does:
Installs su and Superuser.apk
Installs Busybox
Installs Softkeys 3.0.0
Installs NookColor Tools (To Enable Non-Market Installs)
Installs Calendar and Calculator.
Installs Android Market, Gmail, Youtube
Enable Multi-touch for Android Apps
Enables Live Wallpapers
Enables Android Market and Gmail.
App Auto Install (Open up NooterFiles from sdcard drop in /data/app)
Still Needs:
Custom Kernel to display something while working.
How to Use:
Before you begin:
* To update to 1.0.1 you must do a complete wipe.
* You must update to 1.0.1 to use AutoNooter 2.12.25 Instructions Here.
1 You must already have a registered NOOKcolor
2 You must have a Gmail/Youtube linked Account. IF you used a Gmail account for B&N Registration you should use that one for this process.
3 You must either have dd (Linux) or WinImage (Windows) software.
4 You must have an external microSDCard reader or this will not work. Do NOT use the NC.
5 You must have enough intelligence to follow instructions.
Let's get started:
1 Download Auto-Nooter from here: auto-nooter-2-12-25.img.zip
2 Linux: Unzip and use dd if=auto-nooter-2-12-25.img of=/dev/sdcard
2 Windows: Unzip and use WinImage to "Restore Virtual Hard Disk Image" to your SDcard.
2 Windows Alternative: https://launchpad.net/win32-image-writer/+download
3 Unplug your NOOKcolor from computer. (If Plugged in.)
4 Insert AutoNooter SDcard into your NOOKcolor.
5 Plug the USB cable into your computer and your NOOKcolor. (This will boot up the NOOKcolor.)
6 Your NookColor will reboot when it's done.
That was the hard part, now to the simple stuff.
7 Upon boot unlock your screen.
8 At the Android Welcome Screen skip Sign In.
9 Enable Location Services when given the option.
10 Connect to Wifi and launch Youtube from "Extras".
11 Click the Menu button (The one RIGHT of the Up Arrow).
12 Select "My Channel" and Login using your Gmail Account.
13 Exit Youtube and Launch Gmail from "Extras".
14 Sync your Gmail Account and Exit. (If it fails to sync that is fine.)
15 Open up Market and Accept Terms and Service.
If you made it this far your nook should be successfully Rooted. Go Download an App to make sure.
16 Enable Non-Market Installs by running the NookColor Tools App.
17 If your Youtube fails to launch Uninstall and Reinstall Youtube from /data/app
18 Go to Settings > Device Info > SdCard > UnMount > Format
Complete Wipe:
1 8 Failed Boots > Wipes /system
2 Factory Reset > Wipes /data
You must do both of these to completely wipe clean your NOOKcolor.
Is it safe to try this after already having done Nooter 0.2?
The manual market install hasn't done the trick for me. Every time I have to restage the thing, if I'm not at home, I have to run out and find a wi-fi point to re-register it (argh).
I've had no ill effects from running this over an already nootered system with Market already fully functioning.
Link broken? Not finding it.
Never mind. Got it. You've got an extra j on the end BTW
I already have the market hack working but I don't have calendar and live wallpapers and some other stuff listed.
So just to be extra clear, this is save to just install over what I have already?
EDIT: WOW, this worked really WELL! I didn't mess up my already done hacks
And a little surprise in in store! It has the NEW market installed!
EDIT: Never mind, tired.
I'll be your guinea pig...will try it now.
Thanks for pointing out the extra j. Took it out.
While you're at it, you might as well include the ADHOC fix...
http://forum.xda-developers.com/showthread.php?t=872521
Wow. I've got an Android setup wizard. Should I run through it? I haven't seen this before on the NC.
"Learn how to use your LogicPD Zoom2"
Ohs you can try, but it should fail at "sign in" you want to skip it so that you can enable location.
johnopsec said:
While you're at it, you might as well include the ADHOC fix...
http://forum.xda-developers.com/showthread.php?t=872521
Click to expand...
Click to collapse
I dunno. Some people don't tether and probably don't want to hassle switching back and forth. I think that one is kinda optional right now. Probably better off waiting for a good, permanent ad-hoc / infrastructure fix.
greenmky said:
I dunno. Some people don't tether and probably don't want to hassle switching back and forth. I think that one is kinda optional right now. Probably better off waiting for a good, permanent ad-hoc / infrastructure fix.
Click to expand...
Click to collapse
When installed, it defaults to the "stock" Infrastructure (AP) only wpa_supplicant that shipped with the NC. This simply gives them the option off switching to ADHOC mode if they need it.
I've been watching the progress on adhoc and it's currently unstable. As soon as there's a more stable adhoc solution it will most definitely be put in a future version.
Same server error as before for the Market.
"! Attention"
A server error has occurred. Retry, or cancel and return to the previous screen.
Anything else I should do?
This is the same thing that occurred with the manual Market enable process.
I'm convinced there's still something wrong with this whole process for some of us. I know there's 3-4 people getting the same server error as me for the market.
Should I try the manual editing of the packages.xml file?
You can always try to do a factory fallback then rerun autonooter or go look in freenode.net's #nookcolor, others have confirmed that Market works with this so there may be another issue someone in there can help you figure out.
There's been some suggestion that the androidID may not have been properly create, this may of happened if you messed with the db that holds it.
GabrialDestruir said:
You can always try to do a factory fallback then rerun autonooter or go look in freenode.net's #nookcolor, others have confirmed that Market works with this so there may be another issue someone in there can help you figure out.
Click to expand...
Click to collapse
Yeah, there's a problem with the process still somehow. This is the same results as the manual process.
This is much easier though and faster to redo. Maybe they'll find the bug in the process for those of us that it doesn't work for.
EDIT: Just a note. The Auto-Nooter didn't change my packages.xml file to remove these lines:
<sigs count="n">
<cert index="n" />
</sigs>
Not sure if it was supposed to...but it's in the manual install instructions.
Well if you can come into the irc chat maybe someone there can help you figure out the issue and we can see about adding the fix the next version.
Thanks to auto-nooter I was able to get farther than I did before with nooter .2 version. However, I've got a new problem.
After rebooting the NookColor, it started the Android tutorial. Then, when I tried to set up my Google account, I couldn't click on the "Enter Account" option since I already have a Google account. When I tried the enter account in the future option, Android seemed to immediately crash on me and the NookColor went to the normal B/N interface.
I power cycled the NookColor. However, now it immediately goes into the B/N interface, and I never see Android.
Any ideas?
Robert
Well you were suppose to skip the entering info so that it'd ask you if you want to enable location. I'm not sure if it's possible or not to get SetupWizard running again. I don't know anyone that's tried either.
Awesome! Market finally works. Thanks a lot for this! It didn't even break my previous mods.

help with rooting IDeaUSA 7" tablet

I am trying to find a how to root idea usa 7" tablet from fry's for $77.00. Their is a lot of rooting programs but I have not been able to find anything on this model.
Also what would be a good rom to flash it with? I tried finding out if uberoid or cyanogenmod would work but I could not find any info on this model.
Not to sure what model I have that I would be able to flashing this rom with, either uberoid, cm7/cm9 or miui? Help
Model: MID, sv7206 v1.4, kernel 2.6.35.7-infotm
processor armv6 rev5,
hardware imapx200,
android 2.3.3,
brand infotmic,
display gri40,
release codename REL
bootloader unknown
I don't know if this is the right model IDea USA IUMID-0071 because the spec's are off. Http ://ideausa.us/produects.html but similar. I am looking for rom that is more update/modern. any potters?
Does anyone have the original rom for this or know how to make a backup this rom?
Well I am thinking that is might be this model but not to sure wm8650,SV7206 v1.4 or IDea USA IUMID-0071.
The screen is very slow on this model. Unless you use a pen then is works better.
Also hoping to be able to flash this to ics 4
Just trying to get some clarification.
Try running the superoneclick batches. Shortfuse.org
Sent from my HTC Sensation Z710e using XDA App
Thanks, I am download it right now.
Also can you use airdroid to do a backup or has anyone tried this yet and maybe upload a rom that way? any thoughts?
Thanks
Never heard of airdroid
Sent from my HTC Sensation Z710e using XDA App
AirDroid is a fast, free app that lets you wirelessly manage & control your Android device from a web browser Over-The-Air. Just for anyone that wants to know.
I don't know if airdroid can copy all of your file to the desktop from your browser. But I don't know how the file system works for the android. So I wouldn't know if it can or is there a good place to read about the android file system? Wait I know I will google that. google is my friend. But I was hoping for a more advance person that could answer on this topic than me.
Thanks
U have to have a custom recovery to do nandroid backups
Sent from my HTC Sensation Z710e using XDA App
I have not been able to connect this device to the computer. Nothing is being recognize. It does not show up under linux os either. I am not sure what drivers will work for this thing. USB debugging is also enabled.
Any ideas?
Thanks
Rooting Idea USA Tablet
Oh my, what a mess...
This post is in regards to the Idea USA Tablet (Unable to Root)
My specs:
- Idea USA Tablet (Made in China)
- Model Number: MID (Unknown)
- Android Version: 2.3
- Kernel Version: 2.6.35.7
- Build Number: MID-userdebug 2.3 GRH55 (ENG)
Issues:
Whelp, I have tried the basics and I can't get this thing to root for anything. I was able to get it to hook into the PC through USB. There are 2 usb slots on the side of the tablet. I believe one is for HOST and the other usb is for OTG (Charging). Once I figured out the host port, then I had to download the drivers for this poorly made tablet...But, what drivers? You go to the Idea US website and you get no helpful information. So, there are no drivers made specifically for this $100 dollar generic tablet from FRY's. Ok... No big deal... So, I download the default "Android USB Drivers".
Peachy, it worked! Now, I can transfer files back and forth between the card(s). Wonderful, first step down, next step was to root. So, I read up on how to root with Super One Click.
Ok, so now, I set the tablet to "USB Storage" and "Host"...Then I download and run Super One Click.
Ok, I run the "Super One Click v.2.3.3"; by clicking the root button and then all I get is a frozen screen that reads:
Code:
Killing ADB Server.... Kill Server 0.11s
Starting ADB Server.... StartServer 4.09s * daemon not running. starting it now on port 5037* *daemon started successfully*
And then it just freezes the program. So, now I'm completely stuck. I mean I learned a great deal, that I can hook up a keyboard, mouse, etc to this thing, but, obviously Super One Click was not designed for these generic tablets. I have read other articles which have suggested that the .inf driver for the default "Android USB Drivers" needs to be edited for your specific tablet model and you must enter the specific CODE# for it to recognize for rooting with Super One Click... But, god forbid, I haven't found any useful information on where that might be. Also, someone suggested to install the Android SDK and edit those files along with the .inf files to make this work. But, that didn't work either. I did everything right. I turned off USB debugging and then I would wait for super one click to come up with waiting for device...but that never happened. I even tried it with USB debugging on... still nothing.
Has anyone created a generic batch program to root these types of devices? What am I doing wrong here?
Since every tablet is different with different boot mangment. Makes it hard to make a generic root kit.. and being a frys computer salesman I try very hard to talk people out of those things unless. They swear they are only us8ing it for facebook
Sent from my SPH-D700 using xda premium
Rooting Idea USA Tablet
Well, this took me all night to read and learn about how to root this basic tablet from Fry's.
First off, I tried many different things and it just didn't work. Using super one click is definitely out of the question for this particular tablet.
I read all night and thankfully found the forum article on how to solve this issue on xdadevelopers own forum.
As per quoted quotes below:
.....You can use gingerbreak to root this. Run it once and let it reboot, then use supermanager free from market to rename the su symlink from /bin/ to "old" or something, and reboot again.
You should now have root ........ It might take a couple of trys but it works.
You need to download supermanager from the market. Enable root in supermanager settings and click yes when superuser pops up.
Then use the file explorer within supermanager to navigate to the /bin/ directory and you will find a sysmlink called su
You need to rename this su symlink to old - completely take out the name su.
Just to be safe run gingerbreak again and then you can install busybox from market.
pablo11
Click to expand...
Click to collapse
Thank you so much Pablo11. The idea is to download the APK for GingerBreak from online onto your IDEA USA tablet directly. The trick here is that the brand name is IDEA "USA", but the real workings behind the "MID" is "ViMicro". You will notice that displayed as you turn on your tablet. So, in order to find real information about your MID device, you have to search articles for vimicro.
Once you run gingerbreak, your tablet will go completely nuts. Nothing will run right. Things will break and it will be a complete mess. It will however, install superuser apk. However, it will not work. You can download the Root Checker from the market and you will notice it is NOT rooted. So...thanks to pablo11, you will want to download supermanager from the google play market. Install it.
Next go into the supermanager settings and click on ROOT. Make sure root is enabled and checked marked in the settings. When you enable root in the settings, it will prompt you with "allow root?" Click on Yes. This will give you the access you need.
But, your not done, once again as per Pablo11, go to the super managers file manager section. Get to the root directory by clicking up, and then find the folder "bin". Look for the file "SU" and rename this to "old".
Now, you will be able install busybox and any thing else thats root.
By the way, restart your tablet again, and I "personally" recommend that you go into your settings> Privacy> Check mark both (Backup my data and Automatic Restore) and then click on Factory data reset. Start the tablet from like it was brand new. Don't worry it will keep the root that you did intact. You will just have to re-register the tablet with your existing gmail that you originally used with that tablet.
Lastly, use the root checker from the market and you will see that it is successfully rooted.
Okay... Now, my next step. To crack open this tablet and put in a bigger SD Card as the 2G SDCARD is way too small, especially if you want to use new roms and install a linux operating system onto it....
@njbsuperman story telling of Pablo11's method worked for me. I have a generic android 2.2 7 in. "MID" white box, picture of the tablet on each side all of that and it worked for me. Had to restart and run ginger break a couple times but I followed the directions and it worked.
Thanks for posting this, got this for my 6 yr old for his b-day and of course I gotta ****in tim allen it and I happened to stumble across your findings and your post you put up 2 days before the unwrap. Thanks...smoke blunts.
Using Unlock Root to Root IDeaUSA Tablet
I know that this thread is a few months old, but I thought that I'd share what I used to root my 7" IDeaUSA YG A777 Android Tablet. I used Unlock Root. It's a simple program that rooted my tablet in minutes with one click. This site won't let me insert links in posts (I'm new to this site), but you can find the program by typing "Unlock Root" into Google. It should be the first site that comes up.
Same here
Yes i used unlock root also and it worked for me/....
Rooting IdeaUSA CT-702
kokomelala said:
Yes i used unlock root also and it worked for me/....
Click to expand...
Click to collapse
I have the CT-702 with Android 4.0.3 and can't get past the USB connecting to the storage devices. I can manipulate the files on the internal and external cards but any attempts to use the unlockroot package (from unlockroot.com which is full of adware) or other packages (z4root, ICS Root Unlocker 1.0) do not detect the device. There is a payware unlockroot package at unlockroot.org. Is this the package that works? Is there a no computer apk like gingerbreak (which fails) available or a procedure to get past the USB business.
is there a way to root the idea USA ct-705
I've recently purchased the CT-705 and been trying to find any information on rooting this device but all if have found are other people with the same problem can anyone help
specs
Model:
CT705
Android version:
4.1.1
Kernel version:
3.0.8+
[email protected] #877
SMP PREEMPT Fri Jan 11 10:12:03 CST 2013
Firmware version:
([email protected])_([email protected])_N2.59_V411.01_TL12
Build number:
RK30_ANDROID4.1.1-SDK-V1.00.00
rk30sdk-eng4.1.1 JRO03H 20130111.093246 release-keys
any and all info is appreciated thanks
Another CT-705
@captinmudslide,
I'm in the same boat as you, in fact we must have bought them about the same time. I'm hoping that you are following this thread, and that you found something that works to root this beast. I 've been digging and trying any and everything I can find that works on other android devices. I was hoping that holding the power button and vol+ or vol- would get me somewhere. Vol+ at least gives me the dead robot, but can't do anything with it. Was hoping that if the adb server was running it would connect. Nope.
Anybody monitoring this thread, feel free to offer something that hasn't already been covered previously.
Thanks.
njbsuperman said:
The idea is to download the APK for GingerBreak from online onto your IDEA USA tablet directly. The trick here is that the brand name is IDEA "USA", but the real workings behind the "MID" is "ViMicro". You will notice that displayed as you turn on your tablet. So, in order to find real information about your MID device, you have to search articles for vimicro.
Once you run gingerbreak, your tablet will go completely nuts.
Click to expand...
Click to collapse
Holy crap, I rooted the device.
If anyone needs this later, here's what I did:
Fist I pulled down SRS Root, Unlock Root, Gingerbreak and the generic Google USB drivers.
I went into the properties of the missing driver CT1006 and checked the hardware ID. I opened android_winusb.inf and added the lines:
;ProScan plt-7035
%SingleAdbInterface% = USB_Install, USB\VID_2207&PID_0010
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0010&REV_0222&MI_01
under the headings of [Google.NTx86] and [Google.NTamd64].
I ran Gingerbreak a few times, per a thread I read, but the app would hang. I tried it 3 times.
Then, I went back to Device Manager and selected "Update Driver" and pointed to the .inf I edited earlier. I detached and reattached the device via USB to my PC and ran SRS Root, which still reported an error. Then I ran Unlock Root and the first time it said my device was already rooted, but I told it to root again. It did and my device rooted. I then looked in my apps and found SuperSU installed and was able to run Sixaxis Controller, which requires root to run, which confirmed root worked.
I don't know which step actually solved the issue, but hopefully if anyone has this issue in the future, they can figure that part out.
iDeaUSA CT705 (RK3066) Rooted
... CT-705 ... [email protected])_([email protected])_N2.59_V411.01_TL12 ...
RK30_ANDROID4.1.1-SDK-V1.00.00 rk30sdk-eng4.1.1 JRO03H 20130111.093246 release-keys...
any and all info is appreciated thanks
Click to expand...
Click to collapse
I've been able to root this tablet using Kingo ROOT, with the "latest_usb_driver" from Google (1/27/2014).
I have set:
c:\users\{USERNAME}\.android\adb_usb.ini
with the value: 0x2207
And have used the RK_DriverAssitant available online
It takes a lllllllloooooooooonnnnnnnnggggggg time for my Windows 8.1 x64 to recognize it, but eventually it will show with:
c:\adt\sdk\platform-tools>adb devices
List of devices attached
0123456789ABCDEF device
Then run Kingo ROOT.
C.U.tech
You can root with:
POOT: This app is a one click root app. No computer needed
Framaroot: Framaroot is a oneclick root app . No computer needed
This is the most popular one!
Z4Root: Z4Root is an oneclick root app . No computer needed
Towelroot: Towelroot is an oneclick root app. No computer needed
Baidu: No information
Vroot: No information
Gingerbreak: This app can root almost all gingerbread devices
Downloads:
Poot - Download the app >>here<<
Framaroot - Download the app inside this XDA Thread - >> CLICK HERE <<
Z4ROOT - Download the app inside this XDA Thread - >> CLICK HERE <<
Towelroot - Download the app inside this XDA Thread - >> CLICK HERE <<
Baidu ROOT - Download the app >> HERE <<
vROOT - Download the app >> HERE <<
Gingerbreak - Download the app inside this XDA Thread - >> CLICK HERE <<
Flash a SU ZIP - Download the ZIP >> HERE << and flash it on your unlocked bootloader phone !
Hit thanks if you liked this post or this post has helped you out !

[Q] wpa_supplicant "not found" or running as wifi, not system

I've been working on this for days and I'm on the verge of giving up and send my android tablet back to the retailer but, on the off chance that someone can help, I thought I'd post a plea for help.
I have been playing with my mother's birthday gift, an android tablet, in an attempt to put a bird watching app on it. I'm not used to this OS, so it took me a few days to get the hang of it, and then the wifi stopped working.
From a user perspective, you turn on the wifi and, after 20 seconds, it turns itself off and the tick disappears.
I decided to look a little further into the problem, as I didn't believe it was the hardware so soon, and used LauncherPro and SuperOneClick to root the tablet and ddms to see what was going on.
Anyway, I think I have tracked the issue to the wpa_supplicant file. I can load up the wifi interface from the command line:
insmod /system/lib/modules/8192cu.ko
busybox ifconfig wlan0 up
But when I ran the original wpa_supplicant in /system/bin/ it simply said "not found"
The file was there - I could copy it onto a usb stick and open it in a hex editor on my PC, but whatever I did, it would say "not found" if I tried to use it (chmod 777 as well).
When I got no joy from that, I started to look for alternative wpa_supplicants (there was no sign of a direct replacement for my disgo8100 2.3.3 version) and found the ad-hoc enabled ones.
I have tried a selection, but the one that comes closest to working (I mounted the system rw and replaced the original before mounting it ro again) insists on running as "wifi" (or 1010) when the original ran as "system" (or 1000).
This seems to mean that, although the supplicant runs happily, it doesn't create the /data/system/wpa_supplicant/wlan0 file in a form that other programs can access (wrong group/permissions, I think).
So, this has become very frustrating (but I've learned a lot about android, and how it differs from linux).
Can anyone provide an explanation for why the original file says "not found"? Could it be corrupt? If so, could someone provide a replacement from the disgo 8100? Could it be relying on a library that's not there?
What about the ad-hoc version I have? Can I force it to run as system.system instead of wifi? Am I wasting my time and should try to get disgo to provide a whole replacement rom (they have an update apk, but I believe you need to connect to the Internet to do an OTA update, which I can't).
As I said, I'm ready to send this tablet back, but I hate to admit defeat!! Any help would be gratefully received.
Cheers.
Never mind. Made some progress with the ad-hoc supplicant in this thread:
http://www.freaktab.com/showthread....pa_supplicant-file&p=3600&viewfull=1#post3600
Disgo 8100 Rooting
On the basis that there doesn't seem to be much information about the Disgo 8100, I thought I would post my findings.
I initially tried z4root, universalandroot and gingerbreak, but none of these worked. However, I didn't understand that I needed (or how) to enable USB debugging.
Once I did, I installed LauncherPro-0.8.6.apk and configured a shortcut to the development tab, which let me enable the USB debugging option.
I then downloaded android-sdk_r18-windows and modified the android_winusb.inf file by inserting the following at the end of the [Google.NTx86] and [Google.NTamd64] sections:
;Disgo8100
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_1F00
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_1F00&MI_00
When I plugged in the Disgo 8100, windows XP asked for drivers and I pointed it to the edited .inf file so that they could be installed and the disgo was recognised.
I then used SuperOneClickv2.3.3-ShortFuse on the PC to root the tablet - it all worked perfectly and reported success.
Installing term.apk got me a terminal emulator and I could su into root. Hopefully you can get yours rooted, too.
Disgo 8100 Android Market/Vending/Google Play
Whilst I managed to root the tablet, I couldn't get any form of the vending system to work.
I got the play dot google dot com site to recognise my tablet as a T-Mobile Samsung Nexus S using the information in this thread:
http://www.techknow.t0xic.nl/forum/index.php?topic=770.0
But market 2.3.6, 3.4.4 and the latest Google Play all fail with various errors (although I noticed that play only [email protected] out when the wireless is enabled - the others may do the same).
I have taken a log capture of google play failing using ddms and will look through it.
By the way, grabbing the hwver for this tablet gives:
console=ttySAC3,115200 androidboot.mode=normal mem=512M hwver=81.1.0.0 mtdparts=imapx200:[email protected](ramdisk),[email protected](kernel),[email protected](resv),[email protected](system),[email protected](userdata),[email protected](cache),[email protected](Local-disk),[email protected](panic) androidboot.mode=normal
Google Play working on Disgo 8100
Drawing this one to a close, in case anyone is interested:
I have Google Play installed and working. I downloaded com.android.vending-3.5.15.apk from the link in this thread:
http://www.theandroidsoul.com/download-google-play-store-apk-3-5-15/
I renamed it "Vending.apk" (the capitalisation may be important, not sure), mounted /system as rw (mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system) and copied it into /system/app. I changed permissions to "666".
I cleared the data/cache from the YouTube application and deleted YouTube.apk from /system/app (because it kept locking up) and replaced it with signedy244.apk (renamed as YouTube.apk) from http://forum.xda-developers.com/showthread.php?t=1529715 (the WifiHD version).
Rebooting the tablet, I connected to the WiFi and ran YouTube (in order to confirm my gmail account), which worked fine, and then Google Play, which (to my amazement) worked fine too.
Hope yours does too
Excellent thread! Wish I could thank you but I don't seem to have a Thanks button. Anyway, do you mind if I ask a couple of questions re. rooting the 8100:
1) Was your tablet running Android 2.3.3, kernel 2.6.35.7, build number GRI40?
2) Could you explain in a bit more detail what you did when you "configured a shortcut to the development tab"?
a3d35232 said:
Excellent thread! Wish I could thank you but I don't seem to have a Thanks button. Anyway, do you mind if I ask a couple of questions re. rooting the 8100:
Click to expand...
Click to collapse
Glad you like it.
a3d35232 said:
1) Was your tablet running Android 2.3.3, kernel 2.6.35.7, build number GRI40?
Click to expand...
Click to collapse
Yes.
a3d35232 said:
2) Could you explain in a bit more detail what you did when you "configured a shortcut to the development tab"?
Click to expand...
Click to collapse
a. Install launcherpro
b. Press home in the top left corner
c. Choose launcherpro
d. Press and hold a blank part of the screen
e. Choose shortcuts
f. Choose activities
g. Choose settings (scroll down to it)
h. Choose development (scroll down - not in alphabetical order)
i. Press ok
You should now have a desktop icon that lets you turn on USB debugging.
Enjoy
Thanks. Everything worked as you describe except the signedy244 version of YouTube. Whenever I launch it I get an error message "There was a problem with the network [400]". Searching on the net, it seems a lot of people are seeing this error and there may have been an update to the app which isn't in the signedy version. Are you still able to run it?
a3d35232 said:
Thanks.
Click to expand...
Click to collapse
No problem.
a3d35232 said:
Everything worked as you describe except the signedy244 version of YouTube. Are you still able to run it?
Click to expand...
Click to collapse
Yep, didn't have an issue - dropped it into the app folder, chmod and rebooted; worked first time and tested it a few times. The file I downloaded was 2,554,313 bytes, in case you want to check.
FYI, the issue I was having with the YouTube app was that it was making requests to the server with "restriction=ZH" in the uri. The server was replying with a HTML 400 error (bad request) because ZH is a language code, not a country code. Anyway, I've patched the app further to remove the restriction parameter from the request. I've posted details in the YouTubeHD thread (about half-way down page 36) if you're interested.
Any chance of telling a idiot how to get google play on the Disgo 8100?
My dad got given one at work but the app store sucks and I'm a little confused by the above
Many thanks

[Q] Azpen A701 Tablet

Does anyone have any information on rooting the AZPEN A701 Tablet (ICS OS)?
All my searches keep popping up for the Acer Iconia A701.
drivers
I found the correct address for the drivers for this tablet, and 2 others from Azpen.
www.mediafire.com/azpensupport
The links on their webpage incorrectly spell mediafire and also include .com in the last part of the link.
Note: I recently got an email from Azpen telling me the exact same url that I had already figured out. Their email is about week to a week and a half after I sent them a request for the proper address. Also, as of the time I am posting this update, they have not corrected the address on their website.
Tried methods
I have tried SuperOneClick which reports that the system is rooted, but ADB Wireless says it is not.
I have tried Bin4ry's Root Many Android! (options 1, 3, and G) and briefly got temp root on option 3 but I lose wireless functionality (I get one or the other message from ADB Wireless (no root or no wireless), verified that Wireless connection has been turned off and won't turn back on until reboot which loses me the root again).
Retries
Ok, finally rooted the Azpen A701.
What I did:
First, I went back to SuperOneClick, and choose Unroot to reverse anything it did.
Retried Bin4ry's Root Many Android! v31, option 1 (new standard method), test, failed, unroot, 3 (old method), test, failed, unroot, then G (Google Glass method), test, WORKED this time.
Verified by using a root browser (can see files/folders(subdirectories) in /data after giving permission), a root checker (note: do not turn on SuperUser's Autoanswer, gives false information from some checkers), and ADB Wireless works while in range of a wireless router/source.
I am guessing that somehow the leftovers from SuperOneClick were affecting my results with Bin4ry's collected scripts.
Props to all that developed each of those programs and scripts.
I don't know if anyone will be seeing this but I hope it helps anyone needing the info.
Just curious to know if there is a rom available in case this method bricks the tablet? I bought this tablet a couple of weeks ago because I wanted to mess with one and I didn't have a lot of cash to spend. I use it daily and my kids play games on it. I can't afford to get another anytime soon, however I'd like to have it rooted so that I can remove factory installed apps that I don't want or need.
no idea
BizarreMan said:
Just curious to know if there is a rom available in case this method bricks the tablet? I bought this tablet a couple of weeks ago because I wanted to mess with one and I didn't have a lot of cash to spend. I use it daily and my kids play games on it. I can't afford to get another anytime soon, however I'd like to have it rooted so that I can remove factory installed apps that I don't want or need.
Click to expand...
Click to collapse
I have absolutely no idea. The only additional rom I have seen ANYWHERE is the Jellybean update for it (see driver link above). This seems to not be a very popular tablet to work with, going by the fact I received no help from anyone here. All research on this so far has been done by me. I stumbled on to Bin4ry's rooting method by accident. I'm not a ROMer, I don't know how to build one. Also I don't know which ROM backup method to use on it/will work with it.
Alright
I'll give it a shot during the weekend, I've grabbed the jelly bean update (thanks for the link). Hopefully all goes well. I figured there would be little to no support for this device, however due to a tight budget I chose to get this tablet.
I don't really mind the lack of support, however I'd like to have root because like on my old phone I had a few programs I used that required root.
Thanks again.
*Edit*
I attempted last night as I had free time to do the root method and unfortunately it did not work on my device. Not sure why it did not work. I'll try it again at a later time when I can. I also attempted to upgrade to 4.2 but it seems as though I am having issues with it as well.
Maybe I'm just stuck with the tablet as is
trying again...
BizarreMan said:
I'll give it a shot during the weekend, I've grabbed the jelly bean update (thanks for the link). Hopefully all goes well. I figured there would be little to no support for this device, however due to a tight budget I chose to get this tablet.
I don't really mind the lack of support, however I'd like to have root because like on my old phone I had a few programs I used that required root.
Thanks again.
*Edit*
I attempted last night as I had free time to do the root method and unfortunately it did not work on my device. Not sure why it did not work. I'll try it again at a later time when I can. I also attempted to upgrade to 4.2 but it seems as though I am having issues with it as well.
Maybe I'm just stuck with the tablet as is
Click to expand...
Click to collapse
It may have been the sequence I used. Tried SuperOneClick several times (as above it said tablet was rooted but several apps said it wasn't) which installed su, busybox, and superuser. Then found Bin4ry's method, got temp root (tryied 1, 3, and Glass). Then went back to SuperOneClick and unrooted, returned to Bin4ry's and finally got it with Glass method.
Don't know if that helps
Well
After several attempts via Bin4ry and SuperOneClick I have obtained root on this tablet.
Not quite sure which actually did it though as with super one click it froze on me during both times I used it and each time I tried Bin4ry's method I kept getting messages about connecting my device (which was connected fro the get go).
After several tries with these programs yesterday and finally saying screw it I decided to add some apps that required root. I don't know why I did it I just figured it was worth a shot. I added Super User which told me I was rooted, then I added Titanium Backup and was able to use it as it is intended. For added measure I also installed and ran root checker which as well as super user verified that the tablet had been rooted.
Good to see that your were able to root.
BizarreMan said:
After several attempts via Bin4ry and SuperOneClick I have obtained root on this tablet.
Not quite sure which actually did it though as with super one click it froze on me during both times I used it and each time I tried Bin4ry's method I kept getting messages about connecting my device (which was connected fro the get go).
After several tries with these programs yesterday and finally saying screw it I decided to add some apps that required root. I don't know why I did it I just figured it was worth a shot. I added Super User which told me I was rooted, then I added Titanium Backup and was able to use it as it is intended. For added measure I also installed and ran root checker which as well as super user verified that the tablet had been rooted.
Click to expand...
Click to collapse
So I think we can safely say that using both methods together + patience will root this tablet (don't know why one or the other wouldn't do it).
Not having any luck
CyberSpiderPrime said:
Does anyone have any information on rooting the AZPEN A701 Tablet (ICS OS)?
All my searches keep popping up for the Acer Iconia A701.
Click to expand...
Click to collapse
I have been trying to root AZPEN A701 for the past week, I have tried everything written on this forum. Any help PLEASE!
clean slate
Are you willing to do a full restart on the tablet (factory reset)? I had to do that before my root took, as I found on other systems that I have rooted some programs you load can interfer with rooting. Save any personal data before you do this, programs can be reinstalled from Google Play or (hopefully you saved them if you downloaded them) your computer
Factory reset:
Press and hold up volume button then press and hold power button. The screen will remain black (no backlight)
Wait 4 seconds then release both buttons (backlight will come on). Shortly the android on it's back with the open torso (the sick android) will be displayed.
Press the down volume button. You should see 5 options available- You are now in the System Recovery program.
Using the up or down volume button to highlight an option then press power to select the option.
1) select Wipe Cache Partition
let the unit reboot, then turn it completely off
reenter System Recovery again.
2) select Wipe data/factory reset
let the unit reboot, then turn it completely off
The system is as clean as it is going to get now.
On your pc (don't know for MAC's) download the drivers, Android programs needed (Android Debug Bridge -ADB- is part of the Android Development kit and some Java Development Kits), and both SuperOneClick and Bin4ry's root software. Install all software and drivers as per their instructions. Run SuperOneClick and Bin4ry's root programs. Busybox and SuperUser will be added automatically by these root programs.
While having wifi and internet access (McDonalds anyone?), re-sign up for Google Play (sorry, but the settings got wiped earler). Go to Google Play and let all the programs update. Update Busybox and SuperUser if needed/possible.
Download any root enabled file system browser (FSB) (permission will have to be granted in program to use root functions) - I used Ghost Commander for mine. It may take a bit to find it in the directory structure for the FSB you downloaded but you need to get to the root system folder.
Ghost Commander has a Local Storage option press it and an new list of folders/files will be displayed, move to the previous folder level (double dots at the top) and give permission to move to a system folder, move to the previous folder again to get to root directory, "/mnt" is the directory you just came out of and is highlighted but you will be at the root of the file system.
Enter the "/data" directory. If you can see files listed there, you have root; if not rooting attempt failed.
Once rooted, doing a system cleaning and Factory reset will not remove root but will remove SuperUser and Busybox (re-run one of the root programs to re-install then update the next time you are on the internet/web). Updating/upgrading the rom will remove root if the rom does not have root activated - I don't know of any custom roms for this tablet (there is a Jellybean upgrade in the Azpen website, if they haven't updated to the correct web address then use the one I listed on the front page, mediafire is spelled wrong in the address). Nandroid level system backup is not available yet for this tablet to my knowledge.
For several reasons, do not turn on SuperUser's automatically give permission option (the one that affects all programs), except on a one for one basis: 1) some root testing programs will fail if this option is turned on, 2) security: turning this on will allow ALL programs - including some malicious ones - to have super-user rights, 3) you will get to know which programs are asking for root permissions beforehand not after, you may want some to have automatic access (like DroidWall in my case, a firewall) and not others.
Also other information that can be useful:
/sdcard does not refer to the removeable SDCard but to the internal user data area. All programs that can be moved to a SDCard (like by Apps2SD) will be moved to this directory by default (some may allow re-assignment of the destination location) instead of the removeable SDCard (blame Azpen, it was their decision to use the directory and name that way). On most other systems /sdcard is the removeable SDCard.
/extsd is the removeable SDCard, when installed, maximum size is 32Gb.
/usbhost1 is for any usb flashdrive connected by a USB-OTG cable (OTG means On-The-Go, special usb cable that puts the tablet into host mode, similar to connecting a flashdrive to a computer, the cable is not a standard Data Connect/transfer cable, one USB-OTG comes with this tablet). Note about USB-OTG cables: if one is connected you can connect either a flashdrive, usb keyboard, usb mouse, combo keyboard/mouse unit, or a powered usb 2.0 hub. Only one flashdrive can be connected at a time (anyone know of downloadable software that would allow 2 or more? I know some modified kernels can allow more than one) so with a hub you can connect a flashdrive + keyboard + mouse (I use the RII wireless combo keyboard and mouse with mine). Maximum size appears to be 8GB, format must be FAT32; will be testing with a 16GB key shortly.
Azpen A701 and Jelly Bean
Shortly after I wrote the above I had to re-flash my tablet, but Azpen had deleted the ICS image (after a request it was restored to the site, get it while you can) and had to flash Jelly Bean. I found there were troubles with this image.
First: I could not write to either the external SDCard (called extsd) nor an attached USB flash key; reading was unaffected. I found this out when I attempted to reassign my backup location to the external sdcard and it was unable to create the directories.
Second: I couldn't find a rooting program.
After a little research, I found that the external media had not been given R/W permission in the platform.xml file - I could actually navigate the FS and read the file even without root.
Also I finally found after 2 days of searching a root program, VROOT, http://forum.xda-developers.com/showthread.php?t=2434453, that would work. Be prepared to deal with Chinese for a little bit and follow the instructions on that page (press the buttons to see screenshots). The superuser app needed to fix/replace the Chinese app is SuperSU (Google Play) which supposedly fixes problems found with other superuser apps. Once you have downloaded SuperSU, had it download/update its binaries and have rebooted, you will have to disable the Chinese Superuser app as you are unable to uninstall it using the app manager: I located it by its icon (shield with cog) in /system/app and appened '.old' to the name: "Superuser.apk" => "Superuser.apk.old'. I didn't use Titanium Backup as suggested because I am not a fan of the program .
platform.xml is located in /system/ext/permissions. After you have root, open platform.xml in what ever text processor you want locally or transfer it to your computer and work with it. You will have to add '<group gid="media_rw">' to the 'WRITE_EXTERNAL_STORAGE' group, on the line after '<group gid="sdcard_rw">' (don't type the single quotes but the double quotes are needed) and write the file back to its location (need root for that, adb pull/push may be possible to fix this). Remember on this tablet, sdcard refers to the internal user storage, media_rw will give permissions to the extsd (external sdcard) and USBHost1 (using included USB-OTG cable and a flash drive). I rebooted the tablet and tested the RW state of extsd, and voila, it now is write capable.
I wish there was more aid on this tablet but since it is not mainstream (not made by a big manufacturer like LG, Motorola, Samsung, etc.) I doubt that it is coming (I am not a ROMmer but have been using computers since the 80's, so I know a few tricks and am always learning). I will keep adding info as I find or fix it.
I will probably go back to ICS as some of my programs are not working right, and JB is sluggish.
I just picked up the A700 from Microcenter, and this is the ONLY reference to rooting the device I could find. The Azpen website doesn't even acknowledge the device's existence. I just came across this yesterday: Azpen A700 - Cyanogenmod forums. I used the Kingo method without a hitch.
Hopefully, all the other folks who get that tablet for the pre-Black Friday sale who found this link will benefit.
johncro13 said:
I just picked up the A700 from Microcenter, and this is the ONLY reference to rooting the device I could find. The Azpen website doesn't even acknowledge the device's existence. I just came across this yesterday: Azpen A700 - Cyanogenmod forums. I used the Kingo method without a hitch.
Hopefully, all the other folks who get that tablet for the pre-Black Friday sale who found this link will benefit.
Click to expand...
Click to collapse
I picked up this tablet also. Not bad for $40. I used this method to root http://www.cydiaimpactor.com/ It worked the first time. I just had to do it on an old XP machine. Windows 8 would not load the right android drivers. Now I'm working on getting Titanium backup to see my external SD card.
comstar said:
I picked up this tablet also. Not bad for $40. I used this method to root http://www.cydiaimpactor.com/ It worked the first time. I just had to do it on an old XP machine. Windows 8 would not load the right android drivers. Now I'm working on getting Titanium backup to see my external SD card.
Click to expand...
Click to collapse
I was going to return it as no rooting procedure would work....(I only bought it so I could have a android tab to fool with...i'm windows tablet all the way)...and once I tried out that rooter it worked...thanks alot for the info!
cheeb said:
I was going to return it as no rooting procedure would work....(I only bought it so I could have a android tab to fool with...i'm windows tablet all the way)...and once I tried out that rooter it worked...thanks alot for the info!
Click to expand...
Click to collapse
Glad it worked for you! I started this thread for the A700 http://forum.xda-developers.com/showthread.php?t=2532464 - No activity in it yet. But if you come across anything good post it over there.
Sent from my Transformer TF101 using XDA Premium HD app
Update
I am glad to see that others are taking an interest in this tablet.
I found 2 methods that worked and am glad that others are finding more.
Now if I can get the boot loader cracked I could finally make a nandroid copy and save myself 4+ hours restoring everything when it goes wonky. This has happened twice- OS partition fills up (and don't know why) and the device resets to near factory reset level (even some of the factory apps are missing) and won't install anything but the smallest of apps which are deleted on the next reboot; the only solution is to re-flash the tablet. Note that I have gone back to using ICS as JB has other problems (external media including its own sdcard partition is not rw enabled for one).

[Q] Issue with installing an app

Hi everyone,
I'm new on xda and I come here because I struggle to install this app on my rooted Galaxy S4 with CyanogenMod 11: "Paiement mobile (pour Orange)" (sorry, I'm new, so I cannot post urls).
In fact, this app has not been declared by the devs (on the Google Play) to be compatible with my phone, despite the fact that I have the specs to run it (NFC payment).
I asked a friend who was able to download the app to upload it on Aptoide, giving me the opportunity to download the apk on my phone (this apk is available in this thread). I tried to install it, but I get the following the error: "app not installed".
I would like to force the installation of the app. I tried many ways, like using apps that use root access on the phone, without success (for example, I tried with "System Apps Installer" on the Google Play, but I get a problem with mounting /system). I also tried to install it with the command line tool, but I get the error "[install_failed_invalid_uri]". I tried to change the permission of the /data/local directory and /data/local/tmp with ES file explorer, but it did not change anything.
In addition to this, I'm not able to enable usb debugging in the developper options (to install the apk with adb), because every time I activate the option, it becomes disabled in the following seconds.
It seems to be a little bit complicated, because I seem to have different problems, but I hope that someone here will be able to help me !
Thanks for your help,
Aquignis.
The issue is most likely Cm. They alter things so some that normally work no longer work
I suceeded to solve the "[install_failed_invalid_uri]" error in the command line tool by also changing the permissions of /data.
After that, I got another error (yes, one more, but the last) that made me discovering what's the real problem in this situation: "install_failed_missing_shared_library". By doing some researches on the web and exploring the apk, I understood that the app use a library called "org.simalliance.openmobileapi" that corresponds to the work of SIMalliance, who developped an API called "Open Mobile API", which notably enables communication with NFC sim cards and must be integrated to the build of the ROM. This system is used by many banks in Europe and has been integrated in the stock ROM of many NFC devices by the important manufacturers, but not by Cyanogenmod devs in the last stable release of CM 11 for the Galaxy S4.
Like you said it, the problem was CM
I asked them if it has been integrated in CM 12, because that is why the app is said to be incompatible with my device by Google Play which automatically checks which libraries are installed on your device (I'm waiting for their answer). The other solution would be to add the library to the CM build by myself, because it seems not to be very complicated, but I'm not qualified enough to do this !
If it is not part of aosp I wouldn't count on it being added to be honest. Not to mention most banking apps refuse to work if the Rom has root as it can cause security issues.
Yes, the root seems to be a problem with some apps according to the work of this man.
On the other hand, I think that this API is important enough to make CM devs pay attention to it, because it is used in many countries (except the USA which use only HCE, I believe). If only I was able to build it myself !

Categories

Resources