[Q] Random Reboots - Samsung Epic 4G Touch

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)!

Related

To service or not to service

So basically Sprint gave me this ticket a week ago to get my phone diagnosed and then replaced. However, the LOS problem only occurs when i root. I have the USB Jig to reset the Odin Count, so I'm wondering if such problems occur only on root should i service it? Has anyone who's been rooted for a week not experienced ONE LOS? Just wondering if its worth the trouble because LOS is not an issue with the phone, just on Sprint's side. I guess some of you got lucky, or what?
crud accidentally posted this in general
locoboi187 said:
So basically Sprint gave me this ticket a week ago to get my phone diagnosed and then replaced. However, the LOS problem only occurs when i root. I have the USB Jig to reset the Odin Count, so I'm wondering if such problems occur only on root should i service it? Has anyone who's been rooted for a week not experienced ONE LOS? Just wondering if its worth the trouble because LOS is not an issue with the phone, just on Sprint's side. I guess some of you got lucky, or what?
Click to expand...
Click to collapse
I have been rooted with stock kernel for quite sometime without any los
Sent from my Samsung Galaxy S2
R1ptide said:
I have been rooted with stock kernel for quite sometime without any los
Sent from my Samsung Galaxy S2
Click to expand...
Click to collapse
How man? lmao
locoboi187 said:
So basically Sprint gave me this ticket a week ago to get my phone diagnosed and then replaced. However, the LOS problem only occurs when i root. I have the USB Jig to reset the Odin Count, so I'm wondering if such problems occur only on root should i service it? Has anyone who's been rooted for a week not experienced ONE LOS? Just wondering if its worth the trouble because LOS is not an issue with the phone, just on Sprint's side. I guess some of you got lucky, or what?
Click to expand...
Click to collapse
Just install su+binaries+bb while you've got a root kernel and then flash the pulled stock kernel. If you want CWM there is a CWM+pulled stock kernel too, I haven't tested it yet but I'd imagine it would be just as reliable. I also hear the LOsT kernel is getting fantastic results however if you want an aftermarket performance kernel with extremely reduced LOS occurrence.
Any kernel built off of the released kernel source has this issue...while stock phones have gotten LOS it happens far far less.
It's not the rooted kernels fault...the 'stock build' non-rooted kernels built from the released kernel source also feature this bug. Samsung is giving us the deep dicking on this one. Those bastards should probably release the actual kernel source. This is holding up a lot of progress.
If you're worried about being rooted and taking it into sprint, don't be. We work on rooted phones and it doesn't void your warranty with us.
However, we still haven't received software to flash phones so there's not much they'll be able to do.
Sent from my SPH-D710 using xda premium
daneurysm said:
Just install su+binaries+bb while you've got a root kernel and then flash the pulled stock kernel. If you want CWM there is a CWM+pulled stock kernel too, I haven't tested it yet but I'd imagine it would be just as reliable. I also hear the LOsT kernel is getting fantastic results however if you want an aftermarket performance kernel with extremely reduced LOS occurrence.
Any kernel built off of the released kernel source has this issue...while stock phones have gotten LOS it happens far far less.
It's not the rooted kernels fault...the 'stock build' non-rooted kernels built from the released kernel source also feature this bug. Samsung is giving us the deep dicking on this one. Those bastards should probably release the actual kernel source. This is holding up a lot of progress.
Click to expand...
Click to collapse
I've tried that but no luck. I want to try out viper's ROM i guess. I'm not rooted currently. But what EXACT steps would you like me try? I do full wipes each time, including system and just in case the built in factory format.
squshy 7 said:
If you're worried about being rooted and taking it into sprint, don't be. We work on rooted phones and it doesn't void your warranty with us.
However, we still haven't received software to flash phones so there's not much they'll be able to do.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Oh no I'm not worried about being rooted. I can simply unroot and plug in the jig and im set. What i want is root and no LOS haha
locoboi187 said:
I've tried that but no luck. I want to try out viper's ROM i guess. I'm not rooted currently. But what EXACT steps would you like me try? I do full wipes each time, including system and just in case the built in factory format.
Click to expand...
Click to collapse
First go here:
http://forum.xda-developers.com/showthread.php?t=1282415
Follow the directions to install ODIN, drivers, etc. Also carefully follow the directions for using ODIN. Flash that. It'll nuke everything you have now but you will start back up with a brand new stock rooted install with busybox.
If you want to save what you have now flash a CWM+pulled stock kernel first, do a nandroid backup and then flash that rom in ODIN. then if you want you can re-flash the CWM+pulled stock kernel to restore your data partition if you really want...but...I recommend not. Just start over fresh. It's not that big of a pain...and if it is use Titanium Backup instead.
To stay as-stock-as-possible I recommend just putting that rooted-stock+busybox and sticking with that starting over fresh. I never got an LOS on that. If I seriously **** things up I always revert to that and it works every single time. (sometimes I break my wifi or 4G or both when screwing with custom kernels...damned if I know why, but flashing that fixes it every time).
If you still have LOS issues you are just unlucky, unroot and get a new phone and start over...but I doubt it. I bet that works out wonderful for you.
EDIT: and if that works out for you, and I'm sure it will, then you can start modifying things one at a time...next thing would be the pulled stock kernel+CWM. see how that runs...if that is fine (and it probably will be, I've never tested it though) then flash viper rom with CWM and take it from there. if something gets borked you will know at what step it occured which will make diagnosing the problem much easier...just test thoroughly after each modification.
flash this:
http://forum.xda-developers.com/showthread.php?t=1269437
then flash this:
http://forum.xda-developers.com/showthread.php?t=1305099a
that will leave you with root, CWM5, and stock kernel
daneurysm said:
First go here:
http://forum.xda-developers.com/showthread.php?t=1282415
Follow the directions to install ODIN, drivers, etc. Also carefully follow the directions for using ODIN. Flash that. It'll nuke everything you have now but you will start back up with a brand new stock rooted install with busybox.
If you want to save what you have now flash a CWM+pulled stock kernel first, do a nandroid backup and then flash that rom in ODIN. then if you want you can re-flash the CWM+pulled stock kernel to restore your data partition if you really want...but...I recommend not. Just start over fresh. It's not that big of a pain...and if it is use Titanium Backup instead.
To stay as-stock-as-possible I recommend just putting that rooted-stock+busybox and sticking with that starting over fresh. I never got an LOS on that. If I seriously **** things up I always revert to that and it works every single time. (sometimes I break my wifi or 4G or both when screwing with custom kernels...damned if I know why, but flashing that fixes it every time).
If you still have LOS issues you are just unlucky, unroot and get a new phone and start over...but I doubt it. I bet that works out wonderful for you.
EDIT: and if that works out for you, and I'm sure it will, then you can start modifying things one at a time...next thing would be the pulled stock kernel+CWM. see how that runs...if that is fine (and it probably will be, I've never tested it though) then flash viper rom with CWM and take it from there. if something gets borked you will know at what step it occured which will make diagnosing the problem much easier...just test thoroughly after each modification.
Click to expand...
Click to collapse
It says that it doesn't wipe data. I don't suspect it wipes the system partition either.
R1ptide said:
flash this:
http://forum.xda-developers.com/showthread.php?t=1269437
then flash this:
http://forum.xda-developers.com/showthread.php?t=1305099a
that will leave you with root, CWM5, and stock kernel
Click to expand...
Click to collapse
How has this worked for you?
locoboi187 said:
It says that it doesn't wipe data. I don't suspect it wipes the system partition either.
Click to expand...
Click to collapse
then wipe it, lol. Or not, try it without wiping first. If problems persist the only stuff that is left is in /data has to be the source of problems... but, after you flash that you can flash the pulled stock kern+CWM and nandroid just to be safe.
if after that still no dice, well, it's the phone or a very very very unlucky location...but that theory is still up in the air. (I don't buy it)
---------- Post added at 04:26 PM ---------- Previous post was at 04:25 PM ----------
locoboi187 said:
How has this worked for you?
Click to expand...
Click to collapse
I've also done that too. Worked great for me.
I will report back. I only get LOS when I'm in school. It appears when i go to an area where i get no bars, a circle with a slash will appear. So far so good.
Lol, I just got an LOS on 00001.PRL (alltel/verizon towers) with full bars. I haven't seen an LOS in weeks, I haven't seen it happen with full bars though.
I can confirm for the first time I do not suffer from LOS. I used R1ptide's instructions and all went well. I went to a party where no one ever got signal, so when my bars went empty i received a circle with a slash for a second. HOWEVER, it went back to the bars and didnt stay stuck on that stupid circle.
Everything is definitely good
Sent from my SPH-D710 using xda premium

[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.

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

Samsung Galaxy S4 Problem

Hello everyone,
I really need your help with my wife's Metro PCS Samsung GS4 M919N.
The thing is, we are now living outside the US so I had to unlock her phone. After ordering the unlock codes, I decided to root the phone and use a custom ROM while waiting for the codes.
That is why I found this guide here: androidforums.com/metropcs-galaxy-s4-all-things-root/790899-metropcs-galaxy-s4-all-things-root-guide.html
So while reading the guide, I aimed to have the following accomplished at the end:
Recovery: TWRP
Custom ROM: CyanogenMod 10.2.1
I then started doing the guide for the TWRP recovery by using Odin. I got the message saying that the flashing passed and went ahead to restart to recovery to install CM 10.2.1 as a custom ROM. The thing is that I keep on restarting to the stock recovery not TWRP. So I went to YouTube and found a video showing how to flash TWRP using GooManager. After following that guide, I went to restart to recovery and I successfully got into TWRP.
Now, to achieve my goal, all that's left to do is to flash CyanogenMod 10.2.1 (jfltetmo).
Before doing that, I decided to make a backup. After using TWRP to do a backup, I proceeded to installing the custom ROM + gapps (wiped with the default settings). Everything was working I think (I handed the phone to my wife so she was he one testing it). After some time, she decided she wants the stock ROM instead so I decided to download the androidforums.com/metropcs-galaxy-s4-all-things-root/783769-rom-recovery-flash-able-stock-m919nuvuamf2-rooted-deodexed-rom.html ROM.
I flashed the newly downloaded ROM + gapps (same file). This time, I couldn't get the gapps to work probably because it was meant for another version. So I decided to just restore from the backup I created earlier.
So, the usual stuff. Wipe. Restore. Restart.
Seems to be going smoothly because my wife was happy to see the old ROM she was used to.
Until the phone started to restart on it's own. (It's pretty much downhill from here on out).
At first I thought it was just a random thing that probably would never happen again. I was wrong as it became more frequent as days went by.
Recently I can't just restart the phone, I would have to remove the battery and then restart it. Now, it's getting really hard to restart the phone. Please help me fix this. I prefer to leave the phone rooted, but if the fix unroots the phone then so be it, anyway my wife prefers the stock ROM so only the unlocking was necessary.
Metro PCS Samsung Galaxy S4 M919N
Recovery:
TWRP 2.6.3.1
ROMs:
Stock Metro PCS
CyanogenMod 10.2.1
Let me know if you need more information from me. Hopefully I can restart the phone so I can give you some version numbers.
Thanks everyone!
I didn't read everything but just wanted to say
VERY GOOD THREAD!
this is how threads should be done. Very descriptive, organized, told us everything you did and asked for help! Good job man! Only negative is it prolly should have gone in Q&A section but irregardless very good thread!
About your issue, I recommend flashing stock Odin tar file to everything back to stock and reroot and start over. Flashing stock will not lock it again it will remain unlocked. But should get you back up and fresh. Just be aware it will erase all your data and all of the internal SD card.
Sent from my SGH-M919 using Tapatalk
dokgu said:
Hello everyone,
I really need your help with my wife's Metro PCS Samsung GS4 M919N.
The thing is, we are now living outside the US so I had to unlock her phone. After ordering the unlock codes, I decided to root the phone and use a custom ROM while waiting for the codes.
That is why I found this guide here: androidforums.com/metropcs-galaxy-s4-all-things-root/790899-metropcs-galaxy-s4-all-things-root-guide.html
So while reading the guide, I aimed to have the following accomplished at the end:
Recovery: TWRP
Custom ROM: CyanogenMod 10.2.1
I then started doing the guide for the TWRP recovery by using Odin. I got the message saying that the flashing passed and went ahead to restart to recovery to install CM 10.2.1 as a custom ROM. The thing is that I keep on restarting to the stock recovery not TWRP. So I went to YouTube and found a video showing how to flash TWRP using GooManager. After following that guide, I went to restart to recovery and I successfully got into TWRP.
Now, to achieve my goal, all that's left to do is to flash CyanogenMod 10.2.1 (jfltetmo).
Before doing that, I decided to make a backup. After using TWRP to do a backup, I proceeded to installing the custom ROM + gapps (wiped with the default settings). Everything was working I think (I handed the phone to my wife so she was he one testing it). After some time, she decided she wants the stock ROM instead so I decided to download the androidforums.com/metropcs-galaxy-s4-all-things-root/783769-rom-recovery-flash-able-stock-m919nuvuamf2-rooted-deodexed-rom.html ROM.
I flashed the newly downloaded ROM + gapps (same file). This time, I couldn't get the gapps to work probably because it was meant for another version. So I decided to just restore from the backup I created earlier.
So, the usual stuff. Wipe. Restore. Restart.
Seems to be going smoothly because my wife was happy to see the old ROM she was used to.
Until the phone started to restart on it's own. (It's pretty much downhill from here on out).
At first I thought it was just a random thing that probably would never happen again. I was wrong as it became more frequent as days went by.
Recently I can't just restart the phone, I would have to remove the battery and then restart it. Now, it's getting really hard to restart the phone. Please help me fix this. I prefer to leave the phone rooted, but if the fix unroots the phone then so be it, anyway my wife prefers the stock ROM so only the unlocking was necessary.
Metro PCS Samsung Galaxy S4 M919N
Recovery:
TWRP 2.6.3.1
ROMs:
Stock Metro PCS
CyanogenMod 10.2.1
Let me know if you need more information from me. Hopefully I can restart the phone so I can give you some version numbers.
Thanks everyone!
Click to expand...
Click to collapse
I agree with Elesbb. If the goal is jus tto get back to stock, just do an odin flash of the stock ROM. Be advised if you flash the latest Kit Kay update you will nto be able to go back to Jelly Bean. From your post it seems like you are partial to Jelly Bean. So if that's what you want, but sure you use the stock 4.3 ROM. You can find it around here on XDA somewhere with a quick search to make sure you have the right one.
As Elesbb said, you won't loose the 'sim unlock'. But you will lose root. However you can root the stock ROM just fine.
You might also consider one of the myriad of TouchWiz based custom ROMs. They are look just like TouchWiz that your wife wants, but have a lot of optimizations and options in them. Those should flash just like any ROM. If you still get the reboot issue then do the Odin back to stock, reroot, then flash the custom TW roms.
---------- Post added at 12:46 PM ---------- Previous post was at 12:45 PM ----------
Thread cleaned.
Rather than bashing a ROM or user let's keep on topic and help the OP resolved the problems he's having. Arguing over the virtues of a ROM doesn't help anyone.
Thank you,
Rwilco12
Before posting this thread I sent the aforementioned guide's poster (arocker). He sent me a reply saying not to use gapps as the stock ROM for Metro PCS already comes with Google apps. I'll try his suggestion first and see if the phone still reboots a lot.
If the problem persists, I will try the solutions mentioned here. Thanks a lot!
elesbb said:
I didn't read everything but just wanted to say
VERY GOOD THREAD!
this is how threads should be done. Very descriptive, organized, told us everything you did and asked for help! Good job man! Only negative is it prolly should have gone in Q&A section but irregardless very good thread!
About your issue, I recommend flashing stock Odin tar file to everything back to stock and reroot and start over. Flashing stock will not lock it again it will remain unlocked. But should get you back up and fresh. Just be aware it will erase all your data and all of the internal SD card.
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
After trying arocker's suggestion to not flash gapps, the phone still reboots. So now, I am going to try your solution guys.
But before I do, I want to make sure that I am on the correct paths/links.
Here's what I found for the following:
ODIN
forum.xda-developers.com/galaxy-s3/themes-apps/27-08-2013-odin-3-09-odin-1-85-versions-t2189539
I've had a couple of chances to use ODIN but only using specific functions like flashing a recovery file while the phone is in download mode. I don't however have any experience using ODIN to put the phone back to stock where the phone gets unrooted. Having the phone unrooted is fine by me as I only needed to have the phone unlocked.
Any step-by-step guides for using ODIN for this specific purpose guys? I don't want to mess this up again.
Thanks and sorry for the trouble.
dokgu said:
After trying arocker's suggestion to not flash gapps, the phone still reboots. So now, I am going to try your solution guys.
But before I do, I want to make sure that I am on the correct paths/links.
Here's what I found for the following:
ODIN
forum.xda-developers.com/galaxy-s3/themes-apps/27-08-2013-odin-3-09-odin-1-85-versions-t2189539
I've had a couple of chances to use ODIN but only using specific functions like flashing a recovery file while the phone is in download mode. I don't however have any experience using ODIN to put the phone back to stock where the phone gets unrooted. Having the phone unrooted is fine by me as I only needed to have the phone unlocked.
Any step-by-step guides for using ODIN for this specific purpose guys? I don't want to mess this up again.
Thanks and sorry for the trouble.
Click to expand...
Click to collapse
No trouble at all, check out the stickies in the beginning of threads.
Look for guides similar to this.
http://forum.xda-developers.com/showthread.php?t=2335109
Pp. Good luck.
sent from my bluetooth controlled toaster.
PanchoPlanet said:
No trouble at all, check out the stickies in the beginning of threads.
Look for guides similar to this.
http://forum.xda-developers.com/showthread.php?t=2335109
Pp. Good luck.
sent from my bluetooth controlled toaster.
Click to expand...
Click to collapse
Hello PanchoPlanet,
Thanks for the link. I went ahead and tried to unroot without Windows (Mobile Odin) as per the instructions on the link. I downloaded everything and went ahead to install the Mobile Odin APK. When I ran it to install the Flash Kernel, the app told me that the device is not supported.
To my understanding the guide is for M919 devices but should work for my wife's device as well (M919N - Metro PCS). I would like to try the guide for using Windows but I'm not really expecting for it to work or I might mess it up more. I'll try to search some more and provide the links where this forum will lead me to. But if you have any ideas, please let me know asap. Thanks!
PanchoPlanet said:
No trouble at all, check out the stickies in the beginning of threads.
Look for guides similar to this.
http://forum.xda-developers.com/showthread.php?t=2335109
Pp. Good luck.
sent from my bluetooth controlled toaster.
Click to expand...
Click to collapse
Ok, here's what I found:
forum.xda-developers.com/showthread.php?t=2446497
It seems like the perfect thread for what I am trying to achieve. Will let you guys know if it is successful. But it will have to wait for tomorrow. Gonna catch some sleep.
Okay, I'm running out of options. I was able to flash the stock ROM using Odin 3.07. The recovery looks like it came back to the stock recovery as I no longer have TWRP installed. When I install Root Checker, I see that I am no longer rooted. That's good.
But my original problem is still here. The phone reboots a lot. The phone is so unstable that it is barely usable.
I am now going to try one more thing.
I have a Galaxy S4 (I337M) from Rogers Canada (my wife has Metro PCS M919N). Mine got rooted and has CyanogenMod 10.2.1 as a custom ROM. My phone is working perfectly while hers reboots a lot. I was thinking it was because of a faulty battery. So I am doing an experiment by swapping the batteries. So far no reboots have occurred, but I will continue to monitor this.
Any ideas why the battery is kinda messed up?
This thread talks about battery stuff and reboots:
http://au.ibtimes.com/articles/530338/20131216/samsung-galaxy-s4-problems.htm
Batteries can go bad a lot of ways. Extreme temperature, factory defect, phone drops, moisture, etc.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Android_Monsters said:
This thread talks about battery stuff and reboots:
http://au.ibtimes.com/articles/530338/20131216/samsung-galaxy-s4-problems.htm
Batteries can go bad a lot of ways. Extreme temperature, factory defect, phone drops, moisture, etc.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
And 100% of the time, they eventually just get old.
dokgu said:
Okay, I'm running out of options. I was able to flash the stock ROM using Odin 3.07. The recovery looks like it came back to the stock recovery as I no longer have TWRP installed. When I install Root Checker, I see that I am no longer rooted. That's good.
But my original problem is still here. The phone reboots a lot. The phone is so unstable that it is barely usable.
I am now going to try one more thing.
I have a Galaxy S4 (I337M) from Rogers Canada (my wife has Metro PCS M919N). Mine got rooted and has CyanogenMod 10.2.1 as a custom ROM. My phone is working perfectly while hers reboots a lot. I was thinking it was because of a faulty battery. So I am doing an experiment by swapping the batteries. So far no reboots have occurred, but I will continue to monitor this.
Any ideas why the battery is kinda messed up?
Click to expand...
Click to collapse
That's a wierd situation, by swapping batteries you basically performed a battery pull, which acts as a reset, that in it self may have cleared your issue.
Now if battery is bad that could be an unusual problem. Maybe just replacing the battery will be the end of your mystery.
Pp.
sent from my P5113 using TouchPal mind control keyboard. (Beta)
The battery should be brand new as the phone was just recently purchased this April.
Anyways, so far no reboots have happened and any instability has not been shown at all. Everything looks ok, yet.
Anyone know if it is safe to swap batteries? Our phones have different S4 models. I'm not sure what the implications would be. Also what is this battery pull which acts as a reset? We've been pulling the battery a lot of times but the reboot still happens but not when we swapped batteries.
The batteries are all the same. Don't worry about that.
Even if its a new battery if could have just been bad. A manufacturing defect perhaps.
Sent from your phone. You should be more careful where you leave that thing.
dokgu said:
The battery should be brand new as the phone was just recently purchased this April.
Anyways, so far no reboots have happened and any instability has not been shown at all. Everything looks ok, yet.
Anyone know if it is safe to swap batteries? Our phones have different S4 models. I'm not sure what the implications would be. Also what is this battery pull which acts as a reset? We've been pulling the battery a lot of times but the reboot still happens but not when we swapped batteries.
Click to expand...
Click to collapse
This battery thing is wacky, anyway swapping batteries should not be a problem, it's just an energy storage container. Pulling the battery isn't like powering down the phone or resetting/rebooting ,sometimes devs request a battery pull to get the proper wipe effect that reboots can't provide.
You inadvertently solved your problem by accident. That's a good thing.
Pp.
sent from my P5113 using TouchPal mind control keyboard. (Beta)
PanchoPlanet said:
You inadvertently solved your problem by accident. That's a good thing.
Click to expand...
Click to collapse
I have quite literally solved the vast majority of my problems this way.
Its a preferred method.
Sent from your phone. You should be more careful where you leave that thing.
Sometimes it's that "total disconnect "of power that kind of gets all the ducks lined up in a row and everything flows in the dynaflow.
Good.
Pp.
sent from my P5113 using TouchPal mind control keyboard. (Beta)
its very important topics and it might seen for every galaxy s4 users.just wonderful topics.
This exact same thing happened on my mother's 6-month old S3. If you're still wondering, you could try putting the old battery and running a CPU stress test app. It should increase the current draw and trigger a shutdown.
EDIT: whoops, sorry to kind of zombie. Didn't check the date.
Sent from my Galaxy S4

Random reboots and freezing

Hey everyone. I am having random reboots and freezes. I was originally on a stockish OB7 rom. I decided to flash to the Alliance ROM but, I was having some issues. So I flashed stock OB7 through odin 3.07. Used CF-Auto Root. Then chilled. I started getting random reboots all day. About that time the OE1 came out so I thought skip it i'll just roll stock for a while but, low and behold some where in the update it got messed up and I lost my dialer and my camera. So then I essentially had no phone which, has caused me to have to use my wife's old Iphone, which pains me beyond belief. Because of OE1 not having a TAR I could not flash the ROM to fix it and I didn't want anything else random or crazy to happen so I waited for something with a TAR. So I flashed OF5 and still got random reboots and freezes that cause my phone to not turn on and I have to remove the battery to get it to power on. So, now I'm on OG5. It runs great but, still random reboots and freezes and won't turn back on . I can deal with a few random reboots but, I can't deal with the freezing and the phone not coming back on. Does anyone know the cause of this issue and are there any fixes? I have searched high and low. I have been flashing for a while so I know the steps there. Just looking for some help from the group. Thanks. Sorry for the long message I just want to try to be clear. Thanks again. I appreciate any help given.
Did u do a factory reset
dvtmg704 said:
Did u do a factory reset
Click to expand...
Click to collapse
Yep. Multiple times. Have odined numerous times. Wiped Cache. All that.
Odin og5
Beginning to sound like something wrong with the phone, if I'm understanding what you have reported the problem is president across wipes and Odin installs of 3 different versions of lollipop.
Did you ever change kernels?
Sent from my Cloudy G2 with Xposed Framework using Tapatalk
kenjesse said:
Beginning to sound like something wrong with the phone, if I'm understanding what you have reported the problem is president across wipes and Odin installs of 3 different versions of lollipop.
Click to expand...
Click to collapse
I really hope not. I hope that it will work it self out. I had a lot of trouble with OG5 when it came to Odin but, it did eventually take. If there is something wrong with the phone itself what could it be? I feel like I have read everything from freezing when changing towers, to damaged partitions, SD card issues, needing a new battery. I just hope it all pans out.
Aloysius01 said:
Did you ever change kernels?
Sent from my Cloudy G2 with Xposed Framework using Tapatalk
Click to expand...
Click to collapse
No I never changed Kernels on any of the ROMS. I would assume because they are stock they should be okay. Especially OG5 .tar file. It should have had everything.

Categories

Resources