[Q] Calkulin's Rom won't allow recovery.. - Samsung Epic 4G Touch

So I I've had 2 different recoveries so far that have worked fine.. both came from Rogue though. One was from the 1.5 kernel (Hitman) which installed CWM Touch recovery, the other came with the normal recoveries based off CW 5.0.2.7. They were working fine until I installed Calkulin's Rom(2.8.1). Not sure if they're just incompatible or what, but when I go to recovery it shows the background image of the recovery but none of the options show up. It shows for about half a second and then it goes back to the original boot screen, then to the 2nd screen and turns on. So it basically skips right through the recovery and reboots. Do I need a new Rom or can I fix this? I really like the battery life and visuals of Calkulin's Rom and would love to be able to keep it.
EDIT: One more thing.. Since I installed the ROM, I've been getting market error 492. It doesn't allow me to install anything in the market..
I haven't tried a full wipe yet, so I guess I'll try that and then see how that works with the recovery and Rom..

I did the same thing to my phone this week, and I'm running Blazer, so i'm sure it has nothing to do with either ROM.
Not sure how I caused it but with so many folks running both without this error, I'm guessing that your issue (like mine was) was probably some how self induced.
I flashed back to stock and started over, and things have been working great. Might be worth a shot flashing back, or restore a backup and start fresh.
Haven't seen the market error before. I'm sure someone here has
Good Luck

If you got it off here, could you show me which stock you flashed..?

Everything you need is in the Epic 4G Touch Android Development section
Here is the post I used from Sfhub
http://forum.xda-developers.com/showthread.php?t=1433101
Watch the videos by Qbking77 They walk you thru everything step by step. (I hear his video intro rif every time I close my eyes now so you've been warned) Makes it super easy.
I would read everything you can and watch the videos before you get in too deep. I've had this phone since December, and just flashed my 1st ROM this week cause I've been reading up, and learning all I could before I jumped in the pool.

Well I've done all this with 2 phones before but I've never had this happen.. normally I just get the Rom and I'm good to go..

I think I must've gone wrong somewhere when I originally rooted through a stock rom.. It already seems to be more respondful.

premo1 said:
I think I must've gone wrong somewhere when I originally rooted through a stock rom.. It already seems to be more respondful.
Click to expand...
Click to collapse
Try booting while holding the volume up and power button.
If that does not work, flash recovery from rom manager, and that should get you into recovery to flash whatever kernel/recovery u want.

I've done all that.. None of it works.. I'm currently ODIN'ing Factory Stock Rom with root. Hopefully after that I can redo all of these and eventually end up with a working, corresponding Rom and kernel..

premo1 said:
I've done all that.. None of it works.. I'm currently ODIN'ing Factory Stock Rom with root. Hopefully after that I can redo all of these and eventually end up with a working, corresponding Rom and kernel..
Click to expand...
Click to collapse
Good Luck.

Recovery and market are now working Thank you Adanorm!

Glad your back up and running

Related

HELP! I rooted my phone and not touchwiz is gone

Hello,
Last night I rooted my device using this (http://forum.xda-developers.com/showthread.php?t=1265429) method and file from zedomax and everything worked great except when I booted my device there was a yellow triangle with a black “!” in it. I figured that just indicated the device was rooted or running a 3rd party kernel so I didn’t worry about it.
Today I launched my camera app and it failed to load the interface but showed the image from the camera momentary then crashed back to the home screen. I restarted my device and when the device restarted it was very slow and unresponsive and after unlocking it my live wallpaper was gone replaced with the last background I used before selecting a live background a couple weeks back. No icons or widgets loaded and I am unable to open the settings tray. The only things I am able to do with the phone is pull down the notification bar, respond to text messages, adjust the volume and hold power to restart the phone. All of which are very slow and delayed.
When I connect the device to my computer windows is no longer able to load the drivers and Kies is unable to connect with the device. I am not sure what caused this or how to resolve this issue so any advice or known fixes would be fantastic! I am unable to get to clockwork mod to restore my backup and I am unable to get to Kies or the phone settings to do a factory reset so I really don’t know what to do they were supposed to be a last resort and now I don’t even think I can do them. I am an experienced techie but I am new to android and this is the first device I have rooted so any advice would be great no matter how basic it may be.
UPDATE: I just connected the phone via USB to my laptop at work and it was able to discover and install everything it needed to connect with the phone. I am installing Kies now so at least there is hope of a factory restore, although I really hope it doesn't come to that!
Boot into download mode and flash the stock eg30 tar file from crawrj.
Sent From My Evo Killer!!!
Thanks Already started doing that waiting for it to download now
Still no touchwiz... great!
Try flashing a stock rom via clockworkmod.
efarley said:
Still no touchwiz... great!
Click to expand...
Click to collapse
You can root again and restore your backup, or go to this website www.lostandtired.com (midnight roms blog) click on android development and download and flash the sprint bloat and TW restore zip. Hope that helps.
I flashed the stock rom which didn't change anything so then I used clockworkMod to do a factory reset which ended up trapping me into a boot loop. I could use Odin to flash new roms but the device would never go past the 4G logo
I ended up taking the device back to Best Buy and since the loading screen showed the stock rom and they couldn't get past the 4G logo I just had to say it wasn't rooted and they gave me a new one.
I would love to know if anyone has any idea of what went wrong here so that I can feel comfortable rooting again. Also if anyone has some basic articles handy that teach basics of rooting that would be great, I didn't even know about clockwork mod until after I had this problem so knowing things like that earlier would have helped a lot I think. I'll be spending the weekend looking up everything I can find on the subject so any reading you guys can suggest would be fantastic.
efarley said:
I flashed the stock rom which didn't change anything so then I used clockworkMod to do a factory reset which ended up trapping me into a boot loop. I could use Odin to flash new roms but the device would never go past the 4G logo
I ended up taking the device back to Best Buy and since the loading screen showed the stock rom and they couldn't get past the 4G logo I just had to say it wasn't rooted and they gave me a new one.
I would love to know if anyone has any idea of what went wrong here so that I can feel comfortable rooting again. Also if anyone has some basic articles handy that teach basics of rooting that would be great, I didn't even know about clockwork mod until after I had this problem so knowing things like that earlier would have helped a lot I think. I'll be spending the weekend looking up everything I can find on the subject so any reading you guys can suggest would be fantastic.
Click to expand...
Click to collapse
If you a clockwork and "stock rom" you were still rooted...Doing a factory reset will send you into bootloop when rooted. Trying to flash other roms on a bootloop is not going to work. You need to have grabbed a backup such as Zedo has on his post and put the backup in clockwork folder on your phone. Then flash that in CWM. Would of brought you out of bootloop to a stock rom with his kernal. Now you can flash Roms and kernals or could of flashed crawf or anyone else FULL stock rom and been back to stock kernel and rom and not rooted.
dallastx said:
If you a clockwork and "stock rom" you were still rooted...Doing a factory reset will send you into bootloop when rooted. Trying to flash other roms on a bootloop is not going to work. You need to have grabbed a backup such as Zedo has on his post and put the backup in clockwork folder on your phone. Then flash that in CWM. Would of brought you out of bootloop to a stock rom with his kernal. Now you can flash Roms and kernals or could of flashed crawf or anyone else FULL stock rom and been back to stock kernel and rom and not rooted.
Click to expand...
Click to collapse
Ohhhh that's what happened! Awesome thanks. I will be much better prepared with backups out the wazoo this time haha.
Now if only I could figure out why Touchwiz died in the first place hmmm....
I hope you can figure it out, just postin here to say that when I saw this thread, it reminded me of the thread over in the EVO forums about the guy who claimed that sprint removed his Sense from his phone.
Khilbron said:
I hope you can figure it out, just postin here to say that when I saw this thread, it reminded me of the thread over in the EVO forums about the guy who claimed that sprint removed his Sense from his phone.
Click to expand...
Click to collapse
haha SPRINT removed it?! So that person thinks sprint monitors every device and has a team of techies on staff to hack your phone and brick it if you break their rules?... yeah that totally makes more sense than a file got corrupted when you were messing with the kernel.. some people maybe shouldn't be rooting their devices in the first place haha

[Q] boot loop...(sort of)

I just flashed the newest version of the codename rom (JustLoveCodename-Android-(Alpha1)2.0.0-RC to my epic 4g touch. I also flashed the Google apps pack that comes with it. It seemed nice at first, but then I tried using the market and it just kept telling me there was a server error. I tried re-downloading it from third party sites but nothing was working. So I went to flash back to Calkulins rom. As I got into recovery mode, it seems the phone somehow changed itself to another recovery system (It might've been CWM) instead of the rogue one I had prior from the initial root process. I tried flashing anyway and the a picture of a dead android with his front opened up and a red exclamation popped up. I rebooted the phone to see what would happen. It brought me right back to Code name's rom. I tried it 3 more times yet the same thing happened every time. I also tried a battery pull. It did not work. I am thinking of doing one of two things: I am going to either go through the initial root stages again or I am going to try to delete the Codename rom from my SD card and try flashing another rom (preferably Calkulin). Please tell me if this is the right thing to do or if there is another method of fixing this problem. Thank you for taking time to read this. I really appreciate any help. FYI: My phone is still in working condition, but I am stuck using the Codename rom which I really do not want to use anymore. I just was able to get ES file manager working and i checked my external sd folder, but there is nothing in it. When i look at my storage from system settings, it says i still have the memory on it. So why is ES not displaying it? =( I re-installed rogue cwm and flashed calkulin's rom again and everything is fine. Heed my advice and be wary of the Codename Rom. Editor's, you can delete this thread if you wish. =)
Gzerner said:
I just flashed the newest version of the codename rom (JustLoveCodename-Android-(Alpha1)2.0.0-RC to my epic 4g touch. I also flashed the Google apps pack that comes with it. It seemed nice at first, but then I tried using the market and it just kept telling me there was a server error. I tried re-downloading it from third party sites but nothing was working. So I went to flash back to Calkulins rom. As I got into recovery mode, it seems the phone somehow changed itself to another recovery system (It might've been CWM) instead of the rogue one I had prior from the initial root process. I tried flashing anyway and the a picture of a dead android with his front opened up and a red exclamation popped up. I rebooted the phone to see what would happen. It brought me right back to Code name's rom. I tried it 3 more times yet the same thing happened every time. I also tried a battery pull. It did not work. I am thinking of doing one of two things: I am going to either go through the initial root stages again or I am going to try to delete the Codename rom from my SD card and try flashing another rom (preferably Calkulin). Please tell me if this is the right thing to do or if there is another method of fixing this problem. Thank you for taking time to read this. I really appreciate any help. FYI: My phone is still in working condition, but I am stuck using the Codename rom which I really do not want to use anymore. I just was able to get ES file manager working and i checked my external sd folder, but there is nothing in it. When i look at my storage from system settings, it says i still have the memory on it. So why is ES not displaying it? =( I re-installed rogue cwm and flashed calkulin's rom again and everything is fine. Heed my advice and be wary of the Codename Rom. Editor's, you can delete this thread if you wish. =)
Click to expand...
Click to collapse
K. The reason you aren't getting to the old version of CWM is because you flashed Codename. Codename is an AOSP ROM which has been known to cause bricks when flashing with Rogue. Because if the bricks the developers opted to but include CWM of any kind in the kernel. What you need to do is find a replacement ROM and download it. Once you've downloaded it you need to flash the EL26 stock CWM (you can find it in the OP of the link below) then use it to flash your new ROM.
http://forum.xda-developers.com/showthread.php?p=295021
Well you're at it is suggest reading the How Not To Brick Your Phone thread in general.
Good luck!
Codename rom is an AOSP rom so your external SD storage will be under /emmc and not /sdcard/externalsd. That's why it wasn't showing up. Same thing with CM9 and AOKP, not because it doesn't work. Also I wouldn't recommend flashing anything ICS related from rogue recovery, js.
And recoveries changed because with our phones, the recovery is packed into the kernel itself so when you flashed Codename, the recovery changed to the stock recovery included with the roms kernel. Hope that clears it up lol.
Sent from my SPH-D710 using Tapatalk
If you want a fresh install, the best way is to Odin the el29 kernal. From there, get into your recovery and wipe and flash away.
Sent from my SPH-D710 using XDA

I read, I watched, I searched, I bricked(Hard)

So just got this phone a couple of weeks ago. I feel like Im no stranger to rooting/flashing, but obviously Im no expert. Ive flashed custom roms on ppc6600, ppc6700, Treo 600w, HTC Diamond, Palm Pre(rooted it, no roms), Samsung Moment, Hero, Evo 4g, Evo 3d, Hp touchpad, and for a few weeks my Epic Touch4g. Ive never had a single problem until today. I must admit when I got this phone, for the first time I was actually scared to root it/flash roms. I read and re-read everything I could find, and finally took the plunge. I had great luck until I tried to flash the jellybean port.
I was originally on Agats rom tFF18_v0.1.0 which I flashed through ODIN. I tried a few other TW roms but ultimately kept Agats rom as my nandroid back up. Since it was a safe kernel/recovery I would always restore my nandroid to do any wipes or flashes. I thought this was being safe.
This morning I updated the kernel with AGAT_v0.3.0 with tREC_v0.2.1 7/19/12, which I flashed through agats recovery. Worked fine. I then wanted to try out CM9. So heres what I did:
I downloaded/flashed the newest nightly and Gapps and flashed them in Agats recovery which worked fine. I loved CM9 so I made a nandroid back up along with my other agat rom backup. I did notice that it was a different recovery but just assumed it was safe since it was a newer nightly. (Mistake?)
I kept CM9 for a few hours and saw that a JB port was available on androidcentral. Had flashed enough without issue, so I thought I try it out.
Heres where I screwed up.
I downloaded the JB port, JB gapps and it said to get chris41g's [Kernel][AOSP] Safe CWM6/TWRP which I did.
First I wiped data(full wipe), cache, and dalvik, then tried to flash the rom in CMW recovery that came with CM9. It gave me an error and aborted the flash.
Then I rebooted the phone back into CM9 because I thought maybe I had a bad download. I went back to the site reread the OP and noticed I was supposed to flash chris41g's recovery first, so I went back into recovery, flashed the Kernel, rebooted back into recovery and tried to flash JB. I didnt wipe anything, I just flashed it. It seemed to do its normal thing, but the progress bar never grew, it just sat there. I let it sit for like 10mins and the next thing I noticed, the screen was off. I picked up the phone, hit the power button.....nothing except the blue light I had read so much about.
I accept full responsibility for what I did. But to be honest, Im really confused what I did wrong. I was under the impression that most bricks happened when doing wipes? This happened when flashing the rom, which Im sure wipes before flashing, so maybe that where I had the problem? Im gonna go to sprint tomorrow and see if they can help, so hopefully Ill get a replacement, but I DONT want it to happen again. Sorry for the MAJORLY long post, but I wanted to be thorough with my explanation so I dont make the same mistake, and maybe someone else could learn from my screw up.
If possible, please be gentle, I already feel like a total idiot.......
EDIT: BTW, if I didnt make it clear, Im COMPLETELY aware this was my fault. I knew what I was getting into, and messed up somewhere by not FOLLOWING directions to a tee.
Your mistake was not wiping anything at the jb flash part.
Plus i think people was flashing jb using the el26 recovery (cwm5) but dont quote me on that i havent read the jb flash procedure throughly
Sent from my SPH-D710 using xda app-developers app
Sometimes stuff like that just happens... Let us know how the replacement goes
Sent from my SGH-I897 using Tapatalk 2
I read somewhere they wont release the jb post on here because of all the bricks that was going on. Tell sprint u prolonged the ics update and ignored it. Then u finally decided to install and it would not boot at all
Sent from my SPH-D710 using xda app-developers app
rovar said:
Your mistake was not wiping anything at the jb flash part.
Plus i think people was flashing jb using the el26 recovery (cwm5) but dont quote me on that i havent read the jb flash procedure throughly
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Yeah I thought people were using Chris41g's EL26 CWM as well. Sbrissen himself said when in doubt use EL.
Thanks for the responses guys. My phone now has no solid blue light. Just a VERY VERY dim flashing blue light. Its been plugged in for the charger for like 2 hours. Is it possible maybe something just went wrong with battery? It was plugged in when I flashed, and the battery was pretty full, but not topped off...
vinscuzzy said:
So just got this phone a couple of weeks ago. I feel like Im no stranger to rooting/flashing, but obviously Im no expert. Ive flashed custom roms on ppc6600, ppc6700, Treo 600w, HTC Diamond, Palm Pre(rooted it, no roms), Samsung Moment, Hero, Evo 4g, Evo 3d, Hp touchpad, and for a few weeks my Epic Touch4g. Ive never had a single problem until today. I must admit when I got this phone, for the first time I was actually scared to root it/flash roms. I read and re-read everything I could find, and finally took the plunge. I had great luck until I tried to flash the jellybean port.
I was originally on Agats rom tFF18_v0.1.0 which I flashed through ODIN. I tried a few other TW roms but ultimately kept Agats rom as my nandroid back up. Since it was a safe kernel/recovery I would always restore my nandroid to do any wipes or flashes. I thought this was being safe.
This morning I updated the kernel with AGAT_v0.3.0 with tREC_v0.2.1 7/19/12, which I flashed through agats recovery. Worked fine. I then wanted to try out CM9. So heres what I did:
I downloaded/flashed the newest nightly and Gapps and flashed them in Agats recovery which worked fine. I loved CM9 so I made a nandroid back up along with my other agat rom backup. I did notice that it was a different recovery but just assumed it was safe since it was a newer nightly. (Mistake?)
I kept CM9 for a few hours and saw that a JB port was available on androidcentral. Had flashed enough without issue, so I thought I try it out.
Heres where I screwed up.
I downloaded the JB port, JB gapps and it said to get chris41g's [Kernel][AOSP] Safe CWM6/TWRP which I did.
First I wiped data(full wipe), cache, and dalvik, then tried to flash the rom in CMW recovery that came with CM9. It gave me an error and aborted the flash.
Then I rebooted the phone back into CM9 because I thought maybe I had a bad download. I went back to the site reread the OP and noticed I was supposed to flash chris41g's recovery first, so I went back into recovery, flashed the Kernel, rebooted back into recovery and tried to flash JB. I didnt wipe anything, I just flashed it. It seemed to do its normal thing, but the progress bar never grew, it just sat there. I let it sit for like 10mins and the next thing I noticed, the screen was off. I picked up the phone, hit the power button.....nothing except the blue light I had read so much about.
I accept full responsibility for what I did. But to be honest, Im really confused what I did wrong. I was under the impression that most bricks happened when doing wipes? This happened when flashing the rom, which Im sure wipes before flashing, so maybe that where I had the problem? Im gonna go to sprint tomorrow and see if they can help, so hopefully Ill get a replacement, but I DONT want it to happen again. Sorry for the MAJORLY long post, but I wanted to be thorough with my explanation so I dont make the same mistake, and maybe someone else could learn from my screw up.
If possible, please be gentle, I already feel like a total idiot.......
Click to expand...
Click to collapse
I like story's like this that are long very interesting when bored I'm sorry for your lost...try simple small stuff like the stable good looking fully working roms
sent from my DeRpY SuPeRsOnIc
vinscuzzy said:
Thanks for the responses guys. My phone now has no solid blue light. Just a VERY VERY dim flashing blue light. Its been plugged in for the charger for like 2 hours. Is it possible maybe something just went wrong with battery? It was plugged in when I flashed, and the battery was pretty full, but not topped off...
Click to expand...
Click to collapse
Seems unlikely to be the battery, sorry bud :/ seems like your issue was not wiping anything before flashing the jb rom. Not to mention the jelly bean port is unstable as is. And the ics recoveries. I don't care if people say they're safe, i still odin to el26 to flash. I would've stayed away from jb regardless. But thanks for being mature about what happened, you more than most bricks actually seem like you're careful and read.
Swyped from a Galaxy S2
vinscuzzy said:
So just got this phone a couple of weeks ago. I feel like Im no stranger to rooting/flashing, but obviously Im no expert. Ive flashed custom roms on ppc6600, ppc6700, Treo 600w, HTC Diamond, Palm Pre(rooted it, no roms), Samsung Moment, Hero, Evo 4g, Evo 3d, Hp touchpad, and for a few weeks my Epic Touch4g. Ive never had a single problem until today. I must admit when I got this phone, for the first time I was actually scared to root it/flash roms. I read and re-read everything I could find, and finally took the plunge. I had great luck until I tried to flash the jellybean port.
I was originally on Agats rom tFF18_v0.1.0 which I flashed through ODIN. I tried a few other TW roms but ultimately kept Agats rom as my nandroid back up. Since it was a safe kernel/recovery I would always restore my nandroid to do any wipes or flashes. I thought this was being safe.
This morning I updated the kernel with AGAT_v0.3.0 with tREC_v0.2.1 7/19/12, which I flashed through agats recovery. Worked fine. I then wanted to try out CM9. So heres what I did:
I downloaded/flashed the newest nightly and Gapps and flashed them in Agats recovery which worked fine. I loved CM9 so I made a nandroid back up along with my other agat rom backup. I did notice that it was a different recovery but just assumed it was safe since it was a newer nightly. (Mistake?)
I kept CM9 for a few hours and saw that a JB port was available on androidcentral. Had flashed enough without issue, so I thought I try it out.
Heres where I screwed up.
I downloaded the JB port, JB gapps and it said to get chris41g's [Kernel][AOSP] Safe CWM6/TWRP which I did.
First I wiped data(full wipe), cache, and dalvik, then tried to flash the rom in CMW recovery that came with CM9. It gave me an error and aborted the flash.
Then I rebooted the phone back into CM9 because I thought maybe I had a bad download. I went back to the site reread the OP and noticed I was supposed to flash chris41g's recovery first, so I went back into recovery, flashed the Kernel, rebooted back into recovery and tried to flash JB. I didnt wipe anything, I just flashed it. It seemed to do its normal thing, but the progress bar never grew, it just sat there. I let it sit for like 10mins and the next thing I noticed, the screen was off. I picked up the phone, hit the power button.....nothing except the blue light I had read so much about.
I accept full responsibility for what I did. But to be honest, Im really confused what I did wrong. I was under the impression that most bricks happened when doing wipes? This happened when flashing the rom, which Im sure wipes before flashing, so maybe that where I had the problem? Im gonna go to sprint tomorrow and see if they can help, so hopefully Ill get a replacement, but I DONT want it to happen again. Sorry for the MAJORLY long post, but I wanted to be thorough with my explanation so I dont make the same mistake, and maybe someone else could learn from my screw up.
If possible, please be gentle, I already feel like a total idiot.......
EDIT: BTW, if I didnt make it clear, Im COMPLETELY aware this was my fault. I knew what I was getting into, and messed up somewhere by not FOLLOWING directions to a tee.
Click to expand...
Click to collapse
Where did you have the JB ROM located, on your internal memory or your SDcard?
And wait, Flashing blue light? When mine bricked using the same methods you were using, save for the lack of wiping and I used calk's wipeall before flashing, I had a solid blue light.
Eh, Least now I have a paperweight with a nice light on it for now.
Ophois said:
Where did you have the JB ROM located, on your internal memory or your SDcard?
And wait, Flashing blue light? When mine bricked using the same methods you were using, save for the lack of wiping and I used calk's wipeall before flashing, I had a solid blue light.
Eh, Least now I have a paperweight with a nice light on it for now.
Click to expand...
Click to collapse
it was on the internal memory. And yeah, its weird. It started as a solid blue light for like an hour. I plugged in the charger and a few hours later I thought the light was completely off, but if you look real close, its a super dim flashing blue light.
vinscuzzy said:
it was on the internal memory. And yeah, its weird. It started as a solid blue light for like an hour. I plugged in the charger and a few hours later I thought the light was completely off, but if you look real close, its a super dim flashing blue light.
Click to expand...
Click to collapse
Alright, That's two people who got a brick and had flashed it from their internal.
I'll try and get ahold of the other user who bricked their device and find where they had it and from there, We'll know a probable cause and how to prevent it.
I flashed sb's jb from internal. no problem here.
on el26.
please not I am not trying to be a wise ass; however have you read through this post http://forum.xda-developers.com/showthread.php?t=1525495 ? I have "bricked" a few times and have been able to revive my phone using Odin (the pc version). seems as long as you can get the phone into "download" mode (volume rocker down and power button) be sure to check out QBKing77's posts on YouTube. you have nothing to lose and everything to gain
good luck
al_b said:
please not I am not trying to be a wise ass; however have you read through this post http://forum.xda-developers.com/showthread.php?t=1525495 ? I have "bricked" a few times and have been able to revive my phone using Odin (the pc version). seems as long as you can get the phone into "download" mode (volume rocker down and power button) be sure to check out QBKing77's posts on YouTube. you have nothing to lose and everything to gain
good luck
Click to expand...
Click to collapse
Yeah, that was the post that scared me to even root the phone. I can't get into download mode, and have been trying every combination of turning it on, vol up/dwn, plugging it in without the battery, tried different cables, chargers, scoured all the different Samsung forums to see if there was a way to force into download mode, nothing. Its completely dead. I got this phone right around the time the kernel source got released and that post hasn't been updated since may, so I kinda came to the conclusion(stupidly) that maybe the problem had been fixed. I wasn't around for all the leaks that were causing the bricks.
not being able to get into download mode = not good. there are also dongles out there that cost $5 +/-. might work. I believe you mentioned you have insurance, if that is true take the device to your local corporate Sprint store and play "Micky the dunce" i.e. I have no idea what happened to it; I was updating my PRL and this is what happened ... of course if you accidently backed over it with your car on the way to the store that may dissuade them from trying to resurrect it
vinscuzzy said:
Yeah, that was the post that scared me to even root the phone. I can't get into download mode, and have been trying every combination of turning it on, vol up/dwn, plugging it in without the battery, tried different cables, chargers, scoured all the different Samsung forums to see if there was a way to force into download mode, nothing. Its completely dead. I got this phone right around the time the kernel source got released and that post hasn't been updated since may, so I kinda came to the conclusion(stupidly) that maybe the problem had been fixed. I wasn't around for all the leaks that were causing the bricks.
Click to expand...
Click to collapse
the MMC_CAP_ERASE code that causes the emmc controller to bug out and brick is still present in the FF18 kernel, entropy512 has been in contact with samsung about this, but last time i read the emmc thread a a few days ago he was still having difficulty convincing samsung that it was actually their code directly causing all these bricks... sorry about the brick, I just spent some time with cm10 and the vanilla jb rom and thanks to you and the other gentleman that bricked flashing from internal sd I double checked that the zips were on the external... so at least you've helped some of us out! good luck with sprint
does DirectoryBind_0.2.0k.apk help with the EMMC freakiness? a month or so ago this was useful work around. http://forum.xda-developers.com/showthread.php?t=1410262&highlight=directorybind
gershee said:
I flashed sb's jb from internal. no problem here.
on el26.
Click to expand...
Click to collapse
That is the difference, The other two and I appear to have flashed it from internal but we were using CWM6.
I guess CWM6+Internal=brick whereas EL26+Internal=good to go
Though this is all conjecture, I cannot be completely sure with such a small sample size.
When I was little I once had a jelly bean stuck in my nose.
Good luck.
Pp.
Delivered to you via Mayan technology .
No worries happened to me too( sadly :/). On the lighter/much, much darker side[you choose] sprint reps. won't be able to look at your phones files probably. When it happened to me the tech just came out with the 'WTF?' face and said what did you do, to which I replied "I applied the EL29 update and my phone bricked" cheers.
Sent from my Galaxy S2 E4GT

Issue with booting on 4.3

Alright, so I am having this weird issue. I thought I found the fix for it several times, however, NO dice.
I've researched for a few hours now, I just don't know if I have over looked it or what. If it has been answered, I apologize.
I looked at the modified recoveries thread for newer s3 devices, but it doesn't seem to fit my area of error.
The Details:
I've been really curious to try some 4.3 roms. Of course, they are for D2SPR. I get them to flash correctly, after a full wipe. The issue happens right after I set everything up in the phone, and reboot. When I reboot I get hung at the splash screen. I have tried to reflash the rom muliple times only to fall flat on the splash screen again. Now, I don't have an SD Card in the phone, except, I left a TW rom in a folder. I use twrp, forgot to mention that. I rewiped the phone and installed that touchwiz rom, and still it wouldn't allow me to get past splash into that tw rom.
So the only way that I could think of to get out of this hole was to flash the rooted LJ7 tar file I have through ODIN. After getting the S3 into download mode, Odin successfully push LJ7 into my phone. Now again, I had an issue getting it to boot. I read somewhere that when this happens, I need to check the Erase NAND option in Odin. So I tried that out and forced LJ7 back on. After successfully flashing, it boots but gets stuck on the boot animation; the fix to that is booting into stock recovery and wiping once more. Then you are able to get into the OS.
I let the phone sit and take the OTAs till I get from LJ7 to MD4 so I re-root the phone using Odin and Chain Fire's root method. Now I am able to flash the recovery (TWRP) using OpenScript through Goo Manager.
I've only tried flashing Illusion and Carbon's 4.3 rom. The second time I used Carbon's rom. Same results. So I have no Idea what the heck is going on. Can anyone explain this to me better or point me into the direction that I need to go?
Thanks much!
your not the only one that has this problem i have the same thing have tried everything and most of the 4.3 roms same thing. no one on xda seems to know at least i havent gotten any help or responses i have just given u on 4.3. good luck finding any ideas.
Set it up I'm sure you restored some apps and data which may no longer be compatible. Or data which is corrupting the 4.3 rom. Try just flashing the rom setting up your Google account and don't add any apps. See if it does it.
Either way this seems to be a common issue across different devices and 4.3 seems it's part of using roms built on leaks and ports. None are bug free. Very similar to all gb leaks back in the day that would go into bootlooping.
Have a great day!
bbrita said:
your not the only one that has this problem i have the same thing have tried everything and most of the 4.3 roms same thing. no one on xda seems to know at least i havent gotten any help or responses i have just given u on 4.3. good luck finding any ideas.
Click to expand...
Click to collapse
Well, it's good to know that I'm not the only one, however, it's horrible that it's happening to others. I appreciate you spreading the info!
edfunkycold said:
Set it up I'm sure you restored some apps and data which may no longer be compatible. Or data which is corrupting the 4.3 rom. Try just flashing the rom setting up your Google account and don't add any apps. See if it does it.
Either way this seems to be a common issue across different devices and 4.3 seems it's part of using roms built on leaks and ports. None are bug free. Very similar to all gb leaks back in the day that would go into bootlooping.
Have a great day!
Click to expand...
Click to collapse
When I go to set up, I just install about 15 apps, I don't restore. I just download them fresh. I had a habit of doing that and it just stuck. I don't restore anything with Titanium or and root backup/restore app. Could one of those apps not be updated then that causes the partitions to get locked up, or just corrupt /data in general? If that's whats happening.
I just find it extremely odd that I (maybe others), can't wipe, and then re flash another rom; actually I can, it just gets stuck at the splash and never goes forward, that is what had me confused most. If I had an sd card, and formatted data itself, would that fly?
thanks Ed i have tried this after the first 2 tries . i dont have any problems installing 4.3 its just after rebooting it gets stuck. Like you said there are always bugs Im fine with using other roms for now. Hopefully when an official 4.3 drops problems will go away

Issues With Kernels

Hi there!
I have a bit of a problem with my T-Mobile S4 and I was wondering if there was anything I could do to remedy the situation. So here is the problem;
Two days ago, I was playing PPSSPP and then I saved the state so I could eat lunch. When I came back to play, I loaded the state and then all of the sudden, my screen jumbled for a split second then went black. I tried to restart my phone, but it would always boot up and then go back to a black screen. I then reinstalled my ROM and was able to use my phone again. Thinking that it was over, I decided to re-flash my kernel. But then, it happened again, only this time, I could kind of turn my screen on but it was all messed up. See photo below. I re-flashed my ROM once more, made a titanium backup of my apps and then proceeded to wipe my whole phone through TWRP, going to wipe -> advanced wipe and then selecting every check box except for external sd and USB otg. Afterward, I re-flashed my ROM once more, booted my phone to make sure it worked then flashed the kernel same thing happened. SoI tried a couple different kernels but they all produced the same results. Just a jumbled screen. What could have went wrong? And is there a chance I can fix it?
ROM used - ParanoidAndroid 3.99 RC2
Kernel used - KT-SGS4
Other Kernels tried - Chronic Kernel, Blue ROM kernel
Anyone ever have this problem?
over16bit said:
Hi there!
I have a bit of a problem with my T-Mobile S4 and I was wondering if there was anything I could do to remedy the situation. So here is the problem;
Two days ago, I was playing PPSSPP and then I saved the state so I could eat lunch. When I came back to play, I loaded the state and then all of the sudden, my screen jumbled for a split second then went black. I tried to restart my phone, but it would always boot up and then go back to a black screen. I then reinstalled my ROM and was able to use my phone again. Thinking that it was over, I decided to re-flash my kernel. But then, it happened again, only this time, I could kind of turn my screen on but it was all messed up. See photo below. I re-flashed my ROM once more, made a titanium backup of my apps and then proceeded to wipe my whole phone through TWRP, going to wipe -> advanced wipe and then selecting every check box except for external sd and USB otg. Afterward, I re-flashed my ROM once more, booted my phone to make sure it worked then flashed the kernel same thing happened. SoI tried a couple different kernels but they all produced the same results. Just a jumbled screen. What could have went wrong? And is there a chance I can fix it?
ROM used - ParanoidAndroid 3.99 RC2
Kernel used - KT-SGS4
Other Kernels tried - Chronic Kernel, Blue ROM kernel
Click to expand...
Click to collapse
I have never heard of this problem. It seems you have tried your best to fix it...
My suggestion is to go back stock and see if the problem is still there. If it is then its a hardware problem.
If its not...re-root and flash a rom and go from there.
Sent from a Insane S4
SICK MADE DEVELOPMENT
alloycowboy said:
I have never heard of this problem. It seems you have tried your best to fix it...
My suggestion is to go back stock and see if the problem is still there. If it is then its a hardware problem.
If its not...re-root and flash a rom and go from there.
Sent from a Insane S4
SICK MADE DEVELOPMENT
Click to expand...
Click to collapse
This...but use Odin to go back to stock. Dont' just try to flash a stock ROM.
REALLY reset it hardcore by using Odin to flash the stock firmware package in its entirety.
That's what I was thinking about doing, but I can't download the stock image. The download never completes. I've thus far tried to download from the hotfile mirror and from stockROMs but they're always slow and never complete. What I'd really like is a torrent, but if anyone knows of any other mirror or what might be going wrong, I'd appreciate a point in the right direction.
Thanks!
over16bit said:
That's what I was thinking about doing, but I can't download the stock image. The download never completes. I've thus far tried to download from the hotfile mirror and from stockROMs but they're always slow and never complete. What I'd really like is a torrent, but if anyone knows of any other mirror or what might be going wrong, I'd appreciate a point in the right direction.
Thanks!
Click to expand...
Click to collapse
You need to use your pc to DL the firmware....it will fail trying to from your phone.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Flash the 10.16 AOSP 4.3 build of KT's kernel. Any build newer than that is for CM based ROMs compiled AFTER 10.20.
alloycowboy said:
You need to use your pc to DL the firmware....it will fail trying to from your phone.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I am trying to download it from my PC. :/
Also, I tried the earlier KT kernel as that was the one I had on hand. Same thing happens.
over16bit said:
I am trying to download it from my PC. :/
Also, I tried the earlier KT kernel as that was the one I had on hand. Same thing happens.
Click to expand...
Click to collapse
Sounds like hardware problem. I hope im wrong.
Let us know how it goes after you odin back to stock
Sent from Insane S4
SICK MADE DEVELOPMENT

Categories

Resources