I'm running CyanogenMod 10.1.3 RC2 on my One X. If I try to update to 10.2 nightlies the phone goes in to continual reboot. I can then revert back but do I need to do something else to update to 10.2?
did you flash the kernel included inside the 10.2 rom after you flashed the rom.zip from recovery?
if you have flashed the kernel try to wipe data partition.
I hadn't flashed the kernel. It wasn't clear that you had to do this so I can try it later. Thanks
Would updating to CM 10.2 wipe all apps from my phone? Just wondering how long to allow myself before starting
In my experience when i install an update of the same rom i can not flash the kernel, but when i change rom (for example from 10.1 to 10.2), i flash the kernel and wipe data and cache
Is that a full data wipe/factory reset? In other words, delete all data?
Yes
Sent from my HTC One X using XDA Premium 4 mobile app
Actually it wasn't, I just hadn't flashed boot.img
Update 24e
Hallå... After The update This morning i run in to a problem.. Android. Com stopped something.. First and I think I need to flash gapps again but it doesn't help, so I need to run my backup and restore it to the 20th nightly... Is there a new gapps or what?
Related
Howdy y'all!
I'm currently running a 4.1.1 ROM, and would like to get on to MMuzzy's 4.2, but there are a ton of things I think I need to flash and want to make sure I get the order right. Your help will be much appreciated!
I am already using the latest version of TWRP.
I would like to flash the latest JB bootloader, and latest JB radios, but have never flashed either. Should I do these before flashing the ROM, or after? Should I do these before formatting cache? Should I format system or factory reset before flashing these, too?
I am planning to do factory reset, format cache and dalvik before flashing ROM, gapps and kernel. Do I need to do anything else to prep for flashing the ROM? Also, is it okay to flash all three at once, or should I do rom and gapps, let everything boot and restore from market, and only then flash kernel?
My main concern is the differences in file system between 4.1 and 4.2. I'm aware of the /0 subdirectory thing already, but I'd there anything else?
Thanks much!
Jamie
I wouldn't bother with the bootloader, but if you insist then you can flash the bootloader and the radios before or after. Doesn't matter.. Other than that, you do them ROM, gapps, kernel and I've done all three at once. Mmuzzy's is a good ROM. Enjoy.
First make a backup in TWRP
Factory reset
Wipe both caches
Install ROM, gapps, then kernel and reboot. (All at the sometime in that order)
I have heard its better to flash the kernel with the new ROM so just do it all in one flash.
Set everything up and let your phone sit for 15 minutes untouched and go for it.
Sent from my Galaxy Nexus using xda app-developers app
jrbedford said:
My main concern is the differences in file system tree between 4.1 and 4.2. I'm aware of the /0 subdirectory thing already, but I'd there anything else?
Thanks much!
Jamie
Click to expand...
Click to collapse
Just a small correction; file system change would mean switching from ext4 to f2fs, for example. That's not the case.
MartianCeo said:
First make a backup in TWRP
Factory reset
Wipe both caches
Install ROM, gapps, then kernel and reboot. (All at the sometime in that order)
I have heard its better to flash the kernel with the new ROM so just do it all in one flash.
Set everything up and let your phone sit for 15 minutes untouched and go for it.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Watch out with restoring backups. Don't restore app/system data. OP is switching major versions.
sent from my Google Galaxy Nexus
I have a Galaxy s3 rooted So I was ble to flash the newest nightly cb 10.1 before the one that came out today. I want to try out the one that came out today however I am confused about something. I know i have to flash the rom and delete data and cache during recovery mode and what not. What step do i need to take so that when i do flash thi snew rom i dont have to manually re install all my apps and configure my phones layout again?/
You can try dirty flashing by just clearing cache and dalvike cache after you flash the new nightly. This method won't affect any of your apps or settings. If you get any weird bugs from dirty flashing, try clean flashing (which wipes pretty much everything) before reporting any bugs. If you have to clean flash then you can backup your apps with Titanium Backup.
Less than a week ago, I was able to flash cm-10.2-20130917-NIGHTLY-d2tmo.zip onto my girlfriend's Galaxy S III. She hates when I update her phone because it means I have to wipe everything and she has to start from scratch by signing into Google again, signing into all her Wi-Fi connections, re-downloading apps and signing in, etc.........
Now because I installed a nightly, that means there will obviously be a new update from CyanogenMod every 1-2 days.
My question is..
Is there a way I can update her phone with each nighty without having to do a full wipe on her phone and instead just "updating" the ROM without having to wipe everything? Can someone please provide me with the steps? I'm sure if it's possible, it's very easy. I just don't know myself. Thank you in advanced.
The phone is a T-Mobile Galaxy S III (SGH-T999) and it has ClockworkMod Recovery v6.0.3.7
As long as you stay with the same version, CM10.1 or CM10.2, you can dirty flash (without wiping all of the user data.
DJ_SpaRky said:
As long as you stay with the same version, CM10.1 or CM10.2, you can dirty flash (without wiping all of the user data.
Click to expand...
Click to collapse
By dirty flash, do you mean:
1) Reboot into recovery
2) Perform backup
3) Install ZIP (then choose the newly downloaded nightly
4) Reboot
Basically skip the step where I would perform a data wipe?
thatboyjay said:
By dirty flash, do you mean:
1) Reboot into recovery
2) Perform backup
3) Install ZIP (then choose the newly downloaded nightly
4) Reboot
Basically skip the step where I would perform a data wipe?
Click to expand...
Click to collapse
Yes, but it doesn't hurt to wipe cache/dalvik and fix permissions while you are in there, and don't forget to flash GApps too.
I'd say just flash the stable release.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Is anyone having an issue with the new D2LTE builds that have been built recently?
I have tried to flash a few (carbon and c-rom) and just get stuck at kernel splash page. I am on the newest TWRP(2.7), the lk3 modem/bootloader and wiped data,cache, dalvik, and reformatted my internal sd card.
If anyone else is experiencing this, what was done to resolve it?
Edit: I have now also tried
1. Restoring to original stock touchwiz 4.1.1
2. Wiping cache from original recovery
3.Rerooting
4.Restoring a backup of 4.3
5.Attempted to update to C-Rom, Carbonrom, Resurrection Remix -- No Luck Fails
Corvetrims77 said:
Is anyone having an issue with the new D2LTE builds that have been built recently?
I have tried to flash a few (carbon and c-rom) and just get stuck at kernel splash page. I am on the newest TWRP(2.7), the lk3 modem/bootloader and wiped data,cache, dalvik, and reformatted my internal sd card.
If anyone else is experiencing this, what was done to resolve it?
Click to expand...
Click to collapse
I'd like to know myself. I'm stuck too. I can flash a 4.3 rom and everything works, but when I reboot, it gets stuck. All was fine until I flashed Wicked rom and flashed " MJ2 bootloader MJB" Now every time I reboot it gets stuck. Also If I try a reflash, the only way to get it to bootup is to format before flashing.
Try using Philz Touch as your recovery program.
audit13 said:
Try using Philz Touch as your recovery program.
Click to expand...
Click to collapse
I had cwm when I originally started out, switched to twrp to see if the recovery was the issue.
I assume you were running the latest version of cwm before you switched to twrp so it can't be the recovery.
Are you doing a full wipe of the system, cache, data, and Dalvik before installing the ROM?
Yea every time I wiped data, cache, dalvik , I even reformatted once. I have managed to boot up into tasl650AOKP which is a d2lte build but no other ROMs. I mean at this point it looks like I should just wait a bit to see if it is something with the ROMs interacting with my phone(as per all phones are made different)
Sent from my d2lte using Tapatalk
Are you wiping the system before installing? Have you tried wiping system, dalvik, data, cache, install the rom, wipe and re-install the same ROM a second time without trying to boot the ROM in between the 1st and 2nd ROM install?
audit13 said:
Are you wiping the system before installing? Have you tried wiping system, dalvik, data, cache, install the rom, wipe and re-install the same ROM a second time without trying to boot the ROM in between the 1st and 2nd ROM install?
Click to expand...
Click to collapse
Yeah I gave it a shot still no dice. I keep seeing other people having similar issues, so I am still leaning it has to do with the differences in d2lte builds vs dtatt builds
Sent from my d2lte using Tapatalk
d2att ROMs are okay? Just not any d2lte?
audit13 said:
d2att ROMs are okay? Just not any d2lte?
Click to expand...
Click to collapse
As I stated before I am able to boot int Task650AOKP(Which is a d2lte build), any of the others that I have tried have not worked. There are some updates out today, I am going to attempt again and post back results.
As a test, I flashed my i747m back to stock 4.1.2 via Odin. I then installed the latest version of Philz Touch for the d2lte and installed the d2lte version of Validus. Validus booted without any problems.
Edit: just tried the lastest nightly Pac-Rom and Resurrection ROM. Both ROMs had no problem booting to the desktop.
audit13 said:
As a test, I flashed my i747m back to stock 4.1.2 via Odin. I then installed the latest version of Philz Touch for the d2lte and installed the d2lte version of Validus. Validus booted without any problems.
Edit: just tried the lastest nightly Pac-Rom and Resurrection ROM. Both ROMs had no problem booting to the desktop.
Click to expand...
Click to collapse
Thanks for the help, I actually was just able to boot into C-Rom by following the same steps except I am using TWRP. No idea really what caused the Roms to get stuck on boot. Quite annoying.
I had TWRP on my phone but I was having problems installing ROMs when I first got the phone in January.As soon as I switched to CWM or Philz, no problems at all except for ROMs based on a stock 4.3 ROM.
got CM 12.1 release installed on my sgh-t999 and am wanting to update to latest 12.1 nightly, do I just wipe cache/dalvik and then flash via twrp and then flash gapps or should I wipe data as well and then flash? also, do I need to flash gapps every time I flash a new nightly?
You can try dirty flashing the new nightly over the old nightly. There should be no need to perform a full wipe and re-install gapps unless you have altered the old nightly to much to let a dirty flash work.
I understand about dirty flashing one nightly over the next, but was curious if it was any different flashing a nightly over a 'release'
Nope, should not make any difference.
So I don't have to wipe cache or dalvik? Just flash?
Yup. If it doesn't boot, you may gave to perform a full wipe before installing.