Develop Bugs

[Q] EC05 Downgrade issue.....

I tried to downgrade from EH17 to EC05 stock through Odin. I used the official tar first and then tried the plus tar. Neither would complete in odin and just hung; no error or fail. My Epic display however did turn blue on 2 occasions. I used the 1.6 and 1.8 odins and neither worked.
I then tried to flash back to the EH17 stock with root and that didn't work until like the 3rd try. Anybody have issues with going back to EC05 and is it worth the effort? I'm just bored and didn't have any issues whatsoever on the GB builds so based off of that....am I missing anything?

Gorguts said:
I tried to downgrade from EH17 to EC05 stock through Odin. I used the official tar first and then tried the plus tar. Neither would complete in odin and just hung; no error or fail. My Epic display however did turn blue on 2 occasions. I used the 1.6 and 1.8 odins and neither worked.
I then tried to flash back to the EH17 stock with root and that didn't work until like the 3rd try. Anybody have issues with going back to EC05 and is it worth the effort? I'm just bored and didn't have any issues whatsoever on the GB builds so based off of that....am I missing anything?
Click to expand...
Click to collapse
Sounds like your cable is going bad. Time for a heavy duty cable. I am using the one from my Palm Pre and works perfect everytime.
I moved to GB and never looked back. EH17 rebooted at least 2 times a day after the 4th day so ended up going back to EG22. The only issues that has is stock browser won't download from dropbox links so got another browser and alarm wouldn't play in silent mode so got Extreme Alarm. Don't know what advantage going back to EC05 would give you. Many go back because of the reboot issue and can't get decent GPS to work. I can still get 5 out 10 locks so will do for now. If you use GPS constantly for directions then EC05 was way superior.

Odin is Version 1.81, have had no issues with since I have been flashing!
Link for Odin:
http://www.multiupload.com/I6GVRDL0VK
Link for ECO5:
Froyo EC05 (do not extract this file)
---------- Post added at 10:20 AM ---------- Previous post was at 10:17 AM ----------
Here is link for EC05 file. It is part way down in Green Square, if you cannot see you have to sign up to download. Become a Member.
http://forums.androidcentral.com/ep...68-how-factory-restore-fix-bricked-phone.html
---------- Post added at 10:23 AM ---------- Previous post was at 10:20 AM ----------
If you still want to downgrade, you might have to go down to DI18 or EB13 then update to EC05.
That is another Way to do it.
Need Help, Repost we can get you links if you cannot find them.

Gorguts said:
I tried to downgrade from EH17 to EC05 stock through Odin. I used the official tar first and then tried the plus tar. Neither would complete in odin and just hung; no error or fail. My Epic display however did turn blue on 2 occasions. I used the 1.6 and 1.8 odins and neither worked.
I then tried to flash back to the EH17 stock with root and that didn't work until like the 3rd try. Anybody have issues with going back to EC05 and is it worth the effort? I'm just bored and didn't have any issues whatsoever on the GB builds so based off of that....am I missing anything?
Click to expand...
Click to collapse
Flashing the sfr zip right over your gb leak (and also a kernel) works just fine. Ive done it on several occasions. Only issue I had was restoring data from a nandroid. Doing so would lock my epic into an upside down landscape view, so I had to rebuild from a clean install and just used some titanium backup restores sparingly.
Sent from a secret underground bunker

You know what's weird I had some issues going from EH17 to EC05 also... but I traced it down(hopefully) to a bad .tar (even though I succesfully odin'd at least 5 times with that same tar with all 5 previously being successful.
Sent from my SPH-D700

If you wanted to do a clean install and you were already on EC05, would a factory reset (settings/Factory reset) be just as good or would you want to reinstall either the EC05 or original stock DI07 file and do OTAs? What's the advantage of one over the other?

rando991 said:
If you wanted to do a clean install and you were already on EC05, would a factory reset (settings/Factory reset) be just as good or would you want to reinstall either the EC05 or original stock DI07 file and do OTAs? What's the advantage of one over the other?
Click to expand...
Click to collapse
You know, there are two different schools of thought on this. Some always go back and use the OTA updates and some never do. I used to go back to EB13 and take the OTA but now I just go straight to what I want. A custom ROM is going to replace everything anyway
Sent from my SPH-D710 using xda premium

Yeah, I have been using the Factory Data reset a lot more. Then restore only apps, no data except what you must have. Phone always seems faster and smoother for awhile.

kennyglass123 said:
Yeah, I have been using the Factory Data reset a lot more. Then restore only apps, no data except what you must have. Phone always seems faster and smoother for awhile.
Click to expand...
Click to collapse
Thanks, another question, Factory Reset won't remove root or CWM will it?

Ive never had a problem going from EH17 or any other GB leak to EC05 but i have occasionally had issues with a bad USB cord or bad tar. Also going straight to whatever build you want might be better that OTA updates. As i recall there can be issues with OTA updates which can cause problems down the road. Of course thats just my personal opinion

Well my cable was bad but that did not help with flashing ROMS. I have been dloading from the device though so I will get fresh dloads from the PC.
On a side note, I used the SW tool and flashed back to EB13 then took the upgrade prompt back too EC05. Been rollin' stock just for kicks and I noticed that the stock ROM runs faster then it use to but the graphics in the GUI get a little stuttery here and there. The scrolling and gallery interface are where it is most noticable.
I can't wait till they start letting employees get the Epic touch.....

Gorguts said:
Well my cable was bad but that did not help with flashing ROMS. I have been dloading from the device though so I will get fresh dloads from the PC.
On a side note, I used the SW tool and flashed back to EB13 then took the upgrade prompt back too EC05. Been rollin' stock just for kicks and I noticed that the stock ROM runs faster then it use to but the graphics in the GUI get a little stuttery here and there. The scrolling and gallery interface are where it is most noticable.
I can't wait till they start letting employees get the Epic touch.....
Click to expand...
Click to collapse
Did you do Data&Dalvik wipe three times prior to going into EC05?

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

Need some newbie help with Cwm Recovery

First and foremost any help will be appreciated.
Just got my sprint Sph-D710 galaxy, used the one click Odin EL29 stock kernel to root, everything is fine phone is rooted, tested rom manager and it asks for permission, but when i go into recovery it stops a quarter of the way and it goes into the triangle, the phone lets me hit the home button and it goes into some type of recovery but all the options it gives are reboot, wipe and partition, install from sdcard shows nothing in the directory??? any ideas on what i did wrong? Thanks again.

ROM manager is pretty dodgy on this phone...
I'd do some more reading... get to where you have a kernel with cwm recovery built in on your phone (sfhubs auto-roots should be able to get you there, from there I personally recommend the rogue kernels if you want to venture a little farther from stock), manually booting into recovery yourself, and maybe even a rom that gives you the option to boot into recovery from the power menu. (Calk's ROM is a VERY good, stable, close to stock ROM).
Final word of warning -- be very skeptical of the CWM touch recovery (and the "hitman" rogue kernel that includes it); I've read more stories of bricked phones related to the touch recovery than anything else I've seen on the e4gt. It's hella cool to have touch interface in recovery; I ran it myself for a while, but... caveat emptor.

Did you flash recovery while you were in ROM Manager?
---------- Post added at 06:31 AM ---------- Previous post was at 06:27 AM ----------
And what ROM/kernel did you put on?

Yes i did flash recovery from rom manager
Stock EL29

Jt_hatch so its safe to just flash a different kernel even though they all advise a nandroid backup?

After using one-click Odin did you use the Auto Root Package to put CWM on? But ya I agree with Hatch Calks got the best stable ROM for our phone. I absolutely love it. Here's his directions:
http://forum.xda-developers.com/showthread.php?t=1332837
Don't forget to use his Format All zip file first.

Crap, i really wanted an Ics themed rom, there's a couple that use the format all zip from Calks but im terrified that once i place them on the sd card or flash with Odin they won't show up in my recovery, ah forget it i guess ill do the rom first and then worry about recovery, thanks a bunch guys
..... actually i need a custom recovery to flash that rom
back in the same hole

cast466 said:
Jt_hatch so its safe to just flash a different kernel even though they all advise a nandroid backup?
Click to expand...
Click to collapse
If you don't have a custom recovery (i.e cwm/rogue) then you aren't going to be able to make a nandroid...
my memory of what I did was sfhub's autoroot, then adding cwm recovery (again via the autoroot), then I went to calk's ROM, then I was off to the races (rogue stock repacked kernel w/ recovery, then gunslinger w/ rogue recovery...) That was before the EL29 OTA but I'm pretty sure sfhub's process is updated since then.

Why do you want just an ICS theme when Calkulin has ICS? lol It's still a little buggy but it's pretty solid in the end and he's only going to keep working on getting it better.
http://forum.xda-developers.com/showthread.php?t=1505979
---------- Post added at 07:15 AM ---------- Previous post was at 07:11 AM ----------
To put recovery on just skip down and follow the directions for Option C
http://forum.xda-developers.com/showthread.php?t=1342728

cast466 said:
Crap, i really wanted an Ics themed rom, there's a couple that use the format all zip from Calks but im terrified that once i place them on the sd card or flash with Odin they won't show up in my recovery, ah forget it i guess ill do the rom first and then worry about recovery, thanks a bunch guys
..... actually i need a custom recovery to flash that rom
back in the same hole
Click to expand...
Click to collapse
I'd give the ICS roms a little bit more time to ripen... only those who thirst for the bleeding edge can really call them daily driver's (and I've got nuthin but respect for them). "Reasonably" stable leaks (far from releases) of ICS for this phone are just a few days old; devs and bad-ass testers are all over them, and the ROMs, kernels, and themes for the rest of us are starting to come out. My (admittedly granny-ish ) advice -- flash up to calk's 2.8.1 EL29 ROM (now 2.9, tho I haven't tried it yet ) and add overstews or shiftr182s (or others) ICS theme and wait until the real ICS roms settle down just a *wee* bit more.

And don't forget to follow the prerequisite checklist on the top of the page beforehand! Don't worry too much about a backup in this case.
---------- Post added at 07:22 AM ---------- Previous post was at 07:20 AM ----------
jt_hatch said:
I'd give the ICS roms a little bit more time to ripen... only those who thirst for the bleeding edge can really call them daily driver's (and I've got nuthin but respect for them). "Reasonably" stable leaks (far from releases) of ICS for this phone are just a few days old; devs and bad-ass testers are all over them, and the ROMs, kernels, and themes for the rest of us are starting to come out. My (admittedly granny-ish ) advice -- flash up to calk's 2.8.1 EL29 ROM (now 2.9, tho I haven't tried it yet ) and add overstews or shiftr182s (or others) ICS theme and wait until the real ICS roms settle down just a *wee* bit more.
Click to expand...
Click to collapse
I would advise this too, lol. ICS is really tempting but the safer and more stable route is the best. Shouldn't be too long of a wait for a more stable ICS anyways. I probably shouldn't of mentioned it.

yep, im trying the autoroot right now but its not recognizing the phone, debugging enabled and storage turned off, re-installing drivers right now to make sure that's not the issue

Try starting all over again with the one-click Odin again and do the autoroot right away.
http://forum.xda-developers.com/showthread.php?t=1505979
One nice thing about using the one-click and autoroot is how fast it is to redo.

MeWarning said:
And don't forget to follow the prerequisite checklist on the top of the page beforehand! Don't worry too much about a backup in this case.
---------- Post added at 07:22 AM ---------- Previous post was at 07:20 AM ----------
I would advise this too, lol. ICS is really tempting but the safer and more stable route is the best. Shouldn't be too long of a wait for a more stable ICS anyways. I probably shouldn't of mentioned it.
Click to expand...
Click to collapse
believe me, I am TWITCHING to flash up to real ICS; I'm just a bit of a nervous nancy. Of course, I have yet to brick a phone... take that for what it is For now, I'm staying pat on GB; I'm willing to bet 2 weeks from now I'll be on ICS and w/o a trip to the sprint store, hat in hand, swearing up and down my phone is dead but most definitely NOT because I rooted (but a couple of weeks behind many ppl who jumped on ICS without a hint of a problem). Me, I'll pass on the walk on THAT much of the wild side; instead I'll wear out the "thanks" button for those brave souls who will...

Also don't worry about losing a ROM on your sdcard, Calk's format all won't touch it. Nothing really will unless you delete it yourself or specifically format the sdcard again. I've actually have 3 different roms on my card right now.

You might want to try this: Flash sfhub's Full EL29 restore here http://forum.xda-developers.com/showthread.php?t=1433101 then add CWM here http://forum.xda-developers.com/showthread.php?t=1342728 use option C and select the option L - EL29+CWM+Rogue. [sfhub's work is a life saver here - many an assumed 'bricked' phone has been saved via his work.] QBKing77 got's some freakign great vids here is how to get it on there http://youtu.be/jZRnH-_XZmM
That will give you a stock rooted EL29 with a very good CWM version (Rogue Kernal). You can use that as a starting point if you're not familiar with what you are doing. As some have said ROM Manager can be dodgy, Better off manually booting to recovery after getting RogueCWM installed. Make a nandroid image after you've got all your apps and settings working. (copy it to your PC too!) Do a LOT of reading to really understand what you are doing and what you really want! Then do some more searching for other ROMs and or themes, read what people say and through all the posts. Remember stock is Odex and most themes are DeOdexed - search and learn what that means if you don't.
I have used many ROMs and most here are great; it really comes down to your taste. You can't go wrong with anything based on Calkulin's work - PhantomHacker, StrongSteve, VeNuM and Team-Nocturnal. I've been using BlazerROM now for a while and absolutely loving the sh$t out of it, it's an ICS theme too. But just a friendly reminder to spend some time here reading and learning. Asking questions that have been answered will not go over well. Some posts have HUNDREDS of pages and they should ALL be read.
I'd also wait to go to a full/real ICS version till these awesome devs had more time to really work it out.

yep I already tried doing the autoroot with Option C and then Option L, but now it doesn't want to install drivers, it installs it while usb is connected but once i turn on debugging it goes away and the autoroot does not pick up the phone, sooooo frustrated right now but i hate giving up
I did everything exact to the video and it just doesn't pick up the phone

So if you turn on debugging and then plug the phone into the computer there isn't any chiming sound saying it's connected nor the phone recognizing it just got plugged into the comp?
And you have tried just powering off the phone and then holding the Volume Up and power button to go into recovery mode right?

cast466 said:
First and foremost any help will be appreciated.
Just got my sprint Sph-D710 galaxy, used the one click Odin EL29 stock kernel to root, everything is fine phone is rooted, tested rom manager and it asks for permission, but when i go into recovery it stops a quarter of the way and it goes into the triangle, the phone lets me hit the home button and it goes into some type of recovery but all the options it gives are reboot, wipe and partition, install from sdcard shows nothing in the directory??? any ideas on what i did wrong? Thanks again.
Click to expand...
Click to collapse
The recovery you are describing appears to be stock.
The triangle sounds like it is trying to install some leftover OTA.
---------- Post added at 11:21 AM ---------- Previous post was at 11:14 AM ----------
cast466 said:
yep I already tried doing the autoroot with Option C and then Option L, but now it doesn't want to install drivers, it installs it while usb is connected but once i turn on debugging it goes away and the autoroot does not pick up the phone, sooooo frustrated right now but i hate giving up
I did everything exact to the video and it just doesn't pick up the phone
Click to expand...
Click to collapse
If it is stuck waiting for phone to be connected, that means adb isn't able to see your phone.
Have you tried going over FAQ #E3 for troubleshooting:
http://forum.xda-developers.com/showpost.php?p=19443755&postcount=142

Thanks for helping sfhub, I'm starting to run out of ideas for him!

Bootloop after overheating

I was in the car running Waze (GPS), full screen brightness in the sun on the dash. Phone rebooted, then stuck in an infinite bootloop. I was running the newest 4.4.3 PacMan. Sometimes it would reboot after the Samsung Logo, sometimes it would just end up hanging on loading on PacMan.
I can get into Recovery. I tried wiping dalvik, cache, data, didn't work. I tried reflashing the rom, didn't work. Tried restoring a backup from February (Pac 4.2), didn't work. Tried installing OmniRom, DIDN'T work! What the hell is going on?
This is an emergency as I'm currently away and need to use my phone. Fortunately I brought my laptop with me.

Donteventrii said:
I was in the car running Waze (GPS), full screen brightness in the sun on the dash. Phone rebooted, then stuck in an infinite bootloop. I was running the newest 4.4.3 PacMan. Sometimes it would reboot after the Samsung Logo, sometimes it would just end up hanging on loading on PacMan.
I can get into Recovery. I tried wiping dalvik, cache, data, didn't work. I tried reflashing the rom, didn't work. Tried restoring a backup from February (Pac 4.2), didn't work. Tried installing OmniRom, DIDN'T work! What the hell is going on?
This is an emergency as I'm currently away and need to use my phone. Fortunately I brought my laptop with me.
Click to expand...
Click to collapse
What recovery are you running?
---------- Post added at 10:47 PM ---------- Previous post was at 10:47 PM ----------
What recovery are you using

terpin32 said:
What recovery are you running?
Click to expand...
Click to collapse
I was running TWRP 2.6.1.
I ended up Odining to stock, but now realize it might not have been the phone. I use two batteries and a separate charging system. When I Odined, I switched batteries to my full one (not the one that was heated up in the car). This morning the battery I had Odined with was getting low so I switched it out with the one that was overheated. Bootloops on stock! Is this battery fried or can fix it somehow? (I remember with my old SGS there was a "wipe battery stats" in CWM Recovery, I haven't looked into that for TWRP.

Donteventrii said:
I was running TWRP 2.6.1.
I ended up Odining to stock, but now realize it might not have been the phone. I use two batteries and a separate charging system. When I Odined, I switched batteries to my full one (not the one that was heated up in the car). This morning the battery I had Odined with was getting low so I switched it out with the one that was overheated. Bootloops on stock! Is this battery fried or can fix it somehow? (I remember with my old SGS there was a "wipe battery stats" in CWM Recovery, I haven't looked into that for TWRP.
Click to expand...
Click to collapse
Well if the phone turns on then it works but I like using philz recovery some times twrp is weird like but I would give philz a try and just wipe everything but the modem and external sd in I think its mounts and storage and reboot the recovery and when it says something about applying root hit no and then when it boots flash the rom again
---------- Post added at 09:41 AM ---------- Previous post was at 09:41 AM ----------
Well if the phone turns on then it works but I like using philz recovery some times twrp is weird like but I would give philz a try and just wipe everything but the modem and external sd in I think its mounts and storage and reboot the recovery and when it says something about applying root hit no and then when it boots flash the rom again

But it works fine when I use my spare battery (the one that didn't get overheated).
At the point I think that the over-heated battery is just shot unless it can be fixed somehow. Google isn't helping.

I guess it could make the phone not have enough power but I would just toss it out b4 anything happens to the phone have you ever herd of the zero lemon battery for the note 2?

terpin32 said:
I guess it could make the phone not have enough power but I would just toss it out b4 anything happens to the phone have you ever herd of the zero lemon battery for the note 2?
Click to expand...
Click to collapse
No I haven't. This was an OEM battery purchased July 2013. I'm annoyed Samsung doesn't stand by their batteries for longer than 6 months.

Donteventrii said:
No I haven't. This was an OEM battery purchased July 2013. I'm annoyed Samsung doesn't stand by their batteries for longer than 6 months.
Click to expand...
Click to collapse
Ive have this same battery for 2 years almost
http://www.amazon.com/gp/aw/s/ref=is_s_ss_sc_1_15?k=zerolemon+note+2&sprefix=zero+lemon+note
---------- Post added at 10:06 AM ---------- Previous post was at 10:06 AM ----------
Here

[Q] Lost all sound, system is unstable

I had an unfortunate defect in my previous phone where it no longer saw the SIM card, so I had to have it exchanged through T-Mobile. The refurb I got in exchange had the NH7 complete stock ROM installed already, so I was stuck with Knox.
I flashed the 02/23 release of Danvdh's GPE ROM, but lost sound. After reflashing it several times, I thought maybe it was a compatibility issue. I decided if I was going to be stuck with a TW stock ROM for now and already had Knox, might as well use the latest, so I Odined the stock NK2 ROM posted by ShinySide. Sound issue persisted, and on further inspection I found the bootloader had failed to update with the rest of the ROM, so thought the mismatch with the modem was a problem.
After fighting to get it to update, I finally succeeded and have a complete match of bootloader, modem, and ROM for the same (NK2) release, but the sound problem persists. In addition to the sound problem, and probably related to it, various apps are unstable and sometimes FC for no apparent reason, and the camera fails to load at all.
Anyone have any insight to this one?

Don't know why everyone is so anal about Knox, if your warranty is up it doesn't make a difference.
By flashing lollipop you got all the bugs that Samsung and T-mobile are weeding out before releasing the update, try clearing data in recovery or in apps not working.
Reflashing twice with a battery pull in between without rebooting after first flash may help.
Uninstalling and reinstalling apps f/c'ing may work.
Pp.
---------- Post added at 09:51 AM ---------- Previous post was at 09:49 AM ----------
I run stock / debloated with all Knox removed with no issues what so ever, and everything works the way it's supposed to.
Pp.

My warranty wasn't up yet, so I had hopes for avoiding it. The apps with problems are mostly the ones that use sound and I still have the problem on a fresh install of the mentioned stock KK ROM.
As for back-to-back flashes, I forgot to mention I've been using that method after reading about it so often, just to be sure.

What recovery are you using?
CWM
Twerp
Philz
Pp.

TWRP.
The stock ROM I'm Odining overwrites that with stock.

Did you do a full factory reset?
It's needed in your case with the lollipop rom going back to kitkat.
Don't see it mentioned in your op.
Pp.

I did, and my apologies for leaving out so many vital bits of info. Having read so many threads, I really ought to know better.

Wow, this is getting complicated.
I'm running out of ideas, you may have to start going through lollipop threads and maybe you'll come across something that may give you a lead on how to proceed.
It may come down to picking a dev's brain on what to try next.
Sorry about my long response times, snow day today for nyc schools and been busy all day with my daughter, she's disabled with cerebral palsy and a handful.
Check the 5.0 threads maybe someone has been through this before you, and you'll be able to find an answer. I'll try Google and let you know.
Pp.
---------- Post added at 10:21 PM ---------- Previous post was at 09:54 PM ----------
Did you do a factory reset right after flashing stock kitkat?
You do this before first boot up so that conflict from previous rom doesn't stick to new rom flash.
Reset will delete all data pertaining to apps, if you had any lollipop incompatible apps before 5.0 and thy get borked, they will mess with new rom install.
Try a reflash of kitkat and right after flashing completion pull battery, startup in recovery and do the factory data wipe (reset) . Now let phone boot up and see.
Pp.

I did in fact do just that as one of my most recent attempts at this, and I'll probably do it again tonight for giggles. Maybe I'll get lucky.
I appreciate you taking the time to help out. I spent 2 days searching through any thread I could find regarding no sound issues before posting.
If I can make contact with one of the more knowledgeable devs here and get this resolved, I'll most certainly be posting the solution here.
-EDIT-
Got it working!
I recalled this post in which someone mentioned having removed the back speaker and reattached it so solve a no sound issue on their S 4. I had thought to try that at the time, but didn't have a tiny phillips screwdriver handy. When I got one and tried it, I was quite shocked as I hadn't had much hope for it to work for me.
Thanks again for your help, Pancho. You rock.