I've searched around for anything related to this issue and havent been able to find any information so here I am.
I have a galaxy s3 i747 that is rooted and (until recently) was running an unnoficial version of cm12 with android version 5.1. I used all the correct files for my phone model (I'm not new to rooting or flashing) and flashed perfectly. Booted up great and ran really smooth for about 2 or 3 weeks. One day I was out and I tried to make a call multiple times and the phone wouldn't dial out so I thought "okay reboot and it'll work fine" except when I hit soft reboot this time it started to reboot but never came back on...
In the midst of being out and about I waited to get home to really look at it and, you guessed it, the phone is bricked. Somehow it bricked itself after I tried to reboot it. I don't understand how it could have done that but it did. It might be worth mentioning that I've bricked this phone before and miraculously brought it back to life and its doing the exact same thing as when I bricked it before. Except now when I try the same unbrick method (debrick image on SD card) I get nothing. So, does anyone have any information on this? I thought that maybe the phone updated itself to 4.4 last time I unrooted and that was why but I don't think that happened. If you need more information I'm happy to provide, I just really want to figure out how it got bricked and if there is any way to fix it. Thank you in advance
Related
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.
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.
Hi guys, first post here. I read a lot here but never had an account.
So, a couple weeks ago, I borrowed my Nexus 7 2013 Wifi to my stepdad. And today he comes up to me and says that the tablet wont boot. I have had the same issue but managed to fix it pretty easily. I've tried flashing stock, ROM based on stock, CM 13, CM 12.1, based on CM 12.1, 4.3 stock, ElementalX kernel and factory reset. After every single one of these steps, it boots up, i touch the screen, it freezes and reboots.
I've read something about flashing a .FFU but couldn't find any file for the Nexus. My device is rooted, with TWRP.
Thanks for reading the post till this point and I can't thank you enough for your help
It may be the digitizer, if you touch the screen and it reboots, unplug the digitizer and use a otg mouse to test it and see if the issue persists
So the screen works in TWRP but reboots Android?
You say you flashed the factory image (I assume that's what you mean) and it still does this. Makes me think hardware. Take the back off and clean/reseat the ribbon cable connections it might help and is easy.
If that don't work I'd be about out of ideas. Try flashing some of sfhubs ts firmwares. Id do that last though as it shouldn't need a software fix if it worked before.
A couple of years ago, I'd fruitlessly rooted and installed TWRP, and all I remember for the end of it was that I went back into the stock launcher using the LG User Support Tool.
Earlier today, I thought of doing it again, found what seemed to be a reasonable guide on it (little did about the 10/20/a/b/etc things), followed it.
It turns out I was already rooted. So I installed TWRP, worked pretty well, no problems. Most of what I really wanted was to get rid of the stupid menu button and replace it with the multitasking button for almost every other device. I know CM lets you do that from doing it with previous devices, so I grabbed the most recent one just to test it.
While going through the welcome screen, it wouldn't properly connect to any Wi-Fi networks. Entering the correct password just changed the status to "saved", and it wouldn't connect.
I flashed another ROM, and the same issue persisted.
Could someone please help me to figure out what I did wrong? I'd really appreciate it.
Hey, guys. Hopefully one of you can help me. I've been having problems with my Galaxy tab 3 (Sprint version) all damn day and I figured I'd ask for help before I utterly destroy it.
So, I've been trying to restore the tablet to factory and nothing I do is working. It was rooted in the past but it was all undone before it was given to me a couple of years ago.
Anyway, I've downloaded the stock os from here, sammobile, and another source, but no matter which I use I seem to run into the same issues. (All flashed with odin 3.12)
1.) When resetting the tablet to factory before or after flashing, I almost constantly seem to get the message, "process system isn't responding."
2.) Keyboard seems unresponsive.
3.) Wifi doesn't seem to stay on, doesn't even let me get to where I can scan for signals.
Any help would be highly appreciated.
Sorry!
Can't help just because I don't own a T217S but I own a T210 instead!
They are two different models!
So yeah!
Good luck with what you are doing!
Cheers,
Diamond26
I have the same problem - Process system isn't responding Do you want to close it? I can't reply because the touch screen isn't working now. Anyone know what I should do?
What rom do you have on now?