yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy Note II] shangrila500:
The questioms have already been answered but something caught my attention, you want to use your keyboard and mouse on your phone. You can already do that, the Note 2 has USB OTG active so you can use just about anything on it, except XBOX controllers, like PS3 controllers, jump drives, external hard drives (they have to be formatted a certain way but they are able to be used), mice, keyboards, etc.

You should still root your phone because it opens an entirely new world for you.
[Verizon Samsung Galaxy Note II] st34dy:
Wow! I ordered one of those little cables that lets you plug in USB things but never thought to simply try using a USB keyboard or mouse with it! I am typing this on my USB keyboard and it works like a charm :) I also tried using a USB mouse and it works great, the wheel even works for scrolling up and down. I will try my wireless keyboard and mouse combo later to see if it will work but I am doubting it will work if it needs drivers (It is not the bluetooth kind). I wonder if this thing can handle USB splitters....

Thanks!!! Love the Note2
[Verizon Samsung Galaxy Note II] shangrila500:
Yes it works great with USB splitters, at least the few I've tried and a few other members have tried. And it very well may work with the wireless keyboard, I have one from somewhere around '00 and it works perfectly, you never know until you try!
[Verizon Samsung Galaxy Note II] st34dy:
I was able to get the PC USB connection working thanks to eboodnero's advice, but the real issue was that I was trying to connect the USB plug into a splitter USB plug instead of directly into the computer :( A poor mistake, learned the hard way.

Also, I tried logging into the Tumblr app after changing my password to an easy one without special characters, and that seemed to make it work ^shrug^
[Verizon Samsung Galaxy Note II] shangrila500:
Yeah, you always have to plug straight into the computer with this phone it seems, especially for things like Casual or Odin.
[Verizon Samsung Galaxy Note II] eBoody:
glad it worked out for you bud! =)
[8.9" Kindle Fire HD Q&A, Help & Troubleshooting] badbutz:
hi there,

After some hours reading and trying to fix it myself, I have to admin that I need help with rooting my new KFHD8,9 Firmware 8.4.1:

I would rather post in the referring development threads, but I am not allowed to yet. So i am asking here for help :)

The thing is that all my devices at home are running Linux (Ubuntu 13.04) and I am not trusting the "use-Windows-in-a-VM-and-use-USB-to-root" method :)

Now I was following the Tutorial from seokhun and decided to use the Bin4ry method to root, because it is delivered with the RunMe-script as a windows-batch and a shell-script.

The android-tools (android-tools-adb, android-tools-fastboot and android-tools-fsutils) have been successfully installed via apt-get and are working (I can use adb and fastboot to get device information).

When I try to execute the RunMe.sh (have made it executable via chmod +x before) and choose the option 1 it is stuck:

Make a choice:
Please enter a valid number(1 to x):
1

Checking if I should run in Normal Mode or special Sony Mode
Please connect your device with USB-Debugging enabled now
Waiting for device to shop up, if nothing happens please check if Windows ADB-drivers are installed correctly!
* daemon not running. starting it now on port 5037 *
* daemon started successfully *

The script hangs at the line with the first use of the delivered adb with the wait-for-device parameter (inside the stuff folder).

mytest() {
echo "Checking if I should run in Normal Mode or special Sony Mode"
echo "Please connect your device with USB-Debugging enabled now"
echo "Waiting for device to shop up, if nothing happens please check if Windows ADB-drivers are installed correctly!"
./stuff/adb wait-for-device
./stuff/adb pull /system/app/Backup-Restore.apk . > NUL
./stuff/adb pull /system/bin/ric . > NUL

If I run my installed version of adb it terminates successfully with

adb wait-for-device
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
login@computer: ...

But when I call the delivered adb inside the stuff folder it never terminates:

../Root_with_Restore_by_Bin4ry_v30/stuff$ ./adb wait-for-device
adb server is out of date. killing...
* daemon started successfully *

has anybody a clue? :confused:
[8.9" Kindle Fire HD Q&A, Help & Troubleshooting] badbutz:
Its me again :)

I am wondering if i can exchange the delivered ADB with my installed and Working ADB.

If it can be replaced, why is it delivered for Windows and Linux and why most tutorials set them AS requirement proceeding :what:
[8.9" Kindle Fire HD Q&A, Help & Troubleshooting] Thepooch:
Create a live usb with persistent must be an 8 gig usb flash drive for maximum persistent. Use this creator http://www.pendrivelinux.com/universal-usb-installer-easy-as-1-2-3/ . Use linux mint maya the mate one with codecs 32bit http://www.linuxmint.com/edition.php?id=105. Boot it and use this script http://xdaforums.com/showthread.php?t=2162973 . That is all you will need good luck. You can use 32bit ubuntu12.04 as well the reason to use these distros is that the newer ones don`t run soupkit installer properly in a terminal it makes the installation much cleaner I have been able to force install on some of the later distros but it`s a serious pain in the rear.
[8.9" Kindle Fire HD Q&A, Help & Troubleshooting] badbutz:
thanks for your reply!

I will try it with Ubuntu 12.04 the next days!
[8.9" Kindle Fire HD Q&A, Help & Troubleshooting] badbutz:
worked fine with Ubuntu 12.04. Thank you very much for the hint!
[8.9" Kindle Fire HD Q&A, Help & Troubleshooting] Thepooch:
Your welcome anytime.:highfive:
[8.9" Kindle Fire HD Q&A, Help & Troubleshooting] noobapotomus:
Glad i checked forums first

Was going to help a friend root, twrp and cm 10.1 his KF 8.9 after work today. his laptop is running 13.04 ubuntu. glad i ran across this post before wasting significant time. 1'll bring a 12.04 laptop with me. Thanks to Thepooch for sharing this info and have a great week!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] samg007:
i'm presently running liquidsmooth v2 and i love it but i want to update it. The problem is that i've encounter a problem flashing liquidsmooth v2.5 After the flash, my home button was not working anymore. all my other buttons were working but not this one (the most important). I tried to flash it a second time and same problem... any solution ?????
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] psp9000333:
Have you wiped the dalvik cache, cache and data before install? if you have, it must be a broken button. i have no issues with the rom and phone when it comes to the home button. works fine.

Sent from my SGH-I747M running Liquidsmooth JB 4.2.2
[General Questions and Answers] castler:
First off - I have a download of the FA19 factory zip of the gingerbread system to perform a restore, but:

2nd - My hobby has me in creeks and drains - but I slipped and my android galaxy prevail running gingerbread was only in the water less than 5 seconds. but the phone at first was quirky (screen would light up and so would the buttons - but it took a couple hours for it to fully dry before it would fully come on and display the screen properly.) after that it worked fine, but the USB charge port is fried, don't work in a pc nor outlet, i've tried 3 pc's, and 2 wall outlet's, none charge it.

However, I tried to do a format of the phone thinking it might be a firmware, and also erased the sd card which stored most of the phone's files (data for the system and apps, but now I can't restore the phone to factory settings - The only thing I can do since I cannot use Odin since the USB don't work(can't charge nor get the pc to read the device) - is to do the Volume down, power button at boot and the recovery option then appears - I need to know how to load the sd card with the factory files that appear on this page, since some are in zip format so the restore function will work properly - also I get a MD5 error when I tried to do this myself, I probably wasn't doing it right.
[Nook Color Q&A, Help & Troubleshooting] volpo222:
Hi,

Could someone please point me to a post with info on how to return a Nook Color to stock?

While showing some friends how easy it was to run stock on the NC I found out that somehow I managed to overwrite the stock boot with a partial install of CM10. I'm running CM10.1 off of an SD card no problems.

Thanks,

V
[Nook Color Q&A, Help & Troubleshooting] leapinlar:
Go to my NC tips thread linked in my signature and look at item A15.

Sent from my Nook HD+ running CM10.1 on emmc.
[Nook Color Q&A, Help & Troubleshooting] volpo222:
Thanks!

V
[T-Mobile, Samsung Galaxy SIII] Bray90820:
As of right now i can install any Rom from the T999 that does not require the new boot loader upgrade but i get a status 7 when i try to install the newer roms is there any boot loader for the T999L that supports the Roms
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
Edit the update script of the zip files to remove the bootloader asserts.
[T-Mobile, Samsung Galaxy SIII] Bray90820:
How would i do that
[T-Mobile, Samsung Galaxy SIII] mt3g:
There are lines in the with in the roms.zip

meta-inf>com>google>android>updater-script>

assert(getprop("ro.bootloader") =="t999.......) and the three other bootloaders it checks for.

I'm guessing you can remove these lines and rezip and it will flash, but I am not going to do so, and don't plan on trying... I can remove those lines and rezip it for you to try and flash and see how it goes. I would put 20$ down that it won't harm the phone but not 600 (new) or 180 (insurance) lol.
[T-Mobile, Samsung Galaxy SIII] Bray90820:
Until someone else tries i will wait
[T-Mobile, Samsung Galaxy SIII] mt3g:
I edit lines in there when roms fail to install cause they are specific to att, just incase anyone else really wants it, just post and let me know. I'm off til Thursday so I have time at some point each day to do so. if anyone with more knowledge wants to confirm let me know, so that there is more comfort to this. ;)
[T-Mobile, Samsung Galaxy SIII] Bray90820:
If you could edit it out that would be nice and upload the new package that would be nice
[T-Mobile, Samsung Galaxy SIII] mt3g:
I'll work on it in a little bit. Got to do one for an att rom I wanna try anyways. What rom did you wanna try?
[T-Mobile, Samsung Galaxy SIII] Bray90820:
Cyanogenmod 10.1 RC4
[T-Mobile, Samsung Galaxy SIII] Bray90820:
Wait are you going to be editing the rom or the bootloader
[T-Mobile, Samsung Galaxy SIII] mt3g:
Updater Script in the .zip for the rom.
[T-Mobile, Samsung Galaxy SIII] Bray90820:
I was actually looking for the bootloader so i could install whatever rom i wanted
[T-Mobile, Samsung Galaxy SIII] mt3g:
Ohhhhh not possible yet. And if I remove those and it installs fine, you may still run into errors cause the CM team asks for people to be on the latest bootloaders to have it run no issues.

I'm sure your phone will be apart of the CM/AOSP builds soon enough.
[T-Mobile, Samsung Galaxy SIII] Bray90820:
Well I do have RC2 on it right now
[T-Mobile, Samsung Galaxy SIII] mt3g:
That was before all the changes. My personal favorite ;)
[T-Mobile, Samsung Galaxy SIII] Bray90820:
I Guess i'll just wait then
[T-Mobile, Samsung Galaxy SIII] DJ_SpaRky:
How did you install this? Did you edit the updater-script or did it just flash over?

I'm using TWRP on a T999L and am looking to go custom ROM with CM10.1, but am trying to find more info. I know that I can always go back since [MENTION=4081205]DocHoliday77[/MENTION] & [MENTION=4201894]MotoDefier[/MENTION] got the stock ROM all squared away: http://xdaforums.com/showthread.php?t=2308514
[T-Mobile, Samsung Galaxy SIII] Bray90820:
The d2tmo has been updated tir the T999L and the latest nightly is fully working without any modifications needed
[T-Mobile, Samsung Galaxy SIII] DJ_SpaRky:
Awesome!! Thanks, I was thinking that I might have to flash the ROM then flash the T999L modem. What date are you using? Any issues?
[T-Mobile, Samsung Galaxy SIII] Bray90820:
No issues on june 18th
[T-Mobile, Samsung Galaxy SIII] DJ_SpaRky:
Great, thanks. I will flash this weekend and report back any issues.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Even though the T999L isn't put into the asserts as an allowed device, I don't think it would be any issue at all to edit the script to allow the flash.

The T999L shipped with 4.1.2 and even though the build is different, I believe it would run cm just as well as md5.
[T-Mobile, Samsung Galaxy SIII] DJ_SpaRky:
I was just looking at the updater-script for RC5 and 20130621, the nightly has the T999LUVAMB7 assert, but not the RC5. Could I copy that one to the RC5 zip and it flash the ROM? I ask because I have tried to edit zip files before and they have failed to flash.(I was trying to remove apps prior to install)

Also, what about the modem? Think I will need to flash the T999L modem to get connectivity?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
I'm guessing it would work. Look for any.other differences between the two first though.

Custom roms shouldn't ever include a modem imo.

You won't need to flash the modem. Most roms don't include it and the usual Rom flash won't touch your current one. You should only.need to flash it if you've tried to flash a different modem first.
[T-Mobile, Samsung Galaxy SIII] DJ_SpaRky:
Thanks, I wasn't sure if wiping system took the modem too or not.

I will just add the assert and see.
[T-Mobile, Samsung Galaxy SIII] DJ_SpaRky:
OK, well here is an update, I added the LUVAMB7 line to the updater-script and flashed, doing my normal process. Everything seemed to go OK, no FCs or other errors, no random reboots, everything seemed to work. Except the Camera, i get a "Cannot connect to camera" error. I tried the "4CamNex2" camera and no go. I tried to install the Samsung stock one but that failed. I also notice that a lot of the items that I am used to seeing in the Settings are not there. Such as Development and Performance. Not sure if they have been removed or where added on the other ROM I was using (old phone). I also noticed that the build.prop still shows it as a T999, so that will need to be edited. I am going to look into the camera issue, and maybe flash the nightly or edit and flash the CM10.0 Stable. I'll post later.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
I may have something to try for this when I get home this evening. But I've heard the latest nightly fixed several things. Maybe camera was one of them?
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
Flashing CM 10 stable isn't going to fix your problem. There was a commit a few days ago (a kernel commit) that was supposed to fix the camera for Verizon users on their now-pulled firmware release.

That's my way of saying try the stock kernel (people have a habit of using old kernels-a huge mistake), if you weren't already. If you were, probably going to need to wait for it to be fixed on their side.
[T-Mobile, Samsung Galaxy SIII] DJ_SpaRky:
OK thank you both. I am going to wipe again and reflash the Latest nightly unmodified. Hopefully it works.
[T-Mobile, Samsung Galaxy SIII] DJ_SpaRky:
Alrighty, I have flashed cm-10.1-20130622-NIGHTLY-d2tmo, and everything seems OK. The Camera works, Back and Front, Panorama, and all of the settings. Also, Ran the "Ten Taps" to get the Developer and Performance items in Settings. I should have tried this first, it all works from the get go. I have found no issues so far, Calling, SMS, WiFi, Cell Data (not sure about LTE, but the option is still there), OTG, AutoBacklight, LED Flash/Flashlight (Torch app), CRT Off and a bunch more that I can't think of. I am ecstatic about it, I'm going to finish reloading all my apps and other settings and start to enjoy it. Thank you all for your help.
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
Don't flash old nightlies. And if you ever find a ROM that includes a modem (aside from stock and root66), let me know, so I can tell everyone not to flash it.
[T-Mobile, Samsung Galaxy SIII] DJ_SpaRky:
So I have learned. Thanks again to all of you for this info, it has been a learning experience and hopefully helps the T999L owners now and in the future to no make the same mistakes.
[T-Mobile, Samsung Galaxy SIII] DJ_SpaRky:
For those that might be interested:
[T-Mobile, Samsung Galaxy SIII] mystereg:
I wanted to confirm what DJ_SpaRky said. I flashed cm-10.1-20130703-NIGHTLY-d2tmo on my SGH-T999L using TWRP recovery, and everything's fine on my end. I could not flash with CWM recovery even after removing the asserts in the updater script.

I previously had flashed the SlimBean ROM for the SGH-T999, where everything worked except the camera ("Can't connect to camera" with all camera apps and all /system/cameradata drivers I could find). With this CM10.1 nightly, all camera functionality as far I can tell works great with negligible lag. Even Instagram's new video feature seems to mostly work (though I haven't actually posted anything yet). LTE seems to be working as it's supposed to; by default, the fast.tmobile.com APN was selected, and my download speeds are typically 11000-15000kbps using the Speedtest app in Los Angeles, CA. I'm very happy with this outcome, which wouldn't have been possible without everyone's help here! :good:

(Also in case anyone was wondering, I was able to Odin back to stock (when I thought I wouldn't be able to get the camera to work) thanks to DocHoliday77 and Motodefier's help at http://xdaforums.com/showthread.php?t=2308514. Couldn't use both the Deodexed or PureStock ROMs though -- got stuck at the T-Mobile 4G LTE boot animation for over 10 minutes before I pulled the battery. Pretty sure I factory reset, cache wipe and Dalvik wiped before I flashed those ROMs.)
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Dod you try factory resetting after flashing the roms?
[T-Mobile, Samsung Galaxy SIII] mattq24:
hi i have a question can u put a link to download cm-10.1-20130622-NIGHTLY-d2tmo

hi can u put a link to the download for cm-10.1-20130622-NIGHTLY-d2tmo
[T-Mobile, Samsung Galaxy SIII] mattq24:
i have a question

hi im a noob to all this and I rooted my sght-t999l like a couple days ago and I tried installing some rom for sgh-t999 using rom manager and now my phone is useless like it wont connect to wifi or my service I cant text call nothing what do I do? If u can can u please give me a step by step on how to fix this I need my phone asap :( thanks message me would be easier cause idk how to use this site too
[T-Mobile, Samsung Galaxy SIII] imblessed68:
There are few roms available for us t999L owners however the nice people in this forum will help guide you if you want to install a custom rom they helped me and I luv them all!!!!!!!!!!!
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
If you flash a TW based rom and lose wifi/bt/etc, go to tbe T999L thread in development and flash tbe MB7 kernel+ modules. Or you can flash tbe MD5 kernel with or without modules. Either way should work fine.
[T-Mobile, Samsung Galaxy SIII] mystereg:
Darn. I didn't, though I definitely should've (at least tried). If I need to go back to stock again in the future, I'll try the ROMs again.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
99% of the time, hanging at boot is solved by factory resetting. There is some incompatible data left from another rom usually causing it.
[T-Mobile, Samsung Galaxy SIII] Fry-kun:
[how] can I use heimdall to install TWRP? (trying to do the stuff from post #39, but no easy access to a windows machine, so no odin)
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Not sure. Very few people seem to have any experience with Heimlich. I'd assume you flash the tar file like you would a full firmware update, but I'm probably wrong.

If you are rooted, get Goo Manager from the store, press menu then install openrecovery. Wait for the toast confirming its done then reboot recovery.

If you are trying to root, try Motochopper. Google will find it for ya.
[T-Mobile, Samsung Galaxy SIII] Fry-kun:
lol, heimlich xD

sorry, forgot to specify -- rooted (with motochopper, earlier), trying to get recovery & CM

Just now installed Goo Manager, selected "Install OpenRecoveryScript" -- error message says "no recoveries were found for your device"... any other
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Ok, two options, either flash the recovery in heimdall (auto correct got me last time! Too funny though)

Or edit your build.prop.

To edit this file, using a root file explorer, go to /system/build.prop and open in editor.

Anywhere you see 'd2ltetmo' change it to d2tmo

Anywhere you see 'T999L' change it to T999.

Reboot and try Goo Manager again.
[T-Mobile, Samsung Galaxy SIII] Fry-kun:
Okay, so heimdall worked finally. I guess something was in a bad state, and worked after laptop got rebooted

code:

heimdall flash --RECOVERY openrecovery-twrp-2.5.0.0-d2tmo.img

from then on, followed [MENTION=4307789]DJ_SpaRky[/MENTION]'s instructions and so far so good.

NOTE/caution for future adventureres in flashing: cm-10.1.1 stable released 2013/07/10 does not work
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Glad you.figured it out!

How is cm not working??
[T-Mobile, Samsung Galaxy SIII] DJ_SpaRky:
Glad you got it working.

The Stable builds (10.1.0 & 10.1.1) do not contain the assert for the bootloader MB7, only the nightlies, for now.
[T-Mobile, Samsung Galaxy SIII] Fry-kun:
Should I wait for the next stable or just go in and modify the asserts myself now?

I'd feel more at ease not running on a "nightly" build :)
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Why would they put it in the latest nightlies, but not the stable that looks like it was released yesterday?
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
The only difference is a number. I assure you that the stable build is of the same low quality as the nightly builds. Just kidding. Kind of.:eek:

I did not check to verify the validity of that, but if it is true, it would be because they rebuilt 10.1 "stable" and added a few security patches per the website. So, even though it was built last night, the code used is already a few weeks old.
[T-Mobile, Samsung Galaxy SIII] Fry-kun:
thanks that makes me feel so much better

lol
[T-Mobile, Samsung Galaxy SIII] DJ_SpaRky:
The Nightly is just find, there are years of development behind them. You can add the assert and install it, you should have no problems (maybe the camera), but I can't confirm that it will be "Stable".
[T-Mobile, Samsung Galaxy SIII] DJ_SpaRky:
Probably forgot to add it before Jenkins ran it through. Different source trees, right?
[T-Mobile, Samsung Galaxy SIII] BaldwinMR:
SGH-T999L

I downloaded the only available free version of Galaxy S3 ToolKit which was the v7.0.0 to Root my T-Mobile SGH-T999L , My build number is JZO54K, however in the ToolKit that Build is not available for U.S. models, so I went with the U.S. version that was displayed ( JROO3C DLK3) 4.1.1.....I see my build in the International LTE models, but not sure if it would brick my device to flash it........anyone know where I can find a ToolKit (free) that will work with my build?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Toolkit doesn't support it. If you're just trying to root, I have a thread in development section that has an odin flashable called stock system. Flash it to root.
[T-Mobile, Samsung Galaxy SIII] Fry-kun:
So I've been running cm-10.1-20130709-NIGHTLY-d2tmo - so far so good

Small strangeness though: I thought the phone reported model as T999L at first, but now it's just T999 -- is that expected?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Perfectly normal when you flash a T999 Rom. Value is in the build.prop if you want to change it.
[T-Mobile, Samsung Galaxy SIII] Naturesretard:
is this for flashing t999L to t999? or the other way around? or vice versa?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
To the T999L.

I've got a thread I'm half done writing. Itll have answers like this and more. Ill try to get it posted up late tonight, so hopefully it'll clear up a lot of confusion.