T-Mobile Galaxy S3 SGH-T999
Rooted
Latest TWRP recovery
CM 10.2 (Nov 6 nightly- Android 4.3.1)
I am trying to fix the storage issue that the multiple user profiles created when going from Android 4.1 to 4.2, where symlink folders are created and multiple instances of every installed app trick the phone into thinking more storage is being consumed than it actually is.
I found a video (Google: youtube how to fix htc one storage) which is specific to HTC One but figured it would work fine for me.
The video basically tells you to do a full factory wipe from TWRP and then ADB Sideload your ROM of preference.
My issues:
A. I installed Android SDK on my PC (Windows 7 64-bit) as well as the Android USB drivers. I enabled android debugging and did the kill-server and start-server and can get my PC to recognize my Android phone as an 'authorized device' upon entering 'adb devices' on the command line. However, once I wipe the card in recovery, my device ceases to appear in the cmd line. The list is empty. I need to understand why that happens.
B. Even though I've done a 'factory wipe' in recovery, if I reboot my phone, it goes to the CM setup screen and guides me thru initial phone setup.
Looking for some advice on the above issues. Clearly I'll need for my PC and phone to be able to communicate via ADB sideload first, then I can worry about issue B.
I'm not super experienced at this, but appreciate any help someone could provide. Alternatively, if there's a solution to fix the 4.2 storage issue without a full wipe and clean flash (via ADB), then that would be ideal. I've searched for answers on this specific topic to no avail.
I think you're on the wrong forum.
This is for international version of S3
I9300
Sent from my iPhone using Tapatalk
Related
Mods, if this belongs elsewhere, feel free to move it.
I read many many threads about people's problems with adb on the vibrant and while there were no individual threads that matched exactly, little pieces from many helped me in my situation; in case someone else experiences what I had, this is what I did to fix it.
Environment:
Win7 Professional N x64
Vibrant (SGH-T959:2.1-update1/ECLAIR/UVJI) (this was the leaked ROM mid Sept)
Samsung x64 drivers from TGA_Gunnman's thread (forum.xda-developers.com/showthread.php?t=728929)
USB Debugging enabled
Problem:
I was able to get all the components of the phone recognized in device mgr & I was able to mount both the internal SD and my 8gb external SD cards, read & write to them with ease; I was even able to flash the leaked ROM via ODIN. I was NOT able to get adb to connect to my device.
C:\vibrant\adb devices
List of devices attached
T9596f3efa91 offline
I tried in recovery mode, no dice.
I had tried Droid Explorer, it was unable to find my device as well.
I had read somewhere that it was a driver problem, although dev mgr wasn't complaining and everything else appeared to be working just fine. One person noted they were able to use the Samsung Moment drivers from JuneFabric's website. I tried to install those drivers and was met with an error during the installation that said windows was unable to locate the file. Uninstalling, rebooting, reinstall (as many times as I had...) had no effect.
I grabbed USBDeview (thanks to masr1979's post in forum.xda-developers.com/showthread.php?t=735534&highlight=masr1979) and uninstalled every android related driver. Rebooted and when prompted for the drivers, tried the moment drivers only to face the same "unable to locate file" error. I got fed up and tried going back to the drivers from TGA_Gunnman's thread which brought
me back to the start. Atleast I was able to mount my sd cards.
Solution:
Not satisifed with this, I went to Samsung's website and found drivers for XP/Vista... i can't for the life of me re-navigate to that download page, but I have uploaded the drivers here.
After running USBDeview to nuke everythign samsung/android related (again) and rebooting, I plugged my phone back in - pointed it to the extracted folder for the attached drivers, ignored the "unsigned drivers!" error for all three devices and re-tested DroidExplorer. SUCCESS! Droid Explorer found my phone and adb (console) also shows my device attached! Everything is golden.
Summary
Random-assed drivers found on Samsung's site for XP/Vista (attached) matched what my Vibrant wanted on Win7x64 in order to get data and debugging connectivity.
Thanks
(edited for the attachment which didn't stick? & stupid 5min wait to post )
Hey there,
Here is a list of what I have before I get started.
Samsung Galaxy Tab 10.1 Wifi (P7510)
Android Version - 3.2
Kernel Version - [email protected]#1
Build Number - INFAMOUS TAB 0.1 P7510UEKMM
Basically I have no access to my tablets internal SD card via my PC (Windows 7 and KIES)
I bought this tablet from a friend who rooted and flashed with the INFAMOUS mod.
I have searched all over the web for an answer and cant find something for this case specifically.
Each time I plug in my tab, my PC tells me that the Hardware ID is missing.
I can see the tablet in my Devices and Printers (displayed as SAMSUNG_android) as well as in my Device Manager. In device manager it says the drivers are up to date and functioning.
What have I tried?
USB Debugging (On and Off)
Clearing cache via recovery mode
Updating drivers via W7 and KIES via Samsung
I have tried following a few threads on installing the KIES software without internet connectivity. However I would rather not use the KIES Software anyway as it is kind of garbage.
I am looking to have access to the internal SD card so I can flash a new Rom on the Tab, however I would first like to even just have access to the file transferring.
Can anyone point me in the direction of help and me being able to enjoy this tablet?
I hope I have provided enough information. I am a pretty techy person and I understand how to do all of this but it seems like I am missing something really big.
Something to take note of, whenever the tab is plugged in (PC or Wall) there is a red x over the battery symbol and the tab charges very slowly.
Cheers
B
Snugglebutt said:
Basically I have no access to my tablets internal SD card via my PC (Windows 7 and KIES)
...
I am looking to have access to the internal SD card so I can flash a new Rom on the Tab, however I would first like to even just have access to the file transferring.
Click to expand...
Click to collapse
The Galaxy Tab doesn't expose the internal "sdcard" as a device that you can mount on your PC. If you enable it, it shows up as a MTD device.
The sdcard partition is formatted using a Linux native filesystem, not FAT, so Windows can't recognize it.
I use adb to push files onto the sdcard. ADB comes with the android SDK.
k1mu said:
The Galaxy Tab doesn't expose the internal "sdcard" as a device that you can mount on your PC. If you enable it, it shows up as a MTD device.
The sdcard partition is formatted using a Linux native filesystem, not FAT, so Windows can't recognize it.
I use adb to push files onto the sdcard. ADB comes with the android SDK.
Click to expand...
Click to collapse
As stated, make sure you have your tablet in MTP, and if so, make sure to update your drivers.
Settings > Storage > Additional Settings (top right) > MTP
To build on the above, if you have uninstalled Kies but also the Samsung USB drivers, you will be unable to connect the tab. Reinstall (or maybe uninstall and reinstall if you still have them) the drivers. A lot of the times that is the issue.
Go to Settings>Storage>Options/Info (The one on the upper right)>MTP(Check this one)
hope this help
FIXED
k1mu said:
The Galaxy Tab doesn't expose the internal "sdcard" as a device that you can mount on your PC. If you enable it, it shows up as a MTD device.
The sdcard partition is formatted using a Linux native filesystem, not FAT, so Windows can't recognize it.
I use adb to push files onto the sdcard. ADB comes with the android SDK.
Click to expand...
Click to collapse
To build on the above, if you have uninstalled Kies but also the Samsung USB drivers, you will be unable to connect the tab. Reinstall (or maybe uninstall and reinstall if you still have them) the drivers. A lot of the times that is the issue.
Click to expand...
Click to collapse
Ahhh ha! As soon as I uninstalled the driver that windows found and used the Google Driver that came along with the Android SDK, the tablet was recognized. Alas, I can finally use this tablet.
In the end it was as simple as a driver error, I spent a very long time searching last night and now I just feel silly.
The tablet still shows the red X over the battery symbol, whether I have MTP with USB Debugging on or off. I guess this can be avoided with certain ROMS. Anybody know of a ROM that avoids this?
Thank you all for your immediate responses!
B
Tid bit of info
H. Ess said:
As stated, make sure you have your tablet in MTP, and if so, make sure to update your drivers.
Settings > Storage > Additional Settings (top right) > MTP
Click to expand...
Click to collapse
Go to Settings>Storage>Options/Info (The one on the upper right)>MTP(Check this one)
Click to expand...
Click to collapse
By the way you two, there is no option in 3.2 for this.
In 3.2 its Applications/Development/USB Debugging
In storage there is no option to choose MTP, it seems that it always has been enabled and I cant find it anywhere in the settings to change it.
Thanks for the input though
Snugglebutt said:
By the way you two, there is no option in 3.2 for this.
In 3.2 its Applications/Development/USB Debugging
In storage there is no option to choose MTP, it seems that it always has been enabled and I cant find it anywhere in the settings to change it.
Thanks for the input though
Click to expand...
Click to collapse
For honeycomb and many others, debugging is always there. Under the storage option, you have an Additional Settings button usually and it should be present in there. I was always running3.2 until like a couple days ago so surprised its not there. Oh well problem solved lol
I'm having a similar problem with my tab not being recognised by my pc (win7 64) or in kies. It was originally an M380W (Korean) model, which I updated to a P7510. That all went fine, and the tablet works perfectly, except for the fact that my pc no longer sees it when it's plugged in. I tried uninstalling and reinstalling the drivers, but no dice. I'm going to see if adb works.
Hello All,
So there is very little documentation on the PX102 online as of yet, let alone AOCOS products in general (at least on english sites which I have scoured). First off, I'm currently using OSX 10.6.8 and have the current Android developer tools package that was downloaded from their site about three hours ago (just to be clear). The PX102 is running 4.1.1 and the tablet is a fresh restore (I had a number of apps downloaded but considered that some may have been interfering...).
I will be attempting to root via psneuter exploit from SuperOneClick v2.3.3, however in the terminal when I execute "adb devices" it returns "List of devices attached" with blank space underneath...
I have tried to kill/restart server, run "adb usb", and a couple other small things to no avail.
Yes, usb debugging mode is enabled as well.
I would really like to attempt/execute this all via OSX, however name an OS and I have it at my disposal...
I admit- I am a noob in various ways, especially to android as this is my first android device. Hoever, I also consider myself to be rather self sufficient in terms of sourcing knowledge and troubleshooting, which is why I humbly ask for guidance in this endeavor.
Also, feel free to ask me any questions about the PX102 (via PM only please! I dislike threads being fuddled with asides...).
I'm not seeing too many people claiming to have these tablets though there is quite a bit of interest in them.
Anyone?
For windows you can try rkbatchtool v1.5 to get the correct drivers
Rooted mine
I rooted mine, wasn't easy though.
First problem, you need a adb driver that works on this rockchip tablet that doesn't have a built in ADB driver. Also I didn't have much luck on the chinese language AOCOS forum.
The only way I found to get one is:
1) download and install the morborobo phone manager software from moborobo.com. Yes this is a risk to your pc. God knows what else it did to my pc.
2) let IT find a driver. It will download and install two unsigned drivers.
3) those drivers aren't enough. You need to generate adb_usb.ini in c:/Users/%username%/.android/adb_usb.ini (if you're on windows 7)
Installing the SDK does that automatically otherwise you need to run "android update adb" or something to generate it
4) put the vendor id at the end of adb_usb.ini in the case of AOCOS the vendor is 0x2207
I tried using a premade adb_usb.ini with all of the vendor ids. That didn't work. It worked when I put the right on only.
NOTE, that vendor ID exists nowhere online. I had to find it by reading it directly from the device using USBVIEW from http://digital.ni.com/public.nsf/allkb/335A90747734097886257070006415B9
5) Now you should have a working adb driver. Plug the machine in and type "adb devices". It should see yours
6) now comes the rooting.
Follow the instructions here:
http://forum.xda-developers.com/showthread.php?t=1886460
The script is here: http://uploaded.net/file/0fpyh5c5
the videos showing how are here http://forum.xda-developers.com/showthread.php?p=33470626#post33470626
Note there IS a hacked adb driver that doesn't need a vendor ID, BUT it doesn't work for rooting, it's too old to have the restore feature you need for a jelly bean root.
The PX102 is cool, but mine has some problems:
1) the keyboard charge connector is bad, I have to send it back
2) the battery sucks... I'm sending back the tablet too, hopefully that will fix it
3) never drop one of these, mine only fell a couple feet and it's flaky now. :/
4) the camera is fake. It's not the 2mega pixels it says. It's super low quality and maybe vga. They put in bull**** fractal interpolation software to try to fake higher res
The keyboard is no where near as nice as a transformer, the tablet only rests on the keyboard and can fall off.
Still it's a nice machine. I have my memory cards formatted ext2 (from a previous tablet). I can mount them but the machine won't boot with an ext2 card plugged in. I have to take the card out, boot the machine, then plug it in and mount it.
I even managed to install GNU Gcc/ gnu tools
You can also try this: http://www.androidtablets.net/forum/rockchip-rk3066-tablets/46964-root-your-rockchip-3066-a.html
Or this: http://valentijn.sessink.nl/?p=382
I have been trying for a few days not to get my NT to connect to ADB in CWM. I am having no luck.
I am able to connect and browse the 1 gb partition and the sd card in windows but cannot connect to adb even when the tablet is running.
It has been a while since i have messes with my NT but i currently running nightly CM and have CWM 6.0.0.0 installed as well.
I am sure i am just missing someting simple to accomplish this task but my searches are leading me know where.
I have also tried both in linux and windows to connect to ADB.
I feel one of my problems may be that i do not have debugging turned on in my ROM but i cant seem to find that either.
Any guidance or a link would be greatly apreciated.
Thanks in advance.
"ADB Debug" setting is under Settings->Developer's Options.
If you're trying to use ADB over USB, see also http://forum.xda-developers.com/showthread.php?p=35971559#post35971559.
Hello all, longtime reader first time poster. I've got the Galaxy Player 4.0 (YP-G1US), and I'm in a "bootloop" situation similar to the others I've seen around here. It seems that the device can't mount the /data partition (mmcblk0p2), and I've tried flashing the stock ROM using Odin in Windoze, Heimdall in both Windoze and Ubuntu 12.04 and 12.10 (not that that I expected a difference) and Terra Silent ROM as well. I flashed using the files from zaclimon's post (http://forum.xda-developers.com/showthread.php?t=1531850), using the pit (with repartition), param, cache, dbdata, factoryfs and zImage. None of that worked, so, I've resigned myself to the fact that my internal memory must have been damaged.
I stumbled on this post http://forum.xda-developers.com/showthread.php?t=1861294 to try to format my external SD as the /data partition. I realize this isn't for the YP-G1US, but I thought I would try anyway (and the first steps should be agnostic of device.) I made two partitions, one in vfat, the other in ReiserFS, flashed stock ROM using all the files I mentioned above, but still got the bootloop. To monitor the situation, I installed google's SDK tools, but can't get ADB to work with my device. When I am in recovery mode for Terra Silent ROM, I am in USB debugging mode automatically, but ADB shows that my device is offline (specifically, the command 'adb devices' returns '????????? offline' ) I understand this is because my device can't authenticate the RSA key from my computer, which would be a handy feature if my device actually worked (you know, to prevent someone from taking my information.) But, since my device won't boot and I've wiped out all the data it had, this is an unnecessary annoyance that prevents me from diagnosing my problem.
Here are my questions:
1.) Do you know how to restore my device to some sort of working order (which most likely involves mounting the external SD as the internal SD in some manner.)
2.) If you don't know how to do 1.), could you at least tell me how to get ADB to recognize my device so I can figure out what my problem is? Maybe some method of moving the RSA key from my computer to the device, or some other way to run ADB on a device that can boot to recovery or download but not all the way so that I can transfer the key normally?
Thanks very much,
Eric
ewgrashorn said:
Hello all, longtime reader first time poster. I've got the Galaxy Player 4.0 (YP-G1US), and I'm in a "bootloop" situation similar to the others I've seen around here. It seems that the device can't mount the /data partition (mmcblk0p2), and I've tried flashing the stock ROM using Odin in Windoze, Heimdall in both Windoze and Ubuntu 12.04 and 12.10 (not that that I expected a difference) and Terra Silent ROM as well. I flashed using the files from zaclimon's post (http://forum.xda-developers.com/showthread.php?t=1531850), using the pit (with repartition), param, cache, dbdata, factoryfs and zImage. None of that worked, so, I've resigned myself to the fact that my internal memory must have been damaged.
I stumbled on this post http://forum.xda-developers.com/showthread.php?t=1861294 to try to format my external SD as the /data partition. I realize this isn't for the YP-G1US, but I thought I would try anyway (and the first steps should be agnostic of device.) I made two partitions, one in vfat, the other in ReiserFS, flashed stock ROM using all the files I mentioned above, but still got the bootloop. To monitor the situation, I installed google's SDK tools, but can't get ADB to work with my device. When I am in recovery mode for Terra Silent ROM, I am in USB debugging mode automatically, but ADB shows that my device is offline (specifically, the command 'adb devices' returns '????????? offline' ) I understand this is because my device can't authenticate the RSA key from my computer, which would be a handy feature if my device actually worked (you know, to prevent someone from taking my information.) But, since my device won't boot and I've wiped out all the data it had, this is an unnecessary annoyance that prevents me from diagnosing my problem.
Here are my questions:
1.) Do you know how to restore my device to some sort of working order (which most likely involves mounting the external SD as the internal SD in some manner.)
2.) If you don't know how to do 1.), could you at least tell me how to get ADB to recognize my device so I can figure out what my problem is? Maybe some method of moving the RSA key from my computer to the device, or some other way to run ADB on a device that can boot to recovery or download but not all the way so that I can transfer the key normally?
Thanks very much,
Eric
Click to expand...
Click to collapse
Are you using adb on Ubuntu? You have to run adb start-server as root.
Mevordel said:
Are you using adb on Ubuntu? You have to run adb start-server as root.
Click to expand...
Click to collapse
I am (technically Kubuntu, 12.10), but whether or not you need to be root to use adb depends on where you installed it. At any rate, if it were a root user priviliges issue, I'd be seeing "?????????? No Permissions". I did run adb as root, just to be sure, and got the same response as described in the original post.
I know that the issue is the RSA key authentication (whitelist) "feature" that google introduced with more recent versions of adb, which is fine if you can actually boot your device and click "yes" on the popup that asks to verify that you want the connected computer to access your device. The problem I have has arisen because I can't boot normally (I can only get to recovery) and so can't authorize my computer to connect to my Galaxy player (and so can't transfer the RSA key from my computer to my Galaxy.) So again, I ask, is there a workaround?
Thanks,
eric
ewgrashorn said:
I am (technically Kubuntu, 12.10), but whether or not you need to be root to use adb depends on where you installed it. At any rate, if it were a root user priviliges issue, I'd be seeing "?????????? No Permissions". I did run adb as root, just to be sure, and got the same response as described in the original post.
I know that the issue is the RSA key authentication (whitelist) "feature" that google introduced with more recent versions of adb, which is fine if you can actually boot your device and click "yes" on the popup that asks to verify that you want the connected computer to access your device. The problem I have has arisen because I can't boot normally (I can only get to recovery) and so can't authorize my computer to connect to my Galaxy player (and so can't transfer the RSA key from my computer to my Galaxy.) So again, I ask, is there a workaround?
Thanks,
eric
Click to expand...
Click to collapse
The build property ro.adb.secure=0 will override that. You can try putting it in build.prop, but if it doesn't work, you'll have to put it in /default.prop, which requires modifying the kernel ramdisk. While you're at it, ro.secure=0 will give you an automatic root shell.