wondering of the install process with cm10 nightlies ? do i need to flash gapps with it or does it come with it? just wipe and flash correct?
Anytime u flash cm builds u will have to flash gapps also. just make sure u get the gapps for jb n not ICS. Yes just do three wipes then flash cm then gapps...
Sent from my SCH-I535 using Tapatalk 2
bruderhood15 said:
wondering of the install process with cm10 nightlies ? do i need to flash gapps with it or does it come with it? just wipe and flash correct?
Click to expand...
Click to collapse
Not sure about all other builds, but I unlocked my bootloader last night, and flashed dhackers latest build, for his you flash Gapps separately. But the process is very easy. are you coming from stock.?
Related
Okay so I'm stock rooted and unlocked and your not supposed to apply future otas because it'll brick the device.
Since there are no stable versions of jelly bean that's kinda outta the question for me.
If there is ever updates. Radio. Rom. Etc. Can I just download and directly flash through cwm? Will I have to wipe cache and dalvik? How do I reinact a ota updates through cwm
Sent from my SCH-I535 using Tapatalk 2
imablackhat said:
Okay so I'm stock rooted and unlocked and your not supposed to apply future otas because it'll brick the device.
Since there are no stable versions of jelly bean that's kinda outta the question for me.
If there is ever updates. Radio. Rom. Etc. Can I just download and directly flash through cwm? Will I have to wipe cache and dalvik? How do I reinact a ota updates through cwm
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I'll take a stab at this:
I tried the JB roms but a little buggy for now, I'm sure they'll be stable as soon as the stable version of CM is released. For now I run Bean's custom stock rom build 10.
Root your device, unlock boot-loader and flash CWR 6.0.1 or 2 as you recovery. Now you can flash any roms you want. My method is as follows :
1- make a Nandroid back up, either from CWR menu or rom manager. Then use tit backup to backup all my downloaded apps.
2- go to recovery and wipe cache,data, system, and dalvik
3-pick a zip file from sd card
4- flash bean's rom
5- restore all my downloaded apps
6- profit
Going from Bean ver 9 to 10 I only wiped cache and dalvik. Wipe all if dev is asked for it or going from rom to rom, but only these two if you are going to a different version on the same rom.
+1 for beans.
+2 for beans as well. And don't worry, there will be stable builds of JB wayy before verizon sends out an ota of JB.
I just donno if verizon will make another ota for ics or release radio updates to fix some issues.. All I know is since my phone is like this I can't take any updates haha.
Sent from my SCH-I535
imablackhat said:
I just donno if verizon will make another ota for ics or release radio updates to fix some issues.. All I know is since my phone is like this I can't take any updates haha.
Sent from my SCH-I535
Click to expand...
Click to collapse
And how, pray tell, are you controlling whether or not you get updated? My understanding is a stock ROM will automatically accept OTA updates without prompt. sounds like a brick waiting to happen.
Stock roms have always prompted me in the past to update. Is it true they no longer prompt and auto install? Idk I really doubt that.
Sent from my SCH-I535
If you have a custom recovery, an ota will fail
And another vote for Beans!
Stock rom will not force ota without me being able to decline though. Right?
That's my main concern...
Sent from my SCH-I535
I just flashed the latest stable CM10 and it is working well. If I were to flash a new ROM, do I have to flash a new boot.IMG for it to work? And if I were to update my CM10, do I need to flash the new boot.IMG in the new update?
Sent from my One X using xda premium
If you are on ATT version 2.20, yes you need to flash the boot.img when you flash a new rom.
You shouldn't need to when upgrading CM10, however, but if there are kernel changes you may want to, to take full advantage.
area51avenger said:
If you are on ATT version 2.20, yes you need to flash the boot.img when you flash a new rom.
You shouldn't need to when upgrading CM10, however, but if there are kernel changes you may want to, to take full advantage.
Click to expand...
Click to collapse
Then while doing so, do I need to full wipe or just wipe cache and dalvik?
Sent from my One X using xda premium
For going from ics <-> aosp full wipe
For just upgrading CM10, cache and dalvik should be enough
No matter what ROM I'm on, or the compatible custom kernel I try to flash with whatever ROM I'm using at that time, I am still yet to have a successful flash of a kernel without rebooting the device only to have to pull my battery because it boots the first screen and then goes black and flashes the red LED, forcing me to restore to a backup I made prior.
I am running the most updated version of Liquidsmooth, and the most updated versions of CWM/TWRP. Any suggestions or possible causes? I always wipe cache/dalvik and fix permissions like I previously read was required in other threads.Thanks in advance!
StayingSober said:
No matter what ROM I'm on, or the compatible custom kernel I try to flash with whatever ROM I'm using at that time, I am still yet to have a successful flash of a kernel without rebooting the device only to have to pull my battery because it boots the first screen and then goes black and flashes the red LED, forcing me to restore to a backup I made prior.
I am running the most updated version of Liquidsmooth, and the most updated versions of CWM/TWRP. Any suggestions or possible causes? I always wipe cache/dalvik and fix permissions like I previously read was required in other threads.Thanks in advance!
Click to expand...
Click to collapse
What kernels did you flashed? And with what ROM?
If you are on liquid 2.2 I believe it need a aosp 3.4 kernel. I know the latest BMS kernel works. But the latest KT747 will not work unless you are using a new nightly of liquid 2.3. Be sure to wipe cache and dalvik cache after flashing but before rebooting.
Sent from my SCH-I535 using xda app-developers app
jmxc23 said:
What kernels did you flashed? And with what ROM?
Click to expand...
Click to collapse
Basically tried flashing any compatible kernel with the ROM I was running at the time. For example yesterday I tried flashing the KT747 kernel for Jellybean with the current ROM I'm running, which is the most recent Liquidsmooth 4.2.2 ROM. Still no success
Here is the latest liquid...
Nightly Builds 04/29/13 for d2att, d2spr, d2tmo, and d2vzw available on GooInsideMe
http://goo.im/devs/liquidsmooth/nightly/042913 These Builds Are Very STABLE!
View changes & bug fixes made to our source code here http://github.com/LiquidSmooth
This is quoted from liquid0624 in the liquid smooth thread.
Sent from my SCH-I535 using xda app-developers app
redKrome said:
If you are on liquid 2.2 I believe it need a aosp 3.4 kernel. I know the latest BMS kernel works. But the latest KT747 will not work unless you are using a new nightly of liquid 2.3. Be sure to wipe cache and dalvik cache after flashing but before rebooting.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Sorry for taking forever to reply, I originally posted this on my lunch break and am finally out of work to reply freely. Anyways, I tried what you said, and downloaded the BMS 3.4 kernel that states is compatible with the version of Liquidsmooth 4.2.2 I am running. Let's just say I yet again had to restore twice once because it did exactly what I stated above, where it gives me the splash screen saying it's running the custom kernel and doesn't boot any further after the Galaxy S3 screen. The first time, I flashed it and then wiped cache/dalvik and fixed permissions before booting up like everyone says you need to do after flashing a kernel, no success.
Then, I read in the kernel's thread that there is no need to do that for this most up to date release, it says you just have to flash the kernel and reboot like with any other zip file. Well that didn't work either, and was forced to restore a backup a second time! What could the problem be?! I'm using the most updated version of TWRP, I'm on the most updated nightly of the Liquidsmooth ROM, I'm using a highly confirmed working and compatible kernel, and following the directions to the T! When it comes to flashing a different ROM, modem, rpm, backup, etc. I have no problem whatsoever. But trying to flash a kernel has never been successful for me so far
Any help from anyone else? It's frustrating that I've never been able to flash any kernels to any ROM I've ever run
Sent from my Samsung SCH-I535 running Liquidsmooth 4.2.2
Im no expert on any of this but this is what i would do. Odin back to stock ROM and reroot and unlock bootloader. Id do this cause i would want a clean slate so i know there is no previous kernel/rom files that may be effecting something. Make a new nandroid backup then reflash the rom ya want to use. Once booted up and everything is running, restart the phone and boot into recovery. Wipe the dalvik and cache like normal then flash the kernel. Hopefully that would take care of the problem.
Only other thing i can think of is to maybe wipe data/factory reset like 2 or 3 times and wipe the caches again and reinstall your current rom. Then flash the kernel. Other than that im out of ideas. Hopefully someone can get your problem solved!
Sent from my SCH-I535 using xda premium
Hello. on one of my other phones I got cyanogenmod and when a new nightly rom comes out the phone gets a update OTA like normal phones does but how do I update AOKP nightly on my phone to the newest wersion without having to flash like a new. I am on Nexus 5 4.2.2
There is an app called AOKPush https://play.google.com/store/apps/details?id=info.sethyx.aokpush
Sent from my HammerHead
You don't need to wipe anything to update, you can just download the zip and flash it in recovery.
Sent from my Nexus 5
Thomaslje said:
Hello. on one of my other phones I got cyanogenmod and when a new nightly rom comes out the phone gets a update OTA like normal phones does but how do I update AOKP nightly on my phone to the newest wersion without having to flash like a new. I am on Nexus 5 4.2.2
Click to expand...
Click to collapse
I also recommend Goo Manager, it has some OTA feature that might work.
Pirateghost said:
You don't need to wipe anything to update, you can just download the zip and flash it in recovery.
Sent from my Nexus 5
Click to expand...
Click to collapse
Yes and I need mannualy to go into recovery I dont need to do that on my CM edition
ranarn said:
I also recommend Goo Manager, it has some OTA feature that might work.
Click to expand...
Click to collapse
I will try that.
Thomaslje said:
Yes and I need mannualy to go into recovery
Click to expand...
Click to collapse
This is not a chore. Besides, you need to boot into recovery before taking your pre-flash nandroid backup
Sent from my Nexus 5 using Tapatalk
Hi There,
My Atrix 2 is running on Slimkat 4.4.3.build.5.9, while trying to update the same via OTA getting error as Can not read SlimOTA properties.
Pls help!!!!!!
Thanks in advance!
Atrix2dBeast said:
Hi There,
My Atrix 2 is running on Slimkat 4.4.3.build.5.9, while trying to update the same via OTA getting error as Can not read SlimOTA properties.
Pls help!!!!!!
Thanks in advance!
Click to expand...
Click to collapse
No one can help you. Because atrix 2 is not officially supported by slim team.
Sent from my MB865 using XDA Premium 4 mobile app
Can not read SlimOTA properties!!
noranora said:
No one can help you. Because atrix 2 is not officially supported by slim team.
Sent from my MB865 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Okay......thanks for the reply. But then how can I update it to 4.4.4 Build 6.0 without Format/Wiping data?
Pls help @alteredlikeness
Atrix2dBeast said:
Okay......thanks for the reply. But then how can I update it to 4.4.4 Build 6.0 without Format/Wiping data?
Click to expand...
Click to collapse
Ideally you should wipe everything and then clean install the ROM. To retain your data and apps, you can take backup using titanium backup or take backup of data partition using BMM then restore (though I am not too sure about BMM method if it really works perfectly).
If you don't want to wipe then you can try to dirty flash the 6.0 ROM on the existing version. Just don't perform format or wipe, just flash the ROM+Gapps. see If it goes well.
Can not read SlimOTA properties!!
Jack Sparrow xda said:
Ideally you should wipe everything and then clean install the ROM. To retain your data and apps, you can take backup using titanium backup or take backup of data partition using BMM then restore (though I am not too sure about BMM method if it really works perfectly).
If you don't want to wipe then you can try to dirty flash the 6.0 ROM on the existing version. Just don't perform format or wipe, just flash the ROM+Gapps. see If it goes well.
Click to expand...
Click to collapse
Okay...that means there is no way to get OTA update:crying:.........anyways...thanks a lot for replying!
Atrix2dBeast said:
Okay...that means there is no way to get OTA update:crying:.........anyways...thanks a lot for replying!
Click to expand...
Click to collapse
Even if there is OTA support in the ROM then also it doesn't mean that the phone will be updated automatically like how it happens in case of official firmware updates. The OTA in most of the custom ROMs just downloads the ROM file on your phone, thats it. Rest you will have to manually install/flash the ROM using that downloaded file like how you maybe doing it now. OTA just cuts the step of finding and downloading the ROM file from internet. So IMO its not a feature which matters much.
Ok bro...thanks a lot for sharing the info and for the timely response...
Sent from my MB865 using XDA Free mobile app
Can not read SlimOTA properties!!
Jack Sparrow xda said:
Ideally you should wipe everything and then clean install the ROM. To retain your data and apps, you can take backup using titanium backup or take backup of data partition using BMM then restore (though I am not too sure about BMM method if it really works perfectly).
If you don't want to wipe then you can try to dirty flash the 6.0 ROM on the existing version. Just don't perform format or wipe, just flash the ROM+Gapps. see If it goes well.
Click to expand...
Click to collapse
Tried dirty flashing...it worked...post booting found that gapps were not working....so flashed latest gapps again...now its rebooting again n again....what to do??
Atrix2dBeast said:
Tried dirty flashing...it worked...post booting found that gapps were not working....so flashed latest gapps again...now its rebooting again n again....what to do??
Click to expand...
Click to collapse
Perhaps it's time for you to clean flash? Idk. Sounds like it's bootlooping. 5.9 gapps was 4.4.3. Meanwhile version 6 is 4.4.4. Sometimes its best for you to start afresh to avoid any issue.
Sent from my MB865 using XDA Premium 4 mobile app
Atrix2dBeast said:
....so flashed latest gapps again...now its rebooting again n again....what to do??
Click to expand...
Click to collapse
No option other than clean install. That type of issue why its always recommended to clean flash the newer versions.
To have little bit of hope, backup the data partition using BMM then later try to restore the data partition using that backup once you successfully flash the ROM. If it works then all is good and if it doesn't then....
Can not read SlimOTA properties!!
Jack Sparrow xda said:
No option other than clean install. That type of issue why its always recommended to clean flash the newer versions.
To have little bit of hope, backup the data partition using BMM then later try to restore the data partition using that backup once you successfully flash the ROM. If it works then all is good and if it doesn't then....
Click to expand...
Click to collapse
Okay....flashed 4.4.4 built 6 again(clean install)...rebooted...and then flashed gapps for the same build....but again its rebooting....had to fxz again...what i am doing wrong here???
Atrix2dBeast said:
Okay....flashed 4.4.4 built 6 again(clean install)...rebooted...and then flashed gapps for the same build....but again its rebooting....had to fxz again...what i am doing wrong here???
Click to expand...
Click to collapse
What are the steps you are following? Are you flashing using BMM? Which system? What GApps version? Try not to reboot between ROM and GApps flashing. Flash only minimal GApps.
I haven't faced any such issue with any of the ROMs so far. I just follow the BMM guide word to word.
Right now I am having 5.10 build and its pretty much stable and almost bug-free for me on System 1. There are few experiments going on in the builds after 5.10 so I would recommend you should also flash the 5.10 build.
Can not read SlimOTA properties!!
Jack Sparrow xda said:
What are the steps you are following? Are you flashing using BMM? Which system? What GApps version? Try not to reboot between ROM and GApps flashing. Flash only minimal GApps.
I haven't faced any such issue with any of the ROMs so far. I just follow the BMM guide word to word.
Right now I am having 5.10 build and its pretty much stable and almost bug-free for me on System 1. There are few experiments going on in the builds after 5.10 so I would recommend you should also flash the 5.10 build.
Click to expand...
Click to collapse
I am using BMM only....on system 1...made a mistake of rebooting between ROM and GApps flashing.:silly: