[Q] Hard Bricked...What's my next step? - Kindle Fire Q&A, Help & Troubleshooting

[Q] Hard Bricked...What's my next step? - Kindle Fire Q&A, Help & Troubleshooting

I was fooling around with my Fire and did a "fastboot -w". Little did I know it would erase my whole sdcard as well. So in retrospect it was pretty stupid.
To fix it, I had to get the sdcard mounted so I could push a new rom. After plenty of research I found this...
Code:
adb shell
echo /dev/block/[B]mmcblk0p12[/B] > /sys/devices/platform/usb_mass_storage/lun0/file
Which worked...sort of. It mounted the sdcard, I formatted it using OSX Disk Utility, MSDosFAT. I mad sure it was formatted with FAT32 when it was finished. Transferred the 3.0 kernel rom. Flashed, but it wouldn't get past the boot animation, even after 10 minutes.
So, thinking it was a 3.0 kernel bug, I decided to put old reliable Hashcode.Zone on the sdcard to flash it. Not enough room!?!?! WTF? I deleted the 3.0 kernel rom and tried again. Still, not enough room!?!?!
I started all over again, from "fastboot -w". Tried again, but only this time I used the following code...
Code:
adb shell
echo /dev/block/[B]mmcblk0[/B] > /sys/devices/platform/usb_mass_storage/lun0/file
That listed all 12 of the partitions. The last one, "disk2sp12" had the full 5.xxGb. Formatted it, mounted it, transferred Hashcode.Zone, went to flash it...it's not there? Rebooted, checked again...still not there.
Back to the code. This time, when I entered....
Code:
adb shell
echo /dev/block/[B]mmcblk0p12[/B] > /sys/devices/platform/usb_mass_storage/lun0/file
...it came up with only 210Mb. Here's the weird part. When I entered...
Code:
echo /dev/block/[B]mmcblk0p13[/B] > /sys/devices/platform/usb_mass_storage/lun0/file
...it came up with the full 5.xxGb. And they were both listed as "sdcard".
It gets worse.
Thinking I must have messed up somewhere, I "fastboot -w" again. I was in TWRP at the time so fastboot went to "<waiting for device>". Tried to reboot system...wouldn't reboot. So, I held the power button for 30 seconds to shut it down.
Pressed the power button to restart...Nothing! Held the power button for 30 seconds...Nothing. Held the power button for 5 minutes...Nothing. Pulled my factory out, plugged it in...NOTHING!?
Uh...So now what?
[Edit:] Before anyone suggests it, my battery was at 97%

Tried this...
http://forum.xda-developers.com/showthread.php?t=1405052
...didn't work. I even left the battery unplugged for a few minutes. Still nothing.

Are you able to see anything in Windows device manager when you power it on? Even for a split second.
Your issue sounds similar to mine when I ran a dd if=/dev/zero on the entire internal storage. But http://forum.xda-developers.com/showthread.php?t=1405052 worked for me.
You created a bootable USB drive with the utilities on it?
Have you tried this yet? http://forum.xda-developers.com/showthread.php?t=1428428

three-p-o said:
Are you able to see anything in Windows device manager when you power it on? Even for a split second.
Your issue sounds similar to mine when I ran a dd if=/dev/zero on the entire internal storage. But http://forum.xda-developers.com/showthread.php?t=1405052 worked for me.
You created a bootable USB drive with the utilities on it?
Click to expand...
Click to collapse
Well, for starters, I'm on a Mac. I've tried the usbboot on my Linux VM but the problem is when you plug something into the usb port, a prompt comes up asking you whether you want to connect to to Mac or Linux. The whole process takes too long and I miss the window.
It's fine, I guess. I have a protection plan through the retailer, and since the device won't power on, even with a factory cable, they can't really say it was my fault.
It just sucks because I have to mail it in and it'll take about three weeks to get my refund. And to make matters worse, most the 3.0 kernel bugs were fixed a day after my Kindle broke. Irony.

The VM is too slow. Take 5 mins and make the Ubuntu USB drive as outlined here, http://forum.xda-developers.com/showthread.php?t=1430038. It will save you from having to return it.

Related

1.47 Root Problems

So I am attempting to use the newly discovered Flash exploit and I am running into a problem. When I first put the files on my sdcard and ran it, part1 ran successfully, then I started my browser and refreshed, then I rebooted the phone. I kept running the command to run part2 however when it finally got to the point where the device would respond to adb, it simply said permission denied. Now I am unable to run any of the parts or do anything really. I have done the "Clear Storage" option in the volume down menu on bootup and the Clear Data in the Privacy setting and then tried again to no avail...my phone simply refuses to run the scripts. I've also tried to format my SD card both through my computer and through the phone.
Any ideas?
Regards,
-Taco

I would try to do a factory reset (menu->settings->privacy?->factory reset?... i dunno if this is right but its somewhere in there).
First time it boots up, just skip through all of the starting config stuff, enable USB debugging, set to charge only, and connect to adb, run your 'adb shell' then 'sh /sdcard/part1'
you should probably see two lines pop up, one says to reboot your phone and run again, the other says to open up the internet app and go to the bit.ly/ap0dRn, REBOOT your phone.
Rerun adb and part 1, if its successful and tells you to reboot then reboot using adb reboot.
What I did (and it took me 3 or 4 factory resets to get this to work), was to leave my phone plugged into the PC and when it comes up to the white HTC boot logo, it will may take a few seconds, but as soon you hear the windows sound saying the phone connect (BA DUN) hit enter on your 'adb shell /data/local/part2' command. If it says not found, just keep hitting up, enter till it does. I think it needs to be done while the white boot screen is still up. If it doesn't, then in my experience with it, I had to do a factory wipe and start over.
You should see the output when its done saying you have rw-rw-rw- root blah blah and it would always kick me out of adb. I never got the su's # prompt. But I would go in and do the cat stuff like it says and reboot, flash the PC36IMG.zip file and it would be downgraded for me to do toast's part 2.
I know it was an essay, but hopefully that works for you.

[Q] PLEASE HELP!!!!!!! i think i bricked my Evo

My Evo won't charge unless it is turned off. When the phone is on, the usb won't give me any mode option. Phone doesn't see the sdcard. PC won't see the phone. I have usb debugging checked. Device manager gives me three qualcomm CDMA Technologies and can't find drivers. Everything on the phone works except for apps using the sdcard. The phone says "SD Card removed" at the top left of the pulldown bar. With the vol down and power the phone will read the PC36IMG.zip of the sdcard and load and run it. After rebooting it still doesn't recognize the sdcard. I followed all steps in this previous thread:..............................................................................................................................................................................................................
These fixes require the Android SDK and very basic ADB knowledge. You can copy and paste for most.
Make sure in device manager the driver for fastboot is installed (Win 7 downloads them automatically)
For USB fix
Download the flash_image & mtd-eng.img attached, unzip them and put them on the SD card before starting
SD Card Fix
Press & hold vol down and power on the phone
Select fastboot by pressing the power button
ADB commands
fastboot oem enableqxdm 0
fastboot reboot
That should fix your SD card not being detected........................................................................................................................................................................................................................................................................................................................
i get all the way to to Command Prompt and enter the correct dir where my ADB and Fastboot are, then i proceed to type fastboot oem enableqxdm 0. Then it says waiting for device. Help please! Im stuck.

slbyrd said:
My Evo won't charge unless it is turned off. When the phone is on, the usb won't give me any mode option. Phone doesn't see the sdcard. PC won't see the phone. I have usb debugging checked. Device manager gives me three qualcomm CDMA Technologies and can't find drivers. Everything on the phone works except for apps using the sdcard. The phone says "SD Card removed" at the top left of the pulldown bar. With the vol down and power the phone will read the PC36IMG.zip of the sdcard and load and run it. After rebooting it still doesn't recognize the sdcard. I followed all steps in this previous thread:..............................................................................................................................................................................................................
These fixes require the Android SDK and very basic ADB knowledge. You can copy and paste for most.
Make sure in device manager the driver for fastboot is installed (Win 7 downloads them automatically)
For USB fix
Download the flash_image & mtd-eng.img attached, unzip them and put them on the SD card before starting
SD Card Fix
Press & hold vol down and power on the phone
Select fastboot by pressing the power button
ADB commands
fastboot oem enableqxdm 0
fastboot reboot
That should fix your SD card not being detected........................................................................................................................................................................................................................................................................................................................
i get all the way to to Command Prompt and enter the correct dir where my ADB and Fastboot are, then i proceed to type fastboot oem enableqxdm 0. Then it says waiting for device. Help please! Im stuck.
Click to expand...
Click to collapse
Have you tried to flash back to stock rom?

hmm...argh!!
thanks for responding. I just finished to an unroot. My phone does boot up fine now and there is no more "sd card removed" error, but my phone still doesn't see my sd card. And it keeps on powering down and then vibrating 5 times, then the led indicator flashes green and i cant restart my phone without pulling the battery and replacing it. I have a card reader on my pc (im running vista). The pc reads it just fine. ???

sl22857 said:
thanks for responding. I just finished to an unroot. My phone does boot up fine now and there is no more "sd card removed" error, but my phone still doesn't see my sd card. And it keeps on powering down and then vibrating 5 times, then the led indicator flashes green and i cant restart my phone without pulling the battery and replacing it. I have a card reader on my pc (im running vista). The pc reads it just fine. ???
Click to expand...
Click to collapse
Hmm, that is strange. So your pc reads the contents of the card just fine, and when you run a 'disk check' on the sd card, it turns up no errors? What were you doing on the phone when this first started, or was it out of the blue? So since your Evo doesn't see the sd card, then formatting it using the phone isn't an option I presume? What about formatting it using windows (fat32), then putting it in the phone, is that something you tried already?
As far as the phone vibrating 5 times and then you get the blinkng led, i believe that is the phone kicking itself into diagnostic mode. I'm not really clear as to what exactly that is, or why it would be happening, but I am sure that it is in diagnostic mode at that time. So you said you unrooted it, and you're currently on stock, s-off ROM right now? Do you still get the same error when you try the fix that you were initially trying to execute?

And i cant flash any ROM's due to the fact that my computer wont recognize my phone, therefore i cant access the ADB Shell. This is so frustrating!!!

i was in the process of flashing a rom and thats when the problems started. I haven't tried formatting the SD Card. I dont see how that would help me, because i can access the card and its contents just fine but my phone wont recognize there being an sd card in the phone. It seems to be a trifecta of evil!!! LOL 1.) PC doesn't see the phone 2.) Phone doesn't see sd card 3.) i can't flash anything because i can do nothing in the ADB Shell. I initially went the Unrevoked3 route of rooting and then i went the way of flashing the PC36IMG file that you put on the root of the sd card and then renaming it. The guy in this thread seemed to have the same exact issue and he figured it out. I dont know what im doing wrong.
Originally Posted by airauto View Post
Ok thanks, I finally got it all working. After a week of learning about ADB, Terminal and Fastboot commands not to mention the structure of the Evo file system, charging, usb and sdcard are all working thanks to everyone contributing to the forum.

well i thought i did an unroot but it still says SHIP S-on???

i am formatting the sd card now. what do i do once its done formatting? I've been at this for 22hours now and my brain is officially fried!!

sl22857 said:
i am formatting the sd card now. what do i do once its done formatting? I've been at this for 22hours now and my brain is officially fried!!
Click to expand...
Click to collapse
Once you format it, before you put anything else on the card, I would put it back in the Evo, and see if it will recognize it, totally fresh from the format. If that still fails, then I'm out of ideas. I'm sorry, hopefully someone else can offer some advice if that still doesn't work. I would consider dropping by sprint for some service if you can't get it handled.
Is it still giving you the 5 vibrates? And also, if it says s-on, you are unrooted, Forgive my previous typo.

thanks. i'll let you know what it does after the format. hopefully this works. (fingers crossed)

sl22857 said:
thanks. i'll let you know what it does after the format. hopefully this works. (fingers crossed)
Click to expand...
Click to collapse
Good luck dude. I hope that works for ya, I'll do another quick search and see what I come up with.
Also, did you try this again? After you unrooted? Same results as before, "waiting for device?"
These fixes require the Android SDK and very basic ADB knowledge. You can copy and paste for most.
Make sure in device manager the driver for fastboot is installed (Win 7 downloads them automatically)
For USB fix
Download the flash_image & mtd-eng.img attached, unzip them and put them on the SD card before starting
SD Card Fix
Press & hold vol down and power on the phone
Select fastboot by pressing the power button
ADB commands
fastboot oem enableqxdm 0
fastboot reboot
That should fix your SD card not being detected

okay i figured out the sd card issue. too bad i didnt see this thread before i formatted.
"alright, it is done. i was putting it in recovery mode for the sd card, and i should have just stopped at fastboot and not put it in recovery. thanks all of you. you knew what you were speaking about, i just didnt follow the instructions correctly" (posted by airauto)
now my phone recognizes my sd card. whew. one down. thanks for your help anyways.

got the sdcard to be seen by the Evo but now its still rebooting after about two minutes and then vibrates 5 times. ?????

sl22857 said:
okay i figured out the sd card issue. too bad i didnt see this thread before i formatted.
"alright, it is done. i was putting it in recovery mode for the sd card, and i should have just stopped at fastboot and not put it in recovery. thanks all of you. you knew what you were speaking about, i just didnt follow the instructions correctly" (posted by airauto)
now my phone recognizes my sd card. whew. one down. thanks for your help anyways.
Click to expand...
Click to collapse
Glad you got that figured out. Didn't you backup your sd card to your pc before you formatted? Just copy everything back over to the card.

sl22857 said:
got the sdcard to be seen by the Evo but now its still rebooting after about two minutes and then vibrates 5 times. ?????
Click to expand...
Click to collapse
Wish I could help you on that, but any thread I've ever seen where people were having that problem, where it vibrates 5 times then goes black and the led blinks, the only resolution I ever saw (and I could be wrong, I'd do a search on google about that, quite a bit of stuff on there) was replacing the phone. I'm not sure of the cause of that. If there is a fix for it, xda and google should have it somewhere though. (but I still think replacing is the option for you)

[Q] LeeDrOiD V3.3.3-Port-R5 USB Issues.

Yes, this is one n00b 1st. post... but bare with me, as I (think) I have done all the right things.
The Issue:
I flashed the LeeDrOiD HD V3.3.3-Port-R5 A2SD++ to a HTC Desire (Bravo, Root, S-off, Full Wipe).
It is fast and seems to work really well, but there is one major problem: The phone do not recognized USB connection.
I plug the AC charger in, and it takes 2-5 min for the phone to start charging, and the phone seems to think of it as USB charging, not AC...
Plucking the phone to the PC gives error form windows about "unknown USB device", and the phone newer seems to register the PC: It just go to USB charging, after 2-5 min.
The first flashing of the LeeDroid rom caused a USB Brick, that FastBoot "rebootRUU" and "enableqxdm 0" fixed.
Don't know if that have anything to say.
Yes, I guess n00b problem, and I guess all is explained 117 times.
But please... point me to the right threads.

You have what's known as a USB brick. Basically, you had two problems. Your first was that your phone did not recognise that there was an SD card inserted, you have now fixed that. Unfortunately however you do now have a USB brick, which gives exactly the problems you describe. Do some searching on the forum, there's several threads explaining how to fix this.

try this thread
http://forum.xda-developers.com/showthread.php?t=691639&highlight=usb+brick

Thanks a bunch!
I vent to that same thread earlier, when the SD card did not work, but did not find a fix fore it there.
It is all starting to make sense now.
I'l try flowing the guide and, and see if I can make it on my own again.
Thanks Again.

Both SD and USB Un-Bricked now.
Happy Happy!
Thanks.

I've been there and done it. I had EXACTLY the same issues as yourself and on fixing the SD card issue I thought brilliant, "I am legend".... It was only after trying to connect the phone to the PC that I discovered I was not. I was only half way to fixing my problems. I did however make a text file detailing what I did in case it ever happened again and here it is (you will need an image file however which can be got from the thread linked above) :-
============================================
To gain access to SD card:
Put phone into fastboot mode (back button + power)
In CMD, go to dir C:\Android\android-sdk\Tools
Type: path C:\Android\android-sdk\Platform-tools)
Input "fastboot oem enableqxdm 0"
Before trying the stuff below, try to run this command first - fastboot oem eraseconfig
I had already done the below which didn't work then running that it suddenly did work so try it first, if no joy do the below and if still no joy then try the command again.
ALSO FOUND THIS TO TRY -
So I download the HTC hboot stock partition, flashing through fastboot command, and do 'fastboot flash misc mtd0.img' reboot... and ta...da ... my USB connection fix, Bluetooth is working too, testing with some other rom, and all fine ...
AND -
1.download recovery *.img file.
2.put it in androidsdk\tools folder.
3.boot in to fastboot by pressing back button and power button together.
4.run :-
fastboot flash recovery *.img
===================================================
EDIT: Ah you fixed it whilst I was replying (was on a phone call). Nice one fella.

Need urgent help accessing data on my rooted t989 with broken screen

My T989 is rooted. I use it to log my work hours in "It's About Time". I back that app's data up every day to the box folder, and I sync with box. HOWEVER, the box syncing has aparently been pretending to work and doing nothing since february, so I'm screwed right now as the touchscreen on the phone was shattered today. It has no visuals or touch ability. the gorilla glass survived just fine, but the screen behind it is gone.
What I need to know is how can I access the data in the builtin memory. I would love to use Kies, but Kies, points out that my phone is locked (I use a pattern lock) and says I have to unlock it.
Is there someway to remotely unlock a broken phone? The phone can go be a doorstop at this point, but I HAVE to have those backup files sitting in the box folder. They aren't on the microsd card.

So the display is damaged but the digitizer is fine correct? As for data just pull files with adb....I believe you can do that unless you never had USB debugging on
Sent from my SGH-T989 using Tapatalk

CptCrackers said:
My T989 is rooted. I use it to log my work hours in "It's About Time". I back that app's data up every day to the box folder, and I sync with box. HOWEVER, the box syncing has aparently been pretending to work and doing nothing since february, so I'm screwed right now as the touchscreen on the phone was shattered today. It has no visuals or touch ability. the gorilla glass survived just fine, but the screen behind it is gone.
What I need to know is how can I access the data in the builtin memory. I would love to use Kies, but Kies, points out that my phone is locked (I use a pattern lock) and says I have to unlock it.
Is there someway to remotely unlock a broken phone? The phone can go be a doorstop at this point, but I HAVE to have those backup files sitting in the box folder. They aren't on the microsd card.
Click to expand...
Click to collapse
You can always boot into recovery and pull from your data partition using ADB. Then you can restore that to another phone after you install your time tracking app.

I have been in usb debugging. It may be in usb debugging mode right now.
When I connect it, it shows the drive, but they show as empty. Which is the same thing that happens on my GS4G when it's in debugging.
If you could tell me how to go about extracting files, that would be great, assuming there is even a way.
Is the digitizer the touch portion of the touch screen? If so, then no, that's not working. The phone boots, it receives texts, makes other sounds like it's working, but the screen is black. The LCD is cracked, and it will not accept touch input. I have haptic feedback on and it's definitely not letting me attempt to do the unlock screen.

slm4996 said:
You can always boot into recovery and pull from your data partition using ADB. Then you can restore that to another phone after you install your time tracking app.
Click to expand...
Click to collapse
Could you tell me how I do this? The only time I ever booted into recovery was during the rooting process. Do I need to be able to see the screen to do it, or is there a way to get into it remotely? If so, can you either tell me what to do or point me at a tutorial or something? I wouldn't know where to start.

CptCrackers said:
Could you tell me how I do this? The only time I ever booted into recovery was during the rooting process. Do I need to be able to see the screen to do it, or is there a way to get into it remotely? If so, can you either tell me what to do or point me at a tutorial or something? I wouldn't know where to start.
Click to expand...
Click to collapse
To get into recovery, pull your battery then put it back in, then hold both vol up and vol down and hit the power button.
Type "help" without quotes in ADB to get a list of commands.
Sent from my SGH-T989 using xda premium

try this http://forum.xda-developers.com/showthread.php?t=628138
It got me out of a jam once on my vibrant, when the same thing happened to me and needed some pictures for my work. USB debuggin has to be on though.

To backup the data from a damaged phone using ADB:
1) Enter Recovery mode:
Turn the phone off, remove the battery. Insert battery, hold volume up AND down while turning on. Plug in usb cable.
2)Open up your terminal/console. Enter the following commands (one command per line, press enter after each)
(this backs up the entire data partition)
Code:
mkdir phoneDataBackup
adb shell mount data
adb pull /data phoneDataBackup
You now have a copy of your phones /data folder, this contains the settings and data from your apps. Get a new phone and then install you app on it. Once you do that simply put the correct named folder from the phoneDataBackup back into your new phones /data folder.
Code:
adb push phoneDataBackup/data/com.rds.itsabouttime /data/data/
This should work just fine for you, I assume you already have ADB installed or can install it first.

THANKS ALL!!!
I am currently using the suggested Android commander to dump everything out of the phone. Lucky the usb debugging got left on when I was cleaning out bloatware last week!!!
Once it's done, or if even if it doesn't work, I'll be playing with the adb connection since it's not like I can break the phone worse... good learning opp!
Thanks for all the tips from everyone.

Quick update, and info in case someone later finds this thread in a search. The android commander did get back what I needed most. However, it also did some strange things. It can see a lot of stuff on the phone, but when pulling things from the phone, for some reason, some files and directories do not come over. I imagine this may have to do with permissions on those items.
I'm basically making thsi note here in case someone finds the thread, thinks they have dumped heir whole phone... just make sure you pick through the important directories before you think you've got everything and discard the phone.
Thanks again everyone. Ass officially saved.

Hello everyone.
I also just cracked my screen and have neither touch capability nor screen lighting, so I'm effectively blind in controlling my phone.
I know I have Clockworkmod recovery 5.0.2.7 installed and rooted, but these solutions are not working for me.
I have tried removing the batt, reinserting the batt, holding UP+DOWN+POWER until the device vibrates, then let go of the POWER while holding UP+DOWN for another 10 seconds to be sure.
I then plug in the USB cable and my Windows 7 laptop does the "found USB device chime", so I know the device is on (and has not booted into Android, since the Samsung Galaxy logo jungle has not played.)
I also see that Windows 7 sees new "Removable Drives" that it adds after I plug in the device, but the drives cannot be accessed/are not available to Windows 7.
I'm definitely sure I'm in recovery because when I hit POWER, the Windows 7 "unplugged USB device" chime plays, the device vibrates and I'll hear the Galaxy S logo chime, which means I hit the 1st "reboot device" option on the recovery menu.
But when I open a console and type "adb devices" none are listed.
I have also tried Android Commander, and no devices are there either, so these 2 methods do not work. I'm wondering why adb cannot see recovery on mine if people are saying that it can.
I know that Clockworkmod recovery has a option for mounting the sdcard and data via USB. I also see that different versions of Clockworkmod have different menus.
Can someone help me by letting me know what/how many button presses I need to do to get to the "mount sdcard" and "mount data" options once I'm in recovery as I'm flying blind.
Thank you for any help.

soundwave4 said:
Hello everyone.
I also just cracked my screen and have neither touch capability nor screen lighting, so I'm effectively blind in controlling my phone.
I know I have Clockworkmod recovery 5.0.2.7 installed and rooted, but these solutions are not working for me.
I have tried removing the batt, reinserting the batt, holding UP+DOWN+POWER until the device vibrates, then let go of the POWER while holding UP+DOWN for another 10 seconds to be sure.
I then plug in the USB cable and my Windows 7 laptop does the "found USB device chime", so I know the device is on (and has not booted into Android, since the Samsung Galaxy logo jungle has not played.)
I also see that Windows 7 sees new "Removable Drives" that it adds after I plug in the device, but the drives cannot be accessed/are not available to Windows 7.
I'm definitely sure I'm in recovery because when I hit POWER, the Windows 7 "unplugged USB device" chime plays, the device vibrates and I'll hear the Galaxy S logo chime, which means I hit the 1st "reboot device" option on the recovery menu.
But when I open a console and type "adb devices" none are listed.
I have also tried Android Commander, and no devices are there either, so these 2 methods do not work. I'm wondering why adb cannot see recovery on mine if people are saying that it can.
I know that Clockworkmod recovery has a option for mounting the sdcard and data via USB. I also see that different versions of Clockworkmod have different menus.
Can someone help me by letting me know what/how many button presses I need to do to get to the "mount sdcard" and "mount data" options once I'm in recovery as I'm flying blind.
Thank you for any help.
Click to expand...
Click to collapse
If you have adb setup just do adb pulls. You can get anything that way. Slow, but a plan b if nothing else. I would count for you but I run twrp and I don't have time or battery to flash it over to cwm right now.
Edit: for whatever reason tapatalk didn't load anything past the OP...disregard.
Tapatalked from my Galaxy S II.

S4 mini with broken screen, no more data after 'blind' reboots to recovery

Dear All!
(I already searched Google and xda - However, since my problem is rather specific, I may be using the wrong keywords to come up with a solution that is also applicable here; so also links are highly appreciated!)
I will give you the whole story in order not to skip anything important:
While hiking with my family I somehow managed to break my screen (LCD and Touch, as far as I could tell). However, the phone was still powered on, which i could tell from using the volume keys and hearing the normal sounds. Also the phone was ringing when called.
Unfortunately, USB Debugging wasn't activated, so I booted to recovery (some CWM, can't be more specific, sorry) via several tries. It was a bit tricky at first, but i managed to come up with a routine that would work (Holding VolUp+Home, then Power additionally; releasing the power button after the first vibration and then holding the other two for another 3-5 sec did the trick).
I then could gain usb debugging the way described in this thread: [Tool][Windows] Control a device with a broken screen. Now with touchscreen support!!
Using a Linux machine I then used adb commands (ls; cd; pull) to copy my mmssms.db; however I had to leave my workplace for a short while. Afterwards my device wasn't shown in adb devices, because it powered off for some reason.
Here comes the crucial part: At this point I mistakenly booted into Download Mode (and wasn't aware that I did it, cofused VolUp and VolDown - I couldn't see that, so I'm not 100% sure). I pulled out the battery at this point and rebooted into recovery.
Booting into recovery still works and "adb shell" -> "ls" shows the folders, however apart from the top level folders there are no more files/folders left (e.g. "ls mnt" gives "fuse secure shell"; "ls data" gives "media"; "ls data/media" doesn't return anything)
At this point I mainly want to get the contents of my internal sd (now no files are shown).
tl;dr: Broke screen; accidentially booted into Download Mode; Pulled out battery; Can't access my files/files gone in adb shell
Is there a way to recover the file structure? I still can get into recovery and use adb but the phone won't boot to CyanogenMod (I suppose it gives me a soft brick screen, but i can't confirm that as my screen is broken).
I really hope someone could point me in the right direction!
Lukas

Develop Bugs

welcome