i flashed rr v5.8.5 on my zuk z1. it was a clean flash. now i am facing battery issues. google play services is using more battery than display and battery is draining very fast and charging very slowly. can anyone help me with this issue ?
rohan0101 said:
i flashed rr v5.8.5 on my zuk z1. it was a clean flash. now i am facing battery issues. google play services is using more battery than display and battery is draining very fast and charging very slowly. can anyone help me with this issue ?
Click to expand...
Click to collapse
Can you link me to the rom you have used ? i think its a bug in the rom
-Hope- said:
Can you link me to the rom you have used ? i think its a bug in the rom
Click to expand...
Click to collapse
i am using resurrection remix os v.5.8.5 based on android v7.1.2.. it was a clean flash so i was not expecting any bugs because there was no problem with v5.8.4. thank you for your help i hope you can help me out
rohan0101 said:
i am using resurrection remix os v.5.8.5 based on android v7.1.2.. it was a clean flash so i was not expecting any bugs because there was no problem with v5.8.4. thank you for your help i hope you can help me out
Click to expand...
Click to collapse
The problem seem to exist as there are some people reporting it,
Try to reflash the rom again
DON'T REBOOT
go back and flash gapps
DON'T REBOOT (some people reported that flashing gapps after first reboot causes issues then you will have to factory reset)
Do a factory reset again without flashing the rom
REBOOT
-Hope- said:
The problem seem to exist as there are some people reporting it,
Try to reflash the rom again
DON'T REBOOT
go back and flash gapps
DON'T REBOOT (some people reported that flashing gapps after first reboot causes issues then you will have to factory reset)
Do a factory reset again without flashing the rom
REBOOT
Click to expand...
Click to collapse
thank you so much for your help i hope this would help. i am new to this so i wanted to ask that if i want to do a factory reset but don't want to clear my internal storage then what all should i wipe in order to perform a factory reset. thanks
rohan0101 said:
thank you so much for your help i hope this would help. i am new to this so i wanted to ask that if i want to do a factory reset but don't want to clear my internal storage then what all should i wipe in order to perform a factory reset. thanks
Click to expand...
Click to collapse
Data
Cache
And Dalvik
there is also an option in twrp to factory reset with a arrow swipe
go to wipe
then you will see a arrow, swipe it. and then try to use your phone and see if there's a battery draining, it seems to be a problem with gapps. since i think you did flash them after the phone's first reboot.
-Hope- said:
Data
Cache
And Dalvik
there is also an option in twrp to factory reset with a arrow swipe
go to wipe
then you will see a arrow, swipe it. and then try to use your phone and see if there's a battery draining, it seems to be a problem with gapps. since i think you did flash them after the phone's first reboot.
Click to expand...
Click to collapse
Thanks a lot it works fine now
Related
I'll try to remember the steps of what happened as best I can.
T989 All Stock Running Gingerbread (Not sure what Firmware)
1)Installed CWM via ODIN
2)nstalled SuperUser via CWM
3)Installed latest AOKP from here http://aokp.co/devices/hercules
Booted up just fine but two problems
1: No Service
2: Touch screen calibration was WAY OFF
BYAM DURP OOPS
Realized that I needed to get the latest Firmware before flashing the latest AOKP!
4)Full Wipe(I think?)
5)Install latest Firmware (T989UVMC6, right?) (Also did a factory reset/wipe)
Phone boots into Stock with latest firmware, however the touch screen is still calibrated way off!
Do steps 1-3 above again.
Touch screen calibration is still way off!
My only guess on the reason/fix for this is that maybe this is still some lingering problem of flashing the ROM on the outdated firmware, so I need to perform some sort of deeper wipe than just a Full Wipe via ClockWorkMod in order to get rid of any lingering problems. And then flash the latest firmware, and do steps 1-3 above.
Any ideas or suggestions?
Any other information needed?
Thanks in advance!
YoHoJo said:
I'll try to remember the steps of what happened as best I can.
T989 All Stock Running Gingerbread (Not sure what Firmware)
1)Installed CWM via ODIN
2)nstalled SuperUser via CWM
3)Installed latest AOKP from here http://aokp.co/devices/hercules
Booted up just fine but two problems
1: No Service
2: Touch screen calibration was WAY OFF
BYAM DURP OOPS
Realized that I needed to get the latest Firmware before flashing the latest AOKP!
4)Full Wipe(I think?)
5)Install latest Firmware (T989UVMC6, right?) (Also did a factory reset/wipe)
Phone boots into Stock with latest firmware, however the touch screen is still calibrated way off!
Do steps 1-3 above again.
Touch screen calibration is still way off!
My only guess on the reason/fix for this is that maybe this is still some lingering problem of flashing the ROM on the outdated firmware, so I need to perform some sort of deeper wipe than just a Full Wipe via ClockWorkMod in order to get rid of any lingering problems. And then flash the latest firmware, and do steps 1-3 above.
Any ideas or suggestions?
Any other information needed?
Thanks in advance!
Click to expand...
Click to collapse
wipe /system
didn't work??
prantoroy said:
wipe /system
didn't work??
Click to expand...
Click to collapse
I've done wipes like this
Via CWM I do the Factory Reset/Full wipe, then cache and dalvik cache.
Is there a way to more deeply wipe?
I saw in some other places that you can mount some locations and also wipe those too, I assume maybe doing that will result in a "fuller" wipe and also wipe the firmware too?
Care to explain exactly how I should be wiping?
Also after doing the wipe, do I just flash latest firmware, install CWM/root, and then a ROM?
Thanks
YoHoJo said:
I've done wipes like this
Via CWM I do the Factory Reset/Full wipe, then cache and dalvik cache.
Is there a way to more deeply wipe?
I saw in some other places that you can mount some locations and also wipe those too, I assume maybe doing that will result in a "fuller" wipe and also wipe the firmware too?
Care to explain exactly how I should be wiping?
Also after doing the wipe, do I just flash latest firmware, install CWM/root, and then a ROM?
Thanks
Click to expand...
Click to collapse
First,
Go to CWM
and go to mounts&stroage
then format everything except /sdcard
.
.
then flash latest Firmware.
then do whatever u like
like root,cwm or flash custom rom
prantoroy said:
First,
Go to CWM
and go to mounts&stroage
then format everything except /sdcard
.
.
then flash latest Firmware.
then do whatever u like
like root,cwm or flash custom rom
Click to expand...
Click to collapse
So without a doubt I can wipe/format everything except SD Card and just flash a firmware via ODIN and be just fine?
Just double checking because it sounds scary to wipe/format so many things!
YoHoJo said:
So without a doubt I can wipe/format everything except SD Card and just flash a firmware via ODIN and be just fine?
Just double checking because it sounds scary to wipe/format so many things!
Click to expand...
Click to collapse
no.its fine.
I do it everytime I flash a rom
prantoroy said:
no.its fine.
I do it everytime I flash a rom
Click to expand...
Click to collapse
Formatted data, system, cache, and emmc.
Did Factory Wipe/Reset, Wiped cache and Dalvik cache.
Used ODIN to flash T989UVMC6, and still the touch screen is not calibrated properly.
However (I've seen other people report that problem but haven't seen a fix) when the phone is plugged in, it works just fine, but whenever it is unplugged the touch screen very unusable due to being calibrated so wrong. :/ After wiping and formatting everything and flashing a stock Firmware I'm all out of hope now!
YoHoJo said:
Formatted data, system, cache, and emmc.
Did Factory Wipe/Reset, Wiped cache and Dalvik cache.
Used ODIN to flash T989UVMC6, and still the touch screen is not calibrated properly.
However (I've seen other people report that problem but haven't seen a fix) when the phone is plugged in, it works just fine, but whenever it is unplugged the touch screen very unusable due to being calibrated so wrong. :/ After wiping and formatting everything and flashing a stock Firmware I'm all out of hope now!
Click to expand...
Click to collapse
Me TOO
sorry unable to help
Bump
YoHoJo said:
Bump
Click to expand...
Click to collapse
Try using this app. It may help you. Worked for me!
play.google.com/store/apps/details?id=br.shop4apps.touchscreenbooster.com
My Oukitel's k4000 Touch Screen Calibration Messed Up After Flashing ROM on Wrong ROM
Hello,
Please help me. I tried to see if a ROM for 'Oukitel k4000 pro' could fit 'Oukitel k4000'.
Since it didn't work out, I flashed back to the original ROM of 'Oukitel k4000', but since then, my screen behaves wrongly to touches.
Could anyone faced and managed to beat this issue?
I saw several different posts on the net, but none of them actually helped me.
One more thing:
Please try to explain, as if you explaining a child, since my android experience is not that vast to follow all the shortcuts and proffecional terms.
Thank you,
Michael
Hey there!
I flashed cm10.1.3 from dirty developers but the settings gave me fc when I go to security settings.
So I cannot check the unknown sources option and hence I cannot install apps other than from play store
Also keyboard is not working so I cannot type anything
No one has faced these bugs so thought of asking it here
Any help would be appreciated
Thanks in advance!!
Alcatraz said:
Hey there!
I flashed cm10.1.3 from dirty developers but the settings gave me fc when I go to security settings.
So I cannot check the unknown sources option and hence I cannot install apps other than from play store
Also keyboard is not working so I cannot type anything
No one has faced these bugs so thought of asking it here
Any help would be appreciated
Thanks in advance!!
Click to expand...
Click to collapse
it maybe because of a dirty flash. wipe data, cache and dalvik cache and flash the rom again.
PR0707YP3 said:
it maybe because of a dirty flash. wipe data, cache and dalvik cache and flash the rom again.
Click to expand...
Click to collapse
no
I clean flashed
I run CM 13 and want to back to color os because it is not run so smooth. I format and then flash stock recovery image (then recovery) via twrp and reboot to stock recovery.
In stock recovery i wipe data and cache. That's problem come. Before finish, the screen goes black. I try to power on the device, back to wipe data then the screen goes to black again. I try to boot to recovery and fastboot but it remain the same, back to wipe data and then the screen goes to black..
I try repair it using msm tool but because my comp not recognize the device, i use QFIL. And then i can use the fastboot to boot stock recovery. Suceed. But no os inside. Try and error many times, i can power on the device at the end.
But now the other problem comes. My wifi and bluetooth not work. And message nv backup appear.
Flash project spectrum. Wifi and bluetooth work. I flash back to stock os. Wifi and bluetooth not work again..
May someone help me to solve the problem (make bluetooth and wifi work again)?
To get back to ColorOS from spectrum flash this rom from internal storage.
http://community.oppo.com/en/forum.php?mod=viewthread&tid=41945
Sent from my R7plusf using XDA-Developers mobile app
uyab.com said:
I run CM 13 and want to back to color os because it is not run so smooth.
Click to expand...
Click to collapse
I think your initial problem was that you didn't flash open Gapps right after you flashed CM13.
Most users who are new to custom roms don't know that they have to flash Google apps separately.
kishd said:
To get back to ColorOS from spectrum flash this rom from internal storage.
http://community.oppo.com/en/forum.php?mod=viewthread&tid=41945
Sent from my R7plusf using XDA-Developers mobile app
Click to expand...
Click to collapse
I use color os now. Have no problem bout back to color from spectrum. The problem occures after that. Wifi and bluetooth do not work.
celoxocis said:
I think your initial problem was that you didn't flash open Gapps right after you flashed CM13.
Most users who are new to custom roms don't know that they have to flash Google apps separately.
Click to expand...
Click to collapse
I flashed pico after flash CM. Pico TTS unfortunately has stopped. I use browser, unfortunately stopped. Facebook stopped. Camera stopped. That's the beginning of all the problem because after that i format the phone.
uyab.com said:
I flashed pico after flash CM. Pico TTS unfortunately has stopped. I use browser, unfortunately stopped. Facebook stopped. Camera stopped. That's the beginning of all the problem because after that i format the phone.
Click to expand...
Click to collapse
Did you boot into CM after flashing CM? and then installed Gapps later on? This could explain corrupted cache.
Always follow these steps on custom roms. (first time install not upgrade)
Boot into TWRP, select wipe/factory reset.
1. Install CM Rom
after that select the next zip (or add more zips to flash)
2. install Gapps.
Let it boot and setup your phone.
If you follow this you will never have a problem in CM.
Especially the R7 series. Every change to the code is closely tripled (even quadruple) checked by devs.
Because the R5, R7, R7Plus, R7S all share the same base and its tested in on every phone.
celoxocis said:
Did you boot into CM after flashing CM? and then installed Gapps later on? This could explain corrupted cache.
Always follow these steps on custom roms. (first time install not upgrade)
Boot into TWRP, select wipe/factory reset.
1. Install CM Rom
after that select the next zip (or add more zips to flash)
2. install Gapps.
Let it boot and setup your phone.
If you follow this you will never have a problem in CM.
Especially the R7 series. Every change to the code is closely tripled (even quadruple) checked by devs.
Because the R5, R7, R7Plus, R7S all share the same base and its tested in on every phone.
Click to expand...
Click to collapse
Of course not. I flash CM and after that i flash pico right away. Not yet boot into CM. After CM and pico install then wipe dalvik then reboot.
uyab.com said:
Of course not. I flash CM and after that i flash pico right away. Not yet boot into CM. After CM and pico install then wipe dalvik then reboot.
Click to expand...
Click to collapse
But did you wipe factory reset before flashing all the above? Coming from ColorOS. Else those errors can't be explained.
celoxocis said:
But did you wipe factory reset before flashing all the above? Coming from ColorOS. Else those errors can't be explained.
Click to expand...
Click to collapse
Yes. I wipe all but not the internal storage. Is it the cause? I do not know why twrp cannot read otg. So i put CM file on internal storage.
uyab.com said:
Yes. I wipe all but not the internal storage. Is it the cause? I do not know why twrp cannot read otg. So i put CM file on internal storage.
Click to expand...
Click to collapse
I don't know about the R7Plus TWRP. I don't maintain that TWRP. I know that my R7S TWRP works with OTG.
Internal storage should have been fine. I think it will stay a mystery why you received those errors.
celoxocis said:
I don't know about the R7Plus TWRP. I don't maintain that TWRP. I know that my R7S TWRP works with OTG.
Internal storage should have been fine. I think it will stay a mystery why you received those errors.
Click to expand...
Click to collapse
wish me luck. I will try your suggestion.
uyab.com said:
I use color os now. Have no problem bout back to color from spectrum. The problem occures after that. Wifi and bluetooth do not work.
Click to expand...
Click to collapse
Once back on ColorOs from Spectrum. Flash this older version of ColorOs and then CM everything including bluetooth should work fine.
https://www.dropbox.com/s/xmh77xyinz2iero/R7plusfEX_11_OTA_012_all_201512251816.zip?dl=0
kishd said:
Once back on ColorOs from Spectrum. Flash this older version of ColorOs and then CM everything including bluetooth should work fine.
https://www.dropbox.com/s/xmh77xyinz2iero/R7plusfEX_11_OTA_012_all_201512251816.zip?dl=0
Click to expand...
Click to collapse
Oya.. Let me try it..
Solved. WiFi and Bluetooth work fine. Run smooth in CM.
uyab.com said:
Solved. WiFi and Bluetooth work fine. Run smooth in CM.
Click to expand...
Click to collapse
Which method fixed the issue in the end?
Maybe bad repaired or bad flashing. Persist folder is empty. Thats why i can not install CM and unvailable wifi and bluetooth address. So flashing persist.img after remove the old one.
uyab.com said:
Solved. WiFi and Bluetooth work fine. Run smooth in CM.
Click to expand...
Click to collapse
hi sir im having the same problem with my R7 plus can you help me
i already flash my phone using QFIL with Oppo_R7_Plusf_EX_11_A.15_160612_By(GsmTechSupport)
result is only OPPO Logo
flash the phone with Msm8x38 with Oppo_R7_Plusf_EX_11_A.15_160612_By(GsmTechSupport)
result is phone will boot normal but the problem is same with your problem with WIFI and Bluetooth also appear something with NV partion but can be manage with *#268# but with wifi and bluetooth i cant solve
please help me.
thank you in advance
I'm so sorry. I just log in after a long time and read your problem. Have you solved the problem?
same problem for me, no wifi and no bluetooth after flashing stock rom.
Any idea?
uyab.com said:
Maybe bad repaired or bad flashing. Persist folder is empty. Thats why i can not install CM and unvailable wifi and bluetooth address. So flashing persist.img after remove the old one.
Click to expand...
Click to collapse
hello,
please ask me where to find persist.img and the method for flashing it.
thanks in advance
Everytime I try and use Google Maps either flashed with gapps/bean or installed later from play store all reboot my phone. Stock does not have any issue.
Tried:
ASOP-CAF
ASOP-EX
MOTOPURE
Lineage
TESLA
I just wonder why if the stock maps app works on 6.0 why not on 7.0?? The only thing I can think of is the GPS.
Any tips or suggestions?
Thanks!
Tried nano, pico and full for ARM and Android 7
open_gapps-arm-7.1-full-20170523
open_gapps-arm-7.1-nano-20170511
open_gapps-arm-7.1-pico-20170513
also BeansGapps-Full-7.1.x-20170509 BeansGapps-Mini-7.1.x-20170509
Ok I have found that other maps reboot the phone too. Tried a GPS test app from play store and soon as I allowed it to access my location it rebooted. So it seems to be definately a GPS issue.
grantdb said:
Ok I have found that other maps reboot the phone too. Tried a GPS test app from play store and soon as I allowed it to access my location it rebooted. So it seems to be definately a GPS issue.
Click to expand...
Click to collapse
Return to stock by fastboot the lastest images available, flashing everything including the wipes (of course, skip gpt.bin and bootloader.bin if necessary), then take the lastest OTA's, verify operation of GPS... After that install TWRP, backup everything, and flash a ROM and Gapps, do not restore anything and test again.
I can't see how GPS would work with stock and not with ANY custom ROM...
acejavelin said:
Return to stock by fastboot the lastest images available, flashing everything including the wipes (of course, skip gpt.bin and bootloader.bin if necessary), then take the lastest OTA's, verify operation of GPS... After that install TWRP, backup everything, and flash a ROM and Gapps, do not restore anything and test again.
I can't see how GPS would work with stock and not with ANY custom ROM...
Click to expand...
Click to collapse
Thanks for helping me, do you mean bootloader.img?
Ok done reflash stock, OTA's and checked gps is fine now backing up... going to use the PureNexus rom or ASOP-CAF
ARRRRRGGGGG Same damn issue... Maps crashes the phone.... so frustrating I am going to give up soon and stick with stock.
Going to try an get a logfile maybe someone can take a look at it
Thanks
ok after phone crashed the first time I rebooted a couple times and its working!!!!!!!!
Thanks to @acejavelin and @Vikas Tewatia for trying to help me with this issue.
I think one of the problems was the way I was wiping after stock to install a custom ROM, instead of just standard TWRP wipe I was using individual selections?
Anyways I am going to further test and then report back. I will close this thread once I am sure everything is working.
Thanks
grantdb said:
ok after phone crashed the first time I rebooted a couple times and its working!!!!!!!!
Thanks to @acejavelin and @Vikas Tewatia for trying to help me with this issue.
I think one of the problems was the way I was wiping after stock to install a custom ROM, instead of just standard TWRP wipe I was using individual selections?
Anyways I am going to further test and then report back. I will close this thread once I am sure everything is working.
Thanks
Click to expand...
Click to collapse
The recommended way to wipe before installing a ROM is to manually wipe system, data, caches, and internal storage (kind of optional, make sure to move TWRP backups and other info to SD card first), then flash ROM and Gapps. Some people say flash ROM, boot, then shutdown and flash Gapps, but I have never had to do that.
I would be curious to see a logcat of the crash... this is not normal. Are you installing ANYTHING else besides the ROM and Gapps at this point?
acejavelin said:
The recommended way to wipe before installing a ROM is to manually wipe system, data, caches, and internal storage (kind of optional, make sure to move TWRP backups and other info to SD card first), then flash ROM and Gapps. Some people say flash ROM, boot, then shutdown and flash Gapps, but I have never had to do that.
I would be curious to see a logcat of the crash... this is not normal. Are you installing ANYTHING else besides the ROM and Gapps at this point?
Click to expand...
Click to collapse
I started a bug report (interactive) when I tried to use the maps again but thats when it started working properly. lol
If you know of a way to get logs from the first crash off my phone I would be more than happy to send it to you.
I did a twrp standard wipe this time rather than each partition under advanced wipe, I didn't install anything other than a ROM and either gapps or bean depending on the ROM creators suggestion and that's it!
grantdb said:
I started a bug report (interactive) when I tried to use the maps again but thats when it started working properly. lol
If you know of a way to get logs from the first crash off my phone I would be more than happy to send it to you.
I did a twrp standard wipe this time rather than each partition under advanced wipe, I didn't install anything other than a ROM and either gapps or bean depending on the ROM creators suggestion and that's it!
Click to expand...
Click to collapse
You can use ADB to get real-time logging of the crash on your PC... Use Google to find the command.
acejavelin said:
The recommended way to wipe before installing a ROM is to manually wipe system, data, caches, and internal storage (kind of optional, make sure to move TWRP backups and other info to SD card first), then flash ROM and Gapps. Some people say flash ROM, boot, then shutdown and flash Gapps, but I have never had to do that.
I would be curious to see a logcat of the crash... this is not normal. Are you installing ANYTHING else besides the ROM and Gapps at this point?
Click to expand...
Click to collapse
Sent you logcat via pm thanks again!
Well I started getting random reboots in Pure Nexus ROM and so tried LOS and right away I had the reboot from Maps. I give up, staying with stock.
Thanks
Seems like one of my problems could be ASOP-CAF ROM as the version I was flashing uses a custom Kernel that has known issues with 7.1.2 and causes bootloops and crashes. The UltraDev kernel changes some things in the modem and could be why any roms I tried after flashing ASOP-CAF would not change the modem and were 7.1.2 based.
Anyways...
Well I think I have tried almost every 7.x ROM I can find and every single one has a problem with any gps app on my phone.
grantdb said:
Well I think I have tried almost every 7.x ROM I can find and every single one has a problem with any gps app on my phone.
Click to expand...
Click to collapse
Check out this bug report. It might be your APNs... https://jira.lineageos.org/browse/BUGBASH-248
By messing with my APN settings as per above bug report I can use maps and have no more random reboots. Woop woop
I don't even get a haptic feedback anymore.
What gives?
blksith0 said:
I don't even get a haptic feedback anymore.
What gives?
Click to expand...
Click to collapse
It is probably broken/inoperable.
Droidriven said:
It is probably broken/inoperable.
Click to expand...
Click to collapse
It's this CrDroid ROM on the Pixel 3a.
My soft-button didn't break
blksith0 said:
It's this CrDroid ROM on the Pixel 3a.
My soft-button didn't break
Click to expand...
Click to collapse
If it was caused by flashing a ROM, did you factory reset and wipe cache and dalvik cache after flashing the ROM? Did you try wiping the system partition before flashing the ROM? Wiping system before flashing the ROM is sometimes necessary with some ROMs.
If it caused by the ROM itself and not by the flashing procedure, you should post your issue in the ROM thread where you got the ROM from so that whoever built the ROM can fix the issue. You could also try flashing a different custom kernel for your specific model number and android version to see if it corrects this issue.