Develop Bugs

Stock rom problem ... is there a fix?

Hi guys. I am stuck at an impasse here and I know someone here will be able to help.
My wife and I just bought two Samsung Galaxy 2 Epics (refurbished) from the retailer Glyde. I purchased from them because they are partnered with my new carrier, Ting.
My phone activated and ported my number with no issues. Everything works perfectly.
Her phone appeared to activate and then rebooted. It will not go past the Sprint 4G animated opening. I have rebooted, wiped cache, and done factory reset. Still ... 4G logo animation appears and the screen either goes black (appears to shut down) or it just stays on the 4G logo without moving on and then a few minutes later goes black. The phone worked fine before we tried to activate it. It logged in her gmail and connected to wifi.
I am able to get to recovery mode. I was probably going to root and cyanogenmod mine. In your opinion, would this type of action possibly correct the problem with her phone? Is it possible to root and flash the original stock rom in a situation like this? Would that even work seeing that factory reset did no good?
I have contacted Glyde and am waiting - they may or may not replace. If they do replace that is a 2-3 week turn-around. I would rather work some magic here, if possible.
Thoughts and help are appreciated!
Brian

You might have to Odin a stock rom most likely
? Powered By My Moga Pro ?

9/10 Times if you can Odin it, you can fix it. BUT, restoring to stock via Odin will break your flash.
Chances are your flash is already cracked up a little.
A simple cricket nv gen google search combined with Odin, drivers, and DFS Tool. You'll be able to get it back up and running smoothly.
And if your device was on a stock rooted ROM, and you have a custom recovery, then flash a 4.1.2 Custom touchwiz ROM. That way, no programming will be lost.
If you decide to flash an AOSP/AOKP ROM like Cyanogen you could possibly break your flash.
2 cents.

fixed
Would you guys believe it was the battery? It was. I swapped batteries and the other phone started doing the same thing. Battery replaced and problem solved. I guess I panicked, but it sure seemed like a software issue. Thanks for the advice.

[Q] CM11 No Sound/Mic, Force Closes, Etc

Hello fellow XDAers,
I recently went through the flash dance for my Sprint Blue L710 S3 16GB to switch it from some old version of CM 10(.2?) to the latest nightly of CM11. I essentially followed this guide to get my phone up to the latest and greatest and flashed pa_gapps-modular-micro-4.4.4-20141110 to give the the level of GApps I'm comfortable with.
Now I tried to follow the same guide with my wife's Sprint "White" S3 32GB L710. Right off the bat the phone wouldn't boot after the oneclick flash - it got stuck on the loading screen (I waited 30 minutes on the boot screen before giving up... twice). Only after I flashed Philz 6.5.14 recovery was it able to properly boot into the OS (potentially a PIT problem, but all 32GB PIT files seem to be removed from the web). In the stock ROM, phone mic, sound, voice dialer, and Google Search all worked (and I tested this several times during recovery attempts). It noticed it hadn't taken advantage of all 32GB available on the phone, so it decided to expand the partition itself (bonus?). Then I flashed the latest nightly CM11...
Once booted, I cannot get the dialer to behave correctly. I installed the GApps after booting up the ROM once (and tried again on a fresh install by installing it prior to first boot). Immediately after boot, using the Phone app and dialing a number the screen turns to a blank (black) screen. The phone dials fine, but once connected to the number being dialed, there is no sound or mic. When I open the Sound Recorder app, it says "internal application error" and "microphone may be in use". When I try to do "OK, Google", it acts like the microphone isn't able to be accessed. When I open Apollo to listen to anything, DSP Manager force closes. It's as if the hardware can't be accessed by the ROM. SMS, cell network, WiFi, and GPS all work. It seems familiar to this CM thread, but the same steps aren't working for me.
I've flashed a few ROMs based off of AOSP (Slim and AOKP mainly), but none of them seem to allow me to utilize the mic and speaker of the phone. Only ROMs based directly off of sto k ND8 let me "phone out". For instance, stock ND8 works as well as Wicked-X.
I've flashed multiple ways, cleaned/formatted several times, and tried all sorts of tricks to get this to work on my wife's phone. I'd like to believe I've done enough research to feel like coming to the community is my last resort. As a software developer myself, I know there's probably something simple I've missed, but can someone please help me figure out why my "blue" L710 is working but not my wife's "white" 710?
Thank you very much in advance.

Shut off after LG logo

D851 here, When ever i switched from cloudy 2.5 to blisspop 4.0 and after wiping everything i flashed a various of radios bootstacks and etc to make it boot after many failed attempts to boot ( it boots up but after 4 or so seconds after the lg logo the screen turns black and doesnt turn back on until after i pull out the battery) it worked after i flashed the rom WITHOUT a custom kernel so naturally i booted up just fine and thought maybe now i set up everything on my phone and tweaks i should go back and flash a custom kernel i used to use (777 r16) but then it gave me the problem i faced before the black screen after the lg logo no kernal would work. THEN another problem arised similar to the freezing on the black screen randomly during a usage thru my day the phones screen would be unresponsive animations but touch wouldnt work and i know its not my screen cause when i flash back to cloudy it works fine the freezing happens at least every 5 mins. someone halp?

i know this thread is kinds old...
but i have this same issue too... I found if I switch batteries the problem isn't as bad... but, then it becomes bad again. Its weird. Before I swapped batteries I couldn't even login with my google account, after a fresh flash. then after I swapped batteries (gf has same phone) I was able to get through to the end and setup the phone. But, then an hour later it started happening again....
OP, did you find a solution?

warrior420 said:
i know this thread is kinds old...
but i have this same issue too... I found if I switch batteries the problem isn't as bad... but, then it becomes bad again. Its weird. Before I swapped batteries I couldn't even login with my google account, after a fresh flash. then after I swapped batteries (gf has same phone) I was able to get through to the end and setup the phone. But, then an hour later it started happening again....
OP, did you find a solution?
Click to expand...
Click to collapse
i actaully did i think one of the problems was maybe flashing over the same kernel? see what happened was after i gave up flashing the kernel i just flashed without it and to my surprise the build actually came with the kernel pre-installed...shocker and so i had no need to flash over the kernel that i wants because the maker of g3 tmo blisspop already had it in his build and it boots up fine( DISCLAIMER: i cant say this about other roms because the only one i actually tested and wanted was blisspop)

thelgog said:
i actaully did i think one of the problems was maybe flashing over the same kernel? see what happened was after i gave up flashing the kernel i just flashed without it and to my surprise the build actually came with the kernel pre-installed...shocker and so i had no need to flash over the kernel that i wants because the maker of g3 tmo blisspop already had it in his build and it boots up fine( DISCLAIMER: i cant say this about other roms because the only one i actually tested and wanted was blisspop)
Click to expand...
Click to collapse
Okay.
Well, when I was flashing I never flashed a kernel.
Ill be getting a brand new Anker Battery in the mail today. Ill report my findings.
I ended up going to a stock based rom and the issue never happened. So I stuck with it. Ill have to do some testing later and ill let you know how the battery works.

It's not the battery
I downgraded my T-Mo G3 since I couldn't root it with LP on it. Went back to 4.4.2., rooted it, TWRP'd it, and installed the latest CM12 Nightly, Gapps, SU, etc.
As long as the sim card was OUT the installation was great on wifi only, As soon as I put it in it shut off right after, or during boot up. Take the sim out and it works. And yes, the only way to get back into recovery was pulling the battery and doing the key press to recovery. Mystified.
If I find out anything, I'll post it here.

I'd say do a complete return to stock, upgrade via LG Mobile Support tool all the way to 20G, see how it works stock for a while. Then root ( http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197 using the first method) and see what happens.

T800: Can't complete boot when using 7.x.x roms

I had the latest 6.0.1 samsung rom (CPK2) which was giving me problems with freezing. So I am trying to upgrade to an 7.x.x rom, either RR, AIPC, or Lineage. But none of these roms allow the T800 boot to get beyond the initial splash logo screen. I am using latest TWRP, 3.1.1 to wipe and install rom. I am not getting any install errors. Boot loader is confirmed as CPK2.
FYI, I am able to get back to the samsung rom by reflashing it with Odin.
Update 1: In the final attempt of upgrading I installed the official 6.0.1 fw which boots fine unlike the aforementioned alternatives (very strange). However, lock ups and now screen blanking more frequent. This time wiped everything including storage. It looks more like a hardware issue but I wonder if this could be malware even after wiping everything. I will have to take this in for repair but have little hope of solving this problem.

mach281 said:
I had the latest 6.0.1 samsung rom (CPK2) which was giving me problems with freezing. So I am trying to upgrade to an 7.x.x rom, either RR, AIPC, or Lineage.
Update 1: In the final attempt of upgrading I installed the official 6.0.1 fw which boots fine unlike the aforementioned alternatives (very strange). However, lock ups and now screen blanking more frequent. This time wiped everything including storage. It looks more like a hardware issue but I wonder if this could be malware even after wiping everything. I will have to take this in for repair but have little hope of solving this problem.
Click to expand...
Click to collapse
My wife has the US Cellular 10.5 variant (T807R4). It was freezing so frequently it had become almost unusable for anything but watching videos. Rooting and disabling most of the Samsung apps did not fix the problem. I wiped the system with TWRP only to discover that none of the custom ROMs would work on this model. I downloaded and flashed the stock Samsung MM firmware (and it sat on the opening splash screen for at least 15 minutes before it finally booted up) and for the hour I used it after setting it up, I had no problems. I had previously cleared the cache with Titanium Backup and that also seemed to be a temporary fix. My conclusion is that something is happening when the cache fills up that causes the freezes but I'll need more data to say that for sure.

Just an update: I was going to have the hardware looked at so I wiped everything including the storage. But when I took it to the shop and was asked to demonstrate the freezing the tablet wouldn't. So I took it back and it was running OK until a couple weeks later when the same problems reared there heads.
Somehow I managed to get a 7.1.2 installed and the T800 is running great...so far. I'll post back if the freezing starts again.

mach281 said:
Just an update: I was going to have the hardware looked at so I wiped everything including the storage. But when I took it to the shop and was asked to demonstrate the freezing the tablet wouldn't. So I took it back and it was running OK until a couple weeks later when the same problems reared there heads.
Somehow I managed to get a 7.1.2 installed and the T800 is running great...so far. I'll post back if the freezing starts again.
Click to expand...
Click to collapse
Please explain the steps to install 7.1.2 (and which ROM you used) and update on the freezing issue. Most of the freezing issues I have read about seem to be on LTE variants (SM-T807x) so I was about to buy a wifi only (T800) tablet, thinking that would be a solution to the problem. If that's not the case, then I shouldn't waste my money.

The instructions for installing a non-stock ROM are on the dev's host page in Tab s forums. I first tried Resurrection Remix and now am on LineageOS. It was only after I wiped the internal storage area that I was able to get past the 7.x.x boot screens.
I found the stock rom 6.0.1 freezing issue persistent. I believe the problems started for me with XAR H4 and really picked up with K2 (roms supplied by sammobile). The tablet would frequently just freeze while working in an app: the screen and hardware buttons would not respond at all. Never had that problem with Android 5. The only thing I was able to do to unfreeze it was to reboot into download mode then restart the OS from there. I sometimes found that if I left it frozen overnight it would unfreeze itself by morning.

Dead Tab ? Help ! - Free beer

I've searched far and wide, but nothing seems to resolve my issue.
The case:
I have 2 Galaxy Tab S(T800).
One, the oldest, has always run a stock rom + Root
One, I have on LOS 7.1.2.
The oldes one rebooted spontaniously. After searching, i thought it was the battery. On the web people say it often happens with this device. So cracked up de back and checked everything. Thing were looking fine (similar to the working one). Also: in download mode or recovery, it doesn't restarts.
So it has to be software, right? RIGHT ??
I've wiped everything. Factory, Data, Cache. No luck.
Installed the stock rom; no luck. And TWRP then LOS; no luck.
Here is where i loose my mind: Odin gives a pass. The Tab starts perfectly, but upon booting, it quits. On 4.4.2, 5.0.1, 6.0.1. The furthest i've come was the startscreen of LOS, but upon Wifi settings, it reboots again.
Tried to re-partition with the .pit file : no succes either.
HELP wanted. Maybe I can do something with my other, still working tablet.
A free beer for my saviour!

quintinliono said:
I've searched far and wide, but nothing seems to resolve my issue.
The case:
I have 2 Galaxy Tab S(T800).
One, the oldest, has always run a stock rom + Root
One, I have on LOS 7.1.2.
The oldes one rebooted spontaniously. After searching, i thought it was the battery. On the web people say it often happens with this device. So cracked up de back and checked everything. Thing were looking fine (similar to the working one). Also: in download mode or recovery, it doesn't restarts.
So it has to be software, right? RIGHT ??
I've wiped everything. Factory, Data, Cache. No luck.
Installed the stock rom; no luck. And TWRP then LOS; no luck.
Here is where i loose my mind: Odin gives a pass. The Tab starts perfectly, but upon booting, it quits. On 4.4.2, 5.0.1, 6.0.1. The furthest i've come was the startscreen of LOS, but upon Wifi settings, it reboots again.
Tried to re-partition with the .pit file : no succes either.
HELP wanted. Maybe I can do something with my other, still working tablet.
A free beer for my saviour!
Click to expand...
Click to collapse
It looks like a failure in the EMMC .. they were defective in these plates (Toshiba brand) mine has that problem and every 3 days they start restarting and I have to reinstall ..