Just flashed 6.0.1 and am now seeing the battery percentage in values way above 100%. For example, my battery percentage is at 4,110%. Is anyone else seeing this?
Yeah I'm getting the same issue also.
Sent from my Nexus 9 using Tapatalk
Is this happening on a stock and unrooted device ???
Mine is stock, rooted.
Sent from my Nexus 9 using Tapatalk
Every report I've read about this issue is due to someone not running the stock kernel. Does this apply to you ?
Reverting back to the stock kernal or installing a kernal that's been updated to support 6.0.1 seems to have solved the problem.
oias.heeda said:
Mine is stock, rooted.
Sent from my Nexus 9 using Tapatalk
Click to expand...
Click to collapse
kernal says 3.10.40-g909db78
[email protected] #1
fri aug 28 21:16:30 UTC 2015
before updating I was on elementalx
This has to do with the boot.img. I'm using chainfires modified one, but it is for MRA58N. Does anyone have the modified one for MMB29K? I might have to look into modifying myself but I've not done this before...
the.teejster said:
Every report I've read about this issue is due to someone not running the stock kernel. Does this apply to you ?
Reverting back to the stock kernal or installing a kernal that's been updated to support 6.0.1 seems to have solved the problem.
Click to expand...
Click to collapse
Makes sense. My N6 was doing this with a rooted kernel, and the problem went away when I flashed back to stock.
According to most accounts of this problem, the user forgot to flash the appropriate boot.img, vendor.img, or system.img before flashing the kernel/ROM.
So I have a solution for my case!
I was originally on Stock 6.0 unencrypted and rooted, and running a custom Kernel (ElementalX). Then I flashed the stock 6.0.1 System.img and encountered this exact problem, and even updating my custom kernel to the latest (and supported) version did not fix things.
So this is what I did:
- Flash the stock 6.0.1 Boot.img (DON'T boot into System after this or it may Force-Encrypt, if you care about that).
- RE-Flash the stock 6.0.1 System.img
- Boot into your Custom recovery (TWRP for me)
- Flash SuperSU v2.61 - this is an experimental version but seems to work (I also had to ADB Push this zip file since I didn't want to boot into System yet)
- Flash the latest EX Kernel N9-4.05 (Also ADB Pushed this zip)
- Reboot to System
And that's it! all working back to normal now. I realise that most people won't need to go through all that trouble, but if you're like me and didn't want to do a clean install, or wanted to remain rooted/unencrypted/using a custom kernel, then this might help you!
Neptaliuss said:
So I have a solution for my case!
I was originally on Stock 6.0 unencrypted and rooted, and running a custom Kernel (ElementalX). Then I flashed the stock 6.0.1 System.img and encountered this exact problem, and even updating my custom kernel to the latest (and supported) version did not fix things.
So this is what I did:
- Flash the stock 6.0.1 Boot.img (DON'T boot into System after this or it may Force-Encrypt, if you care about that).
- RE-Flash the stock 6.0.1 System.img
- Boot into your Custom recovery (TWRP for me)
- Flash SuperSU v2.61 - this is an experimental version but seems to work (I also had to ADB Push this zip file since I didn't want to boot into System yet)
- Flash the latest EX Kernel N9-4.05 (Also ADB Pushed this zip)
- Reboot to System
And that's it! all working back to normal now. I realise that most people won't need to go through all that trouble, but if you're like me and didn't want to do a clean install, or wanted to remain rooted/unencrypted/using a custom kernel, then this might help you!
Click to expand...
Click to collapse
Worked for me as well!
This worked perfect for me. I didn't need to reflash the system image either. Just the stock boot.img, then supersu, then ex kernel. All from within TWRP. Then reboot. That battery percentage was driving me nuts though. Thanks.
Neptaliuss said:
So I have a solution for my case!
I was originally on Stock 6.0 unencrypted and rooted, and running a custom Kernel (ElementalX). Then I flashed the stock 6.0.1 System.img and encountered this exact problem, and even updating my custom kernel to the latest (and supported) version did not fix things.
So this is what I did:
- Flash the stock 6.0.1 Boot.img (DON'T boot into System after this or it may Force-Encrypt, if you care about that).
- RE-Flash the stock 6.0.1 System.img
- Boot into your Custom recovery (TWRP for me)
- Flash SuperSU v2.61 - this is an experimental version but seems to work (I also had to ADB Push this zip file since I didn't want to boot into System yet)
- Flash the latest EX Kernel N9-4.05 (Also ADB Pushed this zip)
- Reboot to System
And that's it! all working back to normal now. I realise that most people won't need to go through all that trouble, but if you're like me and didn't want to do a clean install, or wanted to remain rooted/unencrypted/using a custom kernel, then this might help you!
Click to expand...
Click to collapse
Related
Would the following work as a way to try out, for example Cyanogenmod 10. I am currently running a 4.1.2 install (pretty much stock just rooted/cwm via Philz as per the tutorial). I have a complete backup made via Philz recovery of this rom along with the kernel (which I believe is still stock from that) and efs.
1) Install a custom kernel (eg. dorimanx 9.x?) via the Philz recovery.
2) Install cm-10.2-20140102-NIGHTLY-i9100.zip.
3) To return to the original rom, reflash the original kernel (with whatever CWM is included in dorimanx) - then reflash the backed up rom via the same recovery?
I hope this is clear enough a question.
I believe you have to flash a stock rom through Odin, to return to complete stock. Just flashing a stock kernel isn't enough, and is surely not going to work (so don't do it).There are also tutorials how to remove the yellow triangle afterwards.
Please correct me if I'm wrong
Donnie Sins said:
I believe you have to flash a stock rom through Odin, to return to complete stock. Just flashing a stock kernel isn't enough, and is surely not going to work (so don't do it).There are also tutorials how to remove the yellow triangle afterwards.
Please correct me if I'm wrong
Click to expand...
Click to collapse
This is the part I'm most unsure of. Ideally I'm trying to figure out the process that lets me go from CM10.2 (and whatever recovery) to the point I am running the backed up rom rooted with PhilZ-cwm6-XWLSW-XEU-5.06.1-signed.zip again. Very confused on how to do so.
TopherBrink said:
This is the part I'm most unsure of. Ideally I'm trying to figure out the process that lets me go from CM10.2 (and whatever recovery) to the point I am running the backed up rom rooted with PhilZ-cwm6-XWLSW-XEU-5.06.1-signed.zip again. Very confused on how to do so.
Click to expand...
Click to collapse
Topher,
If you have rooted and cwm via philz, you already have a modified kernel installed. I believe the philz-cwm6 should be as close to stock kernel with the CWM incorporated. You don't need to add another kernel, because it will be replaced when you install the custom ROM. You should just be able to flash the cm10.2 via philz or via odin. You can then flash the dormanix kernel if you want - can't comment on that kernel - or if it has cwm included.
I would also suggest that you consider backing up you /efs folder (one with you imei information etc) prior to flashing any custom roms. People have been using hcKtool to do the backups and also an actual copy as well.
Depending on the custom rom, you may have connection problems with your network. So you may want to consider keeping a copy of your modem.bin file from your stock rom handy in case you need to flash onto the custom rom.
If you want to go back to stock, then you just need to flash the stock rom - you can check sammobile website for your stock rom or use the backup that you made.
I should point out that I have yet to do any of the above - I gathered this from reading the forums. Some more experienced forum users can add corrections. I rooted my phone a couple of months ago and now considering installing custom rom in the next couple of months.
Thanks.
if u flash a custom rom (cm10.2 for example), it already included kernel as well. so if u want to try out other custom kernel, i can flash it after you are done flashing a custom rom but make sure it is compatible with your android version. (u cant use custom kernel that not support android 4.3 with a custom rom running android 4.3)
I had little issue moving up to 4.0.4 so I don't have to worry about the EMMC erase bug, but I'm realizing I have no way to get up further.
Everything seems to require CWM or a version of TWRP that has no compatible kernels with 4.0.4 best I can do is Siydah and like 6.0.1.2 and looks like CWM but its rather sparse on the details.
Final edit, I found a much better solution.
It does not seem as though you can flash a upgraded kernel from the CWM interface itself and reboot reliably failed on multiple kernels.
Solution
Download mobile Odin
Download the 4.4 ROM of your choice (compatable)
Gapps too stick them all somewhere you can find them (i just leave em in downloads)
Download and flash CWM 6.0.4.4 for Kitkat i777.. no clue where I found it wasn't on XDA though.
Turn the phone off (if you reboot and don't reboot too recovery you get a loop)
Boot to recovery (if you get in a loop here pull the battery THEN boot to recovery)
Now you'll notice your not on your old version of CWM anymore.
Install your ROM and Gapps.
Boot to rom
Boot back to recovery Now your once again on a different version of CWM.
I strongly advise cleaning everything up and installing it again I had some issue until I did.
GL to anyone who finds this thread. If there seems to be a need I could rewrite it with a better title.
TheEgonSpengler said:
I had little issue moving up to 4.0.4 so I don't have to worry about the EMMC erase bug, but I'm realizing I have no way to get up further.
Everything seems to require CWM or a version of TWRP that has no compatible kernels with 4.0.4 best I can do is Siydah and like 6.0.1.2 and looks like CWM but its rather sparse on the details.
Final edit, I found a much better solution.
It does not seem as though you can flash a upgraded kernel from the CWM interface itself and reboot reliably failed on multiple kernels.
Solution
Download mobile Odin
Download the 4.4 ROM of your choice (compatable)
Gapps too stick them all somewhere you can find them (i just leave em in downloads)
Download and flash CWM 6.0.4.4 for Kitkat i777.. no clue where I found it wasn't on XDA though.
Turn the phone off (if you reboot and don't reboot too recovery you get a loop)
Boot to recovery (if you get in a loop here pull the battery THEN boot to recovery)
Now you'll notice your not on your old version of CWM anymore.
Install your ROM and Gapps.
Boot to rom
Boot back to recovery Now your once again on a different version of CWM.
I strongly advise cleaning everything up and installing it again I had some issue until I did.
GL to anyone who finds this thread. If there seems to be a need I could rewrite it with a better title.
Click to expand...
Click to collapse
Always remember that when you flash a ROM, that you typically get the Recovery that is tied to the Kernel contained in that ROM. So, you flashed the Kernel, got Recovery A, then you flashed the ROM and got Recovery B. A KK Kernel can be flashed independent of a KK ROM, and will add different/additional/improved functionality, depending on the dev, but it also contains it's own Recovery in most cases.
desteele said:
Always remember that when you flash a ROM, that you typically get the Recovery that is tied to the Kernel contained in that ROM. So, you flashed the Kernel, got Recovery A, then you flashed the ROM and got Recovery B. A KK Kernel can be flashed independent of a KK ROM, and will add different/additional/improved functionality, depending on the dev, but it also contains it's own Recovery in most cases.
Click to expand...
Click to collapse
"Everything seems to require CWM or a version of TWRP that has no compatible kernels with 4.0.4 best I can do is Siydah and like 6.0.1.2 and looks like CWM but its rather sparse on the details. "
Yes I know, thanks for the advice.
TheEgonSpengler said:
"Everything seems to require CWM or a version of TWRP that has no compatible kernels with 4.0.4 best I can do is Siydah and like 6.0.1.2 and looks like CWM but its rather sparse on the details. "
Yes I know, thanks for the advice.
Click to expand...
Click to collapse
Oh, sorry...sounded like you expected to find the latest recoveries on JB kernels. My bad.
desteele said:
Oh, sorry...sounded like you expected to find the latest recoveries on JB kernels. My bad.
Click to expand...
Click to collapse
Nah, you just can't install the latest ROM with an older recovery.
So if you want to go up you have to do the little dance I described above. (Yes I know certain walkthroughs indicate you can do the first step in recovery, I simply found that to not be true and gained me only bootloops and the joys of reflashing stock then reinstalling a updated-er version so I could try again.)
wil this work in my situation
Quick question.. am on:
android 4.1.2
Shostock v 3.0.2
my cwm v6.0.2.7.
I want to move for a slimmer kitkat rom..
I download the system update for OnePlus x oxygen os 2.2.1. But when I reboot it for installation, there's a message "installation failed". What's wrong with the file? It seems to download everything properly. But error occurs during installation.
Is it rooted? Which recovery r u using? Twrp or stock?
Not rooted
itsmelutfor said:
Is it rooted? Which recovery r u using? Twrp or stock?
Click to expand...
Click to collapse
What have you already modded in the original installation? If your system was stock the update wouldn't fail. Please be more specific so people can help you. If you've kingrooted or flashed twrp, the update will fail...
I don't know about the OP, but I had the same issue when I tried to OTA to OOS 2.2.1. I applied all my hacks through TWRP but always booting TWRP by ADB and never flashing TWRP to the phone. So, I have unlocked bootloader, Developer settings, stock recovery, Boeffla, CameraHAL. With this, OOS 2.2.1 OTA gave me "installation failed". Shouldn't it have worked since I was still in stock recovery?
Thinking it could be the kernel I then tried to restore the original kernel by going to a TWRP backup I made immediately before flashing Boeffla, and restoring boot.img. To my surprise, I then lost all Wi-Fi functionality.
In the end, I downloaded the full OOS 2.2.1 ROM from OnePlus and dirty-flashed it, stacking it before the newest versions of Boeffla and CameraHAL. Phone is working OK, no bugs noticed so far.
I still haven't flashed TWRP nor rooted the phone. In my configuration, what's stopping OTA from working? It would be nice to have OOS3 OTA, since I still don't trust the backups I'm making.
Sent from my ONE E1003 using XDA Labs
TiagoJSilva said:
I don't know about the OP, but I had the same issue when I tried to OTA to OOS 2.2.1. I applied all my hacks through TWRP but always booting TWRP by ADB and never flashing TWRP to the phone. So, I have unlocked bootloader, Developer settings, stock recovery, Boeffla, CameraHAL. With this, OOS 2.2.1 OTA gave me "installation failed". Shouldn't it have worked since I was still in stock recovery?
Thinking it could be the kernel I then tried to restore the original kernel by going to a TWRP backup I made immediately before flashing Boeffla, and restoring boot.img. To my surprise, I then lost all Wi-Fi functionality.
In the end, I downloaded the full OOS 2.2.1 ROM from OnePlus and dirty-flashed it, stacking it before the newest versions of Boeffla and CameraHAL. Phone is working OK, no bugs noticed so far.
I still haven't flashed TWRP nor rooted the phone. In my configuration, what's stopping OTA from working? It would be nice to have OOS3 OTA, since I still don't trust the backups I'm making.
Sent from my ONE E1003 using XDA Labs
Click to expand...
Click to collapse
If you modify even a single bit in stock rom and revert back, updates are definitely going to fail.
The only solution to receive OTAs is flashing stock recovery with stock rom with locked bootloader.
Or you can manually flash OTAs using TWRP.
I made several backups of my stock rom before testing mods, but when I restored and tried to perform OTAs, it always failed while installing.
prabhat.singh.836 said:
If you modify even a single bit in stock rom and revert back, updates are definitely going to fail.
The only solution to receive OTAs is flashing stock recovery with stock rom with locked bootloader.
Or you can manually flash OTAs using TWRP.
I made several backups of my stock rom before testing mods, but when I restored and tried to perform OTAs, it always failed while installing.
Click to expand...
Click to collapse
You just need to wipe cache from the stock recovery in order to install the ota updates , customer care babe told me
---------- Post added at 03:44 AM ---------- Previous post was at 03:43 AM ----------
Hello guys, I unlocked my bootloader...now would I get the ota updates? It's not rooted and on stock ROM.
If no then please tell me how to revert back to locked bootloader.
TiagoJSilva said:
I don't know about the OP, but I had the same issue when I tried to OTA to OOS 2.2.1. I applied all my hacks through TWRP but always booting TWRP by ADB and never flashing TWRP to the phone. So, I have unlocked bootloader, Developer settings, stock recovery, Boeffla, CameraHAL. With this, OOS 2.2.1 OTA gave me "installation failed". Shouldn't it have worked since I was still in stock recovery?
Thinking it could be the kernel I then tried to restore the original kernel by going to a TWRP backup I made immediately before flashing Boeffla, and restoring boot.img. To my surprise, I then lost all Wi-Fi functionality.
In the end, I downloaded the full OOS 2.2.1 ROM from OnePlus and dirty-flashed it, stacking it before the newest versions of Boeffla and CameraHAL. Phone is working OK, no bugs noticed so far.
I still haven't flashed TWRP nor rooted the phone. In my configuration, what's stopping OTA from working? It would be nice to have OOS3 OTA, since I still don't trust the backups I'm making.
Sent from my ONE E1003 using XDA Labs
Click to expand...
Click to collapse
swatidixit710 said:
I download the system update for OnePlus x oxygen os 2.2.1. But when I reboot it for installation, there's a message "installation failed". What's wrong with the file? It seems to download everything properly. But error occurs during installation.
Click to expand...
Click to collapse
deathaddder said:
You just need to wipe cache from the stock recovery in order to install the ota updates , customer care babe told me
---------- Post added at 03:44 AM ---------- Previous post was at 03:43 AM ----------
Hello guys, I unlocked my bootloader...now would I get the ota updates? It's not rooted and on stock ROM.
If no then please tell me how to revert back to locked bootloader.
Click to expand...
Click to collapse
I have tried wipe cache method and doesn't works at all if you have rooted your phone and unrooted back.
And the OTA should work even with unlocked bootloader, if you have not rooted your phone before.
If you want to lock your bootloader again, just follow these steps,
1. Goto Settings -> Developer options
2. OEM unlocking -> turn it off
Error in installation of OxygenOS2.2.1
Having same issue, I doubt why it is not getting installed. Not rooted and not even touchted the kernel. Is it a bug or it requires a flash ?
Ankit_Lal said:
Having same issue, I doubt why it is not getting installed. Not rooted and not even touchted the kernel. Is it a bug or it requires a flash ?
Click to expand...
Click to collapse
Did you try to flash the full rom zip here?
http://downloads.oneplus.net/2016-04-20/opx/OnePlus_X_OxygenOS_2.2.1-X/
Cannot update to Oxygen OS 2.2.1
Yup ! I tried the same but it fails repetedly
Is there anyone who is facing the same issue ?
Ankit_Lal said:
Yup ! I tried the same but it fails repetedly
Is there anyone who is facing the same issue ?
Click to expand...
Click to collapse
I have the same problem. Brand new phone, out of box, Oxygen version 2.1.0.
Hi,
I'm not allowed to post in the developer forum.
I tried to install the dark sense 1.2.2 kernel on the latest stock rom. The phone booted normal and it did not take a long time to boot. However the camera has a weird reddish tint... (maybe wrong installation).
Is it possible to use the dark sense kernel on the latest stock rom?
Phone info:
Latest stock 20170112 (rooted)
recovery: TWRP 3.0.2-8
Kind regards
Hexyl said:
Hi,
I'm not allowed to post in the developer forum.
I tried to install the dark sense 1.2.2 kernel on the latest stock rom. The phone booted normal and it did not take a long time to boot. However the camera has a weird reddish tint... (maybe wrong installation).
Is it possible to use the dark sense kernel on the latest stock rom?
Phone info:
Latest stock 20170112 (rooted)
recovery: TWRP 3.0.2-8
Kind regards
Click to expand...
Click to collapse
How did you install TWRP in that ROM? For me it's impossible
Fran Montero said:
How did you install TWRP in that ROM? For me it's impossible
Click to expand...
Click to collapse
See this forum:
https://forum.xda-developers.com/el...nofficial-twrp-elephone-p9000-t3426678/page14
post #133
Post from floydart:
I installed the 20170112 then TWRP 3.0.2.8 then flashed SU and successfully rooted. Decided to go back to CM13 FV3 though as I couldn't get Gravity Box to work
I followed the exact same steps as posted in that URL. First stock rom (and booted in stock rom). Then flashed only TWRP 3.0.2-8 with flashtools and then SU.
Hexyl said:
See this forum:
https://forum.xda-developers.com/el...nofficial-twrp-elephone-p9000-t3426678/page14
post #133
Post from floydart:
I installed the 20170112 then TWRP 3.0.2.8 then flashed SU and successfully rooted. Decided to go back to CM13 FV3 though as I couldn't get Gravity Box to work
I followed the exact same steps as posted in that URL. First stock rom (and booted in stock rom). Then flashed only TWRP 3.0.2-8 with flashtools and then SU.
Click to expand...
Click to collapse
Did the same but for me didn't work when flashing TWRP, Windows 10 show a preloader error
Fran Montero said:
Did the same but for me didn't work when flashing TWRP, Windows 10 show a preloader error
Click to expand...
Click to collapse
Weird, I also use Windows 10. Have no errors
Does the new stock rom have a different lk and preloader than the previous stock rom?
Fast charge (PE+) does not work properly in the latest stock ROM (I think). Charging takes almost 110 minutes. In other ROMs with custom kernels, charging takes about 1 hour (Started from 5%).
[SOLVED]
Recently I've installed Oreo AOSP, I wanted to return flashing from TWRP but stucks on bootanimation, I tried with XGen but the problem persists
Also I tried through flashhtool but the program it doesn't detect my phone, also I tried with Emma, the process was completed correctly but when I boot up the phone the custom ROM is there
Im going to try flashing the Loire kernel through TWRP, at least I want to move to LineageOS
Flash a stock based custom rom (XGEN or Persian Rom) - dirty or clean /system is your choice. If you want extra then flash the clean patched kernel in the rooting thread (we actually don't need this)
Note that the phone won't boot properly and will bootloop, but now the phone will be recognize as F5121/22 in flashtool so you can flash the rom as normal.
n0k0m3 said:
Flash a stock based custom rom (XGEN or Persian Rom) - dirty or clean /system is your choice. If you want extra then flash the clean patched kernel in the rooting thread (we actually don't need this)
Note that the phone won't boot properly and will bootloop, but now the phone will be recognize as F5121/22 in flashtool so you can flash the rom as normal.
Click to expand...
Click to collapse
Already I solved the problem, i flashed the AOSP kernel in Existenz N, then I can boot as usual, however thanks for your answer