Develop Bugs

[Q] Calkulin's Rom won't allow recovery..

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

[Q] Random Reboots

Hello,
I am new to this forum, so If this is the wrong place I do apologize.
Ive recently purchased a new ET4G and decided to root it. I had another one rooted with no problems. Ive been using a couple different roms and this random reboot has became more frequent and has followed me with each ROM.
I have tried to ODIN back to a stock ICS build with Root and then flashing ROMS over again. I still received the same problem.
I am currently using FD26 stock with the addition of root. When the reboots happen. It seems to drain my battery drastically.
Example:This morning at 50% phone reboots and I am at 9% when it comes back on. After a couple reboots it becomes stuck and only a battery pull will allow it to reboot once again.
Anytime I flash a ROM I always follow the recommended flashing method. I do all the appropriate wipes. Id usually think It was the kernel, but even after trying different kernels the issue still happened.
If anyone could shed some light on what could be happening. I would be very appreciative.

do you do complete wipes prior to flashing?

Yes, I do. I usually wipe Davlik and then will run Caulkins format all zip before I flash any Rom. I always odin back to EL26 w/ CWM to flash through to avoid any conflicts with that.
I have no idea what to try next. I've went back to stock a couple times.

This same thing was happening to me honestly about 10 reboots a day and sometimes it would drain me down about 50% battery. I odined back to stock gingerbread using sfhubs latest method, reinstalled clockwork mod and have not had one reboot since. I think I may have heard though that the fd26 build has reboot issues so I would look into that as well. Though I see that you have tried what I have said not sure if you used sfhubs method or not but if so I would just take it back to sprint.

Have you tried flashing this? http://forum.xda-developers.com/showthread.php?t=1433101
I would flash the full restore and if it keeps rebooting unroot and return to Sprint for repair. In the meantime make sure you are not using a cheapo charger and even charge via usb only if its not too much trouble.

someguyatx said:
Have you tried flashing this? http://forum.xda-developers.com/showthread.php?t=1433101
I would flash the full restore and if it keeps rebooting unroot and return to Sprint for repair. In the meantime make sure you are not using a cheapo charger and even charge via usb only if its not too much trouble.
Click to expand...
Click to collapse
+1
Seriously, if you're having problems, to narrow it down you should not be on a leaked Android OS that is still in the testing stages. Always odin back to stock rooted to troubleshoot any issues, report back and we can get go from there.
Edit: If you need help getting back to stock rooted, please ask for help too.

Thanks for all the replies guys. I didn't try flashing the EL29 Restore, But I did try the EG30 and just OTA updated to EL29. It still didn't fix the reboot issue. Even when the phone wasn't rooted, it still would still power cycle. I just went ahead and restored it again and took it to sprint.
It happened about 10times while waiting to talk to a rep in the store. They didn't have a problem setting me up with a replacement. For now I will just use my old 3D. Thanks for the help though everyone.

I'm still stock EL29 till ICS comes out, but I get a reboot every couple days. It actually happened last night about 2AM and woke me up when the Sprint sound came on. Thought maybe there was some update (ICS?) that had caused it, but i didn't see any reason for it. It wasn't charging at the time and the battery was pretty full... Was hoping ICS update was going to fix this, but it doesn't sound promising.

RaheemA said:
Thanks for all the replies guys. I didn't try flashing the EL29 Restore, But I did try the EG30 and just OTA updated to EL29. It still didn't fix the reboot issue. Even when the phone wasn't rooted, it still would still power cycle. I just went ahead and restored it again and took it to sprint.
It happened about 10times while waiting to talk to a rep in the store. They didn't have a problem setting me up with a replacement. For now I will just use my old 3D. Thanks for the help though everyone.
Click to expand...
Click to collapse
On a previous phone (Samsung Moment) I had that issue and it turned out to be a bad battery. They let me borrow a battery in the store and it went away.

Reboots are ICS related.
Sent from my SPH-D710 using Tapatalk 2

revamper said:
Reboots are ICS related.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
got reboots in GB as well so I don't think its solely ICS related... IMO

Yeah... I still was hitting the problem while on Complete stock GB. The phone could have honestly had the problem prior to rooting and flashing. I didn't keep it stock long enough to know for sure haha

Probably not related, but I was having reboot problems due issues with App2SD, so i figure it is worth mentioning just in case...
Issue 25563: OS keeps rebooting when lots of apps are moved to SDcard! HUGE BUG IN ANDROID OS 2.3.5 (and higher)!

[Q] Stuck in an unual bootloop... Help Please!!!

I cannot get passed the samsung galaxy s2 screen. When i go to recovery it takes forever to try to wipe cache and system and comes up with miscellaneous red text problems. I have never had this happen and have flashed roms since this phone came out. Does anyone know how to get passed this??? I even odined back to various versions of os to included EK02, EL29, EL29 ROOTED, using one clicks and regular odin. Is there anyway to get passed this problem. I looked all through the forums and still can't get the phone to boot. Please help

Were you trying out CM9/AOKP? Did you do wipe data/factory reset in an ICS kernel?

Yes... I was trying the AOKP :-( I was tired so i may have used clockworkmod to wipe while on ics kernel. I know i should have used mobile odin to change kernel, I had no problem going from ics to ics or ics to GB with AGAT's . Have a made a fatal mistake? You knew exactly which rom i was trying. I know not to do that but i may have on accident. Can i get passed this? I can only get to the samsung galaxy screen. and then it turns off and comes back on. Even with the phone off and on charge... The battery charge icon shows up frozen

Can you get to download mode?

Try to boot into download mode from a cold boot, if you can do that I would suggest using ODIN, the flashing god, to restore your phone back to a stock ROM. Preferably EL29, then if that is successful use ODIN again to flash FF11.
Sent from my SPH-D710 using xda premium

I can get to download mode but when i use OC it gets stuck shortly before the modem flash. I have been successful in using 1.85 with the EL29 tar but it still does the same thing. I will try ff11 to see if that works. So many red text errors in recovery. Sometimes i can wipe data sometimes i can't. I even got to a point where i actually used nandroid to restore my backup of wicked sensations ff11 (which i was success doing a few times before the brick) I will try again... with your suggestions. Thank all of you trying to help. This is very frustrating

UGH!!! Tried the FF11 one click and it still stops at the datafs portion! Just freezes. Going to wait a year to download the odin tar from slow file factory and hope that brings some progress... If anyone knows how to get past this, it would greatly be appreciated

That doesn't sound good. Sorry man. Some people have had luck pulling the battery and leaving out our for a few hours then trying the oneclick again. Sounds like you're hard bricked though.
Sent from my SPH-D710 using xda premium

You're bricked my friend ... there goes another victim

There's a bug in the EMMC firmware that causes the phone to lockup when certain mmc erase operations are done. This basically causes a superbrick which can't be fixed at this time.
The best you can hope for is to map around the problem, which is some effort and you'll always feel you phone isn't complete.
I would suggest you get it replaced.

What is considered mapping around the problem? Is there any way i can return to sprint or will that be a no go seeing how i can't reset the binary counter (as far as a know) without a jig? It is really stranger because i can odin back using a tar but one click odins freeze at data img. I can even get to different recoveries and some are functional for wiping cache and data, even restoring nandroid but once i get to the galaxy s2 screen it's game over. And of course when charging the phone the battery logo is frozen

mremale said:
What is considered mapping around the problem? Is there any way i can return to sprint or will that be a no go seeing how i can't reset the binary counter (as far as a know) without a jig? It is really stranger because i can odin back using a tar but one click odins freeze at data img. I can even get to different recoveries and some are functional for wiping cache and data, even restoring nandroid but once i get to the galaxy s2 screen it's game over. And of course when charging the phone the battery logo is frozen
Click to expand...
Click to collapse
Same here, exactly the same.
Does any of this add up to yours? What's happening completely sucks. :/
My once bricked....

mremale said:
It is really stranger because i can odin back using a tar but one click odins freeze at data img. I can even get to different recoveries and some are functional for wiping cache and data, even restoring nandroid but once i get to the galaxy s2 screen it's game over. And of course when charging the phone the battery logo is frozen
Click to expand...
Click to collapse
Nothing is strange about it. The area of flash the /Data partition is mapped to is corrupted at the wearlevelfs level, something that cant be fixed by JTAG. From what I have seen there are 2 levels, the blue light of death and then able to get to recovery and download. The causes are pretty well known, known by Google and some parts of Samsung before we even knew about it.

Have you tried using ODIN to go back to EL26? sometimes EL29 doesn't work when i flash back to that version.

First off, thank you ALL for your replies and attempts to help. It is very appreciated! I odin'd to pretty much every kernel and rom i could. Some got me further than others. The end result was still the same. I get to see either the frozen battery charging icon or samsung galaxy s2 logo and nothing else. I did finally find a stock unrooted EL29 md5 (since everyone is on the one clicks these days) and was able to odin back to stock unrooted with no yellow triangle in hopes that my visit to sprint doesn't bad. This sucks, i can't believe i am hard bricked yet i can odin, get to recoveries, and even flash roms as well as nandroid restore. I looked into the Jtag thing i the post before this one says that's a no go too. Hopefully someone will have a miracle fix or sprint has a heart...

Think those of us with this problem are pretty much screwed...

If this helps anyone out there who may have an answer for me... I had just clean installed AOKP-39 and had a barrage of force closes... I went back into recovery (Actually didn't try flash from ics to ics or ics to gb) to wipe data, cache, ect... and that was the end of my glorious Epic 4g touch! Don't wipe anything people... If you can manage to open mobile odin through all the bs force closes, head back home that way!!!! Still hoping someone has the all spark for my Epic

mremale said:
If this helps anyone out there who may have an answer for me... I had just clean installed AOKP-39 and had a barrage of force closes... I went back into recovery (Actually didn't try flash from ics to ics or ics to gb) to wipe data, cache, ect... and that was the end of my glorious Epic 4g touch! Don't wipe anything people... If you can manage to open mobile odin through all the bs force closes, head back home that way!!!! Still hoping someone has the all spark for my Epic
Click to expand...
Click to collapse
ah, so it looks like you had a bad download of AOKP or a bad flash (they happen) and in your panic forgot to Mobile Odin back and instead you reflashed AOKP from the stock recovery?
Sorry to hear about the brick. It's definitely a good lesson for newer members to read. If you have insurance, at least you'll only have to shell out $60 or so.

Yeah, i think it may have been a bad flash. I don't know what the deal was with all the force close notifications. I didn't try to flash back, i tried to do a wipe and then the trouble came. It was bad after that, so i tried to flash and it was the same situation

To those who have recently suffered a brick due to this issue I will kindly suggest still consider taking your phone to Sprint to ask for replacement. It certainly doesn't hurt to try. As a fallback contact Samsung and you can ask them to fix/replace under warranty.
And just to clarify - is there anyone before this rash of bricks that didn't or wasn't able to get their E4GT replaced? Just curious because it seemed like just about everyone was good.

[Q] Remove Lag?

First off, hi again XDA.
Second, I've been having this problem for a while now... One day, I was working on something and I was running Team PSYCHO's JB ROM (...or someone close to that name) and all of a sudden my phone said "Shutting Down..." and turned off. I went home, plugged it in, left it charging for about three or four hours. I go to turn my phone back on and find out it's lagging out all the way. I thought it was just a root issue that happened because no matter how many times I attempted to take the battery out and restart it, it didn't want to stop lagging. I wiped the cache, almost everything (I didn't wipe the /system because I wanted to get something off there if I could, and yeah....that didn't turn out so well.) So, I go to unroot my phone and find a PGIMG32 file from XDA that everyone was using, just to be denied by my phone saying that the radio/firmware is higher than the one trying to be installed, aborting, so-on-and-so-forth. Tried doing CM9, lag. Tried going back to the JB ROM, lag-city. Decided to go to CM7, it worked fine (for the most part, still had some lag here and there.)
So, I switched back to MIUI and Venom (I now use the Venom wiper everytime I switch a ROM) to find out that those two were still laggy. Currently, I am sitting on MIUI and I am going to try that INC2 respiratory that someone put up (100% forgot the name, but saw the thread.)
My question is, does anyone know how to get rid of this lag?
Thanks again.
P.S. I don't get an upgrade until March, so if it could just last me out until then.

EVoorhees said:
First off, hi again XDA.
Second, I've been having this problem for a while now... One day, I was working on something and I was running Team PSYCHO's JB ROM (...or someone close to that name) and all of a sudden my phone said "Shutting Down..." and turned off. I went home, plugged it in, left it charging for about three or four hours. I go to turn my phone back on and find out it's lagging out all the way. I thought it was just a root issue that happened because no matter how many times I attempted to take the battery out and restart it, it didn't want to stop lagging. I wiped the cache, almost everything (I didn't wipe the /system because I wanted to get something off there if I could, and yeah....that didn't turn out so well.) So, I go to unroot my phone and find a PGIMG32 file from XDA that everyone was using, just to be denied by my phone saying that the radio/firmware is higher than the one trying to be installed, aborting, so-on-and-so-forth. Tried doing CM9, lag. Tried going back to the JB ROM, lag-city. Decided to go to CM7, it worked fine (for the most part, still had some lag here and there.)
So, I switched back to MIUI and Venom (I now use the Venom wiper everytime I switch a ROM) to find out that those two were still laggy. Currently, I am sitting on MIUI and I am going to try that INC2 respiratory that someone put up (100% forgot the name, but saw the thread.)
My question is, does anyone know how to get rid of this lag?
Thanks again.
P.S. I don't get an upgrade until March, so if it could just last me out until then.
Click to expand...
Click to collapse
yea that problem happens when some one flashed venom ROM or other sense based roms....check out my antivenom super wipe thread ....as for solution there really isnt one...buuut a good way to stop it from happening...everytime you do a backup or flash superwipe...every now and then just for the proventitive maintenance i super wipe aleast onces ever few weeks...doing that i havent had ANY death lag since the dawn of it

EVoorhees said:
First off, hi again XDA.
Second, I've been having this problem for a while now... One day, I was working on something and I was running Team PSYCHO's JB ROM (...or someone close to that name) and all of a sudden my phone said "Shutting Down..." and turned off. I went home, plugged it in, left it charging for about three or four hours. I go to turn my phone back on and find out it's lagging out all the way. I thought it was just a root issue that happened because no matter how many times I attempted to take the battery out and restart it, it didn't want to stop lagging. I wiped the cache, almost everything (I didn't wipe the /system because I wanted to get something off there if I could, and yeah....that didn't turn out so well.) So, I go to unroot my phone and find a PGIMG32 file from XDA that everyone was using, just to be denied by my phone saying that the radio/firmware is higher than the one trying to be installed, aborting, so-on-and-so-forth. Tried doing CM9, lag. Tried going back to the JB ROM, lag-city. Decided to go to CM7, it worked fine (for the most part, still had some lag here and there.)
So, I switched back to MIUI and Venom (I now use the Venom wiper everytime I switch a ROM) to find out that those two were still laggy. Currently, I am sitting on MIUI and I am going to try that INC2 respiratory that someone put up (100% forgot the name, but saw the thread.)
My question is, does anyone know how to get rid of this lag?
Thanks again.
P.S. I don't get an upgrade until March, so if it could just last me out until then.
Click to expand...
Click to collapse
Try connecting your phone to your PC, mounting as disk drive so the PC reads the card and not your phone. If the lag goes away then it could be something with the SD card maybe. Don't unroot yet before researching. Be sure you are checking md5 before flashing to ensure a good download. If you narrow down to a SD issue, remove any files you need, and wipe and reformat the card.
Sent from my Incredible 2 using xda app-developers app

Problem with Flashing Almost Everything!

I am posting this as a new topic because I don't have enough posts to post my concern in the thread of the ROM I use.
I have been using PATB ROM for a while now without any issues. Since updating to the newest version I have run into severe issues trying to flash anything besides doing Restores. Every time I try to flash something new it fails immediately and this includes trying to flash a new recovery. I did some reading and thought I had found the answer in restoring the system to stock firmware via Odin. However after trying this a short while ago the process failed as well as soon as Odin showed Recovery in the process bar. This screwed my phone pretty bad, but I was able to Odin a new Recovery on to the phone which seems to have taken it back to functioning normally. I am still unable to flash anything and the only stuff I can do inside Odin is to put different Recovery zips on the device. But even after doing that I am unable to flash anything, and it jumps to Failed right away.
I am not much more then slightly experienced when it comes to rooting and flashing but I have never come across anything like this before. I was using Xposed Framework and I unistalled it because I thought it might be causing the issue. But still no luck. This is driving me crazy. Any help with this would be greatly appreciated because I would like to try out some new ROMs. By the way my flash count reads as only 4 when taken into download mode even though I am pretty sure I have flashed more then that; unless it only trips when completely changing ROMs which would make it a correct count. So I am hoping somebody out there has seen this before and knows how to help me get past this. Thanks to those who are able to help.

Have you tried flashing the full MK4 firmware? IIRC you can't go backwards. Try this out: http://www.mediafire.com/download/7viivd985s7cp8l/L900VPUBMK4_L900SPTBMK4_HOME.tar.zip
Use Odin 3.07. If it fails go with 3.09. Please let me know if it works or not. Your partitions may be corrupt but that's a LONG shot. Let's just stick with you're trying to downgrade and the bootloader isn't letting you
Sent from my SPH-L900 using xda app-developers app

After pouring over countless articles, threads, and posts about the same problem I finally got it to work. I used Odin to put the newest TWRP Recovery on to the device and from there I attempted to flash a stock rooted deodexed MC2. After it failed 3 times I unchecked zip verification as a long shot and it took, flashing the stock ROM. At first I was a little concerned because of how fast it flashed but for the most part everything worked fine. My only problem after this was my baseband was stuck on lj1 which was easily remedied by flashing a modem zip. After that I was having issues with calls dropping almost instantly. I could have a full bar reception and as soon as the call connected it would drop and say I was outside of service area. Thinking back to something I read elsewhere I went into applications/phone and deleted the data (after backing it up) and now things seem to be running very nicely. So needless to say it has been a stressful couple days but diligence and studying got me where I needed to be (hopefully).
By the way no I have not gone to MK4 yet because of there not being any custom ROMs with additional features that make it worth it for me to do so. I will do so either once a custom ROM drops with the N3 air view features added and fully functional or when I purchase my Galaxy Gear. Until then I am going to run the MK4 modem which I have read improves reception and data speed. Thanks for the advice.
Mod this problem is officially solved and this thread can be closed and/or deleted.

dragonrider6218 said:
After pouring over countless articles, threads, and posts about the same problem I finally got it to work. I used Odin to put the newest TWRP Recovery on to the device and from there I attempted to flash a stock rooted deodexed MC2. After it failed 3 times I unchecked zip verification as a long shot and it took, flashing the stock ROM. At first I was a little concerned because of how fast it flashed but for the most part everything worked fine. My only problem after this was my baseband was stuck on lj1 which was easily remedied by flashing a modem zip. After that I was having issues with calls dropping almost instantly. I could have a full bar reception and as soon as the call connected it would drop and say I was outside of service area. Thinking back to something I read elsewhere I went into applications/phone and deleted the data (after backing it up) and now things seem to be running very nicely. So needless to say it has been a stressful couple days but diligence and studying got me where I needed to be (hopefully).
By the way no I have not gone to MK4 yet because of there not being any custom ROMs with additional features that make it worth it for me to do so. I will do so either once a custom ROM drops with the N3 air view features added and fully functional or when I purchase my Galaxy Gear. Until then I am going to run the MK4 modem which I have read improves reception and data speed. Thanks for the advice.
Mod this problem is officially solved and this thread can be closed and/or deleted.
Click to expand...
Click to collapse
If you decide to go to MK4 be sure to install Philz Cwm Recovery or your problems will start all over again