Develop Bugs

[Q] Can't mount SD card

Hi chaps, I've done a lot of searching but unlike many who managed to fix theirs I fear that my Desire is dead. Did a nandroid backup and during reboot for one reason or another (likely the cheap Ebay battery) the phone rebooted a couple of times and I suspect it's corrupted the ext4 that was holding data. Phone was running Starburst 1.5 Classic with data2sd. It's also s-off.
Ok, I've read threads where people have plugged it in and using adb have managed to issue a command to have the phone re-enable the sd card. The issue I have is that adb doesn't even recognise that the phone is actually connected. I've tried this on both my PC and laptop with no joy.
I can still get into recovery and also fastboot and there must be some life as the phone recognises the USB connection when plugged into the PC but 'adb devices' gives me nothing so I therefore can't issue commands.
I have also tried putting the original firmware back on via PB99IMG.zip but since the phone's not reading the card at all that too is a dead end. It still boots to recovery and I get the 'Why so serious' logo if I try starting the phone up but I just can't get any further with it.
Anyone any ideas?

You can wipe and flash partitions and files from fastboot
http://android-dls.com/wiki/index.php?title=Fastboot

Once you get it working, restore your nandroid to see if it's working and not corrupted by the reboot. If it's not working, you can rebuild in fastboot!

Ok, I'm doing some more reading and learning, driving me nuts this thing. Cheers.
Edit: That won't work as I cannot gain access to the phone from the PC. adb devices show nothing connected even when it clearly is.
Edit 2: C:\Android\android-sdk\platform-tools>fastboot
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
Perhaps I'm missing something???

Sorted I think, was me being a n00b. Will post back if I manage to get it all running again.

Did you get fastboot to work and recognise your device?
Take a look at the thread I posted earlier, the command to check it is
Code:
fastboot devices

[Q] How do I mount internal storage from recovery mode?

I have a problem. I have been passed a HTC Wildfire that has a big chunk missing, namely the touchy part of the screen On this phone is, apparently a photograph that I need to rescue or the world is going to end. The phone is configured to charge only when connected to a computer so I need to access the internal storage, whilst in recovery/fastboot and save the photo.
I have HTC Sync installed, the SDK too, but when I use ADB to list devices I see nothing.
Can anyone please point me in the right direction?

philskents said:
I have a problem. I have been passed a HTC Wildfire that has a big chunk missing, namely the touchy part of the screen On this phone is, apparently a photograph that I need to rescue or the world is going to end. The phone is configured to charge only when connected to a computer so I need to access the internal storage, whilst in recovery/fastboot and save the photo.
I have HTC Sync installed, the SDK too, but when I use ADB to list devices I see nothing.
Can anyone please point me in the right direction?
Click to expand...
Click to collapse
How did you save a photo on the internal storage?
More on topic:
If you know where it is you can use adb to pull it out.
Command to do this is:
"adb pull [location of file here]"
If you don't and you know the name, you can use the shell to "search for it"
command:
adb shell
now that your in the shell, use ls to list what's in the folder and cd [folder] to change the directory.

Thanks for your speedy reply!
It's not my phone, so I have no clue how a photo got on to the internal storage. Your response was very helpful, but at the moment I cannot get the device to list in "adb devices". Can you shed any light on that?

Try to turn it on and see if the trackball still works.
If it does, navigate to settings->applications->debugging and turn on USB debugging.

My apologies, I have just noticed I have posted this in the wrong forum. It is a Wildfire S not a Wildfire (no trackball). I will repost in the correct forum.

I did find another way...
but it requires you to install Ubuntu.
http://forum.xda-developers.com/showthread.php?t=981774

NOOB mistake! Need Help

So I somehow managed to completely delete all the data on my sdcard through TWRP recovery when U was getting ready to flash PA 1.7. I have been flashing roms for many years and am now beating myself over the head considering I have never managed to do this before. So other than the fact that I have just lost an immense amount of important photos and data, I need some advice/help.
So to answer a few questions that I know will come up.
- I have not backed up my internal storage lately (I know *Rookie Mistake*)
Since this is the first phone I have ever had that doesnt have an SD Card is there a way to connect it to a PC and then run a data recovery program..All i really care about is the 1600 photos that I had on my phone of my kids.
My other problem is during this process i had factory reset which means there is no current ROM flashed to the phone so I cant usb mass storage through the rom itself. I have even tried to USB mass storage through the TWRP recovery but it is not working. So from what I can tell is I am screwed at this moment.Please I hope someone can shed some light on this situation.
Thanks

m4tt.03 said:
Since this is the first phone I have ever had that doesnt have an SD Card is there a way to connect it to a PC and then run a data recovery program..All i really care about is the 1600 photos that I had on my phone of my kids.
Click to expand...
Click to collapse
No, the internal storage can't be mounted so you can't run any recovery software on it. From this point forward I'd turn on Dropbox instant upload or Google+ instant upload to upload pictures. You can even set it to only do it on WiFi to save your data cap. It'll just back them up every night at home.
My other problem is during this process i had factory reset which means there is no current ROM flashed to the phone so I cant usb mass storage through the rom itself. I have even tried to USB mass storage through the TWRP recovery but it is not working. So from what I can tell is I am screwed at this moment.Please I hope someone can shed some light on this situation.
Click to expand...
Click to collapse
Just use ADB to send the ROM and GAPPS and other files to the phone.
Assuming you have ADB and drivers set up.... Connect to your PC. In the command line, type:
Code:
adb push FILE.zip /sdcard/
and let it go. You won't get a confirmation or anything until its complete. ADB is very slow. It'll take a couple minutes for a large (~200mb) ROM.

martonikaj said:
No, the internal storage can't be mounted so you can't run any recovery software on it. From this point forward I'd turn on Dropbox instant upload or Google+ instant upload to upload pictures. You can even set it to only do it on WiFi to save your data cap. It'll just back them up every night at home.
Just use ADB to send the ROM and GAPPS and other files to the phone.
Assuming you have ADB and drivers set up.... Connect to your PC. In the command line, type:
Code:
adb push FILE.zip /sdcard/
and let it go. You won't get a confirmation or anything until its complete. ADB is very slow. It'll take a couple minutes for a large (~200mb) ROM.
Click to expand...
Click to collapse
Well to be honest I assumed I had adb set up correctly. But for some reason when I plug in the phone, and open cmd prompt. I go to my platform-tools folder and type adb devices i get nothing listed under connected devices? It doesn't seem like my computer recognizes the phone anymore. OMG...so frustrating.. *im that guy now!!!*

m4tt.03 said:
Well to be honest I assumed I had adb set up correctly. But for some reason when I plug in the phone, and open cmd prompt. I go to my platform-tools folder and type adb devices i get nothing listed under connected devices? It doesn't seem like my computer recognizes the phone anymore. OMG...so frustrating.. *im that guy now!!!*
Click to expand...
Click to collapse
Well is ADB updated and installed properly? Do you get anything if you just type "adb" and hit enter?
Its probably a driver issue.

Ok so after a little messing around I was able to get ADB working and am currently pushin ROM files to the phone now. Appreciate the help!! Super bummed about the pictures but like a few of you have said this unfortunately my fault and nothing that can be done. Nowdoes anybody have any advice on how to tell my wife I lost over 1600 photos? She already gives me a hard enough time for always messing with my phone, this is only going to ammo to her already large arsenal. LOL

m4tt.03 said:
Ok so after a little messing around I was able to get ADB working and am currently pushin ROM files to the phone now. Appreciate the help!! Super bummed about the pictures but like a few of you have said this unfortunately my fault and nothing that can be done. Nowdoes anybody have any advice on how to tell my wife I lost over 1600 photos? She already gives me a hard enough time for always messing with my phone, this is only going to ammo to her already large arsenal. LOL
Click to expand...
Click to collapse
Glad it worked.
No idea on the wife front. GL with that.

Trying to use keis to back up GS3 with broken screen (phone locked)

Hi, great site you have here. I dropped my GS3 and broke the digitizer. The phone turns on, but has a blank screen. Of course I didnt back anything up to google or save my contacts to my sim. I tried using kies with my laptop and connected my phone, but it says my phone is locked. I enabled a swipe pattern on the phone before i broke it, but I cannot unlock it since the digitizer is not working. Is there anything I can do to disable it? Also, Samsung is quoting me about $175 ($65 for the digitizer, $100 for labor/shipping) to fix the phone, however they wipe then entire thing and of course all my contacts, pictures, music, apps and everything will be gone. If I cant get kies to work because the phone is locked, can you recommend a good place to purchase the digitizer? Is it difficult to install yourself? Thanks for all the help

You can use the "adb pull" command to pull any files/folders off your sd-card even with the screen lock (I've tested this). Install the android SDK and adb can be found in the platform-tools folder. Simply use the windows command prompt to pull the needed folders out. Sorry for your misfortune hope that helps.

illmatic24 said:
You can use the "adb pull" command to pull any files/folders off your sd-card even with the screen lock (I've tested this). Install the android SDK and adb can be found in the platform-tools folder. Simply use the windows command prompt to pull the needed folders out. Sorry for your misfortune hope that helps.
Click to expand...
Click to collapse
Thank you for the help. I will try and you tube how to do what you told me, as I know next to nothing about using computers in this way lol

xxH3llsp4wNxx said:
Thank you for the help. I will try and you tube how to do what you told me, as I know next to nothing about using computers in this way lol
Click to expand...
Click to collapse
No problem! Good luck, there are tons of videos/tutorials on how to set up the SDK. Just make sure to install the right drivers or else your device won't show up in ADB.
Just to simplify it a bit, I figured it might save you some time.
1. SDK installer file:
http://developer.android.com/sdk/index.html
2. Once you've got the SDK installed and configured open up "Command Prompt" (if on windows) (have your device on and at the lock-screen).
3. In command prompt, navigate to "sdk/platform-tools/" (or wherever you chose to install the SDK, just make sure to navigate to the platform-tools directory as that's where adb is located) (use cd command)
4. Next, type "adb devices" into command prompt to make sure your device shows up (it might be named something weird, don't worry)
5. Now, type "adb pull /sdcard/*FOLDERTOCOPY* (if you don't remember the names of the folders you can dump the entire sdcard)
This will dump your sd-card files to the "sdk/platform-tools/" directory.
Cheers.

wow, thanks for the time to write that out for me, it is greatly appreciated. I will try this out when i get home from work.

Wont identify my phone
Hello! It seems that I have the same problem. I have followed your directions. However, when I type "adb devices" the next line is blank. I do not think that it see's my phone. I have a Galaxy S3 on Verizon. I am running Windows 8. I have attached the phone through it's USB and the computer sees the phone.
Am I missing something?
Thank you

Hi. Most probably it is due to adb drivers not being installed. Download the galaxy s3 toolkit, and install the android drivers from within.
Toolkit:
http://forum.xda-developers.com/showthread.php?t=1746665
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

I have just posted this thread to another topic of whom the user may encounter a similar contacts lost situation.
Hope that would help him

I recently had to pull files from a gnote2 with a broken screen. With the lock enabled you won't have access to the files via adb unless you have a custom recovery installed. What I did was enter download mode and then Odin an insecure boot loader. After that I was able to use adb to pull the files.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

illmatic24 said:
No problem! Good luck, there are tons of videos/tutorials on how to set up the SDK. Just make sure to install the right drivers or else your device won't show up in ADB.
Just to simplify it a bit, I figured it might save you some time.
1. SDK installer file:
http://developer.android.com/sdk/index.html
2. Once you've got the SDK installed and configured open up "Command Prompt" (if on windows) (have your device on and at the lock-screen).
3. In command prompt, navigate to "sdk/platform-tools/" (or wherever you chose to install the SDK, just make sure to navigate to the platform-tools directory as that's where adb is located) (use cd command)
4. Next, type "adb devices" into command prompt to make sure your device shows up (it might be named something weird, don't worry)
5. Now, type "adb pull /sdcard/*FOLDERTOCOPY* (if you don't remember the names of the folders you can dump the entire sdcard)
This will dump your sd-card files to the "sdk/platform-tools/" directory.
Cheers.
Click to expand...
Click to collapse
Thanks for this, I've just recovered data from a Galaxy S2 using this. I was able to activate USB debugging using blind touches, based on a video, and recovered the sdcard using
Code:
adb pull /sdcard/ MYFOLDER

Yea what people seam to forget is that adb only works if it was enabled on the device before hand....
Sent from my ATT Samsung Galaxy SIII using TapaTalk

broken screen with screen lock on, trying to use Kies as a tempory remote terminal
Hi all,
I have the Galaxy S3 SGH-I747, and this morning I managed to break the LCD. The digitizer isn't cracked, but seems to be unresponsive.. I'm not with any of the major carriers, I have GCI in Alaska. I'm on the road, away from home, working. I should be able to get a new case when I get home. Which will be in only 4 days, luckily.
I was also hoping I could use Kies essentially as a remote terminal to send SMS or make calls just until I can get home and replace the case. (Which in my mind is actually an easier quicker repair than the screen digitizer replacement, just not always quite as cheap.)
I have ADB, I'm just not an expert with it. Is there a way to use it to disable to lock screen, even temporarily, so I can use the GUI in Kies? Is there any was to turn on the Bluetooth perhaps? I already have the partnership established with my Laptop, and is set up to connect without confirmation. I might be able to figure out a way to get some sort of functionality out of it until I can get it repaired.
Yea what people seam to forget is that adb only works if it was enabled on the device before hand..
Click to expand...
Click to collapse
I don't think I have connected this phone with the ADB yet. I also didn't have the USB debugging mode enabled. Am I SOL getting it connected with the ADB, then?

Hi illmatic24. I need a help - I have a Samsung E7 - broken lcd, forgot the password and usb debugging mode is off. Is there anyway through which I can recover my phone's content? I want access to my internal storage memory. Any help will be much appreciated. Thanks, Ritz

[Q] Build.prop edit fail -- Completely dead?

Yep, I became that idiot that started messing around with stuff he didn't about well enough. It's been a while since I've really messed around with rooting and editing system files, and this is where it got me.
In an attempt to install CyanogenMod on the G Pad 8.3 (this was a while ago), I attempted to switch out the build.prop file with something else, for whatever reason. Now the tablet will only boot up to the LG logo and hang until it dies.
Yesterday, I attempted to see if I could do absolutely anything for it, and I've found a little out but I'm not sure if it's enough to possibly do some tablet necromancy.
I downloaded the LG Flash Tool, but have only used the USBView file that comes with it. With the tablet plugged in, the tablet looks like it turns off and on every five minutes or so. When the screen turns on and shows the LG logo, I hear the device 'disconnect' from the computer. When the screen turns off, i hear the 'connect' sound on the computer. During the time the tablet is "off" I see the device show up as a USB Input Device on USB View, and managed to track it down on Device Manager as a HID-compliant device.
At this point, I'm not sure what the next step would be in the attempt to saving the tablet if I can. Any and all attempts at installing a new driver for the tablet have failed, and I can't seem to boot into anything else but this boot loop of nothing.
Serves me right if I can't get this thing fixed, but it would be rad if someone knew where to go next from here.
Thanks

are you using Windows or Linux? Which Gpad do you have assumed it is the LG LGE and not the Google Play edition? Do you have adb installed? if you have a Google Play Edition I will be more than happy to upload a copy of the build.prop.
If you saved a copy, use adb to push it back onto your device.
Code:
Adb push file_you_want_to push where_you_want_to_push_it
Example:
Code:
Adb push /home/desktop/build.prop /system
note the space between prop and /system.
this might be a problem because /system is a read only file, but there are ways around this you will have to look them up. If you could get into your device for instance you can mount /system as read / write and simply copy and paste your build.prop file over. I am unsure whether you could do this from recovery or not,and I suppose it would only work if you had already allowed your computer to get into your device. I guess without more information as to what you did there isn't a whole lot to say.
for me, sometimes receiving a small amount of information about how to solve a problem will lead to something better or bigger.

He needs to mount system fisrt
U will need root
And he needed to had usb debugging on
Enviado do meu GT-I9300 através de Tapatalk

I was rooted and more than likely had USB debugging on. I still can't seem to update the driver in anyway for adb to recognize it. The LG drivers are all installed through exe files so it's harder to just go to device manager and point it to the right driver. ADB devices shows nothing.
Also, this is the korean version. Not sure how much that changes anything, but I'd love to get either the US or Google Play software on this puppy if it's able to be saved.

if you have twrp recovery you can make a flashable zip with the right build.prop and push it using the sideload command