yashsingh1/xdaforums huggingface dataset:
[Xoom Q&A, Help & Troubleshooting] okantomi:
Yes, whatever img file you are flashing through fastboot needs to be in the same folder.

I feel your frustration. This has got to be something so simple that it's being overlooked.

I would suggest that you review again every step you have taken, redownload your file (go back to the R4c recovery file in the OP of solarnz thread, cause I'm not sure the one you downloaded was actually the most recent...) If you didn't already do this, rename the file recovery.img, making sure that you don't have the hidden file extension, and use that syntax when flashing. Make sure your micro sdcard is in your Xoom, and try it again.
[Xoom Q&A, Help & Troubleshooting] chrisjabroni:
Should I uninstall Android SDK and Java SDK, Moto Drivers, basically everything and start fresh?
[Xoom Q&A, Help & Troubleshooting] okantomi:
If you've been able to unlock, you seem to have the files needed for ADB/fastboot to work, but of course you could always try that. Are you sure you are actually unlocked? If not, that would be the problem, right there.

Follow my guide to the letter and see if it doesn't work for you. Like I said...there is something impedeing you that is so simple it is just being overlooked.

Step by step, figure it out. I know that you are almost there.
[Xoom Q&A, Help & Troubleshooting] chrisjabroni:
Is there any way to check to ensure that I have, in fact, unlocked the boot loader?
[Xoom Q&A, Help & Troubleshooting] okantomi:
Just follow the steps in the guide. If you are not unlocked, you will follow the instructions that appear on your Xoom when you type fastboot oem unlock and you have to use the volume buttons to navigate and the power button to choose. If you are unlocked it will either give you an error or just not give you those instructions (I don't remember which).
[Xoom Q&A, Help & Troubleshooting] chrisjabroni:
It was so simple I can't believe it...

I was just opening up cmd.exe and executing the commands... I didn't read the part about opening the command prompt using the platform-tools folder! Worked like a charm after that!!!

Thank you SO much Okantomi! I appreciate it immensely!

Now I have to decide what rom :) *Giggles like a little school-girl*
[Xoom Q&A, Help & Troubleshooting] okantomi:
I knew you'd get it. Congrats!

There is only one Rom...Team Tiamat Moray.

There are a few choices for kernels...I love the Tiamat Odachi kernel.

Have fun!
[Xoom Q&A, Help & Troubleshooting] chrisjabroni:
My last question :)

Where can I find more info on roms and kernels? (Like what order to install, how to properly back everything up (I.e., Nandroid)

I would like to instal the Tiamat rom and kernel, I just want to do it right :P
[Xoom Q&A, Help & Troubleshooting] okantomi:
Check out the Xoom Heaven thread at the top the General forum.

for nandroid backup, reboot into cwm recovery and navigate to backup and restore...choose backup.

I flashed the Moray Rom first, did a wipe in the recovery menu, rebooted, went through the setup then when I knew everything was working fine, I rebooted into recovery again and flashed the oc version of the kernel. Should be no reason to rewipe.
[Samsung Epic 4G Touch] SocialReject:
Didn't I just answer this question lol...

2 threads aren't necessary in these forums, we see your question.

Sent from the future.
[Samsung Epic 4G Touch] JohnCorleone:
True but its easy to go into panic mode when your expensive toy wont do a damn thing. I have been there before. A few minutes waiting for answers seems like an eternity.
[Samsung Epic 4G Touch] SocialReject:
lol, understood.

Sent from the future.
[Samsung Epic 4G Touch] wase4711:
First of all, this is the ONLY thread I made for this question; I made a post in the thread where the rom was located to make the dev aware of the issue

I'll be watching you closely, for when you have a serious issue and ask for help, to make sure you don't post it more than once..

And, BTW, I used Heimdall on my own, without your suggestion; I've been flashing phones for longer than you've probably been on this earth...
[Samsung Epic 4G Touch] wase4711:
Thanks for your kind words, John; you show the kind of class that used to be everywhere on this forum!
[Samsung Epic 4G Touch] h20wakebum:
where are you seeing a new rom from CAulk?

All original Posts I see in DEV the only Caulk one are for the 1.5a ROM,

thanks,

RR
[Samsung Epic 4G Touch] wolfkstaag:
The "Stock EK02" ROM.
[Samsung Epic 4G Touch] wase4711:
its in here bro..

http://xdaforums.com/showthread.php?p=19862447&posted=1#post19862447
[Samsung Epic 4G Touch] SocialReject:
Bro, relax smh.... reread what I said and stop taking everything to heart... if I misread a thread name, tell me that. No need to brew up a storm.. anyway, hope you find a solution.

Sent from the future.
[Samsung Epic 4G Touch] JohnCorleone:
Actually if you are on XDA app or Tapatalk, lately its been occasionally doubling up on random threads. I have seen it happen a several times lately. It will show the same exact thread, same amount of posts, but views are different. That may have happened here. Thanks for the kind words wase.
[Samsung Epic 4G Touch] SocialReject:
These 2 threads aren't asking the same question?

http://xdaforums.com/showthread.php?t=1370311

I understand you were in an tight spot but no need to lash out at me for simply pointing out the obvious and trying to help you out...

That is all.....

Sent from the future.
[Samsung Epic 4G Touch] JohnCorleone:
Yup, looks like it got doubled up. I think that's what happened anyway
[Samsung Epic 4G Touch] SocialReject:
Oh well, not that big of a deal.

Sent from the future.
[Samsung Epic 4G Touch] JohnCorleone:
Its really not. Just trying to keep the peace. Since the new modems its been so civil around here...its actually nice. You've been thanked too Social
[Samsung Epic 4G Touch] SocialReject:
lol, my thoughts exactly. No need to plague the forum with bad blood. I appreciate that, man.

Sent from the future.
[Samsung Epic 4G Touch] wase4711:
sorry for flying off the handle; lets just forget it, and have fun again..
[Huawei Ideos X5 U8800] cenkcnk:
hi guys, i could wake the phone up by pressing volume keys when i use the 2.2

but it useless now with 2.3, do you have same issue?
[Huawei Ideos X5 U8800] m1trand1r:
i guess that is normal..not an issue..:P

Sent from my ultrafast

Galaxy 3
[Huawei Ideos X5 U8800] darkweather:
it's not a little issue it's just a big problem.
[Huawei Ideos X5 U8800] ik_jefke:
I have the same annoyance.

This is a Beta release and my guess is that this will be resolved in the official release.

I also miss the ability to go to silent mode from the lock screen.

BUT, apart from that it seems to resolve my random reboots, fingers crossed :p
[Huawei Ideos X5 U8800] Herkku:
Yes, same situation here.

Other than force of habit, is there any specific reason why the previous arrangement was better? After a few hours of use, the Power Button wake-up feels normal.

Yikes, that sounds like a pretty serious oversight. For example, my wife doesn't use the 'draw a pattern' security screen specifically because she needs/likes the ability to immediately slip the phone into silent mode. Fumbling to get your phone into silent mode is awkward and uncomfortable for the user and frequently the user's neighbors. ;-)

I had assumed that the various unlock destinations on the new locked screen could be user assigned. I haven't looked into the matter very far, yet. I suppose the working solution is just stroking into the homescreen and then utilizing the volume key.
[Huawei Ideos X5 U8800] jegor011:
For example, I use my phone in a car on a dashboard. And if, for some reason, it turns the screen off I don't want to chase the button in the dark. Or if I just want to see the time and I'm wearing gloves. ;)
[Omnia 7 General] guycross:
I have an Omnia 7 and use T-Mobile - I live in London.

I debranded and upgraded to Mango as I got bored of waiting for the upgrade, and then got another upgrade with no noticeable effect a couple of weeks ago.

It feels like since the latest upgrade I am struggling to get a signal almost anywhere that I, previously would - more than one place not just a dodgy transmitter.

any ideas?

G
[Android Software/Hacking General [Developers Only]] Sandmonkee:
So I've been putzing around with this thing for a few days since I got it. One thing I've been trying to do now that I have root access is get it to connect to adhoc wifi. To be specific, I want to use my data-enabled cellphone as an adhoc wireless access point so that I can connect the LePan to it over wifi to surf the net, email, play games, etc. Of course, by default, Android is set up NOT to connect to adhoc wireless, or even recognize adhoc networks.

I installed a wifi sniffer app on the LePan, and it can see the adhoc network that my phone is broadcasting, but it won't connect. I managed to find a few webpages with instructions on how to mod android to connect to adhoc, but most of the instructions are device specific, and obviously there's nothing out there for the LePan yet, as its a relatively new device (I would have posted this in the TC970 forum here on xda, but there isn't one yet). Most of the instructions talk about modifying two files in the /system/etc/wifi folder. The first is tiwlan.ini, and the other is wpa_supplicant.conf.

I basically mixed/followed the instructions on these two webpages:

http://www.slatedroid.com/topic/1054...adhoc-on-a81e/

and

http://www.slatedroid.com/topic/1819...rk-android-22/

So right now I've added the following lines to tiwlan.ini:

WiFiAdhoc = 1 (Change from 0 to 1)

dot11DesiredSSID = InsertyourSSIDhere

dot11DesiredBSSType = 0 (Add this line in)

And I've replaced everything in the wpa_supplicant.conf file with this:

ctrl_interface=tiwlan0

update_config=1

eapol_version=1

ap_scan=2

network={

ssid="Ad-hoc ssid here"

scan_ssid=1

key_mgmt=NONE

mode=1

priority=1

}

network={

ssid="Your Accesspoint ssid here"

psk="your wpa key here"

key_mgmt=WPA-PSK

priority=2

}

(obviously I have my own settings in the real file)

In addition, I copied the wpa_supplicant file from the zip in this post:

http://xdaforums.com/showthread.php?t=754961

into /system/bin/.

Now when I try to use my wifi, it turns on, says its trying to connect for a bit, but then the eventually just turns off without connecting or detecting any networks (so it probably doesn't actually turn on at all).

I've backed up all my files, so no problem getting it all back and working like stock, but I'd really like to be able to connect to adhoc with my new tablet. Suggestions are most welcome.

***Sorry if this is posted in the wrong forum. Like I said, there is not yet a dedicated forum for this device, otherwise I would have posted there. Mods - any chance of creating a forum for this device? I've seen a few other stray TC970 posts here on xda.
[Android Software/Hacking General [Developers Only]] Shawn_Everson:
Sandmonkee,

After messing about with this myself, I found a supplicant that works on our tablet (I tried about 6 different supplicants until I found this one). It is the one for a nook color. See this thread http://xdaforums.com/showthread.php?t=868354

It works on my Nokia N900 with the MobileHotspot app.

I believe that the problem with the supplicants that were in the post that you referred to is that they were linked to use wext instead of the statically linked libCustomWifi for the TI chip. See the comments section on szym's blog about the patch.

It would be better to apply szym's patches to the code tree that was used to create the wpa_supplicant for this tablet instead of TI's reference code as this one did. That might fix the sleep problem. I don't know where to find the sources. Anybody have any ideas? If the sleep issue becomes a problem, I might look into modifying the reference code (altho' I have enough on my plate without spending too much time on this toy).

***** UPDATE ****

This supplicant doesn't have a problem on this tablet with sleep as was described in the above thread.

***** END UPDATE ****

BTW the wpa_supplicant.conf that you want to modify is in /data/misc/wifi NOT /system/etc/wifi

Here is my version (replace the ****** with values appropriate for you)

The 1st entry is for my AP using WPA, the 2nd one is for my ad-hoc phone using WEP. You might need to add the line "ap_scan=2" if you don't broadcast a SSID.

ctrl_interface=tiwlan0
update_config=1

network={
ssid="*****"
psk="*********"
key_mgmt=WPA-PSK
priority=1
}

network={
ssid="*********"
scan_ssid=1
key_mgmt=NONE
group=WEP104
auth_alg=SHARED
wep_key0="********"
priority=2
mode=1
}

I don't know if the "group=WEP104" line is needed, I found it in another thread somewhere but it doesn't seem to hurt.

Let me know if this works for you too.

-Shawn
[Android Software/Hacking General [Developers Only]] Sandmonkee:
Works!

Shawn, yer a genius.

I have been struggling with this for a week or so now, and it is finally working. You just increased the usefulness of my tablet by 100x

Thanks again man!!

Mike :D
[Android Software/Hacking General [Developers Only]] john9:
yeah, bro. That's what's up.Thanks!
[Android Software/Hacking General [Developers Only]] joofeloof:
This is great stuff...thanks for sharing. One quick question for you guys: are you using adb to modify the files? I can't seem to get adb to work...do i need a driver different than the one derkoch linked to in the root achieved thread?
[Android Software/Hacking General [Developers Only]] Shawn_Everson:
joofeloof,

I used the one that you referred to. I rooted the tablet. Then for my own sanity I installed HackersKeyboard to get a real keyboard, bash shell so I could get filename completion, and nano for a small editor from the shell. Now the tablet is much like a standard linux system from the command line. I used adb to push the files to the sdcard and copied the files to the correct locations from a local shell. Don't forget the permissions. Any text editor will work to edit the configuration files, altho' I prefer nano. If you are familiar with vi, it is available also.

If you can't get adb to work, you could just copy the files to your sdcard and move them locally.

To do this mod, the tablet must be rooted.

Hope this answers your questions.

-Shawn

P.S. Does anybody know how to get a bluetooth hid device (keyboard/mouse) to work on this tablet? There is a nice folio that has a BT keyboard built in that would make this a great terminal for doing remote system admin stuff.

**** UPDATE****

Found it. For BT keyboard use EasyConnect which is available in the market.

**** END UPDATE ****
[Android Software/Hacking General [Developers Only]] Sandmonkee:
Non-terminal instructions

Shawn's method above will work, but I did it using ES File Explorer with root permissions enabled.

1. Root your phone as described in DerKoch's post

2. Download Shawn's wpa_supplicant file to your PC and extract

3. On your tablet, download and install ES file explorer from the market (its free)

4. Open ES explorer and go into the settings. At the bottom of the list, enable "root explorer" and "mount file system"

5. Use ES file explorer to copy your /data/misc/wifi/wpa_supplicant.conf to your SD card

6. Plug the tablet into your PC and turn on USB file sharing and USB debugging

7. Copy the wpa_supplicant.conf file from your SD card to your PC and modify per Shawn's instructions above, with your own settings.

8. Save the file and then copy it back to your SD card, along with Shawn's wpa_supplicant file

9. Stop USB file sharing on the tablet

10. turn off wifi on your tablet.

11. Open ES file explorer on the tablet, copy the wpa_supplicant.conf file from your SD card to the /data/misc/wifi directory (overwrite), then copy Shawn's wpa_supplicant file to /system/bin (also overwrite).

11.5 Note that these files need to have the right permissions (by default, they should already). In ES file explorer, do a long press of the wpa_supplicant file you just copied to /system/bin, then click on properties, then "change permissions". It should be chmod755, ie the X's should look like this:

X X X

X 0 X

X 0 X

For the wpa_supplicant.conf file, it should be chmod777 (ie ALL the boxes should have X's)

12. Turn on wifi. That should do it.

I noted that although I included the lines from Shawn's file for the adhoc WEP security, when my tablet saw the phone (which was unsecured), it created a new entry in the list of available networks for the open signal. So those lines may not be necessary. In fact, I suspect the only part that may have been necessary would be the header information (ap_scan=2 and all that), since Andriod just makes entries in the wpa_supplicant.conf file when you tell it to remember an access point. If its not already in the .conf file, it still shows up in your list of available AP's, it just doesn't remember it in your list.

Either way, thanks again to Shawn for figuring this out!
[Android Software/Hacking General [Developers Only]] joofeloof:
Much appreciated! Working fine, just fine...I was heading down this path anyway, more curious about how to get adb working than anything.

Many thanks.

Also, does or has anyone play[ed] around much with /proc settings?

I'm more familiar with linux server admin than any of the android specifics - but it seems like many of the kernel settings are readily configurable. I just don't know which would really be of interest in a tablet configuration/setting.
[Android Software/Hacking General [Developers Only]] whatid:
Now, my next question is.. anyway to enable Wifi channel 12-14? :)
[Android Software/Hacking General [Developers Only]] SilverFang83:
Worked Great. Thank you for figuring this out. Now I can make use of that 6gb data plan.
[Android Software/Hacking General [Developers Only]] Ms.Dummbunny:
Wireless Tether 3.1 Beta Supports ad-hoc

hey y'all....

just a heads up (and y'all might already have this info but jussssst in case there are ppl like me out there that read this thread and said, "um, maybe i don't need to have my LePan use my phone's network after all"...(lol) it seems the most recent version of wireless tether 3.1 beta i think http://code.google.com/p/android-wifi-tether/) supports ad-hoc. I just downloaded it, changed from "disabled to enabled" in Acess Control, and then "in CHANGE Device Settings" picked a phone like mine (they didn't have The Infuse but Galaxy S worked)

You might have to restart the Wireless tether ap but after it automatically showed my network on LePan. made a quick video on it here: http://www.youtube.com/watch?v=wACwGZ0XyuA&list=UU-xOxPoQXnvEQKqkucrM_Cg&index=1&feature=plcp

No matter what settings i tried on earlier versions of Wireless Tether it would NOT work, but the new 3.1 v8 Beta did : )

Anyway, i'm a little out of my depth here so if i have posted this in wrong place or if it doesn't directly correspond to the issue at hand, please forgive, just tryin' to help other numbnuts like me : )

Ms D
[Android Software/Hacking General [Developers Only]] BreeZyer:
Alright! Gave it a try with MyWi 4.0 on Iphone 4, can see the SSID and try to connect but fails to get an IP, goes to a loop of trying then scanning then trying to obtain IP. Oh well.

EDIT: made it forget network and re-entered password from settings, worked. I'll post the .conf file in a sec.

EDIT2:

Here are my settings for MyWi 4.0 using Iphone 4

--------------------

ctrl_interface=tiwlan0

update_config=1

network={

ssid="yournetwork"

key_mgmt=NONE

auth_alg=OPEN SHARED

wep_key0=yourkey

priority=4

mode=1

--------------------

The tablet should enter those for you when you first try to connect to your network, though.

GOOD JOB EVERYONE :)
[Android Software/Hacking General [Developers Only]] BreeZyer:
Now this is bizarre to me... The supplicant and the mods on the *.conf file works great, yet if I reboot the tablet, the *.conf file's permissions gets automatically modified to

X X 0

X X 0

0 0 0

thus causing an error on the wifi's startup.

I used Es file explorer to set the permissions and when I change 'em back, well everything works fine.

I'm quite puzzled atm.

Tried to use Terminal Emulator app to set the permissions with adb but I get a permission denied, and no SuperUser prompt :/ .. do you guys use adb from sdk via usb?
[Android Software/Hacking General [Developers Only]] ag2:
Help? Trouble with Barnacle

First off great work guys.

I never connected ad hoc before, and didn't realize I needed to root at first. I finally got it to see my droid eris' wifi network (thanks largely to Sandmonkee's step by step guide) using barnacle and to actually connect but as soon I try going to a webpage on the tablet barnacle freezes and then generates a boat-load of NAT:restart: network is unreachable errors.

What are you all using to broadcast the ad hoc network?

***EDIT

NEVERMIND, Ms.Dummbunny's solution worked for me too :)
[Android Software/Hacking General [Developers Only]] Rockin_Zombie:
I have been trying to do this for the past two days without success too. I have this permission problem. Plus, my tablet just shows "obtaining IP address" for a moment then disconnects. I am not trying to tether from my phone though, I have an old laptop with an intel 3945 card, trying to setup an adhoc network and connect to it. My SGS2 with MIUI works perfectly fine, so it is doable. Any suggestions what else I can try?
[Android Software/Hacking General [Developers Only]] whatid:
OK, this is sort of related...

I go Le Pan TC970 connected on Ch 12!

Base on http://xdaforums.com/showthread.php?t=1067944

I manually modified the settings.db and it sort of worked (Ch 12 only, and no go on Ch 13 for some reasons....)

Steps...

Copy /data/data/com.android.providers.settings/databases/settings.db to sdcard

Modify settings.db using SQLite "Manager" by adding extra row 116, wifi_country_code, EU in "secure" table

Rename /data/data/com.android.providers.settings/databases/settings.db to /data/data/com.android.providers.settings/databases/settings.db.bk just in case

copy the newly modified settings.db from sdcard back to /data/data/com.android.providers.settings/databases folder

Reboot

==

Update: WiFi Analyzer can see my AP when set to Ch13 too. But it can't connect, and I think maybe is my router....
[Android Software/Hacking General [Developers Only]] Sandmonkee:
Hey whatid,

Just curious - what is the advantage of having channel 12? Also, did you have to mod your router at all?
[Android Software/Hacking General [Developers Only]] whatid:
Depends where you are located, in Europe you can use Ch 12&13 and Japan with additional Ch14.

Some router will let you select Ch 12-14. Or if you have DDWRT installed.
[Android Software/Hacking General [Developers Only]] MadHarryRackham:
MsD...Thanks for the info. I tried this on my phone (Xperia Play R800X) and none of the phones in the list worked for me...but I did get a nice little interruption from Verizon in my browser about using my phone as a hotspot when I decided to give up and just opened my browser. It would not go away until I rebooted the phone...I'm guessing Verizon doesn't like tethering...lol
[Android Software/Hacking General [Developers Only]] Sandmonkee:
Hey whatid,

Thanks for the info. Are you using the unit in North America? If so, you might just want to double check the frequencies on some of the other devices in your house (phone, microwave, etc), as they are often very close to wifi frequencies (~2.4GHz). I know its unlikely to actually happen, but you could get crosstalk.

Also, would you consider starting a new thread with your method of unlocking these channels? I don't mind the info being here in this thread, I was just thinking it might make it easier for other people to find, and it is good info. Plus, the more we pollute the general forum with our TC970 stuff, the more likely they are to finally give us our own forum :)
[Android Software/Hacking General [Developers Only]] Sandmonkee:
Just as a heads-up, it looks like the new firmware (4626) will not support the mods described in this post. In a nutshell, if you upgrade to the new firmware, you will no longer be able to use the steps here to connect to an ad-hoc network.

I don't have any more info right now as to what we can do to get it working again, as my tablet is currently in the process of being exchanged for a new one :|