Develop Bugs

Help, Please

So, I have tried all methods posted here. I have not gotten a new sdcard, so that could be it, but if you sift through all these threads, many people have gotten root with the card that came from verizon. Also, would it help to wipe out my phone? Not exactly sure how to do it, but would it help? Also, I hear my phone connect with the usb sounds, but it seems like sometimes I get a quick 3 tones and it doesn't connect. Not sure what that means either.
If anyone can please help, I would appreciate it!

if your not sure if it connected right, open the device manager and see if it is appearing on there.
As far as i know wiping your phone probly won't really help much either.

rstandi said:
So, I have tried all methods posted here. I have not gotten a new sdcard, so that could be it, but if you sift through all these threads, many people have gotten root with the card that came from verizon. Also, would it help to wipe out my phone? Not exactly sure how to do it, but would it help? Also, I hear my phone connect with the usb sounds, but it seems like sometimes I get a quick 3 tones and it doesn't connect. Not sure what that means either.
If anyone can please help, I would appreciate it!
Click to expand...
Click to collapse
There are about 10 threads on adb shell/rooting difficulties already. Why didn't you just bump an older one?

When you connect the usb to the phone what mounting setting did you select? It needs to be on charge only.

So, I have tried all methods posted here.
Click to expand...
Click to collapse
I have rooted two phones using various methods. The Easiest method? Who knows, but this is what I did, I in NO way take credit for this method. This is a culmination of various methods I found on various forums. Thank you to everyone here and on androidforums. Give it a shot.
1. Uninstall HTC sync and PDAnet (If installed)
2. Install drivers as specified for re-flash recovery from revoked team (HTML file has instruction in recovery zip - unrevoked.com/recovery/android-usb-driver.zip
3. Restart PC
4. Install PDANet - junefabrics.com/android/
5. Make sure to complete all steps for PDANet
6. Make default connection on phone, "Disk Drive" AND Turn on "USB Debugging"
7. Shut down the phone
8. Unclick the card
9. Volume down + Power into bootloader
10. Run adb shell in cmd prompt as loop(loop.bat)
11. Start recovery and wait .5 - 1 second after you hear the disconnect sound to click in your card.
12. You should see error device not found change to the other message IF LUCKY.
13. IF NOT,
- Let loop.bat continue to run
- Pull battery, unclick SD card
- Vol down + Power
- Recovery
- Listen for 2 tones (Count aloud..it helps)..
Quick - Insert card right after/during second (Change timing up slightly between tries)
Keep trying, my second root didn't take as long as my first but was easier. I think the unrevoked bootloader drivers with the PDANet usb drivers really make this easier. The other great thing is after you get root, you are set up to do the flash immediately using this method. Its just one more method that worked for me, hope this method helps you succeed. Good luck.

can anyone definitively explain to me which type of usb connection (e.g. "charge only", "disk drive") is necessary to get into shell and why? I have looked at what the various threads have to say about this. In fact that's the problem--I have found contradicting opinions posted on this matter. In my admittedly inexperienced mind, it seems like I should be fine either way, as long as adb recognizes my device.

davisbs999 said:
can anyone definitively explain to me which type of usb connection (e.g. "charge only", "disk drive") is necessary to get into shell and why? I have looked at what the various threads have to say about this. In fact that's the problem--I have found contradicting opinions posted on this matter. In my admittedly inexperienced mind, it seems like I should be fine either way, as long as adb recognizes my device.
Click to expand...
Click to collapse
I used disk drive the first time, and can not recall what I used on my second device. I see that it is contradicting throughout. I really do not think it even makes a difference because you are doing a battery pull and it never reaches that step on the phone. The important thing in my opinion are the drivers and timing.

Studmf said:
I used disk drive the first time, and can not recall what I used on my second device. I see that it is contradicting throughout. I really do not think it even makes a difference because you are doing a battery pull and it never reaches that step on the phone. The important thing in my opinion are the drivers and timing.
Click to expand...
Click to collapse
I rooted my cousin's Droid Incredible and I had Disk Drive enabled. I just want to say THANK YOU Studmf!!!!! I was stuck because I had HTC Sync installed and was stuck forever trying to root the Incredible. The instructions that I WAS following left that detail out.

[Q] Please help my phone isn't being recognized

It's very strange As it seems to be recognized by the computer but is not found by the AIO 1.13 batch file , I've never used Odin as all I've done is to root and install the SDX Remover. I am able to transfer files to and from my SD Card. I've tried numerous USB Cables including the one which initially allowed me to root, it's the only one of all of my many cables which allows windows to recognize the device and transfer files at usb 2.0 speeds all others either fail recognition or tell me to find a faster port. So I'm at a loss and really, desperately wish to update to froyo. I've tried every tip I've found up to and including shutting down my computer and unplugging it for more than 30 seconds. It's probably something quite simple that I'm overlooking,. I recall having to create a guest account in order to run the batch file and tried that as well. Any tips very much appreciated.
I think I'd like to revert my phone to stock(I think I did a full backup) upgrade to froyo officially than re root or not. I've been way to busy to spend too much time fussing with my phone.

If you are still on stock, which it sounds like you are....just follow the instructions on this post:
http://forum.xda-developers.com/showthread.php?t=963652
since you are already at stock...start from step 11 "download update.zip" and go from there.

[Help] A Myriad of Problems

Disclaimer: I am extremely illiterate when it comes to Android terminology, so you will most likely have to talk to me like I'm a child. I will try to explain my problems as best as I can, and will of course answer any questions. I also might over-explain, so I apologize for any length/redundancy issues.
Phone: XPERIA Play R800at, Android 2.3.3, Rooted with su and rom manager
My previous Play's touch screen stopped working, so the warranty granted me this new one. It's only two or three weeks old. The first problem I noticed was that I tried and could not delete anything off of my SD card. I tried formatting it a number of times, both in-phone (In Settings, as well as ES File Manager) and on Windows (both default formatter and a specific SD card formatter), but it would always revert back to what it's previous state would be. After researching a bit, I concluded it's probably faulty or failing, so I've ordered a new one that should get here within the week.
The second problem rose out of the first, I'm sure: My computer now doesn't recognize the sd card anymore. In SMC or MTP mode, it will not pop up on my computer and could not be recognized in PC Companion. On phone, the usual options you get in the notification bar (*dis*connect phone, etc.) do not show up. When connecting, the MTP USB Device driver attempts to install, but never succeeds. This is with USB debugging off and on, and every permutation I could think of.
Now, the most recent problem has been that the Home button doesn't work and there is no lock screen. Using the Terminal Emulator, I've attempted the popular fix (su -> echo -n ON > /efs/imei/keystr -> sync -> reboot) but I get the message /efs/imei/keystr directory nonexistent. I've factory reset my phone a number of times, reset settings, gone into recovery mode and reset things there, as well as caches, but all to no avail.
This could probably easily be remedied by just reflashing Android, or an older version or something, I'm sure, but given that my SD card is currently unreachable, I was wondering if anyone would know of a way I can fix these problems, or at least one of them. Thanks in advance.
If I've left anything out, please tell me and I will expound as best I can.
Other notes that might be of importance:
- It seems my *system* or whatever it would be is read-only, which seems like it could definitely be a problem. How do I fix this or do I even need to?
- I don't have the Setup Guide on my phone; I saw a thread that posited that this was a cause of the no lock screen problem.
Thanks again.

Driver install issue
Hello!
I'm not sure how to fix all of your problems. However, I have the same issue with my MTP drivers not installing when I connect the device. I've tried installing with various tools and the standard sony ericsson software. I believe I have the problem with the driver sorted out. I noticed that the drivers are, for some unknown reason, attempting to install to a TEMP folder. I would assume they are then being dumped from the TEMP folder after only a few seconds because when I install the driver it continues to ask me to install even when I click "finished."
You might try making sure the drivers are installing to the proper location if you haven't already. That might help with some of the issues.
On the same topic, do you know where the drivers are SUPPOSED to go in Windows XP? I'm fairly new to all of this stuff so I'm not sure exactly which folder in C:/WINDOWS the MTP driver for the Experia Play is supposed to go.
I hope this helps!
-Zot-

[Q] MTP USB Device?

I thought I was doing great after uninstalling bloatware. However, when I tried to connect my Note 2 to my PC via USB I received the error that MTP USB Device driver could not be loaded. Apparently I must have uninstalled something on my Note 2 that is not allowing me to connect to the PC via USB. I have been searching for days, read many postings with the same problem, downloading various Driver apps to no avail. I even downloaded and installed Samsung Drivers which also did not work. I still can use my USB plug from NOTE 2 to my Flash Drive to get stuff transfered to/from Note2/PC.
It never ends. Fix one thing and then another pops up. LOL
What else can I say except - H-E-L-P.

What de-bloater tool did you use ?
Does it show the apps it uninstalled ?
By default any de-bloater should only delete apps from /system/app and
/data/app.
Have you considered starting over by flashing root injected stock Rom?
Sent from my SGH-T889 using xda app-developers app

ciphercodes said:
What de-bloater tool did you use ?
Does it show the apps it uninstalled ?
By default any de-bloater should only delete apps from /system/app and
/data/app.
Have you considered starting over by flashing root injected stock Rom?
Click to expand...
Click to collapse
I did not use any de-bloater. I used Titanium Backup Pro (TBP) and have a complete list of all apks uninstalled.
In TBP under Backup/Restore all apks uninstalled are listed. Plus, I kept a list of all that I deleted.
No, I have not considered starting over by flashing root injected stock ROM. Thought about it, however, if I
do flash, I'm back to square one.
If I don't resolve this one problem, I will remain at this point until new OS comes out. I do have a work around for time being.
I do appreciate your help, time and concern. Thank you.
What really amazes me is that this problem is all over the Internet and I can't find a simple solution. I have Googled it,
been on here doing searches, reading postings, etc. I have even tried Driver Booster.

asctony said:
I did not use any de-bloater. I used Titanium Backup Pro (TBP) and have a complete list of all apks uninstalled.
In TBP under Backup/Restore all apks uninstalled are listed. Plus, I kept a list of all that I deleted.
No, I have not considered starting over by flashing root injected stock ROM. Thought about it, however, if I
do flash, I'm back to square one.
If I don't resolve this one problem, I will remain at this point until new OS comes out. I do have a work around for time being.
I do appreciate your help, time and concern. Thank you.
What really amazes me is that this problem is all over the Internet and I can't find a simple solution. I have Googled it,
been on here doing searches, reading postings, etc. I have even tried Driver Booster.
Click to expand...
Click to collapse
Sometimes we miss something small and obvious. Have you disabled USB debugging mode in Developer options?

AE74 said:
Sometimes we miss something small and obvious. Have you disabled USB debugging mode in Developer options?
Click to expand...
Click to collapse
Yes, I just tried that based on your suggestion. However, still got the same: MTP USB Device error. Thanks for your help.

asctony said:
Yes, I just tried that based on your suggestion. However, still got the same: MTP USB Device error. Thanks for your help.
Click to expand...
Click to collapse
Can you check your phone setting by dialing *#7284#?
Method 3 on the link below.
http://www.danrichard.com/2013/06/1...nect-to-pc-via-usb-with-unknown-device-error/

AE74 said:
Can you check your phone setting by dialing *#7284#?
Method 3 on the link below.
http://www.danrichard.com/2013/06/1...nect-to-pc-via-usb-with-unknown-device-error/
Click to expand...
Click to collapse
Tried this and again no success.
Method 3 – Ensure you have the right settings By default my phone was already set to the right settings for USB file transfers so I’ll assume most of these ship with the same configuration, hence why I have this as method 3. I found this on a forum and while it did not work for me, it seems a few other folks declared it a success.
1. Launch the phone key pad on your note and press *#7284# (don’t forget to start with that * symbol!) When you press the last pound sign (#) this will bring up an option that will allow you to change your USB connection settings (modem or PDA) – change it to PDA.
I did not get any option that allowed me to change the USB Connection settings when I entered *#7284#. So I dialed that number and got an error Unable to process request.
Tried new USB cable and it still tried to load/install device drivers but not successful. Same error MTP USB Device Failed.
Thanks again for trying to help. I do appreciate your help and time. Still looking for a resolution.

asctony said:
Tried this and again no success.
Method 3 – Ensure you have the right settings By default my phone was already set to the right settings for USB file transfers so I’ll assume most of these ship with the same configuration, hence why I have this as method 3. I found this on a forum and while it did not work for me, it seems a few other folks declared it a success.
1. Launch the phone key pad on your note and press *#7284# (don’t forget to start with that * symbol!) When you press the last pound sign (#) this will bring up an option that will allow you to change your USB connection settings (modem or PDA) – change it to PDA.
I did not get any option that allowed me to change the USB Connection settings when I entered *#7284#. So I dialed that number and got an error Unable to process request.
Tried new USB cable and it still tried to load/install device drivers but not successful. Same error MTP USB Device Failed.
Thanks again for trying to help. I do appreciate your help and time. Still looking for a resolution.
Click to expand...
Click to collapse
Perhaps you may not have the system file Phone Utility 1.0.0 or corrupted.

AE74 said:
Perhaps you may not have the system file Phone Utility 1.0.0 or corrupted.
Click to expand...
Click to collapse
Yes, I do have Phone UTL as shown in TBP. How do I access it? I can't under the Method 3.

asctony said:
Yes, I do have Phone UTL as shown in TBP. How do I access it? I can't under the Method 3.
Click to expand...
Click to collapse
I am trying to find out if you have all the files and compare with my files to find out why I can access phone utility and you can't. Your issue may be the driver or files idk. Tbh, I am not an expert. Just another android enthusiast trying to help. I have Tweaked Rom so mine may be different. I have found 2 system files in TBU, Service Mode and MTP Application. Do you have them also? Does service mode work for you when you dial, for example, *#0011#?

SUCCESS-Thanks to Y-O-U!!!!
AE74 said:
I am trying to find out if you have all the files and compare with my files to find out why I can access phone utility and you can't. Your issue may be the driver or files idk. Tbh, I am not an expert. Just another android enthusiast trying to help. I have Tweaked Rom so mine may be different. I have found 2 system files in TBU, Service Mode and MTP Application. Do you have them also? Does service mode work for you when you dial, for example, *#0011#?
Click to expand...
Click to collapse
Yes, I uninstalled both of those. Re-installed both Service Mode and MTP Application, powered off both PC and Note 2. Rebooted, USBd Note 2 to PC and SUCCESS!!!!!!!!!
Thank you very much for your help!!!!! You are no longer a Jr. U R A SR!!!

[Q] After installing 5.0.1 on unlocked rooted n7 I can no longer write to sdcard

OK so: I updated my N7(2013) to lollipop 5.0.1 using the Skipsoft toolkit and now I cannot restore my data from a backup on my windows 7 x64 PC.
The N7 is unlocked, rooted, and running lollipop 5.0.1. A few weeks ago the USB port stopped working due to the well-known physical weakness of the N7's USB socket. Fortunately I had made backups and copied them to my PC (windows 7 x 64 up-to-date) via USB just prior to the failure. The backups were a TWRP nandroid made from recovery, a TiBackup of all the apps and app data, and I copied the entire contents of sdcard (/storage/emulated/legacy) to a folder on my pc via drag-and-drop using explorer. (MTP mode on the N7 seen as "Nexus 7\Internal storage" by windows.)
Prior to sending it in for repairs I deleted all my personal data from sdcard, did a factory reset using TWRP recovery, and verified that the phone would boot into android lollipop 5.0.1. I paid iResQ to fix the port, which they did.
When I got it back, I hooked up the N7 to the PC via USB and attempted to copy the files back to sdcard, by dragging them in the opposite direction using explorer. I did not work. "Nexus 7\Internal storage" is read only! I was unable to change the permission on the N7 using explorer. (Apparently since the hated MTP mode makes the PC think that the N7 is not a storage device with permissions). I tried using adb push (did not work). I tried to change the permissions of sdcard on the N7 itself using root explorer (and ES file explorer and xplorer -- did not work). I tried adb shell followed by su then chmod (did not work). I tried "mkdir test" at the su prompt to see if that would work and was told "mkdir failed for test, Read-only file system".
So how do I restore my apps and data? How do I make "/" read-write? Does lollipop make an N7 into a ROM?
I think I'll go back to kitkat.
--------------------------------------
Some hours later~
I tried removing 5.0.1 and went back to kitkat, Android 4.4.4 (KTU84P). I am able to copy files from pc to sdcard via wireless using an explorer on the N7. Nevertheless, using an explorer on the pc I cannot copy a file from it to the n7 via usb . I don't get it. What is going on here?
----------------------------------------
The next day~
It appears to me that the problem with the MTP transfer from the PC to the N7 is on the PC side. Apparently when I plug the N7 into the PC via USB, a file transfer window is supposed to appear on the PC. It does not.
That does not explain why, however I was completely unable to write (via usb, wireless, adb, or on the N7 itself) to the virtual sdcard when the N7 was on lollipop 5.01 but works with KitKat 4.4.4. Any clues? Anyone?

Amazing. All the people who read this forum and not a one has a clue as to why I cannot write to my N7.

lamoid said:
Amazing. All the people who read this forum and not a one has a clue as to why I cannot write to my N7.
Click to expand...
Click to collapse
Yeah that's gonna make people want to help you.
Since you seem wholely incapable of searching for yourself, here you go- http://forum.xda-developers.com/showthread.php?p=56720490

Maybe you did not want to, but you did help me _MetalHead_. Thank you.

lamoid said:
Maybe you did not want to, but you did help me _MetalHead_. Thank you.
Click to expand...
Click to collapse
You're welcome. And I did want to help, but that comment that you posted was rather rude. Next time, instead of acting entitled, a simple "can anyone please help?" would have sufficed.
Anyways... I take it you got it fixed?

I agree that was rude. And I apologize for it. However, on 18 January, I asked after not getting any responses, "Any clues? Anyone?" I checked for a response every day after that and by the 30th was rather frustrated at not having received one. Also I had searched the board extensively and could not find anything like my problem. Clearly I did not use the correct keywords or I would have found the page you pointed me to.
I don't know if that will solve the problem because I need to try to install the upgrade again then try it. Which I will soon.
Nevertheless I do greatly appreciate you for having helped me _MetalHead_ despite the rudeness of my request.

lamoid said:
I agree that was rude. And I apologize for it. However, on 18 January, I asked after not getting any responses, "Any clues? Anyone?" I checked for a response every day after that and by the 30th was rather frustrated at not having received one. Also I had searched the board extensively and could not find anything like my problem. Clearly I did not use the correct keywords or I would have found the page you pointed me to.
I don't know if that will solve the problem because I need to try to install the upgrade again then try it. Which I will soon.
Nevertheless I do greatly appreciate you for having helped me _MetalHead_ despite the rudeness of my request.
Click to expand...
Click to collapse
No worries man, I understand how frustrating it can be, especially when the life of your cherished Nexus 7 hangs in the balance. Keep me posted if you get it worked out or not.