Related
Has anyone, (thinking others who've been shutdown by AT&T), tried tethering their Streak to a phone using PdaNet, or something similar?
A friend tried with his Streak and BB (using PdaNet), but didn't have much success.
Thanks,
AG
gersztoff said:
Has anyone, (thinking others who've been shutdown by AT&T), tried tethering their Streak to a phone using PdaNet, or something similar?
A friend tried with his Streak and BB (using PdaNet), but didn't have much success.
Thanks,
AG
Click to expand...
Click to collapse
i use barnacle to connect with ipad.root necessary.
i have a US streak and im having issues getting it to tether to my HTC Aria (using wireless tether). Ive tried the original rom, the O2 1.6 and 2.1 rom. But still no luck, my laptop, and 2 friends ipods will connect through the aria, but the streak doesnt even see it.. So not sure whats going on!
I have a Sprint EVO 4G that can serve as a hot spot but haven't tried it with my Streak yet. But I plan to. I bought the Streak without activating the AT&T part. Don't need two cell phones.
Thanks all.. I know the Archos 5 (which I believe also runs 1.6) advertises the cell phone tethering capability. Anyone know what software it uses? I don't know much about that specific sofwtare, but will start researching...
Yeah Barnacle works.
gersztoff said:
Thanks all.. I know the Archos 5 (which I believe also runs 1.6) advertises the cell phone tethering capability. Anyone know what software it uses? I don't know much about that specific sofwtare, but will start researching...
Click to expand...
Click to collapse
the archos 5 will not tether if u are using adhoc. found out the hard way... (long time ago before the streak came out i thought i could use that and tether with my iphone and it didint work.. apparantally it doensnt support adhoc wifi. but bluetooth tethering worked fine on the archos 5
Maybe someone can get this to work?
Tried to connect to to my WM Omnia via WMWiFiRouter- No Dice.
tried using wpa_supplicant file attched below- i can see and connect to ad hoc network(s), but can not establish IP --> copied to /system/bin
the apk and files below look more promising but perhaps need editing by someone who actually knows what they are doing. the app installs and runs but there is a location mismatch.
then ran across this info here: http://www.slatedroid.com/pandigital-novel-android-tablet-discussion/4505-i-have-infrastructure-adhoc-working-same-time-do-you-want-look-here.html
"Okay, I'm not taking 100% credit for this because all I did was modify the work that this user did:
'Originally Posted by YasinSiddiqui
NOTE: I'm using Rogerbraun Custom ROM 5.1 on Rockchip APAD, but I don't see any reason why this shouldn't work on the PDN too.
Hi Guys,
Finally figured this out.
Since the wpa_supplicant.conf file is read-only, an Android app can't modify the file. Hence, we were having to go back to connecting the APAD to the PC and use DroidExplorer to overwrite the wpa_supplicant file everytime we wanted to enable Adhoc Wifi.
I realized that when you upload a file to the APAD using DroidExplorer, it gets write permissions
And once you have the file with write permissions, an app CAN modify the file.
So, I've created a small app for easy switching between Normal and Ad-hoc wifi modes.
Here are the steps:
1. Step removed because the files were replaced (see below!)
2. Use DroidEXplorer to copy the 3 files: wpa_supplicant.conf, wpa_supplicant.conf.adhoc and wpa_supplicant.conf.normal to /data/misc/wifi folder
3. Install AdhocAble.apk using any File Manager or even DroidExplorer
Now, start up adhoc wifi tethering on your phone (Barnacle Wifi Legacy on Android, JoikuSpot on Symbian, WMWifirouter on Windows Mobile, MyWi on IPhone etc.) and set the adhoc SSID to: adhocable with NO password.
Remember that you have to Turn wifi off and on everytime you switch modes.
For experts: How the app buttons work:
1. Switch to Ad-hoc Wifi Mode: Overwrite wpa_supplicant.conf with wpa_supplicant.conf.adhoc
So if you want to change the adhoc SSID or give it a password, edit the wpa_supplicant.conf.adhoc before copying it via Droidexplorer
2. Switch to Normal Wifi Mode: Overwrite wpa_supplicant.conf with wpa_supplicant.conf.normal
3. Backup Normal Settings: Overwrite wpa_supplicant.conf.normal with wpa_supplicant.conf
This allows you to avoid having to type the normal wifi passwords every time. But, remember not to use this button when you are in ad-hoc mode, otherwise you'll lose all your saved wifi passwords.
4. Do let us know: opens up an email compose window so that you can tell me whether you like the app or not. Do write your name, country and details of which devices and ROMs you have.
My modifications to these instructions are as follows:
Instead of the supplicant files supplied by the user above use mine
Also feel free to open "wpa_supplicant.conf.adhoc" and change the SSID to whatever you want, i.e. I called mine "AndroidTether"
Also I didn't bother with any security because I'm just using the access control feature on my tethering program, I'm not sure if they all have this feature but basically, my phone tells me when someone is trying to connect and asks if I want to allow the connection before the device is assigned an IP.
1. download: "wpa_supplicant_files_WORKING.zip and unzip
1.1 Open "wpa_supplicant.conf.adhoc" and edit SSID to whatever you want
2. place "wpa_supplicant.conf" , wpa_supplicant.conf.adhoc & wpa_supplicant.conf.normal into the sdk's "tool" folder (where adb.exe is)
3. download "AdhocAble_apk.zip" and unzip
4. Place "AdhocAble.apk" into the sdk's "tool" folder (where adb.exe is)
5. Open the command prompt and get to the folder where your adb.exe iscd c:/where_your_sdk_is/tools
6. enter: " adb push wpa_supplicant.conf /data/misc/wifi "
7. enter: " adb push wpa_supplicant.conf.adhoc /data/misc/wifi "
8. enter: enter: " adb push wpa_supplicant.conf.normal /data/misc/wifi "
9. check to see the files are there by entering " adb shell ls /data/misc/wifi "
10. install the apk, you can use my batch file to do this if you'd like here
11. unzip the file manager batch script and place it in the sdk's "tools" folder (where adb.exe is)
12. open the batch file (it should open a new cmd window)
13. select 2
14. select 1 (install an app)
15. it'll ask for the name of the apk. Enter " AdhocAble.apk " exactly, its case sensitive.
16. reboot the PDN
17. Start your cell phone tether and set the SSID to whatever you set in the .conf.adhoc file at the begining
18. Open up the AdhocAble app and select "backup your normal settings", this should save all of the remembered infrastructure network's SSIDs and passphrases
18.1 select Enable Adhoc, it will prompt you to make sure to turn your wifi connection off and back on.
19. Do so.
20. You should see your cell phone's SSID in the connection list (remember the SSID is hardcoded into the .conf.adhoc file so you have to set it to the same thing in the tether program or vice-versa.
21. If you don't see the tether connection enter it manually
To get back to infrastructure - simply open the app and select enable normal mode and turn the wifi off then back on again - after a short bit you should see the networks as usual. It might take a bit longer to obtain an IP, but it should work...if not reboot the PDN and try it again.
Another success - Flytouch2 / Eclair
What an adventure... I tried lots of different approaches to getting my 10" Flytouch2 running Eclair to my Moto Cliq the instructions in this thread formed a good basis for success. I had to make a few changes which I will describe.
First, I am using a rooted Moto Cliq (1.5 I think) running Barnacle to serve up Ad Hoc Wi-Fi. It worked great with my PC and iPad but I really wanted my Flytouch2 to have network access through the Cliq.
So far I have not yet been able to get the Flytouch2 to connect to my PC using ADB; this is a problem for another day. As such I was side loading until I realized that I could place APK's in Dropbox (great free app) and net-load?? them. I also had to get creative with Root Explorer and other file managers / editors to make the required changes
To accomplish this I did the following on my Flytouch2 (less the stuff that didn't work including a couple of bricking episodes)
- Rooted (permanent) painlessly using Z4Root
- Installed Root Explorer (essential for copying and renaming R/O system files)
- Installed TED to edit files
- Install ASTRO File Manager which is helpful for non root file manipulation activities
- Used Root Explorer to mark the /data/misc/wifi directory as R/W so files could be added/modified (the default is RO)
- Installed AdhocAble.apk which is nice but it turns out not really needed in my case
- Disabled Wi-Fi until done
- Installed the wpa_supplicant.conf.adhoc (after editing - attached and below)
- Renamed old wpa_supplicant.conf file as wpa_supplicant.conf.normal)
- Replaced wpa_supplicant.conf using wpa_supplicant.conf.adhoc (basically leaving backups of each in the directory)
After doing this and enabling Wi-Fi I was able to see and connect to my Cliq running Barnacle. I am also able to connect to my standard Access Point as well without any configuration change. The only issue is that I am not running any security but I think this is not a difficult update to the .conf file. I may add a second network SSID entry with a PSK and use "Wireless Tether" on my Cliq to test. For now I am just happy to connect and Barnacle allows me to screen and block all connection requests. The primary deviation from the great instructions earlier in this thread that got me up and running was the content of the wpa_supplicant.conf file. I used part of my original file and part of the file .adhoc file from earlier in this thread.
ctrl_interface=DIR=/data/system/wpa_supplicant GROUP=system
update_config=1
eapol_version=1
ap_scan=2
network={
ssid="JJJ"
scan_ssid=1
key_mgmt=NONE
mode=1
priority=1
}
Obviously my SSID is set to JJJ (I like J's). I got my inspiration from a file I found buried in my Android file system (attached as ...notes.txt). It is not very interesting reading but it provides lots of clues and it explains the meanings of all the parameters.
So, Ad Hoc connection is possible possible on A Flytouch2 under Eclair.
Now, my rant... it is unconscionable that this is not supported natively in Android. I would speculate that this was a conscious decision by Google resulting from pressure from the big carriers. What I don't understand is how this capability is available in the iPad!? Apple would certainly bow to external pressure (witness the iPhone) from carrier relationships. They also come with $40/mo built in service... so go figure. Now I am delighted to use both my Android Tablet and my iPad with Ad Hoc WiFi served up from my Cliq on T-Mobile!
I hope my additional notes help someone else.
Im gonna have to look at this tomorrow and see if i can finally connect to my omnia 2 running wmwifirouter
Im using an AT&T Streak now on dj steves froyo 1.5.1, I hotspot tether just fine to other devices.
Sent from my Dell Streak using Tapatalk
urphonesux said:
Im gonna have to look at this tomorrow and see if i can finally connect to my omnia 2 running wmwifirouter
Click to expand...
Click to collapse
Interested if it worked? please let me know what settings were needed on the Omnia/WmWiFirouter
Shadowphox said:
Im using an AT&T Streak now on dj steves froyo 1.5.1, I hotspot tether just fine to other devices.
Sent from my Dell Streak using Tapatalk
Click to expand...
Click to collapse
as a client? or you can create a network using your 3g->WiFi hotspot
So, went out and picked up a Mini Pro for the misses.
Well, off the bat I went crazy cause I couldn't find "Market" and well...after searching online, guess this damn region doesn't support the Market. How wonderful is that, so downloaded stuff online through slideme. Which really still sucks.
Then when I downloaded things to my laptop and wanted to bluetooth them over, I couldn't. Then when I wanted to send ringtones from my phone to the mini pro, I couldn't. So I searched, and wouldn't you know it. I gotta download a program, so I downloaded bluetooth explorer and then it prompted me that I gotta root this SOB to be able to send files through bluetooth? Did I just buy an iPhone or what?!
So I plugged in the phone through USB. And we copied over the APK. and I downloaded a file explorer, so I could get to the damn APK (really no file explorer included, or clearly apparent?). And when we launched the file (MSN), we found we couldn't send files, images, or anything other than text. Are you kidding me?
With all these limitations, how is Android so popular?
Are there any possible solutions without having to root this bastard? (aside from MSN). I just bought this thing and don't wanna void warranty so damn early so I could make it something PRACTICAL like every other phone.
I'm guessing you're used to nokia's and the like. I must say i've found bluetooth file transfer a little hit and miss on android, but you need an app called bluetooth file transfer but it's on the market i'm afraid. Where are you then? You can get the market app from these forums and an enabler for regions not supported so you may need to do some digging.
Sent from my E10i using XDA App
Not used to Nokia's. Used to WinMo and running Android Froyo on my Topaz.
Could not find the market standalone app for the life of me. And the phone is from Saudi Arabia, and I can't justify rooting it just yet.
@bmzloum
Hi! I feel your pain. Android Marketplace is not supported in my part of the world too. I am looking for alternate ways to get apps into my phone.
You mentioned that you had to download a separate File Manager to get to the .apk files. Can you tell me which app you are using?
Also how did you manage to install the File Manager in the first place if you could not get to the .apk files?
Do you copy the .apk files to your MicroSD card? Do you any other advice to make installation easier if we download the Apps to our computer then then try to install them to our phone?
Thanks in advance for any help.
Cheers and good luck with your new phone.
Appbrain App Market and Apktor are viable alternatives for getting apps on your phone, the latter you'll need to find public repositories for. Sorry can't post links cause of restrictions on a new account, but google knows all.
drussthelegend said:
You mentioned that you had to download a separate File Manager to get to the .apk files. Can you tell me which app you are using?
Click to expand...
Click to collapse
Hey, found
Code:
http://slideme.org/
which let me download with the barcode, and then I installed the sites app manager directly on there. There are a ton of file managers, I downloaded two, I forget which. But the two most popular ones. Both worked, but only one handled ZIP files. I don't have the phone beside me, so can't recall...
I found the Market standalone apk, but it crashed everytime I clicked on "Download" so I gave up on it.
I'm gonna try those suggestions posted up and see if they have a few new nice apps on there.
I had the exact same issue as others above. My solution was to use the debranded UK Firmware, root the phone and then use the Bluetooth File Manager.
bmazloum: My phone also came from the UAE side and didn't have the Market. I used Omnius to flash the firmware. A friend of mine on the otherhand paid the local Sony Service Centre to flash and debrand the ROM. Maybe this might help
Guys you don't have to move the apk file over to the phone in order to install it btw... get Adb from the Android SDK and then place the apk file in the same folder as adb.
And then from command prompt, navigate to the folder with adb and your apk and type "adb install example.apk".
Make sure you have USB Debugging (Applications -> Development) enabled and that's it.
Works nicely on a Mini. Not sure about the Pro to be honest.
I am totally new to android, but I decided to try to root my phone anyway, mostly to be able to access the eduroam network at my school.
1) I succeeded in rooting my x10mini using the exploid method (this took me two whole days because I was so scared to break my phone lol), but after I updated today, through PC companion, I seem to have lost root. Should I not accept SE updates? Do I just root it again the same way I did the first time?
2) I downloaded Market Access to be able to download Wifi Config Editor. After installing Market Access, if I try to download something off the market, it takes a couple of minutes before the download starts. Even when I am in my own country's market. Is this normal?
3) How do I stop the emulation of foreign SIM card? So far I have tried emulating my original provider or restarted the phone.
4) If someone calls me while I am emulating a foreign provider, will the call be more expensive or something?
5) I tried to directly change the wifi settings with professordes instructions in the original exploid thread
Now that root is in wild one immediately useful thing to do is fix the WPA-PEAP which is missing. I need this for the eduroam university network at work.
So, with the phone connected and usb debugging on/wifi toggled off, from the androidSDK on a PC (Windows,Linux,Mac) get a shell.....
1) adb shell
2) su
3) cd /data/misc/wifi
4) busybox vi wpa_supplicant.conf
(to edit the wpa configuration file)
5) add this at the end
network={
ssid="eduroam"
key_mgmt=WPA-EAP IEEE8021X
eap=PEAP
identity="MYIDENTITY"
password="SECRET"
phase1="peapver=0"
phase2="auth=MSCHAPV2"
priority=7
}
or similar, where MYIDENTITY is your eduroam login ID and SECRET is your password. This is taken verbatim from another phone (HTC Desire, Android 2.2) which does work OK. You could also edit the file off phone and adb push it on, just watch ownerships and permissions don't get munged up.....
6) save
7) log out
8) connect and surf, it works for me
Click to expand...
Click to collapse
I copy-pasted steps 1-5 (I pasted the last step directly after the text in the cmd window). Since I am a noob, I didn't know how to save and exit, so I just closed the cmd window and unplugged usb...
BIG MISTAKE!
...After I restarted it, my phone was completely dead. After a one hour recharge in the wall socket, the phone worked again and it seems fine now.
So, could someone make a step-by-step (noob-)guide on how to successfully change the wifi settings with this metod?
6) Thank you in advance
-krumcake
1 - Updating it removes the root, but you can simply re-root it the same way.
4 - That only applies to the market. It fools it into thinking you're using a SIM from a different country.
Last night I was checking out Cyanogen's web site and I came across this:
Bluetooth Voice Commands Missing in CM6?
Hello,
One of the newer features that I liked so far in CM-6 was the ability to long press my bluetooth headset action button which resulted in a voice telling me to say a command. This was much better than the original phone voice dialer, which requires manual intervention to pick a number from its list of guesses after you speak, and which offers no voice prompt to let you know when it's ready.
Well, as of upgrading to CM-6.0 from the 8-25 nightly, the bluetooth/headset dialer is gone and when I long press my bluetooth headset button It's back to the old phone voice dialer which requires manual intervention to place a call and offers no voice prompt. How do I get the bluetooth dialer back?
I have attached the 09SEP-VoiceDialer.apk from CM-6 release for easy downloading.
***Instructions- Download the file into your root of your SD card, using Root Explorer remove the old VoiceDialer.apk and install the new 09SEP-VoiceDialer.apk
The OLD VoiceDialer.apk can be found under /system/app
Mine is working great!
Any questions, PM me....
Enjoy!
my bluetooth headset can now operate the voice commands, however, after a command is given, Voice Dialer FCs.
KF34
gohamstergo said:
my bluetooth headset can now operate the voice commands, however, after a command is given, Voice Dialer FCs.
KF34
Click to expand...
Click to collapse
Did you remove the old VoiceDialer.apk?
Also, don't forget to change the permissions on the 09SEP-VoiceDialer.apk after yoo move it to /system/app.
This is working great for me, back to the way it was before the update!
Sent from my FroyoEris using XDA App
so as far as the instructions:
***Instructions- Download the file into your root of your SD card, using Root Explorer remove the old VoiceDialer.apk and install the new 09SEP-VoiceDialer.apk
is install the new file is just copying it then pasting it into the system/app folder using root explorer, longpress on app and change permissions to allow all. then reboot.
EDIT: apparently yes, my bt headset works perfectly with voice dialer now. thank you.
This is great -- restores the BT voice dialing functionality that should have been stock in the Eris from the start
Is the source for this APK available? I wonder if it would be possible to modify to add an optional "confirmation" step:
User: "Call Jim Somename"
Phone: "Calling Jeff Someothername, is that correct?"
User: "No"
Could certainly be fancier, like presenting several options, but the above would be sufficient to prevent misdialing people you don't mean to call in other area codes, etc. That's my main hesitation to use it right now; my wife's name, in particular, seems to mismatch to other names often.
I haven't done much Android development yet, but I'd be interested in poking at this code.
jmastron said:
This is great -- restores the BT voice dialing functionality that should have been stock in the Eris from the start
Is the source for this APK available? I wonder if it would be possible to modify to add an optional "confirmation" step:
User: "Call Jim Somename"
Phone: "Calling Jeff Someothername, is that correct?"
User: "No"
Could certainly be fancier, like presenting several options, but the above would be sufficient to prevent misdialing people you don't mean to call in other area codes, etc. That's my main hesitation to use it right now; my wife's name, in particular, seems to mismatch to other names often.
I haven't done much Android development yet, but I'd be interested in poking at this code.
Click to expand...
Click to collapse
I do not know but I can give you a link to Cyanogen's post if you would like....
http://forum.cyanogenmod.com/topic/6497-bt-voice-dialing/page__p__57811__hl__bluetooth__fromsearch__1#entry57811
I remove the old voicedialer. I copied over to system/app change the perms and reboot. when long pressing the bluetooth the dialer comes up but never prompts. I tried renaming the file. I tried just an install. that worked once but FC verytime after.
What am i doing wrong
Thanks for this
I can't believe that Google has worse technology than MS on this! MS Voice Command is far superior.
I tried vlingo with mixed results.
Will try this.
Just installed on my Aria running Liberated 2.2 and it works great!
BTW, I couldn't for the life of me delete the old VoiceDialer.apk using a file explorer, so I just took a shot and installed this Voice Dialer, so no real need as far as I can tell to go through the hassles of the instructions above.
Many thanks.
I tried.this but I keep getting a parsing error ???? I'm a noob have no clue what that means..lol
Sent from my Eris using XDA App
I realize that this is a bit of a dead post, but do you think this apk would work on a Samsung Captivate? I'm currently running with Perception 10.3 and Speedmod kernel, but for some reason the BT Voice Dialer has decided to stop working and is continually stuck at Starting Up.
I'm trying to get this to work on my Aria running FR0008 but no dice. Even using Root Explorer I simply cannot get either the original Dialer.apk deleted or the replacement 09SEPDialer.apk installed.
What am I doing wrong? I REALLY want the proper Bluetooth dialer in this ROM as I use a headset often and at the moment I prefer it to the Cyanogen ROMS.
woodbane said:
I'm trying to get this to work on my Aria running FR0008 but no dice. Even using Root Explorer I simply cannot get either the original Dialer.apk deleted or the replacement 09SEPDialer.apk installed.
What am I doing wrong? I REALLY want the proper Bluetooth dialer in this ROM as I use a headset often and at the moment I prefer it to the Cyanogen ROMS.
Click to expand...
Click to collapse
Have you tried this? Download the 09Sep-VoiceDialer.apk to your computer. Rename it VoiceDialer.apk and place it in your tools directory of SDK. Connect your phone to PC. Open a command prompt window and navigate it to your tools directory of SDK. Type adb remount. Then type adb push VoiceDialer.apk /system/app. Then adb reboot. Be certain to take not to the caps in the file name as well so it will overwrite the one that's already in place on your phone. Hope this helps
CondemnedSoul said:
Have you tried this? Download the 09Sep-VoiceDialer.apk to your computer. Rename it VoiceDialer.apk and place it in your tools directory of SDK. Connect your phone to PC. Open a command prompt window and navigate it to your tools directory of SDK. Type adb remount. Then type adb push VoiceDialer.apk /system/app. Then adb reboot. Be certain to take not to the caps in the file name as well so it will overwrite the one that's already in place on your phone. Hope this helps
Click to expand...
Click to collapse
That sounds very helpful, only problem is I have no idea about SDK and ADB. Is there a really abbreviated way of getting me up and running with this?
woodbane said:
That sounds very helpful, only problem is I have no idea about SDK and ADB. Is there a really abbreviated way of getting me up and running with this?
Click to expand...
Click to collapse
Try here http://developer.android.com/sdk/index.html
There's instructions for installation and the downloads. Everything you should need
CondemnedSoul said:
Try here http://developer.android.com/sdk/index.html
There's instructions for installation and the downloads. Everything you should need
Click to expand...
Click to collapse
Awesome, I'll try giving that a whirl later this evening. Thanks for the pointer.
So, I gotta be honest, I just simply do not have the technical know how to get this working. I've downloaded and installed all relevant files but can't even seem to get the phone connected.
Here's what I'd love to be able to do, simply replace the VoiceDialer.apk in the Aria FR008 ROM - which does not support Bluetooth voice dialing with this one that apparently does.
I have tried unzipping the FR008 ROM and replacing the file and rezipping. When I go to install it from card in recovery mode it immediatly crashes. I'm seeing that the FR008 zip is "signed" and guess that I'm missing doing something important here, resigning either the whole ROM or just the file?
Can anyone please help me out here as I'm really struggling with this.
woodbane said:
So, I gotta be honest, I just simply do not have the technical know how to get this working. I've downloaded and installed all relevant files but can't even seem to get the phone connected.
Here's what I'd love to be able to do, simply replace the VoiceDialer.apk in the Aria FR008 ROM - which does not support Bluetooth voice dialing with this one that apparently does.
I have tried unzipping the FR008 ROM and replacing the file and rezipping. When I go to install it from card in recovery mode it immediatly crashes. I'm seeing that the FR008 zip is "signed" and guess that I'm missing doing something important here, resigning either the whole ROM or just the file?
Can anyone please help me out here as I'm really struggling with this.
Click to expand...
Click to collapse
Yeah... if you unzip it you will need to sign it when you zip it in order to flash it. Try opening to rom with 7zip or winrar and just drag and drop the new one into the zip to replace the old one. Don't unzip it.
Sent from my Blackened Ginger using XDA App
I had/have bricked my X10 Mini Pro
I followed the instructions here
http://forum.xda-developers.com/showthread.php?t=743800
and after receiving NO errors and thinking everything was finished unmounted from the host machine and unmounted the sd card and re-booted the phone
Sadly it all went tits-up.
It booted into the locked screen and the reolution was way lower than before
The GUI was gone leaving only the activity/notification bar - the rest of the touchscreen was a fetching blue, with no applications, no corners, no nuffink.
Somewhere in this forum was a tip to start PCC and hold down the back and home keys, tap the power button and when the screen goes black connect the phone to the PC.
This gave me back a GUI but I have lost some Apps and more importantly it has booted into airline mode and no amount of turning 'Airline Mode' on/off with the power button will get rid of the airplane icon in the notification bar. So I can't get into my phone carrier nor any wireless networks.
So a few questions before I start again
Build.Prop file
changing numbers to have an unbranded phone for Australia ?
- is it just a matter of opening the file with gedit and changing the string with something from the list for Australia then saving or need I also change locale to AU ?
ok assuming that I only cut 'n' paste the 1234-1234, or whatever the number is I need to use to allow SEUS to update the phone for me, into the build.prop file then save it to copy from the SD card into the phone's system directory
( ./busybox cp /sdcard/build.prop /system/ )
I think that command roughly translates to " run busybox to copy the build.prop file on the card into the system sub-directory of the phone"
doesn't it ?
so, to continue this example,
I am in Australia,
I have a phone that used U20a firmware from this line
U20a WORLD-1-2-5 CDF1238-2298 1239-2226 3 AU/Black
I would cut the 1239-2226 and paste it into line #3 of the UK generic .prop file
ro.product.name=U20i_1238-0199
or do I change the line to read ro.product.name=U20a_1239-2226
or am I barking at the wrong tree ?
and
#68 ro.product.locale.region=GB
should that now read
"ro.product.locale.region=AU"?
hey mate hope this helps:
backup your build.prop first
open build.prop and replace the 1234-1234 values with the values directly after CDF, in this case 1238-2298.
do the following:
adb push build.prop /sdcard/build.prop
adb shell
su
mount -o rw,remount /dev/block/mtdblock0 /system
busybox cp /sdcard/build.prop /system/build.prop
exit
Now run update service.
it will ask you to connect your phone to the system. You will need to turn your phone off, hold the back button and connect the usb then after that just follow the prompts.
goodluck
Am I editing lines
#3 ro.product.name=U20a_1238-2298
AND
#8 ro.build.fingerprint=SEMC/U20a_1238-2298/SonyEricssonU20a/delta:1.6/1.1.A.0.8/1:user/release-keys
===
backup your build.prop first
===
I assume this is
./busybox cp /system/build.prop /sdcard/
Boo hoo hoo
That didn't work, having rooted the phone (I assume that when I connect it to my PC run CMD.exe and in the terminal run 'adb shell' then su the SuperUser application opens up in the phone to allow/deny is an indication that I have root)
I have edited the generic UK build.prop file to change it to an Australian Vodafone build.prop file ---I think ---
Exited out of the adb shell, exited out of the command line interface
unmounted the phone from the host machine
unmounted the client - the phone
shut down the phone
removed the battery for at least 5 seconds
during which time I completely removed all traces of SEUS using a Windows application called CCleaner
and reinstalled
opened the Update Programme
put the battery back in the SE phone
held onto the Back Button as if my life depended on it
connected the phone to the PC
SEUS says ..........
wait for it ..............
No new software available, try again later
I may well be the last Australian X10 mini pro owner running Android 1.6 and am getting pretty frickin' sick of being told by Sony that there's nothing new for me
i had the optus firmware but since i live in china now i have been using the chinese firmware. do system restore and see how that goes, otherwise get the optus system installed and update it...but as far as i know everybody should be upgraded to 2.1 by now...
Also all you have to do is just edit the build.prop and restore the original firmware through pc companion... and then try to get the 2.1 update hope that works mate
saywot said:
No new software available, try again later
I may well be the last Australian X10 mini pro owner running Android 1.6 and am getting pretty frickin' sick of being told by Sony that there's nothing new for me
Click to expand...
Click to collapse
You should have used "repair". That will work.
vlissine said:
You should have used "repair". That will work.
Click to expand...
Click to collapse
There isn't a 'repair' option any more with SEUS
and I keep getting the "No new software for your phone" message when attempting to repair using PCC
I'm guessing that I need to edit something else because I have some sort of a VFE file system version
Can I edit the firmware version in the build.prop file to something else
- then ask PCC to repair ?
Hmm
I just did the HBBHBHHB shuffle and see that in the software info section there appears to be an inconsistency
there is a different identifying strings of numbers for
- Phone software version
- S1 Boot Version
- ETS Sofware Version (whatever that is !!)
- Customization Version
I give up
I have edited the build.prop file with quite a few CDF numbers
re-booted
connected to SEUS
only to be told
"there is no new software for your phone"
I am starting to think that there will never be any 2.1 juiciness
I've tried Telstra AU, I've tried 3 Au, and Vodfone
- nothing and am now at my wit's end
And it's not as if this forum is bubbling over with suggestions as to the reason why a rooted phone can't have different firmware installed so it may have an OS upgrade
vlissine said:
You should have used "repair". That will work.
Click to expand...
Click to collapse
well, there's a problem with that
The only 'repairing' is done with PC Companion
I have un-installed/re-installed that POS about 4 times and now it's throwing
"Unable to install or start phone software update components" at me
I decided to just dump the generic UK U20i build.prop file into the system directory and overwrote whatever I had there (the older one was saved as build.prop.bak)
This still didn't get me any software updates from SEUS - if that's what Sony is calling the next Operating System.
So apart from copying and pasting the whole build.prop file I want to use and asking what EXACTLY needs to be changed.
I have a question or two
-- "VFE-1-8 1.1.A.0.8" how can I get it changed to 'World 1-2-5 ?
-- and no matter what I do to the customisation version using an edit or two of /system/build.prop the software version stays the same and this is why I think I keep getting a "No New Software For Your Phone - try again later" from both SEUS and PCC
and the Model Info always reports U20a
as always any help or suggestions will be gratefully received
saywot said:
well, there's a problem with that
The only 'repairing' is done with PC Companion
I have un-installed/re-installed that POS about 4 times and now it's throwing
"Unable to install or start phone software update components" at me
Click to expand...
Click to collapse
There was no need to install and reinstall PCC, you could have simply deleted the directory containing downloaded firmware, so that it will download the correct one.
You are doing lots of unnecessary things, and the way you do it takes you nowhere, since instead of simply following the guide which has been posted and tested by practically everyone on this board you start fiddling with wrong parts of the system.
My sincere advise to you is spend 10 euros and get it reflashed by these guys http://www1.davinciteam.com/index.html
Good luck.
There was no need to install and reinstall PCC, you could have simply deleted the directory containing downloaded firmware, so that it will download the correct one.
You are doing lots of unnecessary things, and the way you do it takes you nowhere, since instead of simply following the guide which has been posted and tested by practically everyone on this board you start fiddling with wrong parts of the system.
Click to expand...
Click to collapse
Now you tell me !
I know what I have been doing is futile and wasting my time.
But the guide is NOT simple for some of us less-talented people.
It doesn't say whether to replace all instances of the xxxx-xxx number in the build.prop file or only one,
I'm still not clear where there is a mention of CDFxxxx-xxx yyyy-yyyy whether I should use xxxx-xxxx or yyyy-yyyy in editing the properties file
Also the phone is a u20a phone, the UK Generic file is for u20i devices, and the guide doesn't make any distinction between the different hardwares - and they are different
In which directory does PCC keep the downloaded firmware that I am to delete?
'Dashboard' 'Drivers' 'Languages' or 'Skin' are the choices of directories, the rest of the C:/Program Files/Sony Ericsson/Sony Ericsson PC Companion/ folder are individual files - dlls exes etc etc
So to start again
I am about to upload (via the CLI in Windows) so
one last question (which is really the first question)
which line do I change in the build.prop file
- I am now assuming from the tone and content from #vlissine that I am changing too much so it's one line with one new number
and is it the string of numbers attached to the alphabetic CDF or those immediately following the CDF alphanumeric string in the u20a listing?
This is sort of the firmware I'm after
U20a WORLD-1-2-5 CDF1239-5023 1238-9150 Telstra AU/Black
which is to ask - do I use "1239-5023" or "1238-9150"
B.T.W.
if the phone has 1.1.A.0.8 firmware
and the build.prop file has 1.2.A.1.174
doesn't that create some sort of 'inconvenience' for me ?