Related
I just got my Captivate last Friday. Hadn't done anything complicated with it, basically I just used "Unleash the Beast" to root and sideload the thing. Ended up with some sort of weird permissions issue going on with the SuperUser app that had been installed with it, I was getting permission request loops. So I used Odin to reset it. At this point there wasn't anything really wrong, USB worked and the device appeared to the computer. So I just rebooted the Captivate into download mode using adb reboot download and went on.
So later on I grabbed SuperUser 2.3.4(?) or whatever the latest one I found online was, loaded that to do adb pull /system/apps since I realized that Unleash the Beast just deleted everything and I honestly hadn't even seen what it removed yet on the phone itself besides the list on the web site. So after the backup I odin'd again and then grabbed the files from SuperUser 2.3.4 replaced the existing files in Unleash the Beast with it. Actually ended up working perfectly for a while.
I'd used the phone for a few days, no issues, finally got my 16GB SD card from my Raphael and inserted it, had been downloading apps left and right. Well all of a sudden the phone seemed to have it's USB stop working for anything but charging. I recall plugging it into a charger or computer when I first got it and it would ask if I wanted to mount the SD cards for use, then I would just see the battery indicator charging. and I'd toggled developer usb a half billion times trying to get access and fix it.
The computer didn't see it, device manager didn't even flinch(Win7 x64) like it normally does when you plug in and unplug a USB device. Tried it with another computer and same issue. So I rebooted into recovery mode and tried that, the first several times around nothing was detected. Well my finger slipped and ended up hitting the Clear user data and cache option in the recovery mode.
At this point when it boots up, i still dont have usb access, I'm stuck in a force close loop, I can't install apps, can't seem to get it to reboot into download mode via the key commands, and installing apps is impossible since browser and market crash on start.
I've spent the night rebooting and trying to get into download mode for odin, I used to be able to get into recovery mode everytime I tried, eventually I started to see an "uknown device" show up in device manager, which I googled some info from it and all I could tell was it was Microsoft's dummy driver for devices that couldn't be found. Another weird response, it seems to be beginning to hang on the charging battery thing from time to time now.
At this point, its been under a week and I'd trade it in. Except the thing is with enough struggling you can see the apps installed. Most of them were removed but Market Access and Superuser are still in the apps list, and I'm worried about AT&T spotting that, figuring out what I've done and rejecting the claim.
just under half the time now, it boots, the other over-half of the time I get the spinning "battery loading" icon that shows up before the battery thing gets loaded, but not spinning. It pops up, and disappears, from time to time goes to show me my battery status instead of booting, even when not plugged in.
I'd like to think I haven't tried everything? quite obviously i can't run update.zip files from my 16gb sd card since it gets mounted at /sdcard/sd, and I've lost the file browser to move anything around. I've tried rewiping but that doesn't do a thing.
I hadn't gotten to the rom manager stuff yet since I wasn't planning on playing with roms if at all. and at this point that doesn't appear to be an option anymore.
Any suggestions? I was getting to continuing to reboot it till the battery thing comes up 100% of the time then goto ATT and see what they say.
So long that you can get to download mode you SHOULD be good. When you plug in the usb..you need to pull the home dropdown..select usb and tell it to mount. I may be telling you what you already know but download mode is hold both volume buttons from the battery screen...one black screen...att screen...black screen and release pwer but hold buttons. I had problems with this so what I did was unplug the usb...volume buttons...hold power and see att boot screen...(plug in usb)...black screen...att boot...black screen and release power til u see download mode. You can use Odin and set back to stock from there normally.
If the PC is showing unknown device..you are kind of stuck til you fix the driver issue. Maybe remove and reinstall or something not sure on that but that's the first order of business. Go to the dev forum and try reinstalling from there. (One click Odin downloader has teh drivers)
If your phone boots or can get into recovery or download mode you are ok. I ran into the problem where I couldnt even power it on.
Well by now I know that download mode is the holy grail to get things fixed. Recovery mode, I used to be able to get to, but didn't show up. I'm wandering if somehow my USB port got shorted or something.
The drop down option to make it mount is why this all began, it disappeared and never came back.
Trying your steps specifically, first couple times would just end up back at the battery screen. I eventually ended up at recovery mode. Did I end up at recovery mode for releaseing early or late?
I've reinstalled the Captivate drivers a couple times now and tried clearing all past installs of it. Still unknown device. At the moment I have it in recovery mode, so I've rebooted my tower into Ubuntu(Which has the sdk, but never tested with it). Since I've kept reading that Linux doesn't need drivers. Well ./adb start-server and ./adb devices still show nothing...
I can grab a fresh computer that never connected to this thing to try, but I'm kinda doubting it will do this trick at this point. I'll download the odin w/ drivers on it and try that.
hmm.... just ran over to one of the computers here that had absolutely nothing to do with android on it, no drivers, no sdk, no software, nothing.
Went to
[STOCK ROM] Odin3 One-Click Downloader and Drivers(new user=no links)
Downloaded the Windows X64 drivers, installed and rebooted
Plugged the phone in after it rebooted and I'm getting
Unkown Device, I'd pull some info from the Device Manager, but all it is reporting is scewed due to it being a usb device and Windows installed dummy drivers.
All I've got left for testing is my brother's Win7 x32 laptop, granted all I've been able to try with here has been x64 so far. Also on the first computer I was doing all this with. The drivers DID work, they WERE installed and functioning. Previously I could ADB to my hearts desire and I've used odin before. I used the same USB port, used different USB ports, tried different cables.
I had some strange issues on mine. When I would try to go to download mode. All of my USB stuff (KB and mouse) froze up and I had to plug in via PS2. I had the unknown device issue and Not sure how I fixed it. I downloaded and installed the Samsung Kies program and I also downloaded the driver. Ultimatly after banging on it for a bit it worked..not a Unknown device but it was some king of...Gadget Driver or some stuff was messing with me. Try installing Kies and see if that does anything...also make sure you remove the drivers before installing. It acted really squirrly to me too tho. From what you say..it sounds like a borked driver. Im on 32bit XP and took it home to my 64 Vista and got it working whne the 32 was jacking me around.
Just had a chance to try with Kies real quick, I'm not so much thinking i killed my drivers but that somehow the cell phone changed it's id calls. I'm going to give it a shot with kies on a fresh Vista x32 system at work. I still can't seem to get it into downloader mode, but I'm getting more consistent with Recovery and getting the thing to boot back up. If I consider the Battery screens to be your blank screens then I can get it to go recovery or "normal" boot. But still can't seem to get download mode at all.
Up until recently, I didn't get Unkown device showing up even when the system was in "normal" boot. Before, originally it would only show up in device manager in recovery mode, and then it would be the unkown device.
Just out of curiosity could you spare the driver specs for your setup so I can compare? Like Date, Version, and any Hardware IDs? I'm wandering what hardware IDs this thing is giving off since windows wont show me.
Well not sure what suddenly happened. But after enough reboot--attempts, recovery mode is finalyl appearing on my office computer as SAMSUNG Android USB Composite Device. Win Vista x32, only installed Kies and download SDK(speaking of, adb still doesn't see devices). Just finished redownloading odin(wish i'd had a thumbdrive on me when i was at home) and am about to see if I'm going to be lucky by vista somehow.
If you still keep having issues find a way to short the phone out and tell at&t that the phone just got really hot and then turned off. They should replace as a bad unit and get you hooked up with a new one.
Sent from my FroyoEris using XDA App
jonscapri said:
If you still keep having issues find a way to short the phone out and tell at&t that the phone just got really hot and then turned off. They should replace as a bad unit and get you hooked up with a new one.
Sent from my FroyoEris using XDA App
Click to expand...
Click to collapse
Well that thought has occured, that and magnets lol
I think i might have found a clue to the cause. I think it was tied to the whole usb thing. When it appeared to show up at all first time around, i had tapped the menu button while in recovery. And the natural way I'd been holding it applied just a little pressure on the usb cable. Well I got the phone to finally show all the notifaction tab options for debug and storage when i held down the usb plug in the phone down a little bit. I'm guessing that the pins for power are fine but maybe the data pins, or maybe one of the data pins is loose and thus it's an unkown device since it's not responding correctly.
I didn't have time to finish trying to fix it at work, and i'm stuck in class now. I'm'a see if i can get admin access on my terminal here and download everything while the teacher does his orientation. Otherwise i think i can fix it once i'm home now.
=====EDIT=====
Well getting the phone into Download Mode was a bit easier with Ubuntu via ADB since I don't have to wait for Windows to load the driver. Then just rebooted the box into windows for Odin. Long painful story short, I didn't setup Rom manager to be able to undo my changes when the USB port went bad/inconsistent and didn't expect those changes to complicate the recovery without USB. So I'm making sure it's a rather provable issue and going down to ATT with it. 7 Days from receiving the phone, and I'm goin in for an exchange due to bad USB. Funny.
Hi all, this is my first post here, but I've been reading walkthroughs for a while now. I really apologize for being such a noob, but any help/pity to help a girl figure out if she's just bricked her phone would be greatly appreciated.
I tried to flash a Gingerbread beta I got through one of these forums. I used Odin to root and it seemed like the install went OK, but when the phone started back up the screen went through a crazy colors standby (red, green, blue lines all over it), right after Samsung and before AT&T. This continued to happen at that point of startup every time, in case that's helpful. I also would randomly not send texts even though it looked on my end like they sent. I must not have rooted it properly because I tried to install an app (ROM Manager, I believe) that needed root permissions it said it couldn't get. I decided I was not ready for the phone ROM world and read up on returning it to stock.
To do that, I found this thread:
http://forum.xda-developers.com/showthread.php?t=1116251
I used GTG's Ultimate Unbrick, but again, I must have done something wrong. I downloaded Odin3 v1.70, ran as Administrator, and connected my phone in download mode. I clicked "PIT" and selected infuse.pit, I clicked "PDA" and selected PDA_UCKD5.tar.md5, then "PHONE" and PHONE_UCKD5.tar.md5. The "Re-partition" box was checked. The first time it said it failed. Two subsequent times it said nothing happened. For some reason my phone said it was "Downloading" even though nothing was happening on my computer and it said it had failed. It had been at that same screen for probably ten minutes or so with no progress I could see, and the thread mentioned it might boot loop or something, so I unplugged it. After that, it never started up again.
So far I've tried:
- Holding down power and volume buttons
- Removing the battery for about an hour
- Leaving it on its charger for about two hours
- Plugging it into the computer without SIM, SD or battery
I'm at a loss and at this point I'm pretty sure I've bricked it. I bought it from someone else (it was fully functional up to the point I tried flashing the ROM, although it said it was missing something it needed for a factory reset), so no warranty here. I'm hoping some brilliant dev will have some insight to save me from going back to a dumb phone!
Thanks for any ideas.
try putting it back in download mode and see if odin recognizes it if it does do the return to stock agian
fawn87 said:
Hi all, this is my first post here, but I've been reading walkthroughs for a while now. I really apologize for being such a noob, but any help/pity to help a girl figure out if she's just bricked her phone would be greatly appreciated.
I tried to flash a Gingerbread beta I got through one of these forums. I used Odin to root and it seemed like the install went OK, but when the phone started back up the screen went through a crazy colors standby (red, green, blue lines all over it), right after Samsung and before AT&T. This continued to happen at that point of startup every time, in case that's helpful. I also would randomly not send texts even though it looked on my end like they sent. I must not have rooted it properly because I tried to install an app (ROM Manager, I believe) that needed root permissions it said it couldn't get. I decided I was not ready for the phone ROM world and read up on returning it to stock.
To do that, I found this thread:
http://forum.xda-developers.com/showthread.php?t=1116251
I used GTG's Ultimate Unbrick, but again, I must have done something wrong. I downloaded Odin3 v1.70, ran as Administrator, and connected my phone in download mode. I clicked "PIT" and selected infuse.pit, I clicked "PDA" and selected PDA_UCKD5.tar.md5, then "PHONE" and PHONE_UCKD5.tar.md5. The "Re-partition" box was checked. The first time it said it failed. Two subsequent times it said nothing happened. For some reason my phone said it was "Downloading" even though nothing was happening on my computer and it said it had failed. It had been at that same screen for probably ten minutes or so with no progress I could see, and the thread mentioned it might boot loop or something, so I unplugged it. After that, it never started up again.
So far I've tried:
- Holding down power and volume buttons
- Removing the battery for about an hour
- Leaving it on its charger for about two hours
- Plugging it into the computer without SIM, SD or battery
I'm at a loss and at this point I'm pretty sure I've bricked it. I bought it from someone else (it was fully functional up to the point I tried flashing the ROM, although it said it was missing something it needed for a factory reset), so no warranty here. I'm hoping some brilliant dev will have some insight to save me from going back to a dumb phone!
Thanks for any ideas.
Click to expand...
Click to collapse
Check out my thread on the HOW TO. The link is on the signature line. Read it a few times.
re: the first paragraph with the colors -rainbow - it's due to lack of GB bootloaders.
The part where the phone is not responsive:
http://forum.xda-developers.com/showthread.php?p=19445643.
This link give you various method of getting into DL mode.
If it doesn't work,
try a different usb port on the pc, diff usb DATA cable, try a diff computer.
IF the phone is still not responsive, you a need a usb jig to put the phone back in DL mode.
search youtube for "usb jig". There's a vid that shows you how to make one.
gl
Hello, my reason for this thread was because I had an old Nexus S phone and one day when I turned the power on, the phone was stuck in the Google startup screen only and never fully loaded again. I have tried to reboot it, but either nothing happens or the Andriod robot comes out laying down with a exclamation point over it. I now have a new Nexus S and have moved the old mainboard to the new phone, but it also just stayed in the startup screen. So now my question is if it is possible to move the mass memory to another phone or if someone would be able to read the contents?
Breakdown:
Old phone still works, but does not fully load
Have a new phone already (to transfer the pics/videos)
Want to see what is possible?
Thank you!!! I am in no way a expert on phones/computers so if you can please speak in "English terms" LOL meaning something I can understand, that would be appreciated!!
Back in June, I turned on my TF700 with the dock attached, it started as usual.. I turned on my wifi, opened up my browser to look up plane tickets, then it restarted. I didn't think much of it, and when it loaded up again, I tried to look up tickets again, and it did the same thing. I gave up, closed it and zipped it up in my sleeve. It was a few hours before I got home, and when I took it out of the sleeve, it was quite warm! It was constantly rebooting and there was no way to turn if off. I left it out of the sleeve and let the battery die. I didn't use my tablet for a few days, and when I went to turn it on again, the same thing happened, and has been happening ever since. I have tried to start the tablet while connected to the dock, the wall charger, without the dock, with wifi on, with wifi off, etc. The tablet gets to the lock screen, I unlock it, and I only have about 10 seconds before it freezes and restarts. I am unable to turn off the device, because when I choose "shut down" from the menu, it shows that it's in the process of slowing down, but then the spinning wheel freezes and it vibrates and restarts before it can fully shut itself off. Since I can boot into android, I thought it was something that the tablet is trying to run upon startup that was causing problems. I was able to quickly get to settings and apps, to uninstall several apps, but nothing has helped. I used to have a task manager widget on the home screen, and uninstalled that too.
After doing research into the problem, I found that most people who have boot loop issues or constant restarting, are rooted and are experiencing difficulties with a new ROM. I am 100% stock. I have held down power and volume down. It gives me RCK, Android and Wipe. I have tried cold booting into android, but the same restart loop after 10 seconds occurs. I thought it might have been a bad firmware update that went through unbeknownst to me. So I downloaded the firmware file from ASUS, renamed and flashed it sucessfully. However, no change in the reboot problem. I am running the following version: US-epad-10.6.1.14.8-20130514. I know there's a new version out, but wasn't sure if I should try to flash that yet.
I am willing to try absolutely anything to fix the problem, with the EXCEPTION of wiping data. I know that would be the easy way to go, but I have photos and videos from my best friend's engagement and they are the only copies. If I am able to get my tablet to be stable enough to copy those off, I would then be willing to wipe and have a fresh start. I have tried connecting my tablet to my computer, and it is recognized. After it boots up and I unlock it, then the tablet begins to mount (I'm on windows 8). However, I still only have 10 seconds or so before the tablet restarts, and that's not enough time to even view the folders from the tablet.
It's been 3 months since this started, and I have done lots of research and tried lots of things, but nothing has helped yet. Since I haven't delved too deeply into the dev side of android (I've only rooted my S3) there is lots of android speak that I don't understand fully, or have experience with, like ADB. If someone is willing to offer suggestions on what to try, I am very good at following directions! Thank you for any help or leads you can offer.
Wow - you're in a difficult situation...
You being on stock I can only imagine the bootloop is caused by something you installed.
So if you can access settings and are able to uninstall apps, just keep doing it until you are back to the original stock setup.
Are you sure the files you are trying to save are still on the SD card? Don't know how you flashed 10.6.1.14.8, but flashing a complete firmware package ususally erases /data - although your persisiting bootloop indicates it didn't...... if the bootloop is caused by an app. And I can't imagine what else would cause it.
You could try to do a factory reset in Backup&Restore but you will loose the contents of your /data partition...
You can flash the 10.6.1.14.10 firmware file, but most likely you will also loose your data.
The only way I can think of to replace your bootloader and firmware without data loss is if you try to find a copy of the 10.6.1.14.10 dlpkgfile. That is the OTA update file Asus pushes out to users. It's a patch file, meaning it only replaces/updates new files and leaves everything else alone.
If you find the dlpkgfile on some forum you would have to place it into your /cache directory and reboot - and I don't know if you can copy it to your tablet before it bootloops again.
Unfortunately the reason for your bootloop is probably an app on the same partiton with the data you don't want to loose. Unless you manage to uninstall the culprit I don't see much hope....
Good luck!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Try getting adb access, this should allow us to diagnose the problem you are experiencing.
Tablet side: go to settings, developer options (if it is not visible, tap the build number 7 times), enable USB debugging
Computer side: no idea, they say Windows 8 is a bit tricky to get the drivers installed correctly.
When you have adb running, do "adb pull /proc/last_kmsg" and post the downloaded file - it should contain valuable info about your reboots.
_that6042401 said:
Try getting adb access, this should allow us to diagnose the problem you are experiencing.
Tablet side: go to settings, developer options (if it is not visible, tap the build number 7 times), enable USB debugging
Computer side: no idea, they say Windows 8 is a bit tricky to get the drivers installed correctly.
When you have adb running, do "adb pull /proc/last_kmsg" and post the downloaded file - it should contain valuable info about your reboots.
Click to expand...
Click to collapse
He's bootlooping..... How does he go into settings and turn on USB debugging?
I think the best option maybe to flash a stock Asus ROM from their site but that will wipe all data including those photos......
zanadoo22 said:
Back in June, I turned on my TF700 with the dock attached, it started as usual.. I turned on my wifi, opened up my browser to look up plane tickets, then it restarted. I didn't think much of it, and when it loaded up again, I tried to look up tickets again, and it did the same thing. I gave up, closed it and zipped it up in my sleeve. It was a few hours before I got home, and when I took it out of the sleeve, it was quite warm! It was constantly rebooting and there was no way to turn if off. I left it out of the sleeve and let the battery die. I didn't use my tablet for a few days, and when I went to turn it on again, the same thing happened, and has been happening ever since. I have tried to start the tablet while connected to the dock, the wall charger, without the dock, with wifi on, with wifi off, etc. The tablet gets to the lock screen, I unlock it, and I only have about 10 seconds before it freezes and restarts. I am unable to turn off the device, because when I choose "shut down" from the menu, it shows that it's in the process of slowing down, but then the spinning wheel freezes and it vibrates and restarts before it can fully shut itself off. Since I can boot into android, I thought it was something that the tablet is trying to run upon startup that was causing problems. I was able to quickly get to settings and apps, to uninstall several apps, but nothing has helped. I used to have a task manager widget on the home screen, and uninstalled that too.
After doing research into the problem, I found that most people who have boot loop issues or constant restarting, are rooted and are experiencing difficulties with a new ROM. I am 100% stock. I have held down power and volume down. It gives me RCK, Android and Wipe. I have tried cold booting into android, but the same restart loop after 10 seconds occurs. I thought it might have been a bad firmware update that went through unbeknownst to me. So I downloaded the firmware file from ASUS, renamed and flashed it sucessfully. However, no change in the reboot problem. I am running the following version: US-epad-10.6.1.14.8-20130514. I know there's a new version out, but wasn't sure if I should try to flash that yet.
I am willing to try absolutely anything to fix the problem, with the EXCEPTION of wiping data. I know that would be the easy way to go, but I have photos and videos from my best friend's engagement and they are the only copies. If I am able to get my tablet to be stable enough to copy those off, I would then be willing to wipe and have a fresh start. I have tried connecting my tablet to my computer, and it is recognized. After it boots up and I unlock it, then the tablet begins to mount (I'm on windows 8). However, I still only have 10 seconds or so before the tablet restarts, and that's not enough time to even view the folders from the tablet.
It's been 3 months since this started, and I have done lots of research and tried lots of things, but nothing has helped yet. Since I haven't delved too deeply into the dev side of android (I've only rooted my S3) there is lots of android speak that I don't understand fully, or have experience with, like ADB. If someone is willing to offer suggestions on what to try, I am very good at following directions! Thank you for any help or leads you can offer.
Click to expand...
Click to collapse
I have not use this method but you could try.
You need a boot OS tool on your external sd and run it from your external sd so you can access to your internal sd to copy files from there. You can search on the internet and you should find more information on how to use them depending on what boot os you are using.. Good luck.
zanadoo22 said:
and I only have about 10 seconds before it freezes and restarts.
Click to expand...
Click to collapse
sbdags said:
He's bootlooping..... How does he go into settings and turn on USB debugging?
Click to expand...
Click to collapse
Preferably FAST.
---------- Post added at 07:51 PM ---------- Previous post was at 07:51 PM ----------
LetMeKnow said:
You need a boot OS tool on your external sd
Click to expand...
Click to collapse
What is a boot OS tool?
_that said:
Try getting adb access, this should allow us to diagnose the problem you are experiencing.
Tablet side: go to settings, developer options (if it is not visible, tap the build number 7 times), enable USB debugging
Computer side: no idea, they say Windows 8 is a bit tricky to get the drivers installed correctly.
When you have adb running, do "adb pull /proc/last_kmsg" and post the downloaded file - it should contain valuable info about your reboots.
Click to expand...
Click to collapse
I was actually able to get usb debugging turned on. It took me quite a few tries, but I did it!
I've never used adb, but here's what I've done so far.. I downloaded the Android SDK and ASUS Pad PC Suite (which contains Asus Sync).
I was able to use the command prompt to navigate to the platform-tools folder and open adb, however when I type in adb devices, it doesn't recognize my device. What steps to do I take from here to be able to use adb to see my device, so I can pull the file to diagnose what's going on? How do I know if I have the right drivers installed so my computer can see my tablet? All I did was install the asus suite. Do I need to do anything further on that end?
zanadoo22 said:
I was actually able to get usb debugging turned on. It took me quite a few tries, but I did it!
I've never used adb, but here's what I've done so far.. I downloaded the Android SDK and ASUS Pad PC Suite (which contains Asus Sync).
I was able to use the command prompt to navigate to the platform-tools folder and open adb, however when I type in adb devices, it doesn't recognize my device. What steps to do I take from here to be able to use adb to see my device, so I can pull the file to diagnose what's going on? How do I know if I have the right drivers installed so my computer can see my tablet? All I did was install the asus suite. Do I need to do anything further on that end?
Click to expand...
Click to collapse
What Windows version do you have on your PC?
You can check your drivers in Device Manager. Open it, look for your tablet under Portable Devices and check if the driver has a yellow exclamation mark next to it. You should be able to update/install/uninstall the driver from here.
Try to find out if there is a setting in your Windows version to only allow Microsoft signed drivers and disable it.
Sent from my DROID4 using Tapatalk 2
Hey everyone, I've exhausted all my options (verizon, samsung, friends, google, etc) in recovering my phone. Hoping you can help.
What happened: verizon galaxy S6, stock, unsure if USB debugging was enabled (unlikely but possible, cant remember if I enabled it with this phone or my last one). I woke up and saw there was an OS update that downloaded overnight, and without thinking about it, just began the installation. The next message I saw said "installation failed" or something along those lines, can't remember exactly. After that, rebooting the phone froze on the verizon logo, and would stay until the battery died.
What I tried and what i CAN do:
Get into maintenance boot mode.
Safe mode: no change.
Simulated hard reboot: no change.
Erasing cache: No change.
Odin on phone: able to get into this from android recovery, but no program on my computer has been able to pull files or flash a rom without doing a factory reset.
Verizon wireless update assistant: Recognizes phone but can only do a factory reset, will not recover data.
Samsung smartswitch: same as above
Other details: Definitely not backed up through verizon, google, samsung (yes I am kicking myself for not going through any of these convenient services that were practically shoved down my throat).
Using a macbook, but I can get access to a PC if absolutely necessary.
When I turn my phone on, I have a yellow triangle with an exclamation point, an android with Xs for eyes rotated 45 degrees, and it goes to system recovery. When I reboot from there, it goes to a normal boot, but freezes on the verizon logo and gets stuck there.
I don't give a crap about this phone, but I have pictures from the first year of my daughter's life on it that I don't want to lose, and I was too stupid to back them up. If you can help I would be incredibly grateful. If it makes you pity me more, I've been using an iPhone 4 for a couple of weeks while I tried to sort this out on my own. I don't want to factory reset this and move on if I can save the pictures.
One last thing I tried: heimdall/jodin/flashing a stock firmware. I can consistently load odin mode and get to download mode, but jodin can't obtain the PIT file so I can't go any further.
I appreciate any help. I can just factory reset and move on, but I really don't want to lose the pictures of my daughter if I don't have to.