[Q] Not sure what to make of this... possible softbrick? - Samsung Epic 4G Touch

I rooted and have been using Calk's 1.1 +setcpu, everything was fine. I upgraded to 1.5 and thought I'd give the battery saver script a chance so I uninstalled SetCPU. This turned out to not be a great idea. My phone must not like the lower voltages, it started to bug out(wouldn't unlock, would freeze up after a little use) I was able to get SetCPU set up again, conservative 500-1200 w/o any voltage scaling. Things seemed to be working much better.
Now though, my phone wont boot past the the bootanimation. the screen just goes blank. I can charge the phone, I can boot to download mode(though heimdall can't detect it) and adb can't see the phone either so I can't restore my nandroid.
I did order a jig the other day, is that my only option? I've had the phone for 1 week.

did u try re flashing the reflashing the rom.... or flashing the stock voltage zip
you mentioned download mode and not clockwork
Sent from my SPH-D710 using xda premium
Sent from my SPH-D710 using xda premium

I can't access cwm, I have no way to boot into recovery. Heimdall is working now, I flashed this kernel forum.xda-developers.com/showthread.php?t=1277000 but phone still goes blank after booting. Can I push a rom via Heimdall?
EDIT: I see that you can push a rom through Heimdall, but you must extract and flash the parts separately.
I'm going to try just flashing through odin.
EDIT 2: Didn't realize that I could boot to recovery by holding vol up and power... I feel very silly.

Related

[Q] Camera Fix not working for me.

I tried the camera fix posted here : http://forum.xda-developers.com/showthread.php?t=970452
I used Odin, all I get after it finishes is my phone sits on a blank screen with Samsung written on it. It never finishes booting.
Before I tried running the camera fix kernal, I used
Stock EB13 Deodexed EXT4 + CW 3.0.0.6 listed here: http://forum.xda-developers.com/showthread.php?t=853209 posted by art3mis-nyc.
It worked fine, except for the lag when rotating phone, (known issue, I was able to fix using the fix posted on the forums) and the video lag.
So I am guessing that the EB13 that I am running isn't compatible with the camera kernal update?
So...my question is, is there a patch I can get to fix that, or do I need to install a different mod? So far, I have only updated my phone via modem, and not through clockwork(which means I have more reading to do, if that is the direction I must take)
Thanks guys.
Try the Genocide 0.3a kernel. Should work perfect.
Sent from my SPH-D700 using XDA App
bjhill2112 said:
Try the Genocide 0.3a kernel. Should work perfect.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
+1
Works flawlessly for me.
Ok. On that note, the eb13 I installed says it is prerooted and has clockwork installed. How do I findclockwork to then install the Genocide? I am watching a youtube on how to use clockwork, but apparently I have no icon for it, and I tried the (hold volume down, camera button and power button at same time) and nothing happened.
I am at a loss.
1. Download the Genocide kernel .zip and copy it to your SD card.
2. Power the phone off.
3. Once completely shut down hold vol down, camera and power until you see the clockwork mod menu
4. Choose install zip from SD card and choose the kernel zip you downloaded.
5. When it says completed (after the screen flickers once or twice) choose reboot and you should be good to go.
insanity213 said:
1. Download the Genocide kernel .zip and copy it to your SD card.
2. Power the phone off.
3. Once completely shut down hold vol down, camera and power until you see the clockwork mod menu
4. Choose install zip from SD card and choose the kernel zip you downloaded.
5. When it says completed (after the screen flickers once or twice) choose reboot and you should be good to go.
Click to expand...
Click to collapse
Will I need to install a custom ROM too, or can I stick with my stock EB13?
Thanks insanity, and other posters.
I finally figured out how to get into clockwork. But the 5 minutes between posts wouldn't let me state that.
I was going to use the "trulyEpic which is about 130mb, and the genocide one I downloaded is like 8mb. Is it supposed to be so small?
b3nny said:
Will I need to install a custom ROM too, or can I stick with my stock EB13?
Click to expand...
Click to collapse
Menchelke said:
Thanks insanity, and other posters.
I finally figured out how to get into clockwork. But the 5 minutes between posts wouldn't let me state that.
I was going to use the "trulyEpic which is about 130mb, and the genocide one I downloaded is like 8mb. Is it supposed to be so small?
Click to expand...
Click to collapse
I do believe the kernel works with stock eb13 as well. Give it a shot! Thats what development is all about.
And yes, around 8mb sounds about right for the kernel size.
Menchelke said:
Thanks insanity, and other posters.
I finally figured out how to get into clockwork. But the 5 minutes between posts wouldn't let me state that.
I was going to use the "trulyEpic which is about 130mb, and the genocide one I downloaded is like 8mb. Is it supposed to be so small?
Click to expand...
Click to collapse
Yes its that small. The rom includes everything for your phone. All the system stuff. That's why its so big of a file the kernel is just that so when u flash the rom u have to flash the kernel afther the rom is installed
Sent from my SPH-D700 using XDA App
Ok. Got ya, so since I had an eb13 rom, just flashing the genocide kernal over it, made basically the few changes he listed including the camera fix. BTW, flashed it, and camera is fixed. Big thanks to everyone.

Off + plugged into ac charger = recovery?

Been having this problem since I rooted and installed the latest CWM recovery via rom manager. I'm currently on cm 7 rc1 if that helps
Sent from my HTC Vision using XDA Premium App
It's more of a "feature" than an issue I believe. Could be wrong.
I don't prefer it either, I would try another rom to see if it happens on there as well.
Yes this happens all the time it is known.. I hate it too I like to do a full charge while phone is off... not much can do except try to talk to dev...
IIRC, the image icon for when the phone is charging while its off is stored in the stock recovery. Since we flashed cwm over it, everytime we plug our phones in to charge while its off, the phone will call for it, make it go into recovery, and then we get cwm.
Get the same thing with CWM on gingervillain 1.5
A Gingervillain-ized G2
eioous said:
Get the same thing with CWM on gingervillain 1.5
A Gingervillain-ized G2
Click to expand...
Click to collapse
The rom has nothing to do with it. Its all with us flashing CWM over our stock recovery.
Working as intended.

Clockwork cycled from 3.1.0.1 (Purple) to 3.0.2.5 (Orange)

I just got a little bug from trying to undervolt/clock my phone. It froze on the spot so I pulled the battery. Restarted, then started getting Google Framework FCs. Rebooted into CWM (I currently sport purple) and fixed permissions. When I hit reboot system, my phone went dark and then booted into Orange clockwork. I hit reboot system on that, phone kept FC Launcher Pro and Google Framework. Rebooted again into purple CWM, fix permissions again, and now phone seems to be fine again.
I currently run SyndicateROM Frozen 1.2 with the Twilight Zone Kernel v1.1.1. I noticed within the Twilight Kernel's thread that it mentions having CWM 3.0.2.5 built in. Prior to installing this Kernel I have been running CWM 3.1.0.1 and the Genocide 1.2 Kernel. Before installing Twilight Zone I asked around, and was lead to believe from others I could install the kernel and have my CWM remain purple. Up to now it's been fine. I do wonder, however, is this supposed to happen? Does having CWM run in 2 different versions simultaneously pose a threat to my phone? Should I install another Kernel? Any help would be appreciated.
PS: I tried to search but only found "[Q] Phone stuck in CWM" and "Help! Bricked my phone" threads. Sorry in advanced if this has been posted before.
Edit: Rebooted again from a widget to see what's up ... booted into Orange, and when trying to boot from there, phone freezes. Managed to fix it by pulling battery and manually (Vol Down, Power, Cam buttons) entering CWM. Doing so boots me into Purple, and from there I can reboot my phone. This is making me nervous :3
Still would like help with this
Odin and start from scratch... i assume u have some weird corrupted/stale data...
There is a known issue with Clockwork Mod on some Epic 4G kernel setups, if you update your Clockwork Mod from the Redirector App, it will only update the one produced by "reboot into recovery" I don't know too many details about it, but you can look it up online if you are interesting. The best workarround is to always update clockwork mod by booting into recovery mode by shutting down, and booting it into the recovery. This only affects redirector.
You should be able to just update your Clockwork Mod from recovery mode. If it doesn't update properly, use Odin to do the update to Clockwork Recovery.
I don't know the tech terms but I am sure someone will post em lol. What it is... your phone has 2 recoverys. The kernel one and one you boot with 3 fingers. That's why its always said to boot with 3 fingers and not off of rom manager. It just simply boot looped off your kernel... there are real terms for these I just don't know em
Sent from my SPH-D700 using Tapatalk
slightly.stoopid said:
I don't know the tech terms but I am sure someone will post em lol. What it is... your phone has 2 recoverys. The kernel one and one you boot with 3 fingers. That's why its always said to boot with 3 fingers and not off of rom manager. It just simply boot looped off your kernel... there are real terms for these I just don't know em
Exactly right... I had this happening also and it never messed anything up. Just remeber to always use the 3 finger salute and everything will be fine
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Sent from my SPH-D700 using XDA App
Oh right, I posted this Yeah it is as everyone says, kernel uses Purple CWM and phone has Orange. Now orange is replaced with the new ACS Blue CWM. Same thing but no issues. I asked because it seemed that having 2 CWM on the phone was bound to mess things up. Not the case. At any rate thanks for the replies.
I am using ACS recovery too
Sent from my SPH-D700 using Tapatalk

[Q] Stuck in boot loop

Info on my phone:I'm using Samsung Epic 4g that was running clean GB 1.0 (build 18). I have Clockwork Mod 5.0.2.7 installed.
I was messing (foolishly I know see) with the voltages on my phone. So I went to Voltage control and under general tab and set "Min=1000Mhz" and "Max=1300" and set the CPU governor to Performance and then I hit the but to change these settings. when I did this my phone frozze and rebooted and started doing the boot loop on the Samsung screen. I figured it was the some setting for the cpu and searched for a way to reset the voltages from CWM. My search lead me to this this post I thus I searched on the genocide thread and attempted to use the tool there to reset the values from CWM to no avail. So I just gave up and tried to re flash my Clean DB(I wiped data factory reset, delvaic and cache partitions before installing) and still I get the boot loop.
No backup to restore? There is a file Voltage Control makes if you allow it called vcremoveboot-CWM.zip. Did you flash that? If that doesn't work try a Factory Data Reset.
Not to scare you but you mighta blew cpu ^^ jk but yeah use the removeboot from voltage control I hope you have one its a life saver if not then odin back to stock ec05 and reroot.
Sent from my OG Epic
If you don't have the file to remove VC boot settings just pm me. I'll send it to you and if you have a card reader on your pc just put it at the root of sd and flash it through cwm.
Sent from my SPH-D700 using Tapatalk
kennyglass123 said:
No backup to restore? There is a file Voltage Control makes if you allow it called vcremoveboot-CWM.zip. Did you flash that? If that doesn't work try a Factory Data Reset.
Click to expand...
Click to collapse
Yea unfortunately no backups. I'm still kind of new to rooting droids (only my second ROM ever) so i don't even know how i would go about doing that. I did flash a Voltage control recovery that was listed on the Genocide EC05 Kernel 2.0 forum post, but other than that and a completely new flash of Clean DB I haven't flashed anything.
Biggoron said:
Not to scare you but you mighta blew cpu ^^ jk but yeah use the removeboot from voltage control I hope you have one its a life saver if not then odin back to stock ec05 and reroot.
Click to expand...
Click to collapse
Oh God i hope not.
Zeinzu said:
If you don't have the file to remove VC boot settings just pm me. I'll send it to you and if you have a card reader on your pc just put it at the root of sd and flash it through cwm.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Thank you I definitely would like that. Unfortunately I tried a completely clean install (I wiped data factory reset, delvaic and cache partitions before installing) and still have the same loop issues.
Do you know how to odin back to stock ec05? If not I can give you a link to a video tutorial. This might help you. Just make sure you don't update to ei22 or you'll have a hell of a time trying to root it. Not bad but for a new guy its very confusing but I can walk you through that if you need it. Pm me if you need a walkthrough I can give my number and ill text you thru it ^^
http://www.youtube.com/watch?v=YQ2g6J1JgjU&feature=youtube_gdata_player
Sent from my OG Epic
Biggoron said:
Do you know how to odin back to stock ec05? If not I can give you a link to a video tutorial. This might help you. Just make sure you don't update to ei22 or you'll have a hell of a time trying to root it. Not bad but for a new guy its very confusing but I can walk you through that if you need it. Pm me if you need a walkthrough I can give my number and ill text you thru it ^^
Sent from my OG Epic
Click to expand...
Click to collapse
/facepalm I should have known that Qbking would have a video don't know why I didn't look. I Used Odin along with the video and now i'm out of the woods and safe back in EC05. I really appreciate the time, effort and quick response from you guys.
Good. Now go into CWM and do a backup. Download Titanium backup and use that as well so you are prepared next time. Glad you got it worked out. Run a backup before you flash anything.
Sent from my SPH-D700 using XDA App
No problem
Sent from my OG Epic

[Q] JB can't keep a recovery?

I just upgraded to JB, and like most of you, I've been adding things to it, mostly through CWM. The problem is, the recovery partition is (kinda) broken. Let me explain.
If I turn off my GNex and reboot it to Fastboot then use Fastboot to go to Recovery mode, or even try to boot to it from ROM manager, I get the "android on his back with his panel open and a <!> floating over him" icon. I have to pull the battery to get past that. From there, if I use the Galaxy Nexus Toolkit to flash a recovery, it will boot to it, but even if I reboot immediately, I get <!> again. If I flash CWM from ROM manager, it will work, but again, only that one time. It's like something in the shutdown process is breaking recovery.
I tried it with CWM, CWM Touch, and TWRP. Same problem.
Am I alone in this?
Is there a fix?
This happened to me after I flashed stock JB. I then flashed bigxie's rooted deodexed Rom and my recovery sticks
I am on Team Liquid vicious v2 w/ franco 200 kernel. it has been very smooth and I have been able to boot into recovery seamlessly.
I am assuming you already have root. Just go to the /system folder then rename recovery-from-boot.p to something else and cwm will stick
I've got the same problem from time to time.
Suddenly CWM is away and I have to reflash it.
Can I fix this by deleting the .p file mentioned?
Sent from my Galaxy Nexus using xda app-developers app
land.apfel said:
I've got the same problem from time to time.
Suddenly CWM is away and I have to reflash it.
Can I fix this by deleting the .p file mentioned?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Kinda weird that it's from "time to time" because if that file is there, then it should bring you back to stock recovery every time after you use your newly flashed temporary recovery. Yes, rename/delete that file and it should stick.
anton2009 said:
Kinda weird that it's from "time to time" because if that file is there, then it should bring you back to stock recovery every time after you use your newly flashed temporary recovery. Yes, rename/delete that file and it should stick.
Click to expand...
Click to collapse
Looks like deleting the files has worked soo far. Thanx
land.apfel
http://forum.xda-developers.com/showthread.php?p=28083666
Sent from my Galaxy Nexus using Tapatalk 2

Categories

Resources