I'm using my P1000 as a development device, and I'm compiling CM9 from source. I have everything set up, and I've been doing fine with it...however, whenever I flash my updated zip from CWMR, it crashes and shuts the device off, leaving me in a state without recovery or a bootable system. This requires me to re-stock it and reflash everything all over again. This happens EVERY TIME. I've tried just flashing the Overcome kernel and zip, but it doesn't boot. Only reverting to stock fixes the issue.
Using Overcome's CWMR, I can flash any zip I want without issues, leaving me to believe that this is a CM9 CWMR issue. Has anyone else had this issue? I'm not sure what to do at this point, and I need this to work consistently between ROMs. I'm syncing the repo and going to do a fresh nightly compile, but I'm not sure it'll help.
Related
So I've been trying to flash CM5.0.8 and I tried flashing Cm6, but neither of them will boot up, at the moment I have the leaked version of FROYO flashed on my Nexus one, whenever I try to flash one of those mentioned it doesn't work. I have the latest radio, I've tried wiping, but it doesn't work. Help?
FIXED: I Flashed Clockwork Recovery and used that instead of Amon Ra, and now everything is fine.
What steps are you executing to flash your phone?
well, I first do a nandroid backup, and then I do a wipe, and I flash the Cm6 zip file, and then the flash the FR91 zip file. It stays on the X with the pad lock.
latest radio meaning 5.08? or the 4.06?
I never have had problems flashing roms, I recommend going back and checking the md5 sum. Wipe data/factory, cache, dalvik cache, then flash the rom, the gapps. Should do the trick, it could take awhile to boot up on first time. Cyangoen has typically taken alittle extra time for me.
I have the 4.06 radio. I tried to flash FRF50 and it didn't boot up either. SO now I'm trying the FRF90 stock.
So neither the stock version of FRF50 works, or FRF90. I'm out of ideas. Help?
Your phone gets to the bootloader and can load recovery - which is good.
In recovery wipe EVERYTHING before loading ROM, install CM6 from ZIP or whatever ROM you want (shouldn't matter), wipe again (data/cache/dalvik/whatever), and reboot.
Please re-download the ROMs, as you may have faulty downloads (most probably).
Okay, I did as you said, I redownloaded CM6, and I tried wiping, reflashing, and wiping again, but for some reason, it still stays at the X screen with the padlock. Err, I tried it with the FRF50 and it seemed to work though, but I was wondering why I'm having troubles with other roms.
I've realize that a lot of times verification fails on updates. Does this have to do with the recovery?
Which recovery are you using?
AmonRA the latest one.
If you have verification failures - means that your updates are faulty. Nothing good will come out of flashing them.
So I'm guessing it's not the recovery that's messed up, but the zip files I'm trying to flash?
I have a lot of verification fails. :\ I'm not sure why. Anyone know?
Trying to install the Cynogen ICS ROM, and when installing the .zip, it loads the Samsung flash screen with Cynogen, then get the green guy and loads of text for about half a second, then it just reboots. Over and over for about 10 mins. WHat went wrong? What should I do?
It happend the same to me.
I just removed the battery and put it back, entered in CWM and reinstalled the ROM.
Good luck!
I somehow got into a recovery mode, but with the assumption it would all go wrong again, tried to install the .zip Darky rom instead, went through the process and said it worked but then it just went back to the Cynogen loop problem!? I just tried a Restore instead, but I haven't rebooted yet, should I wipe everything again, and try the ICM .zip again?
Yep, just go with the whipe. I hope you did a backup.
OK turns out the Restore failed, so now trying to reinstall ICS .zip again. fingers crossed!
yep backed it up, not that its seems to have helped.
Well now it's stuck in the Galaxy S bootscreen...
that really sucks....did you deactivated the lagfix before running the rom?
If the problem persists you have to run a basic ROM using ODIN.
Yes deactivated the lagfixI can't get into recovery or anything now, except download mode.
Download mode is all you need to run a ROM with Odin.
I recommend Amestris, it is a good ROM, good battery life but the thread in not complete, there are some files missing...for now.
I've put some older ROM on I had, then tried to install ICS again but now when I use Clockwork, and select the file it goes to recovery but I can't select any zip files, just reboot back to this awful old ROM!
I had same issue when I installed ics, what I did that worked was pull battery and go back into cwm, reflashed ics zip and it fully installed that time. Had same experience when flashing cm7 before.
Not getting anywhere with this. I get an option to install zip from sdcard which is where the update is (an where the darky update also is which worked), but there is an option to update from internal SD, which is not where the file is. Is it in the wrong place?
I think you would be best to use Odin 1.3 to flash DarkyROM Ficeto JVT base rom.
are you sure those files are still on your sd card?
The reason you need to pull the battery and reflash the ICS rom a few times is because Samsung ROM (most) have a different partition layout to CM7 based roms (which the ICS port is one).
GL.
have been running my captivate on CM7 with Glitch v13 for a while, and having a lot of force close, and sometimes lockups, so decided to try the new Fasty III KK4 rom, the rom is supposed to have Corn kernel built in.
Well everytime I try to flash the zip in CWM, it says successfully installed please reboot, I reboot and it still show the Glitch boot images, and just sits at that screen for 10+ minutes.
I tried flashing just Corn kernel v7.06, says it finished, still reboots with Glitch logo.
I formatted data and cache, tried factory resets, cleared kernel, cleared dalvik, but it still seems the same everytime.
I was able to successfully flash the Glitch v13.1 update, and re-flash CM7, but I still cant seem to flash any other rom or kernel - any ideas?
CM Roms use a different file system than Samsung based roms (Fasty, Legend, Saurom, etc).
You will need to flash back to a stock image so that it will repartition your device back to the Samsung format. After that you can Odin/Heimdall/CWM flash to your new ROM.
thanks -I had a feeling it was something like that.
Dear friends,
Little background. I was on CM10 stable, but decided to I update to CM10.1 M1, After the update, had no market, however, so I tried to downgrade to CM10 stable and it bricked. So .. back to stock it is! Now I am having trouble getting out of stock. I am not new to flashing, but I never had this kind of a persistent problem.
The short summary of what I get no matter what I try is: Every kernel that is not the stock Eclair kernel has boot-animation messed up (random lines of color on screen), and I cannot enter recovery - I sometimes can boot sometimes cannot.
Steps I have taken
I went back to stock Eclair rom + non-root kernel (LINK).
I rooted (LINK)
But when I tried to update kernel to allow CWM, it bricked my phone. So back to stock, again!
I tried this a few times. Now, the latest attempt, I tried the stock 2.3.5 rom + rooted, CWM kernel (LINK... I get the phone running, but I cannot get into recovery, and no utility that has "reboot to recovery" has managed to get me into recovery.
The plea
All I want is CWM, so I can install what I want. Without it, I am stuck with Odin one-click and Odin flashable packages (Heimdall does not want to work right for me - the drivers are messed up - and trying to fix those brkeas my Odin drivers).
I have no data on the phone at the moment, I can reinstall everything if need be .. but I am out of ideas besides keep trying different roms and kernels until something gives me CWM and I am free again.
I have AT&T GB bootloaders.
thanks for any help, I will try to provide any additional info I can.
dozyaustin said:
Dear friends,
Little background. I was on CM10 stable, but decided to I update to CM10.1 M1, After the update, had no market, however, so I tried to downgrade to CM10 stable and it bricked. So .. back to stock it is! Now I am having trouble getting out of stock. I am not new to flashing, but I never had this kind of a persistent problem.
The short summary of what I get no matter what I try is: Every kernel that is not the stock Eclair kernel has boot-animation messed up (random lines of color on screen), and I cannot enter recovery - I sometimes can boot sometimes cannot.
Steps I have taken
I went back to stock Eclair rom + non-root kernel (LINK).
I rooted (LINK)
But when I tried to update kernel to allow CWM, it bricked my phone. So back to stock, again!
I tried this a few times. Now, the latest attempt, I tried the stock 2.3.5 rom + rooted, CWM kernel (LINK... I get the phone running, but I cannot get into recovery, and no utility that has "reboot to recovery" has managed to get me into recovery.
The plea
All I want is CWM, so I can install what I want. Without it, I am stuck with Odin one-click and Odin flashable packages (Heimdall does not want to work right for me - the drivers are messed up - and trying to fix those brkeas my Odin drivers).
I have no data on the phone at the moment, I can reinstall everything if need be .. but I am out of ideas besides keep trying different roms and kernels until something gives me CWM and I am free again.
I have AT&T GB bootloaders.
thanks for any help, I will try to provide any additional info I can.
Click to expand...
Click to collapse
Messed up screen = wrong bootloaders. Flash Odin KK4 with bootloaders
From there, follow this link.
Finally, you can get back up on CM10.1 - Btw, you had no market cause you didn't flash their Gapps.
UPDATE .. ugh that took a while:
1) From the master list LINK, wet back to 2.1, I897UCJF6
2) From the same thread installed I897UCKF1 with bootloaders
3) rooted: LINK (I know -not XDA)
4) removed the 3e recovery lock (LINK) - this did not seem to work, but I did do it.
5) installed Speedmod kernel from here LINK - this did not boot, but it did install CWM
6) installed CM10.0 Stable from SD cadr - twice
7) installed gapps
8) just did my first boot to CM10.
This is both a record for myself for later, and for anyone else that may find this useful.
BWolf56 said:
Messed up screen = wrong bootloaders. Flash Odin KK4 with bootloaders
From there, follow this link.
Finally, you can get back up on CM10.1 - Btw, you had no market cause you didn't flash their Gapps.
Click to expand...
Click to collapse
Ooooh. I learn something new every day! Thanks.
Sent from my SGH-I897 using xda app-developers app
Hey guys, so I am on samfail v2.5, TWIZtd rom 2.2, with the AQK5 build(U2 BL) and ever since I did a backup&restore with safestrap I've been getting kernel panics randomly at times and 100pct anytime I attempt to flash ANYTHING - either from flashfire or safestrap TWRP. I've already flashed the stock kernel in Odin which seemed to have worked initially (was going into panic within 2-3min everytime I booted up prior to stock kernel flash) not as random as before but still making it near impossible to use my phone as normal.
I've posted in the thread for safestrap, got the advice to reflash stock kernel and while it's helped, hasn't fixed the issue completely. Only thing I can think of is to wipe phone(don't want to if I don't need to) and re root, etc, etc. Here is a log from one of the kernel panics. Main msg it gave was "kernel stack is corrupted in ffff". Any help is greatly appreciated as I need to have device functioning normally.
https://drive.google.com/file/d/1edA_sYJ5wIXfQ7Ot8tSs7msU3Gz-iRXp/view?usp=drivesdk
EDIT - 2 DAYS LATER, PERFORMED A FULL WIPE AND HAVE FULL FLASHING ABILITIES BACK WITHOUT KERNEL PANIC =) ALTHOUGH I DID NOT REINSTALL SAFESTRAP.