Yesterday, I flashed Cyanogenmod 13 on my OPX. It is working fine, but then I am noticing that battery life is not great. I had not taken any backup of the stock ROM (Oxygen OS).
So I checked this link to revert to Oxygen OS. This site mentions 2 links to download the stock recovery and ROM:
Code:
https://theunlockr.com/2016/02/17/how-to-unroot-the-oneplus-x/
Now the following link also mentions links to download the same, which I believe the files in the link below are the latest ones.
Code:
http://downloads.oneplus.net/2016-04-02/opx/OnePlus_X_OxygenOS_2.2.1/
My question is if I download the stock ROM from this link:
Code:
https://s3.amazonaws.com/oxygenos.oneplus.net/055/OnePlusOxygen_14_OTA_010_all_201604021001_54d6bba8f7d84502.zip
will I be able to revert to stock ROM?
Yes, you can revert back to stock using the above file from Oneplus.net
Flash the Stock Recovery from the same page first, it's not necessary, but twrp gave me an error while flashing 2.2.0
This is 2.2.1, but it doesn't hurt to take an extra precaution.
Related
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
I'm confused on a few things,
I once had Cyanogenmod with Marshmellow, after updating to an OTA Cyanogen version I got stuck into bootloop and for some reason I couldn't get back to Cyanogenmod in TWRP recovery and the only nandroid backup was B331 which is only Lollipop Stock which i'm currently on. Now I just want to start from scratch and get back to latest Cyanogenmod with Marshmellow. Where do I start? I have Current Build KIW-L24C567B331 that is currently Lollipop and I wiped my internal SD. When I try and look for Stock OTA updates it says no updates, the update client has NEVER worked on this phone. I have currently TWRP recovery on it. Do I have to go to a certain build to get back to Marshmellow? then go to Marshmellow Stock then to Cyanogenmod?
I tried following this guide: http://forum.xda-developers.com/honor-5x/how-to/guide-kiw-l24-to-stock-t3318268 but I don't understand which stock I should go to and the instructions aren't very clear (maybe i'm just dumb)
Another question: for each Custom ROM I install do I go back to a certain stock build then flash the custom ROM?
Much help appreciated,
Thanks
Are you in stock Marshmallow before you flashed CM?
Sent from my honor 5X using XDA Labs
if you are saying that you have twrp, with lollipop emui on, due to twrp, you will never get any update,
since you want marshmallow, i think you need to be upgraded to marshmallow firmware,
to do so, you need to download the marshmallow build, generally the b331 firmware in the link you provided...(dated:10/07/2016)
go ahead and download that firmware and follow the procedure, in the end, you will be left with the marshmallow emui build with stock recovery on (eligible for ota and warranty )...
now, since your bootloader is still unlocked(i guess), you can reboot to bootloader and fastboot twrp recovery(latest twrp is recomended)..
and now, you are pretty much good to go.... download latest cm13 nightly and install... enjoy
please do perform the steps carefully:good:
AND NO, YOU DO NOT NEED TO GO BACK TO A STOCK BUILD TO FLASH CERTAIN CUSTOM ROMS
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%).
Hi.I just saw that it is possible to install stock ROM via custom recovery,just by editing it.
Here is the video I saw: https://m.youtube.com/watch?v=ZqOE5qtFKDk.
Basically,I want to try this on my Huawei Y6 SCL-L01,which now it is running CM 12.1 with TWRP 3.0.2 and SuperSU(forgot the version).
My questions are:
1.Will it work?
2.Will it reinstall stock recovery,unroot and relock bootloader?
3.Will it work fine after installing stock rom?(when I restored nandroid with TWRP it wouldn't recognise my SIM Card.)
Any advices?I really want to get back to stock.
EDIT: Here is the download for Stock ROM : http://consumer.huawei.com/nl-en/support/downloads/detail/index.htm?id=77268
If I have lineageos 16 installed, would I be able to just clean flash any of the following modified stock rom through twrp and get the phone working? Link:
https://mi-globe.com/miui-firmware-rom-builder-features/74/
Do i need to follow any other procedure?
short answer yes!
because (long answer) the link you mentioned its modified stockrom only and gives you more control to add/remove componant! it comes with its own vendor firmware!
however ALWAYS TAKE BACKUP!
Just tried this and it works great was on custom ROM but the luncher kept crashing and it became unstable but now back on stock and loving it..........