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!
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).
Hi all,
Can someone help me please?
I have an S3, and have come from an S1 and several HTC's before that. Well versed in the world of flashing.
My friend has an S2, and is trying to flash a custom ROM (has tried several different ones).
He has successfully rooted and install CWM using CF-root, but when he flashes ROMs they do not work. They don't get errors when flashing, but then always gets bootloops he reboots.
The only thing that I could think was missing was from my S1 days when there was recovery 2e, but I understand the recovery is within the kernel on the S2, so thats not it.
I'm sure there is something simple missing.. he has followed the myriad of guides on here to the letter, with no joy.
His current ROM (flashed through Odin) is XWLPO (which according to several sources can be rooted with cf-root for XXLQ5)
Before flashing a custom rom, he needs to wipe at least cache and dalvik in recovery. If still not fixed, wipe data. But, never and never do this wipe in cwm while on lpo (despite the fixed v 5.6 cf root lq5 should be fine)
Sent from my GT-I9100 using Tapatalk 2
Phil3759 said:
Before flashing a custom rom, he needs to wipe at least cache and dalvik in recovery. If still not fixed, wipe data. But, never and never do this wipe in cwm while on lpo (despite the fixed v 5.6 cf root lq5 should be fine)
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Thank buddy.
Just to clarify, is it only the wipe data that doesn't work from recovery, or the cache & dalvik as well?
And I assume if you don't do it through recovery, then you do it through settings --> Backup and reset?
It is best to perform full wipe, wipe cache and dalvik.
from my personal expirience its better to flash a custom rom via CWM and not via odin and defenatly full wipe and fix permissions bevor reboot
darkside super wipe?
cant i just run darkside super wipe the flash a new rom thats it right or am i missing something
I believe someone here will find this helpful
General steps before flashing a new ROM.
Requirements: ROOT access, CWM recovery
***Backup your present ROM just incase***
1. Wipe data/ factory reset
2. Wipe cache partition
3. Wipe dalvik cache (under advanced)
4. Format /system (under mount)
5. Flash your desired Rom/zips
6. Fix permissions (under advanced)
Notes:
- If you are moving from from an AOSP ROM to Samsung (vice versa), perform all the steps above.
- If you are upgrading / downgrading from one android version to another e.g ICS to jellybean or 4.0.3 to 4.0.4, also perform all the steps above.
- If you are upgrading from a Samsung ROM to another wipe the same android version, you may skip step 1.
- if you are upgrading your Aosp/aokp Rom with another with the same android version e.g 4.0.4 Aosp to 4.0.4 aokp, you may also skip
step 1.
*******Important******
If you are presently running a Samsung based 4.0.4 Rom that is using Samsung based kernel e.g CF-ROOT or stock kernel, please flash Siyah kernel before performing any of the above steps. You will end up with ash unusable device if you don't adhere to this important information.
Swyped from my Samsung Galaxy SII
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
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.
Was flashing my friends i9305 and now it wont boot any rom I flash... always gets stuck on the first boot screen until I take out battery.
I flashed CWM 6.0.4.7 using odin.
I have tried flashing several roms (CM 11, CM 10.1, PACman 4.3)... Each one will flash with no errors, then when I reboot after correct GAPPS it just gets stuck on the loading screen forever and won't boot up into ROM.
Wipe data/cache, wipe dalvik, wipe system > Install rom from zip, install GAPPS from zip > reboot (even here I wipe system/data/cache - still doesnt work).
Any ideas on why it won't load up the roms....
only4dank said:
Was flashing my friends i9305 and now it wont boot any rom I flash... always gets stuck on the first boot screen until I take out battery.
I flashed CWM 6.0.4.7 using odin.
I have tried flashing several roms (CM 11, CM 10.1, PACman 4.3)... Each one will flash with no errors, then when I reboot after correct GAPPS it just gets stuck on the loading screen forever and won't boot up into ROM.
Wipe data/cache, wipe dalvik, wipe system > Install rom from zip, install GAPPS from zip > reboot (even here I wipe system/data/cache - still doesnt work).
Any ideas on why it won't load up the roms....
Click to expand...
Click to collapse
Did you flash a 19305 rom this is 19300 forum?
Wrong forum, report your own post and ask a moderator to move it to the i9305 q&a forum -anything here could brick it.