[Q] Problems after restoring in Clockworkmod - Samsung Epic 4G Touch

Hello, this is kind of a long story but.......I was in clockworkmod recovery looking to restore back to a backed up rom. I saw a backup titled, 2000-01-01.00.00.16/. I didn't remember a backup that had that named and it said it was from the year 2000. Out of curiosity I decided to backup to it. Then It got stuck or what appeared to be stuck on "checking md5 sum". After ten minutes I pulled the battery thinking it hadn't even started restoring. When I put the battery back in I got the charging battery icon with a cloud and a thermometer, assuming this meant that the phone was to hot I felt the back and it wasn't hot at all. I tried to power the phone off but each time I turned it back on I got the same icon. Finally I tried plugging it in. Then the icon went away and the booted into clockworkmod. So then I restored to the Unnamed rom and the led notification light wouldn't go off. Then every time I turn the phone off I get the thermometer icon and have to plug it in. On top of that my computer won't recognize the phone. I want to use Odin to go back to stock but since the computer won't recognize it I'm stuck with a phone full of problems. Any suggestion?

First backups can't contains signs /&%*+# etc...
Second.. can you get to recovery?
Sent from my SPH-D710 using XDA Premium App

omg .. i THINK YOU BRICKED YOUR PHONE!!
But not to worry, most likely it's an easy fix. Reboot phone a couple times, MAKE SURE DRIVERS & EVERYTHING are INSTALLED FIRST, open ODIN with proper .TAR file, .PIT NOT needed. Only Auto Reboot box should be checked, then plug in to pc. Wait for phone to connect and hit start. BE PATIENT. If it doesn't work try booting into CMW, holding POWER and VOL UP buttons. Hope this helps!

Thanks everyone for the help. I ended up downloading mobile odin from the market, and then flashing the stock unrooted EK02.tar file. I still had the same problems and figured it was a hardware problem. So I took it into my local sprint store and they took one look and it and ordered me knew for free, no questions asked!

Related

[Q] Bootloader broken, USB hub damaged, Can't ODIN

This all happened so suddenly the past few days:
1. After flashing AOKP M6, I couldn't mount my phone through USB. I kept getting a "device unrecognized" error, followed by an installation failed error. Wasn't sure what the problem was because my USB was working right before I flashed Milestone 6.
2. I was having random FCs with AOKPM6 + Eugene's kernel so I backed up my data and did a full wipe/reset from CWM. This lead to a black screen on every boot after the Samsung logo faded away, and the ROM wouldn't boot. Freaked out so I tried multiple times with multiple cables and multiple computers to get to ODIN and prevent further damage...
3. Can't get into Download mode for ODIN. I've ODIN-ed my phone at least 2-3 times when official ICS came out for our T-989 so I know I'm doing it properly. When I unplug my battery, plug it back in and hold down both volume keys, it takes me to CWM, not Download mode. I've experienced this before on the Vibrant T-959 and the reason for this would be because the bootloader is broken.
I've heard of Mobile ODIN but it does not support our T-989 :crying:
Obviously my next motive is to send in my phone for replacement for T-Mo but I can't unroot or get back to stock firmware because the USB hub on the phone is damaged. I read elsewhere on XDA that by blowing air into the USB port or by pushing around the connector inside the USB hub with a precision screwdriver, I can temporarily regain USB connection...IT ALMOST WORKED. While my Win7 laptop recognizes my Samsung phone and allows me to mount the SDcards, this same does NOT apply for rebooting to Download mode from the power menu then reconnecting my USB cable when I open up ODIN.
Is there ANYTHING I can do?
Did you flash the Rom again after doing the full wipe?
Sent from my SGH-T989 using xda app-developers app
if not that's explain y it won't boot lol
Sent from my SGH-T989 using xda app-developers app
No I didn't even have the ROM .zip on my phone anymore. Either way I FIXED IT! I woke up earlier and was still content on getting it working somehow. I kept playing around a precision flat head screw driver after putting my phone into Download mode from the power menu. Button combination still wasn't working. My computer and ODIN detected the phone so I flashed right away and tried not moving my phone at all. The first time it lost connection to my phone half way so it didn't install properly and went to a weird alternate Download mode screen that said something like "your upgrade wasn't properly installed, connect to Kies and recovery"...Kies obviously didn't recognize my phone so I saw that ODIN still recognized my phone. Tried restoring from ODIN again and it worked! Went to a bootloop, displaying only the SAMSUNG logo but I went into stock recovery, wiped data/factory reset and everything is okay!
I called TMO to order a replacement- a phone with a working USB hub so I can mount mass storage and whatnot. Weird thing is that this phone's USB is working a-okay. I plugged it into all of my different ports on different PCs and, at least, this stock 2.3.6 TWROM is always asking me if I'd like to mount my phone as removable storage. Both internal and external sdcards are working fine. Very, very strange.
I hope this helps someone who comes across this problem.
**A precision flat-head screwdriver was used to poke the connector sticking in your USB port in your phone (it's the only thing somewhat popping out of your USB port). Don't go too hard, but push the connector up, down, left, right. There's obviously no "right way" to do this so be gentle as not to break it altogether. This is just a temporary fix. I don't know how long this will work for. The first few times I positioned the connector the right way it only stayed that way for a bit and my computer then recognized it as an "unrecognized/unknown device." Now, somehow it's been working for the last 4-5 hours, even after ODIN-ing and unplugging/replugging, etc.
Dude if you wiped the phone in cwm and just rebooted I'm pretty sure that's y you got the black screen after boot. To my understanding when you use super wipe that wiped the Rom off your phone so without flashing another Rom or restoring a nandroid your phone wouldn't boot cause there wasn't anything for it to boot.
Sent from my SGH-T989 using xda app-developers app
I believe u are just using the wrong key combo for download mode. For me its volume down and power for download mode and both volume for recovery.
Sent from my SGH-T989 using xda premium
bobby3306 said:
Dude if you wiped the phone in cwm and just rebooted I'm pretty sure that's y you got the black screen after boot. To my understanding when you use super wipe that wiped the Rom off your phone so without flashing another Rom or restoring a nandroid your phone wouldn't boot cause there wasn't anything for it to boot.
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
I was using aokp_hercules_unofficial but the seemed to be a problem of it sticking upside down. so i decided to reflash the phone. I tried to load the new rom on the phone but it would not be recognized by my computer. My galaxy s 3 had no problem connecting. so i loaded drop box before anything and downloaded it to the phone. did a back up and then i wiped everything and went to look for the file and could not find it nowhere. i tried restarting the phone and it would not go into cwm at all. the 3 button combo only takes me to odin mode (download) if i try to power the phone it flashes Samsung for a second and stays black. I dont want to have to send it in but if i do it shows no binary custom number and says Samsung official.

[Q] Phone constantly reboots before getting to CWM or ODIN

So my S2 is stuck constantly rebooting before I can attempt to get the phone into download mode or back to CWM.
The best luck I've had so far is to rather consistently press the power button while the phone is trying to boot. This keeps the phone booting for the longest, and I've even made it into CWM and ODIN doing so. However anytime I stop tapping the power button, the phone will reboot.
At one point I did do a super wipe of the cache and OS, I just haven't been able to flash the phone back to stock. The same behavior occurs with a charged battery, a battery-less phone plugged into the wall, and a phone plugged into the wall with the battery in it.
I've opened up my phone to take a look at the power button placement. The plastic case is not pressing in the button, and when I press it in myself I hear a distinct click noise as normal. I've even pried away the case with no luck.
What next steps do I have? I do not have insurance with t-mobile or warranty of the phone. I do have the knowledge to solder if needed. Are there more options for me to try, to fix this issue?
EDIT: So this time I was able to get into ODIN, after letting the phone sit and do nothing for a week. No idea why it works now. I flashed back to stock. Will give it a day or two and then flash back to custom.
If you can get a computer to recognize the phone it can be fixed using adb or another method.
Sent from my SGH-T989 using Tapatalk
So now it's in ODIN and staying there! I don't know why, it never did before.
Should following this be all I need?
http://forum.xda-developers.com/showthread.php?t=1513359
My only confusion is, what is "This will restore to T-Mobile 2.3.6 ULKL1." ? I only know I have the T-Mobile T989 version.
ralewis said:
So now it's in ODIN and staying there! I don't know why, it never did before.
Should following this be all I need?
http://forum.xda-developers.com/showthread.php?t=1513359
My only confusion is, what is "This will restore to T-Mobile 2.3.6 ULKL1." ? I only know I have the T-Mobile T989 version.
Click to expand...
Click to collapse
what i know for sure is that it should be T-Mobile uvlh1 which im 98% sure is the standard base band when i got my phone
but other than that is your phone already rooted?
also when you go in CWM what does it say?
Does it just freeze?
So I did go through with the link and flashed back to stock. Everything seems to be working great now. I did nothing to the phone and it stopped acting up.
What used to happen is the device would act like I was holding the power button constantly. It would simply reboot, but never freeze. It felt Software independent, which worries me that it'll come back.
The problem started slowly, where my phone would reboot on its own here and there. Gradually getting worse. This happened after applying some OTA updates for CyanogenMod10. Though it didn't happen immediately after applying the updates.

[Q] Can't get past "Samsung Galaxy Note II" screen on reboot

I recently flashed a Pacman 4.3 ROM and today decided to restore my phone back to my stock/rooted Nandroid file that I made beforehand. Used CWM and, after it said the restore was completed, I went to reboot and have been unable to get past the "Samsung Galaxy Note II" bootscreen. It'll go to that screen for a bit and then the entire screen will go black, requiring me to take out and reinsert the battery to do anything else. I can get it into recovery mode and download mode and have tried using factory resets, cache clears, and Odin to try and reset everything back to the original stock firmware, but so far nothing has worked. Every time, I wind up looking at the "Samsung Galaxy Note II" screen for a bit and then the entire screen shuts off.
Can this phone be saved or am I SOL?
Edit: If I take the battery out and put it back in and don't try to turn on the phone, I can plug my phone into my charger and I get a visual on the screen saying the battery is charging and the LED lights up red. For what it's worth.
cptcliche said:
I recently flashed a Pacman 4.3 ROM and today decided to restore my phone back to my stock/rooted Nandroid file that I made beforehand. Used CWM and, after it said the restore was completed, I went to reboot and have been unable to get past the "Samsung Galaxy Note II" bootscreen. It'll go to that screen for a bit and then the entire screen will go black, requiring me to take out and reinsert the battery to do anything else. I can get it into recovery mode and download mode and have tried using factory resets, cache clears, and Odin to try and reset everything back to the original stock firmware, but so far nothing has worked. Every time, I wind up looking at the "Samsung Galaxy Note II" screen for a bit and then the entire screen shuts off.
Can this phone be saved or am I SOL?
Edit: If I take the battery out and put it back in and don't try to turn on the phone, I can plug my phone into my charger and I get a visual on the screen saying the battery is charging and the LED lights up red. For what it's worth.
Click to expand...
Click to collapse
This is gonna sound like a long shot, but are you sure your battery has juice? I had something very similar to what happened to you on a tablet I owned. I thought the device was messed up, but it was just really low on battery somehow. Left it sitting on the charger for a few hours and it came back.
cptcliche said:
I recently flashed a Pacman 4.3 ROM and today decided to restore my phone back to my stock/rooted Nandroid file that I made beforehand. Used CWM and, after it said the restore was completed, I went to reboot and have been unable to get past the "Samsung Galaxy Note II" bootscreen. It'll go to that screen for a bit and then the entire screen will go black, requiring me to take out and reinsert the battery to do anything else. I can get it into recovery mode and download mode and have tried using factory resets, cache clears, and Odin to try and reset everything back to the original stock firmware, but so far nothing has worked. Every time, I wind up looking at the "Samsung Galaxy Note II" screen for a bit and then the entire screen shuts off.
Can this phone be saved or am I SOL?
Edit: If I take the battery out and put it back in and don't try to turn on the phone, I can plug my phone into my charger and I get a visual on the screen saying the battery is charging and the LED lights up red. For what it's worth.
Click to expand...
Click to collapse
Charge up phone....
Try this.
http://forum.xda-developers.com/showthread.php?t=2618447
Thanks for the help guys, I managed to fix it. What I did was download the stock ROM file from here: (can't post the URL for some reason) and then opened Odin, put it in the PDA slot, put my phone into Download Mode, connected it to my computer, and ran it. Phone rebooted back to a factory reset version.
The link I used is from a site called "Stockroms" and, after typing stockroms, add the following to the URL: .net/file/GalaxyNote2/SGH-I317/I317UCAMA4_I317ATTAMA4_ATT.zip
cptcliche said:
Thanks for the help guys, I managed to fix it. What I did was download the stock ROM file from here: (can't post the URL for some reason) and then opened Odin, put it in the PDA slot, put my phone into Download Mode, connected it to my computer, and ran it. Phone rebooted back to a factory reset version.
The link I used is from a site called "Stockroms" and, after typing stockroms, add the following to the URL: .net/file/GalaxyNote2/SGH-I317/I317UCAMA4_I317ATTAMA4_ATT.zip
Click to expand...
Click to collapse
Excellent. Congrats
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

Soft Bricked Phone Tried a lot of stuff

recently I tried to put a rom on my phone (koodo s2x), so I rooted it went all good, did a back up.
went to put the mod on holy crap phone is dead
try to do recovery wont work
tried to do odin pda recovery but it wont recognize phone
tried kies recovery wont recognize phone
put a rom on my sd card for stock koodo rom on my phone
loads up but gets stuck on android welcome screen, literally 10 minutes in to get to add google account
Try odin pda for tmobile rom same thing
Please help, pretty desperate I like having the ability to communicate with people
newupdate
I just ran recovery again and now I can run about 10 seconds on first start up without lag then after that it craps out again and goes into unbelievable non forgiving lag mode
I'm pretty sure I have the same problem. My phone just sits here doing the very little vibrate it does when it starts. over an over again. I can't access recovery, or download mode, and when I just plug it into the wall, the charge thing shows up for a couple seconds, and then its back to the vibrating and restarts. I'm not even seeing the Samsung screen show up at all. THIS IS RIDICULOUS.
hoiychoiynoiy said:
I just ran recovery again and now I can run about 10 seconds on first start up without lag then after that it craps out again and goes into unbelievable non forgiving lag mode
Click to expand...
Click to collapse
i had that problem due to a virus, rogue program, what i did, format usb storage(make sure you save all your music & pictures to ext sd or computer) then reflashed rom making sure to wipe data and such. hope that helps
What Odin version? I found 3.04 best for 4.1.2. No luck at all using Odin 3.07.
Sent from my Nexus 7 using Tapatalk

VM Soft-Bricked...I know...

Well, guys was doing pretty well there for a second, I had just installed CarbonROM, was tweaking to my heart's content. Flashed a bad file in an attempt to improve speaker clairity, and boom stuck on the HTC boot logo.
Popped open the back, unplugged the battery, rebooted into HBOOT, rebooted into recovery and attempted to restore one of my backups I took right before flashing the bad zip. Failed. Can't load the data partition.
Ok, got the RUU file from this thread: http://forum.xda-developers.com/desire-816/general/ruu-htc-desire-816-a5chl-ruu-file-t2920254
Downloaded, put on root of SD card, renamed, rebooted to HBOOT, it picked it up, seemed to flash it, but it also seemed to go faster than it should. I'm suspecting it failed as well.
So now I've just got my phone sitting in recovery. Unable to mount the data partition.
Any clue on what I can do now? Hoping I haven't bricked this sucker...
Ok, my persistence paid off....Mods feel free to close this thread, I came up with a fix.
For anyone else in the same rut, this is how I fixed it...
Downloaded stock recovery from this link: https://drive.google.com/file/d/0B4NAwrQOaS7QVkxFYnhFZmhjOGc/view
Flashed stock recovery from Fastboot.
Loaded into stock recovery, key combo'd Volume UP + Power, got to the menu. Did a factory reset. Guess it reset partition mount points or something.
Rebooted to Fastboot, flashed TWRP, rebooted to recovery, restored a backup, and bam I'm back!
kenmoini said:
Ok, my persistence paid off....Mods feel free to close this thread, I came up with a fix.
For anyone else in the same rut, this is how I fixed it...
Downloaded stock recovery from this link: https://drive.google.com/file/d/0B4NAwrQOaS7QVkxFYnhFZmhjOGc/view
Flashed stock recovery from Fastboot.
Loaded into stock recovery, key combo'd Volume UP + Power, got to the menu. Did a factory reset. Guess it reset partition mount points or something.
Rebooted to Fastboot, flashed TWRP, rebooted to recovery, restored a backup, and bam I'm back!
Click to expand...
Click to collapse
Haha I had this same problem before, was ready to send my phone back. I was so scared and it wasn't working for like 3 days.
FoxyDrew said:
Haha I had this same problem before, was ready to send my phone back. I was so scared and it wasn't working for like 3 days.
Click to expand...
Click to collapse
Yeah, note to self, never get a phone without a removable battery. The sticky pads under the back cover while I was popping it off were annoying. Thankfully my phone was only down for a few hours.
kenmoini said:
Yeah, note to self, never get a phone without a removable battery. The sticky pads under the back cover while I was popping it off were annoying. Thankfully my phone was only down for a few hours.
Click to expand...
Click to collapse
This phone has a non-removable battery. You don't need to take out anything, all you do is hold volume up + the power button for 10 seconds or more. It will ALWAYS hard power off no matter what state the phone is in.
Also, what file did you flash over to improve the speaker clarity which broke your phone? I spoke to you about this earlier in my CarbonROM thread. I actually was able to fix the boomsound issue and there is no more crackling in my speakers. I'm going to post how to do it when I get home.
Edit: SORRY! Volume UP, not DOWN. Got mixed up
LiquidPlacidity said:
This phone has a non-removable battery. You don't need to take out anything, all you do is hold volume up + the power button for 10 seconds or more. It will ALWAYS hard power off no matter what state the phone is in.
Also, what file did you flash over to improve the speaker clarity which broke your phone? I spoke to you about this earlier in my CarbonROM thread. I actually was able to fix the boomsound issue and there is no more crackling in my speakers. I'm going to post how to do it when I get home.
Edit: SORRY! Volume UP, not DOWN. Got mixed up
Click to expand...
Click to collapse
I tried Vol Up/Down + Power for at least 30 seconds, was just stuck at HTC logo screen and I could feel the phone getting hotter so instead of having it run down the battery I decided to pop off the top. The back is meant to be non-removable but starting at the SD/SIM slot...slot, a guitar pick works great to undo the clips. Used a credit card to separate the sticky pads from the back. Pulled out the battery cable from the mainboard and reseated it, started it back up in HBOOT.
I flashed some sorta ZIP that's used with the HTC One M8 phones, figured if they have BoomSound it'd help too but noooope, haha. Can't remember what it was called. Did a lot of searching, tried Viper4Android, that sucked, tried tweaking the DSP, nothing came close to the original.
Sharing my own bricking experience
I'm a newbie, but I wanted to share my own experience from a few days ago. I bricked my VM/USA 816 when I was restoring a ROM backup of CM12 over a stock ROM. I was stuck on the CM12 blue "alien head" boot screen. I tried to get into the recovery screen by holding down power & volume, but it would only reboot and load CM12 again and not TWRP.
After a couple of hours of trying to get into recovery and deciding not to wait for the battery to drain because I thought the blue CM12 logo might burn into the screen. I decided to try to remove the cover and unplug the battery. I started at the SIM/SD Card slot trying to pop the cover off a little with a small screw driver to get a credit card(CC) between the cover and phone. Once I got it started I moved clockwise(cover side up) around with either a bent CC or a smaller cut up piece of CC to pop the tabs. I wasn't very gentle since I knew I wasn't going to return the phone and I bought the phone from VM with account balance so I didn't feel like I was really going to waste $300. Thank HTC the plastic cover is very forgiving. Once you get past the HTC logo you have to worry about the sticky tape around the bottom half of the phone where the battery is located. The bent CC was the best tool here and as I said earlier I wasn't very gentle while pulling off the cover once the tabs were loose.
Once I had the cover off I didn't know how to unplug the battery connector so I decided to pry the battery out. Once I did that I could see that the connecter pops up. I plugged the battery back in but the phone tried to load CM12 again. I don't remember if I had to press power button to turn on phone or it started when I connected the battery. I got back into the same state as before with a boot loop with no way getting back into recovery. So I unplugged battery again and connected the phone to my PC. I could see the screen the flashing between the charging screen and TWRP, but I couldn't get into recovery with buttons or screen touches. I then went into a command window on my PC to try the adb command. First I did a "adb devices" then I did a "adb reboot recovery" to get into TWRP. Once in TWRP I did an advanced wipe and installed CM12, gapps and supersu again from my ext SD Card. I'm not sure but I may have done a format of the internal storage just to be safe. Once I was up and running again I replaced the cover starting again clockwise from the SIM/SD Card corner and all the way around the phone till you get near the SIM/SD Card slot and have to replace the flap which is held in place by the cover/phone.
I hope this helps anyone who runs into the same problem.
kenmoini said:
Well, guys was doing pretty well there for a second, I had just installed CarbonROM, was tweaking to my heart's content. Flashed a bad file in an attempt to improve speaker clairity, and boom stuck on the HTC boot logo.
Popped open the back, unplugged the battery, rebooted into HBOOT, rebooted into recovery and attempted to restore one of my backups I took right before flashing the bad zip. Failed. Can't load the data partition.
Ok, got the RUU file from this thread: http://forum.xda-developers.com/desire-816/general/ruu-htc-desire-816-a5chl-ruu-file-t2920254
Downloaded, put on root of SD card, renamed, rebooted to HBOOT, it picked it up, seemed to flash it, but it also seemed to go faster than it should. I'm suspecting it failed as well.
So now I've just got my phone sitting in recovery. Unable to mount the data partition.
Any clue on what I can do now? Hoping I haven't bricked this sucker...
Click to expand...
Click to collapse
You have to flash and use CWM 6.0.5.1 and wipe the same partitions that were backed up in your STOCK nandroid backup.
Once you do this, reboot to hboot. Enter fastboot. Flash the stock recovery. Wipe the data/cache/dalvik. Reboot and go to hboot again. (Your device won't be able to boot yet.) Enter fastboot again.
Flash CWM (ONLY CWM) and make sure it flashes by flashing it twice back to back without leaving fastboot at any point.
Boot into recovery and once loaded reboot into hboot once more then go once again to fastboot and flash Philz Recovery with the same double flash process.
Now boot into it, mount as a USB and create a clockworkmod/backup folder on the device root directory since Philz Recovery doesn't use the buried part of the system like CWM.
Drag and drop your stock root nandroid backup. Use Philsz recovery to restore it. Boot up and your phone will boot after 3-5 minutes.
Flash back CM11/12 if you'd like.
Sent from my 710C using XDA Free mobile app
kenmoini said:
Ok, my persistence paid off....Mods feel free to close this thread, I came up with a fix.
For anyone else in the same rut, this is how I fixed it...
Downloaded stock recovery from this link: https://drive.google.com/file/d/0B4NAwrQOaS7QVkxFYnhFZmhjOGc/view
Flashed stock recovery from Fastboot.
Loaded into stock recovery, key combo'd Volume UP + Power, got to the menu. Did a factory reset. Guess it reset partition mount points or something.
Rebooted to Fastboot, flashed TWRP, rebooted to recovery, restored a backup, and bam I'm back!
Click to expand...
Click to collapse
Hello
Thank you for sharing your solution.
I have a problem which is described in this thread: http://forum.xda-developers.com/des...im-boots-fastboot-t3316255/page3#post65409302.
My questions to you:
1. My bootloader is locked. Is it possible to flash stock recovery on it?
2. I tried to flash official rom but I received the message "Partition update fail!". Can what you did, resolve this problem?

Categories

Resources