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%).
Related
------------- SOLVED! --------------
Hello all,
First of all I want to say I'm pretty new to flashing ROMs etc.
Currently I'm at stock 4.3 Jellybean and I want to flash my SGS3 to the new CM 11 ROM.
I rooted my phone following this tutorial: vvvvvv.telefoonrooten.nl/samsung/samsung-galaxy-s3-root/ (sorry if its in Dutch, but it uses the CF-Root-SGS3-v6.3 and Odin).
After I rooted I copied both the CM11 ROM and GAPPS to my external SD, I went to recovery and tried to install the new custom ROM but I got an error (status 7) and it was aborted.
Also if I try to reboot it won't boot normally as it should be but it goes back to recovery mode automatically...
I fixed to get back to Jellybean by flashing the stock rom (unrooting?) it via Odin.
Anyone else got the exact same problem as I do and knows a solution to be able to flash CM 11?
Thanks in advance,
Steelbear
Steelbear said:
Anyone else got the exact same problem as I do and knows a solution to be able to flash CM 11?
Click to expand...
Click to collapse
please read the thirst post in a rom/kernel/whatever thread. and maybe if you havent done it already you should also read the stickies in general section.
FAQ (Read before post !!)
- If you obtain Error 7 when you tried to install ROM in CWM or TWRP
Install the latest version of CMW or TWRP
Click to expand...
Click to collapse
BTW latest philz touch recovery works too
Since you went back to stock and you already know how to root, I suggest you go to Play Store and download ROM Manager to help you install latest CWM recovery on your device.
Or you can simply go to CWM website, pick the version of the recovery for your phone and flash it via Odin.
Hope it helps.
Steelbear said:
Hello all,
First of all I want to say I'm pretty new to flashing ROMs etc.
Currently I'm at stock 4.3 Jellybean and I want to flash my SGS3 to the new CM 11 ROM.
I rooted my phone following this tutorial: vvvvvv.telefoonrooten.nl/samsung/samsung-galaxy-s3-root/ (sorry if its in Dutch, but it uses the CF-Root-SGS3-v6.3 and Odin).
After I rooted I copied both the CM11 ROM and GAPPS to my external SD, I went to recovery and tried to install the new custom ROM but I got an error (status 7) and it was aborted.
Also if I try to reboot it won't boot normally as it should be but it goes back to recovery mode automatically...
I fixed to get back to Jellybean by flashing the stock rom (unrooting?) it via Odin.
Anyone else got the exact same problem as I do and knows a solution to be able to flash CM 11?
Thanks in advance,
Steelbear
Click to expand...
Click to collapse
I had the same problem the fix is quite easy
flash the latest CWM 6.0.4.4 and flash cm11 it will work fine
Blackwolf10 said:
I had the same problem the fix is quite easy
flash the latest CWM 6.0.4.4 and flash cm11 it will work fine
Click to expand...
Click to collapse
Indeed it worked! I found it out myself yesterday. Went to the CWM site and downloaded the latest version (6.0.4.4.) and flashed it through Odin. But thanks for your input anyways (to all who replied) !
An alternative solution that I often use is to open the Updater Script in META-INF folder in the ROM's zip and delete first lines, where it gets device model as property.
Obviously it's an UNSAFE operation (because that lines avoid to install ROMs of other phone on mine) but when I'm sure that ROM I've downloaded is for my phone I do it and it works
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 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.
1) cm-14.0-20160914-UNOFFICIAL-onyx.zip, 2) cm-14.0-20160917-UNOFFICIAL-onyx.zip
These are the 2 cm14 zips that I tried to flash multiple times (using twrp 3.0.2.0). The flash was successful everytime. But no matter how hard I try, it just won't boot. Just stays stuck on the OnePlus logo for eternity. I just recovered my phone from a soft-brick (no OS, no Recovery) and still continuously trying since days to use cm14.
Please, if anyone can then PLEASE HELP!
amritanshu.sikdar said:
1) cm-14.0-20160914-UNOFFICIAL-onyx.zip, 2) cm-14.0-20160917-UNOFFICIAL-onyx.zip
These are the 2 cm14 zips that I tried to flash multiple times (using twrp 3.0.2.0). The flash was successful everytime. But no matter how hard I try, it just won't boot. Just stays stuck on the OnePlus logo for eternity. I just recovered my phone from a soft-brick (no OS, no Recovery) and still continuously trying since days to use cm14.
Please, if anyone can then PLEASE HELP!
Click to expand...
Click to collapse
Check the bootloader compatibilty of these roms, if they r for the mm bootloader it ll not boot untill u upgrade ur bootloader, check the threads from wer u hv downloaded this...
amritanshu.sikdar said:
1) cm-14.0-20160914-UNOFFICIAL-onyx.zip, 2) cm-14.0-20160917-UNOFFICIAL-onyx.zip
These are the 2 cm14 zips that I tried to flash multiple times (using twrp 3.0.2.0). The flash was successful everytime. But no matter how hard I try, it just won't boot. Just stays stuck on the OnePlus logo for eternity. I just recovered my phone from a soft-brick (no OS, no Recovery) and still continuously trying since days to use cm14.
Please, if anyone can then PLEASE HELP!
Click to expand...
Click to collapse
Most Roms now require you too flash OOS 3.1.3 first. Like mentioned above bootloader issue.
Exodusche said:
Most Roms now require you too flash OOS 3.1.3 first. Like mentioned above bootloader issue.
Click to expand...
Click to collapse
I already flash the OOS 3, but still this problem continues.
File name: OnePlusXOxygen_14_OTA_015_all_201608181615_e03d2112e8ad4bff
Is there any other way how I can manually upgrade my bootloader? That would really help.
amritanshu.sikdar said:
I already flash the OOS 3, but still this problem continues.
File name: OnePlusXOxygen_14_OTA_015_all_201608181615_e03d2112e8ad4bff
Is there any other way how I can manually upgrade my bootloader? That would really help.
Click to expand...
Click to collapse
check out this thread http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
amritanshu.sikdar said:
I already flash the OOS 3, but still this problem continues.
File name: OnePlusXOxygen_14_OTA_015_all_201608181615_e03d2112e8ad4bff
Is there any other way how I can manually upgrade my bootloader? That would really help.
Click to expand...
Click to collapse
I use Oxygen_14_OTA_18_all but there's a couple files posted on the bootloader upgrade threads that allow you not too flash the whole firmware just the partions you need to upgrade.
i am having same issue i was on oxygenos 3.1.3 firmware when i started to flash nogut roms every nogut rom works except cm. i flashed official cynogenmod 14.1 thinking that problem must have been solved but it wont boot it just shows oneplus logo. i have waited for 30 minutes but nothing happened if something worked out for you please tell me.
Well I've looked around XDA for soultion and this is it.
CM 14 has some Kernel problems, so only what you have to do is just install new kernel as Arsenic or Black Reactor kernel
I was running the new bootloader on cm13 nightlies and couldn't get it to boot either.
Even after a full wipe and reflash with v7 gapps
Gave up in the end and went back to the last cm13 Nightly
flash arsenic kernel after flashing rom and gapps it will boot. Read the posts in ashwin's official cm 14.1 thread.
Flash Black Reactor (recommended) or Arsenic Kernel.
The zip files that you have for CM are the unofficial ones. So I guess they're from Sarthak Narang. Or at least one of them. Those ROMs require the older bootloader to function. So if you have the newer bootloader, it won't work.
Hi, I am trying to install cynogenmod or mokee rom and the device always gets stuck at cyno/mokee logo. it never goes beyond that. tried to wait for half an hour(waited for one hour twice).
Here is what I am doing:
I used TWRP but it wasnt working so i installed CWM, in both the recoveries I was wiping everything except sd card storage as my zip files were in the card. after that i flashed zip files(ROM & GAPPS). after that i rebooted to system. Am I doing it wrong? I am currently on 4.4.4 stock rom. Need help.
Thank you.
No one to help?
How can TWRP not work on your device? Install again TWRP via adb.
Flash latest twrp 3.0.2 and try
rian_tama said:
How can TWRP not work on your device? Install again TWRP via adb.
Click to expand...
Click to collapse
Rajendran Rasa said:
Flash latest twrp 3.0.2 and try
Click to expand...
Click to collapse
The problem wasn't with the recovery and I wasn't doing anything wrong. It was really too bad to know that the rom version I was installing had a bootloop bug in it. So I had tried two previous versions but they too had the same bug. And unfortunately I tried CONTINUOUSLY for two long days to install those same bugged ROMS as if God has put me in frustration mode. Tech fooled me right, lol.
Grab the November 8 version of Cyanogemod. There are issues with the newer updates.