I have the ATT sgh-i747. I was using it as normal. The battery was low and i could not charge it before it got to 0%. After it died, I connected the charger and started it back up. When the screen came on, the "no sim-emergency calls only" message was there and the touch screen did not work. Also, the time and date were off. it said 3:59 September 15th. I tried the normal reset (take battery out, replace, turn back on) several times and still the same thing. I had just replaced the sim reader a month ago, as well as the rear camera and speaker, and everything was working as normal. I opened the phone up to make sure all connections were set. Still the same message. I did a factory reset and after I turned it on, still, the touchscreen does not work and it says no sim. I find it odd that both these things would stop working at the exact same time. Also the phone is long past its warranty. Any ideas on what this could be?
Anyone?
Have you tried flashing another ROM?
I don't know how to do that, if you could point me in the right direction I'd appreciate it.
Before anyone can give you advice, we need as many details as you are able to provide.
Was your phone running a stock ATT ROM? What ROM was it running? Are you able to boot into download mode?
Stock Rom, phone is not rooted and I can boot to download
What stock ROM? It's important that anything you flash does not try to downgrade the bootloader if you were on stock 4.3 or 4.4.
I'm not 100% sure. I want to say 4.3. There was a software update for the phone that automatically downloaded about a week ago but im not sure if that is related.
Since you received an update a week ago, you may be on KK.
I suggest flashing Philz Touch recovery via Odin and see if you can boot into recovery. In recovery you can see if the digitizer responds.
Flash the latest tar version from here in Odin: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Related
So I've had this problem, and I fought with it for one night until I got it working. I'm sharing my experience here in case others have this issue, and I invite people that have encountered this issue to criticize the way I fixed my problems so that we can get the minimum bricked to working procedure and identify issues in loading custom roms.
The problem is that the phone after flashing a custom rom will work, but you get 'no carrier' meaning that the radio on the device isn't connecting to your carrier. In my case, 'Sprint'. I don't know why this happens, but no matter what I did, I couldn't get it to connect.
What I had to do was go back to stock. The MD4 stock didn't work for me, it would display the samsung note 2 branding screen, then the screen would fuzz out like an old tv that lost the vsync signal, and then the red light would blink blink blink. I bricked my pho.ne
The good news is, I didn't completely brick it. What you have to do is ODIN the phone. The problem was, it would never go into odin mode, it would always crash before it got there. What I had to do was take the battery out and power it ONLY via USB. Then it would go into odin, and I was able to flash the LJC firmware. It seems that if you want to replace the radio, you have to flash an entire rom to do it. Those downloads are a gig!
So even after doing this, it wouldn't quite work right. If you still have issues, you may have to ODIN a new BOOT image. Once you do that, then when it boots you'll get the standard sprint logo and animation / sound, but it will still hang. What you have to do then is load a custom recovery (odin), boot into that recovery, and format system twice then cache twice. The recovery that worked best for me was ClockworkMod Recovery v6.0.4.3.
That seemed to reset the radio/carrier and then I could load the original LJC rom & radio. I verified that I could access everything. Then, I did CF Auto-Root, and loaded a new custom rom. All was working afer that!
Where to start...
First, as a disclaimer, I may use language or terms that sound noobish. I have rooted and run custom ROMs on several devices in the past, however generally when I get a ROM I like I stick with it, so I'm not constantly tinkering. I've done my best to search and find solutions so please go easy on me.
17 days ago I was running stock 4.3 on my SGNII when the battery died. Upon charging I found I was stuck in bootloop and had a bad /efs mount. I searched and searched and spent around 15 hours trying this and that but to no avail. I finally threw my hands in the air and got ahold of Josh at mobiletechvideos and he was able to fix the efs mount issue. However, he left me in factory mode which required me to root to get out of, and once I did this I was unable to activate data on my carrier (Ting). I was so happy to have my phone "back" though that I used it like this for 4 or 5 days. I could get on wifi and I could call and send text messages. I had been off the grid so this felt like something I'd fix fully later.
Well I kept reading and found "fix" after "fix", flashed this and that and still no dice. FINALLY, last night, I found this thread: http://forum.xda-developers.com/show....php?t=2086769 which helped immensely. I was able to get TWRP flashed by unchecking the "auto-reboot" option in Odin and pulling the battery after the update took, and via TWRP I was able to install the ROM. I booted up, the device activated, I was running 4.1.2, I made and received some calls, the birds were chirping, the air was sweet...
I had struggled for so long and I had finally achieved success! Then, for seemingly no reason at all, I accepted an OTA update which bricked my Note2. Devastation.
The current state of things...
* Cannot get past the initial "Samsung Galaxy Note 2" screen
* Cannot boot into recovery
* I CAN get into dl mode,
* but, I CANNOT successfully flash anything. TWRP will flash like it took, but upon reboot I'm not able to boot into it. I'm also able to flash a ROM but it fails when it gets to sbin, and upon rebooting I'm greeted by the screen "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
When I try to use Kies it doesn't find the device. I've installed all of the most recent drivers and I'm running Kies as administrator. I select Tools > Emergency Firmware Recovery, THEN connect my device as instructed.
I'm at the apex of frustration. I beg thee to help!!
I have roughly the same situation. Was rooted and on an MK4 rom, battery ran down super fast yesterday and when charged, only get splash screen and slowly flashing blue light. I can get into Philz recovery but no matter what I try, no dice. Also can get into DL mode, but haven't been able to get anywhere. What the heck happened?
Well i bought another phone because of this problem of unknown baseband and 0 for everything in settings which didnt allow me to connect to sprint. Now when that happen it put me in safe mode . and i couldn't find a fix for months i ended up getting a lg g2 and let my note 2 collect dust. Well I'm using my note 2 and its up in running . my partition was messed up . if you have this issue which it sound like i can help. My phone was running fine then rebooted on its own and rebooted on safe mode with no signal
Sent from my SGH-M919 using XDA Premium 4 mobile app
hi,
so i just got my s6 edge for sprint shipped to me (it wasn't activated to any service when i got it). here is the order of events i took:
1) tried to activate my service, but there was a delay in porting the #
2) while waiting for them to port it, i rooted it, installed twrp and a rom (this was when it was on 5.0.2)
3) they called and said they were ready to port, but the new rom didn't have the activation software in it. so i stalled them and said i would call back. i then reverted back to stock using odin.
4) got the number ported and was fine using the phone at that point.
5) this is where the day turned bad...... i didn't realize that coincidentally today, a new firmware was released to 5.1.1 and the phone auto-updated to it while i wasn't looking
6) i went to go re-root it using the same 5.02 root and now my phone is stuck. it's sitting on the "Samsung Galaxy S6 Edge, Powered by Android" screen and in the top left in red it says "RECOVERY IS NOT SEANDROID ENFORCING"
7) i tried to restore it back to the stock using odin, but it errored in the download mode (i don't remember the error off hand)
i can get into download mode, and that's about it. i had to let the phone's battery die on it's own to turn it off (this phone gets super hot, btw)
so i guess what i need to know is how to restore back to factory default again, now that it thinks it's on 5.1.1. is there any hope?
I'm in the same boat as you, I think the only hope is to wait until the firmware is available to download and install it via Odin. Let me know if you've had any luck getting it up and running again. I had to switch back to my old phone for the time being.
bbacon said:
I'm in the same boat as you, I think the only hope is to wait until the firmware is available to download and install it via Odin. Let me know if you've had any luck getting it up and running again. I had to switch back to my old phone for the time being.
Click to expand...
Click to collapse
check this post, download the tar and flash it in odin. it worked for my phone!
http://forum.xda-developers.com/showpost.php?p=61650724&postcount=142
it got me into a recovery image that worked and i was able to factory reset in there. my phone is booting properly now. (after it reboots when done, it took a bit on the first title screen to do anything, just be patient)
Thanks man, that worked great. Although I found out in the process of trying to fix it the past few days, I must have flashed a non-compatible kernel because once it boots the touch screen is unresponsive. I guess I'll have to wait until the firmware download is available after all. Thanks again for the help though
okay so i have a soft-bricked tab here, its the sm-t310.
it was received in a plastic bag, taken apart. so i put it back together and it wont turn on or charge; so i order a new battery and charge port. Viola! it turns on BUT it freezes on the Samsung screen. so i try to get to a recovery screen. Alas, it has team win custom recovery v2.6.0.0 and no OS installed. it also freezes on the charge screen. (ya know the battery icon and a frozen rotating semicircle on top of it) it also will not charge at all. not sure if its because of the recovery that's making it freeze or the motherboard or what? i cant install anything with a battery at 1%. i also have no sd cards to help an installation either.
I heard that this particular recovery version had a charging issue/bug as well?
Im fairly adept with computers, but this thing is proving to be a pain in my Butt! I've tried numerous methods from odin pushing a flash to it (that failed). i borrowed an sd card and tried manually updating it with the stock firmware 4.2.2 but it was a tar5 or some such thing and the recovery couldn't load it. i also tried a custom lite rom but it failed the flash because it was the wrong version, which btw it wasnt.
So... What Can i do to get it to charge? and what do i need to get this thing back to working order?
UPDATE! i got it working.
turns out whom ever owned it last installed the wrong twrp. so i reinstalled the newest version for my tab. then flashed the rom i had and Viola! it works great! turns out the battery IS charging just not showing it. trying to get GApps installed as i type! thanks xda people for all the files and posts that helped me along the way!
Alright this is my first post here so I hope you'll bare with me. I'll give you the anecdotal account first and get any details that are needed when I get home from work, so here goes...
Friend of mine got a refurbished S3. Later we find she needs a newer firmware than the stock 4.3 to use pokemon go so I tell her I'll put cm13 on it and she'll be at 6.0 and it should run fine. In the process of trying to put cm13 on I find that the recovery error I'm getting is telling me that it's actually a sprint S3 even though the model number in the software and under the battery says sgh-t999. So I try the sprint cm13 file and it boots and seems to work fine. Weeks later we discover she hasn't been receiving calls. No notification, nothing. Everything else works, she has Internet, she can call out, she even gets voice-mail notifications if people leave them. This is no good, so I try to roll her back to stock (sgh-t999 stock) after trying some other simple fixes that didn't work. (just soft fixes not flashing anything weird) But next thing I know the phone is soft bricked and all the tuts I see just say to push this .tar or that .img and pass or fail the phone never boots and I haven't had any kind of recovery menu since the first flash. The counter is at 17 or some-****ing-thing. At this point I've tried both sprint and t-mobile roms just out of desperation but nothing has gotten me out of the softbrick. The download menu also identifies it as a sgh-t999.
I hope someone here can help. Best as I can remember that's everything besides any logs you guys want to see.
Download (i.e. Odin) mode is where the phone's "real" model # is located. Since it is a identified as an sgh-t999, you should be flashing TWRP and CM13 for the d2tmo: https://twrp.me/devices/samsunggalaxys3tmobile.html
Maybe try again with a fresh flash of TWRP and CM13?
Flashed TWRP and it passed on Odin but I can't get into the recovery using the usual method.
Reflash TWRP but uncheck everything in Odin except f reset time. After completing the TWRP flash, remove the USB cable from the phone, remove battery, replace battery, press home, volume up, and power to power up the phone. Once the phone starts to power up, release the power button but hold down home and volumue up.
No idea why it worked that time but I've got TWRP up again. Going to boot into CM13 if I can and see if it's receiving calls yet.
All working, thanks guy!