Related
I know there are various threads like this one but my situation is a bit different. I tried using odin to clean install 2.2 to then use the custom rom epic experience. I attempted to install 2.2 using odin but it would get stuck in "setup connection" and I would have to quit and try again. Last time I tried my phone got the "phone connection caution computer" icon and to get into recovery I would have to hold the power and camera button, not the volume down button. When I go to try and install things straight from my SD card I would get an error like "status 7" cus I didn't have the sprint apps to install 2.2. I believe I get these errors installing straight from the card cus I rooted my phone, modifying the kernal cus I read somewhere because when trying to update, it tries to verify but can't cus things are missing or edited cus of the root. I can't try to use odin again because my computer can't recognize the phone anymore regardless reinstalling the samsung drivers. SOOOO, I'm basically ****ing stuck for sure I think. The way I access the SD card is by using an adapter. The only way I see this working is if I find a fix using the SD card, but it's looking slim cus of the stupid root.
I don't know much about this yet, as I'm still learning myself. Did you try using another usb port and are you putting the phone in download mode?. Restart the computer and the phone. Make sure odin is running before you plug in the phone as well. And try another usb port. Are you using the cable that came with the phone? That one trends to have problems for some people.
Edit: I don't believe your phone is bricked either, people tend to throw the word around to much because that arnt quite sure about the definition. Just hang in there and the community will help you get back up and running. Good luck
Sent from my shoe, I mean....Epic shoe... I mean Samsung Epic!
mxcoldhit said:
I don't know much about this yet, as I'm still learning myself. Did you try using another usb port and are you putting the phone in download mode?. Restart the computer and the phone. Make sure odin is running before you plug in the phone as well. And try another usb port. Are you using the cable that came with the phone? That one trends to have problems for some people.
Edit: I don't believe your phone is bricked either, people tend to throw the word around to much because that arnt quite sure about the definition. Just hang in there and the community will help you get back up and running. Good luck
Sent from my shoe, I mean....Epic shoe... I mean Samsung Epic!
Click to expand...
Click to collapse
You see, I'm out of options. Last thing I thought of was installing a custom rom 2.1 rom cus 2.2 roms need odin, but I try to install and I get a signature error or whatever. I'm about to throw the phone against the wall, crack the screen, and use my warranty and get a new phone cus I literally tried EVERYTHING. I spent my ****ing 8 hours of my saturday trying to fix this.
Try a different computer my new Dell XPS 9100 will never reconize my Epic, however, my wifes laptop will always reconize it. I know that sounds weird, I always thought I had a poblem with my phone but it ended up being my computer.
Sent from my SPH-D700 using XDA App
cbpagent72 said:
Try a different computer my new Dell XPS 9100 will never reconize my Epic, however, my wifes laptop will always reconize it. I know that sounds weird, I always thought I had a poblem with my phone but it ended up being my computer.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
omfg, I used my mom's lappy and the drivers worked. Meaning I can try and use an odin fix.
Odin can be tricky to use because of a few factors other than itself. 1) if you can, use a deskto pc and attach to a usb port literally on the motherboard, no front or pci, this may work, but this I what I found (reading countless threads) to be the most failsafe for everyone. 2) your sammy usb cable is for charging or non critical data transfer ONLY, as it is garbage... repeatedly proven in the threads. 3) reboot pc and phone, boot phone into download mode, (hold down 1. On physical keyboard and press power... DO NOT CONNECT YET! Start up odin, place files where needed (.pit, etc...) uncheck all but what you're told in the flashing instructions with the file you're flashing, most have awesome detals, but sometimes your little issue is resolved on page 50 of the thread... not in the OP. Ok so now plug in the usb connection, odin should find it. If it doesn't, search for drivers, uninstall, reinstall start over, OR you have a bad connection, refer back to usb port and cable. I have 1 out of 4 mobo usb ports that the drivers will maintain a connection to, so try another. Then, once odin has a connection, make sure you're following the guides to the T (and read all the posts)... after that, odin is your best friend. The problem lies elsewhere... odin is the goods. If you have run into problems maintaining connection, and plan to re-root, read all the one click posts and if it drops connection a lot, enter the commands in one by one, repeat if one fails till it sticks. There are way better guides, but you seem to have run into the same issues I did, and after hours and hours, I got that scary ass reconnect me now screen. Just read the whole threads, and if your problem hasn't already been resolved, post in the appropriate thread, so others may learn from your discoveries!
Don't give up, once you figure out the quirks of the relationship between your pc and phone, and of course meticulously follow instructions, your elation when successful will make you forget that pesky 'bricked' screen... trust me I got it too, and no matter how much everyone says you can't brick these following instructions on here... its still scary till it all works. If things are wonky, wipe, go back to DI18 and start over... or just sit tight for froyo roms... good luck!
Oh, and sorry for no links, but it would seem you've probly already read em all... not sure I can do links...
Maybe its just my eeepc that doesn't like the drivers, good luck! Sounds like you're on the way... oh don't forget with the drivers to let em install on connect, leave it plugged in for like 10 mins, unplug, it will then complain it wasn't done, reconnect, then after that finishes, reboot. Crazy drivers...
At least I got a computer recognizing my phone, so I can try and use odin. I've been trying to use this fix
http://forum.xda-developers.com/showthread.php?p=9755894#post9755894
and so far odin has been stuck at this one step "file analysis..."
Yeah I used that method to no avail, but it was about 3 pasts old at the time, so I figured id try
something more stable. Tried a couple dk17 roms, then went back to 2.1 and am now using syndicate xtreme. Id suggest going back to DI18, then go from there. Let me check for another post of mine, theres a dialer code I had to do too at one point...
Ok when doing one click root, someone suggested ##8778# in the dialer, then keyboard enter, then set UART to pda not modem. This and removing comodo firewall, all the sudden my intermittent connection was solid. Not responsible for what this does, but it worked for me. Never found out what it does..... still curious. So this may help you even in odin, try to flash di18 after doing this, then the all in one rom you're looking at...
Oddly enough, I managed to semi-brick my phone several hours ago - my wireless adapter was on the same USB header, and both the wireless adapter and the phone crapped out while trying to flash with Odin.
Thankfully I was still able to get into download mode, and plugging the phone into a different USB port worked fine.
After some more research, about 10 hours of it, odin finally cooperated with me after I downloaded about every kind of file that could make my phone work and finally got it into 2.1
I first flashed the stock kernal to get it working, then flashed stock 2.1
Now I'm that my phone isn't rooted anymore I tried installing 2.2 through the recovery menu and I still get error status 7. Any ideas?
Probly best to post in the thread for the package/rom you are trying to install... others using it should be able to help... or you can do a 2.1 rom and wait for a final froyo based rom... glad to hear you're not bricked... the only way I've heard you can absolutely do that with these is installing a GSM rom or something crazy like that... but non-functional phone is scary regardless...
ungovernable1977 said:
Probly best to post in the thread for the package/rom you are trying to install... others using it should be able to help... or you can do a 2.1 rom and wait for a final froyo based rom... glad to hear you're not bricked... the only way I've heard you can absolutely do that with these is installing a GSM rom or something crazy like that... but non-functional phone is scary regardless...
Click to expand...
Click to collapse
Alright I completely fixed my phone. After I rooted my phone on 2.1, I then used odin v1.6 to install the froyo .tar file into pda and it worked. I then rooted it again so now I'm back to normal. Honestly, I did so many things I forgot what I did but I now have my phone functional. Thanks for help everyone, I greatly appreciate it!
I spent all day yesterday trying to fix my Epic with no progress and feeling a little sol.
Yesterday I decided I needed a new ROM/kernel because I was averaging only 4hrs of battery life with Supernova and wanted to try Nebula ROM with EXT4. I backed up everything on my laptop and did a Nandroid backup as well. I also have Titanium backup backed up on my pc. I always always back up. I started fresh by flashing to stock and starting over. I rooted with 1 click, flashed DK28, and where I believe I screwed up is I didn´t upgrade to Clockwork 3 (looking back I don´t know wtf I was thinking by proceeding the following way), instead I went to advanced, reboot recovery and ended up rebooting my system into 2.5.1.2. I rebooted my phone and all was good, powered off, 3 fingered and I still had 2.5.1.2 so like a dumbass I figured I was good to go ahead and flash Nebula. LOL so what happened? the Rom installed, I finished like I always do and when I went to boot up my phone I flashed into v2.5.1.0 and thats where my phone stays. If I try to do anything it gives me E: Can´t open/cache/recovery/log
I tried to restore of course and I get this message. I have tried to Odin back to stock but my phone will not connect to a pc.
Heres my situation. I live in a house with 6 computers that I have attempted to connect to with no luck, 5 of these have adb and the Android SDK, several drivers (including the Epics) installed and the C drives have literally no more space. The other pc has Windows 2000 so I wondered if it won´t install the drivers or pick up my phone because its so old??? My main laptop is running Ubuntu and Im not understanding how or even if I can Odin my phone on it, besides I think this laptop won´t connect to my Epic because of the USB port and I dont have a clue how to detect or fix that. My mom has a brand new PC with Windows 7 thats never had anything connected via USB yet that I thought was worth giving a shot at. I only have the stock USB cable though and I was wondering if I bought a new cable if it would be more likely that my phone would connect.
I am not very educated on Android or computers so I prob shouldn´t have done as much flashing as I have to begin with. If I understood file systems better I would prob figure it out.
Thanks for any help or advice. If I over looked the answer in front of my face I am sorry it is because I am retarded and don´t understand computer lingo.
Are you connecting the proper way to odin?
Step 1: open odin with phone Disconnected from PC (if you dont open it first it may not recognize your phone, so i hear)
Step 2: hold 1 on keypad and power on phone --> download mode
step 3: connect phone to PC
step 4: Flash rom
if odin still isnt recognized I would suggest taking out your microsd card and put it in another phone or a microsd card reader and put a basic dk28 rom/dl18 (maybe the acs one that includes modem) rom on there then put the sdcard back in your phone and flash that in clockworkmod and see if it'll boot (wide data/cache/dalvik before doing this)
Also search the forum i'm pretty sure theres an RFS formatter somewhere that'll format your /system/data/cache back to RFS, you probably need to do that before flashing back the other rom...
So, if I understand the OP correctly, you accidentally flashed an ext4 only rom on rfs with 2.5.1.0?
This thread had a flashable reRFS conversion, just in case you need it.
This thread has a cwm flashable di18 and modem.
Those should get you up and going again with cwm 2.5.1.0. If they don't, Odin is really the answer and I don't know what to tell you.
So I tried both of your ideas and I am so pist off. I am now stuck in download mode and cant get 7 freaken computers (one literally brand new with Windows 7, one with Vista, one with XP, 3 with Linux, 1 with 2000 out of being desperate with 5 different usb cords to connect. Clearly my phone is the problem because the sd reader can read my sd just fine and my mom, sister and gramps connect o the same computers just fine. Ive accepted that I am ****ed at this point. I have never got this phone to stay connected to a pc and I think I hate it.
It is starting to sound like it is time to head to a sprint store.
Erica8123 said:
I am now stuck in download mode and cant get 7 freaken computers (one literally brand new with Windows 7, one with Vista, one with XP, 3 with Linux, 1 with 2000 out of being desperate with 5 different usb cords to connect.
Click to expand...
Click to collapse
Have you tried to just pull the battery out? Then, put it back in the phone and boot into CWM? Or pull the battery, then boot into recovery? I personally hate going to the Sprint store and I try every possible option before going.
If you can get another USB cable it will probably work. I use an evo cable. Also for future reference there are no custom kernels on dk28.
Sent from my Evo Killer!!!
Hey, I just wanted to update.
I had tried several usb cables to connect btw including a new one I just bought. No luck. I had tried literally everything to fix my Epic and I was super pist during my last post lol. I finally had to cave and take the block walk (literally) down to Sprint and thank God I insured my phone. He was hella cool about it, just laughed and said he doesn't want to bother with it and replaced it. I am still trying to decide what I wanna do as rooting goes (besides getting rid of pretty much every app they put on there).
Thanks again everyone
I have no objections to booting into my Windows partition if it'll help prevent bricks, but I'd like to have the flexibility of flashing or recovering from either OS.
I know programs like Heimdall are around, but are they as fault tolerant or informative as their Windows equivalents?
LLStarks said:
I have no objections to booting into my Windows partition if it'll help prevent bricks, but I'd like to have the flexibility of flashing or recovering from either OS.
I know programs like Heimdall are around, but are they as fault tolerant or informative as their Windows equivalents?
Click to expand...
Click to collapse
AFAIK, Heimdall isn't working 100% yet. I tested 1.3.1 and 1.3.2 for myself, and both versions failed. The developer is working on it, though
You really only need to use Odin or Heimdall ONCE, though, and from there on you can just use CWM to wipe and flash new ROMs (which won't trip the flash counter). With my old Captivate, I didn't actually need to use odin/heimdall at all, because I was able to flash a rooted update.zip directly from Samsung's own recovery (before it got replaced with ClockworkMod).
I'm not going to let Windoze touch my ATT SGS3 on principle.
So, my neighbor bought an Acer A500 a few months back. He ended up not liking it so I bought it off of him. My tablet and I got really close and I fell in love. I started neglecting my girlfriend and all that. We had a beautiful relationship; my tablet and me. But, a couple days ago I was playing N.O.V.A 3 and it froze. I thought nothing of it and just powered it down. To my dismay, it froze at the Acer screen. I restarted it again and got the same thing. My life was over. My heart felt like it was ripped from my chest... I shed a manly tear.
I've tried vol- and power, vol+ and power, the reset button, D/Ling several different update.zip files and copying them to my SD. I've spent the last couple days reading and trying everything. All I get is the Droid guy with the blue thing swirling in his chest and then him laying on the ground with a red triangle and an exclamation point.
I'm told it's most likely not a hardware issue as things things are almost bullet-proof. But, I am pretty good at breaking things
Am I screwed or does someone have a miracle they can share. My gaming life depends on it.
-Dennis.
DennisPimps said:
So, my neighbor bought an Acer A500 a few months back. He ended up not liking it so I bought it off of him. My tablet and I got really close and I fell in love. I started neglecting my girlfriend and all that. We had a beautiful relationship; my tablet and me. But, a couple days ago I was playing N.O.V.A 3 and it froze. I thought nothing of it and just powered it down. To my dismay, it froze at the Acer screen. I restarted it again and got the same thing. My life was over. My heart felt like it was ripped from my chest... I shed a manly tear.
I've tried vol- and power, vol+ and power, the reset button, D/Ling several different update.zip files and copying them to my SD. I've spent the last couple days reading and trying everything. All I get is the Droid guy with the blue thing swirling in his chest and then him laying on the ground with a red triangle and an exclamation point.
I'm told it's most likely not a hardware issue as things things are almost bullet-proof. But, I am pretty good at breaking things
Am I screwed or does someone have a miracle they can share. My gaming life depends on it.
-Dennis.
Click to expand...
Click to collapse
Do you know what you were running on this thing? Was it stock Honeycomb, scock ICS, or was it running a custom ROM? (If so which one?)
Was it ever hooked up to your PC? (This would help with retrieving CPUID, if it was.) Do you know your CPUID? (Or SBK?)
You should at the least know the answers to these questions before you attempt any type of repair, as it is almost certainly salvageable, but you will almost certainly need your CPUID.
Danny2 said:
Do you know what you were running on this thing? Was it stock Honeycomb, scock ICS, or was it running a custom ROM? (If so which one?)
Was it ever hooked up to your PC? (This would help with retrieving CPUID, if it was.) Do you know your CPUID? (Or SBK?)
You should at the least know the answers to these questions before you attempt any type of repair, as it is almost certainly salvageable, but you will almost certainly need your CPUID.
Click to expand...
Click to collapse
I was running 4.0.1 ICS. I do have my cpuid and SBK. I tried flashing a new rom using blackthund3rs flash tool but it got to about 25% and stopped. I keep losing sync with my PCs, though.
DennisPimps said:
I was running 4.0.1 ICS. I do have my cpuid and SBK. I tried flashing a new rom using blackthund3rs flash tool but it got to about 25% and stopped. I keep losing sync with my PCs, though.
Click to expand...
Click to collapse
So, do you want to go back to stock, or to a custom ROM? If you wanna go stock, the easiest way would be load a 3.01 EUU, & upgrade on the play market to 4.03. That will prove it isn't a hardware issue. Alternatively, you could root, load a recovery, a bootloader, & flash a new ROM.
Danny2 said:
So, do you want to go back to stock, or to a custom ROM? If you wanna go stock, the easiest way would be load a 3.01 EUU, & upgrade on the play market to 4.03. That will prove it isn't a hardware issue. Alternatively, you could root, load a recovery, a bootloader, & flash a new ROM.
Click to expand...
Click to collapse
To be honest, I really don't care as long as I can getting it working again. But I would rather root it.
I think I can get it to work but neither one of my computers will recognize it. It shows up in APX and says something about recovery driver mode when I plug it into the laptop with Vista automatically downloads a driver and installs it again. I've tried turning off automatic driver install but that doesn't work for some reason. The one with XP Pro just shows up APX device but the APX Flash Tool by blackthund3r says it can't find it. I've downloaded the Acer Iconia 500 drivers and installed them but that doesn't work either. I'm at a loss.
Any tips would be great. I think I have a better chance using my laptop with XP, though. I also need to let you know that I truly do appreciate you trying to help. If you're ever in Columbus Ohio, let me know and I'll buy you a beer. lol
DennisPimps said:
To be honest, I really don't care as long as I can getting it working again. But I would rather root it.
I think I can get it to work but neither one of my computers will recognize it. It shows up in APX and says something about recovery driver mode when I plug it into the laptop with Vista automatically downloads a driver and installs it again. I've tried turning off automatic driver install but that doesn't work for some reason. The one with XP Pro just shows up APX device but the APX Flash Tool by blackthund3r says it can't find it. I've downloaded the Acer Iconia 500 drivers and installed them but that doesn't work either. I'm at a loss.
Any tips would be great. I think I have a better chance using my laptop with XP, though. I also need to let you know that I truly do appreciate you trying to help. If you're ever in Columbus Ohio, let me know and I'll buy you a beer. lol
Click to expand...
Click to collapse
Sorry,I thought I responded to this yesterday, but just now noticed I didn't.
Fire it up in APX mode, and install the 3.01 EUU from the development section, (Stock ROM listing) then simply follow the upgrade path to 4.03, then root. If you drivers are installed correctly, everything will work fine, if not, nothing will happen. If it does start to load the stock ROM, then fails with a write error after it attempts to write the bootsector, you may need to run Badsector, or babsector, depending where you look. Search the recent posts on this, you will find lots of stuff.
Danny2 said:
Sorry,I thought I responded to this yesterday, but just now noticed I didn't.
Fire it up in APX mode, and install the 3.01 EUU from the development section, (Stock ROM listing) then simply follow the upgrade path to 4.03, then root. If you drivers are installed correctly, everything will work fine, if not, nothing will happen. If it does start to load the stock ROM, then fails with a write error after it attempts to write the bootsector, you may need to run Badsector, or babsector, depending where you look. Search the recent posts on this, you will find lots of stuff.
Click to expand...
Click to collapse
How would I go about installing the EUU? I have nvflash and blackthund3r's flashing tools. But I can't seem to get my PC and tablet to connect. When I plug it into my PC without being in APX mode, it just says MTP Device. When I plug it in while in APX mode it does say something about Picasso Recovery Driver.
If you could explain things to me like I'm aN idiot, I'd really appreciate it.
Thanks,
Dennis
DennisPimps said:
How would I go about installing the EUU? I have nvflash and blackthund3r's flashing tools. But I can't seem to get my PC and tablet to connect. When I plug it into my PC without being in APX mode, it just says MTP Device. When I plug it in while in APX mode it does say something about Picasso Recovery Driver.
If you could explain things to me like I'm aN idiot, I'd really appreciate it.
Thanks,
Dennis
Click to expand...
Click to collapse
Sorry for late response, I watched for reply from yourself, but you didn't answer for 10 days, I lost track. Still need help?
Danny2 said:
Sorry for late response, I watched for reply from yourself, but you didn't answer for 10 days, I lost track. Still need help?
Click to expand...
Click to collapse
Yea, it's still bricked. I did finally get the flash tool to recognize it but it kept hanging up. I also tried Timmy Dean's EUU tool and that hangs up too. I did a little more research and found that I may have a faulty emmc. I ran babsector and got 'fatal error code 9 cannot format partition BCT.' I found a thread here that discusses how to write around the bad sectors using Linux. I'm going to give that a go... I've always wanted to learn Linux. Hey, I can't screw it up anymore than it already is, right? Again, thanks for your time and effort in trying to help.
Cheers,
Dennis
Hey, before you try that, try different USB cables and ports (if u haven't already)
I had a similar problem with my phone not maintaining stable USB link to PC... after 4 days I tried a diff USB cable and boom, snap, working.
Just a thought.....
Sent from my A500 using xda app-developers app
ericpeacock79 said:
Hey, before you try that, try different USB cables and ports (if u haven't already)
I had a similar problem with my phone not maintaining stable USB link to PC... after 4 days I tried a diff USB cable and boom, snap, working.
Just a thought.....
Sent from my A500 using xda app-developers app
Click to expand...
Click to collapse
I'll give that a go, m8.
Thanks!
-Dennis
DennisPimps said:
I'll give that a go, m8.
Thanks!
-Dennis
Click to expand...
Click to collapse
Just wondering if you ever figured out the errors you were getting during flashing? Currently having the same issues when using babsector.
Hi,
I think I've tried everything and was almost losing hope, but decided to ask for help before giving up.
I just bought an used defy, because I've had this phone before and I love it. But since it's still rocking Android Eclair 2.1 and the Google Play Store does not work, it's not very useful. So I wanted to upgrade it to Kitkat (CM, don't remember if it's 7 or 11) like I did to my previous phone.
First steps: what worked:
I've downloaded and installed Framaroot and 2ndInit (v2.3) without much issues. The problems started when I've tried to use ClockworkMod to flash an update.zip image. No matter what I did, I could make it mount the sdcard problem. I've tried with multiple sdcards, formatted the card using the phone itself, transfered the files with the card in the phone, but ClockwordMod could not mount it for anything.
I have read somewhere (maybe here) that ClockworkMod with Eclair had these kind of problems, and I would have to flash an SBF and upgrade it to Froyo before flashing anything else.
For that, I needed RSDLite, fine, did it with my other phone a few years ago. The problem is, I only have a MacBook and a PC with Windows 10 and no version of RSDLite would work with Windows 10, I've tried multiple compatibility settings with different versions of RSDLite and Motorola Drivers and nothing worked. When I was about to give up, I found out about sbf_flash utility for mac osx and linux (from here). I thought my problems were solved, but when trying to flash the sbf with my MacBook, the phone freezes and I get a "Waiting for phone" message on the screen. If I disconnect the cable, the phone instantly reboots and when it comes back to the bootloader, I get an error on the screen (attached). Again, tried with multiple variants of sbfs found on this page, with and without sudo, always with the exact same outcome. Maybe it could be an osx problem, but the only machine with linux that I have access is a raspberry-pi with ARM arch, and the sbf_flash linux binary is for intel platform and it doesn't work, so I can't test it on linux.
I have a feeling this phone was downgraded back to Eclair after being flashed to be sold, and now I can't manage to flash anything else to it.
Does anyone else has any idea about what else I could try?
Thank you all in advance, this community is amazing.
First of all,make sure you have the correct firmware
Not using mac...But i'd guess it might be solved with a flash in windows7 or xp,you can just use a vitual machine and delete it later.
I faced problem like this bcuz i connected to the front usb rather than the back one,so notice this.
Hope it would be helpful,it is great to see there is still someone using our beloved defy:laugh: