Related
Hello people, I have a rather peculiar issue with my SII
I have had this issue for some time now and really doesnt bother me that much, its just annoying. And its just now that I have bothered writing a post about it.
If Ive run out of battery, I plug my phone into the charger, turn it on while its charging, I get no service, not prompted to input PIN and get the Uknown IMEI\baseband version. But if I let it charge a couple of minutes, unplug the charger and turn it on, everything works fine. Whats going on here?
I think this problem occured after installing one of bmarko's MIUI roms. I have since full wiped and restored stock rom. Upgraded two new official samsung roms as they have been released, currently running XWKI8 unrooted completely stock and the issue still persist.
I have searched around and there are similar cases out there but not really any clear solutions. Theres even a post over at cyanogenmods forum site, but no replies.
As said earlier its not really a big issue for me, not expecting a immediate solution but I would really like to understand the problem if someone has the information since I dont have the technical competence to understand it myself. I obviously havent corrupted or lost anything in my efs folder since its working without the charger, or? Could there be remains of a bug from another rom still in the system causing this?
Any replies would be appreciated, thanks.
Same Problem
Hey FlipTrick,
I got exactly the same problem. Dont remember how it happened exactly, but do remember I didn't do anything exotic. Can't display my IMEI, unknown baseband version and no prompt for my PIN.
I Tried several things:
- Reflashed the advised codeworx kernel using odin.
- ReInstalled CM 7.1 and tried nightly version.
- Reflashed different RADIO ROMS from XDA (goo.gl/TjoaM)
Nothing worked. Does anyone know what the problem might be? Or know what I could try next?
Greetings,
Xianduras
I had this problem once when I used a jig to reset the flash counter. Given the modem (and the IMEI) wasn't showing up in the phone details, I reflashed the modem which fixed it.
Occasionally after a reboot my modem/IMEI details take around 20-30 seconds to appear, but they've never not turned up/left me without service apart from that one occasion.
problem gone?!
Problem seems to be gone, noticed it after flashing Hydrog3n rom. Cant say if thats the solution though, havent tested it for awhile and i've flashed alot of roms
Hi guys,
I have a huge problem. I had a stock GB firmware customized by Optus (carrier in Australia) on my S2 I then decided to change to the new ICS 4.0.4. I downloaded the stock unbranded firmware from SamMobile (Australia 2012 September 4.0.4 I9100XWLPW, I9100XSALP6, XSA) I updated using Odin. Before I did the update I reset the phone, did the update, it all went smoothly. After the update I reset the phone again and then proceeded to reinstall all my apps and restore my contacts, sms, etc.
The phone works and all functions on it work, however now very randomly the phone would totally freeze. The phone would be in standby, the screen would come on and it would be frozen. The screen stay on all the time and it does not respond at all. It will stay frozen until I restart the phone by pressing Home+power buttons to restart it.
After restart it all works fine for a few hours, sometimes a day and would just lock up again. The phone is not rooted and as I said i just changed the firmware from the Optus branded GB 2.3.6 to unbranded stock ICS 4.0.4 by using Odin.
Is there a way to find out what is causing the phone to lock up like that? Any suggestions would be helpful.
and then proceeded to reinstall all my apps and restore my contacts, sms, etc.
Click to expand...
Click to collapse
I hope you haven't restored any data app?
przemcio510 said:
I hope you haven't restored any data app?
Click to expand...
Click to collapse
I made sure that I didn't restore any data apps. The only apps that got restored are the ones that get automatically restored by Play store.
I have disabled the live wallpaper that I had and it seems to have stopped the freezing for the moment. I will report on what I find out.
In the mean time if anyone else has a similar issue or has a definite solution please let me know.
Thanks
i know this is a resurrection, but don't see it has been resolved.
also found same/similar problem on another topic, but no resolution either.
couldn't find any resolution anywhere on the net, but possibly i'm just missing it (searching for wrong parameters?)
anyway, a friend of mine bought second-hand (third or even fourth hand to be precise) i9100 with 2.3.6 (stock KI3) on it. the guy who sold it to him said something like: "it works best on 2.3, on 4.x it's buggy".
it was working fine, but friend wanted newer OS, so we tried update. it didn't work, and i found out CSC was broken/missing. somehow i managed to repair it, and update was finally working, but was unable to find any for our location.
so next step was to find stock rom that would work on the device, and then i tried four different 4.1.2 stock roms from this topic.
after flashing it through odin, every one was acting fine, until couple of minutes after it started freezing or rebooting randomly.
then i tried flashing CWM, and flashing from sd card, but it was all the same.
wiping data, cache and dalvik cache, prior to flashing. wiping data after flashing...
nothing seemed to work.
GB works rock solid, ICS works better than JB, but stills it freezes or restarts randomly.
tried CM10, but all the same, except it works a bit faster then official JB. but who cares about speed if it freezes/restarts constantly?
back to who knows which build... freeze... samsung galaxy s2 - i9100... with yellow triangle... booting stopped.
so i decided to dig deeper, trying to find hungarian stock build (country we were told the phone came from) not being sure that KI3 is what the phone came actually with. i found 4.0.3, put it on SD card, wiped data, cache, flashed CWM, wiped data, cache, dalvik cache, flashed 4.0.3 from sd, wiped data, booted, entered location for updates - hungary. update found, hooray... downloading... installing... rebooting... working?
nope... it's worse than ever. trying to log onto google account. typing in email add.... freeze... switching phone on - freeze... thinking about... freeze.
i couldn't sit still. yellow triangle, all those reboots/freezes... at least i wanted that triangle gone, and without a JIG, there was only solution for me was to try triangle away. it wasn't available for download in my country from play store, so luckily xda was there.
somehow i managed to download it from the device, install it, click remove the triangle... it did it's magic, rebooted... and miracle happened!
no more freezes.
so i started torturing poor phone, benchmarking, playing games, listening to music.... it seemed stable for about an hour.
so i said to myself:
- it's possible that previous owners tried to upgrade it to newer firmware, and somehow screwed up the bootloader, which was fixed by this app? maybe that was all there was from the beginning? why not try putting 4.1.2?
and i did... took 4.1.2 spanish build from already mentioned page above, flashed it... and voila. working JB... torturing the phone... playing with it... hour passes, another hour...
friend wakes up... takes his phone in awe, starts playing with it.. we talk a bit... and then that look it just froze again!
from that moment on, the phone again starts restarting or freezing randomly...
and, yes, i still have no clue what could be the cause. it doesn't matter if wifi is on or off, if you're talking on the phone or not, bluetooth and gps are always off. only thing that he noticed is that it usually happens while he's using the phone (meaning: operating the digitizer or buttons). if he starts music playback and not touching buttons or screen, it will probably play for hours.
one more thing, but i doubt it would be the case. the battery in the phone is not original one that was shipped with it, but a quality replacement.
it doesn't feel as if the phone is overheating... so i don't know what else i could do with it.
for now, it's back to 2.3.6.
we both lost a week, torturing ourselves with this problem.
i don't know is there anything i could add more?
all suggestions are welcome.
cheers
Maybe try kernel cleaning script and try philz or siyah kernels.
You shouldn't have to flash a custom kernel so your phone won't freeze, but yes, you could run a nuke script in order to wipe clean all custom ROM's leftovers.
Try flashin' jb via mobile odin, see if it keeps freezing up on you. If so, nuke it up.
Sent from the little guy
i'll try them out.
probably for the weekend, if not sooner. will report back here with info.
any other suggestions are also welcome.
thanks a lot.
cheers
ok, so here are some updates.
i finally got my hands back on my friends phone, and tried nuking remains of older flashes.
following that, i flashed stock spanish rom from above mentioned page, updated after installation to spanish update... and after a few minutes, sudden reboot...
so, went back to nuking, and flashed stock hungarian 4.0.3 i found elsewhere (mentioned in my earlier post. don't remember origin... if i find the link on another computer where i downloaded it on, i'll post the link). tried updating, says no updates found.
started torturing the device. it seemed solid, but battery reported it level was low, so hooked it up onto charger and all seemed well. but phone seemed a bit too hot.
after few minutes (this was all about half an hour to hour after flashing to 4.0.3), again freeze.
after rebooting the phone, battery was at 9%, as if processes were draining battery faster than charger recharged it.
so, i figured i gotta try original battery. so i switched his battery with genuine from my phone.
phone seems stable and less hot, for now.
still checking if it is going to freeze or reboot again.
it's about one hour since battery change. still on charger and using wifi and playing around with apps.
i'll check in with news later.
cheers
I have the same issue.but my battery is original.
What I noticed that the phone stuck when I receive an update notification.
Can I stop softwsre to ask for updates? ???
Sent from my GT-I9100G using xda app-developers app
^go to settings, about device, software update and detick auto update. that should stop it from trying to self-update.
ok, so here is an update to my friend's phone status.
currently on hungarian 4.0.3. about 3-4 freezes/reboots a day. sporadic connection breakups during calls. also, when we talk i can hear myself back. this brings me to conclusion it has to do with modem firmware. i found this topic, so i'll try putting that and see what will happen.
if that doesn't solve anything, my question is this: is there any way of knowing which firmware/rom was originally put on the device, since i don't know the real background of the device? i.e. some way of entering IMEI and finding out what should be on it?
cheers
EDIT: tried KH3 modem, no changes... i could still hear myself while talking to my friend on that device. also, it froze couple minutes later. going back to 2.3.5-2.3.6 for now.
so after couple of months, i finally got my hands back onto this phone...
gave my friend my phone, so i could play a bit with this faulty one.
i have played with it for a couple of days now, and here are things i've tried.
i received it from a friend with 2.3.5 on it which had triggered custom binary counter. he's been using it for couple months without any problems.
so i rooted it and installed triangle away again... reset counter, cleared and flashed hungarian stock (telenor) 4.1.2... random freezes again.
tried several stock roms, mostly hungarian ones (4.0.3, 4.1.2). even reformatted with .pit file... random freezes.
reformatted again with .pit and put XXLSJ, installed stability test and let it run...
cpu stability test 15.5 hours no problems, no freezes. then i realized it didn't have a sim card, so i rebooted phone and installed sim card. let it test cpu+gpu for 9 hours... no errors, no problems, no freezes.
so i thought, maybe it's all fine? but it wasn't! as soon as i took phone into my hands and started going through menus it froze!
so i tried SGII_repair, rooted and did "repair"... but nothing changed... still random freezes.
if i just let it do the stability test, it'll probably work forever.
things i've noticed:
- serial number is wrong format (14 hex digits instead of 11 alphanumeric)
- during stability test, cpu frequency dropped from 1200 to 800 mhz (maybe because it was getting warmer? 42-43C during cpu only+charging battery, and about 39-40 during cpu+gpu test)
i tried to find out which firmware is latest according to serial number via kies, but it gave me error.
i know it's from hungarian market, but don't know which exact part of it (branded or not).
don't know what previous owners did to it, and don't have backups of original efs or anything original.
i just want to make it work, don't care much about custom firmwares. i'd be happy even with unrooted stock... just for it to work!
i have no ideas what else to do.
anyone?
finally, as i couldn't resolve the problem, i returned phone to 2.3.5 and sold it as is.
thanks to all people who tried to help.
cheers
Well, received my Sony Xperia Z Ultra C6833 a couple of days ago.
Received a notice on the OTA, upgraded to 14.1.B.2.257
I encountered random restart issues whenever Wifi is activated, so I thought, fine.
I finally have access to my computer, installed the PC companion, it prompt me with a new 14.2.A.0.290 update.
Again, I updated my phone, hoping it'll fix the Wifi problem.
After restarting, I did a test, as usual. Wifi problem persists, and what's worse, a new problem. Wifi and Playstation 3 SixAxis controller connected using bluetooth didn't play nice, caused my phone to reboot.
I know a lot of people downgraded the firmware back to the previous version, with NAN backups etc.
And some even managed to restore their IMEI back to normal.
But for my case, I haven't root my phone, attempt to downgrade it using Flashtool, lost my IMEI.
Seems that I have no choice, but to return it back to 14.2.A.0.290 praying that it works, and I still can't see my IMEI.
No, I don't have a NAN backup. That's the part which gave me a headache. I've messed around with HTC one X (a year ago), never had this problem problem before, and it's something new I've learnt from you guys today.
Tried cyangenmod's boot.img, doesn't do me any good.
Anyone managed to recover their IMEI here?
Otherwise I might have to get it back to the dealer for a replacement.
Update: Thanks to krabappel2548's guide, I've managed to flash it to 14.2.A.0.290 again and got my IMEI back, but SixAxis still won't play nice with Wifi, and the problem with random reboots while Wifi is ON still persists.
we have the same issue, mine happened during the old update, after ota wifi gets stuck, wont turn on and reboots the device. upto now its still not fixed. 3 updates have passed and still the issue persist. hope you find a fix it will help me too. tried everything from downgrading, flashing custom rom,kernel, upgrade, unlock, relock but still cant fix it
I guess i'm not the only one then. I can live with the wifi issue for the time being as long as i stick to using data. But i fear it's going to affect tethering should i need that.
Please take a look at this post, it may help you. --> http://forum.xda-developers.com/showthread.php?t=2573349
nopponm said:
Please take a look at this post, it may help you. --> http://forum.xda-developers.com/showthread.php?t=2573349
Click to expand...
Click to collapse
Read it the moment I discovered that my IMEI is missing.
I tried reflashing excluding the baseband, doesn't work for me, right after i realized i have a missing IMEI.
Read up on the android emulator, but haven't tried it, as my computer is kinda old, took forever to run it. Will try it once I get my hands on a faster computer
Bah. Crashed when I tried to use my qx100 which i've just received. Haha. Anyone else has any fun with qx100 and z ultra combo? The Z ultra almost reminds me of my ex-girlfriend.
Meanwhile, I can't wait for kit Kat, and hope they really squash these bugs
The best thing would be to contact Sony and make them aware of this bug. Losing your IMEI by simply updating should never happen and it's quite a serious bug.
Actually i lost it after downgrading. Downgrade is simply because of phone keeps rebooting after I turn Wifi on.
LordManhattan said:
The best thing would be to contact Sony and make them aware of this bug. Losing your IMEI by simply updating should never happen and it's quite a serious bug.
Click to expand...
Click to collapse
let's hope this is the answer : p
New build 14.2.A.1.114
abuihsan said:
let's hope this is the answer : p
New build 14.2.A.1.114
Click to expand...
Click to collapse
I certainly hope so too.
Hope it fixes the rebooting issue with WiFi enabled.
Or the Google Play Edition port if it does fix the problem too
Anyone tested the new update yet? Does it fix the wifi issues with crashing/rebooting?
ok so i purchased my phone on amazon and got it somewhere around feb 25th, i got a message on the phone to update software so naturally i did, then i discovered what rooting does and i decided to follow some youtube instructions to flash my phone to an earlier firmware the link wasnt working so i found another which was C6802_14.1.B.0.475_GENERIC Hong Kong.ftf after flashing this i lost my imei its all zeros and i then tried flashing C6802_14.1.B.1.526_M3dD0g.ftf with no luck so im trying to find out what the updated software was that i must have downloaded when i first got the phone given the date i had recieved it im thinking that the 14.2.A.1.142 is the correct one that i must have updated to, i was running version 4.3 jelly bean before all this happened i also have this problem where everytime i turn off the phone and turn it back on it is in the chinese writing again and asks me to select my language again anyone know what to do short of return the phone while i still got time my internet is extremely slow im tired of it taking 4 hours to load a new ftf just to find out its not the right one ive heard some where hving success with the 290 getting their imei back but im thinking thats the software they started with or updated to to get it back so i have no idea which one i started with or which one i updated to all i know is the date i got it and that possibly its the 14.2.A.1.142 looks really familiar im downloading that one now so we will see what happens and i also read something about flashing excluding the basebands so if that is part of it please make it as clear as possible im obviously a noob but im learning quick
Pleas dont ask the same question in multiple threads.
See my reply to the other thread you necromanced
Well as the title says.
Just rebooted my s2 and now when I try to do anything it says "insert sim card to access network" imei is fine serials fine and even shows signal bars but soon as try to make a call to drop signal and network completely....
have restored efs folder and even dne a repair.
changed base bands
reflashed new rom
tried different sims(and networks)
and still nothing
Odd that it happened after weeks of being fine and then just did a reboot and then this all happened
any ideas folks as to next move?
please someone must have an idea or two. to offer!
Well looks like I have fixed the issue after many hours of frustration..
Still have no idea what happened to cause issue in first place..
What I did was refresh my original backup
flash original STOCK rom via odin and this seemed to have fixed it. Are there any friggin better loctaion for these files as took 8 hrs to down load the damn thing!?
now re rooted, flash custom rom, flashed custom kernel of choice and than restored back up
everything seems ok(though my imei is incorrect now as says 004999010xxxxxx ,but am concerned it will happen again. Had flashed a modem several days before and updated a few apps . but at time of the issue occuring was just clearing caches then a reboot..
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.