Related
Problem occur in stock fw(3.2.4), Nexus 2.01 and even after rollback to .3.1.0
My HDX when lying on the table goes on and off every minute(clock resets to 0:00 after each reboot), but when I start to use it, it's working fine without auto reboot...
At first when I flashed Nexus everything was ok but then I was busy and haven't used my tab for few weeks and now I have this annoying problem.
Because of this battery goes low very fast.
Is this hardware or software problem?
Hope for your help.
Clock reset to 0.00 is normal with your Nexus Rom after reboot; when wifi is on while you reboot time setting is ok...
It has been fixed with 2.05
I would install and use stock for a day to try if the problems still are there...
(maybe 13.3.2.3, because after that you can install TWRP and a custom rom straight away...; but disable OTA or disable wifi while on stock, otherwise you will get an update)
Maybe a complete new installation (stock -> twrp -> custom rom) will fix it
futzmaster said:
Clock reset to 0.00 is normal with your Nexus Rom after reboot; when wifi is on while you reboot time setting is ok...
It has been fixed with 2.05
I would install and use stock for a day to try if the problems still are there...
(maybe 13.3.2.3, because after that you can install TWRP and a custom rom straight away...; but disable OTA or disable wifi while on stock, otherwise you will get an update)
Maybe a complete new installation (stock -> twrp -> custom rom) will fix it
Click to expand...
Click to collapse
I'm now on 13.3.2.3.2 and problem is still there... I get clock reset on stock fw not nexus, is this normal too?
I also did factory reset...
Long shot - try a forced shutdown via long press of power button. On rare occasions I have found this corrects device weirdness. Really should have the same effect as soft powering off but for some reason it seems to work. Worst case you've lost 2-3 min trying.
Also check if same behavior occurs while booted into recovery. If so almost certainly a hardware issue, possibly when CPUs throttle down or some other 'idle' state kicks in.
Davey126 said:
Long shot - try a forced shutdown via long press of power button. On rare occasions I have found this corrects device weirdness. Really should have the same effect as soft powering off but for some reason it seems to work. Worst case you've lost 2-3 min trying.
Also check if same behavior occurs while booted into recovery. If so almost certainly a hardware issue, possibly when CPUs throttle down or some other 'idle' state kicks in.
Click to expand...
Click to collapse
Did hardware reset, unfortunately without success...
What do you mean with "booted into recovery"? Fastboot or another fw slot with safestrap?
Flashed cm11 and still got this issue! I'm done...
I think you don't need to test custom roms yet...
Your goal should be to have a clean stock rom with no errors.... (no safestrap and stock custom recovery)
If you still have errors you need to contact amazon anyway i guess....
futzmaster said:
I think you don't need to test custom roms yet...
Your goal should be to have a clean stock rom with no errors.... (no safestrap and stock custom recovery)
If you still have errors you need to contact amazon anyway i guess....
Click to expand...
Click to collapse
alright, what's the steps to recover to clean stock from twrp with cm11?
Hi,
Last night I installed the new stock lollipop. Initially I had a problem with rooting it but eventually everything was working fine. I've used Philz recovery and cf-auto-root. All seemed fine, and I've got all my apps, accounts, etc. back.
This morning I woke up and it looks as if at 6:02am the phone just froze. The strange things are (1) I could turn on and off the display so it was not completely frozen, just the UI (displaying new screens and receiving a response from the keys or the touch screen). (2) I thought to reboot into recovery and when I did - it was the stock recovery! not sure what happened to Philz that was there before?
In any case, I did clear cache and restarted. The logo came up but after 20 sec I've got "unfortunately, media storage has stopped". Of course - it did not receive any response from keys or the touch screen so I could not release this message - only on-off worked. After a minute or so, I saw that other services are crashing...
Of course I can do yet another "wipe to factory" but I was wondering if anyone experience the same. If I will make it work after clear to factory - I'm afraid it will behave the same after a day or so... Any suggestions?
Thanks!
gilbnx said:
Hi,
Last night I installed the new stock lollipop. Initially I had a problem with rooting it but eventually everything was working fine. I've used Philz recovery and cf-auto-root. All seemed fine, and I've got all my apps, accounts, etc. back.
This morning I woke up and it looks as if at 6:02am the phone just froze. The strange things are (1) I could turn on and off the display so it was not completely frozen, just the UI (displaying new screens and receiving a response from the keys or the touch screen). (2) I thought to reboot into recovery and when I did - it was the stock recovery! not sure what happened to Philz that was there before?
In any case, I did clear cache and restarted. The logo came up but after 20 sec I've got "unfortunately, media storage has stopped". Of course - it did not receive any response from keys or the touch screen so I could not release this message - only on-off worked. After a minute or so, I saw that other services are crashing...
Of course I can do yet another "wipe to factory" but I was wondering if anyone experience the same. If I will make it work after clear to factory - I'm afraid it will behave the same after a day or so... Any suggestions?
Thanks!
Click to expand...
Click to collapse
This happened to me. I had to do a factory reset.
I seriously do not recommend cf auto root(because its not designed for this firmware). Use chainfire's update SU zip that you flash through a recovery. That update SU zip will prevent the stock recovery from being re-flashed. In addition, I always do a factory reset (wipe entire internal storage) before updating the ROM since I root. If I didn't root or anything, I wouldn't wipe my data. But when we root and mess with stuff, plus all the tries to prevent root, it conflicts sometimes. So a factory reset is always best. I was able to use Titanium Backup to restore everything. Just forgot to backup my Internal SD card.. xD
elesbb said:
I seriously do not recommend cf auto root(because its not designed for this firmware). Use chainfire's update SU zip that you flash through a recovery. That update SU zip will prevent the stock recovery from being re-flashed. In addition, I always do a factory reset (wipe entire internal storage) before updating the ROM since I root. If I didn't root or anything, I wouldn't wipe my data. But when we root and mess with stuff, plus all the tries to prevent root, it conflicts sometimes. So a factory reset is always best. I was able to use Titanium Backup to restore everything. Just forgot to backup my Internal SD card.. xD
Click to expand...
Click to collapse
Thanks elesbb, I saw your message just now but I have my phone working already since few hours ago after a 2nd stock reflashing. If I have the same issues as before - I will use chainfire's update SU.
What I did find is that once I enable accessibility (to apps like Tasker, and an LG bluetooth headphone I have (so it could announce notifications) the phone becomes unstable; it just went through 2 boot loops but eventually recovered... Hopefully it will stay stable.
Gil.
I asked a few questions in the official thread and did not resolve my issue. From replies to others in the thread I should probably try asking in the 'Discussion' thread(?) but I thought I would ask other HAM2 users here first.
Short version:
On my Ascend Mate 2 and I cannot boot after using romracer's version of xposed for sdk22 (http://forum.xda-developers.com/xposed/super-alpha-posted-permission-xposed-t3072979). I flash the latest version, wipe the cache, and press "reboot". It shows the boot logo, then the boot animation, then stays on the slightly animated Huawei logo indefinitely. I left it for an hour once just to see if it would change/finish.
Longer version:
(Started by making everything factory reset/stock.)
1. Got the B321 update
2. Got TWRP 2.8.7
3. Rooted with the latest SuperSU
4. Installed Viper4Android FX
5. Restored all my apps and settings with the stock backup tool
6. Flashed xposed-v71-sdk22-arm-by-romracer-20150816.zip
7. Would no longer boot. (First logo screen stays on for much longer than normal, then the Huawei animation plays, but without sound, and finally the animated Huawei logo just sits there.)
Nothing else was changed or added or modded before trying to flask xposed.
• The APK is not yet installed (not sure if that matters)
• I’ve tried the current version, as well as 70, 69, 68, and 67 for good measure
• I attempted to flash the 64 and 86 versions just in case
• I even tried a version for sdk22 posted by C3C076. This version did not even get to the animation screen and could not be removed with romracer's uninstaller (just thought I would try)
• I’ve tried waiting 10, 20 and even 60+ minutes for the boot to complete… it just sits there
• I’ve checked and rechecked and redownloaded the zip from the official (“unofficial”) first page
• I wipe the dalvik cache each and every time I flash
• After a few minutes, if connected to my computer, the initial Huawei folder window will appear (the one with Docs, drivers, and “autorun”), and my phone will show up in adb devices list in command prompt. I can even use adb commands at this point. I really believe this means something.
• To get back into my phone, each time, I have to restore the system backup or flash the uninstaller zip.
I really want a number of xposed modules! My phone works 'fine' without them, but who roots their phone for merely 'fine'. Any suggestions are appreciated.
Haven't heard of xposed working on stock lollipop EMUI . It does work on CM tho .
neocortex08 said:
I asked a few questions in the official thread and did not resolve my issue. From replies to others in the thread I should probably try asking in the 'Discussion' thread(?) but I thought I would ask other HAM2 users here first.
Short version:
On my Ascend Mate 2 and I cannot boot after using romracer's version of xposed for sdk22 (http://forum.xda-developers.com/xposed/super-alpha-posted-permission-xposed-t3072979). I flash the latest version, wipe the cache, and press "reboot". It shows the boot logo, then the boot animation, then stays on the slightly animated Huawei logo indefinitely. I left it for an hour once just to see if it would change/finish.
Longer version:
(Started by making everything factory reset/stock.)
1. Got the B321 update
2. Got TWRP 2.8.7
3. Rooted with the latest SuperSU
4. Installed Viper4Android FX
5. Restored all my apps and settings with the stock backup tool
6. Flashed xposed-v71-sdk22-arm-by-romracer-20150816.zip
7. Would no longer boot. (First logo screen stays on for much longer than normal, then the Huawei animation plays, but without sound, and finally the animated Huawei logo just sits there.)
Nothing else was changed or added or modded before trying to flask xposed.
• The APK is not yet installed (not sure if that matters)
• I’ve tried the current version, as well as 70, 69, 68, and 67 for good measure
• I attempted to flash the 64 and 86 versions just in case
• I even tried a version for sdk22 posted by C3C076. This version did not even get to the animation screen and could not be removed with romracer's uninstaller (just thought I would try)
• I’ve tried waiting 10, 20 and even 60+ minutes for the boot to complete… it just sits there
• I’ve checked and rechecked and redownloaded the zip from the official (“unofficial”) first page
• I wipe the dalvik cache each and every time I flash
• After a few minutes, if connected to my computer, the initial Huawei folder window will appear (the one with Docs, drivers, and “autorun”), and my phone will show up in adb devices list in command prompt. I can even use adb commands at this point. I really believe this means something.
• To get back into my phone, each time, I have to restore the system backup or flash the uninstaller zip.
I really want a number of xposed modules! My phone works 'fine' without them, but who roots their phone for merely 'fine'. Any suggestions are appreciated.
Click to expand...
Click to collapse
He is correct. You have to be on CM. EMUI will NOT allow closed to work. Flash the uninstaller zip.
icyboyice said:
Haven't heard of xposed working on stock lollipop EMUI . It does work on CM tho .
Click to expand...
Click to collapse
Thanks. I was worried that might be the case, a few days into my efforts, when I saw the "Xposed for CyanogenMod" guide posted a few days ago.
If that is the case, I suppose I have two additional questions:
1. Will installing CM mean another wipe and restore? (I'm certain I know the answer, which is of course "yes", but I thought I would ask all the same.)
I only ask because I hate having to re-do all my settings (3 email accounts in the google app, general device settings, etc), which neither the stock restore app or non-pro Titanium backup ever seems to put back.
Read through the "preview-cyanogenmod-mate-2 thread". Guess I'd have to bite the bullet.
2. Is CM worth it on its own? (And by worth it, I mean worth it for the HAM2... I can see CM's features with a quick search.)
I know I'll like being able to finally get Xposed, but I wonder if this will be an issue for getting updates like the recent B322. Or perhaps CM fixes that concern? I don't know much about it. My experience is limited to learning to root my phone for slightly more functionality on a few root apps.
Read through the "preview-cyanogenmod-mate-2 thread". Still not sure after reading about random restarts and battery issues (possibly from wake locks and/or google apps?).
Guess I'll just have to decide whether to try it after reading more comments in other threads about it.
Thanks for the help both of you!
neocortex08 said:
Thanks. I was worried that might be the case, a few days into my efforts, when I saw the "Xposed for CyanogenMod" guide posted a few days ago.
If that is the case, I suppose I have two additional questions:
1. Will installing CM mean another wipe and restore? (I'm certain I know the answer, which is of course "yes", but I thought I would ask all the same.)
I only ask because I hate having to re-do all my settings (3 email accounts in the google app, general device settings, etc), which neither the stock restore app or non-pro Titanium backup ever seems to put back.
Read through the "preview-cyanogenmod-mate-2 thread". Guess I'd have to bite the bullet.
2. Is CM worth it on its own? (And by worth it, I mean worth it for the HAM2... I can see CM's features with a quick search.)
I know I'll like being able to finally get Xposed, but I wonder if this will be an issue for getting updates like the recent B322. Or perhaps CM fixes that concern? I don't know much about it. My experience is limited to learning to root my phone for slightly more functionality on a few root apps.
Read through the "preview-cyanogenmod-mate-2 thread". Still not sure after reading about random restarts and battery issues (possibly from wake locks and/or google apps?).
Guess I'll just have to decide whether to try it after reading more comments in other threads about it.
Thanks for the help both of you!
Click to expand...
Click to collapse
For someone like you that doesn't have a lot of experience with custom Roms I would say wait till things are better.
Moody66 said:
For someone like you that doesn't have a lot of experience with custom Roms I would say wait till things are better.
Click to expand...
Click to collapse
Thanks! As excited as I am to have Xposed, I really like my EMUI (and don't want to pay for the play store one you suggested to others), I like B321s stability, and I like not changing settings often. So for now I'll wait and deal with not having trivialities like AdAway or playing Youtube in the background.
@neocortex08
You only need root on your phone to be able to install adaway. You don't need xposed.
For background playback of YouTube videos you may want to check this out
http://forum.xda-developers.com/showthread.php?t=2213945
They have a install method for those who are rooted and have xposed and those who don't .
Marshmallow for this device, keeps crashing as it is (com.android.phone, RIL). Getting the problem solved is easy, @puntoazul already written something like that, but I managed to get everything that has to be flashed in a single post.
Flash these files, in the next order, from top to bottom:
- A-GAPPS_6.0.1_09022016.zip - https://mega.nz/#!M99xiQbZ!fcclA9QDSXxxizsifu21MUbgMGsyRsNCCHPO4KrF5xQ (thanks to @puntoazul for packing it)
- APNFixer4CM13.zip - http://forum.xda-developers.com/attachment.php?attachmentid=3689957&d=1458482477 (thanks to @puntoazul for packing it)
- UNIVERSAL NFC DESTROYER - http://forum.xda-developers.com/attachment.php?attachmentid=3280610&d=1429942749 (thanks to @-CALIBAN666- for developing it), yeah, it's made for lollipop but works perfectly.
- Media.zip (codecs pack) http://forum.xda-developers.com/attachment.php?attachmentid=3680746&d=1457817927 (thanks to @EdwinMoq for packing it.)
When you're done, do a factory reset and reboot your device. Then, enjoy Marshmallow .
EDIT: Media.zip seems to be a mistyped step, I haven't found it and it wasn't needed to get a successful startup on my device.
EDIT: It seems like it's needed, anyways, I haven't found it, waiting for @EdwinMoq to answer.
EDIT: Added Media.zip, found at http://forum.xda-developers.com/opt...ogenmod-13-t3303671/post65803228#post65803228 ( @EdwinMoq 's post).
facuarmo said:
Marshmallow for this device, keeps crashing as it is (com.android.phone, RIL). Getting the problem solved is easy, @puntoazul already written something like that, but I managed to get everything that has to be flashed in a single post.
Flash these files, in the next order, from top to bottom:
- A-GAPPS_6.0.1_09022016.zip - https://mega.nz/#!M99xiQbZ!fcclA9QDSXxxizsifu21MUbgMGsyRsNCCHPO4KrF5xQ (thanks to @puntoazul for packing it)
- APNFixer4CM13.zip - http://forum.xda-developers.com/attachment.php?attachmentid=3689957&d=1458482477 (thanks to @puntoazul for packing it)
- UNIVERSAL NFC DESTROYER - http://forum.xda-developers.com/attachment.php?attachmentid=3280610&d=1429942749 (thanks to @-CALIBAN666- for developing it), yeah, it's made for lollipop but works perfectly.
- Media.zip (codecs pack) http://forum.xda-developers.com/attachment.php?attachmentid=3680746&d=1457817927 (thanks to @EdwinMoq for packing it.)
When you're done, do a factory reset and reboot your device. Then, enjoy Marshmallow .
EDIT: Media.zip seems to be a mistyped step, I haven't found it and it wasn't needed to get a successful startup on my device.
EDIT: It seems like it's needed, anyways, I haven't found it, waiting for @EdwinMoq to answer.
EDIT: Added Media.zip, found at http://forum.xda-developers.com/opt...ogenmod-13-t3303671/post65803228#post65803228 ( @EdwinMoq 's post).
Click to expand...
Click to collapse
Ive been experiencing the same problems you have, but i found my own alternate way. Since this phone isnt my daily driver, i used lucky patcher to remove the phone services app aka com.android.phone from the system.Everything is fixed, all stabilized and smooth. I still get crashing from phone and messaging storage,but no lag or stability issues. But ill try this anyway to try to completely remedy the crashing
As only two entries for Orange seem to be missing in the APN database: Does everyone need that fix because the APN list is totally corrupted by this, or only certain Orange customers?
Elite.101 said:
Ive been experiencing the same problems you have, but i found my own alternate way. Since this phone isnt my daily driver, i used lucky patcher to remove the phone services app aka com.android.phone from the system.Everything is fixed, all stabilized and smooth. I still get crashing from phone and messaging storage,but no lag or stability issues. But ill try this anyway to try to completely remedy the crashing
Click to expand...
Click to collapse
Okay, please let me know what happened when you're done.
lecorbusier said:
As only two entries for Orange seem to be missing in the APN database: Does everyone need that fix because the APN list is totally corrupted by this, or only certain Orange customers?
Click to expand...
Click to collapse
For a better stability, you must flash it. For example, running this ROM without this patch, the RIL keeps crashing, taking in mind that Movistar and Tuenti (a lesser know Argentina provider, a recently started provider), are not being detected.
I'll wait for the next build. Then probably use it as a Wireless AP, as there are huge problems resulting from the small data partition and Ram. I still hope that MMs z-buffer feature provides some solution. This whole mess started about half a year ago and getting worse, on the L9 and a similarly featured tablet with CM11, so it's not the rom's fault. The tablet has plenty of space on the data partition, however, but ram and SoC face similar problems.
My current wireless AP is an Iphone 4s with only 0,5GB Ram. And it's is still working reliably, no apps freezing and fcing, and I can access websites which will make Firefox on the L9 and said tablet quit every time.
All the affected apps seem to deal with HTML code and are supposed to use the system webview engine. Updating the Google webview engine is possible with CM12.1 and 13, but to no avail, only taking space on the data partition.
facuarmo said:
Okay, please let me know what happened when you're done.
Click to expand...
Click to collapse
Well. I tried it. No crashing at all with A-Gapps or Gapps mini
But I kept getting kernel panics,even while charging.So I reverted to my system modified nandroid backup in which I uninstalled Phone services aka com.Android. phone and disabled Phone and messaging storage app.
Elite.101 said:
Well. I tried it. No crashing at all with A-Gapps or Gapps mini
But I kept getting kernel panics,even while charging.So I reverted to my system modified nandroid backup in which I uninstalled Phone services aka com.Android. phone and disabled Phone and messaging storage app.
Click to expand...
Click to collapse
Follow this http://forum.xda-developers.com/showpost.php?p=65892603&postcount=395
As i have previously explained in original thread all of these files in a single go. with order defined
1) Goto TWRP recovery can also use new TWRP 3.0.2.0 (i have already installed marshmallow without any errors)
2) Wipe system, Cache and Davic
3) Flash rom
4) Flash Media.zip
5) Flash A-GAPPS_6.0.1_09022016.zip
6) Flash APNFixer4CM13.zip
7) If you have a p768 flash campatch
Also flashed NFC Destroyer so that on booting for the first time... i did'n encountered any error at all.. i have been using this ROM as my daily driver and never encountered any kernel panic or ant other error also i didn't faced any rotation problem. its working fine as it should be. Only thing i am concerned about is battery, it drains very fast, tweaking with kernel auditor didn't help me either. other then this i haven't faced any problem, everything is working fine, i'm able to install Xposed framework without any problem.. Great work......
I have also tried this with New TWRP Recovery.... worked like a charm
Elite.101 said:
Well. I tried it. No crashing at all with A-Gapps or Gapps mini
But I kept getting kernel panics,even while charging.So I reverted to my system modified nandroid backup in which I uninstalled Phone services aka com.Android. phone and disabled Phone and messaging storage app.
Click to expand...
Click to collapse
Can you tell me your real phone model? There're some hard incompatibilities between the P760 and the P769.
Codeplex said:
Follow this http://forum.xda-developers.com/showpost.php?p=65892603&postcount=395
As i have previously explained in original thread all of these files in a single go. with order defined
1) Goto TWRP recovery can also use new TWRP 3.0.2.0 (i have already installed marshmallow without any errors)
2) Wipe system, Cache and Davic
3) Flash rom
4) Flash Media.zip
5) Flash A-GAPPS_6.0.1_09022016.zip
6) Flash APNFixer4CM13.zip
7) If you have a p768 flash campatch
Also flashed NFC Destroyer so that on booting for the first time... i did'n encountered any error at all.. i have been using this ROM as my daily driver and never encountered any kernel panic or ant other error also i didn't faced any rotation problem. its working fine as it should be. Only thing i am concerned about is battery, it drains very fast, tweaking with kernel auditor didn't help me either. other then this i haven't faced any problem, everything is working fine, i'm able to install Xposed framework without any problem.. Great work......
I have also tried this with New TWRP Recovery.... worked like a charm
Click to expand...
Click to collapse
Well, ill try this.The way i tried this was in a different order, but pretty much i have the phone under control since i uninstalled com.android.phone aka Phone Services and disabled Phone and messaging storage.
but i guess ill try this.i need the exact correct order with NFC Destroyer in the list in order of flashing.
---------- Post added at 01:31 PM ---------- Previous post was at 01:30 PM ----------
facuarmo said:
Can you tell me your real phone model? There're some hard incompatibilities between the P760 and the P769.
Click to expand...
Click to collapse
I currently Have the LG-P769. T-Mobile variant
Elite.101 said:
Well. I tried it. No crashing at all with A-Gapps or Gapps mini
But I kept getting kernel panics,even while charging.So I reverted to my system modified nandroid backup in which I uninstalled Phone services aka com.Android. phone and disabled Phone and messaging storage app.
Click to expand...
Click to collapse
Flash in this order (works for me every time)
1) Goto TWRP recovery can also use new TWRP 3.0.2.0 (i have already installed marshmallow without any errors)
2) Wipe system, Cache and Davic
3) Flash rom
4) Flash Media.zip
5) Flash A-GAPPS_6.0.1_09022016.zip
6) Flash APNFixer4CM13.zip
7) NFC Destroyer
and reboot..
Codeplex said:
Flash in this order (works for me every time)
1) Goto TWRP recovery can also use new TWRP 3.0.2.0 (i have already installed marshmallow without any errors)
2) Wipe system, Cache and Davic
3) Flash rom
4) Flash Media.zip
5) Flash A-GAPPS_6.0.1_09022016.zip
6) Flash APNFixer4CM13.zip
7) NFC Destroyer
and reboot..
Click to expand...
Click to collapse
Alright. Ill try this right now.Ima do a backup first.
Codeplex said:
Flash in this order (works for me every time)
1) Goto TWRP recovery can also use new TWRP 3.0.2.0 (i have already installed marshmallow without any errors)
2) Wipe system, Cache and Davic
3) Flash rom
4) Flash Media.zip
5) Flash A-GAPPS_6.0.1_09022016.zip
6) Flash APNFixer4CM13.zip
7) NFC Destroyer
and reboot..
Click to expand...
Click to collapse
im still having problems. i just finished setting up and now i have a kernel panic.......reverting now
Elite.101 said:
Well, ill try this.The way i tried this was in a different order, but pretty much i have the phone under control since i uninstalled com.android.phone aka Phone Services and disabled Phone and messaging storage.
but i guess ill try this.i need the exact correct order with NFC Destroyer in the list in order of flashing.
---------- Post added at 01:31 PM ---------- Previous post was at 01:30 PM ----------
I currently Have the LG-P769. T-Mobile variant
Click to expand...
Click to collapse
The kernel panics that you're experiencing, are also being faced by most of the people who has tried the P760 build in the P769, please check the ROM @EdwinMoq 's post and download the special build for this model, and try again. Then, please tell me how it goes.
facuarmo said:
The kernel panics that you're experiencing, are also being faced by most of the people who has tried the P760 build in the P769, please check the ROM @EdwinMoq 's post and download the special build for this model, and try again. Then, please tell me how it goes.
Click to expand...
Click to collapse
Well specifically, i used the p769 version. i tried apn fixer, nfc destroyer and media.zip, but the problem persisted. so i just reverted back to my nandroid backup in which i uninstalled com.android.phone aka phone services and disabled phone and messaging storage.I have it stable this way without kernel panics and using gapps mini since this isnt my daily driver. My galaxy core prime is SMG360T1.
Elite.101 said:
Well specifically, i used the p769 version. i tried apn fixer, nfc destroyer and media.zip, but the problem persisted. so i just reverted back to my nandroid backup in which i uninstalled com.android.phone aka phone services and disabled phone and messaging storage.I have it stable this way without kernel panics and using gapps mini since this isnt my daily driver. My galaxy core prime is SMG360T1.
Click to expand...
Click to collapse
Hmmm... Idk, sorry. That's what I've learned from here, not much atm haha.
facuarmo said:
Hmmm... Idk, sorry. That's what I've learned from here, not much atm haha.
Click to expand...
Click to collapse
True.one thing I want fixed is the headphones problem where sound goes to speaker
Elite.101 said:
True.one thing I want fixed is the headphones problem where sound goes to speaker
Click to expand...
Click to collapse
That's quite strange, seems like a bad kernel. For me, using the P760 (in the P778g, Argentina, LATAM) works fine, both speakers (front and rear) and headphones.
When the headphone amp starts to clip/overdrive, this is accompanied by an unplugging event for the headphones. Artas' CM11 and CM12.1 are affected, too, but I could get my P760 to work with decent and stable sound output. While in Rammar's PA sound volume was even lower than with the stock rom(too low for even bothering to take the headphones with me) , CM12.1 is loudest. In order to not accidentially trip clipping and unplugging events, which will also reset volume to safety level, requiring to turn it up and clip again etc etc, Ilimited max volume to 80% in the Headset Button Controller app,which allows to control volume via headset mic button.
Hi everybody,
I'm using a Redmi Note2 Prime with MIUI 8 7.4.27 Beta (weekly). The phone was running very smooth, fast and reliable - battery life was always several days.
Yesterday I tried to root it using method 4 from here using recovery.img from TWRP 3.0.2-2.zip and UPDATE-SuperSU-v2.79-20161211114519.zip (SuperSU app was already installed). After several attempts (installed MI PC Suite twice until it worked on Win10) it finally worked.
I rooted since I wanted to try dual boot patcher and a MM ROM as second.
But after phone booted again it was nearly unusable. No smooth reaction I had to wait several seconds until screens changes when just scroll through them. Also apps and settings now need lots of time more before they start. Wifi is always turned off after reboot (while it was on during shutdown) and Google sync starts automatically after reboot while it is deactivated in all settings. Also background image of lock screen was changed. Google Play Services are now constantly crashing (need to click away these message requesters all the time) and Play Store does not even start anymore. Meanwhile I removed SuperSU app again since it never asked for granting root access while it was set to do so.
Installing a second ROM using Dual Boot Patcher finally also did not work (patching worked - installing not). Details are provided here.
I am still puzzled what happened here and do not have any clue since I rooted already several devices without any problems so far. Even this one some time ago IIRC.
Does anybody have any idea how I can get the phone back into a stable, usable mode? Do I have to completely reflash the MIUI8 ROM? Or do I have to use another SuperSU zip?
Any help is highly appreciated!
Thanks guys!
You can try wiping data/factory reset.
To easily install TWRP, you can use the Fastboot Install Method described here:
https://twrp.me/devices/xiaomiredminote2.html
Thanks. But doesn't this wipe/reset delete all apps and data (which I try to avoid)?
Would reflashing complete MIUI8 (version which I already have installed - without any system/data wipe) cure the problem?
TWRP app is already installed - but either TWRP recovery or SuperSU.zip crashed the Google Services (Play Services or even more) for whatever reason.
Does anybody have some idea why this might have happened? Maybe due to dalvik cache wipe which was requested?
I think that the phone become unusable a Google Services/Play Services is crashing because of wrong settings or data corruption.
That's why I said to do a factory reset.
You can try deleting just cache and data for Google Play Services and Google Play Store apps. Data are on cloud and should be restored automatically when needed.
Seems I got it working again - thanks to post #2. Used TWRP app to install another TWRP, afterwards I got a reboot loop. Then I deleted cache and dalvik cache and now everything works fine again!
Thank you!
Well Dual Boot still does not work but progressed a little bit further - but this is a different topic.
Try do delete your Rom (Backup all with Titanium backup before) and try to install latest Dev from mi-globe ! Prerootet and very smooth and good ROMs!
Thanks. But as said - got it working again (see above). The only thing which is not working is flashing a secondary ROM using Dual Boot Patcher (already opened another thread and posted it into the PATHCER thread - but seems nobody knows about some solution...).