I recently rooted my One and had networking issues so i flashed this rom ( http://forum.xda-developers.com/showthread.php?t=2266025 ) and after flashing though the networking issues were fixed it then had issues with the back and home buttons, as the phone did when i purchased it, so i located and installed the ota patch that tmobile had pushed to fix it, and there was an error installing it, but the buttons were fixed anyway, but now my camera app does not work, i can open it and see nothing but black, the apps buttons do not appear to respond and after some time i get a "unable to start camera: error. i cannot locate a apk or anything similar to try to reinstall the camera app, other apps i launch tell me "error accessing camera", any help would be appreciated
Update: just discovered, the light does not work either
fixed issue by flashing a different rom and flashing back
i had the same problem
I never actually solved it though. It happened when a replacement was already on the way so i didn't bother trying to fix it. I did research a little and came across a few people that said a bad kernel flash could cause this. I was running the stock kernel and stock rom, and it was working just fine before the OTA so i figuered it was probably a hardware issue. If i were you i would try flashing another kernel. If doesnt work call up tmo and they will probably send you a replacement(you can also contact them through the live chat the on the website, much more convenient in my opinion). I had blown speaker and they didnt even ask about unlocking the bootloader or root, i assume it is because it was clearly a hardware issue. If you figure it out, please share.
I received yesterday my new tablet, bought from here, Dubai, UAE. I have an issue. It doesn't shut down and restart properly. After I choose to do any of these it turns off like the battery would be plugged off. After it turns back on, the basic apps like Skype, Search, Twitter and a few others which are preinstalled automatically in the ROM they go back to its initial version and the update is erased. Its like a full reset but the account and settings are not touched. I found similar problems on the forums but they get a full reset after each restart and to solve the issue you have to root your tablet and copy the busybox file from system/xbin to system/bin. I did this but it doesnt help. Also I tried to flash a ROM from their official russian website but after it starts verifying the zip an error like
Code:
assert failed: !less_than_int getprop ro.build.date.utc
shows up, in the recovery menu. My problem is a bit different.. Its related only to the basic apps which come with the ROM and only the ones who install themselves in the data section not system. Where can I start looking for a solution and do you think these improperly shut downs are related to this? I can even uninstall these apps after restart, but they are put back after the next restart. My tablet is running a 4.1.1 Jelly Bean. Would be thankful if you guys advice me in it. The device is really good, you feel some power inside, but this android system issue makes me crazy.
Sent from my B700 using xda app-developers app
Mango Polo said:
I received yesterday my new tablet, bought from here, Dubai, UAE. I have an issue. It doesn't shut down and restart properly. After I choose to do any of these it turns off like the battery would be plugged off. After it turns back on, the basic apps like Skype, Search, Twitter and a few others which are preinstalled automatically in the ROM they go back to its initial version and the update is erased. Its like a full reset but the account and settings are not touched. I found similar problems on the forums but they get a full reset after each restart and to solve the issue you have to root your tablet and copy the busybox file from system/xbin to system/bin. I did this but it doesnt help. Also I tried to flash a ROM from their official russian website but after it starts verifying the zip an error like
Code:
assert failed: !less_than_int getprop ro.build.date.utc
shows up, in the recovery menu. My problem is a bit different.. Its related only to the basic apps which come with the ROM and only the ones who install themselves in the data section not system. Where can I start looking for a solution and do you think these improperly shut downs are related to this? I can even uninstall these apps after restart, but they are put back after the next restart. My tablet is running a 4.1.1 Jelly Bean. Would be thankful if you guys advice me in it. The device is really good, you feel some power inside, but this android system issue makes me crazy.
Sent from my B700 using xda app-developers app
Click to expand...
Click to collapse
i will buy the b800 is it a good tablet im very afraid of it after looking at your comment
Hi guys, this morning my father's Le Max 2 (snap820, 4/64) stopped receiving calls, and both the home and recent apps virtual buttons decided not to function, too. Strange enough, I'm able to long press them and get the action I'm supposed. Any ideas/fix? I've already checked the phone for malicious apps and misconfigurations
Hi, I have exactly the same issue, plus I cant download any more applications from play store. Can anyone help?
If you have a backup taken when the phone was working well, I'd suggest you to restore it. If not, try another ROM, or at least a different ROM flavor (if it had an EUI based ROM, use LineageOS and viceversa). If that doesn't work, you may need to get into Qualcomm recovery mode and flash the developers ROM to get the phone to a real factory state.
But first, try to revert to factory settings from the current ROM, and see if that solves the issue.
There are several threads here with info on how to apply the above solutions.
If none of these solutions works, and you still have warranty time left, you may want to contact the seller for a repair or replacement.
Good luck.
Do the notifications work?
I was on holiday, so no PC I could use for flashing or else. A reset from the settings worked, still don't know what caused the issue sadly
I couldn't find the fix for this in any other threads, can someone help a not-terribly-tech-savvy person with a fix for this
Today I also had a same problem. So just I backed up all important data's and done factory reset. Now everything works fine.
Everyone have same problem at the same time means the ROM has virus or Trojan.
What is the ROM everyone is using?
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.