yashsingh1/xdaforums huggingface dataset:
[Galaxy Note II Accessories] liviococcia:
Thanks for the links, but it's a OTG adapter with an extra USB male plug just for supplying 5 v power, reading a lot about making something up, but in short these modded adapter cables don't work with any certainty (something about not finding the nominal resistor value across pin (ID) 4 & (Ground) 5, which means either the phone goes to charge mode, but doesn't see the USB item that's been connected, or the reverse).

I thought the new Samsung Note 2 Smartdock might work, but it's been found to not see USB audio DAC's when there plugged in, unless someone knows different but I'm guessing the dock already takes the audio signal from the phones USB and feeds it to a 3.5 mm headphone socket in the unit.
[Galaxy Note II Accessories] knight900:
Ebay have tons of them....

http://www.ebay.com.sg/itm/Micro-US...Accessories&hash=item20cdc2cc21#ht_3873wt_906
[Galaxy Note II Accessories] liviococcia:
Thanks knight900, but I wanted to buy the item from anywhere other than ebay, the reason, well in the past whenever I made a purchase from this type of location/trader there was always fraud instigated on my PayPal account.

I might still consider buying from Ebay if other forum members have purchased the same item from a particular Ebay seller with no issues.
[Sony Xperia P, U, Sola, Go] :
Anyone knows how to port a ROM based on ICS for unlocked bootladers only to locked bootladers?
[Sony Xperia P, U, Sola, Go] ajshafiraa:
What rom do you want to port?
[T-Mobile, Samsung Galaxy SIII] TheKid1:
Yea, I know my windows version on my pc is old, but are there any videos or anything using the tool kit with windows xp?
[T-Mobile, Samsung Galaxy SIII] mt3g:
They all work for me on my computer which has XP
[T-Mobile, Samsung Galaxy SIII] TheKid1:
Oh ok. After reading about rooting our phone, Im confused about the whole "kies" thing. There is a stock "kies" app that came installed with my phone. So does that mean I have to go through that whole driver issue? Can someone explain this process a little further if so?
[T-Mobile, Samsung Galaxy SIII] vopezy:
Your probably thinking of Samsung Kies for the computer. Windows version does not matter.

You do not need Kies if your going to root just download and install the ones they tell you in the post your reading.
[General Questions and Answers] Joshgav:
Edit: Delete post as I tried one last thing which worked.
[General Questions and Answers] Clark Joseph Kent:
Problem solved, Good To Go!

Thread Closed & Thank You
[Android Q&A, Help & Troubleshooting] Subash036:
Just dial *#36# and select proximity test just test of two to three times its in chinees dont bother just chaeck thn go back you done......enjoy
[Samsung Epic 4G Touch] Amd4life:
please dont close, as im not listing anything, but I am curious, for those with good online references (like myself)

I'm upgrading the family lines tonight for Black Friday, so I have 4 phones to get rid of 2 epic (the slide keyboard version) and 2 epic touch 4G, since the XDA marketplace is closing where are members selling phones too, or it it just back to ebay (hate the fees) or craigslist (hate the theft risk)?
[Samsung Epic 4G Touch] BluesRulez:
Amazon?
[Samsung Epic 4G Touch] hrffd:
Craigslist. Shouldn't be a theft risk if they hand you the money first and you do it in a public place.
[Samsung Epic 4G Touch] milky1112:
Craigslist for sure.. I buy and sell alot on there... Can get a few bucks for them atleast.
[Samsung Epic 4G Touch] Amd4life:
guess Ill try craiglist then, meet at a sprint store or something.

what exactly happened to the marketplace, did too many people get scammed or something? never understood why heatware or itrader was not mandatory to sell online, say no less than 10 positives, and no negatives or something

or is that not something we can ask??? never know what threads get closed these days
[Samsung Epic 4G Touch] MoHoGalore:
Good Info for your question:

http://www.xda-developers.com/announcements/the-xda-marketplace-is-closing-for-now/
[Samsung Epic 4G Touch] acejoker25000:
Swappa.com it's also a good one

私は神の罰です。
[Samsung Epic 4G Touch] naripsta:
Craigslist..

Agree to meet at a Sprint store, or in a very public place. Oh, and I usually bring a friend with me for most of my Craigslist transactions. Only negative about it is, you gotta deal with your usual lowballers.
[Samsung Epic 4G Touch] Mattix724:
Craigslist.

If you live somewhere like AZ, Carry a gun.
[Samsung Epic 4G Touch] trifthen:
Swappa seems to be the place to hawk phones these days. According to their E4GT page, our phone is worth roughly $200 - 220 right now. If nothing else, that should give you a number to shoot for while using craigslist.
[Xoom Android Development] iruiz2:
The Kernel

This is the part that is weakest on this second thread on the BT5 for the Xoom. Please anyone with more knowledge than me, correct me here. It seems that the kernel has to be compiled with certain code to be able to use the modules that enable us to use injection capabilities. It was originally compiled by Bigrushdog for Honeycomb, and later for ICS, but not for JB due to time constraints.

What we have at present:

The boot.img needed for the overlay is composed of 2 parts: the kernel, and the ramdisk. What we have now in the overlay5 is the ramdisk from JB 4.1.2 mixed with the ICS kernel compiled for module-compatibility. It is not ideal, but it works.There are several threads on how to unpack and pack boot.img files using your favourite kernel and ramdisks, so I will not go into that here (I used instructions in this xda thread and I got it the first time).

What we need:

A fully JB 4.2 (and 4.1.2 ideally) compiled kernel (and how to do it). This is work in progress, and every bit of help is appreciated here.You can contribute on the thread, or by PM to me, and I will keep updating this section until we get a fully working guide.
[Xoom Android Development] iruiz2:
Tools

ConnectBot for Honeycomb
​

Grab it here . Much credit and thanks to arctu for putting this together. You can have many shells open and easily access them for processing jobs​
[Xoom Android Development] krankdroid:
This is so freaking amazing. Can't wait for the rest of the process.

I will flash bt5 and the overlay tomorrow so i can be ready to compile the kernel once the instructions comes up.

Thanks again for taking your time to continue the work on getting it on JB..

Sent from my Xoom using huge amounts of internets
[Xoom Android Development] iruiz2:
If you are running JB, don't flash the ICS overlay, wait a couple of days for the JB instructions! Patience...
[Xoom Android Development] XxLordxX:
Waiting for it :) Amazing work dude!

"This Story Ends Where It Began"
[Xoom Android Development] iruiz2:
Well, the JB instructions and files are now up. I was able to "cook" up a 4.1.2 compatible boot.img mixing the ramdisk of EOS nightly 155 and the ICS kernel from bigrushdog's overlay4. It does work, and it will have to hold until I learn to compile from scratch a 4.1.2 kernel.

Thank you to Trevd for the idea (mixing ramdisks and kernels from different sources), and Mjamocha and Bigrushdog for the work on this.

Enjoy!!
[Xoom Android Development] keywar18:
You have the steps twice

​
[Xoom Android Development] iruiz2:
One is if you are running ICS, the other set if you are running JB. I thought it was clear in the OP.
[Xoom Android Development] XxLordxX:
Downloading to test it :)

thanks for the hard work on it ;)

"This Story Ends Where It Began"
[Xoom Android Development] XxLordxX:
So, I installed the BT5 on my Xoom, flashed everything in the correct order and I didn't get past the "Motorola" logo at the boot screen. I was thinking a little and concluded that maybe it's because of the lack of free space on /system of JB, I may help you finding a work around about it, just didn't post logcat because I'm on my way to school and have no PC here :p... BTW good luck with your project :)

"This Story Ends Where It Began"
[Xoom Android Development] iruiz2:
What ROM are you using? Have you installed anything else on system? I have just flashed everything one more time and it boots fine here. What I did:

Wipe cache, dalvik and system.

Flash Team EOS 155

Flash Eos Gapps 0802

Flash overlay5

Reboot

I didn't flash the script updater again, you only have to do it once but it changes only one file in the BT5 folder.

After booting, I've got 2.36 Mb of free space on /system. Quite tight, you are right, but enough on EOS 155.
[Xoom Android Development] krankdroid:
I am wondering about something here, and I am thinking my question here will end up as d'oh moment for me.

The tutorial mentions the team EOs 4.1.2 ROM. All I can find, both stable and nightlies Team EOS wingray ROMS, are 4.1.1

Am I missing something here?

Edit:

well. it seems that the latest EOS 3 nightly buils is 4.1.2. This is not mentioned anywhere i could see in the EOS Wingray thread. Just flashed the 155 build and there it was. 4.1.2.
[Xoom Android Development] XxLordxX:
I'm using Team EOS nightly 124 (because I'm using a 3g ROM), I wiped the cache and flashed everything... Now I deleted some files on the /system/ like live wallpapers and videos, I'm up to 15Mb free now, the problem I think happened is that, as I'm on a 3g ROM there are many modules that aren't on WiFi only ROM. Will try again soon ;)

"This Story Ends Where It Began"
[Xoom Android Development] XxLordxX:
Iruiz how much space do you have before flashing?

"This Story Ends Where It Began"
[Xoom Android Development] iruiz2:
I think it has more to do with the Android version, what are you running in eos124?

I suggest you follow the instructions in the second post regarding how to mix a ramdisk from your boot.img and the overlay5 kernel. That should work, let me know how it goes...
[Xoom Android Development] krankdroid:
for injection, i belive that any wifi adapter with Realtek 8187L chipset can be used right ?

even the chinese cheap non-brand have paid for blueprints to produce wifi adapters containing realtek 8187L chipsets as far as i know, so they should work just as well i am guessing. i will find out soon enough any how.

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

i too have encountered the same sort of boot loop after flashing according to the tutorial, after mimicking the enviroment you described with same version nightly build and all. i maneged to get it booted, but i do believe that something had messed around in the framework, all gapps would insta crash, and upon sleep it would go back to boot animation loop.

i will try to clear out some stuff from /system tomorrow as well and see if that works.
[Xoom Android Development] mylegiscramped:
Will test in the coming days when I have some time.

Great work y'all! Much thanks to you. Your work is greatly appreciated.

Idk if Bigrushdog is on this thread, but thanks for being an initiator I know you put a lot of effort and work into the things you do and its at least greatly appreciated by me if not many.

Iruiz2 if y'all think I can help with anything let me know! Thanks again for your awesome work, and look forward to some aireplay in the near future :)
[Xoom Android Development] iruiz2:
About rtl8187 cheap versions, I had one that would work on my computer but not on my Xoom, but after I bought an original one I had no problems, just for you guys to know.

About the install instructions, did you follow them to the letter, and if you got into a boot loop, how did you get it to boot? What ROM did you have to start with?
[Xoom Android Development] Mjamocha:
Be weary of cheap knock offs, you will not get the same results.
[Xoom Android Development] krankdroid:
good deal. i will get the ALFA too then.

i did follow the instructions to the letter. i full wiped and flashed the 155 EOS 3 nightly and the Gapps version you mentioned.

i will dig around and see what i can remove from /system

i am thinking some boot animation videos and live wallpapers. And then i will try again.

from the desciption, i assume that the overlay already contains a boot.img, although it might be dirty. And that the second post is in case i want to mix and match kernels and ramdisks right ?

edit: well.. tried again today. first on a slightly edited version of the EOS3 155 ROM, i deleted a few Boot animation videos and the likes. not much more room but still a bit. no luck. tried full wipe, wipe dalvik cache and flash BT5, EOS3 155, Gapps 0820, BT5overlay and then scripts.

i get boot. but all gapps force quits on start up and when trying to open them. and constant random reboots.
[Xoom Android Development] Mjamocha:
Gave overlay5 a go, it boots up but gives random reboots there after. Once into the a Android terminal (not a fan of ConnectBot) / su into root/bt5, any terminal command input shuts down the wifi and reboots, (I'm on Stingray EOS 150) I restored my backup. Will take a look at logcat.
[Xoom Android Development] iruiz2:
For those having problems, try formatting /system (also cache and dalvik wipes, of course) before installing the ROM, gapps, and the overlay5.

On a wingray, with eos155 no problems whatsoever.

Everyone is having problems, or are there successful installs?
[Xoom Android Development] krankdroid:
i have tried every combination back and forth. the end result is pretty much the same. either i get every com.android process fc one after another or i get every single android feature like calendar, camera and the works fc on me. after then hitting "ok" about 15 to 20 times, it reboots. updates apps. reboots. same fc's. rebbot at random constantly.
[Xoom Android Development] Mjamocha:
What is your device model? Is it an GSM xoom Everest or a U.S. Xoom?
[Xoom Android Development] krankdroid:
Motorola Xoom MZ604 32gb
[Xoom Android Development] Mjamocha:
After some testing, The O'5 killed the Data on the Stingray 3G/4G devices that were tested. Quite possibly the result of taking snippets from a Wifi Only device Boot image, not sure. Question is, how can we make this cross compatible for the diff Xoom models? Did a restore, used the awesome repack tut. link the OP provided, pushed a different modified boot.img which is suited for Stingray. (I only have the modules that I use loaded, it takes up less space). The kernel is dirty, which is fine (most kernels like these are a bit dirty, not a big deal) as long as everything loads correctly at boot.

In the dmesg, device info should be listed below the kernel info, the dirty portions later towards the end of the log. The

dmesg

should look similar to this:

dmesg-

[B]sh-4.1# dmesg[/B]
<6>[ 0.000000] Initializing cgroup subsys cpu
<5>[ 0.000000] Linux version Tiamat-3.0.9_Mjamocha_1337_pWnR_h4xR_pack+(bigrushdog-Latitude) (gcc version 4.4.3 (GCC) ) #98 SMP PREEMPT Thu Mar 22 02:55:21 PDT 2012
<4>[ 0.000000] CPU: ARMv7 Processor [411fc090] revision 0 (ARMv7), cr=10c5387f
<4>[ 0.000000] CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
<4>[ 0.000000] Machine: stingray
<4>[ 0.000000] Ignoring unrecognised tag 0x41000810
<6>[ 0.000000] powerup reason=0x00020000
<4>[ 0.000000] WiFi MAC Addr [4] = bla bla bla
<4>[ 0.000000] XX XX XX XX XX XX
<6>[ 0.000000] Found tegra_fbmem: 007d0000@1e018000
<6>[ 0.000000] Reserved 1ff00000@00100000 for ram console
<6>[ 0.000000] Tegra reserved memory:
<6>[ 0.000000] LP0: 1e7f1020 - 1e7f301f
<6>[ 0.000000] Bootloader framebuffer: 1e018000 - 1e7e7fff
<6>[ 0.000000] Framebuffer: 2e800000 - 2effffff
<6>[ 0.000000] 2nd Framebuffer: 2f000000 - 2fffffff
<6>[ 0.000000] Carveout: 30000000 - 3fffffff
<6>[ 0.000000] HACK: Old framebuffer: 1e018000 - 1e7e7fff
<4>[ 0.000000] Memory policy: ECC disabled, Data cache writealloc
<7>[ 0.000000] On node 0 totalpages: 189952
<7>[ 0.000000] free_area_init_node: node 0, pgdat c072ba40, node_mem_map c0973000
<7>[ 0.000000] Normal zone: 1536 pages used for memmap
<7>[ 0.000000] Normal zone: 0 pages reserved
<7>[ 0.000000] Normal zone: 188416 pages, LIFO batch:31
<4>[ 0.000000] HighMem zone: 512 pages exceeds realsize 0
<6>[ 0.000000] Tegra Revision: A02 SKU: 8 CPU Process: 0 Core Process: 0

BT5-

[B]sh-4.1$ export PATH=/data/local/bin:$PATH[/B]
[B]sh-4.1$[/B] [B]su[/B]
[B]sh-4.1# bt5[/B]
[COLOR="blue"]Mjamocha, You Are Now Initializing Backtrack 5 for Xoom 4G LTE on Jelly Bean 4.1.2
We are now Entering BT5 chroot *****ES... Welcome To The Pawn Shoppe!
Loop device exists
Backtrack 5 Image Is Mounting...The Pawn Shoppe Is OPEN![/COLOR]
[COLOR="Red"][B]net.ipv4.ip_forward = 1[/B][/COLOR]
[B][COLOR="red"]root@localhost:/#[/COLOR][/B] [COLOR="Black"][B]cd /root/Desktop[/B][/COLOR]
[COLOR="red"][B]root@localhost:~/[/B][/COLOR][COLOR="black"][B]Desktop# dir[/B][/COLOR]
[COLOR="blue"]a.sh cracked.txt maclist reaver-1.4 wifite.py[/COLOR]
[COLOR="red"][B]root@localhost:~/[/B][/COLOR][B]Desktop#[/B]
[Xoom Android Development] iruiz2:
If you don't want to get into kernel stuff, I could cook one for stingray if you send me the latest eos rom boot.img, you said it was the 150? This way we can be certain if I am doing something wrong here or not.

Sent from my Xoom
[Xoom Android Development] iruiz2:
That's mine, it should work on that one, that's a Wingray!

Sent from my Xoom
[Xoom Android Development] Mjamocha:
Nothing here is wrong, it a learning experience for everyone especially me. I'm trying to figure out what could have killed my LTE data, and what did our predecessor do to make it cross compatible.

Boot Stgry 150
[Xoom Android Development] krankdroid:
exactly. i saw in your signature.. that is why is puzzles me so that it is not working. and it is also why i did go to great lengths to mimic the enviroment your have running with same version gapps and EOS nightly build.

what would be the best use of logcat to help pinpoint the problem ?
[Xoom Android Development] XxLordxX:
@iruiz I really think my problem is the /system maybe some others too, I just flashed CM10 ROM with nothing on the /system/ and it ended up with 860Kb free, maybe because of the 3g modules, on the weekend I may test with a WiFi only ROM.

"This Story Ends Where It Began"
[Xoom Android Development] bigrushdog:
It's the ramdisk portion of boot image. Specifically its the command line. You should publish a stingray boot image. It should work with wingray just fine.
[Xoom Android Development] iruiz2:
I will do that. Thanks for keeping an eye on us :silly:
[Xoom Android Development] iruiz2:
Well, with /system THAT full sure you are going to have problems with the overlay. I calculated how much space the overlay needs by comparing the free space left on /system after flashing eos155 (wingray) + 0802gapps (6.87Mb) with the free space after flashing the overlay5.1 (2.36Mb). So ==> 6.87 - 2.36 = 4.51Mb.

This is the free space you'll at least need in /system to flash the overlay without problems.

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

On another note, I "cooked" a new overlay5.1 using the eos150 stingray kernel, as BRD suggested (look in the OP). @Mjamocha, your 3g should work ok with this one (let me know).
[Xoom Android Development] krankdroid:
i have to ask.

has anyone besides OP made this work ?

i am now back on ICS with the old build. All working, with minor bugs.
[Xoom Android Development] iruiz2:
I am unable to provide clues as to why you can't make it work. The only thing I can recommend is to wipe everything, including /system and /data, and make a barebones install of 155+0802gapps+overlay5. Flash them one after the other, then reboot.

How much space you have left on /system, is exactly the one I reported?

I have used rogue recovery 1.5.0 and twrp 2.3.2.3 to flash these, always without a hitch.

Send the logcat and we'll have a look...

If all this doesn't work, I'm ready to upload a twrp nandroid backup of this barebones 155+0802+ov5 combo for you to flash and see if it still doesn't work. If that's the case, it could indicate some internal sd problem.

I don't want anyone to be left out of the bt5+JB boat! :cool:
[Xoom Android Development] Mjamocha:
Thanks. I can test it for ya if you'd like. As I already have a working 4.12 overlay (Stingray) for my 4G. Currently i'm waiting for the 4.2 EOS4 boot image for Stingray to play with because as soon as it drops, my 4.1.2 custom overlay won't be useful to me any more. EOS has already dropped a 4.2 tester, calling it "E.O.S. 4"
[Xoom Android Development] iruiz2:
Yes, test it please if you can and report here. I know Eos4 is out there, but it looks too unpolished for me to try it. I think I'll wait a couple of nightlies more to try it and will update this thread's overlay accordingly. But if you are playing with it, I can speed up the overlay for 4.2.

Sent from my Xoom
[Xoom Android Development] bigrushdog:
Next nightly coming up shortly has a lot more polish. Btw if you are still having /system issues take a look at the eos 4 gapps package. Problem solved.
[Xoom Android Development] iruiz2:
I saw that now we have 50mb free in /system! Great work you guys are doing... I'll keep this tool up to date with 4.2...
[Xoom Android Development] XxLordxX:
Did you stop working on it? I'd love to try on 4.2 :) :)
[Xoom Android Development] iruiz2:
Nope, still here... I haven't updated to 4.2 because I am very happy with my 4.1.2 and haven't flashed the latest and I like to try first on my Xoom what I post here. Anyway, I'll make a 4.2 mix and post it here, seeing that there's people willing to try it out... Give me a couple of hours :cool:
[Xoom Android Development] XxLordxX:
Cool, thanks for the up :) :good:
[Xoom Android Development] iruiz2:
Ok people... here it is, the overlay for 4.2, based on the ramdisk of eos nightly 160: https://dl.dropbox.com/u/43942134/xoom_dev_overlay_v6.zip. Just flash it with your favourite recovery.

I haven't tested it yet on my Xoom, so make a backup before flashing it. Let me know how it goes...
[Xoom Android Development] krankdroid:
hmm.. is every wingray basically a stingray?

i am still trying to solve the problem and get backtrack 5 flashed so it would work. i returned to ICS for a while, and i got it working, even though it was a bit poorly, and just when i had flashed 4.1, my ALFA card is delivered. typical.

but when looking at the system info i gathered i could see that my wing thought it was a sting it seems.

the guy i bought it from did give me a story about stingray hardware in the wing, but i didnt really take notice of it.
[Xoom Android Development] iruiz2:
This wingray-stingray mix up could be due to the fact that in order to have only one overlay for both models, I used the stingray jb ramdisk to build the overlay (BRD suggested it). I get the same output from "cat /proc/cpuinfo", it shouldn't create any problems.

Any problems making bt5 work on jb4.1.2?

Sent from my Xoom
[Xoom Android Development] Mjamocha:
On 4.2 OS, the bt5 mount script need be updated to reflect the new "0" directory for proper mounting, no?
[Xoom Android Development] iruiz2:
You are completely right, I took that into consideration when reviewing the overlay symlinking but I didn't revise the scripts in the BT5 folder.

I need any of you running 4.2 to tell me where does /sdcard point to: is it /data/media/0 ? This would help me to elegantly update the scripts...

Sent from my Xoom
[Xoom Android Development] slaming:
entering BT5 chroot...
ioctl LOOP_SET_FD failed: Device or resource busy
mount: no such file or directory
mount: no such file or directory
mount: no such file or directory
net.ipv4.ip_forward = 1
/data/media/BT5/bootbt: line 23: /data/local/mnt/etc/resolv.conf: no such file or directory
/data/media/BT5/bootbt: line 24: /data/local/mnt/etc/hosts: no such file or directory
chroot: can't execute '/bin/bash': No such file or directory
Shutting down BackTrack ARM for Xoom
failed: no such file or directory
failed: no such file or directory
failed: no such file or directory
failed: invalid argument

thats the error i get with android 4.2, this is true with all versions of arm linux that I try so could be that something needs to be changed for android 4.2 or my setup is incorrect, although when i try any 4.1 or 4.0 rom it works flawlessly

edit: I think it is causing some major errors because it keeps rebooting now when the screen turns off :(

and some further details i'm running Eos 4 165