I haven't had much time to play around with my phone since cm 9.1.0 stable and have been out of it for a while.
I would like to confirm a couple of things about upgrading to the latest 10.1 nightly.
I currently have CWM 5.5.0.4 loaded. What is the procedure to update to the latest CWM Touch? Is the procedure the same as installing it on an unmodified phone?
Is my checklist for upgrading cm9.1.0 to the latest 10.1 nightly accurate?:
- Boot into Recovery
- Flash CM10.1 zip from SDCard
- Flash GApps zip from SDCard
- Reboot
- Wipe data of clock app
- Reset everything under Settings -> Date & Time otherwise editing alarms might cause FCs
Do let me know if I'm missing any steps.
just flash the recovery via Odin or recovery.
you're missing the fact that you have to wipe data before you flash
Well this is what I did to upgrade in case anyone wants to know:
- boot into download mode, flash cwm touch via odin
- ooot into recovery mode, flash cm10.1, gapps
- data wipe/factory reset
done!
still gets stuck on reboot after flashing the new rom. just remove battery and power on and ur good to go!
yes, that's what I said
Related
About a month ago I wanted to try out CM7 and see what it's worth.
I went to this thread: http://forum.xda-developers.com/showthread.php?t=1176411
I was using a stock GB ROM and rooted with CF-root kernel.
I downloaded the stable build and followed these instructions:
Install via ClockworkMod (do not use ROMManager for initial install):
1.Make sure you're running a rooted device.
2.Root your device and install ClockworkMod Recovery (http://forum.xda-developers.com/show....php?t=1118693)
3.Do a Nandroid backup!
4.WIPE (wipe data/factory reset + wipe cache partition) - do it for real.
5.Install the ROM from internal sdcard using ClockworkMod Recovery.
6.Do not reboot! We mean it - do nothing except choose zip and continue next step (if you come back to us with permission issues in install, we will know you did not read the directions and will call you an idiot). If it just plain hangs, reboot directly back into ClockworkMod recovery and continue at the next step.
7.Install the ROM from internal sdcard using ClockworkMod Recovery, again (due to a bug in the install).
8.Reboot
9.Install the Google Addon through ROMManager which is easiest, but you can
download the gapps.zip and install via ClockworkMod recovery instead.
Click to expand...
Click to collapse
When My phone booted it got into a bootloop.
I could not boot into recovery, I could only boot into download mode.
I searched the web and on one forum website I saw that someone encountered the same problem and after he encountered the bootloop he booted into download mode and flashed Siyah Kernel via Odin and his phone booted successfully.
I followed what he did and my phone booted into CM7.
After that I went on to other ROMs.
Two days ago I was running CM9 and I wanted to flash to CM7, so I downloaded CM7 nightly build #115 and did the following:
1) My phone was rooted with CWM. (CM9)
2) Wiped data, cache and dalvik.
3) Flashed the ROM twice.
4) Flashed GAPPS.
5) Rebooted.
6) "Samsung Galaxy S II with !" Screen.
7) "Kernel Panic" screen.
8) Took battery out.
*Tried booting into CWM with no success.
9) Booted.
10) Stages 6, 7 & 8.
11) Booted into download mode.
12) Flashed siyah kernel via odin.
13) CM7 working!
So there is my story!
I have also seen other people with the same problem, so it is not just me.
And here are my questions:
1) Why did these problems happen (kernel panic or bootloop)?
2) Why does Siyah Kernel fix these problems?
3) How can I prevent the bootloop/kernel panic from happening in the future (without flashing Siyah)?
Seconding the question as well as noting that it also occurs with Arif-Ali's nightly compiles.
did you wipe cache and dalvik cache after flashing cm7?
golcheck said:
did you wipe cache and dalvik cache after flashing cm7?
Click to expand...
Click to collapse
No, you dont need.
golcheck said:
did you wipe cache and dalvik cache after flashing cm7?
Click to expand...
Click to collapse
I did. I tried "messing" with CWM any which way and even flashed a stock rom in odin (and appropriate CF root). Nothing short of flashing Siyah (and probably any other kernel that supports CM7 except the one in the update zip) lets CM7 boot.
Net.silb said:
About a month ago I wanted to try out CM7 and see what it's worth.
I went to this thread: http://forum.xda-developers.com/showthread.php?t=1176411
I was using a stock GB ROM and rooted with CF-root kernel.
I downloaded the stable build and followed these instructions:
When My phone booted it got into a bootloop.
I could not boot into recovery, I could only boot into download mode.
I searched the web and on one forum website I saw that someone encountered the same problem and after he encountered the bootloop he booted into download mode and flashed Siyah Kernel via Odin and his phone booted successfully.
I followed what he did and my phone booted into CM7.
After that I went on to other ROMs.
Two days ago I was running CM9 and I wanted to flash to CM7, so I downloaded CM7 nightly build #115 and did the following:
1) My phone was rooted with CWM. (CM9)
2) Wiped data, cache and dalvik.
3) Flashed the ROM twice.
4) Flashed GAPPS.
5) Rebooted.
6) "Samsung Galaxy S II with !" Screen.
7) "Kernel Panic" screen.
8) Took battery out.
*Tried booting into CWM with no success.
9) Booted.
10) Stages 6, 7 & 8.
11) Booted into download mode.
12) Flashed siyah kernel via odin.
13) CM7 working!
So there is my story!
I have also seen other people with the same problem, so it is not just me.
And here are my questions:
1) Why did these problems happen (kernel panic or bootloop)?
2) Why does Siyah Kernel fix these problems?
3) How can I prevent the bootloop/kernel panic from happening in the future (without flashing Siyah)?
Click to expand...
Click to collapse
I fixed it.
This is how:
1. Make a CWM Backup.
2. Use Odin to flash I9100XXKI3, including the PIT (re-partition)
3. Flash this kernel (PDA section) and the old Bootloader (Bootloader section) with Odin.
4. Boot into CWM recovery and flash cm7+gapps.
5. Use Advance Restore in CWM to restore your /data partition if you want to.
I'm 90% certain that the problem was ICS's partition layout (PIT file).
Hello!
This is my problem:
Yesterday i tried to install my first AOSP, CarbonRom 1.5. Installed last Philz recovery, nandbackuped, wiped data and cache, dalvik, formatted system and preload, and installed the ROM. NOT BOOTING. I HAVE A BOOTANIMATION LOGO LOOP.
OK. Going to try with CWM recovery. SAME! Siyah recovery, SAME TOO!
Ok, is the ROM file.
Cyanogenmod, SAME! AOKP, SAME! Carbon 1.4b, SAMEEEE!!! (of course with a fullwipe before install any ROM...)
However, all stock based ROMs are working fine. From ODIN, from recovery, all working fine. Stock nandbackup wirking too.
Is an august international Galaxy SIII.
Any idea?
Thanks XDA!
Just making sure you're following the instructions right after flashing a rom (Below is for CM10.1) you are doing the data wipe/factory reset as it tells you in the instructions (below underlined and in red)
First time installing CyanogenMod 10.1 to your Galaxy S III, or coming from another ROM:
- Read known issues ans FAQs
- Make sure you're running a proper working ClockworkMod-Recovery
- Copy GApps and CM10.1 ZIPs to your SDCard
- Boot into Recovery
- Flash CM10.1 zip from SDCard
- Flash GApps zip from SDCard
- DO A DATA WIPE / FACTORY RESET (otherwise your device will be stuck at boot)
- Reboot
- Don't restore system data using Titanium Backup!
- Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!
Hi, I'm getting stuck at the black screen just before the boot animation (the one that says "samsung galaxy SIII gt-i9300"), after flashing custom rom via CWM. Maybe I'm a complete noob but I think something is wrong in my phone.
I had installed MIUI official before, then removed it to get warranty back and sent phone to samsung service to fix the my broken simcard compartment.
After getting my phone back, I tried to install MIUI again and got stuck.
The strange thing is how fast ROM is installed in CWM, less than 10 seconds...
No error message and says install is complete
have retried 7 times now, using this:
- Odin 3.04
- CF-Auto-Root (http://forum.xda-developers.com/showthread.php?t=1957273)
- CF-Root 6.4 - SuperSU+CWM5.5+CWMManager (http://forum.xda-developers.com/showthread.php?t=1695238)
- ClockworkMod Touch 6.0.3.2 (http://forum.xda-developers.com/showthread.php?t=1719744)
- ClockworkMod 6.0.3.6 - Touch and Non-Touch (http://forum.xda-developers.com/showthread.php?t=2200501)
ROMs:
- MIUI Official 3.8.16
- MIUI Official 3.7.12
- CyanogenMod 9.1.0 (stable)
what I do:
- boot to bootloader
- flash CF root with Odin (Auto reboot and F.reset Time are checked)
- reboot, then shutdown
- boot to bootloader
- flash CWM with Odin (Auto reboot and F.reset Time are checked) also tried to install with ROM manager
- reboot, then shutdown
- boot to recovery
- wipe data/ factory
- wipe cache
- wipe dalvik
- install zip from sdcard (internal) <-- strange thing here is how fast it is installed, less than 10 seconds...
- wipe data/ factory, cache, dalvik again
- reboot
- got stuck.
- flash samsung stock ROM I9300UBALE6_I9300ZTOALE7_ZTO (brazilian 4.0.4, phone was in that version when installed MIUI first time)
Don't know what to do now, please help!
Does it boot with stock roms?
Please DO NOT flash anything older than 4.1.2 stock...
If all zips opnly take 10 seconds, perhaps theyre getting corrupt on your memory. How are you getting the zips on your phone?
rootSU said:
Does it boot with stock roms?
Please DO NOT flash anything older than 4.1.2 stock...
If all zips opnly take 10 seconds, perhaps theyre getting corrupt on your memory. How are you getting the zips on your phone?
Click to expand...
Click to collapse
yes, it boot with stock rom.
I just copy/paste files from windows, always done that, but now that you say, md5 is diferent...
I'll check stock ROM and file copy.
Thanks!
It was the file copy messing with the zip...
used adb push and all OK now!
Thanks again!
Anyone else have problems flashing to a 4.3 ROM? (I know some people do because I've searched.)
No matter what ROM it is, if it is 4.3 it will always fail to reboot a second time after it has been flashed.
Currently on CleanROM ACE 4.9 (4.1.2) with TWRP 2.6.0.1
I've tried to go to CM10.2 and it would reboot initially but then hang on the Note II logo if I tried to reboot.
I've tried to go to Paranoid Android.. same thing.
I've tried to go to PAC-man.. same thing.
I've tried flashing from the stock 4.1.2 ROM and the same thing happens.
I've followed every instruction I could find including this: http://forum.xda-developers.com/showthread.php?t=2423057
I do a factory reset, format data, flash ROM, wipe caches, flash gapps, wipe caches, reboot. It will boot fine from TWRP and load everything normally. Then, if I reboot or power off the device, it will hang on the Note II screen and I have to nandroid back to my previous ROM.
Any insight as to why this is happening? I haven't been able to find anything besides some random instructions for wiping/flashing (which I've linked). These ROMs look great and I'd really like to move to 4.3, but I cannot figure out what the problem is.
BigBoy275 said:
Anyone else have problems flashing to a 4.3 ROM? (I know some people do because I've searched.)
No matter what ROM it is, if it is 4.3 it will always fail to reboot a second time after it has been flashed.
Currently on CleanROM ACE 4.9 (4.1.2) with TWRP 2.6.0.1
I've tried to go to CM10.2 and it would reboot initially but then hang on the Note II logo if I tried to reboot.
I've tried to go to Paranoid Android.. same thing.
I've tried to go to PAC-man.. same thing.
I've tried flashing from the stock 4.1.2 ROM and the same thing happens.
I've followed every instruction I could find including this: http://forum.xda-developers.com/showthread.php?t=2423057
I do a factory reset, format data, flash ROM, wipe caches, flash gapps, wipe caches, reboot. It will boot fine from TWRP and load everything normally. Then, if I reboot or power off the device, it will hang on the Note II screen and I have to nandroid back to my previous ROM.
Any insight as to why this is happening? I haven't been able to find anything besides some random instructions for wiping/flashing (which I've linked). These ROMs look great and I'd really like to move to 4.3, but I cannot figure out what the problem is.
Click to expand...
Click to collapse
First time installing CyanogenMod 10.2 to your Galaxy Note 2 I605, or coming from another ROM:
- Read known issues ans FAQs
- Flash the latest official ClockworkMod-Recovery
- Copy GApps and CM10.2 ZIPs to your SDCard
- Boot into Recovery
- Flash CM10.2 zip from SDCard
- Flash GApps zip from SDCard
- DO A DATA WIPE / FACTORY RESET (otherwise your device will be stuck at boot)
- Reboot
- Don't restore system data using Titanium Backup!
- Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!
read the OP for CM 10.2 next time....
First - clockworkmod not twrp for 4.3 usually fixes things
Second - do a factory reset AFTER installing
Third - Dont restore apps with TiBu going to 4.3
Next time be truthful when you say you read and searched.
I have updated my galaxy s2 with cyanogenmod 13 and with gapps nano.
To install gapps without problems, I followed this steps:
1-reboot in philz recovery mode
2-Install cyanogen rom ( don't reboot)
3- Install gapps nano
4-Reboot
Now I would like to update cyanogen with nightly update without lose data. I tried to use cyandelta but some errors appear ( permission denied..)
I rebooted in recovery and now I have a clockwork recovery.
Can I install the nightly update with this recovery mode and without lose data and settings?
I have to install gapps nano another time to avoid problems?
Can you describe me step by step what I have to do?
Anyone update cyanogen?
pietrog80 said:
Anyone update cyanogen?
Click to expand...
Click to collapse
if not done yet i would recommend to increase partitions to 1 gb system and 4gb.
And I would install isorec recovery twrp 3.0.2-1 because cm recovery is not very useful.
Please read noob friendly guide "want update to cm13...." by Saber who made also one for "increase system partition.
Sent from my GT-I9100 using XDA-Developers Legacy app
pietrog80 said:
I have updated my galaxy s2 with cyanogenmod 13 and with gapps nano.
To install gapps without problems, I followed this steps:
1-reboot in philz recovery mode
2-Install cyanogen rom ( don't reboot)
3- Install gapps nano
4-Reboot
Now I would like to update cyanogen with nightly update without lose data. I tried to use cyandelta but some errors appear ( permission denied..)
I rebooted in recovery and now I have a clockwork recovery.
Can I install the nightly update with this recovery mode and without lose data and settings?
I have to install gapps nano another time to avoid problems?
Can you describe me step by step what I have to do?
Click to expand...
Click to collapse
If you use the official CM13, you can try the inbuilt update option. You can find it in Settings --> About Phone --> Cyanogenmod updates. There were bugs for a long time, but as far as I know everything has been fixed.
Or try out a dirty flash. Just flash the newer Nightly zip in recovery with wipe of /cache and /dalvik. Not sure if it is also necessary to reflash Gapps.
Edit: I ask myself if updating via settings still works since they switched to Lineage OS... If you try it please report here.