yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab General] TACY:
I like Google maps. I generally use the 3g to load the map and turn off data afterwards it works fine for me. If you search YouTube others have gotten this method to work quite far. The furthest I have tried it is about 100 miles.
[Galaxy Tab General] foxmeister:
Copilot is very good and probably the best value for money.

Regards,

Dave
[Galaxy Tab General] roy8846:
Please search the apps and themes thread.

There is a topic on this with a few mentioned ;)
[Galaxy Tab General] Digiguest:
Without a doubt the absolute BEST is CoPilot.
[Galaxy Tab General] Lucky_Charms:
I'm in agreement that copilot is the best offline alternative GPS solution.
[Galaxy Tab General] pwrsrc:
Not sure if its been said here before but I think CoPilot is the best bang for your buck.

Just USA costs under $10!

I KNOW IT WAS SAID BEFORE. IT IS A GOOD STANDALONE GPS APP thOUGH =P
[Galaxy Tab General] ukjeeper:
Co-Pilot on the road, Viewranger or BackCountry Navigator off the road.
[Galaxy Tab General] Digiguest:
Hmm....I never gave a thought to off road GPS. Thank you. Will try them out. :cool:
[Galaxy Tab General] lacion:
+1 on copilot, a bit more expensive here in europe, but i have to say that it works really well, gave my tomtom to my wife and now using the tab with the carmount for gps.
[Motorola Droid and Milestone General] jeffiphone:
I have a Telus Milestone that I just updated to Android 2.2 official and now I am looking to install Gingerbread on it.

Just wondered if there was an easy to follow guide to accomplish this, or if anyone could give me some help as I have never attempted anything like this before.

Thanks.
[Motorola Droid and Milestone General] sileshnair:
Flash VR and use AOR to apply CM7.

MM@Tapatalk
[Motorola Droid and Milestone General] jeffiphone:
Is CM7 better than the ShadowMOD ROM of Gingerbread?

I'm looking for something that is stable and speedy and without a lot of bugs.

Also, where do I begin?

I'm assuming that I have to root the phone first and then flash the ROM onto the phone?
[Motorola Droid and Milestone General] ccrows:
Looking for this info myself...
[Motorola Droid and Milestone General] sileshnair:
Well, You have to use both to see which suits you better. I would flash CM7 now and wait for Edgar to release his next version which is expected by the end of the coming week.

You need not root your phone. You need to flash the vulnerable recovery to be able to run Androidiani OR. Once you flash CM7, your phone will be rooted automatically.
[Motorola Droid and Milestone General] sileshnair:
Well, You have to use both to see which suits you better. I would flash CM7 now and wait for Edgar to release his next version which is expected by the end of the coming week.

You need not root your phone. You need to flash the vulnerable recovery to be able to run Androidiani OR. Once you flash CM7, your phone will be rooted automatically.

You can also try FroyoMOD, Ice&fire ( based on CM7 ) and HONO's mod ( based on CM7 )
[Motorola Droid and Milestone General] awarbrick89:
Umm, pretty sure we cant use CM7, cause it changes the kernel or something

I just used Androidani Open Recovery or whatever its called to apply the CM7 and it temporarily bricked my phone, thankfully i did a nandroid backup and its rebooting as i type, whew
[Motorola Droid and Milestone General] sileshnair:
What do you think about this thread? And what do you mean by temporary brick? :confused:
[Motorola Droid and Milestone General] akki4p:
Check my post

Hi,

I have made a small series of videos doing just that, check this post

http://xdaforums.com/showthread.php?t=1008044
[Motorola Droid and Milestone General] jeffiphone:
Just wondered if all of this is safe, or if it opens up your phone to security risks, such as when people jailbroke their iPhones and didn't change the root password.

thanks
[Motorola Droid and Milestone General] jeffiphone:
Can anyone offer any insight on the security risks of installing Gingerbread on a Milestone?

thanks
[Motorola Droid and Milestone General] skadude66:
As far as I know, there aren't any glaring security risks that have been discussed at all. Seeing as Gingerbread is really just based off of the 2.2.1/2.2.2 kernel, I don't see any risks associated.
[Motorola Droid and Milestone General] jeffiphone:
Thanks for all of the help guys, but I have decided that it may just be too much for me.

I had an original iphone which I jailbroke and installed apps on, but that was years ago. Ever since then I hadn't really messed around with hacking my phone and now I am hesitant to start again, especially with a new os.
[Motorola Droid and Milestone General] skadude66:
All of the tutorials in the development forums are fairly straightforward. Also, I have compiled a tutorial ZIP that I have given to a few people, if you want. I made about 40 steps from start to finish. It's up to you.
[Motorola Droid and Milestone General] jeffiphone:
Really thought that Gingerbread would rekindle some interest in me for my Milestone, but I think I am gonna trade it away especially sine I have my Nexus One
[Motorola Droid and Milestone General] zeppelinrox:
40 steps?

Well I guess all the little baby steps included but basically,

1. Put AOR on sdcard with cm7.

2. Flash vulnerable recovery

3. Load AOR and flash cm7.

edit: 4. Add V6 SuperCharger as an upgrade option... lol

bazinga!
[Motorola Droid and Milestone General] skadude66:
Yeah, all of those little questions that you think people never ask but do? They're in there :P

Bazinga!
[Motorola Droid and Milestone General] zeppelinrox:
Why do you think my script is over 800 lines? :D

Actually, 847 at the moment... (reformatting to 40 columns and tweaking a bit)

That reminds me I gotta send you a PM
[Motorola Droid and Milestone General] neato4u:
Come on.. nothing is too hard mate! If you can pass your school exams, these will be a piece of cake! Just that you need some spare time, and an internet connection for you to post back to XDA just in case it didn't work out very well.. :D now don't be scared, the chances are very unlikely if you read and follow all the instructions properly.
[Motorola Droid and Milestone General] sys6x:
I'd be interested by that zip if you still got it!

As of now, I'm confused about the Telus Milestone on 2.2.1, are there issues to root it or not?

What version is your cm7? latest build I saw was 2.3.7 but I don't know if its telus-friendly...
[Motorola Droid and Milestone General] zeppelinrox:
Check the sticky threads for all the tiny details:)
[Motorola Droid and Milestone General] dsac:
i've got a telus milestone and am running ice and fire/Ultimate Milestone (based on 2.3.7).

i've tried CM7 (stock), HONO, and I&F, and the one i'm running now is far and away the fastest.
[Android Software/Hacking General [Developers Only]] manialith:
is it possible for me to install Android on my pda Asus P526.

it has windows mobile 6.1 on it.

i dont know if android is suitable for my phone.

any comment shall help.

with regards :)
[Android Software/Hacking General [Developers Only]] shad0wboss:
you should really google things like that before actually making a thread ans waiting for someone to answer !

How to dual boot android and windows mobile.

Android on windows mobile youtube video
[Xoom Android Development] Xaositek:
This is it guys... HUGE props to bigrushdog (his kernel made this possible!), MADindustries and modplan!

Download the Motorola WiFi Xoom Root Zip file and unzip it. (MediaFire) - Contains Tiamat 1.3.1

You need the Moto Drivers - Read this thread to START you - http://xdaforums.com/showthread.php?t=981578

You'll need fastboot - get it here http://developer.htc.com/adp.html

Make sure you have the latest SDK - adb and fastboot should be in /platform-tools - http://developer.android.com/sdk/index.html

Place the files in the SDK Tools folder.

If rebooting works... -

This will wipe your phone by the way!!

adb reboot bootloader

fastboot oem unlock

adb reboot bootloader

If stuck at "Dual Core Technology"

Hold VolUp and power to restart Xoom

Hold VolDown will booting unit for fastboot mode

fastboot flash boot boot.img

fastboot reboot

adb shell

mkdir /data/media/sdcard2

exit

(physically put in microSD card if you are planning to use)

adb reboot

adb remount

adb push bcm4329.ko /system/lib/modules/bcm4329.ko

adb push cifs.ko /system/lib/modules/cifs.ko

adb push tun.ko /system/lib/modules/tun.ko

adb push scsi_wait_scan.ko /system/lib/modules/scsi_wait_scan.ko

adb push su /system/bin

adb shell ln -s /system/bin/su /system/xbin/su

adb shell chmod 4755 /system/bin/su

adb push Superuser.apk /system/app

adb push vold.fstab /system/etc/vold.fstab

adb reboot

adb shell

WE HAZ ROOT!!

Check out this video for basic Windows walkthrough from Buddhahb - http://www.youtube.com/watch?v=ZsVpY0PDwtQ

Check out this video for basic Mac walkthrough from sleeplessninjas - http://www.youtube.com/watch?v=zC6J-hV6SM4

Update: 3/27/2011 12:04pm CST Added cifs.ko, tun.ko, and scsi_wait_scan.ko

Update: 3/27/2011 12:22pm CST Added vold.fstab file for USB mounting & MegaUpload

Update: 4/13/2011 10:07am CST Updated to Tiamat's 1.3.1 kernel for SD card support & Gallery support.
[Xoom Android Development] onicrom:
awesome work guys!
[Xoom Android Development] bwcorvus:
Woooooooooooooooooooooooooot
[Xoom Android Development] -shift-:
fantastic work!! :D

\o/
[Xoom Android Development] onicrom:
can you try the cifs.ko module as well? i have a 3g version and am curious
[Xoom Android Development] ericdabbs:
Thanks Xaositek and HUGE props to MADindustries and modplan for coming up with a quick solution.

Is there a rip of the stock "boot.img" in case it doesn't work so that people who soft brick their xoom can return it back to stock? If so can that be posted in the OP's post? I know I am not the only paranoid one that would like to have the stock boot.img before attempting any rooting.

Also just for curiousity, can someone explain the differences between the wifi and wifi+3g boot.img versions and what they had to do to workaround this. Thanks.
[Xoom Android Development] Xaositek:
We end up replacing the stock boot - We'll probably need to wait for Motorola to toss us a bone there
[Xoom Android Development] ericdabbs:
I just downloaded the "xoomwifiroot.zip" file and realized the files in the "xoomwifiroot.zip" are just tiamat's 1.1.6 files (boot.img and kernel modules) that can be found in tiamat's thread.

I was expecting the files to be something different that was close to the original root method by Koush where there is a "rootboot.img".

Maybe a better question for my understanding is this. Sorry if I am a noob.

Is Koush's file rootboot.img for the original xoom root only good for rooting the system while tiamat's boot.img file not only roots the system but also has code to overclock the xoom?
[Xoom Android Development] Xaositek:
It also has the su and Superuser.apk but essentially yes...

Koush's rootboot got us into this mess, Tiamat's boot.img got us out of it. It also allows the critical adb remount to allow the next steps.
[Xoom Android Development] ericdabbs:
Gotcha. Thanks for all your help.
[Xoom Android Development] Xaositek:
Grab the latest file from MegaUpload and add the additional modules :D
[Xoom Android Development] modplan:
glad I could help get this working and glad that it fixed my bricked xoom! One thing that I would suggest is someone pull the stock ko files and save them, after moto releases the stock boot.img files I am sure that there will be some people that want to go back to the stock kernel which will then be as easy as flashing the stock boot.Img and then pushing the stock ko files back on.
[Xoom Android Development] rootmepls:
Guess I'll run out and grab one now at Best Buy then. :) Thanks!
[Xoom Android Development] ericdabbs:
Is there a way to extract the stock boot.img and wifi ko files before flashing it with tiamat's files? If so, what are the instructions so that people who haven't rooted it yet can give it a try. That way we can give back to the community.
[Xoom Android Development] modplan:
Pulling the boot image looks like it is rather difficult but pulling the ko files should be as simple as using the adb pull command instead of adb push. For example

Adb pull /system/lib/modules/something.ko c:/something.ko (put the right paths obviously the second path is just where you want to save it on your computer)
[Xoom Android Development] d3coy3d:
As an FYI. coolbho's ocboot.img does not work on the wi-fi version of the xoom yet. To prevent your headaches I have already flashed and it stays at boot screen. Tiamat's seems the only kernel that is working for wi-fi only
[Xoom Android Development] ericdabbs:
Got it. When I get my wifi xoom, I'll give this a shot.
[Xoom Android Development] Xaositek:
Tiamat's kernel allows for the 1.5ghz OC
[Xoom Android Development] chaz03:
When i command to push the first file, I get all the info on android debug.
[Xoom Android Development] Xaositek:
Revisit the instructions now - you can just copy and paste them all now
[Xoom Android Development] jaa93997:
This is what happende to me

Hello, first of all, i want to say good job dev dudes!. This is my case. I followed to the letter the rooting tutorial. Superuser did appear on my zoom´s drawer. I purchased a while ago the superuser elite app from the market. So i just went ahead and install that too. What happened is, that no root-requiring app asks for superuser permissions when opened, hence they do not run. I uninstalled the superuser elite app, and now every time i open the superuser app it says there is a new version of su available, and after clicking accept, it returns an automatic update failed error screen. Since then i upgraded to HC 3.1 and flashed tiamat 1.4.4. Everything elese runs ok. Any ideas?
[Xoom Android Development] andrewmc42:
First off, I am a total noob at this stuff and don't know Jack, mostly, but I can follow instructions very well.

I am not sure what I have done wrong, but when I try to flash the boot.img or recovery.img from fastboot I get this error message.

FAILED <data transfer failure <Too many links>>

I tried to re-run the fastboot oem unlock command and got a failure on that also, but I presumed that it failed because I had already run it.

I am using a Windows 7 Professional 64bit machine with the all of the drivers, Java SDK and Android SDK updated. I have access to a Ubuntu 11 machine, but I did not see instructions for what to do in Linux and I am not savvy enough to figure it out. I did try to search the thread but did not find an answer. Any assistance would be appreciated.
[Xoom Android Development] playya:
Have yo tried any other root method publicanimals method of loading as record dry then flashing aa rooted zip file might be perfect for you at this moment. Not saying this method does not work but you may be at a crossroads
[Xoom Android Development] andrewmc42:
I have not tried any other methods. I am a bit hands on and prefer to have more control than the one-click methods offer. When I first rooted my Evo, I used adb for everything and had no problems. Maybe I should re-lock the bootloader and then unlock it again, I dunno. I will look for that method first.

EDIT: I checked on that method, I get a command write error when I try to flash the recovery image, using the img file.
[Xoom Android Development] okantomi:
I used this method to unlock and root prior to the upgrade to Honeycomb 3.1.

So I think this method (boot.img, etc) is for HC 3.0. If you are already at 3.1, you need to use this method:

http://xdaforums.com/showthread.php?t=1130996
[Xoom Android Development] andrewmc42:
Problem is that I can't flash a recovery image or boot image. Without recovery, I can't use his method either. I will figure it out eventually, or brick it in the process...LOL
[Xoom Android Development] okantomi:
If you follow this method, you will see in step 4 you will install CWM recovery which will allow you to flash a .zip from the sd card.

See below:

1. Install Motorola USB drivers for your computers (for USB connectivity)

2. Install Java SDK and Android SDK tools (for adb and fastboot commands)

3. Unlock the device for flashing (allowing replacement of recovery and boot images)

4. Install a modified recovery image (ClockWorkMod recovery for Android)

5. Root the device (Allow r/w access to the device filesystem)

6. Flash a kernel that supports the SD card (SD card access, overclocking etc.)
[Xoom Android Development] andrewmc42:
Yes, I would have that happen if I did not get the Failure <Command write error<Too many links>>. If I did not get that I would already have this done, I don't understand what is causing the error and it shows up if I try to flash either the recovery or boot images. It is an odd error and doesn't allow be to do anything. I also cannot reboot from the fastboot screen. None of the reboot commands work.

Edit: I relocked and then unlocked it again, now I get a <00120003> error, and a failed when I try to flash an image file from fastboot.
[Xoom Android Development] okantomi:
Do you get any recovery options at all? You probably shouldn't have relocked....that's been known to brick a wifi only Xoom. But don't despair...people have brought their Xooms back from pretty dire situations, it's actually hard to destroy.

Read this thread, it may offer some solutions: http://xdaforums.com/showthread.php?t=1152121

So, if you press vol+ and power, then 3 seconds after the dual core screen comes up, you hit vol- and then vol+, what happens? If you get any recovery options, that's a good thing.

You may also want to go to Freenode, #Xoom to chat with the experts. I'm sure they can help you there.
[Xoom Android Development] andrewmc42:
I can get into a recovery, but, as it turns out, I think I have a bad USB cable or something. I could not transfer files normally, after I got it back from a persistent boot failure. The whole thing is a bit odd and I am not sure its actually a software thing. Gonna keep pluggin at it and see what I get.
[Xoom Android Development] okantomi:
I wish you good luck. Also, this is kind of a dead thread so you might get more help if you post on one of the livelier threads (appropriate, of course).
[Xoom Android Development] andrewmc42:
I finally got it all worked out. Thanks for all your time guys.
[Xoom Android Development] okantomi:
So glad to hear it! Have a happy Independence Day.
[Xoom Android Development] clickclickpc:
Thanks so much for pointing out the difference of 3.0 vs. 3.1. Here's the boot.img (for 3.1) quoted from your thread that allowed me to get past the Dual Core screen. Rename extension from .apk to .img first. Then just fastboot flash.
[Xoom Android Development] rash.m2k:
Does this delete stuff from the internal 32GB memory? Or just the apps? Will rooting it delete my documents and stuff?
[Xoom Android Development] gaarak54:
I was feeling good about this and everything was going great til I pushed the boot.img. Now it just stays on the Dual Core screen. What do I do now? It was running JB 4.1.1 when I got it from a guy on CL. This really sucks because I just unlocked it and pushed a recovery and was ready for root and now it's stuck.
[Xoom Android Development] wesamothman:
This guide should help you.

http://xdaforums.com/showthread.php?p=29733454
[Xoom Android Development] mundia:
I unlocked and rebooted to stock Jellybean ver 4.1.1 build JR003H

do i need to flash down to HC inorder get root? Do i need to have mSD card loaded with (which) files to root?
[Xoom Android Development] blocka:
Hi,

I've followed the procedure, and after flashing the boot image and then rebooting "fastboot reboot" it looks as though the Xoom hangs at the Dual Core Boot Screen. I went over to http://xdaforums.com/showthread.php?t=1812943&highlight=stuck. Installed TWRP custom recovery, followed the process to boot into the recovery and it's hang on Reading ODM fuse: 1.

Any help to clear the boot hang would be great.
[Xoom Android Development] notbrodie:
way resurrect a dead thread! reflash twrp from fastboot. then type

fastboot reboot

after it reboots, go into recovery mode and flash the latest superSU zip. no other steps are required. this is way out of date
[Xoom Android Development] blocka:
Cheers man that did the trick NP! Thanks.
[Xoom Android Development] chaz03:
Ok thats what I have tried.

c:/android/tools/adb push bcm4329.ko /system/lib/modules/bcm4329.ko

Then i get:

cannot stat. ..... no such file or directory. I clearly see these files on my pc
[Xoom Android Development] Xaositek:
c:/android/tools/adb push (full path to file here)\bcm4329.ko /system/lib/modules/bcm4329.ko
[Xoom Android Development] PaulG1488:
All the files your pushing need to be in the same folder as adb
[Xoom Android Development] bigrushdog:
I was on these boards around 5:45 AM PST telling folks to flash my kernel. I glad everyone FINALLY figured it out lol.:rolleyes: :rolleyes: :rolleyes:
[Xoom Android Development] modplan:
brd,

I love the kernel since it saved my xoom :-) can you please tell some of us what the pros and cons are for your kernel? on phones I have always been a guy that rooted and flashed roms but never flashed kernels before. is there anything that the stock kernel does better? is the stock one more stable? is this one based on the stock kernel?
[Xoom Android Development] chaz03:
Thanks! worked
[Xoom Android Development] Xaositek:
Yep yep - we had a couple people test it, then we had to get everything in the right order and *BAM* we have a finished root procedure. Thanks!!
[Xoom Android Development] bigrushdog:
Here's how it works. Stock kernel and Tiamat, or any other custom kernel, come from the same source. For the most part... Folks are updating the source on a regular basis, but you don't get OTA's everytime source is updated. Also, you don't get overclock, or all the addon modules with stock.
[Xoom Android Development] chaz03:
adb shell ln -s /system/bin/su /system/xbin/su

adb shell (Full file path here)\ chmod 4755 /system/bin/su

same goes for these correct?
[Xoom Android Development] modplan:
Ok that is what I wanted to know. Cool that they come from the same source. Are there any features that are not in urs that are in the other one that is currently only for the 3g version or does yours have everything that one does?
[Xoom Android Development] Xaositek:
You can do this... same end result.

adb shell

ln -s /system/bin/su /system/xbin/su

chmod 4755 /system/bin/su
[Xoom Android Development] chaz03:
Do I put the file path anywhere in there?
[Xoom Android Development] Xaositek:
No the files are already on the tablet at that point.
[Xoom Android Development] chaz03:
When i type the command for adb shell as you posted, I get Link failed File exists
[Xoom Android Development] ke5hde:
Xao, good to see you got this going. Finally got back with my replacement. May just have to give it a try later.

Chris
[Xoom Android Development] chaz03:
Anybody help? Im unable to run the ln -s /system/bin/su /system/xbin/su

command succesfully. I get Link failed File exists
[Xoom Android Development] Xaositek:
Are you within ADB SHELL?? Sounds like you already completed that step then?
[Xoom Android Development] ericdabbs:
Just curious, if I decide not to push the superuser files, can I always just download superuser from the android market? Would that be doing the same thing?

The reason being is that I might be interested in buying superuser elite to support the developers but they also said that they will provide more features than those who just use regular superuser.
[Xoom Android Development] cavemanb:
When the files are placed "in the SDK tools folder" ,,, would they be placed in the platform-tools folder when using Windows 7 64-bit.....

This is where I run my ADB command from.. or do you place them in the main tools folder under the main sdk folder...

thanks
[Xoom Android Development] chaz03:
Having the # would indicate that correct?

I typed adb shell

then get the #

So i would not need to type the next command:

ln -s /system/bin/su /system/xbin/su
[Xoom Android Development] modplan:
run:

adb shell

rm /system/xbin/su

ls -s /system/bin/su /system/xbin/su