Database Info

Cm7 on Desire HD - no market!

Hi
Recently flashed cm7.0.3 on my DHD after the usual nandroid backup etc. Had to wipe data and cache first. After the cm flash I flashed the latest gapps.
The phone boots fine but with no Android market and no Google apps. I understand that the gapps process has changed so I must be doing something wrong, but what??
Thanks!
George
Sent from my Desire HD using XDA App

Did you use Rom Manager or did you flash from Recovery? May be worth trying whichever method you didn't the first time around.

You need to download the GAPPS file located most likely in the same thread you downloaded the CM7 files. You will have to use CWM to flash the GAPPS file and once done you will have the market once the phone boots back up.
I ran in to the same issue when I installed CM7 on my Captivate and once I found the GAPPS file I was golden!

Aha! Got ya. I've been trying to flash gapps from recovery - I take it that doesn't work then? Haven't used CWM for *ages* but am sure I can guess my way thru it.
Thanks!

gapps have to be flashed from recovery. yes. try rom manager in your phone. it makes the process a lot easier. press Download Rom - CM - and choose the latest stable. it will then ask you abt gapps, just check that box and you are set

Sorted
Thanks for the tips, got it working in the end. There were a couple of problems stopping me flashing GAPPS:
- Clockwork mod was an old version - had to try a couple of times to upgrade it, kept failing, worked after complete wipe and reflash of CM7
- I had been trying to install GAPPS from recovery. Tried from CWM after the upgrade and it worked fine.
Cheers for the help.

[Q] Can you explain how to install the latest CM10?

NOOB here, I am still am running the build just before the nightlies started and I feel like I should update to one of the new builds. But, there are so many discussions going on about radios, that are making this more confusing than it is supposed to be. So, I was wondering if you anyone can post or link me to a straightforward method to be updated to the best build at this time, with the best possible radio. Thanks a lot for your help, and you guys are awesome for making all this stuff possible. I wish I was more knowledgeable and less of a mucher.

Download the 10/7 nightly from here http://get.cm/?device=evita
Download the latest Gapps here http://goo.im/devs/Formula84/gapps-jb-20120929-JRO03R/gapps-jb-20120929-JRO03R-Formula84.zip
I suggest the Htc AT&T 2.20 Radio from here http://forum.xda-developers.com/showthread.php?t=1694012
1.Copy all these to your Phone storage by mounting usb.
2.Reboot into recovery( should have TWRP 2.2.2.0 recovery installed).
3.(I would do a full wipe coming from a build that far back) Wipe system and data/cache.
4.Install latest nightly 10/7 zip.
5.Install Gapps zip.
6.Keep current radio or flash new version zip.
7. Reboot system and enjoy.
The new nightlies have the updated kernel and are much better in terms of battery life.

took out the tf101 after about a year or so

hey guys, ill get straight to the point:
i decided to take out my old tf101(non-3g) after after a year or more, dont remember. it works relatively well, but im sure theres a lot that can be updated rom-wise. right now it has this:
Kernel version
2.6.39.4-JELLYBEAN-g18e8917-dirty [email protected] #89 SMP PREEMPT Wed Aug 22 17:40:05 CEST 2012
Build number
full_tf101-userdebug 4.1.1 MASTER eng. RaymanFX.20120821.232608 test-keys
I include this because I'm not exactly sure what version i have.. i think its the 6.0.0 from raymanfx
Anyway, from what I could from a quick glance of these forums, there's a ton of new features for this tablet! or at least one i really like, multi-window.
So can I get some suggestions from you guys on whats the best way to get my tablet up to date? I'm looking for a stable rom also. Is the best way to get to this point to return my tablet to stock and start over from there?
Any useful suggestions are welcomed. Thanks

First thing you should do is make sure you have TWRP recovery installed
Make sure if you have CWM recovery installed that you change over to TWRP before flashing the ROM or you have a good chance of a boot loop
Easiest method, install Goo Manager from here
https://play.google.com/store/apps/details?id=com.s0up.goomanager
Open app > Hit the top right 3 dots menu button > choose "Install Open RecoveryScript"
Follow instructions to get TWRP running, boot into TWRP to check it has worked by holding Power & Volume Down from a powered off state until you see the white text at the top of the screen
Then release all buttons and tap volume up to enter recovery
If that works fine, then download a new ROM and Gapps and copy to a Micro SD Card
This is the latest and most stable version that has Multi Window support
http://forum.xda-developers.com/showthread.php?t=2392087
Copy the ROM & Gapps to Micro SD and stick it in the TF
Boot into TWRP
Press the WIPE option and wipe everything apart from External which is where your new ROM is
Go back to the main screen by hitting the home button at the top right
Press the install button
Choose External memory to find your new ROM and Gapps
Install ROM
Install Gapps
Wipe Cache & Dalvik Cache
Press reboot to Reboot into your new 4.3.1 Jellybean ROM with Multi Window
----
If you have problems getting TWRP using Goo Manager, use EasyFlasher
http://forum.xda-developers.com/showthread.php?t=1688012

roadrunnerx7 said:
Anyway, from what I could from a quick glance of these forums, there's a ton of new features for this tablet! or at least one i really like, multi-window.
Click to expand...
Click to collapse
Because you want Multi-Window, go with the previously mentioned KatKiss 4.3.1 or, if you can wait a few days, go for 4.4.2 v023. Tim's changelog indicates the next version is going to fix it.
4.4.2 really flies, BTW!

*Detection* said:
.
Click to expand...
Click to collapse
Thank you very much for the thorough explanation. When I get a chance I'll get started on updating things. Thanks!!
DoughMucker said:
Because you want Multi-Window, go with the previously mentioned KatKiss 4.3.1 or, if you can wait a few days, go for 4.4.2 v023. Tim's changelog indicates the next version is going to fix it.
4.4.2 really flies, BTW!
Click to expand...
Click to collapse
Thanks for the suggestion. Why is 4.4.2 v023 better though?

roadrunnerx7 said:
Thanks for the suggestion. Why is 4.4.2 v023 better though?
Click to expand...
Click to collapse
Android 4.4 (Kit Kat) runs much better on lower powered/memory devices than previous versions. The possible downside of KatKiss 4.4.2 compared with KatKiss 4.3.1 is that it is relatively new and may have some issues with some apps (i haven't seen any though).

So I followed all the steps and updated my tablet. Installed the 4.4.2 version. It's awesome!!! I never imagined this tablet would still have so much value in it.
Thanks again guy for helping me out!

Great!
Yea the latest 4.4.2 #23 is a superb ROM, best one so far imo & multiwindow is in this one too

I just bought my wife a used TF300T running stock 4.2.1 and, after rooting and using lagfix, it doesn't seem any faster than my TF101 running KatKiss 4.4.2. Maybe I should have bought another TF101 and saved a few bucks.

DoughMucker said:
I just bought my wife a used TF300T running stock 4.2.1 and, after rooting and using lagfix, it doesn't seem any faster than my TF101 running KatKiss 4.4.2. Maybe I should have bought another TF101 and saved a few bucks.
Click to expand...
Click to collapse
Run a few benchmarks like 3DMark and Antutu on each of them

*Detection* said:
Run a few benchmarks like 3DMark and Antutu on each of them
Click to expand...
Click to collapse
I ran Antutu on each...
TF101 (@1400MHz) got 10113. TF300T got 13444. But they feel pretty much the same for the basic stuff my wife and I do with the tablets.

I'm having problems with Netflix.. A lot of times it hang.. Not loading, but the picture. The video will seemingly stop playing and get stuck, but the sound continues and the playback timer continues also. Only the video gets stuck. The only thing that will temp fix it is to close the app and open again, but even then there's a 50/50 chance it will screw up again. And if I move to a specific spot in the video, so that it has to sort of reload it, it will likely get stuck again.
You guys have any problems like this with Netflix? Solutions?
I'm still on v23.. I see there's a v23c now but not sure if that's a newer version?

Instructions for issues are in post 2 of the main ROM thread
http://forum.xda-developers.com/showpost.php?p=49007034&postcount=2
--
Netflix
To get the latest Netflix versions to work you can use this XPosed module:
http://forum.xda-developers.com/showthread.php?t=2101525
You can also use an older version of Netflix ( 2.0..)

roadrunnerx7 said:
I'm still on v23.. I see there's a v23c now but not sure if that's a newer version?
Click to expand...
Click to collapse
23c just adds support for some international keyboards - they're otherwise the same.

*Detection* said:
Instructions for issues are in post 2 of the main ROM thread
http://forum.xda-developers.com/showpost.php?p=49007034&postcount=2
--
Netflix
To get the latest Netflix versions to work you can use this XPosed module:
http://forum.xda-developers.com/showthread.php?t=2101525
You can also use an older version of Netflix ( 2.0..)
Click to expand...
Click to collapse
I did the netflix fix before already. Thats why im not sure what to do to fix it. Havent tried getting an older version. Do you know where i can get an older version of netflix? Also if i do use the older, can i uninstall the Xposed module?
Thanks

*Detection* said:
First thing you should do is make sure you have TWRP recovery installed
Make sure if you have CWM recovery installed that you change over to TWRP before flashing the ROM or you have a good chance of a boot loop
Easiest method, install Goo Manager from here
https://play.google.com/store/apps/details?id=com.s0up.goomanager
Open app > Hit the top right 3 dots menu button > choose "Install Open RecoveryScript"
Follow instructions to get TWRP running, boot into TWRP to check it has worked by holding Power & Volume Down from a powered off state until you see the white text at the top of the screen
Then release all buttons and tap volume up to enter recovery
If that works fine, then download a new ROM and Gapps and copy to a Micro SD Card
This is the latest and most stable version that has Multi Window support
http://forum.xda-developers.com/showthread.php?t=2392087
Copy the ROM & Gapps to Micro SD and stick it in the TF
Boot into TWRP
Press the WIPE option and wipe everything apart from External which is where your new ROM is
Go back to the main screen by hitting the home button at the top right
Press the install button
Choose External memory to find your new ROM and Gapps
Install ROM
Install Gapps
Wipe Cache & Dalvik Cache
Press reboot to Reboot into your new 4.3.1 Jellybean ROM with Multi Window
----
If you have problems getting TWRP using Goo Manager, use EasyFlasher
http://forum.xda-developers.com/showthread.php?t=1688012
Click to expand...
Click to collapse
Hi
Sorry to revive an old thread
I am in the same boat. I have a B40 tablet.
I followed the steps up till install ROM.
When I install, it is stuck at "updating partition detail".
I have tried to flash newest twrp without success ( cannot even get into recovery)
I have tried easyflasher to unbrick, flash twrp 2.2.1, flash twrp 2.3.2.3 using GOOmanager, but still stuck at "updating partition detail" when flash katkiss 4.4.2v23c.
I have tried different micro-sd cards and different downloads.
What may have gone wrong?
Thanks

strikeraj said:
Hi
Sorry to revive an old thread
I am in the same boat. I have a B40 tablet.
I followed the steps up till install ROM.
When I install, it is stuck at "updating partition detail".
I have tried to flash newest twrp without success ( cannot even get into recovery)
I have tried easyflasher to unbrick, flash twrp 2.2.1, flash twrp 2.3.2.3 using GOOmanager, but still stuck at "updating partition detail" when flash katkiss 4.4.2v23c.
I have tried different micro-sd cards and different downloads.
What may have gone wrong?
Thanks
Click to expand...
Click to collapse
Does it not flash the ROM first, then stop at "Updating Partition Details" ?
Are you sure it hasn't successfully flashed the ROM?
iirc Updating Partition Details is the last thing it says after flashing

*Detection* said:
Does it not flash the ROM first, then stop at "Updating Partition Details" ?
Are you sure it hasn't successfully flashed the ROM?
iirc Updating Partition Details is the last thing it says after flashing
Click to expand...
Click to collapse
Sadly not.
When I swipe to flash, that is the first and only line that pops up immediately.
If I let it sit at that line for the night, in the morning I see TWRP going back to home screen. But the log still only has that one line.

strikeraj said:
Sadly not.
When I swipe to flash, that is the first and only line that pops up immediately.
If I let it sit at that line for the night, in the morning I see TWRP going back to home screen. But the log still only has that one line.
Click to expand...
Click to collapse
Ok, try NVFLASH'ing the Stock ROM
NVFLASH will delete and re-create all the partitions on the device and then flash you back to 100% factory stock
Once you are up and running with stock, use Easyflasher to flash TWRP recovery again, then try flashing KatKiss ROM again from TWRP
Download > Extract > Plug TF into PC USB > Power off TF and Put TF into APX Mode (Vol Up & Power) > Run download.bat as Administrator
Download
https://mega.co.nz/#!tINBhLob!InI_F2Y6D8rSVZ5sDeCQx2T41c9gp_7Z_7kCqFNDVIs

*Detection* said:
Ok, try NVFLASH'ing the Stock ROM
NVFLASH will delete and re-create all the partitions on the device and then flash you back to 100% factory stock
Once you are up and running with stock, use Easyflasher to flash TWRP recovery again, then try flashing KatKiss ROM again from TWRP
Download > Extract > Plug TF into PC USB > Power off TF and Put TF into APX Mode (Vol Up & Power) > Run download.bat as Administrator
Download
https://mega.co.nz/#!tINBhLob!InI_F2Y6D8rSVZ5sDeCQx2T41c9gp_7Z_7kCqFNDVIs
Click to expand...
Click to collapse
Thanks for your reply.
Just a couple questions
1. I have used easyflasher to flash stock before flashing twrp and katkiss. Is that the same as using NVFLASH? Or should I not wipe everything before flashing katkiss so that the partition is not touched? If so, what should I wipe before flashing?
2. I thought katkiss requires twrp >=2.3.2.3 . Easyflasher flashes a version lower than that. Am I correct to use goomanager under stock rom to update twrp to 2.3.2.3 before flashing katkiss?
3. If I want to try flashing katkiss from internal memory, where should I put the zip file and what should I not wipe before flashing?
Thanks

strikeraj said:
Thanks for your reply.
Just a couple questions
1. I have used easyflasher to flash stock before flashing twrp and katkiss. Is that the same as using NVFLASH? Or should I not wipe everything before flashing katkiss so that the partition is not touched? If so, what should I wipe before flashing?
2. I thought katkiss requires twrp >=2.3.2.3 . Easyflasher flashes a version lower than that. Am I correct to use goomanager under stock rom to update twrp to 2.3.2.3 before flashing katkiss?
3. If I want to try flashing katkiss from internal memory, where should I put the zip file and what should I not wipe before flashing?
Thanks
Click to expand...
Click to collapse
1.) Use NVFLASH to flash stock - Wipe everything in TWRP once you're ready for KatKiss
2.) TWRP that comes with Easyflasher will work, you can upgrade later
3.)Flash KatKiss from MicroSD so you can wipe everything on Internal

Going From 2.3.6 (Stock) to 4.4.4 (Carbon)

There's a lot of disparate information on how to do this so wanted to share what worked for me.
Heimdall was way better than Odin in recognizing and flashing ROM's. You need to watch a tutorial on youtube on how to use Heimdall manually in case you can't find a ROM in the right format (compressed as "tar.gz").
I used a rooted Gingerbread 2.3.6 ROM, which was packaged for Odin. Had to decompress the files and set them up manually in Heimdall for flashing.
Once Infuse 4G was running with root I downloaded/installed ROM Manager from Google Play and transfered the Carbon KitKat ROM 4.4.4 (2014-07-06) and GAPPS 4.4.2 (2014-06-06) ".zip" files to the root folder via USB cable from PC (phone connected as USB Mass Storage).
In ROM Manager you can select the ROM you want to install when the phone reboots. At some point I was able to also install GAPPS before finally booting to Carbon KitKat.

kikato said:
There's a lot of disparate information on how to do this so wanted to share what worked for me.
Heimdall was way better than Odin in recognizing and flashing ROM's. You need to watch a tutorial on youtube on how to use Heimdall manually in case you can't find a ROM in the right format (compressed as "tar.gz").
I used a rooted Gingerbread 2.3.6 ROM, which was packaged for Odin. Had to decompress the files and set them up manually in Heimdall for flashing.
Once Infuse 4G was running with root I downloaded/installed ROM Manager from Google Play and transfered the Carbon 4.4.4 KitKat ROM and GAPPS 4.2 ".zip" files to the root folder via USB cable from PC (phone connected as USB Mass Storage).
In ROM Manager you can select the ROM you want to install when the phone reboots. At some point I was able to also install GAPPS before finally booting to Carbon KitKat.
Click to expand...
Click to collapse
so how were you able to flash carbon and the gapps? why did you use 4.2 gapps with a 4.4.4 rom????

Used ROM Manager from Google Play to install latest versions of KitKat (2014-07-06) and GAPPS (2014-06-06) from Carbon website. ROM Manager can also install Clockworkmod Recovery.
Files for download at the website have no version numbers, but the phone showed upgrades for 4 of the Google applications.

kikato said:
Used ROM Manager from Google Play to install latest versions of KitKat (2014-07-06) and GAPPS (2014-06-06) from Carbon website. ROM Manager can also install Clockworkmod Recovery.
Files for download at the website have no version numbers, but the phone showed upgrades for 4 of the Google applications.
Click to expand...
Click to collapse
okay so you used rom manager to install CWM recovery.....and you selected to flash carbon via rom manager which then took you to the recovery then somehow you were able to flash the gapps.........but how was it able to directly flash on GB CWM version did you have to flash carbon rom twice in order to get the updated CWM version then flash carbon again to get the rom then flash the gapps then wipe cache and dalvik cache?
also you made a "root folder" in your sdcard?
PS. did you use heimdall one click or the more complicated version?

I can't say if the Carbon ROM was flashed twice, but it seems the phone rebooted more than once during the whole process (from rooted Gingerbread 2.3.6 to KitKat 4.4.4).
ROM Manager only requires to save ROM .zip file(s) in your phone SD card, read somewhere to use root folder or topmost location in SD card (not a folder named "root"), but you can use Recovery to select the location of the .zip file to install.
ROM Manager boots into Recovery to install .zip files, whether is Carbon ROM or GAPPS.
After the Carbon ROM was installed (and maybe a reboot), before booting into KitKat, I was in CWM Recovery and used the menu to install GAPPS.
Recovery has a "wipe data/factory reset" menu option.
Used Heimdall 1.4.0 to manually flash a rooted Gingerbread 2.3.6 ROM that was packaged for Odin, but there are other ways to root the phone.
It can take a while for KitKat to install so give it some time.

I thought you had to go to ICS before KitKat. Can you really go straight from GB to KK?
Also when I downloaded "Rom Manager" and tried to install CWM it did not list the Infuse as being supported for installing the CWM Recovery saying I had to find and install one manually.

SirAndroid said:
I thought you had to go to ICS before KitKat. Can you really go straight from GB to KK?
Click to expand...
Click to collapse
Apparently can be done as long as you disable lagfix.
SirAndroid said:
Also when I downloaded "Rom Manager" and tried to install CWM it did not list the Infuse as being supported for installing the CWM Recovery saying I had to find and install one manually.
Click to expand...
Click to collapse
CWM for the i9000 is supposed to be a valid substitute. I don't use the AT&T version of the Infuse (mine is Rogers), so it didn't work for me at first - still had to flash with ODIN.
Interestingly, as I remember after flashing with ODIN and rebooting into recovery, it was Blue CWM, not Red (which Red is what you usually get by flashing only the ODIN/Heimdall images).

I didn't have to install any other version before flashing KitKat, only had to root the phone. I rooted by flashing a "rooted" GB 2.3.6 ROM, but there are other ways to root the phone.
When I tried to install CWM Recovery with ROM Manager I got an error so I went ahead and flashed with whatever recovery the phone had.
Is possible the rooted GB 2.3.6 ROM had CWM Recovery already, or ROM Manager was able to install CWM Recovery after all (phone rebooted more than once, I kept trying until it worked ).
Read you must use "Samsung I9300 Galaxy S III" in ROM Manager since they have similar partitions.

ROM Manager no longer has the i9300 Galaxy S III option, but you only need to create a Recovery shortcut in Apex launcher and flash from a Carbon ROM .zip file (KK v4.4.4 nightly for Infuse 4G, dirty flashing with no wipes).
The Carbon ROM includes a Carbon Delta, which doesn't update nightlies (it always says "system is up to date").
Have not seen other KitKat kernels or TWRP touch for the Infuse 4G, currently using CWM Recovery 6.0.5.0.

Impossible to flash stock ROM

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