TP Toolbox Media Mount FAILED - TouchPad Q&A, Help & Troubleshooting

I am attempting to install Android via TP Toolbox and am having a similar problem that others have reported. I can load TP Toolbox, but the media mount portion fails and my Windows 7 x64 machine never sees the HP Touchpad volume. Here's the twist:
I have done this 2 previous times with different Touchpads, the same Windows 7 machine, and the same USB cable, and it worked fine. I have already tried a different cable, same results; works on other TPs, but not this one. So maybe it's NOT the cable, as has been the case with the other instances I've read through on this forum. Unfortunately, I don't have an HP OEM cable to test against.
I'm attaching the klog.txt in the hopes a reason can be found in there. Thanks in advance.

ChefDan said:
I am attempting to install Android via TP Toolbox and am having a similar problem that others have reported. I can load TP Toolbox, but the media mount portion fails and my Windows 7 x64 machine never sees the HP Touchpad volume. Here's the twist:
I have done this 2 previous times with different Touchpads, the same Windows 7 machine, and the same USB cable, and it worked fine. I have already tried a different cable, same results; works on other TPs, but not this one. So maybe it's NOT the cable, as has been the case with the other instances I've read through on this forum. Unfortunately, I don't have an HP OEM cable to test against.
I'm attaching the klog.txt in the hopes a reason can be found in there. Thanks in advance.
Click to expand...
Click to collapse
I have the same problem only I have 2 tablets and i installed tp toolbox wiped webos installed andriod on the first it went so smooth I figure why not do both well cause now I have on functional and one thats not Im unable to get webos or anything It boots with option restart webos restore or shutdown and cant get any os on it now but atleast one of mine works great databuilds are the way to go but its a 50 50 chance youll end up with one only good for parts Ive tried aking on the forums where the guy who released tp toolbox but have been denied access for asking questions and no replies. I only got one of them to mount after tp toolbox android install. It is not the cable its not the os win7 cause I tried my two back to back and their the same model# If you figure it out let me know

ddgls08 said:
I have the same problem only I have 2 tablets and i installed tp toolbox wiped webos installed andriod on the first it went so smooth I figure why not do both well cause now I have on functional and one thats not Im unable to get webos or anything It boots with option restart webos restore or shutdown and cant get any os on it now but atleast one of mine works great databuilds are the way to go but its a 50 50 chance youll end up with one only good for parts Ive tried aking on the forums where the guy who released tp toolbox but have been denied access for asking questions and no replies. I only got one of them to mount after tp toolbox android install. It is not the cable its not the os win7 cause I tried my two back to back and their the same model# If you figure it out let me know
Click to expand...
Click to collapse
If as you have stated there is a 50% chance of bricking your Touchpad pad there would be hundreds if not thousands of members posting about it not just 2.
Please read the rules, you cannot post in the developers forum because you have not made 10 USEFUL posts.
The guy as you put it is Jcsullins a highly respected Developer on this and other forums. So how you can expect any help when you haven't even read the rules and slag of the man you has continued to bring life to a 3 year old device that was never intended to run Android in the first place beggars belief.
Have a nice day.

misunderstood
sstar said:
If as you have stated there is a 50% chance of bricking your Touchpad pad there would be hundreds if not thousands of members posting about it not just 2.
Please read the rules, you cannot post in the developers forum because you have not made 10 USEFUL posts.
The guy as you put it is Jcsullins a highly respected Developer on this and other forums. So how you can expect any help when you haven't even read the rules and slag of the man you has continued to bring life to a 3 year old device that was never intended to run Android in the first place beggars belief.
Have a nice day.
Click to expand...
Click to collapse
sorry if you think that I am putting down jcsullins, you obviously cant read between the lines! If I didnt like jcsullins or all the hard work he put into all of this why would I be on here and using these forums and trying to get help from him and all that follow. Im just frustrated that my first touchpad that I used the tp toolbox on wents so damn smooth with little imput or know how to do and took less than 8 min. then I tried my other (identical) touchpad (serial# and all) and couldnt get it to mount,. then I tried reinstalling webos and that failed, tried the hp webosdoctor to reinstall webos I did as described used the volume up to initiate webos restore and the webdoctor connects to it and only runs for about 2-4 min than automaticaly dissconects it , it switches from the usb symble to the hp logo and now I am unable to do anything with it,
I know I jumped the gun a little but in time Im sure Ill be all over this site so forgive me if im a bit frustrated that no one has figured out a solution yet and I thought if I created a little wave to get some attention, and to also help others that are in the same boat im in to let them know they may have done everything as described in the instuctions and still not get the device to mount thus confirming what they already know that its not the cable, not the windows 7 64bit but most likley some internal part of the touchpad maybe the usb port board or the one he designed this all for was a later model with diff guts than the eirlier models hp put out, who really knows. Im thinking of taking mine appart again and swapping the usb board, but wanted to see if someone had a fix for it before doing that again
to jcsullins you dont really need to here me say that I apprecitate all that youve done, you should allready know that by me trusting all your software and installing it in my device, and recomending your site to all my friends and some strangers!! I dont make much $ or I would gladly fork over some. but I work at a car wash hence the no money but I hope maybe one of the people I refer you too might

Not a problem, this is what I used after I managed to completely mess up my TouchPad well over a year ago and it brought it back to life.
http://forum.xda-developers.com/showthread.php?t=1426244
Pay particular attention to the first post on page 12. Also with all the commands use copy and paste as it avoids any possible typo's.
Good luck and all the best.. ☺

sstar said:
Not a problem, this is what I used after I managed to completely mess up my TouchPad well over a year ago and it brought it back to life.
http://forum.xda-developers.com/showthread.php?t=1426244
Pay particular attention to the first post on page 12. Also with all the commands use copy and paste as it avoids any possible typo's.
Good luck and all the best.. ☺
Click to expand...
Click to collapse
SSTAR, I ran across your post the other day and have already tried this. It fails for me at Step 6. After the HP logo appears, the Touchpad disconnects from the PC and novacom fails. If you run novaterm it just says not connected. This is pretty much the same failure point of WebOS doctor. I just went out and bought a brand new USB cable and will try this again in the morning and report back.

ChefDan said:
SSTAR, I ran across your post the other day and have already tried this. It fails for me at Step 6. After the HP logo appears, the Touchpad disconnects from the PC and novacom fails. If you run novaterm it just says not connected. This is pretty much the same failure point of WebOS doctor. I just went out and bought a brand new USB cable and will try this again in the morning and report back.
Click to expand...
Click to collapse
Pretty much the same for me, that is where the first comment on page 12 helped me and everything was done through command prompt.
Good luck.

FIXED!!
sstar said:
Pretty much the same for me, that is where the first comment on page 12 helped me and everything was done through command prompt.
Good luck.
Click to expand...
Click to collapse
And the verdict is... IT WAS THE USB CABLE. Sstar, I poured over your post and the comment you mentioned. All those lvm.static commands are done by TP Toolbox when you choose Install Android, so I couldn't see where that made a difference. But I tried it anyway. I couldn't figure out how to get a terminal prompt using novacom when it would keep losing connection to the machine, so I had to improvise. I had previously created an Ubuntu 12.04 USB boot stick and downloaded jcsullins' tpdebrick to fix one of the two 16GB touchpads previously, so I edited the tpdebrick script to prematurely exit at line 546, right above where it starts copying the A6 firmware files to the Touchpad. Once there I established a TTY session to the touchpad and manually entered all the commands to configure the Android volumes. However, I never could get WebOSDoctor installed as it recommends in the rest of the post, it kept bombing out at 4%, just like before. I think it must be because some folders and files it's expecting to exist on the Touchpad are missing after you do a Complete Data Reset in TP Toolbox. Finally, out of desperation, I loaded TP Toolbox again and chose Mount Media Volume, in the hopes that maybe I could still get the ROM, recovery and gapps files onto the machine and install. Well, it worked. The mounted Volume was not named HP TOUCHPAD as it was supposed to be, but it was there, and I was indeed able to copy the files to the TP and installed CM11.
Then I thought about it some more. So why would it matter that I manually configured the Android volumes? Turns out it didn't. I did all the above using a brand new 6 ft USB to micro USB cable I bought at Office Depot (Ativa Item #833-445, if anybody's interested). I decided to try the whole process again, using one of the USB cables I had previously, and... the Media Volume would not mount. Tried a 3rd USB cable. No mount again. The new cable was the only one that worked. Why did those cables not work on the 16GB Touchpads, when they worked just fine on 2 previous 32GB Touchpads? I have no idea. I even went back and tested the TP Toolbox Mount Media Volume option on the 32GB Touchpad, and both cables still work, but will NOT work on a 16GB Touchpad. I'll leave that for greater minds than mine to ponder.
Learned a few interesting things along the way:
- If you ever need TP Debrick, you will save yourself a lot of frustration if you use Ubuntu v 12.04 vs the current 14.04. The older version will download the abd and fastboot tools for you; 14.04 requires that you find them and install yourself.
- If your media volume fails to mount in TP Toolbox, like if you had a bad cable, you *MUST* reboot the Touchpad and reload TP Toolbox with a good cable before trying it again. It won't work otherwise.
- Using Ubuntu on a laptop with a mouse touchpad is the most frustrating thing imaginable. Use a standard mouse if you want to keep your blood pressure down.
- If you get the 'There was an error communicating with Google Servers' error when trying to create or sign into your Google account when going through the initial setup, set up, (and you don't have 2 factor authentication on your Google account) check the version of gapps and make sure that is named gapps-kk-20140105.zip with a size of 87,179,530 bytes. There is another, smaller version of the same file out there that apparently does not have Google Play Services in it. If you do have 2 factor authentication, you'll need to create an app password for the Touchpad or turn off 2 factor authentication.
Hope this helps someone!

ChefDan said:
SSTAR, I ran across your post the other day and have already tried this. It fails for me at Step 6. After the HP logo appears, the Touchpad disconnects from the PC and novacom fails. If you run novaterm it just says not connected. This is pretty much the same failure point of WebOS doctor. I just went out and bought a brand new USB cable and will try this again in the morning and report back.
Click to expand...
Click to collapse
I also have simular problem when I try to use webos doctor I get it all set up and then I can get it to start running but within 4min the hp logo pops on the device and it disconects itself and then stops running leaving my device useless, Ive tried useing the tp toolbox following the directions to the letter and then running webos doctor and still nothing, I know you guys are alot brighter than me and hope you find a fix soon thanks

ddgls088 said:
I also have simular problem when I try to use webos doctor I get it all set up and then I can get it to start running but within 4min the hp logo pops on the device and it disconects itself and then stops running leaving my device useless, Ive tried useing the tp toolbox following the directions to the letter and then running webos doctor and still nothing, I know you guys are alot brighter than me and hope you find a fix soon thanks
Click to expand...
Click to collapse
This sounds like the exact place I was. I never got WebOS to install; if you did a 'Complete Data Reset' from TP Toolbox, WebOS is gone forever. However, you can skip installing WebOS and just Install Android. TP Toolbox will create the Android voilumes and mount the media volume, where the next step is to copy a recovery ROM, your Android ROM, and GApps file to the TTINSTALL folder on the media volume. Then, Eject the media volume in Windows, and Unmount Media volume in TP Toolbox. TP Toolbox will check the ZIP files and install Android.

ChefDan said:
This sounds like the exact place I was. I never got WebOS to install; if you did a 'Complete Data Reset' from TP Toolbox, WebOS is gone forever. However, you can skip installing WebOS and just Install Android. TP Toolbox will create the Android voilumes and mount the media volume, where the next step is to copy a recovery ROM, your Android ROM, and GApps file to the TTINSTALL folder on the media volume. Then, Eject the media volume in Windows, and Unmount Media volume in TP Toolbox. TP Toolbox will check the ZIP files and install Android.
Click to expand...
Click to collapse
I appriciate the advice but I was trying to reinstall webos or anything cause after I wiped webos with tptoolbox it wouldnt mount so no ttinstall folder to move all of the roms to

ddgls088 said:
I appriciate the advice but I was trying to reinstall webos or anything cause after I wiped webos with tptoolbox it wouldnt mount so no ttinstall folder to move all of the roms to
Click to expand...
Click to collapse
Ddgls088 - OK, just trying to help here. Re-read what has been posted previously. If the media mount fails in TP Toolbox, you've most likely got a bad USB cable. It may work for other purposes, or on other devices but there's something wrong with it. What is happening to you is exactly what happened to me. Buy a new, good quality USB cable and try it again from the top, with the complete data reset, then Install Android. If you have a good USB cable, the media volume will mount. Good Luck!

For those still having issues, please try the version of Touchpad Toolbox (v41) I just released in this post:
http://forum.xda-developers.com/show...&postcount=293
Note that you will need to use one of the new Recoveries linked from that post.
If you still have problems with that version of TPToolbox, let me know in this thread.
Also, for those having issues re-installing webOS after a "Complete Data Reset," see the second
set of steps in this post:
http://forum.xda-developers.com/showpost.php?p=52922166&postcount=64

Related

Root not working after ICS (ADB can't see it)

So I just updated my Bionic to ICS, YAY!
But, root isn't working, BOO! :crying:
I am relatively knowledgeable in this stuff; it is both my profession and my hobby. Investigating this issue has led me to believe that my problem is that the ADB interface does not show up in device manager (Mass Storage, MTP, and PTP mode have the same result) on Windows 7 Ultimate x64. When the device is connected in AP fastboot, however, the driver does show up and works fine. Additionally, when I try to manually add the driver, it fails to start (code 10).
What does show up, however, is the Motorola USB Networking Driver (MTP only), under network adapters.
The upgrade to ICS was performed with SamuriHL's HoB (ADB), and in an effort to resolve this issue, I did it again with HoB (Fastboot).
Can somebody please help?
Thanks,
Overkill
EDIT: I downloaded the SDK and ADB still doesn't list my device. I do know that the IP used by the Motorola driver is 192.168.137.2 for my device (.1 for my PC) and that "adb connect 192.168.137.2" fails to connect on the default port (maybe another port?)
Thanks again! I feel naked and powerless without my root =(
Do you have USB debugging enabled under Developer Options?
Yes, I do. I have tried disabling/re-enabling it as well to no avail.
I appreciate the KISS approach, but I've gone over the checklist on every how-to and I am confident that nothing is missing.
I tried the phone on another computer and with several different USB cables and no luck. I have all 64-bit machines, but I can also try my XP VM and maybe that'll behave properly ^_^ Or an actual XP machine at one of my jobsites that still won't pay to upgrade their equipment from 2002.
OverkillSD said:
Yes, I do. I have tried disabling/re-enabling it as well to no avail.
I appreciate the KISS approach, but I've gone over the checklist on every how-to and I am confident that nothing is missing.
I tried the phone on another computer and with several different USB cables and no luck. I have all 64-bit machines, but I can also try my XP VM and maybe that'll behave properly ^_^ Or an actual XP machine at one of my jobsites that still won't pay to upgrade their equipment from 2002.
Click to expand...
Click to collapse
I had this problem, reinstalling latest Motorola device manager fixed it for me.
No go on that either.
I gave up and did a factory restore, it's working fine now. Going to analyze the scripts used by House of Bionic and see if it's possible to work backwards and see if there was a way to do it without losing data, for posterity's sake.
OverkillSD said:
I gave up and did a factory restore, it's working fine now. Going to analyze the scripts used by House of Bionic and see if it's possible to work backwards and see if there was a way to do it without losing data, for posterity's sake.
Click to expand...
Click to collapse
You have to remember to reboot with the phone in all the different connection modes for multiple different drivers loaded.
OverkillSD said:
I gave up and did a factory restore, it's working fine now. Going to analyze the scripts used by House of Bionic and see if it's possible to work backwards and see if there was a way to do it without losing data, for posterity's sake.
Click to expand...
Click to collapse
Weird. FDR only kills user settigns and user apps - so, it seems like there was an app that was blocking ADB access. Which is extremely strange, b/c that should not happen, unless you have some sort of firewall on the BIONIC itself (or else something like DroidSheppGuard running).
beray5 said:
You have to remember to reboot with the phone in all the different connection modes for multiple different drivers loaded.
Click to expand...
Click to collapse
Not always true - you may need to reboot the phone. I can switch from any mode to any other mode and the connection pops up within 5 seconds every time. Of course, I'm running Win 7 Ult x64, and I only use the direct connect ports on my computer, no hubs, no USB 3 ports, and I never install the Motorola Device Manager software, only the direct USB drivers that I extract from the installer myself. Any one of those may be a factor in why it works for me, or some combination thereof.
However, I do know that I am not the only one for whom the switching works without rebooting either computer or phone....

[Trifecta] Jelly Bean Root

****Follow Info, Warnings & guides on associated links / pages****
For those of you reading this and in this forum, and if you've rooted before, flashed a rom, or anything like that and got it to work, DO NOT be intimidated by using this method.
I found I actually quite liked Ubuntu (it was my first time using it myself). And it's rather easy.
This is the page I followed, and if you scroll down most of the way (use the one at post #30 ircc) there's a video too. I set up my screen so it was just like in the video, plus a "window" to watch the video too. The directions are exact, what I liked about the video is you could see it run and the results, which helped me realize where things went wrong after it failed about 3 times or so.
***Thanks to drjbliss (method), SamuriHL (HoB & more), & Tomsgt123 (video)***
Things upfront:
I used a Bootable USB, You can do it with a Bootable / "live" CD, but admittedly I thought USB was quicker to set-up and in hindsight probably was beneficial. So that's what I recommend.
Get Ubuntu (img/iso) & follow the directions from HERE.
Make the USB, then restart your computer, and at boot screen, choose boot from USB.
Here's where it saved me and and I'll recommend something else here, not in the instructions... yes it's going to take a bit longer but in the end I spent almost a whole Saturday doing this and this would've made it about an hour had I done it first. It was the solution to 2 errors I had, that took a while to realize where they were and find a fix.
In Ubuntu, open a "terminal" which is like a windows cmd / command window.
I couldn't find a button or anything on a menu to do this so I found out it's either alt + t or ctrl + alt + t.
at the Ubuntu terminal command prompt:
use these 2 commands to update Ubuntu and Samba.
sudo apt-get update
sudo apt-get upgrade
[IIRC] The Ubuntu one will tell you it needs and additional 250 (or so) MB's hit ok or accept and let it update. Then do the next and update Samba.
I'm not exactly sure but I doubt I would've been able to do this with a cd being that it couldn't write to it.
This took care of all errors I ran into using this Root method, and it was a bit frustrating because if you don't know what you're looking for or at, you can get to the end and it says exploit finished or complete or something and you think you're good to go.
On to the root instructions & Video...
I opened (2) terminal windows, you have to manually put them on the same screen or it will move them to multiple ones and that doesn't help so much.
If it does, use the button on the side that looks like (4) windows and pick & drag everything back to one screen.
Errors or what to look for:
when you run this command: sudo apt-get install samba
if it says (something) "unknown" or "Failed" - Samba didn't install, try again. (update if you skipped that part)
when you try to connect remotely over WIFI...
If you get "network connection error / failed", Samba didn't install, or Samba needs update (if you skipped that), or make sure you use the right IP address, a few of them will come up. I found for me it had nothing to with my network and I had the right IP the first time I tried.
****NOTICE****
Ubuntu will let you keep going and continue to run the commands seemingly normally. Even to the end and tell you "exploit complete" (or something like that) So if you get to the end and you don't have root go back and examine your terminal screen. Compare it to the one in the video, something won't match, and there's the issue.
I did notice the "numbers" didn't always match as it ran thru the processes, but make sure it looks like your getting the same type of results and runs thru the process.
I needed to update Ubuntu to update Samba that's why I recommend doing both first.
Once you set-up & update your USB the whole thing shouldn't take more than 15-20 mins or so.
Good luck.
It's really not hard, just follow the instructions.
I tried following the steps for Jelly Bean root, but I think the samba share thing may be holding me back. I know how to do it, that's not the problem. The problem is, I don't have a wifi setup at home, so I wouldn't be able to connect to the Ubuntu live image even if I could set up my Files app the way I'm instructed to. When I go to the section in the Files app to input the information, I don't have all the fields show up for the necessary information. Plus I have a version of Ubuntu running on my laptop that shouldn't require a wireless connection between my phone and the computer, since I can just plug the thing into it. I know this method has worked for many people, and I'm not exactly a noob, my first Android phone was the very first one, the G1. With each Droid style phone I got, I had it rooted within either hours or days, so I am capable of doing it. Also, I know there either isn't a one-click method yet or if there is I can't find it, but is there a way to circumvent the whole samba thing so I don't have to mess with the wifi connect? Finally, and thank you for your patience in reading such a long text, worst case scenario; if I were to try to fxz back to ICS stock (I know it'd more-than-likely brick my phone), is there an unbrick method for those of us who've let themselves spend way to much time obsessing over their phone (I tend to get a little tunnel visioned when it comes to this stuff), or would I be totally screwed? As many on this forum, thanks for all the hard work, and I apologize in advance if I seem a little whiny about this. I should point out that even without the wireless connection between the phone and the computer, the program still runs and displays the terminal screen that roots the phone. It stops just a few lines after the "push a hardware button" phase to make it vibrate. It never vibrates, but Superuser does get copied to the phone, it just install the binaries for it.

[Q] Not recognizing after installing SDK

Hopefully someone can help me because I have been stuck for days and I have researched nonstop. My phone was working fine and could connect to my pc a week ago. I installed Android SDK and eclipse so I could try and develop an application. Now that I have installed it, my phone will not connect to my PC. My tablet will not either. I have ticked the USB debugging on and off, updating drivers from Motorola as well as the Google usb drivers from the sdk manager. When i type in the command for adb devices, no device is shown. In the device manager, my device does not show up. It doesn't even charge anymore. I have the original cords, but have tried others just in case. I am running Windows 8.0 if that makes a difference.
dcon025 said:
Hopefully someone can help me because I have been stuck for days and I have researched nonstop. My phone was working fine and could connect to my pc a week ago. I installed Android SDK and eclipse so I could try and develop an application. Now that I have installed it, my phone will not connect to my PC. My tablet will not either. I have ticked the USB debugging on and off, updating drivers from Motorola as well as the Google usb drivers from the sdk manager. When i type in the command for adb devices, no device is shown. In the device manager, my device does not show up. It doesn't even charge anymore. I have the original cords, but have tried others just in case. I am running Windows 8.0 if that makes a difference.
Click to expand...
Click to collapse
do you actually need eclipse? did you try uninstalling everything to see if you could connect again?
likely you do not need eclipse and should have just installed the sdk but i have never had the problem you are describing. i would just uninstall everything and get it working again then re-try installing whatever you want to
jayboyyyy said:
do you actually need eclipse? did you try uninstalling everything to see if you could connect again?
likely you do not need eclipse and should have just installed the sdk but i have never had the problem you are describing. i would just uninstall everything and get it working again then re-try installing whatever you want to
Click to expand...
Click to collapse
I may sound stupid because I don't know enough about this.. But don't I need eclipse to make an application? I am going to try to make an application for my class, and thought I needed eclipse and the sdk. I am currently uninstalling it all to see if it helps any.
dcon025 said:
I may sound stupid because I don't know enough about this.. But don't I need eclipse to make an application? I am going to try to make an application for my class, and thought I needed eclipse and the sdk. I am currently uninstalling it all to see if it helps any.
Click to expand...
Click to collapse
well there are other IDEs out there besides eclipse but you can use that one. Sounds like you are about to have a pretty big uphill battle creating an app lol.
But if you get everything to work without anything installed, try re downloading and installing everything without your phone plugged into the computer. I have no idea if that would work or if it would matter at all but it could i guess. that's where i would start. it should screw anything up on your computer that wouldn't let you connect your phone but maybe something weird happened.
i just did some research and only found people having similar problems with samsung phones. And the solution was downloading some kies program for samsung phones. so idk what else to tell you.
jayboyyyy said:
well there are other IDEs out there besides eclipse but you can use that one. Sounds like you are about to have a pretty big uphill battle creating an app lol.
But if you get everything to work without anything installed, try re downloading and installing everything without your phone plugged into the computer. I have no idea if that would work or if it would matter at all but it could i guess. that's where i would start. it should screw anything up on your computer that wouldn't let you connect your phone but maybe something weird happened.
i just did some research and only found people having similar problems with samsung phones. And the solution was downloading some kies program for samsung phones. so idk what else to tell you.
Click to expand...
Click to collapse
Ahhhh it worked! My pc will finally recognize my device. I'm not sure what the problem was either, I got the same results when I was researching. No one seemed to have the exact same problem.
I'm definitely going to have some problems trying to create an app haha.. The SDK came with eclipse, so I just assumed I had to use it. I'm pretty sure I'm in over my head! Is there another IDE that you recommend? The easiest method is the method I'm going to take for sure.
dcon025 said:
Ahhhh it worked! My pc will finally recognize my device. I'm not sure what the problem was either, I got the same results when I was researching. No one seemed to have the exact same problem.
I'm definitely going to have some problems trying to create an app haha.. The SDK came with eclipse, so I just assumed I had to use it. I'm pretty sure I'm in over my head! Is there another IDE that you recommend? The easiest method is the method I'm going to take for sure.
Click to expand...
Click to collapse
eclipse is fine. a lot of people use it. just search through xda and you will find threads teaching you how to build apps, but unless you are going to spend a good amount of time or already know how to code, prepare to be ticked off.
jayboyyyy said:
eclipse is fine. a lot of people use it. just search through xda and you will find threads teaching you how to build apps, but unless you are going to spend a good amount of time or already know how to code, prepare to be ticked off.
Click to expand...
Click to collapse
I have 10 weeks left to make it, so I've got plenty of time. I know how to code a little bit, but I'm not very good at it. I'll give eclipse a try and see if it works this time. Thanks for the help!
dcon025 said:
I have 10 weeks left to make it, so I've got plenty of time. I know how to code a little bit, but I'm not very good at it. I'll give eclipse a try and see if it works this time. Thanks for the help!
Click to expand...
Click to collapse
no prob

[Q] Help! Hard reset done and gallery hasn't restored.

So after encountering the annoying 505 error I did a full back up via the Backup app as sync manager on the laptop wasn't playing ball.
Did the hard factory reset and then restored from the back up file I had made 10 minutes beforehand.
Most things have restored but I went to check a picture and ALL GONE!
Things like whatsapp messages and contacts didn't restore either.
What can do to recover the lost images?
and typically none of it worked to solve the 505 error.
I know this isn't the usual standard of question on this forum but is anyone able to shed some light on my problem?
Does the HTC Backup program, back up images or is that an oversight on my part?
ok so it seems that i'm an idiot and htc doesn't back up images on an htc account back up.
I'm now trying to run my phone through recovery software (MagicCute Recovery) but the program won't recognize the phone, I guess because it's not a mass storage device and connects via MTP?
I read a guild to turn on developer mode and then turn on USB debugging but that hasn't made any difference.
If there a way to plug my phone in and the computer to recognize it as a mass storage device?
Paul_TDi said:
ok so it seems that i'm an idiot and htc doesn't back up images on an htc account back up.
I'm now trying to run my phone through recovery software (MagicCute Recovery) but the program won't recognize the phone, I guess because it's not a mass storage device and connects via MTP?
I read a guild to turn on developer mode and then turn on USB debugging but that hasn't made any difference.
If there a way to plug my phone in and the computer to recognize it as a mass storage device?
Click to expand...
Click to collapse
check google playstore for undelete software, plenty on there, be careful about how much you install or uninstall.
Dont know if your aware of this, but nothing is ever really deleted, its flagged as safe to be overwritten and hidden from the user, too much installing or un-installing apps will overwite the flagged images.
Paul_TDi said:
ok so it seems that i'm an idiot and htc doesn't back up images on an htc account back up.
I'm now trying to run my phone through recovery software (MagicCute Recovery) but the program won't recognize the phone, I guess because it's not a mass storage device and connects via MTP?
I read a guild to turn on developer mode and then turn on USB debugging but that hasn't made any difference.
If there a way to plug my phone in and the computer to recognize it as a mass storage device?
Click to expand...
Click to collapse
I am sure that when connected to a Linux machine it shows as an external drive...not sure if that helps at all ?
If what i suggest is true then you can run Linux within windows from a USB drive,but clearly your recovery software has to be a linux compatible version.
Just a suggestion rather than fact!
Seanie280672 said:
check google playstore for undelete software, plenty on there, be careful about how much you install or uninstall.
Dont know if your aware of this, but nothing is ever really deleted, its flagged as safe to be overwritten and hidden from the user, too much installing or un-installing apps will overwite the flagged images.
Click to expand...
Click to collapse
Currently browsing play store now, is there any you can recommend?
I wasn't fully aware of how it works but I knew I could recovery most with some nifty software. MagicCute has worked wonders in the past for me.
At least all my music is stored in music play store.
I found a PC based program to scan the phone but the phone requires to me rooted for that, although that was my main reason for joining this forum to root I'm a little apprehensive to do anything like that until I have saved my pics!
Cheers.
Paul_TDi said:
Currently browsing play store now, is there any you can recommend?
I wasn't fully aware of how it works but I knew I could recovery most with some nifty software. MagicCute has worked wonders in the past for me.
At least all my music is stored in music play store.
I found a PC based program to scan the phone but the phone requires to me rooted for that, although that was my main reason for joining this forum to root I'm a little apprehensive to do anything like that until I have saved my pics!
Cheers.
Click to expand...
Click to collapse
Someone else said they had great luck with DiskDigger Pro
Good luck!
Sorry sheppster, completely missed your reply somehow yesterday. Thanks for the suggestion.
Thanks clsa I'll give that a go once rooted.
I'm currently reading, reading watching and rewatching content on the rooting process. Very confusing for a complete and utter noob. A lot of content is spoken as if I have a clue, haha.
But I'm now registered on HTC DEV, all videos and content say to select all other supported devices due to the HTC One not being listed, but it is. I'm guessing HTC Dev has been updated since the guides were posted. Shall I click HTC One or still use other devices?
I installed Android Studio and also JDK which it asked for, but when continuing to install Android Studio I got the following message...
Is this detrimental to the use of the program or can I just continue?
Sorry this thread is going to turn into more of a rooting Q&A.
I now have sync manager working correctly and have made a back up on my laptop which I'm happier with than having something floating about in my HTC Account. So I think I'll go ahead and try unlocking my bootloader.
Well I have unlooked the bootloader now. Successfully? Not sure!
After confirming to unlock it then restarted and kept going round in circles, it's now saying "Android is upgrading" running through 253 apps. Nothing like the XDA video where it just restarts as a fresh phone.
I used the HTC One instructions from the drop down menu in the end.
Fingers crossed at the end of that it's working and I can continue to root.
Well considering I have an early start I've stayed up far too long messing around.
BUT! My phone is now rooted, I did attempt putting a venom rom on but it didn't install properly although I seem to have a large ammount of it's features here and there like being able to boot directly to bootloader or recovery from the power button.
But any way the lapcop software I had appeared to be useless, it found 603 images from various emails and programs files none on my actual pictures. I'm not running disk digger which again has found background images but still 85% left to scan.
I'm not holding out too much hope now as there's been a few files added and deleted to root and also reset again to root.
I'll update tomorrow how it went.
I didn't realise how cheap Disk Digger Pro was, so bought and ran that last night. I think it found touch under 4000 images but again mostly PNG program images.
It did manager to find 41 useful images though. It seemed to mainly pick up pictures which I had recently used on facebook, so annoyingly mainly recoverable images through facebook.
It picked up a lot of signatures from various emails and made a lot of duplicates. Not a bad effort for under 2 quid though.

Samsung ATIV Odyssey shows nothing in tethered Windows laptop Explorer

I have an Odyssey that currently has 57644 minutes before I can try another code combination. I would like to flash a new ROM on to it that would allow interop unlocking and let me get all the stuff I want off of it. Granted, that isn't a long time to wait to try again, but that is the tail end of a couple years of waiting. I wrote some possible codes down near to the time it got locked, but that is about all I have to go on and I'm not optimistic.
So, I connected the phone to my Windows 10 laptop and it was recognized (eventually.... had to do several soft resets of the phone). In Explorer, however, there was just an empty root directory showing up. I tried MBN_Creator but it also could not see a valid phone to flash to.
In Device Manager, I saw that only a generic (from 2006) USB/phone driver was installed. I have not been able to find a driver (Samsung or otherwise) that will install on Windows 10. I have tried a few on a WIndows 8 Pro system I have, but they also have not worked at showing any kind of file system on the phone. Is there something in the Windows Phone SDK that could be used?
I saw several references to being sure to use the original Samsung cable. I can't find that, but I tried one I did have along with borrowing a newer Samsung. The cable I have shows several folders on the borrowed Samsung (as does the cable my friend's using ... also not a Samsung cable), but neither cable works with the Odyssey.
I've tried soft resetting and power-cycling several times, but no dice.
I'm out of ideas, and would appreciate any insight you can give me.
I stumbled across a 'fix' for the huge number of minutes which was to pull the SIM and reseat it. So, I gave that a try and it came back on with 1.2 million minutes. . not the result I was hoping for.
I repeated the reseat and it was back to the 57k and change.
On the off-chance that the directories would show up, I checked and still nothing.
Once, I got the confirmation pop-up on my laptop for access to photos on the phone, but that had be finished on the phone. It seems weird that I wouldn't have been prompted for that last night, or the other times I tried this morning.
Now I'm thinking what I saw last night with my friend's phone was solely due to one being locked and the other unlocked (so, user error and ignorance). I thought I remembered seeing things when locked and connected to my old computer. I guess I must have allowed access.
From poring over the internet, it looks like what I want to do isn't possible and I'll just have to wait it out and hopefully guess right. If I'm wrong about having to wait, I'd appreciate being corrected.

Categories

Resources