So after initially getting the S4, I couldn't wait for a ROM to come out so I didn't have to run TouchWhiz. Needless to say when I seen some ROMs starting to appear, I flashed some with no hesitation.
I flashed the following before encountering any problems -
garwynn's - AOSPA Beta followed by CM 10.1 (POC)
Everything on those ROMs was pretty much perfect, no errors or glitches in anything I used the phone for, so after a day or two I was feeling pretty confident about the current releases thus far. I seen the thread for SlimBean this morning and flashed it with no problems
The ROM loaded up just fine, instantly obtained 4g signal with full bars and everything seemed pretty much good to go. About a half hour into it my signal indicator went to "Roaming". I figured it was just a glitch in the ROM not properly displaying the signal indicator as it should. My data was working fine, so I just assumed all was well. I switched the indicator to the text / dB style which showed a pretty constant "-72 / 80" It didn't come to me that I could not call or text for about two hours...
Needless to say, I tried to put the phone on "CMDA only" "EVDO only" and pretty much any combination besides "GSM only" in the Phone Information section after dialing *#*#4636#*#*. I tried turning the radio off an on. Still nothing would work....so I dirty flashed SlimBean over itself. Didn't work, flashed the following ROM-
Beans' Stock ROM (Odexed)
Loaded up fine, had 4g but still couldn't call. I tried flashing the CM 10.1 ROM as well with the same problem. When I got home I put the phone in download mode and flashed the stock image (link) hoping that it would solve my problem. It didn't.
I'm currently sitting here as stock as I'm aware I can be with no working voice / text on my radio. Data works fine, as does everything else. My IMEI matches what is on the label under the battery. Everything looks normal to me except the IMEISV which currently reads "00".
I'm not too worried about this as of this moment as I know the SIM card is good, it works in my SIII and my other phones. I'm just not sure if this is a fixable problem or not.
Thanks,
-clay
Odin back to stock and go get your phone exchanged.
Solution
I'm glad to report that I did in fact manage to fix this problem. Hopefully this can help others.
*DISCLAIMER* - I am not claiming this is 100% full proof, nor am I able to explain why this worked.
However it may be useful to others....
After doing a bit of research I came to the conclusion that my EFS wasn't completely corrupt because I still had my IMEI intact on the phone. The best I could come up with was that my files / data for SIM card provisioning weren't correct / corrupt. Thus I tried the following:
1) Odin stock image.
2) Odin MD2 kernel and root via Motochopper.
3) Install Root Explorer and Terminal.
4) Copied my EFS folder and placed it elsewhere. (Never used this copy but could be useful somehow?)
5) Renamed EFS to something random. *Probably very dumb to do* Deemed necessary after some reading.
6) Phone rebooted into Factory Mode.
7) Executed the following command
Code:
su
echo -n ON >/eds/FactoryApp/factory mode
8) Rebooted Phone.
9) Odin Stock Image.
10) Odin MD2 kernel and root via Motochopper.
11) Flashed TWRP.
12) Boot recovery and run Fix Permissions.
13) Rebooted, powered down phone, pulled battery and SIM for about 10 minutes and then reinstalled SIM, powered on.
14) Odin stock MDK kernel back to phone.
To my surprise in a minute or so I locked on to a signal and could make calls / text. 4g was working as it was previously. I'm not sure if all steps are necessary but after a few attempts at various things, this method proved to work.
I'm back on SlimBean and everything seems to be working smoothly.
Glad you got it back up and running! Nice to see a community member work around and solve the issue. Many times a device ends up back to the carrier when all thats needed is a little trial and error with various fixes. Sure the carrier will replace the device, but this is why some carriers lock them down e.g. verizon/att.
nice job :good:
Glad you figured it out, but as an FYI, my IMEISV reads 00 and I have no issues, so this seems normal.
Hi, I'm having a curious problem with my S3 and I've been unable to solve it. I watched the "noob" video and tried searching these forums as well as a google search with various combinations of the wording for my problem. Nothing matching my issue turned up, I hope I didn't miss anything.
I recently bought a S3 second hand (yes, i know, i should have known better). It was rooted and running some kind of custom ROM when I first turned it on, but I was willing to deal with it until I double checked the procedure for getting it back to stock and starting again myself (nothing against the original rooting and flashing, just like to know exactly what I'm running).
When I purchased the phone I obviously checked that all of the main things worked - calling, texts, mobile data, wi-fi etc. I get home and connect to my home wi-fi and start checking things out and setting stuff up. The phone randomly rebooted. I carry on after the reboot and about 10 mins later, another restart.
To cut a long story short, there is something wrong with the wi-fi. If I turn off wi-fi in the settings menu and reboot, everything works great. No crashes, no reboots. If however I enable the wi-fi about 50% of the time it will crash while wi-fi is activating. The other 50% of the time, it will crash as it goes into the screen lock (either via timeout or pressing the button).
I've re-flashed to it's stock version of Android (using the 'Samsung GS3 Toolkit and Odin), same problem. Anyone got any ideas?
Thanks in advance
You can try updating the modem and RIL to the right version for your country, search in general forum. If it still reboots then try with another wifi source - I've seen some routers cause problems on client machines.
If you do a factory reset when you flash the modem, plus you have the latest stock ROM on board, then any remaining problems are probably hardware.
Test it fully after the factory reset, before you add any apps etc.
boomboomer said:
You can try updating the modem and RIL to the right version for your country, search in general forum. If it still reboots then try with another wifi source - I've seen some routers cause problems on client machines.
If you do a factory reset when you flash the modem, plus you have the latest stock ROM on board, then any remaining problems are probably hardware.
Test it fully after the factory reset, before you add any apps etc.
Click to expand...
Click to collapse
After much experimentation and flashing of various files to my phone I have further narrowed the problem. I've still not solved it, but getting closer I feel.
After a clean ROM flash it works like a charm regardless of how much i use the wifi etc. It's only after the first reboot that the trouble starts. It will begin randomly restarting. If I perform a factory reset from recovery mode, it works again, but starts resetting again after a reboot.
Any ideas?
I have infocus epic 1 device and its standby is terrible from the day of purchase(>2.5%/*h).It stays awake 100% of time.I rooted the phone on sole purpose of fixing it.after doing some research now i am sure it's something related to radio layer interface because when i don't install sim card mobile goes deep sleep 98% of time.better battrey stat show's kernel wakelock ttyC0 as main culprit.i think com.android.phone is the reason behind it.i have found one tedious solution to fix it.first i ve to freeze the package com.android.phone pluck the sim out restart the phone put sim back in and defreeze the package.but rebooting the phone again starts the problem.but i want to completely fix it without need to do so.also it would be hepful if i can some how block mandatory restart after inserting sim in the sim slot so i dont have to freeze and defreeze the package com.android.phone
I think you should try a (few) different SIM card(s). It may be the card itself that causes problems.
Then, I’d reboot the phone, after entering the PIN, wait a minute of so for everything to initialize, and then check dmesg (aka the kernel/driver log), or even logcat for that time period.
Also, if you can, try making a complete backup image of your system (all partitions), and
1. try a factory reset of your phone (ideally flashing the original system on there after the factory reset), or even
2. flash an older Android (6? 4.4?),
and see if the problem exists there too.
You should be able to find the newest/best case where it works, vs the oldest/worst case where it doesn't, and then look at what’s different between the two (with some graphical diff tool, using dmesg and logcat output among other things, for example) , especially with regard to your problem, to find the answer.
Hi everybody, I decided to post my problem here, after not being able to find a solution on my own.
I'm experiencing the same issue as mentioned in some other threads: [1] [2] I have the drain since I wiped my EFS partition, because a corrupted twrp backup (it was a bug in a certain version that it made faulty backups) messed it up, and it wouldn't boot. So I found a solution to wipe it, but I have lost my IMEI. I didn't really notice it, because the phone was working fine, but recently I noticed that it shows "0" for both of my IMEI numbers. Also, I switched to oreo immediately after wiping the partition, initially I made the full backup just in case I had to go back to nougat. So first I thought that the problem is caused by the early oreo builds. But I have tried several nougat builds too, even miui, but I got the same issue, standby battery drain, and no IMEI, even after installing the fastboot rom of miui. Yesterday I thought that they may have something to do with each other, so I decided to try to restore the EFS, and the IMEI. I've followed some guides here on xda and also on miui forums, and after restoring the QCN file for my model (global version) and writing IMEI with the Qualcomm imei writer tool, I succeeded . I got my IMEIs back, and I hoped that it would solve the battery drain too. But today after letting it in idle, the battery drain is the same. I would rule out any ROM specific issue, because it happens on miui too, and every rom I have tried. Also I don't think it's connected to any apps, because I have tested roms also without restoring anything, I haven't even flashed gapps, and the idle battery drain was still there. I only managed to "solve" it one way: changing preferred network type to any of the options, without LTE. If the phone is connected to HSPA+/3G, (without mobile data, just the service) I can get it to last 2 days, and it's the same if I have it in airplane mode, the drain is gone. That's why I also think that it's not a hardware issue. I could use my phone without LTE, we don't even have VoLTE here, so it's not mandatory, but I would like to solve this problem If I have already spent that many hours figuring out what the solution could be. It's also important to mention that even if connected to LTE (phone service) kernel adiutor shows that when the phone is in idle, the CPU goes to deep sleep and not awake. Now I'm reaching out to you guys, could you please help me? Thank you in advance!
ardrift said:
Hi everybody, I decided to post my problem here, after not being able to find a solution on my own.
I'm experiencing the same issue as mentioned in some other threads: [1] [2] I have the drain since I wiped my EFS partition, because a corrupted twrp backup (it was a bug in a certain version that it made faulty backups) messed it up, and it wouldn't boot. So I found a solution to wipe it, but I have lost my IMEI. I didn't really notice it, because the phone was working fine, but recently I noticed that it shows "0" for both of my IMEI numbers. Also, I switched to oreo immediately after wiping the partition, initially I made the full backup just in case I had to go back to nougat. So first I thought that the problem is caused by the early oreo builds. But I have tried several nougat builds too, even miui, but I got the same issue, standby battery drain, and no IMEI, even after installing the fastboot rom of miui. Yesterday I thought that they may have something to do with each other, so I decided to try to restore the EFS, and the IMEI. I've followed some guides here on xda and also on miui forums, and after restoring the QCN file for my model (global version) and writing IMEI with the Qualcomm imei writer tool, I succeeded . I got my IMEIs back, and I hoped that it would solve the battery drain too. But today after letting it in idle, the battery drain is the same. I would rule out any ROM specific issue, because it happens on miui too, and every rom I have tried. Also I don't think it's connected to any apps, because I have tested roms also without restoring anything, I haven't even flashed gapps, and the idle battery drain was still there. I only managed to "solve" it one way: changing preferred network type to any of the options, without LTE. If the phone is connected to HSPA+/3G, (without mobile data, just the service) I can get it to last 2 days, and it's the same if I have it in airplane mode, the drain is gone. That's why I also think that it's not a hardware issue. I could use my phone without LTE, we don't even have VoLTE here, so it's not mandatory, but I would like to solve this problem If I have already spent that many hours figuring out what the solution could be. It's also important to mention that even if connected to LTE (phone service) kernel adiutor shows that when the phone is in idle, the CPU goes to deep sleep and not awake. Now I'm reaching out to you guys, could you please help me? Thank you in advance!
Click to expand...
Click to collapse
Many times, this problem is band specific. Since every country uses a different megahertz band for their LTE service, but in this case you said there wasnt any fault before. Have you tried flashing any custom kernel like francokernel?
Yes I have tried other kernels too and it didn't solve the problem, but I didn't try francokernel on the official rr oreo build yet, I'll give it a try, thanks
I also have to add that whenever I'm connected to LTE (service, not data), the signal is fluctuating heavily. If I switch to maximum HSPA+ preferred network type, the signal becomes stable again. Maybe I should try different firmware zips, idk ?
Okay, so I tried flashing the latest francokernel (r4), have been using it for 2 days, and I don't really notice any big difference in terms of battery life. I also switched the "preferred network type" option to include LTE too, but the battery started to drain immediately. Yesterday I also found a guide (on 4PDA, as I'm trying to find a solution really hard) about flashing a QCN with the qpst tool, to unlock some LTE bands and then enable carrier aggravation(?). I just completed the whole process hoping that it would solve my issue too, but after I enabled LTE again, the battery drain came back... I can't really come up with another thing now, but I'll keep searching for it.
Could anyone please share a full (without apps and data of course) backup from TWRP to see if I can restore my EFS partition successfully? Maybe it would solve my problem as I think it is related to some sorts of modem things, and as I have explained it may be a low-level problem.
Thank you in advance!
I took the time to save and search through the logs of my device, I'll attach it to the reply. This is a log taken from the phone as it was in "safe mode", just to exclude all the unnecessary logs from third-party apps, as I experienced that they don't influence the draining of my battery. As I observed, interesting parts are around line 2365 and 4494 from point of view of the phone service, SIM card, and things like that. Also, it's another interesting thing that until the 184th line, the date is way back in november, and as I looked back, it is 4 days before I wiped my EFS partition, because the phone didn't boot then. I don't know if it is connected to my issue somehow, I just noticed it. After that, until the 1886th line, the date is 2-24, when I flashed installed my current rom, and it may be a bug with the rom itself that the date switches back to the initial installation's time, it may not have anything in connection with my main issue. I would be very thankful if someone else could get something valuable out of it. Also, an EFS backup from TWRP may solve my issue... Thank you in advance!
Hey,
Any solution for this issue ? My case is the same with Lenovo z6 pro.
After accidentally erasing my imei, and flashing it back I have idle drain.
Thx
Hope some one will replay to this 'old' thread.
ardrift said:
Hi everybody, I decided to post my problem here, after not being able to find a solution on my own.
I'm experiencing the same issue as mentioned in some other threads: [1] [2] I have the drain since I wiped my EFS partition, because a corrupted twrp backup (it was a bug in a certain version that it made faulty backups) messed it up, and it wouldn't boot. So I found a solution to wipe it, but I have lost my IMEI. I didn't really notice it, because the phone was working fine, but recently I noticed that it shows "0" for both of my IMEI numbers. Also, I switched to oreo immediately after wiping the partition, initially I made the full backup just in case I had to go back to nougat. So first I thought that the problem is caused by the early oreo builds. But I have tried several nougat builds too, even miui, but I got the same issue, standby battery drain, and no IMEI, even after installing the fastboot rom of miui. Yesterday I thought that they may have something to do with each other, so I decided to try to restore the EFS, and the IMEI. I've followed some guides here on xda and also on miui forums, and after restoring the QCN file for my model (global version) and writing IMEI with the Qualcomm imei writer tool, I succeeded . I got my IMEIs back, and I hoped that it would solve the battery drain too. But today after letting it in idle, the battery drain is the same. I would rule out any ROM specific issue, because it happens on miui too, and every rom I have tried. Also I don't think it's connected to any apps, because I have tested roms also without restoring anything, I haven't even flashed gapps, and the idle battery drain was still there. I only managed to "solve" it one way: changing preferred network type to any of the options, without LTE. If the phone is connected to HSPA+/3G, (without mobile data, just the service) I can get it to last 2 days, and it's the same if I have it in airplane mode, the drain is gone. That's why I also think that it's not a hardware issue. I could use my phone without LTE, we don't even have VoLTE here, so it's not mandatory, but I would like to solve this problem If I have already spent that many hours figuring out what the solution could be. It's also important to mention that even if connected to LTE (phone service) kernel adiutor shows that when the phone is in idle, the CPU goes to deep sleep and not awake. Now I'm reaching out to you guys, could you please help me? Thank you in advance!
Click to expand...
Click to collapse
Hi, Did you get any solution for this issue? I am experiencing the same issue as you. Please share your solution (if you got it) or your experience on what you did next to solve it?
himanshuchaurasiyahc said:
Hi, Did you get any solution for this issue? I am experiencing the same issue as you. Please share your solution (if you got it) or your experience on what you did next to solve it?
Click to expand...
Click to collapse
Hello, sorry for replying so late.
I was provided a solution by @evil-god , he sent me a "healthy" qcn, I only had to change my IMEI to my original one using an IMEI writer, and then restore the qcn file with QPST.
Since -as far as I know-, this is a device and hardware specific file, I don't think one should try it on other devices, but it should work if you have the same model.
As the original qcn (sent by "evil-god" as written above) contains his device's IMEI, I won't share it without his agreement, but hopefully he'll see this post and reply with either his agreement or the file itself.
ardrift said:
Hello, sorry for replying so late.
I was provided a solution by @evil-god , he sent me a "healthy" qcn, I only had to change my IMEI to my original one using an IMEI writer, and then restore the qcn file with QPST.
Since -as far as I know-, this is a device and hardware specific file, I don't think one should try it on other devices, but it should work if you have the same model.
As the original qcn (sent by "evil-god" as written above) contains his device's IMEI, I won't share it without his agreement, but hopefully he'll see this post and reply with either his agreement or the file itself.
Click to expand...
Click to collapse
share it, its not my imei.
ardrift said:
Hello, sorry for replying so late.
I was provided a solution by @evil-god , he sent me a "healthy" qcn, I only had to change my IMEI to my original one using an IMEI writer, and then restore the qcn file with QPST.
Since -as far as I know-, this is a device and hardware specific file, I don't think one should try it on other devices, but it should work if you have the same model.
As the original qcn (sent by "evil-god" as written above) contains his device's IMEI, I won't share it without his agreement, but hopefully he'll see this post and reply with either his agreement or the file itself.
Click to expand...
Click to collapse
So here is the mentioned file that fixed the issue, I hope it will work for other affected users as well.
Hey all,
My phone updated today and ever since I cannot move past the initial lock screen. When unlocked, the UI appears to crash and send me back to the lock screen. My pin code works for turning the phone off, restarting the phone and putting it into emergency mode, which indicates some sort of UI crash.
Because this is a new account I can't post a link to a video of the issue directly, but the YouTube video code is: 8ZhlH-Tt-NU
I have tried the standard fixes like wiping the cache partition and booting into safe mode, but these don't seem to make any difference. Unfortunately I never logged into my Samsung account on this device, so their 'Find My Mobile' service is not an option. I am however signed into my Google account on the device and it does have wifi/network enabled.
The phone is running PPR1.180610.011/G965FXXU2CSA8
On the phones internal memory is a bunch of photos from a recent trip to Japan, I'm a fool for not backing these up sooner but I would hate to lose them.
Has anybody experienced anything like this before, and is there any way for me to get back into the phone, or atleast recover the photos that I took?
Thanks!
Edit:
One potential route out of this I can see is sideloading the same or a subsequent OTA update using ADB to hopefully fix the issue. Unfortunately despite some digging I can't find any updates that will allow installation from: PPR1.180610.011/G965FXXU2CSA8
If anybody has any information on this specific firmware version (Is it beta 3? beta 4? ect.), its installation path and where files relating to it may be listed/hosted it would be appreciated. Also how disasterous would it be to take a mismatched OTA upgrade and modify the metadata to allow it to be sideloaded onto the phone? I assume this would almost certainly break the OS completely but I'm not too sure.
You can try to flash your firmware again with ODIN, but with the HOME_CSC (Important!)
profi_fahrer said:
You can try to flash your firmware again with ODIN, but with the HOME_CSC (Important!)
Click to expand...
Click to collapse
Thanks for the reply Profi I had no idea using HOME_CSC would retain user data. I have tried flashing a few different versions of Pie (wish HOME_CSC) using Odin but with no luck, every time the phone boots I have the same problem. Do you know if there is a sure way to downgrade to Oreo while retaining user data? I have seen a few posts of people attemping this and getting stuck in bootloops, eventually requrining them to factory reset.
To give a final update on this. I attempted the Oreo downgrade, upon reboot the phone was stuck in a bootloop so I updated to Pie again. When the phone booted I tried the pin code as quickly as I could, and after some glitchy graphics on the screen it unlocked. From here I turn on the stay awake while plugged in feature in the developer options and managed to transfer all my data over to PC.
I don't believe it was the firmware changes that actually made any difference, because any further attempts to put my pin in, to remove the pin code for example, failed and cause the same crashing behaviour.
All data is recovered, I have factory reset the phone and all appears to be behaving as normal again. If anybody stumbles upon this with the same issue, all hope is not lost, but unfortunately I was unable to determine a realiable way to overcome it. It seems in this case it was just dumb luck.
Thanks for the assistance.