My question is this: is there a way to verify that the file system and the overall ROM is operating healthy and without any corruptions/problems?
This is why I ask.
So, to make a long and frustrating story short I am/was running the Ginger Clone 2.2 Final R5 ROM and after disabling the lagfix, I installed the SpeedMod Captivate Kernal.
The installation of the kernal seemed to go just fine, after the initial startup I deleted the "disable-lagfix" folder/file and rebooted the device. However, when the phone restarted it froze on the "Galaxy S I9000" screen and would not boot into recovery mode.
After much profanity and futile ADB "reboot recovery" commands, I flashed the phone back to stock with Odin. When the phone loaded again I rooted and installed ROM manager, then I proceeded to restore the ROM backup that I made prior to flashing the new kernal. The backup loaded successfully, but when I started the phone again, it went into boot-loop at the AT&T screen.
Now at this point I'm really pissed off . I went back into recovery and cleared the partition cache and reinstalled the Ginger Clone Rom, fresh. Thankfully I heard the lady cyborg voice stating that the lagfix was being applied, success . The phone started up just fine, and I was able to reinstate the backup rom that I had created earlier.
So now, I'm left wondering if my file system is operating how it should be, sans kernal flash.
Thanks in advance for any and all help.
Again... I hate to be that guy but you are posting in the wrong forum.
Please read the stickies and the rules before you decide to post.
Sent from my GT-I9000 using XDA App
yogib83 said:
My question is this: is there a way to verify that the file system and the overall ROM is operating healthy and without any corruptions/problems?
This is why I ask.
So, to make a long and frustrating story short I am/was running the Ginger Clone 2.2 Final R5 ROM and after disabling the lagfix, I installed the SpeedMod Captivate Kernal.
The installation of the kernal seemed to go just fine, after the initial startup I deleted the "disable-lagfix" folder/file and rebooted the device. However, when the phone restarted it froze on the "Galaxy S I9000" screen and would not boot into recovery mode.
After much profanity and futile ADB "reboot recovery" commands, I flashed the phone back to stock with Odin. When the phone loaded again I rooted and installed ROM manager, then I proceeded to restore the ROM backup that I made prior to flashing the new kernal. The backup loaded successfully, but when I started the phone again, it went into boot-loop at the AT&T screen.
Now at this point I'm really pissed off . I went back into recovery and cleared the partition cache and reinstalled the Ginger Clone Rom, fresh. Thankfully I heard the lady cyborg voice stating that the lagfix was being applied, success . The phone started up just fine, and I was able to reinstate the backup rom that I had created earlier.
So now, I'm left wondering if my file system is operating how it should be, sans kernal flash.
Thanks in advance for any and all help.
Click to expand...
Click to collapse
Well when you flashed back to stock and then restored your backup it went into a boot loop because the backup does not back up the kernel so the ROM you restored was trying to boot with the stock AT&T kernel...Not going to work. But when you did the fresh install of the ROM it had the kernel so it worked...
try afv or something like that in the market. Its by scary alien and you can verify md5 sum nand backup. i just flashed a new rom but once I get all set up I will come back with the name. Its a free in the market.
Sent from my GT-I9000 using XDA App
jhernand1102 said:
Well when you flashed back to stock and then restored your backup it went into a boot loop because the backup does not back up the kernel so the ROM you restored was trying to boot with the stock AT&T kernel...Not going to work. But when you did the fresh install of the ROM it had the kernel so it worked...
Click to expand...
Click to collapse
Thank you good Sir! That makes perfect sense.
yogib83 said:
Thank you good Sir! That makes perfect sense.
Click to expand...
Click to collapse
No problem Glad to help. Next time if you flash stock after installing ROM manager you can flash the kernel first and then don't boot up just go back into CWM recovery and then restore your backed up ROM and it will work fine.
Related
hey guys Im a new to the whole rooting and flashing custom roms thing. I love my N1 and I figured it was time to start playing with it more then the usual out of the box customizations.
I rooted the phone using the one click root app:
(cant post the link since Im a new user)
and then installed the Rom Manager.
I then installed the ClockworkMod recovery like it says to do.
Then I performed a Backup of the Current Rom using the Rom Manager
then Downloaded CyanogenMod 6.0.0-RC2 along with the Google Apps add on.
once the download completed it says do you want to do a wipe and also asks option to back up current rom. I checked both boxes and the phone boots into recovery mode.
Now this is where Im confused on what to do. At first I wasnt sure it the Rom manager would auto load the new rom, so I let it sit for like 10 min and realized it wasnt doing anything. Then I pressed the power button and volume at this point it gives me 3 options ..
1) reboot
2) Wipe
3) load update.zip
First I did a reboot ... which did nothing but re boot the phone, then I applied the update.zip and it failed and then I went to the Cyanogen Mod wiki page
on there is said to: "Select the option to Wipe data/factory reset. "
so I did that and then tried to install the update.zip ... which failed ... and basically erased my phone like the noob I am
So can someone please help me and tell me what Im doing wrong? also I installed titanium back up this time around to back up my apps.
Sounds like ClockworkMod Recovery did not flash. Try flashing it again in Rom Manager.
Should have been posted in Q&A
Thank you. Ill try that.
Sorry for not posting in Q&A as i didnt know about it ... Im new here so please forgive me.
Might be Clockworkmod ROM Manager...
I had all sort of problems with 2.1.0.5 and can't use any of the backups I created with it (they just hang when I try to restore them).
Everything seems OK with 2.1.0.6 though...
Sent from my Nexus One using XDA App
I reflashed Clockworkmod and that fixed it ... it flash the CyanogenMod rom, but once I was on there the radio wouldnt work, to I went back in re flashed the recovery.
danger-rat said:
Might be Clockworkmod ROM Manager...
I had all sort of problems with 2.1.0.5 and can't use any of the backups I created with it (they just hang when I try to restore them).
Everything seems OK with 2.1.0.6 though...
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
You had issues too? I couldn't restore any of my backups the other day as well.
Yeah, I was having random problems with my backups... took me a while to realize it was only my newer backups.
Finally worked out that it was the version of ROM Manager. Older versions work great, as does the latest...
Sent from my Nexus One using XDA App
Vegas_Sirk said:
I reflashed Clockworkmod and that fixed it ... it flash the CyanogenMod rom, but once I was on there the radio wouldnt work, to I went back in re flashed the recovery.
Click to expand...
Click to collapse
CM requires the 4.06.00.12_7 radio. Go to settings - about and look at the baseband version, that is your radio version. Also keep in mind most ROM's will not setup your APN, you will have to do that manually. I thought CM did, but I have not used it in a while. I am addicted to Enomther's ROM.
Hey guys, so I had MIUI since it came out and kept updating it every friday like I'm sure everyone else does that has it, but today I wanted to try out a Gingerbread ROM other than MIUI or CM7 so I went and tried to install Mosaic IV. I followed the tutorial on MobileTechVideos for installing it and when I got to the part where I had to install the zip from the sd card I did it and it got stuck at formatting partitions. So I waited a while, about ten minutes, then took out the battery and tried starting over from stock again. Then I realized that I was supposed to use a different kernel for Mosaic IV then the one Josh used in the video. So I downloaded that kernel and used that one instead of the one he used in the tutorial. And I couldn't get into recovery mode with it. So I flashed to stock again and redid the whole thing, this time I got into recovery and flashed it but it still got stuck at formatting partitions. So at this point I was like crap I have to get a different ROM. So I tried flashing Serendipity and that wouldn't install either. Then I tried MIUI again to at least get back to what I had earlier today, and I got an error while flashing the captivate-efsbackup zip in recovery. I have no idea what to do, all I want is to just get off of the stock firmware which im stuck with for now since I have to go to work in a little bit. If anyone can help it would be greatly appreciated. Thanks in advance
I had a similar problem, and the ultimate fix for me was this:
Flash back to eclair stock (which you did)
Master Clear (aka format internal sd - make sure to back up your stuff first!)
Install CWM (may have to go manually - renaming to update.zip and reinstalling packages)
Wipe dalvik cache and cache partition, as well as user data
Install a stable Froyo ROM (take your pick, preferably a full-wipe with no bootloaders)
Reboot to CWM and do a second dalvik/cache/user data cleaning
(If you're going GB)
reboot to download mode
flash stock GB (WATCH OUT FOR BOOTLOADERS!)
boot it up, let it settle, reboot to CWM
flash your GB rom.
(If not)
Go where you would go from a stable Froyo Rom.
That's how I got back from a messed up phone with GB bootloaders to a working Mosaic installation. I can't say it will definitely work for you, but it may give you some ideas.
+1 get clockwork recovery...you need to make sure the rom you are flashing is compatible with the version of CWR you are using.
For example a rom that needs to be installed with CWR3 you will need to install the zip presumably from CWR2. Pull the battery and reboot back to recovery - you should now be in the updated version of CWR. Then for safety sake - re install your zip.
Reboot and you should be all set.
I had lots of trouble going from 2.2 to 2.3. Flashing between 2.3 roms is very easy comparatively
milkytron said:
Hey guys, so I had MIUI since it came out and kept updating it every friday like I'm sure everyone else does that has it, but today I wanted to try out a Gingerbread ROM other than MIUI or CM7 so I went and tried to install Mosaic IV. I followed the tutorial on MobileTechVideos for installing it and when I got to the part where I had to install the zip from the sd card I did it and it got stuck at formatting partitions. So I waited a while, about ten minutes, then took out the battery and tried starting over from stock again. Then I realized that I was supposed to use a different kernel for Mosaic IV then the one Josh used in the video. So I downloaded that kernel and used that one instead of the one he used in the tutorial. And I couldn't get into recovery mode with it. So I flashed to stock again and redid the whole thing, this time I got into recovery and flashed it but it still got stuck at formatting partitions. So at this point I was like crap I have to get a different ROM. So I tried flashing Serendipity and that wouldn't install either. Then I tried MIUI again to at least get back to what I had earlier today, and I got an error while flashing the captivate-efsbackup zip in recovery. I have no idea what to do, all I want is to just get off of the stock firmware which im stuck with for now since I have to go to work in a little bit. If anyone can help it would be greatly appreciated. Thanks in advance
Click to expand...
Click to collapse
so your saying that you went to a gingerbread rom straight from MIUI? if that's true it failed because you didn't have the gingerbread bootloaders before you installed the rom
Sent from my Captivate
pwnerman said:
so your saying that you went to a gingerbread rom straight from MIUI? if that's true it failed because you didn't have the gingerbread bootloaders before you installed the rom
Sent from my Captivate
Click to expand...
Click to collapse
I did have the bootloaders, I went back to stock before I did anything just to be safe. I'm gonna try what the other guys said though right now, wish me luck haha
jmtheiss said:
I had a similar problem, and the ultimate fix for me was this:
Flash back to eclair stock (which you did)
Master Clear (aka format internal sd - make sure to back up your stuff first!)
Install CWM (may have to go manually - renaming to update.zip and reinstalling packages)
Wipe dalvik cache and cache partition, as well as user data
Install a stable Froyo ROM (take your pick, preferably a full-wipe with no bootloaders)
Reboot to CWM and do a second dalvik/cache/user data cleaning
(If you're going GB)
reboot to download mode
flash stock GB (WATCH OUT FOR BOOTLOADERS!)
boot it up, let it settle, reboot to CWM
flash your GB rom.
(If not)
Go where you would go from a stable Froyo Rom.
That's how I got back from a messed up phone with GB bootloaders to a working Mosaic installation. I can't say it will definitely work for you, but it may give you some ideas.
Click to expand...
Click to collapse
Alright so I have Andromeda 2.1 which is a froyo rom. Which method should I use to get to stock GB?
use Odin to flash gingerbread bootloaders then flash gingerbread roms
howtomen said:
use Odin to flash gingerbread bootloaders then flash gingerbread roms
Click to expand...
Click to collapse
I flashed the gingerbread stock rom and have it rooted with xcal's kernel, but when i flashed mosaic IV it got stuck at formatting partitions and i pulled the battery after about 15 minutes and then restarted my phone to find it stuck in a bootloop. So i had to start from stock again and now im back to gingerbread stock with root. I'm kinda scared to try again because it takes me like 30 minutes to get back to gingerbread stock with root. I think ill just stick with stock for a little bit
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.
Hi all. Yes I am a Noob first ever post in fact. I am however good at following directions and reading first. So far found nothing to address my issue.
Intro: First time flashing a Custom ROM although I did previously successfully install Cf-Root and Stock ICS from Sam Mobile using excellent instructions found here.
Background: 1) Decided to move from Rooted Stock ICS to new Aliance ICS -- spent all weekend reading up before developing courage to attempt. 2) Today Successfully downgraded to Gingerbread (Flashing the Darky Resurrection rom and following instructions exactly). 3) Uninstalled DarkyOTA and Cleared app data as specified in instruction 4) Installed Alliance OTA and ROM Config as specified 3) Successfully flashed a XXLPY repack via ODIN per http://forum.xda-developers.com/showpost.php?p=27199210&postcount=4instructions 5) Copied the Alliance ICS Rom Zip to external SD 6) Went into CWM as instructed and flashed file.
Result: received notices -- Preparing for Installation ... Cleaning the phone etc -- through to "Installing Extra Apps" ----- Have been staring at this part for 45 minutes now as no progress has been made.
Current situation: Staring dumbly at phone with fading hopes that the process will complete. Wondering how long my Mugen battery will hold out while I wait. Utterly clueless what to do next. Regretting my courage in attempting this.
Can someone help please?
Where did u come up with DARKY ICS it should be Alliance ICS, just recheck because DARKY ICS is for S2 did u flash S2 rom on Note......
bhasg1007 said:
Where did u come up with DARKY ICS it should be Alliance ICS, just recheck because DARKY ICS is for S2 did u flash S2 rom on Note......
Click to expand...
Click to collapse
You make a very good point --- but i can confirm that the zip was the following:\AllianceROM_N7000_ICS-v1.zip
Still hung (80 minutes now) on "Installing extra apps"
mutineer33 said:
You make a very good point --- but i can confirm that the zip was the following:\AllianceROM_N7000_ICS-v1.zip
Still hung (80 minutes now) on "Installing extra apps"
Click to expand...
Click to collapse
Download the Alliance rom again and reflash it, you might have a corrupted rom.
gee2012 said:
Download the Alliance rom again and reflash it, you might have a corrupted rom.
Click to expand...
Click to collapse
Thank you ---- I will try --- but first how do I get out of this hung install --- no button works --- if I just power down or pull the battery out before this flash has finished , will my phone still be usable?
mutineer33 said:
Thank you ---- I will try --- but first how do I get out of this hung install --- no button works --- if I just power down or pull the battery out before this flash has finished , will my phone still be usable?
Click to expand...
Click to collapse
Haven`t you made a cwm recovery (backup) before you went to flash the rom.
If so pull the battery, wait 30 seconds, insert the battery and go in recoverymode and restore your backup. If there is no backup go in downloadmode and reflash a stock rom and reroot this rom and start over.
gee2012 said:
Haven`t you made a cwm recovery (backup) before you went to flash the rom.
If so pull the battery, wait 30 seconds, insert the battery and go in downloadmode and restore your backup. If there is no backup go in downloadmode and reflash a stock rom and reroot this rom and start over.
Click to expand...
Click to collapse
OK will try --- Thank you and "Thanks" added
gee2012 said:
Haven`t you made a cwm recovery (backup) before you went to flash the rom.
If so pull the battery, wait 30 seconds, insert the battery and go in recoverymode and restore your backup. If there is no backup go in downloadmode and reflash a stock rom and reroot this rom and start over.
Click to expand...
Click to collapse
Ok -- and thanks again. The Good News is after pulling and reinserting the battery the phone booted up and into Alliance (it looks fantastic by the way) and appears to be working. A bit scary as the Flash process itself never actually completed. Since I am as of yet unfamiliar with the ROM I have no idea if I am missing anything (mostly just the wall paper and google search, play store, and Nova settings are displayed --- but app drawer has 49 apps and 36 widgets). So now I would be very interested in opinions as to ---
1) Anyway to validate whether EVERYTHING that was supposed to have flashed on this Rom is in fact there? Or can I assume that since the phone has booted up and is working in terms of voice and data connections that I have been lucky and all has gone well after the initial panic?
2) Related to the above should I reflash this ROM over itself to see if it fully completes this time?
Thank you again.
Congrats on getting past the hanging issue - it is always a nervous time when that happens. I would recommend you reboot the phone and check that it starts up again. If all is good, run with current system for a few days. If you start to notice anything wacky then would be the time to reflash ROM.
I'm a firm believer in "If it ain't broke don't fix it" Hopefully your Note will just work now.
Just before reflashing just confirm if you are fully rooted, install root explorer and check if u can paste in system if yes then for safety purposes just flash abyss 4.2 redpill kernel boot into the kernels cwm and perform wipe and reinstall the rom
TempusFudgeIt said:
Congrats on getting past the hanging issue - it is always a nervous time when that happens. I would recommend you reboot the phone and check that it starts up again. If all is good, run with current system for a few days. If you start to notice anything wacky then would be the time to reflash ROM.
I'm a firm believer in "If it ain't broke don't fix it" Hopefully your Note will just work now.
Click to expand...
Click to collapse
Thank you for the feedback. As it stands I Re-flashed again ---- and the flash hung again (this time @ "Cleaning phone". Started over a 3rd time and it went through perfectly.
No idea why the first two attempts failed -- but it looks like I am good to go.
bhasg1007 said:
Just before reflashing just confirm if you are fully rooted, install root explorer and check if u can paste in system if yes then for safety purposes just flash abyss 4.2 redpill kernel boot into the kernels cwm and perform wipe and reinstall the rom
Click to expand...
Click to collapse
Thank you for the suggestion. Per my post above, I think I am sorted out now.
I've got the same problem, are you on speedmod kernel???
Try to mount system and data from the mount menu.
I hope this can help you
I have the same problem... First I installed successfully the ROM but then i messed up something and my phone started to restart and then I went to recovery, Wiped Cache, Dalvik and then Wiped data, then i mount Data, started installing and it went to Installing extra apps and just froze... I hold the power button and it booted alliance rom only with nova launcher... No other launchers... I want to do this again but im afraid if it is going to get even worse Should I try again of doing this? I'm sure that the rom wasn't corrupted because the first time it worked... Shall i try flashing HydraCore and then flash alliance rom again?
EDIT: I've just flashed it again and it worked.. I have no idea what exactly happend, but it doesn't matter - it worked
Would appreciate if someone could help me with my problem - I had earlier used CF-Root to root and install recovery which went off well, took a nandroid backup and then tried to flash CM9 through recovery. WIthin a few seconds it rebooted, showed the Cyanogenmod splash screen and went back into recovery - only this time it was a newer recovery (6.0.0.2) than what CF-Root had installed. I'm not able to install through zip file and for some reason I am not able to restore from nandroid as it says the md5 does not match. So as of now I am stuck in recovery.
To add to this, I realize that I messed up as the instructions said to update to a GB rom if coming from Froyo, which I did not notice. Any idea what I can do from here? If I can still run through this process can someone point me in the direction of a suitable GB ROM I can install? My end goal is to be on CM9, but right now would just be happy to get back to the stock GB ROM as well.
Flash to the stock firmware again? at SamMobile? That is what I did when my device did not boot up after installing CWM recovery and some rom.
skiddyrow said:
Would appreciate if someone could help me with my problem - I had earlier used CF-Root to root and install recovery which went off well, took a nandroid backup and then tried to flash CM9 through recovery. WIthin a few seconds it rebooted, showed the Cyanogenmod splash screen and went back into recovery - only this time it was a newer recovery (6.0.0.2) than what CF-Root had installed. I'm not able to install through zip file and for some reason I am not able to restore from nandroid as it says the md5 does not match. So as of now I am stuck in recovery.
To add to this, I realize that I messed up as the instructions said to update to a GB rom if coming from Froyo, which I did not notice. Any idea what I can do from here? If I can still run through this process can someone point me in the direction of a suitable GB ROM I can install? My end goal is to be on CM9, but right now would just be happy to get back to the stock GB ROM as well.
Click to expand...
Click to collapse
you better use the overcome stock gingerbread safe 5 (the best stock for all situations) google overcome.com and get the files, you will find also a tutorial for how to stock your tab before updating it to overcome or cm9 etc...
If I helped you, please press the thanks button
MarlX said:
Flash to the stock firmware again? at SamMobile? That is what I did when my device did not boot up after installing CWM recovery and some rom.
Click to expand...
Click to collapse
so the reflash from scratch works for you
If I helped you, please press the thanks button
Thanks sos_sifou - worked great! I think I'll stick with the Overcome GB ROM for a while as it works pretty good, and look at CM9 / 10 whenever it gets stable!