I mistakenly dropped pershoot's 10.1v kernel onto my 10.1 (P7500). Now thw screen draws garbage, and does not seem happy. I do have CWM 4.0.0.4 on it, and that does seem to work well, except that it won't mount a USB drive. ("unable to open ums lunfile" issue)
Any help would be appreciated.
adb shell mount /data
adb push NEW_KERNEL /data/media
flash new kernel and reboot.
done.
Or if you don't understand what pershoot is telling you to do. The backup that you shoulve made prior to flashing anything should work. You can select backup and restore in cwm, then advanced restore, select your backup, then just select boot
pershoot said:
adb...
done.
Click to expand...
Click to collapse
Thank you so much. In my panic, I had forgotten that the adb monitor is still running in recovery mode. I took this time to put ADB on my new Win7 machine. (been using it on my Ubuntu for kernel builds and client coding)
Long story short, ended up flashing a bad rom without backing up my current rom due to lack of storage space Just ordered a micro sd card from Amazon. Currently unable to boot phone due to not having a rom. Downloaded Android SDK and have been trying to sideload the .zip in CWM recovery but I get an "adb server is out of date. killing..." followed by "Daemon started successfully..." "device not found" Running Mac OS and I'm stuck on what to do at this point. Help?
I've been using in Terminal:
cd desktop
cd Android (Placed adb into this folder to make it easier to find)
./adb
./adb sideload Synergy.zip
LGeX said:
Long story short, ended up flashing a bad rom without backing up my current rom due to lack of storage space Just ordered a micro sd card from Amazon. Currently unable to boot phone due to not having a rom. Downloaded Android SDK and have been trying to sideload the .zip in CWM recovery but I get an "adb server is out of date. killing..." followed by "Daemon started successfully..." "device not found" Running Mac OS and I'm stuck on what to do at this point. Help?
I've been using in Terminal:
cd desktop
cd Android (Placed adb into this folder to make it easier to find)
./adb
./adb sideload Synergy.zip
Click to expand...
Click to collapse
You might have to do a system restore of the stock image. If you want to do this I can PM you some info.
Need help as well
DarkMenace said:
You might have to do a system restore of the stock image. If you want to do this I can PM you some info.
Click to expand...
Click to collapse
Could I please get some help with this as well. Trying to do a sideload as well, since I formatted the whole system and lost all of the ROMS I would normally install from the system SD.
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
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.
Hey guys,
before asking for help, I tried to solve my problem by myself but couldn't find a solution.
I bought a Xperia V, unlocked the bootloader, installed Xperia Recovery Manager to install TWRP to FOTA-Partition which worked.
Then I installed Cyanogenmod 11 and it worked. But actually, I wanted to install CM 14. I pushed the zip.file to internal storage via adb but couldn't find it in TWRP. Then I installed Clockworkmod Recovery which didn't solve this problem, too. I can't remember why, but I formatted everything possible with CWM and got an error message while trying to format /storage/sdcard0. After that I installed CM 11 again but the camera app didn't start and no download was possible: I got the message "couldn't find external storage". Even installing CM 10 didn't work. CWM says "error mounting /storage/sdcard0".
In adb shell no mount point shows up and command "chown sdcard_rw sdcard0" says "Unable to chown sdcard0: Read-only file system". Rootfs is read-only. At this point I gave up. Instead I tried to flash Android Stock ROM via flashtool but that didn't work because flashtool doesn't find my device although I installed the drivers. I run Windows 7 on my second Laptop and it says the drivers for Xperia V are current. Is there a chance to repair the device?
Thanks for help!