Hi there,
I have a Chinese OnePlus, achieved to finally install a western cyanogen ROM in early july and rooted. I now have Latest bacon release on (nightly 24.08.2014) from cyanogen website downloads.
Problem: I can't flash or sideload any of the stock roms available even the one with script update, I have TWRP 2.7.1.1. It fails every time. I only can flash certain roms like the ones available on cyanogen downlaods. Don't know why.
I had different error messages trying to flash like 'can't flash on incompatible data' and others...
I wiped everything lots of times before flashing.
2 questions:
1/ How can I flash stock roms on my phone?
2/ What improvements latest nightly bacon rom on cyanogen as I still experience ghost on touchscreen?
Thanks for your help
Firstly, when you refer to stock ROM, I am assuming that you mean CM11S XNPH series--this series differs from the CM11 nightlies that you mentioned. CM11S does not have nightlies and are only available in OTAs.
If you plan on staying on nightlies then you can only flash the zips here http://download.cyanogenmod.com/?device=bacon&type=nightly
If you plan on going to "stock ROM" (CM11S) then you need to flash https://cyngn.com/products/oneplusone/ using fastboot (or find a full OTA zip on the forums)
Hi Zephik and thanks for your answer. I do refer to latest nightly downloads on official cyanogen website.
I would be glad to stay with nightlies but I experiment some bugs with touchscreen and other things.
I tried to update with CM11S downloaded from the official link you provided but it fails every time.
I tried it via TWRP, sideload and normal load but without success.
You mentioned fastboot but I didn't try via fastboot and I don't know how to do it actually, I only went there to flash TWRP recovery.
Can you tell me what adb command I could use via fastboot to update CMS11?
If it didn't work via twrp, why would it work via fastboot?
Thanks
zephiK said:
Firstly, when you refer to stock ROM, I am assuming that you mean CM11S XNPH series--this series differs from the CM11 nightlies that you mentioned. CM11S does not have nightlies and are only available in OTAs.
If you plan on staying on nightlies then you can only flash the zips here
If you plan on going to "stock ROM" (CM11S) then you need to flash using fastboot (or find a full OTA zip on the forums)
Click to expand...
Click to collapse
Roberto2001 said:
Hi Zephik and thanks for your answer. I do refer to latest nightly downloads on official cyanogen website.
I would be glad to stay with nightlies but I experiment some bugs with touchscreen and other things.
I tried to update with CM11S downloaded from the official link you provided but it fails every time.
I tried it via TWRP, sideload and normal load but without success.
You mentioned fastboot but I didn't try via fastboot and I don't know how to do it actually, I only went there to flash TWRP recovery.
Can you tell me what adb command I could use via fastboot to update CMS11?
If it didn't work via twrp, why would it work via fastboot?
Thanks
Click to expand...
Click to collapse
Those bugs with touchscreens etc should be fixed, not all of them but the majority of them. They're in the official CM11S as well. Its just something you'll have to deal with until its fully fixed.
Also you are still confusing me, you say latest nightly and then you mention CM11S. There are no CM11S nightlies, the only nightlies there are is CM11. CM11 and CM11S are two different things, they're very similar but in terms of compatibility they are not the same.
The CM11S zip is not a TWRP flashable zip, thats why the .zip says -fastboot in it. You need to do fastboot to flash this (refer to bottom link), but then you mention that you want nightlies? So I'm getting confused on what you want exactly.
A guide to fastboot http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 THIS IS FOR CM11S not nightlies.
Again, CM11S nightlies do not exist! Its either CM11S or CM11 nightlies. This is a big emphasis since you're confused on what you want.
If you want CM11 nightlies, just simply wipe in TWRP and flash http://download.cyanogenmod.com/?device=bacon&type=nightly alongside with gapps,custom kernel, etc.
zephiK said:
Those bugs with touchscreens etc should be fixed, not all of them but the majority of them. They're in the official CM11S as well. Its just something you'll have to deal with until its fully fixed.
Also you are still confusing me, you say latest nightly and then you mention CM11S. There are no CM11S nightlies, the only nightlies there are is CM11. CM11 and CM11S are two different things, they're very similar but in terms of compatibility they are not the same.
The CM11S zip is not a TWRP flashable zip, thats why the .zip says -fastboot in it. You need to do fastboot to flash this (refer to bottom link), but then you mention that you want nightlies? So I'm getting confused on what you want exactly.
A guide to fastboot
Again, CM11S nightlies do not exist! Its either CM11S or CM11 nightlies. This is a big emphasis since you're confused on what you want.
If you want CM11 nightlies, just simply wipe in TWRP and flash alongside with gapps,custom kernel, etc.
Click to expand...
Click to collapse
Sorry for confusing you.
To be clear, I understood differences between CM11S and CM11.
I have CM11 nightly of 24 of august from caynogen website.
I can't install CM11S from Oneplus website (what I call stock ROM).
I'll try the method you provided.
One last question for the custom roms part, what is a custom kernel? I usually only flash the rom and the gapps.
Thanks
Roberto2001 said:
Sorry for confusing you.
To be clear, I understood differences between CM11S and CM11.
I have CM11 nightly of 24 of august from caynogen website.
I can't install CM11S from Oneplus website (what I call stock ROM).
I'll try the method you provided.
One last question for the custom roms part, what is a custom kernel? I usually only flash the rom and the gapps.
Thanks
Click to expand...
Click to collapse
A custom kernel is a kernel other than the kernel supplied by the ROM.
Yeah when you said, "CM11S nightlies" that was a huge no no because they don't exist. Just simply follow the return to stock guide and then you'll get to where you want to be.
Roberto2001 said:
Sorry for confusing you.
To be clear, I understood differences between CM11S and CM11.
I have CM11 nightly of 24 of august from caynogen website.
I can't install CM11S from Oneplus website (what I call stock ROM).
I'll try the method you provided.
One last question for the custom roms part, what is a custom kernel? I usually only flash the rom and the gapps.
Thanks
Click to expand...
Click to collapse
custom kernel is an enhanced version of the rom kernel with usually the latest advancement and some with an array of additional Governors, I/O shcedulers and a host of tweaks. You can read up on it here.
You have to make sure you read up properly and flash the right kernel for the right OS you are running at the moment. There are Cm11 and CM11S specific kernels. Its all good reading if you do a little Google search of skim through the forum and read the OP's
Related
Hi, I'm trying to update my HBoot to 2.13 or 2.15 so I can install the nightly CM11 builds. However, I'm not certain on the steps, so am hoping someone can clear things up for me.
This is the guide I've been looking at:
http://forum.xda-developers.com/showthread.php?t=2501542
At the top he says to find the correct RUU, then links to RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe for HTC Europe.
Am I able to just use that one? My original RUU is RUU_Ville_U_O2_UK_1.78.206.4_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258707_signed.exe, but I can't find a JB version of that.
Looking on http://www.androidruu.com/?developer=Ville, I can't see any RUUs for JB with Radio_0.16.315.
I don't want to download and try and use the wrong thing, so could someone just confirm whether I can/can't use the HTC Europe RUU, and if not, if there's anyway I can update the HBoot to run CM11?
Thank you.
zodac01 said:
Hi, I'm trying to update my HBoot to 2.13 or 2.15 so I can install the nightly CM11 builds. However, I'm not certain on the steps, so am hoping someone can clear things up for me.
This is the guide I've been looking at:
http://forum.xda-developers.com/showthread.php?t=2501542
At the top he says to find the correct RUU, then links to RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe for HTC Europe.
Am I able to just use that one? My original RUU is RUU_Ville_U_O2_UK_1.78.206.4_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258707_signed.exe, but I can't find a JB version of that.
Looking on http://www.androidruu.com/?developer=Ville, I can't see any RUUs for JB with Radio_0.16.315.
I don't want to download and try and use the wrong thing, so could someone just confirm whether I can/can't use the HTC Europe RUU, and if not, if there's anyway I can update the HBoot to run CM11?
Thank you.
Click to expand...
Click to collapse
No! As the OP has said in his thread, you have to use the correct RUU that matches your CID. So yeah you cant use the Europe RUU.
And if your bootloader is still locked and you are S-ON, i suggest you try to find an OTA for JB.
Because THERE IS NO RUU for JB. HTC did not release any RUU for JB as they pretty well understood OTA did serve their purpose.
So if you can confirm your existing HBOOT version here, that would be great to those who can help. Else please provide your CID. (You can use CID getter which is downloadable from PlayStore)
ayyu3m said:
No! As the OP has said in his thread, you have to use the correct RUU that matches your CID. So yeah you cant use the Europe RUU.
And if your bootloader is still locked and you are S-ON, i suggest you try to find an OTA for JB.
Because THERE IS NO RUU for JB. HTC did not release any RUU for JB as they pretty well understood OTA did serve their purpose.
So if you can confirm your existing HBOOT version here, that would be great to those who can help. Else please provide your CID. (You can use CID getter which is downloadable from PlayStore)
Click to expand...
Click to collapse
Ha, a nice strong "no". Thank you for that - good thing I came here to check first then.
Ok, first things first, I've tried updating using the OTA, but it doesn't install. I'm using TWRP v2.6. I could get the error code, but I think I read somewhere that you can't (or shouldn't) install OTA with custom bootloaders? I was hoping to use CM if possible anyway, so hopefully shouldn't have to worry about that (unless that's the way to update the HBoot...)
As for the other info, my HBoot is v1.13 and my CID is O2___01.
807 94346552
Anyone with any information?
zodac01 said:
Anyone with any information?
Click to expand...
Click to collapse
Have you tried to S-OFF your device? If you don't want to do that, why can't you run the O2 RUU then use the system update to get to the higher android version? You have to re-lock the bootloader etc.. as detailed in that guide.
rosswhite said:
Have you tried to S-OFF your device? If you don't want to do that, why can't you run the O2 RUU then use the system update to get to the higher android version? You have to re-lock the bootloader etc.. as detailed in that guide.
Click to expand...
Click to collapse
I tried doing that - I installed the O2 RUU, and then tried to install the update, but it wouldn't work in TWRP. So I locked the bootloader (using fastboot oem lock), but trying to install the update just sends me to the stock HTC bootloader, and doesn't install anything. Is there something else I need to do to install the OTA update?
zodac01 said:
I tried doing that - I installed the O2 RUU, and then tried to install the update, but it wouldn't work in TWRP. So I locked the bootloader (using fastboot oem lock), but trying to install the update just sends me to the stock HTC bootloader, and doesn't install anything. Is there something else I need to do to install the OTA update?
Click to expand...
Click to collapse
The O2 RUU should revert the phone completely to stock and put the stock HTC recovery on the phone so TWRP should not even be installed at this point. Just to trying to understand what you are doing: you install the RUU, once it has booted go to Settings>About>Software Updates>Check Now. It will will find an update then choose to install it. Are you saying from here the phone just reboots to the bootloader and doesn't install the update?
rosswhite said:
The O2 RUU should revert the phone completely to stock and put the stock HTC recovery on the phone so TWRP should not even be installed at this point. Just to trying to understand what you are doing: you install the RUU, once it has booted go to Settings>About>Software Updates>Check Now. It will will find an update then choose to install it. Are you saying from here the phone just reboots to the bootloader and doesn't install the update?
Click to expand...
Click to collapse
That was my mistake - I used the RUU, but then installed TWRP right away, and the updates wouldn't work.
Updated to 4.1.1 on stock - going to see if I can get CM installed now.
zodac01 said:
That was my mistake - I used the RUU, but then installed TWRP right away, and the updates wouldn't work.
Updated to 4.1.1 on stock - going to see if I can get CM installed now.
Click to expand...
Click to collapse
Ok, so I managed to get CM 10.2 installed (the latest stable version). I'm having an issue with v11 though.
I downloaded the most recent nightly build and try to install it (after flashing the boot.img), but get the following message:
Code:
Installing '/sdcard/cm-11-20140315-NIGHTLY-ville.zip'.
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/sdcard/cm-11 <cut off here>
Error flashing zip '/sdcard/cm-11-20140315-NIGHTLY-vil <cut off here>
Updating partition details...
Unlike the last few times I tried updating, where I got a clear error (like bootloader or hboot errors), the log doesn't seem to specify why the update failed.
zodac01 said:
Ok, so I managed to get CM 10.2 installed (the latest stable version). I'm having an issue with v11 though.
I downloaded the most recent nightly build and try to install it (after flashing the boot.img), but get the following message:
Code:
Installing '/sdcard/cm-11-20140315-NIGHTLY-ville.zip'.
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/sdcard/cm-11 <cut off here>
Error flashing zip '/sdcard/cm-11-20140315-NIGHTLY-vil <cut off here>
Updating partition details...
Unlike the last few times I tried updating, where I got a clear error (like bootloader or hboot errors), the log doesn't seem to specify why the update failed.
Click to expand...
Click to collapse
It might be the recovery, I think CM11 needs a modified version of TWRP 2.6.3.0, its in the OP of the CM11 thread.
http://forum.xda-developers.com/showpost.php?p=47483838&postcount=1
Edit: You should also be able to use TWRP 2.7.0.0 : http://techerrata.com/browse/twrp2/ville
rosswhite said:
It might be the recovery, I think CM11 needs a modified version of TWRP 2.6.3.0, its in the OP of the CM11 thread.
http://forum.xda-developers.com/showpost.php?p=47483838&postcount=1
Edit: You should also be able to use TWRP 2.7.0.0 : http://techerrata.com/browse/twrp2/ville
Click to expand...
Click to collapse
Dammit, it was actually in the OP. I really should have seen that. Sorry for wasting your time - that was the problem. I've got 4.4.2 running nicely now.
Thank you very much for your time and patience.
zodac01 said:
Dammit, it was actually in the OP. I really should have seen that. Sorry for wasting your time - that was the problem. I've got 4.4.2 running nicely now.
Thank you very much for your time and patience.
Click to expand...
Click to collapse
No problem at all, glad you got it sorted.
Hi,
I'm having a similar problem with flashing CM11 nightlies. This is what I have done:
I have been running MaximusHD for a couple of months. Before that I was running CM11 nightlies just fine.
I used this guide (http://forum.xda-developers.com/showthread.php?t=2322755) to successfully downgrade to hboot 2.15. I then ran MIUI for a few days, which worked fine, but I still wanted the AOSP goodness that you get with a CM-based ROM, so I decided to change to the official CM11 nightlies.
I then tried to flash CM11 (and also PA and Vanir, both based on CM11, plus several other versions of the nightlies, which I found on download.cyanogenmod.com) in TWRP 2.7.0.0. Each time failed with the error: "E:Error executing updater binary in zip 'name-of-zip'".
Then I looked at the CM11 OP on XDA (http://forum.xda-developers.com/showthread.php?t=2528113). I read that you must have one of the two "updated recoveries". While I thought that the zips should flash on TWRP 2.7.0.0, I flashed those recoveries via fastboot also. When flashing the same files as above on the modified TWRP 2.3.3.0, I got exactly the same error as I did with 2.7.0.0. When I tried flashing the ROMs on ClockWorkMod, I got a "Status 7" error.
I googled around a bit and found some (old!) posts on various forums that said that there was a recovery called philz-touch that seemed to be working for some people. I downloaded it, flashed it, and got another "status 7" error when I tried to flash any of the zips.
Then I tried using several versions of TWRP (all the ones here http://techerrata.com/browse/twrp2/ville from 2.3.3.0 to 2.7.0.0 to be precise) and tried flashing each of the zips again. Still no luck.
Other things I have tried:
*I re-ran the steps here (http://forum.xda-developers.com/showthread.php?t=2322755) to ensure that it had definitely worked the first time.
*I tried using the hboot 2.15 and 2.13 (both modded and unmodded) that I found here (http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274&nocache=1&z=674317537341266)
*I tried re-downloading the ROM zips that I had been flashing to make sure that none of them had been corrupted in any way.
*I tried flashing the CM10.2 stable ROM that I found on download.cyanogenmod.com. It flashed no problem and booted fine with no fuss.
I feel like I am the only one on the internet who is having these issues even after changing to the updated recoveries! Please excuse my English, it is not my first language! I would really appreciate some help on this, as I have absolutely no idea what to do.
Thank you very much!
c1aran said:
Hi,
I'm having a similar problem with flashing CM11 nightlies. This is what I have done:
I have been running MaximusHD for a couple of months. Before that I was running CM11 nightlies just fine.
I used this guide (http://forum.xda-developers.com/showthread.php?t=2322755) to successfully downgrade to hboot 2.15. I then ran MIUI for a few days, which worked fine, but I still wanted the AOSP goodness that you get with a CM-based ROM, so I decided to change to the official CM11 nightlies.
I then tried to flash CM11 (and also PA and Vanir, both based on CM11, plus several other versions of the nightlies, which I found on download.cyanogenmod.com) in TWRP 2.7.0.0. Each time failed with the error: "E:Error executing updater binary in zip 'name-of-zip'".
Then I looked at the CM11 OP on XDA (http://forum.xda-developers.com/showthread.php?t=2528113). I read that you must have one of the two "updated recoveries". While I thought that the zips should flash on TWRP 2.7.0.0, I flashed those recoveries via fastboot also. When flashing the same files as above on the modified TWRP 2.3.3.0, I got exactly the same error as I did with 2.7.0.0. When I tried flashing the ROMs on ClockWorkMod, I got a "Status 7" error.
I googled around a bit and found some (old!) posts on various forums that said that there was a recovery called philz-touch that seemed to be working for some people. I downloaded it, flashed it, and got another "status 7" error when I tried to flash any of the zips.
Then I tried using several versions of TWRP (all the ones here http://techerrata.com/browse/twrp2/ville from 2.3.3.0 to 2.7.0.0 to be precise) and tried flashing each of the zips again. Still no luck.
Other things I have tried:
*I re-ran the steps here (http://forum.xda-developers.com/showthread.php?t=2322755) to ensure that it had definitely worked the first time.
*I tried using the hboot 2.15 and 2.13 (both modded and unmodded) that I found here (http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274&nocache=1&z=674317537341266)
*I tried re-downloading the ROM zips that I had been flashing to make sure that none of them had been corrupted in any way.
*I tried flashing the CM10.2 stable ROM that I found on download.cyanogenmod.com. It flashed no problem and booted fine with no fuss.
I feel like I am the only one on the internet who is having these issues even after changing to the updated recoveries! Please excuse my English, it is not my first language! I would really appreciate some help on this, as I have absolutely no idea what to do.
Thank you very much!
Click to expand...
Click to collapse
You just got bad luck and probably missed the right recovery. Starting with 1/05 nightly you need a special recovery due to some CM commits. It is an unofficial 2.7.0.8 and you can find it by looking in CM11 official thread in the last pages. It is posted by intervigil a link to CM wiki from where you can download it. You will need this recovery to flash any CM nightly newer than 1/05 and also for any ROM that's based on CM tree and build lately.
The TWRP 2.7.0.0 was fine as long as you flash an older nightly or a ROM that doesn't have those commits yet.
I'm on the phone right now but I'll try to look for a link and give to you if you don't find it
Edit: Here you go...
http://wiki.cyanogenmod.org/w/HTC_fstab_updates
Sent from nowhere over the air...
Rapier said:
You just got bad luck and probably missed the right recovery. Starting with 1/05 nightly you need a special recovery due to some CM commits. It is an unofficial 2.7.0.8 and you can find it by looking in CM11 official thread in the last pages. It is posted by intervigil a link to CM wiki from where you can download it. You will need this recovery to flash any CM nightly newer than 1/05 and also for any ROM that's based on CM tree and build lately.
The TWRP 2.7.0.0 was fine as long as you flash an older nightly or a ROM that doesn't have those commits yet.
I'm on the phone right now but I'll try to look for a link and give to you if you don't find it
Edit: Here you go...
LINK REMOVED
Sent from nowhere over the air...
Click to expand...
Click to collapse
Hi,
I got a bit frustrated last night and must have missed that information in the CM11 thread. I had a look at that link and it has fixed my issues. Thank you very much!
Hi guys,
I want to ask you some questions,I never flashed my tab.
1. Is it this TWRP file I have to flash ? http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.6.3.0-tf300t-4.2.blob (I'm on stock official Asus 4.2.1 now)
2. If I go on CM11 for example, can I revert to stock Asus 4.2.1 ?
3. If I go on CM11, can I flash on it a CM 10.2 rom for example ?
And does the keyboard work on custom rom like CM11?
Thank you for your help
needhelp11 said:
1. Is it this TWRP file I have to flash ? http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.6.3.0-tf300t-4.2.blob (I'm on stock official Asus 4.2.1 now)
2. If I go on CM11 for example, can I revert to stock Asus 4.2.1 ?
3. If I go on CM11, can I flash on it a CM 10.2 rom for example ?
And does the keyboard work on custom rom like CM11?
Click to expand...
Click to collapse
1. That recovery will not work for KitKat ROMs like CM 11 or OmniROM. Check the respective ROM thread for a working TWRP. Also double-check the version of your bootloader.
2. Yes, read the sticky guides in the general section.
3. Yes.
When flashing a different ROM (not just another version of the same ROM) remember to do a full wipe: data, system, cache, dalvik.
If you mean the keyboard dock, yes that basically works in all ROMs I tried so far. Some ROMs don't support all the special keys, but basic typing works fine.
Sent from my TF300T using Tapatalk
Hi,
Thank you for your answer. I have read a lot of guide, but I'm a bit confusing because I never used TWRP before and there is so much things to do ( adb, fastboot etc...)
Im on the lastest Asus official firmware so I think I need the TWRP 2.6.3.0 or .2 4.2 version. Should I do this before : http://forum.xda-developers.com/showthread.php?t=2545610? (install nvflash flatline )
Edit : And if I flash cm 10.2 stable, can I use TWRP 2.6.3.0 ?
Again thank you
needhelp11 said:
Hi,
Thank you for your answer. I have read a lot of guide, but I'm a bit confusing because I never used TWRP before and there is so much things to do ( adb, fastboot etc...)
Im on the lastest Asus official firmware so I think I need the TWRP 2.6.3.0 or .2 4.2 version. Should I do this before : http://forum.xda-developers.com/showthread.php?t=2545610? (install nvflash flatline )
Edit : And if I flash cm 10.2 stable, can I use TWRP 2.6.3.0 ?
Again thank you
Click to expand...
Click to collapse
Flatline is the best thing you can do for your 300... I would highly recommend backing up of your nvflash blobs.....
If you need any help with this just let me know, drop me a line at [email protected]
Thx as always Josh
Thank you. I will do it a little later, im now busy with my work.
Thanks again to you guys for helping me
needhelp11 said:
Edit : And if I flash cm 10.2 stable, can I use TWRP 2.6.3.0 ?
Click to expand...
Click to collapse
Yes, that is fine.
The latest version from scanno (2.7.0.0) should work for both CM 11 and CM 10.2, but I am not sure the respective patch made it into that build, maybe only with the next update.
2.6.3.0-42 from the official download site is the safe choice for CM 10.2.
Sent from my TF300T using Tapatalk
So i was trying to flash CM 11 onto my Razr HD following the instructions on this thread:
http://forum.xda-developers.com/showthread.php?t=2518701&highlight=boot+loop
However, after flashing and everything, my phone ends up in a bootloop... I'm on 4.4.2, 183.46.10XT926, kernel 3.4.42 and an unlocked bootloader
Any help?
braube said:
So i was trying to flash CM 11 onto my Razr HD following the instructions on this thread:
http://forum.xda-developers.com/showthread.php?t=2518701&highlight=boot+loop
However, after flashing and everything, my phone ends up in a bootloop... I'm on 4.4.2, 183.46.10XT926, kernel 3.4.42 and an unlocked bootloader
Any help?
Click to expand...
Click to collapse
i dont think cm is updated to 4.4 source yet, i could be wrong. (as it turns out, i was wrong and cm is on 4.4 source)
if it is not, you cant install it over 4.4, that's why it is bootlooping.
What do you talking about? CM11 is 4.4.4, maybe @braube is trying to install an old version of CM11 that is based on 3.0 kernel, just try the latest versions available here: http://download.cyanogenmod.org/?device=moto_msm8960
DorianX said:
What do you talking about? CM11 is 4.4.4, maybe @braube is trying to install an old version of CM11 that is based on 3.0 kernel, just try the latest versions available here: http://download.cyanogenmod.org/?device=moto_msm8960
Click to expand...
Click to collapse
i said "i could be wrong", learn to read, or at least reply more politely with a correction.
So you answer any question without a minimal knowledge? That's how you get so many thanks?
DorianX said:
So you answer any question without a minimal knowledge? That's how you get so many thanks?
Click to expand...
Click to collapse
jealous?
Yup I'm so jealous ;(
braube said:
So i was trying to flash CM 11 onto my Razr HD following the instructions on this thread:
http://forum.xda-developers.com/showthread.php?t=2518701&highlight=boot+loop
However, after flashing and everything, my phone ends up in a bootloop... I'm on 4.4.2, 183.46.10XT926, kernel 3.4.42 and an unlocked bootloader
Any help?
Click to expand...
Click to collapse
I know you stated you followed the directions, but just in case, this is what I do:
1. Boot into TWRP
2. Wipe cache, dalvik cache, data and system
3. Install CM11.
4. Install GAPPS
5. Wipe cache and dalvik (from the Install screen)
6. Reboot and profit.
If this still doesn't work for you, you might have a corrupted download for CM11 and/or GAPPS, so try downloading them again and make SURE you are using the correct CM11 image.
If you are getting them from epinter, then make sure you choose the correct one. There are a LOT of ROM images there (for XT925, for CM10 for JB-based phones, CM11 xt926 I believe is for JB based phones, you want the CM11 with msm9690 in the file name).
I get mine from here -> http://download.cyanogenmod.com/?device=moto_msm8960
Also, make sure you have the correct TWRP installed (2.7.1.0) that is KK based. Do NOT use earlier versions which are based off of JB.
You can also use CWM recovery, but make sure it's 6.0.4.9. Anything else is for JB-based phones that haven't been upgraded to KK.
Thanks for all the replies. I just did a standard wipe with TWRP so maybe thats the problem.
Another question, is the msm8960 CM11 compatible with XT926? I read somewhere that it was but i just want to make sure
That's what you want and it's what I linked you to.
Sent from my DROID RAZR HD using Tapatalk
So I am new to htc and new to what to do, been on Samsung for years and htc is way different.
First, once I update firmware will it be safe to flash the roms in the android development section even if they are from July or August ?
Do the Roms include kernels or do I need to find one and flash it after I flash the rom along with gapps ? If so what kernels do you recommend and /or do you have a list of some of them ?
What is fastboot and how do I use it? I am updating the firmware through sd card method but also want to update the twrp and I heard that is done through fast boot. Does that require a computer or?
Thank you for taking the time to read my questions
thrgk said:
So I am new to htc and new to what to do, been on Samsung for years and htc is way different.
First, once I update firmware will it be safe to flash the roms in the android development section even if they are from July or August ?
Do the Roms include kernels or do I need to find one and flash it after I flash the rom along with gapps ? If so what kernels do you recommend and /or do you have a list of some of them ?
What is fastboot and how do I use it? I am updating the firmware through sd card method but also want to update the twrp and I heard that is done through fast boot. Does that require a computer or?
Thank you for taking the time to read my questions
Click to expand...
Click to collapse
First off I assume you are s-off and unlocked via firewater or sunshine.
1) this is only anectodal but I ran ViperROM 1.8 (4.4.2 based) with the 4.4.3 firmware for a few weeks without issue.
2) all Roms come with a kernel. Some are stock, some are custom but they all come with one. ASSUMING you are s-off then the packaged kernel will be flashed along with the rom. If you're looking for a custom kernel make sure you find a Sense/GPE/AOSP kernel which matches your rom type (SENSE/GPE/AOSP) and flash it AFTER flashing the rom. Flashing a rom will overwrite whatever kernel you previosly had installed with the new rom's kernel. I am currently runing ViperROM 2.5 which is a Sense ROM with the EliteLunar kernel (sense version) with no issues.
3) fastboot is an interface between a computer and your phone. I always find it alarming when people ask this question. Learn and become familiar with fastboot BEFORE YOU FLASH ANY ROMs OR ZIP FILES IN RECOVERY. I'm not being rude, I assure you this is sound advice. Many fastboot tasks can be performed with apps like flashify or by a flashable zip file which many devs are kind enough to create. However, having fastboot set up and functional (that includes knowledge of how to use it) is irreplaceable if/when things go downhill.
cntryby429 said:
First off I assume you are s-off and unlocked via firewater or sunshine.
1) this is only anectodal but I ran ViperROM 1.8 (4.4.2 based) with the 4.4.3 firmware for a few weeks without issue.
2) all Roms come with a kernel. Some are stock, some are custom but they all come with one. ASSUMING you are s-off then the packaged kernel will be flashed along with the rom. If you're looking for a custom kernel make sure you find a Sense/GPE/AOSP kernel which matches your rom type (SENSE/GPE/AOSP) and flash it AFTER flashing the rom. Flashing a rom will overwrite whatever kernel you previosly had installed with the new rom's kernel. I am currently runing ViperROM 2.5 which is a Sense ROM with the EliteLunar kernel (sense version) with no issues.
3) fastboot is an interface between a computer and your phone. I always find it alarming when people ask this question. Learn and become familiar with fastboot BEFORE YOU FLASH ANY ROMs OR ZIP FILES IN RECOVERY. I'm not being rude, I assure you this is sound advice. Many fastboot tasks can be performed with apps like flashify or by a flashable zip file which many devs are kind enough to create. However, having fastboot set up and functional (that includes knowledge of how to use it) is irreplaceable if/when things go downhill.
Click to expand...
Click to collapse
Thanks for all the info. So if I am on 4.4.3 and want to flash a 4.4.2 rom just flash the 4.4.2 firmware just to be safe before flashing the 4.4.2 rom?
Also where are the kernels located ? Are they carrier dependent as I didn't see any yet browsing but didn't look hard either.
So I can do flash boot through flashify and be ok? Now all roms and kernels are flashed through twrp tho right ?
EDIT: actually fastboot can flash rom and kernels so no real need for custom recovery other then for convenience?
Btw do you have a kernel recommendation for aosp, sense, ? I already saw your recommendation for sense above.
Thanks !!
Sent from my SM-N900V using XDA Free mobile app
I have a feeling that it's simply not necessary to downgrade your firmware in order to run a 4.4.2 rom but you should find a more reputable source than myself. I'm just trying to answer these easy questions to save time for the guys who really know what they're doing. Once you do start flashing things, always make sure 1) they are for your device (and carrier, unless unified for all carriers) and 2) the md5 of the downloaded file matches that provided by the hosting website or the OP.
I'm not a fan of flashing utilities simply because I've heard of instances where they don't work correctly. For example, I keep hearing how the TWRP manager app flashes TWRP to the system partition on Verizon devices and sends the phone into a sort of recovery loop. I would suggest gaining knowledge about the fastboot flash command "fastboot flash <partition name> <filename.extension>" and how to enter and flash within RUU mode.
My experience is that ROMS and kernels are easiest flashed through a custom recovery especially when the developer packages it with an Aroma installer script.
A few Sense/GPE custom kernels exist for verizon. There's MassStashed and Checkm8 (no longer maintained?) for 4.4.2 roms. Also, for 4.4.3 roms I only know of the EliteLunar kernel which isn't on XDA although you can find a few links to it in the forums if you search. Last I knew, there weren't any AOSP kernels which work with verizon but that might not be true anymore. The general HTC One m8 forum may have some kernels which aren't represented in the verizon-specific forum. Just make sure and find out if they're compatible with verizon devices. I'm pretty happy with sense so I haven't wondered off to AOSP like I usually do.
so do you recommend to use flashify or no?
thrgk said:
so do you recommend to use flashify or no?
Click to expand...
Click to collapse
Its the easiest way
thrgk said:
so do you recommend to use flashify or no?
Click to expand...
Click to collapse
I'm not saying you shouldn't use flashify, it's awfully convenient. Just make sure you're using it for the convenience and not because you don't know how to accomplish the same tasks in recovery/fastboot.
Could someone please provide me with the latest Cyanogen Recovery for bacon?
They removed the option of writing recovery from CM12 so I can't get the latest version.
I'm looking for Cyanogen Recovery built from source not CWM or TWRP.
Thanks!
DJXMMX said:
Could someone please provide me with the latest Cyanogen Recovery for bacon?
They removed the option of writing recovery from CM12 so I can't get the latest version.
I'm looking for Cyanogen Recovery built from source not CWM or TWRP.
Thanks!
Click to expand...
Click to collapse
You can simply extract it from the official fastboot zip on this page: cyngn.com/products/oneplusone/ (sorry, not allowed to post links)
DJXMMX said:
Could someone please provide me with the latest Cyanogen Recovery for bacon?
They removed the option of writing recovery from CM12 so I can't get the latest version.
I'm looking for Cyanogen Recovery built from source not CWM or TWRP.
Thanks!
Click to expand...
Click to collapse
They didn't remove it, you are working with nightlys why would they put it in nightlys
I'm not looking for the OnePlus Recovery, I would like the latest Cyanogen Recovery.
Besides, that recovery is fairly dated back to KitKat.
They do allow you to flash recovery in CM11 nighties so I'm afraid you are mistaken.
There is a patch on the CM Gerrit that is waiting to be committed that will allow users to update recovery in CM12.
I guess I'll just have to wait for that but I was hoping to have a flashable IMG as well.
DJXMMX said:
I'm not looking for the OnePlus Recovery, I would like the latest Cyanogen Recovery.
Besides, that recovery is fairly dated back to KitKat.
They do allow you to flash recovery in CM11 nighties so I'm afraid you are mistaken.
There is a patch on the CM Gerrit that is waiting to be committed that will allow users to update recovery in CM12.
I guess I'll just have to wait for that but I was hoping to have a flashable IMG as well.
Click to expand...
Click to collapse
What do you mean? The stock recovery on this device is the CM recovery, there's no such thing as a OnePlus recovery. You can't flash nightlies with it. As previously stated you can just extract the recovery image from the stock fastboot images.
Transmitted via Bacon
Negative.
The stock recovery is Cyanogen based but is modified by OnePlus.
Much like how CM11S is Cyanogen based but is modified by OnePlus.
Now, I'm running CWM 6.0.5.1 but I would like to get the latest recovery which, when you build from source, is called Cyanogen Recovery and is more up to date.
Cyanogen took over development of CWM and eventually renamed it to Cyanogen Recovery.
I have a build, dated 20150118, for my old XT926 that someone graciously provided but I'm looking for bacon now.
Thanks.
DJXMMX said:
Negative.
The stock recovery is Cyanogen based but is modified by OnePlus.
Much like how CM11S is Cyanogen based but is modified by OnePlus.
Now, I'm running CWM 6.0.5.1 but I would like to get the latest recovery which, when you build from source, is called Cyanogen Recovery and is more up to date.
Cyanogen took over development of CWM and eventually renamed it to Cyanogen Recovery.
I have a build, dated 20150118, for my old XT926 that someone graciously provided but I'm looking for bacon now.
Thanks.
Click to expand...
Click to collapse
Where are you getting this information? CM11S is not modified by OnePlus.
Transmitted via Bacon
I'm sorry, I thought this was a well known fact.
Just Google "CM11S vs CM11"
CM11S is a customized version of Cyanogen just for the OPO.
Anyway, we are on CM12 now and I'd like to get the Cyanogen Recovery that is built against CM12 source.
Thanks.
DJXMMX said:
I'm sorry, I thought this was a well known fact.
Just Google "CM11S vs CM11"
CM11S is a customized version of Cyanogen just for the OPO.
Anyway, we are on CM12 now and I'd like to get the Cyanogen Recovery that is built against CM12 source.
Thanks.
Click to expand...
Click to collapse
Sorry, but you're mistaken, it is the exact opposite of a fact (it's completely untrue). Yes, CM11S is a customised version of CM11, but it is developed solely by Cyanogen (Steve Kondik is even the lead developer). Go and ask OnePlus or CM themselves, they'll tell you exactly the same thing. In fact, ask anyone who knows anything about this phone and they'll tell you exactly the same thing. OnePlus have absolutely nothing to do with the actual development of CM11S or CM12S, CM do all the work, CM do all the testing, CM submit it to Google for approval, CM provide the release once it receives accreditation. Why on earth do you think everyone was worried that this device wouldn't receive CM12S after the OnePlus/CM/Micromax drama in India? Because CM have 100% control over CM11S/CM12S.
Transmitted via Bacon
Ok.
Either way, it doesn't change the fact that there is a newer recovery available (I saw the commits on the CM Gerrit).
If someone could build it against CM12 sources for Bacon, that would be appreciated.
Thanks!
DJXMMX said:
Ok.
Either way, it doesn't change the fact that there is a newer recovery available (I saw the commits on the CM Gerrit).
If someone could build it against CM12 sources for Bacon, that would be appreciated.
Thanks!
Click to expand...
Click to collapse
There may be commits, but there definitely isn't a version available, and I highly doubt that anyone is going to build it because of two reasons:
1. It will be included with the CM12S update (coming very soon).
2. It has very limited functionality, it doesn't hold any value for the modding community.
Exactly what do you want it for? Why not use one of the available recoveries (TWRP/CWM/Philz/Cannibal)? They actually have functionality that is useful, CM recovery can only install signed zips (official OTA's), it's only ever been able to do that.
Transmitted via Bacon